### 5G Accessibility KPIs: Comprehensive Monitoring Guide

(Key metrics to measure how easily users can connect to 5G networks)

---

#### � 1. Critical 5G Accessibility KPIs

These metrics determine if users can successfully attach, establish sessions,
and maintain basic access to 5G services.

| KPI Category | Formula | Target | Measurement |

|--------------------------|--------------------------------------------------|-------------|----------
-------|
| RRC Setup Success Rate | `(Successful RRC Connections / Attempts) × 100` | >
99% | Per gNodeB |
| NGSIG (5G Signaling) Success Rate | `(Successful NGAP Initial UE Msgs /
Attempts) × 100` | > 99.5% | Per AMF |
| PDU Session Establishment Success Rate | `(Successful PDU Sessions /
Attempts) × 100` | > 99% | Per SMF |
| Initial Access Delay (ms) | Time from PRACH to RRC Complete |<
50ms | UE-level probe |
| Cell Availability (%) | `(Time Cell is Operational / Total Time) × 100` | >
99.95% | Per cell |

---

#### � 2. Root Cause Analysis (RCA) for Poor Accessibility

If KPI Degrades�→�Check�These:
| KPI Issue | Possible Causes | Troubleshooting Actions |
|------------------------------|---------------------------------------------|-------------------------
----|
| Low RRC Success Rate | - High interference <br> - PRACH misconfiguration
<br> - gNB overload | 1. Adjust `prach-ConfigIndex` <br> 2. Check
`ulSinrThreshold` <br> 3. Scale gNB capacity |
| NGAP Failures | - AMF overload <br> - SCTP congestion <br> - PLMN
mismatch | 1. Monitor AMF CPU <br> 2. Check `n2Interface` QoS <br> 3. Verify
`plmnList` |
| PDU Session Failures | - UPF resource exhaustion <br> - DNN
misconfiguration <br> - SMF policy errors | 1. Check UPF load <br> 2. Validate
`dnnConfig` <br> 3. Review `smfPolicy` logs |
| High Access Delay | - SSB beam misalignment <br> - RACH contention
<br> - Core network latency | 1. Optimize `ssbPeriodicity` <br> 2. Adjust
`preambleReceivedTargetPower` <br> 3. Trace N2/N4 latency |

---

#### � 3. Nokia-Specific Optimization

CloudBand/AMF Tuning:
```bash
# Reduce AMF registration load (Nokia CLI)
amf-config --set t3512=1800 --set maxUePerAmf=100000
```
AirScale gNB Tuning:
```bash
# Improve RACH success (Nokia gNB CLI)
set rach-config prach-ConfigIndex=16, preambleReceivedTargetPower=-100
```
---

#### � 4. Advanced Accessibility Metrics

| KPI | Use Case | Formula |
|-----------------------------|-------------------------------|----------------------------------------
--|
| Emergency Service Accessibility | URLLC compliance | `(Successful
Emergency PDU Sessions / Attempts) × 100` |
| Slice-Specific Accessibility | Network slicing SLA | `(Successful Slice-Specific
Sessions / Attempts) × 100` |
| Dual-Connectivity (EN-DC) Success Rate | LTE-5G interworking | `(Successful
EN-DC Additions / Attempts) × 100` |

---

#### � 5. Real-World Benchmarking

| Scenario | Good | Poor |
|----------------------------|----------------|----------------|
| Urban Macro (Sub-6GHz) | RRC SR > 99.2% | RRC SR < 98% |
| mmWave Stadium | PDU SR > 98.5% | PDU SR < 95% |
| Industrial IoT (URLLC) | Access Delay < 20ms | Delay > 50ms |

---

#### � 6. Pro Tips for Operators

✅ Automate KPI Monitoring: Use Nokia NetAct PM Counter alerts
✅ Correlate Access Failures: Map RRC drops to specific SSB beams
✅ Prevent Signaling Storms: Set AMF rate limits (`maxRegistrationsPerSecond`)

---

### � Conclusion
5G accessibility hinges on RRC, NGAP, and PDU session success rates. Use this
KPI framework to:
1) Detect issues in real-time
2) Diagnose root causes
3) Optimize with vendor-specific tuning

### 5G Accessibility KPIs: Comprehensive Guide

Accessibility KPIs measure how easily users can connect to the 5G network.
Below are the critical KPIs, formulas, targets, and optimization strategies.

