System and method for realizing http interface configuration scheduling based on Redis

Abstract

The invention relates to the technical field of data processing, in particular to a system and method for realizing http interface configuration scheduling based on Redis, and the system comprises a message analysis module, an encryption module, a configuration management module, a front-end configuration module and a technical framework module. The method has the beneficial effects that path matching and mapping of parameters are realized in modes of jsonPath, Snack3, staxon and the like, so that matching of any node of a message structure is realized, and personalized processing of interface configuration is supported; meanwhile, the nullity of the parameters is verified, the types of the parameters are converted, compatibility of a local interface type and a third-party interface type is achieved, and the availability of fields is improved; and symmetric encryption, asymmetric encryption, field encryption and message encryption are supported, encryption configuration is provided for the whole process of the request, and the security of data is ensured. Individual configuration can meet richer service scenes, and modular configuration avoids coupling of internal functions of an interface before the interface, so that the later maintenance efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to a system and method for implementing HTTP interface configuration based on Redis. Background Art

[0002] As system services continue to evolve and business logic increases, interface processing time continues to increase. This increases the volume of interface calls and service pressure. Implementing specific interfaces requires development and rollout, resulting in a lengthy development cycle. The system is planning to build configurable interfaces with scheduling capabilities, enabling simple configuration of interface connections, interface management, and caching of hot data. This effectively improves operational efficiency, simplifies capability rollout, and shortens rollout cycles. Therefore, HTTP interfaces are essential for system configuration and management.

[0003] The patent description for a related technology patent, titled "An Interface Calling Method, Apparatus, Electronic Device, and Storage Medium," states that it primarily includes the following: An interface calling method loads configuration rules and an interface list from a preset configuration library, generating a preset interface file for each interface. The preset interface file is compiled in a preset compilation environment to obtain an interface class corresponding to each interface. An interface call request is received, and the request is responded to by invoking the target interface based on the target interface class to obtain the target data. The interface call comprises a loading unit, a compilation unit, a receiving unit, and a calling unit, respectively responsible for loading the configuration, compiling the interface file, receiving the request, and invoking the interface. Optionally, the method also includes a control module, a generation module, a construction module, and a storage module, responsible for inputting configuration information, generating configuration rules, constructing the interface list, and storing the configuration. The entire method receives external configuration information, including interface identifiers, request types, addresses, and parameters, through a preset configuration interface. Configuration rules and an interface list are then generated based on this configuration information and stored in the preset configuration library. The configuration rules and interface list from the configuration library are loaded, and the interface configuration data is converted into the preset interface file according to the configuration template and preset framework rules. The preset interface file is then loaded into the running compilation environment to compile and generate the interface class. The system configures a unified access address, receives external interface call requests, determines the target interface class based on the target interface identifier, constructs and sends a preset framework request. The preset framework then constructs an interface data acquisition request based on the request and sends it to the target interface provider to retrieve the target data. While this technology simplifies data acquisition development, it still requires separate code development and configuration for each interface, lacking versatility and reusability, and preventing more detailed and comprehensive interface management.

[0004] Another related patent, "Read Timeout Configuration Method, Device, and Electronic Device," mentions configuring the read time of an HTTP interface. This is achieved by intercepting HTTP interface call requests, reading request parameters, sending them to a configuration center, receiving a target read timeout, and generating a new RequestConfig object based on that time. This object replaces the RequestConfig object in the original request and executes the replaced request. The configuration center device then obtains the corresponding target read timeout based on the request parameters and sends the target read timeout to the business service device.

[0005] This patent addresses the timeout issue in existing call processes, thus resolving the issue of limited flexibility in timeout configuration. However, in actual interface use, from a broader application perspective, comprehensive interface management often involves multiple aspects, such as call frequency control, error retry mechanisms, circuit breakers, and performance monitoring. This is necessary to meet other complex interface requirements. Summary of the Invention

