The present invention is generally related to television systems, and, more particularly, is related to personal video recording and interactive program guides.
With recent advances in digital transmission technology, subscriber television systems are now capable of providing much more than the traditional analog broadcast video. In implementing enhanced programming, the home communication terminal device (“HCT”), otherwise known as the set-top box, has become an important computing device for accessing media content services (and media content within those services) and navigating a user 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 and personal video recording.
Typically, a DHCT is connected to a cable or satellite, or generally, a subscriber television system, and includes hardware and software necessary to provide the functionality of the digital television system at the user's site. Some of the software executed by a DHCT can be downloaded and/or updated via the subscriber television system. 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 or even an audio device such as a programmable radio, as will be appreciated by those of ordinary skill in the art.
DHCTs are typically capable of providing users with a very large number and variety of media content choices. DHCTs equipped with personal video recording functionality (e.g., via the use of a coupled storage device) provide the user with the opportunity to record favorite media content and/or to record and subsequently view media content he or she would otherwise have missed due to, for example, scheduling conflicts. Many DHCTs provide users with television program information via interactive program guides (IPGs), which allow a user to scroll through and/or search available program information for broadcast and/or on-demand media content, but current mechanisms provide limited program information for recorded media content and are cumbersome to use.
Thus, a heretofore unaddressed need exists in the industry to address the aforementioned deficiencies and inadequacies.
The preferred embodiments of the invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
The preferred embodiments of the invention now will be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. One way of understanding the preferred embodiments of the invention includes viewing them within the context of a subscriber television system, and more particularly within the context of a media client device, such as a digital home communication terminal (DHCT), that provides for user interaction with what is displayed on a television. Although other communication environments are considered to be within the scope of the preferred embodiments, the preferred embodiments of the invention will be described in the context of a DHCT that receives media content from a headend over a subscriber network as one example implementation among many.
Because the preferred embodiments of the invention can be well understood in the context of a subscriber television system environment, an initial description of a subscriber television system is followed with further description of the headend and DHCT (and coupled storage device) that are included within the subscriber television system. The preferred embodiments of the invention include, among other things, a system that displays information about media content recorded in the storage device that is coupled to the DHCT. Following the description of the subscriber television system components is a description of an interactive program guide (IPG), and how the preferred embodiments of the invention are used in the context of an IPG. The displayed information, or media content information, will preferably be manifested in one or more display channels in an IPG. An IPG is typically presented as a grid with rows of display channels and columns of time slots. Listings of current and scheduled media content instance presentations, preferably identified by title of a particular media content instance (e.g., TV episode, movie), are placed in the grid according to the scheduled presentation.
In the preferred embodiments, listings for the media content stored in a storage device coupled to the DHCT are presented in the IPG in a somewhat similar format to that used for broadcast media content. In one preferred embodiment, broadcast media content that is recorded (either temporarily or permanently recorded, including scheduled recordings, live recordings, or recordings designated as permanent from a storage buffer, among others) to the storage device automatically has the corresponding title displayed in a personal video recording (PVR) channel in the IPG within a time slot that reflects the duration of the recorded presentation.
Following the description of how the preferred embodiments can be used in an IPG is a description of how the preferred embodiments include a series of user interface screens for configuring PVR channels in the IPG. These screens, as will be explained below, can be evoked during the recording process of the PVR functions of the DHCT and/or via a user settings menu screen. In the preferred embodiments, the user can configure one or more PVR channels to reflect the type of media content that is recorded in the storage device. For example, assume the user desires to record all Barney episodes for his or her child. The user can configure the DHCT PVR functionality to record all episodes of Barney to the storage device. Also, the user can configure one of a plurality of PVR channels in the IPG to not only be entitled the Barney Channel, but also to display the titles of all of the recorded Barney episodes into the newly configured Barney channel. Displaying the titles, or other media content information, of the recorded media content into PVR channels in the IPG is herein referred to as channel mapping. Similarly, the user can configure other PVR channels based on the type of downloaded media content. For example, the user can configure a News Channel to channel map all of the instances of recorded news programming. Further, the user can configure time-based channels, such as a Last Night Channel to channel map all of the media content recorded from the prior evening, for example.
The preferred embodiments of the invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those having ordinary skill in the art. Furthermore, all “examples” given herein are intended to be non-limiting, and are provided as an exemplary list among many other examples contemplated but not shown.
A DHCT 16 is typically situated at the residence or place of business of a user and may be a stand-alone unit or integrated into another device such as, for example, a television set or a personal computer or other display devices, or an audio device. The customer's premises may be a user's residence or place of business. The DHCT 16 receives signals (video, audio and/or other data) from the headend 11 through the network 18 and provides any reverse information to the headend 11 through the network 18.
The headend 11 receives, among other data and/or media content, program guide data from a program guide information provider (not shown). The program guide information (data) preferably comprises data corresponding to services that may be provided via the DHCT 16. The headend 11 edits the program guide data and transmits the edited program guide data to the DHCT 16 via the network 18. The headend 11 may include one or more server devices (not shown) for providing video and/or audio and/or data to media client devices such as the DHCT 16. The headend 11 and the DHCT 16 cooperate to provide a user with television services via the television (not shown). The television services may include, for example, broadcast television services, cable television services, premium television services, video-on-demand (VOD) services, and/or pay-per-view (PPV) services, among others.
A digital network control system (DNCS) 223 provides management, monitoring, and control of the network's elements and of the broadcast services provided to users. A content provider such as a program guide information provider transmits data for television program guides through a network interface 209 to the DNCS 223 of the headend 11, preferably using a file transfer protocol (FTP). The DNCS 223 includes functionality that defines relationships between channel names listed in the program guide data received from the program guide provider and the numbered channels that are available via the DHCT 16. This functionality is used by the DNCS 223 to edit the program guide data to include channel numbers that correspond to the listed channel names. After the program guide data is edited by the DNCS 223, it is transmitted to the DHCT 16 preferably using a broadcast file system (BFS) server 202. The BFS server 202 and its counterpart, a BFS client module 343 in the DHCT 16, are part of a file broadcasting system. The BFS server 202 repeatedly sends data through a network interface 206 to the DHCT 16 via a quadrature amplitude modulation (QAM) modem 203 over a period of time in a cyclical manner so that the DHCT 16 may access the data as needed. Of course other mechanisms and techniques may be utilized to transfer data to the DHCT 16.
A quadrature phase shift keying (QPSK) modem 207 is responsible for transporting out-of-band IP (internet protocol) datagram traffic between the distribution headend 11 and a DHCT 16. Data transmitted or received by the QPSK modem 207 may be routed by a headend router 208. The headend router 208 may be used to deliver upstream data to the various server applications (not shown).
The DHCT 16 preferably includes one or more processors, such as processor 344, for controlling operations of the DHCT 16, an output system 348 for driving the television display 341, and at least one tuner system 345 for tuning into a particular television channel or frequency to display media content and for sending and receiving various types of data or media content to and from the headend 11. The DHCT 16 may include, in other embodiments, multiple tuners for receiving downloaded (or transmitted) media content. The tuner system 345 enables the DHCT 16 to tune to downstream media and data transmissions, thereby allowing a user to receive digital and/or analog media content delivered in the downstream transmission via the subscriber television system. The tuner system 345 includes, in one implementation, an out-of-band tuner for bidirectional QPSK data communication and one or more QAM tuners (in band) for receiving television signals. Additionally, a receiver 346 receives externally generated information, such as user inputs or commands from an input device, such as remote control device 380, or other devices.
The DHCT 16 processes analog and/or digital transmission signals for storage in the storage device 373, and/or for display to the television 341. The DHCT 16 preferably includes a signal processing system 314 and a media engine 322. The components of the signal processing system 314 are capable of QAM demodulation, forward error correction, and demultiplexing MPEG-2 transport streams, and parsing elementary streams and packetized elementary streams. Additional components, not shown, include an analog decoder and compression engine for processing an analog transmission signal and, in one implementation, converting it to compressed audio and video streams that are produced in accordance with the syntax and semantics of a designated audio and video coding method, such as specified by the MPEG-2 audio and MPEG-2 video ISO (International Organization for Standardization or ISO) standard, among others.
The signal processing system 314 outputs packetized compressed streams and presents them as input for storage in the storage device 373 via an interface 375, or in other implementations, as input to a media engine 322 for decompression by a video decompression engine (not shown) and an audio decompression engine (not shown) for display on the TV 341. One having ordinary skill in the art will appreciate that the signal processing system 314 will preferably include other components not shown, including memory, decryptors, samplers, digitizers (e.g., analog-to-digital converters), and multiplexers, among other components. Further, it will be understood that one or more of the components listed above will interface with the processor 344 and/or system memory 349 (and/or dedicated memory for a particular component), to facilitate data transfer and/or processing of the video and/or audio signal for display and/or storage.
One or more programmed software applications are executed by utilizing the computing resources in the DHCT 16. Note that an application typically includes a client part and a server counterpart that cooperate to provide the complete functionality of the application. The applications may be resident in FLASH memory 351 or downloaded (or uploaded) into DRAM 352. Applications stored in FLASH memory 351 or DRAM 352 are executed by the processor 344 (e.g., a central processing unit or digital signal processor) under the auspices of the operating system 353. Data required as input by an application is stored in DRAM 352 or FLASH memory 351 and read by the processor 344 as need be during the course of application execution. Input data may be data stored in DRAM 352 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 351. Data generated by an application is stored in DRAM 352 by the processor 344 during the course of application execution. DRAM 352 also includes application memory 370 that various applications may use for storing and/or retrieving-data.
An application referred to as a navigator 355 is also resident in FLASH memory 351 for providing a navigation framework for services provided by the DHCT 16. The navigator 355 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 navigator 355 also provides users with television related menu options that correspond to DHCT functions such as, for example, blocking a channel or a group of channels from being displayed in a channel menu presented on a screen display.
The FLASH memory 351 also contains a platform library 356. The platform library 356 is a collection of utilities useful to applications, such as a timer manager, a compression manager, a configuration manager, a hyper text markup language (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 356 that are shown in
The window manager 359 provides a mechanism for implementing the sharing of the screen regions and user input. The window manager 359 on the DHCT 16 is responsible for, as directed by one or more applications, implementing the creation, display, and deallocation 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 359 communicates with the resource manager 367 to coordinate available resources (such as display memory) among different resource consuming processes. Such processes may be directly or indirectly invoked by one or more applications.
The SAM client 357 is a client component of a client-server pair of components, with the server component (not shown) being located on the headend 11, preferably in the DNCS 323 (
FLASH also includes a BFS client module 343 that is preferably resident in the operating system 353, and which cooperates with a server counterpart (as described above) to provide a directory of modules such as applications that are cyclically broadcast.
An executable program or algorithm corresponding to an operating system (OS) component, or to a client platform component, or to an application, or to respective parts thereof, can reside in and execute out of DRAM 352 and/or FLASH memory 351. Likewise, data input into or output from any executable program can reside in DRAM 352 or FLASH memory 351. Furthermore, an executable program or algorithm corresponding to an operating system component, or to a client platform component, or to an application, or to respective parts thereof, can reside in FLASH memory 351, or in a local storage device (such as storage device 373) externally connected to or integrated into the DHCT 16 and be transferred into DRAM 352 for execution. Likewise, data input for an executable program can reside in FLASH memory 351 or a storage device and be transferred into DRAM 352 for use by an executable program or algorithm. In addition, data output by an executable program can be written into DRAM 352 by an executable program or algorithm and be transferred into FLASH memory 351 or into a storage device. In other embodiments, the executable code is not transferred, but instead, functionality is effected by other mechanisms.
The DHCT 16 can also include one or more wireless or wired interfaces, also called communication ports 374, 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 content devices in an entertainment center), serial, and/or parallel ports. The user inputs may be, for example, provided by an input device including a computer or transmitter with buttons or keys located either on the exterior of the terminal or by a hand-held remote control device 380 or keyboard that includes user actuated buttons, or even aural input (e.g., voice activated).
The DHCT 16 includes at least one storage device 373 to provide storage for downloaded media content. The storage device 373 can be an optical storage device or a magnetic storage device, among others, and is preferably a hard disk drive. The storage device 373 comprises storage for media content and/or data that can be written to for storage and later read from for retrieval for presentation. The storage device 373 preferably includes at least one hard disk 300. Throughout this disclosure, references relating to writing to or reading from the storage device 373, or references regarding recordings from or to the storage device 373 will be understood to mean that such read or write operations are occurring to the actual medium (for example, the hard disk 300) of the storage device 373. The storage device 373 is also comprised of a controller 379 that preferably receives operating instructions from the device driver 311 of the operating system 353 and implements those instructions to cause read and/or write operations to the hard disk 300.
The storage device 373 is preferably internal to the DHCT 16, coupled to a common bus through a communication interface 375, preferably an integrated drive electronics (IDE) interface or small computer system interface (SCSI), although IEEE-1394 or USB can be used. In other embodiments, the storage device 373 can be externally connected to (and thus removable from) the DHCT 16 via a communication port 374 implemented as IEEE-1394 or USB or as a data interface port such as a SCSI or an IDE interface. In one implementation, under the auspices of the real-time operating system 353 and executed by the processor 344, and in coordination with the personal video recording (PVR) application 377, the device driver 311, and the device controller 379, downloaded media content (herein understood to also refer to other types of data, in addition to, or instead of, media content instances) are received in the DHCT 16 via the communications interface 342, processed as described above, and stored in a temporary cache (not shown) in memory 349. The temporary cache is implemented and managed to enable media content transfers from the temporary cache to the storage device 373, or, in concert with the insertion of a newly arriving media content into the temporary cache.
In one implementation, the processor 344, in communication generally with the device driver 311 and the storage device controller 379 and the signal processing system 314, effect retrieval of compressed video streams, compressed audio streams, and data streams corresponding to one or more media content instances from the storage device 373. Retrieved streams are deposited in an output cache in the storage device 373 and transferred to DRAM 352, and then processed for playback according to mechanisms well known to those having ordinary skill in the art. In some embodiments, one or more media content instances are retrieved and routed from the hard disk 300 to the media engine 322 for video and audio decoding simultaneously, and then further processed for eventual presentation on a display device or other device.
The PVR application 377 provides for media content recording functionality by enabling the temporary writing to, and if requested, more permanent recording (i.e., relatively permanent) to the storage device 373. Media content can be transmitted (or downloaded) from a remote location, such as, for example, a remote server located in the headend 11, or from a home communication network, or from consumer electronic devices. Downloaded media content that is received at each tuner of tuner system 345 is temporarily stored, or buffered, on the hard disk 300 of the storage device 373. The corresponding space on the hard disk 300 is called buffer space, or a time shift buffer (TSB) 378. In a preferred embodiment, each tuner in tuner system 345 has a respective TSB 378. Although one TSB 378 is shown, it will be understood that more TSBs can be used with multiple tuners. Note that buffering is understood to include temporarily storing media content, received from a local attached device (e.g., a camera, etc.) and/or either from reception of a broadcast digital channel or a digital compressed version of a broadcast analog channel, and/or data, in the buffer space, or TSB 378, of the storage device 373.
Under normal operation, the PVR application 377 effectively associates a temporary recording designation with the media content received into the TSB 378. The media content stored in the TSB 378 will either be deleted (i.e., the clusters storing the media content will be configured as writeable for eventual write operations that overwrite the media content within those clusters) or retained (through election by the user as one example) as a permanent recording. A permanent recording will be understood to include media content that is stored for an extended period of time, for example as decided by the user. Permanent recordings can be implemented by the user electing in advance to make a scheduled recording of a media content instance that has not yet been tuned to at the DHCT 16. A permanent recording can also be achieved by selecting a media content instance stored in the TSB 378 and designating the media content instance as permanent. Permanent recordings will preferably be more permanent than media content in the TSB 378, and permanent recordings can eventually be deleted from the disk space, typically at the explicit request of a user, as one example. The PVR application 377 maintains a data structure, or data record, for every downloaded media content instance. This data structure is preferably maintained on the hard disk 300 of the storage device 373, but can be maintained in memory 349 also.
The time shift buffer can be managed and implemented according to several mechanisms. Further information pertaining to creating and maintaining the TSB 378, as well as information pertaining to the processing of incoming digital and/or analog transmission signals, can be found in the applications entitled, “Controlling Substantially Constant Buffer Capacity for Personal Video Recording with Consistent User Interface of Available Disk Space,” filed Dec. 6, 2001 under application Ser. No. 10/010,270, which issued on Jun. 14, 2011 as U.S. Pat. No. 7,962,011; “Converting Time-Shift Buffering for Personal Video Recording Into Permanent Recordings,” filed Dec. 6, 2001 under application Ser. No. 10/008,624, which issued on Aug. 14, 2007 as U.S. Pat. No. 7,257,308; “Dividing and Managing Time-Shift Buffering into Program Specific Segments Based on Defined Durations,” filed Dec. 6, 2001 under application Ser. No. 10/008,439, which published on Jun. 12, 2003 as U.S. Publication No. 2003/0110504 A1; “Disk Driver Cluster Management of Time Shift Buffer with File Allocation Table Structure,” filed Dec. 5, 2001 under application Ser. No. 10/005,628, which issued on Mar. 20, 2007 as U.S. Pat. No. 7,194,563; and “Application Management and Interface for Cluster Control of Time Shift Buffer,” filed Dec. 5, 2001 under application Ser. No. 10/010,781, which issued on Jun. 23, 2009 as U.S. Pat. No. 7,551,832, all assigned to Scientific Atlanta, and all herein entirely incorporated by reference.
As described above, the user preferably permanently records from the TSB 378 by designating as permanent a currently viewed media content instance during real-time viewing or returning (e.g., rewinding) to any part of a media content instance in the TSB 378 and selecting the record button from a remote control device 380, or alternatively, from selecting a record button (not shown) on the DHCT 16. In one preferred embodiment, the user can record from an IPG screen, as will be described below. An example remote control device 380 to provide input to the DHCT 16 is illustrated in
Referring again to
Based on the configuration information stored in the IPG configuration module 396, the IPG user interface module 395 utilizes the window manager 359 and other graphics utilities provided by the operating system 353 to render an IPG on the television 341. The window manager 359 is a component that, in one embodiment, is part of the platform 356, but in other embodiments may be part of the operating system 353. The window manager 359 contains functionality for allocating screen areas and managing screen use among multiple applications. The operating system 353 provides primitives to the IPG user interface module 395 in order to help render images on the television 341.
As a window is generated on a display device, the IPG user interface module 395 registers with the window manager 359 for particular user input commands that may be required for selecting options provided by a newly-created window. The EPG application 394 also contains a daemon application 399 that receives IPG data files transmitted by the headend 11 and stores them in the IPG database 398 for utilization by the user interface module 395. The PVR application 377 also includes functionality for searching for and retrieving from multiple sources of PVR media content and/or data for storage in the IPG database 398. Such sources include, for example, the storage device 373 or a navigator database (not shown), or other pluggable database modules (not shown).
Video corresponding to the television service to which the DHCT 16 (
An IPG grid 465 includes a main media content instance listing display area 460, a time area 470, and a service identification area 480. The media content instance listing display area 460 contains listings of service instances that correspond to respective television services identified in the service identification area 480 that are scheduled to be available during the time periods listed in the time area 470. Each media content instance listing is preferably formatted as a rectangle, or block, that has a length that depends on the duration of the scheduled presentation of the media content instance. The media content instance listing, such as the Johnny Bravo listing 420, includes an identifier such as the title of the media content instance (e.g., Johnny Bravo), and can include other identifiers like parental control icons or differences in shading and/or color to represent different functionality. The service identification area 480 includes, in one implementation, a vertical list of television services organized sequentially from top to bottom by increasing television display channel number (except for the highest numbered television service which is typically listed immediately above the lowest numbered television service). In one embodiment, the arrow buttons 386 of the remote control device 380 (
In this non-limiting example, the left-most time column (i.e., under the 8:00 time slot) in the media content instance listing display area 460 includes the titles of media content instance listings, including the highlighted Johnny Bravo listing 420, which is scheduled to be provided via the Cartoon Network (i.e., Toonz on display channel number 201). It should be noted that the current media content instance listing shown in video area 430 with corresponding information referenced in information banner 440, corresponds to the currently tuned television service (display channel number 5), and not to the service corresponding to the currently highlighted Johnny Bravo listing 420. The bottom area 450 of the IPG screen 400 indicates the selected day for which media content instance listing data is being displayed as well as information about the current functions of the “A”, “B”, and “C” buttons on the remote control device 380 (
In an alternative embodiment, the IPG screen 400 may have fewer, additional, and/or different components and may have a different layout. For example, the IPG screen 400 might not include one or more of a detailed focus area 410, a video area 430, an information banner 440, and/or a bottom area 450. The double arrow icons 462 indicate that a given media content instance listing has a duration that expands beyond the time period shown in the current IPG display screen, suggesting to the user that the balance of the listing can be viewed in another IPG display by selecting the right or left navigation arrow buttons 386 on the remote control device 380 (
In one preferred embodiment, the IPG application 394 (
The example confirm recording screen 500 includes a confirm recording header 505 to identify the screen 500. Also included is an information area 510, that includes the title of the media content instance (e.g., Johnny Bravo), the date, time, display channel, and associated service of the scheduled presentation, as well as the default quality and the default start time, which in this case is from the beginning of the scheduled presentation. Note that the quality refers to the recording quality level. In one implementation, there exists three recording quality levels: good (with a video data rate of 3 MegaBytes per second), better (5 MegaBytes per second), and best (8 Megabytes per second). Other data rates and quality levels can also be used in other embodiments. Also included is an information button icon, which corresponds to the information button 389 on the remote control device 380 (
The example recording schedule screen 600 includes a recording schedule header 605, an information area 610, a list block 620, and a bottom area 630. As shown, the information area 610 includes the title of the selected media content instance for recording, as well as default values for the amount of days the media content instances will be saved (e.g., for seven days). Other default values include the quality, which is shown here as “good,” as well as an information button icon as described in respect to
In a preferred embodiment, the blocks representing the recorded media content listings in the PVR channel 301 can be in synchronization with the time periods illustrated in the time area 770. In other words, the PVR channel media content listings are preferably aligned along the time area 770, having a similar appearance to the listings associated with broadcast media content. For example, since Johnny Bravo is a half hour presentation, its block boundaries in the IPG screen 700 are defined by the column positioned between the beginning of the 11:00 p.m. time slot and the beginning of the 11:30 p.m. time slot illustrated in the time area 770. In one implementation, because the media content instance listings in the IPG screen 700 for PVR content are synchronized with the time indicated in the time area 770, a user selecting Johnny Bravo for playback at the current time of 11:10 p.m. will be positioned 10 minutes into the presentation (i.e., ten minutes past the relative hour) of Johnny Bravo. Thus, at the end of the presentation of a recorded media content instance, the user can go to other display channels, for example, broadcast channels, to view from the beginning of a scheduled presentation of one of the broadcast media content. Further, scheduled live broadcasts can be inserted into the PVR channel, as described above, providing the user the opportunity to view the presentation while it is being recorded. In other embodiments, the user can choose to be positioned at the beginning of the presentation of the selected media content instance, regardless of what the current time is relative to the hour. This positioning can be user configurable via a user settings menu, as one example. Note that as time advances, as shown in the time area 770, the relative positions of the media content listings with respect to the boundaries of the media content instance listing display area 760 for the PVR channels remains the same in the IPG screen 700. For example, when the IPG screen 700 advances to 12:30 p.m., Johnny Bravo will still positioned relative to the hour, starting at the left-most position of the IPG grid (i.e., the under the 12:30 column). An exception to this relative positioning occurs when scheduled media content is inserted into the PVR channel, since the scheduled recordings will preferably be tied to a set, or scheduled presentation time.
In other embodiments, the time area 770 can take on other forms and functionality. Unlike broadcast media content, PVR listings that are associated with completed recordings can be viewed at any time. Thus, when a listing in a PVR channel is selected, the time area 770 can be altered to reflect this selection and accessibility feature. For example, responsive to selecting a listing in a PVR channel, the time area 770 can be grayed out. In another embodiment, the time area 770 can depict the duration in “seconds,” and/or “minutes,” and/or “hours” of each recorded media content instance. Other embodiments include not having a time area, or having a time area with index numbers corresponding to the number and/or the recorded sequence of the recorded media content, or a ticker banner, among others. The ticker banner can include a scrolling banner that is displayed to the user when he or she has highlighted one of the listings for recorded media content instances displayed in the PVR channels. In other embodiments, the time area can still illustrate the current time increments by half an hour (as shown by the IPG screen 700), but have relevance only to broadcast media content.
If there was a portion of Johnny Bravo that was not recorded, the playback bar 806 would preferably be divided into two distinct regions. For example, the unrecorded portion can be colored red, and the recorded portion can be colored green, as one example. Such a scenario can arise for scheduled recordings (i.e., scheduled to be recorded in the future), and/or recordings that are in progress, as non-limiting examples. It would be understood, in the context of the detailed description, that other mechanisms can exist to indicate the difference between unrecorded and recorded content including differences in gray shading, etc. The playback bar 806 also includes a playback position indicator 808. As described earlier, the user is positioned, in one implementation, in the presentation of Johnny Bravo ten minutes past the start of the scheduled presentation of Johnny Bravo. The playback position indicator 808 reflects this relative position. The recorded length of Johnny Bravo is also indicated in the recorded length area 810. The pause banner 802 also includes a play button icon 812 and an options button icon 814. The user might select the options button icon 814, for example, to delete a selected recorded media content instance. Preferably, by selecting a delete option (not shown) in a screen prompted by the selection of the options button icon 814, the corresponding listing will also be removed from the IPG screen 700 (
Assume the user has decided to record all episodes of Barney and in addition, the user has decided that he or she wants to configure a PVR channel as a Barney channel. By highlighting and selecting the “record all episodes” option in the options block 1020 of the confirm recording screen 1000, the user is presented with the example recording schedule screen 1100 as shown in
The record options screen 1200 is shown overlaid on a grayed out recording schedule screen 1100 (
The example PVR channel configure menu screen 1300 is a screen where the user can configure a particular PVR channel to catalog past, current, and/or future recordings based on one or more pre-defined and/or user configured categories. The PVR channel configure menu screen 1300 includes a header 1305, a display area 1310, navigation arrow icons 1322, a select button icon 1324, and a bottom header 1330. The header 1305 identifies the PVR channel configuration menu screen 1300. The display area 1310 displays information corresponding to the highlighted PVR channel selection in the PVR channel list 1320. For example, PVR channel 302 is highlighted in the PVR channel list 1320, as indicated in the display area 1310. As shown in the display area 1310, the first line preferably identifies the highlighted PVR channel, which is entitled, PVR channel 302. The next line in the display area 1310 is entitled category, which the user has not yet configured. The bottom line in the display area 1310 instructs the user to press select to configure a highlighted PVR channel. It will be appreciated by those of ordinary skill in the art that this display area can be configured in various forms while being contemplated within the scope of the preferred embodiments. As described above, the PVR channel list 1320 includes a list of configurable PVR channel numbers for channel mapping recorded media content. Herein, it will be understood that recorded media content (or media content instances, or similarly, media content instance recordings) includes media content that is scheduled to be recorded, as well as media content where recording is in progress or has been completed.
In one embodiment, the first listed PVR channel, which is PVR channel 301, is grayed out. As described above, this PVR channel will preferably be used as a default, or miscellaneous channel for recorded media content that does not match a user configured PVR channel. For example, for any recorded media content that does not fall into a configured category (as will be described below), such non-configured, recorded media content will fall under the PVR channel 301 entry in an IPG screen. Accordingly, upon the user being presented with the PVR channel configure menu screen 1300 for the first time, the defaulted highlighted channel available for configuration by the user will preferably be the PVR channel 302. The user can use the navigation arrow icons 1322 and select button icon 1324 to highlight and select to configure other PVR channels. For example, the user can navigate to the PVR channel 305 to configure that PVR channel out of the default display order. The bottom header 1330 includes an IPG button icon 1332, a record options button icon 1334, and a title channel button icon 1336. For example, the user can select the “A” button 381 on the remote control device 380 (
By selecting the record options button icon 1334, the user is presented with a record options screen, such as that shown in
The example PVR channel configuration categories screen 1400 has a similar structure to the PVR channel configure menu screen 1300 (
For example, since the title choice is highlighted in the category choices list 1420, and Barney was the episode that was selected for the PVR channel configuration, the default channel title will be the Barney channel. Similarly, if the category choice entitled, content service, was highlighted in the category choice list 1420, then the default PVR channel title would be the Cartoon Network Channel 302. As shown, the category choices include title, theme, preference engine, date of recording, and content service. Theme choices include comedy, mystery, action, among others. A category choice of preference engine would utilize whatever search rule was used by the DHCT resources to scan for and/or select desired media content. Other category choices can be scrolled to using the navigation arrow icons 1422. Other category choices can include, but are not limited to, artists, data of composition, time of presentation, display channel, rating (e.g., Motion Pictures Artist Association, or MPAA), among others. The bottom header 1430 includes an IPG button icon 1432, as well as a back to PVR channel configuration menu button icon 1434. Assuming the user has highlighted and selected the title choice from the category choices list 1420, the user is presented with the example PVR channel configure menu screen 1500 shown in
As noted by the PVR channel list 1520, the PVR channel 302 is now configured as the Barney channel 302. This fact is reflected by the top line in the display area 1510 and the category line, which describes how recorded media content is channel mapped in this PVR channel. Thus, any Barney recordings, scheduled or otherwise, will be received into the storage device 373 (
Another recording process implementation includes providing the user with the ability to configure his or her own personalized PVR channel (e.g., Michael's channel), and mapping recorded media content under user direction, such as during a manual recording process. Or in other embodiments, the user could configure the personalized channel with categories to search for, with the result that media content with characterizing information matching the categories selected would be mapped to the personalized PVR channel.
One implementation for configuring one or more PVR channels was through the recording process, as described above. Another mechanism for configuring one or more PVR channels is through a user settings menu, such as the example user settings menu screen 1700 shown in
This screen 2000 is for configuring a category that further refines the time of recording choice selected in the prior screen 1900 (
By choosing these relative time choices, a PVR channel can be configured that channel maps past recorded media content into this category based on the recording time relative to the current IPG display time (i.e., time-based channel mapping). For example, if an IPG screen is displayed at 12:00 midnight, all past recorded media content from 6:00 p.m. to 12:00 midnight would be channel mapped in the Past Six Hours channel in an IPG screen. Assume the user has highlighted and selected the past six hours choice of the relevant time choices list 2120, resulting in the example PVR channel configure menu screen 2200 shown in
As noted by the subheader 2615, this screen 2600 presents theme choices to the user. The theme choices list 2620 includes a plurality of choices that can be scrolled through using the navigation arrow icons 2622. Assume in this example the user has selected the news choice in the theme choices list 2620. As a result, the user is presented with the example PVR channel configure menu screen 2700 as illustrated in
In the next example, the user will attempt to configure a PVR channel that channel maps into an IPG screen all recorded media content that has meta data indicating that the media content includes Auburn basketball games. By selecting the PVR channel 305 entry in the example screen 2700, the user is presented with the example PVR channel configuration categories screen 2800 illustrated in
Although there are several category choices to choose from to configure an Auburn basketball channel, in this example, the user begins by highlighting and selecting the category choice, theme, from the category choice list 2820. In response to that selection, the user is presented with the example PVR configuration categories screen 2900 illustrated in
This screen 3000 presents categories that are a further refinement to the sports theme choice selected in the prior screen 2900, as suggested by the subheader 3015 which is entitled, sports options. Since the user desires to have an Auburn basketball channel, the user highlights and selects the basketball college option in the sports options list 3020, resulting in the example PVR channel configure menu screen 3100 illustrated in
Assume the user has highlighted and selected the college basketball channel 305 entry in the PVR channel list 3120 resulting in the example PVR channel configuration categories screen 3200 illustrated in
The configuration query screen 3400 includes an options block 3420, as well as select button icon 3424 and navigation arrow icons 3422. The user can scroll through a plurality of configuration query options, including whether he or she wants to replace the current category, or add the keyword as a limitation to the currently configured category, among others. In this example, the user desires an Auburn basketball channel, thus a logical choice from the option block 3420 is to add the keyword (e.g., Auburn) as a limitation to the current college basketball category by highlighting and then selecting that option, resulting in the example PVR configure menu screen 3500 illustrated in
As described above, the user, at this point in time, has at his or her disposal completed recordings for several Barney episodes, an Auburn basketball game, a news program, and whatever would have been recorded in the past six hours from this time. Looking at the Past Six Hours channel 303, the Auburn basketball game listing 3621 is highlighted and has a double arrow icon on the right most side of this listing in the IPG screen 3600 to indicate that the duration of this recording extends beyond the hour and one-half duration shown in the IPG screen 3600. Note that the Auburn basketball channel 305 also includes this Auburn vs. Georgia basketball game as a media content instance listing. The user can scroll to the right by using the right navigation arrow button 386 on the remote control device 380 (
In one implementation, since the user highlighted and selected the Brady Bunch listing at 5:15 p.m. (as shown in the information banner 3840 of
The record options screen 4000 is similar to that described already for
The PVR application 377 and the IPG application 394 and associated IPG modules can be implemented in hardware, software, firmware, or a combination thereof. In the preferred embodiment(s), the PVR application 377 and the IPG application 394 and associated IPG modules are implemented in software or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, as in an alternative embodiment, the PVR application 377 and the IPG application 394 and associated IPG modules may be implemented with any or a combination of the following technologies, which are all well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.
The PVR application 377 and the IPG application 394 and associated IPG modules, which comprises an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a nonexhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (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 if necessary, and then stored in a computer memory.
It should be emphasized that the above-described embodiments of the present invention, particularly, any “preferred embodiments” are merely possible examples of 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.
This application is a Divisional of co-pending U.S. application Ser. No. 10/253,115 entitled “PVR Channel and PVR IPG Information” filed Sep. 24, 2002, which is incorporated herein by reference. This application is related to copending U.S. application Ser. No. 09/827,470 entitled “System and Method for Providing User-Defined Media Presentations,” filed on Apr. 6, 2001, which issued on Jul. 1, 2008 as U.S. Pat. No. 7,395,547, which is entirely incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4393502 | Tanaka et al. | Jul 1983 | A |
4706121 | Young | Nov 1987 | A |
4908713 | Levine | Mar 1990 | A |
4963994 | Levine | Oct 1990 | A |
5253066 | Vogel | Oct 1993 | A |
5262856 | Lippman et al. | Nov 1993 | A |
5293357 | Hallenbeck | Mar 1994 | A |
5343250 | Iwamura | Aug 1994 | A |
5353121 | Young et al. | Oct 1994 | A |
5357276 | Banker et al. | Oct 1994 | A |
5361173 | Ishii et al. | Nov 1994 | A |
5371551 | Logan et al. | Dec 1994 | A |
5410343 | Coddington et al. | Apr 1995 | A |
5438423 | Lynch et al. | Aug 1995 | A |
5477262 | Banker et al. | Dec 1995 | A |
5479268 | Young et al. | Dec 1995 | A |
5488409 | Yuen et al. | Jan 1996 | A |
5508815 | Levine | Apr 1996 | A |
5530754 | Garfinkle | Jun 1996 | A |
5534911 | Levitan | Jul 1996 | A |
5568272 | Levine | Oct 1996 | A |
5600573 | Hendricks et al. | Feb 1997 | A |
5661526 | Harnamoto et al. | Aug 1997 | A |
5675375 | Riffee | Oct 1997 | A |
5694176 | Bruette et al. | Dec 1997 | A |
5701383 | Russo et al. | Dec 1997 | A |
5721815 | Ottesen et al. | Feb 1998 | A |
5724646 | Ganek et al. | Mar 1998 | A |
5729280 | Inoue et al. | Mar 1998 | A |
5790935 | Payton | Aug 1998 | A |
5809204 | Young et al. | Sep 1998 | A |
5815204 | Ueda | Sep 1998 | A |
5854887 | Kindell et al. | Dec 1998 | A |
5864639 | Chao | Jan 1999 | A |
5880768 | Lemmons et al. | Mar 1999 | A |
5889920 | Compoint et al. | Mar 1999 | A |
5890169 | Wong et al. | Mar 1999 | A |
5990885 | Stortz | May 1999 | A |
5915068 | Levine | Jun 1999 | A |
5963702 | Yamashita | Oct 1999 | A |
5974218 | Nagasaka et al. | Oct 1999 | A |
5978043 | Blonstein et al. | Nov 1999 | A |
5990881 | Inoue | Nov 1999 | A |
5990975 | Nan et al. | Nov 1999 | A |
5999691 | Takagi et al. | Dec 1999 | A |
6002832 | Yoneda | Dec 1999 | A |
6014727 | Creemer | Jan 2000 | A |
6018612 | Thomason et al. | Jan 2000 | A |
6023720 | Aref et al. | Feb 2000 | A |
6029160 | Cabrera et al. | Feb 2000 | A |
6032180 | Nishikawa | Feb 2000 | A |
6032216 | Schmuck et al. | Feb 2000 | A |
6032219 | Robinson et al. | Feb 2000 | A |
6052562 | Dorenbosch | Apr 2000 | A |
6055314 | Spies et al. | Apr 2000 | A |
6088722 | Herz et al. | Jul 2000 | A |
6094695 | Kornher | Jul 2000 | A |
RE36801 | Logan et al. | Aug 2000 | E |
6100883 | Hoarty | Aug 2000 | A |
6118498 | Reitmeier | Sep 2000 | A |
6118834 | Rasanen | Sep 2000 | A |
6151059 | Schein et al. | Nov 2000 | A |
6151688 | Wipfel et al. | Nov 2000 | A |
6163335 | Barraclough | Dec 2000 | A |
6167377 | Gillick et al. | Dec 2000 | A |
6175871 | Schuster et al. | Jan 2001 | B1 |
6177931 | Alexander | Jan 2001 | B1 |
6192340 | Abecasis | Feb 2001 | B1 |
6211858 | Moon et al. | Apr 2001 | B1 |
6216264 | Maze et al. | Apr 2001 | B1 |
6226441 | Hartung et al. | May 2001 | B1 |
6226447 | Sasaki et al. | May 2001 | B1 |
6230220 | Cohen et al. | May 2001 | B1 |
6233389 | Barton et al. | May 2001 | B1 |
6233390 | Yoneda | May 2001 | B1 |
6263308 | Heckerman | Jul 2001 | B1 |
6272610 | Katayama et al. | Aug 2001 | B1 |
6275506 | Fazel et al. | Aug 2001 | B1 |
6292624 | Saib et al. | Sep 2001 | B1 |
6298373 | Burns et al. | Oct 2001 | B1 |
6301313 | Gevargiz et al. | Oct 2001 | B1 |
6311011 | Kuroda | Oct 2001 | B1 |
6324338 | Wood et al. | Nov 2001 | B1 |
6330252 | Shojima | Dec 2001 | B1 |
6334217 | Kim | Dec 2001 | B1 |
6374336 | Peters et al. | Apr 2002 | B1 |
6378035 | Parry et al. | Apr 2002 | B1 |
6378129 | Zetts | Apr 2002 | B1 |
6385386 | Aotake | May 2002 | B1 |
6430363 | Sasaki et al. | Aug 2002 | B2 |
6434748 | Shen et al. | Aug 2002 | B1 |
6441832 | Tao et al. | Aug 2002 | B1 |
6445872 | Sano et al. | Sep 2002 | B1 |
6490000 | Schaefer et al. | Dec 2002 | B1 |
6498895 | Young et al. | Dec 2002 | B2 |
6501397 | Radha et al. | Dec 2002 | B1 |
6542203 | Shadwell et al. | Apr 2003 | B1 |
6543053 | Li et al. | Apr 2003 | B1 |
6570729 | Takayama | May 2003 | B1 |
6591421 | Sullivan | Jul 2003 | B1 |
6594329 | Susnow | Jul 2003 | B1 |
6601237 | Ten Kate et al. | Jul 2003 | B1 |
6625709 | Aiken et al. | Sep 2003 | B2 |
6625811 | Kaneko | Sep 2003 | B1 |
6642939 | Vallone et al. | Nov 2003 | B1 |
6654539 | Duruoz et al. | Nov 2003 | B1 |
6665869 | Ellis et al. | Dec 2003 | B1 |
6670971 | Oral | Dec 2003 | B1 |
6678463 | Pierre et al. | Jan 2004 | B1 |
6681396 | Bates et al. | Jan 2004 | B1 |
6701332 | Vella | Mar 2004 | B1 |
6714722 | Tsukidate | Mar 2004 | B1 |
6744967 | Kaminski et al. | Jun 2004 | B2 |
6757906 | Look et al. | Jun 2004 | B1 |
6766100 | Komar et al. | Jul 2004 | B1 |
6774926 | Ellis et al. | Aug 2004 | B1 |
6775843 | McDermott | Aug 2004 | B1 |
6782550 | Cao | Aug 2004 | B1 |
6798971 | Potrebic | Sep 2004 | B2 |
6803968 | Numata | Oct 2004 | B1 |
6822661 | Sai | Nov 2004 | B2 |
6850691 | Stam et al. | Feb 2005 | B1 |
6868225 | Brown et al. | Mar 2005 | B1 |
6920567 | Doherty et al. | Jul 2005 | B1 |
6970947 | Ebling et al. | Nov 2005 | B2 |
6971121 | West et al. | Nov 2005 | B2 |
6985567 | Vallinen et al. | Jan 2006 | B2 |
6985669 | Unger | Jan 2006 | B1 |
6993782 | Newberry et al. | Jan 2006 | B1 |
7003213 | Hasegawa | Feb 2006 | B1 |
7024676 | Klopfenstein | Apr 2006 | B1 |
7028329 | Mizutani | Apr 2006 | B1 |
7051173 | Tsuchiya et al. | May 2006 | B2 |
7177530 | Suzuka et al. | Feb 2007 | B1 |
7194563 | Plourde, Jr. | Mar 2007 | B2 |
7231136 | Sasaki et al. | Jun 2007 | B2 |
7245822 | Shigaki | Jul 2007 | B2 |
7257308 | Plourde, Jr. et al. | Aug 2007 | B2 |
7369749 | Ichioka et al. | May 2008 | B2 |
7395547 | Hammett et al. | Jul 2008 | B2 |
7409140 | Rodriguez et al. | Aug 2008 | B2 |
7443871 | Newson et al. | Oct 2008 | B2 |
7512136 | Kaminski et al. | Mar 2009 | B2 |
7512315 | Kaminski et al. | Mar 2009 | B2 |
7522817 | Srinivasan et al. | Apr 2009 | B2 |
7551832 | Plourde, Jr. | Jun 2009 | B2 |
7577336 | Srinivasan et al. | Aug 2009 | B2 |
7769925 | Plourde, Jr. | Aug 2010 | B2 |
7773859 | Potrebic et al. | Aug 2010 | B1 |
7779181 | Plourde, Jr. | Aug 2010 | B2 |
7835910 | Hakkani-Tur et al. | Nov 2010 | B1 |
7962011 | Plourde, Jr. et al. | Jun 2011 | B2 |
8015006 | Kennewick et al. | Sep 2011 | B2 |
8181205 | Russ et al. | May 2012 | B2 |
8321220 | Chotimongkol et al. | Nov 2012 | B1 |
8326634 | Di Cristo et al. | Dec 2012 | B2 |
8346563 | Hjelm et al. | Jan 2013 | B1 |
8400332 | Szwabowski et al. | Mar 2013 | B2 |
8565578 | Plourde, Jr. et al. | Oct 2013 | B2 |
8577201 | Kaminski et al. | Nov 2013 | B2 |
8620135 | Plourde, Jr. | Dec 2013 | B2 |
20010002224 | Sasaki et al. | May 2001 | A1 |
20010019658 | Barton et al. | Sep 2001 | A1 |
20010028782 | Ohno et al. | Oct 2001 | A1 |
20010032293 | Korst et al. | Oct 2001 | A1 |
20010033343 | Yap et al. | Oct 2001 | A1 |
20010033736 | Yap et al. | Oct 2001 | A1 |
20010043800 | Gotoh et al. | Nov 2001 | A1 |
20010051037 | Safadi et al. | Dec 2001 | A1 |
20020009285 | Safadi et al. | Jan 2002 | A1 |
20020012517 | Ichioka et al. | Jan 2002 | A1 |
20020019984 | Rakib | Feb 2002 | A1 |
20020037160 | Locket et al. | Mar 2002 | A1 |
20020040475 | Yap et al. | Apr 2002 | A1 |
20020046404 | Mizutani | Apr 2002 | A1 |
20020054752 | Wood et al. | May 2002 | A1 |
20020059623 | Rodriguez et al. | May 2002 | A1 |
20020059649 | Ichioka | May 2002 | A1 |
20020071653 | Cowley et al. | Jun 2002 | A1 |
20020073423 | Krakirian | Jun 2002 | A1 |
20020073425 | Aria et al. | Jun 2002 | A1 |
20020076195 | Nakajima et al. | Jun 2002 | A1 |
20020076203 | Takahashi | Jun 2002 | A1 |
20020090004 | Rinchiuso | Jul 2002 | A1 |
20020103889 | Markson et al. | Aug 2002 | A1 |
20020110352 | Potrebic | Aug 2002 | A1 |
20020122656 | Gates et al. | Sep 2002 | A1 |
20020133491 | Sim et al. | Sep 2002 | A1 |
20020136406 | Fitzhardinge et al. | Sep 2002 | A1 |
20020138641 | Taylor et al. | Sep 2002 | A1 |
20020146233 | Barton et al. | Oct 2002 | A1 |
20020147977 | Hammett et al. | Oct 2002 | A1 |
20020168178 | Rodriguez et al. | Nov 2002 | A1 |
20020174430 | Ellis et al. | Nov 2002 | A1 |
20020174445 | Miller et al. | Nov 2002 | A1 |
20020184637 | Perlman | Dec 2002 | A1 |
20020199185 | Kaminski et al. | Dec 2002 | A1 |
20030014753 | Beach et al. | Jan 2003 | A1 |
20030028706 | Okada | Feb 2003 | A1 |
20030035650 | Demas et al. | Feb 2003 | A1 |
20030040962 | Lewis | Feb 2003 | A1 |
20030068154 | Zylka | Apr 2003 | A1 |
20030095792 | Ogikubo | May 2003 | A1 |
20030099458 | Mizukami et al. | May 2003 | A1 |
20030105918 | Plourde, Jr. | Jun 2003 | A1 |
20030106064 | Plourde, Jr. | Jun 2003 | A1 |
20030108331 | Plourde, Jr. et al. | Jun 2003 | A1 |
20030110504 | Plourde, Jr. et al. | Jun 2003 | A1 |
20030110513 | Plourde, Jr. et al. | Jun 2003 | A1 |
20030121055 | Kaminski et al. | Jun 2003 | A1 |
20030128302 | Potrebic et al. | Jul 2003 | A1 |
20030149988 | Ellis | Aug 2003 | A1 |
20030154484 | Plourde et al. | Aug 2003 | A1 |
20030156826 | Sonoda et al. | Aug 2003 | A1 |
20030177495 | Needham et al. | Sep 2003 | A1 |
20030206719 | Bumgardner et al. | Nov 2003 | A1 |
20030215211 | Coffin | Nov 2003 | A1 |
20030228126 | Buxton | Dec 2003 | A1 |
20030231855 | Gates et al. | Dec 2003 | A1 |
20030235391 | Gates et al. | Dec 2003 | A1 |
20040005142 | Yoo et al. | Jan 2004 | A1 |
20040013406 | Barton et al. | Jan 2004 | A1 |
20040042103 | Mayer | Mar 2004 | A1 |
20040060063 | Russ et al. | Mar 2004 | A1 |
20040088726 | Ma et al. | May 2004 | A1 |
20040091249 | Mekenkamp et al. | May 2004 | A1 |
20040175094 | Mautner et al. | Sep 2004 | A1 |
20040181814 | Ellis et al. | Sep 2004 | A1 |
20040184776 | Inoue et al. | Sep 2004 | A1 |
20040197078 | Yoon et al. | Oct 2004 | A1 |
20040208477 | Bumgardner et al. | Oct 2004 | A1 |
20040218905 | Green et al. | Nov 2004 | A1 |
20040228609 | Nakamura et al. | Nov 2004 | A1 |
20040240840 | Ledermann et al. | Dec 2004 | A1 |
20040258389 | Castillo | Dec 2004 | A1 |
20040258396 | Nakamura et al. | Dec 2004 | A1 |
20050002638 | Putterman et al. | Jan 2005 | A1 |
20050002639 | Putterman et al. | Jan 2005 | A1 |
20050002640 | Putterman et al. | Jan 2005 | A1 |
20050041954 | Austin | Feb 2005 | A1 |
20050047749 | Kaibe | Mar 2005 | A1 |
20050078938 | Crohas | Apr 2005 | A1 |
20050111819 | Cormack et al. | May 2005 | A1 |
20050111838 | Arishima | May 2005 | A1 |
20050120373 | Thomas et al. | Jun 2005 | A1 |
20050132418 | Barton et al. | Jun 2005 | A1 |
20050158029 | Irikuchi et al. | Jul 2005 | A1 |
20050165598 | Cote et al. | Jul 2005 | A1 |
20050229213 | Ellis et al. | Oct 2005 | A1 |
20050246457 | Parry et al. | Nov 2005 | A1 |
20050259961 | Sano | Nov 2005 | A1 |
20050259962 | Sano | Nov 2005 | A1 |
20050259963 | Sano | Nov 2005 | A1 |
20050265694 | Green et al. | Dec 2005 | A1 |
20050276567 | Okuyama et al. | Dec 2005 | A1 |
20060002682 | Kanamori | Jan 2006 | A1 |
20060045472 | Poslinski | Mar 2006 | A1 |
20060051059 | Krakirian et al. | Mar 2006 | A1 |
20060140584 | Ellis et al. | Jun 2006 | A1 |
20060153523 | Ishida et al. | Jul 2006 | A1 |
20060177197 | Nakamura et al. | Aug 2006 | A1 |
20060188221 | Kee | Aug 2006 | A1 |
20060190983 | Plourde, Jr. | Aug 2006 | A1 |
20060193604 | Hoshi et al. | Aug 2006 | A1 |
20060206912 | Klarfield et al. | Sep 2006 | A1 |
20060228096 | Hoshino et al. | Oct 2006 | A1 |
20060239659 | Chng | Oct 2006 | A1 |
20070038436 | Cristo et al. | Feb 2007 | A1 |
20070047919 | Yoshida et al. | Mar 2007 | A1 |
20070077028 | Bodkin et al. | Apr 2007 | A1 |
20070110393 | Jang | May 2007 | A1 |
20070154174 | Sasaki et al. | Jul 2007 | A1 |
20070156392 | Balchandran et al. | Jul 2007 | A1 |
20070168601 | Plourde, Jr. | Jul 2007 | A1 |
20070226649 | Agmon | Sep 2007 | A1 |
20070226767 | Kaminski | Sep 2007 | A1 |
20080013920 | Plourde, Jr. et al. | Jan 2008 | A1 |
20080138033 | Rodriquez et al. | Jun 2008 | A1 |
20080181574 | Ellis et al. | Jul 2008 | A1 |
20080195388 | Bower et al. | Aug 2008 | A1 |
20080235017 | Satomura | Sep 2008 | A1 |
20090030697 | Cerra et al. | Jan 2009 | A1 |
20090196568 | Kaminski et al. | Aug 2009 | A1 |
20090202216 | Kaminski et al. | Aug 2009 | A1 |
20090204994 | Kaminski et al. | Aug 2009 | A1 |
20100128863 | Krum | May 2010 | A1 |
20100211695 | Steinmetz et al. | Aug 2010 | A1 |
20100251284 | Ellis et al. | Sep 2010 | A1 |
20110093459 | Dong et al. | Apr 2011 | A1 |
20110144999 | Jang et al. | Jun 2011 | A1 |
20110153324 | Ballinger et al. | Jun 2011 | A1 |
20110305440 | Plourde, Jr. et al. | Dec 2011 | A1 |
20120232885 | Barbosa et al. | Sep 2012 | A1 |
20120253802 | Heck et al. | Oct 2012 | A1 |
20120254227 | Heck et al. | Oct 2012 | A1 |
20120265531 | Bennett | Oct 2012 | A1 |
20120271617 | Nakajima et al. | Oct 2012 | A1 |
20120290293 | Hakkani-Tur et al. | Nov 2012 | A1 |
20130031476 | Coin et al. | Jan 2013 | A1 |
20130085756 | Chotimongkol et al. | Apr 2013 | A1 |
20130152092 | Yadgar | Jun 2013 | A1 |
20130185065 | Tzirkel-Hancock et al. | Jul 2013 | A1 |
20140025380 | Koch et al. | Jan 2014 | A1 |
20140257803 | Yu et al. | Sep 2014 | A1 |
20140379326 | Sarikaya et al. | Dec 2014 | A1 |
20140379353 | Boies et al. | Dec 2014 | A1 |
20150255061 | Xue et al. | Sep 2015 | A1 |
20150255069 | Adams | Sep 2015 | A1 |
20150278191 | Levit et al. | Oct 2015 | A1 |
20150310858 | Li et al. | Oct 2015 | A1 |
Number | Date | Country |
---|---|---|
2469517 | Aug 2011 | CA |
2571256 | Dec 2011 | CA |
2479347 | Jan 2012 | CA |
2446604 | Mar 2012 | CA |
2 469 554 | Oct 2012 | CA |
0 789 488 | Aug 1997 | EP |
0 834 798 | Apr 1998 | EP |
0 936 615 | Aug 1999 | EP |
1 014 715 | Jun 2000 | EP |
1 102 482 | May 2001 | EP |
1 113 668 | Jul 2001 | EP |
1 126 701 | Aug 2001 | EP |
2575128 | Apr 2013 | EP |
2-228842 | Nov 1990 | JP |
2002091477 | Mar 2002 | JP |
WO 9222983 | Dec 1992 | WO |
WO 9641740 | Dec 1996 | WO |
WO 9933265 | Jul 1999 | WO |
WO 9937045 | Jul 1999 | WO |
WO 9965237 | Dec 1999 | WO |
WO 0004726 | Jan 2000 | WO |
WO 0027114 | May 2000 | WO |
WO 0058967 | Oct 2000 | WO |
WO 0059214 | Oct 2000 | WO |
WO 0060500 | Oct 2000 | WO |
WO 0060591 | Oct 2000 | WO |
WO 0147238 | Jun 2001 | WO |
WO 0147249 | Jun 2001 | WO |
WO 0160064 | Aug 2001 | WO |
WO 0182600 | Nov 2001 | WO |
WO 0243353 | May 2002 | WO |
WO 02093299 | Nov 2002 | WO |
WO 02093901 | Nov 2002 | WO |
WO 03051044 | Jun 2003 | WO |
WO 03051047 | Jun 2003 | WO |
WO 03051052 | Jun 2003 | WO |
WO 03081915 | Oct 2003 | WO |
2005013262 | Feb 2005 | WO |
2013171481 | Nov 2013 | WO |
Entry |
---|
Canadian Office Action dated Oct. 19, 2010 cited in Application No. 2,469,554, 5 pgs. |
Canadian Office Action dated Jun. 2, 2011 cited in Application No. 2,469,542, 4 pgs. |
European Summons to Attend Oral Proceedings dated Aug. 18, 2011 cited in Application No. 02791374.8, 6 pgs. |
Canadian Office Action dated Nov. 19, 2012 cited in Application No. 2,469,542, 5 pgs. |
U.S. Office Action dated Jun. 9, 2008 cited in U.S. Appl. No. 10/008,439, 23 pgs. |
U.S. Final Office Action dated Jan. 27, 2009 cited in U.S. Appl. No. 10/008,439, 24 pgs. |
U.S. Office Action dated Aug. 21, 2009 cited in U.S. Appl. No. 10/008,439, 17 pgs. |
U.S. Final Office Action dated Jan. 22, 2010 cited in U.S. Appl. No. 10/008,439, 26 pgs. |
U.S. Office Action dated Oct. 7, 2010 cited in U.S. Appl. No. 10/008,439, 29 pgs. |
U.S. Office Action dated Apr. 13, 2011 cited in U.S. Appl. No. 10/008,439, 14 pgs. |
U.S. Final Office Action dated Oct. 7, 2011 cited in U.S. Appl. No. 10/008,439, 15 pgs. |
U.S. Office Action dated Mar. 12, 2013 cited in U.S. Appl. No. 10/008,439, 14 pgs. |
T. Raadt et al., “Cryptography in OpenBSD: An Overview,” In Proc. of the 1999 USENIX Annual Technical Conference, Freenix Track, pp. 93-101, Jun. 1999. |
U.S. Appl. No. 10/143,647, filed May 10, 2002 entitled “Managing Time Shift Buffers”. |
U.S. Appl. No. 12/389,082, filed Feb. 19, 2009 entitled “Retention of Program Portions Viewed in Prior Displayed TV Channels”. |
U.S. Appl. No. 12/389,093, filed Feb. 19, 2009 entitled “Management of TV Programs by their Buffered Lengths”. |
U.S. Appl. No. 10/143,123, filed May 10, 2002, entitled “Channel Buffering and Display Management System for Multi-Tuner Set-Top Box”. |
U.S. Appl. No. 12/389,107, filed Feb. 19, 2009, entitled “Buffering of Prior Displayed Television Channels Upon Accessing a Different Channel”. |
U.S. Appl. No. 12/033,203, filed Feb. 19, 2008, entitled “Multi-Tuner Multi-Buffer Digital Home Communication Terminal”. |
U.S. Appl. No. 11/751,754, filed May 22, 2007, entitled “Managing Time Shift Buffers”. |
U.S. Appl. No. 10/008,439, filed Dec. 6, 2001 entitled “Dividing and Managing Time-Shift Buffering into Program Specific Segments Based on Defined Durations”. |
U.S. Appl. No. 10/010,270, filed Dec. 6, 2001 entitled “Controlling Substantially Constant Buffer Capacity for Personal Video Recording with Consistent User Interface of Available Disk Space”. |
U.S. Appl. No. 10/102,043, filed Mar. 20, 2002, entitled “Composite Buffering”. |
U.S. Appl. No. 13/159,406, filed Jun. 13, 2011 entitled “Management of Buffer Capacity for Video Recording and Time Shift Operations”. |
U.S. Appl. No. 10/005,628, filed Dec. 5, 2001 entitled “Disk Driver Cluster Management of Time Shift Buffer with File Allocation Table Structure”. |
U.S. Appl. No. 11/679,625, filed Feb. 27, 2007 entitled “Disk Driver Cluster Management of Time Shift Buffer With File Allocation Table Structure”. |
U.S. Appl. No. 11/381,892, filed May 5, 2006 entitled “Disk Driver Cluster Management of Time Shift Buffer with File Allocation Table Structure”. |
U.S. Appl. No. 10/253,115, filed Sep. 24, 2002 entitled “PVR Channel and PVR IPG Information”. |
U.S. Appl. No. 10/010,781, filed Dec. 5, 2001 entitled “Application Management and Interface for Cluster Control of Time Shift Buffer”. |
U.S. Appl. No. 09/827,470, filed Apr. 6, 2001 entitled “System and Method for Providing User-Defined Media Presentations”. |
U.S. Appl. No. 10/008,624, filed Dec. 6, 2001 entitled “Converting Time-Shift Buffering for Personal Video Recording Into Permanent Recordings”. |
U.S. Appl. No. 11/772,966, filed Jul. 3, 2007, entitled “Converting Time-Shift Buffering for Personal Video Recording Into Permanent Recordings”. |
U.S. Appl. No. 10/034,028, filed Dec. 20, 2001, entitled “Program Position User Interface for Personal Video Recording Time Shift Buffer”. |
U.S. Appl. No. 10/015,349, filed Dec. 11, 2001, entitled “Controlling Personal Video Recording Functions from Interactive Television” (Abandoned). |
U.S. Appl. No. 09/918,376, filed Jul. 30, 2001, entitled “Digital Subscriber Television Networks with Local Physical Storage Devices and Virtual Storage”. |
Dish Network DVR/PVR Receiver—DVR Receiver (Dual-Turner), DVR 921 High Definition; DVR Receiver (Dual-Turner), found at www.afreedish.com/com/dish-network-dvr-receiver.html; 4 pgs.; printed Jul. 13, 2007. |
IPTV Dual Turner SD-DVR; entitled “Pace Introduces Vegas DVR Product”; found at http://www.iptv.industry.com/ar/3o.htm; 3 pgs.; printed Jul. 13, 2007. |
Mavromatic; entitled “Pioneer's Dual Tuner HD-DVR”; found at http://www.mavromatic.com/archives/000228; 4 pgs.; printed Jul. 13, 2007. |
Motorola—Connected Home Solutions—Digital Video Solutions—DCH3416 Host Set-top; DCH3416 Host set-top; found at http://broadband.motorola.com/ business/digitalvideo/product_dch3416_settop.asp; 2 pgs.; printed Jul. 13, 2007. |
Motorola DVR; entitled “Motorola Dual-Tuner DVR High-Definition Set-top DCT6412”; found at http://broadband.motorola.com/dvr/dct6412asp; 4 pgs.; printed Jul. 13, 2007. |
Sanna et al., Special Edition Using Windows NT Workstation 4.0, Second Edition, pp. 128-143 (cited in Jul. 26, 2006 OA). |
TiVo.com Buy TiVo; entitled “Choose a price plan”, found at http://dynamic.tivo.com/2.0boxdetails.asp?box-series280hrDTDVR; 2 pages; printed Jul. 13, 2007. |
International Search Report cited in Application No. PCT/US02/14887 dated Nov. 12, 2002, 6 pgs. |
International Search Report cited in Application No. PCT/US02/14874 dated Nov. 20, 2002, 4 pgs. |
PCT Written Opinion Appl. No. PCT/US02/14874 dated Feb. 11, 2003, 5 pgs. |
International Search Report cited in Application No. PCT/US02/38868 dated Mar. 26, 2003, 5 pgs. |
International Search Report cited in Application No. PCT/US02/38778 dated Apr. 3, 2003, 4 pgs. |
International Search Report cited in Application No. PCT/US02/38777 dated Apr. 4, 2003, 4 pgs. |
International Search Report cited in Application No. PCT/US03/08597 dated Jul. 11, 2003, 4 pgs. |
PCT Written Opinion Appl. No. PCT/US02/38868 dated Sep. 25, 2003, 5 pgs. |
PCT Written Opinion Appl. No. PCT/US02/38778 dated Oct. 27, 2003, 5 pgs. |
PCT Written Opinion Appl. No. PCT/US02/38777 dated Oct. 28, 2003, 5 pgs. |
PCT Written Opinion of the International Preliminary Examining Authority Appl. No. PCT/US03/08597 dated Oct. 28, 2004, 5 pgs. |
Canadian Office Action dated Jun. 22, 2006 cited in Appln No. 2,446,604, 3 pgs. |
Canadian Office Action dated Jan. 11, 2007 cited in Appln No. 2,446,617, 3 pgs. |
Canadian Office Action dated Mar. 19, 2007 cited in Appln No. 2,469,554, 2 pgs. |
Supplementary European Search Report cited in Application No. 02 804 729.8 dated Jun. 21, 2007. |
European Examination dated Nov. 14, 2007 cited in Appln No. 02 804 729.8. |
Canadian Office Action dated Apr. 8, 2008 cited in Appln No. 2,469,558. |
Supplementary European Search Report cited in Application No. 03 745 157.2 dated Jun. 19, 2008. |
Canadian Office Action dated Sep. 16, 2008 cited in Appln No. 2,446,617. |
Canadian Office Action dated Feb. 10, 2009 cited in Appln No. 2,479,347. |
Supplementary European Search Report cited in Application No. 02 791 374.8 dated Feb. 13, 2009. |
Canadian Office Action dated Feb. 13, 2009 cited in Appln No. 2,469,542. |
Supplementary European Search Report cited in Application No. 02 736 739.0 dated Mar. 23, 2009. |
Canadian Office Action dated Mar. 31, 2009 cited in Appln No. 2,571,256. |
European Examination dated Apr. 2, 2009 cited in Appln No. 02 794 161.6. |
European Search Report cited in Application No. 02747828.8 dated Jul. 3, 2009. |
European Examination dated Oct. 13, 2009 cited in Appln No. 02 736 739.0, 3 pgs. |
European Examination dated Oct. 22, 2009 cited in Appln No. 02 794 161.6, 3 pgs. |
European Examination dated Dec. 17, 2009 cited in Appln No. 02 747 828.8. |
Canadian Office Action dated Apr. 12, 2010 cited in Appln No. 2,479,347, 4 pages. |
Canadian Office Action dated Apr. 14, 2010 cited in Appln No. 2,469,542, 4 pages. |
European Examination dated May 25, 2010 cited in Appln No. 02 791 374.8, 5 pages. |
Canadian Office Action dated Dec. 20, 2010 cited in Appln No. 2,446,604, 3 pgs. |
European Communication dated Feb. 17, 2011 cited in Appln. No. 02 747 828.8, 5 pages. |
European Communication dated Jan. 17, 2012 cited in Application No. 02 736 739.0, 4 pages. |
Canadian Office Action dated Oct. 2, 2012 cited in Application No. 2,658,766, 2 pgs. |
U.S. Official Action dated Aug. 17, 2004 in U.S. Appl. No. 10/253,115, 17 pgs. |
U.S. Official Action dated Oct. 21, 2004 in U.S. Appl. No. 10/102,043, 13 pgs. |
U.S. Official Action dated Mar. 21, 2005 in U.S. Appl. No. 10/005,628, 7 pgs. |
U.S. Official Action dated Apr. 7, 2005 in U.S. Appl. No. 10/253,115, 16 pgs. |
U.S. Official Action dated Apr. 25, 2005 in U.S. Appl. No. 09/827,470, 15 pgs. |
U.S. Official Action dated Jul. 25, 2005 in U.S. Appl. No. 10/253,115, 13 pgs. |
U.S. Official Action dated Oct. 19, 2005 in U.S. Appl. No. 09/827,470, 20 pgs. |
U.S. Official Action dated Feb. 8, 2006 in U.S. Appl. No. 10/010,270, 26 pgs. |
U.S. Official Action dated Apr. 6, 2006 in U.S. 09/827,470, 6 pgs. |
U.S. Official Action dated May 3, 2006 in U.S. Appl. No. 10/008,624, 19 pgs. |
U.S. Official Action dated May 11, 2006 in U.S. 10/253,115, 13 pgs. |
U.S. Official Action dated Jun. 30, 2006 in U.S. Appl. No. 10/005,628, 9 pgs. |
U.S. Official Action dated Jul. 26, 2006 in U.S. Appl. No. 10/010,270, 20 pgs. |
U.S. Official Action dated Sep. 8, 2006 in U.S. Appl. No. 09/827,470, 19 pgs. |
U.S. Official Action dated Oct. 19, 2006 in U.S. Appl. No. 10/008,624, 15 pgs. |
U.S. Official Action dated Jan. 25, 2007 in U.S. Appl. No. 09/827,470, 19 pgs. |
U.S. Official Action dated Feb. 26, 2007 in U.S. Appl. No. 10/010,270, 15 pgs. |
U.S. Official Action dated May 21, 2007 in U.S. Appl. No. 10/143,647, 8 pgs. |
U.S. Official Action dated Aug. 10, 2007 in U.S. Appl. No. 10/010,270, 16 pgs. |
U.S. Official Action dated Aug. 28, 2007 in U.S. Appl. No. 09/827,470, 19 pgs. |
U.S. Official Action dated Sep. 5, 2007 in U.S. Appl. No. 11/381,892, 9 pgs. |
U.S. Official Action dated Oct. 16, 2007 in U.S. 10/253,115, 14 pgs. |
U.S. Official Action dated Nov. 19, 2007 in U.S. Appl. No. 10/143,647, 8 pgs. |
U.S. Official Action dated Jan. 18, 2008 in U.S. Appl. No. 10/253,115, 12 pgs. |
U.S. Official Action dated Apr. 2, 2008 in U.S. Appl. No. 10/010,270, 30 pgs. |
U.S. Official Action dated Apr. 17, 2008 in U.S. Appl. No. 11/381,892, 8 pgs. |
U.S. Official Action dated Jul. 21, 2008 in U.S. Appl. No. 10/253,115, 18 pgs. |
U.S. Office Action dated Aug. 8, 2008 in U.S. Appl. No. 10/010,781, 31 pgs. |
U.S. Office Action dated Aug. 19, 2008 in U.S. Appl. No. 10/008,439, 15 pgs. |
U.S. Official Action dated Nov. 28, 2008 in U.S. Appl. No. 11/381,892, 9 pgs. |
U.S. Official Action dated Feb. 19, 2009 in U.S. Appl. No. 10/010,270, 23 pgs. |
U.S. Official Action dated Jun. 12, 2009 in U.S. Appl. No. 11/381,892, 11 pgs. |
U.S. Official Action dated Jul. 6, 2009 in U.S. Appl. No. 11/679,625, 8 pgs. |
U.S. Official Action dated Jul. 22, 2009 in U.S. Appl. No. 11/751,754, 9 pgs. |
U.S. Official Action dated Oct. 9, 2009 in U.S. Appl. No. 11/381,892, 6 pgs. |
U.S. Official Action dated Oct. 13, 2009 in U.S. Appl. No. 10/010,270, 16 pgs. |
U.S. Official Action dated Nov. 12, 2009 in U.S. Appl. No. 11/679,625, 10 pgs. |
U.S. Official Action dated Dec. 1, 2009 in U.S. Appl. No. 11/751,754, 20 pgs. |
U.S. Official Action dated Mar. 17, 2010 in U.S. Appl. No. 10/010,270, 48 pgs. |
U.S. Official Action dated Jun. 18, 2010 in U.S. Appl. No. 11/751,754, 8 pgs. |
U.S. Official Action dated Jan. 21, 2011 in U.S. Appl. No. 11/751,754, 11 pgs. |
U.S. Official Action dated Jun. 20, 2011 in U.S. Appl. No. 11/751,754, 10 pgs. |
U.S. Office Action dated Dec. 27, 2011 in U.S. Appl. No. 11/751,754, 10 pgs. |
U.S. Office Action dated Feb. 14, 2012 in U.S. Appl. No. 11/772,966, 59 pgs. |
U.S. Office Action dated Mar. 27, 2012 in U.S. Appl. No. 12/389,107, 23 pgs. |
U.S. Office Action dated Apr. 10, 2012 in U.S. Appl. No. 12/033,203, 39 pgs. |
U.S. Office Action dated Jul. 3, 2012 in U.S. Appl. No. 11/772,966, 43 pgs. |
U.S. Office Action dated Jul. 16, 2012 in U.S. Appl. No. 12/033,203, 10 pgs. |
U.S. Office Action dated Aug. 30, 2012 in U.S. Appl. No. 12/389,107, 5 pgs. |
U.S. Office Action dated Nov. 7, 2012 in U.S. Appl. No. 11/772,966, 46 pgs. |
U.S. Office Action dated Dec. 26, 2012 in U.S. Appl. No. 12/033,203, 11 pgs. |
U.S. Office Action dated Mar. 29, 2013 in U.S. Appl. No. 11/751,754, 11 pgs. |
U.S. Office Action dated May 14, 2013 in U.S. Appl. No. 11/772,966, 43 pgs. |
U.S. Office Action dated Jul. 10, 2013 in U.S. Appl. No. 12/033,203, 13 pgs. |
U.S. Office Action dated Nov. 26, 2013 in U.S. Appl. No. 12/033,203, 12 pgs. |
U.S. Office Action dated Dec. 6, 2013 in U.S. Appl. No. 11/751,754, 10 pgs. |
U.S. Office Action dated Mar. 20, 2014 in U.S. Appl. No. 13/159,406, 11 pgs. |
U.S. Office Action dated Mar. 24, 2014 in U.S. Appl. No. 12/033,203, 12 pgs. |
International Search Report dated Feb. 7, 2003 cited in Appl. No. PCT/US02/37282, 4 pgs. |
Canadian Office Action dated Jul. 30, 2009 cited in Appl. No. 2,469,402, 2 pgs. |
Canadian Office Action dated Mar. 11, 2010 cited in Appl. No. 2,469,402, 2 pgs. |
European Office Action dated May 7, 2010 with Supplemental European Search Report dated Apr. 27, 2010 cited in Appl. No. 02 782 336.8, 3 pgs. |
Canadian Office Action dated May 31, 2010 cited in Appl. No. 2,499,920, 5 pgs. |
European Office Action dated Feb. 24, 2011 cited in Appl. No. 02 782 336.8, 6 pgs. |
Canadian Office Action dated Jun. 15, 2011 cited in Appl. No. 2,499,920, 3 pgs. |
European Office Action dated Aug. 31, 2011 cited in Appl. No. 02 782 336.8, 5 pgs. |
U.S. Office Action dated Aug. 28, 2014 in U.S. Appl. No. 13/159,406, 30 pgs. |
EP Communication dated Jun. 3, 2014 in Appln No. 03 745 157.2, 6 pgs. |
U.S. Office Action dated Jan. 16, 2015 in U.S. Appl. No. 13/159,406, 16 pages. |
U.S. Appl. No. 14/227,492, filed Mar. 27, 2014, entitled “Flexible Schema for Language Model Customization”. |
Bohus, et al., “Olympus: An Open-Source Framework for Conversational Spoken Language Interface Research”, In Proceedings of the Workshop on Bridging the Gap: Academic and Industrial Research in Dialog Technologies, Apr. 2007, 8 pages. |
Dos Reis Mota, Pedro Jose, “LUP: A Language Understanding Platform”, A Dissertation for the Degree of Master of Information Systems and Computer Engineering, Jul. 2012, 128 pages. |
Eagle, et al., “Common Sense Conversations: Understanding Casual Conversation using a Common Sense Database”, In Proceedings of the Artificial Intelligence, Information Access, and Mobile Computing Workshop, Aug. 2003, 6 pages. |
He et al; “What is Discriminative Learning”; Achorn International; Jun. 25, 2008; 25 pgs. (cited in Jul. 7, 2015 ISR). |
Hoffmeister et al., “Log-Linear Model Combination with Word-Dependent Scaling Factors”; Human Language Technology and Pattern Recognition Computer Science Department; Sep. 6-10; Brighton UK; Copyright © 2009 ISCA; 4 pgs. (cited in Jul. 7, 2015 ISR). |
Huang et al., “Unified Stochastic Engine (USE) for Speech Recognition”; School of Computer Science; 1993 IEEE; 4 pgs. (cited in Jul. 7, 2015 ISR). |
“Integrated Development Environments for Natural Language Processing”, Published on: Oct. 2001, Available at: http://www.textanalysis.com/TAI-IDE-WP.pdf; 13 pgs. |
Keshtkar et al., “A Corpus-based Method for Extracting Paraphrases of Emotion Terms”; Proceedings of the NAACL HLT 2010 Workshop on Computational Appraoches to Analysis and Generation of Emotion in Text; Jun. 2010; 10 pgs. (cited in Jun. 3, 2015 ISR). |
Ko, et al., “Cammia—A Context-Aware Spoken Dialog System for Mobile Environments”, In Automatic Speech Recognition and Understanding Workshop, Jul. 29, 2011, 2 pages. |
Lee, et al., “Intention-Based Corrective Feedback Generationusing Context-Aware Model”, In Proceedings of the Second International Conference on Computer Supported Education, Apr. 7, 2010, 8 pages. |
Liu, et al., “Language Model Combination and Adaptation using Weighted Finite State Transducers”, In Proceedings of IEEE International Conference on Acoustics Speech and Signal Processing, Mar. 14, 2010, 4 pages. |
Moreira, et al., “Towards the Rapid Development of a Natural Language Understanding Module”, In Proceedings of the 10th International Conference on Intelligent Virtual Agents, Jan. 2011, 7 pages. |
Sarukkai et al., “Word Set Probability Boosting for Improved Spontaneous Dialog Recognition”; IEEE Transactions on Speech and Audio Processing, vol. 5, No. 5, Sep. 1997; 13 pgs. (cited in Jul. 7, 2015 ISR). |
Seneff, et al., “Galaxy-II: A Reference Architecture for Conversational System Development”, In Proceedings of the 5th International Conference on Spoken Language Processing, Nov. 2008, 4 pages. |
Sing, et al., “Domain Metric Knowledge Model for Embodied Conversation Agents”, In 5th International Conference on Research, Innovation & Vision for the Future, Mar. 5, 2007, 7 pages. |
Xue, et al., “Singular Value Decomposition Based Low-Footprint Speaker Adaptation and Personalization for Deep Neural Network”, In Proceedings of the IEEE International Conference on Acoustics, Speech and Signal Processing, May 4, 2014, pp. 6359-6363 (cited in Jun. 25, 2015 ISR). |
International Search Report and Written Opinion Issued in PCT Application No. PCT/US2014/041014, dated Oct. 2, 2014, 9 Pages. |
International Search Report and Written Opinion Issued in PCT Application No. PCT/US2014/041023, dated Jun. 3, 2015, 17 Pages. |
International Search Report and Written Opinion Issued in PCT Application No. PCT/US2015/017872, dated Jun. 25, 2015, 11 Pages. |
International Search Report and Written Opinion Issued in PCT Application No. PCT/US2015/029334, dated Jul. 7, 2015, 12 Pages. |
International Search Report and Written Opinion Issued in PCT Application No. PCT/US2015/021921, dated Jul. 17, 2015, 11 Pages. |
Preliminary Report on Patentability dated Sep. 15, 2015 in Appln No. PCT/US2014/041014, 6 pgs. |
U.S. Official Action dated May 6, 2015 in U.S. Appl. No. 13/923,969, 12 pgs. |
U.S. Official Action dated May 28, 2015 in U.S. Appl. No. 13/923,917, 18 pgs. |
U.S. Official Action dated Jul. 1, 2015 in U.S. Appl. No. 14/201,704, 17 pgs. |
Response dated Aug. 6, 2015 in U.S. Appl. No. 13/923,969, 7 pgs. |
Response dated Aug. 7, 2015 in U.S. Appl. No. 13/923,917, 10 pgs. |
U.S. Official Action dated Aug. 13, 2015 in U.S. Appl. No. 14/227,492, 41 pgs. |
U.S. Official Action dated Sep. 29, 2015 in U.S. Appl. No. 13/923,917, 9 pgs. |
U.S. Official Action dated Oct. 1, 2015 in U.S. Appl. No. 13/920,323, 34 pgs. |
Notice of Allowance dated Oct. 1, 2015 in U.S. Appl. No. 13/923,969, 7 pgs. |
Notice of Allowance dated Nov. 30, 2015 in U.S. Appl. No. 13/923,969, 12 pgs. |
Number | Date | Country | |
---|---|---|---|
20120227072 A1 | Sep 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10253115 | Sep 2002 | US |
Child | 13471682 | US |