Filtering for public databases with naming ambiguities

• US 5,961,645 A
• Filed: 10/01/1996
• Issued: 10/05/1999
• Est. Priority Date: 10/02/1995
• 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:
  US08/724,415
• Time in Patent Office: 1,099 Days
• Field of Search: 395/187.01, 395/188.01, 395/186, 395/200.09, 395/200.03, 380/4, 380/25, 340/825.31, 713/200, 713/201, 713/202, 713/200.09, 713/200.03
• US Class Current: 726/1
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 63/0236 Filtering by address, protocol, port number or service, e.g. IP-address or URL

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 requestor, 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 method for selectively restricting access to a plurality of network resources accessible through a network, comprising 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.

2. The method of claim 1, 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.

3. The method of claim 1, 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.

4. The method of claim 1, 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.

5. The method of claim 4, 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.

6. A public network resource access system comprising:

a processor;

a plurality of network resources coupled to said processor through a firewall;

at least one user terminal coupled to said processor; and

a database coupled to said processor;

wherein said processor is programmed to;

a) receive 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) determine 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) submit said first resource identifier to said network;

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

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

7. The system of claim 6, wherein said processor determines whether to forward said response resource by:

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.

8. The system of claim 6, wherein said processor determines whether to forward said first response resource by:

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.

9. The system of claim 6, wherein said response includes a second resource identifier, and wherein said processor is further programmed to:

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

b) submit said second resource identifier to said network;

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

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

10. The system of claim 9, wherein said processor queries said database using said first and second resource identifiers by:

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.