Forschungszentrum

Telekommunikation
Wien

Physical Layer Measurements

Christoph Mecklenbräuker
cfm@ftw.at
10.01.2002
An initiative of the
Kplus Programme
3GPP Release 4 (June 2001)

Physical Layer Specifications:

FDD: 25.215 v 4.1.0 (June’01)
TDD: 25.225 v 4.1.0 (June’01)

Layer-2: Measurement Model:

25.302 v 4.1.0 (June’01)

Layer-3: Requesting Reports

25.331 v 4.1.0 (June’01)
WG4: Accuracy and testing
TDD: 25.123 v 4.1.0 (June’01)
FDD: 25.133 v 4.1.0 (June’01)
1
 Concepts and Principles

© ftw. 10.01.2002 2

One of the key services provided by the physical layer is the measurement of
various quantities, which are used to trigger or perform a multitude of
functions. Both the user equipment (UE) and the UMTS Terrestrial Radio
Access Network (UTRAN) are required to perform a variety of
measurements.
The standard will not specify the method to perform these measurements or
stipulate that the list of measurements must all be performed.

While some of the measurements are critical to the functioning of the network
and are mandatory for delivering the basic functionality, others may be used
by the network operators in optimising the network.

Not all measurements are performed by the physical layer. Some

measurements (e.g. traffic volume statistics) are performed by higher layers
(e.g. the Medium Access Control (MAC) which is a sub-layer of Layer-2).

2
 General measurement concept

ƒ L1 provides a toolbox of measurement abilities:

- For the UE
- For the UTRAN (usually performed by Node B)

ƒ Measurements are controlled by UTRAN Layer 3

UE UTRAN UE UTRAN

MEASUREMENT CONTROL MEASUREMENT REPORT

setup, modify, or release UE measurement report:

a UE measurement normal case (no failure)

© ftw. 10.01.2002 3

In the L1 measurement specifications, the measurements are distinguished

between measurements in the UE (the messages are described in the RRC
Protocol, 3G TS 25.331) and measurements in the UTRAN (the messages are
described in the NBAP and the Frame Protocol, 3G TS 25.4xx).

To initiate a specific measurement the UTRAN transmits a 'measurement

control message' to the UE including a measurement ID and type, a command
(setup, modify, or release), the measurement objects and quantity, the
reporting quantities, criteria (periodical/event-triggered) and mode
(acknowledged/ unacknowledged).

Reporting events are defined which trigger the UE to send a report to the
UTRAN. When the reporting criterion is fulfilled the UE shall answer with a
'measurement report message' to the UTRAN including the measurement ID
and the results.

In idle mode, the measurement control message is broadcast in a System

Information Block (SIB) on the Broadcast Control Channel (BCCH).

3
 Layer-2 Model of physical layer
measurements

parameters parameters

Layer 1 Layer 3
A filtering B filtering C Evaluation D
of reporting
C' criteria

© ftw. 10.01.2002 4

25.302 v. 4.1.0 Clause 9: Measurements provided by the physical layer.

Measurements may be made periodically and reported to the upper layers or
may be event-triggered. Combining the event triggered and the periodical
approach is also possible.
Layer 1 filtering: internal L1 filtering of the inputs measured at point A.
Exact filtering is implementation dependant. How the measurements are
actually executed in the physical layer by an implementation (inputs A and
Layer 1 filtering) is not constrained by the standard i.e. the model does not
state a specific sampling rate or even if the sampling is periodic. What the
standard specifies is the performance objective and reporting rate at point B in
the model.
B: A measurement reported by layer 1 after layer 1 filtering. The reporting
rate at point B is defined by the standard and is measurement type specific. It
is chosen to be equal to the measurement period over which performance
objectives are defined.
Layer 3 filtering: Filtering performed on the measurements provided at point
B. The Layer 3 filters are standardised and the configuration of the layer 3
filters is provided by RRC signalling (UE measurements) or NBAP signalling
(Node B measurements);
C: A measurement after processing in the layer 3 filter. The reporting rate is
identical to the reporting rate at point B and is therefore also measurement
type specific. Although this is not shown in the figure, one measurement can
be used by a multiplicity of evaluation of reporting criteria;
D: a measurement report information (message) sent on the radio or Iub
interface.

4
 Types of UE measurements

- Intra-frequency measurements: on DL phys. channels at

the same frequency as the active set.
- Inter-frequency measurements: on DL phys. channels at
frequencies that differ from the frequency of the active set.
- Inter-system measurements: on DL phys. channels
belonging to another radio access system, e.g. GSM.
- Traffic volume measurements: on UL traffic volume.
- Quality measurements: quality parameters, e.g. DL
transport block error rate.
- Internal measurements: UE transmission power and UE
received signal level.

© ftw. 10.01.2002 5

For FDD, the „active set“ contains the cells to which the UE is connected in
soft handover state. For TDD, the „active set“ contains only one cell.

Physical layer measurements can be very „mode-specific“: although they

have the same name for FDD and TDD, they are different quantities:
see e.g.
Received Signal Code Power (RSCP),
Interference Signal Code Power (ISCP)

Inter-system measurements are defined identically for FDD and TDD, e.g.
GSM carrier RSSI,

Traffic volume is not measured by L1, but by L2

Internal measurements are not reported from UE to UTRAN. They are used
exclusively by the higher layers (RRC) in the UE.

5
 Measurement purposes

ƒ Purposes are not defined in the specs, but

measurements are needed for:
- Radio Resource Management
- Cell selection/reselection
- Power control
- Handover
- Dynamic Channel Allocation in TDD
- Timing advance in TDD
- Location services (LCS)
- other....?

© ftw. 10.01.2002 6

In former times the measurement purpose was included in RAN WG1

