METHOD AND SYSTEM FOR PERFORMING NON-STANDARD MODE OPERATIONS

Abstract

Disclosed are methods and systems for controlling the playback and recording of television programming containing interactive applications. In particular, the disclosed methods and systems detail how “trick modes” can be handled when playing applications that are distributed with the television programming.

Claims

1. A method for controlling playback, by a receiver, of recorded audiovisual programming and executing an application, said method comprising: playing the recorded audiovisual programming stored on a storage device coupled with the receiver; detecting and launching an application included in said audiovisual programming; registering, within a registry of the receiver, rights of the application wherein the application comprises application code and the rights comprise information indicative of which trick modes can be used during the playback; executing the application, and receiving a trick mode request from a viewer and handling this request according to the rights.

2. The method of claim 1 comprising: receiving a viewer command indicating trick mode desired by a viewer; determining whether the trick mode is compatible with the application; and playing the recorded audiovisual programming in the trick mode if the trick mode is compatible with the application.

3. The method of claim 1, wherein the recorded audiovisual programming is paused when a viewer interacts with the application.

4. The method of claim 2, wherein the recorded audiovisual programming is paused when the viewer interacts with the application.

5. The method of claim 1, wherein the receiver comprises a playback driver having a playback state, the method comprising presenting a playback state associated with the playing of the recorded audiovisual programming to the application.

6. The method of claim 1, wherein the trick mode is selected from the group consisting of fast-forward, slow motion, rewind, jump, seek and pause.

7. The method of claim 1, wherein the recorded audiovisual programming is stored on a Personal Video Recorder (PVR) or network PVR.

8. The method of claim 1, wherein the application is an interactive application.

9. The method of claim 1, wherein the application registers which trick modes are compatible with the application.

10. The method of claim 9, wherein the application changes the trick modes that are compatible with the application as the application is played.

11. A receiver for playing recorded audiovisual programming and executing an application comprising: a storage device storing an audiovisual programming and an application included in said audiovisual programming; a system software to execute the application when it is detected in the audiovisual programming and register rights related to the application; a playback driver capable of playing audiovisual programming from the storage device; a registry that indicates which trick modes are available for an application; and an administrative component that determines what action to take when a trick mode is requested and to handle this request according to the rights in the registry.

12. The receiver of claim 11, wherein the trick mode is selected from the group consisting of fast-forward, slow motion, rewind, jump, seek and pause.

13. The receiver of claim 12, wherein the receiver comprises a recording device in a form of a Personal Video Recorder (PVR) or network PVR.

14. The receiver of claim 11, wherein the application is an interactive application.

15. The receiver of claim 12, wherein the application is an interactive application.

16. The receiver of claim 13, wherein the application is an interactive application.

17. The receiver of claim 11, wherein the administrative component determines an action selected from the group consisting of stopping the application, initiating the trick mode, and ignoring the request.

18. The receiver of claim 12, wherein the administrative component determines an action selected from the group consisting of stopping the application, initiating the trick mode, and ignoring the request.

19. The receiver of claim 13, wherein the administrative component determines an action selected from the group consisting of stopping the application, initiating the trick mode, and ignoring the request.

20. The receiver of claim 14, wherein the administrative component determines an action selected from the group consisting of stopping the application, initiating the trick mode, and ignoring the request.

Description

DESCRIPTION OF THE DRAWINGS

[0027] The invention can be understood by reference to the Detailed Description of the Invention when taken together with the attached drawings; wherein:

[0028] FIG. 1 is a functional block diagram of an interactive television system;

[0029] FIG. 2 is a diagram illustrating the structure of a carousel and corresponding data stream;

[0030] FIG. 3 is a flow diagram illustrating one method for controlling the playback of recorded programming that includes an interactive application;

[0031] FIG. 4 is a flow diagram illustrating an embodiment of the present method in the case where there is more than one event;

[0032] FIG. 5 is a flow diagram showing how a recording system can handle a request for recording content that includes an application;

[0033] FIG. 6 is a flow diagram showing a method for initiating playback of recorded applications;

[0034] FIG. 7 is a flow diagram illustrating the detection of an application in a system configured to receive a program as a data stream is shown;

[0035] FIG. 8 is a diagram showing how playback of programs containing applications can be controlled;

[0036] FIG. 9 is a flow diagram illustrating how playback of applications are handled;

[0037] FIG. 10 is a diagram illustrating how the system handles trick mode request signals;

[0038] FIG. 11 illustrates a first process for determining the time and offset relationship for a variably dripped stream;

[0039] FIG. 12 illustrates a second process for determining the time and offset relationship for a variably dripped stream; and

[0040] FIG. 13 illustrates a third process for determining the time and offset relationship for a variably dripped stream.

DETAILED DESCRIPTION OF THE INVENTION

