Media streaming with enhanced seek operation

Abstract

The present disclosure relates to playback of video/audio streaming media data. The media stream is available from the network at multiple bit rates. When a seek operation is performed, a playback device requests a lower bit rate media stream in order to quickly fill a playback buffer so that playback can commence more readily. After a seek start-up period is complete, the playback device can return to downloading the media stream associated with higher bit rates in order to increase the quality of the playback.

Description

BACKGROUND

With the increasing popularity of playing streaming audio and video over networks such as the Internet, there is a need for optimizing the data transferred from a server to a client such that the client's experience is maximized even if network conditions during playback are inconsistent. Optimizing the client's experience involves making encoding decisions such that the video can be transferred and reconstructed with a minimal number of errors.

The term “streaming” is typically used to indicate that the data representing the media is provided by a host computer over a network to a playback device (i.e., a media playback computer implemented as any of a variety of conventional computing devices, such as a desktop PC, a notebook or portable computer a cellular telephone or other wireless communication device, a personal digital assistant (PDA), a gaming console, etc.) The client computer typically renders the streaming content as it is received from the host, rather than waiting for the entire file to be delivered.

The quality level is generally dictated by the bit rate specified for the encoded audio or video portions of the input stream. A higher bit rate generally indicates that a larger amount of information about the original audio or video is encoded and retained, and therefore a more accurate reproduction of the original input audio or video can be presented during video playback. Conversely, a lower bit rate indicates that less information about the original input audio or video is encoded and retained, and thus a less accurate reproduction of the original audio or video will be presented during video playback.

Generally, the bit rate is specified for encoding each of the audio and video based on several factors. The first factor is the network condition between the server and the client. A network connection that can transfer a high amount of data indicates that a higher bit rate can be specified for the input video that is subsequently transferred over the network connection. The second factor is the desired start-up latency. Start-up latency is the delay that a video playback tool experiences when first starting up due to the large amount of data that has to be received, processed, and buffered. Start-up latency can also occur after a seek operation, where the user selects variable positions in the streaming content to view. A third factor is the processing capabilities of the playback device. The fourth factor is the tolerance to glitching. Glitching occurs when the content is not displayed at the rate it was authored causing the playback device to run out of data to display. In most cases any amount of start-up latency or glitching is intolerable, and it is therefore desirable to optimize the bit rate specified such that the start-up latency and the glitching are minimized or eliminated.

SUMMARY

The present disclosure relates to playback of video/audio streaming media data. The media stream is available from the network at multiple encoded bit rates. When a seek operation is performed, a playback device can request a lower bit rate media stream in order to quickly fill a playback buffer so that playback can commence more readily. After a seek start-up period is complete, the playback device can return to downloading the media stream encoded at higher bit rates in order to increase the quality of the playback.

The foregoing and other objects, features, and advantages of the invention will become more apparent from the following detailed description, which proceeds with reference to the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary environment suitable for sending streaming media content over a network from a host device to a playback device.

FIG. 2 illustrates an example encoder on the host device.

FIG. 3 illustrates an example media stream having multiple, fixed hit rates.

FIG. 4 illustrates an example media stream having multiple, variable bit rates.

FIG. 5 illustrates an example application for rendering streaming media content on the playback device wherein a heuristics module is in the same application as a media pipeline.

FIG. 6 illustrates an example application for rendering streaming media content on the playback device wherein the media pipeline is in a platform and the heuristics module is in a downloadable (e.g., plug-in) program.

FIG. 7 illustrates an exemplary computing environment.

FIG. 8 illustrates an exemplary media pipeline on the playback device.

FIG. 9 illustrates a detailed view of a downloadable program coupled to a network.

FIG. 10 is a flowchart of a method to ensure fast start-up after a seek operation.

FIG. 11 is a flowchart of a method for fast ramp-up of a hit rate after a seek operation.

FIG. 12 is a detailed flowchart of a method for implementing playback after a seek operation.

FIG. 13 illustrates using thumbnails in cooperation with a seek operation.

DETAILED DESCRIPTION

As used in this application and in the claims, the singular forms “a,” “an” and “the” include the plural forms unless the context clearly dictates otherwise. Additionally, the term “includes” means “comprises.” Although the operations of some of the disclosed methods and apparatus are described in a particular, sequential order for convenient presentation, it should be understood that this manner of description encompasses rearrangement, unless a particular ordering is required by specific language set forth below. For example, operations described sequentially can in some cases be rearranged or performed concurrently.

