A configurable channel access system

Abstract

The present invention discloses a configurable channel access system. The system includes a background configuration management system, an acceptance side system and a gateway. The background configuration management system is used to provide page functions for channel parameter configuration, channel transaction summary and error handling. The acceptance side system is used to provide a transaction standard interface for the upstream system. The gateway converts the initial parameters of the channel request into downstream channel request parameters through a core interface according to the channel parameter configuration information provided by the background configuration management system, and sends the downstream channel request parameters to the downstream channel, so that the downstream channel performs transaction operations according to the downstream channel request parameters. The present invention can realize complex parameter conversion of different channels through simple configuration, so that developers only need to be familiar with the configuration process and cooperate with a small amount of code to realize it; reduce coupling between channels, and improve channel stability, operation and maintenance efficiency and security.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a configurable channel access system. Background Art

[0002] As banking business continues to expand, there will be more and more external channels that need to be connected, and the business needs of the channels will increase. There will be urgent channel access needs, which not only requires the bank's payment department to have the ability of agile development, but also a set of easy-to-use channel access processes and the support of a dedicated channel access system. Traditional channel access will generate a lot of repetitive work every time it is added, such as: assembling parameters, encryption, signing, decryption, and signature verification. If the business logic is not well encapsulated, it may also cause high code coupling and worse code maintainability. Each modification or addition will bring great risks and cost investment. In addition, the bank monitoring system also hopes to monitor the business success rate and system success rate of each channel through the interface dimension and channel dimension, so as to achieve the channel automatic switching function and improve the channel stability. Summary of the invention

[0003] The purpose of the present invention is to provide a configurable channel access system in view of the deficiencies in the prior art.

[0004] To achieve the above-mentioned purpose, the present invention provides a configurable channel access system, including a background configuration management system, a receiving side system and a gateway;

[0005] The backend configuration management system is used to provide page functions for channel parameter configuration, channel transaction summary and error handling. When a user adds, deletes or modifies channel parameter configuration information through the backend configuration management system, the backend configuration management system sends the modified or new channel parameter configuration information to the acceptance side system and the gateway for storage;

[0006] The receiving-side system is used to provide a transaction standard interface for the upstream system, so that the upstream system sends the transaction request to the receiving-side system by calling the corresponding transaction standard interface. The receiving-side system executes the standard business processing flow according to the interface called by the upstream system to obtain the initial parameters of the channel request, and finally sends the initial parameters of the channel request to the gateway;

[0007] The gateway converts the initial parameters of the channel request into downstream channel request parameters through the core interface according to the channel parameter configuration information provided by the background configuration management system, and sends the downstream channel request parameters to the downstream channel, so that the downstream channel performs transaction operations according to the downstream channel request parameters. The downstream channel generates return information according to the execution result, and sends the return information to the gateway through the core interface. The gateway maps the return information to the transaction result, and finally returns the transaction result to the upstream system through the acceptance side system.

[0008] Furthermore, the standard transaction interface includes a text message application interface, a contract signing interface, a deposit interface, a withdrawal interface and an account splitting interface.

[0009] Furthermore, the channel parameter configuration includes channel basic information configuration, channel message mapping configuration and channel communication parameter configuration.

[0010] Furthermore, the basic information configuration of the channel includes the channel name, the main process of the channel, the channel signature verification method and the channel encryption and decryption method.

[0011] Furthermore, the channel message mapping configuration includes a channel pre-message mapping configuration, a channel request parameter message mapping configuration and a response message mapping configuration.

[0012] Furthermore, the channel communication parameter configuration includes channel calling interface information configuration, channel timeout information configuration and transaction result mapping information configuration.

[0013] Furthermore, the background configuration management system publishes the added, deleted or modified channel parameter configuration information to the redis event, and the receiving side system and gateway use the redis monitoring function at the same time, and save the modified information back to the memory when they detect the addition, deletion or modification of the channel parameter configuration.

[0014] Beneficial effects: 1. Improve channel access efficiency, shield differences between channels, and realize complex parameter conversion of different channels through simple configuration, so that developers only need to be familiar with the configuration process and use a small amount of code to achieve it;

[0015] 2. Reduce coupling between channels and improve channel stability. Developers no longer need to affect other channels by modifying the services of a certain channel, thus improving the stability of each channel.

[0016] 3. Centralized management of channel configuration. All channel parameter configurations are managed in the background. If there are any changes, such as changes in channel merchants, channel interfaces, etc., you only need to modify the configuration in the background to take effect in real time, which improves the efficiency of channel operation and maintenance;

[0017] The standardization of 4-channel interfaces can not only monitor the business success rate of the standard interface on the acceptance side, but also monitor each channel or each bank at the gateway layer to improve the security of the channel. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a schematic diagram of the workflow of the configurable channel access system according to an embodiment of the present invention;

[0019] Figure 2 It is a flowchart of a method in which the backend configuration management system sends channel parameter configuration information to the acceptance side system and gateway;