[0006] The purpose of the present invention is to provide a system and method for implementing HTTP interface configuration scheduling based on Redis to solve the problems raised in the above background technology.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a configuration-based scheduling system for HTTP interfaces based on Redis, comprising:

[0008] The message parsing module supports parsing messages in both json and xml formats. It implements parameter path matching and mapping through jsonPath, Snack3, and staxon, matches any node in the message structure, and supports parameter nullability verification and type conversion to achieve compatibility between local interface types and third-party interface types.

[0009] The encryption module supports symmetric encryption, asymmetric encryption, field encryption, and message encryption, and provides encryption configuration for the entire request process;

[0010] The configuration management module stores the interface configuration information in the Redis cache, stores the switch information in the secondary cache and persists it in the database. When the interface is called, the cached data is used for request processing.

[0011] Front-end configuration module: Interface developers can personalize the interface through the front-end page, enabling the business system to add and optimize business interface data with low or even no code.

[0012] Technical framework module, the system front-end interface is developed using Angular framework technology, and the back-end application is created using the springboot framework to achieve configurable scheduling of the http interface.

[0013] Preferably, the configuration management module also includes an access channel authority management sub-module, which is used to control interface access to ensure that only authorized users or systems can access the interface through specific channels. It includes an access channel authority management list interface and a new access channel authority interface, wherein: the access channel authority management list interface displays the access channel authority ID, authorized channels, channel authorized interface name and authorization status; the new access channel authority interface is used to configure access channels, system status and access interfaces.

[0014] Preferably, the configuration management module also includes an interface management submodule, which supports the management of access interfaces and transfer interfaces, and includes an interface management list interface and a new access / modify access interface interface interface, wherein: the interface management list interface can query the interface by interface type, interface name, and interface class name and return the interface list, and supports adding / modifying access interfaces and transfer interfaces; interface types are divided into access interfaces and transfer interfaces, the access interface is a local system interface, and the transfer interface is a third-party interface connected to the local interface; the new access / modify access interface interface can configure the interface name, whether it is provided by the system, the interface class name, the interface mode, the channel, the interface path, the interface request mode, the interface status, the interface validity time, the interface call threshold and the message format type.

[0015] Preferably, the configuration management module also includes an interface mapping management submodule, which is used to uniformly manage the interfaces between various modules or systems in the system to ensure that the mapping relationship between interfaces is clear and accurate. It includes an interface mapping management list interface and a new interface mapping interface, wherein: the interface mapping management list interface displays the source interface, mapping interface, channel and priority; the new interface mapping interface is used to select the source interface, mapping interface, channel and configuration priority.

[0016] Preferably, it also includes interface parameter management and interface parameter mapping management modules, wherein:

[0017] The interface parameter management module mainly maps, converts names, and converts types of parameters of access interfaces and transfer interfaces. It includes an interface parameter management list interface and a new interface parameter interface. The interface parameter management list interface displays parameter ID, interface ID, interface type, interface name, parameter type, parameter name, and whether it can be empty. The new interface parameter interface can configure the interface type, interface, parameter type, parameter name, and empty flag.

[0018] The interface parameter mapping management module is used to manage and convert input parameters and output parameters. It includes an interface parameter mapping management list interface and a new parameter mapping interface. The interface parameter mapping management list interface displays the access interface, access parameters, transfer interface, transfer interface parameter name and creation time. The new parameter mapping interface is used to select the access interface, access interface parameters, transfer interface and transfer interface parameters.

[0019] A method for implementing a configuration-based scheduling system for an HTTP interface based on Redis comprises the following steps: parsing a caller's input parameter message in JSON and XML formats through jsonPath, Snack3, and staxon to achieve parameter path matching and mapping, matching any node in the message structure, and supporting personalized processing of the interface configuration; verifying the nullability of parameters and converting their types to achieve compatibility between local interface types and third-party interface types; providing encryption configuration including symmetric and asymmetric encryption, field encryption, and message encryption for the entire request process to ensure data security; storing and managing the interface configuration information in a Redis cache, storing switch information in a secondary cache, and persisting it in a database; and using the cached data for request processing when the interface is called.

