WCDMA Radio Network Coverage &

WCDMA Radio Network
Coverage & Capacity

Planning
nw.rnocenter@gmail.com
nw.rrfcenter@gmail.com
nw.osscenter@gmail.com
Contents
Scope of 3G Network Planning
WCDMA Planning Process Overview
Input Parameters
Link Budget Overview
Site Selection Criteria
Co Sitting and Interference Issues
Nominal Planning Fundamentals
NetAct Simulations Process Overview
Nexwave Design and Strategic Page 2

Simplified Network Planning Flowchart
Initial network dimensioning
CW
Measurement
Create nominal plan
Define search areas
Identify site options
Site selection
Site acquisition
Detailed site design
Site construction

Contents
Input Parameters

Scope of 3G network planning
Packet Switched Core

Network planning process & relation to
business planning
Network marketing
dimensioning
Network
business optimization
plan
transmission coverage
plan plan
traffic parameter
assumptions planning
Code & freq. &

interference plan
final NW
topology/
architecture

Contents
Input Parameters

Issues in WCDMA planning
DEFINITION PLEMENTATION O&M

Coverage and capacity
coupling
Network Coverage Parameter Network
Capacity
Configuration Planning and Requirements Planning Optimisation
and Site Selection
Dimensioning Traffic distribution Area / Cell Survey
Service distribution specific measurements
Requirements Propagation Allowed blocking/queuing
and strategy measurements System features
Coverage Handover Statistical
for coverage, strategies performance
quality and prediction
analysis
capacity, Multiple services Maximum
per service Site network Quality
loading Efficiency
acquisition External Interference
Coverage Availability
Analysis
optimisation Other RRM
Identification
Adaptation
Multiple services

Radio networks Dimensioning Overview
COVERAGE CAPACITY
COMPROMISE BETWEEN COVERAGE AND CAPACITY

UTRAN Radio Dimensioning
Infrastr.
Per area and
-Output toward Access planning

Parameters
Traffic
• #Demand
of sectors per Phase
•• per
antennas
bearer
• req
• # of
cov area
subs
•• GoS
etc.  Number of NodeBs
• etc.  NodeB Type
 NodeB
DIM TOOL RF Planning configuration:
LINK BUDGET DIM TOOL
Parameters - Amount
Customer Air Interface • interf
Rel’99, CPICH, NodeBmarg
Requirements Dimensioning •Dimensioning
HO gain - BB dim
HSDPA, HSUPA
(Capacity: Rel’99 • environment
CHC, DRIC, FSM) -etc.
+ HSPA ) • etc.
 And NodeB
Upgrade:
System - #Board / #FSM
Parameters System
• Eb/No Parameters - #Carrier
• TX power • spectral - Sectorisation
• etc. efficiency
• etc. -…

Coverage VS Capacity Dimensioning
Cell Breathing
This diagram shows when some
• This diagram shows cells cells are loaded
are unload
Cell
breathing
Cell-
A
Cell- Cell-
A B
Cell- Cell-
B C
Cell-
C Results =>
Coverage
Holes!

Coverage VS Capacity Dimensioning
Fixed Uplink Load - To avoid Coverage holes
"actual" Loading, (ie from This diagram shows a
the traffic inputs defined Fixed Uplink Load design
• No (or minimum)
in dimensioning)
coverage holes problems
• More cells required

Cell-
B • Traffic mobility taken into
Cell- Cell- account. (Note:
Cell- A C
A dimensioning assumes
Cell-
D uniform traffic
Cell- Cell- Cell- distribution)
B H F
Cell-
Cell- E
C Cell-
G
Results => No
eg. Actual UL or Min Coverage
eg. Fixed UL Holes!
load = 8% load = 30%
Contents
Input Parameters

Input parameters – overview
Input Categories
 CAPACITY RELATED
 Spectrum Available
 User Profile and Traffic Growth
 Gives an Estimation of the
Forecast Equipment Necessary to Meet
 Traffic Density Map the Network Requirements
 Network Dimensioning Activities
 COVERAGE RELATED
 Coverage Regions
 Radio Link Budget
 Area Type Information
Calculation
 Cell Size Calculation
 Capacity Calculation
 QUALITY RELATED  Transmission Network
 MS Class
Estimate
 Indoor Coverage
 Location Probability
 Blocking Probability

