WO2019149019A1

WO2019149019A1 - Data interaction method and apparatus, computer device, and storage medium

Info

Publication number: WO2019149019A1
Application number: PCT/CN2019/070023
Authority: WO
Inventors: 陶勇
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2018-01-30
Filing date: 2019-01-02
Publication date: 2019-08-08
Also published as: CN109344183B; CN109344183A

Abstract

A data interaction method, comprising: receiving a transaction request sent by a terminal, the transaction request carrying transaction data; extracting a transaction type and a product identifier from the transaction data; searching for a product transaction template corresponding to the transaction type and the product identifier; extracting from the transaction data a parameter value corresponding to a transaction parameter in the product transaction template, and generating a standard request packet according to the extracted parameter value and the product transaction template; searching for a service party to which the product identifier belongs, and obtaining a first data format of the service party; if the first data format is a non-standard format, searching for first data conversion information corresponding to the service party, and converting the standard request packet into a demand request packet according to the first data conversion information; and sending the demand request packet to a service server of the service party.

Description

Data interaction method, device, computer device and storage medium

Cross-reference to related applications

The present application claims to be filed on January 30, 2018, the Chinese Patent Office, Application No. 2018100908310, the priority of which is incorporated herein by reference. In this application.

Technical field

The application relates to a data interaction method, device, computer device and storage medium.

Background technique

As a sales platform, the mall platform can connect the products of each company to the platform and sell it online. The mall platform supports product transactions of a number of companies. In the process of product transactions such as trial and calculation of product costs, accounting, the mall platform needs to communicate and interact with each company. However, the inventor realized that the data formats of the data supported by the companies are different at present, and the mall platform needs to customize the data interface for each company, which requires a large amount of time and workload of the developer, resulting in excessive development cost.

Summary of the invention

In accordance with various embodiments disclosed herein, a data interaction method, apparatus, computer device, and storage medium are provided.

A data interaction method, including:

Receiving a transaction request sent by the terminal, where the transaction request carries transaction data;

Extracting the transaction type and product identification from the transaction data;

Finding a product transaction template corresponding to the transaction type and the product identifier;

Extracting a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generating a standard request message according to the extracted parameter value and the product transaction template;

Finding a service party to which the product identifier belongs, and acquiring a first data format of the service party;

When the first data format is a non-standard format, the first data conversion information corresponding to the service party is searched, and the standard request message is converted into a demand request message according to the first data conversion information;

Sending the demand request message to the service server of the service party.

A data interaction device comprising:

a request receiving module, configured to receive a transaction request sent by the terminal, where the transaction request carries transaction data;

a data extraction module, configured to extract a transaction type and a product identifier from the transaction data;

a template search module, configured to search for the transaction type and the product transaction template corresponding to the product identifier;

a message generating module, configured to extract a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generate a standard request message according to the extracted parameter value and the product transaction template;

a format obtaining module, configured to search for a service party to which the product identifier belongs, and obtain a first data format of the service party;

a message conversion module, configured to: when the first data format is a non-standard format, search for first data conversion information corresponding to the service party, and convert the standard request message into Demand request message; and

The first packet sending module is configured to send the demand request message to the service server of the service party.

A computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executable by the processor to cause the one or more processors to execute The following steps:

Sending the demand request message to the service server of the service party.

Computer readable instructions computer readable instructions one or more non-transitory computer readable storage medium storing computer readable instructions, when executed by one or more processors, causing one or more processors Perform the following steps:

Sending the demand request message to the service server of the service party.

Computer readable instructions Computer readable instructions The details of one or more embodiments of the present application are set forth in the accompanying drawings and description. Other features and advantages of the present invention will be apparent from the description, drawings and claims.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings to be used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without any creative work.

1 is an application scenario diagram of a data interaction method in accordance with one or more embodiments.

2 is a flow diagram of a method of data interaction in accordance with one or more embodiments.

3 is a block diagram showing the structure of a data interaction device in accordance with one or more embodiments.

4 is a diagram showing the internal structure of a computer device in accordance with one or more embodiments.

Detailed ways

In order to make the technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

The data interaction method provided by the present application can be applied to an application environment as shown in FIG. 1. The terminal communicates with the server through the network, and the server communicates with the service server through the network. The terminal sends a transaction request to the server, and after receiving the transaction request, the server acquires the transaction data in the transaction request, extracts the transaction type and the product identifier, and finds a corresponding product transaction template, and extracts the product transaction from the transaction data. The parameter value corresponding to the transaction parameter in the template generates a standard request message according to the extracted parameter value and the product transaction template, and the server searches for the business party to which the product identifier belongs, and determines whether the data format required by the business party is a standard data format. When the data format required by the service party is a non-standard data format, the generated standard request message is converted into a service request message according to the data conversion information corresponding to the service party, and the converted demand request message is sent to the service. The business server corresponding to the party, the transaction server processes the transaction request. The number of the terminal and the server of the service side may be one or more. The terminal can be, but is not limited to, various personal computers, notebook computers, smart phones, tablets, and portable wearable devices. The server and the business server can be implemented by a separate server or a server cluster composed of multiple servers.

