3GPP TS 25.427 V6.8.

0 (2006-12)
Technical Specification

3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub/Iur interface user plane protocol for DCH data streams (Release 6)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

Keywords
UMTS. radio

3GPP Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
http://www.3gpp.org

Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
2006, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved.

3GPP

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

Contents
Foreword ............................................................................................................................................................6 1 2 3
3.1 3.2 3.3

Scope ........................................................................................................................................................7 References ................................................................................................................................................7 Definitions and abbreviations...................................................................................................................7

Definitions ......................................................................................................................................................... 7 Abbreviations..................................................................................................................................................... 8 Specification Notations...................................................................................................................................... 8

4
4.1 4.2 4.3

General aspects.........................................................................................................................................9
DCH and E-DCH FP services............................................................................................................................ 9 Services expected from the Data Transport Network layer ............................................................................. 10 Protocol Version .............................................................................................................................................. 10

5
5.1 5.1.0 5.1.1 5.1.1a 5.1.2 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.10.1 5.10.2 5.11 5.12 5.13 5.14

DCH Frame Protocol procedures ...........................................................................................................10

Data Transfer ................................................................................................................................................... 10 General....................................................................................................................................................... 10 Uplink for DCH ......................................................................................................................................... 10 Uplink for E-DCH [FDD] .......................................................................................................................... 11 Downlink.................................................................................................................................................... 11 Timing Adjustment.......................................................................................................................................... 12 DCH Synchronisation...................................................................................................................................... 13 Outer Loop PC Information Transfer [FDD, 1.28 Mcps TDD]....................................................................... 13 Node Synchronisation...................................................................................................................................... 13 Rx Timing Deviation Measurement [3.84 Mcps TDD]................................................................................... 14 DSCH TFCI Signalling [FDD]........................................................................................................................ 14 Radio Interface Parameter Update [FDD] ....................................................................................................... 15 Timing Advance [3.84 Mcps TDD]................................................................................................................. 15 General............................................................................................................................................................. 15 Transport bearer replacement..................................................................................................................... 15 Transport channel addition......................................................................................................................... 16 Generation of subframe number [FDD]........................................................................................................... 16 Generation of number of HARQ retransmissions [FDD] ................................................................................ 16 Indication of HARQ failure [FDD] ................................................................................................................. 17 TNL Congestion Indication [FDD] ................................................................................................................. 17

Frame structure and coding ....................................................................................................................18

6.1 General............................................................................................................................................................. 18 6.1.1 General principles for the coding............................................................................................................... 18 6.2 Data frames...................................................................................................................................................... 19 6.2.1 Introduction................................................................................................................................................ 19 6.2.2 UL DATA FRAME ................................................................................................................................... 19 6.2.2.1 UL DATA FRAME FOR DCH............................................................................................................ 19 6.2.2.2 UL DATA FRAME FOR E-DCH [FDD] ............................................................................................ 21 6.2.3 DL DATA FRAME ................................................................................................................................... 22 6.2.4 Coding of information elements in data frames ......................................................................................... 24 6.2.4.1 Header CRC ......................................................................................................................................... 24 6.2.4.2 Frame Type (FT) .................................................................................................................................. 24 6.2.4.3 Connection Frame Number (CFN) ....................................................................................................... 24 6.2.4.4 Transport Format Indicator (TFI)......................................................................................................... 24 6.2.4.5 Quality Estimate (QE) .......................................................................................................................... 24 6.2.4.6 Transport Block (TB) ........................................................................................................................... 25 6.2.4.7 CRC indicator (CRCI).......................................................................................................................... 25 6.2.4.8 Payload CRC ........................................................................................................................................ 25 6.2.4.9 Spare Extension.................................................................................................................................... 25 6.2.4.10 Subframe Number [FDD]..................................................................................................................... 25

3GPP

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

6.2.4.11 Number of HARQ Retransmissions, NHR [FDD] ............................................................................... 25 6.2.4.12 Number of Subframes [FDD]............................................................................................................... 26 6.2.4.13 Number of MAC-es PDUs [FDD]........................................................................................................ 26 6.2.4.14 Data Description Indicator, DDI [FDD]............................................................................................... 26 6.2.4.15 Number of MAC-d PDUs, N [FDD] .................................................................................................... 26 6.2.4.16 FSN Frame Sequence Number [FDD]............................................................................................... 26 6.3 Control frames ................................................................................................................................................. 26 6.3.1 Introduction................................................................................................................................................ 26 6.3.2 Header structure of the control frames....................................................................................................... 27 6.3.2.1 Frame CRC........................................................................................................................................... 27 6.3.2.2 Frame Type (FT) .................................................................................................................................. 27 6.3.2.3 Control Frame Type ............................................................................................................................. 27 6.3.3 Payload structure and information elements .............................................................................................. 28 6.3.3.1 TIMING ADJUSTMENT .................................................................................................................... 28 6.3.3.1.1 Payload structure............................................................................................................................. 28 6.3.3.1.2 CFN................................................................................................................................................. 28 6.3.3.1.3 Time of Arrival (ToA) .................................................................................................................... 28 6.3.3.1.4 Spare Extension .............................................................................................................................. 29 6.3.3.2 DL SYNCHRONISATION.................................................................................................................. 29 6.3.3.2.1 Payload structure............................................................................................................................. 29 6.3.3.2.2 CFN................................................................................................................................................. 29 6.3.3.2.3 Spare Extension .............................................................................................................................. 29 6.3.3.3 UL SYNCHRONISATION.................................................................................................................. 29 6.3.3.3.1 Payload structure............................................................................................................................. 29 6.3.3.3.2 CFN................................................................................................................................................. 30 6.3.3.3.3 Time of Arrival (ToA) .................................................................................................................... 30 6.3.3.3.4 Spare Extension .............................................................................................................................. 30 6.3.3.4 OUTER LOOP POWER CONTROL [FDD, 1.28Mcps TDD]............................................................ 30 6.3.3.4.1 Payload structure............................................................................................................................. 30 6.3.3.4.2 SIR Target....................................................................................................................................... 30 6.3.3.4.3 Spare Extension .............................................................................................................................. 31 6.3.3.5 DL NODE SYNCHRONISATION...................................................................................................... 31 6.3.3.5.1 Payload structure............................................................................................................................. 31 6.3.3.5.2 T1.................................................................................................................................................... 31 6.3.3.5.3 Spare Extension .............................................................................................................................. 31 6.3.3.6 UL NODE SYNCHRONISATION...................................................................................................... 32 6.3.3.6.1 Payload structure............................................................................................................................. 32 6.3.3.6.2 T1.................................................................................................................................................... 32 6.3.3.6.3 T2.................................................................................................................................................... 32 6.3.3.6.4 T3.................................................................................................................................................... 33 6.3.3.6.5 Spare Extension .............................................................................................................................. 33 6.3.3.7 RX TIMING DEVIATION [3.84Mcps TDD] ..................................................................................... 33 6.3.3.7.1 Payload structure............................................................................................................................. 33 6.3.3.7.2 Rx Timing Deviation ...................................................................................................................... 33 6.3.3.7.3 Spare Extension .............................................................................................................................. 33 6.3.3.7.4 CFN................................................................................................................................................. 33 6.3.3.8 DSCH TFCI SIGNALLING [FDD]..................................................................................................... 34 6.3.3.8.1 Payload structure............................................................................................................................. 34 6.3.3.8.2 TFCI (field 2).................................................................................................................................. 34 6.3.3.8.3 Spare Extension .............................................................................................................................. 34 6.3.3.8.4 CFN................................................................................................................................................. 34 6.3.3.9 RADIO INTERFACE PARAMETER UPDATE [FDD] ..................................................................... 34 6.3.3.9.1 Payload structure............................................................................................................................. 34 6.3.3.9.2 Radio Interface Parameter Update flags ......................................................................................... 35 6.3.3.9.3 TPC Power Offset (TPC PO).......................................................................................................... 36 6.3.3.9.4 Spare Extension .............................................................................................................................. 36 6.3.3.9.4A CFN................................................................................................................................................. 36 6.3.3.9.5 DPC Mode ...................................................................................................................................... 36 6.3.3.9.6 TFCI Power Offset (TFCI PO) ....................................................................................................... 36 6.3.3.9.7 TFCI Power Offset for primary cell (TFCI PO_primary)............................................................... 36 6.3.3.9.8 Multiple RL Sets Indicator.............................................................................................................. 36

3GPP

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