Any of the methods described herein can be performed (at least in part) using software comprising computer-executable instructions stored on one or more computer-readable media. Furthermore, any intermediate or final results of the disclosed methods can be stored on one or more computer-readable media. It should be understood that the disclosed technology is not limited to any specific computer language, program, or computer. For instance, a wide variety of commercially available computer languages, programs, and computers can be used.

FIG. 1 illustrates an exemplary environment 100 which can be suitable for transmitting media content being streamed over a network 106 from a host computer device 102 to a playback computer device 104. The network 106 can be any of a variety of conventional network topologies and types (including optical, wired and/or wireless networks), using a variety of conventional network protocols (including public and/or proprietary protocols). The network 106 can include, for example, a home network, a corporate network, or the Internet, as well as possibly at least portions of one or more local area networks (LANs) and/or wide area networks (WANs) or telephone networks.

A host device 102 generally stores media content and streams media content to the playback device 104. The playback device 104 can receive streaming media content via the network 106 from host device 102 and plays it for a user. Additionally, the playback device 102 can request a desired bit rate from the host device, which offers multiple bit rates to download. Host device 102 may be implemented as any of a variety of conventional computing devices, including, for example, a desktop PC, a notebook or portable computer, a workstation, an Internet appliance, and combinations thereof. Playback device 104 may also be implemented as any of a variety of conventional computing devices, including, for example, a desktop PC, a notebook or portable computer, a workstation, an Internet appliance, a gaming console, a handheld PC, a cellular telephone or other wireless communications device, a personal digital assistant (PDA), a set-top box, and combinations thereof.

Host device 102 can make any of a variety of data available for streaming to playback device 104, including content, such as audio, video, text, images, animation, and the like. However, as used herein with respect to the exemplary embodiments described below, media content is intended to represent audio/video (A/V) content or just video content. Furthermore, references made herein to “media content”, “streaming media”, “streaming video”, “video content”, and any variation thereof are generally intended to include audio/video content. The term “streaming” is used to indicate that the data representing the media content is provided over a network 106 to a playback device 104 and that playback of the content can begin prior to the content being delivered in its entirety.

FIG. 2 illustrates an exemplary encoding tool 200 that can be implemented on the host device 102. The tool includes a segmenter 210 that accepts input video 205 and splits the input video into a plurality of segments each comprising a certain number of frames. Input video generally refers to a stream comprising both audio components and video components. In certain embodiments, the segments each comprise 60 frames. In other embodiments the segments can vary across a range of values such as comprising between 30 frames to 90 frames. The number of frames in the segment can be based on factors such as scene changes in the input video 205. For example, if a segment contains a scene change, the frames before the scene change could be drastically different than the frames after the scene change.

The segmenter 210 outputs the segments to a bit rate controller 215. The bit rate controller 215 analyzes each segment and selects bit rates for one or more bit rate layers for each of the segments. A bit rate layer is a layer comprising a specific bit rate used to encode the input video 205. The number of bit rate layers and their respective bit rates for each segment may be affected by factors associated with the segment such as the number of frames in the segment or the complexity of the input video 205 in the given segment. Additionally, the number of bit rate layers and their corresponding bit rates may be affected by factors not associated with the given segment such as limits on the size of the file or the maximum or minimum bandwidth of the network that the encoded input video 205 will be transferred through. In one embodiment, the bit rate controller 215 selects the bit rates for the bit rate layers for each of the segments independently from each of the other segments. Thus, a given segment may be encoded at the same or different bit rates as any other segment.

The segmenter 210 also outputs the segments to an encoder 220, and the bit rate controller 215 signals the bit rate layers for each segment to the encoder 220. The encoder 220 can encode according to a Windows Media Video or VC-1 format, MPEG-x format (e.g., MPEG-1, MPEG-2, or MPEG-4), H.26x format (e.g., H.261, H.262, H.263, or H.264), or other format. The encoder 220 may also be able to encode according to one or more audio standards such as WAV, FLAC, MP3, WMA, or some other standard. In some embodiments the encoder 220 encodes each segment as each bit rate layer and outputs a series of chunks in an encoded bit stream 225. Generally speaking, a chunk is a segment encoded as a particular bit rate layer. Thus, the encoder 220 can produce one or more chunks for each segment. In other embodiments, the encoder may encode the segment with less than all of the available bit rate layers. This may occur if, for example, a user defines a certain amount of time available for encoding, or conditions make certain bit rate layers un-necessary or undesirable.