specifications (see e.g. temporary documents R1-99F42 (TDD) and R1-99E21
(FDD); details concerning measurements for DCA can be found in R2-99857.
However, the information on measurement purposes was deleted. Temporary
document RPA000013 includes purposes for FDD.

The RRC (Radio Resource Control, UTRAN Layer 3) is responsible for

Radio Resource Management (RRM) functions: it controls the physical
channel configurations for a possibly large set of cells and the serviced users.

The RRC sets up and closes all physical channels. Additionally, it can
reconfigure them while they are active.

The RRC requests measurements from the UE (using the RRC Protocol) and
the Node B (using the NBAP) for obtaining a detailed state of traffic and
interference to be able to perform RRM functions.

In case of a LCS method using UE measurements, it is the RRC which

requests the measurement reports from the UE.

6
 Range, mapping, and accuracy

ƒ The WG1 specs (25.215, 25.225) define the

measurement values without range, mapping, and
accuracy.
ƒ Range, mapping, and accuracy are defined by
WG4 Specs (25.123, 25.133).
ƒ resolution and accuracy are defined separately for
TDD and FDD, but are harmonised.

© ftw. 10.01.2002 7

There are separate specifications for TDD and FDD as is usual at L1 specs,
but for the same type of measurements in both modes the same accuracy is
required. Differences are found in the timing requirements due to a more
complicated timing scheme for initial synchronisation in FDD. This is
necessary, because the FDD Node B is not synchronised.

25.123 v. 4.1.0 for TDD

25.133 v. 4.1.0 for FDD

7
 Compressed Mode (FDD only)
Principles

ƒ UE has normally no idle-slots in FDD to perform

measurements: gaps must be created by network
ƒ Users which are near the center of their own cell
cannot perform intra-frequency measurements on
other cells due to strong intra-cell interference.
- Severe problem for LCS method OTDOA-IPDL.
ƒ Transmission gaps enable measurements on
adjacent cells.
ƒ Complicated scheduling by UTRAN required.

© ftw. 10.01.2002 8

Intra-cell interference is the part of the interference which originates from the own cell. Inter-cell interference is the
part of the interference which originates from other cells. Compressed Mode is introduced for reducing
measurement errors due to intra-cell interference.
Compressed Mode is defined as the mechanism whereby certain idle periods are created in radio frames so that the
UE can perform measurements during these periods.
Compressed Mode is controlled by the RRC.
L2 is responsible to either buffer some layer 2 PDUs or to adapt the rate of data flow (similar to GSM) so that there
is no loss of data because of compressed mode. This will be service dependent and controlled by the RRC layer.
Rate adaptation is usually implemented by puncturing of channel symbols.

FDD: 25.215 v. 4.1.0 Clause 6.1.1.1

The standard specifies that the “UE capabilities” define whether a UE requires compressed mode in order to monitor
cells on other FDD frequencies and on other modes and radio access technologies. UE capabilities indicate the
need for compressed mode separately for the uplink and downlink and for each mode, radio access technology
and frequency band.
A practical case occurs when the UE is equipped with a single receiver front-end only: it needs the idle-slots to free
its receiver from data transfer tasks.
Further, the UE might require uplink compressed mode, when monitoring frequencies which are close to the uplink
transmission frequency (i.e. frequencies in the TDD or GSM 1800/1900 bands).
Some UE might be equipped with dual receivers which can perform independent measurements, with the use of a
"monitoring branch" receiver, that can operate independently from the UTRA FDD receiver branch. Such UE do
not need to support downlink compressed mode.

8
 Compressed Mode (FDD only)
Details
#1 #2 #3 #4 #5 #TGPRC
TG pattern 1 TG pattern 2 TG pattern 1 TG pattern 2 TG pattern 1 TG pattern 2

TG pattern 1 TG pattern 2

Transmission
Transmission Transmission Transmission gap 2
gap 1 gap 2 gap 1

TGSN TGSN

TGL1 TGL2 TGL1 TGL2

TGD TGD

TGPL1 TGPL2
Provision for measurements
involving signals from other cells
© ftw. 10.01.2002 9

For measurements in compressed mode, a Transmission Gap Pattern Sequence

(TGPS) is defined. A TGPS consists of alternating transmission gap patterns 1
and 2, and each of these patterns in turn consists of one or two transmission gaps.
The transmission gap pattern structure, position and repetition are defined with
physical channel parameters described in 25.213 and 25.215.
When using simultaneous pattern sequences, it is the responsibility of the network to
ensure that the compressed mode gaps do not overlap and are not scheduled to
overlap the same frame.
The following parameters characterize a TGPS:
-TGSN (Transmission Gap Starting Slot Number): A transmission gap pattern begins in an
arbitrary „first“ radio frame. TGSN is the slot number of the first transmission gap slot
within the first radio frame of the transmission gap pattern;
-TGLn (Transmission Gap Length n): This is the duration of the n-th transmission gap
within the transmission gap pattern, expressed in number of slots; (n=1 or 2).
--TGD (Transmission Gap start Distance): This is the duration between the starting slots of
two consecutive transmission gaps within a transmission gap pattern, expressed in
number of slots.
-TGPLm (Transmission Gap Pattern Length m): This is the duration of transmission gap
pattern m, expressed in number of frames; (m=1 or 2).
-TGPRC (Transmission Gap Pattern Repetition Count): This is the number of transmission
gap patterns within the TGPS;
-TGCFN (Transmission Gap Connection Frame Number): This is the CFN of the first radio
frame of the first pattern 1 within the TGPS.

9
 UE measurement abilities

© ftw. 10.01.2002 10

10
 CPICH RSCP
Received Signal Code Power

Defined for Received power on one code measured on the Primary CPICH. The
FDD & TDD. reference point for RSCP is the antenna connector at the UE. If Tx
diversity is applied on the Primary CPICH the received code power from
UE each antenna shall be separately measured and summed together in [W]
to a total received code power on the Primary CPICH.

Applicable for
For FDD: Idle-mode, Connected-mode (intra- and inter-frequency)
For TDD: Idle-mode, Connected-mode inter-frequency
Range/ CPICH RSCP is given with a resolution of 1 dB with the range
mapping [-115, ..., -25] dBm.
CPICH RSCP shall be reported in the unit CPICH_RSCP_LEV where:

CPICH_RSCP_LEV _00: CPICH RSCP < –115 dBm

CPICH_RSCP_LEV _01: -115 dBm ≤ CPICH RSCP < –114 dBm
CPICH_RSCP_LEV _02: -114 dBm ≤ CPICH RSCP < –113 dBm
...
CPICH_RSCP_LEV _91: -25 dBm ≤ CPICH RSCP

© ftw. 10.01.2002 11

25.215 v. 4.1.0 Clause 5.1.1

25.225 v. 4.1.0 Clause 5.1.2

This measurement can be used for monitoring FDD cells. CPICH RSCP is
especially useful for handover between UTRA TDD and UTRA FDD. This
measurement is for handover evaluation, DL open loop power control, UL
open loop power control and for the calculation of pathloss.

25.123 v. 4.1.0 Clause 9.1.1.2.1

25.133 v. 4.1.0 Clause 9.1.1

The reporting range for CPICH RSCP is from -115 ... -25 dBm.

Relative accuracy is specified to be within ± 6 dB in normal conditions.

11
 P-CCPCH RSCP
Received Signal Code Power

Defined for Received Signal Code Power, the received power on one code measured
FDD & TDD. on the P-CCPCH from a TDD cell. The reference point for the RSCP is
the antenna connector at the UE.
UE

Applicable for For FDD: Idle-mode, Connected-mode inter-frequency

For TDD: Idle-mode, Connected-mode (intra- and inter-frequency)

Range/ Identical to CPICH RSCP

mapping

© ftw. 10.01.2002 12

25.215 v. 4.1.0 Clause 5.1.2

25.225 v. 4.1.0 Clause 5.1.1
25.123 v. 4.1.0 Clause 9.1.1.1

The P-CCPCH RSCP can either be measured on the data part or the midamble
of a burst, since there is no power difference between these two parts.
However, in order to have a common reference, measurement on the midamble
is assumed.

This measurement is useful for pathloss estimation: (pathloss estimates are

used for cell selection/reselection, HO, DCA, uplink open-loop PC, initial
downlink power setting).

In Idle-mode: P-CCPCH RSCP is measured to evaluate the received signal

strength at the UE from different TDD cells. A comparison with FDD
measurements is done based on ‘mapping functions’ (25.304).There is no
reporting to the UTRAN, therefore it has the character of an internal
measurement. However, it is reported to the RRC in the UE to evaluate the cell
selection criterion (25.304). When the measurement is fulfilled (depends on
L1-averaging) is will be reported automatically to RRC(UE).

This measurement is used for monitoring TDD cells.

12
 Timeslot ISCP
Interference Signal Code Power

Defined for Interference Signal Code Power, the interference on the received signal
TDD only. in a specified timeslot measured on the midamble. The reference point
for the ISCP is the antenna connector at the UE.
UE

Applicable for For TDD: Connected-mode intra-frequency

Range/ Timeslot ISCP is given with a resolution of 0.5 dB with the range
mapping [-120, ..., -80] dBm. Timeslot ISCP shall be reported in the unit
UE_TS_ISCP_LEV where:
UE_TS_ISCP_LEV_00: Timeslot_ISCP < -115 dBm
UE_TS_ISCP_LEV_01: -115 dBm ≤ Timeslot_ISCP < -114 dBm
UE_TS_ISCP_LEV_02: -114 dBm ≤ Timeslot_ISCP < -113 dBm
...
UE_TS_ISCP_LEV_90: -26 dBm ≤ Timeslot_ISCP < -25 dBm
UE_TS_ISCP_LEV_91: -25 dBm ≤ Timeslot_ISCP

© ftw. 10.01.2002 13

25.215 v. 4.1.0:
This UE measurement (ISCP) is not defined for FDD, but the auxiliary
quantity ISCP is used for defining the SIR measurement: see 25.215 v. 4.1.0
Clause 5.2.2

25.225 v. 4.1.0 Clause 5.1.3

25.123 v. 4.1.0 Clause 9.1.1.3

Absolute accuracy requirements of +/- 6 dB under normal conditions
(and +/- 9 dB under extreme conditions)

It is permissible to use the midamble to provide estimates of both ISCP and

RSCP (see notes on previous slide about P-CCPCH RSCP). The following
methods for implementation are given for illustration: One method would
separate the estimated channel impulse response into two parts: one is
regarded as „true taps“ of the channel impulse response, the other is regarded
as noise+interference. A more sophisticated technique would use the channel
estimate to form a replica of the received midamble sequence. The MSE
between the replica and the actual received midamble sequence is an estimate
of the noise+interference power.

13
 SIR
Signal to Interference Ratio
Defined for Signal to Interference Ratio, defined as:
FDD & TDD. (RSCP / Interference) × (SF)

The reference point for the SIR is the antenna connector of the UE.
UE

Applicable for Connected-mode intra-frequency (TDD only)

Range/ SIR is given with a resolution of 0.5 dB with the range [-11, ..., 20] dB.
mapping SIR shall be reported in the unit UE_SIR where:

UE_SIR_00: SIR < –11.0 dB

UE_SIR_01: -11.0 dB ≤ SIR < –10.5 dB
UE_SIR_02: -10.5 dB ≤ SIR < –10.0 dB
...
UE_SIR_62: 19.5 dB ≤ SIR < 20.0 dB
UE_SIR_63: 20.0 dB ≤ SIR

© ftw. 10.01.2002 14

For FDD mode, no such measurement is defined for the UE.

For TDD mode: see 3G TS 25.225 v. 4.1.0 Clause 5.1.6:

SF=The spreading factor used.

RSCP = Received power on the code of a specified DPCH or PDSCH.

Interference = Interference power on the received signal in the same timeslot

which can’t be eliminated by the receiver. (Remark: the measurement result
depends on the receiver type!)

25.133 v. 3.2.0:
Accuracy requirement +/- 3dB.

14
 UTRA Carrier RSSI
Received Signal Strength Indicator
Defined for Received Signal Strength Indicator, the wide-band received power
FDD & TDD. within the relevant channel bandwidth. Measurement shall be performed
on a UTRAN downlink carrier. The reference point for the RSSI is the
UE antenna connector at the UE. (For TDD, this measurement is performed
in a specified timeslot).

Applicable for Idle-mode, Connected-mode (inter- and intra-frequency)

Range/ UTRA carrier RSSI is given with a resolution of 1 dB with the range
mapping [-94, ..., -32] dBm. UTRA carrier RSSI shall be reported in the unit
UTRA_carrier_RSSI_LEV where:

UTRA_carrier_RSSI_LEV _00: UTRA carrier RSSI < –94 dBm

UTRA_carrier_RSSI_LEV _01: -94 dBm ≤ UTRA carrier RSSI < –93dBm
…
UTRA_carrier_RSSI_LEV _63: -32 dBm ≤ UTRA carrier RSSI

© ftw. 10.01.2002 15

FDD: 25.215 v. 3.2.0 Clause 5.1.4:

s e
au :
TDD: 25.225 v. 3.2.0 Clause 5.1.4:
ec cs
b pe
ed s
at he
t d ft
ou n o
b ly sio
s i er
o s v IS
p old TH
is n N
g e a R
pa rs to LEA
h is fe T
t re O
it O N
D

15
 GSM Carrier RSSI
Received Signal Strength Indicator
Defined for Received Signal Strength Indicator, the wide-band received power
FDD & TDD. within the relevant channel bandwidth. Measurement shall be performed
on a GSM BCCH carrier. The reference point for the RSSI is the
UE antenna connector at the UE. (For TDD, this measurement is performed
in a specified timeslot).

Applicable for Idle-mode, Connected-mode inter-frequency

Range/ According to the definition of RXLEV in GSM 05.08.

mapping RXLEV 0 = less than -110dBm.
RXLEV 1 = -110 dBm to -109 dBm.
RXLEV 2 = -109 dBm to -108 dBm.
:
RXLEV 62 = -49 dBm to -48 dBm.
RXLEV 63 = greater than -48 dBm.

© ftw. 10.01.2002 16

FDD: 25.215 v. 3.2.0 Clause 5.1.5:

s e
TDD: 25.225 v. 3.2.0 Clause 5.1.5:
a u :
e c cs
b pe
GSM Recommendation 05.08 (Radio Subsystem Link edControl)s
at he
GSM 05.08 v. 3.8.0 Clause 8.1.4:
d RXLEVf tvalue between 0 and
The received signal level shall be mapped to tan
63, as follows : ou n o
ly sio
RXLEV 0 = less than -110dBm. i
s b r
RXLEV 1 = -110 dBm to -109 s v IS
dBm. e
RXLEV 2 = -109 dBm top-108 dBm.o ld TH
o N
isto -48ndBm.
:
RXLEV 62 = -49 dBm
g e than -48 a dBm.AR
a to E
RXLEV 63 = greater
p
6 bits areis r sdefine RXLEV
L for each carrier measured.
th refe OT
required to

it O N
D

16
 CPICH Ec/No
Defined for Received energy per chip (Ec) divided by power density in the band.
FDD & TDD. Ec/No is identical to RSCP/RSSI. This is performed on Primary CPICH.
Reference point is the antenna connector at the UE. If Tx diversity is
UE applied on the Primary CPICH, the received Ec from each antenna shall
be separately measured and summed together in [Ws] to a total received
Ec on the Primary CPICH, before calculating the Ec/No.
Applicable for Idle-mode, Connected-mode (inter- and intra-frequency)

Range/
CPICH Ec/No is given with a resolution of 1 dB with the range [-24,
mapping
..., 0] dB. CPICH Ec/No shall be reported in the unit CPICH_Ec/No:
CPICH_Ec/No _00: CPICH Ec/No < –24 dB
CPICH_Ec/No _01: -24 dB ≤ CPICH Ec/No < –23 dB
CPICH_Ec/No _02: -23 dB ≤ CPICH Ec/No < –22 dB
...
CPICH_Ec/No _23: -2 dB ≤ CPICH Ec/No < -1 dB
CPICH_Ec/No _24: -1 dB ≤ CPICH Ec/No < 0 dB
CPICH_Ec/No _25: 0 dB ≤ CPICH Ec/No

© ftw. 10.01.2002 17

FDD: 25.215 v. 3.2.0 Clause 5.1.6:

TDD: 25.225 v. 3.2.0 Clause 5.1.7:

s e
This measurement is used monitoring FDD cells (regardlessa
u
of the :
ec cs
b pe
duplexing-mode that the UE is currently using)

ed s
Observe that the definition of CPICH E /N measurementeis slightly
t
t
incorrect because the energy per chip E is actually f th by the total
da divided
c o

power spectral density in the band which isunot theo

c
o n same as the
ly Nsi.o
noise+interference power spectral density
ib er
o

s
smeasurements
v Hare IS defined as absolute
Also, the „UTRA Carrier RSSI“ o
p units) ldratherTthan a power spectral
power levels (reported in dBm
is „UTRA o N
density (mW/Hz). Therefore,
e n Carrier RSSI“ measurements
a AR bandwidth of the receiver
report N B where B g is the noise-equivalent
o
front-end: B = 4.2aMHz (somewhat
o

p rs t LEsmaller than 5 MHz).

h is fe T
t re O
it O N
D
17
 Transport Channel BLER
Defined for Estimation of the transport channel block error rate (BLER). The BLER
FDD & TDD. estimation shall be based on evaluating the CRC on each transport
block.
UE

Applicable for For FDD: Connected-mode intra-frequency, Idle-mode.

For TDD: Connected-mode intra-frequency.

Range/ Transport channel BLER is given with a logarithmic resolution of

mapping 0.065 with the range [10^-4.03 ... 1] including a separate case
BLER=0. This shall be reported in the unit BLER_LOG:
BLER_LOG_00: BLER = 0
BLER_LOG_01: -∞ < log10(BLER) < -4.030
BLER_LOG_02: -4.030 ≤ log10(BLER) < -3.965
BLER_LOG_03: -3.965 ≤ log10(BLER) < -3.900
...
BLER_LOG_63: -0.065 ≤ log10(BLER) ≤ 0.000

© ftw. 10.01.2002 18

Log-resolution 0.065 Æ 16% relative step-size in adjacent BLER_LOG units

s e
On an AWGN channel, it is easy to calculate how many transport blocks n have to be
a u :
transmitted for reaching a desired level of accuracy of this measurement. In this case, the
c cs
number k of CRC failures is binomially distributed B(n,k,p) where BLER= p.
e
b pe
Example: For a transport channel showing BLER = 0.01 using interleaving-depth of 4
d s
frames per block, the confidence-level is 70 %, that the measured BLER is inside the
e
t he
interval of 0.01 ± 20%, i. e. in the interval 0.008 .... 0.012, after a measurement time of
a
approx. 2 minutes.
t d ft
ou v. 3.2.0oClause 9.1.1.6
FDD: 25.133 v. 3.2.0 Clause 8.1.7 & TDD: 25.123 n
b ly sfrom
Transport channel BLER value shall be calculated io a window with the size equal to
s i Periodical
the reporting interval (see section 10.3.7.78
e r reporting criteria in TS 25.331).
o s v IS
p old TH
is aftern RL combination.
FDD: 25.215 v. 3.2.0 Clause 5.1.7:
For FDD: The CRC is evaluated
e a
CRC. In R
N BLER estimation is only required

a g channel.
for transport channels containing
to A connected mode the BLER shall be possible to
p
measure on any transport If
E
requested in idle mode it shall be possible to measure
s ers PCH.
the BLER on transport channel
i L
t h ef OT
ti r Clause
TDD: 25.225 v. 3.2.0 N 5.1.8.
DO

18
 UE Transmitted Power

Defined for The total UE transmitted power on one carrier. The reference point for
FDD & TDD. the UE transmitted power shall be the UE antenna connector.

UE For TDD: Measurement is performed on a specified timeslot.

Applicable for Connected-mode intra-frequency.

Range/ UE transmitted power is given with a resolution of 1dB with the

mapping range [-50, ..., 33] dBm. UE transmitted power shall be reported in
the unit UE_TX_POWER:

UE_TX_POWER_000 to UE_TX_POWER_020: reserved

UE_TX_POWER_021: -50dBm ≤ UE_transmitted_power < -49dBm
UE_TX_POWER_022: -49dBm ≤ UE_transmitted_power < -48dBm
UE_TX_POWER_023: -48dBm ≤ UE_transmitted_power < -47dBm
...
UE_TX_POWER_104: 33dBm ≤ UE_transmitted_power < 34dBm

© ftw. 10.01.2002 19

FDD: 25.215 v. 3.2.0 Clause 5.1.8:

s e
TDD: 25.225 v. 3.2.0 Clause 5.1.9:
au :
ec cs
b pe
ed s
at he
t d ft
ou n o
b ly sio
s i er
o s v IS
p old TH
is n N
e
g to a R
p rs LEA
a
h is fe T
t re O
it O N
D

19
 SFN-CFN observed time difference

Defined for The SFN-CFN observed time difference to cell is defined as:
FDD & TDD
OFF × 38400 + Tm, where: Tm= (TUETx-T0) - TRxSFN, given in chip
units. It is not required to read cell SFN of the target neighbour cell
UE in compressed mode.

Applicable for Connected-mode inter- and intra-frequency.

Range/ Time difference is given with the resolution of one chip with the range
mapping [0, …, 9830399] chips.

NOTES:
1) This is useful for handover.
2) Regarding LCS:
Resulting resolution in time = 260 ns.
Resulting resolution in space = 78 m.