[0020] Preferably, it also includes access channel authority management steps, specifically: displaying the access channel authority ID, authorized channels, channel authorized interface name and authorization status in the access channel authority management list interface; configuring the access channel, system status and access interface in the new access channel authority interface to implement control of interface access and ensure that only authorized users or systems can access the interface through specific channels.

[0021] Preferably, it also includes an interface management step, specifically: querying the interface by interface type, interface name, and interface class name in the interface management list interface and returning the interface list, supporting the addition / modification of access interfaces and transfer interfaces; configuring the interface name, whether it is provided by the system, interface class name, interface mode, channel, interface path, interface request mode, interface status, interface validity time, interface call threshold and message format type in the new access / modify access interface interface to realize the management of access interfaces and transfer interfaces.

[0022] Preferably, it also includes an interface mapping management step, specifically: displaying the source interface, mapping interface, channel and priority in the interface mapping management list interface; selecting the source interface, mapping interface, channel and configuration priority in the new interface mapping interface, and uniformly managing the interfaces between various modules or systems in the system to ensure that the mapping relationship between interfaces is clear and accurate, and that data interaction and communication can be carried out efficiently.

[0023] Preferably, the process further includes interface parameter management and interface parameter mapping management steps, wherein:

[0024] The interface parameter management steps are as follows: display the parameter ID, interface ID, interface type, interface name, parameter type, parameter name, and whether it can be left blank on the interface parameter management list interface; configure the interface type, interface to which it belongs, parameter type, parameter name, and the left blank flag on the new interface parameter interface; and perform mapping, name conversion, and type conversion on the parameters of the access interface and transfer interface;

[0025] The steps for interface parameter mapping management are as follows: display the access interface, access parameters, transfer interface, transfer interface parameter name and creation time in the interface parameter mapping management list interface; select the access interface, access interface parameters, transfer interface and transfer interface parameters in the new parameter mapping interface; manage and convert the input parameters and output parameters to ensure that the request parameters sent by the client can correctly match the internal logic and data structure of the backend service, and at the same time ensure that the data returned by the backend service can be displayed in the format expected by the client.

[0026] Compared with the prior art, the present invention has the following beneficial effects:

[0027] The present invention proposes a Redis-based HTTP interface configuration scheduling system and method. The interface encapsulation is configured, and developers can complete interface development through configuration or a small amount of code. After testing, the interface can be put online, which effectively reduces the difficulty of interface development, shortens the interface development time, improves the interface development efficiency, and effectively reduces labor costs.

[0028] Interface encapsulation and configuration can be mastered through simple training, and non-code developers can also complete the development and launch of the interface through learning; at the same time, interface encapsulation and configuration adopts a non-invasive method and has no coupling relationship with the existing interface. The low-code capability reduces code development and can also reduce the problems caused by code development.

[0029] When the interface needs to be modified, the relevant operations can be completed through configuration, realizing code-free transformation, which can effectively reduce the frequency of version launch and operation and maintenance release, reduce the relevant costs of launch, and avoid possible failures caused by system release, which is conducive to ensuring the stability of the system.

[0030] Due to the urgency of user needs and the rapid iteration of business system construction and optimization, the low-code capabilities supported by business interfaces can greatly improve the efficiency of interface development and optimization. Completing interface development, modification and other operations in a low-code configuration manner can support business development faster and improve user satisfaction.

[0031] Parameter path matching and mapping are implemented through methods such as jsonPath, Snack3, and staxon, enabling matching of any node in the message structure and supporting personalized interface configuration. Parameter nullability is verified and type conversion is performed to achieve compatibility between local and third-party interface types, improving field usability. Symmetric and asymmetric encryption, field encryption, and message encryption are supported, providing encryption configuration for the entire request process to ensure data security. Personalized configuration can meet a wider range of business scenarios, while modular configuration avoids coupling between interfaces and within interfaces, improving subsequent maintenance efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 This is a system block diagram of the present invention;

