Interface transparent transmission method, combined transaction transparent transmission system and readable storage medium

Abstract

The application provides an interface transparent transmission method, a combined transaction transparent transmission system and a readable storage medium. The method is applied to the combined transaction transparent transmission system and includes the following steps: receiving an interface transparent transmission request sent by a request end, wherein the interface transparent transmission request at least includes service request data and first interface ID information; obtaining an interface configuration file; determining second interface ID information corresponding to the first interface ID information according to the first interface ID information and the interface configuration file; sending the service request data to a target service response end corresponding to the second interface ID information, receiving service response data sent by the target service response end, and sending the service response data to the request end. The method does not need to modify the original code of the two systems, only needs to add a few parameter conversion configurations in the database of the combined transaction transparent transmission system, can realize interface adaptation for data transmission, has fast delivery speed, can be used in multiple scenes through one-time development, and has high economic benefits.

Description

Technical Field

[0001] This application relates to the field of data transmission, and more specifically, to an interface pass-through method, a combined transaction pass-through system, a computer-readable storage medium, and an electronic device. Background Technology

[0002] Currently, the channel system used for transparent interfaces, based on project architecture design and network deployment considerations, needs to distinguish at least the business layer and the proxy layer. In actual applications, each layer needs to develop corresponding interfaces to realize the complete link of requests between microservices. However, the development content is largely the same, consisting of the control layer, service layer, and SPI call layer, which consumes a lot of time and manpower. Furthermore, each time an interface is released, it needs to be redeployed, which will cause some fluctuations in business.

[0003] In the software development process, when there is interaction between multiple systems, since the interfaces provided by each system are already developed and ready-made, for example, the request parameters of system A cannot be directly used as the request parameters of system B, or the response parameters of system B cannot be directly recognized by system A, adaptation development is often required to establish connectivity.

[0004] Currently, FastJson provides @JSONField to solve the problem of inconsistent request parameters with required parameters. However, this requires modification in the code of the receiving party (i.e., system B mentioned above), which involves various manpower and time costs related to development, testing, and deployment. Summary of the Invention

[0005] The main objective of this application is to provide an interface pass-through method, a combined transaction pass-through system, a computer-readable storage medium, and an electronic device, so as to at least solve the problem of incompatibility between interfaces of various systems in the prior art, which requires modification of interface code and results in excessive costs.

[0006] To achieve the above objectives, according to one aspect of this application, an interface pass-through method is provided, applied to a combined transaction pass-through system. The method includes: receiving an interface pass-through request sent by a requesting end, the interface pass-through request including at least service request data and first interface ID information, the first interface ID information being the ID information of the interface from which the requesting end sent the interface pass-through request; obtaining an interface configuration file, the interface configuration file including at least a mapping relationship between the interface ID information of the requesting end and the interface ID information of a service responding end; determining second interface ID information corresponding to the first interface ID information based on the first interface ID information and the interface configuration file, the second interface ID information being the interface ID information of a target service responding end corresponding to the first interface ID information; sending the service request data to the target service responding end corresponding to the second interface ID information, receiving service response data sent by the target service responding end, and sending the service response data to the requesting end.

[0007] Optionally, an interface configuration file is obtained, including: constructing an interface configuration table, an interface parameter table, an interface routing table, a back-end service table, a back-end system error code mapping table, and a transparent system error code table. The interface configuration table stores the interface ID information of the requesting end and the interface transparent fields of the requesting end. The interface parameter table stores the request parameters of the requesting end and the response parameters of the service responding end. The interface routing table stores the interface call chain. The back-end service table stores the interface configuration parameters of at least one of the service responding ends. The back-end system error code mapping table stores the response codes and response information of at least one of the service responding ends. The transparent system error code table stores... The system combines the response codes and response information of the transaction pass-through system; it constructs the mapping relationships between the interface configuration table and the interface parameter table, the interface configuration table and the interface routing table, the interface routing table and the back-end service table, the back-end service table and the back-end system error code mapping table, and the back-end system error code mapping table and the combined transaction pass-through system error code table; it stores the interface configuration table, the interface parameter table, the interface routing table, the back-end service table, the back-end system error code mapping table, and the pass-through system error code table in the database of the pass-through system to obtain the interface configuration file.

[0008] Optionally, before determining the second interface ID information corresponding to the first interface ID information based on the first interface ID information and the interface configuration file, the method further includes: determining the interface pass-through parameters corresponding to the first interface ID information based on the first interface ID information and the interface configuration file, wherein the interface pass-through parameters are the request parameters of the interface through which the requesting end sends the interface pass-through request, and the interface configuration file also includes the mapping relationship between the interface ID information of the requesting end and the request parameters of the interface of the requesting end; validating the interface pass-through parameters based on the factory method pattern to obtain a validation result, wherein the interface pass-through parameters include at least a first field, a second field, a third field, a fourth field, and a fifth field, wherein the first field indicates whether the target data in the service request data must be input, the second field indicates the enumeration range of the target data, the third field indicates the field length of the target data, the fourth field indicates whether the target data is empty, and the fifth field indicates the regular expression of the target data.

[0009] Optionally, there are multiple target service response terminals. Sending the service request data to the target service response terminal corresponding to the second interface ID information includes: determining the target interface call chain based on the first interface ID information and the interface configuration file. The interface configuration file also includes a mapping relationship between the interface ID information of the request terminal and the interface call chain. The target interface call chain includes multiple nodes, and each node represents a service executed by one of the service response terminals. Based on the connection relationship of the nodes in the target interface call chain, the service request data is sent to each of the service response terminals in a preset order to invoke each of the service response terminals.

[0010] Optionally, if the current node is not the first node, the service request data is sent to each of the service response terminals in a preset order according to the connection relationship of the nodes in the target interface call chain, so as to call each of the service response terminals, including: obtaining the historical call result of the previous node, wherein the historical call result is the call result of a node before the current node, and the historical call result corresponds one-to-one with each node before the current node; if at least one of the historical call results of the previous node satisfies the corresponding first preset condition, the service response terminal corresponding to the current node is called to obtain the call result of the current node, wherein the historical call result corresponds one-to-one with the first preset condition; if at least one of the historical call results satisfies the corresponding second preset condition, and / or if the call result of the current node is a first result, the target service response terminal corresponding to the next node is called, wherein the historical call result corresponds one-to-one with the second preset condition; if at least one of the historical call results does not satisfy the corresponding second preset condition, and / or if the call result of the current node is a second result, the call is terminated.

