Search engine request method, product, and apparatus
Claim Score by NHIP
Abstract
An accessible URI may be generated in response to determining that an existing valid URI is inaccessible. When a valid URI is determined to be not accessible, then a valid URI may be generated to access content by extracting keywords from the non-query component URI (e.g., directory, domain, port, or fragment, etc.) of the inaccessible URI and using such keywords as a search request or as the query portion of the generated accessible URI.
Term
Term ended
Expired 22 August 2020, 6.1 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
35 claims: 5 independent, 30 dependent
- 1A method for generating newly created information comprising:a user intentionally submitting a request to locate a file that does not exist on a server, said request including a Uniform Resource Identifier (URI) having at least one of a scheme, one or more domains, port, path, one or more directory names, and one or more file names;receiving, at said server, said request to locate said file from said server;determining that said file can not be located on said server;extracting at least one keyword from said at least one of a scheme, one or more domains, port, path, one or more directory names, and one or more tile file names;generating and performing a search request having said at least one keyword to at least one Internet search engine provider to obtain at least one web page including said at least one keyword;and, dynamically generating and providing said newly created information to said user wherein said newly created information includes results of said search request from said Internet search engine provider.
- 10A method for presenting information, the method comprising:receiving a user request at a computing device, the user request comprising a Uniform Resource Identifier (URI) comprising at least one of a scheme, one or more domains, port, path, one or more directory names, or one or more file names;determining whether the user request corresponds to a valid existing resource available from the computing device;the computing device extracting at least one keyword from the at least one of a scheme, one or more domains, port, path, one or more directory names, or one or more file names in response to determining the user request does not correspond to a valid existing resource;the computing device generating a search request based on at least the at least one keyword to obtain an identification of at least one resource corresponding to the at least one keyword;and the computing device communicating the identification of the at least one resource corresponding to the at least one keyword.
- 20A non-transitory tangible computer readable medium having instructions stored thereon, the instructions comprising:instructions for receiving a user request to locate a file, the user request including a Uniform Resource Identifier (URI) having at least one of a scheme, one or more domains, port, path, one or more directory names, or one or more file names;instructions for determining that the file cannot be located on a server;instructions for extracting at least one keyword from the at least one of a scheme, one or more domains, port, path, one or more directory names, or one or more file names;instructions for generating a search request having the at least one keyword to obtain at least one web page;and, instructions for dynamically generating and providing newly created information wherein the newly created information comprises, at least in part, information that leads to the at least one web page.
- 21A non-transitory tangible computer readable medium having instructions stored thereon that cause a computing device to perform operations comprising:determining whether a user request comprising a Uniform Resource Identifier (URI) comprising at least one of a scheme, domain, port, path, directory name, or file name corresponds to an existing resource;extracting at least one keyword from the at least one of a scheme, domain, port, path, directory name, or file name in response to determining that the user request does not correspond to an existing resource;generating a query based on at least the at least one keyword to obtain an identification of at least one resource corresponding to the at least one keyword;and communicating the identification of the at least one resource corresponding to the at least one keyword.
- 26Broadest claimClaim Score 57, broad(NHIP)A system, comprising:at least one interface adapted to receive a user request, the user request comprising a Uniform Resource Identifier (URI) comprising at least one of a scheme, domain, port, path, directory name, or file name;and at least one computing device adapted to: determine whether the user request corresponds to an available resource;extract at least one keyword from the at least one of a scheme, domain, port, path, directory name, or file name in response to determining that the request does not correspond to an available resource;generate a query based on at least the at least one keyword to obtain an identification of at least one resource corresponding to the at least one keyword;and communicate through the at least one interface, at least one of the query or the identification of the at least one resource corresponding to the at least one keyword.
Independent claims5
61 paragraphs in 6 sections, as filed
OTHER APPLICATIONS
0001This application claims the benefit of the following patent applications, which are hereby incorporatedincorporates the following applications by reference: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0002">1.this application is a continuation-in-part of U.S. patent application Ser. No. 09/532,500 filed Mar. 21, 2000, by Schneider, entitled “Fictitious domain name method, product, and apparatus”, which claims the benefit ofnow U.S. Pat. No. 7,136,932; this application is also a continuation-in-part of U.S. patent application Ser. No. 09/525,350 filed Mar. 15, 2000, by Schneider, entitled “Method for integrating domain name registration with domain name resolution”and, now U.S. Pat. No. 6,338,082; this application also claims the benefit of U.S. Provisional Application Ser. No. 60/143,859 filed Jul. 15, 1999, by Schneider entitled “Method and apparatus for generation, registration, resolution, and emulation of name space”, now abandoned,; this application also claims the benefit of U.S. Provisional Application Ser. No. 60/135,751 filed May 25, 1999, by Schneider entitled “Method and system for name space resolution”, now abandoned and; this application also claims the benefit of U.S. Provisional Application Ser. No. 60/125,531 filed Mar. 22, 1999, by Schneider entitled “Method and system for the emulation of name space”, now abandoned.; </li><li id="ul0002-0002" num="0003">2.this application also claims the benefit of U.S. Provisional Application Ser. No. 60/153,594 filed Sep. 13, 1999, by Schneider entitled “Method and apparatus for using a portion of a URI to select and display advertising.”; </li><li id="ul0002-0003" num="0004">3.this application also claims the benefit of U.S. Provisional Application Ser. No. 60/152,015 filed Sep. 1, 1999, by Schneider, et al., entitled “Method and apparatus for using a portion of a URI as a search request.”</li></ul></li></ul>
FIELD OF THE INVENTION
0005This invention generally relates to search requests, and more specifically relates to a method and apparatus for using a non-query URI component as a search request.
BACKGROUND OF THE INVENTION
0006The Internet is a vast computer network consisting of many smaller networks that span the world. A network provides a distributed communicating system of computers that are interconnected by various electronic communication links and computer software protocols. Because of the Internet's distributed and open network architecture, it is possible to transfer data from one computer to any other computer worldwide. In 1991, the World-Wide-Web (WWW or Web) revolutionized the way information is managed and distributed.
0007The Web is based on the concept of hypertext and a transfer method known as Hypertext Transfer Protocol (HTTP) which is designed to run primarily over a Transmission Control Protocol/Internet Protocol (TCP/IP) connection that employs a standard Internet setup. A server-computer may issue the data and a client computer displays or processes it. TCP may then convert messages into streams of packets at the source, then reassemble them back into messages at the destination. Internet Protocol (IP) handles addressing, seeing to it that packets are routed across multiple nodes and even across multiple networks with multiple standards. HTTP protocol permits client systems connected to the Internet to access independent and geographically scattered server systems also connected to the Internet.
0008Client side browsers, such as Netscape Navigator and/or Microsoft Internet Explorer (MSIE) provide graphical user interface (GUI) based client applications that implement the client side portion of the HTTP protocol. One format for information transfer is to create documents using Hypertext Markup Language (HTML). HTML pages are made up of standard text as well as formatting codes that indicate how the page should be displayed. The client side browser reads these codes in order to display the page. A web page may be static and requires no variables to display information or link to other predetermined web pages. A web page is dynamic when arguments are passed which are either hidden in the web page or entered from a client browser to supply the necessary inputs displayed on the web page. Common Gateway Interface (CGI) is a standard for running external programs from a web server. CGI specifies how to pass arguments to the executing program as part of the HTTP server request. Commonly, a CGI script may take the name and value arguments from an input form of a first web page which may be used as a query to access a database server and generate an HTML web page with customized data results as output that is passed back to the client browser for display.
0009The Web is a means of accessing information on the Internet that allows a user to “surf the web” and navigate the Internet resources intuitively, without technical knowledge. The Web dispenses with command-line utilities, which typically require a user to transmit sets of commands to communicate with an Internet server. Instead, the Web is made up of millions of interconnected web pages, or documents, which may be displayed on a computer monitor. Hosts running special servers provide the Web pages. Software that runs these Web servers is relatively simple and is available on a wide range of computer platforms including PC's.
0010A Uniform Resource Identifier (URI) is a compact string of characters for identifying an abstract or physical resource. URIs, is the generic set of all names and addresses that refer to objects on the Internet. URLs that refer to objects accessed with existing protocols are known as URLs. A URL is the address of a file accessible on the Internet. The URL contains the name of the protocol required to access the resource, a domain name, Fully Qualified Domain Name (FQDN), or IP address that identifies a specific computer on the Internet, and a hierarchical description of a file location on the computer. In addition, the last (optional) part of the URL may be a “?” followed by a query string having name/value pairs for parameters (e.g. “?size=small&quantity=3”) or a “#” followed by a fragment identifier indicating a particular position within the specified document.
0011The URI “http://www.example.com:80/index.html#appendix” is the concatenation of several components where “http:” is the scheme or protocol, “//www.example.com” is the FQDN having “www” as the host of the domain name “example.com”, “:80” is the port connection for the HTTP server request, “index.html” is the filename located on the server, “#appendix” is the identifier to display a fragment of the HTML file called “index”. The URL “http://www.example.com” also retrieves an HTML file called “index” on a HTTP server called “example.com”. By default, when either a port or filename is omitted upon accessing a HTTP server via a URL, the client browser interprets the request by connecting via port 80, and retrieving the HTML file called “index”.
0012A domain name consists of two parts: a host and a domain. Technically, the letters to the right of the “dot” (e.g., tut.net) are referred to as Top Level Domains (TLDs), while hosts, computers with assigned IP addresses that are listed in specific TLD registries are known as second-level domains (SLDs). For the domain name “tut.net”, “.net” is the TLD, and “tut” is the SLD. Domain name space is the ordered hierarchical set of all possible domain names either in use or to be used for locating an IP address on the Internet. TLDs are known as top-level domains because they comprise the highest-order name space available on the Internet. Second-level domains, as well as third-level domains (3LDs) such as “king.tut.net”, are subsidiary to TLDs in the hierarchy of the Internet's DNS.
0013The main use of a web browser location field is for locating URLs to access resources. Entering a URL in the location field of a web browser serves as a means to access that URL. Because the function of the location field is so critical for accessing resources, the design of such location fields have rivaled much competition and innovation between existing web browser products. Improvements to better track and organize sites of URLs that users have visited such as Bookmark folders, URL history, and the personal toolbar are all examples of functionality designed to help users navigate.
0014A more recent feature called Smart Browsing is integrated into Netscape Navigator that uses Internet Keywords so users can streamline the use of URLs and get fast access to web sites using the browser's location field. Any single or multiword strings typed into the browser's location field that does not include a “.” are sent via HTTP to a server at “netscape.com”. The keyword server pulls the string and compares it to several separate lists of keyword-URL pairs. If the keyword system finds a match, it redirects the user's browser to the URL of the keyword-URL pair. Failing a match against the lists, the user's browser is redirected to a Netscape Search page with the typed string as the search query.
0015U.S. Provisional Application Ser. No. 60/143,859 filed Jul. 15, 1999, by Schneider entitled “Method and apparatus for generation, registration, resolution, and emulation of name space”, now abandoned, uses a domain name having a top level domain alias (TLDA) to simultaneously access and search a given resource demonstrating the combination of both resolution and search services. For instance, when input is received and processed such as “http://example.44106”, steps are performed to determine that “0.44106” is not a resolvable TLD and may be processed instead as a search term. Steps may then be performed to translate input into a valid URI such as “http://example.com/weather.cgi?zip=44106”. When the URI is accessed, a CGI script called “weather” is executed passing the value “44106” for the name “zip”, which in this case represents a zip code. By so doing a fictitious name is used to simultaneously access both a resource and search request.
0016This clearly demonstrates the need for methods of encouraging the creative use of URIs to access resources. Accordingly, in light of the above, there is a strong need in the art for a system and method to improve how resources and content may be accessed.
SUMMARY OF THE INVENTION
0017Briefly, the present invention allows URI components to be used as a search term in a query or search request. The invention allows for the non-query portion of a first URI to be used in the query portion of a second URI to generate dynamic content. The present invention allows for a shorter URI to be created on the fly in real-time that accesses content of a longer URI. The invention allows the user to combine Boolean logic with valid URI notation to generate a search request from the URI or vice-versa.
0018In general, in accordance with the present invention a method for locating a network resource from a first identifier includes the steps of determining whether the first identifier is accessible, accessing the first identifier in response to determining that the first identifier is accessible, generating a second identifier in response to determining that the first identifier is not accessible, wherein said second identifier is generated by retrieving information from one of a user modifiable configuration settings, template, GO LIST, name translation table, and registry, and accessing said second identifier in response to generating said second identifier.
0019In accordance with another aspect of the present invention a method for locating a network resource from a first identifier having a valid accessible first URI includes the steps of parsing at least one non-query URI component from the first URI, generating a valid accessible second URI having a query component that corresponds to the first URI, and simultaneously accessing both the first URI and said second URI.
0020In accordance with yet another aspect of the present invention a method for locating a network resource from a first identifier having a valid first URI includes the steps of determining whether the first URI is accessible, accessing the first URI in response to determining that the first URI is accessible, parsing at least one non-query URI component from the first URI in response to determining that the first URI is not accessible, generating a valid second URI having a query component that corresponds to the first URI, and accessing said second URI.
0021In accordance with yet additional aspects of the present invention, an apparatus which implements substantially the same functionality in substantially the same manner as the methods described above is provided.
0022In accordance with other additional aspects of the present invention, a computer-readable medium that includes computer-executable instructions may be used to perform substantially the same methods as those described above is provided.
0023The foregoing and other features of the invention are hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail one or more illustrative aspects of the invention, such being indicative, however, of but one or a few of the various ways in which the principles of the invention may be employed.
BRIEF DESCRIPTION OF THE DRAWINGS
0024<figref idref="DRAWINGS">FIG. 1</figref>a is a block diagram of an exemplary distributed computer system in accordance with the present invention.
0025<figref idref="DRAWINGS">FIG. 1</figref>b is a block diagram illustrating exemplary information records stored in memory in accordance with the present invention.
0026<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart illustrating the steps performed by a prior art system for accessing a URI.
0027<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart illustrating the steps performed for generating a valid URI in accordance with the present invention.
0028<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating the steps performed for generating a valid URI in response to determining that an existing valid URI is inaccessible in accordance with the present invention.
0029<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating the steps performed for generating a frame having an accessible URI in accordance with the present invention.
0030<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating the steps performed for creating files or directories as needed to form an accessible URI in accordance with the present invention.
0031<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating the steps performed for extracting a domain to be used as a search request in accordance with the present invention.
0032<figref idref="DRAWINGS">FIG. 8</figref> is a diagram depicting how results may be displayed in a web browser in accordance with the present invention.
DETAILED DESCRIPTION OF THE INVENTION
0033The present invention will now be described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout.
0034Turning first to the nomenclature of the specification, the detailed description that follows represents processes and symbolic representations of operations by conventional computer components, including a local processing unit, memory storage devices for the local processing unit, display devices, and input devices. Furthermore, these processes and operations may utilize conventional computer components in a heterogeneous distributed computing environment, including remote file servers, computer servers, and memory storage devices. These distributed computing components may be accessible to the local processing unit by a communication network.
0035The processes and operations performed by the computer include the manipulation of data bits by a local processing unit and/or remote server and the maintenance of these bits within data structures resident in one or more of the local or remote memory storage devices. These data structures impose a physical organization upon the collection of data bits stored within a memory storage device and represent electromagnetic spectrum elements.
0036A process may generally be defined as being a sequence of computer-executed steps leading to a desired result. These steps generally require physical manipulations of physical quantities. Usually, though not necessarily, these quantities may take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, compared, or otherwise manipulated. It is conventional for those skilled in the art to refer to these signals as bits or bytes (when they have binary logic levels), pixel values, works, values, elements, symbols, characters, terms, numbers, points, records, objects, images, files, directories, subdirectories, or the like. It should be kept in mind, however, that these and similar terms should be associated with appropriate physical quantities for computer operations, and that these terms are merely conventional labels applied to physical quantities that exist within and during operation of the computer.
0037It should also be understood that manipulations within the computer are often referred to in terms such as adding, comparing, moving, positioning, placing, illuminating, removing, altering, etc., which are often associated with manual operations performed by a human operator. The operations described herein are machine operations performed in conjunction with various input provided by a human operator or user that interacts with the computer. The machines used for performing the operation of the present invention include local or remote general-purpose digital computers or other similar computing devices.
0038In addition, it should be understood that the programs, processes, methods, etc. described herein are not related or limited to any particular computer or apparatus nor are they related or limited to any particular communication network architecture. Rather, various types of general-purpose machines may be used with program modules constructed in accordance with the teachings described herein. Similarly, it may prove advantageous to construct a specialized apparatus to perform the method steps described herein by way of dedicated computer systems in a specific network architecture with hard-wired logic or programs stored in nonvolatile memory, such as read only memory.
0039<figref idref="DRAWINGS">FIG. 1</figref>a illustrates an exemplary system for providing a distributed computer system <b>100</b> in accordance with one aspect of the present invention and may include client computers or any network access apparatus <b>110</b> connected to server computers <b>120</b> via a network <b>130</b>. The network <b>130</b> may use Internet communications protocols (IP) to allow clients <b>110</b> to communicate with servers <b>120</b>. The network access apparatus <b>110</b> may include a modem or like transceiver to communicate with the electronic network <b>130</b>. The modem may communicate with the electronic network <b>130</b> via a line <b>116</b> such as a telephone line, an ISDN line, a coaxial line, a cable television line, a fiber optic line, or a computer network line. Alternatively, the modem may wirelessly communicate with the electronic network <b>130</b>. The electronic network <b>130</b> may provide an on-line service, an Internet service provider, a local area network service, a wide area network service, a cable television service, a wireless data service, an intranet, a satellite service, or the like.
0040The client computers <b>110</b> may be any network access apparatus including hand held devices, palmtop computers, personal digital assistants (PDAs), notebook, laptop, portable computers, desktop PCs, workstations, and/or larger/smaller computer systems. It is noted that the network access apparatus <b>110</b> may have a variety of forms, including but not limited to, a general purpose computer, a network computer, an internet television, a set top box, a web-enabled telephone, an internet appliance, a portable wireless device, a game player, a video recorder, and/or an audio component, for example.
0041Each client <b>110</b> typically includes one or more processors <b>166</b>, memories <b>168</b>, and input/output devices <b>170</b>. An input device may be any suitable device for the user to give input to client computer system <b>110</b>, for example: a keyboard, a 10-key pad, a telephone key pad, a light pen or any pen pointing device, a touchscreen, a button, a dial, a joystick, a steering wheel, a foot pedal, a mouse, a trackball, an optical or magnetic recognition unit such as a bar code or magnetic swipe reader, a voice or speech recognition unit, a remote control attached via cable or wireless link to a game set, television, and/or cable box. A data glove, an eye-tracking device, or any MIDI device may also be used. A display device may be any suitable output device, such as a display screen, text-to-speech converter, printer, plotter, fax, television set, or audio player. Although the input device is typically separate from the display device, they may be combined; for example: a display with an integrated touchscreen, a display with an integrated keyboard, or a speech-recognition unit combined with a text-to-speech converter.
0042The servers <b>120</b> may be similarly configured. However, in many instances server sites <b>120</b> include many computers, perhaps connected by a separate private network. In fact, the network <b>130</b> may include hundreds of thousands of individual networks of computers. Although client computers <b>110</b> are shown separate from the server computers <b>120</b>, it is understood that a single computer might perform the client and server roles. Those skilled in the art will appreciate that the computer environment <b>100</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>a is intended to be merely illustrative. The present invention may also be practiced in other computing environments. For example, the present invention may be practiced in multiple processor environments wherein the client computer includes multiple processors. Moreover, the client computer need not include all of the input/output devices as discussed above and may also include additional devices. Those skilled in the art will appreciate that the present invention may also be practiced via Intranets and more generally in distributed environments in which a client computer requests resources from a server computer.
0043During operation of the distributed system <b>100</b>, users of the clients <b>110</b> may desire to access information records <b>122</b> stored by the servers <b>120</b> while utilizing, for example, the Web. Furthermore, such server systems <b>120</b> may also include one or more search engines having one or more databases <b>124</b>. The records of information <b>122</b> may be in the form of Web pages <b>150</b>. The pages <b>150</b> may be data records including as content plain textual information, or more complex digitally encoded multimedia content, such as software programs, graphics, audio signals, videos, and so forth. It should be understood that although this description focuses on locating information on the World-Wide-Web, the system may also be used for locating information via other wide or local area networks (WANs and LANs), or information stored in a single computer using other communications protocols.
0044The clients <b>110</b> may execute Web browser programs <b>112</b>, such as Netscape Navigator or MSIE to locate the pages or records <b>150</b>. The browser programs <b>112</b> enable users to enter addresses of specific Web pages <b>150</b> to be retrieved. Typically, the address of a Web page is specified as a URI or more specifically as a URL. In addition, when a page has been retrieved, the browser programs <b>112</b> may provide access to other pages or records by “clicking” on hyperlinks (or links) to previously retrieved Web pages. Such links may provide an automated way to enter the URL of another page, and to retrieve that page.
0045<figref idref="DRAWINGS">FIG. 1</figref>b illustrates a block diagram of a processor <b>166</b> coupled to a storage device such as memory <b>168</b> and to input/output devices <b>170</b> in a client <b>110</b> and/or server <b>120</b> computing system. Stored in memory <b>168</b> may be information records <b>122</b> having any combination of exemplary content such as lists, files, and databases. Such records may include for example: user modifiable configuration settings <b>174</b>, identifier generation routines <b>176</b>, FDN registry <b>178</b>, TLD cache <b>180</b>, prefix database <b>182</b>, Templates <b>184</b>, GO List <b>186</b>, name translation table <b>188</b>, and advertising cache <b>190</b>. These information records may be further introduced and discussed in more detail throughout the disclosure of this invention.
0046<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart illustrating the steps performed by a prior art system for locating a network resource from an identifier by accessing a URI. A device such as a network access apparatus <b>110</b>, servlet, applet, stand-alone executable program, or user interface element such as a text box object, command line, speech to text interface, location field <b>814</b> of a web browser <b>112</b>, may receive and parse input such as text or voice in step <b>210</b>. It then may be determined in step <b>215</b> whether the input <b>210</b> is a URI. If the input is a URI, then an attempt may be made in step <b>220</b> to access the URI. The URI may be accessed when it is determined in step <b>222</b> that the URI is accessible. If the input is not a URI, then it may be determined in step <b>225</b> whether a URI can be generated from the input (e.g., if a scheme is missing the prefix “http://” or another scheme prefix may be concatenated to input). If so, then a URI is generated <b>230</b> and an attempt may be made in step <b>220</b> to access the URI. If the URI can not be generated or accessed, then a message indicating that the URI can not be generated or accessed may be displayed in step <b>235</b>.
0047<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart illustrating the steps performed for generating a valid URI. When it is determined in step <b>225</b> that a URI can not be generated from the input <b>210</b> in accordance with methods known to one of ordinary skill in the art, then it may be determined in step <b>310</b> whether it is configured to determine whether other methods may be applied to access a valid URI corresponding to input. If configuration <b>174</b> is not enabled, then a message indicating that the URI can not be generated may be displayed in step <b>235</b>. However, when configuration is enabled, then at least one other method may be applied in step <b>315</b> in sequence or parallel including methods explained in U.S. patent application Ser. No. 09/532,500 filed Mar. 21, 2000, by Schneider, entitled “Fictitious domain name method, product, and apparatus” such as retrieving information from user modifiable configuration settings <b>174</b>, template <b>184</b>, GO LIST <b>186</b>, name translation table <b>188</b>, and registry <b>178</b> (e.g., processing a FDN, processing a TLDA as a search request, and multiple accessibility from a plurality of generated URIs, etc.).
0048<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating the steps performed for generating a valid URI in response to determining that an existing valid URI is inaccessible. When a valid URI is determined in step <b>222</b> to be not accessible, then a valid URI may be generated in step <b>410</b> to access content by extracting keywords from the non-query component URI (e.g., directory, domain, port, or fragment, etc.) of the inaccessible URI and using such keywords as a search request or as the query portion of the generated valid URI. After valid URI generation in step <b>410</b> an attempt may be made in step <b>220</b> to access the URI.
0049In effect, the non-query portion of a first URI may be used in the query portion of a second URI to generate dynamic content. Validity of URI syntax is explained in T. Berners-Lee, “Informational RFC (Request for Comment) <b>1630</b>: Universal Resource Identifiers in WWW—A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web”, Internet Engineering Task Force (IETF), June 1994, “http://www.faqs.org/rfcs/rfc1630.html”, which is herein incorporated by reference.
0050Typically, when a HTTP request is submitted to access a URI that does not exist, an error <b>404</b> code is returned from the requested web server, and in turn, a script may be executed to redirect and display a gen-eric web page informing the user of the error <b>404</b> code. A modification may be made to the script to generate an accessible URI by creating the appropriate directories or files on the web server in response to an error <b>404</b> code (or any other applicable error code from the 300 series, 400 series, or 500 series) such that when the HTTP request is resubmitted the URI exists and is accessible.
0051<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating the steps performed for generating a frame having an accessible URI. After valid URI generation in step <b>410</b>, a script may be executed in step <b>510</b> to create a second accessible URI by adding the appropriate directories and files. The content of the newly created file may include at least one frame that displays the content of the valid generated URI. After the second accessible URI is created, an attempt may be made in step <b>220</b> to access the second URI.
0052<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating the steps performed for creating files or directories as needed to form an accessible URI. When it is determined in step <b>222</b> that a valid URI is not accessible it may then be further determined in step <b>610</b> whether the URI has the minimum form of “scheme://SLD.TLD/FLD” where the domain name is “SLD.TLD” and the path is “/FLD”, which in this case represents a first level directory (FLD). If the URI is not of the minimum form then steps (such as <b>410</b> and/or <b>510</b>) may be performed. When it is determined in step <b>610</b> that the URI is of the minimum form, then it may be determined in step <b>615</b> whether the FLD exists. If the FLD exists, then it may be further determined in step <b>620</b> whether a file exists within the FLD. If a file exists, then it may be determined in step <b>625</b> whether the content of the file requires modification (e.g., META tag for purpose of URI redirection). If modification is needed then the content of the file may be modified in step <b>630</b> as necessary. If the FLD does not exist, then a FLD may be created in step <b>635</b>. When the FLD is created or when the FLD exists but a file within the FLD does not exist, then a file within the FLD may be created in step <b>640</b>. When it is determined in step <b>620</b> that the file already exists and does not need modification in step <b>625</b> or the file is created in step <b>640</b> or the existing file is modified in step <b>635</b> then a second URI may be generated in step <b>645</b> including the FLD as part of a search request. After the accessible URI is created, an attempt may be made in step <b>220</b> to access the URI.
0053For example, a device receives the input “http://update.to/news”. When it is determined that the input is a valid URL (URL is a subset of a URI), a HTTP GET request is submitted to retrieve its content. A “404 error code” is received in response to the request indicating that no such URL exists. As practiced by those skilled in the art, the “404 error code” is commonly redirected to display a gen-eric informative page alerting the user that no such URL exists. Advantage may be taken by modifying the redirect script.
0054The modified script may be executed upon the “404 error code” and determines that a “/news” directory does not exist and is created. Furthermore, an “index.htm” is created in the “news” directory serving as a default file for the URL listed above. The content of the file includes a <META> tag which may be used to redirect the URL to another URL such as “http://update.to/cgi-bin/update.cgi?search=news” which serves as a dynamic output.
0055For instance, the input “update.to/news” becomes equivalent to “http://update.to/news/index.htm” and includes within the “index.htm” file the following <META> tag: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0056"><META HTTP-EQUIV=Refresh CONTENT=“5; URL=http://update.to/cgi-bin/update.cgi?search=news”> <br /> which communicates to a device that interprets HTML to load the URL “hftp://update.to/cgi-bin/update.cgi?search=news” 5 seconds after the current document “http://update.to/news/index.htm” has finished loading. Advertising may be displayed by selecting an ad from an advertising cache <b>190</b> that corresponds to any URI components or the like before automatic URI redirection. Advertisement selection is explained in U.S. Provisional Application Ser. No. 60/153,594 filed Sep. 13, 1999, by Schneider entitled “Method and apparatus for using a portion of a URI to select and display advertising.” In another example, the content of the file may include a <FRAME> tag, which may be used to access content from “http://update.to/cgi-bin/update.cgi?search=news”. </li></ul></li></ul>
0057In effect, shorter URLs may be generated in real time or on-the-fly when necessary and used as a substitute or proxy for longer URLs. Though any filename may be used, it is a preferred aspect to use “index.htm” as a frame or redirect so the proxy URL is even shorter in string length. A shorter URL makes it easier for a user to remember the URL for future use. The invention is not limited to using only a FLD as a search request. Any directory or combination of directory levels may be either generated on the fly or used as a search request. In addition to using the directory portion of a URI as a search request, a domain (e.g., SLD) or any combination of domain levels may in turn be used to generate a query as well. For example, a subdomain may be generated to create the FQDN “news.update.to” having the minimum form of “scheme://3LD.SLD.TLD”, which may be used to access content from “http://update.to/cgi-bin/update.cgi?search=news”.
0058Analysis from major online search engines show that more than 90% of all search requests include three keywords or less. For instance, the search request “coffee and cream and sugar” can yield “http://example.com/coffee/cream/sugar/index.htm”. In turn, the input “example.com/coffee/cream/sugar” can generate search results thereby combining the step of searching by entering in a web address or URI to search. Boolean logic can be applied to extend variations for simple search requests. For example, the search request “coffee or cream or sugar” yields “http://example.com/coffee.cream.sugar/index.htm” whereas the search request “coffee or cream and sugar” yields “http://example.com/coffee.cream/sugar/index.htm”. In effect, URI notation can be used a system to generate a Boolean search request from the URI or vice-versa.
0059<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating the steps performed for extracting a domain to be used as a search request. When the input <b>210</b> is a valid <b>215</b> URI or a valid URI is generated in step <b>230</b> and the configuration settings <b>174</b> indicate that domain identifier extraction may be used (e.g., SLD) then a script may be executed to extract in step <b>710</b> the SLD from the valid URI (<b>215</b>, <b>230</b>) and a second URI may be generated in step <b>715</b> by using the SLD as part of a search request. The script generates a web page having two frames. The first frame links to the valid URI and the second frame links to the second URI which displays content when accessed relating to the use of SLD as a keyword in a search request.
0060<figref idref="DRAWINGS">FIG. 8</figref> is a diagram depicting how results may be displayed in a web browser. A client <b>110</b> web browser <b>112</b> having a web page <b>810</b> is used to connect to a server <b>120</b> via the Internet <b>130</b> that runs a CGI script <b>812</b>. The location field of the web browser <b>112</b> is suppressed and the web page <b>810</b> displays at least two frames. The first frame is the web based location field <b>814</b> and the second frame <b>816</b> is used to display the contents <b>150</b> of a web address. An input device (e.g., keyboard, mouse, pen light, touch screen, or microphone, etc.) of a client computer or network access apparatus <b>110</b> is used to receive a web address as input either directly from a hyperlink (not shown) in the web page <b>810</b>, or from the location field <b>814</b> of the web page <b>810</b>. A URL GET request is generated from the input and the browser <b>112</b> forwards the request to a server <b>120</b>, which processes the request by executing a CGI script <b>812</b> to determine accessibility <b>204</b>. An accessible URI <b>206</b> may be generated and the requested page <b>150</b> is sent to the browser <b>112</b>. The content <b>150</b> of the URI may be displayed (as discussed in <figref idref="DRAWINGS">FIG. 6</figref> with a specific example) in the second frame <b>816</b> of the web page <b>810</b>. The location field <b>814</b> of the first frame may either persist by displaying the input or is cleared out for entry of another web address.
0061Another web page <b>810</b>′ (as discussed in <figref idref="DRAWINGS">FIG. 7</figref>) having a location field that is not suppressed may be displayed by using a different CGI script <b>812</b>. A URL GET request may be generated from the input and the browser <b>112</b> forwards the request to a server <b>120</b>, which processes the request by executing a CGI script <b>812</b> to determine accessibility. An accessible URI may be generated and the requested page <b>150</b> is sent to the browser <b>112</b>. The content <b>150</b> of the URI may be displayed in a first frame <b>818</b> of the web page <b>810</b>′ whereas the content of the second frame <b>820</b> may be dynamically generated by corresponding the extracted SLD from the URI as a search term in a second URI. By using the steps illustrated in <figref idref="DRAWINGS">FIG. 7</figref>, when a first URI “http://www.example.com” is received as input, a script extracts “example” from the URI and generates a second URI “http://search.yahoo.com/bin/search?p=example”. Both the first URI and second URI are generated as frames and displayed as a web page <b>810</b>′.
0062Though the above aspects demonstrate how URIs may be accessed based upon a web-based version of a location field, similar teachings may be applied to those skilled in the art by providing a user interface element such as a text box object as input. The text box object may be located anywhere and on any web page including a text box that may be embedded or displayed as part of an on-line advertisement. The text box object may be used in a stand-alone application or stored on magnetic and/or optical media that may be non-volatile, writable, removable, or portable. The text box object may be incorporated as an applet or servlet and embedded in other applications. The text box may be integrated in the task bar or any part of the GUI's OS, or the OS bypassed and a user interface element overlaid as a graphic on a display device based on modifications to a video card and/or it's associated firmware or software drivers. A command line text box may be further overlaid as an interactive object in other embodiments such as Internet television, cable television, digital television, or interactive television through an Internet appliance or set top box.
0063Those skilled in the art may make and use software program that functions as a browser plug-in. Such a program may be downloaded and installed for integration into the command line of a device or location field <b>154</b> of a browser program <b>112</b>. Modifying the source code of the browser program <b>112</b> itself may be more desirable, in effect, enabling tens of millions of users to take advantage of more creative ways to use input as a means to access a valid URI.
0064Although the invention has been shown and described with respect to a certain preferred aspect or aspects, it is obvious that equivalent alterations and modifications will occur to others skilled in the art upon the reading and understanding of this specification and the annexed drawings. In particular regard to the various functions performed by the above described items referred to by numerals (components, assemblies, devices, compositions, etc.), the terms (including a reference to a “means”) used to describe such items are intended to correspond, unless otherwise indicated, to any item which performs the specified function of the described item (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary aspect or aspects of the invention. In addition, while a particular feature of the invention may have been described above with respect to only one of several illustrated aspects, such feature may be combined with one or more other features of the other aspects, as may be desired and advantageous for any given or particular application.
0065The description herein with reference to the figures will be understood to describe the present invention in sufficient detail to enable one skilled in the art to utilize the present invention in a variety of applications and devices. It will be readily apparent that various changes and modifications could be made therein without departing from the spirit and scope of the invention as defined in the following claims.
Contents6
Every citation, both waysCites: the store holds 104 of 105
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9026522B2 | Cited by | United States of America | Applicant |
| US12058099B1 | Cited by | United States of America | Applicant |
| US8874790B2 | Cited by | United States of America | Applicant |
| US9715512B2 | Cited by | United States of America | Applicant |
| US11470039B2 | Cited by | United States of America | Applicant |
| US9552281B2 | Cited by | United States of America | Applicant |
| US11985105B2 | Cited by | United States of America | Applicant |
| US9535971B2 | Cited by | United States of America | Applicant |
| US9455880B2 | Cited by | United States of America | Applicant |
| US11095604B1 | Cited by | United States of America | Applicant |
| US11468529B2 | Cited by | United States of America | Applicant |
| US10560339B2 | Cited by | United States of America | Applicant |
| US10819697B1 | Cited by | United States of America | Applicant |
| US9015670B2 | Cited by | United States of America | Applicant |
| US2011060950A1 | Cited by | United States of America | Pre-grant |
| US8904519B2 | Cited by | United States of America | Applicant |
| US10565666B2 | Cited by | United States of America | Applicant |
| US8990356B2 | Cited by | United States of America | Applicant |
| US11700230B1 | Cited by | United States of America | Applicant |
| US8849849B2 | Cited by | United States of America | Applicant |
| US10182032B2 | Cited by | United States of America | Applicant |
| US9912543B2 | Cited by | United States of America | Applicant |
| US9065855B2 | Cited by | United States of America | Applicant |
| US9742730B2 | Cited by | United States of America | Applicant |
| US2010325723A1 | Cited by | United States of America | Pre-grant |
| US8838531B2 | Cited by | United States of America | Applicant |
| US10061785B2 | Cited by | United States of America | Applicant |
| US9172673B2 | Cited by | United States of America | Applicant |
| US9202079B2 | Cited by | United States of America | Applicant |
| US10270755B2 | Cited by | United States of America | Applicant |
| US9218335B2 | Cited by | United States of America | Applicant |
| US9384097B2 | Cited by | United States of America | Applicant |
| US10346627B2 | Cited by | United States of America | Applicant |
| US11016950B2 | Cited by | United States of America | Applicant |
| US2011016022A1 | Cited by | United States of America | Pre-grant |
| US10565394B2 | Cited by | United States of America | Applicant |
| US11792079B2 | Cited by | United States of America | Applicant |
| US9363288B2 | Cited by | United States of America | Applicant |
| US11882109B2 | Cited by | United States of America | Applicant |
| US9785629B2 | Cited by | United States of America | Applicant |
| US9866536B2 | Cited by | United States of America | Applicant |
| US9613146B2 | Cited by | United States of America | Applicant |
| US10621054B2 | Cited by | United States of America | Applicant |
| US2002156800A1 | Cites | United States of America | Search report |
| US4155042A | Cites | United States of America | Applicant |
| US4190800A | Cites | United States of America | Applicant |
| US4196310A | Cites | United States of America | Applicant |
| US4390876A | Cites | United States of America | Applicant |
| US4486853A | Cites | United States of America | Applicant |
| US4754326A | Cites | United States of America | Applicant |
| US4811382A | Cites | United States of America | Applicant |
| US4823265A | Cites | United States of America | Applicant |
| US4903206A | Cites | United States of America | Applicant |
| US4956771A | Cites | United States of America | Applicant |
| US4956875A | Cites | United States of America | Applicant |
| US5109486A | Cites | United States of America | Applicant |
| US5155837A | Cites | United States of America | Applicant |
| US5155847A | Cites | United States of America | Applicant |
| US5175681A | Cites | United States of America | Applicant |
| US5231570A | Cites | United States of America | Applicant |
| US5249230A | Cites | United States of America | Applicant |
| US5249275A | Cites | United States of America | Applicant |
| US5319699A | Cites | United States of America | Applicant |
| US5321740A | Cites | United States of America | Applicant |
| US5386369A | Cites | United States of America | Applicant |
| US5402490A | Cites | United States of America | Applicant |
| US5404231A | Cites | United States of America | Applicant |
| US5404505A | Cites | United States of America | Applicant |
| US5418951A | Cites | United States of America | Applicant |
| US5437031A | Cites | United States of America | Applicant |
| US5444823A | Cites | United States of America | Applicant |
| US5446891A | Cites | United States of America | Applicant |
| US5454105A | Cites | United States of America | Applicant |
| US5500561A | Cites | United States of America | Applicant |
| US5534734A | Cites | United States of America | Applicant |
| US5535257A | Cites | United States of America | Applicant |
| US5544036A | Cites | United States of America | Applicant |
| US5572438A | Cites | United States of America | Applicant |
| US5576700A | Cites | United States of America | Applicant |
| US5592620A | Cites | United States of America | Applicant |
| US5598464A | Cites | United States of America | Applicant |
| US5600778A | Cites | United States of America | Applicant |
| US5603034A | Cites | United States of America | Applicant |
| US5623679A | Cites | United States of America | Applicant |
| US5623681A | Cites | United States of America | Applicant |
| US5625818A | Cites | United States of America | Applicant |
| US5634016A | Cites | United States of America | Applicant |
| US5634048A | Cites | United States of America | Applicant |
| US5640561A | Cites | United States of America | Applicant |
| US5644625A | Cites | United States of America | Applicant |
| US5649186A | Cites | United States of America | Applicant |
| US5664170A | Cites | United States of America | Applicant |
| US5673252A | Cites | United States of America | Applicant |
| US5684710A | Cites | United States of America | Applicant |
| US5692132A | Cites | United States of America | Applicant |
| US5696695A | Cites | United States of America | Applicant |
| US5699428A | Cites | United States of America | Applicant |
| US5701399A | Cites | United States of America | Applicant |
| US5708709A | Cites | United States of America | Applicant |
| US5721897A | Cites | United States of America | Applicant |
60 members in 6 offices
Priority claims34
| Document | Office | Kind | Date |
|---|---|---|---|
| 12553199 | United States of America | P | |
| 12553199 | United States of America | P | |
| 13575199 | United States of America | P | |
| 13575199 | United States of America | P | |
| 14385999 | United States of America | P | |
| 14385999 | United States of America | P | |
| 15201599 | United States of America | P | |
| 15201599 | United States of America | P | |
| 15359499 | United States of America | P | |
| 15359499 | United States of America | P | |
| 52535000 | United States of America | A | |
| 52535000 | United States of America | A | |
| 53250000 | United States of America | A | |
| 53250000 | United States of America | A | |
| 64358400 | United States of America | A | |
| 64358400 | United States of America | A | |
| 4480408 | United States of America | A | |
| 09525350 | – | – | – |
| 09532500 | – | – | – |
| 09643584 | – | – | – |
| 60125531 | – | – | – |
| 60135751 | – | – | – |
| 60143859 | – | – | – |
| 60152015 | – | – | – |
| 60153594 | – | – | – |
| US19990125531P | – | – | – |
| US19990135751P | – | – | – |
| US19990143859P | – | – | – |
| US19990152015P | – | – | – |
| US19990153594P | – | – | – |
| US20000525350 | – | – | – |
| US20000532500 | – | – | – |
| US20000643584 | – | – | – |
| US20080044804 | – | – | – |
Members60
| Document | Office | Kind | |
|---|---|---|---|
| EP0822477A2 | European Patent Office (EPO) | A2 | |
| EP0822477A3 | European Patent Office (EPO) | A3 | |
| KR980011440A | Republic of Korea | A | |
| JPH114576A | Japan | A | |
| TW362277B | Taiwan Province of China | B | |
| US5987464A | United States of America | A | |
| US6064250A | United States of America | A | |
| EP1028363A1 | European Patent Office (EPO) | A1 | |
| US6137335A | United States of America | A | |
| US2001001230A1 | United States of America | A1 | |
| US6323721B1 | United States of America | B1 | |
| US6323722B1 | United States of America | B1 | |
| US6326839B2 | United States of America | B2 | |
| US6338082B1 | United States of America | B1 | |
| US6442549B1 | United States of America | B1 | |
| EP1028363B1 | European Patent Office (EPO) | B1 | |
| DE69719097D1 | Germany | D1 | |
| EP0822477B1 | European Patent Office (EPO) | B1 | |
| DE69725078D1 | Germany | D1 | |
| DE69719097T2 | Germany | T2 | |
| US6678717B1 | United States of America | B1 | |
| DE69725078T2 | Germany | T2 | |
| US6760746B1 | United States of America | B1 | |
| US6895430B1 | United States of America | B1 | |
| US6901436B1 | United States of America | B1 | |
| US6944658B1 | United States of America | B1 | |
| US2005235031A1 | United States of America | A1 | |
| US6973505B1 | United States of America | B1 | |
| KR100514024B1 | Republic of Korea | B1 | |
| US7010568B1 | United States of America | B1 | |
| US7120236B1 | United States of America | B1 | |
| US7136932B1 | United States of America | B1 | |
| US7188138B1 | United States of America | B1 | |
| US7194552B1 | United States of America | B1 | |
| US2008005127A1 | United States of America | A1 | |
| US2008005342A1 | United States of America | A1 | |
| US2008010365A1 | United States of America | A1 | |
| US2008016142A1 | United States of America | A1 | |
| US2008016233A1 | United States of America | A1 | |
| US2008059607A1 | United States of America | A1 | |
| JP2008259420A | Japan | A | |
| JP4259632B2 | Japan | B2 | |
| US7565402B2 | United States of America | B2 | |
| US8037168B2 | United States of America | B2 | |
| US2011252059A1 | United States of America | A1 | |
| JP4842992B2 | Japan | B2 | |
| US8224994B1 | United States of America | B1 | |
| USRE43690EThis record | United States of America | E | |
| US2012278467A1 | United States of America | A1 | |
| USRE44207E | United States of America | E | |
| US8458161B2 | United States of America | B2 | |
| US8612565B2 | United States of America | B2 | |
| US8635340B1 | United States of America | B1 | |
| US8667051B2 | United States of America | B2 | |
| USRE44898E | United States of America | E | |
| US8990347B2 | United States of America | B2 | |
| US2015201039A1 | United States of America | A1 | |
| US9141717B2 | United States of America | B2 | |
| US2015370866A1 | United States of America | A1 | |
| US9659070B2 | United States of America | B2 |
65 transactions on the USPTO file
Allowed after 1 non-final rejection and 1 final rejection.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Response to Reasons for AllowanceREAS | REAS | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Response after Non-Final ActionA... | A... | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Oath or Declaration Filed (Including Supplemental)C602 | C602 | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Notice of Incomplete ReplyINCR | INCR | |
| Payment of additional filing fee/PreexamFLFEE | FLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Notice of Reissue Published in Official GazetteNRE. | NRE. | |
| Cleared by L&R (LARS)L128 | L128 | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Certificate of correctionCC | CC | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- RE043690
- Publication, DOCDB
- RE43690
- Publication, EPODOC
- USRE43690E
- Application
- 12044804
- Application, DOCDB
- 4480408
- Application, EPODOC
- US20080044804
Titles
- English
- Search engine request method, product, and apparatus
Classification
- CPC, 3
- H04L61/301
- H04L69/40
- H04L61/30
- IPC, 1
- G06F15 16
- USPC, 5
- 709203000
- 707999003
- 707999010
- 709217000
- 709219000