[0041] Personal Video Recorders (PVR) allow viewers to record selected television programs on command. Viewer can then determine when to view the recorded programs. In addition, PVRs typically allow the viewer several features “trick” modes. On such trick mode is the ability to pause and rewind during the recording of a live broadcast. The recorded portion may then be viewed later or skipped to catch up to the real-time broadcast. Another possible use of the PVR is to record one television show while playing back another, previously recorded show. Typically, the PVR achieves these feats by recording compressed video signals on storage devices such as hard-disk drives so that they can be played back on command.

[0042] The storage devices are typically part of the viewers system. They can be integrated in the viewer's receiver/set-top box or they can be part of a separate component of the viewer's system. Alternatively, the storage device can be located at a remote location away from the viewer's location. A so called “network PVR” works by placing the storage device at a remote location, for example the location of a broadcaster. A user is then able to control playback by communicating with the broadcaster over a network. The recorded programming can be provided to the viewer through the network or through another medium. Many embodiments described herein make specific reference to PVRs located at the viewers location and integrated into the viewers set-top box. These embodiments are meant only to be exemplary. Many of the principles apply equally to network PVRs and other storage systems used for recording and controlling the playback of television programming.

[0043] Interactive television systems provide a means to deliver interactive content as well as ordinary television audio and video to a large number of subscribers. Programs broadcast by those systems may incorporate television audio and video, still images, text, data, locators, metadata, interactive graphics and applications, and many other components. The interactive applications of the interactive television signal may therefore include application code, data associated with the audio and video, control signals, raw data, internet addresses and many other types of information. Disclosed are systems and methods for integrating interactive programming into PVR systems.

[0044] Referring to FIG. 1, a functional block diagram of an interactive television system is shown. The interactive television system generally comprises a broadcast station 100 and a receiving station 102 coupled to the broadcast station 100 by a broadcast medium 104. In this figure, the broadcast medium 104 is depicted as a satellite transmission network. The broadcast medium 104 may, in other embodiments, comprise other transmission means such as cable, telco, MMDS (microwave) and terrestrial transmission media. Broadcast station 100 is coupled to a program source 102 which is configured to provide the data which forms the program. The program source 102 could also be an operations center which broadcasts the data to a cable headend.

[0045] Receiving station 106 includes a receiver which is preferably coupled to a recording device 108. Receiver 106 is typically implemented in a set-top box which is connected to a television 110. Alternatively, the receiving station 106 could be integrated into the television. The receiving station could also be a PC with the computer monitor substituting for the television. Alternatively, the television could be used for display of the primary program and the PC (or PDA, web phone, etc.) for playing the interactive application including code and data, commonly know as a “two box” configuration. In any event the present invention is operable and covers without limitation any receiving apparatus known in the art.

[0046] Receiving station 106 incorporates a control unit (e.g., a microprocessor,) a memory, and other components which are necessary to select and decode the received interactive television signals. Because the basic components and features of receiving stations 106 such as set-top boxes are known, they will not be discussed in detail here. Recording device 108 is a conventional personal video recorder (PVR), the operations of which are within the skill in the art.

[0047] Typically, set-top boxes are designed to provide the necessary interactive functionality at minimal cost. Consequently, they normally have a limited amount of memory and no mass storage devices (e.g., hard disk drives.) While the memory is sufficient to execute interactive applications, it is not adequate to store the applications for an indefinite period of time. Therefore, the applications do not normally remain in memory when they are not longer being executed.

[0048] Even if the memory of the set-top box were large enough to store some interactive applications, it might be too small to accommodate a program which includes large amounts of audio or video data, application code, or other information. In one embodiment of the present system, recording device 108 is coupled to the set-top box to provide sufficient storage to record programs that will not fit in the limited amount of memory in the set-top box. Recording device 108 may comprise any suitable storage device, such as a hard disk drive, a recordable DVD drive or optical disk drive. It can be internal to the set-top box, or it may be connected externally. Recording device 108 can be connected permanently or removably to the set-top box.

[0049] Interactive applications such as application code or content relating to an interactive television program can be retrieved at the receiving station 106 in many different ways as understood by one skilled in the art. The interactive content and/or code could already be resident in storage at the receiving station 106. The interactive content and/or code could be stored at the broadcast station 100 and broadcast to the receiving station 106 with or as part of the audiovisual primary program, as discussed in more detail below in relation to “carouselling”. Alternatively, the interactive content may be stored at a different location from the interactive code and when the interactive code is executed, the interactive content could be fetched from a server at the broadcast station 100, online information provider 112, home network, amongst other locations. For example, the interactive content could be stored at a server associated with an online information provider 112 (e.g., the Internet, Web, Intranet, public network, private network, etc.) and could be retrieved from the receiver station during the playing of an audiovisual program. For example, a program may include, or be accompanied by, triggers which when extracted are used by the receiving station 106 to access the interactive content and/or code. In one such embodiment, the triggers could be addresses or reference addresses for one or more sites on an online information provider network. At certain predetermined times or when received and extracted from a datastream at the receiving station 106, these triggers can be used to either automatically or upon user command establish a communications link with the online information provider 112 site for the retrieval of interactive program.

