LTE Retainability PDF

LTE L11 Performance Management and Optimization
3 LTE Retainability Optimization
Objectives
After this chapter the participants will be able to:
1. Measure LTE Retainability performance
2. Describe the E-RAB release procedure and associated
counters
3. Use eNodeB counters to create E-RAB Retainability KPIs
4. Explain the eNodeB parameters that influence Retainability
Figure 3-1 Objectives of Chapter 3
LZT 1239602 R1A © Ericsson 2010 - 51 -

Intentionally Blank
- 52 - © Ericsson 2010 LZT 1239602 R1A

EUTRAN RETAINABILITY KPI

Retainability is defined as the ability of a user to retain the E-RAB
once connected, for the desired duration. The Abnormal E-RAB
Release Rate in drops per second can be calculated using the
formula in Figure 3-2 below.
X The ability of user to retain its requested service

once connected for the desired duration
E-RAB Release Rate [drops/s]:

pmErabRelRelAbnormalEnbAct + pmErabRelMmeAct*
=
pmSessionTimeUe
* Removed to observe the

E-RAB Minutes Per Drop: impact of the RBS only
(pmSessionTimeUe/60)
=
pmErabRelRelAbnormalEnbAct + pmErabRelMmeAct*
Figure 3-2 EUTRAN Retainability KPI
The E-RAB Minutes Per Drop is calculated using the

multiplicative inverse of the E-RAB Retainability formula and
transforming ‘pmSessionTimeUe’ from seconds to minutes. Since
both of these formulas measure the impact of the network on the
end user they include releases initiated by the MME. To observe
the impact of the RBS only, ‘pmErabRelMmeAct’ should be
removed from the formulas as illustrated in Figure 3-2 above.
Using drops per second or minutes per drop to measure

Retainability gives a better representation of end user satisfaction
than using drop %. Imagine a single user in a cell downloading
data for a full 24 hour period with one single drop. Measuring
Retainability with drop % would produce 100% drop rate whereas
drops per seconds would produce 0.00001 drops/s or 1440 minutes
per drop.
LZT 1239602 R1A © Ericsson 2010 - 53 -

The description of the ‘pmSessionTimeUe’ counter used in the

EUTRAN Retainability KPI formula is given in Figure 3-3 below.
Managed Counter
Counter Name Description
Object Type
This counters shows the accumulated active

session time in a cell for the measurement period.
pmSessionTimeUe EutranCellFDD Number of session seconds aggregated for UEs in ACC
a cell. A UE is said to be ‘in session’ if any data on
a DRB (UL or DL) has been transferred during the
last 100 ms.
Figure 3-3 UE Session Time Counter
A UE is said to be ‘in session’ if any data on a DRB (UL or DL)

has been transferred during the last 100 ms as illustrated in Figure
3-4 below.
pmSessionTimeUe +
Data
Transfer
in session out of session in session
100 msec 100 msec
Time
Figure 3-4 UE Session Time
The ‘pmSessionTimeUe’ counter is aggregated for all UEs in the

cell, reset at the end of each ROP and collected by the Primary
scanner on the RBS.
The E-RAB can be released using either of the procedures below:

• E-RAB Release Procedure
• UE Context Release Procedure
- 54 - © Ericsson 2010 LZT 1239602 R1A

E-RAB RELEASE PROCEDURE

The E-RAB release procedure may be initiated by the MME by
sending an ‘E-RAB RELEASE COMMAND’ message containing
a list of E-RABs to be released to the RBS as illustrated in Figure
3-5 below.
MME
RRC S1AP
E-RAB RELEASE COMMAND
Includes a list of E-RABs to be released
pmErabRelMme +
Data buffers OR pmErabRelMmeAct +

UL DL
All resources for the E-RAB are released

(DRB and S1 Bearer)
E-RAB RELEASE RESPONSE
Includes a list of released E-RABs

Figure 3-5 MME Initiated E-RAB Release
Upon reception of the ‘E-RAB RELEASE COMMAND’ message

