NSN UMTS Parameter Optimization

Security Level:
NSN UMTS Parameter

Optimization
Nokia Siemens Network (NSN)
www.huawei.com
Author/ Email: Oleksand Kozlov/oleksandr.kozlov@huawei.com

Version: V1.0(20160324)
HUAWEI TECHNOLOGIES CO., LTD.
Course Content
• Production Knowledge
• Parameter Architecture
• Parameter Tuning for KPI Improvement
HUAWEI TECHNOLOGIES CO., LTD. Huawei proprietary. No spread without permission. Page 2
Slide 2
Course Objectives
• Classify parameters
• Describe usage of main parameters applying to RAN
procedures
• Identify the relations between parameters
• Describe main KPI’s and troubleshooting methods
• Specify parameters set to improve KPI’s
Slide 3
Production Knowledge
Slide 4
Introduction to NSN system
NSN 3G network is functionally divided into three elements.
-WCDMA Radio Access Network (RAN) is one of the main functional elements of the 3G network.
-The other elements in the 3G network are Core Network (CN) and operations support system.
WCDMA radio access network (RAN):

WCDMA RAN consists of one or more Radio Network Subsystems (RNS). RNS is a sub-network within RAN and it consists of one
radio network controller (RNC) and one or more base stations (BTS). RNC controls the radio network and BTS physically implements
the WCDMA radio path.
Core network (CN):

Core network has a circuit-switched domain (MSC, GMSC and VLR) and a packet-switched domain (SGSN and GGSN). CN also
consists of HLR, which handles data needed for subscriber profiles, security activities and establishing connections. Core network is
responsible for switching and routing calls and data connections to external networks. Core network also performs mobility
management together with WCDMA RAN.
Operations support system:

Operations support system is common for WCDMA, GSM and LTE. The same management system is used for managing both the
network and the services provided. In the Nokia Siemens Networks 3G solution, NetAct Framework is used for this task.
Slide 5
Network architecture
Network Interface
Note that the following interfaces

can be IP-based:
•- Iub
•- Iur
•- Iu-CS
•- Iu-PS
RNC Capacity & Connectivity RoadMap
RU10 RU20 RU30 RU40
HSPA Capacity HSPA HSPA

