A method, device, and storage medium for client access to a multi-system server.

Abstract

This invention relates to the field of network communication and discloses a method, device, and storage medium for a client to access a multi-system server, solving the problem that a client cannot access and operate server system resources simultaneously when requesting a multi-system server. The method includes: a processing device constructing a communication channel between a master system and slave systems, and assigning a fixed private IP address to each system; the processing device setting forwarding rules between the client request and the master system's private IP address in each system; according to the forwarding rules, the processing device redirecting the client request to the master system's private IP address; the master system querying the client request to determine whether it can be completed by the master system itself; when the client request cannot be completed by the master system itself, the master system parses the client request and sends the parsing result to the slave system through the communication channel, whereby the slave system processes the parsing result and returns it to the client.

Description

Technical Field

[0001] This invention relates to the field of network communication, and in particular to a method, device and storage medium for a client to access a multi-system server. Background Technology

[0002] Different operating systems are installed on different servers, each with its own advantages. With the advancement of technology, to better integrate the strengths of different operating systems, multiple operating systems are often integrated into a single server.

[0003] However, due to the same-origin policy on client-side systems, access to each other is only possible if the access addresses are the same. Since multi-system servers have multiple access addresses, when a client requests a multi-system server, it cannot directly access and manipulate some system resources at once. This forces the client to initiate multiple requests, impacting the client-side interaction experience. Summary of the Invention

[0004] This invention provides a method, apparatus, computer device, and storage medium for a client to access a multi-system server, addressing the problem that a client cannot directly access and operate some system resources on a server at once when accessing a multi-system server.

[0005] Firstly, a method for a client to access a multi-system server is provided, wherein the server includes a master system, slave systems, and a processing device, comprising:

[0006] The processing device establishes a communication channel between the master system and the slave system, and assigns a fixed private IP address to each system.

[0007] The processing device sets forwarding rules between client requests and the private IP address of the main system in each system;

[0008] According to the forwarding rules, the processing device redirects the client request to the private IP address of the main system;

[0009] The main system queries the client request to determine whether the client request can be completed by the main system itself.

[0010] When the client request cannot be completed by the main system itself, the main system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system then processes the parsing result and returns it to the client.

[0011] Furthermore, the processing device sets forwarding rules between client requests and the private IP address of the main system in each system, including:

[0012] The processing device sets up network services in each system.

[0013] The processing device sets forwarding rules between the client request address and the private IP of the main system in each network service.

[0014] Furthermore, after determining whether the client request can be completed by the main system itself, the method further includes:

[0015] If the client request can be completed by the main system itself, then the main system directly responds to the client request and uses the response result as the result of the client request;

[0016] The main system returns the result of the client's request to the client.

[0017] Furthermore, the step of directly responding to the client request by the main system and using the response result as the result of the client request includes:

[0018] The main system parses the client request into OID nodes and read / write command symbols;

[0019] The main system queries the function corresponding to the OID node;

[0020] According to the read / write command, the corresponding function's read / write operation is executed in the function corresponding to the OID node, and the result of the read / write operation is used as the result of the client request.

[0021] Furthermore, the master system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system then processes the parsing result and returns it to the client, including:

[0022] The main system parses the client request into OID nodes and read / write command symbols;

[0023] The master system forwards the OID node and read / write command to the slave system through the communication channel;

[0024] The system queries the received OID node and read / write command to obtain and execute the function corresponding to the OID node;

[0025] The slave system returns the result of the function execution to the master system through the communication channel, and the master system then returns it to the client.

[0026] Further, the step of querying the OID node and read / write command received by the system to obtain and execute the function corresponding to the OID node includes:

[0027] After receiving the OID node from the slave system, the slave system queries the function corresponding to the OID node.

[0028] The slave system executes the read and write operations of the corresponding function in the function corresponding to the OID node according to the read and write command.

[0029] Furthermore, after the processing device receives the client request, the method further includes:

[0030] The master system and the slave system share the same non-volatile storage, enabling data synchronization between them.

