LNBTS Message Sequence Charts With PM Counters0 4

1 (96) LTE PMO LTE MSC with PM Counters
Dr. Martin Kollar Company Confidential
20th September 2012
LTE Message Sequence Charts with PM

Counters for RL40/35TD
Company Confidential
Version Date Author Approved by Comments
4.0.0 20.09.2012 Dr. Martin Kollar Bernhard Friedrich

20th September 2012
Table of Contents
History ....................................................................................................................................................... 7
1. Scope of the Document ........................................................................................................................ 9
1.1 Introduction .................................................................................................................................. 9
1.2 Message Sequence Charts ............................................................................................................ 9
2. UE State Handling Procedures ........................................................................................................ 10
2.1 Paging Procedure .......................................................................................................................... 10
2.2 Random Access Procedure...................................................................................................... 11
2.2.1 Contention Based Random Access Procedure ........................................................................... 11
2.2.2 Contention Free Random Access Procedure ............................................................................. 12
2.2.2.1 Contention Free Random Access Procedure for PDCCH Order .......................................... 12
2.2.2.2 Contention Free Random Access Procedure for intra eNB Handover ................................ 13
2.2.2.3 Contention Free Random Access Procedure for inter eNB Handover ................................ 13
2.2.2.4 Unsuccessful Contention Free Random Access Procedure Due to Lack of Preamble
Resources ........................................................................................................................................ 14
2.3 RRC Connection Establishment ............................................................................................... 15
2.3.1 Successful RRC Connection Establishment ................................................................................ 15
2.3.2 Unsuccessful RRC Connection Establishment ( RRC CONNECTION COMPLETE Missing) .......... 16
2.3.3 Unsuccessful RRC Connection Establishment (Completions Error in RRC CONNECTION
COMPLETE).......................................................................................................................................... 17
2.3.4 Unsuccessful RRC Connection Establishment (Rejection by RRM RAC - Lack of Resources) ..... 18
2.4 Transaction to ECM-Idle (Signalling Connection Release) ...................................................... 19
2.4.1 Normal procedure ...................................................................................................................... 19
2.4.1.1 MME initiated Transaction to ECM-Idle state..................................................................... 19
2.4.1.2 eNB initiated Transition to ECM-IDLE ................................................................................ 20
2.4.2 Abnormal procedure .................................................................................................................. 21
2.4.2.1 MME initiated Transaction to ECM-Idle state..................................................................... 21
20th September 2012
2.4.2.2 eNB initiated Transaction to ECM-IDLE............................................................................... 22

2.4.2.3 Transaction to ECM-Idle State Due to Reset on S1 ............................................................. 23
2.5 RRC Connection Re-establishment ......................................................................................... 25
2.5.1 RRC Connection Re-establishment (Successful procedure) ................................................ 25
2.5.2 RRC Connection Re-establishment (Unsuccessful procedure)................................................. 26
3. Bearer Management Procedures .................................................................................................... 28
3.1 E-RAB Bearer Establishment ................................................................................................... 28
3.1.1 Successful Initial E-RAB Establishment via Initial Context Setup ........................................ 28
3.1.2 Unsuccessful Initial E-RAB Establishment via Initial Context Setup.................................... 29
3.1.3 Additional E-RAB Establishment (Successful Procedure) .................................................... 30
3.1.4 Additional E-RAB Establishment (Unsuccessful Procedure) ............................................... 31
3.2 Data Radio Bearer (DRB) Establishment ................................................................................. 33
3.2.1 Successful Procedure (DRB establishment done in parallel with E-RAB establishment or
intra eNB handover)............................................................................................................................ 33
3.2.2 Successful Procedure (DRB establishment done during X2 based inter eNB handover).... 35
3.2.3 Successful Procedure (DRB establishment done during S1 based inter eNB handover) .... 36
3.2.4 Unsuccessful Procedure (DRB establishment done in parallel with E-RAB establishment or
intra eNB handover)............................................................................................................................ 37
3.2.5 Unsuccessful Procedure (DRB establishment done during X2 based inter eNB handover) 38
3.2.6 Unsuccessful Procedure (DRB establishment done during S1 based inter eNB handover) 39
3.3 E-RAB Release ......................................................................................................................... 41
3.3.1 Normal E-RAB Release Initiated by eNB (UE stays in ECM-CONNECTED state) .................. 41
3.3.2 Abnormal E-RAB Release Initiated by eNB (UE stays in ECM-CONNECTED state) .............. 42
3.3.3 Normal E-RAB Release Initiated by MME (UE stays in ECM-CONNECTED state)................ 43
3.3.4 Abnormal E-RAB Release Initiated by MME (UE stays in ECM-CONNECTED state) ............ 44
3.3.5 Normal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state) ............................ 45
3.3.6 Abnormal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state) ........................ 46
20th September 2012
3.3.7 Normal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state) .......................... 47
3.3.8 Abnormal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state) ...................... 48
3.4 DRB Release ........................................................................................................................... 49
3.4.1 Normal DRB Release ........................................................................................................... 49
3.4.2 Abnormal DRB Release ....................................................................................................... 50
3.5 UE Context Modification ......................................................................................................... 51
3.5.1 S1AP UE Context Modification (Successful procedure) ...................................................... 51
3.5.2 S1AP UE Context Modification (Unsuccessful procedure) .................................................. 51
4. S1AP Related Procedures ................................................................................................................ 52
4.1 Initial Context Setup................................................................................................................ 52
4.1.1 Successful Procedure .......................................................................................................... 52
4.1.2 Unsuccessful Procedure ...................................................................................................... 53
4.2 S1 Setup .................................................................................................................................. 54
4.2.2 Unsuccessful Procedure (No response) .............................................................................. 54
4.2.3 Unsuccessful Procedure (MME Failure) .............................................................................. 55
4.3 S1 Reset ................................................................................................................................... 55
4.3.1 S1 Partial Reset Initiated by eNB (Successful Procedure) ................................................... 55
4.3.2 S1 Partial Reset Initiated by eNB (Unsuccessful Procedure) .............................................. 56
4.3.3 S1 Partial Reset Initiated by MME (Successful Procedure) ................................................. 57
4.3.4 S1 Partial Reset Initiated by MME (Unsuccessful Procedure) ............................................ 58
4.4 S1 UE Associated Logical S1 Connection Establishment ......................................................... 59
4.5 Additional E-RAB Setup ........................................................................................................... 60
4.5.2 Unsuccessful Procedure ...................................................................................................... 61
5. Mobility ........................................................................................................................................... 62
5.1 eNACC to GSM ........................................................................................................................ 62
20th September 2012
5.2 CS Fallback to UTRAN or GSM via Redirect (UE in Connected Mode) .................................... 63
5.3 CS Fallback to UTRAN or GSM via Redirect (UE in Idle Mode) ................................................ 64
5.4 Intra eNB Handover ................................................................................................................ 66
5.4.2 Unsuccessful Procedure (HO Preparation failure) .............................................................. 67
5.4.3 Unsuccessful Procedure (HO Execution failure) ................................................................. 68
5.5 Inter eNB X2 Based Handover ................................................................................................. 69
5.5.2 Unsuccessful Procedure (HO Preparation Failure -Time cause) ......................................... 70
5.5.3 Unsuccessful Procedure (HO Preparation Failure –AC or OTHER cause) ........................... 71
5.5.4 Unsuccessful Procedure (HO Execution or Completion Failure)......................................... 72
5.6 Inter eNB S1 Based Handover ................................................................................................. 74
5.6.2 Unsuccessful Procedure (HO Preparation Failure -Time cause) ......................................... 75
5.6.3 Unsuccessful Procedure (HO Preparation Failure - Resource or OTHER cause) ................. 76
5.6.4 Unsuccessful Procedure (HO Execution or Completion Failure)......................................... 77
5.7 Inter RAT Handover................................................................................................................. 79
5.7.1 Handover from LTE to UTRAN ............................................................................................. 79
5.7.1.1 Successful Procedure ...................................................................................................... 79
5.7.1.2 Unsuccessful Procedure (Handover Preparation Failure – Time cause) ......................... 80
5.7.1.3 Unsuccessful Procedure (Handover Preparation Failure – AC or OTHER cause) ............ 81
5.7.1.4 Unsuccessful Procedure (Handover Execution or Completion Failure) .......................... 82
5.7.2 Handover from LTE to GERAN ............................................................................................. 84
5.7.2.1 Successful Procedure ...................................................................................................... 84
5.7.2.2 Unsuccessful Procedure (Handover Execution or Completion Failure) .......................... 85
5.8 Mobility Robustness Optimization Features ........................................................................... 86
5.8.1 Late handover ..................................................................................................................... 86
20th September 2012
5.8.2 Early Type 1 handover......................................................................................................... 87

5.8.3 Early Type 2 handover......................................................................................................... 88
6. X2AP Related Procedures ............................................................................................................... 90
6.1 Successful Procedure .............................................................................................................. 90
6.2 Unsuccessful Procedure .......................................................................................................... 90
7. References ...................................................................................................................................... 91
8. Appendix ......................................................................................................................................... 92
8.1 List of E-UTRAN PM Counters ................................................................................................. 92
20th September 2012
History
Version Date Author Reason for update
1.0.0 17.04.2012 M. Kollar First version for review
2.0.0 12.05.2012 M. Kollar Second version – a note related to PM

counters triggering during HO decision
phase added for intra eNB HO (chapter 5.4)
3.0.0 19.07.2012 M. Kollar In the title of the chapter 3.1.1, 3.1.2 and
common notes to chapter 3.1 and 3.2 the
“default” replaced with “initial” due to fact
that with introduction of the LTE 7
(Support of multiple EPS bearers) feature it
is possible to establish via Initial Context
setup message not only non-GBR but also
GBR E-RABs.
A common note related to Path Switch

Failure Request added to chapter 5.5.
A note related E-RAB setup counting added

to chapter 5.3.
Chapter 2.3.1, typo correction:

DSIGN_CONN_ => SIGN_CONN_...
Chapter 5.7.1.1 and 5.7.2.1: correction

from RRC:MOBILITY FROM EUTRAN to
RRC:MOBILITY FROM EUTRAN COMMAND
4.0.0 20.09.2012 M. Kollar

Chapter 2.4.1.2, a note and counter
PRE_EMPT_UE_CONTEXT_NON_GBR
added into the message flow according to
PR 36392ESPE05.
20th September 2012
Chapter 3.3.1, a note related to counters

PRE_EMPT_NON_GBR_BEARER and
PRE_EMPT_NON_GBR_BEARER added
according to PR 36392ESPE05..
Chapter 3.3.5, a note related to counters

PRE_EMPT_NON_GBR_BEARER and
PRE_EMPT_NON_GBR_BEARER added
according to PR 36392ESPE05..
Chapter 4.5 dealing with E-RAB Setup

added.
Chapter 2.4.1.2 a note added to counter

ENB_INIT_TO_IDLE_NORM_REL.
Chapters 5.2, 5.3: counter

ENB_INIT_TO_IDLE_NORM_REL added to
message flow.
20th September 2012
1. Scope of the Document
1.1 Introduction
This manual is a collection of messages of call/session and signaling transactions exchanged between the
UE, eNB and EPC on the Uu, X2 and S1 interfaces which trigger the related performance measurement
(PM) counters, implemented on the C –plane of eNB, during the execution of specific call/session
processing. The data payload related PM counters implemented on the U – plane of eNB that are not
triggered with any external messages but internally within the eNB are not part of this manual.
The PM counters are embedded into the message charts in such a way that the association of one or more
counters to their triggering events becomes clear.
As a general rule, the appearance of a counter within a message chart means that its value is increased
by “1”. Eventual deviations from this rule are explicitly mentioned in the message charts.
This manual does not aim to explain the principle of the features the message sequence charts are related
to. In order to understand the features the reader is instructed to refer to the documents and
specifications listed in the chapter 7.
1.2 Message Sequence Charts
The following chapters contain the message sequence charts related to the most common call/session
processing procedures exchanged between the UE, the eNB and the EPC Network (represented by the
MME, P-GW and S-GW nodes).
The message charts are presented in graphic form. The direction (Uplink, Downlink) of each message is
represented with dotted arrows. In case a message triggers the counters of the related performance
measurements, the PM counter is reported in the graphic (a panel with green background) near the
message. For each message the logical channel via which it is transmitted is also reported. If the channel
mapping on logical (RLC) level cannot be done then the mapping on lower either MAC or physical level is
reported. In addition some important UE states are graphically reported within the panel with blue
background as well.
20th September 2012
2. UE State Handling Procedures