[0033] Figure 2 Flow chart of the method of the present invention. DETAILED DESCRIPTION

[0034] In order to clearly and completely describe the objectives and technical solutions of the present invention and make the advantages more clearly understood, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are part of the embodiments of the present invention, not all of them, and are only used to explain the embodiments of the present invention, not to limit the embodiments of the present invention. All other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0035] In the first embodiment, please refer to the figure. The present invention provides a technical solution: a configuration-based scheduling system for implementing HTTP interfaces based on Redis, comprising:

[0036] The message parsing module supports parsing messages in both json and xml formats. It implements parameter path matching and mapping through jsonPath, Snack3, and staxon, matches any node in the message structure, and supports parameter nullability verification and type conversion to achieve compatibility between local interface types and third-party interface types.

[0037] The encryption module supports symmetric encryption and asymmetric encryption, field encryption and message encryption, and provides encryption configuration for the entire request process.

[0038] The configuration management module saves the configuration information of the interface in the redis cache for management, puts the switch information into the secondary cache and persists it in the database, and uses the cached data for request processing when the interface is called; the configuration management module also includes an access channel permission management sub-module, which is used to control interface access to ensure that only authorized users or systems can access the interface through specific channels. It includes an access channel permission management list interface and a new access channel permission interface, among which: the access channel permission management list interface displays the access channel permission ID, authorized channels, channel authorized interface name and authorization status; the new access channel permission interface is used to configure access channels, system status and access interfaces.

[0039] The configuration management module also includes an interface management submodule. The interface management submodule supports the management of access interfaces and transfer interfaces, including an interface management list interface and a new access / modify access interface interface. Among them: the interface management list interface can query the interface by interface type, interface name, and interface class name and return the interface list, and supports adding / modifying access interfaces and transfer interfaces; interface types are divided into access interfaces and transfer interfaces, the access interface is the local system interface, and the transfer interface is a third-party interface connected to the local interface; the new access / modify access interface interface can configure the interface name, whether it is provided by the system, the interface class name, the interface mode, the channel, the interface path, the interface request mode, the interface status, the interface validity period, the interface call threshold and the message format type.

[0040] The configuration management module also includes an interface mapping management submodule, which is used to uniformly manage the interfaces between various modules or systems in the system to ensure that the mapping relationship between interfaces is clear and accurate. It includes an interface mapping management list interface and a new interface mapping interface, among which: the interface mapping management list interface displays the source interface, mapping interface, channel and priority; the new interface mapping interface is used to select the source interface, mapping interface, channel and configuration priority.

[0041] Front-end configuration module: Interface developers can personalize the interface through the front-end page, enabling the business system to add and optimize business interface data with low or even no code.

[0042] Technical framework module, the system front-end interface is developed using Angular framework technology, and the back-end application is created using the springboot framework to achieve configurable scheduling of the http interface.

[0043] It also includes interface parameter management and interface parameter mapping management modules, where:

[0044] The interface parameter management module mainly maps, converts names, and converts types of parameters of access interfaces and transfer interfaces. It includes an interface parameter management list interface and a new interface parameter interface. The interface parameter management list interface displays parameter ID, interface ID, interface type, interface name, parameter type, parameter name, and whether it can be empty. The new interface parameter interface can configure the interface type, interface, parameter type, parameter name, and empty flag.

[0045] The interface parameter mapping management module is used to manage and convert input parameters and output parameters. It includes an interface parameter mapping management list interface and a new parameter mapping interface. The interface parameter mapping management list interface displays the access interface, access parameters, transfer interface, transfer interface parameter name and creation time. The new parameter mapping interface is used to select the access interface, access interface parameters, transfer interface and transfer interface parameters.

[0046] Example 2, based on Example 1, proposes a method for implementing a HTTP interface configuration scheduling system based on Redis, including the following steps:

