Service registration access method based on logic strong isolation device

Abstract

The invention discloses a service registration access method based on a logic strong isolation device, which belongs to the technical field of data transmission, and comprises the following steps of: S1, registering basic messages of service nodes on two sides of the logic strong isolation device into a cross-regional database based on an HTTP (Hyper Text Transport Protocol), and further generating a node data table; s2, inserting the request instructions into a cross-region database based on a first fragment time period of a CPU, and determining a service node corresponding to each request instruction based on a node data table; s3, processing each request instruction based on the service node corresponding to each request instruction, and further generating an HTTP response corresponding to each request instruction; and S4, inserting the HTTP responses into the cross-region database based on the second fragment time period of the CPU, and returning each HTTP response to the service node corresponding to each HTTP response based on the node data table. The problem of row-level lock competition caused by concurrent consumption of cross-regional database data by multiple service nodes is solved.

Description

Technical Field

[0001] The present invention relates to the technical field of data transmission, and in particular to a service registration access method based on a logic strong isolation device. Background Art

[0002] In a distributed system, data is often distributed in different areas or nodes. When service nodes in different areas need to access database data located in other areas, in order to improve the processing power and response speed of the system, multi-node and multi-threading methods are usually used to concurrently process tasks. For example, a high-frequency database writing method and device based on multi-threaded asynchronous operation is disclosed with patent number CN118467591A. The method and device create a multi-threaded table writer object and initialize it. The table structure to be written to the database is obtained, a group of threads and corresponding cache queues are created, each thread is connected to the database system and monitors the status of the corresponding cache queue, and the number threshold of the cache queue's expected single write and the time threshold of the maximum write interval are set. Data is asynchronously inserted through the multi-threaded table writer object. The table type and partition type are determined according to the table structure. For a partitioned table, data of different partition types are inserted into different cache queues. The threads are executed cyclically, and the write condition of the cache queue is triggered based on the number threshold and the time threshold. The data in the cache queue is sent to the database system through the thread for data insertion, and the cache queue is cleared. This improves writing efficiency and reduces data writing latency. However, in the above solution, when multiple threads or nodes consume database data concurrently, it is easy to cause row-level lock contention problems. Summary of the invention

[0003] In view of the problem of row-level lock competition caused by concurrent consumption of cross-region database data by multiple service nodes in the prior art, the present invention provides a service registration access method based on a logical strong isolation device. According to the information in the node data table, the request instructions and response instructions are accurately assigned to the corresponding service nodes. The service nodes will only access and process the data rows they need, reducing the situation where multiple service nodes access the same data row at the same time. The request instructions and HTTP responses are batch processed using CPU fragmentation time, reducing the number of operations on the cross-region database. The combination of the two solves the problem of row-level lock competition caused by concurrent consumption of cross-region database data by multiple service nodes. At the same time, by reducing the number of cross-region database operations, the data processing efficiency is improved, ensuring the efficiency and stability of cross-region interactions.

[0004] To solve the above technical problems, the present invention provides a service registration access method based on a logical strong isolation device, comprising the following steps: S1: Based on the HTTP protocol, the basic messages of the service nodes on both sides of the logical strong isolation device are registered in the cross-region database, and then the node data table is generated; S2: inserting the request instruction into the cross-zone database based on the first fragmentation time period of the CPU, and determining the service node corresponding to each request instruction based on the node data table; S3: Process each request instruction based on the service node corresponding to each request instruction, and then generate an HTTP response corresponding to each request instruction; S4: inserting the HTTP response into the cross-zone database based on the second fragmentation time period of the CPU, and returning each HTTP response to the service node corresponding to each HTTP response based on the node data table.

[0005] After adopting the above technical solution, the present invention has the following advantages: According to the information in the node data table, the request instructions and response instructions are accurately assigned to the corresponding service nodes. The service nodes will only access and process the data rows they need, avoiding the situation where multiple service nodes access the same data row at the same time. At the same time, the request instructions and HTTP responses are batch processed in combination with CPU fragmentation time, which significantly reduces the number of operations on cross-region databases. At the same time, by reducing the number of cross-region database operations, the data processing efficiency is improved, ensuring the efficiency and stability of cross-region interactions; By encapsulating cross-region database access operations with standard HTTP protocols, the cross-region data interaction process is simplified, security is improved, and it is easy to integrate into the existing network architecture, so it has good compatibility; The problem of row-level lock contention caused by concurrent consumption of cross-region database data by multiple service nodes has been solved.