[0050] As referred to above, interactive applications can also be broadcast in a repeating format. In other words, each piece of information is broadcast a first time, then each is transmitted a second time, and so on. The cycle is repeated so that each piece of interactive data is transmitted, for example, every ten seconds. The pieces of information which are broadcast in this manner form what is referred to as a “carousel.” The sequence of information that makes up the carousel can be prepared in advance, or it can be determined “on the fly.”

[0051] Broadcast systems (e.g., interactive television systems) transmit information in a carousel format in order to allow receivers in the system to selectively obtain particular pieces of information in the carousel without requiring a return path from the receivers to the server. If a particular receiver needs a particular piece of information, it can simply wait until next time that piece of information is broadcast to obtain the information. If the information were not cyclically broadcast, the receiver would have to transmit a request for the information to the server, thus requiring a return path. Other receivers in the system can operate in the same manner, each receiver waiting for the information it needs, and then using only that information. By employing carousels to broadcast information, the system eliminates the need to connect each of the receivers with the server and further eliminates the need for the server to process individual requests for information.

[0052] In one embodiment, the data objects of a program which are to be broadcast from broadcast station to receiving station are stored at the same source as used to store the program. The data objects may be stored separately (e.g., as independently accessible files,) or they may be stored as a preconstruction data stream. If the data objects of the program are stored as individual files, they are retrieved by broadcast station from program source to be sequentially broadcast. If the program is stored as a preconstructed data stream, the stream can be broadcast essentially as it is stored. The program data may be compressed and control information may be added to the data for use by the interactive television system. The program data and any additional information is then converted by broadcast station to a format suitable for transmission over broadcast medium. In this particular embodiment, the data is formatted into packets which can be transmitted over a digital satellite network. These packets may be multiplexed with other packets for transmission.

[0053] Broadcast station transmits the data objects of the program in a carousel which is cyclical transmitted to receiving station. This produces a stream of data in which each data object is transmitted repeatedly. It should be noted that the broadcast medium (a digital satellite network in this embodiment) can support a number of different channels, and that different carousels (and corresponding data streams) can be concurrently broadcast on these channels. When receiving station receives the data stream, the program contained in the data stream may be played immediately or it may be recorded. If the program to be played immediately, receiving station converts the data stream back into the data objects and uses them as necessary in the program. If the program is to be stored, it may be parsed into the individual data objects and stored as a set of files, or it may be stored as a data stream, as it was received. If the program is to be stored, it is conveyed to a recording device. The program may be stored whether it is immediately played or not.

[0054] Referring to FIG. 2, the structure of a carousel (and a corresponding data stream) which is transmitted to the receiver is illustrated. Carousel 24 comprises data objects 21-23 and carousel information 20. Data objects 21-23 are retrieved from the same source as the program as described above. Carousel information 20 is provided by the broadcast station and may contain information such as the carousel ID and version number, the validity range of the carousel, a file access table or directory for the carousel, and various other information. (Portions of this information, such as validity range data, are not necessary in programs which are intended for immediate consumption.) The broadcast station transmits carousel information 20 and data objects 21-23 sequentially. The first instance of the transmission of carousel 24 is indicated by 25. After the broadcast station has completed transmission of the first instance of carousel 24, it is transmitted again, as indicated by 26. The successive, cyclical transmissions of carousel 24 indicated by 25-29 form data stream 30. Transmission of the carousel may be repeated indefinitely.

[0055] As mentioned above, the data objects which comprise a program may include application code, audio and video data, control signals, raw data and other types of information. If the program is to be immediately consumed (i.e., presented to the user,) the data must be parsed to extract the data objects from the stream. When the necessary data objects have been extracted, the program is played. The data objects are used as defined in the program. For example, any applications which need to be executed are launched, any audio or video data which needs to be presented to the user is played or displayed, any signals which need to be produced are generated, and so on. The program is presented to the user, typically via a television, and is consumed. Regardless of whether or not the program is immediately presented to the user, it can also be stored. The recording device can be used to store programs “as is” (i.e., as a data stream which is essentially the same as that received in the broadcast signal) or as a set of files that can be individually accessed or updated. In either case, the recorded program can be played back. The present system and method as employed to facilitate and/or enable the use of playback features such as trick play modes when viewing the recorded program. To illustrate the advantages of the system and method, it may be useful to examine the structure of a program.

Switching from Programming to Interactive Applications

[0056] FIG. 3 is a flow diagram illustrating one method for controlling the playback of recorded programming that includes an interactive application. The method is described with reference to an “audiovisual” program. However, the present invention is not limited to a program containing audio video content but could include any of the following, separately or in combination; audio, video, graphics, data, text, metadata, interactive application, locators, amongst other components.

[0057] Referring again to FIG. 3, and particularly with respect to the prerecorded program, after the program is recorded on a recording device, playback of the program is initiated at 300. If the interactive application is contained as part of pre-recorded program, the receiver is configured to detect applications in the recorded data at 302. The manner in which applications are detected in the program depends upon how the program was stored.