2.1 Paging Procedure
UE eNB MME
S1AP: PAGING
(to each eNB that serves one of the UE’s TAs)
RRC: PAGING
PCCH
RRC_PAGING_MESSAGES*
RRC_PAGING_REQUESTS**
DISC_RRC_PAGING***
* Updated on the transmission of a RRC Paging message
** Updated for each paging record of a RRC Paging message
*** Updated if a paging record cannot be transmitted at the next paging occasion related to the original (S1)
paging request message. This happens if the maximum number of paging records per paging occasion (=16) is
already reached.
20th September 2012
2.2 Random Access Procedure
2.2.1 Contention Based Random Access Procedure
UE eNB
RANDOM ACCESS PREAMBLE

RACH
RACH_STP_ATT_SMALL_MSG
RACH_STP_ATT_LARGE_MSG
RANDOM ACCESS RESPONSE

CCCH
RACH_STP_COMPLETIONS
20th September 2012
2.2.2 Contention Free Random Access Procedure
2.2.2.1 Contention Free Random Access Procedure for PDCCH Order
UE eNB
PDCCH ORDER
PDCCH
PDCCH_INIT_ORDER_ATT*
PDCCH_ORDER_ATT**

RACH
RACH_STP_ATT_DEDICATED
DCCH
PDCCH_ORDER_SUCCESS
* The counter is updated only for the first (initial) PDCCH order transmitted to UE
** This counter is also updated with PDCCH order transmission repetitions.

20th September 2012
2.2.2.2 Contention Free Random Access Procedure for intra eNB Handover
UE eNB
RANDOM ACCESS ASSIGNMENT*
DCCH – Old cell

RACH – new cell
CCCH – new cell
* It is represented by sending RRC Connection Reconfiguration message with included RA-PreambleIndex
2.2.2.3 Contention Free Random Access Procedure for inter eNB Handover
UE Source eNB Target eNB

RANDOM ACCESS ASSIGNMENT*
DCCH – Old cell

RACH – new cell

CCCH – new cell
* It is represented by sending RRC Connection Reconfiguration message with included RA-PreambleIndex

20th September 2012
2.2.2.4 Unsuccessful Contention Free Random Access Procedure Due to Lack of Preamble
Resources
UE eNB
D_PREAMB_UNAVAIL*
D_PREAMB_PDCCH_UNAVAIL
D_PREAMB_HO_UNAVAIL
NO RANDOM ACCESS ASSIGNMENT SENT
* This counter is updated irrespectively of the purpose of dedicated preamble
Common notes to chapter 2.2
1. The counter RACH_STP_COMPLETIONS is triggered both for contention based and free random access
procedures.
2. The counter RACH_STP_ATT_DEDICATED is triggered for all kinds of contention free random access
procedure
20th September 2012
2.3 RRC Connection Establishment
2.3.1 Successful RRC Connection Establishment
UE eNB
Successful Random Access Procedure
RRC CONNECTION REQUEST

CCCH
SIGN_CONN_ESTAB_ATT_MO_S*
SIGN_CONN_ESTAB_ATT_MT*
SIGN_CONN_ESTAB_ATT_MO_D*
SIGN_CONN_ESTAB_ATT_OTHERS *
SIGN_CONN_ESTAB_ATT_EMG*
RRC CONNECTION SETUP Start an O&M Timer

CCCH
RRC CONNECTION SETUP COMPLETE Stop an O&M Timer

DCCH (NAS PDU )
UE in
SIGN_CONN_ESTAB_COMP
RRC-CONNECTED
SIGN_CONN_ESTAB_COMP_EMG**
RRC_CONN_UE_AVG*** (start)
RRC_CONN_UE_MAX
* The counters are triggered depending on the cause within the RRC CONNECTION REQUEST message
** Successful RRC connection establishments are also counted within the SIGN_CONN_ESTAB_COMP
20th September 2012
***The counter is not directly incremented with the RRC CONNECTION REQUEST message but some other
algorithms are used to provide the averaged number of UEs in RRC connected state.
2.3.2 Unsuccessful RRC Connection Establishment ( RRC CONNECTION COMPLETE Missing)
UE eNB

CCCH
SIGN_CONN_ESTAB_ATT_MO_S
SIGN_CONN_ESTAB_ATT_MT
DSIGN_CONN_ESTAB_ATT_MO_D
SIGN_CONN_ESTAB_ATT_OTHERS
SIGN_CONN_ESTAB_ATT_EMG

CCCH
RRC CONNECTION SETUP COMPLETE

DCCH (never reaches eNB)
Expiry O&M Timer
SIGN_EST_F_RRCCOMPL_MISSING
20th September 2012
2.3.3 Unsuccessful RRC Connection Establishment (Completions Error in RRC CONNECTION

COMPLETE)
UE eNB

CCCH

CCCH
RRC CONNECTION SETUP COMPLETE Stop an O&M Timer

DCCH (Erroneous or incomplete)
SIGN_EST_F_RRCCOMPL_ERROR
20th September 2012
2.3.4 Unsuccessful RRC Connection Establishment (Rejection by RRM RAC - Lack of

Resources)
UE eNB

CCCH
RRC CONNECTION REJECT**

CCCH
SIGN_CONN_ESTAB_FAIL_RRMRAC
SIGN_CONN_ESTAB_FAIL_RB_EMG*
*Unsuccessful RRC connection establishments for emergency calls due to lack of radio resources are also counted
within the SIGN_CONN_ESTAB_FAIL_RRMRAC
**The RRC CONNECTION REJECT may contain a wait time to instruct UE to wait with the next RRC CONNECTION
REQUEST
20th September 2012
2.4 Transaction to ECM-Idle (Signalling Connection Release)
2.4.1 Normal procedure
2.4.1.1 MME initiated Transaction to ECM-Idle state
UE eNB MME S-GW
UE in Trigger to initiate
RRC-CONNECTED release
:
S1AP: UE Context Release
Command
EPC_INIT_TO_IDLE_UE_NORM_REL S11 interaction to release the

UE and its bearer
EPC_INIT_TO_IDLE_DETACH
RRC: RRC Connection Release
DCCH
CELL_LOAD_ACT_UE_AVG (stop)
CELL_LOAD_ACT_UE_MAX
L2 ACK Complete
Set UE to
Set UE to Release all UE ECM-IDLE
RRC-IDLE related resources,
remove UE context
RRC_CONN_UE_AVG(stop)
RRC_CONN_UE_MAX
20th September 2012
2.4.1.2 eNB initiated Transition to ECM-IDLE
UE eNB MME S-GW
UE in
RRC-CONNECTED
S1AP: UE Context Release Request
ENB_INIT_TO_IDLE_NORM_REL*
PRE_EMPT_UE_CONTEXT_NON_GBR**
S11 interaction to inform
S1AP: UE Context Release Command S-GW
RRC: RRC Connection Release about connection release
DCCH
CELL_LOAD_ACT_UE_AVG(stop)
S1AP: UE Context Release Complete
L2 ACK
Release all UE related Set UE to
Set UE to
resources, ECM-IDLE
RRC-IDLE
remove UE context
RRC_CONN_UE_MAX
*The counter is also pegged in case of CS Fallback (see also chapters 5.2, 5.3).
**The counter provides the total number of released UE contexts due to “Radio resources not available”
despite a pre-emption used in the counter name.
20th September 2012
2.4.2 Abnormal procedure
2.4.2.1 MME initiated Transaction to ECM-Idle state
UE eNB MME S-GW
UE in Trigger to initiate
RRC-CONNECTED release
S1AP: UE Context Release :
Command
EPC_INIT_TO_IDLE_RNL
S11 interaction to release the UE
EPC_INIT_TO_IDLE_OTHER and its bearer

DCCH
Complete
L2 ACK
Set UE to
Set UE to Release all UE ECM-IDLE
RRC-IDLE related resources,
remove UE context
RRC_CONN_UE_MAX
20th September 2012
2.4.2.2 eNB initiated Transaction to ECM-IDLE
UE eNB MME S-GW
UE in S1AP: UE Context Release Request

RRC-CONNECTED
ENB_INIT_TO_IDLE_RNL
ENB_INIT_TO_IDLE_OTHER
S1AP: UE Context Release Command
S11 interaction to inform S-GW
RRC: RRC Connection Release about connection release
DCCH
L2 ACK
Set UE to Set UE to
Release all UE related ECM-IDLE
RRC-IDLE resources,
remove UE context
RRC_CONN_UE_MAX
20th September 2012
2.4.2.3 Transaction to ECM-Idle State Due to Reset on S1
UE eNB MME S-GW
UE in S1 Reset,
RRC-CONNECTED S11 interaction to inform S-GW
about connection release
ACT_UE_CONT_REL_INIT_ENB
Set UE to
ACT_UE_CONT_REL_INIT_MME ECM-IDLE

DCCH
L2 ACK
Release all UE related
Set UE to resources,
RRC-IDLE remove UE context
RRC_CONN_UE_MAX
1. The counter RRC_CONN_UE_AVG is not directly decremented with the receiving the L2 ACK message as
an answer to RRC Connection release but some other algorithm are used to provide the averaged number
of UEs in RRC connected state.
2. The counters CELL_LOAD_ACT_UE_MAX and CELL_LOAD_ACT_UE_AVG are only triggered if there was at
least one DRB configured for the UE. In parallel to these counters also those ones included in the
following table may be triggered. In addition to CELL_LOAD_ACT_UE_MAX, CELL_LOAD_ACT_UE_AVG the
counters are triggered with a rule that there must be some data in any buffer (for more info see [2,3]).
Averaged value Maximum value

DL direction DL_UE_DATA_BUFF_AVG DL_UE_DATA_BUFF_MAX
UE_DRB_DL_DATA_QCI_1
20th September 2012
UE_DRB_DL_DATA_NON_GBR
UL_UE_DATA_BUFF_AVG UL_UE_DATA_BUFF_MAX
UL direction UE_DRB_UL_DATA_QCI_1
UE_DRB_UL_DATA_NON_GBR
3. The counter CELL_LOAD_ACT_UE_AVG is not directly decremented with sending the RRC Connection
release to UE but some other algorithm are used to provide the averaged number of Active UEs (for more
info see [2,3]).
4. Along with CELL_LOAD_ACT_UE_AVG also the ENB_LOAD_ACT_UE_AVG is triggered but instead per cell
provides the results on a per eNB basis.
5. Regarding the reason why UE is supposed to move to ECM-IDLE state the reader is instructed to see also
the chapters 3.3.5 – 3.3.8.
20th September 2012
2.5 RRC Connection Re-establishment
2.5.1 RRC Connection Re-establishment (Successful procedure)
UE Serving/Source/Target eNB
Reestablishment
Trigger
Contention-based Random Access

( UE receives new C
-RNTI)
RRC: RRCConnectionReestablishmentReque
st
CCCH
RRC_CON_RE_ESTAB_ATT*
RRC_CON_RE_ESTAB_ATT_HO_FAIL**
RRC_CON_RE_ESTAB_ATT_OTHER**
Reestablishment accepted
SRBs and DRBs suspended
RRC: RRCConnectionReestablishment
CCCH
Activate Security
RRC: RRCConnectionReestablishmentComplete
DCCH
RRC_CON_RE_ESTAB_SUCC*
RRC_CON_RE_ESTAB_SUCC_HO_FAIL**
RRC_CON_RE_ESTAB_SUCC_OTHER**
RRC: RRCConnectionReconfiguration
Reestablish and DCCH

