Configuration interface butt joint and analysis method, device, equipment and medium

Abstract

The invention discloses a configured interface docking and analysis method, device and equipment and a medium, and the method comprises the steps: obtaining an interface document of a third-party platform, and combining with preset configuration items according to the interface document to obtain configuration information; the configuration information and the channel identifier are associated and stored in a preset database; in response to a service request for a third-party platform, obtaining configuration information from a preset database; the service request carries a channel identifier and request service data; assembling based on the request configuration and the request business data to obtain a request body, and sending the request body to a third-party platform according to the service address and the request format; and extracting response service data obtained by the third-party platform in response to the request body based on the request response configuration. Through the configuration mode, the tedious development process is avoided, automatic data extraction is achieved through the configuration information corresponding to the third-party platform, rapid docking is completed, the docking efficiency is improved, the research and development period is shortened, and the method can be widely applied to the technical field of data processing.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device, equipment and medium for configurable interface docking and analysis. Background Art

[0002] In the process of software system development, more and more business scenarios need to connect to the interfaces of multiple third-party platforms. For the interface of a single platform, the request protocol, interface specification, request body structure, and response body structure are all fixed, but multiple third-party platforms are different. The traditional connection method requires manual code writing, iteration, and testing and online release, which is repetitive and time-consuming. Summary of the invention

[0003] The present invention proposes a configurable interface docking and parsing method, device, equipment and medium, aiming to solve one of the technical problems in the related technology at least to a certain extent. The embodiment of the present invention can efficiently implement interface docking and calling of a third-party platform.

[0004] On the one hand, an embodiment of the present invention provides a configurable interface docking and parsing method, including:

[0005] Obtain the interface document of the third-party platform, and obtain configuration information according to the interface document combined with the preset configuration items; the configuration information is associated with the channel identifier of the third-party platform and stored in a preset database; the configuration information includes the service address, request format, request configuration and request response configuration of the third-party platform;

[0006] In response to a service request for a third-party platform, configuration information is obtained from a preset database; the service request carries a channel identifier and requested service data;

[0007] The request body is assembled based on the request configuration and the request business data, and is sent to the third-party platform according to the service address and request format;

[0008] Extract the response business data obtained by the third-party platform in response to the request body based on the request response configuration.

[0009] Optionally, the interface document includes the interface URL of the third-party platform, the request header format, the request template, the dynamic variable set, the response type, the key mapping field and the success identifier; and obtaining the configuration information according to the interface document combined with the preset configuration items includes the following steps:

[0010] Get the service address according to the interface url configuration;

[0011] Get the request format according to the request header format configuration;

[0012] Get request configuration according to request template and dynamic variable set configuration;

[0013] Get the request response configuration based on the response type, key mapping fields, and success indicator configuration.

[0014] Optionally, in response to a service request for a third-party platform, obtaining configuration information from a preset database includes the following steps:

[0015] In response to a service request for a third-party platform, a preset database is traversed and matched through a channel identifier carried in the service request;

[0016] The configuration information of the third-party platform is obtained according to the association results of the traversal matching.

[0017] Optionally, the request configuration includes a request template and a dynamic variable set of a third-party platform; each dynamic variable in the dynamic variable set includes its corresponding variable name, variable calculation method and variable calculation parameter list; assembling the request body based on the request configuration combined with the request business data includes the following steps:

[0018] Extracting and obtaining business parameter values ​​of business variables based on requested business data;

[0019] Call the variable calculation method to obtain the dynamic parameter value of the corresponding dynamic variable in the dynamic variable set;

[0020] The business parameter values ​​and dynamic parameter values ​​are sequentially filled into the positions of the corresponding business variables and dynamic variables in the request template to obtain the request body.

[0021] Optionally, the request response configuration includes a response type, a key mapping field, and a success identifier; extracting the response business data obtained by the third-party platform in response to the request body based on the request response configuration includes the following steps:

[0022] Obtain response data output by the third-party platform in response to the request body based on the response type;

[0023] Extract result fields from the response data based on the key mapping fields, and compare the result fields with the success identifier;

[0024] When the result field is consistent with the comparison result of the successful identification, the business field is extracted from the response data as the response business data based on the key mapping field.

[0025] Optionally, the method further comprises the following steps:

[0026] Generate a callback receiving address based on the channel identifier and the preset receiving address prefix, and configure the callback receiving address to the third-party platform.

[0027] Optionally, the method further comprises the following steps:

[0028] Based on the callback receiving address, in response to the callback request of the third-party platform, the response service data in the link is extracted according to the preset callback response configuration to obtain a callback response body, and the callback response body is returned to the third-party platform.

[0029] On the other hand, an embodiment of the present invention provides a configurable interface docking and parsing device, including:

[0030] The first module is used to obtain the interface document of the third-party platform, and to obtain configuration information according to the interface document combined with the preset configuration items; the configuration information is associated with the channel identifier of the third-party platform and stored in a preset database; the configuration information includes the service address, request format, request configuration and request response configuration of the third-party platform;

[0031] The second module is used to obtain configuration information from a preset database in response to a service request for a third-party platform; the service request carries a channel identifier and requested service data;

[0032] The third module is used to assemble the request body based on the request configuration and the request business data, and send the request body to the third-party platform according to the service address and request format;

[0033] The fourth module is used to extract the response business data obtained by the third-party platform in response to the request body based on the request response configuration.

