3GPP TS 25.224: 3rd Generation Partnership Project Technical Specification Group Radio Access Network (Release 8)

3rd Generation Partnership Project;
3GPP TS 25.224
Technical Specification Group Radio Access
V8.0.0 Network;
(2008-03)
Physical layer procedures (TDD)
Technical Specification
(Release 8)
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 Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational 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 Organisational Partners' Publications Offices.
3GPP
3GPP
Release 8 3 3GPP TS 25.224 V8.0.0 (2008-03)
Keywords
UMTS, radio, layer 1
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.
© 2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.
3GPP
Release 8 4 3GPP TS 25.224 V8.0.0 (2008-03)
Contents
Foreword.....................................................................................................................................................7
1 Scope.................................................................................................................................................8
2 References.........................................................................................................................................8
3 Abbreviations....................................................................................................................................9
4 Physical layer procedures for the 3.84 Mcps option.......................................................................10
4.1 General......................................................................................................................................................10
4.2 Transmitter Power Control........................................................................................................................10
4.2.1 General Parameters..............................................................................................................................10
4.2.2 Uplink Control.....................................................................................................................................10
4.2.2.1 General Limits...............................................................................................................................10
4.2.2.2 PRACH..........................................................................................................................................11
4.2.2.3 DPCH, PUSCH and HS-SICH.......................................................................................................11
4.2.2.3.1 Gain Factors.............................................................................................................................11
4.2.2.3.2 Out of synchronisation handling..............................................................................................12
4.2.2.4 E-PUCH.........................................................................................................................................12
4.2.2.4.1 Gain Factors for E-PUCH........................................................................................................13
4.2.2.5 E-RUCCH......................................................................................................................................14
4.2.3 Downlink Control................................................................................................................................14
4.2.3.1 P-CCPCH.......................................................................................................................................14
4.2.3.2 S-CCPCH, PICH............................................................................................................................14
4.2.3.2A MICH.............................................................................................................................................14
4.2.3.3 SCH................................................................................................................................................15
4.2.3.3A PNBSCH........................................................................................................................................15
4.2.3.4 DPCH, PDSCH..............................................................................................................................15
4.2.3.5 HS-PDSCH....................................................................................................................................16
4.2.3.6 HS-SCCH.......................................................................................................................................16
4.2.3.7 E-AGCH........................................................................................................................................16
4.2.3.8 E-HICH..........................................................................................................................................16
4.3 Timing Advance........................................................................................................................................16
4.4 Synchronisation procedures......................................................................................................................17
4.4.1 Cell Search...........................................................................................................................................17
4.4.2 Dedicated channel synchronisation.....................................................................................................17
4.4.2.1 Synchronisation primitives............................................................................................................17
4.4.2.1.1 General.....................................................................................................................................17
4.4.2.1.2 Downlink synchronisation primitives......................................................................................17
4.4.2.1.2a Downlink synchronisation primitives for HS-channels...........................................................18
4.4.2.1.3 Uplink synchronisation primitives...........................................................................................18
4.4.2.2 Radio link monitoring....................................................................................................................19
4.4.2.2.1 Downlink radio link failure......................................................................................................19
4.4.2.2.2 Uplink radio link failure/restore...............................................................................................19
4.5 Discontinuous transmission (DTX) procedure..........................................................................................19
4.5.0 Description of Special Bursts..............................................................................................................19
4.5.1 Use of Special Bursts during DTX......................................................................................................20
4.5.2 Use of Special Bursts for Initial Establishment / Reconfiguration......................................................20
4.5.3 Use of Special Bursts for DTX on Beacon Channels..........................................................................20
4.6 Downlink Transmit Diversity...................................................................................................................20
4.6.1 Transmit Diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH...............................20
4.6.2 Transmit Diversity for SCH and S-CCPCH........................................................................................21
4.6.2.1 SCH Transmission Scheme...........................................................................................................21
4.6.2.2 S-CCPCH Transmission Scheme...................................................................................................22
4.6.3 Transmit Diversity for Beacon Channels............................................................................................22
4.6.3.1 SCTD Transmission Scheme.........................................................................................................22
4.7 Random access procedure.........................................................................................................................23
3GPP
Release 8 5 3GPP TS 25.224 V8.0.0 (2008-03)
4.7.1 Physical random access procedure......................................................................................................23

4.7a E-RUCCH transmission procedure...........................................................................................................24
4.8 DSCH procedure.......................................................................................................................................24
4.8.1 DSCH procedure with TFCI indication...............................................................................................24
4.8.2 DSCH procedure with midamble indication.......................................................................................25
4.9 Node B Synchronisation Procedure over the Air......................................................................................25
4.9.1 Frequency Acquisition Phase..............................................................................................................25
4.9.2 Initial Synchronisation.........................................................................................................................25
4.9.3 Steady-State Phase...............................................................................................................................25
4.9.4 Late entrant cells..................................................................................................................................25
4.10 Idle periods for IPDL location method.....................................................................................................26
4.10.1 General................................................................................................................................................26
4.10.2 Parameters of IPDL.............................................................................................................................26
4.10.3 Calculation of idle period position......................................................................................................26
4.11 HS-DSCH Procedure................................................................................................................................27
4.11.1 Link Adaptation Procedure..................................................................................................................27
4.11.2 HS-DSCH Channel Quality Indication Procedure..............................................................................28
4.12 Macro-diversity procedure........................................................................................................................29
4.13 E-DCH related procedures........................................................................................................................29
4.13.1 ACK/NACK detection.........................................................................................................................29
4.13.2 Serving and neighbour cell pathloss metric derivation.......................................................................29
4.13.3 Channelisation code hopping procedure for E-PUCH........................................................................30
5.1.1 Uplink Control.....................................................................................................................................33
5.1.1.1 General limits.................................................................................................................................33
5.1.1.2 UpPCH...........................................................................................................................................33
5.1.1.3 PRACH..........................................................................................................................................33
5.1.1.4 DPCH and PUSCH........................................................................................................................33
5.1.1.4.1 Gain Factors.............................................................................................................................34
5.1.1.4.2 Out of synchronization handling..............................................................................................34
5.1.1.5 HS-SICH........................................................................................................................................34
5.1.1.6 E-PUCH.........................................................................................................................................34
5.1.1.6.1 Gain Factors for E-PUCH........................................................................................................35
5.1.1.7 E-RUCCH......................................................................................................................................36
5.1.2 Downlink Control................................................................................................................................36
5.1.2.1 P-CCPCH.......................................................................................................................................36
5.1.2.2 The power of the FPACH..............................................................................................................37
5.1.2.3 S-CCPCH, PICH............................................................................................................................37
5.1.2.3A MICH.............................................................................................................................................37
5.1.2.4 DPCH, PDSCH..............................................................................................................................37
5.1.2.5 HS-PDSCH....................................................................................................................................37
5.1.2.6 HS-SCCH.......................................................................................................................................37
5.1.2.7 PLCCH...........................................................................................................................................38
5.1.2.8 E-AGCH........................................................................................................................................38
5.1.2.9 E-HICH..........................................................................................................................................38
5.2 UL Synchronisation..................................................................................................................................38
5.2.1 General Description.............................................................................................................................38
5.2.1.1 Preparation of uplink synchronization (downlink synchronization)..............................................38
5.2.1.2 Establishment of uplink synchronization.......................................................................................38
5.2.1.3 Maintenance of uplink synchronisation.........................................................................................39
5.2.2 UpPCH................................................................................................................................................39
5.2.3 PRACH................................................................................................................................................39
5.2.4 DPCH and PUSCH..............................................................................................................................39
5.2.4.1 Out of synchronization handling....................................................................................................40
5.2.5 HS-SICH..............................................................................................................................................40
5.2.6 E-PUCH...............................................................................................................................................40
5.2.7 E-RUCCH............................................................................................................................................40
5.3.1 Cell search...........................................................................................................................................41
3GPP
Release 8 6 3GPP TS 25.224 V8.0.0 (2008-03)
5.3.2 DCH synchronization..........................................................................................................................41

5.4.1 Description of Special Bursts..............................................................................................................41
5.4.2 Use of Special Bursts during DTX......................................................................................................41
5.4.3 Use of Special Bursts for Initial Establishment / Reconfiguration......................................................42
5.5.1.1 TSTD for PDSCH and DPCH.......................................................................................................42
5.5.1.2 Closed Loop Tx Diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH..............43
5.5.2 Transmit Diversity for DwPCH...........................................................................................................44
5.5.3 Transmit Diversity for P-CCPCH.......................................................................................................44
5.5.3.1 TSTD Transmission Scheme for P-CCPCH..................................................................................44
5.5.4 SCTD Transmission Scheme for Beacon Channels............................................................................44
5.6 Random Access Procedure........................................................................................................................45
5.6.1 Definitions...........................................................................................................................................45
5.6.1A UpPCH sub-channel............................................................................................................................46
5.6.2 Preparation of random access..............................................................................................................46
5.6.3 Random access procedure...................................................................................................................47
5.6.3.1 The use and generation of the information fields transmitted in the FPACH...............................48
5.6.3.1.1 Signature Reference Number...................................................................................................48
5.6.3.1.2 Relative Sub-Frame Number....................................................................................................49
5.6.3.1.3 Received starting position of the UpPCH (UpPCHPOS)..........................................................49
5.6.3.1.4 Transmit Power Level Command for the RACH message......................................................49
5.6.3a E-RUCCH procedure...........................................................................................................................49
5.6.4 Random access collision......................................................................................................................50
5.7 Node B Synchronisation Procedure over the Air......................................................................................50
5.7.1 Initial Synchronisation.........................................................................................................................50
5.7.2 Steady-State Phase...............................................................................................................................50
5.7.3 Late entrant cells..................................................................................................................................51
5.8.1 General................................................................................................................................................51
5.8.2 Parameters of IPDL.............................................................................................................................51
5.8.3 Calculation of idle period position......................................................................................................51
5.9.3 HS-SCCH monitoring procedure........................................................................................................53
5.11 E-DCH Procedure.....................................................................................................................................54
6.2 Timing Advance........................................................................................................................................55
6.5.2 Transmit Diversity for SCH and S-CCPCH........................................................................................56
6.5.3 Transmit Diversity for Beacon Channels............................................................................................56
6.5.3.1 SCTD Transmission Scheme.........................................................................................................56
6.6 Random access procedure.........................................................................................................................57
6.6.1 Physical random access procedure......................................................................................................57
6.6a E-RUCCH transmission procedure...........................................................................................................57
6.7 DSCH procedure.......................................................................................................................................57
6.11 E-DCH related procedures........................................................................................................................58
3GPP
Release 8 7 3GPP TS 25.224 V8.0.0 (2008-03)

6.11.3 Channelisation code hopping procedure for E-PUCH........................................................................59
Annex A (informative): Power Control.........................................................................................61

A.1 Example Implementation of Downlink Power Control in the UE..................................................61
A.2 Example Implementation of Closed Loop Uplink Power Control in Node B for 1.28Mcps TDD 61
A.3 Example Implementation of Downlink Power Control in UE for 1.28Mcps TDD when TSTD is
used.................................................................................................................................................61
A.4 Example Implementation of open Loop Power Control for access procedure for 1.28Mcps TDD62
A.5 Example Implementation of Closed Loop Uplink HS-SICH Power Control in Node B for
1.28Mcps TDD................................................................................................................................62
Annex B (informative): Determination of Weight Information.................................................63
B.1 STD Weights...................................................................................................................................63
B.2 TxAA Weights................................................................................................................................63
Annex C (informative): Cell search procedure for 3.84Mcps TDD............................................64
Annex CA (informative): Cell search procedure for 1.28Mcps TDD............................................65
Annex CB (informative): Examples random access procedure for 1.28Mcps TDD....................67
Annex D (informative): Change history..........................................................................................69
3GPP
Release 8 8 3GPP TS 25.224 V8.0.0 (2008-03)
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 8 9 3GPP TS 25.224 V8.0.0 (2008-03)
1 Scope
The present document describes the Physical Layer Procedures in the TDD mode of UTRA.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
 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] 3GPP TS 25.201: "Physical layer - general description".
[2] 3GPP TS 25.102: "UE physical layer capabilities".
[3] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels
(FDD)".
[4] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)".
[5] 3GPP TS 25.213: "Spreading and modulation (FDD)".
[6] 3GPP TS 25.214: "Physical layer procedures (FDD)".
[7] 3GPP TS 25.215: "Physical Layer - Measurements (FDD)".
[8] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels
(TDD)".
[9] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)".
[10] 3GPP TS 25.223: "Spreading and modulation (TDD)".
[11] 3GPP TS 25.225: "Physical Layer - Measurements (TDD)".
[12] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
[13] 3GPP TS 25.302: "Services Provided by the Physical Layer".
[14] 3GPP TS 25.401: "UTRAN Overall Description".
[15] 3GPP TS 25.331: "RRC Protocol Specification"
[16] 3GPP TS 25.433: "UTRAN Iub Interface NBAP Signalling"
[17] 3GPP TS 25.105: "UTRA (BS) TDD; Radio transmission and Reception"
[18] 3GPP TS 25.321: "MAC protocol specification"
[19] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode"
[20] 3GPP TS 25.402: "Synchronisation in UTRAN Stage 2"
3GPP
Release 8 10 3GPP TS 25.224 V8.0.0 (2008-03)
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK Acknowledgement
ASC Access Service Class
BCCH Broadcast Control Channel
BCH Broadcast Channel
CCTrCH Coded Composite Transport Channel
CDMA Code Division Multiple Access
CQI Channel Quality Information
CRC Cyclic Redundancy Check
DCA Dynamic Channel Allocation
DL Downlink
DPCH Dedicated Physical Channel
DTX Discontinuous Transmission
E-AGCH E-DCH Absolute Grant Channel
ECSN E-AGCH Cyclic Sequence Number
E-DCH Enhanced Dedicated Channel
E-HICH E-DCH Hybrid ARQ Indicator Channel
ENI E-UCCH Number Indicator
E-PUCH E-DCH Physical Uplink Channel
E-RUCCH E-DCH Random Access Uplink Control Channel
E-UCCH E-DCH Uplink Control Channel
FACH Forward Access Channel
FDD Frequency Division Duplex
HS-DSCH High Speed Downlink Shared Channel
HS-PDSCH High Speed Physical Downlink Shared Channel
HS-SCCH Shared Control Channel for HS-DSCH
HS-SICH Shared Information Channel for HS-DSCH
ISCP Interference Signal Code Power
MAC Medium Access Control
MBMS Multimedia Broadcast/Multicast Service
MBSFN MBMS over a Single Frequency Network
MICH MBMS Indicator Channel
MS burst MBSFN Special burst
MT burst MBSFN Traffic burst
NACK Negative Acknowledgement
NRT Non-Real Time
P-CCPCH Primary Common Control Physical Channel
PC Power Control
PDSCH Physical Downlink Shared Channel
PICH Paging Indicator Channel
PLCCH Physical Layer Common Control Channel
PRACH Physical Random Access Channel
PUSCH Physical Uplink Shared Channel
RACH Random Access Channel
RL Radio Link
RRC Radio Resource Control
RSCP Received Signal Code Power
RT Real Time
RU Resource Unit
SBGP Special Burst Generation Gap
SBP Special Burst Period
SBSP Special Burst Scheduling Period
S-CCPCH Secondary Common Control Physical Channel
SCH Synchronisation Channel
SCTD Space Code Transmit Diversity
SFN System Frame Number
SIR Signal–to-Interference Ratio
SNPL Serving and Neighbour cell Pathloss
3GPP
Release 8 11 3GPP TS 25.224 V8.0.0 (2008-03)
SSCH Secondary Synchronisation Channel

STD Selective Transmit Diversity
TA Timing Advance
TDD Time Division Duplex
TF Transport Format
TFC Transport Format Combination
TFCI Transport Format Combination Indicator
TFCS Transport Format Combination Set
TFRI Transport Format Resource Indicator
TPC Transmit Power Control
TSTD Time Switched Transmit Diversity
TTI Transmission Time Interval
TxAA Transmit Adaptive Antennas
UE User Equipment
UL Uplink
UMTS Universal Mobile Telecommunications System
UTRAN UMTS Radio Access Network
VBR Variable Bit Rate
4 Physical layer procedures for the 3.84 Mcps option
4.1 General
4.2 Transmitter Power Control

4.2.1 General Parameters
Power control is applied for the TDD mode to limit the interference level within the system thus reducing the intercell
interference level and to reduce the power consumption in the UE.
All codes within one timeslot allocated to the same CCTrCH use the same transmission power, in case they have the
same spreading factor.
Table 1: Transmit Power Control characteristics
Uplink Downlink
Power control rate Variable Variable, with rate depending on
1-7 slots delay (2 slot SCH) the slot allocation.
1-14 slots delay (1 slot SCH)
TPC Step size -- 1dB or 2 dB or 3 dB
Remarks All figures are without processing and
measurement times
4.2.2 Uplink Control
4.2.2.1 General Limits

During the operation of the uplink power control procedure the UE transmit power shall not exceed a maximum
allowed value which is the lower out of the maximum output power of the terminal power class and a value which may
be set by higher layer signalling.
Uplink power control shall be performed while the total UE transmit power is below the maximum allowed output
power. In some cases the total UE transmit power in a timeslot after uplink power control calculation might exceed the
maximum allowed output power. In these cases the calculated transmit power of all uplink physical channels in this
timeslot shall be scaled by the same amount in dB before transmission. The total UE transmission power used shall be
the maximum allowed output power.
3GPP
Release 8 12 3GPP TS 25.224 V8.0.0 (2008-03)
The UTRAN may not expect the UE to be capable of reducing its total transmit power below the minimum level
specified in [2].
4.2.2.2 PRACH
The transmit power for the PRACH is set by higher layers based on open loop power control as described in [15].
4.2.2.3 DPCH, PUSCH and HS-SICH

The transmit power for DPCH, PUSCH and HS-SICH is set by higher layers based on open loop power control as
described in [15].
In the case that an ACK is being transmitted on the HS-SICH, the UE shall apply a power offset to the transmit power
of the entire HS-SICH. This power offset shall be signalled by higher layers.
4.2.2.3.1 Gain Factors

Two or more transport channels may be multiplexed onto a CCTrCH as described in [9]. These transport channels
undergo rate matching which involves repetition or puncturing. This rate matching affects the transmit power required
to obtain a particular Eb/N0. Thus, the transmission power of the CCTrCH shall be weighted by a gain factor .
There are two ways of controlling the gain factors for different TFC’s within a CCTrCH transmitted in a radio frame:
-  is signalled for the TFC, or
-  is computed for the TFC, based upon the signalled settings for a reference TFC.
Combinations of the two above methods may be used to associate  values to all TFC’s in the TFCS for a CCTrCH.
The two methods are described in sections 4.2.2.3.1.1 and 4.2.2.3.1.2 respectively. Several reference TFC’s for several
different CCTrCH’s may be signalled from higher layers.
The weight and gain factors may vary on a radio frame basis depending upon the current SF and TFC used. The setting
of weight and gain factors is independent of any other form of power control. That means that the transmit power P UL is
calculated according to the formula given in [15] and then the weight and gain factors are applied on top of that, cf.
[10].
4.2.2.3.1.1 Signalled Gain Factors
When the gain factor j is signalled by higher layers for a certain TFC, the signalled values are used directly for
weighting DPCH or PUSCH within a CCTrCH. Exact values are given in [10].
4.2.2.3.1.2 Computed Gain Factors
The gain factorj may also be computed for certain TFCs, based on the signalled settings for a reference TFC:
Let ref denote the signalled gain factor for the reference TFC. Further, let j denote the gain factor used for the j-th
TFC.
Define the variable: K ref   RM

i
i N i
where RMi is the semi-static rate matching attribute for transport channel i, Ni is the number of bits output from the
radio frame segmentation block for transport channel i and the sum is taken over all the transport channels i in the
reference TFC.
Similarly, define the variable K j  RM i N i

i
where the sum is taken over all the transport channels i in the j-th TFC.
1
Moreover, define the variable Lref 
i SFi
3GPP
Release 8 13 3GPP TS 25.224 V8.0.0 (2008-03)
where SFi is the spreading factor of DPCH or PUSCH i and the sum is taken over all DPCH or PUSCH i used in the
reference TFC.
1
Similarly, define the variable L j 
i SFi
where the sum is taken over all DPCH or PUSCH i used in the j-th TFC.
The gain factors j for the j-th TFC are then computed as follows:
No quantisation of j is performed and as such, values other than the quantised j given in [10] may be used.
4.2.2.3.2 Out of synchronisation handling

As stated in 4.2.3.4 , the association between TPC commands sent on uplink DPCH and PUSCH, with the power
controlled downlink DPCH and PDSCH is signaled by higher layers. In the case of multiple DL CCTrCHs it is possible
that an UL CCTrCH will provide TPC commands to more than one DL CCTrCH.
In the second phase of synchronisation evaluation, as defined in 4.4.2.1.2, the UE shall shut off the transmission of an
UL CCTrCH if the following criteria are fulfilled for any one of the DL CCTrCHs commanded by its TPC:
- The UE estimates the received dedicated channel burst quality over the last 160 ms period to be worse than a
threshold Qout, and in addition, no special burst, as defined in 4.5, is detected with quality above a threshold,
Qsbout. Qout and Qsbout are defined implicitly by the relevant tests in [2]. If the UE detects the beacon channel
reception level [10 dB] above the handover triggering level, then the UE shall use a 320 ms estimation period for
the burst quality evaluation and for the Special Burst detection window.
UE shall subsequently resume the uplink transmission of the CCTrCH if the following criteria are fulfilled:
- The UE estimates the received dedicated CCTrCH burst reception quality over the last 160 ms period to be better
than a threshold Qin or the UE detects a burst with quality above threshold Qsbin and TFCI decoded to be that of
the Special Burst. Qin and Qsbin are defined implicitly by the relevant tests in [2]. If the UE detects the beacon
channel reception level [10 dB] above the handover triggering level, then the UE shall use a 320 ms estimation
period for the burst quality evaluation and for the Special Burst detection window.
4.2.2.4 E-PUCH
The power of E-PUCH is set based upon the sum of:
1. An open loop component based upon beacon channel pathloss and on the E-PUCH constant value signalled by
higher layers (KE-PUCH).
2. A closed-loop TPC component. One TPC bit is signalled to the UE within each E-AGCH. The TPC command
is derived by Node-B.
3. An adjustment factor (e) accounting for the E-TFC selected by the UE and the HARQ offset.
The transmit power of the E-PUCH is calculated in the UE as follows:
… where:
 Pe-base is a closed-loop quantity maintained by the UE and which is incremented or decremented by a value Δ e-