6.3.3.9.9 6.3.3.10 6.3.3.10.1 6.3.3.10.2 6.3.3.10.3 6.3.3.10.4 6.3.3.11 6.3.3.11.1 6.3.3.11.2 6.3.3.11.3

Maximum UE TX Power ................................................................................................................ 36 TIMING ADVANCE [3.84Mcps TDD] .............................................................................................. 37 Payload structure............................................................................................................................. 37 CFN................................................................................................................................................. 37 TA ................................................................................................................................................... 37 Spare Extension .............................................................................................................................. 37 TNL CONGESTION INDICATION [FDD]....................................................................................... 37 Payload structure............................................................................................................................. 37 Congestion Status ........................................................................................................................... 38 Spare Extension .............................................................................................................................. 38 General............................................................................................................................................................. 38 Error detection ................................................................................................................................................. 38 CRC Calculation ........................................................................................................................................ 38 Relation between input and output of the Cyclic Redundancy Check ................................................. 39

7
7.1 7.2 7.2.1 7.2.1.1

Handling of Unknown, Unforeseen and Erroneous Protocol Data ........................................................38

Annex A (informative):

Change history ...............................................................................................40

3GPP

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.

3GPP

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

Scope

The present document shall provide a description of the UTRAN Iur and Iub interfaces user plane protocols for Dedicated Transport Channel data streams as agreed within the TSG-RAN working group 3.

References
References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] 3GPP TS 25.301: "Radio Interface Protocol Architecture". 3GPP TS 25.401: "UTRAN Overall Description". 3GPP TS 25.302: "Services provided by the Physical Layer". 3GPP TS 25.433: "UTRAN Iub interface NBAP signalling". 3GPP TS 25.402: "Synchronization in UTRAN, Stage 2". 3GPP TS 25.423: "UTRAN Iur interface RNSAP signalling". 3GPP TS 25.133: Requirements for support of radio resource management (FDD). 3GPP TS 25.123: Requirements for support of radio resource management (TDD). 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". 3GPP TS 25.224: "Physical Layer Procedures (TDD)". 3GPP TS 25.214: "Physical Layer Procedures (FDD)". 3GPP TS 25.309: FDD Enhanced Uplink; Overall description; Stage 2 3GPP TS 25.101: User Equipment (UE) Radio Transmission and Reception (FDD) 3GPP TS 25.331: Radio Resource Control (RRC) Protocol Specification

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

3
3.1

Definitions and abbreviations

Definitions

For the purposes of the present document, the following terms and definitions apply: Transport Bearer: service provided by the transport layer and used by frame protocol for the delivery of FP PDU

3GPP

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

3.2
BER CFN CRC CRCI DCH DL DPC DSCH DTX E-DCH FP FT HARQ LTOA PC QE RL SIR TB TBS TFI TFCI ToA ToAWE ToAWS TPC TTI UE UL

Abbreviations
Bit Error Rate Connection Frame Number Cyclic Redundancy Checksum CRC Indicator Dedicated Transport Channel Downlink Downlink Power Control Downlink Shared Channel Discontinuous Transmission Enhanced DCH Frame Protocol Frame Type Hybrid ARQ Latest Time of Arrival Power Control Quality Estimate Radio Link Signal-to-Interference Ratio Transport Block Transport Block Set Transport Format Indicator Transport Format Combination Indicator Time of Arrival Time of Arrival Window Endpoint Time of Arrival Window Startpoint Transmit Power Control Transmission Time Interval User Equipment Uplink

For the purposes of the present document, the following abbreviations apply:

3.3
[FDD]

Specification Notations
This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD and 1.28Mcps TDD.

For the purposes of the present document, the following notations apply:

[TDD]

