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 Yes Yes
(High 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 Yes Yes

uplink synchronization
Uplink data transfer requiring uplink Yes
synchronization
Uplink data transfer without Yes
dedicated 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.pmRaAtt pmRaAllocCfra The number of allocated CFRA preambles in the cell.
Cbra) pmRaUnassignedCfraFalse The number of detected CFRA preambles that are not allocated to any UE.
pmRaUnassignedCfraSum The total number of unassigned CFRA preambles at each PRACH activity.
The number of CBRA preambles for which no random access response (RA Msg2) was sent due to expiry of the random access
LTE_CFRA_Success_Rate = pmRaFailCbraMsg2Disc response window.
2019-07-03 |
100*(EUtranCellFDD.pmRaSuccCfra/EUtranCellFDD.pmRaAtt The number of CFRA preambles for which no random access response (RA Msg2) was sent due to expiry of the random access
pmRaFailCfraMsg2Disc response window.
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

› Therefore, neighboring
Cell Range
cells RSI should differ by
— feature is enabled 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 Based on 3GPP 36.211
reduce the probability for false RACH detections
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
— Poor RF condition; CBRA/CFRA planning
— Sleeping cell; Possible  Poor RF Condition
 SW Bugs
— SW Bugs Reason  Other reason
— Other reason (e.g. intermittent transport problem)
• Hygiene check • Lock unlock cells • Hygiene Check and
• Solved No contact issue • Cold restart troubleshooting on site if
— Solutions: • Counter activation check • Clear synchronization necessary, regarding
— Network hygiene is the most important factor for all Solution issue. • ASM
“ M Loss of Sync over CPRI • TxRank2
services, including Random Access. Need to follow Connections 
Synchronization=1,NodeGroupSyncM • Active Alarm
up any issue related to Active alarm, VSWR, ASM, ember=1 • VSWR
TxRank2, UL RSSI etc to TS team. (clock_synchronisation_problem)”
• Parameter baseline concheck
— For improper Radio optimization parameter, initial • Basic parameter concheck
tuning team need to follow standard Layering • Layering concheck
parameter guideline; • Eutranrelation concheck
• Rach Optimization
— For current cell range setting (15km), the parameter
• RachRootSequence
rachRootSequence should differ at least 10 between • cellRange
any two neighbors to avoid collision; • preambleInitialReceivedTarg
— Check for poor RF conditions. Increase the coverage etPower
area by adjusting Tilt/Azimuths of self/neighbor sites • Physical Tuning
and avoid overlapped or overshooting coverage; • Upgrade to new SW patch
• Clear transport problem issue
— Upgrade to the newest software patch that available
in the 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
2019-07-03
cells handover that experience bad Random Access
 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 prachConfiguration collision was observed, so there might be high risk of
cell EJD961B, started from 2018-05-26 21:45:00 false CBRA Msg1 detection among cells, and which might lead to
 But counter pmRaSuccCbra did not show obvious pmRaAttCbra Abnormal Stepping Issue.
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.
2019-07-03 |
— If PRACH configuration collision was observed, please contact Planning
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- 100 Counter activation
L_RADIO_COUNTERS_L17.Cont.Y.STATS 90
80
— For DUS Site  USERDEF-L_RADIO_COUNTERS_L17.Cont.Y.STATS 70
60
50
Counter Description 40
30
pmRaAttCbra The number of detected CBRA preambles in the cell. 20
10
pmRaSuccCbr The number of successfully detected RA Message 3 for 0 NULL
a CBRA. 0 19 0 19 0 19 0 19 0 19 0 19 0 19 0 19 9 9 9 9 9
0 1 2 0 1 2 0 1 2 0 1 2 01 2 0 1
9
/2 /2 /2 /2 /2 /2 /2 /2 1/
2
2/ 3/ 4/ 5/ 6/
Before – USERDEF scanner not yet defined 23 /24 /25 /26 /27 /28 /29 /30 7/ 7/ 7/ 7/ 7/ 7/
6/ 6 6 6 6 6 6 6

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
• Found some new L21 sites with Sync Alarm Cold Restart

• Impact to CBRA degradation

Alarm
ERBS Layer Alarm (Cause)
clearance
“ M Loss of Sync over CPRI
Connections 
Sync OK, Cold
Synchronization=1,NodeGrou
4435131E 2100 restart after
pSyncMember=1
TS
(clock_synchronisation_probl
em)”
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
Antenna System Monitoring (ASM) indicates the following problem
problems related to the antenna system: • It is recommended if
• Mismatched antenna pair Rx diagrams X
• Swapped or disconnected feeders any ASM issue persist ,
• Loss in RF path
• Missing feeder need to check and
troubleshooting 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
• CBRA Success Rate cells tend to improved; thus TxRank2
4451812E - Average of CB Random Access Success Rate
is tend to improved also 4451812E - Average of Txrank2
2019-07-03 |
Low CBRA SR due to ASM “Mismatch Antenna” –
2T2R
Background:
• Found ASM Issue “Mismatch Antenna” Impact to CBRA
date_id
6/9/2019
6/9/2019
ERBS
MC4451487E
MC4451487E
SectorCar
rier
1
2
Mean0
0.803429
1.248112
StD0
7.374661
7.213307
Remark0
Normal
Normal
ASM Before

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

• 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
• Found Overshooting issue and RET not working-well
TA After
• Thus impact to Overshooting and Low CBRA
— RET need calibration

— Low TxRank2
CBRA Improvement
CBRA SR vs TxRank2
100
90
80
70
60
50
40
30

Solution:
20
10
0
• Suspect due to mismatch RET configuration/need calibration JK4G18_441PC371E_24 - Average of CB Random Access Success Rate
JK4G18_441PC371E_24 - Average of tx_rank2

• On site Tshoot
• RET calibration and correction set to Y4

Result:
• CBRA Success Rate cells tend to improved

2019-07-03 |
Low CBRA due to Impoper Layering parameter
(Network Roll-Out PY2018)
CBRA Success Rate
Site On Air concheck L2100
120
Background: 100
After Inject License

• Found new site, on air with low CBRA, while hygiene 80

check already PASS 60

40

20

Solution: 0
JK4G18_441PC175E_14 JK4G18_441PC175E_24

• Layering concheck L2100

• Lock unlock after execution
Result:
• CBRA Success Rate and Accessibility cells tend to improved

Accessibility
Site On Air
105 concheck L2100

100
After Inject License
95

90

85

80
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 NCCR211
• Impact to CBRA degradation
old 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
rachRootSequenc First root sequence number for RACH preamble generation.
e 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 consistency check for RSN disc parameter (Part 85

of optimization) 84
• Rach Root Sequence cleanup based on CDR Planning
83
team, to avoid RSN collision.
82
Parameter Description
81
rachRootSequenc First root sequence number for RACH preamble generation.
e RACH root sequence is broadcast as a part of system 80
information distribution and is used for preamble detection.
For information on the definition of logical root sequence 79
number, see 3GPP TS 36.211.
Taking effect depends on the feature state. 78

6/12/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

6/10/2017

6/11/2017

6/13/2017

6/14/2017

6/15/2017
Exists for MO classes:
 EUtranCellFDD.rachRootSequence
 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:
• Found SW Bugs L18.Q2 and W18.Q2 in site with Radio
CBRA Success Rate vs RSSI
120 0
L2100 Mixedmode SW Upgrade from
4443 that connected to DUS/DUW with Radio4443 L18.Q2 to L18.Q4
-20
100

-40
80

-60
60

CBRA SR (%)

RSSI (dBm)
-80

40
-100

20
-120

0 -140
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1: 7: 13: 19: 1 : 7: 13: 19: 1: 7: 1 3: 19 : 1: 8 : 1 4: 20 : 2 : 8 : 1 : 7: 13: 19: 1 : 7:
19 19 9 9 19 19 9 9 19 19 9 9 19 19 9 9 19 19 19 19 9 9 19 19
Solution: / 2 0 / 20 201 201 / 2 0 / 20 2 01 201 / 2 0 / 20 2 01 20 1 / 20 / 2 0 20 1 20 1 / 2 0 / 2 0 / 2 0 / 20 2 01 201 / 2 0 / 20
19 20 1/ 2/ 24 25 6/ 7/ 29 30 1/ 2/ 7/ 4 7/5 /6/ / 7/ 7/9 / 10 / 13 /14 15/ 16/ / 18 /19
• Overall performance (include ASM) improved after SW Update to 6/ 6/ 6/2 6/2 6/ 6/ 6/ 2 6/2 6/ 6/ 7/ 7/ 7 7 7 7 7 7/ 7/ 7 7

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 |
TS - U2100 Config RBB11_1A with UL Attenuation Ext 17 dB and L2100 MIMO
Impact to CBRA
the following connection is RBB22_1A, if we have to configure it as RBB11_1A on W side , then we should
consider 2nd RUS as part of antenna

Sample at 3G_CIKUPA
 Set ulAttenuation to -170 for EXT

TS taken on Thursday, 26 and 31 July

2018
Result :
 UL RSSI improved with config
U2100 RBB11_1A and L2100


MIMO
Payload and traffic still under
ULRSSI improved
monitoring

2019-07-03 |
ericsson.com