3GPPFDD ULPhyCHSeg

3GPPFDD_ULPhyCHSeg

Description: Uplink physical channel segmentation
Library: 3GPPFDD, TrCH Multiplexers & Coders
Class: SDF3GPPFDD_ULPhyCHSeg
Derived From: 3GPPFDD_ULCCTrCHBase

Parameters

Pin Inputs

Pin Outputs

Notes/Equations

1. This model is used to implement uplink physical channel segmentation. When more than one PhCH is used, physical channel segmentation divides the bits among the different PhCHs. Bits input to the physical channel segmentation are denoted by x 1, x 2, x 3, ... , x_Y, where Y is the number of bits input to the physical channel segmentation block. The number of PhCHs is denoted by P.
   The bits after physical channel segmentation are denoted u_p 1, u_p 2, u_p 3, ... , u_pU, where p is PhCH number and U is the number of bits in one radio frame for each PhCH, i.e.

   .

   The relation between x_k and u_pk is given next.
   For all modes, some bits of the input flow are mapped to each code until the number of bits on the code is V. For modes other than compressed mode by puncturing, all bits of the input flow are taken to be mapped to the codes. For compressed mode by puncturing, only the bits of the input flow not corresponding to bits p are taken to be mapped to the codes, each bit p is removed to ensure creation the gap required by the compressed mode, as described next.
   Bits on first PhCH after physical channel segmentation:

   u 1_,k = x_i,k k = 1, 2, ... , U

   Bits on second PhCH after physical channel segmentation:

   u 2_,k = x_i,k+U k = 1, 2, ... , U
   .
   .
   .

   Bits on the Pth PhCH after physical channel segmentation:

   u_P,k = x_{i,k + (P-1)U} k = 1, 2, ... , U

2. This model fires once per radio frame. Each firing, this model receives a data block of one CCTrCH at pin DataIn, and receives slot format and physical channel number at pins SltFin and PCNin. This model will divide the input data block if physical channel number is more than one, then output resulting data blocks through multiple output pin DataOut. Slot format and physical channel number will be output through pin SltFout and PCNout.
3. All transport channel information must be in the form of arrays.
   The DynTFSetArray parameter requires an integer array. The correct format is transport block size 1, transport block set size 1, transport block size 2, transport block set size 2 , etc. The size of this array must be a multiple of 2, and the transport block set size must be a multiple of the relative transport block size.
   TFSetSizeArray indicates how many pairs of transport block and transport block set sizes are contained in a certain transport channel. For example:

   • TFSetSizeArray = "3 2" means the first three pairs of transport block size and transport block set size belong to the first transport channel, and the next two pairs belong to the second transport channel.
   • TFSetSizeArray = "2 2 2" means the first two pairs of transport block size and transport block set size belong to the first transport channel, the next two pairs belong to the second transport channel and the last two pairs belong to the third transport channel.

   When setting TTIArray, CRCArray and CHCodingTypeArray values, refer to the following table.
   
   

   TTIArray		CRCArray		CHCodingTypeArray
   Time	Value	Coding	Value	Coding	Value
   10 msec	0	No CRC	0	No Coding	0
   20 msec	1	8 bits	1	1/2 CC	1
   40 msec	2	12 bits	2	1/3 CC	2
   80 msec	3	16 bits	3	1/3 TC	3
   		24 bits	4
   CC = convolutional coding; TC = turbo coding

4. The PuncLimit parameter denotes the variable PL defined in [1]. Refer to [1] for the details regarding the use of this variable in rate matching algorithm.

References

1. 3GPP Technical Specification TS 25.212 V3.9.0, Multiplexing and Channel Coding (FDD) 2002-03, Release 1999.

   http://www.3gpp.org/ftp/Specs/2002-03/R1999/25_series/25212-390.zip