3g-huawei-ran-resource-monitoring-and-management-ppt (1).ppt

*3G Huawei RAN Resource Monitoring and management

Capacity and resource analysisTo figure out the WCDMA network, we have to associate the several information. As WCDMA blockage can occur at several part also the multiple-service will consume different resource in the network. Furthermore the congestion in WCDMA is consisting of soft and hard blocking. Hence we must gather this information for the analysis. The information will be collected is : Actual resource and configurationTraffic and KPI statisticService distributionFrom these 3 components, we can create 3 dimensions relationship and give the result of enough or inadequate resources for desired service.

Resources and configurationIn Huawei WCDMA network, to avoid the congestion and blockage of the service, we have to monitor the following resources :

NE TypeResourceExpansibleNodeB LevelCE card and licenseNodeB HS-PDSCH code licenseUL and DL Iub bandwidthYesYesYesCell LevelOVSF codeUL power DL powerNoYesYes

RAN Resource diagramBBURRU1RNCRRU2RRU3DL total power/DL ENURTWP/UL ENUOVSF Code (DCH/HS-PDSCH)DL total power/DL ENURTWP/UL ENUOVSF Code (DCH/HS-PDSCH)DL total power/DL ENURTWP/UL ENUOVSF Code (DCH/HS-PDSCH)CE cardCE licenseHS-PDSCH code licenseUL/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 trafficCongestionUtilization

Service distributionEach 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.AMRVPPS R99 DLPS R99 ULHSDPAHSUPA

CE Resource DescriptionCE resource is consisting of hardware and software. CE is the pool resource at NodeB level, all cells connected to NodeB will share the same CE resource.HardwareNumber of CEs will be vary upon the model of card.Truemove typically uses CE Card model WWBP2 (UL/DL128 CEs).The monitor will be done at NodeB level.Software1 License will be equal to 16 CEs.Number of UL/DL license can be assigned independently.The monitor can be done separately for UL and DL.

OVSF Code Resource DescriptionOVSF 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 codeAMR : SF128 SF256 VP : SF32PS R99 DL : SF8 SF128HSDPA : SF16Maximum is 15 * SF16HSDPA Code usage is depended on Manual or Automatic assignment. More OVSF code manually assigned to HSDPA is less OVSF code left for R99.

NodeB HSDPA Code License DescriptionExcept the available number of free OVSF code, HSDPA is required the license.HSDPA code license is a pool resource at BBU as same as CE.Insufficient code license can degrade the throughput of HSDPA user as well.

UL Power Resource DescriptionEven the UL power is not limit corresponding to each UE power, but the noise raise will trig the rejection due to Call Admission Control as well. Hence, 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, another one is equivalent load in term of ENU.

DL Power Resource DescriptionDL Power Limit is considered at RRU total power. Typical use of RRU power in Truemove is 20 and 40 watt.In general, the common control channel will consume about 20% 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)HSDPA will use the remaining power left from R99 service.

UL and DL Iub Bandwidth DescriptionIub is the pool resource at BBU, each RRU have to share same Iub resource.Typical configuration bandwidth of Iub is 10 and 20 Mbps.Truemove deploys IP based Iub transmission.

Total resource usage moduleService distributionResourcesUser experienceRejection2 states of service interruption The user cant get the service (rejection). The user cant get at the desire QoS (low throughput of data service)

Power CAC AlgorithmPower CAC is applied on both DL and ULWe 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 calculationHuawei default for UL is Algorithm2Monitor ENU for UL load calculation

Total RRU power settingTotal 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 PowerMaxPCPICHPower (~ 10% of total cell power)Default = 33 or 36 dBmTotal PowerMaxTxPowerDefault = 43 or 46 dBm according to license

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

TCP Counter and monitoringExample : BKD0040U3MaxTxPower = 43 dBmMaxPCPICHPower = 33 dBm

We can monitor TCP usage from counterVS.MaxTCP (R99+HSDPA)VS.MeanTCP (R99+HSDPA)VS.MaxTCP.NonHS (R99)VS.MeanTCP.NonHS (R99)

We check parameter setting for RAB CACDL threshold of Conv AMR service[%] = 80DL threshold of Conv non_AMR service[%] = 80DL threshold of other services[%] = 75DL handover access threshold[%] = 85DL total power threshold[%] = 90RRC CAC considers OLC Trigger Threshold for admission DL OLC trigger threshold[%] = 95

MaxTxPowerPCPICHMaxTxPowerPCPICHPCPICH + Common channelPCPICH + Common channel

Oversee cell load by ENUEquivalent number of users (ENU) is the indicator from which maps each service type into one normalize cell load. Higher throughput infer the higher ENU value. To get the UL and DL ENU we refer to these counters.VS.RAC.UL.TotalTrfFactorVS.RAC.DL.TotalTrfFactorUL ENUDL ENU

Typical equivalent number of users (ENU)

SeviceENUDCH uplinkDCH downlinkHSDPAHSUPA3.4 kbps SIG0.440.420.281.7613.6 kbps SIG1.111.110.741.893.4 + 12.2 kbps1.441.42--3.4 + 8 kbps (PS)1.351.040.782.263.4 + 16 kbps (PS)1.621.251.112.373.4 + 32 kbps (PS)2.152.191.702.603.4 + 64 kbps (PS)3.453.252.793.143.4 + 128 kbps (PS)5.785.934.924.673.4 + 144 kbps (PS)6.416.615.464.873.4 + 256 kbps (PS)10.1810.499.366.613.4 + 384 kbps (PS)14.2715.5214.179.36

UL ENU counter and monitoring Have a look UL ENU from counter VS.RAC.UL.TotalTrfFactorUL ENU = 27.694 at 21:30 PM.Total UL Load = 27.694/80 = 34.62%We check parameter setting for RAB CACUL threshold of Conv AMR service[%] = 75UL threshold of Conv non_AMR service[%] = 75UL threshold of other services[%] = 60UL handover access threshold[%] = 80UL total power threshold[%] = 83RRC CAC considers OLC Trigger Threshold for admission-UL OLC trigger threshold[%] = 95

OVSF Code Allocation

OVSF and CE Consumption for DL DCH serviceNote : Even HS-PDSCH will not utilize DL CE but A HSDPA User will consume 1*SF256 (1 CE) in DL for A-DCH.

Rate (kbps)SFCE Consumption3.4256113.612818128116128132641643221281641441642568838488

OVSF and CE Consumption for UL DCH service

Rate (kbps)SFCE Consumption3.4256113.664186411664132321.5641631288514485256410384410

OVSF and CE Consumption for HSUPA

Rate (kbps)SFCE Consumption825611664132641.564641.5128323144832564538441060841014502SF23220482SF23228902SF2+2SF44857602SF2+2SF448

OVSF Code UsageExample : BKD0040U3Check parameter settingLST CELLHSDPAAllocate Code Mode = MANUALCode Number for HS-PDSCH = 10By 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-PDSCHMaximum 256 code is available for 1 cellTotal 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

Service rejection due to lack of resourceThe 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.

Counter of RRC rejection due to lack of resourceRRC Connection Setup Rejection due to lack of resource

Counter of CS RAB rejection due to lack of resourceNumber of CS RAB Unsuccessfully Established due to Radio Resource Congestion (Cell)

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

Counter of PS RAB rejection due to lack of resourceNumber 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)

Counter of PS RAB rejection due to lack of resource for different serviceNumber of Unsuccessful PS RAB Setups for Different Services due to Congestion (Cell)

Found UL CE congestion associates with high UL CE UsageRRC Setup Congestion MonitorExample : BKD0040U3Note : When RRC Setup failure, RAB setup will not initiate. Therefore RAB Setup congestion can not be seen.

CS RAB Congestion monitoring

Found some congestion of power and codeCode is DL OVSF CodePower is either DL or UL powerAssociate with TCP and UL ENU, we can judge that power congestion should come from DL

Example : BKD0040U3Congestion but just quite smallTCPUL ENULOW ~ 25 ENUs

UL and DL CE Usage MonitoringExample : BKD0040U3As 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.

Observe the type of serviceExcept the resource usage and rejection, to realize the resource consumption of the cell, we have to figure out the load of each service of a cell to see the distribution and judge which one consumes load the most.The service of a single user may be single-RAB or Multi-RABThe service of a single user will consume balance or unbalance load between UL and DL e.g.AMR user : UL CS AMR and DL CS AMROld Model mobile : DL+UL PS R99iPhone and BB user : UL PS R99 and DL HSDPADatacard user : UL HSUPA and DL HSDPA (all the equipment support HSUPA will support HSDPA).

AMR user number counter in a cellAt the moment AMR user will utilize DL SF128/UL SF64 for each RL.To sum up the number of AMR user we can calculate fromNumber of AMR users =

