122403687 3g huawei ran resource monitoring and management libre

8/9/2019 122403687 3G Huawei RAN Resource Monitoring and Management Libre

1/53

1

3G HuaweiRAN Resource Monitoring and management


2/53


3/53

Resources and configuration

• In Huawei WCDMA network, to avoid the congestion and blockageof the service, we have to monitor the following resources :

NE Type Resource Expansible

NodeB Level -CE card and license-NodeB HS-PDSCH code license-UL and DL Iub bandwidth

YesYesYes

Cell Level -OVSF code-UL power-DL power

NoYesYes


4/53

RAN Resource diagram

BBU

RRU1

RNC RRU2

RRU3

•DL total power/DL ENU•RTWP/UL ENU•OVSF Code (DCH/HS-PDSCH)

•DL total power/DL ENU•RTWP/UL ENU•OVSF Code (DCH/HS-PDSCH)

•DL total power/DL ENU

•RTWP/UL ENU

•OVSF Code (DCH/HS-PDSCH)

-CE card-CE license

-HS-PDSCH code license

UL/DL Iub bandwidth


5/53

Traffic and KPI statistic

• To associate the actual situation of resource usage we haveto consider in term of :

- CS and PS traffic- Congestion- Utilization


6/53

Service distribution

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

– AMR

– VP – PS R99 DL – PS R99 UL – HSDPA – HSUPA


7/53

CE Resource Description

• CE resource is consisting of hardware and software. CE isthe pool resource at NodeB level, all cells connected to NodeBwill share the same CE resource.

– Hardware• Number 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.

– Software• 1 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.


8/53

OVSF Code Resource Description

OVSF Code is the limit resource of each cell. The expansioncan’t be possible in a single cell. OVSF Code will be limited onlyDL 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 HSDPAis less OVSF code left for R99.


9/53

NodeB HSDPA Code LicenseDescription

• Except the available number of free OVSF code, HSDPA isrequired 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.


10/53

UL Power Resource Description

• Even the UL power is not limit corresponding to each UEpower, but the noise raise will trig the rejection due to CallAdmission Control as well. Hence, the increment in UL load cancause service rejection and slow down the data service.

• For Huawei, UL power resource can divided into 2 type. Oneis real load in term of RTWP, another one is equivalent load interm of ENU.


11/53

DL Power Resource Description

• DL Power Limit is considered at RRU total power. Typical useof RRU power in Truemove is 20 and 40 watt.

• In general, the common control channel will consume about20% of total power.

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

• HSDPA will use the remaining power left from R99 service.


12/53

UL and DL Iub Bandwidth Description

• Iub is the pool resource at BBU, each RRU have to sharesame Iub resource.

• Typical configuration bandwidth of Iub is 10 and 20 Mbps.

• Truemove deploys IP based Iub transmission.


13/53

Total resource usage module

-Power-OVSF code-CE-Iub

-Desire QoS

-Congestion

-CS user-PS R99 User

-HSDPA User-HSUPA User

Servicedistribution

Resources Userexperience

Rejection

2 states of service interruption• The user can’t get the ser ice rejection . • The user can’t get at the desire QoS lo throughput of data ser ice


14/53

Power CAC Algorithm

• Power CAC is applied on both DL and UL

• We have to consider our selected algorithm. The monitoring method will bedifferent. 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


15/53

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 andperformance. Although it’s the same RRU power, it may different in thecapacity because of UE distribution in a cell. To overview the power settingin a cell, we can check parameter setting of total power and CPICH power.

• CPICH Power

– MaxPCPICHPower (~ 10% of total cell power) – Default = 33 or 36 dBm• Total Power

– MaxTxPower – Default = 43 or 46 dBm according to license

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

MMP P


16/53

T C P

C

o un

t er

an d m

oni

t or i

•

E x am

pl e: B K D

0 0 4

–

M ax T x P ow

er

–

M ax P C P I C H P

•

W e c anm

oni t or T C

–

V S .M