[0006] Preferably, the basic message of the service node includes at least the IP address and the work thread number of the service node.

[0007] Preferably, the S1 comprises: S11: Design the registration interface based on the basic message of the service node; S12: Building an HTTP request based on the basic message of the service node and the HTTP protocol; S13: Send the HTTP request to the registration interface, and determine whether the request body of the HTTP request contains the basic message of the service node. If it does, generate a node data table. If not, continue to execute S12. The basic message of the service node is the core data of service registration and discovery, including key information such as the IP address, port number, and service type of the service node. When designing the registration interface, it is necessary to clarify the format and transmission method of these basic messages so that the service node can successfully register its own information to the cross-region database. By determining whether the request body of the HTTP request contains the basic message of the service node, node data table errors or inconsistencies caused by incomplete data are avoided, thereby ensuring the accuracy and reliability of service node information in the cross-region database. Avoiding the generation of node data tables based on incomplete data also means that database resources will not be wasted to store invalid or erroneous data, thereby improving resource utilization.

[0008] Preferably, S2 includes: S21: determining whether the CPU is in the first fragmentation time period, if so, obtaining a request instruction, if not, inserting information of all request instructions obtained in the previous first fragmentation time period of the CPU into a cross-region database to generate a request instruction table; S22: Compare the request instruction table with the node data table to obtain a first comparison result, and determine the service node corresponding to each request instruction based on the first comparison result. The first fragmentation time is any time period when the CPU processes except the request instruction. By batch insertion, the number of operations on the cross-region database can be reduced. At the same time, combined with the comparison mechanism, the data processing efficiency is improved, and the efficiency and stability of cross-region interaction are ensured.

[0009] Preferably, the S22 includes: S221: Compare the request data in the request instruction table with the node data in the node data table, mark the request instruction corresponding to the successfully compared request data as a valid instruction, and determine the service node corresponding to the valid instruction based on the node data corresponding to the valid instruction; S222: Record the request data that has not been successfully matched to generate a first record table, and update the node data table based on the first record table. By comparing the request data in the request instruction table with the node data in the node data table, it is possible to verify whether the request instruction points to the correct service node, thereby avoiding the request instruction from being sent to a non-existent or inappropriate service node, ensuring the accuracy and effectiveness of the service request, recording the request data that has not been successfully matched, and generating a first record table, thereby ensuring the accuracy and real-time performance of the node data table.

[0010] Preferably, S3 includes: S31: judging whether to operate the target data according to the state of the target data corresponding to the request instruction received by the service node; if the target data is not operated, monitoring the state of the target data; continuing to execute S31 when the state of the target data changes; if the target data is operated, obtaining the operation result, and continuing to execute S32; S32: Generate an HTTP response corresponding to the request instruction based on the operation result. By first determining the state of the target data and then performing the operation, data consistency is improved and resource utilization is optimized.

[0011] Preferably, in S31, judging whether to operate on the target data according to the state of the target data corresponding to the request instruction received by the service node includes: If the state of the target data corresponding to the request instruction is being modified, it means that the target data is not operated on. If the state of the target data corresponding to the request instruction is any state except being modified, it means that the target data is operated on.

[0012] Preferably, S4 includes: S41: Determine whether it is in the second fragmentation time period of the CPU. If it is in the second fragmentation time period of the CPU, obtain an HTTP response. If it is not in the second fragmentation time period of the CPU, batch insert information of all HTTP responses obtained in the last second fragmentation time period of the CPU into the cross-zone database to generate a response instruction table. S42: Compare the response instruction table with the node data table to obtain a second comparison result, and determine the service node corresponding to each HTTP response based on the second comparison result. The second fragmentation time is any time period when the CPU processes except the HTTP response. By batch insertion, the number of operations on the cross-region database can be reduced. At the same time, combined with the comparison mechanism, the data processing efficiency is improved, and the efficiency and stability of cross-region interaction are ensured.

