Signaling valid entry points in a video stream

RELATED APPLICATION INFORMATION

0001This application claims the benefit of <patcit id="pcit0001" dnum="US52054303P" dnum-type="L"><text>U.S. Provisional Patent Application Serial No. 60/520,543, filed November 13, 2003</text></patcit>.

COPYRIGHT AUTHORIZATION

0002A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by any one of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.

TECHNICAL FIELD

0003Techniques and tools for coding/decoding digital video are described. For example, a video encoder uses described techniques and tools for defining and signaling valid entry points in a video stream.

BACKGROUND

0004Digital video consumes large amounts of storage and transmission capacity. A typical raw digital video sequence includes 15 or 30 frames per second. Each frame can include tens or hundreds of thousands of pixels (also called pels). Each pixel represents a tiny element of the picture. In raw form, a computer commonly represents a pixel as a set of three samples totaling 24 bits. Thus, the number of bits per second, or bit rate, of a typical raw digital video sequence can be 5 million bits/second or more.

0005Many computers and computer networks lack the resources to process raw digital video. For this reason, engineers use compression (also called coding or encoding) to reduce the bit rate of digital video. Compression decreases the cost of storing and transmitting video by converting the video into a lower bit rate form. Decompression (also called decoding) reconstructs a version of the original video from the compressed form. A "codec" is an encoder/decoder system. Compression can be lossless, in which quality of the video does not suffer but decreases in bit rate are limited by the inherent amount of variability (sometimes called entropy) of the video data. Or, compression can be lossy, in which quality of the video suffers but achievable decreases in bit rate are more dramatic. Lossy compression is often used in conjunction with lossless compression - in a system design in which the lossy compression establishes an approximation of information and lossless compression techniques are applied to represent the approximation.

0006In general, video compression techniques include "intra-picture" compression and "inter-picture" compression, where a picture is, for example, a progressively scanned video frame. For progressive video frames, intra-frame compression techniques compress individual frames (typically called I-frames or key frames). Interframe compression techniques compress frames (typically called predicted frames, P-frames, or B-frames for bi-directional prediction) with reference to preceding and/or following frames (typically called reference or anchor frames).

<u>I. Interlaced Video and Progressive Video</u>

0007A typical interlaced video frame consists of two fields scanned starting at different times. For example, an interlaced video frame includes a top field and a bottom field. Typically, the even-numbered lines (top field) are scanned starting at one time (e.g., time <i>t</i>) and the odd-numbered lines (bottom field) are scanned starting at a different (typically later) time (e.g., time <i>t</i> + 1). This timing can create jagged tooth-like features in regions of an interlaced video frame where motion is present because the two fields are scanned starting at different times. For this reason, interlaced video frames can be rearranged for coding according to a field structure, with the odd lines grouped together for coding as one field, and the even lines grouped together for coding as another field. This arrangement, known as field coding, is useful in high-motion pictures for reduction of such jagged edge artifacts. Fields in different field-coded interlaced frames can be coded differently . For example, a field in a field-coded interlaced frame can be intra-coded (e.g., an interlaced I-field) or inter-coded (e.g., an interlaced P-field or interlaced B-field).

0008On the other hand, in stationary regions, image detail in the interlaced video frame may be more efficiently preserved without such a coding rearrangement. Accordingly, frame coding is often used in stationary or low-motion interlaced video frames, in which the original altemating field line arrangement is preserved. Different frame-coded interlaced frames also can be coded differently . For example, such frames can be intra-coded (e.g., an interlaced I-frame) or inter-coded (e.g., an interlaced P-frame or interlaced B-frame).

0009A typical progressive video frame consists of one frame of content with non-alternating lines. In contrast to interlaced video, progressive video does not divide video frames into separate fields, and an entire frame is scanned left to right, top to bottom starting at a single time. Progressive frames can be intra-coded (e.g., a progressive I-frame) or inter-coded (e.g., a progressive P-frame or progressive B-frame).

<u>II. Standards for Video Compression and Decompression</u>

0010Several international standards relate to video compression and decompression. These standards include the Motion Picture Experts Group ["MPEG"] 1, 2, and 4 standards and the H.261, H.262 (another title for MPEG 2), H.263 and H.264 (also called JVT/AVC) standards from the international Telecommunication Union ["ITU"]. These standards specify aspects of video decoders and formats for compressed video information. Directly or by implication, they also specify certain encoder details, but other encoder details are not specified. These standards use (or support the use of) different combinations of intraframe and interframe decompression and compression. In particular, they use or support the use of different "access points" for decoders and/or editors.

0011The MPEG 2/H.262 standard describes intra-coded pictures (e.g., coded I-frames) and group-of-pictures (GOP) headers. In MPEG 2, intra-coded pictures are coded without reference to other pictures and provide access points to the coded sequence where decoding can begin. Intra-coded pictures can be used at different places in a video sequence. For example, intra-coded pictures can be inserted periodically or can be used in places such as scene changes or where motion compensation is otherwise ineffective. A coded I-frame is an I-frame picture or a pair of field pictures, where the first field picture is an I-picture and the second field picture is an I-picture or a P-picture. The MPEG 2 standard does not allow a coded I-frame in which the first field picture is a P-picture and the second field picture is an I-picture.