[0031] In responding to the client request, the master system performs read and write operations on the non-volatile storage itself, and the slave system performs read and write operations on the non-volatile storage through the master system.

[0032] Furthermore, the slave system performs read and write operations on the non-volatile memory through the master system, including:

[0033] When the slave system receives a read operation from the client request, the master system copies the non-volatile storage to the slave system's memory to process the read operation from the client request.

[0034] When the system receives a write operation from the client request, it forwards the write operation to the main system through the communication channel.

[0035] After receiving the write operation, the main system executes the write operation on the non-volatile storage to process the write operation in the client request.

[0036] In a second aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the aforementioned client accessing a multi-system server method.

[0037] Thirdly, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described method for a client to access a multi-system server.

[0038] In the aforementioned scheme implementing a method, device, and storage medium for client access to a multi-system server, when a client initiates a request, the processing device forwards the request to the master system for unified processing. For requests that the master system cannot handle independently, the parsed result is sent to the slave system via a communication channel. The slave system processes the request and returns it to the client, eliminating the need for the client to request the slave system again. Through the internal communication channel established between the master and slave systems and the unified forwarding of client requests, all client request operations can be completed and responded to in the processing device at once. This allows the client to obtain the required result after making only one request, significantly improving the speed of client requests and enhancing the client's interactive experience. It effectively solves the problem of clients needing to request different access addresses multiple times when accessing multi-system servers. It improves the client's interactive experience, increases the efficiency of request transmission, and makes the client's operation process smoother. Attached Figure Description

[0039] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a schematic diagram of an application environment for a client accessing a multi-system server method according to an embodiment of the present invention;

[0041] Figure 2 This is a schematic diagram of a client accessing a multi-system server processing device according to an embodiment of the present invention;

[0042] Figure 3 This is a flowchart of a method for a client to access a multi-system server according to an embodiment of the present invention;

[0043] Figure 4 This is a flowchart of a method for a client to access a multi-system server according to an embodiment of the present invention;

[0044] Figure 5 This is a schematic diagram of a computer device according to an embodiment of the present invention. Detailed Implementation

[0045] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0046] The method for client access to multi-system servers provided in this invention can be applied to, for example... Figure 1 In this application environment, the client communicates with the server over a network to enable seamless access and operation of multiple system servers without requiring multiple requests for different access addresses. The client can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The server can be a standalone server or a server cluster consisting of multiple servers.

[0047] In one embodiment, such as Figure 2 As shown, a method for a client to access a multi-system server is provided, which is then applied to... Figure 1 Taking a server as an example, the server includes a master system, slave systems, and a processing device. The method includes the following steps:

[0048] S10: The processing device constructs a communication channel between the master system and the slave system, and assigns a fixed private IP address to each system.

[0049] The processing unit initializes the inter-thread communication (ITC) channel between the master and slave systems to establish a communication channel. The processing unit assigns a fixed private IP address to each system for internal communication between the master and slave systems. For example, the master system is assigned the private IP address 172.31.255.40, and the slave system is assigned the private IP address 172.31.255.45. In subsequent operations, the master system can send data or instructions to 172.31.255.45 through the communication channel, thus completing the operation of the master system transmitting data or instructions to the slave system.

[0050] The processing device sets multiple systems in a master-slave mode, meaning one of the systems is designated as the master, and the others as slaves. There is one and only one master system. The systems included in the server include, but are not limited to, Windows, Linux, and RTOS systems. In this embodiment, the master system is preferably a Linux system, and the slave systems are preferably RTOS systems. The Linux system includes all operating systems under Linux and all their versions, including but not limited to CentOS and Red Hat. The RTOS system includes all operating systems under RTOS and all their versions, including but not limited to eCos and mbed OS.

[0051] S20: The processing device sets forwarding rules between client requests and the private IP address of the main system in each system.

[0052] The processing unit parses client requests received into IP addresses and ports. A network service is set up on each system, and a forwarding rule is configured in each network service. This forwarding rule maps the IP addresses and ports of all client requests to the private IP address of the main system.