Summary of Dimensioning Inputs
Dense Urban Urban Suburban Rural
# of subs & mErl per # of subs & mErl per # of subs & mErl per # of subs & mErl per
Voice sub sub sub sub
# of subs & mErl per # of subs & mErl per # of subs & mErl per # of subs & mErl per
CS data sub sub sub sub
# of subs & kbps per # of subs & kbps per # of subs & kbps per # of subs & kbps per
PS data sub sub sub sub
Coverage area km2 km2 km2 km2
Location
% % % %
probability
Standard
dB dB dB dB
deviation
Fade margin dB dB dB dB
Penetration loss dB dB dB dB
Area correction
dB dB dB dB
factor
MS / Node B
m m m m
antenna height

Contents
Input Parameters

Link Budget Overview
Soft handover
gain,
antenna gain
Noise figure
Body loss
Cable
losses
Building Penetration
loss
Max Allowed = Tx Signal + All Gains – Other Losses – Rx

Path Loss (L)
Sensitivity

Link Budget Overview
Path loss = Tx signal + all gains - losses - ( SNR + Noise)
Bit rate bit/s 64000 a

Total TX power available dBm 21 b
TX antenna gain dBi 2 c
Body loss dB 0 d
TX EIRP per traffic channel dBm 23 e=b+c-d
RX antenna gain dBi 18 f
RX cable and connector losses dB 3 g
Receiver noise figure dB 3 h
Thermal noise density dBm/Hz -174 j
Cell loading % 70 k
Noise rise due to interference dB 5.23 l=10*log10(1/(1-(k/100)))
Total effect of noise dBm/Hz -171 m=h+j
Information rate dBHz 48.06 n=db(a)
Effective required Eb/No dB 2.54 o
RX sensitivity dBm -115.40 p=l+m+n+o+correction factor
Soft Handoff Gain dB 4.5 q
Fast fading Margin dB 2.5 r
Log normal fade margin dB 11.6 s
In-building penetration loss (urban) dB 20 t
Maximum path loss urban dB 123.80 pl=e+f+q-g-p-r-s-t

Contents
Input Parameters

Site Selection Criteria
Proper site location determines usefulness of its cells
Sites are expensive
Sites are long-term investments
Site acquisition is a slow process
Hundreds/thousands of sites needed per network
Base station sites are valuable
long-term assets for the operator

How do I asses a site option?
Each site needs to be assessed on several
grounds.
Radio
Transmission
Access
Power
Planning
Ideally every site option reported by the
surveyor would pass in each of the areas listed
above.

Bad GSM Sites
In GSM, there were two types of bad sites.
 Donkeys - Low sites which provide very little coverage.
 Donkeys carry so little traffic that they often never pay for themselves.
 Boomers - High sites which propagate much further than is needed.
 A boomer will cause localised interference and prevent capacity being added to
some other sites in the area.
Small “Donkey” site Large “Boomer” site

Bad UMTS Sites
 Good radio engineering practice doesn’t change much for UMTS.
 It just becomes more important.
 In UMTS
 A “Donkey” will never pay for itself.
 A “Boomer” will reduce the range and capacity of surrounding sites.
 Two major factors determine whether a site is considered good, a “Donkey”
or a “Boomer”, They are:
 Site location.
 Antenna height.
 Other parameters can be used in an attempt to control booming sites but it is
far better to avoid building them in the first place.

Contents
Input Parameters

Importance of Controlling 'Little i'
 WCDMA is an interference-limited network. I.e. capacity of the network is
directly linked to how interference is maintained/controlled.
 From the Radio Network Planning point of view, the "little i" - other-to-own cell
interference- is the only thing that can really be influenced by the Planner during
the site selection and planning stage. WCDMA RF planning is all about having
good dominance in the desired coverage area.
 Unlike in GSM, that there is no frequency plan to "play" with in order to

minimize the effects of bad sites.
Uplink Load Downlink Load

Equation Equation
K 1
UL  (1 pw _ rise i )   DL  
K (Eb / No)k
 1 k   i   vk
k 1 W
1 k 1 (W / R)k
 Eb   R  v
 N k k
 o k

i = Coverage Overlap
 Some overlap is required to allow soft handover to occur

 Need to control amount of interference since the network
capacity is directly related to it.
 Soft handover helps to reduce interference. (Soft HO Gain)
 Too much overlap:
• Increases interference to other cells --> reduce capacity
• Increases Soft Handover overhead --> reduce capacity

Bad Site Location
Avoid hill-top locations for BS sites (same for GSM)
 uncontrolled interference
 interleaved coverage
 no sharp dominance areas
 awkward Soft/Hard HO behaviours
 BUT: good location for microwave links ! (TNP jurisdiction)
wanted cell uncontrolled, strong

boundary interferences
interleaved coverage areas:

weak own signal, strong foreign signal

Good Site Location
Prefer sites off the hill-tops
 use hills/high rise buildings to separate cells
 contiguous coverage area
 well defined dominance areas
 needs only low antenna heights if sites are slightly elevated above valley bottom