0012A GOP header is a construct in the MPEG 2 bitstream that signals the beginning of a group of pictures. Groups of pictures are typically used to signal the boundary of a set of video frames/fields all encoded with reference to the same I-frame. A GOP header is an optional header that may be signaled immediately before a coded I-frame to indicate if the first consecutive B-pictures (if any) immediately following the coded I-frame in the bitstream (but typically preceding the coded I-frame in display order) can be reconstructed properly in the case of a random access. For such B-pictures, if a reference picture before the current coded I-frame is not available, the B-pictures cannot be reconstructed properly unless they only use backward prediction from the current coded I-frame or intra coding. A decoder may use this information to avoid displaying B-pictures that cannot be correctly decoded. For a decoder, the GOP header thus indicates how the decoder can perform decoding from the GOP header, even if the GOP header is in the middle of a video sequence. The GOP header includes a start code called group_start_code. The GOP header start code includes a 24-bit start code prefix (23 0s followed by a 1) followed by the GOP header start code value (B8 in hexadecimal). Start codes in MPEG 2 are byte-aligned; 0s are to be inserted before the beginning of the start code prefix to ensure byte alignment. For additional information, see the H.262 standard.

0013The MPEG 4 standard describes intra-coded video object planes (I-VOPs) and group of video object plane (VOP) headers. An I-VOP is a VOP coded using information only from itself. Non-intra-coded VOPs may be derived from progressive or interlaced frames. In MPEG 4, I-VOPs are coded without reference to other pictures and provide access points to the coded sequence where decoding can begin. A group of VOP header is an optional header that can be used immediately before a coded I-VOP to indicate to the decoder if the first consecutive B-VOPs immediately following the coded I-frame can be reconstructed properly in the case of a random access. A group of VOP header must be followed by a coded I-VOP. A group of VOPs start code includes a 24-bit start code prefix (23 0s followed by a 1) followed by the group of VOPs start code value (B3 in hexadecimal). Start codes in MPEG 4 are byte-aligned and the standard provides for bit-stuffing to achieve byte alignment. For example, for stuffing from one to eight bits, a 0 followed by from one to seven 1s are inserted prior to the start code, so long as the previous code was not a start code. For additional information, see the MPEG 4 standard.

0014According to draft JVT-d157 of the JVT/AVC video standard, I-pictures provide access points to a coded sequence where decoding can begin, and various information used in decoding is signaled in network abstraction layer ("NAL") units. A NAL unit indicates what type of data to expect in the NAL unit, followed by the data itself, interspersed with emulation prevention data. A supplemental enhancement information ("SEI") NAL unit is a type of NAL unit. An SEI NAL unit contains one or more SEI messages. Each SEI message consists of SEI header and SEI payload. The type and size of the SEI payload are coded using an extensible syntax. The SEI payload may have a SEI payload header. For example, a payload header may indicate to which picture the particular data belongs.

0015Annex C of draft JVT-d157 establishes rules for dealing with hypothetical reference decoder ("HRD") buffers. For example, at each decoder refresh point a buffering period SEI message shall follow the last NAL unit of the last picture before a decoder refresh and precede the first NAL unit of the first picture after the decoder refresh. An HRD picture SEI message must follow the last NAL unit of each picture and precede the first NAL unit of the next picture. Each of these SEI messages pertains to the picture that follows it.

0016Annex D of the draft JVT-d157 describes a syntax for a random access point SEI message. A random access point SEI message contains an indicator of a random access entry point for a decoder. The entry point is indicated as a count relative to the position of the SEI message in units of coded frame numbers prior to the frame number of the current picture. Annex D states that a buffering period SEI message should be transmitted at the location of the random access entry point indicated in the random access point SEI message in order to establish initialization of the HRD buffer model.

0017These international standards are limited in several important ways. For example, in MPEG 2, the first coded frame after a GOP header must be a "coded I-frame" -- an intra-coded frame picture or a pair of field pictures where the first field picture is an I-picture and the second field picture is either an I-picture or a P-picture. GOP headers are not allowed to precede any other frame type. In MPEG 4, a group of VOP header must be followed by a coded I-VOP.

0018Given the critical importance of video compression and decompression to digital video, it is not surprising that video compression and decompression are richly developed fields. Whatever the benefits of previous video compression and decompression techniques, however, they do not have the advantages of the following techniques and tools.

