LTE Training – Day 6

Protocol Stacks and

Signalling Procedures

1 © Nokia Siemens Networks

Content
• Protocols Stacks
• Measurement Reporting Events
• Measurement Configuration
• System Information Blocks
• Signalling Procedures
– Paging
– RRC Connection Establishment
– Attach and Default Bearer Establishment
– Dedicated Bearer Establishment
– RRC Connection Re-establishment
– Tracking Area Update
– Intra-Frequency Handover
– Inter-Frequency Handover
– IRAT Handover
– CS Fallback

2 © Nokia Siemens Networks

Protocol Stacks

3 © Nokia Siemens Networks

User Plane
• The user plane protocol stack provides support for the transfer of application data
• The radio access network uses:
– PDCP
– RLC (unacknowledged or acknowledged mode)
– MAC
– Layer 1

Application Application

TCP/UDP TCP/UDP

IP Relay
IP
Relay Relay IP IP
PDCP
PDCP GTP-U GTP-U GTP-U GTP-U

RLC RLC UDP UDP UDP UDP

MAC Air- MAC IP IP IP IP L1/L2 L1/L2

Interface S1 S5/S8 SGi
L1 L1 L1/L2 L1/L2 L1/L2 L1/L2

UE eNode B Serving Gateway PDN Gateway Server

4 © Nokia Siemens Networks

PDCP Layer (I)
• The PDCP layer is responsible for:
– transfer of user plane and control plane data
– header compression for user plane data using ROHC
– integrity protection for control plane data
– ciphering
– in-sequence delivery

• Robust Header
Compression (ROHC) is
specified by the IETF

5 © Nokia Siemens Networks

PDCP Layer (II)
• A relatively small set of PDCP parameters are configured by the RRC layer

A packet is discarded
if its discard timer
expires

ROHC profiles for

header compression
(different profile for
each protocol stack)

6 © Nokia Siemens Networks

 PDCP PDU (I)
• Different Data PDU formats are defined for the control and user plane

5 bit sequence
number (0 to 31)
Control Plane
Data PDU
Message
Authentication Code
used for integrity
protection

12 bit sequence
User Plane Data PDU number (0 to 4095)
(long SN for AM or UM RLC)

7 bit sequence
number (0 to 127)
User Plane Data PDU
(short SN for UM RLC)

7 © Nokia Siemens Networks

PDCP PDU (II)
• Control PDU are defined for ROHC feedback and receiver status reporting

Control PDU for Interspersed

ROHC feedback

ROHC feedback packet

Applicable to
RLC AM and UM

Control PDU for PDCP

Status Report Sequence number of first
missing PDCP SDU

Applicable to Indication of which SDU have

RLC AM been successfully received

8 © Nokia Siemens Networks

RLC Layer
• The RLC layer can be configured to operate in 1 of 3 modes:
– Transparent (control plane)
– Unacknowledged (user plane)
– Acknowledged (user plane or control plane)

Control Plane User Plane

Transparent mode Unacknowledged mode
Acknowledged mode Acknowledged mode

9 © Nokia Siemens Networks

Transparent Mode
• Transparent mode is applicable to
BCCH, CCCH and PCCH
• There is no segmentation nor
concatenation
• Transparent mode does not add
any header information

• Transparent mode is used by:

– System Information
– Paging
– RRC Connection Re-establishment Request
– RRC Connection Re-establishment
– RRC Connection Re-establishment Reject Transfers a single higher
SRB0 – RRC Connection Request layer packet
– RRC Connection Setup
– RRC Connection Reject Transparent Mode

10 © Nokia Siemens Networks

Unacknowledged Mode (I)

• Unacknowledged mode is
applicable to DTCH, MCCH and
MTCH
• Segmentation and concatenation
can be applied
• A minimum of 1 byte of header
information is included
• Unacknowledged mode includes a
sequence number to allow:
– re-ordering and in-sequence
delivery to the higher layers
– detection of missing packets
• Sequence number can be 5 or 10
bits
• Length indicators can also be
included to mark the start/end of
higher layer packets

11 © Nokia Siemens Networks

Unacknowledged Mode (II) 5 bit Sequence Number

• eNode B provides the UE with:

– sequence number length to be used
– re-ordering timer
10 bit Sequence Number

• Unacknowledged mode also uses a With length indicators

receiving window size:
– window size = 16 for a 5 bit SN
– window size = 512 for a 10 bit SN

Framing Information
12 © Nokia Siemens Networks (segmentation of higher layer packet)
Acknowledged Mode (I)

• Acknowledged mode includes a

sequence number to allow re-
ordering and in-sequence delivery to
the higher layers
• Acknowledged mode also provides
support for polling and status
reporting to acknowledge
successfully received data
• Re-transmissions can be sent using
an ARQ protocol
• Sequence number is 10 bits
• Length indicators can also be
included to mark the start/end of
higher layer packets

13 © Nokia Siemens Networks

Acknowledged Mode (II)
• A relatively small set of parameters are configured by the RRC layer

Defines the waiting time for a

Status Report after sending a Poll
A poll is re-transmitted if timer
Defines the number of transmitted expires
PDU after which a Poll is sent

Defines the
number of
transmitted
bytes after
which a Poll is Maximum number of RLC re-
sent transmissions

Time allowed for re-ordering before Minimum time between

passing packets to higher layers transmissions of Status Report

14 © Nokia Siemens Networks

Acknowledged Mode (III)
• Data PDU can be sent with or without length indicators
• Sequence Number length is always 10 bits

PDU without length indicators PDU with length indicators

Re-segmentation
Data or flag
Control PDU Framing
Polling Bit Information

15 © Nokia Siemens Networks

Acknowledged Mode (IV)
• Data PDU segments can be used for re-transmitting parts of data PDU
• Applicable if a reduced data block size is used for re-transmissions
• The SO field indicates the position of the AMD PDU segment in bytes within
the original AMD PDU

PDU Segment without length indicators PDU Segment with length indicators

Segment Offset (SO)

16 © Nokia Siemens Networks

RLC Control PDU
• The Status PDU is the only RLC Control PDU
• Sent by the receiving side to provide the sending side with information
regarding successfully and unsuccessfully received PDU
• ACK_SN informs the transmitting side that all PDU up to ACK_SN (but not
including) have been successfully received, with the exception of any that are
specified using NACK_SN

Control PDU Type

• NACK_SN specifies the Sn of the AMD PDU that has been detected as lost
– SO start specifies the start of the portion of the AMD PDU that has been
detected as lost (quantified in terms of byte position)
– SO end specifies the end of the portion of the AMD PDU that has been
detected as lost (quantified in terms of byte position)
17 © Nokia Siemens Networks
MAC Layer

• Functions provided by the MAC layer are shown in the table below

• The MAC layer also supports:

– Random Access
– Maintenance of Uplink Time Alignment
– DRX

18 © Nokia Siemens Networks

MAC PDU (I)
• A MAC PDU includes a header field and a payload field
• The header field includes one or more subheaders
• The payload includes:
– one or more MAC Control Elements Subheaders
– one or more MAC SDU

19 © Nokia Siemens Networks

MAC PDU (II) Back-Off Indicator Subheader

• The Random Access Response (RAR)

originates from the MAC layer
• A RAR PDU includes a header field and a Random Access Preamble
payload field Identity Subheader
• The header field includes one or more
subheaders
• The payload field includes one or more RAR
RAR PDU
• Uplink Grant within RAR PDU includes other
parameters, e.g. Hopping Flag, CSI Request,
TPC Command, MCS and PRB assignment

