A multi-service system interface integration and dynamic host automatic management method and system

Abstract

The present application relates to a method and system for multi-business system interface integration and dynamic host automatic management, which belongs to the field of information integration technology. The method includes: obtaining interface feature information of multiple business systems and performing feature extraction to obtain a preliminary interface feature set; logically labeling fields of the same type, generating a unified interface semantic model and defining data processing logic rules, and storing them in a logic policy rule base in combination with business policy logic rules; obtaining host node information in enterprise infrastructure resources; obtaining a host resource mapping table based on the logic policy rule base; generating a dynamic routing strategy and constructing a dynamic routing table; receiving external business requests in real time, obtaining interface names and searching for dynamic routing strategies in the dynamic routing table, and selecting a target host node; processing data streams of external business requests and routing them to the target host node. The present application can improve resource utilization of multi-business systems and ensure high availability.

Description

Technical Field

[0001] The present application relates to the field of information integration technology, and in particular to a method and system for multi-business system interface integration and dynamic host automatic management. Background Art

[0002] With the widespread application of information technology, enterprises usually use multiple information systems to handle different business needs in the process of management and operation, such as enterprise resource planning system (ERP), customer relationship management system (CRM), manufacturing execution system (MES), warehouse management system (WMS) and supply chain management system, etc. These business systems usually run independently to handle different types of business needs and data.

[0003] At present, in the process of enterprise operation, more and more business needs require efficient data interaction and integration between different systems. In order to achieve the collaborative work between these systems, enterprises often need to transmit data and share information through API interfaces.

[0004] However, there are large differences in interface standards, field names, data formats, and authentication methods between different business systems. When performing cross-system integration, the inconsistency of interfaces not only increases the complexity of system integration, but also may cause errors in data transmission, affecting the smooth operation of business processes. In addition, in the infrastructure resources of an enterprise, there are usually multiple host nodes, and the resources (such as CPU, memory, bandwidth, etc.) and load conditions of these nodes are different. When multiple interface services are running at the same time, how to dynamically deploy the interface service to the most suitable host node to improve the resource utilization of the system and ensure high availability has become a problem that needs to be solved urgently. Summary of the invention

[0005] In order to improve resource utilization of a multi-service system and ensure high availability, the present application provides a multi-service system interface integration and dynamic host automatic management method and system.

[0006] In a first aspect, the present application provides a method for multi-service system interface integration and dynamic host automatic management, which adopts the following technical solution:

[0007] Obtain interface feature information of multiple business systems and perform feature extraction to obtain a preliminary interface feature set;

[0008] Logically labeling the same type of fields in the preliminary interface feature set and adding extensible annotations to generate a unified interface semantic model;

[0009] Acquire business policy logic rules from the business system, define data processing logic rules based on the unified interface semantic model, and store the business policy logic rules and the data processing logic rules in a logic policy rule library;

[0010] Obtain host node information in enterprise infrastructure resources;

[0011] According to the host node information, the host node and the interface feature information are matched based on the logical policy rule base to obtain a host resource mapping table; wherein the host resource mapping table includes a mapping relationship between the interface name and the primary and backup host node lists;

[0012] Based on the host resource mapping table and the logic policy rule base, a dynamic routing policy is generated and a dynamic routing table is constructed;

[0013] Receiving external service requests in real time and obtaining the interface name of the external service requests;

[0014] According to the interface name in the external service request, searching the dynamic routing table for a corresponding dynamic routing policy, and selecting a target host node according to the dynamic routing policy;

[0015] The data flow of the external service request is processed based on the dynamic routing strategy, and the external service request is routed to the target host node.

[0016] By adopting the above technical solution, a complete interface integration and dynamic host management method is formed through feature extraction, semantic mapping, rule generation, host resource management and dynamic routing strategy of multi-business system interfaces. This technical solution effectively solves the problems of inconsistent interfaces, uneven resource allocation, and insufficient dynamic response capabilities among multi-business systems. Through the combination of logical strategy rule base and dynamic routing table, the automatic processing of interface requests and the dynamic allocation of target host nodes are realized, which significantly improves the flexibility, automation level and system reliability of multi-business system integration, and provides solid technical support for data interoperability and collaborative work in enterprise information construction.

[0017] Optionally, the business policy logic rules include host selection priority rules, event triggering rules and corresponding operation lists, and the host selection priority rules include resource demand matching rules, geographic location priority rules, load balancing rules and fault tolerance rules.

[0018] Optionally, the step of obtaining a host resource mapping table by matching host nodes and interface feature information based on the logical policy rule base according to the host node information includes:

[0019] Extracting the remaining available resources, geographical location and current load status of each host node according to the host node information;

[0020] Extracting interface requirement information corresponding to each interface name according to the interface feature information; wherein the interface requirement information includes interface resource requirements, geographical location requirements and data sensitivity level requirements;

[0021] Based on the resource requirement matching rule, the interface requirement information is matched with the remaining available resources of the host node one by one, and candidate host nodes that meet the interface resource requirements are screened;

[0022] Based on the geographic location priority rule, sorting the geographic location of each candidate host node according to the geographic location requirement to obtain a list of candidate host nodes;

[0023] Based on the load balancing rule, the candidate host nodes whose current load status exceeds a preset load threshold are eliminated from the candidate host node list to obtain a load-balanced candidate host node list;

[0024] Verifying the list of candidate host nodes after load balancing based on the data sensitivity level requirements, retaining the candidate host nodes that meet the data sensitivity level requirements, and obtaining a verified list of candidate host nodes;

[0025] From the verified candidate host node list, a primary and backup host node list is assigned to each interface name based on the fault tolerance rule to obtain a host resource mapping table; wherein the primary and backup host node list includes a primary node and at least one candidate node.

[0026] By adopting the above technical solutions, based on resource demand matching, geographic location priority, load balancing screening and sensitivity verification rules, intelligent matching and dynamic allocation of interfaces and host nodes are achieved to ensure that interface requests are supported by optimal resources. At the same time, through the allocation of primary and standby nodes, the fault tolerance and high availability of the system are enhanced. The overall technical solution takes into account performance optimization, security compliance and dynamic adaptation capabilities, providing reliable technical guarantees for the efficient integration and stable operation of multi-business systems.

[0027] Optionally, the step of searching a dynamic routing table for a corresponding dynamic routing policy according to the interface name in the external service request, and selecting a target host node according to the dynamic routing policy includes:

[0028] Searching the dynamic routing table for a dynamic routing policy associated with the interface name;

[0029] Extracting a list of primary and backup host nodes in the dynamic routing strategy;

