EP1588294B1 - Method for browsing a data communications network - Google Patents

Method for browsing a data communications network Download PDF

Info

Publication number
EP1588294B1
EP1588294B1 EP04706591A EP04706591A EP1588294B1 EP 1588294 B1 EP1588294 B1 EP 1588294B1 EP 04706591 A EP04706591 A EP 04706591A EP 04706591 A EP04706591 A EP 04706591A EP 1588294 B1 EP1588294 B1 EP 1588294B1
Authority
EP
European Patent Office
Prior art keywords
resource locator
match
user
keyword string
keyword
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.)
Expired - Lifetime
Application number
EP04706591A
Other languages
German (de)
French (fr)
Other versions
EP1588294A2 (en
Inventor
Joseph Peter Robert Tosey
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.)
Sierra Wireless Inc
Original Assignee
Sierra Wireless Inc
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
Application filed by Sierra Wireless Inc filed Critical Sierra Wireless Inc
Priority to EP06118332A priority Critical patent/EP1720110A1/en
Publication of EP1588294A2 publication Critical patent/EP1588294A2/en
Application granted granted Critical
Publication of EP1588294B1 publication Critical patent/EP1588294B1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72445User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting Internet browser applications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/955Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566URL specific, e.g. using aliases, detecting broken or misspelled links
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Definitions

  • the present invention relates to the field of computer science. More particularly, the present invention relates to a method and apparatus for token-based Web browsing with visual feedback of disclosure.
  • a wireless user device such as a mobile phone or a personal data assistant (PDA).
  • PDA personal data assistant
  • Such a user typically accesses information by entering the name of the item for which information is desired. For example, a user desiring to find a movie review for a film entitled "Dances with Wolves" would enter the keyword string "Dances with Wolves".
  • the wireless user device must then obtain this information and render it to the user. Some of the information may reside locally on the user device, while other information must be obtained from an external source.
  • the wireless user device periodically communicates with one or more service providers to obtain updates for all information available to the wireless user device. This enables the user to store the entire body of information locally.
  • this solution requires a relatively large database on a user device. Such a local database typically becomes outdated quickly and is difficult to maintain.
  • Another solution includes requiring the user search a World Wide Web (“Web”) portal for the desired information.
  • Web World Wide Web
  • This solution requires the user enter a relatively large amount of text.
  • Web portals typically have a relatively large amount of latency and portal menus typically change frequently, confusing the user.
  • obtaining useful information from an external source such as a service provider often requires disclosing private data. For example, a user desiring weather information for the user's current location must first disclose the location. For various reasons, the user may not want this information disclosed.
  • US 6,324,566 B1 discloses a method and system for browsing the web using bookmarks.
  • a data communications network may be browsed using one or more tokens by receiving an input keyword string from a user, determining whether there is a match between the input keyword string and a database of keyword strings, determining a category of the keyword string, rendering to the user at least one service identifier associated with the category, receiving a user-selected service identifier in response to the rendering, substituting at least one variable in a resource locator template associated with the service with a string based at least in part on the keyword string entered by the user and launching the resource locator.
  • a special rendering of a hyperlink corresponding to the resource locator is used to indicate private data will be disclosed upon launching the resource locator.
  • Embodiment of the present invention is described herein in the context of a method and apparatus for token-based Web browsing with visual feedback of disclosure.
  • Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other examples of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure.
  • the components, process steps, and/or data structures may be implemented using various types of operating systems (OS), computing platforms, firmware, computer programs, computer languages, and/or general-purpose machines.
  • OS operating systems
  • the method can be run as a programmed process running on processing circuitry.
  • the processing circuitry can take the form of numerous combinations of processors and operating systems, or a stand-alone device.
  • the process can be implemented as instructions executed by such hardware, hardware alone, or any combination thereof.
  • the software may be stored on a program storage device readable by a machine.
  • FPLDs field programmable logic devices
  • FPGAs field programmable gate arrays
  • CPLDs complex programmable logic devices
  • ASICs application specific integrated circuits
  • network includes local area networks, wide area networks, the Internet, cable television systems, telephone systems, wireless telecommunications systems, fiber optic networks, ATM networks, frame relay networks, satellite communications systems, and the like. Such networks are well known in the art and consequently are not further described here.
  • wireless user device includes any device capable of wireless communication and capable of rendering information to a user.
  • the information may be rendered, by way of example, by visual, auditory or tactile means.
  • exemplary wireless user devices include, by way of example, a personal digital assistant (PDA), a mobile phone, a personal computer, a pager, or the like.
  • PDA personal digital assistant
  • private data refers to personal information about a user.
  • a user may desire to limit or restrict dissemination or availability of such information.
  • Private data may be unique for a particular individual.
  • a social security number is an example of private data that is unique to a particular individual.
  • Private data may also be non-unique information concerning a particular individual.
  • a language preference of "English” is an example of private but non-unique information concerning a particular individual.
  • keyword string refers to one or more keywords comprising one or more characters, which together represent the name of an object or the attributes of an object associated with a service.
  • a keyword string represents well-known brands, titles and generic categories. Exemplary brands include the keyword strings “Starbucks”, “Olive Garden” and “Alpo”. Exemplary titles include the keyword strings “Dances with Wolves”, “Mission Impossible” and “Harry Potter”. Exemplary generic categories include “ATM”, “Weather” and "Hospital”.
  • resource locator or "RL” is defined as an identifier used for accessing a resource.
  • a resource locator may be the name of the resource.
  • a resource locator may also be a Uniform Resource Identifier (URI). More particularly, a resource locator may be a uniform resource locator (URL).
  • URIs and URLs are described in T. Berners-Lee, "Uniform Resource Identifiers (URI): Generic Syntax", Network Working Group Request for Comments: 2396, August 1998 .
  • the resource may be an HTML page, an image file, a program such as a common gateway interface application (CGI) or JavaTM applet, a text file, a document, or the like.
  • CGI common gateway interface application
  • FIG. 1 depicts a block diagram of a computer system 100 suitable for implementing aspects of the present invention.
  • system 100 includes a bus 102 which interconnects major subsystems such as a processor 104, an internal memory 106 (such as a RAM), an input/output (I/O) controller 108, a removable memory (such as a memory card), an external device such as a display screen 110 via display adapter 112, a roller-type input device 114, a joystick 116, a numeric keyboard 118, an alphanumeric keyboard 118, directional navigation pad 126 and a wireless interface 120. Many other devices can be connected.
  • Wireless network interface 120, wired network interface 128, or both, may be used to interface to a local or wide area network (such as the Internet) using any network interface system known to those skilled in the art.
  • Code to implement the present invention may be operably disposed in internal memory 106 or stored on storage media such as removable memory 122, a floppy disk or a CD-ROM.
  • Wireless user device 208 includes a user interface 212 configured to receive input from a user 202 and to render digital content to the user 202.
  • Wireless user device 208 also includes a matcher 210 in communication with both the user interface 212 and a keyword string database.
  • Matcher 210 is configured to receive an input keyword string from the user interface 212, and match the input keyword string with one or more other keyword strings in keyword string database 214.
  • Wireless user device 208 also includes a menu constructor 216 configured to receive a keyword string from the matcher 210, determine the category of the keyword string.
  • the keyword string categories comprise a "brand" category for keyword strings that represent brands, a "title" category for keyword strings that represent titles and a "generic" category for keyword strings that belong to no other category.
  • menu constructor 216 is configured to use the category to obtain one or more corresponding service identifiers and their associated resource locator template from a resource locator template database 220. Service identifiers and resource locator templates are explained in more detail below with reference to FIG. 7 .
  • the menu constructor is also configured to make a list or menu based upon the one or more corresponding service identifiers and provide the menu to user 202 via user interface 212.
  • Wireless user device 208 also includes a resource locator populator 218 configured to receive an indication of the selected service and populate the corresponding resource locator template with the keyword string and the private data stored in private data store 222.
  • Wireless network interface 224 is configured to communicate via network 230 to obtain the corresponding service from one or more service providers 232.
  • the one or more service providers 232 are configured to initialize wireless user device 208 with a keyword string database 214 and a resource locator template database 220.
  • the information used to populate databases 214 and 220 may be extracted from a memory (not shown in FIG. 2 ) under the control of the one or more service providers 232.
  • FIG. 3 a flow diagram that illustrates installing one or more databases for token-based browsing on a wireless user device in accordance with the embodiment of the present invention is presented.
  • an initialization request is received.
  • a keyword string database that includes one or more keyword strings representing the name of an object or the attributes of an object associated with a service is created.
  • a resource locator template database that includes one or more entries comprising a service name and a resource locator template is created.
  • the keyword string database and the resource locator template database are provided in response to the initialization request.
  • FIG. 4 a block diagram that illustrates using a wireless user device configured for token-based browsing in accordance with embodiment of the present invention is presented.
  • Figure 4 illustrates use of wireless user device 408 after it has been initialized as described above with reference to FIG. 2 .
  • a user 402 enters an input keyword string comprising one or more keywords comprising one or more characters.
  • User interface 412 receives the input keyword string and sends it to matcher 410.
  • Matcher 410 receives the input keyword string and matches it with one or more other keyword strings in a keyword string database 414.
  • matcher 410 is configured to perform predictive matching, indicating a match based on incomplete input when further input cannot reduce the number of possible matches. Matches may be based on a prefix of a word. By way of example, the keyword string “jo” matches “john” and “jon”, but not “mojo”.
  • matches are based on one or more words in a keyword string, regardless of the order of keywords within the keyword string.
  • the keyword string “d jo” matches “doctor john smith” and “john dickenson”.
  • the “d” in “d jo” matches the “doctor” keyword of "doctor john” and the “dickenson” of "john dickenson”.
  • the “jo” in “d jo” matches the "john” in “doctor john” and the "john” in “john dickenson”.
  • a predetermined set of input characters are translated to the space character prior to performing a match.
  • the predetermined set of input characters comprises all non-alphanumeric characters.
  • the keyword string "d/jo” is translated to the keyword string "d jo”
  • the keyword string "j.d” is translated to the keyword string "j d”.
  • both keyword strings "d/jo” and "j.d” match the keyword string "john dickenson”.
  • matcher 410 returns a matching keyword string to user interface 412.
  • User interface 412 receives the matching keyword string and communicates it to menu constructor 416.
  • Menu constructor 416 receives the keyword string from the matcher, determines the category of the keyword string and uses the category to obtain one or more corresponding service identifiers and their associated resource locator template from a resource locator template database 220.
  • Menu constructor makes a list or menu based upon the one or more corresponding service identifiers and provides the menu to user 402 via user interface 412.
  • resource locator populator 418 receives an indication of the selected service and populates the corresponding resource locator template with the keyword string and private data if required by the resource locator template.
  • Wireless network interface 466 receives the populated resource locator and communicates via network 430 to obtain a service from at least one service provider 432.
  • FIG. 5 a flow diagram that illustrates using a wireless user device configured with a token-based Web browser in accordance with the embodiment of the present invention is presented.
  • a keyword string from a user is received.
  • a determination is made regarding whether the received keyword string matches a keyword string in a database of keyword strings.
  • predictive matching is used to indicate a match based on incomplete input when further input cannot reduce the number of possible matches.
  • the category of the keyword string is determined.
  • at least one service identifier associated with the category is rendered to the user.
  • a user-selected service identifier is received.
  • at least one variable in a resource locator template associated with the service is substituted with a string based at least in part on the keyword string entered by the user.
  • the resource locator is launched.
  • keyword string database 600 comprises one or more keyword strings (602-612). Keyword strings in keyword string database 600 are compared with an input keyword string to determine a match.
  • the keyword strings illustrated in database 600 are for purposes of illustration only. Those of ordinary skill in the art will recognize that many other keyword strings are possible.
  • FIG. 6B a block diagram that illustrates private data stored on a wireless user device in accordance with the embodiment of the present invention is presented.
  • the exemplary private data shown in FIG. 6B is a user's location 622, service preference 624, wireless carrier 626, preferred language 628, dietary preference 630, name 632, age 634, social security number 636, bank card number 638 and email address 640.
  • the private data illustrated in database 620 are for purposes of illustration only. Those of ordinary skill in the art will recognize that many other private data are possible.
  • Figures 7A - 7E illustrate resource locator templates and resource locator template databases in accordance with embodiment of the present invention.
  • Figure 7A illustrates a resource locator template
  • FIGS. 7B - 7E illustrate template databases for brands, titles, generic items and single-service objects, respectively.
  • Each entry in the databases of FIGS. 7B-7D includes the name of a service and a resource locator template, while the database of FIG. 7E maps a specific keyword string to a resource locator template.
  • Figures 8A - 17 illustrate various mechanisms for providing visual feedback of information to be disclosed to an external entity, in accordance with examples of the present invention.
  • Figures 8A - 8D illustrate methods for rendering a hyperlink that indicates private data will be disclosed upon launching the corresponding resource locator.
  • Figure 9 illustrates rendering a request for data from an external device to indicate private data will be disclosed upon issuing the request.
  • Figures 10-11 illustrate rendering a hyperlink to include a disclosure icon if the resource locator corresponding to the hyperlink requires private data.
  • Figures 12A-13 illustrate rendering a resource locator as a hyperlink that shows the various levels of detail of private data to be disclosed upon user-selection of the hyperlink.
  • Figures 14-15 illustrate incrementally updating a resource locator to indicate private data to be disclosed upon launching the resource locator.
  • Figures 16-17 illustrate dynamically modifying the amount of private data to be disclosed upon selection of a hyperlink.
  • FIGS. 8A and 8B illustrate using a "disclosure icon" to indicate private data will be disclosed upon launching a corresponding resource locator, while FIGS. 8C and 8D use a particular rendering of a hyperlink to make the indication.
  • FIG. 8A a block diagram that illustrates a location disclosure icon in accordance with one example of the present invention is presented.
  • a location disclosure icon 800 is presented with hyperlink 805 to indicate private data will be disclosed upon selecting the corresponding hyperlink 805.
  • the private data to be disclosed is the location of the user, allowing a service provider to determine one or more Italian restaurants near the user's current location.
  • FIG. 8B a block diagram that illustrates a financial disclosure icon in accordance with one example of the present invention is presented.
  • a financial disclosure icon 810 is presented with hyperlink 815 to indicate private data will be disclosed upon selecting the corresponding hyperlink 815.
  • the private data to be disclosed is the bank card information of the user, allowing a service provider to complete a purchase transaction by debiting the user's account.
  • FIG. 8C a block diagram that illustrates a location disclosure rendering in accordance with one example of the present invention is presented.
  • the rendering of a hyperlink 820 is modified to indicate private data will be disclosed upon selecting the corresponding hyperlink 820.
  • the particular rendering shown uses the font "Harlow Solid Italic" to indicate the pending disclosure of private data and is for illustrative purposes only. Those of ordinary skill in the art will recognize that many other renderings are possible.
  • FIG. 8D a block diagram that illustrates a location disclosure button in accordance with one example of the present invention is presented. As shown in FIG. 8D , a location disclosure button is used to indicate private data will be disclosed to indicate private data will be disclosed upon selecting the corresponding hyperlink.
  • FIG. 9 a flow diagram that illustrates a method for rendering a request for data from an external device to indicate private data will be disclosed upon issuing the request, in accordance with one example of the present invention is presented.
  • a request for data from an external device is received.
  • FIG. 10 a block diagram that illustrates rendering a hyperlink to include a disclosure icon if the corresponding resource locator requires private data, in accordance with one example of the present invention is presented.
  • resource locator 1000 includes a reference to a location variable 1005.
  • location variable 1005 is replaced with the location of a user, thus disclosing the user's location.
  • the user is made aware of the potential disclosure of private data by automatically rendering a hyperlink with a disclosure icon 1020 when launching the resource locator 1000 will require disclosure of private data 1005.
  • resource locator 1000 is automatically rendered as a hyperlink 1025 that includes a disclosure icon 1020.
  • FIG. 11 flow diagram that illustrates a method for rendering a hyperlink to include a disclosure icon if the resource locator corresponding to the hyperlink requires private data, in accordance with one example of the present invention is presented.
  • a resource locator is received.
  • a determination is made regarding whether launching the resource locator will disclose private data. If launching the resource locator will not disclose private data, at 1110 a rendering is provided. If launching the resource locator will disclose private data, at 1115 a rendering that indicates private data will be disclosed upon launching the resource locator is provided.
  • Figures 12A - 12E illustrate automatically updating a hyperlink to indicate private data to be disclosed upon user-selection of the hyperlink in accordance with examples of the present invention.
  • Figure 12A illustrates a resource locator that requires private data (city).
  • Figure 12B illustrates rendering the resource locator of FIG. 12A as a hyperlink 1225 that shows the private data (1220) to be disclosed upon user-selection of the hyperlink 1225.
  • the disclosure icon 1220 indicates the location "Vancouver.BC.CA" will be disclosed upon user-selection of the hyperlink 1225.
  • Figure 12C illustrates rendering the resource locator of FIG. 12A as a hyperlink 1235 that shows a transformed version of the private data (1230) to be disclosed upon user-selection of the hyperlink 1235.
  • the disclosure icon 1230 indicates the location "Vancouver” will be disclosed upon user-selection of the hyperlink 1235.
  • Figure 12D illustrates rendering the resource locator of FIG. 12A as a hyperlink 1245 that discloses a more specific version of the private data (1240) to be disclosed upon user-selection of the hyperlink 1245.
  • the disclosure icon 1240 indicates the location "Main St” will be disclosed upon user-selection of the hyperlink 1245.
  • Figure 12E illustrates rendering the resource locator of FIG. 12A as a hyperlink 1255 that discloses a generalized version of the private data (1250) to be disclosed upon user-selection of the hyperlink 1255.
  • the disclosure icon 1250 indicates the location "Earth” will be disclosed upon user-selection of the hyperlink 1255.
  • FIG. 13 a flow diagram that illustrates a method for rendering a hyperlink to indicate the private data that will be disclosed upon launching the resource locator associated with the hyperlink, in accordance with one example of the present invention is presented.
  • a resource locator is received.
  • a determination is made regarding whether launching the resource locator will disclose private data. If launching the resource locator will not disclose private data, a rendering is provided at 1310. If launching the resource locator will disclose private data, at 1315 a rendering that indicates the private data that will be disclosed upon launching the resource locator is provided.
  • a determination is made regarding whether the resource locator was selected. If the resource locator was selected, at 1325 the resource locator is launched.
  • FIG. 14 a block diagram that illustrates incrementally updating a resource locator to indicate private data to be disclosed upon launching the resource locator, in accordance with one example of the present invention is presented.
  • a hyperlink based on a resource locator 1470 that requires private data 1410 is initially rendered as a hyperlink 1430 that reveals user-selection of the hyperlink 1430 will require disclosure of private data, without specifying the private data to be disclosed.
  • icon 1425 indicates location information will be disclosed.
  • user-selection of icon 1425 it is transformed to indicate the actual data to be submitted. In this case, the user's location is Vancouver 1440.
  • the associated resource locator including the private data 1465 is launched.
  • FIG. 15 a flow diagram that illustrates incrementally updating a resource locator to indicate private data to be disclosed upon launching the resource locator, in accordance with one example of the present invention is presented.
  • a resource locator is received.
  • a determination is made regarding whether launching of the resource locator will disclose private data. If launching of the resource locator will not disclose private data, at 1510 a rendering is provided. If launching of the resource locator will disclose private data, at 1515 a rendering that indicates private data will be disclosed upon launching the resource locator is provided.
  • a rendering that indicates the private data that will be disclosed upon launching the resource locator is provided.
  • FIG. 16 a block diagram that illustrates dynamically modifying the amount of private data to be disclosed upon selection of a hyperlink, in accordance with one example of the present invention is presented.
  • a hyperlink based on a resource locator 1665 that requires private data 1610 is initially rendered as a hyperlink 1630 that reveals user-selection of the hyperlink 1630 will require disclosure of private data.
  • icon 1625 indicates location information will be disclosed.
  • the user is allowed to downgrade the link to a form that does not require disclosure of private data.
  • the user right-clicks on the hyperlink 1630 and selects from a pop-up property menu a "disable personal information" option or the equivalent.
  • the user presses a button on a menu-bar for a Window is operative to globally turn off disclosure of personal information.
  • globally turning of the disclosure of personal information causes the initial resource locator 1630 to be rendered without the disclosure icon.
  • FIG. 17 a flow diagram that illustrates modifying the amount of private data to be disclosed upon selection of a hyperlink, in accordance with one example of the present invention is presented.
  • a resource locator is received.
  • a determination is made regarding whether launching of the resource locator will disclose private data. If launching of the resource locator will not disclose private data, at 1710 a rendering is provided. If launching of the resource locator will disclose private data, at 1715 a rendering that indicates private data will be disclosed upon launching the resource locator is provided.
  • a rendering that indicates private data will be disclosed upon launching the resource locator is provided.
  • downgrading the link to a form that does not require the private data is enabled.
  • a determination is made regarding whether the resource locator has been selected. If the resource locator has been selected, it is launched at 1730.

