Automatic interface docking method and system, medium and low-code development platform

Abstract

The invention discloses an automatic interface docking method and system, a medium and a low-code development platform, and relates to the field of Internet information services, and the method comprises the steps: determining a target interface as a docking target in an interface database according to an interface docking request of a user; obtaining an interface configuration file of the target interface, wherein the interface configuration file comprises a service port, an interface transmission protocol and interface authentication setting; generating a calling code template based on the service port, the interface transmission protocol and the interface authentication setting; generating an interface calling code based on parameter setting of a user on the calling code template; and when the interface configuration file of the target interface changes, updating the interface calling code. According to the invention, the interface docking efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of Internet information services, and in particular to an interface automation docking method, system, medium and low-code development platform. Background Art

[0002] As enterprises’ digital transformation deepens, the demand for interconnection between information systems is growing. Enterprises often need to connect to multiple internal and external systems during business operations, such as ERP, CRM, and supply chain management systems. The data exchange and business collaboration between these systems have a significant impact on the operational efficiency and market competitiveness of enterprises. Especially in the context of the rapid development of new technologies such as the Internet of Things and artificial intelligence, enterprises are facing more complex system integration scenarios and higher development efficiency requirements.

[0003] In related technologies, a dedicated system integration development team is usually used to manually write interface adaptation codes to achieve docking between systems. Developers first need to understand the interface documents of each system, and then develop corresponding data conversion modules and interface call programs based on specific business needs. In this process, the development team usually adopts a unified interface specification and development framework, and establishes a corresponding testing process to ensure the reliability of the interface. Some companies also use middleware products such as ESB (Enterprise Service Bus) or API Gateway to uniformly manage and schedule interface calls between various systems.

[0004] However, in the related technology, technicians need to spend a lot of time to understand the interface specifications of different systems, and need to repeat code modification and testing work when the interface changes, resulting in low interface docking efficiency. Summary of the invention

[0005] The present application provides an interface automation docking method, system, medium and low-code development platform for improving interface docking efficiency.

[0006] In the first aspect, the present application provides an interface automation docking method, which is applied to an interface management system, and the method includes: determining a target interface in an interface database as a docking target according to a user's interface docking request; obtaining an interface configuration file of the target interface including a service port, an interface transmission protocol, and an interface authentication setting; generating a calling code template based on the service port, the interface transmission protocol, and the interface authentication setting; generating an interface calling code based on the user's parameter settings for the calling code template; and updating the interface calling code when the interface configuration file of the target interface changes.

[0007] In the above embodiment, the interface management system automatically determines the target interface and obtains its configuration file based on the user request, generates a calling code template and an interface calling code according to the configuration, and automatically updates the code when the configuration changes, thereby automating the interface docking process, avoiding the tedious work of manually writing and maintaining interface codes, improving the efficiency of interface docking, and ensuring synchronous code updates when the interface configuration changes, thereby enhancing the system maintainability and reliability.

[0008] In combination with some embodiments of the first aspect, in some embodiments, the step of generating a calling code template based on the service port, interface transmission protocol and interface authentication settings specifically includes: determining a request interface for issuing an interface docking request, and determining a target transmission protocol for the request interface; determining data conversion rules based on the interface transmission protocol and the target transmission protocol; matching the corresponding calling code template in the interface model library based on the data conversion rules, service port and interface authentication settings.

[0009] In the above embodiment, the interface management system realizes automatic conversion and adaptation between different protocols by determining the request interface and the target transmission protocol, formulating data conversion rules, and calling code templates based on rule matching, thereby solving the compatibility problem of interface docking between heterogeneous systems, simplifying the protocol conversion process, and improving the accuracy and efficiency of interface adaptation.

[0010] In combination with some embodiments of the first aspect, in some embodiments, before the step of determining the target interface in the interface database as the docking target according to the user's interface docking request, the method also includes: determining the target system based on the user's selection, and displaying multiple interface models of the target system; generating an interface docking request according to the user's option selection among the multiple interface models.

[0011] In the above embodiment, the interface management system provides target system selection and interface model display functions, allowing users to intuitively select the required interface and generate a docking request, thereby realizing visual operation of the interface configuration process, lowering the threshold for interface configuration, improving user experience, and reducing the possibility of configuration errors.

[0012] In combination with some embodiments of the first aspect, in some embodiments, after the step of generating an interface docking request based on the user's option selection in multiple interface models, the method also includes: storing historical call records of interface docking requests to the target system; performing model training based on multiple historical docking requests in the historical call records to generate a call prediction model; determining a preset docking request for the target system based on the call prediction model; and generating a preset interface, preset parameter configuration and preset call code for interface docking with the target system based on the preset docking request.

[0013] In the above embodiment, the interface management system realizes the automation of interface docking by recording historical call data, training prediction models and generating preset configurations. It can automatically recommend appropriate interface configurations based on historical experience, improve configuration efficiency and reduce manual intervention.

[0014] In combination with some embodiments of the first aspect, in some embodiments, after the step of generating an interface call code based on the user's parameter settings for the call code template, the method also includes: based on the interface call code, packaging the docking service of the target interface into a container image; deploying the container image in a container cluster so that the target interface runs in an independent environment; monitoring the call load of the target interface and adjusting the number of container instances according to the call load.