[3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. [FDD - ] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.

3GPP

Release 6T

3GPP TS 25.427 V6.8.0 (2006-12)

[TDD - ]

This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.

[3.84Mcps TDD - ] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. [1.28Mcps TDD - ] This tagging indicates that the enclosed text following the "[1.28Mcps TDD " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. Procedure When referring to a procedure in the specification, the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Timing Adjustment procedure. When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DL SYNCHRONISATION control frame. When referring to an information element (IE) in the specification, the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Connection Frame Number IE. When referring to the value of an information element (IE) in the specification, the "Value" is written as it is specified in subclause 6.2.4 or 6.3.3 enclosed by quotation marks, e.g. "0" or "255".

Frame

IE

Value of an IE

General aspects

The specification of Iub DCH and E-DCH data streams is also valid for Iur DCH and E-DCH data streams. The complete configuration of the transport channel is selected by the SRNC and signalled to the Node B via the Iub and Iur control plane protocols. The parameters of a transport channel are described in [1]. Transport channels are multiplexed on the downlink by the Node B on radio physical channels, and de-multiplexed on the uplink from radio physical channels to transport channels. In Iur interface, every set of coordinated transport channels related to one UE context that is communicated over a set of cells that are macro-diversity combined within Node B or DRNC, is carried on one transport bearer. This means that there are as many transport bearers as set of coordinated transport channels and Iur DCH data ports for that communication. In Iub interface, every set of coordinated transport channels related to one UE context that is communicated over a set of cells that are macro-diversity combined within Node B is carried on one transport bearer. This means that there are as many transport bearers as set of coordinated transport channels and Iub DCH data ports for that communication. Bi-directional transport bearers are used.

4.1
-

DCH and E-DCH FP services

Transport of TBS across Iub and Iur interface. Transport of outer loop power control information between the SRNC and the Node B. Support of transport channel synchronisation mechanism.

DCH frame protocol provides the following services:

3GPP

Release 6T

10

3GPP TS 25.427 V6.8.0 (2006-12)

Support of node synchronization mechanism. [3.84 Mcps TDD - Transfer of Rx timing deviation from the Node B to the SRNC.] Transfer of radio interface parameters from the SRNC to the Node B.

[FDD E-DCH frame protocol provides the following services: Transport of MAC-es PDUs across Iub and Iur interface from Node B to SRNC. Transport of outer loop power control information between the SRNC and the Node B. Transfer of radio interface parameters from the SRNC to the Node B. Transport of network congestion indication signal from SRNC across Iub and Iur interface. Transport of hybrid ARQ information between SRNC and nNode B.]

4.2
-

Services expected from the Data Transport Network layer

Delivery of FP PDU.

Following service is required from the transport layer:

In sequence delivery is not required. However, frequent out-of-sequence delivery may impact the performance and should be avoided.

4.3

Protocol Version

This revision of the specification specifies version 1 of the protocol.

5
5.1
5.1.0

DCH Frame Protocol procedures

Data Transfer
General

When there is some data to be transmitted, DCH data frames are transferred every transmission time interval from the SRNC to the Node B for downlink transfer, and DCH/E-DCH data frames are transferred every transmission time interval from Node B to the SRNC for uplink transfer. [FDD For 2 ms Uu TTI and depending on configuration from higher layers, the uplink E-DCH MAC-es PDUs from one or more 2ms Uu TTIs may be bundled into one E-DCH Data Frame before being transferred at an interval of e.g. 10ms from the Node B to the SRNC.] An optional error detection mechanism may be used to protect the data transfer if needed. At the transport channel setup it shall be specified if the error detection on the user data is used.

5.1.1

Uplink for DCH

Node B SRNC

UL DATA FRAME

Figure 1: Uplink Data Transfer procedure

3GPP

Release 6T

11

3GPP TS 25.427 V6.8.0 (2006-12)

Two modes can be used for the UL transmission: normal mode and silent mode. The mode is selected by the SRNC when the transport bearer is setup and signalled to the Node B with the relevant control plane procedure. In normal mode, the Node B shall always send an UL DATA FRAME to the RNC for all the DCHs in a set of coordinated DCHs regardless of the number of Transport Blocks of the DCHs. In silent mode and in case only one transport channel is transported on a transport bearer, the Node B shall not send an UL DATA FRAME to the RNC when it has received a TFI indicating "number of TB equal to 0" for the transport channel during a TTI. In silent mode and in case of coordinated DCHs, when the Node B receives a TFI indicating "number of TB equal to 0" for all the DCHs in a set of coordinated DCHs, the Node B shall not send an UL DATA FRAME to the RNC for this set of coordinated DCHs.

For any TTI in which the Node B Layer 1 generated at least one CPHY-Out-of-Sync-IND primitive, the Node B is not required to send an UL DATA FRAME to the SRNC. When Node B receives an invalid TFCI, no UL DATA FRAME shall be sent to the SRNC.

5.1.1a

Uplink for E-DCH [FDD]

Node B E-DCH UL DATA FRAME SRNC

Figure 1a: Uplink Data Transfer procedure When a MAC-e PDU is received, it is demultiplexed into MAC-d flows which are then each sent on separate transport bearers to the RNC using the E-DCH UL DATA FRAME. Only silent mode is used, i.e. E-DCH user-plane payload is transmitted using the E-DCH UL DATA FRAME only when some payload has been successfully received.

5.1.2

Downlink
Node B DL DATA FRAME SRNC

Figure 2: Downlink Data Transfer procedure The Node B shall only consider a transport bearer synchronised after it has received at least one DL DATA FRAME on this transport bearer before LTOA [5]. The Node B shall consider the DL user plane of a certain RL synchronised once all transport bearers established to carry DCH DL DATA FRAMEs included in the CCTrCH for this RL are considered as synchronised. Once synchronised, the Node B shall assume the DL user plane for this Radio Link stays synchronised as long as the Radio Link exists, even if transport bearers are added (see 5.10.2), replaced (see subclause 5.10.1), or removed. When a RL established through the Radio Link Addition procedure [4] [6] is combined with a RL whose DL user plane is considered as synchronised, the Node B shall consider the DL user plane of this newly established RL as synchronised.

3GPP

Release 6T

12

3GPP TS 25.427 V6.8.0 (2006-12)

[FDD - The Node B shall transmit on the DL DPDCH(s) of a certain RL only when the DL user plane of this RL is considered synchronised.] [TDD The Node B shall transmit special bursts on the DL DPCH as per [11], until the DL user plane is considered synchronised]. When the DL user plane is considered synchronised and the Node B does not receive a valid DL DATA FRAME in a TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel, and shall act as one of the following cases: [TDD If the Node B receives no valid DL DATA FRAMEs for any transport channel assigned to a UE it shall assume DTX and transmit special bursts as per [11]]. If the Node B is aware of a TFI value corresponding to zero bits for this transport channel, this TFI is assumed. If the TFS contains both a TFI corresponding to "TB length equal to 0 bits" and a TFI corresponding to "number of TB equal to 0", the Node B shall assume the TFI corresponding to "number of TB equal to 0". When combining the TFI's of the different transport channels, a valid TFCI might result and in this case data shall be transmitted on Uu. If the Node B is not aware of a TFI value corresponding to zero bits for this transport channel or if combining the TFI corresponding to zero bits with other TFI's, results in an unknown TFI combination, the handling as described in the following paragraph shall be applied.

At each radio frame, the Node B shall build the TFCI value of each CCTrCH, according to the TFI of the DCH data frames multiplexed on this CCTrCH and scheduled for that frame. [FDD - In case the Node B receives an unknown combination of TFIs from the DL DATA FRAMEs, it shall transmit only the DPCCH without TFCI bits.] [TDD - In case the Node B receives an unknown combination of DCH DL DATA FRAMEs, it shall apply DTX, i.e. suspend transmission on the corresponding DPCHs.]

5.2

Timing Adjustment

The Timing Adjustment procedure is used to keep the synchronization of the DCH data stream in DL direction, i.e to ensure that the Node B receives the DL frames in an appropriate time for the transmission of the data in the air interface. SRNC always includes the Connection Frame Number (CFN) to all DCH DL DATA FRAMEs. If a DL DATA FRAME arrives outside the arrival window defined in the Node B, the Node B shall send a TIMING ADJUSTMENT control frame, containing the measured ToA and the CFN value of the received DL DATA FRAME.

Node B

SRNC

TIMING ADJUSTMENT

Figure 3: Timing Adjustment procedure The arrival window and the time of arrival are defined as follows: Time of Arrival Window Endpoint (ToAWE): ToAWE represents the time point by which the DL data shall arrive to the Node B from Iub. The ToAWE is defined as the amount of milliseconds before the last time point from which a timely DL transmission for the identified CFN would still be possible taking into account the Node B internal delays. ToAWE is set via control plane. If data does not arrive before ToAWE a TIMING ADJUSTMENT control frame shall be sent by Node B. Time of Arrival Window Startpoint (ToAWS): ToAWS represents the time after which the DL data shall arrive to the Node B from Iub. The ToAWS is defined as the amount of milliseconds from the ToAWE. ToAWS is set via control plane. If data arrives before ToAWS a TIMING ADJUSTMENT control frame shall be sent by Node B.

3GPP

Release 6T

13

3GPP TS 25.427 V6.8.0 (2006-12)

Time of Arrival (ToA): ToA is the time difference between the end point of the DL arrival window (ToAWE) and the actual arrival time of DL frame for a specific CFN. A positive ToA means that the frame is received before the ToAWE, a negative ToA means that the frame is received after the ToAWE. The general overview on the Timing Adjustment procedure is reported in [2].

5.3

DCH Synchronisation

DCH Synchronisation procedure is used to achieve or restore the synchronisation of the DCH data stream in DL direction, and as a keep alive procedure in order to maintain activity on the Iur/Iub transport bearer. The procedure is initiated by the SRNC by sending a DL SYNCHRONISATION control frame towards Node B. This control frame indicates the target CFN. Upon reception of the DL SYNCHRONISATION control frame, Node B shall immediately respond with UL SYNCHRONISATION control frame indicating the ToA for the DL SYNCHRONISATION control frame and the CFN indicated in the received DL SYNCHRONISATION control frame. UL SYNCHRONISATION control frame shall always be sent, even if the DL SYNCHRONISATION control frame is received by the Node B within the arrival window.

Node B

SRNC

DL SYNCHRONISATION UL SYNCHRONISATION

Figure 4: DCH Synchronisation procedure

5.4

Outer Loop PC Information Transfer [FDD, 1.28 Mcps TDD]

Based, for example, on the CRCI values and on the quality estimate in the UL DATA FRAME, SRNC modifies the SIR target used by the UL inner loop power control by including the absolute value of the new SIR target in the OUTER LOOP PC control frame sent to the Node B's. At the reception of the OUTER LOOP PC control frame, the Node B shall immediately update the SIR target used for the inner loop power control [1.28 Mcps TDD - of the respective CCTrCH for UL DCHs] with the specified value. The OUTER LOOP PC control frame can be sent via any of the transport bearers dedicated to one UE. [1.28 Mcps TDD - In case of multiple CCTrCHs carrying DCHs, the OUTER LOOP PC control frame can be sent via any of the transport bearers carrying DCHs which belong to the CCTrCH for which the UL SIR target shall be adjusted.]

Node B

SRNC

OUTER LOOP PC

Figure 5: Outer Loop Power Control Information Transfer procedure

5.5

Node Synchronisation

The Node Synchronisation procedure is used by the SRNC to acquire information on the Node B timing.

3GPP

Release 6T

14

3GPP TS 25.427 V6.8.0 (2006-12)

The procedure is initiated by the SRNC by sending a DL NODE SYNCHRONISATION control frame to Node B containing the parameter T1. Upon reception of a DL NODE SYNCHRONISATION control frame, the Node B shall respond with UL NODE SYNCHRONISATION control frame, including the parameters T2 and T3, as well as the T1 which was indicated in the initiating DL NODE SYNCHRONISATION control frame. The T1, T2, T3 parameters are defined as: T1: RNC specific frame number (RFN) that indicates the time when RNC sends the DL NODE SYNCHRONISATION control frame through the SAP to the transport layer. T2: Node B specific frame number (BFN) that indicates the time when Node B receives the correspondent DL NODE SYNCHRONIZATION control frame through the SAP from the transport layer. T3: Node B specific frame number (BFN) that indicates the time when Node B sends the UL NODE SYNCHRONISATION control frame through the SAP to the transport layer. The general overview on the Node Synchronisation procedure is reported in [2].

Node B

SRNC

DL NODE SYNCHRONISATION

UL NODE SYNCHRONISATION

Figure 6: Node Synchronisation procedure

5.6

Rx Timing Deviation Measurement [3.84 Mcps TDD]

In case the Timing Advance Applied IE indicates "Yes" (see [4]) in a cell, the Node B shall, for all UEs using DCHs, monitor the receiving time of the uplink DPCH bursts arriving over the radio interface, and shall calculate the Rx timing deviation. If the calculated value, after rounding, is not zero, it shall be reported to the SRNC in a RX TIMING DEVIATION control frame belonging to that UE. For limitation of the frequency of this reporting, the Node B shall not send more than one RX TIMING DEVIATION control frame per UE within one radio frame. If the Timing Advance Applied IE indicates "No" (see [4]) in a cell, monitoring of the receiving time of the uplink DPCH bursts is not necessary and no RX TIMING DEVIATION control frame shall be sent.

Node B

SRNC

RX TIMING DEVIATION

Figure 7: Rx Timing Deviation Measurement procedure

5.7
Void.

DSCH TFCI Signalling [FDD]

3GPP

Release 6T

15

3GPP TS 25.427 V6.8.0 (2006-12)

5.8

Radio Interface Parameter Update [FDD]

This procedure is used to update radio interface parameters which are applicable to all RL's, or E-DCH Serving Radio Link Set, for the concerning UE. Both synchronised and unsynchronised parameter updates are supported. The procedure consists of a RADIO INTERFACE PARAMETER UPDATE control frame sent by the SRNC to the Node B.

Node B

SRNC

RADIO INTERFACE PARAMETER UPDATE

Figure 9: Radio Interface Parameter Update procedure If the RADIO INTERFACE PARAMETER UPDATE control frame contains a valid TPC power offset value, the Node B shall apply the newly provided TPC PO in DL. If the RADIO INTERFACE PARAMETER UPDATE control frame contains a valid Maximum UE TX Power value, the E-DCH serving Node B may use the provided value to improve E-DCH scheduling. If the frame contains a valid DPC mode value, the Node B shall apply the newly provided value in DL power control. The new values shall be applied as soon as possible in case no valid CFN is included or from the indicated CFN. If the frame contains a valid Multiple RL Sets Indicator value, the Node B may use the newly provided value in Multiple RL Sets Indicator whenever the Node B loses UL synchronization on a RL Set after initial UL synchronization as described in [12].

5.9

Timing Advance [3.84 Mcps TDD]

This procedure is used in order to signal to the Node B the adjustment to be performed by the UE in the uplink timing. The Node B shall use the CFN and timing adjustment values to adjust its layer 1 to allow for accurate impulse averaging.

Node B TIMING ADVANCE

SRNC

Figure 9A: Timing Advance procedure

5.10
5.10.1

General
Transport bearer replacement

As described in NBAP [4] and RNSAP [6], transport bearer replacement can be achieved by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure, or by using the Unsynchronised Radio Link Reconfiguration procedure. In both cases the following steps can be discerned: 1) The new transport bearer is established after which 2 transport bearers exist in parallel.