In one embodiment, as shown in FIG. 2, a data interaction method is provided, which is applied to the server in FIG. 1 as an example, and includes the following steps:

Step 210: Receive a transaction request sent by the terminal, where the transaction request carries the transaction data.

The server in this embodiment may be a server of a mall platform, and the mall platform may be connected to multiple business parties, and the products of the business party are sold on the mall platform, and the user may purchase products through the mall platform. The user can operate through the terminal and find that the server of the mall platform initiates a transaction request. The server receives the transaction request initiated by the terminal.

The transaction request carries transaction data, which may include, but is not limited to, product data of the transaction product, transaction type, user information for initiating the request, terminal information, request code, request time, and the like.

Step 220, extracting the transaction type and product identification from the transaction data.

The server obtains the transaction data in the transaction request and extracts the transaction type and product identification from the transaction data. Among them, the transaction type is the type of the transaction initiated, and the product is an insurance product as an example. The transaction type can be the type of premium trial, underwriting, underwriting, and the like. The product identification is used to uniquely identify the products on the mall platform. The product identification can be the product number, product code, and the like. The product party can also determine the business party to which it belongs. If the unused business party provides the product with the same name on the platform, the business party to which the product belongs can be determined according to the product identifier.

Step 230: Find a product transaction template corresponding to the transaction type and the product identifier.

The server pre-stores product transaction templates for each product, and sets a plurality of product transaction templates corresponding to each transaction type for each product according to the transaction types that each product may involve. The product transaction template is stored in association with the product identification and transaction type. The server looks up the product transaction template corresponding to the extracted transaction type and product identification.

After the server processes the transaction request, it sends the request data to the service server of the corresponding business party, and finally the business server processes the transaction request of the user. The product transaction template specifies the parameter composition and data structure of the request data sent by the server to the service server. The parameter composition is a transaction parameter field required by the business party for transaction processing, and the data structure refers to an arrangement rule of each parameter field.

For example, the product transaction template of the premium trial transaction of the pension insurance product of the A insurance company's business party includes four basic components: the basic information of the insured, the basic information of the insured, the insurance information and the responsibility information. Each component further includes a plurality of transaction parameter fields, for example, the basic information of the policyholder includes a plurality of transaction parameter fields such as a product code, a number of insurance shares, and an insurance validity period. And the product trading template stipulates the arrangement rules of each component and each parameter field.

Step 240: Extract a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generate a standard request message according to the extracted parameter value and the product transaction template.

The standard request message is a message in the standard data format provided by the server. The server obtains the transaction parameters in the product transaction template, and extracts the parameter values corresponding to the transaction parameters from the transaction data. If the parameter value corresponding to the extracted product code field is P1394, the parameter value corresponding to the insurance validity period field is 2 years. The server will extract the parameter values and assemble the product transaction template and generate a standard request message.

Step 250: Find a service party to which the product identifier belongs, and obtain a first data format of the service party.

The server finds the business party to which the transaction product belongs based on the product identifier. Specifically, the server may search for the service party identifier of the service party corresponding to the product identifier, and obtain the first data format corresponding to the service party identifier after obtaining the service party identifier, where the first data format refers to the data format of the data required by the service party. The first data format may include a standard format and a non-standard format. The standard format is consistent with the data format provided by the server, and the non-standard format is different from the data format provided by the server, and is a data format specific to the business side.

Step 260: When the first data format is a non-standard format, the first data conversion information corresponding to the service party is searched, and the standard request message is converted into the demand request message according to the first data conversion information.

After obtaining the first data format, the server determines whether the first data format is a standard format. When the server determines that the first data format is a non-standard format, the first data conversion information corresponding to the service party identifier is searched, where the first data conversion information may be stored in the server locality in association with the service party identifier. Specifically, the first data conversion information may include a field mapping relationship between a standard format and a non-standard format difference field, and may also include a data structure of data in the request message required by the service side.

The server maps the difference field in the standard request message according to the first data conversion information that is found, and adjusts the data structure in the standard request message to generate a demand request message required by the service party.

Step 270: Send the demand request message to the service server of the service party.

The server sends the generated demand request packet to the service server corresponding to the service party identifier. After receiving the demand request message, the service server processes the transaction request of the user according to the demand request message.

In this embodiment, after receiving the transaction request, the server first searches for a product transaction template corresponding to the transaction request, generates a standard request message in a unified data format according to the transaction data and the product transaction template, and obtains data required by the corresponding service party. The format is judged. When it is judged that the data format required by the service party is a non-standard format, the standard request message is converted into a data format required by the business party according to the corresponding data conversion information of the service party, and the request data conforming to the demand of the business party can be automatically generated. Therefore, the data interface of the business side with special data format requirements is separately customized and developed, which reduces development cost and saves development time.

