1. Introduction to RACH in NTN
Random Access Channel (RACH) is the first step for UE to access the network. In NTN, this process becomes significantly more complex due to long propagation delay, satellite movement, and timing uncertainty.
- Critical for initial access, handover, and uplink synchronization
- Highly sensitive to timing and power alignment
- One of the most failure prone procedures in NTN
2. RACH Procedure Recap (Terrestrial vs NTN)
Standard 4 step RACH procedure:
- Msg1: Preamble transmission
- Msg2: Random Access Response (RAR)
- Msg3: RRC request
- Msg4: Contention resolution
| Step | Terrestrial Behavior | NTN Impact |
|---|---|---|
| Msg1 | Accurate timing | Delay uncertainty |
| Msg2 | Fast response | RTT delay impact |
| Msg3 | Stable UL sync | TA errors affect decoding |
| Msg4 | Quick resolution | Delayed completion |
3. Key NTN Challenges Affecting RACH
- Long RTT → delayed response windows
- Timing advance inaccuracies
- Doppler shift due to satellite movement
- UE location uncertainty
- Beam edge propagation variation
These factors directly impact RACH success probability.
4. Types of RACH Failures in NTN
Common failure categories:
- Preamble not detected (Msg1 failure)
- No RAR received (Msg2 failure)
- Msg3 decoding failure
- Contention resolution failure
Each type points to different root causes.
5. Case 1: Preamble Detection Failure (Msg1 Failure)
Symptoms:
- High RACH attempts
- Low preamble detection rate
Root causes:
- Incorrect timing advance estimation
- UE power too low (path loss, beam edge)
- Doppler shift impact
Optimization actions:
- Increase RACH preamble power
- Use larger cyclic prefix formats
- Improve TA estimation (GNSS assisted)
6. Case 2: RAR Timeout (Msg2 Failure)
Symptoms:
- UE sends preamble but does not receive response
Root causes:
- RTT longer than RAR window
- Incorrect RACH response window configuration
Optimization actions:
- Increase RAR window size
- Configure NTN specific timing parameters
- Align scheduling with RTT
Real insight:
- This is one of the most common NTN misconfigurations
7. Case 3: Msg3 Failure (Uplink Decoding Issue)
Symptoms:
- RAR received, but connection fails afterward
Root causes:
- Timing misalignment (TA error)
- Poor SINR at uplink
- Beam edge conditions
Optimization actions:
- Improve TA accuracy
- Increase uplink power control parameters
- Optimize beam coverage overlap
8. Case 4: Contention Resolution Failure
Symptoms:
- Multiple UEs collide
- Access process restarts
Root causes:
- Limited preamble space
- High load conditions
- Poor preamble planning
Optimization actions:
- Increase number of available preambles
- Use group based preamble allocation
- Load balancing across beams
9. NTN Specific RACH Parameter Tuning
Critical parameters to tune:
- RACH configuration index
- Preamble format (long formats preferred)
- Power ramping step
- Maximum retransmissions
- RAR window size
| NTN Recommendation | |
|---|---|
| Preamble Format | Long sequence |
| RAR Window | Extended |
| Power Ramping | Aggressive |
| Max Attempts | Higher than terrestrial |
10. Beam Edge Effect on RACH Performance
Users at beam edge experience:
- Higher path loss
- Lower SINR
- Timing uncertainty
Impact:
- Increased RACH failures
- More retransmissions
Optimization:
- Beam overlap tuning
- Power boosting strategies
- Smart beam selection
11. Troubleshooting Workflow (Field Perspective)
Step by step approach:
- Check RACH success rate KPI
- Break down failure type (Msg1, Msg2, Msg3, Msg4)
- Correlate with:
- TA distribution
- UE location (beam edge vs center)
- Load conditions
Then apply targeted fixes instead of generic tuning.
12. Practical Optimization Strategy
From RF optimization perspective:
- Always align RACH timing with RTT
- Avoid terrestrial parameter reuse
- Use GNSS assisted timing where possible
- Continuously monitor:
- Access delay
- RACH retries
- Success probability
Real world insight:
- Many NTN RACH issues come from improper initial configuration, not RF limitations
13. Key Takeaways
- RACH is highly sensitive to timing and delay in NTN
- Each failure stage maps to a specific root cause
- RTT aware configuration is mandatory
- Beam edge conditions significantly impact access success