[0053] For example, if a client requests http: / / test.com / get / list, and the main system's private IP address is 172.31.255.40, this request will resolve to http: / / 10.20.1.58:443 / get / list. Since the client's IP address is 10.20.1.58 and the port number is 443, the processing device needs to configure a corresponding forwarding rule in the network service of each system to map 10.20.1.58:443 to 172.31.255.40:443. The forwarding rule configured is as follows:

[0054] 0.0.0.0 0 10.20.1.58 443 0.0.0.0 0 172.31.255.40 443 2Forward_RGItc

[0055] According to the above forwarding rules, all requests received by the processing device that point to 10.20.1.58:443 will be forwarded to the main system's private IP address 172.31.255.40:443.

[0056] In this embodiment, network services refer to network protocol-oriented services used to support interactive operations and data exchange between different servers on the network. Network services include, but are not limited to, Tomcat, IIS, Apache, etc.

[0057] S30: According to the forwarding rules, the processing device redirects the client request to the private IP address of the main system.

[0058] like Figure 4 As shown, after the master system and slave system have respectively set up forwarding rules between the client request and the master system's private IP address, the client request is forwarded to the master system's private IP address according to the forwarding rules. For example, the master system's private IP address in the processing device is 172.31.255.40, and the slave system has the following forwarding rules set up:

[0059] 0.0.0.0 0 10.20.1.58 80 0.0.0.0 0 172.31.255.40 80 2Forward_RGItc

[0060] According to the above forwarding rules, all requests in the processing device that point to 10.20.1.58:80 will be forwarded to port 80 of 172.31.255.40.

[0061] S40: The main system queries the client request to determine whether the client request can be completed by the main system itself.

[0062] After the processing unit forwards the client request to the main system, it queries the main system's network service for the client request. If the network service can find the node corresponding to the client request, it determines that the client request can be completed by the main system itself. If the network service cannot find the node corresponding to the client request, it determines that the client request cannot be completed by the main system itself.

[0063] S50: When the client request cannot be completed by the main system itself, the main system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system processes the parsing result and returns it to the client.

[0064] After the processing device forwards the client request to the main system, if the main system's network service cannot find the node corresponding to the client request, that is, in the path where the main system cannot complete the client request on its own, the main system will parse the client request, forward the parsing result to the slave system through the communication channel, the slave system will process the parsing result, obtain the corresponding result, send the result back to the main system, and then the main system will return it to the client.

[0065] In this embodiment, when a client initiates a request, the processing device forwards the request to the main system for unified processing. Requests that the main system cannot handle independently are sent to the slave system via a communication channel. The slave system processes the request and returns it to the client, eliminating the need for the client to request the slave system again. Through the internal communication channel established between the main and slave systems and the unified forwarding of client requests, all client request operations can be completed and responded to in the processing device at once. This allows the client to obtain the required result after making only one request, significantly improving the speed of client requests and enhancing the client's interactive experience. It effectively solves the problem of clients needing to request different access addresses multiple times when accessing multiple system servers. This improves the client's interactive experience, increases the efficiency of request transmission, and makes the client's operation process smoother.

[0066] In one embodiment, after the main system receives the client request, following step S40, i.e., after determining whether the client request can be completed by the main system itself, the method further includes the following steps:

[0067] S71: If the client request can be completed by the main system itself, then the main system directly responds to the client request and uses the response result as the result of the client request.

[0068] S72: The main system returns the result of the client's request to the client.

[0069] In step S71, the main system directly responds to the client request and uses the response result as the result of the client request. This specifically includes the following steps:

[0070] S711: The main system parses the client request into OID nodes and read / write command symbols.

[0071] S712: The main system queries the function corresponding to the OID node.

[0072] S713: According to the read / write command, in the function corresponding to the OID node, execute the read / write operation of the corresponding function, and use the result of the read / write operation as the result of the client request.

