3G Huawei
RAN Resource Monitoring and management
1
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 this
information 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.
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
Yes
Yes
Yes
Cell Level
-OVSF code
-UL power
-DL power
No
Yes
Yes
RAN Resource diagram
•DL total power/DL ENU
•RTWP/UL ENU
•OVSF Code (DCH/HS-PDSCH)
RRU
1
-CE card
-CE license
-HS-PDSCH code license
•DL total power/DL ENU
•RTWP/UL ENU
•OVSF Code (DCH/HS-PDSCH)
RRU
2
•DL total power/DL ENU
•RTWP/UL ENU
•OVSF Code (DCH/HS-PDSCH)
RRU
3
BBU
UL/DL Iub bandwidth
RNC
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
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
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.
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.
NodeB HSDPA Code License
Description
• 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.
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. One
is real load in term of RTWP, another one is equivalent load in
term of ENU.
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.
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.
Total resource usage module
Rejection
-CS user
-PS R99 User
-HSDPA User
-HSUPA User
Service
distribution
-Power
-OVSF code
-CE
-Iub
Resources
-Desire QoS
-Congestion
User
experience
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
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
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 it’s 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 or 36 dBm
•
Total Power
– MaxTxPower
– Default = 43 or 46 dBm according to license
By the way, CPICH power + common channel will consume around
20% of total cell power.
38
40
42
MaxTxPower44
dBm
34
PCPICH + Common
channel
36
PCPICH
32
30
38
40
42
44
MaxTxPower
dBm
34
36
PCPICH + Common channel
PCPICH
32
30
Average of VS.MeanTCP.NonHS
Average of VS.MeanTCP
Example : BKD0040U3
– MaxTxPower = 43 dBm
– MaxPCPICHPower = 33 dBm
VS.MaxTCP (R99+HSDPA)
VS.MeanTCP (R99+HSDPA)
VS.MaxTCP.NonHS (R99)
VS.MeanTCP.NonHS (R99)
We can monitor TCP usage from counter
–
–
–
–
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
– DL OLC trigger threshold[%] = 95
•
RRC CAC considers OLC Trigger Threshold for
admission
•
•
•
TCP Counter and monitoring
Average of VS.MaxTCP
Average of VS.MaxTCP.NonHS
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 DL
ENU we refer to these counters.
VS.RAC.UL.TotalTrfFactor
UL ENU
VS.RAC.DL.TotalTrfFactor
DL ENU
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
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
35
•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
30
25
20
15
10
5
0
Average of VS.RAC.DL.TotalTrfFactor
Average of VS.RAC.UL.TotalTrfFactor
• 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%
OVSF Code Allocation
• In general, OVSF Code is occupied by common channel and
for HSDPA (HS-SCCH and HS-PDSCH) as well as HSUPA. The
rest of the code will be able to use by traffic channel.
SF
PS
8
PS 384
16
PS128
32
PS 64
64
128
AMR
0
0
1
0
2
1
3
0
4
2
5
1
6
3
7
0
8
4
9
2
10
5
11
1
12
6
13
3
14
7
15
256
Channel type
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
CPICH
PCCPCH
AICH
PICH
SCCPCH1
SCCPCH1
SCCPCH1
SCCPCH1
HS-SCCH
HS-SCCH
HS-SCCH
HS-SCCH
HS-SCCH
HS-SCCH
HS-SCCH
HS-SCCH
E-AGCH
E-HICH/E-RGCH
E-HICH/E-RGCH
• Upon the reservation of HS-PDSCH code
parameter setting , it may occupy
between 5-10 codes. Therefore, the
total code left for traffic channel is
about (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
OVSF and CE Consumption for DL DCH
service
Rate (kbps)
SF
CE Consumption
3.4
256
1
13.6
128
1
8
16
128
1
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.
OVSF and CE Consumption for UL
DCH service
Rate (kbps)
SF
CE Consumption
3.4
256
1
13.6
64
1
8
16
64
1
64
1
32
32
1.5
64
16
3
128
8
5
144
8
5
256
4
10
384
4
10
OVSF and CE Consumption for
HSUPA
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
OVSF Code Usage
•
Example : BKD0040U3
300
Maximum 256 code is available for 1 cell
Free code for
traffic channel
250
200
Total 179 codes is occupied.
160 is reserved for HS-PDSCH
150
100
50
0
Average of VS.RAB.SFOccupy
•
•
•
Average of VS.RAB.SFOccupy.MAX
•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 HSPDSCH Code only.
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.
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.
Counter of RRC rejection due to lack
of resource
•
RRC Connection Setup Rejection due to lack of resource
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)
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)
Counter of PS RAB rejection due to
lack of resource for different service
• Number of Unsuccessful PS RAB Setups for Different
Services due to Congestion (Cell)
RRC Setup Congestion Monitor
Example : BKD0040U3
UL CE Usage
1.2
160
140
1
120
100
0.8
80
60
40
0.6
20
0
0.4
Sum of VS.LC.ULCreditAvailable.Shared
0.2
Sum of VS.LC.ULMax.LicenseGroup.Shared
Sum of VS.LC.ULMean.LicenseGroup.Shared
0
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
Found UL CE congestion associates with high UL
CE Usage
Note : When RRC Setup failure, RAB setup will not initiate.
Therefore RAB Setup congestion can not be seen.
CS RAB Congestion monitoring
Example : BKD0040U3
TCP
44
42
40
10
38
dBm
9
36
Congestion but
just quite small
8
7
6
34
32
30
5
4
Average of VS.MaxTCP.NonHS
Average of VS.MeanTCP.NonHS
3
2
35
1
30
0
25
UL ENU
20
15
Sum of VS.RAB.FailEstab.CS.DLIUBBand.Cong
Sum of VS.RAB.FailEstab.CS.ULIUBBand.Cong
Sum of VS.RAB.FailEstCs.Code.Cong
Sum of VS.RAB.FailEstCs.DLCE.Cong
Sum of VS.RAB.FailEstCs.Power.Cong
Sum of VS.RAB.FailEstCs.ULCE.Cong
10
5
0
Average of VS.RAC.DL.TotalTrfFactor
•
•
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
Average of VS.RAC.UL.TotalTrfFactor
LOW ~ 25 ENUs
UL and DL CE Usage Monitoring
Example : BKD0040U3
DL CE Usage
120
100
80
60
40
20
0
Sum of VS.LC.DLCreditAvailable.Shared
Sum of VS.LC.DLMax.LicenseGroup.Shared
Sum of VS.LC.DLMean.LicenseGroup.Shared
UL CE Usage
160
140
120
100
80
60
40
20
0
Sum of VS.LC.ULCreditAvailable.Shared
Sum of VS.LC.ULMean.LicenseGroup.Shared
Sum of VS.LC.ULMax.LicenseGroup.Shared
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.
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 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-RAB
• The 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 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).
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
Average no of HSDPA users
VS.HSUPA.UE.Mean.Cell
Average no of HSUPA users
VS.CellPCHUEs
Average no of users in CELL_PCH state
VS.CellDCHUEs
Average no of users in CELL_DCH state
VS.CellFACHUEs
Average no of users in CELL_FACH state
 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 <= VS.CellDCHUEs
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 =
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
•
UL/DL CE consumption for a AMR User = 1/1
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 =
VS.HSUPA.UE.Mean.Cell
•
A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH
•
UL CE consumes up to bit rate of HSUPA
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 =
VS.HSDPA.UE.Mean - VS.HSUPA.UE.Mean.Cell
•
A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH
•
UL CE consumes up to bit rate of DCH
DL+UL PS R99 user number counter
in 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 =
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.DLStrP
S.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
•
DL CE consumes up to bit rate of DL DCH
•
UL CE consumes up to bit rate of UL DCH
Resource threshold : DL Power Load
Overload Congestion -> Overload Congestion Control
PS R99 RAB Service reject
AMR RAB reject
RRC
reject
All RAB service
reject
Handover reject
MaxTxPower = 43 or 46 dBm
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
Basic Congestion-> LDR
Basic Congestion-> LDR
Resource threshold : UL Power Load
Overload Congestion -> Overload Congestion Control
PS R99 RAB Service reject
AMR RAB reject
RRC
reject
All RAB service
reject
Handover reject
UlTotalEqUserNum = 80 (case Algorithm2)
UL OLC Triggering threshold[%] = 95%
UL OLC Release threshold[%] = 85%
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
BackgroundNoise = -106 (Algorithm1)
Basic Congestion-> LDR
Basic Congestion-> LDR
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.
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
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)
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
CE
Power
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.
Code
Iub
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.
One DL BB
Resource
and UL BB
Resource
Group
128 UL/DL
128 UL/DL
UL CE = 256
DL CE = 128
WBBP and CE License up/down grade
•
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
Sector1
DL BB Resource
Group 0
UL BB Resource
Group 0
128 UL/DL
128 UL/DL
UL CE = 256
Sector2
DL CE = 128
Sector3
DL BB Resource
Group 0
DL BB Resource
Group 1
UL BB Resource
Group 0
Sector1
128 UL/DL
128 UL/DL
DL CE = 128
UL CE = 256
Sector2
Sector3
DL CE = 128
CE Configuration and License Information
Using NodeB LMT to view Main Cabinet Topology and get info number of WBBP card
WBBP card
* Slot 01 is not
configured yet.
Or using MML command LST BRD
+++
BKA9042U
O&M
#190945
%%LST BRD: SRN=0;%%
RETCODE = 0 Succeed.
2010-09-15 09:45:13
Board Configuration Information
------------------------------Cabinet No. Subrack No. Slot No.
Master
0
Master
0
Master
0
Master
0
Master
0
Master
0
Master
0
Master
0
Master
0
Master
0
Master
0
(Number of results = 11)
---
END
0
1
2
3
4
5
6
7
16
18
19
Configuration Status
Board Type
NO
NO
YES
YES
NO
NO
NO
YES
YES
NO
YES
Unknown
Unknown
WBBP
WBBP
Unknown
Unknown
Unknown
WMPT
UBF
Unknown
UPEA
CE Configuration and License Information
Using NodeB MML to list the BB Resource Group of DL/UL
LST ULGROUP
LST DLGROUP
+++
BKA9042U
O&M
#191217
%%LST DLGROUP:;%%
RETCODE = 0 Succeed.
2010-09-15 09:58:33
DL BB Resource Group Information
-------------------------------DL BB Resource Group No.
Cabinet No. of DL Process Unit 1
Subrack No. of DL Process Unit 1
Slot No. of DL Process Unit 1
=
=
=
=
0
Master
0
3
DL BB Resource Group No.
Cabinet No. of DL Process Unit 1
Subrack No. of DL Process Unit 1
Slot No. of DL Process Unit 1
=
=
=
=
1
Master
0
2
(Number of results = 2)
---
+++
BKA9042U
O&M
#191359
%%LST ULGROUP:;%%
RETCODE = 0 Succeed.
2010-09-15 10:00:30
UL BB Resource Group Information
-------------------------------UL BB Resource Group No.
Cabinet No. of UL Process Unit 1
Subrack No. of UL Process Unit 1
Slot No. of UL Process Unit 1
Cabinet No. of UL Process Unit 2
Subrack No. of UL Process Unit 2
Slot No. of UL Process Unit 2
(Number of results = 1)
---
END
END
DL Group is divided into 2 group while UL is set only 1 group
=
=
=
=
=
=
=
0
Master
0
2
Master
0
3
CE Configuration and License Information
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;%%
RETCODE = 0 Succeed.
Local Cell Configuration(Summary)
--------------------------------Local Cell ID
Cell ID
Site No.
1
300
2
400
3
500
(Number of results = 3)
---
•
•
300
300
300
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
0
1
2
0
0
0
0
1
1
29000
29000
29000
0
0
0
No
No
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 are
sharing the DL BB Group No. 1
CE Configuration and License Information
Using NodeB LMT to view UL/DL CE License. Not only WBBP Card configuration, CE License
should be managed properly
DSP License
+++
BKA9042U
O&M
#193826
%%DSP LICENSE:;%%
RETCODE = 0 Succeed.
2010-09-15 10:34:20
NodeB License
-------------
Local
Local
Local
Local
Local
Local
Local
Operator Index
Operator Name
Downlink Frequencies
License Status
Max Uplink CE
Max Downlink CE
Max Local Cell
HSDPA Function
Max HSDPA User
HSDPA RRM Package1
Max HS-PDSCH Code Number
MBMS Function
HSUPA Function
PA Sharing Function
HSUPA TTI Function
CCPIC Function
DYNAMIC CE
DYNAMIC Voltage
64QAM NUM
MIMO NUM
Cell Number in 400(0.1dBm)
Cell Number in 418(0.1dBm)
Cell Number in 430(0.1dBm)
Cell Number in 448(0.1dBm)
Cell Number in 460(0.1dBm)
Cell Number in 478(0.1dBm)
Cell Number in 490(0.1dBm)
Multi-Mode BTS TS
Ethernet Syn
IP Clock Function
Multi-Mode BTS
Emergency NodeB License
------------Emergency License Set Status
(Number of results = 1)
---
END
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
0xffff
Shared
Unlimited frequency
Legal license
256
256
4
Yes
100
Yes
45
No
Yes
No
Yes
No
Yes
No
4
0
0
0
4
0
4
4
0
No
No
Yes
No
=
Unset
CE License would be
pool resource for all
the BB Resource
Groups
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 of
the HSDPA carrier.
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 recommend
to avoid as much as possible impact to HSDPA throughput.
1 HS-PDSCH
(SF16)
AMR
(SF128)
1
AMR
(SF128)
2
AMR
(SF128)
3
AMR
(SF128)
4
AMR
(SF128)
5
AMR
(SF128)
6
AMR
(SF128)
AMR
(SF128)
7
8
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.