Hard Blocking – LTE RAN

-Measurement & Mitigation

NPO RAN
V1.1 – Jan 2017
 Hard Blocking

Method of
Measurement

Resolution Workflow
& RACI

Reports & Templates

Point of Contact in
NPO-RAN NHQ
 Hard Blocking Measurement
-Counter Detail & Mitigation Responsibility
Sl Category Measurement Counters Criteria Remarks

Avg Daily Hard Blocking Event Under the Given Category >100
1 PRACH Congestion (Handover) DedicatedPreamblesAssignFail
for (3/7 days& Prevailing the Previous Day of Report day)

Avg Daily Hard Blocking Event Under the Given Category >100
2 PUCCH -CQI,ACK,NACK Blocking CC 371
for (3/7 days&Prevailing the Previous Day of Report day)

Avg Daily Hard Blocking Event Under the Given Category >100
3 RRC Blocking CC 367
for (3/7 days&Prevailing the Previous Day of Report day)

(ErabInitFailNbr_CP_BH_CAC_FAIL OR ErabInitFailNbr_CP_CAPA_CAC_FAIL
OR ErabInitFailNbr_CP_QOS_CAC_FAIL OR
ErabAddFailNbr_CP_BH_CAC_FAIL OR ErabAddFailNbr_CP_CAPA_CAC_FAIL Avg Daily Hard Blocking Event Under the Given Category >0
4 ERAB-Volte & Video Blocking To be selected for QCI 1,2 & 5
OR ErabAddFailNbr_CP_QOS_CAC_FAIL OR for(3/7 days &Prevailing the Previous Day of Report day)
ModQoSFailNbr_CP_BH_CAC_FAIL OR ModQoSFailNbr_CP_CAPA_CAC_FAIL
OR ModQoSFailNbr_CP_QOS_CAC_FAIL)>0

(ErabInitFailNbr_CP_BH_CAC_FAIL OR ErabInitFailNbr_CP_CAPA_CAC_FAIL
OR ErabInitFailNbr_CP_QOS_CAC_FAIL OR
ErabAddFailNbr_CP_BH_CAC_FAIL OR ErabAddFailNbr_CP_CAPA_CAC_FAIL Avg Daily Hard Blocking Event Under the Given Category >0 for
5 ERAB- H S I Blocking To be selected for QCI 9
OR ErabAddFailNbr_CP_QOS_CAC_FAIL OR (3/7 days&Prevailing the Previous Day of Report day)
ModQoSFailNbr_CP_BH_CAC_FAIL OR ModQoSFailNbr_CP_CAPA_CAC_FAIL
OR ModQoSFailNbr_CP_QOS_CAC_FAIL)>0

Avg Daily Hard Blocking Event Under the Given Category >200
6 Paging Denied Denied_Paging
for(3/7 days &Prevailing the Previous Day of Report day)

Avg Daily Hard Blocking Event Under the Given Category >0 for
7 Handover in Blocking (CC 010c or CC 020c)
(3/7 days &Prevailing the Previous Day of Report day)

Avg Daily Hard Blocking Event Under the Given Category >0 for
8 Load Balancing HO IN Blocking CC 378
(3/7 days &Prevailing the Previous Day of Report day)
 Measurement and Actions work flow (1/3)

Sr.
Category Measurement Resolution Workflow RACI
No.
a. if RRC Blocking>0 then first need to resolve RRC blocking (Refer RRC Blocking action)
b. if RRC Blocking>0 & Handover IN Blocking>0 then first need to resolve HO IN Blocking (Refer
A-NPO NHQ
RACH DedicatedPreamblesAssig Handover IN Blocking action)
R-SHQ,NOC-CM
1. Congestion nFail c. If RRC Blocking=0 & Handover IN Blocking=0 then increase PRACH dedicated preamble
C-Samsung
(handover) (NUMBER_OF_RAPREAMBLES from n56 to n44, SIZE_OF_RAPREAMBLES_GROUP_A from n28 to n24)
I-NPE NHQ
PRACH Optimization SON feature is in trial. Post trial, increase/decrease of dedicated preamble will
be controlled by feature.

Change START_STATE_IDX parameter

If 0, change to 1 A-NPO NHQ
PUCCH - 1, change to 2 R-SHQ,NOC-CM
2. CQI,ACK,NAC CC 371 2, change to 3 C-Samsung
K Blocking 3, change to 4 I-NPE NHQ
In Phase 2 guideline, decreasing START_STATE_IDX
Parameter from 43210 based on utilization will be circulated.

a. if RRC Blocking>0 & Handover IN Blocking>0 then first need to resolve HO IN Blocking (Refer
Handover IN Blocking action)
b. Availability,sleeping,alarms need to resolved for serving and it’s top 10 NB cells if observed.
c. Tilt of 850>1800>2300 for optimal load balancing.
d. If RRC connected users of all 3 bands of cell reaching 90% of MAX_CALL_COUNT, cell to be
A-NPE NHQ/SHQ
considered for capacity solution (point b,c to be resolved first before concluding point d)
R-SHQ,NOC-CM,NPO-NHQ
RRC Blocking e. If RRC connected users of any 2 bands of cell reaching 90% of MAX_CALL_COUNT & other band RRC
3. CC367 C-Samsung
connected users>70% of MAX_CALL_COUNT, cell to be considered for capacity solution (point b,c to
I-NPO NHQ
be resolved first before concluding point e)
f. If 2300 (only/or/and) 1800 band CAC failures: Change Idle mode parameter settings to balance load
between carriers.
g. If 850 (only/or/and) 1800,2300 band CAC failures: Identify nearest 850 band less RRC connected
user cell and change CIO to balance load between carriers.
In Phase 2 guideline, changing CALL_CAC_THRESH_FOR_NORMAL from 90 to 98 will be circulated.
 Measurement and Actions work flow (2/3)