[0030] Obtaining the load status of the master node and the candidate nodes in the master and standby host node list in real time;

[0031] Determine the corresponding preset load requirement according to the interface name in the external service request;

[0032] Determine whether the load state of the master node meets the preset load requirement;

[0033] If yes, the master node is used as the target host node;

[0034] If not, a candidate node that meets the preset load requirement and has the best load status is selected as the target host node.

[0035] By adopting the above technical solution, the routing strategy is quickly found according to the dynamic routing table, the load status of the primary and standby nodes is evaluated in real time, and dynamic node allocation is performed based on the preset load threshold and candidate node screening rules, thus achieving efficient processing of business requests and optimized resource allocation. This solution effectively improves the fault tolerance and high availability of the system, avoids service interruptions caused by node overload or failure, and maximizes resource utilization efficiency through real-time load monitoring and optimal node selection, providing reliable guarantee for dynamic response and stable operation in complex business scenarios.

[0036] Optionally, the step of performing data processing on the data flow of the external service request based on the dynamic routing strategy and routing the external service request to the target host node includes:

[0037] Extracting data processing logic rules associated with the interface name of the external business request according to the dynamic routing strategy; wherein the data processing logic rules include data format conversion rules, field mapping rules, data filtering rules and desensitization rules;

[0038] Standardizing the format of the data stream requested by the external service based on the data format conversion rule;

[0039] Traversing the data stream after format standardization, performing field structure conversion based on the field mapping rule, and obtaining a data stream after field mapping;

[0040] Traversing the data stream after the field mapping, filtering the data based on the data filtering rule to obtain a filtered data stream;

[0041] Traversing the filtered data stream, and performing desensitization processing on sensitive data in the data stream based on the desensitization rule;

[0042] Perform integrity check on the data stream after desensitization processing, and obtain the processed data stream after the check passes;

[0043] Determine the target host node address based on the dynamic routing strategy;

[0044] According to the target host node address, the processed data stream is sent to the target host node.

[0045] By adopting the above technical solution, the complete processing and reliable routing of external business request data flow is realized, ensuring that the data undergoes format conversion, field mapping, filtering, desensitization and integrity verification before entering the target host node, meeting the business needs of the target host node. This technical solution improves the standardization and security of data transmission and processing, significantly optimizes the overall performance and response speed of the system, and provides technical support for efficient integration in complex business scenarios.

[0046] Optionally, after the step of routing the external service request to the target host node, the step further includes:

[0047] Acquire the service request execution status of the target host node in real time;

[0048] According to the execution status of the service request, detecting the abnormal status of the target host node in real time;

[0049] When the target host node is in an abnormal state, a candidate node with the best load state is selected according to the dynamic routing strategy, and the unfinished external service request is rerouted to the candidate node.

[0050] By adopting the above technical solution, real-time monitoring and exception handling of the target host node are realized. When the target host node cannot process business requests normally due to response timeout, excessive load or abnormal health status, the system can quickly select the candidate node with the best load status based on the dynamic routing strategy, and reroute the unfinished business request to the node for execution. This solution significantly improves the system's fault tolerance, business process continuity and dynamic adaptability, and provides a strong guarantee for high availability and stability in complex business scenarios.

[0051] Optionally, after the step of routing the external service request to the target host node, the step further includes:

[0052] Receiving and responding to a service request processing completion feedback signal, collecting processing performance data of each target host node; wherein the processing performance data includes response time, success rate and state stability;

[0053] Calculating a performance score for each target host node based on the processing performance data based on a weighted scoring model;

[0054] The priority of the list of primary and backup host nodes in the dynamic routing table is dynamically adjusted according to the performance score to obtain an updated dynamic routing table.

[0055] By adopting the above technical solution, dynamic routing strategy optimization based on the performance of the target host node is realized. The system receives feedback signals, collects performance data such as response time, success rate and state stability, calculates node performance scores based on the weighted scoring model, and dynamically adjusts the priority of the primary and standby nodes accordingly. The updated dynamic routing table ensures that the nodes with the best performance are given priority service, and inefficient nodes are gradually downgraded or replaced, thereby improving the processing efficiency of business requests and the reliability of the system. This solution implements a routing strategy with strong dynamic adaptability and efficient response through a closed-loop optimization mechanism, providing robust technical support for high-performance allocation in complex multi-node scenarios.

[0056] In a second aspect, the present application provides a multi-service system interface integration and dynamic host automatic management system, which adopts the following technical solutions:

[0057] A multi-service system interface integration and dynamic host automatic management system, the system comprising:

[0058] The first acquisition module is used to acquire interface feature information of multiple business systems and perform feature extraction to obtain a preliminary interface feature set;

[0059] An information processing module, used to logically label the same type of fields in the preliminary interface feature set and add extensible annotations to generate a unified interface semantic model;

[0060] A logic rule integration module, used for acquiring business policy logic rules from a business system, defining data processing logic rules based on the unified interface semantic model, and storing the business policy logic rules and the data processing logic rules in a logic policy rule library;

[0061] The second acquisition module is used to obtain host node information in the enterprise infrastructure resources;

[0062] A host resource matching module, used to match the host node and interface feature information based on the logical policy rule base according to the host node information to obtain a host resource mapping table; wherein the host resource mapping table includes a mapping relationship between the interface name and the primary and backup host node lists;

[0063] A dynamic routing table construction module, used to generate a dynamic routing policy and construct a dynamic routing table based on the host resource mapping table and the logical policy rule base;

[0064] A service request receiving module, used to receive external service requests in real time and obtain the interface name of the external service request;

[0065] A target host node determination module, used to search the corresponding dynamic routing policy in the dynamic routing table according to the interface name in the external service request, and select the target host node according to the dynamic routing policy;

[0066] A data processing module, used for processing the data flow of the external service request based on the dynamic routing strategy;

[0067] The service request routing module is used to route the external service request to the target host node.

[0068] Optionally, the system further includes:

[0069] A processing performance data collection module, used to receive and respond to a service request processing completion feedback signal, and collect processing performance data of each target host node; wherein the processing performance data includes response time, success rate and state stability;

[0070] A performance score calculation module, used to calculate the performance score of each target host node according to the processing performance data based on a weighted scoring model;

[0071] The dynamic routing table updating module is used to dynamically adjust the priority of the list of primary and backup host nodes in the dynamic routing table according to the performance score to obtain an updated dynamic routing table.

[0072] Optionally, the system further includes:

[0073] An execution status acquisition module, used to acquire the execution status of the service request of the target host node in real time;