base upon each receipt of a TPC command on E-AGCH. On receipt of a TPC “up” command, P e-base is
incremented by Δe-base. On receipt of a TPC “down” command, Pe-base is decremented by Δe-base. The TPC step
size Δe-base is configured by higher layers [15].
3GPP
Release 8 14 3GPP TS 25.224 V8.0.0 (2008-03)
 L is a pathloss term derived by higher layers from beacon function physical channel measurements. It may
comprise a weighted sum of the instantaneous (LPCCPCH) and filtered (L0) pathloss measurements (as described
in [15])
 e is the gain factor derived for the selected E-TFC transport block size, E-PUCH physical resource size, E-
PUCH modulation type and HARQ offset according to subclause 4.2.2.4.1.
 KE-PUCH is the E-PUCH constant value signalled by higher layers [15].
Higher layers in the UE shall use the current calculated E-PUCH power in conjunction with the current absolute grant
(power) value in order to determine the set of E-TFC’s available (see [18]).
When setting the initial transmit power for E-PUCH or following an extended pause in the reception of TPC commands
on E-AGCH, the UE shall set Pe-base equal to the average of the IBTS values (see [15]) over the timeslots configured for E-
DCH use. When receipt of TPC commands on E-AGCH recommences, the TPC commands shall be used to modify P e-
base from its previously set value.
4.2.2.4.1 Gain Factors for E-PUCH

A beta factor e shall be derived by the UE as a function of:
 the selected E-TFC transport block size
 the E-PUCH resource occupation in the E-DCH TTI
 the modulation type (QPSK/16-QAM)
 the HARQ power offset (see [18])
Higher layers shall provide a set of reference points defining the relationship between the coderate of E-DCH
transmission (e) and the relative reference power per resource unit ( dB). A set of reference points is provided
separately for each of QPSK and 16-QAM modulation.
The coderate of E-DCH transmission e for the selected E-TFC, physical resource allocation and modulation type is
defined as:
… in which Se is the transport block size of the selected E-TFC and Re is the number of physical channel bits output
from the physical channel mapping stage of E-DCH transport channel processing as described in [9].
The maximum and minimum values of  signalled by higher layers for the appropriate modulation type are denoted max
and min respectively. For a given e there exists a 0 and a 1 such that:
 If min≤e<max
o 0 is the largest  signalled by higher layers for the appropriate modulation type and for which ≤e
o 1 is the smallest  signalled by higher layers for the appropriate modulation type and for which
>e
 Else
o If e<min then 0 = min and 1 is the smallest signalled  for which >min.
o If e≥max then 0 is the largest signalled  for which <max and 1 = max
Associated with 0 and 1 are the corresponding 0 and 1 which define the reference points signalled by higher layers.
The normalised (per-resource-unit) beta value for the selected E-TFC and E-PUCH resource set is denoted 0,e and is:
3GPP
Release 8 15 3GPP TS 25.224 V8.0.0 (2008-03)
is a logarithmic value set as a function of the E-PUCH spreading factor (SFE-PUCH) according to table 1a.
Table 1a: Tabulated e values
SFE-PUCH (dB)
1 12
2 9
4 6
8 3
16 0
e is then derived as
Δharq is set by higher layers (see [18]).
4.2.2.5 E-RUCCH
The transmit power for the E-RUCCH is set by higher layers based on open loop power control as described in [15].
4.2.3 Downlink Control
4.2.3.1 P-CCPCH
The Primary CCPCH transmit power is set by higher layer signalling and can be changed based on network conditions
on a slow basis. The reference transmit power of the P-CCPCH is broadcast on BCH or individually signalled to each
UE.
4.2.3.2 S-CCPCH, PICH

The relative transmit power of the Secondary CCPCH and the PICH compared to the P-CCPCH transmit power are set
by higher layer signalling. The PICH power offset relative to the P-CCPCH reference power is signalled on the BCH.
4.2.3.2A MICH
The relative transmit power of the MICH compared to the P-CCPCH transmit power is set by higher layer signalling.
3GPP
Release 8 16 3GPP TS 25.224 V8.0.0 (2008-03)
4.2.3.3 SCH
The SCH transmit power is set by higher layer signalling [16]. The value is given relative to the power of the P-
CCPCH.
4.2.3.3A PNBSCH
The PNBSCH transmit power is set by higher layer signalling [16]. The value given is relative to the power of the P-
CCPCH
4.2.3.4 DPCH, PDSCH

The initial transmission power of the downlink DPCH and the PDSCH shall be set by higher layer signalling. If
associated uplink CCTrCHs for TPC commands are signalled to the UE by higher layers (mandatory for a DPCH), the
network shall transit into inner loop power control after the initial transmission. The UE shall then generate TPC
commands to control the network transmit power and send them in the TPC field of the associated uplink CCTrCHs. If
the physical channel power should be increased, the TPC command is set to “up” whereas if the power should be
reduced the TPC command is set to “down”. An example on how to derive the TPC commands and the definition of the
inner loop power control are given in Annex A.1. A TPC command sent in an uplink CCTrCH controls all downlink
DPCHs or PDSCHs to which the associated downlink CCTrCH is mapped to.
If a PDSCH does not have associated uplink CCTrCHs configured for TPC power control, its power shall be controlled
by higher layer signalling.
In the case that no associated downlink data is scheduled within 15 timeslots before the transmission of a TPC
command then this is regarded as a transmission pause. The TPC commands in this case shall be derived from
measurements on beacon function physical channels. An example solution for the generation of the TPC command for
this case is given in Annex A 1.
When not in a transmission pause each TPC command shall always be based on all associated downlink transmissions
received since the previous related TPC command. Related TPC commands are defined as TPC commands associated
with the same downlink CCTrCHs. If there are no associated downlink transmissions (or equivalently no beacon
transmissions when in a transmission pause) between two or more uplink transmissions carrying related TPC
commands, then these TPC commands shall be identical and they shall be regarded by the UTRAN as a single TPC
command.
UTRAN may decide how to adjust the transmit power in response to the received TPC command.
The UTRAN may apply an individual offset to the transmission power in each timeslot according to the downlink
interference level at the UE.
The transmission power of one DPCH or PDSCH shall not exceed the limits set by higher layer signalling by means of
Maximum_DL_Power (dB) and Minimum_DL_Power (dB). The transmission power is defined as the average power
over one timeslot of the complex QPSK symbols of a single DPCH or PDSCH before spreading relative to the power of
the P-CCPCH.
During a downlink transmission pause, both UE and Node B shall use the same TPC step size which is signalled by
higher layers. The UTRAN may accumulate the TPC commands received during the pause. TPC commands that shall
be regarded as identical may only be counted once. The initial UTRAN transmission power for the first data
transmission after the pause may then be set to the sum of transmission power before the pause and a power offset
according to the accumulated TPC commands. Additionally this sum may include a constant set by the operator and a
correction term due to uncertainties in the reception of the TPC bits. The total downlink transmission power at the Node
B within one timeslot shall not exceed Maximum Transmission Power set by higher layer signalling. If the total
transmit power of all channels in a timeslot exceeds this limit, then the transmission power of all downlink DPCHs and
PDSCHs shall be reduced by the same amount in dB. The value for this power reduction is determined, so that the total
transmit power of all channels in this timeslot is equal to the maximum transmission power.
3GPP
Release 8 17 3GPP TS 25.224 V8.0.0 (2008-03)

When the dedicated physical channel out of sync criteria based on the received burst quality is as given in the
subclause 4.4.2 then the UE shall set the uplink TPC command = "up". The CRC based criteria shall not be taken into
account in TPC bit value setting.
4.2.3.5 HS-PDSCH
The HS-PDSCH power control is under the control of the NodeB.
4.2.3.6 HS-SCCH
Higher layers shall indicate the maximum transmit power of the HS-SCCH. The Node-B shall not exceed this
maximum power when setting the HS-SCCH power.
The initial power of the HS-SCCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may
optionally power control the HS-SCCH. This may be done using TPC commands sent by the UE in the HS-SICH.
The UE shall set the TPC commands in the HS-SICH in order to control the transmit power of the HS-SCCH. The TPC
commands shall be set in order to meet the HS-SCCH target BLER.
The accuracy of the received HS-SCCH BLER estimate made by the UE may be enhanced by a suitable use of the
HCSN field received within the HS-SCCH itself [9]. This field shall initially be set to zero and shall be incremented by
the NodeB each time an HS-SCCH is transmitted to the UE.
4.2.3.7 E-AGCH
Higher layers shall indicate the maximum transmit power of the E-AGCH. The Node-B shall not exceed this maximum
power when setting the E-AGCH power.
The initial power of the E-AGCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may
optionally power control the E-AGCH. This may be done using TPC commands sent by the UE in the E-PUCH.
The UE shall set the TPC commands in the E-PUCH in order to control the transmit power of the E-AGCH. The TPC
commands shall be set in order to meet the E-AGCH target BLER.
The accuracy of the received E-AGCH BLER estimate made by the UE shall be enhanced by a suitable use of the
ECSN field received within the E-AGCH itself [9]. This field shall initially be set to zero and shall be incremented by
the Node-B each time an E-AGCH is transmitted to the UE.
4.2.3.8 E-HICH
The power of the E- HICH is under the control of the Node B.
4.3 Timing Advance

UTRAN may adjust the UE transmission timing with timing advance. The initial value for timing advance (TA phys) will
be determined in the UTRAN by measurement of the timing of the PRACH or E-RUCCH. The required timing advance
will be represented as an 8 bit number (0-255) 'UL Timing Advance' TAul, being the multiplier of 4 chips which is
nearest to the required timing advance (i.e. TAphys = TAul  4 chips).
When Timing Advance is used the UTRAN will continuously measure the timing of a transmission from the UE and
send the necessary timing advance value. On receipt of this value the UE shall adjust the timing of its transmissions
accordingly in steps of ±4chips. The transmission of TA values is done by means of higher layer messages. Upon
receiving the TA command the UE shall adjust its transmission timing according to the timing advance command at the
frame number specified by higher layer signaling. The UE is signaled the TA value in advance of the specified frame
activation time to allow for local processing of the command and application of the TA adjustment on the specified
frame. Node-B is also signaled the TA value and radio frame number that the TA adjustment is expected.to take place.
If TA is enabled by higher layers, after handover the UE shall transmit in the new cell with timing advance TA adjusted
by the relative timing difference t between the new and the old cell:
3GPP
Release 8 18 3GPP TS 25.224 V8.0.0 (2008-03)
TAnew = TAold + 2t.
4.4 Synchronisation procedures

4.4.1 Cell Search
During the cell search, the UE searches for a cell and determines the downlink scrambling code, basic midamble code
and frame synchronisation of that cell. How cell search is typically done is described in Annex C.
For MBSFN FACH, the downlink scrambling codes and basic midamble codes to be used for non-beacon timeslots are
signalled by higher layers.
4.4.2 Dedicated channel synchronisation
4.4.2.1 Synchronisation primitives
4.4.2.1.1 General
For the dedicated channels, synchronisation primitives are used to indicate the synchronisation status of radio links,
both in uplink and downlink. The definition of the primitives is given in the following subclauses.
When operating HS-DSCH, the configuration of a downlink DPCH by UTRAN is optional. Subclause 4.4.2.1.2 relates
to downlink synchronisation in the case that an uplink and downlink DPCH have been configured by higher layers.
Subclause 4.4.2.1.2a relates to downlink synchronisation in the case that only an uplink DPCH has been configured by
higher layers.
4.4.2.1.2 Downlink synchronisation primitives

Layer 1 in the UE shall check the synchronization status of each DL CCTrCH individually in every radio frame All
bursts and transport channels of a CCTrCH shall be taken into account. Synchronisation status is indicated to higher
layers, using the CPHY-Sync-IND or CPHY-Out-of-Sync-IND primitives. For dedicated physical channels configured
with Repetition Periods [15 ] only the configured active periods shall be taken into account in the estimation. The status
check shall also include detection of the Special Bursts defined in 4.5 for DTX.
The criteria for reporting synchronization status are defined in two different phases.
The first phase lasts until 160 ms after the downlink CCTrCH is considered to be established by higher layers. During
this time, Out-of-sync shall not be reported. In-sync shall be reported using the CPHY-Sync-IND primitive if any one of
the following three criteria is fulfilled.
a) The UE estimates the burst reception quality over the previous 40 ms period to be better than a threshold Q in.
This criterion shall be assumed not to be fulfilled before 40 ms of burst reception quality measurement have been
collected.
b) At least one transport block with a CRC attached is received in a TTI ending in the current frame with correct
CRC.
c) The UE detects at least one Special Burst. Special Burst detection shall be successful if the burst is detected with
quality above a threshold, Qsbin, and the TFCI is decoded to be that of the Special Burst.
The second phase starts 160 ms after the downlink dedicated channel is considered established by higher layers..
During this phase both Out-of-Sync and In-Sync are reported as follows.
Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive if all three of the following criteria are
fulfilled:
- the UE estimates the received dedicated channel burst quality over the last 160 ms period to be worse than a
threshold Qout. The value, Qout is defined implicitly by the relevant tests in [2];
3GPP
Release 8 19 3GPP TS 25.224 V8.0.0 (2008-03)
- no Special Burst is detected with quality above a threshold Qsbout within the last 160 ms period. The value Qsbout is
defined implicitly by the relevant tests in [2];
- over the previous 160 ms, no transport block has been received with a correct CRC
If the UE detects the beacon channel reception level [10 dB] above the handover triggering level, the UE shall use 320
ms estimation period for the burst quality evaluation and for the Special Burst and CRC detection window.
In-sync shall be reported using the CPHY-Sync-IND primitive if any of the following criteria is fulfilled:
- the UE estimates the received burst reception quality over the last 160 ms period to be better than a threshold Q in.
The value, Qin is defined implicitly by the relevant tests in [2].
- the UE detects at least one Special Burst with quality above a threshold Qsbin within the last 160 ms period. The
value, Qsbin, is defined implicitly by the relevent tests in [2].
- at least one transport block with a CRC attached is received in a TTI ending in the current frame with correct
CRC.
If the UE detects the beacon channel reception level [10 dB] above the handover triggering level, the UE uses 320 ms
estimation period for the burst quality evaluation and for the Special Burst detection window.
If no data are provided by higher layers for transmission during the second phase on the downlink dedicated channel
then DTX shall be applied as defined in section 4.5.
How the primitives are used by higher layers is described in [15]. The above definitions may lead to radio frames where
neither the In-Sync nor Out-of-Sync primitives are reported.
4.4.2.1.2a Downlink synchronisation primitives for HS-channels

In the case that an uplink DPCH has been configured by higher layers but a downlink DPCH has not been configured,
the UE shall report downlink synchronisation status based upon other downlink physical channels.
The UE shall monitor the received beacon signal level within the cell and shall average the received beacon power over
a period of 160ms. This averaged value is denoted Pb dBm. The UE shall also monitor and average over the same
period, the ISCP on the assigned HS-SCCH resources. This value is denoted IHS-SCCH dBm. A quality value Qhs is
formed as follows:
Qhs = Pb – IHS-SCCH + Dhs-sync
- where Dhs-sync is signalled by higher layers.
In-sync shall be reported using the CPHY-Sync-IND primitive each time an HS-DSCH CRC pass is detected. On this
event, an indicator maintained by the UE termed “HS-DSCH_failure” shall be set to ‘false’. In-sync shall also be
reported if the HS-DSCH_failure indicator is set to ‘false’ and during the last 160ms period, Q hs > Qhsin, where Qhsin is a
quality threshold defined implicitly by the relevant tests in [2].
Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive. “Out-of-sync” is generated in the event
that, during the last 160ms period, Qhs < Qhsout, where Qhsout is a quality threshold defined implicitly by the relevant tests
in [2]. CPHY-Out-of-Sync-IND shall also be generated in the event of 16 successive HS-DSCH CRC failures. On
occurrence of this event, the HS-DSCH_failure indicator shall be set to ‘true’.
How the primitives are used by higher layers is described in [15]. The above definitions may lead to radio frames
where neither the In-Sync nor Out-of-Sync primitives are reported. They may also, under some circumstances, lead to
radio frames in which both In-Sync and Out-of-Sync primitives are generated. In this instance, In-sync shall override
Out-of-Sync and the Out-of-Sync primitive shall not be reported.
4.4.2.1.3 Uplink synchronisation primitives

Layer 1 in the Node B shall every radio frame check synchronisation status, individually for each UL CCTrCH of the
radio link. Synchronisation status is indicated to the RL Failure/Restored triggering function using either the CPHY-
Sync-IND or CPHY-Out-of-Sync-IND primitive.
3GPP
Release 8 20 3GPP TS 25.224 V8.0.0 (2008-03)
The exact criteria for indicating in-sync/out-of-sync is not subject to specification, but could e.g. be based on received
burst quality or CRC checks. One example would be to have the same criteria as for the downlink synchronisation
status primitives.
4.4.2.2 Radio link monitoring
4.4.2.2.1 Downlink radio link failure

The downlink CCTrCHs are monitored by the UE, to trigger radio link failure procedures. The downlink CCTrCH
failure status is specified in [15], and is based on the synchronisation status primitives CPHY-Sync-IND and CPHY-
Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. These primitives shall provide status for each DL
CCTrCH separately.
4.4.2.2.2 Uplink radio link failure/restore

The uplink CCTrCHs are monitored by the Node B in order to trigger CCTrCH failure/restore procedures. The uplink
CCTrCH failure/restore status is reported using the synchronisation status primitives CPHY-Sync-IND and CPHY-Out-
of-Sync-IND, indicating in-sync and out-of-sync respectively.
When the CCTrCH is in the in-sync state, Node B shall start timer T_RLFAILURE after receiving N_OUTSYNC_IND
consecutive out-of-sync indications. Node B shall stop and reset timer T_RLFAILURE upon receiving successive
N_INSYNC_IND in-sync indications. If T_RLFAILURE expires, Node B shall indicate to higher layers which
CCTrCHs are out-of-sync using the synchronization status primitives. Furthermore, the CCTrCH state shall be changed
to the out-of-sync state.
When a CCTrCH is in the out-of-sync state, after receiving N_INSYNC_IND successive in-sync indications Node B
shall indicate that the CCTrCH has re-established synchronisation and the CCTrCH’s state shall be changed to the in-
sync-state. The specific parameter settings (values of T_RLFAILURE, N_OUTSYNC_IND, and N_INSYNC_IND) are
configurable, see [16].
4.5 Discontinuous transmission (DTX) procedure

The DTX procedure shall be applied for CCTrCHs mapped to S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH,
if the total bit rate of the CCTrCH differs from the total channel bit rate of the physical channels allocated to this
CCTrCH. DTX shall not be applied to E-DCH mapped to E-PUCH.
The DTX procedure shall also be applied to HS-PDSCHs, HS-SCCHs, E-AGCHs and E-HICHs if no data is to be
transmitted on these physical channels in a given TTI.
Rate matching is used in order to fill resource units completely, that are only partially filled with data. In the case that
after rate matching and multiplexing no data at all is to be transmitted in a resource unit the complete resource unit shall
be discarded from transmission (DTX), unless a Special Burst is transmitted in the RU. This applies also to the case
where only one resource unit is allocated and no data has to be transmitted.
4.5.0 Description of Special Bursts

For S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, the Special Burst has the same timeslot format as the burst
used for data provided by higher layers. If the timeslot format contains a TFCI field, then the TFCI field shall be filled
with “0” bits. The Special Burst may also carry layer 1 control symbols such as TPC bits for the purposes of inner-loop
power control. The data portions of the Special Burst are filled with an arbitrary bit pattern.
For S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, the transmission power of the special burst shall be the
same as that of the substituted physical channel of the CCTrCH. In the case of uplink physical channels where
autonomous spreading factor change by the UE is permitted by higher layers, the substituted physical channel is
considered to be that which would have been employed for the lowest non-zero rate TFC within the set of allowed
TFC’s and the transmission power of the Special Burst shall again correspond to that of the physical channel
substituted.
For HS-PDSCH, the Special Burst shall use the timeslot format #0 from table 7a, see section 5.3.9.5 in [8]. For HS-
SCCH, the Special Burst shall use timeslot format #0 from table 5a, see section 5.2.2.6.1 in [8]. The Special Burst is
3GPP
Release 8 21 3GPP TS 25.224 V8.0.0 (2008-03)
filled with an arbitrary bit pattern. The transmission power of the Special Burst shall be the same as that of the
substituted Beacon channel.
4.5.1 Use of Special Bursts during DTX

In the case that after link establishment there are no transport blocks provided for transmission by higher layers for a
given CCTrCH mapped to UL DPCH, DL DPCH, PUSCH or PDSCH physical channels, then a Special Burst shall be
transmitted in the first allocated frame of the transmission pause. If, including the first frame, there is a consecutive
period of Special Burst Period (SBP) frames without transport blocks provided by higher layers, then another special
burst shall be generated and transmitted at the next possible frame. This pattern shall be continued until transport blocks
are provided for the CCTrCH by the higher layers. SBP shall be provided by higher layers. The value of SBP shall be
independently specified for uplink and for downlink and shall be designated as
SBGP (special burst generation period) for uplink transmissions
SBSP (special burst scheduling parameter) for downlink transmissions
The default value for both SBGP and SBSP shall be 8.
The Special Burst shall be transmitted using the physical channel with the lowest physical channel sequence number (p)
as defined by the rate matching function in [9].
Special Bursts shall not be transmitted for HS-SCCH and for CCTrCHs mapped to S-CCPCH or HS-PDSCH in non-
Beacon locations, i.e. only DTX shall be applied to these physical channels.
4.5.2 Use of Special Bursts for Initial Establishment / Reconfiguration

Upon initial establishment or reconfiguration for either 160 ms following detection of in-sync, or until the first transport
block is received from higher layers, both the UE and the Node B shall transmit the special burst for each CCTrCH
mapped to UL DPCH, DL DPCH, PUSCH and PDSCH physical channels.
4.5.3 Use of Special Bursts for DTX on Beacon Channels