[0013] Preferably, the S42 includes: S421: Compare the response data in the response instruction table with the node data in the node data table, mark the HTTP response corresponding to the successfully compared response data as a valid response, and determine the service node corresponding to the valid response based on the node data corresponding to the valid response; S422: Record the unmatched HTTP responses to generate a second record table, and update the node data table based on the second record table. By comparing the response data in the response instruction table with the node data in the node data table, it is possible to verify whether the HTTP response points to the correct service node, avoid sending the HTTP response to a non-existent or inappropriate service node, ensure the accuracy and effectiveness of the service request, record the unmatched HTTP responses, and generate a second record table, ensuring the accuracy and real-time performance of the node data table.

[0014] Preferably, it also includes: Record the number of successful comparisons between each node data in the node data table and the request data in the request instruction table, and store the node data in the node data table that has successfully compared the request data in the request instruction table more than the preset number of times in the memory. Frequent reading of node data from the database will cause great pressure on the cross-region database. By storing the node data that meets the conditions in the memory, the number of accesses to the cross-region database can be reduced, thereby reducing the pressure on the cross-region database and improving the response speed.

[0015] Beneficial effects of this program: According to the information in the node data table, the request instructions and response instructions are accurately assigned to the corresponding service nodes. The service nodes will only access and process the data rows they need, avoiding the situation where multiple service nodes access the same data row at the same time. At the same time, the request instructions and HTTP responses are batch processed in combination with CPU fragmentation time, which significantly reduces the number of operations on cross-region databases. At the same time, by reducing the number of cross-region database operations, the data processing efficiency is improved, ensuring the efficiency and stability of cross-region interactions; By encapsulating cross-region database access operations with standard HTTP protocols, the cross-region data interaction process is simplified, security is improved, and it is easy to integrate into the existing network architecture, so it has good compatibility; The problem of row-level lock contention caused by concurrent consumption of cross-region database data by multiple service nodes has been solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Other features, objects and advantages of the present invention will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings. The drawings are only for the purpose of illustrating preferred embodiments and are not to be considered as limiting the present invention. Also, the same reference symbols are used throughout the drawings to represent the same parts.

[0017] Figure 1 It is a flow chart of the service registration access method based on the logic strong isolation device of the present invention; Figure 2It is a cross-region data interaction flow chart of the service registration access method based on the logic strong isolation device of the present invention; Figure 3 A schematic diagram of service node registration of a service registration access method based on a logic-strong isolation device according to the present invention. DETAILED DESCRIPTION

[0018] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific implementation method described herein is only an optimal embodiment of the present invention, which is only used to explain the present invention and does not limit the scope of protection of the present invention. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0019] Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe the operations (or steps) as sequential processes, many of the operations (or steps) therein can be implemented in parallel, concurrently, or simultaneously. In addition, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but can also have additional steps not included in the drawings; the process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0020] Embodiment 1: like Figure 1 As shown, the service registration access method based on the logical strong isolation device includes the following steps: S1: Based on the HTTP protocol, the basic messages of the service nodes on both sides of the logical strong isolation device are registered in the cross-zone database, and then the node data table is generated.

[0021] The basic message of the service node includes at least the IP address and the work thread number of the service node.

[0022] The S1 includes: S11: Design the registration interface based on the basic message of the service node; S12: Building an HTTP request based on the basic message of the service node and the HTTP protocol; S13: Sending an HTTP request to the registration interface, determining whether the request body of the HTTP request contains basic information of the service node, if so, generating a node data table, if not, continuing to execute S12.

[0023] Determine the name, request method, URL path, etc. of the registration interface, design the registration interface according to the IP address and work thread number of the service node, so that the registration interface allows the service node to register, and encapsulate the basic information of the service node into an HTTP request so that it can be sent to the registration interface through the HTTP protocol. After the registration interface accepts the HTTP request, it determines whether the request body in each HTTP request contains the IP address and work thread number, and retransmits the HTTP request that does not contain the IP address or work thread number. The node data table is generated only when the request body in all HTTP requests received by the registration acceptance contains the IP address and work thread number. By determining whether the request body of the HTTP request contains the basic information of the service node, the node data table errors or inconsistencies caused by incomplete data are avoided, thereby ensuring the accuracy and reliability of the service node information in the cross-region database. Avoiding the generation of node data tables based on incomplete data also means that database resources will not be wasted to store invalid or erroneous data, thereby improving resource utilization.

