Title: Throughput Analysis Flow Chart
Phase
Non-Consistent flow
To identify low Consistency check No
throughput sectors with Out of 14 days check
DL Throughput < 5Mbps if cell is non-
Flow
Start and UL Throughput < conforming for 5 or
512kbps, With DL Payload more days(based on
>25MB & UL payload step 1) then cell has
>5MB consistent low thrpt
Consistent flow
Yes
MYCOM to convert date & time to Days to
check for specific pattern:
MYCOM to convert date & time to Days to
Pattern 1:-Which day KPI degradation check for specific pattern:
started and if degradation is still on-going Combine day and
Pattern 1:- Poor only on weekends
till the date(Analysis we are doing) hour logic to check if
When
Pattern 2: Poor only on specific day of Yes
Pattern 2: Greater than equal to 3 pair we get day and hour
Yes week
days combination pattern
Pattern 3: Poor only for particular hour/
Pattern 3: Check whether the problem
hours
exist in busy hour or across hours (if more
than 50% of the quarter hours are having
problem, then it is consistent across all
hours)
Store the pattern Store the pattern
No
No
Take the Traffic Pattern and Store
What
Which other KPIs VoLTE (%)
check if problem is
have been Video(%)
in both DL & UL
degraded along with HSI (%)
throughput
throughput IMS Sig(%)
Others (%)
Page-1
Creating neighbour
handover matrix
Based on Inter S1
Now for Check Coverage
Where
out ATT + Inter X2
neighbouring check Hole, Ping Pong &
out ATT which
throughput statistics Too Late & Early HO
neighbours have
and define zone issues
contributed to more
than 2% of total
attempts ( tunable ).
Check configurations for
electrical tilt and
parameters (to be
specified) or configuration
inconsistencies, VSWR
Check the following scenarios by analysing hourly statistics step by step:
1. Check CQI Samples (1-6) – If more than 50%
2. Check MCS Samples (0-9) – if more than 50%
3. If CQI & MCS band have more than 10% variations highlight
4. check initial and Residual BLER - Retrans0>10% and Residual BLER > 2%
5. Check Interference Power >-95 dBm or Thermal Noise >-95 dBm or RSSI
>=-85 dBm Final output will be:
6. Check GTP loss statistics if more than 1% and Packet Count > 10000
Why
If none of the issue
7. Check Ethernet Interface Utilization if > 70%
Check Alarms on site in is observed, then to
1. Findings of when, what, where & who
8. Check Packet Discard Rate/PDCP Delay for latency
9. Check RI2 samples if less than 50% for MIMO
question and of check CEM traces 2. Configuration issues
neighbour sites for understanding in
10. Check capacity statistics: a) PRB & TTI utilization > 70%
b) ENB processor load c) Scheduled users per TTI
detail. 3. Alarms/Availability/PE
11. Type of Traffic If Non HSI traffic >50% 4. Analysis of why to be highlighted
12. Check Packet Loss Rate >
13. TA Distribution >50% of the samples >15 TA
14. UE Tx Power – After Getting all the Attempts in CSL
Hourly Analysis:
15. If Payload/RRC Connected Users < 2 MB or constant payload &
throughput is observed then it may be due to application behaviour
Consistency check
Out of 14 days check
MYCOM will identify
if cell is non-
sector>2% &&
conforming for 5 or
Start Attempts(denom)>100 or Consistent flow
more days(based on
Absolute call drop >10 on
step 1) then cell has
daily basis(Tunable)
consistent high drop
calls
MYCOM to convert date &
time to Days
Pattern 1:-Which day KPI Pattern 2:-Greater
E.G:-MON-TUE-WED Week 1
degradation started and if than equal to 3 pair
MON-TUE-WED Week 2
degradation is still on-going till days
the date(Analysis we are
doing)
Compare with last 6
If the hour in
First check hourly days if those hours Combine day and
question is
pattern of total drop which are identified hour logic to check if
having drops
count for the day/ are having >= 8% of we get day and hour
>10% of total
date the total drops for combination pattern
drops(tunable)
more than 3 days
1.Calculate call drop
eNB HW /SW
ratio per established
RF
cause for non
Availability Based on Category Which accessibility
conforming days
Eg. Cause num (total drop )/ Backhaul Issue now bifurcate and mobility KPI has
2.If any established
denom(eRAB +X2+S1) Calculating % counter wise failure degraded along with
cause is having 5%
contribution of each ratio call drop rate
or more failures we
category to overall
will store this
drop call
information
Creating neighbour
handover matrix
Based on inter site
Based on Inter S1 Thumbrule will Now for
distance rank
out ATT + Inter X2 check for Intra neighbouring check
neighbour sectors.
out ATT which sector statistics also call drop rate and
Any rank anamolity
neighbours have and quality with define zone where
add that neighbour
contributed to more MRO ping pong stats drop call happening
sector in analysis
than 2% of total
attempts ( tunable ).
For non conforming
days only
1. IMEI make -?
2.Nuimber series
3. Subscriber
4. Device type
Interference power
RF
UE Tx power for all (UL) Quality
1. Coverage
negative value During which hour
2.Interference
How many drop calls Interference Power
due to PHR is >-95 check in CSL
Coverage Why call drop
during that time as
1. UL -UE TX power Due to RF
CQI and BLER – UL Interference
2.DL -CQI BLER Check Alarms on site
Check CQI (0-3) drops
in question and
-Map Cal Rel time DL interference
Interference neighbour sites
-Check BLER For CQI (0-3) when
1 .UL Interference
no BLER &
Power and Internal
Retransmission Interference it is due
Noise
>10% for that time to DL quality
2. DL ?