In the case that a beacon-function physical channel (S-CCPCH or PDSCH) would be DTX’d, then a Special Burst shall
be transmitted on the Beacon Channel in that frame instead in order to maintain the beacon functionality.
4.6 Downlink Transmit Diversity

Downlink transmit diversity for PDSCH, DPCH, P-CCPCH, S-CCPCH, PICH, MICH, HS-SCCH, HS-PDSCH, E-
AGCH, E-HICH and SCH is optional in UTRAN. Its support is mandatory at the UE.
4.6.1 Transmit Diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-

AGCH
The transmitter structure to support transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH
transmission is shown in figure 1. Channel coding, interleaving and spreading are done as in non-diversity mode. The
spread complex valued signal is fed to both TX antenna branches, and weighted with antenna specific weight factors w1
3GPP
Release 8 22 3GPP TS 25.224 V8.0.0 (2008-03)
and w2. The weight factors are complex valued signals (i.e., wi = ai + jbi ), in general. These weight factors are calculated
on a per slot and per user basis.
The weight factors are determined by the UTRAN. Examples of transmit diversity schemes are given in annex B.
ANT1
FIR RF
Midamble w1
MUX
Data ENC INT SPR+SCR ANT2
FIR RF
w2
Uplink channel estimate
Figure 1: Downlink transmitter structure to support Transmit Diversity

for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point)
4.6.2 Transmit Diversity for SCH and S-CCPCH

Time Switched Transmit Diversity (TSTD) can be employed as a transmit diversity scheme for the synchronisation
channel and/or S-CCPCH.
4.6.2.1 SCH Transmission Scheme

The transmitter structure to support transmit diversity for SCH transmission is shown in figure 2. P-SCH and S-SCH are
transmitted from antenna 1 and antenna 2 alternatively. An example for the antenna switching pattern is shown in figure
3.
Ant 1
P-SCH FIR RF
S-SCH
Ant 2
Switching Control FIR RF

for SCH transmission (UTRAN Access Point)
3GPP
Release 8 23 3GPP TS 25.224 V8.0.0 (2008-03)
Frame(15slot) Frame(15slot)
CP CP
Ant #1 b1c1 b1c1
: :
CP CP
Ant #2 b1c1 b1c1
: :
Figure 3: Antenna Switching Pattern (Case 2)
4.6.2.2 S-CCPCH Transmission Scheme

The transmitter structure to support TSTD for S-CCPCH is shown in figure 3a. The antenna switching pattern is under
the control of the Node-B and is not explicitly known to the UE. Switching may only be performed during the guard
periods between timeslots.
Ant 1
FIR RF
S-CCPCH
Ant 2
Switching Control FIR RF
Figure 3a: Downlink transmitter structure to support TSTD

for S-CCPCH transmission (UTRAN Access Point)
4.6.3 Transmit Diversity for Beacon Channels

When beacon channels use burst type 4, SCTD shall not be applied.
When beacon channels use burst type 1, Space Code Transmit Diversity (SCTD) for beacon channels may be employed
optionally in the UTRAN. The support is mandatory in the UE except for the case where the UE only supports burst
type 4. The use of SCTD will be indicated by higher layers. If SCTD is active within a cell:
- SCTD shall be applied to any beacon channel, and
- the maximum number KCell of midambles for burst type 1 that are supported in this cell may be 8 or 16, see [8]. The
case of KCell = 4 midambles is not allowed for this burst type.
4.6.3.1 SCTD Transmission Scheme

The open loop downlink transmit diversity scheme for beacon channels is shown in figure 4. Channel coding, rate
matching, interleaving and bit-to-symbol mapping are performed as in the non-diversity mode. In Space Code Transmit
3GPP
Release 8 24 3GPP TS 25.224 V8.0.0 (2008-03)
( k 1) ( k 2)
Diversity mode the data sequence is spread with the channelisation codes c16 and c16 and scrambled with the cell
( k 2)
specific scrambling code. The spread sequence on code c16 is then transmitted on the diversity antenna. The power
applied to each antenna shall be equal.
Midamble 1 Tx.
M
Antenna 1
U
X
SPR-SCR c(1)
Encoded and Interleaved Data

Symbols, 2 data fields
SPR-SCR c(2) Tx.
M Antenna 2
U
X
Midamble 2
Figure 4: Block Diagram of the transmitter SCTD
4.7 Random access procedure

The physical random access procedure described below is invoked whenever a higher layer requests transmission of a
message on the RACH. The physical random access procedure is controlled by primitives from RRC and MAC.
Retransmission on the RACH in case of failed transmission (e.g. due to a collision) is controlled by higher layers. Thus,
the backoff algorithm and associated handling of timers is not described here. The definition of the RACH in terms of
PRACH Access Service Classes is broadcast on the BCH in each cell. Parameters for common physical channel uplink
outer loop power control are also broadcast on the BCH in each cell. The UE needs to decode this information prior to
transmission on the RACH. Higher layer signalling may indicate, that in some frames a timeslot shall be blocked for
RACH uplink transmission.
4.7.1 Physical random access procedure

The physical random access procedure described in this subclause is initiated upon request from the MAC sublayer (see
[18] and [19]).
Note: The selection of a PRACH is done by the RRC Layer.
Before the physical random-access procedure can be initiated, Layer 1 shall receive the following information from the
RRC layer using the primitives CPHY-TrCH-Config-REQ and CPHY-RL-Setup/Modify-REQ.
- the available PRACH channelization codes (There is a 1-1 mapping between the channelization code and the
midamble shift as defined by RRC) for each Access Service Class (ASC) of the selected PRACH (the selection
of a PRACH is done by the RRC ). CPHY-RL-Setup/Modify-REQ);
- the timeslot, spreading factor, and midamble type(direct or inverted) for the selected PRACH (CPHY-RL-
Setup/Modify-REQ);
- the RACH Transport Format (CPHY-TrCH-Config-REQ);
- the RACH transport channel identity (CPHY-TrCH-Config-REQ)
- the set of parameters for common physical channel uplink outer loop power control(CPHY-RL-Setup/Modify-
REQ).
NOTE: The above parameters may be updated from higher layers before each physical random access procedure
is initiated.
At each initiation of the physical random access procedure, Layer 1 shall receive the following information from the
MAC:
3GPP
Release 8 25 3GPP TS 25.224 V8.0.0 (2008-03)
- the ASC of the PRACH transmission;
- the data to be transmitted (Transport Block Set).
the selected ASC sub-channel. The ASC subchannel is defined in reference [18]. The value is passed in the
PHY-Data-REQ is the CFNCELL.
In addition, Layer 1 may receive information from higher layers, that a timeslot in certain frames shall be blocked for
PRACH uplink transmission.
The physical random-access procedure shall be performed as follows:
1 Randomly select one channelization code from the set of available codes for the selected ASC. The random
function shall be such that each code is chosen with equal probability.
2 Determine the midamble shift to use, based on the selected channelization code.
3 Set the PRACH message transmission power level according to the specification for common physical channels
in uplink (see subclause 4.2.2.2).
4 Transmit the RACH Transport Block Set (the random access message) with no timing advance in the selected
sub-channel using the selected channelization code.
4.7a E-RUCCH transmission procedure

Requests for the transmission of an E-RUCCH are controlled by higher layers [18].
The E-RUCCH random access procedure shall be performed as follows:
1 Randomly select one channelization code from the set of available codes for E-RUCCH. The random function
shall be such that each code is chosen with equal probability.
2 Determine the midamble shift to use, based on the selected channelization code.
3 Set the E-RUCCH message transmission power level according to subclause 4.2.2.5.
4 Transmit the E-RUCCH with no timing advance using the selected channelization code.
4.8 DSCH procedure

The physical downlink shared channel procedure described below shall be applied by the UE when the physical layer
signalling either with the midamble based signalling or TFCI based signalling is used to indicate for the UE the need for
PDSCH detection. There is also a third alternative to indicate to the UE the need for the PDSCH detection and this is
done by means of higher layer signalling, already described in [8].
4.8.1 DSCH procedure with TFCI indication

When the UE has been allocated by higher layers to receive data on DSCH using the TFCI, the UE shall decode the
PDSCH in the following cases:
- In case of a standalone PDSCH the TFCI is located on the PDSCH itself, then the UE shall decode the TFCI and
based on which data rate was indicated by the TFCI, the decoding shall be performed. The UE shall decode
PDSCH only if the TFCI word decode corresponds to the TFC part of the TFCS given to the UE by higher
layers.
- In case that the TFCI is located on the DCH, the UE shall decode the PDSCH frame or frames if the TFCI on the
DCH indicates the need for PDSCH reception. Upon reception of the DCH time slot or time slots, the PDSCH
slot (or first PDSCH slot) shall start SFN n+2 after the DCH frame containing the TFCI, where n indicates the
SFN on which the DCH is received. In the case that the TFCI is repeated over several frames, the PDSCH slot
shall start SFN n+2 after the frame having the DCH slot which contains the last part of the repeated TFCI.
3GPP
Release 8 26 3GPP TS 25.224 V8.0.0 (2008-03)
4.8.2 DSCH procedure with midamble indication

When the UE has been allocated by higher layers to receive PDSCH based on the midamble used on the PDSCH
(midamble based signalling described in [8]), the UE shall operate as follows:
- The UE shall test the midamble it received and if the midamble received was the same as indicated by higher
layers to correspond to PDSCH reception, the UE shall detect the PDSCH data according to the TF given by the
higher layers for the UE.
- In case of multiple time slot allocation for the DSCH indicated to be part of the TF for the UE, the UE shall
receive all timeslots if the midamble of the first timeslot of PDSCH was the midamble indicated to the UE by
higher layers.
- In case the standalone PDSCH (no associated DCH) contains the TFCI the UE shall detect the TF indicated by
the TFCI on PDSCH.
4.9 Node B Synchronisation Procedure over the Air

An option exists to use cell sync bursts to achieve and maintain Node B synchronisation [20]. This optional procedure is
based on transmissions of cell synchronisation bursts [10] in predetermined timeslots normally assigned to contain
PRACH, according to an RNC schedule. Such soundings between neighbouring cells facilitate timing offset
measurements by the cells. The timing offset measurements are reported back to the RNC for processing. The RNC
generates cell timing updates that are transmitted to the Node Bs and cells for implementation.
When Cell Sync Bursts are used to achieve and maintain intercell Synchronisation there are three distinct phases, with a
potential additional sub-phase involving late entrant cells.
4.9.1 Frequency Acquisition Phase

The frequency acquisition phase is used to bring cells of an RNS area to within frequency limits prior to initial
synchronisation. No traffic is supported during this phase. In this phase cell(s) identified as master time reference shall
transmit cell sync bursts [10] specified by higher layers continuously, i. e. one in every timeslot. All other cells shall
listen for transmissions and shall perform frequency locking to the transmissions received. They shall signal
completion of frequency acquisition to the RNC and begin continuous transmission of cell sync bursts specified by
higher layers.
4.9.2 Initial Synchronisation

For Initial Phase, where no traffic is supported, the following procedure for initial synchronisation may be used to bring
cells of an RNS area into synchronisation at network start up. In this phase each cell shall transmit cell sync bursts [10]
according to the higher layer command. All cells use the same cell sync burst code and code offset. Each cell shall
listen for transmissions from other cells. Each cell shall report the timing and received SIR of successfully detected cell
sync bursts to the RNC. The RNC uses these measurements to adjust the timing of each cell to achieve the required
synchronisation accuracy.
4.9.3 Steady-State Phase

The steady-state phase is used to maintain the required synchronisation accuracy. With the start of the steady-state
phase, traffic is supported in a cell. A procedure that may be used for the steady-state phase involves cell synch bursts
[10] that are transmitted and received without effect on existing traffic. Higher layers signal the transmit parameters,
i.e., when to transmit which code and code offset, and which transmit power to use. The higher layers also signal to
appropriate cells the receive parameters i. e. which codes and code offsets to measure in a certain timeslot. Upon
determination of errors in timing, the RNC may adjust the timing of a cell or cells.
4.9.4 Late entrant cells

A procedure that may be used for introducing new cells into an already synchronised RNS involves the one time
transmission of a single cell sync burst [10] (scheduled by higher layers) by all neighbour cells of the late entrant cell.
3GPP
Release 8 27 3GPP TS 25.224 V8.0.0 (2008-03)
and received by the late entrant cell. The RNC may use this information to adjust the late entrant cell sufficiently to
allow the cell to enter steady state phase.
4.10 Idle periods for IPDL location method

4.10.1 General
To support time difference measurements for location services, idle periods can be created in the downlink (hence the
name IPDL) during which time transmission of all channels from a Node B is temporarily ceased, except for the SCH
transmission. During these idle periods the visibility of neighbour cells from the UE is improved.
The idle periods are arranged in a determined pattern according to higher layer parameters. An idle period has a
duration of one time slot. During idle periods only the SCH is transmitted. No attempt is made to prevent data loss.
In general there are two modes for these idle periods:
- Continuous mode, and
- Burst mode.
In continuous mode the idle periods are active all the time. In burst mode the idle periods are arranged in bursts where
each burst contains enough idle periods to allow a UE to make sufficient measurements for its location to be calculated.
The bursts are separated by a period where no idle periods occur.
The time difference measurements can be performed on any channel. If the P-CCPCH falls in an idle slot, UTRAN may
decide not to transmit the P-CCPCH in two consecutive frames, the first of these two frames containing the idle slot.
This option is signalled by higher layers.
4.10.2 Parameters of IPDL

The following parameters are signalled to the UE via higher layers:
IP_Status: This is a logic value that indicates if the idle periods are arranged in continuous or burst mode.
IP_Spacing: The number of 10 ms radio frames between the start of a radio frame that contains an idle period and
the next radio frame that contains the next idle period. Note that there is at most one idle period in a
radio frame.
IP_Start: The number of the first frame with idle periods. In case of continuous mode IP_Start is the SFN of
the first frame with idle periods and in case of burst mode IP_Start defines the number of frames
after Burst_Start with the first frame with idle periods.
IP_Slot: The number of the slot that has to be idle [0..14].
IP_PCCPCH: This logic value indicates, if the P-CCPCH is switched off in two consecutive frames. The first of
these two frames contains the idle period.
Additionally in the case of burst mode operation the following parameters are also communicated to the UE.
Burst_Start: Specifies the start of the first burst of idle periods. 256Burst_Start is the SFN where the first burst
of idle periods starts.
Burst_Length: The number of idle periods in a burst of idle periods.
Burst_Freq: Specifies the time between the start of a burst and the start of the next burst. 256Burst_Freq is the
number of radio frames between the start of a burst and the start of the next burst.
4.10.3 Calculation of idle period position

In burst mode, burst #0 starts in the radio frame with SFN = 256Burst_Start. Burst #n starts in the radio frame with
SFN = 256Burst_Start + n256Burst_Freq ( n = 0,1,2, …). The sequence of bursts according to this formula
continues up to and including the radio frame with SFN = 4095. At the start of the radio frame with SFN = 0, the burst
3GPP
Release 8 28 3GPP TS 25.224 V8.0.0 (2008-03)
sequence is terminated (no idle periods are generated) and at SFN = 256Burst_Start the burst sequence is restarted
with burst #0 followed by burst #1 etc., as described above.
Continuous mode is equivalent to burst mode, with only one burst spanning the whole SFN cycle of 4096 radio frames,
this burst starts in the radio frame with SFN = 0. In case of continuous mode the parameter IP_Start defines the first
frame with idle periods.
The position of an idle period is defined by two values: IP_Frame(x) and IP_Slot. IP_Frame(x) defines the xth frame
within a burst that contains the idle period. IP_Slot defines the slot in that frame during which no transmission takes
place except for the SCH.
The actual frame with idle periods within a burst is calculated as follows:
IP_Frame(x) = IP_Start + (x-1)  IP_Spacing with x = 1, 2, 3, ....
If the parameter IP_PCCPCH is set to 1, then the P-CCPCH will not be transmitted in the frame IP_Frame(x) +1 within
a burst.
Figure 5 below illustrates the idle periods for the burst mode case, if the IP_P-CCPCH parameter is set to 0.
IP_Slot
Slot #0 Slot #1 Slot #14
xth idle period in burst

IP_Frame(x)
(Burst_Length)th idle period
IP_Frame(1)
Frame #i
‘IP_Start’ frames ‘IP_Spacing’ frames
Burst #0 of idle periods Burst #1 of idle periods
SFN = 0
‘256×Burst_Start’ frames ‘256×Burst_Freq’ frames

SFN = SFN =
256×Burst_Start 256×Burst_Start + 256×Burst_Freq
Figure 5: Idle Period placement in the case of burst mode operation with IP_P-CCPCH parameter set
to 0
4.11 HS-DSCH Procedure

4.11.1 Link Adaptation Procedure
For HS-DSCH, the modulation scheme and effective code rate shall be selected by higher layers located within the
NodeB. This shall be achieved by appropriate selection of an HS-DSCH transport block size, modulation format and
resources by higher layers. Selection of these parameters may be based on CQI reports from the UE.
The overall HS-DSCH link adaptation procedure consists of two parts:
Node B procedure:
3GPP
Release 8 29 3GPP TS 25.224 V8.0.0 (2008-03)
1) The NodeB shall transmit HS-SCCH carrying a UE identity identifying the UE for which HS-DSCH TTI
allocation has been given. In the case of HS-DSCH transmissions in consecutive TTIs to the same UE, the same
HS-SCCH shall be used for associated signalling.
2) The NodeB transmits HS-DSCH to the UE using the resources indicated in the HS-SCCH.
3) Upon receiving the HS-SICH from the respective UE, the status report (ACK/NACK and CQI) shall be passed to
higher layers.
UE procedure:
1) When indicated by higher layers, the UE shall start monitoring all HS-SCCHs that are in its HS-SCCH set as
signalled to it by higher layers. The information carried on the HS-SCCH is described in [8].
2) In the case that a HS-SCCH is identified to be correct by its CRC, the UE shall read the HS-PDSCHs indicated
by the HS-SCCH. In the case that a HS-SCCH is identified to be incorrect, the UE shall discard the data on the
HS-SCCH and return to monitoring.
3) After reading the HS-PDSCHs, the UE shall generate an ACK/NACK message and transmit this to the NodeB in
the associated HS-SICH, along with the most recently derived CQI.
The mapping of HS-PDSCH channelisation code set and timeslot information carried by the HS-SCCH for a given HS-
DSCH TTI is described in [9].
For a given allocation of HS-PDSCH resources to a UE for a specific HS-DSCH TTI, the following shall apply:
 If timeslot information on HS-SCCH indicates two or more timeslots, none of these timeslots shall comprise a
beacon channel.
 If timeslot information on HS-SCCH indicates a single timeslot and this timeslot comprises a beacon channel
then:
o The Node-B shall not indicate SF=1 for any HS-PDSCH resource.
o The set of HS-PDSCH resources allocated by the Node-B to a UE shall exclusively comprise either
beacon function or non-beacon function physical channels. The Node B shall therefore not allocate
both beacon function and non-beacon function physical channels within the beacon timeslot to the
UE. If the HS-DSCH for a specific HS-DSCH TTI is mapped to the beacon channel, this shall be
signalled using kstart = 1 and kstop = 1. For a definition of the first and last allocated channelisation code
indices kstart and kstop on HS-SCCH refer to [9].
o When SCTD antenna diversity is applied to the beacon channel, then the presence of channelisation
code within the channelisation code set information on HS-SCCH shall implicitly indicate the
presence of channelisation code .
4.11.2 HS-DSCH Channel Quality Indication Procedure

The channel quality indicator (CQI) provides the NodeB with an estimate of the code rate that would have maximised
the single-transmission throughput of the previous HS-DSCH transmission if decoded in isolation. The CQI report
requires to be referenced to a given set of HS-PDSCH resources by the NodeB, but note that the UE is not restricted to
making measurements only on these reference resources when deriving a given CQI. The reference resources for a CQI
report shall be a set of HS-PDSCH resources that were received by the UE in a single TTI, and contain a complete
transport block. These resources will be known to the NodeB from the relative timings of the HS-SICH carrying the
CQI and previous HS-DSCH transmissions to the UE.
The CQI consists of two fields; a Recommended Transport Block Size (RTBS) and a Recommended Modulation
Format (RMF). The UE shall use the same mapping table for these fields as is being used for the time slot information
and modulation scheme information fields respectively of the HS-SCCH [18].
The reporting procedure is as follows:
1. The UE receives a message on an HS-SCCH telling it which resources have been allocated to it for the next
associated HS-DSCH transmission.
3GPP
Release 8 30 3GPP TS 25.224 V8.0.0 (2008-03)
2. The UE reads the associated HS-DSCH transmission, and makes the necessary measurements to derive a CQI
that it estimates would have given it the highest single-transmission throughput for the allocated resources whilst
achieving a BLER of no more than 10 %.
BLER, in this context, is defined as the probability that a transport block transmitted using the RTBS and RMF
is received in error if decoded in isolation. For the purposes of this calculation, it shall be assumed that the
transport block that would be transmitted with these parameters would use redundancy version parameters s = 1
and r = 0. Note that, by this definition, a UE shall never report a CQI that corresponds to a code rate greater than
unity.
Using this definition of BLER, single-transmission throughput shall be defined as follows :
single-transmission throughput = (1 – BLER)  RTBS
3. The CQI report derived from a given HS-DSCH transmission shall be reported to the NodeB in the next HS-
SICH available to the UE following that HS-DSCH transmission, unless that HS-SICH immediately follows the
last allocated HS-DSCH timeslot, in which case the subsequent available HS-SICH shall be used by the UE.
This HS-SICH may not necessarily be the same HS-SICH that carries the ACK/NACK information for that HS-
DSCH transmission. The UE shall always transmit the most recently derived CQI in any given HS-SICH, which
may mean that some CQI reports are discarded without being transmitted to the NodeB.
4.12 Macro-diversity procedure

When signalled by higher layers, the UE shall combine transmissions on signalled transport channels from multiple
radio links. UTRAN shall only indicate that a transport channel on a radio link may be combined with a transport
channel on another radio link when those transport channels do not occupy the same time slot. UTRAN shall transmit
identical transport blocks on the multiple radio links on the transport channels that may be combined. UTRAN may
multiplex onto a CCTrCH other transport channels with transport channels that can be combined. The TTIs of
transmissions that may be combined shall start at the same SFN on each of the multiple radio links.
4.13 E-DCH related procedures