[0020] Figure 3 It is a schematic diagram of the core modules of the background configuration management system;

[0021] Figure 4 This is a schematic diagram of the core modules of the acceptance-side system;

[0022] Figure 5 This is a schematic diagram of the core module of the gateway;

[0023] Figure 6 This is a schematic diagram of the channel configuration interface;

[0024] Figure 7 This is a schematic diagram of the interface for configuring channel message mapping through message templates;

[0025] Figure 8 This is a schematic diagram of the channel communication parameter configuration interface. DETAILED DESCRIPTION

[0026] The present invention is further explained below in conjunction with the accompanying drawings and specific embodiments. The embodiments are implemented based on the technical solution of the present invention. It should be understood that these embodiments are only used to illustrate the present invention and are not used to limit the scope of the present invention.

[0027] like Figure 1As shown, the embodiment of the present invention provides a configurable channel access system, which is developed and implemented based on Java, uses the third-party springboot framework at the bottom, uses mysql as the database, and the middleware includes redis, zk, kafka, etc. The access of a channel is mainly divided into the following processes: 1: preliminary business docking, 2: product analysis requirements, 3: product requirements, 4: development of docking channel interface documents; 5: channel code development; 6: channel joint debugging test, 7: channel online and grayscale. The system specifically includes a background configuration management system 1, an acceptance side system 2 and a gateway 3. After the developer has clarified the channel interface document and the relevant parameters provided by the channel, the channel parameter configuration of the background configuration management system 1 and the template configuration of the acceptance side system can complete most of the channel access work, and after completing all configurations, the joint debugging with the channel can be started.

[0028] The backend configuration management system 1 is used to provide page functions for channel parameter configuration, channel transaction summary and error handling. When a user adds, deletes or modifies channel parameter configuration information through the backend configuration management system 1, the backend configuration management system 1 sends the modified or new channel parameter configuration information to the acceptance side system 2 and the gateway 3. For details, please refer to Figure 6 The above channel parameter configuration includes channel basic information configuration, channel message mapping configuration and channel communication parameter configuration. Among them, the channel basic information configuration includes channel name, channel main process, channel signature verification method and channel encryption and decryption method. Channel message mapping configuration includes channel pre-message mapping configuration, channel request parameter message mapping configuration and response message mapping configuration. For details, please refer to Figure 7 The above channel message mapping configuration can be configured through Figure 7 It is configured according to some of the message templates shown in . The channel pre-message mapping configuration mainly maps the upstream system parameters into the values ​​required by the channel, such as amount conversion, time format conversion, card institution code mapping, etc. The channel request parameter message mapping configuration is used to assemble the parameters after verification and pre-mapping into the format required by the channel, such as json, xml, etc. The response message mapping configuration is used to assemble the response message fields returned by the channel into the standard format for the acceptance side to determine whether the transaction is successful. The channel communication parameter configuration is the same as the channel basic information configuration. After the acceptance side system sends the message to the gateway, the configuration information is loaded into the memory and follows the transaction thread until the thread ends. The channel communication parameter configuration information mainly includes the interface information for calling the channel, channel timeout information, transaction result mapping information, etc. For details, please refer to Figure 8 . See Figure 2Preferably, the background configuration management system 1 can publish the added, deleted or modified channel parameter configuration information to the redis event, and the receiving side system 2 and the gateway 3 use the redis monitoring function at the same time, and save the modified information back to the memory when the channel parameter configuration is added, deleted or modified.

[0029] The acceptance side system 2 is used to provide a transaction standard interface for the upstream system 4, so that the upstream system 4 sends the transaction request to the acceptance side system 2 by calling the corresponding transaction standard interface. The acceptance side system 2 executes the standard business processing flow according to the interface called by the upstream system 4 to obtain the initial parameters of the channel request, and finally sends the initial parameters of the channel request to the gateway 3. The above-mentioned transaction standard interface includes SMS application interface, contract interface, deposit interface, withdrawal interface and account splitting interface, etc. Take the contract interface as an example to illustrate the above-mentioned standard business processing flow: first, a simple parameter entry verification is performed, and then the contract relationship verification is performed. After the verification is passed, the request parameters are stored, and then the standard channel request initial parameters are assembled, and finally the standard channel request initial parameters are sent to the gateway 3 for transaction. Gateway 3 converts the initial parameters of the channel request into downstream channel request parameters through the core Handler (decode) interface according to the channel parameter configuration information provided by the background configuration management system 1, and sends the downstream channel request parameters to the downstream channel 5, so that the downstream channel 5 performs the transaction operation according to the downstream channel request parameters. The downstream channel 5 generates return information according to the execution result, and sends the return information to gateway 3 through the core interface. Gateway 3 maps the return information into the transaction result, and finally returns the transaction result to the upstream system 4 through the acceptance side system 2.