Resume SRB2 and
DRBs
RRC: RRCConnectionReconfigurationComplete
DCCH ResumeSRB2 and
DRBs
Delete resources of
old C-RNTI
20th September 2012
2.5.2 RRC Connection Re-establishment (Unsuccessful procedure)
UE Serving/Source/Target eNB
Reestablishment
Trigger
Contention-based Random Access

( UE receives new C-RNTI)
RRC: RRCConnectionReestablishmentReque
st
CCCH
RRC_CON_RE_ESTAB_ATT*
RRC_CON_RE_ESTAB_ATT_HO_FAIL**
RRC_CON_RE_ESTAB_ATT_OTH**
1. Reestablishment to source or target cell in case of intra or inter eNB

HO is rejected if UE attempts the re-establishment procedure due to
reconfiguration error.
2. Reestablishment to serving cell without handover is rejected if UE
attempts the re-establishment procedure during Initial Context Setup.
3. Reestablishment is rejected if UE attempts the re-establishment
procedure to any other than serving cell in case without handover.
4.
RRC: RRCConnectionReestablishmentReject
CCCH
REJ_RRC_CONN_RE_ESTAB*
1. *The counters are triggered for all the possible causes within the RRC CONNECTION REESTABLISHMENT
REQUEST
20th September 2012
2. **The counters are triggered depending on the cause within the RRC CONNECTION REESTABLISHMENT
REQUEST
3. The message flow charts included in this chapter are simplified ones meaning that the concentration is on
message exchange between UE and eNB during RRC Connection Re-establishment and so especially some
messaging related to handover is excluded.
4. RRC Connection Re-establishment is also used in case of so-called Mobility Robustness Optimization
procedures followed by late, early 1 or 2 HO events which are part of the chapter 5.8.
20th September 2012
3. Bearer Management Procedures

3.1 E-RAB Bearer Establishment
3.1.1 Successful Initial E-RAB Establishment via Initial Context Setup
UE eNB MME
Successful Random Access procedre (see chapter 2.2.1)
Successful RRC Connection Setup Procedure (see chapter 2.3.1)
Optional: NAS Signalling
S1AP: INITIAL CONTEXT SETUP REQUEST
EPS_BEARER_SETUP_ATTEMPTS
EPS_BEARER_STP_ATT_INI_QCI1*
EPS_BEARER_STP_ATT_INI_QCI_2*
EPS_BEAR_STP_ATT_INI_NON_GBR*
Security and DRB Establishment (see chapter 3.2)
S1AP: INITIAL CONTEXT SETUP RESPONSE

E-RAB Setup List
EPS_BEARER_SETUP_COMPLETIONS
EPS_BEARER_STP_COM_INI_QCI1*
EPS_BEARER_STP_COM_INI_QCI_2*
EPS_BEAR_STP_COM_INI_NON_GBR*
* The counters are triggered on a per QCI basis (QCI1-4 and non GBR bearers).
20th September 2012
From the simplicity point of view in the above message flow chart it is considered that the S1AP: Initial Context
Setup Response message only contains E-RAB Setup List and that the E-RAB Failed To Setup List is empty.
3.1.2 Unsuccessful Initial E-RAB Establishment via Initial Context Setup
UE eNB MME
Successful Random Access Procedure (see chapter 2.2.1)
EPS_BEARER_STP_ATT_INI_QCI1
EPS_BEARER_STP_ATT_INI_QCI_2
EPS_BEAR_STP_ATT_INI_NON_GBR
Security Establishment

E-RAB Failed to
Setup List
EPS_BEARER_SETUP_FAIL_RNL*
EPS_BEARER_SETUP_FAIL_TRPORT*
EPS_BEARER_SETUP_FAIL_RESOUR*
EPS_BEARER_SETUP_FAIL_OTH*
* The counters are triggered on a per cause basis which is obtained from E-RAB Failed to Setup List sent within the
S1AP: Initial Context Setup response message.
From the simplicity point of view in the above message flow chart it is considered that the S1AP: Initial Context
Setup Response message only contains E-RAB Failed To Setup List.
20th September 2012
3.1.3 Additional E-RAB Establishment (Successful Procedure)
UE eNB MME
Successful UE Associated Logical S1 Connection and default E-RAB Establishment
S1AP: E-RAB SETUP REQUEST
EPS_BEARER_STP_ATT_ADD_QCI_1*
E_RAB_SETUP_ATT_EMG**
DRB Establishment (see chapter 3.2)
S1AP: E-RAB SETUP RESPONSE
E-RAB Setup List

EPS_BEARER_SETUP_COMPLETIONS
EPS_BEAR_SET_COM_ADDIT_QCI1*
EPS_BEARER_STP_COM_ADD_QCI_2*
E_RAB_SETUP_SUCC_EMG**
* The counters are triggered on a per QCI basis (QCI1-4).
**The counters are triggered for IMS Emergency sessions i.e. in case when the ARP (Allocation and Retention
Priority) priority level which is used for emergency sessions is part of S1AP: E-RAB SETUP REQUEST message.
From the simplicity point of view in the above message flow chart it is considered that the S1AP: E-RAB SETUP
RESPONSE message only contains E-RAB Setup List and that the E-RAB Failed To Setup List is empty.
20th September 2012
3.1.4 Additional E-RAB Establishment (Unsuccessful Procedure)
UE eNB MME
Successful UE Associated Logical S1 Connection and default E-RAB Establishment
EPS_BEARER_STP_ATT_ADD_QCI_1
E_RAB_SETUP_ATT_EMG
E-RAB Failed to
Setup List
EPS_BEARER_SETUP_FAIL_RNL*
EPS_BEARER_SETUP_FAIL_TRPORT*
EPS_BEARER_SETUP_FAIL_RESOUR*
EPS_BEARER_SETUP_FAIL_OTH*
E_RAB_SETUP_FAIL_RB_EMG
*The counters are triggered on a per cause basis which is obtained from E-RAB Failed to Setup List sent within the
S1AP: E-RAB SETUP RESPONSE message.
From the simplicity point of view in the above message flow chart it is considered that the S1AP: E-RAB SETUP
RESPONSE message only contains the E-RAB Failed To Setup List.
20th September 2012
1. The counters EPS_BEARER_SETUP_ATTEMPTS, EPS_BEARER_SETUP_COMPLETIONS,

EPS_BEARER_SETUP_FAIL_RNL , EPS_BEARER_SETUP_FAIL_TRPORT , EPS_BEARER_SETUP_FAIL_RESOUR
and EPS_BEARER_SETUP_FAIL_OTH are triggered both for initial and additional E-RAB establishment.
20th September 2012
3.2 Data Radio Bearer (DRB) Establishment
3.2.1 Successful Procedure (DRB establishment done in parallel with E-RAB

establishment or intra eNB handover)
UE eNB MME
Start RRC Guide Timer

DCCH
Contention Free Random Access ProcedureIn case of intra
eNB Handover (see chapter 2.2.2.1)
Default or Additional EPS

Bearer Establishment
DATA_RB_STP_ATT
Security Establishment in case of

Default EPS Bearer Establishment
Stop RRC Guide Timer
DCCH
DATA_RB_STP_COMP
CELL_LOAD_ACT_UE_AVG(start)
RRC_CONN_UE_AVG(start)
RRC_CONN_UE_MAX
Notes:
1. The message flow chart from the perspective of sent RRC Connection Reconfiguration and RRC
Connection Reconfiguration Complete covers also a DRB establishment for an intra eNB handover with
the only exception that there is not any E-RAB establishment in parallel.
20th September 2012
2. The counters CELL_LOAD_ACT_UE_MAX and CELL_LOAD_ACT_UE_AVG are triggered if the DRB

successfully configured is the first one for the related UE. This usually happens when DRB establishment
done in parallel with default E-RAB establishment or intra eNB handover. Regarding the counters see also
“Common notes to chapter 2.4 (point 2)”.
3. The counters RRC_CONN_UE_AVG and RRC_CONN_UE_MAX is triggered in this message flow scenario
only when DRB has successfully been established in case of intra eNB handover when UE is getting to RRC
Connected state from network point of view. Regarding the counter RRC_CONN_UE_AVG see also
“Common notes to chapter 2.4 (point 1)”.
20th September 2012
3.2.2 Successful Procedure (DRB establishment done during X2 based inter

eNB handover)
Source Target
UE
eNB eNB
RRC Connection Reconfiguration

(Measurement Configuration)
Measurement Reports
DCCH
old cell
Handover Request
Start Tx2Relocexec
Handover Request Acknowledge

DATA_RB_STP_ATT
Contention Free
Stop Tx2Relocexec
Random Access Procedure (see chapter 2.2.2.2)
RRC Connection Reconfiguration Complete

DCCH DATA_RB_STP_COMP
new cell
RRC_CONN_UE_MAX
20th September 2012
3.2.3 Successful Procedure (DRB establishment done during S1 based inter

eNB handover)
Source Target MME/

UE
eNB eNB EPC

Measurement Reports
DCCH
old cell
Handover Required
Handover Request
Start TS1Relocexec
Handover Request
Acknowledge
DATA_RB_STP_ATT
Handover Command
Contention Free
Stop TS1Relocexec
DCCH
new cell DATA_RB_STP_COMP
RRC_CONN_UE_MAX
Common notes to chapters 3.2.2 and 3.2.3:
1 It should be noted that the message flow chart is simplified and some synchronization messages used during
the handover are excluded.
20th September 2012
2 The counters CELL_LOAD_ACT_UE_MAX and CELL_LOAD_ACT_UE_AVG are triggered in case of inter eNB
handover as this is always the case that after successful DRB establishment the UE appears in the target cell
for the first time with at least one configured DRB. Regarding the counters see also “Common notes to chapter
2.4 (point 2)”.
3.2.4 Unsuccessful Procedure (DRB establishment done in parallel with E-

RAB establishment or intra eNB handover)
UE eNB MME
Start RRC Guard Timer
DCCH
Contention Free Random Access ProcedureIn case of intra
eNB Handover (see chapter 2.2.2.1)
Default or Additional EPS
Bearer Establishment
DATA_RB_STP_ATT
Security Establishment in case of

Default EPS Bearer Establishment
DCCH
Expiry RRC Guard Timer
DATA_RB_STP_FAIL
Note: The message flow chart from the perspective of sent RRC Connection Reconfiguration and RRC Connection
Reconfiguration Complete covers also a DRB establishment for an intra eNB handover with the only exception that
20th September 2012
there is not any EPS Bearer establishment in parallel and that the THOoverall Timer expiry triggers the
DATA_RB_STP_FAIL (see chapter 5.4.3).
3.2.5 Unsuccessful Procedure (DRB establishment done during X2 based

inter eNB handover)
Source Target
UE
eNB eNB

Measurement Reports
DCCH
old cell
Handover Request
Start Tx2Relocexec
Handover Request Acknowledge

DATA_RB_STP_ATT
Contention Free

DCCH
new cell Expiry Tx2Relocexec
DATA_RB_STP_FAIL
Note: It should be noted that the message flow chart is simplified and some synchronization messages used during
20th September 2012
3.2.6 Unsuccessful Procedure (DRB establishment done during S1 based

inter eNB handover)
Source Target MME/

UE
eNB eNB EPC

Measurement Reports
DCCH
old cell
Handover Required
Handover Request
Start TS1Relocexec
Handover Request
Acknowledge
DATA_RB_STP_ATT
Handover Command
Contention Free

DCCH
new cell Expiry TS1Relocexec
DATA_RB_STP_FAIL
20th September 2012
Note: It should be noted that the message flow chart is simplified and some synchronization messages used during
1. The counters DATA_RB_STP_ATT, DATA_RB_STP_COMP and DATA_RB_STP_FAIL are triggered in all

