CafeTeleRadio Optimization SRPO-600 Enroll now ↗
‹ Day 2 · Accessibility Course / Day 2 / 2.2 / Access Features & Golden Params
FGR
2.2
2.2 · Access Features & Golden Parameters

Accessibility Features & Golden Parameters — the Full Catalog

Two things move an accessibility KPI: the feature that governs the gate, and the golden parameter you tune inside it. This page is the complete reference for both — every access-governing feature for LTE, 5G SA and 5G NSA (EN-DC) as a clickable React-Flow pipeline, plus the golden-parameter master tables (RRC timers, RACH/PRACH, admission & overload) with real MO leaf, range and doc-exact default. Click a RAT, click a feature.

43Features across 3 RATs
14LTE (LTE-SW…)
22NR SA (FGR-…)
7NSA / EN-DC
24golden parameters
The feature catalog — pick a RAT, click a feature (React-Flow pipeline)

Each RAT's access-control features arranged as the gate pipeline a request passes. Switch RAT with the buttons; click any feature node for its card — what it is, benefit, recommended parameters and the counters it moves. The fullest per-feature detail lives on each technology's optimization page (linked from every card).

Access-Control Feature Pipelineclick a feature node to open its detail card
!
Order matters — a request passes barring/access → overload → admission → procedure (LTE & SA), or B1 trigger → prep transport → SgNB Addition → keep-the-leg (NSA). Rule out the deliberate gates before tuning capacity — rejected-by-design is not a fault.
Golden parameters · RRC timers & constants (doc-exact)

The UE timers that shape every setup, resume and recovery — MO [DU] ue-timer-constants / ue-timer-const-info, defaults verbatim from the Samsung DU Parameter Description (these supersede the older catalog values; always RTRV your release template first).

ue-timer-constants — NR DU model
LeafRangeDefaultWhat it times · optimization
t300ms100 … ms2000ms200Started on RRCSetupRequest; stops on RRCSetup/Reject. Too short → premature setup-fail counts; too long → worse RRC Setup Time (5214)
t301ms100 … ms2000ms200Started after RRCReestablishmentRequest
t304… ms10000ms1000Handover / PSCell completion (reconfig-with-sync) — widen on large cells / marginal targets
t310… ms6000ms2000Out-of-sync (physical-layer problem) detection — the direct lever between retainability (hold good links) and fast recovery
t311… ms30000ms5000RRC re-establishment cell-search window — widen where neighbour search is slow (deep indoor)
t319ms100 … ms2000ms600Started on RRCResumeRequest (from INACTIVE) — the resume-side timeout
n310… n20n10Consecutive out-of-sync before t310 starts — lower = more sensitive RLF detection
n311… n10n1In-sync count that cancels t310 — raise to require a steadier recovery
Tuning logic — t300 is the accessibility lever (setup supervision); t310/t311/n310/n311 are the retainability↔recovery levers (RLF declaration & re-establishment search); t319 is the resume lever. Move them together — a shorter t310 recovers faster but drops recoverable links.
Golden parameters · RACH / PRACH (doc-exact)

Stage-0 access — MO [DU] ul-physical-resource-config/prach-config & SON rach-optimization. Governed by FGR-RS0121/RS0122 (Random Access Support). A weak SSB beam shows in the per-beam RACH family (5243) before it shows anywhere else.

prach-config — NR DU model
LeafRangeDefaultEffect · optimization
preamble-trans-maxn3 … n200n10Max preamble transmissions (TS 38.321 §5.1.4) — raise where access is coverage-limited
power-ramping-stepdB0 / dB2 / dB4 / dB6dB2Preamble power ramp per attempt — dB4 converges faster at the edge (more interference)
ra-contention-resolution-timersf8 … sf64sf64Msg4 contention-resolution window — shorten for faster failure/retry
msg1-fdmn1 / n2n1RACH occasions in frequency (FGR-RS0121) — n2 doubles capacity under PRACH congestion
prach-configuration-index0 … 255(plan)PRACH format/periodicity (TS 38.331 §6.3.2) — denser = more RACH opportunities; cell-lock to change
ssb-per-rach-occasion-choice… fouroneSSB→RO mapping density — match to SSB beam count; wrong mapping starves beams (check 5243)
cb-preambles-per-ssb1 … 6456Contention preambles per SSB — lower only when reserving CFRA; too low = collisions
zero-correlation-zone-config0 … 1512Preamble cyclic-shift spacing — must match cell radius; wrong value = ghost/missed preambles
Golden parameters · Admission & overload

The hard limits that cap concurrent context (protecting existing users) and the overload switches that shed new access under congestion — the direct levers behind Admission Control Fail Rate (LTE reject causes · NR Families 5147/5148).

Admission & overload — LTE & NR
LeafRATDefaultOptimization
max-enb-call-count / max-call-countLTE18000 / —eNB & cell UE-count caps (SW4101) — size to channel-card capability
call-cac-threshold-for-normalLTE90%Lower to 80–85% to intervene before overload; emergency/HO keep their own higher thresholds
call-count-cac-usageNRuseMaster call-count gate (CC0301) — behind CacFail_GnbCallCount (5148)
call-cac-thresholdNR100.00Lower to 80–90% for early intervention
qos-based-cac-usageNRusePRB-aware GBR admission (CC0302) — behind CacFail_QosBasedCount (5147)
slice-cac-usageNRnot-useEnable when slicing is sold (CC0303) — per-slice-group portions; read per S-NSSAI (5438)
call-protect-usage / paging-protect-usageNRnot-useEnable (FGR-LC0303) — caps RRCSetup/Resume + SgNB-Add + paging per unit time to protect CPU
preemption-trigger-arp-priorityNR3 (1..15)ARP at/above which a new call preempts (CC0401) — lower = more aggressive priority protection
i
The overload families — deliberate shedding is counted: LTE Family 253 Denied_*/Discarded_*; NR Families 5180/5185 denied/discarded paging. When accessibility dips, check these before blaming RF — a rejected-by-design request is not a fault.

Feature governs the gate — parameter tunes it.

Pick the RAT, find the feature on the pipeline, then reach for the golden parameter it exposes. Full per-feature optimization workspaces live on the LTE, NSA and SA pages.

Sources: Samsung eNB (LTE) Feature Description SVR24B (LTE-SW features), 5G RAN Feature Description SVR25B (FGR-CC/BC/LC features), and the eNB / CU-ACPF (SVR25A) / DU (SVR22B) Parameter Descriptions (MO leaf, range, default). Every feature code, name, MO and default is verbatim; recommended values are Samsung optimization guidance. Full per-feature cards on the LTE / NSA / SA optimization pages.