[0011] Optionally, obtaining the interface configuration file includes: querying data in a first database; if the interface configuration file does not exist in the first database, querying data in a second database and loading the data from the second database into the first database to obtain the interface configuration file.

[0012] Optionally, the method further includes: if the data in the interface configuration file needs to be modified, modifying the data identifier of the configuration center based on the front-end page to modify the data in the interface configuration file.

[0013] According to another aspect of this application, a combined transaction pass-through system is provided, comprising: a receiving unit, configured to receive an interface pass-through request sent by a requesting end, the interface pass-through request including at least service request data and first interface ID information, the first interface ID information being the ID information of the interface from which the requesting end sent the interface pass-through request; an obtaining unit, configured to obtain an interface configuration file, the interface configuration file including at least a mapping relationship between the interface ID information of the requesting end and the interface ID information of a service responding end; a determining unit, configured to determine, based on the first interface ID information and the interface configuration file, second interface ID information corresponding to the first interface ID information, the second interface ID information being the interface ID information of a target service responding end corresponding to the first interface ID information; and a processing unit, configured to send the service request data to the target service responding end corresponding to the second interface ID information, and receive service response data sent by the target service responding end, and send the service response data to the requesting end.

[0014] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform any of the described interface pass-through methods.

[0015] According to another aspect of this application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including methods for performing any of the described interface pass-through methods.

[0016] Applying the technical solution of this application, the above-mentioned interface pass-through method is applied to a combined transaction pass-through system. First, it receives an interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and a first interface ID, where the first interface ID is the ID of the interface from which the requesting end sent the interface pass-through request. Next, it obtains an interface configuration file. Based on the first interface ID and the interface configuration file, it determines a second interface ID corresponding to the first interface ID, where the second interface ID is the interface ID of the target service response end corresponding to the first interface ID. Finally, it sends the service request data to the target service response end corresponding to the second interface ID, receives the service response data sent by the target service response end, and sends the service response data back to the requesting end. This method does not require code modification of the existing systems of both parties. It only requires adding a few parameter conversion configurations to the database of the combined transaction pass-through system to achieve interface adaptation for data transmission. Furthermore, it offers fast delivery, allows for one-time development applicable to multiple scenarios, and is highly cost-effective. It solves the problem of incompatibility between interfaces in existing technologies, which necessitates modification of interface code, leading to excessive costs. Attached Figure Description

[0017] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 A hardware structure block diagram of a mobile terminal for performing an interface pass-through method according to an embodiment of this application is shown.

[0019] Figure 2 A flowchart illustrating an interface pass-through method according to an embodiment of this application is shown.

[0020] Figure 3 A schematic diagram illustrating the principle of an interface pass-through method according to an embodiment of this application is shown.

[0021] Figure 4 A schematic diagram of the structure of an interface configuration file provided according to an embodiment of this application is shown;

[0022] Figure 5 A flowchart illustrating another interface pass-through method provided according to an embodiment of this application is shown;

[0023] Figure 6 A flowchart illustrating yet another interface pass-through method provided according to an embodiment of this application is shown;

[0024] Figure 7 A flowchart illustrating yet another interface pass-through method provided according to an embodiment of this application is shown;

[0025] Figure 8 A schematic diagram of an interface pass-through device provided according to an embodiment of this application is shown.

[0026] The above figures include the following reference numerals:

[0027] 102. Processor; 104. Memory; 106. Transmission device; 108. Input / output device. Detailed Implementation

[0028] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0029] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] As described in the background section, FastJson currently provides @JSONField to resolve inconsistencies between request parameters and required parameters. However, this requires modifications to the receiving code, which involves various human and time costs related to development, testing, and deployment. To address the issue of incompatibility between interfaces of different systems in existing technologies, which necessitates modifications to the interface code and results in excessive costs, embodiments of this application provide an interface pass-through method, a combined transaction pass-through system, a computer-readable storage medium, and an electronic device.

[0032] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0033] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of a mobile terminal using an interface pass-through method according to an embodiment of the present invention. Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0034] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the interface pass-through method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the aforementioned networks may include wireless networks provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0035] This embodiment provides an interface pass-through method that runs on a mobile terminal, computer terminal, or similar computing device. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Also, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0036] Figure 2 This is a flowchart of an interface pass-through method according to an embodiment of this application. For example... Figure 2 As shown, this method is applied to a combined transaction pass-through system, and the method includes the following steps:

[0037] Step S201: Receive the interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and first interface ID information. The first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request.

[0038] Specifically, the requesting end can be an application system, and the interface pass-through request can be an account opening request. However, performing the account opening operation requires calling the corresponding service response end. The request parameters from the requesting end cannot be directly used as the request parameters for the service response end, or the response parameters from the service response end cannot be directly recognized by the requesting end. Therefore, by combining the transaction pass-through system to adapt the interfaces of the requesting end and the service response end, the entire call process can be completed.

[0039] The principle of the interface pass-through method in this embodiment is as follows: Figure 3 As shown, the process first creates a call flow from A (the requesting end) to B (the responding end); then, it configures the conversion rules (Rule) for the parameters of A's request and B's input, or B's response and A's received parameters. An interface call from A to B is initiated, and the conversion rules are retrieved from the database for automatic parameter conversion, completing the entire call flow. These conversion rules include message format conversion and field type conversion. This conversion process is performed within the combined transaction pass-through system.

[0040] Step S202: Obtain the interface configuration file. The interface configuration file shall include at least the mapping relationship between the interface ID information of the requesting end and the interface ID information of the service response end.

[0041] Specifically, the interface data configuration depends on the interface information stored in the database table. Based on Maven's individual JAR package dependencies, it achieves non-intrusive and pluggable functionality, facilitating overall portability and feature migration.

[0042] While existing technologies using FastJson with the @JSONField annotation can solve the conversion of request parameters, they suffer from code intrusion and high costs. Code intrusion requires modification of existing code, which established systems may be reluctant to undertake. Each code modification or addition of intermediate conversion logic involves development, testing, and deployment, incurring significant manpower and time costs. Furthermore, the high costs may lead to missed collaboration opportunities.

[0043] Compared to modifying the code, this implementation uses the @JSONField annotation to perform field conversion. This method does not require code modification in the existing systems of both parties. It only requires adding a few parameter conversion configurations to the database. It is fast to deliver and can be used in multiple scenarios with one development, resulting in high economic benefits.

[0044] Specifically, step S202 includes the following steps:

