Systems and methods for relocating media

- Rovi Guides, Inc.

A system and method may be provided that allows users to store, retrieve, and manipulate on-demand media content and data stored on a remote server network in an on-demand media delivery system. More particularly, the system may allow a user to access his or her on-demand media account from user equipment in different locations as long as the current user equipment can communicate with a remote server that stores user-specific information. The system upon user selection may freeze the delivery of on-demand media at a particular point and allow the user to resume the media at a later time from some other network location in system. Users may upload personal images or files to an on-demand delivery server for later retrieval and display. Users may be permitted to assign access rights to the uploaded files.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/023,842, filed Feb. 9, 2011, which is a continuation of U.S. patent application Ser. No. 12/200,593, filed Aug. 28, 2008 (now U.S. Pat. No. 7,917,933), which is a continuation of U.S. patent application Ser. No. 09/974,646, filed Oct. 9, 2001, (now U.S. Pat. No. 7,650,621), which claims the benefit of U.S. Provisional Patent Application No. 60/239,407 filed Oct. 11, 2000, U.S. Provisional Patent Application No. 60/252,171 filed Nov. 20, 2000, and U.S. Provisional Patent Application No. 60/270,351, filed Feb. 21, 2001, which are hereby incorporated by reference herein in their entireties.

BACKGROUND OF THE INVENTION

The present invention relates to on-demand media delivery systems and more particularly, to on-demand media delivery systems that have user-related memory for providing system enhancements.

In some known video on-demand systems, a set-top box may be used to receive on-demand video from cable system headends. Such set-top boxes may communicate or may deliver the video and/or other functionality to television sets, VCRs, or other local devices. These systems have been deficient in allowing users to relocate their video-on-demand service to different locations. These systems may have also been deficient in providing adequate relocation techniques, deficient in allowing users to upload and access their personal videos, graphics, images, or photographs and deficient in allowing users to share media.

Systems have been developed that use hard disk technology or other recording technology to store videos of programs locally. Examples of hard disk systems are described, in Hassell et al. U.S. patent application Ser. No. 09/157,256 filed Sep. 17, 1998, which is hereby incorporated by reference herein in its entirety. Hard-disk based products have also been developed by TiVo, Inc. of Sunnyvale, Calif., and Replay Networks, Inc. of Mountainview, Calif. These systems have been deficient in meeting user needs. For example, these systems do not allow the user to relocate to other households with continued access to the recorded materials.

Television platforms have also been developed that include a return path from a user's set-top box to a cable system headend. For example, client-server based program guides have been developed in which set-top boxes are in client-server arrangements with the cable system headends. These arrangements allow for two-way communication between the cable system headends and set-top boxes. These servers typically provide program listings information (e.g., program titles and broadcast times) to the set-top boxes in response to requests generated from the set-top boxes. Client-server television program guides have also been developed where programming and settings may be recorded on a remote server. These known systems have been deficient in various ways. For example, servers in such systems (servers at the cable system headends) have been deficient in providing sufficient mobility features.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, on-demand media delivery systems and methods may be provided for remote storage of personal media of users, for sharing of stored media and for features for relocating media-on-demand services. Such features and functionality may be provided based on storing user related information on an on-demand media delivering server. Such features may be provided independent of the type of equipment (e.g., set-top box, personal computer, etc.) that is used to interact with the system.

The system may have a relocate feature that may allow a user to freeze on-demand media delivery on one user equipment and resume delivery and viewing from another user equipment (e.g., user equipment in a household that is different from the household where that user was previously watching the on-demand media delivery content when that user froze the delivery). On demand media content that is presented in a live feed may be remotely recorded for a user when a user selects to freeze the delivery of the media content.

User-specific data may sometimes be stored in a user profile. The system may allow a user profile to be remotely accessed and manipulated by a user when that user has been identified by the system. A user may also upload or download any type of data, file, or program between local user equipment and a server in the on-demand media system. Uploaded data, files, or programs may be assigned private access rights or assigned public or group access rights. Access rights may include the right to read, write, manipulate, upload, or download data, files or programs.

An auto-customization feature may be included in the on-demand media system. An on-demand media system may use stored user equipment preferences to configure and customize user equipment. The user equipment may be configured or customized when a user logs in from practically any user equipment in the system. User equipment preferences may, for example, include volume settings, preferred program settings, menu configurations, and channel block settings.

These and other features and functionalities that take advantage of the special capabilities of on-demand media servers and take advantage of storing user related information and/or personal media on an on-demand media server are also described below.

BRIEF DESCRIPTION OF THE DRAWINGS

The principles and advantages of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, in which the same reference numerals denote the same structural elements throughout, and in which:

FIG. 1 is a diagram that is illustrative of a network topology of an on-demand media delivery system in accordance with the principles of the present invention;

FIG. 2 is a diagram that is illustrative of a network topology of an on-demand media delivery system in accordance with the principles of the present invention;

FIG. 3 is a diagram that is illustrative of a remote control for an on-demand media delivery system in accordance with the principles of the present invention;

FIG. 4A is a diagram that is illustrative of a navigation display screen in accordance with the principles of the present invention;

FIG. 4B is a diagram that is illustrative of a video on demand directory display screen in accordance with the principles of the present invention;

FIG. 5A is a diagram that is illustrative of a movie listings display screen in accordance with the principles of the present invention;

FIG. 5B is a diagram that is illustrative of a movie ordering display screen in accordance with the principles of the present invention;

FIG. 6A is a diagram that is illustrative of a movie remote-control display screen in accordance with the principles of the present invention;

FIG. 6B is a diagram that is illustrative of a login display screen in accordance with the principles of the present invention;

FIG. 7A is a diagram that is illustrative of a relocate confirmation display screen in accordance with the principles of the present invention;

FIG. 7B is a diagram that is illustrative of a continue after relocate display screen in accordance with the principles of the present invention;

FIG. 7C is a flow chart that is illustrative of a relocation process in accordance with the principles of the present invention;

FIG. 8 is a flow chart illustrative of a relocation process that includes a live content feed option in accordance with the principles of the present invention;

FIG. 9 is a flow chart that is illustrative of a data and media access process in accordance with the principles of the present invention;

FIG. 10 is a diagram that is illustrative of a profile display screen in accordance with the principles of the present invention;

FIG. 11 is a diagram that is illustrative of an account administration display screen in accordance with the principles of the present invention;

FIG. 12 is a diagram that is illustrative of an auto-configure display screen in accordance with the principles of the present invention;

FIG. 13 is a flow chart illustrative of an auto-configure process in accordance with the principles of the present invention;

FIG. 14A is a diagram that is illustrative of an upload file display screen in accordance with the principles of the present invention;

FIG. 14B is a flow chart illustrative of an upload file process in accordance with the principles of the present invention;

FIG. 15A is a diagram that is illustrative of a display screen for designating a file as public or private in accordance with the principles of the present invention;

FIG. 15B is a diagram that is illustrative of a designate access data display screen in accordance with the principles of the present invention;

FIG. 16A is a diagram that is illustrative of a file search display screen in accordance with the principles of the present invention; and

FIG. 16B is a diagram that is illustrative of a file found display screen in accordance with the principles of the present invention.

 DETAILED DESCRIPTION

Turning first to FIG. 1, network topology 100 shows one embodiment of a system architecture for an on-demand media delivery system in accordance with the principles of the present invention. Included in network topology 100 may be any number of remote server networks 110, service providers 120, program sources 130, program listings sources 140, media distribution facilities 150, user equipment 160, communications networks 170, distribution servers 180, and remote storage devices 190.

Media may be provided from programming sources 130 to media distribution facilities such as media distribution facility 150 either directly or through communications network 170. Programming sources 130 may be any suitable source of television or music programming, such as television and music production studios, etc. Additionally, programming sources 130 may provide programming that is to be broadcast according to a schedule (e.g., a schedule that is published in advance).

On-demand media programming may be provided using distribution server 180 or other suitable on-demand media equipment. On-demand media servers or VOD servers may be servers that are tailored towards storing, manipulating, and processing images and videos. Distribution server 180 may include a plurality of servers wherein some of which are specialized servers for supporting on-demand media services. If desired, distribution server 180 or other on-demand media equipment may be located at network nodes associated with media distribution facility 150 or other suitable locations in network topology 100.

Media distribution facility 150 may be a cable system headend, a satellite television distribution facility, a television broadcast facility, or any other suitable facility for distributing on-demand media content, television, and music programming to users.

Media distribution facility 150 may also be connected to various user equipment 160. Such user equipment 160 may, for example, be located in the homes of users. User equipment 160 may include, for example, user television equipment, user computer equipment, and user audio equipment.

User equipment 160 may receive television and music programming, on-demand media programs, and other information from media distribution facility 150 either directly or through communications network 170. User equipment 160 may also transmit and receive signals from media distribution facility 150, remote server network 110, and any other device in network topology 100 through communications network 170.