In one embodiment, the method further includes: when the first data format is a standard format, sending the standard request message to the service server of the service party.

When the server determines that the first data format is a standard format, it indicates that the format of the data required by the corresponding service party is the same as the data format provided by the server, and the server does not need to perform format conversion, and the server directly sends the generated standard request message to the service corresponding to the service party identifier. server.

After receiving the transaction request, the server can automatically convert the transaction data in the request into a standard format request message in a unified format, which can meet the data requirements of most business parties.

In one embodiment, the step of searching for the first data conversion information corresponding to the service party and converting the standard request message into the demand request message according to the first data conversion information includes: searching for a field mapping table corresponding to the service party; The field mapping table extracts the difference field from the standard request message; finds the custom field corresponding to the difference field from the field mapping table, replaces the difference field in the standard request message with the corresponding customized field; acquires the product identifier and the service The data structure of the request message corresponding to the party; the standard request message after the field replacement is adjusted according to the data structure of the request message, and a request request message is generated.

When performing data format conversion, the server searches for a field mapping table corresponding to the service party according to the service party identifier. The field mapping table may be stored in the server in advance, or may be stored in the service server and obtained by the server to the service server. The field mapping table stores the mapping relationship between the service provider and all the difference fields of the server, that is, the mapping relationship between the standard parameter field provided by the server and the customized field required by the service party, including the mapping relationship between the parameter field names and The correspondence between parameter field values.

For example, the insured gender field is the difference field between the server and the business party, the standard parameter field of the insured gender is named after-Gender, and the mapped requirement parameter field is named after-sex, and the insured gender is male. The standard parameter field value is M, and the mapped requirement parameter field value is 1.

The server obtains the standard parameter field name in the field mapping table, and searches for a parameter field name that is consistent with the standard parameter field name from the standard request message. When the consistent parameter field name is found, the consistent parameter field name and its The corresponding parameter field value is extracted as a difference field, and the server searches for a custom field name corresponding to the standard parameter field name from the field mapping relationship table, and extracts the corresponding customized field name and its customized field value as a custom field, and the standard request message is The difference field in the field is replaced with the extracted custom field.

In one of the embodiments, the server may classify the difference field according to the product to which it belongs in the field mapping table, for example, the field mapping relationship belonging to the same product may be stored in association with the product identifier. The server searches the field mapping table for the field mapping relationship corresponding to the product identifier, and then extracts the difference field from the standard request message according to the found field mapping relationship and performs field replacement.

In one embodiment, the server may store the mapping relationship between the different service parties and the difference fields of the server in the field mapping total table, and the mapping relationship between the difference fields of each service party is associated with the service party identifier. . The server can find the mapping relationship of the difference field corresponding to the service party according to the service party identifier.

After completing the replacement of all the difference fields in the standard request message, the server searches for the request message data structure corresponding to the product identifier and the service party identifier. Request messages for different products in the business side have a specific data structure. The data structure refers to the arrangement rules of various types of data in the request message. The server adjusts the order of the corresponding data in the standard request message after the difference field is replaced according to the arrangement rules of various types of data, and adjusts to generate a demand request message.

In this implementation, the parameter fields with different parameter formats of the server and the service party are uniformly stored in the field mapping table, which facilitates parameter field search and replacement.

In one embodiment, the step of adjusting the standard request message after the field replacement according to the request message data structure and generating the request request message includes: searching for the data with the loop attribute from the request message data structure. The class of the data class is obtained; the message data corresponding to the data class having the loop attribute is searched from the standard request message after the field replacement, and the found message data is segmented and the data class unit is obtained; The loop level of the data class to which the data class unit belongs, sorting the data class units and generating a demand request message.

The server obtains the data class in the request message data structure. The request message data structure stores data classes of request data, and each data class may include multiple parameter fields. For example, the data of the request message of an insurance product includes three types of data: the basic information of the insured, the basic information of the insured, and the type of insurance information, and each data class may include a plurality of parameter fields.

The server obtains the loop attribute value of each data class, and determines whether the data class has a loop attribute according to the loop attribute value. For example, if the value of the loop attribute is 1, the data class has a loop attribute, and the value of the loop attribute is 0, the data type does not have a loop attribute. The above values are only examples. The value of the loop attribute value is not limited to the above value. Each data class includes at least one data class unit. When the data class has a loop property, each data class unit in the data class needs to be cyclically arranged. Taking the insured basic information data class as an example, when there are multiple insured persons, the basic information of the insured person of each insured is a data type unit, and multiple multiple insured persons are required. The data class units are arranged in a loop.

The server finds the data class with the loop attribute according to the loop attribute value of the data class, and the server searches for the packet data corresponding to the found data class from the standard request message after the field replacement. In an embodiment, the server obtains the parameter field combination included in the data class, and searches for the packet data corresponding to each parameter field in the parameter field combination from the standard request message, and when multiple search corresponding to the parameter field are found, In the case of the field, the searched packet data is divided into data. Specifically, the searched data is divided according to the parameter field to obtain a plurality of data class units.

