5 WCDMA RAN Traffic Counters and KPI Introduction RAN10

WCDMA RAN Traffic Counters and KPI
Introduction RAN10
Confidential Information of Huawei. No Spreading Without Permission
N-0
www.huawei.com
Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.
WCDMA RAN Traffic
Counters and KPI
Introduction RAN10
N-1
Page1 Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
Upon completion of this course, you will be able to:
Describe traffic counter system
Know the traffic KPI
Introduction RAN10
N-2
Contents
1. RNC Traffic Counters
2. Cell Traffic Counter
3. Cell Load Counter
Introduction RAN10
N-3
Contents
Introduction RAN10
N-4
RNC Traffic Counters System
In RNC, the counters related to traffic can be divided into:
RNC Total Traffic
Service Traffic
Introduction RAN10
N-5
RNC Total Traffic in CS domain
Equivalent Erlang of CS Domain in RNC
VS.CSLoad.Erlang.Equiv.RNC
Maximum Equivalent Erlang of CS Domain in RNC
VS.CSLoad.MaxErlang.Equiv.RNC
VS.CSLoad.Erlang.Equiv.RNC
This measurement item provides the equivalent Erlang values of all the
services in the CS domain in the RNC.
The RNC periodically takes the samples from the equivalent Erlang values of
all the services in the CS domain. At the end of the measurement period, the
RNC divides the accumulated equivalent Erlang values by the number of
samples to obtain the mean equivalent Erlang values of all the services in the
CS domain. Each time a CS domain service is established, the RNC converts
its rate to the equivalent Erlang, and then increases the equivalent Erlang of
the CS domain in the current RNC. Each time a CS domain service is
released, the RNC converts its rate to the equivalent Erlang and decreases
the equivalent Erlang of the CS domain in the current RNC.
Unit: Erlang.
VS.CSLoad.MaxErlang.Equiv.RNC
This measurement item provides the maximum equivalent Erlang values of all
the services in the CS domain within the RNC.
The RNC periodically takes a sample from the equivalent Erlang values of all
the services in the CS domain. At the end of the period, the RNC calculates
the maximum equivalent Erlang of all the services in the CS domain within the
RNC. Each time a CS domain service is established, the RNC converts its rate
to the equivalent Erlang, and then increases the equivalent Erlang of the CS
domain in the current RNC. Each time a CS domain service is released, the
RNC decreases the equivalent Erlang of the CS domain in the current RNC.
Unit: Erlang.
Introduction RAN10
N-6
RNC Total Traffic in uplink PS domain
UL Traffic of R99 PS Domain in RNC
VS.R99PSLoad.ULThruput.RNC
Maximum UL Traffic of R99 PS Domain in RNC
VS.R99PSLoad.MaxULThruput.RNC
UL Traffic of HSUPA PS Domain in RNC
VS.HSUPAPSLoad.ULThruput.RNC
Maximum UL Traffic of HSUPA PS Domain in RNC
VS.HSUPAPSLoad.MaxULThruput.RNC
VS.R99PSLoad.ULThruput.RNC
This measurement item provides the uplink traffic of all the R99 services in the
PS domain within the RNC.
VS.R99PSLoad.MaxULThruput.RNC
This measurement item provides the maximum uplink traffic of all the R99
services in the PS domain within the RNC.
VS.HSUPAPSLoad.ULThruput.RNC
This measurement item provides the uplink traffic of all the HSUPA services in
the PS domain within the RNC.
VS.HSUPAPSLoad.MaxULThruput.RNC
This measurement item provides the maximum uplink traffic of all the HSUPA
Unit: kbit/s.
Introduction RAN10
N-7
RNC Total Traffic in Downlink PS Domain
DL Traffic of R99 PS Domain in RNC
VS.R99PSLoad.DLThruput.RNC
Maximum DL Traffic of R99 PS Domain in RNC
VS.R99PSLoad.MaxDLThruput.RNC
DL Traffic of HSDPA PS Domain in RNC
VS.HSDPAPSLoad.DLThruput.RNC
Maximum DL Traffic of HSDPA PS Domain in RNC
VS.HSDPAPSLoad.MaxDLThruput.RNC
VS.R99PSLoad.DLThruput.RNC
This measurement item provides the downlink traffic of all the R99 services in
the PS domain within the RNC.
VS.R99PSLoad.MaxDLThruput.RNC
This measurement item provides the maximum downlink traffic of all the R99
VS.HSDPAPSLoad.DLThruput.RNC
This measurement item provides the downlink traffic of all the HSDPA
VS.HSDPAPSLoad.MaxDLThruput.RNC
This measurement item provides the maximum downlink traffic of all the
HSDPA services in the PS domain within the RNC.
Unit: kbit/s
Introduction RAN10
N-8
AMR Service Traffic
Mean number of AMR speech UEs
VS.AMR.RB.UL.4.75 VS.AMR.RB.DL.4.75
The measurement items provide the mean number of UEs that use the AMR speech
services at different bit rates in both uplink and downlink directions in the RNC.
The RNC periodically takes a sample from the number of AMR speech UEs at each
of the eight UL and DL bit rates. At the end of the measurement period, the RNC
divides the accumulated number by the number of samples to obtain the mean
number of AMR speech UEs at each rate.
Introduction RAN10
N-9
VP Service Traffic
Mean number of 64 kbit/s conversational service RBs in CS
domain
VS.RB.DLConvCS.64.RNC
VS.RB.ULConvCS.64.RNC
The measurement items provide the mean number of 64 kbit/s conversational service
RBs in the CS domain in the UL and DL directions.
The RNC periodically takes a sample from the number of 64 kbit/s conversational
service RBs in the CS domain in the UL and DL directions. At the end of the
measurement period, the RNC divides the accumulated number of RBs at one bit rate
by the number of samples to obtain the mean number of such RBs.
Introduction RAN10
N-10
PS Streaming Service Traffic
Mean number of streaming service RBs in PS Domain at different bit
rates
VS.RB.ULStrPS.256.RNC VS.RB.DLStrPS.256.RNC
The measurement items provide the mean number of streaming service RBs in the
PS domain according to different UL and DL bit rates.
The RNC periodically takes a sample from the number of RBs in the PS domain at
each of the seven UL and DL rates of the streaming service. At the end of the
measurement period, the RNC divides the accumulated number of RBs at each bit
rate by the number of samples to obtain the mean number of such RBs.
Introduction RAN10
N-11
PS Interactive Service Traffic
Mean number of interactive service RBs in PS domain at different bit
rates
VS.RB.ULInterPS.384.RNC VS.RB.DLInterPS.384.RNC
The measurement items provide the mean number of interactive service RBs in the
each of the seven UL and DL rates of the interactive service. At the end of the
Introduction RAN10
N-12
PS Background Service Traffic
Mean number of background service RBs in PS domain at different bit
rates
VS.RB.ULBkgPS.384.RNC VS.RB.DLBkgPS.384.RNC
The measurement items provide the mean number of background service RBs in the
each of the seven UL and DL rates of the background service. At the end of the
Introduction RAN10
N-13
Contents
Introduction RAN10
N-14
Cell Traffic Counters System
In cell level, the counters related to traffic can be divided
into:
CELL total traffic
CELL R99 service traffic
CELL HSDPA service traffic
Introduction RAN10
N-15
Cell Total Traffic
The measurement value can be based on:
Common channel
FACH, RACH,PCH
Dedicate channel
This traffic measurement is for Iub interface
These value are total traffic throughput on Iub Interface
The unit is Byte
Introduction RAN10
N-16
Cell Common Channel Traffic Volume
Traffic Volume on IUB_FACH (Cell)
VS.MAC.CRNCIubBytesFACH.TX
CRNC_Iub FACH Bandwidth (Cell)
VS.CRNC.IUB.FACH.Bandwidth
FACH Utility Ratio = VS.MAC.CRNCIubBytesFACH.Tx /
(3600*VS.CRNC.IUB.FACH.Bandwidth)
The FACH Utility Ratio should be calculated based on one busy hour.
VS.MAC.CRNCIubBytesFACH.TX
This measurement item provides the number of DL MAC PDU bytes sent by
the CRNC on the FACH FP over the Iub interface in a cell.
The measurement is triggered when the CRNC sends DL data on the FACH
FP over the Iub interface.
VS.CRNC.IUB.FACH.Bandwidth
The measurement items provide the FACH bandwidth on the Iub interface in a
cell.
The measurement is triggered when the CRNC sets up or deletes a FACH on
the Iub interface.
Introduction RAN10
N-17
Traffic Volume on IUB_RACH (Cell)
VS.MAC.CRNCIubBytesRACH.TX
CRNC_Iub RACH Bandwidth (Cell)
VS.CRNC.IUB.RACH.Bandwidth
RACH Utility Ratio = VS.MAC.CRNCIubBytesRACH.Tx /
(3600*VS.CRNC.IUB.RACH.Bandwidth)
The RACH Utility Ratio should be calculated based on one busy hour.
VS.MAC.CRNCIubBytesRACH.TX
the CRNC on the RACH FP over the Iub interface in a cell.
The measurement is triggered when the CRNC sends DL data on the RACH
FP over the Iub interface.
VS.CRNC.IUB.RACH.Bandwidth
The measurement items provide the RACH bandwidth on the Iub interface in a
cell.
The measurement is triggered when the CRNC sets up or deletes a RACH on
the Iub interface.
Introduction RAN10
N-18
Traffic Volume on PCH of Iub Interface (Cell)
VS.MAC.CRNCIubBytesPCH.TX
CRNC_Iub PCH Bandwidth (Cell)
VS.CRNC.IUB.PCH.Bandwidth
PCH Utility Ratio = VS.MAC.CRNCIubBytesPCH.Tx /
(3600*VS.CRNC.IUB.PCH.Bandwidth)
The PCH Utility Ratio should be calculated based on one busy hour. Different LAC
would generate different PCH Utility Ratio. For the cell in the same LAC, the PCH
Utility Ratio would be the same theoretically.
The basic principles for the PCH utilization are:
1. The PCH Utility Ratio should not exceed 40%
2. The PCH Utility Ratio are balance between different LACs.
If 1) is not met, LAC splitting is suggested. If 2) is not met, it is recommended to
re-plan the LAC.
VS.MAC.CRNCIubBytesPCH.TX
This measurement item provides the number of DL MAC PDU bytes received
by the CRNC on the PCH FP over the Iub interface. These bytes include
paging data transport blocks and paging indication (PI) data.
The measurement is triggered when the CRNC sends DL data on the PCH FP
over the Iub interface.
VS.CRNC.IUB.PCH.Bandwidth
The measurement items provide the PCH bandwidth on the Iub interface in a
cell.
The measurement is triggered when the CRNC sets up or deletes a common
channel on the Iub interface.
Introduction RAN10
N-19
Measurement value for different services on Iub interface
UL CS Conversational Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesCSConv.Rx
UL CS Streaming Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesCSStr.Rx
DL CS Conversational Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesCSConv.Tx
DL CS Streaming Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesCSStr.Tx
Cell CS Service Traffic Volume
VS.MAC.SRNCIubBytesCSConv.Rx
This measurement item provides the number of UL MAC PDU bytes sent by
the SRNC to the MAC-d on the CS conversational service bearer (DCH FP)
over the Iub interface in a cell.
The measurement is triggered when the SRNC sends UL data on the CS
conversational service bearer DCH FP over the Iub interface in a cell.
VS.MAC.SRNCIubBytesCSStr.Rx
the SRNC to the MAC-d on the CS streaming service bearer (DCH FP) over
the Iub interface in a cell.
The measurement is triggered when the SRNC sends UL data on the CS
streaming service bearer DCH FP over the Iub interface.
VS.MAC.SRNCIubBytesCSConv.Tx
the SRNC on the CS conversational service bearer DCH FP over the Iub
interface in a cell.
The measurement is triggered when the SRNC sends DL data on the CS
conversational service bearer DCH FP over the Iub interface.
VS.MAC.SRNCIubBytesCSStr.Tx
the SRNC on the CS streaming service bearer DCH FP over the Iub interface
in a cell.
The measurement is triggered when the SRNC sends DL data on the CS
streaming service bearer DCH FP over the Iub interface in a cell.
Introduction RAN10
N-20
UL PS Conversational Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSConv.Rx
UL PS Streaming Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSStr.Rx
UL PS Interactive Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSInt.Rx
UL PS Background Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSBkg.Rx
Cell PS Service Traffic Volume
VS.MAC.SRNCIubBytesPSConv.Rx
the SRNC to the MAC-d on the PS conversational service bearer (DCH FP)
over the Iub interface in a cell.
The measurement is triggered when the SRNC sends DL data on the PS
VS.MAC.SRNCIubBytesPSStr.Rx
the SRNC to the MAC-d on the PS streaming service bearer (DCH FP) over
The measurement is triggered when the SRNC sends UL data on the PS
streaming service bearer DCH FP over the Iub interface in a cell.
VS.MAC.SRNCIubBytesPSInt.Rx
the SRNC to the MAC-d on the PS interactive service bearer (DCH FP) over
interactive service bearer DCH FP over the Iub interface in a cell.
VS.MAC.SRNCIubBytesPSBkg.Rx
the SRNC to the MAC-d on the PS background service bearer (DCH FP) over
background service bearer DCH FP over the Iub interface in a cell.
Introduction RAN10
N-21
Cell PS Service Traffic Volume
DL PS Conversational Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSConv.Tx
DL PS Streaming Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSStr.Tx
DL PS Interactive Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSInt.Tx
DL PS Background Traffic Volume on Iub Interface (Cell)
VS.MAC.SRNCIubBytesPSBkg.Tx
VS.MAC.SRNCIubBytesPSConv.Tx
This measurement item provides the number of DL MAC PDU bytes sent by the SRNC
on the PS conversational service bearer DCH FP over the Iub interface in a cell.
The measurement is triggered when the SRNC sends DL data on the PS
VS.MAC.SRNCIubBytesPSStr.Tx
on the PS streaming service bearer DCH FP over the Iub interface in a cell.
The measurement is triggered when the SRNC sends DL data on the PS streaming
service bearer DCH FP over the Iub interface in a cell.
VS.MAC.SRNCIubBytesPSInt.Tx
on the PS interactive service bearer DCH FP over the Iub interface in a cell.
The measurement is triggered when the SRNC sends DL data on the PS interactive
VS.MAC.SRNCIubBytesPSBkg.Tx
This measurement item provides the number of bytes of the DL MAC PDU sent by the
SRNC on the PS background service bearer DCH FP over the Iub interface in a cell.
The measurement is triggered when the SRNC sends DL data on the PS background
Introduction RAN10
N-22
Cell AMR Service Traffic
Mean Number of AMR Speech UEs at Different UL and DL Bit
Rates (Cell)
VS.AMR.Ctrl.UL4.75 VS.AMR.Ctrl.DL4.75
The measurement items provide the mean number of UEs that use the AMR speech
service at different UL and DL bit rates in the cell.
The RNC periodically takes a sample from the number of UEs that use the AMR
speech service at the eight different UL and DL rates in the cell. At the end of the
measurement period, the RNC divides the accumulated number by the number of
samples to obtain the mean number of UEs that use the AMR speech service at each
bit rate.
Introduction RAN10
N-23
Average Numbers of CS RBs with Different Bit Rates (Cell)
VS.RB.ULConvCS.64
VS.RB.DLConvCS.64
Cell VP Service Traffic
VS.RB.ULConvCS.64
This measurement item provides the mean number of CS conversational
service RBs at the downlink bit rate of 64 kbit/s in a cell, that is, the mean
number of uplink and downlink RBs obtained at the sampling points in the cell
in the measurement period.
The RNC periodically takes a sample from the number of CS conversational
service RBs at the DL bit rate of 64 kbit/s. At the end of the measurement
period, the RNC divides the accumulated number of conversational service
RBs at the DL bit rate of 64 kbit/s by the number of samples to obtain the
mean number of CS conversational service RBs. In this case, the RNC
measures an item in each cell that the UE camps on.
VS.RB.DLConvCS.64
The measurement items provide the mean number of CS conversational
service RBs at the downlink bit rate of 64 kbit/s in a cell, that is, the mean
number of uplink and downlink RBs obtained at the sampling points in the cell
in the measurement period,
The RNC periodically takes a sample from the number of CS conversational
service RBs at different bit rates. At the end of the measurement period, the
RNC divides the accumulated number of conversational service RBs at each
bit rate by the number of samples to obtain the mean number of CS
conversational service RBs. In this case, the RNC measures the item in each
cell that the UE camps on.
Introduction RAN10
N-24
Cell PS Service Traffic
Mean Number of PS Service RBs at Different UL and DL Bit
Rates (Cell)
VS.RB.ULStrPS.DifferentServiceRate
VS.RB.ULInterPS.DifferentServiceRate
VS.RB.ULBkgPS.DifferentServiceRate
VS.RB.DLStrPS.DifferentServiceRate
VS.RB.DLInterPS.DifferentServiceRate
VS.RB.DLBkgPS.DifferentServiceRate
The measurement items provide the mean number of PS
streaming/interactive/background service R99 RBs at the different bit rates in a cell,
that is, the mean number of R99 RBs obtained at the sampling points in the cell in the
measurement period.
The RNC periodically takes a sample from the number of PS streaming service RBs
at different bit rates. At the end of the measurement period, the RNC divides the
accumulated number of PS streaming service RBs at different bit rates by the number
of samples to obtain the mean number of the PS streaming service RBs. In this case,
the RNC measures the item in the specified cell.
Different service rates are 8, 16, 32, 64, 128, 144, 256, 384, for example:
VS.RB.ULStrPS.8
VS.RB.DLStrPS.8
VS.RB.ULInterPS.384
VS.RB.DLInterPS.384
VS.RB.ULBkgPS.384
VS.RB.DLBkgPS.384
Etc.
Introduction RAN10
N-25
Mean Number of HSDPA UEs in a Cell
VS.HSDPA.UE.Mean.Cell
Mean Number of MAC-d Flows (Cell)
VS.HSDPA.MACD.Mean.Cell
Cell HSDPA Traffic
VS.HSDPA.UE.Mean.Cell
This measurement item provides the mean number of HSDPA UEs in a
serving cell. The value of this unit is lower than or equal to that of the
VS.CellDCHUEs measurement.
The RNC periodically takes a sample from the number of HSDPA UEs in the
cell. At the end of the measurement period, the RNC divides the accumulated
number of UEs by the number of samples to obtain the mean number of
HSDPA UEs in the measurement period.
VS.HSDPA.MACD.Mean.Cell
This measurement item provides the mean number of MAC-d flows in a cell.
In an HSDPA service cell, the system periodically takes a sample of the
number of MAC-D flows. At the end of the measurement period, the
accumulated value of the data at all sampling points is divided by the number
of samples to obtain the mean number of MAC-d flows in the measurement
period.
Introduction RAN10
N-26
Cell HSDPA Traffic
Mean Downlink Throughput of MAC-d Flow (Cell)
VS.HSDPA.MeanChThroughput
Number of Transmitted Downlink Bytes in MAC-d Flow (Cell)
VS.HSDPA.MeanChThroughput.TotalBytes
VS.HSDPA.MeanChThroughput
This measurement item provides the mean downlink throughput of MAC-d flow
in a cell.
When data is transmitted in an HSDPA cell, the RNC measures the total data
transfer time of the UE and the total number of bits in the received data in the
cell. At the end of the measurement period, the RNC divides the total number
of bits by the total data transfer time to obtain the mean downlink throughput of
MAC-d flow in the cell. The RLC header overhead and the retransfer data are
excluded.
VS.HSDPA.MeanChThroughput.TotalBytes
This measurement item provides the number of bytes in the transmitted
downlink data in the MAC-d flow in a cell.
When data is transmitted in an HSDPA cell, the RNC measures the total
number of bytes in the transmitted downlink data at the RLC layer for the
MAC-d flow in the cell. The RLC header overheand and the retransfer data are
excluded.
Introduction RAN10
N-27
Mean Number of HSUPA UEs in a Cell
VS.HSUPA.UE.Mean.Cell
Mean Uplink Throughput of Mac-d flows (Cell)
VS.HSUPA.MeanChThroughput
Number of Bytes in Received Uplink Data at the RLC Layer
of Mac-d flow (Cell)
VS.HSUPA.MeanChThroughput.TotalBytes
Cell HSUPA Traffic
VS.HSUPA.UE.Mean.Cell
This measurement item provides the mean number of HSUPA UEs in a cell,
which is measured in E-DCH active set. The measurement does not contain
the HSUPA UEs under the DRNC.
The RNC periodically takes a sample from the number of HSUPA UEs in the
cell. At the end of the measurement period, the RNC divides the accumulated
number of UEs by the number of samples to obtain the mean number of
HSUPA UEs in the measurement period.
VS.HSUPA.MeanChThroughput
This measurement item provides the mean UL throughput of MAC-d flow in a
cell.
When data is received in an HSUPA active cell, the RNC measures the actual
data transfer time of the UE and the number of bits in the received data. At the
end of the measurement period, the RNC divides the total number of bits by
the actual data transfer time of the UE to obtain the mean UL throughput of the
RLC layer for the MAC-d flow in the cell. The RLC header overhead and the
retransfer data are excluded.
VS.HSUPA.MeanChThroughput.TotalBytes
This measurement item provides the total number of bytes in the received
uplink data at the RLC layer for all the MAC-d flows in a cell.
When data is received in an HSUPA active cell, the RNC measures the total
number of bytes in the received uplink data at the RLC layer for the MAC-d
flow in the cell. The RLC header overhead and the retransfer data are
excluded.
Introduction RAN10
N-28
Contents
Introduction RAN10
N-29
Cell Load Counters System
In cell level, the counters related to load can be divided into:
Cell power load
Cell CE load
Cell code load
Introduction RAN10
N-30
Cell Power Load
Cell RX Power Measurement
Mean RTWP of a cell
VS.MeanRTWP
Maximum RTWP of a cell
VS.MaxRTWP
Minimum RTWP of a cell
VS.MinRTWP
RTWP (Received Total Wideband Power) analysis is used to evaluate the uplink
interference and loading status. If actual loading of the network is empty, then the
RTWP is the thermal noise plus the noise figure of the NodeB. With the access of
more users in the network, RTWP increases accordingly.
The basic principles are:
RTWP at busy hour(BH) in one day should not exceed 1dB over the
target loading of the network.
If HSUPA service is not activated, then 50% target loading is suggested,
otherwise 75% uplink target loading should be used.
Since RTWP would be also influenced by the external interference, the RTWP result
is just for reference, cannot be used for the reason of expansion directly.
The measurement is triggered at point A as shown in the figure, when the RNC
receives from the NodeB a COMMON MEASUREMENT REPORT message about
the RTWP of a cell and obtains the RTWP of the cell. In this case, the RNC measures
the items in this cell.
Introduction RAN10
N-31
Cell Power Load
Cell TX Power Measurement
Mean TCP of a cell
VS.MeanTCP
Maximum TCP of a cell
VS.MaxTCP
Minimum TCP of a cell
VS.MinTCP
Total_TCP_Utility_Ratio =
VS.MeanTCP / Configured_Total_Cell_TCP
TCP is used to assess the downlink power consumption, which represents the
downlink loading status. Evaluation of TCP power is helpful to avoid the congestion
due to the insufficient power in downlink.
The basic principles for the TCP utilization are:
1. The mean R99 TCP Utility Ratio should not exceed 70%
2. No service failure is caused by the insufficient TCP power.
If 1) is not met, then more carrier or more sites are suggested, if 2) is not met,
then more research are needed together with the actual traffic model.
obtains the TCP of a cell after receiving from the NodeB a COMMON
MEASUREMENT REPORT message containing the TCP values of the cell. In this
case, the RNC measures the items in this cell.
Introduction RAN10
N-32
Cell Power Load
Non-HSDPA Cell TCP Values
Mean non-HSPA TCP of a cell
VS.MeanTCP.NonHS
Maximum non-HSPA TCP of a cell
VS.MaxTCP.NonHS
Minimum non-HSPA TCP of a cell
VS.MinTCP.NonHS
R99_TCP_Utility_Ratio =
VS.MeanTCP.NonHS / Configured_Total_Cell_TCP
The basic principles for the TCP utilization are:
1. The mean R99 TCP Utility Ratio should not exceed 70%
2. No service failure is caused by the insufficient TCP power.
If 1) is not met, then more carrier or more sites are suggested, if 2) is not met,
then more research are needed together with the actual traffic model.
The failures statistics counters which are caused by insufficient power are:
VS.RRC.Rej.Power.Cong
VS.RAB.FailEstCs.Power.Cong
VS.RABFailEstPs.Power.Cong
obtains the non-HSPA TCP of a cell after it receives from the NodeB a COMMON
MEASUREMENT REPORT message containing the non-HSPA TCP values of the
cell. In this case, the RNC measures the items in this cell.
Introduction RAN10
N-33
Cell Power Load
HSDPA Cell TX Power for HSDPA Service
Mean HSDPA-required power of an HSDPA cell
VS.HSDPA.MeanRequiredPwr
Maximum HSDPA-required power of an HSDPA cell
VS.HSDPA.MaxRequiredPwr
Minimum HSDPA-required power of an HSDPA cell
VS.HSDPA.MinRequiredPwr
obtains the HSDPA-required power of an HSDPA cell after it receives from the NodeB
a COMMON MEASUREMENT REPORT message containing the values of the cell. In
this case, the RNC measures the items in this cell.
Introduction RAN10
N-34
Cell CE Load
Mean CE Usages (Cell) :
UL_Mean_Used_CE_Number = VS.LC.ULCreditUsed.CELL / 2
DL_Mean_Used_CE_Number = VS.LC.DLCreditUsed.CELL
UL CE Utility Ratio (NodeB) =
UL_Mean_Used_CE_Number_in_BH /
Configured_UL_CE_Number
DL CE Utility Ratio (NodeB) =
DL_Mean_Used_CE_Number_in_BH /
Configured_DL_CE_Number
Note: CE resource are shared by all the cells in one NodeB
CE is the baseband resources for services in NodeB. CE utilization ratio represents
the base band resources consumption status of the NodeB. If the CE utilization ratio
exceeds one specified threshold of the total CE, that means CE resources are going
to be the limitation factor of the network. CE expansion is needed in this case.
The CE utilization ratio should not exceed 70% due to HUAWEIs experiences.
CE is called NodeB credit on the RNC side and called Channel Element on the
NodeB side. It is used to measure the channel demodulation capability of NodeBs.
VS.LC.ULCreditUsed.CELL
Mean UL credit usage (cell). In uplink, 1 Credit corresponds to 0.5 CE, so the
CE number equals to the Credit number divided by 2.
VS.LC.DLCreditUsed.CELL
Mean DL credit usage (cell). In downlink, 1 Credit corresponds to 1 CE, so the
CE number equals to the Credit number
Configured_UL_CE_Number and Configured_UL_CE_Number are from CE license
file.
Introduction RAN10
N-35
Cell Code Load
Mean Number of Occupied Codes (Cell)
VS.RAB.SFOccupy
Note:
The code number is normalized to SF = 256
The occupied codes are the codes occupied by the common channel, R99
user, and HS-DSCH
R99_Code_Utility_Ratio =
R99_Mean_Used_Code_in_BH /
Max_R99_Available_Code
Codes here are the OVSF codes for both R99 and HSPA services. If the codes
utilization ratio exceeds one specified threshold of the total available OVSF codes,
that means codes resources are going to be the limitation factor of the network.
The basic principles for the codes utilization are:
1. The codes utilization for R99 services should not exceed 70%.
2. No congestion due to codes in busy hour of the cell.
If 1is not met, the codes allocation between R99 services and HSDPA services can
be adjusted firstly according to the service distribution. If it is still not OK, then more
carriers and sites are suggested If 2) is not met for a period of time, the adjustment
suggestion is the same to 1).
VS.RAB.SFOccupy
The measurement items provide the mean number and the maximum number
of occupied codes in a cell. The occupied codes are the codes occupied by
the common channel, R99 user, and HS-DSCH. The code number is
normalized to SF = 256, that is, converted to the code number when SF = 256.
The way of the normalization to SF = 256 is to multiply the number when SF =
k by 256/k.
Max_R99_Available_Code= 256 - Common channels(8 SF=256) - HSPDSCH (5
SF=16)*16 HsScchCodeNum ( 4 SF=128) * 2 EAGCHCodeNum( 0 SF=256)
ERGCHEHICHCodeNum(0 SF=128) * 2
R99_Mean_Used_Code_in_BH = VS.RAB.SFOccupy - Common channels(8 SF=256)
- HSPDSCH (5 SF=16)*16 HsScchCodeNum ( 4 SF=128) * 2
EAGCHCodeNum( 0 SF=256) ERGCHEHICHCodeNum(0 SF=128) * 2
Introduction RAN10
N-36
Thank you
www.huawei.com

5 WCDMA RAN Traffic Counters and KPI Introduction RAN10

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5 WCDMA RAN Traffic Counters and KPI Introduction RAN10

Uploaded by

Copyright:

Available Formats

WCDMA RAN Traffic Counters and KPI

You might also like