0019<nplcit id="ncit0001" npl-type="s"><text>Suzuki, Yagasati: "Study of Random Access for JVT", ITU Study Group 16 - Video Coding Experts Group - ISO/IEC MPEG &amp; ITU-T VCEG (ISO/IEC JTC1/SC29/WG11 and ITU-T SG16 Q6), XX, XX, no. JVT-C054, 10 May 2002</text></nplcit> relates to studies on random access for JVT. It is stated that splicing is one of the important functionalities of codec and JVT codec should support it. There are two types of splicing: seamless splicing and non-seamless splicing. Seamless splicing allows clean instantaneous switching of streams. Non-seamless splicing avoids decoder buffer overflow by inserting short dead time between two. The splice point should be a random access point and new stream follows random access point header.

0020<nplcit id="ncit0002" npl-type="s"><text>WANG: "Signaling of Shot Changes", ITU STUDY GROUP 16 - Video Coding Experts Group - ISO/IEC MPEG &amp; ITU-T VCEG (ISO/IEC JTC1/SC29/WG11 and ITU-T SG16 Q6), XX, XX, no. JVT-D099, 26 July 2002</text></nplcit> relates to signaling of shot changes in the JVT bitstream. Shot changes are embodied by scene transitions in video contents. For the purposes of shot detection and error concealment, two kinds of information are needed: 1) in which frames the shot change starts and ends; 2) the type of the scene transition. Since the information is not necessary for correct decoding of the video coding layer data, it is proposed to signal the information as supplemented enhancement information (SEI). An encoder should generate scene information SEI messages. The following guidelines are recommended: an encoder should create a scene information SEI message for each scene cut in gradual transition. For each scene cut picture, there should be an associated scene information SEI message that is preferably repeated later for error resilience. For each gradual scene transition, there should be a scene information SEI message associated with the first transition picture. For each gradual scene transition, there should also be a scene information SEI message associated with the first picture after the last transition picture.

0021<nplcit id="ncit0003" npl-type="s"><text>Miska M Hannuksela et al: "Random Access and Time Information", ITU Study Group 16 - Video Coding Experts Group - ISO/IEC MPEG &amp; ITU-T VCEG (ISO/IEC JTC1/SC29/WG11 and ITU-T SG16 Q6), XX, XX, no. JVT-B109, 1 February 2002</text></nplcit> relates to syntax and semantics for random access and for timing information. A dedicated NAL packet type is reserved for instantaneous random access positions in order to enable its detection easily.

SUMMARY

0022It is the object of the present invention to simplify prior art techniques. This object is solved by the subject matter of the independent claims. Preferred embodiments are defined by the dependent claims.

0023In summary, the detailed description is directed to various techniques and tools for coding/decoding of digital video. In particular, described embodiments include techniques and tools for determining and signaling entry points in video streams.

0024Video compression typically relies on temporal correlation across video fields or video frames to compress video content efficiently. As a result, compression of video fields/frames introduces temporal dependence across these fields and frames. Techniques and tools described herein are used to embed entry point indicator information in the bitstream that receivers, editing systems or insertion systems can use to detect valid entry points in compressed video. The embedded information can be used, for example, in implementation of "trick" modes (e.g., fast forward, fast rewind, etc.) by allowing a video decoder to jump from one entry point or key frame to another. The various techniques and tools can be used in combination or independently.

0025Additional features and advantages will be made apparent from the following detailed description of different embodiments that proceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

0026<ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">Figure 1</figref> is a block diagram of a suitable computing environment in which several described embodiments may be implemented.</li><li><figref idref="f0002">Figure 2</figref> is a block diagram of a generalized video encoder system used in several described embodiments.</li><li><figref idref="f0003">Figure 3</figref> is a block diagram of a generalized video decoder system used in several described embodiments.</li><li><figref idref="f0004">Figure 4</figref> is a flow chart showing a technique for determining and indicating entry points in a bitstream.</li><li><figref idref="f0004">Figure 5</figref> is a flow chart showing a technique for processing a compressed video bitstream having entry point indicators.</li><li><figref idref="f0005">Figure 6</figref> is a diagram showing a bitstream syntax for signaling an entry point before a progressive I frame.</li><li><figref idref="f0005">Figure 7</figref> is a diagram showing a bitstream syntax for signaling an entry point before an I/P frame.</li><li><figref idref="f0006">Figure 8</figref> is a diagram showing a bitstream syntax for signaling an entry point before a P/I frame.</li><li><figref idref="f0006">Figure 9</figref> is a diagram showing a bitstream syntax for signaling an entry point before an I/I frame.</li><li><figref idref="f0007">Figure 10</figref> is a diagram showing a bitstream syntax for signaling an entry point before an interlace I frame.</li></ul>

DETAILED DESCRIPTION

0027The present application relates to techniques and tools for determining and signaling valid entry points in compressed video. In this context, "determining" can mean, for example, detecting whether a video frame is a valid entry point in the bitstream once it has been compressed, or enforcing rules or policies to guarantee production of valid entry points at compression time. A bitstream format or syntax includes flags and other codes to incorporate the techniques. The bitstream format comprises different layers or levels (e.g., sequence level, frame/picture/image level, macroblock level, and/or block level).

