LTE

1 (180) LTE PMO LTE MSC with PM Counters
Dr. Martin Kollar Company Confidential
02 February 2016
LTE Message Sequence Charts with PM

Counters for RL70/55TD
Company Confidential
Version Date Author Approved by Comments
1.0 02.02.2016 Pawel Gradowski Krzysztof Tatarczyk

02 February 2016
Table of Contents
History ....................................................................................................................................................... 9
Changes Compared to RL60 .................................................................................................................... 10
Changes Compared to the Latest Version 1.0 of the Specification for RL50 .......................................... 12
1. Scope of the Document ...................................................................................................................... 13
1.1 Introduction ................................................................................................................................ 13
1.2 Message Sequence Charts .......................................................................................................... 13
2. UE State Handling Procedures ................................................................................................................ 14
2.1 Paging Procedure .............................................................................................................................. 14
2.2 Random Access Procedure................................................................................................................ 15
2.2.1 Contention Based Random Access Procedure ........................................................................... 15
2.2.2 Contention Free Random Access Procedure ............................................................................. 16
2.2.2.1 Contention Free Random Access Procedure for PDCCH Order .......................................... 16
2.2.2.2 Contention Free Random Access Procedure for intra eNB Handover ................................ 17
2.2.2.3 Contention Free Random Access Procedure for inter eNB Handover ................................ 17
2.2.2.4 Unsuccessful Contention Free Random Access Procedure Due to Lack of Preamble
Resources ........................................................................................................................................ 18
2.3 RRC Connection Establishment ......................................................................................................... 19
2.3.1 Successful RRC Connection Establishment ................................................................................ 19
2.3.2 Unsuccessful RRC Connection Establishment ( RRC CONNECTION COMPLETE Missing) .......... 21
2.3.4 Unsuccessful RRC Connection Establishment (Completions Error in RRC CONNECTION
COMPLETE).......................................................................................................................................... 22
2.3.5 Unsuccessful RRC Connection Establishment (Rejection by eNB) ............................................. 23
2.4 Transaction to ECM-Idle (Signalling Connection Release) ................................................................ 25
2.4.1 Normal procedure ...................................................................................................................... 25
2.4.1.1 MME initiated Transaction to ECM-Idle state..................................................................... 25
2.4.1.2 eNB initiated Transition to ECM-IDLE ................................................................................ 26
2.4.2 Abnormal procedure .................................................................................................................. 27
02 February 2016
2.4.2.1 MME initiated Transaction to ECM-Idle state..................................................................... 27

2.4.2.2 eNB initiated Transaction to ECM-IDLE............................................................................... 28
2.4.2.3 Transaction to ECM-Idle State Due to Reset on S1 ............................................................. 29
2.5 RRC Connection Re-establishment ................................................................................................... 32
2.5.1 RRC Connection Re-establishment (Successful procedure) ........................................................... 32
2.5.2 RRC Connection Re-establishment (Unsuccessful procedure)..................................................... 33
2.5.3 RRC Connection Re-establishment to other eNB (RLF triggered Handover) Successful procedure
................................................................................................................................................................ 34
2.5.4 RRC Connection Re-establishment to other eNB (RLF triggered Handover) Unsuccessful
procedure due to expiry of T301guard in requested eNB ...................................................................... 35
3. Bearer Management Procedures ............................................................................................................ 37
3.1 E-RAB Bearer Establishment ............................................................................................................. 37
3.1.1 Successful Initial E-RAB Establishment via Initial Context Setup ............................................... 37
3.1.2 Unsuccessful Initial E-RAB Establishment via Initial Context Setup........................................... 38
3.1.3 Additional E-RAB Establishment (Successful Procedure) ........................................................... 39
3.1.4 Additional E-RAB Establishment (Unsuccessful Procedure) ...................................................... 40
3.2 Data Radio Bearer (DRB) Establishment ........................................................................................... 42
3.2.1 Successful Procedure (DRB establishment done in parallel with E-RAB establishment or intra
eNB handover) .................................................................................................................................... 42
3.2.2 Successful Procedure (DRB establishment done during X2 based inter eNB handover)........... 44
3.2.3 Successful Procedure (DRB establishment done during S1 based inter eNB handover) ........... 45
3.2.4 Unsuccessful Procedure (DRB establishment done in parallel with E-RAB establishment or
intra eNB handover)............................................................................................................................ 46
3.2.5 Unsuccessful Procedure (DRB establishment done during X2 based inter eNB handover) ...... 47
3.2.6 Unsuccessful Procedure (DRB establishment done during S1 based inter eNB handover) ...... 48
3.3 E-RAB Release ................................................................................................................................... 49
3.3.1 Normal E-RAB Release Initiated by eNB (UE stays in ECM-CONNECTED state) ......................... 49
3.3.2 Abnormal E-RAB Release Initiated by eNB (UE stays in ECM-CONNECTED state) ..................... 50
3.3.3 Normal E-RAB Release Initiated by MME (UE stays in ECM-CONNECTED state)....................... 51
02 February 2016
3.3.4 Abnormal E-RAB Release Initiated by MME (UE stays in ECM-CONNECTED state) ................... 52
3.3.5 Normal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state) ................................... 53
3.3.6 Abnormal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state) ............................... 54
3.3.6 Normal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state) ................................. 55
3.3.7 Abnormal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state) ............................. 56
3.4 DRB Release ..................................................................................................................................... 57
3.4.1 Normal DRB Release .................................................................................................................. 57
3.4.2 Abnormal DRB Release .............................................................................................................. 58
3.5 UE Context Modification ................................................................................................................... 59
3.5.1 S1AP UE Context Modification (Successful procedure) ............................................................. 59
3.6 E-RAB Modification ........................................................................................................................... 61
3.6.1 E-RAB Modification (Successful procedure) .............................................................................. 61
E-RAB Modification (Unsuccessful procedure) .................................................................................. 62
4. S1AP Related Procedures ........................................................................................................................ 63
4.1 Initial Context Setup .................................................................................................. 63
4.1.1 Successful Procedure ................................................................................................................. 63
4.1.2 Unsuccessful Procedure ............................................................................................................. 64
4.2 S1 Setup ............................................................................................................................................ 65
4.2.2 Unsuccessful Procedure (No response) ..................................................................................... 65
4.2.3 Unsuccessful Procedure (MME Failure) ..................................................................................... 66
4.3 S1 Reset ............................................................................................................................................. 66
4.3.1 S1 Partial Reset Initiated by eNB (Successful Procedure) .......................................................... 66
4.3.2 S1 Partial Reset Initiated by eNB (Unsuccessful Procedure)...................................................... 67
4.3.3 S1 Partial Reset Initiated by MME (Successful Procedure) ........................................................ 68
4.3.4 S1 Partial Reset Initiated by MME (Unsuccessful Procedure) ................................................... 69
4.4 S1 UE Associated Logical S1 Connection Establishment ................................................................... 70
4.5 Additional E-RAB Setup ..................................................................................................................... 71
02 February 2016

4.5.2 Unsuccessful Procedure ............................................................................................................. 72
4.6 S1AP Procedures Related to ETWS and CMAS .................................................................................. 73
4.6.1 WRITE-REPLACE WARNING REQUEST (Successful Procedure) .................................................. 73
4.6.2 KILL- REQUEST (Successful Procedure) ...................................................................................... 73
4.6.3 WRITE-REPLACE WARNING REQUEST (Unsuccessful Procedure) .............................................. 74
4.6.4 KILL- REQUEST (Unsuccessful Procedure) .................................................................................. 74
5.Mobility .................................................................................................................................................... 75
5.1 eNACC to GSM .................................................................................................................................. 75
5.2 CS Fallback to UTRAN, CDMA/1xRTT or GSM via RRC Connection Release (UE in Connected Mode)
................................................................................................................................................................ 76
5.3 CS Fallback to UTRAN, CDMA/1xRTT or GSM via RRC Connection Release (UE in Idle Mode) ........ 77
5.4 Intra eNB Handover .......................................................................................................................... 79
5.4.2 Unsuccessful Procedure (HO Preparation failure) ..................................................................... 81
5.4.3 Unsuccessful Procedure (HO Execution failure) ........................................................................ 82
5.5 Inter eNB X2 Based Handover ........................................................................................................... 83
5.5.2 Unsuccessful Procedure (HO Preparation Failure -Time cause) ................................................ 84
5.5.3 Unsuccessful Procedure (HO Preparation Failure –AC or OTHER cause) .................................. 85
5.5.4 Unsuccessful Procedure (HO Execution or Completion Failure)................................................ 86
5.6 Inter eNB S1 Based Handover ........................................................................................................... 88
5.6.2 Unsuccessful Procedure (HO Preparation Failure -Time cause) ................................................ 89
5.6.3 Unsuccessful Procedure (HO Preparation Failure - Resource or OTHER cause) ........................ 90
5.6.4 Unsuccessful Procedure (HO Execution or Completion Failure)................................................ 91
5.7 Inter RAT Handover........................................................................................................................... 93
5.7.1 Handover from LTE to UTRAN.................................................................................................... 93
02 February 2016
5.7.1.1 Successful Procedure .......................................................................................................... 93

5.7.1.2 Unsuccessful Procedure (Handover Preparation Failure – Time cause)............................. 94
5.7.1.3 Unsuccessful Procedure (Handover Preparation Failure – AC or OTHER cause) ................ 95
5.7.1.4 Unsuccessful Procedure (Handover Execution or Completion Failure) .............................. 96
5.7.2 Handover from LTE to GERAN.................................................................................................... 98
5.7.2.1 Successful Procedure .......................................................................................................... 98
5.7.2.2 Unsuccessful Procedure (Handover Execution or Completion Failure) .............................. 99
5.8 Mobility Robustness Optimization Features................................................................................... 101
5.8.1 Late handover .......................................................................................................................... 101
5.8.2 Early Type 1 handover.............................................................................................................. 102
5.7.3 Early Type 2 handover.............................................................................................................. 103
5.9 Mobility to Home eNB .................................................................................................................... 104
5.10 Mobility from LTE to eHRPD ......................................................................................................... 105
5.10.1 Successful HO Preparation from LTE to eHRPD ..................................................................... 105
5.10.2 Unsuccessful HO Preparation from LTE to eHRPD due to TUlHoPrepTransferHrpd Timer
expiry................................................................................................................................................. 106
5.10.3 Unsuccessful HO Preparation from LTE to eHRPD due to TC2KRelocPrepHrpd Timer expiry
.......................................................................................................................................................... 107
5.10.4 Unsuccessful HO Preparation from LTE to eHRPD caused by received HO Failure indication
message ............................................................................................................................................ 108
5.10.5 Successful HO Completion from LTE to eHRPD ..................................................................... 109
5.10.5 Unsuccessful HO from LTE to eHRPD (Handover Execution or Completion Failure) ............. 110
6. X2AP Related Procedures ................................................................................................................. 111
6.1 X2 Setup (Successful Procedure) .................................................................................................... 111
6.2 X2 Setup (Unsuccessful Procedure) ................................................................................................ 111
6.3 X2 IP Address Retrieval (Successful Procedure).............................................................................. 111
7. ANR for UTRAN ................................................................................................................................. 112
7.1 Successful Procedure ...................................................................................................................... 112
7.2 Unsuccessful Procedure .................................................................................................................. 112
02 February 2016
8. ANR for E-UTRAN .............................................................................................................................. 113

8.1 Successful Procedure ...................................................................................................................... 113
9. CA Related Procedures ..................................................................................................................... 114
9.1 SCell Addition/Configuration .......................................................................................................... 114
9.2 SCell Release ................................................................................................................................... 115
10. TTI Bundling Related Procedures .................................................................................................. 116
10.1 TTI Bundling Start .......................................................................................................................... 116
10.2 TTI Bundling Stop .......................................................................................................................... 117
11. U Plane E-UTRAN PM Counters..................................................................................................... 119
11.1 PDCP SDU Delay in DL ............................................................................................................... 119
11.1.1 Retention Delay within the eNB in DL............................................................................... 119
11.1.2 PDCP SDU HARQ Loop Delay Measurement in DL ............................................................ 120
11.2 PDCP SDU Delay in UL ............................................................................................................... 122
11.2.1 Retention Delay within the eNB in UL .............................................................................. 122
11.3 RLC PDU Transmission and Re-transmission............................................................................. 123
11.3.1 RLC PDU Transmission and Re-transmission in DL............................................................ 123
11.3.2 RLC PDU Transmission and Re-transmission in UL............................................................ 124
11.4 MAC PDU Transmission and Re-transmission in DL .................................................................. 125
11.5 RSSI Measurements per UE ...................................................................................................... 127
11.5.1 RSSI Measurements per UE for PUCCH............................................................................. 127
11.5.2 RSSI Measurements per UE for PUSCH ............................................................................. 127
11.6 SINR Measurements per UE ...................................................................................................... 128
11.6.1 SINR Measurements per UE for PUCCH ............................................................................ 128
11.6.2 SINR Measurements per UE for PUSCH ............................................................................ 129
11.7 RSSI Measurements per Cell ..................................................................................................... 130
11.7.1 RSSI Measurements per cell for PUCCH............................................................................ 130
11.7.2 RSSI Measurements per cell for PUSCH ............................................................................ 131
11.8 SINR Measurements per Cell .................................................................................................... 133
02 February 2016
11.8.1 SINR Measurements per Cell for PUCCH .......................................................................... 133

11.8.2 SINR Measurements per Cell for PUSCH ........................................................................... 133
11.9 PDCP SDU Volume Measurements ........................................................................................... 135
11.9.1 PDCP SDU Volume in DL .................................................................................................... 135
11.9.2 PDCP SDU Volume in UL.................................................................................................... 137
11.10 RLC Volume Measurements .................................................................................................. 137
11.10.1 RLC PDU Volume in DL .................................................................................................. 137
11.10.2 RLC PDU Volume in UL .................................................................................................. 139
11.10.3 RLC SDU Volume in DL .................................................................................................. 140
11.10.4 RLC SDU Volume in UL .................................................................................................. 141
11.11 Number of PDCP SDUs Measurement .................................................................................. 142
11.11.1 Number of Transmitted PDCP SDUs in DL .................................................................... 142
11.11.2 Number of Lost PDCP SDUs in DL.................................................................................. 143
11.11.3 Number of Discarded PDCP SDUs in DL ........................................................................ 144
11.11.4 Number of Transmitted PDCP SDUs in UL .................................................................... 145
11.11.5 Number of Lost PDCP SDUs in UL ................................................................................. 146
11.12 CQI Measurement ................................................................................................................. 147
11.12.1 CQI Distribution Measurement ..................................................................................... 147
11.12.2 CQI Offset Measurement .............................................................................................. 148
11.13 PRB Measurement ................................................................................................................ 149
11.13.1 PRB Measurement in DL ............................................................................................... 149
11.13.2 PRB Measurement in UL ............................................................................................... 150
11.14 Active UEs with Data in the Buffer Measurement ................................................................ 154
11.14.1 Active UEs with Data in the Buffer Measurement in DL ............................................... 154
11.14.2 Active UEs with Data in the Buffer Measurement in UL ............................................... 154
11.15 Active Scheduled UEs Measurement .................................................................................... 158
11.15.1 Active Scheduled UEs Measurement in DL ................................................................... 158
11.15.2 Active Scheduled UEs Measurement in UL ................................................................... 159
02 February 2016
11.16 Active UEs with Activated SCell(s) Measurement ...................................................................... 160

11.17 End User Throughput Measurement .......................................................................................... 160
IP Scheduled Throughput Measurement in DL ............................................................................. 160
IP Scheduled Throughput Measurement in UL ............................................................................. 161
IP Throughput Measurement in DL ............................................................................................... 162
IP Throughput Measurement in UL............................................................................................... 162
11.18 Active Cell Time Measurement ................................................................................................... 163
Active Cell Time Measurement in DL ................................................................................................ 163
Active Cell Time Measurement in UL ................................................................................................ 164
11.19 Interference Shaping Related Measurements ............................................................................ 165
12. References .................................................................................................................................... 167
13. Appendix ....................................................................................................................................... 168
List of the Trigger Events Related to DRB and E-RAB Release Counters............................................... 168
List of the Trigger Events Related to eNB initiated DRB and E-RAB Release Counters......................... 168
List of the Trigger Events Related to EPC initiated DRB and E-RAB Release Counters ......................... 178
History
Version Date Author Reason for update
0.1 21.01.2016 Pawel Gradowski First version for review
1.0 02.02.2016 Pawel Gradowski Comments received during the review

were incorporated. Approved version 1.0.
02 February 2016
Changes Compared to RL60
2.3 RRC Connection Establishment
Updates due to RACH_MSG3_CONTENTION, RRC_CON_STP_TIM_MEAN and RRC_CON_STP_TIM_MAX
2.5 RRC Connection Re-establishment
Updates due to RACH_MSG3_CONTENTION.
2.5.3 RRC Connection Re-establishment to other eNB (RLF triggered Handover) Successful procedure
New chapter added
2.5.4 RRC Connection Re-establishment to other eNB (RLF triggered Handover) Unsuccessful
procedure due to expiry of T301guard in requested eNB
New chapter added.
3.1 E-RAB Bearer Establishment
Chapter modified and new ERAB counters included
Sum of simultaneous E-RABs of QCIs information added as a note
Mean and Maximum E-RAB setup time information added as a note
3.5 UE Context Modification
Chapter modified. New counters added, obsolete removed.
3.5.2 S1AP UE Context Modification (Unsuccessful procedure)
Chapter removed due to removal of UE_CONTEXT_MOD_FAIL counter
3.6 E-RAB Modification
New chapter added
4.1 Initial Context Setup

02 February 2016
4.4 S1 UE Associated Logical S1 Connection Establishment
4.6.3 WRITE-REPLACE WARNING REQUEST (Unsuccessful Procedure)
New chapter added
4.6.4 KILL- REQUEST (Unsuccessful Procedure)
New chapter added
5.4 Intra eNB Handover
Chapter modified due to Incoming HO counters and Service Based Handover counters.
5.5 Inter eNB X2 Based Handover
5.6 Inter eNB S1 Based Handover
5.7 Inter RAT Handover
Chapter modified due to Incoming HO counters.
9. CA Related Procedures
Chapter modified due to 3CC DL CA.
11.11.1 Retention Delay within the eNB in DL
PDCP_SDU_DELAY_DL_DTCH_MEAN added
11.12.1 CQI Distribution Measurement
Notes modified.
11.13.1 PRB Measurement in DL

02 February 2016
Chapter modified due to eICIC.
11.13.2 PRB Measurement in UL
Chapter modified due to eICIC.
11.14 Active UEs with Data in the Buffer Measurement
Flowcharts modified.
11.16 Active UEs with Activated SCell(s) Measurement
Chapter modified due to 3CC DL CA.
11.19 Interference Shaping Related Measurements
New chapter added

02 February 2016
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 U – plane PM counters that are not triggered with any external messages but internally
within the eNB are part of chapter 11 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 12.
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.
Functionality of the U – plane PM counters is presented via flow chart diagrams where it applies.
02 February 2016
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***
RRC_PAGING_ETWS_CMAS
* 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.
02 February 2016
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
02 February 2016
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.

02 February 2016
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
02 February 2016
* It is represented by sending RRC Connection Reconfiguration message with included RA-PreambleIndex
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
3. RACH_STP_ATT_DEDICATED counter is triggered for both genuine and false dedicated preambles. There
might be such a situation that eNB allocated a dedicated preamble for the UE and send it to UE which
later receives two exactly the same preambles with different time delay, where one of them is valid while
the other one is false.
02 February 2016
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_DEL_TOL *
SIGN_CONN_ESTAB_ATT_HIPRIO *
SIGN_CONN_ESTAB_ATT_EMG *
RACH_MSG3_CONTENTION ****
RRC CONNECTION SETUP

Start an O&M Timer
CCCH
RRC CONNECTION SETUP COMPLETE

