Documente Academic
Documente Profesional
Documente Cultură
Company Confidential
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
3 (96) LTE PMO LTE MSC with PM Counters
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.1 Successful Procedure .......................................................................................................... 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.1 Successful Procedure .......................................................................................................... 60
4.5.2 Unsuccessful Procedure ...................................................................................................... 61
5. Mobility ........................................................................................................................................... 62
5.1 eNACC to GSM ........................................................................................................................ 62
5 (96) LTE PMO LTE MSC with PM Counters
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.1 Successful Procedure .......................................................................................................... 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.1 Successful Procedure .......................................................................................................... 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.1 Successful Procedure .......................................................................................................... 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
6 (96) LTE PMO LTE MSC with PM Counters
History
Version Date Author Reason for update
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.
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.
10 (96) LTE PMO LTE MSC with PM Counters
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 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.
11 (96) LTE PMO LTE MSC with PM Counters
UE eNB
RACH_STP_ATT_LARGE_MSG
RACH_STP_COMPLETIONS
12 (96) LTE PMO LTE MSC with PM Counters
UE eNB
PDCCH ORDER
PDCCH
PDCCH_INIT_ORDER_ATT*
PDCCH_ORDER_ATT**
RACH_STP_COMPLETIONS
PDCCH_ORDER_SUCCESS
* The counter is updated only for the first (initial) PDCCH order transmitted to UE
2.2.2.2 Contention Free Random Access Procedure for intra eNB Handover
UE eNB
RANDOM ACCESS ASSIGNMENT*
DCCH – Old cell
RACH_STP_COMPLETIONS
2.2.2.3 Contention Free Random Access Procedure for inter eNB Handover
RACH_STP_COMPLETIONS
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
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
15 (96) LTE PMO LTE MSC with PM Counters
UE eNB
SIGN_CONN_ESTAB_ATT_MT*
SIGN_CONN_ESTAB_ATT_MO_D*
SIGN_CONN_ESTAB_ATT_OTHERS *
SIGN_CONN_ESTAB_ATT_EMG*
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
16 (96) LTE PMO LTE MSC with PM Counters
***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.
UE eNB
SIGN_CONN_ESTAB_ATT_MT
DSIGN_CONN_ESTAB_ATT_MO_D
SIGN_CONN_ESTAB_ATT_OTHERS
SIGN_CONN_ESTAB_ATT_EMG
SIGN_EST_F_RRCCOMPL_MISSING
17 (96) LTE PMO LTE MSC with PM Counters
UE eNB
SIGN_CONN_ESTAB_ATT_MT
DSIGN_CONN_ESTAB_ATT_MO_D
SIGN_CONN_ESTAB_ATT_OTHERS
SIGN_CONN_ESTAB_ATT_EMG
SIGN_EST_F_RRCCOMPL_ERROR
18 (96) LTE PMO LTE MSC with PM Counters
UE eNB
SIGN_CONN_ESTAB_ATT_MT
DSIGN_CONN_ESTAB_ATT_MO_D
SIGN_CONN_ESTAB_ATT_OTHERS
SIGN_CONN_ESTAB_ATT_EMG
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
19 (96) LTE PMO LTE MSC with PM Counters
UE in Trigger to initiate
RRC-CONNECTED release
:
S1AP: UE Context Release
Command
CELL_LOAD_ACT_UE_AVG (stop)
CELL_LOAD_ACT_UE_MAX
S1AP: UE Context Release
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
20 (96) LTE PMO LTE MSC with PM Counters
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)
CELL_LOAD_ACT_UE_MAX
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_AVG(stop)
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.
21 (96) LTE PMO LTE MSC with PM Counters
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
CELL_LOAD_ACT_UE_AVG(stop)
CELL_LOAD_ACT_UE_MAX
S1AP: UE Context Release
Complete
L2 ACK
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
22 (96) LTE PMO LTE MSC with PM Counters
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
CELL_LOAD_ACT_UE_AVG(stop)
CELL_LOAD_ACT_UE_MAX
S1AP: UE Context Release Complete
L2 ACK
Set UE to Set UE to
Release all UE related ECM-IDLE
RRC-IDLE resources,
remove UE context
RRC_CONN_UE_AVG(stop)
RRC_CONN_UE_MAX
23 (96) LTE PMO LTE MSC with PM Counters
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
CELL_LOAD_ACT_UE_AVG(stop)
CELL_LOAD_ACT_UE_MAX
L2 ACK
Release all UE related
Set UE to resources,
RRC-IDLE remove UE context
RRC_CONN_UE_AVG(stop)
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]).
UE_DRB_DL_DATA_QCI_2
UE_DRB_DL_DATA_QCI_3
UE_DRB_DL_DATA_QCI_4
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.
25 (96) LTE PMO LTE MSC with PM Counters
UE Serving/Source/Target eNB
Reestablishment
Trigger
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
Delete resources of
old C-RNTI
26 (96) LTE PMO LTE MSC with PM Counters
UE Serving/Source/Target eNB
Reestablishment
Trigger
RRC: RRCConnectionReestablishmentReque
st
CCCH
RRC_CON_RE_ESTAB_ATT*
RRC_CON_RE_ESTAB_ATT_HO_FAIL**
RRC_CON_RE_ESTAB_ATT_OTH**
REJ_RRC_CONN_RE_ESTAB*
1. *The counters are triggered for all the possible causes within the RRC CONNECTION REESTABLISHMENT
REQUEST
27 (96) LTE PMO LTE MSC with PM Counters
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.
28 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
EPS_BEARER_STP_ATT_INI_QCI1*
EPS_BEARER_STP_ATT_INI_QCI_2*
EPS_BEARER_STP_ATT_INI_QCI_3*
EPS_BEARER_STP_ATT_INI_QCI_4*
EPS_BEAR_STP_ATT_INI_NON_GBR*
EPS_BEARER_SETUP_COMPLETIONS
EPS_BEARER_STP_COM_INI_QCI1*
EPS_BEARER_STP_COM_INI_QCI_2*
EPS_BEARER_STP_COM_INI_QCI_3*
EPS_BEARER_STP_COM_INI_QCI_4*
EPS_BEAR_STP_COM_INI_NON_GBR*
* The counters are triggered on a per QCI basis (QCI1-4 and non GBR bearers).
29 (96) LTE PMO LTE MSC with PM Counters
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.
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
EPS_BEARER_STP_ATT_INI_QCI1
EPS_BEARER_STP_ATT_INI_QCI_2
EPS_BEARER_STP_ATT_INI_QCI_3
EPS_BEARER_STP_ATT_INI_QCI_4
EPS_BEAR_STP_ATT_INI_NON_GBR
Security Establishment
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.
30 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
EPS_BEARER_STP_ATT_ADD_QCI_1*
EPS_BEARER_STP_ATT_ADD_QCI_2*
EPS_BEARER_STP_ATT_ADD_QCI_3*
EPS_BEARER_STP_ATT_ADD_QCI_4*
E_RAB_SETUP_ATT_EMG**
EPS_BEAR_SET_COM_ADDIT_QCI1*
EPS_BEARER_STP_COM_ADD_QCI_2*
EPS_BEARER_STP_COM_ADD_QCI_3*
EPS_BEARER_STP_COM_ADD_QCI_4*
E_RAB_SETUP_SUCC_EMG**
**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.
31 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
EPS_BEARER_STP_ATT_ADD_QCI_1
EPS_BEARER_STP_ATT_ADD_QCI_2
EPS_BEARER_STP_ATT_ADD_QCI_3
EPS_BEARER_STP_ATT_ADD_QCI_4
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.
32 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
DATA_RB_STP_COMP
CELL_LOAD_ACT_UE_AVG(start)
CELL_LOAD_ACT_UE_MAX
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.
34 (96) LTE PMO LTE MSC with PM Counters
Source Target
UE
eNB eNB
Measurement Reports
DCCH
old cell
Handover Request
Start Tx2Relocexec
Contention Free
Stop Tx2Relocexec
Random Access Procedure (see chapter 2.2.2.2)
Measurement Reports
DCCH
old cell
Handover Required
Handover Request
Start TS1Relocexec
Handover Request
Acknowledge
DATA_RB_STP_ATT
Handover Command
Contention Free
Random Access Procedure (see chapter 2.2.2.2)
Stop TS1Relocexec
RRC Connection Reconfiguration Complete
DCCH
new cell DATA_RB_STP_COMP
CELL_LOAD_ACT_UE_MAX
CELL_LOAD_ACT_UE_AVG(start)
RRC_CONN_UE_AVG(start)
RRC_CONN_UE_MAX
1 It should be noted that the message flow chart is simplified and some synchronization messages used during
the handover are excluded.
37 (96) LTE PMO LTE MSC with PM Counters
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)”.
UE eNB MME
RRC: RRCConnectionReconfiguration
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
RRC: RRCConnectionReconfigurationComplete
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
38 (96) LTE PMO LTE MSC with PM Counters
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).
Source Target
UE
eNB eNB
Measurement Reports
DCCH
old cell
Handover Request
Start Tx2Relocexec
Contention Free
Random Access Procedure (see chapter 2.2.2.2)
DATA_RB_STP_FAIL
Note: It should be noted that the message flow chart is simplified and some synchronization messages used during
the handover are excluded.
39 (96) LTE PMO LTE MSC with PM Counters
Measurement Reports
DCCH
old cell
Handover Required
Handover Request
Start TS1Relocexec
Handover Request
Acknowledge
DATA_RB_STP_ATT
Handover Command
Contention Free
Random Access Procedure (see chapter 2.2.2.2)
DATA_RB_STP_FAIL
40 (96) LTE PMO LTE MSC with PM Counters
Note: It should be noted that the message flow chart is simplified and some synchronization messages used during
the handover are excluded.
UE eNB MME
ENB_EPS_BEARER_REL_REQ_NORM
ENB_EPS_BEAR_REL_REQ_N_QCI1
PRE_EMPT_GBR_BEARER*
PRE_EMPT_NON_GBR_BEARER*
RRC: RRCConnectionReconfiguration
DCCH
RRC: RRCConnectionReconfigurationComplete
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.
42 (96) LTE PMO LTE MSC with PM Counters
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
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
43 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
EPC_EPS_BEARER_REL_REQ_NORM
EPC_EPS_BEARER_REL_REQ_N_QCI1
RRC: RRCConnectionReconfiguration
DCCH
RRC: RRCConnectionReconfigurationComplete
DCCH
S1AP: E-RAB RELEASE RESPONSE
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
44 (96) LTE PMO LTE MSC with PM Counters
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
RRC: RRCConnectionReconfiguration
DCCH
RRC: RRCConnectionReconfigurationComplete
DCCH S1AP: E-RAB RELEASE RESPONSE
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
45 (96) LTE PMO LTE MSC with PM Counters
3.3.5 Normal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state)
UE eNB MME S-GW
ENB_EPSBEAR_REL_REQ_RNL_REDIR
PRE_EMPT_NON_GBR_BEARER*
PRE_EMPT_GBR_BEARER*
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_T_QCI1
ENB_EPS_BEARER_REL_REQ_O_QCI1
3.3.7 Normal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state)
UE eNB MME S-GW
S1AP: UE Context Release
UE in Command
RRC-CONNECTED
:
EPC_EPS_BEARER_REL_REQ_NORM
EPC_EPS_BEARER_REL_REQ_DETACH
S11 interaction to release the UE
EPC_EPS_BEARER_REL_REQ_N_QCI1 and its bearer
EPC_EPS_BEARER_REL_REQ_D_QCI1
EPC_EPS_BEARER_REL_REQ_OTH
S11 interaction to release the UE
and its bearer
EPC_EPS_BEARER_REL_REQ_R_QCI1
EPC_EPS_BEARER_REL_REQ_O_QCI1
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.
49 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
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.
50 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
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.
51 (96) LTE PMO LTE MSC with PM Counters
eNB MME
UE_CONTEXT_MOD_ATT_AMBR
UE_CONTEXT_MOD_ATT_CSFB
S1AP: UE CONTEXT MODIFICATION RESPONSE
eNB MME
UE_CONTEXT_MOD_ATT_AMBR
UE_CONTEXT_MOD_ATT_CSFB
S1AP: UE CONTEXT MODIFICATION FAILURE
UE_CONTEXT_MOD_FAIL
UE eNB MME
INI_CONT_STP_REQ
UE eNB MME
INI_CONT_STP_REQ
Security Establishment
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.
54 (96) LTE PMO LTE MSC with PM Counters
4.2 S1 Setup
eNB MME
Start an O&M Timer
S1AP: S1 SETUP REQUEST
S1_SETUP_ATT
S1_SETUP_SUCC
eNB MME
Start an O&M Timer
S1AP: S1 SETUP REQUEST
S1_SETUP_ATT
S1_SETUP_FAIL_NO_RESP
55 (96) LTE PMO LTE MSC with PM Counters
eNB MME
Start an O&M Timer
S1AP: S1 SETUP REQUEST
S1_SETUP_ATT
S1_SETUP_FAIL_IND_BY_MME
4.3 S1 Reset
eNB MME
Start TimerS1ResetWaitForResponse
S1AP: S1 RESET*
S1AP_PARTIAL_RESET_INIT_ENB
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.
56 (96) LTE PMO LTE MSC with PM Counters
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.
57 (96) LTE PMO LTE MSC with PM Counters
eNB MME
Start a Supervision Wait Timer in MME
S1AP: S1 RESET*
S1AP_PARTIAL_RESET_INIT_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.
58 (96) LTE PMO LTE MSC with PM Counters
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.
59 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
*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.
60 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
E_RAB_SETUP_ATT
UE eNB MME
E_RAB_SETUP_ATT
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.
62 (96) LTE PMO LTE MSC with PM Counters
5. Mobility
5.1 eNACC to GSM
Source
UE MME S-GW
eNB
1. Decision to perform
eNACC to GSM
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
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.
63 (96) LTE PMO LTE MSC with PM Counters
UE eNB MME
RRC: ULInformationTransfer
(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)
UE_CONTEXT_MOD_ATT_CSFB
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
ENB_INIT_TO_IDLE_NORM_REL*
L2ACK S1AP: UE CONTEXT RELEASE COMMAND
UE eNB MME
UE Capabilities E-
UTRA not available
RRC: UECapabilityEnquiry
RRC: UECapabilityInformation
(UE capabilities E-UTRA )
Selection of redirect
target
CSFB_REDIR_CR_EMERGENCY_ATT
Set UE to
Delete Bearer
ECM-IDLE
** 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.
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.
66 (96) LTE PMO LTE MSC with PM Counters
UE eNB
UL allocation
2. Measurement Reports
3. HO Decision**
Start THOoverall
INTRA_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
Handover Execution
HO_EMG_ATT
RB_REL_REQ_NORM_REL*
ENB_EPS_BEARER_REL_REQ_NORM
ENB_INIT_TO_IDLE_NORM_REL
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_SUCC)
HO_EMG_SUCC
HO_DRX_SUCC
Packet data
67 (96) LTE PMO LTE MSC with PM Counters
Notes:
UE eNB
UL allocation
2. Measurement Reports
3. HO Decision
Start THOoverall
INTRA_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
FAIL_ENB_HO_PREP_OTH
HO_EMG_PREP_FAIL
68 (96) LTE PMO LTE MSC with PM Counters
UE eNB
UL allocation
2. Measurement Reports
3. HO Decision
Start THOoverall
INTRA_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
Handover Execution
ATT_INTRA_ENB_HO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
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.
69 (96) LTE PMO LTE MSC with PM Counters
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
5. Admission Control and
Resource Allocation
Stop TX2RELOCprep
Start TX2RELOCOverall 6. Handover Request
Acknowledge Start TX2RELOCexec
ATT_INTER_ENB_HO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
Handover Execution
HO_DRX_ATT
DL allocation
7.RRC Connection Reconfiguration
8. SN Status Transfer
Data Forwarding
Detach from old cell
Buffer Packets from
Source eNB
9. Synchronisation
See chapter 2.2.2.2
10. UL allocation + TA for UE
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
Acknowledge
Release X2
SUCC_INTER_ENB_HO
Signalling
Connection
RB_REL_REQ_NORM_REL*
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_SUCC)
HO_EMG_SUCC
HO_DRX_SUCC
Data Forwarding
End Marker
Packet data Packet data
Note: *See chapter 3.4.1. In relation to points 6 and 11 see also chapter 3.2.2.
70 (96) LTE PMO LTE MSC with PM Counters
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP 5. Admission Control and
Resource Allocation
6. Handover Request
Acknowledge
Expiry TX2RELOCprep
FAIL_ENB_HO_PREP_TIME
HO_EMG_PREP_FAIL
71 (96) LTE PMO LTE MSC with PM Counters
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP
Handover Preparation
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
72 (96) LTE PMO LTE MSC with PM Counters
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
5. Admission Control and
Resource Allocation
Stop TX2RELOCprep
Start TX2RELOCOverall 6. Handover Request
Acknowledge Start TX2RELOCexec
ATT_INTER_ENB_HO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
Handover Execution
HO_DRX_ATT
DL allocation
7.RRC Connection Reconfiguration 8. SN Status Transfer
Data Forwarding
Detach from old cell
Buffer Packets from
Source eNB
9. Synchronisation
See chapter 2.2.2.2
10. UL allocation + TA for UE
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
Expiry TX2RELOCOverall
INTER_ENB_HO_FAIL
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.
74 (96) LTE PMO LTE MSC with PM Counters
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP
Handover Preparation
6. Handover Request
INTER_ENB_S1_HO_ATT
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
HO_DRX_ATT
Handover Execution
12.RRC Connection Reconfiguration 13a. eNB Status Transfer
13b. MME Status Transfer
Detach from old cell
(Indirect) Data Forwarding
Begin sending
fresh S1-U data
Handover Completion
RB_REL_REQ_NORM_REL*
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_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
75 (96) LTE PMO LTE MSC with PM Counters
Notes:
3. HO Decision
4. Handover Required
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP
HO_EMG_PREP
5. HO preparation in EPC
Handover Preparation
6. Handover Request
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
76 (96) LTE PMO LTE MSC with PM Counters
3. HO Decision
4. Handover Required
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP
HO_EMG_PREP
5. HO preparation in EPC
Handover Preparation
6. Handover Request
INTER_S1_HO_PREP_FAIL_NORR
INTER_S1_HO_PREP_FAIL_OTHER
77 (96) LTE PMO LTE MSC with PM Counters
3. HO Decision
4. Handover Required
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP
5. HO preparation in EPC
HO_EMG_PREP
Handover Preparation
6. Handover Request
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
HO_DRX_ATT
Handover Execution
12.RRC Connection Reconfiguration 13a. eNB Status Transfer
13b. MME Status Transfer
Detach from old cell
(Indirect) Data Forwarding
Begin sending
fresh S1-U data
Expiry TS1RELOCOverall
INTER_ENB_S1_HO_FAIL
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).
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.
79 (96) LTE PMO LTE MSC with PM Counters
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
· Map EPS bearers to PDP contexts
Handover Preparation
· 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
CSFB_PSHO_UTRAN_ATT
to new cell
Downlink Data
Uplink Data
ISYS_HO_UTRAN_SRVCC_SUCC
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.
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
·
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)
ISYS_HO_PREP_FAIL_TIM
81 (96) LTE PMO LTE MSC with PM Counters
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
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
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
82 (96) LTE PMO LTE MSC with PM Counters
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
· Map EPS bearers to PDP contexts
Handover Preparation
· 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
CSFB_PSHO_UTRAN_ATT
Downlink Data
Uplink Data
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
83 (96) LTE PMO LTE MSC with PM Counters
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
84 (96) LTE PMO LTE MSC with PM Counters
Source Target
UE MME S-GW SGSN P-GW
eNB BSS
1. Decision to perform
SRVCC to GSM
2. S1AP:HANDOVER REQUIRED
Start TS1RELOCprep
Handover Preparation
3. Handover Preparation
Stop TS1RELOCprep
4. S1AP:HANDOVER COMMAND
Start TS1RELOCoverall
Handover Execution
ISYS_HO_GERAN_SRVCC_ATT
Handover Completion
UL & DL Payload PDUs
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.
85 (96) LTE PMO LTE MSC with PM Counters
Source Target
UE MME S-GW SGSN P-GW
eNB BSS
1. Decision to perform
SRVCC to GSM
2. S1AP:HANDOVER REQUIRED
Start TS1RELOCprep
Handover Preparation
3. Handover Preparation
Stop TS1RELOCprep
4. S1AP:HANDOVER COMMAND
Start TS1RELOCoverall
Handover Execution
ISYS_HO_GERAN_SRVCC_ATT
Handover Completion
UL & DL Payload PDUs
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
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
86 (96) LTE PMO LTE MSC with PM Counters
· 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
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
87 (96) LTE PMO LTE MSC with PM Counters
· 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)
MRO_EARLY_TYPE1_HO
MRO_EARLY_TYPE1_HO_NB
88 (96) LTE PMO LTE MSC with PM Counters
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
89 (96) LTE PMO LTE MSC with PM Counters
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.
90 (96) LTE PMO LTE MSC with PM Counters
Initiating Responding
eNB eNB
X2_SETUP_ATT
Initiating Responding
eNB eNB
X2_SETUP_ATT
X2_SETUP_FAIL
91 (96) LTE PMO LTE MSC with PM Counters
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
8. Appendix
8.1 List of E-UTRAN PM Counters