As is well-understood in the art, the embodiment of FIG. 2 can be modified to encode a continuous media stream that is not divided into chunks. It is, however, desirable to be able to extract portions of the continuous media stream and to be able to logically define different portions of the media stream for extraction, if desired.

In certain embodiments, the encoding tool 200 may include a splitter (not shown) that splits the input video 205 into a separate video component and an audio component. In these embodiments, a separate segmenter, hit rate controller and encoder can be used to encode each of the video component and the audio component. The encoder for the video component can encode according to WMV or VC-1 format, MPEG-x format, H.26x format, or some other format. The encoder for the audio component can encode according to WAV, FLAC, MP3, WMA, or some other standard. Additionally, the segments for the video component and the segments for the audio component may be selected independently of each other. In this embodiment the segments of the video component may, but do not have to, comprise the same frames as the segments of the audio component.

FIG. 3 shows multiple bit rates 1−N for particular content generated by the encoding tool of FIG. 2. The content is identical at each bit rate, but the quality increases with higher bit rates. In the illustrated example, there are N bit rates shown, where N could be any number. In particular embodiments, N is equal to 4. Additionally, the media streams can be divided into segments (also called fragments or chunks). The fragments may range from two to five seconds each in certain embodiments, although any duration may be used. A particular example includes video segments that are 2 seconds in length and audio segments are 5 seconds in length. In the example of FIG. 3, the bit rates are encoded at substantially constant rates (e.g., 1 kbps, 2 kbps, etc.).

FIG. 4 is an example of media streams encoded at variable bit rates 400 that may also be used with any of the embodiments described herein and that is generated by the encoding tool. Variable bit rates allocate a different amount of data to a scene based on complexity. Some scenes require a lower bit rate, such as dark scenes with low levels of movement. Other scenes, such as action scenes, require a higher bit rate because the scenes are more complex. A lower complexity scene can be seen between 0 and 50 seconds and has a small bit rate distribution between the media streams. The higher complexity scenes have a high amount of bit rate distribution as seen at about 100 seconds. In a case with such variance in the bit rates, although the bit rate of one media stream may, on average, be the highest, that media stream's bit rate may fall below the maximum bit rate for other media streams. For purposes of illustration, the bit rates are classified as index 1, 2, 3, . . . N. The bit rates for index 1 and 2 are shown at 402, 404, respectively. At a time shown at 406, the bit rate for index 1 is about 1050 bps. However, as can be seen at a time shown at 404, index 2 is about 2000 bps, which is a higher bit rate than index 1 at time 406. Thus, although index 1 is always higher than index 2 at any particular point of time, over the entire time period, index 2 can peak above values of index 1.

FIG. 5 illustrates an application 502 loaded on a playback device for rendering content. The application 502 may be run on any desired playback device that renders a media stream, such as a gaming console, a cellular phone, a personal digital assistant, in a browser on a computer, etc. The application can include a network communication module 504, a source filter 506, a media pipeline 508, a UI rendering module 510, and a heuristics module 512. The network communication module 504 generally includes software to communicate with a network server from which the media content is streamed. Thus, it is a downloader to obtain the media stream from the network. One example network communication module includes software for implementing a hypertext transfer protocol when communicating with a Web server. Other well-known protocols can be used depending on the playback device. The network communications module chooses an appropriate bitrate of a media stream as directed by the heuristics module. The source filter 506 can be coupled to the network communication module in order to receive audio and video content from the network. The source filter extracts the core media data (by parsing the file, if necessary) and splits the audio and video into two streams for use by the media pipeline. An example media pipeline 508 is shown in FIG. 8 and is described more fully below. The source filter 506 can be included in the media pipeline or separated there from. In any event, the media pipeline decodes the audio and video streams and provides the decoded streams to the UI rendering module 510 for display. Alternatively, the media pipeline 508 can be coupled to a storage device (not shown) that persistently stores the uncompressed data stream. Any variety of media pipelines may be used. The heuristics module 512 monitors the network (via the network communication module 504) and the media pipeline 508 to make intelligent decisions about which bit rate to request from the server in order to minimize glitches that are rendered on the playback device. The heuristics module also can select appropriate bit rates related to a seek operation. As described more fully below, when a seek operation is requested, the heuristics module 512 can direct the network communication module 504 to download a media stream encoded at a low bit rate in order to ensure the fastest possible start-up of rendering. After the start-up period is over, the heuristics module can direct that media streams encoded at higher bit rates are downloaded in order to increase the quality of the playback.

