RAN14 3G Capacity Monitoring

Security Level:
RAN14
3G Capacity monitoring
www.huawei.com
HUAWEI
CO.,LTD.
LTD.
HUAWEI TECHNOLOGIES
TECHNOLOGIES CO.,
Huawei Confidential
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HUAWEI TECHNOLOGIES CO., LTD.
HSDPA User
Page 2
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HSDPA User
Page 3
RTWP
Counter:
VS.MeanRTWP: average RTWP in a cell
VS.MinRTWP: minimum RTWP in a cell
VS.RRC.Rej.ULPower.Cong: number of RRC Connection Rejects for Cell (UL
Power Congestion)
VS.RAB.FailEstabCS.ULPower.Cong: number of Failed CS RAB Establishments for
Cell (UL Power Congestion)
VS.RAB.FailEstabPS.ULPower.Cong: number of Failed PS RAB Establishments for
Cell (UL Power Congestion)
Page 4
RTWP
Optimization Suggestions
If the value of the VS.MinRTWP counter is greater than -100 dBm or less than -110 dBm
during free hours for three consecutive days in one week, hardware faults or external
interference exists. Locate and rectify the faults.
If the value of the VS.MeanRTWP counter is greater than -90 dBm during peak hours for
three consecutive days in one week, there may be hardware faults or external
interference. Locate and rectify the faults.
If one of
VS.RRC.Rej.ULPower.Cong, VS.RAB.FailEstabCS.ULPower.Cong and
VS.RAB.FailEstabPS.ULPower.Cong is not 0, it is meaning Uplink power congestion
happens and need more resource.
Page 5
RTWP
Parameters Optimization
If RTWP is still very high after hardware faults and external interference are rectified,
implement below solutions:
Solution1: CQI feedback period optimization

Description:
The uplink feedback channel HS-DPCCH of HSDPA consume part of uplink load.
More and more HSDPA user online at the same time in the cell (> 20 users).
HSDPA uplink feedback channel contribute a big part of RTWP load.
It is recommended to optimize HSDPA CQI feedback period from 2ms to 8ms, to
reduce impact on uplink.
RNC Level SET UHSDPCCH:CQIFBCK=D8,CQIFBCKFORSHO=D8;
Cell Level ADD UCELLHSDPCCH: CELLID=xxx, CQIFbCk=D8,
CQIFbCkforSHO=D8;
Page 6
RTWP
Solution2: RACH access parameter optimization
Description:
RACH access preamble adopt open-loop power control
When the coverage is bad or massive RRC access exist => UE TX power could increase
quickly involving RTWP peaks. In order to control RTWP peaks, RACH access parameters
could be optimized.
Access Parameter
(default value)
Constantvalue (-20)
PreambleRetransMax (20)
PowerRampStep (2)
Mmax (8)
NB01max (0)
Optimized Value
-30
40
1
3
10
MOD UPRACHUUPARAS: CellId=xxx, PhyChId=4, Constantvalue=-30,

PowerRampStep=1, PreambleRetransMax=40;
Page 7
RTWP
If the uplink capacity of the cell still does not meet the requirements after parameters
optimization, add carriers as required. If there are no additional UARFCNs available, add
NodeBs as required.
Page 8
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HSDPA User
Page 9
TCP
Counter:
VS.MeanTCP: mean transmitted power of carrier for cell
VS.MeanTCP.NonHS: mean Non-HSDPA transmitted carrier power for cell
VS.RRC.Rej.DLPower.Cong: number of RRC Connection Rejects for Cell (DL
Power Congestion)
VS.RAB.FailEstabCS.DLPower.Cong: number of Failed CS RAB Establishments for
Cell (DL Power Congestion)
VS.RAB.FailEstabPS.DLPower.Cong: number of Failed PS RAB Establishments for
Cell (DL Power Congestion)
Page 10
TCP
Formula:
MeanNonHSTCP Utility Ratio = MeanNonHSTCP/MAXTXPOWER x 100%
MeanTCP Utility Ratio = MeanTCP/MAXTXPOWER x 100%
MeanNonHSTCP 10 (VS .MeanTCP. NonHS /10) / 1000

