traffic & cell algorithmskpi’s and relative counter’s

Traffic & Cell Algorithms KPIs and Relative Counters

Abstract:

In this paper, I am going to introduce all common and most Traffic & Cell Algorithms KPIs and Relative Counters used in Radio Network Optimization and Planning project, as problem with any project is they dont know what counters and KPIs should be used, especially when taking with the customer and setting the goals (Counters and KPIs) they should monitor in a daily basisIn this document, I introduce all related Traffic & Cell Algorithms KPIs and Counters that maybe needed in the project, also attached very useful summary about all the counters and KPIs, as found that most of engineers cannot follow on the large amount of counters and KPIs and they often fall in mistakes, this summary paper you will find it very much useful that shows you all required in just one paper

In this document you will find detailed explanation for nearly all counters and KPIs mentioned to know what is its effect and when does it count, by time when working in real-live network you will find yourself by practice will not need anymore the detailed description and need only the one-page summary

Introduction:

Counters in the KPI wizardWithin the KPI wizard, counters are created that are required to determine the value of the KPI. A counter keeps track of the number of occurrences of some situation or event.

In Huawei, there is default counters, extended counters & user-defined counter (often known as custom counters)

If the counters in the M2000 system do not meet your measurement requirement or the default naming conventions of the counters do not meet your requirement, you can define required measurement counters based on the existing counters by using the arithmetic operations. You can define a custom counter based on the existing counters of different function sets, but the involved counters must belong to one object type, and the number of involved function subsets cannot exceed 10.

Key performance indicators (KPIs)

Key performance indicators (KPIs) are the detailed specifications used to track business objectives.

KPIs are created based on business objectives. A business objective is an executive statement of direction in support of a corporate strategy. The business objective is a high-level goal that is quantifiable, measurable, and results-oriented. For business measures modeling, the business objective is translated into a KPI that enables the organization to measure some aspect of the process against a target that they define. KPI is compared against actual results to determine the level of success.

A KPI is associated with a specific process and is generally represented by a numeric value. A KPI may have a target and allowable margins, or lower and upper limits, forming a range of performance that the process should achieve. A KPI can be thought of as a metric with a target.

These are your options for specifying a KPI:

Specify an exact target and acceptable target variations (defined by lower margin and upper margin) Specify a safe range (defined by lower limit and upper limit), using specific numeric values as the limits.

Whenever the value of a KPI (or aggregate metric) changes: NOTE:

Recommended to print the one-page summary in a A3, not normal A4 white paper for better resolution

Analysis:

1) Traffic

Network monitoring is a difficult and demanding task that is a vital part of a Network Administrators job. Network Administrators are constantly striving to maintain smooth operation of their networks. If a network were to be down even for a small period of time productivity within a company would decline, and in the case of public service departments the ability to provide essential services would be compromised. In order to be proactive rather than reactive, administrators need to monitor traffic movement and performance throughout the network and verify that security breaches do not occur within the network.

As company intranets continue to grow it is increasingly important that network administrators are aware of and have a handle on the different types of traffic that is traversing their networks. Traffic monitoring and analysis is essential in order to more effectively troubleshoot and resolve issues when they occur, so as to not bring network services to a stand still for extended periods of time. Numerous tools are available to help administrators with the monitoring and analysis of network traffic. This paper discusses M2000 Counters and KPIs based monitoring techniques. It gives an overview of the whole traffic of network that ranges from below:

CS Equivalent Erlang

PS UL Throughput

PS DL Throughput

UL Traffic of Typical Radio Bearers

DL Traffic of Typical Radio Bearers

HSDPA Mean UE Number

HSDPA RLC Traffic Volume

HSUPA Mean UE Number

HSUPA RLC Traffic Volume

UL Traffic Volume of QoS Classes

DL Traffic Volume of QoS Classes 2) Cell Algorithm

LCC (Load Congestion Control) consist of LDR (Load Reshuffling) and OLC (Over Load Control).In basic congestion state, LDR will be used to optimize resource distribution, the main rules is not to affect the feeling of users as possible as we can.In overload state, OLC will be used to reduce cell load quickly, keep system stability and the service of high priority users.DCCC: Dynamic Channel Configuration ControlDCCC allocates dynamically resources according to the service request and system load. So, DCCC is an effective method to increase the radio resource utilization efficiencyThe UL DCCC algorithm and the DL DCCC algorithm work independently Traffic for AMR Services KPIs and Relative Counters (per RNC): VS.RB.AMR.UL.4.75.RNC

VS.RB.AMR.DL.4.75.RNC VS.RB.AMR.UL.5.15.RNC







VS.RB.AMR.DL.12.2.RNCThese counters provide the average number of AMR users with different UL and DL rates in the RNC.The number of AMR users with each UL or DL rate is sampled every five seconds in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.Traffic for Video Phone 64kbps Services KPIs and Relative Counters (per RNC):

VS.RB.CS.Conv.DL.64.RNC

VS.RB.CS.Conv.UL.64.RNC

The measurement items provide the mean number of conversational service RBs in the CS domain at different UL and DL bit rates in the RNC.

The number of RBs for conversational services are sampled periodically in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.Traffic for PS R99 DL Throughput KPIs and Relative Counters (per RNC):

VS.R99PSLoad.DLThruput.RNC

VS.R99PSLoad.ULThruput.RNC

This measurement item provides the downlink/uplink traffic of all the R99 services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.

The RNC periodically takes a sample from the downlink/uplink 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 mean downlink/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.R99PSLoad.MaxDLThruput.RNC

VS.R99PSLoad.MaxULThruput.RNCThis measurement item provides the maximum downlink/uplink traffic of all the R99 services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.

The RNC periodically takes a sample from the downlink/uplink traffic values of all the R99 services in the PS domain. At the end of the measurement period, the RNC calculates the maximum downlink/uplink traffic of all the R99 services in PS domain within the RNC. The mean downlink/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.Traffic for HSDPA DL Throughput KPIs and Relative Counters (per RNC): VS.HSDPAPSLoad.DLThruput.RNCThis measurement item provides the downlink traffic of all the HSDPA services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.

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 divides the accumulated traffic values by the number of samples to obtain the 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. The item is measured only when the RAN sharing function and MOCN function are switched off.

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

Traffic for HSUPA UL Throughput KPIs and Relative Counters (per RNC):

VS.HSUPAPSLoad.ULThruput.RNCThis measurement item provides the uplink traffic of all the HSUPA services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.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 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.HSUPAPSLoad.MaxULThruput.RNCThis measurement item provides the maximum uplink traffic of all the HSUPA services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.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.

Traffic for PS MBMS DL Throughput KPIs and Relative Counters (per RNC):

VS.MBMSPSLoad.DLThruput.RNCThis measurement item provides the downlink traffic of all the MBMS or IMB services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.The RNC periodically takes a sample from the downlink traffic values of all the MBMS or IMB 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 MBMS or IMB services in the PS domain.The downlink traffic of all the MBMS or IMB 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 or IMB services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.

The RNC periodically takes a sample from the downlink traffic values of all the MBMS or IMB services in the PS domain. At the end of the measurement period, the RNC calculates the maximum downlink traffic of all the MBMS or IMB services in PS domain within the RNC.The downlink traffic of all MBMS or IMB services in the PS domain refers to the traffic obtained at the RLC layer. The data does not include the RLC head data.

Traffic for Common Channels KPIs and Relative Counters (per CELL):

FACH Utility Ratio = [VS.CRNCIubBytesFACH.TX / (60*SP * VS.CRNC.IUB.FACH.Bandwidth)] * 100% B.W for FACH is not fixed, but it depends on the assignment, thats why we tend to calculate the utilization ratio, which represents: at this given B.W, how much do u use of it.

The FACH Utility Ratio should be calculated based on busy hour. VS.CRNCIubBytesFACH.TX

This counter provides the bytes of DL MAC PDUs (including the signaling data and the service data, not including the FP header) sent by the CRNC over the FACH FP on the Iub interface. The measurement involves cells in the active set.