[0034] Optionally, the device further comprises:

[0035] The fifth module is used to generate a callback receiving address according to the channel identifier and a preset receiving address prefix, and configure the callback receiving address to the third-party platform.

[0036] Furthermore, the device also includes:

[0037] The sixth module is used to respond to the callback request of the third-party platform based on the callback receiving address, extract the response business data in the link according to the preset callback response configuration to obtain the callback response body, and return the callback response body to the third-party platform.

[0038] On the other hand, an embodiment of the present invention provides an electronic device, including: a processor and a memory; the memory is used to store programs; the processor executes the program to implement the above-mentioned configured interface docking and parsing method.

[0039] On the other hand, an embodiment of the present invention provides a computer storage medium, in which a program executable by a processor is stored. When the program executable by the processor is executed by the processor, it is used to implement the above-mentioned configurable interface docking and parsing method.

[0040] The embodiment of the present invention obtains the interface document of the third-party platform, and obtains configuration information according to the interface document combined with preset configuration items; the configuration information is associated with the channel identifier of the third-party platform and stored in a preset database; the configuration information includes the service address, request format, request configuration and request response configuration of the third-party platform; in response to a business request for the third-party platform, the configuration information is obtained from the preset database; the business request carries the channel identifier and the requested business data; based on the request configuration combined with the requested business data, a request body is assembled, and the request body is sent to the third-party platform according to the service address and request format; based on the request response configuration, the response business data obtained by the third-party platform in response to the request body is extracted. The present invention proposes a configurable interface docking and parsing solution, which avoids cumbersome development processes through a configurable manner, realizes automatic data extraction through the configuration information corresponding to the third-party platform, completes rapid docking, improves docking efficiency, and reduces the research and development cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.

[0042] Figure 1 A schematic diagram of an implementation environment for configurable interface docking and parsing provided by an embodiment of the present invention;

[0043] Figure 2 A flowchart of a configurable interface docking and parsing method provided by an embodiment of the present invention;

[0044] Figure 3 A schematic diagram of an example of a request configuration provided by an embodiment of the present invention;

[0045] Figure 4 A schematic diagram of an example of a request response configuration provided by an embodiment of the present invention;

[0046] Figure 5 A schematic diagram of the expansion process of step S200 provided in an embodiment of the present invention;

[0047] Figure 6 A schematic diagram of the expansion process of step S300 provided in an embodiment of the present invention;

[0048] Figure 7 A schematic diagram of an example of a callback response configuration provided by an embodiment of the present invention;

[0049] Figure 8 A schematic diagram of an example of an implementation process of a configurable interface docking and parsing method provided in an embodiment of the present invention;

[0050] Fig. 9A schematic diagram of the structure of a configurable interface docking and parsing device provided in an embodiment of the present invention;

[0051] Fig.10 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0053] It should be noted that, although the functional modules are divided in the system schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the system or the order in the flowchart. The terms "first / S100", "second / S200", etc. in the specification, claims and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0054] Reference to "embodiments" in the present invention means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described in the present invention may be combined with other embodiments.

[0055] like Figure 1 FIG. 1 is a schematic diagram of an implementation environment provided by an embodiment of the present invention. Figure 1 The implementation environment includes at least one terminal 102 and a server 101. The terminal 102 and the server 101 can be connected to a network wirelessly or wired to complete data transmission and exchange.

[0056] Server 101 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0057] In addition, the server 101 can also be a node server in the blockchain network. Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm.

[0058] The terminal 102 may be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The terminal 102 and the server 101 may be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiment of the present invention.

[0059] Based on the example Figure 1 In the implementation environment shown, an embodiment of the present invention provides a configurable interface docking and parsing method. The following is explained using the example of the configurable interface docking and parsing method applied in the terminal 102. It can be understood that the configurable interface docking and parsing method can also be applied to the server 101.

[0060] Reference Figure 2 , Figure 2 The flowchart of the method for configuring interface docking and parsing applied to a terminal provided in an embodiment of the present invention, the execution subject of the method for configuring interface docking and parsing can be any of the aforementioned computer devices (including a server or a terminal). Figure 2 , the method comprises the following steps:

[0061] S100, obtaining an interface document of a third-party platform, and obtaining configuration information according to the interface document and preset configuration items;

[0062] The configuration information is associated with the channel identifier of the third-party platform and stored in a preset database; the configuration information includes the service address, request format, request configuration and request response configuration of the third-party platform;

[0063] It should be noted that the interface document includes the interface URL, request header format, request template, dynamic variable set, response type, key mapping fields and success identifier of the third-party platform; in some embodiments, the configuration information is obtained according to the interface document combined with the preset configuration items, which may include the following steps: obtain the service address according to the interface URL configuration; obtain the request format according to the request header format configuration; obtain the request configuration according to the request template and dynamic variable set configuration; obtain the request response configuration according to the response type, key mapping fields and success identifier configuration.

[0064] For example, in some specific implementations, the configuration information can be completed according to the interface document of the third-party platform, the configuration identifier (i.e., the channel identifier) ​​can be set, and saved to the database. The configuration information includes the service address, request format, request body configuration, and request response configuration. Specifically:

[0065] Channel ID: It is used to mark the unique ID of the third-party platform. By configuring this unique ID, all configuration information of the third-party platform can be determined. At the same time, a unique callback receiving address can also be generated based on this ID. The channel ID will be used for explanation in the following sections.

