This invention generally relates selecting online advertisements, and more specifically relates to a method, product, and apparatus for using a URI component to select and provide advertising, search terms, and available identifiers.
The 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.
The 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.
Client 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.
The Web is a means of accessing information on the Internet that allows a user to “surf the web” and navigate 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 available on a wide range of computer platforms including PC's.
A 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. URIs 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.
The 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”.
A 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.
URLs are used in media and written in documents or typed within e-mail, and data files, etc. as a means to make reference to online content that helps express the context of the ideas one wishes to communicate. URLs are generally written in an abbreviated manner as partial URLs or domain names (e.g., “http://www.example.com” is the URL, “www.example.com” is the FQDN, and “example.com” is the domain name). During the early stages of commercialization on the Internet, businesses displayed the full URL when advertising a commercial or display ad as a means to locate such resources on the Internet.
Improvements have been made to recognize partial URLs when entered in the location field of a web browser or network accessible device for automatically appending protocol information so a full URL request can be made. By submitting a domain name or FQDN in the location field, the browser modifies the request by adjusting the partial URL and adding “http://” in front of the domain name or FQDN in order to construct a valid URL. As a result of this convenience, companies have modified their advertising and distribution of URLs through print, film, radio, television and other media as “example.com” or “www.example.com” instead of the URL “http://www.example.com”. Though a helpful mnemonic for consumers to more readily identify and access the location and origin of goods and services on a public network such as the Internet, the mnemonic is only applicable when using a command line of a device or location field of a web browser program as a means to access the advertised web site.
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, 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 “.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 may be used to simultaneously access both a resource and search request.
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.” generates a shorter URI on the fly as a substitute for longer URIs that reflect the results of queries or search requests. For instance, when “http://update.to/news” is received as input it may be determined that no such URI exists and, in response, create the URI on the fly as a means to access content from a longer URI such as:
This 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 including advertising, search terms, and available identifiers may be accessed.
Briefly, the present invention allows portions of a URI to be used as a search request for advertising selection. The invention allows for coupons, rebates, offers and advertising to de displayed or printed in response to keywords extracted from a URI or meta content corresponding with the page source of such a URI. The present invention displays keywords extracted from Meta or Title information to assist a user or subscriber with search terms to help form a query or search request. The invention also displays available identifiers such as domain names in addition to the displayed search terms. The present invention allows for keywords used as a search request to be further used as path names to generate a shorter URI on the fly in real time rather than displaying such search results from a longer URI. The invention further uses extracted keywords to display advertising that represents competition to the received URI. The present invention reduces the extra steps of remembering or typing and possibly misspelling a recipient address, by combining the functions of sending e-mail by only typing in a URI. The invention enables the user to combine Boolean logic with valid URI notation to generate a search request from the URI or vice-versa.
In general, in accordance with 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 URI component from the first URI, selecting a first content corresponding to said at least one URI component of the first URI, generating a valid accessible second URI that accesses said first content, and accessing the first URI and said second URI.
In accordance with another aspect of the present invention a method for processing a search request having at least one keyword, wherein the search results of the search request is accessed from an accessible first URI having a query component that corresponds to the at least one keyword includes the steps of generating a second URI having a default file that accesses the first URI and a non-query component that corresponds to the at least one keyword, and accessing said second URI.
In accordance with yet another aspect of the present invention a method for sending a message to an e-mail address includes the steps of accessing an accessible first URI, wherein said first URI is not an e-mail address, submitting the message to be sent from said first URI, generating the e-mail address from said first URI in response to submitting the message, and sending the message to the generated e-mail address.
In 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.
In 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.
The 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.
The present invention will now be described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout.
Turning 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.
The 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.
A 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, 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.
It 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.
In 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.
The client computers 110 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 110 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.
Each client 110 typically includes one or more processors 166, memories 168, and input/output devices 170. An input device may be any suitable device for the user to give input to client computer system 110, 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.
The servers 120 may be similarly configured. However, in many instances server sites 120 include many computers, perhaps connected by a separate private network. In fact, the network 130 may include hundreds of thousands of individual networks of computers. Although client computers 110 are shown separate from the server computers 120, 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 100 shown in
During operation of the distributed system 100, users of the clients 110 may desire to access information records 122 stored by the servers 120 while utilizing, for example, the Web. Furthermore, such server systems 120 may also include one or more search engines having one or more databases 124. The records of information 122 may be in the form of Web pages 150. The pages 150 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.
The clients 110 may execute Web browser programs 112, such as Netscape Navigator or MSIE to locate the pages or records 150. The browser programs 112 enable users to enter addresses of specific Web pages 150 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 112 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.
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, explains how URI components such as scheme, hostname, TLD, port, path, query, or fragment of a URI are regarded as data elements used for generating an accessible URI. All combinations for concatenating component data that does not form a full URI may be referred to as a Partial Uniform Resource Identifier (PURI). The same applies for Partial Uniform Resource Locators (PURLs) and other resource types.
For example, when the input “books.com” is received, the URI “http://books.com” is generated and URI components “http”, “books”, “com” may be extracted from the CGI script. The word “books” may be used to select an advertisement by consulting a table of advertisements and/or advertising cache 190 relating to the keyword “books”. Many advertisers may compete for rotation frequency of their ad per group or category. When an ad is selected, an accessible URI may be generated and when accessed displays the advertisement and web based location field in one frame and display the content of the URI “http://books.com” in the second frame. Another example, is when a TLDA is received as input such as “top.stories”. The URI “http://stories.top.com” may be generated based upon a selected access method (note that a variety of access methods may be used by the present invention to generate different accessible URIs if need be). Keywords extracted from URI are “stories” and “top”. A phrase such as “top stories” and “stories top” may also be generated from URI components to more specifically target ad categories for advertisers.
It may then be determined in step 550 which ad may be selected and retrieved from an ad cache 190 corresponding to at least one extracted keyword. After the ad has been selected, an accessible second URI may then be generated in step 555 that when accessed displays a web page with two frames. An ad may be accessed by the first frame including selectable keywords to assist the user in performing further targeted searching of other search requests, while accessing the first URI in the other frame.
For instance, before the content of URI “http://stories.top.com” may be displayed as a result of or input “top.stories”, while a URI HEAD request further extracts keywords from the <META> tag or the <TITLE> tag from the URI to assist in yet more specific targeted ad rotation. In addition to “top” and “stories”, words like “news”, “headlines”, “weather”, “sports”, for example, may be extracted from the <META> tag of the URI. These extra keywords may be used to better target ads and also provide suggested categories that may be dynamically generated on the web page for selection to find more content specific to the user. After words have been extracted, the keywords may be used to select an ad from an ad cache the may reside on the client machine and/or locally through an advertising cache 190 stored at the Internet Service Provider (ISP)/Application Service Provider (ASP) or the like. If an ad can not be selected based on this information then keywords may be passed to generate a URI having a query to further assist in ad selection.
The display of suggested search terms or keywords to assist a user in refining a search request is not limited by the components of the URI to extract <META> or <TITLE> tag information from the next web page before displaying the next page. Such keywords may also be selected from any accessed content and/or the page source of the URI. In addition, such keywords may be selected from any URI components. Another preferred implementation is based on a search page as a front end for search engines. To date there is no such program implemented to make use of any tagged language such as HTML, DHTML, XML, XHTML, and SGML to name a few that extracts META information of a subsequent page to be used for extending the range of navigation by concurrently displaying such META information separately from the web page when accessed.
Advertisements may be selected in step 575 by retrieving ads from an ad cache that corresponds to at least one keyword or generated identifier. After keyword extraction, identifier generation, and ad selection, an accessible second URI may be generated in step 580 that displays a web page with two frames having the selected ad in the first frame including links of any identifiers available for registration, and a list of selectable keywords to assist with targeted searching of other web pages, while the first URI is accessed in a second frame.
Ads may be targeted by displaying a combination of competitor ads and/or hyperlinks in response to receiving the domain name or FQDN of the URI as input. The selected advertisement may corresponds to competition of an entity that manages the URI. For instance, the URI generated from input is “http://www.burgerking.com” and “burgerking” is extracted and determines that a McDonalds ad, rebate, or coupon may be displayed in conjunction with displaying the “burgerking” website. Links to a “McDonalds” web site may also be provided. Inputting an identifier such as “burgerking.44106” may generate the URI “http://44106.burgerking.com” and when “44106” is extracted from the identifier, Burger King locations near the zip code “44106” may be displayed in conjunction with the website.
For example, the home page of a website “http://update.to/index.htm” may provide an input text box that is used as a search request front end to pass variables to a CGI script. When the word “news” is entered and submitted as an input search request, the URI “http://update.to/cgi-bin/update.cgi?search=news” is generated. Before accessing the URI a script may be executed to determine whether a directory called “news” exists on the server “update.to”. When it is determined that a “news” directory does not exist, then the directory may be created. Furthermore, a file called “index.htm” is created in the “news” directory to generate the URI “http://update.to/news/index.htm”. The content of the “index.htm” file may include a URI redirection, a <META> tag refresh, or a <FRAME> tag which may be used to display the content from the URI of the search request “http://update.to/cgi-bin/update.cg i?search=news”.
In effect, shorter URLs are 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, 3LD) or any combination of domain levels may in turn be used to generate a query.
Analysis from major online search engines show that more than 90% of all search requests include three keywords or less. For instance, an accessible URI “http://example.com/coffee/cream/sugar/index.htm” may be generated in response processing the search request “coffee and cream and sugar”. In turn, the input “example.com/coffee/cream/sugar” may generate search results in response to processing a web address or URI as a search request. Boolean logic may be applied to extend variations of other search requests. In effect, URI notation may be used as a system to generate a Boolean search request from the URI or vice-versa. For example, the search request “coffee or cream or sugar” may yield “http://example.com/coffee.cream.sugar/index.htm”
whereas the search request “coffee or cream and sugar” may yield “http://example.com/coffee.cream/sugar/index.htm”
Another example for using a URI to reduce user steps is to make use of the correspondence between a HTTP address and an e-mail address. For instance, web pages may be generated such that on each web page there corresponds a hidden variable of an e-mail address as a means to contact the owner of the web page. This is particularly useful when the web page serves as a web based e-mail interface to contact a recipient such as a friend, co-worker, or business entity. For instance, when “http://zipit.to/president” is received as input and accessed, a web page may be displayed allowing anyone viewing the web page to compose an e-mail message without having to enter the e-mail address of the recipient. The burden of remembering or inputting and possibly misspelling the e-mail address of a recipient is eliminated because the hidden variable “mailto:president@zipit.to” is passed as a variable when the e-mail message is sent. After the composed e-mail is submitted from the web page, a lookup table or database may be used to further redirect the e-mail to a final destination designated by the recipient. In effect, e-mail may be delivered by using protocols other than the “mailto:” protocol.
A HTTP GET request may be generated from input and the browser 112 forwards the request to a server 120, which processes the request by executing a CGI script 812 to extract URI components for ad selection. A first URI 206 may be generated to receive a selected ad 815 for display and refresh the web based location field 814 when accessed by the first frame. The content 150 of the URI generated from the input may be displayed in the second frame 816 of the web page 810 when accessed. The location field 814 of the first frame may either persist by displaying the input or may be cleared out for entry of the next web address. Both the first URI and second URI may be generated as frames and displayed as a web page 810 by the CGI script 812.
Another web page 810′ (as discussed in
The second frame 820 may be used to display the content 150 of a web address. A URI GET request may be generated from input, and the browser 112 may forward the request to a server 120, which processes the request by executing a CGI script 812 to determine validity of the input.
An accessible URI is generated from the input and then a URI HEAD request may obtain and extract header information from the accessible URI to determine what advertisement 815′ and/or keywords 825 may be generated and displayed in the first frame 818 of the web page 810′ whereas the content of the second frame 820 is the content of the URI. Both the first URI and second URI may be generated as frames and displayed as a web page 810′ by the CGI script 812′.
Though 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 taskbar 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.
Those 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 154 of a browser program 112. Modifying the source code of the browser program 112 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. In addition, advertising banner ads may be displayed directly as part of the GUI for the client browser 112 rather than limited to web page based banner ad displayed in a frame as discussed in
Although 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.
The 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.
The application for patent claims priority of U.S. Provisional Application Ser. No. 60/153,594 filed Sep. 13, 1999, by Schneider and U.S. Provisional Application Ser. No. 60/152,015 filed Sep. 1, 1999, by Schneider, et al., which are hereby incorporated by reference.; Thethis application for patent is also related to co-pending applications and claims the benefita continuation-in-part of U.S. patent application Ser. No. 09/643,584 filed Aug. 22, 2000, by Schneider, et al., now U.S. Pat. No. 7,010,568; this application for patent is also a continuation-in-part of U.S. patent application Ser. No. 09/598,134 filed Jun. 21, 2000, by Schneider, andnow U.S. Pat. No. 6,895,430; and this application for patent is also a continuation-in-part of U.S. patent application Ser. No. 09/532,500 filed Mar. 21, 2000, by Schneider, now U.S. Pat. No. 7,136,932, which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4155042 | Permut et al. | May 1979 | A |
4190800 | Kelly, Jr. et al. | Feb 1980 | A |
4196310 | Forman et al. | Apr 1980 | A |
4390876 | Bjorklund et al. | Jun 1983 | A |
4486853 | Parsons | Dec 1984 | A |
4754326 | Kram et al. | Jun 1988 | A |
4811382 | Sleevi | Mar 1989 | A |
4823265 | Nelson | Apr 1989 | A |
4903206 | Itoh et al. | Feb 1990 | A |
4956771 | Neustaedter | Sep 1990 | A |
4956875 | Bernard et al. | Sep 1990 | A |
5109486 | Seymour | Apr 1992 | A |
5155837 | Liu et al. | Oct 1992 | A |
5155847 | Kirouac et al. | Oct 1992 | A |
5175681 | Iwai et al. | Dec 1992 | A |
5231570 | Lee | Jul 1993 | A |
5249230 | Mihm, Jr. | Sep 1993 | A |
5249275 | Srivastava | Sep 1993 | A |
5319699 | Kerihuel et al. | Jun 1994 | A |
5321740 | Gregorek et al. | Jun 1994 | A |
5386369 | Christiano | Jan 1995 | A |
5402490 | Mihm, Jr. | Mar 1995 | A |
5404231 | Bloomfield | Apr 1995 | A |
5404505 | Levinson | Apr 1995 | A |
5418951 | Damashek | May 1995 | A |
5437031 | Kitami | Jul 1995 | A |
5444823 | Nguyen | Aug 1995 | A |
5446891 | Kaplan et al. | Aug 1995 | A |
5454105 | Hatakeyama et al. | Sep 1995 | A |
5500561 | Wilhelm | Mar 1996 | A |
5534734 | Pugh et al. | Jul 1996 | A |
5535257 | Goldberg et al. | Jul 1996 | A |
5544036 | Brown, Jr. et al. | Aug 1996 | A |
5572438 | Ehlers et al. | Nov 1996 | A |
5576700 | Davis et al. | Nov 1996 | A |
5592620 | Chen et al. | Jan 1997 | A |
5598464 | Hess et al. | Jan 1997 | A |
5600778 | Swanson et al. | Feb 1997 | A |
5603034 | Swanson | Feb 1997 | A |
5623679 | Rivette et al. | Apr 1997 | A |
5623681 | Rivette et al. | Apr 1997 | A |
5625818 | Zarmer et al. | Apr 1997 | A |
5634016 | Steadham, Jr. et al. | May 1997 | A |
5634048 | Ryu et al. | May 1997 | A |
5640561 | Satoh et al. | Jun 1997 | A |
5644625 | Solot | Jul 1997 | A |
5649186 | Ferguson | Jul 1997 | A |
5664170 | Taylor | Sep 1997 | A |
5673252 | Johnson et al. | Sep 1997 | A |
5684710 | Ehlers et al. | Nov 1997 | A |
5692132 | Hogan | Nov 1997 | A |
5696695 | Ehlers et al. | Dec 1997 | A |
5699428 | McDonnal et al. | Dec 1997 | A |
5701399 | Lee et al. | Dec 1997 | A |
5708709 | Rose | Jan 1998 | A |
5721897 | Rubinstein | Feb 1998 | A |
5742818 | Shoroff et al. | Apr 1998 | A |
5745360 | Leone et al. | Apr 1998 | A |
5761083 | Brown, Jr. et al. | Jun 1998 | A |
5761689 | Rayson et al. | Jun 1998 | A |
5764906 | Edelstein et al. | Jun 1998 | A |
5778367 | Wesinger, Jr. et al. | Jul 1998 | A |
5790790 | Smith et al. | Aug 1998 | A |
5802524 | Flowers et al. | Sep 1998 | A |
5812776 | Gifford | Sep 1998 | A |
5813007 | Nielsen | Sep 1998 | A |
5815830 | Anthony | Sep 1998 | A |
5835087 | Herz et al. | Nov 1998 | A |
5841850 | Fan | Nov 1998 | A |
5842203 | D'Elena et al. | Nov 1998 | A |
5848396 | Gerace | Dec 1998 | A |
5857201 | Wright, Jr. et al. | Jan 1999 | A |
5870546 | Kirsch | Feb 1999 | A |
5881131 | Farris et al. | Mar 1999 | A |
5890172 | Borman et al. | Mar 1999 | A |
5892919 | Nielsen | Apr 1999 | A |
5892920 | Arvidsson et al. | Apr 1999 | A |
5895454 | Harrington | Apr 1999 | A |
5898836 | Freivald et al. | Apr 1999 | A |
5907680 | Nielsen | May 1999 | A |
5908467 | Barrett et al. | Jun 1999 | A |
5913215 | Rubinstein et al. | Jun 1999 | A |
5926116 | Kitano et al. | Jul 1999 | A |
5933604 | Inakoshi | Aug 1999 | A |
5937037 | Kamel et al. | Aug 1999 | A |
5937162 | Funk et al. | Aug 1999 | A |
5940847 | Fein et al. | Aug 1999 | A |
5944787 | Zoken | Aug 1999 | A |
5949419 | Domine et al. | Sep 1999 | A |
5953400 | Rosenthal et al. | Sep 1999 | A |
5953721 | Doi et al. | Sep 1999 | A |
5963205 | Sotomayor | Oct 1999 | A |
5963915 | Kirsch | Oct 1999 | A |
5970680 | Powers | Oct 1999 | A |
5974453 | Andersen et al. | Oct 1999 | A |
5978806 | Lund | Nov 1999 | A |
5978817 | Giannandrea et al. | Nov 1999 | A |
5978828 | Greer et al. | Nov 1999 | A |
5978842 | Noble et al. | Nov 1999 | A |
5982863 | Smiley et al. | Nov 1999 | A |
5987464 | Schneider | Nov 1999 | A |
5987508 | Agraharam et al. | Nov 1999 | A |
5991368 | Quatse et al. | Nov 1999 | A |
5991751 | Rivette et al. | Nov 1999 | A |
5995594 | Shaffer et al. | Nov 1999 | A |
5999907 | Donner | Dec 1999 | A |
5999912 | Wodarz et al. | Dec 1999 | A |
6003061 | Jones et al. | Dec 1999 | A |
6003077 | Bawden et al. | Dec 1999 | A |
6003082 | Gampper et al. | Dec 1999 | A |
6006264 | Colby et al. | Dec 1999 | A |
6006265 | Rangan et al. | Dec 1999 | A |
6009150 | Kamel | Dec 1999 | A |
6009459 | Belfiore et al. | Dec 1999 | A |
6012066 | Discount et al. | Jan 2000 | A |
6014660 | Lim et al. | Jan 2000 | A |
6018619 | Allard et al. | Jan 2000 | A |
6018768 | Ullman et al. | Jan 2000 | A |
6021433 | Payne et al. | Feb 2000 | A |
6023724 | Bhatia et al. | Feb 2000 | A |
6029195 | Herz | Feb 2000 | A |
6032150 | Nguyen | Feb 2000 | A |
6038601 | Lambert et al. | Mar 2000 | A |
6041324 | Earl et al. | Mar 2000 | A |
6057834 | Pickover | May 2000 | A |
6058250 | Harwood et al. | May 2000 | A |
6058355 | Ahmed et al. | May 2000 | A |
6061700 | Brobst et al. | May 2000 | A |
6061734 | London | May 2000 | A |
6061738 | Osaku et al. | May 2000 | A |
6065054 | Dutcher et al. | May 2000 | A |
6085242 | Chandra | Jul 2000 | A |
6091956 | Hollenberg | Jul 2000 | A |
6092100 | Berstis et al. | Jul 2000 | A |
6094665 | Lyons et al. | Jul 2000 | A |
6097108 | Tweed | Aug 2000 | A |
6098099 | Ellesson et al. | Aug 2000 | A |
6104582 | Cannon et al. | Aug 2000 | A |
6104990 | Chaney et al. | Aug 2000 | A |
6105098 | Ninose et al. | Aug 2000 | A |
6119153 | Dujari et al. | Sep 2000 | A |
6119234 | Aziz et al. | Sep 2000 | A |
6122520 | Want et al. | Sep 2000 | A |
6122627 | Carey et al. | Sep 2000 | A |
6125361 | Chakrabarti et al. | Sep 2000 | A |
6128623 | Mattis et al. | Oct 2000 | A |
6134588 | Guenthner et al. | Oct 2000 | A |
6137873 | Gilles | Oct 2000 | A |
6141408 | Garfinkle | Oct 2000 | A |
6141653 | Conklin et al. | Oct 2000 | A |
6148289 | Virdy | Nov 2000 | A |
6148342 | Ho | Nov 2000 | A |
6151622 | Fraenkel et al. | Nov 2000 | A |
6151624 | Teare et al. | Nov 2000 | A |
6154600 | Newman et al. | Nov 2000 | A |
6154725 | Donner | Nov 2000 | A |
6154771 | Rangan et al. | Nov 2000 | A |
6154777 | Ebrahim | Nov 2000 | A |
6157292 | Piercy et al. | Dec 2000 | A |
6167389 | Davis et al. | Dec 2000 | A |
6167449 | Arnold et al. | Dec 2000 | A |
6169476 | Flanagan | Jan 2001 | B1 |
6173406 | Wang et al. | Jan 2001 | B1 |
6181787 | Malik | Jan 2001 | B1 |
6181985 | O'Donnell et al. | Jan 2001 | B1 |
6182148 | Tout | Jan 2001 | B1 |
6182227 | Blair et al. | Jan 2001 | B1 |
6185619 | Joffe et al. | Feb 2001 | B1 |
6189030 | Kirsch et al. | Feb 2001 | B1 |
6195691 | Brown | Feb 2001 | B1 |
6198511 | Matz et al. | Mar 2001 | B1 |
6199076 | Logan et al. | Mar 2001 | B1 |
6202087 | Gadish | Mar 2001 | B1 |
6205139 | Voit | Mar 2001 | B1 |
6209048 | Wolff | Mar 2001 | B1 |
6212565 | Gupta | Apr 2001 | B1 |
6219696 | Wynblatt et al. | Apr 2001 | B1 |
6219709 | Byford | Apr 2001 | B1 |
6229532 | Fujii | May 2001 | B1 |
6230168 | Unger et al. | May 2001 | B1 |
6240360 | Phelan | May 2001 | B1 |
6240555 | Shoff et al. | May 2001 | B1 |
6249817 | Nakabayashi et al. | Jun 2001 | B1 |
6256671 | Strentzsch et al. | Jul 2001 | B1 |
6256739 | Skopp et al. | Jul 2001 | B1 |
6259771 | Kredo et al. | Jul 2001 | B1 |
6259972 | Sumic et al. | Jul 2001 | B1 |
6269361 | Davis et al. | Jul 2001 | B1 |
6282511 | Mayer | Aug 2001 | B1 |
6292172 | Makhlouf | Sep 2001 | B1 |
6292709 | Uhl et al. | Sep 2001 | B1 |
6297819 | Furst | Oct 2001 | B1 |
6298327 | Hunter et al. | Oct 2001 | B1 |
6298341 | Mann et al. | Oct 2001 | B1 |
6298352 | Kannan et al. | Oct 2001 | B1 |
6311214 | Rhoads | Oct 2001 | B1 |
6314469 | Tan et al. | Nov 2001 | B1 |
6321222 | Soderstrom et al. | Nov 2001 | B1 |
6321242 | Fogg et al. | Nov 2001 | B1 |
6324538 | Wesinger, Jr. et al. | Nov 2001 | B1 |
6324585 | Zhang et al. | Nov 2001 | B1 |
6324650 | Ogilvie | Nov 2001 | B1 |
6332141 | Gonzalez et al. | Dec 2001 | B2 |
6332158 | Risley et al. | Dec 2001 | B1 |
6338082 | Schneider | Jan 2002 | B1 |
6339767 | Rivette et al. | Jan 2002 | B1 |
6339786 | Ueda et al. | Jan 2002 | B1 |
6356422 | Bilac et al. | Mar 2002 | B1 |
6356898 | Cohen et al. | Mar 2002 | B2 |
6360256 | Lim | Mar 2002 | B1 |
6363433 | Nakajima | Mar 2002 | B1 |
6366298 | Haitsuka et al. | Apr 2002 | B1 |
6366906 | Hoffman | Apr 2002 | B1 |
6381627 | Kwan et al. | Apr 2002 | B1 |
6381651 | Nishio et al. | Apr 2002 | B1 |
6385620 | Kurzius et al. | May 2002 | B1 |
6389462 | Cohen et al. | May 2002 | B1 |
6393117 | Trell | May 2002 | B1 |
6401118 | Thomas | Jun 2002 | B1 |
6405243 | Nielsen | Jun 2002 | B1 |
6412014 | Ryan | Jun 2002 | B1 |
6421675 | Ryan et al. | Jul 2002 | B1 |
6427164 | Reilly | Jul 2002 | B1 |
6430623 | Alkhatib | Aug 2002 | B1 |
6434547 | Mishelevich et al. | Aug 2002 | B1 |
6438583 | McDowell et al. | Aug 2002 | B1 |
6442549 | Schneider | Aug 2002 | B1 |
6442602 | Choudhry | Aug 2002 | B1 |
6449657 | Stanbach, Jr. et al. | Sep 2002 | B2 |
6452609 | Katinsky et al. | Sep 2002 | B1 |
6496981 | Wistendahl et al. | Dec 2002 | B1 |
6502131 | Vaid et al. | Dec 2002 | B1 |
6502132 | Kumano et al. | Dec 2002 | B1 |
6505201 | Haitsuka et al. | Jan 2003 | B1 |
6509833 | Tate | Jan 2003 | B2 |
6510461 | Nielsen | Jan 2003 | B1 |
6513060 | Nixon et al. | Jan 2003 | B1 |
6519589 | Mann et al. | Feb 2003 | B2 |
6526402 | Ling | Feb 2003 | B2 |
6532366 | Chung et al. | Mar 2003 | B1 |
6549892 | Sansone | Apr 2003 | B1 |
6556992 | Barney et al. | Apr 2003 | B1 |
6560634 | Broadhurst | May 2003 | B1 |
6574737 | Kingsford et al. | Jun 2003 | B1 |
6578078 | Smith et al. | Jun 2003 | B1 |
6591291 | Gabber et al. | Jul 2003 | B1 |
6594697 | Praitis et al. | Jul 2003 | B1 |
6603844 | Chavez, Jr. et al. | Aug 2003 | B1 |
6604132 | Hitt | Aug 2003 | B1 |
6604241 | Haeri et al. | Aug 2003 | B1 |
6605120 | Fields et al. | Aug 2003 | B1 |
6606659 | Hegli et al. | Aug 2003 | B1 |
6608891 | Pelletier et al. | Aug 2003 | B1 |
6611803 | Furuyama et al. | Aug 2003 | B1 |
6615237 | Kyne et al. | Sep 2003 | B1 |
6615247 | Murphy | Sep 2003 | B1 |
6615348 | Gibbs | Sep 2003 | B1 |
6618697 | Kantrowitz et al. | Sep 2003 | B1 |
6618726 | Colbath et al. | Sep 2003 | B1 |
6628314 | Hoyle | Sep 2003 | B1 |
6636854 | Dutta et al. | Oct 2003 | B2 |
6636961 | Braun et al. | Oct 2003 | B1 |
6637032 | Feinleib | Oct 2003 | B1 |
6650877 | Tarbouriech et al. | Nov 2003 | B1 |
6654741 | Cohen et al. | Nov 2003 | B1 |
6654746 | Wong et al. | Nov 2003 | B1 |
6654779 | Tsuei | Nov 2003 | B1 |
6658573 | Bischof et al. | Dec 2003 | B1 |
6665620 | Burns et al. | Dec 2003 | B1 |
6668278 | Yen et al. | Dec 2003 | B1 |
6671585 | Lof et al. | Dec 2003 | B2 |
6671714 | Weyer et al. | Dec 2003 | B1 |
6671738 | Rajchel et al. | Dec 2003 | B1 |
6674993 | Tarbouriech | Jan 2004 | B1 |
6678717 | Schneider | Jan 2004 | B1 |
6691105 | Virdy | Feb 2004 | B1 |
6711585 | Copperman et al. | Mar 2004 | B1 |
6718321 | Birrell et al. | Apr 2004 | B2 |
6728767 | Day et al. | Apr 2004 | B1 |
6735585 | Black et al. | May 2004 | B1 |
6745367 | Bates et al. | Jun 2004 | B1 |
6748375 | Wong et al. | Jun 2004 | B1 |
6751562 | Blackett et al. | Jun 2004 | B1 |
6751606 | Fries et al. | Jun 2004 | B1 |
6760746 | Schneider | Jul 2004 | B1 |
6760770 | Kageyama | Jul 2004 | B1 |
6766369 | Haitsuka et al. | Jul 2004 | B1 |
6779178 | Lloyd et al. | Aug 2004 | B1 |
6799201 | Lee et al. | Sep 2004 | B1 |
6826617 | Ansell et al. | Nov 2004 | B1 |
6829653 | Tout | Dec 2004 | B1 |
6836805 | Cook | Dec 2004 | B1 |
6850940 | Wesinger, Jr. et al. | Feb 2005 | B2 |
6880007 | Gardos et al. | Apr 2005 | B1 |
6892226 | Tso et al. | May 2005 | B1 |
6895402 | Emens et al. | May 2005 | B1 |
6895430 | Schneider | May 2005 | B1 |
6901436 | Schneider | May 2005 | B1 |
6931451 | Logan et al. | Aug 2005 | B1 |
6944658 | Schneider | Sep 2005 | B1 |
6959339 | Wu et al. | Oct 2005 | B1 |
6961700 | Mitchell et al. | Nov 2005 | B2 |
6963928 | Bagley et al. | Nov 2005 | B1 |
6973505 | Schneider | Dec 2005 | B1 |
6981023 | Hamilton et al. | Dec 2005 | B1 |
6990678 | Zigmond | Jan 2006 | B2 |
7000028 | Broadhurst et al. | Feb 2006 | B1 |
7003442 | Tsuda | Feb 2006 | B1 |
7003719 | Rosenoff et al. | Feb 2006 | B1 |
7010568 | Schneider et al. | Mar 2006 | B1 |
7013298 | De La Huerga | Mar 2006 | B1 |
7039697 | Bayles | May 2006 | B2 |
7039708 | Knobl et al. | May 2006 | B1 |
7069323 | Gardos et al. | Jun 2006 | B2 |
7080158 | Squire | Jul 2006 | B1 |
7089194 | Berstis et al. | Aug 2006 | B1 |
7120236 | Schneider | Oct 2006 | B1 |
7136725 | Paciorek et al. | Nov 2006 | B1 |
7136932 | Schneider | Nov 2006 | B1 |
7149780 | Quine et al. | Dec 2006 | B2 |
7188138 | Schneider | Mar 2007 | B1 |
7194552 | Schneider | Mar 2007 | B1 |
7225249 | Barry et al. | May 2007 | B1 |
7337910 | Cartmell et al. | Mar 2008 | B2 |
7359987 | Stahura | Apr 2008 | B2 |
7418471 | King et al. | Aug 2008 | B2 |
7472160 | King et al. | Dec 2008 | B2 |
7490124 | King et al. | Feb 2009 | B2 |
7543026 | Quine et al. | Jun 2009 | B2 |
7546381 | Tout | Jun 2009 | B2 |
7565402 | Schneider | Jul 2009 | B2 |
7606858 | King et al. | Oct 2009 | B2 |
7627628 | King et al. | Dec 2009 | B2 |
7752260 | King et al. | Jul 2010 | B2 |
8037168 | Schneider | Oct 2011 | B2 |
8224994 | Schneider | Jul 2012 | B1 |
20010010032 | Ehlers et al. | Jul 2001 | A1 |
20010021947 | Kim | Sep 2001 | A1 |
20010047429 | Seng et al. | Nov 2001 | A1 |
20020010795 | Brown | Jan 2002 | A1 |
20020016174 | Gibson et al. | Feb 2002 | A1 |
20020023034 | Brown et al. | Feb 2002 | A1 |
20020024424 | Burns et al. | Feb 2002 | A1 |
20020059161 | Li | May 2002 | A1 |
20020065903 | Fellman | May 2002 | A1 |
20020069080 | Roy et al. | Jun 2002 | A1 |
20020069378 | McLellan et al. | Jun 2002 | A1 |
20020073233 | Gross et al. | Jun 2002 | A1 |
20020091703 | Bayles | Jul 2002 | A1 |
20020091827 | King et al. | Jul 2002 | A1 |
20020091836 | Moetteli | Jul 2002 | A1 |
20020103745 | Lof et al. | Aug 2002 | A1 |
20020129013 | Thomas | Sep 2002 | A1 |
20020156800 | Ong | Oct 2002 | A1 |
20020188699 | Ullman et al. | Dec 2002 | A1 |
20020194113 | Lof et al. | Dec 2002 | A1 |
20030009592 | Stahura | Jan 2003 | A1 |
20030014450 | Hoffman | Jan 2003 | A1 |
20030074672 | Daniels | Apr 2003 | A1 |
20030088708 | Lewallen | May 2003 | A1 |
20030098375 | Shiga et al. | May 2003 | A1 |
20030182447 | Schilling | Sep 2003 | A1 |
20030225670 | DeCarlo, III | Dec 2003 | A1 |
20040030759 | Hidary et al. | Feb 2004 | A1 |
20040044791 | Pouzzner | Mar 2004 | A1 |
20040088083 | Davis et al. | May 2004 | A1 |
20040107025 | Ransom et al. | Jun 2004 | A1 |
20050055306 | Miller et al. | Mar 2005 | A1 |
20050102354 | Hollenbeck et al. | May 2005 | A1 |
20050235031 | Schneider | Oct 2005 | A1 |
20060190623 | Stahura | Aug 2006 | A1 |
20060265516 | Schilling | Nov 2006 | A1 |
20080005342 | Schneider | Jan 2008 | A1 |
20080010365 | Schneider | Jan 2008 | A1 |
20080016142 | Schneider | Jan 2008 | A1 |
20080016233 | Schneider | Jan 2008 | A1 |
20080059607 | Schneider | Mar 2008 | A1 |
20080235383 | Schneider | Sep 2008 | A1 |
Number | Date | Country |
---|---|---|
54136617 | Oct 1979 | JP |
11085492 | Mar 1999 | JP |
11184667 | Jul 1999 | JP |
11242682 | Sep 1999 | JP |
11296428 | Oct 1999 | JP |
9909726 | Feb 1999 | WO |
9922488 | May 1999 | WO |
9939275 | Aug 1999 | WO |
0007133 | Feb 2000 | WO |
Entry |
---|
NTIA-DOC, RFC on the enhancement of the .us Domain Space, Aug. 4, 1998, from http:--www.ntia.doc.gov-ntiahome-domainname-usrfc-dotusrfc.htm. |
Oakes, C., Internet Keywords Patent Spat, Wired News, Jul. 22, 1999 from http:--www.wired.com-news-technology-0,1282,13892.00html. |
Perez, Juan Carlos, Mozilla Launches Firefox 1.0, PCWORLD.com, Nov. 9, 2004 <http:--www.pcworld.com-news-article-0,aid,118537,00.asp>. |
Advanced Control Systems, Inc.; Load Management; Advanced Control Systems, Inc.; Jun. 20, 2001 (Aug. 1999); USA; p. 1, paragraph 1; p. 2, paragraphs 1, 2, 3; p. 3, paragraphs 1 & 2; p. 4, paragraphs 1 & 2. |
American City Business Journal, Inc.; Blackout early warnings mandated; Apr. 3, 2001; USA; paragraphs 1, 2, 5, 6. |
Bradley, J.; ISO Blackout Notice Plan Follow-Up; Silicon Valley Manufacturers Group & California Independent System Operator (CAISO); May 8, 2001; p. 1, paragraphs 1, 2, 3, 4; p. 2, paragraphs 1, 3, 4. |
California, State of; Energy Action Plan; May 20, 2003; USA; p. 5, Section 1; pp. 7 & 8 Section V. |
California Independent System Operator; California Independent System Operator Participant's whom have entered into an Interruptible Service Contract or similar agreement; California Independent System Operator (CAISO); Dec. 10, 2002; p. 1. |
Desmond, J.; Customer Centric Alert and Resposne Program Overview; California Independent System Operator (CAISO); May 24, 2001; USA; pp. 2, 3, 4, 5, 6, 12, 13, 17, 18. |
Goldman, C.A.; Kintner-Meyer, M.; Heffner, G.; Do “Enabling Technologies” Affect Customer Performance in Price-Responsive Load Programs?; LBNL-50328; Ernest Orlando Lawrence Berkeley National Laboratory; http:--eetd.lbl.gov-EA-EMP-; Aug. 2002; p. 3, paragraph 2; p. 4, paragraph 2; p. 6, paragraph 3; p. 7, paragraphs 1 & 2, Table 2; p. 8, paragraphs 1, 2, 3, Table 3; p. 9, paragraphs 1, 2, 3, Table 4; p. 10, paragraphs 1, 2, 3; p. 11, paragraph 1, Table 5; p. 12, paragraphs 1 & 2, Figure 2; p. 15, paragraphs 2, 3, 4; p. 16, paragraph 2. |
Oesterreichishe Gesellshaft Fur Unwelt Und Technik; iea-experts group on r&d priority setting and evaluation liberalisation of the electricity market; http:--www.oegut.at; Mar. 18, 2002; Austria (in English); pp. 4 (Sections 3 & 4), 7 Section 3), 8 (Controllable “Dispatchable” Loads; Section 2), 9 (Distributed Energy Resources). |
O'Neil, E.; Cumulative Totals of No-Touch, Restricted Maintenance Operations, Alert, Warning, Emergency and Power Watch Notices Issued from 1998 to Present; California Independent System Operator (CAISO); May 29, 2003; USA; p. 4, Table; p. 5, Table; p. 6, Table; p. 7, Table; p. 8, Table; p. 9, Table; p. 10, Table; p. 11, Table; p. 11, Table; p. 12, Table; p. 14, Table. |
Perez, Pena, R.; Utility Could Have Halted '03 Blackout, Panel Says; New York Times; http:--www.nytimes.com-2004-0406-national-06BLAC.html; Apr. 6, 2004; USA; paragraphs 1, 2, 3, 4, 9. |
Purdum, T.; Statewide Blackouts Ordered as Heat Strains California Grid; New York Times; May 8, 2001; USA; paragraphs 3, 4, 5, 8, 9. |
United States of America, Federal Energy Regulation Commission; National Transmission Grid Study, Consolidated List of Recommendations; FERC; May 6, 2002, USA; pp. 2-76 & 3-77 Section 4, 5-79 Section 5. |
Weiss, J.; EPRI's Enterprise Infrastructure EPRI's Enterprise Infrastructure Security (EIS) Program Security (EIS) Program; Jul. 7, 2000; USA, pp. 2 through 24. |
Weller, G.H.; A Case Study Review of Technical and Technology Issues for Transition of a Utility Load Management Program to Provide System Reliability Resources in Restructured Electricity Markets; LBNL-52408; Ernest Orlando Lawrence Berkeley National Laboratory; http:--certs.lbl.gov.; Jul. 2001; USA; pp. 1 & 2, Section 1; pp. 3 & 4, Section 2; pp. 6-13, Sections 3.1-3.1.8; pp. 16-17, Section 3.3, Table 3.1; pp. 18-40, Section 4; pp. 41-42, Section 5; Appendix A. |
Werst, K.L., Why Rotating Outages?; California Independent System Operation (CAISO); Aug. 17, 2001; USA; paragraphs 1, 2, 3, 5, 6, 7. |
Donaghy, Melanie, “Wines & Vines,” Sep. 1997, vol. 78, No. 9, p. 39(6). |
FAX-Phone Switch for Multi-Ring Telephone Lines; Derwent Abstract; Jul. 1992. |
Schneider, Eric; Claims from Pending U.S. Appl. No. 11/687,672. |
Schneider, Eric; Claims from Pending U.S. Appl. No. 10/711,834. |
Schneider, Eric; Claims from Pending U.S. Appl. No. 12/044,804. |
Schneider, Eric; Claims from Pending U.S. Appl. No. 12/109,608. |
Motegi, N., Piette, MA.; Web-based Energy Information Systems for Large Commercial Buildings; Ernest Orlando Lawrence Berkely National Laboratory; May 2002; USA; p. 3, paragraphs 1, 2, 4, Figure 1; p. 4, paragraphs 1, 2, 3, 4; p. 7, paragraphs 2, 3, 4, Table 1; 10, paragraph 2; p. 11, paragraph 1, Table 5. |
Norman, J.; Southern Telecom and Main.net Announce Successful Demonstration of Broadband over Power Lines; Southern Telecom; Dec. 2003; p. 1. |
Wired News Report, The Postal Proposal, Wired News, May 8, 1999 from http:--www.wired.com-news-technology-0,1282.131-30,00.html. |
Wired News Report, Depp Space Web?, Wired News, Jul. 22, 1999 from http:--www.wired.com-news-technology-0,1282,139-09,00.html. |
Singhal, Vigyan and Smith, Alan Jay, “Analysis of locking behavior in three real database systems,” 1997, The VLDB Journal, vol. 6, pp. 40-52. |
Oakes, Chris, “Net Sol, ICANN Reach Accord,” Wired News, from wired.com-news-politics-0,1283,31557,00.html, Sep. 29, 1999, pp. 1-3. |
Web Page of Network Solutions. |
www.phonetic.com; Internet print-out; Wayback Machine. |
Courter, Gini; Microsoft Office 2000 Professional Edition, 1999, Sybex, pp. 92-96, 254-257. |
“What Words are Hiding in Your Phone Number?” Internet print-out of www.dialabc.com; Wayback Machine. |
Graves, K.; CAISO Summer 2001 Assessment; California Independent System Operator (CAISO); Mar. 22, 2001; USA; p. 29, paragraphs 1 & 2, p. 30, paragraphs 1, 2, Figure III-E. |
Graves, K.; CAISO Feb. 2001 Winter Assessment and Summer 2001 Post-season Summary; California Independent System Operator (CAISO); Oct. 8, 2001; USA; pp. 17 & 18, Section IV. |
Gross, G.; FCC moves ahead with powerline broadband rules; IDG News Service; Feb. 13, 2004; USA; paragraphs 1, 2, 6, 9. |
Guardino; Board of Governors; Notification Plan 2; California Independent System Operator (CAISO); May 21, 2001; USA. |
Helman, C., For years electric companies have dreamed of making their wires the high-speed data pipe to your PC. One tech company may yet make the dream possible.; Forbes.com; Jan. 20, 2003; USA; paragraphs 1, 2, 3, 4, 5. |
Jonker, R.; Dijak, P.; Enabling Distributed Generation and Demand Response with Enterprise Energy-Management Systems; Darnell.com Inc.; May 17, 2001; USA; p. 1, paragraphs 1 & 2; p. 2, paragarphs 1, 2, 3, 4, 5, 6, 7, 8; p. 5, paragraphs 2, 3, 4, 5, 6; p. 7, paragraphs 4, 6, 7, 8, 9; p. 8, paragraphs 2, 3, 4; p. 9; p. 10. |
Keoni, A.; California Independent System Operator Load Program Participants; California Independent System Operator (CAISO); Apr. 8, 2002; pp. 1, 2, 3. |
Keoni, A.; Implementation Plan and Required Information for the Partipating Load Program (PLP); California Independent System Operator (CAISO); Aug. 8, 2002; USA; p. 1, paragraphs 2 & 3; p. 2, paragraphs 1 & 2, Table 1. |
Labaton, S., F.C.C. Begins Rewriting Rules on Delivery of the Internet; Associated Press; Feb. 13, 2004; USA; paragarphs 1, 2, 6, 7. |
Lyon, D.; The Development of Electric System Emergencies and the Emergency Response Communication Network: White Paper; California Independent System Operator (CAISO); Jun. 20, 2001; USA; p. 2, paragraphs 1 & 4; p. 3, paragraph 1 & Section II; pp. 6, 7, 8, 9; pg. 10, Section III, paragraphs 1, 2, 3; p. 11, paragraphs 2 & 3; p. 12, paragraph 1; p. 13, paragraph 4, p. 14. |
Hollenbeck et al., “Domain Name System Wildcards in Top-Level Domain Zones”, VeriSign Naming and Directory Services, VeriSign, Inc., Sep. 9, 2003. |
Ohta, “Incremental Zone Transfer in DNS”, RFC 1995, Aug. 1996. |
Vixie et al., “Dynamic Updates in the Domain Name System (DNS Update)”, RFC 2136, Apr. 1997. |
Request for Comment (RFC) 2276, Architecture Principles of Uniform Resource Name Resolution, Sollins, Jan. 1998; pp. 1-24. |
Berners, Lee T.; “RFC1630: 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”, IETF, Jun. 1994; http:--www.faqs.org-rfcs-rfc1630.html. |
Mockapetris P., “RFC 1035: Domain Names-Implementation and Specification”, IETF, Nov. 1987, http:--www.faqs.org-rfcs-rfc1035.html. |
Harrenstien, et al.; “RFC954: Nicname-Whois”, IETF, Oct. 1985, http:--ww.faqs.org-rfcs-rfc954.html. |
Mockapetris, Request for Comment (RFC) 1034, Domain Names-Concepts and Facilities, Section 4.3.3, IETF, Nov. 1987, pp. 1-55. |
Request for Comment (RFC) 1480, The US Domain; Cooper & Postel, Jun. 1993, pp. 1-47. |
Samson, M., PGMedia, Inc. d-b-a Name.Space TM, v. Network Solutions, Inc., et al., Mar. 1999, pp. 1-2. |
Liberto, S.M., Domain Name Conflicts: Hey! That's My.Com!, WWWiz Magazine, Mar. 1998, pp. 1-3. |
Cabell, D., Learning Cyberlaw in Cyberspace, Name Conflicts, Berkman Center for Internet & Society, Harvard Law Schol, Aug. 1999, pp. 1-21. |
Goodin, D., CNET News.com: NSI domain slowdown persists, Jan. 1999, pp. 1-4. |
Goodin, D., CNET News.com: NSI confirms database revisions, Jan. 21, 1999, pp. 1-2. |
Northrup, T., Windows IT Library: Domain Name Services, Jul. 1998, pp. 1-41. |
Press Release, “OINGO Pioneers New Domain Name Variation Technology”, May 17, 2000; http:--www.namingsolutions.com-ns—new—pr—51700.hmtl. |
Statement of the policy oversign committee, The Economic Structure of Internet Generic Top-Level Domain Name Registries Analysis and Recommendations, Jul. 23, 1998. |
Crow, R., the Telephone Exchange Name Project, Web Site (1998), from http:--ourwebhome.com-TENP-TENproject.html. |
NTIA-DOC, Improvement of Technical Management of Internet Names and Addresses, Federal Register V63 N34, Feb. 20, 1998, from http:--www.ntia.doc.gov-ntiahome-domainname-022098fedreg.httm. |
Berners-Lee, T. et al., Uniform Resource Identifiers (URI): General Syntax; Network Working Group, Aug. 1988. |
Network Solutions and VeriSign Launch Combined Internet Name and Certification Registration, Internet World. Mar. 10, 1997. |
Network Solutions, Inc., Online Team up to Server Internet Needs of Small Business Owners, Jan. 1998, pp. 1-2. |
Schmid, E., McCorkle, S., O'Neil, E.; ISO Electric Emergency Notification: Memorandum; California Independent System Operator (CAISO); May 17, 2001; USA; p. 1, paragraphs 1 & 4; p. 2, paragraphs 1, 2, 3; p. 3; p. 4, paragraph 4 & 5; p. 5; p. 6, paragraph 1, p. 7; p. 8. |
What does your phone number spell?. Home page of www.phonespell.com; Wayback Machine, 1996. |
Network Working Group, Uniform Resource Identifiers (URI): General Syntax by T. Berners-Lee et al, Aug. 1998. |
Number | Date | Country | |
---|---|---|---|
60152015 | Sep 1999 | US | |
60153594 | Sep 1999 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09643584 | Aug 2000 | US |
Child | 09644587 | US | |
Parent | 09598134 | Jun 2000 | US |
Child | 09643584 | US | |
Parent | 09532500 | Mar 2000 | US |
Child | 09598134 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09644587 | Aug 2000 | US |
Child | 11952105 | US |