[0045] Step S2021: Construct an interface configuration table, an interface parameter table, an interface routing table, a back-end service table, a back-end system error code mapping table, and a transparent transmission system error code table. The interface configuration table is used to store the interface ID information of the requesting end and the interface transparent transmission fields of the requesting end. The interface parameter table is used to store the request parameters of the requesting end and the response parameters of the service response end. The interface routing table is used to store the interface call chain. The back-end service table is used to store the interface configuration parameters of at least one of the service response ends. The back-end system error code mapping table is used to store the response code and response information of at least one of the service response ends. The transparent transmission system error code table is used to store the response code and response information of the combined transaction transparent transmission system.

[0046] The specific structure diagrams of the interface configuration table, interface parameter table, interface routing table, back-end service table, back-end system error code mapping table, and transparent transmission system error code table are as follows: Figure 4 As shown.

[0047] The interface configuration table is used to store interface address configurations (including the IP addresses and internet addresses of the sender and receiver). It uses an identifier to determine whether a field is directly passed through. If it is, it means that the complete interface can be passed through directly through the configuration. If it is not, it means that customized development is required. The relevant methods can be overridden for custom configuration. That is, if there are special requirements such as data entry into the database or storage locally, the developers need to develop it themselves.

[0048] The interface parameter table is used to configure the request and response parameters of the interface. Each piece of data sent by the requesting end needs to be validated. The validation conditions are in JSON format, such as {"required":"1","enums":"01,02","length":"0,18","blank":"0","regex":"^[1][3-9]\\d{9}$"}, representing whether it is a required field (i.e., whether it is a necessary transmission field), the range of enumerated values, the field length, and whether it is an empty field, respectively. The factory method design pattern is used to validate different types, facilitating future expansion. JSON format is used because of its strong extensibility; other formats can be used as alternatives in some solutions. The response parameters in the interface parameter table are the data sent to the requesting end after the response data has been encapsulated by the combined transaction transparent transmission system. The corresponding parameters can be recognized by the requesting end, and the response data is sent from the service response end to the combined transaction transparent transmission system.

[0049] The back-end service table stores the interface configuration of the back-end system (i.e., the service response end), including the name of the called microservice, the SPI name in the called microservice, the back-end interface request address, and the interface common request-response mapping. The back-end system is a system providing a dedicated service, and is the only system besides the combined transaction pass-through system that can expose SPI. The combined transaction pass-through system is used for combined transactions, configuration pass-through, and transaction modification.

[0050] The interface routing table stores the entire call chain of the transparent transmission system's interfaces. This call chain includes the order in which multiple service responses are accessed, including serial or parallel access. Each node in the call chain represents a service response or a specific service within a service response to be called. The interface call order is stored through parent and current nodes, and the direction of the interface chain is controlled by admission and termination conditions. The back-end service ID is the primary key in the back-end service table, associated with the specific calling interface. The request and response mapping here is a custom field mapping for that interface.

[0051] The pass-through system error code is used to store the response code and response information of the pass-through system to the outside world.

[0052] The back-end system error code mapping table is used to store the response codes and response information of different back-end systems and map them to the unified error codes of the transparent transmission system. The overall mapping realizes the standardization of external response.

[0053] In the data table above, all request and response mappings are in JSON format.

[0054] The key format is "backline service ID" + "." + "req (request) / resp (response)" + interface field level (multiple levels are separated by "."). For example, "7.req.busiData.mobile" means using the backline interface with backline service ID 7, where the mobile field in {"busiData":{"mobile":"123"}} in the request body is mapped in this way.

[0055] The `value` parameter supports constants, time types, parameter mappings, response code and response information mappings, and conditional statements, and uses a factory method for flexible extension. Time types such as `DATE_FORMAT(NOW, yyyyMMdd)` can generate the current time in a specified date format in real time; parameter mappings such as `user.req.phone` can retrieve the `phone` field value passed from the user's request body, and also support response values ​​from upper-layer interfaces in the interface chain; the response code is `ERR_CODE(7.resp.servRespCd)`, and the response information is `ERR_MSG(7.resp.servRespCd)`, mapped from the back-end system error code mapping table to the pass-through system error code table, implementing a configurable mapping standard; conditional statements such as `SWITCH("6.resp.busiData.code"=="1",10,"6.resp.busiData.code"=="2"&&"7.resp.servRes`... pCd"!="2",20) means that when the code value under the busiData level in the interface response of the back-end system with ID 6 is 1, the value is mapped to 10. In the second case, it is mapped to 20, and then assigned to the key corresponding to the value.

[0056] The admission and termination conditions are also based on the mapping hierarchy for logical judgment. The stored data, such as "6.resp.busiData.code" == "1" && "7.resp.servRespCd" ! = "2", means that if the code value under the busiData level in the response of the interface with the backline system ID 6 is 1 and the servRespCd value in the response of the interface with the backline system ID 7 is not 2, it is true. This is used to determine whether to call the current link node and whether to terminate directly after the current node has been called.

[0057] Step S2022: Construct the mapping relationship between the above interface configuration table and the above interface parameter table, the mapping relationship between the above interface configuration table and the above interface routing table, the mapping relationship between the above interface routing table and the above back-end service table, the mapping relationship between the above back-end service table and the above back-end system error code mapping table, and the mapping relationship between the above back-end system error code mapping table and the above combined transaction transparent transmission system error code table.

[0058] Among them, such as Figure 4As shown, one piece of data in the interface configuration table can correspond to multiple pieces of data in the interface parameter table; one piece of data in the interface configuration table can correspond to multiple pieces of data in the interface routing table; multiple pieces of data in the interface routing table can correspond to one piece of data in the back-end service table; one piece of data in the back-end service table can correspond to multiple pieces of data in the back-end system error code mapping table; and one piece of data in the back-end system error code mapping table can correspond to multiple pieces of data in the transparent transmission system error code table.

[0059] Step S2023: Store the above interface configuration table, the above interface parameter table, the above interface routing table, the above back-end service table, the above back-end system error code mapping table, and the above pass-through system error code table in the database of the above pass-through system to obtain the above interface configuration file.

[0060] Specifically, the above embodiments do not require code modification to the existing systems of both parties. Only a few parameter conversion configurations need to be added to the database, resulting in fast delivery and the ability to be applied to multiple scenarios with a single development effort, leading to high economic efficiency. Rapid configuration enables quick implementation of the pass-through interface. Traditional pass-through interfaces require customized code development, mapping the relevant interfaces of the back-end system to DTOs and the external service's VOs, while simultaneously developing microservice message flow code. Adding and modifying code means a certain development cycle, which is not conducive to the rapid deployment of business requirements. With this technical solution, only the mapping relationship needs to be configured on the page according to the defined structure to quickly implement the pass-through function, greatly shortening the deployment time and manpower investment.

