05 _ LTE NOKIA RAB and NAS Counters.pdf

05 _ LTE NOKIA RAB and NAS Counters

1. •LTE Bearer Concept
•Bearer
•Smart Admin Control
•S1 and X2 Setup
•LTE Bearer Release
•QCI Counters
LTE RAB and NAS Counters

2. LTE Bearers

3. LTE Bearers
Bearer counters
M8006 –EPS Bearer measurement
setups attempts, setup completions, releases,
for QCI1,2,3,4, non GBR
Pre emption for GBR and Non GBR
Activity time for GBR and Non GBR
M8007 –Radio Bearer
DRB setup attempts, completions,, failures, releases
SRB1 and SRB2 setups, completions and failures

4. LTE520 introduces 8 EPS bearers per UE
The following additional radio bearer combinations per UE
supported.
·SRB1 + SRB2 + 6 x AM DRB
·SRB1 + SRB2 + 7 x AM DRB
·SRB1 + SRB2 + 8 x AM DRB
·SRB1 + SRB2 + 4 x AM DRB + 3 UM DRB
·SRB1 + SRB2 + 5 x AM DRB + 2 UM DRB
·SRB1 + SRB2 + 5 x AM DRB + 3 UM DRB
UE supports up to 8 x AM DRB plus 0 x UM DRBs or up to 5 x AM DRB plus 3 x UM
DRB

5. •LTE Bearer Concept
•Bearer Setup
•Smart Admin Control
•S1 Setup
•X2 Setup
•LTE Bearer Release
•QCI Counters
LTE RAB and NAS Counters

6. Attach Procedure (Positive)
UE eNB MME SGW PGW HSS
Random Access
procedure
RRCConnectionSetupComplete
(EMM:Attach Request, ESM:PDN Connectivity Request)
IntialUEMessage
(EMM:Attach Request, ESM:PDN Connectivity Request)
EIR
ME identity check procedure ME identity check procedure
Authentication / Security Authentication / Security
Location updating
CreateSessionRequest
CreateSessionRensponse
7.Session creation

7. Attach Procedure (Positive)
•M8000C0 Initial context setup requests
•M8006C0 EPS bearer setup attempts
UE eNB MME SGW PGW HSS
InitialContextSetupRequest
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
InitialContextSetupResponse
ULInformationTransfer
UplinkNASTransport
First Uplink Data
First Downlink Data
Modify Bearer Request
Modify Bearer Response
(EMM: Attach Accept, ESM: Activate Default EPS Bearer Context Request)
(EMM: Attach Accept, ESM: Activate Default EPS Bearer Context Request )
(EMM: Attach Complete, ESM: Activate Default EPS Bearer Context Complete)
(EMM: Attach Complete, ESM: Activate Default EPS Bearer Context Complete)
M8007C0 Data RB setup attempts
M8007C10: SRB2 setup attempts
M8007C1 Data RB setup completions
M8007C11: SRB2 SETUP SUCC
M8000C1 Initial context setup completions
M8006C1 EPS bearer setup completions
M8000 S1 AP Measurements: eNodeBlevel
M8006 EPS Bearer Measurements: cell level
M8007 Radio Bearer Measurements: cell level

8. Attach Procedure (Positive)
•M8000C0 Initial context setup requests
•M8006C0 EPS bearer setup attempts
UE eNB MME SGW PGW HSS
InitialContextSetupRequest
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
InitialContextSetupResponse
(EMM: Attach Accept, ESM: Activate Default EPS Bearer Context Request)
(EMM: Attach Accept, ESM: Activate Default EPS Bearer Context Request )
M8007C0 Data RB setup attempts
M8007C10: SRB2 setup attempts
M8007C1 Data RB setup completions
M8007C11: SRB2 SETUP complete

9. NAS Service Request (Negative)
UE eNB MME SGW PGW HSS
InitialContextSetupFailure
M8000C9
S1 setup failure indicated by MME
M8000C8
S1 setup failure, no response from MME

10. NAS Service Request (Negative)
UE eNB MME SGW PGW HSS
InitialContextSetupRequest
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
M8007C2
Data bearer setup failure
TS1Relocexec/Tx2Relocexec
expires
Setup DRB