[0074] An abnormal state detection module, used to detect the abnormal state of the target host node in real time according to the execution state of the service request;

[0075] The dynamic routing module is used to select a candidate node with the best load status according to the dynamic routing strategy when the target host node is in an abnormal state, and reroute the unfinished external service request to the candidate node.

[0076] To summarize, the present application includes at least one of the following beneficial technical effects: The technical solution of the present application is of great significance in the field of enterprise informatization, especially in supporting complex business scenarios, multi-node collaboration and global deployment. It provides technical support for enterprises to build flexible and efficient multi-business system integration. At the same time, it significantly reduces resource waste and the cost of manual intervention through automated host management. It can be applied to cloud computing, big data and modern distributed system scenarios, helping enterprises to achieve more efficient resource utilization, faster response time and more stable service delivery, and providing a solid foundation for informatization transformation and intelligent development. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] Figure 1 This is a first flow chart of a method for multi-business system interface integration and dynamic host automatic management according to one of the embodiments of the present application.

[0078] Figure 2 This is a second flow chart of a method for multi-business system interface integration and dynamic host automatic management according to one of the embodiments of the present application.

[0079] Figure 3 This is a third flow chart of a method for multi-business system interface integration and dynamic host automatic management according to one of the embodiments of the present application.

[0080] Figure 4 This is a fourth flow chart of a method for multi-business system interface integration and dynamic host automatic management according to one of the embodiments of the present application.

[0081] Figure 5 This is a fifth flow chart of a method for multi-business system interface integration and dynamic host automatic management according to one of the embodiments of the present application.

[0082] Figure 6 This is a sixth flow chart of a method for multi-business system interface integration and dynamic host automatic management according to one of the embodiments of the present application. DETAILED DESCRIPTION

[0083] In order to make the purpose, technical solutions and advantages of this application more clear, the following Figure 1-6 It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0084] At present, in the integration of multi-business systems, the interface characteristics and data standards of different systems (such as ERP, CRM, MES, etc.) often differ greatly, which poses a great challenge to the collaborative work of internal enterprise systems. At the same time, as enterprise IT infrastructure develops towards cloud computing, virtualized architecture and distributed systems, dynamic management of host node resource allocation, interface processing and request routing has become the key. Since the traditional static allocation method is difficult to meet the requirements of dynamic load, real-time response and high availability, a systematic solution that can automatically realize interface integration, resource matching and dynamic routing is urgently needed.

[0085] Based on this, an embodiment of the present application discloses a method for multi-service system interface integration and dynamic host automatic management.

[0086] Reference Figure 1 , a multi-service system interface integration and dynamic host automatic management method includes:

[0087] Step S101, obtaining interface feature information of multiple business systems and performing feature extraction to obtain a preliminary interface feature set;

[0088] Among them, interface feature information includes interface name, interface requirement information, data format, field structure, authentication method and basic service quality indicators (such as response time, available bandwidth), etc. Interface requirement information includes interface resource requirements, geographical location requirements and data sensitivity level requirements.

[0089] In some embodiments, the interface feature information of multiple business systems already exists in the enterprise, such as ERP, CRM, MES, WMS, supply chain, etc. The system batch-captures the interface feature information from the registered interface list of each business system, analyzes the input and output fields of each interface using a predefined field parser, extracts information such as its data type, field meaning, and authentication method, and represents the interface features of each business system in a unified format (such as a JSON meta file) to generate a preliminary interface feature set.

[0090] For example, the ERP system provides an API interface for obtaining inventory information. The data returned by this interface includes fields such as inventory quantity and inventory location. The system extracts features from these fields and records their names, types (such as integer, string), field purposes, etc.

[0091] Step S102, logically labeling the same type of fields in the preliminary interface feature set and adding extensible annotations to generate a unified interface semantic model;

[0092] Among them, the unified interface semantic model is a field logic mapping dictionary that is common across systems. It contains the semantic equivalence relationship, data sensitivity, scope of application and mapping priority between fields. It is used to provide a reference for consistency between fields for subsequent rule generation. For example, "customer_id of CRM" should be logically synonymous with "client_id of ERP".

[0093] Specifically, using semantic mapping and logical annotation engines, fields of the same type (such as customer ID, order number, inventory quantity, etc.) are uniformly logically labeled to lay the foundation for subsequent rule definition. At the same time, extensible annotations are added to the field set, such as data sensitivity level (high / medium / low), regional applicability tags (local / multinational), and potential mapping priorities (such as ERP fields are primary fields and CRM fields are secondary fields).

[0094] For example, assuming that the field name in the ERP system is "client_id" and the field name used in the CRM system is "customer_id", logical labeling marks these two fields as "customer ID" with the same semantics, and adds business priority annotations to mark the data in the ERP system as master data.

[0095] Step S103, obtaining business policy logic rules from the business system, defining data processing logic rules based on the unified interface semantic model, and storing the business policy logic rules and data processing logic rules in a logic policy rule library;

[0096] Among them, business policy logic rules include host selection priority rules, event triggering rules and corresponding operation lists; data processing logic rules include data format conversion rules (such as date format conversion, string encoding conversion), field mapping rules (such as ERP's client_id is mapped to CRM's customer_id), data filtering and desensitization rules.

[0097] In one of the embodiments of the present application, a business policy (such as cross-border data transmission desensitization, order processing priority, etc.) is received from a business system, and the business policy is converted into a machine-readable logic rule, and an event trigger condition is defined; for example, "cross-border data transmission" is mapped as a trigger condition, and the data desensitization rule is applied when this condition is met.

[0098] For example, the supply chain management system requires that customer information be desensitized before being transmitted to an external system. The data desensitization logic rules can be defined according to the unified interface semantic model, and the customer ID can be partially masked and stored in the policy rule library for subsequent automatic execution.

[0099] Step S104, obtaining host node information in the enterprise infrastructure resources;

[0100] Among them, the available host node information in the enterprise IT infrastructure is obtained, including the type of host node (such as physical server, virtual machine, container cluster), geographical location, available resources (CPU, memory, bandwidth, etc.) and load conditions. These host nodes are the actual execution carriers of interface service deployment.

[0101] For example, an enterprise usually has multiple data centers in different geographical locations, each of which contains several virtual machine clusters. The current load conditions of these host nodes are obtained to determine the optimal resource allocation solution.

[0102] Step S105, according to the host node information, matching the host node and the interface feature information based on the logic policy rule base, to obtain a host resource mapping table; wherein the host resource mapping table includes a mapping relationship between the interface name and the active and standby host node lists;