wanted cell
boundary

Antenna installation issues:
Clearance angle
h (meters)
Clearance angle
d (meters)
Side view
• Rules of thumb:
– h  d/2, d < 10 m Antenna
– h  d/3, 10 < d < 20 m d (meters)
– h  d/4, d > 30 m
Top view

Antenna installation
Safety margin of 15 between the

reflecting surface and the 3 dB lobe
d has to be >
3.2 m

DOCUMENTTYPE 1 (1)
TypeUnitOrDepartmentHere
Other RF-systems
TypeYourNameHere TypeDateHere
Be careful with
back-lobe!
Acceptable
Not Acceptable

Characteristics of a good site
It has good clearance,

no obstacles around, and it
overlooks the surrounding rooftops.
This site will give good macro coverage.
Bad site; blocked by neighbour building

Characteristics of a good site
BAD: In a urban/dense urban area,

too high a site is a bad site since it
will introduce too much interference
to other sites in the network
(remember the little i)
while for a rural area it's a good site.

Examples of Bad Sites
Typical mess! =>

GSM1800 antennas with space div.
between CDMA (IS-95) antennas and These situations can easily be
pointing directly at the high avoided!!
building
Time consuming and costly to fix.

Little i, Little i, Little i !!!
Arghhh… note how far you can see - Well shit happens … who could have known
roughly 10km = TOO FAR. There is a that they were going to build this high
river as well, so interference is building one year after installation ?!
enormous. Site distance is about 700 Planners should
meters in this phase!! Site was good have anticipated this during initial site
in phase 1 when distance between surveys!
sites was 4km!
Is this installation OK? The satellite dish is in

near field of the GSM900 antennas -> some
effects for sure. Definite interference to
The TX/RX and Rx div antennas are satellite system. But could not be tested
not pointing in the same direction! because the satellite system was not in use!
Installation problem. Avoid installing antennas in close proximity
to other objects since its radiation pattern
will be altered.

Summary of Site Selection Guidelines
 The objective is to select a site location which covers the desired area but keeps
emissions to a minimum.
 The site should be located as close to the traffic source as possible. The closer the site is
to the traffic, the less output power will be required by the user equipment and node B.
This will minimize the noise affecting other users on both the serving cell as well as
other nearby cells.
 The antenna height selected will depend largely on the type of environment in which
the site is to be located. Ex Dense Urban, Urban, Suburban, Rural.
 The key factor to be considered is how well can the emissions be controlled.
 You can "feel" the site only if you are there!
 If one or more of these characteristics are not fulfilled by the examined site, the Field
Planner should REJECT the site and choose another site
 Be flexible, even creative! Try to think of all the possible implementation solutions that
the site could support: different pole heights, split poles for different sectors, etc.
 Always check neighbouring sites, to be sure your chosen candidate is "fitting" well into
the surrounding, e.g. for coverage, SHO zones,etc.

Using Existing Cellular Sites
 Most UMTS networks will be built around an existing GSM network.
 Many GSM networks were built around existing analogue sites.
 In the early days of analogue cellular sites were often located to give
maximum coverage. No thought was given to capacity issues.
 Despite causing problems in high capacity networks, many of these high
sites are still in operation today.
 Most cellular networks contain these nightmare sites.
 When rolling out UMTS around an existing network it is vital to avoid these
sites.

UMTS Configurations
• Most vendors support the same basic configurations.
– Omni
– 3 sector
– 6 sector
• Each vendor supports their own variations on these configurations.
– Some solutions eliminate the need for RF plumbing.
– Some require similar amounts of equipment to a GSM BTS.
– Some increase the number of antennas on a site.
• The configuration can be affected by the wide variety of UMTS antennas.

Co-locating a Node B at a GSM site
 Isolation requirements between UMTS and GSM systems can be derived from UMTS
and GSM specifications.
 In many cases equipment performance will exceed the requirements in the
specifications.
 Each vendor should be able to provide information which can be used to improve
the isolation requirements.
 The isolation requirements will affect
• Choice of antenna configuration
• Filtering at both the GSM and UMTS sites.
 Isolation is the attenuation from the output port of a transmitter to the input port of
the receiver.

Interference Issues
 Wideband Noise - unwanted emissions from modulation process and non-
linearity of transmitter
 Spurious Emissions - Harmonic, Parasitic, Inter-modulation products
 Blocking - Transmitter carriers from another system
 Inter-modulation Products - Spurious emission, specifications consider this in