[0030] See also Figure 3 , Figure 3 The figure shows the core modules of the background configuration management system 1, where the functions of EnventPublisher are as follows: When the user operates the background configuration management system 1, each time the configuration information is added, deleted or modified, the information will be sent to the common redis through this class, and redis will broadcast the event to the acceptance side system 2 and gateway 3. There are three main types of channel configuration information: MsgMapping (stores the parameter mapping information of channel message conversion); TunnelConfig (stores the configuration information of channel signature verification, encryption and decryption methods, etc.); PipDictView (stores the system dictionary table configuration information).

[0031] See also Figure 4 , Figure 4The core modules of the acceptance side system 2 are shown in the figure, among which the function of ApplyProvider is to provide transaction standard interfaces, including payment, SMS application, contract signing and authentication, etc. TemplateService is a template service interface class, whose function is to provide query routing channel templates, query the template ID according to the payment method + channel number, and then obtain the execution method corresponding to the template through the scenario coding. This service mainly realizes the configuration of channel acceptance and measurement routing. When adding a new channel, you only need to configure the corresponding channel template in the database to implement the routing function through this interface. ReflectHandler is used to implement the specific execution process of channel transactions. For the same transactions in different channels, the overall process is similar. For example, when applying for SMS, SmsApplyClient is the SMS service interface class. The specific process is: 1. Verify input parameters, 2. SMS pre-processing, 3. Flow information storage, 4. Send application, 5. Return results, 6. Modify storage information, 7. Synchronously return upstream results.

[0032] See also Figure 5 , Figure 5 The core modules of the gateway 3 are shown in the figure, among which PipGateWayService is the gateway interface class, which is used to provide the standard interface of the downstream channel 5 for the acceptance side system 2 to call. Commpent is a configuration information component, which is used to store the detailed configuration information of the background configuration management system. Among them, ParamCommpent (parameter mapping component) maps the upstream parameters to the parameters required by the channel, and TunConfigCommpent (channel configuration component) stores the main configuration information of the channel, including the signature verification method, encryption and decryption method, signature verification field and encryption and decryption field. HttpConfigComment (channel communication component) stores the specific configuration information of the channel communication, including the communication address, communication method, key certificate path and other information. Handler is the specific business process of calling the channel. The main business process of channel 5 is as follows: 1. Encrypt the message field, 2. Assemble the message into the format required by the channel, 3. Sign the assembled message, 4. Connect the channel to send a channel request, 5. Channel message parsing, 6. Verify the parsed message, 7. Assemble the return message, 8. Decrypt the encrypted field of the return message, and 9. Return the upstream channel result information. Convert is a message converter, which is also an important extension point for the system to connect to channel 5. It can convert messages in any format, including json format, xml format, and http format, into the results required by channel 5. The conversion method is based on the specific information of different channel configurations.

[0033] The above is only a preferred embodiment of the present invention. It should be noted that for ordinary technicians in this technical field, other parts not specifically described belong to the prior art or common knowledge. Several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered as the protection scope of the present invention.

Claims

1. A configurable channel access system, characterized in that: Including backend configuration management system, acceptance side system and gateway; The backend configuration management system is used to provide page functions for channel parameter configuration, channel transaction summary and error handling. When a user adds, deletes or modifies channel parameter configuration information through the backend configuration management system, the backend configuration management system sends the modified or added channel parameter configuration information to the acceptance side system and the gateway for storage; The receiving-side system is used to provide a transaction standard interface for the upstream system, so that the upstream system sends the transaction request to the receiving-side system by calling the corresponding transaction standard interface. The receiving-side system executes the standard business processing flow according to the interface called by the upstream system to obtain the initial parameters of the channel request, and finally sends the initial parameters of the channel request to the gateway; The gateway converts the initial channel request parameters into downstream channel request parameters through the core interface according to the channel parameter configuration information provided by the background configuration management system, and sends the downstream channel request parameters to the downstream channel, so that the downstream channel performs the transaction operation according to the downstream channel request parameters. The downstream channel generates return information according to the execution result, and sends the return information to the gateway through the core interface. The gateway maps the return information to the transaction result, and finally returns the transaction result to the upstream system through the acceptance side system; The standard transaction interface includes SMS application interface, contract signing interface, deposit interface, withdrawal interface and account splitting interface; The channel parameter configuration includes channel basic information configuration, channel message mapping configuration and channel communication parameter configuration; The basic information configuration of the channel includes the channel name, channel main process, channel signature verification method and channel encryption and decryption method; The channel message mapping configuration includes a channel pre-message mapping configuration, a channel request parameter message mapping configuration and a response message mapping configuration; The channel communication parameter configuration includes the channel calling interface information configuration, channel timeout information configuration and transaction result mapping information configuration; The background configuration management system publishes the added, deleted or modified channel parameter configuration information to the redis event. The receiving side system and the gateway use the redis monitoring function at the same time. When the channel parameter configuration is added, deleted or modified, the modified information is saved back to the memory.

Images