System for context-dependent name resolution

• US 6,154,777 A
• Filed: 07/01/1996
• Issued: 11/28/2000
• Est. Priority Date: 07/01/1996
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Ebrahim, Zahir
• Primary Examiner(s): Follansbee, John A.
• Application Number:
  US08/674,561
• Time in Patent Office: 1,611 Days
• Field of Search: 340/825.52, 340/825.44, 340/254, 379/100.15, 379/265, 379/112, 379/210, 379/100-15, 370/254, 370/401, 709/226-228, 709/200
• US Class Current: 709/227
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1019 Random or heuristic server selection
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs

Abstract

A context-dependent, multiply binding name resolution system. A name resolver is provided, connected to either a requester'"'"'s system or a receiver'"'"'s system, or both. Requests to a given service or domain name are resolved to the appropriate IP address. The intended recipient of the request is resolved based upon a combination of one or more predetermined criteria, including: information about the sender (e.g. geographical location, specific requester identity, etc.); information about the intended recipient (e.g. load balance at the receiver, type of service, etc.); information contained within the request itself (e.g. type of service requested); or other information (time of day, date, random selection of recipient, e.g.). The system is implemented in hardware and/or software, and the resolution criteria can be made interdependent or independent.

Claims

1. A system for name resolution comprising:

a first service provider;

a first requester configured to generate a request which indicates a destination name of a service; and

a name resolver interposed between said first service provider and said first requester, wherein said name resolver is configured to select a destination address corresponding to said destination name of said service from a plurality of destination addresses depending upon at least two of either a geographical location of said first requester, a load of use of said first provider, and/or a time of said request, wherein said geographic location of said first requester is specified as a parameter within said request.

2. The system as recited in claim 1, wherein said name resolver is configured to select said destination address corresponding to said destination name of said service depending upon said date of said request and said time of said request and wherein said date of said request is specified as a parameter within said request and said time of said request is specified as a parameter within said request.

3. The system as recited in claim 1, wherein said name resolver is further configured to select said destination address corresponding to said destination name of said service depending upon at least one of a quality of said service requested by said first requester and a type of said service requested by said first requester.

4. The system as recited in claim 1, wherein said name resolver is further configured to select said destination address corresponding to said destination name of said service depending upon at least two of a type of service provided by said first server provider, a quality of service provided by said first server provider, a date of said service, and a time of said service.

5. The system as recited in claim 1, wherein said first service provider is included within said first host and said first requester is included within said first host.

6. The system as recited in claim 5, wherein said first service provider is included within said first host and said first requester is included within said first host.

7. A system for resolving names comprising:

a name resolving unit coupled to a requester for a service and a provider of said service, wherein said name resolving unit is configured to select a destination address corresponding to said destination name of said service from a plurality of destination addresses in response to a request for said service, and wherein

said name resolving unit is configured to select said destination address corresponding to said destination name of said service depending upon at least one of either a geographical location of said requester, a date of said request, and/or a time of said request.

8. The system as recited in claim 7, wherein said name resolving unit is configured to select said destination address corresponding to said destination name of said service depending upon said date of said request and said time of said request and wherein said date of said request is specified as a parameter within said request and said time of said request is specified as a parameter within said request.

9. The system as recited in claim 7, wherein said name resolving unit is further configured to select said destination address corresponding to said destination name of said service depending upon at least one of a quality of said service requested by said requester and a type of said service requested by said requester.

10. The system as recited in claim 7, wherein said name resolving unit is further configured to select said destination address corresponding to said destination name of said service depending upon at least two of a type of service provided by said provider, a quality of service provided by said provider, a date of said service, and a time of said service.

11. The system for resolving names as recited in claim 7, wherein said destination name of said service is a domain name.

12. The system for resolving names as recited in claim 7, wherein said destination address corresponding to said destination name of said service is an IP address.

13. The system for resolving names as recited in claim 7, wherein said name resolving unit is configured to look up said destination name of said service in a lookup table, wherein said plurality of destination addresses are stored in said lookup table in connection with said destination name of said service.

14. A method for resolving names comprising:

receiving a request for a service from a requester wherein said request indicates a destination name of said service of a provider;

selecting a destination address corresponding to said destination name of said service from a plurality of destination addresses in response to said request, wherein said selecting said destination address depends upon at least two of either a geographical location of said requester, a load of use of said provider, and/or a time of said request, wherein said geographic location of said requester is specified as a parameter within said request; and

transmitting said destination address to said requester.

15. The method as recited in claim 14, wherein said selecting said destination address corresponding to said destination name of said service said depends upon said date of said request and said time of said request and wherein said date of said request is specified as a parameter within said request and said time of said request is specified as a parameter within said request.

16. The method as recited in claim 14, wherein said selecting said destination address corresponding to said destination name of said service further depends upon at least one of a quality of said service requested by said requester and a type of said service requested by said requester.

17. The method as recited in claim 14, wherein said selecting said destination address corresponding to said destination name of said service further depends upon at least one of a load of use of said provider, a type of service provided by said provider, a quality of service provided by said provider, a date of said service, and a time of said service.

18. A computer readable storage medium having instructions recorded therein, wherein said instructions are operable to,

receive a request for a service from a requester wherein said request indicates a destination name of said service of a provider;

select a destination address corresponding to said destination name of said service from a plurality of destination addresses in response to said request, wherein said select said destination address depends upon at least one of either a geographical location of said requester, a load of use of said provider, and/or a time of said request, wherein said geographic location of said requester is specified as a parameter within said request; and

transmit said destination address corresponding to said destination name of said service to said requester.

19. The computer readable storage medium as recited in claim 18, wherein said selecting said destination address corresponding to said destination name of said service is dependent upon said date of said request and said time of said request and wherein said date of said request is specified as a parameter within said request and said time of said request is specified as a parameter within said request.

20. The system as recited in claim 18, wherein said selecting said destination address corresponding to said destination name of said service further depends upon at least one of a quality of said service requested by said requester, a type of said service requested by said requester, a load of use of said provider, a type of service provided by said provider, a quality of service provided by said provider, a date of said service, and a time of said service.