[0058] If the application was recorded as a data stream, the receiver detects an application by examining the sequential stream of data which is played back from the recording device. When the stream contains information indicating that the application is available, the receiver detects this information and thereby detects the application. The application is then launched at 304.

[0059] If the program was recorded as a set of files, the detection of applications in the program proceeds in a different manner. When playback of the program is initiated, the receiver examines the stored files. In one embodiment, the application files include information defining validity ranges for the corresponding applications. The receiver compares the validity range for each application to a current playback index. If the current playback index falls within the validity range of a particular application, that application is considered to have been detected, and is launched.

[0060] Alternatively, the interactive program could be wholly separate from the pre-recorded program. For example, a trigger could be detected in the pre-recorded program which would allow the interactive application to be accessed and launched according to one of the methods set forth above. For example, the interactive application, which could include code and data, could be stored in local storage at the receiver station, at the broadcast station, or at an online information provider site. If stored at this broadcast station, a request must be sent on the return path back to the broadcast station whereby the interactive application is accessed from a server, for example, and subsequently broadcast to the receiver station where it is detected and launched. In yet another embodiment, an icon or other indicator could be presented to the viewer indicating that an interactive application is available. Upon viewer command, the interactive application could be retrieved from local (i.e., storage within the receiver station) or external storage (storage remotely located from the receiver station including broadcast station or online information provider) and launched.

[0061] In another embodiment, several applications may reside on the receiver or on some other consumer electronics device attached to the receiver. In this case, the application to be launched, possibly automatically without even requiring user intervention, might be determined by the type of data in the stream. A typical example of such an application and associated data would be a web browser and some xml data.

[0062] Referring again to FIG. 3, when either the application is detected in the program or retrieved separately from internal or external storage, the interactive application is launched at 304. Once launched, the viewer may choose to interact with the presentation by selecting an option presented as part of the interactive application. For example, the viewer could select a possible answer to an interrogatory presented as part of a graphics overlay on a video program. For example, a commercial could be running and the viewer could respond affirmatively to an interrogatory presented on a graphics overlay asking if the user would like more information on the product presented in the commercial. Alternatively, an icon could be presented on the screen indicating to the viewer that enhanced content is available. The viewer could respond by any means known by those skilled in the art including without limitation depressing a key on a remote or keyboard, speaking a voice command to be processed by voice recognition component in the receiver station, amongst other ways.

[0063] Once the viewer command is detected by the system at 306, an interrupt could be sent to the interactive application. In other words, a control task or another native or broadcast process could receive notification of a key event that is directed to the interactive application. For example, in some systems, multiple applications may reside on the receiver. Some of those applications may execute natively (consisting of executable code for the particular processor in the receiver) whereas others of them may use an interpreter or virtual machine in which to execute. A control task is a particular type of application that can be furnished by the network operator or by the consumer electronics manufacturer. In either case, the primary objective of the control task is to decide matters of “policy.” Examples of decisions that could be made by a control task include (1) which events can be delivered to which other applications and which they will handle directly; (2) which applications will be allowed to access certain peripherals such as the tuner or modem; and (3) whether to terminate particular applications when resources are running short. These are just a few examples of the types of policies which a network operator and/or consumer electronics manufacturer may wish to establish via a control task. In any case, a control task may execute natively or inside an interpreter or virtual machine.

[0064] In FIG. 3, after detecting a viewer interaction a determination of whether the audio video program is a broadcast or recorded program is made at 308. If the audio video program is broadcast and currently played upon reception, a command is sent from the receiver station to the recording device to begin recording the audio video program at 310 if the broadcast program was not already being recorded in the recording device. If the broadcast program is continuing to be recorded, the read point of the location of the video and/or audio in the recording device where the viewer started interacting is maintained by the system.

[0065] Referring to FIG. 3 with respect to the broadcast program, a command is sent from the processor in the receiver station to the audio, video and/or data decoder to stop playing out the program at 312 resulting in the removal of the video from the screen and stopping the play of the audio content from the speakers. Of course, ceasing playback of the pre-recorded program from the recording device provides the same result of stopping the play of the program.

[0066] Any content, whether graphics, text, stills, voice and/or audio, associated with the interactive program preferably is continued to be played on the screen or speakers. The system preferably has a way to ensure that if the interactive application includes video or audio data that the content will continue to play, preferably without interruption. One way to ensure interactive play is through the use of metadata indicating which content should be “paused” and which content should continue playing for the viewer. Metadata can be associated with segments of content for use by the system. This metadata may be received at the receiver station as part of signaling information, as part of the content or as part of an application. Alternatively, a table, such as an Event Information Table, can be retrieved by the receiver station which indicates event states and control flow.

[0067] In an alternative embodiment, instead of pausing the program during user interaction with the interactive application, the program is played in a loop along with the interactive application. For example, if the interactive application appears during commercial programming, the commercial containing the application can continued to be played along with the application, when the commercial ends, the programming could be paused or the programming could be looped back to the beginning of the commercial and the commercial could be played again while the viewer interacts with the application.

