Filtering for public databases with naming ambiguities

• US 6,092,204 A
• Filed: 06/08/1999
• Issued: 07/18/2000
• Est. Priority Date: 10/01/1996
• Status: Expired due to Term

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Baker, Brenda Sue
• Primary Examiner(s): HUA, LY
• Application Number:
  US09/327,453
• Time in Patent Office: 406 Days
• Field of Search: 713/200, 713/201, 713/202
• US Class Current: 726/5
• CPC Class Codes: G01R 33/4833 using spatially selective excitation of the volume of interest, e.g. selecting non-orthogonal or inclined slices

Abstract

Multiple approaches are used with a filter to handle naming ambiguities when requesting access to a plurality of network resources through a public network such as the Internet. One approach is to consider responses from the public network as well as requested URLs in determining whether to allow or deny resources. The response information used may include header information or the resource itself. If the header information includes a new URL, the new URL can be forwarded to the requester, or submitted to the public network. A permission database is queried to determine whether a resource corresponding to the new URL should be forwarded to the requestor. A checksum database can also be used to determine if a specific resource should be forwarded to the requestor. Another approach is to record and maintain a database of aliases for URLs. When a URL is requested, the alias URLs are determined for that URL. The alias URLs can then be queried in the permission database to determine if the resource corresponding to the aliases can be accessed by the requesting terminal before the URL is requested from the public network.

Claims

1. A filtering device, comprising:

a processor;

a database operably coupled to said processor;

a query module operably coupled to said database and said processor to query said database using a first resource identifier, a first resource corresponding to said resource identifier, and a user identification code; and

a decision module operably coupled to said query module to determine whether to send said first resource to a user corresponding to said user identification code in accordance with said query.

2. The filtering device of claim 1, wherein said database contains a first list of resource identifiers and a second list of resource checksums, and said query module compares said first resource identifier and said first resource to said first and second lists, respectively, and said decision module operates in accordance with said comparison.

3. The filtering device of claim 1, wherein said first resource identifier is a uniform resource locator.

4. The filtering device of claim 1, wherein said first resource is a Hyper-Text Markup Language file.

5. The filtering device of claim 1, wherein said first resource contains a second resource identifier, and further comprising a redirect module operably coupled to said decision module to request a second resource using said second resource identifier.

6. The filtering device of claim 5, wherein said query module queries said database using said second resource identifier and said second resource;

and said decision module determines whether to send said second resource to said user in accordance with said query.

7. A machine-readable medium whose contents cause a computer system to selectively restrict access to a plurality of network resources accessible through a network, by performing the steps of:

a) receiving a request for at least one of said plurality of network resources from a user, said request including a first resource identifier and a user identification code;

b) determining whether to submit said first resource identifier to said network by querying a database using said first resource identifier and said user identification code;

c) submitting said first resource identifier to said network;

d) receiving a first response from said network, said first response including a first response resource; and

e) determining whether to forward said first response resource to said user by querying said database using said first response resource and said user identification code.

8. The machine-readable medium of claim 7, wherein said step of determining using said response resource comprises the steps of:

searching said first response resource for a list of key terms; and

querying said database to determine whether to forward said first response resource to said user, said query based on said search and said user identification code.

9. The machine-readable medium of claim 7, wherein said step of determining using said response resource comprises the steps of:

computing a checksum of said first response resource; and

querying said database to determine whether to forward said first response resource to said user, said query based on said checksum and said user identification code.

10. The machine-readable medium of claim 7, wherein said response includes a second resource identifier, further comprising the steps of:

a) determining whether to submit said second resource identifier to said network by querying a database using said second resource identifier and said user identification code;

b) submitting said second resource identifier to said network;

c) receiving a second response from said network, said second response including a second response resource; and

d) determining whether to forward said second response resource to said user by querying said database using said second response resource and said user identification code.

11. The machine-readable medium of claim 10, wherein said steps of querying using said first and second resource identifiers comprises the steps of:

obtaining an alias of said first and second resource identifiers; and

querying said database to determine whether to submit said first and second resource identifiers to said public network, said query based on said alias and said user identification code.