Physical Layer Measurements

8/8/2019 Physical Layer Measurements

1/361

Forschungszentrum

Telekommunikation

Wien

An initiative of theKplusProgramme

Physical Layer Measurements

Christoph Mecklenbruker

[email protected]

3GPP Release 4 (June 2001)

Physical Layer Specifications:

FDD: 25.215 v 4.1.0 (June01)TDD: 25.225 v 4.1.0 (June01)

Layer-2: Measurement Model:25.302 v 4.1.0 (June01)

Layer-3: Requesting Reports25.331 v 4.1.0 (June01)

WG4: Accuracy and testing

TDD: 25.123 v 4.1.0 (June01)FDD: 25.133 v 4.1.0 (June01)


2/362

ftw. 10.01.2002 2

Concepts and Principles

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 RadioAccess 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).


3/363

ftw. 10.01.2002 3

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

MEASUREMENT CONTROL

setup, modify, or releasea UE measurement

UE UTRAN

MEASUREMENT REPORT

UE measurement report:normal case (no failure)

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 aredescribed 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).


4/364

ftw. 10.01.2002 4

Layer-2 Model of physical layer

measurements

Layer 1filtering

Layer 3filtering Evaluation

of reporting

criteria

A DB C

C'

parameters parameters

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


5/365

ftw. 10.01.2002 5

Types of UE measurements

- Intra-frequency measurements: on DL phys. channels atthe 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.

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.


6/366

ftw. 10.01.2002 6

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

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.


7/367

ftw. 10.01.2002 7

Range, mapping, and accuracy

The WG1 specs (25.215, 25.225) define themeasurement 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.

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


8/368

ftw. 10.01.2002 8

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.

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


9/369

ftw. 10.01.2002 9

Compressed Mode (FDD only)

Details

Transmission

Transmission gap 2

gap 2

TGSN TGSN

TGL2 TGL2

TG pattern 2

#TGPRC

gap 1

Transmission Transmission

gap 1

TGD TGD

TGPL1 TGPL2

TG pattern 1 TG pattern 2

TGL1 TGL1

#1 #2 #3 #4 #5

TG pattern 1TG pat tern 1 TG pattern 2 TG pattern 1 TG pattern 2

Provision for measurements

involving signals from other cells

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.


10/3610

ftw. 10.01.2002 10

UE measurement abilities


11/3611

ftw. 10.01.2002 11

Defined forFDD & TDD.

Received power on one code measured on the Primary CPICH. The

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

each antenna shall be separately measured and summed together in [W]

to a total received code power on the Primary CPICH.

Applicable for

Range/

mapping

CPICH RSCP is given with a resolution of 1 dB with the range