[0068] Referring to FIG. 3, the next step 316 is to detect when the user stops interacting with the interactive application. This could be accomplished by the interactive application calling an exit routine or by receiving a command from the viewer indicating their intent to terminate the session. Typically, computer programs or applications can be written to be either finite in length or infinite (in case they sit in a loop waiting for a network signal, key depression, etc.) Finite applications typically end either with the programmer including a specific call to an exit routine or simply syntax that indicates the end of the application. In the latter case, when the program is compiled or interpreted, a run-time library is typically linked in which will call the exit routine. The exit routine is typically reflected to the operating system or middleware so that such can reclaim the resources that were being used by that application. With this invention, part of the process is involved within the operating system or middleware exit routine may be to resume a video, and/or other interactive application (see FIG. 4). An example where the viewer controls the exit would be the following. The viewer may be retrieving additional information about a product in a commercial from the interactive application. When completed, the interactive application can present a query or “termination” icon on the screen which the viewer could click on by depressing a key on a remote, for example. Another alternative would be to allow the viewer a certain time period to interact. If the viewer does not interact within such period, the system detects that a user has stopped interacting. It is understood as within the skill of the art that there are many ways for determining when a viewer has stopped interacting with the interactive application.

[0069] Referring again to FIG. 3, once the system detects the viewer has stopped interacting at 316, a command is sent to the recording device to retrieve the program. Preferably, the read point of the location of the video and/or audio in the recording device is maintained by the system. For example, the programming could then begin playing again on the screen from the same point where it was stopped (i.e., where the program was originally “paused”) at 318. Alternatively, the program could begin playing at any point automatically identified by control commands, by an event information table, or by viewer manipulated remote control which permits the viewer to select the portion of the recorded program to be viewed, for example.

[0070] The present invention also pertains to “nested recordings” as shown in FIG. 4, This is the case, for example, when a viewer interacts with an application accompanying a television program, then views a commercial and requests additional information about a product advertised in the commercial. After requesting the information, they may return either back to the commercial or the program, where the choice of where to return may be set by the network operator, the supplier of the content, the supplier of the software that runs on the receiver, or set as a default by a customer. For example, a viewer could be watching audiovisual program A at 400, which could include an interactive application. The viewer can choose to launch the interactive application at 402. When a new interactive program B is detected at 404, which, for example, includes an interactive application, it is launched and displayed to the viewer, perhaps in a picture-in-picture or side-by-side arrangement with program A.

[0071] At this point, the interactive application that accompanies program A can be “paused.” For example, the system may pause program A automatically when the viewer chooses to interact with the interactive application B at 406. When the viewer interaction is detected by the system at 406, the receiving station automatically ceases playing program A and effectively “pauses” program A, perhaps also pausing an application associated with Program A at 408. The viewer is now watching audio visual program B which contains another interactive application C, which is then launched at 410. If the viewer now indicates their desire to interact with interactive application C at 412, program B stops playing automatically at 414 and is effectively “paused.” The system now starts executing program C at 416. When the receiving station determines that the viewer stops interacting with interactive application C at 418, the play of either program A, program B or the interactive application accompanying program A can be automatically resumed and displayed on the screen for the viewer at the point where it was previously paused at 420.

Playback Options of Interactive Applications

[0072] Applications included in programming can pose a problem when the programs are recorded using, for example a PVR or other storage device. This is because some programs are designed to run only when originally broadcasted. In addition, systems may not be designed to handle special “trick” modes that are available during playback of recorded programming including applications.

[0073] FIG. 5 is a flow diagram showing how a recording system can handle a request for recording content that includes an application. As stated above, some applications do not allow for being run at any time other than their original broadcast time. Such applications should not therefore be recorded. According, the application's data may include an indicator as to whether the application is allowed to be recorded. If no such indicator exists, then even if someone requests that the application be recorded, it will not be. This indication can be included in the Carousel information 20 described above, or in other data in the stream. For instance, if the program was being broadcast using MPEG standard transport, a descriptor in the PMT could be used to signal that recording is allowed.

[0074] In FIG. 5 a request to record content that includes an application is made at 500. Software on the recording system then checks to determine whether recording the application is allowed at 502. If recordation of the application is not allowed, the system will not record the application at 504. Alternatively, the system can determine whether recording the application should nonetheless be allowed. The system may still, however, record the programming content without the application. If recordation of the application is allowed, the system records the application at 506.

[0075] FIG. 6 is a how diagram showing one method employed by the interactive television system described above for initiating playback of recorded applications. After the program is recorded on the recording device, playback of the program is initiated at 600. The receiver is configured to detect applications in the recorded data at 602. When an application is detected in the program, the application is launched at 604. The manner in which applications are detected in the program depends upon how the program was stored.

