Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
RRC SR%
CSFB SR%
E-RAB Drop%
DL Traffic Volume(GB)
DL Cell Throughput
RRC SR%
• The RRC setup procedure is trigged by different reasons as identified by the EstablishmentCause field in the RRCConnctionRequest
message: Emergency , HighPriorityAccess , Mt-Access , Mo-Signaling
The symptoms of an RRC connection setup failure on the eNB are as follows:
After delivering the RRC Connection Setup message, the eNB fails to receive the RRC Connection Setup Complete
message.
The eNB sends the RRC Connection Reject message to indicate that the eNB is faulty.
1. Resoure Family
2. Reject Family
3. No Reply Family
RRC SR%: Reason of failure
1. Resource Family
The number of RRC connection failures due to resource allocation failures, they are summed up into:
PUCCH resource failures due to the full capacity of the channel.(Physical Uplink Common Channel)
SRS”Sounding Reference Signal” : the eNB cannot estimate the UL channel quality and cannot proceed an UL
frequency selective scheduling.(Channel that carry the reference signal)
User Specification: each cell carries 600 RRC connected UE (limitation of UE Number).
RRC IDLE: for all users so we have no limitation for RRC number
RRC CONNECTED: the maximum number of users who can camp on the cell is 600, which means for example the user
number 601 cannot access to the cell.
RRC SR%: Reason of failure
2. Reject Family
As mentioned before, the eNB will send RRC Connection Reject message if it fails to receive the RRC Connection Setup
Complete message. The RRC connection reject message due to:
Flow Control: UE sends data (out of standard) that the eNB cannot understand.
Theoretically, the UE must transmit the packets by respecting the same data rates adapted by the eNB.
Forbidden Acknowledgement: The UE is located at a distance greater than the cell radius.
MME overload.
RRC SR%: Reason of failure
3. No Reply Family
We are exposed to have a failure in RRC connection setup due to bad radio condition. The UE cannot hear the RRC
Connection Setup Complete message because of site overshooting or the site depends only on RSRP without taking into
consideration the quality of the site (RSRQ).
To avoid all these problems, we have to set timers that control the waiting time of RRC Connection Setup Complete and set
a threshold for the UEs trying to access the network and if they exceed this threshold they must wait a certain time before
reestablishing the connection. We can also decrease the transmitted power if the site overshoots. Moreover, we can check
the IDLE Mode parameters (Cell Selection and Cell Reselection to avoid RRC connection failures.
RRC SR% : Counters name and description
The EnodeB is started T300 when the UE sends RRCConnectionRequest and end when UE received the RRC
T300 RRCConnectionSetup or RRCConnectionReject . Change From 1000ms to 1500ms. LST UETIMERCONST
RRC SR% :Recommended Actions
Indicates the number of trials that UE can retry to make RRC Request(threshold for an RRC
connection penalty). Change From 10 to 5.
RRC Connection Punish Threshold
LST GLOBALPROCSWITCH
Timer that is started after UE finished all his trials of retrying to make RRC Request and all Fail(UE has to
T302 wait a certain time T302 to initiate a request again).Change From 4s to 16s. LST RRCCONNSTATETIMER
Timer is Started from eNodeB at RRC Setup and end at RRC Connection Setup
RRC Connection Setup Complete Waiting Timer Complete(Indicates the timer for the eNodeB to wait for a RRC Connection
Setup Complete). Change to 15s. LST ENODEBCONNSTATETIMER
QrxLevMin , SIntraSearch ,
• SrxLev = QrxLevMin + S-IntraSearch Or S-NonIntraSearch
SNonIntraSearch , QqualMin , SIntraQ
• Squal = QqualMin + S-IntraQ Or S-NonIntraQ
, SNonIntraQ LST CELLRESEL
Measurement
• This KPI can be used to evaluate the ERAB setup success rate of all services in a cell or a cluster.
• The E-RAB Setup Success rate in a cell directly represents a capability of the cell to provide E-RAB Connection Setup for Users.
carried on SRB
0 To Transfer
First UL NAS
Message
carried on SRB
1
• VSWR alarm.
• RF unit maintenance alarm.
• Cell Unavailable.
• RF out of service.
• CPRI or BBU alarms.
Check TA.
Check S1 availability.
Check NBRs.
Actions
LST CELLRESEL
Sintra and Snonintra Search Change Threshold for non intra freq measurements(2dB) from 5 to 10
Change Threshold for intra freq measurements(2dB) from 25 to 30
E RAB Setup SR%: Recommended Actions
If this parameter is set to a small value, excessive polling PDUs are sent. In addition, the
SRB1, SRB2 and DRP number of ARQ retransmissions reaches its maximum due to consecutive PDU
retransmissions, and therefore the RRC connection is reestablished. If this parameter is set to
a large value, status reports cannot be sent promptly Change From 40ms to 100ms.
LST SRBRLCPDCPCFG & LST RLCPDCPPARAGROUP
CSFB SR%
One of the major design choices of LTE was to focus on the development of a packet-based core and access network
infrastructure. The circuit-switched core network and dedicated telephony features of GSM and UMTS radio access
networks have not been adapted for LTE. This design reduces the overall complexity of the network. Here, a clear trend
toward IP and voice services over IP is well ongoing in Egypt. But we have to offer traditional circuit-switched services
over an IP connection (in case of not using the VoIP services) because for a user, it should be invisible if the service is
offered over the circuit-switched part of the GSM or UMTS network or the packet-switched IP-based LTE network. Also,
.should be seamlessly handed over to GSM or UMTS if the user leaves the LTE coverage area. In other words, the IP-based
voice call must be converted to a circuit-switched voice call on the fly as otherwise the overall user experience will be
unsatisfactory. So we implement the CSFB solution to meet this criterion. The SGs interface can be used to deliver paging
messages that inform the mobile device of an incoming call. The call itself, however, is not delivered over the LTE interface
and the UE has to fall back to a GSM or UMTS network where a circuit-switched connection is then established for the
call. This method of delivering voice calls is therefore referred to as CS (circuit-switched) fallback and is executed as
follows.
CSFB SR%
• F2:10787
• M1:3087
• M2: 3066
LST UTRANNFREQ
LST UCELL
CSFB SR% : UTRANRANSHARE
LST UTRANRANSHARE
CSFB SR% : UTRANNCELL
LST UTRANCELL
E-RAB Drop%
• This KPI can be used to evaluate the call drop rate of all services in a cell or a cluster.
• MME Send E-RAB Normal Or Abnormal Release based on the Causes.
• Normal Release for Detach , User Inactivity , CSFB , Om-Intervention , HO , IRAT Redirection.
Normal and
Abnormal
Release
Counters based
on the Causes
E RAB Drop%: Reason of failure
The reasons of Call Drop are summed up as follows:
Radio Problems: If abnormal releases are counted into ERAB.AbnormRel.Radio counter, the call drop is caused by the radio
interface problem on the wireless network side.
DRB: the DRB cannot carry data packets
SRB: the SRB cannot carry signaling messages.
UL Synchronization: there is no synchronization between eNB and UE.
No Reply: the UE doesn’t hear the message
A call drop with the cause value being radio is caused by the reason that the RLC retransmissions reach the maximum timer,
out of synchronization occurs or signaling messages exchange fails due to weak coverage, UL interference or UE faults
Handover Problems: a call drop with cause value being handover failure is caused by an abnormal release due to a failure in
handover out of the serving cell.
Transport Problems: Call drops can be caused by transport layer problems, transmission problem between the eNB and the
MME (disrupted S1 Link).
Congestion Problems: congestion of radio resources (Shortage) on the eNB for example max number of active UE is reached.
We can offload traffic from the serving cell to its neighbors.
MME Problems: A call drop is caused by an abnormal release initiated by the EPC.
E-RAB Drop%:Counters name and description
L.E-RAB.AbnormRel.Radio.DRBReset No.of Abnormal Release because RLC PDU for an DRB has been retransmitted for the MAX No.of
Times
No.of Abnormal Release because RLC PDU for an SRB has been retransmitted for the MAX No.of
L.E-RAB.AbnormRel.Radio.SRBReset
Times
L.E-RAB.AbnormRel.Radio.ULSyncFail No.of Abnormal Release Due to ULSyncFail between UE and enodeB
L.E-RAB.AbnormRel.Radio.UuNoReply No.of Abnormal Release Due to No Response from UE
L.E-RAB.AbnormRel.TNL No.of Abnormal Release Due to Faults at the Transport Network Layer
E-RAB Drop%: Recommended actions
Actions
If this parameter is set to a small value, excessive polling PDUs are sent. In addition, the
number of ARQ retransmissions reaches its maximum due to consecutive PDU
UePollRetransmitTimer retransmissions, and therefore the RRC connection is reestablished. If this parameter is set to
ENodeBPollRetransmitTimer a large value, status reports cannot be sent promptly Change From 40ms to 100ms.
LST SRBRLCPDCPCFG & LST RLCPDCPPARAGROUP
A smaller value of this parameter results in a higher probability that UEs enter the out-of-synchronization
state when they should not and, therefore, a larger number of random access procedures triggered for
maintaining uplink synchronization and more occupied resources for random access. A larger value of this
UL Sync Timer
parameter results in fewer prompt changes of UE status from uplink-synchronized to out-of-synchronization,
more power consumption of UEs, and more occupied PUCCH and SRS resources Change From 180ms to
300ms.
LST RRCCONNSTATETIMER
Indicates the trigger quantity of inter-RAT events A1 and A2. Change From RSRP to BOTH.
InterRAT A1A2 Measurement LST INTERRATHOCOMM
Trgger Quantity Change RSRQ value InterRatHoA1ThdRsrq & InterRatHoA2ThdRsrq
LST INTERRATHOCOMMGROUP
E-RAB Drop%
KPIs Performance After DRX Trial and InterRAT A1A2 Measurement Trigger Quantity
Improvement at E-RAB Drop% Due to Change InterRAT A1A2 Measurement Trigger Quantity From RSRP to BOTH.
DL Cell Throughput
Formula Cell DL Average Throughput (Mbps) = [L.Thrp.bits.DL]*1000/(1000*1000*[L.Thrp.Time.Cell.DL.HighPrecision])
The eNB needs knowledge of the SINR conditions of downlink transmission to a UE in order to select the
most efficient MCS/PRB combination for a selected UE at any point in time.
Radio Analysis
Channel Quality Index (CQI):
Is a feedback mechanism from UE to eNB.
Informs eNB of current channel conditions as seen at UE.
CQI 1-6 map to QPSK
CQI 7-9 map to 16QAM
CQI 10-15 map to 64QAM
PCI Clashes
If we have UL Interference
THANK YOU