[0066] The configuration information includes: service address, request format, request body configuration, and request response configuration.

[0067] Service address: the interface URL provided by the third-party platform.

[0068] Request format: The request header format specified by the third-party platform.

[0069] Request configuration: request template, dynamic variable collection. Request templates can use variables in the variable list.

[0070] Dynamic variables include variable name, variable calculation method, and variable calculation parameter list.

[0071] Other variables can be nested in the variable calculation parameter list.

[0072] Request response configuration: response type, key mapping fields, success flag.

[0073] Optionally, in some specific application scenarios, the following example illustrates the configuration information by taking the case of connecting to a certain external manufacturer's SMS interface. Configure the configuration information of the third-party platform and set the channel identifier to 211.

[0074] Service address: https:xxx / api;

[0075] Request format: json;

[0076] The request configuration example is as follows Figure 3 As shown below; httpTemp is the request template, params is the variable list, key is the variable name, methodPackage is the variable calculation method, and param is the input parameter required to calculate the variable.

[0077] The request response configuration example is as follows Figure 4 As shown; among which:

[0078] type: request body structure type, which can be json, string, etc.

[0079] statusKey: status field key;

[0080] successCode: interface success status code value;

[0081] errorMsgKey: error description field key;

[0082] msgIdKey: is the custom business field key.

[0083] Automatic extraction of request response data: that is, automatically extract the corresponding value from the returned result according to the configured custom business field key. That is, the value of data.msgId can be obtained through msgIdKey.

[0084] Configuration items can be customized according to business needs. There is no limit on the number and name. The value of the configuration item must be the field key in the response structure, and can support multiple layers of nesting, such as data.code. The value of as many fields as the number of configuration items can be automatically extracted.

[0085] S200, in response to a service request for a third-party platform, obtaining configuration information from a preset database;

[0086] The service request carries a channel identifier and requested service data;

[0087] It should be noted that in some embodiments, Figure 5 As shown, in response to a business request for a third-party platform, obtaining configuration information from a preset database may include the following steps: S201, in response to a business request for a third-party platform, traversing and matching the preset database through the channel identifier carried in the business request; S202, obtaining the configuration information of the third-party platform based on the associated results of the traversal matching.

[0088] Exemplarily, in some specific implementations, the channel identifiers and configuration information of all third-party platforms whose interfaces need to be configured are associated and stored in a preset database, for example in the form of key-value pairs; in the specific variable query process, the key in the preset database is traversed and matched based on its corresponding channel identifier for the business request of a specific third-party platform, and the configuration information stored in the value corresponding to the key of the matching result is extracted.

[0089] S300, assembling a request body based on the request configuration and the request business data, and sending the request body to a third-party platform according to the service address and the request format;

[0090] It should be noted that the request configuration includes a request template and a dynamic variable set of the third-party platform; each dynamic variable in the dynamic variable set includes its corresponding variable name, variable calculation method and variable calculation parameter list; in some embodiments, such as Figure 6As shown, the request body is obtained by assembling the request configuration in combination with the request business data, which may include the following steps: S301, extracting the business parameter values ​​of the business variables based on the request business data; S302, calling the variable calculation method to obtain the dynamic parameter values ​​of the corresponding dynamic variables in the dynamic variable set; S303, filling the business parameter values ​​and dynamic parameter values ​​into the positions of the corresponding business variables and dynamic variables in the request template in turn to obtain the request body.

[0091] For example, in some specific implementations, a business request is first received: the business module carries business data (i.e., request business data) and a channel identifier to trigger the request sending module. Then, the request body is filled: the request module determines the corresponding configuration information according to the channel identifier, and assembles a complete request body according to the request template, dynamic variable set, and business data.

[0092] Optionally, in some specific application scenarios, Figure 3 Taking the request configuration as an example, assembling the request body can be implemented as follows:

[0093] 1. Receive business requests. The business module carries business data and channel identifiers to trigger the request delivery module. By querying the database or persistence tool through the channel identifier, the corresponding complete third-party platform configuration information can be obtained.

[0094] 2. Fill in the request body. Fill in the request configuration httpTemp, where send_mobile, send_content, and channel_userName are business variables or system variables that can be directly obtained from the business system. $timestamp, $sign, and $sendTime are dynamic parameters that need to be obtained by executing the specified algorithm.

[0095] 2.1. $timestamp is obtained by executing the specified division method in the key=$timestamp variable, and the parameter is the currentTimeMillis system time.

[0096] 2.2, $sign is obtained by executing the xxx.MD5.getMD5 method specified by the key=$sign variable, and the parameter is $append. If the parameter is also a variable, the value of $append is calculated first.

[0097] $append executes the specified append method in the variable list to obtain the parameters of channel_userName, $timestamp, and $md5. The $timestamp execution variable is the value of 2.2.1.

[0098] $md5 executes the specified xxx.MD5.getMD5 method in the variable list to obtain the parameter channel_passWord.

[0099] At this point, the $timestamp and $md5 required by $append have actual values, and the value of $sign can be calculated.

[0100] 2.3. $sendTime executes the specified yyyy-MM-dd HH:mm:ss system time with key=$sendTime in the variable list.

[0101] 2.4. Fill httpTemp with the values ​​of business parameters and dynamic variables to form a complete request body.