© ftw. 10.01.2002 20

25.215 v. 3.2.0 Clause 5.1.9:

TUETx is the time when the UE transmits an uplink DPCCH/DPDCH frame. s e

T0 is defined in TS 25.211 subclause 7.1.3.
a u :
c cs
TRxSFN is the time at the beginning of the neighbouring P-CCPCH frame received
e
most recent in time before the time instant TUETx-T0 in the UE. b pe
e d s
OFF=(SFN-CFN ) mod 256, given in number of frames
a t with htheerange [0, 1, …, 255]
d ft
Tx
frames.
t
u o of an uplink
CFN is the connection frame number for the o n
UE transmission
Tx
ly io
DPCCH/DPDCH frame at the time T
s i b rsat the time T .
. SFN is the system frame number for the
UETx
neighbouring P-CCPCH frame received
s v e IS
in the UE RxSFN

po oldis doneTwith
In case the inter-frequency measurement H compressed mode, the value
is reported
for the parameter OFF is always
n N
to be 0. This is an interesting special case
e
useful for LCS (location services). a
In case
g nottoneed to readRthat the SFN measurement indicator
a
indicates that the UE does
p E A cell SFN of the target neighbour cell, the
value of the parameter OFFsis always L be set to 0.
s
i fe T r
9830399 = (256 thx 38400)
r e – N1 =O(255 x 38400) + 38399.
it O during RAN WG1#14, June’00, Tdoc R1-00-0911:
For TDD: newly introduced
„Change Request 25.225 D CR 013rev1“. However the TDD measurement is defined
quite differently. (see below).

