Debian Codegraph @

rfc2029.html

raw
1 <pre>Network Working Group M. Speer
2 Request for Comment: 2029 D. Hoffman
3 Category: Standards Track Sun Microsystems, Inc.
4 October 1996
5
6
7 <span class="h1">RTP Payload Format of Sun's CellB Video Encoding</span>
8
9 Status of this Memo
10
11 This document specifies an Internet standards track protocol for the
12 Internet community, and requests discussion and suggestions for
13 improvements. Please refer to the current edition of the "Internet
14 Official Protocol Standards" (STD 1) for the standardization state
15 and status of this protocol. Distribution of this memo is unlimited.
16
17 Abstract
18
19 This memo describes a packetization scheme for the CellB video
20 encoding. The scheme proposed allows applications to transport CellB
21 video flows over protocols used by RTP. This document is meant for
22 implementors of video applications that want to use RTP and CellB.
23
24 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
25
26 The Cell image compression algorithm is a variable bit-rate video
27 coding scheme. It provides "high" quality, low bit-rate image
28 compression at low computational cost. The bytestream that is
29 produced by the Cell encoder consists of instructional codes and
30 information about the compressed image.
31
32 For futher information on Cell compression technology, refer to [1].
33 Currently, there are two versions of the Cell compression technology:
34 CellA and CellB. CellA is primarily designed for the encoding of
35 stored video intended for local display, and will not be discussed in
36 this memo.
37
38 CellB, derived from CellA, has been optimized for network-based video
39 applications. It is computationally symmetric in both encode and
40 decode. CellB utilizes a fixed colormap and vector quantization
41 techniques in the YUV color space to achieve compression.
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Speer &amp; Hoffman Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2029">RFC 2029</a> RTP Payload Format October 1996</span>
55
56
57 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Network Packetization and Encapsulation</span>
58
59 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> RTP Usage</span>
60
61 The RTP timestamp is in units of 90KHz. The same timestamp value is
62 used for all packet payloads of a frame. The RTP maker bit denotes
63 the end of a frame.
64
65 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> CellB Header</span>
66
67 The packetization of the CellB bytestream is designed to make the
68 resulting packet stream robust to packet loss. To achieve this goal,
69 an additional header is added to each RTP packet to uniquely identify
70 the location of the first cell of the packet within the current
71 frame. In addition, the width and height of the frame in pixels is
72 carried in each CellB packet header. Although the size can only
73 change between frames, it is carried in every packet to simplify the
74 packet encoding.
75
76 0 1 2 3
77 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
78 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
79 | Cell X Location | Cell Y Location |
80 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
81 | Width of Image | Height of Image |
82 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
83 | Compressed CellB Data |
84 | .... |
85 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
86
87 All fields are 16-bit unsigned integers in network byte order, and
88 are placed at the beginning of the payload for each RTP packet. The
89 Cell X and the Cell Y Location coordinates are expressed as cell
90 coordinates, not pixel coordinates. Since cells represent 4x4 blocks
91 of pixels, the X or Y dimension of the cell coordinates range in
92 value from 0 through 1/4 of the of the same dimension in pixel
93 coordinates.
94
95 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> Packetization Rules</span>
96
97 A packet can be of any size chosen by the implementor, up to a full
98 frame. All multi-byte codes must be completely contained within a
99 packet. In general, the implementor should avoid packet sizes that
100 result in fragmentation by the network.
101
102
103
104
105
106
107
108 <span class="grey">Speer &amp; Hoffman Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2029">RFC 2029</a> RTP Payload Format October 1996</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. References</span>
114
115 1. "Cell Image Compression Byte Stream Description,"
116 <a href="ftp://playground.sun.com:/pub/multimedia/video/cellbytestream.ps.Z">ftp://playground.sun.com:/pub/multimedia/video/</a>
117 <a href="ftp://playground.sun.com:/pub/multimedia/video/cellbytestream.ps.Z">cellbytestream.ps.Z</a>
118
119 2. Turletti, T., and C. Huitema, "RTP Payload Format
120 for H.261 Video Streams", <a href="./rfc2032">RFC 2032</a>, October 1996.
121
122 3. Schulzrinne, H., Casner, S., Frederick, R., and
123 V. Jacobson, "RTP: A Transport Protocol for Real-Time
124 Applications", <a href="./rfc1889">RFC 1889</a>, January 1996.
125
126 4. Schulzrinne, H., "RTP Profile for Audio and Video
127 Conferences with Minimal Control", <a href="./rfc1890">RFC 1890</a>,
128 January 1996.
129
130 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> Authors' Addresses</span>
131
132 Michael F. Speer
133 Sun Microsystems Computer Corporation
134 2550 Garcia Ave MailStop UMPK14-305
135 Mountain View, CA 94043
136
137 Voice: +1 415 786 6368
138 Fax: +1 415 786 6445
139 EMail: [email protected]
140
141
142 Don Hoffman
143 Sun Microsystems Computer Corporation
144 2550 Garcia Ave MailStop UMPK14-305
145 Mountain View, CA 94043
146
147 Voice: +1 415 786 6370
148 Fax: +1 415 786 6445
149 EMail: [email protected]
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Speer &amp; Hoffman Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2029">RFC 2029</a> RTP Payload Format October 1996</span>
167
168
169 Appendix A - Structure of the CellB Video Stream
170
171 The CellB bytestream consists of cell codes, skip codes and
172 quantization-table specific codes. These are now described.
173
174 <span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a> CellB Cell Code</span>
175
176 Cell codes are 4 bytes in length, and describe a 4x4 pixel cell.
177 There are two possible luminance (Y) levels for each cell, but only
178 one pair of chrominance (UV) values. The CellB cell code is shown
179 below:
180
181
182 0 1 2 3
183 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
185 |0 M M M M M M M M M M M M M M M|U V U V U V U V|Y Y Y Y Y Y Y Y|
186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
187 4x4 Bitmask U/V Code Y/Y Code
188
189 The first two bytes of the cell code are a bitmask. Each bit in the
190 mask represents a pixel in a 16-pixel cell. Bit 0 represents the
191 value of the upper right-hand pixel of the cell, and subsequent bits
192 represent the pixels in row-major order. If a pixel's bit is set in
193 the 4x4 Bitmask, then the pixel will be rendered with the pixel value
194 &lt;Y(1), U, V&gt;. If the pixel's bit is not set in the bitmask, then the
195 pixel's value will be rendered with the value &lt;Y(0), U, V&gt;. The
196 bitmask for the cell is normalized so that the most significant bit
197 is always 0 (i.e., corresponding to &lt;Y(0), U, V&gt;).
198
199 The U/V field of the cell code represents the chrominance component.
200 This code is in index into a table of vectors that represents two
201 independent components of chrominance.
202
203 The Y/Y field of the cell code represents two luminance values (Y(0)
204 and Y(1)). This code is an index into a table of two-compoment
205 luminance vectors.
206
207 The derivation of the U/V and Y/Y tables is outside the scope of this
208 memo. A complete discussion can be found in [1].
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Speer &amp; Hoffman Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2029">RFC 2029</a> RTP Payload Format October 1996</span>
223
224
225 <span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a> CellB Skip Code</span>
226
227 The single byte CellB skip code tells the CellB decoder to skip the
228 next S+1 cells in the current video frame being decoded. The maximum
229 number of cells that can be skipped is 32. The format of the skip
230 code is shown below.
231
232 0 1 2 3 4 5 6 7
233 +-+-+-+-+-+-+-+-+
234 |1 0 0 S S S S S|
235 +-+-+-+-+-+-+-+-+
236
237 <span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a> CellB Y/Y Table Code</span>
238
239 The single byte "new Y/Y table" code is used to tell the decoder that
240 the next 512 bytes are a new Y/Y quantization table. The code and
241 the representation of the table are shown below. The sample
242 encoder/decoder pair in this document do not implement this feature
243 of the CellB compression. However, future CellB codecs may implement
244 this feature.
245
246 0 1 2 3 4 5 6 7
247 +-+-+-+-+-+-+-+-+
248 |1 1 1 1 1 1 1 0|
249 +-+-+-+-+-+-+-+-+
250
251 The format of the new Y/Y table is:
252
253 0 1 2 3
254 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
256 | Y1_000 | Y2_000 | Y1_001 | Y2_001 |
257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
258
259 .
260 .
261 .
262
263 0 1 2 3
264 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
266 | Y1_254 | Y2_254 | Y1_255 | Y2_255 |
267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
268
269
270
271
272
273
274
275
276 <span class="grey">Speer &amp; Hoffman Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2029">RFC 2029</a> RTP Payload Format October 1996</span>
279
280
281 <span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a> CellB U/V Table Code</span>
282
283 The single byte "new U/V table" code is used to tell the decoder that
284 the next 512 bytes represent a new U/V quantization table. The code
285 is shown below. The sample encoder/decoder pair provided in this
286 document do not implement this feature of the CellB compression.
287 However, future CellB codecs may implement this feature.
288
289 0 1 2 3 4 5 6 7
290 +-+-+-+-+-+-+-+-+
291 |1 1 1 1 1 1 1 1|
292 +-+-+-+-+-+-+-+-+
293
294 The bytes of the new U/V quantization table are arranged as:
295
296 0 1 2 3
297 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
299 | U_000 | V_000 | U_001 | V_001 |
300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
301
302 .
303 .
304 .
305
306 0 1 2 3
307 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
309 | U_254 | V_254 | U_255 | V_255 |
310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
311
312 Appendix B - Availability of CellB
313
314 It is the viewpoint of Sun Microsystems, Inc, that CellB is
315 publically available for use without any license.
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332 Speer &amp; Hoffman Standards Track [Page 6]
333 </pre>