Apparatus and a process for the retrieval of data in the case of a faulty request on a server in the internet

• US 20020059396A1
• Filed: 09/27/2001
• Published: 05/16/2002
• Est. Priority Date: 09/28/2000
• Status: Abandoned Application

• Current Assignee: Nutzwerk InformationsGmbH
• Original Assignee: Nutzwerk InformationsGmbH
• Inventors: Holzer, Dipl.-Ing. Rene, Wonneberger, Ramona
• Application Number:
  US09/966,943
• Publication Number:
  US 20020059396A1
• Time in Patent Office: Days
• US Class Current: 709/217
• 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/3005 Mechanisms for avoiding name conflicts
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

This invention relates to an apparatus and a process for the retrieval of alternative data in the case of a faulty request by a client on a server in a network (such as the internet). Included is a network interface (12) which enables the stream of data between a client (11) and server (20) to be analysed. The network interface (12) has a processing unit (18) which checks the traffic of data in the case of a faulty request by the client. The error messages from the server will be blocked and replaced by alternative data, based on the nature of the search. This alternative data (19) will then be sent to the client (11) by the network interface (12).

Claims

1. An apparatus for a retrieval of alternative data in the case of a faulty request of a client to a server in a packet-based network,

a. with a network interface which enables a data stream between the client and the server to be analysed,

b. with a processing unit which checks the data stream following the request of the client, wherein a data pattern that indicates an error message from the server is blocked and replaced by alternative data, wherein said alternative data depends on the content and type of request, wherein said alternative data will be sent to the client using the network interface.

3. The apparatus of claim 1 or claim 2, wherein said alternative data will be loaded from a database, and wherein said alternative data is determined by searches on the nature, content, and/or type of the request.

4. The apparatus of claim 3, wherein said database is a common search engine in the internet.

5. The apparatus of claim 1 or claim 2, wherein said client is a client-computer, which is equipped with a client program, like a web browser, an FTP client, and/or a gopher client, and wherein said server is a Domain-Name-Server, a web server, an FTP server, or a gopher server.

6. The apparatus of claim 1 or claim 2, wherein said apparatus is integrated in a proxy, and/or a DNS server, and/or in a client-computer.

7. The apparatus of claim 1 or claim 2, wherein the client'"'"'s request is recorded to determine said alternative data by a search in said database, and wherein information of the recorded request is used.

8. The apparatus of claim 7, wherein said alternative data can be alternative domain names, IP addresses, URLs, and/or data from alternative internet servers such as ad-servers, wherein in the case of a faulty DNS request the error message will be replaced by an IP address, and wherein said IP address refers to a second server which provides a second, more specific piece of alternative information.

9. The apparatus of claim 8, wherein said second server will serve the second alternative data depending on the replaced IP address or depending on the IP address, which shows up on the client'"'"'s computer.

2. An apparatus for a retrieval of alternative data, in particular a proxy, in the case of a faulty DNS or URL request of a client to a server in a IP network,

a. with a network interface which enables a IP data stream between the client and the server to be analysed,

b. with a processing unit which checks the data stream following the DNS or URL request of the client, wherein a data pattern that indicates an error message from the server is blocked and replaced by alternative data, wherein said alternative data is an IP address or a HTML page depending on the content and type of request, wherein said alternative data will be sent to the client using the network interface.

10. A process, for the retrieval of alternative data in the case of a faulty request of a client to a server in a packet-based network,

a. with a step in which a stream of data between said client and said server is analysed,

b. with a further step in which an error message from said server caused by a faulty request of said client is blocked,

c. with a further step in which alternative data is produced, depending on the nature and/or content of said request,

d. with a further step in which said alternative data, not the server'"'"'s original response, will be sent to the client.

12. The process of claim 10 or claim 11, wherein the alternative data is loaded from a data-base, wherein the search is based on information about the request, and wherein the data-base can be based on a common search engine in the internet.

13. The process of claim 10 or claim 11, wherein the client is a computer, which is equipped with a web browser, FTP client, and/or gopher client, and wherein the server is a DNS server, a web server, and/or a gopher server.

14. The process of claim 10 or claim 11, characterized by an integration into a proxy-process or a DNS-resolution-process.

15. The process of claim 10 or claim 11, wherein the request is recorded to enable the search for alternative data based on the recorded information.

16. The process of claim 10 or claim 11, wherein an error message from a DNS server in response to faulty request will be replaced by an IP address, wherein said IP address refers to a certain error-server, which serves depending on the nature and content of the request a second, more specific piece of alternative data.

18. Computer readable disk, characterized by a computer loadable data structure, that enables the computer to execute the processes described in claim 10 or 11.

11. A process, in particular used by a proxy, for the retrieval of alternative data in the case of a faulty DNS request or URL request of a client to a server in a IP network,

a. with a step in which data packets between said client and said server are analysed,

b. with a further step in which an error message from said server in the case of a faulty request by the client is blocked,

c. with a further step in which alternative data in form of an IP address or a HTML page is produced, wherein the alternative data depends on the nature and/or content of said request,

d. with a further step in which said alternative data, not the server'"'"'s original response, will be sent to the client.

17. The process of claim 16, wherein the second, more specific alternative data is related to the IP address of the error-server, wherein the error-server is multihomed, or the more specific alternative data is related to the IP address, which shows up on the client'"'"'s computer.