5G Initial Access Troubleshooting
5G initial access problems happen before the UE reaches random access, RRC setup, or NAS registration. At this stage, the UE must find NR synchronization signals, decode PBCH and system information, determine whether the cell is suitable, and camp normally on the correct cell before it can attempt access.
This page is written as a fault-isolation guide for the pre-access phase. It helps separate can't find or decode the cell, can decode but cannot camp, and camped but gated by access conditions before moving on to random access or RRC setup troubleshooting.
Initial Access Ladder
Keep the troubleshooting boundary at camped normally and ready for access, not inside later RACH or RRC setup handling.
Step 1: Search for NR cell
- frequency scan or stored information path
- SSB detection
- synchronization acquisition
Step 2: Decode PBCH and essential broadcast information
Step 3: Acquire SIB1
cellAccessRelatedInfo- access-related broadcast fields
- optional
uac-BarringInfo
Step 4: Determine cell suitability
- right PLMN or selection context
- suitable-cell conditions met
- not effectively barred for the intended service
Step 5: Camp normally
- UE camps on the selected suitable cell
- monitors control and system information
- ready to proceed to random access
Baseline Successful Call Flow
Use this baseline to confirm where the pre-access chain actually stops.
Call Flow: Normal Initial Access Up To Camping
Symptoms and Fast Triage
Map the symptom first, then decide whether the failure is still in search, broadcast acquisition, suitability, or access gating.
UE cannot find the cell at all
- SSB detection issue
- RF, coverage, or beam issue
- wrong frequency or scan scope
- severe radio quality problem
UE sees the cell but cannot proceed
- PBCH or broadcast decode issue
- unstable synchronization
- MIB or SIB1 acquisition failure
UE decodes SIB1 but does not camp normally
- unsuitable-cell logic
- wrong PLMN selection context
- barred or restricted access condition
- cell not acceptable for the intended service
UE camps but still never starts access
- access gating before random access
- SIB1 access restrictions
- wrong troubleshooting branch after camping
Cell Search and Synchronization Checks
Initial access cannot proceed without a stable synchronization starting point.
What to verify first
- correct NR frequency or carrier under test
- SSB visibility
- synchronization stability over repeated attempts
- whether the failure is total or intermittent
Example: SSB not reliably found
Observed behavior - UE scans expected NR carrier - no stable initial cell candidate is retained - no consistent move to PBCH decode stage Interpretation - stay in RF, synchronization, and search scope - do not jump to SIB1 or RRC troubleshooting yet
PBCH and Broadcast Acquisition Checks
A UE can see something NR-like without being able to acquire the cell cleanly enough for normal service.
PBCH and early broadcast checkpoint
- does PBCH decode complete consistently
- does the UE move from synchronization to system information acquisition
- does the problem occur only on some beams or cells
Example: Cell seen but broadcast acquisition fails
Observed behavior - UE detects cell timing - PBCH or follow-on broadcast handling is inconsistent - UE never gets to stable SIB1-driven suitability evaluation Interpretation - treat this as a broadcast acquisition problem - do not classify it as barring or NAS failure
SIB1 and Access-Gating Checks
SIB1 is the first structured breakpoint where the UE learns whether the cell is operationally usable for its access attempt.
What to inspect in SIB1
cellAccessRelatedInfo- selected PLMN relevance
- optional
uac-BarringInfo - any service or access restrictions relevant to the UE's attempt
Example: SIB1 decoded but access is gated
Observed behavior - UE decodes SIB1 - UE does not proceed into a normal access attempt Checks - inspect cellAccessRelatedInfo - inspect uac-BarringInfo - confirm the issue is pre-random-access and not later RRC failure
Suitable Cell and Camping Validation
Suitable-cell and camped-normally status are the clean breakpoints between initial access failure and readiness for random access.
What to verify
- UE selected the intended PLMN
- cell passes suitability logic
- UE reaches camped normally state
- system information remains stable after camping
Example: Cell found but not suitable
Observed behavior - UE can detect and decode the cell - UE still does not camp normally Interpretation - issue is in selection or suitability logic, not in pure RF detection - check PLMN context, suitability assumptions, and broadcast access conditions
Handover to the Next Troubleshooting Branch
Only leave this page once the UE is genuinely ready to start access.
When to leave this page
- found and selected a suitable cell
- camped normally
- decoded the required broadcast information
- became ready to attempt access
Next likely branches
Practical rule
- failure before camping normally: stay on this page
- failure after camping, during access attempt: move to random access or RRC setup pages
Practical Troubleshooting Workflow
Keep the investigation anchored to the first hard stop, then avoid drifting into later branches too early.
1. Confirm the first hard break
- no cell found
- cell found but PBCH or broadcast not stable
- SIB1 missing or unusable
- cell decoded but not suitable
- camped normally but access gated
2. Decode the exact stage
- search and synchronization
- PBCH
- SIB1
- suitability
- camping
- pre-random-access gating
3. Avoid false branches
- do not start with RACH if the UE is not camped normally
- do not start with RRC setup if SIB1 or suitability is still failing
- do not start with NAS if the UE never reached access readiness
4. Escalate to the right team
- RF, beam, or coverage issue
- broadcast or system-information issue
- access control, barring, or configuration issue
- PLMN, suitability, or selection-logic issue
Evidence Checklist for Escalation
Escalation should show the exact stage where progress stopped, not just a generic access failure label.
Minimum radio evidence
- carrier or frequency under test
- SSB detection result
- PBCH decode result
- SIB1 decode result
- camping state outcome
Minimum decoded broadcast evidence
- SIB1 snapshot
cellAccessRelatedInfouac-BarringInfoif present- PLMN-related fields used by the UE
Minimum problem summary
- whether the UE ever reached camped normally state
- whether the issue is cell-specific or area-wide
- whether the issue is constant or intermittent
- exact first stage where progress stops
Specification Map
FAQ
What is the difference between initial access failure and random access failure?
Initial access failure stops before the UE is truly ready to attempt access. The UE may fail during search, synchronization, PBCH decode, SIB1 acquisition, suitability checks, or camping. Random access failure starts later, after the UE has found a suitable cell, camped normally, and is ready to begin the access attempt.
Why is SIB1 the key breakpoint in early 5G access troubleshooting?
SIB1 is where the UE learns the main access-gating information for the cell, including cellAccessRelatedInfo and optional uac-BarringInfo. That makes it the clean breakpoint between pure radio detection problems and access-control or suitability problems.
When should I treat the problem as a suitable-cell issue instead of an RF issue?
Treat it as a suitable-cell issue when the UE can already detect and decode the cell but still cannot camp normally or use the cell for the intended service. If the UE never reaches stable detection or broadcast decode, stay in the RF, search, and synchronization branch first.
What does camped normally mean for fault isolation?
Camped normally is the practical breakpoint between early access preparation and later access execution. If the UE has not reached that state, you should not jump into random access, RRC setup, or NAS registration analysis yet.
When should I move from this page to random access troubleshooting?
Move on only after the UE has found and selected a suitable cell, decoded the required broadcast information, camped normally, and become ready to attempt access. If the break happens before that point, stay on the initial-access branch.