MeanTCP 10(VS .MeanTCP /10) / 1000
To obtain MAXTXPOWER, run the LST UCELL command, query the value of the
Max Transmit Power of Cell parameter, and convert the parameter value from the unit
"0.1 dBm" to "watt.
Page 11
TCP
Perform capacity expansion in the following scenarios:
The MeanNonHSTCP Utility Ratio is greater than 70% during peak hours for three
consecutive days in one week.
The MeanTCP Utility Ratio is greater than 85% during peak hours for three
consecutive days in one week.
If one of VS.RRC.Rej.DLPower.Cong, VS.RAB.FailEstabCS.DLPower.Cong and
VS.RAB.FailEstabPS.DLPower.Cong is not 0, need more resource.
The capacity expansion methods are as follows:
For cells with heavy traffic, add a carrier for the current sector if possible; add a
NodeB or split the sector if the number of carriers in the sector reaches the maximum.
For cells with light traffic and poor coverage, add a NodeB.
Page 12
TCP
Parameter Optimization
Solution1: Decrease Power Margin
Description:
Power Margin parameter is used to set the reserved power for R99 handover;
In the low handover factor scenario, decrease the threshold will increase available
load.
NODEB MML: SET MACHSPARA: PWRMGN=1; (Default Value 5)
Solution2:Increase CAC (Call Admission Control) Threshold
Description:
If cell load is high with some congestion, and if there is no other resources
congestion : Increasing downlink CAC threshold of 5% (from 80% to 85%) to decrease
the congestion temporarily
If the DL load of a cell is higher than this threshold => this service will be rejected
RNC MML: MOD UCELLCAC: CellID=xxxx, DlConvAMRThd=85,
DlConvNonAMRThd=85, DlOtherThd=80, DlHOThd=90, DlCellTotalThd=95;
Page 13
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HSDPA User
Page 14
Code
Counter:
VS.RAB.SFOccupy: mean Number of SFs that Have Been Occupied (Let the SFs
that Have Been Occupied a Unitary SF of 256) for Cell
VS.RRC.Rej.Code.Cong: number of RRC Connection Rejects for Cell (Code
Resource Congestion)
VS.RAB.FailEstabCS.Code.Cong: number of Failed CS RAB Establishments for
Cell (Code Congestion)
VS.RAB.FailEstabPS.Code.Cong: number of Failed CS RAB Establishments for
Cell (Code Congestion)
Page 15
Code
The codes available for the DCH can be calculated using the following
formula:
DCH_OVSF_CODE = (<VS.SingleRAB.SF4> + <VS.MultRAB.SF4>) * 64 +
(<VS.MultRAB.SF8> + <VS.SingleRAB.SF8>) * 32 + (<VS.MultRAB.SF16> +
<VS.SingleRAB.SF16>) * 16 + (<VS.SingleRAB.SF32> + <VS.MultRAB.SF32>) * 8 +
(<VS.MultRAB.SF64> + <VS.SingleRAB.SF64>) * 4 + (<VS.SingleRAB.SF128> +
<VS.MultRAB.SF128>) * 2 + (<VS.SingleRAB.SF256> + <VS.MultRAB.SF256>)
The maximum number of codes available for the DCH can be