20 © Nokia Siemens Networks

MAC Control Elements

• 3GPP TS 36.321 specifies the following MAC Control Elements:

– Buffer Status Report MAC Control Elements
– C-RNTI MAC Control Element
– DRX Command MAC Control Element
– UE Contention Resolution Identity MAC Control Element
– Timing Advance Command MAC Control Element
– Power Headroom MAC Control Element
– Extended Power Headroom MAC Control Element
– MCH Scheduling Information MAC Control Element
– Activation/Deactivation MAC Control Element

21 © Nokia Siemens Networks

RRC Signalling
• The RRC protocol stack layer allows signalling between the UE and eNode B
• It also provides support for the transfer of Non-Access Stratum (NAS) messages
between the UE and eNode B
– S1 Application Protocol (S1-AP) used to transfer NAS messages between
eNode B and MME
• The RRC protocol is specified within 3GPP TS 36.331

RRC RRC
PDCP PDCP

RLC RLC
Air-
MAC Interface MAC
L1 L1
UE eNode B

22 © Nokia Siemens Networks

RRC Messages
• The complete set of messages belonging to the RRC signalling protocol
is presented below
• These are transferred using SRB0, SRB1 and SRB2
– CounterCheck – RRCConnectionReestablishment
– CounterCheckResponse – RRCConnectionReestablishmentComplete
– CSFBParametersRequestCDMA2000 – RRCConnectionReestablishmentReject
– CSFBParametersResponseCDMA2000 – RRCConnectionReestablishmentRequest
– DLInformationTransfer – RRCConnectionReject
– HandoverFromEUTRAPreparationRequest – RRCConnectionRelease
– InterFreqRSTDMeasurementIndication – RRCConnectionRequest
– LoggedMeasurementConfiguration – RRCConnectionSetup
– MasterInformationBlock – RRCConnectionSetupComplete
– MBMSCountingRequest – SecurityModeCommand
– MBMSCountingResponse – SecurityModeComplete
– MBSFNAreaConfiguration – SecurityModeFailure
– MeasurementReport – SystemInformation
– MobilityFromEUTRACommand – SystemInformationBlockType1
– Paging – UECapabilityEnquiry
– ProximityIndication – UECapabilityInformation
– RNReconfiguration – UEInformationRequest
– RNReconfigurationComplete – UEInformationResponse
– RRCConnectionReconfiguration – ULHandoverPreparationTransfer
– RRCConnectionReconfigurationComplete – ULInformationTransfer

23 © Nokia Siemens Networks

Signalling Radio Bearers (SRB)
• LTE uses 3 SRB:
– SRB0
 RRC messages using the CCCH logical channel
– SRB1
 RRC messages (which may include a piggybacked NAS message)
 NAS messages prior to the establishment of SRB2
 transfers DCCH logical channel
– SRB2
 RRC messages (which include logged measurement information as
well as for NAS messages)
 transfers DCCH logical channel

• SRB2 has a lower-priority than SRB1 and is always configured by E-

UTRAN after security activation
• Once security is activated, all RRC messages on SRB1 and SRB2 are
integrity protected and ciphered by PDCP

24 © Nokia Siemens Networks

NAS Signalling
• Non-Access Stratum (NAS) signalling allows the transfer of control plane
messages between the UE and the MME
• NAS messages are specified within 3GPP TS 24.301

NAS NAS
Relay S1-AP
RRC RRC S1-AP

PDCP PDCP SCTP SCTP

RLC RLC IP IP

MAC Air- MAC L2 L2

Interface S1
L1 L1 L1 L1

UE eNode B eNode B MME

25 © Nokia Siemens Networks

NAS Messages
• NAS messages within 3GPP TS 24.301 are categorised as Mobility
Management or Session Management
EPS Session Management messages
EPS Mobility Management messages – Activate dedicated EPS bearer context accept
– Activate dedicated EPS bearer context reject
– Attach accept – Security mode command – Activate dedicated EPS bearer context request
– Attach complete – Security mode complete – Activate default EPS bearer context accept
– Attach reject – Security mode reject – Activate default EPS bearer context reject
– Attach request – Security protected NAS message – Activate default EPS bearer context request
– Authentication failure – Service reject – Bearer resource allocation reject
– Authentication reject – Service request – Bearer resource allocation request
– Authentication request – Tracking area update accept – Bearer resource modification reject
– Authentication response – Tracking area update complete – Bearer resource modification request
– CS service notification – Tracking area update reject – Deactivate EPS bearer context accept
– Detach accept – Tracking area update request – Deactivate EPS bearer context request
– Detach request – Uplink NAS Transport – ESM information request
– Downlink NAS Transport – Downlink generic NAS transport – ESM information response
– EMM information – Uplink generic NAS transport – ESM status
– EMM status – Modify EPS bearer context accept
– Extended service request – Modify EPS bearer context reject
– GUTI reallocation command – Modify EPS bearer context request
– GUTI reallocation complete – PDN connectivity reject
– Identity request – PDN connectivity request
– Identity response – PDN disconnect reject
– PDN disconnect request

26 © Nokia Siemens Networks

X2 Signalling
• The X2 Application Protocol (X2-AP) allows signalling between neighbouring
eNode B
• The X2-AP is specified within 3GPP TS 36.423

X2-AP functions

X2-AP X2-AP

SCTP SCTP

IP IP
X2
L1/L2 L1/L2

eNode B eNode B

27 © Nokia Siemens Networks

X2-AP Messages
Messages for Global Procedures
• X2-AP messages are associated with: – LOAD INFORMATION
– mobility procedures – ERROR INDICATION
– X2 SETUP REQUEST
– global procedures – X2 SETUP RESPONSE
– X2 SETUP FAILURE
– RESET REQUEST
– RESET RESPONSE
– ENB CONFIGURATION UPDATE
– ENB CONFIGURATION UPDATE ACKNOWLEDGE
– ENB CONFIGURATION UPDATE FAILURE
– RESOURCE STATUS REQUEST
– RESOURCE STATUS RESPONSE
– RESOURCE STATUS FAILURE
– RESOURCE STATUS UPDATE
– MOBILITY CHANGE REQUEST
Messages for Mobility Procedures – MOBILITY CHANGE ACKNOWLEDGE
– HANDOVER REQUEST – MOBILITY CHANGE FAILURE
– HANDOVER REQUEST ACKNOWLEDGE – RLF INDICATION
– HANDOVER PREPARATION FAILURE – HANDOVER REPORT
– SN STATUS TRANSFER – CELL ACTIVATION REQUEST
– UE CONTEXT RELEASE – CELL ACTIVATION RESPONSE
– HANDOVER CANCEL – CELL ACTIVATION FAILURE

28 © Nokia Siemens Networks

 Class 2 procedures
S1 Signalling Class 1
procedures
• The S1 Application Protocol (S1-AP)
allows signalling between an eNode B
and the MME
• The S1-AP is specified within 3GPP TS
36.413
• Class 1 procedures have an associated
response
• Class 2 procedures do not require a
response

S1-AP S1-AP

SCTP SCTP

IP IP
S1
L1/L2 L1/L2

eNode B MME

29 © Nokia Siemens Networks