possible scenarios when DRB can be established (i.e. in parallel to initial or additional EPS Bearer
establishment and intra or inter eNB handover).
20th September 2012
3.3 E-RAB Release
3.3.1 Normal E-RAB Release Initiated by eNB (UE stays in ECM-CONNECTED

state)
UE eNB MME
S1AP: E-RAB RELEASE REQUEST
ENB_EPS_BEARER_REL_REQ_NORM
ENB_EPS_BEAR_REL_REQ_N_QCI1
PRE_EMPT_GBR_BEARER*
PRE_EMPT_NON_GBR_BEARER*
S1AP: E-RAB RELEASE COMMAND
DCCH
DCCH S1AP: E-RAB RELEASE RESPONSE
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
*The counters provide the total number of released GBR and non GBR E-RABs due to “Radio resources
not available” despite a pre-emption used in the counter names, respectively.
20th September 2012
3.3.2 Abnormal E-RAB Release Initiated by eNB (UE stays in ECM-

CONNECTED state)
UE eNB MME
S1AP: E-RAB RELEASE REQUEST
ENB_EPS_BEARER_REL_REQ_RNL
ENB_EPS_BEARER_REL_REQ_TNL
ENB_EPS_BEARER_REL_REQ_OTH
ENB_EPS_BEARER_REL_REQ_R_QCI1
ENB_EPS_BEARER_REL_REQ_T_QCI1
ENB_EPS_BEARER_REL_REQ_O_QCI1

DCCH
DCCH
S1AP: E-RAB RELEASE RESPONSE
20th September 2012
3.3.3 Normal E-RAB Release Initiated by MME (UE stays in ECM-CONNECTED

state)
UE eNB MME
EPC_EPS_BEARER_REL_REQ_NORM
EPC_EPS_BEARER_REL_REQ_N_QCI1
DCCH
DCCH
S1AP: E-RAB RELEASE RESPONSE
20th September 2012
3.3.4 Abnormal E-RAB Release Initiated by MME (UE stays in ECM-

CONNECTED state)
UE eNB MME
EPC_EPS_BEARER_REL_REQ_RNL
EPC_EPS_BEARER_REL_REQ_OTH
EPC_EPS_BEARER_REL_REQ_R_QCI1
EPC_EPS_BEARER_REL_REQ_O_QCI1
DCCH
DCCH S1AP: E-RAB RELEASE RESPONSE
20th September 2012
3.3.5 Normal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state)
UE eNB MME S-GW
UE in S1AP: UE Context Release Request

RRC-CONNECTED
ENB_EPSBEAR_REL_REQ_RNL_REDIR
ENB_EPS_BEARER_REL_REQ_N_QCI1 S11 interaction to inform

S-GW
ENB_EPSBEAR_REL_REQ_RNL_RD_QCI1 about connection release
PRE_EMPT_NON_GBR_BEARER*
PRE_EMPT_GBR_BEARER*

DCCH
L2 ACK See chapters 2.4.1.2 and 3.4.1 to get
an info on other specific counters
Set UE to Release all UE related triggering related to this phase. Set UE to
RRC-IDLE resources, ECM-IDLE
remove UE context
**See also a comment in the chapter 3.3.1

20th September 2012
3.3.6 Abnormal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE

state)
UE eNB MME S-GW
UE in
RRC-CONNECTED S1AP: UE Context Release Request
ENB_EPS_BEARER_REL_REQ_RNL
ENB_EPS_BEARER_REL_REQ_TNL
ENB_EPS_BEARER_REL_REQ_OTH S11 interaction to inform

S-GW
ENB_EPS_BEARER_REL_REQ_R_QCI1 about connection release
ENB_EPS_BEARER_REL_REQ_T_QCI1
ENB_EPS_BEARER_REL_REQ_O_QCI1

DCCH
L2 ACK See chapters 2.4.1.2 and 3.4.2 to get
triggering related to this phase.
Set UE to Release all UE related Set UE to
RRC-IDLE resources, ECM-IDLE
remove UE context
20th September 2012
3.3.7 Normal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state)
UE eNB MME S-GW
UE in Command
RRC-CONNECTED
:
EPC_EPS_BEARER_REL_REQ_NORM
EPC_EPS_BEARER_REL_REQ_DETACH
EPC_EPS_BEARER_REL_REQ_N_QCI1 and its bearer
EPC_EPS_BEARER_REL_REQ_D_QCI1

DCCH
Complete
L2 ACK
See chapters 2.4.1.1 and 3.4.1 to get
Set UE to Release all UE
RRC-IDLE related resources, Set UE to
remove UE context ECM-IDLE
20th September 2012
3.3.8 Abnormal E-RAB Release Initiated by MME (UE moves to ECM-IDLE

state)
UE eNB MME S-GW

UE in
Command
RRC-CONNECTED
:
EPC_EPS_BEARER_REL_REQ_RNL
EPC_EPS_BEARER_REL_REQ_OTH
and its bearer
EPC_EPS_BEARER_REL_REQ_R_QCI1
EPC_EPS_BEARER_REL_REQ_O_QCI1

DCCH
Complete
L2 ACK
See chapters 2.4.1.2 and 3.4.2 to get
Set UE to Release all UE
RRC-IDLE related resources, Set UE to
remove UE context ECM-IDLE
1. All the used counters in this chapter are triggered both for the UE staying in ECM-CONNECTED and
moving to ECM-IDLE state but differentiate between the release procedure initiated by EPC or eNB
excepting PRE_EMPT_GBR_BEARER and PRE_EMPT_NON_GBR_BEARER.
2. For each counter it holds that if the release procedure is executed for more than one E-RAB bearer the
counter is pegged for each released E-RAB bearer.
20th September 2012
3.4 DRB Release
3.4.1 Normal DRB Release
UE eNB MME

or Events or interactions leading
RRC: RRC Connection Reconfiguration* to DRB release via sending the RRC
DCCH Connection Release or RRC Connection
reconfiguration message
RB_REL_REQ_NORM_REL**
(see also chapter 3.3)
RB_REL_REQ_DETACH_PROC
RB_REL_REQ_RNL_REDIR
L2 ACK
*The RRC Connection Reconfiguration triggers the RB_REL_REQ_NORM_REL counter in the scenarios when not all
DRBs established for an UE have to be released, i.e. the UE after the release procedure does not move into the
ECM-IDLE state.
**Besides the normal cause of releasing the DRB via sending the RRC Connection Release message the
RB_REL_REQ_NORM_REL may also by triggered internally after a successful intra LTE or inter RAT handover when
the DRB is being released.
20th September 2012
3.4.2 Abnormal DRB Release
UE eNB MME

or Events or interactions leading
RRC: RRC Connection Reconfiguration* to DRB release via sending the RRC
Connection Release or RRC Connection
DCCH
reconfiguration message
(see also chapter 3.3)

RB_REL_REQ_RNL
RB_REL_REQ_OTHER
L2 ACK
*The RRC Connection Reconfiguration triggers the RB_REL_REQ_OTHER counter in the scenarios when not all DRBs
established for an UE have to be released, i.e. the UE after the release procedure does not move into the ECM-IDLE
state.
1. For each counter used in this chapter it holds that if the release procedure is executed for more than one
DRB the counter is pegged for each released DRB.
20th September 2012
3.5 UE Context Modification
3.5.1 S1AP UE Context Modification (Successful procedure)
eNB MME
S1AP: UE CONTEXT MODIFICATION REQUEST

UE_CONTEXT_MOD_ATT UE-AMBR (opt.),
CS Fallback Indicator (opt.)
UE_CONTEXT_MOD_ATT_AMBR
UE_CONTEXT_MOD_ATT_CSFB
S1AP: UE CONTEXT MODIFICATION RESPONSE
3.5.2 S1AP UE Context Modification (Unsuccessful procedure)
eNB MME
S1AP: UE CONTEXT MODIFICATION REQUEST

UE_CONTEXT_MOD_ATT
UE_CONTEXT_MOD_ATT_AMBR
S1AP: UE CONTEXT MODIFICATION FAILURE
UE_CONTEXT_MOD_FAIL
1. The counters UE_CONTEXT_MOD_ATT, UE_CONTEXT_MOD_FAIL are triggered irrespective of the

modified information.
2. The counters UE_CONTEXT_MOD_ATT_AMBR, UE_CONTEXT_MOD_ATT_CSFB are triggered in
dependence it is AMBR and CSFB modified information, respectively.
20th September 2012
4. S1AP Related Procedures

4.1 Initial Context Setup
4.1.1 Successful Procedure
UE eNB MME
INI_CONT_STP_REQ
Security and DRB Establishment (see chapter 3.2.1)

E-RAB Failed to Setup
List is empty
INI_CONT_STP_COMP
20th September 2012
4.1.2 Unsuccessful Procedure
UE eNB MME
INI_CONT_STP_REQ
Security Establishment

List is not empty
OR
S1AP: INITIAL CONTEXT SETUP FAILURE
INI_CONT_STP_FAIL_RNL*
INI_CONT_STP_FAIL_TRPORT*
INI_CONT_STP_FAIL_RESOUR*
INI_CONT_STP_FAIL_OTHER*
*For each Initial Context Setup counted by INI_CONT_STP_REQ always only one of these counters is triggered in
case of unsuccessful procedure, i.e. when there is either an Initial Context Setup Failure or the E-RAB Failed to
Setup List within an Initial Context Setup Response message is not empty.
20th September 2012
4.2 S1 Setup
eNB MME
Start an O&M Timer
S1AP: S1 SETUP REQUEST
S1_SETUP_ATT
Stop an O&M Timer S1AP: S1 SETUP RESPONSE
S1_SETUP_SUCC
4.2.2 Unsuccessful Procedure (No response)
eNB MME
Start an O&M Timer
S1_SETUP_ATT
Expiry O&M Timer
S1_SETUP_FAIL_NO_RESP
20th September 2012
4.2.3 Unsuccessful Procedure (MME Failure)
eNB MME
Start an O&M Timer
S1_SETUP_ATT
Stop an O&M Timer S1AP: S1 SETUP FAILURE
S1_SETUP_FAIL_IND_BY_MME
4.3 S1 Reset
4.3.1 S1 Partial Reset Initiated by eNB (Successful Procedure)
eNB MME
Start TimerS1ResetWaitForResponse
S1AP: S1 RESET*
S1AP_PARTIAL_RESET_INIT_ENB
S1AP: S1 RESET ACKNOWLEDGE
Stop TimerS1ResetWaitForResponse
*The intention “partial” means that with the S1 reset procedure the UE contexts included in the “UE-
associated logical S1-connection list” within the message are released.
20th September 2012
4.3.2 S1 Partial Reset Initiated by eNB (Unsuccessful Procedure)
eNB MME
Start TimerS1ResetWaitForResponse
S1AP: S1 RESET
S1AP_PARTIAL_RESET_INIT_ENB
Expiry TimerS1ResetWaitForResponse
S1AP: S1 RESET*
S1AP_GLOBAL_RESET_INIT_ENB
*After the unsuccessful S1 partial reset procedure which is indicated by a timer expiry the S1AP: S1 RESET
message is sent again from eNB to MME in order to initialize global S1 reset which means that all the UE
contexts associated with the respective S1 interface have to be released.
20th September 2012
4.3.3 S1 Partial Reset Initiated by MME (Successful Procedure)
eNB MME
Start a Supervision Wait Timer in MME
S1AP: S1 RESET*
S1AP_PARTIAL_RESET_INIT_MME
S1AP: S1 RESET ACKNOWLEDGE
Stop a Supervision Wait Timer in MME
*The intention “partial” means that with the S1 reset procedure the UE contexts included in the “UE-
associated logical S1-connection list” within the message are released.
20th September 2012
4.3.4 S1 Partial Reset Initiated by MME (Unsuccessful Procedure)
eNB MME
Start a Supervision Wait Timer in MME
S1AP: S1 RESET
S1AP_PARTIAL_RESET_INIT_MME
Expiry TimerS1ResetWaitForResponse*
S1AP: S1 RESET
S1AP_GLOBAL_RESET_INIT_MME
*After the unsuccessful S1 partial reset procedure initiated by MME which is indicated by a timer expiry the MME
either considers the S1 partial reset as finished with failures or sends S1 the S1AP: S1 RESET message to eNB in order
to initialize global S1 reset which means that all the UE contexts associated with the respective S1 interface have to
be released.
20th September 2012
4.4 S1 UE Associated Logical S1 Connection Establishment
UE eNB MME

(see chapter 2.2.1)
Successful RRC Connection establishment

(chapter 2.3.1) ending with
RRC CONNECTION SETUP COMPLETE