0028Described techniques and tools introduce conditions for a video frame or a video field to be a valid entry point in a bitstream. These conditions represent policies that a video encoder enforces during encoding of a video sequence to produce entry points in bitstreams (in order to enable "trick" modes, for example). The policies can produce entry points in the bitstream at different locations. For example, policies can direct entry points to be provided when a scene change occurs or to indicate where a commercial can be inserted to facilitate activities such as video summarization and splicing, respectively. The policies governing the insertion of entry points in the bitstream can also be designed such that entry points are provided at regular intervals and at specific time intervals (for example, to minimize latency upon tuning to the service). Described techniques and tools are also directed to the mechanisms by which entry points can be signaled unambiguously in an elementary stream. This can be achieved by a special start code followed by an entry header.

0029The various techniques and tools can be used in combination or independently. Different embodiments implement one or more of the described techniques and tools.

<u>I. Computing Environment</u>

0030<figref idref="f0001">Figure 1</figref> illustrates a generalized example of a suitable computing environment 100 in which several of the described embodiments may be implemented. The computing environment 100 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.

0031With reference to <figref idref="f0001">Figure 1</figref>, the computing environment 100 includes at least one processing unit 110 and memory 120. In <figref idref="f0001">Figure 1</figref>, this most basic configuration 130 is included within a dashed line. The processing unit 110 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 120 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. The memory 120 stores software 180 implementing a video encoder or decoder with entry point processing.

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

0033The storage 140 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 100. The storage 140 stores instructions for the software 180 implementing the video encoder or decoder.

0034The input device(s) 150 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 100. For audio or video encoding, the input device(s) 150 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 100. The output device(s) 160 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing environment 100.

0035The communication connection(s) 170 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.

0036The 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, within the computing environment 100, computer-readable media include memory 120, storage 140, communication media, and combinations of any of the above.

0037The 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.

0038For the sake of presentation, the detailed description uses terms like "determine," "enforce," and "provide" 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.

<u>II. Generalized Video Encoder and Decoder</u>

0039<figref idref="f0002">Figure 2</figref> is a block diagram of a generalized video encoder 200 and <figref idref="f0003">Figure 3</figref> is a block diagram of a generalized video decoder 300.

0040The relationships shown between modules within the encoder and decoder indicate the main flow of information in the encoder and decoder, other relationships are not shown for the sake of simplicity. In particular, <figref idref="f0002">Figures 2</figref> and <figref idref="f0003">3</figref> generally do not show side information indicating the encoder settings, modes, tables, etc. used for a video sequence, frame, macroblock, block, etc. Such side information is sent in the output bitstream, typically after entropy encoding of the side information. The format of the output bitstream can be a Windows Media Video format or another format.

0041The encoder 200 and decoder 300 are block-based and use a 4:2:0 macroblock format. Alternatively, the encoder 200 and decoder 300 are object-based or use a different macroblock or block format.

0042Depending on implementation and the type of compression desired, modules of the encoder or decoder can be added, omitted, split into multiple modules, combined with other modules, and/or replaced with like modules. In alternative embodiments, encoder or decoders with different modules and/or other configurations of modules perform one or more of the described techniques.

A. Video Encoder

0043<figref idref="f0002">Figure 2</figref> is a block diagram of a general video encoder system 200. The encoder system 200 receives a sequence of video frames including a current frame 205, and produces compressed video information 295 as output. Particular embodiments of video encoders typically use a variation or supplemented version of the generalized encoder 200.

0044The encoder system 200 compresses predicted frames and key frames. For the sake of presentation, <figref idref="f0002">Figure 2</figref> shows a path for key frames through the encoder system 200 and a path for predicted frames. Many of the components of the encoder system 200 are used for compressing both key frames and predicted frames. The exact operations performed by those components can vary depending on the type of information being compressed.

0045A predicted frame (also called P-frame, B-frame for bi-directional prediction, or inter-coded frame) is represented in terms of prediction (or difference) from one or more reference (or anchor) frames. A prediction residual is the difference between what was predicted and the original frame. In contrast, a key frame (also called I-frame, intra-coded frame) is compressed without reference to other frames. Intra-coded frames include progressive I-frames, interlaced I-frames (frame interlaced mode), and I/I frames (field interlaced mode). Parts of other frames also can be compressed without reference to other frames. For example, the I-fields of I/P-frames and P/I frames are compressed without reference to other frames and are described in detail below. In some cases, the P-fields of I/P frames are compressed without reference to other frames, as described in detail below.

0046If the current frame 205 is a forward-predicted frame, a motion estimator 210 estimates motion of macroblocks or other sets of pixels of the current frame 205 with respect to a reference frame, which is the reconstructed previous frame 225 buffered in a frame store (e.g., frame store 220). If the current frame 205 is a bi-directionally-predicted frame (a B-frame), a motion estimator 210 estimates motion in the current frame 205 with respect to two reconstructed reference frames. Typically, a motion estimator estimates motion in a B-frame with respect to a temporally previous reference frame and a temporally future reference frame.

