Nemo Analysis Workshop

Topics
1.Nemo Events and Definition

2.RRC and Layer3 messages
3.SIB Information,Measument Control (MC),Measurement Report
(MR)
4.CS and PS Call Flow
5.Cell Reselection, SHO and ISHO
Nemo Events and
Definitions
Nemo Events and
Definitions
MOC/MTC Call Flow timing
M
T
MOC C
Nemo Events and
Definitions
Block error ratio:BLER is measured from the CRC
– Transport Block (TB) is a basic unit that is
exchanged between Layer 1 and Layer 2 (MAC).
Layer 1 adds CRC for each TB and BLER is
calculated from the CRC
Cell update causes in priority order:
• Uplink data transmissionin URA_PCH,
CELL_PACH
• Paging response in URA_PCH,
CELL_PACH
• Radio link failure in CELL_DCH (*)
• Re-entering service area in
When do I CELL_FACH, CELL_PCH
have to • RLC unrecoverable error in all sub-
perform a states
cell/ URA • Cell reselection in CELL_FACH,
update? CELL_PCH
• Periodical cellupdate
update causes
in
URA in priority
CELL_FACH, CELL_PCH
order:
(the UE is in the URA_PCH sub-
state)
• URA reselection
• Periodic URA update
RRC and Layer-3
Messages
System Information Blocks
(SIB)
RRC Modes
CELL_FACH
CELL_DCH
• DCCH and – if configured –
• DCCH and – if configured –
DTCH
DTCH
• FACH used for higher layer
• Dedicate physical channel in
data transfer,
use
• UE monitors FACH
• UE location known on active
permanently
set cell level
• Uplink transmission on RACH
• UE responsible for
• UE location known on serving
measurement reporting
• Cell system information on cell level
• UE performs cell re-selection
BCCH
• UE responsible for
• RRC messages on DCCH
measurement reporting
• Cell system information on
BCCH
CELL_PCH and URA_PCH • RRC messages on BCCH,
CCCH and DCCH
• no DCCH and DTCH
• Before uplink transmission ⇒ UE moves to
CELL_FACH
• UE must be paged
• RRC messages on BCCH and PCCH
• In CELL_PCH
- UE location known on cell level
- UE performs cell re-selection and cell updates
• In CELL URA
- UE location known on URA level
- UE performs cell re-selection and URA updates
What are the characteristics of the individual sub-states, when the UE is in the RRC connected mode?
• CELL_DCH
In this sub-state, dedicated physical channels are allocated to the UE. DCCH and – if configured – DTCH information can
be transmitted. There no need to identify the UE on a dedicated channel, because the physical channels are exclusively
allocated to this UE. UTRAN knows the active set cells for the radio links and thus the location of the the UE. Also
downlink shared channels can be allocated to the UE.
In this state, the UE is capable to receive RRC messages on the DCCH (and BCCH, if it owns specific capabilities). The
cell system information is broadcasted on the FACH. The UE reads the cell system information and acts accordingly. For
instance, it determines the measurement quality and the reporting events from the cell system information.
• CELL_FACH
This state was introduced for traffic situations, where only small amounts of data have to be transmitted. This is the
case when only higher layer signalling information (NAS signalling) or small amount of user data (e.g. SMS messages)
have to be transmitted. In this case, an exclusive allocation of one physical channel to the UE would result in a waste of
resources.
• The UE is capable to receive and transmit DCCH and – if configured – DTCH information. Only common transport
channel FACH can be used by the UE to transmit higher layer data, which it has to share with other UEs. Each UE must
be explicitly addressed, for instance by the RNTI. It has to monitor the FACH permanently in the downlink, not to miss
user data for it. The UE‘s FACH is mapped on one S-CCPCH. In the uplink, it uses the shared transport channels for user
data transfer, such as the RACH.
The UE is only connected to one cell, and this is the location information, known within UTRAN. No soft handover takes
place in this sub-state. The UE is responsible for cell re-selection. By listening to the cell system information from the
BCCH, it gains all relevant measurement qualities, threshold values, neighbourhood lists to perform the cell re-selection
process. Other relevant information is also learned from the BCCH. The UE receives RRC messages on the BCCH, CCCH
and DCCH channels.
• CELL_PCH
Due to the discontinuous type of traffic, UTRAN can command the UE to perform periodic cell updates.
In this sub-state, the UE‘s current cell is known to the RNC. If the RNC wants to exchange data with the UE, it only needs
to page the UE there. If the UE changes the cell, it must perform a cell update. Also periodical cell updates can be
requested by UTRAN. To perform updates, the UE must change to the CELL_FACH sub-state. (Please note, that no uplink
transmission is allowed in CELL_PCH/URA_PCH.)
• URA_PCH
URA stands for UTRAN Registration Area. If the UE is in the CELL_PCH and moving fast, a lot of cell updates have to be
performed. URAs are a combination of one or several cells under one C-RNC. URAs may overlap, i.e. a cell may belong to
several URAs. If UTRAN wants to transmit something to the UE, it must page the UE within the URA. The UE is
responsible for URA updates – when it changes the URA – and periodic URA updates – when required by UTRAN.
States of Bearer Allocation
System Information
Within UTRAN system information is broadcasted with the help of the RRC messages
• System Information,
• Paging Type I, and
• System Information Change Indication.
Most system information parameters are determined by the RNC. The Node B is informed
about the parameters via the NBAP message BCCH Information. Some system
parameters can be made available by the Node B, such as interference values, which
change fast. Given the system information, the UE is capable to decide, whether or how
to access the PLMN via the existing cell.
System information is organised in System Information Blocks (SIBs). System information is

grouped into SIB 1 to SIB 18. Each SIB is responsible to carry a specific content. For
instance, SIB 12 holds measurement control information and parameters. Depending on
the UE‘s RRC state, it reads specific SIBs, and uses the transmitted parameters.
There is a huge amount of SIBs, which have to be read by the UE. This requires a lot of
battery power.
Therefore, a Master Information Block (MIB) was introduced, which gives references and
scheduling information about the SIBs. The MIB is transmitted in every 8th radio frame on
the P-CCPCH (on position SFN mod 8 = 0, and with a TTI of 20 ms).
For most of the SIBs used within the system, the MIB may carry a value tag. The only
exceptions are SIB 15.2, SIB 15.3 and SIB 16. If a value tag is unchanged, the
corresponding system information has not been modified. Thus, there is no need for the
UE to read the SIB. SIB 7 has no value tag. It changes with each occurrence.
Scheduling information is used to inform the UE, where and when a specific system
information is transmitted.
NBAP = Node
UTRAN
System Information ( ) B Application
Part BCCH Information
NBAP:
UE RNC
Node B
position on P-CCPCH: SFN

mod 8 = 0
TTI: 20 ms
MIB value tag M: range 1..8
value tag M
SIB 1 SIB 2 SIB 3 SIB 18

value tag 1 value tag 2 value tag 3 value tag 18
UTRAN can notify UEs, that a value tag in the MIB has been changed. Hereby, the information element BCCH Modification Info is
broadcasted. There are two RRC messages, which can carry this information element:
• Paging Type 1
Some mobile phones have no radio link allocated, mobile phones, which are in the RRC idle mode, and in the RRC connected mode
sub-states CELL_PCH and URA_PCH. This paging message is transmitted in all paging occasions in the cell.
• System Information Change Indication
With this message, we address UEs in the CELL_FACH sub-state. Consequently, this message must be transmitted on every S-CCPCH,
which carries FACHs. The System Information Change Indication message is transmitted on a BCCH, which must be mapped on
FACHs in such a way, that every S-CCPCH carries the BCCH Modification Change IE.
Within the IE BCCH Modification Change, even a BCCH Modification Time can be given, indicating to the UEs, when the value tags will
change.
Please note, that UEs in the CELL_DCH sub-state are addressed directly by the RNC via the Measurement Control message.
In this course documentation, we only describe the System Information Blocks (SIBs), which are used in
Nokia‘s RAN1, and SIB 4 and SIB16. Please note, that all SIBs are valid on cell level except for SIB 1, SIB
15.3, and SIB 16. SIB 1 and SIB 15.3 are valid on PLMN level, while SIB 16 is valid for equivalent PLMNs.
For each SIB, following characteristics were specified:
• Area scope: Where is the value tag valid: within one cell or within a PLMN/ equivalent PLMN?
• UE RRC state: When the SIB is valid?
• UE RRC state: When the SIB is read?
• Scheduling information: At which position is the SIB transmitted and what is its repetition period?
• Modification of system information: Is it indicated by a value tag, or is it timer based?
The UE receives all SIBs via the BCCH. There is only one exception: SIB 10. If a UE is capable to receive
simultaneously one S-CCPCH and one DPCH, than it receives SIB 10 on a FACH.
Master Information Block (MIB):

The MIB informs the UE about the supported PLMN types and the PLMN identity. The UE finds in the MIB also
references to up to maxSIB (=32) SIBs, including their scheduling information and type.
A MIB is valid in one cell. If a UE changes the cell, is must read the new cell‘s MIB. The MIB is read in the RRC
modes/states RRC idle, CELL_FACH, CELL_PCH and URA PCH. Its parameter are valid in the same states. A
change of the MIB information is indicated by a value tag.
In this course documentation, we only describe the System Information Blocks (SIBs), which are used in Nokia‘s
RAN1, and SIB 4 and SIB16. Please note, that all SIBs are valid on cell level except for SIB 1, SIB 15.3, and SIB
16. SIB 1 and SIB 15.3 are valid on PLMN level, while SIB 16 is valid for equivalent PLMNs.
SIB1
System Information Block 1 (SIB 1)
This SIB is used to inform the UE about NAS system information.
The NAS system information characterises the NAS domains. SIB
1 also delivers UE timers and counters, which have to be used by
the UE in the RRC idle and RRC connected mode.
For instance, a UE in the RRC connected mode uses the timer
T305 for periodic cell and URA updates.
SIB 1 is valid in one PLMN. The MIB is read in the RRC

modes/states RRC idle, CELL_FACH, CELL_PCH and URA PCH. Its
parameter are valid in the same states, and the the RRC sub-
state CELL_DCH. If the UE selects a new cell, and the SIB 1 value
tag has the same number as in the preceding cell, the same
content is transmitted in this SIB. There is then no necessity for
the UE to read this SIB after cell re-selection.
T302/N302 The CELL UPDATE/URA UPDATE retransmission timer
(MS timer)
T300/N300 The RRC CONNECTION REQUEST retransmission timer

(MS timer)
T312/N312 The timer for supervising successful establishment of a

physical channel (MS timer)
T309 The timer for supervising successful connection establishment

in case of an inter-RAT cell re-selection (MS timer)
T316 This timer is started when the UE detects an out of service

area in URA_PCH or CELL_PCH state. This timer is stopped when the
UE detects an in service area. When the timer expires the UE
initiates cell update procedure (MS timer).
T317 This timer is started when the T316 expires and the UE
detects an out of service area. This timer is stopped when the UE
detects an in service area. When the timer expires the UE transits to
idle mode (MS timer)
SIB2

This SIB contains an URA identity list.
SIB 2 is read and valid in the RRC sub-state URA_PCH. A change of the SIB 2 information is indicated by a
value tag.
SIB3
This SIB contains relevant parameters for cell selection and re-
selection. It also holds the cell identity and cell restriction data,
such as „cell barred“ IEs. SIB 3 must be read and is valid in the
RRC idle mode. It is read and valid in the RRC connected mode
sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 4 is not
broadcasted. A change of the SIB 3 information is indicated by a
value tag.

SIB4 This SIB holds mostly the same data fields as SIB 3, but it is read and valid only, when the UE is in
the RRC connected mode. I.e, this optional SIB is read and valid in the CELL_FACH, CELL_PACH
and URA_PCH sub-state. A change of the SIB 4 information is indicated by a value tag.
SIB5 The parameters for the configuration of physical channels are broadcasted in this SIB. The
parameters cover the PICH power offset, the AICH power offset, P-CCPCH, S-CCPCH and PRACH
system information lists. SIB 5 must be read and is valid in the RRC idle mode. It is read and valid
in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 6 is not
available. A change of the SIB 5 information is indicated by a value tag.
SIB7