11. UE eNB MME SGW PGW HSS
InitialContextSetupRequest
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
InitialContextSetupResponse
(withfailurecause)
NAS Service Request (Negative)
M8000C2/C3/C4/C5
Initial context setup failure due to
•Radio network layer
•Transport layer
•Resource reasons
•Other reasons
M8006C2/C3/C4/C5
EPS bearer setup failure due to
•Radio network layer
•Transport layer
•Resource reasons
•Other reasons

12. Data Radio Bearer Setup Counter Summary
M8007C0
M8007C1


Data bearer setup
attempts
Data bearer setup
failures /
completions
M8007C2

13. M8000C2
M8006C2
M8000C0
M8006C0
M8000C1
M8007C1


Initial context &
EPS bearer setup
attempts
Initial context & EPS
bearer setup failures /
completions
M8000C3
M8006C3
M8000C4
M8006C4
M8000C5
M8006C5
failures due to
Radio Network Layer
failures due to
Transport Layer
failures due to
Resource reasons
failures due to
Other reasons
NAS Bearer Setup Counter Summary

14. DRB Setup KPIs
DRB SSR = (DRB setup
successes / DRB setup
attempts) * 100%
100 * sum ([M8007C1]) / sum
([M8007C0])
100 * sum ([DATA_RB_STP_COMP]) / sum
([DATA_RB_STP_ATT])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5003aE-UTRAN Data Radio Bearer Setup Success Ratio
Shows the setup success ratio for the data radio bearer setup procedure
The elementary procedure "RRC connection reconfiguration" is used in this context to
setup a user plane (data) radio bearer