3GPP

Release 6T

16

3GPP TS 25.427 V6.8.0 (2006-12)

2) The transport channel(s) is/are switched to the new transport bearer. 3) The old transport bearer is released. In step 1), communication on the old transport bearer continues as normal. In addition, the Node B shall support DL DATA FRAMEs, the DCH Synchronisation procedure (see section 5.3) and the Timing Adjustment procedure (see section 5.2) on the new bearer. This enables the SRNC to determine the timing on the new transport bearer. DL DATA FRAMEs transported on the new transport bearer shall not be transmitted on the DL DPDCH before the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message. Regarding step 2), the moment of switching is determined differently in the synchronised and unsynchronised case: When using the combination of the Synchronised Radio Link Reconfiguration Preparation procedure and the Synchronised Radio Link Reconfiguration Commit procedure, the UL/DL DATA FRAMEs shall be transported on the new transport bearer from the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message. When using the Unsynchronised Radio Link Reconfiguration procedure, the Node B shall start using the new transport bearer for the transport of UL DATA FRAMEs from the CFN at which the new transport bearer is considered synchronised (i.e. has received a DL DATA FRAME before LTOA [4]). [FDD - Not applicable for E-DCH. Change is done directly in case of an E-DCH.]

In both cases, starting from this CFN the Node-B shall support all applicable DCH/E-DCH Frame Protocol procedures on the new transport bearer and no requirements exist regarding support of DCH/E-DCH Frame Protocol procedures on the old transport bearer. Finally in step 3), the old transport bearer is released.

5.10.2

Transport channel addition

As described in NBAP [4] and RNSAP [6], transport channel addition can be achieved by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure, or by using the Unsynchronised Radio Link Reconfiguration procedure. When using the Synchronised Radio Link Reconfiguration Preparation procedure the Node B shall support DL DATA FRAMEs, the Synchronisation procedure (see section 5.3) and the Timing Adjustment procedure (see section 5.2) on the new transport bearer also before the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message, in order to enable the SRNC to determine the timing on the new transport bearer. DL DATA FRAMEs transported on the new transport bearer before this CFN shall not be transmitted on the DL DPDCH. Starting from this CFN the Node B shall support all applicable DCH and E-DCH frame protocol procedures on the new transport bearer. When using the Unsynchronised Radio Link Reconfiguration procedure the Node B shall support data frames and control frames when the new transport bearer is established.

5.11

Generation of subframe number [FDD]

The CFN and Subframe Number IEs values in the E-DCH Data Frame shall reflect the CFN and subframe number when the payload in the E-DCH Data Frame was correctly received on the Uu. This corresponds to when the HARQ process correctly decoded the data. The subframe number is for 2 ms TTI set to values {0-4} and for 10 ms TTI set to {0}.

5.12 Generation of number of HARQ retransmissions [FDD]

After successful decoding of E-DCH payload received over Uu, the Node B shall insert the following values in the Number of HARQ Retransmissions IE: If the RSN value in the last HARQ retransmission that resulted in successful decoding has the value 0, 1 or 2, then the Node B shall insert the same value in the Number Of HARQ Retransmissions IE in the E-DCH Data Frame.

3GPP

Release 6T

17

3GPP TS 25.427 V6.8.0 (2006-12)

If the RSN value in the last HARQ retransmission that resulted in successful decoding has the value 3, then the Node B shall insert the calculated value of the actual number of retransmissions used for the successful decoding into the Number of HARQ Retransmissions IE in the E-DCH Data Frame. If the actual number of retransmission cannot be calculated, then the Node B shall insert the value 15 in the Number of HARQ Retransmissions IE, indicating that the number of HARQ retransmissions is unknown.

After unsuccessful decoding of the E-DCH payload, the serving Node B shall act according to section 5.13, Indication of HARQ failure.

5.13 Indication of HARQ failure [FDD]

After unsuccessful decoding of the E-DCH payload and under conditions listed below, the serving Node B shall send a HARQ Failure Indication to the SRNC. The non-serving Node B(s) shall not send a HARQ Failure Indication. The serving Node B shall send a HARQ Failure Indication to the SRNC under any of the following conditions: A MAC-e PDU for a HARQ process has not yet been successfully decoded and the RSN indicates the transmission of a new MAC-e PDU for the same HARQ process and the number of HARQ retransmissions that had already occurred was equal or higher than the lowest of the maximum HARQ retransmissions values for the UEs configured MAC-d flows. A MAC-e PDU for a HARQ process has not yet been successfully decoded and the maximum retransmissions for the MAC-d flow with the highest maximum HARQ retransmissions value valid for the UE connection have occurred, or should have occurred in case the HARQ related outband signalling (RSN) on the E-DPCCH could not be decoded. A MAC-e PDU for a HARQ process has not yet been successfully decoded when the MAC-e Reset is performed in UE. The Node B knows the timing of the MAC-e Reset in the UE via higher layer.

The HARQ Failure Indication shall be sent on only one transport bearer. The Node B may select any of the transport bearers associated with the UE for which the HARQ failure relates to. The HARQ failure is indicated in a user data frame with values set as follows: The CFN and Subframe Number IE values shall reflect the time when the failure was detected The Number of MAC-es PDUs IE shall be set to zero. As a consequence there are no DDI and N IEs in the header and 4 bits padding is used after Number of MAC-es PDUs IE in order to have the octet aligned structure, and there are no MAC-es PDUs IEs in the payload part of the data frame related to the HARQ failure. The Number of HARQ Retransmissions IE shall be set to the number of HARQ retransmissions that occurred when the failure was detected. The coding shall be the same as for a correctly decoded payload as described in section 5.12.

5.14

TNL Congestion Indication [FDD]

This procedure is used by the SRNC to signal, on a transport bearer carrying an E-DCH MAC-d flow, that a transport network congestion situation on Iub/Iur has been detected.

Node B

SRNC

TNL CONGESTION INDICATION

Figure 9AB: TNL Congestion Indication procedure At the reception of the TNL CONGESTION INDICATION control frame, the Node B should reduce the bit rate on the Iub interface.