0047The motion estimator 210 outputs as side information motion information 215 such as motion vectors. A motion compensator 230 applies the motion information 215 to the reconstructed frame(s) 225 to form a motion-compensated current frame 235. The prediction is rarely perfect, however, and the difference between the motion-compensated current frame 235 and the original current frame 205 is the prediction residual 245. Alternatively, a motion estimator and motion compensator apply another type of motion estimation/compensation.

0048A frequency transformer 260 converts the spatial domain video information into frequency domain (i.e., spectral) data. A quantizer 270 then quantizes the blocks of spectral data coefficients. In addition to quantization, the encoder 200 can use frame dropping, adaptive filtering, or other techniques for rate control.

0049When a reconstructed current frame is needed for subsequent motion estimation/compensation, an inverse quantizer 276 performs inverse quantization on the quantized spectral data coefficients. An inverse frequency transformer 266 then performs the inverse of the operations of the frequency transformer 260, producing a reconstructed prediction residual (for a predicted frame) or a reconstructed key frame. If the current frame 205 was a key frame, the reconstructed key frame is taken as the reconstructed current frame (not shown). If the current frame 205 was a predicted frame, the reconstructed prediction residual is added to the motion-compensated current frame 235 to form the reconstructed current frame. A frame store (e.g., frame store 220) buffers the reconstructed current frame for use in predicting another frame.

0050The entropy coder 280 compresses the output of the quantizer 270 as well as certain side information (e.g., motion information 215, quantization step size). Typical entropy coding techniques include arithmetic coding, differential coding, Huffman coding, run length coding, LZ coding, dictionary coding, and combinations of the above.

0051The entropy coder 280 puts compressed video information 295 in the buffer 290. A buffer level indicator is fed back to bit rate adaptive modules. The compressed video information 295 is depleted from the buffer 290 at a constant or relatively constant bit rate and stored for subsequent streaming at that bit rate. Therefore, the level of the buffer 290 is primarily a function of the entropy of the filtered, quantized video information, which affects the efficiency of the entropy coding. Alternatively, the encoder system 200 streams compressed video information immediately following compression, and the level of the buffer 290 also depends on the rate at which information is depleted from the buffer 290 for transmission.

0052Before or after the buffer 290, the compressed video information 295 can be channel coded for transmission over the network. The channel coding can apply error detection and correction data to the compressed video information 295.

B. Video Decoder

0053<figref idref="f0003">Figure 3</figref> is a block diagram of a general video decoder system 300. The decoder system 300 receives information 395 for a compressed sequence of video frames and produces output including a reconstructed frame 305. Particular embodiments of video decoders typically use a variation or supplemented version of the generalized decoder 300.

0054The decoder system 300 decompresses predicted frames and key frames. For the sake of presentation, <figref idref="f0003">Figure 3</figref> shows a path for key frames through the decoder system 300 and a path for predicted frames. Many of the components of the decoder system 300 are used for decompressing both key frames and predicted frames. The exact operations performed by those components can vary depending on the type of information being decompressed.

0055A buffer 390 receives the information 395 for the compressed video sequence and makes the received information available to the entropy decoder 380. The buffer 390 typically receives the information at a rate that is fairly constant over time, and includes a jitter buffer to smooth short-term variations in bandwidth or transmission. The buffer 390 can include a playback buffer and other buffers as well. Alternatively, the buffer 390 receives information at a varying rate. Before or after the buffer 390, the compressed video information can be channel decoded and processed for error detection and correction.

0056The entropy decoder 380 entropy decodes entropy-coded quantized data as well as entropy-coded side information (e.g., motion information 315, quantization step size), typically applying the inverse of the entropy encoding performed in the encoder.

0057A motion compensator 330 applies motion information 315 to one or more reference frames 325 to form a prediction 335 of the frame 305 being reconstructed. For example, the motion compensator 330 uses a macroblock motion vector to find a macroblock in a reference frame 325. A frame buffer (e.g., frame buffer 320) stores previously reconstructed frames for use as reference frames. Typically, B-frames have more than one reference frame (e.g., a temporally previous reference frame and a temporally future reference frame). The prediction by the motion compensator is rarely perfect, so the decoder 300 also reconstructs prediction residuals.

0058When the decoder needs a reconstructed frame for subsequent motion compensation, a frame buffer (e.g., frame buffer 320) buffers the reconstructed frame for use in predicting another frame.

0059An inverse quantizer 370 inverse quantizes entropy-decoded data. An inverse frequency transformer 360 converts the quantized, frequency domain data into spatial domain video information.

<u>III. Determining and Signaling Valid Entry Points</u>

0060Valid entry points in a bitstream are locations in an elementary bitstream from which a system (e.g., a receiver, a video splicer, a commercial insertion tool, a video editor, a summarization engine, etc.) can decode or process the bitstream without the need of any preceding information (bits) in the bitstream. Frames that can be decoded without reference to preceding frames are typically referred to as "key" frames.

