Formulas 160516

IDEA-ZTE
19 May 2016
Agenda
 Network KPIs
 KPI Formulas
 Counter Description
© ZTE Corporation. All rights reserved

2
Network KPIs
KPIs (for 4G sites/cells) UoM Granularity 11-May-16 12-May-16 13-May-16 14-May-16 15-May-16 16-May-16
SN
A No of Nodes
Total 4G Sites NUM 2462 2462 2462 2462 2462 2462
1
2 4G VLR Subs Regd. NUM NBH
B Radio Network Capacity & Utilization
3 Total Traffic-4G GB 24 HRS 6509.7494 6202.4430 7060.2994 6919.1236 6861.1986 6563.4183
4 Data Volume (DL) - Total-4G GB 24 HRS 5942.3406 5655.5509 6433.6785 6333.1440 6298.9230 5983.2765
5 Data Volume (UL) - Total-4G GB 24 HRS 567.4089 546.8959 626.6125 585.9787 562.2765 580.1436
6 CSFB MO Call attempts. NUM 24 HRS 432316 418509 428492 405366 339652 452393
7 CSFB MT Call attempts NUM 24 HRS 456555 450779 452241 431049 363222 472307
8 % eNB with Traffic Volume > 20 GB % 24 HRS 0.04 0.04 0.04 0.00 0.04 0.04
9 % eNB with Traffic Volume >= 10 GB & <20 GB % 24 HRS 1.67 1.39 1.75 1.61 1.91 1.32
10 % eNB with Traffic Volume >= 5 GB & <10 GB % 24 HRS 10.56 9.87 11.23 12.15 12.45 11.90
11 % eNB with Traffic Volume < 5 GB % 24 HRS 87.73 88.70 86.80 86.23 85.60 86.74
12 Total data Traffic-4G (Radio) GB NBH 479.32 401.54 446.01 533.43 456.91 550.18
13 Data Volume (DL) - Total-4G GB NBH 442.79 372.01 416.01 497.15 425.91 509.63
14 Data Volume (UL) - Total-4G GB NBH 36.54 29.53 30.00 36.28 31.01 40.55
15 %eNodeB with < 25 subs(RRC connected users) % NBH 98.65 99.35 98.77 95.45 96.22 95.33
16 %eNodeB with < 50 subs & >25 subs % NBH 1.35 0.65 1.23 4.55 3.78 4.67
17 %eNodeB with < 100 subs & > 50 subs 0.00 0.00 0.00 0.00 0.00 0.00
18 %eNodeB with > 100 subs % NBH 0.00 0.00 0.00 0.00 0.00 0.00
19 % cells DL PRB Utilization >=70% (AVG of Hr) % NBH 0.00 0.00 0.00 0.00 0.00 0.00
20 % cells UL PRB Utilization >=70% (AVG of Hr) % NBH 0.00 0.00 0.00 0.00 0.00 0.00
C Radio Network Accessibility (NBH)
21 RRC Setup successful rate % NBH 99.95 99.89 99.90 99.94 99.94 99.95
22 E-RAB Setup Success Rate % NBH 99.94 99.84 99.89 99.92 99.91 99.94
23 S1 Sig Setup Success Rate % NBH 100.00 99.50 100.00 100.00 100.00 100.00
24 Initial E-rab Setup Success Rate(RRC+Sig+E rab) % NBH 99.86 99.56 99.58 99.66 99.72 99.84
3
Network KPIs
SN
D Radio Network Mobility (NBH)
Intra Frequency Handover Success Rate (X2, S1
% NBH
25 Combined) 99.50 99.35 99.55 99.51 99.38 99.48
26 Handover over X2 success Rate % NBH 99.45 99.25 99.49 99.44 99.30 99.42
27 Handover over S1 success Rate % NBH 97.68 99.35 98.46 97.27 97.27 97.86
E Radio Network Integrity (NBH)
28 Average Number of Users (RRC connected User) NUM NBH 1 1 1 1 1 1
29 Peak Number of Users (RRC connected User) NUM NBH 43 40 43 50 44 44
30 CSFB Setup Success Rate(4G side) % NBH 99.11 99.90 99.87 99.89 99.47 99.90
E Radio Network Integrity (NBH)
31 MIMO Utilization- Rank Indicator-1 % NBH 24.53 24.64 24.68 25.22 24.84 24.74
32 MIMO Utilization- Rank Indicator-2 % NBH 75.47 75.36 75.32 74.78 75.16 75.26
33 Average CQI NUM NBH 10.63 10.70 10.66 10.61 10.63 10.61
34 Average MCS in Uplink NUM NBH 14 14 14 14 14 14
35 Average MCS IN Downlink NUM NBH 16 16 16 16 16 15
36 PDCCH Aggregation Level-1 Utilization % NBH 9.73 10.105 10.385 9.68 9.28 9.93
40 Average Cell DL PDCP Throughput Mbps NBH 7.43 7.41 7.75 7.57 7.47 7.55
41 Average Cell UL PDCP Throughput (per cell) Mbps NBH 0.75 0.71 0.71 0.71 0.68 0.76
44 %cells having more than 70% samples for CQI>10 % NBH 21.33 20.92 21.10 21.26 20.75 21.66
46 Downlink Latency (ms) (Radio) MS NBH 7.90 8.24 7.88 7.41 7.41 7.08

4
Network KPIs
SN
F Radio Network Retaibility (NBH)
47 E-RAB Drop Rate (%) % NBH 0.020 0.010 0.090 0.020 0.010 0.010
48 DL Packet Loss Rate (%) % NBH 0.000 0.00 0.00 0.00 0.000 0.000
49 UL Packet Loss Rate (%) % NBH 0.185 0.015 0.005 0.150 0.100 0.390
G Radio Network Accessibility (BBH)
50 % cell -RRC Setup successful rate >98% % BBH 99.63 99.40 99.30 99.42 99.58 99.44
51 % cell -E-RAB Setup Success Rate >98% % BBH 98.93 99.02 99.01 98.97 99.05 99.17
52 % cell -S1 Sig Setup Success Rate >98% % BBH 99.07 99.18 99.32 99.43 99.38 99.39
% cell -Initial E-rab Setup Success
% BBH
53 Rate(RRC+Sig+E rab) >98% 97.05 95.83 96.94 97.38 97.38 97.47
H Radio Network Mobility (BBH)
% cell -Intra Frequency Handover Success Rate
% BBH
54 >98% 88.04 87.83 91.15 89.60 90.09 90.09
55 % cell -Handover over X2 success Rate >98% % BBH 93.09 92.70 93.56 92.92 93.90 93.48
56 % cell -Handover over S1 success Rate >98% % BBH 98.54 98.13 98.25 98.70 98.90 98.70
E Radio Network Integrity (BBH)
% Cells having - Average DL PDCP Throughput
Mbps BBH
57 (per cell) > 8 Mbps 53.87 54.92 57.02 58.35 58.01 57.13
% Cells having - Average UL PDCP Throughput
Mbps BBH
58 (per cell) > 5 Mbps 6.67 6.86 6.69 5.94 5.64 5.46
E Radio Network Retainability (BBH)
59 % cell- E-RAB Drop Rate < 1% % BBH 99.52 99.44 99.40 99.66 99.74 99.63
F Radio Network Avaialbility (24H)
60 Radio Network Avaialbility % 24 HRS 86.96 90.30 92.93 89.09 93.21 91.11
Uplink Load (RSSI or RTWP) - No. of cells >-
Number NBH
61 95dbm 124 133 144 155 170 155