20
 SFN-SFN observed time difference
(Measurement Type 1)
Defined for The SFN-SFN observed time difference to cell is defined as:
FDD & TDD OFF×38400+ Tm, where:
Tm= TRxSFNj - TRxSFNi, given in chip units with the range
UE
[0, 1, …, 38399] chips

Applicable for FDD: Idle-mode, Connected-mode intra-frequency.

TDD: Idle-mode, Connected-mode inter- and intra-frequency.

Range/ Time difference is given with the resolution of one chip with the range
mapping [0, …, 9830399] chips.

NOTES:
1) This is useful for handover.
2) Regarding LCS: (maybe Type 1 is not used for LCS)
Resulting resolution in time = 260 ns.
Resulting resolution in space = 78 m.

© ftw. 10.01.2002 21

FDD: 25.215 v. 3.2.0 Clause 5.1.10: Type 1

Tm= TRxSFNj - TRxSFNi, given in chip units with the range [0, 1, …, 38399] chips
s e
TRxSFNj is the time at the beginning of a received neighbouring P-CCPCH frame from cell j.
a u :
TRxSFNi is time at the beginning of the neighbouring P-CCPCH frame from cell i received
most recent in time before the time instant TRxSFNj in the UE.
ec cs
b pe
OFF=(SFNi- SFNj) mod 256, given in number of frames with the range [0, 1, …, 255] frames.
d s
SFNj is the system frame number for downlink P-CCPCH frame from cell j in the UE at the
e
time TRxSFNj.
a t he
t d ft
SFNi is the system frame number for the P-CCPCH frame from cell i received in the UE at
the time TRxSFNi.
ou n o
TDD: 25.225 v. 3.2.0 Clause 5.1.10: Type 1 ly io
SFN-SFN observed time difference is the s
b s
i difference
r of the reception times of frames
time
e
s in thev UE andISexpressed in chips.
o
from two cells (serving and target) measured
, given in chippunits withl H[0, 1, …, 38399] chips
dthe range
T =T
m RxSFNi -T RxSFNk
is nframe o SFN T
T
T
RxSFNi :
:
time of start of the received
time of start of the received frame
N
SFN
of the serving TDD cell i.
e a R of the target UTRA cell k received most
i
RxSFNk
recent in time before the a g to
time instant T Ain the UE. k