Program listings source 140 may be used to provide user equipment with television program listings information such as scheduled broadcast times, titles, channels, ratings information (e.g., parental ratings and critic's ratings), detailed title descriptions, genre or category information (e.g., sports, news, movies, etc.), information on actors and actresses, running times, etc. Program listings source 140 may provide program listings information to television distribution facility 150 either directly or indirectly through communications network 170.

User equipment 160 may use the program listings information to display program listings and program information for television programming, for on-demand media programming, and for PVR programming. An interactive television program guide application or other suitable application may be used to display such information on a display device that is part of user equipment 160.

Communications network 170 may provide a communications hub between the elements in network topology 100. Communications networks 170 may include a number of different networks such as a public switched telephone network, a packet-based network, a wireless network or the Internet.

An on-line program guide may be provided by a server located in remote server network 110, in distribution server 180, or by a server located in any element included in network topology 100. Remote server 110 may include remote storage 190. Remote storage 190 may be used to store software, media content, and data. In some embodiments, remote storage 190 may provide a user interfacing with user equipment 160 with the capability to store, manipulate, and retrieve media content, user-specific data, and any other type of data.

Remote server network 110 may include one or more VOD specialized servers. VOD servers are tailored towards storing, manipulating, and processing images and video. For example, VOD and VOD-related servers have been developed by Concurrent Computer Corporation of Atlanta, Ga., nCUBE of Foster City, Calif., DIVA Systems Corporation of Princeton, N.J., and SeaChange International of Maynard, Mass.

Interactive television applications other than program guide applications may use service providers such as service provider 120. For example, a home shopping service may be supported by a service provider such as service provider 120 that has sales representatives, order fulfillment facilities, account maintenance facilities, and other equipment for supporting interactive home shopping features. A home shopping application that is implemented using the user equipment may be used to access the service provider to provide these features to the user. The user equipment may access service provider 120 via media distribution facility 150 or via communications network 170.

If desired, applications such as interactive television program guide applications, home shopping applications, home banking applications, and other applications (e.g., applications related to e-mail and chat or other communications functions, etc.) may be provided as separate applications. These separate applications may be accessed through a navigation shell application (e.g., a menu application with menu options corresponding to the applications). Additionally, the features of such applications may be combined. For example, on-demand media, home shopping, and communications functions may be incorporated into the program guide or other application.

These applications or features may be implemented locally on the user equipment. The applications or features may also be implemented using a client-server architecture in which user equipment serves as a client processor, and a server, such as distribution server 180, at media distribution facility 150 or at some other suitable location acts as a server processor. Other distributed architectures may also be used if desired.

Examples of client-server program guides are shown in Ellis et al. U.S. application Ser. No. 09/332,244, filed Jun. 11, 1999, which is hereby incorporated herein in its entirety. Examples of interactive television program guide systems with integrated program listings and video-on-demand display screens are shown in Walker et al. U.S. application Ser. No. 09/829,856, filed Apr. 10, 2001, which is hereby incorporated herein in its entirety. For clarity and brevity, FIG. 1 is illustrated to include only one of each of the elements that are shown therein. However, in implementation, network topology 100 may include more than one of the elements that are shown therein. For example, network topology 100 may include multiple media distribution facilities 180, multiple user-equipment 160, multiple distributions servers 180, etc.

Turning next to FIG. 2, network topology 200 includes select elements from network topology 100 of FIG. 1 and expands on possible arrangements for such elements.

Network topology 200 may include user equipment 260 and 265, server network 210, and communications network 270. User equipment 260 and 265 are both included in network topology 200 to better illustrate the level of equipment independency that may be obtained in on-demand media delivery systems.

User equipment 260 and 265 may provide a user with the capability to display, retrieve, record, and manipulate user-specific data, on-demand media content, and on-demand media data. User equipment 260 and 265 may be user equipment 160 of FIG. 1. Additionally, user equipment 260 and 265 may include input devices 261 and 266, display devices 262 and 267, set-top boxes 263 and 268, and communication devices 264 and 269 respectively.

Input devices 261 and 266 may allow a user to access, control, or communicate with devices in user equipment 260 and 265 respectively. When used in conjunction with communication devices 264 and 269, a user may communicate with, access, or program certain devices in network topology 200 via communications network 270. Examples of input devices 261 and 266 may include, for example, remote controls, keyboards, voice recognition devices, and control panels located on the devices in user equipment 260 and 265.

Display devices 262 and 267 may provide a medium on which on-demand media content and data may be presented or displayed to a user. Examples of display devices that may generally be used may include, for example, television sets, personal digital assistants (FDA's), computer monitors, and cell phones. Display devices 262 and 267 of FIG. 2 may be television sets, monitors, or other suitable display devices. Display devices 262 and 267 may not be limited to only visual forms of presentation. For example, if desired, on-demand audio content and data may be presented and displayed audibly to the user by display devices 262 and 267. Display devices may also include, for example, speakers, radios, sound-systems, and earphones.

Set-top boxes 263 and 268 may be capable of retrieving and sending on-demand media content and on-demand media data to devices located outside of user equipment 260 and 265 through communication devices 264 and 269. Examples of communication devices 264 and 269 may include, for example, local servers, telephone or cable modems, infrared ports, and wireless LAN access points. Set top boxes 263 and 268 may also contain processing and storage capabilities as well as software needed for an on-demand media delivery system. Examples of software implemented on set-top boxes 263 and 268 may include, for example, interactive television program guide applications.

For clarity and brevity, user equipment 260 and 265 are illustratively shown to include set-top boxes 263 and 268. However, in some embodiments, user equipment systems 260 and 265 may include a personal computer that has sufficient hardware and software capability to perform the functionality described herein or may include other devices with capabilities similar to set-top boxes. If desired, user equipment may include local storage devices such as a VCR, or a digital video recorder that may provide conventional data recording and storage capabilities.

Communications network 270 may provide a communications hub and communications medium for the devices of network topology 200. Persons skilled in the art will appreciate that communications network 270 has been provided in network topology 200 to illustrate the many different ways that the devices of network topology 200 may be connected together. Communications network 270 may represent connections such as direct connections network connections, or combinations of direct and network connections for devices in network topology 200. Communications network 270 may include, for example, routers, switches, wide area networks, the Internet, LANs, intranets, wireless LANs, repeaters, landline networks, PSTN, PABX, cable television systems, etc.

Remote server network 210 may provide a remote location in which on-demand media content and on-demand media data may be stored. Remote server network 210, which may be an on-demand media server, may be configured to store, access, and manipulate user-specific data in addition to the on-demand media content and the on-demand media data. If desired, remote server network 210 may provide a communications hub between user equipment 260 and 265 and other elements in network topology 200. Furthermore, remote server network 210 may be part of a media distribution facility or cable system headend.

Remote server network 210 may also include any number of remote servers 211 and 212. Examples of remote servers 211 and 212 may include virtual servers, routing servers, queuing servers, storage servers, media servers, or any other type of server. Remote server network 210 may include one or more servers.

User equipment platform independent on-demand features may be provided to users for accessing, manipulating, or storing on-demand media content and on-demand media data, and also for accessing, manipulating, or storing user-specific data.

FIG. 3 shows illustrative remote control 300, which may be used as an input device for user equipment. Remote control 300 may include, for example, primary option buttons 310, alpha-numeric buttons 320, task buttons 330, control buttons 340, secondary option buttons 350, and custom buttons 360. Other arrangements of some or all of the buttons may also be used.

Primary buttons 310 provide a user with access to frequently used actions in an on-demand media delivery system. Primary buttons 310 may include display button 211, local storage button 312, other device button 313, power button 314, login button 315, and logout button 316. Display button 311, local storage button 312, and other device button 313 may be used to identify the device with which the user seeks to interact. Login and logout buttons 315 and 316 may allow a user to communicate his or her identification to the on-demand media system. This identification may be communicated through alpha-numeric buttons 320.

Alpha-numeric buttons 320 may be used to enter, for example, numbers, letters, or an alpha-numeric string. Alpha-numeric buttons 320 may be used in conjunction with other buttons of remote control 300. For example, if login button 315 is pressed, alpha-numeric buttons 320 may be used for alpha-numeric entry of identification information.

Task buttons 330 may provide means for directing a task to be performed by a device in the on-demand media delivery system. For example, “LREC” button 338 may be used to have a local VCR record media content that is currently being displayed by the user equipment. If “RREC” button 339 is used, currently displayed media content may be recorded on a server in a remote server network. Task buttons 330 may include, for example, play, pause, record, stop, menu, confirm, rewind, fast-forward, local record, and remote record buttons or any other task button.

Control buttons 340 may include volume control buttons 341, navigation buttons 342, and channel control buttons 343. Navigation buttons 342 may be used to adjust or move a desired element (e.g., a cursor, a highlight window, etc.) either vertically, horizontally, or both. For example, if the desired element is a cursor on an interactive program guide display screen, navigation buttons 342 may be used to move the cursor in the display screen. The “OK” key in task buttons 330 may be used in combination with navigation buttons 342 to select on-screen options.

Secondary buttons grouping 350 may include, for example, profile access, relocate, auto-configure, access rights, billing information, administration, remote access, personal data, and public data buttons. Some of these features are further discussed below.

Custom buttons grouping 360 may include buttons associated with any actions or commands that are pre-defined by a user. If desired, other keys and options may be included on remote control 300. Functions shown on remote control 300 of FIG. 3 may alternatively be offered as on-screen options or using other input means (e.g., voice input).

FIG. 4A shows illustrative navigation display screen 400 that may be used as a top-level display screen for an on-demand media delivery system in accordance with the principles of the present invention. Navigation display screen 400 includes media windows 401 and 402, mail prompt 405, time label 406, quick fact button 408, program listing options 410, cable showcase options 420, and viewer services options 430.

Media windows 401 and 402 may be used to display user-selected media content, system-selected media content, interactive advertisements, or other content displayed through user equipment. Media windows 401 and 402 may be removed, relocated, or resized in display screen 400.

Mail prompt 405 may be displayed to indicate new messages or selected by a user to read electronic mail or to prepare and send electronic mail. Time label 406 may be used on display screen 400 to display the current time to a user. Time label 406 may be tailored by the user to also display other time critical information. Quick fact button 408 may display a fact of possible interest (e.g., an interactive advertisement) in display screen 400. Quick fact button 408 may be selected to take further action or to display a related display screen.

Program listing options 410 may include options for viewing program listings by time, by channel, or by genre (e.g., sports, children, etc.). Program listings options 410 may also include an option for searching for programs of interest (e.g., using keywords, based on a title search, based on an actor search, etc.). Program listings options 410 may include an option to view a user's favorite program listings.

Cable showcase options 420 may include options for accessing video-on-demand program listings, pay-per-view program listings, pay-per-view event listings, premium program listings, music program listings, or adult program listings.

A highlight window or cursor may be used to move within a display screen. For example, cursor 440 may be used to select options in display screen 400. Remote control 300 (FIG. 3), particularly navigation buttons 342 (FIG. 3), may be used for moving cursor 440 within display screen 400. The area upon which cursor 440 is positioned over may be selected by pressing a select, enter, or OK key, such as remote control button 335 of FIG. 3.

Screen 400 may also contain viewer services options 430. Suitable viewer services options 430 may include, for example, an option to access features and/or information from a personal video recorder, an option to access Messages (either e-mail messages or messages provided from a television system service provider), an option to adjust parental control settings (e.g., blocked channels or ratings, etc.), an option to set or view profile data (e.g., favorite channels, etc.), an option to set up the program guide or user equipment, an option to exit display screen 400, and an option to login to the system.

For brevity and clarity, programming and other media that is available for viewing, but is without a scheduled air time is primarily discussed in the context of video-on-demand programming.

If the user selects video-on-demand (VOD) option 421, the program guide may present the user with a screen such as video-on-demand display screen 450 of FIG. 4B. Display screen 450 may contain various options that allow the user to view video-on-demand program listings organized by different criteria such as genres (e.g., family, action, drama, comedy, kids, thrillers, classics, etc.). If the user selects movies A-Z button 452 of display screen 400, the program guide may present display screen 500 of FIG. 5A in which video-on-demand program listings are listed alphabetically.

Active area 507 may be present in many different display screens. Active area 507 may be an interactive advertisement. Illustrative ordering display screen 550 of FIG. 5B may be displayed when a user selects a VOD listing such as a listing for Star Wars from display screen region 540 of FIG. 5A or from active area 507 of FIG. 5A. Video-on-demand ordering display screen 550 may be displayed through any other suitable technique.

Display screen 550 may contain information region 552 that includes information on the title, purchase price, running time, rating, and other information related to the user's selection. A detailed information region such as information region 551 may also be displayed. Region 551 may include a detailed description of the VOD listing, information on the actors in the movie, the running time, the year of release, etc.

If the user selects back option 556, the user may be taken back to display screen 500 of FIG. 5A. If the user desires to purchase the video-on-demand program, the user may use remote control 300 of FIG. 3 to enter the user's login identification and associated password information. Other user identification techniques may also be used. These identification structures may support the entry, for example, of a purchase code or personal identification number (PIN) in region 553.

When valid login information is entered and a purchase button is selected (e.g., button 557), the distribution of the selected video-on-demand program may be authorized to the user from server 180 or remote server network 110 of FIG. 1 or other suitable distribution source to the user who is currently logged into the system. The requested video-on-demand program may be displayed in display screen 600 of FIG. 6A.

Region 608 may be displayed in display screen 600 and may contain information on the program title and the time remaining in the current video-on-demand program. Region 608 may also contain a selectable advertisement. Region 608 may be provided as an overlay over the video-on-demand program that is being presented, as an L-shaped frame region surrounding a reduced-size video window, or in any other suitable configuration or layout. Region 608 may be invoked whenever a user presses an appropriate key on remote control 300 of FIG. 3 and may be removed, for example, after a specified period of inactivity.

Primary on-screen control options 610 may be included in display screen 600 to give users one way of controlling the on-demand media content being displayed in window 601. Primary control options 610 may be selected by the user, for example, to play, pause, stop, rewind, record locally, record remotely, or fast-forward the video-on-demand program. Hide option 615 may also be included in control options 610. When selected, hide option 615 may remove all elements other than window 601 from display screen 600.

When the user selects a control command, the program guide may direct server 180 of FIG. 1, a server located in remote server 110, or other suitable equipment to perform the requested function. For example, when the user selects the remote record option 619, the program guide may direct the server in remote server network 110 to record the video-on-demand program on the relevant storage space 190. When the user selects record option 619, the server may record some or all of the video-on-demand program that is currently available to the user. These are merely illustrative examples and any suitable technique for handling video-on-demand recordings may be used if desired.

If the user selects rewind option 616, the program guide may direct the appropriate device, such as server 180 of FIG. 1, to skip to an earlier portion of the video-on-demand program. A real-time rewind process may be used in which the video-on-demand programming is displayed during the rewind operation. Commands for pausing, playing and fast-forwarding may be handled similarly.

FIG. 6B shows illustrative primary login display screen 650. Login display screen 650 may include an enter identification region 670 in which user identification may be entered by a user (e.g., using alpha-numeric keypad 660). Additionally, options region 680 may be included in display screen 650. Options region 680 may include options that are be used to access, for example, a user's profile, a prior display screen, help information, a VOD menu, and/or login/logout options. Once an appropriate identification information is entered into identification region 670, a user may use login/logout button 685 to send the user's identification information to remote server network 110 or any other suitable device in network topology 100 of FIG. 1. Other techniques for login may also be used. For example, if a user has already been identified by the user, the system may not be required to submit further information.

A relocate feature may be included in the on-demand media system. This relocate feature may allow a user to freeze media-on demand content being presented on one user equipment and switch to some other user equipment to resume the presentation of the media on-demand content (i.e., resume from the point at which the user had frozen the content). The user equipment may be equipment such as user equipment 260 and 265 of FIG. 2. If the user wants to continue watching the on-demand media content at a friends house (e.g., user equipment system 265 of FIG. 2), the user mayonly have to use the relocate feature to freeze the on-demand media content and relocate to the friend's house to resume the on-demand media content.

FIG. 7A shows an illustrative relocate feature confirmation display screen 700. Display screen 700 may be displayed when a command from remote control 300 of FIG. 3 is selected or when an appropriate option on an on-demand media display screen is selected to indicate a user's interest to freeze the program. If a user wants to confirm a freeze request, option 710 may be selected. If a user does not want to confirm the freeze request, option 720 may be selected. If desired, a user may freeze a VOD program by simply selecting the relocate feature from a remote control or from an earlier on-screen menu. If the user has not previously logged in or otherwise been identified, the user may be asked to log in or to provide identification information when making a freeze request.

FIG. 7B shows illustrative relocation display screen 750 that may be displayed when a command from remote control 300 of FIG. 3 is selected or when an appropriate option on an on-demand media display screen is selected to resume on-demand media that was frozen earlier by the user, Option 740 may be selected if a user wants to start to view the media from the frozen point on user equipment that is different (e.g., different household, different subscriber site, different room, different equipment platform, etc.) than that which was used to freeze the media.

When a user selects continue option 740, the media may be presented on the current user equipment starting from the frozen point. If desired, media may be queued to the frozen point for presentation to a user when a user who had previously selected a freeze (or relocated) option logs into the system. Also, if desired, the media may be queued selectively upon user request (e.g., user selects a resume from frozen point option). If the user has not previously logged in or otherwise been identified, the user may be asked to log in or asked to provide identification information when making a resume request. The system may also allow the user to select from multiple programs which may have been previously frozen by the user.

When the relocate feature is first selected by a user, remote server network 110 of FIG. 1 may, for example, pause the on-demand media content being viewed by the user and store a content location reference to an appropriate user-specific account. After the user switches to a different location and requests that the paused content be appropriately delivered, remote server network 110 may retrieve the appropriate content location reference and continue delivering the media content from the point at which the user paused the content. Before the media content may be delivered, the remote server network may require that the user be identified so that the appropriate user-specific data and/or a user-specific account information, may be located and accessed.

User-specific data or account information may be stored in a section of remote server network 110 (FIG. 1) dedicated to the user. Remote server network 110 (FIG. 1) may be a VOD server that is configured to store such information and data. An account on remote server network 110 (FIG. 1) may also be used to store that user's personal images or video. Remote server network (FIG. 1) may allow users to access their personal images or videos from their own home or from user equipment at other locations.

FIG. 7C is a flow chart of illustrative relocation process 760 that shows how data is stored and accessed when a relocate feature is selected. Process 760 begins with start step 761 that may include almost any interaction with the media-delivery system that results in the relocation feature being presented to the user. Start step 761 may, for example, be a user interaction that brings up relocate display screen 700 of FIG. 7A. At step 762, a user may be given an opportunity to choose or confirm the relocate feature.

If desired, step 762 may include step 771 for identifying a current user (e.g., identifying a current user on a first user equipment). User identification step 771 may provide the user with the ability to log into the on-demand media system, which may include prompting the user for an identification and/or password. Step 771 may be performed, for example, in response to a user selecting the relocate feature.

If desired, step 771 may be part of start step 761 to allow the system to identify the current user before the relocate feature is selected by the user.

The on-demand media system may then save the user's current position (step 763) when the user selects the relocate feature. Saving the current position may involve, for example, saving a pointer that identifies where the media content was ‘frozen’ or paused by the relocate feature. If the user was identified in step 771, process 760 may store any data relevant to the operation of the relocate feature in storage space associated with the user. If desired, saving the current position may involve recording the media content from the point at which the relocate feature was chosen. At step 764, process 760 may enter an idle mode until a user selects to resume reception. Step 764 may include step 772 for identifying the current user (e.g., identifying a current user on a second user equipment). Step 772 may be performed when a user selects to resume media using the relocate feature. At step 772, the system may provide a current user with the ability to log into the on-demand media system, which may include prompting the user for an identification and/or password. If desired, step 772 may be performed before the current user selects to resume media using the relocate feature.

At step 765, the location of the media content that was being viewed when the relocate feature was initially selected may be retrieved. If the user was identified in step 772, data associated with the operation of the relocate feature may be retrieved from storage space associated with the current user.

If a pointer was stored, the system may find the correct location of content in the on-demand media delivery system using the pointer and continue playing the media from that point (Step 765). If desired, the media may have been remotely recorded from the point at which the relocate future was selected. In such embodiments, the system will simply begin playing content from the point at which the content was recorded. After the content has been successfully retrieved and resumed, finish step 766 may occur which may denote the end of process 760.

FIG. 8 illustrates relocation process 880 and is similar to process 760, but includes the possibility of relocating while watching live content. Steps 881, 882, 891, 886, 892, and 888 are essentially the same as steps 761, 762, 771, 764, 772, and 766 of FIG. 7C, respectively. At live feed check step 883, the system may determine if the current media is a live feed. If the media is not a live feed, step 885 is performed, which involves storing the current position of the media. If the media is a live feed, the media may be remotely recorded at step 884. After step 884 occurs, the position of the media may be stored at step 885. If desired, the position of the media may be stored in the form of a pointer. During step 886, the system may be in an idle state, waiting for the user to indicate that the user has relocated to new user equipment. If desired, process 880 may include steps 891 and 892 at particular points in process 880 as shown and/or discussed above in connection with steps 771 and 772 of FIG. 7C for identifying a current user at a first user equipment and at a second user equipment when a user has relocated to the second user equipment. After a user has relocated, the system may, in step 887, determine the stored media position, retrieve the stored media position, and then continue playing the media from the stored media position. Once play commences, finish step 888 is reached and the user is successfully relocated.

A remote on-demand media server may be configured to store and deliver user-specific media (e.g., pictures, videocam recordings, etc.), or user-uploaded data or media. Access to such data and media may be controlled in a variety of ways.

FIG. 9 shows illustrative data and media access process 900 for remote servers. At step 901, a static request from the on-demand media system or a manual request from a user interfacing with user equipment may be received. The request may be associated with the retrieval of media content or user-specific data.

To retrieve media content, server 180 of FIG. 1 may be accessed. At step 902, in response to a request for user-specific data, the appropriate device in network topology 100 of FIG. 1 may be checked to determine if any type of authorization is needed to access the requested data. At step 903, in response to a request for media content, the system may check appropriate devices in network topology 100 of FIG. 1 to determine if any type of authorization to access the requested media content is needed.

If access to the data or media does not need any type of authorization, the data or media may be retrieved and the user may be provided with an opportunity to access the data or the media at steps 907 and 908. Data or media that may not require access privileges may include, for example, data or media defined by a user as public.

If authorization is needed, then at step 904 or at step 905, a request may be sent to determine if the user has permission to access the desired data or media. Steps 904 and 905 may include asking the user for an account identity and/or password. At step 906, users may be denied access when the users have not been given access rights for the desired data or media. If a user does have permission to access the desired data or media, the user may be given access to the data at step 907 or access to the media at step 908.

If desired, steps 902 and 903 may be combined. If desired, steps 904 and 905 may be combined. Also if desired, 907 and 908 may be combined.

As mentioned above, the on-demand media system realizes many unique features in utilizing the capabilities of remote storage and remote access. Some of such unique features may be realized in connection with remotely stored user profiles or remotely stored user accounts.

An on-demand media delivery system may have an account for a user or a group of users (e.g., a household) that may be used to store user profiles for users associated with the account. A user profile may act as a governing data structure through which user-specific data and on-demand media content and data may be accessed, stored, and retrieved.

Remote server network 110 of FIG. 1 may be partitioned and formatted to include a user account for any user or group of users in which account-specific data and on-demand media content may be stored, manipulated, and accessed.

FIG. 10 shows illustrative profile display screen 1000 that may include user identification information 1005 to show who is currently recognized by the system. If a new user wishes to login, new login option 1031 may be selected and a login display screen such as display screen 650 of FIG. 65 may be initiated. If the user desires an option that is not present on display screen 1100, more options button 1032 may be selected.

Region 1010 includes a number of different user-selectable options such as a preferences option as shown. These options may allow the user to access or use locally or remotely stored data or media when the user is logged into the system.

FIG. 11 shows illustrative account administration display screen 1150 that may be displayed when account administration option 1034 of FIG. 10 is selected. Account information 1151 may be displayed on display screen 1150 to show which user is currently recognized and to identify the administrative position of that user. Account administration window 1160 may be located on display screen 1150 and may contain a list of users or groups that are under the recognized user's account. The recognized user may change the properties of the users or groups in window 1160 through administrative controls 1170. A user may change properties of a user or a group by first selecting a user or group from window 1160 (e.g., pressing a data entry key when a highlighted window is positioned over a user or group) and next positioning a cursor or highlight window on one of the options in controls 1170 to take desired action. Examples of controls that may be included in administrative controls 1170 may include, for example, add new group, add new user, restrict group, restrict user, limit group, limit user, delete group, delete user, create a new account for a user, and create a new account for a group.

Storing user-specific data such as the user's preferences (e.g., preferences in general, preferences for on-demand media, etc.) in a remote server such as a VOD server may allow for a personal auto-configure feature that would follow a user to move from equipment to equipment. This feature may allow preferences to be retrieved and executed by user equipment after the user has been identified by the system (e.g., identified by a remote server network). Some categories of preferences and user-specific information that may be used in an auto-configure feature may include, for example, volume settings, favorite channels, reminders, information about user-recorded on-demand media content, the user's last activity, auto-record times, as well as any other preference or activity. For example, after a user is verified by a remote server network, the user equipment may selectively or automatically be configured to match or use some or all of the user's remotely stored preferences.

FIG. 12 shows illustrative auto-configure display screen 1200, which may be initiated after a user has logged in via a login display screen (e.g., display screen 650 of FIG. 6B). Display screen 1200 may allow a user to select have user equipment auto configured. The user equipment may be user equipment that is currently being used that user. The user equipment may be auto-configured by downloading user-related data and information and processing the data and information on the user equipment to suit the current user.

Information region 1210 may be present on display screen 1200 and may include data from a user's profile or data related to a user's login. Configure options 1220 may be included on display screen 1200. Information stored in a user's profile may be accessed to perform a number of activities when one of options 1220 are selected. The options displayed among in configure options 1220 may vary depending on types of the information that are stored in a particular user's profile. Examples of configuration options 1220 may include, for example, auto-configuration options, last activity options, favorite show option, last show option, and favorite activity option.

Always auto-configure option 1211 may be selected by a user to automatically configured user equipment with the user's personal information whenever the user logs into the system. Auto-configure option 1212 may be displayed when always auto configure option 1211 was not previously selected by the user. Auto-configure option 1212 may be selected to auto-configure the currently used user equipment. User equipment settings may be deleted or reset by the user equipment settings by after a user has logged off and is no longer recognized to be the user equipment.

FIG. 13 shows illustrative process 1350 that may be involved in automatically configuring user equipment. The process may begin at start step 1351, when, for example, an on-demand media delivery system is activated. A user may be allowed to log into the system at step 1352. At step 1353, the user's login information may be verified. At step 1354, if the login information that is entered is valid, the system may check to see if the account of the logged in user indicates that the always auto-configure feature is selected. If the account shows the always, auto-configure feature to be selected, the user equipment that was used for logging into the system may be automatically configured with that user's preference information at step 1358.

At step 1358, auto-configuration preferences and information may be retrieved and downloaded to the currently-used user equipment and the user equipment may be configured based on the preferences and information.

If the option to always auto-configure was not selected, a user may be provided with an opportunity to have the currently-used user equipment automatically configured for the current login at step 1355. Step 1358 may be performed when the user selects the auto-configure option during the current login. At finish step 1359, a user may be allowed to resume other activity. In this technique, some or all of a user's profile or preferences may be stored at a remote server.

The on-demand media delivery system may also contain an upload feature. FIG. 14A depicts an illustrative upload file display screen 1400 which may be initiated in order to upload a file. If desired, the upload feature may include a process that automatically scans user equipment for upload devices. Upload device buttons 1420 may be displayed on display screen 1400 when different file sources are available. For example, display screen 1400 may include VCR upload button 1411, computer upload button 1412, and DVD player upload button 1413. A user may be allowed to select a button from buttons 1420 to upload data from the device associated with that button.

The upload feature may also include an Internet address entry box 1410. A user may type or select a file address in box 1410. The on-demand media system may search the Internet for a file based on the file address and may upload the file. A user may select practically any file to upload when the file is found and have the file stored on a remote server of the on-demand media system.

Files uploaded to the remote server (e.g., VOD server) may also be downloaded to user equipment to be presented to a user. Files may be transferred from one user equipment to a different user equipment system through a media-on-demand remote server. Files may include almost any type of data, program, or content. Examples of files that may be uploaded include, for example, pictures, movies, songs, video games, documents, e-mails, and Internet Web pages. Files such as pictures, movies, songs, video, or other audio-visuals materials may be of particular interest because on-demand media servers are particularly suited for the delivery and presentation of audio-visuals to users.

Process 1450 is illustrated in FIG. 14B to show illustrative steps that may be involved in uploading a file to a device such as a VOD server. At step 1452, a user may be provided with an opportunity to select an upload feature. At step 1454, the on-demand media system may check to see if a user is currently logged into the system. If a user is not currently logged in, user login may be requested at step 1455. At step 1456 the system may check to see whether the login was valid. The upload process may commence at step 1457 when the current user is logged into the system.

At step 1457, the system will determine if file location information has been given by the user. If desired, the system may search the user equipment for file source devices. If file source devices are found, appropriate upload options may be presented at step 1459. These options may be presented to a user in the form of device buttons 1410 of FIG. 14A. If no devices were found at step 1458, default options may be presented to the user at step 1460. Default options may include, for example, an Internet upload box or a list of possible storage devices that the user equipment may include. At step 1461, a user may be provided with an opportunity to select a file location for upload using the presented options. At step 1462, the selected file may be uploaded. If desired, at step 1472, the system may convert file formats for files that are being uploaded (e.g., convert JPG files to MPEG files) and/or may convert analog signals to digital file format.

After a file has been uploaded in step 1462, a user may want to assign access rights to that file. A user may also want to download the file to a different device in the on-demand media system. FIG. 15A is an illustration of display screen 1500 which may allow a user to download a recently uploaded file or to assign access rights to that file.

If a user desires to designate an uploaded file as a public file, public button 1531 may be selected. If a user desires to designate an uploaded file as a private file, private button 1532 may be selected. Download buttons 1520 may also be included in display screen 1500. If desired, the system may convert file formats for files that are downloaded (e.g., convert JPG files to MPEG files) and/or may provide digital to analog format conversions. Examples of such buttons may include for example, download to VCR button 1511, download to computer button 1512, and download to DVD player button 1513. If desired, however, the user may be presented with an option to have the file, which may be an audiovisual file, displayed or played back for the user. For example, the system may present the user with “view on your TV” option 1533, which may allow the user to view the file on the user's television set.

Files that are designated as private may be files that are associated with a particular user or with particular groups of users that have access rights to the file to the exclusion of others. Access may be limited to certain activities, which may include, for example, downloading, viewing, deleting, writing, and manipulating a file.

FIG. 15B illustrates display screen 1550, in which a user may grant and restrict access to particular users or groups of users in the on-demand media system. Display screen 1550 may include identity listings 1580 that contains a list of users and groups in the on-demand media system. After selecting a user or group from listings 1580 (e.g., by navigating on a listing and pressing a select key), a user may use grant button 1562 to grant access to a selected user or group. A user may select restrict button 1563 to restrict access to selected user or groups. If the user decides to make the file a public file, the user may select public button 1564.

The on-demand media system may include a file search feature to aid users in locating files. FIG. 16A illustrates display screen 1600 from which a user may search for files on the on-demand media system. Display screen 1600 may contain search-type listings 1611. Listings 1611 may include options that allow a user to designate which types of files are to be located in a search. Examples of file types in listings 1611 may include, files to which the user has access rights, files associated with the current user, files for the presentation of audiovisuals such as pictures, games, or videos, or files for any other type of data.

Search listings 1612 may be included in display screen 1600 to give a user capabilities to narrow a search. A user may use listings 1612 to enter searchable text that may be associated with either a file's title or description. Identity search listings box 1613 may also be included in display screen 1600 to narrow a search even further. Box 1613 gives a user the capabilities to search for files associated with specific identities. After one or more files have been found by the on-demand media system, the user may download the file either to the remote server or to a device in the user equipment system.

FIG. 16B is an illustration of display screen 1650 that allows a user to download files which were located in a file search. Display screen 1650 may contain found files listings box 1680, in which the found files may be listed. Box 1680 may list found files in any manner, such as alphabetically, and if desired may include a data or ownership hierarchy showing where the file was found in the system. Files from box 1680 may be downloaded to a remote server with the selection of a download button, such as download button 1662. For example, a user may select a file in box 1680 and then move a cursor to button 1662 to select that button. Device download buttons 1670 may also be included in display screen 1650 based on what devices are included in the currently-used user equipment. Download buttons may include for example, download to VCR button 1671, download to computer button 1672, download to DVD player button 1673, or any other suitable button for downloading files to a local device. If desired, the system may convert file formats for files that are downloaded (e.g., convert JPG files to MPEG files) and/or may provide digital to analog format conversions. Additionally, the user may be presented with view file option 1661, which may allow the user to view files located in the file search on the user equipment. See also “view on your TV” option 1533 of FIG. 15A, which essentially provides the same functionality.

For clarity and brevity, the features of the systems that are described herein are primarily discussed in the context of video-on-demand services. The features may also be implemented with other types of media on-demand services. Media on-demand services may be used to mass distribute movies, programs, music albums, etc. to users. User equipment and remote network servers may be configured for users to store personal media such as photographs, home videos, old recordings, or other media on a remote server for on-demand access by the user at a later time. The user as described above may associate desired access rights with the media that the user stores on the remote server.

Some or all of the features that are described herein may be implemented as part of an interactive television program guide, as part of a media on-demand application, as part of a dedicated application for those features; or implemented using a combination of such applications.

If desired, in connection with the relocate feature, the system may prompt a user to select whether to freeze on-demand-media of the user when the user is logging out of the system. Also, if desired, in connection with the relocate feature, the system may allow the user to resume the presentation of on-demand-media from a different point than the point at which the on-demand media may have been frozen. For example, the system may provide the user with an option to resume the presentation of on-demand media from the beginning of the media when the user relocates and exercise the relocate feature. The system may further allow the user to rewind the media past the point at which the media frozen.

The foregoing is merely illustrative of the principles of this invention and various modifications may be made by those skilled in the art without departing from the scope and spirit of the invention.

Claims

1. A method for use in an interactive media guide system, the method comprising:

receiving a first indication from a first user equipment device to pause a media content that is displayed on the first user equipment device;
in response to receiving the first indication, storing position information that is indicative of a pause point in the media content at which the media content was paused at the first user equipment device;
receiving a second indication from a second user equipment device to view the media content on the second user equipment device, wherein the media content was paused on the first user equipment device;
in response to receiving the second indication, generating for simultaneous display on the second user equipment device: a first option that causes, responsive user selection, the second user equipment device to resume display of the media content based on the pause point; and a second option that causes, responsive to user selection, the second user equipment device to display the media content from a point in the media content that is prior to the pause point;
determining whether the first option or the second option was selected at the second user equipment device; and
generating an instruction to display the media content at the second user equipment device from a viewing point in the media content, wherein the viewing point is based on the determining.

2. The method of claim 1, further comprising:

in response to determining that the first option was selected at the second user equipment device, determining the viewing point in the media content based on the stored position information.

3. The method of claim 1, further comprising:

in response to determining that the second option was selected at the second user equipment device, determining that the viewing point in the media content is a point that is prior to the pause point.

4. The method of claim 3, wherein the viewing point in the media content is selected by the user using the second equipment device.

5. The method of claim 1, further comprising:

generating for display a relocate option on the first user equipment device that causes, responsive to user selection, the media content that was paused at the first user equipment device to be displayed on the second user equipment device.

6. The method of claim 1, further comprising:

generating a login option to be displayed to the user using the second user equipment device that allows the user to log into the system.

7. The method of claim 6, further comprising:

in response to receiving selection of the login option by the user using the second user equipment device, identifying information associated with the user who logged into the system.

8. The method of claim 7, further comprising:

in response to the identifying, retrieving the stored position information, wherein the stored position information is associated with the identified information associated with the user who logged into the system.

9. The method of claim 1, wherein selection of the second option causes, responsive to user selection, the second user equipment device to display the media content from the beginning of the media content.

10. The method of claim 1, further comprising:

generating for display, on the second user equipment device, a third option that causes, responsive to user selection, the second user equipment device to display the media content from a point in the media content that is after the pause point, wherein the determining further comprises determining whether the third option was selected at the second user equipment device.

11. An interactive media content guide system, the system comprising a server configured to:

receive a first indication from a first user equipment device to pause a media content that is displayed on the first user equipment device;
in response to receiving the first indication, store position information that is indicative of a pause point in the media content at which the media content was paused at the first user equipment device;
receive a second indication from a second user equipment device to view the media content on the second user equipment device, wherein the media content was paused on the first user equipment device;
in response to receiving the second indication, generate for simultaneous display on the second user equipment device: a first option that causes, responsive to user selection, the second user equipment device to resume display of the media content based on the pause point; and a second option that causes, responsive to user selection, the second user equipment device to display the media content from a point in the media content that is prior to the pause point;
determine whether the first option or the second option was selected at the second user equipment device; and
generate an instruction to display the media content at the second user equipment device from a viewing point in the media content, wherein the viewing point is based on the determining.

12. The system of claim 11, wherein the server is further configured to:

in response to determining that the first option was selected at the second user equipment device, determine the viewing point in the media content based on the stored position information.

13. The system of claim 11, wherein the server is further configured to:

in response to determining that the second option was selected at the second user equipment device, determine that the viewing point in the media content is a point that is prior to the pause point.

14. The system of claim 13, wherein the viewing point in the media content is selected by the user using the second equipment device.

15. The system of claim 11, wherein the server is further configured to:

generate for display a relocate option on the first user equipment device that causes, responsive to user selection, the media content that was paused on the first user equipment device to be displayed on the second user equipment device.

16. The system of claim 11, wherein the server is further configured to:

generate a login option to be displayed to the user using the second user equipment device that allows the user to log into the system.

17. The system of claim 16, wherein the server is further configured to:

in response to receiving selection of the login option by the user using the second user equipment device, identify information associated with the user who logged into the system.

18. The system of claim 17, wherein the server is further configured to:

in response to the identifying, retrieve the stored position information, wherein the stored position information is associated with the identified information associated with the user who logged into the system.

19. The system of claim 11, wherein selection of the second option causes, responsive to user selection, the second equipment device to display the media content from the beginning of the media content.

20. The system of claim 11, wherein the server is further configured to:

generate for display, on the second user equipment device, a third option that causes, responsive to user selection, the second user equipment device to display the media content from a point in the media content that is after the pause point, wherein the determining further comprises determining whether the third option was selected at the second user equipment device.
Referenced Cited
U.S. Patent Documents
4355415 October 19, 1982 George et al.
4488179 December 11, 1984 Krüger et al.
4602279 July 22, 1986 Freeman
4605964 August 12, 1986 Chard
4694490 September 15, 1987 Harvey et al.
4704725 November 3, 1987 Harvey et al.
4706121 November 10, 1987 Young
4718107 January 5, 1988 Hayes
4745549 May 17, 1988 Hashimoto
4751578 June 14, 1988 Reiter et al.
4787063 November 22, 1988 Muguet
4847698 July 11, 1989 Freeman
4857999 August 15, 1989 Welsh
4908707 March 13, 1990 Kinghorn
4930158 May 29, 1990 Vogel
4959720 September 25, 1990 Duffield et al.
4963994 October 16, 1990 Levine
4965825 October 23, 1990 Harvey et al.
4977455 December 11, 1990 Young
5027400 June 25, 1991 Baji et al.
5047867 September 10, 1991 Strubbe et al.
5109279 April 28, 1992 Ando
5109414 April 28, 1992 Harvey et al.
5134719 July 28, 1992 Mankovitz
5151789 September 29, 1992 Young
5155591 October 13, 1992 Wachob
5172413 December 15, 1992 Bradley et al.
5200822 April 6, 1993 Bronfin et al.
5223924 June 29, 1993 Strubbe
5231493 July 27, 1993 Apitz
5233654 August 3, 1993 Harvey et al.
5249043 September 28, 1993 Grandmougin
5253066 October 12, 1993 Vogel
5299006 March 29, 1994 Kim
5335277 August 2, 1994 Harvey et al.
5339434 August 16, 1994 Rusis
5341350 August 23, 1994 Frank et al.
5353121 October 4, 1994 Young et al.
5355162 October 11, 1994 Yazolino et al.
5357276 October 18, 1994 Banker et al.
5404567 April 4, 1995 DePietro et al.
5410343 April 25, 1995 Coddington et al.
5410344 April 25, 1995 Graves et al.
5412720 May 2, 1995 Hoarty
5426699 June 20, 1995 Wunderlich et al.
5442389 August 15, 1995 Blahut et al.
5442390 August 15, 1995 Hooper et al.
5453779 September 26, 1995 Dan et al.
5461415 October 24, 1995 Wolf et al.
5465385 November 7, 1995 Ohga et al.
5477263 December 19, 1995 O'Callaghan et al.
5479266 December 26, 1995 Young et al.
5479268 December 26, 1995 Young et al.
5479302 December 26, 1995 Haines
5485197 January 16, 1996 Hoarty
5502504 March 26, 1996 Marshall et al.
5506932 April 9, 1996 Holmes et al.
5517254 May 14, 1996 Monta et al.
5517257 May 14, 1996 Dunn et al.
5521631 May 28, 1996 Budow et al.
5523794 June 4, 1996 Mankovitz et al.
5524195 June 4, 1996 Clanton, III et al.
5524271 June 4, 1996 Hollmann et al.
5528513 June 18, 1996 Vaitzblit et al.
5537141 July 16, 1996 Harper et al.
5539449 July 23, 1996 Blahut et al.
5539880 July 23, 1996 Lakhani
5541638 July 30, 1996 Story
5541738 July 30, 1996 Mankovitz
5548338 August 20, 1996 Ellis et al.
5550576 August 27, 1996 Klosterman
5550825 August 27, 1996 McMullan, Jr. et al.
5557338 September 17, 1996 Maze et al.
5557724 September 17, 1996 Sampat et al.
5559548 September 24, 1996 Davis et al.
5559549 September 24, 1996 Hendricks et al.
5574778 November 12, 1996 Ely et al.
5576755 November 19, 1996 Davis et al.
5583561 December 10, 1996 Baker et al.
5583563 December 10, 1996 Wanderscheid et al.
5585838 December 17, 1996 Lawler et al.
5585858 December 17, 1996 Harper et al.
5585866 December 17, 1996 Miller et al.
5586264 December 17, 1996 Belknap et al.
5589892 December 31, 1996 Knee et al.
5592551 January 7, 1997 Lett et al.
5594509 January 14, 1997 Florin et al.
5594779 January 14, 1997 Goodman
5602582 February 11, 1997 Wanderscheid et al.
5606642 February 25, 1997 Stautner et al.
5610653 March 11, 1997 Abecassis
5616876 April 1, 1997 Cluts
5619247 April 8, 1997 Russo
5619249 April 8, 1997 Billock et al.
5619274 April 8, 1997 Roop et al.
5623613 April 22, 1997 Rowe et al.
5625678 April 29, 1997 Blomfield-Brown
5629867 May 13, 1997 Goldman
5630060 May 13, 1997 Tang et al.
5630119 May 13, 1997 Aristides et al.
5632007 May 20, 1997 Freeman
5635987 June 3, 1997 Park et al.
5648824 July 15, 1997 Dunn et al.
5652613 July 29, 1997 Lazarus et al.
5654748 August 5, 1997 Matthews, III
5654886 August 5, 1997 Zereski, Jr. et al.
5657072 August 12, 1997 Aristides et al.
5666645 September 9, 1997 Thomas et al.
5671277 September 23, 1997 Ikenoue et al.
5671377 September 23, 1997 Bleidt et al.
5675743 October 7, 1997 Mavity
5682195 October 28, 1997 Hendricks et al.
5684525 November 4, 1997 Klosterman
5694163 December 2, 1997 Harrison
5696765 December 9, 1997 Safadi
5708845 January 13, 1998 Wistendahl et al.
5708961 January 13, 1998 Hylton et al.
5710601 January 20, 1998 Marshall et al.
5717452 February 10, 1998 Janin et al.
5721815 February 24, 1998 Ottesen et al.
5721829 February 24, 1998 Dunn et al.
5727060 March 10, 1998 Young
5732216 March 24, 1998 Logan et al.
5734119 March 31, 1998 France et al.
5742443 April 21, 1998 Tsao et al.
5745710 April 28, 1998 Clanton, III et al.
5751282 May 12, 1998 Girard et al.
5751672 May 12, 1998 Yankowski et al.
5752159 May 12, 1998 Faust et al.
5752160 May 12, 1998 Dunn
5754771 May 19, 1998 Epperson et al.
5758257 May 26, 1998 Herz et al.
5758258 May 26, 1998 Shoff et al.
5758259 May 26, 1998 Lawler
5760821 June 2, 1998 Ellis et al.
5761417 June 2, 1998 Henley et al.
5761607 June 2, 1998 Gudesen et al.
5768528 June 16, 1998 Stumm
5771354 June 23, 1998 Crawford et al.
5774170 June 30, 1998 Hite et al.
5778181 July 7, 1998 Hidary et al.
5778182 July 7, 1998 Cathey et al.
5778187 July 7, 1998 Monteiro et al.
5781226 July 14, 1998 Sheehan
5781227 July 14, 1998 Goode et al.
5781228 July 14, 1998 Sposato
5790198 August 4, 1998 Roop et al.
5790423 August 4, 1998 Lau et al.
5793366 August 11, 1998 Mario et al.
5793412 August 11, 1998 Asamizuya
5793971 August 11, 1998 Fujita et al.
5794217 August 11, 1998 Allen
5796952 August 18, 1998 Davis et al.
5798921 August 25, 1998 Johnson et al.
5802284 September 1, 1998 Karlton et al.
5805154 September 8, 1998 Brown
5805763 September 8, 1998 Lawler et al.
5805804 September 8, 1998 Laursen et al.
5805806 September 8, 1998 McArthur
5808608 September 15, 1998 Young et al.
5808694 September 15, 1998 Usui et al.
5809246 September 15, 1998 Goldman
5812123 September 22, 1998 Rowe et al.
5812205 September 22, 1998 Milnes et al.
5815146 September 29, 1998 Youden et al.
5815297 September 29, 1998 Ciciora
5818438 October 6, 1998 Howe et al.
5818439 October 6, 1998 Nagasaka et al.
5819019 October 6, 1998 Nelson
5819160 October 6, 1998 Foladare et al.
5822530 October 13, 1998 Brown
RE35954 November 10, 1998 Levine
5832287 November 3, 1998 Atalla
5835126 November 10, 1998 Lewis
5841979 November 24, 1998 Schulhof et al.
5844620 December 1, 1998 Coleman et al.
5850218 December 15, 1998 LaJoie et al.
5861906 January 19, 1999 Dunn et al.
5872588 February 16, 1999 Ares et al.
5881245 March 9, 1999 Thompson
5883621 March 16, 1999 Iwamura
5884028 March 16, 1999 Kindell et al.
5884141 March 16, 1999 Inoue et al.
5886707 March 23, 1999 Berg
5886732 March 23, 1999 Humpleman
5887243 March 23, 1999 Harvey et al.
5892915 April 6, 1999 Duso et al.
5894589 April 13, 1999 Reber et al.
5896414 April 20, 1999 Meyer et al.
5898441 April 27, 1999 Flurry
5898456 April 27, 1999 Wahl
5899582 May 4, 1999 DuLac
5900904 May 4, 1999 Okada et al.
5903234 May 11, 1999 Kimura
5903263 May 11, 1999 Emura
5903264 May 11, 1999 Moeller et al.
5905522 May 18, 1999 Lawler
5905847 May 18, 1999 Kobayashi et al.
5909638 June 1, 1999 Allen
5911046 June 8, 1999 Amano
5913039 June 15, 1999 Nakamura et al.
5914941 June 22, 1999 Janky
5915090 June 22, 1999 Joseph et al.
5915094 June 22, 1999 Kouloheris et al.
5916303 June 29, 1999 Scott
5917538 June 29, 1999 Asamizuya
5917835 June 29, 1999 Barrett et al.
5920702 July 6, 1999 Bleidt et al.
5920800 July 6, 1999 Schafer
5922045 July 13, 1999 Hanson
5922048 July 13, 1999 Emura
5923361 July 13, 1999 Sutton, Jr.
5926204 July 20, 1999 Mayer
5926205 July 20, 1999 Krause et al.
5926624 July 20, 1999 Katz et al.
5928327 July 27, 1999 Wang et al.
5929849 July 27, 1999 Kikinis
5929850 July 27, 1999 Broadwin et al.
5930473 July 27, 1999 Teng et al.
5930493 July 27, 1999 Ottesen et al.
5931901 August 3, 1999 Wolfe et al.
5933603 August 3, 1999 Vahalia et al.
5933835 August 3, 1999 Adams et al.
5935206 August 10, 1999 Dixon et al.
5936569 August 10, 1999 Ståhle et al.
5940071 August 17, 1999 Treffers et al.
5940073 August 17, 1999 Klosterman et al.
5943046 August 24, 1999 Cave et al.
5943047 August 24, 1999 Suzuki
5945987 August 31, 1999 Dunn
5945988 August 31, 1999 Williams et al.
5947746 September 7, 1999 Tsai
5949411 September 7, 1999 Doerr et al.
5956482 September 21, 1999 Agraharam et al.
5956716 September 21, 1999 Kenner et al.
5959659 September 28, 1999 Dokic
5961603 October 5, 1999 Kunkel et al.
5963202 October 5, 1999 Polish
5964455 October 12, 1999 Catanzarite et al.
5969283 October 19, 1999 Looney et al.
5969714 October 19, 1999 Butcher
5973680 October 26, 1999 Ueda
5973722 October 26, 1999 Wakai et al.
5974217 October 26, 1999 Haraquchi
5977963 November 2, 1999 Gaughan et al.
5977964 November 2, 1999 Williams et al.
5978567 November 2, 1999 Rebane et al.
5978843 November 2, 1999 Wu et al.
5986650 November 16, 1999 Ellis et al.
5990881 November 23, 1999 Inoue et al.
5999688 December 7, 1999 Iggulden et al.
5999970 December 7, 1999 Krisbergh et al.
6002394 December 14, 1999 Schein et al.
6002720 December 14, 1999 Yurt et al.
6005564 December 21, 1999 Ahmad et al.
6005600 December 21, 1999 Hill
6008802 December 28, 1999 Iki et al.
6009465 December 28, 1999 Decker et al.
6012089 January 4, 2000 Hasegawa
6012091 January 4, 2000 Boyce
6014184 January 11, 2000 Knee et al.
6014381 January 11, 2000 Troxel et al.
6014693 January 11, 2000 Ito et al.
6014694 January 11, 2000 Aharoni et al.
6014706 January 11, 2000 Cannon et al.
6018359 January 25, 2000 Kermode et al.
6018765 January 25, 2000 Durana et al.
6020912 February 1, 2000 De Lang
6022223 February 8, 2000 Taniguchi et al.
6023725 February 8, 2000 Ozawa et al.
6025837 February 15, 2000 Matthews, III et al.
6025868 February 15, 2000 Russo
6028600 February 22, 2000 Rosin et al.
6029064 February 22, 2000 Farris et al.
6032202 February 29, 2000 Lea et al.
6038591 March 14, 2000 Wolfe et al.
6038614 March 14, 2000 Chan et al.
6049831 April 11, 2000 Gardell et al.
6052145 April 18, 2000 Macrae et al.
6064380 May 16, 2000 Swenson et al.
6085236 July 4, 2000 Lea
6091823 July 18, 2000 Hosomi et al.
6091883 July 18, 2000 Artigalas et al.
6098082 August 1, 2000 Gibbon et al.
6111677 August 29, 2000 Shintani et al.
6112181 August 29, 2000 Shear et al.
6118450 September 12, 2000 Proehl et al.
6125230 September 26, 2000 Yaginuma et al.
6141003 October 31, 2000 Chor
6141488 October 31, 2000 Knudson et al.
6147715 November 14, 2000 Yuen et al.
6154206 November 28, 2000 Ludtke
6160546 December 12, 2000 Thompson et al.
6160796 December 12, 2000 Zou
6166730 December 26, 2000 Goode et al.
6167188 December 26, 2000 Young et al.
6169725 January 2, 2001 Gibbs et al.
6170006 January 2, 2001 Namba
6172712 January 9, 2001 Beard
6177931 January 23, 2001 Alexander et al.
6182094 January 30, 2001 Humpleman et al.
6184878 February 6, 2001 Alonso et al.
6208335 March 27, 2001 Gordon et al.
6208341 March 27, 2001 van Ee et al.
6219839 April 17, 2001 Sampsell
6230325 May 8, 2001 Iinuma et al.
6232539 May 15, 2001 Looney et al.
6236395 May 22, 2001 Sezan et al.
6237049 May 22, 2001 Ludtke
6243707 June 5, 2001 Humpleman et al.
6243725 June 5, 2001 Hempleman et al.
6263503 July 17, 2001 Margulis
6289165 September 11, 2001 Abecassis
6311011 October 30, 2001 Kuroda
6314575 November 6, 2001 Billock et al.
6324338 November 27, 2001 Wood et al.
6349410 February 19, 2002 Lortz
6353700 March 5, 2002 Zhou
6356971 March 12, 2002 Katz et al.
6359661 March 19, 2002 Nickum
6388714 May 14, 2002 Schein et al.
6393430 May 21, 2002 Van Ryzin
6433835 August 13, 2002 Hartson et al.
6441832 August 27, 2002 Tao et al.
6449767 September 10, 2002 Krapf et al.
6456621 September 24, 2002 Wada et al.
RE37881 October 15, 2002 Haines
6466080 October 15, 2002 Kawai et al.
6473559 October 29, 2002 Knudson et al.
6483986 November 19, 2002 Krapf
6487145 November 26, 2002 Berhan
6487362 November 26, 2002 Yuen et al.
6496981 December 17, 2002 Wistendahl et al.
6498895 December 24, 2002 Young et al.
6505348 January 7, 2003 Knowles et al.
6564378 May 13, 2003 Satterfield et al.
6577735 June 10, 2003 Bharat
6578070 June 10, 2003 Weaver et al.
6594699 July 15, 2003 Sahai et al.
6647417 November 11, 2003 Hunter et al.
6654933 November 25, 2003 Abbott et al.
6657116 December 2, 2003 Gunnerson
6671882 December 30, 2003 Murphy et al.
6741617 May 25, 2004 Rosengren et al.
6746127 June 8, 2004 Suyama
6751402 June 15, 2004 Elliott et al.
6751802 June 15, 2004 Huizer et al.
6756997 June 29, 2004 Ward, III et al.
6760758 July 6, 2004 Lund et al.
6769127 July 27, 2004 Bonomi et al.
6813775 November 2, 2004 Finseth et al.
6816175 November 9, 2004 Hamp et al.
6816904 November 9, 2004 Ludwig et al.
6820278 November 16, 2004 Ellis
6826512 November 30, 2004 Dara-Abrams et al.
6837789 January 4, 2005 Garahi et al.
6839769 January 4, 2005 Needham et al.
6868225 March 15, 2005 Brown et al.
6882793 April 19, 2005 Fu et al.
6901603 May 31, 2005 Ziedler et al.
6925246 August 2, 2005 Behl
6931593 August 16, 2005 Grooters
6938101 August 30, 2005 Hayes et al.
6950624 September 27, 2005 Kim et al.
6973474 December 6, 2005 Hatayama
6993788 January 31, 2006 Lawrence et al.
7035804 April 25, 2006 Saindon et al.
7039643 May 2, 2006 Sena et al.
7047377 May 16, 2006 Elder et al.
7058635 June 6, 2006 Shah-Nazaroff et al.
7086077 August 1, 2006 Giammaressi
7098958 August 29, 2006 Wredenhagen et al.
7103906 September 5, 2006 Katz et al.
7127735 October 24, 2006 Lee et al.
7143432 November 28, 2006 Brooks et al.
7159232 January 2, 2007 Blackketter et al.
7159235 January 2, 2007 Son et al.
7168086 January 23, 2007 Carpenter et al.
7178161 February 13, 2007 Fristoe et al.
7213071 May 1, 2007 DeLima et
7231175 June 12, 2007 Ellis
7237253 June 26, 2007 Blackketter et al.
7240356 July 3, 2007 Iki et al.
7242324 July 10, 2007 Lai et al.
7248778 July 24, 2007 Anderson et al.
7260461 August 21, 2007 Rao et al.
7263709 August 28, 2007 Krapf
7269733 September 11, 2007 O'Toole, Jr.
7292774 November 6, 2007 Masters et al.
7302697 November 27, 2007 Wilson et al.
7305254 December 4, 2007 Findikli
7346920 March 18, 2008 Lamkin et al.
7356246 April 8, 2008 Kobb
7366199 April 29, 2008 Vaughan et al.
7483964 January 27, 2009 Jackson et al.
7536704 May 19, 2009 Pierre et al.
7574723 August 11, 2009 Putterman et al.
7624337 November 24, 2009 Sull et al.
7650621 January 19, 2010 Thomas et al.
7684673 March 23, 2010 Monroe
7689510 March 30, 2010 Lamkin et al.
7787010 August 31, 2010 DiFrancesco et al.
7793326 September 7, 2010 McCoskey et al.
7840977 November 23, 2010 Walker
7877766 January 25, 2011 Wu et al.
7917933 March 29, 2011 Thomas et al.
7929551 April 19, 2011 Dietrich
20010004338 June 21, 2001 Yankowski
20010007147 July 5, 2001 Goldschmidt Iki et al.
20010026287 October 4, 2001 Watanabe
20010033343 October 25, 2001 Yap et al.
20010039660 November 8, 2001 Vasilevsky et al.
20010042107 November 15, 2001 Palm
20010043700 November 22, 2001 Shima et al.
20020010652 January 24, 2002 Deguchi
20020026639 February 28, 2002 Haneda
20020043700 April 18, 2002 Sasaki et al.
20020046315 April 18, 2002 Miller et al.
20020056087 May 9, 2002 Berezowski et al.
20020059588 May 16, 2002 Huber et al.
20020059621 May 16, 2002 Thomas et al.
20020059642 May 16, 2002 Russ et al.
20020069218 June 6, 2002 Sull et al.
20020069746 June 13, 2002 Taira et al.
20020070982 June 13, 2002 Hill et al.
20020078293 June 20, 2002 Kou et al.
20020082901 June 27, 2002 Dunning et al.
20020087588 July 4, 2002 McBride et al.
20020088011 July 4, 2002 Lamkin et al.
20020104091 August 1, 2002 Prabhu et al.
20020113824 August 22, 2002 Myers, Jr.
20020120935 August 29, 2002 Huber et al.
20020161579 October 31, 2002 Saindon et al.
20020166123 November 7, 2002 Schrader et al.
20020174430 November 21, 2002 Ellis et al.
20020174444 November 21, 2002 Gatto et al.
20020180803 December 5, 2002 Kaplan et al.
20020188735 December 12, 2002 Needham et al.
20020194011 December 19, 2002 Boies et al.
20030005446 January 2, 2003 Jaff et al.
20030035404 February 20, 2003 Ozluturk et al.
20030037068 February 20, 2003 Thomas et al.
20030046437 March 6, 2003 Eytchison et al.
20030066084 April 3, 2003 Kaars
20030066092 April 3, 2003 Wagner
20030068154 April 10, 2003 Zylka
20030101104 May 29, 2003 Dimitrova et al.
20030105813 June 5, 2003 Mizutani
20030110499 June 12, 2003 Knudson et al.
20030135860 July 17, 2003 Dureau
20030149980 August 7, 2003 Ellis et al.
20030149988 August 7, 2003 Ellis et al.
20030152096 August 14, 2003 Chapman
20030162096 August 28, 2003 Michot et al.
20030163832 August 28, 2003 Tsuria et al.
20030194260 October 16, 2003 Ward et al.
20030206710 November 6, 2003 Ferman et al.
20030214955 November 20, 2003 Kim
20040008972 January 15, 2004 Haken
20040088731 May 6, 2004 Putterman et al.
20040117831 June 17, 2004 Ellis
20040128686 July 1, 2004 Boyer et al.
20040139233 July 15, 2004 Kellerman et al.
20040156614 August 12, 2004 Bumgardner et al.
20040181814 September 16, 2004 Ellis et al.
20040184763 September 23, 2004 DiFrancesco
20040193648 September 30, 2004 Lai et al.
20040220091 November 4, 2004 Adam et al.
20040226034 November 11, 2004 Kaczowka et al.
20040237104 November 25, 2004 Cooper et al.
20040255326 December 16, 2004 Hicks, III et al.
20040259537 December 23, 2004 Ackley
20040267965 December 30, 2004 Vasudevan et al.
20050028208 February 3, 2005 Ellis
20050039208 February 17, 2005 Veeck et al.
20050046174 March 3, 2005 Botes
20050071876 March 31, 2005 van Beek
20050102324 May 12, 2005 Spring et al.
20050120373 June 2, 2005 Thomas et al.
20050132264 June 16, 2005 Joshi et al.
20050138137 June 23, 2005 Encarnacion et al.
20050138658 June 23, 2005 Bryan
20050204388 September 15, 2005 Knudson et al.
20050227611 October 13, 2005 Ellis
20050246393 November 3, 2005 Coates et al.
20050251827 November 10, 2005 Ellis et al.
20060004685 January 5, 2006 Pyhalammi et al.
20060015888 January 19, 2006 Shih
20060031883 February 9, 2006 Ellis et al.
20060037054 February 16, 2006 McDowell et al.
20060064728 March 23, 2006 Son et al.
20060080707 April 13, 2006 Laksono
20060085835 April 20, 2006 Istvan et al.
20060090186 April 27, 2006 Santangelo et al.
20060095942 May 4, 2006 van Beek
20060173838 August 3, 2006 Garg et al.
20060215650 September 28, 2006 Wollmershauser et al.
20060238648 October 26, 2006 Wogsberg
20060248570 November 2, 2006 Witwer
20060253874 November 9, 2006 Stark et al.
20060259949 November 16, 2006 Schaefer et al.
20060271953 November 30, 2006 Jacoby et al.
20070011709 January 11, 2007 Katz et al.
20070022442 January 25, 2007 Gil et al.
20070028267 February 1, 2007 Ostojic et al.
20070055980 March 8, 2007 Megeid et al.
20070089160 April 19, 2007 Ando
20070094702 April 26, 2007 Khare et al.
20070124781 May 31, 2007 Casey et al.
20070147351 June 28, 2007 Dietrich et al.
20070157234 July 5, 2007 Walker
20070157240 July 5, 2007 Walker
20070157241 July 5, 2007 Walker
20070157242 July 5, 2007 Cordray et al.
20070157260 July 5, 2007 Walker
20070157266 July 5, 2007 Ellis et al.
20070162661 July 12, 2007 Fu et al.
20070174774 July 26, 2007 Lerman et al.
20070198659 August 23, 2007 Lam
20070220024 September 20, 2007 Putterman et al.
20070220580 September 20, 2007 Putterman et al.
20070282969 December 6, 2007 Dietrich et al.
20070283046 December 6, 2007 Dietrich et al.
20080034396 February 7, 2008 Lev
20080060001 March 6, 2008 Logan et al.
20080263227 October 23, 2008 Roberts et al.
20080307477 December 11, 2008 Omernick
20090019492 January 15, 2009 Grasset
20100186034 July 22, 2010 Walker
20110131607 June 2, 2011 Thomas et al.
20110185392 July 28, 2011 Walker
Foreign Patent Documents
2635571 May 2009 CA
0 424 469 May 1991 EP
0 535 749 April 1993 EP
0 572 090 December 1993 EP
0 583 196 February 1994 EP
0 605 115 July 1994 EP
0 624 039 November 1994 EP
0 662 771 July 1995 EP
0 673 160 September 1995 EP
0 682 452 November 1995 EP
0 711 076 May 1996 EP
0 725 539 August 1996 EP
0 753 964 January 1997 EP
0 758 833 February 1997 EP
0 762 756 March 1997 EP
0 763 938 March 1997 EP
0 862 833 May 1997 EP
0 836 321 April 1998 EP
0 854 645 July 1998 EP
0 874 524 October 1998 EP
0 924 927 June 1999 EP
0 932 275 July 1999 EP
0 940 985 September 1999 EP
0 944 253 September 1999 EP
0 944 257 September 1999 EP
1 099 341 January 2000 EP
0 986 046 March 2000 EP
0 806 111 October 2001 EP
1 213 919 June 2002 EP
1 217 787 June 2002 EP
0 969 662 July 2002 EP
1 237 372 September 2002 EP
1 244 300 September 2002 EP
0 880 856 March 2005 EP
1 687 951 May 2005 EP
0 757 873 March 2006 EP
1 427 148 June 2006 EP
1 377 049 August 2006 EP
1 763 234 March 2007 EP
1 613 066 June 2007 EP
0 821 856 September 2007 EP
1 327 209 August 2009 EP
2 256 115 November 1992 GB
2 307 628 May 1997 GB
60-061935 September 1985 JP
06-111413 April 1994 JP
06-303541 October 1994 JP
07-336318 December 1995 JP
09-214873 August 1997 JP
10-65978 March 1998 JP
11-032272 February 1999 JP
11-177962 July 1999 JP
11-205711 July 1999 JP
11-341040 December 1999 JP
2000-004272 January 2000 JP
2003-162444 June 2003 JP
2003-209893 July 2003 JP
10-533103 February 2005 JP
1999-0086454 December 1999 KR
2000-0059522 October 2000 KR
2000-0059522 October 2000 KR
247388 October 1994 TW
WO 88/04507 June 1988 WO
WO 89/12370 December 1989 WO
WO 90/00847 January 1990 WO
WO 91/00670 January 1991 WO
WO 91/07050 May 1991 WO
WO 92/04801 March 1992 WO
WO 92/22983 December 1992 WO
WO 93/08542 April 1993 WO
WO 93/22877 November 1993 WO
WO 94/14284 June 1994 WO
WO 95/01058 January 1995 WO
WO 95/02945 January 1995 WO
WO 95/004431 February 1995 WO
WO 95/15658 June 1995 WO
WO 95/31069 November 1995 WO
WO 95/32583 November 1995 WO
WO 95/32584 November 1995 WO
WO 95/32585 November 1995 WO
WO 95/32587 November 1995 WO
WO 96/09721 March 1996 WO
WO 96/17467 June 1996 WO
WO 96/25821 August 1996 WO
WO 96/31980 October 1996 WO
WO 96/33572 October 1996 WO
WO 96/34467 October 1996 WO
WO 96/34491 October 1996 WO
WO 96/41472 December 1996 WO
WO 96/41478 December 1996 WO
WO 97/12342 April 1997 WO
WO 97/13368 April 1997 WO
WO 97/21291 June 1997 WO
WO 97/32434 September 1997 WO
WO 97/34413 September 1997 WO
WO 97/34414 September 1997 WO
WO 97/37500 October 1997 WO
WO 97/42763 November 1997 WO
WO 97/46016 December 1997 WO
WO 97/46943 December 1997 WO
WO 97/47124 December 1997 WO
WO 97/48228 December 1997 WO
WO 97/49237 December 1997 WO
WO 98/01995 January 1998 WO
WO 98/07277 February 1998 WO
WO 98/10589 March 1998 WO
WO 98/12872 March 1998 WO
WO 98/17033 April 1998 WO
WO 98/17064 April 1998 WO
WO 98/18260 April 1998 WO
WO 98/19459 May 1998 WO
WO 98/26528 June 1998 WO
WO 98/26584 June 1998 WO
WO 98/26596 June 1998 WO
WO 98/31115 July 1998 WO
WO 98/31116 July 1998 WO
WO 98/34405 August 1998 WO
WO 98/38831 September 1998 WO
WO 98/47279 October 1998 WO
WO 98/47283 October 1998 WO
WO 98/48566 October 1998 WO
WO 98/53611 November 1998 WO
WO 99/03267 January 1999 WO
WO 99/04561 January 1999 WO
WO 99/11060 March 1999 WO
WO 99/12320 March 1999 WO
WO 99/14945 March 1999 WO
WO 99/27681 June 1999 WO
WO 99/28897 June 1999 WO
WO 99/35753 July 1999 WO
WO 99/39466 August 1999 WO
WO 99/56473 November 1999 WO
WO 99/60790 November 1999 WO
WO 99/64969 December 1999 WO
WO 99/65244 December 1999 WO
WO 99/66725 December 1999 WO
WO 00/04706 January 2000 WO
WO 00/04707 January 2000 WO
WO-00/04709 January 2000 WO
WO 00/05885 February 2000 WO
WO 00/11869 March 2000 WO
WO 00/16548 March 2000 WO
WO 00/17738 March 2000 WO
WO 00/30345 May 2000 WO
WO 00/33208 June 2000 WO
WO 00/33560 June 2000 WO
WO 00/33565 June 2000 WO
WO 00/34891 June 2000 WO
WO 00/58967 October 2000 WO
WO 00/59230 October 2000 WO
WO 00/74383 December 2000 WO
WO 01/01689 January 2001 WO
WO 01/35662 May 2001 WO
WO 01/50743 July 2001 WO
WO 01/01677 October 2001 WO
WO 03/046727 June 2003 WO
WO 2004/032511 April 2004 WO
WO 2004/061699 July 2004 WO
WO 2007/078503 July 2007 WO
Other references
  • “Addressable Converters: A New Development at CableData,” Via Cable, vol. 1, No. 12 (Dec. 1981).
  • BrugLiera, V. “Digital On-Screen Display—A New Technology for the Consumer Interface,” Symposium Record Cable Sessions, 18th International Television Symposium and Technical Exhibition, Montreux, Switzerland Jun. 10-15, 1993, pp. 571-586 (Jun. 11, 1993).
  • CableData brochure, “A New Approach to Addressability” (undated).
  • Chang, Y., et al., “An Open-Systems Approach to Video on Demand,” IEEE Communications Magazine, vol. 32, No. 5 pp. 68-80 (May 1994).
  • “Digital Video Broadcasting (DVB); DVB specification for data broadcasting”, European Telecommunications Standards Institute, Draft EN 301 192 V1.2.1 (Jan. 1999).
  • “Electronic Programme Guide (EPG); Protocol for a TV Guide using electronic data transmission” by European Telecommunication Standards Institute, May 1997, Valbonne, France, publication No. ETS 300 707.
  • Gondow, S., et al., “The Architecture of Communication Migration and Media State Management for Distributed Applications on Wearable Networks,” Information Processing Society of Japan (National Conference Lecture Collected Paper), Tokyo, Japan, Oct. 3, 2000, pp. 1-2.
  • Hofmann, et al., “Videotext Programmiert Videorecorder,” Rundfunktechnische Mitteilungen, Nov.-Dec. 1982, pp. 254-257 (translation abstract attached).
  • Li, et al., “Distributed Multimedia Systems,” Proceedings of the IEEE, vol. 85, No. 7, pp. 1063-1108 (Jul. 1997).
  • Miller, M. D. “A Scenario for the Deployment of Interactive Multimedia Cable Television Systems in the United States in the 1990's,” Proceedings of the IEEE, vol. 82, No. 4, pp. 585-589 (Apr. 1994).
  • David M. Rudnick, U.S. Appl. No. 09/283,681, filed Apr. 1, 1999, entitled Interactive Television Program Guide System Having Graphic Arrangements of Program Event Regions.
  • A. C. Snoeren et al., “An End-to-End Approach to Host Mobility” 6th ACM-IEEE International Conference on Mobile Computing and Networking (Mobicom 2000), Boston, MA, USA, Aug. 2000, pp. 1-12.
  • Sorce, J. et al., “Designing a Broadband Residential Entertainment Service: A Case Study,” 13th International Symposium Human Factors in Telecommunications, Torino, Italy, Sep. 10-14, 1990 pp. 141-148.
  • F. Teraoka et al., “Host Migration Transparency in IP networks: The VIP Approach” ACM SIGCOMM—Computer Communication Review, ACM Press, New York, NY, USA, Jan. 1993, pp. 45-65.
  • The New York Times Website Article, “2 Makers Plan Introductions of Digital VCR”, by John Markoff, Mar. 29, 1999.
  • Article: “Windows 98 Feature Combines TV, Terminal and the Internet”, New York Times, Aug. 18, 1998.
  • Abarca, C. et al., Telecommunications Information Networking Architecture Consortium, Service Architecture, Version 5.0, Jun. 16, 1997, 168 pages.
  • Hong, C.S. et al., “A Networking Architecture for Mobility Services Using Mobile Agent Approach”, Proceedings of the TINA '97—Global Convergence of Telecommunications and Distributed Object Computing, IEEE, 1997, 11 pages.
  • Limongiello, A. et al., “An Experimental Open Architecture to Support Multimedia Services based on CORBA, Java and WWW Technologies”, Intelligence in Services and Networks: Technology for Cooperative Competition, Fourth International Conference on Intelligence in Services and Networks, IS&N'97, May 27-29, 1997, pp. 69-75.
  • Davic 1.3.1 Specification Part 1, Published in 1998 by Digital Audio-Visual Counsel, 85 pages.
  • Wedlund, E. et al. “Mobility Support using SIP”, ACM/IEEE International Conference on Wireless and Mobile Multimedia, pp. 76-82, Aug. 20, 1999.
  • Federighi, C. et al. “A Distributed Hierarchical Storage Manager for a Video-on-Demand System”, Storage and Retrieval for Image and Video Databases II, IS&T/SPIE, Symp. on Elec. Imaging Sci. & Tech., San Jose, CA, pp. 1-13, Feb. 1994.
  • Fox, A., et al., “Adapting to Network and Client Variation Using Infrastructural Proxies: Lessons and Perspectives”, IEEE Personal Communications, pp. 10-19, Aug. 1998.
  • Chawathe, Y., et al., “A Proxy Architecture for Reliable Multicast in Heterogeneous Environments”, ACM Multimedia '98, Bristol, UK, pp. 151-159, 1998.
  • Rowe, L., et al., “A Continuous Media Player”, Proc. 3rd Int. Workshop on Network and OS Support for Digital Audio and Video, San Diego, CA, 11 pages, Nov. 1992.
  • Mobile Agent Approach, Global Convergence of Telecommunications and Distributed Object Computing, pp. 297-307 (1997), Section 8.4: X.
  • “Don Imus: The Thinking Man's Shock Jock”, Broadcasting Cable, Jun. 13, 1994, pp. 49-52.
  • December, J., “Understanding the Potential of Java and the Web”, Presenting Java, published Sep. 20, 1995.
  • “TV Listing Star on the Computer”, Central Penn Business Journal/HighBeam Research, pp. 1-4, Mar. 15, 1996.
  • Bestler, C. et al., “Flexible Data Structures and Interface Rituals for Rapid Development of OSD Applications”, published NCTA Technical Papers, pp. 223-236, 1993.
  • Davis, B., “Violence on Television”, TV Guide on Screen to the US House of Representatives Committee of Energy and Commerce Subcommittee on Telecommunications and Finance, pp. 93-163, Jun. 25, 1993.
  • Uniden UST-4800 Integrated Receiver/Descrambler, Operating Guide, copyright 1990, Uniden America Corporation, 24 pages.
  • Uniden UST-4800 Integrated Receiver/Descrambler, Installation Guide, Installation Device, copyright 1990, Uniden America Corporation, 60 pages.
  • Uniden UST-4800 Super Integrated Receiver/Descrambler, Preliminary Reference Manual, 80 pages, Nov. 12, 1991.
  • Cable Data: Via Cable, vol. 1, No. 12, Addressable Converters: A New Development at CableData, 11 pages, Dec. 1981.
  • Verma, D., “Content Distribution Networks—An Engineering Approach”, p. 24-49, 2002.
  • Dias, D. “A Scalable and Highly Available Web Server”, IEEE, Proceedings of Compcon '96, p. 85-92, 1996.
  • Schroeder, T. et al. “Scalable Web Server Clustering Technologies”, University of Nebraska—Lincoln CSE Journal Articles, Department of Computer Science and Engineering, pp. 38-45, Jun. 1, 2000.
  • Knutsson, B. et al., “Transparent Proxy Signalling”, Journal of Communications and Networks, vol. 3, No. 2, p. 164-174, Jun. 2001.
  • Arango et al., “The Touring Machine System,” Communications of the ACM, Jan. 1993, vol. 36, No. 1, pp. 68-77.
  • Dimitrova, et al. “Personalizing Video Recorders in Multimedia Processing and Integration.” ACM 2001.
  • Fortino et al., A Cooperative Playback System for On-Demand Multimedia Sessions over Internet, 2000 IEEE, pp. 41-44.
  • Haas et al., Proceedings of ICIP 2002 Personalized News Through Content Augmentation and Profiling:, Rochester, NY, Sep. 2002.
  • Han et al., “Dynamic Adaptation in an Image Transcoding Proxy for Mobile Web Browsing,” IEEE Personal Communications, Dec. 1998, pp. 8-17.
  • IBM Corporation “IBM Content Manager VideoCharger, New dimensions for enterprise content, DB2 Data Management Software” pp. 1-4, Mar. 2002.
  • IBM Corporation “IBM Content Manager VideoCharger, Version 8, New dimensions for enterprise content, DB2 Data Management Software, pp. 1-4,” May 2002, Visit IBM Web site at ibm.com/software/data/videocharger.
  • IBM Corporation “IBM VideoCharger for AIX Version 2.0” Streaming the power of video to your desktop, pp. 1-5 Visit the IBM VideoCharger Website at: www.software.ibm.com/data/videocharger/; (undated).
  • IBM Corporation, “IBM Video Charger Server”, pp. 1-2, Jun. 1998.
  • Jaidev, “XSLT—A Wired and Wireless Case Study,” http://csharpcomputing.com/XML Tutorial/Lesson15.htm; Oct. 14, 2005.
  • Mah et al., “Providing Network Video Service to Mobile Clients,” 1993 IEEE, pp. 48-54.
  • Papers Delivered (Part 1), 61st National Conference, Information Processing Society of Japan, Oct. 3-5, 2000.
  • Pham et al,, “Exploiting Location-Based Composite Devices to Support and Facilitate Situated Ubiquitous Computing,” HUC 2000, LNCS 1927, pp. 143-156.
  • Pogue, D., “State of the Art: For TiVo and Replay, New Reach,” N.Y. Times, May 29, 2003.
  • Randerson, J., “Let Software Catch the Game for You,” New Scientist, Jul. 3, 2004.
  • Realplayer 8 Plus User Manual, Rev. 1, Real Networks, Inc. p. 32 (2000).
  • Rewind, reply and unwind with new high-tech TV devices, by Lawrence J. Magid, LA Times (This document was printed from the internet on Jun. 6, 1999 and bears a date of May 19, 1999).
  • Thesis of Bo Zou “Mobile IDS Protocol: A badge-activated application level handoff of a multimedia streaming to support user mobility” (Aug. 2000) available at the website of the Multimedia Operating System and Networking Group of the University of Illinois.
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Respondents' Response to the Commission's Determination to Review the Final Initial Determination” Aug. 26, 2013 (62 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Complainants' Reply Submission in Response to Commission's Determination to Review the Final Initial Determination” Aug. 30, 2013 (32 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Respondents Netflix, Inc.'s and Roku, Inc.'s Response to Complainants' Initial Submission in Response to Commission's Determination to Review the Final Initial Determination” Aug. 30, 2013 (43 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Notice of the Commission's Final Determination Finding No Violoation of Section 337; Termination of the Investigation” Nov. 1, 2013 (4 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Commission Opinion” Dec. 11, 2013 (27 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Respondent Netflix Response to Complaintants' Petition for Review” Jul. 12, 2013 (64 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Respondent Netflix, Inc.'s Summary of Issues for its Repsonse to Complainants Petition for Review” Jul. 12, 2013 (6 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, “Notice of Commission Determination to Review in its Entirety a Final Initial Determination Finding No Violation of Section 337” Aug. 9, 2013 (6 pages).
  • ITC Investigation of Certain Products Containing Interactive Program Guide and Parental Control Technology, Investigation No. 337-TA-845, Complainants' Initial Submission in Response to Commission's Determination to Review the Final Initial Determination Aug. 23, 2013 (55 pages).
  • U.S. Appl. No. 09/330,860, filed Jun. 11, 1999, Ellis.
  • U.S. Appl. No. 09/332,244, filed Jun. 11, 1999, Ellis.
  • U.S. Appl. No. 09/354,344, filed Jul. 16, 1999, Ellis.
  • S. Draper et al., TV Anytime, Proceedings International Broadcasting Convention, 1999, pp. 103-108.
  • United Kingdom: BSKyB to launch integrated personal TV recorder, BBC Monitoring Media, Sep. 11, 2000.
Patent History
Patent number: 8973069
Type: Grant
Filed: Oct 8, 2013
Date of Patent: Mar 3, 2015
Patent Publication Number: 20140040938
Assignee: Rovi Guides, Inc. (Santa Clara, CA)
Inventors: William L. Thomas (Evergreen, CO), Michael D. Ellis (Boulder, CO), Kevin B. Easterbrook (Gilbert, AZ), M. Scott Reichardt (Tulsa, OK), Robert A. Knee (Lansdale, PA)
Primary Examiner: Hunter B Lonsberry
Application Number: 14/048,818
Classifications
Current U.S. Class: Scheduling (e.g., Grouping Users Together) (725/97); Video-on-demand (725/87); Server Or Headend (725/91)
International Classification: H04N 7/173 (20110101); H04N 21/482 (20110101); G06F 3/0481 (20130101); H04N 5/445 (20110101); H04N 5/76 (20060101); H04N 21/2187 (20110101); H04N 21/258 (20110101); H04N 21/262 (20110101); H04N 21/2743 (20110101); H04N 21/2747 (20110101); H04N 21/278 (20110101); H04N 21/422 (20110101); H04N 21/431 (20110101); H04N 21/441 (20110101); H04N 21/47 (20110101); H04N 21/472 (20110101); H04N 21/475 (20110101); H04N 21/6587 (20110101); H04N 5/44 (20110101); H04N 5/775 (20060101); H04N 5/781 (20060101); H04N 5/85 (20060101); H04N 9/804 (20060101);