6 Frame Structure and Coding
25.4353GPPRelease 17TSUTRAN Iub interface user plane protocols for Common Transport Channel data streams
6.1 General
The general structure of a Common Transport Channel frame consists of a header and a payload. This structure is depicted in figure 13.
|
Header |
Payload: Data or Control Information |
Figure 13: General Frame Structure
The header shall contain the Frame Type field and information related to the frame type.
There are two types of frames (indicated by the Frame Type field).
– Data frame.
– Control frame.
In the present document the structure of frames will be specified by using pictures similar to figure 14.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Condition |
||
|
Field 1 |
Field 2 |
Byte 1 |
||||||||
|
Field 3 |
Byte 2 |
|||||||||
|
Field 3 (cont) |
Field 4 |
Byte 3 |
||||||||
|
Spare Extension |
||||||||||
Figure 14: Example frame structure
Unless otherwise indicated, fields which consist of multiple bits within a byte will have the more significant bit located at the higher bit position (indicated above frame in figure 14). In addition, if a field spans several bytes, more significant bits will be located in lower numbered bytes (right of frame in figure 14).
On the Iub interface, the frame will be transmitted starting from the lowest numbered byte. Within each byte, the bits are sent according decreasing bit position (bit position 7 first).
The parameters are specified giving the value range and the step (if not 1). The coding is done as follows (unless otherwise specified):
– Unsigned values are binary coded.
– Signed values are 2’s complement binary coded.
The Spare Extension indicates the location where new IEs can in the future be added in a backward compatible way. The Spare Extension shall not be used by the transmitter and shall be ignored by the receiver.
Bits labelled "Spare" shall be set to zero by the transmitter and shall be ignored by the receiver.
6.2 Data frame structure
6.2.1 RACH Channels
The RACH DATA FRAME includes the CFN corresponding to the SFN of the frame in which the payload was received. If the payload was received in several frames, the CFN corresponding to the first Uu frame in which the information was received shall be indicated.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Header |
||||
|
Header CRC |
FT |
|||||||||||
|
CFN |
||||||||||||
|
spare |
TFI |
|||||||||||
|
Conditional FDD |
||||||||||||
|
Rx Timing Deviation |
Conditional 3.84 Mcps and 7.68Mcps TDD |
|||||||||||
|
Received SYNC UL Timing Deviation |
Conditional 1.28Mcps TDD |
|||||||||||
|
First TB |
Payload |
|||||||||||
|
First TB |
Pad |
|||||||||||
|
Last TB |
||||||||||||
|
Last TB |
Pad |
|||||||||||
|
CRCI of first TB |
||||||||||||
|
CRCI of last TB |
Pad |
|||||||||||
|
New IE Fl 7(E) |
New IE Fl 6 |
New IE Fl 5 |
New IE Fl 4 |
New IE Fl 3 |
New IE Fl 2 |
New IE Fl 1 |
New IE Fl 0 |
|||||
|
Spare 7-6 |
Cell Porting ID |
Conditional FDD |
||||||||||
|
Spare 7-1 bits for 3.84 Mcps Spare 7-2 bits for 7.68 Mcps |
Rx Timing Deviation (continuation) |
Conditional 3.84Mcps or 7.68Mcps |
||||||||||
|
Spare 7-2 |
Ext Propa-gation Delay |
Conditional FDD |
||||||||||
|
Ext Propagation Delay |
Conditional FDD Conditional 1.28Mcps |
|||||||||||
|
Spare 7-2 |
AOA |
|||||||||||
|
AOA |
Conditional 1.28Mcps Conditional 1.28Mcps |
|||||||||||
|
Spare 7-5 |
Ext Received SYNC UL Timing Deviation |
|||||||||||
|
Ext Received SYNC UL Timing Deviation |
Conditional 1.28Mcps |
|||||||||||
|
Cell Portion LCR ID |
Conditional 1.28Mcps |
|||||||||||
|
Spare Extension |
||||||||||||
|
Payload CRC |
||||||||||||
|
Payload CRC (cont) |
||||||||||||
Figure 15: RACH DATA FRAME structure
Propagation Delay is a conditional Information Element which is only present when the Cell supporting the RACH Transport Channel is a FDD Cell.
Rx Timing Deviation is a conditional Information Element which is only present when the Cell supporting the RACH Transport Channel is a 3.84 Mcps or 7.68Mcps TDD Cell.
Received SYNC UL Timing Deviation is a conditional Information Element which is only present when the Cell supporting the RACH Transport Channel is a 1.28Mcps TDD Cell. The RNC shall ignore this IE if the measured Received SYNC UL Timing Deviation is sent in Ext Received SYNC UL Timing Deviation IE
With respect to new IEs, for which the presence is indicated by the New IE Flags IE, the Figure 15 is an example of how a frame is structured when all such new IEs are present. Note that non-presence of such a new IE changes the position of all subsequent IEs on octet level.
[FDD- Bit 0 of New IE Flags in RACH DATA FRAME indicates if a Cell Portion ID is present (1) or not present (0) in the byte (bits 0-5) following the New IE Flags IE.]
[FDD – Bit 1 of New IE Flags in RACH DATA FRAME indicates if Ext Propagation Delay IE is present (1) or not present (0)]
[FDD – Bits 2 through 6 of New IE Flags in RACH DATA FRAME shall be set to 0.]
[FDD – Field length of Spare Extension IE in RACH DATA FRAME is 0-28 octets.]
[3.84 Mcps and 7.68 Mcps TDD – Bit 0 of New IE Flags in RACH DATA FRAME indicates if the extended bits of the Rx Timing Deviation are present (1) or not present (0) in the byte (bit 0 for 3.84 Mcps TDD, bits 0 and 1 for 7.68 Mcps TDD) following the New IE Flags IE. Bits 1 through 6 of New IE Flags in RACH DATA FRAME shall be set to 0. Field length of Spare Extension IE in RACH DATA FRAME is 0-30 octets.]
[1.28Mcps TDD – Bit 0 of New IE Flags in RACH DATA FRAME indicates if the AOA IE is present (1) or not present (0).]
[1.28Mcps TDD – Bit 1 of New IE Flags in RACH DATA FRAME indicates if Ext Received SYNC UL Timing Deviation IE is present (1) or not present (0).]
[1.28Mcps TDD – Bit 2 of New IE Flags in RACH DATA FRAME indicates if Cell Portion LCR IE is present (1) or not present (0).]
[1.28Mcps TDD – Bits 3 through 6 of New IE Flags in RACH DATA FRAME shall be set to 0.]
[1.28Mcps TDD – Field length of Spare Extension IE in RACH DATA FRAME is 0-26 octets.]
6.2.2 CPCH Channels [FDD]
Void.
6.2.3 FACH Channels
FACH DATA FRAME includes the CFN corresponding to the Uu frame at which this data in which the payload (FACH TBS) has to be transmitted. If the payload is to be sent in several frames, the CFN corresponding to the first frame shall be indicated. In case a transport bearer is used by several FACH channels, the CFN and Transmit power level are valid for all these FACH channels.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|||||
|
Header CRC |
FT |
Header |
||||||||||
|
CFN |
||||||||||||
|
Spare |
TFI |
|||||||||||
|
Transmit power level |
||||||||||||
|
First TB |
Payload |
|||||||||||
|
First TB |
Pad |
|||||||||||
|
Last TB |
||||||||||||
|
Last TB |
Pad |
|||||||||||
|
New IE Fl 7(E) |
New IE Fl 6 |
New IE Fl 5 |
New IE Fl 4 |
New IE Fl 3 |
New IE Fl 2 |
New IE Fl 1 |
New IE Fl 0 |
|||||
|
Spare 7 -2 |
AOA |
|||||||||||
|
AOA |
||||||||||||
|
Cell Portion LCR ID |
Conditional 1.28Mcps TDD |
|||||||||||
|
Spare Extension |
||||||||||||
|
Payload CRC |
||||||||||||
|
Payload CRC( cont) |
||||||||||||
Figure 17: FACH DATA FRAME structure
[1.28Mcps TDD – Bit 0 of New IE Flags in FACH DATA FRAME indicates if the AOA IE is present (1) or not present (0).]
[1.28Mcps TDD – Bit 1 of New IE Flags in FACH DATA FRAME indicates if Cell Portion LCR ID IE is present (1) or not present (0).]
[1.28Mcps TDD – Field length of Spare Extension IE in FACH DATA FRAME is 0-29 octets.]
6.2.4 PCH Channels
The PCH DATA FRAME includes the paging indication information and paging messages [FDD – To page one User Equipment, two consecutive PCH DATA FRAMEs with consecutive CFN numbers are transmitted, the first frame contains the Paging Indication Information and the second contains the Paging Message.] [TDD – To page one User Equipment, one or more PCH DATA FRAMEs are trasmitted.]
[TDD – If two or more consecutive frames are used, the first frame contains the Paging Indication Information and the rest contain the Paging Messages. If PI-bitmap and PCH TBS are both transmitted within the PCH DATA FRAME, the CFN is related to the PCH TBS only. The PI bitmap is mapped to the PICH frames, transmitted at the beginning of the paging block.]
The paging messages are transmitted in S-CCPCH frames. The CFN in the PCH DATA FRAME header corresponds to the Cell SFN of the frame in which the start of the S-CCPCH frame is located. [TDD – If the paging messages are to be sent in several frames, the CFN corresponding to the first frame shall be indicated.]
[FDD – The timing of the PICH frame (containing the paging indication information) is PICH prior to the S-CCPCH frame timing (TS 25.211 [5])].
In contrast to all other Common Transport Channel data frames, which use a CFN of length 8, the PCH DATA FRAME includes a CFN of length 12.
The Node B has no responsibility to ensure the consistency between the paging indication information and the corresponding paging messages. E.g. if the paging indication information is lost over the Iub, the paging messages might be sent over the Uu while no UE is actually listening.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|||||
|
Header CRC |
FT |
Header |
||||||||||
|
CFN |
||||||||||||
|
CFN (cont) |
Not Used |
PI |
||||||||||
|
Spare |
TFI |
|||||||||||
|
PI-bitmap |
Payload |
|||||||||||
|
PI-bitmap |
Pad |
|||||||||||
|
First TB |
||||||||||||
|
First TB |
Pad |
|||||||||||
|
Last TB |
||||||||||||
|
Last TB |
Pad |
|||||||||||
|
Spare Extension |
||||||||||||
|
Payload CRC |
||||||||||||
|
Payload CRC( cont) |
||||||||||||
Figure 18: PCH DATA FRAME structure
"Not Used" bits shall be set to 0 by the RNC and ignored by the Node B.
6.2.5 Downlink Shared Channels [TDD]
DSCH DATA FRAME includes a CFN indicating the SFN of the PDSCH in which the payload shall be sent. If the payload is to be sent over several frames, the CFN corresponding to the first frame shall be indicated.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|||||
|
Header CRC |
FT |
Header |
||||||||||
|
CFN |
||||||||||||
|
Spare |
TFI |
|||||||||||
|
PDSCH Set Id |
||||||||||||
|
Transmit power level |
||||||||||||
|
First TB |
Payload |
|||||||||||
|
First TB |
Pad |
|||||||||||
|
Last TB |
||||||||||||
|
Last TB |
Pad |
|||||||||||
|
Spare Extension |
||||||||||||
|
Payload CRC |
||||||||||||
|
Payload CRC (cont) |
||||||||||||
Figure 20: DSCH DATA FRAME structure
6.2.6 Uplink Shared Channels [TDD]
USCH DATA FRAME includes the CFN in which the payload was received. If the payload was received in several frames, the CFN corresponding to the first frame will be indicated.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|||||
|
Header CRC |
FT |
Header |
||||||||||
|
CFN |
||||||||||||
|
Spare |
TFI |
|||||||||||
|
Rx Timing Deviation |
||||||||||||
|
First TB |
Payload |
|||||||||||
|
First TB |
Pad |
|||||||||||
|
Last TB |
||||||||||||
|
Last TB |
Pad |
|||||||||||
|
QE |
||||||||||||
|
CRCI of first TB |
||||||||||||
|
CRCI of last TB |
Pad |
|||||||||||
|
New IE Fl 7(E) |
New IE Fl 6 |
New IE Fl 5 |
New IE Fl 4 |
New IE Fl 3 |
New IE Fl 2 |
New IE Fl 1 |
New IE Fl 0 |
|||||
|
Spare 7-1 bits for 3.84Mcps Spare 7-2 bits for 7.68Mcps |
Rx Timing Deviation (continuation) |
|||||||||||
|
Spare Extension |
||||||||||||
|
Payload CRC |
||||||||||||
|
Payload CRC( cont) |
||||||||||||
Figure 21: USCH DATA FRAME structure
[3.84 Mcps and 7.68 Mcps TDD – Field length of Spare Extension IE in USCH DATA FRAME is 0-30 octets.
Bit 0 of New IE Flags in USCH DATA FRAME indicates if the extended bits of the Rx Timing Deviation are present (1) or not present (0) in the byte (bit 0 for 3.84 Mcps TDD, bits 0 and 1 for 7.68 Mcps TDD) following the New IE Flags IE. Bits 1 through 6 of New IE Flags in USCH DATA FRAME shall be set to 0.]
6.2.6A HS-DSCH Channels
[FDD and 1.28Mcps TDD – Three types of HS-DSCH DATA FRAME exist for the HS-DSCH data transfer, i.e. HS-DSCH DATA FRAME TYPE 1, HS-DSCH DATA FRAME TYPE 2 and HS-DSCH DATA FRAME TYPE 3.]
[3.84Mcps and 7.68Mcps TDD – Two types of HS-DSCH DATA FRAME exist for the HS-DSCH data transfer, i.e. HS-DSCH DATA FRAME TYPE 1 and HS-DSCH DATA FRAME TYPE 2.]
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|||
|
Header CRC |
FT |
Header |
||||||||
|
Frame Seq Nr |
CmCH-PI |
|||||||||
|
MAC –d PDU Length |
||||||||||
|
MAC –c/sh SDU Length (cont) |
Flush |
FSN/DRT Reset |
CPC Recov |
|||||||
|
Num Of PDUs |
||||||||||
|
User Buffer Size |
||||||||||
|
User Buffer Size (cont) |
||||||||||
|
Spare, bits 7-4 |
MAC-d PDU-1 |
Payload |
||||||||
|
MAC –d PDU 1 (cont) |
Pad |
|||||||||
|
Spare, bits 7-4 |
MAC-d PDU-n |
|||||||||
|
MAC –d PDU n (cont) |
Pad |
|||||||||
|
New IE FI 7(E) |
New IE FI 6 |
New IE FI 5 |
New IE FI 4 |
New IE FI 3 |
New IE FI 2 |
New IE FI 1 |
New IE FI 0 |
|||
|
DRT |
||||||||||
|
DRT (cont) |
||||||||||
|
SN |
||||||||||
|
SN(cont) |
S/D |
|||||||||
|
SN |
||||||||||
|
SN(cont) |
S/D |
|||||||||
|
Spare Extension |
||||||||||
|
Payload CRC |
||||||||||
|
Payload CRC (cont) |
||||||||||
Figure 21A: HS-DSCH DATA FRAME TYPE 1 structure
Bit 0 of New IE Flags in HS-DSCH DATA FRAME TYPE 1 indicates if a DRT is present (1) or not (0) in the 2 octets following the New IE Flags IE. Bit 1 of New IE Flags in HS-DSCH DATA FRAME TYPE1 indicates if SN is present (1) or not (0) in the third and the forth octets following the New IE Flags IE. Bit 0 in the forth octet is allocated for IE S/D. Bit 2 of New IE Flags in HS-DSCH DATA FRAME TYPE1 indicates if SN is present (1) or not (0) in the fifth and the sixth octets following the New IE Flags IE. Bit 0 in the sixth octet is allocated for IE S/D. Bits 3 through 6 of New IE Flags in HS-DSCH DATA FRAME TYPE 1 shall be set to 0.
Field length of Spare Extension IE in HS-DSCH DATA FRAME TYPE 1 is 0-25 octets.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
||||||||
|
Header CRC |
FT |
Header |
|||||||||||||
|
Frame Seq Nr |
CmCH-PI |
||||||||||||||
|
Total Num of PDU blocks |
Flush |
FSN/DRT Reset |
DRT Indicator |
||||||||||||
|
FI |
eDRX Indicator |
TS0 indicator |
MI |
CPC Recov |
Spare 2-0 |
||||||||||
|
User Buffer Size |
|||||||||||||||
|
User Buffer Size (cont) |
|||||||||||||||
|
MAC-d PDU length in block 1 |
|||||||||||||||
|
M len 1 (cont) |
Spare |
#PDUs in block 1 |
|||||||||||||
|
Logical CH ID block1 |
MAC-d PDU length in block 2 |
||||||||||||||
|
M len 2 (cont) |
Spare |
||||||||||||||
|
#PDUs in block2 |
Logical Ch ID in block2 |
||||||||||||||
|
MAC –d PDU length in block n |
|||||||||||||||
|
M len n (cont) |
Spare |
#PDUs in block n |
|||||||||||||
|
Logical CH ID block n |
Padding if n is odd |
||||||||||||||
|
DRT |
Payload |
||||||||||||||
|
DRT (cont) |
|||||||||||||||
|
H-RNTI |
|||||||||||||||
|
H-RNTI (cont) |
|||||||||||||||
|
RACH Measurement Result |
|||||||||||||||
|
MAC-d/c PDU 1 |
First block of PDUs with the same size |
||||||||||||||
|
MAC-d/c PDU 1 (cont) |
|||||||||||||||
|
MAC-d/c PDU m1 |
|||||||||||||||
|
MAC-d/c PDU m1 (cont) |
|||||||||||||||
|
MAC-d/c PDU 1 |
nth block of PDUs with the same size |
||||||||||||||
|
MAC-d/c PDU mn (cont) |
|||||||||||||||
|
New IE FI 7(E) |
New IE FI 6 |
New IE FI 5 |
New IE FI 4 |
New IE FI 3 |
New IE FI 2 |
New IE FI 1 |
New IE FI 0 |
||||||||
|
New IE FI 7(E) |
New IE FI 6 |
New IE FI 5 |
New IE FI 4 |
New IE FI 3 |
New IE FI 2 |
New IE FI 1 |
New IE FI 0 |
||||||||
|
Dedicated H-RNTI |
|||||||||||||||
|
Dedicated H-RNTI (cont) |
|||||||||||||||
|
E-RNTI |
|||||||||||||||
|
E-RNTI (cont) |
|||||||||||||||
|
HS-DSCH physical layer category |
EI |
spare |
|||||||||||||
|
SN |
|||||||||||||||
|
SN (cont) |
S/D |
||||||||||||||
|
SN |
|||||||||||||||
|
SN (cont) |
S/D |
||||||||||||||
|
FeDRX Indicator |
NTHT |
CR Ind |
OPCE Ind |
HS-SCCH DRX Indication |
Spare 2-0 |
||||||||||
|
CFN |
|||||||||||||||
|
Spare Extension |
|||||||||||||||
|
Payload CRC |
|||||||||||||||
|
Payload CRC (cont) |
|||||||||||||||
Figure 21B: HS-DSCH DATA FRAME TYPE 2 structure
[FDD and 1.28Mcps TDD – Bit 0 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the Dedicated H-RNTI IE and the E-RNTI IE is present (1) or not (0) in the 4 octets following the New IE Flags IE. Bit 1 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the HS-DSCH physical layer category [FDD] is present (1) or not (0) in the 5th octet following the New IE Flags IE.]
[FDD – Bit 2 of the 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the EI is present (1) or not (0).]
[FDD – Bit 3 of 1st New IE Flags in HS-DSCH DATA FRAME TYPE2 indicates if SN and S/D is present (1) or not (0).]
[FDD – Bit 4 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE2 indicates if SN and S/D is present (1) or not (0).]
[FDD – Bit 5 of 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the FeDRX Indication is present (1) or not (0).]
[FDD – Bit 6 of the 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the NodeB Triggered HS-DPCCH Transmission (NTHT) is present (1) or not (0).]
[FDD – Bit 7 of the 1st octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 is present (1) or not (0), and if present, then:]
[FDD – Bit 0 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the CFN is present (1) or not (0).]
[FDD – Bit 1 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the Cell Reselection Indication (CR Ind) IE is present (1) or not (0).]
[FDD – Bit 2 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the Operation Preference of Common E-DCH resource Indication (OPCE Ind) is present (1) or not (0).]
[FDD – Bit 3 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 indicates if the HS-SCCH DRX Indication is present (1) or not (0). Bits 4 through 6 of the 2nd octet of New IE Flags in HS-DSCH DATA FRAME TYPE 2 shall be set to 0.]
With respect to new IEs, for which the presence is indicated by the New IE Flags IE, the Figure 21B is an example of how a frame is structured when all such new IEs are present. Note that non-presence of such a new IE changes the position of all subsequent IEs on octet level.
[FDD and 1.28Mcps TDD – Field length of Spare Extension IE in HS-DSCH DATA FRAME TYPE 2 is 0-20 octets.]
[FDD – If the received H-RNTI IE sets to same value as the BCCH Specific HS-DSCH RNTI IE configured in NBAP (TS 25.433 [6]), the Node B shall ignore RACH Measurement Result IE in the frame.]
[FDD – If the received H-RNTI IE sets to same value as the BCCH Specific HS-DSCH RNTI Information IE configured in NBAP (TS 25.433 [6]), the Node B should not calculate FACH measurement occasion for scheduling the data in the frame.]
[FDD – If the received H-RNTI IE sets to same value as the Common HS-DSCH RNTI Information IE configured in NBAP (TS 25.433 [6]), the Node B should not calculate FACH measurement occasion for scheduling the data in the frame.]
[FDD – The CFN corresponding to the SFN of the frame in which the payload was received on Uplink. If the payload was received in several frames, the CFN corresponding to the last Uu frame in which the information was received shall be indicated.]
[1.28Mcps TDD – If the received H-RNTI IE sets to the same value as the BCCH Specific HS-DSCH RNTI IE configured in NBAP (TS 25.433 [6]), the Node B shall ignore RACH Measurement Result IE in the frame.]
[FDD and 1.28Mcps TDD – when a UE using E-DCH for CELL_FACH and Idle is provided with a new H-RNTI and/or a new E-RNTI signalled to the UE in the RRC message contained in this HS-DSCH data frame, the Dedicated H-RNTI IE and the E-RNTI IE contains the values to be used after successful execution of the RRC procedure (TS 25.331 [8]). The H-RNTI IE either contains the same value as the BCCH Specific HS-DSCH RNTI IE configured in NBAP (TS 25.433 [6]) or the H-RNTI currently allocated to the UE.]
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Notes in this column apply only when MUI=1 |
|||||
|
Header CRC |
FT |
all IEs are common for all UEs |
Header |
||||||||||
|
CFN |
|||||||||||||
|
CFN (cont) |
Frame Seq Nr |
||||||||||||
|
Total Num of PDU blocks |
HI |
FSN/DRT Reset |
DRT Indicator |
all IEs are dedicated for UE1 except FSN/DRT Reset and DRT Indicator |
|||||||||
|
MAC-d/c PDU length in block 1 |
|||||||||||||
|
M len 1 (cont) |
Spare |
#PDUs in block 1 |
|||||||||||
|
Logical CH ID block1 |
M len 2 |
||||||||||||
|
MAC-d PDU length in block 2 |
Spare |
||||||||||||
|
#PDUs in block2 |
Logical Ch ID in block2 |
||||||||||||
|
MAC –d PDU length in block n |
|||||||||||||
|
M len n (cont) |
Spare |
#PDUs in block n |
|||||||||||
|
Logical CH ID block n |
Padding if n is odd |
||||||||||||
|
DRT |
all IEs are common for all UEs |
Payload |
|||||||||||
|
DRT (cont) |
|||||||||||||
|
H-RNTI |
all IEs are dedicated for UE1 |
||||||||||||
|
H-RNTI (cont) |
|||||||||||||
|
CmCH-PI |
Not Used |
PI |
|||||||||||
|
PI-bitmap |
all IEs are common for all UEs |
||||||||||||
|
PI-bitmap |
Pad |
||||||||||||
|
MAC-d/c PDU 1 |
First block of PDUs with the same size |
all IEs are dedicated for UE1 |
|||||||||||
|
MAC-d/c PDU 1 (cont) |
|||||||||||||
|
MAC-d/c PDU m1 |
|||||||||||||
|
MAC-d/c PDU m1 (cont) |
|||||||||||||
|
MAC-d/c PDU 1 |
nth block of PDUs with the same size |
||||||||||||
|
MAC-d/c PDU mn (cont) |
|||||||||||||
|
New IE FI 7(E) |
New IE FI 6 |
New IE FI 5 |
New IE FI 4 |
New IE FI 3 |
New IE FI 2 |
New IE FI 1 |
New IE FI 0 |
||||||
|
HS-DSCH physical layer category |
EI |
NTHT |
|||||||||||
|
Spare 7-1 |
MUI |
||||||||||||
|
Extended for UE2 |
Extension for UE2 |
||||||||||||
|
Spare Extension |
all IEs are common for all UEs |
||||||||||||
|
Payload CRC |
|||||||||||||
|
Payload CRC (cont) |
|||||||||||||
Figure 21C: HS-DSCH DATA FRAME TYPE 3 structure [FDD and 1.28Mcps TDD only]
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Notes in this column apply only when MUI=1 |
||
|
Total Num of PDU blocks |
HI |
Spare |
all IEs are dedicated for UEn |
|||||||
|
MAC-d/c PDU length in block 1 |
||||||||||
|
M len 1 (cont) |
Spare |
#PDUs in block 1 |
||||||||
|
Logical CH ID block1 |
M len 2 |
|||||||||
|
MAC-d PDU length in block 2 |
Spare |
|||||||||
|
#PDUs in block2 |
Logical Ch ID in block2 |
|||||||||
|
MAC –d PDU length in block n |
||||||||||
|
M len n (cont) |
Spare |
#PDUs in block n |
||||||||
|
Logical CH ID block n |
Padding if n is odd |
|||||||||
|
H-RNTI |
||||||||||
|
H-RNTI (cont) |
||||||||||
|
CmCH-PI |
Spare |
|||||||||
|
MAC-d/c PDU 1 |
First block of PDUs with the same size |
|||||||||
|
MAC-d/c PDU 1 (cont) |
||||||||||
|
MAC-d/c PDU m1 |
||||||||||
|
MAC-d/c PDU m1 (cont) |
||||||||||
|
MAC-d/c PDU 1 |
nth block of PDUs with the same size |
|||||||||
|
MAC-d/c PDU mn (cont) |
||||||||||
|
New IE FI 7(E) |
New IE FI 6 |
New IE FI 5 |
New IE FI 4 |
New IE FI 3 |
New IE FI 2 |
New IE FI 1 |
New IE FI 0 |
|||
|
HS-DSCH physical layer category |
EI |
NTHT |
||||||||
|
Spare 7-1 |
MUI |
|||||||||
|
Extended for UE(n+1) |
Extension for UE(n+1) |
|||||||||
|
Spare Extension |
||||||||||
Figure 21C-1: Extended for UEn in HS-DSCH DATA FRAME TYPE 3 structure [FDD only]
[FDD – The CFN in the HS-DSCH DATA FRAME TYPE 3 header corresponds to the Cell SFN of the frame in which the start of the HS-SCCH frame is located. The timing of the PICH frame (containing the paging indication information) is the same as the HS-SCCH frame timing (TS 25.211 [5])].
[1.28Mcps TDD – In case Total Number of PDU blocks IE is not set to 0, or Total Number of PDU blocks IE is set to 0 and Paging Indication (PI) IE is set to 0, i.e. PI-bitmap not present in payload, the CFN in the HS-DSCH DATA FRAME TYPE 3 header corresponds to the Cell SFN of the frame in which the start of the HS-SCCH frame is located. The timing of the PICH frame (containing the paging indication information) is NGAP prior to the HS-SCCH or the HS-PDSCH frame timing (TS 25.221 [4])].
[1.28Mcps TDD –In case Total Number of PDU blocks IE is set to 0 and Paging Indication (PI) IE is set to 1, i.e. PI-bitmap present in payload, the CFN in the HS-DSCH DATA FRAME TYPE 3 header corresponds to the Cell SFN of the frame in which the start of the PICH frame].
[1.28Mcps TDD – If PI-bitmap and MAC-c PDU are both transmitted within the HS-DSCH DATA FRAME TYPE 3, the CFN is related to the MAC-c PDU only. The PI bitmap is mapped to the PICH frames, transmitted at the beginning of the paging block.]
[FDD and 1.28Mcps TDD – Note: The HS-SCCH frame is not sent if HI IE is set to 0, i.e. H-RNTI not present.]
[FDD – Bit 0 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if the HS-DSCH physical layer category is present (1) or not (0) in the 1st octet following the New IE Flags IE. Bit 1 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if EI [FDD] is present (1) or not (0) in the 1st octet following the New IE Flags IE. Bit 2 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if NodeB Triggered HS-DPCCH Transmission (NTHT) [FDD] is present (1) or not (0) in the 1st octet following the New IE Flags IE. Bit 3 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 indicates if Multiple UEs Indicator (MUI) is present (1) or not (0) in the 2nd octet following the New IE Flags IE. Bits 4 through 6 of New IE Flags in HS-DSCH DATA FRAME TYPE 3 shall be set to 0.]
[FDD – Note: When MUI is used, data of number of UEs carried in one HS-DSCH DATA FRAME TYPE 3 should be considered, in order to avoid too many UEs being scheduled in one CFN in NodeB.]
[FDD – Field length of Spare Extension IE in HS-DSCH DATA FRAME TYPE 3 is 0-30 octets.]
6.2.6B E-DCH Channels for CELL_FACH and Idle[FDD and 1.28Mcps TDD]
The structure of the E-DCH DATA FRAME is shown in Figure 21D. This frame structure is used for carrying MAC-is PDUs in Cell_FACH and Idle UE state (TS 25.321 [9]) for one UE.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|||||||
|
Header CRC |
FT |
Frame Header |
||||||||||||
|
Header CRC (cont) |
FSN |
|||||||||||||
|
Spare |
Number of subframes |
|||||||||||||
|
CFN |
||||||||||||||
|
E-DCH User Buffer Size (eUB Size) |
||||||||||||||
|
E-DCH User Buffer Size (eUB Size) |
||||||||||||||
|
eUB Size |
Spare |
Nr. of MAC-is SDU in frame |
||||||||||||
|
Nr of MAC-is SDU in frame(cont) |
||||||||||||||
|
E-RNTI |
||||||||||||||
|
E-RNTI |
||||||||||||||
|
Spare |
1st Subframe number |
N of MAC-is PDUs |
||||||||||||
|
Spare |
2nd Subframe number |
N of MAC-is PDUs |
||||||||||||
|
Spare |
Last Subframe number |
N of MAC-is PDUs |
||||||||||||
|
MAC-is PDU descriptor of 1st MAC-is PDU of 1st subframe |
||||||||||||||
|
MAC-is PDU descriptor of 2nd MAC-is PDU of 1st subframe |
||||||||||||||
|
MAC-is PDU descriptor of last MAC-is PDU of 1st subframe |
||||||||||||||
|
MAC-is PDU descriptor of 1st MAC-is PDU of last subframe |
||||||||||||||
|
MAC-is PDU descriptor of last MAC-is PDU of last subframe |
||||||||||||||
|
First MAC-is PDU of first subframe |
Frame Payload |
|||||||||||||
|
Last MAC-is PDU of first subframe |
||||||||||||||
|
First MAC-is PDU of last subframe |
||||||||||||||
|
Last MAC-is PDU of last subframe |
||||||||||||||
|
New IE FI 7(E) |
New IE FI 6 |
New IE FI 5 |
New IE FI 4 |
New IE FI 3 |
New IE FI 2 |
New IE FI 1 |
New IE FI 0 |
|||||||
|
Cell Portion LCR ID |
Conditional 1.28Mcps TDD |
|||||||||||||
|
Spare 7-2 |
AOA |
Conditional 1.28Mcps TDD |
||||||||||||
|
AOA |
Conditional 1.28Mcps TDD |
|||||||||||||
|
Spare 7-5 |
Ext Received SYNC UL Timing Deviation |
Conditional 1.28Mcps TDD |
||||||||||||
|
Ext received SYNC UL Timing Deviation |
Conditional 1.28Mcps TDD |
|||||||||||||
|
Spare 7-4 |
CRR Rec |
TTI length |
Prop. Delay FR |
FDD |
||||||||||
|
Propagation Delay Full Range |
FDD |
|||||||||||||
|
Spare Extension |
Optional |
|||||||||||||
|
Payload CRC |
||||||||||||||
|
Payload CRC (cont) |
||||||||||||||
Figure 21D: E-DCH DATA FRAME structure
For the description of the fields see subclause 6.2.7.
The Payload CRC IE is optional in frames that contain a Payload, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). The Payload CRC IE may only be present if the E-DCH DATA FRAME contains payload.
[1.28Mcps TDD – Bit 0 of New IE Flags in E-DCH DATA FRAME indicates if the Cell Portion LCR ID IE is present (1) or not present (0).]
[1.28Mcps TDD – Bit 1 of New IE Flags in E-DCH DATA FRAME indicates if AOA IE is present (1) or not present (0)]
[1.28Mcps TDD – Bit 2 of New IE Flags in E-DCH DATA FRAME indicates if Ext Received SYNC UL Timing Deviation IE is present (1) or not present (0)]
[1.28Mcps TDD – Bits 2 through 6 of New IE Flags in E-DCH DATA FRAME shall be set to 0.]
[FDD – Bit 0 of New IE Flags IE in E-DCH DATA FRAME indicates if Propagation Delay Full Range IE is present (1) or not present (0)]
[FDD – Bit 1 of New IE Flags IE in E-DCH DATA FRAME indicates if TTI length IE is present (1) or not present (0).]
[FDD – Bit 2 of New IE Flags IE in E-DCH DATA FRAME indicates if Cell Reselection Request Received (CRR Rec) IE is present (1) or not present (0).]
[FDD – Bits 3 through 6 of New IE Flags IE in E-DCH DATA FRAME shall be set to 0.]
[FDD – Field length of Spare Extension IE in E-DCH DATA FRAME is 0-29 octets.]
6.2.7 Coding of information elements in data frames
6.2.7.1 Header CRC
Description: Cyclic Redundancy Checksum calculated on the header of a data frame with polynom:
X^7+X^6+X^2+1 for the 7 bit header CRC [FDD and 1.28Mcps TDD – ,X^11+X^9+X^8+ X^2+X+1 for the 11 bit header CRC].
The CRC calculation shall cover all bits in the header, starting from bit 0 in the first byte (FT field) up to the end of the header. See subclause 7.1.
Value range: {0..127} [FDD and 1.28Mcps TDD – , {0..2047} for E-DCH DATA FRAME].
Field length: 7 bits [FDD and 1.28Mcps TDD – , 11 bits for E-DCH DATA FRAME].
6.2.7.2 Frame Type
Description: Describes if it is a control frame or a data frame.
Value range: {0=data, 1=control}.
Field Length: 1 bit.
6.2.7.3 Connection Frame Number (CFN)
Description: Indicator as to which radio frame the first data was received on uplink or shall be transmitted on downlink. In case a transport bearer is used by several FACH channels with IP multicast option, the radio frame in which the first data shall be transmitted on a FACH mapping on the transport bearer shall be calculated according to:
CFN = (MFN – CFN Offset) mod 256,
where:
– MFN is the value of CFN field in the data frame;
– CFN Offset is a FACH parameter indicated by RNC (TS 25.433 [6]).
The value range and field length depend on the transport channel for which the CFN is used.
Value range (PCH): {0..4095}.
Value range (other): {0..255}.
Field length (PCH): 12 bits.
Field length (other): 8 bits.
6.2.7.4 Transport Format Indicator
Description: TFI is the local number of the transport format used for the transmission time interval. For information about what the transport format includes see TS 25.302 [3].
Value range: {0..31}.
Field length: 5 bits.
6.2.7.5 Propagation Delay [FDD]
Description: One-way radio interface delay as measured during RACH access. If the measured value exceeds the range of this information element, the information element shall be set to its maximum value, and the Ext Propagation Delay IE shall be used to represent the measured value, see subclause 6.2.7.5A.
Value range: {0..765 chips}.
Granularity: 3 chips.
Field length: 8 bits.
6.2.7.5A Ext Propagation Delay [FDD]
Description: One-way radio interface delay as measured during RACH access, extended value part. This IE shall be present only if the range of the Propagation Delay IE is insufficient to represent the measured value.
Value range: {0 – 3069 chips}, values 0 -765 are not used.
Granularity: 3 chips.
Field length: 10 bits.
6.2.7.6 Rx Timing Deviation [3.84Mcps TDD]
Description: Measured Rx Timing Deviation as a basis for timing advance. This value should consider measurements made in all frames and all timeslots that contain the transport blocks in the payload. In case the Timing Advance Applied IE indicates "No" (see TS 25.433 [6]) in a cell, the Rx Timing Deviation field shall be set to N = 0.
Value range: {-1024 .. +1023 chips}.
{N*4 –256} chips RxTiming Deviation < {(N+1)*4 – 256} chips.
With N = 0, 1, .., 127.
{(N-128)*4 – 1024} chips Rx Timing Deviation < {(N-127)*4 – 1024} chips
With N = 128, 129, …,319
{N*4 – 1024} chips Rx Timing Deviation < {(N+1)*4 – 1024} chips
With N = 320, 321, …,511
Granularity: 4 chips.
Field length: 9 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant bit is contained in the RX timing deviation (continuation) field.
6.2.7.6A Received SYNC UL Timing Deviation [1.28Mcps TDD]
Description: Measured Received SYNC UL Timing Deviation as a basis for propagation delay.
Value range: {0, .., +255} chips
Granularity: 1 chip.
Field length: 8 bits.
6.2.7.6B Rx Timing Deviation [7.68Mcps TDD]
Description: Measured Rx Timing Deviation as a basis for timing advance. This value should consider measurements made in all frames and all timeslots that contain the transport blocks in the payload. In case the Timing Advance Applied IE indicates "No" (see TS 25.433 [6]) in a cell, the Rx Timing Deviation field shall be set to N = 0.
Value range: {-2056, …, +2055} chips
{N*4 -2056} chips RxTiming Deviation < {(N+1)*4 -2056} chips
With N = 0, 1, …, 1027
Granularity: 4 chips.
Field length: 10 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant 2 bits are contained in the RX timing deviation (continuation) field.
6.2.7.7 Transport Block
Description: A block of data to be transmitted or have been received over the radio interface. The transport format indicated by the TFI describes the transport block length and transport block set size. See TS 25.302 [3].
6.2.7.8 CRC Indicator
Description: Shows if the transport block has a correct CRC. The UL Outer Loop Power Control may use the CRC indication.
Value range: {0=Correct, 1=Not Correct}.
Field length: 1 bit.
6.2.7.9 Payload CRC
Description: Cyclic Redundancy Checksum calculated on the payload of a data frame with polynom
X^16+X^15+X^2+1.
The CRC calculation shall cover all bits in the data frame payload, starting from bit 7 in the first byte up to bit 0 in the byte before the payload CRC. See subclause 7.1.
In HS-DSCH DATA FRAME TYPE3, if MUI is set, the CRC calculation shall cover all bits in the data frame payload, starting from bit 7 in the first byte up to bit 0 in the byte before the payload CRC, and all the bits in the Extended for UEn in HS-DSCH DATA FRAME TYPE 3 structure. See subclause 7.1.
Field length: 16 bits.
6.2.7.10 Transmit Power Level
Description: Preferred transmission power level during this TTI for the corresponding transport channel. The indicated value is the negative offset relative to the maximum power configured for the physical channel(s) used for the respective transport channel. [1.28Mcps TDD – The Node B shall ignore the Transmit Power Level in the TDD DSCH DATA FRAME.] [3.84Mcps and 7.68Mcps TDD – The Node B shall ignore the Transmit Power Level in the TDD DSCH DATA FRAME if closed loop TPC power control is used.]
Value range: {0 .. 25.5 dB}.
Granularity: 0,1 dB.
Field length: 8 bits.
6.2.7.11 Paging Indication (PI)
Description: Describes if the PI Bitmap is present in the payload.
Value range: {0=no PI-bitmap in payload, 1=PI-bitmap in payload}.
Field length: 1 bit.
6.2.7.12 Paging Indication bitmap (PI-bitmap)
Description: Bitmap of Paging Indications PI0..PIN-1. Bit 7 of the first byte contains PI0, Bit6 of the first byte contains PI1,,…, Bit7 of the second byte contains PI8 and so on.
Value range: [FDD – {18, 36, 72 or 144 Paging Indications}.]
[3.84Mcps TDD – {30, 34, 60, 68, 120 and 136} Paging Indications for 2 PICH frames,
{60, 68, 120, 136, 240 and 272} Paging Indications for 4 PICH frames].
[1.28Mcps TDD – {44, 88 and 176} Paging Indications for 2 PICH frames,
{88, 176 and 352} Paging Indications for 4 PICH frames].
[7.68Mcps TDD – {30, 34, 60, 68, 120 and 136} Paging Indications for 2 PICH frames,
{60, 68, 120, 136, 240 and 272} Paging Indications for 4 PICH frames,
…………. {120, 136, 240, 272, 480 and 544} Paging Indications for 8 PICH frames].
Field length: [FDD – 3, 5, 9 or 18 bytes (the PI-bitmap field is padded at the end up to an octet boundary)].
[3.84Mcps TDD – 4, 5, 8, 9, 15, 17, 30 or 34 bytes (the PI-bitmap field is padded at the endup to an octet boundary)].
[1.28Mcps TDD – 6, 11, 22 or 44 bytes (the PI-bitmap field is padded at the endup to an octet boundary)].
[7.68Mcps TDD – 4, 5, 8, 9, 15, 17, 30, 34, 60 or 68 bytes (the PI-bitmap field is padded at the end up to an octet boundary)].
6.2.7.13 Rx Timing Deviation on RACH [3.84Mcps TDD]
Void.
6.2.7.14 PDSCH Set Id [TDD]
Description: A pointer to the PDSCH Set which shall be used to transmit the DSCH DATA FRAME over the radio interface.
Value range: {0..255}.
Field length: 8 bits.
6.2.7.15 Code Number [FDD]
Void.
6.2.7.16 Spreading Factor (SF) [FDD]
Void.
6.2.7.17 Power Offset [FDD]
Void.
6.2.7.18 MC Info [FDD]
Void.
6.2.7.19 Spare Extension
Description: Indicates the location where new IEs can in the future be added in a backward compatible way.
Field length: 0-32 octets.
6.2.7.20 Quality Estimate (QE) [TDD]
Description: The quality estimate is derived from the Transport channel BER.
If the USCH FP frame includes TB’s for the USCH then the QE is the Transport channel BER for the selected USCH. If no Transport channel BER is available the QE shall be set to 0.
The quality estimate shall be set to the Transport channel BER and be measured in the units TrCH_BER_LOG respectively (see TS 25.433 [6]). The UL Outer Loop Power Control may use the quality estimate.
Value range: {0..255}.
Granularity: 1.
Field length: 8 bits.
6.2.7.21 Common Transport Channel Priority Indicator (CmCH-PI)
Description: CmCH-PI, configured via the Scheduling Priority Indicator in NBAP (TS 25.433 [6]), is the relative priority of the data frame and the SDUs included.
Value range: {0-15, where 0=lowest priority, 15=highest priority}.
Field length: 4 bits.
6.2.7.22 User Buffer Size
Description: Indicates the users’ buffer size (i.e. the amount of data in the buffer) in octets for a given Common Transport Channel Priority Indicator level.
Value range: {0-65535}.
Field length: 16 bits.
6.2.7.23 MAC-d PDU Length
Description: The value of that field indicates the length of every MAC-d PDU in the payload of the HS-DSCH DATA FRAME in number of bits.
Value range: {0-5000}.
Field Length: 13 bits.
6.2.7.24 NumOfPDU
Description: Indicates the number of MAC-d PDUs in the payload.
Value range: {1-255}.
Field Length: 8 bits.
6.2.7.25 MAC-d PDU
Description: A MAC-d PDU contains the MAC-d PDU as defined in TS 25.321 [9].
Field length: See the value of the MAC-d PDU Length IE.
6.2.7.26 Cell Portion ID [FDD]
Description: Cell Portion ID indicates the cell portion with highest SIR during RACH access. Cell Portion ID is configured by O&M.
Value range: {0-63}.
Field Length: 6 bits.
6.2.7.27 New IE Flags
Description: The New IE Flags IE is only present if at least one new IE is present. The New IE Flags IE contains flags indicating which new IEs that are present following the New IE Flags IE. The last bit position of the New IE Flags IE is used as the Extension Flag to allow the extension of the New IE Flags IE in the future. Extension octets of the New IE Flags IE shall follow directly after the first octet of the New IE Flags IE. When an extension octet of the New IE Flags IE is present, then all previous extension octets of the New IE Flags IE and the New IE Flags IE shall also be present, even if they have all their flag bits indicating no presence of their respective new IEs.
Value range:
Bit 0-6 of each octet: Indicates if a new IE is present (1) or not present (0) in the bytes following the New IE Flags IE. The meaning of each bit is explained in the corresponding DATA FRAME subclause;
Bit 7 of each octet: Indicates if an extension octet of the New IE Flags IE follows (1) or not (0).
Field length: 1 – 31 octets.
6.2.7.28 Flush
Description: Indicates whether the DRNS should remove (1) or not (0) all the MAC-d PDUs from the corresponding MAC-hs Priority Queue that have been received prior to this data frame HS-DSCH DATA FRAME on the same transport bearer.
Value range: {0 = no flush, 1 = flush}.
Field Length: 1 bit.
6.2.7.29 DRT (Delay Reference Time)
Description: DRT is a 16-bit Delay Reference Time. DRT can be used for dynamic delay measurements. The DRT counter bridges the same time span as RFN and BFN. DRT is locked to RFN in SRNC and is a 40960 counter with 1 ms resolution.
Value range: {0..40959DEC ms (0..9FFFHEX ms)}.
Granularity: 1 ms.
Field length: 16 bits.
6.2.7.30 Frame Sequence Number
Description: The 4-bit Frame Sequence Number (FSN) is incremented for each transmitted HS‑DSCH data frame belonging to one MAC-d flow [FDD and 1.28Mcps TDD – , common MAC flow or E-DCH DATA FRAME belonging to one E-DCH data flow for CELL_FACH and Idle]. At wraparound of the Frame Sequence Number, the value "0" shall not be used. Each flow generates its own Frame Sequence.
Value range:
0 is a special value and indicates that the Frame Sequence Number IE shall be treated as spare.
1 – 15 indicates the Frame Sequence Number.
Granularity: 1.
Field length: 4 bits.
6.2.7.31 Logical Channel ID in block n
Description: This field provides identification of the logical channel instance associated with the PDUs of the n-th block of PDUs with the same size in the HS-DSCH DATA FRAME TYPE 2 [FDD and 1.28Mcps TDD – and TYPE 3]. Multiple logical channels may be carried on the same MAC-d flow [FDD and 1.28Mcps TDD – , Common MAC flow or Paging MAC flow].
Value range: {0-15}, where 0-14 identifies logical channels 1-15, 15 identifies BCCH or PCCH logical channel mapped on HS-DSCH.
Field length: 4 bits.
6.2.7.32 Total Number of PDU blocks
Description: The field indicates the number of blocks of block of PDUs with the same size in this HS-DSCH DATA FRAME. In HS-DSCH DATA FRAME TYPE3, the field indicates the number of blocks of block of PDUs with the same size per UE, if MUI is set.
Value range: {0-31}, 0 only for 1.28Mcps TDD HS-DSCH DATA FRAME TYPE 3.
Field length: 5 bits.
6.2.7.33 MAC-d/c PDU Length in block n
Description: The value of this field indicates the length of every MAC-d PDU [FDD and 1.28Mcps TDD – or MAC-c PDU] in the n-th block of PDUs with the same size in number of octets.
Value range: {0-1505}, 0 – not used.
Field length: 11 bits.
6.2.7.34 Number of MAC-d/c PDUs in block n (#PDUs in block n)
Description: Indicates the number of MAC-d PDUs [FDD and 1.28Mcps TDD – or MAC-c PDUs] in the n-th block of PDUs with the same size.
Value range: {0-15}, 0 – not used.
Field length: 4 bits.
6.2.7.35 DRT Indicator
Description: Indicates whether a DRT is present.
Value range: {0 = DRT not present, 1= DRT present}.
Field length: 1 bit.
6.2.7.36 FACH Indicator (FI) [FDD and 1.28Mcps TDD]
Description: Indicates whether an H-RNTI and a RACH Measurement Result are present (i.e. whether UE in CELL_FACH).
Value range: {0 = H-RNTI and RACH Measurement Result not present, 1= H-RNTI and RACH Measurement Result present}.
Field length: 1 bit.
6.2.7.37 H-RNTI [FDD and 1.28Mcps TDD]
Description: H-RNTI is defined in TS 25.401 [11]. The field identifies an UE having a HS-PDSCH assignment within a cell [FDD and 1.28Mcps TDD – or has the same value as the BCCH Specific HS-DSCH RNTI IE configured in TS 25.433 [6]].
Value range: {0-65535}, 0 – not used.
Field length: 16 bits.
6.2.7.38 RACH Measurement Result [FDD and 1.28Mcps TDD]
Description: [FDD – This field indicates the values received in RACH Measurement. The type of the measured value in the field is configured via NBAP (TS 25.433 [6])]. [1.28Mcps TDD – This field indicats the pathloss value (in dB) calculated based on the Primary CCPCH RSCP IE in the measurement result on RACH according to the formula in TS 25.331 [8].]
Value range: [FDD – {0-158, 255}
255 is a special value for FDD and indicates that the Node B may ignore the RACH Measurement Results IE.]
[1.28Mcps TDD – {0-112}
Note: The value “0” of the IE corresponds to the pathloss value of “46”, the value “1” corresponds to the pathloss value of “47”,…, the value “112” corresponds to the pathloss value of “158”.]
Field length: [FDD – 8 bits].
[1.28Mcps TDD – 7 bits (Bit 7 of the RACH Measurement Result field is not used)].
6.2.7.39 H-RNTI Indicator (HI) [FDD and 1.28Mcps TDD]
Description: Indicates whether an H-RNTI and a CmCH-PI are present.
Value range: {0 = H-RNTI and CmCH-PI not present, 1= H-RNTI and CmCH-PI present}.
Field length: 1 bit.
6.2.7.40 FSN/DRT Reset
Description: When the Node B receives a HS-DSCH DATA FRAME where the 1-bit FSN/DRT Reset IE is set to 1, the Node B should reset any state of congestion estimation based on previously received FSN and DRT values. Node B may instead decide to start a new estimation of congestion detection initiated with the FSN and DRT values included in this HS-DSCH data frame. FSN/DRT Reset IE set to 1 may indicate a discontinuity in the sequence of the transmitted DRT and FSN values in the transmitted HS‑DSCH data frames belonging to the associated MAC-d flow.
If the 1-bit FSN/DRT Reset IE is set to 0, Node B may use the included DRT and FSN values for congestion detection.
Value range:
0 Node B may use the included DRT and FSN values for congestion detection.
1 Node B should not use previously received FSN and DRT values for congestion detection.
Field length: 1 bit.
6.2.7.41 MAC-d/c PDU
Description: A MAC-d/c PDU contains the MAC-ehs SDU as defined in TS 25.321 [9].
Field length: For length of MAC-d/c PDU of block n, see the value of the MAC-d/c PDU length in block n IE.
6.2.7.42 AOA (Angle of Arrival) [1.28Mcps TDD]
Description: This filed indicates the angle of arrival information of UE measured by Node B.
Value range: {0-719}
Field length: 10 bit.
6.2.7.43 Ext Received SYNC UL Timing Deviation [1.28Mcps TDD]
Description: Measured Received SYNC UL Timing Deviation as a basis for propagation delay.
Value range: {0, .., +1023} chips
Granularity: 1/8 chip.
Field length: 13 bits.
6.2.7.44 Number of Subframes [FDD and 1.28Mcps TDD]
Description: The Number of Subframes field indicates how many subframes that follows in the frame. [1.28Mcps TDD – This will always be set to "1".]
NOTE: A subframe has both a header portion and a payload portion in the frame.
Value range: {1-16}
The binary coding is derived from the value minus 1. E.g. value 1 is coded as binary "0000" and value 16 is coded as binary "1111".
Values {11, 12, 13, 14, 15, 16}: Reserved in this user plane revision. Shall be ignored by the receiver.
Field length: 4 bits.
6.2.7.45 Number of MAC-is SDU in frame [FDD and 1.28Mcps TDD]
Description: Total number of MAC-is SDUs in all MAC-is PDUs in the E-DCH DATA FRAME.
Value range: {0-4095}.
Field length: 12 bits.
6.2.7.46 Number of MAC-is PDUs [FDD and 1.28Mcps TDD]
Description: Indicates the number of MAC-is PDUs in the user data frame in the payload part for the corresponding subframe number.
Value range: {0-15}
Field length: 4 bits.
6.2.7.47 Subframe Number [FDD and 1.28Mcps TDD]
Description: Indicates the subframe number in which the payload was received. [1.28 Mcps TDD – This will be set to {0-1}.]
Value range: {0-4}
Field length: 3 bits.
6.2.7.48 E-DCH User Buffer Size [FDD and 1.28Mcps TDD]
Description: Indicates the the total size of the E-DCH DATA FRAME in octets
Value range: {0-262 140}
Field length: 18 bits.
6.2.7.49 E-RNTI [FDD and 1.28Mcps TDD]
Description: E-RNTI is defined in TS 25.401 [11].
In the E-DCH DATA FRAME: the field identifies a UE having an E-DCH assignment within a cell or the allocated E-RNTI to a UE requesting E-DCH resources for CELL_FACH and Idle in a cell.
In HS-DSCH DATA FRAME TYPE 2: E-RNTI identifies the UE using E-DCH in Cell_FACH and Idle state.
Value range: {0-65535}, 0 – not used.
Field length: 16 bits.
6.2.7.50 MAC-is PDU descriptor [FDD and 1.28Mcps TDD]
Description: The MAC-is PDU descriptor contains the Length (L), Logical channel identifier (LCH-ID) and Flag (F) fields mapped directly from the "MAC-i Header n" field (n>0) received over the Uu (TS 25.321 [9]).
Field length: variable; length of MAC-is PDU descriptor in octets = 2 * number of MAC-is SDU contained in the corresponding MAC-is PDU as described in TS 25.321 [9].
6.2.7.51 Dedicated H-RNTI [FDD and 1.28Mcps TDD]
Description: Dedicated H-RNTI identifies the H-RNTI for a UE using E-DCH in Cell_FACH and Idle state. H-RNTI is defined in TS 25.401 [11].
Value range: {0-65535}, 0 – not used.
Field length: 16 bits
6.2.7.52 eDRX Indication [FDD]
Description: Indicates whether the UE in Cell_FACH state supports Enhanced UE DRX or not.
Value range: {0 = Enhanced UE DRX not supported, 1= Enhanced UE DRX supported}.
Field length: 1 bit.
6.2.7.53 HS-DSCH physical layer category [FDD]
Description: HS-DSCH physical layer category is defined in TS 25.306 [12]. The value of the field identifies the HS-DSCH physical layer category number of the UE, which is not applicable to the case that the H-RNTI IE sets to the same value as the BCCH Specific HS-DSCH RNTI IE.
Value range: {1 – 63}, where the valid values are defined in TS 25.306 [12].
Field length: 6 bit.
6.2.7.54 Cell Portion LCR ID [1.28Mcps TDD]
Description: Cell Portion LCR ID indicates the cell portion with best received quality during RACH access. Cell Portion LCR ID is configured by O&M.
Value range: {0-255}.
Field Length: 8 bits.
6.2.7.55 TS0 Indication [1.28Mcps TDD]
Description: Indicates whether the UE supports TS0 enhancement or not.
Value range: {0 = Enhanced TS0 not supported, 1= Enhanced TS0 supported}.
Field length: 1 bit.
6.2.7.56 Enhanced HS-SCCH support indicator (EI) [FDD]
Description: Indicates whether the UE in Cell_FACH state supports enhanced different HS-SCCHs in consecutive TTIs support or not.
Value range: {0 = Enhanced different HS-SCCHs in consecutive TTIs not supported, 1= Enhanced different HS-SCCHs in consecutive TTIs supported}.
Field length: 1 bit.
6.2.7.57 MU-MIMO Indication(MI) [1.28Mcps TDD]
Description: Indicates whether the UE in Cell_FACH state supports MU-MIMO or not.
Value range: {0 = MU-MIMO not supported, 1= MU-MIMO supported}.
Field length: 1 bit.
6.2.7.58 Propagation Delay Full Range [FDD]
Description: One-way radio interface delay as measured during random access on Common E-DCH.
Value range: {0..3069 chips}.
Granularity: 3 chips.
Field length: 10 bits.
6.2.7.59 CPC Recovery (CPC Recov) [FDD]
Description: Describes if UE is CPC non-uniform related to HS-SCCH order and CPC recovery is needed in the serving Node-B. It indicates that the dynamic DTX/DRX (de)activation using HS-SCCH order is needed.
Value range: {0=no Recovery, 1=Recovery}.
Field Length: 1 bit.
Note: This is not applicable when HS-SCCH order is not used.
6.2.7.60 FeDRX Indication [FDD]
Description: Indicates whether the UE in Cell_FACH state supports Further Enhanced UE DRX or not.
Value range: {0 = Further Enhanced UE DRX not supported, 1= Further Enhanced UE DRX supported}.
Field length: 1 bit.
6.2.7.61 NodeB Triggered HS-DPCCH Transmission(NTHT) [FDD]
Description: Indicates whether the UE in Cell_FACH and CELL_PCH state supports NodeB Triggered HS-DPCCH Transmission or not.
Value range: {0 = NodeB Triggered HS-DPCCH Transmission not supported, 1= NodeB Triggered HS-DPCCH Transmission supported}.
Field length: 1 bit.
6.2.7.62 TTI length [FDD]
Description: Indicates which type of TTI length UE in Cell_FACH and Idle state is in use for 2ms/10ms concurrent deployment.
Value range: {0 = 2ms, 1= 10ms}.
Field length: 1 bit.
6.2.7.63 SN, Frame Number
Description: SN is a sequence number assigned to each HS-DSCH data frame by RNC and can be used by Node B to identify the set of MAC-d PDU’s sent in the frame. This is also used by RNC to indicate the HS-DSCH data frame that the Node B can discard.
Value range: {0.. 32767}.
Field length: 15 bits.
6.2.7.64 S/D, Store/Discard indicator
Description: The S/D indicator indicates if Node B can store or discard data associated with SN (See section 6.2.7.63).
Value range: {0 = Discard data associated with SN, 1 = Store and associate MAC-d PDUs in frame with SN}.
Field length: 1 bit.
6.2.7.65 CR Ind (Cell Reselection Indication)
Description: Indicates that the Node B may release the common E-DCH resource due to a cell reselection indication.
Value range: {0 = Release common E-DCH resource not permitted due to a cell reselection indication, 1 = Release common E-DCH resource permitted due to a cell reselection indication.}
Field length: 1 bit.
6.2.7.66 CRR Rec (Cell Reselection Request Received)
Description: Indicates that the Node B has received Cell Reselection Request from UE or not.
Value range: {0 = Cell Reselection Request from UE not received, 1 = Cell Reselection Request from UE received}.
Field length: 1 bit.
6.2.7.67 Multiple UEs Indicator (MUI) [FDD]
Description: The MUI indicates there is another UE’s MAC-d/c PDUs (Extended for UEn) followed in below octets. MUI=0, indicates no other UE’s MAC-d/c PDUs is followed. MUI=1 in Extended for UE(n-1) indicates nth UE’s MAC-d/c PDUs (Extended for UEn) is followed.
Value range: {0 = No other UE’s MAC-d/c PDUs followed, 1 = there is another UE’s MAC-d/c PDUs followed}.
Field length: 1 bit.
6.2.7.68 Extended for UEn [FDD]
Description: The Extended for UEn is used to carry another UE’s data in same HS-DSCH DATA FRAME TYPE3 in case of MUI =1 is indicated in previous UE’s New IE flags. All IEs included in Extended for UEn are defined in subclause 6.2.6A Figure21C-1.
6.2.7.69 Operation Preference of Common E-DCH resource Indication (OPCE Ind) [FDD]
Description: The OPCE Ind indicates there is a preference for the Node B to trigger acquisition of the common E-DCH resource or to release the allocated common E-DCH resource for the particular UE. In case of NTHT is not set or set to zero, the OPCE Ind bit is not used.
Value range: {0 = Preference to release the allocated common E-DCH resource, 1 = Preference to trigger acquisition of the common E-DCH resource}.
Field length: 1 bit.
6.2.7.70 HS-SCCH DRX Indication [FDD]
Description: Indicates whether the UE in Cell_FACH state supports HS-SCCH DRX or not.
Value range: {0 = HS-SCCH DRX not supported, 1= HS-SCCH DRX DRX supported}.
Field length: 1 bit.
6.3 Control frame structure
6.3.1 Introduction
The Common Control Channel control frames are used to transport control information between the CRNC and the Node B. Figure 22 defines the Control Frame structure for common transport channels.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
||
|
Frame CRC |
FT |
Header (2 bytes) |
|||||||
|
Control Frame Type |
|||||||||
|
Control Information |
Payload (variable length) |
||||||||
|
Control Information (cont) |
|||||||||
Figure 22: Iub Common Transport Channel Control Frame Format
The structure of the header and the payload of the control frames is defined in the following subclauses.
6.3.2 Coding of information elements of the Control frame header
6.3.2.1 Frame CRC
Description: Cyclic Redundancy Checksum calculated on a control frame with polynom:
X^7+X^6+X^2+1.
The CRC calculation shall cover all bits in the control frame, starting from bit 0 in the first byte (FT field) up to the end of the control frame. See subclause 7.1.
Value range: {0..127}.
Field length: 7 bits.
6.3.2.2 Frame Type (FT)
Refer to subclause 6.2.7.2.
6.3.2.3 Control Frame Type
Description: Indicates the type of the control information (information elements and length) contained in the payload.
Value: Values of the Control Frame Type parameter are defined in table 2.
Table 2
|
Type of control frame |
Value |
|
OUTER LOOP POWER CONTROL |
0000 0001 |
|
TIMING ADJUSTMENT |
0000 0010 |
|
DL SYNCHRONISATION |
0000 0011 |
|
UL SYNCHRONISATION |
0000 0100 |
|
Reserved Value |
0000 0101 |
|
DL NODE SYNCHRONISATION |
0000 0110 |
|
UL NODE SYNCHRONISATION |
0000 0111 |
|
DYNAMIC PUSCH ASSIGNMENT |
0000 1000 |
|
TIMING ADVANCE |
0000 1001 |
|
HS-DSCH Capacity Request |
0000 1010 |
|
HS-DSCH Capacity Allocation TYPE 1 |
0000 1011 |
|
HS-DSCH Capacity Allocation TYPE 2 |
0000 1100 |
|
HS-DSCH UL Synchronization Establishment Failure (1.28Mcps TDD only) |
0000 1101 |
|
HS-DSCH PDU Drop Indication |
0000 1110 |
Field Length: 8 bits.
The "Reserved Value" for the Control Frame Type IE shall not be used by the SRNC. A control frame whose Control Frame Type IE is set to the "Reserved Value" shall be ignored by the Node B.
6.3.3 Payload structure and information elements
6.3.3.1 TIMING ADJUSTMENT
6.3.3.1.1 Payload Structure
Figures 23 and 24 shows the structure of the payload when control frame is used for the timing adjustment.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
|
|
CFN |
1 |
Payload |
|||||||
|
ToA |
1 |
||||||||
|
ToA (cont) |
1 |
||||||||
|
Spare Extension |
0-32 |
||||||||
Figure 23: TIMING ADJUSTMENT payload structure (non-PCH transport bearers)
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
||
|
CFN |
1 |
Payload |
||||||||
|
CFN(cont) |
Not Used |
1 |
||||||||
|
ToA |
1 |
|||||||||
|
ToA (cont) |
1 |
|||||||||
|
ToA(cont) |
Not Used |
1 |
||||||||
|
Spare Extension |
0-32 |
|||||||||
Figure 24: TIMING ADJUSTMENT payload structure (PCH transport bearer)
6.3.3.1.2 CFN
Refer to subclause 6.2.7.3.
6.3.3.1.3 Time of arrival (ToA)
Description: Time difference between the arrival of the DL frame with respect to TOAWE (based on the CFN in the frame). The value range and field length depend on the transport channel for which the CFN is used.
Value range (PCH): {-20480ms, +20479.875ms}.
Value range (other): {-1280ms, +1279.875ms}.
Granularity: 125s.
Field length (PCH): 20 bits.
Field length (other): 16 bits.
6.3.3.1.4 Spare Extension
Description: Indicates the location where new IEs can in the future be added in a backward compatible way.
Field length: 0-32 octets.
6.3.3.2 DL SYNCHRONISATION
6.3.3.2.1 Payload Structure
Figures 25 and 26 shows the structure of the payload when control frame is used for the user plane synchronisation.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
|
|
CFN |
1 |
Payload |
|||||||
|
Spare Extension |
0-32 |
||||||||
Figure 25: DL SYNCHRONISATION payload structure (non-PCH transport bearers)
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
||
|
CFN |
1 |
Payload |
||||||||
|
CFN(cont) |
Not Used |
1 |
||||||||
|
Spare Extension |
0-32 |
|||||||||
Figure 26: DL SYNCHRONISATION payload structure (PCH transport bearers)
6.3.3.2.2 CFN
Refer to subclause 6.2.7.3.
6.3.3.2.3 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.3 UL SYNCHRONISATION
6.3.3.3.1 Payload Structure
Figures 27 and 28 shows the structure of the payload when the control frame is used for the user plane synchronisation (UL).
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
|
|
CFN |
1 |
Payload |
|||||||
|
ToA |
1 |
||||||||
|
ToA (cont) |
1 |
||||||||
|
Spare Extension |
0-32 |
||||||||
Figure 27: UL SYNCHRONISATION payload structure (non-PCH transport bearers)
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
||
|
CFN |
1 |
Payload |
||||||||
|
CFN(cont) |
Not Used |
1 |
||||||||
|
ToA |
1 |
|||||||||
|
ToA (cont) |
1 |
|||||||||
|
ToA(cont) |
Not Used |
1 |
||||||||
|
Spare Extension |
0-32 |
|||||||||
Figure 28: UL SYNCHRONISATION payload structure (PCH transport bearers)
6.3.3.3.2 CFN
Refer to subclause 6.2.7.3.
6.3.3.3.3 Time of Arrival (TOA)
Refer to subclause 6.3.3.1.3.
6.3.3.3.4 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.4 DL NODE SYNCHRONISATION
6.3.3.4.1 Payload Structure
The payload of the DL Node synchronisation control frames is shown in figure 29.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
|
|
T1 |
1 |
Payload |
|||||||
|
T1 (cont) |
1 |
||||||||
|
T1 (cont) |
1 |
||||||||
|
Spare Extension |
0-32 |
||||||||
Figure 29: DL NODE SYNCHRONISATION payload structure
6.3.3.4.2 T1
Description: RNC specific frame number (RFN) that indicates the time when RNC sends the frame through the SAP to the transport layer.
Value range: {0 .. 40959.875 ms}.
Granularity: 0.125ms.
Field length: 24 bits.
6.3.3.4.3 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.5 UL NODE SYNCHRONISATION
6.3.3.5.1 Payload Structure
The payload of the UL Node synchronisation control frames is shown in figure 30.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
|
|
T1 |
1 |
Payload |
|||||||
|
T1 (cont) |
1 |
||||||||
|
T1 (cont) |
1 |
||||||||
|
T2 |
1 |
||||||||
|
T2 (cont) |
1 |
||||||||
|
T2 (cont) |
1 |
||||||||
|
T3 |
1 |
||||||||
|
T3 (cont) |
1 |
||||||||
|
T3 (cont) |
1 |
||||||||
|
Spare Extension |
0-32 |
||||||||
Figure 30: UL NODE SYNCHRONISATION payload structure
6.3.3.5.2 T1
Description: T1 timer is extracted from the correspondent DL Node synchronisation control frame.
Value range: {0 .. 40959.875 ms.}
Granularity: 0.125ms.
Field length: 24 bits.
6.3.3.5.3 T2
Description: Node B specific frame number (BFN) that indicates the time when Node B received the correspondent DL synchronisation frame through the SAP from the transport layer.
Value range: {0 .. 40959.875 ms}.
Granularity: 0.125ms.
Field length: 24 bits.
6.3.3.5.4 T3
Description: Node B specific frame number (BFN) that indicates the time when Node B sends the frame through the SAP to the transport layer.
Value range: {0 .. 40959.875 ms}.
Granularity: 0.125ms.
Field length: 24 bits.
6.3.3.5.5 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.6 DYNAMIC PUSCH ASSIGNMENT [TDD]
6.3.3.6.1 Payload structure
The payload of the Dynamic PUSCH Assignment control frames is shown in figure 31.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
||
|
PUSCH Set Id |
Payload (3 bytes) |
||||||||
|
Activation CFN |
|||||||||
|
Duration |
|||||||||
Figure 31: DYNAMIC PUSCH ASSIGNMENT payload structure
6.3.3.6.2 PUSCH Set Id
Description: Identifies a PUSCH Set from the collection of PUSCH Sets which have been pre-configured in the Node B, for the respective cell in which the USCH exists. The PUSCH Set Id is unique within a cell.
Value range: {0..255}.
Field length: 8 bits.
6.3.3.6.3 Activation CFN
Description: Activation CFN, specifies the Connection Frame Number where the allocation period of that PUSCH Set starts.
Value range: Integer {0..255}.
Field length: 8 bits.
6.3.3.6.4 Duration
Description: Indicates the duration of the activation period of the PUSCH Set, in radio frames.
Value range: 0..255 means: 0 to 255 radio frames, i.e. 0 to 2550 msec.
Field length: 8 bits.
6.3.3.7 DSCH TFCI SIGNALLING [FDD]
6.3.3.7.1 Payload structure
Void.
6.3.3.7.2 TFCI (field 2)
Void.
6.3.3.7.3 Spare Extension
Void.
6.3.3.8 TIMING ADVANCE [3.84Mcps and 7.68Mcps TDD]
6.3.3.8.1 Payload structure
Figure 33 shows the structure of the payload when the control frame is used for timing advance.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of Octets |
||
|
CFN |
1 |
Payload |
||||||||
|
Spare |
TA |
1 |
||||||||
|
Spare Extension |
0-32 |
|||||||||
Figure 33: TIMING ADVANCE payload structure
6.3.3.8.2 CFN
Refer to subclause 6.2.7.3.
6.3.3.8.3 TA [3.84 Mcps]
Description: UE applied UL timing advance adjustment.
Value range: {0 .. 252 chips}.
Granularity: 4 chips.
Field length: 6 bits.
6.3.3.8.3A TA [7.68 Mcps]
Description: UE applied UL timing advance adjustment.
Value range: {0 .. 508 chips}.
Granularity: 4 chips.
Field length: 7 bits.
6.3.3.8.4 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.9 OUTER LOOP POWER CONTROL [1.28 Mcps TDD]
6.3.3.9.1 Payload structure
Figure 34 shows the structure of the payload when control frame is used for the UL outer loop power control.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of Octets |
|
|
UL_SIR_TARGET |
1 |
Payload |
|||||||
|
Spare Extension |
0-32 |
||||||||
Figure 34: Structure of the payload for OUTER LOOP PC control frame
6.3.3.9.2 SIR Target
Description: Value (in dB) of the SIR target to be used by the UL inner loop power control.
SIR Target is given in the unit UL_SIR_TARGET where:
UL_SIR_TARGET = 000 SIR Target = -8.2 dB
UL_SIR_TARGET = 001 SIR Target = -8.1 dB
UL_SIR_TARGET = 002 SIR Target = -8.0 dB
…
UL_SIR_TARGET = 254 SIR Target = 17.2 dB
UL_SIR_TARGET = 255 SIR Target = 17.3 dB
Value range: {-8.2 .. 17.3 dB}.
Granularity: 0.1 dB.
Field length: 8 bits.
6.3.3.9.3 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.10 HS-DSCH CAPACITY REQUEST
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of Bytes |
||
|
Spare bits 7-4 |
CmCH-PI |
1 |
Payload |
|||||||
|
User Buffer Size |
1 |
|||||||||
|
User Buffer Size (cont) |
1 |
|||||||||
|
Spare Extension |
0-32 |
|||||||||
Figure 35: CAPACITY REQUEST payload structure
The HS-DSCH CAPACITY REQUEST control frame is sent for each priority group to indicate the user buffer size. The control frame is sent by the CRNC when the CRNC considers the user buffer status needs an increased buffer reporting frequency. This may be sent to signal an event, such as, data arrival or user-buffer discard. This control frame is used to improve user-buffer reporting above the level produced by the user-buffer reporting associated with the HS-DSCH DATA FRAMEs.
6.3.3.10.1 Common Transport Channel Priority Indicator (CmCH-PI)
Refer to subclause 6.2.7.21.
6.3.3.10.2 User Buffer Size
Refer to subclause 6.2.7.22.
6.3.3.10.3 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.11 HS-DSCH CAPACITY ALLOCATION
Two types of HS-DSCH CAPACITY ALLOCATION exist for the HS-DSCH capacity allocation, i.e. HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame and HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|
Spare bits 7-6 |
Congestion Status |
CmCH-PI |
|||||
|
Maximum MAC-d PDU Length |
|||||||
|
Maximum MAC-d PDU Length (cont) |
HS-DSCH Credits |
||||||
|
HS-DSCH Credits (cont) |
|||||||
|
HS-DSCH Interval |
|||||||
|
HS0DSCH Repetition Period |
|||||||
|
Spare Extension |
|||||||
Figure 36: CAPACITY ALLOCATION TYPE 1 payload structure
The CAPACITY ALLOCATION TYPE 1 Control Frame describes an allocation that the CRNC may use. When the HS-DSCH Credits IE has a value of 0 it signifies that there is no resources allocated for transmission and to thus stop transmission. When the HS-DSCH Credits IE has a value of 2047, it signifies unlimited capacity for transmission of PDUs. When the HS-DSCH Repetition Period IE has a value of 0, it signifies that the allocation (Maximum MAC-d PDU Length, HS-DSCH Credits and HS-DSCH Interval IEs) can be repeated without limit. In addition to this the CAPACITY ALLOCATION TYPE 1 Control Frame informs the CRNC about the detection of congestion in the DL transport network layer with the Congestion Status Bits.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|
|
Spare bits 7-6 |
Congestion Status |
CmCH-PI |
||||||
|
Spare bits 7 – 3 |
Maximum MAC-d/c PDU Length |
|||||||
|
Maximum MAC-d/c PDU Length (cont) |
||||||||
|
HS-DSCH Credits |
||||||||
|
HS-DSCH Credits (cont) |
||||||||
|
HS-DSCH Interval |
||||||||
|
HS0DSCH Repetition Period |
||||||||
|
Spare Extension |
||||||||
Figure 37: CAPACITY ALLOCATION TYPE 2 payload structure
The CAPACITY ALLOCATION TYPE 2 Control Frame describes an allocation that the CRNC may use. When the HS-DSCH Credits IE has a value of 0 it signifies that there is no resources allocated for transmission and to thus stop transmission. When the HS-DSCH Credits IE has a value of 65535, it signifies unlimited capacity for transmission of PDUs. When the HS-DSCH Repetition Period IE has a value of 0, it signifies that the allocation (Maximum MAC-d/c PDU Length, HS-DSCH Credits and HS-DSCH Interval IEs) can be repeated without limit. In addition to this the CAPACITY ALLOCATION TYPE 2 Control Frame informs the CRNC about the detection of congestion in the DL transport network layer with the Congestion Status Bits.
6.3.3.11.1 Common Transport Channel Priority Indicator (CmCH-PI)
Refer to subclause 6.2.7.21.
6.3.3.11.2 Maximum MAC-d PDU Length
Description: The Maximum MAC-d PDU Length IE is used in HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame. The value indicates the maximum allowable PDU size among the MAC-d PDU sizes configured via NBAP (TS 25.433 [6]).
Value range: Refer to subclause 6.2.7.23.
Field length: Refer to subclause 6.2.7.23.
6.3.3.11.3 HS-DSCH Credits
Description: The HS-DSCH Credits IE is used in HS-DSCH CAPACITY ALLOCATION (TYPE 1 and TYPE 2) Control Frame. It indicates the granted amount of MAC-d PDU data that CRNC may transmit during one HD-DSCH interval
In case of HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame, it indicates the number of MAC-d PDUs that a CRNC may transmit during one HS-DSCH Interval granted in the HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame.
In case of HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame, the granted amount of MAC-d [FDD and 1.28Mcps TDD – or MAC-c] PDU data in octets is obtained by multiplying the MAC-d PDU length [FDD and 1.28Mcps TDD – or the MAC-c PDU length] (indicated by the Maximum MAC- d/c PDU Length IE) with the number of MAC-d PDUs [FDD and 1.28Mcps TDD – or MAC-c PDUs] (indicated by the HS-DSCH Credits IE).
Value range: {0-2047, where 0=stop transmission, 2047=unlimited} in case of HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame, {0-65535, where 0=stop transmission, 65535=unlimited} in case of HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame.
Field length: 11 bits in case of HS-DSCH CAPACITY ALLOCATION TYPE 1 Control Frame, 16 bits in case of HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame.
6.3.3.11.4 HS-DSCH Interval
Description: The value of this field indicates the time interval during which the HS-DSCH Credits granted in the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame may be used. The first interval starts immediately after reception of the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame, subsequent intervals start immediately after the previous interval has elapsed. This value is only applied to the HS-DSCH transport channel.
Value range: {0-2550 ms}. Value 0 shall be interpreted that none of the credits shall be used.
Granularity: 10ms.
Field Length: 8 bits.
6.3.3.11.5 HS-DSCH Repetition Period
Description: The value of this field indicates the number of subsequent intervals that the HS-DSCH Credits IE granted in the HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame may be used. These values represent an integer number of Intervals (see subclause 6.3.3.11.4). This field is only applied to the HS-DSCH transport channel.
Value range: {0-255, where 0= unlimited repetition period}.
Field Length: 8 bits.
6.3.3.11.6 Spare Extension
Refer to subclause 6.3.3.1.4.
6.3.3.11.7 Congestion Status
Description: The Congestion Status Bits are used by the Node B to indicate whether a congestion situation is detected in a DL transport network layer or not. The Node B provides the congestion status in every HS-DSCH CAPACITY ALLOCATION (TYPE 1 or TYPE 2) Control Frame, which the CRNC may use.
Value range:
0 No TNL Congestion
1 Reserved for future use
2 TNL Congestion – detected by delay build-up
3 TNL Congestion – detected by frame loss
Field Length: 2 bits.
6.3.3.11.8 Maximum MAC-d/c PDU Length
Description: The Maximum MAC-d/c PDU Length IE is used in HS-DSCH CAPACITY ALLOCATION TYPE 2 Control Frame. The value is a factor in the granted amount of MAC-d PDU data that a CRNC may transmit during one HS-DSCH Interval. The amount of MAC-d [FDD and 1.28Mcps TDD – or MAC-c ] PDU data in octets is obtained by multiplying the MAC-d [FDD and 1.28Mcps TDD – or MAC-c ] PDU length (indicated by the Maximum MAC d/c PDU Length IE) with the number of MAC-d PDUs [FDD and 1.28Mcps TDD – or MAC-c PDUs] (indicated by the HS-DSCH Credits IE).
Value range: {0-1505}, 0 – not used.
Field length: 11 bits.
6.3.3.12 HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE [1.28Mcps TDD]
6.3.3.12.1 Payload structure
The payload of the HS-DSCH UL Synchronization Establishment Failure control frames is shown in figure 38.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
|
|
H-RNTI |
1 |
Payload |
|||||||
|
H-RNTI (cont.) |
1 |
||||||||
|
Spare Extension |
0-32 |
||||||||
Figure 38: HS-DSCH UL SYNCHRONIZATION ESTABLISHMENT FAILURE payload structure
6.3.3.12.2 H-RNTI
Refer to subclause 6.2.7.37.
6.3.3.13 HS-DSCH PDU DROP INDICATION
6.3.3.13.1 Payload structure
The payload of the HS-DSCH PDU Drop Indication control frame is shown in figure 39.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Number of bytes |
||||
|
Spare bit 7 to 3 |
Drop Reason |
1 |
Payload |
|||||||||
|
Number of PDUs Dropped |
1 |
|||||||||||
|
SN 1 |
1 |
|||||||||||
|
SN 1 (cont) |
Spare |
1 |
||||||||||
|
PDU 1 Index |
1 |
|||||||||||
|
… |
1 |
|||||||||||
|
SN N |
1 |
|||||||||||
|
SN N (cont) |
Spare |
1 |
||||||||||
|
PDU N Index |
1 |
|||||||||||
|
Spare Extension |
0-32 |
|||||||||||
Figure 39: HS-DSCH PDU DROP INDICATION payload structure
6.3.3.13.2 Drop Reason
Description: The Drop Reason IE is used in HS-DSCH PDU DROP INDICATION Control Frame. It indicates the reason of drop of HS-DSCH PDUs in Node B.
Value range:
0 too long delay in MAC-hs/ehs buffer
1 unsuccessful HARQ due to T1 timer expiry
2 TNL Congestion – detected by frame loss
3 to 7 are reserved
Field length: 3 bits
6.3.3.13.3 PDU Index
Description: The PDU Index IE identifies the PDU index in the HS-DSCH DATA FRAME.
Value range: {0-255}.
Field length: 8 bits.