p
OFF=(SFN - SFN ) mod 256, given s L E
in number
RxSFNi
of frames with the range [0, 1, …, 255]
i
s
i fe T
k
r
th number
frames.
SFNi: system frame
r e O
for downlink
N
frame from serving TDD cell i in the UE at the
time TRxSFNi . it
SFNk: system frame number
D O for downlink frame from target UTRA cell k received in the UE
at the time T .(for FDD: the P-CCPCH frame)
RxSFNk

21
 SFN-SFN observed time difference
(Measurement Type 2)
Defined for FDD: The relative timing difference between cell j and cell i,
FDD & TDD defined as TCPICHRxj – TCPICHRxi.
TDD: SFN-SFN observed time difference = TRxTSk - TRxTSi,
UE

Applicable for Idle-mode, Connected-mode inter- and intra-frequency (FDD & TDD).

Range/ Time difference is given with the resolution of 0.25 chip (but with an
mapping accuracy of only 0.5 chip) with the range [-1279.75, …, 1280] chips.
(The reported value is described 14 bits).

NOTES regarding LCS:

Resulting resolution in time = 65 ns and accuracy is 130 ns.
Resulting resolution in space = 20 m and accuracy is 40 m.

© ftw. 10.01.2002 22

This „Type 2“ measurement provides high-resolution time-differences which are useful for
location services (LCS). This is especially true for the standard LCS method „observed time
s e
difference of arrival“ (OTDOA-IPDL), but this measurement is not restricted to OTDOA-
a u :
IPDL. It may also be used in combination with other LCS methods. (See also 25.305 v. 3.2.0
Clause 4.4.2: OTDOA-IPDL Method with network configurable idle periods)
e c cs
b pe
e d s
FDD: 25.215 v. 3.2.0 Clause 5.1.10: Type 2
a t as he
d ft
The relative timing difference between cell j and cell i, defined
t
T CPICHRxj
-T ,
CPICHRxi
o u o
where:
T y siCPICH
is the time when the UE receives onelPrimary o n slot from cell j
ibPrimary
CPICHRxj
T is the time when the UE receives the
s e r CPICH slot from cell i that is closest
s fromvcell j IS
CPICHRxi
in time to the Primary CPICH slot received
o
p old TH
is n 2 N
g e defined
TDD: 25.225 v. 3.2.0 Clause 5.1.10: Type
a AdasR
T -T , in chips, a to E
SFN-SFN observed time difference
p
s ers T L
RxTSk RxTSi
where; i
h of aetimeslot
f Oreceived of the serving TDD cell i.
TRxTSi t
: time of start
r
TRxTSk
it of O N received from the target UTRA cell k that is closest in
:time of start of a timeslot
time to the start the timeslot of the serving TDD cell i.
D