the RBS shall increment the ‘pmErabRelMme’ counter. If there
was data in either the uplink or downlink buffers the
‘pmErabRelMmeAct’ counter will also be incremented as
illustrated in Figure 3-5 above.
The RBS shall release the corresponding DRB and S1 Bearer for
all E-RABs indicated in the ‘E-RAB RELEASE COMMAND’
message and respond with an ‘E-RAB RELEASE RESPONSE’
message to the MME indicating which E-RABs have been
released.
Alternatively the RBS can initiate the release of the E-RAB by

sending an ‘E-RAB RELEASE INDICATION’ message containing
at least one E-RAB to be released towards the MME.
LZT 1239602 R1A © Ericsson 2010 - 55 -

Upon reception of the E-RAB RELEASE INDICATION message

the MME shall normally initiate the appropriate release procedure
on the core network side for the E-RABs identified in the E-RAB
RELEASE INDICATION message.
When the E-RAB release procedure has been initiated by the RBS
the ‘pmErabRelNormalEnb’ counter is incremented for all ‘normal’
release causes and ‘pmErabRelAbnormalEnb’ for all ‘abnormal’
release causes as illustrated in Figure 3-6 below.
MME
RRC S1AP
Normal release pmErabRelNormalEnb +
Abnormal release pmErabRelAbnormalEnb +
Data buffers OR pmErabRelAbnormalEnbAct +

UL DL
All resources for the E-RAB are released

(DRB and S1 Bearer)
E-RAB RELEASE INDICATION
Includes a list of released E-RABs

Figure 3-6 RBS Initiated E-RAB Release
The ‘pmErabRelAbnormalEnbAct’ counter will be incremented for

any abnormally released E-RABs where there was data in either the
uplink or downlink buffers as illustrated in Figure 3-6 above.
If either the MME or RBS wants to remove all remaining E-RABs,

for example due to user inactivity, the UE Context Release Request
procedure is used instead.
- 56 - © Ericsson 2010 LZT 1239602 R1A

UE CONTEXT RELEASE PROCEDURE

The UE context release procedure can be initiated by the MME or
RBS for various reasons, for example completion of a transaction
between the UE and the EPC or completion of successful handover.
The MME can initiate the UE context release procedure sending

the UE CONTEXT RELEASE COMMAND message to the RBS.
On reception of this message the RBS will release all resources for
the UE context (DRB and S1 Bearer) and increment the
‘pmErabRelMme’ and ‘pmUeCtxtRelMm’ counters as illustrated in
Figure 3-7below.
MME
RRC S1AP
UE CONTEXT RELEASE COMMAND
pmErabRelMme +
pmUeCtxtRelMme +
pmErabRelMmeAct +
Data buffers OR
pmUeCtxtRelMmeAct +
UL DL
All resources for the UE context are released