particular
• Active: non-linearities of active components - can be filtered out by BTS
• Passive: non-linearities of passive components - cannot be filtered out by BTS
 Other EMC problems - feeders, antennas, transceivers and receivers

Interference from Other System
 GSM spurious emissions and intermodulation results of GSM 1800
interfere WCDMA receiver sensitivity
 WCDMA spurious emissions interfere GSM receiver sensitivity
 GSM transmitter blocks WCDMA receiver
 WCDMA transmitter blocks GSM receiver
GSM GSM UMTS UMTS

1800 UL 1800 DL UL DL
40 MHz
1710-1785 1805-1880 1920-1980 2110-2170
MHz MHz MHz MHz

Contents
Input Parameters

What is a nominal plan?
 A nominal plan is initially a hypothetical
wireless network. Nominal Plan
 The nominal plan is the starting point for the
cell rollout process and will evolve into the
final network design. Rollout
process
 As physical sites are identified and acquired,
the nominal plan is amended.
Final Network
Design

Initial Network Dimensioning
 Spreadsheet based analysis. Typical cell radii estimates
 Used in the license application. Urban Suburban Rural
 Identifies the approximate number Voice 1.8 km 3.1 km 4.4 km
64 kb/s 1.6 km 2.7 km 3.5 km
of sites required. 384 kb/s 1.1 km 2.4 km 3.2 km
 Identifies the approximate site radii
required for: Service supported
 Urban/Suburban/Rural areas Maximum range to support all services

 Voice/Data services Service not supported in this environment
 Used as a major input to the
nominal plan.

Create Nominal Plan
 Position a hexagonal grid of sites
over the desired coverage area.
 The radius of each hexagon can be
determined from the previous
slide.
 The capacity of the network can
then be analyzed to detect:
 Hot spots that require cell
splits.
 Under used cells that could be
Example nominal plan for Jersey
removed from the plan.

Define Search Areas
 The sites in a nominal plan are only imaginary.
 To become a real network, physical sites are required.
 A suitable physical site must be found for each nominal site.
 A suitable physical site must amongst other things:
 Give adequate radio coverage.
 Have connectivity into the transmission network.
 Be aesthetically and politically acceptable to the local community.
 Have power nearby, good access and a co-operative owner.
 A survey of each nominal site is normally carried out to identify possible site
options which meet the above criteria.

Define Search Areas
 Guidelines have to be given to the surveyor so the options give appropriate
radio coverage.
 The guideline is given in the form of a search area. Could be:
• Radius from the nominal site.
• One or more polygons following height contours.
Or

Identify Site Options
 Surveyor visits each search area and identifies potential site options.
 The first sites to be considered should be
• Existing radio sites.
• Sites offered from major site owners (MSO) E.g. Utilities & Railways.
 All options should meet certain criteria to ensure that they are
• Technically acceptable.
• Build able
 A good idea to consult with the planning/zoning authority during the survey.
 Good training of surveyors will save time later in the build process.

Identify Site Options
 The surveyor will prepare a report
listing the options.
 Report will include: A
• Accurate grid reference.
• Accurate height of structures D
or available antenna
windows.
C B
• Photographs of the site.
• 360º panoramic photos from
site or if obstructed from
nearby location/structure.

Site Selection
 Normally a desk study.
 Evaluate radio coverage and
transmission. A3rd
 Quickly eliminate unsuitable
options.
D1st
 Rank the remaining sites in
order of preference.
C2nd
 Nominate a preferred option and B - Unsuitable
possibly a backup option.

Detailed Site Design
 Prior to commencement of 300º 60º
construction work, a detailed site
design is required. Ant 6 Ant 1
 Includes 300º 60º
Ant 5
 Antenna and feeder
requirements. Ant 2
 Antenna azimuths and tilts. Ant 4 Ant 3
 Equipment capacity
requirements 180º 180º
 Can’t be completed in isolation.
Must take into account other sites.

Contents
Input Parameters

Evaluate Nominal Network Coverage
 Run a coverage array for the nominal

network.
 Check that the coverage is in line with
your expectations.
 Adjust site locations and add additional
sites if improvements to coverage is
necessary.
 Check for excessively high sites.

WCDMA Radio Network
Capacity

RAN Resource diagram
•DL total power/DL ENU

•RTWP/UL ENU RRU
•OVSF Code (DCH/HS-PDSCH) 1
-CE card
-CE license
-HS-PDSCH code license
•RTWP/UL ENU RRU
2
BBU RNC
•OVSF Code (DCH/HS-PDSCH) UL/DL Iub bandwidth

•RTWP/UL ENU RRU
•OVSF Code (DCH/HS-PDSCH) 3