FIG. 6 illustrates another possible environment used to render content on the playback device 104. The lowest layer (not shown) is an operating system executing on the playback device. A platform 602 is an executable file that is downloaded one time from a web server and remains resident on the playback device 104. The platform 602 includes a media pipeline 604 that is explained further below in FIG. 8, a simple source module 606, and a UI rendering module 608 used to render the media stream. A download management program 610 is typically downloaded each time a website is accessed and includes a managed source 612 and a heuristics module 614, which include the intelligence to make decisions about a desired bit rate to download from the host device 102. The purpose of the simple source 606 is to communicate with the managed source 612. Both the managed source 612 and the heuristics module 614 are described further below. The download management program 610 and platform 602 are part of an application 620 that is loaded in a browser 622.

FIG. 7 illustrates a generalized example of a suitable computing environment 700 in which several of the described embodiments may be implemented. The computing environment 700 is not intended to suggest any limitation as to scope of use or functionality, as the techniques and tools may be implemented in diverse general-purpose or special-purpose computing environments.

With reference to FIG. 7, the computing environment 700 includes at least one processing unit 710 and memory 720. Similar computing devices may be used as either the host device 102 or the playback device 104. This most basic configuration 730 is included within a dashed line. The processing unit 710 executes computer-executable instructions and may be a real or a virtual processor. In a multi-processing system, multiple processing units execute computer-executable instructions to increase processing power. The memory 720 may be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two.

A computing environment may have additional features. For example, the computing environment 700 includes storage 740, one or more input devices 750, one or more output devices 760, and one or more communication connections 770. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computing environment 700. Typically, operating system software (not shown) provides an operating environment for other software executing in the computing environment 700, and coordinates activities of the components of the computing environment 700.

The storage 740 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, DVDs, or any other medium which can be used to store information and which can be accessed within the computing environment 700. The storage 740 stores instructions for the software 780 implementing the video encoder and/or decoder.

The input device(s) 750 may be a touch input device such as a keyboard, mouse, pen, or trackball, a voice input device, a scanning device, or another device that provides input to the computing environment 700. The input device(s) 750 may be a sound card, video card, TV tuner card, or similar device that accepts audio or video input in analog or digital form, or a CD-ROM or CD-RW that reads audio or video samples into the computing environment 700. The output device(s) 760 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing environment 700.

The communication connection(s) 770 enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, audio or video input or output, or other data in a modulated data signal. A modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired or wireless techniques implemented with an electrical, optical, RF, infrared, acoustic, or other carrier.

The techniques and tools can be described in the general context of computer-readable media. Computer-readable media are any available media that can be accessed within a computing environment. By way of example, and not limitation, with the computing environment 700, computer-readable media include memory 720, storage 740, communication media, and combinations of any of the above.

The techniques and tools can be described in the general context of computer-executable instructions, such as those included in program modules, being executed in a computing environment on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Computer-executable instructions for program modules may be executed within a local or distributed computing environment.

For the sake of presentation, the detailed description uses terms like “produce” and “encode” to describe computer operations in a computing environment. These terms are high-level abstractions for operations performed by a computer, and should not be confused with acts performed by a human being. The actual computer operations corresponding to these terms vary depending on implementation. Generally, the computing environment 700 can be used as the playback device 104.

FIG. 8 shows an example of the media pipeline 804 in more detail. The illustrated media pipeline is only an example of a possible media pipeline that can be used. In this example, a source filter 800 is included in the media pipeline and is coupled to the network to receive audio and video content from the network. The source filter can extract the core media data (by parsing the file, if necessary) and can split the audio and video into two streams. Two decoders 806, 808 can be used to decompress the encoded audio and video, respectively. Two transform modules 810, 812 can transform the decompressed audio and video signals. The transform operations can include a variety of operations, such as changing color space, changing scale, adding special effects, etc. Finally, sinks 814, 816 can be used to transmit the content to the audio and video drivers, respectively.

