Soft Handover overhead [%]

KPI name
Soft Handover overhead in CIADA
KPI
sho overhead in CIADA
abbreviation
KPI ID
IHSPA_192a
Description
Soft Handover overhead [%] for Controlling IADA over the reporting period.
Measurement
M1007 - Soft Handover I-HSPA (I-HSPA Adapter)
100* (sum([M1007C0] + [M1007C19] + [M1007C1] + [M1007C20] + [M1007C2] +
[M1007C21])
KPI formula
/
sum(([M1007C0] + [M1007C19]) + ([M1007C1] + [M1007C20])/2 + ([M1007C2] +
[M1007C21])/3) - 1)
100* (sum([ONE_CELL_IN_ACT_SET_FOR_RT] +
[ONE_CELL_IN_ACT_SET_FOR_NRT] + [TWO_CELLS_IN_ACT_SET_FOR_RT] +
[TWO_CELLS_IN_ACT_SET_FOR_NRT] + [THREE_CELLS_IN_ACT_SET_RT] +
KPI formula
[THREE_CELLS_IN_ACT_SET_NRT])
with short
/
names
sum(([ONE_CELL_IN_ACT_SET_FOR_RT] + [ONE_CELL_IN_ACT_SET_FOR_NRT]) +
([TWO_CELLS_IN_ACT_SET_FOR_RT] + [TWO_CELLS_IN_ACT_SET_FOR_NRT])/2 +
([THREE_CELLS_IN_ACT_SET_RT] + [THREE_CELLS_IN_ACT_SET_NRT])/3) - 1)
KPI class
Usage/Allocated Capacity
Unit
Percentage
Object Summary
Network, IADA, WCEL
Levels
Time Summary
Total; week; weeklyBH; day; dailyBH; hour
Levels

The following table contains the basic information needed to perform this use case.
ID
RAN_USE_CASE_OPT_002
Use case name
Soft handover analysis and optimization
RAN releases
All RAN releases
Actors
Network planner, operation engineer
Based on cell-to-cell level KPIs, you can identify, profile
Summary
and manually correct sho problems
Triggers for service/resource
KPIs based on mobile reports
information used
Limitations and restrictions
Measurements are not available
Reasons for performing the
Problematic areas were found based on cell-level sho KPIs.
use case
Preconditions
Reliable traffic data is available.
Initial adjacencies have been created and their performance
Postconditions
can be measured.
Table 4:
Use case information
sho analysis and optimization is based on the following counters/KPIs:

Number of sho attempts from cell A to cell B, leading to a dropped call (M1013C0 M1013C1)

Total sho attempts from cell pair (M1013C0)

Average Ec/No difference between cell pair (M1013C2/M1013C3)

Average sho duration ((M1007C6+M1007C8+M1007C25+M1007C26)/(M1007C15+M1007C32))

Period of time where cell A and cell B are in the active set simultaneously (M1007C1 + M1007C20)

Average number of sho attempts from cell pair per call (M1030C0/M802C19)

Total number of radio link failure messages during an sho attempt (M1005C180+M1005C181+M1005C182+M1005C183)

Total time in sho

(sho duration timers - M1007C8+M1007C26+M1007C6+M1007C25
for HSUPA - M1007C66
for HSDPA - M1007C52+M1007C51 (when, after the sho, the UE receives the HS-DSCH))

Total time a cell is in Active Set Size = 1 (M1007C0+M1007C19 (differentiation for RT and NRT bearers))

Soft Handover overhead [%] for One Cell or whole RNC (RNC_192)

Steps
1 Select the threshold for the cell level cost function for cells that are performing well and those that are performing badly.
2 Visualize the cell-level SHO KPIs and identify problematic areas.
3 Visualize the cell-to-cell KPIs further for adjacencies to the problematic cells.
4 Modify the CM data necessary to improve the SHO conditions.
5

Verify and save the changes.

Provision the changes to the network

Soft Handover overhead [%]

