CBRA Optimization

Guideline

July 2019
Introduction
CBRA CFRA
❑ CBRA(Contention Based Random Access)
Initiate access, handover and ue initiated ul resync

❑ CFRA(Contention Free Random Access)

The CFRA can be used for incoming handover and for
PDCCH ordered UL re-synchronization in case of DL data
arrival for a UE that is out-of-sync in UL, i.e. a UE whose
time alignment timer has expired.

RA Senario CBRA CFRA

Initial network access Yes

Access following a radio link failure Yes

Incoming Handover between cells (High Yes Yes

speed ue: PDCCH order for requesting UE
access attempts due to RA failures at their
previous access attempts by using CFRA)

Downlink data transfer requiring uplink Yes Yes

synchronization

Uplink data transfer requiring uplink Yes

synchronization

Uplink data transfer without dedicated Yes

scheduling request resource Counter Description
pmRaAttCbra The number of detected CBRA preambles in the cell.
pmRaSuccCbra The number of successfully detected RA Message 3 for CBRA.
LTE_CBRA_Success_Rate = pmRaAttCfra The number of detected CFRA preambles in the cell.
pmRaSuccCfra The number of successfully detected RA Message 3 for CFRA.
100*(EUtranCellFDD.pmRaSuccCbra/EUtranCellFDD.pmRaAttCbra) pmRaAllocCfra The number of allocated CFRA preambles in the cell.
pmRaUnassignedCfraFalse The number of detected CFRA preambles that are not allocated to any UE.
LTE_CFRA_Success_Rate = pmRaUnassignedCfraSum The total number of unassigned CFRA preambles at each PRACH activity.
pmRaFailCbraMsg2Disc The number of CBRA preambles for which no random access response (RA Msg2) was sent due to expiry of the random access response window.
100*(EUtranCellFDD.pmRaSuccCfra/EUtranCellFDD.pmRaAttCfra) pmRaFailCfraMsg2Disc The number of CFRA preambles for which no random access response (RA Msg2) was sent due to expiry of the random access response window.
2019-07-03 |
Random Access – Cell Range vs RachRootSequence
The value of cellRange decides the preamble format to be used in the
random access procedure;
› Cell Range = 15km → # of
— cellRange  15  preamble format 0
RSI = 10
— cellRange > 15  preamble format 1

› Default RSI =384

– For the particular cell
384,385,
— By Default, cellRange parameter is fixed to 15 km. …….,394 will be used.

— Other cell ranges than 15 km can be set if the Maximum Cell Range
› Therefore, neighboring
— feature is enabled cells RSI should differ by
at least 10, resulting a
reuse of 838 (0 to 837) /
rachRootSequence 10 → 80 “groups”
The first root (Zadoff-Chu) sequence number for Random Access Channel
(RACH) preamble generation. It is broadcasted as a part of system
information distribution and used for preamble detection
The parameter takes the value in the range of 0 to 837 and the default value
is 386. It is recommended to set the parameter rachRootSequence to
different values in neighboring cells to reduce the probability for false RACH
detections Based on 3GPP 36.211

cellRange
Defines the maximum distance from the RBS where a connection to a UE can
be setup or maintained, or both

For a cellrange of 15 km size, the values of rachRootSequence in adjacent cells must differ by at least 10 between any two neighbors (and at most 827 since there is a wrap-around between the first
and last value in the value range) in order to eliminate overlap or collision