[0061] Prior to step S203, the above method further includes the following steps:

[0062] Step S301: Based on the first interface ID information and the interface configuration file, determine the interface pass-through parameters corresponding to the first interface ID information. The interface pass-through parameters are the request parameters of the interface through which the requesting end sends the interface pass-through request. The interface configuration file also includes the mapping relationship between the interface ID information of the requesting end and the request parameters of the interface of the requesting end.

[0063] Step S302: Validate the above-mentioned interface pass-through parameters based on the factory method pattern to obtain the validation result. The above-mentioned interface pass-through parameters include at least a first field, a second field, a third field, a fourth field, and a fifth field. The first field indicates whether the target data in the above-mentioned service request data must be input. The second field indicates the range of enumerated values ​​of the above-mentioned target data. The third field indicates the field length of the above-mentioned target data. The fourth field indicates whether the above-mentioned target data is empty. The fifth field indicates the regular expression of the above-mentioned target data.

[0064] In practical applications, the parameters passed through the interface are not limited to the first, second, third, fourth, and fifth fields mentioned above; they may also include other fields. Accordingly, validating the interface parameters based on the factory method pattern can directly validate the extended parameter fields.

[0065] Specifically, this way, by simply configuring the mapping relationship on the page according to the defined structure, the pass-through function can be quickly implemented, greatly shortening the production time and manpower input.

[0066] Obtaining the interface configuration file also includes the following steps:

[0067] Step S401: Query data in the first database;

[0068] Step S402: If the interface configuration file does not exist in the first database, query the data in the second database and load the data in the second database into the first database to obtain the interface configuration file.

[0069] The system uses two databases: the first is the Guava caching tool, and the second is a PostgreSQL database. All data is stored in the PostgreSQL database. The first data query is performed from the PostgreSQL database, and the data is then cached in the Guava caching tool. Subsequent queries can then directly retrieve data from the Guava caching tool, speeding up data retrieval. The PostgreSQL database can be replaced; the relational database is primarily used for persistent maintenance of user parameters, backend system configurations, response code configurations, and for synchronizing the cache when it expires. The Guava caching tool can be partially replaced to implement its own local cache functions, such as timeout, size limits, cache loading, and automatic refresh. The specific data query process is as follows: Figure 5 As shown, the system first queries the Guava cache; if the data is not found there, it then queries the PostgreSQL database and loads it into Guava. The Guava cache is configured with a specific cache size and timeout for each response. For high-traffic interfaces, the cache ensures that configuration data is readily available in real-time, while low-traffic interfaces do not consume excessive memory.

[0070] Specifically, a local caching mechanism is introduced to address the low efficiency of reading configuration data from relational databases. During use, reading from the database can be time-consuming; introducing a local caching mechanism significantly reduces program response time and improves pass-through efficiency.

[0071] Step S203: Based on the first interface ID information and the interface configuration file, determine the second interface ID information corresponding to the first interface ID information. The second interface ID information is the interface ID information of the target service response end corresponding to the first interface ID information.

[0072] Specifically, by simply configuring the mapping relationship on the page according to the defined structure, the pass-through function can be quickly implemented, greatly reducing the time required for production and the investment of manpower.

[0073] Step S204: Send the service request data to the target service response end corresponding to the second interface ID information, receive the service response data sent by the target service response end, and send the service response data to the request end.

[0074] Specifically, no code modification is required in the existing systems of both parties. Only a few parameter conversion configurations need to be added to the database. The delivery speed is fast, and the development can be applied to multiple scenarios once, resulting in high economic benefits.

[0075] There are multiple target service response endpoints mentioned above. Sending the service request data to the target service response endpoint corresponding to the second interface ID information includes the following steps:

[0076] Step S501: Based on the first interface ID information and the interface configuration file, determine the target interface call chain. The interface configuration file also includes the mapping relationship between the interface ID information of the requesting end and the interface call chain. The target interface call chain includes multiple nodes, and each node represents a service executed by the service response end.

[0077] Step S502: Based on the connection relationship of the nodes of the target interface call link, the service request data is sent to each of the service response terminals in a preset order to call each of the service response terminals.

[0078] The preset order includes: the aforementioned service response terminals calling each other serially or in parallel in a certain order, or several service response terminals calling each other serially and the other several service response terminals calling each other in parallel. The specific calling order is related to the actual application, that is, the calling order of each service response terminal is not fixed and can be flexibly called.

[0079] Specifically, this allows for flexible configuration and reserves extension points to meet diverse pass-through needs. Compared to traditional single-layer routing pass-through, it is not limited to single-layer pass-through. Routing configuration is added to the process, and pass-through links are flexibly configured based on admission and exit conditions to meet most practical needs. Extension points are also reserved for customized service calls, allowing customization through rewriting some methods, greatly simplifying code development. Furthermore, compared to low-code platforms, which focus on modularizing and atomicating business processes by maintaining template configurations, and combining them in a certain order, the low-code platform controls the process through templates and configurations for routing configuration, making template configurations more flexible, efficient, and better suited to actual business needs. Where the current node is not the first node, the specific implementation steps of step S402 above are as follows:

[0080] Step S5021: Obtain the historical call result of the previous node. The historical call result is the call result of a node before the current node. The historical call result corresponds one-to-one with each node before the current node.

[0081] Step S5022: If at least one of the above-mentioned previous node's historical call results satisfies the corresponding first preset condition, call the above-mentioned service response terminal corresponding to the current node to obtain the current node's call result. The above-mentioned historical call results correspond one-to-one with the above-mentioned first preset condition.

[0082] Step S5023: If at least one of the above-mentioned historical call results satisfies the corresponding second preset condition, and / or the call result of the current node is the first result, continue to call the target service response terminal corresponding to the next node. The above-mentioned historical call results correspond one-to-one with the above-mentioned second preset conditions.

[0083] Step S5024: If at least one of the above-mentioned historical call results does not meet the corresponding second preset condition, and / or the call result of the current node is the second result, the call ends.

[0084] Specifically, based on the call result of the previous node, the admission conditions for the current node are determined, and based on the call result of the current node, the termination conditions for the process are determined. Both admission and termination conditions are based on logical judgments at the mapping level. Stored data such as "6.resp.busiData.code" == "1" && "7.resp.servRespCd" ! = "2" indicates that if the code value at the busiData level in the response of the interface with backline system ID 6 is 1 and the servRespCd value in the response of the interface with backline system ID 7 is not 2, this is considered true. This is used to determine whether to call the current link node and whether to terminate directly after the current node's call is completed. This allows for more accurate and faster process invocation.