[0102] S400: Extracting response business data obtained by the third-party platform in response to the request body based on the request response configuration.

[0103] It should be noted that the request response configuration includes a response type, a key mapping field and a success identifier; in some embodiments, extracting the response business data obtained by the third-party platform in response to the request body based on the request response configuration may include the following steps: obtaining the response data output by the third-party platform in response to the request body based on the response type; extracting the result field from the response data based on the key mapping field, and comparing the result field with the success identifier; when the comparison result of the result field and the success identifier is consistent, extracting the business field from the response data as the response business data based on the key mapping field.

[0104] Exemplarily, in some specific implementations, the request is sent to the third-party platform according to the service address and the request format, and the result of the request is determined according to the request response configuration, and the business data (ie, the response business data) is automatically extracted.

[0105] Optionally, in some specific application scenarios, Figure 4 Taking the request response configuration as an example, extracting the response business data can be achieved as follows:

[0106] Based on the complete assembly of httpTemp completed in the previous steps, excluding variables, the system can initiate a request to the third-party platform according to the service address and request format. According to the request response configuration field type, the request response body is converted to json.

[0107] Extract data.code from the received data according to the statusKey field. That is, extract data first and then code.

[0108] Since the value of successCode is 0, the trigger is successful by checking whether the value of data.code is 0.

[0109] Extract the value of the data.msgId field from the returned data according to the custom business field item msgIdKey. The extracted fields are determined by the configuration items, and there is no limit on the number and name. You can extract as many fields as the configuration items. Objects can be nested.

[0110] In some optional implementations, the method may further include the following steps: generating a callback receiving address according to the channel identifier in combination with a preset receiving address prefix, and configuring the callback receiving address to the third-party platform.

[0111] Exemplarily, in some specific implementations, the configuration information may further include a callback receiving address and a callback response configuration; specifically:

[0112] Generate callback receiving address: You can use the system-fixed receiving address prefix (baseUrl) and channel identifier to generate a unique callback address to receive callbacks from third-party platforms.

[0113] Callback response configuration: callback structure type, success flag, field mapping, response writeback structure, response writeback template.

[0114] Optionally, in some specific application scenarios, the callback response configuration example is as follows Figure 7 As shown; among which:

[0115] type: request response structure type, which can be json, string, etc.

[0116] successCode: interface success status code;

[0117] errorMsgKey: error log field key;

[0118] statusKey: status field;

[0119] resType: the structure type of the response callback, which can be json, string, etc.

[0120] successResTemp: the template that responds to the third party when receiving successfully;

[0121] msgIdKey, mobileKey, and receiveTimeKey are custom business field keys.

[0122] Automatic extraction of callback response data: that is, automatically extracting the corresponding value from the return result according to the configured custom business field key (msgIdKey, mobileKey, receiveTimeKey).

[0123] Assume that the entire callback structure is data. Then you can get the desired key business data data.msgId, data.phone, and data.receiveTime through configuration.

[0124] Configuration items can be customized according to business needs. There is no limit on the number and name. The value of the configuration item must be the field key in the response structure, and can support multiple layers of nesting, such as data.code. The value of as many fields as the number of configuration items can be automatically extracted.

[0125] Furthermore, in some optional implementations, the method may also include the following steps: based on the callback receiving address, in response to the callback request of the third-party platform, extracting the response business data in the link according to the preset callback response configuration to obtain a callback response body, and returning the callback response body to the third-party platform.

[0126] For example, in some specific implementations, callbacks, automatic withdrawals, and template responses may also be received through a third-party platform, specifically:

[0127] 1. Receive callback: The system needs to be able to externally callback the address baseUrl+ / {channel identifier}.

[0128] The system needs to be able to receive requests from baseUrl+ / {channel identifier} dynamic addresses and read the channel identifier.

[0129] Determine the corresponding configuration information based on the channel identifier in the callback address.

[0130] 2. Automatic data extraction: parse the callback data according to the callback response configuration in the configuration information, judge the result of the link based on this, and extract the corresponding business data.

[0131] 3. Template response: respond according to the write-back third-party structure and fill in the write-back third-party template.

[0132] Optionally, in some specific application scenarios, the aforementioned example of connecting to an external manufacturer's SMS interface and Figure 7 Taking the callback response configuration as an example, receiving callbacks, automatic data extraction and callback responses can be implemented as follows:

[0133] 1. Receive callback: http: / / xxx / report / 211 is agreed to be the third-party callback address and provided to the third-party platform, where 211 is the channel identifier configured earlier. The corresponding complete callback response configuration can be obtained by querying the database or persistence tool through the channel identifier. The callback is initiated by the third-party platform, and whether a callback is required is determined by the business.

[0134] 2. Automatic withdrawal:

[0135] According to the callback response configuration, the received data is converted into json.

[0136] Extract the status in the received data according to the statusKey field, and determine whether the service is successful by judging whether its value is DELIVRD.

[0137] According to successResTemp, the success or failure response body is returned to the third-party platform.

[0138] Extract the values ​​of errdesc, msgId, phone, and receiveTime fields from the received data according to the configured errorMsgKey, msgIdKey, mobileKey, statusKey, and receiveTimeKey. Therefore, the extracted fields are determined by the previous configuration items, and there is no limit on the number and name. The number of configured items can be automatically extracted. By specifying the callback field to associate or echo the request response field, the result of the entire link can be determined.