4.13.1 ACK/NACK detection
The physical layer in the UE shall detect ACK or NACK contained within the E-HICH. Which E-HICH is associated
with the corresponding E-DCH transmission is defined in [8].
4.13.2 Serving and neighbour cell pathloss metric derivation

The UE shall be capable of measuring the P-CCPCH RSCP of the serving cell and of intra-frequency neighbour cells in
accordance with [11]. The P-CCPCH transmit power (Pref) of the serving cell and of each intra-frequency neighbour
cell in the monitored neighbour cell list shall be signalled by higher layers to the UE in order that the UE may estimate
the mean pathloss to the serving cell (Lserv) and to each of the N neighbour cells in the monitored neighbour cell list (L1,
L2, … LN).
Higher layers shall configure the UE to use SNPL reporting type 1 or SNPL reporting type 2. In accordance with the
SNPL reporting type, the UE shall be capable of forming a metric corresponding to:
{for SNPL reporting type 1}
The metric  shall be converted into a logarithmic (dB) value Q and shall be mapped to a Serving and Neighbour Cell
Pathloss (SNPL) index according to table 1b. The SNPL index is supplied to and used by higher layers (see [18]).
3GPP
Release 8 31 3GPP TS 25.224 V8.0.0 (2008-03)
Table 1b: SNPL mapping

Q = 10*log10() SNPL index
Q <-6 0
-6 ≤ Q < -5 1
-5 ≤ Q < -4 2
-4 ≤ Q < -3 3
-3 ≤ Q < -2 4
-2 ≤ Q < -1 5
-1 ≤ Q < -0 6
0≤Q<1 7
1≤Q<2 8
2≤Q<3 9
3≤Q<4 10
4≤Q<5 11
5≤Q<6 12
6≤Q<7 13
7≤Q<8 14
8≤Q<9 15
9 ≤ Q < 10 16
10 ≤ Q < 11 17
11 ≤ Q < 12 18
12 ≤ Q < 13 19
13 ≤ Q < 14 20
14 ≤ Q < 15 21
15 ≤ Q < 16 22
16 ≤ Q < 17 23
17 ≤ Q < 18 24
18 ≤ Q < 19 25
19 ≤ Q < 20 26
20 ≤ Q < 21 27
21 ≤ Q < 22 28
22 ≤ Q < 23 29
23 ≤ Q < 24 30
24 ≤ Q < 25 31
If the higher layer signalling information regarding the required P-CCPCH reference powers is not available, the UE
shall return an SNPL index value of 7.
4.13.3 Channelisation code hopping procedure for E-PUCH

Channelisation code hopping may be applied to E-PUCH transmissions.
When channelisation code hopping is configured by higher layers, the allocated OVSF code (determined by the code
resource related information (CRRI) on E-AGCH – see [9]) is first transformed by the physical layer into a sequence of
“effective” allocated OVSF codes (one for each active timeslot of the resource allocation) before further physical layer
processing is performed (see figure 5a). The mapping of the allocated code to the sequence of effective codes is a
function of the allocated timeslots and of the current CFN.
3GPP
Release 8 32 3GPP TS 25.224 V8.0.0 (2008-03)
Figure 5a - physical layer interpretation of OVSF code allocation in the case that channelisation code
hopping is applied
The allocated OVSF code (indicated by E-AGCH) is denoted . The sequence of “effective” allocated OVSF
codes is denoted , one for each allocated timeslot index value ti. nTRRI is configured by higher layers [15].
The set of nTRRI timeslots configured for E-DCH use is denoted tE-DCH (where each element of tE-DCH may assume a value
between 0 and 14). The first element of tE-DCH is associated with ti = 0, the second element with ti = 1 and so on. ti = 0
therefore corresponds to the lowest numbered timeslot configured for E-DCH use and to the first element (LSB) of the
timeslot resource related information bitmap [9].
A hopping index parameter hi is calculated for each timeslot of the E-DCH TTI in which the UE has been allocated as
follows:
The effective allocated OVSF code for timeslot index ti is then derived from hi and the channelisation code
indicated by the corresponding E-AGCH ( ) as according to table 1c.
Table 1c: Hopping index parameter sequences
Hop index hi
CRRI
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
SF16
1 15 1 9 5 13 3 11 7 15 2 10 6 14 4 12 8 16
2 16 2 10 6 14 4 12 8 16 1 9 5 13 3 11 7 15
3 17 3 11 7 15 1 9 5 13 4 12 8 16 2 10 6 14
4 18 4 12 8 16 2 10 6 14 3 11 7 15 1 9 5 13
5 19 5 13 1 9 7 15 3 11 6 14 2 10 8 16 4 12
6 20 6 14 2 10 8 16 4 12 5 13 1 9 7 15 3 11
7 21 7 15 3 11 5 13 1 9 8 16 4 12 6 14 2 10
8 22 8 16 4 12 6 14 2 10 7 15 3 11 5 13 1 9
9 23 9 1 13 5 11 3 15 7 10 2 14 6 12 4 16 8
10 24 10 2 14 6 12 4 16 8 9 1 13 5 11 3 15 7
11 25 11 3 15 7 9 1 13 5 12 4 16 8 10 2 14 6
12 26 12 4 16 8 10 2 14 6 11 3 15 7 9 1 13 5
3GPP
Release 8 33 3GPP TS 25.224 V8.0.0 (2008-03)
13 27 13 5 9 1 15 7 11 3 14 6 10 2 16 8 12 4
14 28 14 6 10 2 16 8 12 4 13 5 9 1 15 7 11 3
15 29 15 7 11 3 13 5 9 1 16 8 12 4 14 6 10 2
16 30 16 8 12 4 14 6 10 2 15 7 11 3 13 5 9 1
SF8
1 7 1 5 3 7 2 6 4 8 1 5 3 7 2 6 4 8
2 8 2 6 4 8 1 5 3 7 2 6 4 8 1 5 3 7
3 9 3 7 1 5 4 8 2 6 3 7 1 5 4 8 2 6
4 10 4 8 2 6 3 7 1 5 4 8 2 6 3 7 1 5
5 11 5 1 7 3 6 2 8 4 5 1 7 3 6 2 8 4
6 12 6 2 8 4 5 1 7 3 6 2 8 4 5 1 7 3
7 13 7 3 5 1 8 4 6 2 7 3 5 1 8 4 6 2
8 14 8 4 6 2 7 3 5 1 8 4 6 2 7 3 5 1
SF4
1 3 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4
2 4 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3
3 5 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2
4 6 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1
SF2
1 1 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2
2 2 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1
SF1
1 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
For all subsequent operations, the physical layer shall assume the allocated E-PUCH physical resources to be described
by the effective allocated code derived for that timeslot.

The basic purpose of power control is to limit the interference level within the system thus reducing the intercell
interference level and to reduce the power consumption in the UE.
The main characteristics of power control are summarized in the following table.
Table 2: Transmit Power Control characteristics
Uplink Downlink
Power control rate Variable Variable
Closed loop: 0-200 cycles/sec. Closed loop: 0-200 cycles/sec.
Open loop: (about 200us –
3575us delay )
Step size 1,2,3 dB (closed loop) 1,2,3 dB (closed loop)
Remarks All figures are without processing

and measurement times
3GPP
Release 8 34 3GPP TS 25.224 V8.0.0 (2008-03)
Note: All codes within one timeslot allocated to the same CCTrCH use the same transmission power in case they have
the same Spreading Factor.
5.1.1 Uplink Control
5.1.1.1 General limits

By means of higher layer signalling, the Maximum_Allowed_UL_TX_ power for uplink may be set to a value lower
than what the terminal power class is capable of. Uplink power control shall be performed while the total UE transmit
power is below the maximum allowed output TX power. In some cases the total requested UE transmit power in a
timeslot after uplink power control calculation might exceed the maximum allowed output power. In these cases the
calculated transmit power of all uplink physical channels in this timeslot shall be scaled by the same amount in dB
before transmission in order that the total UE transmission power used shall be the maximum allowed output power.
The UTRAN may not expect the UE to be capable of reducing its total transmit power below the minimum level
specified in [2].
5.1.1.2 UpPCH
The transmit power for the UpPCH is set by higher layers based on open loop power control as described in [15]
5.1.1.3 PRACH
The transmit power for the PRACH is set by higher layers based on open loop power control as described in [15].
5.1.1.4 DPCH and PUSCH

The initial transmission power for uplink DPCH and PUSCH is set by higher layers based on open loop power control
as described in [15]. The UE then transits into closed loop power control. The node B shall generate TPC commands
according to a quality target set by higher layers in order to instruct an increase or decrease in the level of transmission
power from the UE and send them either in the TPC field of associated downlink CCTrCHs (see [8] for a description of
the mapping between DL associated TPC symbols and UL controlled CCTrCH/timeslots) or on PLCCH (see [8]
5A.3.13). If the physical channel power should be increased, the TPC command is set to “up”, whereas if the power
should be reduced the command is set to “down”. A TPC command sent in a downlink CCTrCH or via PLCCH controls
all uplink DPCHs and PUSCHs in the associated uplink CCTrCH and timeslot. An example of SIR based UL power
control is given in annex A2
If signalled by higher layers, the UE must follow the received TPC commands only. In this case, at the UE when the
TPC command is judged as ‘down’, the mobile transmit power shall be reduced by one power control step, whereas if it
is judged as ‘up’, the mobile transmit power shall be raised by one power control step.
If indicated as allowed by higher layers, the UE may optionally take into account pathloss estimated from beacon
function physical channels in addition to the TPC commands when calculating the transmit power. In this case, the
mobile transmit power is first modified as described above by the received TPC command and is then further modified
based upon the pathloss estimated on recent beacon transmissions. Modifications based upon pathloss shall only be
applied when the UE estimates that the pathloss on the uplink transmission timeslot and the pathloss on the beacon
timeslots used to derive the modification value are likely to be similar.
The closed loop power control procedure for UL DPCH and PUSCH is not affected by the use of TSTD.
In the event of no associated uplink data being transmitted between two related downlink TPC commands, the UE shall
ignore the resulting TPC command. The transmit power for the next instance of the timeslot/CCTrCH pair shall then be
set:
i) to the power level of the previous uplink transmission, optionally modified to compensate for the change
in pathloss observed during the uplink transmission pause or,
3GPP
Release 8 35 3GPP TS 25.224 V8.0.0 (2008-03)
ii) using the open loop procedure as for initial transmissions.
The UE shall select which of the above methods to apply. For short transmission pauses method (i) should be used.
5.1.1.4.1 Gain Factors

Same as that of 3.84 Mcps TDD, cf. [4.2.2.3.1 Gain Factors].
5.1.1.4.2 Out of synchronization handling

In the case that uplink DPCH is controlled by TPC commands carried on downlink DPCH, out of synchronisation
handling is the same as that of 3.84 Mcps TDD, cf.[ 4.2.2.3.2 Out of synchronisation handling].
In the case that uplink DPCH is controlled by TPC commands carried on PLCCH, the UE shall shut off the transmission
of an UL CCTrCH if the following criteria are fulfilled for the PLCCH carrying its TPC commands:
- The UE estimates the received PLCCH quality over the last 160 ms period to be worse than a threshold Q out. Qout
is defined implicitly by the relevant tests in [2].
The UE shall subsequently resume the uplink transmission of the CCTrCH if the following criteria are fulfilled:
- The UE estimates the received PLCCH reception quality over the last 160 ms period to be better than a threshold
Qin. Qin is defined implicitly by the relevant tests in [2].
5.1.1.5 HS-SICH
The transmit power of the HS-SICH shall be set by the UE according to the procedures described below. In the case that
an ACK is being transmitted on the HS-SICH, the UE shall apply a power offset to the transmit power of the entire HS-
SICH. This power offset shall be signalled by higher layers.
On receipt of a TPC command in the HS-SCCH, the UE shall adjust the HS-SICH transmit power according to the
power control step size specified by higher layers. An example of SIR based UL power control is given in annex A5.
i. However, for the first HS-SICH transmission following the first detected HS-SCCH transmission, the UE
shall use open loop power control to set the HS-SICH transmit power for that transmission. In this case, the
transmission power for HS-SICH is set by higher layers based on open loop power control as described in
[15]
ii. When the transmission interval of HS-SICHs is less than a certain threshold，which is signalled by higher
layers, UE shall adjust the transmit power according to received TPC command during HS-SICH
transmission pause based on transmission power of last instance. If indicated by higher layers, UE should
take into account the pathloss compensation by means of beacon channel estimation in addition to the TPC
command when calculating HS-SICH transmit power.
iii. When the transmission interval of HS-SICHs is equal or larger than a certain threshold, for the next instance
of HS-SICH, UE shall use open loop power control described above for the initial transmission.
5.1.1.6 E-PUCH
The power of E-PUCH is set following the same principle used for DPCH/PUSCH in R4/5/6[15] and in 5.1.1.4, i.e., the
combination of open-loop power control and traditional closed-loop power control:
 the initial transmit power of E-PUCH is set based on an open-loop power control scheme, then
 the transmission power control transits into closed-loop power control using TPC commands carried on E-
AGCH for the scheduled transmission or on E-HICH for the non-scheduled transmission
The transmit power for E-PUCH set in the UE is calculated as follows:
… where:
3GPP
Release 8 36 3GPP TS 25.224 V8.0.0 (2008-03)
 PE  PUCH is the transmit power of the E-DCH physical channel E-PUCH.
 Pe  base is a closed-loop quantity maintained by the UE and NodeB, and which is incremented or decremented
by a value Δe-base upon each receipt of a TPC command on E-AGCH for scheduled transmission or on E-HICH
for non-scheduled transmission. On receipt of a TPC “up” command, Pe-base is incremented by Δe-base. On
receipt of a TPC “down” command, Pe-base is decremented by Δe-base. The TPC step size Δe-base is configured by
higher layers [15].
Pe  base  PRX des _ base  step *  TPC i  PRX des _ base  P TPC
i
…where, PRX des _ base is the reference Desired E-PUCH RX power signalled by RRC signalling
according to [15], which is set to the average value of the interference signal power level over the timeslots
configured for E-DCH use.
step is the power control step size Δe-base configured by higher layers, and TPCi is a
closed-loop control command.
 L is a pathloss term derived from beacon function physical channels. The same as that in 5.1.1.4, if indicated
as allowed by higher layers, the UE may optionally take into account pathloss modification which is
estimated from the most recently received beacon function physical channel transmission, in addition to the
TPC commands when calculating the transmit power.
  e is the gain factor for the selected E-TFC transport block size, the allocated E-PUCH physical resources,
and the Modulation type and HARQ power offset according to subclause 5.1.1.6.1.
Higher layers in the UE shall use the current calculated E-PUCH power in conjunction with the current absolute grant
(power) value in order to determine the set of E-TFC’s available.
UE maintains a closed-loop quantity Pe-base for both scheduled transmission and non-scheduled transmission. Pe  base
is incremented or decremented by a value Δe-base upon each receipt of a TPC command on E-AGCH and on E-HICH.
When following an extend pause in the reception of TPC commands on E-AGCH and on E-HICH, the UE shall set
Pe  base equal to the reference Desired E-PUCH RX power. When receipt of TPC commands on E-AGCH or on E-
HICH recommences, the TPC commands shall be used to modify Pe  base from its previously set value.
5.1.1.6.1 Gain Factors for E-PUCH

A beta factor shall be derived by the UE as a function of:
 the selected E-TFC transport block size
 the E-PUCH resource occupation in the E-DCH TTI
 the modulation type (QPSK/16-QAM)
 the HARQ power offset
Higher layers shall provide a mapping table containing a set of reference points, which defines the relationship between
the coderate of E-DCH transmission (e) and the relative reference power per resource unit (bl dB). The mapping table
is provided separately for each of QPSK and 16-QAM modulation.
The coderate of E-DCH transmission e for the selected E-TFC, physical resource allocation and modulation type is
defined as:
… in which Se is the transport block size of the selected E-TFC and Re is the number of physical channel bits output
from the physical channel mapping stage of E-DCH transport channel processing as described in [9].
3GPP
Release 8 37 3GPP TS 25.224 V8.0.0 (2008-03)
The maximum and minimum values of  are the maximum and minimum values of Reference Code Rate respectively,
which are signalled by higher layers for the appropriate modulation type [15], and are denoted max and min
respectively. For a given e there exist a 0 and a 1 such that:
 If min≤e<max
o 0 is the largest  signalled by higher layers for the appropriate modulation type and for which ≤e
o 1 is the smallest  signalled by higher layers for the appropriate modulation type and for which
>e
 Else
o If e<min then 0 = min and 1 is the smallest signalled  for which >min.
o If e≥max then 0 is the largest signalled  for which <max and 1 = max
Associated with 0 and 1 are the corresponding 0 and 1 which define the reference points signalled by higher layers.
The normalised (per-resource-unit) beta value for the selected E-TFC and E-PUCH resource set is denoted 0,e and is:
is a logarithmic value set as a function of the E-PUCH spreading factor (SFE-PUCH) according to table 2a.
Table 2a: Tabulated e values
SFE-PUCH (dB)
1 12
2 9
4 6
8 3
16 0
e is then derived as
Δharq is set by higher layers ( see [18] )，which is the HARQ profile power offset of the highest priority logical channels
mapped on the current E-DCH transmission.
5.1.1.7 E-RUCCH
The transmit power for the E-RUCCH is set by higher layers based on open loop power control as described
in [15].
5.1.2 Downlink Control

The total downlink transmission power at the Node B within one timeslot shall not exceed the Maximum Transmission
Power set by higher layer signalling.
5.1.2.1 P-CCPCH
Same as that of 3.84 Mcps TDD, cf.[4.2.3.1 P-CCPCH].
5.1.2.2 The power of the FPACH

The transmit power for the FPACH is set by the higher layer signalling [16].
3GPP
Release 8 38 3GPP TS 25.224 V8.0.0 (2008-03)
5.1.2.3 S-CCPCH, PICH

Same as that of 3.84 Mcps TDD, cf.[4.2.3.2 S-CCPCH , PICH].
5.1.2.3A MICH
Same as that of 3.84 Mcps TDD, cf.[4.2.3.2A MICH].
5.1.2.4 DPCH, PDSCH

The initial transmission power of the downlink Dedicated Physical Channel is signalled by higher layers. After the
initial transmission, the node B transits into closed-loop TPC. The UE shall generate TPC commands according to a
quality target set by higher layers in order to control the level of transmission power from the node B and send them in
the TPC field of associated uplink CCTrCHs (see [8] for a description of the mapping between UL associated TPC
symbols and DL controlled CCTrCH/timeslots) or in the Non-scheduled E-PUCH when the associated uplink CCTrCHs
do not exist. If the physical channel power should be increased, the TPC command is set to “up”, whereas if the power
should be reduced the command is set to “down”. A TPC command sent in an uplink CCTrCH or in the Non-scheduled
E-PUCH when the associated uplink CCTrCH does not exist controls all downlink DPCHs or PDSCHs in the
associated downlink CCTrCH and timeslot.
UTRAN may decide how to adjust the transmit power in response to the received TPC command
When TSTD is applied, the UE can use two consecutive measurements of the received SIR in two consecutive sub-
frames to generate the power control command. An example implementation of DL power control procedure for 1.28
Mcps TDD when TSTD is applied is given in Annex A.3.
The transmission power of one DPCH or PDSCH shall not exceed the limits set by higher layer signalling by means of
Maximum_DL_Power (dB) and Minimum_DL_Power (dB). The transmission power is defined as the average power
over one timeslot of the complex QPSK (or 8PSK respectively) symbols of a single DPCH or PDSCH before spreading
relative to the power of the P-CCPCH.
Each TPC command shall be based on all associated downlink transmissions since the previous related TPC command.
In the event of no associated downlink data being transmitted between two related TPC commands, the UTRAN should
ignore the resulting TPC command.

Same as that of 3.84 Mcps TDD, cf.[4.2.3.4.1 Out of synchronisation handling].
5.1.2.5 HS-PDSCH
The power control for HS-PDSCH for 1.28 Mcps TDD is the same as for 3.84 Mcps, see section 4.2.3.5
5.1.2.6 HS-SCCH
Higher layers shall indicate the maximum transmit power of the HS-SCCH. The Node-B shall not exceed this
maximum power when setting the HS-SCCH power.
The initial power of the HS-SCCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may
optionally power control the HS-SCCH. This may be done using TPC commands sent by the UE in the HS-SICH.
When the transmission interval of HS-SCCHs is more than or equal to a certain threshold, which is signalled by higher
layers, NodeB shall use initial transmit power for the next HS-SCCH transmission.
The UE shall set the TPC commands in the HS-SICH in order to control the transmit power of the HS-SCCH. The TPC
commands shall be set in order to meet the HS-SCCH target BLER.
The accuracy of the received HS-SCCH BLER estimate made by the UE may be enhanced by a suitable use of the
HCSN field received within the HS-SCCH itself [9]. This field shall initially be set to zero and shall be incremented by
the NodeB each time an HS-SCCH is transmitted to the UE.
3GPP
Release 8 39 3GPP TS 25.224 V8.0.0 (2008-03)
5.1.2.7 PLCCH
The initial transmission power of the downlink PLCCH is signalled by higher layers. After the initial transmission, the
transmission power of PLCCH is under the control of Node-B. The Node-B may optionally adjust the transmission
power of PLCCH according to the received TPC commands which are carried by the PLCCH-controlled UL
CCTrCH(s). The UE shall generate TPC commands according to a PLCCH quality target set by higher layers. If the
PLCCH power should be increased, the TPC command is set to “up”, whereas if the power should be reduced the
command is set to “down”. UTRAN may decide how to adjust the transmit power in response to the received TPC
commands. The average power of transmitted PLCCH symbols over one timeslot shall not exceed the limits set by
higher layers. The transmission power is defined as the average power over one timeslot of the complex QPSK symbols
of a single PLCCH before spreading relative to the power of the P-CCPCH.
5.1.2.8 E-AGCH
Higher layers shall indicate the maximum transmit power of the E-AGCH. The Node-B shall not exceed this maximum
power when setting the E-AGCH power.
The initial power of the E-AGCH is at the discretion of the Node-B. Following the initial transmission, the NodeB may
optionally power control the E-AGCH. This may be done using TPC commands sent by the UE in the scheduled E-
PUCH.
The UE shall set the TPC commands in the Scheduled E-PUCH in order to control the transmit power of the E-AGCH.
The TPC commands shall be set in order to meet the E-AGCH target BLER.
The accuracy of the received E-AGCH BLER estimate made by the UE shall be enhanced by a suitable use of the
ECSN field received within the E-AGCH itself [9]. This field shall initially be set to zero and shall be incremented by
the Node-B each time an E-AGCH is transmitted to the UE.
5.1.2.9 E-HICH
The power of the E- HICH is under the control of the Node B.
5.2 UL Synchronisation
5.2.1 General Description
Support of UL synchronization is mandatory for the UE.
5.2.1.1 Preparation of uplink synchronization (downlink synchronization)