This SIB holds fast changing parameters. Therefore no value tag is used for it. The UE has to read its
parameters periodically. For that, an expiration timer (Expiration Time Factor) is broadcasted with this
message. SIB 7 expires at max(32, 8 * Expiration Time Factor). Expiration Time Factor can have the
values 2times, 4 times, 8 times ... 256 times. Its default value is 1.
The fast changing parameters transmitted with SIB 7 include the UL interference and dynamic
persistence level. It is read and valid in all states except for the CELL_DCH sub-state.
This SIB holds measurement control information. The UE gets here the relevant date for traffic
SIB11 measurement, intra-frequency measurements, etc. SIB 11 must be read and is valid in the RRC idle
mode. It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH,
if SIB 12 is not broadcasted. It is also valid in the RRC sub-state CELL_DCH, as long as the UE did not
get a Measurement Control message from UTRAN and SIB 12 is not broadcasted. A change of the SIB
11 information is indicated by a value tag.
SIB11
SIB11
SIB12 SIB 12 transmits measurement control information for UEs in the RRC connected mode. If not
transmitted, the UEs take the parameters broadcasted with SIB 11. If available, SIB 12 is read
and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH. It is
also valid in the RRC sub-state CELL_DCH, as long as the UE did not get a Measurement
Control message from UTRAN. A change of the SIB 12 information is indicated by a value tag.

SIB16 RB, TrCH, and PhyCH parameters are broadcasted, which are stored by the UE both in the
RRC idle and RRC connected mode. The parameters are used during a handover to UTRAN.
Consequently, these parameters stay valid, when the UE is connected to GSM and GPRS.
This SIB is valid in all RRC states, and read in all RRC states except for the CELL_DCH. The UE
reads and stores the parameters. A change of the SIB 16 information is indicated by a value
tag.
RRC messages information - CS Voice and Video are both Conversational
DL SRB
UE in DUAL MODE UE in 3G LOCKED MODE
CS call, 64Kbps,
Voice AMR Transparent
Video Call
Video CS 64:
DL SF 32
UL SF 16
Voice AMR:
DL SF 128
UL SF 64
(16 Kbps,12.2kbps)
PS can also be OriginatingHighPrioritySignalling
And Registration (Only for Attach)
RRC messages information - PS
Modify max bit rate by Nemo
SIM Card QoS profile
Measurement Control (MC) and Measurement Report (MR)
UTRAN controls the measurements in the UE, either by

broadcasting system information on the BCCH, and/or by
transmitting a Measurement Control message on the DCCH.
If the UE is in the RRC idle mode, it receives relevant measurement information from the
BCCH. The SIB type 3 contains parameters for cell selection and re-selection. In parallel,
the SIB type 11 is used to deliver measurement control information to the UE for the
serving cell. SIB 3 and SIB 11are read and valid in the RRC idle state.
If the UE is in the RRC sub-states CELL_FACH, CELL_PCH and URA_PCH, it is connected to
one cell only and responsible for cell selection and re-selection. It retrieves the
parameters for cell selection from SIB type 4. The measurement control information is
broadcasted with SIB type 12. SIB 4 and SIB 12 are read and valid, when the UE is in the
CELL_FACH, CELL_PCH and URA_PCH sub-state. If SIB 4 resp. SIB 12 is not broadcasted,
then SIB 3 resp. SIB 11 parameters are used instead.
In the sub-state CELL_DCH, the UE is not reading the SIB type 3/4 and 11/12. The
parameters of SIB 12 (SIB 11, if SIB is not available) can be still valid in this state.
The RRC message Measurement Control can be transmitted to the UE, if a DCCH has been
setup between the UE and UTRAN. This message informs the UE about the type of
measurement, which has to be conducted. Each measurement command links a
measurement with a measurement identity, quantity, objects, reporting quantities,
reporting criteria, type, etc.
UE UTRAN
I am in the
System
RRC idle mode
Information
SIB 3 & SIB 11
[BCCH] Node B RNC
I am in the UE UTRAN
ELL_FACH, CELL_PCH or System
URA_PCH sub-state Information
SIB 4 & SIB 12
[BCCH] Node B RNC
(SIB 3 & SIB 11)
I am in the UE UTRAN
CELL_DCH sub-state Measurement Control
[DCCH]
Node B RNC
: parameters for cell selection and re-selection [in the RRC connected mode]
12] : measurement control information [in the RRC connected mode]
d valid: idle, CELL_FACH, CELL_PCH, URA_PCH.
12 is also valid in the CELL_DCH.)
How does a UE perform measurements after a transition in the CELL_DCH state. Two cases
have to be distinguished:
Transition from the RRC idle state to the CELL_DCH sub-state

In the RRC idle state, the UE retrieved the measurement control parameters from the SIB
type 11. Information Elements, which contain intra-frequency, inter-frequency, inter-RAT
and traffic volume measurement system information, may be included in the SIB 11. If
they are included, the UE can send a measurement report, when a measurement
reporting criteria is fulfilled.
As soon as the UE receives a Measurement Control message including one of the above
mentioned measurement types, it replaces its internal stored data based on the SIB11 by
the parameters delivered with the Measurement Control message.
Transition from the CELL_FACH to the CELL_DCH sub-state.

In the CELL_FACH sub-state, the SIB 12 (or SIB 11, if there is no SIB 12) is valid including
all relevant measurement control parameters. If the UE transits to the CELL_DCH sub-
state, the system information stays valid, as long as there was no Measurement Control
message, which replaces the parameters.
But what happens, if the UE was in the CELL_DCH sub-state, it has received Measurement
Control messages, and it then transits to the CELL_FACH sub-state. In the CELL_FACH
sub-state, the UE reads SIB 12 (SIB 11), and its measurement control parameters become
valid. But when the UE then transits back to the CELL_DCH sub-state, the UE resumes
with the measurements and associated reporting, as they were stored before the
transition to the CELL_FACH (or any other RRC connected) sub-state.
The RRC message Measurement Control is used to setup, to modify, and to release a
measurement in the UE. The UE gets all relevant information, how to perform a specific type of
measurements. A measurement is either conducted periodically or driven by an event. Then, the
UE returns a measurement report.
The Measurement Control message is transmitted on a DCCH via an RLC entity in the
acknowledged mode. I.e. the UE is either in the RRC connected sub-state CELL_DCH or
CELL_FACH.
If the setup of a measurement fails, the UE returns the RRC message Measurement Control
Failure. It is transmitted on an UL DCCH via an RLC entity in the acknowledged mode.
The RRC message Measurement Report was specified to deliver measurement results from the
UE to UTRAN (RNC). This message is transmitted on a DCCH. The RLC entity can be in the
acknowledged or unacknowledged mode. The RLC entity mode is set by the RRC message
Measurement Control.
Measurement results can be only transmitted in the CELL_DCH or CELL_FACH sub-state.

CELL_DCH: If a reporting criterion is met, the UE transmits a Measurement Report. A
measurement identity identifies the measurement as specified by UTRAN. It includes
measurement quantities and identifies the measurement event.
CELL_FACH: In this sub-state, traffic volume measurements and positioning measurements are
reported by the UE. Intra-frequency measurements are reported via the RACH, whereby the UE
learns from the BCCH (SIB11 or SIB12) the maximum numbers of cells, it can report.
CELL_PCH or URA_PCH: UE must perform a cell update. Cell update cause is „uplink data
transmission“. Then they are in the CELL_FACH state, where the Measurement Report can be
sent. The measurement report either holds traffic volume measurements or positioning
measurements.
With the RRC message Measurement Control, UTRAN commands the UE to perform
measurements on its behalf. There is a set of different types of measurements, which
can be conducted:
• Intra-Frequency Measurements
• Inter-Frequency Measurements
• Inter-RAT Measurements
• UE-Internal Measurements
• Traffic Volume Measurements
• Quality Measurements
• UE Positioning Methods
As a consequence, a UE may be forced to conduct several different types of
measurements
simultaneously. Each type of measurement is identified by an allocated „Measurement
Identity“.
Some measurements are not conducted continuously. UTRAN tells the UE once, how to
perform a type
of measurements. Whenever necessary, it just informs the UE to conduct the
measurements of a
measurement type by just telling it the associated measurement identity.
Each measurement type comes with a measurement command: setup, modify, and
release.
Finally, UTRAN inform the UE, how to deliver the measurement reports:
Delivery on an acknowledged or unacknowledged RLC, and
Periodical or event triggered reporting.
In the RRC message Measurement Control, the is an PhyCH information elements, where
the UE can
Measurement Control ( )
RNC
UE
UE IEs
Measurement Identity
Measurement IEs setup/modify/release
Measurement Command
PhyCH IEs RLC AM/UM and
Measurement Reporting Mode periodical reporting/event triggered
Additional measurements list

includes non-frequency
related cell info
CHOICE Measurement type
Intra-Frequency Measurements
Inter-Frequency Measurements
Inter-RAT Measurements
DPCH compressed mode
status info UE-Internal Measurements
Traffic Volume Measurements
Quality Measurements
UE Positioning Methods
raffic Volume Measurements
Traffic volume measurements are used to trigger measurement reports based on uplink
traffic volume.
Why is it necessary to perform this type of measurement? The UE is in the RRC connected
sub-state CELL_FACH. The volume of uplink traffic is increasing. UTRAN tells the UE to report
an increased amount of uplink traffic. UTRAN (here: the S-RNC) can decide to allocate
dedicated physical channel resources to the UE. In other words, the UE is moved to the
CELL_DCH sub-state.
The measurement object is the individual cell. The reported quantities are
Buffer Occupancy (BO) which „indicates for each logical channel the amount of data in
number of bytes that is available for transmission and retransmission in the RLC layer“. (TS
25.321) At least every TTI, the MAC layer receives this information from each RLC entity.
Average of Buffer Occupancy
Variance of Buffer Occupancy.
The two last reporting quantities are statistics, which the MAC layer computes and delivers
after being configured accordingly by the RRC. These statistics on BO values are determined
from all RBs/LogCHs mapped onto a given TrCH. The Transport Channel Traffic Volume
(TCTV) is the sum of the BO of all LogCHs, mapped on a given TrCH. The evaluation has to be
done at least once every TTI.
Following reporting events were specified:

4A: Transport Channel Traffic Volume becomes larger than an absolute threshold
4B: Transport Channel Traffic Volume becomes smaller than an absolute threshold
raffic Volume Measurements
RRC messages information
Traffic volumes High threshold information sent after RAB setup complete (CELL
UE Buffer triggers Threshold for RAB Upgrade

First RAB Reconfiguration

DL 32Kbps(SF64)/ UL 32Kbps SF32)
Traffic volumes High threshold information sent after RAB setup complete (CELL
Maximum DL bit rate for PS domain NRT data = 384 Kbps
Maximum UL bit rate for PS domain NRT data = 64 Kbps
nitial and minimum allowed bit rate in downlink = 32 Kbps
nitial and minimum allowed bit rate in uplink = 32 Kbps
Second RAB Reconfiguration

DL 384Kbps(SF8)/ UL 32Kbps (SF32)
Cell DCH  Cell FACH

Cell FACH  Cell PCH

Cell PCH  Cell FACH

Cell FACH  Cell DCH

Quality Reporting Event
How good is the connection? Downlink, this must be determined by the UE, uplink by the
Node B. Downlink, the quality measurements are used to set DL quality thresholds, such as
the DL TB error rate.
In contrast to the UE internal measurements, there is only one specified reporting event:
5A: A predefined number of bad CRCs is exceeded (when a DCH is established)
If the reporting of 5A is ordered by UTRAN, the UE sends a report to indicate to UTRAN, that
the number of bad CRCs during a predefined sliding window has exceeded a predefined
number.
The following three parameters are used:

- Total CRC is the length of the sliding window over which the number of bad CRCs are
counted.
- Bad CRC tells the UE the number of bad CRCs that are required within "Total CRC" for the
event to be triggered.
- Pending after trigger is a time period. A new event can not be triggered until "Pending
after trigger" CRCs have been received.
The Quality Deterioration report is used when the UL outer loop power control is not reaching
it's BLER/BER target. If the DL link quality is not reaching its quality target, the RNC can
increase the SIR set at the Node B to improve the link quality. But this reduces also the
capacity of the serving cells and increases the interference level, imposed on the radio links
of other Ues served in the same geographical area. The Radio link measurements from BTS
are used to check whether the DL DPCH power of the radio link is approaching it maximum
value. If such a situation is given, this may trigger measurements in the compressed mode
(handover measurements).
Quality Reporting Event
Cells for Measurement and Monitoring (new)
The mobile phone is capable to run several measurement types in parallel. Each measurement
is hereby controlled and reported independently. The UE groups the monitored cells:
Active Set Cells
The UE is connected to all these cells, performing a soft handover. User data can be
transmitted in all these cells. For measurements and event reporting, the UE only considers
cells, which are stored in the CELL_INFO_LIST for measurements. If an active cell set is not
stored there, the UE won‘t consider it for event evaluation and measurement reporting.
Monitored Set Cells
The cells, which are stored in the CELL_INFO_LIST are monitored set cells, when they are not
active set cells.
Detected Set Cells
The UE is capable to detect cells, which do not belong to the two above mentioned sets. They
are stored in the detected set list. Measurement reporting of detected set cells can be
conducted only for intra-frequency measurements, when the UE is in the CELL_DCH sub-state
In the RRC message, the IE „Cells for measurements“ can be included. If so, only these cells are
considered for the (intra-, inter-, or inter-RAT) measurement. If the IE „Cells for
measurements“ is not included in the RRC message, than all cells must be considered for
measurements, which are stored in the CELL_INFO_LIST.
tra-frequency Measurements
Intra-frequency measurements are measurements on downlink physical channels at the
same frequency as the active set.“ The measurement object is one cell.
If the RRC message Measurement Control commands the UE to make intra-frequency
measurement, it may contain among others:
Intra-frequency cell info list (optional)
Measurement quantity
There are three different measurement quantities for the FDD mode:
- Downlink Ec/N0
- Downlink received signal code power (RSCP) after despreading.
- Downlink pathloss in dB = Primary CPICH Tx power - CPICH RSCP.
Measurement validity
The measurement validity describes, when the measurement has to be conducted. There are
three options:
- CELL_DCH state,
- all states except the CELL_DCH state, and
- all states.
Reporting Criteria
Reporting criteria outline, what kind of intra-frequency measurements have to be conducted.
A set of intra-frequency measurements were specified, but it is the operator‘s choice, which
ones are used.
ra-frequency Reporting Events
Below, you can see a list of intra-frequency reporting events. UTRAN decides, which of the listed
events have to be reported by the UE. The required intra-frequency reporting events, which
are choosen by UTRAN, depend on the implemented handover reporting function or other
radio network functions. The measurement quantities are determined by measuring the P-
CPICH of the cell.
Reporting events
1A: A Primary CPICH enters the reporting range
The reporting range can be between 0 and 14.5 dB (step size 0.5 dB). The reporting range can
be set in relation with the measurement of the best (strongest) cell – as is was displayed on
the next figure. It can be also set in ration with a weighted average of the best measured cell
and the averaged measurement results of additional, non-forbidden cells. If a CPICH crosses
the reporting range, a reporting event is triggered. A individual cell offset can be taken into
account.
1B: A primary CPICH leaves the reporting rang Similar concept as in 1A.
1C: A non-active primary CPICH becomes better than an active primary CPICH
1D: Change of best cell Inter-
1E: A Primary CPICH becomes better than an absolute threshold rat(RAN 1.5)
1F: A Primary CPICH becomes worse than an absolute threshold (RAN 1.5)
A hysteresis value can be set before reporting the event in all reporting events – in the figures,
this is only shown for 1A and 1B.
Reporting event: 1E: A P-CPICH becomes better than
an absolute threshold
1F: A P-CPICH becomes worse than
e.g. P-CPICH Ec/No
Cell 1 Cell 2
Cell 3
absolute
threshold
time
1F
for
cell
1E 1
for
cell
Neighbourhood Lists
In the RRC idle state and in the RRC connected sub-states CELL_FACH, CELL_PCH and
URA_PCH, the UE is responsible for cell selection and re-selection. It camps on one cell or it is
served by one cell. By reading the System Information Block 11 and/or 12, the UE gets the
Intra-frequency cell info list,
Inter-frequency cell info list, and
Inter-RAT cell info list,
i.e. it gets several neighbourhood lists.
In the CELL_DCH sub-state, the RNC must be able to continuously update the neighbour cell
lists in order to reflect the changing neighbourhood of a moving mobile station. This is part of
the RNC‘s handover control. If we have more than one active set cell, which participate in a
soft handover, the handover control of the RNC is responsible to combine the lists into one
neighbour cell list which is then transmitted to the mobile station. The neighbour cell list
combination is carried out in the steps depicted in next slide.
A soft handover only takes place with cells on the same UTRA carrier band. Consequently, the
combining of neighbourhood lists of several active set cells is only required for intra-
frequency handovers and has to combined with their measurements.
Neighbourhood List Combination for Intra-frequency HOs
Two Cells in the Neighbour

Active Set
List Cell 7:
Cell 3
Cell4
Cell 8
Cell Cell Cell
Cell 1 2 3 Cell 12
4
Cell 11
Cell
Cell 6
Cell Cell Cell
5 6 7 8
Neighbour cells
defined only for
Cell Cell Cell Cell Cell 7
9 10 11 12
Neighbour List Cell

Cell 6: Cell33
Cell 2 Cell11
Cell11
Cell3 Neighbour cells
which are Cell
Cell 7 Cell22 Cell
Cell44
common to Cell
6 and Cell 7 Cell7
Cell7 Cell
Cell88
Cell 11
Neighbour cells Cell Cell
Cell 10 defined only for Cell Cell
10
10 12
12
Cell 5 Cell 6
Cell
Cell55 Cell
Cell66
Neighbourhood List Combination for Intra-frequency HOs
The neighbourhood lists for intra-frequency handover measurements can be composed like this:
Step 1: Active set cells

First the handover control sets the active set cells into the neighbour cell list.
Step 2: Neighbour cells which are common to three active set cells
During the second step of neighbour cell list combination the handover control selects those neighbour cells
which are common to all three active set cells. If the total number of relevant neighbour cells exceeds the
maximum number of 32 after the second step, the handover control removes in random order those surplus
cells from the combined neighbour cell list which are selected during the second step
Step 3: Neighbour cells which are common to two active set cells
During the third step of neighbour cell list combination the handover control selects those neighbour cells
which are common to two active set cells. If the total number of relevant neighbour cells exceeds the
maximum number of 32 after the third step, the handover control removes in random order those surplus
cells from the combined neighbour cell list which are selected during the third step.
Step 4: Neighbour cells which are defined for only one active set cell
During the fourth step of neighbour cell list combination the handover control selects those neighbour cells
which are defined for only one active set cell. If the total number of relevant neighbour cells exceeds the
maximum number of 32 after the fourth step, the handover control removes those surplus neighbours from
the combined neighbour cell list which are selected during the fourth step, starting from the neighbours of the
weakest (CPICH Ec/Io) active set cell.
Cell
Cell
Neighbourhood
Cell 2 List Combination
15
15 for
Cell1Intra-frequency
Cell 1 HOs
Cell 2
Cell Cell
Cell
Cell55 Cell Cell22
21
21
Cell Cell
Cell33
Cell77 Cell
Cell22 Cell
Cell
Cell99 Cell77 Step
Step22
Cell
Cell77
Cell Cell
Cell
Cell Cell 11
11
11 Cell 11
37
37 Common to 3
Cell Cell
Cell
Cell Cell 50 Neighbour Lists
15
15 Cell 50
51
51
Cell Cell
Cell99
Cell Cell
48
48 Cell Cell
49 Cell
49 13
Cell
Cell44 13 Cell2
Cell
Cell99 Common to Cell2
Cell Cell
Cell 2 Cell
Cell
41 Cell
Cell 10
10 Neighbour Cell77
41 10 Cell 9
10 Cell Lists Cell
Cell
Cell
Cell66 Cell Cell9
Cell
Cell 22 11
11
.... 22
56
56 …… Cell
Cell
... … Step 15
... … ...
... Step33 15
Cell
Cell
Cell
Cell ... Cell
37 Max
... Cell Cell
37
43
43 Cell 10 32
Cell
Cell 33 10
Cell Cells
33 Cell
Step 25
Step11 Neighbour
25 Cells 41
41
Lists
Cell
Cell
Neighbour Cells 49
49
defined for only 1 …..
Three Cells in the Neighbour List: …..
Active Set
Step
Step44 …
random selection …
Cell
Cell
CS and PS Call
Flow Cell Search
When a UE is switched on, it starts to monitor the radio interface to find a suitable cell to
camp on. But it has to determine, whether there is a WCDMA cell nearby. If a WCDMA
cell is available, the UE has to be synchronised to the downlink transmission of the
system information – transmitted on the physical channel P-CCPCH – before it can
make a decision, in how far the available cell is suitable to camp on. Initial cell
selection is not the only reason, why a UE wants to perform cell synchronisation. This
process is also required for cell re-selection and the handover procedure.
Cell synchronisation is achieved with the Synchronisation Channel (SCH). This channel
divides up into two sub-channels: P-SCH and S-SCH
With the help of the SCH, the UE was capable to perform chip, TS, and frame
synchronisation. Even the cell‘s scrambling code group is known to the UE.
The UE knows the cell‘s primary scrambling code. It now wants to gain the cell system
information, which is transmitted on the physical channel P-CCPCH. The
channelisation code of the P-CCPCH is also known to the UE, because it must be Cch,256,1
in every cell for every operator. By reading the cell system information on the P-
CCPCH, the UE learns everything about the configuration of the remaining common
physical channels in the cell, such as the physical channels for paging and random
access.
RAB 1st
then
RRC
MOS CS Message Flow
UE NodeB RNC MGW/CN
RRC: RRC Connection Request (RACH)
NBAP: Radio Link Setup Request
T300=2s ; N300=3
NBAP: Radio Link Setup Response RNC checks if resources are
available: BTS, AC,
ALCAP: ERQ (Establish Request)
Transmission.
ALCAP: ECF (Establish Confirm) If not it sends RRC
Connection Reject
FP: Downlink Synch
FP: Uplink Synch
L1 Synchronization
RRC: RRC Connection Setup (FACH) [RRCconnRepTimer1/2(100ms,1s)]
L1 Synchronization
NBAP: Synchronization Indication
RRC: RRC Connection Setup Complete (DCH)
RRC Connection Establishment – CELL DCH State

T312=6s ; N312=4
RRC: Initial Direct Transfer (MM: CM Service Request)
SCCP: CR (Connection Request)
RRC RANAP: Initial UE Message (MM: CM Service Request)
Connection till SCCP: CC (Connection Confirm)

the RNC RANAP: Direct Transfer (MM: Authentication Request)
RRC: Downlink Direct Transfer (MM: Authentication Request)
RRC: Uplink Direct Transfer (MM: Authentication Response)
RANAP: Direct Transfer (MM: Authentication Response)
RANAP: Common ID
RANAP: Security Mode Command
RRC: Security Mode Command

UE NodeB RNC MGW/CN
RRC: Security Mode Complete
RANAP: Security Mode Complete
RANAP: Direct Transfer (CC: Setup)

RRC: Uplink Direct Transfer (CC: Setup)
RRC: Downlink Direct Transfer (CC: Call Confirmed)

RANAP: Direct Transfer (CC: Call Confirmed)
RAB Establishment RANAP: RAB Assignment Request
NBAP: Radio Link Reconfiguration Prepare

RL modification procedure:
NBAP: Radio Link Reconfiguration Ready SRB+DCH, HW resources checked
Possible failure in AAL2
ALCAP: ECF (Establish Confirm)
setup (Iub, Iur and Iu)
FP: Downlink Synch
FP: Uplink Synch
NBAP: Radio Link Reconfiguration Commit)
RRC: Radio Bearer Setup
Soft handover is not allowed during the RAB establishment procedure (The mobile can not add or
remove cells in AS) this makes the UE and Node B particularly sensitive to mobility and
dominance Timer wf_rb_setup_cpl (6s) is started when the RRC: Radio Bearer Setup message is
sent to the UE In case the timer expires Iu Release Request is sent to the CN with release cause
(radio_conn_lost)
RRC: Radio Bearer Setup Complete
RANAP: RAB Assignment Response
UE NodeB RNC MGW/CN
RANAP: Direct Transfer (CC: Alerting)
RRC: Downlink Direct Transfer (CC: Alerting)
RANAP: Direct Transfer (CC: Connect)
RRC: Downlink Direct Transfer (CC: Connect)
RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (CC: Connect Acknowledge)
Call Established
RANAP: Location Report
RRC: Measurement Control
Call Disconnect
RRC: Uplink Direct Transfer (CC: Disconnect)
RANAP: Direct Transfer (CC: Disconnect)
RANAP: Direct Transfer (CC: Release)
RRC: Downlink Direct Transfer (CC: Release)
RANAP: Direct Transfer (CC: Release Complete)
RANAP: Iu Release Command
RANAP: Iu Release Complete

RRC: Downlink Direct Transfer (CC: RRC Connection Release)
RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
NBAP: Radio Link Deletion Request
NBAP: Radio Link Deletion Response
MTC CS Message Flow
UE NodeB RNC MGW/CN
RANAP: Paging
RRC: Paging Type 1
NBAP: Radio Link Setup Request
NBAP: Radio Link Setup Response

FP: Downlink Synch
FP: Uplink Synch
L1 Synchronization
RRC: RRC Connection Setup (FACH)
L1 Synchronization

RRC: Initial Direct Transfer (MM: Paging Response)
SCCP: CR (Connection Request)
RANAP: Initial UE Message (MM: Paging Response)
SCCP: CC (Connection Confirm)
RANAP: Direct Transfer (MM: Authentication Request)
RRC: Downlink Direct Transfer (MM: Authentication Request)
RRC: Uplink Direct Transfer (MM: Authentication Response)
RANAP: Direct Transfer (MM: Authentication Response)
RANAP: Common ID
RANAP: Security Mode Command