[0047] Parameter path matching and mapping are implemented through methods such as jsonPath, Snack3, and staxon, enabling matching of any node in the message structure and supporting personalized interface configuration. Parameter nullability is verified and type conversion is performed to achieve compatibility between local and third-party interface types, improving field usability. Symmetric and asymmetric encryption, field encryption, and message encryption are supported, providing encryption configuration for the entire request process to ensure data security. Personalized configuration can meet a wider range of business scenarios, while modular configuration avoids coupling between interfaces and within interfaces, improving subsequent maintenance efficiency.

[0048] Interface encapsulation configuration saves the interface configuration information in the redis cache for management, and at the same time puts the switch information into the secondary cache and persists it in the database, which improves the efficiency of interface configuration processing. When the interface is called, the cached data is used for request processing, which minimizes the time spent on processing non-interface request parts and improves the efficiency of the interface.

[0049] Interface developers can personalize the interface configuration through the front-end page to help the business system complete the addition and optimization of business interface data with low code or even no code, reduce the difficulty of interface development, improve the interface support efficiency, and thus reduce development costs.

[0050] The system's front-end interface was developed using the Angular framework, while the back-end application was created using the Spring Boot framework. The combination of these two technologies enables a configurable HTTP interface scheduling system. The system includes menus for access channel permission management, interface management, interface mapping management, interface parameter management, interface parameter mapping management, and Redis cache management.

[0051] Access channel permission management:

[0052] It mainly involves controlling access to interfaces, ensuring that only authorized users or systems can access interfaces through specific channels, thereby protecting the data security and stability of the system.

[0053] (1) Access channel permission management list interface

[0054] ① Access channel authority ID: Displays a globally unique string of channel IDs generated according to internal rules.

[0055] ② Authorized channel: Displays the system name of the caller

[0056] ③Channel authorized interface name: Displays the authorized access interface name

[0057] ④Authorization status: shows whether the corresponding authorization is available

[0058] (2) Added access channel permission interface

[0059] ① Access channel: Configure the caller system

[0060] ②System status: whether the configuration channel is available

[0061] ③Access interface: Configure the access interface bound to this channel

[0062] Interface management:

[0063] It supports the management of access interfaces and transfer interfaces. A series of interface-related information such as interface name, interface path, interface belonging system, request method, interface type and interface protocol can be added and modified through configuration, which greatly improves the management efficiency of the interface, adapts to the rapid development of the business, and enhances the governance capabilities of the interface.

[0064] (1) In the interface management list interface, you can query the interface by interface type, interface name, interface class name to return the interface list, and you can also add / modify access interfaces and transfer interfaces.

[0065] (2) Interface types are divided into access interfaces and transfer interfaces

[0066] Access interface: refers to the local system interface

[0067] Transfer interface: refers to the need to connect to a third-party interface based on the local interface

[0068] (3) Add access / modify access interface configuration:

[0069] ①Interface name: the name of the interface defined in the system

[0070] ② Whether it is provided by the system: whether it is provided by the local system

[0071] ③Interface class name: the program name (class name) that specifically implements the business logic

[0072] ④Interface mode: synchronous interface / asynchronous interface

[0073] ⑤Channel: You can choose a third-party interface source

[0074] ⑥Interface path: configure the URL of the access interface

[0075] ⑦Interface request method: get, post

[0076] ⑧ Interface status: available / unavailable

[0077] ⑨Interface validity period: Configure the validity period of the interface

[0078] ⑩Interface call threshold: the maximum number of times an interface can be called within a unit of time

[0079] 11. Message format type: Select the message format supported by the interface (json / xml)

[0080] Interface mapping management:

[0081] Interface mapping management is the unified management of interfaces between modules or systems within a system, ensuring clear and accurate mappings and efficient data exchange and communication. Interface mapping typically involves converting the interface of one system to the interface of another system to achieve seamless integration between different systems.

[0082] (1) Interface mapping management list interface

[0083] ① Source interface: Displays the configured local interface name