When a UE is powered on, it first needs to establish the downlink synchronisation with the cell. Only after the UE has
established the downlink synchronisation, it shall start the uplink synchronisation procedure.
5.2.1.2 Establishment of uplink synchronization

The establishment of uplink synchronization is done during the random access procedure and involves the UpPCH and
the PRACH.
Although the UE can receive the downlink signal from the Node B, the distance to Node B is still uncertain. This would
lead to unsynchronised uplink transmission. Therefore, the first transmission in the uplink direction is performed in a
special time-slot UpPTS or other uplink access position indicated by UTRAN to reduce interference in the traffic time-
slots.
After the detection of the SYNC-UL sequence in the searching window, the Node B will evaluate the timing, and reply
by sending the adjustment information to the UE to modify its timing for next transmission. This is done with the
FPACH within the following 4 sub-frames. After sending the PRACH the uplink synchronization is established. The
uplink synchronisation procedure shall also be used for the re-establishment of the uplink synchronisation when uplink
is out of synchronisation.
3GPP
Release 8 40 3GPP TS 25.224 V8.0.0 (2008-03)
5.2.1.3 Maintenance of uplink synchronisation

Uplink synchronization is maintained in 1.28 Mcps TDD by sending the uplink advanced in time with respect to the
timing of the received downlink.
For the maintenance of the uplink synchronization, the midamble field of each uplink burst can be used.
In each uplink time slot the midamble for each UE is different. The Node B may estimate the timing by evaluating the
channel impulse response of each UE in the same time slot. Then, in the next available downlink time slot, the Node B
will signal Synchronisation Shift (SS) commands to enable the UE to properly adjust its Tx timing.
5.2.2 UpPCH
Open loop uplink synchronisation control is used for UpPCH.
The UE may estimate the propagation delay tp based upon the path loss using the received P-CCPCH and/or DwPCH
power.
The UpPCH is sent to the Node B advanced in time according to the timing of the received DwPCH. The time of the
beginning of the UpPCH TTX-UpPCH is given by:
TTX-UpPCH = TRX-DwPCH -2tp +12*16 TCTTX-UpPCH = TRX-DwPCH -2tp +12*16 TC＋nUpPCHShift*16Tc
nUpPCHShift =0..127，nUpPCHShift is indicated by higher layers
in multiple of 1/8 chips, where
TTX-UpPCH is the beginning time of UpPCH transmission with the UE’s timing,
TRX-DwPCH is the received beginning time of DwPCH with the UE’s timing,
2tp is the timing advance of the UpPCH default value is 48Tc.
5.2.3 PRACH
The Node B shall measure the received SYNC-UL timing deviation UpPCHPOS. UpPCHPOS is sent in the FPACH and is
represented as a 13 bit number (0-8191) being the multiple of 1/8 chips which is nearest to received position of the
UpPCH.
Time of the beginning of the PRACH TTX-PRACH is given by:
TTX-PRACH = TRX-PRACH –(UpPCHADV + UpPCHPOS – 8*16 TC)
TTX-PRACH is the beginning time of PRACH transmission with the UE’s timing,
TRX-PRACH is the beginning time of PRACH reception with the UE’s timing if the PRACH was a DL channel.
5.2.4 DPCH and PUSCH

The closed loop uplink synchronisation control uses layer 1 symbols (SS commands) for DPCH and PUSCH. After
establishment of the uplink synchronisation, NodeB and UE start to use the closed loop UL synchronisation control
procedure. This procedure is continuous during connected mode.
The Node B will continuously measure the timing of the UE and send the necessary synchronisation shift commands in
each sub-frame. The UE shall derive a single SS command separately for each controlled uplink timeslot by combining
all received SS commands that are related to the controlled time slot (cf. [8]) and that are received within the last up to
M sub-frames. The value of the “Uplink synchronisation frequency” M (1..8) is configured by higher layers.
When the combined SS command is judged as ‘down’, the UE transmit timing for the controlled UL timeslot shall be
delayed by one timing adjustment step of k/8 chips. When the command is judged as ‘up’, the UE transmit timing for
the controlled UL timeslot shall be advanced by one timing adjustment step of k/8 chips. When the command is judged
3GPP
Release 8 41 3GPP TS 25.224 V8.0.0 (2008-03)
as ‘do nothing’, the timing shall not be changed. The value of the “Uplink synchronisation step size” k (1..8) is
configured by higher layers.
The timing adjustment shall take place in each sub-frame satisfying the following equation:
where
SFN’ is the system frame number counting the sub-frames. The system frame number of the radio frames (SFN) can
be derived from SFN’ by
SFN=SFN’ div 2, where div is the remainder free division operation.
During a 1.28 Mcps TDD to 1.28 Mcps TDD hand-over the UE shall transmit in the new cell with timing advance TA
adjusted by the relative timing difference t between the new and the old cell if indicated by higher layers:
5.2.4.1 Out of synchronization handling

Same as that of 3,84 Mcps TDD, cf.[ 4.2.2.3.2 Out of synchronisation handling.]
5.2.5 HS-SICH
The initial transmit timing for the HS-SICH shall be taken from that of the associated uplink DPCH. The UE shall then
adjust the timing of the HS-SICH according to SS commands transmitted to it on the HS-SCCH. The step size for these
commands shall be signalled to the UE by higher layers. In the case that there is a gap of one or more subframes during
which no HS-SCCH transmissions, and thus no SS commands, are received by the UE, the UE shall adjust the timing of
the HS-SICH according to SS commands received on the associated downlink DPCH until such time as another HS-
SCCH transmission is received.
5.2.6 E-PUCH
Uplink synchronization control procedure for E-PUCH remains the same as that used for DPCH, cf. 5.2.4 DPCH and
PUSCH, using SS commands carried on E-AGCH with regard to scheduled transmissions or on E-HICH with regard to
non-scheduled transmissions.
If configured with DPCH, the timing of E-PUCH can be directly set to the timing of the DPCH. If configured with non-
scheduled transmission, the timing of scheduled E-PUCH can be set to the timing of the non-scheduled E-PUCH.
5.2.7 E-RUCCH
The Node B shall measure the received SYNC-UL timing deviation UpPCHPOS. UpPCHPOS is sent in the FPACH and is
represented as an 11 bit number (0-2047) being the multiple of 1/8 chips which is nearest to received position of the
UpPCH.
Time of the beginning of the E-RUCCH TTX-E-RUCCH is given by:
TTX-E-RUCCH = TRX-E-RUCCH –(UpPCHADV + UpPCHPOS – 8*16 TC)
TTX- E-RUCCH is the beginning time of E-RUCCH transmission with the UE’s timing,
TRX- E-RUCCH is the beginning time of E-RUCCH reception with the UE’s timing if the E-RUCCH was a DL channel,
UpPCHADV is the timing advance of the UpPCH.
3GPP
Release 8 42 3GPP TS 25.224 V8.0.0 (2008-03)

5.3.1 Cell search
During the initial cell search, the UE searches for a cell. It then determines the DwPTS synchronisation, scrambling
code and basic midamble code, control multi-frame synchronisation and then reads the BCH. How cell search is
typically done is described in Annex CA.
For MBSFN FACH, the downlink scrambling codes and basic midamble codes to be used for non-beacon timeslots are
signalled by higher layers.
5.3.2 DCH synchronization

The DPCH synchronisation is the same as that of 3,84 Mcps TDD, cf. [4.4.2 Dedicated channel synchronisation].

The DTX procedure shall be applied for CCTrCHs mapped to S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH,
if the total bit rate of the CCTrCH differs from the total channel bit rate of the physical channels allocated to this
CCTrCH.
Rate matching is used in order to fill resource units completely, that are only partially filled with data. In the case that
after rate matching and multiplexing no data at all is to be transmitted in a resource unit the complete resource unit shall
be discarded from transmission (DTX), unless a Special Burst is transmitted in the RU. This applies also to the case
where only one resource unit is allocated and no data has to be transmitted.
The special burst is transmitted in both consecutive subframes (subframe#1 and #2). SS Bits may be transmitted in
Special Bursts.for each CCTrCH mapped to UL DPCH, DL DPCH, PUSCH and PDSCH physical channels.
5.4.1 Description of Special Bursts

For S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, the Special Burst has the same timeslot format as the burst
used for data provided by higher layers. If the timeslot format contains a TFCI field, then the TFCI field shall be filled
with “0” bits. The Special Burst may also carry layer 1 control symbols such as TPC bits for the purposes of inner-loop
power control. The data portions of the Special Burst are filled with an arbitrary bit pattern.
For S-CCPCH, UL DPCH, DL DPCH, PUSCH and PDSCH, the transmission power of the special burst shall be the
same as that of the substituted physical channel of the CCTrCH. In the case of uplink physical channels where
autonomous spreading factor change by the UE is permitted by higher layers, the substituted physical channel is
considered to be that which would have been employed for the lowest non-zero rate TFC within the set of allowed
TFC’s and the transmission power of the Special Burst shall again correspond to that of the physical channel
substituted.
5.4.2 Use of Special Bursts during DTX

In the case that after link establishment there are no transport blocks provided for transmission by higher layers for a
given CCTrCH mapped to UL DPCH, DL DPCH, PUSCH or PDSCH physical channels, then a Special Burst shall be
transmitted in the first allocated frame of the transmission pause. If, including the first frame, there is a consecutive
period of Special Burst Period (SBP) frames without transport blocks provided by higher layers, then another special
burst shall be generated and transmitted at the next possible frame. This pattern shall be continued until transport blocks
are provided for the CCTrCH by the higher layers. SBP shall be provided by higher layers. The value of SBP shall be
independently specified for uplink and for downlink and shall be designated as
SBGP (special burst generation period) for uplink transmissions
3GPP
Release 8 43 3GPP TS 25.224 V8.0.0 (2008-03)
SBSP (special burst scheduling parameter) for downlink transmissions
The default value for both SBGP and SBSP shall be 8.
5.4.3 Use of Special Bursts for Initial Establishment / Reconfiguration

Upon initial establishment or reconfiguration for either 160 ms following detection of in-sync, or until the first transport
block is received from higher layers, both the UE and the Node B shall transmit the special burst for each CCTrCH
mapped to UL DPCH, DL DPCH, PUSCH and PDSCH physical channels.

Downlink Transmit diversity for PDSCH, DPCH, P-CCPCH, S-CCPCH, PICH, MICH, HS-SCCH, HS-PDSCH, E-
AGCH, E-HICH and DwPCH is optional in UTRAN. Its support is mandatory at the UE.

AGCH
Time Switched Transmit Diversity (TSTD) may be employed as transmit diversity scheme for downlink DPCH and
PDSCH. Closed loop Transmit Diversity may be employed as transmit diversity scheme for downlink DPCH, HS-
SCCH, HS-PDSCH and E-AGCH.
5.5.1.1 TSTD for PDSCH and DPCH

TSTD can be employed as transmit diversity scheme for PDSCH and downlink DPCH. An example for the transmitter
structure of the TSTD transmitter is shown in figure 6. Channel coding, rate matching, interleaving, bit-to-symbol
mapping, spreading, and scrambling are performed as in the non-diversity mode. Then the data is time multiplexed with
the midamble sequence. Then, after pulse shaping, modulation and amplification, DPCH and/or PDSCH is transmitted
from antenna 1 and antenna 2 alternately every sub-frame. Not all DPCHs and/or PDSCHs in the sub-frame need to be
transmitted on the same antenna and not all DPCHs and/or PDSCHs within a sub-frame have to use TSTD. Figure 7
shows an example for the antenna switching pattern for the transmission of DPCH/PDSCH for the case that all physical
channels are transmitted with TSTD and are using the same antenna in the sub-frame.
3GPP
Release 8 44 3GPP TS 25.224 V8.0.0 (2008-03)
Switching control ANT 1

cos w c
t
I
I
Midamble FIR
Q
ANT 2
TDM
I I
SPR SCR
DEMUX
Q
Data ENC INT FIR
Q Q
SPR SCR
-sin w c
t
Figure 6: Example for TSTD Transmitter structure for DPCH/PDSCH and P-CCPCH.
Sub-frame (5ms) Sub-frame (5ms)
ANT 1
ANT 2
12.5 micro sec 12.5 micro sec
Figure 7: Example for the antenna swithing pattern for TSTD transmission of DPCH/PDSCH and P-
CCPCH: all physical channels are transmitted with TSTD and are using the same antenna in the sub-
frame.
5.5.1.2 Closed Loop Tx Diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-
AGCH
The transmitter structure to support transmit diversity for DPCH, PDSCH, HS-SCCH, HS-PDSCH and E-AGCH
transmission is shown in figure 8. Channel coding, interleaving and spreading are done as in non-diversity mode. The
spread complex valued signal is fed to both TX antenna branches, and weighted with antenna specific weight factors w 1
and w2. The weight factors are complex valued signals (i.e., wi = ai + jbi ), in general. These weight factors are
calculated on a per slot and per user basis.
The weight factors are determined by the UTRAN.
3GPP
Release 8 45 3GPP TS 25.224 V8.0.0 (2008-03)
ANT1
FIR RF
Midamble w1
MUX
Data ENC INT SPR+SCR ANT2
FIR RF
w2
Uplink channel estimate

for DPCH, PDSCH, HS-SCCH, HS-PDSCH and E-AGCH transmission (UTRAN Access Point) in
1.28 Mcps TDD
5.5.2 Transmit Diversity for DwPCH

The transmitter structure to support transmit diversity for DwPCH transmission is shown in figure 9. DwPCH is
transmitted from antenna 1 and antenna 2 alternatively.
Ant 1
FIR RF
DwP CH
Ant 2
Switching Control
FIR RF

for DwPCH transmission (UTRAN Access Point) in 1.28 Mcps TDD
5.5.3 Transmit Diversity for P-CCPCH

TSTD or Space Code Transmit Diversity (SCTD) can be employed as transmit diversity scheme for the Primary
Common Control Physical Channel (P-CCPCH)
5.5.3.1 TSTD Transmission Scheme for P-CCPCH

A block diagram of an example of a TSTD transmitter is shown in figure 6. Channel coding, rate matching,
interleaving, bit-to-symbol mapping, spreading, and scrambling are performed as in the non-diversity mode. Then the
data is time multiplexed with the midamble sequence. Then, after pulse shaping and modulation and amplification, P-
CCPCH is transmitted from antenna 1 and antenna 2 alternately every sub-frame. If there is a DPCH that uses TSTD,
TSTD is also applied to P-CCPCH. An example of the antenna-switching pattern is shown in figure 7. If TSTD is
applied to P-CCPCH, it shall also be applied to other beacon channels.
5.5.4 SCTD Transmission Scheme for Beacon Channels

The use of SCTD will be indicated by higher layers. If SCTD is active within a cell, SCTD shall be applied to any
beacon channel. When beacon channel is used on dedicated MBSFN frequency, SCTD shall not be applied.
3GPP
Release 8 46 3GPP TS 25.224 V8.0.0 (2008-03)
The SCTD open loop downlink transmit diversity scheme for beacon channels is shown in figure 10, exemplary for the
P-CCPCH. Channel coding, rate matching, interleaving and bit-to-symbol mapping are performed as in the non-
( k 1)
diversity mode. In TxDiversity mode the beacon channel that is allocated to code c16 is spread with the
( k 1) ( k 3)
channelisation codes c16 and c16 and scrambled with the cell specific scrambling code. The beacon channel that is
( k 2) ( k 2) ( k 4)
allocated to code c16 is spread with the channelisation codes c16 and c16 and scrambled with the cell specific
( k 3) ( k 4)
scrambling code. The spread sequences on code c16 and code c16 are then transmitted on the diversity antenna.
The power applied to each antenna shall be equal.
The use of SCTD will be indicated by higher layers.
Midamble m (2)
Spreading Code * s (4) MUX
X
Tx Antenna 2
Spreading Code * s (3) MUX +
(2)
Midamble m
Midamble m (1)
Spreading Code * s (2) MUX
P-CCPCH2
X
P-CCPCH1
X
Tx Antenna 1
Spreading Code *
s (1) MUX +
Midamble m (1)
(k) (k)
* Spreading by s means channelisation by c and cell specific scrambling
Figure 10: Block Diagram of the transmitter (SCTD) in 1.28 Mcps TDD, exemplary for the P-CCPCH
5.6 Random Access Procedure

5.6.1 Definitions
FPACHi : : The ith FPACH number parameter i indicates the position of the FPACH, the first position is corresponding
to the first instance defined in IE “PRACH system information list)” (see [15]).
Li : Length of RACH transport blocks associated to FPACHi in sub-frames
NRACHi : The number of PRACHs associated to the ith FPACH
3GPP
Release 8 47 3GPP TS 25.224 V8.0.0 (2008-03)
nRACHi : The number of a PRACH associated to the ith FPACH ranging from 0 to NRACHi-1
M : Maximum number transmissions in the UpPCH
WT : Maximum number of sub-frames to wait for the network acknowledgement to a sent signature
SFN’ : The sub-frame number counting the sub-frames. At the beginning of the frame with the system frame
number SFN=0 the sub-frame number is set to zero.
5.6.1A UpPCH sub-channel

In order to separate different ASCs, UpPCH has N sub-channels associated with it (numbered from 0 to N-1). N may be
assigned the value 1,2,4, or 8 by higher layer signaling.
- Sub-channel i for UpPCH is defined as the UpPTS timeslot in the sub_frame where SFN’ mod N = i.
Where SFN’: the sub-frame number counting the sub-frames. At the beginning of the frame with the system frame
number SFN=0 the sub-frame number is set to zero.
The following figure illustrates the eight possible sub channels for the case, N=8.
Figure 10A : Example of UpPCH subchannels
5.6.2 Preparation of random access

When the UE is in idle mode, it will keep the downlink synchronisation and read the system information. From the used
SYNC-DL code in DwPCH, the UE will get the code set of 8 SYNC-UL codes (signatures) assigned to UpPCH for
random access.
The description (codes, spreading factor, midambles, time slots) of the P-RACH, FPACH, S-CCPCH (carrying the
FACH transport channel) channel; mapping relation of RACH and FPACH; ASC (available SYNC-UL sequences and
available sub-channels) sets for each RACH are broadcast on the BCH.
3GPP
Release 8 48 3GPP TS 25.224 V8.0.0 (2008-03)
Thus, when sending a SYNC-UL sequence, the UE knows which FPACH resource, P-RACH resources and S-CCPCH
resources will be used for the access.
The physical random access procedure described in this sub-clause is initiated upon request from the MAC sub-layer
(see [18] and [19]).
Before the physical random-access procedure can be initiated, Layer 1 shall receive the following information by a
CPHY-TrCH-Config-REQ from the RRC layer:
- The uplink access position by higher layers.
- The association between which signatures and which FPACHs; which FPACHs and which PRACHs; which
PRACHs and which S-CCPCHs; including the parameter values for each listed physical channel.
- The length Li of a RACH message associated to FPACHi can be configured to be either 1 or 2 or 4 sub-frames
corresponding to a length in time of either 5 ms or 10 ms or 20 ms.
NOTE 1: NRACHi PRACHs can be associated with to FPACHi. The maximum allowed
NRACHi is Li.
- The available UpPCH sub-channels for each Access Service Class (ASC);
- The set of Transport Format parameters for the PRACH message;
- The "M" maximum number transmissions in the UpPCH;
- The "WT" maximum number of sub-frames to wait for the network acknowledgement to a sent signature; (1..4)
the maximum value supported by Layer 1 is 4 sub-frames.
- The initial signature power "Signature_Initial_Power";
- The power-ramping factor Power Ramp Step [Integer];
The above parameters may be updated from higher layers before each physical random access procedure is initiated.
At each initiation of the physical random access procedure, Layer 1 shall receive the following information from the
higher layers (MAC):
- The Transport Format to be used for the specific PRACH message;
- The ASC for the specific Random Access procedure;
- The data to be transmitted (Transport Block Set).
- The type of random access
5.6.3 Random access procedure

The physical random-access procedure shall be performed as follows:
UE side:
1 Set the Signature Re-Transmission Counter to M.
2 Set the Signature transmission power to Signature_Initial_Power.
3 Based on the type of random access and the transport format indicated by MAC layer, an E-RUCCH or unique
RACH used for the radio access is chosen, and then randomly select one UpPCH sub-channel and one signature
respectively from the available ones for the given ASC. The random function shall be such that each of the
allowed selections is chosen with equal probability.
4 Transmit the signature at UpPCH or other uplink access position indicated by higher layers using the selected
UpPCH sub-channel at the signature transmission power. In the case that the Commanded Signature
transmission Power exceeds the maximum allowed value, set the Signature transmission Power to the maximum
allowed power.
3GPP
Release 8 49 3GPP TS 25.224 V8.0.0 (2008-03)
5 After sending a signature, listen to the relevant FPACH for the next WT sub-frames to get the network
acknowledgement. The UE will read the FPACHi associated to the transmitted UpPCH only in the sub-frames
fulfilling the following relation:
(SFN’ mod Li)=nRACHi ; nRACHi=0,…, NRACHi-1, Here, FPACH to which UE should listen is decided according to
the following formula:
FPACHi= N mod M,
Where, N denotes the signature number (0..7) and M denotes the maximum number of FPACHs that defined
in the cell.
6 In case no valid answer is detected in the due time: Increase the Signature transmission power by P0 = Power
Ramp Step [dB], decrease the Signature Re-transmission counter by one and if it is still greater than 0, then
repeat from step 3; else report a random access failure to the MAC sub-layer.
7 In case a valid answer is detected in the due time
a) set the timing and power level values according to the indication received by the network in the FPACH i
b) send at the sub-frame coming 2 sub-frames after the one carrying the signature acknowledgement, the RACH
message on the relevant PRACH. In case Li is bigger than one and the sub-frame number of the
acknowledgement is odd the UE will wait one more sub-frame. The relevant PRACH is the n RACHi th PRACH
associated to the FPACHi if the following equation ifs fulfilled:
(SFN’ mod Li)=nRACHi ;
Here SFN’ is the sub-frame number of the arrival of the acknowledgement.
Both on the UpPCH and on the PRACH, the transmit power level shall never exceed the indicated value signalled by
the network.
Network side:
- The node B will transmit the FPACHi associated with the received UpPCH only in the sub-frames fulfilling the
following relation:
(SFN’ mod L)=nRACHi ; nRACHi=0,…, NRACHi-1,
Here, FPACH number i is selected according to the following formula based on acknowledged signature:
FPACHi= N mod M,
Where, N denotes the signature number (0..7) and M denotes the maximum number of FPACH that defined in
the cell.
- The Node B will not acknowledge UpPCHs transmitted more than WT sub-frames ago
At the reception of a valid signature:
- Measure the timing deviation with respect to the reference time Tref of the received first path in time from the
UpPCH and acknowledge the detected signature sending the FPACH burst on the relevant FPACH.
For examples on the random access procedure refer to Annex CB.
5.6.3.1 The use and generation of the information fields transmitted in the FPACH
The Fast Physical Access CHannel (FPACH) is used by the Node B to carry, in a single burst, the acknowledgement of
a detected signature with timing and power level adjustment indication to a user equipment.
The length and coding of the information fields is explained in TS25.221 sub-clause 5A.3.3.1 .
5.6.3.1.1 Signature Reference Number