RRC: Security Mode Command
UE NodeB RNC MGW/CN
RANAP: Security Mode Complete
RANAP: Direct Transfer (CC: Setup)

RRC: Uplink Direct Transfer (CC: Setup)
RRC: Downlink Direct Transfer (CC: Call Confirmed)

RANAP: Direct Transfer (CC: Call Confirmed)
RAB Establishment RANAP: RAB Assignment Request

RL modification procedure:
NBAP: Radio Link Reconfiguration Ready SRB+DCH, HW resources checked
Possible failure in AAL2
setup (Iub, Iur and Iu)
FP: Downlink Synch
FP: Uplink Synch
NBAP: Radio Link Reconfiguration Commit)
RRC: Radio Bearer Setup
Soft handover is not allowed during the RAB establishment procedure (The mobile can not add or
remove cells in AS) this makes the UE and Node B particularly sensitive to mobility and
dominance Timer wf_rb_setup_cpl (6s) is started when the RRC: Radio Bearer Setup message is
sent to the UE In case the timer expires Iu Release Request is sent to the CN with release cause
(radio_conn_lost)
RANAP: RAB Assignment Response
UE NodeB RNC MGW/CN
RRC: Downlink Direct Transfer (CC: Alerting)

RANAP: Direct Transfer (CC: Alerting)
RANAP: Direct Transfer (CC: Connect)
RRC: Downlink Direct Transfer (CC: Connect)
RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (CC: Connect Acknowledge)
Call Established
RANAP: Location Report
MOS PS Message Flow
UE NodeB RNC SGSN
NBAP: Radio Link Setup Request RNC checks if resources are
available: BTS, AC,
NBAP: Radio Link Setup Response
Transmission.
AAL2SIG: ERQ If not it sends RRC
AAL2SIG: ECF Connection Reject
FP: Downlink Synch
FP: Uplink Synch
L1 Synchronization
RRC: RRC Connection Setup (FACH) [RRCconnRepTimer1/2(100ms,1s)]
L1 Synchronization

RRC: Initial Direct Transfer (MM: Attach Request)
RANAP: Initial UE Message MM: (Attach Request)
RANAP: Direct Transfer (MM: GPRS Identity
RRC: Downlink Direct Transfer (MM: GPRS Identity Request) Request)
RRC: Uplink Direct Transfer (MM: GPRS Identity Response)
RANAP: Direct Transfer (MM: GPRS Identity
Response)
RANAP: Direct Transfer (MM: Authentication &
Ciphering Request)
RRC: Downlink Direct Transfer (MM: Authentication & Ciphering Request)
RRC: Uplink Direct Transfer (MM: Authentication & Ciphering Response)

RANAP: Direct Transfer (MM: Authentication &
Ciphering Response)
RANAP: Security Mode
RRC: Security Mode Command Command

RANAP: Security Mode
Complete
RANAP: Common
ID
MOS PS Message Flow
UE NodeB RNC SGSN
RANAP: Direct Transfer (MM: Attach
RRC: Downlink Direct Transfer (MM: Attach Accept) Accept)
RRC: Uplink Direct Transfer (MM: Attach Complete)
RANAP: Direct Transfer (MM: Attach

Complete)
RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
RANAP: Direct Transfer
(SM: Activate PDP Context Request)
RAB Establishment RANAP: RAB Assignment

RRC: Radio Bearer Setup Request
SRB + DCH 0/0
RANAP: RAB Assignment
Response
RRC: Measurement Control RANAP: Direct Transfer
(SM: Activate PDP Context
RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept) Accept)
RRC: Measurement Repor (Trafic Volume Reports 4a)
NBAP: Radio Link Reconfiguration Ready RL modification procedure:

AAL2SIG:
SRB+DCH, HW resources checked
ERQ
AAL2SIG:
ECF
NBAP: Radio Link Reconfiguration Commit
RRC: Radio Bearer Reconfiguration
RRC: Radio Bearer Reconfiguration Complete
Uplink & Downlink Data Transfer

MOS PS Message Flow
UE NodeB RNC SGSN
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RANAP: Direct Transfer (SM: Deactivate
PDP Context Request)
RANAP: Direct Transfer
(SM: Deactivate PDP Context
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept) Accept)
NBAP: Radio Link Reconfiguration Ready
AAL2SIG:
ERQ
AAL2SIG:
ECF
NBAP: Radio Link Reconfiguration Commit
RRC: Uplink Direct Transfer (MM: Detach Request) RANAP: Direct Transfer (MM: Detach Request)
RRC: Radio Bearer Release

RANAP: Direct Transfer (MM: Detach
RRC: Downlink Direct Transfer (MM: Detach Accept) Accept)
RANAP: Iu Release Command
RANAP: Iu Release
Complete
RRC: Radio Bearer Release Complete
RRC: RRC Connection Release

RRC: RRC Connection Release Complete
NBAP: Radio Link Deletion Request
NBAP: Radio Link Deletion Response

AAL2SIG: REL (Release
Request)
AAL2SIG: RCL (Release
Confirm)
0 bit rate
Based on
102 © 2006 Nokia
e4a
Bearer Real
RRC setup traffic
setup transfe
r
9:52:53 : C09 AMR
Soft
Handover
Handover Types
• Intra-Frequency Handovers
– Softer Handover
• Handover between sectors of the same Node B (handled by BTS)
• No extra transmissions across Iub interface
• Maximum Ratio Combining (MRC) is occurring in both the UL and DL
– Soft Handover
• MS simultaneously connected to multiple cells (from different Node Bs)
• Extra transmission across Iub, more channel cards are needed (compared to
non-SHO)
• Mobile Evaluated Handover (MEHO)
• DL/UE: MRC & UL/RNC: Frame selection combining
– Hard Handover
• Arises when inter-RNC SHO is not possible (Iur not supported or Iur congestion)
• Decision procedure is the same as SHO (MEHO and RNC controlled)
• Causes temporary disconnection of the (RT) user
• Inter-Frequency Handover
– Can be intra-BS, intra-RNC, inter-RNC
– Network Evaluated Handover (NEHO)
– Decision algorithm located in RNC
• Inter-RAT Handover
– Handovers between GSM and WCDMA (NEHO)
121 © 2006 Nokia

Soft Handover
WCDMA F1 WCDMA WCDMA

F1 F1
• Main method is soft/softer Handover

• MS connected to two or more cells
• Up to 3 branches can be used (MaxActiveSetSize parameter)
• Seamless Handover without any disconnection of UE-RAN
connection
• softer Handover probability about 5-15 % : soft Handover
probability about 20-50 %
• Same power levels in use for all soft Handover branches

• Optimum power levels for link quality and cell capacity
• Macro Diversity Combining (MDC) gain to reduce power levels
• Mobile Evaluated Handover (MEHO)

• Enables different cell sizes due to Common Pilot Channel Ec/No
measurement
• Optimum fast close loop power control in use
122 © 2006 Nokia
• Outer loop PC after MDC controls the BLER according to set target
SHO: Neighbour Cell Definition
• Each intra-frequency neighbour (ADJS) is identified using ADJSid (ADJS)

• The ADJS parameters provide information on the identity of each neighbour cell
together with its properties (i.e. Handover parameter set identifier, scrambling
code etc..)
• Each neighbour cell is defined using the UTRAN cell identifier which comprises
UTRAN Cell Identifier = MCC + MNC + RNC identifier + Cell

identifier
• Each neighbor cell is defined using the UTRAN cell identifier which comprises;
MCC (Mobile Country Code) = AdjsMCC

MNC (Mobile Network Code) = AdjsMNC
ADJS Parameters
RNC Identifier = AdjsRNCid
Cell Identifier = AdjsCI
• The LAC (AdjsLAC) & RAC (AdjsRAC) are also in ADJS parameter set
Neighbour Cell Definition
• Separate Handover Parameter Set (HOPS) identifiers for

real time(RT) & non-real time(NRT) traffic
– RtHopsIdentifier - real time
– NrtHopsIdentifier - non-real time
– HSDPAHopsIdentifier - HSDPA
• Each HOPS object is identified by a unique HOPSid
(HOPS) in the RNC - on to which the xxHopsIdentifier
parameters are mapped to identify the appropriate HOPS
parameter set for that particular neighbor cell
• Primary scrambling code for neighbor cell specified using

AdjsScrCode
• AdjsTxDiv specifies whether the neighbor cell is using Tx
diversity
• AdjsTxPwrRACH determines the maximum power the UE
can use on the PRACH when accessing the neighbor cell
124 © 2006 Nokia

Maximum number of neighbours
• The maximum number of neighbours that can be defined in

RNC database is
– ADJS: 31
• 31 neighbours + serving cell = 32 cells to measure
– ADJI: 32/carrier, total 48
– ADJG: 32
• Total: max. 111 in RNC database
• Limitation due to specifications of SIB11/12 size
125 © 2006 Nokia

Maximum number of neighbours – SIB11 length limitation
• 3GPP has inconsistent requirements concerning the maximum number of

neighbouring cells that can be broadcasted in the SIB 11 and 12
– SIB 11 and 12 can contain information on the maximum of 96 cells (32 intra-
frequency cells, 32 inter-frequency cells and 32 GSM cells)
– On the other hand, the physical size of SIB data (no more than 3552 bits) has
capacity only for about (depending on the type etc.) 47 cells!!
• If too many adjacencies are declared, the cell will go blocked by system
with alarm: 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) in
RAN04
• As a rule of thumb, assuming that …
ADJS=15, ADJG=15, ADJI=15

and “realistic worst case values”, SIB11 length = 3187.5 < 3552
…
-> OK!!
• Some sites might need additional neighbors and might pose a problem
with the SIB11 limitation
• Avoid setting AdjsQoffset2 values, different CPICH values or other parameters
used to tune cell reselection or handover
Further information Technical Note No. 046 / Restriction on number of

cells in SIB11/12 due to inconsistency problem in 3GPP TS 25.331
126 © 2006 Nokia
Soft Handover
• HC supports the following measurement reporting events and
features:
– Event 1A: A primary CPICH enters the reporting range (Ncell addition)
– Event 1B: A primary CPICH leaves the reporting range (Ncell deletion)
– Event 1C: A non-active CPICH becomes better than an active primary
CPICH (Ncell replacement)
– Cell individual offsets for modifying measurement reporting behaviour
– Mechanism for forbidding a neighbor ing cell to affect the reporting
range
• Handover decision performed by RNC based on measurements and

available resources
• Admission Control can reject the branch addition in case the
maximum load is achieved in DL (threshold + offset), valid both for
RT and NRT bitrates.
• Hard blocking may prevent branch addition
127 © 2006 Nokia

SHO: Measurement Averaging
• The Handover measurement is based on CPICH Ec/Io
• The accuracy of pilot Ec/Io measurements is important for Handover
performance
• Measurement accuracy depends on the filtering length and mobile speed.
– When a MS moves slowly or is stationary, filtering length (in ms) has to be just
long enough to avoid fast fades leading to errors and causing unnecessary
Handovers within a short period.
– Long filtering length will cause Handover delays to fast moving MS
• UE can perform averaging on EC/IO measurement prior to the event
reporting process
• EcNoFilterCoefficient (FMCS) defines the filtering period for intra-
frequency CPICH EC/IO measurements used by UE (default = 200ms)
– Similar filter than in Higher Layer Filtering of common and dedicated BTS
measurements
• RNC averages CPICH Ec/Io measurements using
EcNoAveragingWindow (HOPS)
– defines the number of event triggered or periodic intra-frequency
measurement reports used by RNC to calculate averaged CPICH EC/IO (default
= 8 Measurements)
– Used for intra-frequency hard handovers
128 © 2006 Nokia

1A: A Primary CPICH Enters the Reporting Range
1 • Reporting range defined by offset (point 1 on next slide) from either

(i) best CPICH Ec/Io in the AS, or
(ii) sum of the AS measurement results
set using ActiveSetWeightingCoefficient (FMCS) (0 = use best CPICH : <>0 =
use sum)
• Offset defined using AdditionWindow (FMCS)
2 • Event 1A triggered when CPCIH3 Ec/Io enters UE reporting range (point 2)
3 • If CPICH3 Ec/Io remains within reporting range for a time period defined by
AdditionTime (FMCS) , and the AS is not full, UE sends measurement report to
RNC which adds Ncell3 to AS if possible (point 3)
• AdditionTime defines the 'time-to-trigger' interval between the Ncell first entering
the reporting range and the UE sending the measurement report to the RNC
• If RNC is unable to add Ncell to AS, UE will wait for a period of time, defined by
4 AdditionReportingInterval (FMCS) (point 4) after the first measurement report,
before sending further reports periodically, with interval
AdditionReportingInterval, until (a) Ncell moves out of reporting range, or (b)
RNC adds Ncell to AS.
129 © 2006 Nokia