3GPP

Release 6T

18

3GPP TS 25.427 V6.8.0 (2006-12)

If the TNL CONGESTION INDICATION control frame is indicating TNL Congestion detected by frame loss, or the TNL CONGESTION INDICATION control frame is indicating TNL Congestion detected by delay build-up, the Node B should reduce the bit rate for at least the MAC-d flow on which the congestion indication control frame was received. If the TNL CONGESTION INDICATION control frame is indicating No TNL Congestion, the Node B can gradually go back to normal operation.

6
6.1

Frame structure and coding

General

The general structure of a DCH FP frame consists of a header and a payload. The structure is depicted in figure 9B.

Header

Payload

Figure 9B: General structure of a frame protocol PDU The header contains a CRC checksum, the frame type field and information related to the frame type. There are two types of DCH FP frames (indicated by the FT IE): [FDD For the UL direction there is also an E-DCH data frame (indicated by signalling) E-DCH data frame.] DCH data frame. DCH control frame.

The payload of the data frames contains radio interface user data, quality information for the transport blocks and for the radio interface physical channel during the transmission time interval (for UL only), and an optional CRC field. The payload of the control frames contains commands and measurement reports related to transport bearer and the radio interface physical channel but not directly related to specific radio interface user data.

6.1.1

General principles for the coding

In the present document the structure of frames will be specified by using pictures similar to figure 10.

3GPP

Release 6T

19

3GPP TS 25.427 V6.8.0 (2006-12)

0 Byte 1 Byte 2

Field 1 Field 3 Field 3 ( cont.)

Field 2 Field 4

Byte 3

Spare Extension

Figure 10: Example of notation used for the definition of the 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 10). In addition, if a field spans several bytes, more significant bits will be located in lower numbered bytes (right of frame in figure 10). On the Iub/Iur 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 coded with the 2's complement notation.

Bits labelled "Spare" shall be set to zero by the transmitter and shall be ignored by the receiver. The Spare Extension IE indicates the location where new IEs can in the future be added in a backward compatible way. The Spare Extension IE shall not be used by the transmitter and shall be ignored by the receiver.

6.2
6.2.1

Data frames
Introduction

The purpose of the user data frames is to transparently transport the transport blocks between Node B and SRNC. The protocol allows for multiplexing of coordinated dedicated transport channels, with the same transmission time interval, onto one transport bearer. The transport blocks of all the coordinated DCHs for one transmission time interval are included in one frame. SRNC indicates the multiplexing of coordinated dedicated transport channels in the appropriate RNSAP/NBAP message.

6.2.2
6.2.2.1

UL DATA FRAME
UL DATA FRAME FOR DCH

The structure of the UL DATA FRAME is shown in figure 11.

3GPP

Release 6T

20

3GPP TS 25.427 V6.8.0 (2006-12)

Header CRC
CFN
Spare

FT

TFI of first DCH

Header

Spare

TFI of last DCH

First TB of first DCH

First TB of first DCH (cont.)

Pad

Last TB of first DCH

Last TB of first DCH (cont.)

Pad

First TB of last DCH Payload First TB of last DCH (cont.) Pad

Last TB of last DCH

Last TB of last DCH (cont.)

Pad

QE
CRCI of first TB of first DCH

CRCI of lastTB of last DCH

Pad

Spare Extension
Payload CRC Optional Payload CRC (cont.)

Figure 11: UL DATA FRAME structure For the description of the fields see subclause 6.2.4. There are as many TFI fields as number of DCH multiplexed in the same transport bearer.

3GPP

Release 6T

21

3GPP TS 25.427 V6.8.0 (2006-12)

The DCHs in the frame structure are ordered from the lower DCH id ('first DCH') to the higher DCH id ('last DCH'). The size and the number of TBs for each DCH are defined by the correspondent TFI. If the TB does not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex: a TB of 21 bits requires 3 bits of padding). There is a CRCI for each TB included in the frame irrespective of the size of the TB, i.e. the CRCI is included also when the TB length is zero. If the CRCIs of one data frame do not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex. 3 CRCI bits require 5 bits of padding, but there are no CRCI bits and no padding, when the number of TBs is zero). The Payload CRC IE is optional, 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).

6.2.2.2

UL DATA FRAME FOR E-DCH [FDD]

The structure of the E-DCH UL DATA FRAME is shown in Figure 11a.

3GPP

Release 6T

22

3GPP TS 25.427 V6.8.0 (2006-12)

0 Header CRC FT Header CRC cont FSN Number of Subframes Spare CFN Spare N of HARQ Retransm 1st Subframe number N of MAC-es PDUs First DDI First DDI cont First N Last DDI Last N cont
Spare N of HARQ Retransm
N of MAC-es PDUs
First DDI cont

Last N Pad
Last Subframe number

Header

First DDI

First N

Last DDI Last N Last N cont Pad Spare First MAC-es PDU of first Subframe Spare Second MAC-es PDU of first Subframe Spare Last MAC-es PDU of first Subframe Spare First MAC-es PDU of last Subframe Spare Second MAC-es PDU of last Subframe Spare Last MAC-es PDU of last Subframe Spare extension Payload CRC Payload CRC cont Optional

Payload

Figure 11a: E-DCH UL DATA FRAME structure For the description of the fields see subclause 6.2.4. When there is an even, including zero, number of DDI + N field pairs for a subframe, then 4 bits padding is used as shown in the figure in order to have the octet aligned structure. 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 UL data frame contains payload.

6.2.3

DL DATA FRAME

The structure of the DL DATA FRAME is shown in figure 12.

3GPP

Release 6T

23

3GPP TS 25.427 V6.8.0 (2006-12)

7 Header CRC CFN

Spare

0 FT

TFI of first DCH

Header

Spare

TFI of last DCH First TB of first DCH

First TB of first DCH ( cont.)

Pad

Last TB of first DCH

Last TB of first DCH (cont.)

Pad

First TB of last DCH

Payload

First TB of last DCH ( cont.)

Pad

Last TB of last DCH

Last TB of last DCH ( cont.) Spare Extension Payload CRC

Pad

Optional Payload CRC (cont.)

Figure 12: DL DATA FRAME structure For the description of the fields see subclause 6.2.4. There are as many TFI fields as number of DCH multiplexed in the same transport bearer. The DCHs in the frame structure are ordered from the lower DCH id ('first DCH') to the higher DCH id ('last DCH'). The size and the number of TBs for each DCH is defined by the correspondent TFI.

3GPP

Release 6T

24

3GPP TS 25.427 V6.8.0 (2006-12)

If the TB does not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex: a TB of 21 bits requires 3 bits of padding). The Payload CRC IE is optional, 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).

6.2.4
6.2.4.1

Coding of information elements in data frames

Header CRC

Description: Result of the CRC applied to the remaining part of the header, i.e. from bit 0 of the first byte (the FT IE) to the bit 0 (included) of the last byte of the header (not including the Header CRC Cont four bits), with one of the corresponding generator polynomials: G(D) = D7+D6+D2+1 for the 7 bit header CRC, G(D) = D11 + D9 + D8 + D2 + D + 1 for the 11 bit header CRC. See subclause 7.2. Field Length: 7 bits. [FDD 11 bits for UL Data Frame for E-DCH.]

6.2.4.2

Frame Type (FT)

Description: Describes if it is a control frame or a data frame. Value range: {0=data, 1=control}. Field Length: 1 bit.

6.2.4.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. See [2]. [FDD - For E-DCH the Connection Frame Number shall indicate the radio frame when the HARQ process correctly decoded the data.] [FDD - For E-DCH apart from reordering purposes, CFN (and Subframe number) can be used for dynamic delay measurements.] Value range: {0-255}. Field length: 8 bits.

6.2.4.4

Transport Format Indicator (TFI)

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 [3]. Value range: {0-31}. Field length: 5 bits.

6.2.4.5

Quality Estimate (QE)