5
Network KPIs-Accessibility
RRC Setup Successful
Rate (%)
E-RAB Establish Success

Rate (%)
Accessibility
S1 Sig Setup Success

Rate (%)
Initial E-rab Setup Success

Rate(RRC+Sig+E rab)
6
Network KPIs-Retainability
E-RAB Drop rate(%)
Retainability DL Packet Loss Rate (%)
UL Packet Loss Rate (%)

7
Network KPIs-Mobility
Intra Frequency Outgoing
Handover Execution
Success Rate(%)
X2 Intra Frequency
Mobility Outgoing Handover
Success Rate(%)
S1 Intra Frequency
Outgoing Handover
Success Rate(%)
8
Network KPIs-Integrity
Average Cell DL PDCP
Throughput(Mbps)
CSFB Setup Success Rate(4G

side)
Average Cell UL PDCP

Throughput(Mbps)
Rank Indicator=1/ Rank
Indicator=2
Integrity
User DL
Throughput(Mbps)
PDCCH Aggregation Level-

1/Level-2/Level-4/Level-8
User UL
Throughput(Mbps)

9
RRC Setup Successful
Rate (%)
The RRC Setup procedure is triggered by different reasons as identified by the

establishment Cause field in the RRC Connection Request messages: Emergency, High
Priority Access, MT-Access, MO-Access, MO-Data, Delay Tolerant Access.
UE Sets the establishment Cause and received by eNB.
RRC_Setup Successful Rate= RRC Connection Success/RRC Connection Attempt*100

10
RRC Setup Successful (C373200000+C373200004+C373200008+C373200012+C373200
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200000 Number of Successful Mt-Access RRC Establishment

Short Name
RRC.ConnEstabSucc.CauseMtAccess
Counter Description
The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment. The counter is
used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mt-
Access.
Triggering Point
When the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishment Cause is mt-access.
Update Description
The counter is incremented by 1 when the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishment
Cause is mt-access.
Unit
times

11
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200004 Number of Successful Mo-Signalling RRC Establishment

Short Name
RRC.ConnEstabSucc.CauseMoSignalling
Counter Description
used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mo-
Signalling.
Triggering Point
When the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishmentCause is mo-signalling.
Update Description
The counter is incremented by 1 when the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishment
Cause is mo-signalling.
Unit
times

12
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200008 Number of Successful Mo-Data RRC Establishment

Short Name
RRC.ConnEstabSucc.CauseMoData
Counter Description
used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mo-
Data.
Triggering Point
When the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishmentCause is mo-Data.
Update Description
The counter is incremented by 1 when the eNodeB receives the RRCConnectionSetupComplete message from the UE and the
establishmentCause is mo-Data.
Unit
times

13
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200012 Number of Successful HighPriorityAccess RRC Establishment

Short Name
RRC.ConnEstabSucc.CauseHighPriorityAccess
Counter Description
used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is
highPriorityAccess.
Triggering Point
When the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishmentCause is highPriorityAccess.
Update Description
establishmentCause is highPriorityAccess.
Unit
times

14
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200016 Number of Successful Emergency RRC Establishment

Short Name
RRC.ConnEstabSucc.CauseEmergency
Counter Description
emergency.
Triggering Point
When the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishmentCause is emergency.
Update Description
establishmentCause is emergency.
Unit
times

15
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200120 Number of Successful delayTolerantAccess RRC Establishment

Short Name
RRC.ConnEstabSucc.CauseDelayTolerantAccess
Counter Description
The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is
delayTolerantAccess.
Triggering Point
When the eNodeB receives the RRCConnectionSetupComplete message from the UE and the establishmentCause is delayTolerantAccess.
Update Description
The counter is incremented by 1 when the eNodeB receives the
RRCConnectionSetupComplete message from the UE and the establishmentCause is delayTolerantAccess.
Unit
times

16
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200084 Number of Mt-Access RRC Establishment Request

Short Name
RRC.ConnEstabAtt.CauseMtAccess
Counter Description
The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mt-access. Each RRC
ConnectionRequest message received is added to the counter.
Triggering Point
When the eNodeB receives the RRCConnectionRequest message from UE and the RRC Connection setup cause is mt-access.
Update Description
The counter is incremented by 1 when the eNodeB receives the RRCConnectionRequest message from UE and the RRC Connection setup cause
is mt-access.
Unit
times

17
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200085 Number of Mo-Signalling RRC Establishment Request

Short Name
RRC.ConnEstabAtt.CauseMoSignalling
Counter Description
The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mo-Signalling. Each RRC
Triggering Point
When the eNodeB receives the RRCConnectionRequest message from UE and the RRC Connection setup cause is mo-Signalling.
Update Description
is mo-Signalling.
Unit
times

18
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200086 Number of Mo-Data RRC Establishment Request

Short Name
RRC.ConnEstabAtt.CauseMoData
Counter Description
The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mo-Data. Each RRC
Triggering Point
When the eNodeB receives the RRCConnectionRequest message from UE and the RRC Connection setup cause is mo-Data.
Update Description
is mo-Data.
Unit
times

19
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200087 Number of HighPriorityAccess RRC Establishment Request

Short Name
RRC.ConnEstabAtt.CauseHighPriorityAccess
Counter Description
The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is highPriorityAccess. Each RRC
Triggering Point
When the eNodeB receives the RRCConnectionRequest message from UE and the RRC Connection setup cause is highPriorityAccess.
Update Description
is highPriorityAccess.
Unit
times

20
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200088 Number of Emergency RRC Establishment Request

Short Name
RRC.ConnEstabAtt.CauseEmergency
Counter Description
The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is emergency. Each RRC
Triggering Point
When the eNodeB receives the RRCConnectionRequest message from UE and the RRC Connection setup cause is emergency.
Update Description
is emergency.
Unit
times

21
Rate (%) 016+C373200120)/(C373200084+C373200085+C373200086+C37
3200087+C373200088+C373200124)
C373200124 Number of delayTolerantAccess RRC Establishment Request

Short Name
RRC.ConnEstabAtt.CauseDelayTolerantAccess
Counter Description
The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is delayTolerantAccess. Each RRC
Triggering Point
When the eNodeB receives the RRC Connection Request message from UE and the RRC Connection setup cause is delayTolerantAccess.
Update Description
is delayTolerantAccess.
Unit
times

22
Rate (%)
This index indicates the success ratio of E-RAB establishment, including initial
E-RAB establishment and added E-RAB establishment.
E-RAB Establish Success Rate (%)= Total E-RAB EstabSucc/Total E-RAB EstabAtt*100
If a different QOS characteristics is required with the QOS characteristics provided by an existing Intial E-RAB, an Added E-RAB can
be requested. QOS Characteristics can be defined on an E-RAB basis, hence both Initial E-RAB establishment Success Rate(A1) and
Added E-RAB establishment success rate(A2) shall be available per QOS Group.

23
(C373505473+C373505481)/(C373505472+C373505480)
Rate (%)
C373505473 Number of Initial E-RAB Successful Setup