UL/DL CE consumption for a AMR User = 1/1VS.AMR.Ctrl.DL4.75+VS.AMR.Ctrl.DL5.15+VS.AMR.Ctrl.DL5.9+VS.AMR.Ctrl.DL6.7+VS.AMR.Ctrl.DL7.4+VS.AMR.Ctrl.DL7.95+VS.AMR.Ctrl.DL10.2+VS.AMR.Ctrl.DL12.2

HSDPA+HSUPA user number counter in a cellAssume that HSUPA user is HSDPA user as well. Hence while UL is HSUPA, DL will be HSDPA.Number of HSDPA+HSUPA Users =

A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCHUL CE consumes up to bit rate of HSUPAVS.HSUPA.UE.Mean.Cell

HSDPA+R99 user number counter in a cellTypical mobile in a market will support only HSDPA while using R99 in UL. Therefore,Number of HSDPA+R99 User =

A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCHUL CE consumes up to bit rate of DCHVS.HSDPA.UE.Mean - VS.HSUPA.UE.Mean.Cell

DL+UL PS R99 user number counter in a cellAssume that if the UE model supports only DL R99, the number of DL+UL R99 is equal to number of DL R99 UserNumber of DL+UL R99 User =

DL CE consumes up to bit rate of DL DCHUL CE consumes up to bit rate of UL DCH

VS.RB.DLConvPS.8+VS.RB.DLConvPS.16+VS.RB.DLConvPS.32+VS.RB.DLConvPS.64+VS.RB.DLStrPS.8+VS.RB.DLStrPS.16+VS.RB.DLStrPS.32+VS.RB.DLStrPS.64+VS.RB.DLStrPS.128+VS.RB.DLStrPS.144+VS.RB.DLStrPS.256+VS.RB.DLInterPS.8+VS.RB.DLInterPS.16+VS.RB.DLInterPS.32+VS.RB.DLInterPS.64+VS.RB.DLInterPS.128+VS.RB.DLInterPS.144+VS.RB.DLInterPS.256+VS.RB.DLInterPS.384+VS.RB.DLBkgPS.8VS.RB.DLBkgPS.16+VS.RB.DLBkgPS.32+VS.RB.DLBkgPS.64+VS.RB.DLBkgPS.128+VS.RB.DLBkgPS.144+VS.RB.DLBkgPS.256+VS.RB.DLBkgPS.384

Resource threshold : DL Power LoadDL OLC Triggering threshold[%] = 95DL total power threshold[%] = 90DL handover access threshold[%] = 85UL OLC Release threshold[%] = 85DL threshold of Conv AMR service[%] = 80DL threshold of Conv non_AMR service[%] = 80DL threshold of other services[%] = 75DL LDR Trigger Threshold[%] = 70DL LDR Release Threshold[%] = 60Overload Congestion -> Overload Congestion ControlMaxTxPower = 43 or 46 dBm Basic Congestion-> LDRBasic Congestion-> LDR

Resource threshold : UL Power LoadUL OLC Triggering threshold[%] = 95%UL total power threshold[%] = 83UL handover access threshold[%] = 80UL threshold of Conv AMR service[%] = 75UL threshold of Conv non_AMR service[%] = 75UL threshold of other services[%] = 60UL LDR Trigger Threshold[%] = 55UL LDR Release Threshold[%] = 45Overload Congestion -> Overload Congestion ControlBackgroundNoise = -106 (Algorithm1)Basic Congestion-> LDRBasic Congestion-> LDRUlTotalEqUserNum = 80 (case Algorithm2)UL OLC Release threshold[%] = 85%

Resource Threshold : DL OVSF CodeFor RRC connection setup request, the admission accepted when code resource is sufficient for RRC Connection.For handover, the admission accepted when code resource is sufficient for the service.For other R99 service, the admission accepted when code resource after admit the service is less than HandOver Credit and Code Reserved SF.Dl HandOver Credit and Code Reserved SF = SF32For HSDPA service, there is no code resource admission.

Resource Threshold : Iub For handover of a user, the admission accepted when [load of the path] + [bandwidth required by user] < [Total configured bandwidth of the path]For a new user, the admission accepted when [load of the path] + [bandwidth required by user] < [Total configured bandwidth of the path] [bandwidth reserved for handover]For rate upsizing of a user, the admission accepted when [load of the path] + [bandwidth required by user] < [Total configured bandwidth of the path] [congestion threshold]Forward handover reserved bandwidth[KBIT/S] = 0Backward handover reserved bandwidth[KBIT/S] = 0Forward congestion threshold[KBIT/S] = 0Backward congestion threshold[KBIT/S] = 0Forward congestion clear threshold[KBIT/S] = 0Backward congestion clear threshold[KBIT/S] = 0