[0015] In the above embodiment, the interface management system realizes elastic scaling and isolated operation of interface services by containerizing and deploying interface services and dynamically adjusting the number of instances according to the load, thereby improving the availability and stability of the system and optimizing resource utilization efficiency.

[0016] In combination with some embodiments of the first aspect, in some embodiments, after the step of generating an interface calling code based on the user's parameter settings for the calling code template, the method also includes: in response to the user's event binding operation, binding a task event to the target interface, and determining the triggering conditions of the task event; executing the task event when the target interface meets the triggering conditions; obtaining the execution status of the task event, and updating the task status field when the execution status changes.

[0017] In the above embodiment, the interface management system realizes the automatic triggering and status monitoring of interface tasks by providing an event binding mechanism, enhances the automation of interface calls, provides real-time feedback on task execution status, and facilitates system monitoring and management.

[0018] In combination with some embodiments of the first aspect, in some embodiments, the step of determining the target interface in the interface database as the docking target based on the user's interface docking request specifically includes: based on the visual configuration interface, displaying the preset interface model in the interface model library; receiving the user's drag operation in the visual configuration interface to determine the target interface model; matching the corresponding target interface in the interface database according to the configuration parameters of the target interface model.

[0019] In the above embodiment, the interface management system realizes intuitive selection and matching of interface models through a visual configuration interface and drag-and-drop operations, simplifies the interface configuration process, improves operational convenience, and lowers the usage threshold.

[0020] In a second aspect, an embodiment of the present application provides an interface management system, which includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the interface management system to execute the method described in the first aspect and any possible implementation method of the first aspect.

[0021] In the third aspect, an embodiment of the present application provides a low-code development platform including instructions. When the above-mentioned low-code development platform runs on an interface management system, the above-mentioned interface management system executes the method described in the first aspect and any possible implementation method of the first aspect.

[0022] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on an interface management system, enables the interface management system to execute the method described in the first aspect and any possible implementation of the first aspect.

[0023] It can be understood that the interface management system provided in the second aspect, the low-code development platform provided in the third aspect, and the computer storage medium provided in the fourth aspect are all used to execute the method provided in the embodiment of the present application. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be repeated here.

[0024] One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: 1. Due to the adoption of a technical solution that automatically determines the target interface based on user requests, obtains configuration files, generates calling codes, and automatically updates when the configuration changes, the entire process from interface selection to code generation can be completed, effectively solving the problem of manually writing and maintaining interface codes and manually updating codes when configuration changes are required in related technologies, thereby realizing the automation, standardization and intelligence of the interface docking process, improving development efficiency, reducing maintenance costs, and enhancing the reliability and adaptability of the system.

[0025] 2. Due to the adoption of a technical solution that trains models based on historical call records and generates preset configurations, the system can analyze historical docking experience and predict the optimal configuration through machine learning, effectively solving the problem that interface configuration in related technologies relies on manual experience and lacks intelligent recommendations, thereby realizing the intelligent and automated interface configuration, greatly improving configuration efficiency and reducing configuration error rate.

[0026] 3. Due to the adoption of a technical solution based on an event binding mechanism to realize automatic triggering of interface tasks and status monitoring, the system can automatically execute interface calls and track task status in real time according to preset conditions, effectively solving the problem that interface calls in related technologies require manual triggering and lack of status feedback, thereby realizing the automation and visual monitoring of interface calls, enhancing operation and maintenance monitoring capabilities, and ensuring the reliability and timeliness of interface calls. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 This is a flow chart of the automatic interface docking method in the embodiment of the present application; Figure 2 This is a schematic diagram of a scenario of the interface automatic docking method in an embodiment of the present application; Figure 3 This is another flowchart of the interface automation docking method in the embodiment of the present application; Figure 4 It is a schematic diagram of the structure of a physical device of the interface management system in an embodiment of the present application. DETAILED DESCRIPTION

[0028] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be used as limitations to the present application. As used in the specification of the present application, the singular expressions "one", "a kind of", "above", "the" and "this" are intended to also include plural expressions, unless there is a clear indication to the contrary in the context. It should also be understood that the term "and / or" used in the present application refers to any or all possible combinations comprising one or more of the listed items.

[0029] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

[0030] For ease of understanding, the application scenarios of the embodiments of the present application are introduced below.

[0031] A multinational e-commerce platform needs to integrate payment systems, logistics systems, and tax systems in multiple countries. Each country's system has its own specific interface specifications and certification requirements. For example, the United States uses REST API, Japan prefers SOAP protocol, and the European Union requires strict security certification. The development team faces the challenge of manually writing and maintaining hundreds of interface adaptation codes. Every time the system is updated or a new country is added, a lot of manpower is required for interface development and testing, which hinders business expansion. In addition, the systems in different countries often change interfaces, which requires a huge maintenance workload and is prone to errors.

[0032] In the related art, a dedicated system integration development team can manually write interface adaptation codes and use middleware products such as ESB or API gateway to achieve docking between systems. The following describes the scenario of using the interface automatic docking method in the related art.

[0033] An enterprise uses traditional ESB middleware to handle system integration needs. Developers need to manually write interface adaptation code between various systems and configure routing rules in ESB. When a supplier system updates the interface, developers need to modify the relevant code and redeploy it. For example, when processing the connection between the order system and the warehousing system, since the two systems use different data formats, developers need to write data conversion logic. When the API structure is changed after the warehousing system is upgraded, the adaptation code cannot automatically adapt to the changes, resulting in interruption of communication between systems, which requires manual intervention and repair, affecting business continuity.