calculated using the following formula:
DCH_OVSF_CODE_Ava = 256 - (Codes occupied by CCHs + Codes occupied by
E-AGCHs + Codes occupied by E-RGCHs and E-HICHs + Codes reserved for HSPDSCHs + HS-SCCH codes)
Page 16
Code
OVSF code usages are calculated as follows:
OVSF_Utilization = VS.RAB.SFOccupy/256 x 100%
DCH_OVSF_Utilization = DCH_OVSF_CODE/DCH_OVSF_CODE_Ava
If the value of the DCH_OVSF_Utilization or OVSF Utilization counter is
greater than 70% during peak hours for three consecutive days in one week, a cell
runs out of OVSF codes and code congestion will happen.
Recommended measures are as follows:
Enable the WRFD-010631 Dynamic Code Allocation Based on NodeB
feature if this feature has not been enabled. Preferentially allocate idle codes to
HSDPA UEs to improve the HSDPA UE throughput.
Add a carrier or split the sector.
Page 17
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HSDPA User
Page 18
HSUPA User
Counter:
VS.HSUPA.UE.Mean.Cell: Average Number of HSUPA UEs in a Cell
The number of HSUPA users in a cell is large, for example, reaches the maximum
number of HSUPA users allowed in the cell. As a result, new HSUPA users access R99
services, and user experience is affected.
Parameters Optimization:
Solution 1: modifying the maximum number of HSUPA users in the cell
If the maximum number of HSUPA users in the cell is set to a small value, you can
increase the value.
MOD UCELLCAC: CellId=100, MaxHsupaUserNum=20;
Solution 2: expansion
Add carriers or use HETNET solutions.
Page 19
HSUPA User----XL Surabaya02 Data
More HSUPA users, higher RTWP, lower single user throughput