[0103] Specifically, in the logical policy rule base, according to the host selection priority rules defined by the business policy logic rules, combined with the acquired host node information, the interface feature information and the host node can be matched to generate a host resource mapping table. The mapping table indicates the list of primary and backup host nodes to which each interface can be assigned, and is sorted according to load, geographical location and resource requirements. The list of primary and backup host nodes includes a primary node and at least one backup node, and the backup node is used for primary node failover.

[0104] Exemplarily, assuming that an interface has a high priority requirement and processes a large amount of data, it is preferentially mapped to a host node with sufficient resources and the closest geographical location, and alternative nodes are recorded to cope with load or node failure.

[0105] It can be understood that the generation of the host resource mapping table enables the system to allocate appropriate host nodes to different interfaces, ensure the reliability and load balancing of the system, and improve resource utilization and availability of interface services.

[0106] Step S106, generating a dynamic routing strategy and constructing a dynamic routing table based on the host resource mapping table and the logic policy rule base;

[0107] Specifically, according to the rules in the host resource mapping table and the logic policy rule base, a dynamic routing policy for the interface request is generated, and a dynamic routing table is constructed, wherein the dynamic routing table includes the interface name, data processing requirements, target host node selection, and fault candidate host node information.

[0108] It should be noted that the dynamic routing strategy generated based on the host resource mapping table and the logical strategy rule base includes the list of primary and backup host nodes (list of primary nodes and backup nodes), data processing logic rules (such as data format mapping requirements, data filtering and desensitization rules), and host node switching rules (automatically switching to backup nodes under high load). In addition, after the dynamic routing strategy is synthesized, the dynamic routing table can be stored in a quickly accessible in-memory database so that the orchestration engine at runtime can query and update it in real time.

[0109] Step S107, receiving an external service request in real time, and obtaining an interface name of the external service request;

[0110] Among them, the service request from the outside is received in real time, and the interface name is obtained by parsing the request content, so as to perform further processing according to the corresponding routing table. For example, the inventory query request from the client contains the name of the target interface "inventory_query", and the system parses the request to obtain the interface name.

[0111] Step S108, searching the dynamic routing table for a corresponding dynamic routing policy according to the interface name in the external service request, and selecting a target host node according to the dynamic routing policy;

[0112] Specifically, when an external service request arrives, the corresponding dynamic routing policy can be found in the dynamic routing table according to the interface name, and the optimal host node is selected as the target node based on the dynamic routing policy for data processing and request response.

[0113] It can be understood that by dynamically selecting the target host node, it is ensured that the request receives the best resource support, avoiding service interruptions due to host node load or unavailability, and enhancing the system's high availability and load balancing capabilities.

[0114] Step S109: Process the data flow of the external service request based on the dynamic routing strategy, and route the external service request to the target host node.

[0115] Specifically, the data processing logic rules in the dynamic routing strategy are called to process the data flow of external business requests, including data format conversion rules, field mapping rules, data filtering and desensitization rules, etc. After processing, the business request is routed to the selected target host node for execution to ensure that the data flow completes the necessary adaptation when entering the target host node.

[0116] It can be understood that the execution of data processing logic ensures the consistency of data formats between different systems, ensures that requests can be executed correctly, and the correct processing and rapid routing of data streams to the target host node improves the overall performance and response speed of the system.

[0117] In the above implementation, a complete interface integration and dynamic host management method is formed through feature extraction, semantic mapping, rule generation, host resource management and dynamic routing strategy of multi-business system interfaces. This technical solution effectively solves the problems of inconsistent interfaces, uneven resource allocation, and insufficient dynamic response capabilities among multi-business systems. Through the combination of logical strategy rule base and dynamic routing table, the automatic processing of interface requests and the dynamic allocation of target host nodes are realized, which significantly improves the flexibility, automation level and system reliability of multi-business system integration, and provides solid technical support for data intercommunication and collaborative work in enterprise information construction.

[0118] In one of the embodiments of the present application, the host selection priority rules include resource demand matching rules, geographic location priority rules, load balancing rules and fault tolerance rules. Specifically, the resource demand matching rule is to select a host node that can meet the requirements based on the CPU, memory and bandwidth requirements of the interface; the geographic location priority rule is to give priority to the host node with the closest geographical location based on the request source or business area; the load balancing rule is to avoid assigning the interface to a high-load node and give priority to the node with a lower current load; the fault tolerance rule is to select at least one alternative node for each interface for primary node failover.

[0119] Reference Figure 2 As an implementation method of step S105, according to the host node information, the step of matching the host node and the interface feature information based on the logical policy rule library to obtain the host resource mapping table includes:

[0120] Step S201, extracting the remaining available resources, geographical location and current load status of each host node according to the host node information;

[0121] Among them, host node information is obtained from the enterprise resource database, including the remaining available resources (CPU, memory, bandwidth, etc.), geographical location and current load status of each host node. This data provides the static capabilities and real-time status of the host node, forming a list of resources that can be analyzed and matched, ensuring that subsequent steps can accurately make decisions based on the capabilities and status of the nodes.

[0122] Step S202, extracting interface requirement information corresponding to each interface name according to the interface feature information;

[0123] Among them, the interface requirement information includes interface resource requirements, geographical location requirements and data sensitivity level requirements;

[0124] Specifically, interface requirement information is extracted from the interface feature information, including interface resource requirements (such as CPU, memory, bandwidth), geographical location requirements (such as "Asia priority"), and data sensitivity level requirements (such as "high sensitivity"). This information is a direct expression of the resources and constraints required for interface operation.

[0125] It is understandable that by clarifying the resource needs and special requirements of interface operation, the necessary basis is provided for resource allocation to avoid allocation errors due to insufficient information.

[0126] Step S203, based on the resource requirement matching rule, matching the interface requirement information with the remaining available resources of the host node one by one, and screening candidate host nodes that meet the interface resource requirements;

[0127] Among them, the interface resource requirements are compared with the remaining available resources of the host node one by one, and the nodes that cannot meet the requirements are eliminated. Only candidate host nodes that meet the resource requirements are retained to ensure that the resources required for interface operation can be met, preliminarily narrow the scope of candidate host nodes, and reduce the computational complexity of subsequent steps.

[0128] Step S204, based on the geographical location priority rule, sort the geographical location of each candidate host node according to the geographical location requirements to obtain a list of candidate host nodes;

[0129] Among them, according to the geographical location requirements of the interface, the distance between the candidate host node and the target geographical location is calculated, and the distance is sorted from near to far to give priority to the node with the closest geographical location, reduce network transmission delay, and improve interface response speed.