ax T C P (R

–

V S .M

e anT C P

–

V S .M

ax T C P .N

–

V S .M

e anT C P

•

W e c h e c k p ar am et

–

D L

t h r e s h ol d o

8 0

–

D L

t h r e s h ol d o

= 8 0

–

D L

t h r e s h ol d o

–

D L h an d ov er a

–

D L

t o t al p ow e

•

R R

C C A

C

c on s i d e

a d mi s s i on–

D L

O

L C t r i g ge

3 0 3 2 3 4 3 6 3 8 4 0 4 2 4 4

d B m

A v e r a g e o f V S . M a x T C P

A v e r a g e o f V S . M e a n T C P

3 0

3 2 3 4 3 6 3 8 4 0 4 2 4 4

d B m

A v e r a g e o f V S . M a x T C P . N o n H S

A v e r a g e o f V S . M e a n T C P . N o n H S

M a x T x P o w e r

P C P I C H

M a x T x P o w e r

P C P I C H

P C P I C H +

C o m m o n c h a n n e l

P C P I C H +

C o m m o n c h a n n e l


17/53


18/53

Typical equivalent number of users (ENU)

Sevice ENU DCH uplink DCH downlink HSDPA HSUPA

3.4 kbps SIG 0.44 0.42 0.28 1.76

13.6 kbps SIG 1.11 1.11 0.74 1.89

3.4 + 12.2 kbps 1.44 1.42 - -

3.4 + 8 kbps (PS) 1.35 1.04 0.78 2.26

3.4 + 16 kbps (PS) 1.62 1.25 1.11 2.37

3.4 + 32 kbps (PS) 2.15 2.19 1.70 2.60

3.4 + 64 kbps (PS) 3.45 3.25 2.79 3.14

3.4 + 128 kbps (PS) 5.78 5.93 4.92 4.67

3.4 + 144 kbps (PS) 6.41 6.61 5.46 4.87

3.4 + 256 kbps (PS) 10.18 10.49 9.36 6.61

3.4 + 384 kbps (PS) 14.27 15.52 14.17 9.36


19/53

UL ENU counter and monitoring

• Take a look at parameter setting of maximum allowedequivalent 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

0

5

10

15

20

25

30

35

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


20/53

OVSF Code Allocation

• In general, OVSF Code is occupied by common channel andfor HSDPA (HS-SCCH and HS-PDSCH) as well as HSUPA. Therest of the code will be able to use by traffic channel.

• Upon the reservation of HS-PDSCH codeparameter setting , it may occupybetween 5-10 codes. Therefore, thetotal code left for traffic channel isabout (normalize at SF256) :256 – (19+SF256 of HS-PDSCH(5,10)) =

157 – 77 codes at SF256

• OVSF code usage counter- VS.RAB.SFOccupy- VS.RAB.SFOccupy.MAX

SF 8 16 32 64 128 256

PS PS 384 PS128 PS 64 AMR Channel type0 CPICH

1 PCCPCH

2 AICH3 PICH

4 SCCPCH1

5 SCCPCH1

6 SCCPCH17 SCCPCH1

8 HS-SCCH

9 HS-SCCH

10 HS-SCCH11 HS-SCCH

12 HS-SCCH

13 HS-SCCH14 HS-SCCH15 HS-SCCH

16 E-AGCH

1718 E-HICH/E-RGCH19 E-HICH/E-RGCH

202122232425262728293031

0

14

15

8

9

10

11

12

13

0

1

2

3

4

5

6

7

0

1

2

3

4

5

6

7

0

1

2

3

0

1


21/53

OVSF and CE Consumption for DL DCHservice

Rate (kbps)

SF

CE Consumption

3.4 256 1

13.6 128 1

8 128 1

16

128

1

32 64 1

64 32 2

128 16 4

144 16 4

256 8 8

384 8 8

Note : Even HS-PDSCH will not utilize DL CE but A HSDPA User will

consume 1*SF256 (1 CE) in DL for A-DCH.


22/53

OVSF and CE Consumption for ULDCH service

Rate (kbps)

SF

CE Consumption

3.4 256 1

13.6 64 1

8 64 1

16

64

1

32 32 1.5

64 16 3

128 8 5

144 8 5

256 4 10

384 4 10


23/53


24/53

0

50

100

150

200

250

300

Average of VS.RAB.SFOccupy Average of VS.RAB.SFOccupy.MAX

OVSF Code Usage

• Example : BKD0040U3

•Check parameter setting

•LST CELLHSDPA•Allocate Code Mode = MANUAL•Code Number for HS-PDSCH = 10•By method of reservation byMANUAL then total 10*SF16 = 160SF256 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 trafficchannel.

• 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 fortraffic channel


25/53

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 willreject the service.

• The rejection may occur at RRC or RAB setup state. RRC is morecritical than RAB rejection as RRC CAC threshold (typical 95% load) ishigher than RAB CAC threshold.

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


26/53

Counter of RRC rejection due to lackof resource

• RRC Connection Setup Rejection due to lack of resource


27/53

Counter of CS RAB rejection due tolack of resource

• Number of CS RAB Unsuccessfully Established due toRadio Resource Congestion (Cell)

• Number of CS RAB Unsuccessfully Established due toIub Bandwidth Congestion (Cell)


28/53

Counter of PS RAB rejection due tolack of resource

• Number of PS RABs Unsuccessfully Established due toRadio Resource Congestion (Cell)

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


29/53

Counter of PS RAB rejection due tolack of resource for different service

• Number of Unsuccessful PS RAB Setups for Different

Services due to Congestion (Cell)


30/53


31/53

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 thatpower congestion should come from DL

0

1

2

3

4

5

6

7

8

9

10

Sum of VS.RAB.FailEstab.CS.DLIUBBand.Cong Sum of VS.RAB.Fail Estab.CS.ULIUBBand.Cong

Su m o f VS.RAB.Fa i lEs tCs .Co de.Co ng Su m o f VS.RAB.Fa i lEs tCs .DLCE.Co ng

Sum of VS.RAB.Fai lEs tCs .Power.Cong Sum of VS.RAB.Fai lEs tCs.ULCE.Cong

Example : BKD0040U3

Congestion but just quite small

30

32

34

36

38

40

42

44

dBm

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

TCP

0

5

10

15

20

25

30

35

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

UL ENU

LOW ~ 25 ENUs


32/53

UL and DL CE Usage Monitoring

0

20

40

60

80

100

120

DL CE Usage

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

Sum of VS.LC.DLMean.Licens eGroup.Shared

0

20

40

60

80

100

120

140

160

UL CE Usage

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

Sum of VS.LC.ULMean.LicenseGroup.Shared

Example : BKD0040U3

As PS RAB congestion hasbeen found in cause UL CEcongestion. From CE usagemonitoring we can see

sometimes the maximumusage touches all availableCE.


33/53

Observe the type of service

• Except the resource usage and rejection, to realize the resourceconsumption of the cell, we have to figure out the load of each serviceof a cell to see the distribution and judge which one consumes load themost.

• The service of a single user may be single-RAB or Multi-RAB

• The service of a single user will consume balance or unbalanceload between UL and DL e.g.

– AMR user : UL CS AMR and DL CS AMR – Old Model mobile : DL+UL PS R99 – iPhone and BB user : UL PS R99 and DL HSDPA – Datacard user : UL HSUPA and DL HSDPA (all the equipment support

HSUPA will support HSDPA).


34/53


35/53

AMR user number counter in a cell

• At the moment AMR user will utilize DL SF128/UL SF64 foreach RL.

• To sum up the number of AMR user we can calculate from

Number of AMR users =

• UL/DL CE consumption for a AMR User = 1/1

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


36/53

HSDPA+HSUPA user number counter in a cell

•Assume that HSUPA user is HSDPA user as well. Hencewhile UL is HSUPA, DL will be HSDPA.

Number of HSDPA+HSUPA Users =

• A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH

• UL CE consumes up to bit rate of HSUPA

VS.HSUPA.UE.Mean.Cell


37/53

HSDPA+R99 user number counter in a cell

• Typical mobile in a market will support only HSDPA whileusing R99 in UL. Therefore,

Number of HSDPA+R99 User =

• A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH

• UL CE consumes up to bit rate of DCH

VS.HSDPA.UE.Mean - VS.HSUPA.UE.Mean.Cell

DL UL PS R99 b


38/53

DL+UL PS R99 user number counterin a cell

• Assume that if the UE model supports only DL R99, thenumber of DL+UL R99 is equal to number of DL R99 User

Number of DL+UL R99 User =

• DL CE consumes up to bit rate of DL DCH

• UL 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


39/53

Resource threshold : DL Power Load

DL OLC Triggering threshold[%] = 95

DL total power threshold[%] = 90

DL handover access threshold[%] = 85UL OLC Release threshold[%] = 85

DL threshold of Conv AMR service[%] = 80DL 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

A l l R A B s e r v i c e

r e j e c t

H a n

d o v e r r e j e c t

P S R 9 9 R A B S e r v i c e r e j e c t

A M R R A B r e j e c t

R R C

r e j e c t

Basic Congestion-> LDR Basic Congestion-> LDR


40/53

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[%] = 75UL 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

BackgroundNoise = -106 (Algorithm1)

R R C

r e j e c t

Basic Congestion-> LDR Basic Congestion-> LDR

UlTotalEqUserNum = 80 (case Algorithm2)

A l l R A B s e r v i c e

r e j e c t

H a n

d o v e r r e j e c t

P S R 9 9 R A B S e r v i c e r e j e c t

A M R R A B r e j e c t

UL OLC Release threshold[%] = 85%


41/53

Resource Threshold : DL OVSF Code

• For RRC connection setup request, the admission acceptedwhen code resource is sufficient for RRC Connection .

• For handover, the admission accepted when code resourceis sufficient for the service .

• For other R99 service, the admission accepted when coderesource after admit the service is less than HandOver Creditand Code Reserved SF .

• Dl HandOver Credit and Code Reserved SF = SF32

• For HSDPA service, there is no code resourceadmission.


42/53

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] = 0