22
 UE Rx-Tx time difference

Defined for The difference in time between the UE uplink DPCCH / DPDCH
FDD only frame transmission and the first significant path, of the downlink
DPCH frame from the measured radio link.
UE

Applicable for Connected-mode intra-frequency.

Range/ The UE Rx-Tx time difference is given with the resolution of 0.25 chip
mapping with the range [876, …, 1172] chips.

This corresponds to the Round Trip Time (RTT).

© ftw. 10.01.2002 23

FDD: 25.215 v. 3.2.0 Clause 5.1.11:

s e
Measurement shall be made for each cell included in the active set.
au :
e c cs
b pe
Note: The definition of "first significant path" needs further elaboration.

e d s
a t he
t d ft
ou n o
b ly sio
s i er
o s v IS
p old TH
is n N
e
g to a R
p rs LEA
a
h is fe T
t re O
it O N
D

23
 Observed time difference to GSM cell

Defined for The Observed time difference to GSM cell is defined as:
FDD & TDD
For FDD: TRxGSMj - TRxSFNi,

UE For TDD: TRxGSMk - TRxSFN0i

The value is reported in the unit [ms].

Applicable for Idle mode, connected mode inter-frequency

Range/ The Observed time difference to GSM cell is given with the resolution of
mapping 3060/(4096×13) ms with the range [0, …, 3060/13-3060/(4096×13)] ms.

NOTE: this is useful for preparing handover from UMTS to GSM.

© ftw. 10.01.2002 24

The beginning of the GSM BCCH 51-multiframe is defined as the beginning of the first tail
bit of the frequency correction burst in the first TDMA-frame of the GSM BCCH 51-
multiframe, i.e. the TDMA-frame following the IDLE-frame. s e
a u :
ec cs
FDD: 25.215 v. 3.2.0 Clause 5.1.12: e
bT ,pwhere:
The Observed time difference to GSM cell is defined as: T
e d s
- RxGSMj RxSFNi
T is the time at the beginning of the P-CCPCH frame with
a t SFN=0 he from cell i
T
RxSFNi
is the time at the beginning of the GSM BCCHtd
t
f from GSM frequency
51-multiframe
.

RxGSMj
o u o
j received closest in time after the time T
exactly at T then T =T (whichly
. If the
RxSFNi
leads to iTo
n - T = 0) The timing
next GSM multiframe is received
RxSFNi RxGSMj RxSFNi
measurement shall reflect the timing situation
s ibwhen the r s most recent (in time) P-CCPCH with
RxGSMj RxSFNi .

SFN=0 was received in the UE. s v e IS

po old TH
TDD: 25.225 v. 3.2.0 Clause 5.1.11: is n N
e
g to a R
Observed time difference to
T =T -T
a
p rs LE
GSM cell is the
A time difference T in ms, wherem

is of thefereceivedTframe SFN=0 of the serving TDD cell i

m RxGSMk RxSFN0i
TRxSFN0i h
: time of start
t rethe GSMOBCCH 51-multiframe of the considered target GSM
it closestOinNtime after the time T
TRxGSMk.
: time of start of
frequency k received RxSFN0i.

24
 UE GPS Timing of Cell Frames
for LCS
Defined for The timing between cell j and GPS Time Of Week. TUE-GPSj is
FDD only defined as the time of occurrence of a specified UTRAN event
according to GPS time. The specified UTRAN event is the
UE beginning of a particular frame (identified through its SFN) in the
first significant multipath of the cell j CPICH, where cell j is a cell
within the active set.
Applicable for Connected mode (intra- and inter-frequency)

Range/ The reporting range is from 0 ... 2319360000000 chip. The resolution of
mapping the reported value is 0.125 chip durations (i.e. 32.6 ns).

Resulting resolution in time = 32.6 ns.

Resulting resolution in space = 9.8 m.

The accuracy of this measurement is not yet defined.

© ftw. 10.01.2002 25

FDD: 25.215 v. 3.3.0 Clause 5.1.13.