Stop an O&M Timer
DCCH
SIGN_CONN_ESTAB_COMP
SIGN_CONN_ESTAB_SUCC_MO_S **
SIGN_CONN_ESTAB_SUCC_MT **
SIGN_CONN_ESTAB_SUCC_MO_D **
SIGN_CONN_ESTAB_SUCC_DEL_TOL **
SIGN_CONN_ESTAB_COMP_HIPRIO **
SIGN_CONN_ESTAB_COMP_EMG **
RRC_CONN_UE_AVG *** (start)
RRC_CONN_UE_MAX
RRC_CON_STP_TIM_MEAN*****
RRC_CON_STP_TIM_MAX*****
02 February 2016
* The counters are triggered depending on the cause within the RRC CONNECTION REQUEST message. Only valid
RRC Connection Request messages trigger the counters. I.e. when RRC Connection Request message is sent from
UE while the connection setup procedure in eNB is still under processing for previous RRC Connection Request, the
second or any other request is ignored.
** Successful RRC connection establishments are also counted within the SIGN_CONN_ESTAB_COMP
***The counter is not directly incremented with the RRC CONNECTION COMPLETE message but some other
algorithms are used to provide the averaged number of UEs in RRC connected state. See also the “Common notes
to chapter 2.4”.
**** For RACH_MSG3_CONTENTION details, see the “Common notes to chapter 2.3”
***** RRC_CON_STP_TIM_MEAN and RRC_CON_STP_TIM_MAX are calculated by measuring the time intervals
between reception of an RRC connection Request and sending corresponding RRC Connection Setup Complete.
eNB measures accumulate time of successful RRC Connection establishment over the granularity period
irrespective of establishment cause.
02 February 2016
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
SIGN_CONN_ESTAB_ATT_MO_D
SIGN_CONN_ESTAB_ATT_DEL_TOL
SIGN_CONN_ESTAB_ATT_HIPRIO
SIGN_CONN_ESTAB_ATT_EMG
RACH_MSG3_CONTENTION
RRC CONNECTION SETUP Start tHalfRrcCon

Timer
CCCH

DCCH
Expiry tHalfRrcCo Timer
SIGN_EST_F_RRCCOMPL_MISSING
02 February 2016
2.3.4 Unsuccessful RRC Connection Establishment (Completions Error in RRC CONNECTION

COMPLETE)
UE eNB

CCCH
RRC CONNECTION SETUP

Start an O&M Timer
CCCH

Stop an O&M Timer
DCCH
(Erroneous or incomplete)
SIGN_EST_F_RRCCOMPL_ERROR
02 February 2016
2.3.5 Unsuccessful RRC Connection Establishment (Rejection by eNB)
UE eNB

CCCH
RRC CONNECTION REJECT*

CCCH
SIGN_CONN_ESTAB_REJ_MO_S **
SIGN_CONN_ESTAB_REJ_MT **
SIGN_CONN_ESTAB_REJ_MO_D **
SIGN_CONN_ESTAB_REJ_DEL_TOL **
SIGN_CONN_ESTAB_REJ_HIPRIO **
SIGN_CONN_ESTAB_REJ_EMG ***
SIGN_CONN_ESTAB_FAIL_RB_EMG ***
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
02 February 2016
** triggered on any sending the RRC Connection Reject message
*** triggered on sending the RRC Connection Reject message due to missing radio resources for emergency calls
**** triggered on sending the RRC Connection Reject message initiated by RRM RAC. Possible causes:
- cell disabled
- cell barred
- number of rrc connections exceeded
- failed scheduling request indication allocation
- failed transmission mode selection
- failed cqi, ri allocation
- (optional) failed RSR allocation
- aperiodic cqi reporting mode on PUSCH.
1. In case the features LTE22, LTE 572 are disabled (a common flag) and RRC Connection Request has been
received from UE for the cause “Emergency call” the SIGN_CONN_ESTAB_ATT_OTHERS is triggered
instead the SIGN_CONN_ESTAB_ATT_EMG counter. The call is then handled as normal (non emergency)
one and when successfully answered with the RRC Connection Setup Complete message from UE the
counter SIGN_CONN_ESTAB_COMP is triggered only. The SIGN_CONN_ESTAB_COMP_EMG not triggered
in this scenario at all.
2. The SIGN_CONN_ESTAB_FAIL_RB_EMG only triggered in case the features LTE22, LTE 572 are enabled (a
common flag).
3. SIGN_CONN_ESTAB_REJ_EMG triggering is not feature flag LTE22, LTE 572 sensitive.
4. RACH_MSG3_CONTENTION counter increments every time eNB receives from the UE and decodes Msg3
in the contention based RA procedure
02 February 2016
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
02 February 2016
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.
02 February 2016
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
02 February 2016
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
02 February 2016
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. In case of an incoming HO the UE is considered to be in RRC- Connected
state in the target cell (from network/eNB side) after successful transmission of an RRC Connection
Reconfiguration Complete message from UE to eNB (see also chapter 3.2).
2. In parallel to RRC_CONN_UE_AVG also the counter CELL_LOAD_UNL_POW_RES may be triggered. This
counter provides the average number of RRC connected UEs which have set the "deviceType" in the "UE-
EUTRA-Capability" to "noBenFromBatConsumpOpt", that is which have indicated to the network (eNB) that
they do not foresee to benefit from network-based battery consumption optimization (3GPP TS 36.331, TS
36.306), that is which have indicated that their power supply resources are not limited to the small battery
of a normal UE (for example LTE smart phone with limited battery life) but that they have access to
unlimited power supply resources (for example LTE USB-stick connected to a PC using the PC power supply
resources).
02 February 2016
3. 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] and
chapter 11.14).
Averaged value Maximum value

DL direction DL_UE_DATA_BUFF_AVG/100 DL_UE_DATA_BUFF_MAX
UE_DRB_DL_DATA_QCI_1/100
UE_DRB_DL_DATA_NON_GBR/100
UL_UE_DATA_BUFF_AVG/100 UL_UE_DATA_BUFF_MAX
UL direction UE_DRB_UL_DATA_QCI_1/100
UE_DRB_UL_DATA_NON_GBR/100
4. 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]).
5. 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. It shall be noted that eNB level counter ENB_LOAD_ACT_UE_AVG
may provide bigger value as sum of cell level counter CELL_LOAD_ACT_UE_AVG of the cells covered by the
eNB due to different system components and some additional delay in processing trigger events for the
eNB level counter.
6. The counters related to UE transition to ECM-IDLE state are triggered independently there is at least one
E-RAB established for the UE or not. Thus for example the EPC_INIT_TO_IDLE_UE_NORM_REL may be
triggered also after successful TAU initiated with the TAU request and inactive Active Flag within (see note
within the chapter 4.4). 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 and chapter 13.1 within the Appendix of this specification.
7. Since RL50 the mean number of RRC Connected UEs, Active UEs per cell and eNB and Active UEs with data
in the buffer in UL and DL has in addition been measured as shown in the second column of the following
table (see also chapter 11.14). The first column of the table summarizes the corresponding measurements
which have been available since RL10.
Since RL10 Since RL 50

RRC_CONN_UE_AVG SUM_RRC_CONN_UE/DENOM_RRC_CONN_UE
CELL_LOAD_ACT_UE_AVG SUM_ACTIVE_UE/ DENOM_ACTIVE_UE
ENB_LOAD_ACT_UE_AVG SUM_ACTIVE_UE_ENB/ DENOM_ACTIVE_UE_ENB
DL_UE_DATA_BUFF_AVG/100* SUM_ACTIVE_UE_DATA_DL/ DENOM_ACTIVE_UE_DATA_DL*
UL_UE_DATA_BUFF_AVG/100* SUM_ACTIVE_UE_DATA_UL/ DENOM_ACTIVE_UE_DATA_UL*
02 February 2016
*The results obtained using the measurements from the both columns do not need to correlate to the
same values as the averaging for the counters in the first column have been done per active cell time
while since RL50 per measurement period.
SUM_ACTIVE_UE and CELL_LOAD_ACT_UE are NOT incremented in a SCell by the number of UEs which
are performing CA connection in a PCell with this particular SCell.
02 February 2016
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 received new CRNTI)
RRC: RRCConnectionReestablishmentRequest
CCCH
RRC_CON_RE_ESTAB_ATT *
RRC_CON_RE_ESTAB_ATT_HO_FAIL **
RRC_CON_RE_ESTAB_ATT_OTHER **
RACH_MSG3_CONTENTION ***
Reestablishment accepted
SRB and DRB 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
DCCH
Reestablish and
Resume SRB2 and
DRBs
RRC: RRCConnectionReconfigurationComplete
DCCH
Resume SRB2 and
DRBs
Delete resources of old

C-RNTI
02 February 2016
2.5.2 RRC Connection Re-establishment (Unsuccessful procedure)

UE Serving/Source/Target eNB
Reestablishment Trigger
Contention-based Random Access

(UE receives new CRNTI)
RRC: RRCConnectionReestablishmentRequest
CCCH
RRC_CON_RE_ESTAB_ATT *
RRC_CON_RE_ESTAB_ATT_HO_FAIL **
RRC_CON_RE_ESTAB_ATT_OTHER **
RACH_MSG3_CONTENTION ***
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.
RRC: RRCConnectionReestablishmentReject
CCCH
REJ_RRC_CONN_RE_ESTAB *
02 February 2016
2.5.3 RRC Connection Re-establishment to other eNB (RLF triggered

Handover) Successful procedure
requested serving
UE EPC
eNB eNB
RRC:RRCConnectionReestablishmentRequest
X2AP: RLF Indication
RCR_UE_CONTEXT_RETR_ATT
X2AP: Handover Request
HO_RLF_PREP_ATT

Acknowledge
RCR_UE_CONTEXT_RETR_SUCC HO_RLF_PREP_SUCC
X2AP: SN STATUS TRANSFER
Completion of successful RCR (see chapter

2.5.1)
X2 Handover Completion (see chapter 5.5)
X2AP:UE Context Release
HO_RLF_SUCC
PM counters that are incremented during normal handover execution are not incremented during RLF triggered
handover execution
02 February 2016
In case that multiple X2AP:RLF INDICATION messages are sent, for example, because the original serving eNB
cannot be defined uniquely, the counter RCR_UE_CONTEXT_RETR_ATT is updated only once
2.5.4 RRC Connection Re-establishment to other eNB (RLF triggered

Handover) Unsuccessful procedure due to expiry of T301guard in requested
eNB
requested serving
UE EPC
eNB eNB
RRC:RRCConnectionReestablishmentRequest
X2AP: RLF Indication
Start T301guard
RCR_UE_CONTEXT_RETR_ATT
Expiry T301guard
RCR_UE_CONTEXT_RETR_FAIL_TIM
RRC:RRCConnectionReestablishmentReject
HO_RLF_PREP_ATT
Start TX2RELOCexec Acknowledge Start TX2RELOCoverall
X2AP: SN Status Transfer
Expiry TX2RELOCexec
Expiry TX2RELOCoverall
Note to chapter 2.5.3 and 2.5.4

02 February 2016
Counters are also incremented in case of Intra-eNB HO.
1. *The counters are triggered for all the possible causes within the RRC CONNECTION REESTABLISHMENT
REQUEST
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.
5. The number of RRC Connection Reestablishment Attempts due to “Reconfiguration Failure” cause can be
calculated in an indirect way using the formula (RRC_CON_RE_ESTAB_ATT -
RRC_CON_RE_ESTAB_ATT_HO_FAIL - RRC_CON_RE_ESTAB_ATT_OTHER) and Successes using the formula
(RRC_CON_RE_ESTAB_SUCC - RRC_CON_RE_ESTAB_SUCC_HO_FAIL -
RRC_CON_RE_ESTAB_SUCC_OTHER).
6*** RACH_MSG3_CONTENTION counter increments every time eNB receives from the UE and decodes Msg3
in the contention based RA procedure
02 February 2016
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
ERAB_INI_SETUP_ATT_QCI1*
ERAB_INI_SETUP_ATT_QCI9*
Security and DRB Establishment (see chapter 3.2)
S1AP: INITIAL CONTEXT SETUP RESPONSE

E-RAB Setup List
EPS_BEARER_SETUP_COMPLETIONS
ERAB_INI_SETUP_SUCC_QCI1*
ERAB_INI_SETUP_SUCC_QCI9*
ERAB_SETUP_TIME_MEAN**
ERAB_SETUP_TIME_MAX**
* The counters are triggered on a per QCI basis (QCI1-9).
** See common notes to chapter 3.1 [4]

02 February 2016
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)
ERAB_INI_SETUP_ATT_QCI1
ERAB_INI_SETUP_ATT_QCI9
Security Establishment
S1AP: INITIAL CONTEXT SETUP RESPONSE/

FAILURE
E-RAB Failed to
Setup List/Cause
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 and Cause sent
within the S1AP: Initial Context Setup Response message and within the S1AP: Initial Context Setup Failure
message, respectively.
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 and S1AP: Initial Context Setup Failure message
only the Cause field.
02 February 2016
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
ERAB_ADD_SETUP_ATT_QCI1
ERAB_ADD_SETUP_ATT_QCI9
E_RAB_SETUP_ATT_EMG**
DRB Establishment (see chapter 3.2)
S1AP: E-RAB SETUP RESPONSE

E-RAB Setup List
EPS_BEARER_SETUP_COMPLETIONS
ERAB_ADD_SETUP_SUCC_QCI1*
ERAB_ADD_SETUP_SUCC_QCI9*
E_RAB_SETUP_SUCC_EMG**
ERAB_SETUP_TIME_MEAN***
ERAB_SETUP_TIME_MAX***
* The counters are triggered on a per QCI basis (QCI1-9).
**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.
*** See common notes to chapter 3.1 [4]
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.
02 February 2016
3.1.4 Additional E-RAB Establishment (Unsuccessful Procedure)
UE eNB MME
Successful UE Associated Logical S1 Connection and default E-RAB Establishment
ERAB_ADD_SETUP_ATT_QCI1*
ERAB_ADD_SETUP_ATT_QCI9*
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.
02 February 2016
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 and
counting each bearer of the "SAE Bearer to Be Setup List" IE.
2. The counters E_RAB_SETUP_ATT_EMG, E_RAB_SETUP_SUCC_EMG and E_RAB_SETUP_FAIL_RB_EMG are
triggered on the transmission of the related S1AP message irrespective of the number of bearers included
in the "SAE Bearer to Be Setup List" IE however considering that there is at maximum only one emergency
call per UE at the same time it may be considered that the mentioned counters provides the number of E-
RABs. It shall be considered that for one emergency call the related QCI5 and QCI1 dedicated bearers may
be established via two separated E-RAB Setup procedures.
3. The counters SUM_SIMUL_ERAB_QCI_x and SIMUL_ERAB_QCIx_MAX for x as an integer being changed
from 1 to 9 provide the mean and maximum number of the simultaneous QCIx E-RABs during the
measurement period. Each E-RAB starts to be counted after successful initial or additional establishment
procedure and the counting is stopped after its normal or abnormal release (see chapter 3.3 and 3.4).
4. The time shall be measured in two scenarios:
• Between receipt of Initial Context Setup Request and sending Initial Context Setup Response
• Between receipt of E-RAB Setup Request and sending E-RAB Setup Response.
5. ERAB_NBR_DL_AVG and ERAB_NBR_UL_AVG can be incremented in the following scenarios

- Initial Context Setup
- ERAB Setup
- ERAB Modify
- X2 HO target
- S1 HO target
- Inter-RAT HO from UTRAN to LTE, Target eNB (very similar to S1 HO target)
- Intra-eNB HO
ERAB_NBR_DL_AVG and ERAB_NBR_UL_AVG can be decremented in the following scenarios:
- UE Context Release (and others which cause context removal from the cell)
- ERAB Release
- ERAB Modify
6. If NBR feature is activated ( actNbrForNonGbrBearers ==TRUE), the scheduler sends in each second an
update of the average number of de-prioritized NBR bearers to the PM counters
ERAB_NBR_DL_FAIL_OVL_AVG (DL-S) and ERAB_NBR_UL_FAIL_OVL_AVG (UL-S) . If Downlink Carrier
Aggregation is activated (actDlCAggr=TRUE) NBR bearers are only counted in PCell. The reported value is
100 times higher than the actual value (for example 1.00 is stored as 100).
02 February 2016
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.
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
02 February 2016
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)”.
02 February 2016
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
02 February 2016
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.
02 February 2016
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 and 6 for RL 35 TD)”.
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
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).
02 February 2016
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
the handover are excluded.
02 February 2016
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
Note:
It should be noted that the message flow chart is simplified and some synchronization messages used during the
handover are excluded.
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).
02 February 2016
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.
02 February 2016
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
02 February 2016
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
02 February 2016
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
02 February 2016
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_EPS_BEARER_REL_REQ_NORM
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*
S1AP: UE Context Release Command

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

02 February 2016
3.3.6 Abnormal 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_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
ERAB_REL_ENB_ACT_QCI1*
ERAB_REL_ENB_ACT_NON_GBR*
RRC: RRC Connection Release S1AP: UE Context Release Command