For example, the basic information data class of the policyholder includes a combination of parameter fields composed of a plurality of parameter fields such as a product code, a number of insurance shares, and an insurance validity period, and the server searches for a message corresponding to each parameter field from the standard request message that has been replaced by the field. Data, when multiple fields corresponding to the product code, the number of insured copies, and the insurance validity period parameter field are found, the found message data is divided into multiple product codes, the number of insured copies, and the insurance validity period parameter combination, thereby obtaining more Data class units.

The server obtains the loop level of the data class with the loop attribute, and determines the order of the loops between different data classes according to the level of the loop of different data classes. For a data class that does not have a loop attribute, it has a fixed arrangement position in the request message, and the server obtains the arrangement position of the data class that does not have the loop attribute, and adjusts the corresponding arrangement position of the value. Specifically, the data class with the highest cycle level is ranked first, and all the data class units with lower ranks are required to be listed after each of the highest data class units. When there is a data class with the same cycle level, according to the original The arrangement in the standard request message is arranged in order, and the data classes are arranged in a one-to-one correspondence.

Continue to take an insurance product as an example to illustrate, the insured basic information, the insured basic information and the insurance information three data categories, the insured basic information and insurance information two data categories have a circular attribute. The insured basic information data class includes two data class units, A insured information and B insured information, and the insurance information data class includes two data type units, C insurance information and D insurance information. The insured basic information data class does not have a loop attribute, and the server obtains the arrangement position of the insured basic information data class, and the arrangement position is before the insured basic information and the insurance type information.

In the standard request message, the loop level of the insured basic information data class is higher than the loop level of the insurance information data class, and the order of each data type unit in the standard request message is the basic information of the insured, and the information of the A insured. , C insurance information, D insurance information, B insured information, C insurance information, D insurance information. That is, the data classes with higher cycle levels are ranked first, and all data class units with lower ranks need to be listed after each higher-level data class unit. The order of the data class units belonging to the same data class is not limited. Preferably, the order of the parameter fields in the transaction data may be sorted.

The server acquires a loop level of two data categories of the insured basic information and the insurance information, wherein the loop level of the insured basic information data class is equal to the loop level of the insurance information data category. According to the cycle level, the data arrangement order in the standard request message is adjusted to: basic information of the insured, A insured information, C insurance information, A insured information, D insurance information, B insured information, C insurance information , B insured information, D insurance information.

In this embodiment, by storing the data structure of the request message in the server in advance, the server can automatically adjust the data sequence of the data structure in the standard request message according to the cycle level of the data class in the data structure, thereby improving data conversion. effectiveness.

In one embodiment, after the step of sending the demand request message to the service server of the service party, the method includes: receiving a transaction response message; extracting the service party identifier from the transaction response message, and obtaining the extracted service party identifier corresponding to a second data format; when the second data format is a non-standard format, searching for the second data conversion information corresponding to the extracted service party identifier, and converting the transaction response message into a standard response message according to the second data conversion information .

After the service party processes the request packet sent by the server, it returns the transaction processing result, that is, the transaction response message, to the server, and the server receives the transaction response message sent by the service server. The transaction response message may include data such as transaction code, customer information, and processing result. When the data format of the transaction response message sent by the business party maintains its own data format, some business parties have the same data format as the server, and some business parties have their own customized data format.

The server extracts the service party identifier from the transaction response message, and obtains the second data format corresponding to the service party identifier. It should be noted that, when the service party in this embodiment is consistent with the service party in the foregoing embodiment, the first data format and the second data format are the same, and the first and second in the text are only for different parties. The situation is to distinguish.

The server determines whether the second data format is a standard format. When it is determined that the second data format is a standard format, the data conversion is not required, and the server may parse the transaction request message and return it to the terminal. When the server determines that the second data format is a standard format, the server searches for the second data conversion information corresponding to the service party identifier. The second data conversion information may include a field mapping table corresponding to the service party identifier and a data structure in the standard request message corresponding to the product identifier. The server first searches the difference field in the transaction response message according to the field mapping table, and converts the difference field from the custom field of the business party to the standard field of the server. After the field is converted, the server adjusts the order of the data in the transaction response message after the field is replaced according to the data structure in the standard request message, and generates a standard response message after the adjustment. For the specific field replacement method and the data structure adjustment method, reference may be made to the method steps of requesting message format conversion in the foregoing embodiment, and details are not described herein again. The server parses the standard response message and returns the parsed data to the terminal.

In this embodiment, when the transaction response message returned by the terminal is in a non-standard format, the server converts it into a standard data format of the server to parse the processing result of the request.

In one embodiment, the standard request message and the standard request message in the foregoing embodiment may be in the form of a JSON string and may be encoded in a UTF-8 encoding format. It should be noted that, in other embodiments, the server may also adopt other data formats or encoding manners according to specific situations.