[0076] FIG. 7 is a flow diagram illustrating the detection of an application in a system configured to receive a program as a data stream is shown. If the application was recorded as a data stream, the receiver detects an application by examining the sequential stream of data which is played back from the recording device at 702. When the stream contains information indicating that the application is available, the receiver detects this information and thereby detects the application at 704. If the application is available it is launched at 706.

[0077] Whether the program was stored as a data stream or as a set of files, the detection of applications continues as the program is played back. Thus, as new application are detected, they are launched. It should be noted that the capabilities of the receiver and the policies implemented in the execution environment of the receiver determine the effect on a currently executing application of launching another application. Preferably, as described above, programming and other applications are paused when a new application is launched. It may or may not be necessary to unload the first application from memory while the second application is executing. If the receiver can simultaneously execute more than one application, then the second application may be launched while the first application continues to run. The receiver may, however, implement a policy which prohibits executing applications simultaneously. The receiver may therefore be required to kill or suspend the first application upon launching the second, even though the receiver is capable of executing both.

[0078] As mentioned above, when a user plays back a program, he or she may wish to use special playback modes rather than simply playing the program back sequentially (i.e., in a normal play mode.) The special modes include trick play modes, such as fast-forward, slow motion and rewind, and may also include jump, seek and pause features. When special play modes are used, the program moves from a first point at which an application is in a first state (e.g., showing a particular graphic) to a second point at which the application should be in a second state (e.g., showing a different graphic.) Because the portion of the program between the first and second points is not played (or executed,) certain signals and events which would normally cause an application to modify its state are not encountered. Care must therefore be taken to ensure that the behavior of the application resulting from use of the special play mode corresponds to the position in the program after the special play mode is stopped. In many cases, the author of the application will implement the application such that it is resilient to some or all of the trick modes, while other trick modes may cause undesirable behavior if not signaled.

[0079] FIG. 8 is a diagram showing how playback of programs containing applications can be controlled. Television programs with associated interactive applications are stored on the recording device 800 for playback at the viewer's convenience. System software 802 implements all the functions normally associated with this type of device, such as controlling drivers for peripheral devices and subsystems, as well as implementing the operating system, FIG. 8 illustrates three special sub-components, namely the playback driver 804 which controls the playback of the content, a registry 808 that maintains information about the capabilities of the application 806, and, an administrative component 810 that handles policy decisions for the system. The administrative component 810 can be implemented in several ways including as an application, as a 3rd party extension to the system, or built into the system itself. The application 806, in conjunction with the system software 802, registers its capabilities and rights.

[0080] The registered capabilities include what trick modes it is able to handle at the moment. This can be implemented as a static mechanism where the information is stored in the description of the application (in the Carousel information 20 described above, or in other data in the stream. For instance, if the program was being broadcast using MPEG standard transport, a descriptor in the PMT can be used to signal that recording is allowed.) In this case the capabilities are read by the system and registered accordingly. Alternatively (or in addition to the static mechanism), this can be a dynamic process where the application can, as it runs, change what trick modes it is prepared to handle by using an interface provided by the system to change the current capabilities. So it might never handle rewind, and only handle fast-forward through certain parts of the program. This dynamic change in behavior can be applied to all special playback modes available in the system.

[0081] The rights registered with the system include whether or not it has the right to handle requests from the viewer to perform trick modes. Generally the viewer will indicate that they want to fast-forward by pressing a “fast-forward” key on their remote (although other mechanisms are possible). The signal that the viewer pressed that key could be processed in two ways—either the system handles it, invoking the trick mode accordingly, or the signaled key press can be passed on to the application to let the application do what it wants with it (which may not be to fast-forward the recorded program). The former provides consistency of behavior, while the latter give the application the ability to enhance the behavior of the system. Since many broadcasters have a strong interest in consistency, they may want to maintain control of what applications process trick mode requests, so the ability to process such signals is a right that is granted to applications.

[0082] The registration of this right with the system can be implemented in several ways. It can be described in the Carousel information 20 described above. See U.S. Pat. No. 5,625,693, “Apparatus and method for authenticating transmitting applications in an interactive TV system,” incorporated here in its entirety by reference for all it teaches, for a description of defining applications permissions in a signed application directory. Alternatively, the application can register a credential that authorizes the application. See U.S. Pat. No. 6,148,081, “Security model for interactive television applications,” incorporated here in its entirety by reference for all it teaches, for a description of using credentials to establish rights. Alternatively, the rights could resident in memory on the STB. For example, they could be distributed by the Conditional Access System normally used to control access to Premium pay services such as HBO or Pay-per-view movies. Furthermore, if an application has the right to handle these signals, it still may not desire to handle them all the time, so an additional step may be employed where an authorized application makes a request to the system to send trick mode requests signals to the application, and can later request that the system resume handling those signals itself.

[0083] FIG. 8 shows the playback driver 804 in communication with the application 806, again in conjunction with the system software 802. At fixed intervals or at instances of state changes, and at other times of its choosing, the drier 804 will send a message to the application 806 concerning its current state. Illustrative messages might be, for example, “Normal Play”, “Fast-forward”, “Fast-forward 10×”, “Stopped”, etc.