Flow Chart of CAC
Nexwave
CopyrightDesign and
© 2006 Huawei Strategic
Technologies Co., Ltd. All rights reserved. Page 73
CE board – WBBP type configuration

Step for Low CSSR PS Investigation

Solution for Code Congestion
To solve code congestion, we recommend using LDR algorithm also. The MML configuration is
as follows:
Switch on the LDR switch:

MOD CELLALGOSWITCH: CellId=0, NBMLdcAlgoSwitch= CELL_CODE_LDR -1;
Setting LDR action:

MOD CELLLDR: CellId=0, DLLDRFIRSTACTION=CodeAdj, DLLDRSECONDACTION=BERateRed,
DlLdrBERateReductionRabNum=1, GoldUserLoadControlSwitch=ON;

Solution for Power Congestion
Power congestion will cause low CSSR of both CS and PS service.

We can check counters as below to find power congestion:
VS.RRC.Rej.ULPower.Cong
VS.RRC.Rej.DLPower.Cong
VS.RAB.FailEstabCS.ULPower.Cong
VS.RAB.FailEstabCS.DLPower.Cong
VS.RAB.FailEstabPS.ULPower.Cong
VS.RAB.FailEstabPS.DLPower.Cong
To check whether UL or DL congestion:

1. Check the Max Tx power of the congested cell
Add cellsetup:cellid=1111, maxtxpower=430
2. Check counter VS.MeanTCP and VS.MeanTCP.NonHS and calculate the utility
ratio to check whether the utility ratio is very high.
3. Monitor the RTWP to check whether RTWP is very high.

Currently for uplink we use Equivalent Number of User (ALGORITHM_SECOND) to do CAC; for
downlink we use TCP (ALGORITHM_FIRST) to do CAC. According to our CAC strategy, first make
sure some basic parameters should be configured as follows:
ADD CELLALGOSWITCH: CellId=0, NBMUlCacAlgoSelSwitch=ALGORITHM_SECOND,
NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST;
Solution for Uplink Power Congestion:

1. Increase Equivalent Number of User
MOD CELLCAC: CellId=0, UlTotalEqUserNum=150;
2. For single carrier cells or F1 cells, use LDR algorithm:
Switch on the LDR switch:
MOD CELLALGOSWITCH: CellId=0, NBMLdcAlgoSwitch=UL_UU_LDR-1;
Setting LDR action:
MOD CELLLDR: CellId=0, UlLdrFirstAction=BERateRed,
UlLdrBERateReductionRabNum=1; GoldUserLoadControlSwitch=ON;

Solution for Downlink Power Congestion:

1. Raise the power congestion threshold
MOD CELLCAC: CellId=0, DlConvAMRThd=85, DlConvNonAMRThd=85, DlOtherThd=83,
DlHOThd=87, DlCellTotalThd=93;
2. For single carrier cells, we can use downlink LDR:
MOD CELLALGOSWITCH: CellId=0, NBMLdcAlgoSwitch=DL_UU_LDR-1;
MOD CELLLDR: CellId=0, DlLdrFirstAction=BERateRed,
DlLdrBERateReductionRabNum=1; GoldUserLoadControlSwitch=ON;

TCP Counter and monitoring
• Example : BKD0040U3
MaxTxPower44
– MaxTxPower = 43 dBm
42
– MaxPCPICHPower = 33 dBm
40
38
dBm
PCPICH + Common channel • We can monitor TCP usage from counter
36
– VS.MaxTCP (R99+HSDPA)
PCPICH 34
– VS.MeanTCP (R99+HSDPA)
32 – VS.MaxTCP.NonHS (R99)
30 – 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[%] =
Average of VS.MaxTCP Average of VS.MeanTCP 80
– DL threshold of other services[%] = 75
– DL handover access threshold[%] = 85
MaxTxPower
44
– DL total power threshold[%] = 90
42 • RRC CAC considers OLC Trigger Threshold for
admission
40
– DL OLC trigger threshold[%] = 95
38
dBm
PCPICH + Common
36
channel
PCPICH
34
32
30
Nexwave Design and Strategic

Average of VS.MaxTCP.NonHS Average of VS.MeanTCP.NonHS
Page 102
UL ENU counter and monitoring
• Take a look at parameter setting of maximum

allowed equivalent user number
35
– UL total equivalent user number = 80 (by default)
30 • Example : BKD0040U3
25
•We check parameter setting for RAB CAC

20
-UL threshold of Conv AMR service[%] = 75
15
-UL threshold of Conv non_AMR service[%] = 75
10 -UL threshold of other services[%] = 60
-UL handover access threshold[%] = 80
5
-UL total power threshold[%] = 83
0
•RRC CAC considers OLC Trigger Threshold for admission
-UL OLC trigger threshold[%] = 95
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%