[0084] ②Mapping interface: Displays the configured transfer interface name (third-party interface)

[0085] ③Channel: Display configuration third-party platform

[0086] ④Priority: Displays which transfer interface the local interface will call first when multiple transfer interfaces are configured.

[0087] (2) New interface mapping interface:

[0088] ① Source interface: drop-down selection (select the newly added access interface under the interface management menu)

[0089] ② Mapping interface: drop-down options (select the newly added transfer interface under the interface management menu)

[0090] ③Channel: Select the platform where the transfer interface is located

[0091] ④Priority: When transferring multiple transfer interfaces, configure the priority of the interface

[0092] Interface parameter management:

[0093] It mainly maps the parameters of the access interface and the transfer interface and performs name conversion and type conversion to complete the full configuration conversion from the caller format to the callee interface format, realize low-code or even code-free development, improve development efficiency, and achieve cost reduction and efficiency improvement.

[0094] (1) Interface parameter management list interface

[0095] ①Parameter ID: Displays the added parameter ID value

[0096] ②Interface ID: Displays the ID value corresponding to the selected interface

[0097] ③Interface type: Displays the corresponding interface type (access interface / transfer interface) when adding parameters

[0098] ④Interface name: Displays the interface name corresponding to the parameter

[0099] ⑤Parameter type: Display parameter type (output parameter / input parameter)

[0100] ⑥Parameter name: Displays the configured parameter name

[0101] ⑦Is it empty: Displays whether the parameter is empty

[0102] (2) New interface parameter interface

[0103] ①Interface type: drop-down selection (access interface / transfer interface)

[0104] ②Interface: Select the interface for configuring parameters

[0105] ③Parameter type: Enter the type of the newly added parameter (output parameter / input parameter)

[0106] ④Parameter name: Enter the parameter name

[0107] ⑤Nullable flag: select whether the parameter can be empty

[0108] Interface parameter mapping management:

[0109] The process of managing and converting input and output parameters. It ensures that the request parameters sent by the client correctly match the internal logic and data structure of the backend service, and also ensures that the data returned by the backend service can be displayed in the format expected by the client, improving the usability, compatibility, and maintainability of the interface.

[0110] (3) Interface parameter mapping management list interface

[0111] ①Access interface: Displays the name of the access interface

[0112] ②Access parameters: Display the parameter names corresponding to the access interface

[0113] ③ Transfer interface: Display the name of the transfer interface

[0114] ④ Transfer interface parameters: Name: Display transfer interface name

[0115] ⑤Creation time: Displays the corresponding creation time

[0116] (4) New parameter mapping

[0117] ① Access interface: Select the access interface (drop-down option: newly created interface in interface management)

[0118] ②Access interface parameters: Select the parameters that need to be bound to the access interface

[0119] ③ Transfer interface: Select the transfer interface (drop-down option: newly created interface in interface management)

[0120] ④Transfer interface parameters: Select the parameters that need to be bound to the transfer interface

[0121] ⑤Submit new additions

[0122] Channel management:

[0123] The process of systematically managing the use, security, performance, documentation, and partnerships of interfaces when interacting with external systems (such as partners, third-party developers, and customers) for data and business collaboration.

[0124] Channel management interface:

[0125] ①Channel Name: Displays the name of the configured channel

[0126] ② Address of the system: Displays the IP address of the configuration channel

[0127] ③Creation time: Displays the creation time

[0128] ④Is it effective?: Displays whether the channel is effective.

[0129] New channels:

[0130] ①Channel Name: Configure the name of the channel

[0131] ② Address of the system: IP address of the configuration channel

[0132] ③ Is it valid: Is the configured channel valid?

[0133] Redis cache management:

[0134] (1) Query interface:

[0135] ①Key name: Displays the configuration item ID + business code (key value)

[0136] ②Value: Displays the configured cache value

[0137] (2) Clear the cache:

[0138] ①After querying the corresponding value of Redis cache by key value, click the clear button to delete the value in Redis to refresh the cache.