KPI name
Soft Handover overhead in CRNC
KPI
sho overhead in CRNC
abbreviation
KPI ID
RNC_192b
Description
Soft Handover overhead [%] for Controlling RNC over the reporting period.
In the sho Measurement the counters are both for RNC and WCELL. This formula is purely using
Note 1
the cell level counters.
The formula will not work properly in border areas. This because that for the DRNC cells in the
Note 2
AS there will not be any counter updates.
Measurement M1007: Soft Handover
100* (sum([M1007C0] + [M1007C19] + [M1007C1] + [M1007C20] + [M1007C2] +
KPI formula
[M1007C21]) / sum(([M1007C0] + [M1007C19]) + ([M1007C1] + [M1007C20])/2 +
([M1007C2] + [M1007C21])/3) - 1)
100* (sum([ONE_CELL_IN_ACT_SET_FOR_RT] + [ONE_CELL_IN_ACT_SET_FOR_NRT]
+ [TWO_CELLS_IN_ACT_SET_FOR_RT] + [TWO_CELLS_IN_ACT_SET_FOR_NRT] +
KPI formula
[THREE_CELLS_IN_ACT_SET_RT] + [THREE_CELLS_IN_ACT_SET_NRT]) /
with short
sum(([ONE_CELL_IN_ACT_SET_FOR_RT] + [ONE_CELL_IN_ACT_SET_FOR_NRT]) +
names
([TWO_CELLS_IN_ACT_SET_FOR_RT] + [TWO_CELLS_IN_ACT_SET_FOR_NRT])/2 +
([THREE_CELLS_IN_ACT_SET_RT] + [THREE_CELLS_IN_ACT_SET_NRT])/3) - 1)
KPI class
Usage/Allocated Capacity
Unit
Percentage
Typical values 40 % (Average AS size = 1.4)
Object
Summary
Network, City, Area, RNC, Cluster of cells, Cell
Levels
Time Summary
Week, Day, Hour
Levels
Table 122:
Soft Handover overhead in CRNC

MBLB
mblbMobilityEnabled (mblb in Mobility Enabled)
Field
RNC mcRNC 2.0
This parameter defines if Multi-Band Load Balancing is
enabled due to mobility in Cell_DCH state. If this
parameter is enabled, Multi-Band Load Balancing is done
Description with handover based on (CM) measurements on Cell_DCH
state.
Changes in the parameter are applied in upcoming
inactivity detected events in Cell_DCH state.
Modificatio
onLine
n

mblbInactivityEnabled (mblb in Inactivity Enabled)

Field
RNC mcRNC 2.0
This parameter defines if Multi-Band Load Balancing is
enabled when inactivity is detected in Cell_DCH state. If
this parameter is enabled, Multi-Band Load Balancing is
done with handover based on (CM) measurements on
Cell_DCH state.
Description Changes in the parameter are applied in upcoming
inactivity detected events in Cell_DCH state.
When this parameter is enabled, HSPA capability based
HO, MIMO capability based HO and DC-HSDPA
capability based HO are not done in case of inactivity
detected in Cell_DCH state.
Modificatio
onLine
n

RNC mcRNC 3.0

This parameter defines if Multi-Band Load Balancing is
enabled due to mobility in Cell_DCH state. If this
parameter is enabled, Multi-Band Load Balancing is done
with handover based on (CM) measurements on Cell_DCH
state.
objectLocking

RNC mcRNC 3.0

This parameter defines if Multi-Band Load Balancing is
enabled when inactivity is detected in Cell_DCH state. If
this parameter is enabled, Multi-Band Load Balancing is
done with handover based on (CM) measurements on
Cell_DCH state.
When this parameter is enabled, HSPA capability based
HO, MIMO capability based HO and DC-HSDPA
capability based HO are not done in case of inactivity
detected in Cell_DCH state.
objectLocking

Multi-Band Load Balancing due to mobility caused mblb guard timer expiration.
Multi-Band Load Balancing triggers handover because of the following reasons:

mblb guard timer expires.

This functionality is enabled in current HS-DSCH serving cell after SRNC relocation with mblbMobilityEnabled parameter. If
HSDPA is not allocated then a cell with highest RSCP value is used.

This functionality is allowed to UEs current RAB combination with mblbMobilityRABComb parameter.

mblbLoadInfoDistr (mblb Load Information Distribution)

This parameter defines whether the HSPA load information (used in Multi-Band Load Balancing) of the cell is
distributed inside the RNC. This same information is distributed also in case if any of Multi-Band Load Balancing
triggers (mblbRABSetupEnabled, mblbStateTransEnabled, mblbInactivityEnabled, mblbMobilityEnabled) is enabled in
the cell. If any of above triggering parameter and this parameter is not enabled the HSPA load information of this cell is
not distributed inside the RNC meaning that HSPA load information of this cell is not available for Multi-Band Load
Description Balancing decision making. If the HSPA load information distribution is activated, HS-DSCH and E-DCH provided bit
rate measurements are also activated in the cell. It is better not to set this parameter enabled if the cell cannot be MultiBand Load Balancing target cell to avoid unnecessary internal message load and to avoid unnecessary measurements to
be activated.
Note! From the cell where HSDPA is not enabled the HSPA load information is not distributed and HS-DSCH and EDCH provided bit rate measurements are not activated.
Related
Multi-Band Load Balancing (optional)
features