[0034] The interface automation docking method in the embodiment of the present application is adopted, and the interface docking automation is realized through the interface model library, automatic code generation and configuration change monitoring and other technologies, which not only improves the development efficiency, but also ensures the stability and maintainability of the interface service. The following introduces the scenario in which the interface automation docking method in the present application is used.

[0035] A smart city platform uses the interface automation docking method of this application to achieve seamless integration of multiple government systems. The platform displays the interface models of each system through a visual interface, and operation and maintenance personnel only need to drag and drop to select the systems and interfaces that need to be docked. The system automatically generates adaptation code and supports protocol conversion. For example, when the transportation system needs to call data from the public security system, the platform automatically handles the protocol conversion from REST to SOAP and automatically configures security authentication. When any system upgrades the interface, the platform can automatically detect changes and update the calling code to ensure the continuous availability of the service.

[0036] It can be seen that the interface automatic docking method in the embodiment of the present application can not only realize the interconnection between systems, but also effectively solve the problems of low manual development efficiency and high maintenance cost, thereby realizing the standardization, automation and intelligence of the interface docking process.

[0037] For ease of understanding, the following describes the process of the method provided by this implementation in combination with the above scenario. Figure 1 , which is a flow chart of the interface automatic docking method in an embodiment of the present application.

[0038] S101. According to a user's interface docking request, determine a target interface in an interface database as a docking target.

[0039] Among them, the interface docking request refers to the application sent by the user to establish data exchange between two systems or services; the interface database refers to the data warehouse that stores all available interface information in the system, including the basic information, configuration parameters and calling rules of the interface; the target interface refers to the specific interface instance that the user wants to dock.

[0040] When the interface management system receives the interface connection request initiated by the user, it needs to determine the specific target interface to be connected. Specifically, the system first parses the connection request submitted by the user, extracts key information such as the target system, business type, data format, etc., and then accurately matches and filters in the interface database based on this information, and finally determines the target interface that meets the user's needs.

[0041] In some embodiments, the target interface determination process can be implemented in a variety of ways: Optionally, the system can receive the target system selected by the user on the interface, and then filter out a list of related interfaces based on the target system, and then match the interfaces based on the user's screening conditions, and return the matching results for the user to confirm; Optionally, the system can also parse the interface description file uploaded by the user, and extract the interface feature information in the file, and then perform feature matching in the database, and determine the target interface after sorting by matching degree. It is understandable that other methods can also be used to determine the target interface, such as automatic discovery through the API gateway or acquisition by the service registration center, which is not limited here.

[0042] S102: Acquire an interface configuration file of the target interface including a service port, an interface transmission protocol, and an interface authentication setting.

[0043] Among them, the service port indicates the network port number of the target interface providing services; the interface transmission protocol refers to the network communication protocol used for data transmission, such as HTTP, HTTPS, WebSocket, etc.; the interface authentication setting indicates the identity authentication method and related parameters required when accessing the interface, including authentication type, key, token and other security credentials; the interface configuration file refers to a structured document that describes the complete technical parameters of the interface.

[0044] After determining the target interface, the interface management system needs to obtain the detailed configuration information of the interface to support subsequent code generation. Specifically, the system first accesses the interface configuration management module to obtain the configuration file of the target interface; then parses the content of the configuration file, extracts the service port information to determine the interface access address, parses the transmission protocol information to determine the data transmission method, obtains the authentication settings to achieve secure access, and finally forms a complete interface parameter set.

[0045] In some embodiments, the configuration file can be obtained in a variety of ways: optionally, the system can query the configuration center to obtain the latest configuration, verify the integrity and validity of the configuration file, and then decrypt the sensitive configuration information to build a standard configuration object; optionally, the system can also load the basic configuration from the local configuration library, supplement the dynamic configuration through remote calls, merge the information of multiple configuration sources, and cache the processed configuration data. It is understandable that other methods can also be used to obtain the configuration file, such as periodically pulling from the configuration server or pushing through a message queue, which is not limited here.

[0046] S103: Generate a calling code template based on the service port, interface transmission protocol and interface authentication settings.

[0047] The calling code template represents the basic code framework for generating the final interface calling code, including common calling logic and configurable parameter placeholders.

[0048] After obtaining the interface configuration information, the interface management system needs to generate a call code template that conforms to the current configuration. Specifically, the system first selects the corresponding basic code template according to the interface transmission protocol, then injects the service port information into the service address configuration, then supplements the authentication-related code logic according to the authentication settings, and finally preprocesses the template to form a code template that can be further customized.

[0049] In some embodiments, the generation of code templates can be achieved in a variety of ways: optionally, the system can select a basic template from a template library, inject configuration parameters, supplement authentication logic, and generate parameter verification code; optionally, the system can also dynamically assemble template fragments, add error handling logic, and inject logging code to generate a complete template structure. It is understandable that the generation of code templates can also be achieved in other ways, such as based on DSL parsing or using a code generation engine, which is not limited here.

[0050] S104: Generate an interface calling code based on the parameter settings of the calling code template by the user.

[0051] Among them, parameter settings refer to the specific configurations made by users for configurable items in the calling code template, including business parameters, timeout settings, retry strategies, etc.; interface calling code refers to the complete interface calling program code that can be finally executed.

