|Publication number||US7839930 B2|
|Application number||US 10/882,739|
|Publication date||Nov 23, 2010|
|Filing date||Jun 30, 2004|
|Priority date||Nov 13, 2003|
|Also published as||CN1617593A, CN100568970C, EP1549064A2, EP1549064A3, EP1549064B1, US20050105883|
|Publication number||10882739, 882739, US 7839930 B2, US 7839930B2, US-B2-7839930, US7839930 B2, US7839930B2|
|Inventors||Thomas W. Holcomb, Regis J. Crinon, Timothy E. Onders, Sridhar Srinivasan, Shankar Regunathan|
|Original Assignee||Microsoft Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (102), Non-Patent Citations (54), Referenced by (9), Classifications (18), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims the benefit of U.S. Provisional patent application Ser. No. 60/520,543, filed Nov. 13, 2003, the disclosure of which is incorporated herein by reference.
A 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.
Techniques 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.
Digital 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.
Many 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.
In 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). Inter-frame compression techniques compress frames (typically called predicted frames, P-frames, or B-frames for bidirectional prediction) with reference to preceding and/or following frames (typically called reference or anchor frames).
I. Interlaced Video and Progressive Video
A 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 t) and the odd-numbered lines (bottom field) are scanned starting at a different (typically later) time (e.g., time t+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).
On 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 alternating 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).
A 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).
II. Standards for Video Compression and Decompression
Several 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.
The 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.
A 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.
The 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 is 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.
According 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.
Annex 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.
Annex 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.
These 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.
Given 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.
In 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.
Video 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.
Additional features and advantages will be made apparent from the following detailed description of different embodiments that proceeds with reference to the accompanying drawings.
The 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).
Described 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.
The various techniques and tools can be used in combination or independently. Different embodiments implement one or more of the described techniques and tools.
With reference to
A 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.
The 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.
The 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.
The 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.
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, within the computing environment 100, computer-readable media include memory 120, storage 140, 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 “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.
The 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,
The 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.
Depending 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
The encoder system 200 compresses predicted frames and key frames. For the sake of presentation,
A predicted frame (also called P-frame, B-frame for bidirectional 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.
If 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.
The 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.
A 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.
When 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.
The 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.
The 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.
Before 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
The decoder system 300 decompresses predicted frames and key frames. For the sake of presentation,
A 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.
The 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.
A 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.
When 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.
An inverse quantizer 370 inverse quantizes entropy-decoded data. An inverse frequency transformer 360 converts the quantized, frequency domain data into spatial domain video information.
Valid 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.
An 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.
As an example, an entry point indicator can comprise an entry point start code and an entry point header.
In 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.
Entry 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.
A 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.
In 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.
Since 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.
In 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
These 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).
SEQ_SC: Sequence Start Code
SEQ_HDR: Sequence Header
ENTRY_SC: Entry Point Start Code
ENTRY_HDR: Entry Point Header
FRAME_SC: Frame Start Code
FRAME_HDR: Frame Header
FIELD_SC: Field Start Code
FIELD_HDR: Field Header
UD_SC: User Data Start Code
UD_BYT: User Data Bytes
The 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
Since 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
Since 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:
The 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
Since 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:
The 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. II/-frame in Field Interlace Mode
Since 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.
The 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
Since 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.
In conjunction with or in addition to the various alternatives described above, the encoder and decoder may operate as follows.
Policies 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.
An 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.
In 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.
Entry 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.
For performing video splicing, a video splicer could search for entry points to find scene changes at which splicing would be appropriate.
The 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.
In 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. Alternatively, 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.
Having 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.
In 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 and spirit of the following claims and equivalents thereto.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4847877||Nov 28, 1986||Jul 11, 1989||International Business Machines Corporation||Method and apparatus for detecting a predetermined bit pattern within a serial bit stream|
|US4969055 *||Aug 25, 1988||Nov 6, 1990||Oberjatzas Guenter||Method for recording and/or reproducing digitally coded signals with interframe and interframe coding|
|US5023727||Oct 12, 1989||Jun 11, 1991||Ian A. R. Boyd||Method and device for producing a substantially continuous composite video signal|
|US5027206||Sep 13, 1989||Jun 25, 1991||U.S. Philips Corporation||High-definition television systems|
|US5168356||Dec 20, 1991||Dec 1, 1992||General Electric Company||Apparatus for segmenting encoded video signal for transmission|
|US5175618||Oct 30, 1991||Dec 29, 1992||Victor Company Of Japan, Ltd.||Compression method for interlace moving image signals|
|US5191436||Apr 30, 1991||Mar 2, 1993||Sony Corporation||Method for recording coded motion picture data|
|US5212549 *||Jun 16, 1992||May 18, 1993||Rca Thomson Licensing Corporation||Error concealment apparatus for a compressed video signal processing system|
|US5223949||Apr 17, 1992||Jun 29, 1993||Matsushita Electric Industrial Co., Ltd.||Coding means for a signal processing system|
|US5293229||Mar 27, 1992||Mar 8, 1994||Matsushita Electric Corporation Of America||Apparatus and method for processing groups of fields in a video data compression system|
|US5325126||Apr 1, 1992||Jun 28, 1994||Intel Corporation||Method and apparatus for real time compression and decompression of a digital motion video signal|
|US5365552||Nov 16, 1992||Nov 15, 1994||Intel Corporation||Buffer fullness indicator|
|US5428396||Dec 27, 1993||Jun 27, 1995||Sony Corporation||Variable length coding/decoding method for motion vectors|
|US5477397||Jun 8, 1993||Dec 19, 1995||Matsushita Electric Corporation Of America||Digital high definition television receiver with features that facilitate trick-play modes on a digital VCR|
|US5543847||Dec 13, 1993||Aug 6, 1996||Sony Corporation||Picture coding and decoding method for random accessing|
|US5586200||Jan 7, 1994||Dec 17, 1996||Panasonic Technologies, Inc.||Segmentation based image compression system|
|US5602956 *||Jan 6, 1994||Feb 11, 1997||Sony Corporation||Picture signal coding method, decoding method and picture signal recording medium|
|US5621840 *||Sep 21, 1994||Apr 15, 1997||Sony Corporation||Data transmission method and apparatus, data decoding apparatus, and data recording medium|
|US5661665||Jun 26, 1996||Aug 26, 1997||Microsoft Corporation||Multi-media synchronization|
|US5740310||Jun 28, 1994||Apr 14, 1998||U.S. Philips Corporation||Method of maintaining display continuity from a CD with slow-motion or freeze capability|
|US5784528||Sep 27, 1996||Jul 21, 1998||Matsushita Electric Industrial Co. Ltd.||Method and an apparatus for interleaving bitstream to record thereof on a recording medium, and reproducing the interleaved bitstream therefrom|
|US5835636||May 28, 1996||Nov 10, 1998||Lsi Logic Corporation||Method and apparatus for reducing the memory required for decoding bidirectionally predictive-coded frames during pull-down|
|US5838823||Feb 29, 1996||Nov 17, 1998||Electronic Arts, Inc.||Video image compression and decompression|
|US5838872 *||Mar 15, 1996||Nov 17, 1998||Matsushita Electric Industrial Co., Ltd.||Image information recording apparatus and image information recording method|
|US5864368 *||Feb 26, 1996||Jan 26, 1999||Sony Corporation||Picture signal editing and encoding method and apparatus, signal recording medium and picture signal decoding method and apparatus|
|US5870444||Apr 23, 1996||Feb 9, 1999||Scientific-Atlanta, Inc.||Method and apparatus for performing very fast message synchronization|
|US5898897||Oct 18, 1996||Apr 27, 1999||Samsung Electronics Company, Ltd.||Bit stream signal feature detection in a signal processing system|
|US5912709 *||Nov 28, 1994||Jun 15, 1999||Matsushita Electric Industrial Co., Ltd.||Method and apparatus for editing or mixing compressed pictures|
|US5946043||Dec 31, 1997||Aug 31, 1999||Microsoft Corporation||Video coding using adaptive coding of block parameters for coded/uncoded blocks|
|US5955977||Mar 31, 1997||Sep 21, 1999||Sharp Laboratories Of America, Inc.||System for avoiding start code emulation and long carry-over propagation|
|US5956090||Jul 23, 1997||Sep 21, 1999||Oki Electric Industry Co., Ltd.||Television standards converter with time-code conversion function|
|US5959796||Mar 13, 1996||Sep 28, 1999||Matsushita Electric Industrial Co., Ltd.||Method of transmitting digital video and audio signals between bit rate reduction encoded signal recording and reproducing systems|
|US5970173||Jun 4, 1996||Oct 19, 1999||Microsoft Corporation||Image compression and affine transformation for image motion compensation|
|US5973743||Dec 2, 1997||Oct 26, 1999||Daewoo Electronics Co., Ltd.||Mode coding method and apparatus for use in an interlaced shape coder|
|US6018765||Jan 23, 1997||Jan 25, 2000||Storage Concepts, Inc.||Multi-channel multimedia data server|
|US6061399 *||May 28, 1997||May 9, 2000||Sarnoff Corporation||Method and apparatus for information stream frame synchronization|
|US6075576||Jul 3, 1997||Jun 13, 2000||Matsushita Electric Industrial Co., Ltd.||Method for display time stamping and synchronization of multiple video object planes|
|US6169573||Jul 3, 1997||Jan 2, 2001||Hotv, Inc.||Hypervideo system and method with object tracking in a compressed digital video environment|
|US6188428||Feb 11, 1992||Feb 13, 2001||Mark Koz||Transcoding video file server and methods for its use|
|US6198773||Dec 18, 1997||Mar 6, 2001||Zoran Corporation||Video memory management for MPEG video decode and display system|
|US6201927||Feb 13, 1998||Mar 13, 2001||Mary Lafuze Comer||Trick play reproduction of MPEG encoded signals|
|US6266158||Jan 21, 1998||Jul 24, 2001||Matsushita Electric Industrial Co., Ltd.||Image encoding/decoding device and method|
|US6301428||Dec 9, 1997||Oct 9, 2001||Lsi Logic Corporation||Compressed video editor with transition buffer matcher|
|US6330214||Sep 28, 1998||Dec 11, 2001||Sony Corporation||Signal recording/reproducing apparatus and method|
|US6380991||Nov 19, 1998||Apr 30, 2002||Tektronix, Inc.||Method for splicing MPEG-2 transport streams|
|US6414998||Jan 27, 1998||Jul 2, 2002||Sony Corporation||Method and apparatus for inserting an image material|
|US6415326||Sep 15, 1998||Jul 2, 2002||Microsoft Corporation||Timeline correlation between multiple timeline-altered media streams|
|US6434195 *||Nov 20, 1998||Aug 13, 2002||General Instrument Corporaiton||Splicing of video data in progressively refreshed video streams|
|US6442604||Dec 31, 1997||Aug 27, 2002||Koninklijke Philips Electronics N.V.||Incremental archiving and restoring of data in a multimedia server|
|US6453115 *||Aug 31, 2000||Sep 17, 2002||Keen Personal Media, Inc.||Digital video recording system which generates an index data structure for displaying a video stream in trickplay mode|
|US6470135 *||Nov 8, 1999||Oct 22, 2002||Lg Electronics Inc.||Method and apparatus for recording digital data streams|
|US6499060||Mar 12, 1999||Dec 24, 2002||Microsoft Corporation||Media coding for loss recovery with remotely predicted data units|
|US6512882 *||May 7, 1999||Jan 28, 2003||Koninklijke Philips Electronics N.V.||Method of storing digital audio and/or video programs compressed on the basis of groups of pictures (gops) on a medium with immediate jumping between groups through co-storage of transport stream packets and pointer information, a method for reading such information, and a device for storing and/or reading such information|
|US6529555 *||Aug 25, 2000||Mar 4, 2003||Sony United Kingdom Limited||Signal processor|
|US6532333 *||Nov 18, 1998||Mar 11, 2003||Kabushiki Kaisha Toshiba||System and method for editing video information|
|US6567471 *||Mar 25, 1999||May 20, 2003||Sony Corporation||System method and apparatus for seamlessly splicing data|
|US6584273 *||Jun 15, 1999||Jun 24, 2003||Koninklijke Philips Electronics N.V.||Frame-accurate editing of encoded A/V sequences|
|US6611624 *||Oct 15, 1998||Aug 26, 2003||Cisco Systems, Inc.||System and method for frame accurate splicing of compressed bitstreams|
|US6728317||Apr 7, 2000||Apr 27, 2004||Dolby Laboratories Licensing Corporation||Moving image compression quality enhancement using displacement filters with negative lobes|
|US6735253||May 16, 1997||May 11, 2004||The Trustees Of Columbia University In The City Of New York||Methods and architecture for indexing and editing compressed video over the world wide web|
|US6765963||Jun 18, 2001||Jul 20, 2004||Nokia Corporation||Video decoder architecture and method for using same|
|US6823010 *||Oct 14, 1999||Nov 23, 2004||France Telecom Sa||Method for switching a first digital audio-visual program video component(s) on a second digital audio-visual program video component(s)|
|US6873629||Dec 20, 2000||Mar 29, 2005||Koninklijke Philips Electronics N.V.||Method and apparatus for converting data streams|
|US6912251||Jul 2, 1999||Jun 28, 2005||Sarnoff Corporation||Frame-accurate seamless splicing of information streams|
|US6920175||Aug 9, 2001||Jul 19, 2005||Nokia Corporation||Video coding architecture and methods for using same|
|US6985188||Nov 30, 1999||Jan 10, 2006||Thomson Licensing||Video decoding and channel acquisition system|
|US7027509 *||Mar 6, 2001||Apr 11, 2006||Lg Electronics Inc.||Hierarchical hybrid shot change detection method for MPEG-compressed video|
|US7164844||Sep 21, 2000||Jan 16, 2007||The Directv Group, Inc.||Method and apparatus for facilitating reverse playback|
|US7177522||Oct 9, 2001||Feb 13, 2007||Broadcom Corporation||System and method for personal video recording|
|US7242716||Apr 9, 2003||Jul 10, 2007||Kabushiki Kaisha Toshiba||Video encoding method and apparatus and video decoding method and apparatus|
|US7609762 *||Nov 15, 2004||Oct 27, 2009||Microsoft Corporation||Signaling for entry point frames with predicted first field|
|US20020041628 *||Dec 29, 2000||Apr 11, 2002||Roger Andersson||Method and apparatus for splicing|
|US20020061183 *||Oct 9, 2001||May 23, 2002||Macinnis Alexander G.||System and method for personal video recording|
|US20020163532 *||Mar 30, 2001||Nov 7, 2002||Koninklijke Philips Electronics N.V.||Streaming video bookmarks|
|US20030053416||Sep 19, 2001||Mar 20, 2003||Microsoft Corporation||Generalized reference decoder for image or video processing|
|US20030156640||Jan 22, 2003||Aug 21, 2003||Sullivan Gary J.||Methods and systems for encoding and decoding video data to enable random access and splicing|
|US20030194010||Mar 4, 2003||Oct 16, 2003||Microsoft Corporation||Chrominance motion vector rounding|
|US20030231863||Apr 4, 2003||Dec 18, 2003||Koninklijke Philips Electronics N.V.||Trick play signal generation for a digital video recorder using retrieved intra-encoded pictures and generated inter-encoded pictures|
|US20040190770||Jul 24, 2002||Sep 30, 2004||Eastman Kodak Company||Producing an extended color gamut luminance-chrominance digital image from a captured image|
|US20040264578||Jun 26, 2003||Dec 30, 2004||Lsi Logic Corporation||Method and/or apparatus for decoding an intra-only MPEG-2 stream composed of two separate fields encoded as a special frame picture|
|US20050099869 *||Nov 15, 2004||May 12, 2005||Microsoft Corporation||Field start code for entry point frames with predicted first field|
|US20050111547||Nov 15, 2004||May 26, 2005||Microsoft Corporation||Signaling reference frame distances|
|US20050123274||Nov 15, 2004||Jun 9, 2005||Microsoft Corporation||Signaling coding and display options in entry point headers|
|US20050135783||Nov 15, 2004||Jun 23, 2005||Microsoft Corporation||Trick mode elementary stream and receiver system|
|US20050152448||Nov 15, 2004||Jul 14, 2005||Microsoft Corporation||Signaling for entry point frames with predicted first field|
|US20060013568||Jul 14, 2004||Jan 19, 2006||Rodriguez Arturo A||System and method for playback of digital video pictures in compressed streams|
|USRE36015||Oct 2, 1995||Dec 29, 1998||Matsushita Electric Corporation Of America||Apparatus and method for processing groups of fields in a video data compression system|
|USRE36507||Oct 21, 1997||Jan 18, 2000||Matsushita Electric Corporation Of America||Apparatus and method for processing groups of fields in a video data compression system to encode a single frame as an I-field and a P-field|
|USRE37222||Jul 19, 1994||Jun 12, 2001||Sony Corporation||Video signal transmitting system|
|CA2257577A1||Apr 7, 1998||Oct 15, 1998||At&T Corp.||System and method for interfacing mpeg-coded audiovisual objects permitting adaptive control|
|EP0886398A1||Mar 18, 1997||Dec 23, 1998||Kabushiki Kaisha Toshiba||Encoder and decoder|
|EP0948214A2||Mar 2, 1999||Oct 6, 1999||Nds Limited||Method and apparatus for detecting a start code in a bitstream|
|EP1018840A2||Dec 7, 1999||Jul 12, 2000||Canon Kabushiki Kaisha||Digital receiving apparatus and method|
|EP1043892A1||Mar 16, 2000||Oct 11, 2000||Sony Corporation||Recording and playing back packetized video programs|
|EP1069777A1||Feb 4, 2000||Jan 17, 2001||Sony Corporation||Encoding system, encoding method, decoding system, decoding method, multiplexing device, multiplexing method, display system and display method|
|EP1079631A1||Aug 7, 2000||Feb 28, 2001||Sony United Kingdom Limited||Switching between bit-rate reduced signals|
|EP1111932A2||Nov 30, 2000||Jun 27, 2001||Sony Corporation||Information processing apparatus, information processing method and recording medium|
|WO1999027713A2 *||Nov 20, 1998||Jun 3, 1999||Koninklijke Philips Electronics N.V.||Video buffer for seamless splicing of mpeg streams|
|WO1999056472A1||Apr 23, 1999||Nov 4, 1999||Rockwell Science Center, Llc||N-bit video coder and method of extending an 8-bit mpeg video coder|
|WO2000056077A1||Mar 3, 2000||Sep 21, 2000||Microsoft Corporation||Media coding for loss recovery with remotely predicted data units|
|WO2000064186A2||Mar 31, 2000||Oct 26, 2000||Ravisent Technologies, Inc.||Memory management method for high speed streaming data processing in a computer device|
|WO2001035650A1||Nov 2, 2000||May 17, 2001||Thomson Licensing S.A.||Improvements to dvd navigation information for improved trick modes|
|1||*||"Packetized Elementary Stream Headers". Mar. 2004. Retrieved Apr. 2008. .|
|2||*||"Packetized Elementary Stream Headers". Mar. 2004. Retrieved Apr. 2008. <http://dvd.sourceforge.net/dvdinfo/pes-hdr.html>.|
|3||Andersen, "A Proposed Method for Creating VCR Functions using MPEG Streams," Proc. 12th Int'l Conf. on Data Engineering (ICDE), pp. 380-382 (1996).|
|4||Anonymous, "DivX Multi Standard Video Encoder," 2 pp. (Downloaded from the World Wide Web on Jan. 24, 2006).|
|5||*||ISO/IEC Standard 11172, Coding of Moving Pictures and Associated Audio (MPEG-1), Part 2: Video. Nov. 1991.|
|6||ISO/IEC, "DSM-CC FAQ Version 1.0," 12 pp. (1997) [Downloaded from the World Wide Web on Oct. 25, 2005].|
|7||ISO/IEC, "Information Technology-Coding of Audio-Visual Objects: Visual, ISO/IEC 14496-2, Committee Draft," 330 pp. (1998).|
|8||ISO/IEC, "Information Technology—Coding of Audio-Visual Objects: Visual, ISO/IEC 14496-2, Committee Draft," 330 pp. (1998).|
|9||ISO/IEC, "ISO/IEC 11172-2: Information Technology-Coding of Moving Pictures and Associated Audio for Storage Media at up to About 1,5 Mbit/s," 122 pp. (1993).|
|10||ISO/IEC, "ISO/IEC 11172-2: Information Technology—Coding of Moving Pictures and Associated Audio for Storage Media at up to About 1,5 Mbit/s," 122 pp. (1993).|
|11||ISO/IEC, "ISO/IEC 13818-1: Information Technology-Generic Coding of Moving Pictures and Associated Audio Information: Systems," 174 pp., (2000).|
|12||ISO/IEC, "ISO/IEC 13818-1: Information Technology—Generic Coding of Moving Pictures and Associated Audio Information: Systems," 174 pp., (2000).|
|13||ISO/IEC, "ISO/IEC 13818-2: Information Technology-Generic Coding of Moving Pictures and Associated Audio Information: Video-Amendment 1: Content Description Data," 23 pp. (Document dated Dec. 2001).|
|14||ISO/IEC, "ISO/IEC 13818-2: Information Technology—Generic Coding of Moving Pictures and Associated Audio Information: Video—Amendment 1: Content Description Data," 23 pp. (Document dated Dec. 2001).|
|15||ISO/IEC, "ISO/IEC 13818-4: Information Technology-Generic Coding of Moving Pictures and Associated Audio Information-Part 4: Conformance testing," 79 pp. (1998).|
|16||ISO/IEC, "ISO/IEC 13818-4: Information Technology—Generic Coding of Moving Pictures and Associated Audio Information—Part 4: Conformance testing," 79 pp. (1998).|
|17||ISO/IEC, "ISO/IEC 13818-6: Information Technology-Generic Coding of Moving Pictures and Associated Audio Information-Part 6: Extensions for DSM-CC," pp. ii-9, 136-147, 204, 205, 222-224, 279-290, 311-318, 399-401 (1998).|
|18||ISO/IEC, "ISO/IEC 13818-6: Information Technology—Generic Coding of Moving Pictures and Associated Audio Information—Part 6: Extensions for DSM-CC," pp. ii-9, 136-147, 204, 205, 222-224, 279-290, 311-318, 399-401 (1998).|
|19||ISO/IEC, Draft ISO/IEC 11172-2, "Coding of Moving Pictures and Associated Audio for Digital Storage Media at up to About 1.5 Mbit/s," Part 2: Video, SS 18.104.22.168 (Nov. 1991).|
|20||ITU-T, "ITU-T Recommendation H.261: Video Codec for Audiovisual Services at p ×64 kbits," 28 pp. (1993).|
|21||ITU-T, "ITU-T Recommendation H.262: Information Technology-Generic Coding of Moving Pictures and Associated Audio Information: Videol," 218 pp. (1995).|
|22||ITU-T, "ITU-T Recommendation H.262: Information Technology—Generic Coding of Moving Pictures and Associated Audio Information: Videol," 218 pp. (1995).|
|23||ITU-T, "ITU-T Recommendation H.263: Video Coding for Low Bit Rate Communication," 167 pp. (1998).|
|24||ITU-T, "ITU-T Recommendation H.320: Infrastructure of Audiovisual Services-Systems and Terminal Equipment for Audiovisual Services: Narrow-band Visual Telephone Systems and Terminal Equipment," 31 pp. (1999).|
|25||ITU-T, "ITU-T Recommendation H.320: Infrastructure of Audiovisual Services—Systems and Terminal Equipment for Audiovisual Services: Narrow-band Visual Telephone Systems and Terminal Equipment," 31 pp. (1999).|
|26||Joint Video Team of ISO/IEC MPEG and ITU-T VCEG, "Final Joint Committee Draft of Joint Video Specification (ITU-T Recommendation H.264, ISO/IEC 14496-10 AVC," 206 pp. (Aug. 2002).|
|27||Joint Video Team of ISO/IEC MPEG and ITU-T VCEG, "Joint Model No. 1, Revision 1 (JM-1r1)," 80 pp. (Document dated Jan. 2002) [Downloaded from the World Wide Web on May 6, 2005].|
|28||Joint Video Team of ISO/IEC MPEG and ITU-T VCEG, "Study of Final Committee Draft of Joint Video Specification (ITU-T Rec. H.264, ISO/IEC 14496-10 AVC," 257 pp. (Document dated Dec. 2002) [Downloaded from the World Wide Web on May 6, 2005].|
|29||Lei, "The construction of efficient variable-length codes with clear synchronizing codewords for digital video applications," SPIE Visual Comm. & Image Processing '91: Visual Comm., vol. 1605, pp. 863-873 (1991).|
|30||Microsoft Corporation, "Microsoft Debuts New Windows Media Player 9 Series, Redefining Digital Media on the PC," 4 pp. (Sep. 4, 2002) [Downloaded from the World Wide Web on May 14, 2004].|
|31||Miranda Technologies, Inc., "TCP-101i: Time Code Processor and Remote Control Panel," 1 p. (Downloaded from the World Wide Web on Oct. 22, 2005).|
|32||Mook, "Next-Gen Windows Media Player Leaks to the Web," BetaNews, 17 pp. (Jul. 19, 2002) [Downloaded from the World Wide Web on Aug. 8, 2003].|
|33||Notice on Grant of Patent Right for Invention dated Sep. 4, 2009, from Chinese Patent Application No. 200410095789.X, 4 pp.|
|34||Notice on Office Action dated Aug. 1, 2008, from Chinese Patent Application No. 200410095789.X, 19 pp.|
|35||Office action dated Aug. 1, 2008, from Chinese Patent Application No. 200410095789.X, 19 pp.|
|36||Office action dated Mar. 13, 2009, from Chinese Patent Application No. 200410095789.X, 11 pp.|
|37||Printouts of FTP directories from http://ftp3.itu.ch , 8 pp. (downloaded from the World Wide Web on Sep. 20, 2005.)|
|38||Reader, "History of MPEG Video Compression-Ver. 4.0," 99 pp., document marked Dec. 16, 2003.|
|39||Reader, "History of MPEG Video Compression—Ver. 4.0," 99 pp., document marked Dec. 16, 2003.|
|40||Schwalb, "iTV Food Chain," Prentice Hall Professional Technical Reference, 35 pp. (Oct. 2003) [Downloaded from the World Wide Web on Oct. 22, 2005].|
|41||Second Office Action dated Mar. 13, 2009, from Chinese Patent Application No. 200410095789.X, 11 pp.|
|42||Stockhammer et al., "H.26L/JVT Coding Network Abstraction Layer and IP-based Transport," Proc. 2002 Int'l Conf. on Image Processing: ICIP 2002, pp. 485-488 (Sep. 2002).|
|43||Sullivan, "Header-Level Needs for H.26L," ITU-T, Study Group 16, Questions 15/16, 6 pp. (Dec. 2001).|
|44||Sullivan, "On Random Access and Bitstream Format for JVT Video," JVT-B063, 10 pp. (document marked Jan. 23, 2002).|
|45||Sun, H., et al., "Architectures for MPEG Compressed Bitstream Scaling," IEEE Transactions on Circuits and Systems for Video Technology, vol. 6, No. 2, pp. 191-199 (Apr. 1996).|
|46||Suzuki et al., "Group of Pictures for JVT Codec," ITU-T, Study Group 16, Question 6, 4 pp. (Document dated Jan. 2002) [Downloaded from the World Wide Web on May 6, 2005].|
|47||Suzuki et al., "Tool to Support Random Access," ITU-T, Study Group 16, Question 6, 3 pp. (Document dated Dec. 2001) [Downloaded from the World Wide Web on May 6, 2005].|
|48||Suzuki, "AHG Report: GOP Syntax," ITU-T, Study Group 16, Question 6, 1 p. (Document dated Dec. 2002) [Downloaded from the World Wide Web on May 6, 2005].|
|49||U.S. Appl. No. 60/341/674, filed Dec. 17, 2001, Lee et al.|
|50||U.S. Appl. No. 60/488,710, filed Jul. 18, 2003, Srinivasan et al.|
|51||U.S. Appl. No. 60/501,081, filed Sep. 7, 2003, Srinivasan et al.|
|52||U.S. Appl. No. 60/501,133, filed Sep. 7, 2003, Srinivasan et al.|
|53||Wien, "Variable Block-Size Transforms for Hybrid Video Coding," Dissertation, 182 pp. (Feb. 2004).|
|54||Williams, "All in Good Timcode," Adobe Magazine, 3 pp. (Spring 1999).|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8787441 *||Jul 5, 2006||Jul 22, 2014||Thomson Licensing||Device and method for coding and decoding video data and data train|
|US8873070 *||Jan 17, 2007||Oct 28, 2014||Canon Kabushiki Kaisha||Image processing apparatus and method of starting image processing apparatus|
|US9560384||Oct 17, 2012||Jan 31, 2017||Kt Corporation||Method and apparatus for encoding/decoding image|
|US9560385||Jan 26, 2015||Jan 31, 2017||Kt Corporation||Method and apparatus for encoding/decoding image|
|US9621909||Jul 2, 2013||Apr 11, 2017||Lg Electronics Inc.||Method for decoding image and apparatus using same|
|US20070206211 *||Jan 17, 2007||Sep 6, 2007||Canon Kabushiki Kaisha||Image processing apparatus and method of starting image processing apparatus|
|US20080240227 *||Mar 30, 2007||Oct 2, 2008||Wan Wade K||Bitstream processing using marker codes with offset values|
|US20090279599 *||Jul 5, 2006||Nov 12, 2009||Frederic Pasquier||Device and Method for Coding and Decoding Video Data and Data Train|
|US20110026593 *||Jan 14, 2010||Feb 3, 2011||New Wei Lee||Image processing apparatus, image processing method, program and integrated circuit|
|U.S. Classification||375/240.13, 348/550, 375/240.12, 348/305|
|International Classification||H04N7/173, H04N5/91, H04N3/10, H04N7/26, H04N7/32, H04N19/00, H04N21/83, H04N21/438|
|Cooperative Classification||H04N21/23424, H04N21/8455, H04N21/44016|
|European Classification||H04N21/44S, H04N21/845P, H04N21/234S|
|Jun 30, 2004||AS||Assignment|
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOLCOMB, THOMAS W.;CRINON, REGIS J.;ONDERS, TIMOTHY E.;AND OTHERS;REEL/FRAME:015557/0236
Effective date: 20040630
|Aug 23, 2004||AS||Assignment|
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOLCOMB, THOMAS W.;CRINON, REGIS J.;ONDERS, TIMOTHY E.;AND OTHERS;REEL/FRAME:015079/0174
Effective date: 20040630
|Apr 24, 2014||FPAY||Fee payment|
Year of fee payment: 4
|Dec 9, 2014||AS||Assignment|
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0477
Effective date: 20141014