[0073] In steps S711-S713 of this embodiment, a network management protocol agent is set up in the main system. This embodiment preferably uses an SNMP (Simple Network Management Protocol) agent. Network management protocols may also include, but are not limited to, CMIP, SNMP, etc. OID refers to Object Identifier (OID).

[0074] In step S711, the client request is parsed into the corresponding OID node and read / write command symbol in the network management protocol proxy of the main system. The read / write command symbol refers to the identifier of the read / write operation contained in the client request, including but not limited to read operation identifiers and write operation identifiers. Read operations include but are not limited to query operations, and write operations include but are not limited to add, delete, and modify operations.

[0075] For example, if the current client request is https: / / test.com / delete, according to the forwarding rules, this request is redirected to the private IP address 172.31.255.40:443. Parsing this request retrieves the Network Management Protocol (NMP) OID node 1.3.6.1.2.1.4.21. This node is used by the main system to find the specific information of the operation required by the client request. Furthermore, this client request will be parsed as a write operation, which will be marked as a 'set'. This 'set' will then serve as the write identifier for the client request. In other words, after the main system finds the node for the required operation based on 1.3.6.1.2.1.4.21, it executes the 'set' operation on that information according to the function of the corresponding node.

[0076] In this embodiment, OID nodes using the Network Management Protocol (NMP) are selected for information querying, data reading and writing operations. This enables the entire processing device to achieve unified management of different systems during data processing, resulting in low management costs. In particular, SNMP OID nodes are preferred, fully leveraging the advantages of SNMP's simple design and reducing operational costs. Utilizing OID nodes for data processing simplifies and speeds up data retrieval, effectively improving the processing device's work efficiency and operational efficiency.

[0077] In one embodiment, after receiving a client request and determining from the query results that it cannot complete the requested operation, the main system, such as... Figure 3 As shown, in step S50, the main system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system then processes the parsing result and returns it to the client. Specifically, this includes the following steps:

[0078] S51: The main system parses the client request into OID nodes and read / write command symbols.

[0079] S52: The master system forwards the OID node and read / write command to the slave system through the communication channel.

[0080] S53: The system queries the received OID node and read / write command to obtain and execute the function corresponding to the OID node.

[0081] S54: The slave system returns the result of the function execution to the master system through the communication channel, and the master system then returns it to the client.

[0082] In step S53 of this embodiment, after the master system forwards the OID node and read / write command to the slave system, the slave system queries the network management protocol proxy based on the OID node to obtain the function corresponding to the OID node. The slave system executes the corresponding read / write operation in the function according to the read / write command; that is, the slave system executes the read / write operation function corresponding to the OID node.

[0083] In step S54, after executing the function corresponding to the OID node from the system and obtaining the result, the result is returned to the main system. This result includes, but is not limited to, the results of querying the OID node and the results of executing the function corresponding to the OID node. The results of querying the OID node include, but are not limited to, request failure, query success, and lack of query permissions. The results of executing the function corresponding to the OID node include, but are not limited to, list data results, data deletion failure messages, and the number of successfully inserted data entries.

[0084] In step S53, the system queries the received OID node and read / write command to obtain and execute the function corresponding to the OID node. This includes the following steps:

[0085] S531: After receiving the OID node from the slave system, the slave system queries the function corresponding to the OID node.

[0086] S532: The slave system executes the read / write operation of the corresponding function in the function corresponding to the OID node according to the read / write command.

[0087] In step S531 of this embodiment, after the master system forwards the OID node and read / write command to the slave system, the network management protocol agent in the slave system receives the OID node and queries each registered node under the network management protocol agent according to the OID node. This continues until a corresponding OID node is found, at which point the corresponding function is obtained. If no result is found, a query failure is returned.

[0088] In step S532, after obtaining the function corresponding to the OID node from the system's network management protocol proxy, the function operation corresponding to the read / write command is selected and executed according to the read / write command. For example, if the function corresponding to the OID node contains read and write operations, and the read / write command is marked as "set", then the operation of writing OID node information in the function is executed.

