3 g Capacity Monk Pi

Slide 1I insert classification level
Logo holding slide
Logo is aligned right to reflect the corporate stationery.
* © Nokia Siemens Networks 3GRANcapKPI / Wirongrong Inkeaw / Oct 2007
Soc Classification level
What can be measured – RAN Capacity Management
How you can measure it
Capacity upgrade process overview
A limited number of indicators have been implemented within optima.
There is no documentation for where and when to use of these indicators.
Currently the indicators are only executed when performance issues are highlighted.
The result from the indicators are not fully understood.
RAN Capacity Management
RNC
RRC
NBA
BRM
(2)
(3)
(4)
(7)
NRM
(8)
(11)
UE
WBTS
(9) aal2_establish_request
(12) RRC: RRC Connection Setup
NBA= NobeB application part, BRM = BTS resource manager RRC= Radio Resource Control,
NRM = Transmission Resource Control
CNBAP
AAL2SIG
Core
RNC
UE
WBTS
(17) RAB assignment response
What can be measured – RAN Capacity Management
How you can measure it
Capacity upgrade process overview
DSP Performance Measurement
Unit load measurement *
Iu layer 3 signalling
AAL5 protocol measurement in DMX
Availability performance measurement
AAL2 Resource Reservation*
ATM VCC Measurements *
Capacity Shortfall Indicators
UE
WBTS
Radio Resource Indication
Service Level Table
Average non-HSDPA Transmit Power
Average Channelisation Code Occupancy
Maximum Channelisation Code Occupancy
Cell Resource Indicators
CS Voice RAB Blocking Rate Caused by AC
CS Conversational RAB Blocking Rate Caused by AC
PS Data RAB Blocking Rate Caused by AC
Service Level Indicators
UL CS Voice DCH Accept Rate
UL CS Video DCH Accept Rate
UL PS Data DCH Accept Rate
UL HSDPA Accept Rate
DL CS Voice DCH Accept Rate
DL CS Video DCH Accept Rate
DL PS Data DCH Accept Rate
Traffic Level Indicators
Uplink interference can be reduced by:
1. Checking for sources of external interference e.g. GSM1800 antennas with inadequate isolation.
2. Checking that the Node B has been configured correctly during commissioning.
3. Checking that the neighbour plan is optimum
3. Adjusting antenna down tilt, height and azimuth while ensuring that service coverage is not compromised.
4. Upgrading the Node B configuration in terms of an additional carrier.
Background interference can be reduced by:
1. Checking for sources of external interference e.g. GSM1800 antennas with inadequate isolation.
2.Checking that the Node B has been configured correctly during commissioning.
Triggering Indicator:
The total downlink transmit power can be reduced by:
1. Reducing the power assigned to the common channels.
2. Adjusting antenna downtilt, height and azimuth while ensuring that service coverage is not compromised.
The channelisation code load can be reduced by:
1. Introducing code tree optimisation to help avoid code tree segmentation.
2. Introducing a secondary scrambling code.
3. Evaluating the impact of reducing the level of soft handover.
1. Increasing the number of available PRACH preamble signatures.
2. Increasing the number of available PRACH access slots.
The S-CCPCH (FACH only) load can be reduced by:
1. Increasing the number of available S-CCPCH.
2. Evaluate whether or not there are large quantities of signalling generated by cell, URA, location area or routing area updates. If so, consider adjusting the area boundaries.
Scope and objective
The scope of this document is to documented and explained 3G capacity shortfall indicators which has been implemented in Aircom Optima tool
3G capacity shortfall indicator is used for 3G capacity monitoring and capacity upgrade purpose.
Threshold for 3G capacity shortfall indicator is identified to triggered 3G capacity upgrade evaluation process.
The capacity shortfall indicator in this report are implemented in Optima under directory
Team folders/Radio Networks/Team North/3G capacity Monitoring
PI expression 100 % * SUM(SUM_RACH_ACK_PREAMBLES) / SUM(PERIOD_DURATION * 180000)
PI description This KPI quantifies the PRACH preamble load in percentage. Based on up to 4 PRACH signatures is supported and 15 PRACH access slots per 20 ms PRACH frame. This results in 60 random access opportunities per 20 ms or 180 000 access opportunities per 1 minute. KPI is applicable when the open Iub is used. The open Iub can use either Nokia proprietary content within the NBAP PRIVATE RADIO RESOURCE MEASUREMENT REPORT or 3GPP content within the NBAP COMMON MEASUREMENT REPORT. The former is used when a RAS05 Nokia RNC is connected to a RAS05 Nokia Node B. The latter is used if a third party Node B is connected to the RNC. The Nokia KPI definition has been modified so the result is presented as a percentage load rather than an absolute figure. The PERIOD_DURATION is defined by the measurement period in units of minutes.
Note PRACH preable is based on slotred ALOHA approach. High PRACH preamble load indicates high probability of random access collision
PI name in Optima
PI expression SUM(AVE_SCCPCH_INC_PCH_LOAD) / SUM(SCCPCH_LOAD_DENOM_0)
PI description The current Nokia implementation allows the configuration of up to two S-CCPCH. If a single S-CCPCH is configured then it encapsulates the PCH and two FACH transport channels. Separate FACH transport channels are required for control plane and user plane data. If two S-CCPCH are configured then the first encapsulates the two FACH transport channels while the second encapsulates the PCH transport channel. If a single S-CCPCH is configured then this KPI is applicable to that channel. If two S-CCPCH are configured then this KPI is applicable to the S-CCPCH encapsulating the PCH transport channel. The result represents the percentage load of the S-CCPCH.
Note
PI name in Optima
PI expression 10 * LOG10[SUM(POWER(10, AVE_PTXTOT_CLASS_0 / 1000) * PTXTOT_DENOM_0 + POWER(10, AVE_PTXTOT_CLASS_1 / 1000) * PTXTOT_DENOM_1 + POWER(10, AVE_PTXTOT_CLASS_2 / 1000) * PTXTOT_DENOM_2 + POWER(10, AVE_PTXTOT_CLASS_3 / 1000) * PTXTOT_DENOM_3 + POWER(10, AVE_PTXTOT_CLASS_4 / 1000) * PTXTOT_DENOM_4) / SUM( PTXTOT_DENOM_0 + PTXTOT_DENOM_1 + PTXTOT_DENOM_2 + PTXTOT_DENOM_3 + PTXTOT_DENOM_4)]
PI description The result is the average total downlink transmit power in absolute terms. The result includes the transmit power assigned to both common and dedicated physical channels (not HSDPA). The Node B sends total downlink transmit power measurements to the RNC every radio resource indication period (typically every 200 ms). When HSDPA is enabled on the site if the average ptxtotal power becomes high relative to PtxTargetHSDPA then a capacity upgrade should be considered to increase the availability of downlink transmit power. If HSDPA is not enabled if the average ptxtotal power becomes high relative to PtxTarget then a capacity upgrade should be considered.
Note The RNC databuild and alarm history should also be checked to ensure there are no databuild errors nor hardware issues.
PI name in Optima
PI expression MAXIMUM_PTXTOTAL
PI description This KPI result quantifies the maximum downlink transmit power experienced during the measurement period. The result is generated from a single counter which represents a downlink transmit power in dBm. The result of this KPI depends upon the common channel transmit power configuration as well as the downlink traffic loading the cell. A high common channel transmit power and/or high downlink traffic will generate a high KPI result. An unloaded cell should have a downlink transmit power of approximately 36 dBm.
Note The RNC databuild and alarm history should also be checked to ensure there are no databuild errors nor hardware issues
PI name in Optima
PI expression 100 % * SUM(PTXTOT_DENOM_2 + PTXTOT_DENOM_3 + PTXTOT_DENOM_4) / SUM(PTXTOT_DENOM_0 + PTXTOT_DENOM_1 + PTXTOT_DENOM_2 + PTXTOT_DENOM_3 + PTXTOT_DENOM_4)
PI description The result is the percentage of time that the PtxTotal measurements exceed the relative threshold defined by PtxTarget – PtxOffset. PtxOffset is typically configured as 1 dB. The PtxTotal measurement includes the transmit power assigned to both common and dedicated physical channels. The Node B sends total downlink transmit power measurements to the RNC every radio resource indication period (typically every 200 ms). When HSPDA is active in the Cell the relative thresholds become PtxTargetHSDPA –PtxOffsetHSDPA.
Note The RNC databuild and alarm history should also be checked to ensure there are no databuild errors nor hardware issues
PI name in Optima
PI expression SUM(AVG_NON_HSDPA_PWR * AVG_NON_HSDPA_PWR_DENOM) / SUM(AVG_NON_HSDPA_PWR_DENOM)
PI description This KPI quantifies the non-HSDPA downlink transmit power averaged throughout the entire measurement period. The result is presented as a percentage of the total downlink transmit power capability. The non-HSDPA transmit power measurement is used as a criteria for overload control when HSDPA is active. If the non-HSDPA transmit power exceeds PtxTargetHSDPA then overload actions are triggered. Therefore If the average non-HSDPA transmit power becomes high relative to PtxTargetHSDPA then a capacity upgrade should be considered to increase the availability of downlink transmit power. This criteria should only be applied to cells which have HSDPA enabled.
Note
PI expression 10*LOG10(AVERAGE(POWER(10,(AVE_PRX_NOISE / -100)/10)))
PI description The result is the average background interference floor of a cell. PrxTotal measurements are classified as representing background interference when neither UnloadedRT nor UnloadedNRT are exceeded. UnloadedRT and UnloadedNRT both have defaults values of 2 %. The RNC tracks the own cell load associated with its active connections and compares this load with these thresholds. The RNC tracks the own cell load by computing 10^[(Eb/No - Processing Gain)/10] for each active connection.
Note PrxNoise is meaningful only when PrxNoise auto-tuning is enabled
PI expression 10 *LOG10[SUM(POWER(10, (-112.1 + 0.1 *AVE_PRXTOT_CLASS_0) / 10) * PRXTOT_DENOM_0 + POWER(10, (-112.1 + 0.1 * AVE_PRXTOT_CLASS_1) / 10) * PRXTOT_DENOM_1 + POWER(10, (-112.1 + 0.1 * AVE_PRXTOT_CLASS_2) / 10) * PRXTOT_DENOM_2 + POWER(10, (-112.1 + 0.1 * AVE_PRXTOT_CLASS_3) / 10) * PRXTOT_DENOM_3 + POWER(10, (-112.1 + 0.1 * AVE_PRXTOT_CLASS_4) / 10) * PRXTOT_DENOM_4) / SUM(PRXTOT_DENOM_0 + PRXTOT_DENOM_1 + PRXTOT_DENOM_2 + PRXTOT_DENOM_3 + PRXTOT_DENOM_4)]
PI description The result is the average uplink received interference power in absolute terms. The PrxTotal measurement is made by the WTR. If an MHA is not installed then the measurement reference point is the Node B cabinet antenna connector. If an MHA is installed then the measurement reference point is the far side of the MHA.
Note Reliability of the indicators are good with no known faults. MHA is implemented in VI IE for the whole network
PI expression MAX(MAXIMUM_PRXTOTAL)
PI description This KPI result quantifies the maximum uplink interference floor experienced during the measurement period. The result is generated from a single counter which represents an uplink received power in dBm. The result of this KPI depends upon the uplink noise figure of the receiver sub-system as well as the uplink load generated by the cell. A high uplink noise figure and/or a high uplink load will generate a high KPI result. An unloaded cell should have an uplink interference floor of approximately -105 dBm. This figure assumes a 3 dB composite noise figure
Note
PI expression 100 % [PRXTOT_DENOM_2 + PRXTOT_DENOM_3 + PRXTOT_DENOM_4] / [PRXTOT_DENOM_0 + PRXTOT_DENOM_1 + PRXTOT_DENOM_2 + PRXTOT_DENOM_3 + PRXTOT_DENOM_4]
PI description The result is the percentage of time that the PrxTotal measurements exceed the relative threshold defined by PrxTarget – PrxOffset. PrxOffset is typically configured as 1 dB. The Node B sends uplink received interference power measurements to the RNC every radio resource indication period (typically every 200 ms).
Note Hardware fault or an error in the WBTS commissioning parameters lead to an incorrect measurement result
PI name in Optima
Capacity evaluation threshold
3-6 dB (threshold can be different depend upon area type(rural and urban area)
Time resolution
1 hour
PI expression Background Interference - Absolute uplink interference
PI description The different between average Prx noise and average PrxTotal is the uplink interference (uplink load).
Note
PI name in Optima
PI expression 100 % * [SUM(RRC_STP_FAIL_AC)] / [SUM(RRC_STP_ATT)]
PI description The result represents the failure rate of the SRB admission. The counter RRC_STP_FAIL_AC is incremented when the admission control entity reports a failure. This can be as a result of congestion (high uplink interference or the downlink power is limited), therefore this indicator should be used in conjunction with the lower layer performance indicators to identify capacity shortfalls. The service level counters are applicable to the RRC establishment procedure and provide an indication of end user perception. This KPI may be used to identify cells which exhibit a high proportion of RRC admission control rejections.
Note The main reason of ‘RRC set up failure’ counter is due to lack of resources on the air interface.
This PI is required BH traffic. Daily statistic will average out the rrc blocking during peak hour. Most case seen from 1wcel of the site. No any other cause from trans, bts, RNC etc.
Sometime the wcell has failure in AC, BTS and TRANS at the same time- active alarm and alarm history should be checked for this case. Hareware problem was suspected.
PI name in Optima
PI expression 100 % * [SUM(RAB_STP_FAIL_CS_VOICE_AC)] / [SUM(RAB_STP_ATT_CS_VOICE)].
PI description The result provides an indication of the probability of blocking for the CS speech service caused by 'admission control'. The counter RAB_STP_FAIL_CS_VOICE_AC is incremented when the admission control entity reports a failure. This can be as a result of congestion (high uplink interference, downlink power is limited or channelisation code blocking), therefore this indicator should be used in conjunction with the lower layer performance indicators to identify capacity shortfalls. The service level counters are applicable to the RAB establishment procedure and provide an indication of end user perception.
NoteThe service level counters are updated on the main cell (The main cell being the cell with the best radio condition in the last received measurement report). Therefore in soft handover scenarios blocking indication can increment on the incorrect cell. Service level indicators should be used in conjunction with lower layer indicators to identify capacity shortfalls.
PI name in Optima
PI expression 100 % * [SUM(RAB_STP_FAIL_CS_CONV_AC)] / [SUM(RAB_STP_ATT_CS_CONV)]
PI description The result provides an indication of the probability of blocking for the CS Conversational service caused by 'admission control'. The counter RAB_STP_FAIL_CS_CONV_AC is incremented when the admission control entity reports a failure. This can be as a result of congestion (high uplink interference, downlink power is limited or channelisation code blocking), therefore this indicator should be used in conjunction with the lower layer performance indicators to identify capacity shortfalls. The service level counters are applicable to the RAB establishment procedure and provide an indication of end user perception.
Note Theservice level counters are updated on the main cell (The main cell being the cell with the best radio condition in the last received measurement report). Therefore in soft handover scenarios blocking indication can increment on the incorrect cell. Service level indicators should be used in conjunction with lower layer indicators to identify capacity shortfalls.
PI name in Optima
PI expression 100 % * SUM(RAB_STP_FAIL_PS_INTER_AC + RAB_STP_FAIL_PS_BACKG_AC) / SUM(RAB_STP_ATT_PS_INTER + RAB_STP_ATT_PS_BACKG)
PI description The result provides an indication of the probability of blocking for the PS NRT data service caused by 'admission control' indicating instances of air-interface or channelisation blocking. In the case of the PS data service, the RAB is established with a 0/0 kbps configuration and is subsequently upgraded after either an uplink or downlink capacity request. This means that the probability of blocking during RAB establishment should be low because additional resources are not required for the air-interface. The blocking of subsequent upgrades can be observed in indicators DL/UL PS Data DCH Accept Rate.
Note The service level counters are updated on the main cell (The main cell being the cell with the best radio condition in the last received measurement report). Therefore in soft handover scenarios blocking indication can increment on the incorrect cell. Service level indicators should be used in conjunction with lower layer indicators to identify capacity shortfalls.
PI name in Optima
PI expression 100 % * [1 - SUM(DCH_REQ_LINK_REJ_UL_SRNC) / SUM(DCH_REQ_LINK_SRNC)]
PI description The result represents the success rate of uplink SRB admission. The admission procedure is applicable to RRC connection establishment, the transition from CELL_FACH to CELL_DCH, soft handover branch addition and hard handovers. Admission control may reject an uplink request if the current uplink interference is high. The DCH_REQ_LINK_REJ_UL_SRNC counter is incremented by the RNC when a DCH request for an uplink SRB is rejected by admission control. The DCH_REQ_LINK_SRNC counter is incremented by the RNC when admission control receives a request for an SRB DCH. This KPI may be used to identify cells which exhibit a high proportion of admission control rejections.
Note .
PI name in Optima
PI expression 100 % * [1 - SUM(DCH_REQ_LINK_REJ_DL_SRNC) / SUM(DCH_REQ_LINK_SRNC)]
PI description The result represents the success rate of downlink SRB admission. The admission procedure is applicable to RRC connection establishment, the transition from CELL_FACH to CELL_DCH, soft handover branch addition and hard handovers. Admission control may reject a downlink request if the current cell downlink transmit power is high, or there are no channelisation codes available. The DCH_REQ_LINK_REJ_DL_SRNC counter is incremented by the RNC when a DCH request for a downlink SRB is rejected by admission control. The DCH_REQ_LINK_SRNC counter is incremented by the RNC when admission control receives a request for an SRB DCH.
Note .
PI name in Optima
PI expression 100 % * [1 – SUM(REQ_CS_VOICE_REJ_UL_SRNC) / SUM(REQ_CS_VOICE_IN_SRNC)]
PI description The result represents the success rate of downlink SRB admission. The admission procedure is applicable to RRC connection establishment, the transition from CELL_FACH to CELL_DCH, soft handover branch addition and hard handovers. Admission control may reject a downlink request if the current cell downlink transmit power is high, or there are no channelisation codes available. The DCH_REQ_LINK_REJ_DL_SRNC counter is incremented by the RNC when a DCH request for a downlink SRB is rejected by admission control. The DCH_REQ_LINK_SRNC counter is incremented by the RNC when admission control receives a request for an SRB DCH.
Note .
PI name in Optima
PI expression 100 % * [1 – SUM(REQ_CS_VOICE_REJ_DL_SRNC) / SUM(REQ_CS_VOICE_IN_SRNC)]
PI description The result represents the success rate of downlink CS speech DCH admission. The admission procedure is applicable to RAB establishment, soft handover branch addition and hard handovers. Admission control may reject a downlink request if the current cell downlink transmit power is high, or there are no channelisation codes available. The REQ_CS_VOICE_REJ_DL_SRNC counter is incremented by the RNC when a downlink speech DCH request is rejected by admission control. The REQ_CS_VOICE_IN_SRNC counter is incremented by the RNC when admission control receives a request for an downlink speech DCH. This KPI may be used to identify cells which exhibit a high proportion of admission control rejections.
Note .
PI name in Optima
PI expression 100 % * [1 – SUM(REQ_CS_CONV_REJ_UL_SRNC) / SUM(REQ_CS_DATA_CONV_SRNC)]
PI description The result represents the success rate of uplink CS video DCH admission. The admission procedure is applicable to RAB establishment, soft handover branch addition and hard handovers. Admission control may reject an uplink request if the current uplink interference is high. The REQ_CS_CONV_REJ_UL_SRNC counter is incremented by the RNC when a CS video DCH request is rejected by admission control. The REQ_CS_DATA_CONV_SRNC counter is incremented by the RNC when admission control receives a request for an uplink video DCH. This KPI may be used to identify cells which exhibit a high proportion of admission control rejections.
Note .
PI name in Optima
PI expression 100 % * [1 – SUM(REQ_CS_CONV_REJ_DL_SRNC) / SUM(REQ_CS_DATA_CONV_SRNC)]
PI description The result represents the success rate of downlink CS video DCH admission. The admission procedure is applicable to RAB establishment, soft handover branch addition and hard handovers. Admission control may reject a downlink request if the current cell downlink transmit power is high, or there are no channelisation codes available. The REQ_CS_CONV_REJ_DL_SRNC counter is incremented by the RNC when a CS video DCH request is rejected by admission control. The REQ_CS_DATA_CONV_SRNC counter is incremented by the RNC when admission control receives a request for a CS video DCH.This KPI may be used to identify cells which exhibit a high proportion of admission control rejections.
Note
PI name in Optima
PI expression 100 %* [1 – SUM(REQ_PS_INTERA_REJ_UL_SRNC + REQ_PS_BACKG_REJ_UL_SRNC) / SUM(REQ_FOR_PS_INTERA_UL_SRNC + REQ_FOR_PS_BACKG_UL_SRNC)]
PI description The result represents the success rate of uplink PS data DCH admission. The admission procedure is applicable to RAB establishment, radio bearer reconfiguration, soft handover branch addition and hard handovers. Admission control may reject an uplink request if the current uplink interference is high or if the maximum allowed bit rate is already allocated. The REQ_PS_xxx_REJ_UL_SRNC counters are incremented by the RNC when a PS data DCH request is rejected by admission control. The REQ_FOR_PS_xxx_UL_SRNC counters are incremented by the RNC when admission control receives a request for a PS data DCH.This KPI may be used to identify cells which exhibit a high proportion of admission control rejections.
Note
PI name in Optima
PI expression 100 % * [1 – SUM(REQ_PS_INTERA_REJ_DL_SRNC + REQ_PS_BACKG_REJ_DL_SRNC) / SUM(REQ_FOR_PS_INTERA_DL_SRNC + REQ_FOR_PS_BACKG_DL_SRNC)]
PI description The result represents the success rate of downlink PS data DCH admission. The admission procedure is applicable to RAB establishment, radio bearer reconfiguration, soft handover branch addition and hard handovers. Admission control may reject a downlink request if the current cell downlink transmit power is high, there are no channelisation codes available, if the new initial downlink transmit power exceeds the dynamic link optimisation threshold, or if the maximum allowed bit rate is already allocated. The REQ_PS_xxx_REJ_DL_SRNC counters are incremented by the RNC when a PS data DCH request is rejected by admission control. The REQ_FOR_PS_xxx_DL_SRNC counters are incremented by the RNC when admission control receives a request for a PS data DCH.
Note
PI expression 100 % *[1-((SUM(REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR) / SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR+SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR + REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR + SETUP_FAIL_RNC_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_RNC_HS_DSCH_BGR + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR))]
PI description The result provides an indication of the probability of blocking for the HSDPA service due to radio resources for the return channel. The counter REJ_HS_DSCH_RET_XX increments for the HS-DSCH transport channel due to lack of radio resources for the UL DCH return channel for the different traffic classes. Counters are defined for both interactive and background services.
Note
PI expression SUM(CODE_CAPACITY) / (DENOM_CODE_CAPACITY)
PI description The result is the average occupancy of the downlink channelisation code tree. The result represents the ratio: (total number of codes used) / (total number of codes within the OVSF code tree). The number of codes used includes codes that have been assigned in addition to codes which have been blocked by those which have been assigned. This KPI may be used to identify cells which are approaching their maximum channelisation code capability. This KPI may be used as a trigger for a capacity upgrade process
Note
PI expression MAX(MAX_CODE_OCCUPANCE_PERCENT)
PI description The result is the maximum occupancy of the downlink channelisation code tree during the measurement period. The result represents the maximum of the ratio: (total number of codes used) / (total number of codes within the OVSF code tree). The number of codes used includes codes that have been assigned in addition to codes which have been blocked by those which have been assigned.
Note
PI expression 100 % * SUM(NO_CODES_AVAILABLE_SF4 + NO_CODES_AVAILABLE_SF8 + NO_CODES_AVAILABLE_SF16 + NO_CODES_AVAILABLE_SF32 + NO_CODES_AVAILABLE_SF64 + NO_CODES_AVAILABLE_SF128 + NO_CODES_AVAILABLE_SF256) / SUM(NBR_SUCC_CODE_TREE_ALLO + NO_CODES_AVAILABLE_SF4 + NO_CODES_AVAILABLE_SF8 + NO_CODES_AVAILABLE_SF16 + NO_CODES_AVAILABLE_SF32 + NO_CODES_AVAILABLE_SF64 + NO_CODES_AVAILABLE_SF128 + NO_CODES_AVAILABLE_SF256)
PI description The result is the percentage of code allocation attempts which are blocked as a result of code tree congestion. The numerator of the equation represents the number of blocked allocation attempts whereas the demononator represents the total number of attempts. The blocked allocation attempt counters are incremented on a per spreading factor basis.
Note
Capacity upgrade process
Channelisation code blocking > 0.5%
UE
WBTS
Service Level Table
Cell Resource Table
The indicators within each counter table
Cell Resource Indicators
RAB Setup failure for Voice by BTS
RAB Setup failure for CS Conv by BTS
RAB Setup failure for PS Background by BTS
Iub Transport Indicator
Proactive
Reactive
Reactive
Traffic Indicators
Node B Uplink/Downlink Baseband Processing
If the baseband processing capacity of a Node B becomes congested then a hardware upgrade should be considered in terms of configuring an additional WSPC card. Other approaches can also be considered to reduce the baseband processing load, e.g. reducing the soft handover overhead and reducing the bit rates assigned. However these approaches are likely to have an impact upon network performance.
AVE_AVAIL_PERC_POOL_CAPA_DL
Counter Table:
Cell Resource
Units/Level: %/WBTS
Note: N/A
PI Description
This KPI quantifies the percentage of available baseband processing resources at a Node B. The M1000C134 counter provides the result for a single Node B. The M1000C136 counter is used to weight the KPI result when summarised for multiple Node B. In this case, the M1000C136 counter provides more weighting to Node B which have generated larger quantities of resource reports. The M1000C136 counter cancels from the numerator and denominator when the KPI is generated for a single Node B. If the baseband processing capacity of a Node B becomes heavily loaded then this KPI will generate a relatively small result.
Monitoring Type:
M1000C136 Cell_Resource NBR_OF_BTS_HW_CAPA_ALLOC_DL BTS HW CAPACITY DL DENOMINATOR not supported RN3.0
M1000C137 Cell_Resource NBR_OF_BTS_HW_CAPA_ALLOC_UL BTS HW CAPACITY UL DENOMINATOR not supported RN3.0
PI Name:
Counter Table:
Cell Resource
Units/Level: %/WBTS
Note: N/A
PI Description
This KPI quantifies the percentage of available baseband processing resources at a Node B. The M1000C135 counter provides the result for a single Node B. The M1000C137 counter is used to weight the KPI result when summarised for multiple Node B. In this case, the M1000C137 counter provides more weighting to Node B which have generated larger quantities of resource reports. The M1000C137 counter cancels from the numerator and denominator when the KPI is generated for a single Node B. If the baseband processing capacity of a Node B becomes heavily loaded then this KPI will generate a relatively small result.
Monitoring Type:
PI name in Optima
PI expression 100 % * [SUM(RRC_CONN_STP_FAIL_BTS)] / [SUM(RRC_CONN_STP_ATT )]
PI description The result provides an indication of the blocking probability for the RRC connection setup caused by ‘BTS’ reasons. The RRC_STP_FAIL_BTS counter increments when the NBAP entity receives an unsuccessful radio link setup from the WBTS. This can be as a result of insufficient WSP resources and should therefore be used in conjunction with the lower layer performance indicators to identify capacity shortfalls. The service level counters are applicable to the RRC establishment procedure and provide an indication of end user set up perception
Note Failure counters itself are not enough to indicate congestion but together with WBTS hardware resource measurement (M5001) it is possible to identify cells having capacity problems.
PI name in Optima
PI expression 100 % * [SUM(RAB_STP_FAIL_CS_VOICE_BTS)] / [SUM(RAB_STP_ATT_CS_VOICE)]
PI description The result provides an indication of the blocking probability for the CS voice service caused by ‘BTS’ reasons. The RAB_STP_FAIL_CS_VOICE_BTS counter increments when the NBAP entity receives an unsuccessful radio link reconfiguration from the WBTS. This can be as a result of insufficient WSP resources and should therefore be used in conjunction with the lower layer performance indicators to identify capacity shortfalls. The service level counters are applicable to the RAB establishment procedure and provides an indication of end user perception.
PI name in Optima
PI expression 100 % * [SUM(RAB_STP_FAIL_CS_CONV_BTS)] / [SUM(RAB_STP_ATT_CS_CONV)]
PI description The result provides an indication of the blocking probability for the CS video service caused by ‘BTS’ reasons. The RAB_STP_FAIL_CS_CONV_BTS counter increments when the NBAP entity receives an unsuccessful radio link reconfiguration from the WBTS. This can be as a result of insufficient WSP resources and should therefore be used in conjunction with the lower layer performance indicators to identify capacity shortfalls. The service level counters are applicable to the RAB establishment procedure and provides an indication of end user perception.
PI name in Optima
PI expression 100*( SUM(SETUP_FAIL_FIRST_RL_MISC + SETUP_FAIL_SHO_SRNC_MISC+SETUP_FAIL_SHO_DRNC_MISC) / SUM (RL_SETUP_ATT_FOR_FIRST_RL+ RL_SETUP_ATT_FOR_SHO_ON_SRNC+RL_SETUP_ATT_FOR_SHO_ON_DRNC)
PI description The result provides the percentage of radio link setup failures caused by miscellaneous. The Nokia solution maps the lack of WSP processing resources to the counters Miscellaneous as specified in 3GPP 25.433. This PI should be used in conjunction with the lower layer performance indicators to identify capacity shortfalls.
PI name in Optima
PI expression 100 % *SUM(SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_BGR) / SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR+SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR +REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR + SETUP_FAIL_RNC_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_RNC_HS_DSCH_BGR + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR)
PI description The result provides an indication of the probability of blocking due to WBTS for the HSDPA service. The KPI is defined by dividing the number of unsuccessful establishments for BTS by the total number of successful and unsuccessful attempts. Counters are defined for both interactive and background services.
PI name in Optima
PI expression max_value(sum( AVG_USED_CE_DL/AVE_AVAIL_CE)) , sum( AVG_USED_CE_UL/AVE_AVAIL_CE))
PI description The result provides an indication of percentage of channel element(CE) usage during the measurement period . The channel element usage is symmetrical, so the KPI is based on taking the larger average of UL/DL utilization.
Note
PI name in Optima
PI expression max_value(sum( MAX_USED_CE_DL/AVE_AVAIL_CE)) , sum( MAX_USED_CE_UL/AVE_AVAIL_CE))
PI description The result provides an indication of percentage of maximum channel element (CE) usage during the measurement period . The channel element usage is symmetrical, so the KPI is based on taking the larger average of UL/DL utilization.
Note
UE
WBTS
(13) RRC: RRC Connection Setup Complete
Note: If NRM rejects for RT call, then pre emption is started of a NRT call.
CNBAP
CAC
AAL2SIG
CS Voice RAB Blocking Rate Caused by Transport
CS Conversational RAB Blocking Rate Caused by Transport
PS Data RAB Blocking Rate Caused by Transport
Iub DCH Reservation (cps)
Iub HSDPA Reserved Bandwidth
Iub Maximum AAL2 Connections
Total User Plane Egress Transport Load
AAL2 VCC measurement indicators
Iub Average AAL2 Connections
Iub Maximum AAL2 Connections
A high maximum result indicates that it may be necessary to introduce an additional VCC, i.e. a logical capacity upgrade.
A high reserved bandwidth or if the average Iub bandwidth available for HSDPA is less than the target HSDPA throughput then a physical capacity upgrade should be considered.
-Transport-
Due to problem in Optima (VCI and VPI missing), this KPI is not able to implement in Optima.
PI full name
PI name in Optima
Monitor type
PI expression 100 % SUM(EG_TOT_CELLS_VC) / SUM(AAL2_PATH_GUAR_CELL_RATE PERIOD_DURATION 60)
PI description This KPI quantifies the total downlink traffic transferred across the Iub user plane VCC as a percentage of the user plane VCC capacity. Counter EG_TOT_CELLS_VC quantifies the number of Egress ATM cells which are transferred during the measurement period. Counter AAL2_PATH_GUAR_CELL_RATE quantifies the bandwidth of the Iub user plane VCC.
Note If the KPI result becomes high, an Iub physical capacity upgrade should be considered. The KPI result represents an average load during the measurement period. There could be short term peaks in activity which cause blocking prior to the load approaching 100 %.
-Transport-
Due to problem in Optima (VCI and VPI missing), this KPI is not able to implement in Optima.
PI full name
PI name in Optima
Monitor type
PI expression 100 % SUM(IN_TOT_CELLS_VC) / SUM(AAL2_PATH_GUAR_CELL_RATE PERIOD_DURATION 60)
PI description This KPI quantifies the total uplink traffic transferred across the Iub user plane VCC as a percentage of the user plane VCC capacity. Counter IN_TOT_CELLS_VC quantifies the number of Egress ATM cells which are transferred during the measurement period. Counter AAL2_PATH_GUAR_CELL_RATE quantifies the bandwidth of the Iub user plane VCC.
Note If the KPI result becomes high, an Iub physical capacity upgrade should be considered. The KPI result represents an average load during the measurement period. There could be short term peaks in activity which cause blocking prior to the load approaching 100 %.
Monitor type
PI expression 100 * SUM_RESERVED_CELL_RATE / (NBR_SAMPLES * AAL2_PATH_GUAR_CELL_RATE )
PI description This KPI quantifies the percentage of the Iub user plane VCC which has been reserved for DCH and HSDPA connections. This KPI provides an indication of the overall load of the Iub user plane VCC. This KPI is based upon the sum of all Iub reservations rather than actual throughput. The actual throughput could be less than or greater than the sum of the reservations.
Note A high load indicates that a physical capacity upgrade (additional E1) is likely to be necessary. When zero is dedicated to HSDPA( ‘ShareAllocationHSDPA’ = 0, This KPI quantifies the percentage of the Iub user plane VCC which has been reserved for DCH(this is because iub user plane VCC is reserved for HSDPA is equal to zero). In this case HSDPA uses capacity which is left from DCH reservation.
PI name in Optima
Monitor type
Time resolution
1 hour
PI expression SUM_RESERVED_CELL_RATE / NBR_SAMPLES
PI description This KPI quantifies the Iub user plane VCC which has been reserved for DCH and HSDPA connections in cells per second. This KPI provides an indication of the overall load of the Iub user plane VCC. This KPI is based upon the sum of all Iub reservations rather than actual throughput. The actual throughput could be less than or greater than the sum of the reservations.
Note A high load indicates that a physical capacity upgrade (additional E1) is likely to be necessary.
Monitor type
PI expression 100 *(MAX_RESERVED_CELL_RATE / AAL2_PATH_GUAR_CELL_RATE )
PI description This KPI quantifies the percentage of the maximum Iub user plane VCC which has been reserved for DCH and HSDPA connections. This KPI provides an indication of the maximum overall load of the Iub user plane VCC. The actual Iub throughput can be greater than or less than that indicated by the reserved load, i.e. The DCH throughput should be less than the DCH reserved bandwidth but the HSPDA throughput may be either greater than or less than the reserved bandwidth.
PI name in Optima
Monitor type
Time resolution
1 hour
PI expression MAX_RESERVED_CELL_RATE
PI description This KPI quantifies maximim of the Iub user plane VCC which has been reserved for DCH and HSDPA connections. This KPI provides an indication of the overall load of the Iub user plane VCC. This KPI is based upon the sum of all Iub reservations rather than actual throughput. The actual throughput could be less than or greater than the sum of the reservations.
Monitor type
PI expression 100 % * (SUM_RESERVED_CELL_RATE - SHARED_HSDPA_AAL2_ALLOCATION) / (NBR_SAMPLES * (AAL2_PATH_GUAR_CELL_RATE – MAX_SHARED_HSDPA_AAL2_ALLOC))
PI description This KPI quantifies the percentage of the Iub user plane VCC which has been reserved for DCH connections when using shared user plane VCC for both DCH and HSDPA. The calculation is based upon a user plane VCC bandwidth which has been reduced by the bandwidth which can be reserved for HSDPA. A result of more than 100 % means that it is unlikely that an HSDPA reservation would be successful. The result should be less than 70 % to allow HSDPA to make full use of the Iub bandwidth defined by the RNC databuild parameter SHFCA. This parameter has a recommended value which is 30 % greater than the reserved HSDPA bandwidth.
Note
Monitor type
PI expression (SUM_RESERVED_CELL_RATE - SHARED_HSDPA_AAL2_ALLOCATION) / (NBR_SAMPLES)
PI description This KPI quantifies the Iub user plane VCC load which has been reserved for DCH connections when using shared user plane VCC for both DCH and HSDPA. The calculation is based upon a user plane VCC bandwidth which has been reduced by the bandwidth which can be reserved for HSDPA.
Note
Monitor type
PI expression (AAL2_PATH_GUAR_CELL_RATE – (SUM_RESERVED_CELL_RATE – SHARED_HSDPA_AAL2_ALLOCATION) / NBR_SAMPLES) * (53 * 8 / 1000)
PI description This KPI quantifies the average Iub bandwidth available for HSDPA when using shared user plane VCC for both DCH and HSDPA. The result is calculated by subtracting the sum of the DCH reservations from the total Iub user plane VCC bandwidth. The average Iub bandwidth available for HSDPA provides an indication of the maximum HSDPA throughput which can be expected across the Iub. If the maximum HSDPA throughput is below the target throughput then it is likely that a capacity upgrade will be required. The resulting throughput includes the Iub overheads and should be divided by 1.25 to estimate an equivalent RLC throughput.
Note
Monitor type
PI expression SHARED_HSDPA_AAL2_ALLOCATION / NBR_SAMPLES
PI description This KPI quantifies the average Iub user plane bandwidth which has been reserved for HSDPA during the measurement period when using shared user plane VCC for both DCH and HSDPA. HSDPA throughput could be either greater than or less than the reserved bandwidth.
Note
Monitor type
PI expression 100 % * SUM_AAL2_CONNECTIONS / (NBR_SAMPLES * 248)
PI description This KPI quantifies the average percentage of simultaneous AAL2 connection identifiers which were used throughout the measurement period. The maximum possible number of simultaneous AAL2 connections per VCC is 248.
Note A high average result indicates that it may be necessary to introduce an additional VCC, i.e. a logical capacity upgrade.
Monitor type
PI expression 100 % * MAX_AAL2_CONNECTIONS / 248
PI description This KPI quantifies the maximum percentage of simultaneous AAL2 connection identifiers which were used throughout the measurement period. The maximum possible number of simultaneous AAL2 connections per VCC is 248.
Note A high maximum result indicates that it may be necessary to introduce an additional VCC, i.e. a logical capacity upgrade.
PI expression 100 % * SUM(AAL2_SUCCEEDED) / SUM(RES_EXT_CAP + RES_INT_CAP + RES_OTHER + AAL2_SUCCEEDED + AAL2_REJECTED)
PI description This KPI quantifies the success rate of AAL2 transport reservations including HSDPA. In the case of the Iub, a successful reservation includes successful admission within both the RNC and the Node B. The RNC admits the resource request and subsequently sends an AAL2 ERQ message to the Node B. The AAL2_SUCCEEDED counter is incremented if the Node B successfully returns an AAL2 ECF message. If the RNC internal reservation fails then one of RES_EXT_CAP, RES_INT_CAP or RES_OTHER is incremented. RES_EXT_CAP indicates a lack of external AAL2 resources whereas M800C2 indicates a lack of AAL2 internal resources. AAL2_REJECTED is incremented if the ERQ/ECF handshake with the Node B is rejected.
Note
PI name in Optima
PI expression 100 % * SUM(AAL2_SUCCEEDED_HSDPA)/ SUM(AAL2_SUCCEEDED_HSDPA + TRANSPORT_REJECTED_EXT_HSDPA + TRANSPORT_REJECTED_INT_HSDPA + OTHER_REJECTED_HSDPA)
PI description This KPI quantifies the success rate of the HSDPA shared AAL2 transport reservation. This KPI is applicable to the Iub. The reservation for the HSDPA shared bandwidth does not require an AAL2 ERQ/ECF handshake. The M800C6 counter is incremented if the RNC completes a successful reservation. If the reservation fails then one of M800C7, M800C8 or M800C9 is incremented. M800C7 indicates a lack of external resources whereas M800C8 indicates a lack of internal resources. M800C9 is incremented if the failure is for any other reason
Note
PI name in Optima
PI expression 100 % * [SUM(RRC_CONN_STP_FAIL _IUB_AAL2)] / [SUM(RRC_STP_ATT)]
PI description The result provides an indication of the probability of blocking for the RRC connection setup caused by ‘transport’ reasons. The RRC_CONN_STP_FAIL _IUB_AAL2 increments when the transport entity rejects the RRC connection setup due to Iub transport resource shortage between RNC and WBTS. In this case the RRC setup attempt is rejected prior to the ALCAP signalling used to reserve the Iub resources. The service level counters are applicable to the R establishment procedure and provide an indication of end user perception.
Note
PI name in Optima
PI expression 100 % * [SUM(RAB_STP_FAIL_CS_V_IUB_AAL2 )] / [SUM(RAB_STP_ATT_CS_VOICE)]
PI description The result provides an indication of the probability of blocking for the CS voice service caused by ‘Transport’ reasons. The RAB_STP_FAIL_CS_V_IUB_AAL2 increments when the transport entity rejects the RAB setup request due to Iub transport resource shortage between RNC and WBTS. In this case the RAB setup attempt is rejected prior to the ALCAP signaling used to reserve the Iub resources. The service level counters are applicable to the RAB establishment procedure and provides an indication of end user call setup perception.
PI name in Optima
PI expression 100 % * [SUM(RAB_STP_FAIL_CS_CO_IUB_AAL2)] / [SUM(RAB_STP_ATT_CS_CONV )]
PI description The result provides an indication of the probability of blocking for the CS video service caused by ‘Transport’ reasons. The RAB_STP_FAIL_CS_CO_IUB_AAL2 counter increments when the transport entity rejects the RAB setup request due to Iub transport resource shortage between RNC and WBTS. In this case the RAB setup attempt is rejected prior to the ALCAP signalling used to reserve the Iub resources. The service level counters are applicable to the RAB establishment procedure and provide an indication of end user call setup perception.
PI name in Optima
PI expression 100 % * SUM(RAB_STP_FAIL_PS_INTER_TRANS+ RAB_STP_FAIL_PS_BACKG_TRANS) / SUM(RAB_STP_ATT_PS_INTER + RAB_STP_ATT_PS_BACKG)
PI description The result provides an indication of the probability of blocking for the PS NRT data service caused by ‘Transport' reasons indicating the instances of insufficient Iub resource. In the case of the PS data service, the RAB is established with a 0/0 kbps configuration and is subsequently upgraded after either an uplink or downlink capacity request. This means that the probability of blocking during RAB establishment should be low , however the blocking of subsequent upgrades are observed in the indicator RAB_STP_FAIL_PS_X_TRANS.
Note The service level counters are updated on the main cell (The main cell being the cell with the best radio condition in the last received measurement report). Therefore in soft handover scenarios blocking indication can increment on the incorrect cell. Service level indicators should be used in conjunction with lower layer indicators to identify capacity shortfalls. The number of DCH setup failures caused by Iub AAL2 transport resource shortage for PS data. The failure can happen in FACH to DCH transition, DCH 0/0 to DCH xx/yy transition, DCH upgrade, soft handover branch addition or Intra-RNC HHO.
PI name in Optima
PI expression 100 % *SUM(SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_IUB_HS_TOTAL_BGR) / SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR+SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR + REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR + SETUP_FAIL_RNC_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_RNC_HS_DSCH_BGR + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR)
PI description The result provides an indication of the probability of blocking due to Iub for the HSDPA service. The KPI is defined by dividing the number of unsuccessful establishments for either the return channel or MAC-d flow. Counters are defined for both interactive and background services.
Note
or
or
or
Monitor KPIs
or
Monitor KPIs
-High Level Indicators-
The indicators within each counter table
Service Level
Efficiency
PI name in Optima
PI expression 100 % * SUM(RAB_STP_FAIL_CS_VOICE_AC + RAB_STP_FAIL_CS_VOICE_BTS + RAB_STP_FAIL_CS_VOICE_TRANS) / SUM(RAB_STP_ATT_CS_VOICE)
PI description The result provides an indication of the probability of blocking for the CS speech service. The failure counter with cause 'admission control' records instances of air-interface blocking. The failure counter with cause ' BTS' records instances of baseband processing blocking. The failure counter with cause 'transport' records instances of Iub blocking. This KPI should be computed on a per RNC basis as well as on a per cell basis. When computing the RNC result the individual counters should be summed on a per RNC basis. An intermediate measurement period of 1 hour has been defined to provide a balance between the quantity of KPI data generated and the resolution of that data.
Note The fail counters will update in both fault and congestion scenarios, therefore this KPI should be used in conjunction with lower layer indicators to identify capacity shortfalls.
PI name in Optima
PI expression 100 % * SUM(RAB_STP_FAIL_CS_CONV_AC + RAB_STP_FAIL_CS_CONV_BTS + RAB_STP_FAIL_CS_CONV_TRANS) / SUM(RAB_STP_ATT_CS_CONV)
PI description The result provides an indication of the probability of blocking for the CS video service. The failure counter with cause 'admission control' records instances of air-interface blocking. The failure counter with cause ' BTS' records instances of baseband processing blocking. The failure counter with cause 'transport' records instances of Iub blocking. This KPI should be computed on a per RNC basis as well as on a per cell basis. When computing the RNC result the individual counters should be summed on a per RNC basis. An intermediate measurement period of 1 hour has been defined to provide a balance between the quantity of KPI data generated and the resolution of that data.
PI name in Optima
PI expression 100 % * SUM(RAB_STP_FAIL_PS_INTER_AC + RAB_STP_FAIL_PS_INTER_TRANS + RAB_STP_FAIL_PS_BACKG_AC + RAB_STP_FAIL_PS_BACKG_TRANS) / SUM(RAB_STP_ATT_PS_INTER + RAB_STP_ATT_PS_BACKG)
PI description The result provides an indication of the probability of blocking for the PS data service. In the case of the PS data service, the RAB is established with a 0/0 kbps configuration and is subsequently upgraded after either an uplink or downlink capacity request. This means that the probability of blocking during RAB establishment should be 0 % because additional resources are not required. The KPI specified above includes failure counters which record blocking resulting from Iub transport limitations during the subsequent capacity request process, i.e. after RAB establishment. It is possible that a single RAB establishment has multiple instances of capacity requests and blocking. Service level counters are not available for the Node B baseband processing resources. In addition, the admission control (air-interface) counters are applicable to the RAB establishment phase rather than the subsequent capacity request phase.
PI expression 100 % *SUM(REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR) / SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR+SUM(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR +REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR + SETUP_FAIL_RNC_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_RNC_HS_DSCH_BGR + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR)
PI description The result provides an indication of the probability of blocking for the HSDPA service. The KPI is defined by dividing the number of unsuccessful establishments by the sum of the successful and unsuccessful establishments. Counters are defined for both interactive and background services. The failure mechanisms include: air-interface congestion for the return channel, Iub congestion for either the return channel or MAC-d flow, BTS congestion in terms of WSPC resource.
Note
PI name in Optima
PI expression 100 % * SUM(HS_DSCH_RET_DOWNGRADE_INT + HS_DSCH_RET_DOWNGRADE_BGR) / SUM(ALLO_HS_DSCH_RET_64_INT + ALLO_HS_DSCH_RET_128_INT + ALLO_HS_DSCH_RET_384_INT + ALLO_HS_DSCH_RET_64_BGR + ALLO_HS_DSCH_RET_128_BGR + ALLO_HS_DSCH_RET_384_BGR)
PI description This KPI quantifies the percentage of HSDPA return channel allocations which are downgrades. The total number of return channel allocations include upgrades, downgrades and initial allocations.
Note
PI name in Optima
PI expression SUM(ONE_CELL_IN_ACT_SET_FOR_RT + (TWO_CELL_IN_ACT_SET_FOR_RT*2) + (THREE_CELL_IN_ACT_SET_FOR_RT*3) + ONE_CELL_IN_ACT_SET_FOR_NRT + (TWO_CELL_IN_ACT_SET_FOR_NRT*2) + (THREE_CELL_IN_ACT_SET_FOR_NRT*3)) / [SUM(ONE_CELL_IN_ACT_SET_FOR_RT) + SUM(TWO_CELL_IN_ACT_SET_FOR_RT) + SUM(THREE_CELL_IN_ACT_SET_FOR_RT) + SUM(ONE_CELL_IN_ACT_SET_FOR_NRT) + SUM(TWO_CELL_IN_ACT_SET_FOR_NRT) + SUM(THREE_CELL_IN_ACT_SET_FOR_NRT)]
PI description The result represents the serving cell average active set size for real time and non-real time dedicated channel connections. The Nokia RNC allows the configuration of different soft handover parameter sets for real time and non-real time services. If different parameter sets are configured it is useful to define separate real time and non-real time KPI. Each counter represents the period of time (with units of 100 ms) that the cell belongs to an active set, the size of which is that specified. The counters are updated for every active set cell i.e. if a UE has a radio link with Cell A and a radio link with Cell B then both cells will have their TWO_CELL_IN_ACT_SET counters incremented. This KPI may be used to identify cells which exhibit high or low active set sizes.
Note If congestion is occurred on wcel which has Average Active Set Size > 1.75 or Soft Handover Overhead > 50%, Soft handover tuning should be done to minimise the use of soft handover which generates overheads in terms of Iub, Node B hardware resources and Node B transmit power.
PI expression {100% * [SUM(ONE_CELL_IN_ACT_SET_FOR_RT + (TWO_CELL_IN_ACT_SET_FOR_RT*2) + (THREE_CELL_IN_ACT_SET_FOR_RT*3) + ONE_CELL_IN_ACT_SET_FOR_NRT + (TWO_CELL_IN_ACT_SET_FOR_NRT*2) + (THREE_CELL_IN_ACT_SET_FOR_NRT*3)) / [SUM(ONE_CELL_IN_ACT_SET_FOR_RT) + SUM(TWO_CELL_IN_ACT_SET_FOR_RT) + SUM(THREE_CELL_IN_ACT_SET_FOR_RT) + SUM(ONE_CELL_IN_ACT_SET_FOR_NRT) + SUM(TWO_CELL_IN_ACT_SET_FOR_NRT) + SUM(THREE_CELL_IN_ACT_SET_FOR_NRT)] ]-1]
PI description Soft handover overhead quantifies how much overlapping there has been between cells. If congestion is occurred on wcel which has Average Active Set Size > 1.75 or Soft Handover Overhead > 50%, Soft handover tuning should be done to minimise the use of soft handover which generates overheads in terms of Iub, Node B hardware resources and Node B transmit power.
Note
Service level
HSDPA accessibility for NRT
PI name in Optima
PI expression 100 *(MOC_CONV_CALL_ATTS - MOC_CONV_CALL_FAILS + MTC_CONV_CALL_ATTS - MTC_CONV_CALL_FAILS + EMERGENCY_CALL_ATTS - EMERGENCY_CALL_FAILS ) / (MOC_CONV_CALL_ATTS + MTC_CONV_CALL_ATTS + EMERGENCY_CALL_ATTS - RRC_ATT_REP_MO_CONV - RRC_ATT_REP_MT_CONV - RRC_ATT_REP_EMERGENCY) * (RAB_ACC_COMP_CS_VOICE / RAB_STP_ATT_CS_VOICE) )
PI description This KPI quantifies the percentage of call set up success rate for CS voice (AMR) calls.
Note
Call set up success rate for PS Background and Interactive
PI name in Optima
PI expression 100 *((MOC_INTER_CALL_ATTS -MOC_INTER_CALL_FAILS + MOC_BACKG_CALL_ATTS -MOC_BACKG_CALL_FAILS + MTC_INTER_CALL_ATTS - MTC_INTER_CALL_FAILS + MTC_BACKG_CALL_ATTS -MTC_BACKG_CALL_FAILS) /(MOC_INTER_CALL_ATTS + MOC_BACKG_CALL_ATTS + MTC_INTER_CALL_ATTS + MTC_BACKG_CALL_ATTS - RRC_ATT_REP_INTERACTIVE - RRC_ATT_REP_MO_INTERACTIVE - RRC_ATT_REP_MO_BACKGROUND - RRC_ATT_REP_MT_BACKGROUND)) * ((RAB_ACC_COMP_PS_INTER +RAB_ACC_COMP_PS_BACKG ) /(RAB_STP_ATT_PS_INTER+ RAB_STP_ATT_PS_BACKG ))
PI description This KPI quantifies the percentage of call set up success rate for PS interactive and PS background calls.
Note
Call set up success rate for CS conversational (Video call)
PI name in Optima
PI expression 100 *(MOC_CONV_CALL_ATTS - MOC_CONV_CALL_FAILS + MTC_CONV_CALL_ATTS - MTC_CONV_CALL_FAILS) / (MOC_CONV_CALL_ATTS + MTC_CONV_CALL_ATTS -RRC_ATT_REP_MO_CONV - RRC_ATT_REP_MT_CONV) * (RAB_ACC_COMP_CS_CONV / RAB_STP_ATT_CS_CONV)
PI description This KPI quantifies the percentage of call set up success rate for CS converstaion (video) calls.
Note
PI name in Optima
PI expression 100* sum( ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR ) / sum( ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR + REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR + SETUP_FAIL_RNC_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_RNC_HS_DSCH_BGR + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR )
PI description The accessibility of all started allocations for HS-DSCH for NRT Traffic.
Note

Documents

3 g Capacity Monk Pi