[0052] After the interface management system generates the calling code template, it needs to complete the personalized configuration of the code according to the specific needs of the user. Specifically, the system first displays the configurable items in the code template for the user to set, then collects the user's parameter configuration, then verifies the legitimacy of the parameters, and finally replaces the user's configured parameter values ​​into the code template to generate the final calling code.

[0053] In some embodiments, the generation of the call code can be achieved in a variety of ways: optionally, the system can collect user parameter configurations, verify parameter validity and replace template placeholders to generate complete call code; optionally, the system can also merge default configurations and inject business parameters to optimize the generated code. It is understandable that other methods can also be used to generate the call code, such as through a visual configuration interface or a command line tool, which is not limited here.

[0054] S105. When the interface configuration file of the target interface changes, update the interface calling code.

[0055] The configuration file change indicates that the configuration of the target interface, such as the service port, transmission protocol or authentication setting, is updated.

[0056] The interface management system needs to continuously monitor the configuration changes of the target interface and ensure that the calling code is synchronized with the latest configuration. Specifically, the system first establishes a change monitoring mechanism for the configuration file. When a configuration change is detected, it obtains the latest configuration information, then analyzes the changes, and decides whether to perform a partial update or regenerate the calling code based on the degree of change. Finally, the code update is completed and the relevant parties (user terminals connected to the interface) are notified.

[0057] In some embodiments, the dynamic update of the code can be achieved in a variety of ways: optionally, the system can monitor the configuration change event, compare the configuration difference, and then incrementally update the calling code and notify the code user; optionally, the system can also regularly check the configuration version, back up the existing code, regenerate the calling code, and then smoothly switch to the new code. It is understandable that other methods can also be used to update the calling code, such as pushing through the configuration center or managing the version control system, which is not limited here.

[0058] In the above embodiment, the system can automatically complete the whole process from interface selection to code generation. In practical applications, the scalability and availability of the system can be further improved through technologies such as containerized deployment and load balancing. The following is a supplement to the scenario of this embodiment.

[0059] A cloud service provider has established an intelligent interface management platform based on this solution. The system uses machine learning to analyze historical call data and predict interface usage patterns and load changes. When a surge in the number of visits to a service is detected, the number of container instances is automatically expanded. The platform also integrates an interface anomaly warning mechanism to proactively adjust the configuration when potential problems are found. For example, during the Double 11 period, the system predicted that the load on the order interface would increase significantly, prepared an elastic expansion plan in advance, and automatically optimized the performance parameters of the call code to ensure stable operation during business peak periods.

[0060] In combination with the above scenarios, the following describes the interface management platform involved in this application. Figure 2 , Figure 2 A schematic diagram of a scenario of the interface automatic docking method in the embodiment of the present application; Figure 2 (a) shows the graphical interface of the interface management platform. Figure 2 In (a), area 201 is the main menu option, including four main options: system management, system monitoring, system tools, and data platform; after the data platform is selected, area 202 is the sub-menu option, including four sub-options: data source configuration, interface configuration, task management, and data receiving configuration; Figure 2 In (a), the data source configuration option of the data platform is selected, and a specific configuration list is displayed in area 203, including multiple configuration options such as id, source table name, etc. Different configuration items are selected in the submenu option 202, and the configuration list 203 can display different configuration lists.

[0061] The following is a more detailed description of the process of the method provided by this implementation. Figure 3 , is another flow chart of the interface automatic docking method in an embodiment of the present application.

[0062] S301 . Determine a target system based on user selection, and display multiple interface models of the target system.

[0063] Among them, the target system represents the external system or application platform that needs to be interfaced; the interface model refers to the structured description of the interface, including the name, function, parameter format, return value and other information of the interface; multiple interface models represent the collection of all available interfaces provided by the target system.

[0064] When the user starts the interface docking operation, the interface management system needs to help the user select the target system and browse the available interfaces. Specifically, the system first displays a list of all dockable systems for the user to choose. When the user selects the target system, the system obtains all interface definitions of the system from the interface registration center, classifies and organizes these interfaces according to business domains, functional types and other dimensions, and finally displays these interface models on the interface in a tree structure or list form, and provides auxiliary functions such as search and filtering.

[0065] For the interface management platform, see Figure 2 , Figure 2 A schematic diagram of a scenario of the interface automatic docking method in the embodiment of the present application; Figure 2 (b) shows the interface for adding data source configuration, which is the basic configuration link for realizing automatic interface docking. Through the user's setting of data types, the interface management system can determine the basic rules and verification methods for data processing, and provide data specifications for subsequent interface calls; through the user's setting of source table names and source table primary keys, the interface management system can determine the data source and unique identification field, and establish a data tracking mechanism; through the user's setting of target table names and target table primary keys, the interface management system can determine the data storage location and association relationship, and realize accurate data mapping; in addition, there are two options, reading topic and entering topic, which can be used to configure the message queue topics when reading and writing data, respectively, to realize asynchronous data transmission, and provide a reliable data foundation for subsequent interface calls. These configurations together constitute the data-level support for automatic interface docking, laying the foundation for subsequent interface configuration and task management.