DCCH
L2 ACK S1AP: UE Context Release Complete
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
*The counters are only triggered with RNL failure with UE lost cause and having data in the RLC buffer in
the time of drop.
02 February 2016
3.3.6 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
Set UE to Release all UE
RRC-IDLE related resources, Set UE to
remove UE context ECM-IDLE
02 February 2016
3.3.7 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
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, excepting those ones for active E-RAB drops noted in the chapter
3.3.6 and PRE_EMPT_GBR_BEARER, PRE_EMPT_NON_GBR_BEARER, 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.
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.
3. More info on the counters’ triggering can be found in the chapter 13.1 (Appendix of the specification) .
02 February 2016
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
*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 outgoing intra LTE or inter RAT handover
when the DRB is being released. Counter RB_REL_REQ_NORM_REL can be also incremented by an abnormal cause
- EPS initiated E-RAB Release, which is not expected.
02 February 2016
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
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.
2. The RRC Connection Reconfiguration with previous receipt of S1AP E-RAB RELEASE COMMAND
((RB_REL_REQ_NORM_REL, RB_REL_REQ_OTHER) from MME or followed with sending the S1AP E-RAB
RELEASE INDICATION (RB_REL_REQ_NORM_REL, RB_REL_REQ_OTHER) to MME trigger the counters in the
brackets in the scenarios when not all DRBs established for the UE have to be released, i.e. the UE after the
release procedure does not move into the ECM-IDLE state. While with the RRC Connection Release with
previous receipt the S1AP UE CONTEXT RELEASE COMMAND (RB_REL_REQ_NORM_REL,
RB_REL_REQ_DETACH_PROC, RB_REL_REQ_OTHER) from MME or followed with sending the S1AP UE
CONTEXT RELEASE REQUEST (RB_REL_REQ_NORM_REL, RB_REL_REQ_RNL_REDIR, RB_REL_REQ_OTHER,
RB_REL_REQ_RNL) to MME trigger the counters in the brackets in the scenarios when all DRBs established
02 February 2016
for an UE have to be released, i.e. the UE after the release procedure moves into the ECM-IDLE state. To find
the exact trigger cause the reader is instructed to read the chapter 13.1 in the Appendix of the specification.
3. The RRC Connection Reconfiguration with previous receipt of S1AP E-RAB RELEASE COMMAND
((RB_REL_REQ_NORM_REL, RB_REL_REQ_OTHER, RB_REL_REQ_RNL) from MME or followed with sending
the S1AP E-RAB RELEASE INDICATION (RB_REL_REQ_NORM_REL, RB_REL_REQ_OTHER) to MME trigger the
counters in the brackets in the scenarios when not all DRBs established for the UE have to be released, i.e.
the UE after the release procedure does not move into the ECM-IDLE state. While with the receipt the S1AP
UE CONTEXT RELEASE COMMAND (RB_REL_REQ_NORM_REL, RB_REL_REQ_DETACH_PROC,
RB_REL_REQ_OTHER) from MME or followed with sending the S1AP UE CONTEXT RELEASE REQUEST
(RB_REL_REQ_NORM_REL, RB_REL_REQ_RNL_REDIR, RB_REL_REQ_OTHER, RB_REL_REQ_RNL) to MME
trigger the counters in the brackets in the scenarios when all DRBs established for an UE have to be released,
i.e. the UE after the release procedure moves into the ECM-IDLE state. To find the exact trigger cause the
reader is instructed to read the chapter 13.1 in the Appendix of the specification.
3.5 UE Context Modification

3.5.1 S1AP UE Context Modification (Successful procedure)
eNB MME
S1AP: UE CONTEXT MODIFICATION REQUEST

UE_CTX_MOD_ATT UE-AMBR (opt.),
CS Fallback Indicator (opt.)
UE_CONTEXT_MOD_ATT_AMBR
UE_CTX_MOD_ATT_CSFB
S1AP: UE CONTEXT MODIFICATION RESPONSE
UE_CTX_MOD_SUCC
UE_CTX_MOD_SUCC_CSFB
02 February 2016
Notes :
1. The counters UE_CTX_MOD_ATT, UE_CTX_MOD_SUCC are triggered irrespective of the modified

information.
2. The counters UE_CONTEXT_MOD_ATT_AMBR, UE_CTX_MOD_ATT_CSFB and UE_CTX_MOD_SUCC_CSFB
are triggered in dependence it is AMBR and CSFB modified information, respectively.
3. There is no UE Context modification failure counter and UE Context Modification Success Rate is
calculated using KPI (LTE_5523a).
02 February 2016
3.6 E-RAB Modification

3.6.1 E-RAB Modification (Successful procedure)
UE eNB MME
S1AP: E-RAB MODIFY REQUEST

E-RAB to be Modified List
ERAB_MOD_ATT_QCI5*
ERAB_MOD_ATT_QCI6*
ERAB_MOD_ATT_QCI7*
ERAB_MOD_ATT_QCI8*
ERAB_MOD_ATT_QCI9*
RRC CONNECTION RECONFIGURATION

DCCH

COMPLETE
DCCH
S1AP: E-RAB MODIFY RESPONSE
E-RAB Modified List
ERAB_MOD_SUCC_QCI5**
* The counter is incremented by the number of QCIx bearers contained in the "E-RAB to be Modified List" IE,
where x is a integer within the range 5-9
** The counter is incremented by the number of QCIx bearers contained in the "E-RAB Modified List, where x is a
integer within the range 5-9
02 February 2016
E-RAB Modification (Unsuccessful procedure)
UE eNB MME
S1AP: E-RAB MODIFY REQUEST
E-RAB to be Modified List

ERAB_MOD_ATT_QCI5*
ERAB_MOD_ATT_QCI6*
ERAB_MOD_ATT_QCI7*
ERAB_MOD_ATT_QCI8*
ERAB_MOD_ATT_QCI9*

DCCH

COMPLETE
DCCH
S1AP: E-RAB MODIFY RESPONSE
E-RAB Failed to Modify List
ERAB_MOD_FAIL_TIMER**
ERAB_MOD_FAIL_QCI_NSUPP**
ERAB_MOD_FAIL_RNL_UNSPEC**
* The counter is incremented by the number of QCIx bearers contained in the "E-RAB to be Modified List" IE,
where x is a integer within the range of 5-9
** The counters are triggered on a per cause basis which is obtained from E-RAB Failed to Modify sent within the
S1AP: E-RAB Modify Response message
02 February 2016
4. S1AP Related Procedures

4.1 Initial Context Setup
4.1.1 Successful Procedure
UE eNB MME

UE_CTX_SETUP_ATT* E-RAB Failed to Setup
List is empty
UE_CTX_SETUP_ATT_CSFB**
Security and DRB Establishment (see chapter 3.2.1)
UE_CTX_SETUP_SUCC*
UE_CTX_SETUP_SUCC_CSFB***
*Includes also the UE Contexts that are subject to CS Fallback
** Incremented only when S1AP: INITIAL CONTEXT SETUP REQUEST message contains “CS Fallback Indicator IE”
*** Incremented only when S1AP: INITIAL CONTEXT SETUP RESPONSE was sent as a result of received S1AP:
INITIAL CONTEXT SETUP REQUEST message with “CS Fallback Indicator IE”.
02 February 2016
4.1.2 Unsuccessful Procedure

UE eNB MME

UE_CTX_SETUP_ATT
UE_CTX_SETUP_ATT_CSFB
Security Establishment

E-RAB Failed to Setup
List is not empty
OR
S1AP: INITIAL CONTEXT SETUP FAILURE
UE_CTX_SETUP_FAIL_RADIO_INT
02 February 2016
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
02 February 2016
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.
02 February 2016
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.
02 February 2016
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.
02 February 2016
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.
02 February 2016
4.4 S1 UE Associated Logical S1 Connection Establishment
UE eNB MME

ending with:
(NAS PDU)
DCCH
S1AP: INITIAL UE MESSAGE* (NAS PDU)

(eNB UE S1AP ID)
S1_SIGN_CONN_ESTAB_ATT_UE
S1AP: INITIAL CONTEXT SETUP REQUEST*
(MME UE S1AP ID)
S1_SIGN_CONN_ESTAB_SUCC_UE**
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. It shall be noted that the Initial Context Setup message is not the
only way how to move the UE to ECM-CONNECTED state. Another possible way is via DL NAS TRANSPORT which may
be sent to respond TAU request with inactive Active Flag and which always contains the MME UE S1AP ID IE and thus
moves the UE to EMC-CONNECTED state without any E-RAB establishment. However it shall be noted that UE stays
in the state for a very short time and after successful TAU moved to ECM-IDLE state by sending UE Context Release
Command from MME to eNB.
** Reception of the first S1AP message (MME->eNB) containing NAS signaling, which was received as a consequence
of a preceding transmission of the S1AP: INITIAL UE MESSAGE that contains the first NAS signalling message to the
MME.
02 February 2016
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
02 February 2016
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.
02 February 2016
4.6 S1AP Procedures Related to ETWS and CMAS

4.6.1 WRITE-REPLACE WARNING REQUEST (Successful Procedure)
eNB MME
S1AP:WRITE-REPLACE WARNING REQUEST
S1AP_WRITE_REP_WARN_REQ
S1AP:WRITE-REPLACE WARNING RESPONSE
S1AP_WRITE_REP_WARN_RESP
4.6.2 KILL- REQUEST (Successful Procedure)
eNB MME
S1AP:KILL REQUEST
S1AP_KILL_REQ
S1AP:KILL RESPONSE
S1AP_KILL_RESP
02 February 2016
4.6.3 WRITE-REPLACE WARNING REQUEST (Unsuccessful Procedure)
eNB MME
S1AP:WRITE-REPLACE WARNING REQUEST
S1AP_WRITE_REP_WARN_REQ
S1AP:WRITE-REPLACE WARNING RESPONSE
S1AP_WRITE_REP_WARN_FAIL*
* The counter is incremented when an S1AP:WRITE-REPLACE WARNING RESPONSE message is sent to

the MME and the Broadcast Completed Area List IE is not included in this message
4.6.4 KILL- REQUEST (Unsuccessful Procedure)
eNB MME
S1AP:KILL REQUEST
S1AP_KILL_REQ
S1AP:KILL RESPONSE
S1AP_KILL_FAIL*
* The counter is incremented when an S1AP:KILL RESPONSE message is sent to the MME and the
Broadcast Cancelled Area List IE is not included in this message.
02 February 2016
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
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.
02 February 2016
5.2 CS Fallback to UTRAN, CDMA/1xRTT or GSM via RRC Connection Release

(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)
UE_CTX_MOD_ATT_CSFB
Selection of redirect
target if possible
S1AP: UE CONTEXT MODIFICATION RESPONSE
RRC: RRCConnectionRelease
(with or without 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.

02 February 2016
5.3 CS Fallback to UTRAN, CDMA/1xRTT or GSM via RRC Connection Release

(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 if possible
S1AP: INITIAL CONTEXT SETUP RESPONSE**

(With or without Redirect Info)
CSFB_REDIR_CR_ATT
CSFB_REDIR_CR_EMERGENCY_ATT

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.

02 February 2016
** 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.
3. CSFB counters are being also updated by CSFB case to 1xRTT.
02 February 2016
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
HO_EMG_PREP
HO_PREP_IN_ATT****
Handover Preparation
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO ****
4. Admission Control and

Resource Allocation
HO_PREP_IN_SUCC****
HO_PREP_IN_SUCC_TC, HO_PREP_IN_SUCC_RR
HO_PREP_IN_SUCC_RL, HO_PREP_IN_SUCC_RO ****

DL allocation
ATT_INTRA_ENB_HO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
Handover Execution
HO_DRX_ATT, HO_LB_ATT, HO_SB_ATT***
Detach from old cell and

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
Handover Completion
SUCC_INTRA_ENB_HO
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_SUCC)
HO_EMG_SUCC
HO_DRX_SUCC, HO_LB_SUCC, HO_SB_SUCC***
Packet data
02 February 2016
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.
Despite TOT_HO_DECISION, TOT_NOT_START_HO_PREP are assigned to M8009 measurement type for
intra eNB HO they are triggered for all intra LTE HO types as it is not possible to assign it to a handover
type (intra eNB, X2 or S1 inter eNB based) as target cell has not been selected yet.
- ***The counters are triggered independent from each other
- **** For Incoming HO related counters explanation, see [5] in Common Notes
- In relation to points 5 and 8 see also chapter 3.2.1.
02 February 2016
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
HO_PREP_IN_ATT
HO_PREP_IN_ATT_RL, HO_PRER_IN_ATT_RO

Resource Allocation -Failure
Stop THOoverall
FAIL_ENB_HO_PREP_AC
FAIL_ENB_HO_PREP_OTH
HO_EMG_PREP_FAIL
HO_PREP_IN_FAIL_RAC
HO_PREP_IN_FAIL_TAC
02 February 2016
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
HO_PREP_IN_ATT
HO_PREP_IN_ATT_RL, HO_PRER_IN_ATT_RO
Resource Allocation
HO_PREP_IN_SUCC
HO_PREP_IN_SUCC_RL, HO_PRER_IN_SUCC_RO
DL allocation
Handover Execution
ATT_INTRA_ENB_HO
HO_EMG_ATT
HO_DRX_ATT,HO_LB_ATT, HO_SB_ATT*
Expiry THOoverall
ENB_INTRA_HO_FAIL
Note: In relation to point 5 and THOoverall Timer expiry see also chapter 3.2.4.
*The counters are triggered independent from each other.

02 February 2016
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_PREP_IN_ATT
HO_EMG_PREP HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO

Resource Allocation
Stop TX2RELOCprep
Start TX2RELOCOverall 6. Handover Request
Acknowledge Start TX2RELOCexec
ATT_INTER_ENB_HO HO_PREP_IN_SUCC
HO_EMG_ATT
HO_PREP_IN_SUCC_RL, HO_PREP_IN_SUCC_RO
Handover Execution
HO_DRX_ATT
DL allocation
8. SN Status Transfer
Data Forwarding
Detach from old cell
HO_LB_ATT, HO_SB_ATT Buffer Packets from
Source eNB
9. Synchronisation
10. UL allocation + TA for UE 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
Handover Completion
17. Path Switch Request 16. User Plane Update Response

Acknowledge
Stop TX2RELOCOverall 18. UE Context Release
SUCC_INTER_ENB_HO Release X2
Signalling
Connection
HO_EMG_SUCC
HO_DRX_SUCC
HO_LB_SUCC, HO_SB_SUCC
Data Forwarding
End Marker
Notes: *See chapter 3.4.1. In relation to points 6 and 11 see also chapter 3.2.2.
02 February 2016
5.5.2 Unsuccessful Procedure (HO Preparation Failure -Time cause)

UE MME
eNB eNB GW

UL allocation
3. HO Decision
HO_EMG_PREP

Resource Allocation
6. Handover Request
Acknowledge
Expiry TX2RELOCprep
FAIL_ENB_HO_PREP_TIME
HO_EMG_PREP_FAIL
02 February 2016
5.5.3 Unsuccessful Procedure (HO Preparation Failure –AC or OTHER cause)

UE MME
eNB eNB GW

UL allocation
3. HO Decision

Resource Allocation
Stop TX2RELOCprep 6. Handover Preparation
Failure
FAIL_ENB_HO_PREP_AC HO_FAIL_IN_FAIL_RAC
FAIL_ENB_HO_PREP_OTHER HO_PREP_IN_FAIL_TAC
02 February 2016
5.5.4 Unsuccessful Procedure (HO Execution or Completion Failure)

UE MME
eNB eNB GW

UL allocation
3. HO Decision

Resource Allocation
Stop TX2RELOCprep
Start TX2RELOCOverall 6. Handover Request
Acknowledge Start TX2RELOCexec
ATT_INTER_ENB_HO HO_PREP_IN_SUCC
HO_EMG_ATT HO_PREP_IN_SUCC_TC, HO_PREP_IN_SUCC_RR
Handover Execution
HO_DRX_ATT
DL allocation
7.RRC Connection Reconfiguration 8. SN Status Transfer
Data Forwarding
Detach from old cell
HO_LB_ATT, HO_SB_ATT 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 Handover Completion
Stop TX2RELOCcomp
17. Path Switch Request 16. User Plane Update Response
Acknowledge
18. UE Context Release

An error occurred which leads to
UE Context Release never received by Source eNB
Expiry TX2RELOCOverall
INTER_ENB_HO_FAIL
02 February 2016
Common note to chapter 5.5
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.
02 February 2016
5.6 Inter eNB S1 Based Handover

Source Target MME/ Serving
UE eNB GW
eNB EPC

3. HO Decision
4. Handover Required
Start TS1RELOCprep INTER_ENB_S1_HO_PREP 5. HO preparation in EPC
6. Handover Request
HO_EMG_PREP
HO_PREP_IN_ATT
Resource Allocation
8. Handover Request
Start TS1RELOCexec Acknowledge
HO_PREP_IN_SUCC
Stop TS1RELOCprep
9. HO preparation
completion in EPC
StartTS1RELOCOverall 10. Handover Command 9a. Create Indirect Data
Forwarding Tunnel Request
11. Trigger HO execution
9b. Create Indirect Data
INTER_ENB_S1_HO_ATT Forwarding Tunnel Response
HO_EMG_ATT
Handover Execution
HO_DRX_ATT

13a. eNB Status Transfer
13b. MME Status Transfer
Detach from old cell HO_LB_ATT, HO_SB_ATT
(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
Handover Completion
fresh S1-U data

18. UE Context Release Command
StopTS1RELOCOverall
INTER_ENB_S1_HO_SUCC
HO_EMG_SUCC
20. Delete Indirect Data

HO_DRX_SUCC Forwarding Tunnel Request
HO_LB_SUCC, HO_SB_SUCC
19. UE Context Release Complete
21. Delete Indirect Data
Release data forwarding Release data forwarding Forwarding Tunnel Response
resources resources
02 February 2016
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 Source Target MME/ Serving
eNB eNB EPC GW

3. HO Decision
Start TS1RELOCprep
5. HO preparation in EPC
INTER_ENB_S1_HO_PREP
6. Handover Request
HO_EMG_PREP
HO_PREP_IN_ATT
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR Handover Preparation


Resource Allocation
8. Handover Request
Start TS1RELOCexec Acknowledge
9a. Create Indirect Data
Forwarding Tunnel Request
HO_PREP_SUCC_ATT
10. Handover Command

9b. Create Indirect Data
Forwarding Tunnel Response
Expiry TS1RELOCprep

INTER_S1_HO_PREP_FAIL_TIME
Handover Command never received by Source eNB
HO_EMG_PREP_FAIL
02 February 2016
5.6.3 Unsuccessful Procedure (HO Preparation Failure - Resource or OTHER cause)

UE
eNB eNB EPC GW

3. HO Decision
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP
HO_EMG_PREP
6. Handover Request
HO_PREP_IN_ATT

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

Failure
INTER_S1_HO_PREP_FAIL_NORR
INTER_S1_HO_PREP_FAIL_OTHER
02 February 2016
5.6.4 Unsuccessful Procedure (HO Execution or Completion Failure)

UE
eNB eNB EPC GW

3. HO Decision
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP 6. Handover Request
HO_EMG_PREP HO_PREP_IN_ATT

Resource Allocation
8. Handover Request
Acknowledge
Start TS1RELOCexec
HO_PREP_IN_SUCC
HO_PREP_IN_SUCC_TC, HO_PREP_IN_SUCC_RR 9. HO preparation

Stop TS1RELOCprep HO_PREP_IN_SUCC_RL, HO_PREP_IN_SUCC_RO completion in EPC
9a. Create Indirect Data
StartTS1RELOCOverall 10. Handover Command Forwarding Tunnel Request
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
Detach from old cell HO_LB_ATT, HO_SB_ATT
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)
Handover Completion
Packet data (route optimized)
Begin sending
fresh S1-U data
18. UE Context Release Command

UE Context Release Command never received by Source eNB
Expiry TS1RELOCOverall
INTER_ENB_S1_HO_FAIL
02 February 2016
Common notes to chapters 5.4, 5.5 and 5.6
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 timers THOoverall, TX2RELOCoverall and TS1RELOCoverall are stopped in case an ongoing handover is
aborted for any reason (including also UE Context Release Command message received from MME
regardless the cause different from “RNL: Successful HO”) and therefore neither ENB_INTRA_HO_FAIL nor
INTER_ENB_HO_FAIL nor INTER_ENB_S1_HO_FAIL is triggered in this case.
4. 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.
5. Incoming handover preparation counters are updated in the handover target cell for which the incoming
handover preparation request was received. Counters are not updated in case of intra-cell handover or in
case of RLF (Radio Link Failure) triggered incoming handover.
HO_PREP_IN_ATT and HO_PREP_IN_SUCC provide the number of incoming handover preparation
attempts irrespective of the handover case. Other incoming HO preparation counters are triggered
depending on the HO preparation cause or HO preparation failure cause.
In case of incoming Inter-RAT HO, HO_PREP_IN_ATT HO_PREP_IN_SUCC, HO_PREP_IN_FAIL_RAC,
HO_PREP_IN_FAIL_TAC counters are triggered in the target LTE eNB.
02 February 2016
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

02 February 2016
* see also chapter 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
02 February 2016
5.7.1.3 Unsuccessful Procedure (Handover 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
02 February 2016
5.7.1.4 Unsuccessful Procedure (Handover 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
Common notes to chapter 5.7.1

02 February 2016
1. The counters related to handover preparation to UTRAN (in this chapter) are also triggered in case of
handover preparation to UTRAN or GERAN 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 or GERAN 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. The CSFB_PSHO_UTRAN_ATT is also triggered in case of CS Fallback to CDMA/1xRTT.
4. 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 UTRAN neighbouring cell (see the following table). The counters are not triggered for GERAN
neighbouring cell in case of HO with SRVCC.
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
02 February 2016
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
* see also chapter 3.4.1.

02 February 2016
5.7.2.2 Unsuccessful Procedure (Handover 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
02 February 2016
Common note to chapter 5.7.
PM Counters for HO preparation phase monitoring on target eNB in case of Inter-RAT HO are updated with the
same trigger conditions as in S1 Based HO at the target eNB. The following counters are incremented at the target
eNB:
Network element name NetAct name
Incoming handover preparation attempts HO_PREP_IN_ATT

Incoming handover preparation attempts (Time Critical Handover) HO_PREP_IN_ATT_TC
Incoming handover preparation attempts (Handover desirable for Radio Reasons) HO_PREP_IN_ATT_RR
Incoming handover preparation attempts (Handover to Reduce Load in serving cell) HO_PREP_IN_ATT_RL
Incoming handover preparation attempts (Resource Optimization Handover) HO_PREP_IN_ATT_RO
Successful incoming handover preparations HO_PREP_IN_SUCC
Successful incoming handover preparations (Time Critical Handover) HO_PREP_IN_SUCC_TC
Successful incoming handover preparations (Handover desirable for Radio
Reasons) HO_PREP_IN_SUCC_RR
Successful incoming handover preparations (Handover to Reduce Load in serving
cell) HO_PREP_IN_SUCC_RL
Successful incoming handover preparations (Resource Optimization Handover) HO_PREP_IN_SUCC_RO
Incoming handover preparation failures (Radio Resources) HO_PREP_IN_FAIL_RAC
Incoming handover preparation failures (Transport Resources) HO_PREP_IN_FAIL_TAC
For more details, see [5] in Common notes to chapters 5.4, 5.5 and 5.6)
Common note to chapter 5.4, 5.5, 5.6, 5.7:
1. The RRC_CONN_UE_AVG and RRC_CONN_UE_MAX are updated accordingly after UE has been
successfully handed over (releasing the resources) in the observing source cell.
02 February 2016
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
02 February 2016
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
02 February 2016
5.7.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
02 February 2016
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. Counters
MRO_EARLY_TYPE2 and MRO_EARLY_TYPE2_NB are also being triggered in case of HO to a wrong cell.
There is no separate counter for HO to a wrong cell case.
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.
5.9 Mobility to Home eNB

UE Source eNB Home eNB MME
RRC: Measurement Report

(measResults(measId of
„Event E-UTRA A3" or
„Event E-UTRA A5"))
Decision for mobility towards

a PCI belonging to Home
eNB
with Redirect Info for Home eNB.
Cause = RadioNetworkLayer
RRC_CON_REL_REDIR_H_ENB Cause(IRAT Redirect)
Normal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state), see chapter 3.1.1
UE performs cell selection and performs call setup to Home eNodeB

02 February 2016
5.10 Mobility from LTE to eHRPD

5.10.1 Successful HO Preparation from LTE to eHRPD
UE eNB MME S- GW EHRPD_ AN
RRC: HandoverFromEUTRA
PreparationRequest
Start TUIHoPrepTransferHrpd
( CDMA2000- Type = typeHRPD)
ISYS_HO_EHRPD_PREP_BC
RRC: ULHandoverPreparationTransfer
Stop TUIHoPrepTransferHrpd
The eNB determines the HO target based

on the strongest PN in the RRC:
Measurement Report received from the UE.
The eNB determines the SectorID
assocaited with the handover target
.
S1AP: UPLINK S1 CDMA 2000 TUNNELING

( CDMA 2000 HO Required Indication = true,
CDMA2000 Sector ID, CDMA2000- PDU,
EUTRAN Round Trip Delay Estimation Info ) S101: Direct Transfer Request
( Handover Indicator = HO Ready)
Start TC2KRelocPrepHrpd
S101: Direct Transfer Response
( Cause =Request Accepted )
S101: Direct Transfer Request
(S 101 Transparent Container, S 103 HSGW IP Address
if DL data forwarding applies)

( Cause = Request Accepted)
S11 : Create Forwarding Tunnel Request

(S 103 PDN Data Forwarding Info)
S11 : Create Forwarding Tunnel Response

(S1- U Data Forwarding Info)
S1AP: DOWNLINK S1 CDMA 2000 TUNNELING
( CDMA 2000 HO Status= HO Success, CDMA2000- PDU)
Stop TC2KRelocPrepHrpd
ISYS_HO_EHRPD_PREP_SUCC_BC
02 February 2016
5.10.2 Unsuccessful HO Preparation from LTE to eHRPD due to TUlHoPrepTransferHrpd

Timer expiry
PreparationRequest
( CDMA2000- Type = typeHRPD) Start TUIHoPrepTransferHrpd
TUIHoPrepTransferHrpd Expiry
ISYS_HO_EHRPD_PREP_FAIL1_BC
02 February 2016
5.10.3 Unsuccessful HO Preparation from LTE to eHRPD due to TC2KRelocPrepHrpd Timer

expiry
PreparationRequest

.

Start TC2KRelocPrepHrpd S101: Direct Transfer Response




( CDMA 2000 HO Status= HO Success, CDMA2000- PDU)
TC2KRelocPrepHrpd Expiry
02 February 2016
5.10.4 Unsuccessful HO Preparation from LTE to eHRPD caused by received HO Failure

indication message
PreparationRequest

.

Start TC2KRelocPrepHrpd




( CDMA 2000 HO Status== Ho Failure)
Stop TC2KRelocPrepHrpd
02 February 2016
5.10.5 Successful HO Completion from LTE to eHRPD

Successful HO Preparation from LTE to eHRPD

(see chapter 5.10.1)
(Purpose = Handover) Start TC2KRelocOverallHRPD
ISYS_HO_EHRPD_ATT_BC
Handover Execution
Notification Request
Stop TC2KRelocOverallHRPD
Handover Completion
Command (Successful HO)
ISYS_HO_EHRPD_SUCC_BC

Complete (Successful HO)
02 February 2016
5.10.5 Unsuccessful HO from LTE to eHRPD (Handover Execution or Completion Failure)

Successful HO Preparation from LTE to eHRPD

(see chapter 5.10.1)
(Purpose = Handover) Start TC2KRelocOverallHRPD
ISYS_HO_EHRPD_ATT_BC
Handover Execution
Notification Request

Command (Successful HO)
Handover Completion
TC2KRelocOverallHRPD Expiry
ISYS_HO_EHRPD_FAIL_TIM_BC
Common note to chapter 5.10:
1. For each handover relationship between the LTE cell (source of the inter system handover) and the
eHRPD bandclass (target of the inter system handover) a separate counter is provided.
02 February 2016
6. X2AP Related Procedures

6.1 X2 Setup (Successful Procedure)
Initiating Responding
eNB eNB
X2AP: X2 SETUP REQUEST
X2_SETUP_ATT
X2AP: X2 SETUP RESPONSE
6.2 X2 Setup (Unsuccessful Procedure)
Initiating Responding
eNB eNB
X2AP: X2 SETUP REQUEST
X2_SETUP_ATT
X2AP: X2 SETUP FAILURE
X2_SETUP_FAIL
6.3 X2 IP Address Retrieval (Successful Procedure)
Initiating
MME
eNB
S1AP:ENB CONFIGURATION TRANSFER
including 'SON Information Request' for 'X2 TNL Configuration Info'
X2_IP_RETR_VIA_S1_ATT
S1AP:MME CONFIGURATION TRANSFER
including 'SON Information Reply' with 'X2 TNL Configuration Info'
X2_IP_RETR_VIA_S1_SUCC
Common notes to chapter 6:
1. The functionalities mentioned in this chapter are restricted to intra LTE and intra frequency configuration.
02 February 2016
7. ANR for UTRAN

7.1 Successful Procedure
UE eNB
RRC: RRC Connection Reconfiguration

(CGI Measurement report)
DCCH
RRC: Measurement Report UTRAN_REPORT_CGI_ATT

(valid reportCGI)
DCCH
UTRAN_REPORT_CGI_SUCC
7.2 Unsuccessful Procedure
UE eNB

DCCH
RRC: Measurement Report UTRAN_REPORT_CGI_ATT

(incomplete reportCGI)
DCCH
UTRAN_REPORT_CGI_FAIL*
Note: *The counter is triggered on the reception of RRC Measurement Report message including a "reportCGI"
measurement result not containing the necessary IEs needed for unique cell identification like the LAC or RAC for a
UTRAN cell according to 3GPP TS 36.331.
02 February 2016
8. ANR for E-UTRAN

8.1 Successful Procedure
UE eNB

DCCH
RRC: Measurement Report REPORT_CGI_REQ

(valid reportCGI)
DCCH
SUCC_CGI_REPORTS
1. The ANR to E-UTRAN is applicable for CGI retrieval to intra and inter frequency.
02 February 2016
9. CA Related Procedures
9.1 SCell Addition/Configuration
UE eNB MME
Initial Context Setup

Handover (target side)
Reestablishment
AdditionTrigger for
SCell Addition
Admit SCell
Configure SCell
Adapt PCell
configuration
DCCH
(physicalConfig: PCell reconfiguration,
SCelltoAddModList: SCell addition)
CA_SCELL_CONFIG_ATT
DCCH
CA_SCELL_CONFIG_SUCC
CA_SCELL_CONF_UE_AVG (Start)
CA_2SCELLS_CONF_UE_AVG (Start)
02 February 2016
9.2 SCell Release
UE eNB MME
SCell has become disabled
Trigger for SCell Release
Adapt PCell configuration
(physicalConfig: PCell reconfiguration, DCCH

SCelltoReleaseList: SCell release)
DCCH
CA_SCELL_CONF_UE_AVG (Stop)
CA_2SCELLS_CONF_UE_AVG (Stop)
Release SCell
related resources
1. Counters CA_SCELL_CONF_ UE_AVG, CA_2SCELLS_CONF_UE_AVG are not directly incremented and

decremented with sending the RRC Connection Reconfiguration Complete message from UE but some
other algorithm are used to provide the averaged number of CA UEs with SCell(s) configured (for more
info see [2,3]).
2. After the UE has been in RRC Connected state some checks the UE is CA capable or not is done. The
averaged number of CA capable UEs is measured within the CA_DL_CAP_UE_AVG and
CA_DL_CAP_UE_3CC_AVG depending on UE Capability (for more info see [2,3]). Counters are updated
even if CA is disabled or if a CS Fallback Indicator was received.
02 February 2016
10. TTI Bundling Related Procedures

10.1 TTI Bundling Start
UE eNB
TTI bundling is not activated

for the UE
Conditions to start
TTI bundling are
met
Intracell Handover
preparation,
ttiBundlingStatusCh
ange flag set to
active.
DCCH
ttiBundling set to active
Internal timer started to
RRC: RRCConnectionReconfigurationComplete measure how long the UE
was in the TTI bundling
DCCH
TTI_BUNDLING_MODE_UE_AVG (Start)
02 February 2016
10.2 TTI Bundling Stop
UE eNB
TTI bundling is activated for

the UE
Conditions to stop
TTI bundling are
met
Intacell Handover
preparation,
ttiBundlingStatusCh
ange flag set to
deactive.
Internal timer stopped to
DCCH measure how long the UE
ttiBundling set to inactive
was in the TTI bundling.
According to the measured
value one of the following
DCCH counters is triggered
TTI_BUNDLING_MODE_UE_AVG (Stop) TTI_BUNDL_RETENTION_SHORT
TTI_BUNDL_RETENTION_MEDIUM
TTI_BUNDL_RETENTION_LONG
TTI Bundling counting for the

UE is also stopped with the
UE Context Release see
chapter 2.4 including also
any successful mobility, see
chapter 5.
1. The counter TTI_BUNDLING_MODE_UE_AVG is not directly incremented and decremented with sending
the RRC Connection Reconfiguration Complete message from UE but some other algorithm are used to
provide the averaged number of UEs in TTI Bundling mode (for more info see [2,3]).
2. The reported value for the TTI_BUNDLING_MODE_UE_AVG is 100 times higher than the actual value (for
example 1.00 is stored as 100).
02 February 2016
3. The short and medium intervals for the TTI_BUNDL_RETENTION_SHORT and

TTI_BUNDL_RETENTION_MEDIUM are hardly coded and set to 0,25 and 5 seconds, respectively.
02 February 2016
11. U Plane E-UTRAN PM Counters

11.1 PDCP SDU Delay in DL
11.1.1 Retention Delay within the eNB in DL
The relevant counters for this scenario are the following:
- PDCP_RET_DL_DEL_MEAN_QCI_1
- PDCP_SDU_DELAY_DL_DTCH_MEAN
The principle of measurement is shown in the following Fig. 1.
Fig. 1 Principle of retention delay within the eNB measurement in DL

02 February 2016
The measurement is done on a per burst basis. It means that focuses only on the first PDCP SDU from
the burst in such a way that t0 represents the time of the PDCP SDU reception in the eNB and t1 the time
TB containing a segment of the SDU is transmitted via air interface. At the end of the measurement
period the t1- t0 intervals of the all involved bursts are summed up and divided with the number of
bursts. The measurement is done per each QCI and per whole DL
It shall be noted that in case the first PDCP SDU of the burst is discarded this is not counted within the
measurement.
11.1.2 PDCP SDU HARQ Loop Delay Measurement in DL

- HARQ_DURATION_QCI1_AVG
The measurement is done for each PDCP SDU within the burst and all the bursts.
  t Ack (i )  t Asend (i ) 
HARQ_DURATION_QCIx_AVG (T )   i  (1)
 I (T ) 
 
The HARQ_DURATION_QCIx_AVG is updated with the tACK(i) – tsend(i) time period for each PDCP SDU
of the related QCIx characteristic in such a way that tsend(i) represents the point in time when first
piece of the i-th PDCP SDU was send via air interface while the tACK(i) the point in time the last piece
of the i –th PDCP SDU was received by the UE according to received HARQ feedback information. At
the end of the measurement period T the accumulated value is divided with the number of
successfully transmitted PDCP SDUs I for the related QCIx characteristic.
02 February 2016
Regarding the segmented PDCP PDUs when the first piece and last piece do not belong to the same
transmitted TB the measurement is done exactly like mentioned above according to Eq. 1. For the cases
when a whole PDCP PDU/SDU is transmitted via a TB containing one or more compact RLC SDUs (PDCP
PDUs) the HARQ transmission time of the TB is multiplied with this number of RLC SDUs in the TB
updates the related counter. The principle is summarized in the Fig.2
First piece of i-th PDCP SDU

(QCIx) was send via air
t=tsend(i)
NO
Last piece of i-th PDCP SDU (QCIx)

was successfully acknowledged by
the UE via HARQ feedback
YES
t=tACK(i)
K represents the number of

RLC SDUs (PDCP SDU/
PDUs) contained in the Is the PDCP SDU
same TB like the measured YES
segmented one?
i-th PDCP SDU for the same
QCIx. Numerator of the
HARQ_DURATION_QCIx_AVG +
The HARQ transmission time NO tACK(i) – tsend(i)
for the PDCP SDUs
contained in the same TB Numerator of the
are then measured in one HARQ_DURATION_QCIx_AVG + At the end of the measurement
place with the i-th PDCP K.(tACK(i) – tsend(i)) period T the accumulated value
SDU, i.e. no separated
of the numerator of the
measurement loop needed
HARQ_DURATION_QCIx_AVG
for them.
is divided with the number of
End successfully transmitted PDSCP
SDUs for the QCIx.
Fig. 2 PDCP SDU HARQ loop delay procedure

02 February 2016
1. The end to end delay in DL according to 3GPP TS 36.314 chapter 4.1.4 is given as the sum of the retention
delay counter from the chapter 11.1.1 and the corresponding one from the chapter 11.1.2. For instance
regarding the averaged PDCP SDU delay for QCI1 it is given as PDCP_RET_DL_DEL_MEAN_QCI_1 +
HARQ_DURATION_QCI1_AVG.
11.2 PDCP SDU Delay in UL

11.2.1 Retention Delay within the eNB in UL
The relevant counter for this scenario is the following:

- PDCP_SDU_DELAY_UL_DTCH_MEAN
t1
t0
Fig. 3 Principle of retention delay within the eNB measurement in UL
The measurement is done for each successfully received PDCP SDU in UL in such a way that t0 the point
in when a last segment of the PDCP SDU is received from the MAC layer (part of the MAC SDU) and t1
the point in time when the PDCP SDU is sent via S1/X2 interface out of the eNB, i.e. before sending to
transport module which is excluded from measurement. At the end of the measurement period the t1- t0
intervals of the all involved PDCP SDUs are summed up and divided with the number of PDCP SDUs.
02 February 2016
Common note to chapter 11.2.1
1. Win 7 and Win8 OS decide on TCP window size by measuring time that hand shake takes. The longer it
takes, the bigger receive window size is selected. Bigger the window is, the faster bitrates are achieved
over LTE. (Too small window size leads to empty receiver buffer and thus smaller average bit
rates). Nokia RTT is "too" fast during TCP hand shake, due to utilization of UL pre-scheduler, which E/// or
Huawei don't have. Nokia smaller RTT leads then to smaller receive window sizes and thus smaller IP
scheduled throughputs in Win7/Win8 based UE's than competitors have. To fix this issue eNB is delaying
TCP syn packets by 20 ms. Considering 2- 3% of packets are TCP SYN packets it may lead to overall UL
retention delay increase by 0.4 to 0.6 ms.
11.3 RLC PDU Transmission and Re-transmission

11.3.1 RLC PDU Transmission and Re-transmission in DL

- RLC_PDU_FIRST_TRANS
- RLC_PDU_RE_TRANS

02 February 2016
RLC PDU sent to MAC layer

in DL
NO
Is the RLC PDU first transmission
YES
In case re-segmentation is
RLC_PDU_FIRST_TRANS++ RLC_PDU_RE_TRANS++ applied during the re-
transmission the counting is
done for each re-segmented
RLC PDU.
End
Fig. 4 Principle of RLC PDU (re) transmission measurement in DL
11.3.2 RLC PDU Transmission and Re-transmission in UL

- UL_RLC_PDU_RETR_REQ
- UL_RLC_PDU_REC_TOT

02 February 2016
RLC PDU is requested for

RLC PDU received in UL
retransmission in UL
UL_RLC_PDU_REC_TOT++ UL_RLC_PDU_RETR_REQ++
End End
In case re-segmentation is
applied during the re- Triggered with the number
transmission the counting is of NACKs within the RLC
done for each re-segmented Status Report message sent
RLC PDU successfully to UE.
received.
Fig. 5 Principle of RLC PDU (re) transmission measurement in UL
1. The triggering in DL direction is done per each RLC PDU, i.e. re-segmented one sent during re-transmission
is counted as a separated RLC PDU and pegs the RLC_PDU_RE_TRANS.
2. The triggering in UL direction for the received RLC PDUs is done per each RLC PDU, i.e. re-segmented one
received during re-transmission is counted as a separated RLC PDU and pegs the UL_RLC_PDU_REC_TOT.
3. The triggering in UL direction in case of retransmission (UL_RLC_PDU_RETR_REQ) is done depending on
the number of NACKs included within the RLC Statue Report message sent to UE. Thus it may happen that
the first transmission of the RLC PDU from UE was unsuccessful and eNB sent the NACK within the RLC
Status Report message to UE which triggers the UL_RLC_PDU_RETR_REQ by one however the RLC PDU
was re-segmented on UE side and for instance sent via the two segments (two RLC PDUs) which triggers
the UL_RLC_PDU_REC_TOT by two in case of their successful reception by eNB.
4. The counters are also triggered for SRB0, 1 and 2 transmissions.
11.4 MAC PDU Transmission and Re-transmission in DL

- HARQ_RETRANS_ON_DL_SCH
- TRANSMIT_TB_ON_DL_SCH
02 February 2016
MAC PDU sent in DL via air

interface
Is the MSC PDU transmitted for the NO

first time?
YES
TRANSMIT_TB_ON_DL_SCH++
Was the HARQ NACK received for

the MAC PDU from the UE and re-
transmission is going to be done?
YES
HARQ NACK pegs the
counter as it is triggering for
MAC PDU resending.
HARQ_RETRANS_ON_DL_SCH++
NO
End
Fig. 6 Principle of MAC PDU (re) transmission measurement in DL
The principle of measurement is shown in the above Fig. 6.
1. The counters described in this chapter are not triggered on SIB transmission/re-transmission.
02 February 2016
11.5 RSSI Measurements per UE

11.5.1 RSSI Measurements per UE for PUCCH

- RSSI_PUCCH_LEVEL_01 … RSSI_PUCCH_LEVEL_22
- RSSI_PUCCH_MIN
- RSSI_PUCCH_MAX
- RSSI_PUCCH_AVG
11.5.2 RSSI Measurements per UE for PUSCH

- RSSI_PUSCH_LEVEL_01 … RSSI_PUSCH_LEVEL_22
- RSSI_PUSCH_MIN
- RSSI_PUSCH_MAX
- RSSI_PUSCH_AVG
The same flow chart as used for RSSI measurement on PUCCH according to Fig.7 applies. The only
difference is that the measurement done on PUSCH.
1. The result of the measurement is an RSSI per UE and PRB.

2. In inactive TTIs with no UE’s transmission on PUSCH/PUCCH no measurement is done and those TTIs are
completely excluded from the consideration.
3. The measurement periods with no active TTI are assigned with -140 dBm as measured averaged RSSI
(RSSI_PUCCH_AVG, RSSI_PUSCH_AVG) per UE and PRB by default. The histogram counters are not
triggered at all in such measurement periods.
4. The averaged value represented by the RSSI_PUCCH_AVG/ RSSI_PUSCH_AVG is calculated in the dBm
domain.
5. The averaging within the TTI per the UE is done in Watt domain.
02 February 2016
j-th UE did transmission on

PUCCH in i-th TTI In case of multiple receive
diversity antenna the
measurement is done for
each antenna summing up
Physical layer of the eNB measures the results from all the
RSSIj,I realized by averaging over all allocated UL antennas.
demodulation reference signals of a particular UE in
Watt domain and normalized to a single PRB. The
result is consequently converted to dBm.
NO
Is the RSSIj,i< RSSI_PUCCH_MIN?
YES
RSSI_PUCCH_MIN=RSSIj,i
Is the RSSIj,i
> RSSI_PUCCH_MAX?
YES
RSSI_PUCCH_MAX=RSSIj,i
NO At the end of the
measurement period a total
average is calculated by
dividing this accumulated
value by the total number of
Numerator(RSSI_PUCCH_AVG)= UEs that did transmission on
Numerator(RSSI_PUCCH_AVG)+ RSSIj,i PUCCH during the
measurement period
Increment the RSSI_PUCCH_Level_x

counter according to the bin x the measured
RSSIj,I falls to
End
Fig. 7 Principle of RSSI measurement per UE for PUCCH per one TTI
11.6 SINR Measurements per UE

11.6.1 SINR Measurements per UE for PUCCH

- SINR_PUCCH_LEVEL_01 … SINR_PUCCH_LEVEL_22
- SINR_PUCCH_MIN
- SINR_PUCCH_MAX
- SINR_PUCCH_AVG
02 February 2016
11.6.2 SINR Measurements per UE for PUSCH

- SINR_PUSCH_LEVEL_01 … RSSI_PUSCH_LEVEL_22
- SINR_PUSCH_MIN
- SINR_PUSCH_MAX
- SINR_PUSCH_AVG
The same flow chart as used for RSSI measurement on PUCCH according to Fig.8 applies. The only
difference is that the measurement done on PUSCH.
1. The result of the measurement is an SINR per UE and PRB.

2. In inactive TTIs with no UE’s transmission on PUSCH/PUCCH no measurement is done and those TTIs are
completely excluded from the consideration.
3. The measurement periods with no active TTI are assigned with -22 dB as measured averaged SINR
(SINR_PUSCH_AVG, SINR_PUCCH_AVG) per UE by default. The histogram counters are not triggered at all
in such measurement periods.
4. The averaged value represented by the SINR_PUCCH_AVG/ SINR_PUSCH_AVG is calculated in the dB
domain.
5. The averaging within the TTI per the UE is done in Watt domain.
02 February 2016
j-th UE did transmission on

PUCCH in i-th TTI
Received vector Error (I+N) vector
Physical layer of the eNB measures

RSSIj,I [W] as specified in the “RSSI Measurement per UE for
PUCCH” chapter and (I+N)j,I realized by averaging over all Error free vector
allocated resources of a particular UE in Watt domain and
normalized to a single PRB.
SINRj,I=RSSIj,I/(I+N)j,I [dB]
In particular an error vector (I+N) is
measured for each symbol (DMRS) as
difference between the received and
error free vector. The averaging is then
NO done from the error vectors from all
received symbols for the UE in the TTI
Is the SINRj, <SINR_PUCCH_MIN? in the Watt domain and normalization
to a single PRB.
In case of multiple receive

diversity antenna the (I+N)
YES measurement is done for
each antenna summing up
the results and dividing the
SINR_PUCCH_MIN=SINRj, result with the number of
antennas
Is the SINRj,
> SINR_PUCCH_MAX?
YES
SINR_PUCCH_MAX=SINRj,i
Numerator(SINR_PUCCH_AVG)= UEs that did transmission on
Numerator(SINR_PUCCH_AVG)+ SINRj,i PUCCH during the
measurement period
Increment the SINR_PUCCH_Level_x

counter according to the bin x the measured
SINRj,I falls to
End
Fig. 8 Principle of SINR measurement per UE for PUCCH per one TTI
11.7 RSSI Measurements per Cell

11.7.1 RSSI Measurements per cell for PUCCH

- RSSI_CELL_PUCCH_LEVEL_01 … RSSI_CELL_PUCCH_LEVEL_22
- RSSI_ CELL_PUCCH_MIN
- RSSI_ CELL_PUCCH_MAX
- RSSI_ CELL_PUCCH_MEAN
02 February 2016
11.7.2 RSSI Measurements per cell for PUSCH

- RSSI_ CELL_PUSCH_LEVEL_01 … RSSI_ CELL_PUSCH_LEVEL_22
- RSSI_ CELL_PUSCH_MIN
- RSSI_ CELL_PUSCH_MAX
- RSSI_ CELL_PUSCH_MEAN

.
1. The result of the measurement is an RSSI per cell and PRB.

2. Inactive TTIs with no UE’s transmission on PUSCH/PUCCH are assigned with -130 dBm.
3. The averaged value represented by the RSSI_PUCCH_AVG/ RSSI_PUSCH_AVG is calculated in the dBm
domain.
4. The averaging within the TTI per the cell is done in Watt domain.
02 February 2016
j-th TTI on PUCCH has - As one PRB can be only allocated

occurred per one UE only the measurement is
equivalent to RSSI per UE for
PUCCH one.
- In case the PRB is unused by any
UE the reporting for this PRB is
Physical layer of the eNB measures signal power RSSIj,I assigned RSSI with a default value -
for each PRB (i being changed from 1 to N where N is the 130 dBm.
number of configured PRBs for PUCCH) in Watt. - In case of multiple receive diversity
antenna the measurement is done
for each antenna summing up the
results from all the diversity
antennas is provided
𝑁
𝑅𝑆𝑆𝐼𝑗 = 𝑖=1 𝑅𝑆𝑆𝐼𝑗 ,𝑖 /𝑁 [W]
At the end of the

Numerator(RSSI_CELL_PUCCH_MEAN)= measurement period a total
Numerator(RSSI_CELL_PUCCH_MEAN)+ average is calculated by
RSSIj dividing this accumulated
TTIs in the measurement
period that apply for PUCCH.
Increment the RSSI_CELL_PUCCH_Level_x The result is afterwards
counter according to the bin x the measured RSSIj converted to dBm.
[dBm] falls to
PUCCH
UEs that did transmission on
At the end of the
Is the RSSIj [dBm] < NO
RSSI_CELL_PUCCH_MIN?
YES
RSSI_CELL_PUCCH_MIN=RSSIj [dBm]
Is the RSSIj [dBm]

> RSSI_CELL_PUCCH_MAX?
YES
RSSI_CELL_PUCCH_MAX=RSSIj [dBm]
NO
End
Fig. 9 Principle of RSSI measurement per cell for PUCCH per one TTI
02 February 2016
11.8 SINR Measurements per Cell

11.8.1 SINR Measurements per Cell for PUCCH

- SINR_CELL_PUCCH_LEVEL_01 … SINR_CELL_PUCCH_LEVEL_22
- SINR_CELL_PUCCH_MIN
- SINR_CELL_PUCCH_MAX
- SINR_CELL_PUCCH_MEAN
11.8.2 SINR Measurements per Cell for PUSCH

- SINR_CELL_PUSCH_LEVEL_01 … RSSI_CELL_PUSCH_LEVEL_22
- SINR_CELL_PUSCH_MIN
- SINR_CELL_PUSCH_MAX
- SINR_CELL_PUSCH_MEAN
1. The result of the measurement is an SINR per cell and configured PRB.
2. Inactive TTIs with no UE’s transmission on PUSCH/PUCCH are assigned with -22 dB.
3. The averaged value represented by the SINR_CELL_PUSCH_MEAN / SINR_CELL_PUCCH_MEAN is
calculated in the dB domain.
02 February 2016
j-th TTI on PUCCH has

occurred
- As one PRB can be only allocated per one
UE only the measurement is equivalent to
RSSI per UE for PUCCH one.
Physical layer of the eNB measures signal power RSSIj,I - In case of multiple receive diversity
and (I+N)j,I for each PRB (i being changed from 1 to N antenna the (I+N) measurement is done for
where N is the number of configured PRBs for PUCCH) each antenna summing up the results and
in Watt. dividing the result with the number of
antennas
𝑁 𝑁
𝑆𝐼𝑁𝑅𝑗 = 𝑖=1 𝑅𝑆𝑆𝐼𝑗 ,𝑖 / 𝑖=1(𝐼 + 𝑁)𝑗 ,𝑖 [dB]
Numerator(SINR_CELL_PUCCH_MEAN)= At the end of the

Numerator(SINR_CELL_PUCCH_MEAN)+ measurement period a total
SINRj average is calculated by
TTIs in the measurement
Increment the SINR_CELL_PUCCH_Level_x period that apply for PUCCH.
counter according to the bin x the measured SINRj The averaging is done in dB
falls to domain.
PUCCH
UEs that did transmission on
At the end of the
Is the SINRj < NO
SINR_CELL_PUCCH_MIN?
YES
SINR_CELL_PUCCH_MIN=SINRj
Is the SINRj
> SINR_CELL_PUCCH_MAX?
YES
SINR_CELL_PUCCH_MAX=SINRj
NO
End
Fig. 11 Principle of SINR measurement per cell for PUCCH per one TTI
02 February 2016
Common notes to chapter 11.5, 11.6, 11.7 and 11.8:
1. The RSSI/S per UE/cell in case of RX diversity antenna is always provided as the sum from all antennas
while the (I+N) for UE/cell evaluated as an average per RX diversity antenna.
2. In relation to previous point in case of RX diversity antenna it is seen as an antenna’s aperture increase
from which both RSSI and SINR may benefit (i.e. show an increase and improvement, respectively).
3. The RSSI per UE/cell is measured out of the noise and interference!
11.9 PDCP SDU Volume Measurements

11.9.1 PDCP SDU Volume in DL

- PDCP_SDU_VOL_DL which is updated when PDCP receives acknowledgment from RLC that PDCP
PDU was successfully transmitted to UE. Note that in RLC AM mode it means that PDU was
actually received by UE. In RLC UM mode it only means that RLC mapped the PDU to transport
blocks, but such PDU might be lost later and not reach UE. The related size of DL PDCP SDU's
mapped to DRB is counted (see Fig. 13).
02 February 2016
PDCP SDU has been

received in PDCP layer.
Is the PDCP SDU related to RLC NO

AM?
Has the RLC successfully mapped

YES the PDCP PDU to RLC PDU(s)?
YES
Has PDCP received ACK for the
PDCP SDU from RLC layer?
PDCP_SDU_VOL_DL+
size(PDCP SDU)
NO
YES
PDCP_SDU_VOL_DL+ size(PDCP
SDU)
NO
End
Fig. 13 PDCP SDU volume measurement principle in DL
Note: In case of intra LTE inter cell HO the UE successfully received the PDCP SDU packet in the source cell but
some of its part or the whole packet was not confirmed by UE via sending the ARQ ACK into the eNB the following
scenarios are possible:
1. PDCP status report is not sent by the UE in the target cell

Then the PDCP SDU packet will be sent to UE again and in case of successful reception by the UE counted
within the PDCP_SDU_VOL_DL for target cell although PDCP layer on UE side will discard this packet.
2. PDCP status report to inform the PDCP SDU packet was successfully received by the UE in the source cell
is sent in the target cell
Then the PDCP SDU packet will be dropped from eNB buffer and not counted via any PDCP_SDU_VOL_DL
counter neither in source nor in target cell.
The same apply also for counting the number of transmitted PDCP SDUs in DL (chapter 11.1.1).
02 February 2016
11.9.2 PDCP SDU Volume in UL

- PDCP_SDU_VOL_UL is updated for every successfully received and processed PDCP PDU. In RLC
AM mode, PDCP PDUs received with SN out of receiving window will be dropped and not
counted. The related size of UL PDCP SDU's mapped to DRB is counted (see Fig. 14).
RLC layer created the RLC

SDU (PDCP PDU) from the
received RLC PDUs in UL.
Is the created PDCP PDU evaluated NO

as successfully received.
In RLC AM the PDCP SDUs

YES corresponding to the PDCP
PDUs received with SN out
of receiving window are not
PDCP_SDU_VOL_DL+ size(PDCP counted
SDU)
End
Fig. 14 PDCP SDU volume measurement principle in UL
1. Only DRBs are counted not SRBs.
11.10 RLC Volume Measurements

11.10.1 RLC PDU Volume in DL

- RRC_DL_VOL which is updated when an RRC data block is sent to UE. Size of DL RLC PDU's
mapped to SRB0, SRB1 and SRB2 is counted (see Fig. 15).
- RLC_PDU_VOL_TRANSMITTED which is updated when RLC PDU is transmitted to UE. Size of each
RLC PDU also on BCCH and PCCH transmission is counted. To get 3GPP defined PDU size in this
02 February 2016
counter, MAC layer have to calculate and add the amount of SDU padding in PDU volume for
BCCH and PCCH (see Fig. 15).
- RLC_PDU_DL_VOL_CA_SCELL which is incremented by a volume of each RLC PDU when the RLC
PDU is transmitted on SCell. LTE MAC has no information about possible happened blocking in
PDCCH LA, and that is why the counter is updated also in that case which can cause a little
inaccuracy to statistics (see Fig. 15).
RLC PDU has been

transmitted. for BCCH and PCCH the
added amount of SDU
padding in PDU volume is
also counted
RLC_PDU_VOL_TRANSMITTED+
size(RLC PDU)
Is the RLC PDU mapped to SRB0,1

or 2?
YES
RRC_DL_VOL+ size(RLC PDU)

NO
Is the RLC PDU transmitted via

Scell?
The counter is updated also

in case of possible blocking
YES in PDCCH LA in the target
Scell.
RLC_PDU_DL_VOL_CA_SCELL
+ size(RLC PDU)
NO
End
Fig. 15 RLC PDU volume measurement principle in DL
Note: Both new and re-transmissions are considered where it applies.

02 February 2016
11.10.2 RLC PDU Volume in UL
RLC PDU has been

received.
Is the RLC PDU evaluated as

NO
duplicated reception?
Is the RLC PDU part of the RLC SDU

exceeding the maximum RLC SDU
size (8193 bytes)? NO
RLC_PDU_VOL_RECEIVED+
size(RLC PDU)
YES
Is the RLC PDU mapped to SRB0,1

or 2?
YES
RRC_UL_VOL+ size(RLC PDU)

NO
YES
End
Fig. 16 RLC PDU volume measurement principle in UL

- RRC_UL_VOL which is updated when an RRC data block from UE is received. Size of UL RLC
PDU's mapped to SRB0, SRB1 and SRB2 is counted. Duplicate RLC PDU receptions are not
counted and also the RLC PDUs which are part of the RLC SDUs exceeding the maximum RLC
SDU size (8193 bytes) are excluded from the measurement (see Fig. 16).
- RLC_PDU_VOL_RECEIVED which is updated when an RLC PDU from UE is received. Size of UL RLC
PDU's is counted. Duplicate RLC PDU receptions are not counted and also the RLC PDUs which
02 February 2016
are part of the RLC SDUs exceeding the maximum RLC SDU size (8193 bytes) are excluded from
the measurement (see Fig 16).
Note: RLC data volumes for logical channels BCCH, PCCH, UL/DL CCCH mapped to RLC TM mode can be seen from
corresponding MAC counters MAC_SDU_VOL_BCCH, MAC_SDU_VOL_PCCH, MAC_SDU_VOL_UL_CCCH and
MAC_SDU_VOL_DL_CCCH as they give equal results.
11.10.3 RLC SDU Volume in DL
RLC SDU transmission

towards the UE.
NO
Is the RLC SDU mapped to DRB?
YES Is the RLC SDU mapped to SRB 1 or

2?
RLC_SDU_VOL_DL_DTCH+
size(RLC SDU)
NO
YES
RLC_SDU_VOL_DL_DCCH+
size(RLC SDU)
End
Fig. 17 RLC SDU volume measurement principle in DL

- RLC_SDU_VOL_DL_DCCH which is updated on the transmission of an RLC SDU on DL DCCH
towards the UE. Size of DL RLC SDU's mapped to SRB1 and 2 is counted (see Fig.17).
- RLC_SDU_VOL_DL_DTCH which is updated on the transmission of an RLC SDU on DL-DTCH
towards the UE. Size of DL RLC SDU's mapped to DRB is counted (see Fig.17).
02 February 2016
11.10.4 RLC SDU Volume in UL
Successful reception of the

RLC SDU from UE
Is the RLC SDU size greater than

NO
maximum limit (8193 bytes)?
Is the RLC SDU mapped to DRB?
NO
YES
RLC_SDU_VOL_UL_DTCH+
size(RLC SDU)
Is the RLC SDU mapped to SRB1 or

2?
YES
RLC_SDU_VOL_UL_DCCH+
size(RLC SDU)
NO
YES
End
Fig. 18 RLC SDU volume measurement principle in UL

- RLC_SDU_VOL_UL_DCCH which is updated on successful reception of an RLC SDU in RLC AM on
DCCH from UE. Size of UL RLC SDU's mapped to SRB1 and 2 is counted. If size of a received RLC
SDU is greater than maximum RLC SDU size (8193 bytes), the RLC SDU is discarded and not
counted by the counter (see Fig. 18).
- RLC_SDU_VOL_UL_DTCH which is updated on the reception of an RLC SDU both in RLC AM and
UM on UL-DTCH from UE. Size of UL RLC SDU's mapped to DRB is counted. If size of a received
02 February 2016
RLC SDU is greater than maximum RLC SDU size (8193 bytes), the RLC SDU is discarded and not
counted by the counter (see Fig. 18).
11.11 Number of PDCP SDUs Measurement

11.11.1 Number of Transmitted PDCP SDUs in DL

- PDCP_SDU_DL
- PDCP_SDU_DL_QCI_1 - PDCP_SDU_DL_QCI_9.
The principle is shown in the Fig. 19 and follows the principles for the PDCP SDU volume measurement
which are part of the chapter 11.9.1.
02 February 2016
PDCP SDU has been

received in PDCP layer.

AM?
Has the RLC successfully mapped

YES the PDCP PDU to RLC PDU(s)?
YES
Has PDCP received ACK for the
PDCP SDU from RLC layer?
PDCP_SDU_DL++
PDCP_SDU_DL_QCI_x ++
NO
YES
PDCP_SDU_DL++
PDCP_SDU_DL_QCI_x ++ where x ranges from 1 to 9
NO according to the QCI the
transmitted PDCP SDU
belongs to.
End
Fig. 19 Number of PDCP SDUs measurement principle in DL
Note: Please refer also to note in the chapter 11.9.1.
11.11.2 Number of Lost PDCP SDUs in DL

- PDCP_SDU_LOSS_DL_FNA
- PDCP_SDU_LOSS_DL_QCI_1_FNA - PDCP_SDU_LOSS_DL_QCI_9_FNA.
The principle of measurement is shown in the Fig. 20.

02 February 2016
At least a part of the PDCP

SDU transmitted to lower
layers towards the UE.

AM?
Has a final HARQ NACK for an RLC

YES SDU (PDCP PDU) been received for
the corresponding PDCP SDU.
YES
Has PDCP received NACK (max # re-
transmissions reached) for the PDCP
SDU from RLC layer? PDCP_SDU_LOSS_DL_FNA++
PDCP_SDU_LOSS_DL_QCI_x_FNA ++
NO
YES
- where x ranges from 1 to 9

PDCP_SDU_LOSS_DL_FNA++ according to the QCI the
PDCP_SDU_LOSS_DL_QCI_x_FNA ++ transmitted PDCP SDU
NO belongs to.
- triggered after it was
decided during time period
that no more transmission
attempts will be done.
End
Fig. 20 Number of lost PDCP SDUs measurement principle in DL
Common note to chapter 11.1.1 and 11.11.2:
1. If transmission of a PDCP SDU might continue in another cell no one from the counters in the chapters is
triggered.
2. In case of RLC AM and maximum number of re-transmissions reached normally an intra cell handover
procedure shall follow leading to zero number of lost PDCP SDUs.
11.11.3 Number of Discarded PDCP SDUs in DL

- PDCP_SDU_DL_DISC
02 February 2016
- PDCP_SDU_DISC_DL_QCI_1 - PDCP_SDU_DISC_DL_QCI_4.
PDCP SDU has been

received from IP layer in DL.
Has the PDCP SDU been removed NO

from the eNB without having started
the transmission towards RLC layer.
YES - x ranges from 1 to 4

according to the QCI the
PDCP SDU in DL belongs to.
PDCP_SDU_DL_DISC++
PDCP_SDU_DISC_DL_QCI_x++
End
Fig. 21 Number of discarded PDCP SDUs measurement principle in DL
11.11.4 Number of Transmitted PDCP SDUs in UL

- PDCP_SDU_UL
- PDCP_SDU_UL_QCI_1 - PDCP_SDU_UL_QCI_9.
The principle is shown in the Fig. 22 and follows the principles for the PDCP SDU volume measurement
which are part of the chapter 11.9.2.
02 February 2016
RLC layer created the RLC

SDU (PDCP PDU) from the
received RLC PDUs in UL.
Is the created PDCP PDU evaluated NO

as successfully received.
YES x ranges from 1 to 9

received PDCP SDU
PDCP_SDU_UL++ belongs to.
PDCP_SDU_UL_QCI_x++
End
Fig. 22 Number of PDCP SDUs measurement principle in UL
11.11.5 Number of Lost PDCP SDUs in UL

- PDCP_SDU_LOSS_UL_FNA
- PDCP_SDU_LOSS_UL_QCI_1_FNA - PDCP_SDU_LOSS_UL_QCI_9_FNA.

02 February 2016
Processing the PDCP SDUs/

PDUs from the received RLC
SDUs.
Is the UL PDCP sequence number NO

representing PDCP SDU that is not
delivered to higher layers missing?,
- triggering is not done if

transmission of a PDCP
YES SDU might continue in
another cell
- x ranges from 1 to 9
PDCP_SDU_LOSS_UL_FNA++ received PDCP SDU
PDCP_SDU_LOSS_UL_QCI_x_FNA ++ belongs to.
End
Fig. 23 Number of lost PDCP SDUs measurement principle in UL
11.12 CQI Measurement

11.12.1 CQI Distribution Measurement
- UE_REP_CQI_LEVEL_01 - UE_REP_CQI_LEVEL_15.
Valid CQI report received

from the UE.
x ranges from 1 to 15 and

selection is done according
UE_REP_CQI_LEVEL_x++ to the bin the received CQI
falls to.
End
Fig. 24 CQI distribution measurement principle

02 February 2016
Notes to chapter 11.12.1:
1. Only wideband CQI reports triggered the counters.

2. In case of spatial multiplexing MIMO the counters are triggered both for wideband CQI report for
codeword 0 and 1.
3. In case of TM3 related to open loop MIMO the PUCCH reporting mode: MODE_1_0 is used and only first
CW (CW0) is reported. The CW1 reporting is completely skipped in this case.
11.12.2 CQI Offset Measurement

- CQI_OFF_MAX,
- CQI_OFF_MIN,
- CQI_OFF_MEAN.
02 February 2016
- calculation is done according to

deltaCQI has been an internal eNB algorithm (link
caclualted. adaption process from outer loop
link adaptation)
- the intention is to correct

channel quality estimation
provided by the UE.
NO
Is the deltaCQI < CQI_OFF_MIN?
YES
CQI_OFF_MIN = deltaCQI
Is the deltaCQI > CQI_OFF_MAX?
YES
CQI_OFF_MAX = deltaCQI
Numerator(CQI_OFF_MIN)+ deltaCQI value by the total number of
calculated deltaCQIs.
End
Fig. 25 CQI offset measurement principle

11.13 PRB Measurement

11.13.1 PRB Measurement in DL

- DL_PRB_UTIL_TTI_LEVEL_1 - DL_PRB_UTIL_TTI_LEVEL_10,
- DL_PRB_UTIL_TTI_MAX,
- DL_PRB_UTIL_TTI_MEAN,
- DL_PRB_UTIL_TTI_MIN,
- PRB_USED_DL_TOTAL,
02 February 2016
- PRB_USED_PDSCH,
- E_ICIC_DL_PRB_UTIL_LEVEL_1 - E_ICIC_DL_PRB_UTIL_LEVEL_10.
1. The DL_PRB_UTIL_TTI_LEVEL_1 - DL_PRB_UTIL_TTI_LEVEL_10, DL_PRB_UTIL_TTI_MAX,

DL_PRB_UTIL_TTI_MEAN, DL_PRB_UTIL_TTI_MIN and PRB_USED_DL_TOTAL are triggered in ABS with PRBs
from
- system info scheduling
- paging
- SRB0 transmission
- RA Resp transmission
for the cells that are configured as macro ones in the eICIC partnership.
2. The PRB_USED_PDSCH is triggered in ABS with PRBs from SRB0 transmission for the cells that are configured
as macro ones in the eICIC partnership.
3. The E_ICIC_DL_PRB_UTIL_LEVEL_1 - E_ICIC_DL_PRB_UTIL_LEVEL_10 are triggered for the cell that is
configured as micro / small one in the eICIC partnership and for CRE UE which is an UE located in the range
expansion area of the small cell.
4. In relation to previous point 3 it shall be noted the eNB scheduler may decide to use the resources in the DL
ABSs also for non CRE UEs which does not trigger the E_ICIC_DL_PRB_UTIL_LEVEL_1 -
E_ICIC_DL_PRB_UTIL_LEVEL_10.
5. In addition to eICIC counters related PRB utilization ratio there are also counters E_ICIC_MUTING_PATTERN_0
- E_ICIC_MUTING_PATTERN_6 related to muting pattern (which ranges from 0 to 6) activation time.
11.13.2 PRB Measurement in UL

- UL_PRB_UTIL_TTI_LEVEL_1 - UL_PRB_UTIL_TTI_LEVEL_10,
- UL_PRB_UTIL_TTI_MAX,
- UL_PRB_UTIL_TTI_MEAN,
- UL_PRB_UTIL_TTI_MIN,
- PRB_USED_UL_TOTAL,
- PRB_USED_PUSCH,
- E_ICIC_UL_PRB_UTIL_LEVEL_1 - E_ICIC_UL_PRB_UTIL_LEVEL_10.

02 February 2016
1. The E_ICIC_UL_PRB_UTIL_LEVEL_1 - E_ICIC_UL_PRB_UTIL_LEVEL_10 are triggered for the cell that is

configured as micro / small one in the eICIC partnership and for CRE UE which is an UE located in the range
expansion area of the small cell.
2. Under UL ABS a sub-frame that occured after 4ms to the corresponding ABS in DL direction (when no PUSCH
scheduling shall be done for UEs in macro cell) is meant. Thus small cell shall benefit from that as in the UL
ABSs the UL interference coming from UEs served by macro cell shall be siginifcantly decreased.
3. Regarding the TDD part under UL ABS a sub-frame that occured after 4 or 6 ms (depending on TDD
configuration) to the corresponding ABS in DL direction (when no PUSCH scheduling shall be done for UEs in
macro cell) is meant.
02 February 2016
PRBs have been allocated in

the TTI in DL direction.
- no special counting for PDCCH is needed as it is

represented by up to 3 OFDM symbols in the first
slot of the radio sub-frame.
Obtain the following numbers from the
allocated PRBs: - no special counting for the SRB1 and 2 is needed
- AllocatedUePrbs, as it is included within the PRBs allocated for the
- SysInfoPrbs (used for SIBs), UE (AllocatedUePrbs).
- PagingPrbs,
- RaRespPrbs (used for RA response), - the PRB pair in the two consecutive slots is
- srb0 Prbs. counted as one.
The (AllocatedUePrbs+srb0 Prbs
+SysInfoPrbs+PagingPrbs+RaRespPrbs )/
DL_PRB_UTIL_TTI_LEVEL_x++, depending on the bin x the calculated
(Configured number of PRBs in DL)x100%
(AllocatedUePrbs+srb0 Prbs +SysInfoPrbs+PagingPrbs+RaRespPrbs )/(Configured
equal to zero triggers the
number of PRBs in DL)x100% falls to.
DL_PRB_UTIL_TTI_LEVEL_1
E_ICIC_DL_PRB_UTIL_LEVEL_x++, depending on the bin x the calculated

(AllocatedUePrbs+srb0 Prbs)/(Configured number of PRBs for PDSCH)x100% falls to. The (AllocatedUePrbs+srb0 Prbs )/(Configured
number of PRBs for PDSCH)x100% equal to
zero triggers the
E_ICIC_DL_PRB_UTIL_LEVEL_x
Is the (AllocatedUePrbs+srb0 Prbs

> DL_PRB_UTIL_TTI_MAX
YES
DL_PRB_UTIL_TTI_MAX=(AllocatedUePrbs+srb0 Prbs
+SysInfoPrbs+PagingPrbs+RaRespPrbs )/(Configured number
of PRBs in DL)x100%
NO
Is the (AllocatedUePrbs+srb0 Prbs

< DL_PRB_UTIL_TTI_MIN
YES
DL_PRB_UTIL_TTI_MIN=(AllocatedUePrbs+srb0 Prbs
+SysInfoPrbs+PagingPrbs+RaRespPrbs )/(Configured
number of PRBs in DL)x100% At the end of the
NO measurement period a total
Numerator(DL_PRB_UTIL_TTI_MEAN)= average is calculated by
Numerator(DL_PRB_UTIL_TTI_MEAN)+(AllocatedUePrbs+srb0 Prbs dividing this accumulated
+SysInfoPrbs+PagingPrbs+RaRespPrbs )/(Configured number of PRBs in DL)x100% value by the total number of
TTIs.
PRB_USED_PDSCH =
PRB_USED_PDSCH+(AllocatedUePrbs+srb0 Prbs)
PRB_USED_DL_TOTAL =
PRB_USED_DL_TOTAL+(AllocatedUePrbs+srb0 Prbs
+SysInfoPrbs + PagingPrbs + RaRespPrbs)
End
Fig. 26 Principle of the PRB measurement in DL per one TTI

02 February 2016
PRBs have been allocated in - special counting for PUCCH is needed as it is

the TTI in UL direction. represented by the PRBs transmitted separately
from the PUSCH at the edge of the configured
bandwidth.
Obtain the following numbers from the allocated - no special counting for the SRB1 and 2 is needed
PRBs: as it is included within the PRBs allocated for the
- AllocatedUePrbs (PUCCH PRBs excluded, UE (AllocatedUePrbs).
- PUCCHPrbs,
- RaPrbs (used for preamble), - the PRB pair in the two consecutive slots is
- srb0 Prbs. counted as one.
The (AllocatedUePrbs+srb0
Prbs+PUCCHPrbs+RaPrbs )/
UL_PRB_UTIL_TTI_LEVEL_x++, depending on the bin x the calculated
(Configured number of PRBs in
(AllocatedUePrbs+srb0 Prbs+PUCCHPrbs+RaPrbs )/(Configured number of PRBs in
UL)x100% equal to zero triggers the
UL)x100% falls to.
UL_PRB_UTIL_TTI_LEVEL_1
The (AllocatedUePrbs+srb0 Prbs )/

E_ICIC_UL_PRB_UTIL_LEVEL_x++, depending on the bin x the calculated
(Configured number of PRBs for
(AllocatedUePrbs+srb0 Prbs)/(Configured number of PRBs for PUSCH)x100% falls to.
PUSCH)x100% equal to zero
triggers the
E_ICIC_UL_PRB_UTIL_LEVEL_1
Is the (AllocatedUePrbs+srb0
Prbs+PUCCHPrbs+RaPrbs )/(Configured
number of PRBs in UL)x100% >
UL_PRB_UTIL_TTI_MAX
YES
UL_PRB_UTIL_TTI_MAX=(AllocatedUePrbs+
srb0 Prbs+PUCCHPrbs+RaPrbs )/(Configured
number of PRBs in UL)x100%
NO
Is the(AllocatedUePrbs+srb0
Prbs+PUCCHPrbs+RaPrbs )/(Configured
number of PRBs in UL)x100% <
UL_PRB_UTIL_TTI_MIN
YES
UL_PRB_UTIL_TTI_MIN=(AllocatedUePrbs+srb0
Prbs+PUCCHPrbs+RaPrbs )/(Configured number of
PRBs in UL)x100% At the end of the
NO
Numerator(UL_PRB_UTIL_TTI_MEAN)= average is calculated by
Numerator(UL_PRB_UTIL_TTI_MEAN)+(AllocatedUePrbs+srb0 dividing this accumulated
Prbs+PUCCHPrbs+RaPrbs )/(Configured number of PRBs in UL)x100% value by the total number of
TTIs.
PRB_USED_PUSCH =
PRB_USED_PUSCH+(AllocatedUePrbs+srb0 Prbs)
PRBs which are used for
PRB_USED_UL_TOTAL = both PUCCH and PRACH
PRB_USED_UL_TOTAL+(AllocatedUePrbs+srb0 Prbs + are not counted twice.
PUCCHPrbs + RaPrbs)
End
Fig. 27 Principle of the PRB measurement in UL per one TTI

02 February 2016
11.14 Active UEs with Data in the Buffer Measurement

11.14.1 Active UEs with Data in the Buffer Measurement in DL
- SUM_ACTIVE_UE_DATA_DL
- DENOM_ACTIVE_UE_DATA_DL
- DL_UE_DATA_BUFF_AVG
- UE_DRB_DL_DATA_QCI_1 - UE_DRB_DL_DATA_QCI_4
- UE_DRB_DL_DATA_NON_QCI
- DL_UE_DATA_BUFF_MAX.
11.14.2 Active UEs with Data in the Buffer Measurement in UL

- SUM_ACTIVE_UE_DATA_UL
- DENOM_ACTIVE_UE_DATA_UL
- UL_UE_DATA_BUFF_AVG
- UE_DRB_UL_DATA_QCI_1
- UE_DRB_UL_DATA_NON_QCI
- UL_UE_DATA_BUFF_MAX.

1. Counters SUM_ACTIVE_UE_DATA_DL, DENOM_ACTIVE_UE_DATA_DL and SUM_ACTIVE_UE_DATA_UL,

DENOM_ACTIVE_UE_DATA_UL provide the averaged number of active UEs with data in the buffer per
measurement period in DL and UL, respectively.
2. Counters UE_DRB_DL_DATA_QCI_1 - UE_DRB_DL_DATA_QCI_4, UE_DRB_DL_DATA_NON_QCI and
UE_DRB_UL_DATA_QCI_1, UE_DRB_DL_DATA_NON_QCI, DL_UE_DATA_BUFF_AVG and
UL_UE_DATA_BUFF_AVG provide the averaged number of active UEs with data in the buffer per active
cell time in DL and UL, respectively.
3. For the counters from the previous point 2 the number of active UEs with data in the buffer is only
measured for the TTIs where at least one UE is scheduled (for the exact definition see the flow diagrams
in the Fig. 28 and 29). I.e. in the case there are some UE(s) with data in the buffer but in the observed TTI
no UE scheduled the TTI is completely excluded from the measurement.
02 February 2016
4. In UL the measurement is feasible only per QCI1 and nonGBR services as there are some UEs with data in
the buffer or not is evaluated from scheduling report message from UE which is reported per LCG (not per
QCI).
5. As it can be seen from the principle flow diagrams the triggering of the counters that are part of the
chapters is based on two sampling periods. First one ensuring the triggering per TTI and the second one (4
seconds in DL and 4,096 seconds in UL) upon which the sub-results (except the
SUM_ACTIVE_UE_DATA_DL and SUM_ACTIVE_UE_DATA_UL which are reported only once and it at the
end of measurement period) are reported from MAC sub-system to another sub-system that accumulates
all the sub-results and reports the final results at the end of measurement period.
6. In relation to previous point therefore in case the measurement period is not compact multiple of the 4
seconds in DL and 4,096 seconds in UL the reporting does not need to be done for the complete
measurement period. In the worst case last 4 seconds in DL and 4,096 seconds in UL are completely
excluded from measurement.
7. In relation to previous point and regarding the average value counters because the same excluding is
done both from numerator and denominator the resultant error shall be negligible (one exception
mentioned in the next point). Regarding the max value counters in case the maximum value occurred in
the last unreported interval this may lead to some non negligible error.
8. The numerator counter (SUM_ACTIVE_UE_DATA_DL and SUM_ACTIVE_UE_DATA_UL) is
reported/obtained with resolution 1 ms while the denominator one DENOM_ACTIVE_UE_DATA_DL with 4
seconds resolution (DENOM_ACTIVE_UE_DATA_UL with 4.096 seconds resolution). Thus the precision of
the results obtained with this KPI may not be higher than two digits, or that the absolute error is up to ±
0.005.
02 February 2016
eNB internally in the

MAC sub-system Measurement period has
measures the total started.
and number of active i=1,
UEs with data in the
RLC buffer on a per Measure the following in the i-th TTI:
QCI basis in DL. - NumUEDataBufferDL
- NumUEDataBufferQCI1DL
- NumUEDataBuffernonGBRDL
Update the following counters:

- SUM_ACTIVE_UE_DATA_DL = SUM_ACTIVE_UE_DATA_DL + NumUEDataBufferDL
- DENOM_ACTIVE_UE_DATA_DL++
- Numerator(DL_UE_DATA_BUFF_AVG) = Numerator(DL_UE_DATA_BUFF_AVG) +
NumUEDataBufferDL
- Numerator(UE_DRB_DL_DATA_QCI_1) = Numerator(UE_DRB_DL_DATA_QCI_1) + NO
NumUEDataBufferQCI1DL
- Numerator(UE_DRB_DL_DATA_QCI_2) = Numerator(UE_DRB_DL_DATA_QCI_2) +
- Numerator(UE_DRB_DL_DATA_NON_QCI) =
Numerator(UE_DRB_DL_DATA_NON_QCI) + NumUEDataBuffernonGBRQCIDL
Is the NumUEDataBufferDL>
DL_UE_DATA_BUFF_MAX
YES
DL_UE_DATA_BUFF_MAX + NumUEDataBufferDL
SUM_ACTIVE_UE_DATA_DL = 0
NO DENOM_ACTIVE_UE_DATA_DL = 0
Numerator(DL_UE_DATA_BUFF_AVG) = 0
i = 4000 NumeratorUE_DRB_DL_DATA_QCI_1) = 0
Numerator(UE_DRB_DL_DATA_QCI_2) = 0
YES Numerator(UE_DRB_DL_DATA_QCI_3) = 0
Report all the counters (except the SUM_ACTIVE_UE_DATA_DL) internally within the Numerator(UE_DRB_DL_DATA_QCI_4) = 0
eNB from MAC subsystem to a sub-system that accumulates the measurement results Numerator(UE_DRB_DL_DATA_NON_QCI) = 0
and consequently reset the counters (except the DL_UE_DATA_BUFF_MAX) in MAC. i=1
SUM_ACTIVE_UE_DATA_DL is reported at
the end of measurement period with 1 ms
End of Measurement period? NO resolution
YES
Report the final results at the end of measurement period:
- SUM_ACTIVE_UE_DATA_DL, DENOM_ACTIVE_UE_DATA_DL,
DL_UE_DATA_BUFF_MAX - ActiveTTIsDLprovides total number
- Numerator(DL_UE_DATA_BUFF_AVG)/ActiveTTIsDL of TTIs, i.e. the TTIs there was at
least one UE scheduled in DL and at
- Numerator(UE_DRB_DL_DATA_QCI_1)/ActiveTTIsDL least one of its DRBs contained
- Numerator(UE_DRB_DL_DATA_QCI_2)/ActiveTTIsDL data.
- Numerator(UE_DRB_DL_DATA_QCI_3)/ActiveTTIsDL
- Numerator(UE_DRB_DL_DATA_QCI_4)/ActiveTTIsDL
- Numerator(UE_DRB_DL_DATA_NON_QCI)/ActiveTTIsDL
End
Fig. 28 Principle of the active UEs with data in the buffer measurement in DL
02 February 2016
eNB internally in the

MAC sub-system Measurement period has
measures the total started.
and number of active i=1,
UEs with data in the
RLC buffer on a per Measure the following in the i-th TTI:
QCI basis in UL. - NumUEDataBufferUL
- NumUEDataBufferQCI1UL
- NumUEDataBuffernonGBRUL

- SUM_ACTIVE_UE_DATA_UL = SUM_ACTIVE_UE_DATA_UL + NumUEDataBufferUL
- DENOM_ACTIVE_UE_DATA_UL++
- Numerator(UL_UE_DATA_BUFF_AVG) = Numerator(UL_UE_DATA_BUFF_AVG) +
NumUEDataBufferUL NO
- Numerator(UE_DRB_UL_DATA_QCI_1) = Numerator(UE_DRB_UL_DATA_QCI_1) +
NumUEDataBufferQCI1UL
- Numerator(UE_DRB_UL_DATA_NON_QCI) =
Numerator(UE_DRB_UL_DATA_NON_QCI) + NumUEDataBuffernonGBRQCIUL
Is the NumUEDataBufferUL>
UL_UE_DATA_BUFF_MAX
YES
UL_UE_DATA_BUFF_MAX + NumUEDataBufferUL
NO
SUM_ACTIVE_UE_DATA_UL = 0
i = 4096 DENOM_ACTIVE_UE_DATA_UL = 0
Numerator(UL_UE_DATA_BUFF_AVG) = 0
YES NumeratorUE_DRB_UL_DATA_QCI_1) = 0
Numerator(UE_DRB_UL_DATA_NON_QCI) = 0
Report all the counters (except the SUM_ACTIVE_UE_DATA_UL ) internally within the i=1
eNB from MAC subsystem to a sub-system that accumulates the measurement results
and consequently reset the counters (except the UL_UE_DATA_BUFF_MAX) in MAC. SUM_ACTIVE_UE_DATA_UL is
reported at the end of measurement
period with 1 ms resolution
End of Measurement period? NO
YES
Report the final results at the end of measurement period: - ActiveTTIsULprovides total number
- SUM_ACTIVE_UE_DATA_UL, DENOM_ACTIVE_UE_DATA_UL, of TTIs, i.e. the TTIs there was at
UL_UE_DATA_BUFF_MAX least one UE scheduled in UL and
- Numerator(UL_UE_DATA_BUFF_AVG)/ActiveTTIsUL at least one of its DRBs contained
data.
- Numerator(UE_DRB_UL_DATA_QCI_1)/ActiveTTIsUL
- Numerator(UE_DRB_UL_DATA_NON_QCI)/ActiveTTIsUL
End
Fig. 29 Principle of the active UEs with data in the buffer measurement in UL
02 February 2016
11.15 Active Scheduled UEs Measurement

11.15.1 Active Scheduled UEs Measurement in DL
- SUM_ACT_UE_SCHED_DATA_DL
- DENOM_ACT_UE_SCHED_DATA_DL
eNB internally in the Measurement period has

MAC sub-system started.
measures the i=1,
number of scheduled
UEs in DL.
Measure the following in the i-th TTI:
- NumUEScheduledDL

- SUM_ACT_UE_SCHED_DATA_DL = SUM_ACT_UE_SCHED_DATA_DL +
NumUEScheduledDL
- DENOM_ACT_UE_SCHED_DATA_DL++
NO
End of Measurement period?
YES
SUM_ACT_UE_SCHED_DATA_DL = 0
Report the final results at the end of measurement period: DENOM_ACT_UE_SCHED_DATA_DL = 0
- SUM_ACT_UE_SCHED_DATA_DL,
- DENOM_ACT_UE_SCHED_DATA_DL.
End
Fig. 30 Principle of the scheduled UEs measurement in DL

02 February 2016
11.15.2 Active Scheduled UEs Measurement in UL

- SUM_ACT_UE_SCHED_DATA_UL
- DENOM_ACT_UE_SCHED_DATA_UL
eNB internally in the Measurement period has

MAC sub-system started.
measures the i=1,
number of scheduled
UEs in UL.
Measure the following in the i-th TTI:
- NumUEScheduledUL

- SUM_ACT_UE_SCHED_DATA_UL = SUM_ACT_UE_SCHED_DATA_UL + NO
NumUEScheduledDL
- DENOM_ACT_UE_SCHED_DATA_UL++
End of Measurement period?
YES
SUM_ACT_UE_SCHED_DATA_UL = 0
Report the final results at the end of measurement period: DENOM_ACT_UE_SCHED_DATA_UL = 0
- SUM_ACT_UE_SCHED_DATA_UL,
- DENOM_ACT_UE_SCHED_DATA_UL.
End
Fig. 31 Principle of the scheduled UEs measurement in UL

02 February 2016
11.16 Active UEs with Activated SCell(s) Measurement

- CA_SCELL_ACTIVE_UE_AVG
- CA_2SCELLS_ACTIVE_UE_AVG
Time to trigger
CA_SCELL_ACTIVE_UE_AVG and
CA_2SCELLS_ACTIVE_UE_AVG The counters are triggered
counter with the sampling period 1
second.
eNB measures internally the number of UEs with At the end of the
activated one and two SCells (NumUEsActiveSCell measurement period a total
and NumUEsActive2SCels) in the TTI under average is calculated by
consideration at the time to trigger. dividing this accumulated
Numerator(CA_SCELL_ACTIVE_UE_AVG) = Numerator(CA_SCELL_ACTIVE_UE_AVG) + 1 second intervals the
NumUEsActiveSCell counter was updated during
Numerator(CA_2SCELLS_ACTIVE_UE_AVG) = Numerator(CA_2SCELLS_ACTIVE_UE_AVG) + the measurement period.
NumUEsActive2SCells
End
Fig. 32 Principle of the active UEs with activated SCell(s) measurement in one sampling interval
Notes to chapter 11.16:
1. If a 3CC UE has only one SCell activated this is counted in CA_SCELL_ACTIVE_UE_AVG.

2. The reported value is 100 times higher than the actual value (for example 1.00 is stored as 100).
11.17 End User Throughput Measurement
IP Scheduled Throughput Measurement in DL

- IP_TPUT_VOL_DL_QCI_1 - IP_TPUT_VOL_DL_QCI_9 (so called Volume IP scheduled throughput
counters)
- IP_TPUT_TIME_DL_QCI_1 - IP_TPUT_TIME_DL_QCI_9 (so called Time IP scheduled throughput
counters)
-
02 February 2016
The principle of measurement is shown in the Fig. 33. The end user throughput is calculated per QCI by
calculating the ratio of the volume (ThpVolDl) and corresponding time counter (ThpTimeDl), e.g. for the
QCI1 as counter IP_TPUT_VOL_DL_QCI_1/ IP_TPUT_TIME_DL_QCI_1.
Successful transmission,
buffer not empty
The last data unit
Failed transmission ( ” Block TTI shall always be
error ”) ThpTimeDl removed from
calulations since it
Successful transmission,
can be impacted
buffer empty
by packet size of
User Plane (UP) packets.
No transmission, buffer not
empty (e.g. due to contention)
Data arrives to Time (ms)

empty DL buffer
First data is The send buffer is

transmitted to the UE again empty
∑
ThpVolDl = (kbits)
Total DL transferred volume = ∑ + (kbits)
IP Throughput in DL = ThpVolDl / ThpTimeDl (kbits/s)
Fig. 33 Principle of IP scheduled throughput measurement in DL
IP Scheduled Throughput Measurement in UL

- IP_TPUT_VOL_UL_QCI_1 - IP_TPUT_VOL_UL_QCI_9 (so called Volume IP scheduled throughput
counters)
- IP_TPUT_TIME_UL_QCI_1 - IP_TPUT_TIME_UL_QCI_9 (so called Volume IP scheduled
throughput counters)
The principle of measurement is similar to one in DL according to Fig. 33. The end user throughput is
calculated per QCI by calculating the ratio of the volume and corresponding time counter, e.g. for the
QCI1 as counter IP_TPUT_VOL_UL_QCI_1/ IP_TPUT_TIME_UL_QCI_1.
02 February 2016
IP Throughput Measurement in DL
- IP_TPUT_NET_TIME_DL_QCI_1- IP_TPUT_NET_TIME_DL_QCI_9 (so called Time IP throughput
counters)
The time IP throughput measurement is similar to the one mentioned in the chapter 11.17.1 with the
only difference that TTIs where UE was scheduled per the evaluated QCI are counted. The rest of the
conditions to trigger the time IP throughput counters stay unchanged. The end user throughput is
calculated per QCI by calculating the ratio of the volume using the counters from the chapter 11.17.1
and corresponding time counter, e.g. for the QCI1 as counter IP_TPUT_VOL_DL_QCI_1/
IP_TPUT_NET_TIME_DL_QCI_1.
IP Throughput Measurement in UL
- IP_TPUT_NET_TIME_UL_QCI_1- IP_TPUT_NET_TIME_UL_QCI_9 (so called Time IP throughput
counters)
The time IP throughput measurement is similar to the one mentioned in the chapter 11.17.2 with the
only difference that TTIs where UE was scheduled per the evaluated QCI are counted. The rest of the
conditions to trigger the time IP throughput counters stay unchanged. The end user throughput is
calculated per QCI by calculating the ratio of the volume using the counters from the chapter 11.17.2
and corresponding time counter, e.g. for the QCI1 as counter IP_TPUT_VOL_UL_QCI_1/
IP_TPUT_NET_TIME_UL_QCI_1.
1. It shall be noted that there is restriction in DL as only one burst per bearer can be processed at the same
time. In other words said after last part of the burst has been sent to the UE even this was positively ACK
via HARQ to evaluate it is earliest possible within the next 8 ms and during this time interval if there was
another burst no measurement is done for this burst. For instance in case burst duration would be 5 TTIs,
i.e. buffer is emptied in each 5th TTI and bursts are pretty continuous (FTP session) it means that
following one by one. Then the burst 1 starts to be processed at the TTI #8 according to the following
Tab.1 below and this burst gets completely processed in case of positive ACK HARQ for each part at the
TTI # 12. It means that the second burst is completely excluded from the measurement and the earliest
burst that starts to be processed is the 3rd one from its 4th TTI (TTI # 13 in the below table).
02 February 2016
TTI Buffer status after TTI HARQ ACK for Burst measuring
0 1000 Burst 1 measuring starts
1 2000 Burst 1 measuring
8 3000 TTI0 Burst 1 measuring

12 1000 TTI4 Burst 1 measuring ends
(but this TTI excluded)
13 3000 TTI5 Burst 3 measuring starts
Tab. 1 Restriction in the DL end user throughput measurement where TTIs with the buffer status after the
TTI marked in green are processed while the ones in red are completely excluded. Buffer status values
are marked just for illustration. Zero means that the TTI is the last one in the burst and empting the
buffer.
2. In relation to previous point Nokia’s implementation of the IP scheduled throughput in DL is not fully
compliant to 3GPP TS 36.314.
3. Successful transmission in DL direction means HARQ acknowledged by UE while in UL direction successful

reception of the PDCP SDU.
11.18 Active Cell Time Measurement

Active Cell Time Measurement in DL
02 February 2016

- ACTIVE_TTI_DL
i-th TTI in DL is to be evaluated

The counter is evaluated in
each TTI in DL within the
measurement period.
Is the i-th TTI

active one?
- Increment in each TTI in which PDSCH
YES and PDCCH are allocated for at least one
UE to receive DRB data. Active TTI DL
ACTIVE_TTI_DL++ means, if there was user-data (only data
on DRB, RLC control data not excluded;
SRB data transfers are not considered) to
be scheduled within a TTI for transmission
in DL (independent from the number of
active UEs),
End - at the end of measurement period a total
accumulated value is reported.
Fig. 34 Principle of active cell time measurement per TTI in DL
Active Cell Time Measurement in UL

- ACTIVE_TTI_UL

02 February 2016
i-th TTI in UL is to be evaluated

each TTI in UL within the
measurement period.
Is the i-th TTI

active one?
- Incremented in every active TTI, in which
YES PUSCH is allocated at least for one UE to
transmit DRB data excluding random access
ACTIVE_TTI_UL++ msg3/first scheduled uplink transmisson. Active
TTI UL means, if there was user-data (only data
on DRB, RLC control data not excluded; SRB
data transfers are not considered) to be
scheduled within a TTI for transmission in UL
(independent from the number of active UEs).
End - at the end of measurement period a total
Fig. 35 Principle of active cell time measurement per TTI in UL
11.19 Interference Shaping Related Measurements

- DL_INTERFER_SHAP_USE,
- DL_INTERFER_SHAP_AMOUNT,
- DL_INTERFER_SHAP_CHANGE.

02 February 2016
i-th TTI in DL is to be evaluated

each TTI in DL within the
measurement period.
Is the i-th TTI the one where DL

scheduling is restricted to the preferred
area as a result of the DL Interference
Shaping feature.?
YES
Has the Preferred Area Size been

increased or decreased?
YES - Check if the preferred area size needs to be

increased or decreased is done by checking if
the current RBG utilization exceeds the
DL_INTERFER_SHAP_CHANGE++ configured upper or lower limit.
NO - at the end of measurement period a total
NO accumulated value is reported.
DL_INTERFER_SHAP_USE++ - at the end of measurement period a total
DL_INTERFER_SHAP_AMOUNT+ - deltPRB is obtained in each TTI via
deltPRB rrmDlIshPrefAreaSize which represents the
size of the preferred area in number of RBGs.
- at the end of measurement period a total
End
Fig. 36 Principle of interference shaping measurement per TTI in DL

02 February 2016
12. References
[1] RL60 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] RL60/RL45TD 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

02 February 2016
13. Appendix
List of the Trigger Events Related to DRB and E-RAB Release Counters
This chapter presents a list of the trigger events related to DRB and E-RAB release counters. The intention
is to show all causes why the DRB/E-RAB release may happen despite at the final end the counters are
mainly triggered with either E-RAB Release Indication or UE Context Release request (initiated by eNB)
and E-RAB Release Command and UE Context Release Command (initiated by MME/EPC) from eNB to
MME and from MME to eNB, respectively. This detailed view is needed as those counters are crucial for
DRB/E-RAB drop KPIs calculation as one from the most important benchmarking KPIs showing the network
performance.
List of the Trigger Events Related to eNB initiated DRB and E-RAB Release
Counters
In the following table all possible causes that may trigger DRB and E-RAB Release Counters initiated by
eNB are shown.
Counter name Cause Value Use Case Description Detailed description
RB_REL_REQ_RNL RNL Ongoing X2 handover is The UE context and all the related E-
ENB_EPS_BEARER_REL_REQ_RNL Unspecified aborted for any reason RABs released and counted at the source
ENB_EPS_BEAR_REL_REQ_R_QCI1 sent within where the UE has left the cell.
ENB_INIT_TO_IDLE_RNL the UE source cell and is not
Context allowed to return
Release Ongoing S1 handover is The UE context and all the related E-
Request aborted for any reason RABs released and counted at the source
message from where the UE is not cell.
eNB to MME allowed to continue in the
source cell
S1AP: ERROR INDICATION
[syntax error] received at
Source eNB in response
to S1AP: HANDOVER
CANCEL message
Security configuration
becomes permanently
inoperable and no other
defense action is defined
(or was unsuccessful)
Release dependant key
refresh procedure.
02 February 2016
Bearer Modification fails. If the modification of some bearers

failed within the eNB for some reason
and all E-RAB IDs from the received
S1AP: E-RAB MODIFY REQUEST message
are moved on the "E-RAB Failed to
Modify List". The rejection cause for
each E-RAB ID shall be set to "Radio
Network Layer Cause - Unspecified".
And the eNB continues by sending back

to MME the S1AP: E-RAB MODIFY
RESPONSE with all bearers rejected for
modification and sending to MME the
with cause "Radio Network Layer Cause -
Unspecified".
E-RAB Release* An error occurred during the E-RAB
release triggered via E-RAB RELEASE
COMMAND and all the requested DRBs
to be released are moved from “E-RAB
to be Released List” to “E-RAB Failed to
Released List”. The cause shall be set to
"Radio Network Layer Cause -
Unspecified". The S1AP:E-RAB RELEASE
RESPONSE is send to MME.
And the eNB continues by sending S1AP:

UE CONTEXT RELEASE REQUEST with
cause set to "Radio Network Layer
Cause: Unspecified" .
E-RAB Setup Request In case there is an error in bearer setup

and the eNB rejects all the DRBs
requested by E-RAB Setup Request. That
means all the bearers located in “E-RAB
to Be Setup List” will be moved to “E-
RAB Failed to Setup List” with cause
“Radio Network Layer Cause -
Unspecified”.
And the eNB continues with sending the

S1AP:E-RAB SETUP RESPONSE and
S1AP:UE CONTEXT RELEASE REQUEST
with cause "Radio Network Layer Cause -
unspecified".
Inter-RAT handover from S1AP: ERROR INDICATION [“Semantic

LTE to HRPD Error” or “Message not compatible with
receiver state”] during on-going eHRPD-
Opt HO.
02 February 2016
SCell Release for Carrier The SCell of the CA UE is to be released

Aggregation and the reconfiguration of the CA was
for some reason unsuccessful.
SCell Addition for Carrier The SCell of the CA UE is to be added and
Aggregation the reconfiguration of the CA was for
some reason unsuccessful.
RB_REL_REQ_NORM_REL RNL User eNB initiated release due
ENB_EPS_BEARER_REL_REQ_NORM Inactivity sent to user inactivity
ENB_EPS_BEAR_REL_REQ_N_QCI1 within the UE
ENB_INIT_TO_IDLE_NORM_REL Context
Release
Request
message from
eNB to MME
RB_REL_REQ_NORM_REL X2AP UE Target eNB initiated
CONTEXT release due to successful
RELEASE outgoing X2 based HO.
message sent
from target to
source eNB
due to
successful
outgoing X2-
Handover
RB_REL_REQ_NORM_REL RRC UE in the target cell Note: despite this kind of release does
Connection initiated release due to not fit exactly to eNB initiated release
Reconfigurati successful inter cell intra group included in this chapter as occurs
on Complete eNB HO. within the eNB.
message sent
from UE from
target cell to
eNB due to
successful
inter cell intra
eNB
handover.
RB_REL_REQ_RNL RNL Radio eNB-initiated release due eNB detected T_RLF ( T310 + T311) timer
ENB_EPS_BEARER_REL_REQ_RNL Connection to radio link failure expiry due to either PUSCH RLF or
ENB_EPS_BEAR_REL_REQ_R_QCI1 with UE Lost Periodic CQI RLF or Ack/Nack RLF or SRS
ENB_INIT_TO_IDLE_RNL sent within RLF.
the UE Rejection of RRC
Context Connection Re-
Release establishment Request
Request eNB initiated Release due eNB detected that the maximum
message from to UE being out-of-sync number of retries
eNB to (taCommandMaxRetries) for the TA
MME** Update command is exceeded or the
timing alignment timer has expired and
resynchronization of a UE was
unsuccessful.
02 February 2016
Handling of Event eNB detected that the max RLC

“Maximum number of retransmissions has been reached and
RLC retransmissions T311 has expired.
reached”
Timer THOoverall expiry eNB detected THOoverall = T304 + T311
+ T301 + THOoverallDelta expiry where
THOoverallDelta is defined by the
vendor as the estimated time taken to
send the RRC: RRC CONNECTION
RECONFIGURATION message to the UE
plus the time taken for the UE to
generate and send an RRC message in
the target cell.
Source eNB initiates UE If an RRC: RRC CONNECTION RE-
context release due to a ESTABLISHMENT REJECT message has
rejected RRC Connection been sent to the UE in response to the
Re-establishment RRC: RRC CONNECTION RE-
ESTABLISHMENT REQUEST message, the
source eNB shall trigger the eNB
Initiated Context Release procedure with
the MME with Cause value: Radio
Network Layer Cause (Radio Connection
with UE Lost).
RRC Connection Re- If the RRC: RRC CONNECTION RE-

establishment rejected at ESTABLISHMENT REJECT message has
Target eNB for a UE been sent to a UE performing a
performing Measurement Measurement Configuration the target
Configuration eNB shall start the eNB Initiated Context
Release procedure as soon as the S1AP:
PATH SWITCH REQUEST ACKNOWLEDGE
message has been received using Cause
value: Radio Network Layer Cause (Radio
Connection with UE Lost).
The actions taken by the target eNB as a

result of receiving the S1AP: PATH
SWITCH REQUEST ACKNOWLEDGE
message (e.g. sending an X2AP: UE
CONTEXT RELEASE message to the
source eNB) shall continue as described
for the successful case.
Re-establishment during eNb detected interruption of the

E-RAB Setup including the RRCConnectionReconfiguration message
pre-emption of other containing the release of pre-empted
bearers of this UE DRB(s) caused by RRC Connection Re-
establishment according followed with
sending the UE Context Release message
to MME with the cause “RNL Radio
Connection with UE Lost”
02 February 2016
E-RAB Setup Request An error during E-RAB setup indicated by

RRC Connection Reconfiguration guard
timer expiry followed with sending the
UE Context Release message to MME
with the cause “RNL Radio Connection
with UE Lost”
RRC Connection MinLifeTimeOfHalfOpenRrcConnection
Reestablishment in timer has expired as no RRC Connection
serving cell and in HO Reestablishment Complete message
source cell received from UE in time which is
followed with sending the UE Context
Release message to MME with the cause
“RNL Radio Connection with UE Lost”
RRC Connection RRCGuardTimerRadioBearerManagemen
Reconfiguration in serving t timer has expired as no RRC
cell Connection Reconfiguration Complete
message received from UE in time which
is followed with sending the UE Context
E-RAB Modification An error during E-RAB modification
indicated by RRC Connection
Reconfiguration guard timer expiry
followed with sending the UE Context
E-RAB Release* An error during E-RAB release indicated
by RRC Connection Reconfiguration
guard timer expiry. If eNB was triggered
for E-RAB RELEASE COMMAND the eNB
shall move all DRBs from “E-RAB to be
Released List” to “E-RAB Failed to
Release” in S1AP:E-RAB RELEASE
RESPONSE with the cause set to “Radio
Network Layer Cause - Failure in the
Radio Interface Procedure”.
eNB shall additionally send S1AP: UE

CONTEXT RELEASE REQUEST with cause
set to "Radio Network Layer Cause:
Release due to E-UTRAN Generated
Reason"
RB_REL_REQ_RNL RNL Failure in Failure to send RRC The UE context and all the related E-
ENB_EPS_BEARER_REL_REQ_RNL the Radio Connection RABs released and counted at the target
ENB_EPS_BEAR_REL_REQ_R_QCI1 Interface Reconfiguration cell.
ENB_INIT_TO_IDLE_RNL Procedure (Measurement
sent within configuration) at Target
the UE eNB
02 February 2016
Context Handover Handling due to The UE context and all the related E-
Release timer RABs released and counted at the target
Request TRECGuardTimerRadioBearerManage cell.
message from ment expiry
eNB to MME RRC Transaction ID If the RRC transaction Id in the
mismatch. RRCConnection
ReconfigurationComplete is not identical
to the ID sent in the
RRCConnectionReconfiguration, and eNB
puts all E-RAB IDs from the received
S1AP: E-RAB MODIFY REQUEST message
on the "E-RAB Failed to Modify List". The
rejection cause for each E-RAB ID shall
be set to "Failure in the Radio Interface
Procedure".
And the eNB continues with this sending

back to MME the S1AP: E-RAB MODIFY
RESPONSE with all bearers rejected for
modification. And the eNB for this UE
sends to MME the S1AP: UE CONTEXT
RELEASE REQUEST with cause "Radio
Radio Interface Procedure".
SCell Addition for Carrier Addition of the SCell for CA UE failed for
Aggregation some reason (RRC Guard Timer expiry or
RRC Connection Reconfiguration failure
or RRC Transaction ID mismatch) .

back to MME the S1AP: UE CONTEXT
SCell Swap for Carrier SCell swap for CA UE failed for some
Aggregation reason (a timer expiry or RRC Connection
Reconfiguration failure or RRC
Transaction ID mismatch) .

back to MME the S1AP: UE CONTEXT
RNL THOoverall Timer THOoverall expiry at

Expiry sent Source cell in case if intra
within the UE eNB or intra cell HO.
Context
02 February 2016
Release
Request
message from
eNB to MME
Radio E-RAB ID is not assigned eNB rejects the E-RAB RELEASE
Network to an existing DRB. COMMAND for all requested DRBs, and
Layer Cause: all requested DRBs are moved from “E-
Release due RAB to be Released List” to “E-RAB Failed
to E-UTRAN to Released List”. For Bearers which E-
Generated RAB Id is not known the cause is set to
Reason" sent “Unknown E-RAB ID” for others the
within the cause is set to "Release due to E-UTRAN
S1AP: UE Generated Reason".
CONTEXT
RELEASE eNB sends the S1AP: UE CONTEXT
REQUEST RELEASE REQUEST with cause set to
message from "Radio Network Layer Cause: Release
eNB to MME* due to E-UTRAN Generated Reason".
Both UL AMBR and DL eNB rejects the S1AP: E-RAB RELEASE
AMBR are received as 0 COMMAND for all requested DRBs and
all requested DRBs are moved from “E-
RAB to be Released List” to “E-RAB Failed
to Released List”.
eNB sends the S1AP: UE CONTEXT

RELEASE REQUEST with cause set to
"Radio Network Layer Cause: Release
due to E-UTRAN Generated Reason"
RRC Transaction ID RRC Transaction ID received in RRC
mismatch CONNECTION RECONFIGURATION
COMPLETE is not the same comparing
with sent in RRC CONNECTION
RECONFIGURATION. If eNB was triggered
for E-RAB RELEASE COMMAND all the
DRBs shall be moved from “E-RAB to be
Released List” to “E-RAB Failed to
Release” in S1AP:E-RAB RELEASE
RESPONSE with the cause set to “Radio
Radio Interface Procedure”.
eNB shall additionally send S1AP: UE

CONTEXT RELEASE REQUEST with cause
set to "Radio Network Layer Cause:
Release due to E-UTRAN Generated
Reason"
Radio eNB initiated release due UE has no DRB bearer setup and timer
Network to UE Inactivity Detection s1_inactivity expires (e.g. after the TAU).
Layer Cause:
Release due
02 February 2016
to E-UTRAN
Generated
Reason" sent
within the
S1AP: UE
CONTEXT
RELEASE
REQUEST
message from
eNB to MME
RB_REL_REQ_RNL_REDIR RNL E-UTRAN Initiating UE context
ENB_EPSBEAR_REL_REQ_RNL_REDIR Generated release with Redirect to
ENB_EPS_BEAR_REL_REQ_RD_QCI1 Reason sent LTE
ENB_INIT_TO_IDLE_NORM_REL within the UE Initiating UE context
Context release without Redirect
Release (redirection fails)
Request
message from
eNB to MME
RNL Inter-RAT Initiating UE context
Redirection release with Redirect to
sent within other RAT
the UE
Context
Release
Request
message from
eNB to MME
RB_REL_REQ_OTHER TNL Transport Handling of Event “GTP-U eNB received a “GTP-U Error Indication”
ENB_EPS_BEARER_REL_REQ_TNL Resource Error Indication” (S-GW on an active (single) S1 bearer (S-GW has
ENB_EPS_BEAR_REL_REQ_T_QCI1 Unavailable has rejected the rejected the reception of uplink data
ENB_INIT_TO_IDLE_OTHER sent within reception of uplink data packets)
the UE packets)
Context Note: from RL20 onwards, eNB shall stop
Release sending UL data to S-GW for the single
Request and S1 bearer and wait for a timer
E-RAB (configured by R&D parameter) before
Release sending the S1AP message UE CONTEXT
Indication RELEASE REQUEST. This is caused by
message from non-3GPP-compliant UEs that continue
eNB to MME sending UL data though they have
in case all initiated the NAS Detach procedure.
non-GBR S1 eNB initiated release due When the eNB gets an indication that
bearers of an to GTP-U path failure GTP-U path has failed, the eNB will
UE have failed detection initiate connection release (both S1 and
and one RRC connection) for a UE using the failed
active non- path.
GBR S1
bearer
remains
02 February 2016
active,
respectively
RB_REL_REQ_OTHER TNL Path Switch Request The UE context and all the related E-
ENB_EPS_BEARER_REL_REQ_OTH Unspecified Failure at Target eNB RABs released and counted at the target
ENB_EPS_BEAR_REL_REQ_O_QCI1 sent within cell.
ENB_INIT_TO_IDLE_OTHER the UE
Context Timer TX2RELOCcomp expiry The UE context and all the related E-
Release at Target eNB RABs released and counted at the target
Request cell.
message from
eNB to MME
PRE_EMPT_GBR_BEARER RNL Radio GBR Congestion based eNB detected that running GBR EPS
PRE_EMPT_NON_GBR_BEARER resources not Bearer Release bearers cannot be supported according
PRE_EMPT_UE_CONTEXT_NON_GBR available sent to QOS criteria anymore and must be
within the E- released.
RAB Release
Indication
message from
eNB to MME
RNL Radio Pre-emption eNB decided that one or several EPS
resources not bearers of an UE shall be pre-empted
available sent
within the UE
Context
Release
Request and
E-RAB
Release
Indication
message from
eNB to MME
in case all
non-GBR S1
bearers of an
UE have failed
and one
active non-
GBR S1
bearer
remains
active,
respectively
Invalid QoS Pre-emption eNB decided that one or several EPS
combination bearers of an UE shall be pre-empted
sent within
the UE
Context
Release
Request and
E-RAB
Release
02 February 2016
Indication
message from
eNB to MME
in case all
non-GBR S1
bearers of an
UE have failed
and one
active non-
GBR S1
bearer
remains
active,
respectively
RB_REL_REQ_OTHER RNL Timer TX2RELOCoverall expiry
ENB_EPS_BEARER_REL_REQ_OTH TX2RELOCoverall at Source eNB
ENB_EPS_BEAR_REL_REQ_O_QCI1 Expiry sent
ENB_INIT_TO_IDLE_OTHER within the UE
Context
Release
Request
message from
eNB to MME
RNL Timer TS1RELOCoverall expiry
TS1RELOCoverall at Source eNB
Expiry sent
within the UE
Context
Release
Request
message from
eNB to MME
Any cause eNB initiated release due
different from to any cause different
RNL (not used from the above
above) and mentioned ones. And
Transport one includes also some
sent within protocol causes (see
the UE chapter 9.2.1.3 in the
Context 3GPP TS 36.413) which
Release apply for E-RAB release.
Request and
E-RAB
Release
Indication
message from
eNB to MME
in case all
non-GBR S1
bearers of an
UE have failed
02 February 2016
and one
active non-
GBR S1
bearer
*
Only ENB_INIT_TO_IDLE_RNL is triggered with sending the UE Context Release Request message from eNB to MME in these
scenarios. The previously received E-RAB RELEASE COMMAND message from MME in case if unsuccessful E-RAB (s) release
does not trigger any E-RAB Release EPC initiated PM counter in those scenarios.
** In case the inactivity timer for the UE being out-of-sync has expired the UE may still be in RRC_CONNECTED or may have
gone to RRC_IDLE silently. The eNB checks the reachability of the UE by triggering random access procedure. If the UE performs
a random access, eNB recognizes that this is a normal “user inactivity” case and performs RRC Connection Reconfiguration
procedure to configure PUCCH resources. After this, the eNB requests the MME to release UE context. The release procedure
goes with the cause value is: Radio Network Layer cause (User Inactivity). If the eNB does not recognize any random access by
the UE, the eNB requests MME to release UE context with the cause value is: Radio Network Layer cause (Radio Connection
with UE lost).
List of the Trigger Events Related to EPC initiated DRB and E-RAB Release
Counters
The following table summarizes the triggering of the DRB and E-RAB Release Counters initiated by EPC
without detailed cause description as it is done in previous chapter as this specification does not aim to
focus on EPC part.
Counter name Cause Value Use Case Description Detailed description
RB_REL_REQ_RNL Any RNL cause EPC initiated release due

EPC_EPS_BEARER_REL_REQ_RNL sent within the E- to any RNL cause except
EPC_EPS_BEAR_REL_REQ_R_QCI1 RAB Release the “successful
EPC_INIT_TO_IDLE_RNL Command or UE handover” is counted.
Context Release
Command
message from
MME to eNB
except the
“successful
handover” and
“normal”.
02 February 2016
RB_REL_REQ_NORM_REL RNL Normal EPC initiated release RB_REL_REQ_NORM_REL is

EPC_EPS_BEARER_REL_REQ_NORM Release sent due to normal cause triggered on releases due to all
EPC_EPS_BEAR_REL_REQ_N_QCI1 within the E-RAB kinds of successful outgoing
EPC_INIT_TO_IDLE_UE_NORM_REL Release handovers initiated by EPC.
Command or UE
Context Release EPC_EPS_BEARER_REL_REQ_NORM
Command EPC_EPS_BEAR_REL_REQ_N_QCI1
message from are not triggered on any release
MME to eNB due to successful outgoing HO..
RB_REL_REQ_DETACH_PROC RNL Detach sent EPC initiated release due

EPC_EPS_BEARER_REL_REQ_DETACH within the UE to detach.
EPC_EPS_BEAR_REL_REQ_D_QCI1 Context Release
EPC_INIT_TO_IDLE_DETACH Command
message from
MME to eNB
RB_REL_REQ_OTHER Any cause EPC initiated release due The triggering is done for NAS
EPC_EPS_BEARER_REL_REQ_OTH different to to other cause. causes different from "normal
EPC_EPS_BEAR_REL_REQ_O_QCI1 “RNL” or release" or "detach" and some
EPC_INIT_TO_IDLE_OTHER "normal release" Miscellaneous causes (see chapter
or "detach" sent 9.2.1.3 in the 3GPP TS 36.413)
within the E-RAB
Release
Command or UE
Context Release
Command
message from
MME to eNB
1. Regarding the DRB and E-RAB release related counters 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. It also holds for
the QCI1 based E-RAB Release counters with the exception that the paging is only executed for the QCI1
services.
2. The counters related to UE transmission from ECM-CONNECTED to ECM-IDLE are triggered independent
there was an E-RAB in the E-RAB Release list or not (see also Note 5 in the chapter 2.4).
3. For the cases when eNB sent Initial Context setup Failure to MME and UE related resources are released
silently via RRC Connection Release procedure after InitialContextSetupRollback timer expiry without
previous sending UE Context Release Request to MME the counters ENB_INIT_TO_IDLE_OTHER,
ENB_INIT_TO_IDLE_RNL are not triggered at all despite the UE moves to ECM-Idle state.
4. For the cases when UEs are moving to ECM idle without notification to MME like S1 drop, S1 deletion, S1
reset, GTPu failure, Cell delete the related ECM to Idle state and E-RAB Release counters (when UE has
established at least default E-RAB) are not triggered at all.
02 February 2016
5. Regarding the DRB Release counters triggering please see the note 2 in the “Common notes to chapter
3.4”.

LTE

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LTE

Caricato da

Copyright:

Formati disponibili

1 (180) LTE PMO LTE MSC with PM Counters

Dr. Martin Kollar Company Confidential

LTE Message Sequence Charts with PM

Version Date Author Approved by Comments

1.0 02.02.2016 Pawel Gradowski Krzysztof Tatarczyk

Dr. Martin Kollar Company Confidential

Dr. Martin Kollar Company Confidential

2.4.2.1 MME initiated Transaction to ECM-Idle state..................................................................... 27

Dr. Martin Kollar Company Confidential

Dr. Martin Kollar Company Confidential

4.5.1 Successful Procedure ................................................................................................................. 71

Dr. Martin Kollar Company Confidential

5.7.1.1 Successful Procedure .......................................................................................................... 93

Dr. Martin Kollar Company Confidential

8. ANR for E-UTRAN .............................................................................................................................. 113

Dr. Martin Kollar Company Confidential

11.8.1 SINR Measurements per Cell for PUCCH .......................................................................... 133

Dr. Martin Kollar Company Confidential

11.16 Active UEs with Activated SCell(s) Measurement ...................................................................... 160

0.1 21.01.2016 Pawel Gradowski First version for review

1.0 02.02.2016 Pawel Gradowski Comments received during the review

Dr. Martin Kollar Company Confidential

Changes Compared to RL60

2.3 RRC Connection Establishment

Updates due to RACH_MSG3_CONTENTION, RRC_CON_STP_TIM_MEAN and RRC_CON_STP_TIM_MAX

2.5 RRC Connection Re-establishment

Updates due to RACH_MSG3_CONTENTION.

New chapter added

New chapter added.

3.1 E-RAB Bearer Establishment

Chapter modified and new ERAB counters included

Sum of simultaneous E-RABs of QCIs information added as a note

Mean and Maximum E-RAB setup time information added as a note

3.5 UE Context Modification

Chapter modified. New counters added, obsolete removed.

3.5.2 S1AP UE Context Modification (Unsuccessful procedure)

Chapter removed due to removal of UE_CONTEXT_MOD_FAIL counter

3.6 E-RAB Modification

New chapter added

4.1 Initial Context Setup

Dr. Martin Kollar Company Confidential

Chapter modified. New counters added, obsolete removed.

4.4 S1 UE Associated Logical S1 Connection Establishment

Chapter modified. New counters added, obsolete removed.

4.6.3 WRITE-REPLACE WARNING REQUEST (Unsuccessful Procedure)

New chapter added

4.6.4 KILL- REQUEST (Unsuccessful Procedure)

New chapter added

5.4 Intra eNB Handover

5.5 Inter eNB X2 Based Handover

5.6 Inter eNB S1 Based Handover

5.7 Inter RAT Handover

Chapter modified due to Incoming HO counters.

Chapter modified due to 3CC DL CA.

11.11.1 Retention Delay within the eNB in DL

11.12.1 CQI Distribution Measurement

11.13.1 PRB Measurement in DL

Dr. Martin Kollar Company Confidential

Chapter modified due to eICIC.

11.13.2 PRB Measurement in UL

Chapter modified due to eICIC.

11.14 Active UEs with Data in the Buffer Measurement

11.16 Active UEs with Activated SCell(s) Measurement

Chapter modified due to 3CC DL CA.