FIG. 9 shows an example of the download management program 610 in more detail. An index file 900 is provided by the host and generally describes the different bit rates for the media streams that are available from the network and an address (e.g., URL) where to obtain the source content. In general, the managed source 612 reads data from the network (e.g., Internet), parses the index file 900 that describes the content, parses the file received from the network (e.g., remove header information), communicates with the heuristics module 614 about which bit rate to download next, and maintains an input buffer. The heuristics module 614 instructs the managed source 612 which bit rate to pull next based on empirical data, such as one or more of the following:

1) current and historic bandwidth levels;

2) current and historic buffer levels; and

3) capabilities of the playback device.

An example index file can have separate sections for video and audio and describe the different bit rates that are available to pull from the host. It also can include the URLs, the duration of the content segments, quality information, the size of the files, the number of content segments, position in time of the content segments, the media attributes, etc. In sum, the index file includes information about the time-varying properties of the encoded media streams. An example index file is as follows:

manifest
<MediaIndex MajorVersion=″0″ MinorVersion=″1″>
<Attribute Name=″XCP_MS_UINT64_DURATION″ value=″30″/>
<StreamIndex
Type = ″video″
Subtype = ″WVC1″
Chunks = ″15″
Url = ″{1}/chunk_{1}_{0}.vid″
>
<Bitrate Kbps = ″200″/>
<Bitrate Kbps = ″700″/>
<Bitrate Kbps = ″1500″/>
<Attribute Name=″XCP_MS_UINT32_4CC″ Value=″WVC1″/>
<Attribute Name=″XCP_MS_UINT32_WIDTH″ Value=″720″/>
<Attribute Name=″XCP_MS_UINT32_HEIGHT″ Value=″480″/>
<Attribute Name=″XCP_MS_BLOB_VIDEO_CODEC″
value=″270000010FCBEE1670EF8A16783BF180C9089CC4AFA11C0000010E1207F840″/>
<c n=″0″ d=″20020000″/> <c n=″1″ d=″20020000″/> <c n=″2″ d=″20020000″/> <c
n=″3″ d=″20020000″/> <c n=″4″ d=″20020000″/> <c n=″5″ d=″20020000″/> <c n=″6″
d=″20020000″/> <c n=″7″ d=″20020000″/> <c n=″8″ d=″20020000″/> <c n=″9″ d=″20020000″/>
<c n=″10″ d=″20020000″/> <c n=″11″ d=″20020000″/> <c n=″12″ d=″20020000″/> <c
n=″13″ d=″20020000″/> <c n=″14″ d=″20020000″/>
</StreamIndex>
<StreamIndex
Type = ″audio″
Subtype = ″WMA″
Chunks = ″15″
Url = ″audio/chunk_{1}_{0}.aud″
Language=″en-us″
>
<Bitrate Kbps = ″700″/>
<Attribute Name=″XCP_MS_BLOB_WAVEFORMATEX″
Value=″6101020044AC0000853E00009D0B10000A00008800000F0000000000″/>
<c n=″0″ d=″20630000″/> <c n=″1″ d=″20810000″/> <c n=″2″ d=″19390000″/> <c
n=″3″ d=″20430000″/> <c n=″4″ d=″18800000″/> <c n=″5″ d=″20210000″/> <c n=″6″
d=″20440000″/> <c n=″7″ d=″19500000″/> <c n=″8″ d=″21370000″/> <c n=″9″ d=″19040000″/>
<c n=″10″ d=″19960000″/> <c n=″11″ d=″20610000″/> <c n=″12″ d=″18870000″/> <c
n=″13″ d=″21360000″/> <c n=″14″ d=″19510000″/>
</StreamIndex>
</MediaIndex>

The content is divided into segments (called chunks) that are generally 2-5 seconds each. The chunks are available at multiple bit rates. As already discussed, the chunks may be physically divided segments or virtually divided segments (in the case of a continuous stream). After a predetermined period of time, the quality and bit rate are reevaluated to ensure a glitch-free display of the media stream.

The designation of “bit rates” refers to the bit rates available for the media stream. The “attribute” names can provide information used by the decoder in the media pipeline in order to decode the media stream. One example is that the attributes can be initialization information for the decoder. There can be different sections in the index file for “video” and “audio”, so that the chunks are described independently for each. The designation of “n=” refers to a chunk number. The chunks can be numbered sequentially. The designation of “d=” following each chunk number refers to the duration of the chunk. As can be seen, the chunks are of varying duration but are approximately equal in length. Other characteristics of the media stream can easily be inserted into the index file, such as the size of files associated with the chunks or the duration of the entire media segment. An additional characteristic is also resolution that can be useful to proper rendering. The illustrated index file is only an example and not all of the data elements described need to be used. Indeed, one or more of any of the data elements can be used.