2019-07-03 |
Random Access - Optimization
— Possible reasons for RACH failure: CBRA = NULL CBRA = 0% CBRA < 20%
— Hygiene issue
• Availability issue; ▪ Sleeping Cells ▪ Hygiene issue
— Improper Radio optimization parameter • No contact; Synchronization issue
▪ ▪ Improper Radio parameter
— Improper RA preamble planning; • Counter not yet activated ▪ Sudden degradation of ▪ Improper RA preamble planning
— Poor RF condition; CBRA/CFRA ▪ Poor RF Condition
— Sleeping cell; Possible ▪ SW Bugs
▪ Other reason
— SW Bugs Reason
— Other reason (e.g. intermittent transport problem)
• Hygiene check • Lock unlock cells • Hygiene Check and troubleshooting
• Solved No contact issue • Cold restart on site if necessary, regarding
— Solutions: • Counter activation check • Clear synchronization issue. • ASM
“ M Loss of Sync over CPRI • TxRank2
— Network hygiene is the most important factor for all services, Solution Connections Synchronization=1,NodeGrou
including Random Access. Need to follow up any issue related pSyncMember=1 • Active Alarm
(clock_synchronisation_problem)” • VSWR
to Active alarm, VSWR, ASM, TxRank2, UL RSSI etc to TS team.
• Parameter baseline concheck
— For improper Radio optimization parameter, initial tuning team • Basic parameter concheck
need to follow standard Layering parameter guideline; • Layering concheck
— For current cell range setting (15km), the parameter • Eutranrelation concheck
rachRootSequence should differ at least 10 between any two • Rach Optimization
• RachRootSequence
neighbors to avoid collision;
• cellRange
— Check for poor RF conditions. Increase the coverage area by • preambleInitialReceivedTargetP
adjusting Tilt/Azimuths of self/neighbor sites and avoid ower
overlapped or overshooting coverage; • Physical Tuning
— Upgrade to the newest software patch that available in the • Upgrade to new SW patch
• Clear transport problem issue
network;
— Sleeping cell is hard to detect. When there are many RA
attempt, but none successes (high pmRaFailCbraMsg2Disc),
the cell is considered a sleeping one. Try to lock/unlock the cell,
or cold restart;
— Clear issue transport problem for both source/target cells
handover that experience bad Random Access

2019-07-03 |
 Optimization Sample Cases

2019-07-03 |
CellRange and RachRootSequence Relation on CBRA Case
Background: Analysis
▪ Sharp raising of pmRaAttCbra was observed in a sudden in cell prachConfiguration collision was observed, so there might be high risk of false CBRA Msg1
EJD961B, started from 2018-05-26 21:45:00 detection among cells, and which might lead to pmRaAttCbra Abnormal Stepping Issue.
▪ But counter pmRaSuccCbra did not show obvious degradation before
and after sharp raising of pmRaAttCbra;

Way Forward:
— If pmRaAttCbra Abnormal Stepping Issue was observed with
— No obvious abnormal behavior was observed for counter ” pmRaSuccCbra”,
”pmRaAttCfra”, and ”pmRaSuccCfra”
— No obvious abnormal behavior was observed for UL interfernce counters
— No obvious abnormal behavior was observed for other KPI/PI measurements
— Please collect cell information with template in previous table within at least 15 km cell
range of current cell with issue observed.
— If PRACH configuration collision was observed, please contact Planning team first for
more suggestions
2019-07-03 |
CBRA_SR = NULL due to counter not yet activated
In XL OSS, CBRA counters are include in USERDEF counter, need to activate below
pmJobs/Scanner to measure CBRA : CBRA Success Rate
— For BB Site → PmJob=USERDEF-L_RADIO_COUNTERS_L17.Cont.Y.STATS 100 Counter activation
— For DUS Site → USERDEF-L_RADIO_COUNTERS_L17.Cont.Y.STATS 90
80
70
60
50
Counter Description 40
30
pmRaAttCbra The number of detected CBRA preambles in the cell. 20
pmRaSuccCbra The number of successfully detected RA Message 3 for CBRA. 10
0
NULL

Before – USERDEF scanner not yet defined

X3472391G_CO

time object LTE_UL_RSSI_Pwr_dBm LTE_pmRaSuccCbra_SR