• HSDPA 14Mbps/user • Gigabit+ RNC196 Upgrade • DL 42 Mbps 64QAM & MIMO • DL 84 Mbps DC with MIMO
Interfaces & Features - 1.4Gbps DL + UL • UL 11 Mbps 16QAM
- 22 400 Erl AMR
• Iu-PS, Iu-CS, Iur, Iub over IP, Giga-Ethernet
- 600 BTSs
• Common Iub for RNC196/step7
- 1800 Cells
• Capacity Management Reports*
HSPA
• DL 24 Mbps
HSPA
• HSUPA 5.8 Mbps
Latency
• RNC HSPA latency <5 ms
RU50 RU60
Planned
HSPA HSPA
• DL 84 Mbps DC with MIMO • DL 168 Mbps Multi-Cell with MIMO
• Dual Band HSDPA 42 Mbps • UL 24Mbps Multi-Cell
(* on top feature
Parameter Architecture
Logical Structure of the Parameters Database Objects
WSG WANE WLCSE
RNC
CMOB WSMLC
IUCS/IUPS IUR
IPQM WRAB
COCO HOPL
HOPG
IPNB WBTS
HOPI
TQM HOPS
ADJD
FMCL
ADJS
FMCS
WCEL
ADJI
FMCI
ADJG
ADJL
FMCG
Managed Object types
• RNC = Radio Network Controller • COCO = Radio Network Connection
• WBTS = WCDMA Base Station
Configuration
• WCEL = WCDMA Cell • CMOB = Congestion Management OBject

• ADJ = Adjacency for WCDMA cell • WANE = WCDMA Authorized Network
• ADJS = intra-frequency adjacency • WSG = WCDMA subscriber group
• ADJI = inter-frequency adjacency
• WLCSE = WCDMA Location service entity
• ADJG = inter-system adjacency
• ADJD = detected adjacency • WSMLC = WCDMA Serving Mobile Location
Center
•ADJL =inter-system adjacency to LTE Network
(added to later releases)
• IPNB = IP NodeB
• HOP = Handover Path
• IPQM = IP transmission QoS
• HOPS, HOPI, HOPG , HOPL
• TQM = Transmission Quality Management
• FMC = Frequency Measurement Control
FMCS, FMCI, FMCG, FMCL • WRAB = WCEL RAB parameters
RNC Object
• The logical object of the Radio Network Controller
• It can have up to 1320 WBTS objects (for mcRNC)
• In the RNC object, the following interfaces are defined: Iu-PS, Iu-CS and
Iur
• The logical object are hierarchically related to each other, therefore it is
not possible to create any other object before RNC creation.
WBTS Object
• The logical object of the WCDMA Base Station (Node B). A WBTS can
have up to 24 WCDMA cells, one COCO and one IPNB object.
• If Iub transport QoS is used, WBTS connects to one TQM object
• Similar to UNODEBSetup
WCEL object
• The logical object of the WCDMA Cell is created to define the

configuration of the WCDMA Node B site. In one RNC database there
can be 2800 WCELs.
• Similar to UNODEBSetup
Handover Path
HOPx
• The Handover Path object stores mainly cell reselection and Intra frequency
HHO parameters. One HOPx can be related to several Adjacency objects.
• The maximum number of HOPx objects within one category is 100.
• E.g. for different type of cells (urban, rural, macro/micro/pico)
 HOP Types:
 HOPS — object for intra-frequency
Handover Path
 HOPI — object for inter-frequency
Handover Path
 HOPG — object for inter-system
Handover Path
 HOPL – object for inter-system LTE
 Handover Path
HOPx Level Parameters
Intra Frequency Inter Frequency Inter System
IntraFreqNcellHCSpriority InterFreqNcellHCSpriority GSMncellHCSpriority
IntraFreqNcellHCSthreshold InterFreqNcellHCSthreshold GSMncellHCSthreshold
IntraFreqNcellQqualMin InterFreqNcellQqualMin GSMncellQrxlevMin
IntraFreqNcellQrxlevMin InterFreqNcellQrxlevMin GSMncellPenaltyTime
IntraFreqNcellPenaltyTime InterFreqNcellPenaltyTime GSMncellQoffset1
IntraFreqNcellQoffset1 InterFreqNcellQoffset1 GSMncellTempOffset1
IntraFreqNcellQoffset2 InterFreqNcellQoffset2 HOPGId
IntraFreqNcellTempOffset1 InterFreqNcellTempOffset1
IntraFreqNcellTempOffset2 InterFreqNcellTempOffset2 AdjLAbsPrioCellReselec
EcNoAveragingWindow HOPIId AdjLQrxlevminEUTRA
EnableInterRNCsho AdjLThreshigh
EnableRRCRelease AdjLThreslow
HHOMarginAverageEcNo HOPLId
HHOMarginPeakEcNo
Idle Mode Parameters
ReleaseMarginAverageEcNo
Handover Parameters
ReleaseMarginPeakEcNo
HOPSId
Not Huawei
HUAWEI TECHNOLOGIES CO., LTD. a complete
proprietary. list
No spread without permission. Page 16
Adjacencies
ADJx
• Adjacencies for WCDMA cell refers to a handover relationship between

two cells. They are defined for neighbouring cells.
• ADJS — object for intra-frequency Adjacency
• ADJI — object for inter-frequency Adjacency
• ADJG — object for inter-system Adjacency
• ADJD — object for detected intra-frequency Adjacency
• ADJL – object for inter-system LTE Adjacency
There can be 31 intra frequency

adjacencies (ADJS), 48 inter-frequency
adjacencies (ADJI) and 32 inter-system
adjacencies (ADJG)
Handover Path objects must be created

before ADJx can be used
Adjacencies (ADJx)
IntraFreqNcellCI InterFreqNcellCI GSMncellBandIndicator
IntraFreqNcellEcNoOffset InterFreqNcellLAC GSMncellBCC
IntraFreqNcellDERR InterFreqNcellTxPwrRACH GSMncellBCCH
IntraFreqNcellLAC InterFreqNcellMCC GSMncellCI
IntraFreqNcellTxPwrRACH InterFreqNcellMNC GSMncellLAC
IntraFreqNcellMCC InterFreqNcellMNCLength GSMncellTxPwrMaxRACH
IntraFreqNcellMNC NrtHopiIdentifier GSMncellMCC
IntraFreqNcellMNCLength InterFreqNcellScrCode GSMncellMNC
HSDPAHopsIdentifier InterFreqNcellRNCid GSMncellNCC
NrtHopsIdentifier InterFreqNcellRAC NrtHopgIdentifier
IntraFreqNcellScrCode RtHopiIdentifier RtHopgIdentifier
IntraFreqNcellRNCid InterFreqNcellTxDiv ADJGId
IntraFreqNcellRAC InterFreqNcellUARFCN AdjLEARFCN
RtHopsIdentifier ADJIId AdjLMeasBw
IntraFreqNcellTxDiv HopLIdentifier
ADJSId ADJLId
Not a complete list

Detected Adjacencies (ADJD)
Intra Frequency
ADJDChangeOrigin (Change origin)
ADJDId (Identifier of additional intra-
frequency adjacency)  Optional features related to
AdjdCI (Cell Identifier) ADJD allow UE to report and
AdjdCPICHTxPwr (Primary CPICH power)
AdjdDERR (Disable Effect on Reporting
handover to cells not included
Range) in the neighbor list
AdjdHSDPAHopsId (HSDPA HOPS
identifier)
AdjdLAC (Location Area Code)
AdjdMCC (Mobile Country Code)
AdjdMNC (Mobile Network Code)
AdjdMNCLength (Mobile Network Code
Length)
AdjdNRTHopsId (NRT HOPS Identifier)
AdjdRAC (Routing Area Code)AdjdRNCId
(RNC Identifier)
AdjdRTHopsId (RT HOPS Identifier)
AdjdRTWithHSDPAHopsId (HSDPA HOPS
identifier for AMR multi-service)
AdjdScrCode (Primary Scrambling Code)
AdjdTxDiv (Tx Diversity Indicator)
Adjacencies (ADJx) to HOPx
• Every adjacency definition contains links to HOPx parameter sets
• RtHopxIdentifier defines the HOPx (x = S, I, G) parameter set that is applied
• Idle mode cell-reselections
• RT bearer intra-frequency hard handovers
• NrtHopxIdentifier defines the HOPx (x = S, I, G) parameter set that is applied
• Connected mode cell-reselections (CELL_FACH, CELL_PCH, URA_PCH)
• NRT bearer intra-frequency hard handovers
• HSDPAHopsIdentifier defines the HOPS parameter set that is applied
• For user having HS-DSCH allocated
• RTWithHSDPAHopsIdentifier defines the HOPS parameter set that is applied
• For user having HS-DSCH allocated simultaneously with AMR speech CS
RAB
Frequency Measurement Control
• The FMC object contains information concerning the frequency measurement
functionality of the RNC.
• The maximum number of frequency measurement control objects within one
category is 100.
• E.g. for different type of cells (urban, rural, macro/micro/pico)
• One FMC can be related to several WCDMA cells.
• FMC Types:
• FMCS — object for intra-frequency
• FMCI — object for inter-frequency
• FMCG — object for inter-system
• FMCL — object for inter-systemLTE
Measurement Control
FMCX Level ParametersThreshold & Trigger Handover Cause

ActiveSetWeightingCoefficient IFHOcauseCPICHEcNo GSMcauseCPICHEcNo
AdditionReportingInterval IFHOcauseCPICHrscp GSMcauseCPICHrscp
AdditionTime IFHOcauseTxPwrDL GSMcauseTxPwrDL
AdditionWindow IFHOcauseTxPwrUL GSMcauseTxPwrUL
EcNoFilterCoefficient IFHOcauseUplinkQuality GSMcauseUplinkQuality
DropTime InterFreqDLTxPwrThrAMR GsmDLTxPwrThrAMR
DropWindow InterFreqDLTxPwrThrCS GsmDLTxPwrThrCS
MaxActiveSetSize InterFreqDLTxPwrThrNrtPS GsmDLTxPwrThrNrtPS
ReplacementReportingInterval InterFreqDLTxPwrThrRtPS GsmDLTxPwrThrRtPS
ReplacementTime InterFreqMaxMeasPeriod GsmMaxMeasPeriod
ReplacementWindow InterFreqMeasAveWindow GsmMeasAveWindow
HHoEcNoCancel InterFreqMeasRepInterval GsmMeasRepInterval
HHoEcNoCancelTime InterFreqMinHoInterval GsmMinHoInterval
HHoEcNoThreshold InterFreqMinMeasInterval GsmMinMeasInterval
HHoEcNoTimeHysteresis InterFreqNcellSearchPeriod GsmNcellSearchPeriod
HHoRscpCancel InterFreqUETxPwrFilterCoeff GsmUETxPwrFilterCoeff
HHoRscpCancelTime InterFreqUETxPwrThrAMR GsmUETxPwrThrAMR
HHoRscpFilterCoefficient InterFreqUETxPwrThrCS GsmUETxPwrThrCS
HHoRscpThreshold InterFreqUETxPwrThrNrtPS GsmUETxPwrThrNrtPS
HHoRscpTimeHysteresis InterFreqUETxPwrThrRtPS GsmUETxPwrThrRtPS
IMSIbasedSHO InterFreqUETxPwrTimeHyst GsmUETxPwrTimeHyst
FMCSId FMCIId FMCGId
HUAWEI TECHNOLOGIES CO., LTD. Huawei proprietary. list without permission. Page 22
No spread
Not a complete
WCEL to FMCx
• Every WCEL definition contains links to max. 14 FMCx parameter sets
• RtFmcxIdentifier (x = S, I, G) defines the FMCx parameter set that is applied for
radio links with RT bearers
• NrtFmcxIdentifier (x = S, I, G) defines the FMCx parameter set that is applied
for radio links with only NRT bearers
• HSDPAFmcxIdentifier (x = S, I, G) defines the FMCx parameter set controlling
measurements of a user having HS-DSCH allocated
• RTWithHSDPAFmcxIdentifier (x = S, I, G) defines the FMCx parameter set
controlling measurements of a user having HS-DSCH allocated simultaneously
with AMR speech CS RAB
• HSPAFmcsIdentifier defines the FMCS parameter set controlling
measurements of a user having HS-DSCH and E-DCH allocated
• RTWithHSPAFmcsIdentifier defines the FMCS parameter set controlling
measurements of a user having HS-DSCH and E-DCH allocated
simultaneously with AMR speech CS RAB
Connection Configuration
COCO
• A new logical COCO object is created in order to reserve local transmission

resources for the WCDMA BTS.
• The COCO objects display the transmission resources in the Iub interface, but not
the actual network topology
• There can be up to TBD COCO objects
in the RNW database
WCEL RAB parameters
WRAB
• WRAB contains parameters used by Admission Control for various tasks in

configuration of radio bearers
• WCEL refers to WRAB via EbNoSetIdentifier parameter
• There can be five WRAB per RNC
NrtHopsIdentifier = 1
HOPS
Summary RtHopsIdentifier = 2 (RTwHSDPA)
HOPSid = 3
HSDPAHopsIdentifier = 6
WCEL RTwithHSDPAHopsIdentifier = 3 HOPS HOPSid = 1

(NRT)
ADJS HOPS HOPSid = 2

(RT)
WBTS WCEL
ADJSid = 1 HOPS
HOPSid = 6
(HSDPA)
NrtFmcsIdentifier = 3
WCEL Each ADJS has associated 1 HOPS for NRT, 1 for RT
RtFmcsIdentifier = 40
& 2 for HSDPA, sets can be reused for other cells.)
HSDPAFmcsIdentifier = 50
FMCSid = 1 FMCS HOPS HOPSid = 1