S1-AP Messages (I)
• S1-AP messages are categorised as:
– E-RAB Management – Location Reporting
– Context Management – Warning Message Transmission
– Handover Signalling – eNode B Direct Information Transfer
– Paging – MME Direct Information Transfer
– NAS Transport – eNode B Configuration Transfer
– Management – MME Configuration Transfer
– S1 CDMA2000 Tunneling – Cell Traffic Trace
– UE Capability Information Indication – LPPa Transport
– Trace
Context Management
E-RAB Management – INITIAL CONTEXT SETUP REQUEST
– E-RAB SETUP REQUEST – INITIAL CONTEXT SETUP RESPONSE
– E-RAB SETUP RESPONSE – INITIAL CONTEXT SETUP FAILURE
– E-RAB MODIFY REQUEST – UE CONTEXT RELEASE REQUEST
– E-RAB MODIFY RESPONSE – UE CONTEXT RELEASE COMMAND
– E-RAB RELEASE COMMAND – UE CONTEXT RELEASE COMPLETE
– E-RAB RELEASE RESPONSE – UE CONTEXT MODIFICATION REQUEST
– E-RAB RELEASE INDICATION – UE CONTEXT MODIFICATION RESPONSE
– UE CONTEXT MODIFICATION FAILURE
30 © Nokia Siemens Networks
S1-AP Messages (II)

Handover Signalling NAS Transport

– HANDOVER REQUIRED – INITIAL UE MESSAGE
– HANDOVER COMMAND – DOWNLINK NAS TRANSPORT
– HANDOVER PREPARATION FAILURE – UPLINK NAS TRANSPORT
– HANDOVER REQUEST – NAS NON DELIVERY INDICATION
– HANDOVER REQUEST ACKNOWLEDGE
– HANDOVER FAILURE
– HANDOVER NOTIFY Management
– PATH SWITCH REQUEST – RESET
– PATH SWITCH REQUEST ACKNOWLEDGE – RESET ACKNOWLEDGE
– PATH SWITCH REQUEST FAILURE – ERROR INDICATION
– HANDOVER CANCEL – S1 SETUP REQUEST
– HANDOVER CANCEL ACKNOWLEDGE – S1 SETUP RESPONSE
– eNB STATUS TRANSFER – S1 SETUP FAILURE
– MME STATUS TRANSFER – ENB CONFIGURATION UPDATE
– ENB CONFIGURATION UPDATE ACKNOWLEDGE
– ENB CONFIGURATION UPDATE FAILURE
Paging – MME CONFIGURATION UPDATE
– PAGING – MME CONFIGURATION UPDATE ACKNOWLEDGE
– MME CONFIGURATION UPDATE FAILURE
– OVERLOAD START
– OVERLOAD STOP

31 © Nokia Siemens Networks

Measurement Reporting Events

32 © Nokia Siemens Networks

Event A1 – Serving becomes Better than Threshold
• Event A1 is triggered when:

Ms  Hys  Thresh

• Triggering stops when:

Ms  Hys  Thresh

• Ms is the measurement result of the serving cell

• Hys is the hysteresis parameter for this event
• Thresh is the threshold parameter for this event

• Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.

• Hys is expressed in dB.
• Thresh is expressed in the same unit as M

33 © Nokia Siemens Networks

Event A2 – Serving becomes Worse than Threshold
• Event A2 is triggered when:

Ms  Hys  Thresh

• Triggering stops when:

Ms  Hys  Thresh

• Ms is the measurement result of the serving cell

• Hys is the hysteresis parameter for this event
• Thresh is the threshold parameter for this event

• Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.

• Hys is expressed in dB.
• Thresh is expressed in the same unit as M

34 © Nokia Siemens Networks

Event A3 – Neighbour becomes Offset better than
Primary Cell
• Event A3 is triggered when: Mn  Ofn  Ocn  Hys  Mp  Ofp  Ocp  Off

• Triggering stops when: Mn  Ofn  Ocn  Hys  Mp  Ofp  Ocp  Off

• Mn is the measurement result of the neighbouring cell

• Ofn is the frequency specific offset of the frequency of the neighbour cell
• Ocn is the cell specific offset of the neighbour cell
• Mp is the measurement result of the Pcell
• Ofp is the frequency specific offset of the primary frequency
• Ocp is the cell specific offset of the PCell
• Hys is the hysteresis parameter for this event
• Off is the offset parameter for this event

• Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ

• Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB

35 © Nokia Siemens Networks

Event A4 – Neighbour becomes better Threshold

• Event A4 is triggered when: Mn  Ofn  Ocn  Hys  Thresh

• Triggering stops when: Mn  Ofn  Ocn  Hys  Thresh

• Mn is the measurement result of the neighbouring cell

• Ofn is the frequency specific offset of the frequency of the neighbour cell
• Ocn is the cell specific offset of the neighbour cell
• Hys is the hysteresis parameter for this event
• Thresh is the threshold parameter for this event

• Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ

• Ofn, Ocn, Hys are expressed in dB
• Thresh is expressed in the same unit as Ms

36 © Nokia Siemens Networks

Event A5 – Primary Cell becomes worse than
Threshold1 & Neighbour becomes better than
Threshold2
• Event A5 is triggered when: Mp  Hys  Thresh1
Mn  Ofn  Ocn  Hys  Thresh 2

• Triggering stops when: Mp  Hys  Thresh1

Mn  Ofn  Ocn  Hys  Thresh 2

• Mp is the measurement result of the PCell

• Mn is the measurement result of the neighbouring cell
• Ofn is the frequency specific offset of the frequency of the neighbour cell
• Ocn is the cell specific offset of the neighbour cell
• Hys is the hysteresis parameter for this event
• Thresh1 is the threshold parameter for this event
• Thresh2 is the threshold parameter for this event
• Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ
• Ofn, Ocn, Hys are expressed in dB
• Thresh1 is expressed in the same unit as Mp
• Thresh2 is expressed in the same unit as Mn
37 © Nokia Siemens Networks
Event A6 – Neighbour becomes Offset better than
Secondary Cell

• Event A6 is triggered when: Mn  Ocn  Hys  Ms  Ocs  Off

• Triggering stops when: Mn  Ocn  Hys  Ms  Ocs  Off

• Mn is the measurement result of the neighbouring cell

• Ocn is the cell specific offset of the neighbour cell
• Ms is the measurement result of the serving cell
• Ocs is the cell specific offset of the serving cell
• Hys is the hysteresis parameter for this event
• Off is the offset parameter for this event
• Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ
• Ocn, Ocs, Hys, Off are expressed in dB

38 © Nokia Siemens Networks

Event B1 – Inter RAT Neighbour becomes better
than Threshold

• Event B1 is triggered when: Mn  Ofn  Hys  Thresh

• Triggering stops when: Mn  Ofn  Hys  Thresh

• Mn is the measurement result of the inter-RAT neighbour cell, not taking into account
any offsets. For CDMA 2000 measurement result, pilotStrength is divided by -2
• Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell (i.e.
offsetFreq as defined within the measObject corresponding to the frequency of the
neighbour inter-RAT cell)
• Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within
reportConfigInterRAT for this event)
• Thresh is the threshold parameter for this event (i.e. b1-Threshold as defined within
reportConfigInterRAT for this event). For CDMA2000, b1-Threshold is divided by -2
• Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-
RAT neighbour cell
• Ofn, Hys are expressed in dB

39 © Nokia Siemens Networks

Event B2 – Primary Cell becomes worse than
Threshold1 and Inter RAT Neighbour becomes
better than Threshold2
• Event B2 is triggered when: Mp  Hys  Thresh1
Mn  Ofn  Hys  Thresh 2

• Triggering stops when: Mp  Hys  Thresh1

Mn  Ofn  Hys  Thresh 2

