Day objective — reliable access (RRC / RA / admission) and strong retainability (drop & RLF reduction), tuned via golden parameters. Pick a sub-topic on the left — it opens here on its own.
Accessibility KPIs (LTE & NR)
Accessibility is a chain — every stage from random access to bearer setup has its own Samsung KPI and Family ID. A failure at any link drops the end-to-end setup success.
| KPI | Samsung Family ID | Stage |
|---|---|---|
| RRC Connection Establishment SR | 5213 | RRC setup |
| RRC Setup Time | 5214 | RRC setup |
| RRC Resume SR | 5217 | INACTIVE→CONNECTED |
| RRC Re-establishment SR | 5203 | recovery |
| Initial Context Setup SR | 5223 / 5224 | context |
| F1 UE Context Setup SR | 5136 / 5137 | DU↔CU (NR) |
| E-RAB / DRB / PDU-Session Setup SR | 5118 / 5218-5219 / 5222-5438 | bearer |
| Random Access Success Rate | 5243 | RACH |
| Admission Control Fail Rate | 5147 / 5148 | admission |
- Accessibility KPIs (LTE & NR) — unified family map · KPI Explorer · deep-dive hub
- LTE accessibility — full KPI · counter · optimization deep-dive
- 5G NSA (EN-DC) accessibility — SgNB Addition deep-dive
- 5G SA accessibility — RRC/Registration/PDU deep-dive
- RRC Connection Establishment SR —
Family 5213; RRC Setup Time —5214 - RRC Resume SR —
5217; RRC Re-establishment SR —5203 - Initial Context Setup SR —
5223 / 5224 - F1 UE Context Setup SR —
5136 / 5137 - E-RAB / DRB / PDU-Session Setup SR —
5118 / 5218-5219 / 5222-5438 - Random Access Success Rate —
5243 - Admission Control Fail Rate —
5147 / 5148
Accessibility Features & Golden Parameters
The FGR features that govern access, and the golden-parameter groups you tune to move the accessibility KPIs — shown with their real Samsung managed-object leaf, range and default from the Parameter Description.
Every accessibility fix is this chain: an FGR feature owns a gate, a golden parameter (kebab-case, with its MO path) tunes it one variable at a time, and a counter Family ID proves the result after a 48 h soak. The console below turns any golden parameter into a full Format-A tuning card.
Golden parameters are RAT-specific — the same KPI is tuned by a different managed-object leaf in each technology. Pick a RAT, then a parameter; the console renders its full Samsung Format-A card: MO path, doc-exact default, Samsung-recommended value, tuning range, KPI impact, the FGR/LTE-SW feature, the counter Family IDs to watch before/after, a single-variable trial plan, and the rollback trigger. LTE leaves & timer defaults verbatim from the eNB Parameter Description SSLR 9.0.0; NR from the DU SVR22B / CU-ACPF SVR25A descriptions; NSA (EN-DC) from the LTE-anchor eutra-nr-dual-connectivity tree.
t310 ms2000 not ms50, preamble-trans-max n10 not n4, ssb-per-rach-occasion one not one-fourth).- Method — feature (FGR) governs the gate · one kebab-case parameter tunes it · counter Family ID proves it after a 48 h soak · roll back if degraded
- FGR features —
CC3102access ·CC0301/0302/0303capacity/QoS/slice CAC ·CC0102re-establishment ·CC0103/0107/0108Inactive ·RS0121/0122RACH ·LC0303/LC0401overload - Golden params — RRC timers
t300/t301/t304/t310/t311/t319· RACHpreamble-trans-max, power-ramping-step, ra-contention-resolution-timer, msg1-fdm, ssb-per-rach-occasion· admissioncall-cac-threshold, preemption-trigger-arp-priority
Retainability Optimization
Keep established connections alive — call-drop and RLF KPIs, and a structured root-cause workflow that sorts every drop into one of four causes before you touch a parameter.
- KPIs & counters — call-drop and Radio Link Failure (RLF) KPIs and counters
- Drop root-cause workflow — coverage vs interference vs mobility vs capacity
- Golden params · Retainability — RLF + RRC timers, admission-preemption, mobility-related drop settings
- LTE retainability — Call Drop 24 · E-RAB 15 · RRC 4 · RLF/MRO deep-dive with T310 simulator
- 5G NSA (EN-DC) retainability — SCG Failure & SgNB Release dual-ledger deep-dive
- 5G SA retainability — DRB/UE-context release & two-path rescue deep-dive
t310 (Day-2 accessibility) is also the primary retainability lever: shorten it and you recover faster but risk dropping recoverable links; lengthen it and you hold links longer but delay re-establishment. Retainability and accessibility are tuned together, never in isolation.Hands-on Lab 2 — Accessibility Trial & Call-Drop Reduction
Run a controlled accessibility trial by tuning RACH / RRC timers, then work a real call-drop reduction case straight from the counters.
RACH / RRC timer trial · counter-driven call-drop reduction
⚡- 1Baseline the accessibility KPIs (RRC Est SR 5213, RA SR 5243) from the counters
- 2Run an accessibility trial — tune RACH / RRC timer golden parameters (e.g.
t300,preamble-trans-max) - 3Work a call-drop reduction case using the RLF / drop counters and the 4-way root-cause workflow
- 4Verify the KPI movement and document before/after