[0085] The above method also includes: when the data in the above interface configuration file needs to be modified, modifying the data identifier in the configuration center based on the front-end page to modify the data in the above interface configuration file.

[0086] The front-end page can be an H5 page, such as... Figure 6 As shown, a solution for the entire configurable transparent interface was implemented through interface data configuration and logical flow links. Considering the complexity of interface configuration and the high availability of configuration content, H5 page configuration was used to improve configuration convenience. Given the inability of Guava single-instance caching to synchronize, Apollo configuration was used to handle cache synchronization issues. When interface configuration data is modified, the identifier in Apollo is modified. When retrieving configuration data, the identifier (or listener) determines whether to retrieve the Guava cache or query the database and then reload the cache, ensuring real-time updates of configuration data.

[0087] Specifically, by using a "template + configuration" approach, leveraging a database and local cache as parameter pools, the H5 page dynamically configures these parameter pools, enabling rapid message mapping and transmission between upstream and downstream systems. This significantly reduces code development and allows for quick implementation of requirements.

[0088] The interface pass-through method described in this application is applied to a combined transaction pass-through system. First, it receives an interface pass-through request from the requesting end. The interface pass-through request includes at least service request data and a first interface ID, which is the ID of the interface from which the requesting end sent the pass-through request. Next, it obtains an interface configuration file. Based on the first interface ID and the interface configuration file, it determines a second interface ID corresponding to the first interface ID, which is the interface ID of the target service response end corresponding to the first interface ID. Finally, it sends the service request data to the target service response end corresponding to the second interface ID, receives the service response data sent by the target service response end, and sends the service response data back to the requesting end. This method does not require code modification to the existing systems of both parties. It only requires adding a few parameter conversion configurations to the database of the combined transaction pass-through system to achieve interface adaptation for data transmission. Furthermore, it offers fast delivery, allows for application across multiple scenarios with a single development effort, and is highly cost-effective. It solves the problem of incompatibility between interfaces in existing technologies, which necessitates modifications to interface code, leading to excessive costs.

[0089] To enable those skilled in the art to better understand the technical solution of this application, the implementation process of the interface pass-through method of this application will be described in detail below with reference to specific embodiments.

[0090] This embodiment relates to a specific interface pass-through method, such as... Figure 7 As shown, it includes the following steps:

[0091] Step S1: After the user's request is decrypted and verified, it enters the business layer;

[0092] Step S2: Query the interface configuration based on the unique interface ID;

[0093] Step S3: Perform validation on the interface parameter configuration, including whether the parameters are required, their length, the enumeration range, and regular expression matching.

[0094] Step S4: After successful verification, add the user request as a map to the parameter pool;

[0095] Step S5: After the verification is successful, check whether the interface directly transmits the data. If not, you need to load custom development content to supplement the parameters and add them to the parameter pool.

[0096] Step S6: Load the complete interface route;

[0097] Step S7: Query the child nodes of the current node. If it is the first child node, then the current parent node is 0.

[0098] Step S8: Determine whether the admission conditions are met by combining the parameter pool;

[0099] Step S9: If the conditions are met, use the parameter pool and request mapping to construct a JSON request message to be sent to the back-end system and initiate the request;

[0100] Step S10: After receiving the backline response message, add the response fields to the parameter pool;

[0101] Step S11: Determine whether the termination condition is met by combining the parameter pool;

[0102] Step S12: If the termination condition is met, the process ends directly. The parameter pool is used for response mapping, and a response message is constructed for the user. Then, the process jumps to step S14.

[0103] Step S13: If the termination condition is not met, query the child node links based on the current node and repeat steps S8 to S13.

[0104] Step S14: The message is encrypted, signed, and returned to the user.

[0105] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0106] This application also provides a combined transaction pass-through system. It should be noted that the combined transaction pass-through system of this application can be used to execute the interface pass-through method provided in this application. This combined transaction pass-through system is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0107] The following describes the combined transaction pass-through system provided in the embodiments of this application.

[0108] Figure 8 This is a schematic diagram of a combined transaction pass-through system according to an embodiment of this application. Figure 8 As shown, the combined transaction pass-through system includes a receiving unit 10, an acquisition unit 20, a determining unit 30, and a processing unit 40. The receiving unit 10 is used to receive an interface pass-through request sent by a requesting end. The interface pass-through request includes at least service request data and first interface ID information, where the first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request. The acquisition unit 20 is used to acquire an interface configuration file, which includes at least a mapping relationship between the interface ID information of the requesting end and the interface ID information of the service responding end. The determining unit 30 is used to determine a second interface ID information corresponding to the first interface ID information based on the first interface ID information and the interface configuration file. The second interface ID information is the interface ID information of the target service responding end corresponding to the first interface ID information. The processing unit 40 is used to send the service request data to the target service responding end corresponding to the second interface ID information, receive the service response data sent by the target service responding end, and send the service response data to the requesting end.

[0109] The combined transaction pass-through system of this application includes a receiving unit, an acquiring unit, a determining unit, and a processing unit. The receiving unit is used to receive an interface pass-through request sent by a requesting end. The interface pass-through request includes at least service request data and first interface ID information, where the first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request. The acquiring unit is used to acquire an interface configuration file, where the interface configuration file includes at least a mapping relationship between the interface ID information of the requesting end and the interface ID information of the service responding end. The determining unit is used to determine, based on the first interface ID information and the interface configuration file, a second interface ID information corresponding to the first interface ID information, where the second interface ID information is the interface ID information of the target service responding end corresponding to the first interface ID information. The processing unit is used to send the service request data to the target service responding end corresponding to the second interface ID information, receive service response data sent by the target service responding end, and send the service response data to the requesting end. This combined transaction transparent transmission system does not require code modification of the existing systems of both parties. It only requires adding a few parameter conversion configurations to the database of the combined transaction transparent transmission system to achieve interface adaptation for data transmission. Moreover, it has a fast delivery speed, can be used in multiple scenarios with one development, and has high economic benefits. It solves the problem of incompatibility between interfaces of various systems in the existing technology, which requires modification of interface code and leads to excessive costs.