Each WCEL has (NRT) (NRT)
associated 1
FMCS for NRT & FMCSid = 1 FMCS HOPS
ADJD HOPSid = 5
1 for RT & 2 for (RT) (RT)
HS(D)PA, all can
be reused for FMCSid = 2 FMCS HOPS
(HS(D)PA) ADJDid = 1 HOPSid = 7
other cells. (HSDPA)
FMCSid = 2 FMCS HOPS HOPSid = 3

(RT&HS(D)PA) (RTwHSDPA)
Parameters Tuning for KPI Improvement
Factors Affecting Network Performance
 Many factors and network elements can affect the network performance. Here
are some of the main examples:
• Quality of network equipment, both hardware and software – BTS, RNC, PS
Core, CS Core and transmission equipment
• Performance of UE and field measurement tools – inter-operability, sensitivities
of measurement parameters, level of accuracy
• Quality of network planning and optimization – coverage, interference,
parameter tuning, capacity dimensioning
• Quality of network implementation - site and network equipment installation,
integration and commissioning
• Quality of network operation and maintenance
• Multi-vendor environment – Application servers, IP Backbone
• Measurement method – test setup, service dependent, cluster or system level,
area type (dense urban, urban, suburban, rural).
UE Impact on Performance
 The functionality of different UEs are not similar, there are differences in
• Power control (RACH process)
• SRNC relocation support
• Cell FACH/PCH performance
• Cell reselection/inter RAT cell reselection
• Throughput (during SHO)
• UE power consumption
• UE power spiking
• UE Measurement performance (cell_DCH, cell reselection, ISHO)
• UE Sensitivity
• Data card throughputs
 The malfunctioning of certain UEs will naturally cause drops in setup of
active phase
KPI Definitions
 The KPIs to be monitored from the RAN could be:
• Cell availability
• Call Setup Success Rate (CSSR)
• Call Drop rate
• SHO/ISHO/HSPA SCC success rate
• Packet Session setup/success rate (NRT, HSDPA, HSUPA)
 In Libraries:
• RNC counter description
• NetAckt DB description for RNC measurements
• WCDMA RAN Key Performance Indicators
• Key Indicator Changes
• Measurement Changes
KPIs and Target Values
Average Value Maximal Value
KPI # Name "Optimised" "Well optimised"
RNC_727a Cell Availability excluding blocked by User 99.50% 99.90%
RNC_154d RRC Connection Setup and Access Complete Ratio 98% 99.50%
RNC_565f Call Setup Success Ratio for AMR call 98% 99.50%
RNC_618a RAB Setup Success Ratio for Streaming Call 99% 99.50%
RNC_916a Packet Session Setup Success Ratio 98% 99.50%
RNC_922a Packet Session Success Rate 97.50% 98%
RNC_231c RAB Success Ratio, AMR Voice 99.20% 99.80%
RNC_232c RAB Success Ratio, CS Conv 99.20% 99.80%
RNC_619a RAB Success Ratio, Streaming 98.20% 99.20%
RNC_736a RAB Success Ratio, NRT Services 98.20% 99.20%
RNC_217d RRC Connection Success Ratio 99% 99.70%
RNC_153b Soft Handover Success Ratio, RT 99.70% 99.90%
RNC_192b Soft Handover Success Ratio, NRT 99.70% 99.90%
RNC_305a Inter-frequency Hard HO Success Rate (RT+NRT) 97% 98%
RNC_300a Inter-System Hard HO Success Rate, RT 96% 98%
RNC_301a Inter-System Hard HO Success Rate, NRT 95% 97%
KPIs and Target Values Cont. - HSPA
Average Value Maximal Value "Well

KPI # Name "Optimised" optimised"
RNC_733a HSDPA Serving Cell Change Success Rate 98% 99.50%
RNC_605a HSDPA accessibility 97.50% 99.00%
RNC_609a HSDPA Retainability 97% 99%
RNC_914a HSDPA Setup Success Rate 97% 99%
RNC_920a HSDPA Success Rate 97.50% 97%
RNC_607a HSDPA Mac_hs Efficiency 93% 96%
Cell Availability
 RNC_183c Cell Availability KPI counts Cell availability

from user point 100 * sum AVAIL _ WCELL _ IN _ WO _ STATE 
Cell _ Availabili ty  of view:
sum AVAIL _ WCELL _ EXIST _ IN _ RNW _ DB 
M1000C178 AVAILABILITY WCELL IN WORKING STATE

• # of samples when WCELL is in WO State. Counter M1000C180 is always updated along with this counter
• Counter is updated with the value 1 once in approx. 5 seconds when the WCELL is in WO State
M1000C180 AVAILABILITY WCELL EXIST IN RNW DATABASE
• # of samples when WCELL is configured in the database. This counter is used as a denominator for cell availability
calculation
• Counter is updated with the value 1 one in approx. 5 seconds when the WCELL is configured in the radio network
database
Cell Availability
 RNC_727a Cell Availability KPI, excluding blocked by user

state (BLU), _Counts Cell 100 * sum AVAIL _ WCELL _ IN _ WO _ STATE 
Cell _ Availabili ty _ excluding BLU _ state  availability from network point of
 AVAIL _ WCELL _ EXIST _ IN _ RNW _ DB 
view: sum 
  AVAIL _ WCELL _ BLOCKED _ BY _ USER 
M1000C179 AVAILABILITY WCELL BLOCKED BY USER

• # of samples when WCELL is BLU State. Counter M1000C180 is always updated along with this counter
• Counter is updated with the value 1 once in approx. 5 seconds when the WCELL is in BLU state
Call Setup Success Rate (CSSR)
 Poor CSSR could be a result of