• Mp is the measurement result of the PCell, not taking into account any offsets
• Mn is the measurement result of the inter-RAT neighbour cell, not taking into account
any offsets
• Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell
• Hys is the hysteresis parameter for this event
• Thresh1 is the threshold parameter for this event
• Thresh2 is the threshold parameter for this event
• Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ
• Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT
neighbour cell

40 © Nokia Siemens Networks

Layer 3 Filtering
• Measurements are filtered prior to event evaluation

Fn  (1  a )  Fn 1  a  M n

• Mn is the latest received measurement result from the physical layer

• Fn is the updated filtered measurement result
• Fn-1 is the old filtered measurement result
• F0 is set to M1 when the first measurement result from the physical layer is received
• a = 1/2(k/4), where k is the filterCoefficent (a=1 when k=0)

• A sampling period of 200 ms is assumed

– the filter must be adapted to maintain the same characteristic if a different
sampling period is used
• Filtering is completed in the same domain as used for the evaluation of
reporting criteria, i.e. logarithmic filtering for logarithmic measurements

41 © Nokia Siemens Networks

Measurement Configuration

42 © Nokia Siemens Networks

Measurement Configuration
• Measurement reporting can be used to trigger handovers
• The eNode B provides the UE with instructions
• Measurement Configuration information can be included within an
RRC Connection Reconfiguration message
• The Measurement Configuration includes:
– Measurement Object
– Reporting Configuration
– Measurement Identity
Measurement
Object

Reporting
Configuration

Measurement
Identity

43 © Nokia Siemens Networks

Measurement Objects

• One or more Measurement Objects can be defined for each RAT:

– intra and inter-frequency: defines a single LTE RF carrier
– inter-RAT UMTS: defines a set of cells on a single UMTS RF carrier
– inter-RAT GERAN: defines a set of GERAN RF carriers

44 © Nokia Siemens Networks

LTE Measurement Object
• Frequency specific and
cell specific
measurement offsets
can be applied

45 © Nokia Siemens Networks

UMTS Measurement Object
• UMTS measurement object defines a set of cells on a specific RF carrier
• A frequency specific offset can be defined

46 © Nokia Siemens Networks

GERAN Measurement Object
• GERAN measurement object defines a set of cells on a specific RF carrier
• A frequency specific offset can be defined

47 © Nokia Siemens Networks

Reporting Configurations
• Reporting Configurations can be defined for:
– LTE
– inter-RAT

• A list of reporting configurations where each reporting configuration

consists of the following:
– Reporting criterion: The criterion that triggers the UE to send a
measurement report. This can either be periodical or a single event
description
– Reporting format: The quantities that the UE includes in the
measurement report and associated information (e.g. number of cells
to report)

48 © Nokia Siemens Networks

LTE Reporting Configuration
• Reporting
configuration
defines either
event driven or
periodic reporting
• Event driven
allows the
definition of events
A1 to A6
• Triggering and
reporting quantities
can be specified as
RSRP or RSRQ
• Also defines the
number of cells to
be reported, the
reporting interval
and the number of
reports to send

49 © Nokia Siemens Networks

Inter-RAT Reporting Configuration
• Reporting
configuration
defines either
event driven or
periodic reporting
• Event driven
allows the
definition of events
B1 and B2
• Defines the
number of cells to
be reported, the
reporting interval
and the number of
reports to send

50 © Nokia Siemens Networks

Measurement Identities
• Measurement Identity is used to link a Measurement Object to a Reporting
Configuration
• Multiple Measurement Identities can be used to link:
– more than one Measurement Object to a single Reporting Configuration
– more than one Reporting Configuration to a single Measurement Object
• The Measurement Identity is used as a reference within the Measurement
Report message

51 © Nokia Siemens Networks

Measurement Identities, Reporting Configurations
& Measurement Objects

Single Intra-Frequency Measurement Meas. Id 1

RF Carrier Object 1 Meas. Id 2

Single Intra-Frequency Measurement Meas. Id 3 Reporting Reporting

RF Carrier Object 2 Config. 1 Config. 2
LTE BTS Meas. Id 4

Single Inter-Frequency Measurement Meas. Id 5

RF Carrier Object 3 Meas. Id 6

Single Inter-RAT Measurement

Meas. Id 7
UTRAN RF Carrier Object 4
Reporting
UTRAN
Config. 3
BTS Single Inter-RAT Measurement Meas. Id 8
UTRAN RF Carrier Object 5

Set of Inter-RAT Measurement Reporting

GERAN Meas. Id 9
GERAN RF Carriers Object 6 Config. 4
BTS

52 © Nokia Siemens Networks

System Information

53 © Nokia Siemens Networks

Master Information Block (MIB)
• The MIB is broadcast using the BCH and PBCH
• The content of the MIB is shown below:
Channel Bandwidth
in Resource Blocks

8 bits of
the SFN

PHICH Capacity
Number of OFDMA symbols
across which PHICH is
distributed

54 © Nokia Siemens Networks

SIB1
• SIB1 is broadcast using the DL-SCH
and PDSCH
• Specifies:
– the list of PLMN and the Tracking
Area Code (TAC)
– access restriction information
– cell selection criteria
– operating band

-130 dBm
• Also specifies scheduling information
of the remaining SIB
• SIB2 is always present in the first
scheduled System Information
message

55 © Nokia Siemens Networks

SIB2 (I)
• SIB2 includes radio resource
configuration information

RACH

BCCH

PCCH

PRACH
56 © Nokia Siemens Networks
SIB2 (II)
PDSCH

PUSCH

PUCCH Timers
and
SRS Constants

Uplink
UL Power RF
Control Uplink
Sync.
UL Cyclic
Prefix
57 © Nokia Siemens Networks
SIB3
• SIB3 includes cell reselection information

Hysteresis for cell ranking

Inter-frequency and Inter-RAT

measurement triggering threshold
Serving cell threshold for cell
reselection to lower priority layer
Absolute priority for serving cell
Target cell Qrxlevmin for intra-
frequency cell reselection
Intra-frequency Measurement TDD and
triggering threshold Treselection
MBSFN time-to-trigger
configuration
Indication of whether or not measurements
can be recorded from antenna 1
58 © Nokia Siemens Networks
SIB4
• SIB4 includes intra-frequency cell reselection parameters

PCI

Cell specific offset

59 © Nokia Siemens Networks

Paging

60 © Nokia Siemens Networks

Paging Occasions
• UE apply DRX to reduce power consumption
• Paging Occasion (PO) defines 1 subframe during which the UE may receive a
PDCCH with its CRC scrambled by the P-RNTI
• Paging Frame (PF) defines radio frame which includes the PO
• UE monitor 1 PO per DRX cycle

Paging Frame is defined by:

T is the minimum of
SFN mod T= (T div N)*(UE_ID mod N) the default and UE
specific DRX cycles

DRX Cycle Min(T,nB) Default DRX cycle

and nB are broadcast
IMSI mod 1024 in SIB2

Paging Occasion is defined by:

Max(1,nB/T) i_s = floor(UE_ID/N) mod Ns

61 © Nokia Siemens Networks

S1-AP Paging message
• MME forwards the S1-AP: Paging message to the eNode B
• Specifies the UE identity and list of Tracking Area Identities
• Core Network Domain is also specified
• The UE Identity Index allows the eNode B to calculate the Paging Frame
without having to signal the IMSI across the S1 interface
• The UE Paging Identity is typically S-TMSI, but can also be the IMSI