DCCH (NAS PDU)
S 1 AP : INITIAL UE MESSAGE* (NAS PDU )
(eNB UE S1AP ID)
UE_LOG_S1_SETUP
S1AP: INITIAL CONTEXT SETUP REQUEST*

(MME UE S1AP ID)
INI_CONT_STP_REQ
UE in ECM-CONNECTED State
*With those messages exchange the UE associated logical S1 connection is successfully established which means
that some unique UE S1AP IDs have successfully been exchanged between eNB and MME and UE has reached
ECM-CONNECTED state from network point of view.
20th September 2012
4.5 Additional E-RAB Setup
UE eNB MME
Security and Default E-RAB Establishment (see chapter 3.1.1)
E_RAB_SETUP_ATT
DRB Establishment (see chapter 3.2.1)

List is empty
E_RAB_SETUP_SUCC
20th September 2012
4.5.2 Unsuccessful Procedure
UE eNB MME
Security and Default E-RAB Establishment (see chapter 3.1.1)
S1AP:E-RAB SETUP REQUEST
E_RAB_SETUP_ATT

List is not empty
E_RAB_SETUP_FAIL_RNL*
E_RAB_SETUP_FAIL_TRANSPORT*
E_RAB_SETUP_FAIL_RESOURCE*
E_RAB_SETUP_FAIL_OTHER*
*For each E-RAB Setup counted by E_RAB_SETUP_ATT always only one of these counters is triggered in case of
unsuccessful procedure, i.e. when the E-RAB Failed to Setup List within an E-RAB Setup Response message is not
empty.
20th September 2012
5. Mobility
5.1 eNACC to GSM
Source
UE MME S-GW
eNB
UL & DL Payload PDUs
1. Decision to perform
eNACC to GSM
2. RRC:MOBILITY FROM EUTRAN
NACC_TO_GSM_ATT
Execution
eNACC
3. Detach Stop/freeze
from old L2
cell and & continue
setup of DL data
RRC buffering
Connection
in GSM 4. S1AP:UE CONTEXT RELEASE COMMAND
Completion
eNACC
NACC_TO_GSM_SUCC
5. S1AP:UE CONTEXT RELEASE COMPLETE
Note: In relation to point 4 and consequent release of all resources see also chapter 2.4.1.1, 3.3.7 and 3.4.1.
20th September 2012
5.2 CS Fallback to UTRAN or GSM via Redirect (UE in Connected Mode)
UE eNB MME
Optionally: DL NAS-PDU Transfer „CS SERVICE NOTIFICATION“ (in case of MTC)
(EXTENDED SERVICE REQUEST)
S1AP: UL NAS TRANSPORT
See also chapter 3.5 dealing on UE Context S1AP: UE CONTEXT MODIFICATION REQUEST
Modification counters. (CS Fallback Indicator)
Selection of redirect
target
S1AP: UE CONTEXT MODIFICATION RESPONSE
RRC: RRCConnectionRelease
(With Redirect Info)
CSFB_REDIR_CR_ATT
CSFB_REDIR_CR_CMODE_ATT
CSFB_REDIR_CR_EMERGENCY_ATT
S1AP: UE CONTEXT RELEASE REQUEST
L2ACK S1AP: UE CONTEXT RELEASE COMMAND
UE leaves cell S1AP: UE CONTEXT RELEASE COMPLETE
Delete Bearer Set UE to

ECM-IDLE
See also chapters 2.4.1.2, 3.3.5 and 3.4.1

dealing on some DRB, E-RAB release and
transition to ECM-IDLE state counters.
*See also the chapter 2.4.1.2.

20th September 2012
5.3 CS Fallback to UTRAN or GSM via Redirect (UE in Idle Mode)
UE eNB MME
Optional: Paging for CS domain (in case of MTC)
Initial Access with NAS Signalling for „Extended Service Request“

(CS Fallback Indicator)
UE Capabilities E-
UTRA not available
RRC: UECapabilityEnquiry
RRC: UECapabilityInformation
(UE capabilities E-UTRA )
Selection of redirect
target
S1AP: INITIAL CONTEXT SETUP RESPONSE**

RRC: RRCConnectionRelease
(With Redirect Info)
CSFB_REDIR_CR_ATT
CSFB_REDIR_CR_EMERGENCY_ATT
S1AP: UE CONTEXT RELEASE REQUEST

L2ACK
S1AP: UE CONTEXT RELEASE COMMAND
S1AP: UE CONTEXT RELEASE COMPLETE

UE leaves cell
Set UE to
Delete Bearer
ECM-IDLE
See also chapter 2.4.1.2 dealing on some

transition to ECM-IDLE state counters.
*See also the chapter 2.4.1.2.

20th September 2012
** The MME may sent Initial Context Setup message with default and/or dedicated E-RABs which eNB answers in
case of successful CSFB feedback with Initial Context Setup Complete where all the E-RAB IDs are listed, which
triggers all the related Initial E-RAB Setup counters, despite no DRB established and eNB consequently sends RRC
Connection Release with Redirect info to UE.
Common notes to chapter 5.2 and 5.3
1. The counter CSFB_REDIR_CR_ATT is pegged both for CS Fallback with redirect for UE in idle and
connected mode.
2. The counter CSFB_REDIR_CR_EMERGENCY_ATT is pegged both for CS Fallback with redirect for UE in idle
and connected mode with the with the CS Fallback Indicator set to CS Fallback High Priority in the S1AP:
INITIAL CONTEXT SETUP REQUEST and S1AP: UE CONTEXT MODIFICATION REQUEST message,
respectively.
20th September 2012
5.4 Intra eNB Handover
UE eNB
1. RRC Connection Reconfiguration

(Measurement Control)
Packet data
UL allocation
2. Measurement Reports
3. HO Decision**
Start THOoverall
INTRA_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
4. Admission Control and

Resource Allocation
DL allocation
ATT_INTRA_ENB_HO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
Handover Execution
HO_EMG_ATT
Detach from old cell and

HO_DRX_ATT
synchronise to new cell
6. Synchronisation
See chapter 2.2.2.1
7. UL allocation + TA for UE
8. RRC Connection Reconfiguration Stop THOoverall

Complete
9. Release
Resources
SUCC_INTRA_ENB_HO
Handover Completion
RB_REL_REQ_NORM_REL*
ENB_INIT_TO_IDLE_NORM_REL
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_SUCC)
HO_EMG_SUCC
HO_DRX_SUCC
Packet data
20th September 2012
Notes:
- *See chapter 3.4.1.

- **During this phase when RRM decides to send the target cells list to Mobility Management (MM) unit
the counter TOT_HO_DECISION is incremented otherwise the TOT_NOT_START_HO_PREP is pegged.
- In relation to points 5 and 8 see also chapter 3.2.1.
5.4.2 Unsuccessful Procedure (HO Preparation failure)
UE eNB

Packet data
UL allocation
3. HO Decision
Start THOoverall
INTRA_ENB_HO_PREP
HO_EMG_PREP

Resource Allocation -Failure
Stop THOoverall
FAIL_ENB_HO_PREP_AC
FAIL_ENB_HO_PREP_OTH
HO_EMG_PREP_FAIL
20th September 2012
5.4.3 Unsuccessful Procedure (HO Execution failure)
UE eNB

Packet data
UL allocation
3. HO Decision
Start THOoverall
INTRA_ENB_HO_PREP
HO_EMG_PREP

Resource Allocation
DL allocation
Handover Execution
ATT_INTRA_ENB_HO
HO_EMG_ATT
HO_DRX_ATT
Expiry THOoverall
ENB_INTRA_HO_FAIL
Note: In relation to point 5 and THOoverall Timer expiry see also chapter 3.2.4.
20th September 2012
5.5 Inter eNB X2 Based Handover

Source Target Serving
UE MME
eNB eNB GW
0. Area Restriction Provided

1.RRC Connection Reconfiguration
Packet data Packet data
UL allocation
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP
HO_EMG_PREP
Resource Allocation
Stop TX2RELOCprep
Start TX2RELOCOverall 6. Handover Request
Acknowledge Start TX2RELOCexec
ATT_INTER_ENB_HO
HO_EMG_ATT
Handover Execution
HO_DRX_ATT
DL allocation
8. SN Status Transfer
Data Forwarding
Detach from old cell
Buffer Packets from
Source eNB
9. Synchronisation
See chapter 2.2.2.2
11. RRC Connection Reconfiguration Complete
Stop TX2RELOCexec
12a.RRC Connection Reconfiguration(Measurement Configuration)
13. Path Switch Request
12b. RRC Connection Reconfiguration Complete 14. User Plane Update Request
End Marker
15. Switch DL Path
Packet data
17. Path Switch Request 16. User Plane Update Response

Handover Completion
Acknowledge
Stop TX2RELOCOverall 18. UE Context Release
Release X2
SUCC_INTER_ENB_HO
Signalling
Connection
HO_EMG_SUCC
HO_DRX_SUCC
Data Forwarding
End Marker
Note: *See chapter 3.4.1. In relation to points 6 and 11 see also chapter 3.2.2.
20th September 2012
5.5.2 Unsuccessful Procedure (HO Preparation Failure -Time

cause)
UE MME
eNB eNB GW

UL allocation
3. HO Decision
INTER_ENB_HO_PREP
HO_EMG_PREP 5. Admission Control and
Resource Allocation
6. Handover Request
Acknowledge
Expiry TX2RELOCprep
FAIL_ENB_HO_PREP_TIME
HO_EMG_PREP_FAIL
20th September 2012
5.5.3 Unsuccessful Procedure (HO Preparation Failure –AC or

OTHER cause)
UE MME
eNB eNB GW

UL allocation
3. HO Decision
INTER_ENB_HO_PREP
HO_EMG_PREP 5. Admission Control and
Resource Allocation
Stop TX2RELOCprep 6. Handover Preparation
Failure
FAIL_ENB_HO_PREP_AC
FAIL_ENB_HO_PREP_OTHER
20th September 2012
5.5.4 Unsuccessful Procedure (HO Execution or Completion

Failure)
UE MME
eNB eNB GW

UL allocation
3. HO Decision
INTER_ENB_HO_PREP
HO_EMG_PREP
Resource Allocation
Stop TX2RELOCprep
Start TX2RELOCOverall 6. Handover Request
Acknowledge Start TX2RELOCexec
ATT_INTER_ENB_HO
HO_EMG_ATT
Handover Execution
HO_DRX_ATT
DL allocation
7.RRC Connection Reconfiguration 8. SN Status Transfer
Data Forwarding
Buffer Packets from
Source eNB
9. Synchronisation
See chapter 2.2.2.2
11. RRC Connection Reconfiguration Complete
Stop TX2RELOCexec
12a.RRC Connection Reconfiguration(Measurement Configuration)
13. Path Switch Request
12b. RRC Connection Reconfiguration Complete 14. User Plane Update Request
Start TX2RELOCcomp
End Marker
15. Switch DL Path
Packet data
Stop TX2RELOCcomp
17. Path Switch Request 16. User Plane Update Response
Handover Completion
Acknowledge
An error occurred which leads to 18. UE Context Release

UE Context Release never received by Source eNB
Expiry TX2RELOCOverall
INTER_ENB_HO_FAIL
Common note to chapter 5.5

20th September 2012
In case of path switch request failure (triggered by either Path Switch Request Failure message sent from MME to
target eNB or TX2RELOCcomp timer expiry) the handover is evaluated as a normal one from source cell point of view
(i.e. X2AP: UE Context Release is sent from Target to Source eNB) but the related UE Context is consequently released
which triggers ENB_INIT_TO_IDLE_OTHER, ENB_EPS_BEARER_REL_REQ_TNL and RB_REL_REQ_OTHER counters in
the target cell.
20th September 2012
5.6 Inter eNB S1 Based Handover

Source Target MME/ Serving
UE
eNB eNB EPC GW

3. HO Decision 4. Handover Required
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP
HO_EMG_PREP 5. HO preparation in EPC
6. Handover Request