• Poor coverage or dominance or interference issues in Radio interface
• Capacity issues in Radio or Iub interface
• Configuration issues in WBTS (parameters or HW)
 CSSR is essentially RRC Setup Success * RAB Setup Success

(or successful PS session setups in case of PS call)
 CSSR covers all the steps from the initial RRC connection request from the UE to the
network, through the RRC setup phase and the RAB setup phase, and until user data
is starting to get transferred.
 The CSSR formulas are for different traffic classes like:

• CS voice calls (RNC 565 f)
• CS video calls (RNC 566e)
• PS RT Streaming Calls (RNC 575 d)
• PS NRT Calls (Interactive & Background) (RNC 576d)
Definition of Call Set-Up Success Rate
(CSSR) RNC CN
UE BTS
RRC: Connection Request
RRC Connection Setup phase
Resource Reservation in RNC, BTS, Transmission
RRC: RRC Connection Request Setup
RRC Connection Access phase
RNC waits reply from UE
RRC: RRC Connection Completed
RRC: Initial Direct Transfer cm service request
RANAP: Initial UE Message
DIRECT TRANSFER (Call
Call Set-
Proceeding)
RANAP: RAB Assignment up
Request Success
RAB Connection Setup phase Rate
Resource Reservation in RNC, BTS, Transmission
Call Set-
RRC: Radio Bearer Set-up up Time
RAB Connection Access phase
RNC waits reply from UE
RRC: Radio Bearer Setup
Complete RANAP: RAB Assignment
DIRECT TRANSFER (Alerting) Response
DIRECT TRANSFER (Connect)
DIRECT TRANSFER (Connect
Acknowledge)
Call Setup Success Rate (CSSR)
 CSSR KPI for CS voice from end user perspective (RNC 565f)
