IP MANAGEMENT METHOD, CLIENT AND SERVER

• US 20160323238A1
• Filed: 02/10/2015
• Published: 11/03/2016
• Est. Priority Date: 12/17/2013
• Status: Active Grant

• Current Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Inventors: Yuan, Shuai
• Granted Patent: US 9,590,947 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

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.

Claims

1. An IP management method comprising:

looking up, by a client device, in a first correspondence table to determine an IP address of a server corresponding to a type of service to which the client device is to access, wherein the first correspondence table is saved by the client device and stores correspondence between IP addresses of servers and types of services in a service cluster;

sending, by the client device, an access request to the server corresponding to the determined IP address, wherein the access request comprises information indicating the type of service to which the client device is to access; and

receiving, by the client device, access data fed back by the server, wherein the access data corresponds to the type of service to which the client device is to access,

wherein the access request further comprises a latest update time of the first correspondence table, and the method further comprises;

receiving, by the client device, update data for the first correspondence table fed back by the server, wherein the update data represents data updated in a second correspondence table during a period from the latest update time of the first correspondence table to a current time, and the second correspondence table is saved by the server and stores correspondence between the IP addresses of the servers and the types of services in the service cluster.

2. (canceled)

3. The method according to claim 2, wherein the update data for the first correspondence table comprises a to-be-added correspondence, and the method further comprises:

adding the to-be-added correspondence to the first correspondence table.

4. The method according to claim 2, wherein the update data for the first correspondence table comprises a to-be-deleted correspondence, and the method further comprises:

deleting the to-be-deleted correspondence from the first correspondence table.

5. An IP management method comprising:

receiving, by a first server, an access request sent by a client device, wherein the access request comprises information indicating a type of service to which the client device is to access and a latest update time of a first correspondence table saved by the client device, wherein the first correspondence table is saved by the client device and stores correspondence between IP addresses of servers and types of services in a service cluster; and

feeding back, by the first server, access data corresponding to the type of service to which the client device is to access and update data for the first correspondence table based on the access request, wherein the update data represents data updated in a second correspondence table during a period from a latest update time of the first correspondence table to a current time, and the second correspondence table is saved by the first server and stores correspondence between the IP addresses of servers and the types of services in the service cluster.

6. The method according to claim 5, further comprising:

checking, by the first server, first heartbeat information to determine in the service cluster a second server of which heartbeat time is greater than a preset value, wherein the first heartbeat information is saved by the first server and represents correspondence between IP addresses of servers in the service cluster and heartbeat time;

initiating, by the first server, a heartbeat to the second server; and

in a case that second heartbeat information fed back by the second server is received by the first server in a preset period, wherein the second heartbeat information is saved by the second server and represents correspondence between IP addresses of servers in the service cluster and heartbeat time, obtaining third heartbeat information by comparing heartbeat time in the first heartbeat information with heartbeat time in the second heartbeat information and taking the smallest ones among the heartbeat time corresponding to the IP addresses of the servers in the service cluster as updated heartbeat time; and

replacing, by the first server, the first heartbeat information with the third heartbeat information, and sending the third heartbeat information to the second server so that the second server replaces the second heartbeat information with the third heartbeat information.

7. The management method according to claim 6, further comprising:

deleting the correspondence between the IP address of the second server and the type of service from the first correspondence table, and deleting the correspondence between the IP address of the second server and the heartbeat time from the first heartbeat information, in a case that the second heartbeat information fed back by the second server is not received by the first server in the preset period; and

sending a deletion notification to servers in the first correspondence table other than the first server and the second server, wherein the deletion notification comprises the IP address of the second server.

8. The management method according to claim 5, further comprising:

receiving, by the first server, a heartbeat initiated by a third server, wherein the heartbeat comprises a correspondence between an IP address of the third server and a type of service; and

sending the first heartbeat information to the third server in a case that the first heartbeat information comprises the IP address of the third server.

9. The management method according to claim 8, further comprising:

adding the correspondence between the IP address of the third server and the type of service to the first correspondence table and adding the IP address of the third server to the first heartbeat information, in a case that the first heartbeat information does not comprise the IP address of the third server; and

sending an adding notification to servers in the first correspondence table other than the first server and the third server, wherein the adding notification comprises the correspondence between the IP address of the third server and the type of service.

10. A client device comprising:

one or more processors; and

storage media for storing instructions,

wherein when executing the instructions, the one or more processors are configured for;

looking-up in a first correspondence table to determine an IP address of a server corresponding to a type of service to which the client device is to access, wherein the first correspondence table is saved by the client device and stores correspondence between IP addresses of servers and types of services in a service cluster;

sending, an access request to the server corresponding to the determined IP address, wherein the access request comprises information indicating the type of service to which the client device is to access; and

receiving, access data fed back by the server, wherein the access data corresponds to the type of service to which the client device is to access,

wherein in a case that the access request further comprises a latest update time of the first correspondence table, the one or more processors are further configured for;

receiving update data for the first correspondence table fed back by the server, wherein the update data represents data updated in a second correspondence table during a period from a latest update time of the first correspondence table to a current time, and the second correspondence table is saved by the server and stores correspondence between the IP addresses of the servers and the types of services in the service cluster.

11. (canceled)

12. The client device according to claim 11, wherein the update data for the first correspondence table comprises a to-be-added correspondence, and the one or more processors are further configured for:

adding the to-be-added correspondence to the first correspondence table.

13. The client device according to claim 11, wherein the update data for the first correspondence table comprises a to-be-deleted correspondence, and the one or more processors are further configured for:

deleting the to-be-deleted correspondence from the first correspondence table.

14-18. -18. (canceled)