Description: The quality estimate is derived from the transport channel BER [FDD - or physical channel BER.] [FDD - If the DCH FP frame includes TB's for the DCH which was indicated as "selected" with the QE-selector IE in the control plane [4] [6], then the QE is the transport channel BER for the selected DCH. If no transport channel BER is available the QE is the physical channel BER.] [FDD - If the value of the QE-Selector IE equals "non-selected" for all DCHs in the DCH FP frame, then the QE is the physical channel BER.]

3GPP

Release 6T

25

3GPP TS 25.427 V6.8.0 (2006-12)

[TDD - If no transport channel BER is available, then the QE shall be set to 0. This is in particular the case when no transport blocks have been received. The value of QE will be ignored by the RNC in this case.] The quality estimate shall be set to the transport channel BER [FDD - or physical channel BER] and be measured in the units TrCh_BER_LOG [FDD - and PhCh_BER_LOG respectively] (see [7] and [8]). The quality estimate is needed in order to select a transport block when all CRC indications are showing bad (or good) frame. The UL outer loop power control may also use the quality estimate. Value range: {0-255}. Granularity: 1. Field length: 8 bits.

6.2.4.6

Transport Block (TB)

Description: A block of data to be transmitted or received over the air interface. The transport format indicated by the TFI describes the transport block length and transport block set size. See [3]. Field length: The length of the TB is specified by the TFI.

6.2.4.7

CRC indicator (CRCI)

Description: Indicates the correctness/incorrectness of the TB CRC received on the Uu interface. For every transport block included in the data frame a CRCI bit will be present, irrespective of the presence of a TB CRC on the Uu interface. If no CRC was present on the Uu for a certain TB, the corresponding CRCI bit shall be set to "0". Value range: {0=Correct, 1=Not Correct}. Field length: 1 bit.

6.2.4.8

Payload CRC

Description: CRC for the payload. This field is optional. It is the result of the CRC applied to the remaining part of the payload, i.e. from the bit 7 of the first byte of the payload to the bit 0 of the byte of the payload before the Payload CRC IE, with the corresponding generator polynomial: G(D) = D16+D15+D2+1. See clause 7.2. Field length: 16 bits.

6.2.4.9

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.4.10

Subframe Number [FDD]

Description: Indicates the subframe number in which the payload was received. Apart from reordering purposes, Subframe number (and CFN) can be used for dynamic delay measurements. Value range: {0-4} Field length: 3 bits.

6.2.4.11

Number of HARQ Retransmissions, NHR [FDD]

Description: Indicates the number of HARQ retransmissions used for successful decoding of the payload, or in case of HARQ decoding failure the number of HARQ retransmissions that were used at the time when the HARQ decoding failure was detected. The value 15 indicates that the Node B could not calculate the number of HARQ retransmissions. Value range: {0-15}

3GPP

Release 6T

26

3GPP TS 25.427 V6.8.0 (2006-12)

Value {12}: Used for indicating that the number of HARQ retransmissions was 12 or higher. Values {13, 14}: Reserved in this user plane revision. Shall be ignored by the receiver. Value {15}: Used for indicating that the number of HARQ retransmissions is unknown. Field length: 4 bits.

6.2.4.12

Number of Subframes [FDD]

Description: The Number of Subframes field indicates how many subframes that follows in the frame. 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.4.13

Number of MAC-es PDUs [FDD]

Description: Indicates the number of MAC-es 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.4.14

Data Description Indicator, DDI [FDD]

Description: The Data Description Indicator is mapped directly from the DDI field received over the Uu. Field length: 6 bits.

6.2.4.15

Number of MAC-d PDUs, N [FDD]

Description: The Number of MAC-d PDUs is mapped directly from the N field received over the Uu. Field length: 6 bits.

6.2.4.16

FSN Frame Sequence Number [FDD]

Description: The 4-bit Frame Sequence Number is incremented (modulo 16) for each transmitted data frame. Each flow generates its own Frame Sequence. Value range: {0..15}. Granularity: 1. Field length: 4 bits.

6.3
6.3.1

Control frames
Introduction

Control frames are used to transport control information between SRNC and Node B.

3GPP

Release 6T

27

3GPP TS 25.427 V6.8.0 (2006-12)

On the uplink, these frames are not combined all frames are passed transparently from Node B to SRNC. On the downlink, the same control frame is copied and sent transparently to all the Node Bs from the SRNC. The structure of the control frames is shown in the figure 13.
7 Frame CRC Control Frame Type FT Header (2 bytes) 0

Control information

Payload (variable length) Control information (cont.) Spare Extension

Figure 13: General structure of the control frames Control Frame Type IE defines the type of the control frame. The structure of the header and the payload of the control frames is defined in the following subclauses.

6.3.2
6.3.2.1

Header structure of the control frames

Frame CRC

Description: It is the result of the CRC applied to the remaining part of the frame, i.e. from bit 0 of the first byte of the header (the FT IE) to bit 0 of the last byte of the payload, with the corresponding generator polynomial: G(D) = D7+D6+D2+1. See subclause 7.2. Field Length: 7 bits.

6.3.2.2

Frame Type (FT)

Description: Describes if it is a control frame or a data frame. Value range: {0=data, 1=control}. Field Length: 1 bit.

6.3.2.3

Control Frame Type

Description: Indicates the type of the control information (information elements and length) contained in the payload. Value: The values are defined in table 1.

3GPP

Release 6T

28

3GPP TS 25.427 V6.8.0 (2006-12)

Table 1
Control frame type OUTER LOOP POWER CONTROL TIMING ADJUSTMENT DL SYNCHRONISATION UL SYNCHRONISATION Reserved Value DL NODE SYNCHRONISATION UL NODE SYNCHRONISATION RX TIMING DEVIATION RADIO INTERFACE PARAMETER UPDATE TIMING ADVANCE TNL CONGESTION INDICATION Coding 0000 0001 0000 0010 0000 0011 0000 0100 0000 0101 0000 0110 0000 0111 0000 1000 0000 1001

0000 1010 0000 1011

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
6.3.3.1
6.3.3.1.1

Payload structure and information elements

TIMING ADJUSTMENT
Payload structure

Figure 14 shows the structure of the payload when control frame is used for the timing adjustment.

Number of Octets 7 CFN ToA ToA (cont.) 0 1 1 1 0-32 Spare Extension Payload

Figure 14: Structure of the payload for the TIMING ADJUSTMENT control frame

6.3.3.1.2

CFN

Description: The CFN value is extracted from the corresponding DL DATA FRAME. Value range: As defined in subclause 6.2.4.3. Field length: 8 bits.

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 value in the frame).

3GPP

Release 6T

29

3GPP TS 25.427 V6.8.0 (2006-12)

Value range: {-1280, +1279.875 msec}. Granularity: 125 s. Field length: 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
6.3.3.2.1

DL SYNCHRONISATION
Payload structure

Figure 15 shows the structure of the payload when control frame is used for the user plane synchronisation.
Number of Octets 7 CFN Spare Extension 0-32 0 1 Payload

Figure 15: Structure of the payload for the DL SYNCHRONISATION control frame

6.3.3.2.2

CFN

Description: The CFN value is the target CFN and used to calculate ToA. Value range: As defined in subclause 6.2.4.3. Field length: 8 bits.

6.3.3.2.3

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

6.3.3.3
6.3.3.3.1

UL SYNCHRONISATION
Payload structure

Figure 16 shows the structure of the payload when the control frame is used for the user plane synchronisation.

3GPP

Release 6T

30

3GPP TS 25.427 V6.8.0 (2006-12)

Number of Octets 7 CFN ToA ToA (cont.) 0 1 1 1 0-32 Spare Extension Payload

Figure 16: Structure of the UL SYNCHRONISATION control frame

6.3.3.3.2

CFN

Description: The CFN value is extracted from the corresponding DL SYNCHRONISATION control frame. Value range: As defined in subclause 6.2.4.3. Field length: 8 bits.

6.3.3.3.3

Time of Arrival (ToA)

The ToA IE is described in subclause 6.3.3.1.3.

6.3.3.3.4

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

6.3.3.4
6.3.3.4.1

OUTER LOOP POWER CONTROL [FDD, 1.28Mcps TDD]

Payload structure

Figure 17 shows the structure of the payload when control frame is used for the UL outer loop power control.

Number of Octets 7 1 UL_SIR_TARGET Spare Extension 0-32 Payload

Figure 17: Structure of the payload for OUTER LOOP PC control frame

6.3.3.4.2

SIR Target

Description: Value (in dB) of the SIR target to be used by the UL inner loop power control.

3GPP

Release 6T

31

3GPP TS 25.427 V6.8.0 (2006-12)

SIR Target is given in the unit UL_SIR_TARGET where: UL_SIR_TARGET = 000 UL_SIR_TARGET = 001 UL_SIR_TARGET = 002 ... UL_SIR_TARGET = 254 UL_SIR_TARGET = 255 SIR Target = -8.2 dB SIR Target = -8.1 dB SIR Target = -8.0 dB SIR Target = 17.2 dB SIR Target = 17.3 dB