[0024] S2: inserting the request instruction into the cross-zone database based on the first fragmentation time period of the CPU, and determining the service node corresponding to each request instruction based on the node data table.

[0025] The S2 includes: S21: determining whether the CPU is in the first fragmentation time period, if so, obtaining a request instruction, if not, inserting information of all request instructions obtained in the previous first fragmentation time period of the CPU into a cross-region database to generate a request instruction table; S22: Compare the request instruction table with the node data table to obtain a first comparison result, and determine the service node corresponding to each request instruction based on the first comparison result.

[0026] The S22 includes: S221: Compare the request data in the request instruction table with the node data in the node data table, mark the request instruction corresponding to the successfully compared request data as a valid instruction, and determine the service node corresponding to the valid instruction based on the node data corresponding to the valid instruction; S222: Record the request data that has not been successfully matched to generate a first record table, and update the node data table based on the first record table.

[0027] The first fragmentation time period is any time period in which the CPU processes except the request instruction. The upstream caller batch inserts all request instructions in the first fragmentation time period into the cross-region database to generate a request instruction table. The request instruction includes the service name, method name, parameters, etc. of the call. The downstream listener compares the request instruction table with the node data table to obtain the first comparison result, and then batch pulls the first comparison result. The request instruction corresponding to the successfully compared request data is marked as a valid instruction. The service node corresponding to the valid instruction is determined according to the node data corresponding to the valid instruction. If the comparison is not successful, it means that the service node corresponding to the unsuccessful request data is not registered in the node data table, so the node data table is updated. By comparing the request data in the request instruction table with the node data in the node data table, it can be verified whether the request instruction points to the correct service node, avoiding sending the request instruction to a non-existent or inappropriate service node, ensuring the accuracy and effectiveness of the service request, recording the unsuccessful request data, and generating the first record table, ensuring the accuracy and real-time performance of the node data table.

[0028] S3: Process each request instruction based on the service node corresponding to each request instruction, and then generate an HTTP response corresponding to each request instruction.

[0029] The S3 includes: S31: judging whether to operate the target data according to the state of the target data corresponding to the request instruction received by the service node; if the target data is not operated, monitoring the state of the target data; continuing to execute S31 when the state of the target data changes; if the target data is operated, obtaining the operation result, and continuing to execute S32; S32: Generate an HTTP response corresponding to the request instruction based on the operation result.

[0030] In S31, judging whether to operate on the target data according to the state of the target data corresponding to the request instruction received by the service node includes: If the state of the target data corresponding to the request instruction is being modified, it means that the target data is not operated on. If the state of the target data corresponding to the request instruction is any state except being modified, it means that the target data is operated on.

[0031] If user A reads the product information with product ID 123, and user B modifies the product information with product ID 123, the product information with product ID 123 is stored in the cross-region database. User A initiates a read request to read the product information with product ID 123. After receiving the request, the service node first queries the information status of the product with product ID 123. Assuming that the status of the product information with product ID 123 is "under modification" at this time, it waits for the modification to be completed. When the modification is completed, the status is readable. At this time, the product information with product ID 123 is read. Assuming that the status of the product information with product ID 123 is "readable" at this time, user B initiates a read request to modify the product information with product ID 123. After receiving the request, the service node first queries the information status of the product with product ID 123. At this time, it is "readable". The product information can be modified in this state. By first judging the target data status and then performing operations, data consistency is improved and resource utilization is optimized. S4: inserting the HTTP response into the cross-zone database based on the second fragmentation time period of the CPU, and returning each HTTP response to the service node corresponding to each HTTP response based on the node data table.

[0032] The S4 includes: S41: Determine whether it is in the second fragmentation time period of the CPU. If it is in the second fragmentation time period of the CPU, obtain an HTTP response. If it is not in the second fragmentation time period of the CPU, batch insert information of all HTTP responses obtained in the last second fragmentation time period of the CPU into the cross-zone database to generate a response instruction table. S42: Compare the response instruction table with the node data table to obtain a second comparison result, and determine the service node corresponding to each HTTP response based on the second comparison result.

[0033] The S42 includes: S421: Compare the response data in the response instruction table with the node data in the node data table, mark the HTTP response corresponding to the successfully compared response data as a valid response, and determine the service node corresponding to the valid response based on the node data corresponding to the valid response; S422: Record the HTTP responses that have not been successfully compared to generate a second record table, and update the node data table based on the second record table.