Short Name
ERAB.EstabInitSuccNbr
Counter Description
On transmission by the eNodeB of an INITIAL CONTEXT SETUP RESPONSE message, in which each E-RAB successfully established is added to the
counter.
Triggering Point
When the eNodeB replies the InitialContextSetupResponse to the MME.
Update Description
The counter is incremented by 1 for every E-RAB when eNodeB sends the InitialContextSetupResponse message to MME and the E-RAB Setup List
IE includes the E-RAB.
Unit
unit

24
(C373505473+C373505481)/(C373505472+C373505480)
Rate (%)
C373505481 Number of Additional E-RAB Successful Setup

Short Name
ERAB.EstabAddSuccNbr
Counter Description
On transmission by the eNodeB of an E-RAB SETUP RESPONSE message, in which each E-RAB successfully established is added to the counter.
Triggering Point
When the eNodeB replies the E-RABSetupResponse to the MME, and the E-RAB Setup List IE includes E-RAB.
Update Description
The counter is incremented by 1 for every E-RAB when eNodeB sends E-RABSetupResponse to MME and the E-RAB Setup List IE includes the E-
RAB.
Unit
unit

25
(C373505473+C373505481)/(C373505472+C373505480)
Rate (%)
C373505472 Number of Initial E-RAB Setup Attempt
Counter Description
On receipt by the eNodeB of an INITIAL CONTEXT SETUP REQUEST message, each requested E-RAB in the message is added to the counter.
Triggering Point
When the eNodeB receives the INITIAL CONTEXT SETUP REQUEST message from the MME.
Update Description
The counter is incremented by 1 for every E-RAB when the eNodeB receives the INITIAL CONTEXT SETUP REQUEST message from the MME in
which IE:E-RAB to Be Setup List includes E-RAB.
Unit
unit

26
(C373505473+C373505481)/(C373505472+C373505480)
Rate (%)
CC373505480 Number of Additional E-RAB Setup Attempt
Counter Description
On receipt by the eNodeB of an E-RAB SETUP REQUEST message, each requested E-RAB in the message is added to the counter.
Triggering Point
When the eNodeB receives the E-RAB SETUP REQUEST message from the MME.
Update Description
The counter is incremented by 1 for every E-RAB when the eNodeB receives the E-RAB SETUP REQUEST message from the MME.
Unit
unit

27
S1 Sig Setup Success Rate
(%)
The purpose of the S1 Setup procedure is to exchange application level data needed
for the eNB and MME to interoperate correctly on the S1 interface.
It indicates the ratio between the number of initial direct messages and the number of the responses that the
MME replies to these initial direct messages and also indicates the success ratio of signaling connection
establishment over the S1 interface.
S1 Sig Setup Success Rate (%)= S1 SigConnEstabSuccess /S1 SigConnEstabAtt*100

28
Rate (%) (C373495201/C37345200)
C373495201 Number of Received First Message by ENB after Init UE Message

Short Name
S1SIG.ConnEstabSucc
Counter Description
On receipt by The eNodeB of first message from MME which succeeds INITIAL UE MESSAGE message on an UE-associated logical S1-connection.
Triggering Point
When the eNodeB receives the first signal message from MME after sending the Initial UE Message.
Update Description
The counter is incremented by 1 when eNodeB receives the first signal message from the MME after sending the InitialUEMessage.
Unit
Times

29
(C373495201/C37345200)
Rate (%)
C373495200 Number of Send Init UE Message by ENB

Short Name
S1SIG.ConnEstabAtt
Counter Description
Transmission of an INITIAL UE MESSAGE by the eNodeB to the MME.
Triggering Point
When the eNodeB sends the InitialUEMessage to MME.
Update Description
The counter is incremented by 1 when eNodeB sends InitialUEMessage to the MME.
Unit
times

30
Initial E-rab Setup Success
Rate(RRC+Sig+E rab)
Ability of a UE to obtain and E-RAB from the system.

It is a combination of 3-Phase: RRC Phase, S1 Signalling, E-RAB Phase
Initial E-rab Setup Success Rate=
(RRC ConnEstabSucc /RCC ConnEstabAtt)*(S1 SigConnEstabSucc / S1 SigConnEstabAtt)*(Initial E-RAB
EstabSucc/ Initial E-RAB EstabAtt)*100

31
((C373200000+C373200004+C373200008+C373200012+C37320001
Initial E-rab Setup Success 6+C373200120)/(C373200084+C373200085+C373200086+C373200
Rate(RRC+Sig+E rab) 087+C373200088+C373200124))*
(C373495201/C37345200)*(C373505473/C373505472)

Short Name
Counter Description
counter.
Triggering Point
Update Description
The counter is incremented by 1 for every E-RAB when eNodeB sends the InitialContextSetupResponse message to MME and the E-RAB Setup
List IE includes the E-RAB.
Unit
Unit

32
((C373200000+C373200004+C373200008+C373200012+C37320001
Initial E-rab Setup Success 6+C373200120)/(C373200084+C373200085+C373200086+C373200
Rate(RRC+Sig+E rab) 087+C373200088+C373200124))*
(C373495201/C37345200)*(C373505473/C373505472)
C373505472 Number of Initial E-RAB Setup Attempt
Counter Description
On receipt by the eNodeB of an INITIAL CONTEXT SETUP REQUEST message, each requested E-RAB in the message is added to the counter.
Triggering Point
When the eNodeB receives the INITIAL CONTEXT SETUP REQUEST message from the MME.
Update Description
The counter is incremented by 1 for every E-RAB when the eNodeB receives the INITIAL CONTEXT SETUP REQUEST message from the MME in
which IE:E-RAB to Be Setup List includes E-RAB.
Unit
Unit

33
E-RAB Drop rate(%)
It shows how often an end-user abnormally looses an E-RAB during the time E-RAB is used.
E-RAB Drop rate(%)= Total No. of Abnormal Release/Total E-RAB Release*100

34
(C373210381+C373210391+C373210421+C373210441+C373210
E-RAB Drop rate(%) 451+C373210511+C373210521+C373505354)/(C373210461+C37
3240828+C373505473+C373505481+C373546257)
C373210381 Number of E-RAB Release by ENB Through E-RAB Release Procedure due to Overload Control
Short Name
ERAB.RelEnbNbr.CauseOverLoadControl
Counter Description
In the condition of opening "Load Control" switch,the eNodeB trigger the some appropriate traffic to release when detecting cell
overloading.When a E-RAB is released for above reason, it is added to the counter.
Triggering Point
When the eNodeB sends the E-RABReleaseIndication message to MME due to detection Overload,
Update Description
The counter is incremented by 1 for every E-RAB when eNodeB sends the E-RAB RELEASE INDICATION message or UE Context Release Request
to the MME due to LoadControl.
Unit
unit

35
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373210391 Number of E-RAB Release by ENB Through E-RAB Release Procedure due to Other Abnormal Reason
Short Name
ERAB.RelEnbNbr.Other
Counter Description
For other reason, the eNodeB sends the E-RABReleaseIndication message to MME. Each above E-RABs initiated by eNodeB is added to the
counter.
Triggering Point
When the eNodeB sends the E-RABReleaseIndication message to MME due to other reason
Update Description
The counter is incremented by 1 for every this E-RAB when the eNodeB sends the E-RABReleaseIndication message to MME due to other
reason.
Unit
Unit