[0130] Step S205, based on the load balancing rule, remove the candidate host nodes whose current load status exceeds the preset load threshold in the candidate host node list, and obtain a load-balanced candidate host node list;

[0131] Among them, the real-time load status of the candidate host nodes is checked, and the nodes whose current load status exceeds the preset threshold are eliminated, and only the nodes with normal load are retained to avoid the degradation of interface operation performance due to excessive node load, further ensuring the stability and reliability of the system.

[0132] Step S206, verifying the candidate host node list after load balancing based on the data sensitivity level requirement, retaining the candidate host nodes that meet the data sensitivity level requirement, and obtaining a verified candidate host node list;

[0133] Among them, according to the sensitivity level requirements of the interface, only candidate host nodes that meet the data security requirements are retained; for example, highly sensitive interfaces need to be deployed on host nodes with high security levels to ensure that sensitive data is properly protected, meets security and compliance requirements, and avoids business risks caused by data leakage.

[0134] Step S207, from the verified candidate host node list, assign a primary and backup host node list to each interface name based on the fault tolerance rule to obtain a host resource mapping table; wherein the primary and backup host node list includes a primary node and at least one candidate node.

[0135] Specifically, a master node is selected from the verified candidate host nodes, and at least one candidate node is allocated according to the fault tolerance rule (such as giving priority to nodes in different physical areas to ensure fault tolerance).

[0136] It should be noted that the selection of the master node can be based on load priority, geographical location priority and security level priority, with priority given to nodes with lower load, closest to the geographical location requirements of the interface and meeting the interface sensitivity level requirements.

[0137] In one embodiment of the present application, the structure of the host resource mapping table includes: interface name, primary node information (including node type, geographical location, resource allocation) and candidate node information (including node type, geographical location, resource allocation). In addition, the mapping table can be stored in a key-value pair format to support efficient query and dynamic update.

[0138] In the above implementation, based on resource demand matching, geographic location priority, load balancing screening and sensitivity verification, intelligent matching and dynamic allocation of interfaces and host nodes are achieved to ensure that interface requests are supported by optimal resources. At the same time, through the allocation of primary and standby nodes, the fault tolerance and high availability of the system are enhanced. The overall technical solution takes into account performance optimization, security compliance and dynamic adaptation capabilities, providing reliable technical guarantees for the efficient integration and stable operation of multi-business systems.

[0139] Reference Figure 3 As an implementation method of step S108, the steps of searching the dynamic routing table for the corresponding dynamic routing policy according to the interface name in the external service request, and selecting the target host node according to the dynamic routing policy include:

[0140] Step S301, searching the dynamic routing table for a dynamic routing policy associated with the interface name;

[0141] When an external service request arrives, it is quickly searched in the dynamic routing table according to the interface name it contains. The dynamic routing table stores the mapping relationship between the interface name and its corresponding dynamic routing policy. This operation is intended to locate the routing policy information required for the request.

[0142] Step S302, extracting the list of primary and backup host nodes in the dynamic routing policy;

[0143] Among them, the list of primary and backup nodes is extracted from the dynamic routing strategy, including the primary node and the backup node, to clarify the primary processing node and fault-tolerant backup solution for interface requests. The primary node is the node that preferentially carries the service request, and the backup node is the replacement node used when the primary node is unavailable or overloaded.

[0144] Step S303, obtaining the load status of the master node and the candidate node in the master and standby host node list in real time;

[0145] Among them, the monitoring system is used to query the operating status of the active and standby nodes in real time (such as CPU utilization, memory utilization, and bandwidth utilization), obtain the latest load information of each node, and provide real-time data support for node selection.

[0146] Step S304, determining the corresponding preset load requirement according to the interface name in the external service request;

[0147] Among them, the characteristics of each interface (such as data volume, processing complexity, real-time requirements, etc.) directly determine the demand for target host node resources. These demands are defined in the logical policy rule base with preset load demand standards, which may include CPU utilization thresholds, memory utilization thresholds, and bandwidth utilization thresholds.

[0148] For example, for compute-intensive interfaces, such as interfaces for data analysis or complex logic processing, the demand for CPU resources is relatively high; for memory-intensive interfaces, such as interfaces for large-scale data caching or storage, the demand for memory is relatively high; for network-intensive interfaces, such as interfaces for file upload and download or high-frequency communication, the demand for bandwidth is relatively high.

[0149] Step S305, determining whether the load state of the master node meets the preset load requirement;

[0150] Among them, the real-time load status of the main node is compared with the preset load requirement of the interface to determine whether the main node is suitable to continue to serve as the target node to carry business requests. By comparing the status of the main node with the preset load requirement of the interface one by one, it is checked whether all the preset conditions are met.

[0151] If yes, jump to step S306; if no, jump to step S307;

[0152] Step S306, taking the master node as the target host node;

[0153] Among them, through load threshold judgment, if all status parameters of the master node meet the preset load requirements of the interface, the master node can continue to carry requests as the target node, and ensure that the master node operates within a safe load range to avoid performance degradation or service interruption caused by overload.

[0154] Step S307: Select a candidate node that meets the preset load requirement and has the best load status as the target host node.

[0155] If the load of the main node exceeds the limit, based on the real-time load status of the candidate nodes, the candidate node that meets the preset load requirements and has the best load status is automatically selected as the target host node. The node with the best load status refers to the node with the lowest resource utilization (CPU, memory, bandwidth utilization).

[0156] Exemplarily, for the interface "inventory_query", the corresponding main node found in the dynamic routing table is "node A", but if the current load of node A is too high, the system can automatically select alternative node B as the target host node based on the load status according to the alternative node list.

[0157] In the above implementation, the routing strategy is quickly searched according to the dynamic routing table, the load status of the primary and standby nodes is evaluated in real time, and dynamic node allocation is performed based on the preset load requirements and candidate node screening rules, thereby achieving efficient processing of business requests and optimized resource allocation. This solution effectively improves the fault tolerance and high availability of the system, avoids service interruptions caused by node overload or failure, and maximizes resource utilization efficiency through real-time load monitoring and optimal node selection, providing reliable guarantees for dynamic response and stable operation in complex business scenarios.

[0158] Reference Figure 4 As an implementation method of step S109, the step of processing the data flow of the external service request based on the dynamic routing strategy and routing the external service request to the target host node includes:

[0159] Step S401, extracting data processing logic rules associated with the interface name of the external service request according to the dynamic routing strategy;