[0066] It should be noted that the interface model in this application can be generated quickly; specifically, the interface management system builds a standardized interface model by collecting and analyzing the definition information of various interfaces, including interface name, function description, parameter format, return value type, authentication method and other data; and then generates a reusable interface model template by extracting common features and personalized features. The interface model is a structured description of interface features, including basic attributes (such as service ports, transmission protocols, authentication settings) and extended attributes (such as business types, performance requirements, error handling strategies, etc.). The interface model adopts a hierarchical structure, supports inheritance and combination, and is convenient for quickly building new interface definitions. The interface management system can perform interface matching and code generation based on the interface model. When entering the basic information of the new interface, the interface management system can classify and match according to the characteristics of the interface model, output the most similar model template, and assist users in quickly completing the interface configuration.

[0067] In some embodiments, target system selection and interface display can be achieved in a variety of ways: Optionally, the system can load the system directory tree, parse the system interface list, build an interface classification view, and then render the interface list interface by applying display filtering rules; Optionally, the system can also query the service registration center, obtain interface metadata, build an interface index, generate an interface navigation tree, and display the interface detail card. It is understandable that other methods can also be used to achieve system selection and interface display, such as through configuration file import or API document parsing, which are not limited here.

[0068] S302: Generate an interface connection request according to the user's selection of options in multiple interface models.

[0069] The interface connection request refers to a structured data object that includes information such as the target system, target interface, and connection parameters.

[0070] After obtaining the user's interface selection, the interface management system needs to construct a standard interface docking request. Specifically, the system first records the target interface information selected by the user, then collects the basic parameters required for the interface call, then verifies the integrity and legality of the parameters, and finally encapsulates this information into a standard request object to prepare for subsequent interface docking processing.

[0071] For the interface management platform, see Figure 2 , Figure 2 A schematic diagram of a scenario of the interface automatic docking method in the embodiment of the present application; Figure 2(c) shows the interface for adding interface configuration, which is a further configuration based on the completed data source configuration. Through the user's settings of the interface name, URL address, request method, and request type, the interface management system can establish a basic interface call framework to ensure the accessibility and standardization of the interface; in addition, batchSize and handler can be used to set the size of batch processing data and the type of data processor, respectively, to optimize and customize data processing; in the request parameters and return parameters, the parameter name, type, and value (variable) can be configured respectively, based on which the interface management system can implement parameter mapping and data conversion to ensure the accuracy of data exchange; at the same time, the signature field can be used to configure the security verification method of the interface call to provide security protection; there is also an encryption button option to control the encryption processing during data transmission to further enhance data security. These detailed interface configurations provide specific execution specifications for subsequent task configuration and automated execution.

[0072] In some embodiments, the interface management system also stores historical call records of interface docking requests to the target system; performs model training based on multiple historical docking requests in the historical call records to generate a call prediction model; determines a preset docking request for the target system based on the call prediction model; and generates a preset interface, preset parameter configuration and preset call code for interface docking with the target system based on the preset docking request.

[0073] Among them, historical call records represent past interface docking operation information recorded by the system; call prediction model refers to an algorithm model built through machine learning methods for predicting interface call trends; preset docking request represents the standardized interface call configuration pre-generated by the system; preset interface represents the target interface recommended by the system; preset parameter configuration refers to the interface call parameter set pre-generated by the system; preset call code represents the standard interface call program automatically generated by the system.

[0074] After completing the interface docking operation, the interface management system needs to accumulate data and make intelligent predictions. Specifically, the system first stores the detailed information of each interface docking request in the historical database, including request time, docking parameters, call results, etc.; then trains the prediction model based on these historical data to analyze the interface call mode and parameter characteristics; then uses the trained model to predict possible future docking requirements and generate standardized preset configurations; finally, converts these preset configurations into specific interface call implementations.

[0075] It should be noted that the call prediction model in this application collects historical call records as training data during training, including call time, call frequency, request parameters, response time and other information. These data are analyzed by machine learning algorithms to identify call patterns and load characteristics, and train a model that can predict interface call trends. The training standards include prediction accuracy, time window coverage and model generalization ability. The call prediction model uses time series analysis and pattern recognition algorithms to predict interface calls in the future based on historical data. The call prediction model takes into account multiple dimensions such as time periodicity, business relevance and environmental factors, and supports short-term and medium-term load forecasts. By inputting real-time monitoring data and historical statistical data, the call prediction model can output future call volume forecasts and load trends. Based on the prediction results, the interface management system can adjust resource configuration in advance, such as adding container instances, optimizing caching strategies, etc., to ensure the stability of the service.

[0076] S303: According to the interface docking request of the user, determine the target interface in the interface database as the docking target.

[0077] Referring to step S101 , the interface management system determines a target interface.

[0078] In some embodiments, the interface management system displays preset interface models in the interface model library based on a visual configuration interface; receives a user's drag operation on the visual configuration interface to determine the target interface model; and matches the corresponding target interface in the interface database according to the configuration parameters of the target interface model.

[0079] Among them, the visual configuration interface refers to the graphical operating platform for interface configuration; the preset interface model refers to the standard interface template pre-defined in the system; the drag operation refers to the interface operation performed by the user through dragging and dropping the mouse; the target interface model refers to the specific interface template selected by the user.

[0080] When providing interface configuration services, the interface management system needs to provide users with intuitive operation methods. Specifically, the system first loads all preset models in the interface model library and displays them visually on the interface; then supports users to select and configure the target interface by dragging and dropping, and previews the configuration effect in real time; finally, according to the interface model confirmed by the user, automatically matches the corresponding specific interface implementation in the database.

