Hypertext service guide menu display

Information

  • Patent Grant
  • 9380347
  • Patent Number
    9,380,347
  • Date Filed
    Tuesday, May 27, 2014
    10 years ago
  • Date Issued
    Tuesday, June 28, 2016
    8 years ago
Abstract
The present invention provides a method and system for accessing services in a television system. In one implementation, a DHCT presents a user a menu containing a plurality of selectable link representations corresponding to separate services or applications offered by the cable television system. The user navigates the menu with a remote device and selects a desired service by choosing the selectable link representation corresponding to the desired service or application. The DHCT receives the user input, translates the selectable link command into an executable call, and activates the service or application corresponding to the selected link representation from the menu chosen by the user.
Description
FIELD OF THE INVENTION

This invention relates in general to the field of television systems, and more particularly, to a user interface for accessing services in television systems.


BACKGROUND

Historically, television services have been comprised of analog broadcast audio and video signals. Cable television systems now receive broadcasts and retransmit them with other programming to users over land-line networks, typically comprising fiber optic cable and/or coaxial cable. With the recent advent of digital transmission technology, cable television systems are now capable of providing much more than the traditional analog broadcast video. In addition, two-way and advanced one-way communications between a subscriber and a cable system headend are now possible.


In implementing enhanced programming, the home communication terminal (“HCT”), otherwise known as the settop box, has become an important computing device for accessing video services and navigating a subscriber through a maze of services available. In addition to supporting traditional analog broadcast video functionality, digital HCTs (or “DHCTs”) now also support an increasing number of services that are not analog, but rather digital; are not basic broadcast, but rather two-way communication such as video-on-demand; and are not basic video, such as e-mail or web browsers. These are all in addition to the host of other television services that are increasingly being demanded by consumers, examples of which include audio and audio/visual programming, advanced navigation controls, impulse pay-per-view technology, and on-line commerce. In addition to the interactive services, the increased bandwidth available through a digital television system has made it possible for a subscriber to have access to hundreds, or even thousands, of channels and/or services. Thus, in order to provide these more powerful and complex features, the simple conventional channel abstractions need to be extended beyond those that have traditionally been provided.


Each HCT or DHCT (collectively hereinafter “DHCT”) is typically connected to a cable or satellite television network. The DHCTs generally include hardware and software necessary to provide the functionality of the digital television system at the client's site. Preferably, some of the software executed by a DHCT is downloaded and/or updated via the cable television network. Each DHCT typically includes a processor, communication components and memory, and is connected to a television or other display device, such as a personal computer. While many conventional DHCTs are stand-alone devices that are externally connected to a television, a DHCT and/or its functionality may be integrated into a television or personal computer, as will be appreciated by those of ordinary skill in the art.


Because many separate services may be offered by a single cable television service provider to each individual subscriber, including television viewing channels as well as other applications, there is a need for the DHCT to not only be able to provide each service or application that the cable television system provider offers but also be able to flexibly control access to services that are denoted as premium services. As system operators of cable television systems continue to add services and applications, a problem exists in both making the subscriber aware of and also in providing quick access to the new services and channels. Because of the large number of viewing options presented to a subscriber, a problem also exists in providing the subscriber a quick and efficient method to access the most popular or commonly viewed services.


SUMMARY OF THE INVENTION

Briefly described, the preferred embodiment of the present invention provides a method and system for accessing services in a television system. In one implementation, a DHCT presents a subscriber a menu containing a plurality of selectable link representations corresponding to separate services or applications offered by the cable television system. The subscriber navigates the menu with a remote device and selects a desired service for viewing by choosing the selectable link representation corresponding to the desired service or application. The DHCT receives the user input, translates the selectable link command into an executable call, and activates the service or application corresponding to the selected link from the menu chosen by the subscriber.


Many objects, features, and advantages of the present invention will become apparent to one with skill in the art upon examination of the following drawings and detailed description.





BRIEF DESCRIPTION OF THE DRAWINGS

The invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. In the drawings, like reference numerals designate corresponding parts throughout the several views.



FIG. 1 is a block diagram of a cable television system in accordance with one preferred embodiment of the present invention.



FIG. 2 is a block diagram of a DHCT with components and applications shown in various memories with related equipment in accordance with the preferred embodiment of present invention depicted in FIG. 1.



FIG. 3 is a diagram of the service guide presented to the user by the DHCT in FIG. 2 upon activation of the service guide application.



FIG. 4 is a flowchart of the process of presenting the service guide menu as depicted in FIG. 3 and activating the chosen service or application corresponding to the selected link in the service guide menu.



FIG. 5 is a diagram of the service guide presented to the user by the DHCT in FIG. 2 depicting selectable link representations with additional information banners viewable by the user upon moving the cursor to a particular selectable link representation.



FIG. 6 is a diagram of a remote unit with a dedicated key to access the service guide depicted in FIG. 3.



FIG. 7 is a diagram of the mappings of services to channels wherein the service guide in FIG. 3 is mapped to a channel of the channel table.



FIG. 8 is a diagram of an interactive program guide display that provides access to the service guide in FIG. 3.



FIG. 9 is a diagram of the service guide in FIG. 3 displayed upon selection of the service guide menu from the interactive program guide of FIG. 8.



FIG. 10 is a diagram of an alternative embodiment service guide presentation for the user upon activating the service guide menu from the IPG display in FIG. 8.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT


FIG. 1 is a block diagram of a cable television system 10 including a headend 11 for receiving television signals, such as satellite television signals, and converting the signals into a format for transmitting the signals over the system 10. The transmitted signals can, for example, be radio frequency (RF) signals or optical signals, as shown, transmitted over fiber optic cable 12. When the optical signals are transmitted by the headend 11, one or more optical nodes 13 are included in the system 10 for converting the optical signals to RF signals that are thereafter routed over other media, such as coaxial cables 14. Taps 15 are provided within the cable system 10 for splitting the RF signal off, via cables 17, to subscriber equipment such as DHCTs 16, cable-ready television sets, video recorders, or computers. Thus, headend 11 is connected through a network 20 to multiple DHCTs 16.



FIG. 2 is a block diagram illustrating the DHCT 16 and other system equipment. The DHCT 16 is typically situated within the residence or business of a subscriber. It may be integrated into a device that has a display 21, such as a television set, or it may be a stand-alone unit that couples to an external display 21, such as a display included with a computer or a television, and that processes media transported in television signals for presentation or playback to a subscriber (user of the DHCT). The DHCT 16 preferably comprises a communications interface 22 for receiving the RF signals, which can include media such as video, audio, graphical and data information, from the tap 15 and for providing any reverse information to the tap 15 for transmission back to the headend 11 (FIG. 1). The DHCT 16 further includes a processor 24 for controlling operations of the DHCT 16, including a video output port such as an RF output system 28 for driving the display 21, a tuner system 25 for tuning into a particular television channel to be displayed and for sending and receiving data corresponding to various types of media from the headend 11. The tuner system includes in one implementation, an out-of-band tuner for bi-directional quadrature phase shift keying (QPSK) data communication and a quadrature amplitude modulation (QAM) tuner for receiving television signals. Additionally, DHCT 16 includes a receiver 26 for receiving externally-generated information, such as user inputs or commands for other devices. The DHCT 16 may also include one or more wireless or wired communication interfaces, also called ports, for receiving and/or transmitting data to other devices. For instance, the DHCT may feature USB (Universal Serial Bus), Ethernet (for connection to a computer), IEEE-1394 (for connection to media devices in an entertainment center), serial, and/or parallel ports. The user inputs may, for example, be provided by a computer or transmitter with buttons or keys located either on the exterior of the terminal or by a hand-held remote control device 27 or keyboard that includes user-actuated buttons.


In one implementation, a memory portion 29 of the DHCT 16 includes flash memory 31 and dynamic random access memory (DRAM) 32 for storing the executable programs and related data components of various applications and modules for execution by the DHCT 16. Both the flash memory 31 and the DRAM memory 32 are coupled to the processor 24 for storing configuration data and operational parameters, such as commands that are recognized by the processor 24.


Basic functionality of the DHCT 16 is provided by an operating system 33 that is contained in flash memory 31. One or more programmed software applications, herein referred to as applications, are executed by utilizing the computing resources in the DHCT 16. The application executable program stored in flash memory 31 or DRAM memory 32 is executed by processor 24 (e.g., a central processing unit or digital signal processor) under the auspices of the operating system 33. Data required as input by the application program is stored in DRAM memory 32 and read by processor 24 from DRAM memory 32 as need be during the course of application program execution. Input data may be data stored in DRAM memory 32 by a secondary application or other source, either internal or external to the DHCT 16, or possibly anticipated by the application and thus created with the application program at the time it was generated as a software application program, in which case it is stored in flash memory 31. Data may be received via any of the communication ports of the DHCT 16, from the headend 11 via the DHCT's network interface (i.e., the QAM or out-of-band tuners) or as user input via receiver 26. A type of input data fulfills and serves the purpose of parameters as described below. Data generated by application program is stored in DRAM memory 32 by processor 24 during the course of application program execution.


The flash memory 31 also contains a platform library 36. The platform library 36 is a collection of functionality useful to applications, such as a Timer Manager, Compression Manager, Database Manager, Widget Toolkit, String Managers, and other utilities (not shown). These utilities are accessed by applications as necessary so that each application does not have to contain these utilities thus resulting in memory consumption savings and a consistent user interface.


A Service Application Manager (SAM) provides a model in which the user can access services available on the system. A service consists of an application to run and a parameter, such as data content, specific to that service. The SAM handles the lifecycle of the applications on the system, including the definition, initiation, activation, suspension and deletion of services they provide and the downloading of the application into the DHCT 16 as necessary. Many services can be defined using the same application component, with different parameters. The SAM includes a SAM server (not shown) in headend 11 and a SAM client 37 in the DHCT 16. The SAM client 37 (hereinafter referred to as SAM 37) is a part of the platform 36. As a non-limiting example, an application to tune video programming could be executed with one set of parameters to view HBO and a separate set of parameters to view CNN. Each association of the application component (tune video) and one parameter component (HBO or CNN) represent a particular service that has a unique service ID.


An application client is the portion of an application that executes on the DHCT 16 and provides the application's services to the user typically through a graphical user interface. Also contained in flash memory 31 is a navigator application 35 that provides a navigation framework for the user to access services available on the cable system. Examples of the services include, in one implementation, watching television and pay-per-view events, listening to digital music, and an interactive program guide, each of which is controlled through separate applications in flash memory 31. The navigator 35 also allows users to access various settings of the DHCT 16, including volume, parental control, VCR commands, etc.


Interactive program guide (IPG) 38, Watch TV 42, and pay-per-view (PPV) 44 are all resident applications in flash memory 31. The IPG 38 displays a program guide to the user and populates the guide with program data for selection. Watch TV 42 enables a user to simply “watch television” while PPV 44 enables viewing of premium television services. These applications, because they are in flash memory 31, are available to the user and do not need to be downloaded each time the DHCT 16 initializes.


The applications that are stored in the DRAM 32 may be applications that are loaded when the DHCT 16 initializes or are applications that are downloaded to the DHCT 16 upon a user-initiated command using an input device such as the remote 27. In this non-limiting example, as shown in FIG. 2, DRAM 32 contains the following application clients (hereinafter referred to as “application(s)”): a video-on-demand application (VOD) 43, an e-mail application 45, a digital music application 47. Additionally, DRAM 32 could also contain a calendar application (not shown) and a calculator application (not shown). It should be obvious to one with ordinary skill in the art that these applications are not limiting and merely serve as examples for this present embodiment of the invention.


The applications shown in FIG. 2 and all others provided by the cable system operator are top level software entities on the network for providing services to the user. In one implementation, all applications executing on the DHCT 16 work with the navigator 35 by abiding by several guidelines. First, an application must utilize and implement the SAM 37 for provisioning, activation, and suspension of services. Second, an application must share DHCT 16 resources with other applications and abide by the resource management policies of the SAM 37, the operating system 33, and the DHCT 16. Third, an application must handle all situations where resources are unavailable without navigator 35 intervention. Fourth, when an application loses service authorization while providing a service, an application should suspend the service gracefully. The navigator 35 will reactivate an individual service application when it later becomes authorized. Finally, an application must be configured so it does not respond to input commands reserved for the navigator. For instance, as a non-limiting example, when user input commands are entered via a wireless remote control device or keyboard, the application must be configured so it does not have access to certain user input keys that are reserved by the navigator 35 (i.e., power, channel +/−, volume +/−, etc.). However, without any limitations to the aforementioned, in certain circumstances certain applications during the course of program execution may reach a machine-state in which input keys that would ordinarily be reserved may be employed for input by the application but only during that particular machine-state. For instance, an application may display a user interface that specifically requests input or selection from the user in which one or more of the reserved keys are used momentarily during that machine-state.


Other forms of entering input commands, such as voice-activated commands in a DHCT 16 with an input communication port that receives signals from a wired or wireless microphone and circuitry to process and compare digitized speech signals, would be subject to similar configuration so that DHCT 16 does not respond to input commands reserved for the navigator 35. In this alternate embodiment, the audio input port (not shown) in the DHCT 16 is a single receiver device. Additionally, the DHCT 16 has digital signal processing capability that implements a subtraction filter to effect subtraction of the audio generated by the DHCT 16 from the speech signal received from the user.


Another application shown in FIG. 2 that is contained in DRAM 32 is the service guide application client 39 (hereinafter referred to as “service guide 39”). The service guide 39 consists of a graphical user interface to create a hypertext markup language (HTML) file (or other middleware markup languages such as one created via XML (Extensible Markup Language)). The service guide 39 may be customized remotely by the system operator by editing the generated HTML file or by using a graphical HTML editor. The service guide 39 uses an HTML display engine and parser (not shown) to parse the HTML file and render the service guide display to the user. Depending on the embodiment, the HTML engine may be part of the service guide 39 or extended by the operating system 33 or platform 36, or some combination of both. The service guide 39 receives input commands generated by a user via an input device, such as a remote control device 27 (FIGS. 2 & 6), and received by an input communication port 26 (FIG. 2) in DHCT 16. A service selection may be effected by navigating (moving the highlight “cursor”) through the service guide display by manipulating designated buttons of a wired or wireless remote device or keyboard 27 or electronic mouse (not shown). The selection of a service or entry from the service guide 39 HTML display invokes HTML commands, which are received by the service guide 39 and translated into one or more application executable calls that are executed by the navigator 35 and the SAM 37 in activating the desired service. Any of a multiplicity of services may be activated through the service guide 39 and its corresponding interface (discussed below), including any native application to the DHCT 16, any downloadable application supported by the cable television provider at the headend 11, any Internet web content, or any other information source provided through the cable television system 10.


References to the selection of a service or entry from the multiplicity of services and/or entries displayed by the service guide 39 on display 21 comprise the process of interactively navigating by moving the highlight cursor and transmitting input commands to DHCT 16. The processor 24 processes data extracted and/or interpreted from the input commands to effect visual cursor position and visual feedback of the user's selection on the display 21. When the user inputs a selection, the processor 24 invokes communication between internal components in the DHCT 16, including software components such as the navigator 35 and SAM 37, to activate the selected service. The processor 24 employs the messaging services of the operating system 33 to effect the communication between any two or more of the internal components.