[0034] The second fragmentation time of the CPU is any time period in which the CPU processes except the HTTP response. The downstream listener batch-inserts all HTTP responses in the second fragmentation time period into the cross-region database to generate a response instruction table. The HTTP response includes the request instruction ID and the response data, etc. The upstream listener compares the response instruction table with the node data table to obtain the second comparison result, and then batch-pulls the second comparison result, marks the HTTP response corresponding to the successfully compared HTTP response as a valid response, and determines the service node corresponding to the valid response according to the node data corresponding to the valid response. If the comparison is not successful, it means that the service node corresponding to the unsuccessful HTTP response is not registered in the node data table, so the node data table is updated. By comparing the response data in the response instruction table with the node data in the node data table, it can be verified whether the HTTP response points to the correct service node, avoiding sending the HTTP response to a non-existent or inappropriate service node, recording the unsuccessful HTTP response, and generating the first record table, ensuring the accuracy and real-time performance of the node data table.

[0035] Also includes: Record the number of successful comparisons between each node data in the node data table and the request data in the request instruction table, and store the node data in the node data table that has successfully compared the request data in the request instruction table more than the preset number of times in the memory. Frequent reading of node data from the database will cause great pressure on the cross-region database. By storing the node data that meets the conditions in the memory, the number of accesses to the cross-region database can be reduced, thereby reducing the pressure on the cross-region database and improving the response speed.

[0036] like Figure 2As shown, it includes two parts, a request initiation side and a request response side. On the request initiation side, after initiating a request instruction, a batch request storage process is executed. The batch request storage process includes: a batch request blocking queue, using a take() loop to take out the request instruction from the blocking queue until the first fragment time of the CPU is reached, and the batch request instructions accumulated in the first fragment time of the CPU, that is, the CPU time slice, are batch stored to generate a request instruction table. At the same time as the batch request storage process, batch request response polling monitoring is performed. The batch request response polling monitoring includes: a batch request blocking queue, using a take() loop to take out the request instruction ID from the blocking queue until the first fragment time of the CPU is reached, and the batch request instruction ID accumulated in the first fragment time of the CPU, that is, the request ID, is used to batch query the HTTP response result from the response instruction table in the cross-region database, that is, the database, and write the HTTP response listening queue timeout result and the normal result to obtain the response result table. While the request initiation side is running, the request response side also starts running at the same time. On the request response side, batch request instructions are polled and listened. The batch request instruction polling and listening includes obtaining the service ID, IP, and thread ID of the current service node, asynchronous linear pool batch execution of business requests, proxy call business services, write HTTP responses, that is, the results returned by calling the business interface, and execute the batch HTTP response storage process. The batch HTTP response storage process includes: batch response blocking queue, using take() loop to take out HTTP responses from the blocking queue until the second fragment time of the CPU is reached, and batch storage of batch HTTP responses accumulated in the second fragment time of the CPU, that is, the CPU time slice, to generate a response instruction table.

[0037] like Figure 3 As shown, the cross-zone server is the intranet database, and the service node is the cross-zone proxy service node of the intranet and the intranet. In the intranet environment, the information of the new service node (including the service name, ip, mac, time, thread_num) is registered in the intranet database and the cache at the same time. When the internal and external databases are overloaded, the cache can be accessed directly, which further solves the problem of row-level lock competition. At the same time, the "registration" component in the external network will periodically send heartbeat messages to the service registration module of the intranet to indicate that it is still active and hopes to maintain synchronization.

[0038] In order to verify the effectiveness and feasibility of the present invention, the following tests were conducted: Performance testing: Simulate the processing of a large number of requests and responses in a high-concurrency environment, and record the processing time and system resource consumption.

[0039] Stability test: Run the cross-region interactive component service for a long time to observe its stability and data consistency performance.

[0040] Security testing: Simulate various attack methods to verify the effectiveness of the security protection measures of the present invention.

[0041] By implementing the specific steps of the present invention, the security, performance and stability of cross-region data interaction are successfully improved.

[0042] The specific implementation described above is a preferred implementation of the service registration access method based on a logically strong isolation device of the present invention, and is not intended to limit the specific implementation scope of the present invention. The scope of the present invention includes but is not limited to this specific implementation. All equivalent changes made in accordance with the shape and structure of the present invention are within the protection scope of the present invention.