[0139] 3. Callback response: Extract the status in the received data according to the statusKey field, and determine whether the service is successful by judging whether its value is DELIVRD. According to the successResTemp in the configuration item, return the successful or failed response body to the third-party platform.

[0140] In order to explain the principle of the technical solution of the present invention in detail, the overall process of the present invention is described below in combination with some specific embodiments. It is easy to understand that the following is an explanation of the technical principle of the present invention and cannot be regarded as a limitation of the present invention.

[0141] First of all, it should be noted that, in view of the increasing number of business scenarios that require the docking of multiple third-party platform interfaces, the traditional docking method requires manual code writing, iteration, testing and online release, which is a large amount of repetitive work and takes a long time. The patent of this invention proposes a method and system for configurable interface docking and parsing. Through a configurable method, it avoids cumbersome open imaging, automatically extracts data, and completes rapid docking. The present invention can avoid cumbersome open processes, improve docking efficiency, and reduce the R&D cycle.

[0142] In some specific application scenarios, the present invention can be Figure 8 The system architecture shown implements a configurable interface docking and parsing method. The system architecture includes three core modules: configuration module, request module, and callback module. The specific implementation steps can be as follows:

[0143] Step 1: Configure third-party platform information:

[0144] Channel ID: It is used to mark the unique ID of the third-party platform. By configuring this unique ID, all configuration information of the third-party platform can be determined. At the same time, a unique callback receiving address can also be generated based on this ID. The channel ID will be used for explanation in the following sections.

[0145] The configuration information includes: service address, request format, request body configuration, request response configuration, and callback response configuration.

[0146] Service address: the interface URL provided by the third-party platform.

[0147] Request format: The request header format specified by the third-party platform.

[0148] Request configuration: request template, dynamic variable collection. Request templates can use variables in the variable list.

[0149] Dynamic variables include variable name, variable calculation method, and variable calculation parameter list.

[0150] Other variables can be nested in the variable calculation parameter list.

[0151] Request response configuration: response type, key mapping fields, success flag.

[0152] Generate callback receiving address: Use the system-fixed receiving address prefix (baseUrl) and channel identifier to generate a unique callback address for receiving callbacks from third-party platforms.

[0153] If a third-party callback service is needed, this callback URL can be provided to the third-party platform, and the third-party platform will trigger the callback. Whether the third-party platform callback is needed depends on the actual situation. Callback address: baseUrl+ / {channel identifier}.

[0154] Callback response configuration: callback structure type, success flag, field mapping, response writeback structure, response writeback template.

[0155] After completing this step of configuration, the connection with the third-party service is completed. After configuring the above information, save all the above information to the database.

[0156] Step 2: Fill in the template, request a call and automatically withdraw the data:

[0157] 2.1. Receiving business request: The business module carries business data and channel identification to trigger the request sending module.

[0158] 2.2. Fill in the request body: The module below the request determines the corresponding configuration information according to the channel identifier, and assembles the complete request body according to the request template, dynamic variable set, and business data.

[0159] 2.3. Request to third-party platform and automatically extract data: Send the request to the third-party platform according to the service address and request format, and judge the result of the request according to the request response configuration to automatically extract business data.

[0160] Step 3: Receive callback, automatic withdrawal and template response:

[0161] 3.1. Receive callback: The system needs to be able to externally callback the address baseUrl+ / {channel identifier}.

[0162] The system needs to be able to receive requests from baseUrl+ / {channel identifier} dynamic addresses and read the channel identifier.

[0163] Determine the corresponding configuration information based on the channel identifier in the callback address.

[0164] 3.2. Automatic data extraction: parse the callback data according to the callback response configuration from the configuration information, and use it to determine the result of the link and extract the corresponding business data

[0165] 3.3. Template response: respond according to the write-back third-party structure and fill in the write-back third-party template.

[0166] After completing the configuration of the above three steps, the configuration information will be persisted. All configuration information of the third-party platform can be determined through the channel identifier later, including service address, request format, request configuration, request response configuration, and callback response configuration.

[0167] The following example uses the SMS interface of an external manufacturer to illustrate the configuration information:

[0168] Step 1: Configure third-party platform information:

[0169] Configure the configuration information of the third-party platform and set the channel ID to 211.

[0170] Service address: https:xxx / api;

[0171] Request format: json;

[0172] The request configuration example is as follows Figure 3 As shown below; httpTemp is the request template, params is the variable list, key is the variable name, methodPackage is the variable calculation method, and param is the input parameter required to calculate the variable.

[0173] The request response configuration example is as follows Figure 4 As shown; type: is the request body structure type, which can be json, string, etc.

[0174] statusKey: status field key

[0175] successCode: Interface success status code value

[0176] errorMsgKey: error description field key

[0177] msgIdKey: is the custom business field key.

[0178] Automatic extraction of request response data: that is, automatically extract the corresponding value from the returned result according to the configured custom business field key. That is, the value of data.msgId can be obtained through msgIdKey.

[0179] Configuration items can be customized according to business needs. There is no limit on the number and name. The value of the configuration item must be the field key in the response structure, and can support multiple layers of nesting, such as data.code. The value of as many fields as the number of configuration items can be automatically extracted.

[0180] The callback response configuration is as follows Figure 7 As shown; type: is the request response structure type, which can be json, string, etc.

[0181] successCode: interface success status code;

