3G.LTE Network Capacity Management.pptx

3G Congestion and Capacity Algorithms A Practical Guide

1

3G/LTE Huawei

RAN Capacity Management

1

1

A Practical Guide

Introduction

This presentation is not a technical document, but more of a practical guide of how deal with 3G/LTE Capacity and Congestion. Including

Types of Congestion

How to Monitor Capacity Resources

Basic Capacity Features (CAC, LDR etc)

Monitoring and Identifying Capacity Issues

Current Techniques Used to Optimize Capacity

Suggestions for Future Trials and Network Strategy

Capacity Resources

There are 4 Separate Capacity Resources to monitor in UMTS

Power

Code

Baseband Resources (CE)

Iub Resources

DL Power

Most Cells are set with a MaxTxPower of 43dBm/20W

After Pilot (typically 10%) and common channels, the rest of available power is used to carry traffic

As Traffic increases, so does the power requirement

When available power runs out, there is a risk of call drop as power is not available to maintain Ec/No

UL Power

UL Power in normal circumstances is a measure of the RTWP being received

We use a Equivalent User Number as the algorithm for measuring UL Load

Currently MaxULUserNumber is set to 160

DL Codes

Channelisation Codes are a Cell level resource and are Allocated to users from the Code Tree depending on Service

HSDPA can use up to 15 Codes should they not be currently used by R99 Services

Baseband Resource (CE)

Baseband Resource, otherwise known as Channel Elements or Credits, is the Hardware resource installed at NodeB Level

Each WBBP Board contains 256 CEs and installed at NodeB Level and allocated to a Resource Group

CEs are dynamically allocated to users across cells in that resource group based on service

Huawei has a limitation of max 6 Cells in a RG, for a NodeB

Iub Resource

Iub resource is the number of installed E1s or the size of the configured IP Bandwidth

Resources and configuration

In Huawei WCDMA network, to avoid the congestion and blockage of the service, we have to monitor the following resources :
NE TypeResourceNodeB LevelCE card and licenseUL and DL Iub bandwidthCell LevelOVSF codeUL power DL power

RAN Resource diagram

BBU

RRU1

RNC

RRU2

RRU3

DL total power/DL ENU

RTWP/UL ENU

OVSF Code (DCH/HS-PDSCH)


RTWP/UL ENU



RTWP/UL ENU


CE card

CE license

HS-PDSCH code license

UL/DL Iub bandwidth

Traffic and KPI statistic

To associate the actual situation of resource usage we have to consider in term of :

CS and PS traffic

Congestion

Utilization

together

we can make

it convergence

Service distribution

Each service type will occupy different resources. Hence we should divide the traffic volume corresponding to each service type to understand the characteristic of the cell.

AMR

VP

PS R99 DL

PS R99 UL

HSDPA

HSUPA

together

we can make

it convergence

CE Resource Description

CE is the pool resource at NodeB level, all cells connected to NodeB will share the same CE resource.

Number of CEs will be vary upon the model of card.

Zain typically uses (UL/DL 256 CEs).

The monitoring will be done at NodeB level.

Number of UL/DL license can be assigned independently.

The monitoring can be done separately for UL and DL.

together

we can make

it convergence

OVSF Code Resource Description

OVSF Code is the limit resource of each cell. The expansion cant be possible in a single cell. OVSF Code will be limited only DL direction.

Typical usage of OVSF code

AMR : SF128 SF256

VP : SF32

PS R99 DL : SF8 SF128

HSDPA : SF16

Maximum is 15 * SF16

HSDPA Code usage is depended on Manual or Automatic assignment. More OVSF code manually assigned to HSDPA is less OVSF code left for R99.

together

we can make

it convergence

UL Power Resource Description

Due to the rejection by Call Admission Control, the increment in UL load can cause service rejection and slow down the data service.

For Huawei, UL power resource can divided into 2 type. One is real load in term of RTWP (Algorithm 1), another one is equivalent load in term of ENU (Algorithm 2).