• Backward handover reserved bandwidth[KBIT/S] = 0

• Forward congestion threshold[KBIT/S] = 0

• Backward congestion threshold[KBIT/S] = 0• Forward congestion clear threshold[KBIT/S] = 0

• Backward congestion clear threshold[KBIT/S] = 0


43/53

Resource Threshold : CE (UL/DL)

• For RRC connection setup request, the admission acceptedwhen CE resource is sufficient for RRC Connection .

• For handover, the admission accepted when CE resource issufficient for the service .

• For other service, the admission accepted when CE resourceafter admit the service is not less than Ul HandOver CreditReserved 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)


44/53

Iub

Code

Power

CE

Capacity upgrade solution

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

1. WBBP upgrade/downgrade

2. UL/DL CE upgrade/downgrade

3. Increase UL ENU (if RTWP is normal)

4. Increase total RRU power

5. Reduce CPICH power

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

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

8. Increase Iub bandwidth

Note : Capacity upgrade in term of optimization would be taken into accountbetter 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.


45/53


46/53


47/53

CE Configuration and License Information

+++ BKA9042U 2010-09-15 09:45:13O&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 WBBPMaster 0 3 YES WBBPMaster 0 4 NO UnknownMaster 0 5 NO UnknownMaster 0 6 NO UnknownMaster 0 7 YES WMPTMaster 0 16 YES UBFMaster 0 18 NO UnknownMaster 0 19 YES UPEA(Number of results = 11)