6/23/2019 X3472391G_CO NaN !NULL!
6/24/2019 X3472391G_CO NaN !NULL!
6/25/2019 X3472391G_CO NaN !NULL!
6/26/2019 X3472391G_CO NaN !NULL!
6/27/2019 X3472391G_CO -111.15 77.40
6/28/2019 X3472391G_CO -111.95 73.96
6/29/2019 X3472391G_CO -111.72 76.17
After – USERDEF scanner defined on 27 June 2019
6/30/2019 X3472391G_CO -110.71 86.07
7/1/2019 X3472391G_CO -111.28 83.10
7/2/2019 X3472391G_CO -107.62 73.22
7/3/2019 X3472391G_CO -105.78 66.11
7/4/2019 X3472391G_CO -105.86 75.59
7/5/2019 X3472391G_CO -105.46 73.11
7/6/2019 X3472391G_CO -104.81 69.95

2019-07-03 |
CBRA SR = 0 – Clock Sync alarm solved after clear NGS issue
and cold restart
Background: Alarm Clearance
Cold Restart
• Found some new L21 sites with Sync Alarm
• Impact to CBRA degradation

ERBS Layer Alarm (Cause) Alarm clearance

“ M Loss of Sync over CPRI

Connections Synchronization=1,N Sync OK, Cold
4435131E 2100
odeGroupSyncMember=1 restart after TS
(clock_synchronisation_problem)”

Solution:
• Clock Sync Alarm clearance, NGS alarm at 3G node
• Cold restart after execution
Result:
• CBRA Success Rate cells tend to improved

2019-07-03 |
CBRA and Antenna System Monitoring (ASM) 1. disconnected 2. RF loss

— Refer to counter pmBranchDeltaSinrDistr (LTE)

— Detection Bad ASM indicated from this counter calculation • SIR/SINR difference
std dev and Avg delta SINR indicates potential problem
Antenna System Monitoring (ASM) indicates the following • It is recommended if any
problems related to the antenna system: ASM issue persist , need to
• Mismatched antenna pair Rx diagrams X
• Swapped or disconnected feeders check and troubleshooting
• Loss in RF path
• Missing feeder on site

3. Mismatched antennas

4. Swapped antennas

2019-07-03 |
Low CBRA SR due to ASM with remark “Partial Swap Feeder”
Background:
• Found ASM Issue “Partial swap feeder” at
LTE_DIPONEGORO_JATIMULYA, Impact to CBRA degradation
ASM BEFORE ASM AFTER
Solution:
• Clear ASM and TxRank2 issue by
• On site Tshoot
• RU-Antenna connection correction

Connection Before Connection After

120 Correction
100

80

60 Locked RRU

40

20

Result: 0
0 5 10 15 20 1 6 11 16 21 2 7 12 17 22 3 8 13 18 23 4 9 14 19 0 5 10 15 20 1 6 11 16 21 2 7 12 17 22 3 8 13 18 23 4
• CBRA Success Rate cells tend to improved; thus TxRank2 is tend to 8/27/2018 8/28/2018 8/29/2018 8/30/2018 8/31/2018 9/1/2018 9/2/2018 9/3/2018 9/4/20189/5/2018
improved also 4451812E - Average of CB Random Access Success Rate 4451812E - Average of Txrank2
2019-07-03 |
Low CBRA SR due to ASM “Mismatch Antenna” – 2T2R
date_id ERBS SectorCarrier Mean0 StD0 Remark0
Background: 6/9/2019 MC4451487E 1 0.803429 7.374661 Normal
6/9/2019 MC4451487E 2 1.248112 7.213307 Normal
• Found ASM Issue “Mismatch Antenna” Impact to CBRA 6/9/2019 MC4451487E 3 0.114598 7.517325 Normal
ASM Before
6/9/2019 MC4451487E 4 1.004739 6.830422 Normal