Claims

1. A service registration access method based on a logical strong isolation device, characterized in that: The following steps are involved: S1: Based on the HTTP protocol, the basic messages of the service nodes on both sides of the logical strong isolation device are registered in the cross-region database, and then the node data table is generated; S2: inserting the request instruction into the cross-zone database based on the first fragmentation time period of the CPU, and determining the service node corresponding to each request instruction based on the node data table; S3: Process each request instruction based on the service node corresponding to each request instruction, and then generate an HTTP response corresponding to each request instruction; S4: inserting the HTTP response into the cross-zone database based on the second fragmentation time period of the CPU, and returning each HTTP response to the service node corresponding to each HTTP response based on the node data table.

2. The service registration access method based on a logical strong isolation device according to claim 1 is characterized in that: The basic message of the service node includes at least the IP address and the work thread number of the service node.

3. The service registration access method based on a logical strong isolation device according to claim 1 is characterized in that: The S1 includes: S11: Design the registration interface based on the basic message of the service node; S12: Building an HTTP request based on the basic message of the service node and the HTTP protocol; S13: Sending an HTTP request to the registration interface, determining whether the request body of the HTTP request contains basic information of the service node, if so, generating a node data table, if not, continuing to execute S12.

4. The service registration access method based on a logically strong isolation device according to claim 1 is characterized in that: The S2 includes: S21: determining whether the CPU is in the first fragmentation time period, if so, obtaining a request instruction, if not, inserting information of all request instructions obtained in the previous first fragmentation time period of the CPU into a cross-region database to generate a request instruction table; S22: Compare the request instruction table with the node data table to obtain a first comparison result, and determine the service node corresponding to each request instruction based on the first comparison result.

5. The service registration access method based on the logic strong isolation device according to claim 4 is characterized in that: The S22 includes: S221: Compare the request data in the request instruction table with the node data in the node data table, mark the request instruction corresponding to the successfully compared request data as a valid instruction, and determine the service node corresponding to the valid instruction based on the node data corresponding to the valid instruction; S222: Record the request data that has not been successfully matched to generate a first record table, and update the node data table based on the first record table.

6. The service registration access method based on a strong logic isolation device according to claim 1 is characterized in that: The S3 includes: S31: judging whether to operate the target data according to the state of the target data corresponding to the request instruction received by the service node; if the target data is not operated, monitoring the state of the target data; continuing to execute S31 when the state of the target data changes; if the target data is operated, obtaining the operation result, and continuing to execute S32; S32: Generate an HTTP response corresponding to the request instruction based on the operation result.

7. The service registration access method based on the logic strong isolation device according to claim 6 is characterized in that: In S31, judging whether to operate on the target data according to the state of the target data corresponding to the request instruction received by the service node includes: If the state of the target data corresponding to the request instruction is being modified, it means that the target data is not operated on. If the state of the target data corresponding to the request instruction is any state except being modified, it means that the target data is operated on.

8. The service registration access method based on a logical strong isolation device according to claim 1 is characterized in that: The S4 includes: S41: Determine whether it is in the second fragmentation time period of the CPU. If it is in the second fragmentation time period of the CPU, obtain an HTTP response. If it is not in the second fragmentation time period of the CPU, batch insert information of all HTTP responses obtained in the last second fragmentation time period of the CPU into the cross-zone database to generate a response instruction table. S42: Compare the response instruction table with the node data table to obtain a second comparison result, and determine the service node corresponding to each HTTP response based on the second comparison result.

9. The service registration access method based on the logic strong isolation device according to claim 8 is characterized in that: The S42 includes: S421: Compare the response data in the response instruction table with the node data in the node data table, mark the HTTP response corresponding to the successfully compared response data as a valid response, and determine the service node corresponding to the valid response based on the node data corresponding to the valid response; S422: Record the HTTP responses that have not been successfully compared to generate a second record table, and update the node data table based on the second record table.

10. The service registration access method based on a strong logic isolation device according to claim 5, characterized in that: Also includes: The number of successful comparisons between each node data in the node data table and the request data in the request instruction table is recorded, and the node data whose number of successful comparisons between the node data table and the request data in the request instruction table is greater than a preset number is stored in the memory.

Images