1A: A Primary CPICH Enters the Reporting Range
Ec/Io ActiveSetWeightingCoefficient
Strongest CPICH in AS P CPICH 1
P CPICH 2 AdditionWin
dow
1
P CPICH 3
time
3 AdditionTime
Measurement no AdditionReportingInterval
4
Report
Add to
the AS?
130 © 2006 Nokia RNC

1A: A Primary CPICH Enters the Reporting
Range
• Reporting criteria of event 1A in 25.331/RRC Measurement Control :
• Reporting Cell Status: All active cells + 2 monitored cells.
• Triggering Condition: Monitored Set cells
• Reporting Range Constant AdditionWindow / 4 dB
• Cells forbidden to affect Reporting range: AdjsDERR / Enable
• W: ActiveSetWeightingCoefficient / 0
• Time to trigger: AdditionTime / 0 = 0 ms
• Reporting deactivation threshold: MaxActiveSetSize = 3
• Amount of reporting: infinity
• Reporting interval: AdditionReportingInterval / O.5 s
131 © 2006 Nokia

1B: A Primary CPICH Leaves the Reporting Range
1 • Event 1B triggered when CPICH3 EC/I0 drops out of the UE reporting range
for a defined period of time (point 1 on next slide)
2 • Reporting range = Strongest CPICH in AS - DropWindow (FMCS) (point 2)
• Time-to-trigger period set using DropTime (FMCS) (point 3)

3
• UE sends RNC measurement report on expiry of DropTime to remove Ncell

(CPICH3) from AS.
• RNC drops the cell from the AS and UE drops the cell from the AS to the
Neighbour Set
132 © 2006 Nokia

1B: A Primary CPICH leaves the Reporting Range
Ec/Io Strongest CPICH in AS

P CPICH 1
DropWindow
P CPICH 2 2
P CPICH 3
time
DropTime Remove the
reported cell
Measurement from the AS
Report
133 © 2006 Nokia
1B: A Primary CPICH Leaves the Reporting
Range
• Reporting criteria of event 1B in 25.331/RRC Measurement Control :
• Reporting cell Status: 3 active cells
• Triggering Condition: Active cells
• Reporting Range Constant: DropWindow / 4 dB
• Cells forbidden to affect Reporting range AdjsDERR / Enable
• W : ActiveSetWeightingCoefficient / 0
• Time to trigger: DropTime / 320 ms
134 © 2006 Nokia

Soft and Softer Handover (case1)
Extract from SIB 11
• SIB 11 contains the relevant reportCriteria
intraFreqReportingCriteria : {
parameters to read when in idle eventCriteriaList {
mode {
event e1a : {
• These are valid in connected triggeringCondition
mode prior to receiving the monitoredSetCellsOnly,
reportingRange 4,
measurement control that w 0,
reportDeactivationThreshold t2,
overwrites them reportingAmount ra-Infinity,
• In this example: reportingInterval ri0-5
},
• Addition window= 2 dB (factor of 2 hysteresis 0,
mapping between the signalled timeToTrigger ttt100,
reportingCellStatus
value and the actual value, TS allActiveplusMonitoredSet :
25.331 defines this mapping) viactCellsPlus2
}
• Addition time = 100 ms event e1b : {
• Reporting interval = 500 ms triggeringCondition
activeSetCellsOnly,
• Drop window = 3 dB (factor of 2 reportingRange 6,
w0
mapping between the signalled },
value and the actual value) hysteresis 0,
timeToTrigger ttt640,
• Drop time = 640 ms reportingCellStatus
135 © 2006 Nokia withinActiveSet : e3
},
1C: A non-active CPICH becomes better than an
active primary CPICH
• UE AS full (MaxActiveSetSize = 3)
1
• Event 1C triggered when CPICH4 EC/IO > CPICH3 in AS by a defined margin,
ReplacementWindow (FMCS). (point 1 in next slide)
• Sending of measurement report to RNC can be delayed by using 'time-to-
trigger' period set by ReplacementTime (FMCS)
2 • If 'time-to-trigger' is used difference between CPICH4 and CPICH3 must be
≥ ReplacementWindow for the period of ReplacementTime (point 2)
3 • If the RNC is not able to replace the Ncells, the UE continues to send
measurement reports periodically, with interval
ReplacementReportingInterval, to the RNC until (a) CPICH4 falls out
of ReplacementWindow or (b) RNC replaces CPICH4 by CPICH3 (point 3)
136 © 2006 Nokia

1C: A non-active CPICH becomes better than an active
primary CPICH
Ec/Io AS has 3 cells
P CPICH 1
P CPICH 2
P CPICH 4
1
ReplacementWindow
P CPICH 3
weakest CPICH3 in AS
time
2 3
ReplacementTime
ReplacementReportingInterva
no
Measurement AS
Report update?
137 © 2006 Nokia

RNC
Soft and Softer Handover (case 2)
Extract from SIB 11 cont.

• In this example: event e1c : {
– Replacement window = 1 dB replacementActivationThresh

– Replacement time = 100 ms old t3,
reportingAmount ra-Infinity,
– Reporting interval = 500 ms reportingInterval ri0-5
– },
Replacement window requires mapping to its true
value according to: hysteresis 4,
timeToTrigger ttt100,
4/(2*2) = 1 dB reportingCellStatus
withinActiveSet : e3
}
• There are two mappings – first is the signalled value to actual value
mapping and second is the way in which hysteresis is applied in the event
triggering equation (TS25.331)
• Once in connected mode the networks sends the same set of information
elements via a measurement control message
• Nokia’s implementation is that the values in the measurement control
message are the same as those within SIB 11
• Events 6F and 6G are configured in a similar fashion i.e. within SIB 11 and
subsequently with a measurement control message
138 © 2006 Nokia

Individual Ncell Offset &
Forbidding Neighbour Cell from Reporting Range
Individual Ncell Offset

• cell individual offsets for modifying measurement reporting behaviour
• effectively 'moves' cell border (shrinks or enlarges cell)
• offset set using AdjsEcNoOffset (= CPICH Ec/No Offset) (ADJS)
• offset applied to Primary CPICH measurements before event evaluation by
the UE
Forbidding Neighbour Cells from Reporting Range

• the primary CPICH of certain cells can be forbidden from reporting range
calculation in some instances
• cells can be forbidden from reporting range using AdjsDERR (ADJS)
139 © 2006 Nokia

Individual Ncell Offset
Ec/Io
Reporti
P CPICH 1 ng
Range
P CPICH 2
AdjsEcNoOffset
Enlarging Cell 3
by x dB
P CPICH 3
time
Reportin Reportin
g Event g Event
1B 1A
140 © 2006 Nokia
Forbidding Neighbour Cell from Reporting Range
Ec/Io
P CPICH 1
PCPICH3 is
Repor forbidden to affect
ting the reporting range
Range as its quality is
quite unstable.
P CPICH 2 AdjsDERR
P CPICH 3
Time
141 © 2006 Nokia

Soft Handover signalling
Branch addition Branch deletion
RRC: Measurement Report (e1b)
RRC: Measurement Report (e1a)
RRC: Active Set Update
RRC: Active Set Update
RRC: Active Set Update Complete
RRC: Active Set Update Complete
g
ovin
UE m
142 © 2006 Nokia

SHO Summary
Reporting cell TriggeringReporting Range/ Reporting

Event Time to Trigger
status Condition Hysteresis Interval
Addition
Active set cells +
Event 1A Monitored set Addition Addition Time Reporting
2 monitored set
(Add) cells Window/4 dB /100 ms Interval
cells
/0.5 s
Drop Window/
Event 1B Drop time
Active set cells
Active set cells 6 dB -
(Drop) /640 ms
Replacement
Active set cells +
Event 1C Replacement Replacement Reporting
2 monitored set -
(Replace) Window/2 dB time/100 ms Interval/
cells
0.5s
• 3GPP reporting events 1A, 1B and 1C (also 6F and 6G)

• CPICH Ec/Io is used as a measurement quantity rather than CPICH RSCP
– CPICH Ec/Io measurements are more accurate
• 1A and 1B reporting range is defined by strongest active set cell
• 1C reporting range is defined by weakest active set cell
143 © 2006 Nokia

RRC Connection Release
• If difference between the best AS cell and the NS cell is too high and SHO is not
performed, the RRC connection is released to avoid excessive interference
• Why might an AS update not be possible?
– Excessive load in the neighbor ing cell
– Hard blocking in the target BTS
– Unavailability of DL spreading codes
– Iub transport resources unavailable
• This function is activated by EnableRRCRelease (HOPS parameter)/0=no

(def),1 =yes
• The RRC connection is released if either:
AveEcNoDownlink + ReleaseMarginForAveEcNo(n) < AvEcNoNcell(n)
EcNoDownlink + ReleaseMarginPeakEcNo(n) < EcNoNcell(n)
– ReleaseMarginForAveEcNo (HOPS) = average Eb/N0 margin [-6 … 6] dB, default 2.5dB

– ReleaseMarginPeakEcNo (HOPS) = peak Eb/N0 margin [-6 … 6] dB, default 3.5dB
• Emergency calls are exempt from RRC Connection Release process
144 © 2006 Nokia

Inter-RNC Mobility
• Most of the times the UE hands over among WBTS belonging to the same
RNC (Intra-RNC Handovers)
• However, what happens when the target WBTS is under a different WBTS??
• 3GPP gives two different options to handle inter-RNC mobility in WCDMA
– Anchoring: the UE will be connected to the CN via the “old” RNC. It is required Iur
connection between the RNCs involved
– SRNS relocation: the UE will be connected to the CN via the “new” RNC. It is the
Nokia implemented method
SRNS relocation *) Anchoring

CN CN CN CN
Iu Iu Iu Iu Iu Iu Iu Iu
RNC RNC RNC RNC RNC RNC RNC RNC
Iur Iur Iur Iur
*) SRNS relocation needs core

network
support; UE support mandatory
in 3GPP
145 © 2006 Nokia

UE not involved SRNC Relocation for RT
NrncRelocationSupp RelocationSuppo
ortSource
=1 RNC rtCN=1 Target RNC UE SRNC Relocation is initiated in the
SRNC Relocation Decision Serving RNC when all the cells of the
active set belong to a different RNC.
RANAP:Relocation Required
The SRNC sends a Relocation Required
Start RANAP:Relocation Request • The CN evaluates if the relocation is
RelocPrep possible and in that case, it sends a
Relocation Request to the target RNC
Start with parameters for the bearer
RelocOverall
RANAP:Relocation Request Ack establishment
• Relocation Command sent from CN to
Stop User plane set-up Source RNC with UTRAN information
RelocPrep
RANAP:Relocation Command
and bearer parameters
Start
• After that, the Source RNC sends
RelocOverall Relocation Commit message over Iur to
RNSAP:Relocation Commit the Target RNC
SRNC operation • When target RNC starts to act as
started
Serving RNC, it sends a Relocation
RANAP:Relocation Detect Detect message to CN. This message
has no parameters
UP switching RRC:UTRAN Mobility Information • At the same time UTRAN Mobility
Information is sent to the UE, to inform
RRC:UTRAN Mobility Information Confirm
that the relocation is performed
Stop RANAP:Relocation complete • After the confirm, the target RNC
RelocOverall
RANAP:Iu Release informs CN with Relocation Complete –
Stop
message that the relocation procedure
RANAP:Iu Release Complete RelocOverall was successful and Iu is released from
source RNC
User plane release
146 © 2006 Nokia

UE involved: Combined SRNC Relocation and inter-RNC HHO for RT
NrncRelocationSupp RelocationSuppo
ortSource
=1 RNC rtCN=1 Target RNC UE
SRNC Relocation Decision
RANAP:Relocation Required
• Because there is no Iur interface, combined SRNS
relocation and HHO are done before the UE is
RANAP:Relocation Request
Start completely under the target RNC
RelocPrep
• The procedure is quite similar to the not UE
Start involved case until Relocation Command
RelocOverall
RANAP:Relocation Request Ack • The only difference in the Relocation Required
message, the Relocation Type IE is set to "UE
User plane set-up
Stop involved in relocation of SRNS"
RelocPrep
RANAP:Relocation Command
Start Physical Channel Reconfiguration • Instead of Relocation Commit via Iur, the serving
RelocOverall RNC sends a Physical CH Reconfiguration, after
L1 sync. Established which the UE stops transmitting and receiving on
between BTS and
UE the old radio links and starts on the new radio link
RANAP:Relocation Detect
UP switching
Physical Ch Reconfig Complete
RANAP:Relocation complete
Stop
RelocOverall
RANAP:Iu Release
Stop
RANAP:Iu Release Complete RelocOverall
User plane release
147 © 2006 Nokia

Inter-system Handover
(ISHO)
ISHO General
Inter System Handover 3G -> 2G
RAN Internal measurements Configured UE measurements
UL Quality
Downlink DPCH power UE Tx power CPICH RSCP CPICH Ec/I0
deterioration
Initiate Compressed Mode