FIG. 3 is a diagram of the display 50 with the service guide menu 52 presented to the user by the DHCT 16 depicted in FIG. 2. With additional reference to the flowchart 60 shown in FIG. 4, the service guide menu 52 is presented upon activation of the service guide 39 (FIG. 2), as depicted in step 61 and as described above. Upon activation of the service guide 39, a navigable menu 52 is presented to the user as shown in FIG. 3 and depicted in step 62 as shown in FIG. 4. In this embodiment, the HTML display includes an identification string 54 indicating that the pop-up menu 52 is the service guide. The HTML display also includes a series of icons and text strings that are each selectable hyper-text link labels 56 organized in a vertically oriented list of services for the user to navigate (by moving the cursor) with the remote device 21. A footer includes a text string and graphical image instructing the user how to exit the service guide menu 52.


One of the selectable link labels 56 is highlighted to visually identify the current cursor position 58 so that the user can enact cursor navigation functionality and move among the selectable link labels 56, as shown in step 64 (FIG. 4). Once the user, via the remote 21 or other input device, selects one of the selectable link labels 56, the service guide 39 translates the associated HTML hyper-text link destination information for the selected link label 56 to an executable call for the navigator 35 or the SAM 37, as shown in step 67 (FIG. 4). The SAM 37 implements the service request by executing and activating the desired application to provide the service corresponding to the selected selectable link label 56, as shown in step 69 (FIG. 4).


In the preferred embodiment, the selectable link labels 56 are written in a customized version of the middleware markup language HTML. The selectable link label 56 is only one type of link representation that may be displayed to the user by the DHCT 16. Moreover, a link label 56 may be displayed as text only, text plus an icon, or an icon only. The selectable link labels 56 are rendered based upon HTML (or XML) hyperlink definitions. Therefore, the link definitions are comprised of an anchor <A> to define the start and destination of the hypertext link definition, and the text between the start and an end tag defines the label for the link definition. The label can include graphics defined with IMG or OBJECT elements. One example link definition expressed in HTML includes the following syntax: <A HREF=“tv://destination_service”><IMG SRC=“graphic_icon”>text label</A>. In this example, “tv://destination_service” is the destination definition (also referred to herein as a destination address, destination reference, service reference, or universal resource locator (URL)) and “<IMG SRC=“graphic_icon”>text label” is the label definition (also referred to herein as one type of link representation definition or label reference). Also in this example, the label definition includes an IMG element and text, both of which will be used to generate visual representations that are selectable by the user. The IMG element further defines the location of the image file, as a URL.


A system operator at the headend 11 uses a service guide server 48 (FIG. 2) to configure the service guide display 52 depicted in FIG. 3. The system operator may construct the selectable link labels by writing the customized HTML code necessary to construct the service guide menu 52. An alternative embodiment provides a graphical interface in the service guide server 48 (FIG. 2) to enable a system operator to graphically create the service guide menu 52 that is implemented by the DHCTs 16. From a multiplicity of services available on the cable system and shown in the graphical interface, the operator chooses and organizes into a list the services to be offered by the service guide 39 for all the DHCTs 16 in the network 20.


In an alternate embodiment, a user customizes his/her service guide display 52 by calling a telephone number that guides the user through a series of automated voice menus. The user enters account information and a personal identification number received from the cable service company and uses a brochure as a reference to make selections through an automated phone menu system.


In another alternate embodiment, the user accesses the Internet through a computer, PC, DHCT 16, or similar device and logs on to a specified secure and encrypted web site facilitated by the cable service company to select the set of services that the user desires in the service guide display. The user enters account information and a password or personal identification number to navigate through a set of menus and make customized selections that are routed from a secured web site to the service guide server 48.


In another alternate embodiment, the user configures the service guide menu 52 similarly in an interactive fashion by navigating through a series of menus generated by a configuration application (not shown) running in the DHCT 16 and presented on display 21. The user can re-customize his/her service guide preferences in the future by calling the automated phone menu system, logging on to the specified secure and encrypted web site, or through the configuration application running in the DHCT 16. Regardless of which method is utilized to create the service guide menu 52 in the service guide server 48, the information is communicated to the service guide client 39 executing on each DHCT 16 in the network 20 for display to the user.


The service guide 39, in the preferred embodiment, is communicated to the DHCT 16 when the DHCT 16 initializes as part of a power up sequence, but, in alternative embodiments, the service guide 39 could be a resident application in the DHCT 16 or could be downloaded to the DHCT 16 upon command by the user. The service guide client executable 39 is received from a broadcast file system (BFS) carousel that continually broadcasts it and the service guide HTML file(s) 52 across the network. This BFS system (not shown) provides a mechanism for delivering various types of media or data from a group of servers to a BFS client 41 in the operating system 33 for each DHCT 16. This data can contain practically any type of information. Applications on both the server and the client can access the data via the BFS in a similar manner to a file system found on disk operating systems. In an alternative embodiment, the HTML file(s) are retrieved via HTTP from the service guide server 48.


The service guide menu 52 (FIG. 3), as stated above, is comprised of multiple selectable link labels 56 that activate services and are, in the preferred embodiment, expressed in a customized version of HTML. In utilizing customized HTML (or XML) to create the service guide menu 52 (FIG. 3), several features may be implemented by the service guide 39. For example, the language of the textual display of the service guide menu 52 may be defined by the system operator by including the following HTML syntax: <html lang=“language-code”>. The “language-code” variable allows the service guide to be presented in various languages depending on the language code parameter (i.e., English (“en”), French (“fr”), Spanish (“es”)), etc.


The underlying link definition, or syntax, that comprises the selectable link labels 56 (FIG. 3) corresponding to the services provided by the DHCT 16 includes identification of the particular services, so that when one of the link labels 56 is selected by the user, the service guide 39 knows which service to activate. The underlying link definition may, for example, include in the reference a short description of the service. Consequently, the syntax, <A HREF=“tv://service/short_description”>, would reference the target service and the application that provides the service according to the short description assigned or corresponding to the target service. Similarly, the SAM service ID or the actual channel assigned to a desired service may also be used to activate a service. The syntax <A HREF=“tv://service/decimal_id”>, where the “decimal_id” is “10,” identifies the SAM service with the service ID that is 10. Additionally, the syntax, <A HREF=“tv://channel/display_channel_number”>, where “display_channel_number” is equal to “3,” activates the service on the receiver's channel 3.


Examples of services that can be included in the service guide menu 52 include, but are not limited to, those provided by the following applications: watching TV, listening to digital music, impulse pay-per-view, interactive program guide, DHCT settings, E-mail, video-on-demand, games-on-demand, videophone and/or conferencing, ticker tape data services, web browser, home banking, billing, calendar, calculator, context-sensitive help applications that display help text depending on the current channel service, downloading digital music into an MP3 device attached to the DHCT, uploading images from a digital camera attached to the DHCT, e-commerce, etc. In the preferred embodiment, any service available to the user in the cable system 10 can be accessed via the service guide menu 52, as configured by the system operator and/or in the respective alternate embodiments as configured by the user to reflect a user's own customization and preferences.


As discussed above, graphical icons and text representing the services can be included as part of the selectable link labels 56, as shown in 56a, 56b, and 56c. For example, the HTML link definition syntax <A HREF=“tv://service/ipg”><IMG SRC=“bfs://images/ipg_icon.jpg”>What's On</A> would be used to create the selectable link representation in 56a. This embodiment is shown in FIG. 3.


An alternative embodiment enables additional information about the selectable link labels to be incorporated in the link definition itself by specifying a title for the information to be displayed. As a non-limiting example, the link definition <A HREF=“tv://service/wnbc”TITLE=“information about the link”><IMG SRC=“tv://service/logo/215”></A> instructs the service guide 39 that additional information exists for this service and may be presented to the user in a variety of formats depending on the layout of the service guide menu 52. The “TITLE” attribute describes the object specified with the HREF attribute. If the service guide menu 52 is arranged in a horizontal toolbar format at the bottom of the screen (see FIG. 9), the information referenced by the “TITLE” attribute is displayed in a fixed location immediately above or below the row of buttons. Finally, if the service guide menu 52 is arranged in a vertical toolbar format at the left of the screen (as shown in FIG. 5), the “TITLE” information may appear in a window 57 to the right of each selectable link label 56 centered vertically with the link label 56.


If, as in one example, the title information for all selections is not already shown to the user upon initial presentation of the service guide menu 52, the information display about each selectable link label 56 may be accessed in several methods. As a non-limiting example, an information key on a remote device 27, such as the “INFO” key 72 (FIG. 6), may be configured to instruct the service guide application 39 to display the information corresponding to a selectable link label 56 as described above. As another non-limiting example, the service guide 39 may immediately present the information 57 (FIG. 5) about a selectable link label 56 after the user moves the cursor 58 on to the selectable link label 56 as described above. The presentation of the information 57 (FIG. 5) may be immediate or after a programmable timed delay set by the system operator to insure that the user is interested in the selectable link label 56 and not merely surfing between the plurality of selectable link labels 56. If the information is configured to display in a fixed portion of the screen display as described above, the service guide 39 may immediately present any available information referenced by the selectable link label 56 when the cursor 58 moves to a new selectable link label 56.


The underlying link definition for the selectable HTML link label 56 may additionally include information regarding activation of the target service in a specified screen state and location. As a non-limiting example, the selectable link definition <A HREF=“tv://channel/32”>NBC</A> uses the full screen in tuning to the channel that is assigned to the target service. Upon selection of the link label 56, for example, though not shown, corresponding to the link definition <A HREF=“tv://channel/13”>ABC</A> from the service guide 52 (FIG. 3), the service assigned to channel 13 is displayed in the full screen, and the service guide 52 and current TV program 59 are removed from view. As an additional non-limiting example, the link definition <A HREF=“tv://service/email”>E-mail</A> when activated causes the E-mail service to overlay on top of the current TV program 59 in full screen mode.


Some applications may be configured so that they are presented to the user in only a portion and/or relative spatial position of the display while another service or application is presented to the user in another location of the display 21. For example, a selectable link definition such as <A HREF=“tv://service/email;env=fullScreenObstructed (location)”>E-mail<A> (where location is a set of xmin, ymin, xmax, ymax coordinates) indicates to the service guide 39 that the E-mail service is to be activated in full screen obstructed mode and that the current TV program 59 is to be shown in a reduced location. A user is able to utilize the E-mail service while the DHCT 16 presents a current TV program 59 in a reduced screen portion of the display. Similarly, the selectable link label 56 in the service guide 52 may also specify activation of the target service in a reduced portion of the screen while retaining the current TV program 59 in the remaining portion of the display. For instance, a sport ticker tape may be designated to be displayed in the bottom of the TV display while a stock ticker tape may be designated to be displayed on the top. Thus, as a non-limiting example, the selectable link definition <A HREF=“tv://service/stocks;env=reducedScreen(location)”>Stock Ticker</A> instructs the service guide 39 (FIG. 2) to activate the stock ticker service with the stock ticker application's screen reduced to a specified portion of the screen as indicated by the “location” coordinates. The service guide 39 instructs the SAM 37 to activate the ticker application overlaid on the current TV program 59 (or any existing service on the current channel) when the user chooses this link label 56 from the service guide menu 52 (FIG. 3). In this manner, the target services may be activated in accordance to the selectable link labels 56 in the service guide menu 52 as configured by the system operator at the headend 11 of the network 20.


As discussed above, it is possible for the service guide menu 52 to include a link label 56 to a specific channel number accessible by the user. For example, the link definition <A HREF=“tv://channel/13”>ABC</A> can be included in the service guide content. When selected by the user, the service guide instructs the navigator to tune the DHCT to channel 3, thereby activating the service (i.e., ABC) defined for that channel.


The service guide menu 52 is additionally configurable to control the behavior and presence of the links based on the service authorization status of the DHCT 16. As a non-limiting example, the XML syntax <META UNAUTHORIZED=“display_mode”> in the header of the service guide customized HTML file, sets the display format of the link according to the level of authorization for the user. Service authorization information is available to the service guide via the SAM API. If the “display_mode” is “activeIfAlternative,” the link label 56 is selectable (shown active) even if the service is unauthorized as long as an alternate unauthorized service is available. Thus, the user may select the link label 56 to the target service, but the service guide 39 will activate the alternative service if the service specified in the service guide menu 52 is not authorized. Additional information regarding activation of alternative services to unauthorized services may be found in related U.S. patent application Ser. No. 09/542,484 filed Apr. 3, 2000, which is herein incorporated by reference in its entirety. If the “display_mode” is set to “inactive,” links to services that are not authorized for the DHCT 16 are displayed to the user in a “grayed out” format so that the user may see the link label 56 but may not select the link label 56 for activation of the underlying target service. Alternatively, unauthorized services may not be displayed at all. Alternatively, unauthorized services are coalesced into a service category such as “Other Purchasable Services” or “Other Available Services.”


Either the system operator of the cable television system or the user of the DHCT 16 may configure the display status of the link labels 56 with respect to authorization status of the target service. The system operator may designate the display status with respect to service authorization status for a link by a graphical user interface that graphically configures the service guide 39 XML/HTML code. The user, through a settings menu (not shown) may configure the service guide menu 52 so that the display mode of one or more selectable link labels 56 is “inactive” or “none” so the display of the selectable link label 56 conforms to the display modes described above.


The service guide menu 52 is additionally configurable to control the behavior and presence of the link labels 56 based on the parental control status of the DHCT as maintained by the navigator 35 application. As a non-limiting example, the syntax <META BLOCKED=display_mode”> in the header of the service guide customized HTML file directs the service guide 39 to set the display format of the link label 56 according to the level of parental control set by the user. Service parental control information is available to the service guide 39 via the navigator API. If the “display_mode” is “active,” the link label 56 is selectable (shown active) even if the service is blocked. Thus, the user may select the link label 56 to the target service, but the service guide will display a pop-up barker (not shown) indicating that the service is not available because it has been blocked by parental control. If the “display_mode” is set to “inactive,” links to services that are blocked by parental control are displayed to the user in a “grayed out” format so that the user may see the link label 56 but may not select the link label 56 for activation of the underlying target service. Finally, if the “display_mode” is set to “none,” links to services that are blocked by parental control are not included in the service guide menu 52.


Either the system operator of the cable television system or the user of the DHCT 16 may configure the display status of link labels 56 with respect to parental control status of the target service. The system operator may designate the display status with respect to service blocking status by a graphical user interface that graphically configures the service guide 39 HTML (or XML) code. More likely, the user, through a settings menu (not shown), may configure the service guide menu 52 so that the display mode of one or more link labels 56 is “inactive” or “none” so the display of the selectable graphic 56 conforms to the display modes described above. Alternatively, the user can configure the service guide menu 52 by calling the automated phone menu system, logging on to a specified secure and encrypted web site, or navigating through a configuration application running in the user's DHCT 16 as described above.


The service guide 52 may allow configurability by the user so as to include one or more favorite links so designated by the user to appear in the service guide menu 52. While the system operator may configure one or more selectable link labels 56 to always be presented in the service guide menu 52, the system operator may configure the service guide menu 52 to display selectable link labels 56 to services chosen by the user for incorporation in the service guide menu 52. As a non-limiting example, the system operator can include the syntax <A HREF=“tv://favorite/favorite_number”> whereby a user may choose to designate a frequently watched channel, such as ESPN, to appear on the service guide menu 52 through a settings display (not shown) so the user can quickly access the ESPN channel upon activating the service guide menu 52. The user may designate any channel or service as a favorite for inclusion in the service guide menu 52 for quick access. The user is limited to the number of favorite selectable link labels 56 as permitted by the system operator in configuring the service guide display, as specified in the “favorite_number” in the non-limiting example.


