E2E Performance Team
E2E Performance
RF Job Aid
Version Date Author Notes
Information
1 11/25/2020 Alex Gardini Initial Document Released
Title Degraded SIP DCR - RF Job Aid
Purpose
▪ To quickly identify sites with SIP drop degradation.
▪ Fast identification of sudden KPI degradations and fast action on them are very important. It
increases the chances the network Engineer can identify the cause of the degradation and
restore the previous performance protecting the customer experience and KPis.
▪ This document explains the logic behind the audit and suggests troubleshooting steps.
Issues flagged and related KPIs
Issue Name KPI Ericsson KPI Nokia
Degraded SIP DCR Overall SIP DCR% / all_drops Overall SIP DCR% / all_drops
Criteria to flag cells with issues
▪ FALCON identifies deviations on SIP DCR pattern based on statistical analysis from last 10 weeks.
▪ Falcon identifies deviant sites compared to the historical performance and flags the ones with relevant number
of new drops.
▪ SIP DCR = SIP Volte Drops / SIP Volte Calls.
Issue Name Logic
SIP DCR = SIP Volte Drops / SIP Volte Calls.
Degraded SIP DCR Falcon identifies deviant sites compared to the historical performance and flags the
ones with relevant number of new drops.
Suggested troubleshooting steps:
➔ Check hourly SIP DCR. Issue might have been a one-time spike already normalized.
➔ Check if drop cause is mainly SIP 481, SIP 503, SIP 408 or others.
o SIP 503 - Can be RAN related, but after MME GBR Retention activation, is mostly result of:
▪ SW issues in device
▪ Interoperability issues UE/eNB/Core
▪ Parameter mismatch
o SIP 481 - Generally related to poor RF or transport issues (check backhaul)
o SIP 408 - Rarely RF related, mostly Core/Transport related
▪ Possible reason in Ericsson: scheduling misconfigured, Ethernet port speed too low
▪ Possible reason in NOKIA: SW issue in TDD (requires restart)
o All Other SIPs - Core/IMS related
➔ Check for other issues flagged for this site in FALCON and if they match the degradation date
➔ Verify if there has been activity in the site and what has been done
➔ Check for Tilts and other configuration/parameters changes matching the degradation date
➔ Check for possible wrong parameters, as wrong EARFCN configured in mobility related objects (e.g.
LNHOIF/IRFIM for Nokia).
➔ Check if handover performance is normal (RSSI issue on neighbor site can prevent handover and lead
to call drop).
➔ Check for degraded performance or outages in neighbor sites.
➔ Check for alarms and hardware issues.
➔ Check for RF shaping opportunities.
➔ Consider site reset if nothing else helps.
Cases Fixed – Examples
Site Engr Comments
PH21005F James Madison Fixed, Post-retune LNHOIF/IRFIM Corrected
Site Engr Comments
PH33934E FNU ABIN JOSE Fixed, Post-retune LNHOIF/IRFIM Corrected