The Signature Reference Number field contains the number of the acknowledged signature. The user equipment shall
use this information to verify whether it is the recipient of the FPACH message.
3GPP
Release 8 50 3GPP TS 25.224 V8.0.0 (2008-03)
5.6.3.1.2 Relative Sub-Frame Number

The Relative Sub-Frame Number field indicates the current sub-frame number with respect to the sub-frame at which
the acknowledged signature has been detected.
The user equipment shall use this information to verify whether it is the recipient of the FPACH message.
5.6.3.1.3 Received starting position of the UpPCH (UpPCHPOS)

The received starting position of the UpPCH (UpPCHPOS) field indirectly indicates to the user equipment the timing
adjustment it has to implement for the following transmission to the network. The node B computes the proper value for
this parameter according to the following rules: UpPCHPOS = UpPCHRxpath - UpPCHTS
where
UpPCHRxpath: time of the reception in the Node B of the SYNC-UL to be used in the uplink synchronization process
UpPCHTS: time instance 128 chips prior to the start of the UpPCH according to the Node B internal timing
This information shall be used by the UE to adjust its timing when accessing the network, as described in section [5.2
'Uplink Synchronisation'] .
5.6.3.1.4 Transmit Power Level Command for the RACH message

This field indicates to the user equipment the power level to use for the RACH message transmission on the FPACH
associated P-RACH.
The network may set this value based on the measured interference level (I) (in dBm) on the specific PRACH and on
the desired signal to interference ratio (SIR) (in dB) on this channel as follows:
Transmit Power Level Command for the PRACH(PRXPRACH,des)
PRXPRACH,des is the desired receive power level on the PRACH.
The UE shall add to this value the estimated path-loss to compute the power level to transmit for the PRACH.
5.6.3a E-RUCCH procedure

Requests for the transmission of an E-RUCCH are controlled by higher layers [18].
The available eight SYNC_UL signatures in a cell is devided into two subsets, one for the access of RACH information
and the other for the access of E-RUCCH information.
When a Node B detects a SYNC_UL signature and acknowledges it on the related FPACH, it should do some
recordings, including the FPACH channel number, the sub-frame on which the acknowledgement is sent and the
SYNC_UL signature number. When a PRACH or E-RUCCH comes from a UE, the Node B should derive the related
FPACH and the sub-frame on which the acknowledgement was sent for the UE and find the right record. The signature
number in the record can help the Node B know the access type.
Random access procedure for enhanced uplink is basically same as random access procedure in subclause 5.6.3, only
adding some new definitions.
LiE is the Length of E-RUCCH information transport blocks associated to FPACHi in sub-frames.
NRACHi is the number of PRACHs associated to the ith FPACH.
NE-RUCCHi is the number of E-RUCCHs associated to the ith FPACH and NE-RUCCHi equals to .
When SF of PRACH code equals to 16, LiE will be 2, otherwise LiE will be 1。
When SF of PRACH code equals to 4, SF of E-RUCCH will be 8, otherwise E-RUCCHs has the same SF with
PRACH.
3GPP
Release 8 51 3GPP TS 25.224 V8.0.0 (2008-03)
When nE-RUCCHi equals to nRACHi, E-RUCCH will share the same code resource with PRACH. And when SF of PRACH
code equals to 4, the code resource assigned to PRACH including two codes (code i and code i+1) of SF 8, E-RUCCH
can use the ith code of SF 8.
If FPACHi sent an acknowledgement for E-RUCCH information, the sub-frames on which an acknowledgement is
sent on FPACHi is fulfilling the following relation:
(SFN’ mod LiE)=nE-RUCCHi ; nE-RUCCHi=0,…, NE-RUCCHi-1,
Where, SFN’ is the sub-frame number of the acknowledgement on FPACH
Accordingly, the code resource assigned to PRACH may be used by PRACH or E-RUCCH, we should make two
prescript avoiding the collision between PRACH and E-RUCCH.
When Node B sent a FPACHi for in sub frame K，Node B could not send a FPACHi for
before sub frame K+Li；
When Node B sent a FPACHi for in sub frame K，Node B could not send a FPACHi for
before sub frame K+LiE。
The interval between the acknowledgement on FPACH and transmission of E-RUCCH is fixed for a UE. The UE will
send at the sub-frame coming 2 sub-frames after the one carrying the signature acknowledgement. In case L iE is bigger
than one and the sub-frame number of the acknowledgement is odd the UE will wait one more sub-frame.
The transmission power and the transmission timing are set according to subclause 5.1.1.7 and 5.2.7 respectively.
5.6.4 Random access collision

When a collision is very likely or in bad propagation environment, the Node B does not transmit the FPACH or cannot
receive the SYNC-UL. In this case, the UE will not get any response from the Node B. Thus the UE will have to adjust
its Tx time and Tx power level based on a new measurement and send a SYNC-UL again after a random delay.
Note that at each (re-)transmission, the SYNC-UL sequence and the UpPCH sub-channel will be randomly selected
again by the UE.
Note: Due to the two-step approach a collision most likely happens on the UpPCH. The resources allocated to
PRACH and E-RUCCH are virtually collision free. This two-step approach will guarantee that the RACH
resources can be handled with conventional traffic on the same UL time slots.
5.7 Node B Synchronisation Procedure over the Air

An option exists to use the regular DwPCH transmissions to achieve and maintain Node B synchronisation [20]. This
optional procedure is based on measurements of DwPCHs from neighbouring cells according to an RNC schedule. The
timing offset measurements are reported back to the RNC for processing. The RNC generates cell timing updates that
are transmitted to the Node Bs and cells for implementation (common with the 3.84 Mcps TDD option). Alternatively
the RNC may indicate that the NodeB shall autonomously adjust the cell timings. Two distinct phases can be
distinguished for Node B synchronisation over the air, with a potential additional sub-phase involving late entrant cells.
5.7.1 Initial Synchronisation

Common with 3.84 Mcps TDD, see [4.9.2 Initial Synchronisation], however, the regular DwPCHs are used as cell sync
bursts.
5.7.2 Steady-State Phase

Common with 3.84 Mcps TDD, see [4.9.3 Steady-State Phase], however, the regular DwPCHs are used as cell sync
bursts. If the NodeB adjusts the cell timings autonomously, it shall take into account the propagation delay, signaled by
the RNC.
3GPP
Release 8 52 3GPP TS 25.224 V8.0.0 (2008-03)
5.7.3 Late entrant cells

A procedure that may be used for introducing new cells into an already synchronised RNS involves the continuous
measurement of the DwPCHs of the neighbouring cells by the late entrant cell. The RNC may use this information to
adjust the late entrant cell sufficiently to allow the cell to enter steady state phase.

5.8.1 General
To support time difference measurements for location services, idle periods can be created in the downlink (hence the
name IPDL) during which time transmission of the DwPCH from a Node B is temporarily ceased. During these idle
periods the visibility of neighbour cells from the UE is improved.
The idle periods are arranged in a determined pattern according to higher layer parameters. An idle period has a
duration of one DwPTS.
In general there are two modes for these idle periods:
- Continuous mode, and
- Burst mode
In continuous mode, the idle periods are active all the time. In burst mode the idle periods are arranged in bursts where
each burst contains enough idle periods to allow a UE to make sufficient measurements for its location to be calculated.
The bursts are separated by a period where no idle periods occur. The time difference measurements can be performed
on any channel.
5.8.2 Parameters of IPDL

The following parameters are signalled to the UE via higher layers:
IP_Status: This is a logic value that indicates if the idle periods are arranged in continuous or burst mode.
IP_Spacing: The number of 10 ms radio frames between the start of a radio frame that contains an idle period and
the next radio frame that contains the next idle period.
IP_Start: The number of the first frame with idle periods. In case of continuous mode IP_Start is the SFN of the
first frame with idle periods and in case of burst mode IP_Start defines the number of frames after
Burst_Start with the first frame with idle periods.
IP_Sub: Indicates whether the idle period is to occur in the odd, the even or both the odd and even 5 ms sub-
frames of the 10 ms idle frame.
Additionally in the case of burst mode operation the following parameters are also communicated to the UE.
Burst_Start: Specifies the start of the first burst of idle periods. 256Burst_Start is the SFN where the first burst of
idle periods starts.
Burst_Length: The number of idle periods in a burst of idle periods.
Burst_Freq: Specifies the time between the start of a burst and the start of the next burst. 256Burst_Freq is the
number of radio frames between the start of a burst and the start of the next burst.
5.8.3 Calculation of idle period position

In burst mode, burst #0 starts in the radio frame with SFN = 256Burst_Start. Burst #n starts in the radio frame with
SFN = 256Burst_Start + n256Burst_Freq ( n = 0,1,2, …). The sequence of bursts according to this formula
continues up to and including the radio frame with SFN = 4095. At the start of the radio frame with SFN = 0, the burst
sequence is terminated (no idle periods are generated) and at SFN = 256Burst_Start the burst sequence is restarted
with burst #0 followed by burst #1 etc., as described above.
3GPP
Release 8 53 3GPP TS 25.224 V8.0.0 (2008-03)
Continuous mode is equivalent to burst mode, with only one burst spanning the whole SFN cycle of 4096 radio frames,
this burst starts in the radio frame with SFN = 0. In case of continuous mode the parameter IP_Start defines the first
frame with idle periods.
The DwPCH, that has to be idle, is defined by two values: IP_Frame(x) and IP_Sub. IP_Frame(x) defines the xth frame
within a burst in which subframe with the number IP_Sub has to be switched off.
The actual frame with idle periods within a burst is calculated as follows:
IP_Frame(x) = IP_Start + (x-1)  IP_Spacing with x = 1, 2, 3, ....
Figure 11 below illustrates the idle periods for the burst mode which shows the case that both subframes within each
frame have DwPTS as an idle period.
Figure 11: Idle periods of burst mode for 1.28Mcps TDD

resources by higher layers. If UE supports multi-carrier HS-DSCH reception, higher layers may select multiple carriers
to transfer data. Carriers selection may be based on CQI reports from the UE. If UE supports multi-carrier HS-DSCH
transmission, UE shall report the CQI information of every carrier via HS-SICH.
Node B procedure:
1) The NodeB transmits HS-SCCH carrying a UE identity identifying the UE to which HS-DSCH TTI si to be
granted. In case of HS-DSCH transmissions in consecutive TTIs to the same UE, the same HS-SCCH shall be
used for associated signalling. If UE supports multi-carrier HS-DSCH reception, above HS-SCCH detection
procedure applied on each independent carriers.
2) The NodeB transmits HS-DSCH to the UE using the grant indicated in the HS-SCCH. If UE supports multi-
carrier HS-DSCH reception, the mapping relation between HS-SCCH and its associated HS-DSCH is set by
higher layers.
higher layers. If UE supports multi-carrier HS-DSCH reception, the mapping relation between HS-SICH and its
associated HS-DSCH is set by higher layers.
UE procedure:
3GPP
Release 8 54 3GPP TS 25.224 V8.0.0 (2008-03)
signalled to it by higher layers. The information carried on the HS-SCCH is described in [8]. If UE supports
multi-carrier HS-DSCH reception, the monitoring HS-SCCH set is signalled by higher layers.
by the HS-SCCH. If UE supports multi-carrier HS-DSCH reception, UE may acquire HS-PDSCH resource
allocation information of each carrier according to the associated HS-SCCHs, the mapping relation between
every HS-SCCH and its associated HS-PDSCH is signalled by higher layers. In the case that a HS-SCCH is
identified to be incorrect, the UE shall discard the data on the HS-SCCH and return to monitoring.
the associated HS-SICH, along with the most recently derived CQI. If UE supports multi-carrier HS-DSCH
reception, the CQI and ACK/NACK of every carrier are transferred via individual HS-SICH.
beacon channel.
then:

The HS-DSCH channel quality indication procedure is same as that of 3.84Mcps TDD, cf. 4.11.2 HS-DSCH Channel
QualityIndication Procedure.
5.9.3 HS-SCCH monitoring procedure

For 1.28Mcps TDD, in a multi-frequency HS-DSCH cell, a UE divides its HS-SCCH set into one or more HS-SCCH
subsets; in each HS-SCCH subset all HS-SCCHs are associated with the same frequency’s HS-PDSCH. When indicated
by higher layers, the UE shall start monitoring all HS-SCCHs in all HS-SCCH subsets to acquire the configuration
information of HS-PDSCHs. In the case that one HS-SCCH is detected carrying its UE identity, the UE shall skip
monitoring the remaining HS-SCCHs in this HS-SCCH subset, and restrict its monitoring only to previously detected
HS-SCCH in the following TTIs. The UE shall set all HS-SCCHs carrying its UE identity in all HS-SCCH subsets into
an active set, and set all HS-SCCH subsets in which no HS-SCCH carries its UE identity into a remaining set.
In the case that the multi-carrier number (as described in [15]) is not configured by high layers, a UE shall always
monitor all HS-SCCH subsets. Otherwise, the UE may skip monitoring remaining HS-SCCH subsets when the number
of HS-SCCHs carrying its UE identity, i.e. the number of HS-SCCHs in the active set, is equal to the configured value.
During the following TTIs, the UE shall update and maintain the active set and the remaining set. If one or more HS-
SCCHs in the active set do not carry its UE identity, the UE shall remove them from the active set and set their
corresponding HS-SCCH subsets into remaining set. Meanwhile, if one or more HS-SCCHs in remaining sets are
3GPP
Release 8 55 3GPP TS 25.224 V8.0.0 (2008-03)
detected carrying its UE identity, the UE shall set these founded HS-SCCHs into the active set and remove their
corresponding HS-SCCH subsets from the remaining set.

The macro-diversity procedure is the same as that of 3.84 Mcps TDD, cf. 4.12 Macro-diversity procedure.
5.11 E-DCH Procedure

The physical layer in the UE shall detect ACK or NACK contained within the E-HICH. Which E-HICH is associated
with the corresponding E-DCH transmission is defined in [8].

The UE shall be capable of measuring the P-CCPCH RSCP of the serving cell and of intra-frequency neighbour cells in
accordance with [11]. The P-CCPCH transmit power (Pref) of the serving cell and of each intra-frequency neighbour
cell in the monitored neighbour cell list shall be signalled by higher layers to the UE in order that the UE may estimate
the mean pathloss to the serving cell (Lserv) and to each of the N neighbour cells in the monitored neighbour cell list (L1,
L2, … LN).
Higher layers shall configure the UE to use SNPL reporting type 1 or SNPL reporting type 2. In accordance with the
SNPL reporting type, the UE shall be capable of forming a metric corresponding to:
The metric  shall be converted into a logarithmic (dB) value Q and shall be mapped to a Serving and Neighbour Cell
Pathloss (SNPL) index according to table 2b. The SNPL index is supplied to and used by higher layers (see [18]).
Table 2b: SNPL mapping
Q = 10*log10(f) SNPL index

Q <-10 0
-10 ≤ Q < -8 1
-8≤ Q < -6 2
-6≤ Q < -5 3
-5≤ Q < -4 4
-4 ≤ Q < -3 5
-3 ≤ Q < -2 6
-2 ≤ Q < -1 7
-1 ≤ Q < 0 8
0≤Q<1 9
1≤Q<2 10
2≤Q<3 11
3≤Q<4 12
4≤Q<5 13
5≤Q<6 14
6≤Q<7 15
7≤Q<8 16
8≤Q<9 17
9 ≤ Q < 10 18
3GPP
Release 8 56 3GPP TS 25.224 V8.0.0 (2008-03)
10 ≤ Q < 11 19
11 ≤ Q < 12 20
12 ≤ Q < 13 21
13 ≤ Q < 14 22
14 ≤ Q < 15 23
15 ≤ Q < 16 24
16 ≤ Q < 17 25
17 ≤ Q < 18 26
18 ≤ Q < 20 27
20 ≤ Q < 22 28
22 ≤ Q < 24 29
24 ≤ Q < 26 30
26 ≤ Q 31
If the higher layer signalling information regarding the required P-CCPCH reference powers is not available, the UE
shall return an SNPL index value of 9.

The transmit power control procedure is identical to that of the 3.84Mcps TDD option [clause 4.2] with the exception
that the tablulated e values of subclause 4.2.2.4.1 for uplink power control of E-PUCH are substituted with the
following values of table 3.
Table 3: Tabulated e values for the 7.68Mcps option
SFE-PUCH (dB)
1 15
2 12
4 9
8 6
16 3
32 0
6.2 Timing Advance

UTRAN may adjust the UE transmission timing with timing advance. The initial value for timing advance (TA phys) will
be determined in the UTRAN by measurement of the timing of the PRACH or E-RUCCH. The required timing advance
will be represented as a 9 bit number (0-511) 'UL Timing Advance' TAul, being the multiplier of 4 chips which is
nearest to the required timing advance (i.e. TAphys = TAul  4 chips).
When Timing Advance is used the UTRAN will continuously measure the timing of a transmission from the UE and
send the necessary timing advance value. On receipt of this value the UE shall adjust the timing of its transmissions
accordingly in steps of ±4chips. The transmission of TA values is done by means of higher layer messages. Upon
receiving the TA command the UE shall adjust its transmission timing according to the timing advance command at the
frame number specified by higher layer signaling. The UE is signaled the TA value in advance of the specified frame
activation time to allow for local processing of the command and application of the TA adjustment on the specified
frame. Node-B is also signaled the TA value and radio frame number that the TA adjustment is expected.to take place.
If TA is enabled by higher layers, after handover the UE shall transmit in the new cell with timing advance TA adjusted
by the relative timing difference t between the new and the old cell:
3GPP
Release 8 57 3GPP TS 25.224 V8.0.0 (2008-03)

The synchronisation procedures are identical to those of the 3.84Mcps TDD option [clause 4.4].

The discontinuous transmission procedure is identical to that of the 3.84Mcps TDD option [clause 4.5].

Downlink transmit diversity for PDSCH, DPCH, P-CCPCH, S-CCPCH, PICH, MICH, HS-SCCH, HS-PDSCH, E-
AGCH, E-HICH and SCH is optional in UTRAN. Its support is mandatory at the UE.

AGCH
Transmit diversity for PDSCH, DPCH, HS-SCCH, HS-PDSCH and E-AGCH is identical to the 3.84Mcps TDD option
[clause 4.6.1].
6.5.2 Transmit Diversity for SCH and S-CCPCH

Transmit diversity for SCH and S-CCPCH is identical to the 3.84Mcps TDD option [clause 4.6.2].
6.5.3 Transmit Diversity for Beacon Channels

When beacon channels use burst type 4, SCTD shall not be applied.
When beacon channels use burst type 1, Space Code Transmit Diversity (SCTD) for beacon channels may be employed
optionally in the UTRAN. The support is mandatory in the UE except for the case where the UE only supports burst
type 4. The use of SCTD will be indicated by higher layers. If SCTD is active within a cell:
- SCTD shall be applied to any beacon channel, and
- the maximum number KCell of midambles for burst type 1 that are supported in this cell may be 8 or 16, see [8]. The
case of KCell = 4 midambles is not allowed for this burst type.
6.5.3.1 SCTD Transmission Scheme

The open loop downlink transmit diversity scheme for beacon channels is shown in figure 12. Channel coding, rate
matching, interleaving and bit-to-symbol mapping are performed as in the non-diversity mode. In Space Code Transmit
Diversity mode the data sequence is spread with the channelisation codes and and scrambled with the cell
specific scrambling code. The spread sequence on code is then transmitted on the diversity antenna. The power
applied to each antenna shall be equal.
3GPP
Release 8 58 3GPP TS 25.224 V8.0.0 (2008-03)
Midamble 1 Tx.
M
Antenna 1
U
X
SPR-SCR c(1)
Encoded and Interleaved Data

Symbols, 2 data fields
SPR-SCR c(2) Tx.
M Antenna 2
U
X
Midamble 2
Figure 12: Block Diagram of the transmitter SCTD
6.6 Random access procedure

Retransmission on the RACH in case of failed transmission (e.g. due to a collision) is controlled by higher layers. Thus,
the backoff algorithm and associated handling of timers is not described here. The definition of the RACH in terms of
PRACH Access Service Classes is broadcast on the BCH in each cell. Parameters for common physical channel uplink
outer loop power control are also broadcast on the BCH in each cell. The UE needs to decode this information prior to
transmission on the RACH.
6.6.1 Physical random access procedure

The physical random access procedure is identical to that of the 3.84Mcps TDD option [clause 4.7.1].
6.6a E-RUCCH transmission procedure

The E-RUCCH transmission procedure is identical to that of the 3.84Mcps TDD option [clause 4.7a]
6.7 DSCH procedure

Higher layer signalling is used to indicate to the UE the need for PDSCH detection.

The IPDL procedure is identical to that of the 3.84Mcps TDD option [clause 4.10].