Configure GSM measurements
UE Reports
GSM RSSI measurements
GSM Cell
Meets HO condition ?
CS
Initiate Compressed Mode
Configure GSM measurements
PS
UE Reports
GSM BSIC measurements
Initiate Handover
ISHO parameters
CPICH RSCP (Event CPICH Ec/Io (Event 1F)
1F) DL DPCH power •Thresholds:
•Thresholds: •Threshold: HHoEcNoThreshold
HHoRscpThreshold GsmDLTxPwrThrXX HHoEcNoCancel
HHoRscpCancel •Data rate threshold •L3 filter:
L3 filter: Done already for SHO
HHoRscpFilterCoefficie HHOMAxAllowedBitrate •Timers:
nt DL HHoEcNoTimeHysteresis
•Timers: HHoEcNoCancelTime
HHoRscpTimeHysteresi
s
UE Tx Power (Event
HHoRscpCancelTime UL Quality
6A) •Timer:
•Threshold:
GSM measurement reporting ULQualDetRepThreshol
GsmUETxPwrThrXX GsmMeasRepInterval d
•L3 filter: •Data rate threshold
GsmNcellSearchPeriod
GsmUETxPwrFilterCoeff
•Hysteresis margin: GsmMinMeasInterval HHOMAxAllowedBitrate
GsmUETxPwrTimeHyst GsmMaxMeasPeriod UL
•Data rate threshold
HHOMAxAllowedBitrate Handover Triggering

UL
(XX=AMR,CS,NrtPS,RtPS)
Decision Algorithm
AdjgTxPwrMaxTCH
AdjgRxLevMinHO (n)
GsmMeasAveWindow
2 more optional triggers in RAN04:

Handover Execution
IMSI based ISHO 2G-to-3G back prevention
Emergency ISHO (EMISHO)
GsmMinHoInterval
150 © 2006 Nokia

Measurement Control Parameters: FMCG
• Maximum allowed duration of the inter-system measurement is
calculated:
– GSMMeasRepInterval * GSMMaxMeasPeriod (=0.5*20s) =10s,
• This seems to be too long time, because based on field measurements
BSIC and RSSI delays are about 3 seconds, so it makes senses to reduce
the value of this parameter to some value about 3 seconds, otherwise, if
the BSIC or RSSI measurements fail or if the IS-HO execution is not
possible to due low GSM RSSI levels, the network will not deactivate
compressed mode until the timer of 10 seconds has expired. Thus,
decreasing the parameter value will allow the UE/network to initiate a new
IS-HO attempt. Proposed value for GSMMaxMeasPeriod is 6
• GSMNcellSearchPeriod: 0
– This is neighbor cell search period parameter, ISHO is not allowed until the are
enough measurement reports given by this parameter
– O means that only 1 measurement result is enough for decision making
– Duration of the cell search period is calculated:
– GSMRepInterval * GSMNcellSearchPeriod).
151 © 2006 Nokia

ISHO Process Overview
HO About 25 HO parameters
HOTriggering
TriggeringThresholds
Thresholdsset
setininRNC
RNC
Event
EventTriggered
TriggeredCoverage/Capacity
Coverage/Capacity 5 Coverage/Capacity HO Reasons
based
based HO fulfilledininRNC
HO fulfilled RNC
(31 Intra-Freq neighbours)
RNC
RNCcommands
commandsselected
selectedUE(s)
UE(s)to
tostart
start 48 Inter-Freq neighbours
IF/IS measurements
IF/IS measurements 32 Inter-System neighbours can be measured
Measurements
Measurementsare
aredone
doneinin
Compressed
CompressedMode
Mode(CM)
(CM)
UE
UEreports
reportsGSM
GSMcells
cellswith
with Max 32 neighbours could be measured
strongest
strongest RSSI signalsto
RSSI signals toRNC
RNC
RSSI
RSSImeasurements
measurementsandandBSIC
BSIC Reporting cells are active set cells
verification for GSM cells
verification for GSM cells (max 3) + max 6 IFHO, max 6 ISHO neighb.
RNC
RNCmakes
makesHOHOdecision
decisionand
and Different decision methods for IF HO
commands UE to target cell
commands UE to target cell Only one decision method for IS HO
ISHO 3G -> 2G - AMR Signalling Flow
U Node RNC CN
E B RRC: Measurement
Control ISHO triggering
RRC: Measurement (2 reasons are
Report NBAP: Radio Link possible)
Reconfiguration
NBAP: Radio Link Prepare
Reconfiguration Ready Initial
NBAP: Radio Link Compressed
Reconfiguration Commit
RRC: Physical Channel Mode
RRC: Physical Channel Reconfiguration Configuration
Reconfiguration Complete NBAP: Compressed Mode
Command
RRC: Measurement GSM RSSI
RRC: Measurement Control Measure
Report ment
NBAP: Compressed Mode
Command
RRC: Measurement GSM BSIC
RRC: Measurement Control Identificatio
Report nRANAP: Relocation
Required
RRC: Handover from UTRAN RANAP: Relocation
Command Command
RANAP: IU Release
Command
RANAP: IU Release
Complete
• BSIC verification always performed for AMR calls – no interrupt in voice call
153 © 2006 Nokia

ISHO 3G -> 2G - PS Signalling Flow
U Node RNC CN
E B RRC: Measurement
Control
RRC: Measurement Report ISHO triggering (5 reasons
are possible)
NBAP: Radio Link Reconfiguration

Prepare
Ready Initial
Commit Compressed
RRC: Physical Channel Mode
Reconfiguration Configuration
RRC: Physical Channel Reconfiguration
Complete
NBAP: Compressed Mode Command
RRC: Measurement Control GSM RSSI Measurement

RRC: Measurement Report
RRC: Cell Change Order from

UTRAN RANAP: SRNS Context
Request
RANAP: SRNS Context
Response
RANAP: SRNS Data Forward
Command
RANAP: IU Release
Command
RANAP: IU Release
Complete
• In most cases BSIC verification is not required (data interrupt as UE

moves to 2G)
• PS makes use of RRC: CELL CHANGE ORDER FROM UTRAN message
154 © 2006 Nokia
3G -> 2G Handover measurement
triggering
IS Handover Triggering Reasons
2. Quality deterioration report

1. DL DPCH approaches its
from UL outer loop PC
maximum allowed power
FMCI: IFHOcauseUplinkQuality
FMCI: IFHOcauseTxPwrDL
FMCG: GSMcauseUplinkQuality
FMCG: GSMcauseTxPwrDL
3. Low measured absolute

CPICH Ec/No, event 1E/1F 4. UE Tx power approaches its
HO trigger
FMCI: IFHOcauseCPICHEcNo maximum allowed power, event 6A/6D
FMCG: GSMcauseCPICHEcNo FMCI: IFHOcauseTxPwrUL
FMCG: GSMcauseTxPwrUL
5 . Low measured absolute

CPICH RSCP, events 1E/1F 6 . Others (Not implemented in RAN 1.5):
FMCI: IFHOcauseCPICHrscp, e.g. Traffic & load reason IS-HO, etc
FMCG: GSMcauseCPICHrscp
Frequency Measuring Control for Inter-Frequency = FMCI

Frequency Measuring Control for Inter-System (GSM) = FMCG
Measurement triggering: CPICH Ec/No
Reporting event: 1E: A P-CPICH exceeds an absolute
threshold (triggered if one) 1F: A P-CPICH falls below an
e.g. P-CPICH Ec/No
absolute threshold (triggered if all)

Cell 1 Cell 2
Cell 3
absolute 1E: HHoEcNoCancel

threshold
1F: HHoEcNoThreshold
time
1E: HHoEcNoCancelTime 1F: HHoEcNoTimeHysteresis
• RNC starts IF/IS measurement when event 1F occurs for all

cells in the active set: A Primary CPICH becomes less than
• RNC stops IF/IS measurement when event 1E occurs for at
least one cell of the active set : A Primary CPICH becomes
better than an absolute threshold
• Note:IF/IS measurements can be stopped if event 1Fs
are cancelled by events 1E only when IFHO/ISHO was
not successful and only inside the time between
CM measurements, specified by the time
InterFreqMinMeasInterval ,GsmMinMeasInterval/default
10s, recommendation 2s .
• Filtering applied before event evaluation in the UE:
– FMCS: EcNoFilterCoefficient/0= 200ms filtering period
• Event 1E parameters:
– Triggering conditions: Active set cells
– Hysteresis: not used in 1F
– Threshold used frequency: FMCS : HHoEcNoCancel/ -9dB
– Time-to-trigger: FMCS: HHoEcNoCancelTime/ 1280 ms
– Amount of reporting: infinity
– Reporting interval: not applied.
– Reporting cell status: max 3 active cells.
• Event 1F parameters:
– hysteresis: not used in 1F
– Threshold used frequency: FMCS : HHoEcNoThreshold / - 12dB (range 0..-24 dB)
– Time-to-trigger: FMCS: HHoEcNoTimeHysteresis / 100 ms (range 0..5000ms)
Measurement triggering: CPICH RSCP
Reporting event: 1E: A P-CPICH exceeds an absolute threshold (triggered
if one) 1F: A P-CPICH falls below an absolute threshold
e.g. P-CPICH Rscp
(triggered if all)
Cell 1 Cell 2
Cell 3
absolute 1E: HHoRscpCancel

threshold
1F: HHoRscpThreshold
time
1E: HHoRscpCancelTime 1F: HHoRscpTimeHysteresis
• UE continually monitors pilot channels of BTSs in AS

• If RSCP of a Node B falls below threshold, HHoRscpThreshold,
UE sends event 1F report
• RNC starts IF/IS measurements when event 1F occurs for all cells
in AS
• RNC stops IF/IS measurements when event 1E occurs for at least
one cell of AS
• Note:IF/IS measurements can be stopped if event 1Fs are
cancelled by events 1E only when IFHO/ISHO was not
successful and only inside the time between
CM measurements, specified by the time
InterFreqMinMeasInterval GsmMinMeasInterval/default 10s,
recommendation 2s .
• UE filtering applied before event evaluation using
HHoRscpFilterCoefficient (FMCS) /200ms, range 200…1600ms
• Event 1E (A primary CPICH exceeds an absolute threshold) parameters:

– hysteresis: not used in 1E
– Threshold used frequency: (FMCS) : HHoRscpCancel/ - 90 dBm
– Time-to-trigger: (FMCS): HHoRscpCancelTime/ 1280 ms
• Event 1F (A primary CPICH falls below an absolute threshold) parameters:

– Hysteresis: not used in 1F
– Threshold used frequency: HHoRscpThreshold (FMCS)/ - 93 dBm
– Time-to-trigger: HHoRscpTimeHysteresis (FMCS)/ 100 ms
3G -> 2G Measurements
ISHO parameters
CPICH RSCP (Event 1F) CPICH Ec/Io (Event 1F)
•Thresholds: DL DPCH power •Thresholds:
HHoRscpThreshold •Threshold: HHoEcNoThreshold
HHoRscpCancel GsmDLTxPwrThrXX HHoEcNoCancel
L3 filter: •Data rate threshold •L3 filter:
HHoRscpFilterCoefficie Done already for SHO
nt HHOMAxAllowedBitrate •Timers:
•Timers: DL HHoEcNoTimeHysteresis
HHoRscpTimeHysteresi HHoEcNoCancelTime
s
UE Tx Power (Event 6A) UL Quality
HHoRscpCancelTime
•Threshold: •Timer:
GSM measurement reporting ULQualDetRepThreshol
GsmUETxPwrThrXX
•L3 filter: GsmMeasRepInterval d
GsmUETxPwrFilterCoeff GsmNcellSearchPeriod •Data rate threshold
•Hysteresis margin: GsmMinMeasInterval
GsmUETxPwrTimeHyst HHOMAxAllowedBitrate
GsmMaxMeasPeriod UL
•Data rate threshold
HHOMAxAllowedBitrate Handover Triggering

UL
(XX=AMR,CS,NrtPS,RtPS)
Decision Algorithm
AdjgTxPwrMaxTCH
AdjgRxLevMinHO (n)
GsmMeasAveWindow
2G-to-3G
Handover Execution back prevention
GsmMinHoInterval
ISHO measurements
• After HO triggering message is sent to RNC, a RRC message ”Measurement
Control” is sent to UE containing details of the measurement that the UE
must execute. Measurement reporting is periodical. Max 6 GSM cells could
be measured by UE and reported to RNC. No filtering in measurements by
UE
RRC: ”Measurement control ” message
(GSM RSSI measurements)
RNC
UE
• Upon reception of the measurements reported by the UE, RNC applies a