Another example index file is as follows:

<MediaIndex MajorVersion=″0″ MinorVersion=″3″>
<Attribute Name=″XCP_MS _UINT64_DURATION_HNS″ Value=″1169500000″/>
<StreamIndex Type=″Video″ SubType=″WVC1″
Url=″mbr/JennaEasyHD_1280×720_30fps_{1}_{0}.vid″ Chunks=″62″ Bitrates=″12″>
<Bitrate n=″0″ Kbps=″3960″ w=″1280″ h=″720″/>
<Bitrate n=″1″ Kbps=″2083″ w=″1280″ h=″720″/>
<Bitrate n=″2″ Kbps=″1813″ w=″1280″ h=″720″/>
<Bitrate n=″3″ Kbps=″1564″ w=″1280″ h=″720″/>
<Bitrate n=″4″ Kbps=″1396″ w=″1280″ h=″720″/>
<Bitrate n=″5″ Kbps=″1140″ w=″1280″ h=″720″/>
<Bitrate n=″6″ Kbps=″925″ w=″600″ h=″400″/>
<Bitrate n=″7″ Kbps=″781″ w=″600″ h=″400″/>
<Bitrate n=″8″ Kbps=″597″ w=″600″ h=″400″/>
<Bitrate n=″9″ Kbps=″455″ w=″600″ h=″400″/>
<Bitrate n=″10″ Kbps=″349″ w=″600″ h=″400″/>
<Bitrate n=″11″ Kbps=″249″ w=″600″ h=″400″/>
<Attribute Name=″XCP_MS_UINT32_4CC″ Value=″WVC1″/>
<Attribute Name=″XCP_MS_UINT32_WIDTH″ Value=″1280″/>
<Attribute Name=″XCP_MS_UINT32_HEIGHT″ Value=″720″/>
<Attribute Name=″XCP_MS_BLOB_VIDEO_CODEC″
Value=″250000010fd3fe27fl678a27f859fl80c8800000010e5a0040″/>
<c n=″0″ d=″20020000″> <f n=″0″ s=″839″ q=″4930″/> <f n=″1″ s=″413″ q=″2421″/> <f n=″2″
s=″367″ q=″2148″/> <f n=″3″ s=″322″ q=″1885″/> <f n=″4″ s=″290″ q=″1696″/> <f n=″5″
s=″232″ q=″1355″/> <f n=″6″ s=″184″ q=″1076″/> <f n=″7″ s=″164″ q=″953″/> <f n=″8″
s=″124″ q=″721″/> <f n=″9″ s=″99″ q=″575″/> <f n=″10″ s=″79″ q=″454″/> <f n=″11″ s=″58″
q=″334″/> </c>
<c n=″1″ d=″22020000″> <f n=″0″ s=″837″ q=″4761″/> <f n=″1″ s=″435″ q=″2469″/> <f n=″2″
s=″397″ q=″2255″/> <f n=″3″ s=″342″ q=″1941″/> <f n=″4″ s=″308″ q=″1748″/> <f n=″5″
s=″251″ q=″1422″/> <f n=″6″ s=″194″ q=″1099″/> <f n=″7″ s=″168″ q=″946″/> <f n=″8″
s=″130″ q=″731″/> <f n=″9″ s=″108″ q=″605″/> <f n=″10″ s=″88″ q=″494″/> <f n=″11″ s=″65″
q=″359″/> </c>

This index file includes additional information about each chunk. As already described above, “n” is the chunk number and “d” is the duration of the chunk. Additional information can include a designation “s=”, which is a size of each chunk. The “q” designation represents each chunk's average quality. The average quality of a chunk can be calculated during encoding. In the particular example shown, the higher quality number generally means less information is lost due to video compression. As described further below, the heuristics module makes a determination based on a number of factors, such as empirical data of the playback, which bit rate to choose. Quality levels can also be considered into the decision. For example, quality information allows intelligent decisions about accepting lower bit rates for low quality content in order to reserve bandwidth for higher bit rates for high quality content. For example, low bit rates can be used for dark scenes that have little motion (where high quality might not necessarily be visually different than low quality) in favor of using high bit rates for scenes that are complex with a lot of motion.

