OWO205050 WCDMA RAN13 Traffic KPI and Relative Counters ISSUE 1.00

WCDMA RAN Traffic KPI and Relative Counters
Confidential Information of Huawei. No Spreading Without Permission





There are other counter to measure the AMR service traffic with different rate:
VS.RB.AMR.UL.4.75.RNC VS.RB.AMR.DL.4.75.RNC
For all the above counters:
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.

VS.RB.CS.Conv.DL.64.RNC (ID: 67202766)
VS.RB.CS.Conv.UL.64.RNC (ID: 67202778)
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.

VS.R99PSLoad.ULThruput.RNC / VS.R99PSLoad.DLThruput.RNC
This measurement items provide the uplink / downlink traffic of all the R99 services
in the PS domain within the RNC.
The RNC periodically takes a sample from the uplink / downlink traffic values of all
the R99 services in the PS domain. At the end of the measurement period, the RNC
divides the accumulated traffic values by the number of samples to obtain the
mean downlink traffic of all the R99 services in the PS domain. The downlink traffic
of all the R99 services in the PS domain refers to the traffic measured at the RLC
layer. The data does not include the RLC head data.
VS.R99PSLoad.MaxULThruput.RNC / VS.R99PSLoad.MaxDLThruput.RNC
This measurement items provide the maximum uplink / downlink traffic of all the
R99 services in the PS domain within the RNC.
The RNC periodically takes a sample from the uplink / downlink traffic values of all
the R99 services in the PS domain. At the end of the measurement period, the RNC
calculates the maximum uplink / downlink traffic of all the R99 services in the PS
domain within the RNC. The mean uplink traffic of all the R99 services in the PS
domain is the traffic measured at the RLC layer. The RLC header data is not
included and the soft handover traffic is included.

VS.HSDPAPSLoad.DLThruput.RNC
This measurement item provides the downlink traffic of all the HSDPA services in
the PS domain within the RNC.
The RNC periodically takes a sample from the downlink traffic values of all the
HSDPA services in the PS domain. At the end of the measurement period, the RNC
mean downlink traffic of all the HSDPA services in the PS domain.The downlink
traffic of all the HSDPA services in the PS domain refers to the traffic measured at
the RLC layer. The data does not include the RLC head data.
VS.HSDPAPSLoad.MaxDLThruput.RNC
This measurement item provides the maximum downlink traffic of all the HSDPA
services in the PS domain within the RNC.
HSDPA services in the PS domain. At the end of the measurement period, the RNC
calculates the maximum downlink traffic of all the HSDPA services in PS domain
within the RNC.The downlink traffic of all HSDPA services in the PS domain refers
to the traffic obtained at the RLC layer. The data does not include the RLC head
data.

VS.HSUPAPSLoad.ULThruput.RNC
This measurement item provides the uplink traffic of all the HSUPA services in the
PS domain within the RNC.
The RNC periodically takes a sample from the uplink traffic values of all the HSUPA
services in the PS domain. At the end of the measurement period, the RNC divides
the accumulated values by the number of samples to obtain the mean uplink traffic
of all the HSUPA services in the PS domain.The uplink traffic of all the HSUPA
services in the PS domain refers to the traffic obtained at the RLC layer. The data
does not include the RLC head data.
VS.HSUPAPSLoad.MaxULThruput.RNC
This measurement item provides the maximum uplink traffic of all the HSUPA
The RNC periodically takes a sample from the uplink traffic values of all the HSUPA
services in the PS domain. At the end of the measurement period, the RNC
calculates the maximum uplink traffic of all the HSUPA services in the PS domain
within the RNC.The mean uplink traffic of all the HSUPA services in the PS domain
is the traffic measured at the RLC layer. The RLC header data is not included and
the soft handover traffic is included.

VS.MBMSPSLoad.DLThruput.RNC
This measurement item provides the downlink traffic of all the MBMS services in
the PS domain within the RNC.
MBMS services in the PS domain. At the end of the measurement period, the RNC
mean downlink traffic of all the MBMS services in the PS domain.The downlink
traffic of all the MBMS services in the PS domain refers to the traffic measured at
the RLC layer. The data does not include the RLC head data.
VS.MBMSPSLoad.MaxDLThruput.RNC
This measurement item provides the maximum downlink traffic of all the MBMS
MBMS services in the PS domain. At the end of the measurement period, the RNC
calculates the maximum downlink traffic of all the MBMS services in PS domain
within the RNC.The downlink traffic of all MBMS services in the PS domain refers
to the traffic obtained at the RLC layer. The data does not include the RLC head
data.


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 common channel 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.
The RACH Utility Ratio should be calculated based on one busy hour.
VS.CRNCIubBytesRACH.Rx
This measurement item provides the number of UL MAC PDU bytes sent by the
CRNC on the RACH FP over the Iub interface in a cell.
The measurement is triggered when the CRNC sends UL data on the RACH FP over
the Iub interface.
VS.CRNC.IUB.RACH.Bandwidth
interface in a cell
The PCH Utility Ratio should be calculated based on one busy hour.
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
interface in a cell

VS.SRNCIubBytesCSConv.Rx
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.SRNCIubBytesCSStr.Rx
SRNC to the MAC-d on the CS streaming service bearer (DCH FP) over the Iub
The measurement is triggered when the SRNC sends UL data on the CS streaming
service bearer DCH FP over the Iub interface.
VS.SRNCIubBytesCSConv.Tx
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.SRNCIubBytesCSStr.Tx
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.

VS.SRNCIubBytesPSR99Conv.Rx
SRNC to the MAC-d on the PS conversational service bearer (DCH FP) over the Iub
The measurement is triggered when the SRNC sends UL data on the PS
VS.SRNCIubBytesPSR99Str.Rx
SRNC to the MAC-d on the PS streaming service bearer (DCH FP) over the Iub
The measurement is triggered when the SRNC sends UL data on the PS streaming
VS.SRNCIubBytesPSR99Int.Rx
SRNC to the MAC-d on the PS interactive service bearer (DCH FP) over the Iub
The measurement is triggered when the SRNC sends UL data on the PS interactive
VS.SRNCIubBytesPSR99Bkg.Rx
SRNC to the MAC-d on the PS background service bearer (DCH FP) over the Iub
The measurement is triggered when the SRNC sends UL data on the PS
background service bearer DCH FP over the Iub interface in a cell.
VS.SRNCIubBytesPSR99Conv.Tx
SRNC to the MAC-d on the PS conversational service bearer (DCH FP) over the Iub
The measurement is triggered when the SRNC sends DL data on the PS
VS.MAC.SRNCIubBytesPSStr.Tx
SRNC 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
VS.MAC.SRNCIubBytesPSInt.Tx
SRNC 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 service bearer DCH FP over the Iub interface in a cell.

For all the above conters:
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.
Counter ID:
VS.RB.AMR.UL.4.75 / VS.RB.AMR.DL.4.75: 67199632 / 67199625
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.
DifferentServiceRates1 are 8, 16, 32, 64, 128, 144, 256,256.384,
DifferentServiceRates2 are 8, 16, 32, 64, 128, 144, 256,384. For example:
VS.RB.PS.Str.UL.8 (ID: 67203445): Mean number of PS streaming service RBs at
the UL rate of 8 kbit/s
VS.RB.PS.Str.DL.8 (ID: 67203439): Mean number of PS streaming service RBs at
the DL rate of 8 kbit/s
VS.RB.PS.Str.DL.256.384 (ID: 67203441) : Mean number of PS streaming
service RBs at the DL rate of (256,384] kbit/s
VS.RB.PS.Int.UL.384 (ID: 67199589): Mean number of PS interactive service
RBs at the UL rate of 384 kbit/s
VS.RB.PS.Int.DL.384 (ID: 67199581): Mean number of PS interactive service
RBs at the DL rate of 384 kbit/s
VS.RB.PS.Bkg.UL.384 (ID: 67199605): Mean number of PS background service
RBs at the UL rate of 384 kbit/s
VS.RB.PS.Bkg.DL.384 (ID: 67199597): Mean number of PS background service
RBs at the DL rate of 384 kbit/s