sliding averaging window to the RXLEV measurements. The averaged levels
are used as input to the IS-HO decision algorithm.The first measurement report
RNC has info from the best GSM cell:
UE BCCH freq & RSSI, no filtering
used in UE
RRC: ”Measurement report”
GsmMeasRepInterval
(default 0.5s) RRC: ”Measurement report”
RXLEV measurements are reported through
”Measurement report” messages
• GSMMeasRepInterval: 0.5 seconds
– This is the interval between measurement reports, which are sent to
BTS
– This parameter should be kept to 0.5 seconds. Increasing the reporting
interval would increase the IS-HO process delay.
• GSMMinMeasInterval: 2 s
– This is Minimum Measurement Interval, wait time when the following
CM starts. In case of an unsuccessful IS-HO attempt, the network will
deactivate compressed mode for a time period given by this
parameter, thus better value will be 2 s to speed up the reactivation of
CM.
• GSMMeasAveWindow: 6 reports
– This is Measurement Averaging Window size, sliding window is used
• GSMMaxMeasPeriod: 12 reports
– This is Maximum Measurement Period which determines the maximum
allowed duration of the inter-system measurement
– If the RNC is not able to execute an inter-system handover, it shall stop
the inter-system measurements after the UE has sent the predefined
number of measurement reports to the RNC.
• Maximum allowed duration of the inter-system measurement is calculated:

– GSMMeasRepInterval * GSMMaxMeasPeriod (=0.5*12) =6s,
• This seems to be too long time, because based on field measurements BSIC
and RSSI delays are about 3 seconds, so it makes senses to reduce the value of
this parameter to some value about 3 seconds, otherwise, if the BSIC or RSSI
measurements fail or if the IS-HO execution is not possible to due low GSM
RSSI levels, the network will not deactivate compressed mode until the timer of
10 seconds has expired. Thus, decreasing the parameter value will allow the
UE/network to initiate a new IS-HO attempt. Proposed value for
GSMMaxMeasPeriod is 6
• GSMNcellSearchPeriod: 0
– This is neighbour cell search period parameter, ISHO is not allowed until the
are enough measurement reports given by this parameter
– O means that only 1 measurement result is enough for decision making
– Duration of the cell search period is calculated:
– GSMRepInterval * GSMNcellSearchPeriod).
ISHO: BSIC Verification
• After the selection of the target GSM cell, the RNC sends to UE the RRC
message "Measurement control” which includes details to measure
”BSIC” .
• UE stops RSSI measurements and updates the transmission gap pattern to
the pattern used for BSIC decoding. The measurement reports are sent
periodically to RNC.
• If the UE is unable to decode the BSIC during the given period, the BSIC
IS-HO
measurement operation is aborted. IS-HO trigger Target Cell found command
WCDM RSSI meas. BSIC verification

A TRSSI depends on TBSIC depends on :
RRC: ”Measurement control ” message
(BSIC decoding)
•Numbers of GSM cells
•Transmission gap pattern for
in the BSIC decoding
RNC neighbour cell list
•Reporting interval
•Sliding averaging
window
•Transmission gap
pattern for
RSSI measurements
3G -> 2G Handover decision
Inter-RAT HO Decision
On this page, you find conditions, which have to be satisfied, before an inter-
frequency handover can be conducted. The best neighbouring cell must fulfil
following criterion („best“ according to Ec/No):
AVE_RXLEV_NCell(n) > GSMncellRxLevMinHO(n) + max(0,

GSMncellTxPwrMaxTCH(n) - P_max)
where
• AVE_RXLEV _Ncell(n) is the averaged GSM carrier RSSI value of the GSM
neighbour cell(n), averaging done directly from dBm values (no linear
averaging); GSMMeasAveWindow / 6, 1…32 meas report.
• GSMncellRxLevMinHO(n) determines the minimum Required RSSI (dBm) level of
the neighbour cell(n). ( -95 dBm)
• GSMncellTxPwrMaxTCH(n) indicated the maximum Tx power level (dBm) an UE
may use in GSM neighbour cell(n).
• P_MAX is the maximum UE power capability.
• If several GSM cells fulfils the equation above, cells are ranked based on HOPG:
GSMncellPriorityCoverage/0, range 0…7
• A cell is ranked higher than another cell if it has a higher priority level
even though its signal strength condition was worse
• Inter-system HO could be forbidden during the first measurements reports from
the UE, to let the UE report all the candidate inter-system cells in its
neighbourhood.
ISHO Decision
E_RXLEV_NCell(n) > AdjgRxLevMinHO(n) + max(0, AdjgTxPwrMaxTCH(n) - P_max
GSM cell
AdjgRxLevMinHO(n)
max(0, AdjgTxPwrMaxTCH(n) - P_max)

3G -> 2G Handover signalling
ISHO analysis with Nemo
ISHO IS TRIGGERED
EVENT 1F
-(48-32)/2 = -8 dB  -8.5 ≤ EcNo < -8
-115 + 11 = -104 dBm  -105 ≤ Rscp <

-104
Compressed mode
started
Tstart = 17:22:41.7
Tstop = 17:22:53.7
Compressed mode MW = 12 s
stopped
axMeasPeriod x GsmMeasRepInterval +4 x GsmMeasRepInterval = 20 x 0.5+ 4x0
RxLev = -110 + 4 = -106 dBm
AdjgRxLevMinHO = -95 dBm
4
POOR GSM
COVERAGE
No suitable cell
AMR Handover procedure
overview (1)
RRC connection setup
ISUP signalling
Parameters for HO event

trigger
e1e, e1f, e6a,e6b
overview (2)
ISUP signalling
Mobility management;
several AS cell add & cell drops
overview (3)
Mobility management;
several AS cell add & cell drops
Measurement report to
Compressed
trigger CM Mode
Parameters
overview (4)
RNC sends updated GSM

NB list
UE sends inter RAT meas.
RNC commands UE to verify
Results
BSIC of
best reported
Target cell
cell BSIC
RNC triggers HO to GSM
verified
target cell
Timing advance
information
UE ends HHO - procedure
UE is handed over to
GSM
2G signalling
Physical Channel reconfiguration
RRC: Physical Channel reconfiguration
Measurement Control new RAT NB list
[..]
new inter RAT NB list

Measurement info
UE Measurement Report GSM cells-RSSI measurements
measured best cell by ARFCN
measured 2nd best cell by ARFCN
measured 3rd best cell by ARFCN
measured 4th best cell by ARFCN

Measurement Control carrying target cell info
UE shall stop measuring RSSI of RAT NB

and focus on best cell´s BSIC verificatio
UE Measurement Report target GSM cell-BSIC
verification
UE reports verified BSIC of best cell to

Handover from UTRAN command
RRC: HO from UTRAN command

Handover command GSM signalling
L3: Handover command
2G cell information (RF&configuration)
2G cell information (PC)
2G cell information (Security)

Cell Selection and
Reselection
2G <-> 3G inter working
Idle mode Connected mode
2G -> 3G reselection 2G -> 3G handover CS AMR
3G -> 2G reselection 2G -> 3G handover PS
3G -> 2G handover CS AMR
3G -> 2G handover PS
3G -> 2G reselection
TS
TS25.304
25.304
Cell Reselection
5.2.3.1.2
5.2.3.1.2 Cell Selection S-Ccriteria
• The cell selection criteria
S are defined as follows: Squal = Q – Qqualmin qualmeas
Srxlev =Qrxlevmeas - Qrxlevmin -Pcompensation

• The cell selection criterion
S for a suitable cell is Squal > 0
fulfilled when: Srxlev > 0
Squal Cell Selection quality value, (dB).

• Where: Srxlev
Not applicable for TDD cells or GSM cells
Cell Selection RX level value (dB)
Qqualmeas Measured cell quality value. The quality of the
received signal expressed in CPICH Ec/N0 (dB) for
FDD cells. Not applicable for TDD cells or GSM cells.
Qrxlevmeas Measured cell RX level value. This is received signal, -115dBm intra
CPICH RSCP for FDD cells (dBm), P-CCPCH RSCP -101dBm GSM
for TDD cells (dBm) and RXLEV for GSM cells (dBm).
Qqualmin Minimum required quality level in the cell (dB). -18dB
Not applicable for TDD cells or GSM cells.
Qrxlevmin Minimum required RX level in the cell. (dBm) -115dBm
Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB)
UE_TXPWR_ Maximum TX power level an UE may use when
MAX_RACH accessing the cell on RACH (read in system information), (dBm)
P_MAX Maximum RF output power of the UE, (dBm)
Cell Reselection
Cell Selection S-Ccriteria
• If system info in the cell indicates that HCS is not used (UseOfHCS) then
for intra-freq, inter-freq and inter-system the UE shall:
• If Squal > Sintrasearch , UE need not perform intra-frequency

measurements.
If Squal <= Sintrasearch , perform intra-frequency measurements.
• If Squal > Sintersearch , UE need not perform inter-frequency

measurements
If Squal <= Sintersearch , perform inter-frequency measurements.
• If Squal > SsearchRAT m, UE need not perform measurements on cells

of RAT "m".
If Squal <= SsearchRATm , perform measurements on cells of RAT "m".
Cell Reselection
Region Condition Neighbour cells to be measured ONLY TRIGGER FOR
MEASURE
1 Squal > Sintrasearch None
2 Sintersearch < Squal ≤ Sintrasearch Intra-frequency cells
3 SsearchRATm < Squal ≤ Intra- and inter-frequency cells