[0084] The administrative component 810 may also override the capabilities of the application 806 based on its own criteria. For example, some features may be disabled at different times, such as, the application 806 may register that it is fast-forward capable, but the administration 810 may register that it wants the playback driver 804 to disallow that feature for some reason.

[0085] FIG. 9 is a flow diagram illustrating how playback of applications are handled. First, playback is initiated at 900 and an application is launched at 902. After playback is initiated, a starting sit of capabilities of the application are registered at 904. Execution of the application then begins. During its continued execution at 906, the application will receive, via any of several methods (interrupt, polling, shared memory, etc.), messages from the playback driver concerning its state, The actions taken by the application will vary depending on the effect desired by the author. For example, some applications may choose to remove all graphical overlays from the screen during a Fast-forward Operation, and may not redisplay overlay elements after Normal play resumes and new data is acquired from the stream. Alternatively, a different type of application may be designed predominately for use during Trick play during which most “normal” applications cannot provide meaningful applications. For example, consider a Fast-forward book-marking application, where in the user watches a TV program during Fast-forward, hitting select when the fast-forward video content is “interesting.” Information sent to the application by the Playback Driver, concerning the speed of playback, the position of the PlayBack Index, etc. could be used to build a bookmark list, possibly in conjunction with other MetaData in order to rapidly move from marked scene to marked scene. For example, previewing an entire football game in FastMotion, marking the proximate positions of all long pass plays is possible. When combined with MetaData of the precise times when play begin and end, an application could prepare a playlist of the long-pass plays.

[0086] It should be pointed out that some applications may depend on live data reception to maintain state. When a special playback mode is used to cause an application to move to a particular point in the playback of the program, precautions may be taken to ensure the application is in the appropriate state after the program returns to a normal playback mode. This can be addressed for two different cases: cases in which applications were authored with the intent that they would be recorded and played back; and cases in which applications were not intended to the recorded and replayed.

[0087] In the first case, an application is produced with the knowledge that it maybe recorded and played back using special y mode& Such an application is designed to accept notifications of these special play modes and to accommodate them. For example, an application can be configured to generate a query to determine the current position in the playback of the program. The application could then set its internal state according to the position in the program. In the second case, and application is produced with the intent that it should be consumed as it is received. The application is not designed to jump from one position to another in the program except as the program progresses in a normal play mode. In either case, a request for a trick mode not currently handled by the application may occur.

[0088] FIG. 10 is a diagram illustrating how the first case is handled. First, the viewer requests a trick mode at 1000. The system then determines if the application has the right to handle trick mode request signals (key presses) and if it has requested them at 1002. If so, the signal is sent to the application at 1004, and it is up to the application to handle the situation. If the system is handling the trick mode signals, it determines if the application can currently handle the specific trick mode requested at 1006. If it can, the request is processed normally at 1008, if the application has registered that it cannot currently handle the trick mode, then the administrative component is informed of the decision and is allowed to take appropriate action at 1010. Options 1012 for the administrative component include (but are not limited to): killing the application and letting the trick mode occur, allowing the application to run and ignoring the trick mode request, and letting the trick mode occur but allowing the application to continue to run. If the administrative component does kill the application it further has the option to restart the application once the trick mode is exited.

[0089] The application may be allowed to save information (e.g., state information) to persistent storage such as the recording device when it is terminated. It should be noted that the application may be removed from memory when it is terminated, so it may have to be downloaded again from the data stream and restarted after the program has jumped to the new position.

Recording Variable Rate Streams

[0090] Programming streams can be transmitted at variable rates depending upon the available bandwidth. When viewing the programming as it is broadcasted this does not become a problem because the system can play back the streams at a constant frame rate. However, when the streams are recorded before playback on a PVR or other recording devices, the variable rate of the streams can pose problems during playback. Specifically, playback on PVRs often uses trick modes that allow a user to skip ahead or back in the broadcast a predetermined amount or play the streams fast-forward or reverse. To use trick modes with variable rate content metadata that indicates a correspondence between play-time and location of the data on the recording media is typically required.

[0091] This metadata can be generated in a variety of manners as described below with reference to FIGS. 11-13.

[0092] FIG. 11 illustrates a first process for determining the time and offset relationship for a variably dripped stream. The system shown in FIG. 11 includes transmission equipment 1100 and receiving equipment 1102. For the example shown in FIG. 11, three streams of data (A,B,C) are being dripped to a population of PVR's over a broadcast network. The Table of T's and O's is dripped to receivers along with each video program. FIG. 11 depicts a case were the Table 1104 is sent in its entirety prior to trickling the videos. However, it should be understood that the Table 1104 could be dripped slowly as well. Furthermore, for simplicity, FIG. 11 shows a single table 1104 for all three streams; however, the Table 1104 could have several T,O pairs, one for each stream, or multiple Tables could be sent. The Table is prepared by the Analysis Engine 1106, which calculates indices at the server side that provide a correspondence between normal play time and depth (e.g., in bytes) into either the individual streams (video, audio, etc.) into a mixed transport/program stream that is going to be dripped. In addition to time and offset calculations, the table may also include other information about the programming content. For example, the table may also include the parental rating of the content. The system could then block recording and/or playback of data that the viewer is not authorized to view. Note that the stream is generally dripped with the express purpose of being recorded for later use, so the broadcaster knows for which streams they want to calculate this information. This correspondence (e.g., the tables) is broadcast as meta-data along with the transport/program stream. It is also possible to send the tables separately through a return channel. Preferably, the tables are broadcast by sending the information first or sending it last, by “dripping” the table information by multiplexing it with the three streams of data at 1108.