36
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373210421 Number of E-RAB Release by ENB Through E-RAB Release Procedure due to Cell Congestion
Short Name
ERAB.RelEnbNbr.eNodebCellCongestion
Counter Description
In the condition of opening "Congestion Control" switch,the eNodeB trigger the some appropriate traffics to release when cell
congestion.When QCI1 E-RAB is released for above reason,it is added to the counter.
Triggering Point
When the eNodeB sends the E-RABReleaseIndication message to MME due to cell congestion,and the E-RAB To Be Released List includes the
QCI1 E-RAB.
Update Description
The counter is incremented by 1 for every this E-RAB when eNodeB sends the E-RABRELEASE INDICATION message or UE Context Release
Request to the MME due to Congestion Control,and the E-RAB released List includes the QCI1 E-RAB.
Unit
Unit

37
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373210441 Number of E-RAB Release by ENB Through E-RAB Release Procedure due to Radio Link Failure
Short Name
ERAB.RelEnbNbr.CauseRadioLinkFail
Counter Description
When a RLC PDU is transfered then exceeded the maximum number on the downlink, it is regarded as RLF.When eNodeB's timer expires that
monitoring the message from the the UE to eNodeB, it is regarded as RLF. For example, the RRCConnectionReestablishmentComplete message,
the RRCConnectionReconfigurationComplete message and so on.When a SR is transferred
Triggering Point
When the eNodeB sends the E-RABReleaseIndication message to MME due to radio link failures
Update Description
The counter is incremented by 1 for every E-RAB when the eNodeB sends the E-RABReleaseIndication message to MME due to radio link
failures.
Unit
Unit

38
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373210451 Number of E-RAB Release by ENB Through E-RAB Release Procedure due to Reestablish Fail
Short Name
ERAB.RelEnbNbr.ReestFail
Counter Description
Transmission of a UE CONTEXT RELEASE REQUEST message by the eNodeB to the MME when eNodeB occur RRC connection reestablishment
failures then sends the RRCConnectionReestablishmentReject message to the UE. Each above E-RAB released is added to the counter.
Triggering Point
When the eNodeB sends the UeContextReleaseRequest message to MME due to RRC connection reestablishment failures
Update Description
The counter is incremented by 1 for every E-RAB when the eNodeB sends the UeContextReleaseRequest message to MME due to RRC
connection reestablishment failures.
Unit
Unit

39
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373210511 Number of E-RAB Release by ENB Through E-RAB Release Procedure due to Shut Down or Reset Cell
Short Name
ERAB.RelEnbNbr.CellBlockOrReset
Counter Description
1 The eNodeB receives the Cell Block Command from the OMM for manual operation.2 The eNodeB occurs alarm about cell that trigger UE
release.Each above two conditions E-RAB released is added to the counter.
Triggering Point
The counter is incremented by 1 for every E-RAB when the eNodeB sends the UeContextReleaseRequest message to MME due to cell block or
reset.
Update Description
The counter is incremented by 1 for every E-RAB when the eNodeB sends the UeContextReleaseRequest message to MME due to cell block or
reset.
Unit
Unit

40
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373210521 Number of E-RAB Release by Reestablish Failure inter eNB

Short Name
ERAB.RelAttNbr.MmeErrorInd
Counter Description
An E-RAB is released when the eNodeB initiates UE release after receiving a UE context release message, which indicates that the cause is
"Failure in the Radio Interface Procedure", from the MME. This counter counts the number of times that an E-RAB is released in this case.
Triggering Point
This counter starts counting when the eNodeB initiates UE release after receiving a UE context release message, which indicates that the cause
is "Failure in the Radio Interface Procedure", from the MME.
Sampling Point 5
Update Description
This counter is incremented by one when the eNodeB initiates UE release after receiving a UE context release message, which indicates that
the cause is "Failure in the Radio Interface Procedure", from the MME.
Unit
Unit

41
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373505354 Number of E-RAB Release by ENB Through E-RAB Release Procedure due to S1 Link Error
Short Name
ERAB.RelEnbNbr.S1LinkError
Counter Description
The S1 link fault refer to the following.1 The eNodeB detects the fibber warning.2 The eNodeB gtpu layer detects the path fault from the
eNodeB to SGW.3 The eNodeB gtpu layer receives the ErrorIndication message from the SGW.
Triggering Point
When the eNodeB sends the UEContextReleaseRequest message to the MME due to S1 link fault.
Update Description
The counter is incremented by 1 for every E-RAB When the eNodeB sends the UE Context ReleaseRequest message to the MME due to S1 link
fault.
Unit
Unit

42
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373210461 Number of Successful E-RAB HO Incoming

Short Name
ERAB.HoInSucc
Counter Description
This counter counts the number of E-RABs successfully obtained through incoming handover at the destination side, including the cases of
inter-system handover, S1 handover, X2 handover, and intra-eNodeB handover.
Triggering Point
This counter starts counting at the following three time points: 1. When the destination eNodeB sends a HANDOVER NOTIFY message to the
MME during S1 handover. 2. When the destination eNodeB sends a UE CONTEXT RELEASE message to the source eNodeB during X2 handover.
3. When the eNodeB receives an RRCConnectionReconfigurationComplete message, which indicates handover
completion, from an UE during intrasite handover E-RAB X2 Handover ; E-RAB S1 Handover ; E-RAB Intra-eNodeB Handover
Sampling Point2
Update Description
This counter is incremented by one at the following three time points: 1. When the destination eNodeB sends a HANDOVER NOTIFY message to
the MME. 2. When the destination eNodeB sends a UE CONTEXT RELEASE message to the source eNodeB. 3. When the eNodeB receives an
RRCConnectionReconfigurationComplete message, which indicates handover completion, from an UE during intrasite handover.
Unit
Unit

43
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373240828 Online E-RAB Number

Short Name
ERAB.UsageNbrOnline
Counter Description
When the eNodeB has an E-RAB successfully established, the counter of E-RAB number is increased by 1. When the eNodeB has an E-RAB
successfully released by MME or eNodeB, the counter of E-RAB number is decreased by 1.
Triggering Point
When the eNodeB has an E-RAB successfully established or released.
Update Description
The counter is updated by the current E-RAB number at sampling points.
Unit
Unit

44
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)

Short Name
Counter Description
counter.
Triggering Point
Update Description
The counter is incremented by 1 for every E-RAB when eNodeB sends the InitialContextSetupResponse message to MME and the E-RAB Setup
List IE includes the E-RAB.
Unit
Unit

45
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373505481 Number of Additional E-RAB Successful Setup

Short Name
ERAB.EstabAddSuccNbr
Counter Description
On transmission by the eNodeB of an E-RAB SETUP RESPONSE message, in which each E-RAB successfully established is added to the counter
Triggering Point
When the eNodeB replies the E-RABSetupResponse to the MME, and the E-RAB Setup List IE includes E-RAB.
Update Description
The counter is incremented by 1 for every E-RAB when eNodeB sends E-RABSetupResponse to MME and the E-RAB Setup List IE includes the E-
RAB.
Unit
Unit

46
(C373210381+C373210391+C373210421+C373210441+C373210
3240828+C373505473+C373505481+C373546257)
C373546257 Number of Successful E-RAB Incoming in RRC Re-Establishment
Counter Description
Each E-RAB for successful incoming re-establishment from other cell to local cell is added to the counter.
Triggering Point
When the local cell receives the RRC CONNECTION REESTABLISHMENT COMPLETE from the UE in other cell
Update Description
The counter is incremented by 1 for every this E-RAB when the local cell receives the RRC CONNECTION REESTABLISHMENT COMPLETE from
the UE in other cell.
Unit
Unit

