EP1706832B1 - Verbesserte benutzerschnittstelle - Google Patents

Verbesserte benutzerschnittstelle Download PDF

Info

Publication number
EP1706832B1
EP1706832B1 EP05762142A EP05762142A EP1706832B1 EP 1706832 B1 EP1706832 B1 EP 1706832B1 EP 05762142 A EP05762142 A EP 05762142A EP 05762142 A EP05762142 A EP 05762142A EP 1706832 B1 EP1706832 B1 EP 1706832B1
Authority
EP
European Patent Office
Prior art keywords
server
web
web page
operable
context
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Not-in-force
Application number
EP05762142A
Other languages
English (en)
French (fr)
Other versions
EP1706832A1 (de
Inventor
Simon Richard Barefruit Limited EDGE
Shane Lee Barefruit Limited AMBRIDGE
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Barefruit Ltd
Original Assignee
Barefruit Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from GB0416405A external-priority patent/GB2421322A/en
Application filed by Barefruit Ltd filed Critical Barefruit Ltd
Publication of EP1706832A1 publication Critical patent/EP1706832A1/de
Application granted granted Critical
Publication of EP1706832B1 publication Critical patent/EP1706832B1/de
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/567—Integrating service provisioning from a plurality of service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • This invention relates to an improved user interface for a telecommunications apparatus that can receive data from, and transmit data to, other telecommunication apparatuses. More particularly, but not exclusively, the invention relates to an improved user interface for an Internet web browser.
  • the user when a user uses a web browser to view internet pages, the user will type the web page address (also known as a Uniform Resource Locator or "URL") into the web browser.
  • the user may use a "bookmark" specifying a web page address.
  • the web page address both specifies a particular machine connected to the internet, and also specifies a particular web resource (such as a specific web server name or specific web page) on that machine.
  • the web browser transmits a request for the desired page to the web server, as a result of which the web server returns information to the web browser that defines the appearance of the web page.
  • the web address validly specifies the internet address of a web server but does not validly specify a web page on the particular web server.
  • the user may either (i) incorrectly enter the internet address of the desired page, or (ii) may enter the resource address (path) of a web page that previously existed but no longer exists.
  • the web server will return an error code to the user's web browser.
  • a typical error code is hyper text transfer protocol (HTTP) "404 Not Found” although there are also various other error codes such as "410 Gone".
  • HTTP hyper text transfer protocol
  • a user receiving such messages thus learns only that the specified web page does not exist, without any further reasons or useful information being provided.
  • the web server may direct a user to the website's homepage, in the event that the user requests a page that is not available on the server, but this is usually of limited usefulness or interest to the user whose actions in specifying a particular web page within a web site are typically indicative of a specific interest.
  • Document US 2002/059396 A1 discloses a system wherein a user is provided with a list of alternative web page addresses in case the user types incorrect address of a web page into a web browser.
  • URL of the requested web page is analysed in order to provide alternative web page addresses.
  • an error code receiver as set out in claim 37.
  • a method of providing a user with a user interface as set out in claim 61.
  • An advantage of the present invention is that rather than merely presenting the user with an error code indicating that the requested web page could not be retrieved, the user is presented with one or more alternative links that are relevant to the web page that the user was attempting to view. The user can then click on one or more of the links. Thus, the invention can provide constructive suggestions of alternative web pages when the originally requested web page does not exist.
  • Figure 1 shows a system 100 according to a first example that is not an embodiment of the invention but which provides background information relevant to embodiments of the invention.
  • the system 100 comprises a user's personal computer (PC) 101.
  • the user's PC 101 has standard accessories such as a mouse (not shown), a keyboard 103 and a screen 104 that can be used for displaying web pages.
  • the user's PC 101 also has a modem 105 which allows the user's PC 101 to be connected to the internet.
  • the user's PC 101 is a desktop PC although in other embodiments, the user's PC 101 could, for example, be a mobile telephone or a personal digital assistant (PDA).
  • PDA personal digital assistant
  • the user's PC 101 is provided with web browser software 110.
  • the web browser software 110 may, for example, be the Microsoft (RTM) Internet Explorer (RTM) , Netscape Navigator (RTM) or Mozilla (RTM) .
  • RTM Internet Explorer
  • RTM Netscape Navigator
  • RTM Mozilla
  • a user enters a URL for a web page, usually via keystrokes on the keyboard 103. This results in the browser software sending a request to the web server specified by the entered URL. Where such a URL exists, that web server returns instructions to the browser software 110 at the user's PC 101, and that browser software 110 interprets the received information and then displays the requested web page on the screen 104.
  • HTTP hypertext transfer protocol
  • IP Internet Protocol
  • a preliminary step when a user requests a web page, is usually for the browser software 110 to access a remote domain name server (DNS) which resolves the textual web address (a fully-qualified domain name, or FQDN) entered by the user into its IP address.
  • DNS remote domain name server
  • This IP address is then returned by the DNS to the browser which then sends the request for a particular page to the resolved IP address.
  • One or more web resources may be present at the resolved IP address, for example two web servers for unrelated web sites may both be accessible at the same IP address.
  • the textual form of the FQDN (rather than the IP address which is the resolved form) is used by the web server to select a web site; the rest of the URL (the path part or resource specifier) selects a particular page on that site.
  • Errors in a web page (or URL) as requested by a web browser that cause the web page to be unavailable to the web browser may be in the domain name and/or in a particular web page specified as residing at the domain name.
  • the web browser software 110 sends an HTTP request 130 to the web server 120 (having initially obtained a resolution of the URL into an IP address as defined above).
  • the web server 120 receives the request for the information (the page) sought, but (in this hypothetical example), finds that the requested page is not available.
  • the web server 120 therefore returns an HTTP status code to the web browser software 110 at the user's PC 101, indicating that the requested web page could not be found.
  • An example of an HTTP status code is "404 Not Found". This status code indicates that the requested web page could not be found; there are alternative HTTP status codes which can be used by the web server 120 to indicate whether the requested web page is temporarily or permanently unavailable on the web server 120.
  • plug-in 111 is instead employed to enhance the functionality of the browser in handling such errors, as will be explained below.
  • Plug-ins such as plug-in 111 are pieces of software that augment the web browser software 110.
  • a browser helper object BHO
  • BHO could be used as a plug-in for Microsoft (RTM) Internet Explorer (RTM) .
  • the web browser software 110 would simply display an indication that the requested page could not be found on the server, together with the HTTP status code (e.g., "404 Not Found”).
  • the plug-in 111 modifies the behaviour of the web browser software 110 when an appropriate HTTP status code such as "404 Not Found” is received. Specifically, the plug-in 111 detects the HTTP status code and prevents the web browser software 110 from displaying the normal "404 Not Found” error display.
  • the plug-in 111 causes the web browser software 110 to send an HTTP request 132 to a helper web server 140 which is typically remote from both the web server 120 hosting the URL which could not be located, and the user's PC 101.
  • the HTTP request 132 includes the URL of the web page that was not available on the web server 120.
  • the helper web server 140 operates in conjunction with the plug-in 111 to provide the user with an alternative, improved display of information, as set out below.
  • the helper web server 140 includes analysis software 141 that analyses the address contained in the HTTP request 132 in order to determine the context of the page that was not available on the web server 120.
  • the analysis software 141 analyses the web address of the web server 120 and also analyses the address of the web page that could not be found on the web server 120, and determines that the context of the missing web page involves the keywords: "chemical”, “elements", “hydrogen”, “atomic” and “weight”.
  • Software and algorithms for determining the context of information are, as such, well known in the art. For example, some known algorithms assess the number of links to a web page, and the sources of those links, in order to determine the context of the information; some others employ techniques based on word stemming. The details of the algorithm(s) used by the analysis software employed here do not form part of the present invention and will not be discussed further.
  • the helper web server 140 also includes index database software 142 which is used to identify web pages on other web servers (i.e. on web servers other than the web server 120 and the helper web server 140) that could be relevant to the context of the missing web page.
  • the index database software 142 comprises a database that lists potentially relevant web sites for each term in the database.
  • the index database software 142 may have several entries that are related to the field of chemistry. For the word “elements”, the index database software 142 may have some entries that are relevant to chemistry and some that are not relevant to chemistry. An example of an entry in the index database software 142 for the word "element” that is not relevant to the field of chemistry would be a web page entitled “elements of modern dance” which, in this example, would be related to choreography and not to chemistry.
  • the index database software 142 uses the key words extracted by the analysis software 141 to produce a list of potentially relevant web pages. The list produced may be ordered/ranked by the anticipated relevance of the web pages to the key words.
  • a web page having the key words “atomic”, “weight” and “hydrogen” may be ranked higher than a web page having the key words “chemical”, “elements”, “hydrogen” and “weight” even though the latter web page has four of the key words rather than three of the key words.
  • the details of the ranking algorithms employed here do not form a part of the present invention and will not be described further. Ranking algorithms are, as such, known in the art, and the details of the ranking algorithm(s) employed here do not form part of the present invention and will not be discussed further.
  • the ranked list of potentially relevant websites produced by the index database software 142 is then passed to web page creation software 143.
  • the web page creation software 143 also forms part of the helper web server 140.
  • the web page creation software 143 dynamically generates a web page that is sent as an HTTP response 133 to the user's PC 101.
  • the web browser software 110 interprets the HTTP response 133 and displays the web page on the display 104 of the user's PC 101.
  • the web page creation software 143 does not retrieve a pre-defined web page, but that the web page creation software 143 generates a web page on the basis of the context that was determined by the analysis software 141 and by the links as determined and ranked by the index database software 142.
  • the web page that is generated by the web page creation software 143 will usually be particular to a given context.
  • the plug-in 111 is able to detect the receipt of the HTTP "404 Not Found" or similar response from the web server. The plug-in 111 then causes the user's PC 101 to contact the helper web server 140 so that a dynamically generated web page, that is relevant to the context of the unavailable page, is displayed on the screen 104 of the user's PC 101.
  • Figure 5 shows an example of a web page 500 that is displayed on the screen 104 of the user's PC 101 once the HTTP response 133 has been received by the user's PC 101 and interpreted by the web browser software 110.
  • the web page 500 contains a message field 501, which provides the user with an informative message, and also contains a back button 502 and a link field 503.
  • the message is:
  • the back button 502 allows the user to move back through his history of previously viewed web pages.
  • the link field 503 provides the user with a ranked list of suggested links that may be of relevance to the context of the user.
  • the link field 503 contains two links, link 503.1 and link 503.2.
  • the title of the web page pointed to by the respective links is given, followed by the respective key words that are present on the respective web page followed by the internet address of the respective web page.
  • the link 503.1 is a web page that is relevant to the properties of hydrogen.
  • the web address gives the web server and the address of the web page on the web server.
  • Link 503.2 is concerned with a choreography web page.
  • Link 503.2 is displayed below link 503.1 as, according to the ranking formed by the index database software 142, link 503.2 is considered less likely to be relevant to the user than the link 503.1.
  • the link 503.1 specifies the internet address of the web page that the user wishes to view.
  • the page may be found on a linked server 150.
  • the linked server 150 in this embodiment is not typically a part of the web server 120 or the helper web server 140; instead, the database of the index database software 142, held on the helper server 140, contains an internet link to the linked server 150.
  • the link 503.1 specifies the internet address of linked server 150 and also specifies the location on the linked server 150 where the page may be found.
  • the web browser software 110 sends an HTTP request 134 to the linked server 150.
  • the linked server 150 returns an HTTP response 135 which defines the required web page.
  • the web browser software 110 interprets the web page defined by the HTTP response 135 and displays the requested web page on the screen 104 of the user's PC 101.
  • the plug-in 111 and the helper web server 140 can improve the web browsing experience of a user by, instead of merely presenting the user with a HTTP "404 Not Found” message, presenting the user with a list of potentially relevant links for the user to click on.
  • Figure 2 shows a system 200 according to a first embodiment of the invention. Many of the components of the system 200 are identical to components of the system 100. The parts in common have therefore retained the same reference numerals that were used in Figure 1.
  • system 200 caters for the situation where a user clicks on a link provided by a "linking web server" 201 which points to a link that does not exist on the web server 120.
  • the system 200 is also able to collect information that may be used to improve the relevance of the links presented to the user, or for other purposes.
  • the user types the internet address (URL) of a website on the linking web server 201 into the web browser software 110 via the keyboard 103.
  • the web browser software 110 sends an HTTP request 202 to the linking web server 201.
  • the requested page on the linking web server 201 is found, so the linking web server 201 responds with an HTTP response 203.
  • the web browser software 110 interprets the web page defined by the HTTP response 203 and displays the web page on the display 104.
  • the displayed web page includes one or more faulty links. By faulty links, it is meant that the link is either incorrect or that the link points to a page that is no longer available.
  • the user clicks on one of the faulty links (which, of course, he does not know to be faulty as a rule).
  • the web browser software 110 sends an HTTP request 130 to the remote web server 120 where the website of the missing page or broken link is held.
  • the web server 120 determines that the requested page is not available and returns an HTTP "404 Not Found" response 131 to the web browser software 110.
  • the system 200 has a plug-in 211 which is similar to the plug-in 111 but includes a participant ID 212.
  • the participant ID 212 is a piece of data that identifies the organisation that supplied the plug-in 211 to the user.
  • the plug-in 211 is arranged to be able to transmit the participant ID 212 to a helper server 240.
  • the helper server 240 is similar to the helper server 140 of the system 100 but includes participant monitoring software 242 for analysing the various participant IDs 212 of different users. Although for clarity only a single user's PC 101 is shown in system 200, multiple users, using respective PCs, can simultaneously use web browser software 110 at their respective PCs together with respective plug-ins 211.
  • the plug-ins 211 are substantially identical but are provided with different participant IDs 212, depending on whichever organisation supplied a plug-in 211 to a user.
  • the plug-in 211 when the plug-in 211 detects that an HTTP "404 Not Found" response 131 has been received from the web server 120, the plug-in 211 causes the web browser software 110 to send an HTTP request 232 to the helper web server 240.
  • the HTTP request 232 is similar to the HTTP request 132 of system 100 but includes the participant ID 212.
  • HTTP request 232 For the system 200, an example of the HTTP request 232, is as follows:
  • the helper web server 240 uses the HTTP request 232 to deduce the context of the missing web page.
  • the participant monitoring software 242 that forms part of the helper server 240 records the participant ID 212 of the plug-in 211 that caused the HTTP request 232 to be sent.
  • the participant ID 212 has a value of "123456".
  • the helper server 240 comprises analysis software 241 that is similar to the analysis software 141 of the system 100. However, the analysis software 241 obtains, by virtue of the extra information provided in the HTTP request 232 (compared to the HTTP request 132), enhanced information regarding the context of the web page that the user attempted to view.
  • the analysis software 241 uses the "referrer" information in the HTTP request 232 to send an HTTP request 220 to the linking web server 201.
  • the HTTP request 220 requests the web page, from the web server 201, that contained the erroneous link to a page on the web server 120.
  • the linking web server 201 responds with an HTTP response 221.
  • the HTTP response 221 includes information which defines the appearance and content of the web page that was displayed on the display 104 of the user's PC 101.
  • the analysis software 241 does not actually display the web page defined by the information in the context HTTP response 221 but analyses the information to determine keywords in the vicinity of the link.
  • Figure 6 shows an example of a web page 600 as it could be displayed (the analysis software would not usually display the web page 600) on the display 104 of the user's PC 101.
  • the analysis software 241 analyses the web page 600 to determine the location of the link that pointed to the non-existent web page on the web server 120.
  • the link is denoted by the reference numeral 601.
  • the words in the vicinity of the link 601 contains various keywords that are relevant to the context of the link 601.
  • the analysis software 241 analyses these keywords to determine appropriate key words.
  • Various methods for analysing and indexing key words on web pages are known in the art.
  • the analysis software 241 determines key words 602 that are to be used by the index database software 142.
  • the analysis software 241 also analyses the web address of the web page 600 for relevant key words. The results of the analysis are passed by the analysis software 241 to the index database software 142. The index database software 142 then produces a list of one or more links that are anticipated to be relevant to the user.
  • system 200 uses the participant ID 212 to obtain further context information.
  • the participant monitoring software 242 comprises a database that relates participant IDs to whichever organisation supplied the plug-in 211 to the user.
  • the participant ID 212 has a value of "123456" which indicates that the plug-in 211 was supplied to the user by a hypothetical organisation called "Industrial Chemistry Organisation". It is likely that the user has some affiliation with the hypothetical society of "Industrial Chemistry Organisation" and this provides additional context information, namely that the expected context is the field of chemistry.
  • the participant monitoring software 242 passes to the index database software 142 information indicating the expected context.
  • the list of potentially relevant websites that is created by the index database software 142 is passed to the web page creation software 143 which then sends an HTTP response 233 to the web browser software 110.
  • the HTTP response 233 includes information defining a web page; the web browser software 110 interprets the information and displays the web page on the display 104.
  • the displayed web page is similar to that shown in Figure 5 but is more focused towards what is deemed by the analysis software 241 and the index database software 142 to be the likely context of the user.
  • the HTTP response 233 is similar to the HTTP response 133 of the system 100 but, whereas the web page defined by the HTTP response 133 included a link that pointed directly to the linked server 150, the web page defined by the HTTP response 233 has links to the helper server 240.
  • the links point to the helper server 240 rather than the linked server 150, the links contain information which allows the helper server 240 to direct the web browser software 110 to the linked server 150. The way in which the helper server 240 processes these links will now be discussed.
  • HTTP request 234 For the system 200, an example of the HTTP request 234 is as follows:
  • the HTTP request 234 specifies the web address of the helper server 240 and also contains, as parameters, the web address of the linked server 150 and the participant ID 212.
  • the helper server 240 includes tracker software 243.
  • the tracker software 243 determines that the participant ID is "123456".
  • the tracker software 243 maintains a count of the number of times that an HTTP request 234 is received for each participant ID 212. Thus, each time that the user of the PC 101 clicks on a link received from the helper server 240, the tracker software 243 will increment by 1 a tally for the participant ID "123456". When other users click on such links, the respective tally for the other participant IDs will be increased by 1. Thus, the tracker software 243 allows the helper server 240 to determine how many "clicks" are received from each of the organisations that can distribute plug-ins 211.
  • the helper server 240 also includes re-direction software 244.
  • the re-direction software 244 extracts the parameter specifying the web address of a page on a linked server 150.
  • the re-direction software 244 then sends an HTTP response 235 to the web browser software 110.
  • the HTTP response 235 includes an HTTP re-direction status code (e.g. "302 Moved Temporarily", which is always followed by a "Location:" header field) which indicates to the web browser software 110 that the web browser software 110 should look for the web page (that is, the web page requested by the HTTP request 234) at another location.
  • the other location is specified by, in this example, the "Location:" header field of the HTTP response 235.
  • the web browser software 110 on receipt of the HTTP response 235, sends an HTTP request 134 to the linked server 150.
  • the linked server 150 responds with an HTTP response 135 and causes a web page to be displayed on the display 104 of the user's PC 101.
  • An advantage of the inclusion in the HTTP request 232 of the participant ID 212 is that the participant monitoring software 242 can improve the context that is used by the index database software 142.
  • the participant ID 212 is omitted from the HTTP request 232 and the participant monitoring software 242 is dispensed with.
  • the participant monitoring software 242 is used, in conjunction with the analysis software 241 and the index database software 142, to either enhance the ranking of "favoured" linked servers 150 or is used to prevent links to one or more "non-favoured" linked servers 150 from being presented to the user.
  • the plug-in 211 is arranged so that the participant ID 212 is not included in the HTTP request 234, in which case the tracker software 243 of the helper server 240 could be dispensed with.
  • the inclusion of the participant ID 212 in the HTTP request 234 and retention of the tracker software 243 is preferred.
  • the use of the participant ID 212 tracker software 243 allows the helper server 240 to count how many links have been provided to a particular linked server 150, and also to determine the participant ID 212 of the plug-in 211 that was used to access a particular linked server 150. This allows the owners of the helper server 240 to obtain financial revenue from owners of linked servers 150 and to share the revenue with the organisations that provide the plug-in 211 to users.
  • Figure 2 shows only a single linked server 150.
  • the index database software 142 contains information that specifies the web address of a web page on a particular linked server 150.
  • the index database software 142 may have links to a plurality of web pages that are retrievable from a particular linked server 150.
  • the links may also include links to other web pages, that can be retrieved without a "404 Not Found" error, on the web server 120.
  • the owners of the helper server 240 have concluded agreements with the respective owners of various linked servers 150 so that, for each "click-through" to a linked server 150 that results from the use of a plug-in 211 and the helper server 240, the owner of the respective linked server 150 provides a payment to the owner of the helper server 240.
  • the owners of the helper server 240 have concluded agreements with one or more organisations that are prepared to distribute plug-ins 211, where each of the organisations is allocated a respective participant ID 212 (e.g. "123456" or "111222") to distinguish the plug-ins 211.
  • the tracker software 243 and the re-direction software 244 each counts how many click-throughs have been passed to each linked server 150.
  • the owners of the helper server 240 can provide the organisations C and D with a portion of the remuneration received from the owners A and B, in proportion to the number of click-throughs resulting from (i) the plug-in 211 having the participant ID of "123456", and (ii) from the plug-in 211 having the participant ID 212 of "111222".
  • the organisations C and D are encouraged to distribute plug-ins 211 with the respective participant IDs 212 to users.
  • the participant ID 212 is not included in the HTTP request 234; similarly, the tracker software 243 may be dispensed with.
  • FIG. 3 shows a system 300 according to a second embodiment of the invention.
  • the system 300 is in some ways similar to the system 200 and like reference numerals are again employed for like components.
  • the system 300 includes a proxy web server 301.
  • Proxy servers are used by some internet service providers (ISPs) as gateways between individual subscribers of the ISP (e.g. home users) and the internet. Proxy servers are also used by some businesses as an interface between the PCs used by their staff, and the internet. Proxy servers can provide increased security by incorporating a virus scanner and increased performance by caching information. All web (HTTP) communication between the user's PC 101 and the internet is through the proxy server 301 which receives HTTP requests from the user's PC 101 and then relays them to other web servers on the internet. HTTP responses from the other web servers on the internet are received by the proxy server 301 which then relays them to the user's PC 101.
  • ISPs internet service providers
  • HTTP HyperText Transfer Protocol
  • the helper web server 340 of the system 300 does not count the number of click-throughs to linked servers 150.
  • modified index database software 342 is used instead of the index database software 142.
  • the index database software 342 also stores "linked IDs" 312 which allow linked servers 350 to count how many click-throughs they have received from the helper server 340.
  • the linked servers 350 are similar to the linked servers 150 but include tracker software 343 for counting the number of click-throughs received.
  • the user of the PC 101 either types in a web address into the web browser software 110 or clicks on a link to the linking web server 201.
  • the HTTP request 202 is intercepted by the proxy server 301 which modifies the header of the HTTP request 202 and sends a new HTTP request 302 to the linking web server 201.
  • the linking web server 201 responds with a HTTP response 203 which is intercepted by the proxy server 301.
  • the proxy server 301 modifies the header of the HTTP response 203 and sends a HTTP response 303 back to the web browser software 110.
  • a similar sequence of events occurs for HTTP requests 130 and 330.
  • a "proxy add-in" 311 modifies the behaviour of the proxy server 301.
  • the proxy add-in 311 is a piece of software (in this embodiment) or hardware that modifies the behaviour of the proxy server 301 when an HTTP "404 Not Found" or similar status code is received. Thus, the proxy add-in 311 performs a function that is in some ways equivalent to the plug-in 111 and the plug-in 211 of the systems 100 and 200.
  • the proxy add-in 311 is typically supplied to the owner of the proxy server 301 by the owner of the helper server 340. Whenever the proxy server 301 receives an HTTP "404 Not Found" response 131 from a web server 120, the proxy add-in 311 causes the proxy server 301 to generate a HTTP re-direct response 331 and send it to the web browser software 110.
  • the HTTP re-direct response 331 includes the web address of the page on the linking web server 201 that has an erroneous link to a page on the web server 120, and the web address of the missing page on the web server 120.
  • the web browser software 110 on receipt of the HTTP redirect response 331, sends an HTTP request 132 to the helper web server 340 via the proxy server 301.
  • the HTTP request 132 is received by the helper web server 340 as HTTP request 332.
  • the HTTP requests 132 and 332 both include as parameters the web address of the page on the linking web server 201 that contained an erroneous link to a page on the linked web server 120, together with the address of the missing page on the web server 120.
  • the helper web server 340 extracts from the HTTP request 332 the web address of the page on the linking web server 201. As for the system 200, the helper web server 340 sends an HTTP request 220 to the linking web server 201 and receives an HTTP response 221. As for the system 200, the analysis software 241 determines the context of the missing web page and passes context information to index database software 342.
  • the index database software 342 includes a database of web pages on linked servers 350.
  • the index database software 342 also includes one or more linked IDs 312.
  • the linked IDs 312 are provided to the owner of the helper web server 340 by the respective owner(s) of the linked servers 350.
  • each owner of a linked server 350 supplies the owner of the helper server 340 with a linked ID 312 that is unique to the owner of the helper server 340.
  • the one or more linked IDs 312 allow the owner(s) of linked servers 350 to distinguish click-throughs from the helper server 340 with click-throughs from other web servers (not shown).
  • the linked server 350 counts the number of linked IDs 312 that it receives.
  • the owner of the helper web server 340 has been allocated a linked ID 312 having the value of "123321".
  • a counter (not shown) is incremented.
  • this counter allows the owner of the linked server 350 to determine how many click-throughs have originated from the helper web server 340.
  • the owner of the linked server 350 remunerates the owner of the helper web server 340.
  • the web page creation software 143 generates a web page and this web page is sent as an HTTP response 133 to the user's PC 101 via the proxy server 301.
  • the HTTP response 133 is received by the user's PC 101 as HTTP response 333.
  • a web page is displayed on the display 104 of the user's PC 101.
  • the web page includes one or more links. Each of the one or more links points to a linked server 350.
  • Each of the links also includes, as a parameter, the linked ID 312 that has been allocated by the owner of the respective linked server 350 to the owner of the helper web server 340.
  • HTTP request 334 is sent from the user's PC 101 via the proxy server 301, and is received by the linked server 350 as an HTTP request 334A.
  • the HTTP request 334 is similar to the HTTP request 134 of the systems 100 and 200 but includes, as a parameter, the value of the linked ID 312, i.e. "123321".
  • the linked server 350 includes tracker software 343 that analyses the linked ID parameters that are contained in HTTP requests. Each time that the linked server 350 receives an HTTP request with a linked ID of "123321", the tracker software 343 increments a counter, indicating that a click-through has been received under the auspices of the helper web server 340. In response to the HTTP request 334A, the linked web server 350 sends an HTTP response 135 via the proxy server 301, to the user's PC 101, where it is received as an HTTP response 135A.
  • the proxy add-in 311 of the system 300 does not store a participant ID 212.
  • the proxy add-in 311 stores a participant ID 212 which is conveyed to the helper server 340. This allows the helper server 340 to distinguish between proxy servers 301 owned by different organisations. By counting, for each value, e.g. "123456", the number of participant IDs 212 received, the owner of the helper server 340 can remunerate the owners of the proxy servers 301 in proportion with the number of click-throughs. Of course, this alternative embodiment cannot track whether or not an HTTP request 332 actually resulted in a click-through.
  • the proxy add-in 311 is modified so that HTTP requests 334 are monitored, thus allowing the modified proxy add-in 311 to determine the remuneration appropriate to each of the respective owners of the participating proxy servers 301.
  • Figure 4 shows a system 400 according to a third embodiment of the invention.
  • the system 400 has a web server 420.
  • the web server 420 is similar to the web server 120 but includes an error handler 411.
  • the error handler 411 modifies the behaviour of the web server 420, compared to the behaviour of the web server 120, when a requested web page cannot be retrieved from the web server 420.
  • the error handler 411 modifies the behaviour of the web server 420 so that rather than returning an HTTP status code such as "404 Not Found", the web server 420 returns an HTTP response 431 which includes an HTTP re-direction status code (e.g.
  • the HTTP response 431 causes the web browser software 110 to send an HTTP request 132 to a helper server 440.
  • the helper server 440 is in communication with an auxiliary server 460.
  • the auxiliary server 460 includes analysis software 241, index database software 142 and web page creation software 143.
  • the helper server 440 differs from the helper servers 140, 240, 340, it is able to provide, in effect, similar functionality in conjunction with the auxiliary server 460.
  • the helper server 440 acts as a proxy server for the auxiliary server 460.
  • the helper server 440 sends an HTTP request 220 to the linking web server 201 which responds with an HTTP response 221 to the helper server 440.
  • the web page creation software 143 of the auxiliary server 460 then generates a web page and sends, via the helper server 440, an HTTP response 133 to the web browser software 110. If the user clicks on a link then an HTTP request 134 is sent to the linked server 150 which replies with an HTTP response 135, thereby causing a web page from the linked server 150 to be displayed on the display 104 of the user's 101.
  • the error handler 411 is arranged to include a participant ID 212 which is included in the HTTP response 431 and thus conveyed to the helper server 440.
  • the index database software 142 of the auxiliary server 460 is replaced with the index database software 342 which includes linked IDs 312.
  • the helper server 440 further includes tracker software 243 and re-direction software 244.
  • the plug-in 111, 211, proxy add-in 311 or error handler 411 detected that a signal (such as the HTTP status code "404 Not Found") that indicated that a web page requested by the user could not be displayed on the web browser 110/display 104 of the user's PC 101. In some situations, an error may occur without an HTTP status code being generated.
  • a signal such as the HTTP status code "404 Not Found"
  • the errors in such situations are detected by the plug-in 111, 211, proxy add-in 311 or error handler 411, as appropriate, and used to activate the analysis software 141, the index database software 142 and the web page creation software 143.
  • the plug-in 111, 211, proxy add-in 311 or error handler 411 are modified by the plug-in 111, 211, proxy add-in 311 or error handler 411.
  • the plug-in 111, 211 or proxy add-in 311 will receive an error code from the DNS server and behaves as if an HTTP 'Host not found' error has occurred.
  • a standard web proxy server i.e. a proxy server that does not include the proxy add-in 311
  • that standard proxy server will convert its received DNS error message to an HTTP error message and send that back to the web browser 110 or proxy server 301.
  • the plug-in 111, 211 or proxy add-in 311 will then be informed of the HTTP status code as usual.
  • the web browser 110 or proxy server will fail to establish a connection to the non-existent web server 120.
  • Server is not a web server
  • the server 120 may ignore requests completely which would result in case 2.1 or it may return ICMP 'Protocol unreachable' or ICMP 'Port unreachable' which can be handled as in 2.2.
  • Figure 7 shows a system 700 according to a fifth embodiment of the invention.
  • the system 700 has many features in common with the system 100 that was described earlier.
  • the helper server 140 of the system 100 is replaced by a helper server 740.
  • the helper server 740 is similar to the helper server 140 but is also arranged to communicate with a "who is" server 701 and a "what is” server 702.
  • the system 700 allows additional information to be obtained about the context of a failed HTTP request 130.
  • the system 100 as described above analysed the textual form of the URL of the web server 120 to determine keywords (e.g. "chemical” and "elements").
  • keywords e.g. "chemical” and "elements”
  • the analysis of keywords of a URL may provide sufficient context information, in other situations more context information may be required in order to provide a user of the system with links to alternative web pages that are of sufficient relevance.
  • the web server 120 returns an HTTP response 131 which includes the HTTP status code "404 Not Found". (Note that this is a hypothetical example, the actual www.elephant.co.uk website does not return a 404 HTTP status code but instead displays a page indicating that the "this_page_does_not_exist.html" page could not be found.)
  • the plug-in 111 then sends an HTTP request 132 (which includes the web address) to analysis software 741 of the helper server 740.
  • the analysis software 741 is similar to the analysis software 141 but is arranged to attempt to obtain further information regarding the context of the web page that could not be found. For example, a naive analysis of the context of the web address above for natural language keywords might suggest that the context of the web page is pachyderms (i.e. animals such as elephants having a thick skin).
  • the analysis software 741 sends the FQDN (i.e. www.elephant.co.uk) as part of an HTTP request 730 to a "whois" server 701.
  • the whois server 701 provides information regarding the person or organisation that has registered the domain name www.elephant.co.uk.
  • An example of a whois server 701 is the whois server at the following web address:
  • the whois protocol is defined by the IETF in RFC 3912 (see http://www.ietf.org/rfc/rfc3912.txt).
  • RFC3912 defines the whois protocol which is independent of HTTP. Therefore depending upon the whois server chosen for helper server 740, request/response pair 730/731 may use a custom HTTP-based format as illustrated for SamSpade or they may use the defined whois format from RFC3912.
  • the analysis software 741 receives an HTTP response 732 from the whois server 701.
  • the HTTP response 732 includes the following information:
  • the context analyser 741 analyses the HTTP response 732 for keywords and on finding the keyword "insurance” (in this case, as part of the name of the registrant), determines that the context of the hypothetical web page that could not be retrieved is in fact insurance and not pachyderms.
  • system 700 can provide an improvement in the relevance of the links in the HTTP response 133.
  • the HTTP response 731 from the whois server 701 included sufficient context information.
  • the response from the whois server 701 may contain the name and address of the registered owner of a domain name but might not include keywords such as insurance.
  • the whois response for the domain name www.newscientist.co.uk includes the following information:
  • the analysis software 741 extracts, for example, the name of the registrant and sends an HTTP request 732 to the what_is server 702.
  • the what_is server 702 responds with an HTTP response 733 that includes information regarding the context of the registrant. For example, in the United Kingdom the following website:
  • the system 700 may also use the address of the registrant as part of the context information or as part of the query to the what_is server 702. Instead of using www.192.com, the system 700 may be arranged to interrogate an on-line database such as that of Companies House. In the UK, Companies House is an official register which provides details of registered companies.
  • the system 700 may be modified, for example to operate in conjunction with the systems 200, 300, 400.
  • the system 700 may be modified.
  • the analysis software 741 may be modified so that instead of, or in addition to, seeking context information from a whois server 701 or a what_is server 702, the context analysis software 741 may perform a context analysis on some other information resource.
  • the analysis software 741 may be arranged to send an HTTP request to the home page of a website for which a requested page is unavailable (i.e.
  • the analysis software 741 requests the home page from the web site www.elephant.co.uk and performs a context analysis on the home page).
  • the analysis software 741 may perform a context analysis.
  • Some of these on-line resources are of greater use in obtaining context information (that is, context information regarding a web page that could not be sent to a user's PC 101) than other on-line resources.
  • on-line resources may determine which on-line resources provide useful information. For example, a web page chosen at random is unlikely to provide useful context information. Conversely, on-line databases, the home page of a web site or a referring web page (i.e. a web page with a defective link) are likely to provide useful context information.
  • FIG 8 shows a system 800 that may be used to replace the proxy add-in 311 of the system 300.
  • Figure 8 shows an internet content adaptation protocol (ICAP) enabled proxy server 801 and an ICAP server 811.
  • ICAP internet content adaptation protocol
  • Some parts of the system 800 are common with the system 300 and so, for the convenience of the reader, some of the HTTP requests and HTTP responses are shown on Figure 8.
  • ICAP is an IETF standard protocol described in RFC 3507 (http://www.ietf.org/rfc/rfc3507.txt) that allows an Internet proxy server to perform functions such as virus scanning, language translation or content filtering.
  • the ICAP protocol allows proxy servers to send queries to one or more content-adaptation server over a private network (such as an ISP's internal LAN) or over a public IP-based network (such as the public Internet).
  • the proxy server 801 replaces the proxy server 301 while the ICAP server 811 replaces the proxy add-in 311.
  • the ICAP server 811 is a server that is connected to the helper server 340 via the Internet and is connected to the proxy server 801 by an Ethernet link.
  • the ICAP server 811 does not itself need to have a direct connection to the helper server 340, since communication in preferred proxy-based embodiments operates by making the web browser 110 issue HTTP requests by means of HTTP 302 redirect responses.
  • the proxy server 801 includes an ICAP client which communicates with the ICAP server 811.
  • the system 800 may be used to intercept and modify outgoing HTTP requests 130 from a user's PC 101 and/or incoming HTTP responses 131 to the user's PC 101. As some features of the system 800 are similar to those of the system 300, a description of the operation of the system 800 will be provided in terms of the system 300.
  • the proxy server 801 When the proxy server 801 receives the HTTP request 130, the proxy server 801 sends a message 860 over the Ethernet link to the ICAP server 811.
  • the message 860 includes a copy of the HTTP request 130.
  • the ICAP server 811 first checks that the FQDN in the URI of the HTTP request 130 resolves to a real IP address.
  • the ICAP server 811 checks that the FQDN resolves by using a DNS server.
  • An example of a situation where the FQDN would not resolve to a real IP address is if the web site name in the HTTP request 130 has been incorrectly specified such that DNS resolution of the web site name fails.
  • the ICAP server 811 checks whether or not there is a web server 120 listening at the IP address that is given by the DNS resolution. If there is a web server 120 listening then the ICAP server 811 sends a message 861 back to the proxy server 801.
  • the message 861 includes the un-modified HTTP request 130 which is sent by the proxy server 801 as an HTTP request 330 over the Internet to the web server 120.
  • the ICAP server 811 instead of sending a message 861 including the un-modified HTTP request, causes the proxy server 801 to send an HTTP redirect response 331 to the web browser 110 on the user's PC 101.
  • the HTTP re-direct response 331 causes the web browser 110 to send an HTTP request 132 to the helper server 340.
  • the helper server 340 then performs a context analysis as was described above.
  • the ICAP server 811 could be arranged to send a message 861 to the proxy server 801 in which the header of the HTTP request is modified.
  • the proxy server 801 then sends out the modified HTTP request to the internet.
  • the HTTP request is modified so that instead of being addressed to the web server 120, the HTTP request specifies the helper server 340 as the destination.
  • the helper server 340 then performs a context analysis as was described above.
  • the proxy server 801 When the proxy server 801 receives the HTTP response 131 from the web server 120, the proxy server 801 sends a message 871 to the ICAP server 811.
  • the message 871 includes a copy of the HTTP response 131.
  • the ICAP server 811 examines the header of the HTTP response 131 to determine whether the web page (or other resource) that was requested by the user was successfully retrieved from the web server 120. If the status code of the HTTP response 131 indicates that the web page was successfully retrieved then the ICAP server 811 sends a message 872 to the proxy server 801; the message 872 informs the proxy server 801 that the HTTP response 131 should be passed unmodified to the user's PC 101.
  • the ICAP server 811 also examines the length (i.e. the number of characters) of the body (as opposed to the header) of the HTTP response 131. If the length of the body is below a threshold length then the ICAP server 811 sends a message 872 that instructs the proxy server 801 to replace the HTTP response 131 with an HTTP re-direct response 331.
  • the HTTP re-direct response 331 causes the web browser 110 to send an HTTP request 132 to the helper server 340.
  • the helper server 340 then performs a context analysis as was described above.
  • the ICAP server 811 may be arranged to check only the status code of an HTTP response 131 instead of checking both the status code and the body length of an HTTP response 131.
  • the ICAP server 811 communicated with a DNS server and with a web server 120 in order to check that an outgoing HTTP request 130 would be responded to by the web server 120.
  • the ICAP server 811 includes a timer for determining whether too much time has elapsed since either the DNS server or the web server 120 was interrogated. If too much time has elapsed then the ICAP server 811 deems that an error has occurred and causes the proxy server 801 to send an HTTP re-direct response 331 to the web browser 110.
  • web pages comprise a plurality of images.
  • Such web pages contain HTML information that specifies from where the images can be downloaded.
  • the web browser 110 issues an HTTP request for each of the images.
  • the ICAP server 811 ignores the HTTP status of requests for images (e.g. in the file formats .jpg and .png) and executable files (e.g. in the format .exe).
  • the proxy server 801 it is possible to configure the proxy server 801 not to query the ICAP server 811 at all.
  • the URL may not indicate the data type and the ICAP server 811 has to make the determination.
  • One method is to examine the text of previously returned HTML pages for the URLs of embedded objects and to store these in a database for a set period of time. When the ICAP server subsequently receives the request for the embedded object, it can detect them from the database. (To prevent the database from growing indefinitely, older URLs may be discarded once they have been there for a certain amount of time. This kind of cache management is well known in the art.)
  • the systems 100, 200, 300, 400, 700 and 800 described above obtained context information from either (i) the FQDN, (ii) a web page with a defective link or (iii) from an auxiliary server (such as the whois server 701 or the what is server 702).
  • an auxiliary server such as the whois server 701 or the what is server 702.
  • the systems are modified so that as well as, or in addition to, obtaining context information from those sources, the systems also attempt to obtain context information from the home page of the web site with the unobtainable web page. For example, suppose the user either types in a URL, or clicks on a link, for example the hypothetical web page:
  • the context analyser e.g. the analysis software 141
  • the context analyser sends an HTTP request to the web site and performs a context analysis on the web page that is returned by the website.
  • context information from an auxiliary server a two step process may need to be performed.
  • the context analyser sends an HTTP request to the auxiliary server and receives an HTTP response from the auxiliary server.
  • the HTTP response may define a web page that includes one or more fields.
  • the whois server 701 may have a field in which a user (or a computer) can enter a domain name. Once the user (or a computer) has entered a domain name and pressed the "Enter" key, the whois server 701 replies with a dynamically generated HTML web page which includes context information. The context analyser then analyses the dynamically generated HTML web page for, for example, keywords.
  • the systems 100, 200, 300, 400 integrated the analysis software 141, 241, the index database software 142, 342 and the web page creation software 143 with the helper server 140, 240, 340.
  • the helper server does not include that functionality but instead has communication links to other servers which implement the required functionality.
  • the helper server on receipt of an HTTP request 232 and a HTTP response 221 communicates the information to "context" software which deduces the context and returns the context to the helper server.
  • the helper server then communicates the context to a database server which provides details of the relevant links directly to a web page creation server.
  • the web page creation server then generates the required web page and sends this to the helper server for transmission to the web browser software 110.
  • the systems 100, 200, 300, 400 do not typically communicate the internet protocol (IP) address of the user's PC 101 to the helper server 140, 240, 340, 440.
  • IP internet protocol
  • the user's IP address is sent as a parameter to the helper server. This is used to improve the context information by taking account of the approximate geographic location of the user's PC 101. This allows the relevance of, for example, credit cards or other financial services to be improved, or allow appropriate retailing of heavy or bulky goods, or of language translation services.
  • the helper server is arranged to cache requests and indexing so as to improve the speed of response to the user. For example, if a web server 120 becomes temporarily unavailable, it is possible that different users will attempt to access pages on the web server 120 and thus similar "404 Not Found" errors will repeatedly occur.
  • the plug-in 111, 211, or the proxy add-in 311 generates a persistent "globally unique identifier" that uniquely identifies a particular user.
  • the globally unique identifier cannot be traced to an individual, thereby ensuring privacy.
  • the helper server can take account of the browsing habits of the user, thus improving the context and thus relevance of the links presented to the user.
  • the globally unique identifier may be implemented as persistent cookies on the user's PC 101.
  • the participant ID may be stored as a persistent cookie on the user's PC 101.
  • the participant ID is not used to record which organization distributed, say, the plug-in 211 to the user but is used as a persistent globally unique identifier or to categorise the user according to a stereotype, for example to indicate that the user tends to be interested in chemistry or choreography.
  • a combination of the systems 100, 200, 300 and 400 are simultaneously present.
  • a user's PC 101 having a plug-in 211 may access the internet through a proxy 301 having a proxy add-in 311, to access a web server 420 incorporating an error handler 411.
  • the error handler 411 would dominate the proxy add-in 311 and the plug-in 211 as no "404 Not Found" error response would be returned to the user's PC 101.
  • the behaviour of the error handler 411 may be modified so that it provides information that can be checked by the proxy add-in 311 and the plug-in 211, so as to enable sharing of remuneration between the various organisation(s) that supply the error handler 411, proxy add-in 311 and plug-in 211.
  • the plug-in 211 is arranged to include the more recent web page addresses (URLs) that the user visited (e.g. the previous five web servers) to provide additional context information.
  • the error handler 411 may be modified to provide a limited implementation of the same functionality by the use of session cookies on the user's PC 101 to store the more recent web page addresses visited by the user.
  • a plurality of helper servers may be provided.
  • each user is directed to a particular helper server so as to balance the load between the various helper servers, for example, to distribute the computational load or the internet traffic equally between the various helper servers.
  • different users may be directed to different helper servers on the basis of a participant ID 212.
  • a plurality of ICAP servers may also be used to distribute the load and/or provide redundancy in the event of failure of one of the ICAP servers.
  • ISPs generally use multiple proxy servers. In this case, a single ICAP server 811 may provide services for more than one ICAP-enabled proxy server 801.
  • the web page creation software 143 of the systems 100, 200, 300, 400 created a web page to be viewed by a user on a display 104.
  • the user may not be able to readily view a display, for example, if the user is driving.
  • modified web browser software is used to produce an output that is communicated to the user, for example, by text-to-speech conversion software so that the user listens to the ranked links and selects a link by speaking to the web browser to select a link.
  • the systems 100, 200, 300, 400 used either a plug-in 111, 211, a proxy add-in 311 or a error handler 411 in combination with a helper server 140, 240, 340, 440.
  • some or all of the functionality of the helper server is included in the plug-in 111, 211, proxy add-in 311 or the error handler 411.
  • the user's PC implements a web server and the functionality of the plug-ins 111, 211, proxy add-in 311 or the error handler 411 is part of the user's PC 101.
  • any/some/all of the plug-ins 111, 211, proxy add-in 311 or error handler 411, analysis software 141, index database software 142 and web page creation software 143 may be implemented as part of the operating system of the user's PC.
  • a re-direction HTTP response is sent to the user's PC 101 which causes whichever link is deemed to be most relevant to be directly displayed on the display 104.
  • Revenue can be obtained on the basis of cost per click (CPC), cost per lead (CPL), cost per action (CPA), cost per customer, cost per thousand (CPM, where "M” is the Roman numeral for 1000), cost per sale (CPS) or cost per order (CPO).
  • CPC cost per click
  • CPL cost per lead
  • CPA cost per action
  • CCM cost per customer
  • CPM cost per thousand
  • CPS cost per sale
  • CPO cost per order
  • Different categories of links may be allocated different values. For example, leads to mortgage suppliers may be allocated a high financial value due to the fact that mortgage contracts are typically of high value.
  • the owner of a website will pay an organisation to "host" the website on a web server owned by the organisation. In this situation, the remuneration would be received from the owner of the website rather than the owner of the web server.
  • the helper server 440 was connected to an auxiliary server 460 which included analysis software 241 and index database software 242.
  • web servers (not shown) provided by third parties may be used to perform the context analysis.
  • the plug-in 111, 211, proxy add-in 311 or error handler 411 is arranged, on receipt of an HTTP status code, to send context information to the third party server.
  • the third party server analyses the context information and sends a list of potential links to the helper server which then causes a web page to be generated and sent to the user.
  • the systems 100-400 used index database software to determine links of potential relevance to the user. The links were then presented to the user. In some circumstances, it may be preferable to ensure that a user does not have to wait for too long before receiving some results.
  • the analysis software and the index database software are arranged so that the first time that a URL specifying a particular non-existent page is entered by a user, links are presented to the user based on a relatively brief analysis of the context information. This ensures that the user does not have to wait for too long.
  • the analysis software and the index database software are arranged to analyse the context information in more detail and determine a new list; it is likely that this new list will be more relevant to the context than the list of links originally presented to the user as the analysis software and the index database software will have had more time for analysis. If a different user subsequently enters the same URL, or if the original user enters the same URL a second time, then the new list is presented.
  • An advantage of this embodiment is that the response time until links are returned to a user is kept reasonably short while allowing for relatively detailed context analysis.
  • the web page creation software 143 is arranged to generate a "frameset" web page that contains two or more "frames".
  • a frameset web page appears to the user as a single web page but each of the frames may originate from a different web server.
  • a frame may contain a reference instructing the web browser to retrieve the home web page of a particular web server.
  • the web page creation software is arranged so that a frame including links found after a relatively brief analysis is displayed first. If the user has sufficient patience to wait longer, a frame including links found after a more detailed context analysis is also displayed.
  • a modem 105 was used to connect the user's PC 101 to the internet.
  • PC 101 includes other devices using the HTTP, wireless access protocol (WAP) or a similar protocol to request and receive information from a web server.
  • WAP wireless access protocol
  • the invention is also applicable to networks that do not use the HTTP and HTML protocols.
  • the invention is applicable to "intranets" instead of the Internet.
  • intranets are typically private networks that are either not connected to the Internet or are separated from the Internet by a firewall.
  • a helper web server 140, 240, 340, 440 was used to present the user with potentially relevant links when the user could not access requested information from a web server 120, 420.
  • the helper web server and the web server were distinct web servers.
  • the web server and the helper web server may not only have the same IP address but may also be the same web server i.e. the helper web server helps itself.
  • An advantage of such embodiments is that the response time in providing the user with relevant links can be minimised. For example, when compared to the HTTP requests 220 and HTTP responses 221 of systems 200-400, the need in such alternative embodiments for information to travel over physically large distances is avoided.
  • the system 200 used participant monitoring software 242 and tracker software 243 to allow the helper server 240 to determine the allocation of remuneration.
  • the plug-in 211 (for example) is modified so that the modified plug-in is used to determine the allocation of remuneration.
  • the HTTP request 234 and the HTTP response 235 are not needed as the HTTP response 233 is modified to include the actual links to linked servers 150 (rather than links to the helper server 240 which include the URL of the linked servers 150).
  • the modified plug-in 211 records this and, if applicable, the participant ID so that the remuneration can be shared.
  • Figures 1-4 show various locations (between a user's PC 101 and web servers 120, 420) where error codes may be intercepted and used to initiate a context analysis of incorrect URLs.
  • ISPs Internet Service Providers
  • web proxies may be incorporated into switch/routing equipment. Such proxies would operate in a similar way to the proxy server 301 shown in Figure 3.
  • a DNS server is modified to change the behaviour of the DNS server in the event that a domain name cannot be resolved into an IP address.
  • the modified DNS server may, for example, be modified by the use of a DNS add-in (not shown) analogous to the proxy add-in 311.
  • the browser uses a DNS server to resolve the domain name into an IP address. Once the browser receives the IP address from the DNS server, the browser sends the HTTP request to a host at the IP address specified by the DNS server.
  • a non existent domain name for example 'www.some_non_existent_domain.com'
  • the modified DNS server returns the IP address of a helper server 140, 240, 340, 440.
  • the IP address of the helper server is communicated by the Internet to the web browser 110 which then sends an HTTP request to the helper server 140, 240, 340, 440.
  • a proxy DNS server may be used as an intermediary between a user's PC and a DNS server.
  • the proxy DNS server receives DNS status codes (including DNS error codes) from the DNS server.
  • the proxy DNS server intercepts the DNS error code received from the DNS server and replaces (or amends) the received DNS error code with a DNS status code which includes the IP address of a helper server 140, 240, 340, 440.
  • the web browser would send the path information to the IP address of the helper server.
  • the helper server would be able to perform a context analysis as described earlier. Note that in cases where the user clicked on a link, the address of the web page (that is, the web page having the link specifying a non existent domain name) would also be sent to the helper server.
  • the present invention may be applied to Internet web pages.
  • Such web pages may include, for example, images.
  • images on a web page are typically denoted using the HTML/XHTML tag " ⁇ img>".
  • One of the attributes of the ⁇ img> tag is "src" which specifies the URL of the image that is to be displayed as part of the web page.
  • src specifies the URL of the image that is to be displayed as part of the web page.
  • embodimentsrc attribute may be arranged to analyse the src attribute. For example, if a src attribute specified the URL "www.some_domain_name.com/images/elephant.jpg" then the context analysis could determine that the image was called “elephant” and was in the JPEG format.
  • the name of the image to be displayed may not be indicative of the contents of the image.
  • an image may be called "img0001" but may show a picture of an elephant.
  • embodiments of the present invention may be arranged to retrieve the image and perform image processing of the image.
  • processing a monochrome image to detect representations of circles and squares will require less computer processing power than the detection of more complicated representations such as that of an elephant.
  • embodiments may be arranged to analyse music (for example music in the MPEG layer 3 format, also known as MP3 file format) filenames or the music represented by music files to determine, for example, whether a music file represents Classical music or jazz music.
  • a web page may contain a defective link but may also contain valid links.
  • embodiments of the present invention may be arranged, if the user selects the defective link, to retrieve web pages specified by the valid links and analyse those web pages for context information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Library & Information Science (AREA)
  • Information Transfer Between Computers (AREA)

Claims (61)

  1. System, umfassend:
    ein Terminal (101) zur Benutzung durch einen Benutzer, wobei der Terminal einen Web-Browser (110) zur Anforderung von Web-Seiten für den Benutzer umfasst;
    einen Web-Server (120);
    einen Fehlerdetektor (120), der einen Fehler-Code (131) für den Fall erzeugt, dass nach der Wahl einer Verknüpfung (link) (601) auf einer ersten Web-Seite (600), die eine zweite Web-Seite spezifiziert, die zweite Web-Seite nicht von dem Web-Server zu dem Web-Browser gesendet wird;
    einen Fehler-Code-Empfänger (211; 311; 411; 811), der einen Fehler-Code (131) von dem Fehlerdetektor empfängt und als Reaktion bewirkt, dass Informationen (232), die sich auf die erste Web-Seite (600) beziehen, zu einem Kontext-Analysator gesendet werden;
    einen Kontext-Analysator (241, 242; 341, 343; 741): zum Empfang der Informationen (232) von dem Fehler-Code-Empfänger, zur Analyse des Inhalts der ersten Web-Seite (600), um die Informationen (602) hinsichtlich des Kontextes der Verknüpfung (601) zu bestimmen, zur Errichtung einer Liste (503) von einer oder mehr Web-Seiten auf der Basis der Kontext-Informationen (602), und zum Übermitteln der Liste zu einem Antwortgenerator; und
    einen Antwortgenerator (143), der eine Antwort (500) auf der Basis der Liste erzeugt und die Antwort an den Web-Browser übermittelt.
  2. System nach Anspruch 1, das einen DNS-Server umfasst, wobei der Fehlerdetektor einen Fehler-Code für den Fall eines DNS-Auflösungsausfalls der zweiten, von dem Web-Browser angeforderten zweiten Web-Seite erzeugt.
  3. System nach Anspruch 2, bei dem der Fehlerdetektor als ein DNS-Add-in ausgebildet ist, der in Verbindung mit dem DNS-Server arbeitet.
  4. System nach einem der Ansprüche 1 bis 3, bei dem der Fehlerdetektor (120) einen Fehler-Code für den Fall erzeugt, dass die von dem Web-Browser angeforderte zweite Web-Seite für den Browser nicht verfügbar ist.
  5. System nach Anspruch 4, bei dem der Web-Server (120) den Fehlerdetektor (120) umfasst.
  6. System nach Anspruch 4 oder 5, bei dem der Web-Browser (110) den Fehlerdetektor umfasst.
  7. System nach einem der Ansprüche 1 bis 6, bei dem der Fehlerdetektor einen Zeitablauf-Detektor umfasst, der den Fehlerdetektor veranlasst, einen Fehler-Code für den Fall zu erzeugen, dass eine Anforderung für eine Web-Seite abgelaufen ist.
  8. System nach einem der Ansprüche 1 bis 7, bei dem der Terminal (101) einen Desktop-PC oder ein Mobiltelefon oder einen Personal Digital Assistant umfasst, und bei dem der Web-Browser (110) Web-Browser-Software umfasst.
  9. System nach einem der Ansprüche 1 bis 8, bei dem der Fehler-Code-Empfänger als Einsteckelement (111, 211) ausgebildet ist, das in Verbindung mit dem Web-Browser arbeitet.
  10. System nach einem der Ansprüche 1 bis 8, bei dem der Fehler-Code-Empfänger als Proxi-Add-in (311) ausgebildet ist, der in Verbindung mit einem Proxi-Web-Server arbeitet.
  11. System nach einem der Ansprüche 1 bis 8, bei dem der Fehler-Code-Empfänger als Server (811) ausgebildet ist, der in Verbindung mit einem Proxi-Web-Server arbeitet, um das Verhalten des Proxi-Web-Servers zu modifizieren.
  12. System nach einem der Ansprüche 1 bis 8, bei dem der Fehler-Code-Empfänger als Fehlerbehandler ausgebildet ist, der mit einem anderen Web-Server als dem Web-Server der Ansprüche 4 bis 8 zusammenarbeitet.
  13. System nach einem der vorhergehenden Ansprüche, bei dem der Kontext-Analysator und der Antwortgenerator als Hilfs-Web-Server (240; 340; 440; 740) ausgebildet sind.
  14. System nach einem der Ansprüche 1 bis 12, bei dem der Fehler-Code-Empfänger, der Kontext-Analysator und der Antwortgenerator als Einsteckelement (111, 211) ausgebildet sind, das mit dem Web-Browser zusammenarbeitet.
  15. System nach einem der Ansprüche 1 bis 12, das einen Hilfs-Web-Server (440) in Verbindung mit dem Kontext-Analysator und dem Antwortgenerator umfasst.
  16. System nach einem der vorhergehenden Ansprüche, bei dem der Kontext-Analysator eine Datenbasis (142) umfasst, die Web-Seiten mit Schlüsselworten indiziert.
  17. System nach einem der vorhergehenden Ansprüche, bei dem für den Fall, dass die zweite Web-Seite nicht an den Terminal gesendet wird, der Kontext-Analysator eine andere Web-Seite (600) als die zweite Web-Seite abruft und die andere Web-Seite (600) analysiert, um die Kontext-Informationen (602) zu bestimmen.
  18. System nach Anspruch 17, bei dem der Kontext-Analysator (i) einen Werdegang einer oder mehrerer Web-Seiten (600) bestimmt, die Verknüpfungen (601) aufweisen, die den Benutzer zur zweiten Web-Seite führten, (ii) die eine oder mehr Web-Seiten abruft, und (iii) die eine oder mehrere Web-Seiten analysiert, um Kontext-Informationen (602) zu bestimmen.
  19. System nach Anspruch 17 oder 18, bei dem der Kontext-Analysator eine Homepage aufruft, die der zweiten Web-Seite zugeordnet ist, und die Homepage analysiert, um Kontext-Informationen zu bestimmen.
  20. System nach einem der Ansprüche 17 bis 19, bei dem der Kontext-Analysator eine Web-Seite aus einem Hilfs-Server (701, 702) aufruft und die aufgerufene Web-Seite analysiert, um Kontext-Informationen zu bestimmen.
  21. System nach Anspruch 20, bei dem der Hilfs-Server ein Wer-ist-(whois)-Server (701) ist.
  22. System nach Anspruch 20 oder 21, bei dem: der Hilfs-Server ein erster Hilfs-Server (701) ist; der Kontext-Analysator Kontext-Informationen verwendet, die aus einer von dem ersten Hilfs-Server als Eingabe zu einem zweiten Hilfs-Server (702) aufgerufenen Web-Seite bestimmt werden; der Kontext-Analysator eine Web-Seite aus einem zweiten Hilfs-Server als Reaktion auf die Eingabe aufruft; und der Kontext-Analysator die von dem zweiten Hilfs-Server aufgerufene Web-Seite analysiert, um Kontext-Informationen zu bestimmen.
  23. System nach Anspruch 22, bei dem der zweite Hilfs-Server einen Was-ist-(what_is)-Server (702) umfasst.
  24. System nach einem der Ansprüche 17 bis 23, bei dem der Kontext-Analysator die eine oder mehr Web-Seiten analysiert, um Schlüsselworte (602) als Kontext-Informationen zu bestimmen.
  25. System nach einem der vorhergehenden Ansprüche, bei dem der Fehler-Code-Empfänger teilnehmende ID-Informationen (212) speichert, bei dem der Fehler-Code-Empfänger die teilnehmenden ID-Informationen zu dem Kontext-Analysator (242) sendet, und bei dem der Kontext-Analysator die teilnehmenden ID-Informationen als Informationen hinsichtlich des Kontextes der zweiten von dem Web-Browser angeforderten Web-Seite interpretiert.
  26. System nach einem der vorhergehenden Ansprüche, bei dem der Antwortgenerator (143) eine Antwort an den Web-Browser sendet, um den Web-Browser zu einer der Web-Seiten der Liste mit einer oder mehr Web-Seiten umzuleiten, die von Interesse für den Benutzer sein können.
  27. System nach einem der Ansprüche 1 bis 25, bei dem der Antwortgenerator (143) eine Web-Seite (500) erzeugt und diese zu dem Terminal sendet.
  28. System nach Anspruch 27, bei dem der Antwortgenerator (143) eine Web-Seite erzeugt, die eine oder mehr Verknüpfungen (503) zu einer oder mehreren entsprechenden Web-Seiten enthält, die von Interesse für den Benutzer sein können.
  29. System nach einem der vorhergehenden Ansprüche, bei dem der Fehler-Code-Empfänger teilnehmende ID-Informationen (212) speichert;
    bei dem der Fehler-Code-Empfänger bewirkt, dass die teilnehmenden ID-Informationen dem Antwortgemerator zugeführt werden;
    bei dem der Antwortgenerator (143) eine Web-Seite (500) erzeugt, die eine oder mehr, auf einen Hilfs-Server zeigende Verknüpfungen enthält und die erzeugte Web-Seite zu dem Terminal sendet, wobei jede der einen oder mehr Verknüpfungen der erzeugten Web-Seite (i) Informationen, die eine entsprechende der einen oder mehr Web-Seiten, die von Interesse für den Benutzer sein können, und (ii) die teilnehmenden ID-Informationen enthält; und
    einen Zähler (243) umfasst, der den teilnehmenden ID-Informationen zugeordnet ist, wobei der Zähler als Reaktion auf die Auswahl des Benutzers einer der einen oder mehr Verknüpfungen der erzeugten Web-Seite fortgeschaltet wird.
  30. System nach Anspruch 29, umfassend einen Hilfs-Server (240) zum Empfang einer Web-Seiten-Anforderung (234) von dem Terminal, die Informationen enthält, die eine Web-Seite und die teilnehmenden ID-Informationen spezifiziert, und zum Senden einer Antwort (235) zu dem Web-Browser als Reaktion auf die Web-Seiten-Anforderung, um den Web-Browser zu der in der Web-Seiten-Anforderung spezifizierten Web-Seite umzuleiten und den Zähler (243) fortzuschalten.
  31. System nach Anspruch 30, das mehrere Zähler (243) umfasst, von denen jeder entsprechenden teilnehmenden ID-Informationen (212) zugeordnet ist.
  32. System nach einem der Ansprüche 29 bis 31, bei dem der Fehler-Code-Empfänger die teilnehmenden ID-Informationen dem Kontext-Analysator zuführt, und bei dem der Kontext-Analysator die teilnehmenden ID-Informationen dem Antwortgenerator zuführt.
  33. System nach Anspruch 28 oder einem der von dem Anspruch 28 abhängigen Ansprüche 29 bis 32, bei dem der Antwortgenerator (143) entsprechende verknüpfte ID-Informationen (312) in die eine oder mehr Verknüpfungen der erzeugten Web-Seite einbezieht.
  34. System nach einem der vorhergehenden Ansprüche, das ferner einen oder mehr verknüpfte Server (150; 350) umfasst, die die Web-Seiten speichern, die für den Benutzer von Interesse sein können.
  35. System nach Anspruch 27 oder einem der von dem Anspruch 27 abhängigen Ansprüche 28 bis 34, bei dem der Antwortgenerator eine vorbereitende Web-Seite auf der Basis einer vorbereitenden Liste erzeugt, die von dem Kontext-Analysator empfangen wird, und bei dem der Antwortgenerator eine ergänzende Web-Seite auf der Basis einer von dem Kontext-Analysator empfangenen ergänzenden Liste erzeugt.
  36. System nach Anspruch 35, bei dem der Antwortgenerator eine Web-Seite erzeugt, die eine Rahmengruppe umfasst, wobei einer der Rahmen der Rahmengruppe die vorbereitende Web-Seite spezifiziert und ein anderer Rahmen der Rahmengruppe die ergänzende Web-Seite spezifiziert.
  37. Fehler-Code-Empfänger (211; 311; 411; 811), umfassend:
    Mittel zum Empfangen eines Fehler-Codes (131) von einem Fehlerdetektor (120), wobei der Fehler-Code (131) anzeigt, dass nach der Auswahl einer Verknüpfung (601) auf einer ersten Web-Seite (600), die eine zweite Web-Seite spezifiziert, die zweite Seite nicht zu einem Web-Browser gesendet wurde, gekennzeichnet dadurch, dass sie ferner umfassen:
    Mittel, die als Reaktion auf den Empfang eines Fehler-Codes (131) veranlassen, dass Informationen hinsichtlich der ersten Web-Seite (600) zu einem Kontext-Analysator (241, 242; 341, 343; 741) gesendet werden, der den Inhalt der ersten Web-Seite (600) analysiert.
  38. Fehler-Code-Empfänger nach Anspruch 37, der bewirkt, dass Informationen zu einem Kontext-Analysator gesendet werden, in dem eine HTTP-Umleitungs-Antwort (331) zu dem Web-Browser (110) gesendet wird.
  39. Einsteckelement (211) für einen Web-Browser (110), das einen Fehler-Code-Empfänger gemäß Anspruch 37 oder 38 umfasst.
  40. Die Kombination eines Einsteckelements nach Anspruch 39 mit einem Web-Browser (110).
  41. Proxi-Add-in (311) für einen Proxi-Server (301), wobei die Einsteckeinheit einen Fehler-Code-Empfänger nach Anspruch 37 oder 38 umfasst.
  42. Die Kombination eines Einsteckelements nach Anspruch 41 mit einem Proxi-Server (301).
  43. Server (811) zum Modifizieren des Verhaltens eines Proxi-Servers (801) umfassend:
    Kommunikationsmittel zum Übertragen von Nachrichten zwischen dem Server (811) und einem Proxi-Server (801);
    einen Fehler-Code-Empfänger nach Anspruch 37 oder 38 zum Analysieren von Nachrichten, um zu bestimmen, ob eine Nachricht einen Fehler-Code (131) enthält.
  44. Server nach Anspruch 43 umfassend:
    Mittel zum Messen der Länge einer Nachricht und zur Veranlassung, dass die Informationen (232) hinsichtlich der ersten Web-Seite (600) zu einem Kontext-Analysator (241, 242; 341, 343; 741) gesendet werden, wenn sowohl die Länge einer Nachricht einen Schwellwert überschreitet als auch die Nachricht einen Fehler-Code (131) enthält.
  45. Server (811) zum Modifizieren des Verhaltens eines Proxi-Servers (801) umfassend:
    Kommunikationsmittel zum Übertragen von Nachrichten zwischen dem Server (811) und einem Proxi-Server (801);
    einen Fehlerdetektor zum Analysieren von Nachrichten, die aus der Wahl einer Verknüofung (601) auf einer ersten Web-Seite (600), die eine zweite Web-Seite spezifiziert, herrühren, und zur Erzeugung eines Fehler-Codes, wenn die zweite Web-Seite für eine Sendung zu einem Web-Browser nicht verfügbar ist;
    einen Fehler-Code-Empfänger nach Anspruch 37 oder 38 zum Empfang von Fehler-Codes von dem Fehlerdetektor.
  46. Server nach Anspruch 45, bei dem der Fehlerdetektor Timer-Mittel zum Bestimmung umfasst, ob eine Web-Seite für die Sendung zu einem Web-Browser zu lange gedauert hat.
  47. Ein einzelner Server, der alle Merkmale von Anspruch 43 oder 44 in Kombination mit allen Merkmalen von Anspruch 45 oder 46 umfasst.
  48. Server nach einem der Ansprüche 43 bis 47, bei dem die Kommunikationsmittel ICAP-Nachrichten übertragen.
  49. Server nach einem der Ansprüche 43 bis 48, der Kommunikationsmittel zum Kommunizieren mit einem DNS-Server umfasst.
  50. Server nach einem der Ansprüche 43 bis 49, der Kommunikationsmittel zum Kommunizieren mit einem Web-Server umfasst.
  51. Fehlerbehandler (411) für einen Web-Server (420), der einen Fehler-Code-Empfänger nach Anspruch 37 oder 38 umfasst.
  52. Die Kombination eines Fehlerbehandlers (411) nach Anspruch 51 mit einem Web-Server (420).
  53. DNS-Add-in für einen DNS-Server, wobei der DNS-Add-in einen Fehler-Code-Empfänger gemäß Anspruch 37 oder 38 umfasst.
  54. Die Kombination eines DNS-Add-in gemäß Anspruch 53 mit einem DNS-Server.
  55. Kontext-Analysator (241, 242; 341, 343; 741), bei dem für den Fall, dass nach Auswahl einer Verknüpfung (601) auf einer ersten Web-Seite (600), die eine zweite Web-Seite spezifiziert, die zweite Web-Seite nicht von einem Web-Server zu einem Web-Browser gesendet wird, um:
    Informationen (232) hinsichtlich der ersten Web-Seite (600) von einem Fehler-Code-Empfänger (211; 311; 411; 811) zu empfangen,
    den Inhalt der ersten Web-Seite (600) zu analysieren, um Informationen (602) hinsichtlich des Kontextes der Verknüpfung (601) zu bestimmen;
    eine Liste (503) mit einer oder mehr Web-Seiten auf der Basis der Kontext-Informationen (602) zu errichten und die Liste zu einem Antwortgenerator zu übertragen.
  56. Hilfs-Server (240; 340; 440; 740), umfassend einen Kontext-Analysator nach Anspruch 55.
  57. Hilfs-Server nach Anspruch 56, umfassend einen Antwortgenerator (143), der eine Antwort (500) auf der Basis der Liste erzeugt und die Antwort zu einem Web-Browser überträgt.
  58. Computerprogramm-Produkt, das von einem Prozessor interpretierbare Instruktionen definiert, um einen Prozessor zu veranlassen, zu realisieren: einen Fehler-Code-Empfänger (211; 311; 411; 811) nach Anspruch 37 oder 38, oder ein Einsteckelement (211) nach Anspruch 39, oder einen Proxi-Add-in (311) nach Anspruch 41, oder einen Server (811) nach Anspruch 34 oder 45, oder einen Fehlerbehandler (411) nach Anspruch 51, oder einen DNS-Add-in nach Anspruch 53 oder einen Kontext-Analysator (241, 242; 341, 343; 741) nach Anspruch 55 oder einen Hilfs-Server (240; 340; 440; 740) nach Anspruch 56, wenn die Instruktionen auf einem Computer laufen.
  59. Computerprogramm-Produkt nach Anspruch 58, das einen Datenträger umfasst.
  60. Computerprogramm-Produkt nach Anspruch 59, das aus dem Internet herunterladbare Daten umfasst.
  61. Verfahren, um einen Benutzer mit einer Benutzer-Schnittstelle zu versehen, umfassend die Schritte:
    Feststellen als Reaktion auf die Auswahl einer Verknüpfung (601) auf einer ersten Web-Seite (600), die eine zweite Web-Seite spezifiziert, dass die zweite Web-Seite nicht zu einem Web-Browser (110) gesendet wird, und Erzeugen eines Fehler-Codes (131) als Reaktion;
    Empfangen (211; 311; 411; 811) des Fehler-Codes und als Reaktion:
    Analysieren (241, 242; 341, 343; 741) des Inhalts der ersten Web-Seite (600), um Informationen (602) in Bezug auf den Kontext der Verknüpfung (601) zu bestimmen und dadurch eine Liste (503) von einer oder mehr Web-Seiten auf der Basis der Kontext-Informationen (602) zu errichten; und
    Erzeugen einer Antwort auf der Basis der Liste und Übertragen der Antwort zu dem Benutzer.
EP05762142A 2004-07-22 2005-07-19 Verbesserte benutzerschnittstelle Not-in-force EP1706832B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
GB0416405A GB2421322A (en) 2004-07-22 2004-07-22 User interface for an internet web browser
GBGB0501851.0A GB0501851D0 (en) 2004-07-22 2005-01-28 Improved user interface
PCT/GB2005/002835 WO2006008516A1 (en) 2004-07-22 2005-07-19 Improved user interface

Publications (2)

Publication Number Publication Date
EP1706832A1 EP1706832A1 (de) 2006-10-04
EP1706832B1 true EP1706832B1 (de) 2007-11-21

Family

ID=35432462

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05762142A Not-in-force EP1706832B1 (de) 2004-07-22 2005-07-19 Verbesserte benutzerschnittstelle

Country Status (9)

Country Link
US (1) US8751601B2 (de)
EP (1) EP1706832B1 (de)
JP (1) JP2008507057A (de)
AU (1) AU2005263962B2 (de)
BR (1) BRPI0513582A (de)
CA (1) CA2574521A1 (de)
DE (1) DE602005003449T2 (de)
ES (1) ES2297734T3 (de)
WO (1) WO2006008516A1 (de)

Families Citing this family (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2873882A1 (fr) * 2004-07-29 2006-02-03 France Telecom Procede et dispositif de distinction de requetes http utilisateur
EP1810483A1 (de) * 2004-10-27 2007-07-25 France Telecom Verfahren zum abfangen von http-umleitungsanfragen, system und servervorrichtung zur ausführung dieses verfahrens
US8825837B2 (en) 2010-04-21 2014-09-02 International Business Machines Corporation Notice of restored malfunctioning links
US20070185884A1 (en) * 2006-02-07 2007-08-09 Yahoo! Inc. Aggregating and presenting information on the web
US10042927B2 (en) 2006-04-24 2018-08-07 Yeildbot Inc. Interest keyword identification
US8069182B2 (en) 2006-04-24 2011-11-29 Working Research, Inc. Relevancy-based domain classification
US8838773B1 (en) * 2006-09-29 2014-09-16 Trend Micro Incorporated Detecting anonymized data traffic
US8037182B2 (en) * 2006-11-30 2011-10-11 Microsoft Corporation Capture of content from dynamic resource services
US8494897B1 (en) * 2008-06-30 2013-07-23 Alexa Internet Inferring profiles of network users and the resources they access
US8438582B2 (en) * 2008-06-30 2013-05-07 Alcatel Lucent Soft denial of application actions over the network communications
CN101662464A (zh) * 2008-08-26 2010-03-03 阿里巴巴集团控股有限公司 一种用于实现http请求服务的系统及其方法
US8825740B2 (en) * 2008-10-23 2014-09-02 Microsoft Corporation Smart, search-enabled web error pages
JP5395461B2 (ja) * 2009-02-27 2014-01-22 株式会社東芝 情報推薦装置、情報推薦方法および情報推薦プログラム
US8224923B2 (en) * 2009-06-22 2012-07-17 Verisign, Inc. Characterizing unregistered domain names
US8078922B2 (en) * 2009-09-30 2011-12-13 Sap Ag Internal server error analysis
US9356991B2 (en) 2010-05-10 2016-05-31 Litera Technology Llc Systems and methods for a bidirectional multi-function communication module
US10674230B2 (en) * 2010-07-30 2020-06-02 Grab Vision Group LLC Interactive advertising and marketing system
US8504673B2 (en) 2011-03-31 2013-08-06 Verisign, Inc. Traffic like NXDomains
US9405739B1 (en) * 2011-08-12 2016-08-02 The Boeing Company Source code format for IDE code development with embedded objects
WO2013038320A1 (en) * 2011-09-16 2013-03-21 Strangeloop Networks, Inc. Mobile resource accelerator
US8504692B1 (en) * 2011-09-26 2013-08-06 Google Inc. Browser based redirection of broken links
US8392576B1 (en) 2011-09-26 2013-03-05 Google Inc. Browser based redirection of broken links
CA2789909C (en) * 2012-09-14 2019-09-10 Ibm Canada Limited - Ibm Canada Limitee Synchronizing http requests with respective html context
US9411786B2 (en) * 2013-07-08 2016-08-09 Adobe Systems Incorporated Method and apparatus for determining the relevancy of hyperlinks
WO2015069165A1 (en) * 2013-11-08 2015-05-14 Telefonaktiebolaget L M Ericsson (Publ) Allocation of ressources for real-time communication
WO2015070426A1 (en) * 2013-11-15 2015-05-21 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for operating an icap server
RU2014103705A (ru) * 2014-01-31 2015-08-10 Общество С Ограниченной Ответственностью "Яндекс" Способ обработки пользовательского запроса на доступ к веб-ресурсу (варианты) и электронное устройство
CN104113592A (zh) * 2014-07-01 2014-10-22 北京乐途园科技有限公司 一种本地微服务器及车载服务信息提供系统及方法
KR102264992B1 (ko) 2014-12-31 2021-06-15 삼성전자 주식회사 무선 통신 시스템에서 서버 할당 방법 및 장치
CN104580552A (zh) * 2015-01-29 2015-04-29 太仓市同维电子有限公司 家庭网关中错误域名解析服务器解析重定向的实现方法
CN104965926B (zh) * 2015-07-14 2019-03-26 安一恒通（北京）科技有限公司 网页提供方法及装置
US9762521B2 (en) * 2016-01-15 2017-09-12 International Business Machines Corporation Semantic analysis and delivery of alternative content
US10505985B1 (en) * 2016-04-13 2019-12-10 Palo Alto Networks, Inc. Hostname validation and policy evasion prevention
US10832000B2 (en) * 2016-11-14 2020-11-10 International Business Machines Corporation Identification of textual similarity with references
US11669675B2 (en) 2016-11-23 2023-06-06 International Business Machines Corporation Comparing similar applications with redirection to a new web page
US11032127B2 (en) 2017-06-26 2021-06-08 Verisign, Inc. Resilient domain name service (DNS) resolution when an authoritative name server is unavailable
US11288336B2 (en) * 2018-04-18 2022-03-29 Google Llc Systems and methods for providing content items in situations involving suboptimal network conditions
US11082339B2 (en) * 2018-10-12 2021-08-03 Hewlett Packard Enterprise Development Lp Domain name system (DNS) optimization for wide area networks
US11514127B2 (en) 2019-02-22 2022-11-29 International Business Machines Corporation Missing web page relocation
EP4328760A1 (de) * 2022-08-24 2024-02-28 Sandvine Corporation System und verfahren zur klassifizierung von verkehrsflüssen mittels sprachverarbeitung

Family Cites Families (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5751961A (en) 1996-01-31 1998-05-12 Bell Communications Research, Inc. Integrated internet system for translating logical addresses of internet documents to physical addresses using integrated service control point
GB2330430B (en) * 1997-10-16 2002-07-17 Ibm Error handler for a proxy server computer system
US6092100A (en) * 1997-11-21 2000-07-18 International Business Machines Corporation Method for intelligently resolving entry of an incorrect uniform resource locator (URL)
US6742030B1 (en) 1997-11-24 2004-05-25 International Business Machines Corporation Method to keep a persistent trace of weblink use per user
US6590588B2 (en) * 1998-05-29 2003-07-08 Palm, Inc. Wireless, radio-frequency communications using a handheld computer
US6269460B1 (en) * 1998-09-01 2001-07-31 International Business Machines Corporation Dynamic enhancement of error condition handling and displayed error messages in computer operations
US6687732B1 (en) * 1998-09-28 2004-02-03 Inktomi Corporation Adaptive traffic bypassing in an intercepting network driver
US6332158B1 (en) 1998-12-03 2001-12-18 Chris Risley Domain name system lookup allowing intelligent correction of searches and presentation of auxiliary information
US9141717B2 (en) * 1999-03-22 2015-09-22 Esdr Network Solutions Llc Methods, systems, products, and devices for processing DNS friendly identifiers
US6202087B1 (en) 1999-03-22 2001-03-13 Ofer Gadish Replacement of error messages with non-error messages
US7188138B1 (en) * 1999-03-22 2007-03-06 Eric Schneider Method, product, and apparatus for resource identifier registration and aftermarket services
US6763496B1 (en) * 1999-03-31 2004-07-13 Microsoft Corporation Method for promoting contextual information to display pages containing hyperlinks
US6594697B1 (en) 1999-05-20 2003-07-15 Microsoft Corporation Client system having error page analysis and replacement capabilities
US6725214B2 (en) * 2000-01-14 2004-04-20 Dotnsf Apparatus and method to support management of uniform resource locators and/or contents of database servers
AU2001259075A1 (en) * 2000-04-17 2001-10-30 Circadence Corporation System and method for web serving
US6832239B1 (en) * 2000-07-07 2004-12-14 International Business Machines Corporation Systems for managing network resources
US20030018694A1 (en) * 2000-09-01 2003-01-23 Shuang Chen System, method, uses, products, program products, and business methods for distributed internet and distributed network services over multi-tiered networks
DE10048112A1 (de) * 2000-09-28 2002-04-18 Nutzwerk Informationsgmbh Vorrichtung unter Verfahren zur Bereitstellung von Informationen bei einer fehlerhaften Anfrage an einen Server in einem Datennetz
US20020056053A1 (en) * 2000-10-26 2002-05-09 Ben Vine System and method for handling web failures
JP2002183002A (ja) * 2000-12-14 2002-06-28 Yafoo Japan Corp 訂正候補のドメイン名を通知するサーバ装置、およびこのサーバ装置により通知された訂正候補のドメイン名を利用するクライアントコンピュータ、およびこのクライアントコンピュータ上で動作するプログラムを記録した記録媒体、および訂正候補のメールアドレスを通知するメールサーバ
US7685224B2 (en) * 2001-01-11 2010-03-23 Truelocal Inc. Method for providing an attribute bounded network of computers
US20020116495A1 (en) * 2001-01-29 2002-08-22 Curt Hutten System and method for displaying news information on a user computer
US20020198937A1 (en) * 2001-03-09 2002-12-26 Arif Diwan Content-request redirection method and system
US20030074400A1 (en) * 2001-03-30 2003-04-17 David Brooks Web user profiling system and method
US6990534B2 (en) * 2001-07-20 2006-01-24 Flowfinity Wireless, Inc. Method for a proactive browser system for implementing background frame maintenance and asynchronous frame submissions
JP4692802B2 (ja) * 2001-08-21 2011-06-01 ソニー株式会社 アドレス自動検索装置、アドレス自動検索方法、アドレス自動検索プログラム及びアドレス自動検索プログラム格納媒体
WO2003052614A1 (en) 2001-12-17 2003-06-26 Stargazer Foundation, Inc. System and method for disseminating knowledge over a global computer network
US7277924B1 (en) * 2002-05-07 2007-10-02 Oracle International Corporation Method and mechanism for a portal website architecture
US7360160B2 (en) * 2002-06-20 2008-04-15 At&T Intellectual Property, Inc. System and method for providing substitute content in place of blocked content
US20040019697A1 (en) * 2002-07-03 2004-01-29 Chris Rose Method and system for correcting the spelling of incorrectly spelled uniform resource locators using closest alphabetical match technique
US20060053213A1 (en) * 2002-10-30 2006-03-09 Robert Seeman Method of handling web page requests from a browser
JP4098610B2 (ja) * 2002-12-10 2008-06-11 株式会社日立製作所 アクセス中継装置
JP4109258B2 (ja) * 2002-12-13 2008-07-02 テレフオンアクチーボラゲット エル エム エリクソン（パブル） Ｈｔｔｐに基づく通信システムにおけるエラーメッセージングの方法
FR2854297A1 (fr) 2003-04-25 2004-10-29 France Telecom Procede et systeme de redirection sur detection d'erreur de resolutions dns
US7325045B1 (en) * 2003-08-05 2008-01-29 A9.Com, Inc. Error processing methods for providing responsive content to a user when a page load error occurs
US7756996B2 (en) * 2004-01-30 2010-07-13 Finjan, Inc. Embedding management data within HTTP messages
US20050268219A1 (en) * 2004-05-28 2005-12-01 Microsoft Corporation Method and system for embedding context information in a document
US7702902B2 (en) * 2004-06-25 2010-04-20 The Go Daddy Group, Inc. Method for a web site with a proxy domain name registration to receive a secure socket layer certificate
CN101877696B (zh) * 2009-04-30 2014-01-08 国际商业机器公司 在网络应用环境下重构错误响应信息的设备和方法

Also Published As

Publication number Publication date
US20070033264A1 (en) 2007-02-08
JP2008507057A (ja) 2008-03-06
AU2005263962A1 (en) 2006-01-26
BRPI0513582A (pt) 2008-05-13
AU2005263962B2 (en) 2011-12-22
CA2574521A1 (en) 2006-01-26
DE602005003449T2 (de) 2008-10-02
US8751601B2 (en) 2014-06-10
EP1706832A1 (de) 2006-10-04
WO2006008516A1 (en) 2006-01-26
ES2297734T3 (es) 2008-05-01
DE602005003449D1 (de) 2008-01-03

Similar Documents

Publication Publication Date Title
EP1706832B1 (de) Verbesserte benutzerschnittstelle
US6636854B2 (en) Method and system for augmenting web-indexed search engine results with peer-to-peer search results
CA2457511C (en) Method, apparatus, and user interface for managing electronic mail and alert messages
CA2734774C (en) A user-transparent system for uniquely identifying network-distributed devices without explicitly provided device or user identifying information
US7310687B2 (en) Methods and systems for managing class-based condensation
JP3807961B2 (ja) セッション管理方法、セッション管理システムおよびプログラム
US8180376B1 (en) Mobile analytics tracking and reporting
US6910077B2 (en) System and method for identifying cloaked web servers
US20030018707A1 (en) Server-side filter for corrupt web-browser cookies
EP2089817B1 (de) Verfahren und system zur intelligenten verarbeitung elektronischer daten
US11456935B2 (en) Method and server for monitoring users during their browsing within a communications network
US20060271641A1 (en) Method and system for object prediction
US20050091202A1 (en) Social network-based internet search engine
US20040122951A1 (en) Method and apparatus for providing Web users with a click-to-contact service
WO2004084097A1 (en) Method and apparatus for detecting invalid clicks on the internet search engine
CN100550015C (zh) 改进的用户界面
US20030084034A1 (en) Web-based search system
JP2019506692A (ja) データを処理する方法、装置、及びコンピュータプログラム、並びに階層ドメインネームシステムのゾーンファイル
US20030187976A1 (en) Tracking users at a web server network
US9959302B2 (en) Method and apparatus for providing traffic-based content acquisition and indexing
TW200805972A (en) Context based navigation
WO2003005240A1 (en) Apparatus for searching on internet
KR100400649B1 (ko) 유알엘을 이용한 정보제공방법 및 그 시스템
KR20050079282A (ko) 웹 브라우저를 이용한 전자메일 서비스 방법 및 이를저장한 컴퓨터 판독가능 저장매체

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060807

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20061129

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

DAX Request for extension of the european patent (deleted)
AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REF Corresponds to:

Ref document number: 602005003449

Country of ref document: DE

Date of ref document: 20080103

Kind code of ref document: P

REG Reference to a national code

Ref country code: PT

Ref legal event code: SC4A

Free format text: AVAILABILITY OF NATIONAL TRANSLATION

Effective date: 20080221

REG Reference to a national code

Ref country code: CH

Ref legal event code: NV

Representative=s name: ISLER & PEDRAZZINI AG

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080221

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2297734

Country of ref document: ES

Kind code of ref document: T3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080221

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080321

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

ET Fr: translation filed
PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20080822

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080222

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080522

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071121

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: LU

Payment date: 20110720

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: CH

Payment date: 20110728

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: AT

Payment date: 20110726

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IE

Payment date: 20120626

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20120705

Year of fee payment: 8

Ref country code: BE

Payment date: 20120723

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20120719

Year of fee payment: 8

Ref country code: PT

Payment date: 20120119

Year of fee payment: 8

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 379252

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120719

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120731

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120719

REG Reference to a national code

Ref country code: PT

Ref legal event code: MM4A

Free format text: LAPSE DUE TO NON-PAYMENT OF FEES

Effective date: 20140120

BERE Be: lapsed

Owner name: BAREFRUIT LTD

Effective date: 20130731

REG Reference to a national code

Ref country code: NL

Ref legal event code: V1

Effective date: 20140201

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130731

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140201

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120719

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130719

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20140908

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130720

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20160720

Year of fee payment: 12

Ref country code: IT

Payment date: 20160721

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20160801

Year of fee payment: 12

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602005003449

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20180330

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180201

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170719

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20200625

Year of fee payment: 16

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210719

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210719