[0182] errorMsgKey: error log field key;

[0183] statusKey: status field;

[0184] resType: the structure type of the response callback, which can be json, string, etc.

[0185] successResTemp: the template that responds to the third party when receiving successfully;

[0186] msgIdKey, mobileKey, and receiveTimeKey are custom business field keys.

[0187] Automatic extraction of callback response data: that is, automatically extracting the corresponding value from the return result according to the configured custom business field key (msgIdKey, mobileKey, receiveTimeKey).

[0188] Assume that the entire callback structure is data. Then you can get the desired key business data data.msgId, data.phone, and data.receiveTime through configuration.

[0189] Configuration items can be customized according to business needs. There is no limit on the number and name. The value of the configuration item must be the field key in the response structure, and can support multiple layers of nesting, such as data.code. The value of as many fields as the number of configuration items can be automatically extracted.

[0190] Step 2: Fill in the template, request the call and automatically withdraw the data:

[0191] 2.1. Receiving business requests: The business module carries business data and channel identifiers to trigger the request sending module. The corresponding complete third-party platform configuration information can be obtained by querying the database or persistence tool through the channel identifier.

[0192] 2.2. Fill in the request body: Fill in the request configuration httpTemp, where send_mobile, send_content, and channel_userName are business variables or system variables that can be directly obtained from the business system. $timestamp, $sign, and $sendTime are dynamic parameters that need to be obtained by executing the specified algorithm.

[0193] 2.2.1. $timestamp is obtained by executing the specified division method in the key=$timestamp variable, and the parameter is the currentTimeMillis system time.

[0194] 2.2.2, $sign is obtained by executing the xxx.MD5.getMD5 method specified by the key=$sign variable, and the parameter is $append. If the parameter is also a variable, the value of $append is calculated first.

[0195] $append executes the specified append method in the variable list to obtain the parameters of channel_userName, $timestamp, and $md5. The $timestamp execution variable is the value of 2.2.1.

[0196] $md5 executes the specified xxx.MD5.getMD5 method in the variable list to obtain the parameter channel_passWord.

[0197] At this point, the $timestamp and $md5 required by $append have actual values, and the value of $sign can be calculated.

[0198] 2.2.3. $sendTime executes the specified yyyy-MM-dd HH:mm:ss system time with key=$sendTime in the variable list.

[0199] 2.2.4. Fill httpTemp with the values ​​of business parameters and dynamic variables to form a complete request body.

[0200] 2.3. Request call and automatic withdrawal:

[0201] After the previous step, the complete assembly of httpTemp has been completed, excluding variables. The system can initiate a request to the third-party platform according to the service address and request format. According to the request response configuration field type, the request return body is converted to json.

[0202] Extract data.code from the received data according to the statusKey field. That is, extract data first and then code.

[0203] Since the value of successCode is 0, the trigger is successful by checking whether the value of data.code is 0.

[0204] Extract the value of the data.msgId field from the returned data according to the custom business field item msgIdKey. The extracted fields are determined by the configuration items, and there is no limit on the number and name. You can extract as many fields as the configuration items. Objects can be nested.

[0205] Step 3: Receive callback, automatic withdrawal and callback response:

[0206] 3.1、Receive callback: http: / / xxx / report / 211 is agreed to be the third-party callback address and provided to the third-party platform, where 211 is the channel identifier configured earlier. The corresponding complete callback response configuration can be obtained by querying the database or persistence tool through the channel identifier. The callback is initiated by the third-party platform, and whether a callback is required is determined by the business.

[0207] 3.2、Automatic withdrawal:

[0208] According to the callback response configuration, the received data is converted into json.

[0209] Extract the status in the received data according to the statusKey field, and determine whether the service is successful by judging whether its value is DELIVRD.

[0210] According to successResTemp, the success or failure response body is returned to the third-party platform.

[0211] Extract the values ​​of errdesc, msgId, phone, and receiveTime fields from the received data according to the configured errorMsgKey, msgIdKey, mobileKey, statusKey, and receiveTimeKey. Therefore, the extracted fields are determined by the previous configuration items, and there is no limit on the number and name. The number of configured items can be automatically extracted. By specifying the callback field to associate or echo the request response field, the result of the entire link can be determined.

[0212] 3.3. Callback response: Extract the status in the received data according to the statusKey field, and determine whether the service is successful by judging whether its value is DELIVRD. According to the successResTemp in the configuration item, return the successful or failed response body to the third-party platform.

[0213] In summary, the present invention uses templates and dynamic variables to adapt to the standard protocols of most third-party platforms. It has a wide range of applications. In addition, the present invention does not require code, and is generated through scripts, and the connection is completed when the configuration is completed. It reduces the development cycle, reduces deployment resources, and improves efficiency. At the same time, the present invention can realize automatic data extraction. The corresponding data values ​​can be automatically extracted by customizing the required data lines, and there is no limit on the number and name. As long as there are fields in the response, they can be extracted through configuration, and what is configured will be extracted, and multi-layer nesting can be supported.

[0214] Compared with the prior art, the present invention has at least the following beneficial effects:

[0215] 1. By using configuration request templates and dynamic variables, it can adapt to most scenarios of docking with third-party platforms.

[0216] 2. Configuring request templates can reduce a lot of coding work before docking and reduce most of the workload overall.