We are using Algorithm 2 as default.

together

we can make

it convergence

DL Power Resource Description

DL Power Limit is considered at RRU total power. Typical use of RRU power is 20 (43dBm) and 40 watt (46dBm).

In general, the common control channel will consume about 10% of total power.

The power consumption of each service will be different as well as the radio condition of each UE (e.g. distance, RSCP, Ec/Io)

together

we can make

it convergence

UL and DL Iub Bandwidth Description

Iub is the pool resource at BBU, each RRU have to share same Iub resource.

Typical configuration bandwidth of Iub is 10 and 20 Mbps.

IP based Iub transmission (100 Mbps).

together

we can make

it convergence

Total resource usage module

Power

OVSF code

CE

Iub

-Desire QoS

Congestion

CS user

PS R99 User

HSDPA User

HSUPA User

Service distribution

Resources

User experience

Rejection

2 states of service interruption

The user cant get the service (rejection).

The user cant get at the desire QoS (low throughput of data service)

together

we can make

it convergence

Power CAC Algorithm

Power CAC is applied on both DL and UL

We have to consider our selected algorithm. The monitoring method will be different. Algorithm 1 or Algorithm 2 ?

Huawei default for DL is Algorithm1

Monitor TCP usage for load calculation

Huawei default for UL is Algorithm2

Monitor ENU for UL load calculation

together

we can make

it convergence

Total RRU power setting

Total Carrier Power (TCP) is one of limited resource depending upon RRU total power output that impact directly to cell capacity and performance. Although its the same RRU power, it may different in the capacity because of UE distribution in a cell. To overview the power setting in a cell, we can check parameter setting of total power and CPICH power.

CPICH Power

MaxPCPICHPower (~ 10% of total cell power)

Default = 33 dBm

Total Power

MaxTxPower

Default = 43 dBm according to license

By the way, CPICH power + common channel will consume around 10% of total cell power.

together

we can make

it convergence

TCP Counter and monitoring

Example : BKD0040U3

MaxTxPower = 43 dBm

MaxPCPICHPower = 33 dBm

We can monitor TCP usage from counter

VS.MaxTCP (R99+HSDPA)

VS.MeanTCP (R99+HSDPA)

VS.MaxTCP.NonHS (R99)

VS.MeanTCP.NonHS (R99)

We check parameter setting for RAB CAC

DL threshold of Conv AMR service[%] = 80

DL threshold of Conv non_AMR service[%] = 80

DL threshold of other services[%] = 75

DL handover access threshold[%] = 85

DL total power threshold[%] = 90

RRC CAC considers OLC Trigger Threshold for admission

DL OLC trigger threshold[%] = 95

MaxTxPower

PCPICH

MaxTxPower

PCPICH

PCPICH + Common channel

PCPICH + Common channel

together

we can make

it convergence

UL ENU counter and monitoring

Take a look at parameter setting of maximum allowed equivalent user number

UL total equivalent user number = 80 (by default)

Example : BKD0040U3

Have a look UL ENU from counter VS.RAC.UL.TotalTrfFactor

UL ENU = 27.694 at 21:30 PM.

Total UL Load = 27.694/80 = 34.62%

We check parameter setting for RAB CAC

UL threshold of Conv AMR service[%] = 75

UL threshold of Conv non_AMR service[%] = 75

UL threshold of other services[%] = 60

UL handover access threshold[%] = 80

UL total power threshold[%] = 83

RRC CAC considers OLC Trigger Threshold for admission

-UL OLC trigger threshold[%] = 95

together

we can make

it convergence

OVSF and CE Consumption for DL DCH service
Rate (kbps)SFCE Consumption3.4256113.612818128116128132641643221281641441642568838488

together

we can make

it convergence

OVSF and CE Consumption for UL DCH service
Rate (kbps)SFCE Consumption3.4256113.664186411664132321.5641631288514485256410384410

together

we can make

it convergence