0061An entry point is signaled in a bitstream by an entry point indicator. The purpose of an entry point indicator is to signal the presence of a special location in a bitstream to begin or resume decoding (e.g., where there is no dependency on past decoded video fields or frames to decode the video frame following immediately the entry point indicator). Entry point indicators can be inserted at regular or irregular intervals in a bitstream. Therefore, an encoder can adopt different policies to govern the insertion of entry point indicators in a bitstream.

0062<figref idref="f0004">Figure 4</figref> is a flow chart showing a technique 400 for determining and indicating entry points in a bitstream. At 410, an entry point is determined in a bitstream based on an entry point policy. Then, at 420, an entry point indicator is included in an encoded bitstream. <figref idref="f0004">Figure 5</figref> is a flow chart showing a technique 500 for processing (e.g., in a video decoder) a compressed video bitstream having entry point indicators. At 510, compressed video with one or more entry point indicators is received (e.g., by a video decoder, video editor, splicer, etc.). Then, at 520, the compressed video is processed based at least in part on the one or more entry point indicators.

0063As an example, an entry point indicator can comprise an entry point start code and an entry point header.

0064In some implementations, entry point start codes signal entry points in the bitstream. Entry point start codes can consist of a special 32-bit code that is not emulated anywhere else in the bitstream. For example, entry point start codes can take the form of a unique sequence of 32 bits, where the first three bytes are 0x000001 and the last byte identifies the start code the entry start code. However, more compact representations of the start code are allowed if the underlying transport includes enough signaling to provide similar information. For example, the entry point start code can be an abbreviated start code (e.g., one byte or a few bits) sufficient to distinguish the entry point start code from other kinds of start codes in the video stream. In some implementations, an entry point start code is located after the last of a video frame and before the beginning of the next video frame.

0065Entry point start codes can be used along with other start codes in a bitstream, such as sequence start codes, frame start code, field start codes, slice start codes, and user data start codes. Each type of start code can be a 32-bit field. The various types of start codes can have different last bytes that identify the start code as a sequence start code, frame start code, field start code, slice start code, user data start code, etc.

0066A start code may be preceded by an arbitrary number of "0"-valued bits, themselves preceded by a "1"-valued bit. The purpose of using a "10 ... 0" flushing bits sequence between the last of the previous structure and the beginning of a start code is to allow consecutive start codes to be separated by an integer number of bytes, thereby facilitating parsing of start codes by receivers. Before the start code and after the last '0'-valued flushing bit, it is also possible to add an arbitrary number of 0x00-valued bytes.

0067In some implementations, an entry point start code is followed immediately by an entry point header. If there is a need to insert an entry point start code and an entry point header in a position in the bitstream where there are already a sequence start code and sequence header between two consecutive video frames, the entry point start code and the entry point header follow the sequence start code and sequence header.

0068Since an entry point start code and an entry point header may be inserted at regular or irregular intervals in a bitstream, an encoder can adopt different policies to govern the insertion of entry point start codes and associated headers.

<u>IV. Examples</u>

0069In some implementations, an entry point start code and associated header signal a valid entry point in the bitstream. Put differently, the entry point start code and/or header signals the presence of a special location in a bitstream where there is no dependency on decoded video fields or frames prior to (in time order) the key frame after the entry point start code and header to decode the video frame(s) following immediately (in time order) the key frame after the entry point start code and header. Thus, frames that can follow entry point key frames include both frames which can themselves be entry point frames (e.g., progressive I-frames, frame interlaced I-frames, field interlaced I/I frames, field interlaced I/P frames, field interlaced P/I frames, etc.) and predicted frames, subject to certain conditions described below. The conditions for achieving this are listed in the examples below with reference to <figref idref="f0005 f0006 f0007">Figures 6-10</figref>. Video frames and/or fields must satisfy certain conditions, depending on the type of picture. These conditions are only examples. Other conditions could be used.

0070These conditions depend on the type of the first frames/fields after the entry point. In these examples, the type of the first frame following an entry point start code header is I if picture coding type is set to progressive or frame interlace. If the picture coding type is set to field interlace, the type of the first two fields following an entry point start code and header is I/P (I and P), P/I (P and I), or I/I (I and I).

