Patent EP0817444A2 successfully refreshed from Google Patents.
← Back to Patent Explorer
EP0817444A2 Expired / Lapsed EP ⏱️ 0.0 years remaining

System for context-dependent name resolution

Assignee: Sun Microsystems Inc
•
Filing: 1997-06-30
•
Granted: —
•
Expires: 2017-06-30
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

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.

Inventors

  • 👤 Zahir Ebrahim

Bibliographic Details

Application Number —
Jurisdiction EP
Data Source google_patents
Last Synchronized 2026-11-05 09:51
CPC Classifications
H; H04; H04L; H04L67/00; H04L67/01; H04L67/10; H04L67/1001; H04L67/1004; H04L67/1008; H04L61/00; H04L61/45; H04L61/4505; H04L61/4511; H04L67/1019; H04L67/1021; H04L67/1023

Claims Analysis

Total Claims: 24
Claim 1
Independent Claim 86 words
A system for name resolution of at least one request directed to a destination name of a receiver and issued from a requester system, including: a name resolver connected to the requester service and including predetermined information correlating a plurality of destination addresses with said destination name; a criteria selection subsystem configured to provide a selection of at least one said destination address based upon at least one predetermined criterion; and a destination address binder configured to bind said destination name with said selected destination address.
Claim 2
Dependent Claim 23 words
The system of claim 1, wherein said at least one predetermined criterion includes a criterion based upon information explicitly contained within said request.
Claim 3
Dependent Claim 14 words
The system of claim 2, wherein said information includes an address of said requester.
Claim 4
Dependent Claim 20 words
The system of claim 2, wherein said information is based upon at least a portion of contents of said request.
Claim 5
Dependent Claim 33 words
The system of claim 4, wherein said portion of said contents includes at least one of: a type of service requested by said request; and a quality of service requested by said request.
Claim 6
Dependent Claim 24 words
The system of claim 1, wherein said at least one predetermined criterion includes a criterion based upon information not explicitly contained within said request.
Claim 7
Dependent Claim 16 words
The system of claim 6, wherein said information pertains to a geographical region of said requester.
Claim 8
Dependent Claim 16 words
The system of claim 6, wherein said information pertains to a geographical region of said receiver.
Claim 9
Dependent Claim 15 words
The system of claim 6, wherein said information includes load information relating to said receiver.
Claim 10
Dependent Claim 17 words
The system of claim 6, wherein said information includes at least one of time and date information.
Claim 11
Dependent Claim 16 words
The system of claim 1, wherein said binding is to a port at said destination address.
Claim 12
Dependent Claim 23 words
The system of claim 1, wherein said binding is based at least in part upon a random selection of one said destination address.
Claim 13
Independent Claim 87 words
A method for context-dependent binding of a destination name to a destination address in a name resolver having a predetermined set of binding criteria and predetermined correlations of destination names with destination addresses, wherein at least one said correlation is a multiple correlation correlating a plurality of said destination addresses with a single destination name, including the steps of: (1) receiving said request at said name resolver; and (2) based upon said multiple correlation, retrieving at least one said destination address from said plurality of destination addresses.
Claim 14
Dependent Claim 23 words
The method of claim 13, further including after step 2, the step of: (3) binding said retrieved destination address to said destination name.
Claim 15
Dependent Claim 21 words
The method of claim 14, further including after step 3, the step of: (4) transmitting said request with said destination address.
Claim 16
Dependent Claim 18 words
The method of claim 13, wherein said multiple correlation is based upon information explicitly contained within said request.
Claim 17
Dependent Claim 21 words
The system of claim 13, wherein said multiple correlation is based upon at least a portion of contents of said request.
Claim 18
Dependent Claim 39 words
The system of claim 13, wherein said multiple correlation is based upon at least one of: an address of said requester; and a type of service requested by said request; and a quality of service requested by said request.
Claim 19
Dependent Claim 19 words
The system of claim 1, wherein said multiple correlation is based upon information not explicitly contained within said request.
Claim 20
Dependent Claim 41 words
The system of claim 19, wherein said multiple correlation is based upon at least one of: a geographical region of said receiver; load information relating to said receiver; time information; date information; and a random factor generated by said name resolver.
Claim 21
Independent Claim 96 words
A system for name resolution of at least one request directed to a destination name of a receiver and issued from a requester system, the request information relating to caller context, the system including: a name resolver connected to the requester service and including predetermined information correlating a plurality of service names with said caller context; a service selection subsystem configured to provide a selection of at least one said service name based upon said caller context; and a host name selection subsystem configured to return a host name based corresponding to said selected service name.
Claim 22
Dependent Claim 37 words
The system of claim 1, wherein said at least one predetermined criterion includes: a first criterion based upon information explicitly contained within said request; and a second criterion based upon information not explicitly contained within said request.
Claim 23
Dependent Claim 19 words
The system of claim 22, wherein said second criterion corresponds to a predetermined policy used by said name resolver.
Claim 24
Dependent Claim 18 words
The system of claim 23, wherein said first criterion corresponds to information relating specifically to said requester system.

References Cited (Backward Citations)

No citation records indexed.

USPTO Annuity & Maintenance Windows

Maintenance schedule is calculated for granted US utility patents.

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag