3g_huawei_ran_resource_monitoring_and_ma.pdf

8/17/2019 3G_Huawei_RAN_Resource_Monitoring_and_ma.pdf

1/53

1

3G HuaweiRAN Resource Monitoring and management


2/53

Capacity and resource analysis

• To 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 thisinformation for the analysis. The information will be collected is :

– Actual resource and configuration

– Traffic and KPI statistic

– Service distribution• From these 3 components, we can create 3 dimensions

relationship and give the result of enough or inadequate

resources for desired service.


3/53

Resources and configuration

• In Huawei WCDMA network, to avoid the congestion and blockage

of 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

No

Yes

Yes


4/53

RAN Resource diagram

BBU

RRU1

RNC

RRU2

RRU

3

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

to consider in term of :

- CS and PS traffic

- Congestion

- Utilization


6/53

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


7/53

CE Resource Description

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

– 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 expansion

can’t 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.


9/53

NodeB HSDPA Code LicenseDescription

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


10/53

UL Power Resource Description

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


12/53

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.

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

experience

Rejection

2 states of service interruption

• The user can’t get the service (rejection).

• The user can’t get at the desire QoS (low throughput of data service)


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


15/53


16/53

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

30

32

34

36

38

40

42

44

dBm

Average of VS.MaxTCP Average of VS.MeanTCP

30

32

34

36

38

40

42

44

dBm

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

MaxTxPower

PCPICH

MaxTxPower

PCPICH

PCPICH + Common channel

PCPICH + Common channel


17/53

Oversee cell load by ENU

• Equivalent 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 DLENU we refer to these counters.

VS.RAC.UL.TotalTrfFactor

VS.RAC.DL.TotalTrfFactor

UL ENU

DL ENU


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 allowed

equivalent user number

– UL total equivalent user number = 80 (by default)


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

0 CPICH

1 PCCPCH

2 AICH

3 PICH

4 SCCPCH1

5 SCCPCH1

6 SCCPCH1

7 SCCPCH1

8 HS-SCCH

9 HS-SCCH

10 HS-SCCH

11 HS-SCCH

12 HS-SCCH

13 HS-SCCH

14 HS-SCCH

15 HS-SCCH

16 E-AGCH

17

18 E-HICH/E-RGCH

19 E-HICH/E-RGCH

20

21

22

23

24

25

26

27

28

29

30

31

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

OVSF and CE Consumption forHSUPA

Rate (kbps) SF CE Consumption

8 256 1

16 64 1

32 64 1.5

64 64 1.5

128

32

3

144 8 3

256 4 5

384 4 10

608 4 10

1450 2SF2 32

2048 2SF2 32

2890 2SF2+2SF4 48

5760

2SF2+2SF4

48


24/53

0

50

100

150

200

250

300

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

OVSF Code Usage


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


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 to

Radio Resource Congestion (Cell)

• Number of CS RAB Unsuccessfully Established due to

Iub Bandwidth Congestion (Cell)


28/53

C f PS RAB j i d


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

Found UL CE congestion associates with high ULCE Usage

RRC Setup Congestion Monitor

0

0.2

0.4

0.6

0.8

1

1.2

Sum of VS.RRC.Rej.DLIUBBandCong Sum of VS.RRC.Rej.DL.CE.Cong

Sum of VS.RRC.Rej.Power.Cong Sum of VS.RRC.Rej.ULIUBBandCong

Sum of VS.RRC.Rej.UL.CE.Cong Sum of VS.RRC.Rej.Code.Cong

Example : BKD0040U3

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

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


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 that

power 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 .Cod e.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 CE

congestion. From CE usage

monitoring 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 resource

consumption 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 the

most.

• 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

User number counter in a cell

• We can roughly discover the number of users to imply the

traffic density in a cell.

VS.HSDPA.UE.Mean.Cell

VS.HSUPA.UE.Mean.Cell

VS.CellPCHUEs

VS.CellDCHUEs

VS.CellFACHUEs

Typically, VS.HSUPA.UE.Mean.Cell is the subset of VS.HSDPA.UE.Mean.Cell

as UE which supports HSUPA shall support HSDPA.

VS.HSDPA.UE.Mean.Cell


35/53

AMR user number counter in a cell

• At the moment AMR user will utilize DL SF128/UL SF64 for

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

using 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 user number counter


38/53

DL+UL PS R99 user number counterin a cell

• Assume that if the UE model supports only DL R99, the

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