Any of the described index files can be represented as an XML file with the specific schema, potentially, with a simple encoding to hide clear text. It can contain media level attributes (e.g. total playback duration), and description of individual streams. Stream descriptions can include media stream-specific information, such as type of the stream (e.g. video, audio), encoding and other codec information (e.g. fourCC code, width, height), available bitrates, and information on individual media segments represented by chunks of different available bitrates (e.g. segment duration, chunk sizes). Also, the stream description can include information that allows production of individual chunks URLs for download, which is normally a text pattern that includes calculated fields based on chunk number, chunk bitrate, chunk stream and stream type.

FIG. 10 is a flowchart of a method for seeking in a media stream. In process block 1000, the playback device 104 receives user input to seek to an entry location in a media stream. A typical user input is to drag a location indicator to a new position along a time line. For example, media segments may be viewed on the Internet that include an indicator showing the current position of a video presentation and how much of the presentation remains. The indicator may be dragged along the time line to a new position. Such a drag-and-drop operation results in a seek starting from the new location. Other types of user input for a seek operation may also be used, as is well understood in the art. In process block 1002, the media stream is downloaded substantially at the new location. However, a lower bit rate version of the media stream is used to ensure fast start-up. Generally, a bit rate is used that is lower than the user's network bandwidth can sustain in order to maximize speed of start-up, rather than quality. For example, the lowest bit rate available can be used to ensure that the playback buffer fills quickly. By filling the buffer quickly, the media stream is rendered at a faster speed, albeit quality is sacrificed. Additionally, the location can be a starting point of the nearest fragment or chunk. It may also be possible (if the stream is continuous) to start the media segment at the actual location in time corresponding to the position indicator. In process block 1004, the media stream is rendered starting at the new location or as close to the new location as is possible.

FIG. 11 is a flowchart of a method showing another aspect of the seek operation. In process block 1100, a determination of a sustainable bit rate is made after the seek start-up period is completed. The seek start-up period can be any desired duration. For example, the start-up period can be a predetermined time period (e.g., 2, 3, 4 seconds, etc.) or it can be a certain number of chunks that are downloaded (1, 2, 3, 4, etc.). Generally, the heuristics module determines the sustainable bit rate based on historical information, etc., as already described. In process block 1102, the bit rate is ramped up or changed to the determined bit rate. More particularly, the media stream encoded with the determined bit rate is downloaded from the server. Thus, after a seek operation, the bit rate of the media stream rendered is temporarily reduced in order to have fast start up. After the start-up period, the media stream returns to higher bit rates to render with the highest sustainable quality. As a result, the playback device renders the media stream encoded at a first bit rate and then after a seek operation renders a media stream encoded at a lower, second bit rate, and then after a predetermined period of time after the seek, the playback device renders the media stream encoded at a higher, third bit rate that can be equal to the first bit rate or another bit rate as determined by the heuristics module.

Using a chunking scheme works well with a seek operation. For example, where each chunk has a duration of 2 seconds, if the user wants to seek to the 30th second into the content, the playback device only needs to start downloading the 15th chunk into the stream. Alternatively, the index file can be used to determine the proper location. For example, the index file can allow calculation of a chunk number associated with a selected location in the media stream. In any event, the index file can be used in cooperation with the heuristics module to convert the user seek request into a request from the server to download the media segment from a desired point.

FIG. 12 is a detailed flowchart of a method for implementing a playback after a seek operation. In process block 1200, the playback device receives user input to seek to an entry location in a media stream. In process block 1202, the entry location is used to determine a chunk number in the media stream. For example, if the entry location is 60 seconds and the chunks are 2 seconds each, then the chunk number associated with the entry location is 30. The timing can be determined using the index file described above. In process block 1204, an address (e.g., URL) associated with the chunk is determined. The address can also be determined using the index file. Additionally, the lowest bit rate associated with the media stream is selected in order to fill the playback buffer as quickly as possible to ensure fast playback. In process block 1206, a network request (e.g., HTTP request) is made using the generated network address. The playback is then initiated using the media segment encoded at a low bit rate. For example, if the media stream is encoded at 1, 2, 3, and 4 kbps, the heuristics module can select 1 kbps after a seek operation, even if this is below the network and playback device's ability to download and render. In process block 1208, a next address is generated for the subsequent chunk to be displayed. A determination is made by the heuristics module whether to elect a higher bit rate or maintain the current bit rate. If the start-up period is complete, and the playback buffer substantially full, the heuristics module can elect to increase the bit rate in order to maximize quality. For example, the heuristics module can decide to download a media stream encoded at a bit rate of 3 or 4 kbps. In process block 1210, the new address and bit rate is used to request a next chunk (i.e., fragment) from the network. In process block 1212, the playback continues and a loop is performed as shown at 1214 until the playback is completed. If another seek operation occurs, the flowchart starts again at process block 1200.