In one embodiment, the method further includes: counting the number of requests for the current transaction request; when the number of requests exceeds the preset request threshold, starting a new request processing thread; when the first data format is a non-standard format, generating The data conversion task allocates the data conversion task to the new request processing thread, performs the first data conversion information corresponding to the search service party in the new request processing thread, and converts the standard request message into the requirement according to the first data conversion information. The step of requesting a message.

The server can periodically count the number of requests for transaction requests sent by each terminal currently received. And obtaining a preset request threshold, the server compares the current number of requests with a preset request threshold, and when the number of requests is greater than the preset request threshold, the server starts a new request processing thread. When the server determines that the first data format of the service party corresponding to the request is a non-standard format, the server generates a data conversion task according to the transaction data and the generated standard request message, wherein the data conversion task may be identified according to the requested transaction code. . The server allocates the data conversion task to the new request processing thread that is started, performs the first data conversion information corresponding to the search service party in the new request processing thread, and converts the standard request message into the requirement according to the first data conversion information. The step of requesting a message. After the request request packet is generated, it can be directly sent to the service server corresponding to the service party ID. The processing task of processing the data format of the standard request message is processed in the new request processing thread, the task amount of the main processing thread is reduced, and the system is blocked from being excessively caused by the request.

In one of the embodiments, when the server detects that the current number of requests is less than the preset request threshold, the task is no longer assigned to the new request processing thread, and is closed after all data conversion tasks in the new request processing thread finish processing. The new request processing thread. So as to avoid thread redundancy caused by too many threads when the amount of tasks is too small.

It should be understood that although the various steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, the execution of these sub-steps or stages The order is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.

In one embodiment, as shown in FIG. 3, a data interaction apparatus is provided, including: a request receiving module 310, a data extracting module 320, a template searching module 330, a message generating module 340, a format obtaining module 350, and a newspaper. The text conversion module 360 and the first message sending module 370, wherein:

The request receiving module 310 is configured to receive a transaction request sent by the terminal, where the transaction request carries the transaction data.

The data extraction module 320 is configured to extract a transaction type and a product identifier from the transaction data.

The template search module 330 is configured to find a product transaction template corresponding to the transaction type and the product identifier.

The message generating module 340 is configured to extract a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generate a standard request message according to the extracted parameter value and the product transaction template.

The format obtaining module 350 is configured to find a service party to which the product identifier belongs, and obtain a first data format of the service party.

The message conversion module 360 is configured to: when the first data format is a non-standard format, search for the first data conversion information corresponding to the service party, and convert the standard request message into the demand request message according to the first data conversion information.

The first message sending module 370 is configured to send the demand request message to the service server of the service party.

In one embodiment, the apparatus further includes:

The second packet sending module is configured to send the standard request packet to the service server of the service party when the first data format is a standard format.

In an embodiment, the message conversion module 360 may include:

The mapping table searching module is configured to find a field mapping table corresponding to the business party.

The difference field extraction module is configured to extract the difference field from the standard request message according to the field mapping table.

The field replacement module is configured to find a custom field corresponding to the difference field from the field mapping table, and replace the difference field in the standard request message with the corresponding customized field.

The structure obtaining module is configured to obtain a product identifier and a request message data structure corresponding to the service party.

The requirement message generating module is configured to adjust the standard request message after the field replacement according to the request message data structure and generate a demand request message.

In one of the embodiments, the requirement message generating module may include:

The data class finding module is configured to find a data class having a loop attribute from the request message data structure.

A level acquisition module for obtaining a loop level of a data class.

The unit splitting module is configured to search for the packet data corresponding to the data class having the loop attribute from the standard request message after the field replacement, and divide the found message data to obtain the data class unit.

The unit arranging module is configured to arrange the data class units according to the cycle level of the data class to which the data class unit belongs and generate a demand request message.

In one embodiment, the apparatus may further include:

The response message receiving module is configured to receive a transaction response message.

The second format extraction module is configured to extract a service party identifier from the transaction response message, and obtain a second data format corresponding to the extracted service party identifier.

The standard message conversion module is configured to: when the second data format is a non-standard format, search for the second data conversion information corresponding to the extracted service party identifier, and convert the transaction response message into a standard response according to the second data conversion information. Message.

In one embodiment, the apparatus may further include:

The request statistics module is used to count the number of requests for the current transaction request.

A thread initiation module is configured to start a new request processing thread when the number of requests exceeds a preset request threshold.

a step execution module, configured to: when the first data format is a non-standard format, generate a data conversion task, allocate the data conversion task to the new request processing thread, and execute the first corresponding to the search service party in the new request processing thread. The data conversion information is a step of converting the standard request message into the demand request message according to the first data conversion information.