47
DL Packet Loss Rate (%)
The DL Packet Loss measurement is done against measurement of Packets dropped due
to congestion, traffic management etc.
The measurement refers to discard for DRBs. One packet corresponds to one PDCP SDU.
DL Packet Loss Rate= No. of DL PDCP SDU Loss/ (No. of DL PDCP SDU- No. of Discarded DL PDCP SDU)

48
DL Packet Loss Rate (%) C373353957*100/(C373353960-C373353958)
C373353957 DL PDCP SDU Loss Number

Short Name
DRB.PdcpSduAirLossDl
Counter Description
the eNodeB discards the PDCP SDU when timeout of "timer discard" detecting the SDU or not DL buffer for the SDU. If at least a part of it has
been transmitted over the air but not positively acknowledged, the counter is counted.
Triggering Point
This counter counts when the ERAB SDU RLC message in the downlink buffer of the eNodeB (PDCP, RLC, DMAC) is discarded due to that the
number of times of retransmission reaches the maximum value. Part of or all of the SDU is transmitted at the air interface but is not
acknowledged. This counter does not count for the RN part.
Update Description
The counter is increased by 1 when the eNodeB discards the PDCP SDU in DL, for which at least a part has been transmitted over the air but
not positively acknowledged.
Unit
Unit

49
C373353960 DL PDCP SDU Number

Short Name
DRB.PdcpSduDl
Counter Description
When the eNodeB PDCP layer receives the PDCP SDU from the SGW or the other eNodeB.the counter is used to count.
Triggering Point
When the eNodeB PDCP layer receives the PDCP SDU.
Update Description
The counter is increased by 1 when the eNodeB PDCP layer receives the PDCP SDU from the SGW or the other eNodeB.
Unit
Unit

50
C373353958 DL PDCP SDU Discard Number

Short Name
DRB.PdcpSduAirDropDl
Counter Description
the eNodeB discards the PDCP SDU when timeout of "timer discard" detecting the SDU or not DL buffer for the SDU. If no part of it has been
transmitted over the air, the counter is counted.
Triggering Point
When the eNodeB discards the PDCP SDU in DL, for which no part has been transmitted over the air
Update Description
The counter is increased by 1 when the eNodeB discards the PDCP SDU in DL, for which no part has been transmitted over the air.
Unit
Unit

51
UL Packet Loss Rate (%)
The UL Packet Loss measurement is done to measure Packets Lost in UL

The measurement refers to discard for DRBs. One packet corresponds to one PDCP SDU.
UL Packet Loss Rate= No. of UL PDCP SDU Loss/ No. of UL PDCP SDU*100

52
UL Packet Loss Rate (%) C373353956*100/C373353959
C373353956 UL PDCP SDU Loss Number

Short Name
DRB.PdcpSduLossUl
Counter Description
When the eNodeB PDCP layer receives the PDCP PDU from the RLC layer, compare the received PDU sequence number with the expected
sequence number. If the received is larger than the expected, it is considered that there is packet loss in UL. The number of the lost SDU is the
difference between the received sequence number and the expected sequence number.
Triggering Point
When the eNodeB detects the PDCP SDU sequece number discontinuity in UL.
Update Description
The counter is increased by the number of missing UL PDCP sequence numbers when the eNodeB detects the UL PDCP SDU sequece number
discontinuity.
Unit
Unit

53
UL Packet Loss Rate (%) C373353956*100/C373353959
C373353959 UL PDCP SDU Number

Short Name
DRB.PdcpSduUl
Counter Description
After the PDCP layer receives the PDCP PDU from RLC layer, the PDU is disposed successfully and than becomes PDCP SDU. The counter is used
to count the number of the SDU.
Triggering Point
When the eNodeB PDCP layer sends the PDCP packet in the uplink
Update Description
The counter is increased by 1 when the eNodeB PDCP layer sends the PDCP packet in the uplink.
Unit
Unit

54
Intra Frequency Outgoing
Handover Execution Success
Rate(%)
The Probability of successful Co-channel outgoing handover inside an eNB
Intra Frequency Outgoing Handover Execution Success Rate(%)

=No. of Successful outgoing intra eNB intra freq Handover Execution/ No. of outgoing
intra eNB intra freq Handover Preparation Attempt*100

55
Intra Frequency Outgoing Handover
(C373250980+C373261280+C373271580)/(C373250900+C3732
Execution Success Rate(%) 50901+C373250902+C373250903+C373250988+C373261292+C
373271591)
C373250980 Number of Successful Outgoing intra-eNB intra-freq Handover Execution
Short Name
HO.IntraEnbIntraFreqOutExeSucc
Counter Description
During a UE handover procedure, when the source cell receives a UEContextRelease message, this counter counts the number of times that load-
balancing-based outgoing handover preparation from LTE FDD to LTE TDD or from LTE TDD to LTE FDD is successful.
Triggering Point
During a UE handover procedure, when the source cell receives a UEContextRelease message, this counter is updated.
Update Description
During a UE handover procedure, when the source cell receives a UEContextRelease message, and a load-balancing-based inter-standard intra-system
handover occurs, this counter is incremented by one.
Unit
times

56
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373261280 Number of Successful Outgoing inter-eNB(via X2) intra-freq Handover Execution
Short Name
HO.InterEnbX2IntraFreqOutExeSucc
Counter Description
When eNodeB receives a X2AP message UE CONTEXT RELEASE sent from the target eNodeB to the source eNodeB, it indicates a successful handover
over the X2. Each UE CONTEXT RELEASE message received is added to the counter.
Triggering Point
When the source eNodeB receives the UE Context Release message from the target eNodeB.
6
Update Description
The counter is incremented by 1 when the source eNodeB receives the UE Context Release message from the target eNodeB.
Unit
times

57
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373271580 Number of Successful Outgoing inter-eNB(via S1) intra-freq Handover Execution
Short Name
HO.InterEnbS1IntraFreqOutExeSucc
Counter Description
When eNodeB receives a S1AP message UE CONTEXT RELEASE COMMAND sent from the MME to the source eNodeB, it indicates a successful handover
over the S1. Each UE CONTEXT RELEASE COMMAND message received is added to the counter.
Triggering Point
When the source eNodeB receives the UE Context Release message from the MME.
3
Update Description
The counter is incremented by 1 when the source eNodeB receives the UE Context Release message from the MME.
Unit
times

58
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373250900 Number of Successful Outgoing intra-eNB intra-freq Handover Preparation
Short Name
HO.IntraEnbIntraFreqOutPrepSucc
Counter Description
When the source eNodeB sends the MME a HandoverRequired message, if the Handover Type IE indicates that the handover is an inter-RAT
handover from EUTRAN to UTRAN and is a blind handover, this counter counts the number of handover requests from EUTRAN to UTRAN.
Triggering Point
When the source eNodeB sends the MME a HandoverRequired message, this counter is updated.
Update Description
handover from EUTRAN to UTRAN and is a blind handover, this counter is incremented by one.
Unit
times

59
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373250901 Number of Re-estabilshment to Source eNodeB When Outgoing intra-eNB intra-freq
Handover Preparation
Short Name
HO.IntraEnbIntraFreqOutPrepFail.UeReSrcCell
Counter Description
When the source eNodeB receive a HandoverCommand message from the MME, and this handover is a blind handover, this counter counts the
number of outgoing handovers from EUTRAN to UTRAN.
Triggering Point
When the source eNodeB receives a HandoverCommand message from the MME, this counter is updated.
Sampling Point 6
Update Description
When the source eNodeB receives a HandoverCommand message from the MME, and this handover is a blind handover, this counter is incremented
by one.
Unit
times