Sr.
Category Measurement Resolution Workflow RACI
No.

ErabInitFailNbr_CP_BH_CAC_FAIL OR a. Availability,sleeping,alarms need to

ErabInitFailNbr_CP_CAPA_CAC_FAIL OR resolved for serving and it’s top 10 NB
ErabInitFailNbr_CP_QOS_CAC_FAIL OR cells if observed.
A-NPO NHQ
ErabAddFailNbr_CP_BH_CAC_FAIL OR b. Tilt of 850>1800>2300 for optimal
R-SHQ,NOC-CM
ERAB-Volte & Video ErabAddFailNbr_CP_CAPA_CAC_FAIL OR load balancing.
4 C-Samsung
Blocking ErabAddFailNbr_CP_QOS_CAC_FAIL OR c. Change
I-NPE NHQ
ModQoSFailNbr_CP_BH_CAC_FAIL OR DRB_CAC_THRESH_FOR_NORMAL
ModQoSFailNbr_CP_CAPA_CAC_FAIL OR from 90 to 98
ModQoSFailNbr_CP_QOS_CAC_FAIL)>0 d. Change GBR Dedicated mode
(For QC! 1,2,5) parameters for load balancing.

(ErabInitFailNbr_CP_BH_CAC_FAIL OR a. Availability,sleeping,alarms need to

ErabInitFailNbr_CP_CAPA_CAC_FAIL OR resolved for serving and it’s top 10 NB
ErabInitFailNbr_CP_QOS_CAC_FAIL OR cells if observed.
A-NPO NHQ
ERAB- H S I Blocking ErabAddFailNbr_CP_BH_CAC_FAIL OR b. Tilt of 850>1800>2300 for optimal
R-SHQ,NOC-CM
ErabAddFailNbr_CP_CAPA_CAC_FAIL OR load balancing.
5 C-Samsung
ErabAddFailNbr_CP_QOS_CAC_FAIL OR c. Change
I-NPE NHQ
ModQoSFailNbr_CP_BH_CAC_FAIL OR DRB_CAC_THRESH_FOR_NORMAL
ModQoSFailNbr_CP_CAPA_CAC_FAIL OR from 90 to 98
ModQoSFailNbr_CP_QOS_CAC_FAIL)>0 d. Change NBR Dedicated mode
(For QC! 9) parameters for load balancing.

A-NPE CORE-NHQ
a. Change of paging strategy R-NPO RAN NHQ,NPE NHQ
Paging Denied Denied_Paging
6 b. TAC Splitting(Methodology Under C-Samsung
Trial) I-NPE NHQ
 Measurement and Actions work flow (3/3)

Sr. No. Category Measurement Resolution Workflow RACI

a. Availability,sleeping,alarms need to resolved

for serving and it’s top 10 NB cells if observed.
b. Tilt of 850>1800>2300 for optimal load
balancing.
c. Change CALL_CAC_THRESH_FOR_HO from 90 A-NPO NHQ
to 98. R-SHQ,NOC-CM
Handover in Blocking (CC 010c or CC 020c)
7 d. Identify top 2 NB contributing highest HO C-Samsung
attempt to this source cell. Decrease CIO to I-NPE NHQ
make this relationship less favorable. Increase
CIO to other NB where less RRC connected
users are present to make these cells more
favorable for HO.

a. Availability,sleeping,alarms need to resolved

for serving and it’s top 10 NB cells if observed.
b. Tilt of 850>1800>2300 for optimal load
Load Balancing HO IN balancing.
A-NPO NHQ
Blocking c. Change CALL_CAC_THRESH_FOR_HO from 90
R-SHQ,NOC-CM
CC 378 to 98.
8 C-Samsung
d. Identify top 2 NB contributing highest HO
I-NPE NHQ
attempt to this source cell. Decrease CIO to
make this relationship less favorable. Increase
CIO to other NB where less RRC connected
users are present to make these cells more
favorable for HO.
 Mycom template path
/everybody/Hard_Blocking_R4G_State_Band.rpt

Path In Mycom
/everybody/Hard_Blocking_R4
G_State_Band.rpt

Path In Mycom
/everybody/Hard_Blocking_Cel
lwise_Scope.rpt
 NPO-RAN Point of Contact
-Hard Blocking

L2 Support L3 Support & Zonal Query and Escalation Direction &

Capacity Management Support
Managemenet
Arnab
Joita North
Mukherjee
Bhattacharya
East Onkar Jha Rajib
Lohith G Chakrabarti
Avik Modak South Roopal Bagree

West Chirag Joshi

Thank You