100 * ( sum( MOC _ CONV _ CALL _ ATTS  MOC _ CONV _ CALL _ FAILS
 MTC _ CONV _ CALL _ ATTS  MTC _ CONV _ CALL _ FAILS
 EMERGENCY _ CALL _ ATTS  EMERGENCY _ CALL _ FAILS
 RRC _ ACC _ REL _ EMERGENCY  RRC _ ACC _ REL _ MO _ CONV
 RRC _ ACC _ REL _ MT _ CONV ) ( sum( RAB _ ACC _ COMP _ CS _ VOICE )
AMR _ CSSR  *
sum( MOC _ CONV _ CALL _ ATTS  MTC _ CONV _ CALL _ ATTS sum( RAB _ STP _ ATT _ CS _ VOICE ))
 EMERGENCY _ CALL _ ATTS  RRC _ ATT _ REP _ MO _ CONV
 RRC _ ATT _ REP _ MT _ CONV  RRC _ ATT _ REP _ EMERGENCY
 RRC _ ACC _ REL _ EMERGENCY  RRC _ ACC _ REL _ MO _ CONV
 RRC _ ACC _ REL _ MT _ CONV  RRC _ CONN _ STP _ REJ _ EMERG _ CALL) RAB part
RRC part
 RRC request repetitions done by UE after RRC reject are excluded from denominator (not
necessarily seen as failures from the user's perspective)
 Emergency calls re-directed to GSM layer are excluded from denominator
 The occurred cell re-selections are subtracted both from the numerator and denominator
because they are not considered as call attempts from mobile end-user point of view. The
UE has made a new RRC connection via another cell and Attempts-counter is updated in
the new cell for the new attempt.
PS Call Setup Success Rate (CSSR)
• RNC_576e Packet Call Setup Success Ratio [%] over the reporting period.
• Includes both Interactive and Background PS calls
• Counts from RRC request until RAB is established (with 0/0 RB)
100 * ( sum ( 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
 EMERGENCY _ CALL _ ATTS  EMERGENCY _ CALL _ FAILS
 RRC _ ACC _ REL _ INTER  RRC _ ACC _ REL _ MO _ BACKG ( sum ( RAB _ ACC _ COMP _ PS _ INTER
 RRC _ ACC _ REL _ MO _ INTER  RRC _ ACC _ REL _ MT _ BACKG )  RAB _ ACC _ COMP _ PS _ BACKG )
PS _ CSSR  *
sum ( MOC _ INTER _ CALL _ ATTS  MOC _ BACKG _ CALL _ ATTS sum ( RAB _ STP _ ATT _ PS _ INTER
MTC _ INTER _ CALL _ ATTS  MTC _ BACKG _ CALL _ ATTS  RAB _ STP _ ATT _ PS _ BACKG ))
 RRC _ ATT _ REP _ INTER  RRC _ ATT _ REP _ MO _ INTER
 RRC _ ATT _ REP _ MO _ BACKG  RRC _ ATT _ REP _ MT _ BACKG
 RRC _ ACC _ REL _ INTER  RRC _ ACC _ REL _ MO _ BACKG
RRC part  RRC _ ACC _ REL _ MO _ INTER  RRC _ ACC _ REL _ MT _ BACKG ))
RAB part
 Same as CSSR for AMR, except:
 Emergency calls not included
 Counters for NRT RAB instead of Voice RAB
Packet Call: HSPA setup success radio
 RNC_914 HSDPA setup success ratio from User point of view
RNC_914b HSDPA Setup Success Ratio from User Perspectiv e[%] 
M1022C21 HS_E_REQ_H S_E_ALLO_I NT + M1022C21 HS_E_REQ_H S_E_ALLO_B GR 
  M1022C23 HS_E_REQ_H S_D_ALLO_I NT + M1022C24 HS_E_REQ_H S_D_ALLO_B GR 
+ M1022C25 HS_D_REQ_H S_D_ALLO_I NT + M1022C26 HS_D_REQ_H S_D_ALLO_B GR
M1022C3 PS_ATT_HSD SCH_EDCH_I NT + M1022C4 PS_ATT_HSD SCH_EDCH_B GR 
M1022C5 PS_ATT_HSD SCH_DCH_IN T + M1022C6 PS_ATT_HSD SCH_DCH_BG R 
 M1022C221 HS_D_REQ_D _D_ALLO_BG R_CELL  M1022C220 HS_D_REQ_D _D_ALLO_IN T_CELL 
M1022C218 HS_E_REQ_D _D_ALLO_BG R_CELL  M1022C217 HS_E_REQ_D _D_ALLO_IN T_CELL
 RNC_915b HSUPA setup success ratio from User perspective

RNC_915b HSUPA Setup Success Ratio from User Perspectiv e[%] 
 M1022C21 HS_E_REQ_H S_E_ALLO_I NT + M1022C21 HS_E_REQ_H S_E_ALLO_B GR
M1022C3 PS_ATT_HSD SCH_EDCH_I NT + M1022C4 PS_ATT_HSD SCH_EDCH_B GR 
 M1022C215 HS_E_REQ_H S_D_ALLO_B GR_CELL  M1022C214 HS_E_REQ_H S_D_ALLO_I NT_CELL
M1022C218 HS_E_REQ_D _D_ALLO_BG R_CELL  M1022C217 HS_E_REQ_D _D_ALLO_IN T_CELL
RAB Success Ratio (Drop call rate)
• Call is dropped if one (or more) of the following RAB, RB or RL, drops.
• PS call drop is different than the other call type drops, RAB service can still exits even if
the RB and/or RL drops
• Poor RAB success ratio could be reason of coverage or interference issues, SHO
problems, missing neighbour, inter RNC problems, just to mention some
• Call Drop rate (CDR) is calculated based on RAB activation failures, it can be defined
separately for different services
 Normal RAB releases are taken into account
 Drops during the signalling are not included
RAB Success Ratio, Voice (CSR)
 RNC_231d – RAB Success KPI for CS Voice from end user perspective
For Voice, the

release due to pre-
emption is included
100  100 * sum( RAB _ ACT _ REL _ CS _ VOICE _ P _ EMP
 RAB _ ACT _ FAIL _ CS _ VOICE _ IU  RAB _ ACT _ FAIL _ CS _ VOICE _ RADIO
 RAB _ ACT _ FAIL _ CS _ VOICE _ BTS  RAB _ ACT _ FAIL _ CS _ VOICE _ IUR
 RAB _ ACT _ FAIL _ CS _ VOICE _ RNC  RAB _ ACT _ FAIL _ CS _ VOICE _ UE )
RNC _ 231d 
sum( RAB _ ACT _ COMP _ CS _ VOICE  RAB _ ACT _ REL _ CS _ VOICE _ SRNC
 RAB _ ACT _ REL _ CS _ VOICE _ P _ EMP  RAB _ ACT _ REL _ CS _ V _ UNSPE _ ER _ CN
 RAB _ ACT _ FAIL _ CS _ VOICE _ IU  RAB _ ACT _ FAIL _ CS _ VOICE _ RADIO
 RAB _ ACT _ FAIL _ CS _ VOICE _ BTS  RAB _ ACT _ FAIL _ CS _ VOICE _ IUR
 RAB _ ACT _ FAIL _ CS _ VOICE _ RNC  RAB _ ACT _ FAIL _ CS _ VOICE _ UE)
 Covers RAB Active Phase of a call. Probability that call has ended normally after setup
has been successful. This is taking into notice just calls which has ended this cell, but
might have been started in other cells.
RAB Success Ratio, NRT service
 RNC_736b - RAB Success Ratio for NRT Services [%] from user perspective
over the reporting period.
 Covers RAB Active Phase of a call. Includes both Interactive and Background
PS calls.
100  100 * sum( RAB _ ACT _ FAIL _ PS _ INTER _ IU  RAB _ ACT _ FAIL _ PS _ INTER _ RADIO Both Interactive
 RAB _ ACT _ FAIL _ PS _ INTER _ BTS  RAB _ ACT _ FAIL _ PS _ INTER _ IUR
 RAB _ ACT _ FAIL _ PS _ INTER _ RNC  RAB _ ACT _ FAIL _ PS _ INTER _ UE
and Background PS
RAB _ ACT _ FAIL _ PS _ BACKG _ IU  RAB _ ACT _ FAIL _ PS _ BACKG _ RADIO calls
 RAB _ ACT _ FAIL _ PS _ BACKG _ BTS  RAB _ ACT _ FAIL _ PS _ BACKG _ IUR
 RAB _ ACT _ FAIL _ PS _ BACKG _ RNC  RAB _ ACT _ FAIL _ PS _ BACKG _ UE
 RAB _ ACT _ FAIL _ PS _ BACKG _ PCH  RAB _ ACT _ FAIL _ PS _ INTER _ PCH )
RNC _ 736b 
sum ( RAB _ ACT _ COMP _ PS _ INTER  RAB _ ACT _ COMP _ PS _ BACKG
 RAB _ ACT _ REL _ PS _ INTER _ SRNC   RAB _ ACT _ REL _ PS _ BACKG _ SRNC
 RAB _ ACT _ FAIL _ PS _ INTER _ IU  RAB _ ACT _ FAIL _ PS _ BACKG _ IU
RAB _ ACT _ FAIL _ PS _ INTER _ RADIO  RAB _ ACT _ FAIL _ PS _ BACKG _ RADIO
 RAB _ ACT _ FAIL _ PS _ INTER _ BTS  RAB _ ACT _ FAIL _ PS _ BACKG _ BTS
 RAB _ ACT _ FAIL _ PS _ INTER _ IUR  RAB _ ACT _ FAIL _ PS _ BACKG _ IUR
 RAB _ ACT _ FAIL _ PS _ INTER _ RNC  RAB _ ACT _ FAIL _ PS _ BACKG _ RNC
 RAB _ ACT _ FAIL _ PS _ INTER _ UE  RAB _ ACT _ FAIL _ PS _ BACKG _ UE )
• For NRT RABs pre-emption is not possible

• As the formula is based on active fail counters is means in this case that when RAB drops in
CELL_PCH state that two fail counters are updated. This is taken into account in the formula (the
drops in CELL_PCH subtracted from all drops.)
HSDPA Retainability
 Current RNC_609a HSDPA Retainability for NRT Traffic
M1002C407 REL_ALLO_N ORM_HS_DSC H_INT  M1002C410 REL_ALLO_N ORM_HS_DSC H_BGR
RNC _ 609a  100%
M1002C407 REL_ALLO_N ORM_HS_DSC H_INT  M1002C410 REL_ALLO_N ORM_HS_DSC H_BGR 
 M1002C408REL_ALLO_OT H_FAIL_HSD SCH_INT  M1002C411REL_ALLO_OT H_FAIL_HSD SCH_BGR 
 M1002C479REL_ALLO_RL _FAIL_HS_D SCH_INT  M1002C482REL_ALLO_RL _FAIL_HS_D SCH_BGR
 The normal transition from HS-DSCH to FACH/DCH are considered

as a normal HS-DSCH release (including transitions due to mobility
and pre-emption)
 The fallbacks and other possible normal release counters are not
separately included in the formula, as they are already included in
the Normal release counters
HSUPA resource retainability
(REL_EDCH_ NORM_INT  REL_EDCH_N ORM_BGR 
REL_EDCH_H SDSCH_SCC_INT  REL_EDCH_H SDSCH_SCC_BGR)
RNC _ 919b  100%
(REL_EDCH_ NORM_INT  REL_EDCH_N ORM_BGR 
REL_EDCH_H SDSCH_SCC_INT  REL_EDCH_H SDSCH_SCC_BGR 
REL_EDCH_R L_FAIL_INT  REL_EDCH_R L_FAIL_BGR 
REL_EDCH_O THER_FAIL_ INT  REL_EDCH_O THER_FAIL_ BGR)
R99 Success Ratio from user perspective
for NRT
 Counters for normal release includes releases due to

RNC_ 944a R99 Success Ratio from End User Perspective [%] 
SRNC relocation, hard handovers etc
M 1022C 61 PS_REL_RL _FAIL_D_D_ INT  M 1022C 62 PS_REL_RL _FAIL_D_D_ BGR 

 M 1022C 67 PS_REL_OT H_FAIL_D_D _INT  M 1022C 68 PS_REL_OT H_FAIL_D_D _BGR
1
M 1022C 61 PS_REL_RL _FAIL_D_D_ INT  M 1022C 62 PS_REL_RL _FAIL_D_D_ BGR 
  M 1022C 67 PS_REL_OT H_FAIL_D_D _INT  M 1022C 68 PS_REL_OT H_FAIL_D_D _BGR 
 M 1022C 49 PS_REL_NORM_D_D_INT  M 1022C 50 PS_REL_NORM_D_D_BGR
HSDPA Success Ratio from user perspective for NRT
 The HSDPA Success Ratio for Interactive and Background Services from user
perspective
 This KPI is based on Packet Call Measurement
RNC_ 920a HSDPA Success Ratio From User Perspective 
M 1022C 57 PS_REL_RL_FAIL_HS_E_INT+ M 1022C 58 PS_REL_RL_FAIL_HS_E_BGR

+ M 1022C 59 PS_REL_RL_FAIL_HS_D_INT+ M 1022C 60 PS_REL_RL_FAIL_HS_D_BGR
 + M 1022C 63 PS_REL_OTH_FAIL_HS_E_INT+ M 1022C 64 PS_REL_OTH_FAIL_HS_E_BGR
+ M 1022C 65 PS_REL_OTH_FAIL_HS_D_INT+ M 1022C 66 PS_REL_OTH_FAIL_HS_D_BGR
 1 M 1022C 57 PS_REL_RL_FAIL_HS_E_INT+ M 1022C 58 PS_REL_RL_FAIL_HS_E_BGR  100%
+ M 1022C 59 PS_REL_RL_FAIL_HS_D_INT+ M 1022C 60 PS_REL_RL_FAIL_HS_D_BGR
+ M 1022C 63 PS_REL_OTH_FAIL_HS_E_INT+ M 1022C 64 PS_REL_OTH_FAIL_HS_E_BGR
 + M 1022C 65 PS_REL_OTH_FAIL_HS_D_INT+ M 1022C 66 PS_REL_OTH_FAIL_HS_D_BGR
+ M 1022C 45 PS_REL_NORM_HS_E_INT+ M 1022C 46 PS_REL_NORM_HS_E_BGR 
+ M 1022C 47 PS_REL_NORM_HS_D_INT+ M 1022C 48 PS_REL_NORM_HS_D_BGR
HSUPA Success-M1022
 The HSUPA Success Ratio for Interactive and Background Services from user
perspective
 This KPI is based on Packet Call Measurement (M1022)
RNC_921aHSUPA SuccessRatio FromUser Perspective 
+ M1022C63PS_REL_OTH_FAIL_HS_E_INT + M1022C64PS_REL_OTH_FAIL_HS_E_BGR
M1022C57PS_REL_RL_FAIL_HS_E_INT + M1022C58PS_REL_RL_FAIL_HS_E_BGR 
100%  100%
+ M1022C45PS_REL_NORM_HS_E_INT+ M1022C46PS_REL_NORM_HS_E_BGR
+ M1022C63PS_REL_OTH_FAIL_HS_E_INT + M1022C64PS_REL_OTH_FAIL_HS_E_BGR 
 RNC_921b include PS streaming traffic also
Packet Session success ratio
 All NRT sessions, 100 % -drop rate
RNC_922aPacket Session SuccessRatio [% ] 

+ M1022C59PS_REL_RL_FAIL_HS_D_INT  M1022C60PS_REL_RL_FAIL_HS_D_BGR 
+ M1022C63PS_REL_OTH_FAIL_HS_E_INT + M1022C64PS_REL_OTH_FAIL_HS_E_BGR
+ M1022C61PS_REL_RL_FAIL_D_D_INT + M1022C62PS_REL_RL_FAIL_D_D_BGR 
+ M1022C65PS_REL_OTH_FAIL_HS_D_INT + M1022C66PS_REL_OTH_FAIL_HS_D_BGR 
+ M1022C67PS_REL_OTH_FAIL_D_D_INT + M1022C68PS_REL_OTH_FAIL_D_D_BGR
100%  100% 
+ M1022C59PS_REL_RL_FAIL_HS_D_INT + M1022C60PS_REL_RL_FAIL_HS_D_BGR 
+ M1022C61PS_REL_RL_FAIL_D_D_INT + M1022C62PS_REL_RL_FAIL_D_D_BGR 
+ M1022C63PS_REL_OTH_FAIL_HS_E_INT + M1022C64PS_REL_OTH_FAIL_HS_E_BGR 
++ M1022C65PS_REL_OTH_FAIL_HS_D_INT + M1022C66PS_REL_OTH_FAIL_HS_D_BGR 
M1022C67PS_REL_OTH_FAIL_D_D_INT + M1022C68PS_REL_OTH_FAIL_D_D_BGR 
+ M1022C45PS_REL_NORM_HS_E_INT+ M1022C46PS_REL_NORM_HS_E_BGR
+ M1022C47PS_REL_NORM_HS_D_INT+ M1022C48PS_REL_NORM_HS_D_BGR
+ M1022C49PS_REL_NORM_D_D_INT+ M1022C50PS_REL_NORM_D_D_BGR
SHO success rate
• SHO success rate KPI (195a) is informing how many successful Active set updates we will have
compared to initial Addition/Replacement/Deletion requests.
• This formula is excluding periodical reports, which might occur if for example RNC is busy and
cannot process immediately initial request.
100 * sum( SUCC _ UPDATES _ ON _ SHO _ FOR _ RT  SUCC _ UPDATES _ ON _ SHO _ FOR _ NRT )
SHO _ Success 
sum(CELL _ ADD _ REQ _ ON _ SHO _ FOR _ RT  CELL _ REPL _ REQ _ ON _ SHO _ FOR _ RT
 CELL _ DEL _ REQ _ ON _ SHO _ FOR _ RT  CELL _ ADD _ REQ _ ON _ SHO _ FOR _ NRT
 CELL _ REPL _ REQ _ ON _ SHO _ FOR _ NRT  CELL _ DEL _ REQ _ ON _ SHO _ FOR _ NRT )
UE BTS RNC
RRC: Measurement Report (e1a / e1c)
Decision to
set up new RL
SUCC_UPDAT ES_ON_SHO NUMBER OF SUCCESSFUL AS UPDATE
NBAP: Radio Link Setup Request – for Soft Handover FOR THE CELL UNDER OBSERVATION
NBAP: Radio Link Addition Request – for Softer Handover CELL_ADD_R EQ_ON_SHO 
Start TX/RX CELL_DEL_R EQ_ON_SHO 
NBAP: Radio Link Setup Response TOTAL NUMBER OF NOT PERIODOICAL
NBAP: Radio Link Addition Response
CELL_REPL_ REQ_ON_SHO MEASUREMENT REPORT (1A,1B,1C)
ALCAP:ERQ
RECEIVED BY THE CELL UNDER OBSERVATION
ALCAP:ECF
RRC: Active Set Update
RRC: Active Set Update Complete UPDATED FOR ALL THE CELLS WITHIN AS WHEN MEAS. REPORT IS RECEIVED
RECEIVED
ISHO Success Rate
 Normally ISHO may fail due to missing target cell or the cell is not good enough
• coverage
• interference
• configuration problem
• capacity limitation
 From the measurement point of view the ISHO is divided into two phases:
• Inter-system measurement
• Inter-system handover
 The RT and NRT Inter System HO differs in nature. Therefore the ISHO KPI can be spitted in RT
and NRT parts
 In case of Multi-RAB having at least one RT RAB only RT counters are updated and the
Handover is performed using RT handover procedure
ISHO Success Rate, RT
 KPIs for ISHO measurement started for RT and NRT (RNC_294c, RNC_295c)
 KPIs for not good enough cells for RT and NRT, RNC_296a, and RNC_297a)
 ISHO success rate for RT services (RNC_300g)
LB –Load Base HO
100 * sum( SUCC _ IS _ HHO _ UL _ DCH _ Q _ RT  SUCC _ IS _ HHO _ UE _ TRX _ PWR _ RT
 SUCC _ IS _ HHO _ DL _ DPCH _ PWR _ RT  SUCC _ IS _ HHO _ CPICH _ RSCP _ RT
SB-Service Base HO
 SUCC _ IS _ HHO _ CPICH _ ECNO _ RT  SUCC _ IS _ HHO _ IM _ IMS _ RT
 SUCC _ IS _ HHO _ EMERG _ CALL  SUCC _ IS _ HHO _ LB _ PRX _ TOT _ RT
 SUCC _ IS _ HHO _ LB _ PTX _ TOT _ RT  SUCC _ IS _ HHO _ LB _ RES _ LIM _ RT
 SUCC _ IS _ HHO _ LB _ RSVR _ SC _ RT  SUCC _ IS _ HHO _ SB _ RT )
ISHO _ Success _ RT 
sum( IS _ HHO _ ATT _ UL _ DCH _ Q _ RT  IS _ HHO _ ATT _ UE _ TRX _ PWR _ RT
 IS _ HHO _ ATT _ DL _ DPCH _ PWR _ RT  IS _ HHO _ ATT _ CPICH _ RSCP _ RT
 IS _ HHO _ ATT _ CPICH _ ECNO _ RT  IS _ HHO _ ATT _ IM _ IMS _ RT
 IS _ HHO _ ATT _ EMERG _ CALL  IS _ HHO _ ATT _ LB _ PRX _ TOT _ RT
 IS _ HHO _ ATT _ LB _ PTX _ TOT _ RT  IS _ HHO _ ATT _ LB _ RES _ LIM _ RT
 IS _ HHO _ ATT _ LB _ RSVR _ SC _ RT  IS _ HHO _ ATT _ SB _ RT )
• ISHO success rate for NRT services (RNC_301c)
ISHO Success Rate, NRT
• ISHO success rate for NRT services (RNC_301e)

100 * sum( SUCC _ IS _ HHO _ UL _ DCH _ Q _ NRT  SUCC _ IS _ HHO _ UE _ TRX _ PWR _ NRT
 SUCC _ IS _ HHO _ DL _ DPCH _ PWR _ NRT  SUCC _ IS _ HHO _ CPICH _ RSCP _ NRT
 SUCC _ IS _ HHO _ CPICH _ ECNO _ NRT  SUCC _ IS _ HHO _ IM _ IMS _ NRT
 SUCC _ IS _ HHO _ LB _ CAPA _ DL _ NRT  SUCC _ IS _ HHO _ LB _ CAPA _ UL _ NRT
 SUCC _ IS _ HHO _ LB _ PRX _ TOT _ NRT  SUCC _ IS _ HHO _ LB _ PTX _ TOT _ NRT
 SUCC _ IS _ HHO _ LB _ RES _ LIM _ NRT  SUCC _ IS _ HHO _ LB _ RSVR _ SC _ NRT
 SUCC _ IS _ HHO _ SB _ NRT )
RNC _ 301e 
sum( IS _ HHO _ ATT _ UL _ DCH _ Q _ NRT  IS _ HHO _ ATT _ UE _ TRX _ PWR _ NRT
 IS _ HHO _ ATT _ DL _ DPCH _ PWR _ NRT  IS _ HHO _ ATT _ CPICH _ RSCP _ NRT
 IS _ HHO _ ATT _ CPICH _ ECNO _ NRT  IS _ HHO _ ATT _ IM _ IMS _ NRT
 IS _ HHO _ ATT _ LB _ CAPA _ DL _ NRT  IS _ HHO _ ATT _ LB _ CAPA _ UL _ NRT
 IS _ HHO _ ATT _ LB _ PRX _ TOT _ NRT  IS _ HHO _ ATT _ LB _ PTX _ TOT _ NRT
 IS _ HHO _ ATT _ LB _ RES _ LIM _ NRT  IS _ HHO _ ATT _ LB _ RSVR _ SC _ NRT
 IS _ HHO _ ATT _ SB _ NRT )
HS-DSCH Serving Cell Change
 The HS-DSCH Serving Cell Change success rate can be calculated as below
SCC _ INTRA _ BTS _ SUCCESSFUL  SCC _ INTER _ BTS _ SUCCESSFUL

RNC _ 733 A  100% 
SCC _ STARTED _ CPICH _ ECNO  SCC _ STARTED _ UL _ SIR _ ERROR 
SCC _ STARTED _ ACTIVE _ SET _ UPD  SCC _ STARTED _ OTHER _ REASON
 It should be noted that the KPI above is not very accurate in cell level as
denominator is incremented in the source cell (old serving cell) and numerator
is incremented in the target cell (new serving cell)
 So this KPI is useful in RNC level
 However in case the SCC failure rate is calculated then it is possible to find
out under which HS-DSCH serving cell plenty of SCCs are failing (but this
will not tell the cell to which the SCC is failing)
SCC_FAILED_DUE_TO_UE  SCC_FAILED_DUE_TO_BT S  SCC_FAILED_DUE_TO_TRANSM 
SCC_FAILED_DUE_TO_AC  SCC_FAILED_DUE_TO_OT HER
SCC Failure Rate  100% 
SCC _ STARTED _ CPICH _ ECNO  SCC _ STARTED _ UL _ SIR _ ERROR 
SCC _ STARTED _ ACTIVE _ SET _ UPD  SCC _ STARTED _ OTHER _ REASON
E-DCH Serving Cell Change
 The E-DCH Serving Cell Change initiations can be calculated as below
RNC _ 929a HSUPASCC Attemps M1008C239EDCH _ SCC _ STARTED
 The E-DCH SCC success ratio can be calculated as below

RNC_918aHSUPA ServingCell ChangeSuccessRate 
100% 
 M1008C240EDCH_SCC_INTRA_BTS_SUCCESS + M1008C241EDCH_SCC_INTER_BTS_SUCCESS
M1008C239EDCH_SCC_STARTED
Cell Throughput Measurements
 R99 NRT Throughput DL
RNC_1174a  NRT DCH MAC - d Throughput DL [kbit/s]

 M1023C7 NRT_DCH_DL _DATA_VOL  8
1000  PERIOD_DUR ATION  60
R99 NRT DL MAC - d Data Volume at RNC [kbit]

 M1023C7 NRT_DCH_DL _DATA_VOL  8
1000
 R99 NRT Throughput UL
RNC_1173a  NRT DCH MAC - d Throughput UL [kbit/s]

 M1023C6 NRT_DCH_UL _DATA_VOL  8
RNC_1175a  HSDPA UL return channel Throughput [kbit/s]

 M1023C9 NRT_DCH_HS DPA_UL_DAT A_VOL  8
R99 NRT UL MAC - d Data Volume at RNC [kbit]

 M1023C6 NRT_DCH_UL _DATA_VOL  8
1000
 HS-DSCH Throughput
RNC_941a  HSDPA MAC - d Average Throughput at RNC [kbit/s]

 M1023C8 HS_DSCH_DA TA_VOL  8
HSDPA MAC - d Data Volume at RNC [kbit]

 M1023C8 HS_DSCH_DA TA_VOL  8
1000
 E-DCH Throughput can be measured by RNC_952a/c
RNC _ 952a HSUPA MAC - es Average Throughput at RNC [kbit/s]

 M1023C10 _ NRT_EDCH_H SDPA_UL_DA TA_VOL  8
RNC _ 952c  HSUPA MAC - es Average Throughput at RNC [Mbit/s]

 M1023C10 NRT_EDCH_H SDPA_UL_DA TA_VOL  8  M1023C23 RT_E_DCH_U L_STREA_DA TA
RNC _ 931a HSUPA MAC - es Data Volume at RNC [Mbit]

 M 1023C10 _ NRT_EDCH_ HSDPA_UL_DATA_VOL  8
1000000
HSDPA Data Volume and Throughput
 The average active HS-DSCH MAC-d throughput from network perspective calculated as
the HSDPA MAC-d throughput at BTS, divided by the active HS-DSCH time from the
network perspective
 The active time refers to the scheduled TTIs, i.e. when sending data
 The throughput is looked at from MAC-d layer, i.e. how much MAC-d level data the HS-
DSCH is able to successfully transfer to UEs using the scheduled TTIs, so this considers
also the MAC-hs efficiency
RNC _ 722b[kbps]
 M5000C126 RECEIVED_H S_MACD_BIT S - M5000C127 DISCARDED_ HS_MACD_BI TS 
 M5000C69 HS_SCCH_PWR_DIST_CLA SS_0  M5000C70 HS_SCCH_PWR_DIST_CLA SS_1 
 
   M5000C71 HS_SCCH_PWR_DIST_CLA SS_2  M5000C72 HS_SCCH_PWR_DIST_CLA SS_3 
  M5000C73 HS_SCCH_PWR_DIST_CLA SS_4  M5000C74 HS_SCCH_PWR_DIST_CLA SS_5) 
