Professional Documents
Culture Documents
LTE
LTE
02 February 2016
Company Confidential
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
3 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.1 Successful Procedure ................................................................................................................. 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
5 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
02 February 2016
02 February 2016
02 February 2016
02 February 2016
History
Version Date Author Reason for update
02 February 2016
2.5.3 RRC Connection Re-establishment to other eNB (RLF triggered Handover) Successful procedure
2.5.4 RRC Connection Re-establishment to other eNB (RLF triggered Handover) Unsuccessful
procedure due to expiry of T301guard in requested eNB
02 February 2016
Chapter modified due to Incoming HO counters and Service Based Handover counters.
Chapter modified due to Incoming HO counters and Service Based Handover counters.
Chapter modified due to Incoming HO counters and Service Based Handover counters.
9. CA Related Procedures
PDCP_SDU_DELAY_DL_DTCH_MEAN added
Notes modified.
02 February 2016
Flowcharts modified.
02 February 2016
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.
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.
14 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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 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.
15 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
RACH_STP_ATT_LARGE_MSG
RACH_STP_COMPLETIONS
16 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
PDCCH ORDER
PDCCH
PDCCH_INIT_ORDER_ATT*
PDCCH_ORDER_ATT**
RACH_STP_COMPLETIONS
PDCCH_ORDER_SUCCESS
* The counter is updated only for the first (initial) PDCCH order transmitted to UE
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_STP_COMPLETIONS
2.2.2.3 Contention Free Random Access Procedure for inter eNB Handover
RACH_STP_COMPLETIONS
18 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
2.2.2.4 Unsuccessful Contention Free Random Access Procedure Due to Lack of Preamble
Resources
UE eNB
D_PREAMB_UNAVAIL*
D_PREAMB_PDCCH_UNAVAIL
D_PREAMB_HO_UNAVAIL
1. The counter RACH_STP_COMPLETIONS is triggered both for contention based and free random access
procedures.
2. The counter RACH_STP_ATT_DEDICATED is triggered for all kinds of contention free random access
procedure
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.
19 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
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 ****
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_MAX
RRC_CON_STP_TIM_MEAN*****
RRC_CON_STP_TIM_MAX*****
20 (180) LTE PMO LTE MSC with PM Counters
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.
21 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
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
SIGN_EST_F_RRCCOMPL_MISSING
22 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
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
SIGN_EST_F_RRCCOMPL_ERROR
23 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
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
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
24 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
*** 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
25 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE in Trigger to initiate
RRC-CONNECTED release
:
S1AP: UE Context Release
Command
CELL_LOAD_ACT_UE_AVG (stop)
CELL_LOAD_ACT_UE_MAX
S1AP: UE Context Release
L2 ACK Complete
Set UE to
Set UE to Release all UE ECM-IDLE
RRC-IDLE related resources,
remove UE context
RRC_CONN_UE_AVG(stop)
RRC_CONN_UE_MAX
26 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE in
RRC-CONNECTED
S1AP: UE Context Release Request
ENB_INIT_TO_IDLE_NORM_REL*
PRE_EMPT_UE_CONTEXT_NON_GBR**
S11 interaction to inform
S1AP: UE Context Release Command S-GW
RRC: RRC Connection Release about connection release
DCCH
CELL_LOAD_ACT_UE_AVG(stop)
CELL_LOAD_ACT_UE_MAX
S1AP: UE Context Release Complete
L2 ACK
Release all UE related Set UE to
Set UE to
resources, ECM-IDLE
RRC-IDLE
remove UE context
RRC_CONN_UE_AVG(stop)
RRC_CONN_UE_MAX
*The counter is also pegged in case of CS Fallback (see also chapters 5.2, 5.3).
**The counter provides the total number of released UE contexts due to “Radio resources not available”
despite a pre-emption used in the counter name.
27 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE in Trigger to initiate
RRC-CONNECTED release
S1AP: UE Context Release :
Command
EPC_INIT_TO_IDLE_RNL
S11 interaction to release the UE
EPC_INIT_TO_IDLE_OTHER and its bearer
CELL_LOAD_ACT_UE_AVG(stop)
CELL_LOAD_ACT_UE_MAX
S1AP: UE Context Release
Complete
L2 ACK
Set UE to
Set UE to Release all UE ECM-IDLE
RRC-IDLE related resources,
remove UE context
RRC_CONN_UE_AVG(stop)
RRC_CONN_UE_MAX
28 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
ENB_INIT_TO_IDLE_RNL
ENB_INIT_TO_IDLE_OTHER
S1AP: UE Context Release Command
S11 interaction to inform S-GW
RRC: RRC Connection Release about connection release
DCCH
CELL_LOAD_ACT_UE_AVG(stop)
CELL_LOAD_ACT_UE_MAX
S1AP: UE Context Release Complete
L2 ACK
Set UE to Set UE to
Release all UE related ECM-IDLE
RRC-IDLE resources,
remove UE context
RRC_CONN_UE_AVG(stop)
RRC_CONN_UE_MAX
29 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE in S1 Reset,
RRC-CONNECTED S11 interaction to inform S-GW
about connection release
ACT_UE_CONT_REL_INIT_ENB
Set UE to
ACT_UE_CONT_REL_INIT_MME ECM-IDLE
CELL_LOAD_ACT_UE_AVG(stop)
CELL_LOAD_ACT_UE_MAX
L2 ACK
Release all UE related
Set UE to resources,
RRC-IDLE remove UE context
RRC_CONN_UE_AVG(stop)
RRC_CONN_UE_MAX
1. The counter RRC_CONN_UE_AVG is not directly decremented with the receiving the L2 ACK message as
an answer to RRC Connection release but some other algorithm are used to provide the averaged number
of UEs in RRC connected state. 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).
30 (180) LTE PMO LTE MSC with PM Counters
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).
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.
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.
32 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE Serving/Source/Target eNB
Reestablishment Trigger
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
02 February 2016
Reestablishment Trigger
RRC: RRCConnectionReestablishmentRequest
CCCH
RRC_CON_RE_ESTAB_ATT *
RRC_CON_RE_ESTAB_ATT_HO_FAIL **
RRC_CON_RE_ESTAB_ATT_OTHER **
RACH_MSG3_CONTENTION ***
RRC: RRCConnectionReestablishmentReject
CCCH
REJ_RRC_CONN_RE_ESTAB *
34 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
requested serving
UE EPC
eNB eNB
RRC:RRCConnectionReestablishmentRequest
RCR_UE_CONTEXT_RETR_ATT
X2AP: Handover Request
HO_RLF_PREP_ATT
RCR_UE_CONTEXT_RETR_SUCC HO_RLF_PREP_SUCC
HO_RLF_SUCC
PM counters that are incremented during normal handover execution are not incremented during RLF triggered
handover execution
35 (180) LTE PMO LTE MSC with PM Counters
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
requested serving
UE EPC
eNB eNB
RRC:RRCConnectionReestablishmentRequest
Start T301guard
RCR_UE_CONTEXT_RETR_ATT
Expiry T301guard
RCR_UE_CONTEXT_RETR_FAIL_TIM
RRC:RRCConnectionReestablishmentReject
HO_RLF_PREP_ATT
X2AP: Handover Request
Start TX2RELOCexec Acknowledge Start TX2RELOCoverall
Expiry TX2RELOCexec
Expiry TX2RELOCoverall
02 February 2016
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
37 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
ERAB_INI_SETUP_ATT_QCI1*
ERAB_INI_SETUP_ATT_QCI9*
EPS_BEARER_SETUP_COMPLETIONS
ERAB_INI_SETUP_SUCC_QCI1*
ERAB_INI_SETUP_SUCC_QCI9*
ERAB_SETUP_TIME_MEAN**
ERAB_SETUP_TIME_MAX**
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.
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
ERAB_INI_SETUP_ATT_QCI1
ERAB_INI_SETUP_ATT_QCI9
Security Establishment
EPS_BEARER_SETUP_FAIL_RNL*
EPS_BEARER_SETUP_FAIL_TRPORT*
EPS_BEARER_SETUP_FAIL_RESOUR*
EPS_BEARER_SETUP_FAIL_OTH*
* The counters are triggered on a per cause basis which is obtained from E-RAB Failed to Setup List 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.
39 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
ERAB_ADD_SETUP_ATT_QCI1
ERAB_ADD_SETUP_ATT_QCI9
E_RAB_SETUP_ATT_EMG**
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 for IMS Emergency sessions i.e. in case when the ARP (Allocation and Retention
Priority) priority level which is used for emergency sessions is part of S1AP: E-RAB SETUP REQUEST message.
From the simplicity point of view in the above message flow chart it is considered that the S1AP: E-RAB SETUP
RESPONSE message only contains E-RAB Setup List and that the E-RAB Failed To Setup List is empty.
40 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
EPS_BEARER_SETUP_ATTEMPTS
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.
41 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
• 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.
- 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).
42 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
DATA_RB_STP_COMP
CELL_LOAD_ACT_UE_AVG(start)
CELL_LOAD_ACT_UE_MAX
RRC_CONN_UE_AVG(start)
RRC_CONN_UE_MAX
Notes:
1. The message flow chart from the perspective of sent RRC Connection Reconfiguration and RRC Connection
Reconfiguration Complete covers also a DRB establishment for an intra eNB handover with the only exception
that there is not any E-RAB establishment in parallel.
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
43 (180) LTE PMO LTE MSC with PM Counters
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)”.
44 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3.2.2 Successful Procedure (DRB establishment done during X2 based inter eNB handover)
Source Target
UE
eNB eNB
Measurement Reports
DCCH
old cell
Handover Request
Start Tx2Relocexec
Contention Free
Stop Tx2Relocexec
Random Access Procedure (see chapter 2.2.2.2)
02 February 2016
3.2.3 Successful Procedure (DRB establishment done during S1 based inter eNB handover)
Measurement Reports
DCCH
old cell
Handover Required
Handover Request
Start TS1Relocexec
Handover Request
Acknowledge
DATA_RB_STP_ATT
Handover Command
Contention Free
Random Access Procedure (see chapter 2.2.2.2)
Stop TS1Relocexec
RRC Connection Reconfiguration Complete
DCCH
new cell DATA_RB_STP_COMP
CELL_LOAD_ACT_UE_MAX
CELL_LOAD_ACT_UE_AVG(start)
RRC_CONN_UE_AVG(start)
RRC_CONN_UE_MAX
1 It should be noted that the message flow chart is simplified and some synchronization messages used during
the handover are excluded.
46 (180) LTE PMO LTE MSC with PM Counters
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
RRC: RRCConnectionReconfiguration
DCCH
Contention Free Random Access ProcedureIn case of intra
eNB Handover (see chapter 2.2.2.1)
Default or Additional EPS
Bearer Establishment
DATA_RB_STP_ATT
RRC: RRCConnectionReconfigurationComplete
DCCH
Expiry RRC Guard Timer
DATA_RB_STP_FAIL
Note: The message flow chart from the perspective of sent RRC Connection Reconfiguration and RRC Connection
Reconfiguration Complete covers also a DRB establishment for an intra eNB handover with the only exception that
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).
47 (180) LTE PMO LTE MSC with PM Counters
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
Contention Free
Random Access Procedure (see chapter 2.2.2.2)
DATA_RB_STP_FAIL
Note: It should be noted that the message flow chart is simplified and some synchronization messages used during
the handover are excluded.
48 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3.2.6 Unsuccessful Procedure (DRB establishment done during S1 based inter eNB
handover)
Measurement Reports
DCCH
old cell
Handover Required
Handover Request
Start TS1Relocexec
Handover Request
Acknowledge
DATA_RB_STP_ATT
Handover Command
Contention Free
Random Access Procedure (see chapter 2.2.2.2)
DATA_RB_STP_FAIL
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
UE eNB MME
ENB_EPS_BEARER_REL_REQ_NORM
ENB_EPS_BEAR_REL_REQ_N_QCI1
PRE_EMPT_GBR_BEARER*
PRE_EMPT_NON_GBR_BEARER*
RRC: RRCConnectionReconfiguration
DCCH
RRC: RRCConnectionReconfigurationComplete
DCCH S1AP: E-RAB RELEASE RESPONSE
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
*The counters provide the total number of released GBR and non GBR E-RABs due to “Radio resources not
available” despite a pre-emption used in the counter names, respectively.
50 (180) LTE PMO LTE MSC with PM Counters
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
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
51 (180) LTE PMO LTE MSC with PM Counters
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
RRC: RRCConnectionReconfiguration
DCCH
RRC: RRCConnectionReconfigurationComplete
DCCH
S1AP: E-RAB RELEASE RESPONSE
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
52 (180) LTE PMO LTE MSC with PM Counters
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
RRC: RRCConnectionReconfiguration
DCCH
RRC: RRCConnectionReconfigurationComplete
DCCH S1AP: E-RAB RELEASE RESPONSE
RRC: ULInformationTransfer
DCCH S1AP: UL NAS TRANSPORT
53 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3.3.5 Normal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state)
UE eNB MME S-GW
ENB_EPSBEAR_REL_REQ_RNL_REDIR
PRE_EMPT_NON_GBR_BEARER*
PRE_EMPT_GBR_BEARER*
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_T_QCI1
ENB_EPS_BEARER_REL_REQ_O_QCI1
ERAB_REL_ENB_ACT_QCI1*
ERAB_REL_ENB_ACT_QCI2*
ERAB_REL_ENB_ACT_QCI3*
ERAB_REL_ENB_ACT_QCI4*
ERAB_REL_ENB_ACT_NON_GBR*
*The counters are only triggered with RNL failure with UE lost cause and having data in the RLC buffer in
the time of drop.
55 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3.3.6 Normal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state)
UE eNB MME S-GW
S1AP: UE Context Release
UE in Command
RRC-CONNECTED
:
EPC_EPS_BEARER_REL_REQ_NORM
EPC_EPS_BEARER_REL_REQ_DETACH
S11 interaction to release the UE
EPC_EPS_BEARER_REL_REQ_N_QCI1 and its bearer
EPC_EPS_BEARER_REL_REQ_D_QCI1
02 February 2016
3.3.7 Abnormal E-RAB Release Initiated by MME (UE moves to ECM-IDLE state)
UE eNB MME S-GW
EPC_EPS_BEARER_REL_REQ_OTH
S11 interaction to release the UE
and its bearer
EPC_EPS_BEARER_REL_REQ_R_QCI1
EPC_EPS_BEARER_REL_REQ_O_QCI1
1. All the used counters in this chapter, 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) .
57 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
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.
58 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
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
59 (180) LTE PMO LTE MSC with PM Counters
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.
eNB MME
UE_CONTEXT_MOD_ATT_AMBR
UE_CTX_MOD_ATT_CSFB
S1AP: UE CONTEXT MODIFICATION RESPONSE
UE_CTX_MOD_SUCC
UE_CTX_MOD_SUCC_CSFB
60 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Notes :
02 February 2016
UE eNB MME
ERAB_MOD_ATT_QCI5*
ERAB_MOD_ATT_QCI6*
ERAB_MOD_ATT_QCI7*
ERAB_MOD_ATT_QCI8*
ERAB_MOD_ATT_QCI9*
ERAB_MOD_SUCC_QCI5**
ERAB_MOD_SUCC_QCI6**
ERAB_MOD_SUCC_QCI7**
ERAB_MOD_SUCC_QCI8**
ERAB_MOD_SUCC_QCI9**
* 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
62 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
ERAB_MOD_ATT_QCI6*
ERAB_MOD_ATT_QCI7*
ERAB_MOD_ATT_QCI8*
ERAB_MOD_ATT_QCI9*
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
63 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
UE_CTX_SETUP_SUCC*
UE_CTX_SETUP_SUCC_CSFB***
** 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”.
64 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE_CTX_SETUP_ATT_CSFB
Security Establishment
UE_CTX_SETUP_FAIL_RADIO_INT
65 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
4.2 S1 Setup
4.2.1 Successful Procedure
eNB MME
Start an O&M Timer
S1AP: S1 SETUP REQUEST
S1_SETUP_ATT
S1_SETUP_SUCC
eNB MME
Start an O&M Timer
S1AP: S1 SETUP REQUEST
S1_SETUP_ATT
S1_SETUP_FAIL_NO_RESP
66 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
eNB MME
Start an O&M Timer
S1AP: S1 SETUP REQUEST
S1_SETUP_ATT
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
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.
67 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.
68 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
eNB MME
Start a Supervision Wait Timer in MME
S1AP: S1 RESET*
S1AP_PARTIAL_RESET_INIT_MME
*The intention “partial” means that with the S1 reset procedure the UE contexts included in the “UE-associated
logical S1-connection list” within the message are released.
69 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.
70 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
S1_SIGN_CONN_ESTAB_ATT_UE
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.
71 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
E_RAB_SETUP_ATT
02 February 2016
UE eNB MME
E_RAB_SETUP_ATT
E_RAB_SETUP_FAIL_RNL*
E_RAB_SETUP_FAIL_TRANSPORT*
E_RAB_SETUP_FAIL_RESOURCE*
E_RAB_SETUP_FAIL_OTHER*
*For each E-RAB Setup counted by E_RAB_SETUP_ATT always only one of these counters is triggered in case of
unsuccessful procedure, i.e. when the E-RAB Failed to Setup List within an E-RAB Setup Response message is not
empty.
73 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
eNB MME
S1AP_WRITE_REP_WARN_REQ
S1AP_WRITE_REP_WARN_RESP
eNB MME
S1AP:KILL REQUEST
S1AP_KILL_REQ
S1AP:KILL RESPONSE
S1AP_KILL_RESP
74 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
eNB MME
S1AP_WRITE_REP_WARN_REQ
S1AP_WRITE_REP_WARN_FAIL*
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.
75 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
5.Mobility
5.1 eNACC to GSM
Source
UE MME S-GW
eNB
1. Decision to perform
eNACC to GSM
NACC_TO_GSM_ATT
Execution
eNACC
3. Detach Stop/freeze
from old L2
cell and & continue
setup of DL data
RRC buffering
Connection
in GSM 4. S1AP:UE CONTEXT RELEASE COMMAND
Completion
eNACC
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.
76 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
RRC: ULInformationTransfer
(EXTENDED SERVICE REQUEST)
S1AP: UL NAS TRANSPORT
See also chapter 3.5 dealing on UE Context S1AP: UE CONTEXT MODIFICATION REQUEST
Modification counters. (CS Fallback Indicator)
UE_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
ENB_INIT_TO_IDLE_NORM_REL*
L2ACK S1AP: UE CONTEXT RELEASE COMMAND
02 February 2016
UE eNB MME
UE Capabilities E-
UTRA not available
RRC: UECapabilityEnquiry
RRC: UECapabilityInformation
(UE capabilities E-UTRA )
Selection of redirect
target if possible
CSFB_REDIR_CR_EMERGENCY_ATT
Set UE to
Delete Bearer
ECM-IDLE
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.
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.
79 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
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_SUCC_TC, HO_PREP_IN_SUCC_RR
ATT_INTRA_ENB_HO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
Handover Execution
SUCC_INTRA_ENB_HO
RB_REL_REQ_NORM_REL*
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_SUCC)
HO_EMG_SUCC
Packet data
80 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Notes:
02 February 2016
UE eNB
UL allocation
2. Measurement Reports
3. HO Decision
Start THOoverall
INTRA_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
HO_PREP_IN_ATT
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PRER_IN_ATT_RO
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
82 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
UL allocation
2. Measurement Reports
3. HO Decision
Start THOoverall
INTRA_ENB_HO_PREP
Handover Preparation
HO_EMG_PREP
HO_PREP_IN_ATT
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PRER_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_PRER_IN_SUCC_RO
DL allocation
Handover Execution
ATT_INTRA_ENB_HO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
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.
02 February 2016
3. HO Decision
Start TX2RELOCprep 4. Handover Request
Handover Preparation
INTER_ENB_HO_PREP HO_PREP_IN_ATT
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
HO_PREP_IN_SUCC_TC, HO_PREP_IN_SUCC_RR
HO_PREP_IN_SUCC_RL, HO_PREP_IN_SUCC_RO
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
10. UL allocation + TA for UE See chapter 2.2.2.2
End Marker
15. Switch DL Path
Packet data
Handover Completion
SUCC_INTER_ENB_HO Release X2
Signalling
Connection
RB_REL_REQ_NORM_REL*
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_SUCC)
HO_EMG_SUCC
HO_DRX_SUCC
HO_LB_SUCC, HO_SB_SUCC
Data Forwarding
End Marker
Packet data Packet data
Notes: *See chapter 3.4.1. In relation to points 6 and 11 see also chapter 3.2.2.
84 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP HO_PREP_IN_ATT
Handover Preparation
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_EMG_PREP
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO
Expiry TX2RELOCprep
FAIL_ENB_HO_PREP_TIME
HO_EMG_PREP_FAIL
85 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP HO_PREP_IN_ATT
Handover Preparation
HO_EMG_PREP HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO
FAIL_ENB_HO_PREP_AC HO_FAIL_IN_FAIL_RAC
FAIL_ENB_HO_PREP_OTHER HO_PREP_IN_FAIL_TAC
86 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3. HO Decision
Start TX2RELOCprep 4. Handover Request
INTER_ENB_HO_PREP HO_PREP_IN_ATT
Handover Preparation
HO_EMG_PREP HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO
ATT_INTER_ENB_HO HO_PREP_IN_SUCC
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
Handover Execution
HO_PREP_IN_SUCC_RL, HO_PREP_IN_SUCC_RO
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
Expiry TX2RELOCOverall
INTER_ENB_HO_FAIL
87 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.
88 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3. HO Decision
4. Handover Required
6. Handover Request
HO_EMG_PREP
HO_PREP_IN_ATT
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO
Handover Preparation
7. Admission Control and
Resource Allocation
8. Handover Request
Start TS1RELOCexec Acknowledge
HO_PREP_IN_SUCC
HO_PREP_IN_SUCC_TC, HO_PREP_IN_SUCC_RR
HO_PREP_IN_SUCC_RL, HO_PREP_IN_SUCC_RO
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_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
Handover Execution
HO_DRX_ATT
Begin sending
Handover Completion
RB_REL_REQ_NORM_REL*
HO_INTFREQ_SUCC (HO_INTFREQ_GAP_SUCC)
HO_EMG_SUCC
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
89 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Notes:
3. HO Decision
4. Handover Required
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_SUCC_TC, HO_PREP_IN_SUCC_RR
HO_PREP_IN_SUCC_RL, HO_PREP_IN_SUCC_RO
Expiry TS1RELOCprep
HO_EMG_PREP_FAIL
90 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3. HO Decision
4. Handover Required
Start TS1RELOCprep
INTER_ENB_S1_HO_PREP
HO_EMG_PREP
5. HO preparation in EPC
6. Handover Request
HO_PREP_IN_ATT
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
Handover Preparation
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO
HO_PREP_IN_FAIL_TAC
INTER_S1_HO_PREP_FAIL_NORR
INTER_S1_HO_PREP_FAIL_OTHER
91 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
3. HO Decision
4. Handover Required
Start TS1RELOCprep
5. HO preparation in EPC
HO_EMG_PREP HO_PREP_IN_ATT
HO_PREP_IN_ATT_TC, HO_PREP_IN_ATT_RR
HO_PREP_IN_ATT_RL, HO_PREP_IN_ATT_RO
Handover Preparation
Acknowledge
Start TS1RELOCexec
HO_PREP_IN_SUCC
HO_INTFREQ_ATT (HO_INTFREQ_GAP_ATT)
HO_EMG_ATT
HO_DRX_ATT
Handover Execution
Begin sending
fresh S1-U data
Expiry TS1RELOCOverall
INTER_ENB_S1_HO_FAIL
92 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
1. The counters included in the following table dealing with handover for IMS emergency sessions, inter-
frequency handover and handover for the UEs running in DRX mode are triggered independently of
network topology (i.e. it is intra or inter eNB handover).
2. It should be noted that besides the mentioned intra and inter eNB counters triggered on a per source cell
basis there are also the counters pegged with the same trigger events but updated in addition with a
relationship to the touched neighbouring cell (see the following table).
Intra eNB HO counters per neighbouring INTRA_HO_PREP_FAIL_NB, INTRA_HO_ATT_NB,
cell INTRA_HO_SUCC_NB, INTRA_HO_FAIL_NB
Inter eNB HO counters per neighbouring INTER_HO_PREP_FAIL_OTH_NB,
cell INTER_HO_PREP_FAIL_TIME_NB,
INTER_HO_PREP_FAIL_AC_NB,
INTER_HO_ATT_NB, INTER_HO_SUCC_NB,
INTER_HO_FAIL_NB
3. The 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.
93 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
· Map EPS bearers to PDP contexts
Handover Preparation
· Map EPS QoS parameters to pre-Rel8 QoS parameters
· Map EPS security parameters to UTRAN security parameters
· Data path tunnel resource allocation
· Selection of data forwarding
· Indirect forwarding tunnel setup (if required)
· Transport of direct forwarding tunnel parameters (if required)
Stop TS1RELOCprep
4. S1AP:HANDOVER COMMAND
Start TS1RELOCoverall
Handover Execution
ISYS_HO_ATT
ISYS_HO_UTRAN_SRVCC_ATT
CSFB_PSHO_UTRAN_ATT
to new cell
Downlink Data
Uplink Data
ISYS_HO_UTRAN_SRVCC_SUCC
RB_REL_REQ_NORM_REL*
02 February 2016
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
·
Handover Preparation
Map EPS bearers to PDP contexts
· Map EPS QoS parameters to pre-Rel8 QoS parameters
· Map EPS security parameters to UTRAN security parameters
· Data path tunnel resource allocation
· Selection of data forwarding
· Indirect forwarding tunnel setup (if required)
· Transport of direct forwarding tunnel parameters (if required)
ISYS_HO_PREP_FAIL_TIM
95 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
Handover Preparation
· Map EPS bearers to PDP contexts
· Map EPS QoS parameters to pre-Rel8 QoS parameters
· Map EPS security parameters to UTRAN security parameters
· Data path tunnel resource allocation
· Selection of data forwarding
· Indirect forwarding tunnel setup (if required)
· Transport of direct forwarding tunnel parameters (if required)
Stop TS1RELOCprep
4. S1AP:HANDOVER
PREPARATION FAILURE An error occurred which leads to sending
HO Preparation Failure to Source eNB
ISYS_HO_PREP_FAIL_AC
ISYS_HO_PREP_FAIL_OTH
96 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Source Target
UE MME S-GW SGSN P-GW
eNB RNC
1. Decision to perform
handover to UMTS
ISYS_HO_PREP
3. Handover Preparation:
· Map EPS bearers to PDP contexts
Handover Preparation
· Map EPS QoS parameters to pre-Rel8 QoS parameters
· Map EPS security parameters to UTRAN security parameters
· Data path tunnel resource allocation
· Selection of data forwarding
· Indirect forwarding tunnel setup (if required)
· Transport of direct forwarding tunnel parameters (if required)
Stop TS1RELOCprep
4. S1AP:HANDOVER COMMAND
Start TS1RELOCoverall
Handover Execution
ISYS_HO_ATT
ISYS_HO_UTRAN_SRVCC_ATT
CSFB_PSHO_UTRAN_ATT
Handover Completion
to new cell
Downlink Data
Uplink Data
Expiry TS1RELOCoverall
An error occurred which leads to UE
Context Release Command never received
by Source eNB
ISYS_HO_FAIL
ISYS_HO_UTRAN_SRVCC_FAIL
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
98 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Source Target
UE MME S-GW SGSN P-GW
eNB BSS
1. Decision to perform
SRVCC to GSM
2. S1AP:HANDOVER REQUIRED
Start TS1RELOCprep
Handover Preparation
3. Handover Preparation
Stop TS1RELOCprep
4. S1AP:HANDOVER COMMAND
Start TS1RELOCoverall
Handover Execution
ISYS_HO_GERAN_SRVCC_ATT
Handover Completion
UL & DL Payload PDUs
7. S1AP:UE CONTEXT RELEASE COMMAND
Stop TS1RELOCoverall
ISYS_HO_GERAN_SRVCC_SUCC
RB_REL_REQ_NORM_REL*
02 February 2016
Source Target
UE MME S-GW SGSN P-GW
eNB BSS
1. Decision to perform
SRVCC to GSM
2. S1AP:HANDOVER REQUIRED
Start TS1RELOCprep
Handover Preparation
3. Handover Preparation
Stop TS1RELOCprep
4. S1AP:HANDOVER COMMAND
Start TS1RELOCoverall
Handover Execution
ISYS_HO_GERAN_SRVCC_ATT
Handover Completion
UL & DL Payload PDUs
7. S1AP:UE CONTEXT
RELEASE COMMAND
Expiry TS1RELOCoverall An error occurred which leads to UE
Context Release Command never received
ISYS_HO_GERAN_SRVCC_FAIL
by Source eNB
1. The handover from LTE to GERAN is only possible with SRVCC. To hand over a non VoIP session from LTE
to GERAN an eNACC is used (see chapter 5.1).
2. It should be noted that besides the mentioned counters triggered on a per source cell basis there are also
the counters pegged with the same trigger events but updated in addition with a relationship to the
touched neighbouring cell (see the following table).
Intra RAT HO to GERAN with SRVCC ISYS_HO_GERAN_SRVCC_ATT_NB,
counters per neighbouring cell ISYS_HO_GERAN_SRVCC_SUCC_NB,
ISYS_HO_GERAN_SRVCC_FAIL_NB
100 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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:
For more details, see [5] in Common notes to chapters 5.4, 5.5 and 5.6)
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.
101 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
· The UE is experienced to RLF instead of HO (optionally recoverable RLF on eNB side). I.e. HO
is missed with an option that in the source cell of missed HO attempt, a HO preparation for the
considered UE context can be ongoing.
· The UE will continue with RRC connection re-establishment request in another cell
If,
· the UE context is not found,
or the request cannot be authenticated,
· and If the reestablishment cause is not
“ReconfigurationFailure
the target eNB shall trigger the X2 RLF
Indication procedure.
X2AP: RLF INDICATION
If,
· the received PhysCellId field in the
Failure cell (PCI IE) corresponds to
the physical cell identity of the cell
receiving this X2 message,
· the UE context is found and
· the UE authentication is successful
and
· if If TStoreUE_CNTXT timer is not running
and no incoming handover has been
initiated
then, the eNB shall stop TRLF timer if
running, release the held UE context and
increment the following too late HO
counters
MRO_LATE_HO
MRO_LATE_HO_NB
102 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
· The HO is successfully attempted in the target cell but failed (T304 expired)
· The UE will continue with RRC connection re-establishment request in source cell
RRC CONNECTION
REESTABLISHMENT
REQUEST
If,
· re-establishment cause is equal to
‘HOfailure’
· C-RNTI corresponds to an available
UE context for which outgoing HO
preparation is ongoing
· included shortMAC-I matches the
local security calculation (successful
authentication)
MRO_EARLY_TYPE1_HO
MRO_EARLY_TYPE1_HO_NB
103 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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
104 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.
Normal E-RAB Release Initiated by eNB (UE moves to ECM-IDLE state), see chapter 3.1.1
02 February 2016
RRC: HandoverFromEUTRA
PreparationRequest
Start TUIHoPrepTransferHrpd
( CDMA2000- Type = typeHRPD)
ISYS_HO_EHRPD_PREP_BC
RRC: ULHandoverPreparationTransfer
Stop TUIHoPrepTransferHrpd
( CDMA2000- Type = typeHRPD)
Stop TC2KRelocPrepHrpd
ISYS_HO_EHRPD_PREP_SUCC_BC
106 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
ISYS_HO_EHRPD_PREP_BC
RRC: ULHandoverPreparationTransfer
( CDMA2000- Type = typeHRPD)
TUIHoPrepTransferHrpd Expiry
ISYS_HO_EHRPD_PREP_FAIL1_BC
107 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
RRC: HandoverFromEUTRA
PreparationRequest
Start TUIHoPrepTransferHrpd
( CDMA2000- Type = typeHRPD)
ISYS_HO_EHRPD_PREP_BC
RRC: ULHandoverPreparationTransfer
Stop TUIHoPrepTransferHrpd
( CDMA2000- Type = typeHRPD)
TC2KRelocPrepHrpd Expiry
ISYS_HO_EHRPD_PREP_FAIL2_BC
108 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
RRC: HandoverFromEUTRA
PreparationRequest
Start TUIHoPrepTransferHrpd
( CDMA2000- Type = typeHRPD)
ISYS_HO_EHRPD_PREP_BC
RRC: ULHandoverPreparationTransfer
Stop TUIHoPrepTransferHrpd
( CDMA2000- Type = typeHRPD)
Stop TC2KRelocPrepHrpd
ISYS_HO_EHRPD_PREP_FAIL3_BC
109 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
RRC: HandoverFromEUTRA
(Purpose = Handover) Start TC2KRelocOverallHRPD
( CDMA2000- Type = typeHRPD)
ISYS_HO_EHRPD_ATT_BC
Handover Execution
Notification Request
Stop TC2KRelocOverallHRPD
Handover Completion
Command (Successful HO)
ISYS_HO_EHRPD_SUCC_BC
02 February 2016
RRC: HandoverFromEUTRA
(Purpose = Handover) Start TC2KRelocOverallHRPD
( CDMA2000- Type = typeHRPD)
ISYS_HO_EHRPD_ATT_BC
Handover Execution
Notification Request
Handover Completion
TC2KRelocOverallHRPD Expiry
ISYS_HO_EHRPD_FAIL_TIM_BC
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.
111 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
Initiating Responding
eNB eNB
X2_SETUP_ATT
Initiating Responding
eNB eNB
X2_SETUP_ATT
X2_SETUP_FAIL
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
1. The functionalities mentioned in this chapter are restricted to intra LTE and intra frequency configuration.
112 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
UE eNB
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.
113 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
1. The ANR to E-UTRAN is applicable for CGI retrieval to intra and inter frequency.
114 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
9. CA Related Procedures
9.1 SCell Addition/Configuration
UE eNB MME
Admit SCell
Configure SCell
Adapt PCell
configuration
RRC: RRCConnectionReconfiguration
DCCH
(physicalConfig: PCell reconfiguration,
SCelltoAddModList: SCell addition)
CA_SCELL_CONFIG_ATT
RRC: RRCConnectionReconfigurationComplete
DCCH
CA_SCELL_CONFIG_SUCC
CA_SCELL_CONF_UE_AVG (Start)
CA_2SCELLS_CONF_UE_AVG (Start)
115 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB MME
RRC: RRCConnectionReconfiguration
RRC: RRCConnectionReconfigurationComplete
DCCH
CA_SCELL_CONF_UE_AVG (Stop)
CA_2SCELLS_CONF_UE_AVG (Stop)
Release SCell
related resources
02 February 2016
UE eNB
Intracell Handover
preparation,
ttiBundlingStatusCh
ange flag set to
active.
RRC: RRCConnectionReconfiguration
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)
117 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
UE eNB
Intacell Handover
preparation,
ttiBundlingStatusCh
ange flag set to
deactive.
RRC: RRCConnectionReconfiguration
Internal timer stopped to
DCCH measure how long the UE
ttiBundling set to inactive
was in the TTI bundling.
According to the measured
RRC: RRCConnectionReconfigurationComplete
value one of the following
DCCH counters is triggered
TTI_BUNDL_RETENTION_MEDIUM
TTI_BUNDL_RETENTION_LONG
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).
118 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
02 February 2016
- PDCP_RET_DL_DEL_MEAN_QCI_1
- PDCP_RET_DL_DEL_MEAN_QCI_2
- PDCP_RET_DL_DEL_MEAN_QCI_3
- PDCP_RET_DL_DEL_MEAN_QCI_4
- PDCP_RET_DL_DEL_MEAN_QCI_5
- PDCP_RET_DL_DEL_MEAN_QCI_6
- PDCP_RET_DL_DEL_MEAN_QCI_7
- PDCP_RET_DL_DEL_MEAN_QCI_8
- PDCP_RET_DL_DEL_MEAN_QCI_9
- PDCP_SDU_DELAY_DL_DTCH_MEAN
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.
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.
121 (180) LTE PMO LTE MSC with PM Counters
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
t=tsend(i)
NO
YES
t=tACK(i)
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.
t1
t0
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.
123 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.
02 February 2016
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
02 February 2016
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.
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.
02 February 2016
YES
TRANSMIT_TB_ON_DL_SCH++
YES
HARQ NACK pegs the
counter as it is triggering for
MAC PDU resending.
HARQ_RETRANS_ON_DL_SCH++
NO
End
1. The counters described in this chapter are not triggered on SIB transmission/re-transmission.
127 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.
02 February 2016
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
End
Fig. 7 Principle of RSSI measurement per UE for PUCCH per one TTI
02 February 2016
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.
02 February 2016
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.
Is the SINRj,
> SINR_PUCCH_MAX?
YES
SINR_PUCCH_MAX=SINRj,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(SINR_PUCCH_AVG)= UEs that did transmission on
Numerator(SINR_PUCCH_AVG)+ SINRj,i PUCCH during the
measurement period
End
Fig. 8 Principle of SINR measurement per UE for PUCCH per one TTI
02 February 2016
02 February 2016
PUCCH
UEs that did transmission on
value by the total number of
dividing this accumulated
average is calculated by
measurement period a total
At the end of the
Is the RSSIj [dBm] < NO
RSSI_CELL_PUCCH_MIN?
YES
RSSI_CELL_PUCCH_MIN=RSSIj [dBm]
YES
RSSI_CELL_PUCCH_MAX=RSSIj [dBm]
NO
End
Fig. 9 Principle of RSSI measurement per cell for PUCCH per one TTI
133 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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.
134 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
𝑁 𝑁
𝑆𝐼𝑁𝑅𝑗 = 𝑖=1 𝑅𝑆𝑆𝐼𝑗 ,𝑖 / 𝑖=1(𝐼 + 𝑁)𝑗 ,𝑖 [dB]
PUCCH
UEs that did transmission on
value by the total number of
dividing this accumulated
average is calculated by
measurement period a total
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
135 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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!
02 February 2016
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
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:
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).
137 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
End
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_VOL_TRANSMITTED+
size(RLC PDU)
YES
RLC_PDU_DL_VOL_CA_SCELL
+ size(RLC PDU)
NO
End
02 February 2016
RLC_PDU_VOL_RECEIVED+
size(RLC PDU)
YES
YES
End
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.
NO
Is the RLC SDU mapped to DRB?
RLC_SDU_VOL_DL_DTCH+
size(RLC SDU)
NO
YES
RLC_SDU_VOL_DL_DCCH+
size(RLC SDU)
End
02 February 2016
NO
YES
RLC_SDU_VOL_UL_DTCH+
size(RLC SDU)
YES
RLC_SDU_VOL_UL_DCCH+
size(RLC SDU)
NO
YES
End
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).
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.
143 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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
02 February 2016
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
End
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.
02 February 2016
- PDCP_SDU_DISC_DL_QCI_1 - PDCP_SDU_DISC_DL_QCI_4.
End
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.
146 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
End
02 February 2016
End
End
02 February 2016
02 February 2016
NO
Is the deltaCQI < CQI_OFF_MIN?
YES
CQI_OFF_MIN = deltaCQI
YES
CQI_OFF_MAX = deltaCQI
NO At the end of the
measurement period a total
average is calculated by
dividing this accumulated
Numerator(CQI_OFF_MIN)+ deltaCQI value by the total number of
calculated deltaCQIs.
End
02 February 2016
- PRB_USED_PDSCH,
- E_ICIC_DL_PRB_UTIL_LEVEL_1 - E_ICIC_DL_PRB_UTIL_LEVEL_10.
02 February 2016
02 February 2016
YES
DL_PRB_UTIL_TTI_MAX=(AllocatedUePrbs+srb0 Prbs
+SysInfoPrbs+PagingPrbs+RaRespPrbs )/(Configured number
of PRBs in DL)x100%
NO
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
02 February 2016
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
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
measurement period a total
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
02 February 2016
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.
156 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
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
157 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
- 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
158 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
NO
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
02 February 2016
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
02 February 2016
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
value by the total number of
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
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)
∑
ThpVolDl = (kbits)
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.
162 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
IP Throughput Measurement in DL
The relevant counters for this scenario are the following:
- 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
The relevant counters for this scenario are the following:
- 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).
163 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
TTI Buffer status after TTI HARQ ACK for Burst measuring
0 1000 Burst 1 measuring starts
1 2000 Burst 1 measuring
2 3000 Burst 1 measuring
3 1000 Burst 1 measuring
4 0 Burst 1 measuring
5 1000 Burst 1 measuring
6 1000 Burst 1 measuring
7 1000 Burst 1 measuring
8 3000 TTI0 Burst 1 measuring
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.
02 February 2016
02 February 2016
02 February 2016
YES
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
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.
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.
169 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
02 February 2016
02 February 2016
02 February 2016
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
173 (180) LTE PMO LTE MSC with PM Counters
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".
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) .
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) .
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”.
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
175 (180) LTE PMO LTE MSC with PM Counters
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
176 (180) LTE PMO LTE MSC with PM Counters
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
177 (180) LTE PMO LTE MSC with PM Counters
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
178 (180) LTE PMO LTE MSC with PM Counters
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.
02 February 2016
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.
180 (180) LTE PMO LTE MSC with PM Counters
02 February 2016
5. Regarding the DRB Release counters triggering please see the note 2 in the “Common notes to chapter
3.4”.