[0217] 3. By using dynamic variables, more third-party platform specifications can be met, which has a wider range of adaptability.

[0218] The configurable interface docking provided by the present invention can be widely used in software system development. Through the configurable docking, it can flexibly respond to changes, simplify maintenance, reduce code, improve development efficiency, and enhance the intelligence level of the software system. The following are some main application scenarios:

[0219] 1. Need to integrate multiple third-party service providers' systems. Common enterprise-level application systems, e-commerce platforms, financial technology companies, Internet of Things (IoT) platforms and other software systems need to be integrated into multiple third-party services. Third-party service providers cover a wide range, involving different interface protocols and fields. The configuration-based docking method can adapt to these changes. By adjusting the configuration information of the third-party platform, the integration of new third-party service providers can be completed. The data fields that need to be extracted are not fixed. The data in the response request can be automatically extracted through the interface response configuration, which can greatly improve the efficiency of docking.

[0220] 2. It is necessary to integrate multiple third-party platform interfaces or service systems with similar functions or services. Usually, the extracted fields of such systems also have business similarities. Common payment platforms, social media platforms, e-commerce platforms, etc. need to connect to multiple similar third-party platform systems, which requires a lot of interface connection, data conversion and testing. These platforms may introduce some new third parties every once in a while. The use of configured connection methods can greatly improve the connection efficiency. In addition, due to the similarity of third-party platforms, the data obtained from each third-party platform also has business similarities. Therefore, there may be similarities in request configuration, request response configuration, callback response configuration, etc., which can speed up the connection efficiency. The connection efficiency is improved to the minute or hour level.

[0221] 3. Systems with high requirements for service continuity and reliability. The configuration-based docking method, zero code development, and automatic data collection can improve docking efficiency and reduce R&D cycles. This can greatly improve service continuity and reliability.

[0222] On the other hand, Fig. 9 As shown, the embodiment of the present invention provides a configurable interface docking and parsing device 900, including:

[0223] The first module 901 is used to obtain the interface document of the third-party platform, and to obtain configuration information according to the interface document combined with the preset configuration items; the configuration information is associated with the channel identifier of the third-party platform and stored in a preset database; the configuration information includes the service address, request format, request configuration and request response configuration of the third-party platform;

[0224] The second module 902 is used to obtain configuration information from a preset database in response to a service request for a third-party platform; the service request carries a channel identifier and requested service data;

[0225] The third module 903 is used to assemble a request body based on the request configuration and the request business data, and send the request body to the third-party platform according to the service address and the request format;

[0226] The fourth module 904 is used to extract the response business data obtained by the third-party platform in response to the request body based on the request response configuration.

[0227] In some embodiments, the apparatus may further include:

[0228] The fifth module is used to generate a callback receiving address according to the channel identifier and a preset receiving address prefix, and configure the callback receiving address to the third-party platform.

[0229] Furthermore, the device may also include:

[0230] The sixth module is used to respond to the callback request of the third-party platform based on the callback receiving address, extract the response business data in the link according to the preset callback response configuration to obtain the callback response body, and return the callback response body to the third-party platform.

[0231] The contents of the method embodiments of the present invention are all applicable to the device embodiments. The functions specifically implemented by the device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0232] On the other hand, an embodiment of the present invention further provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above sensitive information method when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a car computer, etc.

[0233] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0234] like Fig.10 As shown, Fig.10 A specific example of the hardware structure of an electronic device 1000 according to an embodiment is shown. The electronic device 1000 includes:

[0235] The processor 1001 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present invention.

[0236] The memory 1002 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 1002, and the processor 1001 calls and executes the network node population optimization method of the embodiment of the present invention;

[0237] Input / output interface 1003, used to implement information input and output;

[0238] The communication interface 1004 is used to realize the communication interaction between the device and other devices. The communication can be realized through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0239] A bus 1005 , which transmits information between various components of the device (e.g., the processor 1001 , the memory 1002 , the input / output interface 1003 , and the communication interface 1004 );

[0240] The processor 1001 , the memory 1002 , the input / output interface 1003 and the communication interface 1004 are connected to each other in communication within the device via the bus 1005 .

[0241] The electronic device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0242] The contents of the method embodiments of the present invention are all applicable to the electronic device embodiments. The functions specifically implemented by the electronic device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0243] Another aspect of an embodiment of the present invention further provides a computer-readable storage medium, wherein the storage medium stores a program, and the program is executed by a processor to implement the above method.

[0244] It should be noted that the computer-readable medium shown in the embodiment of the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (Compact Disc Read to Only Memory, CD to ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0245] The contents of the method embodiments of the present invention are all applicable to the computer-readable storage medium embodiments. The functions specifically implemented by the computer-readable storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0246] The embodiment of the present invention also discloses a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device can read the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the above method.

[0247] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0248] It should be noted that, although several modules of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to an embodiment of the present invention, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0249] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD to ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation of the present invention.

[0250] In some selectable embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the boxes can sometimes be executed in reverse order. In addition, the embodiment presented and described in the flow chart of the present invention is provided by way of example, for the purpose of providing a more comprehensive understanding of the technology. The disclosed method is not limited to the operation and logic flow presented by the present invention. Selectable embodiments are expected, wherein the order of various operations is changed and the sub-operation of a part described as a larger operation is performed independently.