resources by higher layers. Selection of these parameters may be based on CQI reports from the UE.
Node B procedure:
3GPP
Release 8 59 3GPP TS 25.224 V8.0.0 (2008-03)
1) The NodeB shall transmit HS-SCCH carrying a UE identity identifying the UE for which HS-DSCH TTI
allocation has been given. In the case of HS-DSCH transmissions in consecutive TTIs to the same UE, the same
HS-SCCH shall be used for associated signalling.
2) The NodeB transmits HS-DSCH to the UE using the resources indicated in the HS-SCCH.
higher layers.
UE procedure:
signalled to it by higher layers. The information carried on the HS-SCCH is described in [8].
by the HS-SCCH. In the case that a HS-SCCH is identified to be incorrect, the UE shall discard the data on the
HS-SCCH and return to monitoring.
the associated HS-SICH, along with the most recently derived CQI.
beacon channel.
then:

The HS-DSCH channel quality indication procedure is identical to that of the 3.84Mcps TDD option [clause 4.11.2].

The macrodiversity procedure is identical to that of the 3.84Mcps TDD option [clause 4.12].
6.11 E-DCH related procedures

The procedure for detection of ACK/NACK is identical to that of the 3.84Mcps option [subclause 4.13.1]
3GPP
Release 8 60 3GPP TS 25.224 V8.0.0 (2008-03)

The procedure for serving and neighbour cell metric derivation is identical to that of the 3.84Mcps option [subclause
4.13.2]
6.11.3 Channelisation code hopping procedure for E-PUCH

For the 7.68Mcps option, the procedure for channelisation code hopping on E-PUCH is identical to that of the
3.84Mcps option [subclause 4.13.3] with two exceptions:
i) the code hopping index parameter is calculated as:
ii) the code hopping index parameter sequences of table 1c are substituted for the values of table 4 below.
Table 4: Hopping index parameter sequences for the 7.68Mcps options
Hop index hi
CRRI
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
SF32
1 31 1 17 9 25 5 21 13 29 3 19 11 27 7 23 15 31 2 18 10 26 6 22 14 30 4 20 12 28 8 24 16 32
2 32 2 18 10 26 6 22 14 30 4 20 12 28 8 24 16 32 1 17 9 25 5 21 13 29 3 19 11 27 7 23 15 31
3 33 3 19 11 27 7 23 15 31 1 17 9 25 5 21 13 29 4 20 12 28 8 24 16 32 2 18 10 26 6 22 14 30
4 34 4 20 12 28 8 24 16 32 2 18 10 26 6 22 14 30 3 19 11 27 7 23 15 31 1 17 9 25 5 21 13 29
5 35 5 21 13 29 1 17 9 25 7 23 15 31 3 19 11 27 6 22 14 30 2 18 10 26 8 24 16 32 4 20 12 28
6 36 6 22 14 30 2 18 10 26 8 24 16 32 4 20 12 28 5 21 13 29 1 17 9 25 7 23 15 31 3 19 11 27
7 37 7 23 15 31 3 19 11 27 5 21 13 29 1 17 9 25 8 24 16 32 4 20 12 28 6 22 14 30 2 18 10 26
8 38 8 24 16 32 4 20 12 28 6 22 14 30 2 18 10 26 7 23 15 31 3 19 11 27 5 21 13 29 1 17 9 25
9 39 9 25 1 17 13 29 5 21 11 27 3 19 15 31 7 23 10 26 2 18 14 30 6 22 12 28 4 20 16 32 8 24
10 40 10 26 2 18 14 30 6 22 12 28 4 20 16 32 8 24 9 25 1 17 13 29 5 21 11 27 3 19 15 31 7 23
11 41 11 27 3 19 15 31 7 23 9 25 1 17 13 29 5 21 12 28 4 20 16 32 8 24 10 26 2 18 14 30 6 22
12 42 12 28 4 20 16 32 8 24 10 26 2 18 14 30 6 22 11 27 3 19 15 31 7 23 9 25 1 17 13 29 5 21
13 43 13 29 5 21 9 25 1 17 15 31 7 23 11 27 3 19 14 30 6 22 10 26 2 18 16 32 8 24 12 28 4 20
14 44 14 30 6 22 10 26 2 18 16 32 8 24 12 28 4 20 13 29 5 21 9 25 1 17 15 31 7 23 11 27 3 19
15 45 15 31 7 23 11 27 3 19 13 29 5 21 9 25 1 17 16 32 8 24 12 28 4 20 14 30 6 22 10 26 2 18
16 46 16 32 8 24 12 28 4 20 14 30 6 22 10 26 2 18 15 31 7 23 11 27 3 19 13 29 5 21 9 25 1 17
17 47 17 1 25 9 21 5 29 13 19 3 27 11 23 7 31 15 18 2 26 10 22 6 30 14 20 4 28 12 24 8 32 16
18 48 18 2 26 10 22 6 30 14 20 4 28 12 24 8 32 16 17 1 25 9 21 5 29 13 19 3 27 11 23 7 31 15
19 49 19 3 27 11 23 7 31 15 17 1 25 9 21 5 29 13 20 4 28 12 24 8 32 16 18 2 26 10 22 6 30 14
20 50 20 4 28 12 24 8 32 16 18 2 26 10 22 6 30 14 19 3 27 11 23 7 31 15 17 1 25 9 21 5 29 13
21 51 21 5 29 13 17 1 25 9 23 7 31 15 19 3 27 11 22 6 30 14 18 2 26 10 24 8 32 16 20 4 28 12
22 52 22 6 30 14 18 2 26 10 24 8 32 16 20 4 28 12 21 5 29 13 17 1 25 9 23 7 31 15 19 3 27 11
23 53 23 7 31 15 19 3 27 11 21 5 29 13 17 1 25 9 24 8 32 16 20 4 28 12 22 6 30 14 18 2 26 10
24 54 24 8 32 16 20 4 28 12 22 6 30 14 18 2 26 10 23 7 31 15 19 3 27 11 21 5 29 13 17 1 25 9
25 55 25 9 17 1 29 13 21 5 27 11 19 3 31 15 23 7 26 10 18 2 30 14 22 6 28 12 20 4 32 16 24 8
26 56 26 10 18 2 30 14 22 6 28 12 20 4 32 16 24 8 25 9 17 1 29 13 21 5 27 11 19 3 31 15 23 7
27 57 27 11 19 3 31 15 23 7 25 9 17 1 29 13 21 5 28 12 20 4 32 16 24 8 26 10 18 2 30 14 22 6
28 58 28 12 20 4 32 16 24 8 26 10 18 2 30 14 22 6 27 11 19 3 31 15 23 7 25 9 17 1 29 13 21 5
29 59 29 13 21 5 25 9 17 1 31 15 23 7 27 11 19 3 30 14 22 6 26 10 18 2 32 16 24 8 28 12 20 4
30 60 30 14 22 6 26 10 18 2 32 16 24 8 28 12 20 4 29 13 21 5 25 9 17 1 31 15 23 7 27 11 19 3
31 61 31 15 23 7 27 11 19 3 29 13 21 5 25 9 17 1 32 16 24 8 28 12 20 4 30 14 22 6 26 10 18 2
32 62 32 16 24 8 28 12 20 4 30 14 22 6 26 10 18 2 31 15 23 7 27 11 19 3 29 13 21 5 25 9 17 1
SF16
1 15 1 9 5 13 3 11 7 15 2 10 6 14 4 12 8 16 1 9 5 13 3 11 7 15 2 10 6 14 4 12 8 16
2 16 2 10 6 14 4 12 8 16 1 9 5 13 3 11 7 15 2 10 6 14 4 12 8 16 1 9 5 13 3 11 7 15
3 17 3 11 7 15 1 9 5 13 4 12 8 16 2 10 6 14 3 11 7 15 1 9 5 13 4 12 8 16 2 10 6 14
4 18 4 12 8 16 2 10 6 14 3 11 7 15 1 9 5 13 4 12 8 16 2 10 6 14 3 11 7 15 1 9 5 13
5 19 5 13 1 9 7 15 3 11 6 14 2 10 8 16 4 12 5 13 1 9 7 15 3 11 6 14 2 10 8 16 4 12
6 20 6 14 2 10 8 16 4 12 5 13 1 9 7 15 3 11 6 14 2 10 8 16 4 12 5 13 1 9 7 15 3 11
7 21 7 15 3 11 5 13 1 9 8 16 4 12 6 14 2 10 7 15 3 11 5 13 1 9 8 16 4 12 6 14 2 10
8 22 8 16 4 12 6 14 2 10 7 15 3 11 5 13 1 9 8 16 4 12 6 14 2 10 7 15 3 11 5 13 1 9
3GPP
Release 8 61 3GPP TS 25.224 V8.0.0 (2008-03)
9 23 9 1 13 5 11 3 15 7 10 2 14 6 12 4 16 8 9 1 13 5 11 3 15 7 10 2 14 6 12 4 16 8
10 24 10 2 14 6 12 4 16 8 9 1 13 5 11 3 15 7 10 2 14 6 12 4 16 8 9 1 13 5 11 3 15 7
11 25 11 3 15 7 9 1 13 5 12 4 16 8 10 2 14 6 11 3 15 7 9 1 13 5 12 4 16 8 10 2 14 6
12 26 12 4 16 8 10 2 14 6 11 3 15 7 9 1 13 5 12 4 16 8 10 2 14 6 11 3 15 7 9 1 13 5
13 27 13 5 9 1 15 7 11 3 14 6 10 2 16 8 12 4 13 5 9 1 15 7 11 3 14 6 10 2 16 8 12 4
14 28 14 6 10 2 16 8 12 4 13 5 9 1 15 7 11 3 14 6 10 2 16 8 12 4 13 5 9 1 15 7 11 3
15 29 15 7 11 3 13 5 9 1 16 8 12 4 14 6 10 2 15 7 11 3 13 5 9 1 16 8 12 4 14 6 10 2
16 30 16 8 12 4 14 6 10 2 15 7 11 3 13 5 9 1 16 8 12 4 14 6 10 2 15 7 11 3 13 5 9 1
SF8
1 7 1 5 3 7 2 6 4 8 1 5 3 7 2 6 4 8 1 5 3 7 2 6 4 8 1 5 3 7 2 6 4 8
2 8 2 6 4 8 1 5 3 7 2 6 4 8 1 5 3 7 2 6 4 8 1 5 3 7 2 6 4 8 1 5 3 7
3 9 3 7 1 5 4 8 2 6 3 7 1 5 4 8 2 6 3 7 1 5 4 8 2 6 3 7 1 5 4 8 2 6
4 10 4 8 2 6 3 7 1 5 4 8 2 6 3 7 1 5 4 8 2 6 3 7 1 5 4 8 2 6 3 7 1 5
5 11 5 1 7 3 6 2 8 4 5 1 7 3 6 2 8 4 5 1 7 3 6 2 8 4 5 1 7 3 6 2 8 4
6 12 6 2 8 4 5 1 7 3 6 2 8 4 5 1 7 3 6 2 8 4 5 1 7 3 6 2 8 4 5 1 7 3
7 13 7 3 5 1 8 4 6 2 7 3 5 1 8 4 6 2 7 3 5 1 8 4 6 2 7 3 5 1 8 4 6 2
8 14 8 4 6 2 7 3 5 1 8 4 6 2 7 3 5 1 8 4 6 2 7 3 5 1 8 4 6 2 7 3 5 1
SF4
1 3 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4
2 4 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3 2 4 1 3
3 5 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2
4 6 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1 4 2 3 1
SF2
1 1 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2
2 2 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1
SF1
1 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
3GPP
Release 8 62 3GPP TS 25.224 V8.0.0 (2008-03)
Annex A (informative):
Power Control
A.1 Example Implementation of Downlink Power Control

in the UE
The power control may be realized by two cascaded control loops. The outer loop controls the transmission quality,
whose reference value is set by higher layers [15], by providing the reference value for the inner loop. This reference
value should be the SIR at the UE [15]. The inner loop controls the physical quantity for which the outer loop produces
the reference value (e. g. the SIR) by generating TPC commands. This may be done by comparing the measured SIR to
its reference value. When the measured value is higher than the target SIR value, TPC command = "down". When this
is lower than or equal to the target SIR value, TPC command = "up".
In case of a downlink transmission pause on the DPCH or PDSCH, the receive power (RSCP) of the data can no longer
be used for inner loop SIR calculations in the UE. In this case the UE should trace the fluctuations of the pathloss based
on the P-CCPCH and use these values instead for generating the TPC commands. This pathloss together with the
timeslot ISCP measurement in the data timeslot, which is ongoing, should be used to calculate a virtual SIR value:
SIRvirt(i) = RSCPvirt(i)  ISCP(i) + 10 lg SF ,

i 1
RSCPvirt(i) = RSCP0 + L0 – L(i) +  TPC (k ) ,
k 1
RSCP: Received signal code power in dBm

ISCP: Interference signal code power in the DPCH / PDSCH timeslot in dBm
SF： Used spreading factor
L: pathloss in dB measured on the P-CCPCH. The same weighting of the long- and short-term pathloss
should be used as for uplink open loop power control, see Annex A.1
i: index for the frames during a transmission pause, 1  i  number of frames in the pause
L0: weighted pathloss in the last frame before the transmission pause in dB
RSCP0: RSCP of the data that was used in the SIR calculation of the last frame before the pause in dBm
TPC (k):  power control stepsize in dB according to the TPC bit generated and transmitted in frame k, TPC
bit "up" = +stepsize, TPC bit "down" = stepsize
A.2 Example Implementation of Closed Loop Uplink

Power Control in Node B for 1.28Mcps TDD
Uplink power control is based on a quality target, set by higher layers. An example implementation for a Node B TPC
calculation algorithm is SIR based. In this algorithm, an outer loop sets a target SIR value, SIR target, which may be
adjusted from time to time in order to ensure that the quality target is met. In the meantime, as part of an inner loop a
calculation of SIR in associated uplink transmissions may be carried out. When the measured value is higher than the
target SIR value, TPC command = "down". When the measurement is lower than or equal to the target SIR, TPC
command = "up".
A.3 Example Implementation of Downlink Power Control

in UE for 1.28Mcps TDD when TSTD is used
Downlink power control is based on a quality target, set by higher layers. An example implementation for a UE TPC
calculation algorithm is SIR based. In this algorithm, an outer loop sets a target SIR value, SIR target, which may be
3GPP
Release 8 63 3GPP TS 25.224 V8.0.0 (2008-03)
adjusted from time to time in order to ensure that the quality target is met. In the meantime, as part of an inner loop a
calculation of SIR in associated downlink transmissions may be carried out. When the measured value is higher than the
target SIR value, TPC command = "down". When the measurement is lower than or equal to the target SIR, TPC
command = "up".
When TSTD is applied, the UE can use the consecutive measurements of SIR to calculate SIRAVG:
SIRAVG(i) = w1SIR(i-1) + w2SIR(i),
where, w1 + w2 = 1, w1 >= 0, w2 >= 0, and SIR(i) is the measurement of SIR in sub-frame i and SIRAVG(i) is the
measurement of SIRAVG in sub-frame i. If SIRAVG is greater than the target SIR value, TPC command = "down". If the
SIRAVG is smaller than the target SIR value, TPC command = "up".
In case of a downlink transmission pause on the DPCH, the example in Annex A.1 can be used for DL power control
with RSCPvirt(i) and ISCP(i) replaced by RSCPAVG(i) and ISCPAVG(i), where
RSCPAVG(i) = w1RSCPvirt(i-1) + w2RSCPvirt(i),
ISCPAVG(i) = w1ISCP(i-1) + w2ISCP(i).
A.4 Example Implementation of open Loop Power

Control for access procedure for 1.28Mcps TDD
The higher layer signals (on BCH) a power increment that is applied to the SYNC-UL burst only for the access
procedure. At each new transmission of a SYNC-UL burst during the access procedure, the transmit power level can be
increased by this power increment.
A.5 Example Implementation of Closed Loop Uplink HS-

SICH Power Control in Node B for 1.28Mcps TDD
Uplink power control is based on a quality target and a power offset, set by higher layers. An example implementation
for a Node B TPC calculation algorithm is SIR based (HS-SICH SIR Target). In this algorithm, if an ACK is decoded
from HS-SICH, the Node B shall adjust the measured value of HS-SICH with a power offset. When the (adjusted)
measured value is higher than the target SIR value, TPC command = "down". When the (adjusted) measurement is
lower than or equal to the target SIR, TPC command = "up"
3GPP
Release 8 64 3GPP TS 25.224 V8.0.0 (2008-03)
Annex B (informative):
Determination of Weight Information
Selective Transmit Diversity (STD) and Transmit Adaptive Antennas (TxAA) are examples of transmit diversity
schemes for dedicated physical channels.
B.1 STD Weights

The weight vector will take only two values depending on the signal strength received by each antenna in the uplink
slot. For each user, the antenna receiving the highest power will be selected (i.e. the corresponding weight will be set
to 1).
Table B.1: STD weights for two TX antennas
W1 W2
Antenna 1 receiving highest power 1 0
Antenna 2 receiving highest power 0 1
B.2 TxAA Weights

In a generic sense, the weight vector to be applied at the transmitter is the w that maximises:
P=wHHHHw (1)
where
H=h1 h2 and w = [ w1, w2 ]T
and where the column vector hi represents the estimated uplink channel impulse response for the i'th transmission
antenna, of length equal to the length of the channel impulse response.
3GPP
Release 8 65 3GPP TS 25.224 V8.0.0 (2008-03)
Annex C (informative):
Cell search procedure for 3.84Mcps TDD
During the cell search, the UE searches for a cell and determines the downlink scrambling code, basic midamble code
and frame synchronisation of that cell. The cell search is typically carried out in three steps:
Step 1: Primary synchronisation code acquisition
During the first step of the cell search procedure, the UE uses the SCH's primary synchronisation code to find a cell.
This is typically done with a single matched filter (or any similar device) matched to the primary synchronisation code
which is common to all cells. A cell can be found by detecting peaks in the matched filter output.
Note that for a cell of SCH slot configuration case 1, the SCH can be received periodically every 15 slots. In case of a
cell of SCH slot configuration case 2, the following SCH slot can be received at offsets of either 7 or 8 slots from the
previous SCH slot.
Step 2: Code group identification and slot synchronisation
During the second step of the cell search procedure, the UE uses the SCH's secondary synchronisation codes to identify
1 out of 32 code groups for the cell found in the first step. This is typically done by correlating the received signal with
the secondary synchronisation codes at the detected peak positions of the first step. The primary synchronisation code
provides the phase reference for coherent detection of the secondary synchronisation codes. The code group can then
uniquely be identified by detection of the maximum correlation values.
Each code group indicates a different toffset parameter and 4 specific cell parameters. Each of the cell parameters is
associated with one particular downlink scrambling code and one particular long and short basic midamble code. When
the UE has determined the code group, it can unambiguously derive the slot timing of the found cell from the detected
peak position in the first step and the toffset parameter of the found code group in the second step.
Note that the modulation of the secondary synchronisation codes also indicates the position of the SCH slot within a 2
frames period, e.g. a frame with even or odd SFN. Additionally, in the case of SCH slot configuration following case 2,
the SCH slot position within one frame, e.g. first or last SCH slot, can be derived from the modulation of the secondary
synchronisation codes.
Step 3: Downlink scrambling code, basic midamble code identification and frame synchronisation
During the third and last step of the cell search procedure, the UE determines the exact downlink scrambling code, basic
midamble code and frame timing used by the found cell. The long basic midamble code can be identified by correlation
over the P-CCPCH (or any other beacon channel) with the 4 possible long basic midamble codes of the code group
found in the second step. A P-CCPCH (or any other beacon channel) always uses the midamble m (1) (and in case of
SCTD also midamble m(2)) derived from the long basic midamble code and always uses a fixed and pre-assigned
channelisation code.
When the long basic midamble code has been identified, downlink scrambling code and cell parameter are also known.
The UE can read system and cell specific BCH information and acquire frame synchronisation.
Note that even for an initial cell parameter assignment, a cell cycles through a set composed of 2 different cell
parameters according to the SFN of a frame, e.g. the downlink scrambling code and the basic midamble code of a cell
alternate for frames with even and odd SFN. Cell parameter cycling leaves the code group of a cell unchanged.
If the UE has received information about which cell parameters or SCH configurations to search for, cell search can be
simplified.
3GPP
Release 8 66 3GPP TS 25.224 V8.0.0 (2008-03)
Annex CA (informative):
Cell search procedure for 1.28Mcps TDD
During the initial cell search, the UE searches for a cell. It then determines the DwPTS synchronization, scrambling and
basic midamble code identification, control multi-frame synchronisation and then reads the contents in BCH. This
initial cell search is carried out in 4 steps:
Step 1: Search for DwPTS
During the first step of the initial cell search procedure, the UE uses the SYNC-DL (in DwPTS) to acquire DwPTS
synchronization to a cell. This is typically done with one or more matched filters (or any similar device) matched to the
received SYNC-DL which is chosen from PN sequences set. A single or more matched filter (or any similar device) is
used for this purpose. During this procedure, the UE needs to identify which of the 32 possible SYNC-DL sequences is
used.
Step 2: Scrambling and basic midamble code identification
During the second step of the initial cell search procedure, the UE receives the midamble of the P-CCPCH.The P-
CCPCH is followed by the DwPTS. In the 1.28 Mcps TDD each DwPTS code corresponds to a group of 4 different
basic midamble code. Therefore there are total 128 midamble codes and these codes are not overlapping with each
other. Basic midamble code number divided by 4 gives the SYNC-DL code number. Since the SYNC-DL and the group
of basic midamble codes of the P-CCPCH are related one by one (i.e, once the SYNC-DL is detected, the 4 midamble
codes can be determined), the UE knows which 4 basic midamble codes are used. Then the UE can determine the used
basic midamble code using a try and error technique. The same basic midamble code will be used throughout the frame.
As each basic midamble code is associated with a scrambling code, the scrambling code is also known by that time.
According to the result of the search for the right midamble code, UE may go to next step or go back to step 1.
Step 3: Control multi-frame synchronisation
During the third step of the initial cell search procedure, the UE searches for the MIB( Master Indication Block) of
multi-frame of the BCH in the P-CCPCH indicated by QPSK phase modulation of the DwPTS with respect to the P-
CCPCH midamble. The control multi-frame is positioned by a sequence of QPSK symbols modulated on the DwPTS.
[n] consecutive DwPTS are sufficient for detecting the current position in the control multi-frame. According to the
result of the control multi-frame synchronisation for the right midamble code, UE may go to next step or go back to step
2.
Step 4: Read the BCH
The (complete) broadcast information of the found cell in one or several BCHs is read. According to the result the UE
may move back to previous steps or the initial cell search is finished.
For Dedicated Carrier MBSFN
For the MS burst, the preamble codes (see the Table AA.1a in TS25.221) are segmented into even code group and odd
code group, PP,even group and PP,odd group (see the clause 8.3Aa in TS25.223). When the preamble of the MS burst is
PP,odd, it indicates that the next sub-frame is the beginning of the multi-frame of PCCPCH; otherwise, the preamble of
MS burst uses the PP,even (PP,even and PP,odd belong to the same subgroup). The preamble of MT burst is decided by the
upper-layer signaling. This initial SFN cell search is carried out in 4 steps:
Step 1: Search for PP,even
During the first step of the initial SFN cell search procedure, the UE uses the PP,even (in MS burst) to acquire
synchronization to a SFN cell.
Step 2: Multi-frame synchronization
During the second step of the initial SFN cell search procedure, the UE searches for the PP,odd (in MS burst) to get the
beginning position of the multi-frame of PCCPCH. According to the result of multi-frame synchronization, UE may go
to next step or go back to step 1.
3GPP
Release 8 67 3GPP TS 25.224 V8.0.0 (2008-03)
Step 3: Read the BCCH
The UE reads the MIB (Master Indication Block) of multi-frame P-CCPCHs in the BCH and gets the system
information of the found SFN cell. According to the result of reading the BCCH, UE may go to next step or go back to
step 2.
Step 4: Read the MCCH
The UE reads the MCCH indicated by the BCCH information. According to the result the UE may move back to
previous steps or the initial cell search is finished.
3GPP
Release 8 68 3GPP TS 25.224 V8.0.0 (2008-03)
Annex CB (informative):
Examples random access procedure for 1.28Mcps TDD
Table CB.1: One PRACH, TTI=5ms, WT=4, L =1, SF4 PRACH
Sub-frame Number 0 1 2 3 4 5 6 7 8 9 10
Users sending on UpPCH 1 3 5 7
2 4 6 8
Acknowledged user on
FPACH 1 2 3 4 5 6 7
User sending on PRACH 0 1 2 3 4 5 6 7
User 8 is not granted because more than 5 sub-frames would have passed since the UpPCH.
Table CB.2: Two PRACHs, TTI=10ms, WT=4, L =2, SF8 PRACH
Sub-frame Number 0 1 2 3 4 5 6 7 8 9 10 11
2 4 6 8
FPACH 1 2 3 4 5 6 7
User sending on PRACH 0