In an alternative embodiment, multiple favorite entries are allowed in the service guide menu 52 and the user is allowed to edit and rename the entry specifying a favorite set. Furthermore, any service included in a favorite set can appear in one or more favorite sets as the user desires.


In an alternative embodiment, selectable link labels 56 may be added to the service guide menu 52 by the service guide 39 itself for services most frequently activated by the user. The navigator 35 or other software in the DHCT 16 may be configured to tabulate the frequency of activation for services channels or applications and include one or more selectable link labels 56 for the most popular or frequently activated services. Thus, as a non-limiting example, the system operator can configure the service guide menu 52 to include one or more link labels 56 to frequently accessed services by specifying the syntax <A HREF=“tv://frequent/frequent_num”>. If a user frequently utilizes, for example, a Cyberdeli service (an interactive service supported by the DHCT 16, but not shown, for ordering delicatessen foods), the service guide 39 will include a selectable link label 56 referencing the Cyberdeli service in the service guide menu 52. Alternatively, the DHCT 16 may present the user the tabulated list of most frequently activated services for the user to choose which services to incorporate on the favorites list.


The display order and the number of most frequently activated services by the user may be programmed by the cable operator or alternatively configurable by the user during any of the user configuration sessions described above. In an alternate embodiment, the set of services most frequently activated by the user is displayed in the service guide menu 52 in chronological order from top to bottom. Alternatively, the displayed chronological order is from bottom to top. In yet another alternate embodiment, the finite set of services most frequently activated by the user is displayed in the service guide menu 52 in an order programmable as a function of both chronology and the amount of time of use of each service. For instance, a first service that was frequented fewer times than a second service within the past few days may be displayed with higher precedence in the display order or retained for a longer period of time in the set of most frequently activated services if the accumulated time usage of the first service is significantly higher than the second service over the same span of time.


The service guide menu 52 may be configured to additionally display a selectable link label 56 to services or channels in a time-specific manner. The service guide 39 may be configured to switch as time progresses from a first configurable service guide menu presentation to a second configurable service guide menu presentation according to a schedule that specifies the time interval when each of two or more respective service guide menu presentations is to be active. Two or more from a multiplicity of configurable service guide menu presentations are each configured to be active for one or more intervals of time in a recurring schedule. Only one configurable service guide menu is active at a time throughout the configurable recurring schedule but a first configurable service guide menu may be active throughout one or more distinct and non-overlapping time intervals of the configurable recurring schedule. The recurrence of the schedule is configured to one of a multiplicity of choices such as a weekly, daily, or a monthly recurring schedule.


In one embodiment, the system operator configures a multiplicity of time-adaptive service guide presentations for each of a multiplicity of recurring schedule choices. For instance, the system operator may configure six different arrangements to choose from for users that opt for a time-adaptive service guide on a daily recurring schedule. On the other hand, the system operator may configure more than six different arrangements to choose from for users that opt for a time-adaptive service guide on a weekly recurring schedule.


In another embodiment, in addition to having the choice of selecting one of a multiplicity of time-adaptive service guides pre-configured by the system operator, the user can additionally configure a time-adaptive service guide according to the user's preference for a user-selected recurring schedule from the set of recurring schedule choices. The user can enter the user's preferences through an interactive configuration session in the DHCT 16 or in alternate embodiments by calling the automated phone menu system or logging on to a specified secure and encrypted web site as described above.


In one embodiment, a time adaptive service guide 39 running a weekly recurring schedule may include selectable link labels 56 to, for example, news and financial programming for one or more specific time intervals (e.g., 7:30 to 8:00 A.M. and/or 11:00 to 11:30 PM for news; 1:00 to 5:00 PM for financial services) during weekdays. During weekends, the weekday selectable link labels 56 become inactive. Examples of selectable link labels for weekend days include sports programming (i.e., football on Sundays from 1:00 to 7:00 PM), videos-on-demand (i.e., Saturdays from 8:00 to 11:00 PM), or pizza delivery. This is accomplished by configuring the service guide server 48 to include different HTML files for each day, such that the service guide client 39 receives a different set of link labels 56 depending on the aforementioned time criteria.


A user may access the service guide menu 52 in several ways. FIG. 6 is a block diagram of a remote unit 27 with a dedicated key to access the service guide 39. The navigator 35 on the DHCT 16 may be configured to activate the service guide 39 to present the service guide menu 52 whenever the user presses the GUIDE key 71 on remote 27. The user may navigate the service guide menu 52 by pressing the arrow keys 74 to move the cursor 58 (FIG. 3) to the desired selectable link label 56 (FIG. 3) in the service guide menu 52. Once the user moves the cursor 58 to the desired target service or application, the user presses the SEL key 76 to select the selectable link label 56 corresponding to that target service. If the user desires to exit the service guide menu 52, the DHCT 16 may be configured to remove the service guide menu 61 and return to the current TV program 59 if the user presses the GUIDE key 71a second time or the EXIT key 78. It should be clear to one of ordinary skill that virtually any key on the remote 27 may be configured to activate the service guide application 39. It should also be obvious that remote 27 could be any type of corded or wireless remote or keyboard or other input devices. Other input commands can be received as signals in DHCT 16 by alternate means of receiving input, including voice signals and signals received via a communication port in DHCT 16.


The service guide 39 may also be activated by the user upon entering a channel input corresponding to the service guide service 39, as defined by the system operator. FIG. 7 is a diagram of the mappings of services to channels wherein the service guide menu 52 in FIG. 3 is mapped to a channel of the channel table 81. The system operator at the headend 11 configures the assignment of services to channels. The channel table 81 is a list of all channels in the cable television system, and the service table 82 is a list of all available services or applications provided by the cable television system. The system operator configures the channel line-up by setting the various channels in channel table 81 to point 83 to the various service or application in the service table 82. A channel in the channel table 81 may point 83a to the service guide service, provided by the service guide application 39, so that the service guide menu 52 is displayed whenever the user selects that channel. Thus, in a non-limiting example, the service guide menu 52 is presented to the user upon the DHCT 16 receiving a command to display channel 1. Consequently, the service guide menu 52 is presented if the user inputs a channel 1 command or merely scrolls through the channels and stops on channel 1.


When the service guide service is assigned to a channel, the layout of the service guide covers the entire screen, similar to that shown in FIG. 9 and discussed below, without the current channel area. This is done by configuring the navigator 35 to activate the service guide with a SAM service resource environment of the full screen, and the service guide HTML content would be formatted for the entire 640×480 screen resolution of the DHCT.



FIG. 8 is a screen display diagram of an interactive program guide (IPG) display 90 that provides access to the service guide menu 52 in FIG. 3. The IPG display 90 presents current and future viewable programs to the user in a scrollable format based on channel and time. The user may navigate the IPG display 90 to select a current program for immediate viewing. The IPG display 90 is a vertically scrollable list of channel numbers in a channel portion of the display 91 and a horizontally and vertically scrollable program listing display 93 of program services corresponding to the respective channels in the channel portion of the display 91. The user navigates a cursor 95 in the program listing display 93 to select the individual program or service for activation. The service guide menu 52, as shown in FIG. 3, may be activated by the user in similar fashion by moving the cursor 95 to the service guide program listing in the program listing display 93. In this non-limiting example, the service guide 39 is listed in the channel portion of the display 91 as channel 1, and the service guide menu 52 is activated by moving the cursor 95 to the service guide listing in the program listing display 93 and selecting the service guide menu 52 with the remote 27.



FIG. 9 is a screen display diagram of another example of the service guide menu 52 in a full screen format. Note that the selectable link labels 56 are arranged in horizontal format with the title information already displayed for each selectable link label 56. This is displayed upon selection of the service guide using a key on the remote as described previously. This is done by configuring the navigator 35 to activate the service guide 39 with a SAM service resource environment of the whole screen, and the service guide HTML content would be formatted for the entire 640×480 screen resolution of the DHCT. The current television program is displayed in ¼ screen section 55 by including an OBJECT with the SRC of “tv:” in the HTML content. The user may navigate the selectable link labels 56 of services 56 in the service guide menu 52 in similar fashion as described above.


An example of HTML code necessary to create the service guide 52 in full screen obstructed format as shown in FIG. 9 is as follows:

















<html lang=“en”>




<TABLE BGCOLOR=color TEXT=color HBGCOLOR=color




HTEXT=color>




<TR>




 <TD COLSPAN=2>




  <IMG SRC=“logo.jpg”>




 </TD>




 <TD COLSPAN=3>




  <OBJECT SRC=“tv:”>




 </TD>




</TR>




<TR>




 <TD>




  <A HREF=“tv://channel/901” TITLE=“WATCH TV”>




   <IMG SRC=“tv://service/logo/233”>




  </A>




 </TD>




 <TD>




  <A HREF=“tv://channe1/1001” TITLE=“PAY-PER-VIEW”>




   <IMG SRC=“tv://service/logo/278”>




  </A>




 </TD>




 <TD>




  <A HREF=“tv://service/501” TITLE=“VOD”>




   <IMG SRC=“tv://service/logo/33”>




  </A>




 </TD>




 <TD>




  <A HREF=“tv://service/1400;env=fullScreenObstructed( )”




  TITLE=“MUSIC”>




  <IMG SRC=“tv://service/logo/299”>




  </A>




 </TD>




</TR>




<TR>




 <TD>




  <A HREF=“tv://service/1201” TITLE=“E-MAIL”>




   <IMG SRC=“tv://service/logo/304”>




  </A>




 </TD>




 <TD>




  <A HREF=“tv://service/1202” TITLE=“WEB BROWSER”>




   <IMG SRC=“tv://service/logo/305”>




  </A>




 </TD>




 <TD>




  <A HREF=“tv://service/1203” TITLE=“CYBERDELI”>




   <IMG SRC=“tv://service/logo/306”>




  </A>




 </TD>




 <TD>




  <A HREF=“tv://service/1204” TITLE=“SETTINGS”>




   <IMG SRC=“tv://service/logo/307”>




  </A>




 </TD>




</TR>




</TABLE>




</html>









Alternatively, the <OBJECT src=“tv”> tag could be removed, and the navigator 35 could be configured to activate the service guide service in the fullScreenObstructed mode. This would also cause the current channel to be displayed in the specified obstructed rectangle, rather than determining the location based on the location of the “tv:” OBJECT in the service guide HTML content.



FIG. 10 is a screen display diagram of an alternative embodiment service guide presentation 90 for the user upon activating the service guide menu 52 from the IPG display 90. In this alternative embodiment, the service guide menu 52 is overlaid on the IPG display 90 for the user to navigate the selectable link labels 56. The IPG display 90 is shown dimmed by hatching provide emphasis on the service guide menu 52, but the IPG display 90 could also be dimmed of discolored from its original display format signify its background position. The user may exit the service guide menu by depressing the Exit key 78 (FIG. 6) to return to the IPG display 90. This view is shown to depict that the service guide menu may be presented to the user in a variety of formats and may be accessed by the user by a variety of methods.


The service guide 39, which comprises an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a nonexhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (magnetic), a read-only memory (ROM) (magnetic), an erasable programmable read-only memory (EPROM or Flash memory) (magnetic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). Note that the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory. Furthermore, any process descriptions or blocks in flow charts should be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.


It should be emphasized that the above-described embodiments of the present invention, particularly any “preferred embodiments” are merely possible examples of the implementations, merely set forth for a clear understanding of the principles of the invention. Any variations and modifications may be made to the above-described embodiments of the invention without departing substantially from the spirit of the principles of the invention. All such modifications and variations are intended to be included herein within the scope of the disclosure and present invention and protected by the following claims.

Claims
  • 1. A method, comprising: presenting for display at a display device a first service guide menu and a second service guide menu both with a plurality of hypertext links ordered according to at least in part a received specification, wherein the ordering provides at least in part that television programming services are displayed as hypertext links in the first service guide menu and non-television services are displayed as hypertext links in the second service guide menu, wherein the second service guide menu is overlaid on the first service guide menu, the second service menu configured to be presented for repeated occurrences of a first recurring predetermined time period upon expiration of a second recurring predetermined time period associated with the first service menu wherein both the television programming services and the non-television programming services are available during the first and second recurring predetermined time periods, and wherein the hypertext links in the first service guide menu become inactive during the first recurring predetermined time period;dimming the first service guide menu;receiving a user selection of a hypertext link; andactivating a service that corresponds to the selected hypertext link, wherein activating the service that corresponds to the selected hypertext link comprises utilizing additional information included in the selected hypertext link, wherein the additional information comprises a specified screen state and a service display location comprising a plurality of minimum and maximum coordinates.
  • 2. The method of claim 1, wherein the ordering is based at least in part on a frequency of activation of a service.
  • 3. The method of claim 1, wherein the ordering is based at least in part on usage by a user of a service.
  • 4. The method of claim 1, wherein the ordering is based on an amount of time of use of a service.
  • 5. The method of claim 1, wherein the dimming is performed by hatching the first service guide.
  • 6. The method of claim 1, wherein the ordering is based on a combination of an amount of time of use of a service and a frequency of activation of the service.
  • 7. The method of claim 1, further comprising the step of: displaying the first service guide menu upon expiration of a predetermined time period.
  • 8. The method of claim 7, wherein the predetermined time period corresponds to a weekday time period.
  • 9. The method of claim 7, wherein the predetermined time period corresponds to a recurring schedule.
  • 10. A system, comprising: a memory; and;a processor capable of performing steps stored in the memory, the steps comprising:presenting for display at a display device a first service guide menu and a second service guide menu both with a plurality of hypertext links ordered according to at least in part a received specification, wherein the ordering provides at least in part that television programming services are displayed as hypertext links in the first service guide menu and non-television service are displayed as hypertext links in the second service guide menu, wherein the second service guide menu is overlaid on the first service guide menu, the second service menu configured to be presented for repeated occurrences of a first recurring predetermined time period upon expiration of a second recurring predetermined time period associated with the first service menu wherein both the television programming services and the non-television programming services are available during the first and second recurring predetermined time periods, and wherein the hypertext links in the first service guide menu become inactive during the first recurring predetermined time period;dimming the first service guide menu;receiving a user selection of a hypertext link; andactivating a service that corresponds to the selected hypertext link, wherein activating the service that corresponds to the selected hypertext link comprises utilizing additional information included in the selected hypertext link, wherein the additional information comprises a specified screen state and a service display location comprising a plurality of minimum and maximum coordinates.
  • 11. A method comprising: receiving a specification;ordering a plurality of hypertext links based on the specification, wherein the ordering provides at least in part that television programming services are displayed as hypertext links in the first service guide menu and non-television services are displayed as hypertext links in the second service guide menu;displaying the first service guide menu and the second service guide menu upon user request, wherein the second service guide menu is overlaid on the first service guide menu, the second service menu configured to be presented for repeated occurrences of a first recurring predetermined time period upon expiration of a second recurring predetermined time period associated with the first service menu wherein both the television programming services and the non-television programming services are available during the first and second recurring predetermined time periods, and wherein the hypertext links in the first service guide menu become inactive during the first recurring predetermined time period;receiving a user selection of a hypertext link; andactivating the service that corresponds to the selected hypertext link, wherein activating the service that corresponds to the selected hypertext link comprises utilizing additional information included in the selected hypertext link, wherein the additional information comprises a specified screen state and a service display location comprising a plurality of minimum and maximum coordinates.
  • 12. The method of claim 11, wherein the non-television programming services comprise at least one of: an e-mail service, a video-on-demand service, and an e-commerce service.
  • 13. The method of claim 11, further comprising: presenting information about the one of the first or second hypertext links upon a user request.
  • 14. The method of claim 11, wherein, based on the specified screen state and the location, the selected service is displayed as an obstructed full screen on a display.
  • 15. The method of claim 14, wherein the full screen is obstructed by a currently displayed television programming service which is displayed in a reduced screen portion of the display.
  • 16. The method of claim 13, wherein the information is textual information including at least a title of a service associated with one of the first or second hypertext links.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/596,689, filed on Aug. 28, 2012 (now U.S. Pat. No. 8,739,212, Issued May 27, 2014), which is a continuation of U.S. patent application Ser. No. 10/957,849, filed on Oct. 4, 2004 (now U.S. Pat. No. 8,255,951, Issued Aug. 28, 2012), which is a divisional of U.S. patent application Ser. No. 09/565,931, filed on May 4, 2000 (now U.S. Pat. No. 7,934,232, Issued Apr. 26, 2011), each of which are incorporated by reference herein in their entirety.

