Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 26.346  Word version:  19.1.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.3…   6   7…   7.3…   8…   8A…   8B…   9…   9.4…   10…   11…   12…   A   B…   C…   D…   G…   H…   J…   K…   L…   M…

 

B (Normative)  FEC encoder specificationp. 204

This Annex specifies the systematic Raptor Forward Error Correction code (see RFC 5053) and its application to MBMS. Raptor is a fountain code, i.e., as many encoding symbols as needed can be generated on the fly by the encoder from the source symbols of a block. The decoder is able to recover the source block from any set of encoding symbols only slightly more in number than the number of source symbols.
The code described in this document is a Systematic code, that is, the original source symbols are sent unmodified from sender to receiver, as well as a number of repair symbols.
Up

B.1Void

B.2Void

B.3  File downloadp. 204

B.3.1Void

B.3.2Void

B.3.3Void

B.3.4  Example parametersp. 204

B.3.4.1  Parameter derivation algorithmp. 204

Section 4.2 of RFC 5053 provides recommendations for the derivation of the transport parameters G, T, Z and N.
Recommended settings for the input parameters, W, Al, KMIN and GMAX are as follows:
W = 256 KB   Al = 4   KMIN = 1024   GMAX = 10

B.3.4.2  Examplesp. 205

The above algorithm leads to transport parameters as shown in Table B.3.4.2-1 below, assuming the recommended values for W, Al, KMIN and GMAX and P = 512:
File size F G Symbol size T G*T Kt Source blocks Z Sub-blocks N KL KS TL ∙A TS ∙A
100 KB6845041,220111,2201,220N/AN/A
100 KB8645121,600111,6001,600N/AN/A
300 KB22565121,200121,2001,200128128
1,000 KB15125122,000152,0002,000104100
3,000 KB15125126,0001126,0006,0004440
10,000 KB151251220,0003146,6666,6674036
Up

B.4  Streamingp. 205

B.4.1Void

B.4.2Void

B.4.3Void

B.4.4  Example parametersp. 205

B.4.4.1  Parameter derivation algorithmp. 205

This clause provides recommendations for the derivation of the transport parameter T. This recommendation is based on the following input parameters:
  • B   the maximum source block size, in bytes
  • P   the maximum repair packet payload size, in bytes, which is a multiple of Al
  • Al   the symbol alignment factor, in bytes
  • KMAX   the maximum number of source symbols per source block.
  • KMIN   a minimum target on the number of symbols per source block
  • KMIN   a maximum target number of symbols per repair packet
A requirement on these inputs is that ceil(B/P) ≤ KMAX. Based on the above inputs, the transport parameter T is calculated as follows:
Let,
G = min{ceil(P·KMIN/B), P/Al, KMIN} - the approximate number of symbols per packet
T = floor(P/(Al·G))·Al
The value of T derived above should be considered as a guide to the actual value of T used. It may be advantageous to ensure that T divides into P, or it may be advantageous to set the value of T smaller to minimize wastage when full size repair symbols are used to recover partial source symbols at the end of lost source packets (as long as the maximum number of source symbols in a source block does not exceed KMAX). Furthermore, the choice of T may depend on the source packet size distribution, e.g., if all source packets are the same size then it is advantageous to choose T so that the actual payload size of a repair packet P', where P' is a multiple of T, is equal to (or as few bytes as possible larger than) the number of bytes each source packet occupies in the source block.
Recommended settings for the input parameters, Al, KMIN and KMIN are as follows:
Al = 4   KMIN = 1024   KMIN = 10
Up

B.4.4.2  Examplesp. 206

The above algorithm leads to transport parameters as shown in Table B.4.4.2-1 below, assuming the recommended values for Al, KMIN and KMIN and P = 512:
Max source block size B G Symbol size T G∙T
40 KB1048480
160 KB4128512
640 KB1512512
Up

B.5Void

B.6Void

B.7Void

B.8Void


Up   Top   ToC