Resource Allocation
8. Handover Request
Start TS1RELOCexec Acknowledge
9. HO preparation
Stop TS1RELOCprep completion in EPC
9a. Create Indirect Data
10. Handover Command Forwarding Tunnel Request
StartTS1RELOCOverall
11. Trigger HO execution

9b. Create Indirect Data
Forwarding Tunnel Response
INTER_ENB_S1_HO_ATT
HO_EMG_ATT
HO_DRX_ATT
Handover Execution
12.RRC Connection Reconfiguration 13a. eNB Status Transfer
13b. MME Status Transfer
(Indirect) Data Forwarding

Buffer Packets from
Source eNB
14. Synchronisation
See chapter 2.2.2.2
14a. UL allocation + TA for UE
15. RRC Connection Reconfiguration Complete Stop TS1RELOCexec
Packet data
16. Handover Notify
17a. Modify Bearer Request
17b. Modify Bearer Response

End Marker (or TDATAS1retard)
Packet data (route optimized)
Begin sending
fresh S1-U data
Handover Completion
18. UE Context Release Command

StopTS1RELOCOverall
INTER_ENB_S1_HO_SUCC
HO_EMG_SUCC
20. Delete Indirect Data
Forwarding Tunnel Request
HO_DRX_SUCC
19. UE Context Release Complete
21. Delete Indirect Data
Release data forwarding Release data forwarding Forwarding Tunnel Response
resources resources
20th September 2012
Notes:
- *See chapter 3.4.1.

- In relation to points 8 and 15 see also chapter 3.2.3.
5.6.2 Unsuccessful Procedure (HO Preparation Failure -Time

cause)
UE
eNB eNB EPC GW

3. HO Decision
4. Handover Required
Start TS1RELOCprep
HO_EMG_PREP
5. HO preparation in EPC
6. Handover Request

Resource Allocation
8. Handover Request
Forwarding Tunnel Request
10. Handover Command
9b. Create Indirect Data
Expiry TS1RELOCprep
An error occurred which leads to
Handover Command never received by Source eNB
INTER_S1_HO_PREP_FAIL_TIME
HO_EMG_PREP_FAIL
20th September 2012
5.6.3 Unsuccessful Procedure (HO Preparation Failure -

Resource or OTHER cause)
UE
eNB eNB EPC GW

3. HO Decision
Start TS1RELOCprep
HO_EMG_PREP
6. Handover Request

Resource Allocation
8. Handover Preparation
Failure
Stop TS1RELOCprep 9. Handover Preparation

Failure
INTER_S1_HO_PREP_FAIL_NORR
INTER_S1_HO_PREP_FAIL_OTHER
20th September 2012
5.6.4 Unsuccessful Procedure (HO Execution or Completion

Failure)
UE
eNB eNB EPC GW

3. HO Decision
Start TS1RELOCprep
HO_EMG_PREP
6. Handover Request

Resource Allocation
8. Handover Request
9. HO preparation
Stop TS1RELOCprep completion in EPC
StartTS1RELOCOverall 10. Handover Command Forwarding Tunnel Request
11. Trigger HO execution 9b. Create Indirect Data

INTER_ENB_S1_HO_ATT
HO_EMG_ATT
HO_DRX_ATT
Handover Execution
12.RRC Connection Reconfiguration 13a. eNB Status Transfer
13b. MME Status Transfer
Buffer Packets from

Source eNB
14. Synchronisation
14a. UL allocation + TA for UE
15. RRC Connection Reconfiguration Complete Stop TS1RELOCexec
Packet data
16. Handover Notify
17a. Modify Bearer Request
17b. Modify Bearer Response

End Marker (or TDATAS1retard)
Packet data (route optimized)
Handover Completion
Begin sending
fresh S1-U data
18. UE Context Release Command

An error occurred which leads to
UE Context Release Command never received by Source eNB
Expiry TS1RELOCOverall
INTER_ENB_S1_HO_FAIL
Common notes to chapters 5.4, 5.5 and 5.6

20th September 2012
1. The counters included in the following table dealing with handover for IMS emergency sessions, inter-
frequency handover and handover for the UEs running in DRX mode are triggered independently of
network topology (i.e. it is intra or inter eNB handover).
HO for IMS Emergency Sessions HO_EMG_PREP, HO_EMG_PREP_FAIL, HO_EMG_ATT,

HO_EMG_SUCC,
Inter-frequency HO Total:
HO_INTFREQ_ATT, HO_INTFREQ_SUCC
Measurement gaps assisted:
HO_INTFREQ_GAP_ATT, HO_INTFREQ_GAP_SUCC
HO for the UEs running in DRX HO_DRX_ATT, HO_DRX_SUCC
mode
2. It should be noted that besides the mentioned intra and inter eNB counters triggered on a per source cell
basis there are also the counters pegged with the same trigger events but updated in addition with a
relationship to the touched neighbouring cell (see the following table).
Intra eNB HO counters per neighbouring INTRA_HO_PREP_FAIL_NB, INTRA_HO_ATT_NB,
cell INTRA_HO_SUCC_NB, INTRA_HO_FAIL_NB
Inter eNB HO counters per neighbouring INTER_HO_PREP_FAIL_OTH_NB,
cell INTER_HO_PREP_FAIL_TIME_NB,
INTER_HO_PREP_FAIL_AC_NB,
INTER_HO_ATT_NB, INTER_HO_SUCC_NB,
INTER_HO_FAIL_NB
3. The message exchange between the UE and eNB is out of indicating logical channel type due to huge
number of messages in the message sequence charts. Anyhow all the RRC messages are transmitted via
either DCCH or CCCH, payload on DTCH and regarding the random access the messages used for that
procedure can be found in the chapter 2.2.2.
20th September 2012
5.7 Inter RAT Handover
5.7.1 Handover from LTE to UTRAN
5.7.1.1 Successful Procedure
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
handover to UMTS
Start TS1RELOCprep 2. S1AP:HANDOVER REQUIRED
ISYS_HO_PREP
3. Handover Preparation:
· Map EPS bearers to PDP contexts
· Map EPS QoS parameters to pre-Rel8 QoS parameters
· Map EPS security parameters to UTRAN security parameters
· Data path tunnel resource allocation
· Selection of data forwarding
· Indirect forwarding tunnel setup (if required)
· Transport of direct forwarding tunnel parameters (if required)
Stop TS1RELOCprep
4. S1AP:HANDOVER COMMAND
Start TS1RELOCoverall
Handover Execution
ISYS_HO_ATT
ISYS_HO_UTRAN_SRVCC_ATT

COMMAND
CSFB_PSHO_UTRAN_ATT
6a. Data Forwarding (direct case)
6b. Data Forwarding (indirect case)

7. Detach
from old
cell and
complete
handover
Handover Completion
to new cell
Downlink Data
Uplink Data
8. Update Path in P-GW is S-GW relocation is performed (transparent to eNB).
9. S1AP:UE CONTEXT RELEASE COMMAND

Stop TS1RELOCoverall
ISYS_HO_SUCC
ISYS_HO_UTRAN_SRVCC_SUCC

20th September 2012
Note: In relation to points 9 and 10 and consequent release of all the resources assigned to the UE see also
chapter 2.4.1.1, 3.3.7 and 3.4.1.
5.7.1.2 Unsuccessful Procedure (Handover

Preparation Failure – Time cause)
Source Target
eNB RNC
handover to UMTS
ISYS_HO_PREP
·
Map EPS bearers to PDP contexts
Expiry TS1RELOCprep An error occurred which leads to HO

Command never received by Source eNB
ISYS_HO_PREP_FAIL_TIM
20th September 2012

Preparation Failure – AC or OTHER cause)
Source Target
eNB RNC
handover to UMTS
ISYS_HO_PREP
Stop TS1RELOCprep
4. S1AP:HANDOVER
PREPARATION FAILURE An error occurred which leads to sending
HO Preparation Failure to Source eNB
ISYS_HO_PREP_FAIL_AC
ISYS_HO_PREP_FAIL_OTH
20th September 2012

Execution or Completion Failure)
Source Target
eNB RNC
handover to UMTS
ISYS_HO_PREP
Stop TS1RELOCprep
Handover Execution
ISYS_HO_ATT
ISYS_HO_UTRAN_SRVCC_ATT
CSFB_PSHO_UTRAN_ATT
6a. Data Forwarding (direct case)
7. Detach 6b. Data Forwarding (indirect case)

from old
cell and
complete
handover
Handover Completion
to new cell
Downlink Data
Uplink Data
8. Update Path in P-GW is S-GW relocation is performed (transparent to eNB).
Expiry TS1RELOCoverall
An error occurred which leads to UE
Context Release Command never received
by Source eNB
ISYS_HO_FAIL
ISYS_HO_UTRAN_SRVCC_FAIL
20th September 2012
Common notes to chapter 5.7.1
1. The counters related to handover preparation to UTRAN are also triggered in case of handover
preparation to UTRAN with SRVCC while the rest of the counters related handover execution and
completion phase to UTRAN do not. In those phases some own counters for the handover to UTRAN with
SRVCC are triggered only.
2. All the counters related to handover to UTRAN are also triggered in case of CSFB with PS Handover.
3. It should be noted that besides the mentioned counters triggered on a per source cell basis there are also
the counters pegged with the same trigger events but updated in addition with a relationship to the
touched neighbouring cell (see the following table).
Inter RAT HO counters to UTRAN per ISYS_HO_UTRAN_PREP_FAIL_TIM_NB,
neighbouring cell ISYS_HO_UTRAN_PREP_FAIL_AC_NB,
ISYS_HO_UTRAN_PREP_FAIL_OTH_NB,
ISYS_HO_UTRAN_ATT_NB,
ISYS_HO_UTRAN_SUCC_NB,
ISYS_HO_UTRAN_FAIL_NB,
ISYS_HO_UTRAN_PREP_NB
Inter RAT HO counters to UTRAN with ISYS_HO_UTRAN_SRVCC_ATT_NB,
SRVCC per neighbouring cell ISYS_HO_UTRAN_SRVCC_SUCC_NB,
ISYS_HO_UTRAN_SRVCC_FAIL_NB
20th September 2012
5.7.2 Handover from LTE to GERAN
5.7.2.1 Successful Procedure
Source Target
eNB BSS
SRVCC to GSM
2. S1AP:HANDOVER REQUIRED
Start TS1RELOCprep
Stop TS1RELOCprep
Handover Execution
ISYS_HO_GERAN_SRVCC_ATT

COMMAND
6. Detach from old cell and complete handover to GERAN
Handover Completion

Stop TS1RELOCoverall
ISYS_HO_GERAN_SRVCC_SUCC
Note: In relation to points 7 and 8 and consequent release of all the resources assigned to the UE see also
chapter 2.4.1.1, 3.3.7 and 3.4.1.
20th September 2012

Execution or Completion Failure)
Source Target
eNB BSS
SRVCC to GSM
2. S1AP:HANDOVER REQUIRED
Start TS1RELOCprep
Stop TS1RELOCprep
Handover Execution
ISYS_HO_GERAN_SRVCC_ATT

COMMAND
6. Detach from old cell and complete handover to GERAN
Handover Completion
7. S1AP:UE CONTEXT
RELEASE COMMAND
Expiry TS1RELOCoverall An error occurred which leads to UE
Context Release Command never received
ISYS_HO_GERAN_SRVCC_FAIL
by Source eNB
Common notes to chapter 5.7.2
1. The handover from LTE to GERAN is only possible with SRVCC. To hand over a non VoIP session from LTE
to GERAN an eNACC is used (see chapter 5.1).
2. It should be noted that besides the mentioned counters triggered on a per source cell basis there are also
the counters pegged with the same trigger events but updated in addition with a relationship to the
touched neighbouring cell (see the following table).
Intra RAT HO to GERAN with SRVCC ISYS_HO_GERAN_SRVCC_ATT_NB,
counters per neighbouring cell ISYS_HO_GERAN_SRVCC_SUCC_NB,
ISYS_HO_GERAN_SRVCC_FAIL_NB
20th September 2012
5.8 Mobility Robustness Optimization Features
5.8.1 Late handover