6+VS.RB.DLInterPS.32+VS.RB.DLInterPS.64+VS.RB.DLInterPS.128+VS.RB.DLInterPS.1

44+VS.RB.DLInterPS.256+VS.RB.DLInterPS.384+VS.RB.DLBkgPS.8

VS.RB.DLBkgPS.16+VS.RB.DLBkgPS.32+VS.RB.DLBkgPS.64+VS.RB.DLBkgPS.128+VS.R

B.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[%] = 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

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 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 = SF32

• For HSDPA service, there is no code resource

admission.


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


44/53

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)

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 : Capaci ty upg rade in term of op t imizat ion w ould b e taken into accou nt

better in cel l level. The optim izer shou ld co ntro l cov erage and parameter e.g.

handover in order to b alance between cov erage and capaci ty of i tsel f and

surrounding cells .


45/53

WBBP and CE License up/down grade

• Resource unit

– WBBP : 128 UL/DL – CE License : 16 CE in UL or DL separately

• CE resource configuration

– To configure and use CE resource at NodeB, it will be defined as BB Resource

Group separately for UL and DL

– The 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/DL

128 UL/DL

One DL BBResource

and UL BB

ResourceGroup

UL CE = 256DL CE = 128


46/53

• Recommendation in CE up/down grade

– Add/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 grade

128 UL/DL

128 UL/DL

UL CE = 256

Sector1

Sector2

Sector3

128 UL/DL

128 UL/DL

DL BB Resource

Group 0

DL BB Resource

Group 1

UL BB ResourceGroup 0

DL CE = 128

Sector1

Sector2

Sector3

DL CE = 128

UL CE = 256

DL CE = 128

DL BB Resource

Group 0

UL BB ResourceGroup 0


47/53

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 Unknown

Master 0 2 YES WBBP

Master 0 3 YES WBBP

Master 0 4 NO Unknown



Master 0 7 YES WMPT

Master 0 16 YES UBF


Master 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


Using NodeB MML to list the BB Resource Group of DL/UL

+++ BKA9042U 2010-09-15 09:58:33

O&M #191217

%%LST DLGROUP:;%%


DL BB Resource Group Information

--------------------------------

DL BB Resource Group No. = 0

Cabinet No. of DL Process Unit 1 = Master

Subrack No. of DL Process Unit 1 = 0

Slot No. of DL Process Unit 1 = 3

DL BB Resource Group No. = 1

Cabinet No. of DL Process Unit 1 = Master

Subrack No. of DL Process Unit 1 = 0

Slot No. of DL Process Unit 1 = 2


--- END

LST DLGROUP

LST ULGROUP

+++ BKA9042U 2010-09-15 10:00:30

O&M #191359

%%LST ULGROUP:;%%


UL BB Resource Group Information

--------------------------------

UL BB Resource Group No. = 0

Cabinet No. of UL Process Unit 1 = Master

Subrack No. of UL Process Unit 1 = 0

Slot No. of UL Process Unit 1 = 2

Cabinet No. of UL Process Unit 2 = Master

Subrack No. of UL Process Unit 2 = 0

Slot No. of UL Process Unit 2 = 3


--- END

DL Group is div id ed into 2 group w hi le 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:32

O&M #191658

%%LST LOCELL: MODE=ALLLOCALCELL;%%


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 No

3 500 300 2 0 1 29000 0 No


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

CE C fi i d i I f i


50/53


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

DSP Lic ense

+++ BKA9042U 2010-09-15 10:34:20

O&M #193826

%%DSP LICENSE:;%%


NodeB License

-------------

Operator Index = 0xffff

Operator Name = Shared

Downlink Frequencies = Unlimited frequency

License Status = Legal license

Max Uplink CE = 256

Max Downlink CE = 256Max 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 = 0

Local Cell Number in 400(0.1dBm) = 0Local Cell Number in 418(0.1dBm) = 0

Local Cell Number in 430(0.1dBm) = 4





Multi-Mode BTS TS = No

Ethernet Syn = No

IP Clock Function = Yes

Multi-Mode BTS = No

Emergency NodeB License

-------------

Emergency License Set Status = Unset


--- END

CE License would be

pool resource for all

the BB ResourceGroups

P ti l ti


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

– If 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 ofthe HSDPA carrier.

DLOVSFC d C ti S l ti


52/53

DL OVSF Code Congestion Solution

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

I b C ti S l ti


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.

3g_huawei_ran_resource_monitoring_and_ma.pdf

Documents