Sintersearch
4 Squal ≤ SsearchRATm Intra-, inter-frequency and inter-RAT cells
Sintrasearch=4dB : Equateto–16dBEc/No
S S Ssearch
Sintersearch=2dB : Equateto–18dBEc/No
intrasearchintersearch RAT
SsearchRAT m
, = 0dB: Equateto–
20dBEc/No 4 3 2 1
WCDMA
CELL
Cell Reselection
Rs = Qmeas ,s + Qhysts(C
s(COMAPREDWITHSELF)
Rn = Qmeas ,n – Qoffsetn(COMPAREDWITHADJACENTCELLS)
Where:
Qmeas Quality value. The quality value of the received signal expressed in
CPICH_Ec/No or CPICH_RSCP_LEV for FDD cells as set by the
Cell_selection_and_reselection_quality_measure information element, P-
CCPCH_RSCP_LEV for TDD cells and RXLEV for GSM cells.
Qhyst1 This specifies the hysteresis for serving cell that is of different radio access
modes or technologies AND for serving FDD cell when cell_selection_and
reselection-quality_measure is set CPICH RSCP..
Qhyst2 This specifies the hysteresis for serving FDD cell when the
cell_selection_and reselection-quality_measure is set CPICH Ec/No.
Qoffset1 This specifies the offset between the two cells when the neighbour cells that
are of different radio access modes or technologies AND for neighbour FDD
cells when cell_selection_and reselection-quality_measure is set CPICH
RSCP
Qoffset2 This specifies the offset between the two cells when neighbour FDD cells
when the cell_selection_and reselection-quality_measure is set CPICH
Ec/No.
Concept
Cell Reselection 3G -> 2G
UE starts GSM measurements if

CPICH EcNo
CPICH Ec/No < qQualMin + sSearchRAT
Serving WCDMA cell
SintraSearch First ranking of all the cells based on calculation, with
CPICH RSCP (WCDMA) and RSSI (GSM) hysteresis parameter
SinterSearch Rs = CPICH RSCP + Qhyst1
Rn= Rxlev(n) - Qoffset1 Neighbour WCDMA or GSM
SsearchRAT
cell calculation with offset
qQualMin parameter
No Yes
Rn (GSM) > Rs (WCDMA)
And
Rxlev (GSM) >QrxlevMin
Second ranking only for WCDMA

cells based on CPICH Ec/No Cell re-selection
to GSM
Rs = CPICH Ec/No + Qhyst2 Cell re-selection to
Rn=CPICH_Ec/No(n)-Qoffset2 WCDMA cell of highest
R value
HCS in use: HCS not in use:
Serving + measured Serving + measured

neighboring cells neighboring cells
S-Criteria OK S-Criteria OK
Fast MS
Cells with If No Cell
Cells with
Highest HCS with H>0 Best
Lower HCS
Priority than Priorities & accept all R
in Serving cell H>0 neighbors
Best Best
R R
Cell Reselection
Neighbour measurements summary
Sx=Squal=
SsearchRATm SlimitsearchRATm Sintersearch Sintrasearch Ec/No
Intra-
No need to HCS not used
frequency Intra-frequency Intra-
measure
Inter-freqency Inter-frequency frequency
neighbour cells
Inter-RAT
Intra-
frequency
Intra- Intra-
Inter- Higher HCS priority
frequency frequency HCS used
frequency Intra-frequency
Inter-freqency Inter-
Higher HCS Inter-frequency
Inter-RAT frequency
priority inter
RAT
Performance
• There is no timer defined how long the GSM should be fulfilling the re-
selection criteria
• However there is running average of 4 GSM measurements which provides
some protection against ping – pong (time vice –based on DRX cycle length
and as sliding window average)
• In case additional protection is needed it can be arranged by using the
Qhyst1 parameter (for WCDMA serving cell RSCP) or AdjgQoffset1 (for
GSM neighbouring cell RxLev)
First ranking of all the cells based on

CPICH RSCP (WCDMA) and RSSI (GSM)
Rs = CPICH RSCP + Qhyst1

Rn= Rxlev(n) - Qoffset1
Parameter
Cell Reselection 3G -> 2G Tuning
General
• When to trigger the cell reselection to 2G depends greatly

on:
– how much the 3G network is requested to be utilised
• target is to maximise the utilisation of WCDMA
network but…
– what is the desired CSSR
• …at the same time maximise the quality
– minimise the possibility of ping – pong
• Due to very different fading conditions, there should be
couple of different parameter sets for 3G -> 2G reselection
– Outdoor, typical outdoor to dedicated indoor (in case of
missing 3G indoor)
– 3G border
– Special indoor cases without dedicated 3G where the UE
speed is high (e.g. tunnels)
ISHO Parameter
Tuning
Cell Reselection 3G -> 2G Outdoor
Call Setup status statistics for each Ec/No range

100% WCDMA intra
90%
frequency search
80%
70%
should be started
60% latest at ~ qQualMin
50% + sSearchIntra = -8
[%]
40% … -10dB
30%
20%
10%
0%
> -4 -4 to - -6 to - -8 to - -10 to -12 to -14 to -16 to -18 to <-21
6 8 10 -12 -14 -16 -18 -21
Ec/No [dB]
As long as the Ec/No

is >-12…-14dB the
CSSR is excellent
qQualMin + sSearchRAT
~ -14dB
2G -> 3G reselection
ll Reselection Algorithm from GSM to FDD-WCDMA (
Cell Reselectio
n List
BCCH: FDD_Qm
in, FDD_Qoffse
t
at least every 5 s
GSM MS starts WCDMA measurements if :
RLA_C< F(Qsearch_I) for 0<Qsearch_I<=7
or
RLA_C> F(Qsearch_I) for 7<Qsearch_I<=15
check
Measurement Updates:
• RLA_C value of the serving cell
• + least 6 strongest non serving GSM cells
Fdd_Qoffset:
If, for suitable UMTS cell select allways
& for a period of 5 s: (value is
no priorities CPICH RSCP > RLA_C + FDD_Qoffset -infinity)
WCDMA cell
between reselection
WCDMA and
neighbours
CPICH Ec/No ≥ FDD_Qmin
FDD_Qmin= -13
ll Reselection Algorithm from GSM to FDD-WCDMA (
• In GSM the UE is usually set to measure UE starts WCDMA measurements if Rxlev

the 3G neighbours all the time I.e. UE starts WCDMA measurements if Rxlev
running average (RLA_C) is below or above
running average (RLA_C) is below or above
certain threshold:
Qsearch_I and Qsearch_P are both set to 7 certain threshold:
RLA_C # Qsearch_I and Qsearch_P (GPRS)
RLA_C # Qsearch_I and Qsearch_P (GPRS)
Cell Reselection
Parameters
• Qsearch_I and Qsearch_P define thresholds. The threshold value also
indicates, when the measurements have to be initiated and performed.
The measurements are either started, when the serving cell‘s RLA is
below or above the threshold value. The default value is 15.
• FDD_Qoffset and FDD_GPRS_Offset define offset values, which have to be
added to the RLA of the serving and non-serving GSM cells. The result is
compared with the RSCP value of the WCDMA cell. The default parameter
is 0.
• FDD_Qmin defines a minimum CPICH Ec/No threshold for WCDMA cell for
cell re-selection.
• FDD_REP_QUANT defines the reporting quantity for UTRAN cell (1=Ec/No
or 0=RSCP, default: 1).
• 3G_Search_PRIO is used to inidicate to the MS if 3G cells can be looked
for when BSIC decoding is required. (0=no, 1=yes, default: 1)
The 3G Cell Reselection list is only used by multi-RAT MSs. The system
information SI2quater and SI2ter can be used to provide 3G cell
information. If the two system information messages carry 3G cell
information, than their lists have to be combined in the UE‘s 3G Cell
Reselection list, which may then hold up to 96 UMTS cells. Up to 8 carrier
Cell Reselection Algorithm
Algorithm for cell re-selection from GSM (GPRS) to the FDD mode in UTRAN
Pre-requisite for cell re-selection to UMTS is, that UTRAN carrier bands are
included in the (GPRS) 3G Cell Reselection list. If so, the MS must update
• RLA_C (RLA_P) value for the serving cell and
• at least 6 strongest non serving GSM cells
at least every 5 seconds. Thereafter, the MS can re-select a suitable
UTRAN cell, based on the S-Criterion. If an FDD cell is suitable, following
two conditions must have been met:
• For a period of 5 seconds, the measured RSCP value must exceed the
PLA_C (RLA_P) of the serving GSM and of all non-serving GSM cells by the
value FDD_Qoffset (FDD_GPRS_Qoffset). Did a cell re-selection occur
within the previous 15 seconds, the FDD_Qoffset value is increased by 5
dB.
• The measured Ec/No value of the FDD cell must be greater or equal than
the broadcasted value FDD_Qmin.
• If the UE as performed a cell re-selection to UTRAN within the previous 5
seconds, a cell re-selection back to UTRAN is not allowed, when a
suitable cell can be found within GSM.
Cell Re-selection Parameters
• Range of FDD_Qmin
– Recommended value is 7 (-13 dBm) New mapping from 05.08 [late 2003]:
UEs have to support new parameter range !
Fdd_Qmin mapping
Range00 11 22 33 44 55 66 77 Aif parameter 0 1 2 3 4 5 6 7
Fdd_Qmin (old) [dB] -20 -19 -18 -17 -16 -15 -14 -13
Fdd_Qmin (new) [dB] -20 -6 -18 -8 -16 -10 -14 -12
dBm -20
-20-19
-19 -18
-18 -17
-17 -16
-16 -15
-15 -14
-14 -13
-13
• FDD_REP_QUANT defines the reporting quantity for UTRAN cell (1=Ec/No or
0=RSCP, default 1)
• 3G_Search_PRIO parameter allows to extend the BSIC reporting interval
from 10 s to 13s by checking the BSICs from non-serving BCCH carriers and
also make WCDMA measurements as often as possible. Range is 0=no,
1=yes, default value 1
old • Defined in the SI2quater and PSI3quater if PBCCH is allocated.
FDD_(GPRS)
FDD_(GPRS)FDD_REP_
FDD_REP_3G_search_
3G_search_
Parameter Qsearch_I Qsearch_PQsearch_P FDD_QMin
Parameter Qsearch_I Qsearch_PQsearch_P FDD_QMin Qoffset
Qoffset QUANT PRIO
QUANT PRIO
Name
Nameforfor 2quater 2quater 3quater 2ter 2(3)quarter
2(3)quarter
2quater 2quater 3quater 2ter 2quater 2ter
2quater 2ter
Sys Info (SI)
Sys Info (SI) (PBCCH)
(PBCCH)
Cell Re-selection Parameters
• In case the reselection is wanted to happen UE can select WCDMA cell if the level of
immediately when the 3G is “good enough” UE can select WCDMA cell if the level of
the serving GSM and non-serving GSM cells
the serving GSM and non-serving GSM cells
just based on CPICH Ec/No value (RSCP has been exceeded by certain offset
has been exceeded by certain offset
for a period of 5 s: CPICH RSCP >
threshold is not used i.e. reselection is done for a period of 5 s: CPICH RSCP >
RLA_C + FDD_Cell_Reselect_Offset
RLA_C + FDD_Cell_Reselect_Offset
RSCP > Rxlev – infinity)
FDD_Qoffset Mapped Comment:

(FDD_Cell_Reselect_Offset to:
)
0 −∞ Always select irrespective of RSCP
value
1 -28dB Reselect in case WCDAM RSCP > GSM

RXLev (RLA_C) –28dB
2 -24dB
… …
14 24dB
15 28dB Reselect in case WCDAM RSCP > GSM
RXLev (RLA_C) +28dB
How to avoid ping-pong ?
• As a general rule the value for FDD_Qmin parameter can be UE will re-select WCDMA cell in case it's
UE will re-select WCDMA cell in case it's
quality is acceptable:
set to –11…-12 dB (i.e. for the case where the QqualMin quality is acceptable:
CPICH Ec/No ≥ Minimum_FDD_Threshold
CPICH Ec/No ≥ Minimum_FDD_Threshold
+Ssearch_RAT = -14dB)
CPICH Ec/No
• The “rule” to set the
FDD_Qmin >= QqualMin + Ssearch_RAT FDD_Qmin value has
not been possible to
be fulfilled until the
FDD_Qmin >=-12
specification change
(05.08 v8.18.0, 2003-
8) has been
QqualMin + Ssearch_RAT
= -14dB implemented to the
UEs – as below
QqualMin = -18dB
t
Camping in 3G Camping in 2G Camping in 3G
Fdd_Qmin mapping
Aif parameter 0 1 2 3 4 5 6 7
Fdd_Qmin (old) [dB] -20 -19 -18 -17 -16 -15 -14 -13
Fdd_Qmin (new) [dB] -20 -6 -18 -8 -16 -10 -14 -12
GSM BCCH 2Quater / 2Ter inf o
CC H
B
Cell Re-selection Example
Non GPRS case
RSCP/
RLA_C Ec/No
Cell re-selection to WCDMA
Serving GSM Cell RLA_C

Qsearch_I=0
(-98 dBm)
FDD_Qoffset =6 (-8 dB)
Measurements starts (serving cell)
FDD_Qmin=0
RSCP
Neighbour WCDMA Cell (-20 dB)
Ec/N0
Minimum Quality Requirement for WCDMA
t
5 sec.
Cell Re-selection Example
GPRS case
RSCP/
RLA_C Ec/No
RLA_P
Cell re-selection to WCDMA
FDD_GPRS_Qoffset =10 (8 d
Serving GSM Cell (Best) Qsearch_P=0
(-98 dBm)
RSCP
Measurements starts (serving cell)
FDD_Qmin
=-20 dB
Neighbour WCDMA Cell Ec/N0
Minimum Quality Requirement for WCDMA

t
5 sec.

Nemo Analysis Workshop

Uploaded by

Document Information

Original Description:

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

Nemo Analysis Workshop

Uploaded by

Copyright:

Available Formats

Topics

1.Nemo Events and Definition

System information is organised in System Information Blocks (SIBs). System information is

position on P-CCPCH: SFN

SIB 1 SIB 2 SIB 3 SIB 18

Master Information Block (MIB):

SIB 1 is valid in one PLMN. The MIB is read in the RRC

T300/N300 The RRC CONNECTION REQUEST retransmission timer

T312/N312 The timer for supervising successful establishment of a

T309 The timer for supervising successful connection establishment

T316 This timer is started when the UE detects an out of service

System Information Block 2 (SIB 2)

System Information Block 4 (SIB 4)

System Information Block 7 (SIB 7)

System Information Block 16 (SIB 16)

UTRAN controls the measurements in the UE, either by

Transition from the RRC idle state to the CELL_DCH sub-state

Transition from the CELL_FACH to the CELL_DCH sub-state.

Measurement results can be only transmitted in the CELL_DCH or CELL_FACH sub-state.

Additional measurements list

Following reporting events were specified:

UE Buffer triggers Threshold for RAB Upgrade

First RAB Reconfiguration

Second RAB Reconfiguration

Cell DCH  Cell FACH

Cell FACH  Cell PCH

Cell PCH  Cell FACH

Cell FACH  Cell DCH

The following three parameters are used:

Two Cells in the Neighbour

Neighbour List Cell

Step 1: Active set cells

RRC Connection Establishment – CELL DCH State

RRC RANAP: Initial UE Message (MM: CM Service Request)

Connection till SCCP: CC (Connection Confirm)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Response)

RANAP: Security Mode Command

RRC: Security Mode Command

RANAP: Security Mode Complete

RANAP: Direct Transfer (CC: Setup)

RRC: Downlink Direct Transfer (CC: Call Confirmed)

RAB Establishment RANAP: RAB Assignment Request

NBAP: Radio Link Reconfiguration Prepare

RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (CC: Release)

RRC: Downlink Direct Transfer (CC: Release)

RANAP: Direct Transfer (CC: Release Complete)

RANAP: Iu Release Command

RANAP: Iu Release Complete

ALCAP: ERQ (Establish Request)

ALCAP: ECF (Establish Confirm)

RRC Connection Establishment – CELL DCH State

RANAP: Initial UE Message (MM: Paging Response)

SCCP: CC (Connection Confirm)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Response)

RANAP: Security Mode Command

RANAP: Security Mode Complete

RANAP: Direct Transfer (CC: Setup)