60
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373250902 Number of Outgoing intra-eNB intra-freq Handover Preparation Failure due to Dest Preparation Failure
Short Name
HO.IntraEnbIntraFreqOutPrepFail.DstFail
Counter Description
When the source eNodeB receive a UEContextRelease message from the MME, indicating the handover is successfully executed, and this handover is
a blind handover, this counter counts the number of outgoing handovers from EUTRAN to UTRAN.
Triggering Point
When the source eNodeB receives a UEContextRelease message from the MME, indicating the handover is successfully executed, this counter is
updated.
Update Description
When the source eNodeB receives a UEContextRelease message from the MME, indicating the handover is successfully executed, and this handover
is a blind handover, this counter is incremented by one.
Unit
times

61
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373250903 Number of Outgoing intra-eNB intra-freq Handover Preparation Failure due to Other Reason
Short Name
HO.IntraEnbIntraFreqOutPrepFail.OtherReason
Counter Description
handover from EUTRAN to GSM and is a blind handover, this counter counts the number of handover requests from EUTRAN to GSM.
Triggering Point
When the source eNodeB sends the MME a HandoverRequired message, this counter is updated.
Update Description
handover from EUTRAN to GSM and is a blind handover, this counter is incremented by one.
Unit
times

62
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373250988 Number of Outgoing intra-eNB intra-freq Handover Preparation Failure due to User Inactivity
Short Name
HO.IntraEnbIntraFreqOutPrepFail.UserInactive
Counter Description
This counter counts the number of intra-eNodeB, X2, S1, and inter-RAT handovers.
Triggering Point
When the source eNodeB sends the MME a Handover Required message or sends the target eNodeB a Handover Request message, and this
handover is triggered by cell shutdown or cell reset, this counter is updated.
Update Description
When the source eNodeB sends the MME a Handover Required message or sends the target eNodeB a Handover Request message, and this
handover is triggered by cell shutdown or cell reset, this counter is incremented by one.
Unit
times

63
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373261292 Number of Outgoing inter-eNB(via X2) intra-freq Handover Preparation Request

Short Name
HO.InterEnbX2IntraFreqOutPrepReq
Counter Description
After transmission of a X2AP message HANDOVER REQUEST ACKNOWLEDGE from source eNB to the target eNodeB, it indicates the attempt of an
outgoing inter-eNB handover preparation.
Triggering Point
When the source eNodeB sends the Handover Request message to the target eNodeB.
Update Description
The counter is incremented by 1 when the source eNodeB sends the Handover Request message to the target eNodeB
Unit
times

64
(C373250980+C373261280+C373271580)/(C373250900+C3732
373271591)
C373271591 Number of Outgoing inter-eNB(via S1) intra-freq Handover Preparation Request

Short Name
HO.InterEnbS1IntraFreqOutPrepReq
Counter Description
Transmission of the S1AP message HANDOVER REQUIRED from the source eNodeB to the MME, indicating the attempt of an outgoing inter-eNB
handover preparation.
Triggering Point
When the source eNodeB sends the HandoverRequired message to the MME.
Update Description
The counter is incremented by 1 when the source eNodeB sends the Handover Required message to the MME.
Unit
times

65
X2 Intra Frequency Outgoing
Handover Success Rate(%)
The Probability of successful Co-channel outgoing handover through the X2 interface between
eNBs.
X2 Intra Frequency Outgoing Handover Success Rate(%)= No. of Successful outgoing inter eNB(via X2) intra freq
Handover Execution/ No. of outgoing inter eNB(via X2) intra freq Handover Preparation Request*100

66
X2 Intra Frequency Outgoing Handover
Success Rate(%)
C373261280/C373261292
C373261280 Number of Successful Outgoing inter-eNB(via X2) intra-freq Handover Execution

Short Name
HO.InterEnbX2IntraFreqOutExeSucc
Counter Description
When eNodeB receives a X2AP message UE CONTEXT RELEASE sent from the target eNodeB to the source eNodeB, it indicates a successful handover over the X2. Each UE CONTEXT
RELEASE message received is added to the counter.
Triggering Point
When the source eNodeB receives the UE Context Release message from the target eNodeB.
6
Update Description
The counter is incremented by 1 when the source eNodeB receives the UE Context Release message from the target eNodeB.
C373261292 Number of Outgoing inter-eNB(via X2) intra-freq Handover Preparation Request

Short Name
HO.InterEnbX2IntraFreqOutPrepReq
Counter Description
After transmission of a X2AP message HANDOVER REQUEST ACKNOWLEDGE from source eNB to the target eNodeB, it indicates the attempt of an outgoing inter-
eNB handover preparation.
Triggering Point
When the source eNodeB sends the Handover Request message to the target eNodeB.
Update Description
The counter is incremented by 1 when the source eNodeB sends the Handover Request message to the target eNodeB
Unit
times

67
S1 Intra Frequency Outgoing
Handover Success Rate(%)
The Probability of successful Co-channel outgoing handover through the S1 interface between
eNBs.
S1 Intra Frequency Outgoing Handover Success Rate(%)= No. of Successful outgoing inter eNB(via S1) intra freq
Handover Execution/ No. of outgoing inter eNB(via S1) intra freq Handover Preparation Request*100

68
S1 Intra Frequency Outgoing Handover
Success Rate(%)
C373271580/C373271591
C373271580 Number of Successful Outgoing inter-eNB(via S1) intra-freq Handover Execution

Short Name
HO.InterEnbS1IntraFreqOutExeSucc
Counter Description
When eNodeB receives a S1AP message UE CONTEXT RELEASE COMMAND sent from the MME to the source eNodeB, it indicates a successful handover over the S1. Each UE CONTEXT
RELEASE COMMAND message received is added to the counter.
Triggering Point
When the source eNodeB receives the UE Context Release message from the MME.
3
Update Description
The counter is incremented by 1 when the source eNodeB receives the UE Context Release message from the MME.
C373271591 Number of Outgoing inter-eNB(via S1) intra-freq Handover Preparation Request

Short Name
HO.InterEnbS1IntraFreqOutPrepReq
Counter Description
Transmission of the S1AP message HANDOVER REQUIRED from the source eNodeB to the MME, indicating the attempt of an outgoing inter-eNB handover preparation.
Triggering Point
When the source eNodeB sends the HandoverRequired message to the MME.
Update Description
The counter is incremented by 1 when the source eNodeB sends the Handover Required message to the MME.
Unit
times

69
Average Cell DL PDCP (C373343806*1000+C373343807)/C37

Throughput(Mbps) 3343885
C373343806 DL Aggregated Volume High through Uu

Short Name
Drb.IpThrouDlVoH
Counter Description
The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the downlink. The total volume = volume High + Volume
Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air interface
successfully, the counter is collected.
Triggering Point
When all packets of a PDCP SDU are sent by the eNodeB over air interface on the downlink
Update Description
When all packets of a PDCP SDU are sent by the eNodeB over air interface on the downlink, the counter is incremented by the bit-size of the
PDCP SDU.
Unit
Mbit

70

C373343807 DL Aggregated Volume Low through Uu