ASM
degradation (2T2R) 6/9/2019 MC4451487E 5 1.475389 7.056444 Normal
6/9/2019 MC4451487E 6 4.284947 8.450536 Antenna diagram mismatch
6/16/2019 MC4451487E 1 0.963841 6.978253 Normal
Solution: 6/16/2019 MC4451487E 2 1.672386 7.203958 Normal
• Clear ASM issue by ASM After
6/16/2019
6/16/2019
MC4451487E
MC4451487E
3
4
1.089405
1.036284
7.83548
6.978314
Normal
Normal
• On site Tshoot 6/16/2019 MC4451487E 5 1.250208 7.083157 Normal
6/16/2019 MC4451487E 6 0.647968 7.209906 Normal
• RU-Antenna connection correction
• Physical or Remote Tilting changes
Result:

Tilting
• CBRA Success Rate cells tend to improved

CBRA Improvement
— CBRA cell_9 improved

2019-07-03 |
Low CBRA SR due to ASM “Mismatch Antenna” – 4T4R
Background:
• Found ASM Issue “Mismatch Antenna” Impact to CBRA
ASM Before

ASM
degradation (4T4R)

Solution:
• Clear ASM issue by ASM After
• On site Tshoot
• RU-Antenna connection correction
• Physical or Remote Tilting changes
Result:

Tilting
• CBRA Success Rate cells tend to improved

CBRA Improvement
— CBRA L2100 improved

2019-07-03 |
Low CBRA SR due to RET not calibrate – Overshooting
Background: TA Before TA After
• Found Overshooting issue and RET not working-well
• Thus impact to Overshooting and Low CBRA
— RET need calibration

— Low TxRank2
CBRA Improvement
CBRA SR vs TxRank2
100
90
80
70
Solution: 60
50
• Suspect due to mismatch RET configuration/need calibration 40
• On site Tshoot 30

• RET calibration and correction set to Y4 20

10
0
Result: 0 3 6 9 12 15 18 21 0 3 6 9 12 15 18 21 0 3 6 9 12 15 18 21 0 3 6 9 12 15 18 21 0 3 6 9 12 15 18 21 0 3 6 9

• CBRA Success Rate cells tend to improved 3/4/2019 3/5/2019 3/6/2019 3/7/2019 3/8/2019 3/9/2019

JK4G18_441PC371E_24 - Average of CB Random Access Success Rate JK4G18_441PC371E_24 - Average of tx_rank2

2019-07-03 |
Low CBRA due to Impoper Layering parameter
(Network Roll-Out PY2018)
CBRA Success Rate
Background: 120 Site On Air concheck L2100
• Found new site, on air with low CBRA, while hygiene check already After Inject License
100
PASS 80
60

Solution: 40

• Layering concheck L2100 20

• Lock unlock after execution 0

0 4 8 12 16 20 0 4 8 12 16 20 0 4 8 12 16 20 0 4 8 12 16 20 0 4 8 12 16 20 0 4

Result: 9/1/2018 9/2/2018 9/3/2018 9/4/2018 9/5/2018 9/6/2018

• CBRA Success Rate and Accessibility cells tend to improved JK4G18_441PC175E_14 JK4G18_441PC175E_24

Accessibility
Site On Air
105 concheck L2100
After Inject License
100

95

90

85

80
0 3 7 1013161922 1 5 8 1114172023 2 6 9 12151821 0 3 7 1013161922 1 5 8 1114172023 2 6
9/1/2018 9/2/2018 9/3/2018 9/4/2018 9/5/2018 9/6/2018

JK4G18_441PC175E_14 JK4G18_441PC175E_24

2019-07-03 |
Low CBRA due to Improper eARFCN
(Network Roll-Out PY2018)
Background:
• Found some new sites ON Air with old eARFCN
New sites with old NCCR211
• Impact to CBRA degradation
earfcn on air

Solution:
• NCCR221_XL_Discrepancy earfcn JABO_Dec2018.

Result:
• CBRA Success Rate cells tend to improved

