Source: http://www.google.de/patents/US8032914
Timestamp: 2015-05-28 07:57:39
Document Index: 276013670

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

Patent US8032914 - Systems and methods for dynamically allocating bandwidth in a digital ... - Google PatenteSuche Bilder Maps Play YouTube News Gmail Drive Mehr »Anmelden Erweiterte Patentsuche PatenteSystems and methods for dynamically allocating bandwidth in a digital broadband delivery system are disclosed. One example method includes receiving information describing subscriber requests for content delivery, receiving bandwidth allocation criteria, and processing the information describing subscriber...http://www.google.de/patents/US8032914?utm_source=gb-gplus-sharePatent US8032914 - Systems and methods for dynamically allocating bandwidth in a digital broadband delivery system Erweiterte Patentsuche Ver�ffentlichungsnummerUS8032914 B2PublikationstypErteilung AnmeldenummerUS 11/969,297 Ver�ffentlichungsdatum4. Okt. 2011Eingetragen4. Jan. 2008 Priorit�tsdatum10. Nov. 2000Geb�hrenstatusBezahltAuch ver�ffentlicht unterUS7340759, US20080101460 Ver�ffentlichungsnummer11969297, 969297, US 8032914 B2, US 8032914B2, US-B2-8032914, US8032914 B2, US8032914B2 ErfinderArturo A. RodriguezUrspr�nglich Bevollm�chtigterRodriguez Arturo AZitat exportierenBiBTeX, EndNote, RefManPatentzitate (99), Nichtpatentzitate (376), Referenziert von (17), Klassifizierungen (31), Juristische Ereignisse (3) Externe Links: USPTO, USPTO-Zuordnung, EspacenetSystems and methods for dynamically allocating bandwidth in a digital broadband delivery system
US 8032914 B2 Zusammenfassung
Systems and methods for dynamically allocating bandwidth in a digital broadband delivery system are disclosed. One example method includes receiving information describing subscriber requests for content delivery, receiving bandwidth allocation criteria, and processing the information describing subscriber requests and the bandwidth allocation criteria according to a statistical model. The bandwidth allocation criteria comprise at least one of subscriber pricing information, content delivery mode information, and program content information. The processing produces a bandwidth allocation schedule in which one of a plurality of content delivery modes is assigned to each of a plurality of digital transmission channels for each of a plurality of time periods.
1. A method of dynamically allocating bandwidth in a digital broadband delivery method, the method comprising:
receiving information describing subscriber requests for content delivery;
receiving bandwidth allocation criteria comprising at least one of subscriber pricing information, content delivery mode information, and program content information; and
processing the information describing subscriber requests and the bandwidth allocation criteria, according to a statistical model, to produce a bandwidth allocation schedule in which one of a plurality of content delivery modes is assigned to each of a plurality of digital transmission channels for each of a plurality of time periods.
processing the subscriber request information and the bandwidth allocation criteria according to a predetermined statistical model designed to maximize a total number of subscriber requests fulfilled.
processing the subscriber request information and the bandwidth allocation criteria according to a predetermined statistical model designed to maximize revenue generated from the bandwidth.
processing the subscriber request information and the bandwidth allocation criteria according to a predetermined statistical model, the model based on analysis of a history describing bandwidth consumption of subscribers over time.
5. The method of claim 1, wherein the bandwidth allocation criteria further comprises subscriber priority data which prioritizes requests of one subscriber above the requests of another subscriber.
repeating the receiving information and receiving bandwidth allocation criteria;
determining whether to revise the statistical model based on changes in bandwidth demand or changes in bandwidth consumption pattern; and
updating the statistical model with the newly received information based on the determination.
7. The method of claim 1, wherein the processing further comprises producing the bandwidth allocation schedule which includes a particular program that is repeatedly broadcast at non-linear non-decreasing time intervals.
8. The method of claim 1, wherein the processing further comprises producing the bandwidth allocation schedule which includes a program which is repeatedly broadcast at a non-linear progression rate with start times that double the time separation between the two previous start times.
9. The method of claim 1, wherein the processing further comprises producing the bandwidth allocation schedule which includes a program which is repeatedly broadcast using a non-linear progression of the program's start time that is proportionate to a personal activity duration, the personal activity gathered from historical subscriber viewing data.
10. The method of claim 1, wherein the processing further comprises selecting the bandwidth allocation schedule from one of a plurality of pre-configured allocation schedules.
11. A headend in a digital broadband delivery system comprising:
memory having program code stored thereon; and
receive information describing subscriber requests for content delivery;
receive bandwidth allocation criteria comprising at least one of subscriber pricing information, content delivery mode information, and program content information; and
process the information describing subscriber requests and the bandwidth allocation criteria, according to a statistical model, to produce a bandwidth allocation schedule in which one of a plurality of content delivery modes is assigned to each of a plurality of digital transmission channels for each of a plurality of time periods.
12. The headend of claim 11, wherein the statistical model is a predetermined statistical model designed to maximize a total number of subscriber requests fulfilled.
13. The headend of claim 11, wherein the statistical model is a predetermined statistical model designed to maximize revenue generated from the bandwidth.
14. The headend of claim 11, wherein the statistical model is a predetermined statistical model based on analysis of a history describing bandwidth consumption of subscribers over time.
15. The headend of claim 11, wherein the bandwidth allocation criteria further comprises subscriber priority data which prioritizes requests of one subscriber above the requests of another subscriber.
16. The headend of claim 11, wherein the processor is further programmed by the program code to:
repeat the receiving information and receiving bandwidth allocation criteria;
determine whether to revise the statistical model based on changes in bandwidth demand or changes in bandwidth consumption pattern; and
update the statistical model with the newly received information based on the determination.
17. A computer-readable medium having a computer program for dynamically allocating bandwidth in a digital broadband delivery system, the computer program comprising logic executed by a processor, said computer readable medium comprising:
logic configured to receive information describing subscriber requests for content delivery;
logic configured receive bandwidth allocation criteria comprising at least one of subscriber pricing information, content delivery mode information, and program content information; and
logic configured process the information describing subscriber requests and the bandwidth allocation criteria, according to a statistical model, to produce a bandwidth allocation schedule in which one of a plurality of content delivery modes is assigned to each of a plurality of digital transmission channels for each of a plurality of time periods.
18. The computer-readable medium of claim 17, wherein the statistical model is a predetermined statistical model designed to maximize revenue generated from the bandwidth.
19. The computer-readable medium of claim 17, wherein the statistical model is a predetermined statistical model based on analysis of a history describing bandwidth consumption of subscribers over time.
This application is a continuation of U.S. Ser. No. 09/709,145, filed Nov. 10, 2000, which is incorporated herein by reference in its entirety.
The present invention relates to digital broadband delivery systems. More particularly, the invention relates to a pricing system for use in a digital broadband delivery system.
For many years now, attempts have been made to develop new delivery systems that provide users with more control over broadcast programming. Ideally, it should be possible for most viewers to obtain access to particular content at the time of their choosing, notwithstanding the time of day or the number of other viewers simultaneously requesting access. It is also desirable for each viewer to have the ability to perform random-access operations on the program such as Play, Pause, Fast Forward, Rewind, Stop, and Resume Play as in a conventional Video Cassette Recorder. This delivery model is known as true “video-on-demand” (VOD). The problem with implementing a true VOD system is that the most intuitively simple solution, in which a central service provides a separate transmission of a program to individual subscribers upon their requests, requires duplication of equipment and substantial bandwidth resources. Despite recent advances in video compression technology, there still exists a limited amount of bandwidth that may be used to fulfill viewer demands. For this reason, numerous research efforts have been undertaken in an effort to simulate true VOD service by providing viewers with more options while minimizing the number of channels, and consequently the amount of bandwidth, used to broadcast any one program.
A method is provided for dynamically pricing viewing options in a digital broadband communication network by receiving bandwidth allocation information from a bandwidth allocation manager and dynamically assigning a price criterion to each of a plurality of viewing options based at least in part on the bandwidth allocation information. The plurality of viewing options may, for example, comprise a reservation option, a normal-play option, a random access option, an on-demand random access option, and an adjust preference option. Advantageously, the present invention enables cable operators to adaptively price viewing options to take into account bandwidth allocation information and a subscriber's willingness to pay additional fees for the enhanced flexibility and advanced random access features made available by dynamic bandwidth allocation. The present invention also enables cable operators to adapt their pricing schemes based on the viewing options available under the bandwidth allocation determined by the bandwidth allocation manager.
As the high-level operation of DBDSs is well known to those of skill in the art, further description of the overall DBDS 10 of FIG. 1 will not be contained herein. It will be appreciated, however, that the DBDS shown in FIG. 1 is merely illustrative and should not be construed as implying any limitations upon the scope of the present invention. Because the form and content provided to the subscribers DHCT 14 by the DBDS 10 is useful to understanding the purpose, operation and function of the present invention, the data provided by the DBDS to the DHCT will next be discussed with reference to FIG. 2. FIG. 2 shows illustrative channels supported by the DBDS, where the channels 60, 64, 68, 72 and 76 are input into a DHCT 14. The content contained in these input channels is mostly provided by the one or more content providers 18 illustrated in FIG. 1. A portion of the content may be generated at a headend 26 or at a hub 34 that might function as a mini-headend and thus possesses some of the headend functionality.
Although broadcast in nature, the carousel DTCs 68 and on-demand DTCs 72 offer different functionality. The User-to-Network Download Protocol of the MPEG-2 standard's DSM-CC specification (Digital Storage Media—Command and Control) provides the data carousel protocol used for broadcasting data from a Server located at headend 26. It also provides the interactive download protocol for reliable downloading of data from a Server (possibly the same server) to an individual DHCT through the on-demand DTCs. Each carousel and on-demand DTC is defined by a DSM-CC session.
Also shown in FIG. 2 is an Out-Of-Band (OOB) channel that provides a continuously available two-way signaling path to the subscribers' DHCT 14 regardless of which in-band channels are tuned to by an individual DHCT in-band tuner. The DHCT 14 may also comprise multiple in-band tuners in which case the OOB channel complements the service of the set of in-band tuners. The OOB channel consists of a forward data channel (FDC) 76 and a reverse data channel (RDC) 80. The OOB channel can comply to any one of a number of well known transport protocols but preferably complies to either a DAVIC 1.1 Transport Protocol with FDC of 1.544 Mbps or more using QPSK modulation and an RDC of 1.544 Mbps or more using QPSK modulation, or to a DOCSIS Transport Protocol with FDC of 27 Mbps using 64-QAM modulation and a RDC of 1.544 Mbps or more using QPSK modulation or 16-QAM modulation. The OOB channels provide the two-way operation of the network, which allows a subscriber interactivity with the services provided by the network. Therefore, the DHCT 14 typically contains functionality similar to a networked computer (i.e., a computer without a persistent storage device) in addition to traditional set top box functionality, as is well known in the art. Furthermore, the OOB channels are not limited to a 6 MHz spectrum, but generally to a smaller spectrum, such as 1.5 or 3 MHz.
Also included within the DHCT 14 are an OOB tuner and upstream transmitter 108, which is connected to the interface of DBDS 10. It should be appreciated that although the OOB tuner and upstream transmitter are illustrated as one component in FIG. 3, the tuner and transmitter can be independent of each other and located separately within the DHCT 14. Nonetheless, both components should be in communication with the DBDS so that upstream transmissions can be received by the system. The OOB tuner and upstream transmitter 108 enables the DHCT 14 to interface with a DBDS network so that the DHCT 14 can provide upstream data to the network, for example, via a QPSK channel or a QAM channel. In this manner, a subscriber can interact with the DBDS to request services, such as Pay-Per-View programming, View-On-Demand programs, more comprehensive EPG data for desired programs, and data associated with VOD programs and services. Data associated with VOD programs and services may comprise data to populate the entries of a Video Catalogue that is presented to the subscriber via a Graphical-User-Interface (GUI) from which a subscriber selects and purchases movies, retrieves program information for the respective VOD movie titles, and from which the subscriber enters subscriber selection criteria and/or preferences. The VOD Catalogue data set may also comprise database records containing program information such as program showing times, program titles, program descriptions, program genres, program release years, casts lists, ratings information, price criteria (or combinations of multiple price criteria) associated with various viewing options, program durations, and/or links to additional respective program related information such as program previews and critic's reviews and comments. The effective window of calendar days in which a program is purchasable may also be included. As is described in more detail below, the VOD Catalogue data may also comprise one or more database records pertaining to variable fee structures for a particular program.
The DHCT 14 preferably includes an infrared receiver 128 for receiving externally generated information such as subscriber input via an input device such as an Infrared (IR) remote control. The DHCT 14 may also include one or more wireless or wired communication interfaces, also called ports 124, for receiving and/or transmitting data to other devices. For instance, the DHCT may feature USB (Universal Serial Bus), Ethernet (for connection to a computer), IEEE-1394 (for connection to media devices in an entertainment center), serial, and/or parallel ports. The user inputs may, for example, be provided by a computer or transmitter with buttons or keys located either on the exterior of the terminal or by a hand-held remote control device or keyboard that includes user-actuated buttons. Signals generated by such input devices are received by a communication port or receiver in DHCT 14 and consequently interpreted by CPU 110 or other processor in DHCT 14 and passed as input data to the VOD software program residing in system memory 112.
Referring still to FIG. 3, a telephone modem in the DHCT 14 can be utilized for upstream data transmission and a headend 26 or hub 34 or other component located upstream in the DBDS can receive data from a telephone network coupled to a telephone modem and can route the upstream data to a destination internal or external to the DBDS. After the one or more tuners 100, 102, 104 select one or more transmission channels, incoming data is forwarded to hardware 114 comprising circuitry with capability for demodulating 116, demultiplexing and parsing 118, and decrypting 121 the incoming signals. More specifically, the hardware components 114 are capable, among other things, of QAM demodulation, Forward Error Correction (FEC), Parsing MPEG-2 Transport Streams, Packetized Elementary Streams and Elementary Streams, and Decryption, as is well known in the art, to counter the effect of signal processing of broadcast media and data in the DBDS. Particularly, such signal processing is performed at the headend 26 and in some cases it may be performed in part at the hubs 34. Although not illustrated in FIG. 3, additional components can be included within the hardware 114, such as descramblers, decoders, digitizers, signal amplifiers, and other circuitry for signal or error recovery.
Referring now to FIG. 4, there is shown a high-level representation of a headend according to one possible embodiment of the present invention. In this embodiment, the headend 26 contains a video server 410, a video-on-demand application server 115, a network manager 120, a billing system 130, a pricing system, and a bandwidth allocation manager 125. It should be appreciated that although single components (e.g., video server 410, video-on-demand application server 115, network manager 120, etc.) are illustrated in FIG. 4, a headend 26 can feature a plurality of each of the illustrated components or may be configured with alternative embodiments for any one of the individual components. It should also be appreciated that, although the VOD application server 115, bandwidth allocation manager 125, network manager 120, billing system 130, and pricing system are shown as separate components, these components may be combined into one or more components with similar functionality without altering the novel aspects of the present invention. For example, the pricing system may be incorporated as part of the bandwidth allocation manager 125, billing system 130, or VOD application server 115 without altering the novel aspects of the present invention. It will also be appreciated that one or more of these components may be located at a location remote from the headend such as in the DHCT 14 or in a separate device in communication with the headend 26 or the DHCT 14.
The video server 410 serves as a repository for storage of video content such as digital movies. Each movie may be represented by a single “normal play” compressed video stream or, alternatively, by multiple streams representing different playback speeds and directions. For example, a single movie may be stored as three separate video streams, one for normal play, one for fast forward and one for reverse. The video content may also comprise content formatted for specific content delivery modes such as VOD or NVOD modes, some of which are described above. The video content is typically transferred from remote content providers 18 as shown in FIG. 1 and stored to the local video server 410 where it can be made available as video streams to the other equipment located within the headend 26.
The VOD application server 115 coordinates the various parts of the system and records transaction and state information in a database. It may also communicate with the billing system 130 and the pricing system to insure that subscribers are charged the appropriate rate for any VOD services that may be provided. In addition, the VOD application server 115 manages the loading of video content such as movies or other programs into the video server 110 from content providers and creates a list of available video titles and associated VOD data. Part of the VOD data, such as the VOD Catalogue, may be transmitted to the DHCTs 14. Other parts of VOD data may reside in the VOD server and be accessible to subscribers on an on-demand basis. For instance, movie previews may be requested by employing the OOB channel to carry the subscriber's request from the DHCT 14 to the VOD application server 115 to view the desired movie preview. The VOD application server 115 may also manage a self-contained database and communicate with the network manager 120 to coordinate the delivery of the VOD services from the video server 110 to the DHCT 14. It is also common for the VOD application server 115 to accept commands from a system administrator through an administration graphical user interface (GUI) to set the parameters and configurations of the VOD components throughout the DBDS. The Administration GUI (not shown) enables the system administrators to configure the system and review past activity.
The billing system 130 communicates with the VOD application server 115, the pricing system, and the network manager 120 to calculate and process subscriber fee information. Information pertaining to fees associated with respective VOD services or other services may be stored locally in the memory 112 of the DHCT 14 and displayed for subscriber viewing via the presentation of a graphical user interface. Alternatively, the billing system 130 may communicate directly with bandwidth allocation manager 125 and/or the pricing system to provide adaptive billing and pricing information pertaining to each available viewing option.
The pricing system communicates with the bandwidth allocation manager 125 to receive bandwidth allocation information and dynamically assigns a price criterion to each of a plurality of viewing options based at least in part on the bandwidth allocation information. The pricing system may also communicate with the DHCT 14 and/or the billing system 130 to transmit pricing information (such as price criteria) to the subscriber and track the price criteria associated with the programs viewed by the subscriber. The subscriber's viewing options may consist of the choices the subscriber has for viewing one or more programs and/or random-access features that may be used while viewing the programs. The price criteria assigned by the pricing system may comprise viewing fees, discounts associated with particular viewing options or with a particular subscriber, redemptive award points, usage fees based on bandwidth consumption (i.e. use of bandwidth by a particular viewing option or random access feature), or any other criteria relating to the costs and/or discounts associated with one or more viewing options and/or bandwidth allocation.
Referring still to FIG. 4, in one embodiment of the present invention, the bandwidth allocation manager 125 is in communication with the VOD application server 115, the network manager 120, and, preferably, the DHCT 14 and pricing system. It will be appreciated by one of ordinary skill in the art, however, that such communication can be established in a number of ways and does not require that there be a direct connection between each of the components. For example, the bandwidth allocation manager 125 may communicate with the VOD application server 115 indirectly by transmitting and receiving information to and from the network manager 120 which then communicates with the VOD application server 115. Similarly, the bandwidth allocation manager 125 may communicate with the DHCT 14 and pricing system indirectly either through the network manager 120 or through the VOD application server 115. Likewise, any communication can be established with any headend component that interfaces a first VOD component to a second VOD component. The bandwidth allocation manager 125 may receive one or more allocation criteria from any one of the above referenced components in communication with the bandwidth allocation manager.
Numerous allocation criteria may be used to determine a bandwidth allocation schedule. According to one aspect of the invention, the allocation criteria comprises one or more subscriber criteria. The subscriber criteria may comprise subscriber preferences selected by the subscriber from a series of preference fields presented to the subscriber via a graphical user interface displayed on the display or TV driven by DHCT 14. The subscriber may select particular preferences, or enter additional data, using any of numerous input devices such as a wireless remote control device or a wired or wireless keyboard. Alternatively, a subscriber may select one of a multiplicity of choices displayed for each preference field as displayed and presented in a GUI. The GUI may include data from a VOD catalogue as described above, including pricing information or pricing alternatives. Examples of subscriber preference data may include movie start times, movie titles, the degree of random access functionality (i.e., the amount of control over movie play desired), or a particular fee that the subscriber is willing to pay (which may be based on one or more price criteria). If the subscriber is presented with a GUI of subscriber preference fields, the subscriber may also be given the option of “don't care” for one or more of the fields. The subscriber may also be given the option of entering multiple sets of preferences, each containing one or more sets of subscriber preferences. The subscriber may also be given the option to order preference sets according to the subscriber's desired priority. An entry for a preference field may be repeated in one or more, and possibly all, preference sets. For instance, the subscriber may enter the same movie title in all preference sets or the same starting time.
In addition, the subscriber may enter a preferred content delivery mode for the movie in a fifth preference field. Since the level of random access functionality is implied by the selected delivery mode, in yet another embodiment, the preference field for the level of random access functionality is replaced with the field for a preferred delivery mode. In another embodiment, the DHCT 14 may include program logic capable of presenting a GUI to a subscriber wherein the subscriber can eliminate choices that would ordinarily be displayed in a respective list for each respective preference field. In this way, a subscriber may, for instance, eliminate undesired delivery modes, undesired start times (such as very late), or undesired high service fees. Subsequently to such interactive configuration sessions, when the subscriber invokes a session to enter his/her viewing preferences for the purchase of a movie service, the GUI presentation does not display the respective eliminated entries for each list associated with a preference field.
According to another aspect of the present invention, the bandwidth allocation manager 125 allocates the available bandwidth based, at least in part, on subscriber criteria comprising a subscriber request received from a subscriber, such as a request for a VOD service according to one or more subscriber preferences as discussed above. To appreciate the advantages of the present invention, it is useful to first set forth a common method used to fulfill a VOD request. In a typical DBDS, for each VOD request it is necessary to set up a “session” between the DHCT 14 and the video server 410. Upon the subscriber instantiating a purchase of a VOD service for a price via the displayed GUI (i.e., the subscriber enters input via an input device and such input may comprise a password or PIN to authenticate authorization to purchase service), a purchase transaction is executed by CPU 110 or some other processor in DHCT 14 that causes a session to be set-up between DBDS resources to the DHCT 14. A session is a logical entity used to define a connection between the DHCT 14 and the video server 410 and the resources used to maintain that connection in the DBDS. The signaling required to implement the session is defined by the MPEG-2 standard's ISO/IEC 13818-6 IS (MPEG-2 DSM-CC). Upon a session setup request generated by the DHCT 14 (usually in response to a request from a subscriber), the network manager 120 verifies the eligibility of the DHCT 14 to receive the VOD service being requested and then passes the request to the VOD application server 115. If the VOD application server 115 determines that it can deliver the service, it communicates with the network manager 120 to reserve the network resources required to deliver the VOD service. The network manager 120 allocates the requested resources, including the necessary bandwidth, and sends a message back to the VOD application server 115 to indicate that the requested resources have been allocated. This message contains MPEG-2 transport stream ID, identifying the physical connection from the video server 110 to the headend 26, and the connectivity from the QAM 137 to the Hub 34 in which the DHCT 14 is connected. The amount of bandwidth that will be reserved for the duration of the VOD session is also communicated. The VOD application server 115 sends a message to the DHCT 14 that indicates that it is ready to begin delivering the video content using the resources allocated. The DHCT 14 receives information in the message identifying the QAM Modulator that is transmitting the video content (and hence where to tune to receive the requested content) and the bandwidth allocated to deliver the service. After a session has been established, the DHCT 14 communicates directly with the VOD application server 115 to facilitate delivery of the requested VOD service. Throughout the course of time that a VOD service is active further messaging is conducted between the respective DHCT 14 receiving the VOD service and the VOD application server 115 to monitor the status of the session. Thus, the VOD server can monitor that a session is properly functioning and determine whether the subscriber has invoked any random access feature of the VOD service.
The procedures for requesting and delivering of a VOD service can be quite complex, especially when there are more requests than there are available VOD bandwidth resources. Advantageously, according to one aspect of invention, the bandwidth allocation manager 125 eliminates some of these problems by dynamically determining bandwidth allocation based on subscriber criteria. Because the bandwidth is not pre-allocated to certain types of DTCs that transmit content according to predetermined delivery modes, the bandwidth allocation manager can dynamically adjust bandwidth allocation in response to a subscriber criterion. This allows the bandwidth allocation manager 125 to either set up a VOD session according to several well-known methods such as that described above, or to choose an alternative delivery method to broadcast the requested VOD service without necessitating a VOD session. For example, since the bandwidth allocation manager 125 receives the subscriber request prior to determining a bandwidth allocation schedule, the bandwidth allocation manager 125 has the option to fulfill the request using any available bandwidth. Hence, if no or a small number of subscribers have requested a particular movie that is planned to be transmitted according to a pay-per-view model, then the bandwidth allocation manager can “recapture” that bandwidth and allocate it to fulfill a subscriber request during the same time period if it is to result in a more financially advantageous bandwidth allocation.
In another aspect of the invention, the bandwidth allocation manager 125 determines a bandwidth allocation schedule (and thus allocates the available bandwidth) based on allocation criteria comprising a subscriber reservation request. The subscriber reservation request is a request initiated by the subscriber to view a particular service at a particular time in the future. According to this aspect of the invention, the DHCT 14 includes a VOD reservation application that allows a user to select video content from a catalog of available services and to select the date and time that they wish to view the video. The VOD reservation application may also allow the user to select the level of random-access functionality desired while viewing the movie. In addition, the reservation application may display the fees and/or price criteria associated with the reservation viewing options. The VOD reservation application may comprise software loaded onto existing DHCT messaging utilities, or additional hardware programmed to provide the requisite functionality. Providing the DHCT 14 with a list of available video content, reservation times, and respective pricing alternatives can be done in a similar fashion to providing data for an EPG service. Typically, the list of available content and respective pricing information is compiled by the VOD application server 115 after incorporating pricing information from pricing system and transferred to the DHCT 14 either automatically or upon transmittal of a request by the DHCT 14. A VOD Catalogue of movie titles with pricing information may be presented to the subscriber through an easy-to-use graphical user interface. For example, the GUI may comprise a series of fields similar to that described above with regard to the subscriber preference fields.
According to another possible bandwidth allocation schedule, a multiplicity of time-adaptive schedules for each of a multiplicity of recurring schedule choices are pre-configured. In this embodiment, the cable system operator may monitor the bandwidth and on-demand service usage and be given the option of manually implementing one of the pre-configured allocation schedules without following a plan. Alternatively, the network manager 120 may automatically monitor bandwidth usage and on-demand service usage and the bandwidth allocation manager 125 may communicate with the network manager 120, the pricing system, and the VOD application server 115 to automatically select one of the pre-configured schedules and/or modify or adjust the pricing of one or more selected services. For instance, six different configurations may be available for time-adaptive management of the bandwidth allocated for movie viewing and on-demand services for a daily recurring schedule. On the other hand, more than six different arrangements may be necessary when implementing time-adaptive bandwidth management on a weekly recurring schedule.
The bandwidth allocation schedule may also employ a small number of auxiliary channels, aggregated to support full random access functionality during a parallel NVOD service. Thus, a set of channels may be assigned for on-demand random access functionality in parallel with the NVOD service featured with progressively non-decreasing staggered start times. Because the activation of random access functionality by any subscriber tends to be for significantly shorter time intervals than for normal playback, bandwidth consumption for random access functionality is relatively small and a small number of auxiliary channels to support on-demand random access functionality are typically sufficient. According to another possible bandwidth allocation schedule and another aspect of the present invention, the cable operator may assess a fee per time usage of the auxiliary channel bandwidth.
Consequently, the subscriber consumes bandwidth for on-demand random access functionality fully aware that he/she is incurring a cost associated with the time that random access functionality is utilized or according to some other parameter. This may be achieved by assigning a price criterion to the on-demand random access viewing option as described in detail below. If on-demand random access functionality is not available instantaneously, the projected delay to provide the bandwidth necessary for the requested random-access feature is typically minimal. To fill the delay, the bandwidth allocation manager 125 or DHCT 14 may cause a temporary graphical or textual barker that indicates that the requested operation is in progress. In such way, the delay will appear shorter since the subscriber focuses attention to the displayed barker. The displayed barker may also display an input device (such as a remote control) key or button with instructions to press such key or button in the input device to cancel the requested on-demand random access operation. Furthermore, such key or button with associated canceling instructions may not be displayed at all unless the delay is significantly longer than expected.
Alternatively, the subscriber continues to consume the bandwidth of the auxiliary channel and the additional associated fee. If the software application determines that significant delay will be experienced to connect the subscriber's DHCT 14 to the broadcast version of the movie where the normal play mode is to resume, the program logic may query the subscriber via a graphical user interface (GUI) to select either to wait for the estimated amount of time or to incur additional dedicated bandwidth granted via one of the auxiliary channels. Random access functionality may also be assisted with a GUI whereby common keys of the input device are employed (e.g., arrow keys) to control cursor position and a separate “select or “enter” key is used to activate the respective random access key displayed with a graphical representation.
According to another aspect of the present invention, the pricing system communicates with the DHCT 14 and the bandwidth allocation manager 125 to provide pricing information associated with the subscriber's viewing options. According to this embodiment, the pricing system receives bandwidth allocation information from the bandwidth allocation manager 125 as described above and, based at least in part on the bandwidth allocation information, assigns a price criterion to each of a plurality of available viewing options. The bandwidth allocation information may comprise information regarding the available bandwidth, the present and scheduled allocation of bandwidth, the content delivery modes associated with the bandwidth allocation, the viewing options available under various bandwidth allocation schemes, or any other information relevant to pricing information associated with the bandwidth allocation. The price criteria assigned by the pricing system may comprise viewing fees, discounts associated with particular viewing options or with a particular subscriber, redemptive award points, usage fees based on bandwidth consumption, or any other criteria relating to the costs and/or discounts associated with one or more viewing options and/or bandwidth allocation schemes. Advantageously, the price criteria assigned to each viewing option may be used to encourage subscribers to make more efficient use of bandwidth resources. In addition, the bandwidth allocation manager 125 may alter the method in which bandwidth is allocated based on the subscriber's willingness to pay a higher price (as evidenced by their selection of viewing options with higher assigned price criteria).
The manner in which the pricing criteria are assigned may also depend on the available viewing options, the bandwidth allocation information, or choices made by the cable operator. For example, according to one embodiment of the present invention, price criteria are assigned according to a predetermined schedule listing the price criteria to be assigned to each viewing option. In this embodiment, the pricing system receives bandwidth allocation information from the bandwidth allocation manager 125 and uses the predetermined schedule to assign a price to each viewing option available under the current bandwidth allocation.
Alternatively, the amount and type of price criteria assigned to each available viewing option may be determined using a predefined statistical model similar to the statistical model described above with respect to the bandwidth allocation manager 125. According to another possible embodiment, the pricing system may utilize a predefined algorithm that assigns pricing criteria by weighting bandwidth allocation information obtained from the bandwidth allocation manager 125, the subscriber profile, or external sources such as program ratings etc. In addition, the pricing system may assign price criteria to each viewing option on a real-time basis, at predetermined intervals, or only in response to a subscriber request (as described below).
It will be appreciated that the manner in which the price criteria are assigned may vary according to the manner in which the bandwidth allocation manager 125 allocates bandwidth. Accordingly, each content delivery mode, bandwidth allocation schedule, and/or each bandwidth allocation statistical model may have a corresponding schedule and/or model used to determine the type and amount of the price criteria assigned to each viewing option. Therefore, each of the bandwidth allocation examples provided above may be associated with a particular pricing scheme under which the pricing system assigns at least one price criterion to each viewing option currently available.
In addition, the pricing system of the present invention enables cable providers to charge different rates for viewing different program content. For example, if a subscriber wishes to view a program that is less popular, the pricing system may assign a higher price criteria to that program than to a program which is very popular and is being broadcast using an NVOD content delivery mode. Thus, during peak periods, one program may cost $10.00 while another program may cost only $5.00. Advantageously, this results in more efficient (and more profitable) use of bandwidth because the additional subscribers may watch the program being broadcast using NVOD without consuming additional bandwidth. The higher fee associated with the less popular program encourages subscribers to watch the program already being broadcast as opposed to consuming additional resources. Moreover, this enables the cable operator to offer a wide variety of programs without wasting bandwidth on programs that are less in demand. If a subscriber is willing to pay a higher fee, then it may be more efficient (or more profitable) to allocate bandwidth to comply with the subscriber's request. If the subscriber is not willing to pay the higher fee, then the bandwidth is better allocated elsewhere.
According to another aspect of the present invention, the pricing system may adaptively assign price criteria to each available viewing option on a real-time or near real-time basis such that the price assigned to a particular viewing option may change as bandwidth is allocated differently or more bandwidth is used (or made available). Hence, the price criteria assigned to each viewing option may be updated at periodic (or non-periodic) intervals. For example, each of the options listed above may change if the viewing times are shifted in either direction or if the subscriber desires to view the program on a different day. Thus, at peak viewing times such as Saturday evenings, the price criteria assigned to full random access options may be very high (such as three or four times the normal price) because the bandwidth at peak times is used more efficiently by allocating it to other content delivery modes.
It will be appreciated that numerous combinations of viewing options may arise depending on the subscriber's preferences and/or the manner in which the bandwidth is allocated. Advantageously, the pricing system of the present invention provides the flexibility to adaptively assign price criteria, regardless of the viewing options available. For example, as described above, the subscriber may be given the option of obtaining on-demand random access functionality using bandwidth assigned via an auxiliary channel dedicated for on-demand random access. In this circumstance, the pricing system may assign price criteria comprising a per/minute charge using the on-demand random access functionality. The pricing system may also dynamically assign a different price criteria if the subscriber chooses to cease using the on-demand random access functionality and continue viewing the program using a different content delivery mode (as described above).
According to another aspect of the present invention, the pricing system may also assign a price criterion to a viewing option based in part on subscriber profile data. As described above, subscriber profile data may comprise information regarding the subscriber's past viewing patterns, the amount and type of the subscriber's previous program purchases, the type of viewing plan used by the subscriber, or other information regarding the subscriber. The pricing system may take this information into account when assigning a price criterion to a particular viewing option for a particular subscriber. For example, if a subscriber is considered a valued customer or has reached a preset threshold qualifying them for a preferential price criterion, the amount of the price criteria assigned to a particular viewing option may be less than it would be otherwise. This may be accomplished by receiving subscriber profile data from the DHCT 14, the bandwidth allocation manager 125, or the billing system 130 and reducing the amount of the assigned price criteria based, at least in part, on that information.
According to another aspect of the present invention, the pricing system may receive a subscriber request related to one or more of the available viewing options and transmit at least one price criterion related to one or more of the available viewing options to the subscriber in response to the request. The subscriber request may comprise a request for a price criteria for a viewing option, a request for viewing a program according to a viewing option, a request for a list of available viewing options or any of numerous other requests wherein the information requested is associated with price criteria. For example, if the subscriber desires to view a particular program, they may request price criteria for each of the viewing options available for that program for a particular time (or for a particular period of time such as a day, week or month). In response, the pricing system may transmit the price criteria for each viewing option to the subscriber. This may be accomplished by transmitting the price criteria to the DHCT 14 which may then display the information to the subscriber via a series of menus as described above.
Alternatively, the subscriber request may comprise an indirect request that is generated by the DHCT 14 in response to an action taken by the subscriber. For example, if the subscriber selects a program that is not available, the DHCT 14 may request price criteria for other available viewing options and/or programs. Similarly, the DHCT 14 may request price criteria when the subscriber selects a particular feature such as pause or other random access functionality. It will be appreciated, however, that the pricing system may also transmit price criteria for each available viewing option to the DHCT 14 at predefined times or intervals. In this embodiment, the price criteria are preferably stored on the DHCT 14 and retrieved as necessary to provide pricing information for various viewing options.
According to another aspect of the present invention, the DHCT 14 contains a local storage device (not shown) such as a hard drive, either internally connected to the DHCT 14 or externally connected to the DHCT 14 via a storage device interface port (not shown) such as SCSI or IDE or a communication port (not shown) such as USB or IEEE-1394. In addition, the DHCT 14 may comprise a decryption subsystem and capabilities to decrypt encrypted VOD titles and prohibit replication of locally-stored VOD titles. The security processor 131 may be part of the decryption subsystem. The pricing system assigns a price criteria to allow the subscriber to receive the VOD title in encrypted fashion via the DHCT's DBDS interface 106 or OOB tuner 108 ahead of time at a lower bit rate and record and store the VOD stream in the DHCT's local storage device. The subscriber is offered full random access functionality. For an additional price, the subscriber is allowed to view the movie over an extended period of time upon which on expiration, the VOD client programmed application executing within DHCT 14 erases the encrypted movie from the storage device. Alternatively, for an additional price the subscriber is allowed to view the movie in its entirety for a finite number of repetitions. Since the movie is stored in the local storage device of the DHCT 14, additional viewings do not need to reflect a considerably higher price.
Patentzitate Zitiertes PatentEingetragen Ver�ffentlichungsdatum Antragsteller TitelUS36765801. Juni 197011. Juli 1972Video Information SystemsInterrogated transponder systemUS458615822. Febr. 198329. Apr. 1986International Business Machines Corp.Screen management systemUS47061216. Mai 198610. Nov. 1987Patrick YoungTV schedule system and processUS475157828. Mai 198514. Juni 1988David P. GordonSystem for electronically controllably viewing on a television updateable television programming informationUS48210975. M�rz 198711. Apr. 1989General Instrument CorporationApparatus and method for providing digital audio on the sound carrier of a standard television signalUS482725026. Okt. 19872. Mai 1989Tektronix, Inc.Graphics display system having data transform circuitUS488577521. Sept. 19845. Dez. 1989Scientific-Atlanta, Inc.Information display scheme for subscribers of a subscription television systemUS490871329. Juni 198813. M�rz 1990Levine Michael RVCR ProgrammerUS493015829. Aug. 198829. Mai 1990Vogel Peter SSelective video playing systemUS494918716. Dez. 198814. Aug. 1990Cohen Jason MVideo communications system having a remotely controlled central source of video and audio dataUS496399423. Febr. 199016. Okt. 1990Levine Michael RVCR programmerUS49841526. Okt. 19878. Jan. 1991Bell Communications Research, Inc.System for controlling computer processing utilizing a multifunctional cursor with decoupling of pointer and image functionalities in space and timeUS499101120. Apr. 19895. Febr. 1991Scientific-Atlanta, Inc.Interactive television terminal with programmable background audio or videoUS50382115. Juli 19896. Aug. 1991The Superguide CorporationMethod and apparatus for transmitting and receiving television program informationUS517241320. Dez. 199015. Dez. 1992SasktelSecure hierarchial video delivery system and methodUS525306630. Mai 199012. Okt. 1993Vogel Peter STV recording and viewing control systemUS529155419. Aug. 19921. M�rz 1994Tv Answer, Inc.Shared-price custom video rentals via interactive TVUS529335710. Sept. 19908. M�rz 1994The Superguide CorporationMethod and apparatus for controlling a television program recording deviceUS531739129. Nov. 199131. Mai 1994Scientific-Atlanta, Inc.Method and apparatus for providing message information to subscribers in a cable television systemUS53295908. Juli 199312. Juli 1994Uniden America CorporationAutomatic pay-per-view reception in a satellite receiverUS535312119. M�rz 19934. Okt. 1994Starsight Telecast, Inc.Television schedule systemUS53572761. Dez. 199218. Okt. 1994Scientific-Atlanta, Inc.Method of providing video on demand with VCR like functionsUS535936230. M�rz 199325. Okt. 1994Nec Usa, Inc.Videoconference system using a virtual camera imageUS537155129. Okt. 19926. Dez. 1994Logan; JamesTime delayed digital video system using concurrent recording and playbackUS53980712. Nov. 199314. M�rz 1995Texas Instruments IncorporatedFilm-to-video format detection for digital televisionUS54103264. Dez. 199225. Apr. 1995Goldstein; Steven W.Programmable remote control device for interacting with a plurality of remotely controlled devicesUS54103432. Apr. 199325. Apr. 1995Bell Atlantic Network Services, Inc.Video-on-demand services using public switched telephone networkUS541034422. Sept. 199325. Apr. 1995Arrowsmith Technologies, Inc.Apparatus and method of selecting video programs based on viewers' preferencesUS54144557. Juli 19939. Mai 1995Digital Equipment CorporationSegmented video on demand systemUS541862227. Okt. 199323. Mai 1995Sony CorporationApparatus for recording and reproducing audio and video signals in accordance with a broadcast scheduleUS544831315. Sept. 19945. Sept. 1995Thomson Consumer Electronics, Inc.On/off control of a cable converter unit by a VCRUS547726229. Nov. 199119. Dez. 1995Scientific-Altanta, Inc.Method and apparatus for providing an on-screen user interface for a subscription television terminalUS547926818. Febr. 199426. Dez. 1995Starsight Telecast Inc.User interface for television schedule systemUS548154210. Nov. 19932. Jan. 1996Scientific-Atlanta, Inc.Interactive information services control systemUS548327715. Dez. 19929. Jan. 1996Alcatel Network SystemsSimplified set-top converter for broadband switched networkUS549363813. Okt. 199420. Febr. 1996Digital Equipment CorporationRemote display of an image by transmitting compressed video frames representing back-ground and overlay portions thereofUS550881513. Sept. 199516. Apr. 1996Smart Vcr Limited PartnershipSchedule display system for video recorder programmingUS551295829. Apr. 199430. Apr. 1996Matsushita Electric Corporation Of AmericaSystem for controlling the effects of noise in television receiversUS551549529. Sept. 19927. Mai 1996Kabushiki Kaisha ToshibaIcon display apparatusUS552163125. Mai 199428. Mai 1996Spectravision, Inc.Interactive digital video services system with store and forward capabilitiesUS55307542. Aug. 199425. Juni 1996Garfinkle; NortonVideo on demandUS553273529. Apr. 19942. Juli 1996At&T Corp.Method of advertisement selection for interactive serviceUS553275411. Apr. 19942. Juli 1996Starsight Telecast Inc.Background television schedule systemUS554435418. Juli 19946. Aug. 1996Ikonic Interactive, Inc.Multimedia matrix architecture user interfaceUS55554412. Aug. 199410. Sept. 1996Interim Design Inc.Interactive audiovisual distribution systemUS555754121. Juli 199417. Sept. 1996Information Highway Media CorporationApparatus for distributing subscription and on-demand audio programmingUS55627326. Sept. 19958. Okt. 1996Eisenberg; Eric L.Hair graft support trayUS556827220. Okt. 199522. Okt. 1996Smart Vcr Limited PartnershipSchedule display system for video recorder programmingUS558356022. Juni 199310. Dez. 1996Apple Computer, Inc.Method and apparatus for audio-visual interface for the selective display of listing information on a displayUS558399530. Jan. 199510. Dez. 1996Mrj, Inc.Apparatus and method for data storage and retrieval using bandwidth allocationUS558582120. Dez. 199517. Dez. 1996Hitachi Ltd.Apparatus and method for screen displayUS55858385. Mai 199517. Dez. 1996Microsoft CorporationProgram time guideUS55898927. Juni 199531. Dez. 1996Knee; Robert A.Electronic television program guide schedule system and method with data feed accessUS559255119. Apr. 19947. Jan. 1997Scientific-Atlanta, Inc.Method and apparatus for providing interactive electronic programming guideUS559450922. Juni 199314. Jan. 1997Apple Computer, Inc.Method and apparatus for audio-visual interface for the display of multiple levels of information on a displayUS55985243. M�rz 199328. Jan. 1997Apple Computer, Inc.Method and apparatus for improved manipulation of data between an application program and the files system on a computer-controlled display systemUS56003642. Dez. 19934. Febr. 1997Discovery Communications, Inc.Network controller for cable television delivery systemsUS56005732. Dez. 19944. Febr. 1997Discovery Communications, Inc.Operations center with video storage for a television program packaging and delivery systemUS561494021. Okt. 199425. M�rz 1997Intel CorporationMethod and apparatus for providing broadcast information with indexingUS561924724. Febr. 19958. Apr. 1997Smart Vcr Limited PartnershipStored program pay-per-playUS561924914. Sept. 19948. Apr. 1997Time Warner Entertainment Company, L.P.Telecasting service for providing video programs on demand with an interactive interface for facilitating viewer selection of video programsUS562145622. Juni 199315. Apr. 1997Apple Computer, Inc.Methods and apparatus for audio-visual interface for the display of multiple program categoriesUS562361329. Nov. 199422. Apr. 1997Microsoft CorporationSystem for displaying programming informationUS562540520. Febr. 199629. Apr. 1997At&T Global Information Solutions CompanyArchitectural arrangement for a video serverUS562586430. Juni 199529. Apr. 1997Budow; Harry S.Interactive digital video services system with store and forward capabilitiesUS562973229. M�rz 199413. Mai 1997The Trustees Of Columbia University In The City Of New YorkViewer controllable on-demand multimedia serviceUS563169325. Okt. 199320. Mai 1997Antec CorporationMethod and apparatus for providing on demand services in a subscriber systemUS56326817. M�rz 199527. Mai 1997International Business Machines CorporationUniversal electronic video game renting/distributing systemUS563597927. Mai 19943. Juni 1997Bell AtlanticDynamically programmable digital entertainment terminal using downloaded software to control broadband data operationsUS56359804. Apr. 19953. Juni 1997Bell Communications Research, Inc.System and method for customer premises broadband interface with on-hook alertingUS563598913. Febr. 19963. Juni 1997Hughes ElectronicsMethod and apparatus for sorting and searching a television program guideUS565083117. Juli 199522. Juli 1997Gateway 2000, Inc.Adjustable power remote control driveUS56593502. Dez. 199319. Aug. 1997Discovery Communications, Inc.Operations center for a television program packaging and delivery systemUS56662933. Juli 19959. Sept. 1997Bell Atlantic Network Services, Inc.Downloading operating system software through a broadcast channelUS56714117. Juni 199523. Sept. 1997Intel CorporationMethod of searching an audio/visual programming database using selected criterion having implicit logical operationUS567575215. Sept. 19947. Okt. 1997Sony CorporationInteractive applications generator for an interactive presentation environmentUS568220625. Sept. 199528. Okt. 1997Thomson Consumer Electronics, Inc.Consumer interface for programming deviceUS568259715. Juni 199528. Okt. 1997International Business Machines CorporationHybrid video-on-demand based on a near-video-on-demand systemUS56849188. Sept. 19944. Nov. 1997Abecassis; MaxSystem for integrating video and communicationsUS56869546. Juni 199511. Nov. 1997Sony CorporationProgram information broadcasting method program information display method, and receiving deviceUS56873313. Aug. 199511. Nov. 1997Microsoft CorporationMethod and system for displaying an animated focus itemUS56896411. Okt. 199318. Nov. 1997Vicor, Inc.Multimedia collaboration system arrangement for routing compressed AV signal through a participant site without decompressing the AV signalUS569417629. Febr. 19962. Dez. 1997Hughes ElectronicsMethod and apparatus for generating television program guides with category selection overlayUS569454631. Mai 19942. Dez. 1997Reisman; Richard R.System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest listUS569910710. Apr. 199616. Dez. 1997Microsoft CorporationProgram reminder systemUS571516917. Jan. 19953. Febr. 1998Csk Research Institute Corp.Software rental method and apparatus, and circulating medium thereforUS571551519. Sept. 19943. Febr. 1998Scientific-Atlanta, Inc.Method and apparatus for downloading on-screen graphics and captions to a television terminalUS57218272. Okt. 199624. Febr. 1998James LoganSystem for electrically distributing personalized informationUS57218295. Mai 199524. Febr. 1998Microsoft CorporationSystem for automatic pause/resume of content delivered on a channel in response to switching to and from that channel and resuming so that a portion of the content is repeatedUS572189726. Juli 199624. Febr. 1998Rubinstein; Seymour I.Browse by prompted keyword phrases with an improved user interfaceUS572410627. M�rz 19963. M�rz 1998Gateway 2000, Inc.Hand held remote control device with trigger buttonUS57245213. Nov. 19943. M�rz 1998Intel CorporationMethod and apparatus for providing electronic advertisements to end users in a consumer best-fit pricing mannerUS572464615. Juni 19953. M�rz 1998International Business Machines CorporationFixed video-on-demandUS572706016. Juni 199310. M�rz 1998Starsight Telecast, Inc.Television schedule systemUS572954919. Juni 199517. M�rz 1998Bell Atlantic Network Services, Inc.Simulcasting digital video programs for broadcast and interactive servicesUS57322162. Okt. 199624. M�rz 1998Internet Angles, Inc.Audio message exchange systemUS57348532. Dez. 199331. M�rz 1998Discovery Communications, Inc.Set top terminal for cable television delivery systemsUS57370281. Nov. 19957. Apr. 1998International Business Machines CorporationPrevious channel listing with cursor controlled user interface for television video displaysUS574030410. M�rz 199714. Apr. 1998Sony CorporationMethod and apparatus for replaying recording medium from any bookmark-set position thereonNichtpatentzitateReferenz1"A Brief History of the Trailer," http://www.movietrailertrash.com/views/history.html, 11 pages (Publicly known at least as early as Dec. 20, 2003).2"Client User Interface Specification (Phase I) for Video-On-Demand Application Development on the Explorer 2000(TM) Digital Home Communications Terminal", Revision 1.10 (Aug. 31, 1998).3"Evidence of illustrative movie release years," Retrieved from the Internet Movie Database using Internet, http://www.imdb.com, 19 pages (Retrieved on Jun. 6, 2005).4"ISO/IEC 13818-6 Information technology-Generic coding of moving pictures and associated audio information-Part 6: Extensions for DSM-CC," Chapter 4, 113 pages (Sep. 1, 1998).5"Netcaster Developer's Guide," Devedge Online Documentation, Netscape Communications Corporation, http://developer.netscape.com/docs/manuals/netcast/devguide/ index.html, XP-002166370, 82 pages (Sep. 25, 1997).6"Netscape Navigator Help," Netscape Navigator Software User Documentation, Netscape Communications Corporation, http://home.netscape.com, XP-002166369, pp. 1-63 (Aug. 10, 1997).7"Sez You . . . origin of word daemon," Take Our Word For It, Issue 146, p. 4, http://www.takeourword.com/TOW146/page4.html (retrieved on Apr. 4, 2006).8"Client User Interface Specification (Phase I) for Video-On-Demand Application Development on the Explorer 2000™ Digital Home Communications Terminal", Revision 1.10 (Aug. 31, 1998).9"Industry Leading Software Vendors Endorse BroadVision's Next Generation of Retail and Business-To-Business E-Commerce Application Solutions," PR Newswire, Jun. 14, 1999, 4 pages.10"ISO/IEC 13818-6 Information technology—Generic coding of moving pictures and associated audio information—Part 6: Extensions for DSM-CC," Chapter 4, 113 pages (Sep. 1, 1998).11Addington, Timothy H., "System Architecture Specification for Video-On-Demand Application Development on the Explorer 2000(TM) Digital Home Communications Terminal", Revision 1.10r Review Copy (Mar. 4, 1999).12Addington, Timothy H., "System Architecture Specification for Video-On-Demand Application Development on the Explorer 2000™ Digital Home Communications Terminal", Revision 1.10r Review Copy (Mar. 4, 1999).13Alberico, G. et al., "Satellite Interactive Multimedia: A New Opportunity for Broadcasters," International Broadcasting Convention, Conference Publication No. 447, pp. 18-23 (Sep. 12-16, 1997).14ATI Multimedia Center 7.9, User's Guide, ATI Technologies Inc., pp. i-vi and 1-96 (Copyright 2002).15Barth et al., "10 Fernsehen am PC", Suse GMBH, XP-002324319, pp. 143-149 (2001).16BPAI Decision for U.S. Appl. No. 09/692,995, mailed Aug. 20, 2008.17BPAI Decision for U.S. Appl. No. 09/693,288, mailed Nov. 28, 2007.18Canadian Office Action cited in Application No. 2,376,556 mailed Dec. 6, 2005.19Canadian Office Action cited in Application No. 2,376,556 mailed Nov. 23, 2007.20Canadian Office Action cited in Application No. 2,376,556 mailed Sep. 30, 2008.21Canadian Office Action cited in Application No. 2,402,088 mailed Jun. 1, 2010.22Canadian Office Action cited in Application No. 2,402,088 mailed May 30, 2006.23Canadian Office Action cited in Application No. 2,405,491 mailed Apr. 3, 2009.24Canadian Office Action cited in Application No. 2,405,491 mailed Jan. 20, 2006.25Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 20, 2007.26Canadian Office Action cited in Application No. 2,405,491 mailed Jun. 9, 2010.27Canadian Office Action cited in Application No. 2,405,491 mailed May 22, 2008.28Canadian Office Action cited in Application No. 2,408,289 mailed Aug. 27, 2008.29Canadian Office Action cited in Application No. 2,408,289 mailed May 30, 2006.30Canadian Office Action cited in Application No. 2,408,289 mailed Sep. 2, 2010.31Canadian Office Action cited in Application No. 2,451,477 mailed Nov. 3, 2009.32Canadian Office Action cited in Application No. 2,451,477 mailed Oct. 20, 2010.33Canadian Office Action cited in Application No. 2,456,318 mailed Mar. 27, 2007.34Canadian Office Action cited in Application No. 2,456,318 mailed May 5, 2008.35Canadian Office Action cited in Application No. 2,456,318 mailed Nov. 17, 2010, 4 pages.36Canadian Office Action cited in Application No. 2,459,334 mailed Apr. 16, 2009.37Canadian Office Action cited in Application No. 2,459,334 mailed Mar. 4, 2011, 3 pages.38Canadian Office Action cited in Application No. 2,466,667 mailed Apr. 15, 2009.39Canadian Office Action cited in Application No. 2,475,723 mailed Jul. 7, 2009.40Canadian Office Action cited in Application No. 2,554,208 mailed Apr. 1, 2010.41Canadian Office Action cited in Application No. 2,621,605 mailed Dec. 15, 2009.42Cunningham et al., "5 Das X Window System"., Suse GMBH, XP-002324320, pp. 129-180 (2001).43Decision on Appeal affirmed cited in U.S. Appl. No. 09/590,434 mailed May 28, 2008.44Definition of "flag", Microsoft Press: Computer User's Dictionary, 3 pages (1998).45Definition of "renting", Webster's II: New College Dictionary, 1995, Houghton Mifflin Company, p. 939.46European Examination Report cited in Application No. 00 938 251.6 mailed Mar. 2, 2010.47European Examination Report cited in Application No. 00 938 251.6 mailed Nov. 2, 2007.48European Examination Report cited in Application No. 00 939 759.7 mailed May 10, 2007.49European Examination Report cited in Application No. 01 905 058.2 mailed Dec. 19, 2006.50European Examination Report cited in Application No. 01 922 261.1 mailed Jan. 24, 2007.51European Examination Report cited in Application No. 01 922 261.1 mailed Jul. 18, 2008.52European Examination Report cited in Application No. 01 922 261.1 mailed May 26, 2006.53European Examination Report cited in Application No. 01 922 261.1 mailed Nov. 2, 2007.54European Examination Report cited in Application No. 01 923 092.9 mailed Jul. 20, 2009.55European Examination Report cited in Application No. 01 923 092.9 mailed Nov. 27, 2008.56European Examination Report cited in Application No. 01 937 209.3 mailed Jun. 23, 2008.57European Examination Report cited in Application No. 01 937 209.3 mailed Mar. 16, 2010.58European Examination Report cited in Application No. 02 737 593.0 mailed May 6, 2009.59European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 28, 2007.60European Examination Report cited in Application No. 02 750 416.6 mailed Aug. 4, 2008.61European Examination Report cited in Application No. 02 761 572.3 mailed Apr. 20, 2009.62European Examination Report cited in Application No. 02 761 572.3 mailed Aug. 29, 2007.63European Examination Report cited in Application No. 02 761 572.3 mailed Jan. 22, 2008.64European Examination Report cited in Application No. 02 761 572.3 mailed Sep. 22, 2008.65European Examination Report cited in Application No. 06 802 683.0 mailed Jun. 26, 2008.66Examiner's Answer to Appeal Brief cited in U.S. Appl. No. 09/590,488 mailed Jan. 11, 2008.67Japanese Office Action cited in Application No. 2001-581527 mailed Feb. 10, 2010.68Japanese Office Action cited in Application No. 2001-581527 mailed Sep. 8, 2009.69Kevin, "Change Screen Resolution in Windows (Tips, Tricks, Tweaks, and Setting)," http://www.tacktech.com/display.cfm?ttid=207, pp. 1-3 (Oct. 26, 2002).70Leftwitch et al., "StarSight Interactive Television Program Guide-Functional/Interational Architecture Specification Document, Interaction Analysis and Design Project-Phase III," 36 pages.71Leftwitch et al., "StarSight Interactive Television Program Guide—Functional/Interational Architecture Specification Document, Interaction Analysis and Design Project—Phase III," 36 pages.72Little et al., "Prospects for Interactive Video-On-Demand", IEEE Multimedia, IEEE Service Center, New York, NY US, vol. 1 No. 3, Sep. 1994, pp. 14-24, XP000476885 ISSN: 1070-986X.73McFedries, "The Complete Idiot's Guide to Windows 95," Que, 2nd Edition, p. 49 (1997).74PCT Search Report and Written Opinion cited in International Application No. PCT/US2005/001812 mailed May 2, 2005.75PCT Search Report and Written Opinion cited in International Application No. PCT/US2006/033965 Feb. 19, 2007.76PCT Search Report and Written Opinion cited in International Application No. PCT/US2006/033965 mailed Feb. 9, 2007.77PCT Search Report cited in International Application No. PCT/US00/15952 mailed Jan. 16, 2001.78PCT Search Report cited in International Application No. PCT/US00/15963 mailed Sep. 1, 2000.79PCT Search Report cited in International Application No. PCT/US00/16000 mailed Oct. 2, 2000.80PCT Search Report cited in International Application No. PCT/US01/02490 mailed May 18, 2001.81PCT Search Report cited in International Application No. PCT/US01/06663 mailed Oct. 18, 2001.82PCT Search Report cited in International Application No. PCT/US01/10874 mailed Nov. 29, 2001.83PCT Search Report cited in International Application No. PCT/US01/14150 mailed Apr. 29, 2002.84PCT Search Report cited in International Application No. PCT/US02/20307 mailed Jan. 3, 2003.85PCT Search Report cited in International Application No. PCT/US02/20519 mailed Apr. 7, 2003.86PCT Search Report cited in International Application No. PCT/US02/24704 mailed Mar. 5, 2003.87PCT Search Report cited in International Application No. PCT/US02/28212 mailed Jan. 23, 2003.88PCT Search Report cited in International Application No. PCT/US02/36291 mailed May 23, 2003.89PCT Search Report cited in International Application No. PCT/US03/03391 mailed Jul. 14, 2003.90PCT Written Opinion cited in International Application No. PCT/US00/15952 mailed Jul. 25, 2001.91PCT Written Opinion cited in International Application No. PCT/US00/15963 mailed Jun. 22, 2001.92PCT Written Opinion cited in International Application No. PCT/US00/16000 mailed Oct. 25, 2001.93PCT Written Opinion cited in International Application No. PCT/US01/02490 mailed Oct. 23, 2001.94PCT Written Opinion cited in International Application No. PCT/US01/06663 mailed Jan. 3, 2002.95PCT Written Opinion cited in International Application No. PCT/US01/10874 mailed Jun. 4, 2002.96PCT Written Opinion cited in International Application No. PCT/US01/14150 mailed Sep. 30, 2004.97PCT Written Opinion cited in International Application No. PCT/US02/20307 mailed Aug. 8, 2003.98PCT Written Opinion cited in International Application No. PCT/US02/20519 mailed Apr. 6, 2004.99PCT Written Opinion cited in International Application No. PCT/US02/24704 mailed Nov. 20, 2003.100PCT Written Opinion cited in International Application No. PCT/US02/28212 mailed Dec. 4, 2003.101Petit et al., "Bandwidth Resource Optimization in Video-On-Demand Network Architectures", Community Networking Integrated Multimedia Services to the Home, 1994, Proceedings of the 1st International Workshop on San Francisco, CA USA, Jul. 1994, New York, NY USA, IEEE, Jul. 1994, pp. 91-97, XP010124402 ISBN: 978-0-7803-2076-5.102Reid, Dixie, "Coming attractions before they hit the big screen, most films begin life as a trailer," The Sacramento Bee, Sacramento, California, p. E.1 (Jul. 18, 1996).103Remote Wonder, ATI, Tweak 3D, pp. 1-5 (Sep. 30, 2002).104Reply Brief in U.S. Appl. No. 09/565,931 mailed on Sep. 17, 2007.105Rodriguez: Non-Final Office Action mailed Jan. 2, 2008, filing Nov. 4, 2004; U.S. Appl. No. 10/981,053.106Rodriguez: Non-Final Office Action mailed Oct. 27, 2007, filing date Dec. 18, 2003; U.S. Appl. No. 10/740,138.107Rottentomatoes web archived site, http://web.archive.org/web/20000301122211/http://rottentomatoes.com, Mar. 1, 2000, pp. 1-2.108Summons to attend oral proceedings in EP Application No. 01937209.3 mailed Mar. 21, 2011, 7 pages.109Summons to attend oral proceedings pursuant to Rule 115(1) EPC in European Application No. 02737593.0-1241 mailed May 28, 2010.110Supplementary European Search Report cited in European Application No. 02737593.0 mailed Mar. 3, 2009.111Supplementary European Search Report cited in European Application No. 02744705.1 mailed Feb. 19, 2010.112Supplementary European Search Report cited in European Application No. 02750416.6 mailed Jan. 2, 2007.113Supplementary European Search Report cited in European Application No. 02761572.3 mailed Mar. 20, 2007.114Supplementary European Search Report cited in European Application No. 02797096.1 mailed Oct. 14, 2005.115Supplementary European Search Report cited in European Application No. 03713364.2 mailed Jul. 6, 2005.116U.S. Appl. No. 09/330,792, filed Jun. 11, 1999 entitled "Series Reminders and Series Recording from an Interactive Television program Guide".117U.S. Appl. No. 09/378,533, filed Aug. 20, 1999 entitled "Electronic Program Guide with Advance Notification".118U.S. Appl. No. 09/518,041, filed Mar. 2, 2000 entitled "Apparatus and Method for Providing a Plurality of Interactive Program Guide Initial Arrangements".119U.S. Appl. No. 09/542,484, filed Apr. 3, 2000 entitled "System for Providing Alternative Services".120U.S. Appl. No. 09/565,931, filed May 4, 2000 entitled "Navigation Paradigm for Access to Television Services".121U.S. Appl. No. 09/590,434, filed Jun. 9, 2000 entitled "Video Promotional and Advertising Systems for Video on Demand System".122U.S. Appl. No. 09/590,488, filed Jun. 9, 2000 entitled "User Interface Navigational System with Parental Control for Video on Demand System".123U.S. Appl. No. 09/590,521, filed Jun. 9, 2000 entitled "Systems and Methods for Adaptive Scheduling and Dynamic Bandwidth Resource Allocation Management in a Digital Broadband Delivery System".124U.S. Appl. No. 09/590,904, filed Jun. 9, 2000 entitled "Program Information Searching System for Interactive Program Guide".125U.S. Appl. No. 09/591,356, filed Jun. 9, 2000 entitled "Future Program Options Menu System for Interactive Program Guide".126U.S. Appl. No. 09/692,920, filed Oct. 20, 2000 entitled "Media-on-Demand Title Indexing System".127U.S. Appl. No. 09/692,995, filed Oct. 20, 2000 entitled "Media-on-Demand Bookmark System".128U.S. Appl. No. 09/693,115, filed Oct. 20, 2000 entitled "Media Services Window Configuration System".129U.S. Appl. No. 09/693,288, filed Oct. 20, 2000 entitled "Media-on-Demand Rental Duration Management System".130U.S. Appl. No. 09/693,790, filed Oct. 20, 2000 entitled "Integrated Searching System for Interactive Media Guide".131U.S. Final Office Action cited in Serial No. 11/564,431 mailed Jan. 4, 2010.132U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 24, 2007.133U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 27, 2003.134U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Aug. 28, 2006.135U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jul. 7, 2008.136U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Oct. 20, 2004.137U.S. Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Sep. 15, 2005.138U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jun. 17, 2008.139U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 21, 2006.140U.S. Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 22, 2005.141U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 1, 2005.142U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jul. 14, 2009.143U.S. Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jun. 15, 2006.144U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Dec. 1, 2004.145U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Dec. 18, 2003.146U.S. Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 11, 2006.147U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 16, 2003.148U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Feb. 27, 2007.149U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jul. 10, 2006.150U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 30, 2005.151U.S. Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 7, 2004.152U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 11, 2005.153U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jan. 24, 2006.154U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Nov. 15, 2006.155U.S. Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Sep. 13, 2007.156U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Apr. 13, 2006.157U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jun. 30, 2005.158U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 10, 2004.159U.S. Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Sep. 26, 2003.160U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jul. 22, 2008.161U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 14, 2007.162U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 17, 2005.163U.S. Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jun. 21, 2006.164U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Apr. 26, 2004.165U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed May 3, 2005.166U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 21, 2005.167U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 4, 2009.168U.S. Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Sep. 8, 2006.169U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Feb. 9, 2004.170U.S. Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jan. 25, 2005.171U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Dec. 1, 2005.172U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 10, 2005.173U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 26, 2004.174U.S. Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Feb. 8, 2011, 28 pages.175U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jul. 25, 2008.176U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 16, 2006.177U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 19, 2007.178U.S. Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jun. 21, 2005.179U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Apr. 21, 2004.180U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jul. 26, 2004.181U.S. Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Jun. 3, 2005.182U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Dec. 31, 2007.183U.S. Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Sep. 17, 2009.184U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 29, 2005.185U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 3, 2009.186U.S. Final Office Action cited in U.S. Appl. No. 09/896,231 mailed May 28, 2010.187U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Aug. 7, 2008.188U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Oct. 5, 2007.189U.S. Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Sep. 18, 2006.190U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 24, 2009.191U.S. Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Nov. 6, 2008.192U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jan. 15, 2010.193U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 11, 2008.194U.S. Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Mar. 19, 2009.195U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Aug. 2, 2010.196U.S. Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Dec. 19, 2008.197U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Aug. 28, 2006.198U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jul. 25, 2008.199U.S. Final Office Action cited in U.S. Appl. No. 10/778,494 mailed May 22, 2007.200U.S. Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Oct. 2, 2008.201U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 23, 2009.202U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Dec. 26, 2008.203U.S. Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jul. 24, 2007.204U.S. Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Aug. 8, 2008.205U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 1, 2010.206U.S. Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 7, 2009.207U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 28, 2009.208U.S. Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jul. 31, 2008.209U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Aug. 6, 2008.210U.S. Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Jan. 21, 2010.211U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Dec. 1, 2006.212U.S. Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Jan. 26, 2006.213U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 16, 2010.214U.S. Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Mar. 9, 2009.215U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Feb. 1, 2010.216U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Jun. 9, 2011, 14 pages.217U.S. Final Office Action cited in U.S. Appl. No. 11/170,348 mailed May 28, 2009.218U.S. Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Dec. 22, 2008.219U.S. Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Aug. 31, 2010.220U.S. Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Aug. 18, 2010.221U.S. Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Sep. 17, 2009.222U.S. Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Jul. 29, 2009.223U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Feb. 13, 2009.224U.S. Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Mar. 18, 2010.225U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Apr. 1, 2009.226U.S. Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Jul. 22, 2010.227U.S. Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Jun. 23, 2010.228U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Dec. 1, 2009.229U.S. Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Sep. 14, 2010.230U.S. Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Aug. 20, 2010.231U.S. Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Apr. 14, 2010.232U.S. Final Office Action cited in U.S. Appl. No. 12/372,917 mailed May 17, 2010.233U.S. Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Jul. 6, 2010.234U.S. Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Nov. 9, 2010, 50 pages.235U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Apr. 28, 2010.236U.S. Final Office Action cited in U.S. Appl. No. 12/389,564 mailed May 19, 2011, 15 pages.237U.S. Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Jun. 10, 2010.238U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 22, 2005.239U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Apr. 4, 2006.240U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 11, 2004.241U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Feb. 6, 2007.242U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Jan. 10, 2008.243U.S. Non-Final Office Action cited in U.S. Appl. No. 09/518,041 mailed Mar. 18, 2003.244U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Apr. 1, 2004.245U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Dec. 7, 2007.246U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Jul. 28, 2005.247U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Mar. 12, 2007.248U.S. Non-Final Office Action cited in U.S. Appl. No. 09/542,484 mailed Sep. 7, 2006.249U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Feb. 13, 2009.250U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Jan. 11, 2006.251U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Oct. 28, 2009.252U.S. Non-Final Office Action cited in U.S. Appl. No. 09/565,931 mailed Sep. 10, 2004.253U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Apr. 22, 2004.254U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed May 23, 2003.255U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,434 mailed Nov. 21, 2005.256U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Dec. 20, 2005.257U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Jun. 10, 2003.258U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Nov. 16, 2004.259U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,488 mailed Oct. 26, 2006.260U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jul. 13, 2005.261U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Jun. 4, 2004.262U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed Mar. 26, 2007.263U.S. Non-Final Office Action cited in U.S. Appl. No. 09/590,904 mailed May 31, 2006.264U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Dec. 20, 2005.265U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed Jan. 14, 2004.266U.S. Non-Final Office Action cited in U.S. Appl. No. 09/591,356 mailed May 21, 2003.267U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Feb. 16, 2006.268U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Jan. 17, 2008.269U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 18, 2004.270U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,920 mailed Nov. 24, 2006.271U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Dec. 5, 2003.272U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Jan. 23, 2009.273U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Mar. 27, 2006.274U.S. Non-Final Office Action cited in U.S. Appl. No. 09/692,995 mailed Oct. 21, 2004.275U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Jun. 16, 2004.276U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,115 mailed Sep. 26, 2003.277U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 15, 2004.278U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jul. 19, 2005.279U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Jun. 21, 2010.280U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,288 mailed Oct. 27, 2003.281U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2005.282U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Dec. 28, 2006.283U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Jan. 15, 2008.284U.S. Non-Final Office Action cited in U.S. Appl. No. 09/693,790 mailed Oct. 6, 2004.285U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Dec. 29, 2004.286U.S. Non-Final Office Action cited in U.S. Appl. No. 09/881,516 mailed Oct. 28, 2003.287U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Feb. 4, 2009.288U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jul. 26, 2007.289U.S. Non-Final Office Action cited in U.S. Appl. No. 09/894,508 mailed Jun. 13, 2008.290U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Dec. 23, 2008.291U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Jun. 23, 2005.292U.S. Non-Final Office Action cited in U.S. Appl. No. 09/896,231 mailed Nov. 17, 2009.293U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Apr. 19, 2007.294U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Jan. 29, 2008.295U.S. Non-Final Office Action cited in U.S. Appl. No. 09/924,111 mailed Mar. 15, 2006.296U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Apr. 10, 2009.297U.S. Non-Final Office Action cited in U.S. Appl. No. 09/947,890 mailed Jun. 25, 2008.298U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Jun. 8, 2011, 26 pages.299U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Oct. 27, 2010.300U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 15, 2008.301U.S. Non-Final Office Action cited in U.S. Appl. No. 10/740,138 mailed Sep. 3, 2009.302U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Apr. 12, 2011, 20 pages.303U.S. Non-final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 21, 2010.304U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jan. 24, 2007.305U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jul. 18, 2007.306U.S. Non-Final Office Action cited in U.S. Appl. No. 10/761,777 mailed Jun. 11, 2009.307U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Dec. 29, 2004.308U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Feb. 2, 2007.309U.S. Non-Final Office Action cited in U.S. Appl. No. 10/778,494 mailed Jan. 16, 2008.310U.S. Non-Final Office Action cited in U.S. Appl. No. 10/783,235 mailed Feb. 25, 2008.311U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Apr. 27, 2010.312U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Apr. 29, 2011, 11 pages.313U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Feb. 9, 2007.314U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 17, 2008.315U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Jun. 26, 2009.316U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Nov. 4, 2010.317U.S. Non-Final Office Action cited in U.S. Appl. No. 10/934,253 mailed Sep. 14, 2006.318U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,849 mailed Apr. 30, 2008.319U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Apr. 30, 2008.320U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Oct. 15, 2008.321U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,854 mailed Sep. 28, 2009.322U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jan. 14, 2009.323U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed Jun. 30, 2010.324U.S. Non-Final Office Action cited in U.S. Appl. No. 10/957,942 mailed May 1, 2008.325U.S. Non-Final Office Action cited in U.S. Appl. No. 10/981,053 mailed Apr. 15, 2009.326U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed Aug. 23, 2005.327U.S. Non-Final Office Action cited in U.S. Appl. No. 10/994,599 mailed May 16, 2006.328U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Aug. 21, 2009.329U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Feb. 1, 2011, 33 pages.330U.S. Non-Final Office Action cited in U.S. Appl. No. 11/162,345 mailed Oct. 31, 2008.331U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Dec. 11, 2008.332U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Oct. 26, 2010.333U.S. Non-Final Office Action cited in U.S. Appl. No. 11/170,348 mailed Sep. 30, 2009.334U.S. Non-Final Office Action cited in U.S. Appl. No. 11/208,387 mailed Jun. 12, 2008.335U.S. Non-Final Office Action cited in U.S. Appl. No. 11/234,967 mailed Sep. 10, 2010.336U.S. Non-Final Office Action cited in U.S. Appl. No. 11/238,369 mailed Mar. 30, 2010.337U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Feb. 5, 2010.338U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Mar. 19, 2009.339U.S. Non-Final Office Action cited in U.S. Appl. No. 11/244,621 mailed Sep. 19, 2008.340U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed May 5, 2010.341U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Oct. 22, 2009.342U.S. Non-Final Office Action cited in U.S. Appl. No. 11/275,245 mailed Sep. 22, 2008.343U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Jun. 26, 2009.344U.S. Non-Final Office Action cited in U.S. Appl. No. 11/460,516 mailed Sep. 17, 2008.345U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Mar. 2, 2010.346U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 18, 2008.347U.S. Non-Final Office Action cited in U.S. Appl. No. 11/496,303 mailed Sep. 29, 2009.348U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Aug. 24, 2009.349U.S. Non-Final Office Action cited in U.S. Appl. No. 11/564,431 mailed Jul. 20, 2010.350U.S. Non-Final Office Action cited in U.S. Appl. No. 11/678,653 mailed Dec. 16, 2009.351U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,942 mailed Jun. 8, 2010.352U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,945 mailed Jul. 16, 2010.353U.S. Non-Final Office Action cited in U.S. Appl. No. 11/963,951 mailed Aug. 2, 2010.354U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Apr. 30, 2009.355U.S. Non-Final Office Action cited in U.S. Appl. No. 12/127,968 mailed Mar. 31, 2010.356U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,752 mailed Dec. 23, 2009.357U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,763 mailed Jan. 4, 2011, 18 pages.358U.S. Non-Final Office Action cited in U.S. Appl. No. 12/179,767 mailed Jan. 22, 2010.359U.S. Non-Final Office Action cited in U.S. Appl. No. 12/180,416 mailed Jun. 25, 2010.360U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,887 mailed Oct. 16, 2009.361U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,894 mailed Oct. 27, 2009.362U.S. Non-Final Office Action cited in U.S. Appl. No. 12/372,917 mailed Oct. 26, 2009.363U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,002 mailed Sep. 3, 2010.364U.S. Non-Final Office Action cited in U.S. Appl. No. 12/388,139 mailed Dec. 15, 2009.365U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,128 mailed Jun. 2, 2010.366U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Aug. 23, 2010.367U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Jan. 21, 2011, 13 pages.368U.S. Non-Final Office Action cited in U.S. Appl. No. 12/389,564 mailed Nov. 10, 2009.369U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,418 mailed Sep. 28, 2010.370U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,420 mailed Oct. 19, 2010.371U.S. Non-Final Office Action cited in U.S. Appl. No. 12/390,422 mailed Oct. 20, 2010.372U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Mar. 17, 2011, 20 pages.373U.S. Non-Final Office Action cited in U.S. Appl. No. 12/413,686 mailed Nov. 30, 2009.374U.S. Restriction Requirement cited in U.S. Appl. No. 11/162,345 mailed Jul. 3, 2008.375VESA Plug and Display Standard, Version 1, Video Electronics Standards Association, XP-002123075, 90 pages (Jun. 11, 1997).376W3C, Putting language attributes in HTML, www.w3.org.org/International/O-help-lang, 2 pages (Apr. 29, 1997). Referenziert von Zitiert von PatentEingetragen Ver�ffentlichungsdatum Antragsteller TitelUS8341667 *23. Juni 201025. Dez. 2012Philip Clifford JacobsAdvertising driven switched digital videoUS8472930 *14. M�rz 201125. Juni 2013Qualcomm IncorporatedMethods and apparatus for creation and transport of multimedia content flowsUS854404319. Juli 200524. Sept. 2013Qualcomm IncorporatedMethods and apparatus for providing content information to content serversUS86774316. Mai 201018. M�rz 2014Time Warner Cable Enterprises LlcTechnique for providing uninterrupted switched digital video serviceUS88237695. Jan. 20112. Sept. 2014Ricoh Company, Ltd.Three-dimensional video conferencing system with eye contactUS889316314. Mai 201318. Nov. 2014Cihan AtkinMethod and system for viewing moviesUS8909740 *9. Febr. 20109. Dez. 2014Amazon Technologies, Inc.Video session content selected by multiple usersUS8978079 *23. M�rz 201210. M�rz 2015Time Warner Cable Enterprises LlcApparatus and methods for managing delivery of content in a network with limited bandwidth using pre-cachingUS9009319 *18. Jan. 201214. Apr. 2015Rackspace Us, Inc.Optimizing allocation of on-demand resources using performanceUS90157835. M�rz 201021. Apr. 2015Time Warner Cable Enterprises LlcBandwidth conservationUS20110055002 *9. Nov. 20103. M�rz 2011Microsoft CorporationFunding information delivery using advertising revenueUS20110126244 *20. Nov. 200926. Mai 2011Time Warner Cable Inc.Policy management arbitration by service groupUS20110202659 *14. M�rz 201118. Aug. 2011Qualcomm IncorporatedMethods and apparatus for creation and transport of multimedia content flowsUS20110321088 *23. Juni 201029. Dez. 2011Cisco Technology, Inc.Advertising driven switched digital videoUS20130074127 *21. Sept. 201121. M�rz 2013Verizon Patent And Licensing Inc.Optimizing mobile electronic program guide deliveryUS20130185436 *18. Jan. 201218. Juli 2013Erik V. CarlinOptimizing Allocation Of On-Demand Resources Using Performance ZonesWO2013173272A2 *14. Mai 201321. Nov. 2013Atkin CihanMethod and system for viewing movies* Vom Pr�fer zitiertKlassifizierungen US-Klassifikation725/97, 725/93, 725/9, 725/95, 725/94, 725/96Internationale KlassifikationH04N7/173 UnternehmensklassifikationH04N21/2385, H04N21/6125, H04N21/6175, H04N21/26216, H04N21/4263, H04N21/6118, H04N21/4622, H04N21/6137, H04N21/6187, H04N21/47202, H04N21/2547, H04N21/47208 Europ�ische KlassifikationH04N21/472N, H04N21/61D5, H04N21/61D2, H04N21/2547, H04N21/61U3, H04N21/61U5, H04N21/462S, H04N21/2385, H04N21/426B3, H04N21/472D, H04N21/61D3, H04N21/262C1Juristische Ereignisse DatumCodeEreignisBeschreibung6. Apr. 2015FPAYFee paymentYear of fee payment: 419. Nov. 2014ASAssignmentOwner name: SCIENTIFIC-ATLANTA, LLC, GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:034299/0440Effective date: 20081205Owner name: CISCO TECHNOLOGY, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SCIENTIFIC-ATLANTA, LLC;REEL/FRAME:034300/0001Effective date: 2014111827. Juli 2009ASAssignmentOwner name: SCIENTIFIC-ATLANTA, LLC, GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:023012/0703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100316;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100323;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100504;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100518;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100525;REEL/FRAME:23012/703Free format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:23012/703Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100323;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100504;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100316;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:023012/0703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100525;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:23012/703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;US-ASSIGNMENT DATABASE UPDATED:20100518;REEL/FRAME:23012/703Effective date: 20081205DrehenOriginalbildGoogle-Startseite - Sitemap - USPTO-Bulk-Downloads - Datenschutzerkl�rung - Nutzungsbedingungen - �ber Google Patente - Feedback gebenDaten bereitgestellt von IFI CLAIMS Patent Services.