2 2 4 4 6 6
User sending on PRACH 1 1 1 3 3 5 5 7 7
Table CB.3: Four PRACHs, TTI=20ms, WT=4, L =4, SF16 PRACH
Sub-frame Number 0 1 2 3 4 5 6 7 8 9 10 11 12 13
2 4 6 8
1 2 3 4 5 6 7
FPACH
User sending on PRACH 0 4 4 4 4
3GPP
Release 8 69 3GPP TS 25.224 V8.0.0 (2008-03)
Table CB.4: Two PRACHs, TTI=20ms, WT=4, L =4, SF16 PRACH
Sub-frame Number 0 1 2 3 4 5 6 7 8 9 10 11 12
2 4 6 8
X 1 2 3 X X
FPACH
User sending on PRACH 0 2 2 2 2
The FPACH is used ONLY in sub-frames 0, 1, 4, 5, 8, 9,… because they correspond to the used RACH resources.
The FPACH in sub-frame 0 is not used because no UpPCH is preceding.
The FPACH in sub-frames 8,9 is not used because no UpPCH is preceding in the last 4 sub-frames.
In contrast to the previous examples users 4,5,6,7 are not granted because they would not lead to a RACH anyway. In
this example their grant would come too late.
3GPP
Release 8 70 3GPP TS 25.224 V8.0.0 (2008-03)
Annex D (informative):
Change history
3GPP
Release 8 71 3GPP TS 25.224 V8.0.0 (2008-03)
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Old New
14/01/00 RAN_05 RP-99594 - Approved at TSG RAN #5 and placed under Change Control - 3.0.0
14/01/00 RAN_06 RP-99698 001 01 Primary and Secondary CCPCH in TDD 3.0.0 3.1.0
14/01/00 RAN_06 RP-99698 002 - Measurement procedure of received reference power for OL-TPC 3.0.0 3.1.0
in TDD
14/01/00 RAN_06 RP-99699 004 1 STTD capability for P-CCPCH, TDD component 3.0.0 3.1.0
14/01/00 RAN_06 RP-99697 005 1 Alignment of Terminology Regarding Spreading for TDD Mode 3.0.0 3.1.0
14/01/00 - - - Change history was added by the editor 3.1.0 3.1.1
31/03/00 RAN_07 RP-000070 003 2 Cycling of cell parameters 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 007 2 Clarifications on the UL synchronisation and Timing advance 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 008 - Modification of SIR threshold on setting TPC 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 009 1 New section describing the random access procedure 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 011 - Removal of Synchronisation Case 3 in TDD 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 012 1 Clarifications on power control procedures 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 013 - Signal Point Constellation 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 014 2 Out-of-sync handling for UTRA TDD 3.1.1 3.2.0
31/03/00 RAN_07 RP-000070 015 - Removal of ODMA from the TDD specifications 3.1.1 3.2.0
26/06/00 RAN_08 RP-000274 016 - Editorial correction for the power control section in 25.224 3.2.0 3.3.0
26/06/00 RAN_08 RP-000274 017 - Power control for TDD during DTX 3.2.0 3.3.0
26/06/00 RAN_08 RP-000274 018 1 Power Control for PDSCH 3.2.0 3.3.0
26/06/00 RAN_08 RP-000274 020 1 Editorial modification of 25.224 3.2.0 3.3.0
26/06/00 RAN_08 RP-000274 021 - Clarifications on TxDiversity for UTRA TDD 3.2.0 3.3.0
26/06/00 RAN_08 RP-000274 022 1 Introduction of the TDD DSCH detection procedure in TS 25.224 3.2.0 3.3.0
26/06/00 RAN_08 RP-000274 023 - Downlink power control on timeslot basis 3.2.0 3.3.0
23/09/00 RAN_09 RP-000347 019 1 Gain Factors for TDD Mode 3.3.0 3.4.0
23/09/00 RAN_09 RP-000347 025 - Terminology regarding the beacon function 3.3.0 3.4.0
23/09/00 RAN_09 RP-000347 026 1 Synchronisation of timing advance adjustment and timing deviation 3.3.0 3.4.0
measurement
23/09/00 RAN_09 RP-000347 027 1 CCTrCH UL/DL pairing for DL inner loop power control 3.3.0 3.4.0
23/09/00 RAN_09 RP-000347 028 1 RACH timing in TDD mode 3.3.0 3.4.0
23/09/00 RAN_09 RP-000347 030 1 TDD Access Bursts for HOV 3.3.0 3.4.0
23/09/00 RAN_09 RP-000347 032 - Removal of ODMA related abbreviations and correction of 3.3.0 3.4.0
references
23/09/00 RAN_09 RP-000347 033 - Clarifications on the Out-of-sync handling for UTRA TDD 3.3.0 3.4.0
15/12/00 RAN_10 RP-000544 035 1 Radio Link establishment and sync status reporting 3.4.0 3.5.0
15/12/00 RAN_10 RP-000544 040 - Clarification on PICH power setting 3.4.0 3.5.0
15/12/00 RAN_10 RP-000544 042 - Correction to TDD timing advance description 3.4.0 3.5.0
15/12/00 RAN_10 RP-000544 043 - Limit on maximum value of alpha used for open loop power control 3.4.0 3.5.0
16/03/01 RAN_11 - - - Approved as Release 4 specification (v4.0.0) at TSG RAN #11 3.5.0 4.0.0
16/03/01 RAN_11 RP-010065 036 - DTX and Special Burst Scheduling 3.5.0 4.0.0
16/03/01 RAN_11 RP-010065 037 1 RACH random access procedure 3.5.0 4.0.0
16/03/01 RAN_11 RP-010065 045 - Introduction of closed-loop Tx diversity for the PDSCH and DTX for 3.5.0 4.0.0
the PUSCH/PDSCH
16/03/01 RAN_11 RP-010065 046 2 Corrections of TDD power control sections 3.5.0 4.0.0
16/03/01 RAN_11 RP-010065 050 - Use of a special burst in reconfiguration 3.5.0 4.0.0
16/03/01 RAN_11 RP-010065 053 - Known TFCI for the TDD special burst 3.5.0 4.0.0
16/03/01 RAN_11 RP-010073 044 2 Layer 1 procedure for Node B synchronisation 3.5.0 4.0.0
16/03/01 RAN_11 RP-010071 047 1 Inclusion of 1,28 Mcps TDD in TS 25.224 3.5.0 4.0.0
16/03/01 RAN_11 RP-010072 048 1 Idle periods for IPDL location method 3.5.0 4.0.0
15/06/01 RAN_12 RP-010338 057 - Correction of Timing Advance section for 3.84 Mcps TDD 4.0.0 4.1.0
15/06/01 RAN_12 RP-010338 059 - Addition to the abbreviation list 4.0.0 4.1.0
15/06/01 RAN_12 RP-010343 049 - Clarification of IP_Frame(x) definition 4.0.0 4.1.0
15/06/01 RAN_12 RP-010343 055 1 Correction of IPDL burst parameters 4.0.0 4.1.0
21/09/01 RAN_13 RP-010525 064 1 Correction of criteria for OOS indication 4.1.0 4.2.0
21/09/01 RAN_13 RP-010531 060 - Corrections for TS 25.224 4.1.0 4.2.0
21/09/01 RAN_13 RP-010531 062 1 Corrections of Annex E in 25.224 4.1.0 4.2.0
21/09/01 RAN_13 RP-010531 061 - Corrections and Clarifications for calculation of idle period position 4.1.0 4.2.0
in subclause 4.10.3 in 25.224
14/12/01 RAN_14 RP-010742 066 - Removal of the remark on power control 4.2.0 4.3.0
14/12/01 RAN_14 RP-010742 068 1 Transmit Diversity for P-CCPCH and PICH 4.2.0 4.3.0
14/12/01 RAN_14 RP-010742 070 1 Correction to random access procedure (Primitive from MAC) 4.2.0 4.3.0
14/12/01 RAN_14 RP-010749 073 1 Random access procedure for 1.28Mcps TDD 4.2.0 4.3.0
14/12/01 RAN_14 RP-010749 074 - Transmit diversity for P-CCPCH and PICH 4.2.0 4.3.0
14/12/01 RAN_14 RP-010749 075 - Correction of Annex A.3 in 25.224 4.2.0 4.3.0
14/12/01 RAN_14 RP-010749 076 - Removal of the remark on power control 4.2.0 4.3.0
14/12/01 RAN_14 RP-010749 077 - Corrections to DL-PC sections for 1.28 Mcps TDD 4.2.0 4.3.0
08/03/02 RAN_15 RP-020052 079 1 Removal of quantisation of bj gain factor when calculated from a 4.3.0 4.4.0
reference TFC
08/03/02 RAN_15 RP-020052 084 1 TDD MAC layer subchannel assignment 4.3.0 4.4.0
08/03/02 RAN_15 RP-020052 086 - Transmit diversity on PICH 4.3.0 4.4.0
08/03/02 RAN_15 RP-020057 080 - Introduction of “UE Positioning Enhancements for 1.28 Mcps TDD” 4.3.0 5.0.0
3GPP
Release 8 72 3GPP TS 25.224 V8.0.0 (2008-03)
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Old New
08/03/02 RAN_15 RP-020055 082 1 Introduction of “Node B synchronization for 1.28 Mcps TDD” 4.3.0 5.0.0
08/03/02 RAN_15 RP-020058 081 1 Power Control and Procedures for HSDPA 4.3.0 5.0.0
07/06/02 RAN_16 RP-020315 088 - Clarification on power control and TxDiversity procedure for 1.28 5.0.0 5.1.0
Mcps TDD
07/06/02 RAN_16 RP-020317 089 - TxDiversity for HSDPA in TDD 5.0.0 5.1.0
07/06/02 RAN_16 RP-020317 090 - Correction to HS-SCCH Power Control (TDD) 5.0.0 5.1.0
20/09/02 RAN_17 RP-020586 091 1 Corrections to 25.224 for HSDPA 5.1.0 5.2.0
20/09/02 RAN_17 RP-020572 094 2 Corrections to transmit diversity mode for TDD beacon-function 5.1.0 5.2.0
physical channels
20/09/02 RAN_17 RP-020577 097 1 Corrections to uplink synchronisation procedure 5.1.0 5.2.0
20/09/02 RAN_17 RP-020577 099 - Correction to the PRACH open loop power control procedure for 5.1.0 5.2.0
1.28 Mcps TDD
20/09/02 RAN_17 RP-020579 101 1 Corrections to transmit diversity mode for TDD beacon-function 5.1.0 5.2.0
physical channels
15/10/02 - - - - Separate subclause 5.1.1.3, which was by accident merged into the 5.2.0 5.2.1
header of subclause 5.1.1.4
22/12/02 RAN_18 RP-020854 102 1 Corrections and clarifications to TDD CQI description 5.2.1 5.3.0
22/12/02 RAN_18 RP-020852 105 - Editorial modification to the section numberings 5.2.1 5.3.0
24/03/03 RAN_19 RP-030141 109 1 Corrections to TPC Procedures During a DL Transmission Pause 5.3.0 5.4.0
24/03/03 RAN_19 RP-030141 114 1 Corrections to link adaptation procedure for UTRA TDD (3.84 Mcps 5.3.0 5.4.0
Option)
24/03/03 RAN_19 RP-030141 115 2 Minimum timing requirement for CQI transmission on HS-SICH in 5.3.0 5.4.0
UTRA TDD
24/03/03 RAN_19 RP-030141 117 2 Clarification of downlink closed loop power control procedures for 5.3.0 5.4.0
3.84 Mcps TDD
24/03/03 RAN_19 RP-030133 119 2 Corrections to the LCR power control procedure 5.3.0 5.4.0
24/06/03 RAN_20 RP-030277 120 - Clarifications for the 1.28Mcps TDD power control procedure 5.4.0 5.5.0
22/09/03 RAN_21 RP-030460 121 3 Clarification on PDSCH Downlink Power Control Procedures 5.5.0 5.6.0
22/09/03 RAN_21 RP-030476 125 1 DTX and Special Bursts in case of no data on S-CCPCH and 5.5.0 5.6.0
Beacon Channels
06/01/04 RAN_22 RP-030698 128 1 Correction to computed gain factors with signalled reference gain 5.6.0 5.7.0
factor values
13/01/04 RAN_22 - - - Created for M.1457 update 5.7.0 6.0.0
09/06/04 RAN_24 RP-040235 131 2 Addition of TSTD for S-CCPCH in 3.84Mcps TDD 6.0.0 6.1.0
07/09/04 RAN_25 RP-040316 134 - Transmit diversity usage for beacon channels in LCR TDD 6.1.0 6.2.0
07/09/04 RAN_25 RP-040319 137 1 Corrections of radio access procedure for 1.28Mcps TDD 6.1.0 6.2.0
13/12/04 RAN_26 RP-040451 138 - Introduction of MICH 6.2.0 6.3.0
13/12/04 RAN_26 RP-040452 139 - Introduction of MBMS soft combining for TDD 6.2.0 6.3.0
14/03/05 RAN_27 RP-050097 140 2 Improvements to uplink closed-loop power control for 1.28Mcps 6.3.0 6.4.0
TDD
14/03/05 RAN_27 RP-050089 141 - Release 6 HS-DSCH operation without a DL DPCH for 3.84Mcps 6.3.0 6.4.0
TDD
16/06/05 RAN_28 RP-050255 144 2 Clarification of UpPCH Sub-channel for 1.28 Mcps TDD 6.4.0 6.5.0
12/12/05 RAN_30 RP-050724 0146 1 Clarify the power control procedure of HS-SCCH for TDD 6.5.0 6.6.0
20/03/06 RAN_31 RP-060078 0149 - Introduction of the Physical Layer Common Control Channel 6.6.0 7.0.0
(PLCCH)
20/03/06 RAN_31 RP-060079 0150 - Introduction of 7.68Mcps TDD option 6.6.0 7.0.0
29/09/06 RAN_33 RP-060497 0152 - Release 7 Timing Advance (3.84 Mpcs and 7.68 Mcps TDD) 7.0.0 7.1.0
29/09/06 RAN_33 RP-060492 0153 - Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD 7.0.0 7.1.0
29/09/06 RAN_33 - - - Editorial correction for Tdoc number of CR0140R2 from RP-050096 7.0.0 7.1.0
to RP-050097 on table of history change
13/03/07 RAN_35 RP-070118 0159 2 Introduction of E-DCH for 1.28Mcps TDD 7.1.0 7.2.0
13/03/07 RAN_35 RP-070113 0155 1 Modification on the power control function of HS-SICH for LCR 7.1.0 7.2.0
TDD
13/03/07 RAN_35 RP-070113 0158 2 Clarification of closed Loop Uplink HS-SICH Power Control for 7.1.0 7.2.0
1.28Mcps TDD
30/05/07 RAN_36 RP-070385 0160 1 Support for MBSFN operation 7.2.0 7.3.0
30/05/07 RAN_36 RP-070386 0162 1 Support for 1.28Mcps TDD MBSFN operation 7.2.0 7.3.0
11/09/07 RAN_37 RP-070640 0164 1 Improvement on the power control of E-PUCH in 1.28Mcps TDD 7.3.0 7.4.0
11/09/07 RAN_37 RP-070650 0163 1 Introduction of multi-frequency operation for 1.28Mcps TDD 7.3.0 7.4.0
14/09/07 RAN_37 RP-070726 0166 1 Correction to the calculating formula of SIR 7.3.0 7.4.0
27/11/07 RAN_38 RP-070942 0172 - 7.4.0 7.5.0
Clarification of gain factor  e and Pe-base in LCR TDD EUL
27/11/07 RAN_38 RP-070943 0171 1 More improvement on dedicated carrier for 1.28Mcps TDD MBMS 7.4.0 7.5.0
04/03/08 RAN_39 RP-080140 0170 2 EUL power control improvements for 1.28Mcps TDD 7.5.0 7.6.0
04/03/08 RAN_39 RP-080140 0176 - Improvement of the UL synchronisation of E-PUCH for 1.28Mcps 7.5.0 7.6.0
TDD EUL
04/03/08 RAN_39 RP-080140 0177 1 Clarification and Correction of E-PUCH power control for LCR TDD 7.5.0 7.6.0
04/03/08 RAN_39 - - - Creation of Release 8 further to RAN_39 decision 7.6.0 8.0.0
3GPP
Release 8 73 3GPP TS 25.224 V8.0.0 (2008-03)
3GPP

3GPP TS 25.224: 3rd Generation Partnership Project Technical Specification Group Radio Access Network (Release 8)

Uploaded by

Copyright:

Available Formats

3GPP TS 25.224: 3rd Generation Partnership Project Technical Specification Group Radio Access Network (Release 8)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP TS 25.224: 3rd Generation Partnership Project Technical Specification Group Radio Access Network (Release 8)

Uploaded by

Copyright:

Available Formats

3rd Generation Partnership Project;

3GPP support office address

No part may be reproduced except as authorized by written permission.

4.7.1 Physical random access procedure......................................................................................................23

5.3.2 DCH synchronization..........................................................................................................................41

6.11.1 ACK/NACK detection.........................................................................................................................58

Annex A (informative): Power Control.........................................................................................61

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.

 For a specific reference, subsequent revisions do not apply.

[1] 3GPP TS 25.201: "Physical layer - general description".

[2] 3GPP TS 25.102: "UE physical layer capabilities".

[4] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)".

[5] 3GPP TS 25.213: "Spreading and modulation (FDD)".

[6] 3GPP TS 25.214: "Physical layer procedures (FDD)".

[7] 3GPP TS 25.215: "Physical Layer - Measurements (FDD)".

[9] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)".

[10] 3GPP TS 25.223: "Spreading and modulation (TDD)".

[11] 3GPP TS 25.225: "Physical Layer - Measurements (TDD)".

[12] 3GPP TS 25.301: "Radio Interface Protocol Architecture".

[13] 3GPP TS 25.302: "Services Provided by the Physical Layer".

[14] 3GPP TS 25.401: "UTRAN Overall Description".

[15] 3GPP TS 25.331: "RRC Protocol Specification"

[16] 3GPP TS 25.433: "UTRAN Iub Interface NBAP Signalling"

[18] 3GPP TS 25.321: "MAC protocol specification"

[19] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode"

[20] 3GPP TS 25.402: "Synchronisation in UTRAN Stage 2"

SSCH Secondary Synchronisation Channel

4 Physical layer procedures for the 3.84 Mcps option

4.2 Transmitter Power Control

Table 1: Transmit Power Control characteristics

4.2.2 Uplink Control

4.2.2.1 General Limits

4.2.2.3 DPCH, PUSCH and HS-SICH

4.2.2.3.1 Gain Factors

-  is signalled for the TFC, or

4.2.2.3.1.1 Signalled Gain Factors

4.2.2.3.1.2 Computed Gain Factors

Define the variable: K ref   RM

Similarly, define the variable K j  RM i N i

4.2.2.3.2 Out of synchronisation handling

The transmit power of the E-PUCH is calculated in the UE as follows:

 KE-PUCH is the E-PUCH constant value signalled by higher layers [15].

4.2.2.4.1 Gain Factors for E-PUCH

 the selected E-TFC transport block size

 the E-PUCH resource occupation in the E-DCH TTI

 the modulation type (QPSK/16-QAM)

 the HARQ power offset (see [18])

Table 1a: Tabulated e values

Δharq is set by higher layers (see [18]).

4.2.3 Downlink Control

4.2.3.2 S-CCPCH, PICH

4.2.3.4 DPCH, PDSCH

4.2.3.4.1 Out of synchronisation handling

4.3 Timing Advance

TAnew = TAold + 2t.

4.4 Synchronisation procedures