For the specific definition of the data interaction device, reference may be made to the definition of the data interaction method in the above, and details are not described herein again. The various modules in the above data interaction device may be implemented in whole or in part by software, hardware, and combinations thereof. Each of the above modules may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in FIG. The computer device includes a processor, memory, network interface, and database connected by a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The non-volatile storage medium stores an operating system, computer readable instructions, and a database. The internal memory provides an environment for operation of an operating system and computer readable instructions in a non-volatile storage medium. The database of the computer device is used to store data such as product transaction templates, data conversion information, and the like. The network interface of the computer device is used to communicate with an external terminal via a network connection. The computer readable instructions are executed by a processor to implement a method of data interaction.

It will be understood by those skilled in the art that the structure shown in FIG. 4 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied. The specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.

A computer device comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to perform the steps of: receiving a transaction sent by the terminal Requesting, the transaction request carries the transaction data; extracting the transaction type and the product identification from the transaction data; finding the product transaction template corresponding to the transaction type and the product identification; and extracting the parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, And generating a standard request message according to the extracted parameter value and the product transaction template; searching for the service party to which the product identifier belongs, and obtaining the first data format of the service party; when the first data format is a non-standard format, searching for the corresponding service party The first data conversion information is used to convert the standard request message into a demand request message according to the first data conversion information; and send the demand request message to the service server of the service side.

In one of the embodiments, the processor, when executing the computer readable instructions, further implements the step of: transmitting the standard request message to the service server of the service party when the first data format is a standard format.

In one embodiment, the processor executes the computer readable instructions to implement the first data conversion information corresponding to the search service party, and the step of converting the standard request message into the demand request message according to the first data conversion information is further used to: Find a field mapping table corresponding to the service party; extract the difference field from the standard request message according to the field mapping table; find a custom field corresponding to the difference field from the field mapping table, and replace the difference field in the standard request message with Corresponding custom field; obtaining the product identifier and the request message data structure corresponding to the service party; adjusting the standard request message after the field replacement according to the request message data structure and generating the demand request message.

In one of the embodiments, the processor executes the computer readable instructions to implement the step of adjusting the standard request message after the field replacement according to the request message data structure and generating the request request message, and is further used for: the request message Find the data class with the loop attribute in the data structure; obtain the loop level of the data class; find the message data corresponding to the data class with the loop attribute from the standard request message after the field replacement, and find the message The data is segmented and the data class unit is obtained; according to the cycle level of the data class to which the data class unit belongs, the data class units are arranged and a demand request message is generated.

In one embodiment, the processor further implements the following steps: receiving a transaction response message; extracting a service party identifier from the transaction response message, and acquiring a second data format corresponding to the extracted service party identifier. When the second data format is a non-standard format, the second data conversion information corresponding to the extracted service party identifier is searched, and the transaction response message is converted into a standard response message according to the second data conversion information.

In one embodiment, the processor, when executing the computer readable instructions, further implements the steps of: counting the number of requests for the current transaction request; when the number of requests exceeds the preset request threshold, initiating a new request processing thread; when the first data format When the data format is non-standard, the data conversion task is generated, the data conversion task is allocated to the new request processing thread, and the first data conversion information corresponding to the search service party is executed in the new request processing thread, and the first data conversion information is The step of converting a standard request message into a request request message.

One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of: receiving by a terminal Transaction request, transaction request carries transaction data; extract transaction type and product identification from transaction data; find product transaction template corresponding to transaction type and product identification; extract parameter value corresponding to transaction parameter in product transaction template from transaction data And generating a standard request message according to the extracted parameter value and the product transaction template; searching for the service party to which the product identifier belongs, obtaining the first data format of the service party; and when the first data format is a non-standard format, searching for the service party corresponding The first data conversion information is used to convert the standard request message into a demand request message according to the first data conversion information; and send the demand request message to the service server of the service side.

In one of the embodiments, the computer readable instructions are further executed by the processor to: when the first data format is a standard format, send the standard request message to the service server of the business party.

In one embodiment, the computer readable instructions are executed by the processor to search for first data conversion information corresponding to the service party, and are further used to implement the step of converting the standard request message into the demand request message according to the first data conversion information. Finding a field mapping table corresponding to the service party; extracting a difference field from the standard request message according to the field mapping table; finding a custom field corresponding to the difference field from the field mapping table, and replacing the difference field in the standard request message For the corresponding custom field, the product identifier and the request message data structure corresponding to the service party are obtained; the standard request message after the field replacement is adjusted according to the request message data structure, and the demand request message is generated.

In one embodiment, the computer readable instructions are further implemented by the processor when the processor performs the step of adjusting the standard request message after the field replacement according to the request message data structure and generating the demand request message: Find the data class with the loop attribute in the text data structure; obtain the loop level of the data class; search for the message data corresponding to the data class with the loop attribute from the standard request message after the field replacement, and find the reported message The text data is segmented and the data class unit is obtained; according to the cycle level of the data class to which the data class unit belongs, the data class units are arranged and a demand request message is generated.

In one embodiment, when the computer readable instructions are executed by the processor, the following steps are further performed: receiving a transaction response message; extracting a service party identifier from the transaction response message, and acquiring the second data corresponding to the extracted service party identifier a format; when the second data format is a non-standard format, searching for the second data conversion information corresponding to the extracted service party identifier, and converting the transaction response message into a standard response message according to the second data conversion information.