1000   
500
Active HSUPA Cell Throughput
 HSUPA Cell throughput by comparing the total number of transmitted data against the total
amount of active simultaneous HSUPA user's allocation time
RNC_1883c[kbps]
 M5002C2 EDCH_DATA_ SCELL_UL  M5002C3EDC H_DATA_NSC _S_EDCH_UL  M5002C4EDC H_DATA_NSC _NS_EDCH_UL * 8
 M1000C272DUR_HSUPA_U SERS_1_OR_ 2  M1000C273DUR_HSUPA_U SERS_3_OR_ 4  
 
 M1000C274DUR_HSUPA_U SERS_5_OR_ 6  M1000C275DUR_HSUPA_U SERS_7_OR_ 8  
 M1000C276DUR_HSUPA_U SERS_9_OR_ 10  M1000C277DUR_HSUPA_U SERS_11_OR _12  
 
 M1000C278DUR_HSUPA_U SERS_13_OR _14  M1000C279DUR_HSUPA_U SERS_15_OR _16  
 M1000C280DUR_HSUPA_U SERS_17_OR _18  M1000C281DUR_HSUPA_U SERS_19_OR _20  
 
 M1000C365DURA_HSUPA_ USERS_21_T O_24  M1000C366DURA_HSUPA_ USERS_25_T O_28  
 
  M1000C369DURA_HSUPA_ USERS_37_T O_40  M1000C370DURA_HSUPA_ USERS_41_T O_44  
 
 
 
 M1000C386DURA_HSUPA_ USERS_97_T O_112  M1000C387DURA_HSUPA_ USERS_113_ OR_MORE) 
 
 