[0139] The caller's input message is parsed through jsonPath, Snack3 and staxon. The access interface parameter list is obtained by querying Redis according to the interface item id value through Jedis's API and the parameters are checked according to the configuration items. The channel / authority check is checked to see if it passes. If it passes, jsonNode dynamically assembles parameters according to the parameter configuration and the message. The interface mapping management configuration is queried through Jedis's API to determine whether the transfer interface is configured. If not, the local system business logic is returned. Otherwise, the transfer interface configuration item is read. SpringWebFlux initiates a call interface request according to the transfer interface configuration item, obtains the transfer interface output parameter configuration item, and jsonNode returns the result message according to the output parameter configuration.

[0140] If third-party system interfaces are required in this solution, users can configure interface parameters through an intuitive interface. These parameters include, but are not limited to, the request method, path, header information, query parameters, and the request body. Furthermore, the system supports detailed configuration of interface attributes such as the response format, encoding method, and timeout settings. The system's mapping function automatically converts local interface parameters to the format required by third-party interfaces, and vice versa. This automated mapping process not only reduces manual configuration workload but also mitigates issues caused by configuration errors. This means that even if parameters in third-party interfaces change, enterprises can quickly update the mapping rules in the system without requiring complex code modifications or system redeployment. This capability enables enterprises to quickly respond to updates to third-party services, maintaining the continuity and stability of business processes. Focusing solely on internal business logic development, this solution implements a mechanism that stores configuration information in a Redis cache, enabling fast access and low-latency access.

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

Claims

1. A configuration-based scheduling system for HTTP interfaces based on Redis, characterized by: include: The message parsing module supports parsing messages in both json and xml formats. It implements parameter path matching and mapping through jsonPath, Snack3, and staxon, matches any node in the message structure, and supports parameter nullability verification and type conversion to achieve compatibility between local interface types and third-party interface types. The encryption module supports symmetric encryption, asymmetric encryption, field encryption, and message encryption, and provides encryption configuration for the entire request process; The configuration management module stores the interface configuration information in the Redis cache, stores the switch information in the secondary cache and persists it in the database. When the interface is called, the cached data is used for request processing. Front-end configuration module: Interface developers can personalize the interface through the front-end page, enabling the business system to add and optimize business interface data with low or even no code. Technical framework module, the system front-end interface is developed using Angular framework technology, and the back-end application is created using the springboot framework to achieve configurable scheduling of the http interface.

2. The method according to claim 1, wherein the method comprises: The configuration management module also includes an access channel permission management sub-module, which is used to control interface access to ensure that only authorized users or systems can access the interface through specific channels. It includes an access channel permission management list interface and a new access channel permission interface, among which: the access channel permission management list interface displays the access channel permission ID, authorized channels, channel authorized interface name and authorization status; the new access channel permission interface is used to configure access channels, system status and access interfaces.

3. The method according to claim 2, wherein the method comprises: The configuration management module also includes an interface management submodule. The interface management submodule supports the management of access interfaces and transfer interfaces, including an interface management list interface and a new access / modify access interface interface. Among them: the interface management list interface can query the interface by interface type, interface name, and interface class name and return the interface list, and supports adding / modifying access interfaces and transfer interfaces; interface types are divided into access interfaces and transfer interfaces, the access interface is the local system interface, and the transfer interface is a third-party interface connected to the local interface; the new access / modify access interface interface can configure the interface name, whether it is provided by the system, the interface class name, the interface mode, the channel, the interface path, the interface request mode, the interface status, the interface validity period, the interface call threshold and the message format type.

4. The method according to claim 3, wherein the configuration-based scheduling system for implementing HTTP interface based on Redis is characterized in that: The configuration management module also includes an interface mapping management submodule, which is used to uniformly manage the interfaces between various modules or systems in the system to ensure that the mapping relationship between interfaces is clear and accurate. It includes an interface mapping management list interface and a new interface mapping interface, among which: the interface mapping management list interface displays the source interface, mapping interface, channel and priority; the new interface mapping interface is used to select the source interface, mapping interface, channel and configuration priority.