[0160] Among them, data processing logic rules include data format conversion rules, field mapping rules, data filtering rules and desensitization rules;

[0161] Step S402, standardizing the format of the data stream requested by the external service based on the data format conversion rule;

[0162] Among them, according to the data format conversion rules in the dynamic routing strategy, the request data stream is converted into a standard format that can be correctly recognized and parsed by the target host node to eliminate the differences in data structure and ensure that the data is consistent with the expected format of the target host node.

[0163] Step S403, traversing the data stream after the format standardization, performing field structure conversion based on the field mapping rule, and obtaining a data stream after the field mapping is completed;

[0164] According to the field mapping rules in the dynamic routing strategy, the field names and structures in the data stream are mapped to the field formats required by the target host node.

[0165] Step S404, traversing the data stream after field mapping, filtering the data based on the data filtering rule, and obtaining the filtered data stream;

[0166] Among them, records or fields that do not meet the conditions in the data stream are eliminated according to data filtering rules to reduce unnecessary load and optimize the accuracy of the data stream.

[0167] Step S405, traversing the filtered data stream, and performing desensitization processing on sensitive data in the data stream based on desensitization rules;

[0168] Among them, sensitive information in the data flow is processed according to desensitizing rules to ensure security and privacy protection during data transmission and processing.

[0169] Step S406, performing integrity check on the desensitized data stream, and obtaining the processed data stream after the check passes;

[0170] After the data stream is processed, the integrity of the data is checked according to the requirements of the target host node to ensure that the data meets the field integrity and format correctness. For example, check whether the required fields exist, check whether the field values ​​conform to the expected format (such as request_date is in date format), and mark or repair records with missing fields or incorrect formats.

[0171] Step S407, determining the target host node address based on the dynamic routing strategy;

[0172] Step S408, sending the processed data stream to the target host node according to the address of the target host node.

[0173] Among them, according to the target host node address specified in the dynamic routing strategy, the processed data stream is transmitted to the target host node to start the business processing process.

[0174] In the above implementation, the complete processing and reliable routing of external business request data streams are achieved, ensuring that the data undergoes format conversion, field mapping, filtering, desensitization, and integrity verification before entering the target host node, thus meeting the business needs of the target host node. This technical solution improves the standardization and security of data transmission and processing, significantly optimizes the overall performance and response speed of the system, and provides technical support for efficient integration in complex business scenarios.

[0175] Reference Figure 5 As a further implementation of the present application, after the step of routing the external service request to the target host node, the method further includes:

[0176] Step S501, obtaining the service request execution status of the target host node in real time;

[0177] Among them, the current business request execution status of the target host node is obtained through the real-time monitoring mechanism, including execution progress (completion percentage of business request processing), processing load (CPU, memory and bandwidth utilization), response delay (the time from request sending to response receiving) and health status (whether the node is operating normally), so as to fully understand the node operation status.

[0178] Step S502, detecting the abnormal state of the target host node in real time according to the execution state of the service request;

[0179] Specifically, according to the preset abnormal judgment conditions, the collected status data is checked one by one to determine whether the following abnormal conditions exist: response timeout (node ​​response time exceeds the preset threshold), excessive load (CPU, memory or bandwidth utilization exceeds the set threshold), node unavailability (health status is marked as unhealthy or no response for multiple consecutive times). If the abnormal judgment conditions are met, an abnormal event is generated and the current target host node is marked as an abnormal state.

[0180] Step S503: When the target host node is in an abnormal state, a candidate node with the best load state is selected according to a dynamic routing strategy, and the unfinished external service request is rerouted to the candidate node.

[0181] Among them, when the target host node is judged to be abnormal, based on the dynamic routing strategy, the node with the best load status is selected from the candidate node list as the new target node, and the detailed information of the current unfinished external business request (such as request ID, data content, execution progress, etc.) is obtained, the dynamic routing strategy is called, a new request package is constructed, and the unfinished request is resent to the new target host node.

[0182] It should be noted that the candidate node with the best load status (lowest resource utilization) is selected first. If multiple candidate nodes have the same load status, the candidate node with the closest geographical location to the request source is selected.

[0183] In the above implementation, real-time monitoring and exception handling of the target host node are realized. When the target host node cannot process the service request normally due to response timeout, excessive load or abnormal health status, the system can quickly select the candidate node with the best load status based on the dynamic routing strategy, and reroute the unfinished service request to the node for execution. This solution significantly improves the system's fault tolerance, business process continuity and dynamic adaptability, and provides a strong guarantee for high availability and stability in complex business scenarios.

[0184] Reference Figure 6 As a further implementation of the present application, after the step of routing the external service request to the target host node, the method further includes:

[0185] Step S601, receiving and responding to a service request processing completion feedback signal, collecting processing performance data of each target host node; wherein the processing performance data includes response time, success rate and state stability;

[0186] Specifically, after the target host node completes the business processing, it returns a feedback signal, which includes the request status (success / failure), processing time (response time), and status information during the execution process (such as node load, resource usage). The system extracts key performance indicator data from the feedback signal of the target host node, including response time, success rate, and status stability, and collects and stores them uniformly.

[0187] Among them, the response time is the time from the request being sent to the response being received; the success rate is the ratio of the number of requests successfully processed by the target host node within a certain time window to the total number of requests; and the state stability is the number of consecutive successful processing times of the target node within a period of time.

[0188] Step S602, calculating the performance score of each target host node according to the processing performance data based on the weighted scoring model;

[0189] Among them, through the weighted scoring model, multiple performance data indicators (response time, success rate, state stability) are integrated into a performance score, which intuitively reflects the overall performance of the target host node.

[0190] For example, the weight of each processing performance data can be pre-configured, for example, the weight of response time is 40%, and the shorter the response time, the higher the score; the weight of success rate is 50%, and the higher the success rate, the higher the score; the weight of state stability is 10%, and the more consecutive success times, the higher the score. By substituting the collected processing performance data and weight ratio into the pre-built weighted scoring model, the corresponding performance scoring result can be obtained;

[0191] Step S603: dynamically adjust the priority of the list of primary and backup host nodes in the dynamic routing table according to the performance score to obtain an updated dynamic routing table.

[0192] Among them, according to the performance score of the target host node, the priority of the primary and backup host nodes in the dynamic routing table is dynamically adjusted to ensure that the node with a high performance score processes the request first.

[0193] Specifically, the target host nodes are sorted according to the performance scores, the node with the highest performance score is set as the primary node, and the nodes with the second highest scores are set as backup nodes in turn, and the priority of the primary and backup node list is updated in the dynamic routing table to ensure that subsequent business requests can be allocated according to the latest optimized routing strategy.