OVSF and CE Consumption for HSUPA
Rate (kbps)SFCE Consumption825611664132641.564641.5128323144832564538441060841014502SF23220482SF23228902SF2+2SF44857602SF2+2SF448

together

we can make

it convergence

OVSF Code Usage

Example : BKD0040U3

Check parameter setting

LST CELLHSDPA

Allocate Code Mode = MANUAL

Code Number for HS-PDSCH = 10

By method of reservation by MANUAL then total 10*SF16 = 160 SF256 Code will be reserved for HS-PDSCH Code only.

160 is reserved for HS-PDSCH

Maximum 256 code is available for 1 cell

Total 160 + 19 common channel = 179 codes are occupied and forbidden for traffic channel.

Free code left for traffic channel = 256-179 = 77 Codes

However, 1 SF32 is reserved for handover during CAC process . The actual free left code should be about 77- 8 = 69 Codes or about 34 AMR Voice.

Total 179 codes is occupied.

Free code for traffic channel

together

we can make

it convergence

Service rejection due to lack of resource

The rejection occurs at CAC phase, RNC check the network resources. If found insufficient resources for a new service, CAC will reject the service.

The rejection may occur at RRC or RAB setup state. RRC is more critical than RAB rejection as RRC CAC threshold (typical 95% load) is higher than RAB CAC threshold.

To ensure the proper rejection due to lack of resource, we can review the CAC threshold setting prior to perform further analysis.

together

we can make

it convergence

Counter of RRC rejection due to lack of resource

RRC Connection Setup Rejection due to lack of resource

together

we can make

it convergence

Counter of CS RAB rejection due to lack of resource

Number of CS RAB Unsuccessfully Established due to Radio Resource Congestion (Cell)

Number of CS RAB Unsuccessfully Established due to Iub Bandwidth Congestion (Cell)

together

we can make

it convergence

Counter of PS RAB rejection due to lack of resource

Number of PS RABs Unsuccessfully Established due to Radio Resource Congestion (Cell)

Number of RABs Failing to Be Set Up in PS Domain due to Iub Bandwidth Congestion (Cell)

together

we can make

it convergence

Found UL CE congestion associates with high UL CE Usage

RRC Setup Congestion Monitor

Example : BKD0040U3

Note : When RRC Setup failure, RAB setup will not initiate. Therefore RAB Setup congestion can not be seen.

together

we can make

it convergence

CS RAB Congestion monitoring

Found some congestion of power and code

Code is DL OVSF Code

Power is either DL or UL power

Associate with TCP and UL ENU, we can judge that power congestion should come from DL

Example : BKD0040U3

Congestion but just quite small

TCP

UL ENU

LOW ~ 25 ENUs

together

we can make

it convergence

UL and DL CE Usage Monitoring

Example : BKD0040U3

As PS RAB congestion has been found in cause UL CE congestion. From CE usage monitoring we can see sometimes the maximum usage touches all available CE.

together

we can make

it convergence

Summary

Capacity Features & Algorithms

Mechanisms are put in place to monitor the resources on a cell to maintain the integrity of the network

CAC Call Admission Control sets capacity limits for each resource such that new requests do not lead to failures of existing connections

LDR Load Re-Shuffling involves different techniques to re-allocate resources or balance load

Call Admission Control

RRC and RAB Rejections are the result of a CAC Failure, meaning resources are not available to setup the required service

Values are set to define maximum usage for each resource, after which it will reject any new admissions. Rejections will start to occur before 100% utilisation, as the network needs to leave a buffer to maintain existing connection

For DL Power, the cell calculates its existing TCP+calculated TCP increase based on service.

For UL Power, preferred algorithm is using Equivelant User Number.

Using MaxTxPower=460 and MaxULUserNumber=160 as reference, it uses thresholds below to admit or reject

Resource threshold : DL Power Load

DL OLC Triggering threshold[%] = 95

DL total power threshold[%] = 90

DL handover access threshold[%] = 85

UL OLC Release threshold[%] = 85

DL threshold of Conv AMR service[%] = 80