15. DRB Setup KPIs
RB SR= 100 -RB DR RB SR= 100 -
(100*sum([M8007C5])+
([M8007C6]) / sum([M8007C3]+
([M8007C4]+ [M8007C5]+
[M8007C13]+ [M8007C6]))
RB SR= 100 -LTE_5004
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5117aE-UTRAN Radio Bearer Success Ratio
The KPI shows the Radio Bearer Success Ratio given as 100% -Radio Bearer Drop Ratio.

16. 0
2,000
4,000
6,000
8,000
10,000
12,000
50.00
60.00
70.00
80.00
90.00
100.00
23.05.2011 25.05.2011 27.05.2011 29.05.2011 31.05.2011 02.06.2011 04.06.2011 06.06.2011 09.06.2011 11.06.2011 13.06.2011 15.06.2011 17.06.2011 19.06.2011 21.06.2011
LTE_5116a Data Radio Bearer Attempts (#)
LTE_5117a Data Radio Bearer Success Ratio (%)
LTE_5003a Data Radio Bearer Setup Success Ratio (%)
Data Radio Bearer Setup KPIs

17. E-RAB Setup KPIs
E-RAB SSR = (E-RAB setup
successes / E-RAB setup
attempts) * 100 %
100 * sum ([M8006C1]) / sum
([M8006C0])
100 * sum ([EPS_BEARER_SETUP_COMPLETIONS]) / sum
([EPS_BEARER_SETUP_ATTEMPTS])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5017aE-UTRAN E-RAB Setup Success Ratio
Describes the setup success ratio of the elementary E-RAB setup procedure used to setup the
E-RAB between MME and UE
It indicates the E-UTRAN contributionto network accessibility for the end user, not the whole
end-to-end service accessibility.

18. E-RAB Setup KPIs
0
2,000
4,000
6,000
8,000
10,000
12,000
50.00
60.00
70.00
80.00
90.00
100.00
23.05.2011 25.05.2011 27.05.2011 29.05.2011 31.05.2011 02.06.2011 04.06.2011 06.06.2011 09.06.2011 11.06.2011 13.06.2011 15.06.2011 17.06.2011 19.06.2011 21.06.2011
LTE_5118a E-RAB Setup Attempts (#)
LTE_5024a E-RAB Normal Release Ratio RAN View (%)
LTE_5017a E RAB Setup Success Ratio (%)
LTE_5023a E-RAB Normal Release Ratio User Perspective (%)

19. E-RAB SSR QCI1=(E-RAB setup successes
QCI1 / E-RAB setup attempts
QCI1)*100%
100*sum([M8006C35] + [M8006C44]) /
sum([M8006C17] + [M8006C26])
100*sum([EPS_BEARER_STP_COM_INI_QCI1] + [EPS_BEAR_SET_COM_ADDIT_QCI1]) /
sum([EPS_BEARER_STP_ATT_INI_QCI_1] + [EPS_BEARER_STP_ATT_ADD_QCI_1])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5204a E-UTRAN E-RAB SetupSuccess Ratio, QCI1
The KPI describes the setup success ratio of the elementary E-RAB setup procedure used to
setup the E-RAB between MME and UE for QCI1 DRBs.
It indicates the E-UTRAN contribution to network accessibility for the end-user, not the whole
end-to-end service accessibility.
E-RAB Setup KPIs

20. E-RAB Setup KPIs
E-RAB SSR QCI2=(E-RAB setup successes
QCI2 / E-RAB setup attempts
QCI2)*100%
100*sum([M8006C168] + [M8006C171])
/ sum([M8006C162] + [M8006C165])
100*sum([EPS_BEARER_STP_COM_INI_QCI_2] + [EPS_BEAR_SET_COM_ADD_QCI_2]) /
sum([EPS_BEARER_STP_ATT_INI_QCI_2] + [EPS_BEARER_STP_ATT_ADD_QCI_2])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5553a E-UTRAN E-RAB SetupSuccess Ratio, QCI2
The KPI describes the setup success ratio of the elementary E-RAB setup procedure used to
setup the E-RAB between MME and UE for QCI2 DRBs.
It indicates the E-UTRAN contribution to network accessibility for the end-user, not the whole
end-to-end service accessibility.
In a similar manner LTE_5554a and LTE_5555a calculate success ratio for QCI 3 and 4
respectively

21. E-RAB Setup KPIs
E-RAB SSR non GBR=(E-RAB setup successes
non GBR / E-RAB setup attempts non
GBR)*100%
100*sum(([M8006C1] -([M8006C35] +
[M8006C44]) -([M8006C168] + [M8006C171]) -
([M8006C169] + [M8006C172]) -([M8006C169]
+ [M8006C173])) / sum([M8006C0] -
([M8006C17] + [M8006C26]) -([M8006C162] +
[M8006C165]) -([M8006C163] + [M8006C166])
-([M8006C164] + [M8006C167])))
100*sum(EPS_BEARER_SETUP_COMPLETIONS] -([EPS_BEARER_STP_COM_INI_QCI1]
+[EPS_BEAR_SET_COM_ADD_QCI1]) -([EPS_BEARER_STP_COM_INI_QCI_2] +
[EPS_BEAR_SET_COM_ADD_QCI_2]) -([EPS_BEARER_STP_COM_INI_QCI_3] +
[EPS_BEAR_SET_COM_ADD_QCI_3]) -([EPS_BEARER_STP_COM_INI_QCI_4] +
[EPS_BEAR_SET_COM_ADD_QCI_4])) / sum([EPS_BEARER_SETUP_ATTEMPTS] -
([EPS_BEARER_STP_ATT_INI_QCI_1] + [EPS_BEARER_STP_ATT_ADD_QCI_1]) -
([EPS_BEARER_STP_ATT_INI_QCI_2] + [EPS_BEARER_STP_ATT_ADD_QCI_2]) -
([EPS_BEARER_STP_ATT_INI_QCI_3] + [EPS_BEARER_STP_ATT_ADD_QCI_3]) -
([EPS_BEARER_STP_ATT_INI_QCI_4] + [EPS_BEARER_STP_ATT_ADD_QCI_4]))
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5217b E-UTRAN E-RAB SetupSuccess Ratio, non -GBR
The KPI describes the setup success ratio of the elementary E-RAB setup procedure used to
setup the E-RAB between MME and UE for non GBR services.
It indicates the E-UTRAN contribution to network accessibility for the end-user, not the whole
end-to-end service accessibility.

22. CSSR (Call Setup Success Rate)
0
200
400
600
800
1000
1200
1400
18.10.2010 19.10.2010 20.10.2010 21.10.2010 22.10.2010 23.10.2010 24.10.2010 25.10.2010 26.10.2010 27.10.2010 28.10.2010 29.10.2010 30.10.2010 31.10.2010 01.11.2010 02.11.2010 03.11.2010 04.11.2010 05.11.2010 06.11.2010
0
10
20
30
40
50
60
70
80
90
100
%
eRAB Setup Attempts CSSR [%] Call Setup Success Ratio =
RRC setup success ratio * RAB setup success ratio (like for WCDMA)
NAS Bearer Setup KPIs

23. •LTE Bearer Concept
•Bearer Setup
•Smart Admin Control
•S1 Setup
•X2 Setup
•LTE Bearer Release
•QCI Counters
LTE RAB and NAS Counters

24. Smart Admin Control and ARP
•Smart Admission Control
•Smart admission control is a feature only for GBR traffic
and is required to prevent congestion on “guaranteed”
resources.
•The counter based RAC is replaced by a measurement
based function which leads to a more accurate and
dynamic system behavior. Counting of used resources and
applying statistical methods on load schemes will not work
when serving high bit rate users.
•ARP based admission Control
If an E-RAB shall be admitted, it needs resources:
•In case of insufficient free resources, the E-RAB will be rejected.
•With LTE534: In case of insufficient free resources, other E-
RABs may be pre-empted to steal their resources.
•Pre-Emption decisions are based on ARP parameters, which are
provided for each E-RAB by EPC.
ARP = Allocation and
retention/maintenance Priority
Service management
High RB requests with congestion control by
using of priority and smart admissions
Rejected UE requests due of too high RB
utilization
Only for QCI 2-4
Not for VoIP
Descriptions / Objective:
To admit or to reject the requests for
establishment of Radio Bearers (RB)
on a cell basis
Based on number of RRC connections
and number of active users per cell w/s
allocation and retention priority (ARP)
S-RAC
LTE497 Smart Admission Control
LTE534 ARP (Radio) Admission Control for E-RABs

25. M8013C28 Pre-empted UE contexts due to pre-emption of last non-GBR bearer
•ARP concept
•Each time an E-RABneeds to be established
–some bearer combination,
–radio resources
–transport resources
are required.
•Insufficient resources available
–Other E-RABs may be preemptedto steal their resources
or
–Request is rejected
•Controlled by an ARP parameter
–Mandatory part of any E-RAB requested by EPC
ARP Counters

26. •LTE Bearer Concept
•Bearer Setup
•Smart Admin Control
•S1 Setup
•X2 Setup
•LTE Bearer Release
•QCI Counters
LTE RAB and NAS Counters

27. S1 Setup Procedure
eNB MME
S1AP: S1 SETUP REQUEST
SCTP: SACK
S1AP: S1 SETUP RESPONSE
SCTP: SACK
eNB global ID, eNB name, supported TAs and Paging DRX configuration
ServedGUMMEI, Relative MME capacity
GUMMEI: Globally Unique MME Identity
TA: Tracking Area
DRX: Discontinue Reception
M8000C6: S1 Setup attempt
M8000C7: S1 Setup complete

28. M8000C8
S1 Setup Counter Summary
M8000C6
M8000C7


S1 setup
attempts
S1 setup failures
/ completions
M8000C9

29. S1 SSR = (S1 setup
successes / S1 setup
attempts) * 100%
100 * sum([M8000C7]) /
sum ([M8000C6])
100 * sum ([S1_SETUP_SUCC]) / sum
([S1_SETUP_ATT])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5014aE-UTRAN S1 Setup Success Ratio
Shows the setup success ratio for the elementary procedure "S1 Setup“
When this procedure is finished S1 interface is operational and other S1 messages can be
exchanged
S1 Setup KPIs

30. S1 initial context Setup Procedure
All S1 messages are treated as SCTP data, thus everytimeeither eNBor MME receives S1
message, it shall sends back selective acknowledge (SACK) chunk to its peer.
M8013 LTE UE State

31. UE LOGS1 Succrate =( UE-
specific logical S1 Signaling
Connection Completions/
UE-specific logical S1
Signaling Connection
Attempts)*100%
100*
sum([M8013C44])/sum
([M8013C43])
100* sum([S1_SIGN_CONN_ESTAB_SUCC_UE])/
sum([S1_SIGN_CONN_ESTAB_ATT_UE])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5526a E-UTRAN UE-specific logical S1 Signaling Connection Success Rate
This KPI describes the ratio of UE-specific logical S1 Signaling Connection Completions to total attempts.
Context Setup KPIs

32. LTE RAB and NAS Counters
•LTE Bearer Concept
•Bearer Setup
•Smart Admin Control
•S1 Setup
•X2 Setup
•LTE Bearer Release
•QCI Counters

33. LTE X2AP (8022)
It provides measurements related to X2 Setup procedure.
The counters are updated at the originating eNBsite
eNB1 eNB2
X2AP: X2SETUP REQUEST
X2AP: X2SETUP RESPONSE
X2Setup Procedure: Positive
M8022C0: X2 setup attempt

34. LTE X2AP (8022)
It provides measurements related to X2 Setup procedure.
The counters are updated at the originating eNBsite
eNB1 eNB2
X2AP: X2SETUP REQUEST
X2AP: X2SETUP FAILURE
X2Setup Procedure: Negative
M8022C0: X2 setup attempt
M8022C1: X2 setup failure
message or expiration of Timer (wait for X2 SETUP RESPONSE)
3GPP TS 36.423

35. •LTE Bearer Concept
•Bearer Setup
•Smart Admin Control
•S1 Setup
•X2 Setup
•LTE Bearer Release
•QCI Counters
LTE RAB and NAS Counters

36. eNodeBInitiated Transition to ECM Idle
Transition due to inactivity
UE consumes less battery power in idle mode
Less active UEs which network has to handle
Fast going to inactivity has drawback of longer connection setup time (more transitions idle to
connected)
eNBUE MME S-GW
S1AP: UE Context Release Command
S1AP: UE Context Release Complete
RRC: RRC Connection Release
Release all UE related
resources,
remove UE context
Set UE to
RRC-IDLE
Set UE to
ECM-IDLE
Detect user inactivity
or other eNBtrigger
S1AP: UE Context Release Request
S11 interaction to inform S-GW
about connection release
UE in
RRC-CONNECTED
L2 ACK
InactivityTimer
LNCEL, 10..65535 s, 30s

37. S1AP: UEContextReleaseRequest
With cause
eNodeBinitiated EPS bearer release
M8006C10 normal release (UE inactivity)
M8006C15 radio network layer inter-RAT redirection
eNodeBinitiated transition to ECM idle
M8013C13 normal release
S1AP: UEContextReleaseCommand
With cause
S1AP: UEContextReleaseComplete
eNB MME
ECM_IDLE
ECM_CONNECTED
Radio bearer release
M8007C3 normal release
M8006 EPS Bearer Measurements: cell level
M8007 Radio Bearer Measurements: cell level
M8013 UE State Measurements: cell level
eNodeBInitiated Transition to ECM Idle (Positive)

38. S1AP: UEContextReleaseRequest
With cause
S1AP: UEContextReleaseCommand
With cause
S1AP: UEContextReleaseComplete
eNB MME
ECM_IDLE
ECM_CONNECTED
EPC initiated EPS bearer release
M8006C6 normal release (UE initiated)
M8006C7 detach (UE or MME initiated)
EPC initiated transition to ECM idle
M8013C9 normal release (UE initiated)
M8013C10 detach (UE or MME initiated)
Radio bearer release
M8007C4 detach
M8006 EPS Bearer Measurements: cell level
M8007 Radio Bearer Measurements: cell level
M8013 UE State Measurements: cell level
EPC Initiated Transition to ECM Idle(Positive)

39. S1AP: UEContextReleaseRequest
With cause
S1AP: UEContextReleaseCommand
With cause
S1AP: UEContextReleaseComplete
eNB MME
ECM_IDLE
ECM_CONNECTED
eNodeBinitiated EPS bearer release
M8006C12 radio link failure
M8006C14 transport network unavailable
M8006C13 other failure
eNodeBinitiated transition to ECM idle
M8013C15 radio link failure
M8013C16 other failure
Radio bearer release
M8007C5 radio link failure
M8007C6 other failure
Transition to ECM Idle (Negative)

40. S1AP: UEContextReleaseCommand
With cause
S1AP: UEContextReleaseComplete
eNB MME
ECM_IDLE
ECM_CONNECTED
EPC initiated EPS bearer release
M8006C8 radio network layer cause
M8006C9 other cause
EPC initiated transition to ECM idle
M8013C11 radio network layer cause
M8013C12 other cause
Radio bearer release
M8007C5 radio network layer cause
M8007C6 other cause
Transition to ECM Idle (Negative)

41. eNodeB initiated
M8006C10/C15
EPC initiated
M8006C6/C7


EPS bearer releases
Always triggers radio
bearer release
eNodeB initiated
M8006C12/C13/C14
EPC initiated
M8006C8/C9
M8007C3/C4
Radio bearer releases
M8007C5/C6
eNodeB initiated
M8013C13
EPC initiated
M8013C9/C10
Transitions to ECM idle
Always triggers EPS bearer
release
eNodeB initiated
M8013C15/C16
EPC initiated
M8013C11/C12
LTE Bearer Release Counter Summary

42. LTE Bearer Release KPIs
E-RAB NRR UP = (normal E-RAB
releases user perspective / all E-
RAB releases) * 100%
100*sum([M8006C255] +
[M8006C258] +
[M8006C260] + [M8006C6]
+ [M8006C7]) /sum
([M8006C254] +
[M8006C261] + [M8006C6]
+ [M8006C7] + [M8006C8]
+ [M8006C9])
100*sum( [ERAB_REL_ENB_RNL_INA] +
[ERAB_REL_ENB_RNL_RED] + [ERAB_REL_ENB_RNL_RRNA] +
[EPC_EPS_BEARER_REL_REQ_NORM] +
[EPC_EPS_BEARER_REL_REQ_DETACH])
/sum([ERAB_REL_ENB] + [ERAB_REL_HO_PART] +
[EPC_EPS_BEARER_REL_REQ_NORM] +
[EPC_EPS_BEARER_REL_REQ_DETACH] +
[EPC_EPS_BEARER_REL_REQ_RNL] +
[EPC_EPS_BEARER_REL_REQ_OTH])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5023e E-RAB Normal Release Ratio, user perspective
Describes the ratio of normally released E-RABs from user perspective
Corresponding to a connection completion ratio

43. LTE Bearer Release KPIs
E-RAB NRR UP = (normal E-
RAB releases RAN perspective
/ all E-RAB releases) * 100%
100*sum ([M8006C255] +
[M8006C258] + [M8006C260]
+ [M8006C6] + [M8006C7] +
[M8006C8] + [M8006C9])
/sum ([M8006C254] +
[M8006C261] + [M8006C6] +
[M8006C7] + [M8006C8] +
[M8006C9])
100*sum( [ERAB_REL_ENB_RNL_INA] +
[ERAB_REL_ENB_RNL_RED] + [ERAB_REL_ENB_RNL_RRNA] +
[EPC_EPS_BEARER_REL_REQ_NORM] +
[EPC_EPS_BEARER_REL_REQ_DETACH] +
[EPC_EPS_BEARER_REL_REQ_RNL] +
[EPC_EPS_BEARER_REL_REQ_OTH]) /sum ([ERAB_REL_ENB]
+ [ERAB_REL_HO_PART] +
[EPC_EPS_BEARER_REL_REQ_NORM] +
[EPC_EPS_BEARER_REL_REQ_DETACH] +
[EPC_EPS_BEARER_REL_REQ_RNL] +
[EPC_EPS_BEARER_REL_REQ_OTH]) Logical formula
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5024e E-RAB Normal Release Ratio, RAN perspective
Describes the ratio of normally released E-RABs from RAN perspective
M80006C8/9 are included in RAN
perspective,
E-RAB releases due to "No Radio Resources Available“(M8006C260) initiated by eNBare arecounted as
normal releases as they are not real drops resulted from any radio quality problems.

44. LTE Bearer Release KPIs
E-RAB DR = (abnormal E-RAB
release requests, user perspective
/ all E-RAB releases) * 100%
100*sum([M8006C261]
+ [M8006C254] -
[M8006C255] -
[M8006C258] –
[M8006C260]
+[M8006C8] +
[M8006C9]) /sum
([M8006C254] +
[M8006C261] +
[M8006C6] + [M8006C7]
+ [M8006C8] +
[M8006C9])
100*sum( [ERAB_REL_HO_PART] + [ERAB_REL_ENB] -
[ERAB_REL_ENB_RNL_INA] -[ERAB_REL_ENB_RNL_RED] -
[ERAB_REL_ENB_RNL_RRNA] +
[EPC_EPS_BEARER_REL_REQ_RNL] +
[EPC_EPS_BEARER_REL_REQ_OTH]) /sum ([ERAB_REL_ENB] +
[ERAB_REL_HO_PART] + [EPC_EPS_BEARER_REL_REQ_NORM] +
[EPC_EPS_BEARER_REL_REQ_DETACH] +
[EPC_EPS_BEARER_REL_REQ_RNL] +
[EPC_EPS_BEARER_REL_REQ_OTH])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5119d E-RAB Drop Ratio, User View
Describes the ratio of abnormally released (dropped) E-RABs from user point of view
Each bearer of the "Bearer to be Released List" IE is counted
User point of view means that as abnormal E-RAB drops both those ones initiated by eNBand EPC
are counted
M8006C8/9 included in user drop view
but not in RAN view

45. LTE Bearer Release KPIs
E-RAB DR = (abnormal E-RAB
releases from RAN point of view /
all E-RAB releases) * 100%
100*sum([M8006C12]+
[M8006C14]+ [M8006C13])/sum
([M8006C6]+ [M8006C7]+
[M8006C8]+ [M8006C9] +
[M8006C15]+ [M8006C10]+
[M8006C12] + [M8006C14]+
[M8006C13]+ [M8006C174] +
[M8006C175])
100*sum([ENB_EPS_BEARER_REL_REQ_RNL]
+[ENB_EPS_BEARER_REL_REQ_TNL]+
[ENB_EPS_BEARER_REL_REQ_OTH])/sum
([EPC_EPS_BEARER_REL_REQ_NORM]+
[EPC_EPS_BEARER_REL_REQ_DETACH]+
[EPC_EPS_BEARER_REL_REQ_RNL] +[EPC_EPS_BEARER_REL_REQ_OTH] +
[ENB_EPSBEAR_REL_REQ_RNL_REDIR]
+[ENB_EPS_BEARER_REL_REQ_NORM]
+[ENB_EPS_BEARER_REL_REQ_RNL]+ [ENB_EPS_BEARER_REL_REQ_TNL]+
[ENB_EPS_BEARER_REL_REQ_OTH]+ [PRE_EMPT_GBR_BEARER] +
[PRE_EMPT_NON_GBR_BEARER])
Logical formula
Summarization
formula (PI ID) Summarization formula (Abbreviation)
LTE_5025dE-RAB Drop Ratio, RAN View
Describes the ratio of abnormally released (dropped) E-RABs from RAN point of view
Each bearer of the "Bearer to be Released List" IE is counted
RAN point of view means that as abnormal E-RAB drops only those ones initiated by eNBare
counted
Also –Drop ratio for QCI1 RAN view
LTE_5572a

46. LTE1819 Data Session Profiling
•Data Session Profiling adapts the UE inactivity timer based on UE
data session short term history
•With LTE1819 when a new RRC connection request is received the
eNodeBchecks for the same S-TMSI from the database and adapts UE
inactivity timer based on UE data session short term history
• If S-TMSI is found and the timestamp indicated data activity in very recent history,
the eNodeBapplies a long operator configurable inactivity timer for the UE
• Otherwise a short operator configurable timer is applied
•2 new counters:
•M8013C70 INACT_TIME_REL_SHORT
•M8013C71 INACT_TIME_REL_LONG

47. •LTE Bearer Concept
•Bearer Setup
•Smart Admin Control
•S1 Setup
•X2 Setup
•QCI counters
LTE RAB and NAS Counters

48. Operator Specific QCI
•In RL30 –up to 21 additional QCIs are defined
•Only for non-GBR bearers
•QCI range is 128…254
•For each QCI an additional counterGroupis defined
•Examples of Counter Groups for the typical use cases:
•1. Better user and service differentiation for non-GBR services for one operator:
•Bronze users:QCI: 130, 131, 132, 133 Counter Group 1
•Silver users: QCI: 140, 141, 142, 143 Counter Group 2
•Gold users: QCI: 150, 151, 152, 153 Counter Group 3
•2. RAN sharing (operators share eNodeB) to define a set of QCIs dedicated for each operator:
•Operator A: QCI: 140, 141, 142, 143 Counter Group 1
•Operator B: QCI: 160, 161, 162, 163 Counter Group 2
counterGroup
The counter group to which the
QCI belongs
LNBTS; 1..6;1; -

49. LTE UE and Service Differentiation (8023)
LTE UE and Service Differentiation (M8023) measures Operator specific UE and Service Differentiation items.
M8023C0..5
PDCP SDU data volume on eUuInterface UL for UEs assigned to QCI Counter Group 1..6
M8023C6 ..11
PDCP SDU data volume on eUuInterface DL for UEs assigned to QCI Counter Group 1..6
M8023C21..26
Average number of active UEs of QCI Counter Group 1..6