62 © Nokia Siemens Networks

RRC Paging message
• Paging record includes only the UE identity and the core network domain
• Up to 16 paging records can be included within each paging message

63 © Nokia Siemens Networks

RRC Connection Establishment

64 © Nokia Siemens Networks

Signalling eNode B

UE

• RRC Connection Establishment

involves a 3-way handshake RRC Connection Request / SRB 0 / CCCH / UL-SCH / PUSCH

• In contrast to UMTS, RRC Connection Setup / SRB 0 / CCCH / DL-SCH / PDSCH

– there is no NBAP signalling
to establish a radio link RRC Connection Setup Complete / SRB 1 / DCCH / UL-SCH / PUSCH

– there is no ALCAP signalling

to establish a transport
connection
– flat network architecture eNode B

– Intial NAS message can be

UE
included within the Complete
message
– No re-transmissions of the
RRC Connection Request RRC Connection Request / SRB 0 / CCCH / UL-SCH / PUSCH

message from layer 3

RRC Connection Reject / SRB 0 / CCCH / DL-SCH / PDSCH

65 © Nokia Siemens Networks

Signalling
• An example of RRC connection establishment from within XCAP is shown
below
• Procedure completed in just over 100 ms

66 © Nokia Siemens Networks

RRC Connection Request
From UE log file
• Transferred using
the CCCH logical
channel (SRB 0)
• RRC Message
includes only:
– UE identity
– establishment From 36.331
cause
• Majority of message
is occupied by UE
identity:
– 5 bytes
• Establishment cause
has 8 values so
occupies 3 bits

67 © Nokia Siemens Networks

RRC Connection Establishment Causes

• 3GPP TS 24.301
specifies the
mapping between
NAS procedure and
RRC connection
establishment cause

68 © Nokia Siemens Networks

RRC Connection Setup (I)
Example (part 1)
• Transferred using the CCCH logical
channel (SRB 0)

Timer between RLC polls

(requests for status reports)

Number of PDU which trigger a poll

Number of bytes which trigger a poll
Maximum number of RLC re-transmissions

• Both the RLC and Logical Channel

configurations can be signalled using
either:
– Explicit Configuration
– Default Configuration

69 © Nokia Siemens Networks

RRC Connection Setup (II)

Maximum number of Example (part 2)

HARQ re-transmissions

Timers for transmission of Buffer Status Report

TTI Bundling not used

Maximum interval between timing advance

commands for UE to remain ‘time aligned’

Used when calculating the ratio of

PDSCH EPRE to cell-specific RS EPRE

Provide inputs to power control calculation

Power control parameters

70 © Nokia Siemens Networks

RRC Connection Setup (III)

Reporting Mode 3-0

(configured sub-band without PMI) Example (part 3)
Allocated resource for PUCCH format 2
Timing for CQI reports
Reporting Mode 1-0
(wideband without
PMI)
Timing for RI reports
Open loop spatial multiplexing
Codebook is not restricted
Antenna selection not used

Scheduling Request resource

Scheduling Request timing
Maximum number of Scheduling
Request transmissions

71 © Nokia Siemens Networks

RRC Connection Setup Complete
• RRC Connection Setup Complete message includes only a few information
elements
• Selected PLMN Identity defines a pointer towards the list of PLMN broadcast
within SIB1
• Registered MME defines the GUMMEI (Globally Unique MME Identity)
– PLMN Identity is the same as the selected PLMN if excluded
– MMEGI (MME Group Identity) – identities MME group
– MMEC (MME Code) – identifies MME within the group
• Initial NAS message is included

72 © Nokia Siemens Networks

 Attach and
Default Bearer Establishment

73 © Nokia Siemens Networks

Overall Signalling
UE eNode B MME Serving PDN
Gateway Gateway

RRC Connection Setup Complete /

Attach Request /
PDN Connectivity Request
Initial UE Message /
Attach Request /
PDN Connectivity Request
Create Session Request
Create Session Request

Initial Context Setup Request / Create Session Response

Attach Accept /
RRC Connection Reconfiguration / Create Session Response
Activate Default EPS Bearer
Attach Accept / Context Request
Activate Default EPS Bearer
Context Request

RRC Connection
Reconfiguration Complete

Initial Context Setup Response

Uplink Information Transfer /
Attach Complete /
Activate Default EPS Bearer Uplink NAS Transport /
Context Accept Attach Complete /
Activate Default EPS Bearer
Context Accept

Modify Bearer Request

Modify Bearer Response

74 © Nokia Siemens Networks
Signalling from UE Log File
• RRC and NAS signalling visible within the UE log file
• Takes < 1 second to attach and have the default bearer allocated

75 © Nokia Siemens Networks

Attach Request / PDN Connectivity Request
Example

76 © Nokia Siemens Networks

Security Mode Procedure
• The Security Mode Procedure instructs the UE to apply specific ciphering and
integrity protection algorithms

Security Mode
Command

Security Mode
Complete

77 © Nokia Siemens Networks

UE Capability Enquiry
• The eNode B can request UE capability information for each RAT
• Example below requests only LTE capability information

From UE
log file

From
3GPP TS
36.331

78 © Nokia Siemens Networks

UE Capability Information

79 © Nokia Siemens Networks

RRC Connection Reconfiguration (I)
• Provides the UE with measurement control information
• Also includes the Attach Accept and Activate Default EPS Bearer Context
Request messages

80 © Nokia Siemens Networks

RRC Connection Reconfiguration (II)

81 © Nokia Siemens Networks

RRC Connection
Reconfiguration (III)

Activate Default EPS

Attach Accept Bearer Context
Request

82 © Nokia Siemens Networks

RRC Connection Reconfiguration Complete
• RRC Connection Reconfiguration Complete message is a simple
acknowledgement

83 © Nokia Siemens Networks

Uplink Information Transfer
• Procedure is completed from the UE perspective by sending an Uplink
Information Transfer message

84 © Nokia Siemens Networks

 Dedicated Bearer Establishment

85 © Nokia Siemens Networks

Dedicated Bearer Establishment
UE eNB MME P-GW

Attach and Default Bearer Activation

Triggering of
Dedicated Bearer triggering of
activation Dedicated
RRC: UL NAS INFO TRANSFER + ESM BEARER
Bearer activation
RESOURCE ALLOCATION REQUEST
S1AP: UL NAS TRANSPORT (ESM BEARER
RESOURCE ALLOCATION REQUEST) GTPv2: Bearer
optional procedure, P-GW may also trigger dedicated bearer creation without UE requesting it Resource Command

Create Bearer

S1AP: E-RAB SETUP + ESM ACTIVATE

DEDICATED BEARER REQUEST
RRC: RRCConnectionReconfiguration + ESM
DRB ACTIVATE DEDICATED BEARER REQUEST
Configuration

RRC: RRCConnectionReconfigurationComplete

RRC: UL NAS INFO TRANSFER + ESM ACTIVATE

DEDICATED BEARER REQUEST ACCEPT

S1AP: UL NAS TRANSPORT (ESM ACTIVATE

DEDICATED BEARER REQUEST ACCEPT)

86 © Nokia Siemens Networks