[0110] In one optional scheme, the acquisition unit includes a first construction module, a second construction module, and a storage module. The first construction module is used to construct an interface configuration table, an interface parameter table, an interface routing table, a back-end service table, a back-end system error code mapping table, and a transparent system error code table. The interface configuration table stores the interface ID information of the requesting end and the interface transparent fields of the requesting end. The interface parameter table stores the request parameters of the requesting end and the response parameters of the service responding end. The interface routing table stores the interface call chain. The back-end service table stores the interface configuration parameters of at least one of the service responding ends. The back-end system error code mapping table stores the response code and response information of at least one of the service responding ends. The transparent system error code mapping table stores the interface configuration parameters of at least one of the service responding ends. The code table stores the response codes and response information of the combined transaction pass-through system. The second construction module constructs the mapping relationships between the interface configuration table and the interface parameter table, the interface configuration table and the interface routing table, the interface routing table and the back-end service table, the back-end service table and the back-end system error code mapping table, and the back-end system error code mapping table and the combined transaction pass-through system error code table. The storage module stores the interface configuration table, interface parameter table, interface routing table, back-end service table, back-end system error code mapping table, and pass-through system error code table in the database of the pass-through system, obtaining the interface configuration file. This approach eliminates the need for code modification in the existing systems of both parties; only a few parameter conversion configurations need to be added to the database. Delivery is fast, and a single development effort can be applied to multiple scenarios, resulting in high economic efficiency. Rapid configuration enables quick implementation of the pass-through interface.

[0111] In some optional solutions, the above-mentioned device further includes a first determining module and a verification module. The first determining module is used to determine the interface pass-through parameters corresponding to the first interface ID information based on the first interface ID information and the interface configuration file before determining the second interface ID information corresponding to the first interface ID information based on the first interface ID information and the interface configuration file. The interface pass-through parameters are the request parameters of the interface through which the requesting end sends the interface pass-through request. The interface configuration file also includes the mapping relationship between the interface ID information of the requesting end and the request parameters of the interface of the requesting end. The verification module is used to verify the interface pass-through parameters based on the factory method pattern and obtain the verification result. The interface pass-through parameters include at least a first field, a second field, a third field, a fourth field, and a fifth field. The first field indicates whether the target data in the service request data must be input. The second field indicates the range of enumerated values ​​of the target data. The third field indicates the field length of the target data. The fourth field indicates whether the target data is empty. The fifth field indicates the regular expression of the target data. This way, by simply configuring the mapping relationship on the page according to the defined structure, the pass-through function can be implemented quickly, greatly reducing the time required for production and the investment of manpower.

[0112] In some optional solutions, there are multiple target service response terminals. The processing unit includes a second determining module and a first processing module. The second determining module is used to determine the target interface call chain based on the first interface ID information and the interface configuration file. The interface configuration file also includes the mapping relationship between the interface ID information of the requesting terminal and the interface call chain. The target interface call chain includes multiple nodes, and each node represents a service executed by one of the service response terminals. The first processing module is used to send the service request data to each of the service response terminals in a preset order according to the connection relationship of the nodes in the target interface call chain, so as to invoke each of the service response terminals. This allows for flexible configuration, reserves expansion points, and meets diverse pass-through requirements. Compared with traditional single-layer routing pass-through, it is not limited to single-layer pass-through. By adding routing configuration to the process, the pass-through chain can be flexibly configured according to admission and exit conditions to meet most practical needs.

[0113] In this embodiment, the current node is not the first node. The first processing module includes an acquisition submodule, a first theft submodule, a second invocation submodule, and a processing submodule. The acquisition submodule is used to acquire the historical invocation results of the previous node. The historical invocation results are the invocation results of a node before the current node, and each historical invocation result corresponds one-to-one with each node before the current node. The first invocation submodule is used to invoke the service response terminal corresponding to the current node to obtain the invocation result of the current node when at least one of the historical invocation results of the previous node meets the corresponding first preset condition. The historical invocation results correspond one-to-one with the first preset condition. The second invocation submodule is used to continue invoking the target service response terminal corresponding to the next node when at least one of the historical invocation results meets the corresponding second preset condition, and / or when the invocation result of the current node is the first result. The historical invocation results correspond one-to-one with the second preset condition. The processing submodule is used to terminate the invocation when at least one of the historical invocation results does not meet the corresponding second preset condition, and / or when the invocation result of the current node is the second result. This allows for a more accurate and faster invocation process.

[0114] An optional scheme includes a first query module and a second query module in the acquisition unit. The first query module queries data in a first database; the second query module queries data in a second database if the interface configuration file is not present in the first database, and loads the data from the second database into the first database to obtain the interface configuration file. A local caching mechanism is introduced to address the low efficiency of reading configuration files from relational databases. During use, reading the database results in long processing times; introducing a local caching mechanism significantly reduces program response time and improves pass-through efficiency.

[0115] As an optional solution, the aforementioned device also includes a modification module. This module is used to modify the data identifier in the configuration center based on the front-end page when the data in the interface configuration file needs to be modified, thereby altering the data in the interface configuration file. Through a "template + configuration" approach, utilizing a database and local cache as parameter pools, the H5 page dynamically configures the parameter pool, enabling rapid message mapping and transmission between the upstream and downstream systems. This significantly reduces code development and allows for rapid implementation of requirements.

[0116] The aforementioned interface transparent transmission device includes a processor and a memory. The aforementioned receiving units, etc., are all stored as program units in the memory, and the processor executes these program units stored in the memory to achieve the corresponding functions. All of the aforementioned modules are located in the same processor; alternatively, the aforementioned modules may be located in different processors in any combination.

[0117] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured. Adjusting kernel parameters can resolve incompatibility issues between systems in existing technologies, which require modifications to the interface code and result in excessive costs.

[0118] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0119] This invention provides a computer-readable storage medium including a stored program, wherein the program, when running, controls the device containing the computer-readable storage medium to execute the interface pass-through method.

[0120] Specifically, the interface pass-through method includes:

[0121] Step S201: Receive the interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and first interface ID information. The first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request.

[0122] Specifically, the requesting end can be an application system, and the interface pass-through request can be an account opening request. However, performing the account opening operation requires calling the corresponding service response end. The request parameters from the requesting end cannot be directly used as the request parameters for the service response end, or the response parameters from the service response end cannot be directly recognized by the requesting end. Therefore, by combining the transaction pass-through system to adapt the interfaces of the requesting end and the service response end, the entire call process can be completed.

[0123] Step S202: Obtain the interface configuration file. The interface configuration file shall include at least the mapping relationship between the interface ID information of the requesting end and the interface ID information of the service response end.

[0124] Specifically, the interface data configuration depends on the interface information stored in the database table. Based on Maven's individual JAR package dependencies, it achieves non-intrusive and pluggable functionality, facilitating overall portability and feature migration.