US Referenced Citations (702)
Number Name Date Kind
3676580 Beck Jul 1972 A
4528643 Freeny Jul 1985 A
4586158 Brandle Apr 1986 A
4706121 Young Nov 1987 A
4751578 Reiter et al. Jun 1988 A
4821097 Robbins Apr 1989 A
4827250 Stallkamp May 1989 A
4885775 Lucas Dec 1989 A
4908713 Levine Mar 1990 A
4930158 Vogel May 1990 A
4949187 Cohen Aug 1990 A
4963994 Levine Oct 1990 A
4984152 Mueller Jan 1991 A
4991011 Johnson et al. Feb 1991 A
5038211 Hallenbeck Aug 1991 A
5172413 Bradley et al. Dec 1992 A
5191410 McCalley et al. Mar 1993 A
5253066 Vogel Oct 1993 A
5291554 Morales Mar 1994 A
5293357 Hallenbeck Mar 1994 A
5317391 Banker et al. May 1994 A
5329590 Pond Jul 1994 A
5353121 Young et al. Oct 1994 A
5357276 Banker et al. Oct 1994 A
5359362 Lewis et al. Oct 1994 A
5371551 Logan et al. Dec 1994 A
5398071 Gove et al. Mar 1995 A
5410326 Goldstein Apr 1995 A
5410343 Coddington et al. Apr 1995 A
5410344 Graves et al. Apr 1995 A
5414455 Hooper et al. May 1995 A
5418622 Takeuchi May 1995 A
5448313 Kim et al. Sep 1995 A
5461427 Duffield et al. Oct 1995 A
5465120 Schultheiss Nov 1995 A
5477262 Banker et al. Dec 1995 A
5479268 Young et al. Dec 1995 A
5481542 Logston et al. Jan 1996 A
5483277 Granger Jan 1996 A
5483278 Strubbe et al. Jan 1996 A
5485216 Lee Jan 1996 A
5493638 Hooper et al. Feb 1996 A
5508815 Levine Apr 1996 A
5512958 Rzeszewski Apr 1996 A
5515495 Ikemoto May 1996 A
5521631 Budow et al. May 1996 A
5524195 Clanton et al. Jun 1996 A
5530754 Garfinkle Jun 1996 A
5532735 Blahut et al. Jul 1996 A
5532754 Young et al. Jul 1996 A
5544354 May et al. Aug 1996 A
5555441 Haddad Sep 1996 A
5557541 Schulhof et al. Sep 1996 A
5562732 Eisenberg Oct 1996 A
5565908 Ahmad Oct 1996 A
5568181 Greenwood et al. Oct 1996 A
5568272 Levine Oct 1996 A
5568785 Hazen Oct 1996 A
5579055 Hamilton et al. Nov 1996 A
5583560 Florin et al. Dec 1996 A
5583995 Gardner et al. Dec 1996 A
5585821 Ishikura et al. Dec 1996 A
5585838 Lawler et al. Dec 1996 A
5589892 Knee et al. Dec 1996 A
5592551 Lett et al. Jan 1997 A
5594509 Florin et al. Jan 1997 A
5598524 Johnston, Jr. et al. Jan 1997 A
5600364 Hendricks et al. Feb 1997 A
5600573 Hendricks et al. Feb 1997 A
5604528 Edwards et al. Feb 1997 A
5614940 Cobbley et al. Mar 1997 A
5619247 Russo Apr 1997 A
5619249 Billock et al. Apr 1997 A
5621456 Florin et al. Apr 1997 A
5623613 Rowe et al. Apr 1997 A
5625405 DuLac et al. Apr 1997 A
5625864 Budow et al. Apr 1997 A
5629732 Moskowitz et al. May 1997 A
5629733 Youman et al. May 1997 A
5631693 Wunderlich et al. May 1997 A
5632681 Bakoglu et al. May 1997 A
5635979 Kostreski et al. Jun 1997 A
5635980 Lin et al. Jun 1997 A
5635989 Rothmuller Jun 1997 A
5650831 Farwell Jul 1997 A
5654747 Ottesen et al. Aug 1997 A
5659350 Hendricks et al. Aug 1997 A
5664133 Malamud Sep 1997 A
5666293 Metz et al. Sep 1997 A
5671411 Watts et al. Sep 1997 A
5675752 Scott et al. Oct 1997 A
5677905 Bigham et al. Oct 1997 A
5682206 Wehmeyer et al. Oct 1997 A
5682597 Ganek et al. Oct 1997 A
5684918 Abecassis Nov 1997 A
5686954 Yoshinobu et al. Nov 1997 A
5687331 Volk et al. Nov 1997 A
5689641 Ludwig et al. Nov 1997 A
5694163 Harrison Dec 1997 A
5694176 Bruette et al. Dec 1997 A
5694546 Reisman Dec 1997 A
5696905 Reimer et al. Dec 1997 A
5696906 Peters et al. Dec 1997 A
5699107 Lawler et al. Dec 1997 A
5710591 Bruno et al. Jan 1998 A
5715169 Noguchi Feb 1998 A
5715515 Akins, III et al. Feb 1998 A
5717468 Baryla Feb 1998 A
5721827 Logan et al. Feb 1998 A
5721829 Dunn et al. Feb 1998 A
5721897 Rubinstein Feb 1998 A
5724106 Autry et al. Mar 1998 A
5724521 Dedrick Mar 1998 A
5724646 Ganek et al. Mar 1998 A
5727060 Young Mar 1998 A
5729549 Kostreski et al. Mar 1998 A
5732216 Logan et al. Mar 1998 A
5734853 Hendricks et al. Mar 1998 A
5737028 Bertram et al. Apr 1998 A
5740304 Katsuyama et al. Apr 1998 A
5740549 Reilly et al. Apr 1998 A
5745837 Fuhrmann Apr 1998 A
5748493 Lightfoot et al. May 1998 A
5751282 Girard et al. May 1998 A
5752160 Dunn May 1998 A
5754773 Ozden et al. May 1998 A
5758257 Herz et al. May 1998 A
5764873 Magid et al. Jun 1998 A
5764899 Eggleston et al. Jun 1998 A
5771435 Brown Jun 1998 A
5774170 Hite et al. Jun 1998 A
5778077 Davidson Jul 1998 A
5790170 Suzuki Aug 1998 A
5790176 Craig Aug 1998 A
5790935 Payton Aug 1998 A
5790940 Laborde et al. Aug 1998 A
5796828 Tsukamoto et al. Aug 1998 A
5798785 Hendricks et al. Aug 1998 A
5799063 Krane Aug 1998 A
5801747 Bedard Sep 1998 A
5801787 Schein et al. Sep 1998 A
5802502 Gell et al. Sep 1998 A
5808608 Young et al. Sep 1998 A
5808611 Johnson et al. Sep 1998 A
5809204 Young et al. Sep 1998 A
5812123 Rowe et al. Sep 1998 A
5812124 Eick et al. Sep 1998 A
5812786 Seazholtz et al. Sep 1998 A
5822123 Davis et al. Oct 1998 A
5826102 Escobar et al. Oct 1998 A
5826110 Ozden et al. Oct 1998 A
5828419 Bruette et al. Oct 1998 A
5828845 Jagadish et al. Oct 1998 A
5835843 Haddad Nov 1998 A
5838314 Neel et al. Nov 1998 A
5844620 Coleman et al. Dec 1998 A
5848352 Dougherty et al. Dec 1998 A
5850218 LaJoie et al. Dec 1998 A
5856975 Rostoker et al. Jan 1999 A
5859641 Cave Jan 1999 A
5861881 Freeman et al. Jan 1999 A
5861906 Dunn et al. Jan 1999 A
5877755 Hallhake Mar 1999 A
5877756 Um Mar 1999 A
5880768 Lemmons et al. Mar 1999 A
5886690 Pond et al. Mar 1999 A
5886732 Humpleman Mar 1999 A
5895454 Harrington Apr 1999 A
5898456 Wahl Apr 1999 A
5900905 Shoff et al. May 1999 A
5905522 Lawler May 1999 A
5905865 Palmer et al. May 1999 A
5905942 Stoel et al. May 1999 A
5907323 Lawler et al. May 1999 A
5913040 Rakavy et al. Jun 1999 A
5914712 Sartain et al. Jun 1999 A
5914746 Matthews, III et al. Jun 1999 A
5915068 Levine Jun 1999 A
5917822 Lyles et al. Jun 1999 A
5929849 Kikinis Jul 1999 A
5930493 Ottesen et al. Jul 1999 A
5935206 Dixon et al. Aug 1999 A
5936659 Viswanathan Aug 1999 A
5940073 Klosterman et al. Aug 1999 A
5943047 Suzuki Aug 1999 A
5956024 Strickland et al. Sep 1999 A
5956716 Kenner et al. Sep 1999 A
5960411 Hartman et al. Sep 1999 A
5961603 Kunkel et al. Oct 1999 A
5969748 Casement et al. Oct 1999 A
5973685 Schaffa et al. Oct 1999 A
5978043 Blonstein et al. Nov 1999 A
5978381 Perlman et al. Nov 1999 A
5983273 White et al. Nov 1999 A
5986650 Ellis et al. Nov 1999 A
5987256 Wu et al. Nov 1999 A
5990881 Inoue et al. Nov 1999 A
5990890 Etheredge Nov 1999 A
5990927 Hendricks et al. Nov 1999 A
5995134 Hayashi Nov 1999 A
5996015 Day et al. Nov 1999 A
6002401 Baker Dec 1999 A
6005565 Legall et al. Dec 1999 A
6005631 Anderson et al. Dec 1999 A
6006257 Slezak Dec 1999 A
6008803 Rowe et al. Dec 1999 A
6008836 Bruck et al. Dec 1999 A
6014184 Knee et al. Jan 2000 A
6014694 Aharoni et al. Jan 2000 A
6014727 Creemer Jan 2000 A
6016348 Blatter et al. Jan 2000 A
6018359 Kermode Jan 2000 A
6018372 Etheredge Jan 2000 A
6020912 De Lang Feb 2000 A
6023267 Chapuis et al. Feb 2000 A
6025837 Matthews, III et al. Feb 2000 A
6025868 Russo Feb 2000 A
6025869 Stas et al. Feb 2000 A
6026376 Kenney Feb 2000 A
6034677 Noguchi et al. Mar 2000 A
6035281 Crosskey et al. Mar 2000 A
6037933 Blonstein et al. Mar 2000 A
6049831 Gardell et al. Apr 2000 A
6055571 Fulp et al. Apr 2000 A
6057872 Candelore May 2000 A
6061097 Satterfield May 2000 A
6064380 Swenson et al. May 2000 A
6064980 Jacobi et al. May 2000 A
6070186 Nishio May 2000 A
6072982 Haddad Jun 2000 A
6073105 Sutcliffe et al. Jun 2000 A
6075575 Schein et al. Jun 2000 A
6081263 LeGall et al. Jun 2000 A
6081830 Schindler Jun 2000 A
6085185 Matsuzawa et al. Jul 2000 A
6088455 Logan Jul 2000 A
6094680 Hokanson Jul 2000 A
6097383 Gaughan et al. Aug 2000 A
6098082 Gibbon et al. Aug 2000 A
6100883 Hoarty Aug 2000 A
6101512 DeRose et al. Aug 2000 A
6108002 Ishizaki Aug 2000 A
6108042 Adams et al. Aug 2000 A
6108706 Birdwell et al. Aug 2000 A
6118445 Nonomura et al. Sep 2000 A
6118498 Reitmeier Sep 2000 A
6118976 Arias et al. Sep 2000 A
6119163 Monteiro et al. Sep 2000 A
6124878 Adams et al. Sep 2000 A
6125259 Perlman Sep 2000 A
6130726 Darbee et al. Oct 2000 A
6133909 Schein et al. Oct 2000 A
6134572 Wolf et al. Oct 2000 A
6137539 Lownes et al. Oct 2000 A
6138139 Beck et al. Oct 2000 A
6141003 Chor et al. Oct 2000 A
6141488 Knudson et al. Oct 2000 A
6145083 Shaffer et al. Nov 2000 A
6148332 Brewer et al. Nov 2000 A
6151059 Schein et al. Nov 2000 A
6151688 Wipfel et al. Nov 2000 A
6157377 Shah-Nazaroff et al. Dec 2000 A
6157413 Hanafee et al. Dec 2000 A
6160545 Eyer et al. Dec 2000 A
6160546 Thompson et al. Dec 2000 A
6160989 Hendricks et al. Dec 2000 A
6163272 Goode et al. Dec 2000 A
6166730 Goode et al. Dec 2000 A
6166778 Yamamoto et al. Dec 2000 A
6169543 Wehmeyer Jan 2001 B1
6172674 Etheredge Jan 2001 B1
6172677 Stautner et al. Jan 2001 B1
6177931 Alexander et al. Jan 2001 B1
6181333 Chaney et al. Jan 2001 B1
6181693 Maresca Jan 2001 B1
6182287 Schneidewend et al. Jan 2001 B1
6184877 Dodson et al. Feb 2001 B1
6188684 Setoyama et al. Feb 2001 B1
6195689 Bahlmann Feb 2001 B1
6201536 Hendricks et al. Mar 2001 B1
6201540 Gallup et al. Mar 2001 B1
6205485 Kikinis Mar 2001 B1
6208335 Gordon et al. Mar 2001 B1
6209130 Rector et al. Mar 2001 B1
6216264 Maze et al. Apr 2001 B1
6233390 Yoneda May 2001 B1
6238290 Tarr et al. May 2001 B1
6239794 Yuen et al. May 2001 B1
6239845 Itagaki et al. May 2001 B1
6240555 Shoff et al. May 2001 B1
6243142 Mugura et al. Jun 2001 B1
6249532 Yoshikawa et al. Jun 2001 B1
6253375 Gordon et al. Jun 2001 B1
6259733 Kaye et al. Jul 2001 B1
6263501 Schein et al. Jul 2001 B1
6266814 Lemmons et al. Jul 2001 B1
6268849 Boyer et al. Jul 2001 B1
6272484 Martin et al. Aug 2001 B1
6275268 Ellis et al. Aug 2001 B1
6275506 Fazel et al. Aug 2001 B1
6275648 Knudson et al. Aug 2001 B1
6282713 Kitsukawa et al. Aug 2001 B1
6289346 Milewski et al. Sep 2001 B1
6289514 Link et al. Sep 2001 B1
6292624 Saib et al. Sep 2001 B1
6305019 Dyer et al. Oct 2001 B1
6305020 Hoarty et al. Oct 2001 B1
6311011 Kuroda Oct 2001 B1
6314572 LaRocca et al. Nov 2001 B1
6314573 Gordon et al. Nov 2001 B1
6314575 Billock et al. Nov 2001 B1
6317777 Skarbo et al. Nov 2001 B1
6317881 Shah-Nazaroff et al. Nov 2001 B1
6317885 Fries Nov 2001 B1
6323911 Schein et al. Nov 2001 B1
6324694 Watts et al. Nov 2001 B1
6326982 Wu et al. Dec 2001 B1
6327628 Anuff et al. Dec 2001 B1
6335936 Bossemeyer, Jr. et al. Jan 2002 B1
6347400 Ohkura et al. Feb 2002 B1
6349410 Lortz Feb 2002 B1
6353448 Scarborough et al. Mar 2002 B1
6357046 Thompson et al. Mar 2002 B1
6359636 Schindler et al. Mar 2002 B1
6360367 Yamamoto Mar 2002 B1
6362841 Nykanen Mar 2002 B1
6367078 Lasky Apr 2002 B1
6378130 Adams Apr 2002 B1
6381332 Glaab Apr 2002 B1
6385614 Vellandi May 2002 B1
6393585 Houha et al. May 2002 B1
6396549 Weber May 2002 B1
6397386 O'Conner et al. May 2002 B1
6400280 Osakabe Jun 2002 B1
6401243 Suzuki Jun 2002 B1
6405239 Addington et al. Jun 2002 B1
6408128 Abecassis Jun 2002 B1
6421067 Kamen et al. Jul 2002 B1
6429899 Nio et al. Aug 2002 B1
6434748 Shen et al. Aug 2002 B1
6441862 Yuen et al. Aug 2002 B1
6442332 Knudson et al. Aug 2002 B1
6442755 Lemmons et al. Aug 2002 B1
6442756 Durden et al. Aug 2002 B1
6446261 Rosser Sep 2002 B1
6446262 Malaure et al. Sep 2002 B1
6452611 Gerba et al. Sep 2002 B1
6460181 Donnelly Oct 2002 B1
6463585 Hendricks et al. Oct 2002 B1
6476833 Moshfeghi Nov 2002 B1
6480669 Tsumagari et al. Nov 2002 B1
6481010 Nishikawa et al. Nov 2002 B2
6481011 Lemmons Nov 2002 B1
6484318 Shioda et al. Nov 2002 B1
6486920 Arai et al. Nov 2002 B2
6501902 Wang Dec 2002 B1
6505348 Knowles et al. Jan 2003 B1
6507949 Jonason et al. Jan 2003 B1
6510556 Kusaba et al. Jan 2003 B1
6512552 Subramanian Jan 2003 B1
6515680 Hendricks et al. Feb 2003 B1
6515710 Koshimuta Feb 2003 B1
6518986 Mugura Feb 2003 B1
6519770 Ford Feb 2003 B2
6526575 McCoy et al. Feb 2003 B1
6526577 Knudson et al. Feb 2003 B1
6530083 Liebenow Mar 2003 B1
6532589 Proehl et al. Mar 2003 B1
6532593 Moroney Mar 2003 B1
6536041 Knudson et al. Mar 2003 B1
6539548 Hendricks et al. Mar 2003 B1
6543053 Li et al. Apr 2003 B1
6545669 Kinawi et al. Apr 2003 B1
6557030 Hoang Apr 2003 B1
6563515 Reynolds et al. May 2003 B1
6564005 Berstis May 2003 B1
6564378 Satterfield et al. May 2003 B1
6564379 Knudson et al. May 2003 B1
6564383 Combs et al. May 2003 B1
6571390 Dunn et al. May 2003 B1
6574793 Ngo et al. Jun 2003 B1
6578077 Rakoshitz et al. Jun 2003 B1
6578201 LaRocca et al. Jun 2003 B1
6594699 Sahai et al. Jul 2003 B1
6594825 Goldschmidt Iki et al. Jul 2003 B1
6594826 Rao et al. Jul 2003 B1
6600496 Wagner et al. Jul 2003 B1
6601103 Goldschmidt Iki et al. Jul 2003 B1
6604240 Ellis et al. Aug 2003 B2
6609253 Swix et al. Aug 2003 B1
6611958 Shintani et al. Aug 2003 B1
6614440 Bowen et al. Sep 2003 B1
6614988 Sampsell Sep 2003 B1
6628302 White et al. Sep 2003 B2
6631413 Aggarwal et al. Oct 2003 B1
6642939 Vallone et al. Nov 2003 B1
6647548 Lu et al. Nov 2003 B1
6651044 Stoneman Nov 2003 B1
6662365 Sullivan et al. Dec 2003 B1
6664984 Schlarb et al. Dec 2003 B2
6665869 Ellis et al. Dec 2003 B1
6671328 Poon et al. Dec 2003 B1
6675384 Block et al. Jan 2004 B1
6675385 Wang Jan 2004 B1
6675388 Beckmann et al. Jan 2004 B1
6678891 Wilcox et al. Jan 2004 B1
6681395 Nishi Jan 2004 B1
6681396 Bates et al. Jan 2004 B1
6684025 Perlman Jan 2004 B1
6684400 Goode et al. Jan 2004 B1
6690391 Proehl et al. Feb 2004 B1
6697376 Son et al. Feb 2004 B1
6698023 Levitan Feb 2004 B2
6701523 Hancock et al. Mar 2004 B1
6701528 Arsenault et al. Mar 2004 B1
6706311 Wong et al. Mar 2004 B2
6708336 Bruette Mar 2004 B1
6717590 Sullivan et al. Apr 2004 B1
6718552 Goode Apr 2004 B1
6721953 Bates et al. Apr 2004 B1
6725461 Dougherty et al. Apr 2004 B1
6731310 Craycroft et al. May 2004 B2
6732366 Russo May 2004 B1
6732367 Ellis et al. May 2004 B1
6732369 Schein et al. May 2004 B1
6732372 Tomita et al. May 2004 B2
6735572 Landesmann May 2004 B2
6738978 Hendricks et al. May 2004 B1
6738982 Jerding May 2004 B1
6754904 Cooper et al. Jun 2004 B1
6754906 Finseth et al. Jun 2004 B1
6757909 Maruo et al. Jun 2004 B1
6760918 Rodriguez et al. Jul 2004 B2
6769127 Bonomi et al. Jul 2004 B1
6771290 Hoyle Aug 2004 B1
6772209 Chernock et al. Aug 2004 B1
6772433 LaJoie et al. Aug 2004 B1
6782550 Cao Aug 2004 B1
6791620 Elswick et al. Sep 2004 B1
6792615 Rowe et al. Sep 2004 B1
6801533 Barkley Oct 2004 B1
6817028 Jerding et al. Nov 2004 B1
6832386 Jerding et al. Dec 2004 B1
6847969 Mathai et al. Jan 2005 B1
6876628 Howard et al. Apr 2005 B2
6898762 Ellis et al. May 2005 B2
6901385 Okamoto et al. May 2005 B2
6934964 Schaffer et al. Aug 2005 B1
6938258 Weinberger et al. Aug 2005 B1
6957386 Nishina et al. Oct 2005 B2
6968372 Thompson et al. Nov 2005 B1
6978310 Rodriguez et al. Dec 2005 B1
6978475 Kunin et al. Dec 2005 B1
6986156 Rodriguez et al. Jan 2006 B1
6987728 Deshpande Jan 2006 B2
6990676 Proehl et al. Jan 2006 B1
6990677 Pietraszak et al. Jan 2006 B1
6993782 Newberry et al. Jan 2006 B1
7010492 Bassett et al. Mar 2006 B1
7010801 Jerding et al. Mar 2006 B1
7024681 Fransman et al. Apr 2006 B1
7039944 Cho et al. May 2006 B1
7062466 Wagner et al. Jun 2006 B2
7065709 Ellis et al. Jun 2006 B2
7069575 Goode et al. Jun 2006 B1
7076734 Wolff et al. Jul 2006 B2
7086077 Giammaressi Aug 2006 B2
7103903 Kydd Sep 2006 B1
7103905 Novak Sep 2006 B2
7110714 Kay et al. Sep 2006 B1
7117440 Gordon et al. Oct 2006 B2
7120926 Safadi et al. Oct 2006 B1
7143430 Fingerman et al. Nov 2006 B1
7143432 Brooks et al. Nov 2006 B1
7150031 Rodriguez et al. Dec 2006 B1
7155733 Rodriguez et al. Dec 2006 B2
7168086 Carpenter et al. Jan 2007 B1
7180422 Milenkovic et al. Feb 2007 B2
7185355 Ellis et al. Feb 2007 B1
7188356 Miura et al. Mar 2007 B1
7194757 Fish et al. Mar 2007 B1
7200857 Rodriguez et al. Apr 2007 B1
7237251 Oz et al. Jun 2007 B1
7243364 Dunn et al. Jul 2007 B2
7246367 Livonen Jul 2007 B2
7249366 Flavin Jul 2007 B1
7324552 Galand et al. Jan 2008 B1
7324553 Varier et al. Jan 2008 B1
7334251 Rodriguez et al. Feb 2008 B2
7340759 Rodriguez Mar 2008 B1
7343614 Hendricks et al. Mar 2008 B1
7356477 Allan et al. Apr 2008 B1
7404200 Hailey et al. Jul 2008 B1
7496943 Goldberg et al. Feb 2009 B1
7496945 Rodriguez Feb 2009 B2
7509267 Yarmolich et al. Mar 2009 B1
7512964 Rodriguez et al. Mar 2009 B2
7526788 Rodriguez Apr 2009 B2
7535888 Carlucci et al. May 2009 B1
7647549 Denoual et al. Jan 2010 B2
7673314 Ellis et al. Mar 2010 B2
7685520 Rashkovskiy et al. Mar 2010 B2
7707614 Krikorian et al. Apr 2010 B2
7925534 Amano et al. Apr 2011 B2
7934232 Jerding et al. Apr 2011 B1
7961643 McDonald et al. Jun 2011 B2
7962370 Rodriguez et al. Jun 2011 B2
7975277 Jerding et al. Jul 2011 B1
7992163 Jerding et al. Aug 2011 B1
7992166 Jerding et al. Aug 2011 B2
8005713 Sanz-Pastor et al. Aug 2011 B1
8006262 Rodriguez et al. Aug 2011 B2
8006273 Rodriguez et al. Aug 2011 B2
8020184 Jerding et al. Sep 2011 B2
8032914 Rodriguez Oct 2011 B2
8037504 Jerding et al. Oct 2011 B2
8056106 Rodriguez et al. Nov 2011 B2
8069259 Rodriguez et al. Nov 2011 B2
8079047 Jerding et al. Dec 2011 B1
8161388 Rodriguez et al. Apr 2012 B2
8189472 McDonald et al. May 2012 B2
8191093 Rodriguez May 2012 B2
8255951 Jerding et al. Aug 2012 B2
8516525 Jerding et al. Aug 2013 B1
8621353 Schlarb et al. Dec 2013 B2
8640172 Rodriguez et al. Jan 2014 B2
8707153 Rodriguez et al. Apr 2014 B2
8745656 Rodriguez et al. Jun 2014 B2
20010003846 Rowe et al. Jun 2001 A1
20010013125 Kitsukawa et al. Aug 2001 A1
20010013127 Tomita et al. Aug 2001 A1
20010029523 Mcternan et al. Oct 2001 A1
20010030667 Kelts Oct 2001 A1
20010032293 Korst et al. Oct 2001 A1
20010032335 Jones Oct 2001 A1
20010034763 Jacobs et al. Oct 2001 A1
20010036271 Javed Nov 2001 A1
20010044744 Rhoads Nov 2001 A1
20010047517 Christopoulos et al. Nov 2001 A1
20020002642 Tyson et al. Jan 2002 A1
20020007485 Rodriguez et al. Jan 2002 A1
20020013836 Friedman et al. Jan 2002 A1
20020026496 Boyer et al. Feb 2002 A1
20020026638 Eldering et al. Feb 2002 A1
20020032638 Arora et al. Mar 2002 A1
20020032728 Sako et al. Mar 2002 A1
20020032905 Sherr et al. Mar 2002 A1
20020042913 Ellis et al. Apr 2002 A1
20020042920 Thomas et al. Apr 2002 A1
20020044762 Wood et al. Apr 2002 A1
20020049804 Rodriguez et al. Apr 2002 A1
20020049978 Rodriguez et al. Apr 2002 A1
20020056098 White May 2002 A1
20020056118 Hunter et al. May 2002 A1
20020057336 Gaul et al. May 2002 A1
20020062481 Slaney et al. May 2002 A1
20020069105 do Rosario Botelho Jun 2002 A1
20020069218 Sull et al. Jun 2002 A1
20020069412 Philips Jun 2002 A1
20020078176 Nomura et al. Jun 2002 A1
20020083443 Eldering et al. Jun 2002 A1
20020087981 Daniels Jul 2002 A1
20020101367 Geiger et al. Aug 2002 A1
20020104083 Hendricks et al. Aug 2002 A1
20020108125 Joao Aug 2002 A1
20020124249 Shintani et al. Sep 2002 A1
20020124255 Reichardt et al. Sep 2002 A1
20020128908 Levin et al. Sep 2002 A1
20020129362 Chang et al. Sep 2002 A1
20020138831 Wachtfogel et al. Sep 2002 A1
20020186957 Yuen Dec 2002 A1
20030002862 Rodriguez et al. Jan 2003 A1
20030014753 Beach et al. Jan 2003 A1
20030020744 Ellis et al. Jan 2003 A1
20030023971 Martinolich et al. Jan 2003 A1
20030030679 Jain Feb 2003 A1
20030031465 Blake Feb 2003 A1
20030037068 Thomas et al. Feb 2003 A1
20030037332 Chapin et al. Feb 2003 A1
20030040962 Lewis Feb 2003 A1
20030061619 Giammaressi Mar 2003 A1
20030067554 Klarfeld et al. Apr 2003 A1
20030074214 Kelliher Apr 2003 A1
20030074257 Saveliev et al. Apr 2003 A1
20030079224 Komar et al. Apr 2003 A1
20030079227 Knowles et al. Apr 2003 A1
20030088872 Maissel et al. May 2003 A1
20030101451 Bentolila et al. May 2003 A1
20030101454 Ozer et al. May 2003 A1
20030124973 Sie et al. Jul 2003 A1
20030126425 Yang et al. Jul 2003 A1
20030131356 Proehl et al. Jul 2003 A1
20030135853 Goldman et al. Jul 2003 A1
20030154475 Rodriguez et al. Aug 2003 A1
20030154486 Dunn et al. Aug 2003 A1
20030159147 Young et al. Aug 2003 A1
20030174243 Arbeiter et al. Sep 2003 A1
20030188313 Ellis et al. Oct 2003 A1
20030193486 Estrop Oct 2003 A1
20030206553 Surcouf et al. Nov 2003 A1
20030219228 Thiagarajan et al. Nov 2003 A1
20030221194 Thiagarajan et al. Nov 2003 A1
20040034867 Rashkovskiy et al. Feb 2004 A1
20040049787 Maissel et al. Mar 2004 A1
20040107436 Ishizaki Jun 2004 A1
20040117831 Ellis et al. Jun 2004 A1
20040128685 Hassell et al. Jul 2004 A1
20040133907 Rodriguez et al. Jul 2004 A1
20040163114 Rodriguez et al. Aug 2004 A1
20040163117 Rodriguez et al. Aug 2004 A1
20040168191 Jerding et al. Aug 2004 A1
20040181801 Hagen et al. Sep 2004 A1
20040221310 Herrington et al. Nov 2004 A1
20040261098 Macrae et al. Dec 2004 A1
20040261112 Hicks et al. Dec 2004 A1
20040261125 Ellis et al. Dec 2004 A1
20050005308 Logan et al. Jan 2005 A1
20050008074 van Beek et al. Jan 2005 A1
20050028190 Rodriguez et al. Feb 2005 A1
20050044565 Jerding et al. Feb 2005 A1
20050044566 Jerding et al. Feb 2005 A1
20050044577 Jerding et al. Feb 2005 A1
20050071882 Rodriguez et al. Mar 2005 A1
20050076360 Jerding et al. Apr 2005 A1
20050091693 Amine et al. Apr 2005 A1
20050111046 Kurumisawa et al. May 2005 A1
20050138657 Leftwich Jun 2005 A1
20050155056 Knee et al. Jul 2005 A1
20050160468 Rodriguez et al. Jul 2005 A1
20050188415 Riley Aug 2005 A1
20050204387 Knudson et al. Sep 2005 A1
20050204388 Knudson et al. Sep 2005 A1
20050213506 Wakumoto et al. Sep 2005 A1
20050216936 Knudson et al. Sep 2005 A1
20050235319 Carpenter et al. Oct 2005 A1
20050240961 Jerding et al. Oct 2005 A1
20050251822 Knowles et al. Nov 2005 A1
20050278741 Robarts et al. Dec 2005 A1
20050283797 Eldering et al. Dec 2005 A1
20050283810 Ellis et al. Dec 2005 A1
20050289618 Hardin Dec 2005 A1
20060020982 Jerding et al. Jan 2006 A1
20060026080 Rodriguez et al. Feb 2006 A1
20060026665 Rodriguez et al. Feb 2006 A1
20060059525 Jerding et al. Mar 2006 A1
20060070107 Renkis Mar 2006 A1
20060088105 Shen et al. Apr 2006 A1
20060112434 Banker et al. May 2006 A1
20060206913 Jerding et al. Sep 2006 A1
20060271933 Agassi et al. Nov 2006 A1
20060271964 Rodriguez et al. Nov 2006 A1
20060271973 Jerding et al. Nov 2006 A1
20070019670 Falardeau Jan 2007 A1
20070053293 McDonald et al. Mar 2007 A1
20070094690 Rodriguez et al. Apr 2007 A1
20070136748 Rodriguez et al. Jun 2007 A1
20070186240 Ward, III et al. Aug 2007 A1
20080010658 Abbott et al. Jan 2008 A1
20080046947 Katznelson Feb 2008 A1
20080098421 Rodriguez et al. Apr 2008 A1
20080098422 Rodriguez et al. Apr 2008 A1
20080101460 Rodriguez May 2008 A1
20080104637 Rodriguez et al. May 2008 A1
20080137755 Onur et al. Jun 2008 A1
20080155631 Liwerant et al. Jun 2008 A1
20080216111 Alten et al. Sep 2008 A1
20080229361 Jerding et al. Sep 2008 A1
20080279217 McDonald et al. Nov 2008 A1
20080281968 Rodriguez Nov 2008 A1
20080282307 McDonald et al. Nov 2008 A1
20080282308 McDonald et al. Nov 2008 A1
20090141794 Rodriguez et al. Jun 2009 A1
20090150946 Rodriguez et al. Jun 2009 A1
20090150957 Jerding et al. Jun 2009 A1
20090150958 Jerding et al. Jun 2009 A1
20090150959 Jerding et al. Jun 2009 A1
20090158306 Rodriguez et al. Jun 2009 A1
20090158324 Rodriguez et al. Jun 2009 A1
20090158329 Rodriguez et al. Jun 2009 A1
20090158331 Rodriguez et al. Jun 2009 A1
20090158332 Rodriguez et al. Jun 2009 A1
20090158335 Rodriguez et al. Jun 2009 A1
20090158339 Rodriguez et al. Jun 2009 A1
20090158352 Rodriguez et al. Jun 2009 A1
20090158354 Rodriguez et al. Jun 2009 A1
20090158355 Rodriguez et al. Jun 2009 A1
20090158363 Rodriguez et al. Jun 2009 A1
20090183081 Rodriguez et al. Jul 2009 A1
20090190028 Rodriguez et al. Jul 2009 A1
20090193468 Rodriguez Jul 2009 A1
20090193471 Rodriguez Jul 2009 A1
20090199249 Rodriguez et al. Aug 2009 A1
20090276808 Jerding et al. Nov 2009 A1
20090282372 Jerding et al. Nov 2009 A1
20090282440 Rodriguez Nov 2009 A1
20100242063 Slaney et al. Sep 2010 A1
20110279863 Chang et al. Nov 2011 A1
20120188445 Rodriguez et al. Jul 2012 A1
20120233654 McDonald et al. Sep 2012 A1
20120240147 Rodriguez Sep 2012 A1
20120324488 Jerding et al. Dec 2012 A1
20140282701 Rodriguez et al. Sep 2014 A1
Foreign Referenced Citations (102)
Number Date Country
2 363 052 Nov 1995 CA
2 223 025 Nov 2001 CA
2 475 723 Jan 2011 CA
2 408 289 Aug 2012 CA
0 572 090 Dec 1993 EP
0 673 159 Sep 1995 EP
0 680 214 Nov 1995 EP
0 725 538 Aug 1996 EP
0 763 936 Mar 1997 EP
0 811 939 Dec 1997 EP
0 838 915 Apr 1998 EP
0 849 948 Jun 1998 EP
0 854 645 Jul 1998 EP
0 891 084 Jan 1999 EP
0 896 318 Feb 1999 EP
0 909 095 Apr 1999 EP
0 701 756 Dec 1999 EP
0 989 751 Mar 2000 EP
1 052 644 Nov 2000 EP
1 069 801 Jan 2001 EP
1 075 143 Feb 2001 EP
1 113 668 Apr 2001 EP
1 111 572 Jun 2001 EP
1 161 085 Dec 2001 EP
2 343 051 Apr 2000 GB
8-289219 Nov 1996 JP
9-322022 Dec 1997 JP
10-143734 May 1998 JP
11-73361 Mar 1999 JP
11-73394 Mar 1999 JP
11-164284 Jun 1999 JP
2000-101941 Apr 2000 JP
2001 67786 Mar 2001 JP
WO 9222983 Dec 1992 WO
WO 9414284 Jun 1994 WO
9525799 Oct 1995 WO
WO 9617467 Jun 1996 WO
WO 9633579 Oct 1996 WO
WO 9634486 Oct 1996 WO
WO 9634491 Oct 1996 WO
9641470 Dec 1996 WO
WO 9641477 Dec 1996 WO
WO 9641478 Dec 1996 WO
WO 9734414 Sep 1997 WO
WO 9803012 Jan 1998 WO
WO 9826528 Jun 1998 WO
WO 9831116 Jul 1998 WO
WO 9837695 Aug 1998 WO
WO 9839893 Sep 1998 WO
WO 9847279 Oct 1998 WO
WO 9848566 Oct 1998 WO
WO 9856172 Dec 1998 WO
WO 9856173 Dec 1998 WO
WO 9856188 Dec 1998 WO
WO 9901984 Jan 1999 WO
WO 9904560 Jan 1999 WO
WO 9904561 Jan 1999 WO
WO 9912109 Mar 1999 WO
WO 9914947 Mar 1999 WO
WO 9935831 Jul 1999 WO
WO 9945701 Sep 1999 WO
WO 9949717 Oct 1999 WO
WO 9952285 Oct 1999 WO
WO 9957903 Nov 1999 WO
WO 9960790 Nov 1999 WO
9965237 Dec 1999 WO
WO 9966719 Dec 1999 WO
0001149 Jan 2000 WO
WO 0002385 Jan 2000 WO
WO 0004726 Jan 2000 WO
WO 0005889 Feb 2000 WO
WO 0030354 May 2000 WO
WO 0040017 Jul 2000 WO
WO 0046988 Aug 2000 WO
WO 0049801 Aug 2000 WO
0058967 Oct 2000 WO
WO 0059202 Oct 2000 WO
WO 0060482 Oct 2000 WO
WO 0078031 Dec 2000 WO
WO 0078045 Dec 2000 WO
WO 0078047 Dec 2000 WO
WO 0078048 Dec 2000 WO
WO 0106788 Jan 2001 WO
WO 0120907 Mar 2001 WO
WO 0124067 Apr 2001 WO
WO 0156273 Aug 2001 WO
WO 0167736 Sep 2001 WO
WO 0172042 Sep 2001 WO
WO 0176245 Oct 2001 WO
WO 0177888 Oct 2001 WO
WO 0184831 Nov 2001 WO
WO 02097584 Dec 2002 WO
WO 03003164 Jan 2003 WO
WO 03003709 Jan 2003 WO
WO 03014873 Feb 2003 WO
WO 03024084 Mar 2003 WO
WO 03042787 May 2003 WO
WO 03069898 Aug 2003 WO
WO 2004091219 Oct 2004 WO
WO 2004100500 Nov 2004 WO
WO 2005071658 Aug 2005 WO
WO 2007030370 Mar 2007 WO
Non-Patent Literature Citations (513)
Entry
U.S. Office Action mailed Jun. 27, 2014 in U.S. Appl. No. 13/482,689, 25 pgs.
U.S. Office Action mailed Sep. 22, 2014 in U.S. Appl. No. 13/482,689, 74 pgs.
EP Communication cited in Appln No. 02 794 161.6 mailed Apr. 2, 2009, 4 pgs.
EP Communication cited in Appln No. 02 794 161.6 mailed Oct. 22, 2009, 3 pgs.
PCT Search Report cited in International Application No. PCT/US02/37282 mailed Feb. 7, 2003, 4 pgs.
PCT International Search Report in Appln No. PCT/US02/14874 mailed Nov. 20, 2002, 4 pgs.
PCT Written Opinion in Appln No. PCT/US02/14874 mailed Feb. 11, 2003, 5 pgs.
EP Communication cited in Appln No. 02 736 739.0 mailed Oct. 13, 2009, 3 pgs.
EP Communication cited in Appln No. 02 736 739.0 mailed Jan. 17, 2012, 4 pgs.
Canadian Office Action mailed Oct. 2, 2012 in Appln No. 2,658,766, 2 pgs.
EP Communication mailed May 26, 2014 in Appln No. 02 782 347.5, 6 pgs.
EP Communication mailed Jun. 3, 2014 in Appln No. 03 745 157.2, 6 pgs.
U.S. Appl. No. 11/170,348, filed Jun. 29, 2005 entitled “Methods and Systems for Advertising During Video-on-Demand Suspensions”.
U.S. Appl. No. 11/460,516, filed Jul. 27, 2006 entitled “Video Promotional and Advertising Systems for Video on Demand System”.
U.S. Appl. No. 12/372,887, filed Feb. 18, 2009 entitled “Selection of Purchasable Enhancements of a Television Service”.
U.S. Appl. No. 09/330,792, filed Jun. 11, 1999 entitled “Series Reminders and Series Recording from an Interactive Television program Guide”.
U.S. Appl. No. 09/378,533, filed Aug. 20, 1999 entitled “Electronic Program Guide with Advance Notification”.
U.S. Appl. No. 09/518,041, filed Mar. 2, 2000 entitled “Apparatus and Method for Providing a Plurality of Interactive Program Guide Initial Arrangements”.
U.S. Appl. No. 09/542,484, filed Apr. 3, 2000 entitled “System for Providing Alternative Services”.
U.S. Appl. No. 09/565,931, filed May 4, 2000 entitled “Navigation Paradigm for Access to Television Services”.
U.S. Appl. No. 09/590,434, filed Jun. 9, 2000 entitled “Video Promotional and Advertising Systems for Video on Demand System”.
U.S. Appl. No. 09/590,488, filed Jun. 9, 2000 entitled “User Interface Navigational System with Parental Control for Video on Demand System”.
U.S. Appl. No. 09/590,521, filed Jun. 9, 2000 entitled “Systems and Methods for Adaptive Scheduling and Dynamic Bandwidth Resource Allocation Management in a Digital Broadband Delivery System”.
U.S. Appl. No. 09/590,904, filed Jun. 9, 2000 entitled “Program Information Searching System for Interactive Program Guide”.
U.S. Appl. No. 09/591,356, filed Jun. 9, 2000 entitled “Future Program Options Menu System for Interactive Program Guide”.
U.S. Appl. No. 09/692,920, filed Oct. 20, 2000 entitled “Media-on-Demand Title Indexing System”.
U.S. Appl. No. 09/692,995, filed Oct. 20, 2000 entitled “Media-on-Demand Bookmark System”.
U.S. Appl. No. 09/693,115, filed Oct. 20, 2000 entitled “Media Services Window Configuration System”.
U.S. Appl. No. 09/693,288, filed Oct. 20, 2000 entitled “Media-on-Demand Rental Duration Management System”.
U.S. Appl. No. 09/693,790, filed Oct. 20, 2000 entitled “Integrated Searching System for Interactive Media Guide”.
U.S. Appl. No. 10/957,849 filed Oct. 4, 2004, entitled “User Input for Access to Television Services”.
U.S. Appl. No. 10/957,854, filed Oct. 4, 2004, entitled “Menu Operation for Access to Television Services”.
U.S. Appl. No. 10/957,942, filed Oct. 4, 2004, entitled “Control Access to Television Services”.
U.S. Appl. No. 12/389,128, filed Feb. 19, 2009, entitled “Configuration of TV Services via Alternate Communication”.
“A Brief History of the Trailer,” http://www.movietrailertrash.com/views/history.html, 11 pages (Publicly known at least as early as Dec. 20, 2003).
Addington, Timothy H., “System Architecture Specification for Video-On-Demand Application Development on the Explorer 2000™ Digital Home Communications Terminal”, Revision 1.10r Review Copy (Mar. 4, 1999), 53 pages.
Alberico, G. et al., “Satellite Interactive Multimedia: A New Opportunity for Broadcasters,” International Broadcasting Convention, Conference Publication No. 447, pp. 18-23 (Sep. 12-16, 1997).
ATI Multimedia Center 7.9, User's Guide, ATI Technologies Inc., pp. i-vi and 1-96 (Copyright 2002).
Barth et al., “10 Fernsehen am PC”, Suse GMBH, XP-002324319, pp. 143-149 (2001).
“Client User Interface Specification (Phase I) for Video-On-Demand Application Development on the Explorer 2000™ Digital Home Communications Terminal”, Revision 1.10 (Aug. 31, 1998), 20 pages.
Cunningham et al., “5 Das X Window System”., Suse GMBH, XP-002324320, pp. 129-180 (2001).
Definition of “flag”, Microsoft Press: Computer User's Dictionary, 3 pages (1998).
Definition of “renting”, Webster's II: New College Dictionary, 1995, Houghton Mifflin Company, p. 939.
“Evidence of illustrative movie release years,” Retrieved from the Internet Movie Database using Internet, http://www.imdb.com, 19 pages (Retrieved on Jun. 6, 2005).
“Industry Leading Software Vendors Endorse BroadVision's Next Generation of Retail and Business-To-Business E-Commerce Application Solutions,” PR Newswire, Jun. 14, 1999, 4 pages.
“ISO/IEC 13818-6 Information technology—Generic coding of moving pictures and associated audio information—Part 6: Extensions for DSM-CC,” Chapter 4, 113 pp. (Sep. 1, 1998).
Kevin, “Change Screen Resolution in Windows (Tips, Tricks, Tweaks, and Setting),” http://www.tacktech.com/display.cfm?ttid=207, pp. 1-3 (Oct. 26, 2002).
Leftwitch et al., “StarSight Interactive Television Program Guide—Functional/International Architecture Specification Document, Interaction Analysis and Design Project—Phase III,” published no later than Dec. 15, 1995, 36 pages.
Little et al., “Prospects for Interactive Video-On-Demand”, IEEE Multimedia, IEEE Service Center, New York, NY US, vol. 1 No. 3, Sep. 1994, pp. 14-24, XP000476885 ISSN: 1070-986X.
McFedries, “The Complete Idiot's Guide to Windows 95,” Que, 2nd Edition, p. 49 (1997).
“Netcaster Developer's Guide,” Devedge Online Documentation, Netscape Communications Corporation, http://developer.netscape.com/docs/manuals/netcast/devguide/ index.html, XP-002166370, 82 pages (Sep. 25, 1997).
“Netscape Navigator Help,” Netscape Navigator Software User Documentation, Netscape Communications Corporation, http://home.netscape.com, XP-002166369, pp. 1-63 (Aug. 10, 1997).
Petit et al., “Bandwidth Resource Optimization in Video-On-Demand Network Architectures”, Community Networking Integrated Multimedia Services to the Home, 1994, Proceedings of the 1st International Workshop on San Francisco, CA USA, Jul. 1994, New York, NY USA, IEEE, Jul. 1994, pp. 91-97, XP010124402 ISBN: 978-0-7803-2076-5.
Reid, Dixie, “Coming attractions before they hit the big screen, most films begin life as a trailer,” The Sacramento Bee, Sacramento, California, p. E.1 (Jul. 18, 1996).
Remote Wonder, ATI, Tweak 3D, pp. 1-5 (Sep. 30, 2002).
Rottentomatoes web archived site, http://web.archive.org/web/20000301122211/http://rottentomatoes.com, Mar. 1, 2000, pp. 1-2.
“Sez You . . . origin of word daemon,” Take Our Word for It, Issue 146, p. 4, http://www.takeourword.com/TOW146/page4.html, 4 pgs. (retrieved on Apr. 4, 2006).
VESA Plug and Display Standard, Version 1, Video Electronics Standards Association, XP-002123075, 90 pages (Jun. 11, 1997).
W3C, Putting language attributes in HTML, www.w3.org.org/International/O-help-lang, 2 pages (Apr. 29, 1997).
BPAI Decision for U.S. Appl. No. 09/693,288, mailed Nov. 28, 2007, 5 pages.
BPAI Decision for U.S. Appl. No. 09/692,995, mailed Aug. 20, 2008, 10 pages.
Canadian Office Action cited in Application No. 2,376,556 mailed Sep. 30, 2008, 4 pages.
Canadian Office Action cited in Application No. 2,376,556 mailed Nov. 23, 2007, 3 pages.
Canadian Office Action cited in Application No. 2,376,556 mailed Dec. 6, 2005, 5 pages.
Canadian Office Action cited in Application No. 2,402,088 mailed Jun. 1, 2010, 3 pages.
Canadian Office Action cited in Application No. 2,402,088 mailed May 30, 2006, 2 pages.
Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 9, 2010, 5 pages.
Canadian Office Action cited in Application No. 2,405,491 mailed Apr. 3, 2009, 4 pages.
Canadian Office Action cited in Application No. 2,405,491 mailed May 22, 2008, 4 pages.
Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 20, 2007, 4 pages.
Canadian Office Action cited in Application No. 2,405,491 mailed Jan. 20, 2006, 3 pages.
Canadian Office Action cited in Application No. 2,408,289 mailed Sep. 2, 2010, 3 pages.
Canadian Office Action cited in Application No. 2,408,289 mailed Aug. 27, 2008, 4 pages.
Canadian Office Action cited in Application No. 2,408,289 mailed May 30, 2006, 2 pages.
Canadian Office Action cited in Application No. 2,451,477 mailed Nov. 3, 2009, 6 pages.
Canadian Office Action cited in Application No. 2,456,318 mailed Nov. 17, 2010, 4 pages.
Canadian Office Action cited in Application No. 2,456,318 mailed May 5, 2008, 3 pages.
Canadian Office Action cited in Application No. 2,456,318 mailed Mar. 27, 2007, 2 pages.
Canadian Office Action cited in Application No. 2,459,334 mailed Mar. 4, 2011, 3 pages.
Canadian Office Action cited in Application No. 2,466,667 mailed Apr. 15, 2009, 3 pages.
Canadian Office Action cited in Application No. 2,459,334 mailed Apr. 16, 2009, 3 pages.
Canadian Office Action cited in Application No. 2,475,723 mailed Jul. 7, 2009, 3 pages.
Canadian Office Action cited in Application No. 2,554,208 mailed Apr. 1, 2010, 4 pages.
Canadian Office Action cited in Application No. 2,621,605 mailed Dec. 15, 2009, 6 pages.
Canadian Office Action cited in Application No. 2,451,477 mailed Oct. 20, 2010, 4 pages.
Decision on Appeal affirmed cited in U.S. Appl. No. 09/590,434 mailed May 28, 2008, 10 pages.
European Examination Report cited in Application No. 00 938 251.6 mailed Mar. 2, 2010, 8 pages.
European Examination Report cited in Application No. 00 938 251.6 mailed Nov. 2, 2007, 7 pages.
European Examination Report cited in Application No. 00 939 759.7 mailed May 10, 2007, 6 pages.
European Examination Report cited in Application No. 01 905 058.2 mailed Dec. 19, 2006, 5 pages.
European Examination Report cited in Application No. 01 922 261.1 mailed Jul. 18, 2008, 5 pages.
European Examination Report cited in Application No. 01 922 261.1 mailed Nov. 2, 2007, 3 pages.
European Examination Report cited in Application No. 01 922 261.1 mailed Jan. 24, 2007, 5 pages.
European Examination Report cited in Application No. 01 922 261.1 mailed May 26, 2006, 4 pages.
European Examination Report cited in Application No. 01 923 092.9 mailed Jul. 20, 2009, 6 pages.
European Examination Report cited in Application No. 01 923 092.9 mailed Nov. 27, 2008, 6 pages.
European Examination Report cited in Application No. 01 937 209.3 mailed Mar. 16, 2010, 3 pages.
European Examination Report cited in Application No. 01 937 209.3 mailed Jun. 23, 2008, 5 pages.
European Examination Report cited in Application No. 02 737 593.0 mailed May 6, 2009, 5 pages.
European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 4, 2008, 3 pages.
European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 28, 2007, 5 pages.
European Examination Report cited in Application No. 02 761 572.3 mailed Apr. 20, 2009, 5 pages.
European Examination Report cited in Application No. 02 761 572.3 mailed Sep. 22, 2008, 5 pages.
European Examination Report cited in Application No. 02 761 572.3 mailed Jan. 22, 2008, 4 pages.
European Examination Report cited in Application No. 02 761 572.3 mailed Aug. 29, 2007, 4 pages.
European Examination Report cited in Application No. 06 802 683.0 mailed Jun. 26, 2008, 3 pages.
Examiner's Answer to Appeal Brief cited in U.S. Appl. No. 09/590,488 mailed Jan. 11, 2008, 24 pages.
Japanese Office Action cited in Application No. 2001-581527 mailed Feb. 10, 2010, 7 pages.
Japanese Office Action cited in Application No. 2001-581527 mailed Sep. 8, 2009, 11 pages.
PCT Search Report cited in International Application No. PCT/US00/15952 mailed Jan. 16, 2001, 5 pages.
PCT Search Report cited in International Application No. PCT/US00/15963 mailed Sep. 1, 2000, 5 pages.
PCT Search Report cited in International Application No. PCT/US00/16000 mailed Oct. 2, 2000, 5 pages.
PCT Search Report cited in International Application No. PCT/US01/02490 mailed May 18, 2001, 6 pages.
PCT Search Report cited in International Application No. PCT/US01/06663 mailed Oct. 18, 2001, 5 pages.
PCT Search Report cited in International Application No. PCT/US01/10874 mailed Nov. 29, 2001, 5 pages.
PCT Search Report cited in International Application No. PCT/US01/14150 mailed Apr. 29, 2002, 7 pages.
PCT Search Report cited in International Application No. PCT/US02/20307 mailed Jan. 3, 2003, 4 pages.
PCT Search Report cited in International Application No. PCT/US02/20519 mailed Apr. 7, 2003, 5 pages.
PCT Search Report cited in International Application No. PCT/US02/24704 mailed Mar. 5, 2003, 4 pages.
PCT Search Report cited in International Application No. PCT/US02/28212 mailed Jan. 23, 2003, 4 pages.
PCT Search Report cited in International Application No. PCT/US02/36291 mailed May 23, 2003, 4 pages.
PCT Search Report cited in International Application No. PCT/US03/03391 mailed Jul. 14, 2003, 4 pages.
PCT Search Report and Written Opinion cited in International Application No. PCT/US2005/001812 mailed May 2, 2005, 15 pages.
PCT Search Report and Written Opinion cited in International Application No. PCT/US2006/033965 mailed Feb. 9, 2007, 15 pages.
PCT Written Opinion cited in International Application No. PCT/US00/15952 mailed Jul. 25, 2001, 4 pages.
PCT Written Opinion cited in International Application No. PCT/US00/15963 mailed Jun. 22, 2001, 3 pages.
PCT Written Opinion cited in International Application No. PCT/US00/16000 mailed Oct. 25, 2001, 4 pages.
PCT Written Opinion cited in International Application No. PCT/US01/02490 mailed Oct. 23, 2001, 3 pages.
PCT Written Opinion cited in International Application No. PCT/US01/06663 mailed Jan. 3, 2002, 6 pages.
PCT Written Opinion cited in International Application No. PCT/US01/10874 mailed Jun. 4, 2002, 4 pages.
PCT Written Opinion cited in International Application No. PCT/US01/14150 mailed Sep. 30, 2004, 6 pages.
PCT Written Opinion cited in International Application No. PCT/US02/20307 mailed Aug. 8, 2003, 5 pages.
PCT Written Opinion cited in International Application No. PCT/US02/20519 mailed Apr. 6, 2004, 7 pages.
PCT Written Opinion cited in International Application No. PCT/US02/24704 mailed Nov. 20, 2003, 4 pages.
PCT Written Opinion cited in International Application No. PCT/US02/28212 mailed Dec. 4, 2003, 4 pages.
Summons to attend oral proceedings in EP Application No. 01937209.3 mailed Mar. 21, 2011, 7 pages.
Reply Brief in U.S. Appl. No. 09/565,931 mailed on Sep. 17, 2007, 6 pages.
Summons to attend oral proceedings pursuant to Rule 115(1) EPC in European Application No. 02737593.0-1241 mailed May 28, 2010, 6 pages.
Supplementary European Search Report cited in European Application No. 02737593.0 mailed Mar. 3, 2009, 4 pages.
Supplementary European Search Report cited in European Application No. 02744705.1 mailed Feb. 19, 2010, 4 pages.
Supplementary European Search Report cited in European Application No. 02750416.6 mailed Jan. 2, 2007, 4 pages.
Supplementary European Search Report cited in European Application No. 02761572.3 mailed Mar. 20, 2007, 4 pages.
Supplementary European Search Report cited in European Application No. 02797096.1 mailed Oct. 14, 2005, 3 pages.
Supplementary European Search Report cited in European Application No. 03713364.2 mailed Jul. 6, 2005, 3 pages.
Canadian Office Action dated May 31, 2011 cited in Application No. 2,621,605, 2 pages.
Canadian Office Action dated Jul. 11, 2011 cited in Application No. 2,554,208, 4 pages.
European Office Action dated Oct. 10, 2011 cited in Application No. 02744705.1, 9 pages.
Canadian Office Action dated Oct. 17, 2011 cited in Application No. 2,402,088, 4 pages.
Summons to attend oral proceedings mailed Dec. 29, 2011 in Application No. 00939759.7, 9 pages.
Summons to attend oral proceedings mailed Jul. 31, 2012 in Application No. 02744705.1, 5 pages.
European Communication dated Nov. 14, 2012 in Application No. 09154377.7, 6 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Mar. 18, 2003, 17 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 21, 2003, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 23, 2003, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 10, 2003, 34 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 27, 2003, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Sep. 26, 2003, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Sep. 26, 2003, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Oct. 27, 2003, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Oct. 28, 2003, 30 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Dec. 5, 2003, 18 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 16, 2003, 9 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Dec. 18, 2003, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jan. 14, 2004, 9 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Feb. 9, 2004, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 11, 2004, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 26, 2004, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Apr. 1, 2004, 14 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Apr. 21, 2004, 34 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Apr. 22, 2004, 12 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Apr. 26, 2004, 24 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 10, 2004, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jun. 4, 2004, 20 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 7, 2004, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jun. 16, 2004, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 15, 2004, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jul. 26, 2004, 36 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Sep. 10, 2004, 22 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Oct. 6, 2004, 19 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Oct. 20, 2004, 25 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Oct. 21, 2004, 28 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Nov. 16, 2004, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 18, 2004, 13 pages.
U.S. Office Action cited in U.S. Appl. No. 09/693,784 mailed Dec. 1, 2004, 8 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Dec. 29, 2004, 30 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Dec. 29, 2004, 11 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 11, 2005, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jan. 25, 2005, 18 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 10, 2005, 9 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 22, 2005, 21 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 22, 2005, 12 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed May 3, 2005, 33 pages.
U.S. Office Action cited in U.S. Appl. No. 10/073,842 mailed Jun. 1, 2005, 10 pgs.
U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jun. 3, 2005, 41 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 17, 2005, 22 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 21, 2005, 25 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 23, 2005, all pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 30, 2005, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jun. 30, 2005, 21 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 1, 2005, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jul. 13, 2005, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 19, 2005, 17 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jul. 28, 2005, 22 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Aug. 23, 2005, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Sep. 15, 2005, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 21, 2005, 28 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Nov. 21, 2005, 20 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Dec. 1, 2005, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 20, 2005, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Dec. 20, 2005, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2005, 18 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 29, 2005, 30 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jan. 11, 2006, 25 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 24, 2006, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Jan. 26, 2006, 12 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Feb. 16, 2006, 26 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Mar. 15, 2006, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 21, 2006, 26 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Mar. 27, 2006, 19 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 4, 2006, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Apr. 13, 2006, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 11, 2006, 17 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed May 16, 2006, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed May 31, 2006, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jun. 15, 2006, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 16, 2006, 21 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 21, 2006, 25 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jul. 10, 2006, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 28, 2006, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Aug. 28, 2006, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Sep. 7, 2006, 23 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 8, 2006, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Sep. 14, 2006, 9 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Sep. 18, 2006, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Oct. 26, 2006, 15 pages.
U.S. Office Action cited in U.S. Appl. No. 10/008,429 mailed Oct. 31, 2006, 25 pgs.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Nov. 15, 2006, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 24, 2006, 24 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Dec. 1, 2006, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2006, 10 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 24, 2007, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Feb. 2, 2007, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 6, 2007, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Feb. 9, 2007, 7 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Feb. 27, 2007, 17 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 12, 2007, 17 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Mar. 26, 2007, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed May 22, 2007, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Apr. 19, 2007, 9 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 19, 2007, 12 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 14, 2007, 25 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jul. 18, 2007, 22 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jul. 24, 2007, 8 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jul. 26, 2007, 6 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 24, 2007, 14 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Sep. 13, 2007, 11 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Oct. 2, 2007, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Oct. 5, 2007, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Dec. 7, 2007, 20 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Dec. 31, 2007, 8 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Jan. 2, 2008, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jan. 10, 2008, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jan. 15, 2008, 11 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jan. 16, 2008, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jan. 17, 2008, 44 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Jan. 29, 2008, 8 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Feb. 25, 2008, 10 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Apr. 30, 2008, 12 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 30, 2008, 10 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed May 1, 2008, 11 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 11, 2008, 17 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Jun. 12, 2008, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jun. 13, 2008, 7 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jun. 17, 2008, 21 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 17, 2008, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Jun. 25, 2008, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jul. 7, 2008, 10 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jul. 22, 2008, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jul. 25, 2008, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jul. 25, 2008, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 31, 2008, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Aug. 6, 2008, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Aug. 7, 2008, 8 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Aug. 8, 2008, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 15, 2008, 21 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Sep. 17, 2008, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 18, 2008, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Sep. 19, 2008, 11 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Sep. 22, 2008, 22 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Oct. 2, 2008, 6 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Oct. 15, 2008, 12 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Oct. 31, 2008, 44 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 6, 2008, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Dec. 11, 2008, 22 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Dec. 19, 2008, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Dec. 22, 2008, 19 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 23, 2008, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 26, 2008, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jan. 14, 2009, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Jan. 23, 2009, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Feb. 4, 2009, 11 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Feb. 13, 2009, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Feb. 13, 2009, 18 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 9, 2009, 37 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Mar. 19, 2009, 25 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Mar. 19, 2009, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Apr. 1, 2009, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 7, 2009, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Apr. 10, 2009, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Apr. 15, 2009, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Apr. 30, 2009, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed May 28, 2009, 10 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 3, 2009, 21 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jun. 11, 2009, 19 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 26, 2009, 9 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Jun. 26, 2009, 19 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 14, 2009, 18 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 28, 2009, 14 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Jul. 29, 2009, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Aug. 21, 2009, 39 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Aug. 24, 2009, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 3, 2009, 25 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 4, 2009, 25 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Sep. 17, 2009, 12 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Sep. 17, 2009, 10 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Sep. 28, 2009, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 29, 2009, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Sep. 30, 2009, 10 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Oct. 16, 2009, 21 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Oct. 22, 2009, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,917 mailed Oct. 26, 2009, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,894 mailed Oct. 27, 2009, 6 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Oct. 28, 2009, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Nov. 10, 2009, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Nov. 17, 2009, 21 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 24, 2009, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Nov. 30, 2009, 14 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Dec. 1, 2009, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Dec. 15, 2009, 24 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Dec. 16, 2009, 25 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 23, 2009, 10 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,752 mailed Dec. 23, 2009, 13 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Jan. 4, 2010, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jan. 15, 2010, 26 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 21, 2010, 21 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Jan. 21, 2010, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Jan. 22, 2010, 30 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Feb. 1, 2010, 12 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Feb. 5, 2010, 12 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Mar. 2, 2010, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 16, 2010, 27 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Mar. 18, 2010, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Mar. 30, 2010, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Mar. 31, 2010, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 1, 2010, 19 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Apr. 14, 2010, 27 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Apr. 27, 2010, 10 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Apr. 28, 2010, 10 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed May 5, 2010, 21 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/372,917 mailed May 17, 2010, 19 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed May 28, 2010, 21 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Jun. 2, 2010, 14 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,942 mailed Jun. 8, 2010, 20 pp. (60374.0053USD3).
U.S. Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Jun. 10, 2010, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jun. 21, 2010, 22 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/180,416 mailed Jun. 25, 2010, 11 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Jun. 23, 2010, 28 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jun. 30, 2010, 22 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Jul. 6, 2010, 23 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,945 mailed Jul. 16, 2010, 16 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Jul. 20, 2010, 17 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Jul. 22, 2010, 22 pages.
U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Aug. 2, 2010, 22 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,951 mailed Aug. 2, 2010, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Aug. 18, 2010, 15 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Aug. 20, 2010, 27 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Aug. 23, 2010, 16 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Aug. 31, 2010, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,002 mailed Sep. 3, 2010, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/234,967 mailed Sep. 10, 2010, 10 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Sep. 14, 2010, 24 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,418 mailed Sep. 28, 2010, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,420 mailed Oct. 19, 2010, 12 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,422 mailed Oct. 20, 2010, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Oct. 26, 2010, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Oct. 27, 2010, 23 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Nov. 4, 2010, 10 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Nov. 9, 2010, 50 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,763 mailed Jan. 4, 2011, 18 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Jan. 21, 2011, 13 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Feb. 1, 2011, 33 pages.
U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 8, 2011, 28 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Mar. 17, 2011, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Apr. 12, 2011, 20 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Apr. 29, 2011, 11 pages.
U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed May 19, 2011, 15 pages.
U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 8, 2011, 26 pages.
U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Jun. 9, 2011, 14 pages.
U.S. Final Office Action mailed Jul. 19, 2011 in U.S. Appl. No. 11/162,345, 31 pgs.
Board of Patent Appeals and Interferences Decision mailed Aug. 8, 2011 in U.S. Appl. No. 09/518,041, 9 pgs.
U.S. Non-Final Office Action mailed Sep. 6, 2011 in U.S. Appl. No. 11/238,369, 22 pgs.
U.S Non-Final Office Action mailed Sep. 13, 2011 in U.S. Appl. No. 12/389,564, 16 pgs.
U.S. Non-Final Office Action mailed Sep. 27, 2011 in U.S. Appl. No. 12/413,686, 24 pgs.
U.S. Final Office Action mailed Nov. 10, 2011 in U.S. Appl. No. 10/934,253, 14 pgs.
U.S. Final Office Action mailed Jan. 24, 2012 in U.S. Appl. No. 11/238,369, 19 pgs.
U.S. Final Office Action mailed Apr. 16, 2012 in U.S. Appl. No. 12/413,686, 21 pgs.
U.S. Final Office Action mailed May 14, 2012 in U.S. Appl. No. 11/238,369, 16 pgs.
U.S. Appl. No. 12/372,952, filed Feb. 18, 2009 entitled “System and Method for Assessing Usage of Purchasable Enhancements of Television Services”.
U.S. Appl. No. 12/388,002, filed Feb. 18, 2009 entitled “System and Method for Providing Purchasable Enhancements of VOD Services”.
U.S. Appl. No. 12/372,776, filed Feb. 18, 2009 entitled “Configurable Options for Accessible On-Demand Information”.
U.S. Appl. No. 12/388,139, filed Feb. 18, 2009 entitled “Upgrading Access of Television Program Information with Optional Features”.
U.S. Appl. No. 12/372,803, filed Feb. 18, 2009 entitled “Management of Generic Service Enhancements for Television Services”.
U.S. Appl. No. 10/780,448, filed Feb. 13, 2004 entitled “System and Method for Expiration Reminders of Rentable Media Offerings”.
U.S. Appl. No. 09/494,209 filed Jan. 1, 2000 entitled “System and Method for Allowing a User to Quickly Navigate Within a Program Guide to an Established Point”.
U.S. Appl. No. 09/502,067 filed Feb. 10, 2000 entitled “Method and System for Identification of Pay-per-View Programming”.
U.S. Appl. No. 09/590,520, filed Jun. 9, 2000 entitled “Video on Deman System with Parameter-Controlled Bandwidth Deallocation”.
U.S. Appl. No. 09/590,518 filed Jun. 9, 2000 entitled “Catalog Management System for Video on Demand System”.
U.S. Appl. No. 09/693,784 filed Oct. 20, 2000 entitled “System and Method for Reminders of Upcoming Rentable Media Offerings”.
U.S. Appl. No. 09/693,780 filed Oct. 20, 2000 entitled “Sychronized Video-On-Demand Supplemental Commentary”.
U.S. Appl. No. 09/896,390 filed Jun. 29, 2001 entitled “System and Method for Archiving Multiple Downloaded Recordable Media Content”.
U.S. Appl. No. 09/896,331 filed Jun. 29, 2001 entitled “Method and Apparatus for Recordable Media Content Distribution”.
U.S. Appl. No. 14/166,460 filed Jan. 28, 2014 entitled “System and Method for Characterization of Purchasable and Recordable Media (PRM)”.
U.S. Appl. No. 10/008,429 filed Nov. 13, 2001 entitled “Graphic User Interface Alternate Download Options for Unavailable PRM Content”.
U.S. Appl. No. 13/438,511 filed Apr. 3, 2012 entitled “Determining Device That Performs Processing of Output Pictures ”.
Almeroth et al.; An Alternative Paradigm for Scalable On-Demand Applications: Evaluating and Deploying the Interactive multimedia Jukebox; 1999; I EEE; vol. 11; p. 658-672.
Law Office Computing, AportisDoc Mobile Edition 2.2, retrieved on Aug. 14, 2008 at http://www.lawofficecomputing.com/old—site/Reviewsdata/djO 1/aportisdoc.asp, 2 pgs.
Perlman et al.; a working Anti-Taping System for Cable Pay-Per-View; Aug. 1998; IEEE; vol. 35; 6 pgs.
Rousseau, “Synchronized Multimedia for the WWW.,” retrieved from http://www7.wwwconference.org/1833/com1833.htm on Nocember 21, 2013, 15 pages.
Wikipedia, Moxi, retrieved on Aug. 14, 2008 at http://en.wikipedia.orglwiki/Moxi, 8 pgs.
BPAI Decision for U.S. Appl. No. 09/896,231, mailed Nov. 6, 2007, 17 pgs.
Canadian Office Action mailed Apr. 11, 2013 in Application No. 2,402,088, 7 pages.
Canadian Office Action mailed Oct. 17, 2013 in Application No. 2,451,477, 3 pages.
U.S. Office Action cited in U.S. Appl. No. 09/590,521 mailed Apr. 9, 2001, 15 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,521 mailed Oct. 24, 2001, 19 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,521 mailed May 23, 2002, 19 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,521 mailed Aug. 28, 2002, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,521 mailed Feb. 26, 2003, 17 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/073,842 mailed Jun. 25, 2003, 16 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,521 mailed Aug. 6, 2003, 19 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Sep. 9, 2003, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,780 mailed Sep. 13, 2003, 16 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,784 mailed Sep. 25, 2003, 9 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/073,842 mailed Dec. 24, 2003, 9 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,780 mailed Jan. 9, 2004, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,521 mailed Jan. 21, 2004, 12 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Mar. 11, 2004, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,780 mailed May 6, 2004, 16 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/709,145 mailed Jul. 20, 2004, 14 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/073,842 mailed Aug. 2, 2004, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Sep. 23, 2004, 14 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,784 mailed Dec. 1, 2004, 8 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/780,448 mailed Dec. 29, 2004, 9 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,520 mailed Mar. 11, 2005, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Mar. 14, 2005, 15 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,780 mailed Apr. 20, 2005, 20 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/709,145 mailed Apr. 22, 2005, 21 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/780,448 mailed May 3, 2005, 7 pgs.
U.S. Office Action mailed Nov. 10, 2014 in U.S. Appl. No. 13/482,497, 73 pages.
U.S. Office Action mailed Nov. 20, 2014 in U.S. Appl. No. 14/294,624, 99 pages.
U.S. Office Action cited in U.S. Appl. No. 09/896,390 mailed Jun. 15, 2005, 7 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,784 mailed Aug. 12, 2005, 15 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,470 mailed Aug. 25, 2005, 21 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/780,448 mailed Oct. 13, 2005, 9 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,390 mailed Oct. 19, 2005, 15 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/709,145 mailed Nov. 2, 2005, 26 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,780 mailed Dec. 19, 2005, 17 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,470 mailed Feb. 1, 2006, 15 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,390 mailed Feb. 8, 2006, 14 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/008,429 mailed Apr. 4, 2006, 18 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,780 mailed Apr. 5, 2006, 25 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/073,842 mailed May 2, 2006, 9 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/693,780 mailed Jul. 7, 2006, 18 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/709,145 mailed Jul. 28, 2006, 25 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Aug. 14, 2006, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/073,842 mailed Sep. 5, 2006, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,470 mailed Sep. 6, 2006, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,390 mailed Oct. 23, 2006, 20 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/709,145 mailed Jan. 12, 2007, 27 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,470 mailed Feb. 27, 2007, 14 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/073,842 mailed Mar. 9, 2007, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/008,429 mailed May 3, 2007, 22 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,390 mailed May 21, 2007, 16 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Jun. 26, 2007, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/683,138 mailed Jul. 5, 2007, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,470 mailed Jul. 30, 2007, 17 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,390 mailed Nov. 5, 2007, 14 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/008,429 mailed Dec. 5, 2007, 23 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Dec. 14, 2007, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/683,138 mailed Dec. 28, 2007, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,390 mailed Apr. 9, 2008, 17 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/896,470 mailed Apr. 18, 2008, 14 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Jul. 23, 2008, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/683,138 mailed Aug. 7, 2008, 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/683,138 mailed Jan. 21, 2009 10 pgs.
U.S. Office Action cited in U.S. Appl. No. 09/590,518 mailed Jan. 23, 2009, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/683,138 mailed Jul. 6, 2009, 11 pgs.
U.S. Office Action cited in U.S. Appl. No. 12/372,898 mailed Oct. 27, 2009, 8 pgs.
U.S. Office Action cited in U.S. Appl. No. 12/372,905 mailed Oct. 27, 2009, 6 pgs.
U.S. Office Action cited in U.S. Appl. No. 10/683,138 mailed Jan. 27, 2010, 11 pgs.
U.S. Non-Final Office Action mailed May 30, 2012 in U.S. Appl. No. 10/740,138, 27 pgs.
U.S. Non-Final Office Action mailed Dec. 26, 2012 in U.S. Appl. No. 12/413,686, 9 pages.
U.S. Final Office Action mailed Apr. 19, 2013 in U.S. Appl. No. 10/740,138, 31 pages.
U.S. Non-Final Office Action mailed Jun. 5, 2013 in U.S. Appl. No. 11/678,653, 50 pages.
U.S. Non-Final Office Action mailed Jun. 19, 2013 in U.S. Appl. No. 10/934,253, 14 pages.
U.S. Final Office Action mailed Jun. 25, 2013 in U.S. Appl. No. 12/413,686, 10 pages.
U.S. Office Action mailed Feb. 26, 2014 in U.S. Appl. No. 13/482,689, 26 pages.
U.S. Office Action mailed Apr. 16, 2014 in U.S. Appl. No. 13/482,497, 16 pages.
U.S. Office Action mailed Nov. 27, 2015 in U.S. Appl. No. 14/294,624, 11 pages.
U.S. Office Action mailed Jan. 4, 2016 in U.S. Appl. No. 13/482,497, 22 pages.
U.S. Office Action mailed Feb. 1, 2016 in U.S. Appl. No. 13/438,511, 91 pages.
U.S. Office Action mailed Feb. 25, 2015 in U.S. Appl. No. 13/482,497, 20 pages.
U.S. Office Action mailed Aug. 14, 2015 in U.S. Appl. No. 14/294,624, 20 pages.
U.S. Final Office Action dated Apr. 4, 2016 in U.S. Appl. No. 14/294,624, 29 pgs.
Related Publications (1)
Number Date Country
20140282732 A1 Sep 2014 US
Divisions (1)
Number Date Country
Parent 09565931 May 2000 US
Child 10957849 US
Continuations (2)
Number Date Country
Parent 13596689 Aug 2012 US
Child 14287339 US
Parent 10957849 Oct 2004 US
Child 13596689 US