Solution for CE Congestion
CE congestion will cause low CSSR of both CS and PS service.

We can check counters as below to find CE congestion:
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RAB.FailEstabCS.ULCE.Cong
VS.RAB.FailEstabCS.DLCE.Cong
VS.RAB.FailEstabPS.ULCE.Cong
VS.RAB.FailEstabPS.DLCE.Cong
Solution
1. Adding BBU Board is recommended.
2. CE Rebalancing

Solution for IuB Congestion
IuB congestion will cause low CSSR of both CS and PS service.

We can check counters as below to find IuB congestion:
VS.RRC.Rej.ULIUBBand.Cong
VS.RRC.Rej.DLIUBBand.Cong
VS.RAB.FailEstabCS.DLIUBBand.Cong
VS.RAB.FailEstabCS.ULIUBBand.Cong
VS.RAB.FailEstabPS.DLIUBBand.Cong
VS.RAB.FailEstabPS.ULIUBBand.Cong
Solution
The best solution is to expand the IUB band. Other solutions are just temporary
methods to remain the KPI.
When IUB congestion is detected, first we need check the IUB utility ratio, if utility
ratio is very small but still congestion, it may caused by wrong transmission
configuration.

Solution for IuB Congestion
Usually we can modify the FTI of the congested NodeB. MML is as follow:
1. Find the FTI of the Node B.
ADD ADJNODE: ANI=33, NAME="node B", NODET=IUB, NODEBID=1111,
TRANST=ATM;
ADD ADJMAP: ANI=33, ITFT=IUB, TRANST=ATM, CNMNGMODE=SHARE,
TMIGLD=1, TMISLV=2, TMIBRZ=1, FTI=4;
2. Change the FTI of the Node B to 20.

MOD ADJMAP: ANI=33, ITFT=IUB, TRANST=ATM, CNMNGMODE=SHARE,
TMIGLD=1, TMISLV=2, TMIBRZ=1, FTI=20;
Example
FTI=4 =>100%
FTI=20=> 50%

Load Reshuffle Step

3G Scope of Work
SPU Load Utilization

UL/DL CE Utilization DSP Load Utilization
HSDPA License User Numbers INT Load Utilization IuCS CP/UP Utilization
Power Utilization Forecast CPU Load
Code Utilization Load Rebalancing
NodeB RNC MGW MSC
IuB Utilization
IuB E1 Numbers Forecast
SGSN
IuPS CP/UP Utilization
GGSN

Page 108
SPUa Board Introduction
SPU Load (CPU usage, CP & UP Inter-  The resources of CP and UP within a subrack
CCB usage) reporting subrack Load
are managed and allocated by the MPU
Sharing
subsystem.
 Only user related signaling such as RRC, RB
signal processing can be shared between
MPU MPU different SPU boards.
SPU SPU
SPU SPU  1st priority: MPU will transfer new services

request to SPU resources within subrack.
SPU SPU
 2nd priority: Transfer new services request to
other subrack SPU resources for signal
processing.
If SPU CPU overloads, MPU will
If SPU CPU loads remain low, divert new call attempts to other
new call attempts will not be SPU for signal processing.
transferred to other SPU for
signal processing.
SPU High CPU Load MPU Main Processing

Unit
SPU Low Load SPU
Page 109

Study Case 1 – SPU-DPU
Capacity Expansion

SPU CPU Load Utilization
Methodology
Counts of SPU Modules Quantities
SPUa Hardware
(Exclude MPU)
BH Average SPU Load (%) VS.XPU.CPULOAD.MEAN
BH Maximum SPU Load (%) VS.XPU.CPULOAD.MAX
Expansion Threshold VS.XPU.CPULOAD.MEAN >= 70%

Page 111
SPU Load Balancing
Methodology
SET CTRLPLNSHAREPARA:
Parameters Setting
CP Sharing out Threshold 40%
1% SPU CPU Load ≈ 11300 BHCA values

If there were huge amount of sites integrated under one SPU, the CPU load
will remains high because of cell related signal processing which cannot be
shared.
Query NodeB BHCA (V2R11 Formulas)=