UL ESM Bearer Resource Allocation Request
NAS EPS session management messages: Bearer resource allocation request (0xd4)
0000 .... = Spare half octet: 0
.... 0101 = Linked EPS bearer identity: EPS bearer identity value 5 (5)
Traffic Flow Template - Traffic flow aggregate Request to create a
Length: 13
new Traffic Flow
001. .... = TFT operation code: Create new TFT (1)
Template (Dedicated
...0 .... = E bit: Parameters list is not included
.... 0001 = Number of packet filters: 1
Bearer)
Packet filter 0
0011 .... = Packet filter direction: Bidirectional (3)
.... 0000 = Packet filter identifier: 0
Packet evaluation precedence: 0x00 (0)
Packet filter length: 0x09 (9)
Packet filter component type identifier: (16) IPv4 remote address type
IPv4 adress: 10.102.50.0 (10.102.50.0)
IPv4 address mask: 255.255.255.0 (255.255.255.0)
EPS quality of service - Required traffic flow QoS
Length: 9
Quality of Service Class Identifier (QCI): QCI 6 (6)
UE->NW Subscribed maximum bit rate for uplink/ NW->UE Reserved
UE->NW Subscribed maximum bit rate for downlink/ NW->UE Reserved Packet Filter for the
Guaranteed bit rate for uplink : 0 kbps TFT, requested by
Guaranteed bit rate for downlink : 0 kbps
UE
Use the value indicated by the maximum bit rate for uplink in octet 4.
Use the value indicated by the maximum bit rate for downlink in octet 5.
Use the value indicated by the Guaranteed bit rate for uplink in octet 6.
Use the value indicated by the Guaranteed bit rate for downlink in octet 7.

87 © Nokia Siemens Networks

DL S1AP E-RAB SETUP (piggybagged ESM
Activate dedicated EPS bearer context request)
E-RABToBeSetupItemBearerSUReq
e-RAB-ID: 6
e-RABlevelQoSParameters
qCI: 6
S-GW GTP-U Tunnel
allocationRetentionPriority
priorityLevel: no-priority (15)
Endpoint ID + S-GW IP@
pre-emptionCapability: may-trigger-pre-emption (1)
for this S1-U bearer
pre-emptionVulnerability: pre-emptable (1)
transportLayerAddress: 0A66C824 [bit length 32]
transportLayerAddress(IPv4): 10.102.200.36 (10.102.200.36)
gTP-TEID: 0100001A
nAS-PDU: 2700000000026202C5050506FFFFFFFF0D21300009100A66...
Non-Access-Stratum (NAS)PDU
0010 .... = Security header type: Integrity protected and ciphered (2)
.... 0111 = Protocol discriminator: EPS mobility management messages (7)
Message authentication code: 0x00000000
Ciphered message ~ null de-ciphering only!
Sequence number: 2
0110 .... = EPS bearer identity: 0x06 Piggybagged ESM
.... 0010 = Protocol discriminator: EPS session management messages (2) NAS message from
Procedure transaction identity: 2 MME to UE
[……. CONTINUES…………….]

88 © Nokia Siemens Networks

Activate dedicated EPS bearer context request
NAS EPS session management messages: Activate dedicated EPS bearer context request (0xc5)
0000 .... = Spare half octet: 0
.... 0101 = Linked EPS bearer identity: EPS bearer identity value 5 (5)
EPS quality of service
Length: 5
Quality of Service Class Identifier (QCI): QCI 6 (6)
Maximum bit rate for uplink : 0 kbps
Maximum bit rate for downlink : 0 kbps
Guaranteed bit rate for uplink : 0 kbps
Corresponding
Guaranteed bit rate for downlink : 0 kbps
default bearer id
Traffic Flow Template
Length: 13
001. .... = TFT operation code: Create new TFT (1)
...0 .... = E bit: Parameters list is not included Dedicated bearer
.... 0001 = Number of packet filters: 1 QoS for GBR
Packet filter 0
0011 .... = Packet filter direction: Bidirectional (3)
.... 0000 = Packet filter identifier: 0
Packet evaluation precedence: 0x00 (0) Dedicated bearer
Packet filter length: 0x09 (9) TFT
Packet filter component type identifier: (16) IPv4 remote address type
IPv4 adress: 10.102.50.0 (10.102.50.0)
IPv4 address mask: 255.255.255.0 (255.255.255.0)

89 © Nokia Siemens Networks

RRC Connection Re-establishment

90 © Nokia Siemens Networks

RRC Re-Establishment Procedure
• 3-way handshake used for RRC connection re-establishment
• Allows the re-establishment of SRB1
– SRB2 and Data Radio Bearers are subsequently

UE EUTRAN

RRCConnectionReestablishmentRequest

RRCConnectionReestablishment

RRCConnectionReestablishmentComplete

91 © Nokia Siemens Networks

Radio Link Failure (I)
• Upon receiving N310 consecutive "out-of-sync" indications from the lower
layers while neither T300, T301, T304 nor T311 is running:
– start timer T310
• Upon receiving N311 consecutive "in-sync" indications from the lower layers
while T310 is running:
– stop timer T310
From SIB2
3 criteria for radio link failure
• T310 expiry, or
• Random access problem indication from MAC while
neither T300, T301, T304 nor T311 is running, or
• Indication from RLC that maximum number of
retransmissions has been reached

92 © Nokia Siemens Networks

Radio Link Failure (II)

• Upon detecting Radio Link Failure

– store radio link failure information in the VarRLF-Report
– if AS security has not been activated, perform the actions upon leaving
RRC_CONNECTED with release cause 'other'
– else initiate the connection re-establishment procedure

• T311 is started when initiating the RRC Connection Re-establishment

procedure
• If T311 expires then the UE releases to RRC Idle mode using cause ‘RRC
Connection Failure’

• T311 is stopped if the UE manages to camp on a suitable cell

• T301 is then started and the RRC Connection Reestablishment Request
message is sent

93 © Nokia Siemens Networks

RRC Re-Establishment Request

• Upon detecting Radio Link Failure

– store radio link failure information in the VarRLF-Report
– if AS security has not been activated, perform the actions upon leaving
RRC_CONNECTED with release cause 'other'
– else initiate the connection re-establishment procedure

94 © Nokia Siemens Networks

RRC Re-Establishment procedure, example
• T301 is stopped if the UE receives an RRC Connection Reestablishment
message

• If T301 expires then the UE releases to RRC Idle mode using cause ‘RRC
Connection Failure’

95 © Nokia Siemens Networks

RRC Re-Establishment procedure
• RRC Re-establishment message sets up SRB1 again
RRC SIGNALING MESSAGE
Time: 16:49:06.085
RRCConnectionReestablishment (3GPP TS 36.331 ver 8.7.0 Rel 8)

DL-CCCH-Message
message
c1
rrcConnectionReestablishment
rrc-TransactionIdentifier :2
criticalExtensions
c1
rrcConnectionReestablishment-r8
radioResourceConfigDedicated
SRB1 re-establishment
srb-ToAddModList in RRC Conn Re-
srb-ToAddModList value 1 establishment
srb-Identity :1 message.
mac-MainConfig
explicitValue
ul-SCH-Config
maxHARQ-Tx : n5
periodicBSR-Timer : infinity
retxBSR-Timer : sf2560
ttiBundling : false
drx-Config : release

-----------------KLIP-----------------------

96 © Nokia Siemens Networks

RRC Re-Establishment Complete
• Complete message is a simple acknowledgment

97 © Nokia Siemens Networks

Tracking Area Update

98 © Nokia Siemens Networks

Tracking Area Update Signalling
UE eNode B New Old Serving HSS
MME MME Gateway

RRC Connection Setup Complete /

Tracking Area Update Request Initial UE Message /
Tracking Area Update Request
Context Request

Context Response

Context Acknowledge