Value range: {-8.217.3 dB}. Granularity: 0.1 dB. Field length: 8 bits.

6.3.3.4.3

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

6.3.3.5
6.3.3.5.1

DL NODE SYNCHRONISATION
Payload structure

Figure 18 shows the structure of the payload for the DL NODE SYNCHRONISATION control frame.
Number of Octets

7 T1 T1 (cont.) T1 (cont.) Spare Extension

0 1 1 1 0-32 Payload

Figure 18: Structure of the payload for the DL NODE SYNCHRONISATION control frame

6.3.3.5.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: As defined in subclause 6.3.3.6.2. Field length: 24 bits.

6.3.3.5.3

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

3GPP

Release 6T

32

3GPP TS 25.427 V6.8.0 (2006-12)

6.3.3.6
6.3.3.6.1

UL NODE SYNCHRONISATION
Payload structure

The payload of the UL NODE SYNCHRONISATION control frames is shown in figure 19.
Number of Octets 7 T1 T1 (cont.) T1 (cont.) T2 T2 (cont.) T2 (cont.) T3 T3 (cont.) T3 (cont.) Spare Extension 0-32 0 1 1 1 1 1 1 1 1 1 Payload

Figure 19: Structure of the payload for UL NODE SYNCHRONISATION control frame

6.3.3.6.2

T1

Description: T1 timer is extracted from the correspondent DL NODE SYNCHRONISATION control frame. Value range: {0-40959.875 ms}. Granularity: 0.125 ms. Field length: 24 bits.

6.3.3.6.3

T2

Description: Node B specific frame number (BFN) that indicates the time when Node B received the correspondent DL NODE SYNCHRONISATION control frame through the SAP from the transport layer. Value range: {0-40959.875 ms}. Granularity: 0.125 ms. Field length: 24 bits.

3GPP

Release 6T

33

3GPP TS 25.427 V6.8.0 (2006-12)

6.3.3.6.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.125 ms. Field length: 24 bits.

6.3.3.6.5

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

6.3.3.7
6.3.3.7.1

RX TIMING DEVIATION [3.84Mcps TDD]

Payload structure

Figure 20 shows the structure of the payload when the control frame is used for the Rx timing deviation.
Number of Octets 7 CFN
Spare

0 1

Rx Timing Deviation Spare Extension

1 0-32

Payload

Figure 20: Structure of the payload for RX TIMING DEVIATION control frame

6.3.3.7.2

Rx Timing Deviation

Description: Measured Rx Timing deviation as a basis for timing advance. Value range: {-256, ..,+255 chips}. {N x 4 256}chips RxTiming Deviation < {(N+1) x 4 256} chips With N = 0,1, .. , 127 Granularity: 4 chips. Field length: 7 bits.

6.3.3.7.3

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

6.3.3.7.4

CFN

Description: The CFN value in this control frame is the CFN when the RX timing deviation was measured. Value range: As defined in subclause 6.2.4.3. Field length: 8 bits.

3GPP

Release 6T

34

3GPP TS 25.427 V6.8.0 (2006-12)

6.3.3.8
6.3.3.8.1
Void.

DSCH TFCI SIGNALLING [FDD]

Payload structure

6.3.3.8.2
Void.

TFCI (field 2)

6.3.3.8.3
Void.

Spare Extension

6.3.3.8.4
Void.

CFN

6.3.3.9
6.3.3.9.1

RADIO INTERFACE PARAMETER UPDATE [FDD]

Payload structure

The figure 22 shows the structure of the payload when the control frame is used for signalling radio interface parameter updates.

3GPP

Release 6T

35

3GPP TS 25.427 V6.8.0 (2006-12)

Number of Octets 7 Radio Interface Parameter Update Flags 15 14 13 12 11 10 9 7 Radio Interface Parameter Update Flags 6 5 4 3 2 1 CFN 7 6 DPC Mode TPC PO 8 0 0 1 1 1 1 Payload (>=7 bytes) 1 1 1 0-29

Spare

Multiple RL Sets Indicator

Reserved Bits Reserved Bits MAX_UE_TX_POW Spare Extension

Spare

Spare

Figure 22: Structure of the payload for the RADIO INTERFACE PARAMETER UPDATE control frame

6.3.3.9.2

Radio Interface Parameter Update flags

Description: Contains flags indicating which information is valid in this control frame. Value range: Bit 0: Indicates if the 3rd byte of the control frame payload contains a valid CFN (1) or not (0); Bit 1: Indicates if the 4th byte (bits 0-4) of the control frame payload contains a valid TPC PO (1) or not (0); Bit 2: Indicates if the 4th byte (bit 5) of the control frame payload contains a valid DPC mode (1) or not (0); Bit 3: Reserved bit; Bit 4: Reserved bit; Bit 5: Indicates if the 5th byte (bit 7) of the control frame payload contains a valid Multiple RL Sets Indicator (1) or not (0); Bit 6: Indicates if the 7th byte (bits 0-6) of the control frame payload contains a valid Maximum UE TX Power (1) or not (0); Bit 7-15: Set to (0): reserved in this user plane revision. Any indicated flags shall be ignored by the receiver. Reserved bits shall be set to 0 by the SRNC and ignored by the Node B. Field length: 16 bits.

3GPP

Release 6T

36

3GPP TS 25.427 V6.8.0 (2006-12)

6.3.3.9.3

TPC Power Offset (TPC PO)

Description: Power offset to be applied in the DL between the DPDCH information and the TPC bits on the DPCCH as specified in the clause 5.2 of [12]. Value range: {0-7.75 dB}. Granularity: 0.25 dB. Field length: 5 bits.

6.3.3.9.4

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

6.3.3.9.4A

CFN

Description: The CFN value indicates when the presented parameters shall be applied. Value range: As defined in subclause 6.2.4.3. Field length: 8 bits.

6.3.3.9.5

DPC Mode

Description: DPC mode to be applied in the UL. Value range: {0,1}. The DPC mode shall be applied as specified in [12]. Field length: 1 bit.

6.3.3.9.6
Void.

TFCI Power Offset (TFCI PO)

6.3.3.9.7
Void.

TFCI Power Offset for primary cell (TFCI PO_primary)

6.3.3.9.8

Multiple RL Sets Indicator

Description: Multiple RL Sets Indicator indicates whether the UE has several RL Sets or not. Value range: {0=UE has only one RL Set, 1=UE has several RL Sets}. Field length: 1 bit.

6.3.3.9.9

Maximum UE TX Power

Description: The Maximum UE TX Power is the lower of the maximum output power of the UE power class, defined in ref [14], and the Maximum Allowed UL TX Power that is also sent to the UE, see ref [15]. Maximum UE TX Power is given in the unit MAX_UE_TX_POW where:

3GPP

Release 6T

37

3GPP TS 25.427 V6.8.0 (2006-12)

MAX_UE_TX_POW = 00 MAX_UE_TX_POW = 01 MAX_UE_TX_POW = 02 ... MAX_UE_TX_POW = 87 MAX_UE_TX_POW = 88 Value range: {-55..33 dBm}. Granularity: 1 dBm Field length: 7 bit

Maximum UE TX Power = -55 dBm Maximum UE TX Power = -54 dBm Maximum UE TX Power = -53 dBm Maximum UE TX Power = 32 dBm Maximum UE TX Power = 33 dBm

6.3.3.10
6.3.3.10.1

TIMING ADVANCE [3.84Mcps TDD]

Payload structure

Figure 23 shows the structure of the payload when the control frame is used for timing advance.
Number of Octets 7 CFN Spare TA Spare Extension 0 1 1 0-32 Payload

Figure 23: Structure of the TIMING ADVANCE control frame

6.3.3.10.2

CFN

Description: The CFN value in this control frame is the frame that the timing advance will occur. Value range: As defined in subclause 6.2.4.3. Field length: 8 bits.

6.3.3.10.3

TA

Description: UE applied UL timing advance adjustment. Value range: {0-252 chips}. Granularity: 4 chips. Field length: 6 bits.

6.3.3.10.4

Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

6.3.3.11

TNL CONGESTION INDICATION [FDD]

6.3.3.11.1 Payload structure

Figure 24 shows the structure of the payload when the control frame is used for TNL CONGESTION INDICATION.

3GPP

Release 6T

38

3GPP TS 25.427 V6.8.0 (2006-12)

