Soft Handover overhead [%]KPI name Soft Handover overhead in CIADAKPI abbreviation sho overhead in CIADAKPI ID IHSPA_192aDescription Soft Handover overhead [%] for Controlling IADA over the reporting period.Measurement M1007 - Soft Handover I-HSPA (I-HSPA Adapter)

KPI formula

100* (sum([M1007C0] + [M1007C19] + [M1007C1] + [M1007C20] + [M1007C2] + [M1007C21]) / sum(([M1007C0] + [M1007C19]) + ([M1007C1] + [M1007C20])/2 + ([M1007C2] + [M1007C21])/3) - 1)

KPI formula with short names

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] + [THREE_CELLS_IN_ACT_SET_NRT]) / 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 CapacityUnit PercentageObject Summary Levels

Network, IADA, WCEL

Time Summary Levels

Total; week; weeklyBH; day; dailyBH; hour

The following table contains the basic information needed to perform this use case.

ID RAN_USE_CASE_OPT_002Use case name Soft handover analysis and optimizationRAN releases All RAN releasesActors Network planner, operation engineer

SummaryBased on cell-to-cell level KPIs, you can identify, profile and manually correct sho problems

Triggers for service/resource information used

KPIs based on mobile reports

Limitations and restrictions Measurements are not availableReasons for performing the use case

Problematic areas were found based on cell-level sho KPIs.

Preconditions Reliable traffic data is available.

PostconditionsInitial adjacencies have been created and their performance can be measured.

Table 4:  Use case informationsho 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+M1007C25for HSUPA - M1007C66for 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.

6 Provision the changes to the network

Soft Handover overhead [%]KPI name Soft Handover overhead in CRNCKPI abbreviation

sho overhead in CRNC

KPI ID RNC_192bDescription Soft Handover overhead [%] for Controlling RNC over the reporting period.

Note 1In the sho Measurement the counters are both for RNC and WCELL. This formula is purely using the cell level counters.

Note 2The formula will not work properly in border areas. This because that for the DRNC cells in the AS there will not be any counter updates.

Measurement M1007: Soft Handover

KPI formula100* (sum([M1007C0] + [M1007C19] + [M1007C1] + [M1007C20] + [M1007C2] + [M1007C21]) / sum(([M1007C0] + [M1007C19]) + ([M1007C1] + [M1007C20])/2 + ([M1007C2] + [M1007C21])/3) - 1)

KPI formula with short names

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] + [THREE_CELLS_IN_ACT_SET_NRT]) / 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 CapacityUnit PercentageTypical values 40 % (Average AS size = 1.4)Object Summary Levels

Network, City, Area, RNC, Cluster of cells, Cell

Time Summary Levels

Week, Day, Hour

Table 122:  Soft Handover overhead in CRNC

MBLB

mblbMobilityEnabled (mblb in Mobility Enabled)Field RNC mcRNC 2.0 RNC mcRNC 3.0Description 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.

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.

Field RNC mcRNC 2.0 RNC mcRNC 3.0Changes in the parameter are applied in upcoming inactivity detected events in Cell_DCH state.

Modification onLine objectLocking

mblbInactivityEnabled (mblb in Inactivity Enabled)Field RNC mcRNC 2.0 RNC mcRNC 3.0

Description

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.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.

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.

Modification onLine objectLockingMulti-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)

Description

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 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 Multi-Band 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 E-DCH provided bit rate measurements are not activated.

Related features

Multi-Band Load Balancing (optional)