---

## � 1. Key 5G Accessibility KPIs

| KPI | Formula | Target | Measurement |

|----------------------------------|------------|------------|----------------|
| RRC Setup Success Rate | `(Successful RRC Connections / Attempted RRC
Connections) × 100` | > 99% | Per gNB, per hour |
| NG Setup Success Rate | `(Successful NG Connections / Attempted NG
Connections) × 100` | > 99.5% | Between gNB and AMF |
| 5G Registration Success Rate | `(Successful UE Registrations / Attempted
Registrations) × 100` | > 99% | Per AMF |
| PDU Session Establishment Success Rate | `(Successful PDU Sessions /
Attempted PDU Sessions) × 100` | > 98.5% | Per SMF |
| Initial Access Success Rate | `(Successful Initial Access Attempts / Total
Attempts) × 100` | > 98% | Per cell |

---

## � 2. Root Causes of Poor Accessibility

| KPI Degradation | Possible Causes | Troubleshooting Actions |
|----------------------------------|---------------------|-----------------------------|
| Low RRC Setup Success | - High UE load <br> - PRACH misconfiguration
<br> - Radio interference | - Adjust `prach-ConfigIndex` <br> - Check
`ssbPeriodicity` |
| NG Setup Failures | - AMF overload <br> - Transport network issues | -
Scale AMF capacity <br> - Check N2 interface |
| Registration Failures | - Authentication issues <br> - UE capability
mismatch | - Verify `5G-AKA` config <br> - Check `SUPI` mapping |
| PDU Session Failures | - SMF/UPF congestion <br> - QoS policy mismatch
| - Monitor SMF CPU <br> - Verify `5QI` mapping |

---

## � 3. Optimization Strategies

### A. Radio Access Optimization

1. PRACH Configuration
- Parameter: `prach-ConfigurationIndex`
- Optimal Value: `16` (for 30kHz SCS)
 - Command (Nokia):
```bash
MOD PRACH: CONFIGINDEX=16;
```

2. SSB Beam Alignment

- Ensure `ssbPeriodicity=20ms` for better initial access.

3. RACH Power Control

- Adjust `preambleReceivedTargetPower` (e.g., `-100 dBm`).

### B. Core Network Optimization

1. AMF Load Balancing
- Deploy AMF pooling and N2 load balancing.
- CloudBand Command:
```bash
amf-pool --add amf1,amf2 --strategy=round_robin;
```

2. SMF Session Management

- Set optimal `t3580` (PDU Session Timer = `10s`).
- Nokia CLI:
```bash
smf-config --set t3580=10;
```
3. QoS Policy Alignment
- Ensure `5QI` mappings match UE capabilities.

---

## � 4. Monitoring & Reporting

### A. Real-Time Dashboards
- Nokia NetAct →�Track `RRC Success Rate`, `NG Setup Drops`.
- CloudBand Analytics →�Monitor�`PDU�Session�Failures`.��

### B. Key Alerts

| Alert Condition | Severity | Action |
|--------------------------------|--------------|------------|
| RRC Success < 98% | Critical | Check PRACH & interference |
| NG Setup Failures > 0.5% | Major | Verify AMF health |
| PDU Session Drops > 1.5% | Minor | Review SMF logs |

---

## � 5. 5G Accessibility Targets (3GPP Standards)

| KPI | Excellent | Acceptable | Poor |
|----------------------------------|---------------|----------------|----------|
| RRC Setup Success Rate | > 99.5% | 98 - 99.5% | < 98% |
| PDU Session Success Rate | > 99% | 97 - 99% | < 97% |
| Initial Access Success Rate | > 98.5% | 95 - 98.5% | < 95% |
---

## � Pro Tips for Operators

✅ Use SON (Self-Organizing Networks) for auto-optimization of PRACH and
RRC.
✅ Enable AMF Redundancy to avoid single-point failures.
✅ Regularly Audit QoS Policies to prevent PDU session drops.

---

### � Conclusion
5G accessibility KPIs are critical for first-time-right connectivity. Optimize RRC,
NG setup, and PDU sessions using these parameters.
### 5G SA vs NSA Accessibility: Key Differences

The accessibility performance of 5G Standalone (SA) and Non-Standalone

(NSA) networks varies significantly due to differences in architecture, signaling,
and core dependencies. Below is a detailed comparison of critical accessibility
KPIs and optimization strategies.