Thank you
www.huawei.com
Copyright©2011 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation,
statements regarding the future financial and operating results, future product portfolio, new technology,
etc. There are a number of factors that could cause actual results and developments to differ materially
from those expressed or implied in the predictive statements. Therefore, such information is provided for
reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the
information at any time without notice.

NSN UMTS Parameter Optimization

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

NSN UMTS Parameter Optimization

Загружено:

Авторское право:

Доступные форматы

Security Level:

NSN UMTS Parameter

Author/ Email: Oleksand Kozlov/oleksandr.kozlov@huawei.com

WCDMA radio access network (RAN):

Core network (CN):

Operations support system:

Note that the following interfaces

HSPA Capacity HSPA HSPA

• WCEL = WCDMA Cell • CMOB = Congestion Management OBject

• The logical object of the WCDMA Cell is created to define the

• Adjacencies for WCDMA cell refers to a handover relationship between

There can be 31 intra frequency

Handover Path objects must be created

Not a complete list

Intra Frequency Inter Frequency Inter System

• A new logical COCO object is created in order to reserve local transmission

• WRAB contains parameters used by Admission Control for various tasks in

WCEL RTwithHSDPAHopsIdentifier = 3 HOPS HOPSid = 1

ADJS HOPS HOPSid = 2

FMCSid = 1 FMCS HOPS HOPSid = 1