The measurement is triggered when the CRNC sends DL data over the FACH FP on the Iub interface.

Unit: byte

VS.CRNC.IUB.FACH.Bandwidth The counter provides the bandwidth of common channels for the CRNC on the Iub interface in the unit of bytes per second. The measurement involves cells in the active set.

The measurement is triggered when the CRNC sets up or removes a common channel on the Iub interface.

Unit: byte/s RACH Utility Ratio = [VS.CRNCIubBytesRACH.Rx / (60*SP * VS.CRNC.IUB.RACH.Bandwidth)] * 100% B.W for RACH is not fixed, but it depends on the assignment, thats why we tend to calculate the utilization ratio, which represents: at this given B.W, how much do u use of it.

The FACH Utility Ratio should be calculated based on busy hour.

VS.CRNCIubBytesRACH.Rx This counter provides the bytes of UL MAC PDUs (including the signaling data and the service data, not including the FP header) received by the CRNC over the RACH FP on the Iub interface. The measurement involves cells in the active set.

The measurement is triggered when the CRNC sends UL data over the RACH FP on the Iub interface.

VS.CRNC.IUB.RACH.Bandwidth The counter provides the bandwidth of common channels for the CRNC on the Iub interface in the unit of bytes per second. The measurement involves cells in the active set.


Unit: byte/s

PCH Utility Ratio = [VS.CRNCIubBytesPCH.Tx / (60*SP * VS.CRNC.IUB.PCH.Bandwidth)] * 100% B.W for PCH is not fixed, but it depends on the assignment, thats why we tend to calculate the utilization ratio, which represents: at this given B.W, how much do u use of it.

The FACH Utility Ratio should be calculated based on busy hour.

VS.CRNCIubBytesPCH.Tx This counter provides the bytes of DL MAC PDUs (not including the FP header) sent by the CRNC over the PCH FP on the Iub interface. The measurement involves cells in the active set.

The measurement is triggered when the CRNC sends DL data over the PCH FP on the Iub interface.

VS.CRNC.IUB.PCH.Bandwidth The counter provides the bandwidth of common channels for the CRNC on the Iub interface in the unit of bytes per second. The measurement involves cells in the active set.


Unit: byte/sTraffic Iub Volume for different services KPIs and Relative Counters (per CELL): VS.SRNCIubBytesCSConv.Rx

VS.SRNCIubBytesCSConv.Tx

VS.SRNCIubBytesCSStr.Rx

VS.SRNCIubBytesCSStr.Tx

VS.SRNCIubBytesPSR99Conv.Rx

VS.SRNCIubBytesPSR99Conv.Tx

VS.SRNCIubBytesPSR99Str.Rx

VS.SRNCIubBytesPSR99Str.Tx

VS.SRNCIubBytesPSR99Int.Rx

VS.SRNCIubBytesPSR99Int.Tx VS.SRNCIubBytesPSR99Bkg.Rx

VS.SRNCIubBytesPSR99Bkg.Tx This counter provides the bytes of DL/UL MAC PDUs received/sent by the SRNC over the DCH FP that carries different services on the Iub interface. The measurement involves cells in the active set.

The measurement is triggered when the SRNC sends/receives DL data over the DCH FP (not including the EDCH FP) that carries different services on the Iub interface. The FP header is not included.

Unit: byte

Traffic AMR Service KPIs and Relative Counters (per CELL): VS.RB.AMR.UL.4.75

VS.RB.AMR.DL.4.75

VS.RB.AMR.UL.5.15

VS.RB.AMR.DL.5.15

VS.RB.AMR.UL.5.9

VS.RB.AMR.DL.5.9

VS.RB.AMR.UL.6.7

VS.RB.AMR.DL.6.7

VS.RB.AMR.UL.7.4

VS.RB.AMR.DL.7.4

VS.RB.AMR.UL.7.95

VS.RB.AMR.DL.7.95

VS.RB.AMR.UL.10.2

VS.RB.AMR.DL.10.2