[0089] In steps S531-S532, for example, the OID node received from the system is 1.3.6.1.2.1.2.2.1.2, and the read / write command identifier is "get," meaning the received read / write command identifier is "read." The system's network management protocol agent will then search for the node 1.3.6.1.2.1.2.2.1.2. After finding the node's information, it will perform a read operation on the node according to the corresponding function in the node information. During this process, if the system cannot find the node, the result is a query failure; if the system finds the node and successfully executes the read operation, the result of reading the data is returned.

[0090] In this embodiment, by setting up network management protocol proxies in both the master and slave systems, client requests are transformed into corresponding OID nodes of the network management service and the specific read / write commands to be executed by the client request operation. This allows the master and slave systems to directly forward client request information through an internal communication channel without forwarding the request itself. This effectively prevents encoding anomalies during the forwarding of client requests between different systems, eliminating the need for repeated encoding and decoding operations and accelerating the system's processing speed for client requests. It also reduces the amount of data that needs to be transmitted between different systems, speeding up data transmission. This effectively improves the overall response speed of the processing device to client requests.

[0091] In one embodiment, when multiple systems initiate a client request, such as Figure 2 As shown, in step S30, after the processing device receives the client request, the method further includes the following steps:

[0092] S91: The master system and the slave system share the same non-volatile storage, enabling data synchronization between the master system and the slave system.

[0093] S92: In the process of responding to the client request, the master system completes the read and write operations on the non-volatile storage itself, and the slave system completes the read and write operations on the non-volatile storage through the master system.

[0094] In this embodiment, all read and write operations in both the master and slave systems are changed to read and write operations on the same non-volatile storage, ensuring data consistency and effectively preventing abnormal data loss due to power outages or other reasons. Non-volatile storage includes, but is not limited to, NVRAM (non-volatile random access memory) and FLASH (flash memory).

[0095] It is worth noting that since different systems store all read and write operations in the same non-volatile storage, not only is the data between different systems synchronized, but the speed of the entire read and write operation process is also accelerated, the data is saved more effectively and in a timely manner, the data integrity is guaranteed, and the response performance of the processing device is improved, optimizing the response time and interactive experience of the entire operation process.

[0096] In one embodiment, when the system processes a client request, such as Figure 2 As shown, step S93, which involves the slave system performing read and write operations on the non-volatile memory through the master system, specifically includes the following steps:

[0097] S931: When the slave system receives a read operation from the client request, it copies the non-volatile storage to the slave system's memory to process the read operation from the client request.

[0098] S932: When the slave system receives a write operation from the client request, it forwards the write operation to the master system through the communication channel.

[0099] S933: After receiving the write operation, the main system executes the write operation on the non-volatile storage to process the write operation in the client request.

[0100] In steps S931-S933, read operations from the slave system are sent to the master system via command commands. The master system then copies non-volatile storage to system memory for the slave system to read. System memory refers to volatile storage, which includes, but is not limited to, DDR (DDR SDRAM, short for Double Data Rate Synchronous Dynamic Random Access Memory). Write operations, on the other hand, are all handled by the master system via command forwarding. This effectively utilizes the master-slave mode and DDR to distinguish between read and write operations, enabling the slave system to achieve read-write separation quickly and easily, and achieving overall load balancing of the processing device.

[0101] It is worth noting that in this embodiment, read and write operations are performed separately from the slave system. This read-write separation distributes system load and improves system resource utilization. In scenarios with high concurrency reads, load balancing can be used to balance the load across multiple slave systems. Furthermore, the scalability of the slave system is enhanced; expanding the slave system does not affect the server itself.

[0102] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0103] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 5 As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements a method for a client to access a multi-system server.

[0104] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:

[0105] The processing device establishes a communication channel between the master system and the slave system, and assigns a fixed private IP address to each system.

[0106] The processing device sets forwarding rules between client requests and the private IP address of the main system in each system;