[0251] In addition, although the present invention is described in the context of functional modules, it should be understood that, unless otherwise specified, one or more of the functions and / or features can be integrated into a single physical device and / or software module, or one or more functions and / or features can be implemented in separate physical devices or software modules. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the present invention. More specifically, in view of the properties, functions and internal relationships of various functional modules in the device disclosed in the present invention, the actual implementation of the module will be understood within the conventional skills of engineers. Therefore, those skilled in the art can implement the present invention set forth in the claims without excessive experimentation using ordinary techniques. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0252] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0253] The logic and / or steps represented in the flowchart or otherwise described herein, for example, may be considered as an ordered list of executable instructions for implementing logical functions, and may be embodied in any computer-readable medium for use by an instruction execution device, apparatus or device (such as a computer-based device, a device including a processor, or other device that can fetch instructions from an instruction execution device, apparatus or device and execute the instructions), or in conjunction with such instruction execution device, apparatus or device. For purposes of this specification, "computer-readable medium" may be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution device, apparatus or device, or in conjunction with such instruction execution device, apparatus or device.

[0254] More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be a paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or, if necessary, processing in another suitable manner, and then stored in a computer memory.

[0255] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution device. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0256] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0257] Although the embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

[0258] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the embodiments. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A method for configuring interface docking and parsing, characterized in that: The following steps are involved: Obtain an interface document of a third-party platform, and obtain configuration information according to the interface document combined with preset configuration items; the configuration information is associated with a channel identifier of the third-party platform and stored in a preset database; the configuration information includes a service address, request format, request configuration, and request response configuration of the third-party platform; In response to a service request for the third-party platform, obtaining the configuration information from the preset database; The service request carries the channel identifier and requested service data; Assembling a request body based on the request configuration and the request business data, and sending the request body to the third-party platform according to the service address and the request format; Response business data obtained by the third-party platform in response to the request body is extracted based on the request response configuration.

2. The method for configuring interface connection and analysis according to claim 1, characterized in that: The interface document includes the interface URL, request header format, request template, dynamic variable set, response type, key mapping field and success mark of the third-party platform; the configuration information is obtained according to the interface document combined with the preset configuration items, including the following steps: Obtain the service address according to the interface url configuration; Obtaining the request format according to the request header format configuration; Obtaining the request configuration according to the request template and the dynamic variable set configuration; The request response configuration is obtained according to the response type, the key mapping field and the success identification configuration.

3. The method for configuring interface connection and analysis according to claim 1, characterized in that: The step of obtaining the configuration information from the preset database in response to the service request for the third-party platform comprises the following steps: In response to a service request for the third-party platform, traversing and matching the preset database through the channel identifier carried in the service request; The configuration information of the third-party platform is obtained according to the association result of the traversal matching.

4. The method for configuring interface connection and analysis according to claim 1, characterized in that: The request configuration includes a request template and a dynamic variable set of the third-party platform; each dynamic variable in the dynamic variable set includes its corresponding variable name, variable calculation method and variable calculation parameter list; the request body is obtained by assembling the request configuration in combination with the request business data, including the following steps: Extracting and obtaining a business parameter value of a business variable based on the requested business data; Calling the variable calculation method to obtain the dynamic parameter value corresponding to the dynamic variable in the dynamic variable set; The business parameter value and the dynamic parameter value are sequentially filled into the positions of the corresponding business variables and the dynamic variables in the request template to obtain the request body.

5. The method for configuring interface connection and analysis according to claim 1, characterized in that: The request response configuration includes a response type, a key mapping field, and a success flag; extracting the response business data obtained by the third-party platform in response to the request body based on the request response configuration includes the following steps: Acquire response data output by the third-party platform in response to the request body based on the response type; Extracting a result field from the response data based on the key mapping field, and comparing the result field with the success identifier; When the result field is consistent with the comparison result of the successful identification, a business field is extracted from the response data based on the key mapping field as the response business data.

6. The method for configuring interface connection and analysis according to claim 1, characterized in that: The method further comprises the following steps: A callback receiving address is generated according to the channel identifier and a preset receiving address prefix, and the callback receiving address is configured to the third-party platform.

7. The method for configuring interface connection and analysis according to claim 6, characterized in that: The method further comprises the following steps: Based on the callback receiving address, in response to the callback request of the third-party platform, data is extracted from the response service data in the link according to the preset callback response configuration to obtain a callback response body, and the callback response body is returned to the third-party platform.

8. A configurable interface docking and parsing device, characterized in that: include: The first module is used to obtain the interface document of the third-party platform, and to obtain configuration information according to the interface document combined with the preset configuration items; The configuration information is associated with the channel identifier of the third-party platform and stored in a preset database; the configuration information includes the service address, request format, request configuration and request response configuration of the third-party platform; A second module is used to obtain the configuration information from the preset database in response to a service request for the third-party platform; The service request carries the channel identifier and requested service data; A third module is used to assemble a request body based on the request configuration and the request business data, and send the request body to the third-party platform according to the service address and the request format; The fourth module is used to extract the response business data obtained by the third-party platform in response to the request body based on the request response configuration.

9. An electronic device, characterized in that: including a processor and a memory; The memory is used to store programs; The processor executes the program to implement the method according to any one of claims 1 to 7.

10. A computer storage medium storing a program executable by a processor, characterized in that: The program executable by the processor is used to implement the method according to any one of claims 1 to 7 when executed by the processor.

Images