FMCSid = 2 FMCS HOPS HOPSid = 3

Average Value Maximal Value "Well

 RNC_183c Cell Availability KPI counts Cell availability

M1000C178 AVAILABILITY WCELL IN WORKING STATE

 RNC_727a Cell Availability KPI, excluding blocked by user

M1000C179 AVAILABILITY WCELL BLOCKED BY USER

 CSSR is essentially RRC Setup Success * RAB Setup Success

 The CSSR formulas are for different traffic classes like:

 RNC_915b HSUPA setup success ratio from User perspective

For Voice, the

• For NRT RABs pre-emption is not possible

 The normal transition from HS-DSCH to FACH/DCH are considered

 Counters for normal release includes releases due to

RNC_ 920a HSDPA Success Ratio From User Perspective 

M 1022C 57 PS_REL_RL_FAIL_HS_E_INT+ M 1022C 58 PS_REL_RL_FAIL_HS_E_BGR

 RNC_921b include PS streaming traffic also

RNC_922aPacket Session SuccessRatio [% ] 

• ISHO success rate for NRT services (RNC_301c)

• ISHO success rate for NRT services (RNC_301e)

SCC _ INTRA _ BTS _ SUCCESSFUL  SCC _ INTER _ BTS _ SUCCESSFUL

RNC _ 929a HSUPASCC Attemps M1008C239EDCH _ SCC _ STARTED

 The E-DCH SCC success ratio can be calculated as below

RNC_1174a  NRT DCH MAC - d Throughput DL [kbit/s]

R99 NRT DL MAC - d Data Volume at RNC [kbit]

RNC_1173a  NRT DCH MAC - d Throughput UL [kbit/s]

RNC_1175a  HSDPA UL return channel Throughput [kbit/s]

R99 NRT UL MAC - d Data Volume at RNC [kbit]

HSDPA MAC - d Data Volume at RNC [kbit]

RNC _ 952c  HSUPA MAC - es Average Throughput at RNC [Mbit/s]

RNC _ 931a HSUPA MAC - es Data Volume at RNC [Mbit]

Copyright©2011 Huawei Technologies Co., Ltd. All Rights Reserved.

Вам также может понравиться