0071<figref idref="f0005 f0006 f0007">Figures 6-10</figref> reference certain bitstream constructs, definitions of which can be found in the following list: <ul id="ul0002" list-style="none" compact="compact"><li>SEQ_SC: Sequence Start Code</li><li>SEQ_HDR: Sequence Header</li><li>ENTRY_SC: Entry Point Start Code</li><li>ENTRY_HDR: Entry Point Header</li><li>FRAME_SC: Frame Start Code</li><li>FRAME_HDR: Frame Header</li><li>FIELD_SC: Field Start Code</li><li>FIELD_HDR: Field Header</li><li>UD_SC: User Data Start Code</li><li>UD_BYT: User Data Bytes</li></ul> In addition, <figref idref="f0005 f0006 f0007">Figures 6-10</figref> refer to an FCM field. FCM is a variable-size field indicating the type of the picture coding used for the video frame. The value "0" indicates that the picture coding type is "progressive." The value "10" indicates that the frame is encoded as "field interlaced." In a field interlaced picture, a frame is comprised of two distinct video fields, a top field and a bottom field, which are typically roughly 15 milliseconds apart. The value "11" indicates a "frame interlaced" type picture. In a frame interlaced picture, an interlaced video frame is comprised of macroblocks in either field mode or frame mode. This is useful for situations where there is a lot of foreground motion in reduced areas in the picture (coded in field mode as separate fields within macroblocks) while the background is static (and coded in frame mode as interlaced lines within macroblocks). The FCM value correlates with the title of each respective Figure. The conditions for valid entry points differ depending on how the picture has been encoded (progressive, field interlaced or frame interlaced). The I, P, or B type for frames and fields may be signaled in the respective headers for the frames and fields. For example, for a field interlaced mode frame, the picture type for the first field is signaled in the frame or field header preceding the first field data, and the picture type for the second field is signaled in the field header preceding the second field data. Altematively, a field in the frame header indicates the combination of field types for the pair of fields, for example, I/I, P/I, or I/P.

0072The following diagrams and discussion incorporate certain rules for positions of reference fields and frames. In general, the reference frame for a progressive P-frame is the first I- or P-frame preceding the frame, and the reference frame(s) for a progressive B-frame may further include the first I- or P-frame following the frame. Similar rules apply for frame interlaced mode P-frames and B-frames. For field interlaced frames, the reference field(s) for a P-field are, for example, one or both of the first I- or P-fields preceding the field. The reference field(s) for a B-field are, for example, the two temporally preceding fields and two temporally subsequent fields.

A. I-frame in Progressive Mode

0073<figref idref="f0005">Figure 6</figref> illustrates how an entry point start code and header can be present before an I-frame when the picture coding type (FCM field) is set to the binary value "0" (progressive mode). <figref idref="f0005">Figure 6</figref> also shows a sequence start code and a sequence header before the entry point start code, but this is not a requirement. An entry point start code need not always be preceded by such structures.

0074Since the frame is intra-coded, no additional condition is needed to make this I-frame a valid entry point in a bitstream. The entry point applies to the I-frame that follows the entry point start code and header. It does not apply to any B-frame data or B-field data that follow that I-frame in the bitstream and for which the presentation time is earlier than the presentation time for that I-frame.

B. I/P-frame in Field Interlace Mode

0075<figref idref="f0005">Figure 7</figref> illustrates how an entry point start code and header can be present before an I/P-frame when the picture coding type (FCM field) is set to the binary value "10" (field interlace mode). <figref idref="f0005">Figure 7</figref> does not show a sequence start code and a sequence header before the entry point start code, but it may be the case that such structures precede the entry point start code.

0076Since the frame is made of an I-field followed by a P-field, the following conditions shall be met to make this I/P frame a valid entry point in a bitstream: <ul id="ul0003" list-style="bullet" compact="compact"><li>The value of the "numref' field in the field header of the P-field of the entry I/P-frame shall be the binary value "0".</li><li>The value of the "reffield" field in the field header of the P-field of the entry I/P-frame shall be the binary value "0".</li></ul> These conditions ensure that the P-field is only predicted from the I-field, and therefore there is no dependency on frames or fields before the entry point. (In other words, the "numref" (number of references) field indicates the number of reference fields for the P-field is one (numref = 0), and the "reffield" (reference field) field indicates the one reference field for the P-field is the temporally closest field - the I-field (reffield = 0)).

0077The entry point applies to the I/P-frame that follows the entry point start code and header but it does not apply to any B-frame data or B-field data that follow that I/P-frame in the bitstream and for which the presentation time comes earlier than the presentation time for that I/P-frame.

C. P/I frame in Field Interlace Mode

0078<figref idref="f0006">Figure 8</figref> illustrates how an entry point start code and header can be present before a P/I-frame when the picture coding type (FCM field) is set to the binary value "10" (field interlace mode). <figref idref="f0006">Figure 8</figref> does not show a sequence start code and a sequence header before the entry point start code, but it may be the case that such structures precede the entry point start code.