[-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

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

For TDD: Idle-mode, Connected-mode inter-frequency

CPICH RSCPReceived Signal Code Power

UE

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.


12/3612

ftw. 10.01.2002 12

Defined forFDD & TDD.

Received Signal Code Power, the received power on one code measured

on the P-CCPCH from a TDD cell. The reference point for the RSCP is

the antenna connector at the UE.

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

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

Range/

mapping

Identical to CPICH RSCP

P-CCPCH RSCPReceived Signal Code Power

UE

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.


13/3613

ftw. 10.01.2002 13

Defined forTDD only.

Interference Signal Code Power, the interference on the received signal

in a specified timeslot measured on the midamble. The reference point

for the ISCP is the antenna connector at the UE.

Applicable for For TDD: Connected-mode intra-frequency

Range/

mappingTimeslot ISCP is given with a resolution of 0.5 dB with the range

[-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_91: -25 dBm Timeslot_ISCP

Timeslot ISCPInterference Signal Code Power

UE

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.0Clause 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.


14/3614

ftw. 10.01.2002 14

Defined for

FDD & TDD.

Signal to Interference Ratio, defined as:

(RSCP / Interference) (SF)

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

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

Range/

mapping

SIR is given with a resolution of 0.5 dB with the range [-11, ..., 20] dB.

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

SIRSignal to Interference Ratio

UE

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 cant be eliminated by the receiver. (Remark: the measurement resultdepends on the receiver type!)

25.133 v. 3.2.0:

Accuracy requirement +/- 3dB.


15/3615

ftw. 10.01.2002 15

Defined for

FDD & TDD.

Received Signal Strength Indicator, the wide-band received power

within the relevant channel bandwidth. Measurement shall be performedon a UTRAN downlink carrier. The reference point for the RSSI is the

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/

mapping

UTRA carrier RSSI is given with a resolution of 1 dB with the range

[-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

UTRA Carrier RSSIReceived Signal Strength Indicator

UE

FDD: 25.215 v. 3.2.0 Clause 5.1.4:

TDD: 25.225 v. 3.2.0 Clause 5.1.4:

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


16/3616

ftw. 10.01.2002 16

Defined for

FDD & TDD.


within the relevant channel bandwidth. Measurement shall be performedon a GSM BCCH carrier. The reference point for the RSSI is the

antenna connector at the UE. (For TDD, this measurement is performed

in a specified timeslot).

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

Range/

mapping

According to the definition of RXLEV in GSM 05.08.

RXLEV 0 = less than -110dBm.

RXLEV 1 = -110 dBm to -109 dBm.


:


RXLEV 63 = greater than -48 dBm.

GSM Carrier RSSIReceived Signal Strength Indicator

UE

FDD: 25.215 v. 3.2.0 Clause 5.1.5:

TDD: 25.225 v. 3.2.0 Clause 5.1.5:

GSM Recommendation 05.08 (Radio Subsystem Link Control)

GSM 05.08 v. 3.8.0 Clause 8.1.4:

The received signal level shall be mapped to an RXLEV value between 0 and

63, as follows :

RXLEV 0 = less than -110dBm.RXLEV 1 = -110 dBm to -109 dBm.


:


RXLEV 63 = greater than -48 dBm.

6 bits are required to define RXLEV for each carrier measured.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


17/3617

ftw. 10.01.2002 17

Defined for

FDD & TDD.

Received energy per chip (Ec) divided by power density in the band.

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

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/

mappingCPICH Ec/No is given with a resolution of 1 dB with the range [-24,

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

CPICH Ec/No

UE

FDD: 25.215 v. 3.2.0 Clause 5.1.6:

TDD: 25.225 v. 3.2.0 Clause 5.1.7:

This measurement is used monitoring FDD cells (regardless of theduplexing-mode that the UE is currently using)

Observe that the definition of CPICHEc/No measurement is slightlyincorrect because the energy per chipEc is actually divided by the totalpower spectral density in the band which is not the same as the

noise+interference power spectral densityNo.

Also, the UTRA Carrier RSSI measurements are defined as absolutepower levels (reported in dBm units) rather than a power spectraldensity (mW/Hz). Therefore, UTRA Carrier RSSI measurements

reportNoB whereB is the noise-equivalent bandwidth of the receiver

front-end:B = 4.2 MHz (somewhat smaller than 5 MHz).

thisp

agei

spos

siblyoutda

tedbeca

use

itre

ferst

oano

ldversio

nofth

espe

cs:

DONO

TLE

ARNTH

IS


18/3618

ftw. 10.01.2002 18

Defined for

FDD & TDD.

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

For TDD: Connected-mode intra-frequency.

Range/

mapping

Transport channel BLER is given with a logarithmic resolution of0.065 with the range [10^-4.03 ... 1] including a separate caseBLER=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.965BLER_LOG_03: -3.965 log10(BLER) < -3.900...BLER_LOG_63: -0.065 log10(BLER) 0.000

Estimation of the transport channel block error rate (BLER). The BLER

estimation shall be based on evaluating the CRC on each transport

block.

Transport Channel BLER

UE

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

On an AWGN channel, it is easy to calculate how many transport blocksn have to betransmitted for reaching a desired level of accuracy of this measurement. In this case, the

numberk of CRC failures is binomially distributed B(n,k,p) where BLER=p.

Example: For a transport channel showing BLER = 0.01 using interleaving-depth of 4

frames per block, the confidence-level is 70 %, that the measured BLER is inside the

interval of 0.01 20%, i. e. in the interval 0.008 .... 0.012, after a measurement time of

approx. 2 minutes.

FDD: 25.133 v. 3.2.0 Clause 8.1.7 & TDD: 25.123 v. 3.2.0 Clause 9.1.1.6

Transport channel BLER value shall be calculated from a window with the size equal to

the reporting interval (see section 10.3.7.78 Periodical reporting criteria in TS 25.331).

FDD: 25.215 v. 3.2.0 Clause 5.1.7:

For FDD: The CRC is evaluated after RL combination. BLER estimation is only required

for transport channels containing CRC. In connected mode the BLER shall be possible to

measure on any transport channel. If requested in idle mode it shall be possible to measure

the BLER on transport channel PCH.

TDD: 25.225 v. 3.2.0 Clause 5.1.8.thi

spag

eisp

ossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


19/3619

ftw. 10.01.2002 19

Defined for

FDD & TDD.

The total UE transmitted power on one carrier. The reference point for

the UE transmitted power shall be the UE antenna connector.

For TDD: Measurement is performed on a specified timeslot.

Applicable for Connected-mode intra-frequency.

Range/

mapping

UE transmitted power is given with a resolution of 1dB with therange [-50, ..., 33] dBm. UE transmitted power shall be reported inthe unit UE_TX_POWER:

UE_TX_POWER_000 to UE_TX_POWER_020: reserved

UE_TX_POWER_021: -50dBm UE_transmitted_power < -49dBmUE_TX_POWER_022: -49dBm UE_transmitted_power < -48dBmUE_TX_POWER_023: -48dBm UE_transmitted_power < -47dBm...UE_TX_POWER_104: 33dBm UE_transmitted_power < 34dBm

UE Transmitted Power

UE

FDD: 25.215 v. 3.2.0 Clause 5.1.8:

TDD: 25.225 v. 3.2.0 Clause 5.1.9:

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


20/3620

ftw. 10.01.2002 20

Defined for

FDD & TDD

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

Range/

mapping

The SFN-CFN observed time difference to cell is defined as:

OFF 38400 + Tm, where: Tm= (TUETx-T0) - TRxSFN, given in chipunits. It is not required to read cell SFN of the target neighbour cellin compressed mode.

Time difference is given with the resolution of one chip with the range

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

SFN-CFN observed time difference

UE

25.215 v. 3.2.0 Clause 5.1.9:

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

0is defined in TS 25.211 subclause 7.1.3.

TRxSFN

is the time at the beginning of the neighbouring P-CCPCH frame receivedmost recent in time before the time instant T

UETx-T

0in the UE.

OFF=(SFN-CFNTx

) mod 256, given in number of frames with the range [0, 1, , 255]frames.

CFNTx

is the connection frame number for the UE transmission of an uplinkDPCCH/DPDCH frame at the time T

UETx. SFN is the system frame number for the

neighbouring P-CCPCH frame received in the UE at the time TRxSFN.

In case the inter-frequency measurement is done with compressed mode, the valuefor the parameter OFF is always reported to be 0. This is an interesting special case

useful for LCS (location services). In case that the SFN measurement indicatorindicates that the UE does not need to read cell SFN of the target neighbour cell, thevalue of the parameter OFF is always be set to 0.

9830399 = (256 x 38400) 1 = (255 x 38400) + 38399.

For TDD: newly introduced during RAN WG1#14, June00, Tdoc R1-00-0911:Change Request 25.225 CR 013rev1. However the TDD measurement is definedquite differently. (see below).

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


21/3621

ftw. 10.01.2002 21

Defined for

FDD & TDD

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

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

Range/

mapping

The SFN-SFN observed time difference to cell is defined as:

OFF38400+ Tm, where:

Tm= TRxSFNj - TRxSFNi, given in chip units with the range

[0, 1, , 38399] chips

Time difference is given with the resolution of one chip with the range

[0, , 9830399] chips.

NOTES:

1) This is useful for handover.

2) Regarding LCS: (maybe Type 1 isnot usedfor LCS)

Resulting resolution in time = 260 ns.

Resulting resolution in space = 78 m.

SFN-SFN observed time difference

(Measurement Type 1)

UE

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

TRxSFNj is the time at the beginning of a received neighbouring P-CCPCH frame from cell j.T

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

OFF=(SFNi- SFN

j) mod 256, given in number of frames with the range [0, 1, , 255] frames.

SFNj

is the system frame number for downlink P-CCPCH frame from cell j in the UE at the

time TRxSFNj

.

SFNiis the system frame number for the P-CCPCH frame from cell i received in the UE at

the time TRxSFNi

.

TDD: 25.225 v. 3.2.0 Clause 5.1.10: Type 1

SFN-SFN observed time difference is the time difference of the reception times of framesfrom two cells (serving and target) measured in the UE and expressed in chips.

Tm

= TRxSFNi

- TRxSFNk

, given in chip units with the range [0, 1, , 38399] chips

TRxSFNi

: time of start of the received frame SFNiof the serving TDD cell i.

TRxSFNk

: time of start of the received frame SFNk

of the target UTRA cell k received most

recent in time before the time instant TRxSFNi

in the UE.

OFF=(SFNi- SFN

k) mod 256, given in number of frames with the range [0, 1, , 255]

frames.

SFNi: system frame number for downlink frame from serving TDD cell i in the UE at the

time TRxSFNi

.

SFNk: system frame number for downlink frame from target UTRA cell k received in the UEat the time T

RxSFNk.(for FDD: the P-CCPCH frame)

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


22/3622

ftw. 10.01.2002 22

Defined for

FDD & TDD

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

Range/

mapping

FDD: The relative timing difference between cell j and cell i,

defined as TCPICHRxj TCPICHRxi.

TDD: SFN-SFN observed time difference = TRxTSk - TRxTSi,

Time difference is given with the resolution of 0.25 chip (but with an

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.

SFN-SFN observed time difference(Measurement Type 2)

UE

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

difference of arrival (OTDOA-IPDL), but this measurement is not restricted to OTDOA-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)

FDD: 25.215 v. 3.2.0 Clause 5.1.10: Type 2

The relative timing difference between cell j and cell i, defined as

TCPICHRxj

- TCPICHRxi

,

where:

TCPICHRxj

is the time when the UE receives one Primary CPICH slot from cell j

TCPICHRxi is the time when the UE receives the Primary CPICH slot from cell i that is closestin time to the Primary CPICH slot received from cell j

TDD: 25.225 v. 3.2.0 Clause 5.1.10: Type 2

SFN-SFN observed time difference defined das

TRxTSk

- TRxTSi

, in chips,

where;

TRxTSi

: time of start of a timeslot received of the serving TDD cell i.

TRxTSk

:time of start of a timeslot received from the target UTRA cell k that is closest in

time to the start of the timeslot of the serving TDD cell i.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


23/3623

ftw. 10.01.2002 23

Defined for

FDD only

Applicable for Connected-mode intra-frequency.

Range/

mapping

The difference in time between the UE uplink DPCCH / DPDCH

frame transmission and the first significant path, of the downlinkDPCH frame from the measured radio link.

The UE Rx-Tx time difference is given with the resolution of 0.25 chip

with the range [876, , 1172] chips.

This corresponds to the Round Trip Time (RTT).

UE Rx-Tx time difference

UE

FDD: 25.215 v. 3.2.0 Clause 5.1.11:

Measurement shall be made for each cell included in the active set.

Note: The definition of "first significant path" needs further elaboration.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


24/3624

ftw. 10.01.2002 24

Defined for

FDD & TDD

Applicable for Idle mode, connected mode inter-frequency

Range/

mapping

The Observed time difference to GSM cell is defined as:

For FDD: TRxGSMj - TRxSFNi,

For TDD: TRxGSMk - TRxSFN0i

The value is reported in the unit [ms].

The Observed time difference to GSM cell is given with the resolution of

3060/(409613) ms with the range [0, , 3060/13-3060/(409613)] ms.

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

Observed time difference to GSM cell

UE

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.

FDD: 25.215 v. 3.2.0 Clause 5.1.12:

The Observed time difference to GSM cell is defined as: TRxGSMj

- TRxSFNi

, where:

TRxSFNi

is the time at the beginning of the P-CCPCH frame with SFN=0 from cell i.

TRxGSMj

is the time at the beginning of the GSM BCCH 51-multiframe from GSM frequency

j received closest in time after the time TRxSFNi

. If the next GSM multiframe is received

exactly at TRxSFNi

then TRxGSMj

=TRxSFNi

(which leads to TRxGSMj

- TRxSFNi

= 0).The timing

measurement shall reflect the timing situation when the most recent (in time) P-CCPCH withSFN=0 was received in the UE.

TDD: 25.225 v. 3.2.0 Clause 5.1.11:

Observed time difference to GSM cell is the time difference Tm

in ms, where

Tm

= TRxGSMk

- TRxSFN0i

TRxSFN0i

: time of start of the received frame SFN=0 of the serving TDD cell i

TRxGSMk.

: time of start of the GSM BCCH 51-multiframe of the considered target GSM

frequency k received closest in time after the time TRxSFN0i.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


25/3625

ftw. 10.01.2002 25

Defined for

FDD only

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

Range/

mapping

The timing between cell j and GPS Time Of Week. TUE-GPSj is

defined as the time of occurrence of a specified UTRAN eventaccording to GPS time. The specified UTRAN event is thebeginning of a particular frame (identified through its SFN) in thefirst significant multipath of the cell j CPICH, where cell j is a cellwithin the active set.

The reporting range is from 0 ... 2319360000000 chip. The resolution of

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.

UE GPS Timing of Cell Framesfor LCS

UE

FDD: 25.215 v. 3.3.0 Clause 5.1.13.

FDD: 25.133 v. 3.2.0 Clause 8.1.15.1.

See also 25.305 v. 3.2.0 Clause 10: Network assisted GPS location method.

Accuracy requirements are still missing.

45 bits are needed to report the measurement value.

2.31936e+12 chip durations = 60.4e+06 frame durations = 604000 s = 6d 23h 46m 40s.

This measurement is optional for implementation in the UE and it is only needed for certain

LCS methods involving GPS (i.e. not even all UEs with LCS capabilities need this).

How is such a measurement performed? Note that the chip rates of UMTS and GPS differ:

The Coarse/Acquisition code of GPS (aka "civilian code) is a sequence of 1023 pseudo-

random, binary, biphase modulations on the GPS carrier at a chip rate of 1.023 MHz. The

Precise code (P-code) is very long sequence of pseudo random binary biphase modulations

on the GPS carrier at a chip rate of 10.23 MHz which repeats about every 267 days. Each one

week segment of this code is unique to one GPS satellite and is reset each week.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


26/3626

ftw. 10.01.2002 26

UTRAN measurement abilities

If the UTRAN supports multiple frequency bands then the

UTRAN measurements apply for each frequency band individually.


27/3627

ftw. 10.01.2002 27

Defined for

FDD & TDD

Range/

mapping


within the UTRAN uplink carrier channel bandwidth in an UTRANaccess point. The reference point for the RSSI measurementsshall be the antenna connector. (For TDD, this measurement shallbe performed in a specified time-slot).

Resolution of 0.1dB with the range [-112, ..., -50] dBm. RSSI shallbe reported in the unit RSSI_LEV

:RSSI_LEV_000: RSSI < -112.0dBm

RSSI_LEV_001: -112.0dBm RSSI < 111.9dBmRSSI_LEV_002: -111.9dBm RSSI < 111.8dBm...RSSI_LEV_620: -50.1dBm RSSI < 50.0dBmRSSI_LEV_621: -50.0dBm RSSI

RSSIReceived Signal Strength Indicator

UTRAN

This is a measurement performed on the uplink.

FDD: 25.215 v. 3.3.0 Clause 5.2.1 and 25.133 v. 3.2.0 Clause 8.2.1

TDD: 25.225 v. 3.3.0 Clause 5.2.3.

Accuracy requirement +/- 4 dB

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


28/3628

ftw. 10.01.2002 28

Defined for

FDD & TDD

Range/

mapping

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

UTRAN_SIR_00: SIR < -11.0dB

UTRAN_SIR_01:-11.0dB SIR < -10.5dBUTRAN_SIR_02:-10.5dB SIR < -10.0dB....UTRAN_SIR_61:19.0dB SIR < 19.5dBUTRAN_SIR_62:19.5dB SIR < 20.0dBUTRAN_SIR_63:20.0dB SIR

(RSCP / ISCP)SF for FDD mode.

(RSCP / Interference) SF for TDD mode.

Measurement shall be performed on the DPCCH of a Radio Link Set. Incompressed mode the SIR shall not be measured in the transmission gap.The reference point for the SIR measurements shall be the Rx antennaconnector.

SIRSignal to Interference Ratio

UTRAN


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

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 cant be eliminated by the receiver.

SF = The used spreading factor.


29/3629

ftw. 10.01.2002 29

Defined for

FDD & TDD

Range/

mapping

The reporting range for Transmitted carrier poweris from 0 ... 100 %.The reporting resolution is 1%.

Ratio between the total transmitted power and the maximumtransmission power. Total transmission power is the mean poweron one carrier from one UTRAN access point. The reference pointshall be the antenna connector. In case of Tx diversity the

transmitted carrier power for each branch shall be measured.

Transmitted carrier power

UTRAN

This is a measurement performed on the downlink.

FDD: 25.215 v. 3.3.0 Clause 5.2.3

TDD: 25.225 v. 3.3.0 Clause 5.2.7

FDD: 25.133 v. 3.2.0 Clause 8.2.3

The measurement period shall be [100] ms.

FDD accuracy +/- 5%

TDD: 25.123 v. 3.2.0 Clause 9.2.2.1

The output power is defined as the average power of the transmit timeslot,

and is measured with a filter that has a Root-Raised Cosine (RRC) impulse

response with a roll off = 0.22 and a bandwidth equal to the chip rate.

TDD accuracy +/- 10%

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


30/3630

ftw. 10.01.2002 30

Defined for

FDD & TDD

This is the transmitted power on one channelisation code on one

scrambling code on one carrier. Measurement shall reflect the power onthe pilot bits of the DPCCH-field. When measuring the transmitted code

power in compressed mode all slots shall be included. The reference

point shall be the antenna connector. In case of Tx diversity the

transmitted code power for each branch shall be summed in [W].

Range/

mapping

The reporting range for Transmitted code poweris 10 ... 46 dBmThe reporting resolution is 0.5 dB

Transmitted code power

UTRAN

This is a measurement performed on the downlink.

FDD: 25.215 v. 3.3.0 Clause 5.2.4

Measurement shall be possible on the DPCCH-field of any dedicated radio

link transmitted from the UTRAN access point.

When measuring the transmitted code power in compressed mode all slots

shall be included in the measurement, e.g. also the slots in the transmission gap

shall be included in the measurement.

TDD: 25.225 v. 3.3.0 Clause 5.2.8

Transmitted Code Power, is the transmitted power on one carrier and one

channelisation code in one timeslot. The reference point for the transmittedcode power measurement shall be the antenna connector at the UTRAN access

point cabinet. (cabinet ?)

FDD: 25.133 v. 3.2.0 Clause 8.2.4

The measurement period shall be [100] ms.

Accuracy: +/- 3 dB (abs) and +/- 2 dB (rel)

TDD: 25.123 v. 3.2.0 Clause 9.2.2.1

Accuracy: +/- 3 dB (abs) and +/- 2 dB (rel)

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


31/3631

ftw. 10.01.2002 31

Defined for

TDD only

Received Signal Code Power, the received power on one DPCH,

PRACH or PUSCH code. The reference point for the RSCP shall be theantenna connector.

Range/

mapping

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

RSCP_LEV_00: RSCP < -120.0dBm

RSCP_LEV_01: -120.0dBm RSCP < -119.5dBmRSCP_LEV_02: -119.5dBm RSCP < -119.0dBm...RSCP_LEV_79: -81.0dBm RSCP < -80.5dBmRSCP_LEV_80: -80.5dBm RSCP < -80.0dBmRSCP_LEV_81: -80.0dBm RSCP.

RSCPReceived Signal Code Power

UTRAN


TDD: 25.225 v. 3.3.0 Clause 5.2.1TDD: 25.123 v. 3.2.0 Clause 9.2.1.1

Absolute accuracy: +/- 6 dB (normal conditions),

+/- 9 dB (extreme conditions).

Relative accuracy: +/- 3 dB

The RSCP can either be measured on the data part or the midamble of a

burst, since there is no power offset between both. However, in order to have

a common reference, the measurement on the midamble is assumed.(Remark: The problem of the downlink UE measurement P-CCPCH RSCP

with a midamble-based measurement does not exist for the uplink UTRAN

measurement, because each user in uplink uses a different midamble)

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


32/3632

ftw. 10.01.2002 32

Defined for

FDD & TDD

The TrCH BER is an estimate of the bit error rate (BER) of radiolink-

combinedxxxCH data. The TrCH BER is measured from the dataconsidering 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

during the latest TTI for that TrCH.

Range/

mapping

Transport channel BER

UTRAN


It shall be possible to report a TrCH BER for a TrCH after the end of eachTTI of the TrCH.

TrCH BER is only required to be reported for TrCHs that are channel coded.

FDD: 25.215 v. 3.3.0 Clause 5.2.5

xxxCH = DPDCH = Dedicated physical data channel

TDD: 25.225 v. 3.3.0 Clause 5.2.5xxxCH = DCH or USCH = Dedicated- or Uplink Shared Channel

TDD: 25.123 v. 3.2.0 Clause 9.2.1.7

FDD: 25.133 v. 3.2.0 Clause 8.2.8

No accuracy requirements are specified yet.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


33/3633

ftw. 10.01.2002 33

Defined for

FDD only

Applicable for

Range/

mapping

Round trip time is defined as RTT = TRX TTX, where

TTX = The time of transmission of the beginning of a downlink DPCH

frame to a UE.

TRX = The time of reception of the beginning (the first significant path)

of the corresponding uplink DPCCH/DPDCH frame from the UE.

TheRound trip time reporting range is from 876.00 ... 2923.50 chip with

a resolution of 0.25 chip durations.

RTT Round Trip Time

UTRAN

FDD: 25.215 v. 3.3.0 Clause 5.2.7

Note: The definition of "first significant path" needs further elaboration.

Measurement shall be possible on DPCH for each RL transmitted from an

UTRAN access point and DPDCH/DPCCH for each RL received in the same

UTRAN access point. Measurement shall be possible on DPCH for each RL

transmitted from an UTRAN access point and DPDCH/DPCCH for each RL

received in the same UTRAN access point.

FDD: 25.133 v. 3.2.0 Clause 8.2.7

Accuracy: +/- 0.5 chip durations

Useful for handover, LCS, ...

+/- 0.5 chip durations correspond to +/- 130 m in range.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


34/3634

ftw. 10.01.2002 34

Defined for

TDD only

Applicable for

Range/

mapping

RX Timing Deviation is given with a resolution of 0.25 chip with the range[-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.

RX Timing Deviation is the time difference TRXdev = TTS TRXpath

in chips. TRXpath is the time of the reception in the Node B of the firstsignificant uplink path to be used in the detection process. TTS: time of

the beginning of the respective slot according to the Node B internal

timing.

RX Timing Deviation

UTRAN

TDD: 25.215 v. 3.3.0 Clause 5.2.9

This measurement can be used for timing advance calculation or

location services.

TDD: 25.123 v. 3.2.0 Clause 8.2.

Accuracy: +/- 0.5 chip durations

Useful for handover, LCS, ...

+/- 0.5 chip durations correspond to +/- 130 m in range.

thisp

agei

spossib

lyou

tdated

because

itrefe

rsto

anoldvers

ionof

thes

pecs

:

DONOT

LEAR

NTH

IS


35/3635

ftw. 10.01.2002 35

Skipped UTRAN Measurements

in this Talk:

FDD:

Physical Channel BER

UTRAN GPS Timing of

Cell Frames for LCS

PRACH/PCPCH

Propagation Delay

Acknowledged PRACH

Preambles ....

TDD:

Timeslot ISCP

Physical Channel BER


36/36

ftw. 10.01.2002 36

Conclusions

FDD and TDD definitions are quite well harmonised.

Uplink vs. Downlink show strong asymmetry in somemeasurement definitions.

Documents

Physical Layer Measurements