In one of the embodiments, the computer readable instructions are further executed by the processor to: count the number of requests for the current transaction request; when the number of requests exceeds the preset request threshold, initiate a new request processing thread; when the first data When the format is a non-standard format, a data conversion task is generated, the data conversion task is allocated to the new request processing thread, and the first data conversion information corresponding to the search service party is executed in the new request processing thread, and the first data conversion information is performed according to the first data conversion information. The step of converting a standard request message into a request request message.

One of ordinary skill in the art can understand that all or part of the process of implementing the above embodiments can be completed by computer readable instructions, which can be stored in a non-volatile computer. The readable storage medium, which when executed, may include the flow of an embodiment of the methods as described above. Any reference to a memory, storage, database or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain. Synchlink DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The technical features of the above embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, It is considered to be the range described in this specification.

The above-mentioned embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims

A data interaction method, including:

Receiving a transaction request sent by the terminal, where the transaction request carries transaction data;

Extracting the transaction type and product identification from the transaction data;

Finding a product transaction template corresponding to the transaction type and the product identifier;

Extracting a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generating a standard request message according to the extracted parameter value and the product transaction template;

Finding a service party to which the product identifier belongs, and acquiring a first data format of the service party;

When the first data format is a non-standard format, the first data conversion information corresponding to the service party is searched, and the standard request message is converted into a demand request message according to the first data conversion information;

Sending the demand request message to the service server of the service party.
The method of claim 1 further comprising:

When the first data format is a standard format, the standard request message is sent to the service server of the service party.
The method according to claim 1, wherein the searching for the first data conversion information corresponding to the service party, and converting the standard request message into a request request message according to the first data conversion information Steps, including:

Find a field mapping table corresponding to the service party;

Extracting a difference field from the standard request message according to the field mapping table;

Finding a custom field corresponding to the difference field from the field mapping table, and replacing the difference field in the standard request message with the corresponding customized field;

Obtaining the product identifier and a request message data structure corresponding to the service party; and

The standard request message after the field replacement is adjusted according to the request message data structure, and a demand request message is generated.
The method according to claim 3, wherein the step of adjusting the standard request message after the field replacement according to the request message data structure and generating the demand request message comprises:

Finding a data class having a loop attribute from the request message data structure;

Obtaining a loop level of the data class;

And searching for the packet data corresponding to the data class having the cyclic attribute from the standard request message after the field replacement, and dividing the found message data to obtain the data class unit;

And arranging the data class units according to a cycle level of the data class to which the data class unit belongs and generating a demand request message.
The method according to claim 1, wherein the step of transmitting the demand request message to the service server of the service party comprises:

Receiving a transaction response message;

Extracting a service party identifier from the transaction response message, and acquiring a second data format corresponding to the extracted service party identifier; and

When the second data format is a non-standard format, searching for the second data conversion information corresponding to the extracted service party identifier, and converting the transaction response message into a standard response message according to the second data conversion information .
The method of claim 1 further comprising:

Count the number of requests for the current transaction request;

Initiating a new request processing thread when the number of requests exceeds a preset request threshold; and

Generating a data conversion task, assigning the data conversion task to the new request processing thread, and performing the searching in the new request processing thread when the first data format is a non-standard format The first data conversion information corresponding to the service party, and the step of converting the standard request message into a demand request message according to the first data conversion information.
A data interaction device comprising:

a request receiving module, configured to receive a transaction request sent by the terminal, where the transaction request carries transaction data;

a data extraction module, configured to extract a transaction type and a product identifier from the transaction data;

a template search module, configured to search for the transaction type and the product transaction template corresponding to the product identifier;

a message generating module, configured to extract a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generate a standard request message according to the extracted parameter value and the product transaction template;

a format obtaining module, configured to search for a service party to which the product identifier belongs, and obtain a first data format of the service party;

a message conversion module, configured to: when the first data format is a non-standard format, search for first data conversion information corresponding to the service party, and convert the standard request message into Demand request message; and

The first packet sending module is configured to send the demand request message to the service server of the service party.
The device according to claim 7, further comprising:

The second packet sending module is configured to send the standard request packet to the service server of the service party when the first data format is a standard format.
A computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executed by the one or more processors to cause the one or more The processors perform the following steps:

Receiving a transaction request sent by the terminal, where the transaction request carries transaction data;

Extracting the transaction type and product identification from the transaction data;

Finding a product transaction template corresponding to the transaction type and the product identifier;

Extracting a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generating a standard request message according to the extracted parameter value and the product transaction template;

Finding a service party to which the product identifier belongs, and acquiring a first data format of the service party;

When the first data format is a non-standard format, the first data conversion information corresponding to the service party is searched, and the standard request message is converted into a demand request message according to the first data conversion information;