[0081] S304: Obtain an interface configuration file of the target interface including a service port, an interface transmission protocol, and an interface authentication setting.

[0082] Referring to step S102, the interface management system obtains an interface configuration file.

[0083] S305: Determine a request interface for sending an interface docking request, and determine a target transmission protocol for the request interface.

[0084] The request interface refers to the source system interface that initiates the connection request; the target transmission protocol refers to the data transmission method that the request interface expects to use.

[0085] When processing a connection request, the interface management system needs to clarify the protocol requirements of both parties. Specifically, the system first parses the initiator's interface information from the connection request, including the interface identifier, the system to which it belongs, etc., then analyzes the transmission protocol currently used by the interface, and finally determines the target transmission protocol it expects to use, in preparation for subsequent protocol conversion.

[0086] In some embodiments, the determination of the request interface and the transmission protocol can be achieved in a variety of ways: Optionally, the system can parse the request metadata, extract the interface identifier, and query the interface registration information to identify the current protocol type and determine the target protocol requirements; Optionally, the system can also read the interface configuration file, analyze the protocol dependency, and verify the protocol compatibility to determine the protocol version and record the protocol mapping relationship. It is understandable that other methods can also be used to achieve the determination of the request interface and protocol, such as obtaining through service discovery or configuration center, which is not limited here.

[0087] S306: Determine data conversion rules according to the interface transmission protocol and the target transmission protocol.

[0088] The interface transmission protocol refers to the protocol currently used by the target interface; the data conversion rule refers to the mapping rule for converting data formats between different protocols.

[0089] After the interface management system clarifies the agreement between the two parties, it needs to establish a data conversion plan. Specifically, the system first compares the transmission protocol differences between the source interface and the target interface, and then searches for existing conversion rules from the rule library. If no matching rules are found, the conversion rules are dynamically generated according to the protocol characteristics, and finally the feasibility of the rules is verified to ensure that the data can be converted correctly.

[0090] In some embodiments, the determination of data conversion rules can be achieved in a variety of ways: optionally, the system can analyze protocol differences, first find rule templates, then configure conversion parameters, and finally verify the correctness of the rules and save the rule definitions; optionally, the system can also build a protocol mapping diagram, generate a conversion script, test the conversion effect, optimize the conversion performance and cache the conversion rules. It is understandable that other methods can also be used to determine data conversion rules, such as automatic generation through machine learning or expert system recommendation, which is not limited here.

[0091] It should be noted that the data conversion rule model in this application can be used to determine the data conversion rules; the data conversion rule model will analyze the data format differences and conversion requirements between different protocols during training, and collect various data conversion scenarios and corresponding processing rules. The training process focuses on the compatibility of the data format and the accuracy of the conversion to form a standardized conversion rule model. The data conversion rule model defines the data mapping relationship and conversion logic between different protocols, including rules such as data type conversion, format conversion, and encoding conversion. The model supports complex conversion scenarios, such as multi-level conversion, conditional conversion, etc. By inputting the data format definition of the source protocol and the target protocol, the data conversion rule model can output the corresponding conversion rules. During the interface call process, the system automatically completes the data format conversion according to these rules to ensure the correct transmission of data between different protocols.

[0092] S307. According to the data conversion rules, service ports and interface authentication settings, a corresponding calling code template is matched in the interface model library.

[0093] Among them, the calling code template represents a predefined code framework; the interface model library refers to a warehouse for storing various interface calling templates.

[0094] After determining the conversion rules, the interface management system needs to select a suitable code template. Specifically, the system first combines the data conversion rules, service ports, and authentication settings into query conditions, and then searches for code templates that meet the conditions in the interface model library. If multiple matches are found, they are sorted according to the matching degree, and finally the most suitable template is selected to prepare for subsequent code generation.

[0095] S308: Generate an interface calling code based on the parameter settings of the calling code template by the user.

[0096] Referring to step S104, the interface management system generates an interface calling code.

[0097] In some embodiments, the interface management system will also respond to the user's event binding operation, bind the task event to the target interface, and determine the triggering conditions of the task event; execute the task event when the target interface meets the triggering conditions; obtain the execution status of the task event, and update the task status field when the execution status changes.

[0098] Among them, the event binding operation represents the configuration process of the user setting the trigger action for the interface; the task event refers to the specific business operation that needs to be executed by the interface; the trigger condition represents the specific scenario or rule for starting the task event; the execution status represents the running status of the task event; and the task status field refers to the data item that records the execution status of the task.

[0099] When providing interface services, the interface management system needs to support event-based automated task processing. Specifically, the system first receives the user-defined event binding configuration, including event type, trigger conditions, and execution actions; then establishes an event monitoring mechanism to continuously detect the satisfaction of the trigger conditions; when the conditions are met, the corresponding task event is automatically executed; at the same time, the execution process of the task is tracked in real time, the changes in the execution status are recorded, and the status information is updated in a timely manner for query and monitoring.

[0100] For the interface management platform, see Figure 2 , Figure 2 A schematic diagram of a scenario of the interface automatic docking method in the embodiment of the present application; Figure 2 (d) shows the configuration diagram for adding tasks, which integrates the aforementioned data source configuration and interface configuration into an executable task unit. Through the user setting the task name, interface id, data configuration id, and number of execution threads, the interface management system can create and manage independent task instances, realize concurrent processing, and improve system processing efficiency; in addition, cron expressions can be used to configure the scheduled execution rules of tasks, support flexible scheduling strategies, and ensure that tasks are executed at the expected time. The completion of task configuration marks the establishment of a complete automated interface call process, providing a task execution environment for subsequent data reception configuration.