Number of Octets 7 Spare Spare Extension 0 Congestion Status

1 Payload 0 - 32

Figure 24: Structure of the TNL CONGESTION INDICATION control frame

6.3.3.11.2 Congestion Status

Description: The Congestion Status indicates whether there is transport network congestion or not. 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.3 Spare Extension

The Spare Extension IE is described in subclause 6.3.3.1.4.

7
7.1

Handling of Unknown, Unforeseen and Erroneous Protocol Data

General

A frame protocol frame with illegal or not comprehended parameter value shall be ignored. Frame protocol frames sent with a CFN in which the radio resources assigned to the associated Iub data port are not available, shall be ignored. Frame protocol data frames with CFN value that does not fulfil the requirement set in clause [FDD - 4.2.14 of [9]] [TDD - 4.2.12 of [10]], shall be ignored.

7.2

Error detection

Error detection is provided on frames through a Cyclic Redundancy Check. The length of the CRC for the payload is 16 bits, for the data frame header 7 or 11 bits and for control frames it is 7 bits.

7.2.1

CRC Calculation

The parity bits are generated by one of the following cyclic generator polynomials: gCRC16(D) = D16 + D15 + D2 + 1

3GPP

Release 6T

39

3GPP TS 25.427 V6.8.0 (2006-12)

gCRC11(D) = D11 + D9 + D8 + D2 + D + 1 gCRC7(D) = D + D6 + D2 + 1 Denote the bits in a frame by a1 , a 2 , a 3 , K , a Ai , and the parity bits by p1 , p 2 , p3 , K , p Li . Ai is the length of a protected data and Li is 16, 11 or 7 depending on the CRC length. The encoding is performed in a systematic form, which means that in GF(2), the polynomial for the payload
7

a1 D Ai +15 + a2 D Ai +14 + K + a Ai D16 + p1 D15 + p2 D14 + K + p15 D1 + p16

yields a remainder equal to 0 when divided by gCRC16(D), the polynomial for the data frame header with 11 bit CRC

a1 D Ai +11 + a2 D Ai +10 + K + a Ai D11 + p1 D10 + p2 D 9 + K + p10 D1 + p11

yields a reminder equal to 0 when divided by gCRC11(D) and the polynomial for the data frame header with 7 bit CRC and control frame

a1 D Ai +6 + a2 D Ai +5 + K + a Ai D 7 + p1 D 6 + p2 D 5 + K + p6 D1 + p7
yields a remainder equal to 0 when divided by gCRC7(D). If Ai = 0 , p1 = p2 = p3 = L = p Li = 0 .

7.2.1.1

Relation between input and output of the Cyclic Redundancy Check

B

The bits after CRC attachment are denoted by b1 , b2 , b3 , K , bBi , where Bi=Ai+Li. The parity bits for the payload are attached at the end of the frame:

bk = a k

k = 1, 2, 3, , Ai

bk = p ( k Ai ) k = Ai + 1, Ai + 2, Ai + 3, , Ai + LI
The parity bits for the frame header and the control frames are attached at the beginning of the frame:

bk = pk

k = 1, 2, 3, , Li k = Li + 1, Li + 2, Li + 3, , LI + Ai

bk = a ( k Li )

3GPP

Release 6T

40

3GPP TS 25.427 V6.8.0 (2006-12)

Annex A (informative): Change history

TSG RAN# RAN_05 RAN_06 RAN_06 RAN_06 RAN_07 RAN_08 RAN_09 Version 3.0.0 3.0.0 3.0.0 3.1.0 3.2.0 3.3.0 CR 005 026 028 029 031 032 033 034 035 036 037 038 039 040 043 Tdoc RAN RP-99758 RP-99759 RP-99760 RP-000248 RP-000384 Change history New Subject/Comment Version 3.0.0 Approved at TSG RAN #5 and placed under Change Control 3.1.0 Approved at TSG RAN #6 3.1.0 Approved at TSG RAN #6 3.1.0 Approved at TSG RAN #6 3.2.0 Approved at TSG RAN #7 3.3.0 Approved at TSG RAN #8 3.4.0 Approved at TSG RAN #9

RAN_10

3.4.0

RP-000625

3.5.0

Approved at TSG RAN #10

RAN_11

3.5.0

RP-010122

3.6.0

Approved at TSG RAN #11

Change history
Date March 01 March 01 06/2001 06/2001 09/2001 09/2001 09/2001 09/2001 09/2001 12/2001 12/2001 12/2001 12/2001 03/2002 12/2002 09/2003 12/2003 12/2003 12/2003 12/2004 03/2005 03/2005 06/2005 06/2005 06/2005 06/2005 06/2005 06/2005 TSG # 11 11 12 12 13 13 13 13 13 14 14 14 14 15 18 21 22 22 22 26 27 27 28 28 28 28 28 28 TSG Doc. RP-010160 RP-010164 RP-010381 RP-010395 RP-010586 RP-010586 RP-010598 RP-010598 RP-010598 RP-010860 CR Rev Subject/Comment 045 Approved at TSG RAN #11 and placed under Change Control 042 Approved at TSG RAN #11 and placed under Change Control 050, Approved at TSG RAN #12 054 047 Approved at TSG RAN #12 056 Transport bearer replacement clarification 063 1 General Corrections on Iub_Iur UP protocol for DCH data streams 057 Uplink power control for LCR TDD 060 1 DPC Mode Correction in the User Plane 061 25.427 Correction 067 Correction to inconsistencies in TS 25.427 1 Clarifications on data/control frame support Specification Notations 2 1 1 1 1 2 1 Terminology Correction Rel4 DCH FP changes for TFCI power control in DSCH hard split mode Correction for the DL DPDCH transmission Coordination with RRC about the TFS of DL DCH for HS-DSCH Signalling support for soft handover indicator Spare Extension in Data frame Introduction of Release 6 specification Changes on 25.427 due to the introduction of Enhanced Uplink Reference for QE mapping is incorrect EDCH Frame format update Correction to the range of TDD parameter in RX TIMING DEVIATION [3.84Mcps TDD] FRAME Support for HARQ Retransmission and Failure Indication Clarification of the use of CFN for Enhanced Uplink Removing the abbreviation SFN for Subframe Number Feature clean-up: Removal of DSCH (FDD mode) Transport Network CongestionDetection and Control Old 4.0.0 4.0.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.2.0 4.2.0 4.2.0 4.2.0 4.3.0 5.0.0 5.1.0 5.2.0 5.2.0 5.3.0 6.0.0 6.1.0 6.1.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 New 4.0.0 4.0.0 4.1.0 4.1.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.3.0 4.3.0 4.3.0 4.3.0 5.0.0 5.1.0 5.2.0 5.3.0 5.3.0 6.0.0 6.1.0 6.2.0 6.2.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0

RP-010860 069 RP-010860 071 RP-010860 077 RP-020194 RP-020744 RP-030447 RP-030678 RP-030682 RP-040440 RP-050054 RP-050137 RP-050234 RP-050229 RP-050229 RP-050229 RP-050222 RP-050229 082 088 089 090 093 095 097 102 103 104 105 106 108 109

1 1

3GPP

Release 6T

41

3GPP TS 25.427 V6.8.0 (2006-12)

Change history
Date 09/2005 09/2005 09/2005 12/2005 12/2005 03/2006 03/2006 06/2006 12/2006 12/2006 TSG # 29 29 29 30 30 31 31 32 34 34 TSG Doc. CR RP-050434 110 RP-050434 115 RP-050434 RP-050702 RP-050702 RP-060066 RP-060066 RP-060284 RP-060699 118 120 121 125 126 128 136 Rev Subject/Comment 1 CRC-11 Polynomial for E-DCH 1 Value range missing for Number of Subframes and Number of Maces PDUs fields 3 Maximum UE Tx Power for EDCH 1 Conditions for sending HARQ Failure 1 HARQ failure shall be sent on highest bearer 1 HARQ Failure Indication due to MAC-e Reset in UE 2 Clarification for HARQ Failure Indication 1 Missing new frame protocol services in list of services in clause 4.1 1 No Payload CRC if no Payload TNL congestion indication signal not applicable for DCH Old 6.3.0 6.3.0 6.3.0 6.4.0 6.4.0 6.5.0 6.5.0 6.6.0 6.7.0 6.7.0 New 6.4.0 6.4.0 6.4.0 6.5.0 6.5.0 6.6.0 6.6.0 6.7.0 6.8.0 6.8.0

RP-060702 138

3GPP