Short Name
Drb.IpThrouDlVoL
Counter Description
The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the downlink. The total volume = volume High +
Volume Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air
interface successfully, the counter is collected.
Triggering Point
When all packets of a PDCP SDU are sent by the eNodeB over air interface on the downlink
Update Description
When all packets of a PDCP SDU are sent by the eNodeB over air interface on the downlink, The counter is incremented by the bit-size of the
PDCP SDU.
Unit
Kbit

71

C373343885 DL Traffic Transmission Time
Counter Description
This counter counts the duration from the time data appears in the downlink service buffer to the time the service buffer becomes empty in a
measurement period of all eNodeBs.The overlapping time periods of multiple services are counted once.
Triggering Point
This counter counts the transmission period of downlink data at the PDCP layer, including the QCI-related period and the total period. The
overlapping time periods of multiple UEs or QCIs are counted once.
Update Description
This counter counts the duration collected in a measurement period when PDCP SDUs of downlink services in a cell are used.
Unit
ms

72
Average Cell UL PDCP (C373343804*1000+C373343805)/C373

C373343804 UL Aggregated Volume High

Short Name
Drb.IpThrouUlVoH
Counter Description
The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the uplink.The total volume = volume High + Volume Low.
Triggering Point
When a PDCP SDU are received by PDCP layer from RLC layer on the uplink
Update Description
When a PDCP SDU are received by PDCP layer from RLC layer on the uplink,the counter is incremented by the bit-size of the PDCP SDU.
Unit
Mbit

73

C373343805 UL Aggregated Volume Low

Short Name
Drb.IpThrouUlVoL
Counter Description
The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the uplink. The total volume = volume High + Volume
Low.
Triggering Point
When a PDCP SDU are received by PDCP layer from RLC layer on the uplink
Update Description
When a PDCP SDU are received by PDCP layer from RLC layer on the uplink,the counter is incremented by the bit-size of the PDCP SDU.
Unit
Kbit

74

C373343875 UL Traffic Transmission Time
Counter Description
This counter counts the duration from the time data appears in the uplink service buffer to the time the service buffer becomes empty in a
measurement period of all eNodeBs. The overlapping time periods of multiple services are counted once.
Triggering Point
This counter counts the transmission period of uplink data at the PDCP layer, including QCI-related period and the total period. The overlapping
time periods of multiple UEs or QCIs are counted once.
Update Description
This counter counts the duration collected in a measurement period when the PDCP layer of uplink services in a cell receives a message
indicating that a PDCP SDU is used.
Unit
ms

75
(C373576607+C373576600)/(C3732206
CSFB Setup Success
44+C373220647+C373220650+C373220
Rate(4G side)
653)
C373576607 Number of Redirection Requests from LTE to UTRAN(CSFB)
Counter Description
This counter counts the number of redirection requests towards the UTRAN system from the LTE system due to CSFB.
Triggering Point
This counter is incremented when the eNodeB sends an RRCConnectionRelease message (including the Redirection IE) to a UE due to CSFB. This
counter counts the number of redirection requests to the UTRAN system from the LTE system due to CSFB.
Update Description
This counter is incremented when the eNodeB sends an RRCConnectionRelease message (including the Redirection IE) to a UE due to CSFB. This
counter counts the number of redirection requests to the UTRAN system from the LTE system due to CSFB. This counter is incremented by one
before a redirection request towards the UTRANsystem is triggered due to CSFB.
Unit
times

76
(C373576607+C373576600)/(C3732206
CSFB Setup Success
44+C373220647+C373220650+C373220
Rate(4G side)
653)
C373576600 Number of Redirection Requests from LTE to GSM(CSFB)
Counter Description
This counter counts the number of redirection requests towards the GSM system from the LTE system that are triggered due to CSFB.
Triggering Point
This counter is incremented when the eNodeB sends an RRCConnectionReleasemessage (including the Redirection IE) to a UE due to CSFB. This
counter counts the number of redirection requests towards the GSM system from the LTE system due to CSFB.
Update Description
This counter is incremented when the eNodeB sends an RRCConnectionReleasemessage (including the Redirection IE) to a UE due to CSFB. This
counter counts the number of redirection requests towards the GSM system from the LTE system due to CSFB. This counter is incremented by
one before a redirection request towards the GSM system is triggered due to CSFB.
Unit
times

77
(C373576607+C373576600)/(C3732206
CSFB Setup Success
44+C373220647+C373220650+C373220
Rate(4G side)
653)
C373220644 Number of Attempted Mt-Access Initial Context Setup with CSFB
Counter Description
After the LTE user sends the service request message to MME, the MME find the eNodeB not supportting CS service.Then the MME requires
eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN. The counter calculates the numberof this UE Context
setup attempts.
Triggering Point
When the eNodeB receives the InitialContextSetupRequest with CSFB indication message from the MME and the RRC establishmentCause is mt-
access.
Update Description
The counter is incremented by 1 when the eNodeB receives the InitialContextSetupRequest with CSFB indication message from the MME for
mt-Access.
Unit
times

78
(C373576607+C373576600)/(C3732206
CSFB Setup Success
44+C373220647+C373220650+C373220
Rate(4G side)
653)
C373220647 Number of Attempted Mo-Signalling or Mo-Data Initial Context Setup with CSFB
Counter Description
After the LTE user sends the service request message to MME for mo-signaling or mo-data, the MME requires eNodeB to establish the UE
Context which indicates CS service fallback to GERAN/UTRAN. The counter calculates the number of this UE Context request.
Triggering Point
When the eNodeB receives the InitialContextSetupRequest with CSFB indication message from the MME and the RRC establishmentCause is
mo-signalling.
Update Description
The counter is incremented by 1 when the eNodeB receives theInitialContextSetupRequest with CSFB indication message from the MME for
mo-signalling.
Unit
times

79
(C373576607+C373576600)/(C3732206
CSFB Setup Success
44+C373220647+C373220650+C373220
Rate(4G side)
653)
C373220650 Number of Attempted Context Modification with CSFB
Counter Description
After the LTE user sends the service request message to MME, the MME requires eNodeB to modify the UE Context which indicates CS service
fallback to GERAN/UTRAN. The counter calculates the number of UE Context modification request for CSFB.
Triggering Point
When the eNodeB receives the UEContextModificationRequest with CSFB indication message from the MME.
Update Description
The counter is incremented by 1 when the eNodeB receives the UEContextModificationRequest with CSFB indication message from the MME.
Unit
times

80
(C373576607+C373576600)/(C3732206
CSFB Setup Success
44+C373220647+C373220650+C373220
Rate(4G side)
653)
C373220653 Number of Attempted Other Initial Context Setup with CSFB
Counter Description
After the LTE user sends the service request message to MME for neither mt nor mo type,the MME find the eNodeB not supportting CS
service.Then the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN. The counter
calculates the number of this UE Context setup attempts.
Triggering Point
When the eNodeB receives the InitialContextSetupRequest with CSFB indication message from the MME and the RRC establishmentCause
neither mt nor mo type.
Update Description
The counter is incremented by 1 when the eNodeB receives the InitialContextSetupRequest with CSFB indication message from the MME for
neither mt nor mo type.
Unit
times

