US 8,438,601 B2Grant
Resource management for a networked personal video recording system
Issue Date:2013-05-07
•27 Claims
•16 Drawing Sheets
Abstract
A networked personal video recording (“PVR”) system couples a plurality of clients to one or more PVR media servers over a network. One or more PVR media servers include television tuners to tune television signals. A storage medium buffers the television signals to implement PVR functionality. For example, the PVR media server records television programs for clients. Clients are assigned to television tuners, and the clients display television programs received at the assigned tuner. The network transfers the buffered television signals to the clients.
Metadata
Assignee
- Rovi Solutions Corporation
Inventors
- Daniel Putterman
- Brad Dietrich
- Jeremy Toeman
- Pedro Freitas
- Ludovic Legrand
- Shawn McCaffrey
- James Grimm
- Lijia Jin
- Paul Novaes
Application Information
Application Number:US 10/613,399
Filing Date:2003-07-02
Priority Date:2003-07-02
Art Unit:2427
Classifications
IPC:
H04N7/18
Patent Drawings (16 sheets)
Description
Background of the Invention
[0001] 1. Field of the Invention
[0002] The present invention is directed toward the field of video recording, and more particularly toward a networked personal video recording system.
[0003] 2. Art Background
[0004] Typically, a personal video recorder (“PVR”) includes a storage device, such as a hard disk drive, and a television input. Similar to a video cassette recorder, the PVR system permits a user to record television programming. Specifically, the PVR system stores a digital representation of television signals on the storage device for subsequent replay by the user. The PVR system also buffers live television. For this application, television signals are stored on the storage device and output to a television for viewing by a user. The function of buffering television permits a user to seemingly manipulate live television. For example, a user may pause, rewind, and, to a limited extent, fast forward the live television signal. Due to the numerous functions and features, PVR systems have become very popular. However, these PVR systems typically operate on a signal television signal for subsequent display on a single television. As such, it is desirable to develop a PVR system that effectively integrates one or more television inputs with a network of televisions.
Summary of the Invention
[0005] A personal video recording (“PVR”) system manages resources for a plurality of clients. The system includes at least one PVR media server. The PVR media server contains tuners to tune television signals and a storage medium to buffer the television signals. The clients are coupled to the PVR media server over a network. The clients generate requests for PVR system services. In one embodiment, the clients generate requests to record a television program and to watch buffered live television. In response to the request, the system allocates resources of the PVR system to the clients, as appropriate, to delivery services to the clients. For example, if the client desires to watch buffered live television, the system assigns a tuner to the client, generates a buffer position to identify a location within the television signal for playback of the television signal at a client, and delivers the television signal using the buffer position. If the client desires to record a television program, then the system assigns a tuner to the client, allocates space on the storage medium to record the television program, and stores the television signal on the storage medium during a time scheduled for the television program.
[0006] In one embodiment, the system attempts to resolve conflicts for system resources. For example, if a client requests to watch buffered live television at a channel selected, then the system determines whether one of the tuners is available to receive the television signal. If so, the system assigns the tuner to receive the television signal at the channel selected. If not, the system determines which tuners are potentially available by querying clients assigned to the tuners potentially available to determine whether the clients desire to change a current channel of the tuner to the channel selected and by assigning a tuner potentially available to receive a television signal at the channel selected if no clients cancel a change of the current channel. In another embodiment, to record a television program, the system attempts to resolve any conflicts of assigning resources by determining whether one of the tuners is available to receive the television signal. If so, the system assigns the tuner to receive the television signal. If not, the system determines which tuners are potentially available, queries clients assigned to the tuners potentially available to determine whether the clients desire to cancel recordation of the television program, and assigns a tuner potentially available to receive the television signal if no clients cancel recordation of the television program.
Brief Description of the Drawings
[0007] FIG. 1 is a block diagram illustrating one embodiment for the networked PVR system of the present invention.
[0008] FIG. 2 is a block diagram illustrating one embodiment for the networked PVR system of the present invention.
[0009] FIG. 3 is a block diagram illustrating one embodiment of television signal buffering for the networked PVR system.
[0010] FIG. 4 is a block diagram illustrating on embodiment for a buffer in the networked PVR system.
[0011] FIG. 5 is a flow diagram illustrating one embodiment for viewing video in the networked PVR system.
[0012] FIG. 6 is a flow diagram illustrating one embodiment for using the networked PVR system of the present invention.
[0013] FIG. 7 is a flow diagram illustrating one embodiment for scheduling events in the networked PVR system of the present invention.
[0014] FIG. 8 is a flow diagram illustrating one embodiment for recording programs.
[0015] FIG. 9 illustrates client device aggregation of media in accordance with one embodiment of the present invention.
[0016] FIG. 10 is a flow diagram illustrating one embodiment for client media aggregation over a network.
[0017] FIG. 11 is a block diagram illustrating one embodiment for software components operating on a networked PVR system device.
[0018] FIG. 12 is a block diagram illustrating an example home network for the networked PVR system.
[0019] FIG. 13 is a flow diagram illustrating one embodiment for discovering devices in the networked PVR system.
[0020] FIG. 14 is a block diagram illustrating one embodiment for a data model for elements of a networked PVR system.
[0021] FIG. 15 is a block diagram illustrating one embodiment of accessing a data store through the networked PVR system.
Detailed Description
[0022] FIG. 1 is a block diagram illustrating one embodiment for the networked PVR system of the present invention. For this embodiment, a home entertainment system includes “n” clients and “m” personal video recording (“PVR”)-media servers (i.e., “n” and “m” are any integer values greater than or equal to one). A client, as used herein, is any device that plays back media. For example, a client may comprise a television to playback video and live television. A server, as used herein, connotes any device that stores or acquires media. A PVR-media server connotes any device that delivers video to the network, including a device that acquires television signals and buffers television signals for viewing by the clients. For example, a PVR-media server may comprise a device with storage, designed specifically to minimize cost or a PVR-media server may comprise a personal computer.
[0023] As shown in FIG. 1 , different types of media, including television signals, are input to each PVR-media server. The PVR-media servers may store media, including audio and video, for access by the clients. In addition, the PVR-media servers buffer live television. Each client (e.g., client1, client2 and clientn) may access media stored or buffered on the PVR-media servers via network 110. Network 110 may comprise any type of network, including wireless networks. For example, network 110 may comprise networks implemented in accordance with standards, such as IEEE 802.3, Ethernet 10/100 on Category 5, HPNA, Home Plug, IEEE 802.11x, IEEE 1394, and USB 1.1/2.0.
[0024] The networked system 100, shown in FIG. 1 , may be implemented in a residence. For example, each client may consist of a television for viewing stored video and television. Such an example home system may include a client television located in the living room, one or more client televisions located in bedrooms, and a client television located in the kitchen. In general, system 100 permits any client to playback media (e.g., video) stored or acquired through any of the PVR-media servers. The PVR-media servers may be configured to acquire television signals from different sources. For example, PVR-media server1 may acquire a television signal from a satellite television system, whereas PVR-media server2 may acquire a television signal from a cable television system. A PVR-media server includes permanent storage (e.g., hard disk drive) and at least one television tuner. Thus, system 100 permits any client to access media from any tuner or media stored on any PVR-media server.
[0025] FIG. 2 is a block diagram illustrating one embodiment for the networked PVR system of the present invention. Similar to system 100 of FIG. 1 , system 200 includes “n” clients, including at least two televisions. For this example system, there are three PVR-media servers (PVR-media server1, PVR-media server2, and PVR-media server3). The clients access media (e.g., video) through network 210. Each PVR-media server includes storage (220, 230 and 240) and “n” tuners (i.e., “n” represents any integer greater than or equal to one). The PVR-media servers receive a television signal. For this example, PVR-media server, and PVR-media server2 receive a signal from television service provider1, and PVR-media server3 receives a television signal from television service provider2. Under this configuration, any client (i.e., client1, client2, and clientn) may receive an output video signal demodulated by any tuner (i.e., any one of “n” tuners from PVR-media server1, PVR-media server2, and PVR-media server3).
[0026] FIG. 3 is a block diagram illustrating one embodiment of television signal buffering for the networked PVR system. Every tuner has a continuous ring buffer. In one embodiment, the size of the ring buffer is flexible, and may be configured. For example, the ring buffer may permit storage of sixty (60) minutes of television. In turn, each client has an independent buffer position for every ring buffer and stored video available in the system. FIG. 3 illustrates an example networked PVR system-with “n” tuners. The “n” tuners may be implemented in conjunction with one or more PVR-media servers. As shown in FIG. 3 , the output of each tuner is input to a corresponding buffer (e.g., ring buffer). Each client, client1-n, has an associated buffer position for each tuner-buffer pair. Specifically, as shown in FIG. 3 , client1 has buffer positions for tuner1, tuner2, and tunern. Similarly, clientn also has independent buffer positions for tuners 1-n. In general, a buffer position may comprise a pointer to a position within a video or to a position within a tuner buffer. Each tuner buffer position is depicted in FIG. 3 as a timeline, wherein the beginning and end line segments represent the length of the buffer, and the center line segments represent the clients current buffer position.
[0027] A buffer in the networked PVR system includes a write tap and a plurality of read taps. FIG. 4 is a block diagram illustrating on embodiment for a buffer in the networked PVR system. A tuner 410 outputs data (e.g., MPEG encoded video) for storage on buffer 420. In one embodiment, the buffer comprises a hard disk drive. The tuner 410 may write to the hard disk drive using a file system. In other embodiments, the tuner 410 may execute direct write operations on the hard disk drive. The buffer has a plurality of read taps. For the example shown in FIG. 4 , the buffer has “n” read taps (i.e., “n” represents any integer greater than or equal to one). Each read tap supports an independent buffer position. For example, read tap1 supports tuner buffer position1, read tap2 supports tuner buffer position2, and read tapn supports tuner buffer positionn. In one software embodiment, the software conducts multiple read operations on a file to generate the multiple taps.
[0028] In one embodiment, the system sets boundary conditions on the relative positions of read and write buffer taps. One boundary condition requires that the read tap not fall behind the write tap an amount greater than the buffer length. For example, a client may view a buffered television program using a first buffer position (i.e., read tap). For this example, a client may pause the viewing of the television program. If this occurs, the first buffer position is constant (i.e., the first buffer position is not advanced). However, the write position is advanced as the television signal is received. Therefore, the distant between the write buffer position and the read buffer position is increased. If the difference between the read buffer position and the write buffer position exceeds the length of the buffer, then an event is generated. A response to the event may be to advance the read buffer position. Also, in another scenario, if a read buffer position advances forward to the corresponding write buffer position, then the read buffer position becomes the location of the write buffer position (i.e., the read buffer position does not advance beyond the write buffer position). For example, a client may fast forward a buffer television program up to the current write position.
[0029] FIG. 5 is a flow diagram illustrating one embodiment for viewing video in the networked PVR system. Initially, the user receives a menu option, displayed on a client television, to watch live TV or to select media from a PVR-media server (block 520, FIG. 5 ). If the client does not elect to watch live television, then the client selects media stored on a PVR-media server (blocks 520 and 530, FIG. 5 ). Then, as discussed below, the client sets the buffer position through the system. If the user elects to watch live television, then the client selects a television service provider (block 510, FIG. 5 ). If there is only one television service provider available to the client, then the system eliminates the function of block 510. In one embodiment, the service provider selection may be configured during a set-up mode. For example, the television in the living room may be configured to always receive a television signal from a satellite system. The system selects a tuner for the client (block 540, FIG. 5 ). In one embodiment, the system automatically allocates, for the client television, an available tuner.
[0030] The user views the program at the client (block 580, FIG. 5 ). If the user desires to change the program, then the client selects programming from the electronic programming guide displayed at the client (blocks 555 and 550, FIG. 5 ). If the user does not desire to change the program, then the user potentially sets the buffer position. If the user has an existing buffer position and the user desires to set the program to an existing buffer position, then the user selects, through a menu, the existing buffer position (blocks 570 and 572, FIG. 5 ). If the client does not have an existing buffer position, then the system sets the buffer position to the start of the file/media (blocks 570 and 574, FIG. 5 ). The user may desire to change the buffer position to an existing buffer position (block 560 FIG. 5 ). If the user desires to set the program to an existing buffer position, the user, through the system, changes the buffer position. (block 565, See FIG. 6 ). For example, the user may select a program already in progress. Under this scenario, the user may wish to view the program from the beginning. To accomplish this, the user selects a new buffer position to start at the beginning of the program. The user then views the program at the client (block 580, FIG. 5 ).
[0031] In one embodiment, the PVR-media server acquires programming data, referred to as an electronic programming guide (“EPG”), from an EPG content provider. The EPG dataset provides a list of programs, including channels and times, available from the corresponding television service provider. Typically, the EPG data is provided on a service basis from the EPG content provider. The PVR-media server contacts the EPG content provider to acquire updated programming data. The PVR system utilizes the EPG data to schedule programs as well as to provide programming menus to the clients. Thus, for this embodiment, the PVR system scheduler is specific to an EPG data set. However, a home media networked system may include servers that utilize different EPG content providers, and consequently operate using different EPG data sets. For this embodiment, users only view channel selection menus based on the underlying EPG data sets. Thus, the menu presented at the client is dependent upon the underlying PVR-media server.
[0032] In one embodiment, the PVR system permits a client to select television programs without requiring the client to understand the notion of a television tuner. For example, two clients may be receiving a signal from the same tuner. Under this scenario, one of the clients may desire to change the channel to view a different program without affecting the ability of the other client to view the current program. The PVR system provides a menu that permits the user to select additional programming. In one embodiment, the programming menu is based on a specific television service provider and corresponding EPG content provider.
[0033] In one embodiment, the user selects programming within a television service provider—EPG content data set. A client may set-up the system to automatically select a preferred television service provider. If a user executes an operation that requires a new tuner, the user selects programming from the previously selected EPG content provider. After the user selects a new program, the system allocates a tuner to the user. Under this scenario, the user does not need to understand the notion of a tuner. Instead, the client only selects a program or cancels an event in order to acquire use of a tuner. If a tuner is not available for allocation to the user, then the system resolves conflict through predetermined “conflict management” procedures. One embodiment for resolving certain conflicts that arise in networked PVR systems is described more fully below.
[0034] The networked PVR system permits users to select buffer positions from different clients. For example, a user watching a program at a first client (e.g., television in living room) may go to another room and pickup that program from a second client (e.g., television in kitchen) where they left off watching on the first client. Under this scenario, the user may pause the program playing at the living room client for subsequent viewing at the kitchen client. FIG. 6 is a flow diagram illustrating one embodiment for using the networked PVR system of the present invention. For this scenario, the user selects, from a client, a program for viewing (block 610, FIG. 6 ). The user may then desire to select that program from a different client. To accomplish this, the user queries the PVR system to determine other clients tuned to be selected program (block 620, FIG. 6 ). If other clients are tuned to the selected program, then the system displays a list of clients tuned to the program (blocks 630 and 640, FIG. 6 ). For the above scenario, the user may query the PVR system from the client in the kitchen to pickup the program paused in the living room. In one embodiment, the user, from a client, pulls-up a menu item to determine “Who is watching the selected program?” In response, the PVR system displays a menu of client locations currently playing the selected program. For the above example, the PVR system displays the “living room client” to identify that the selected program is currently playing in the living room. Alternatively, if no other clients are tuned to the selected program, then the buffer position is set to the start of the program (blocks 630 and 655, FIG. 6 ).
[0035] If the user desires to select a buffer position of another client, then the PVR system copies a buffer position from the selected client for use as the buffer position for the user's client (blocks 650 and 660, FIG. 6 ). For the above example, the user, at the kitchen client, selects the buffer position of the living room client, so as to pickup the selected program at the position of the program was paused. Alternatively, the user may desire to view the selected program from the start of the program (blocks 650 and 655, FIG. 6 ). In one embodiment, the PVR system may synchronize two buffer positions for simultaneous playback at two clients. For example, a user may desire to playback a music video at two different clients so as to play the music over a broader area of the home.
[0036] In one embodiment, the PVR system assigns states to television tuners. For this embodiment, a television tuner includes one of the following states: busy, maybe free, and totally free. A busy state indicates that the server is currently recording a program using the tuner. The maybe free state indicates that a client may be viewing a program using the tuner. For example, a user may select to view a program at a client. Thereafter, the PVR system does not actually know whether the user is still viewing the program (e.g., as the user may have just turned off their monitor). Under this scenario, the tuner is designated as “maybe free.” If the tuner is designated as “totally free”, then the tuner was not allocated by the scheduler and a client was not viewing programming with the tuner. As described fully below, the tuners states are used to allocate tuners.
[0037] In one embodiment, the PVR system utilizes a scheduler. In general, the scheduler acts as a “to do list” for the system. For example, the scheduler executes a process to record programs selected by system users. The programs may be selected for recording on an individual basis, or the programs may be scheduled for recording based on a subscription. The scheduler resolves issues of conflict management in order to allocate resources to record programs.
[0038] In one embodiment, the PVR system supports “subscriptions.” In general, with a subscription, the system records recurring broadcasts of a selected program. Using a subscription, a user need only select the program for subscription to record all occurrences of that program. In one embodiment, the scheduler of a PVR-media server identifies events to fulfill subscriptions. For example, a user may select a subscription to a television show, “Reality Television.” The scheduler of a PVR-media server determines, from the EPG data set, all unique episodes of the television show, “Reality Television.” The scheduler generates events, one event for each unique episode identified, to record the event. In one embodiment, a subscription is scheduled within a single PVR-media server. However, in other embodiments, subscriptions may be pushed to other PVR-media servers. For example, the scheduler of a first PVR-media server may include events pertaining to a subscription. If the first PVR-media server has conflicts with one or more events of the subscription, then an event of the entire subscription may be assigned to a second PVR-media server. If this occurs, the scheduler of the second PVR-media server fulfills the subscription (e.g., in the same manner as the scheduler for the first PVR-media server). For example, events from the scheduler of the first PVR-media server may be transferred to the scheduler of the second PVR-media server. In addition, the scheduler of the second PVR-media server may assume the task of scheduling future events for the subscription. Also, subscriptions may be pushed between PVR-media servers if a PVR-media server is removed from the network.
[0039] FIG. 7 is a flow diagram illustrating one embodiment for scheduling events in the networked PVR system of the present invention. First, a user selects, through a menu, programs to record, either individually or through a subscription (block 710, FIG. 7 ). In response, the system selects a tuner available during the time slot of the event (block 720, FIG. 7 ). In addition, the system allocates storage space on the storage medium for the scheduled program (block 730, FIG. 7 ). If a “re-schedule” of event occurs in the system, the process is repeated to both allocate available tuners and available storage space (blocks 740, 720 and 730, FIG. 7 ). In one embodiment, a “re-schedule” event occurs when the electronic programming guide data is downloaded to a PVR-media server. A re-schedule event also occurs when a user deletes an item from the scheduler. For example, a user may delete an event to record a program that previously canceled another program from a prior subscription. Under this scenario, the system reschedules the prior subscription because the user canceled the conflicting program.
[0040] When the time to set-up the scheduled event has arrived (e.g., a time prior to the time of the scheduled event), the system initiates the process to commence recording of the scheduled event (blocks 750 and 760, FIG. 7 ). One embodiment for recording a scheduled event, including resolving conflicts of tuner resources, is described fully below in conjunction with a description of FIG. 8 . If the event is canceled, then the system frees a tuner and de-allocates space on the storage medium for the cancelled event (blocks 770 and 775, FIG. 7 ). Also, the scheduler is run to determine any new allocations to fill the slot (block 785, FIG. 7 ). In one embodiment, the system also permits the user to re-schedule, instead of cancel, the event. Alternatively, if the event is not canceled, then the scheduled event is recorded (blocks 770 and 780, FIG. 7 ).
[0041] In one embodiment, the PVR system assigns equal ownership to all clients using a tuner. For example, three clients may be utilizing the same tuner (i.e., all three clients are viewing the same program although potentially, at different portions of the program). If one client changes the channel of the tuner, then the tuner is set to the new the channel, and consequently all three clients are tuned to the new program.
[0042] The PVR system resolves several conflicts that may occur in a networked PVR system (i.e., referred to as “conflict management”). Some conflicts that arise in a networked PVR system include: inadequate storage space to record new programs; an insufficient number of tuners to record scheduled programming; inconsistent input, including requests to change the channel when recording a scheduled event; and an insufficient number of tuners to record events.
[0043] In one embodiment, if a PVR-media server has insufficient storage space to record a scheduled event, then the system automatically deletes content prior to recording. One embodiment to assign priority for content deletion is described more fully below.
[0044] FIG. 8 is a flow diagram illustrating one embodiment for recording programs. Just prior to the time of a scheduled event, the PVR system determines whether a tuner is available (blocks 810 and 820, FIG. 8 ). If a tuner is available (i.e., the tuner is designated as “totally free”), then the tuner is assigned to record the program (blocks 820 and 880, FIG. 8 ). If no tuners are designated “totally free” on the PVR-media server, then the system determines whether there are any other PVR-media servers with tuners (block 822, FIG. 8 ). If so, another PVR-media server is selected, and the system determines whether the selected PVR-media server has an available tuner (blocks 825 and 820, FIG. 8 ). This process is repeated for all PVR-media servers on the network.
[0045] If a tuner is not available (i.e., all tuners on the network are designated as either “busy” or “maybe free”), then the system queries the clients allocated or potentially allocated to the tuners to determine whether the clients desire to cancel the scheduled event (block 830, FIG. 8 ). For example, in one embodiment, to query the clients, the PVR system displays a menu screen on each client asking whether the system should proceed with the scheduled event. All clients allocated to the tuner receive the inquiry. For example, the screen display may ask “System needs to change the channel to record program X at time Y, is this OK?” If all of the client responses are yes to the inquiry, then the system proceeds to record the scheduled event. If a client does not answer the inquiry in a predetermined amount of time, then the system also proceeds to record the scheduled event.
[0046] The PVR system retrieves the responses from the clients (block 840, FIG. 8 ). If any one of the clients cancels the event, then the system determines whether there are additional PVR-media servers with tuners to allocate to record the scheduled event (blocks 850 and 860, FIG. 8 ). If there are no more additional PVR-media servers, then the scheduled event is canceled (blocks 860 and 870, FIG. 8 ). Alternatively, if there are additional PVR-media servers in the system, then the process is repeated to allocate available tuners (blocks 860, 820, 830, 840, and 850, FIG. 8 ). This process to assign tuners is repeated for all PVR-media servers in the system.
[0047] The process of FIG. 8 may be used to allocate tuners for multiple events scheduled at the same time. For example, three programs may be scheduled for recording at an instance in time. The process is repeated for each of the programs. For example, if a client cancels the first scheduled program, then that program is pushed to, if available, another PVR-media server in the system. Then, all the relevant clients receive another inquiry with regard to the scheduling of the second program. Again, if anyone of the clients cancel the second program, the scheduling of the second program is potentially shifted to another PVR-media server.
[0048] In one embodiment, the PVR networked system has the ability for the user to “lock a tuner.” For example, if a user is watching a TV show that spans several hours (e.g. baseball game, academy awards, etc.), then the user may not want to receive multiple requests to change the channel to a previously scheduled event. In one embodiment, the user may select an option in the system to bypass the inquiry to change the channel. When enabled, the system does not display the inquiry to re-allocate the tuner to resolve tuner resource conflicts during the user's program.
[0049] In one embodiment, the networked PVR system includes advanced conflict management. In general, advanced conflict management aids the user to resolve conflicts using means other then querying the user to cancel scheduled events. For example, an advanced conflict manager may automatically seek out alternate presentations of identical television episodes, and present to the user an option for the system to record the program when a conflict does not arise. Thus, if a user attempts to record two shows simultaneously, the system may return a message stating that “The episode of “Your Favorite Show”, set to record at 9 pm on channel 4, is now set to record at 11 pm on channel 7.”
[0050] A user may attempt to change a channel on a tuner currently recording a scheduled event. Under this scenario, the system prompts the user to cancel the scheduled event. Also, a user may attempt to record a program when there are no more available tuners in the system. Under this scenario, the user receives a list, from the entire network, of events to cancel. For example, a system may have three tuners. A first tuner may be recording a first scheduled event, a second tuner may be recording a second scheduled event, and a third tuner may be allocated for use by at least one client. If the user attempts to record another program, the system displays the three programs currently allocated to the three tuners. In response, if the user still wants to record the new program, the user cancels one of the events displayed.
[0051] In one embodiment, the PVR system includes a “deletion manager.” In general, a deletion manager determines the priority to delete content stored in the PVR-media servers. In one embodiment, the deletion manager utilizes a date based deletion system. Under a date based deletion system, the first recorded program is also the first program scheduled for deletion. After a predetermined amount of time, an item is tagged on a menu to inform the user that the program may be deleted. Additional icons may be used to inform the user concerning potential deletion of programs. For example, another icon may be used to inform the user that the item may be deleted, and a different icon may be used to inform the user that the program will not be deleted.
[0052] In one embodiment, the deletion manager uses a priority system based on “sooner” or “later” flags. Under this system, the user marks content for deletion “sooner” or “later.” The deletion manager analyzes content to delete items marked “sooner” before items marked “later.” This system may be used in conjunction with the date based deletion system described above. In another embodiment, the user ranks content for a priority of deletion in accordance with a range (e.g., 1-5).
Client Device Aggregation:
[0053] The networked PVR system utilizes a “peer-to-peer” architecture. All client devices on the media platform have the ability to communicate with other devices, including multiple client devices and multiple PVR-media servers. This architecture permits a device to obtain all media, including television signals, available on the network and to aggregate the media for presentation on that device.
[0054] A device, including a client device or a server device, may enter and/or exit the home network, at any tire, and still maintain full functionality. Thus, when a device is powered off, other devices automatically recognize that the device is no longer available on the home network. When a new device is added or a portable device comes onto the network, the other nodes automatically recognize the new devices. The other nodes may utilize the services on the added device. A new PVR-media server may also automatically recognize new devices, as long as at least one other PVR-media server is currently on the network.
[0055] FIG. 9 illustrates client device aggregation of television signals in accordance with one embodiment of the present invention. For this example, three PVR-media servers (910, 920, and 930) are coupled to home network 940. As shown in FIG. 9 , each PVR-media server has at least one tuner. For example, PVR-media server 930 has three tuners (932, 934 and 936). In addition, the PVR-media servers may store various media items (e.g., video, audio, photos, etc). Also, for this example, client device 950 resides on the home media network 940. Client device 950 may comprise a television.
[0056] After completing a discovery process, client device 950 determines programming available on home network 940. Thus, client device 950 aggregates programming from all tuners for use at client device 950. As shown in FIG. 9 , client device 950 aggregates all programming available through PVR-media servers 910, 920 and 930.
[0057] The networked PYR system provides the capability to identify all programming as unique. For example, all programming classified under the genre “comedy” is recognized as such, and the system displays them accordingly. Two or more actors may have the same name. The networked PVR system utilizes a distributed database that allows the system to distinguish among unique programs. Thus, if a program is offered over two different television service providers, then during client device aggregation, the client device recognizes only a single program. For the example of FIG. 9 , the movie, “Greatest American Movie”, is offered through both PVR-media server 920 and PVR-media server 910. During client programming aggregation, client device 950 recognizes the movie, “Greatest American Movie”, offered through both PVR-media servers 910 and 920, as the same program. Thus, client device 350 only recognizes the movie, “Greatest American Movie”, as a single program.
[0058] The underlying protocols alone do not permit a client device to aggregate programming from devices on the home network. The protocols themselves have no requirement to support a distributed system. For this embodiment of the networked PVR system, aggregation logic creates a distributed system using non-distributed protocols. The aggregation logic uses multiple protocols to integrate devices on the home network.
[0059] FIG. 10 is a flow diagram illustrating one embodiment for client aggregation of programs over a network. Initially, a client device discovers devices (e.g., PVR-media servers) on the home network (block 1010, FIG. 10 ). One embodiment for discovering devices on the home network is described more fully below. Based on information learned in the discovery process, the client device constructs state information for the discovered devices (block 420, FIG. 10 ). The client device receives a request for media items (block 430, FIG. 10 ). The aggregation logic receives requests from software components operating above the aggregation logic. For example, the client device may comprise a television operating a user interface. A user may request, using a remote control device, a list of all television programs, either live or pre-recorded, available on the home network. For this example, application logic on the user interface translates the request for programs, and forwards the request to the aggregation logic.
[0060] The aggregation logic for the client device acquires programming information from all PVR-media servers that provide the selected programs. For example, if the client requests television programs from a specific genre (e.g., comedy), then the client device acquires all programs classified in that genre available from all PVR-media servers. This operation is illustrated in FIG. 10 (blocks 1040, 1050, 1060, 1070 and 1080). Specifically, an identifier (i.e., n=0) to select a specific PVR-media server is set (block 440, FIG. 10 ). The client device connects to a selected PVR-media server (e.g., PVR-media server[0]) using state information acquired during the discovery process (block 1050, FIG. 10 ). Specifically, the client device translates the request for programming to a protocol supported by the selected PVR-media server, and forwards the request to the PVR-media server. In one embodiment, the client device invokes a service on the selected PVR-media server to obtain the programming (block 1060, FIG. 10 ). In one embodiment, the client device invokes a content manager service on the PVR-media server to acquire a list of programs available. If there are more PVR-media servers available on the home network, the client device identifies a new PVR-media server to acquire programming (blocks 1070 and 1080, FIG. 10 ). When the client device has acquired a list of programming from all the available PVR-media servers, the process is complete.
[0061] FIG. 11 is a block diagram illustrating one embodiment for software components operating on a networked PVR system device. Software components 500 include, at the highest level, application software 502. The application software 502 implements functionality for an underlying device. For example, application software 502 may implement functions for a DVD player. As shown in FIG. 11 , underneath the application software 502 is aggregation logic 520. As discussed above, aggregation logic 520 permits a client device to aggregate media items and television programming on the home network.
[0062] The software components 500 also include user interface (“UT”) rendering logic 510. UI rendering component 510 translates scene information to display information suitable for display on the client device. The UI rendering component 510 also renders the display data. For example, if the underlying client device includes a television display (e.g., CRT), then UI rendering engine 510 generates graphics data from scene information, and renders the graphics data on the television display.
[0063] As shown in FIG. 11 , the client device incorporates one or more network protocols and remote procedure calls (“RPC”) mechanisms: For example, FIG. 11 shows that the client device supports network protocolA (1125), network protocolB (1130), and network protocoln (1135). For this example, client device software 500 supports RPC mechanismA (1140), RPC mechanismB (1145), and RPC mechanismn (1150).
[0064] The client device software 500 supports one or more services. As shown in FIG. 11 , one or more methods of a service are accessible through an interface. In general, the methods, when invoked, provide specific functionality for the underlying service. For this example, client device software 500 includes serviceA (555), serviceB (560), and servicen (565). Each service is associated with one or more methods (i.e., method(1)-method(n)).
[0065] In one embodiment, the networked PVR system supports a plurality of underlying protocols. In general, the protocols define commands, RPC mechanisms, and interfaces to services. In one embodiment, the networked PVR system supports an industry defined UPnP protocol. In general, the UPnP protocol defines discovery over IP networks, an RPC mechanism, and interfaces for activating services. UPnP services include: a content directory service, a connection manager service, an audio/video (“A/V”) transport service and an A/V control service.
[0066] In one embodiment, the networked PVR system also supports a proprietary protocol (i.e., non-industry standard protocol). For this embodiment, the proprietary protocol defines a network discovery process, an RPC mechanism, and an interface to services. The services include a content manager, a media player service, and a PVR control interface. The content manager service allows a client device to interface to a database. Specifically, using the content manager service, the client device may extract information (e.g., URL to identify media, metadata, etc.) from a database on another network device. Thus, the content manager service provides a means for a device of the networked PVR system to query a database. The media player service defines an interface to permit playback functionality (e.g., initiate and control media streams). The PVR control interface enables streaming media on a non-stored object. In addition, the PVR control interface permits a user to record current programming as well as schedule recording of future programming.
[0067] In one embodiment, the discovery process on the proprietary protocol implements asynchronous based messaging. The discovery protocol operates on any network that supports packet based messaging or on a serialized network. In one embodiment, the discovery protocol includes an “announce” command, a “discovery” command, and a “bye-bye” command. The announce command is used by a device to announce its presence on the home media network. A discovery command is a request for an announcement (i.e., queries whether any client devices are on the home network). The “bye-bye” command is used by a client device to announce that the client device is leaving the network. In one embodiment, there are two types of announcements and two types of “bye-bye” commands: one for devices and one for services.
[0068] In one embodiment, the RPC mechanism, supported by the proprietary protocol, uses a packet-based protocol. The services include methods and an identification number to permit a device on the home network to construct RPC based packets with the appropriate arguments. In general, an RPC mechanism permits a device to control another device on the network. The protocol is effectuated through requests and responses. The RPC packets include a header. In one embodiment, the header contains: version information, a command class (maps to a particular service), the command (the method the device is requesting or the response coming from the method), an identification (identification of requests or identification of responses corresponding to a request), and a length. After the header, the RPC protocol format specifies data (i.e., arguments for requests and returns values for responses).
[0069] FIG. 12 is a block diagram illustrating an example home network for the networked PVR system. For this example, a home network includes PVR-media server 1250, DVD player 1240, and PVR-media server 1230. A client device (1210), which includes a television, enters the home network 620, and discovers, using a supporting protocol, three devices (e.g., PVR-media server 1250, DVD player 1240, and PVR-media server 1230). As shown in FIG. 12 , client device 1210 stores state information for each of the devices discovered on home network 1220. Specifically, client device 1210 stores, for device1 (PVR-media server 1230) a supporting network protocol (i.e., network protocolA) as well as a list of services supported by the devices (i.e., serviceA and serviceC). The network protocol also specifies an RPC mechanism to execute remote procedure calls on PVR-media server 1230. Similarly, state information for device2 (i.e., DVD player 1240) indicates that device2 supports network protocolA and implements serviceA and serviceB. Device3, PVR-media server 1250, supports network protocolC, and implements serviceA and serviceB.
[0070] As shown in FIG. 12 , each service (e.g., serviceA, serviceB, and serviceC) supports an interface. The interface defines a specification to provide a means to access the methods or commands within a service. As such, the client device 1210 utilizes services (serviceA or serviceB) on PVR-media server 1250 through their respective interfaces. Note that PVR-media server 1230, DVD player 1240 and PVR-server 1250 all implement serviceA. Each interface for serviceA is the same to permit uniform accessibility to the service. However, the implementation of serviceA in each of the devices may be different.
[0071] In one embodiment, a networked PVR system implementation provides security. For this embodiment, the announcement command is open ended, such that the protocol only defines a minimum specification for communication. Thus, announcement protocols may support multiple network specifications, including TCP and secure sockets layer (“SSL”). The protocol supports implementation on TCP/IP networks. In addition, the protocol supports SSL operating on TCP/IP networks. SSL permits secure communications, including authentication, between two parties on a network.
[0072] The proprietary protocol also permits an implementation using partial security. For this embodiment, a service may include some methods that require secure communications and other methods that do not require secure communications. Thus, some methods utilize SSL technology to realize secure communications between two devices on the home network.
Discovery:
[0073] FIG. 13 is a flow diagram illustrating one embodiment for discovering devices in the networked PVR system. A new device (i.e., a device not currently connected to the network) is connected to the home media network (block 1310, FIG. 13 ). In order to communicate on the network, the new device obtains a network address (block 1320, FIG. 13 ). For example, in an IP network, the client requires an IP address. If the underlying network supports TCP/IP, then the client device determines if there is a DHCP server. If so, the DHCP server assigns the IP address to the new device. If not (i.e., the DHCP server is not available to assign the new device an IP address), then the new device selects an IP address from a pool and determines whether any other device on the home network has that IP address. If no other device on the network has that IP address, then the client device uses this IP address. This process of auto IP addressing allows communication on a home network within a single subnet.
[0074] The new device transmits an “announcement” command over the network (block 1330, FIG. 13 ). The format of the announcement command complies with a protocol supported by the devices. The new device may broadcast or multicast the announcement command over the network. For example, in an IP network, the new device may multicast the announcement in order to expand subnets if the home network includes a gateway. A multicast format is used to specify specific IP addresses (e.g., transmitting an announcement only to those devices on the network interested or compatible with the new device). As used herein, compatible devices are those devices that may be interested in communicating with the client device.
[0075] In response to the new device's announcement command, the new device constructs state information. In general, the state information provides details regarding devices available on the network. The state information includes protocols and services supported by those devices. When compatible devices on the network receive the announcement command, those compatible devices may add information, encapsulated in the announcement command, to a local cache.
[0076] If there are no compatible devices on the network or the new device does not desire to utilize a service on the network, then the process terminates. For example, if the new device is a television, then compatible devices include those PVR-media servers storing video (e.g., DVD, MPEG, etc.) as well as providing live or pre-recorded television. If there are other compatible devices on the network, those devices expose one or more services to the new device (block 1350, FIG. 13 ). To discovery services on the network, the new device transmits a discovery command and waits for a response. For this example, a PVR-media server, which provides live television, exposes an interface to allow the new device to aggregate programming provided by the PVR-media server (e.g., programming provided by a television service provider).
[0077] In response to the request (e.g., new device application logic), the new device connects to a compatible device via a supporting protocol (block 760, FIG. 13 ). Specifically, the device translates the protocol for the appropriate device using the state information. For example, if the compatible device supports an industry standard protocol, then the new device selects the industry standard protocol to communicate to that device. The new device utilizes the services on the compatible device (block 1370, FIG. 13 ).
[0078] A PVR-media server entering a home network is one example of the discovery process. For this example, the PVR-media server, after obtaining a network address, transmits an announcement command over the network. The PVR-media server announces the services it supports (e.g., content manager, media player service and PVR control interface), and exposes interfaces to network clients to permit access to those services. If a device enters the network, the device waits for an announcement from the server. When the client identifies the PVR-media server, the client connects to the PVR-media server via a protocol the server specified in the announcement command. This process allows the client device to navigate media and programming on the PVR-media server. Using the supporting protocol, the client device connects to a playback device (e.g., television), either itself or another playback device, and instructs the playback device to play the program that a user selected from programming available on the PVR-media server.
Networked PVR Data Model:
[0079] The networked PVR system operates in conjunction with a data model. The format and arrangement of underlying database is not defined by the networked PVR system. In the data model, objects (e.g., media items) have unique identifications in the database. The objects also have an associated “type” (e.g., channels, time slots, episodes, and shows). The data model defines relationships to define structure and hierarchy among objects and types.
[0080] FIG. 14 is a block diagram illustrating one embodiment for a data model for elements of a networked PVR system. For this embodiment, many service providers are mapped to a single MSO package. In general, the MSO package defines data (e.g., time, channel, content, etc.) for television programming. Data is extracted to map the MSO package to channels. The channels data object defines all channels available. As shown in FIG. 14 , each channel maps to multiple time slots. An episode data object is mapped to one or more time slots. The episode data object identifies each individual episode of a program. In turn, the episode data object maps to one or more episodes to a show. An actors data object is mapped to each episode to identify actors. Also, a genres data object is used to classify shows in genres (e.g., comedy, drama, action, sports, etc.).
[0081] In one embodiment, the database for the networked PVR system comprises a relational database (e.g., key value pair database or standard query language (“SQL”) database). For this embodiment, the database maps objects for storage in the relational database. Although one embodiment of the networked PVR system utilizes a relational database, other databases may be used without deviating from the spirit or scope of the invention.
[0082] FIG. 15 is a block diagram illustrating one embodiment of accessing a data store in the networked PVR system. A client device 1510 is connected to a home network 1520. As shown in FIG. 15 , device 1530 and device 1540 are also coupled to home network 1520. Device 1540 includes a persistent data store, labeled Database B in FIG. 15 . Similarly, device 1530 includes a persistent data store, Database A. Device 1530 and 1540 support a service that permits access to information in the persistent data stores. In one embodiment, the content manager service is used. Specifically, a first implementation of the content manager serviceA supports access to Database A, and a second implementation of the content manager serviceB supports access to Database B.
[0083] Client device 1510 may obtain information from Database A and Database B. To query Database B, client device 1510 obtains a connection with device 1540 in a manner as described above. The client device 1510 invokes methods via an interface on content manager serviceB. For example, client device 1510 may desire to obtain a list of all genres recognized by the networked PVR system. This information may be stored in database B. Client device 1510 generates a request using data model parameters specified in the interface for content manager serviceB. For the example above, client device 1510 generates a request to content manager serviceB to identify all objects with the type “genre.” In response to the request, client manager serviceB translates the data model notion of “genre” to a query compatible with Database B. For example, if Database B supports SQL, then content manager serviceB generates a SQL request to Database B to obtain all records in a table with the type “genre.”
[0084] The implementation of the content manager service performs the translation from the networked PVR system data model to an underlying database implementation. For the example in FIG. 15 , the content manager serviceA supports a first translation to Database A, and the content manager serviceB supports a second translation for requests for data stored in Database B. Accordingly, client device 1510 uses the same request, as defined by the interface on both content manager services, to access different database implementations (e.g., Database A and Database B).
[0085] In one embodiment, the networked PVR system is implemented using a database. In general, the database stores objects, attributes associated with those objects, and associations between those objects. For example, the database stores an identification of television programs available within the media space. The database stores a plurality of attributes, so as to associate one or more attributes for each object. In one embodiment, the objects include. Thus, a track may be associated with one or more albums, one or more artists, one or more genres, and one or more playlists. Attributes include titles, creation dates, and multiple associated media files. Thus, a track may have associated album art, lyrics, etc.
[0086] The networked PVR system database permits classifying audio tracks in an extremely versatile manner. For example, a user may desire to classify a track or album (i.e., collection of tracks) in more than one genre because the user associates the music with two different types of genres (e.g., rock and blues). Also, a musical track may be a result of a collaboration between two artists. To properly classify the track, a user of the networked PVR system may associate the track with two different artists. As illustrated by the above examples, the networked PVR system provides m1imum flexibility in classifying and organizing music.
[0087] The networked PVR system handles each classification or item as a distinct object. For example, for the music jukeb13 application, playlists, genres, artists, albums, and tracks are all handled as individual objects. This feature, which supports independent objects for organization and classification of items, provides m1imum flexibility in organizing and classifying music. For example, the user may create nested playlists, such that a first playlist may be wholly contained within a second playlist. Prior art music systems only deal with playlists by tracks. For these prior art systems, a playlist only consists of tracks. In the networked PVR system, playlists may comprise any “objects.” Therefore, playlists may be created from one or more artists, genres, albums or other playlists.
[0088] The use of objects in organizing and playing music also permits artists with the same name to be treated differently. Prior art digital music systems store metadata to identify artists. If a user executes a search on the metadata using these prior art systems, there is no way for the system to differentiate among artists with the same name. In the networked PVR system, each artist is treated as an object. Thus, two artists with the same name are two distinct objects, and may be manipulated as two separate artists.
[0089] The networked PVR system utilizes distributed iterators. A response to a query to a database may generate a huge amount of data. In one embodiment, the networked PVR system protocol supports transmitting a portion of the data, and maintaining a pointer to identify the data that has been sent. In one embodiment, the protocol uses iterators. The use of iterators by the networked PVR system allows the system to track a portion of data (e.g., a list) transferred from one device to another device. The iterator is implemented such that the iterator dynamically changes if items in the database change during transfer of the data. In general, the iterator specifies a position in an array. A list is a result from the database. For example, the response to a query to a database may produce a list of audio tracks. Subsequently, an audio track, extracted as part of the example query, may be deleted. In another scenario, an audio track, specified by the query, may be added to the database.
[0090] If the networked PVR system is implemented using the proprietary protocol and a TCP/IP network, the system associates state with the request for database information. This state information is utilized to maintain iterator information.
[0091] Although the present invention has been described in terms of specific exemplary embodiments, it will be appreciated that various modifications and alterations might be made by those skilled in the art without departing from the spirit and scope of the invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method for networking a plurality of clients in a personal video recording (“PVR”) system, said method comprising the steps of:
receiving a plurality of television signals;
tuning each of said television signals in one of a plurality of tuners;
buffering said television signals on a storage medium in a PVR media server, wherein the buffered television signals are accessible from the storage medium based on a plurality of independent read taps, and wherein a plurality of clients are coupled, over a network, to said PVR media server;
receiving a request from each of at least two clients for a service in said PVR system;
allocating resources of said PVR system to said clients, as appropriate, to deliver said service to each of said clients, wherein:
resources of the PVR system comprise the plurality of tuners and the plurality of independent read taps,
the different clients may share said service to manipulate live television signals using the independent read taps while the live television signals are being recorded, and
each client is configured to modify a position, identifying a storage location within the storage medium, of a respective one of the plurality of independent read taps;
designating one of at least three states to a first tuner of the plurality of tuners based on allocation of the first tuner and usage of the plurality of clients, the at least three states comprising at least: a busy state, a maybe free state, and a totally free state;
storing, in a memory, the designated state for the first tuner prior to a scheduled event based on said allocating;
detecting a conflict for the first tuner among the requesting clients;
resolving the conflict among the requesting clients based on the designated state of the first tuner stored in the memory, and the availability of the resources of the PVR system comprising the tuners and the plurality of independent read taps; and
when a new PVR media server, not previously connected to the network, is coupled to the network, transmitting information identifying a service available from the new PVR media server over the network to the plurality of clients.
2. The method as set forth in claim 1, wherein:
the step of receiving the request comprises receiving a request to record a television program; and
the step of allocating resources of said PVR system to said clients comprises:
assigning a tuner to record said television program;
allocating space on said storage medium to record said television program; and
storing said television signal on said storage medium during a time scheduled for said television program.
3. The method as set forth in claim 1, wherein: the step of receiving the request comprises receiving a request to watch buffered live television; and
the step of allocating resources of said PVR system comprises:
assigning a tuner to said client;
generating a buffer position to identify a location within said television signal for playback of said television signal at a client; and
transferring said television signal to said client, so as to deliver said television signal using said buffer position.
4. The method as set forth in claim 1, wherein:
the step of receiving the request comprises receiving a request to receive television signals from a specific television service provider; and
the step of allocating resources of said PVR system comprises:
identifying one or more tuners coupled to receive television signals from said television service provider; and
assigning a tuner from said tuners to receive television signals from said television service provider.
5. The method as set forth in claim 1, wherein the step of allocating resources of said PVR system to said clients comprises the step of resolving any conflicts of assigning resources to said clients.
6. The method as set forth in claim 5, wherein:
the step of receiving the request comprises receiving a request to watch buffered live television at a channel selected; and
the step of resolving any conflicts of assigning resources comprises:
determining whether one of said tuners is available to receive said television signal;
if so, assigning said tuner to receive said television signal at said channel selected;
if not, determining which tuners are potentially available;
querying clients assigned to said tuners potentially available to determine whether said clients desire to change a current channel of said tuner to said channel selected; and
assigning a tuner potentially available to receive a television signal at said channel selected if no clients cancel a change of said current channel.
7. The method as set forth in claim 5, wherein:
the step of receiving the request comprises receiving a request to record a television program; and
the step of resolving any conflicts of assigning resources comprises:
determining whether one of said tuners is available to receive said television signal;
if so, assigning said tuner to receive said television signal;
if not, determining which tuners are potentially available;
querying clients assigned to said tuners potentially available to determine whether said clients desire to cancel recordation of said television program; and
assigning a tuner potentially available to receive said television signal if no clients cancel recordation of said television program.
8. The method as set forth in claim 5, further comprising the steps of:
designating a totally free tuner state to a tuner not assigned to a client;
designating a maybe free tuner state to a tuner assigned to a client but not currently executing a scheduled recordation; and
designating a busy tuner state to a tuner currently executing a scheduled recordation.
9. A personal video recording (“PVR”) media server comprising:
an input for receiving a plurality of television signals;
a plurality of tuners for tuning each of said television signals;
a storage medium for buffering said television signals, wherein the buffered television signals are accessible based on a plurality of independent read taps;
a network interface for coupling a plurality of clients, over a network, to said PVR media server; and
said PVR media server for receiving a request from each of at least two clients for a service in a PVR system, and for allocating resources of said PVR system to said two clients, as appropriate, to deliver said service to each of said clients, wherein:
resources of the PVR system comprise the plurality of tuners and the plurality of independent read taps,
the different clients may share a service to manipulate live television signals using the independent read taps while the live television signals are being recorded, and
each client is configured to modify a position, identifying a storage location within the storage medium, of a respective one of the plurality of independent read taps;
the PVR server configured to designate one of at least three states to a first tuner of the plurality of tuners based on allocation of the first tuner and usage of the plurality of clients, the at least three states comprising at least:
a busy state, a maybe free state, and a totally free state,
a memory for storing the designated state for the first tuner based on said allocating, the storing prior to a scheduled event:
the PVR server further for:
detecting a conflict for the first tuner among the requesting clients; and
resolving the conflict among the requesting clients based on the designated state of the first tuner stored in the memory and the availability of the resources of the PVR system comprising the tuners and the plurality of independent read taps,
wherein, when a new PVR media server, not previously on the network, is coupled to the network, transmitting information identifying a service available from the new PVR media server over the network to the plurality of clients.
10. The PVR media server as set forth in claim 9, wherein:
said input further for receiving a request to record a television program; and
said PVR media server further for assigning a tuner to record said television program, for allocating space on said storage medium to record said television program, and for storing said television signal on said storage medium during a time scheduled for said television program.
11. The PVR media server as set forth in claim 9, wherein:
said input further for receiving a request to watch buffered live television; and
said PVR media server further for assigning a tuner to watch said buffered live television, for generating a buffer position to identify a location within said television signal for playback of said television signal at a client, and for transferring said television to said client, so as to deliver said television signal using said buffer position.
12. The PVR media server as set forth in claim 9, wherein:
said input further for receiving the request comprises receiving a request to receive television signals from a specific television service provider; and
said PVR media server further for identifying one or more tuners coupled to receive television signals from said television service provider, and for assigning a tuner from said tuners identified to said client.
13. The PVR media server as set forth in claim 9, said PVR media server further for resolving any conflicts of assigning resources to said clients.
14. The PVR media server as set forth in claim 13, wherein:
said input further for receiving a request to watch buffered live television at a channel selected; and
said PVR media server further for determining whether one of said tuners is available to receive said television signal;
if so, for assigning said tuner to receive said television signal at said channel selected;
if not, for determining which tuners are potentially available, for querying clients assigned to said tuners potentially available to determine whether said clients desire to change a current channel of said tuner to said channel selected, and for assigning a tuner potentially available to receive a television signal at said channel selected if no clients cancel a change of said current channel.
15. The PVR media server as set forth in claim 13, wherein:
said input further for receiving a request to record a television program; and
said PVR media server further for determining whether one of said tuners is available to receive said television signal;
if so, for assigning said tuner to receive said television signal;
if not, for determining which tuners are potentially available, for querying clients assigned to said tuners potentially available to determine whether said clients desire to cancel recordation of said television program, and for assigning a tuner potentially available to receive said television signal if no clients cancel recordation of said television program.
16. The PVR media server as set forth in claim 13, said PVR media server further
for designating a totally free tuner state to a tuner not assigned to a client,
for designating a maybe free tuner state to a tuner assigned to a client but not currently executing a scheduled recordation, and
for designating a busy tuner state to a tuner currently executing a scheduled recordation.
17. A personal video recording (“PVR”) system comprising:
a PVR media server comprising:
an input for receiving a plurality of television signals;
a plurality of tuners for tuning each of said television signals;
a storage medium for buffering said television signals, wherein the buffered television signals are accessible based on a plurality of independent read taps;
a network; and
a plurality of clients, coupled over said network to said PVR media server, for receiving a request from each of at least two clients for a service in said PVR system, and for allocating resources of said PVR system to said clients, as appropriate, to deliver said service to each of said clients, wherein:
resources of the PVR system comprise the plurality of tuners and the plurality of independent read taps,
the different clients may share said service to manipulate live television signals using the independent read taps while the live television signals are being recorded, and
each client is configured to modify a position, identifying a storage location within the storage medium, of a respective one of the plurality of independent read taps;
the PVR system configured to designate one of at least three states to a first tuner of the plurality of tuners based on allocation of the first tuner and usage of the plurality of clients, the at least three states comprising at least: a busy state, a maybe free state, and a totally free state,
a memory for storing the designated state for the first tuner based on said allocating, the storing prior to a scheduled event;
the PVR server further for
detecting a conflict for the first tuner among the requesting clients; and
resolving the conflict among the requesting clients based on the designated state of the first tuner stored in the memory and the availability of the resources of the PVR system comprising the tuners and the plurality of independent read taps,
wherein, when a new PVR media server, not previously on the network, is coupled to the network, transmitting information identifying a service available from the new PVR media server over the network to the plurality of clients.
18. The system of claim 17, further configured for resolving conflicts of assigning resources to the clients,
the busy state for indicating that the server is currently receiving a program by using the first tuner;
the maybe free state for indicating a probability that a client is viewing a program by using the first tuner, wherein when a tuner is designated as in the maybe free state a user selects to view a program at a client and the PVR system is missing information as to whether the user is still viewing the program; and
the totally free state for indicating when a tuner is not allocated by a scheduler and a client is not viewing programming by using the tuner; wherein:
the input is further for receiving one or more of:
a request to watch buffered live television at a channel selected, and
a request to record a television program;
the PVR media server is further for determining whether one of the tuners is available to receive the television signal;
if so, for assigning a first tuner to receive the television signal at the channel selected;
if not, for determining which tuners are potentially available, for querying clients assigned to the tuners potentially available to determine whether the clients desire to change a current channel of the tuner to the channel selected, and for assigning a tuner potentially available to receive a television signal at the channel selected if no clients cancel a change of the current channel and if no clients cancel recordation of the television program.
19. The system of claim 17, further comprising a new device coupled to the network, and a set of compatible devices on the network include one or more PVR-media servers configured for storing pre-recorded video and for providing live television,
wherein to discover services on the network, the new device transmits a discovery command and waits for a response,
wherein a first PVR-media server on the network exposes an interface to allow the new device to aggregate programming provided by the PVR-media server in response to the request, the new device connects to a compatible device via a supporting protocol, and the compatible device translates the protocol for the appropriate device using state information.
20. The system of claim 19, wherein the new device comprises a television, and the compatible device supports an industry standard protocol, wherein the industry standard protocol is selected to communicate to the compatible device and to use the services provided by the compatible device.
21. The system of claim 17, wherein the PVR system is further configured for discovering devices in the networked PVR system, wherein when a new device not currently connected to the network is connected to the network, in order to communicate on the network, the new device obtains a network address,
the system further comprising a home media network, and a plurality of devices having network addresses, wherein if the underlying network supports TCP/IP, then the new device determines if there is an available DHCP server;
if so, the DHCP server assigns the network address to the new device;
if a DHCP server is not available to assign the new device a network address, then the new device selects a network address from a pool and determines whether any other device on the network has the selected network address, wherein if no other device on the network has the selected network address, then the new device uses the selected network address, wherein the network addressing allows communication on the network within a single subnet;
wherein the new device transmits an announcement command over the network, the format of the announcement command complies with a supported protocol, wherein the new device broadcasts or multicasts the announcement command over the network, the multicast of the announcement command is for expanding subnets if the network includes a gateway, wherein a multicast format is used to specify specific network addresses transmitting an announcement only to those devices on the network interested or compatible with the new device, wherein compatible devices are those devices that are interested in communicating with the new device, wherein a compatible device on the network exposes one or more services to the new device;
wherein in response to the new device's announcement command, the new device constructs state information that provides details regarding devices available on the network, the state information comprising protocols and services supported by the networked devices, such that when compatible devices on the network receive the announcement command, the compatible devices add information encapsulated in the announcement command, to a local cache.
22. The method of claim 1, wherein the storage medium further comprises a plurality of buffers, and wherein:
one of the plurality of buffers is coupled to one of the plurality of tuners and includes the plurality of independent read taps;
the respective position of each of the plurality of independent read taps corresponds to a location in the one of the plurality of buffers; and
each respective one of the plurality of independent read taps corresponds to a respective one of the plurality of clients.
23. The method of claim 22, wherein each client is further configured to:
identify the position, identifying the storage location within the storage medium, of the respective one of the plurality of independent read taps; and
modify the position of the respective one the plurality of independent read taps by modifying the corresponding location in the one of the plurality of buffers.
24. The PVR media server of claim 9, wherein the storage medium further comprises a plurality of buffers, and wherein:
one of the plurality of buffers is coupled to one of the plurality of tuners and includes the plurality of independent read taps;
the respective position of each of the plurality of independent read taps corresponds to a location in the one of the plurality of buffers; and
each respective one of the plurality of independent read taps corresponds to a respective one of the plurality of clients.
25. The PVR media server of claim 24, wherein each client is further configured to:
identify the position, identifying the storage location within the storage medium, of the respective one of the plurality of independent read taps; and
modify the position of the respective one the plurality of independent read taps by modifying the corresponding location in the one of the plurality of buffers.
26. The system of claim 17, wherein the storage medium further comprises a plurality of buffers, and wherein:
one of the plurality of buffers is coupled to one of the plurality of tuners and includes the plurality of independent read taps;
the respective position of each of the plurality of independent read taps corresponds to a location in the one of the plurality of buffers; and
each respective one of the plurality of independent read taps corresponds to a respective one of the plurality of clients.
27. The system of claim 26, wherein each client is further configured to:
identify the position, identifying the storage location within the storage medium, of the respective one of the plurality of independent read taps; and
modify the position of the respective one the plurality of independent read taps by modifying the corresponding location in the one of the plurality of buffers.
Patent Citations (573)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4063220(A) | 1977-12-01 | Metcalfe et al. | Applicant |
| US4079419(A) | 1978-03-01 | Siegle et al. | Applicant |
| US4081754(A) | 1978-03-01 | Jackson | Applicant |
| US4193120(A) | 1980-03-01 | Yello | Applicant |
| US4206483(A) | 1980-06-01 | Nakamura | Applicant |
| US4264924(A) | 1981-04-01 | Freeman | Applicant |
| US4264925(A) | 1981-04-01 | Freeman et al. | Applicant |
| US4267563(A) | 1981-05-01 | Sato et al. | Applicant |
| US4305101(A) | 1981-12-01 | Yarbrough | Applicant |
| US4310924(A) | 1982-01-01 | Miyasaka et al. | Applicant |
| US4325081(A) | 1982-04-01 | Abe et al. | Applicant |
| US4334242(A) | 1982-06-01 | Marigold | Applicant |
| US4355415(A) | 1982-10-01 | George et al. | Applicant |
| US4390901(A) | 1983-06-01 | Keiser | Applicant |
| US4429385(A) | 1984-01-01 | Cichelli et al. | Applicant |
| US4435842(A) | 1984-03-01 | Mayumi et al. | Applicant |
| US4449249(A) | 1984-05-01 | Price | Applicant |
| US4475153(A) | 1984-10-01 | Kihara et al. | Applicant |
| US4488179(A) | 1984-12-01 | Kruger et al. | Applicant |
| US4519003(A) | 1985-05-01 | Scholz | Applicant |
| US4573072(A) | 1986-02-01 | Freeman | Applicant |
| US4593414(A) | 1986-06-01 | Koyanagi | Applicant |
| US4598288(A) | 1986-07-01 | Yarbrough et al. | Applicant |
| US4602279(A) | 1986-07-01 | Freeman | Applicant |
| US4605964(A) | 1986-08-01 | Chard | Applicant |
| US4605973(A) | 1986-08-01 | Von Kohorn | Applicant |
| US4621259(A) | 1986-11-01 | Schepers et al. | Applicant |
| US4625080(A) | 1986-11-01 | Scott | Applicant |
| US4631601(A) | 1986-12-01 | Brugliera et al. | Applicant |
| US4635121(A) | 1987-01-01 | Hoffman et al. | Applicant |
| US4641205(A) | 1987-02-01 | Beyers, Jr. | Applicant |
| US4694490(A) | 1987-09-01 | Harvey et al. | Applicant |
| US4706121(A) | 1987-11-01 | Young | Applicant |
| US4718107(A) | 1988-01-01 | Hayes | Applicant |
| US4751578(A) | 1988-06-01 | Reiter et al. | Applicant |
| US4755883(A) | 1988-07-01 | Uehira | Applicant |
| US4832373(A) | 1989-05-01 | Swan | Applicant |
| US4843482(A) | 1989-06-01 | Hegendorfer | Applicant |
| US4847698(A) | 1989-07-01 | Freeman | Applicant |
| US4847700(A) | 1989-07-01 | Freeman | Applicant |
| US4857999(A) | 1989-08-01 | Welsh | Applicant |
| US4879611(A) | 1989-11-01 | Fukui et al. | Applicant |
| US4885579(A) | 1989-12-01 | Sandbank | Applicant |
| US4899370(A) | 1990-02-01 | Kameo et al. | Applicant |
| US4908707(A) | 1990-03-01 | Kinghorn | Applicant |
| US4908713(A) | 1990-03-01 | Levine | Applicant |
| US4930158(A) | 1990-05-01 | Vogel | Applicant |
| US4945563(A) | 1990-07-01 | Horton et al. | Applicant |
| US4959720(A) | 1990-09-01 | Duffield et al. | Applicant |
| US4977455(A) | 1990-12-01 | Young | Applicant |
| US5036314(A) | 1991-07-01 | Barillari et al. | Applicant |
| US5038211(A) | 1991-08-01 | Hallenbeck | Applicant |
| US5047867(A) | 1991-09-01 | Strubbe et al. | Applicant |
| US5068733(A) | 1991-11-01 | Bennett | Applicant |
| US5105184(A) | 1992-04-01 | Pirani et al. | Applicant |
| US5109279(A) | 1992-04-01 | Ando | Applicant |
| US5134719(A) | 1992-07-01 | Mankovitz | Applicant |
| US5151789(A) | 1992-09-01 | Young | Applicant |
| US5155591(A) | 1992-10-01 | Wachob | Applicant |
| US5172413(A) | 1992-12-01 | Bradley et al. | Applicant |
| US5187589(A) | 1993-02-01 | Kono et al. | Applicant |
| US5195134(A) | 1993-03-01 | Inoue | Applicant |
| US5200822(A) | 1993-04-01 | Bronfin et al. | Applicant |
| US5210611(A) | 1993-05-01 | Yee et al. | Applicant |
| US5223924(A) | 1993-06-01 | Strubbe | Applicant |
| USRE34340(E) | 1993-08-01 | Freeman | Applicant |
| US5233423(A) | 1993-08-01 | Jernigan et al. | Applicant |
| US5241428(A) | 1993-08-01 | Goldwasser et al. | Applicant |
| US5253066(A) | 1993-10-01 | Vogel | Applicant |
| US5285284(A) | 1994-02-01 | Takashirna et al. | Applicant |
| US5296931(A) | 1994-03-01 | Na | Applicant |
| US5323234(A) | 1994-06-01 | Kawasaki | Applicant |
| US5325183(A) | 1994-06-01 | Rhee | Applicant |
| US5335277(A) | 1994-08-01 | Harvey et al. | Applicant |
| US5353121(A) | 1994-10-01 | Young et al. | Applicant |
| US5371551(A) | 1994-12-01 | Logan et al. | Applicant |
| US5398074(A) | 1995-03-01 | Duffield et al. | Applicant |
| US5410344(A) | 1995-04-01 | Graves et al. | Applicant |
| US5412720(A) | 1995-05-01 | Hoarty | Applicant |
| US5414455(A) | 1995-05-01 | Hooper et al. | Applicant |
| US5416508(A) | 1995-05-01 | Sakuma et al. | Applicant |
| US5432561(A) | 1995-07-01 | Strubbe | Applicant |
| US5434626(A) | 1995-07-01 | Hayashi et al. | Applicant |
| US5440678(A) | 1995-08-01 | Eisen et al. | Applicant |
| US5442389(A) | 1995-08-01 | Blahut et al. | Applicant |
| US5452012(A) | 1995-09-01 | Saitoh | Applicant |
| US5459522(A) | 1995-10-01 | Pint | Applicant |
| US5461415(A) | 1995-10-01 | Wolf et al. | Applicant |
| US5469206(A) | 1995-11-01 | Strubbe et al. | Applicant |
| US5479266(A) | 1995-12-01 | Young et al. | Applicant |
| US5479268(A) | 1995-12-01 | Young et al. | Applicant |
| US5479302(A) | 1995-12-01 | Haines | Applicant |
| US5479497(A) | 1995-12-01 | Kovarik | Applicant |
| US5483278(A) | 1996-01-01 | Strubbe et al. | Applicant |
| US5485197(A) | 1996-01-01 | Hoarty | Applicant |
| US5485219(A) | 1996-01-01 | Woo | Applicant |
| US5488409(A) | 1996-01-01 | Yuen et al. | Applicant |
| US5517254(A) | 1996-05-01 | Monta et al. | Applicant |
| US5517257(A) | 1996-05-01 | Dunn et al. | Applicant |
| US5523794(A) | 1996-06-01 | Mankovitz et al. | Applicant |
| US5523796(A) | 1996-06-01 | Marshall et al. | Applicant |
| US5524195(A) | 1996-06-01 | Clanton, III et al. | Applicant |
| US5528304(A) | 1996-06-01 | Cherrick et al. | Applicant |
| US5532754(A) | 1996-07-01 | Young et al. | Applicant |
| US5534911(A) | 1996-07-01 | Levitan | Applicant |
| US5537141(A) | 1996-07-01 | Harper et al. | Applicant |
| US5539449(A) | 1996-07-01 | Blahut et al. | Applicant |
| US5539822(A) | 1996-07-01 | Lett | Applicant |
| US5541662(A) | 1996-07-01 | Adams et al. | Applicant |
| US5541738(A) | 1996-07-01 | Mankovitz | Applicant |
| US5543852(A) | 1996-08-01 | Yuen et al. | Applicant |
| US5543929(A) | 1996-08-01 | Mankovitz | Applicant |
| US5550576(A) | 1996-08-01 | Klosterman | Applicant |
| US5557338(A) | 1996-09-01 | Maze et al. | Applicant |
| US5559548(A) | 1996-09-01 | Davis et al. | Applicant |
| US5559549(A) | 1996-09-01 | Hendricks et al. | Applicant |
| US5559550(A) | 1996-09-01 | Mankovitz | Applicant |
| US5568272(A) | 1996-10-01 | Levine | Applicant |
| US5581614(A) | 1996-12-01 | Ng et al. | Applicant |
| US5583560(A) | 1996-12-01 | Florin et al. | Applicant |
| US5583561(A) | 1996-12-01 | Baker et al. | Applicant |
| US5583563(A) | 1996-12-01 | Wanderscheid et al. | Applicant |
| US5583653(A) | 1996-12-01 | Timmernians | Applicant |
| US5585838(A) | 1996-12-01 | Lawler et al. | Applicant |
| US5585858(A) | 1996-12-01 | Harper et al. | Applicant |
| US5585866(A) | 1996-12-01 | Miller et al. | Applicant |
| US5589892(A) | 1996-12-01 | Knee et al. | Applicant |
| US5592551(A) | 1997-01-01 | Lett et al. | Applicant |
| US5592571(A) | 1997-01-01 | Peters et al. | Applicant |
| US5594509(A) | 1997-01-01 | Florin et al. | Applicant |
| US5600364(A) | 1997-02-01 | Hendricks et al. | Applicant |
| US5602582(A) | 1997-02-01 | Wanderscheid et al. | Applicant |
| US5606374(A) | 1997-02-01 | Bertram | Applicant |
| US5617565(A) | 1997-04-01 | Augenbraun et al. | Applicant |
| US5619274(A) | 1997-04-01 | Roop et al. | Applicant |
| US5621456(A) | 1997-04-01 | Florin et al. | Applicant |
| US5621579(A) | 1997-04-01 | Yuen | Applicant |
| US5629733(A) | 1997-05-01 | Youman et al. | Applicant |
| US5630067(A) | 1997-05-01 | Kindell et al. | Applicant |
| US5630119(A) | 1997-05-01 | Aristides et al. | Applicant |
| US5631995(A) | 1997-05-01 | Weissensteiner et al. | Applicant |
| US5632007(A) | 1997-05-01 | Freeman | Applicant |
| US5635978(A) | 1997-06-01 | Alten et al. | Applicant |
| US5635989(A) | 1997-06-01 | Rothmuller | Applicant |
| US5648824(A) | 1997-07-01 | Dunn et al. | Applicant |
| US5650826(A) | 1997-07-01 | Eitz | Applicant |
| US5650831(A) | 1997-07-01 | Farwell | Applicant |
| US5652613(A) | 1997-07-01 | Lazarus et al. | Applicant |
| US5652615(A) | 1997-07-01 | Bryant et al. | Applicant |
| US5654748(A) | 1997-08-01 | Matthews, III | Applicant |
| US5654886(A) | 1997-08-01 | Zereski, Jr. et al. | Applicant |
| US5657072(A) | 1997-08-01 | Aristides et al. | Applicant |
| US5657414(A) | 1997-08-01 | Lett et al. | Applicant |
| US5659367(A) | 1997-08-01 | Yuen | Applicant |
| US5661516(A) | 1997-08-01 | Carles | Applicant |
| US5666498(A) | 1997-09-01 | Amro | Applicant |
| US5666645(A) | 1997-09-01 | Thomas et al. | Applicant |
| US5671225(A) | 1997-09-01 | Hooper et al. | Applicant |
| US5684525(A) | 1997-11-01 | Klosterman | Applicant |
| US5689666(A) | 1997-11-01 | Berquist et al. | Applicant |
| US5694163(A) | 1997-12-01 | Harrison | Applicant |
| US5694176(A) | 1997-12-01 | Bruette et al. | Applicant |
| US5694381(A) | 1997-12-01 | Sako | Applicant |
| US5699107(A) | 1997-12-01 | Lawler et al. | Applicant |
| US5699125(A) | 1997-12-01 | Rzeszewski et al. | Applicant |
| US5701383(A) | 1997-12-01 | Russo et al. | Applicant |
| US5710601(A) | 1998-01-01 | Marshall et al. | Applicant |
| US5717452(A) | 1998-02-01 | Janin et al. | Applicant |
| US5724091(A) | 1998-03-01 | Freeman et al. | Applicant |
| US5724203(A) | 1998-03-01 | Kwoh et al. | Applicant |
| US5727060(A) | 1998-03-01 | Young | Applicant |
| US5732216(A) | 1998-03-01 | Logan et al. | Applicant |
| US5734853(A) | 1998-03-01 | Hendricks et al. | Applicant |
| US5737028(A) | 1998-04-01 | Bertram et al. | Applicant |
| US5745710(A) | 1998-04-01 | Clanton, III et al. | Applicant |
| US5751282(A) | 1998-05-01 | Girard et al. | Applicant |
| US5752159(A) | 1998-05-01 | Faust et al. | Applicant |
| US5754771(A) | 1998-05-01 | Epperson et al. | Applicant |
| US5758257(A) | 1998-05-01 | Herz et al. | Applicant |
| US5760821(A) | 1998-06-01 | Ellis et al. | Applicant |
| US5761607(A) | 1998-06-01 | Gudesen | Applicant |
| US5768528(A) | 1998-06-01 | Stumm | Applicant |
| US5771354(A) | 1998-06-01 | Crawford | Applicant |
| US5778181(A) | 1998-07-01 | Hidary et al. | Applicant |
| US5778182(A) | 1998-07-01 | Cathey et al. | Applicant |
| US5781226(A) | 1998-07-01 | Sheehan | Applicant |
| US5781228(A) | 1998-07-01 | Sposato | Applicant |
| US5781246(A) | 1998-07-01 | Alten et al. | Applicant |
| US5790198(A) | 1998-08-01 | Roop et al. | Applicant |
| US5790202(A) | 1998-08-01 | Kummer et al. | Applicant |
| US5796952(A) | 1998-08-01 | Davis et al. | Applicant |
| US5801747(A) | 1998-09-01 | Bedard | Applicant |
| US5801787(A) | 1998-09-01 | Schein et al. | Applicant |
| US5802284(A) | 1998-09-01 | Karlton et al. | Applicant |
| US5805155(A) | 1998-09-01 | Allibhoy et al. | Applicant |
| US5805763(A) | 1998-09-01 | Lawler et al. | Applicant |
| US5805804(A) | 1998-09-01 | Laursen et al. | Applicant |
| US5808608(A) | 1998-09-01 | Young et al. | Applicant |
| US5808694(A) | 1998-09-01 | Usui et al. | Applicant |
| US5809204(A) | 1998-09-01 | Young et al. | Applicant |
| US5812123(A) | 1998-09-01 | Rowe et al. | Applicant |
| US5812205(A) | 1998-09-01 | Milnes et al. | Applicant |
| US5812937(A) | 1998-09-01 | Takahisa | Applicant |
| US5815662(A) | 1998-09-01 | Ong | Applicant |
| US5818438(A) | 1998-10-01 | Howe et al. | Applicant |
| US5819019(A) | 1998-10-01 | Nelson | Applicant |
| US5819156(A) | 1998-10-01 | Belmont | Applicant |
| US5822123(A) | 1998-10-01 | Davis et al. | Applicant |
| US5828420(A) | 1998-10-01 | Marshall et al. | Applicant |
| US5828945(A) | 1998-10-01 | Klosterman | Applicant |
| US5838314(A) | 1998-11-01 | Neel et al. | Applicant |
| US5841938(A) | 1998-11-01 | Nitta et al. | Applicant |
| US5844620(A) | 1998-12-01 | Coleman et al. | Applicant |
| US5850218(A) | 1998-12-01 | LaJoie et al. | Applicant |
| US5867227(A) | 1999-02-01 | Yamaguchi | Applicant |
| US5903314(A) | 1999-05-01 | Niijima et al. | Applicant |
| US5909212(A) | 1999-06-01 | Nishina et al. | Applicant |
| US5917481(A) | 1999-06-01 | Rzeszewski et al. | Applicant |
| US5940073(A) | 1999-08-01 | Klosterman et al. | Applicant |
| US5940387(A) | 1999-08-01 | Humpleman | Applicant |
| US5940572(A) | 1999-08-01 | Balaban et al. | Applicant |
| US5945988(A) | 1999-08-01 | Williams et al. | Applicant |
| US5949954(A) | 1999-09-01 | Young et al. | Applicant |
| US5959592(A) | 1999-09-01 | Petruzzelli | Applicant |
| US5963264(A) | 1999-10-01 | Jackson | Applicant |
| US5963645(A) | 1999-10-01 | Kigawa et al. | Applicant |
| US5970486(A) | 1999-10-01 | Yoshida et al. | Applicant |
| US5973683(A) | 1999-10-01 | Cragun et al. | Applicant |
| US5974222(A) | 1999-10-01 | Yuen et al. | Applicant |
| US5977964(A) | 1999-11-01 | Williams et al. | Applicant |
| US5987213(A) | 1999-11-01 | Mankovitz et al. | Applicant |
| US5991799(A) | 1999-11-01 | Yen et al. | Applicant |
| US5995155(A) | 1999-11-01 | Schindler et al. | Applicant |
| US5999688(A) | 1999-12-01 | Iggulden et al. | Applicant |
| US6002394(A) | 1999-12-01 | Schein et al. | Applicant |
| US6005561(A) | 1999-12-01 | Hawkins et al. | Applicant |
| US6005631(A) | 1999-12-01 | Anderson et al. | Applicant |
| US6006257(A) | 1999-12-01 | Slezak | Applicant |
| US6020880(A) | 2000-02-01 | Naimpally | Applicant |
| US6020883(A) | 2000-02-01 | Herz et al. | Applicant |
| US6038367(A) | 2000-03-01 | Abecassis | Applicant |
| US6052145(A) | 2000-04-01 | Macrae et al. | Applicant |
| US6057872(A) | 2000-05-01 | Candelore | Applicant |
| US6057890(A) | 2000-05-01 | Virden et al. | Applicant |
| US6058238(A) | 2000-05-01 | Ng | Applicant |
| US6061097(A) | 2000-05-01 | Satterfield | Applicant |
| US6091883(A) | 2000-07-01 | Artigalas et al. | Applicant |
| US6091884(A) | 2000-07-01 | Yuen et al. | Applicant |
| US6094680(A) | 2000-07-01 | Hokanson | Applicant |
| USRE36801(E) | 2000-08-01 | Logan et al. | Applicant |
| US6115057(A) | 2000-09-01 | Kwoh et al. | Applicant |
| US6118493(A) | 2000-09-01 | Duhault et al. | Applicant |
| US6122011(A) | 2000-09-01 | Dias et al. | Applicant |
| US6125230(A) | 2000-09-01 | Yaqinuma | Applicant |
| US6125231(A) | 2000-09-01 | Yuen et al. | Applicant |
| US6130726(A) | 2000-10-01 | Darbee et al. | Applicant |
| US6133910(A) | 2000-10-01 | Stinebruner | Applicant |
| US6141488(A) | 2000-10-01 | Knudson et al. | Applicant |
| US6147715(A) | 2000-11-01 | Yuen et al. | Applicant |
| US6157413(A) | 2000-12-01 | Hanafee et al. | Applicant |
| US6163316(A) | 2000-12-01 | Killian | Applicant |
| US6167188(A) | 2000-12-01 | Young et al. | Applicant |
| US6172674(B1) | 2001-01-01 | Etheredge | Applicant |
| US6177931(B1) | 2001-01-01 | Alexander et al. | Applicant |
| US6208335(B1) | 2001-03-01 | Gordon et al. | Applicant |
| US6208799(B1) | 2001-03-01 | Marsh et al. | Applicant |
| US6219839(B1) | 2001-04-01 | Sampsell | Applicant |
| US6233389(B1) | 2001-05-01 | Barton et al. | Applicant |
| US6239794(B1) | 2001-05-01 | Yuen et al. | Applicant |
| US6240105(B1) | 2001-05-01 | Zetts | Examiner |
| US6240241(B1) | 2001-05-01 | Yuen | Applicant |
| US6256071(B1) | 2001-07-01 | Hiroi | Applicant |
| US6263501(B1) | 2001-07-01 | Schein et al. | Applicant |
| US6275648(B1) | 2001-08-01 | Knudson et al. | Applicant |
| US6289346(B1) | 2001-09-01 | Milewski et al. | Applicant |
| US6292624(B1) | 2001-09-01 | Saib et al. | Applicant |
| US6324338(B1) | 2001-11-01 | Wood et al. | Applicant |
| US6326982(B1) | 2001-12-01 | Wu et al. | Applicant |
| US6327418(B1) | 2001-12-01 | Barton et al. | Applicant |
| US6334022(B1) | 2001-12-01 | Ohba et al. | Applicant |
| US6345279(B1) | 2002-02-01 | Li et al. | Applicant |
| US6388714(B1) | 2002-05-01 | Schein et al. | Applicant |
| US6414725(B1) | 2002-07-01 | Clarin et al. | Applicant |
| US6434614(B1) | 2002-08-01 | Blumenau | Applicant |
| US6441832(B1) | 2002-08-01 | Tao et al. | Applicant |
| US6442332(B1) | 2002-08-01 | Knudson et al. | Applicant |
| USRE37881(E) | 2002-10-01 | Haines | Applicant |
| US6470319(B1) | 2002-10-01 | Ryan | Applicant |
| US6473559(B1) | 2002-10-01 | Knudson et al. | Applicant |
| US6486892(B1) | 2002-11-01 | Stern | Applicant |
| US6487362(B1) | 2002-11-01 | Yuen et al. | Applicant |
| US6498895(B2) | 2002-12-01 | Young et al. | Applicant |
| US6505348(B1) | 2003-01-01 | Knowles et al. | Applicant |
| US6532589(B1) | 2003-03-01 | Proehl et al. | Applicant |
| US6549715(B1) | 2003-04-01 | Sasaki | Applicant |
| US6564005(B1) | 2003-05-01 | Berstis | Applicant |
| US6564378(B1) | 2003-05-01 | Satterfield et al. | Applicant |
| US6574716(B2) | 2003-06-01 | Dovi | Applicant |
| US6601237(B1) | 2003-07-01 | Kate et al. | Applicant |
| US6640145(B2) | 2003-10-01 | Hoffberg et al. | Applicant |
| US6670971(B1) | 2003-12-01 | Oral | Applicant |
| US6678737(B1) | 2004-01-01 | Bucher | Applicant |
| US6721954(B1) | 2004-04-01 | Nickum | Applicant |
| US6725253(B1) | 2004-04-01 | Okano et al. | Applicant |
| US6727914(B1) | 2004-04-01 | Gutta | Applicant |
| US6744967(B2) | 2004-06-01 | Kaminski et al. | Applicant |
| US6748481(B1) | 2004-06-01 | Parry et al. | Applicant |
| US6756997(B1) | 2004-06-01 | Ward, III et al. | Applicant |
| US6772433(B1) | 2004-08-01 | LaJoie et al. | Applicant |
| US6788882(B1) | 2004-09-01 | Geer et al. | Applicant |
| US6789204(B2) | 2004-09-01 | Abdelnur et al. | Applicant |
| US6792197(B1) | 2004-09-01 | Helmstetter | Applicant |
| US6820278(B1) | 2004-11-01 | Ellis | Applicant |
| US6850693(B2) | 2005-02-01 | Young et al. | Applicant |
| US6853728(B1) | 2005-02-01 | Kahn et al. | Applicant |
| US6857130(B2) | 2005-02-01 | Srikantan et al. | Examiner |
| US6934964(B1) | 2005-08-01 | Schaffer et al. | Applicant |
| US6961511(B2) | 2005-11-01 | Ohno | Applicant |
| US6977897(B1) | 2005-12-01 | Nelson et al. | Applicant |
| US7088910(B2) | 2006-08-01 | Potrebic et al. | Applicant |
| US7089321(B2) | 2006-08-01 | Hayashi | Examiner |
| US7089348(B2) | 2006-08-01 | Parry et al. | Applicant |
| US7096486(B1) | 2006-08-01 | Ukai et al. | Applicant |
| US7116894(B1) | 2006-10-01 | Chatterton | Applicant |
| US7130623(B2) | 2006-10-01 | Kirkeby et al. | Applicant |
| US7139868(B2) | 2006-11-01 | Parry et al. | Applicant |
| US7143170(B2) | 2006-11-01 | Swildens et al. | Applicant |
| US7151886(B2) | 2006-12-01 | Young et al. | Applicant |
| US7165098(B1) | 2007-01-01 | Boyer et al. | Applicant |
| US7185355(B1) | 2007-02-01 | Ellis et al. | Applicant |
| US7187847(B2) | 2007-03-01 | Young et al. | Applicant |
| US7209640(B2) | 2007-04-01 | Young et al. | Applicant |
| US7243364(B2) | 2007-07-01 | Dunn et al. | Applicant |
| US7293276(B2) | 2007-11-01 | Phillips et al. | Applicant |
| US7298960(B1) | 2007-11-01 | Taylor et al. | Applicant |
| US7430753(B2) | 2008-09-01 | Gray et al. | Applicant |
| US7454120(B2) | 2008-11-01 | Putterman et al. | Applicant |
| US7457511(B2) | 2008-11-01 | Putterman et al. | Applicant |
| US7477832(B2) | 2009-01-01 | Young et al. | Applicant |
| US7546363(B2) | 2009-06-01 | Harrow et al. | Applicant |
| US7603022(B2) | 2009-10-01 | Putterman et al. | Applicant |
| US7640564(B2) | 2009-12-01 | Green et al. | Applicant |
| US7650621(B2) | 2010-01-01 | Thomas et al. | Applicant |
| US7739709(B2) | 2010-06-01 | Ellis et al. | Applicant |
| US7779445(B2) | 2010-08-01 | Ellis | Applicant |
| US7840977(B2) | 2010-11-01 | Walker et al. | Applicant |
| US2001/0043795(A1) | 2001-11-01 | Wood et al. | Applicant |
| US2002/0010917(A1) | 2002-01-01 | Srikantan et al. | Applicant |
| US2002/0016818(A1) | 2002-02-01 | Kirani et al. | Applicant |
| US2002/0059599(A1) | 2002-05-01 | Schein et al. | Applicant |
| US2002/0059621(A1) | 2002-05-01 | Thomas et al. | Applicant |
| US2002/0073229(A1) | 2002-06-01 | Hayashi | Applicant |
| US2002/0090203(A1) | 2002-07-01 | Mankovitz | Applicant |
| US2002/0152311(A1) | 2002-10-01 | Veltman et al. | Applicant |
| US2002/0174430(A1) | 2002-11-01 | Ellis et al. | Applicant |
| US2002/0184451(A1) | 2002-12-01 | Dovi | Applicant |
| US2002/0191954(A1) | 2002-12-01 | Beach et al. | Applicant |
| US2002/0194585(A1) | 2002-12-01 | Connelly | Applicant |
| US2002/0194598(A1) | 2002-12-01 | Connelly | Applicant |
| US2002/0194607(A1) | 2002-12-01 | Connelly | Applicant |
| US2003/0009766(A1) | 2003-01-01 | Marolda | Applicant |
| US2003/0020744(A1) | 2003-01-01 | Ellis et al. | Applicant |
| US2003/0046057(A1) | 2003-03-01 | Okunishi et al. | Applicant |
| US2003/0086023(A1) | 2003-05-01 | Chung et al. | Applicant |
| US2003/0110499(A1) | 2003-06-01 | Knudson et al. | Applicant |
| US2003/0118323(A1) | 2003-06-01 | Ismail et al. | Applicant |
| US2003/0149980(A1) | 2003-08-01 | Hassel et al. | Applicant |
| US2003/0149988(A1) | 2003-08-01 | Ellis et al. | Applicant |
| US2003/0154486(A1) | 2003-08-01 | Dunn et al. | Applicant |
| US2003/0154493(A1) | 2003-08-01 | Kagle | Applicant |
| US2003/0204848(A1) | 2003-10-01 | Cheng | Applicant |
| US2003/0204856(A1) | 2003-10-01 | Buxton | Applicant |
| US2003/0210898(A1) | 2003-11-01 | Juen et al. | Applicant |
| US2004/0008971(A1) | 2004-01-01 | Young et al. | Applicant |
| US2004/0013406(A1) | 2004-01-01 | Barton et al. | Applicant |
| US2004/0107236(A1) | 2004-06-01 | Nakagawa et al. | Applicant |
| US2004/0128686(A1) | 2004-07-01 | Boyer et al. | Applicant |
| US2004/0163130(A1) | 2004-08-01 | Gray et al. | Applicant |
| US2004/0181814(A1) | 2004-09-01 | Ellis et al. | Applicant |
| US2004/0186901(A1) | 2004-09-01 | Guigui | Applicant |
| US2004/0215757(A1) | 2004-10-01 | Butler | Applicant |
| US2004/0218905(A1) | 2004-11-01 | Green et al. | Applicant |
| US2004/0221019(A1) | 2004-11-01 | Swildens | Applicant |
| US2004/0221302(A1) | 2004-11-01 | Ansari et al. | Examiner |
| US2004/0268407(A1) | 2004-12-01 | Sparrell et al. | Examiner |
| US2005/0002638(A1) | 2005-01-01 | Putterman et al. | Applicant |
| US2005/0002640(A1) | 2005-01-01 | Putterman et al. | Applicant |
| US2005/0010671(A1) | 2005-01-01 | Grannan | Applicant |
| US2005/0028208(A1) | 2005-02-01 | Ellis et al. | Examiner |
| US2005/0044567(A1) | 2005-02-01 | Young et al. | Applicant |
| US2005/0102698(A1) | 2005-05-01 | Bumgardner et al. | Applicant |
| US2005/0149964(A1) | 2005-07-01 | Thomas et al. | Applicant |
| US2005/0152669(A1) | 2005-07-01 | Kim et al. | Applicant |
| US2005/0204388(A1) | 2005-09-01 | Knudson et al. | Applicant |
| US2005/0240968(A1) | 2005-10-01 | Knudson et al. | Applicant |
| US2005/0251827(A1) | 2005-11-01 | Ellis et al. | Applicant |
| US2005/0273819(A1) | 2005-12-01 | Knudson et al. | Applicant |
| US2005/0283547(A1) | 2005-12-01 | Parry et al. | Applicant |
| US2006/0018625(A1) | 2006-01-01 | Johnson et al. | Applicant |
| US2006/0080415(A1) | 2006-04-01 | Tu | Applicant |
| US2006/0101417(A1) | 2006-05-01 | Hoh | Applicant |
| US2006/0114360(A1) | 2006-06-01 | Kortum et al. | Applicant |
| US2006/0136965(A1) | 2006-06-01 | Ellis et al. | Applicant |
| US2006/0140584(A1) | 2006-06-01 | Ellis et al. | Applicant |
| US2006/0179462(A1) | 2006-08-01 | Willame et al. | Examiner |
| US2007/0058924(A1) | 2007-03-01 | Yeh | Applicant |
| US2007/0067800(A1) | 2007-03-01 | Wachtfogel et al. | Examiner |
| US2007/0101377(A1) | 2007-05-01 | Six et al. | Applicant |
| US2007/0104456(A1) | 2007-05-01 | Craner et al. | Applicant |
| US2007/0157234(A1) | 2007-07-01 | Walker | Applicant |
| US2007/0157241(A1) | 2007-07-01 | Walker | Applicant |
| US2007/0157266(A1) | 2007-07-01 | Ellis et al. | Applicant |
| US2007/0199030(A1) | 2007-08-01 | Ellis et al. | Applicant |
| US2008/0115169(A1) | 2008-05-01 | Ellis et al. | Applicant |
| US2008/0184327(A1) | 2008-07-01 | Ellis et al. | Applicant |
| US2009/0034935(A1) | 2009-02-01 | Putterman et al. | Applicant |
| US2009/0074380(A1) | 2009-03-01 | Boston et al. | Applicant |
| US2009/0222875(A1) | 2009-09-01 | Cheng et al. | Examiner |
| US2010/0074600(A1) | 2010-03-01 | Putterman et al. | Applicant |
| US2010/0175086(A1) | 2010-07-01 | Gaydou et al. | Applicant |
| DE4440419 | 1996-05-01 | Applicant | |
| EP122626 | 1984-10-01 | Applicant | |
| EP133985 | 1985-03-01 | Applicant | |
| EP424469 | 1991-05-01 | Applicant | |
| EP572090 | 1993-12-01 | Applicant | |
| EP682452 | 1995-11-01 | Applicant | |
| EP753964 | 1997-01-01 | Applicant | |
| EP762756 | 1997-03-01 | Applicant | |
| EP763938 | 1997-03-01 | Applicant | |
| EP836320 | 1998-04-01 | Applicant | |
| EP843468 | 1998-05-01 | Applicant | |
| EP848554 | 1998-06-01 | Applicant | |
| EP854645 | 1998-07-01 | Applicant | |
| EP874524 | 1998-10-01 | Applicant | |
| EP940983 | 1999-09-01 | Applicant | |
| EP940985 | 1999-09-01 | Applicant | |
| EP1280122 | 2003-01-01 | Applicant | |
| EP1355496 | 2003-10-01 | Applicant | |
| EP1387272 | 2004-02-01 | Applicant | |
| EP1473934 | 2004-11-01 | Applicant | |
| GB2227622(A) | 1990-08-01 | Applicant | |
| GB2229595(A) | 1990-09-01 | Applicant | |
| GB2346251(A) | 2000-08-01 | Applicant | |
| JP6-111413 | 1994-04-01 | Applicant | |
| JP6-303541 | 1994-10-01 | Applicant | |
| JP9-289630 | 1997-11-01 | Applicant | |
| JP10-042242 | 1998-02-01 | Applicant | |
| JP10-112087 | 1998-04-01 | Applicant | |
| JP10-164487 | 1998-06-01 | Applicant | |
| JP11-088280 | 1999-03-01 | Applicant | |
| JP11-136615 | 1999-05-01 | Applicant | |
| JP11-266414 | 1999-09-01 | Applicant | |
| JP11-313280 | 1999-11-01 | Applicant | |
| JP11-353071 | 1999-12-01 | Applicant | |
| JP2000-013708 | 2000-01-01 | Applicant | |
| JP2000-138886 | 2000-05-01 | Applicant | |
| JP2000-224533 | 2000-08-01 | Applicant | |
| JP2000-235546 | 2000-08-01 | Applicant | |
| JP2000-306314 | 2000-11-01 | Applicant | |
| JP2001-088372 | 2001-04-01 | Applicant | |
| JP2001-165669 | 2001-06-01 | Applicant | |
| JP2001-167522 | 2001-06-01 | Applicant | |
| JP2001-257950 | 2001-09-01 | Applicant | |
| JP2002-185951 | 2002-06-01 | Applicant | |
| JP2004-007592(A) | 2004-01-01 | Applicant | |
| JP2004-23326(A) | 2004-01-01 | Applicant | |
| TW247388 | 1994-10-01 | Applicant | |
| WO88/04507 | 1988-06-01 | Applicant | |
| WO90/00847 | 1990-01-01 | Applicant | |
| WO90/07844 | 1990-07-01 | Applicant | |
| WO91/00670 | 1991-01-01 | Applicant | |
| WO91/07050 | 1991-05-01 | Applicant | |
| WO92/04801 | 1992-03-01 | Applicant | |
| WO92/22983 | 1992-12-01 | Applicant | |
| WO93/04473 | 1993-03-01 | Applicant | |
| WO93/08542 | 1993-04-01 | Applicant | |
| WO93/23957 | 1993-11-01 | Applicant | |
| WO94/13284 | 1994-06-01 | Applicant | |
| WO94/14284 | 1994-06-01 | Applicant | |
| WO95/01058 | 1995-01-01 | Applicant | |
| WO95/04431 | 1995-02-01 | Applicant | |
| WO95/11567 | 1995-04-01 | Applicant | |
| WO95/18449 | 1995-07-01 | Applicant | |
| WO95/31069 | 1995-11-01 | Applicant | |
| WO95/32584 | 1995-11-01 | Applicant | |
| WO95/32585 | 1995-11-01 | Applicant | |
| WO95/32587 | 1995-11-01 | Applicant | |
| WO96/09721 | 1996-03-01 | Applicant | |
| WO96/13932 | 1996-05-01 | Applicant | |
| WO96/25821 | 1996-08-01 | Applicant | |
| WO96/26605 | 1996-08-01 | Applicant | |
| WO96/27982 | 1996-09-01 | Applicant | |
| WO96/31980 | 1996-10-01 | Applicant | |
| WO96/33572 | 1996-10-01 | Applicant | |
| WO96/34491 | 1996-10-01 | Applicant | |
| WO96/36172 | 1996-11-01 | Applicant | |
| WO96/37075 | 1996-11-01 | Applicant | |
| WO96/41418 | 1996-12-01 | Applicant | |
| WO96/41472 | 1996-12-01 | Applicant | |
| WO96/41478 | 1996-12-01 | Applicant | |
| WO97/13368 | 1997-04-01 | Applicant | |
| WO97/31479 | 1997-08-01 | Applicant | |
| WO97/32434 | 1997-09-01 | Applicant | |
| WO97/34413 | 1997-09-01 | Applicant | |
| WO97/34414 | 1997-09-01 | Applicant | |
| WO97/40623 | 1997-10-01 | Applicant | |
| WO97/42763 | 1997-11-01 | Applicant | |
| WO97/46016 | 1997-12-01 | Applicant | |
| WO97/46943 | 1997-12-01 | Applicant | |
| WO97/47124 | 1997-12-01 | Applicant | |
| WO97/48228 | 1997-12-01 | Applicant | |
| WO97/48230 | 1997-12-01 | Applicant | |
| WO97/49237 | 1997-12-01 | Applicant | |
| WO97/49242 | 1997-12-01 | Applicant | |
| WO98/01995 | 1998-01-01 | Applicant | |
| WO98/06219 | 1998-02-01 | Applicant | |
| WO98/07277 | 1998-02-01 | Applicant | |
| WO98/10589 | 1998-03-01 | Applicant | |
| WO98/12872 | 1998-03-01 | Applicant | |
| WO98/16056 | 1998-04-01 | Applicant | |
| WO98/17064 | 1998-04-01 | Applicant | |
| WO98/26584 | 1998-06-01 | Applicant | |
| WO98/26594 | 1998-06-01 | Applicant | |
| WO98/26596 | 1998-06-01 | Applicant | |
| WO98/38831 | 1998-09-01 | Applicant | |
| WO98/39893 | 1998-09-01 | Applicant | |
| WO98/43183 | 1998-10-01 | Applicant | |
| WO98/47279 | 1998-10-01 | Applicant | |
| WO98/47283 | 1998-10-01 | Applicant | |
| WO98/47287 | 1998-10-01 | Applicant | |
| WO98/47289 | 1998-10-01 | Applicant | |
| WO99/03267 | 1999-01-01 | Applicant | |
| WO99/12346 | 1999-03-01 | Applicant | |
| WO99/45700 | 1999-09-01 | Applicant | |
| WO99/52279 | 1999-10-01 | Applicant | |
| WO99/57839 | 1999-11-01 | Applicant | |
| WO99/60790 | 1999-11-01 | Applicant | |
| WO99/66725 | 1999-12-01 | Applicant | |
| WO/04706 | 2000-01-01 | Applicant | |
| WO/07368 | 2000-02-01 | Applicant | |
| WO/08850 | 2000-02-01 | Applicant | |
| WO/08851 | 2000-02-01 | Applicant | |
| WO/08852 | 2000-02-01 | Applicant | |
| WO/11869 | 2000-03-01 | Applicant | |
| WO/16548 | 2000-03-01 | Applicant | |
| WO/28739 | 2000-05-01 | Applicant | |
| WO/35193 | 2000-06-01 | Applicant | |
| WO/58833 | 2000-10-01 | Applicant | |
| WO/58967 | 2000-10-01 | Applicant | |
| WO/59214 | 2000-10-01 | Applicant | |
| WO/59223 | 2000-10-01 | Applicant | |
| WO/62298 | 2000-10-01 | Applicant | |
| WO/62299 | 2000-10-01 | Applicant | |
| WO/62533 | 2000-10-01 | Applicant | |
| WO/67475 | 2000-11-01 | Applicant | |
| WO1/03088 | 2001-01-01 | Applicant | |
| WO1/22729 | 2001-03-01 | Applicant | |
| WO1/46843 | 2001-06-01 | Applicant | |
| WO1/47238 | 2001-06-01 | Applicant | |
| WO1/47249 | 2001-06-01 | Applicant | |
| WO1/47257 | 2001-06-01 | Applicant | |
| WO1/47273 | 2001-06-01 | Applicant | |
| WO1/47279 | 2001-06-01 | Applicant | |
| WO1/76239 | 2001-10-01 | Applicant | |
| WO1/76248 | 2001-10-01 | Applicant | |
| WO1/86511 | 2001-11-01 | Applicant | |
| WO2/069636 | 2002-09-01 | Applicant | |
| WO2/078317 | 2002-10-01 | Applicant | |
| WO3/026187 | 2003-03-01 | Applicant | |
| WO3/032620 | 2003-04-01 | Applicant | |
| WO3/047235 | 2003-06-01 | Applicant | |
| WO2004/059528 | 2004-07-01 | Applicant | |
| WO2008/042242 | 2008-04-01 | Applicant |
Non-Patent Literature (30)
- “Automatic Windows 98/Me TCP/IP Addressing Without a DHCP Server”. Revised Oct. 20, 2000. http://web.archive.org/web/20010208204235/http://support.microsoft.com/support/kb/articles/Q220/8/74.ASP.Examiner
- Goland, Yaron et al. SSDP Draft Standard. Oct. 28, 1999. http://tools.ietf.org/html/draft-cai-ssdp-v1-03.Examiner
- “Universal Plug and Play Device Architecture.” Version 1.0, Jun. 8, 2000.Examiner
- “DIRECTV Digital Satellite Receiver—Operating Instructions,” Sony Electronics Inc. (2001).Applicant
- “DIRECTV Receiver—Owner's Manual,” DIRECTV, INC. (2002).Applicant
- “DIRECTV Receiver with TiVo Digital Satellite Receiver/Recorder SAT-T60—Installation Guide,” Sony Corporation (2000).Applicant
- “DIRECTV Receiver with TiVo Installation Guide,” Philips (2000).Applicant
- “DIRECTV Receiver with TiVo Viewers Guide” (1999, 2000).Applicant
- “DishPro Satellite System—Users Guide,” Dish Network, (undated), accessed 2008.Applicant
- “Fall 2001 TiVo Service Update with Dual Tuner!,” TiVo Inc. (2001).Applicant
- “PTV Recorder Setup Guide,” Philips (2000).Applicant
- “RCA Satellite Receiver Users Guide,” Thomson Multimedia Inc. (2001).Applicant
- “Start Here,” Sony, TiVo and DIRECTV, (undated), accessed 2008.Applicant
- “VPV-Videotext Programs Videorecorder”, by Bensch, IEEE Jun. 1988, pp. 788-792.Applicant
- Advanced Analog Systems—Addressable Terminals, General Instrument Corp. of Horsham, Pennsylvania (URL:http//www.gi.com/BUSAREA/ANALOG/TERMINAL/WATCH/watch.html), Printed from the Internet on Mar. 4, 1999.Applicant
- Digital Video Broadcasting (DVB); DVB specification for data broadcasting, European Telecommunications Standards Institute, Draft EN 301 192 V1.2.1 (Jan. 1999).Applicant
- 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.Applicant
- Gong, A Software Architecture for Open Service Gateways, IEEE Internet Computing, Jan.-Feb. 2001 (FROM UV-449).Applicant
- Hofmann et al., Videotext Programmiert Videorecorder, Rundfunktechnische Mitteilungen, Nov.-Dec. 1982, pp. 254-257 (translation attached).Applicant
- http://www.iapplianceweb.com/story/OEG20040510N0003BC.htm (May 11, 2004).Applicant
- Inside I-Guide User's Manual (Aug. 24, 2004).Applicant
- Jaeger, Set-top Box Software Architecture for Digital Video Broadcast and Interative Services, IEEE 2001 (FROM UV-449).Applicant
- Rewind, replay and unwind with new high-tech TV devices, LA Times, Magid. This document was printed from the Internet on Jun. 6, 1999 and bears a date of May 19, 1999.Applicant
- Markoff, 2 Makers Plan Introductions of Digital VCR, The New York Times, Mar. 29, 1999.Applicant
- Monaco et al., “Remote Device Command Resource Sharing over the Internet: A New Approach Based on a Distributed Layered Architecture,” IEEE Transaction on Computers, vol. 51, No. 7, Jul. 2002, pp. 787-792.Applicant
- Saito, Takeshi, et al., “Homenetwork Architecture Considering Digital Home Appliance,” Technical Committee meeting of The Institute of Electronics, Information and Communication Engineers (IEICE), Japan, Nov. 6, 1997, vol. 97, No. 368, p. 57-64.Applicant
- TivoToGo™ Transfers (printed Mar. 8, 2006).Applicant
- User's Guide RCA Color TV with TV Plus + Guide, 1997.Applicant
- Windows 98 Feature Combines TV, Terminal and the Internet, The New York Times, Aug. 18, 1998.Applicant
- Wittress et al., Internet Protocol (IP) Set-Top Boxes, Microsoft Windows Embedded IP Set-Top Boxes, Microsoft Corporation, Sep. 2003.Applicant