Modify Bearer Request

Modify Bearer Response

Update Location Request

Cancel Location

Cancel Location Acknowledge

Update Location Acknowledge

Downlink NAS Transport /
Downlink Information Transfer / Tracking Area Update Accept
Tracking Area Update Accept

Uplink Information Transfer /

Tracking Area Update Complete Uplink NAS Transport /
Tracking Area Update Complete

99 © Nokia Siemens Networks

Tracking Area Update
Request

• TA updating
• combined TA/LA updating
• combined TA/LA updating with IMSI attach
• periodic updating

• The Tracking Area Update procedure

can be triggered by mobility or
periodically
• Periodic Tracking Area Update timer is
T3412
– provided within the Attach Accept
message
• UE can be registered with a list of
Tracking Areas to help reduce the
requirement for updates due to mobility

100 © Nokia Siemens Networks

Tracking Area Update
Accept
• TA updated
• combined TA/LA updated
• TA updated and ISR activated
• combined TA/LA updated and
ISR activated

Periodic update timer can

be changed

List of Tracking Areas with

which the UE is registered

101 © Nokia Siemens Networks

Tracking Area Update Complete

• Complete message is a simple acknowledgment

– message does not include any content

102 © Nokia Siemens Networks

Intra-Frequency Handover

103 © Nokia Siemens Networks

General
• The intra-frequency handover procedure is divided into 3 phases:
– preparation
– execution
– completion

UE Source Target MME Serving

eNode B eNode B Gateway

Handover Preparation

Handover Execution

Handover Completion

104 © Nokia Siemens Networks

Handover Preparation
• Does not involve the core network (assuming target cell is known to
the source eNode B)
• Measurement control information is sent to the UE, prior to the UE
providing a Measurement Report to trigger a handover

UE Source Target MME Serving

eNode B eNode B Gateway

RRC Connection Reconfiguration

RRC Connection Reconfiguration Complete

Measurement Report

Handover Decision

Handover Request

Admission Control

Handover Request Acknowledge /

Handover Command /
RRC Connection Reconfiguration

105 © Nokia Siemens Networks

RRC Connection Reconfiguration
• The RRC
Connection
Reconfiguration
message
provides the UE
with
measurement
control
information
• The UE is
provided with
Measurement
Objects,
Reporting
Configurations
and
Measurement
Identities

106 © Nokia Siemens Networks

Measurement Identities, Reporting Configurations
& Measurement Objects
• The example on the previous slide generates the configuration below
• Only intra-frequency measurements are configured

Intra-Frequency 1 Measurement 1 Reporting

RF Carrier Id 1 Event A3 Configuration 1
Measurement
Object
Measurement 2 Reporting
1 Event A5
Id 2 Configuration 2

1 Measurement 3 Reporting
Event A2 Configuration 3
Id 4

107 © Nokia Siemens Networks

Event A3
• Event A3 is triggered when a neighbour becomes Offset better than the
primary cell

Mn  Ofn  Ocn  Hys  Mp  Ofp  Ocp  Off

Offset

Hysteresis

• The actual Offset = (signalled value / 2) dB

• In this example, the Offset is 6 dB
• Frequency and cell specific offsets can be included within the Measurement
Object

108 © Nokia Siemens Networks

Event A5
• Event A5 is triggered when the primary cell becomes worse than
Threshold1 & a neighbour cell becomes better than Threshold2

Mp  Hys  Thresh1
Mn  Ofn  Ocn  Hys  Thresh 2

Threshold1

Threshold2
Hysteresis

• The actual RSRP threshold = (signalled value – 140) dBm

• In this example
– RSRP threshold1 is -93 dBm
– RSRP threshold2 is -80 dBm
109 © Nokia Siemens Networks
Event A2
• Event A2 is triggered when the serving cell becomes worse than a Threshold

Ms  Hys  Thresh

Threshold
Hysteresis

• The actual RSRP threshold = (signalled value – 140) dBm

• In this example, the RSRP threshold is -139 dBm

110 © Nokia Siemens Networks

Quantity Configuration
• The quantity configuration defines the filter coefficients to apply prior to
evaluation of the reporting events
• The example RRC Connection Reconfiguration message includes:

• The lack of information elements indicates that the default 3GPP values are to
be applied:

111 © Nokia Siemens Networks

Other Configuration
• Other parameters associated with measurement control are shown below

Measurement Gaps are not configured

RSRP threshold used to trigger measurements

(actual value = signalled value -140), i.e. -50 dBm

Criteria used to detect

medium and high mobility
Scaling Factors for Time-To-Trigger
(medium and high mobility)

112 © Nokia Siemens Networks

RRC Connection Reconfiguration Complete
• RRC Connection Reconfiguration Complete message is a simple
acknowledgement
• 3GPP release 10 added flags to indicate the availability of Radio Link Failure
and Logged Measurement information

113 © Nokia Siemens Networks

Measurement Report
• Measurement Report indicates that it was triggered by Measurement Identity 1
• Measurement Identity 1 corresponds to Event A3 (neighbour becomes Offset
better than the primary cell)
• Measurement results are provided for both the serving and neighbouring cells

Reporting quantity is set to RSRP

so RSRQ results are excluded

114 © Nokia Siemens Networks

X2-AP: Handover
Request
• X2 signalling is used to
request the handover
at the target cell
• E-RAB information is
included to allow
admission control to be
completed at the target
cell
• GTP tunnel endpoint is
specified for the data
forwarding in the uplink
direction
• UE History information
is included to keep
track of the UE mobility

115 © Nokia Siemens Networks

X2-AP: Handover Request Acknowledge

• GTP tunnel endpoint is

specified for the data
forwarding in the downlink
direction
• The Target eNode B to
Source eNode B
Transparent Container
includes the RRC E-UTRA
Handover Command
message
• The E-UTRA Handover
Command message
includes the RRC
Connection Reconfiguration
message to be sent to the
UE when providing the
handover instruction

116 © Nokia Siemens Networks

Handover Execution
• The UE is provided with the Handover Command using an RRC Connection
Reconfiguration message
• Handover completes from the UE perspective once it has sent the
acknowledgement on the target cell

UE Source Target MME Serving

eNode B eNode B Gateway

RRC Connection Reconfiguration

SN Status Transfer

Forward User Plane Data

Buffer Packets

Synchronisation

Random Access Procedure

RRC Connection Reconfiguration Complete

117 © Nokia Siemens Networks

RRC Connection Reconfiguration (I)
• Handover Command is issued
within an RRC Connection
Reconfiguration message

PCI

Maximum time for handover to

complete from UE perspective
New C-RNTI

UE is also provided with random

access information to access the
target cell

118 © Nokia Siemens Networks

RRC Connection Reconfiguration (II)
• PRACH preamble index is specified for the non-contention based random
access procedure

119 © Nokia Siemens Networks

Handover SN Status Transfer
• The source eNode B forwards an X2: SN Status Transfer message to the
target eNode B
• Provides the target eNode B with information regarding the PDCP PDU which
have been successfully received

3GPP TS 36.423
120 © Nokia Siemens Networks
RRC Connection Reconfiguration Complete
• RRC Connection Reconfiguration Complete message is a simple
acknowledgement

121 © Nokia Siemens Networks

Handover Completion
• Switches the S1 connection from the source eNode B to the target eNode B
• Releases resources at the source eNode B

UE Source Target MME Serving

eNode B eNode B Gateway

Uplink and Downlink User Plane Data Uplink User Plane Data

Path Switch Request