[0194] In the above implementation, dynamic routing strategy optimization based on the performance of the target host node is implemented. The system receives feedback signals, collects performance data such as response time, success rate and state stability, calculates node performance scores based on a weighted scoring model, and dynamically adjusts the priority of the primary and standby nodes accordingly. The updated dynamic routing table ensures that the nodes with the best performance are given priority service, and inefficient nodes are gradually downgraded or replaced, thereby improving the processing efficiency of business requests and the reliability of the system. This solution implements a routing strategy with strong dynamic adaptability and efficient response through a closed-loop optimization mechanism, providing robust technical support for high-performance allocation in complex multi-node scenarios.

[0195] The embodiment of the present application also discloses a multi-business system interface integration and dynamic host automatic management system.

[0196] A multi-service system interface integration and dynamic host automatic management system, the system includes:

[0197] The first acquisition module is used to acquire interface feature information of multiple business systems and perform feature extraction to obtain a preliminary interface feature set;

[0198] An information processing module is used to logically label the same type of fields in the preliminary interface feature set and add extensible annotations to generate a unified interface semantic model;

[0199] The logic rule integration module is used to obtain the business policy logic rules from the business system, define the data processing logic rules based on the unified interface semantic model, and store the business policy logic rules and data processing logic rules in the logic policy rule library;

[0200] The second acquisition module is used to obtain the host node information in the enterprise infrastructure resources;

[0201] A host resource matching module is used to match the host node and interface feature information based on the host node information and the logical policy rule base to obtain a host resource mapping table; wherein the host resource mapping table includes a mapping relationship between the interface name and the list of primary and backup host nodes;

[0202] A dynamic routing table building module is used to generate dynamic routing policies and build dynamic routing tables based on a host resource mapping table and a logic policy rule base;

[0203] The service request receiving module is used to receive external service requests in real time and obtain the interface name of the external service request;

[0204] The target host node determination module is used to search the corresponding dynamic routing policy in the dynamic routing table according to the interface name in the external service request, and select the target host node according to the dynamic routing policy;

[0205] A data processing module is used to process the data stream of external business requests based on a dynamic routing strategy;

[0206] The service request routing module is used to route external service requests to the target host node.

[0207] In the above implementation, modular design is used to achieve full process automation from interface feature extraction, unified semantic model construction, to logic rule integration, dynamic matching of host nodes, request processing and routing. This not only solves the problem of inconsistent interfaces between multiple business systems, but also dynamically adjusts host resource allocation to ensure efficient load balancing and fault tolerance. The dynamic routing strategy constructed by this solution can adapt to external request changes in real time, improve the consistency and security of data processing and the reliability of target node selection, thereby greatly improving the overall performance and business continuity of the system.

[0208] As a further implementation of the embodiment of the present application, the system further includes:

[0209] A processing performance data collection module is used to receive and respond to the service request processing completion feedback signal, and collect the processing performance data of each target host node; wherein the processing performance data includes response time, success rate and state stability;

[0210] A performance score calculation module, used to calculate the performance score of each target host node according to the processing performance data based on a weighted scoring model;

[0211] The dynamic routing table update module is used to dynamically adjust the priority of the primary and backup host node lists in the dynamic routing table according to the performance score to obtain an updated dynamic routing table.

[0212] In the above implementation, through real-time monitoring and exception handling of the target host node, when the target host node is unable to process business requests normally due to response timeout, excessive load or abnormal health status, the system can quickly select an alternative node with the best load status based on a dynamic routing strategy, and reroute the unfinished business request to the node for execution.

[0213] As a further implementation of the embodiment of the present application, the system further includes:

[0214] An execution status acquisition module is used to obtain the business request execution status of the target host node in real time;

[0215] The abnormal state detection module is used to detect the abnormal state of the target host node in real time according to the execution state of the business request;

[0216] The dynamic routing module is used to select an alternative node with the best load status according to the dynamic routing strategy when the target host node is in an abnormal state, and reroute the unfinished external business requests to the alternative node.

[0217] In the above implementation, the system receives feedback signals, collects performance data such as response time, success rate and state stability, calculates node performance scores based on a weighted scoring model, and dynamically adjusts the priority of the primary and backup nodes accordingly. The updated dynamic routing table ensures that the nodes with the best performance are given priority service, and inefficient nodes are gradually downgraded or replaced, thereby improving the processing efficiency of business requests and the reliability of the system.

[0218] A multi-business system interface integration and dynamic host automatic management system of an embodiment of the present application can implement any of the above-mentioned multi-business system interface integration and dynamic host automatic management methods, and the specific working process of each module in the multi-business system interface integration and dynamic host automatic management system can refer to the corresponding process in the above-mentioned method embodiment.

[0219] In the several embodiments provided in this application, it should be understood that the provided methods and systems can be implemented in other ways. For example, the system embodiments described above are only illustrative; for example, the division of a certain module is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed.

[0220] It should be noted that in the above embodiments, the description of each embodiment has different emphases, and for parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0221] The above are all preferred embodiments of the present application, and are not intended to limit the protection scope of the present application. Any feature disclosed in this specification (including the abstract and drawings), unless otherwise stated, can be replaced by other equivalent or alternative features with similar purposes. That is, unless otherwise stated, each feature is only an example of a series of equivalent or similar features.

Claims

1. A method for multi-service system interface integration and dynamic host automatic management, characterized in that: The method comprises: Obtain interface feature information of multiple business systems and perform feature extraction to obtain a preliminary interface feature set; Logically labeling the same type of fields in the preliminary interface feature set and adding extensible annotations to generate a unified interface semantic model; Acquire business policy logic rules from the business system, define data processing logic rules based on the unified interface semantic model, and store the business policy logic rules and the data processing logic rules in a logic policy rule library; Obtain host node information in enterprise infrastructure resources; According to the host node information, the host node and the interface feature information are matched based on the logical policy rule base to obtain a host resource mapping table; wherein the host resource mapping table includes a mapping relationship between the interface name and the primary and backup host node lists; Based on the host resource mapping table and the logic policy rule base, a dynamic routing policy is generated and a dynamic routing table is constructed; Receiving external service requests in real time and obtaining the interface name of the external service requests; According to the interface name in the external service request, searching the dynamic routing table for a corresponding dynamic routing policy, and selecting a target host node according to the dynamic routing policy; The data flow of the external service request is processed based on the dynamic routing strategy, and the external service request is routed to the target host node.