[RRC.SuccConnEstab.Reg]*{0.438}+[RRC.SuccConnEstab.Detach]*{0.438}+[RRC.SuccConnEstab.IRATCelRes]*{0.625}+[RRC.SuccCon
nEstab.OgLwPrSig]*{0.438}+[RRC.SuccConnEstab.TmLwPrSig]*{0.442}+[VS.RAB.SuccEstab.AMR]*{1}+[VS.RAB.SuccEstCS.Conv.64]*
{1}+([VS.RAB.SuccEstabPS.Conv]+[VS.RAB.SuccEstabPS.Str]+[VS.RAB.SuccEstabPS.Inter]+[VS.RAB.SuccEstabPS.Bkg])*{1}+[VS.UTRA
N.AttPaging1]*{0.005}+[SHO.SuccRLAddUESide]*{0.303}+[SHO.SuccRLDelUESide]*{0.144}+[VS.SoHO.ASU.SuccRLAdd]*{0.202}+[VS
Manual Balancing .SoHO.ASU.SuccRlDel]*{0.106}+([VS.RRC.MrRpt.1A]+[VS.RRC.MrRpt.1B]+[VS.RRC.MrRpt.1C]+[VS.RRC.MrRpt.1D]-
[SHO.SuccRLAddUESide]-[VS.SoHO.ASU.SuccRLAdd]-[SHO.SuccRLDelUESide]-
[VS.SoHO.ASU.SuccRlDel])*{0.002}+[IRATHO.SuccOutCS]*{0.558}+([VS.URAUpd.Succ.Prd]+[VS.URAUpd.Succ.CHG])*{0.038}+([VS.C
ellUpdt.SuccUpd]+[VS.CellUpdt.SuccPrd]+[VS.CellUpdt.SuccResel]+[VS.CellUpdt.SuccPage]+[VS.CellUpdt.SuccULDatTrsf])*{0.038}+
[VS.SuccRBRecfg]*{0.240}
 Determine which SPU subsystems processed the highest BHCA traffics.

 Determine numbers of NodeB to be re-homed based on each BHCA
values, to lower BHCA traffics SPU subsystems.
Monitoring the SPU Load (%) after NodeB Re-homed.

Page 112
SPU Load Balancing
Before
SPU 1:0:1
76261 BHCA
75% CPU Load
NodeB Re-homed
to other load BHCA
SPU modules After
SPU 1:0:1
55808 BHCA
60% CPU Load

Page 113
DPUb Board Introduction
Description
 Performing functions involved: GTP-u, IuUP, PDCP, RLC,

MAC, and FP protocols.
 Performing encryption, decryption, and paging.
 Processing internal communication protocols between
SPU and DPU board.
 Providing Multimedia Broadcast and Multicast Service
(MBMS) processed on RLC and MAC layers.
DPUb Standard Specifications

 Supported 115 Mbit/s Data Throughputs
(UL+DL)
 CS Voice Services: 1800 erlangs
 CS Data Services: 900 erlangs
 Supported MAX. 150 cells

Page 114
DSP Load Utilization
Methodology
DPUb Hardware 22 DSP modules per DPUb boards.
BH Average DSP Load (%) VS.DSP.DSPUsageAvg
BH Maximum SPU Load (%) VS.DSP.DSPUsagePeak
Expansion Threshold VS.DSP.DSPUsageAvg >= 70%

Page 115
DSP Load Balancing
Methodology
SET USERPLNSHAREPARA:
Parameters Setting
UP Sharing out Threshold 50%
Factors for RNC DSP load unbalanced between subracks:
 High NodeB occupancy in several subracks.
 User plane sharing out threshold parameter setting.
 GBR parameters setting for Best Effort services.
1% DSP CPU Load ≈ 2.63 UP Traffics Throughputs Mbit/s
Cell level UP Traffic Throughputs Mbit/s:

(VS.CS.RB.Erlang*64/1000)+(PS.UL.Throughput(RLC)+PS.DL.Throughput(RLC)+
Manual Balancing VS.HSDPA.MeanChThroughput.TotalBytes+VS.HSUPA.MeanChThroughput.Tota
lBytes)*8/3600/1000000
 Find out which subrack processed the highest UP traffics.
 Query the DSP overload alarms attempt.
 Determine numbers of NodeB to be re-homed on the basis of cell level
UP, to lower traffics subrack.
 Monitoring the DSP Load (%) after NodeB Re-homed.
 Update DSP overload alarms report.

Page 116
DSP Load After Balancing

Page 117
Study Case 2 – High RRC
rejection due to Node B
Resource Unavailable
impacted to Accessibility
Service

Study Case - high RRC rejection due to Node B Resource Unavailable
impacted to Accessibility Service

Highlight :
1. For degradation at RNC_KAYUN_03 is because of high RRC rejection due to NodeB Resource
Unavailable occurred again in GILI_ANYAR_XL sector 1
2. BBP condition now is balance. HSDPA Pool switch has been activated by 10-Sep


Highlight :
1. NBAP Capacity for 1 UMPT + 2 UBBPd1-5 = 700
2. License injected = 500 (350+150)