VS.RB.AMR.UL.12.2

VS.RB.AMR.DL.12.2

These counters provide the number of AMR users with different UL and DL rates in the cells in the active set.The number of AMR users with each UL or DL rate is sampled every 30 seconds in the cells in the active set. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.

Traffic for PS Service KPIs and Relative Counters (per CELL): VS.RB.PS.Str.UL.DifferentRate1

VS.RB.PS.Str.DL.DifferentRate1

VS.RB.PS.Int.UL.DifferentRate2

VS.RB.PS.Int.DL.DifferentRate2

VS.RB.PS.Bkg.UL.DifferentRate2 VS.RB.PS.Bkg.UL.DifferentRate2Where DifferentServiceRate1 means the rates are: 8, 16, 32, 64, 128, 144, [256,384] (kbps)Where DifferentServiceRate2 means the rates are: 8, 16, 32, 64, 128, 144, 256, 384 (kbps)These counters provide the average number of RBs for PS R99 for different services with different UL and DL rates in the cells in the active set.

The RNC takes a sample every 5 seconds from the number of PS for different service RBs at different bit rates. At the end of the measurement period, the RNC divides the accumulated number of different service RBs at each bit rate by the number of samples to obtain the mean number of PS for different service RBs. In this case, the RNC measures the item in each cell that the UE camps on.

Traffic KPI HSDPA DL Throughput KPIs and Relative Counters (per CELL): VS.HSDPA.UE.Mean.CellThe counter provide the average 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;

VS.HSDPA.DC.PRIM.UE.Mean.Cell

These counters provide the average number of DC-HSDPA UEs whose anchor carrier is the current cell in a serving cell.

VS.HSDPA.DC.SEC.UE.Mean.CellThese counters provide the average number of DC-HSDPA UEs whose supplementary carrier is the current cell in a serving cell.

VS.HSDPA.64QAM.UE.Mean.Cell

This counter provides the average number of 64QAM UEs in a serving cell. VS.HSDPA.MIMO.UE.Mean.Cell

This counter provides the average number of MIMO UEs in a serving cell. VS.HSDPA.MIMO64QAM.UE.Mean.CellThis counter provides the average number of MIMO+64QAM UEs in a serving cell.

VS.HSDPA.UE.Max.Cell

The counter provide the 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 selecting the maximum value of sample data in the period, the maximum number of HSDPA UEs in the measurement period is obtained.

VS.HSDPA.UE.Max.CAT1.6 / 7.10 / 11.12 / 13.14 / 15.16 / 17.20 / 21.24 / 25.28

VS.HSDPA.UE.Mean.CAT1.6 / 7.10 / 11.12 / 13.14 / 15.16 / 17.20 / 21.24 / 25.28These counters provide the average and maximum number of HSDPA UEs with various categories in a serving cell. The HSDPA UEs with categoriy 21-28 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.

HSDPA RLC Traffic Volume (M bytes) = VS.HSDPA.MeanChThroughput.TotalBytes / (1024 * 1024)

This KPI provides the total downlink bytes of all the HSDPA MAC-d flows in a cell.

When the data is transmitted to an HSDPA serving cell, the RNC measures the number of total bytes sent in the downlink (including data of all types of services) at the RLC layer for the MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.

Unit: Byte HSDPA RLC Throughput (Mbps) = VS.HSDPA.MeanChThroughput.TotalBytes * 8 / (1024*1024 * SP * 60)

This KPI indicates the mean downlink throughput for ONE HSDPA UE in a cell.

When the data is transferred to an HSDPA serving cell, the RNC measures the data transfer time of all the UEs and the total bytes sent in the cell. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean downlink throughput of MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.Unit: Kbit/sec VS.HSDPA.MeanChThroughput.TotalBytesThis counter provides the mean downlink throughput of single MAC-d flows in a cell.

When data is sent in an HSDPA serving cell, the RNC measures the data transfer time of all the UEs and the total bytes sent in the cell. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean downlink throughput of MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.