2. A method for multi-service system interface integration and dynamic host automatic management according to claim 1, characterized in that: The business policy logic rules include host selection priority rules, event triggering rules and corresponding operation lists. The host selection priority rules include resource demand matching rules, geographic location priority rules, load balancing rules and fault tolerance rules.

3. A method for multi-service system interface integration and dynamic host automatic management according to claim 2, characterized in that: According to the host node information, the step of matching the host node and the interface feature information based on the logical policy rule base to obtain the host resource mapping table includes: Extracting the remaining available resources, geographical location and current load status of each host node according to the host node information; Extracting interface requirement information corresponding to each interface name according to the interface feature information; wherein the interface requirement information includes interface resource requirements, geographical location requirements and data sensitivity level requirements; Based on the resource requirement matching rule, the interface requirement information is matched with the remaining available resources of the host node one by one, and candidate host nodes that meet the interface resource requirements are screened; Based on the geographic location priority rule, sorting the geographic location of each candidate host node according to the geographic location requirement to obtain a list of candidate host nodes; Based on the load balancing rule, the candidate host nodes whose current load status exceeds a preset load threshold are eliminated from the candidate host node list to obtain a load-balanced candidate host node list; Verifying the list of candidate host nodes after load balancing based on the data sensitivity level requirements, retaining the candidate host nodes that meet the data sensitivity level requirements, and obtaining a verified list of candidate host nodes; From the verified candidate host node list, a primary and backup host node list is assigned to each interface name based on the fault tolerance rule to obtain a host resource mapping table; wherein the primary and backup host node list includes a primary node and at least one candidate node.

4. A method for multi-service system interface integration and dynamic host automatic management according to claim 3, characterized in that: The steps of searching a corresponding dynamic routing policy in a dynamic routing table according to the interface name in the external service request, and selecting a target host node according to the dynamic routing policy include: Searching the dynamic routing table for a dynamic routing policy associated with the interface name; Extracting a list of primary and backup host nodes in the dynamic routing strategy; Obtaining the load status of the master node and the candidate nodes in the master and standby host node list in real time; Determine the corresponding preset load requirement according to the interface name in the external service request; Determining whether the load state of the master node meets the preset load requirement; If yes, the master node is used as the target host node; If not, a candidate node that meets the preset load requirement and has the best load status is selected as the target host node.

5. A method for multi-service system interface integration and dynamic host automatic management according to claim 1, characterized in that: The step of processing the data flow of the external service request based on the dynamic routing strategy and routing the external service request to the target host node includes: Extracting data processing logic rules associated with the interface name of the external business request according to the dynamic routing strategy; wherein the data processing logic rules include data format conversion rules, field mapping rules, data filtering rules and desensitization rules; Standardizing the format of the data stream requested by the external service based on the data format conversion rule; Traversing the data stream after format standardization, performing field structure conversion based on the field mapping rule, and obtaining a data stream after field mapping; Traversing the data stream after the field mapping, filtering the data based on the data filtering rule to obtain a filtered data stream; Traversing the filtered data stream, and performing desensitization processing on sensitive data in the data stream based on the desensitization rule; Perform integrity check on the data stream after desensitization processing, and obtain the processed data stream after the check passes; Determine the target host node address based on the dynamic routing strategy; According to the target host node address, the processed data stream is sent to the target host node.

6. A method for multi-service system interface integration and dynamic host automatic management according to any one of claims 1 to 5, characterized in that: After the step of routing the external service request to the target host node, the method further includes: Acquire the service request execution status of the target host node in real time; According to the execution status of the service request, detecting the abnormal status of the target host node in real time; When the target host node is in an abnormal state, a candidate node with the best load state is selected according to the dynamic routing strategy, and the unfinished external service request is rerouted to the candidate node.

7. A method for multi-service system interface integration and dynamic host automatic management according to claim 6, characterized in that: After the step of routing the external service request to the target host node, the method further includes: Receiving and responding to a service request processing completion feedback signal, collecting processing performance data of each target host node; wherein the processing performance data includes response time, success rate and state stability; Calculating a performance score for each target host node based on the processing performance data based on a weighted scoring model; The priority of the list of primary and backup host nodes in the dynamic routing table is dynamically adjusted according to the performance score to obtain an updated dynamic routing table.

8. A multi-service system interface integration and dynamic host automatic management system, characterized in that: The system comprises: The first acquisition module is used to acquire interface feature information of multiple business systems and perform feature extraction to obtain a preliminary interface feature set; An information processing module, used to logically label the same type of fields in the preliminary interface feature set and add extensible annotations to generate a unified interface semantic model; A logic rule integration module, used for acquiring business policy logic rules from a business system, defining data processing logic rules based on the unified interface semantic model, and storing the business policy logic rules and the data processing logic rules in a logic policy rule library; The second acquisition module is used to obtain the host node information in the enterprise infrastructure resources; A host resource matching module, used to match the host node and interface feature information based on the logical policy rule base according to the host node information to obtain a host resource mapping table; wherein the host resource mapping table includes a mapping relationship between the interface name and the primary and backup host node lists; A dynamic routing table construction module, used to generate a dynamic routing policy and construct a dynamic routing table based on the host resource mapping table and the logical policy rule base; A service request receiving module, used to receive external service requests in real time and obtain the interface name of the external service request; A target host node determination module, used to search the corresponding dynamic routing policy in the dynamic routing table according to the interface name in the external service request, and select the target host node according to the dynamic routing policy; A data processing module, used for processing the data flow of the external service request based on the dynamic routing strategy; The service request routing module is used to route the external service request to the target host node.

9. A multi-business system interface integration and dynamic host automatic management system according to claim 8, characterized in that: The system further comprises: A processing performance data collection module, used to receive and respond to a service request processing completion feedback signal, and collect processing performance data of each target host node; wherein the processing performance data includes response time, success rate and state stability; A performance score calculation module, used to calculate the performance score of each target host node according to the processing performance data based on a weighted scoring model; The dynamic routing table updating module is used to dynamically adjust the priority of the primary and backup host node lists in the dynamic routing table according to the performance score to obtain an updated dynamic routing table.

10. A multi-business system interface integration and dynamic host automatic management system according to claim 8, characterized in that: The system further comprises: An execution status acquisition module, used to acquire the execution status of the service request of the target host node in real time; An abnormal state detection module, used to detect the abnormal state of the target host node in real time according to the execution state of the service request; The dynamic routing module is used to select a candidate node with the best load status according to the dynamic routing strategy when the target host node is in an abnormal state, and reroute the unfinished external service request to the candidate node.

Images