Page 20
HSUPA User Num
Linear (HSUPA User Num)
VS.HSUPA.MeanChThroughput
HSUPA user number
RTWP
Page 21
Linear (VS.HSUPA.MeanChThroughput)
H S U P A ue sx pe er r i e n c e )( K b p s
HSUPA User --- XL Surabaya02
From the chart, we can see more

HSUPA user number, higher
RTWP, lower throughput every
user.
HSUPA User --- From other operator

This operator activated 40 HSUPA users and 60 HSUPA users.
Implementation
Implementation 60
60 user
user
20
20 user
user
60
60 user
user
40
40 user
user
20
20 user
user
Max HSUPA max User Number increased

200% and the CELLDCH user decreased
26.6% after we modify the Ucell Max
HSUPA user number to 60 at 14:43,2-92013
Implementation
Implementation 40
40 user
user
20
20 user
user
60
60 user
user
40
40 user
user
20
20 user
user
Max HSUPA max User Number increased

100% and the CELLDCH user decreased
25.5% after we modify the Ucell Max
HSUPA user number to 40 at 14:41,5-92013
Page 22

Implementation
Implementation 60
60 user
user
20
20 user
user
60
60 user
user
40
40 user
user
20
20 user
user
The HSUPA Payload increased

195% and the PS Payload
decreased 72.5 % after we
modify the Ucell Max HSUPA
user number to 60 at 14:43,29-2013 ;
Implementation
Implementation 40
40 user
user
20
20 user
user
60
60 user
user
40
40 user
user
20
20 user
user
The HSUPA Payload increased

115% and the PS Payload
decreased 40.9%after we
modify the Ucell Max HSUPA
user number to 40 at 14:41,59-2013 ;
Page 23

20
20 user
user
60
60 user
user
40
40 user
user
20
20 user
user
Implementation
Implementation 60
60 user
user
The RTWP increased around 1.5 dBm after we modify the

Ucell Max HSUPA user number to 60 at 14:43,2-9-2013.
Implementation
Implementation 40
40 user
user
The RTWP keep the maintain after we modify the Ucell

Max HSUPA user number to 40 at 14:41,5-9-2013.
Page 24

20
20 user
user
20
20 user
user
60
60 user
user
60
60 user
user
40
40 user
user
40
40 user
user
VS.RAB failEstabPS.ULPower.cong
caused power congestion due to the
increased user number and high
traffic ;
VS.RAB failEstabPS.HSUPAUser.cong
caused HSUPA user congestion due
to the increased HSUPA user
number;
20
20 user
user
20
20 user
user
Page 25
20
20 user
user
60
60 user
user
40
40 user
user
20
20 user
user
20
20 user
user
20
20 user
user
60
60 user
user
40
40 user
user
20
20 user
user
60
60 user
user
40
40 user
user
CS,PS and HS CSSR degradation due to the

RAB fail which caused by UL power
congestion ;
Page 26
20
20 user
user
HSUPA User
Conclusion
More HSUPA, higher RTWP and lower single user throughput.

UL power congestion will increase seriously which is caused by more HSUPA users.
The access performance will degrade seriously.
Huawei suggest the number of HSUPA users is set to 20 based on access
performance and single user throughput.
If the RTWP is very high and serious UL power congestion, Huawei suggest to
decrease the number of HSUPA users to less than 20.
Page 27
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HSDPA User
Page 28
HSDPA User
Counter:
VS.HSDPA.UE.Mean.Cell: Average Number of HSDPA UEs in a Cell
The number of HSDPA subscribers is large, or access to HSDPA services fails.
Consequently, the service rate is low.
Solution 1: increasing the maximum number of
HSDPA subscribers
To modify the maximum number of HSDPA subscribers of the cell, run the
following command:
MOD UCELLCAC: CellId=xxx, MaxHsdpaUserNum=64;
Solution 2: adding carriers, NodeBs, 6-sector

solution, mini NodeBs.
Page 29
HSDPA User ---- XL Surabaya02 Data
More HSDPA users, higher nonHS TCP Utility, lower single user throughput
Page 30
HSDPA User----from other operator
512kbps
The access performance degraded for DL power congestion.

Page 31
Page 31
HSDPA User----from other operator

VS.HSDPA.MeanChThroughput
VS.HSDPA.UE.Mean.Cell
HSDPA Poor User Experience Zone
700
60
50
512kbps
500
40
400
30
300
20
200
Number user
HSDPA
Experience user
HSDPA
600
10
100
0
<50%
50%-55%
55%-60%
60%-65%
65%-70%
70%-75%
75%-80%
85%-90%
0
>90%
HSDPA <512kbps: Non-HSDPA load>50%& HSDPA user/ cell

number>15
Page 32
Page 32
HSDPA User
HSDPA scheduling strategy:
Time
Code
TTI=2ms
Data to UE #1
Data to UE #2
Data to UE #3
More HSDPA user active means longer scheduling period, and lower data rate.
More HSDPA user will introduce more signaling and consume more power resource result
in less resource for HSDPA traffic.
Page 33
HSDPA User
Conclusion
More HSDPA users, higher non HSPA TCP utility rate and lower single
user throughput.
Higher non HSPA TCP utility will cause DL power congestion.
512kbps
Considering access performance and single user throughput, Huawei
suggests HSDPA is to set 64.
Page 34
Page 34
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HSDPA User
Page 35
CE
Counter:
VS.NodeB.ULCreditUsed.Mean: average uplink credit resource usage of a NodeB
when CE Overbooking is enabled
VS.LC.ULCreditUsed.Mean: average uplink credit resource usage of a NodeB in a cell
VS.LC.DLCreditUsed.Mean: average downlink credit resource usage of a NodeB in a
cell
VS.RRC.Rej.UL.CE.Cong: number of RRC Connection Rejects for Cell (UL CE
VS.RRC.Rej.DL.CE.Cong: number of RRC Connection Rejects for Cell (DL CE
VS.RAB.FailEstabCS.ULCE.Cong: number of Failed CS RAB Establishments for Cell
(UL CE Congestion)
VS.RAB.FailEstabPS.ULCE.Cong: number of Failed PS RAB Establishments for Cell
(UL CE Congestion)
VS.RAB.FailEstabCS.DLCE.Cong: number of Failed CS RAB Establishments for Cell
(DL CE Congestion)
VS.RAB.FailEstabPS.DLCE.Cong: number of Failed PS RAB Establishments for Cell
(DL CE Congestion)
Page 36
CE
Formula:
License-based downlink CE usage
DL License CE Resource Utility Ratio = DL NodeB Mean CE Used Number/DL
License CE Number
DL NodeB Mean CE Used Number =
Sum_AllCells_of_NodeB(VS.LC.DLCreditUsed.Mean)
DL License CE Number = DL NodeB License CE Cfg Number
Page 37
CE
Formula:
License-based uplink CE usage
UL License CE Resource Utility Ratio = UL NodeB Mean CE Used Number/UL License
CE Number
If the value of the VS.NodeB.ULCreditUsed.Mean counter is greater than 0, the CE
Overbooking feature has taken effect, and the following formula is true:
UL NodeB Mean CE Used Number = VS.NodeB.ULCreditUsed.Mean/2
Otherwise, the following formula is true:
UL NodeB Mean CE Used Number =
Sum_AllCells_of_NodeB(VS.LC.ULCreditUsed.Mean/2)
UL License CE Number = UL NodeB License CE Cfg Number
Page 38
CE
Formula:
Hardware-based downlink CE usage
DL CE Capacity Utility Ratio = DL NodeB Mean CE Used Number/DL CE
Capacity Number
The value of DL NodeB Mean CE Used Number equals that used for
calculating the license-based downlink CE usage.
DL CE Capacity Number = VS.HW.DLCreditAvailable
Hardware-based uplink CE usage
UL CE Capacity Utility Ratio = UL NodeB Mean CE Used Number/UL CE
Capacity Number
The value of UL NodeB Mean CE Used Number equals that used for
calculating the license-based uplink CE usage.
UL CE Capacity Number = VS.HW.ULCreditAvailable
Page 39
CE
If the uplink or downlink License-based or Hardware-based CE usage is constantly higher
than 70% during peak hours for three consecutive days in one week, expand capacity as
follows:
If the license-based CE usage exceeds its capacity expansion threshold, CE resources
are limited by the license. In this case, upgrade the license file.
If the hardware-based CE usage exceeds its capacity expansion threshold, CE
resources are limited by the hardware capacity. In this case, add WBBP boards.
Page 40
CE
If capacity expansion is inapplicable, perform the following operations to optimize the CE
usage:
Solution1: Decrease GBR (Guaranteed Bit Rate)
Description:
If the throughput is low in live network and the default GBR is high, more CE resource will
be reserved (low CE efficiency. Decrease GBR from 64K to 32K, it will allowed more users to
access the network.
SET UUSERGBR: TrafficClass=BACKGROUND, BearType=HSPA, UserPriority=GOLD,
UlGBR=D32, DlGBR=D32;
Solution2: TTI switch based on admission CE
Description:
HSUPA 2ms require more admission CE than 10ms, active 2ms may result in admission CE
congestion, influent user access. The feature switch 2ms HSUPA user to 10ms when CE
resource is congested, which will allow more user to access the network, and improve the CE
utility and KPI.
SET UCORRMALGOSWITCH: DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH-1;
Page 41
Content
Uplink
RTWP
HSUPA User
CE
Iub
CE
Iub
Downlink
TCP
Code
HSDPA User
Page 42
Iub
Congestion Counter
VS.RRC.Rej.ULIUBBand.Cong: number of RRC Connection Rejects for Cell (UL Iub
Bandwidth Congestion)
VS.RRC.Rej.DLIUBBand.Cong: number of RRC Connection Rejects for Cell (DL Iub
Bandwidth Congestion)
VS.RAB.FailEstabCS.ULIUBBand.Cong: number of Failed CS RAB Establishments
for Cell (UL Iub Bandwidth Congestion)
VS.RAB.FailEstabCS.DLIUBBand.Cong: number of Failed CS RAB Establishments
for Cell (DL Iub Bandwidth Congestion)
VS.RAB.FailEstabPS.ULIUBBand.Cong: number of Failed PS RAB Establishments
for Cell (UL Iub Bandwidth Congestion)
VS.RAB.FailEstabPS.DLIUBBand.Cong: number of Failed PS RAB Establishments
for Cell (DL Iub Bandwidth Congestion)
Page 43
Iub---ATM Transmission
The Iub bandwidth usage is represented by the ratio of the actual uplink or downlink load
to the configured Iub bandwidth.
1. Bandwidth-based admission success rate
Counters:
VS.AAL2.CAC.Succ: number of successful AAL2 path admissions
VS.AAL2.CAC.Att: number of AAL2 path resource admissions
Formula:
Bandwidth-based admission success rate = VS.AAL2.CAC.Succ/VS.AAL2.CAC.Att
If the bandwidth-based admission success rate is less than 99%, bandwidth congestion
probably occurred on the user plane.
Page 44
2. Physical bandwidth utilization
Control plane
Counter:
VS.SAALLNK.PVCLAYER.TXBYTES
number of bytes transmitted on an SAAL link at the ATM layer
VS.SAALLNK.PVCLAYER.RXBYTES
number of bytes received on an SAAL link at the ATM layer
Formula:
VS.SAALLNK.PVCLAYER.RX.LOAD =
VS.SAALLNK.PVCLAYER.RXBYTES*8/1000/SP<Measurement period>/RX BW_CFG
VS.SAALLNK.PVCLAYER.TX.LOAD = VS.SAALLNK.PVCLAYER.TXBYTES*
8/1000/SP<Measurement period>/TX BW_CFG
When the uplink or downlink bandwidth utility ratio reaches 70%, bandwidth congestion
occurred on the control plane.
Page 45
User plane
Counter:
VS.AAL2PATH.PVCLAYER.TXBYTES
number of bytes transmitted on an AAL2 path at the ATM layer
VS.AAL2PATH.PVCLAYER.RXBYTES
number of bytes received on an AAL2 path at the ATM layer
Formulas:
DL IUB User Plane Utility Ratio = Sum (VS.AAL2PATH.PVCLAYER.TXBYTES) *
8/SP<Measurement period>/1000/TX BW_CFG
UL IUB User Plane Utility Ratio = Sum (VS.AAL2PATH.PVCLAYER.RXBYTES) *
8/SP<Measurement period>/1000/RX BW_CFG
When the uplink or downlink bandwidth utility ratio reaches 70%, bandwidth congestion
occurred on the user plane. Then, capacity expansion is required.
Page 46
Iub---IP Transmission
The Iub bandwidth usage is represented by the ratio of the average uplink or downlink load
to the configured Iub bandwidth.
1.Bandwidth-based admission success rate
Counters :
VS.ANI.IP.Conn.Estab.Succ: number of successful IP connection setups initiated by
the transport layer on IP transport adjacent node
VS.ANI.IP.Conn.Estab.Att: number of connection setup requests for IP transport from
the transport layer to the radio network layer on the IP transport adjacent node
VS.ANI.IP.FailResAllocForBwLimit: number of failed resource allocations due to
insufficient bandwidth on the IP transport adjacent node
Formula:
IP connection setup success rate =
VS.ANI.IP.Conn.Estab.Succ/VS.ANI.IP.Conn.Estab.Att
If the IP connection setup success rate is less than 99%, bandwidth congestion probably
occurred on the user plane.
If the value of the VS.ANI.IP.FailResAllocForBwLimit counter is not zero, bandwidth
congestion occurred on the user plane.
Page 47
2. Physical bandwidth usage
Control plane
Counter:
VS.SCTP.TX.BYTES: number of IP bytes transmitted on an SCTP link
VS.SCTP.RX.BYTES: number of IP bytes received on an SCTP link
Formula:
STCP DL KBPS = VS.SCTP.TX.BYTES * 8/SP<Measurement period>/1000
SCTP UL KBPS = VS.SCTP.RX.BYTES * 8/SP<Measurement period>/1000
Page 48
User plane
Non-transmission resource pool networking

Counters:
VS.IPPATH.IPLAYER.TXBYTES: number of bytes transmitted on an IP path at the
IP layer
VS.IPPATH.IPLAYER.RXBYTES: number of bytes received on an IP path at the
IP layer
Formulas:
DL IUB User Plane Utility Ratio = Sum (VS.IPPATH.IPLAYER.TXBYTES) *
UL IUB User Plane Utility Ratio = Sum (VS.IPPATH.IPLAYER.RXBYTES) *
If the uplink or downlink bandwidth utility ratio of the user plane on the Iub interface
reaches 70%, bandwidth congestion occurred on the user plane. Then, capacity
expansion is required.
Page 49
Transmission resource pool networking
Counters:
VS.IPPOOL.ANI.IPLAYER.TXBYTES: number of IP bytes transmitted on the user
plane of an adjacent node
VS.IPPOOL.ANI.IPLAYER.RXBYTES: number of IP bytes received on the user
plane of an adjacent node
Formulas:
DL IUB User Plane Utility Ratio = VS.IPPOOL.ANI.IPLAYER.TXBYTES *
UL IUB User Plane Utility Ratio = VS.IPPOOL.ANI.IPLAYER.RXBYTES *
If the uplink or downlink bandwidth utility ratio of the user plane on the Iub interface
reaches 70%, bandwidth congestion occurred on the user plane. Then, capacity
expansion is required.
Page 50
Iub
If the Iub bandwidth usage exceeds 70% during peak hours for three consecutive days in one
week, the Iub bandwidth is considered insufficient.
No.
1
2
3
Scenario
Optimization Suggestion
Bandwidth congestion on the ATM control Increase the bandwidth configured for
plane
the SAAL link.
Bandwidth congestion on the IP control
plane
Physical bandwidth congestion on the
ATM and IP user planes
Admission bandwidth congestion on the
ATM and IP user planes, not
accompanied by physical bandwidth
congestion
Increase the transmission bandwidth for

the SCTP link.
Increase the transmission bandwidth.
Decrease the activity factor for PS
services.
Page 51
Thank you
www.huawei.com

RAN14 3G Capacity Monitoring

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RAN14 3G Capacity Monitoring

Transféré par

Droits d'auteur :

Formats disponibles

Security Level:

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Solution1: CQI feedback period optimization

MOD UPRACHUUPARAS: CellId=xxx, PhyChId=4, Constantvalue=-30,

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

MeanNonHSTCP 10 (VS .MeanTCP. NonHS /10) / 1000

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

The maximum number of codes available for the DCH can be

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HSUPA User----XL Surabaya02 Data

More HSUPA users, higher RTWP, lower single user throughput

HSUPA User Num

Linear (HSUPA User Num)

HSUPA user number

HUAWEI TECHNOLOGIES CO., LTD.

HSUPA User --- XL Surabaya02

From the chart, we can see more

HSUPA User --- From other operator

Max HSUPA max User Number increased

HUAWEI TECHNOLOGIES CO., LTD.

Max HSUPA max User Number increased

HSUPA User --- From other operator

The HSUPA Payload increased

HUAWEI TECHNOLOGIES CO., LTD.

The HSUPA Payload increased

HSUPA User --- From other operator

The RTWP increased around 1.5 dBm after we modify the

The RTWP keep the maintain after we modify the Ucell

HUAWEI TECHNOLOGIES CO., LTD.

HSUPA User --- From other operator

HUAWEI TECHNOLOGIES CO., LTD.

HSUPA User --- From other operator

HUAWEI TECHNOLOGIES CO., LTD.

CS,PS and HS CSSR degradation due to the

More HSUPA, higher RTWP and lower single user throughput.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Solution 2: adding carriers, NodeBs, 6-sector

HSDPA User ---- XL Surabaya02 Data

HSDPA User----from other operator

The access performance degraded for DL power congestion.

HSDPA User----from other operator

HSDPA Poor User Experience Zone

HSDPA <512kbps: Non-HSDPA load>50%& HSDPA user/ cell

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.