DL threshold of Conv non_AMR service[%] = 80

DL threshold of other services[%] = 75

DL LDR Trigger Threshold[%] = 70

DL LDR Release Threshold[%] = 60

Overload Congestion -> Overload Congestion Control

MaxTxPower = 43 or 46 dBm (case Algorithm1)

All RAB service reject

Handover reject

PS R99 RAB Service reject

AMR RAB reject

RRC reject

Basic Congestion-> LDR


together

we can make

it convergence

Resource threshold : UL Power Load

UL OLC Triggering threshold[%] = 95%

UL total power threshold[%] = 83

UL handover access threshold[%] = 80

UL threshold of Conv AMR service[%] = 75

UL threshold of Conv non_AMR service[%] = 75

UL threshold of other services[%] = 60

UL LDR Trigger Threshold[%] = 55

UL LDR Release Threshold[%] = 45

Overload Congestion -> Overload Congestion Control

RRC reject



UlTotalEqUserNum = 80 (case Algorithm2)

All RAB service reject

Handover reject

PS R99 RAB Service reject

AMR RAB reject

UL OLC Release threshold[%] = 85%

together

we can make

it convergence

Call Admission Control

For Codes and Credits the algorithm is slightly simpler. It reserves a minimum SF as a spare resource. If this will not be available after new service is admitted, the request is rejected. Incoming Handovers are admitted, if the remaining resource is enough for the incoming service

And Simplest of all algorithms is for HSPA connections. Max User Number is set, requests beyond this value are rejected and a failure pegged as DL/UL Power

Load Re-Shuffling

Load Re-Shuffling can be used to free up resources to make room for new connections

Just as with CAC, utilisation of each resource is monitored. Should it break a threshold, the cell goes into a Basic Congestion State during which it will perform Actions to try and reduce utilisation

Enabled Algorithms and associated trigger levels below

LDR Actions

In LDR State, the cell will take the following Actions on its traffic in attempt to reduce load.

It will perform the first action on defined number of RABs and re-assess. If cell is still in LDR state, it will repeat the first action until it fails, before moving to the second action

Iub

Code

Power

CE

Capacity upgrade solution

In resource expansion, these activities would be performed to increase or balance cell capacity (This is assumed that the site has been well optimization)

WBBP upgrade/downgrade

UL/DL CE upgrade/downgrade

Increase UL ENU

Increase total RRU power

Reduce CPICH power

Reduce fix HS-PDSCH code, if code congest from Voice

Increase fix HS-PDSCH code, if low throughput on HSPDA

Increase Iub bandwidth

together

we can make

it convergence

Upgrade Path & Current Optimisation Techniques

First Upgrade Path for Sites with Congestion of Cell Level Resources is to upgrade to 2nd Layer.

Extra WBBP Board

F2 Upgrades generally clear Power Congestion as this is based purely on number of users. Distributing HS Users across 2 Layers reduces number of users on F1/F2 Layer

By modifying MaxHSUserNum on the F1/F2 Layer from baseline Value is 64, to 32 or 32, the DRD Algorithm will assign more HS Users to F2

RF Re-Design

If Congestion still exists with 2 Layers, particularly if there is DL Power or Code Congestion or High RTWP, then this suggests the coverage area should be reviewed !!!

LTE

Page47

LTE Channel Bandwidths

LTE must support the international wireless market and regional spectrum regulations and spectrum availability. To this end the specifications include variable channel bandwidths selectable from 1.4 to 20 MHz, with subcarrier spacing of 15 kHz.

1 RB=12 Sub-carriers.

For 20 MHz, NRB =20M/(15k*12)=100
Channel bandwidth BWChannel [MHz]1.43 5101520Transmission bandwidth configuration NRB615 255075100
NRB is the number of resource blocks

HUAWEI TECHNOLOGIES CO., LTD.

Huawei Confidential

LTE System Overview

Confidential Information of Huawei. No Spreading Without Permission