UE
eNB eNB EPC GW
· The UE is experienced to RLF instead of HO (optionally recoverable RLF on eNB side). I.e. HO
is missed with an option that in the source cell of missed HO attempt, a HO preparation for the
considered UE context can be ongoing.
· The UE will continue with RRC connection re-establishment request in another cell
RRC CONNECTION REESTABLISHMENT REQUEST
If,
· the UE context is not found,
or the request cannot be authenticated,
· and If the reestablishment cause is not
“ReconfigurationFailure
the target eNB shall trigger the X2 RLF
Indication procedure.
X2AP: RLF INDICATION
If,
· the received PhysCellId field in the
Failure cell (PCI IE) corresponds to
the physical cell identity of the cell
receiving this X2 message,
· the UE context is found and
· the UE authentication is successful
and
· if If TStoreUE_CNTXT timer is not running
and no incoming handover has been
initiated
then, the eNB shall stop TRLF timer if
running, release the held UE context and
increment the following too late HO
counters
MRO_LATE_HO
MRO_LATE_HO_NB
20th September 2012
5.8.2 Early Type 1 handover

UE
eNB eNB EPC GW
· The HO is successfully attempted in the target cell but failed (T304 expired)
· The UE will continue with RRC connection re-establishment request in source cell
RRC CONNECTION
REESTABLISHMENT
REQUEST
If,
· re-establishment cause is equal to
‘HOfailure’
· C-RNTI corresponds to an available
UE context for which outgoing HO
preparation is ongoing
· included shortMAC-I matches the
local security calculation (successful
authentication)
then, the eNB shall increment the

following early type 1 HO counters
MRO_EARLY_TYPE1_HO
MRO_EARLY_TYPE1_HO_NB
20th September 2012
5.8.3 Early Type 2 handover

Source Target Another MME/ Serving
UE
eNB eNB eNB EPC GW
· successfull connection establishment in HO target cell (attempted HO completed) followed by

RRC connection re-establishment request in another cell a ‘short time’ after HO completion due
to an error,
· successfull random access to HO target cell followed by failed Msg3 reception (attempted HO
uncompleted) followed by re-establishment request in another cell. ‘Short time’ is defined as
time period no longer than expiration value of Tstore_UE_cntxt timer up from HO completion.
RRC CONNECTION
REESTABLISHMENT
REQUEST
If,
· the UE context is not found,
or the request cannot be
authenticated,
· and If the reestablishment
cause is not
“ReconfigurationFailure
the another eNB shall trigger the
X2 RLF Indication procedure.
X2AP: RLF
INDICATION
If,
· the received PhysCellId field in
the Failure cell (PCI IE)
corresponds to the physical cell
identity of the cell receiving this
X2 message,
· the UE context is found and
· the UE authentication is
successful
and
· If TStoreUE_CNTXT timer
(note1) is running OR an
incoming handover has been
initiated
Then eNB shall stop
TStoreUE_CNTXT timer and/or
TRLF timer whichever is running,
release the held UE context and trigger
the X2 Handover Report procedure
X2AP: HANDOVER
REPORT (Early)
MRO_EARLY_TYPE2_HO
MRO_EARLY_TYPE2_HO_NB
20th September 2012
Common notes to chapter 5.8:
1. The counters MRO_LATE_HO, MRO_EARLY_TYPE1_HO and MRO_EARLY_TYPE2_HO are triggered on a per

source cell basis while the following one MRO_LATE_HO_NB, MRO_EARLY_TYPE1_HO_NB and
MRO_EARLY_TYPE2_HO_NB in addition with a relationship to the touched neighbouring cell.
2. The source, target and another cell do not need to be located in separated eNBs. Also feasible scenario is
if they are located even within the same eNB when the mentioned procedures are evaluated internally in
this one eNB.
20th September 2012
6. X2AP Related Procedures

6.1 Successful Procedure
Initiating Responding
eNB eNB
X2AP: X2 SETUP REQUEST
X2_SETUP_ATT
X2AP: X2 SETUP RESPONSE
6.2 Unsuccessful Procedure
Initiating Responding
eNB eNB
X2AP: X2 SETUP REQUEST
X2_SETUP_ATT
X2AP: X2 SETUP FAILURE
X2_SETUP_FAIL
20th September 2012
7. References
[1] RL30 LTE Control Plane Message Sequence Charts, System Feature Specification
https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=437481274&objAction=Browse
[2] PMO LTE SFS RAN Measure

doors://fiesvmp040:36655/?version=2&prodID=0&urn=urn:telelogic:68a6beb0-29bd-11df-bcd9-cd506bb8bf5d:1-
4017b9fe29051a61-M-00009100
[3] Common Counter Module

doors://fiesvmp040:36655/?version=2&prodID=0&urn=urn:telelogic:68a6beb0-29bd-11df-bcd9-cd506bb8bf5d:1-
4017b9fe29051a61-M-0000a557
[4] RL40/RL35TD LTE RAN KPI Specification Document

https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=424432649&objAction=Browse
[5] 3GPP TS 32.425 - Performance measurements for E-UTRAN
[6] 3GPP TS 32.404 - Performance measurements - Definitions and template

20th September 2012
8. Appendix
8.1 List of E-UTRAN PM Counters
PI ID NetAct name Chapter (where the counter is used)

M8006C1 EPS_BEARER_SETUP_COMPLETIONS 3.1.1, 3.1.3
M8006C0 EPS_BEARER_SETUP_ATTEMPTS 3.1.1, 3.1.2, 3.1.3, 3.1.4
M8006C35 EPS_BEARER_STP_COM_INI_QCI1 3.1.1,
M8006C168 EPS_BEARER_STP_COM_INI_QCI_2 3.1.1,
M8006C169 EPS_BEARER_STP_COM_INI_QCI_3 3.1.1
M8006C170 EPS_BEARER_STP_COM_INI_QCI_4 3.1.1
M8006C36 EPS_BEAR_STP_COM_INI_NON_GBR 3.1.1
M8006C17 EPS_BEARER_STP_ATT_INI_QCI_1 3.1.1, 3.1.2
M8006C18 EPS_BEAR_STP_ATT_INI_NON_GBR 3.1.1, 3.1.2
M8000C32 E_RAB_SETUP_ATT_EMG 3.1.3, 3.1.4
M8000C33 E_RAB_SETUP_SUCC_EMG 3.1.3
M8006C2 EPS_BEARER_SETUP_FAIL_RNL 3.1.2, 3.1.4
M8006C3 EPS_BEARER_SETUP_FAIL_TRPORT 3.1.2, 3.1.4
M8006C4 EPS_BEARER_SETUP_FAIL_RESOUR 3.1.2, 3.1.4
M8006C5 EPS_BEARER_SETUP_FAIL_OTH 3.1.2, 3.1.4
M8000C34 E_RAB_SETUP_FAIL_RB_EMG 3.1.4
M8006C26 EPS_BEARER_STP_ATT_ADD_QCI_1 3.1.3, 3.1.4
M8006C44 EPS_BEAR_SET_COM_ADDIT_QCI1 3.1.3
M8006C171 EPS_BEAR_SET_COM_ADD_QCI_2 3.1.3
M8006C6 EPC_EPS_BEARER_REL_REQ_NORM 3.3.3, 3.3.7
M8006C7 EPC_EPS_BEARER_REL_REQ_DETACH 3.3.3, 3.3.7
M8006C8 EPC_EPS_BEARER_REL_REQ_RNL 3.3.4, 3.3.8
M8006C9 EPC_EPS_BEARER_REL_REQ_OTH 3.3.4, 3.3.8
M8006C15 ENB_EPSBEAR_REL_REQ_RNL_REDIR 3.3.5
M8006C10 ENB_EPS_BEARER_REL_REQ_NORM 3.3.1, 3.3.5
M8006C12 ENB_EPS_BEARER_REL_REQ_RNL 3.3.2, 3.3.6
20th September 2012
M8006C14 ENB_EPS_BEARER_REL_REQ_TNL 3.3.2, 3.3.6

M8006C13 ENB_EPS_BEARER_REL_REQ_OTH 3.3.2, 3.3.6
M8006C89 EPC_EPS_BEAR_REL_REQ_N_QCI1 3.3.3, 3.3.7
M8006C98 EPC_EPS_BEAR_REL_REQ_D_QCI1 3.3.3, 3.3.7
M8006C107 EPC_EPS_BEAR_REL_REQ_R_QCI1 3.3.4, 3.3.8
M8006C116 EPC_EPS_BEAR_REL_REQ_O_QCI1 3.3.4, 3.3.8
M8006C161 ENB_EPS_BEAR_REL_REQ_RD_QCI1 3.3.5
M8006C125 ENB_EPS_BEAR_REL_REQ_N_QCI1 3.3.1, 3.3.5
M8006C134 ENB_EPS_BEAR_REL_REQ_R_QCI1 3.3.2, 3.3.6
M8006C152 ENB_EPS_BEAR_REL_REQ_T_QCI1 3.3.2, 3.3.6
M8006C143 ENB_EPS_BEAR_REL_REQ_O_QCI1 3.3.2, 3.3.6
M8006C174 PRE_EMPT_GBR_BEARER 3.3.1, 3.3.5
M8006C175 PRE_EMPT_NON_GBR_BEARER 3.3.1, 3.3.5
M8000C1 INI_CONT_STP_COMP 4.1.1
M8000C0 INI_CONT_STP_REQ 4.1.1, 4.1.2
M8000C2 INI_CONT_STP_FAIL_RNL 4.1.2
M8000C3 INI_CONT_STP_FAIL_TRPORT 4.1.2
M8000C4 INI_CONT_STP_FAIL_RESOUR 4.1.2
M8000C5 INI_CONT_STP_FAIL_OTHER 4.1.2
M8000C12 UE_LOG_S1_SETUP 4.4
M8000C7 S1_SETUP_SUCC 4.2.1
M8000C6 S1_SETUP_ATT 4.2.1, 4.2.2, 4.2.3
M8000C8 S1_SETUP_FAIL_NO_RESP 4.2.2
M8000C9 S1_SETUP_FAIL_IND_BY_MME 4.2.3
M8000C15 S1AP_PARTIAL_RESET_INIT_ENB 4.3.1, 4.3.2
M8000C13 S1AP_GLOBAL_ RESET_INIT_ENB 4.3.2
M8000C16 S1AP_PARTIAL_RESET_INIT_MME 4.3.3, 4.3.4
M8000C14 S1AP_GLOBAL_RESET_INIT_MME 4.3.4
M8007C0 DATA_RB_STP_ATT 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5,
3.2.6
M8007C1 DATA_RB_STP_COMP 3.2.1, 3.2.2, 3.2.3
M8007C2 DATA_RB_STP_FAIL 3.2.4, 3.2.5, 3.2.6
M8001C224 CELL_LOAD_ACT_UE_MAX 3.2.1, 3.2.2, 3.2.3, 2.4.1.1,
2.4.1.2, 2.4.2.1, 2.4.2.2, 2.4.2.3
M8001C223 CELL_LOAD_ACT_UE_AVG 3.2.1, 3.2.2, 3.2.3, 2.4.1.1,
2.4.1.2, 2.4.2.1, 2.4.2.2, 2.4.2.3
M8001C199 RRC_CONN_UE_AVG 3.2.1, 3.2.2, 3.2.3, 2.3.1, 2.4.1.1,
2.4.1.2, 2.4.2.1, 2.4.2.2, 2.4.2.3
M8001C200 RRC_CONN_UE_MAX 3.2.1, 3.2.2, 3.2.3, 2.3.1, 2.4.1.1,
2.4.1.2, 2.4.2.1, 2.4.2.2, 2.4.2.3
20th September 2012
M8007C3 RB_REL_REQ_NORM_REL 3.4.1, 5.4.1, 5.5.1, 5.6.1

