Client Server IP Management via Local Correspondence Table
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IP management systems are costly and unreliable due to reliance on proxy servers or DNS servers, which can lead to connectivity issues and high maintenance costs when IP addresses change or servers fail.
Innovation Solution
A client device and server system that uses a local correspondence table to determine and manage IP addresses for service access, eliminating the need for proxy or DNS servers by allowing clients to directly access servers and synchronize data with a second correspondence table maintained by the server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the client device uses a proxy server or DNS server to determine the IP address of the server, then the IP address management is centralized and easy to control, but the system reliability decreases and maintenance cost increases when the proxy server or DNS server fails or its IP address changes
Solution Approach 1:
The patent divides the centralized IP address management function into two parts: the server maintains the authoritative mapping between service types and IP addresses (second correspondence table), while the client device maintains a local copy (first correspondence table). This segmentation allows the client to independently resolve IP addresses without relying on the proxy server or DNS server, improving reliability while maintaining ease of management through the server's centralized update capability.
Solution Approach 2:
The client device creates a local copy (first correspondence table) of the server's IP address mapping data (second correspondence table). This copying mechanism enables the client to access IP addresses directly from its local table, eliminating dependency on external proxy servers or DNS servers, thereby improving system reliability while the server can still update the copy when changes occur.
2Device complexity
If the client device relies on the proxy server or DNS server for IP address resolution, then the client device does not need to maintain local IP address data, but the maintenance cost increases and the system becomes vulnerable to server failures
Solution Approach 1:
The client device performs preliminary action by pre-obtaining and storing the correspondence between service types and IP addresses in its local first correspondence table before actually needing to access a service. This allows the client to have immediate access to IP address information without needing to query external servers at the moment of service access, reducing dependency and improving reliability.
Solution Approach 2:
The client device serves itself by maintaining and using its own local first correspondence table for IP address resolution, rather than continuously relying on external proxy servers or DNS servers. The client can independently resolve service types to IP addresses using its local data, making the system more reliable and reducing maintenance costs associated with external server management.
3Adaptability or versatility
If the IP address of the proxy server or DNS server changes, then the server can be updated with new IP addresses, but all client devices need to be updated, resulting in high maintenance cost
Solution Approach 1:
When the server's IP address changes, the server updates its second correspondence table and sends the updated data to client devices. Each client device updates its local first correspondence table independently based on the received update data. This copying mechanism allows distributed updates without requiring manual configuration of all client devices, reducing maintenance costs while maintaining adaptability to IP address changes.
Solution Approach 2:
The server provides feedback to client devices when IP address changes occur by sending update data containing the new correspondence information. Client devices receive this feedback and automatically update their local first correspondence tables, enabling adaptive response to IP address changes without manual intervention on each client, thus reducing maintenance costs while maintaining adaptability.
Data Source
AI summary
An IP management method, a client and a server. The method comprises: searching, by a client, a first correlation table, and determining an IP address of a server corresponding to the type of a service to which the client needs access, the first correlation table being a table of the correlation between the IP address of the server in a service cluster saved by the client and the type of the service; sending, by the client, an access request to a server corresponding to the determined IP address of the server, the access request containing the type of the service to which the client needs access; and receiving, by the client, access data which is fed back by the server and corresponds to the type of the service to which the client needs access.