[0125] Step S203: Based on the first interface ID information and the interface configuration file, determine the second interface ID information corresponding to the first interface ID information. The second interface ID information is the interface ID information of the target service response end corresponding to the first interface ID information.

[0126] Specifically, by simply configuring the mapping relationship on the page according to the defined structure, the pass-through function can be quickly implemented, greatly reducing the time required for production and the investment of manpower.

[0127] Step S204: Send the service request data to the target service response end corresponding to the second interface ID information, receive the service response data sent by the target service response end, and send the service response data to the request end.

[0128] Specifically, no code modification is required in the existing systems of both parties. Only a few parameter conversion configurations need to be added to the database. The delivery speed is fast, and the development can be applied to multiple scenarios once, resulting in high economic benefits.

[0129] This invention provides a processor for running a program, wherein the program executes the interface pass-through method during runtime.

[0130] Specifically, the interface pass-through method includes:

[0131] Step S201: Receive the interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and first interface ID information. The first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request.

[0132] Specifically, the requesting end can be an application system, and the interface pass-through request can be an account opening request. However, performing the account opening operation requires calling the corresponding service response end. The request parameters from the requesting end cannot be directly used as the request parameters for the service response end, or the response parameters from the service response end cannot be directly recognized by the requesting end. Therefore, by combining the transaction pass-through system to adapt the interfaces of the requesting end and the service response end, the entire call process can be completed.

[0133] Step S202: Obtain the interface configuration file. The interface configuration file shall include at least the mapping relationship between the interface ID information of the requesting end and the interface ID information of the service response end.

[0134] Specifically, the interface data configuration depends on the interface information stored in the database table. Based on Maven's individual JAR package dependencies, it achieves non-intrusive and pluggable functionality, facilitating overall portability and feature migration.

[0135] Step S203: Based on the first interface ID information and the interface configuration file, determine the second interface ID information corresponding to the first interface ID information. The second interface ID information is the interface ID information of the target service response end corresponding to the first interface ID information.

[0136] Specifically, by simply configuring the mapping relationship on the page according to the defined structure, the pass-through function can be quickly implemented, greatly reducing the time required for production and the investment of manpower.

[0137] Step S204: Send the service request data to the target service response end corresponding to the second interface ID information, receive the service response data sent by the target service response end, and send the service response data to the request end.

[0138] Specifically, no code modification is required in the existing systems of both parties. Only a few parameter conversion configurations need to be added to the database. The delivery speed is fast, and the development can be applied to multiple scenarios once, resulting in high economic benefits.

[0139] This invention provides a device including a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs at least the following steps:

[0140] Step S201: Receive the interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and first interface ID information. The first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request.

[0141] Step S202: Obtain the interface configuration file. The interface configuration file shall include at least the mapping relationship between the interface ID information of the requesting end and the interface ID information of the service response end.

[0142] Step S203: Based on the first interface ID information and the interface configuration file, determine the second interface ID information corresponding to the first interface ID information. The second interface ID information is the interface ID information of the target service response end corresponding to the first interface ID information.

[0143] Step S204: Send the service request data to the target service response end corresponding to the second interface ID information, receive the service response data sent by the target service response end, and send the service response data to the request end.

[0144] The devices mentioned in this article can be servers, PCs, tablets, mobile phones, etc.

[0145] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having at least the following method steps:

[0146] Step S201: Receive the interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and first interface ID information. The first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request.

[0147] Step S202: Obtain the interface configuration file. The interface configuration file shall include at least the mapping relationship between the interface ID information of the requesting end and the interface ID information of the service response end.

[0148] Step S203: Based on the first interface ID information and the interface configuration file, determine the second interface ID information corresponding to the first interface ID information. The second interface ID information is the interface ID information of the target service response end corresponding to the first interface ID information.

[0149] Step S204: Send the service request data to the target service response end corresponding to the second interface ID information, receive the service response data sent by the target service response end, and send the service response data to the request end.

[0150] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0151] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0152] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0153] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0154] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0155] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0156] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0157] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0158] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0159] As can be seen from the above description, the embodiments of this application achieve the following technical effects:

[0160] 1) The interface pass-through method described in this application, applied to a combined transaction pass-through system, firstly receives an interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and a first interface ID, where the first interface ID is the ID of the interface from which the requesting end sent the pass-through request. Next, it obtains an interface configuration file. Based on the first interface ID and the interface configuration file, it determines a second interface ID corresponding to the first interface ID, where the second interface ID is the interface ID of the target service response end corresponding to the first interface ID. Finally, it sends the service request data to the target service response end corresponding to the second interface ID, receives the service response data sent by the target service response end, and sends the service response data back to the requesting end. This method does not require code modification of the existing systems of both parties. It only requires adding a few parameter conversion configurations to the database of the combined transaction pass-through system to achieve interface adaptation for data transmission. Furthermore, it offers fast delivery, allows for multi-scenario applicability with a single development, and is highly cost-effective. It solves the problem of incompatibility between interfaces in existing technologies, which necessitates modifications to the interface code, leading to excessive costs.

[0161] 2) The combined transaction pass-through system of this application includes a receiving unit, an acquiring unit, a determining unit, and a processing unit. The receiving unit is used to receive an interface pass-through request sent by a requesting end. The interface pass-through request includes at least service request data and first interface ID information. The first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request. The acquiring unit is used to acquire an interface configuration file. The interface configuration file includes at least a mapping relationship between the interface ID information of the requesting end and the interface ID information of the service responding end. The determining unit is used to determine a second interface ID information corresponding to the first interface ID information based on the first interface ID information and the interface configuration file. The second interface ID information is the interface ID information of the target service responding end corresponding to the first interface ID information. The processing unit is used to send the service request data to the target service responding end corresponding to the second interface ID information, receive the service response data sent by the target service responding end, and send the service response data to the requesting end. This combined transaction transparent transmission system does not require code modification of the existing systems of both parties. It only requires adding a few parameter conversion configurations to the database of the combined transaction transparent transmission system to achieve interface adaptation for data transmission. Moreover, it has a fast delivery speed, can be used in multiple scenarios with one development, and has high economic benefits. It solves the problem of incompatibility between interfaces of various systems in the existing technology, which requires modification of interface code and leads to excessive costs.