M8007C4 RB_REL_REQ_DETACH_PROC 3.4.1
M8007C5 RB_REL_REQ_RNL 3.4.2
M8007C13 RB_REL_REQ_RNL_REDIR 3.4.1
M8007C6 RB_REL_REQ_OTHER 3.4.2
M8013C17 SIGN_CONN_ESTAB_ATT_MO_S 2.3.1, 2.3.2, 2.3.3, 2.3.4
M8013C18 SIGN_CONN_ESTAB_ATT_MT 2.3.1, 2.3.2, 2.3.3, 2.3.4
M8013C19 SIGN_CONN_ESTAB_ATT_MO_D 2.3.1, 2.3.2, 2.3.3, 2.3.4
M8013C20 SIGN_CONN_ESTAB_ATT_OTHERS 2.3.1, 2.3.2, 2.3.3, 2.3.4
M8013C21 SIGN_CONN_ESTAB_ATT_EMG 2.3.1, 2.3.2, 2.3.3, 2.3.4
M8013C5 SIGN_CONN_ESTAB_COMP 2.3.1
M8013C26 SIGN_CONN_ESTAB_COMP_EMG 2.3.1
M8013C6 SIGN_EST_F_RRCCOMPL_MISSING 2.3.2
M8013C7 SIGN_EST_F_RRCCOMPL_ERROR 2.3.3
M8013C8 SIGN_CONN_ESTAB_FAIL_RRMRAC 2.3.4
M8008C6 RRC_CON_RE_ESTAB_ATT_HO_FAIL 2.5.1, 2.5.2
M8008C8 RRC_CON_RE_ESTAB_ATT_OTHER 2.5.1, 2.5.2
M8008C4 RRC_CON_RE_ESTAB_ATT 2.5.1, 2.5.2
M8008C5 RRC_CON_RE_ESTAB_SUCC 2.5.1
M8008C7 RRC_CON_RE_ESTAB_SUCC_HO_FAIL 2.5.1
M8008C9 RRC_CON_RE_ESTAB_SUCC_OTHER 2.5.1
M8008C0 REJ_RRC_CONN_RE_ESTAB 2.5.2
M8008C2 DISC_RRC_PAGING 2.1
M8008C1 RRC_PAGING_REQUESTS 2.1
M8008C3 RRC_PAGING_MESSAGES 2.1
M8009C2 INTRA_ENB_HO_PREP 5.4.1, 5.4.2, 5.4.3
M8009C6 ATT_INTRA_ENB_HO 5.4.1, 5.4.3
M8009C3 FAIL_ENB_HO_PREP_AC 5.4.2
M8009C5 FAIL_ENB_HO_PREP_OTH 5.4.2
M8009C7 SUCC_INTRA_ENB_HO 5.4.1
M8009C8 ENB_INTRA_HO_FAIL 5.4.3
M8021C6 HO_EMG_PREP 5.4.1, 5.4.2, 5.4.3, 5.5.1, 5.5.2,
5.5.3, 5.5.4, 5.6.1, 5.6.2, 5.6.3,
5.6.4
M8021C9 HO_EMG_PREP_FAIL 5.4.2, 5.5.2, 5.6.2
M8021C12 HO_EMG_ATT 5.4.1, 5.4.3, 5.5.1, 5.5.4, 5.6.1,
5.6.4
M8021C15 HO_EMG_SUCC 5.4.1, 5.5.1, 5.6.1
M8021C18 HO_DRX_ATT 5.4.1, 5.4.3, 5.5.1, 5.5.4, 5.6.1,
5.6.4
20th September 2012
M8021C19 HO_DRX_SUCC 5.4.1, 5.5.1, 5.6.1

M8021C2 HO_INTFREQ_SUCC 5.4.1, 5.5.1, 5.6.1
M8021C0 HO_INTFREQ_ATT 5.4.1, 5.4.3, 5.5.1, 5.5.4, 5.6.1,
5.6.4
M8021C3 HO_INTFREQ_GAP_SUCC 5.4.1, 5.5.1, 5.6.1
M8021C1 HO_INTFREQ_GAP_ATT 5.4.1, 5.4.3, 5.5.1, 5.5.4, 5.6.1,
5.6.4
M8021C20 MRO_LATE_HO 5.8.1
M8021C21 MRO_EARLY_TYPE1_HO 5.8.2
M8021C22 MRO_EARLY_TYPE2_HO 5.8.3
M8015C16 MRO_LATE_HO_NB 5.8.1
M8015C17 MRO_EARLY_TYPE1_HO_NB 5.8.2
M8015C18 MRO_EARLY_TYPE2_HO_NB 5.8.3
M8014C6 INTER_ENB_HO_PREP 5.5.1, 5.5.2, 5.5.3, 5.5.4
M8014C0 ATT_INTER_ENB_HO 5.5.1, 5.5.4
M8014C2 FAIL_ENB_HO_PREP_TIME 5.5.2
M8014C3 FAIL_ENB_HO_PREP_AC 5.5.3
M8014C5 FAIL_ENB_HO_PREP_OTHER 5.5.3
M8014C7 SUCC_INTER_ENB_HO 5.5.1
M8014C8 INTER_ENB_HO_FAIL 5.5.4
M8014C18 INTER_ENB_S1_HO_ATT 5.6.1, 5.6.4
M8014C14 INTER_ENB_S1_HO_PREP 5.6.1, 5.6.2, 5.6.3, 5.6.4
M8014C15 INTER_S1_HO_PREP_FAIL_TIME 5.6.2
M8014C16 INTER_S1_HO_PREP_FAIL_NORR 5.6.3
M8014C17 INTER_S1_HO_PREP_FAIL_OTHER 5.6.3
M8014C19 INTER_ENB_S1_HO_SUCC 5.6.1
M8014C20 INTER_ENB_S1_HO_FAIL 5.6.4
M8016C11 CSFB_REDIR_CR_ATT 5.2, 5.3
M8016C12 CSFB_REDIR_CR_CMODE_ATT 5.2
M8016C13 CSFB_REDIR_CR_EMERGENCY_ATT 5.2, 5.3
M8000C31 UE_CONTEXT_MOD_ATT_CSFB 3.5.1, 3.5.2, 5.2
M8016C32 CSFB_PSHO_UTRAN_ATT 5.7.1.1, 5.7.1.4
M8016C14 ISYS_HO_PREP 5.7.1.1, 5.7.1.2, 5.7.1.3, 5.7.1.4
M8016C21 ISYS_HO_ATT 5.7.1.1, 5.7.1.4
M8016C15 ISYS_HO_PREP_FAIL_TIM 5.7.1.2
M8016C16 ISYS_HO_PREP_FAIL_AC 5.7.1.3
M8016C17 ISYS_HO_PREP_FAIL_OTH 5.7.1.3
M8016C23 ISYS_HO_SUCC 5.7.1.1
M8016C25 ISYS_HO_FAIL 5.7.1.4
M8016C29 ISYS_HO_UTRAN_SRVCC_ATT 5.7.1.1, 5.7.1.4
20th September 2012
M8016C31 ISYS_HO_UTRAN_SRVCC_FAIL 5.7.1.4

M8016C30 ISYS_HO_UTRAN_SRVCC_SUCC 5.7.1.1
M8016C33 ISYS_HO_GERAN_SRVCC_ATT 5.7.2.1, 5.7.2.2
M8016C35 ISYS_HO_GERAN_SRVCC_FAIL 5.7.2.2
M8016C34 ISYS_HO_GERAN_SRVCC_SUCC 5.7.2.1
M8016C26 NACC_TO_GSM_ATT 5.1
M8016C27 NACC_TO_GSM_SUCC 5.1
M8000C23 UE_CONTEXT_MOD_ATT 3.5.1, 3.5.2
M8000C25 UE_CONTEXT_MOD_FAIL 3.5.2
M8000C24 UE_CONTEXT_MOD_ATT_AMBR 3.5.1, 3.5.2
M8022C0 X2_SETUP_ATT 6.1, 6.2
M8022C1 X2_SETUP_FAIL 6.2
M8001C421 PDCCH_ORDER_ATT 2.2.2.1
M8001C422 PDCCH_INIT_ORDER_ATT 2.2.2.1
M8001C423 PDCCH_ORDER_SUCCESS 2.2.2.1
M8001C425 D_PREAMB_PDCCH_UNAVAIL 2.2.2.4
M8001C426 D_PREAMB_HO_UNAVAIL 2.2.2.4
M8001C424 D_PREAMB_UNAVAIL 2.2.2.4
M8001C6 RACH_STP_ATT_SMALL_MSG 2.2.1
M8001C7 RACH_STP_ATT_LARGE_MSG 2.2.1
M8001C8 RACH_STP_COMPLETIONS 2.2.1, 2.2.2.1, 2.2.2.2, 2.2.2.3
M8001C286 RACH_STP_ATT_DEDICATED 2.2.2.1, 2.2.2.2, 2.2.2.3
M8013C9 EPC_INIT_TO_IDLE_UE_NORM_REL 2.4.1.1
M8013C10 EPC_INIT_TO_IDLE_DETACH 2.4.1.1
M8013C11 EPC_INIT_TO_IDLE_RNL 2.4.2.1
M8013C12 EPC_INIT_TO_IDLE_OTHER 2.4.2.1
M8013C13 ENB_INIT_TO_IDLE_NORM_REL 2.4.1.2
M8013C15 ENB_INIT_TO_IDLE_RNL 2.4.2.2
M8013C16 ENB_INIT_TO_IDLE_OTHER 2.4.2.2
M8018C5 ACT_UE_CONT_REL_INIT_ENB 2.4.2.3
M8018C7 ACT_UE_CONT_REL_INIT_MME 2.4.2.3

LNBTS Message Sequence Charts With PM Counters0 4

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

LNBTS Message Sequence Charts With PM Counters0 4

Diunggah oleh

Hak Cipta:

Format Tersedia

1 (96) LTE PMO LTE MSC with PM Counters

Dr. Martin Kollar Company Confidential

20th September 2012

LTE Message Sequence Charts with PM

Version Date Author Approved by Comments

4.0.0 20.09.2012 Dr. Martin Kollar Bernhard Friedrich

Dr. Martin Kollar Company Confidential

20th September 2012

Dr. Martin Kollar Company Confidential

20th September 2012

2.4.2.2 eNB initiated Transaction to ECM-IDLE............................................................................... 22

Dr. Martin Kollar Company Confidential

20th September 2012

Dr. Martin Kollar Company Confidential

20th September 2012

Dr. Martin Kollar Company Confidential

20th September 2012

5.8.2 Early Type 1 handover......................................................................................................... 87

Dr. Martin Kollar Company Confidential

20th September 2012

1.0.0 17.04.2012 M. Kollar First version for review

2.0.0 12.05.2012 M. Kollar Second version – a note related to PM

A common note related to Path Switch

A note related E-RAB setup counting added

Chapter 2.3.1, typo correction:

Chapter 5.7.1.1 and 5.7.2.1: correction

4.0.0 20.09.2012 M. Kollar

Dr. Martin Kollar Company Confidential

20th September 2012

Chapter 3.3.1, a note related to counters

Chapter 3.3.5, a note related to counters

Chapter 4.5 dealing with E-RAB Setup

Chapter 2.4.1.2 a note added to counter

Chapters 5.2, 5.3: counter

Dr. Martin Kollar Company Confidential

20th September 2012

1. Scope of the Document

1.2 Message Sequence Charts

Dr. Martin Kollar Company Confidential

20th September 2012

2. UE State Handling Procedures

* Updated on the transmission of a RRC Paging message

** Updated for each paging record of a RRC Paging message

Dr. Martin Kollar Company Confidential

20th September 2012

2.2 Random Access Procedure

2.2.1 Contention Based Random Access Procedure

RANDOM ACCESS PREAMBLE

RANDOM ACCESS RESPONSE

Dr. Martin Kollar Company Confidential

20th September 2012

2.2.2 Contention Free Random Access Procedure

2.2.2.1 Contention Free Random Access Procedure for PDCCH Order

RANDOM ACCESS PREAMBLE

** This counter is also updated with PDCCH order transmission repetitions.

Dr. Martin Kollar Company Confidential

20th September 2012

RANDOM ACCESS PREAMBLE

* It is represented by sending RRC Connection Reconfiguration message with included RA-PreambleIndex

UE Source eNB Target eNB

RANDOM ACCESS PREAMBLE

RANDOM ACCESS RESPONSE

* It is represented by sending RRC Connection Reconfiguration message with included RA-PreambleIndex