Resource Threshold : CE (UL/DL)For RRC connection setup request, the admission accepted when CE resource is sufficient for RRC Connection.For handover, the admission accepted when CE resource is sufficient for the service.For other service, the admission accepted when CE resource after admit the service is not less than Ul HandOver Credit Reserved SF/Dl HandOver Credit and Code Reserved SF.Ul HandOver Credit Reserved SF = SF16 (3 CE)Dl HandOver Credit and Code Reserved SF = SF32 (2 CE)

IubCodePowerCECapacity upgrade solutionIn 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/downgradeUL/DL CE upgrade/downgradeIncrease UL ENU (if RTWP is normal)Increase total RRU power Reduce CPICH powerReduce fix HS-PDSCH code, if code congest from VoiceIncrease fix HS-PDSCH code, if low throughput on HSPDAIncrease Iub bandwidth

Note : Capacity upgrade in term of optimization would be taken into account better in cell level. The optimizer should control coverage and parameter e.g. handover in order to balance between coverage and capacity of itself and surrounding cells.

WBBP and CE License up/down gradeResource unitWBBP : 128 UL/DLCE License : 16 CE in UL or DL separatelyCE resource configurationTo configure and use CE resource at NodeB, it will be defined as BB Resource Group separately for UL and DLThe main concern about the BB Resource Group is If configure multi WBBP card into one UL BB Resource Group, CE is sum of CE from every WBBP cards.If configure multi WBBP card into one DL BB Resource Group, CE is CE of only one WBBP card.

128 UL/DL128 UL/DLOne DL BB Resource and UL BB Resource GroupUL CE = 256DL CE = 128

Recommendation in CE up/down gradeAdd/remove CE License on demand. The CE License is in 16 CE unit. Add or remove in term of 1 license (smallest unit) is recommended for highest efficiency.WBBP card should be utilized at full license prior to add WBBP.If UL CE is congestion at full license, adding new WBBP card is needed.If DL CE is congestion. Reconfigure congested sector to separated WBBP Card can solve the problem prior to add new WBBP

WBBP and CE License up/down grade128 UL/DL128 UL/DLUL CE = 256Sector1Sector2Sector3128 UL/DL128 UL/DLDL BB Resource Group 0DL BB Resource Group 1UL BB Resource Group 0DL CE = 128Sector1Sector2Sector3DL CE = 128UL CE = 256DL CE = 128DL BB Resource Group 0UL BB Resource Group 0

CE Configuration and License Information+++ BKA9042U 2010-09-15 09:45:13 O&M #190945%%LST BRD: SRN=0;%%RETCODE = 0 Succeed.

Board Configuration Information-------------------------------Cabinet No. Subrack No. Slot No. Configuration Status Board Type

Master 0 0 NO UnknownMaster 0 1 NO UnknownMaster 0 2 YES WBBP Master 0 3 YES WBBP Master 0 4 NO UnknownMaster 0 5 NO UnknownMaster 0 6 NO UnknownMaster 0 7 YES WMPT Master 0 16 YES UBF Master 0 18 NO UnknownMaster 0 19 YES UPEA (Number of results = 11)

--- ENDUsing NodeB LMT to view Main Cabinet Topology and get info number of WBBP cardOr using MML command LST BRDWBBP card* Slot 01 is not configured yet.

CE Configuration and License InformationUsing NodeB MML to list the BB Resource Group of DL/UL+++ BKA9042U 2010-09-15 09:58:33 O&M #191217%%LST DLGROUP:;%%RETCODE = 0 Succeed.

DL BB Resource Group Information-------------------------------- DL BB Resource Group No. = 0Cabinet No. of DL Process Unit 1 = MasterSubrack No. of DL Process Unit 1 = 0 Slot No. of DL Process Unit 1 = 3

DL BB Resource Group No. = 1Cabinet No. of DL Process Unit 1 = MasterSubrack No. of DL Process Unit 1 = 0 Slot No. of DL Process Unit 1 = 2

(Number of results = 2)

--- ENDLST DLGROUPLST ULGROUP+++ BKA9042U 2010-09-15 10:00:30 O&M #191359%%LST ULGROUP:;%%RETCODE = 0 Succeed.