(DRB and S1 Bearer)
UE CONTEXT RELEASE COMPLETE
Figure 3-7 MME Initiated UE Context Release
If there was data in either the uplink or downlink buffers for the UE
context being released that ‘pmErabRelMmeAct’ and
‘pmUeCtxtRelMmeAct’ counters will also be incremented as
The RBS will release all resources for the UE context (DRB and S1
Bearer and respond with a UE CONTEXT RELEASE
COMPLETE message to the MME as illustrated Figure 3-7 above.
LZT 1239602 R1A © Ericsson 2010 - 57 -

The RBS can also initiate the UE context release procedure by

sending a UE CONTEXT RELEASE REQUEST message towards
the affected MME. This message indicates the appropriate cause
value for example "User Inactivity", "Radio Connection With UE
Lost" etc. On reception of this message the MME will send a UE
CONTEXT RELEASE COMMAND message to the RBS.
The RBS will increment ‘pmErabRelNormalEnb’ and

‘pmUeCtxtRelNormalEnb’ counters for all normal releases or the
‘pmErabRelAbnormalEnb’ and ‘pmUeCtxtRelAbnormalEnb’
counter for all abnormal releases as illustrated in Figure 3-8 below.
MME
RRC S1AP
UE CONTEXT RELEASE REQUEST
Includes release cause

UE CONTEXT RELEASE COMMAND
pmErabRelNormalEnb +
Normal release
pmUeCtxtRelNormalEnb +
pmErabRelAbnormalEnb +
Abnormal release
pmUeCtxtRelAbnormalEnb +
pmErabRelAbnormalEnbAct +
Data buffers OR
pmUeCtxtRelAbnormalEnbAct +
UL DL
All resources for the UE context are released
(DRB and S1 Bearer)
UE CONTEXT RELEASE COMPLETE
Figure 3-8 RBS Initiated UE Context Release
The ‘pmErabRelAbnormalEnbAct’ and

‘pmUeCtxtRelAbnormalEnbAct’ counters will be incremented for
any abnormally released UE contexts where there was data in
either the uplink or downlink buffers as illustrated in Figure 3-8
above. The RBS will release all resources for the UE context
(DRB and S1 Bearer and respond with a UE CONTEXT
RELEASE COMPLETE message to the MME as illustrated Figure
3-8 above.
- 58 - © Ericsson 2010 LZT 1239602 R1A

MME Initiated Release Counters

Details of some of the counters triggered by a MME initiated E-
RAB or UE context release are illustrated in Figure 3-9 below.
Counter
Counter Name Managed Object Description
Type
The total number of E-RAB Releases initiated

by the MME.
pmErabRelMme EutranCellFDD This counter is stepped at reception of S1 PEG
message E-RAB RELEASE COMMAND or
UE CONTEXT RELEASE COMMAND and
the release is MME initiated.
The total number of E-RAB Releases initiated
by the MME and that there was data in either
the UL or DL buffer (i.e. active).
pmErabRelMmeAct EutranCellFDD This counter is stepped at reception of PEG
Stepped at reception of S1 message E-RAB
RELEASE COMMAND or UE CONTEXT
RELEASE COMMAND and the release is
MME initiated.
The total number of UE Context Releases
initiated by the MME.
pmUeCtxtRelMme EutranCellFDD This counter is stepped at reception of S1 PEG
message UE CONTEXT RELEASE
COMMAND and the release is MME
initiated.
The total number of UE Context Releases
initiated by the MME and that there was data
in either the UL or DL buffer (i.e. active).
pmUeCtxtRelMmeAct EutranCellFDD The counter is stepped at reception of S1 PEG
message UE CONTEXT RELEASE
COMMAND and the release is MME
initiated.
Figure 3-9 MME Initiated Release Counters
The counters illustrated in Figure 3-9 above are reset at the end of
each ROP but only the ‘pmErabRelMmeAct’ and
‘pmUeCtxtRelMmeAct’ are collected by the Primary scanner on
the RBS.
LZT 1239602 R1A © Ericsson 2010 - 59 -

RBS Initiated Release Counters

Details of some of the counters triggered by an RBS initiated E-
RAB or UE context release are illustrated in Figure 3-10 below.
Managed Counter
Object Type
The total number of normal E-RAB Releases per cell initiated by

the RBS.
pmErabRelNormalEnb EutranCellFDD This counter is stepped at reception of the S1 message E-RAB PEG
RELEASE COMMAND or UE CONTEXT RELEASE
COMMAND where the cause value indicates normal release and
the release is RBS initiated.
The total number of abnormal E-RAB Releases per cell initiated by
the RBS.
pmErabRelAbnormalEnb EutranCellFDD The counter is stepped at reception of the S1 message E-RAB PEG
COMMAND where the cause value indicates system (abnormal)
release and the release is RBS initiated.
The total number of abnormal E-RAB Releases per cell initiated by
the RBS and that there was data in either the UL or DL buffer (i.e.
active).
pmErabRelAbnormalEnbAct EutranCellFDD The counter is stepped at reception of the S1 message E-RAB PEG
COMMAND where the cause value indicates system (abnormal)
release and the release is RBS initiated.
The total number of normal UE Context Releases initiated by the
RBS.
pmUeCtxtRelNormalEnb EutranCellFDD This counter is stepped at reception of the S1 message UE PEG
CONTEXT RELEASE COMMAND where the cause value
indicates normal release and the release is RBS initiated.
The total number of abnormal UE Context Releases initiated by the
RBS.
pmUeCtxtRelAbnormalEnb EutranCellFDD This counter is stepped at reception of Stepped at reception of the PEG
S1 message UE Context Release Command where the cause value
indicates system (abnormal) release and the release was RBS
initiated.
The total number of abnormal UE Context Releases initiated by the
RBS and that there was data in either the UL or DL buffer (i.e.
active).
pmUeCtxtRelAbnormalEnbAct EutranCellFDD This counter is stepped at reception of the S1 message UE PEG
CONTEXT RELEASE COMMAND where the cause value
indicates system (abnormal) release and the release was RBS
initiated.
Figure 3-10 RBS Initiated Release Counters
Only ‘pmErabRelAbnormalEnbAct’ and

‘pmUeCtxtRelAbnormalEnbAct’ are collected by the Primary
scanner on the RBS.
- 60 - © Ericsson 2010 LZT 1239602 R1A

RETAINABILITY INVESTIGATION
The ‘Flowcharts for Counters’ document from the LTE RAN Alex
Library contains a flow chart for UE Context and RAB release
showing the various counters that are incremented in each case.
UE CONTEXT RELEASE FLOW CHARTS

A section of the RBS Initiated UE Context Release flow chart
showing the various counters incremented for an abnormal UE
Context release, when there is data in the UL or DL buffer is
illustrated in Figure 3-11 below.
UE lost due Yes

to S1 I/F pmUeCtxtRelAbnormalEnbActTnFail +
down?
No
HO fails,
Yes
UE dropped ? pmUeCtxtRelAbnormalEnbActHo +
No
UE Yes
connection pmUeCtxtRelAbnormalEnbActUeLost +
lost ?
No
UE lost due to Yes
cell downtime pmUeCtxtRelAbnormalEnbActCdt +
(manual intervention)
No
Figure 3-11 RBS Initiated UE Context Release Flow Chart
The counters illustrated in Figure 3-11 above may be used to

investigation the reason for poor UE context retainability
performance in LTE. LTE Handover and the associated parameters
are explained in chapter 7 (LTE Mobility Optimization).
LZT 1239602 R1A © Ericsson 2010 - 61 -

Details of the Ue Context Release counters illustrated in Figure

3-11 are given in the table in Figure 3-12 below.
Managed Counter
Object Type
The total number of abnormal UE

Context releases initiated by the eNB
due to S1 interface down and that there
pmUeCtxtRelAbnormalEnbActTnFail EutranCellFDD was data in either the UL or DL buffer PEG
(i.e. active).
This counter is stepped for each UE that
is lost due to that the S1 interface is lost.
Context Releases initiated by the eNB
due to handover execution failure and
that there was data in either the UL or
pmUeCtxtRelAbnormalEnbActHo EutranCellFDD DL buffer (i.e. active). PEG
This counter is stepped when an
executed handover fails and the UE is
considered dropped.
context releases by the eNB due that the
contact with the UE is lost and that
there was data in either the UL or DL
pmUeCtxtRelAbnormalEnbActUeLost EutranCellFDD buffer (i.e. active). PEG
is lost when UEs are unreachable by the
eNB.
context releases by the eNB due cell
down time (manual intervention) and
that there was data in either the UL or
pmUeCtxtRelAbnormalEnbActCdt EutranCellFDD DL buffer (i.e. active). PEG
is lost due to cell down time (manual
intervention).
Figure 3-12 RBS Initiated UE Context Release Flow Chart Counters
The counters illustrated in Figure 3-12 above are not collected by

the Primary scanner on the RBS and as such would require a user-
defined subscription set up to initiate their collection.
The ‘pmUeCtxtRelAbnormalEnbActUeLost’ is triggered by the

Radio Connection Supervision algorithm in the RBS.
- 62 - © Ericsson 2010 LZT 1239602 R1A

E-RAB RELEASE FLOW CHART

A section of the RBS Initiated E-RAB Release flow chart showing
the various counters incremented for an abnormal UE Context
release, when there is data in the UL or DL buffer is illustrated in
Figure 3-13 below.
E-RAB lost due to Yes

S1 I/F down?
pmErabRelAbnormalEnbActTnFail +
No
HO fails Yes
UE dropped? pmErabRelAbnormalEnbActHo +
No
HO excludes Yes
E-RAB? pmErabRelAbnormalEnbActHpr +
No
E-RAB lost due to Yes
UE unreachable? pmErabRelAbnormalEnbActUeLost +
No
Cell downtime Yes
manual interv? pmErabRelAbnormalEnbActCdt +
No
Figure 3-13 RBS Initiated E-RAB Release Flow Chart
The counters illustrated in Figure 3-13 above may be used to

investigation the reason for poor E-RAB retainability performance
in LTE. LTE Handover and the associated parameters are
explained in chapter 7 (LTE Mobility Optimization).
LZT 1239602 R1A © Ericsson 2010 - 63 -

Details of the E-RAB release counters illustrated in Figure 3-13 are

given in the table in Figure 3-14 below.
Managed Counter
Object Type
The total number of abnormal ERAB releases

initiated by the eNB due to S1 interface down and
that there was data in either the UL or DL buffer
pmErabRelAbnormalEnbActTnFail EutranCellFDD (i.e. active). PEG
This counter is stepped for each ERAB that is lost
due to that the S1 interface is lost.
The total number of abnormal ERAB releases by
the eNB due to handover execution failure and
that there was data in either the UL or DL buffer
pmErabRelAbnormalEnbActHo EutranCellFDD (i.e. active). PEG
This counter is stepped when an executed
handover fails and the UE is considered dropped.
the eNB due to handover preparation and that
there was data in either the UL or DL buffer (i.e.
pmErabRelAbnormalEnbActHpr EutranCellFDD active). PEG
This counter is stepped when an executed
handover excludes an ERAB
the eNB due that the contact with the UE is lost
and that there was data in either the UL or DL
pmErabRelAbnormalEnbActUeLost EutranCellFDD buffer (i.e. active). PEG
when UEs are unreachable by the eNB.
the RBS due to cell down time (manual
intervention) when data was in either the UL or
pmErabRelAbnormalEnbActCdt EutranCellFDD DL buffer (i.e. active). PEG
due to cell down time (manual intervention) when
data was in either the UL or DL buffer.
Figure 3-14 RBS Initiated E-RAB Release Flow Chart Counters
The counters illustrated in Figure 3-14 above are not collected by

the Primary scanner on the RBS and as such would require a user-
defined subscription set up to initiate their collection.
The ‘pmErabRelAbnormalEnbActUeLost’ is triggered by the

Radio Connection Supervision algorithm in the RBS.
- 64 - © Ericsson 2010 LZT 1239602 R1A

RADIO CONNECTION SUPERVISION

The principles of the Radio Connection Supervision algorithm are
illustrated in Figure 3-15 below.
RRC_CONNECTED
Maximum
No Inactivity for number of RLC No
‘tInactivityTimer’ retransmissions
0 = Off RLC Acknowledged

Yes Yes
10 to 86400 seconds Mode parameters
RRC_IDLE
Figure 3-15 Radio Connection Supervision Principles
Radio Connection supervision starts when the UE enters the

‘RRC_CONNECTED’ state. The UE will be returned to the
‘RRC_IDLE’ state if UE inactivity or Radio Link Control Failure
(RLC) is detected.
If a Data radio Bearer (DRB) has been inactive in both uplink and
downlink for a certain period, RLC will report inactivity of DRB to
the Radio Connection Supervision. If all DRBs are inactive for the
duration specified by the ‘tInactivityTimer’ RBS parameter Radio
Connection Supervision will trigger a UE release. The
‘tInactivityTimer’ parameter can be set to 0 to switch off
supervision or between 10 and 86400 seconds as illustrated in
Figure 3-15 above.
The number of retransmissions to RLC failure is specified by the

RLC Acknowledged Mode (AM) parameters. Although these
parameters are not configurable by the operator, the uplink power
of the UE can have a big impact on the success of RLC. For this
reason the ‘pZeroNominalPusch’ and ‘pZeroNominalPucch’
parameters can be used to improve LTE retainability.
LZT 1239602 R1A © Ericsson 2010 - 65 -

The operation of the ‘pZeroNominalPusch’ and

‘pZeroNominalPucch’ parameters is illustrated in Figure 3-16
below.
-127 to -96 dBm, Default = -117 dBm
PPUCCH = min {Pmax, pZeroNominalPucch + PL + h[ncqi, nharq] + Fpucch +g[i]} dBm
PUCCH
PUSCH
PUCCH
PPUSCH = min {Pmax,10logM + pZeroNominalPusch + ·PL + mcs + f[i]} dBm
-126 to 24 dBm, Default = -103 dBm

Figure 3-16 Operation of ‘pZeroNominalPusch’ and ‘pZeroNominalPucch’
The other terms in the formulas illustrated in Figure 3-16 above are
explained below:
Pmax is the UE power capability.
PL is the path loss estimated by the UE.
h(n) is a PUCCH format dependent value where ncqi corresponds to

the number of information bits for the CQI, and nharq the number of
HARQ bits.
Ppucch is an offset that depends on the information transmitted on

PUCCH.
G[i] is the current PUCCH power control adjustment state.
M is the number of scheduled resource blocks.
is the path-loss compensation factor, which is set to 1, so the

open loop compensates completely for the path loss.
mcs is a Modulation Coding Scheme specific offset and set to 0.
F[i] is the closed loop power control part included in the uplink
scheduling grant on PDCCH.
- 66 - © Ericsson 2010 LZT 1239602 R1A

It should be remembered that increasing the PUCCH and/or

PUSCH on a particular call can increase the uplink noise and
interference on its neighboring cells as illustrated in Figure 3-17
below.
pmRadioRecInterferencePwr
Increased PUCCH power
Increased PUSCH power
Figure 3-17 Noise and Interference on PUSCH
The noise and interference averaged over every TTI can be

measured with the ‘pmRadioRecInterferencePwr’ counter as
LZT 1239602 R1A © Ericsson 2010 - 67 -

Details of the ‘pmRadioRecInterferencePwr’ counter are given in

the table in Figure 3-18 below.
Counter
Counter Name Managed Object Description
Type
The measured Noise and Interference Power

on PUSCH, according to 36.214
PDF ranges:
[0]: N+I <= -121
[1]: -121 < N+I <= -120
[2]: -120 < N+I <= -119
[3]: -119 < N+I <= -118
[4]: -118 < N+I <= -117
[5]: -117 < N+I <= -116
[6]: -116 < N+I <= -115
pmRadioRecInterferencePwr EutranCellFDD PDF
[7]: -115 < N+I <= -114
[8]: -114< N+I <= -113
[9]: -113 < N+I <= -112
[10]: -112 < N+I <= -108
[11]: -108 < N+I <= -104
[12]: -104 < N+I <= -100
[13]: -100 < N+I <= -96
[14]: -96 < N+I <= -92
[15]: -92 < N+I
An average value is measured on a TTI basis
Figure 3-18 Noise and Interference on PUSCH Counter
The ‘pmRadioRecInterferencePwr’ counter illustrated in Figure

3-18 above is not collected by the Primary scanner on the RBS and
as such would require a user-defined subscription set up to initiate
its collection.
RETAINABILITY FURTHER INVESTIGATION

Once a cell has been highlighted as having poor retainability the
LTE Cell and/or UE Trace applications may be used to investigate
the reason for the dropped calls. The LTE cell and UE trace
applications are explained in chapter 7.
- 68 - © Ericsson 2010 LZT 1239602 R1A

SUMMARY
The participants should now be able to:

1. Measure LTE Retainability performance
2. Describe the E-RAB release procedure and associated
counters
3. Use eNodeB counters to create E-RAB Retainability KPIs
4. Explain the eNodeB parameters that influence Retainability
Figure 3-19 Summary of Chapter 3
LZT 1239602 R1A © Ericsson 2010 - 69 -

LTE Retainability PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE Retainability PDF

Uploaded by

Copyright:

Available Formats

LTE L11 Performance Management and Optimization

3 LTE Retainability Optimization

Figure 3-1 Objectives of Chapter 3

LZT 1239602 R1A © Ericsson 2010 - 51 -

- 52 - © Ericsson 2010 LZT 1239602 R1A

EUTRAN RETAINABILITY KPI

X The ability of user to retain its requested service

E-RAB Release Rate [drops/s]:

* Removed to observe the

Figure 3-2 EUTRAN Retainability KPI

The E-RAB Minutes Per Drop is calculated using the

Using drops per second or minutes per drop to measure

LZT 1239602 R1A © Ericsson 2010 - 53 -

The description of the ‘pmSessionTimeUe’ counter used in the

This counters shows the accumulated active

A UE is said to be ‘in session’ if any data on a DRB (UL or DL)

in session out of session in session

100 msec 100 msec

The ‘pmSessionTimeUe’ counter is aggregated for all UEs in the

The E-RAB can be released using either of the procedures below:

- 54 - © Ericsson 2010 LZT 1239602 R1A

E-RAB RELEASE PROCEDURE

Data buffers OR pmErabRelMmeAct +

All resources for the E-RAB are released

E-RAB RELEASE RESPONSE

Includes a list of released E-RABs

Upon reception of the ‘E-RAB RELEASE COMMAND’ message

Alternatively the RBS can initiate the release of the E-RAB by

LZT 1239602 R1A © Ericsson 2010 - 55 -

Upon reception of the E-RAB RELEASE INDICATION message

Normal release pmErabRelNormalEnb +

Abnormal release pmErabRelAbnormalEnb +

Data buffers OR pmErabRelAbnormalEnbAct +

All resources for the E-RAB are released

E-RAB RELEASE INDICATION

Includes a list of released E-RABs

The ‘pmErabRelAbnormalEnbAct’ counter will be incremented for

If either the MME or RBS wants to remove all remaining E-RABs,

- 56 - © Ericsson 2010 LZT 1239602 R1A

UE CONTEXT RELEASE PROCEDURE

The MME can initiate the UE context release procedure sending

UE CONTEXT RELEASE COMMAND

All resources for the UE context are released

UE CONTEXT RELEASE COMPLETE

Figure 3-7 MME Initiated UE Context Release

LZT 1239602 R1A © Ericsson 2010 - 57 -

The RBS can also initiate the UE context release procedure by

The RBS will increment ‘pmErabRelNormalEnb’ and

Includes release cause

Figure 3-8 RBS Initiated UE Context Release

The ‘pmErabRelAbnormalEnbAct’ and

- 58 - © Ericsson 2010 LZT 1239602 R1A

MME Initiated Release Counters

The total number of E-RAB Releases initiated

LZT 1239602 R1A © Ericsson 2010 - 59 -

RBS Initiated Release Counters

The total number of normal E-RAB Releases per cell initiated by

Figure 3-10 RBS Initiated Release Counters

Only ‘pmErabRelAbnormalEnbAct’ and

- 60 - © Ericsson 2010 LZT 1239602 R1A

UE CONTEXT RELEASE FLOW CHARTS

UE lost due Yes

The counters illustrated in Figure 3-11 above may be used to