[0162] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An interface pass-through method, characterized in that, The method, applied to a combined transaction pass-through system, includes: The interface pass-through request sent by the requesting end is received. The interface pass-through request includes at least service request data and first interface ID information. The first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request. Obtain the interface configuration file, which includes at least the mapping relationship between the interface ID information of the requesting end and the interface ID information of the service response end; Based on the first interface ID information and the interface configuration file, determine the second interface ID information corresponding to the first interface ID information. The second interface ID information is the interface ID information of the target service response end corresponding to the first interface ID information. The service request data is sent to the target service response end corresponding to the second interface ID information, and the service response data sent by the target service response end is received and then sent to the request end. Before determining the second interface ID information corresponding to the first interface ID information based on the first interface ID information and the interface configuration file, the method further includes: Based on the first interface ID information and the interface configuration file, the interface pass-through parameters corresponding to the first interface ID information are determined. The interface pass-through parameters are the request parameters of the interface through which the requesting end sends the interface pass-through request. The interface configuration file also includes the mapping relationship between the interface ID information of the requesting end and the request parameters of the interface of the requesting end. The interface pass-through parameters are validated based on the factory method pattern to obtain the validation result. The interface pass-through parameters include at least a first field, a second field, a third field, a fourth field, and a fifth field. The first field indicates whether the target data in the service request data must be input. The second field indicates the range of enumerated values ​​of the target data. The third field indicates the field length of the target data. The fourth field indicates whether the target data is empty. The fifth field indicates the regular expression of the target data. There are multiple target service response endpoints, and the service request data is sent to the target service response endpoint corresponding to the second interface ID information, including: Based on the first interface ID information and the interface configuration file, the target interface call chain is determined. The interface configuration file also includes the mapping relationship between the interface ID information of the requesting end and the interface call chain. The target interface call chain includes multiple nodes, and each node represents a service executed by the service responding end. Based on the connection relationship of the nodes in the target interface call chain, the service request data is sent to each of the service response terminals in a preset order to invoke each of the service response terminals.

2. The interface transparent transmission method according to claim 1, characterized in that, Obtain the interface configuration file, including: The system constructs an interface configuration table, an interface parameter table, an interface routing table, a back-end service table, a back-end system error code mapping table, and a transparent transmission system error code table. The interface configuration table stores the interface ID information of the requesting end and the interface transparent transmission fields of the requesting end. The interface parameter table stores the request parameters of the requesting end and the response parameters of the service response end. The interface routing table stores the interface call chain. The back-end service table stores the interface configuration parameters of at least one of the service response ends. The back-end system error code mapping table stores the response code and response information of at least one of the service response ends. The transparent transmission system error code table stores the response code and response information of the combined transaction transparent transmission system. Construct the mapping relationships between the interface configuration table and the interface parameter table, the interface configuration table and the interface routing table, the interface routing table and the back-end service table, the back-end service table and the back-end system error code mapping table, and the back-end system error code mapping table and the combined transaction transparent transmission system error code table; The interface configuration table, the interface parameter table, the interface routing table, the back-end service table, the back-end system error code mapping table, and the pass-through system error code table are stored in the database of the pass-through system to obtain the interface configuration file.

3. The interface transparent transmission method according to claim 1, characterized in that, If the current node is not the first node, the service request data is sent to each of the service response terminals in a preset order according to the connection relationship of the nodes in the target interface call link, in order to call each of the service response terminals, including: Obtain historical call results, which are the call results of a node before the current node, and the historical call results correspond one-to-one with each node before the current node; If at least one of the historical call results satisfies the corresponding first preset condition, the service response terminal corresponding to the current node is called to obtain the call result of the current node, and the historical call result corresponds one-to-one with the first preset condition; If at least one of the historical call results satisfies the corresponding second preset condition, and / or the call result of the current node is the first result, the target service response terminal corresponding to the next node is called again, and the historical call results correspond one-to-one with the second preset condition; The call ends if at least one of the historical call results does not meet the corresponding second preset condition, and / or if the call result of the current node is the second result.

4. The interface transparent transmission method according to claim 1, characterized in that, Obtain the interface configuration file, including: Query data from the first database; If the interface configuration file does not exist in the first database, the data in the second database is queried and loaded into the first database to obtain the interface configuration file.

5. The interface transparent transmission method according to claim 1, characterized in that, The method further includes: If the data in the interface configuration file needs to be modified, the data identifier in the configuration center is modified based on the front-end page to modify the data in the interface configuration file.

6. A combined transaction transparent transmission system, characterized in that, include: The receiving unit is used to receive an interface pass-through request sent by the requesting end. The interface pass-through request includes at least service request data and first interface ID information, wherein the first interface ID information is the ID information of the interface from which the requesting end sent the interface pass-through request. An acquisition unit is used to acquire an interface configuration file, wherein the interface configuration file includes at least a mapping relationship between the interface ID information of the requesting end and the interface ID information of the service response end. The determining unit is configured to determine, based on the first interface ID information and the interface configuration file, the second interface ID information being the interface ID information of the target service response end corresponding to the first interface ID information; The processing unit is configured to send the service request data to the target service response end corresponding to the second interface ID information, receive the service response data sent by the target service response end, and send the service response data to the request end. The system further includes a first determining module and a verification module. The first determining module is used to determine the interface pass-through parameters corresponding to the first interface ID information based on the first interface ID information and the interface configuration file before determining the second interface ID information corresponding to the first interface ID information based on the first interface ID information and the interface configuration file. The interface pass-through parameters are the request parameters of the interface through which the requesting end sends the interface pass-through request. The interface configuration file also includes the mapping relationship between the interface ID information of the requesting end and the request parameters of the interface of the requesting end. The validation module is used to validate the interface pass-through parameters based on the factory method pattern and obtain the validation result. The interface pass-through parameters include at least a first field, a second field, a third field, a fourth field, and a fifth field. The first field indicates whether the target data in the service request data must be input. The second field indicates the range of enumerated values ​​of the target data. The third field indicates the field length of the target data. The fourth field indicates whether the target data is empty. The fifth field indicates the regular expression of the target data. There are multiple target service response terminals. The processing unit includes a second determining module and a first processing module. The second determining module is used to determine the target interface call chain based on the first interface ID information and the interface configuration file. The interface configuration file also includes the mapping relationship between the interface ID information of the request terminal and the interface call chain. The target interface call chain includes multiple nodes, and each node represents a service executed by one of the service response terminals. The first processing module is used to send the service request data to each of the service response terminals in a preset order according to the connection relationship of the nodes of the target interface call link, so as to call each of the service response terminals.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device containing the computer-readable storage medium to perform the interface pass-through method according to any one of claims 1 to 5.

8. An electronic device, characterized in that, include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including methods for performing the interface pass-through method according to any one of claims 1 to 5.

Images