The smallest amount of resource that can be allocated in the uplink or downlink is called a resource block (RB). An RB is 180 kHz wide and lasts for one 0.5 ms timeslot. For standard LTE, an RB comprises 12 subcarriers at a 15 kHz spacing,

Admission & Congestion Control in LTE

Page48

RB Usage

QoS satisfaction rate

Admission Control

Congestion Control

Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved.

:32-35pt

: R153 G0 B0

:

FrutigerNext LT Medium

: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:

FrutigerNext LT Regular

: Arial

:18-20pt

(2-5):18pt

:

:

13

.

Load monitoring provides the monitoring results of physical resource block (PRB) usage, QoS satisfaction rate of guaranteed bit rate (GBR) services, and resource limitation indications. The eNodeB determines whether to admit services and perform congestion control based on the load monitoring results.

An eNodeB monitors the PRB usage and QoS satisfaction rate of GBR services to determine the cell load status. Based on the cell load status, admission control and congestion control determine whether to admit GBR services and whether to release low-priority services, respectively. The resource allocation algorithms provide resource limitation indications for load monitoring.

LTE eRAN6.0 Admission & Congestion Control

P-48


RB Usage Monitoring

On uplink, eNodeB will monitoring the RB ratio used by high priority service, including GBR service

Page49


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

In the downlink, radio resources such as PRBs and power are shared by all UEs in a cell. Decreases in the downlink QoS satisfaction rates indicate limited radio resources. The eNodeB performs downlink admission control based only on QoS satisfaction rates.


P-49


QoS Satisfaction Rate Downlink

For QCI=1 VoIP service, the QoS satisfaction rate is represented by the ratio of voice over IP (VoIP) services whose QoS requirements are satisfied in a cell to all VoIP services in the cell.

For QCI=2~4 service, QoS satisfaction rate is evaluated by the following formula with each QCI

GBR Service QoS Satisfaction Rate(QCI2~4)= the scheduled data volume/ the total required GBR data volume

Page50


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

QoS Satisfaction Rate Uplink

Uplink QoS evaluation is similar as downlink

For QCI 1 service, the QoS satisfaction rate is represented by the ratio of voice over IP (VoIP) services whose QoS requirements are satisfied in a cell to all VoIP services in the cell

For QCI=2~4 service, eNodeB evaluates the ratio based on each logical channel group which is configured by RRC

Page51


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

Admission Control

Admission control determines whether to accept the requests for new services and handover services.

Page52


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.


P-52


Non-GBR Service Admission Control

If the following resource check has passed, non-GBR service could be directly admitted.

User number doesnt achieve the maximum number in the license

UE capability is capable for the requested service

No cell congestion indication

After user number, UE capability, SRB could be directly admitted

Page53


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.


P-53


GBR Service Admission Control

GBR service admission control is triggered after preliminary resource check.

QoS satisfaction ratio based admission control is the key technology for GBR service admission control which is used for both uplink and downlink.

For uplink GBR service, besides QoS satisfaction ratio, the following will be considered as well:

Uplink RB usage, if it is low than lower threshold, then GBR service could be directly admitted

Page54


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

Admission Threshold Based on Satisfaction Ratio

The admission threshold for handovers is QcixHoThd.

The admission threshold for new gold services is QcixHoThd plus NewGoldUserOffset.

The admission threshold for new silver services is QcixHoThd plus NewSilverUserOffset.

The admission threshold for new copper services is QcixHoThd plus NewCopperUserOffset.

QcixHoThd QcixHoThd + NewGoldUserOffset QcixHoThd + NewSilverUserOffset QcixHoThd + NewCopperUserOffset 100%

Page55


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

The admission threshold for handovers is lower than that for new services. The eNodeB defines four handover thresholds QcixHoThd (x = 1-4) for each QCIs.

Based on the handover thresholds, the service differentiation can be achieved by setting the admission offsets for new gold, silver, and copper services, depending on the mapping between ARP values and service priorities. The admission offsets are NewGoldUserOffset, NewSilverUserOffset, and NewCopperUserOffset. These offset values apply to both uplink and downlink.