Traffic KPI HSUPA UL Throughput KPIs and Relative Counters (per CELL): VS.HSUPA.UE.Mean.CellThese counters provide the average number of HSUPA UEs in a serving cell.

The system periodically takes samples of the number of HSUPA 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 UEs in the measurement period is obtained

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

These counters provide the maximum number of HSUPA UEs in a serving cell.

The system periodically takes samples of the number of HSUPA UEs. At the end of the measurement period by selecting the maximum value of sample data in the period, the maximum number of HSUPA UEs in the measurement period is obtained.

VS.HSUPA.UE.Max.CAT1.4 / 5 / 6 / 7 ( VS.HSUPA.UE.Mean.CAT1.4 / 5 / 6 /7

These counters provide the average and maximum number of HSUPA UEs with various categories in 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.

HSUPA RLC Traffic Volume (M bytes) = VS.HSUPA.MeanChThroughput.TotalBytes / (1024 * 1024) This counter provides the total uplink bytes of all the HSUPA MAC-d flows in a cell.

When data is received in HSUPA active cells, the RNC measures the number of total bytes received in the uplink (including data of different services) at the RLC layer for the MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.Unit: Byte HSUPA RLC Throughput (Mbps) = VS.HSUPA.MeanChThroughput.TotalBytes * 8 / (1024* 1024 * SP * 60)

This counter indicates the mean downlink throughput for ONE HSUPA UE in a cell.

When the data is received in HSUPA active cells, the RNC measures the data transfer time of all the UEs and the total bytes received in the cell. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean uplink throughput of MAC-d flow in the cell. The RLC header and the retransfer data are excluded.

Unit: Kbit/sec

VS.HSUPA.MeanChThroughput.TotalBytes This counter provides the number of total bytes received in uplink of all the HSUPA MAC-d flows in a cell.

When data is received in HSUPA active cells, the RNC measures the number of total bytes received in the uplink (including data of different services) at the RLC layer for the MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.In the case of a soft handover, the RNC measures the number of bits received after combining in all cells of the active set.Load Reshuffling (Duration in LDR State) KPIs and Relative Counters (per CELL): VS.LCC.LDR.Time.DLPower

VS.LCC.LDR.Time.ULPower

VS.LCC.LDR.Time.DLCode

VS.LCC.LDR.Time.DLCE

VS.LCC.LDR.Time.ULCE

VS.LCC.LDR.Time.DLIub

VS.LCC.LDR.Time.ULIub

These counters provide the duration of a cell in LDR state due to congestion of various resources.

If the cell is in LDR state due to congestion of various resources, in a measurement period the RNC measures the duration that the cell is in LDR state due to uplink or downlink congestion of various resources.

Unit: SecLoad Reshuffling (Times in LDR State) KPIs and Relative Counters (per CELL): VS.LCC.LDR.Num.DLPower VS.LCC.LDR.Num.ULPowerWhen a cell is in LDR state due to power (Equivalent Number of Users) congestion, VS.LCC.LDR.Num.ULPower takes statistics of the number of times in LDR state for the uplink of the cell, whereas VS.LCC.LDR.Num.DLPower for the downlink of the cell.

When a cell is in LDR state due to power (Equivalent Number of Users) congestion, This measurement item provides the number of times in LDR state within the cell. VS.LCC.LDR.Num.DLCode

When a cell is in LDR state due to code resource congestion, This measurement item provides the number of times in LDR state for the downlink of the cell.

When a cell is in LDR state due to code resource congestion, This measurement item provides the number of times in LDR state within the cell where the UE camps on. VS.LCC.LDR.Num.DLCE

VS.LCC.LDR.Num.ULCE

When a cell is in LDR state due to Channel Element (CE) resource congestion, VS.LCC.LDR.Num.ULCE takes statistics of the number of times in LDR state for the uplink of the cell, whereas VS.LCC.LDR.Num.DLCE for the downlink of the cell.

When a cell is in LDR state due to CE resource congestion, This measurement item provides the number of times in LDR state within the cell where the UE camps on. VS.LCC.LDR.Num.DLIub

VS.LCC.LDR.Num.ULIub

When a cell is in LDR state due to Iub transmission resource congestion, VS.LCC.LDR.Num.ULIub takes statistics of the number of times in LDR state for the uplink of the cell, whereas VS.LCC.LDR.Num.DLIub for the downlink of the cell.

When a cell is in LDR state due to Iub transmission resource congestion, This measurement item provides the number of times in LDR state within the cell.Load Reshuffling (LDR Actions) KPIs and Relative Counters (per CELL): VS.LCC.LDR.DL.BERateDown

VS.LCC.LDR.UL.BERateDown

When the cell is in basic congestion, the RNC selects certain UEs for BE service downsizing to relieve congestion. These counters provide the number of UEs performing BE service downsizing according to the UL or DL congestion.

When the cell is in basic congestion, the RNC sends the RADIO BEARER RECONFIGURATION message to the UE through the UU interface every time the RNC selects a UE to perform BE service downsizing. The measurement is triggered at point A as shown in the following figure. The RNC measures the related counter in the cell where the UE camps on according to the UL or DL congestion.

VS.LCC.LDR.DL.QosReNego

VS.LCC.LDR.UL.QosReNego

When the cell is in basic congestion, the RNC decreases the service QoS of certain UEs performing uncontrollable real-time service to relieve congestion. These counters provide the number of UEs performing uncontrollable real-time service QoS renegotiation according to the UL or DL congestion.

The measurement is triggered at point A as shown in the following figure. When the cell is in basic congestion, the RNC selects certain UEs to perform QoS renegotiation. At the same time, the RNC sends the RAB MODIFY REQUEST message to the CN. In this case, the RNC measures the related counter in the cell where the UE camps on according to the UL or DL congestion.

VS.LCC.LDR.AMRRateDL

VS.LCC.LDR.AMRRateUL

When the cell is in basic congestion, the RNC selects certain UEs to perform AMR rate decrease. These counters provide the number of UEs performing AMR rate decrease according to the UL or DL congestion.

When the cell is in basic congestion, according to the UL or DL congestion, the RNC measures the related counters in the cell where the UE camps on every time the RNC selects a UE to perform AMR rate decrease.

VS.LCC.LDR.CodeAdj.Succ

When a cell is in basic congestion of downlink code resources, the RNC selects certain UEs in the cell to perform code adjustment so that some idle codes are combined to meet the requirement of a higher rate. This counter provides the number of UEs that has performed code adjustment successfully in a cell.

After detecting a basic congestion of downlink code resources, the RNC selects some UEs in the cell and checks whether the congestion can be eliminated by performing code adjustment on these UEs. If the congestion cannot be eliminated, the RNC periodically selects other UEs in the cell and checks whether the congestion can be eliminated until it has successfully selected certain UEs.

Then, the RNC performs code adjustment on the selected UEs. This counter is measured after the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE. The RNC determines that the code adjustment is successful after receiving this message.

VS.LCC.LDR.MbmsPowerDec

When the cell is in basic congestion, the RNC selects certain MBMS services to perform power decreasing. This counter provides the number of MBMS services performing power decreasing in a cell.

When the cell is in basic congestion, the RNC measures the counter in the cell where the MBMS service is processed every time the RNC selects an MBMS service to perform power decreasing. VS.LCC.LDR.InterFreq

VS.LCC.LDR.HSDPA.InterFreq

VS.LCC.LDR.HSUPA.InterFreq

When the cell is in basic congestion, the RNC selects certain UEs to perform inter-frequency load handover. VS.LCC.LDR.InterFreq is used to measure the number of UEs performing inter-frequency handovers. VS.LCC.LDR.HSDPA.InterFreq is used to measure the number of HSDPA UEs performing inter-frequency handovers. VS.LCC.LDR.HSUPA.InterFreq is used to measure the number of HSUPA UEs performing inter-frequency handovers.

When the cell is in basic congestion, VS.LCC.LDR.InterFreq is measured in the cell where the UE camps on every time the RNC selects a UE to perform inter-frequency handover. If the RNC selects an HSDPA UE, VS.LCC.LDR.HSDPA.InterFreq is measured in the cell where the UE camps on. If the RNC selects an HSUPA UE, VS.LCC.LDR.HSUPA.InterFreq is measured in the cell where the UE camps on.

VS.LCC.LDR.InterRATCS

VS.LCC.LDR.InterRATPS

VS.LCC.LDR.HSDPA.InterRATCS

VS.HSDPA.LDR.InterRATPS

VS.LCC.LDR.HSUPA.InterRATCS

VS.LCC.LDR.HSUPA.InterRATPS

When the cell is in basic congestion, the RNC selects certain UEs to perform CS/PS inter-RAT load handover. VS.LCC.LDR.InterRATCS is used to measure the number of UEs performing CS/PS inter-RAT handovers. VS.LCC.LDR.HSDPA.InterRATCS is used to measure the number of HSDPA UEs performing CS/PS inter-RAT handovers. VS.LCC.LDR.HSUPA.InterRATCS is used to measure the number of HSUPA UEs performing CS/PS inter-RAT handovers.

When the cell is in basic congestion, VS.LCC.LDR.InterRATCS is measured in the cell where the UE camps on every time the RNC selects a UE to perform CS/PS inter-RAT handover. If the RNC selects a HSDPA UE, VS.LCC.LDR.HSDPA.InterRATCS is measured in the cell where the UE camps on. If the RNC selects a HSUPA UE, VS.LCC.LDR.HSUPA.InterRATCS is measured in the cell where the UE camps on.

Over Load Control (Duration in LDR State) KPIs and Relative Counters (per CELL): VS.LCC.OLC.DL.Time VS.LCC.OLC.UL.Time

These counters provide the duration of UL or DL overload congestion in a cell.

After a cell is set up, the RNC measures the durations of UL or DL overload congestion in the cell in a measurement period.

Unit: secOver Load Control (Times in LDR State) KPIs and Relative Counters (per CELL): VS.LCC.OLC.DL.Num VS.LCC.OLC.UL.Num

These counters provide the number of UL or DL overload congestion in a cell. A cell enters the congestion state when the uplink power or downlink power exceeds the preset Overload Control (OLC) threshold.

The measurement is triggered at point A as shown in the following figure. After receiving the COMMON MEASUREMENT REPORT message from the NodeB, the RNC measures the related counter in the cell where the overload congestion occurs at UL or DL.

Over Load Control (LDR Actions) KPIs and Relative Counters (per CELL): VS.LCC.OLC.DL.TF VS.LCC.OLC.UL.TF

When the cell is in overload congestion, the RNC selects certain UEs performing BE services to implement TF control, that is, reduce the BE throughput based on the MAC control though the TFC selection process. These counters provide the number of UEs performing BE service TF control.

When the cell is in overload congestion, every time the RNC selects a UE to perform BE service TF control, the RNC measures the related counters in the cell where the UE camps on according to the UL or DL overload congestion.

VS.LCC.OLC.D2C

When the cell is in overload congestion, the RNC transfer certain UEs performing BE services to common channels (CCHs) to decrease the throughput of interactive and background services, thus reducing the cell load. This counter provides the number of UEs performing BE services that are transferred to CCHs.

When the cell is in overload congestion, the RNC measures the counter in the cell where the UE camps on every time a UE performing BE services is transferred to CCH. VS.LCC.OLC.DL.UserRel

VS.LCC.OLC.UL.UserRel

VS.HSDPA.OLC.UserRel

VS.LCC.OLC.HSUPA.UserRel

When a cell is in overload congestion, and if the RNC cannot relieve the congestion through BE service TF control, it shall select some UEs to release from the cell. VS.LCC.OLC.UL.UserRel: number of UEs released due to uplink overload congestion. VS.LCC.OLC.DL.UserRel: number of UEs released due to downlink overload congestion. VS.LCC.OLC.HSUPA.UserRel: number of HSUPA UEs released due to overload congestion. VS.HSDPA.OLC.UserRel: number of HSDPA UEs released due to overload congestion.

The measurement of VS.LCC.OLC.UL.UserRel/ VS.LCC.OLC.DL.UserRel is triggered when the RNC releases a UE due to overload congestion. The measurement of VS.LCC.OLC.HSUPA.UserRel is triggered when the RNC releases a HSUPA UE due to overload congestion. The measurement of VS.HSDPA.OLC.UserRel is triggered when the RNC releases a HSDPA UE due to overload congestion.

Downlink/Uplink DCH DCCC Attempts (Rate Reallocation) KPIs and Relative Counters (per CELL): VS.DCCC.AttDownsizing.DL.Thr VS.DCCC.AttDownsizing.UL.Thr

VS.DCCC.AttDownsizing.DL.Cov

VS.DCCC.AttDownsizing.UL.Cov

VS.DCCC.AttDownsizing.DL.Cong

VS.DCCC.AttDownsizing.UL.CongThese counters provide the number of downlink/uplink DCH DCCC downsizing attempts based on different strategies in the best cell where the UE camps on.

The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the related counter based on different DCCC strategies in the best cell where the UE camps on if downlink/uplink service is carried on the DCH.

VS.DCCC.AttUpsizing.DL.Thr

VS.DCCC.AttUpsizing.UL.Thr

This counter provides the number of downlink/uplink DCH DCCC upsizing attempts based on the throughput or RLC BO in the best cell where the UE camps on.

The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counter based on the throughput or RLC BO in the best cell where the UE camps on if downlink/uplink service is carried on the DCH.

Downlink/Uplink DCH DCCC Success (Rate Reallocation) KPIs and Relative Counters (per CELL): VS.DCCC.SuccDownsizing.DL.Thr VS.DCCC.SuccDownsizing.UL.Thr

VS.DCCC.SuccDownsizing.DL.Cov

VS.DCCC.SuccDownsizing.UL.Cov

VS.DCCC.SuccDownsizing.DL.Cong

VS.DCCC.SuccDownsizing.UL.CongThese counters provide the number of successful downlink/upink DCH DCCC downsizings based on different strategies in the best cell where the UE camps on.

The measurement is triggered at point B as shown in the following figure. When receiving the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures the related counter based on different DCCC strategies in the best cell where the UE camps on if downlink/uplink service is carried on the DCH.

VS.DCCC.SuccUpsizing.DL.Thr VS.DCCC.SuccUpsizing.UL.Thr

This counter provides the number of successful downlink/uplink DCH DCCC upsizings based on the throughput or RLC BO in the best cell where the UE camps on.

The measurement is triggered at point B as shown in the following figure. During the DCCC upsizing, when receiving the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures the counter based on the throughput or RLC BO in the best cell where the UE camps on if downlink/uplink service is carried on the DCH.

DCCC (UE State Transition) KPIs and Relative Counters (per CELL): VS.DCCC.D2C.Att VS.DCCC.C2D.Att

The measurement items take statistics of the number of attempts between channels of different types for R99 services in the best cell.

The measurement is triggered at point A as shown in the figure. When sending a RADIO BEARER RECONFIGURATION message to a UE, the RNC measures the item in the best cell according to the channel transfer type.

VS.DCCC.Succ.D2F

VS.DCCC.Succ.F2D

These counters provide the number of successful dynamic channel conversions from DCH to FACH or from FACH to DCH for R99 service in a cell during the RAB modification procedure and DCCC procedure. The number of successful dynamic channel conversions from DCH to FACH is measured in the best cell where the UE camps on before channel conversion.

The measurement is triggered at point B as shown in the following figure. In the process of dynamic channel conversion, when the RNC receives the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, if the DCH is converted to the FACH, the RNC measures the related counter in the best cell where the UE camps on before channel conversion. If the FACH is converted to the DCH, the RNC measures the related counter in the cell where the UE camps on after channel conversion.

[Huawei Technologies] | Traffic & Cell Algorithms KPIs and Relative Counters1

traffic & cell algorithmskpi’s and relative counter’s

Documents