2019-07-03 |
Low CBRA due to Improper Rach Root Sequence (386)
(Network Roll-Out PY2018)
Background:
• Found L21 cell Rach Root Sequence setting = 386 (Default value)
• Rach Root Sequence cleanup based on CDR Planning team, to
avoid RSN collision.
Parameter Description
rachRootSequence First root sequence number for RACH preamble generation.
RACH root sequence is broadcast as a part of system information
distribution and is used for preamble detection. For information on the
definition of logical root sequence number, see 3GPP TS 36.211.
Taking effect depends on the feature state.
Exists for MO classes:
• EUtranCellFDD.rachRootSequence
• EUtranCellTDD.rachRootSequence

Solution:
• NCCR143_XL_Lte_Concheck_rachRootSequence_20190405.

Result:
• CBRA Success Rate L2100 cells tend to improved

2019-07-03 |
CBRA Improvement after RachRootSequence Optimization
(XL NQI Project 2017)
Background: CBRA Success Rate
• The purpose of RACH Root sequence number clean up is as one of 85

consistency check for RSN disc parameter (Part of optimization) 84

• Rach Root Sequence cleanup based on CDR Planning team, to
avoid RSN collision. 83

82
Parameter Description
81
rachRootSequence First root sequence number for RACH preamble generation.
RACH root sequence is broadcast as a part of system information 80
distribution and is used for preamble detection. For information on the
definition of logical root sequence number, see 3GPP TS 36.211. 79
Taking effect depends on the feature state.
Exists for MO classes: 78
• EUtranCellFDD.rachRootSequence

6/10/2017

6/11/2017

6/12/2017

6/13/2017

6/14/2017

6/15/2017

6/16/2017
6/2/2017

6/3/2017

6/4/2017

6/5/2017

6/6/2017

6/7/2017

6/8/2017

6/9/2017
• EUtranCellTDD.rachRootSequence

Solution:
• NCCR NW_Wide_Rach_Seq_Disc_PARA_20170607

Result:
• CBRA Success Rate tend to improved

2019-07-03 |
Low CBRA on Radio4443 Connected to DUS/DUW – SW Bugs
(XL Orion H2 Program)
Background: CBRA Success Rate vs RSSI
• Found SW Bugs L18.Q2 and W18.Q2 in site with Radio 4443 that 120 -100

connected to DUS/DUW L2100 Mixedmode SW Upgrade from

with Radio4443 -102
L18.Q2 to L18.Q4
100
-104

80 -106

CBRA SR (%)

RSSI (dBm)
-108
60
-110

40 -112

-114
20
-116

0 -118

6/19/2019

6/22/2019

6/25/2019

6/28/2019

7/1/2019

7/4/2019

7/13/2019

7/16/2019

7/19/2019
6/21/2019 6:00

6/24/2019 6:00

6/27/2019 6:00

6/30/2019 6:00

7/1/2019 18:00
7/2/2019 12:00
7/3/2019 6:00

7/4/2019 18:00
7/5/2019 13:00
7/6/2019 7:00
7/7/2019 1:00
7/7/2019 19:00
7/8/2019 13:00
7/9/2019 7:00
7/10/2019 1:00

7/15/2019 6:00

7/18/2019 6:00
6/19/2019 18:00
6/20/2019 12:00

6/22/2019 18:00
6/23/2019 12:00

6/25/2019 18:00
6/26/2019 12:00

6/28/2019 18:00
6/29/2019 12:00

7/10/2019 19:00

7/13/2019 18:00
7/14/2019 12:00

7/16/2019 18:00
7/17/2019 12:00
Solution:
• Overall performance (include ASM) improved after SW Update to
W18Q4.5-1 (3G) and L18.Q4 (LTE)
Average of LTE_pmRaSuccCbra_SR Average of LTE_UL_RSSI_Pwr_dBm
• Cold Restart after Software upgrade
Result:
• CBRA Success Rate tend to improved

2019-07-03 |
ericsson.com