Modify Bearer Request

Switch downlink Path

Uplink and Downlink User Plane Data Uplink and Downlink User Plane Data

Modify Bearer Response

Path Switch Request Ack
UE Context Release

122 © Nokia Siemens Networks

Path Switch Request

• The source eNode B forwards an S1: Path Switch Request message to

the MME
• Provides the MME with information regarding the target eNode B

3GPP TS 36.413

123 © Nokia Siemens Networks

Modify Bearer Request / Response
• This example assumes that handover involves a single Serving Gateway,
i.e. the Serving Gateway does not change
• It is also possible to switch between Serving Gateways at this stage

• Assuming the Serving Gateway does not change, the MME forwards a
GTPv2-C Modify Bearer Request message to the Serving Gateway
• The Modify Bearer Request message provides the Serving Gateway with
information regarding the switch of user plane data flow towards the target
eNode B
• This uses the S11 interface between the MME and Serving Gateway

• The Serving Gateway responds with a Modify Bearer Response message

124 © Nokia Siemens Networks

Path Switch Request Acknowledge
• The MME forwards an S1: Path Switch Request Acknowledge message to the
target eNode B

125 © Nokia Siemens Networks

UE Context Release

• The target eNode B forwards an X2: UE Context Release message to the

source eNode B
• Allows the source eNode B to release its resources for the connection

126 © Nokia Siemens Networks

Inter-System Handover

127 © Nokia Siemens Networks

Triggering
• Does not involve the core network (assuming target cell is known to
the source eNode B)
• Measurement control information is sent to the UE, prior to the UE
providing a Measurement Report to trigger a handover

• Event A2 can trigger inter-

UE Source
eNode B frequency handover
measurements, as well as
inter-system handover
RRC Connection Reconfiguration
measurements
RRC Connection Reconfiguration Complete
Measurement control
information
• Handover measurements
can be cancelled if event A1
is subsequently triggered, i.e.
Measurement Report (event A2) Serving cell coverage
becomes weak serving cell coverage
becomes strong
RRC Connection Reconfiguration Measurement control
information (includes 3G
RRC Connection Reconfiguration Complete neighbour cell information)

Measurement Report (event B2) Serving cell coverage

remains weak, while target
cell coverage is strong

128 © Nokia Siemens Networks

Inter-System Measurements
• UE are provided with a
Measurement Gap configuration
• Gap Pattern (GP) identity 0 or 1
can be signalled:
• GP identity 0:
– Measurement Gap Length (MGL) = 6 ms
– Measurement Gap Repetition Period (MGRP) = 40 ms
• GP identity 1:
– Measurement Gap Length (MGL) = 6 ms
– Measurement Gap Repetition Period (MGRP) = 80 ms
• Measurement gaps start at radio frames and subframes defined by:

SFN mod T = FLOOR(gapOffset/10)

subframe = gapOffset mod 10
T = MGRP/10

129 © Nokia Siemens Networks

Handover Preparation and Execution
• Handover command for UE is tunnelled from the target RNC

UE eNode B MME SGSN Node B RNC

S1-AP: Handover Required GTPv2-C: Forward

Relocation Request
RANAP: Relocation Request

NBAP: Radio Link

Setup Request
NBAP: Radio Link
Setup Response
GTPv2: Forward
Relocation RANAP: Relocation Request Acknowledge
Response
S1-AP: Handover Command

Mobility from EUTRA Command

Handover to UTRAN Complete

RANAP: Relocation Complete

130 © Nokia Siemens Networks

Example Signalling

Triggered EventA2

Triggered EventB2

131 © Nokia Siemens Networks

S1-AP: Handover Required

TargetCellId: 6291758 = 60 01 2E (Hex)

=> 60Hex is RNC-id = 96 Dec
=> 01 1E Hex is Cell-id = 302 Dec
132 © Nokia Siemens Networks
CS Fallback

133 © Nokia Siemens Networks

CS Fallback – Joint Attach
• The UE must be attached to both the PS (LTE) and CS (UMTS or GSM) core
network domains
– uses a joint attach procedure
• Signalling for the combined ‘EPS/IMSI’ Attach procedure is shown below
• The NAS Attach Request message informs the MME that the UE would like to
complete a combined procedure

MSC/
UE MME VLR HSS
SGs Interface

Attach Request

Derive VLR number

Location Update Request

Create SGs association

Location Update in CS domain

Location Update Accept

Attach Accept

Attach Complete

134 © Nokia Siemens Networks

CS Fallback – Attach Request
Attach Request

Set to “combined EPS/IMSI attach”

Set the “EMM Combined

procedures capability” flag

135 © Nokia Siemens Networks

CS Fallback - Scenarios
• There are multiple scenarios for the CS Fallback procedure:
– mobile originated or mobile terminated
– starting from Idle mode or Connected mode
– using an inter-system handover or a redirection instruction
• These possibilities result in a total of 8 different scenarios
• The inter-system handover possibility is applicable to the idle mode scenario
as well as the connected mode scenario because UE in Idle mode are moved
into connected mode prior to redirection

136 © Nokia Siemens Networks

CS Fallback
eNode B MSC/
UE MME VLR
SGs Interface RNC

Paging Request
Paging
Paging

RRC Connection Request

RRC Connection Setup

RRC Connection Setup Complete /

Extended Service Request
Extended Service Request
Service Request
Initial Context Setup Request

Initial Context Setup Response

RRC Connection Release
UE Context Release Request

UE Context Release Command

UE Context Release Complete

RRC Connection Request

RRC Connection Setup

RRC Connection Setup Complete

Initial Direct Transfer / Paging Response

Paging Response
137 © Nokia Siemens Networks
RRC Connection Release
• For intra and inter-frequency measurements a measurement object is a
single LTE RF carrier
• Cell ssaas

138 © Nokia Siemens Networks

SRVCC

139 © Nokia Siemens Networks

SRVCC – network Architecture
• General architecture for SRVCC is shown below

Core Network

IP Multimedia
MSC
Subsystem (IMS)

Sv
MME SGSN
S-GW / S11
P-GW
S3

S1-U S1-MME Iu-ps Iu-cs

RNC
UE Iub

eNode B Node B

E-UTRAN UTRAN

140 © Nokia Siemens Networks

SRVCC Signalling (I)
Source Target
eNode B Source MSC Target Target RNS
MME Server / MSC SGSN IMS
MGW
UE

Meas. Reports

Handover Decision
HO Required

Bearer Splitting

PS to CS Request
Prepare HO
Relocation Request
Forward Relocation Request
Relocation Request

Relocation Request Ack

Forward Relocation Response

Relocation Request Ack

Prep. HO Resp

Est. Circuit

Initialisation of Session Transfer

PS to CS Response
Mobility from Session Transfer &
HO Command
EUTRA Update Remote Leg
Command
Release of IMS
Access Leg
141 © Nokia Siemens Networks
SRVCC Signalling (II)

Source Target
eNode B Source MSC Target Target S-GW / RNS
MME Server / MSC SGSN P-GW
MGW
UE

UE tunes to UTRAN Relocation Detect

Relocation Detect
Handover to UTRAN Complete

Relocation Complete
HO Complete
Answer
PS to CS Complete
Notification

PS to CS Complete
Ack
Delete Bearer

Relocation Complete
Forward Relocation Complete

Forward Relocation Complete Ack

Update Bearer
Release
Resources Delete Session

142 © Nokia Siemens Networks

End of Day 6

143 © Nokia Siemens Networks