[0107] According to the forwarding rules, the processing device redirects the client request to the private IP address of the main system;

[0108] The main system queries the client request to determine whether the client request can be completed by the main system itself.

[0109] When the client request cannot be completed by the main system itself, the main system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system then processes the parsing result and returns it to the client.

[0110] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0111] The processing device establishes a communication channel between the master system and the slave system, and assigns a fixed private IP address to each system.

[0112] The processing device sets forwarding rules between client requests and the private IP address of the main system in each system;

[0113] According to the forwarding rules, the processing device redirects the client request to the private IP address of the main system;

[0114] The main system queries the client request to determine whether the client request can be completed by the main system itself.

[0115] When the client request cannot be completed by the main system itself, the main system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system then processes the parsing result and returns it to the client.

[0116] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0117] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0118] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method for a client to access a multi-system server, characterized in that, The multi-system server includes a master system, slave systems, and a processing device; the method includes: The processing device establishes a communication channel between the master system and the slave system, and assigns a fixed private IP address to each system. The processing device sets forwarding rules between client requests and the private IP address of the main system in each system; According to the forwarding rules, the processing device redirects the client request to the private IP address of the main system; The main system queries the client request to determine whether the client request can be completed by the main system itself. When the client request cannot be completed by the main system itself, the main system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system then processes the parsing result and returns it to the client. The master system parses the client request and sends the parsing result to the slave system through the communication channel. The slave system processes the parsing result and returns it to the client, including: The main system parses the client request into OID nodes and read / write command symbols; The master system forwards the OID node and read / write command to the slave system through the communication channel; The system queries the received OID node and read / write command to obtain and execute the function corresponding to the OID node; The slave system returns the result of the function execution to the master system through the communication channel, and the master system then returns it to the client.

2. The method for a client to access a multi-system server as described in claim 1, characterized in that, The processing device sets forwarding rules between client requests and the private IP address of the main system in each system, including: The processing device sets up network services in each system. The processing device sets forwarding rules between the client request address and the private IP of the main system in each network service.

3. The method for a client to access a multi-system server as described in claim 1, characterized in that, After determining whether the client request can be completed by the main system itself, the method further includes: If the client request can be completed by the main system itself, then the main system directly responds to the client request and uses the response result as the result of the client request; The main system returns the result of the client's request to the client.

4. The method for a client to access a multi-system server as described in claim 3, characterized in that, The direct response of the main system to the client request, using the response result as the result of the client request, includes: The main system parses the client request into OID nodes and read / write command symbols; The main system queries the function corresponding to the OID node; According to the read / write command, the corresponding function is executed in the function corresponding to the OID node, and the result of the read / write operation is used as the result of the client request.

5. The method for a client to access a multi-system server as described in claim 1, characterized in that, The process of querying the OID node and read / write command received by the system to obtain and execute the function corresponding to the OID node includes: After receiving the OID node from the slave system, the slave system queries the function corresponding to the OID node. The slave system executes the read and write operations of the corresponding function in the function corresponding to the OID node according to the read and write command.

6. The method for a client to access a multi-system server as described in claim 1, characterized in that, After the processing device receives the client request, the method further includes: The master system and the slave system share the same non-volatile storage, enabling data synchronization between them. In responding to the client request, the master system performs read and write operations on the non-volatile storage itself, and the slave system performs read and write operations on the non-volatile storage through the master system.

7. The method for a client to access a multi-system server as described in claim 6, characterized in that, The slave system performs read and write operations on the non-volatile memory through the master system, including: When the slave system receives a read operation from the client request, the master system copies the non-volatile storage to the slave system's memory to process the read operation from the client request. When the system receives a write operation from the client request, it forwards the write operation to the main system through the communication channel. After receiving the write operation, the main system executes the write operation on the non-volatile storage to process the write operation in the client request.

8. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the client accessing a multi-system server method as described in any one of claims 1 to 7.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the client accessing a multi-system server method as described in any one of claims 1 to 7.

Images