s e
FDD: 25.133 v. 3.2.0 Clause 8.1.15.1.
a u :
See also 25.305 v. 3.2.0 Clause 10: Network assisted GPS location method.
ec cs
b pe
e d s
Accuracy requirements are still missing.
a t he
45 bits are needed to report the measurement value.
t d ft
o u o
2.31936e+12 chip durations = 60.4e+06 frameydurations
l o n= 604000 s = 6d 23h 46m 40s.
i
s ib ers
o s vin the UEISand it is only needed for certain
This measurement is optional for implementation
LCS methods involving GPS (i.e. not p evenoallldUEs with
T HLCS capabilities need this).
is n N
e
gperformed? a R
How is such a measurement
The Coarse/Acquisition a
pcode to A
Note that the chip rates of UMTS and GPS differ:
of GPS (akaE"civilian code“) is a sequence of 1023 pseudo-
is e s TonLthe GPS carrier at a chip rate of 1.023 MHz. The
random, binary, biphase r
modulations
th eisfvery long
Precise code („P-code“)
O sequence of pseudo random binary biphase modulations
t r N
on the GPS carrier at a chip rate of 10.23 MHz which repeats about every 267 days. Each one
i
DO
week segment of this code is unique to one GPS satellite and is reset each week.

25
 UTRAN measurement abilities

© ftw. 10.01.2002 26

If the UTRAN supports multiple frequency bands then the

UTRAN measurements apply for each frequency band individually.

26
 RSSI
Received Signal Strength Indicator
Defined for Received Signal Strength Indicator, the wide-band received power
FDD & TDD within the UTRAN uplink carrier channel bandwidth in an UTRAN
access point. The reference point for the RSSI measurements
shall be the antenna connector. (For TDD, this measurement shall
UTRAN be performed in a specified time-slot).

Range/ Resolution of 0.1dB with the range [-112, ..., -50] dBm. RSSI shall
mapping be reported in the unit RSSI_LEV
:
RSSI_LEV_000: RSSI < -112.0dBm
RSSI_LEV_001: -112.0dBm ≤ RSSI < –111.9dBm
RSSI_LEV_002: -111.9dBm ≤ RSSI < –111.8dBm
...
RSSI_LEV_620: -50.1dBm ≤ RSSI < –50.0dBm
RSSI_LEV_621: -50.0dBm ≤ RSSI

© ftw. 10.01.2002 27

This is a measurement performed on the uplink.

s e
u :
FDD: 25.215 v. 3.3.0 Clause 5.2.1 and 25.133 v. 3.2.0 Clause 8.2.1
a
TDD: 25.225 v. 3.3.0 Clause 5.2.3.
ec cs
b pe
ed s
Accuracy requirement +/- 4 dB
at he
t d ft
ou n o
b ly sio
s i er
o s v IS
p old TH
is n N
e
g to a R
p rs LEA
a
his fe T
t re O
it O N
D

27
 SIR
Signal to Interference Ratio
Defined for (RSCP / ISCP)×SF for FDD mode.
FDD & TDD (RSCP / Interference) ×SF for TDD mode.
Measurement shall be performed on the DPCCH of a Radio Link Set. In
UTRAN compressed mode the SIR shall not be measured in the transmission gap.
The reference point for the SIR measurements shall be the Rx antenna
connector.

Range/ The reporting range for SIR is from -11 ... 20 dB.
mapping The reporting resolution is 0.5 dB.

UTRAN_SIR_00: SIR < -11.0dB

UTRAN_SIR_01:-11.0dB ≤ SIR < -10.5dB
UTRAN_SIR_02:-10.5dB ≤ SIR < -10.0dB
....
UTRAN_SIR_61:19.0dB ≤ SIR < 19.5dB
UTRAN_SIR_62:19.5dB ≤ SIR < 20.0dB
UTRAN_SIR_63:20.0dB ≤ SIR

© ftw. 10.01.2002 28

This is a measurement performed on the uplink.

FDD: 25.133 v. 4.1.0 Clause 9.2.2

TDD: 25.123 v. 4.1.0 Clause 9.2.1.4
Accuracy requirement +/- 3 dB for both duplexing modes

FDD: 25.215 v. 4.1.0 Clause 5.2.2:

RSCP = Received Signal Code Power, the received power on one code.
ISCP = Interference Signal Code Power, the interference on the received
signal. Only the non-orthogonal part of the interference is included in the
measurement.
SF=The spreading factor used on the DPCCH.

TDD: 25.225 v. 4.1.0 Clause 5.2.4:

RSCP = Received Signal Code Power, the received power on the code of a
specified DPCH, PRACH or PUSCH.
Interference = the interference on the received signal in the same timeslot
which can’t be eliminated by the receiver.
SF = The used spreading factor.

28
 Transmitted carrier power

Defined for Ratio between the total transmitted power and the maximum
FDD & TDD transmission power. Total transmission power is the mean power
on one carrier from one UTRAN access point. The reference point
UTRAN shall be the antenna connector. In case of Tx diversity the
transmitted carrier power for each branch shall be measured.

Range/ The reporting range for Transmitted carrier power is from 0 ... 100 %.
mapping The reporting resolution is 1%.

© ftw. 10.01.2002 29

This is a measurement performed on the downlink.

FDD: 25.215 v. 3.3.0 Clause 5.2.3
s e
TDD: 25.225 v. 3.3.0 Clause 5.2.7
a u :
e c cs
b pe
e d s
FDD: 25.133 v. 3.2.0 Clause 8.2.3 t he
The measurement period shall be [100] ms. da t
t f
FDD accuracy +/- 5%
ou n o
b ly sio
TDD: 25.123 v. 3.2.0 Clause 9.2.2.1s i er
The output power is definedo assthe average
v power I Sof the transmit timeslot,
and is measured with a filter T H Cosine (RRC) impulse
p thatohaslda Root-Raised
response with a roll offisα = 0.22 N
n andRa bandwidth equal to the chip rate.
e
g10%to a
p rs LEA
TDD accuracy +/-
a
his fe T
t re O
it O N
D

29
 Transmitted code power

Defined for This is the transmitted power on one channelisation code on one
FDD & TDD scrambling code on one carrier. Measurement shall reflect the power on
the pilot bits of the DPCCH-field. When measuring the transmitted code
power in compressed mode all slots shall be included. The reference
UTRAN point shall be the antenna connector. In case of Tx diversity the
transmitted code power for each branch shall be summed in [W].

Range/ The reporting range for Transmitted code power is –10 ... 46 dBm
mapping The reporting resolution is 0.5 dB

© ftw. 10.01.2002 30

This is a measurement performed on the downlink.

FDD: 25.215 v. 3.3.0 Clause 5.2.4
s e
u :
Measurement shall be possible on the DPCCH-field of any dedicated radio
a
link transmitted from the UTRAN access point.
e c cs
When measuring the transmitted code power in compressed b themode p e slots
all
d
shall be included in the measurement, e.g. also the slots in s
transmission gap
shall be included in the measurement.
a te he
t d ft
TDD: 25.225 v. 3.3.0 Clause 5.2.8 ou n o
b ly power
Transmitted Code Power, is the transmitted
s io on one carrier and one
channelisation code in one timeslot.s i Theereference
r point for the transmitted
code power measurement shallsbe the antenna
o I S
v Hconnector at the UTRAN access
point cabinet. (cabinet ?) p d
l T
s
i n o N
e
g Clause a 8.2.4A R
FDD: 25.133 v. 3.2.0
a
p period to E[100] ms.
The measurement
r s L
shall be
is+/- 3 fdBe (abs) and
t re OT +/- 2 dB (rel)
h
Accuracy:

it 3.2.0NClause 9.2.2.1
TDD: 25.123 v. O
Accuracy: +/-D 3 dB (abs) and +/- 2 dB (rel)

30
 RSCP
Received Signal Code Power
Defined for Received Signal Code Power, the received power on one DPCH,
TDD only PRACH or PUSCH code. The reference point for the RSCP shall be the
antenna connector.
UTRAN

Range/ RSCP is given with a resolution of 0.5 dB with the range [-120, ..., -80]
mapping dBm. RSCP shall be reported in the unit RSCP_LEV where:

RSCP_LEV_00: RSCP < -120.0dBm

RSCP_LEV_01: -120.0dBm ≤ RSCP < -119.5dBm
RSCP_LEV_02: -119.5dBm ≤ RSCP < -119.0dBm
...
RSCP_LEV_79: -81.0dBm ≤ RSCP < -80.5dBm
RSCP_LEV_80: -80.5dBm ≤ RSCP < -80.0dBm
RSCP_LEV_81: -80.0dBm ≤ RSCP.

© ftw. 10.01.2002 31

This is a measurement performed on the uplink.

TDD: 25.225 v. 3.3.0 Clause 5.2.1

s e
TDD: 25.123 v. 3.2.0 Clause 9.2.1.1
a u :
Absolute accuracy: +/- 6 dB (normal conditions), e c cs
+/- 9 dB (extreme conditions). b pe
ed s
Relative accuracy: +/- 3 dB
a t he
t d ft
The RSCP can either be measured on theodata u part orothe midamble of a
ly o nHowever, in order to have
burst, since there is no power offset between
b on the i
both.
s midamble is assumed.
a common reference, the measurement
s i
(Remark: The problem of thesdownlink e
r
v I S
UE measurement P-CCPCH RSCP
o ld does notHexist for the uplink UTRAN
p
with a midamble-based measurement
measurement, becauseseach useroin uplinkTuses a different midamble)
i n N
e
g to a R
p rs LEA
a
h is fe T
t re O
it O N
D

31
 Transport channel BER

Defined for The TrCH BER is an estimate of the bit error rate (BER) of radiolink-
FDD & TDD combined xxxCH data. The TrCH BER is measured from the data
considering only non-punctured bits at the input of the channel decoder
in Node B. The reported TrCH BER shall be an estimate of the BER
UTRAN during the latest TTI for that TrCH.

Range/
mapping

© ftw. 10.01.2002 32

This is a measurement performed on the uplink.

e
It shall be possible to report a TrCH BER for a TrCH after the end of each
s
TTI of the TrCH.
au :
e c cs
e coded.
TrCH BER is only required to be reported for TrCHs thatbare channel
p
ed s
a t he
FDD: 25.215 v. 3.3.0 Clause 5.2.5
t d ft
o no
xxxCH = „DPDCH“ = Dedicated physicaludata channel

b ly sio
TDD: 25.225 v. 3.3.0 Clause 5.2.5i r
s e
s= Dedicated- IS Shared Channel
v orHUplink
xxxCH = „DCH“ or „USCH“ o
p old T
s 9.2.1.7
iClause n RN
e
TDD: 25.123 v. 3.2.0
g Clause a
FDD: 25.133 v.a3.2.0
p to 8.2.8
E A
r s areLspecified yet.
s requirements
No accuracy
i
th refe OT
it O N
D

32
 RTT Round Trip Time

Defined for Round trip time is defined as RTT = TRX – TTX, where
FDD only
TTX = The time of transmission of the beginning of a downlink DPCH
frame to a UE.
UTRAN TRX = The time of reception of the beginning (the first significant path)
of the corresponding uplink DPCCH/DPDCH frame from the UE.
Applicable for

Range/ The Round trip time reporting range is from 876.00 ... 2923.50 chip with
mapping a resolution of 0.25 chip durations.

© ftw. 10.01.2002 33

FDD: 25.215 v. 3.3.0 Clause 5.2.7

e
Note: The definition of "first significant path" needs further elaboration.
s
Measurement shall be possible on DPCH for each RL transmittedufrom an :
c a in thessame
UTRAN access point and DPDCH/DPCCH for each RL received
UTRAN access point. Measurement shall be possible onb
c RL
e foreeach
d
transmitted from an UTRAN access point and DPDCH/DPCCH
DPCH
spfor each RL
received in the same UTRAN access point.
a te he
t d ft
FDD: 25.133 v. 3.2.0 Clause 8.2.7 ou n o
ly sio
Accuracy: +/- 0.5 chip durations i
s b r
s v IS e
o
p... old TH
is n
Useful for handover, LCS,
N130 m in range.
e
+/- 0.5 chip durations
g to a
correspond R
to +/-

p rs LEA
a
h is fe T
t re O
it O N
D

33
 RX Timing Deviation

Defined for ‘RX Timing Deviation’ is the time difference TRXdev = TTS – TRXpath
TDD only in chips. TRXpath is the time of the reception in the Node B of the first
significant uplink path to be used in the detection process. TTS: time of
the beginning of the respective slot according to the Node B internal
UTRAN timing.

Applicable for

Range/ RX Timing Deviation is given with a resolution of 0.25 chip with the range
mapping [-256; 256) chips (11 bit).

RX Timing Deviation cell shall be reported in the unit RX_TIME_DEV,

where

RX_TIME_DEV: (n/4 –256) chips ≤ RX Timing Deviation < ((n+1)/4 –256)

chips with n = 0, 1, 2, ..., 2047.

© ftw. 10.01.2002 34

TDD: 25.215 v. 3.3.0 Clause 5.2.9

e
This measurement can be used for timing advance calculation or
s
location services.
au :
ec cs
TDD: 25.123 v. 3.2.0 Clause 8.2. b pe
ed s
Accuracy: +/- 0.5 chip durations
a t he
t d ft
Useful for handover, LCS, ... ou n o
ly sio
b
i +/- 130
+/- 0.5 chip durations correspond to
s r m in range.
s v IS e
o
p old TH
is n N
e
g to a R
p rs LEA
a
h is fe T
t re O
it O N
D

34
Skipped UTRAN Measurements
in this Talk:

ƒ FDD: ƒ TDD:
ƒ Timeslot ISCP
ƒ Physical Channel BER ƒ Physical Channel BER
ƒ UTRAN GPS Timing of
Cell Frames for LCS
ƒ PRACH/PCPCH
Propagation Delay
ƒ Acknowledged PRACH
Preambles
ƒ ....

© ftw. 10.01.2002 35

35
Conclusions

FDD and TDD definitions are quite well harmonised.

Uplink vs. Downlink show strong asymmetry in some

measurement definitions.

© ftw. 10.01.2002 36

36