P-55


Admission Decision Based on QoS Satisfaction Rate(Cont.)

Page56

Command for threshold configuration:


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.



Cell Congestion Overview

Congestion can be prevented in most cases if admission control is performed. However, congestion may occur in the following cases:

The services are diverse and the data rates of certain services vary significantly. Variations in the data volume inevitably affect the cell load.

The radio conditions vary because of user mobility. The same service at the same data rate may require different radio resources on different occasions.

Page57


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

Cell Congestion Status Trigger

Page58

The cell is regarded as congested if

The downlink QoS satisfaction rate corresponding to one or more QCIs is lower than the relevant congestion threshold

or if the uplink QoS satisfaction rate is lower than the relevant congestion threshold and the uplink RB usage is high.

Cell congestion indication will be removed if

all QoS satisfaction rate both for uplink and down link is higher than the congestion threshold plus an offset.

The cell is regarded as normal if the QoS satisfaction rates of all QCIs are higher than the corresponding QcixCongThd (x = 14).


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

After cell congestion is triggered, eNodeB immediately notify admission control module to stop admitting new GBR service. Meanwhile, eNodeB will initiate congestion control algorithm


P-58


Threshold Configuration

Page59


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

Cell Congestion Control Solution

If cell is congested, congestion control selects a service that ranks the first in the group of admitted low-priority GBR services and releases the selected service.

After the GBR service is released, the eNodeB checks whether the QoS satisfaction rates of GBR services are restored. If the QoS satisfaction rates of GBR services are not restored, the eNodeB performs the GBR service release procedure again until the congestion is relieved.

Page60


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

Summary

The significance of admission control and congestion control

The important load indications in the eNodeB

Admission control flow, especially QoS satisfaction rate based GBR admission control.

Cause of cell congestion, and solution for congestion control

Interaction between admission control and congestion control

Page61


:32-35pt

: R153 G0 B0

:


: Arial

:30-32pt

: R153 G0 B0

:

:20-22pt

(2-5) :18pt

:

:


: Arial

:18-20pt

(2-5):18pt

:

:

13

.

Course Name

P-61


Thank you

www.huawei.com

Course Name

P-62


3032343638404244

dBm

Average of VS.MaxTCPAverage of VS.MeanTCP

3032343638404244

dBm

Average of VS.MaxTCP.NonHSAverage of VS.MeanTCP.NonHS

05101520253035

Average of VS.RAC.DL.TotalTrfFactorAverage of VS.RAC.UL.TotalTrfFactor

050100150200250300Average of VS.RAB.SFOccupyAverage of VS.RAB.SFOccupy.MAX

00.20.40.60.811.2Sum of VS.RRC.Rej.DLIUBBandCongSum of VS.RRC.Rej.DL.CE.CongSum of VS.RRC.Rej.Power.CongSum of VS.RRC.Rej.ULIUBBandCongSum of VS.RRC.Rej.UL.CE.CongSum of VS.RRC.Rej.Code.Cong

020406080100120140160

UL CE Usage

Sum of VS.LC.ULCreditAvailable.SharedSum of VS.LC.ULMax.LicenseGroup.SharedSum of VS.LC.ULMean.LicenseGroup.Shared

012345678910Sum of VS.RAB.FailEstab.CS.DLIUBBand.CongSum of VS.RAB.FailEstab.CS.ULIUBBand.CongSum of VS.RAB.FailEstCs.Code.CongSum of VS.RAB.FailEstCs.DLCE.CongSum of VS.RAB.FailEstCs.Power.CongSum of VS.RAB.FailEstCs.ULCE.Cong

020406080100120

DL CE Usage

Sum of VS.LC.DLCreditAvailable.SharedSum of VS.LC.DLMax.LicenseGroup.SharedSum of VS.LC.DLMean.LicenseGroup.Shared

Documents

3G.LTE Network Capacity Management.pptx