[0101] This event-driven task processing mechanism enables the system to automatically respond to various business scenarios, improving the automation level of interface services and business processing efficiency. Through real-time status tracking and updating, it also provides effective support for system monitoring and problem diagnosis. The design of the state management mechanism not only ensures the reliability of task execution, but also provides observability of task execution, which is helpful for system operation and maintenance management and performance optimization.

[0102] S309: Based on the interface calling code, the docking service of the target interface is packaged into a container image.

[0103] Among them, container image means packaging an application and its dependencies into a standardized unit; packaging process refers to the operation of encapsulating the interface call code and its operating environment into a container image; docking service means an independent service component that implements the interface call function.

[0104] After the interface management system generates the call code, it needs to be containerized to support flexible deployment. Specifically, the system first prepares the basic image environment, then copies the interface call code and related dependencies into the image, then configures runtime parameters and environment variables, adds health checks and monitoring configurations, and finally builds and saves the container image to the image repository.

[0105] S310. Deploy the container image in the container cluster so that the target interface runs in an independent environment.

[0106] Among them, the container cluster refers to the distributed system environment for managing and running containers; the deployment process refers to the operation of publishing the container image to the running environment; the independent environment refers to the isolated running space.

[0107] After the image is prepared, the interface management system needs to deploy it to the container cluster. Specifically, the system first selects the appropriate deployment node, then configures resource restrictions and network policies, then creates a container instance and injects configuration information, then sets service discovery and load balancing rules, and finally starts the container and verifies the service status.

[0108] In some embodiments, the deployment and operation of containers can be implemented in a variety of ways: optionally, the system can select the target node, create the deployment configuration and allocate computing resources, finally configure the network rules and start the container instance, and can also check the running status; optionally, the system can also generate a deployment list, set up service discovery by applying the configuration template, and configure the storage volume, and finally deploy the service instance and verify the service availability. It is understandable that other methods can also be used to implement the deployment of containers, such as through container orchestration tools or service grid frameworks, which are not limited here.

[0109] For the interface management platform, see Figure 2 , Figure 2 A schematic diagram of a scenario of the interface automatic docking method in the embodiment of the present application; Figure 2 (e) shows the configuration diagram for adding received data, which is the last configuration link of the entire interface automation docking process. Through the user setting the interface ID, data source ID and asynchronous execution button, the interface management system can establish a data receiving task, realize asynchronous data processing, and improve the concurrent processing capability of the system; in addition, the configuration current limiting option can be used to control the rate of data reception, prevent system overload, and ensure the stability of the overall service. The completion of these configurations makes the entire interface automation docking system form a complete closed loop, from data source configuration, interface configuration, task management to data reception, each link has been properly handled.

[0110] S311. Monitor the call load of the target interface and adjust the number of container instances according to the call load.

[0111] The call load indicates the request pressure borne by the interface service; the number of container instances refers to the number of container copies running the service.

[0112] The interface management system needs to continuously monitor and adjust the service scale during service operation. Specifically, the system first establishes multi-dimensional monitoring indicators, including request volume, response time, resource utilization, etc., and then collects and analyzes monitoring data in real time. When the load exceeds the threshold, the number of instances is automatically increased, and when the load is low, the number of instances is reduced to ensure elastic scaling of the service.

[0113] S312: When the interface configuration file of the target interface changes, update the interface calling code.

[0114] Referring to step S105, the interface management system will update the interface calling code in a timely manner.

[0115] The interface calling code represents the program code that implements the interface calling function.

[0116] During the operation and maintenance phase, the interface management system needs to keep the code and configuration updated synchronously. Specifically, the system first establishes a monitoring mechanism for configuration changes. When a configuration change is detected, the system obtains the latest configuration and analyzes the changes. Then, based on the scope of the change, it decides whether to use incremental updates or full updates. Finally, the code update is completed and the service is redeployed.

[0117] In some embodiments, configuration changes and code updates can be implemented in a variety of ways: Optionally, the system can monitor configuration changes, compare configuration differences, determine update strategies, regenerate update code and verify code correctness to implement hot update services; Optionally, the system can also subscribe to configuration events, deploy new versions by parsing configuration data, backing up existing code, and regenerating code. It is understandable that other methods can also be used to implement synchronous updates of configuration and code, such as through configuration center push or version control system, which is not limited here.

[0118] In the embodiment of the present application, due to the use of an automated docking method based on an interface model library, which integrates technologies such as a visual configuration interface, intelligent code generation, configuration change monitoring, and containerized deployment, it is possible to achieve automated processing of the entire process of interface docking, effectively solving the problems of traditional technologies that require a lot of manual coding, untimely configuration updates, and poor service scalability, thereby achieving the goal of high efficiency, low cost, and easy maintenance of interface docking. By analyzing historical call data through machine learning to predict load changes and combining the elastic scaling mechanism of the container cluster, the high availability and stability of the service can also be ensured. It not only greatly improves development efficiency and reduces maintenance costs, but also enhances the reliability and scalability of services, providing strong technical support for the digital transformation of enterprises.