FIG. 13 is a user interface diagram showing a seek line 1300 with a current location indicator 1302 that indicates the current location of the content relative to the total duration. Multiple thumbnail photos 1304 are shown along the seek line to indicate actual or logical entry points into the content. The index file can include the information about where to place the thumbnail photos as the encoder generally knows where the scene changes are located. Thus, a user drags the current rendering location indicator 1302 to the desired point and drops to start viewing the content at the new location. Such a drag-and-drop operation causes a seek operation to occur.

Any of the examples described herein are only for purposes of illustration. For example, the example bit rates provided can easily be modified to whatever hit rates work on the system and allow for appropriate rendering of a media stream on a playback device.

In view of the many possible embodiments to which the principles of the disclosed invention may be applied, it should be recognized that the illustrated embodiments are only preferred examples of the invention and should not be taken as limiting the scope of the invention. Rather, the scope of the invention is defined by the following claims. We therefore claim as our invention all that comes within the scope of these claims.

Claims

1. A computer-readable non-volatile storage storing instructions thereon for executing a method for performing a seek operation in a media stream displayed on a playback device, the method comprising: receiving a media stream from a network, the media stream being associated with a first bit rate;receiving a user request to seek to a new location in the media stream;in response to the user request, downloading the media stream, associated with a second bit rate that is less than the first bit rate, from at or about the new location to ensure fast start-up, wherein the content of the media stream content is identical whether received at the first or second bit rates, but quality increases with higher bit rates;rendering the media stream starting at the new location; andramping up the bit rate of the media stream after the fast start-up.

2. The computer-readable non-volatile storage of claim 1, wherein the ramping-up the bit rate of the media stream after the fast start-up is based on a previously stored network bandwidth.

3. The computer-readable non-volatile storage of claim 1, wherein the media stream is available from a server computer coupled to the playback device at multiple bit rates, and each bit rate has a different quality level of content.

4. The computer-readable non-volatile storage of claim 1, further including displaying an indicator of a current point in the media segment being displayed and displaying thumbnail photos as seek points that can be selected.

5. The computer-readable non-volatile storage of claim 1, wherein the media stream is divided into fragments of substantially equal time duration.

6. The computer-readable non-volatile storage of claim 1, further including generating a network address for the new location using an index file associated with the media stream.

7. The computer-readable non-volatile storage of claim 1, wherein the media stream includes multiple logical or actual entry points.

8. The computer-readable non-volatile storage of claim 1, wherein the playback device includes one of the following: a computer, a mobile phone, a gaming console, and a television; and wherein the network is the Internet.

9. The computer-readable non-volatile storage of claim 1, wherein the first and second bit rates for the media stream are at substantially constant bit rates or variable bit rates.

10. A computer-readable non-volatile storage having instructions for executing a method for performing a seek operation, the method comprising: receiving a media segment, associated with a first bit rate, from a network;displaying the media segment including a location indicator showing a current time point being viewed in the media segment;receiving a request to view the media segment from a second time point that is different than the current time point;in response to the request, receiving the media segment, associated with a second bit rate that is lower than the first bit rate, from the network for rendering from the second time point to ensure fast start-up for viewing the media segment, wherein the second bit rate includes a same content of the media segment as the first bit rate, but a different quality level; andreturning to receiving the media segment at the first bit rate after the fast start-up is completed.

11. The computer-readable non-volatile storage of claim 10, wherein the request to view the media segment from the second time point is in response to a user drag-and-drop operation on the location indicator.

12. The computer-readable non-volatile storage of claim 10, further including returning to receiving the media segment associated with the first bit rate from the network after the start-up is completed.

13. The computer-readable non-volatile storage of claim 10, wherein the network is the Internet.

14. The computer-readable non-volatile storage of claim 10, wherein the media segment is divided into fragments and the second time point is a start of a fragment; and further including switching to a higher bit rate after the fragment associated with the second time point is received.