VS.HSDPA.UE.Mean.Cell / VS.HSDPA.UE.Max.Cell
These counters provide the average and maximum number of HSDPA UEs in a
serving cell. The DC-HSDPA UE is only sampled in anchor carrier.
The system periodically takes samples of the number of HSDPA UEs. At the end of
the measurement period, by dividing the accumulated value of sample data in the
period by the number of samples, the average number of HSDPA UEs in the
measurement period is obtained; by selecting the maximum value of sample data
in the period, the maximum number of HSDPA UEs in the measurement period is
obtained.
VS.HSDPA.DC.PRIM.UE.Mean.Cell / VS.HSDPA.DC.SEC.UE.Mean.Cell
These counters provide the average number of DC-HSDPA UEs whose anchor or
supplementary carrier is the current cell in a serving cell.
The system periodically takes samples of the number of DC-HSDPA UEs, whose
anchor or supplementary carrier being the current cell. At the end of the
measurement period, by dividing the accumulated value of sample data in the
period by the number of samples, the average number of DC-HSDPA UEs whose
anchor or supplementary carrier being the current cell in the measurement period
is obtained.
These counters provide the average and maximum number of HSDPA UEs with various
categories in a serving cell. The HSDPA UEs with categoriy 21-24 using the DC-HSDPA
feature are only sampled in anchor carriers.
The system periodically takes samples of the number of HSDPA UEs with various categories.
At the end of the measurement period, by dividing the accumulated value of sample data
in the period by the number of samples, the average number of HSDPA UEs with various
categories in the measurement period is obtained; by selecting the maximum value of
sample data in the period, the maximum number of HSDPA UEs with various categories in
the measurement period is obtained.
Counter ID:
VS.HSDPA.UE.Max.CAT1.6 / 7.10 / 11.12 / 13.14 / 15.16 / 17.20 / 21.24 /
25.28:
67193578 / 67193581 / 67193584 / 67193587 / 67193590 / 67193593 /
67193596 / 73423377
VS.HSDPA.UE.Mean.CAT1.6 / 7.10 / 11.12 / 13.14 / 15.16 / 17.20 / 21.24 /
25.28:
67204259 / 67204260 / 67204261 / 67204262 / 67204263 / 67204264 /
67204265 / 73441138
VS.HSDPA.64QAM.UE.Mean.Cell
The system periodically takes samples of the number of 64QAM UEs. At the end of
period by the number of samples, the average number of 64QAM UEs in the
measurement period is obtained.
VS.HSDPA.MIMO.UE.Mean.Cell
The system periodically takes samples of the number of MIMO UEs. At the end of
period by the number of samples, the average number of MIMO UEs in the
measurement period is obtained.
VS.HSDPA.MIMO64QAM.UE.Mean.Cell
The system periodically takes samples of the number of MIMO+64QAM UEs. At
the end of the measurement period, by dividing the accumulated value of sample
data in the period by the number of samples, the average number of
MIMO+64QAM UEs in the measurement period is obtained.
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.


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.16QAM.UE.Mean.Cell
This counter provides the average number of HSUPA 16QAM UEs in a serving cell.
The system periodically takes samples of the number of HSUPA 16QAM UEs. At the end of
the measurement period, by dividing the accumulated value of sample data in the period by
the number of samples, the average number of HSUPA 16QAM UEs in the measurement
period is obtained.
VS.HSUPA.UE.Mean.CAT(Number) / VS.HSUPA.UE.Max.CAT(Number)
These counters provide the average and maximum number of HSUPA UEs with various
categories in a serving cell.
The system periodically takes samples of the number of HSUPA UEs with various categories.
At the end of the measurement period, by dividing the accumulated value of sample data in
the period by the number of samples, the average number of HSUPA UEs with various
categories in the measurement period is obtained; by selecting the maximum value of
sample data in the period, the maximum number of HSUPA UEs with various categories in
the measurement period is obtained.
VS.HSUPA.UE.Max.CAT1.4 / 5 / 6 / 7: 67193599 / 67193602 / 67193605 / 67193608
VS.HSUPA.UE.Mean.CAT1.4 / 5 / 6 /7: 67204266 / 67204267 / 67204268 / 67204269
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.



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.
These counters provides the RTWP measurement values of a cell in the RNC as shown
below.
The measurement is triggered at point A as shown in 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.

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.
These counters provide the TCP measurement values of a cell in the RNC, as listed below
The measurement is triggered at point A as shown in Figure, when the RNC 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.
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.
These counters provide the non-HSDPA TCP measurement values of a cell in the RNC.
The measurement is triggered at point A as shown in figure, when the RNC obtains the
non-HSDPA TCP of a cell after it receives from the NodeB a COMMON MEASUREMENT
REPORT message containing the non-HSDPA TCP values of the cell. In this case, the RNC
measures the items in this cell.
These counters provide the HSDPA-required power measurement values of an HSDPA cell
in the RNC.
The measurement is triggered at point A as shown in figure, when the RNC 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.

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.
For each data rate and service, the number of UL credits is equal to the number of UL CEs
multiplied by 2. This is because the RESOURCE STATUS INDICATION message over the Iub
interface supports only integers. For example, a UL 32 kbit/s PS service consumes 1.5 CEs.
Then, the number of corresponding UL credits consumed is 3, an integer, which can be
carried in the RESOURCE STATUS INDICATION message.

There are several counters which can show the Credit utilization:
VS.LC.ULCreditUsed.Mean (ID: 67202567): UL credit usage (cell)
VS.LC.ULCreditUsed.Max (ID: 67202565): UL credit usage (cell)
VS.LC.ULCreditUsed.Min (ID: 67202566): UL credit usage (cell)
VS.LC.DLCreditUsed.Mean (ID: 67202570): DL credit usage (cell)
VS.LC.DLCreditUsed.Max (ID: 67202567): DL credit usage (cell)
VS.LC.DLCreditUsed.Min (ID: 67202568): DL credit usage (cell)
The measurement items provide the mean, maximum, and minimum credit usages in a cell.
The RNC periodically takes samples from the UL credit usage and DL credit usage in the
cell. At the end of the measurement period, the RNC calculates the maximum and
minimum usages of CE resources, and divides the accumulated usages by the number of
samples to obtain the mean usage of both UL and DL CE resources in the measurement
period.


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


OWO205050 WCDMA RAN13 Traffic KPI and Relative Counters ISSUE 1.00

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

OWO205050 WCDMA RAN13 Traffic KPI and Relative Counters ISSUE 1.00

Diunggah oleh

Hak Cipta:

Format Tersedia

WCDMA RAN Traffic KPI and Relative Counters

Confidential Information of Huawei. No Spreading Without Permission

Anda mungkin juga menyukai