0079Since the frame is made of a P-field followed by an I-field, the following conditions shall be met to make this P/I-frame a valid entry point in a bitstream: <ul id="ul0004" list-style="bullet" compact="compact"><li>Following the entry I-field of the P/I frame, a P/P-frame in field interlace mode shall be present in the bitstream before any occurrence of P-frames in progressive or frame interlaced modes.</li><li>The value of the "numref" field in the field header of the first P-field following the entry P/I-frame shall be the binary value "0".</li><li>The value of the "reffield" field in the field header of the first P-field following the entry P/I-frame shall be the binary value "0".</li><li>Any B-frames following the entry P/I-frame in the bitstream and for which the presentation time comes later than the presentation times for that entry P/I-frame shall not be encoded as depending on the P/I-frame.</li><li>The first (in temporal order) B-field of any B/B-frames following the entry P/I-frame in the bitstream and for which the presentation time comes later than the presentation times of that P/I-frame shall not be encoded as depending on the P-field of the entry P/I-frame.</li></ul> These conditions ensure that the next P/P-frame and B/B-frames in the bitstream may be predicted from the entry I-field but not the P-field that immediately precedes it. Note also that it is impossible to have a valid entry point here if there is a P-frame that has been predicted from the P/I-frame, since this would create a dependency on the P-field of the entry P/I-frame.

0080The entry point applies to the I-field that follows the entry point start code and header but it does not apply to any B-frame data that follows that I-field in the bitstream and for which the presentation time is earlier than the presentation time for that I-field. Furthermore, the entry point does not apply to the P-field data located between the entry point start code and the following I-field of the entry P/I frame.

D. I/I-frame in Field Interlace Mode

0081<figref idref="f0006">Figure 9</figref> illustrates how an entry point start code and header can be present before an I/I-frame when the picture coding type (FCM field) is set to the binary value "10" (field interlace mode). <figref idref="f0006">Figure 9</figref> does not show a sequence start code and a sequence header before the entry point start code, but it may be the case that such structures precede the entry start code.

0082Since the I/I-frame is made of two I-fields, no additional condition is needed to make this frame a valid entry point in a bitstream.

0083The entry point applies to the I/I-frame that follows the entry point start code and header, but it does not apply to any B-frame data or B-field data that follows that I/I-frame in the bitstream and for which the presentation times come earlier than the presentation time for that I/I-frame.

E. I frame in Frame Interlace Mode

0084<figref idref="f0007">Figure 10</figref> illustrates how an entry point start code and header can be present before an I-frame when the picture coding type (FCM field) is set to the binary value "11" (frame interlace mode). <figref idref="f0007">Figure 10</figref> also shows a sequence start code and a sequence header before the entry point start code, but it is not a requirement that an entry start code be always preceded by such structures.

0085Since the frame is intra-coded, no additional condition is needed to make this I-frame a valid entry point in a bitstream. The entry point applies to the I-frame that follows the entry point start code and header, but it does not apply to any B-frame data or B-field data that follows that I-frame in the bitstream and for which the presentation times come earlier than the presentation time for that I-frame.

<u>V. Extensions</u>

0086In conjunction with or in addition to the various alternatives described above, the encoder and decoder may operate as follows.

0087Policies assess whether a point in a bitstream is a valid entry point. An encoder can use a policy that defines scene changes as valid entry points (and therefore ensures that the compression engine yields one of the constraints described above). In this case, scene changes can be detected by means of a scene change detector component that can interface (communicate) with the encoder in real time. Encoders can additionally use policies for generating I-frames or I-fields at particular time intervals.

0088An encoder can also monitor the type and properties of the compressed video it produces and detect the points in the bitstream that verify one of the conditions such as those described in the examples for I-, I/P-, P/I- and I/I-frames stated above. Upon detecting such an event, the encoder can insert an entry point start code and an entry point header in the final bitstream.

0089In modes such as fast-forward or fast-rewind, a video decoder could search for and render entry point frames by searching for entry point start codes.

0090Entry points can be utilized by an application to produce and display a summarized version (thumbnails) of a video sequence directly from the compressed bitstream. Such an application can be a video editing application or a digital television electronic program guide.

0091For performing video splicing, a video splicer could search for entry points to find scene changes at which splicing would be appropriate.

0092The entry point header can contain information on buffer status. This information indicates buffer status that needs to be achieved to avoid buffer underflow or overflow. The buffer status information is stored in a field in the entry header. For example, putting buffer fullness requirement information into the entry header lets the decoder know what the minimum fullness of the buffer should be achieved before decoding can begin.

0093In several examples above, an entry point does not apply to B-frame or B-field data that follow the entry I-frame or I-field in the bitstream and for which the presentation time is earlier than the presentation time for the I-frame or I-field. Altematively, the entry point does apply to such B-frame or B-field data if the B-frame or B-field data is intra coded or predicted only from the entry point I-frame or I-field.

0094Having described and illustrated the principles of our invention with reference to various embodiments, it will be recognized that the various embodiments can be modified in arrangement and detail without departing from such principles. It should be understood that the programs, processes, or methods described herein are not related or limited to any particular type of computing environment, unless indicated otherwise. Various types of general purpose or specialized computing environments may be used with or perform operations in accordance with the teachings described herein. Elements of embodiments shown in software may be implemented in hardware and vice versa.

0095In view of the many possible embodiments to which the principles of our invention may be applied, we claim as our invention all such embodiments as may come within the scope of the following claims and equivalents thereto.