---

## � 1. Architectural Differences Impacting Accessibility

| Feature | 5G SA | 5G NSA (EN-DC) |

|---------------------------|------------------------------------|-----------------------------------|
| Core Network | 5GC (AMF, SMF, UPF) | EPC (MME, S-GW) + 5G
gNB |
| Control Plane | Pure 5G (N1/N2 interfaces) | LTE eNB as anchor (N2
to 5GC) |
| Initial Access | Direct 5G RACH & Registration | LTE RRC + 5G
Secondary Cell Add |
| Dependency | Independent of LTE | Requires LTE anchor
(Coverage critical) |

---

## � 2. Accessibility KPI Comparison

| KPI | 5G SA (Target) | 5G NSA (Target) | Reason for Difference |

|----------------------------|--------------------|---------------------|--------------------------|
| RRC Setup Success Rate | > 99.5% | > 99% | SA uses pure 5G
RACH; NSA relies on LTE anchor stability |
| Registration Success Rate | > 99% (to AMF) | N/A (EPC handles) | SA
requires 5G-AKA; NSA uses LTE auth |
| PDU Session Success Rate | > 99% | > 98% | SA has simpler
SMF-UPF path; NSA involves EPC/5GC interworking |
| Handover Success Rate | > 99% (Xn/N2) | > 98% (LTE-to-NR) | SA has
native 5G HO; NSA requires dual connectivity |
| Call Setup Time | < 100ms | < 150ms | SA avoids LTE-5G
signaling coordination |

---

## � 3. Key Challenges & Fixes

### A. 5G SA Accessibility Issues

1. Problem: AMF Overload (Due to direct 5G registrations)
- Fix: Scale AMF pools + enable N2 load balancing.

2. Problem: PDU Session Failures (SMF/UPF misconfiguration)

- Fix: Verify `5QI` mappings + UPF `N4` interface health.

3. Problem: Beam Failure (mmWave)

- Fix: Optimize `ssbPeriodicity` (20ms) + `beamFailureRecoveryConfig`.

### B. 5G NSA Accessibility Issues

1. Problem: LTE Anchor Dependency (No 5G without LTE coverage)
- Fix: Ensure LTE-NR co-location + `endcHighMob` config.

2. Problem: Secondary Cell (SCG) Addition Failures

- Fix: Adjust `A2/A4 thresholds` + `scgFailureInfo` timers.

3. Problem: Dual-Registration Conflicts

- Fix: Align `t3502` (LTE TAU) with 5G registration timers.

---

## � 4. Optimization Strategies

### For 5G SA:

✅ AMF Redundancy: Deploy multiple AMFs in a pool.
✅ URLLC Slicing: Use `5QI 80/82` for critical services.
✅ Fast RACH: Configure `prach-ConfigIndex=16` (30kHz SCS).

Nokia SA Tuning Example:

```bash
# Set aggressive HO params for SA mobility
MOD NRCELL: ID=1, A3OFFSET=2dB, TTT=160ms;
```

### For 5G NSA:

✅ LTE Anchor Optimization: Tune�`A2`�(LTE→NR�threshold�=�-110 dBm).
✅ EN-DC Scheduler: Prioritize `SCG_Addition` over legacy LTE traffic.
✅ X2 Interface Health: Monitor `SgNB_Add_Req` success rate.

Nokia NSA Tuning Example:

```bash
# Optimize EN-DC thresholds
MOD LTECELL: ID=1, A2THRESH=-110dBm, A4THRESH=-105dBm;
```

---

## � 5. Real-World Performance Comparison

| Scenario | 5G SA | 5G NSA |
|-----------------------|----------|----------|
| Rural Coverage | ✅ (Needs dense gNBs) | ✅�(LTE�anchor�helps)�|��
| Urban Latency | ✅ (1-5ms) | ✅�(10-20ms due to LTE) |
| VoNR Call Success | ✅ (>99%) | ✅�(Depends�on�EPS�fallback)�|��

---

## � Conclusion
- 5G SA offers better latency & signaling efficiency but requires full 5G
coverage.
- 5G NSA leverages LTE for wider accessibility but suffers from dual-
connectivity complexity.

Need more? Ask about:

- SA/NSA interworking strategies
- Best thresholds for EN-DC mobility
- AMF/SMF tuning for massive IoT

This is real-deployment knowledge – test adjustments in a lab first! �