81
C373454837/(C373454837+C37345483
Rank Indicator=1
8)
C373454837 Number of DL TBs with RI=1
Counter Description
This counter counts the number of downlink RANK1 TBs transmitted by the cell, including retransmitted TBs. When the eNodeB schedules
downlink TBs, this counter is updated.
Triggering Point
When the eNodeB schedules downlink TBs, this counter is updated.
Update Description
downlink TBs, this counter is incremented by the number of corresponding TBs.
Unit
unit

82
C373454837/(C373454837+C37345483
Rank Indicator=1
8)
C373454838 Number of DL TBs with RI=2
Counter Description
downlink TBs, this counter is updated.
Triggering Point
When the eNodeB schedules downlink TBs, this counter is updated.
Update Description
downlink TBs, this counter is incremented by the number of corresponding TBs.
Unit
unit

83
PDCCH Aggregation C373424643/(C373424643+C373424644+

Level-1 C373424645+C373424646)
C373424643 Number of CCE Aggregation Level 1
Counter Description
The counter provides the number of CCE aggregation level 1 for PDCCH.
Triggering Point
When the eNodeB DL scheduler allocates the CCE aggregation level 1 for PDCCH
Update Description
The counter is incremented by 1 when the eNodeB DL scheduler allocates the CCE aggregation level 1 for PDCCH.
Unit
times

84

Level-1 C373424645+C373424646)
Counter Description
Triggering Point
When the eNodeB DL scheduler allocates the CCE aggregation level 2 for PDCCH.
Update Description
Unit
times

85

Level-1 C373424645+C373424646)
Counter Description
Triggering Point
Update Description
Unit
times

86

Level-1 C373424645+C373424646)
Counter Description
Triggering Point
Update Description
Unit
times

87

Level-2 C373424645+C373424646)
Counter Description
Triggering Point
Update Description
Unit
times

88

Level-4 C373424645+C373424646)
Counter Description
Triggering Point
Update Description
Unit
times

89

Level-8 C373424645+C373424646)
Counter Description
Triggering Point
Update Description
Unit
times

90
User DL (C374107514*1000*1000+C374107515*1
Throughput(Mbps) 000)*1000/(C374107516*1024*1024)
C374107514 DL Aggregated Volume High through Uu For IP Throughput
Counter Description
This counter counts the total downlink PDCP SDU dead load, not including packets lost at the Uu interface, tail packets, and data completed
through one data scheduling. The counter value = the total data / 1000000.
Triggering Point
through one data scheduling. The counter value = the total data / 1000000.
Update Description
through one data scheduling. The counter value = the total data / 1000000. The counter accumulates the data volume.
Unit
Mbit

91
User DL (C374107514*1000*1000+C374107515*1
C374107515 DL Aggregated Volume Low through Uu For IP Throughput
Counter Description
through one data scheduling. The counter value = the total data % 1000000.
Triggering Point
through one data scheduling. The counter value = the total data % 1000000.
Update Description
through one data scheduling. The counter value = the total data % 1000000. The counter accumulates the data volume.
Unit
Kbit

92
User DL (C374107514*1000*1000+C374107515*1
C374107516 DL Aggregated Time For IP Throughput
Counter Description
This counter counts the downlink service time during which the eNodeB buffer becomes empty from being not empty, not including the data
transmission time for tail packets and data completed through one data scheduling.
Triggering Point
Update Description
transmission time for tail packets and data completed through one data scheduling. The counter accumulates the transmission time.
Unit
ms

93
User UL (C374107517*1000*1000+C374107518*1
C374107517 UL Aggregated Volume High through Uu For IP Throughput
Counter Description
This counter counts the total uplink PDCP SDU dead load, not including packets lost at the Uu interface, tail packets, and data completed through one
data scheduling. The counter value = the total data / 1000000.
Triggering Point
data scheduling. The counter value = the total data / 1000000.
Update Description
data scheduling. The countervalue = the total data / 1000000. The counter accumulates the data volume.
Unit
Mbit

94
User UL (C374107517*1000*1000+C374107518*1
C374107518 UL Aggregated Volume Low through Uu For IP Throughput
Counter Description
data scheduling. The counter value = the total data % 1000000.
Triggering Point
data scheduling. The counter value = the total data % 1000000.
Update Description
data scheduling. The countervalue = the total data % 1000000. The counter accumulates the data volume.
Unit
Kbit

95
User UL (C374107517*1000*1000+C374107518*1
C374107519 UL Aggregated Time For IP Throughput
Counter Description
This counter counts the uplink service time during which the eNodeB buffer becomes empty from being not empty, not including the data
Triggering Point
Update Description
transmission time for tail packets and data completed through one data scheduling. The counter accumulates the transmission time.
Unit
ms

96
Thank you

Formulas 160516

Uploaded by

Copyright:

Available Formats

Formulas 160516

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

Formulas 160516

Uploaded by

Copyright:

Available Formats

IDEA-ZTE

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

E-RAB Establish Success

S1 Sig Setup Success

Initial E-rab Setup Success

Retainability DL Packet Loss Rate (%)

UL Packet Loss Rate (%)

CSFB Setup Success Rate(4G

Average Cell UL PDCP

PDCCH Aggregation Level-

© ZTE Corporation. All rights reserved

The RRC Setup procedure is triggered by different reasons as identified by the

RRC_Setup Successful Rate= RRC Connection Success/RRC Connection Attempt*100

© ZTE Corporation. All rights reserved

C373200000 Number of Successful Mt-Access RRC Establishment

© ZTE Corporation. All rights reserved

C373200004 Number of Successful Mo-Signalling RRC Establishment

© ZTE Corporation. All rights reserved

C373200008 Number of Successful Mo-Data RRC Establishment

© ZTE Corporation. All rights reserved

C373200012 Number of Successful HighPriorityAccess RRC Establishment

© ZTE Corporation. All rights reserved

C373200016 Number of Successful Emergency RRC Establishment

© ZTE Corporation. All rights reserved

C373200120 Number of Successful delayTolerantAccess RRC Establishment

© ZTE Corporation. All rights reserved

C373200084 Number of Mt-Access RRC Establishment Request

© ZTE Corporation. All rights reserved

C373200085 Number of Mo-Signalling RRC Establishment Request

© ZTE Corporation. All rights reserved

C373200086 Number of Mo-Data RRC Establishment Request

© ZTE Corporation. All rights reserved

C373200087 Number of HighPriorityAccess RRC Establishment Request

© ZTE Corporation. All rights reserved

C373200088 Number of Emergency RRC Establishment Request

© ZTE Corporation. All rights reserved

C373200124 Number of delayTolerantAccess RRC Establishment Request

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

C373505473 Number of Initial E-RAB Successful Setup

© ZTE Corporation. All rights reserved

C373505481 Number of Additional E-RAB Successful Setup

© ZTE Corporation. All rights reserved

C373505472 Number of Initial E-RAB Setup Attempt

© ZTE Corporation. All rights reserved

CC373505480 Number of Additional E-RAB Setup Attempt

© ZTE Corporation. All rights reserved

S1 Sig Setup Success Rate (%)= S1 SigConnEstabSuccess /S1 SigConnEstabAtt*100

© ZTE Corporation. All rights reserved

C373495201 Number of Received First Message by ENB after Init UE Message

© ZTE Corporation. All rights reserved

C373495200 Number of Send Init UE Message by ENB

© ZTE Corporation. All rights reserved

Ability of a UE to obtain and E-RAB from the system.

© ZTE Corporation. All rights reserved

C373505473 Number of Initial E-RAB Successful Setup

© ZTE Corporation. All rights reserved