Abstract

A method for rendering a request for data from an external device to indicate private data will be disclosed upon issuing the request, the method comprising: receiving a request for data, said request to be issued to an external device; determining whether the request includes private data; rendering said requested data if said request does not include private data; and rendering said request to indicate said private data will be disclosed upon issuing said request if said request includes private data.

Description

    FIELD OF THE INVENTION
  • The present invention relates to the field of computer science. More particularly, the present invention relates to a method and apparatus for token-based Web browsing with visual feedback of disclosure.
  • BACKGROUND OF THE INVENTION
  • The ability to quickly access information about various services is important to the typical user of a wireless user device such as a mobile phone or a personal data assistant (PDA). Such a user typically accesses information by entering the name of the item for which information is desired. For example, a user desiring to find a movie review for a film entitled "Dances with Wolves" would enter the keyword string "Dances with Wolves". The wireless user device must then obtain this information and render it to the user. Some of the information may reside locally on the user device, while other information must be obtained from an external source.
  • In one solution, the wireless user device periodically communicates with one or more service providers to obtain updates for all information available to the wireless user device. This enables the user to store the entire body of information locally. Unfortunately, this solution requires a relatively large database on a user device. Such a local database typically becomes outdated quickly and is difficult to maintain.
  • Another solution includes requiring the user search a World Wide Web ("Web") portal for the desired information. Unfortunately, this solution requires the user enter a relatively large amount of text. Furthermore, Web portals typically have a relatively large amount of latency and portal menus typically change frequently, confusing the user.
  • Additionally, obtaining useful information from an external source such as a service provider often requires disclosing private data. For example, a user desiring weather information for the user's current location must first disclose the location. For various reasons, the user may not want this information disclosed.
  • US 6,324,566 B1 discloses a method and system for browsing the web using bookmarks.
  • Accordingly, a need exists in the prior art for a solution that supports local searching on a device, such that a service is accessible by name. A further need exists for such a solution that minimizes the amount of text that a user must enter. Yet another need exists for a solution that maintains data on the device as long as possible. A further need exists for such a solution that allows private data to be incorporated into a search on a query-by-query basis, simply and efficiently, but with the user's knowledge and consent. Yet another need exists for such a solution that allows a relatively large amount of content to be stored on a wireless user device.
  • The present invention is defined in claims 1-12.
  • SUMMARY OF THE INVENTION
  • A data communications network may be browsed using one or more tokens by receiving an input keyword string from a user, determining whether there is a match between the input keyword string and a database of keyword strings, determining a category of the keyword string, rendering to the user at least one service identifier associated with the category, receiving a user-selected service identifier in response to the rendering, substituting at least one variable in a resource locator template associated with the service with a string based at least in part on the keyword string entered by the user and launching the resource locator. According to one aspect, a special rendering of a hyperlink corresponding to the resource locator is used to indicate private data will be disclosed upon launching the resource locator.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one embodiment of the present invention and, together with the detailed description, serve to explain the principles and implementations of the invention.
  • In the drawings:
    • FIG. 1 is a block diagram of a computer system suitable for implementing aspects of the present invention.
    • FIG. 2 is a block diagram that illustrates installing one or more databases on a wireless user device in accordance with the embodiment of the present invention.
    • FIG. 3 is a flow diagram that illustrates installing one or more databases for token-based browsing on a wireless user device in accordance with the embodiment of the present invention.
    • FIG. 4 is a block diagram that illustrates using a wireless user device configured for token-based browsing in accordance with embodiment of the present invention.
    • FIG. 5 is a flow diagram that illustrates using a wireless user device configured with a token-based Web browser in accordance with the embodiment of the present invention.
    • FIG. 6A is a block diagram that illustrates a keyword string database in accordance with the embodiment of the present invention.
    • FIG. 6A is a block diagram that illustrates private data stored on a wireless user device in accordance with the embodiment of the present invention.
    • FIG. 7A is a block diagram that illustrates a resource locator template in accordance with the embodiment of the present invention.
    • FIG. 7B is a block diagram that illustrates a brand resource locator template database in accordance with the embodiment of the present invention.
    • FIG. 7C is a block diagram that illustrates a title resource locator template database in accordance with the embodiment of the present invention.
    • FIG. 7D is a block diagram that illustrates a generic resource locator template database in accordance with the embodiment of the present invention.
    • FIG. 7E is a block diagram that illustrates a single service resource locator template database in accordance with the embodiment of the present invention.
    • FIG. 8A is a block diagram that illustrates a location disclosure icon in accordance with one example of the present invention.
    • FIG. 8B is a block diagram that illustrates a financial disclosure icon in accordance with one example of the present invention.
    • FIG. 8C is a block diagram that illustrates a location disclosure rendering in accordance with one example of the present invention.
    • FIG. 8D is a block diagram that illustrates a location disclosure button in accordance with one example of the present invention.
    • FIG. 9 is a flow diagram that illustrates a method for rendering a request for data from an external device to indicate private data will be disclosed upon issuing the request, in accordance with one example of the present invention.
    • FIG. 10 is a block diagram that illustrates rendering a hyperlink to include a disclosure icon if the corresponding resource locator requires private data, in accordance with one example of the present invention.
    • FIG. 11 is flow diagram that illustrates a method for rendering a hyperlink to include a disclosure icon if the resource locator corresponding to the hyperlink requires private data, in accordance with one example of the present invention.
    • FIG. 12A is a block diagram of a resource locator that requires private data.
    • FIG. 12B is a block diagram of a hyperlink that illustrates rendering the resource locator of FIG. 12A as a hyperlink that shows the private data to be disclosed upon user-selection of the hyperlink, in accordance with one example of the present invention.
    • FIG. 12C is a block diagram of a hyperlink that illustrates rendering the resource locator of FIG. 12A as a hyperlink that shows a transformed version of the private data to be disclosed upon user-selection of the hyperlink, in accordance with one example of the present invention.
    • FIG. 12D is a block diagram of a hyperlink that illustrates rendering the resource locator of FIG. 12A as a hyperlink that discloses a more specific version of the private data to be disclosed upon user-selection of the hyperlink, in accordance with one example of the present invention.
    • FIG. 12E is a block diagram of a hyperlink that illustrates rendering the resource locator of FIG. 12A as a hyperlink that discloses a generalized version of the private data to be disclosed upon user-selection of the hyperlink, in accordance with one example of the present invention.
    • FIG. 13 is a flow diagram that illustrates a method for rendering a hyperlink to indicate the private data that will be disclosed upon launching the resource locator associated with the hyperlink, in accordance with one example of the present invention.
    • FIG. 14 is a block diagram that illustrates incrementally updating an resource locator to indicate private data to be disclosed upon launching the resource locator, in accordance with one example of the present invention.
    • FIG. 15 is a flow diagram that illustrates incrementally updating an resource locator to indicate private data to be disclosed upon launching the resource locator, in accordance with one example of the present invention.
    • FIG. 16 is a block diagram that illustrates dynamically modifying the amount of private data to be disclosed upon selection of a hyperlink, in accordance with one example of the present invention.
    • FIG. 17 is a flow diagram that illustrates modifying the amount of private data to be disclosed upon selection of a hyperlink, in accordance with one example of the present invention.
    DETAILED DESCRIPTION
  • Embodiment of the present invention is described herein in the context of a method and apparatus for token-based Web browsing with visual feedback of disclosure. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other examples of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.
  • In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
  • In accordance with the embodiment of the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems (OS), computing platforms, firmware, computer programs, computer languages, and/or general-purpose machines. The method can be run as a programmed process running on processing circuitry. The processing circuitry can take the form of numerous combinations of processors and operating systems, or a stand-alone device. The process can be implemented as instructions executed by such hardware, hardware alone, or any combination thereof. The software may be stored on a program storage device readable by a machine.
  • In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable logic devices (FPLDs), including field programmable gate arrays (FPGAs) and complex programmable logic devices (CPLDs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope of the inventive concepts disclosed herein.
  • In the context of the present invention, the term "network" includes local area networks, wide area networks, the Internet, cable television systems, telephone systems, wireless telecommunications systems, fiber optic networks, ATM networks, frame relay networks, satellite communications systems, and the like. Such networks are well known in the art and consequently are not further described here.
  • In the context of the present invention, the term "wireless user device" includes any device capable of wireless communication and capable of rendering information to a user. The information may be rendered, by way of example, by visual, auditory or tactile means. Exemplary wireless user devices include, by way of example, a personal digital assistant (PDA), a mobile phone, a personal computer, a pager, or the like.
  • In the context of the present invention, the term "private data" refers to personal information about a user. A user may desire to limit or restrict dissemination or availability of such information. Private data may be unique for a particular individual. A social security number is an example of private data that is unique to a particular individual. Private data may also be non-unique information concerning a particular individual. A language preference of "English" is an example of private but non-unique information concerning a particular individual.
  • In the context of the present invention, the term "keyword string" refers to one or more keywords comprising one or more characters, which together represent the name of an object or the attributes of an object associated with a service. In accordance with the embodiment of the present invention, a keyword string represents well-known brands, titles and generic categories. Exemplary brands include the keyword strings "Starbucks", "Olive Garden" and "Alpo". Exemplary titles include the keyword strings "Dances with Wolves", "Mission Impossible" and "Harry Potter". Exemplary generic categories include "ATM", "Weather" and "Hospital".
  • In the context of the present invention, the term "resource locator" or "RL" is defined as an identifier used for accessing a resource. A resource locator may be the name of the resource. A resource locator may also be a Uniform Resource Identifier (URI). More particularly, a resource locator may be a uniform resource locator (URL). URIs and URLs are described in T. Berners-Lee, "Uniform Resource Identifiers (URI): Generic Syntax", Network Working Group Request for Comments: 2396, August 1998. The resource may be an HTML page, an image file, a program such as a common gateway interface application (CGI) or Java™ applet, a text file, a document, or the like.
  • Figure 1 depicts a block diagram of a computer system 100 suitable for implementing aspects of the present invention. As shown in FIG. 1, system 100 includes a bus 102 which interconnects major subsystems such as a processor 104, an internal memory 106 (such as a RAM), an input/output (I/O) controller 108, a removable memory (such as a memory card), an external device such as a display screen 110 via display adapter 112, a roller-type input device 114, a joystick 116, a numeric keyboard 118, an alphanumeric keyboard 118, directional navigation pad 126 and a wireless interface 120. Many other devices can be connected. Wireless network interface 120, wired network interface 128, or both, may be used to interface to a local or wide area network (such as the Internet) using any network interface system known to those skilled in the art.
  • Many other devices or subsystems (not shown) may be connected in a similar manner. Also, it is not necessary for all of the devices shown in FIG. 1 to be present to practice the present invention. Furthermore, the devices and subsystems may be interconnected in different ways from that shown in FIG. 1. Code to implement the present invention may be operably disposed in internal memory 106 or stored on storage media such as removable memory 122, a floppy disk or a CD-ROM.
  • Turning now to FIG. 2, a block diagram that illustrates installing one or more databases on a wireless user device in accordance with the embodiment of the present invention is presented. Wireless user device 208 includes a user interface 212 configured to receive input from a user 202 and to render digital content to the user 202. Wireless user device 208 also includes a matcher 210 in communication with both the user interface 212 and a keyword string database. Matcher 210 is configured to receive an input keyword string from the user interface 212, and match the input keyword string with one or more other keyword strings in keyword string database 214. Wireless user device 208 also includes a menu constructor 216 configured to receive a keyword string from the matcher 210, determine the category of the keyword string. According to the embodiment of the present invention, the keyword string categories comprise a "brand" category for keyword strings that represent brands, a "title" category for keyword strings that represent titles and a "generic" category for keyword strings that belong to no other category.
  • Still referring to FIG. 2, menu constructor 216 is configured to use the category to obtain one or more corresponding service identifiers and their associated resource locator template from a resource locator template database 220. Service identifiers and resource locator templates are explained in more detail below with reference to FIG. 7. The menu constructor is also configured to make a list or menu based upon the one or more corresponding service identifiers and provide the menu to user 202 via user interface 212. Wireless user device 208 also includes a resource locator populator 218 configured to receive an indication of the selected service and populate the corresponding resource locator template with the keyword string and the private data stored in private data store 222. Wireless network interface 224 is configured to communicate via network 230 to obtain the corresponding service from one or more service providers 232.
  • The one or more service providers 232 are configured to initialize wireless user device 208 with a keyword string database 214 and a resource locator template database 220. The information used to populate databases 214 and 220 may be extracted from a memory (not shown in FIG. 2) under the control of the one or more service providers 232.
  • Many other devices or subsystems (not shown) may be connected in manner similar to that shown in FIG. 2. Also, it is not necessary for all of the devices shown in FIG. 2 to be present to practice the present invention. Furthermore, the devices and subsystems may be interconnected in different ways from that shown in FIG. 2. The operations described with respect to matcher 210, user interface 212, resource locator populator 218, menu constructor 216 and wireless network interface 224 may be combined in various ways. Also, keyword string database 214, resource locator template database 220 and private data store 222 may be combined into a smaller number of databases, or further divided into a larger number of databases. Use of wireless user device 208 is described below in more detail, with reference to FIG. 4.
  • Turning now to FIG. 3, a flow diagram that illustrates installing one or more databases for token-based browsing on a wireless user device in accordance with the embodiment of the present invention is presented. At 300, an initialization request is received. At 305, a keyword string database that includes one or more keyword strings representing the name of an object or the attributes of an object associated with a service is created. At 310, a resource locator template database that includes one or more entries comprising a service name and a resource locator template is created. At 315, the keyword string database and the resource locator template database are provided in response to the initialization request.
  • Turning now to FIG. 4, a block diagram that illustrates using a wireless user device configured for token-based browsing in accordance with embodiment of the present invention is presented. Figure 4 illustrates use of wireless user device 408 after it has been initialized as described above with reference to FIG. 2. A user 402 enters an input keyword string comprising one or more keywords comprising one or more characters. User interface 412 receives the input keyword string and sends it to matcher 410. Matcher 410 receives the input keyword string and matches it with one or more other keyword strings in a keyword string database 414.
  • According to the embodiment of the present invention, matcher 410 is configured to perform predictive matching, indicating a match based on incomplete input when further input cannot reduce the number of possible matches. Matches may be based on a prefix of a word. By way of example, the keyword string "jo" matches "john" and "jon", but not "mojo".
  • According to the embodiment of the present invention, matches are based on one or more words in a keyword string, regardless of the order of keywords within the keyword string. By way of example, the keyword string "d jo" matches "doctor john smith" and "john dickenson". In this example, the "d" in "d jo" matches the "doctor" keyword of "doctor john" and the "dickenson" of "john dickenson". And the "jo" in "d jo" matches the "john" in "doctor john" and the "john" in "john dickenson".
  • According to another example of the present invention, a predetermined set of input characters are translated to the space character prior to performing a match. According to one example of the present invention, the predetermined set of input characters comprises all non-alphanumeric characters. By way of example, the keyword string "d/jo" is translated to the keyword string "d jo", and the keyword string "j.d" is translated to the keyword string "j d". Thus translated, both keyword strings "d/jo" and "j.d" match the keyword string "john dickenson".
  • Still referring to FIG. 4, matcher 410 returns a matching keyword string to user interface 412. User interface 412 receives the matching keyword string and communicates it to menu constructor 416. Menu constructor 416 receives the keyword string from the matcher, determines the category of the keyword string and uses the category to obtain one or more corresponding service identifiers and their associated resource locator template from a resource locator template database 220. Menu constructor makes a list or menu based upon the one or more corresponding service identifiers and provides the menu to user 402 via user interface 412. resource locator populator 418 receives an indication of the selected service and populates the corresponding resource locator template with the keyword string and private data if required by the resource locator template. Wireless network interface 466 receives the populated resource locator and communicates via network 430 to obtain a service from at least one service provider 432.
  • Turning now to FIG. 5, a flow diagram that illustrates using a wireless user device configured with a token-based Web browser in accordance with the embodiment of the present invention is presented. At 500, a keyword string from a user is received. At 505, a determination is made regarding whether the received keyword string matches a keyword string in a database of keyword strings. According to the embodiment of the present invention, predictive matching is used to indicate a match based on incomplete input when further input cannot reduce the number of possible matches. At 510, the category of the keyword string is determined. At 515, at least one service identifier associated with the category is rendered to the user. At 520, a user-selected service identifier is received. At 525, at least one variable in a resource locator template associated with the service is substituted with a string based at least in part on the keyword string entered by the user. At 530, the resource locator is launched.
  • Turning now to FIG. 6A, a block diagram that illustrates a keyword string database in accordance with the embodiment of the present invention is presented. As shown in FIG. 6A, keyword string database 600 comprises one or more keyword strings (602-612). Keyword strings in keyword string database 600 are compared with an input keyword string to determine a match. The keyword strings illustrated in database 600 are for purposes of illustration only. Those of ordinary skill in the art will recognize that many other keyword strings are possible.
  • Turning now to FIG. 6B, a block diagram that illustrates private data stored on a wireless user device in accordance with the embodiment of the present invention is presented. The exemplary private data shown in FIG. 6B is a user's location 622, service preference 624, wireless carrier 626, preferred language 628, dietary preference 630, name 632, age 634, social security number 636, bank card number 638 and email address 640. The private data illustrated in database 620 are for purposes of illustration only. Those of ordinary skill in the art will recognize that many other private data are possible.
  • Figures 7A - 7E illustrate resource locator templates and resource locator template databases in accordance with embodiment of the present invention. Figure 7A illustrates a resource locator template, and FIGS. 7B - 7E illustrate template databases for brands, titles, generic items and single-service objects, respectively. Each entry in the databases of FIGS. 7B-7D includes the name of a service and a resource locator template, while the database of FIG. 7E maps a specific keyword string to a resource locator template.
  • Figures 8A - 17 illustrate various mechanisms for providing visual feedback of information to be disclosed to an external entity, in accordance with examples of the present invention. Figures 8A - 8D illustrate methods for rendering a hyperlink that indicates private data will be disclosed upon launching the corresponding resource locator. Figure 9 illustrates rendering a request for data from an external device to indicate private data will be disclosed upon issuing the request. Figures 10-11 illustrate rendering a hyperlink to include a disclosure icon if the resource locator corresponding to the hyperlink requires private data. Figures 12A-13 illustrate rendering a resource locator as a hyperlink that shows the various levels of detail of private data to be disclosed upon user-selection of the hyperlink. Figures 14-15 illustrate incrementally updating a resource locator to indicate private data to be disclosed upon launching the resource locator. Figures 16-17 illustrate dynamically modifying the amount of private data to be disclosed upon selection of a hyperlink.
  • Figures 8A and 8B illustrate using a "disclosure icon" to indicate private data will be disclosed upon launching a corresponding resource locator, while FIGS. 8C and 8D use a particular rendering of a hyperlink to make the indication.
  • Turning now to FIG. 8A, a block diagram that illustrates a location disclosure icon in accordance with one example of the present invention is presented. As shown in FIG. 8A, a location disclosure icon 800 is presented with hyperlink 805 to indicate private data will be disclosed upon selecting the corresponding hyperlink 805. In this case, the private data to be disclosed is the location of the user, allowing a service provider to determine one or more Italian restaurants near the user's current location.
  • Turning now to FIG. 8B, a block diagram that illustrates a financial disclosure icon in accordance with one example of the present invention is presented. As shown in FIG. 8B, a financial disclosure icon 810 is presented with hyperlink 815 to indicate private data will be disclosed upon selecting the corresponding hyperlink 815. In this case, the private data to be disclosed is the bank card information of the user, allowing a service provider to complete a purchase transaction by debiting the user's account.
  • Turning now to FIG. 8C, a block diagram that illustrates a location disclosure rendering in accordance with one example of the present invention is presented. As shown in FIG. 8C, the rendering of a hyperlink 820 is modified to indicate private data will be disclosed upon selecting the corresponding hyperlink 820. The particular rendering shown uses the font "Harlow Solid Italic" to indicate the pending disclosure of private data and is for illustrative purposes only. Those of ordinary skill in the art will recognize that many other renderings are possible.
  • Turning now to FIG. 8D, a block diagram that illustrates a location disclosure button in accordance with one example of the present invention is presented. As shown in FIG. 8D, a location disclosure button is used to indicate private data will be disclosed to indicate private data will be disclosed upon selecting the corresponding hyperlink.
  • Turning now to FIG. 9, a flow diagram that illustrates a method for rendering a request for data from an external device to indicate private data will be disclosed upon issuing the request, in accordance with one example of the present invention is presented. At 900, a request for data from an external device is received. At 905, a determination is made regarding whether the request includes private data. If the request does not include private data, the requested data is displayed at 910. If the request includes private data, the request is rendered to indicate private data will be disclosed upon issuing the request.
  • Turning now to FIG. 10, a block diagram that illustrates rendering a hyperlink to include a disclosure icon if the corresponding resource locator requires private data, in accordance with one example of the present invention is presented. As shown in FIG. 10, resource locator 1000 includes a reference to a location variable 1005. Upon launching resource locator 1000, location variable 1005 is replaced with the location of a user, thus disclosing the user's location. According to one example of the present invention, the user is made aware of the potential disclosure of private data by automatically rendering a hyperlink with a disclosure icon 1020 when launching the resource locator 1000 will require disclosure of private data 1005. As shown in FIG. 10, resource locator 1000 is automatically rendered as a hyperlink 1025 that includes a disclosure icon 1020.
  • Turning now to FIG. 11, flow diagram that illustrates a method for rendering a hyperlink to include a disclosure icon if the resource locator corresponding to the hyperlink requires private data, in accordance with one example of the present invention is presented. At 1100, a resource locator is received. At 1105, a determination is made regarding whether launching the resource locator will disclose private data. If launching the resource locator will not disclose private data, at 1110 a rendering is provided. If launching the resource locator will disclose private data, at 1115 a rendering that indicates private data will be disclosed upon launching the resource locator is provided. At 1120, a determination is made regarding whether the resource locator has been selected. If the resource locator has been selected, it is launched at 1125.
  • Figures 12A - 12E illustrate automatically updating a hyperlink to indicate private data to be disclosed upon user-selection of the hyperlink in accordance with examples of the present invention. Figure 12A illustrates a resource locator that requires private data (city). Figure 12B illustrates rendering the resource locator of FIG. 12A as a hyperlink 1225 that shows the private data (1220) to be disclosed upon user-selection of the hyperlink 1225. Here, the disclosure icon 1220 indicates the location "Vancouver.BC.CA" will be disclosed upon user-selection of the hyperlink 1225. Figure 12C illustrates rendering the resource locator of FIG. 12A as a hyperlink 1235 that shows a transformed version of the private data (1230) to be disclosed upon user-selection of the hyperlink 1235. Here, the disclosure icon 1230 indicates the location "Vancouver" will be disclosed upon user-selection of the hyperlink 1235. Figure 12D illustrates rendering the resource locator of FIG. 12A as a hyperlink 1245 that discloses a more specific version of the private data (1240) to be disclosed upon user-selection of the hyperlink 1245. Here, the disclosure icon 1240 indicates the location "Main St" will be disclosed upon user-selection of the hyperlink 1245. Figure 12E illustrates rendering the resource locator of FIG. 12A as a hyperlink 1255 that discloses a generalized version of the private data (1250) to be disclosed upon user-selection of the hyperlink 1255. Here, the disclosure icon 1250 indicates the location "Earth" will be disclosed upon user-selection of the hyperlink 1255.
  • Turning now to FIG. 13, a flow diagram that illustrates a method for rendering a hyperlink to indicate the private data that will be disclosed upon launching the resource locator associated with the hyperlink, in accordance with one example of the present invention is presented. At 1300, a resource locator is received. At 1305, a determination is made regarding whether launching the resource locator will disclose private data. If launching the resource locator will not disclose private data, a rendering is provided at 1310. If launching the resource locator will disclose private data, at 1315 a rendering that indicates the private data that will be disclosed upon launching the resource locator is provided. At 1320, a determination is made regarding whether the resource locator was selected. If the resource locator was selected, at 1325 the resource locator is launched.
  • Turning now to FIG. 14, a block diagram that illustrates incrementally updating a resource locator to indicate private data to be disclosed upon launching the resource locator, in accordance with one example of the present invention is presented. As shown in FIG. 14, a hyperlink based on a resource locator 1470 that requires private data 1410 is initially rendered as a hyperlink 1430 that reveals user-selection of the hyperlink 1430 will require disclosure of private data, without specifying the private data to be disclosed. In this case, icon 1425 indicates location information will be disclosed. Upon user-selection of icon 1425, it is transformed to indicate the actual data to be submitted. In this case, the user's location is Vancouver 1440. Upon user-selection of hyperlink 1445, the associated resource locator including the private data 1465 is launched.
  • Turning now to FIG. 15, a flow diagram that illustrates incrementally updating a resource locator to indicate private data to be disclosed upon launching the resource locator, in accordance with one example of the present invention is presented. At 1300, a resource locator is received. At 1505, a determination is made regarding whether launching of the resource locator will disclose private data. If launching of the resource locator will not disclose private data, at 1510 a rendering is provided. If launching of the resource locator will disclose private data, at 1515 a rendering that indicates private data will be disclosed upon launching the resource locator is provided. At 1520, a determination is made regarding whether the resource locator has been selected. If the resource locator has been selected, at 1525 a rendering that indicates the private data that will be disclosed upon launching the resource locator is provided. At 1530, a determination is made regarding whether the hyperlink associated with the resource locator has been selected. If the hyperlink has been selected, it is launched at 1535.
  • Turning now to FIG. 16, a block diagram that illustrates dynamically modifying the amount of private data to be disclosed upon selection of a hyperlink, in accordance with one example of the present invention is presented. As shown in FIG. 16, a hyperlink based on a resource locator 1665 that requires private data 1610 is initially rendered as a hyperlink 1630 that reveals user-selection of the hyperlink 1630 will require disclosure of private data. In this case, icon 1625 indicates location information will be disclosed. At this point, the user is allowed to downgrade the link to a form that does not require disclosure of private data. According to one example of the present invention, the user right-clicks on the hyperlink 1630 and selects from a pop-up property menu a "disable personal information" option or the equivalent. According to another example of the present invention, the user presses a button on a menu-bar for a Window is operative to globally turn off disclosure of personal information. In this case, globally turning of the disclosure of personal information causes the initial resource locator 1630 to be rendered without the disclosure icon.
  • Turning now to FIG. 17, a flow diagram that illustrates modifying the amount of private data to be disclosed upon selection of a hyperlink, in accordance with one example of the present invention is presented. At 1700, a resource locator is received. At 1705, a determination is made regarding whether launching of the resource locator will disclose private data. If launching of the resource locator will not disclose private data, at 1710 a rendering is provided. If launching of the resource locator will disclose private data, at 1715 a rendering that indicates private data will be disclosed upon launching the resource locator is provided. At 1720, downgrading the link to a form that does not require the private data is enabled. At 1725, a determination is made regarding whether the resource locator has been selected. If the resource locator has been selected, it is launched at 1730.
  • While examples and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the scope of the appended claims.

Claims (12)

  1. A method for browsing a data communications network using one or more tokens, the method comprising:
    receiving an input keyword string from a user, said input keyword string comprising one or more keywords comprising one or more characters;
    determining whether there is a match between said input keyword string and a database of keyword strings;
    determining a category of said keyword string;
    rendering to said user at least one service identifier associated with said category;
    receiving a user-selected service identifier in response to said rendering;
    substituting at least one variable in a resource locator template associated with said service with a string based at least in part on the keyword string entered by the user; and
    launching said resource locator.
  2. The method of claim 1 wherein said determining whether there is a match further comprises indicating a match based on incomplete input when further input cannot reduce the number of possible matches.
  3. The method of claim 1 wherein said determining whether there is a match further comprises indicating a match if prefixes of keywords in said input keyword string match prefixes of keywords in a keyword string of said database.
  4. The method of claim 1 wherein said determining whether there is a match further comprises indicating a match if at least one keyword prefix in said input keyword string matches a corresponding keyword prefix in a keyword string of said database.
  5. A program storage device readable by a machine, embodying a program of instructions executable by the machine to perform a method for browsing a data communications network using one or more tokens, the method comprising:
    receiving an input keyword string from a user, said input keyword string comprising one or more keywords comprising one or more characters;
    determining whither there is a match between said input keyword string and a database of keyword strings;
    determining a category of said keyword string;
    rendering to said user at least one service identifier associated with said category;
    receiving a user-selected service identifier in response to said rendering;
    substituting at least one variable in a resource locator template associated with said service with a string based at least in part on the keyword string entered by the user; and
    launching said resource locator.
  6. The program storage device of claim 5 wherein said determining whether there is a match further comprises indicating a match based on incomplete input when further input cannot reduce the number of possible matches.
  7. The program storage device of claim 5 wherein said determining whether there is a match further comprises indicating a match if prefixes of keywords in said input keyword string match prefixes of keywords in a keyword string of said database.
  8. The program storage device of claim 5 wherein said determining whether there is a match further comprises indicating a match if at least one keyword prefix in said input keyword string matches a corresponding keyword prefix in a keyword string of said database.
  9. An apparatus for browsing a data communications network using one or more tokens, the apparatus comprising:
    means for receiving an input keyword string from a user, said input keyword string comprising one or more keywords comprising one or more characters;
    means for determining whether there is a match between said input keyword string and a database of keyword strings;
    means for determining a category of said keyword string,
    means for rendering to said user at least one service identifier associated with said category;
    means for receiving a user-selected service identifier in response to said rendering;
    means for substituting at least one variable in a resource locator template associated with said service with a string based at least in part on the keyword string entered by the user, and
    means for launching said resource locator.
  10. The apparatus of claim 9 wherein said means for determining whether there is a match further comprises means for indicating a match based on incomplete input when further input cannot reduce the number of possible matches.
  11. The apparatus of claim 9 wherein said means for determining whether there is a match further comprises means for indicating a match if prefixes of keywords in said input keyword string match prefixes of keywords in a keyword string of said database.
  12. The apparatus of claim 9 wherein said means for determining whether there is a match further comprises means for indicating a match if at least one keyword prefix in said input keyword string matches a corresponding keyword prefix in a keyword string of said database.
EP04706591A 2003-01-31 2004-01-30 Method for browsing a data communications network Expired - Lifetime EP1588294B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP06118332A EP1720110A1 (en) 2003-01-31 2004-01-30 Method for browsing a data communications network

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10/355,719 US7167905B2 (en) 2003-01-31 2003-01-31 Token-based Web browsing with visual feedback of disclosure
US355719 2003-01-31
PCT/CA2004/000140 WO2004068256A2 (en) 2003-01-31 2004-01-30 Method for browsing a data communications network

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP06118332A Division EP1720110A1 (en) 2003-01-31 2004-01-30 Method for browsing a data communications network
EP06118332.3 Division-Into 2006-08-02

Publications (2)

Publication Number Publication Date
EP1588294A2 EP1588294A2 (en) 2005-10-26
EP1588294B1 true EP1588294B1 (en) 2011-12-14

Family

ID=32770606

Family Applications (2)

Application Number Title Priority Date Filing Date
EP04706591A Expired - Lifetime EP1588294B1 (en) 2003-01-31 2004-01-30 Method for browsing a data communications network
EP06118332A Withdrawn EP1720110A1 (en) 2003-01-31 2004-01-30 Method for browsing a data communications network

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP06118332A Withdrawn EP1720110A1 (en) 2003-01-31 2004-01-30 Method for browsing a data communications network

Country Status (6)

Country Link
US (3) US7167905B2 (en)
EP (2) EP1588294B1 (en)
CN (2) CN100444161C (en)
AT (1) ATE537508T1 (en)
CA (1) CA2514216A1 (en)
WO (1) WO2004068256A2 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8090698B2 (en) 2004-05-07 2012-01-03 Ebay Inc. Method and system to facilitate a search of an information resource
US7895218B2 (en) 2004-11-09 2011-02-22 Veveo, Inc. Method and system for performing searches for television content using reduced text input
GB2432236A (en) * 2005-11-09 2007-05-16 Samsung Electronics Co Ltd Associating a text input string with an application in a mobile communication device
CN101075234A (en) * 2006-05-17 2007-11-21 联发博动科技(北京)有限公司 Method and system for inputting WAP browser
US9563621B2 (en) * 2007-03-30 2017-02-07 Nokia Technologies Oy Search based user interface
CN101951433A (en) * 2010-09-02 2011-01-19 宇龙计算机通信科技(深圳)有限公司 Method and system for processing application icon and mobile terminal
US9146765B2 (en) 2011-03-11 2015-09-29 Microsoft Technology Licensing, Llc Virtual disk storage techniques
KR101401371B1 (en) * 2011-12-26 2014-05-30 박석일 Method of automatic identification service based on keyword identification search
US9251201B2 (en) * 2012-12-14 2016-02-02 Microsoft Technology Licensing, Llc Compatibly extending offload token size
US10721313B2 (en) 2015-10-30 2020-07-21 Lg Electronics Inc. Method for processing service request in wireless communication system and apparatus therefor
SE544484C2 (en) 2019-02-18 2022-06-14 Jondetech Sensors Ab Publ Method and system for detecting presence of a person

Family Cites Families (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5157783A (en) * 1988-02-26 1992-10-20 Wang Laboratories, Inc. Data base system which maintains project query list, desktop list and status of multiple ongoing research projects
US5315646A (en) * 1990-12-18 1994-05-24 Bell Communications Research Systems and processes for providing multiple interfaces for telephone services
US5276679A (en) * 1992-02-12 1994-01-04 U.S. West Advanced Technologies, Inc. Method for maintaining channels and a subscriber station for use in an ISDN system
US5550968A (en) * 1994-04-12 1996-08-27 International Business Machines Corporation Method and system for providing access security to controls in a graphical user interface
US6026429A (en) * 1995-06-07 2000-02-15 America Online, Inc. Seamless integration of internet resources
US6345268B1 (en) * 1997-06-09 2002-02-05 Carlos De La Huerga Method and system for resolving temporal descriptors of data records in a computer system
US5953541A (en) 1997-01-24 1999-09-14 Tegic Communications, Inc. Disambiguating system for disambiguating ambiguous input sequences by displaying objects associated with the generated input sequences in the order of decreasing frequency of use
US5960085A (en) * 1997-04-14 1999-09-28 De La Huerga; Carlos Security badge for automated access control and secure data gathering
US20020004783A1 (en) 1997-11-12 2002-01-10 Cris T. Paltenghe Virtual wallet system
JP3648051B2 (en) * 1998-02-02 2005-05-18 富士通株式会社 Related information retrieval apparatus and program recording medium
US6212522B1 (en) 1998-05-15 2001-04-03 International Business Machines Corporation Searching and conditionally serving bookmark sets based on keywords
US6782430B1 (en) * 1998-06-05 2004-08-24 International Business Machines Corporation Invalid link recovery
US20010029582A1 (en) * 1999-05-17 2001-10-11 Goodman Daniel Isaac Method and system for copy protection of data content
US6661904B1 (en) * 1998-07-15 2003-12-09 Personalogo Method and system for automated electronic conveyance of hidden data
US7734541B2 (en) 1998-12-08 2010-06-08 Yodlee.Com, Inc. Interactive funds transfer interface
CN100334582C (en) * 1999-01-08 2007-08-29 国际商业机器公司 Method and apparatus for storing and searching data in hand-held device
US6237033B1 (en) 1999-01-13 2001-05-22 Pitney Bowes Inc. System for managing user-characterizing network protocol headers
US7149726B1 (en) * 1999-06-01 2006-12-12 Stamps.Com Online value bearing item printing
US7080070B1 (en) * 1999-07-02 2006-07-18 Amazon Technologies, Inc. System and methods for browsing a database of items and conducting associated transactions
US6738910B1 (en) * 1999-10-28 2004-05-18 International Business Machines Corporation Manual virtual private network internet snoop avoider
US6671818B1 (en) * 1999-11-22 2003-12-30 Accenture Llp Problem isolation through translating and filtering events into a standard object format in a network based supply chain
US6490575B1 (en) * 1999-12-06 2002-12-03 International Business Machines Corporation Distributed network search engine
US7167844B1 (en) * 1999-12-22 2007-01-23 Accenture Llp Electronic menu document creator in a virtual financial environment
US7089582B1 (en) * 2000-02-17 2006-08-08 International Business Machines Corporation Method and apparatus for identifying universal resource locator rewriting in a distributed data processing system
US7017109B1 (en) * 2000-02-18 2006-03-21 Hewlett-Packard Development Company, L.P. E-service to manage contact information and signature ECards
US7155419B2 (en) * 2000-04-20 2006-12-26 Agreenet Agreement management system and method
GB2364480B (en) * 2000-06-30 2004-07-14 Mitel Corp Method of using speech recognition to initiate a wireless application (WAP) session
AU2001272809A1 (en) 2000-07-25 2002-02-05 Cypus Communication terminal capable for searching internet domain name, system and method for searching internet domain name using the same
EP1178409A1 (en) 2000-08-01 2002-02-06 DR. Riccardo Genghini Studio Notarile Genghini Cookiemanager to control the exchange of cookies in an Internet client-server computersystem
US20020021311A1 (en) 2000-08-14 2002-02-21 Approximatch Ltd. Data entry using a reduced keyboard
WO2002035336A1 (en) 2000-10-27 2002-05-02 Qcode Information Technology Limited Text inputting system
US7032168B1 (en) * 2000-11-28 2006-04-18 Be Free, Inc. Method and apparatus for generating website links
US6983310B2 (en) * 2000-12-29 2006-01-03 International Business Machines Corporation System and method for providing search capabilties on a wireless device
US6810402B2 (en) 2001-05-15 2004-10-26 International Business Machines Corporation Method and computer program product for color coding search results
CN1321939A (en) * 2001-06-21 2001-11-14 成都力天网讯科技有限公司 Method for implementing information inquiry and management by using PDA and its system
US6732105B1 (en) * 2001-07-27 2004-05-04 Palmone, Inc. Secure authentication proxy architecture for a web-based wireless intranet application
JP2003065783A (en) * 2001-08-27 2003-03-05 Pioneer Electronic Corp Communication navigation system and method for the same, device for communication center for providing map information, communication navigation terminal and computer program
US6701851B2 (en) * 2002-03-19 2004-03-09 Zafar Y. Ibrahim Stand for reading materials and laptop computers
US7091851B2 (en) * 2002-07-02 2006-08-15 Tri-Sentinel, Inc. Geolocation system-enabled speaker-microphone accessory for radio communication devices
US20070016636A1 (en) * 2005-07-14 2007-01-18 Yahoo! Inc. Methods and systems for data transfer and notification mechanisms

Also Published As

Publication number Publication date
US8032612B2 (en) 2011-10-04
US20090164616A1 (en) 2009-06-25
CN1745383A (en) 2006-03-08
WO2004068256A3 (en) 2004-12-29
US20040153527A1 (en) 2004-08-05
EP1720110A1 (en) 2006-11-08
EP1588294A2 (en) 2005-10-26
US20060277274A1 (en) 2006-12-07
ATE537508T1 (en) 2011-12-15
CA2514216A1 (en) 2004-08-12
WO2004068256A2 (en) 2004-08-12
CN100444161C (en) 2008-12-17
US7310662B2 (en) 2007-12-18
CN101266615B (en) 2011-02-09
US7167905B2 (en) 2007-01-23
CN101266615A (en) 2008-09-17

Similar Documents

Publication Publication Date Title
US8032612B2 (en) Token-based web browsing with visual feedback of disclosure
US6842612B2 (en) Method of connecting network URL addresses through cellular network
KR100644399B1 (en) Method and system for supporting information access and record media thehefor
US8972856B2 (en) Document modification by a client-side application
US20110289015A1 (en) Mobile device recommendations
JP4483238B2 (en) Mobile terminal, mobile terminal function calling method and program thereof
WO2008065549A1 (en) Input prediction
US20180300058A1 (en) Supplementing a virtual input keyboard
US20090006342A1 (en) Method, Apparatus and Computer Program Product for Providing Internationalization of Content Tagging
KR20000030601A (en) Method of search for domain in internet
US7895337B2 (en) Systems and methods of generating a content aware interface
US7110790B2 (en) Quick access list for previously accessed network addresses
US20070094071A1 (en) Pushing content to browsers
JP2002259011A (en) Personal digital assistant and its screen updating program
US20030120779A1 (en) Method for performing a search, and computer program product and user interface for same
US20080189271A1 (en) Search system and search method
JP4455429B2 (en) Mobile communication terminal and server
JP2008242681A (en) Search service system, search server, search service method, and program for search service
JP2007011761A (en) Retrieval system and mobile communication terminal
KR100443774B1 (en) Multi-Language Image Keyboard Providing Method and Computer System thereof
KR102051507B1 (en) Method for providing web browser and terminal device using the same
JP2006107199A (en) Retrieval system
KR20010075818A (en) Method of searching a web domain
JP2017188021A (en) Job seeker support system
KR101182255B1 (en) Method for supporting information access and record media thehefor

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: 20050728

AK Designated contracting states

Kind code of ref document: A2

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

AX Request for extension of the european patent

Extension state: AL LT LV MK

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1085021

Country of ref document: HK

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

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 IT LI LU MC NL 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: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602004035657

Country of ref document: DE

Effective date: 20120209

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20111214

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: 20111214

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: 20120315

Ref country code: NL

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: 20111214

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: 20111214

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: 20111214

Ref country code: BE

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: 20111214

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

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: 20111214

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: 20111214

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: 20120314

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: 20111214

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120416

Ref country code: MC

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

Effective date: 20120131

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: 20111214

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: HK

Ref legal event code: WD

Ref document number: 1085021

Country of ref document: HK

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 537508

Country of ref document: AT

Kind code of ref document: T

Effective date: 20111214

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

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: LI

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

Effective date: 20120131

Ref country code: CH

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

Effective date: 20120131

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: 20111214

26N No opposition filed

Effective date: 20120917

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20111214

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602004035657

Country of ref document: DE

Effective date: 20120917

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: 20120130

Ref country code: AT

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: 20111214

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120325

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

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: 20111214

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: 20111214

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: 20120130

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: 20040130

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: FR

Payment date: 20150202

Year of fee payment: 12

Ref country code: GB

Payment date: 20150114

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: 20160108

Year of fee payment: 13

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

Effective date: 20160130

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20160930

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: 20160130

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: 20160201

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602004035657

Country of ref document: DE

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: 20170801