[0093] On the set-top box at the receiver side, the dripped a/v/d/md (streamed data) 1110 is received, demultiplexed 1112, and recorded on a storage device 1114. At this time, a correspondence between depth into respective individual streams, or a mixed transport program stream and location on the recording media is maintained. The broadcast correspondence between playtime and depth 1116 is also recorded on the recording media. Note that the recorded mixed transport/program stream need not be identical to the original broadcast one. It is also noted that the data need not be stored on the recording media contiguously, e.g., something similar to (paged, segmented) virtual memory tables could be used. When trick modes, e.g., fast-forward, rewind, etc., are requested, the normal playtime to which to jump is determined. Thereafter, the depth is looked up, and using the depth, the location is determined and the content is fetched. In an alternative embodiment, the receiver could also pull the Table information from an on-line server over a 2-way communications link (not shown). It should be noted that the Table could be in a different format than described above. For example, a hash structure could be used, as well as other known data structures.

[0094] FIG. 12 illustrates a second process for determining the time and offset relationship for a variably dripped stream. The structure is the same as in the embodiment shown in FIG. 11. In this embodiment, however, the Analysis Engine 1106 is replaced by a Playback Timestamp Engine 1200. This component creates a timestamp packet that is multiplexed and dripped along with the video programs 1202, and the data within the packet is used to create the T,O pairs at the receiver side 1204. If interactive applications are included with the video programs in the broadcast streams, preferably, the interactive applications are also time stamped.

[0095] The embodiment illustrated in FIG. 12 includes broadcasting intermixed within the program data (the individual streams or mixed transport/program stream), and time stamp information that indicated the normal play time of the data it is being mixed with. Two alternative methods of performing this method include a) ensuring that one of the individual streams includes program clock reference (PCR) information in its packets, or b) including an additional stream (a separate packet id (PID) when using MPEG transport) into a program designated to maintain the normal play time. In the latter case, that stream is multiplexed into the other streams frequently enough to ensure a quality mapping of the correspondence between normal play time and offset into the other stream data, but no so frequently that the overhead of collecting the information is problematic. For example, on MPEG based streams, it is necessary to ensure that packets that include the time base occur frequently in the mix.

[0096] On the set-top box, as the dripped a/v/d/md is received and recorded, whenever content is detected that includes time base information, an entry is added to the mapping from normal play time and offset into the stream data as it is saved. If the separate stream approach is used with MPEG transport, them is usually hardware that is able to filter on the PID of the time base stream and assist in collecting the data.

[0097] When trick modes are requested, the normal playtime in which to jump is determined by the system. Thereafter, the depth is looked up, and using the depth, the location is looked up and the content is fetched.

[0098] FIG. 13 illustrates a third process for determining the time and offset relationship for a variably dripped stream. The structure of this embodiment is similar to the embodiments in FIGS. 11 and 12. In this embodiment, the algorithms run at the encoder can also be run at the receiver, directly or an equivalent thereto. In the third embodiment, the PVR stores the dripped program, and subsequently performs an analysis phase to build the Table. One way to perform this function is as follows. The dripped program is recorded. When the set-top box (note: as always, the set top box components and functionality could be built into the television or other consumer electronic (CE) device) is not busy, it could “play” A/V at the normal rate (though not display on the television) for purposes of calculating the correspondence between normal play time and location on the recording media to build a table 1300. Then, the correspondence could be used for trick modes. Other methods of building the table at the receiver side could also be implemented.

[0099] In alternative embodiments of the invention, if the stream is missed during recording because the viewer switched channels briefly or due to broadcast errors, the missing part could be requested later over a return channel or could be obtained from a scheduled re-broadcast, when the television was off, for example.

[0100] In still further alternative embodiments, the receiver could play back (during “off times”) the video at normal speed while not presenting it on the display. In this way, the correspondences are computed using special purpose hardware to mark certain time increments in the video, for example. This may overcome the disadvantage of having to play back (at least a portion of) the video before trick mode becomes usable.

[0101] The many features and advantages of the invention are apparent from the detailed specification and, thus, it is intended by the appended claims to cover all such features and advantages of the invention that fall within the true spirit and scope of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation illustrated and described, and accordingly all suitable modifications and equivalents may be resorted to, falling within the scope of the invention.