--- END

Using NodeB LMT to view Main Cabinet Topology and get info number of WBBP card

Or using MML command LST BRD

WBBP card* Slot 01 is notconfigured yet.


48/53

CE Configuration and License Information Using NodeB MML to list the BB Resource Group of DL/UL

+++ BKA9042U 2010-09-15 09:58:33O&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)

--- END

LST DLGROUP LST ULGROUP

+++ BKA9042U 2010-09-15 10:00:30O&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


--- END

DL Group is divided into 2 group while UL is set only 1 group


49/53


Using NodeB LMT to view the BB DL/UL Resource Group allocated to each Local Cell

LST LOCELL

+++ BKA9042U 2010-09-15 10:04:32O&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)

--- END

• All Local Cells are using the same UL BB Resource Group

• Local Cell 1 is using DL BB Resource Group No. 0 while Local Cell 2 and 3 aresharing the DL BB Group No. 1


50/53


Using NodeB LMT to view UL/DL CE License. Not only WBBP Card configuration, CE Licenseshould be managed properly

DSP License +++ BKA9042U 2010-09-15 10:34:20O&M #193826%%DSP LICENSE:;%%RETCODE = 0 Succeed.

NodeB License-------------

Operator Index = 0xffffOperator Name = Shared

Downlink Frequencies = Unlimited frequencyLicense Status = Legal license

Max Uplink CE = 256

Max Downlink CE = 256Max Local Cell = 4HSDPA Function = YesMax HSDPA User = 100

HSDPA RRM Package1 = YesMax HS-PDSCH Code Number = 45

MBMS Function = NoHSUPA Function = Yes

PA Sharing Function = NoHSUPA TTI Function = Yes

CCPIC Function = NoDYNAMIC CE = Yes

DYNAMIC Voltage = No64QAM NUM = 4

MIMO NUM = 0

Local 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 = NoEthernet Syn = No

IP Clock Function = YesMulti-Mode BTS = No

Emergency NodeB License-------------

Emergency License Set Status = Unset


--- END

CE License would bepool resource for allthe BB ResourceGroups


51/53

Power congestion solution

• As 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 – 200

– The concern of increasing UL ENU is RTWP. Although, call admission is success but it maylead 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 power

– If coverage is not the issue of the cell, we can slightly reduce the CPICH power. 1 dB stepadjust is recommended.

– If coverage is the main concern in the serving area, we can increase 1 dB step adjust isrecommended.

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


52/53

DL OVSF Code Congestion Solution

• At the moment, code congestion would be caused by insufficient code for AMR andPS 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 bestsolution at the moment. The trade-off between AMR and HS-PDSCH code allocation isunavoidable 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 recommendto avoid as much as possible impact to HSDPA throughput.

1 HS-PDSCH(SF16)

AMR(SF128)

AMR(SF128)

AMR(SF128)

AMR(SF128)

AMR(SF128)

AMR(SF128)

AMR(SF128)

AMR(SF128)

1

2

3

4

5

6

7

8

b C i S l i


53/53

Iub Congestion Solution

• The only available solution is to expand Iub bandwidth.

• Almost all of Iub is IP over MPLS, the bandwidth limit should be omitted.

122403687 3g huawei ran resource monitoring and management libre

Documents