[0119] The following describes the interface management system in the embodiment of the present invention from the perspective of hardware processing. Figure 4, which is a schematic diagram of a physical device structure of an interface management system in an embodiment of the present application.

[0120] It should be noted that Figure 4 The structure of the interface management system shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0121] like Figure 4 As shown, the interface management system includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 402 or the program loaded from the storage part 408 to the random access memory (RAM) 403, such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in the RAM 403. The CPU 401, ROM 402 and RAM 403 are connected to each other through a bus 404. The input / output (I / O) interface 405 is also connected to the bus 404.

[0122] The following components are connected to the I / O interface 405: an input section 406 including an audio input device, a button switch, etc.; an output section 407 including a liquid crystal display (LCD) and an audio output device, an indicator light, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 410 as needed so that a computer program read therefrom is installed into the storage section 408 as needed.

[0123] In particular, according to an embodiment of the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present invention includes a low-code development platform, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 409, and / or installed from the removable medium 411. When the computer program is executed by the central processing unit (CPU) 401, the various functions defined in the present invention are performed.

[0124] It should be noted that specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

[0125] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of the systems, methods, and low-code development platforms according to various embodiments of the present invention. Each box in the flowchart or block diagram may represent a module, a program segment, or a portion of a code, and the above module, program segment, or a portion of a code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the boxes may also occur in an order different from that marked in the accompanying drawings.

[0126] Specifically, the interface management system of this embodiment includes a processor and a memory. The memory stores a computer program. When the computer program is executed by the processor, the interface automatic docking method provided in the above embodiment is implemented.

[0127] As another aspect, the present invention further provides a computer-readable storage medium, which may be included in the interface management system described in the above embodiment; or may exist independently without being assembled into the interface management system. The above storage medium carries one or more computer programs, and when the above one or more computer programs are executed by a processor of the interface management system, the interface management system implements the interface automatic docking method provided in the above embodiment.

[0128] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0129] As used in the above embodiments, the term "when..." may be interpreted to mean "if..." or "after..." or "in response to determining..." or "in response to detecting...", depending on the context. Similarly, the phrases "upon determining..." or "if (the stated condition or event) is detected" may be interpreted to mean "if determining..." or "in response to determining..." or "upon detecting (the stated condition or event)" or "in response to detecting (the stated condition or event)", depending on the context.

[0130] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

Claims

1. An interface automation docking method, characterized in that: Applied to an interface management system, the method comprises: According to the interface connection request of the user, a target interface as a connection target is determined in the interface database; Obtaining an interface configuration file of the target interface including a service port, an interface transmission protocol, and an interface authentication setting; Generate a calling code template based on the service port, the interface transmission protocol and the interface authentication setting; Generate an interface calling code based on the parameter setting of the calling code template by the user; When the interface configuration file of the target interface changes, the interface calling code is updated.

2. The method according to claim 1, characterized in that The step of generating a calling code template based on the service port, the interface transmission protocol and the interface authentication setting specifically includes: Determine a request interface for issuing the interface docking request, and determine a target transmission protocol for the request interface; Determining data conversion rules according to the interface transmission protocol and the target transmission protocol; According to the data conversion rules, the service port and the interface authentication settings, a corresponding calling code template is matched in the interface model library.

3. The method according to claim 1, characterized in that Before the step of determining the target interface in the interface database as the docking target according to the interface docking request of the user, the method further includes: determining a target system based on a user selection, and displaying a plurality of interface models of the target system; An interface docking request is generated according to the option selection of the user in the multiple interface models.

4. The method according to claim 3, characterized in that After the step of generating an interface connection request according to the user's option selection in the plurality of interface models, the method further includes: Storing historical call records of the interface docking request to the target system; Performing model training based on multiple historical docking requests in the historical call records to generate a call prediction model; Determining a preset docking request of the target system according to the call prediction model; According to the preset docking request, a preset interface, preset parameter configuration and preset calling code for interface docking of the target system are generated.

5. The method according to claim 1, characterized in that After the step of generating the interface calling code based on the parameter setting of the calling code template by the user, the method further includes: Based on the interface calling code, packaging the docking service of the target interface into a container image; Deploy the container image in a container cluster so that the target interface runs in an independent environment; The call load of the target interface is monitored, and the number of container instances is adjusted according to the call load.

6. The method according to claim 1, characterized in that After the step of generating the interface calling code based on the parameter setting of the calling code template by the user, the method further includes: In response to the user's event binding operation, binding a task event to the target interface and determining a triggering condition of the task event; When the target interface meets the trigger condition, executing the task event; The execution status of the task event is obtained, and the task status field is updated when the execution status changes.

7. The method according to claim 1, characterized in that The step of determining a target interface in the interface database as a docking target according to the interface docking request of the user specifically includes: Based on the visual configuration interface, the preset interface models in the interface model library are displayed; receiving a drag operation of a user on the visual configuration interface and determining a target interface model; According to the configuration parameters of the target interface model, the corresponding target interface in the interface database is matched.

8. An interface management system, characterized in that: The interface management system includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the interface management system to execute the method described in any one of claims 1-7.

9. A computer-readable storage medium comprising instructions, characterized in that: When the instruction is executed on the interface management system, the interface management system is caused to execute the method according to any one of claims 1 to 7.

10. A low-code development platform, characterized in that: When the low-code development platform runs on the interface management system, the interface management system executes the method as described in any one of claims 1-7.

Images