UL BB Resource Group Information-------------------------------- UL BB Resource Group No. = 0Cabinet No. of UL Process Unit 1 = MasterSubrack No. of UL Process Unit 1 = 0 Slot No. of UL Process Unit 1 = 2Cabinet No. of UL Process Unit 2 = MasterSubrack No. of UL Process Unit 2 = 0 Slot No. of UL Process Unit 2 = 3

(Number of results = 1)

--- ENDDL Group is divided into 2 group while UL is set only 1 group

CE Configuration and License InformationUsing NodeB LMT to view the BB DL/UL Resource Group allocated to each Local CellLST LOCELL+++ BKA9042U 2010-09-15 10:04:32 O&M #191658%%LST LOCELL: MODE=ALLLOCALCELL;%%RETCODE = 0 Succeed.

Local Cell Configuration(Summary)---------------------------------Local Cell ID Cell ID Site No. Sector No. UL BB Resource Group No. DL BB Resource Group No. Local Cell Radius(m) Local Cell Inner Handover Radius(m) Two Tx Way

1 300 300 0 0 0 29000 0 No2 400 300 1 0 1 29000 0 No3 500 300 2 0 1 29000 0 No(Number of results = 3)

--- ENDAll Local Cells are using the same UL BB Resource GroupLocal Cell 1 is using DL BB Resource Group No. 0 while Local Cell 2 and 3 are sharing the DL BB Group No. 1

CE Configuration and License InformationUsing NodeB LMT to view UL/DL CE License. Not only WBBP Card configuration, CE License should be managed properlyDSP License+++ BKA9042U 2010-09-15 10:34:20 O&M #193826%%DSP LICENSE:;%%RETCODE = 0 Succeed.

NodeB License------------- Operator Index = 0xffff Operator Name = Shared Downlink Frequencies = Unlimited frequency License Status = Legal license Max Uplink CE = 256 Max Downlink CE = 256 Max Local Cell = 4 HSDPA Function = Yes Max HSDPA User = 100 HSDPA RRM Package1 = Yes Max HS-PDSCH Code Number = 45 MBMS Function = No HSUPA Function = Yes PA Sharing Function = No HSUPA TTI Function = Yes CCPIC Function = No DYNAMIC CE = Yes DYNAMIC Voltage = No 64QAM NUM = 4 MIMO NUM = 0Local Cell Number in 400(0.1dBm) = 0Local Cell Number in 418(0.1dBm) = 0Local Cell Number in 430(0.1dBm) = 4Local Cell Number in 448(0.1dBm) = 0Local Cell Number in 460(0.1dBm) = 4Local Cell Number in 478(0.1dBm) = 4Local Cell Number in 490(0.1dBm) = 0 Multi-Mode BTS TS = No Ethernet Syn = No IP Clock Function = Yes Multi-Mode BTS = No

Emergency NodeB License------------- Emergency License Set Status = Unset(Number of results = 1)

--- ENDCE License would be pool resource for all the BB Resource Groups

Power congestion solutionAs we have analyzed the root cause of power congestion whether UL (ENU) or DL (RRU power). The solution would be different up to the type of power congestion.Only limit power resource on UL is ENU, UL ENU can adjust ranging from 1 200The concern of increasing UL ENU is RTWP. Although, call admission is success but it may lead to voice quality and drop call problem to itself or other UEs.The performance after increasing UL ENU should be closely monitored.If power is congested due to DL powerIf coverage is not the issue of the cell, we can slightly reduce the CPICH power. 1 dB step adjust is recommended.If coverage is the main concern in the serving area, we can increase 1 dB step adjust is recommended.

Note : please try to keep the ratio of CPICH power vs Max Transmit Power of Cell at 10% this would help to easily maintain CPICH Ec/No of the HSDPA carrier.

DL OVSF Code Congestion SolutionAt the moment, code congestion would be caused by insufficient code for AMR and PS R99. However, PS DL R99 should be very low as most of DL PS RB is HSDPA. Thus, most of the service congestion due to code should be AMR.To overcome this problem, the reduction of fix HS-PDSCH code would be the best solution at the moment. The trade-off between AMR and HS-PDSCH code allocation is unavoidable according to limit of DL OVSF Code.1 SF16 of HS-PDSCH can convert to about 8 AMR (SF128). This would be equivalent to 1 TRX. Thus, the fix HS-PDSCH 1 code reduction step would recommend to avoid as much as possible impact to HSDPA throughput.12345678

Iub Congestion SolutionThe only available solution is to expand Iub bandwidth.Almost all of Iub is IP over MPLS, the bandwidth limit should be omitted.

**