5. The method according to claim 4, wherein the configuration-based scheduling system for implementing HTTP interface based on Redis is characterized in that: It also includes interface parameter management and interface parameter mapping management modules, where: The interface parameter management module mainly maps, converts names, and converts types of parameters of access interfaces and transfer interfaces. It includes an interface parameter management list interface and a new interface parameter interface. The interface parameter management list interface displays parameter ID, interface ID, interface type, interface name, parameter type, parameter name, and whether it can be empty. The new interface parameter interface can configure the interface type, interface, parameter type, parameter name, and empty flag. The interface parameter mapping management module is used to manage and convert input parameters and output parameters. It includes an interface parameter mapping management list interface and a new parameter mapping interface. The interface parameter mapping management list interface displays the access interface, access parameters, transfer interface, transfer interface parameter name and creation time. The new parameter mapping interface is used to select the access interface, access interface parameters, transfer interface and transfer interface parameters.

6. A method for implementing a configuration-based scheduling system for an HTTP interface based on Redis according to claim 5, characterized in that: The following steps are involved: Parse the caller's input message in JSON and XML formats through jsonPath, Snack3, and staxon, implement parameter path matching and mapping, match any node in the message structure, and support personalized processing of interface configuration; Verify the nullability of parameters and convert types to achieve compatibility between local interface types and third-party interface types; Encryption configurations including symmetric and asymmetric encryption, field encryption, and message encryption are provided for the entire request process to ensure data security. The interface configuration information is stored and managed in the Redis cache, while the switch information is placed in the secondary cache and persisted in the database. The cached data is used for request processing when the interface is called.

7. A method according to claim 6, characterized in that: It also includes access channel permission management steps, specifically: displaying the access channel permission ID, authorized channels, channel authorized interface name and authorization status in the access channel permission management list interface; configuring the access channel, system status and access interface in the new access channel permission interface to implement control over interface access and ensure that only authorized users or systems can access the interface through specific channels.

8. A method according to claim 7, characterized in that: It also includes interface management steps, specifically: query the interface by interface type, interface name, and interface class name in the interface management list interface and return the interface list, supporting the addition / modification of access interfaces and transfer interfaces; configure the interface name, whether it is provided by the system, interface class name, interface mode, channel, interface path, interface request mode, interface status, interface validity time, interface call threshold and message format type in the new access / modify access interface interface to realize the management of access interfaces and transfer interfaces.

9. A method according to claim 8, characterized in that: It also includes interface mapping management steps, specifically: displaying the source interface, mapping interface, channel and priority in the interface mapping management list interface; selecting the source interface, mapping interface, channel and configuration priority in the new interface mapping interface, and uniformly managing the interfaces between various modules or systems in the system to ensure that the mapping relationship between interfaces is clear and accurate, and that data interaction and communication can be carried out efficiently.

10. A method according to claim 9, characterized in that: It also includes interface parameter management and interface parameter mapping management steps, where: The interface parameter management steps are as follows: display the parameter ID, interface ID, interface type, interface name, parameter type, parameter name, and whether it can be left blank on the interface parameter management list interface; configure the interface type, interface to which it belongs, parameter type, parameter name, and the left blank flag on the new interface parameter interface; and perform mapping, name conversion, and type conversion on the parameters of the access interface and transfer interface; The steps for interface parameter mapping management are as follows: display the access interface, access parameters, transfer interface, transfer interface parameter name and creation time in the interface parameter mapping management list interface; select the access interface, access interface parameters, transfer interface and transfer interface parameters in the new parameter mapping interface; manage and convert the input parameters and output parameters to ensure that the request parameters sent by the client can correctly match the internal logic and data structure of the backend service, and at the same time ensure that the data returned by the backend service can be displayed in the format expected by the client.

Images