Highlight :
1. From chart above, and from evaluation, it’s not reach the CNBAP capacity.
2. If the DCH user reach 128, cell will reject the new users. And from performance log, even the DCH
user still reach 100, the performance already degraded.
3. This is because the performance measured in a static condition for a certain period and only show
the mean value of that certain period, so it might reach 128 at a time and cause this degradation.
4. At U2100 sector 1 , DCH user number higher than 100 (exceeded), need to expand node B capacity or
optimizing traffic sharing strategy to U900 to solve this issue.

Study Case 3 – CE Congestion
Monitoring

RRC Setup Congestion Monitor
Example : BKD0040U3
1.2 UL CE Usage
160
140
1
120
100
0.8 80
60
40
0.6
20
0
0.4
Sum of VS.LC.ULCreditAvailable.Shared Sum of VS.LC.ULMax.LicenseGroup.Shared
0.2 Sum of VS.LC.ULMean.LicenseGroup.Shared
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.
UL and DL CE Usage Monitoring
Example : BKD0040U3
120
DL CE Usage
As PS RAB congestion has
100
80
been found in cause UL CE
60 congestion. From CE usage
40
20
monitoring we can see
0
sometimes the maximum
Sum of VS.LC.DLCreditAvailable.Shared
Sum of VS.LC.DLMean.LicenseGroup.Shared
Sum of VS.LC.DLMax.LicenseGroup.Shared
usage touches all available
CE.
UL CE Usage
160
140
120
100
80
60
40
20
0
Sum of VS.LC.ULCreditAvailable.Shared Sum of VS.LC.ULMax.LicenseGroup.Shared

Sum of VS.LC.ULMean.LicenseGroup.Shared

Thank You
nw.rnocenter@gmail.com
nw.rrfcenter@gmail.com
nw.osscenter@gmail.com

WCDMA Radio Network Coverage &amp;

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

WCDMA Radio Network Coverage &amp;

Încărcat de

Drepturi de autor:

Formate disponibile

WCDMA Radio Network

Coverage & Capacity

Nexwave Design and Strategic Page 2

Create nominal plan

Define search areas

Identify site options

Detailed site design

Nexwave Design and Strategic Page 3

Nexwave Design and Strategic Page 4

Packet Switched Core

Nexwave Design and Strategic Page 5

Code & freq. &

Nexwave Design and Strategic Page 6

Nexwave Design and Strategic Page 7

DEFINITION PLEMENTATION O&M

Nexwave Design and Strategic Page 8

COMPROMISE BETWEEN COVERAGE AND CAPACITY

Nexwave Design and Strategic Page 9

-Output toward Access planning

Nexwave Design and Strategic Page 10

Nexwave Design and Strategic Page 11

• More cells required

Nexwave Design and Strategic Page 13

Nexwave Design and Strategic Page 14

Coverage area km2 km2 km2 km2

Nexwave Design and Strategic Page 15

Nexwave Design and Strategic Page 16

Max Allowed = Tx Signal + All Gains – Other Losses – Rx

Nexwave Design and Strategic Page 17

Bit rate bit/s 64000 a

Nexwave Design and Strategic Page 19

Nexwave Design and Strategic Page 20

Nexwave Design and Strategic Page 21

Nexwave Design and Strategic Page 22

Small “Donkey” site Large “Boomer” site

Nexwave Design and Strategic Page 23

Nexwave Design and Strategic Page 24

Nexwave Design and Strategic Page 25

 Unlike in GSM, that there is no frequency plan to "play" with in order to

Uplink Load Downlink Load

Nexwave Design and Strategic Page 26

 Some overlap is required to allow soft handover to occur

Nexwave Design and Strategic Page 27

wanted cell uncontrolled, strong

interleaved coverage areas:

Nexwave Design and Strategic Page 28

Nexwave Design and Strategic Page 29

Nexwave Design and Strategic Page 30

Safety margin of 15 between the

Nexwave Design and Strategic Page 31

Nexwave Design and Strategic Page 32

It has good clearance,

Bad site; blocked by neighbour building

Nexwave Design and Strategic Page 33

BAD: In a urban/dense urban area,

while for a rural area it's a good site.

Nexwave Design and Strategic Page 34

Typical mess! =>

Nexwave Design and Strategic Page 35

Is this installation OK? The satellite dish is in

Nexwave Design and Strategic Page 37

Nexwave Design and Strategic Page 38

Nexwave Design and Strategic Page 39

Nexwave Design and Strategic Page 40

WCDMA Radio Network Coverage &

WCDMA Radio Network Coverage &