Nell’iperspazio con Rocket: il Framework Web di Rust!
Lte kpis, counters & amp; timers
1. Telecom Earth Your One Stop for Telecom Updates, Forum, Discussion and Job Portal
LTE 0
LTE KPIs, Counters & Timers
BY TELECOMEARTH · PUBLISHED DECEMBER 7, 2016 · UPDATED JANUARY 18, 2017
0
SHARES
RAN KPIs & Counters Introduction
RAN KPIs
1. Accessibility
2. Retainability
3. Mobility
4. Integrity
Accessibility KPIs are used to measure
how successfully user is able to access
the network.
Divided in 3 segments, RRC setup, S1
setup & ERAB setup
RRC Connection Setup Success Rate:-
Description
Probability success rate for RRC Connections establishment.
Successful attempts compared with total number of attempts.
KPI Formula
[ConnEstabSucc/ ConnEstabAtt] * 100
ConnEstabAtt: RRC connection establishments attempt count
ConnEstabSucc: RRC connection establishments success count
Unit: Percentage(%)
Measuring point
For statistics on RRC connection establishment
Attempt statistic is counted when the RRC Connection Request
message is received.
Success statistic is counted when the RRC Connection Setup
Complete message is received.
S1 Connection Setup Success Rate
Description
Probability success rate for Logical S1-Connections establishment.
Successful attempts compared with total number of attempts.
KPI Formula
[S1ConnEstabSucc/S1ConnEstabAtt] * 100
Share Tweet +
Book Tata Sky Connection
Choose From Over 600 Channels
And Services With Superior Picture
& Sound Quality
MOREFOLLOW:
RECENT POSTS
One More Merger: BSNL, MTNL
merger plan back on discussion table
Stop buying that new 4G phone now
!!! 5G Smartphone is on the way
Reliance Jio’s massive small cell
deployment to enable smooth change
to 5G: President Mathew Oommen
Reliance Jio impact: Indian telecom
market to have ve players, says
Telecom Secretary J S Deepak
Freedom 251 phone:Director of
Ringing Bells Mohit Goel detained for
‘fraud’
RECENT COMMENTS
One More Merger: BSNL, MTNL
merger plan back on discussion table |
Telecom Earth on Stop buying that new
4G phone now !!! 5G Smartphone is on
the way
telecomearth on Reliance Jio Impact:
Bharti Airtel to buy Telenor India
Tinku Sharma on Vodafone has
signed a massive deal of 4G
deployment and expansion to Nokia,
Ready For New Jobs
Gyanendra kumar on The telecom
sector is expected to create two million
jobs this year,Thanks to New Entry
Kuldeep verma on Reliance Jio
offers free SIM, instant activation after
Amitabh Bachchan tweets Vodafone
SMS down
ARCHIVES
March 2017
February 2017
January 2017
December 2016
November 2016
CATEGORIES
2G
3G
NEXT STORY
WCDMA Channel
PREVIOUS STORY
LTE Channel
To search type and hit enter
Home
Technology
Telecom Tools
Forums
2. S1ConnEstabAtt: S1-connection establishment attempt count
S1ConnEstabSucc: S1-connection establishment success count
Unit: Percentage(%)
Measuring point
For statistics on Logical S1-connection establishment
when the Initial UE message is transmitted, it is counted as Attempt;
when the Initial Context Setup Request message is received, it is
counted as Success.
Initial E-RAB Setup Success Rate
Description
Probability success rate for initial E-RABs establishment.
Successful attempts compared with total number of attempts.
KPI Formula
[EstablnitSuccNbr/ EstablnitAttNbr] * 100
EstablnitAttNbr: E-RAB setup attempt count
EstablnitSuccNbr: E-RAB setup success count
Unit: Percentage(%)
Measuring point
For E-RAB setup statistics
When the Initial Context Setup Request message is received upon
initial call setup, it is counted as Attempt.
When the Initial Context Setup Response message is transmitted, it is
counted as Success.
Additional E-RAB Setup Success Rate
Description
Probability success rate for additional E-RABs establishment.
Successful attempts compared with total number of attempts.
KPI Formula
[EstabAddSuccNbr/ EstabAddAttNbr] * 100
EstabAddAttNbr: Additional E-RAB setup attempt count
EstabAddSuccNbr: Additional E-RAB setup success count
Unit: Percentage(%)
Measuring point
For Additional E-RAB setup statistics
When eNBreceives the E-RAB Setup Request message from MME, it is
counted as Attempt.
After eNBsends E-RAB Setup Response message to MME, it is
counted as Success.
Session Setup Success Rate
Description
Probability success rate of overall initial attach procedure.
Product of RRC connection setup success rate, S1 signaling connection
setup success rate and initial E-RAB establishment success rate.
KPI Formula
(ConnEstabSucc/ ConnEstabAtt) * (S1ConnEstabSucc / S1ConnEstabAtt) *
(EstablnitSuccNbr/ EstablnitAttNbr) * 100
LTE
News and telecom Update
Technology
Telecom Tools
FORUMS
Lte Discussion
SIGN UP
Pureit Water Purifier -
Pureit Official Website
Complete Range of Pureit
Product Available. Get Free
Home Demo Now!
pureitwater.com
Sign Up to Telecom Earth for Telecom
Updates.
First Name
Last Name
E-Mail
Submit
3. ConnEstabAtt: RRC connection establishments attempt count
ConnEstabSucc: RRC connection establishments success count
S1ConnEstabAtt: S1-connection establishment attempt count
S1ConnEstabSucc: S1-connection establishment success count
EstablnitAttNbr: E-RAB setup attempt count
EstablnitSuccNbr: E-RAB setup success count
Unit: Percentage(%)
Call Drop Rate
Description
Probability abnormally released(call drop) for established
connections.
The call drop statistics are on the calls that are connected
successfully but abnormally dropped due to eNB failure or by the
MME.
KPI Formula
[Call Drop(All type id sum) / (EstabInitSuccNbr+ InterX2InSucc +
InterS1InSucc)] * 100
Call Drop(All type id) : Call Drop count about all type
EstablnitSuccNbr: E-RAB setup success count
InterX2InSucc : X2 HO success count in target eNB
InterS1InSucc : S1 HO success count in target eNB
Unit: Percentage(%)
Measuring point
For Call Drop statistics,
Calls released by the eNB due to user inactivity, normally released by
the MME, and released by the UE duplication are not considered
abnormally terminated.
For established connection statistics,
Successful call connection indicates that the default bearer setup is
successful or incoming handover is successful for a call.
4. ERAB Drop Rate
Description
Probability abnormally released E-RAB for established connections.
This formula expresses E-RAB drop rate with respect to successful E-
RAB attempts, as R2 expresses E-RAB drop rate with respect to total E-
RAB session time.
KPI Formula
ErabDropRate= RelActive/ (EstabInitSuccNbr+ EstabAddSuccNbr) * 100
RelActive: Number of active E-RABs, for which a call is released due
to abnormal operation in eNB.
EstabInitSuccNbr: Number of successfully established initial E-RAB.
EstabAddSuccNbr: Number of successfully established added E-RAB.
Unit: Percentage(%)
Measuring point
For E-RAB drop statistics
E-RABs released by the eNB due to user inactivity and normally
released by the MME are not considered abnormally terminated.
For established E-RAB statistics,
Successful E-RAB establishment considers both of the default and
additional bears setup successful.
Handover Success Rate-Intra LTE
Description
Success rate of overall handover.
Successful attempts compared with total number of handover attempts.
KPI Formula
HO Success Rate = [(IntraEnbSucc+ InterX2OutSucc + InterS1OutSucc) /
(IntraEnbAtt+ InterX2OutAtt + InterS1OutAtt)] * 100
IntraEnbAtt: Intra eNB Handover attempt count
IntraEnbSucc: Intra eNB Handover success count
InterX2OutAtt : X2 Handover attempt count in source eNB
InterX2OutSucc : X2 Handover success count in source eNB
InterS1OutAtt : S1 Handover attempt count in source eNB
InterS1OutSucc : S1 Handover success count in source eNB
Unit: Percentage(%)
Measuring point
Please refer to the following slides for the details of measuring points of
each parameter.
Intra-eNB Handover
Description
Success rate for intra-eNB handover.
Successful attempts compared with total number of attempts.
KPI Formula
[IntraEnbSucc/ IntraEnbAtt] * 100
IntraEnbAtt: Intra eNBHandover attempt count
IntraEnbSucc: Intra eNBHandover success count
Unit: Percentage(%)
Measuring point
For intra-eNB HO statistics
when an intra-handover is decided after the Measurement Report
message arrival, it is counted as Attempt;
When the target cell successfully receives the RRC Connection
Recon guration Complete message from the UE, it is counted as
Success.
Inter-eNB X2 Out Handover
Description
Success rate for X2 Out handover.
5. Successful attempts compared with total number of attempts.
KPI Formula
[InterX2OutSucc / InterX2OutAtt] * 100
InterX2OutAtt : X2 Handover attempt count in source eNB
InterX2OutSucc : X2 Handover success count in source eNB
Unit: Percentage(%)
Measuring point
For X2 handover out statistics
when the X2 Handover Request message can be transmitted to the
target eNB after the inter X2 handover decision following the
Measurement Report message arrival, it is counted as Attempt;
The target eNB transmits the X2 UE Context Release message to the
source eNB when the handover is successfully completed. At this
point, the source eNB is counted as Success.
Inter-eNB S1 Out Handover
Description
Success rate for S1 handover.
Successful attempts compared with total number of attempts.
KPI Formula
[InterS1OutSucc / InterS1OutAtt] * 100
InterS1OutAtt : S1 Handover attempt count in source eNB
InterS1OutSucc : S1 Handover success count in source eNB
Unit: Percentage(%)
Measuring point
For inter S1 handover out statistics
when the S1 Handover Required message can be transmitted to the
MME after the inter S1 handover decision following the Measurement
Report message arrival, it is counted as Attempt;
The MME transmits the S1 UE Context Release Command message to
the source eNB when the handover is successfully completed in the
target eNB. At this point, the source eNB is counted as Success.
Handover Interruption Time
Description
Statistics of the average setup time of the handover interrupt time in the
target eNB for each cell.
PEG
IntraHOTime: Average Inter-eNB HO interrupt time
X2HOTime : Average X2 HO interrupt time
S1HOTime : Average S1 HO interrupt time
Unit: msec
6.
Cell Throughput (MAC Layer)
Description
Statistics data for the MAC layer cell throughput
Average size of the transport block (TB) successfully sent/received,
among the downlink/uplink TBs that the eNB’sMAC allocated to the UE
KPI Formula
AirMacUlThru= [(AirMacByteUl* 8)/(5.12 * AirMacByteUlCnt)]
AirMacDlThru= [(AirMacByteDl* 8)/(5.12 * AirMacByteDlCnt)]
AirMacUlEfctivThru= [(AirMacByteUl* 8)/AirMacTtiUl]*1000
AirMacDlEfctivThru= [(AirMacByteDl* 8)/AirMacTtiUl]*1000
Unit: Kbps
Packet Discard Rate
Description
Drop rate for downlink packet drops of the user plane traf c, and is
counted by E-RAB QoS level(QCI).
Packet drops can occur due to congestion, traf c management etc.
KPI Formula
7. Packet Drop Rate = {[PdcpSduDropRateDl+ (1 –PdcpSduDropRateDl/ 10^6)
* PdcpPduDropRateDl] / 10^6} x 100
PdcpSduDropRateDl: DL PDCP SDU packet drop rate on the downlink
that occurred for one minute at PDCP layer
PdcpPduDropRateDl: DL PDCP PDU packet drop rate on the downlink
that occurred for 10 seconds at RLC layer
Unit: Packet Drop Rate (%), PdcpSduDropRateDl&
PdcpPduDropRateDl(ppm)
Measuring point
For PDCP SDU Drop Rate statistics
When buffer over ow occurs at the PDCP layer, PDCP SDU will be
discarded.
For PDCP PDU Drop Rate statistics,
When buffer over ow occurs at the RLC layer, PDCP PDU will be
discarded.
Packet Delay
Description
Statistics data for the DL PDCP SDU delay de ned in the standard 3GPP
TS 36.314 for each QCI.
Average DL PDCP SDU delay per QCI
This measurement refers to packet delay for DRBs. For arrival of packets
the reference point is PDCP upper SAP. For successful reception the
reference point is MAC lower SAP
KPI Formula
Packet Delay
PdcpSduDelay: PDCP SDU delay on the downlink.
Unit: msec
Measuring point
For DL PDCP SDU delay statistics
From the point in time when PDCP SDU arrives to the point in time
when the last piece of PDCP SDU was received by the UE according to
received HARQ feedback information.
Block Error Rate (BLER)-Post HARQ
Description
Block Error Rate (BLER) is an error rate of data transmission of
PDSCH/PUSCH after all HARQ procedures.
KPI Formula
DlResidualBLER= [ DlTransmission_Nacked_Retrans3 /
DlTransmission_Retrans0 ] * 100
DlTransmission_Nacked_Retrans3 : Count of the 3rd PDSCH HARQ
retransmission failure
DlTransmission_Retrans0 : Count of the initial PDSCH HARQ
transmissions
UlResidualBLER= [ UlTransmission_Nacked_Retrans27 /
UlTransmission_Retrans0 ] * 100
UlTransmision_Nacked_Retrans27 : Count of the 27th PUSCH HARQ
retransmission failure
UlTransmission_Retrans0 : Count of the initial PUSCH HARQ
transmission
Unit: Percentage(%)
Retransmission Rate (DL/UL)
Description
Retransmission rate of DL and UL user traf c.
Number of retransmitted blocks compared with total transmitted blocks.
KPI Formula
Retransmission Rate DL = [(DlTransmission_Retrans1 +
DlTransmission_Retrans2 + DlTransmission_Retrans3) /
(DlTransmission_Retrans0 + DlTransmission_Retrans1 +
DlTransmission_Retrans2 + DlTransmission_Retrans3)] * 100
Retransmission Rate UL =[(UlTransmission_Retrans1 +
UlTransmission_Retrans2 + UlTransmission_Retrans3 + … +
UlTransmission_Retrans27) / (UlTransmission_Retrans0 +
UlTransmission_Retrans1 + UlTransmission_Retrans2 +
UlTransmission_Retrans3 + … + UlTransmission_Retrans27)] * 100
Unit: Percentage(%)
Summary
SHARE
0
0
0
8.
LTE Timers:-
LTE
Timers
Function at Start/Stop/Expiry
T300
>>Starts at the RRC connection REQ transmit
>>Stops at the Receipt of RRC connection setup or reject message OR at the cell
reselection time OR upon abortion of connection establishment by Higher layers
(L2/L3).
>>At the expiry performs the actions
T301
>>Starts at the RRC Connection Re-establishment REQUEST
>>Stops at the Receipt of RRC Connection Re-establishment OR
RRC Connection Re-Establishment REJECT message OR
When selected cell becomes unsuitable to continue further
>>At expiry, it Go to RRC_IDLE mode
T303
>>Starts when access is barred while performing RRC CONNECTION
ESTABLISHMENT for MO(Mobile Originating) calls
>>Stops while entering RRC_CONNECTED and upon cell re-selection mode
>>At expiry, Informs higher layers about barring alleviation
T304
>>Starts at the Receipt of RRC CONNECTION RECONFIGURATION message along
with Mobility Control Info OR at the receipt of mobility from EUTRA command
message including CELL CHANGE ORDER
>>Stops at the successful completion of HANDOVER to EUTRA or CELL CHANGE
ORDER is met
>>At expiry, it performs action based on need.
1. In the case of CELL CHANGE ORDER from E-UTRA OR intra E-UTRA handover,
initiate the RRC connection re-establishment procedure.
2. In case of HANDOVER to E-UTRA, perform the actions de ned as per the
speci cations applicable for the source RAT.
T305
>>starts when access is barred while performing RRC CONNECTION
ESTABLISHMENT for MO signaling
>>Stops when entering RRC_CONNECTED and when UE does cell re-selection
>> At expiry, Informs higher layers about barring alleviation
T310
>>Starts when UE detects PHY layer related problems (when it receives N310
consecutive out-of-sync INDs from lower layers)
>>Stops 1. When UE receives N311 consecutive in-sync INDs from lower layers/
2. Upon triggering the HANDOVER procedure
3. Upon initiating the CONNECTION RE-ESTABLISHMENT procedure
>> At expiry, if security is not activated it goes to RRC IDLE else it initiates the
CONNECTION RE-ESTABLISHMENT Procedure
T311
>>Starts while initiating RRC CONNECTION RE-ESTABLISHMENT procedure
>>stops upon selection of suitable E-UTRA cell OR a cell using another RAT
>>At expiry it enters RRC IDLE state
T320
>> Starts upon receipt of t320 or upon cell re- selection to E-UTRA from another RAT
with validity time con gured for dedicated priorities (in which case the remaining
validity time is applied).
>>Stops upon entering RRC_CONNECTED state, when PLMN selection is performed
on request by NAS OR upon cell re-selection to another RAT
>> At expiry, it discards the cell re-selection priority info provided by dedicated
signaling
T321
>>starts upon receipt of measCon g including a reportCon g with the purpose set
to reportCGI
>> Stops at either of following cases:
1. Upon acquiring the information needed to set all elds of globalCellId for the
requested cell
2. upon receipt of measCon g that includes removal of the reportCon g with the
purpose set to reportCGI
>> At expiry initiates the measurement reporting procedure, stop performing the
related measurements and remove the corresponding measID