Sending the demand request message to the service server of the service party.
The computer apparatus according to claim 9, wherein said processor further performs the following steps when said computer readable instructions are executed:

When the first data format is a standard format, the standard request message is sent to the service server of the service party.
The computer device according to claim 9, wherein the processor executes the first readable data corresponding to the service party when the computer readable instructions are executed, and according to the first data conversion information The step of converting the standard request message into the demand request message includes:

Find a field mapping table corresponding to the service party;

Extracting a difference field from the standard request message according to the field mapping table;

Finding a custom field corresponding to the difference field from the field mapping table, and replacing the difference field in the standard request message with the corresponding customized field;

Obtaining the product identifier and a request message data structure corresponding to the service party; and

The standard request message after the field replacement is adjusted according to the request message data structure, and a demand request message is generated.
The computer apparatus according to claim 11, wherein said processor executes said computer readable instructions to perform adjustment of a standard request message after field replacement according to said request message data structure and generate a request The steps for requesting a message, including:

Finding a data class having a loop attribute from the request message data structure;

Obtaining a loop level of the data class;

And searching for the packet data corresponding to the data class having the cyclic attribute from the standard request message after the field replacement, and dividing the found message data to obtain the data class unit;

And arranging the data class units according to a cycle level of the data class to which the data class unit belongs and generating a demand request message.
The computer apparatus according to claim 9, wherein said processor further performs the following steps when said computer readable instructions are executed:

Receiving a transaction response message;

Extracting a service party identifier from the transaction response message, and acquiring a second data format corresponding to the extracted service party identifier; and

When the second data format is a non-standard format, searching for the second data conversion information corresponding to the extracted service party identifier, and converting the transaction response message into a standard response message according to the second data conversion information .
The computer apparatus according to claim 9, wherein said processor further performs the following steps when said computer readable instructions are executed:

Count the number of requests for the current transaction request;

Initiating a new request processing thread when the number of requests exceeds a preset request threshold; and

Generating a data conversion task, assigning the data conversion task to the new request processing thread, and performing the searching in the new request processing thread when the first data format is a non-standard format The first data conversion information corresponding to the service party, and the step of converting the standard request message into a demand request message according to the first data conversion information.
One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:

Receiving a transaction request sent by the terminal, where the transaction request carries transaction data;

Extracting the transaction type and product identification from the transaction data;

Finding a product transaction template corresponding to the transaction type and the product identifier;

Extracting a parameter value corresponding to the transaction parameter in the product transaction template from the transaction data, and generating a standard request message according to the extracted parameter value and the product transaction template;

Finding a service party to which the product identifier belongs, and acquiring a first data format of the service party;

When the first data format is a non-standard format, the first data conversion information corresponding to the service party is searched, and the standard request message is converted into a demand request message according to the first data conversion information;

Sending the demand request message to the service server of the service party.
The storage medium of claim 15 wherein said computer readable instructions, when executed by said processor, further perform the following steps:

When the first data format is a standard format, the standard request message is sent to the service server of the service party.
The storage medium according to claim 15, wherein the computer readable instructions are executed by the processor to perform first search for first data conversion information corresponding to the service party, according to the first data conversion information The step of converting the standard request message into a request request message includes:

Find a field mapping table corresponding to the service party;

Extracting a difference field from the standard request message according to the field mapping table;

Finding a custom field corresponding to the difference field from the field mapping table, and replacing the difference field in the standard request message with the corresponding customized field;

Obtaining the product identifier and a request message data structure corresponding to the service party; and

The standard request message after the field replacement is adjusted according to the request message data structure, and a demand request message is generated.
The storage medium according to claim 17, wherein said computer readable instructions are executed by said processor to perform adjustment and generation of standard request messages after field replacement according to said request message data structure The steps of the request request message, including:

Finding a data class having a loop attribute from the request message data structure;

Obtaining a loop level of the data class;

And searching for the packet data corresponding to the data class having the cyclic attribute from the standard request message after the field replacement, and dividing the found message data to obtain the data class unit;

And arranging the data class units according to a cycle level of the data class to which the data class unit belongs and generating a demand request message.
The storage medium of claim 15 wherein said computer readable instructions, when executed by said processor, further perform the following steps:

Receiving a transaction response message;

Extracting a service party identifier from the transaction response message, and acquiring a second data format corresponding to the extracted service party identifier; and

When the second data format is a non-standard format, searching for the second data conversion information corresponding to the extracted service party identifier, and converting the transaction response message into a standard response message according to the second data conversion information .
The storage medium of claim 15 wherein said computer readable instructions, when executed by said processor, further perform the following steps:

Count the number of requests for the current transaction request;

Initiating a new request processing thread when the number of requests exceeds a preset request threshold; and

Generating a data conversion task, assigning the data conversion task to the new request processing thread, and performing the searching in the new request processing thread when the first data format is a non-standard format The first data conversion information corresponding to the service party, and the step of converting the standard request message into a demand request message according to the first data conversion information.