Source: http://www.google.com/patents/US8069259?dq=5,845,077
Timestamp: 2015-07-07 13:46:15
Document Index: 618753864

Matched Legal Cases: ['art 6', 'art 6', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 00', 'Application No. 00', 'Application No. 00', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 02', 'Application No. 02', 'Application No. 02', 'Application No. 02', 'Application No. 02', 'Application No. 02', 'Application No. 02', 'Application No. 06', 'Application No. 2001', 'Application No. 2001', 'Application No. 01937209', 'Application No. 02737593', 'Application No. 02737593', 'Application No. 02744705', 'Application No. 02750416', 'Application No. 02761572', 'Application No. 02797096', 'Application No. 03713364']

Patent US8069259 - Managing removal of media titles from a list - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsThe invention can be viewed as a system for providing media information to a user via an interactive media services client device coupled to a programmable television services server device. A method of the preferred embodiment of the present invention includes receiving user input and excluding one...http://www.google.com/patents/US8069259?utm_source=gb-gplus-sharePatent US8069259 - Managing removal of media titles from a listAdvanced Patent SearchPublication numberUS8069259 B2Publication typeGrantApplication numberUS 11/244,621Publication dateNov 29, 2011Filing dateOct 6, 2005Priority dateJun 9, 2000Also published asUS20060026665Publication number11244621, 244621, US 8069259 B2, US 8069259B2, US-B2-8069259, US8069259 B2, US8069259B2InventorsArturo A. Rodriguez, Robert O. Banker, Dean F. JerdingOriginal AssigneeRodriguez Arturo A, Banker Robert O, Jerding Dean FExport CitationBiBTeX, EndNote, RefManPatent Citations (102), Non-Patent Citations (375), Referenced by (3), Classifications (31), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetManaging removal of media titles from a list
US 8069259 B2Abstract
The invention can be viewed as a system for providing media information to a user via an interactive media services client device coupled to a programmable television services server device. A method of the preferred embodiment of the present invention includes receiving user input and excluding one or more media titles from a media title list based on the user input.
1. An interactive media services client device for providing a user with media information received from a programmable television services server device, said client device comprising:
memory for storing data, the memory further comprising media titles corresponding to a displayed media title list, the media title list having at least one of the media titles, each media title being displayed in a title area;
cause a title area containing a media title identified by user input to be removed from said media title list; and
provide the user with a list of removed media titles, the list of removed media titles comprising the identified and removed media title that is provided to the user in the list of removed media titles subsequent to its removal.
2. The interactive media services client device of claim 1, wherein the user input is transmitted via a remote control device.
3. The interactive media services client device of claim 1, wherein the media title identified by said user is highlighted.
4. The interactive media services client device of claim 1, wherein the media title identified by said user input is a video-on-demand media title.
5. The interactive media services client device of claim 1, wherein said media title list is displayed via a television.
6. A programmable television services server device for providing media information to a user via an interactive media services client device, said server device comprising:
memory for storing data, the memory further comprising media titles for populating a displayed media title list, the media title list having plural media titles from among the media titles, each media title of the plural media titles being displayed in a respective title area; and
a processor configured to cause a title area containing one of the plural media titles identified by user input to be removed from said media title list, said processor being further configured to provide the user with a list of removed media titles that includes the one of the plural media titles, the list of removed media titles provided to the user subsequent to the removal of the one of the plural media titles.
7. The programmable television services server device of claim 6, wherein the user input is transmitted via a remote control device.
8. The programmable television services server device of claim 6, wherein the media title identified by said user is highlighted.
9. The programmable television services server device of claim 6, wherein the media title identified by said user input is a video-on-demand media title.
10. The programmable television services server device of claim 6, wherein said media title list is displayed via a television.
11. A method for providing media information to a user via an interactive media services client device coupled to a programmable television services server device, said method comprising:
receiving user input selecting a filtering criterion, the filtering criterion displayed on a graphics user interface;
implementing a filtering function on a media title list based on the selected filtering criterion, the filtering function capable of filtering-in and filtering-out functionality;
presenting for display a plurality of title areas each containing respective media titles of a subset of the media title list, the displayed plurality based on said filtering criterion; and
providing the user with a displayed list of removed media titles, the removed media titles corresponding to those subject to the implemented filtering function.
12. The method of claim 11, wherein the media title is a media title that is received by the client device from the server device at a future time.
13. The method of claim 11, further comprising implementing in the future the filtering function exclusively on media titles added in the future to the plurality of title areas of the subset based on future selected filtering criterion.
14. The method of claim 11, further comprising implementing in the future the filtering function on the plurality of title areas of the subset based on future selected filtering criterion.
15. The method of claim 11, wherein the filtering criterion is selected from a displayed, pre-configured list of filtering criterion.
16. The method of claim 11, wherein said media title list contains video-on-demand media titles.
17. The method of claim 11, wherein said media title list is displayed via a television.
18. The method of claim 11, wherein said filtering criterion is selected from a group consisting of:
a release year, a movie classification, an actor/actress, a critic rating, a category, and a rental fee.
19. An interactive media services client device for providing a user with media information received from a programmable television services server device, said client device comprising:
memory for storing data, the memory further comprising media titles for a displayed media title list, each of the media titles being displayed in a respective title area; and
cause a title area containing at least one of the media titles to be deleted from said media title list;
store information identifying the deleted media title and a corresponding deletion duration in the memory; and
cause the deleted media title to be displayed based on the stored information.
20. The client device of claim 19, wherein the processor is further configured to cause the title area to be deleted based on user input that is transmitted via a remote control device.
21. The client device of claim 19, wherein the processor is further configured to cause the deleted media title to be displayed in a list adjacent to the media title list.
22. The client device of claim 19, wherein said media title list contains video-on-demand media titles.
23. The client device of claim 19, wherein said media title list is displayed via a television.
24. The client device of claim 19, wherein the processor is further configured to cause the deleted media title to be displayed in a window separate from the window in which the media title list is displayed.
25. A programmable television services server device for providing media information to a user via an interactive media services client device, said server device comprising:
memory for storing data, the memory further comprising media titles for populating a media title list, each media title being displayed in a respective title area; and
cause a title area containing a media title corresponding to a filtering criterion identified by user input to be excluded from said media title list; and
provide the user with a list of removed media titles.
26. The server device of claim 25, wherein the user input is transmitted via a remote control device.
27. The server device of claim 25, wherein the filtering criterion identified by said user is highlighted.
28. The server device of claim 25, wherein said media title list contains video-on-demand media titles.
29. The server device of claim 25, wherein said media title list is displayed via a television.
30. The server device of claim 25, wherein said filtering criterion is selected from a group consisting of:
31. The client device of claim 19, wherein said client device is a television set-top box.
32. The client device of claim 19, wherein data corresponding to said filtering criterion is stored in non-volatile memory.
33. The method of claim 11, wherein said filtering criterion is whether said user had previously been provided with a media presentation corresponding to said media title.
34. The method of claim 11, wherein said filtering criterion is a text string entered by said user.
35. The method of claim 34, further comprising comparing said text string to other text strings; and providing said user with alternative text string selections.
36. The method of claim 35, further comprising prompting said user to select a filtering criterion that corresponds to said text string.
37. The method of claim 35, further comprising prompting said user to select an alternative text string.
38. The method of claim 11, further comprising:
receiving user input identifying a second filtering criterion; and
excluding a media title that does not meet said second filtering criterion from said media title list.
39. The method of claim 11, wherein a video presentation identified by said media title is currently available to said user via said client device.
40. The method of claim 11, wherein a video presentation identified by said media title is not currently available to said user via said client device.
41. A media services system for providing media information to a user via an interactive media services client device coupled to a programmable media services server device, said system comprising:
memory having titles for display in a media title list, each media title being displayed in a title area; and
logic stored in said memory, said logic being configured to:
cause a title area containing a media title corresponding to a filtering criterion identified by user input to be excluded from a media title list; and
42. The system of claim 41, wherein each of a plurality of users provides user input identifying a filtering criterion.
43. The system of claim 42, wherein a plurality of filtering criteria corresponding to a plurality of users are stored in memory.
44. The system of claim 42, wherein each of said plurality of users is presented with a media title list.
45. The system of claim 41, wherein said filtering criterion is based on whether said user had previously been provided with a media presentation corresponding to said media title.
46. The system of claim 41, wherein said user input is a text string.
47. The system of claim 46, further comprising logic configured to cause said client device to prompt said user to select a filtering criterion that corresponds to said text string.
48. The system of claim 46, further comprising logic configured to cause said client device to prompt said user to select an alternative text string.
49. The system of claim 41, further comprising logic configured to cause a media title that does not meet a second filtering criterion identified by user input to be excluded from said media title list.
50. The system of claim 41, wherein a video presentation identified by said media title is currently available to said user via said client device.
51. The system of claim 41, wherein a video presentation identified by said media title is not currently available to said user via said client device. Description
This application is a continuation of application Ser. No. 09/692,986, filed Oct. 20, 2000 now U.S. Pat. No. 6,978,310, which is a continuation-in-part of application Ser. No. 09/590,488, filed on Jun. 9, 2000, which are entirely incorporated herein by reference.
This invention relates in general to television systems, and more particularly, to the field of media-on-demand.
With recent advances in digital transmission technology, cable television systems are now capable of providing much more than the traditional analog broadcast video. 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 available services. In addition to supporting traditional analog broadcast video functionality, digital HCTs (or “DHCTs”) now also support an increasing number of two-way digital services such as video-on-demand.
Typically, a DHCT is connected to a cable or satellite television network and includes 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 also 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.
DHCTs are capable of providing users with a very large number and variety of purchasable media rentals and/or non-purchasable on-demand media. Given the vast number of years that film and television studios have produced movies, television programs and audio programs, copious media titles can be offered for convenient on-demand viewing. As the number of available on-demand media increases, it can become inconvenient and time consuming for users to continually browse through unwanted media titles in order to find the ones that they like. Therefore there exists a need to make it easier and more convenient for users to browse through available media titles.
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 diagram of the headend 11 as depicted in FIG. 1.
FIG. 3 is a block diagram of a DHCT and related equipment, in accordance with one preferred embodiment of the present invention depicted in FIG. 1.
FIG. 4 is a remote control device that can be used to provide user input to the DHCT shown in FIG. 3.
FIG. 5 depicts an example title selection window that illustrates a media title list presented to the user by the DHCT of FIG. 3.
FIG. 6 depicts an example deletion confirmation window that is presented to a user after the user requests the deletion of a media title via the title selection window depicted in FIG. 5.
FIG. 7 depicts an alternative embodiment to the deletion confirmation window shown in FIG. 6.
FIG. 8 depicts an example window that illustrates the deletion of a media title from the media title list of FIG. 5.
FIG. 9 depicts an example window that illustrates the process of restoring a deleted media title to the media title list shown in FIG. 8 FIG. 10 depicts an example window that illustrates media filtering categories presented by the DHCT of FIG. 3.
FIG. 11 depicts an example windows that illustrates filtering criteria corresponding to a filtering category shown in the example window of FIG. 10.
FIG. 12 depicts an example window that illustrates the activation of a filtering criterion shown in example window of FIG. 11.
FIG. 13 depicts an example window that illustrates the de-activation of a filtering criterion shown in the example window of FIG. 12.
FIG. 14 depicts an alternative embodiment to the example window shown in FIG. 5, illustrating a media title list.
FIG. 15 depicts an alternative embodiment to the example window in FIG. 8, illustrating the deletion of a media title from the media title list shown in FIG. 14.
FIG. 16 depicts an example window that illustrates the process of restoring (undeleting) a deleted media title to the media title list shown in FIG. 15.
The present invention is generally implemented as part of a cable television system (CTS). Hence, an illustrative CTS 10 and its operation will be described initially. FIG. 1 shows a block diagram view of a CTS 10, which is generally a high quality, reliable and integrated network system that features video, audio, voice and data services to DHCT users. Although FIG. 1 depicts a high level view of a CTS 10, it should be appreciated that a plurality of cable television systems can tie together a plurality of regional networks into an integrated global network so that DHCT users can receive content provided from anywhere in the world.
The CTS 10 delivers broadcast video signals as digitally formatted signals in addition to delivering traditional broadcast analog video signals. Furthermore, the system can support one way broadcast services as well as both one-way data services and two-way media and data services. The two-way operation of the network allows for user interactivity with services, such as Pay-Per-View programming, Near Video-On-Demand (NVOD) programming according to any of several known NVOD implementation methods, View-on-Demand (VOD) programming (according to any of several known VOD implementation methods), and interactive applications, such as Internet connections and interactive media Guide (IMG) applications.
The CTS 10 also provides the interfaces, network control, transport control, session control, and servers to access content and services, and distributes content and services to DHCT users. As shown in FIG. 1, a typical CTS 10 comprises a headend 11, hubs 12, an HFC access network 17, and users' digital home communication terminals (DHCTs) 16. It should be appreciated that although a single component (e.g. a headend) is illustrated in FIG. 1, a CTS 10 can feature a plurality of any one of the illustrated components or may be configured with alternative embodiments for any one of the individual components or with yet other additional components not enumerated above. A content provider (not shown) transmits media content to a headend for further transmission to users downstream in the network.
Content provided by a content provider is communicated by the content provider to one or more headends 11. From those headends the content is then communicated over a communications network 18 that includes a plurality of HFC access networks 17 (only one HFC access network 17 is illustrated). The HFC access network 17 typically comprises a plurality of HFC nodes 13, each of which may serve a local geographical area. The hub 12 connects to the HFC node 13 through a fiber portion of the HFC access network 17. The HFC node 13 is connected to a tap 14 which is connected to a network interface unit (NIU) 15 which is connected to a DHCT 16. The NIU 15 is normally located at a user's property and provides a transparent interface between the HFC node 13 and the users' internal wiring. Coaxial cables are typically used to couple nodes 13, taps 14 and NIUs 15 because the electrical signals can be easily repeated with radio frequency (RF) amplifiers.
As the high-level operations of many of the functions of CTSs 10 are well known to those of skill in the art, further description of the overall CTS 10 of FIG. 1 will not be contained herein. It will be appreciated, however, that the CTS 10 shown in FIG. 1 is merely illustrative and should not be construed as implying any limitations upon the scope of the present invention.
FIG. 2 is a block diagram of portions of a headend 11 that is configured to provide media-on-demand (MOD) services in accordance with one embodiment of the present invention. MOD services include, among other things, video-on-demand (VOD) services and respective MOD information suitable to be presented to a user via display of an interactive media guide. MOD server application 19 and a plurality of other server applications 20 are connected to a digital network control system (DNCS) 23 via a high-speed network such as an Ethernet connection 32. The MOD server application 19 is responsible for reserving and configuring system resources needed to provide MOD services and for providing configuration and service data to an MOD client application 63 (FIG. 3), including MOD information comprising a catalog of titles available for on-demand viewing and/or on-demand rental by a user.
The DNCS 23 provides complete management, monitoring, and control of the network's elements and broadcast services provided to users. In one implementation, the DNCS 23 uses a data insertion multiplexer 29 and a data QAM 30 to insert in-band broadcast file system (BFS) data into an MPEG-2 transport stream that is broadcast and received via DHCT's communication interface 42 and tuner system 45. The DNCS 23 also contains a session manager 34 that uses Digital Storage Media Command and Control (DSMCC) protocol to set up and maintain MOD sessions. The session manager 34 processes user to network (U-N) session signaling messages, manages allocation of session-related network resources, supports network management operations, acts as a point of contact to the network for the DHCT's 16 in the network 18 to establish individual sessions, and supports MOD services by providing the signaling interface to establish, maintain and release client initiated exclusive sessions.
A service application manager (SAM) server 25 is a server component of a client-server pair of components, with the client component being located at the DHCT 16. Together, the client-server SAM components provide a system in which the user can access services, which are identified by an application to run and a parameter, such as particular data content, specific to that service. The client-server SAM components also manage the life cycle of the applications on the system, including the definition, activation, and suspension of services they provide and the downloading of the applications into the DHCT 16 as necessary.
Applications on both the headend 11 and the DHCT 16 can access the data stored in a broadcast file system (BFS) server 28 in a similar manner to a file system found on operating systems. The BFS server 28 is a part of a broadcast file system that has a counterpart BFS client module 43 (FIG. 3) in a DHCT 16 connected to the network 18. The BFS server 28 repeatedly sends data for applications on a data carousel (not shown) over a period of time in cyclical repeated fashion so that a DHCT 16 that is in need of reading any particular data file or parts thereof may receive it when requested by a user or one or more of its internal running processes.
A VOD content manager 21 is responsible for managing the content on the VOD content servers 22. The MOD server application 19 controls both the VOD content manager 21 and the VOD content servers 22 and utilizes them to help deliver the video and audio streams that make up VOD services. In one embodiment, an MOD content manager and MOD content servers (not shown) could run respectively in parallel to the VOD content manager 21 and VOD content servers 22 to manage other types of on-demand media content. In an alternate embodiment an MOD content manager replaces the VOD content manager 21 and the MOD content servers replaces the VOD content servers 22. The QAM modulators that comprise the QAM group 24 receive the MPEG-2 transport streams from the VOD content servers 22, convert them into encrypted RF signals at a specified frequency (channel), and transmit them to a DHCT 16 via the network 18.
The QPSK modem 26 is responsible for transporting the out-of-band IP (internet protocol) datagram traffic between the distribution headend 11 and a DHCT 16. Data from the QPSK modem 26 is routed by headend router 27 within the headend 11. The headend router 27 is also responsible for delivering upstream application traffic to the various server applications 19 & 20.
FIG. 3 is a block diagram illustrating a DHCT 16 that is coupled to a headend 11 and to a television 41. Some of the functionality performed by applications executed in the DHCT 16 (such as the MOD client application 63) may instead be performed at the headend 11 and vice versa. A DHCT 16 is typically situated at a user's residence or place of business and may be a stand alone unit or integrated into another device such as, for example, a television set or a personal computer. The DHCT 16 preferably includes a communications interface 42 for receiving signals (video, audio and/or other data) from the headend 11 through the network 18 and for providing any reverse information to the headend 11 through the network 18. The DHCT 16 further includes at least one processor 44 for controlling operations of the DHCT 16, an RF output system 48 for driving the television display 41, and a tuner system 45 for tuning into a particular television channel to be displayed and for sending and receiving various types of data or media from the headend 11. The tuner system 45 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, a receiver 46 receives externally-generated information, such as user inputs or commands from other devices.
The DHCT 16 may also include one or more wireless or wired interfaces, also called ports, for receiving and/or transmitting data to other devices. For instance, the DHCT 16 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 or keyboard that includes user-actuated buttons.
In one implementation, the DHCT 16 includes system memory 49, which includes flash memory 51 and dynamic random access memory (DRAM) 52, for storing various applications, modules and data for execution and use by the processor 44. Basic functionality of the DHCT 16 is provided by an operating system 53 that is primarily stored in flash memory 51. Among other things, the operating system 53 includes at least one resource manager 67 that provides an interface to resources of the DHCT 16 such as, for example, computing resources.
One or more programmed software applications, herein referred to as applications, are executed by utilizing the computing resources in the DHCT 16. Applications stored in flash memory 51 or DRAM 52 are executed by processor 44 (e.g., a central processing unit or digital signal processor) under the auspices of the operating system 53. Data required as input by an application is stored in DRAM 52 or flash memory 51 and read by processor 44 as need be during the course of the application's execution. Input data may be data stored in DRAM 52 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 at the time it was generated as a software application, in which case it is stored in flash memory 51. Data generated by an application is stored in DRAM 52 by processor 44 during the course of the application's execution. DRAM 52 also includes application memory 70 that various applications may use for storing and/or retrieving data.
An application referred to as navigator 55 is also resident in flash memory 51 for providing a navigation framework for services provided by the DHCT 16. The navigator 55 registers for and in some cases reserves certain user inputs related to navigational keys such as channel increment/decrement, last channel, favorite channel, etc. The client applications may be resident in flash memory 51 or downloaded into DRAM 52. The navigator 55 also provides users with television related menu options that correspond to DHCT functions such as, for example, providing an interactive program guide, blocking a channel or a group of channels from being displayed in a channel menu, and displaying a video-on-demand purchase list.
The flash memory 51 also contains a platform library 56. The platform library 56 is a collection of utilities useful to applications, such as a timer manager, a compression manager, a configuration manager, an HTML parser, a database manager, a widget toolkit, a string manager, and other utilities (not shown). These utilities are accessed by applications via application programming interfaces (APIs) as necessary so that each application does not have to contain these utilities. Two components of the platform library 56 that are shown in FIG. 3 are a window manager 59 and a service application manager (SAM) client 57.
The window manager 59 provides a mechanism for implementing the sharing of the screen regions and user input. The window manager 59 on the DHCT 16 is responsible for, as directed by one or more applications, implementing the creation, display, and de-allocation of the limited DHCT 16 screen resources. It allows multiple applications to share the screen by assigning ownership of screen regions, or windows. The window manager 59 also maintains, among other things, a user input registry 50 in DRAM 52 so that when a user enters a key or a command via the remote control device 80 or another input device such as a keyboard or mouse, the user input registry 50 is accessed to determine which of various applications running on the DHCT 16 should receive data corresponding to the input key and in which order. As an application is executed, it registers a request to receive certain user input keys or commands. When the user presses a key corresponding to one of the commands on the remote control device 80, the command is received by the receiver 46 and relayed to the processor 44. The processor 44 dispatches the event to the operating system 53 where it is forwarded to the window manager 59 which ultimately accesses the user input registry 50 and routes data corresponding to the incoming command to the appropriate application.
The SAM client 57 is a client component of a client-server pair of components, with the server component being located on the headend 11. A SAM database 60 in DRAM 52 includes a data structure of services and a data structure of channels that are created and updated by the headend 11. Many services can be defined using the same application component, with different parameters. Examples of services include, without limitation and in accordance with one implementation, presenting television programs (available through a WatchTV application 62), pay-per-view events (available through a PPV application 64), digital music (not shown), media-on-demand (available through an MOD application 63), and an interactive program guide. In general, the identification of a service includes the identification of an executable application that provides the service along with a set of application-dependent parameters that indicate to the application the service to be provided. As a non-limiting example, a service of presenting a television program could be executed with a set of parameters to view HBO or with a separate set of parameters to view CNN. Each association of the application component (tune video) and one parameter component (HBO or CNN) represents a particular service that has a unique service I.D. The SAM client 57 also interfaces with the resource manager 67, as discussed below, to control resources of the DHCT 16.
Application clients can also be downloaded into DRAM 52 at the request of the SAM client 57, typically in response to a request by the user or in response to a message from the headend. In this non-limiting example DRAM 52 contains a media-on-demand application (MOD) 63, an e-mail application 65, and a web browser application 66, among others (not shown). It should be clear 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. Furthermore, one or more DRAM based applications may, as an alternative embodiment, be resident in flash memory 51. These applications, and others provided by the cable system operator, are top level software entities on the network for providing services to the user.
In one implementation, applications executing on the DHCT 16 work with the navigator 55 by abiding by several guidelines. First, an application utilizes the SAM client 57 for the provision, activation, and suspension of services. Second, an application shares DHCT 16 resources with other applications and abides by the resource management policies of the SAM client 57, the operating system 53, and the DHCT 16. Third, an application handles situations where resources are only available with navigator 55 intervention. Fourth, when an application loses service authorization while providing a service, the application suspends the service via the SAM (the navigator 55 will reactivate an individual service application when it later becomes authorized). Finally, an application client is designed to not have access to certain user input keys reserved by the navigator (i.e., power, channel +/−, volume +/−, etc.).
The MOD client application 63 provides the user with lists of available media titles to choose from and with video presentations requested by the user. The MOD client application 63 provides video presentations to the user by engaging, preferably, in a direct two-way IP (Internet Protocol) connection with VOD content servers 22 (FIG. 2). The MOD client application 63 is also responsible for providing title deletion functionality as described below. In an alternative embodiment, the title deletion functionality is provided by a separate application that can be selectively aggregated to the MOD client application 63 for purposes of charging separately for that functionality.
An executable program or algorithm corresponding to an operating system (OS) component, or to a client platform component, or to a client application, or to respective parts thereof, can reside in and execute out of DRAM 52 and/or flash memory 51. Likewise, data inputted into or outputted from any executable program can reside in DRAM 52 or flash memory 51. Furthermore, an executable program or algorithm corresponding to an OS component, or to a client platform component, or to a client application, or to respective parts thereof, can reside in flash memory 51, or in a local storage device connected to DHCT 16 and be transferred into DRAM 52 for execution. Likewise, data input for an executable program can reside in flash memory 51 or a storage device and be transferred into DRAM 52 for use by an executable program or algorithm. In addition, data outputted by an executable program can be written into DRAM 52 by an executable program or algorithm and be transferred into flash memory 51 or into a storage device for storage purposes. The present invention is not limited by where or how data and/or applications are stored or retrieved.
Each of the above mentioned applications comprises executable instructions for implementing logical functions and 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 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 non-exhaustive 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) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), 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, and then stored in a computer memory.
FIG. 4 illustrates a non limiting example of a remote control device 80 that is used to provide user input to the DHCT 16. The arrow buttons 82 include an up arrow button 83, a down arrow button 84, a left arrow button 85, and a right arrow button 86 that are used to scroll through options and/or to highlight an option. The select button 87 may be used to select a currently highlighted option that is provided to the user. Other buttons that are available on the remote control device will be discussed further below. Many alternative methods of providing user input may be used including a remote control device with different buttons and/or button layouts, a keyboard device, a voice activated device, etc. The invention described herein is not limited by the type of device used to provide user input.
With continued reference to FIGS. 3 and 4 throughout the remaining figures, FIG. 5 depicts an example media title deletion window 100A. As with other window examples discussed below, processor 44 executes program instructions of MOD client application 63 that cause it to direct the window manager 59 to create window 100A via display data that is formatted for television 41. Processor 44 stores the display data or parts thereof in DRAM 52 (as necessary) and transfers the display data to a display output system such as RF output system 48 wherein display data is converted to respective television signals and transmitted to television 41. Of course, the scope of the invention also includes any other method of causing the described windows to appear to the user.
The example window 100A contains a top portion 101 that typically contains one or more headings and a bottom portion 102 that typically illustrates relevant buttons available on the remote control device 80. Media title list 107 contains media titles that are retrieved by MOD client application 63 from application memory 70. Information section 104 contains information related to a media title shown in a highlighted title area 109, which in this example is “Angela's Ashes” 105. Browsing symbol 103 suggests to the user that the user may use the up and down arrow buttons 83, 84 on the remote control device 80 to browse the media title list 107 and use the select button 87 to request the currently highlighted media title. For example the user may activate the down arrow button on the remote control device in order to cause the media title “Any Given Sunday” 108 to be displayed in the highlighted title area 109 and then activate the select button 87 in order to request the movie. In an alternative embodiment activating the up an down arrows on the remote control device 80 would result in shifting the highlighted title area rather than shifting the media title list. The user may delete the media title currently shown in the highlighted title area 109 from the media title list 107 by pressing the “D” button 88 on the remote control device 80. Instead of a single dedicated key in an input device to invoke the delete functionality, in an alternate embodiment, a combination of keys pressed simultaneously or in sequential order are designated for deleting a highlighted media title.
FIGS. 6 and 7 depict example confirmation windows 110A and 110B that serve as alternative intermediate confirmation steps prior to the implementation of a title deletion. This intermediate confirmation step ensures that the user wishes to delete the highlighted title from the media title list and reduces accidental deletions. Example window 110A prompts the user to either confirm the deletion by pressing the “D” button 88 or to cancel the deletion by pressing the “E” button 89. Example window 110B, on the other hand, prompts the user for input on whether the deletion is to be effective permanently (via the “D” button 88) or just during the current on-demand title selection session (via the “E” button 89). Information identifying a deleted media title and its corresponding deletion duration is stored in application memory 70, such as in a database, by MOD client application 63 in order prevent the deleted media title from being included in media title lists subsequently presented to the user, including after receiving additional title information from the MOD server application 19. A user may, however, undelete a media title by following the procedure illustrated further below.
FIG. 8 depicts an example window 100B illustrating the deletion of a media title from the media title list 107 (FIG. 5). Example window 100B is presented to the user after the user activates the “D” button 88 on the remote control device 80 while being presented with example window 100A and then confirms the deletion request by re-activating the “D” button 88 while being presented with a confirmation window (110A or 110B). The media title previously shown in the highlighted title area 109 is deleted and replaced by the next media title on the media title list 107 (FIG. 5). In this example, the title “Angela's Ashes” 105 (FIG. 5) is deleted and replaced with the title “Any Given Sunday” 108.
FIG. 9 depicts an example window 120 illustrating the process of undeleting a media title. Example window 120 is presented to the user after the user activates the “E” button 89 on the remote control device 80 while being presented with example window 110 (FIG. 8). The user can undelete a highlighted media title by activating the select button 87. Upon being undeleted, a media title will no longer be identified in application memory 70 as being deleted and will be shown in media title lists subsequently presented to the user.
FIG. 10 depicts an example window 130 illustrating media filtering categories. Example window 130 is presented to the user after the user activates the “F” button 90 on the remote control device 80. The filtering list 131 contains filtering categories, such as filtering category 132, and a highlighted filtering category area 133. A filtering category contains criteria that are used to remove or filter out media titles from media title lists that are presented to the user. Example filtering categories include release year (e.g. 1999), released after a year, released prior to a year, movie classification (such as comedy, drama, etc.), critic rating (such as one star, two star, etc.), movie rating (such as PG, PG-13, etc.), movies already viewed, and the cost of renting the movie. For example, in one implementation, the cost of renting a movie can be used as a filter to exclude movies that cost more than defined selectable amounts, and in another implementation, the user is able to enter the cost to use as the threshold. The user can use the remote control device 80 to select a desired media filtering category. Upon selection of a media filtering category, the user is presented with media filtering criteria falling under the selected media filtering category as illustrated in FIG. 11.
In an alternate embodiment, the MOD client application 63 comprises a text string matching sub-component that enables filtering based on text strings entered by the user for applicable filtering categories. For instance, the user can implement a filter to delete titles that feature a disliked leading actor or actress. Upon user selection of filter by leading actor/actress 134 in window 130, an intermediate window is displayed to the user for entering alphanumeric characters via an input device. In the absence of a keyboard, MOD client application causes display of a window comprising visual information for scrolling and selection of individual letters. A mapping of alphanumeric characters to input device keys can also be displayed to facilitate entering letters with the remote control device. Upon the user entering the name of a leading actor or actress, the media client application may proceed to verify correct name spelling by transmitting the input name to the MOD server. The MOD server sends an addressable message to DHCT 16 that gets input as data to MOD client application 63. The received message data from MOD server confirms the correct spelling, rectifies the spelling, or suggests close variants of the user-entered name. MOD client application 63 interprets the message data and presents it to the user. In the event that variants are displayed to the user, the user is prompted to select one of the displayed name variants or to cancel the filtering request.
In an alternate embodiment, a “filter in” function rather than a “filter out” function is implemented such that filter enactment causes those on-demand titles that do not match the filter's criteria to be removed from the media title list. Furthermore, when applicable, the function of a user-implemented filter can be selected by the user to function as a “filter in” or “filter out”. Some filters in the set of available filters may not feature user-selectable “filter in” or “filter out” functionality but merely may default to either a “filter in” or “filter out” function. In an alternate embodiment, the MOD client application enacts capabilities to the user to filter only existing titles in the current media title list, to filter only future title additions to the media title list, or both.
FIGS. 11 and 12 are example windows 140 & 150 respectively illustrating the activation of a filtering criterion. The filtering criteria list 141 contains filtering criteria, such as filtering criterion 142, and a highlighted filtering criterion area 143. The user can use the remote control device 80 to select a desired filtering criteria. In this example, the user can filter out media titles corresponding to media titles that have critic ratings below one star by activating the select button on the remote control device 80. Referring now to FIG. 12, once a highlighted criterion is selected by the user, it becomes activated and is displayed in an active filters list 144. Upon activation, the filtering criterion is stored by MOD client application 63 in application memory 70 and is used to filter out media titles that meet the activated filtering criterion from media title lists that are presented to the user. In this example, media titles with critic ratings of under one star will be filtered out from media title lists that are presented to the user. In one embodiment, new media titles that are subsequently received by MOD client application 63 from MOD server application 19 (FIG. 2) are filtered according to currently active filtering criteria so that they are not included in media title lists presented to the user.
FIG. 13 depicts an example window 160 illustrating the de-activation of a filtering criterion. Example window 160 is presented to the user upon the activation of the right arrow button on the remote control device 80 while being presented with example window 150 (FIG. 12). Once an activated filtering criterion is selected by the user from the active filters list 144, it becomes de-activated, is removed from the active filters list 144, and is added back to the filtering criteria list 141. Upon de-activation, a filtering criterion is deleted from application memory 70 and is no longer used by the MOD client application 63 to filter out media titles.
FIGS. 14 and 15 are example windows 170 and 180 respectively that illustrate an alternative embodiment to the media title deletion windows illustrated in FIGS. 5 and 8. In this embodiment, example window 170 is presented to the user after the user activates the “D” button 88 on the remote control device 80 while being presented with example window 100A (FIG. 5). The user may then activate the up and down arrow buttons 83, 84 on the remote control device 80 to browse the media title list 117 and the select button 87 to delete a currently highlighted media title from the media title list 171. Once a title is deleted from a media title list, it remains excluded from such list even after the list is presented to the user at a later time. The user may however restore a previously deleted title to the media title list from which it was deleted by following the procedure illustrated in FIG. 16. Referring now to FIG. 15, example window 180 is presented to the user after the user activates the select button 87 on the remote control device 80 while being presented with example window 170. The media title previously shown in the highlighted title area 172 is replaced by the next media title on the media title list 171 (FIG. 14) and is transferred to the deleted title list 173. In this example, the title “Angela's Ashes” 105 (FIG. 14) is replaced with the title “Any Given Sunday” 108 and is transferred to the deleted title list 173 as shown in FIG. 15.
FIG. 16 depicts an example window 190 illustrating the process of undeleting a media title. Example window 190 is presented to the user after the user activates the right arrow button 86 on the remote control device 80 while being presented with example window 180 (FIG. 15). The user can undelete a highlighted media title by activating the select button 87. Once undeleted, a media title will be included in media title lists subsequently presented to the user.
In another embodiments, MOD client application 63 features the capability of creating a plurality of title removal or fine-tuning sets, each set designated to respectively retain the title viewing preferences of each individual viewer or member of the family. A title viewing preference set may simply be named with a suffice or prefix number or letter that individual viewers appropriate under personal agreements between themselves, or the set may be named by a user inputting alphanumeric strings with an input device such as a keyboard or remote control device.
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 setting forth a clear understanding of the principles of the inventions. Many 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.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS3676580Jun 1, 1970Jul 11, 1972Video Information SystemsInterrogated transponder systemUS4586158Feb 22, 1983Apr 29, 1986International Business Machines Corp.Screen management systemUS4706121May 6, 1986Nov 10, 1987Patrick YoungTV schedule system and processUS4751578May 28, 1985Jun 14, 1988David P. GordonSystem for electronically controllably viewing on a television updateable television programming informationUS4821097Mar 5, 1987Apr 11, 1989General Instrument CorporationApparatus and method for providing digital audio on the sound carrier of a standard television signalUS4827250Oct 26, 1987May 2, 1989Tektronix, Inc.Graphics display system having data transform circuitUS4885775Sep 21, 1984Dec 5, 1989Scientific-Atlanta, Inc.Information display scheme for subscribers of a subscription television systemUS4908713Jun 29, 1988Mar 13, 1990Levine Michael RVCR ProgrammerUS4930158Aug 29, 1988May 29, 1990Vogel Peter SSelective video playing systemUS4949187Dec 16, 1988Aug 14, 1990Cohen Jason MVideo communications system having a remotely controlled central source of video and audio dataUS4963994Feb 23, 1990Oct 16, 1990Levine Michael RVCR programmerUS4984152Oct 6, 1987Jan 8, 1991Bell Communications Research, Inc.System for controlling computer processing utilizing a multifunctional cursor with decoupling of pointer and image functionalities in space and timeUS4991011Apr 20, 1989Feb 5, 1991Scientific-Atlanta, Inc.Interactive television terminal with programmable background audio or videoUS5038211Jul 5, 1989Aug 6, 1991The Superguide CorporationMethod and apparatus for transmitting and receiving television program informationUS5172413Dec 20, 1990Dec 15, 1992SasktelSecure hierarchial video delivery system and methodUS5191410Feb 5, 1991Mar 2, 1993Telaction CorporationInteractive multimedia presentation and communications systemUS5253066May 30, 1990Oct 12, 1993Vogel Peter STV recording and viewing control systemUS5291554Aug 19, 1992Mar 1, 1994Tv Answer, Inc.Shared-price custom video rentals via interactive TVUS5293357Sep 10, 1990Mar 8, 1994The Superguide CorporationMethod and apparatus for controlling a television program recording deviceUS5317391Nov 29, 1991May 31, 1994Scientific-Atlanta, Inc.Method and apparatus for providing message information to subscribers in a cable television systemUS5329590Jul 8, 1993Jul 12, 1994Uniden America CorporationAutomatic pay-per-view reception in a satellite receiverUS5353121Mar 19, 1993Oct 4, 1994Starsight Telecast, Inc.Television schedule systemUS5357276Dec 1, 1992Oct 18, 1994Scientific-Atlanta, Inc.Method of providing video on demand with VCR like functionsUS5359362Mar 30, 1993Oct 25, 1994Nec Usa, Inc.Videoconference system using a virtual camera imageUS5371551Oct 29, 1992Dec 6, 1994Logan; JamesTime delayed digital video system using concurrent recording and playbackUS5398071Nov 2, 1993Mar 14, 1995Texas Instruments IncorporatedFilm-to-video format detection for digital televisionUS5410326Dec 4, 1992Apr 25, 1995Goldstein; Steven W.Programmable remote control device for interacting with a plurality of remotely controlled devicesUS5410343Apr 2, 1993Apr 25, 1995Bell Atlantic Network Services, Inc.Video-on-demand services using public switched telephone networkUS5410344Sep 22, 1993Apr 25, 1995Arrowsmith Technologies, Inc.Apparatus and method of selecting video programs based on viewers' preferencesUS5414455Jul 7, 1993May 9, 1995Digital Equipment CorporationSegmented video on demand systemUS5418622Oct 27, 1993May 23, 1995Sony CorporationApparatus for recording and reproducing audio and video signals in accordance with a broadcast scheduleUS5448313Sep 15, 1994Sep 5, 1995Thomson Consumer Electronics, Inc.On/off control of a cable converter unit by a VCRUS5477262Nov 29, 1991Dec 19, 1995Scientific-Altanta, Inc.Method and apparatus for providing an on-screen user interface for a subscription television terminalUS5479268Feb 18, 1994Dec 26, 1995Starsight Telecast Inc.User interface for television schedule systemUS5481542Nov 10, 1993Jan 2, 1996Scientific-Atlanta, Inc.Interactive information services control systemUS5483277Dec 15, 1992Jan 9, 1996Alcatel Network SystemsSimplified set-top converter for broadband switched networkUS5485216Aug 11, 1994Jan 16, 1996Goldstar Co., Ltd.Video format conversion apparatus for high definition televisionUS5493638Oct 13, 1994Feb 20, 1996Digital Equipment CorporationRemote display of an image by transmitting compressed video frames representing back-ground and overlay portions thereofUS5508815Sep 13, 1995Apr 16, 1996Smart Vcr Limited PartnershipSchedule display system for video recorder programmingUS5512958Apr 29, 1994Apr 30, 1996Matsushita Electric Corporation Of AmericaSystem for controlling the effects of noise in television receiversUS5515495Sep 29, 1992May 7, 1996Kabushiki Kaisha ToshibaIcon display apparatusUS5521631May 25, 1994May 28, 1996Spectravision, Inc.Interactive digital video services system with store and forward capabilitiesUS5530754Aug 2, 1994Jun 25, 1996Garfinkle; NortonVideo on demandUS5532735Apr 29, 1994Jul 2, 1996At&T Corp.Method of advertisement selection for interactive serviceUS5532754Apr 11, 1994Jul 2, 1996Starsight Telecast Inc.Background television schedule systemUS5544354Jul 18, 1994Aug 6, 1996Ikonic Interactive, Inc.Multimedia matrix architecture user interfaceUS5555441Aug 2, 1994Sep 10, 1996Interim Design Inc.Interactive audiovisual distribution systemUS5557541Jul 21, 1994Sep 17, 1996Information Highway Media CorporationApparatus for distributing subscription and on-demand audio programmingUS5562732Sep 6, 1995Oct 8, 1996Eisenberg; Eric L.Hair graft support trayUS5568272Oct 20, 1995Oct 22, 1996Smart Vcr Limited PartnershipSchedule display system for video recorder programmingUS5583560Jun 22, 1993Dec 10, 1996Apple Computer, Inc.Method and apparatus for audio-visual interface for the selective display of listing information on a displayUS5583995Jan 30, 1995Dec 10, 1996Mrj, Inc.Apparatus and method for data storage and retrieval using bandwidth allocationUS5585821Dec 20, 1995Dec 17, 1996Hitachi Ltd.Apparatus and method for screen displayUS5585838May 5, 1995Dec 17, 1996Microsoft CorporationProgram time guideUS5589892Jun 7, 1995Dec 31, 1996Knee; Robert A.Electronic television program guide schedule system and method with data feed accessUS5592551Apr 19, 1994Jan 7, 1997Scientific-Atlanta, Inc.Method and apparatus for providing interactive electronic programming guideUS5594509Jun 22, 1993Jan 14, 1997Apple Computer, Inc.Method and apparatus for audio-visual interface for the display of multiple levels of information on a displayUS5598524Mar 3, 1993Jan 28, 1997Apple Computer, Inc.Method and apparatus for improved manipulation of data between an application program and the files system on a computer-controlled display systemUS5600364Dec 2, 1993Feb 4, 1997Discovery Communications, Inc.Network controller for cable television delivery systemsUS5600573Dec 2, 1994Feb 4, 1997Discovery Communications, Inc.Operations center with video storage for a television program packaging and delivery systemUS5614940Oct 21, 1994Mar 25, 1997Intel CorporationMethod and apparatus for providing broadcast information with indexingUS5619247Feb 24, 1995Apr 8, 1997Smart Vcr Limited PartnershipStored program pay-per-playUS5619249Sep 14, 1994Apr 8, 1997Time Warner Entertainment Company, L.P.Telecasting service for providing video programs on demand with an interactive interface for facilitating viewer selection of video programsUS5621456Jun 22, 1993Apr 15, 1997Apple Computer, Inc.Methods and apparatus for audio-visual interface for the display of multiple program categoriesUS5623613Nov 29, 1994Apr 22, 1997Microsoft CorporationSystem for displaying programming informationUS5625405Feb 20, 1996Apr 29, 1997At&T Global Information Solutions CompanyArchitectural arrangement for a video serverUS5625864Jun 30, 1995Apr 29, 1997Budow; Harry S.Interactive digital video services system with store and forward capabilitiesUS5629732Mar 29, 1994May 13, 1997The Trustees Of Columbia University In The City Of New YorkViewer controllable on-demand multimedia serviceUS5631693Oct 25, 1993May 20, 1997Antec CorporationMethod and apparatus for providing on demand services in a subscriber systemUS5632681Mar 7, 1995May 27, 1997International Business Machines CorporationUniversal electronic video game renting/distributing systemUS5635979May 27, 1994Jun 3, 1997Bell AtlanticDynamically programmable digital entertainment terminal using downloaded software to control broadband data operationsUS5635980Apr 4, 1995Jun 3, 1997Bell Communications Research, Inc.System and method for customer premises broadband interface with on-hook alertingUS5635989Feb 13, 1996Jun 3, 1997Hughes ElectronicsMethod and apparatus for sorting and searching a television program guideUS5650831Jul 17, 1995Jul 22, 1997Gateway 2000, Inc.Adjustable power remote control driveUS5659350Dec 2, 1993Aug 19, 1997Discovery Communications, Inc.Operations center for a television program packaging and delivery systemUS5664133Apr 30, 1996Sep 2, 1997Microsoft CorporationContext sensitive menu system/menu behaviorUS5666293Jul 3, 1995Sep 9, 1997Bell Atlantic Network Services, Inc.Downloading operating system software through a broadcast channelUS5671411Jun 7, 1995Sep 23, 1997Intel CorporationMethod of searching an audio/visual programming database using selected criterion having implicit logical operationUS5675752Sep 15, 1994Oct 7, 1997Sony CorporationInteractive applications generator for an interactive presentation environmentUS5682206Sep 25, 1995Oct 28, 1997Thomson Consumer Electronics, Inc.Consumer interface for programming deviceUS5682597Jun 15, 1995Oct 28, 1997International Business Machines CorporationHybrid video-on-demand based on a near-video-on-demand systemUS5684918Sep 8, 1994Nov 4, 1997Abecassis; MaxSystem for integrating video and communicationsUS5686954Jun 6, 1995Nov 11, 1997Sony CorporationProgram information broadcasting method program information display method, and receiving deviceUS5687331Aug 3, 1995Nov 11, 1997Microsoft CorporationMethod and system for displaying an animated focus itemUS5689641Oct 1, 1993Nov 18, 1997Vicor, Inc.Multimedia collaboration system arrangement for routing compressed AV signal through a participant site without decompressing the AV signalUS5694176Feb 29, 1996Dec 2, 1997Hughes ElectronicsMethod and apparatus for generating television program guides with category selection overlayUS5694546May 31, 1994Dec 2, 1997Reisman; Richard R.System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest listUS5699107Apr 10, 1996Dec 16, 1997Microsoft CorporationProgram reminder systemUS5715169Jan 17, 1995Feb 3, 1998Csk Research Institute Corp.Software rental method and apparatus, and circulating medium thereforUS5715515Sep 19, 1994Feb 3, 1998Scientific-Atlanta, Inc.Method and apparatus for downloading on-screen graphics and captions to a television terminalUS5721827Oct 2, 1996Feb 24, 1998James LoganSystem for electrically distributing personalized informationUS5721829May 5, 1995Feb 24, 1998Microsoft CorporationSystem for automatic pause/resume of content delivered on a channel in response to switching to and from that channel and resuming so that a portion of the content is repeatedUS5721897Jul 26, 1996Feb 24, 1998Rubinstein; Seymour I.Browse by prompted keyword phrases with an improved user interfaceUS5724106Mar 27, 1996Mar 3, 1998Gateway 2000, Inc.Hand held remote control device with trigger buttonUS5724521Nov 3, 1994Mar 3, 1998Intel CorporationMethod and apparatus for providing electronic advertisements to end users in a consumer best-fit pricing mannerUS5724646Jun 15, 1995Mar 3, 1998International Business Machines CorporationFixed video-on-demandUS5727060Jun 16, 1993Mar 10, 1998Starsight Telecast, Inc.Television schedule systemUS5729549Jun 19, 1995Mar 17, 1998Bell Atlantic Network Services, Inc.Simulcasting digital video programs for broadcast and interactive servicesUS5732216Oct 2, 1996Mar 24, 1998Internet Angles, Inc.Audio message exchange systemUS6075575 *Apr 28, 1997Jun 13, 2000Starsight Telecast, Inc.Remote control device and method for using television schedule informationUS6526575 *Jan 7, 1997Feb 25, 2003United Video Properties, Inc.System and method for distributing and broadcasting multimediaUS6978310 *Oct 20, 2000Dec 20, 2005Scientific-Atlanta, IncMedia-on-demand catalog viewing preference system* Cited by examinerNon-Patent CitationsReference1"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).2"Client User Interface Specification (Phase I) for Video-On-Demand Application Development on the Explorer 2000(TM) Digital Home Communications Terminal", Revision 1.10 (Aug. 31, 1998).3"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).4"ISO/IEC 13818-6 Information technology-Generic coding of moving pictures and associated audio information-Part 6: Extensions for DSM-CC," Chapter 4, 113 pages (Sep. 1, 1998).5"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).6"Netscape Navigator Help," Netscape Navigator Software User Documentation, Netscape Communications Corporation, http://home.netscape.com, XP-002166369, pp. 1-63 (Aug. 10, 1997).7"Sez You . . . origin of word daemon," Take Our Word For It, Issue 146, p. 4, http://www.takeourword.com/TOW146/page4.html (retrieved on Apr. 4, 2006).8"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).9"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.10"ISO/IEC 13818-6 Information technology—Generic coding of moving pictures and associated audio information—Part 6: Extensions for DSM-CC," Chapter 4, 113 pages (Sep. 1, 1998).11Addington, Timothy H., "System Architecture Specification for Video-On-Demand Application Development on the Explorer 2000(TM) Digital Home Communications Terminal", Revision 1.10r Review Copy (Mar. 4, 1999).12Addington, 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).13Alberico, 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).14ATI Multimedia Center 7.9, User's Guide, ATI Technologies Inc., pp. i-vi and 1-96 (Copyright 2002).15Barth et al., "10 Fernsehen am PC", Suse GMBH, XP-002324319, pp. 143-149 (2001).16BPAI Decision for U.S. Appl. No. 09/692,995, mailed Aug. 20, 2008.17BPAI Decision for U.S. Appl. No. 09/693,288, mailed Nov. 28, 2007.18Canadian Office Action cited in Application No. 2,376,556 mailed Dec. 6, 2005.19Canadian Office Action cited in Application No. 2,376,556 mailed Nov. 23, 2007.20Canadian Office Action cited in Application No. 2,376,556 mailed Sep. 30, 2008.21Canadian Office Action cited in Application No. 2,402,088 mailed Jun. 1, 2010.22Canadian Office Action cited in Application No. 2,402,088 mailed May 30, 2006.23Canadian Office Action cited in Application No. 2,405,491 mailed Apr. 3, 2009.24Canadian Office Action cited in Application No. 2,405,491 mailed Jan. 20, 2006.25Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 20, 2007.26Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 9, 2010.27Canadian Office Action cited in Application No. 2,405,491 mailed May 22, 2008.28Canadian Office Action cited in Application No. 2,408,289 mailed Aug. 27, 2008.29Canadian Office Action cited in Application No. 2,408,289 mailed May 30, 2006.30Canadian Office Action cited in Application No. 2,408,289 mailed Sep. 2, 2010, 3 pages.31Canadian Office Action cited in Application No. 2,451,477 mailed Nov. 3, 2009.32Canadian Office Action cited in Application No. 2,451,477 mailed Oct. 20, 2010, 4 pages.33Canadian Office Action cited in Application No. 2,456,318 mailed Mar. 27, 2007.34Canadian Office Action cited in Application No. 2,456,318 mailed May 5, 2008.35Canadian Office Action cited in Application No. 2,456,318 mailed Nov. 17, 2010, 4 pages.36Canadian Office Action cited in Application No. 2,459,334 mailed Apr. 16, 2009.37Canadian Office Action cited in Application No. 2,459,334 mailed Mar. 4, 2011, 3 pages.38Canadian Office Action cited in Application No. 2,466,667 mailed Apr. 15, 2009.39Canadian Office Action cited in Application No. 2,475,723 mailed Jul. 7, 2009.40Canadian Office Action cited in Application No. 2,554,208 mailed Apr. 1, 2010.41Canadian Office Action cited in Application No. 2,621,605 mailed Dec. 15, 2009.42Canadian Office Action dated May 31, 2011 cited in Application No. 2,621,605.43Cunningham et al., "5 Das X Window System"., Suse GMBH, XP-002324320, pp. 129-180 (2001).44Decision on Appeal affirmed cited in U.S. Appl. No. 09/590,434 mailed May 28, 2008.45Definition of "flag", Microsoft Press: Computer User's Dictionary, 3 pages (1998).46Definition of "renting", Webster's II: New College Dictionary, 1995, Houghton Mifflin Company, p. 939.47European Examination Report cited in Application No. 00 938 251.6 mailed Mar. 2, 2010.48European Examination Report cited in Application No. 00 938 251.6 mailed Nov. 2, 2007.49European Examination Report cited in Application No. 00 939 759.7 mailed May 10, 2007.50European Examination Report cited in Application No. 01 905 058.2 mailed Dec. 19, 2006.51European Examination Report cited in Application No. 01 922 261.1 mailed Jan. 24, 2007.52European Examination Report cited in Application No. 01 922 261.1 mailed Jul. 18, 2008.53European Examination Report cited in Application No. 01 922 261.1 mailed May 26, 2006.54European Examination Report cited in Application No. 01 922 261.1 mailed Nov. 2, 2007.55European Examination Report cited in Application No. 01 923 092.9 mailed Jul. 20, 2009.56European Examination Report cited in Application No. 01 923 092.9 mailed Nov. 27, 2008.57European Examination Report cited in Application No. 01 937 209.3 mailed Jun. 23, 2008.58European Examination Report cited in Application No. 01 937 209.3 mailed Mar. 16, 2010.59European Examination Report cited in Application No. 02 737 593.0 mailed May 6, 2009.60European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 28, 2007.61European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 4, 2008.62European Examination Report cited in Application No. 02 761 572.3 mailed Apr. 20, 2009.63European Examination Report cited in Application No. 02 761 572.3 mailed Aug. 29, 2007.64European Examination Report cited in Application No. 02 761 572.3 mailed Jan. 22, 2008.65European Examination Report cited in Application No. 02 761 572.3 mailed Sep. 22, 2008.66European Examination Report cited in Application No. 06 802 683.0 mailed Jun. 26, 2008.67Examiner's Answer to Appeal Brief cited in U.S. Appl. No. 09/590,488 mailed Jan. 11, 2008.68Japanese Office Action cited in Application No. 2001-581527 mailed Feb. 10, 2010.69Japanese Office Action cited in Application No. 2001-581527 mailed Sep. 8, 2009.70Kevin, "Change Screen Resolution in Windows (Tips, Tricks, Tweaks, and Setting)," http://www.tacktech.com/display.cfm?ttid=207, pp. 1-3 (Oct. 26, 2002).71Leftwitch et al., "StarSight Interactive Television Program Guide-Functional/Interational Architecture Specification Document, Interaction Analysis and Design Project-Phase III," 36 pages.72Leftwitch et al., "StarSight Interactive Television Program Guide—Functional/Interational Architecture Specification Document, Interaction Analysis and Design Project—Phase III," 36 pages.73Little 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.74McFedries, "The Complete Idiot's Guide to Windows 95," Que, 2nd Edition, p. 49 (1997).75PCT Search Report and Written Opinion cited in International Application No. PCT/US2005/001812 mailed May 2, 2005.76PCT Search Report and Written Opinion cited in International Application No. PCT/US2006/033965 Feb. 19, 2007.77PCT Search Report and Written Opinion cited in International Application No. PCT/US2006/033965 mailed Feb. 9, 2007.78PCT Search Report cited in International Application No. PCT/US00/15952 mailed Jan. 16, 2001.79PCT Search Report cited in International Application No. PCT/US00/15963 mailed Sep. 1, 2000.80PCT Search Report cited in International Application No. PCT/US00/16000 mailed Oct. 2, 2000.81PCT Search Report cited in International Application No. PCT/US01/02490 mailed May 18, 2001.82PCT Search Report cited in International Application No. PCT/US01/06663 mailed Oct. 18, 2001.83PCT Search Report cited in International Application No. PCT/US01/10874 mailed Nov. 29, 2001.84PCT Search Report cited in International Application No. PCT/US01/14150 mailed Apr. 29, 2002.85PCT Search Report cited in International Application No. PCT/US02/20307 mailed Jan. 3, 2003.86PCT Search Report cited in International Application No. PCT/US02/20519 mailed Apr. 7, 2003.87PCT Search Report cited in International Application No. PCT/US02/24704 mailed Mar. 5, 2003.88PCT Search Report cited in International Application No. PCT/US02/28212 mailed Jan. 23, 2003.89PCT Search Report cited in International Application No. PCT/US02/36291 mailed May 23, 2003.90PCT Search Report cited in International Application No. PCT/US03/03391 mailed Jul. 14, 2003.91PCT Written Opinion cited in International Application No. PCT/US00/15952 mailed Jul. 25, 2001.92PCT Written Opinion cited in International Application No. PCT/US00/15963 mailed Jun. 22, 2001.93PCT Written Opinion cited in International Application No. PCT/US00/16000 mailed Oct. 25, 2001.94PCT Written Opinion cited in International Application No. PCT/US01/02490 mailed Oct. 23, 2001.95PCT Written Opinion cited in International Application No. PCT/US01/06663 mailed Jan. 3, 2002.96PCT Written Opinion cited in International Application No. PCT/US01/10874 mailed Jun. 4, 2002.97PCT Written Opinion cited in International Application No. PCT/US01/14150 mailed Sep. 30, 2004.98PCT Written Opinion cited in International Application No. PCT/US02/20307 mailed Aug. 8, 2003.99PCT Written Opinion cited in International Application No. PCT/US02/20519 mailed Apr. 6, 2004.100PCT Written Opinion cited in International Application No. PCT/US02/24704 mailed Nov. 20, 2003.101PCT Written Opinion cited in International Application No. PCT/US02/28212 mailed Dec. 4, 2003.102Petit 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.103Reid, 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).104Remote Wonder, ATI, Tweak 3D, pp. 1-5 (Sep. 30, 2002).105Reply Brief in U.S. Appl. No. 09/565,931 mailed on Sep. 17, 2007.106Rottentomatoes web archived site, http://web.archive.org/web/20000301122211/http://rottentomatoes.com, Mar. 1, 2000, pp. 1-2.107Summons to attend oral proceedings in EP Application No. 01937209.3 mailed Mar. 21, 2011, 7 pages.108Summons to attend oral proceedings pursuant to Rule 115(1) EPC in European Application No. 02737593.0-1241 mailed May 28, 2010.109Supplementary European Search Report cited in European Application No. 02737593.0 mailed Mar. 3, 2009.110Supplementary European Search Report cited in European Application No. 02744705.1 mailed Feb. 19, 2010.111Supplementary European Search Report cited in European Application No. 02750416.6 mailed Jan. 2, 2007.112Supplementary European Search Report cited in European Application No. 02761572.3 mailed Mar. 20, 2007.113Supplementary European Search Report cited in European Application No. 02797096.1 mailed Oct. 14, 2005.114Supplementary European Search Report cited in European Application No. 03713364.2 mailed Jul. 6, 2005.115U.S. Appl. No. 09/330,792, filed Jun. 11, 1999 entitled "Series Reminders and Series Recording from an Interactive Television program Guide".116U.S. Appl. No. 09/378,533, filed Aug. 20, 1999 entitled "Electronic Program Guide with Advance Notification".117U.S. Appl. No. 09/518,041, filed Mar. 2, 2000 entitled "Apparatus and Method for Providing a Plurality of Interactive Program Guide Initial Arrangements".118U.S. Appl. No. 09/542,484, filed Apr. 3, 2000 entitled "System for Providing Alternative Services".119U.S. Appl. No. 09/565,931, filed May 4, 2000 entitled "Navigation Paradigm for Access to Television Services".120U.S. Appl. No. 09/590,434, filed Jun. 9, 2000 entitled "Video Promotional and Advertising Systems for Video on Demand System".121U.S. Appl. No. 09/590,488, filed Jun. 9, 2000 entitled "User Interface Navigational System with Parental Control for Video on Demand System".122U.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".123U.S. Appl. No. 09/590,904, filed Jun. 9, 2000 entitled "Program Information Searching System for Interactive Program Guide".124U.S. Appl. No. 09/591,356, filed Jun. 9, 2000 entitled "Future Program Options Menu System for Interactive Program Guide".125U.S. Appl. No. 09/692,920, filed Oct. 20, 2000 entitled "Media-on-Demand Title Indexing System".126U.S. Appl. No. 09/692,995, filed Oct. 20, 2000 entitled "Media-on-Demand Bookmark System".127U.S. Appl. No. 09/693,115, filed Oct. 20, 2000 entitled "Media Services Window Configuration System".128U.S. Appl. No. 09/693,288, filed Oct. 20, 2000 entitled "Media-on-Demand Rental Duration Management System".129U.S. Appl. No. 09/693,790, filed Oct. 20, 2000 entitled "Integrated Searching System for Interactive Media Guide".130U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 24, 2007.131U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 27, 2003.132U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 28, 2006.133U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jul. 7, 2008.134U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Oct. 20, 2004.135U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Sep. 15, 2005.136U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jun. 17, 2008.137U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 21, 2006.138U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 22, 2005.139U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 1, 2005.140U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 14, 2009.141U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jun. 15, 2006.142U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Dec. 1, 2004.143U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Dec. 18, 2003.144U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 11, 2006.145U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 16, 2003.146U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Feb. 27, 2007.147U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jul. 10, 2006.148U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 30, 2005.149U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 7, 2004.150U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 11, 2005.151U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 24, 2006.152U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Nov. 15, 2006.153U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Sep. 13, 2007.154U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Apr. 13, 2006.155U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jun. 30, 2005.156U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 10, 2004.157U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Sep. 26, 2003.158U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jul. 22, 2008.159U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 14, 2007.160U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 17, 2005.161U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 21, 2006.162U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Apr. 26, 2004.163U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed May 3, 2005.164U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 21, 2005.165U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 4, 2009.166U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 8, 2006.167U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Feb. 9, 2004.168U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jan. 25, 2005.169U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Dec. 1, 2005.170U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 10, 2005.171U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 26, 2004.172U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 8, 2011, 28 pages.173U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jul. 25, 2008.174U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 16, 2006.175U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 19, 2007.176U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 21, 2005.177U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Apr. 21, 2004.178U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jul. 26, 2004.179U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jun. 3, 2005.180U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Dec. 31, 2007.181U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Sep. 17, 2009.182U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 29, 2005.183U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 3, 2009.184U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed May 28, 2010.185U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Aug. 7, 2008.186U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Oct. 5, 2007.187U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Sep. 18, 2006.188U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 24, 2009.189U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 6, 2008.190U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jan. 15, 2010.191U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 11, 2008.192U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Mar. 19, 2009.193U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Aug. 2, 2010.194U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Dec. 19, 2008.195U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Aug. 28, 2006.196U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jul. 25, 2008.197U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed May 22, 2007.198U.S. Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Oct. 2, 2008.199U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 23, 2009.200U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 26, 2008.201U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jul. 24, 2007.202U.S. Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Aug. 8, 2008.203U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 1, 2010.204U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 7, 2009.205U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 28, 2009.206U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 31, 2008.207U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Aug. 6, 2008.208U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Jan. 21, 2010.209U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Dec. 1, 2006.210U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Jan. 26, 2006.211U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 16, 2010.212U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 9, 2009.213U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Feb. 1, 2010.214U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Jun. 9, 2011, 14 pages.215U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed May 28, 2009.216U.S. Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Dec. 22, 2008.217U.S. Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Aug. 31, 2010.218U.S. Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Jul. 29, 2009.219U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Feb. 13, 2009.220U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Mar. 18, 2010.221U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Apr. 1, 2009.222U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Jul. 22, 2010.223U.S. Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Jan. 4, 2010.224U.S. Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Jun. 23, 2010.225U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Dec. 1, 2009.226U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Sep. 14, 2010.227U.S. Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Aug. 20, 2010.228U.S. Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Apr. 14, 2010.229U.S. Final Office Action cited in U.S. Appl. No. 12/372,917 mailed May 17, 2010.230U.S. Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Jul. 6, 2010.231U.S. Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Nov. 9, 2010, 50 pages.232U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Apr. 28, 2010.233U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed May 19, 2011, 15 pages.234U.S. Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Jun. 10, 2010.235U.S. Non-Final Office Action cited in U.S Appl. No. 09/692,920 mailed Jan. 17, 2008.236U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 22, 2005.237U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 4, 2006.238U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 11, 2004.239U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 6, 2007.240U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jan. 10, 2008.241U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Mar. 18, 2003.242U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Apr. 1, 2004.243U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Dec. 7, 2007.244U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jul. 28, 2005.245U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 12, 2007.246U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Sep. 7, 2006.247U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Feb. 13, 2009.248U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jan. 11, 2006.249U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Oct. 28, 2009.250U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Sep. 10, 2004.251U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Apr. 22, 2004.252U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 23, 2003.253U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Nov. 21, 2005.254U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 20, 2005.255U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 10, 2003.256U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Nov. 16, 2004.257U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Oct. 26, 2006.258U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jul. 13, 2005.259U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jun. 4, 2004.260U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Mar. 26, 2007.261U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed May 31, 2006.262U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Dec. 20, 2005.263U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jan. 14, 2004.264U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 21, 2003.265U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Feb. 16, 2006.266U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 18, 2004.267U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 24, 2006.268U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Dec. 5, 2003.269U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Jan. 23, 2009.270U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Mar. 27, 2006.271U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Oct. 21, 2004.272U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jun. 16, 2004.273U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Sep. 26, 2003.274U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 15, 2004.275U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 19, 2005.276U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jun. 21, 2010.277U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Oct. 27, 2003.278U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2005.279U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2006.280U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jan. 15, 2008.281U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Oct. 6, 2004.282U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Dec. 29, 2004.283U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Oct. 28, 2003.284U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Feb. 4, 2009.285U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jul. 26, 2007.286U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jun. 13, 2008.287U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 23, 2008.288U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 23, 2005.289U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Nov. 17, 2009.290U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Apr. 19, 2007.291U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Jan. 29, 2008.292U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Mar. 15, 2006.293U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Apr. 10, 2009.294U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Jun. 25, 2008.295U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 8, 2011, 26 pages.296U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Oct. 2, 2007.297U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Oct. 27, 2010, 23 pages.298U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 15, 2008.299U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 3, 2009.300U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Apr. 12, 2011, 20 pages.301U.S. Non-final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 21, 2010.302U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 24, 2007.303U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jul. 18, 2007.304U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jun. 11, 2009.305U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Dec. 29, 2004.306U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Feb. 2, 2007.307U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jan. 16, 2008.308U.S. Non-Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Feb. 25, 2008.309U.S. Non-Final Office Action cited in U.S. Appl. No. 10/891,053 mailed Jan. 2, 2008.310U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Apr. 27, 2010.311U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Apr. 29, 2011, 11 pages.312U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Feb. 9, 2007.313U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 17, 2008.314U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 26, 2009.315U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Nov. 4, 2010, 10 pages.316U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Sep. 14, 2006.317U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Apr. 30, 2008.318U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 30, 2008.319U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Oct. 15, 2008.320U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Sep. 28, 2009.321U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jan. 14, 2009.322U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jun. 30, 2010.323U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed May 1, 2008.324U.S. Non-Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Apr. 15, 2009.325U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Aug. 23, 2005.326U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed May 16, 2006.327U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Aug. 21, 2009.328U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Feb. 1, 2011, 33 pages.329U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Oct. 31, 2008.330U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Dec. 11, 2008.331U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Oct. 26, 2010, 13 pages.332U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Sep. 30, 2009.333U.S. Non-Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Jun. 12, 2008.334U.S. Non-Final Office Action cited in U.S. Appl. No. 11/234,967 mailed Sep. 10, 2010.335U.S. Non-Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Mar. 30, 2010.336U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed May 5, 2010.337U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Oct. 22, 2009.338U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Sep. 22, 2008.339U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Jun. 26, 2009.340U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Sep. 17, 2008.341U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Mar. 2, 2010.342U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 18, 2008.343U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 29, 2009.344U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Aug. 24, 2009.345U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Jul. 20, 2010.346U.S. Non-Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Dec. 16, 2009.347U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,942 mailed Jun. 8, 2010.348U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,945 mailed Jul. 16, 2010.349U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,951 mailed Aug. 2, 2010.350U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Apr. 30, 2009.351U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Mar. 31, 2010.352U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,752 mailed Dec. 23, 2009.353U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,763 mailed Jan. 4, 2011, 18 pages.354U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Jan. 22, 2010.355U.S. Non-Final Office Action cited in U.S. Appl. No. 12/180,416 mailed Jun. 25, 2010.356U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Oct. 16, 2009.357U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,894 mailed Oct. 27, 2009.358U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,917 mailed Oct. 26, 2009.359U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,002 mailed Sep. 3, 2010.360U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Dec. 15, 2009.361U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Jun. 2, 2010.362U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Aug. 23, 2010.363U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Jan. 21, 2011, 13 pages.364U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Nov. 10, 2009.365U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,418 mailed Sep. 28, 2010, 13 pages.366U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,420 mailed Oct. 19, 2010, 12 pages.367U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,422 mailed Oct. 20, 2010, 13 pages.368U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Mar. 17, 2011, 20 pages.369U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Nov. 30, 2009.370U.S. Restriction Requirement cited in U.S. Appl. No. 11/162,345 mailed Jul. 3, 2008.371US 7,934,240, 04/2011, Rodriguez et al. (withdrawn)372US 7,934,241, 04/2011, Jerding et al. (withdrawn)373US 7,934,242, 04/2011, Rodriguez (withdrawn)374VESA Plug and Display Standard, Version 1, Video Electronics Standards Association, XP-002123075, 90 pages (Jun. 11, 1997).375W3C, Putting language attributes in HTML, www.w3.org.org/International/O-help-lang, 2 pages (Apr. 29, 1997).Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8823769Jan 5, 2011Sep 2, 2014Ricoh Company, Ltd.Three-dimensional video conferencing system with eye contactUS20110209224 *Feb 24, 2010Aug 25, 2011Christopher GentileDigital multimedia albumUS20120254250 *Apr 5, 2012Oct 4, 2012Iboard IncorporatedDigital multimedia album* Cited by examinerClassifications U.S. Classification709/231, 709/229, 709/226, 348/14.07, 709/203International ClassificationG06F15/173, G06F15/16, H04N5/445, H04N7/173, H04N5/44Cooperative ClassificationH04N21/4828, H04N21/443, H04N5/4401, H04N5/44543, H04N21/4755, H04N21/4782, H04N7/17318, H04N21/482, H04N21/84, H04N21/4622, H04N21/47202European ClassificationH04N21/475P, H04N5/445M, H04N21/472D, H04N21/482S, H04N21/84, H04N7/173B2, H04N21/462S, H04N21/482, H04N21/4782, H04N21/443Legal EventsDateCodeEventDescriptionJul 27, 2009ASAssignmentOwner name: SCIENTIFIC-ATLANTA, LLC, GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:023012/0703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100316;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100323;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100504;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100518;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100525;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:23012/703Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100518;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100323;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100525;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:023012/0703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100316;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100504;REEL/FRAME:23012/703Effective date: 20081205Nov 25, 2013ASAssignmentOwner name: CISCO TECHNOLOGY, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SCIENTIFIC-ATLANTA, LLC;REEL/FRAME:031719/0891Effective date: 20131120Dec 10, 2014ASAssignmentOwner name: SCIENTIFIC-ATLANTA, LLC, GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:034609/0790Effective date: 20081205RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services