Module 6 Planning Details

UMTS Radio Network Planning
Fundamentals
(FDD mode, R2/R3)
Prerequisites:
GSM Radio Network Engineering
Fundamentals
Introduction to UMTS
UMTS Radio Network Planning Fundamentals
Table of content
1. Introduction
2. Inputs for Radio Network Planning
3. Link Budget (in Uplink) and Cell Range Calculation
4. Initial Radio Network Design
5. Basic Radio Network Parameter Definition
6. Basic Radio Network Optimization
7. UMTS/GSM co-location and Antenna Systems
Appendix
Abbreviations and acronyms
2

Duratio
n:
2h30
1. Introduction
1. Introduction
Session presentation
Objective:
to get the necessary background information in
regards of UMTS basics and RNP principles for a
good start in UMTS Radio Network Planning.
Program:
1.1
UMTS Basics
1.2
UMTS RNP notations
1.3
UMTS RNP tool overview
1.4
UMTS RNP process overview
All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04
1. Introduction
1.1
UMTS Basics
Objective:
to be able to describe the UMTS network

architecture and main radio mechanisms
1.1
UMTS Basics
UMTS network architecture(1)

Entities and interfaces
Uu
(air)
Iu
Node B
Iu-CS
Iub
USIM
Node B
RNC
MSC/VLR
GMSC
PLMN, PSTN,
ISDN, ...
RNS
HLR
Iur
Cu
Node B
ME
Iub
Node B
UE
User
Equipmen
t
RNC
RNS
UTRAN
UMTS Radio
Access
Network
SGSN
GGSN
IP
networks
CN
External Networks
Iu-PS
Core Network
1.1
UMTS Basics
UMTS network architecture(2)

A1353 OMC-UR
Alcatel OMC-UR
architecture
RNO
+
NPA
A9155
RNP tool
LAN
ItfB
NM
A9100
MBS
Note: the
Alcatel
NodeB is
called
A9100
MBS
(Multistandard
Base
Station)
from R2
onwards
A9140
RNC
A9100
MBS
RNS
A9100
MBS
Iub
A9100
MBS
A9140
RNC
RNS
UTRAN
ItfR
RNO
Radio Network Optimizer
NPA
Network Performance
Analyzer
NM
Network Manager (used to

perform supervision and
of onwards.
the UTRAN)
Note: NM configuration
is provided from R3
In R2,
the NM function are implemented in two
separate servers EM (Element Manager) and
SNM (Sub-network Manager)
7
1.1
UMTS Basics
3GPP: the UMTS standardization body

Members:
ETSI (Europe)
ARIB/TTC (Japan)
T1 (USA)
TTA (South Korea)
CWTS (China)
UMTS system specifications:

Access Network
WCDMA (UTRAN FDD)
TD-CDMA (UTRAN TDD)
Core Network
Evolved GSM
All-IP
Note: 3GPP has also taken over the GSM recommendations (previously written by
ETSI)
Releases defined for the UMTS system specifications:

Release 99 (sometimes called Release 3)
(former Release 2000)
Release 4
Release 5
In the following material we will only deal with UMTS FDD R99.
1.1
UMTS Basics
3GPP UMTS specifications

3GPP UMTS specifications are classified in 15 series (numbered from
21 to 35), e.g. the serie 25 deals with UTRAN aspects.
Note: See 3GPP 21.101 for more details about the numbering
scheme and an overview about all UMTS series and specifications.
Interesting specifications for UMTS Radio Network Planning:
3GPP TS 25.101:
"UE Radio transmission and Reception (FDD)"
3GPP TS 25.104:
"UTRA (BS) FDD; Radio transmission and Reception
3GPP TS 25.133:
"Requirements for support of radio resource management (FDD)"
3GPP TS 25.141:
"Base Station (BS) conformance testing (FDD)
3GPP TS 25.214:
"Physical layer procedures (FDD)".
3GPP TS 25.215:
3GPP TS 25.942:
er
d
un
d
n
f ou
be
n
ca org
"Physical layer - Measurements (FDD)
s
on gpp.
i
t
ca w.3
"RF system scenarios".
f
i
c
ww
pe
s
PP
G
3
1.1
UMTS Basics
Alcatel UTRAN releases

Alcatel UTRAN equipment (RNC, NodeB and OMC-UR) is designed by
a joint-venture between Alcatel and Fujitsu, called Evolium.
Note: the Alcatel UMTS equipment is called Evolium TM 9100 MBS,
EvoliumTM 9140 RNC and EvoliumTM 1353 OMC-UR
Relationship between Evolium UTRAN releases and 3GPP releases:
Evolium UTRAN
releases
3GPP releases
R1
R99
(former 3GR1)
(Technical Status December

2000)
R2
R99
(Technical Status June 2001)
R3
R99
(Technical Status March 2002)
R4
R4
R5
R5
Prevision
Stand:
June 2004
10
1.1
UMTS Basics
UMTS main radio mechanisms(1)

Sector/Cell/Carrier in UMTS
Sector and cell are not equivalent anymore in UMTS:
A sector consists of one or several cells
A cell consists of one frequency (or carrier)
Note: a given frequency (carrier) can be reused in each sector of
each NodeB in the network (frequency reuse=1)
11
1.1
UMTS Basics

CDMA (called W-CDMA for UMTS FDD) as access method on the air
a given carrier can be reused in each cell (frequency reuse=1)no
FDMA
all active users can transmit/receive at the same timeno TDMA
As a consequence, there are inside one frequency:
Extra-cell interference: cell separation is achieved by codes
(CDMA)
Intra-cell interference: user separation is achieved by codes
(CDMA)
Multiple frequencies (carriers)

first step of UMTS deployment: a single
frequency (e.g. frequency 1) is used for the

whole network of an operator
second step of UMTS deployment:
additional frequencies can be used to
enhance the capacity of the network: an
additional frequency (e.g frequency 2) works
as an overlap on the first frequency.
Frequency 2
Frequency 1
12
1.1
UMTS Basics
Physical channels
Channelization and scrambling codes (UL side)

Bit rateA
cch1
Bit rateB
cch 2
Bit rateC
.
.
.
UE
3.84 Mchips/s
3.84 Mchips/s
3.84 Mchips/s
3.84 Mchips/s
cscrambling
air
interfac
Modulato
e
r
cch 3
Channelization codes (spreading

codes)
short codes (limited number, but they
can be reused with another scrambling
code)
code length chosen according to the bit
rate of the physical channel (spreading
factor)
Scrambling codes
long codes (more than 1 million
available)
fixed length (no spreading)
1 unique code per UE assigned by
the RNC at connection setup
13
1.1
UMTS Basics
Physical channels
Channelization and scrambling codes (DL side)

Bit rateA
cch1
Bit rateB
cch 2
Bit rateC
.
.
.
NodeB
sector
3.84 Mchips/s
3.84 Mchips/s
3.84 Mchips/s
3.84 Mchips/s
cch 3
Channelization codes
(spreading codes)
same remarks as for UL
side
Note: the restricted number
of channelization codes is
more problematic in DL,
because they must be shared
between all UEs in the NodeB
sector.
cscrambling
air
interfac
Modulato
e
r
Scrambling codes
long codes (more than 1 million available,
but restricted to 512 (primary) codes to limit
the time for code research during cell
selection by the UE)
fixed length (no spreading)
1(primary) code per NodeB sector defined
by a code planning: 2 adjacent sectors shall
have different codes (see 5)
Note: it is also possible to define secondary
scrambling codes, but it is seldom used.
14
1.1
UMTS Basics

Physical channels
Physical channels are defined mainly by:
a specific frequency (carrier)
a combination channelization code / scrambling code
used to separate the physical channels (2 physical channels
must NOT have the same combination channelization code /
scrambling code)
start and stop instants
physical channels are sent continuously on the air interface
between start and stop instants
Examples in UL:
DPDCH: dedicated to a UE, used to carry traffic and signalling between UE
and RNC such as radio measurement report, handover command
DPCCH: dedicated to a UE, used to carry signalling between UE and
NodeB such as fast power control commands
Examples in DL:
DPCH: dedicated to a UE , same functions as UL DPDCH and UL DPCCH
P-CCPCH: common channel sent permanently in each cell to provide
system- and cell-specific information, e.g. LAI (similar to the time slot 0
used for BCCH in GSM)
15
1.1
UMTS Basics

CPICH (or Pilot channel)
DL common channel sent permanently in each cell to provide:
srambling code of NodeB sector: the UE can find out the DL
scrambling code of the cell through symbol-by-symbol
correlation over the CPICH (used during cell selection)
power reference: used to perform measurements for
handover and cell selection/reselection (function performed
by time slot 0 used for BCCH in GSM)
time and phase reference: used to aid channel estimation
in reception at the UE side
The CPICH contains:
Pre-defined symbol sequence
a pre-defined symbol sequence

(the same for each cell of all UMTS
networks) scrambled with the NodeB
sector scrambling code
at a fixed and low bit rate
(Spreading Factor=256): to make
easier Pilot detection by UE
Tslot = 2560 chips , 20 bits = 10 symbols
Slot #0
Slot #1
Slot #i
Slot #14
1 radio frame: Tf = 10 ms
16
1.1
UMTS Basics

Power control
Near-Far Problem: on the uplink way an overpowered mobile
phone near the base station (e.g. UE1) can jam any other
mobile phones far from the base station (e.g. UE2).
UE1
Node
B
UE2
an efficient and fast power control is necessary in UL to

avoid near-far effect
power control is also used in DL to reduce interference and
consequently to increase the system capacity
Power control mechanisms (see Appendix for more details):
open loop (without feedback information) for common
physical channels
closed loop (with feedback information) for dedicated
physical channels (1500 Hz command rate, also called fast
power control)
17
1.1
UMTS Basics

Soft/softer Handover (HO)
a UE is in soft handover state if
there are two (or more) radio links
between this UE and the UTRAN
it is a fundamental UMTS
mechanism (necessary to avoid
near-far effect)
only possible intra-frequency, ie
between cells with the same
frequency
Note: hard handover is provided if
soft/er handover is not possible
A softer handover is a soft
handover between different sectors
of the same Node B
RNC
Node B
Node B
UE
Soft handover
(different sectors of different NodeBs)
RNC
Node B
UE
Softer handover
(different sectors of the same NodeB)
18
1.1
UMTS Basics

Active Set (AS) and Macro Diversity Gain
All cells, which are involved in soft/softer handover for a given
UE belong to the UE Active Set (AS):
usual situation: about 30% of UE with at least 2 cells in
their AS.
up to 6 cells in AS for a given UE
The different propagation paths in DL and UL lead to a diversity
gain, called Macro Diversity gain:
UL
one physical signal sent by one UE and received by
two different cells
soft handover: selection on frame basis (each 10ms) in
RNC
softer handover: Maximum Ratio Combining(MRC) in
NodeB
DL
two physical signals (with the same content) sent by
two different cells and received by one UE
19
1. Introduction
1.2
UMTS RNP notations and principles

Objective:
to be able to understand the vocabulary and

notations* used in this course in regards of
UMTS planning
* unfortunately, UMTS RNP notations are not

clearly standardized, so that the meaning of a
notation can be quite different from one
reference to another one.
20
1.2
Received power and

power density
Received (useful)
signal
Thermal Noise
Thermal Noise at
receiver
Interference intra-cell
Power
[dBm]
Power
Density
[dBm/Hz]
-108.1
Iintra
(Iown)
(Iother;Iinte
Comment
(Power Density=Power/B
with B=3.84MHz)
Ec
Nth=-174
Nth = k.T0 with k=1.38E-20mW/Hz/K

(Bolztmann constant) and T0=293K
(20C)
N =-108.1dBm+NFreceiver [dB]
(=Thermal noise + Noise generated
at receiver)
interference received from

transmitters located in the same cell
as the receiver
Note: C is included in Iintra
Iextra
Interference extra-cell
Notations (1)
Ec = Energy per chip=C/B
C
(or
RSCP)
interference received from

transmitters not located in the same
21
cell as the receiver
1.2
Received power
and power density
Power
[dBm]
Total received power

(Total noise)
I+N
Total received power

(Total noise without
useful signal)
Power
Density
[dBm/Hz]
(RSSI)
I+N-C
Io
Notations (2)
Comment
Power Density=Power/B with
B=3.84MHz
I+N= Iintra+ Iextra +N
Note: C is included in (I+N)
No
No=( Iintra+ Iextra +N-C)/B
(Nt)
Note: C is not included in No
Note: Io can be measured with a good precision, whereas No is not

easy to measure (but it is useful for theoretical demonstrations)
22
1.2
Ratio
in [dB]
Ec/Io
Received
energy per
chip over
noise
Ec/No
(C/I)*
Received
energy per
bit over
noise
Required
energy per
bit over
noise
Eb/No
(Eb/No)req
Notations (3)
Comment
Here noise=Io
This ratio can be accurately measured: it is used for
physical channels without real information bits,
especially for CPICH (Pilot channel)
Here noise=No
This ratio is difficult to measure, but is useful for
theoretical demonstrations: it is used for physical
channels with real information bits, especially for PCCPCH and UL/DL dedicated channels.
Eb/No=Ec/No+PG with PG (Processing Gain) = 10 log
[(3.84 Mchips/s) / (service bit rate)]
e.g. for speech 12.2 kbits/s, Processing Gain = 25dB
Fixed value which depends on service bit rate...(see
3.5)
Eb/No shall be equal or greater than the (Eb/No)req
*This ratio is often written with the classical GSM notation C/I (Carrier over Interference ratio): this
notation is incorrect, it should be C/(I+N-C)
23
1.2
Two more
interesting in [dB]
ratios!
f
(or little i)
Noise Rise
Iextra / Iintra
(I+N)/N
Notations (4)
Comment
In a homogenous network (same traffic and user
distribution in each cell), f is a constant in uplink.
Typical value for macro-cells with omni-directional
antennas: 0.55 (in uplink)
Very useful UMTS ratio to characterize the moving
interference level I compare to the fixed Thermal
Noise at receiver level N.
24
1.2
Exercise (1/2)
Surrounding cells
link
p
U
de
i
s
on
red
Serving cell
Node
B
Assumptions:
-
n active users in the serving cell with speech service at 12.2kbits/s

and (Eb/No)req =6 dB
Received power at NodeB: C=-120dBm (for each user)
homogenous network (f=0.55)
NFNodeB = 4dB and NFUE =8dB
25
1.2
Exercise (2/2)
1. What is the processing gain for speech 12.2kbits/s ?

2. The users in the serving cell are located at different distance from the
NodeB: is it desirable and possible to have the same received power C for
each user?
3. What is the value of the Thermal Noise at receiver N?
4. nComplete the following table:
[users
]
I +N
[dBm]
[dBm]
Noise
Rise
[dB]
Ec/No
Eb/No
[dB]
[dB]
Comment
1
10
25
100
26
1. Introduction
1.3
UMTS RNP Tool Overview

Objective:
to be able to describe briefly the structure of a

RNP tool
27
1.3
RNP tool requirements(1)

Digital maps
topographic data (terrain height)
Resolution:
typically 20m for city areas and 50 m for rural areas
possibly building and road databases for more accuracy
Coordinates system
important for interfacing with measurement tools
e.g. UTM based on WGS-84 ellipsoid
morphographic data (clutter type)

Resolution: same as topographic data
Propagation model dialog

e.g. setting Cost-Hata propagation model parameters (see 3.2)
Site/sector/cell/antenna dialog
importing sites (e.g GSM sites)
setting site/sector/cell/antenna parameters (Network design
parameters, see 4.1)
Note: in UMTS, sector and cell are not equivalent
28
1.3
RNP tool requirements(2)

Link loss calculation
Traffic simulation
Setting traffic parameters (2.2)
Traffic map generation
Resolution: same as topographic data
UE list generation (a snapshot of the UMTS network)

Coverage predictions
displaying the results on the map
showing the results as numerical tables
Automatic neighborhood planning
Automatic scrambling code planning
Interworking with other tools (dimensioning tools, OMC-UR,
measurements tools, transmission planning tool...)
29
1.3
Example: A9155 UMTS/GSM RNP tool
A9155
screensho
t
30
1. Introduction
1.4
RNP Process Overview

Objective:
to be able to describe briefly the 11 steps of

the RNP Process, which starts with Radio
Network Requirements definition and ends with
Radio Network Acceptance.
31
1.4
The 11 steps of RNP process

1. Radio Network
Requirements (see 2.4)
2. Preliminary Network
Design
(see 3)
3. Project Setup and
Management
4. Initial Radio Network
Design
(see 4)
5. Site Acquisition
Procedure
6. Technical Site
Survey
7. Basic Parameter
Definition
(see 5)
8. Cell Design CAE Data
Exchange over COF
9. Turn On Cycle
10. Basic Network
Optimization
(see 6)
11. Network
Acceptance
(12. Further
Optimization)
32
1.4
Step 1: Definition of Radio Network Requirements

The Request for Quotation (RfQ) from the operator prescribes the
requirements which consists mainly in:
Coverage
Traffic
QoS
see 2.4 for more details
33
1.4
Step 2: Preliminary Network Design

The preliminary design lays the
foundation to create the Bill of
Quantity (BoQ)
List of needed network
elements
Geo data procurement
Digital Elevation Model
DEM/Topographic map
Clutter map
Definition of standard equipment
configurations dependent on
clutter type
traffic density
Definition of roll out phases

Areas to be covered
Number of sites to be
installed
Date, when the roll out
takes place.
Network architecture design
Planning of RNC, MSC and
SGSN locations and their
links
Frequency spectrum from
license conditions
34
1.4
Step 3: Project Setup and Management

This phase includes all tasks to be performed before the on site part
of the RNP process takes place.
This ramp up phase includes:
Geo data procurement if required
Setting up general rules of the project
Define and agree on reporting scheme to be used
Coordination of information exchange between the
different teams which are involved in the project
Each department/team has to prepare its part of the project
Definition of required manpower and budget
Selection of project database (MatrixX)
35
1.4
Step 4: Initial Radio Network Design

Area surveys
As well check of correctness of geo data
Frequency spectrum partitioning design
RNP tool calibration
For the different morpho classes:
Performing of drive measurements
Calibration of correction factor and standard deviation by
comparison of measurements to predicted received power
values of the tool
Definition of search areas (SAM Search Area Map)
A team searches for site locations in the defined areas
The search team should be able to speak the national language
Selection of number of sectors/cells per site together with project
management and operator
Get real design acceptance from operator based on coverage
prediction and predefined design level thresholds
36
1.4
Step 5: Site Acquisition Procedure

Delivery of site candidates
Several site candidates shall be
the result out of the site location
search
Find alternative sites
If no site candidate or no
satisfactory candidate can be
found in the search area
Definition of new SAM (Search Area
Map)
Possibly adaptation of radio
network design
Check and correct SAR (Site Acquisition
Report)
Location information
Land usage
Object (roof top, pylon, grassland)
information
Site plan
Site candidate acceptance and ranking

If the reported site is accepted as
candidate, then it is ranked
according to its quality in terms of
Radio transmission
High visibility on
covered area
No obstacles in the
near field of the antennas
No interference from
other systems/antennas
Installation costs
Installation possibilities
Power supply
Wind and heat
Maintenance costs
Accessibility
Rental rates for object
Durability of object
37
1.4
Step 6: Technical Site Survey

Agree on an equipment installation
solution satisfying the needs of
RNE (Radio Network Engineer)
Transmission planner
Site engineer
Site owner
The Technical Site Survey Report
(TSSR) defines
Antenna type, position,
orientation and tilt
Mast/pole or wall mounting
position of antennas
EMC rules are taken into
account
Radio network engineer
and transmission planner
check electro magnetic
compatibility (EMC) with
other installed devices
BTS/Node B location
Power and feeder cable mount
Transmission equipment
installation
Final Line Of Site (LOS)
confirmation for microwave
link planning
E.g. red balloon of around
half a meter diameter
marks target location
If the site is not acceptable or the
owner disagrees with all suggested
solutions
The site will be rejected
Site acquisition team has to
organize a new date with the
next site from the ranking list
38
1.4
Step 7: Basic Parameter Definition

After installation of equipment the
basic parameter settings are used for
Commissioning
Functional test of
BTS/NodeB and VSWR check
Call tests
RNEs define cell design data
Operations field service generates the
basic software using the cell design
CAE data
Cell parameters definition

LAC/RAC...
Frequencies
Neighborhood/cell
handover relationship
Transmit power
Cell type (macro, micro,
umbrella, )
Scrambling code planning
39
1.4
Step 8: Cell Design CAE Data Exchange over COF
ACIE
A956
A956 RNO
RNO
A9155 V5/V6 RNP
OMC 1
COF
A9155
PRC Generator
Conversion
3rd Party RNP

or Database
ACIE
OMC 2
ACIE = PRC file

POLO
BSS Software offline production
40
1.4
Step 9: Turn On Cycle(1)

The network is launched step by step during the Turn On Cycle.
A single step takes typically two or three weeks
Not to mix up with rollout phases, which take months or even
years
For each step the RNE has to define Turn On Cycle Parameter
Cells to go on air
Cell design CAE parameter
Each step is finished with the Turn On Cycle Activation
Upload PRC/ACIE files into OMC-R
Unlock sites
41
1.4

Site Verification and Drive Test
RNE performs drive measurement to compare the real
coverage with the predicted coverage of the cells.
If coverage holes or areas of high interference are detected
Adjust the antenna tilt and orientation
Verification of cell design CAE data
To fulfill heavy acceptance test requirements, it is absolutely
essential to perform such a drive measurement.
Basic site and area optimization is preventing to have
unforeseen mysterious network behavior afterwards.
42
1.4

HW / SW Problem Detection
Problems can be detected due to drive tests or equipment
monitoring
Defective equipment
will trigger replacement by operation field service
Software bugs
Incorrect parameter settings
are corrected by using the OMC or in the next TOC
Faulty antenna installation
Wrong coverage footprints of the site will trigger antenna
re-alignments
If the problem is serious
Lock BTS/NodeB
Detailed error detection
Get rid of the fault
Eventually adjusting antenna tilt and orientation
43
1.4
Step 10: Basic Network Optimization

Network wide drive measurements
It is highly recommended to perform network wide drive tests
before doing the commercial opening of the network
Key performance indicators (KPI) are determined
The results out of the drive tests are used for basic
optimization of the network
Basic optimization
All optimization tasks are still site related
Alignment of antenna system
Adding new sites in case of too large coverage holes
Parameter optimization
No traffic yet -> not all parameters can be optimized
Basic optimization during commercial service
If only a small number of new sites are going on air the basic
optimization will be included in the site verification procedure
44
1.4
Step 11: Network Acceptance

Acceptance drive test
Calculation of KPI according to acceptance requirements in contract
Presentation of KPI to the operator
Comparison of key performance indicators with the acceptance
targets in the contract
The operator accepts
the whole network
only parts of it step by step
Now the network is ready for commercial launch
45
1.4
(Step 12: Further Optimization)

Network is in commercial operation
Network optimization can be performed
Significant traffic allows to use OMC based statistics by using A956
RNO and A985 NPA
46

Duratio
n:
2h00
2. Inputs for Radio Network

Planning
47
Objective:
to be able to describe the UMTS RNP inputs in
regards of frequency spectrum, traffic parameters,
equipment parameters and radio network
requirements
Program:
2.1
UMTS FDD frequency spectrum
2.2
UMTS traffic parameters
2.3
UMTS Terminal, NodeB and Antenna
overview
2.4
UMTS Radio Network Requirements
48
2.1

Objective:
to be able to describe the UMTS FDD

frequency parameters defined by the 3GPP
49
2.1
Frequency spectrum
Frequency spectrum (UMTS FDD mode)

UL: 1920 MHz 1980 MHz
DL: 2110 MHz 2170 MHz
Duplex spacing: 190 MHz
1920-1980
2110-2170
50
2.1
Carrier spacing
Carrier spacing: 5MHz

2110 MHz 2170 MHz = 60 MHz; 60 MHz / 5 MHz =12
frequencies
One operator gets typically 23 frequencies (carriers)
So typically 46 licenses per country as a maximum
Required bandwidth: 4.7MHz
The chip rate is 3.84Mchip/s, therefore at least 3.84MHz bandwidth are needed
to avoid inter-symbol interference (Nyquist-Criterion)
The roll-of factor of the pulse-shaping filter is 0.22 (root-raised cosine)
The needed minimum bandwidth is 3.84MHz x 1.22 4.7MHz
Examples:
60MHz
6 operators
5MHz
4 operators
51
2.1
Frequency channel numbering

UTRA Absolute Radio Frequency Channel Number (UARFCN)
UARFCN formula (3GPP 25.101 and 25.104):
UARFCNUplink/Downlink 5 f Center Uplink/Downlink [MHz]

with
0.0 MHz f Center Uplink/Downlink 3276.6 MHz
UARFCN is integer:
0 <= UARFCN <= 16383
52
2.1
Center Frequency
Center Frequency fcenter

Consequence of UARFCN formula (see previous slide):
fcenter must be set in steps of 0.2MHz (Channel Raster=200
kHz)
fcenter must terminate with an even number (e.g 1927.4 not
1927.5)
fcenter values
Uplink (1920Mhz-1980MHz)
1922.4MHz <= fcenter <= 1977.6MHz
9612 <= UARFCN Uplink <= 9888

Downlink (2110Mhz-2170MHz)
2112.4MHz <= fcenter <= 2167.6MHz
10562 <= UARFCN Downlink <= 10838
53
2.1
Further comments
Frequency adjustment
If an overlap between frequency bands belonging to same
operator is set, guard band between different operators will
increase.
This feature can be used to enlarge the guard band between
frequency blocks belonging different operators and prevent
dead zones.
Example:
5 MHz
it shows an overlap5 of
0.3 MHz between two carriers of one operator0.6 MHz
MHz
additional channel separation
between the operators is created.
0.3 MHz overlap
4.7 MHz
4.7 MHz
Operator 1
1920
0.3 MHz overlap
Operator
2
1940
0.6 MHz additional

guard band
Frequency coordination at country borders (see Appendix)

54
2.2
UMTS traffic parameters (UMTS traffic map)

Objective:
to be able to describe the method to create a

traffic map
55
2.2
Step 1: Terminal parameters

Terminal parameters
Tx power
(dBm)
(typical values)
Min
Max
Antenna
Gain
(dB)
Deep Indoor
15
Incar
8
-50
Deep Indoor
Indoor
Personal Digital
Assitent (PDA)
Active
set
size
18
21
Indoor First Wall
Outdoor
Noise
Factor
(dB)
20
Indoor
Mobile phone
Internal
Losses+
Indoor
Margin
(dB)
Indoor First Wall
0
20
24
18
15
Incar
Outdoor
The indoor margin (also called penetration loss) is part of

UE parameters.
56
2.2
UL
DL
Speech 12.2
CS 64
PS 64
PS 128
PS 384
DL
CS
see next page
Y
PS
2
1
0
0
12.
2
64
64
64
64
12.2
64
64
128
384
DL traffic
Power (dBm)
Min
Max
Body loss
(dB)
UL
DL
Activity Factor
(UL/DL)
UL
Coding Factor
UL/ DL
120 km/ h
DL nominal rate
(Kb/ sec)
50 km/h
UL nominal rate
(Kb/ sec)
3 Km/h
Priority
(typical
values)
(Eb/No)req (dB)
Type
Service
parameters
SHO allowed
Step 2: Service parameters(1)
0.6
1
3
-50
+40
Activity factor and Body loss are part of service parameters
57
2.2
Step 2: Service parameters(2)

(Eb/No)req typical values
PS services for a target BLER of 0.05
fixed values which depends on link

PACKET 64
direction (UL or DL )service bit rate,
BLER (or BER), UE speed, UE multipath
Vehicular A - 3 km/h
environment, TX/RX diversity and
processing/hardware imperfection
margin
(2dB)
Speech services for a target BLER of 0.01(10-2)
SPEECH 12.2
Uplink Downlink
2 rx ants
1 tx ant
5,8
6,2
7,1
7,6
8,1
8,7
CS services for a target BLER of 0.0001 (10-4)

CIRCUIT 64
Uplink Downlink
2 rx ants
1 tx ant
3,2
3,5
4,4
6,2
6,5
7,1
PACKET 128
Uplink Downlink
2 rx ants
1 tx ant
2,8
3,2
4,2
5,5
6,2
6,7
Uplink Downlink
2 rx ants
1 tx ant
2,1
2,5
3,4
4,8
5,5
6,1
Uplink Downlink
2 rx ants
1 tx ant
PACKET 384
1,8
2,2
3,0
5,2
6,1
6,8
Source: Alcatel simulations

58
2.2
Step 3: User Profile parameters

Traffic Density
User Profle
(Examples)
Service
(see Step2)
Terminal
(see Step1)
Calls/
hour
Duration
(sec)
Volume
(Kb/sec)
UL
DL
Surfing user
PS 384
PDA Deep Indoor
60
Videocall user
PS 64
PDA Deep Indoor
20
Phonecall user
Speech 12.2
Mobile phone Deep

Indoor
115.2
Speech 12.2
72
CS64
72
0.2
40
200
City user
PS64
Mobile Phone Outdoor
PS128
PS384
Standard user
same as City User without PS384 service
All of this data has to be provided by the operator: as the user profiles
will be different for different operators in different countries, no typical
values can be given.
59
2.2
Step 4: Environment Class parameters

User profiles have been used to describe single user types.
Environment classes are used to distribute and quantify these user
profiles on the planning area.
Environment User profles
(see Step
class*
(Examples)
3)
Geographical density (users/km2)

low
traffic
medium
traffic
high traffic
Dense Urban
city user
1000
3000
6000
Urban
city user
750
1500
3000
Suburban
city user
50
250
500
standard user
10
20
40
Rural
*BE CAREFUL: environment classes and clutter classes have often the same names,
although they refer to quite different concepts: an environment class refers to a
traffic property whereas a clutter class refers to an electromagnetic wave propagation
property. The reason is that environment classes are very often mapped on clutter
classes to generate a traffic map (see Step 5)
60
2.2
Step 5: Traffic Map definition

Mapping of Environment Classes (see Step 4) on a map:
Example with 4 environment classes: Dense Urban, Urban,
Rural
Suburban, Rural
Traffic
map
Map
Suburban
Dense Urban
Planning Area
(also called Focus Area)
Resolution:
20m100m
Urban
Note: an easy way to generate a traffic map is to use the clutter map and to
associate each clutter class to an environment class (e.g. Dense Urban environment
class is mapped on Dense Urban clutter class)
61
2.3
UMTS Terminal, NodeB and Antenna overview

Objective:
to be able to describe briefly the main

characteristics of the UMTS radio equipment
(UE, Alcatel NodeB and antenna)
62
2.3
UE characteristics
According to 3GPP 25.101 (Release 1999):

UE power classes at antenna connector*:
Power class 1: (+33 +1/-3)dBm
Power class 4: (+21 2)dBm
UE minimum output power: <-50dBm
According to UE manufacturers:
UE Noise Figure: 8dB (typically)
UE internal losses + UE antenna gain = 0dB
What is EIRP for a UE of power class 4?
Answer:
UE EIRP=UE TX Power+ UE Antenna Gain - UE Internal Loss=21dBm + 0 dB = 21 d
* the notation means e.g. for

class 1:
- Maximum output power:
+33dBm
- Tolerance: +1dBm/-3dBm
63
2.3
Alcatel NodeB(1)
The EVOLIUMTM Alcatel 9100 MBS (=Alcatel NodeB)

is a multi-standard base station, which can handle the UMTS and GSM
functions
is available in 3 types of configurations: UMTS only, GSM only, mixed
UMTS/GSM
is available from UTRAN Release 2 (R2) onwards*
UMTS
The UMTS part is a
Iub
UE
part
Node_B in charge of
radio transmission
GSM
part
A-bis
handling (with W-CDMA
UE
RNC
method)
MBS
UE
UMTS
part
The GSM part is a BTS in

charge of radio
transmission handling
(with FDMA/TDMA
method)
Iub
GSM
part
MBS
A-bis
BSC
* in UTRAN release 1 (former 3GR1) there was the Alcatel NodeB V1. This product is no more
produced and no more supported from UTRAN R3 onwards.
64
2.3
Alcatel NodeB (2)
DL
RF
UL
UMTS
Part
TMA
TEU
ANRU
BASE BAND
COMMON
BB
Option
Iub
BB
SUMU
TMA
ANRU
TEU
Option
BB
2 antennas per
sector:
-necessary due to
RX diversity
-can also be used
with optional TX
diversity
GSM
Part
up to 4 E1 interfaces
(2Mbits/s) on Iub
(hardware limit)
only 4 types of modules for the MBS: SUMU, BB, TEU and ANRU
65
2.3
RF
TMA
ANRU
TEU
Alcatel NodeB (3)
BASE BAND
COMMON
BB
Option
Iub
BB
SUMU
TMA
ANRU
TEU
Option
Functions: pool of processing resources

to be shared between all cells of the MBS
for UL/DL channel coding, interleaving,
spreading, scrambling, power control
(inner loop), softer handover
Capacity:
64 speech channels (AMR) or 1536
kbits/s per BB board*
number of boards depends on the
required traffic capacity ( not on the
number of sectors)
BB
Functions: O&M (alarm,
software), clock, transmission
towards RNC
Capacity:1 SUMU board per MBS
* Soft/softer handover overhead capacity has
already been taken into account in these
figures.
BB board dimensioning rule for mixed traffic:
K + L + M + N < 64 user channels
K x 12.2 kbps + L x 64 kbps + M x 128 kbps +
N x 384 kbps < 1536 kbps
Where
K = number of speech12.2kbps users
L = number of 64 kbps channel users
M = number of 128 kbps channel users
N = number of 384 kbps channel users
66
2.3
RF
TMA
TEU
ANRU
Alcatel NodeB (4)
BASE BAND
COMMON
BB
Option
Iub
BB
SUMU
TMA
ANRU
TEU
Option
Functions: UL/DL
filtering and
duplexing, and UL
multi-carrier low
noise amplification
Capacity:
as many ANRU as
number of sectors
NF(Noise
Figure)=4dB
BB
Functions: DL multi-carrier modulation and DL multicarrier power amplification

Capacity:
1 TEU board per sector (2 per sector with optional TX
diversity )
TEU output power at antenna connector:
20 W (43 dBm) for TEUM
35 W (46 dBm) for TEUH (only available from R3
onwards)
Note: the output power is shared between all the carriers
of one sector (symmetrically or asymmetrically).
67
2.3
Alcatel NodeB (5)
MBS hardware limits (due to number of connectors, space

constraints)
up to 6 sectors and up to 24 cells per MBS
up to 4 carriers (cells) per sector
up to 13 BB boards per MBS
MBS limits in R2
up to 1 carrier (cell) per sector
MBS limits in R3 (Stand: June 2004)
up to 3 carriers (cells) per sector
68
2.3
UMTS antennas (1)
Constraints for antenna system installation:

visual impact
space or building constraints
co-siting with existing GSM BTS (see 7)
Note: the antenna system includes not only the antennas themselves, but
also the feeders, jumpers and connectors as well as diplexers (in case of
antenna system sharing) and TMAs (tower mounted amplifiers)
Whenever possible, a solution with a standard antenna has to be

chosen:
Model: 65 horizontal beam width
Azimuth: 0, 120 and 240 (3 sectored site)
Gain: 17-18dBi
Height (above ground): 20-25 m for urban and 30-35 m for
suburban
Downtilt: electrical downtilt adjustable between 0 and 10
69
2.3
UMTS antennas (2)
Antenna parameters are key parameters which can be tuned to

decrease interference in critical zones, especially:
Antenna downtilt
by increasing the antenna downtilt of the interfering cell
downtilt changes with a difference less than 2 compared
to the previous value do not make sense, since the
modification effort (requiring on-site tuning) does not stand
in relation to the effect.
rule of thumb: the downtilt in UMTS should be at least 1-2
higher than the value a planner would chose for GSM
Antenna azimuth
by re-directing the beam direction of the interfering cell
azimuth modifications of 10-20 compared to the
previous value do not make sense
Note: Azimuth/downtilt modifications can be restricted or even forbidden
due to antenna system installation constraints (especially the constraints for
UMTS/GSM co-location, see 7 for more details)
70
2.4
Radio Network Requirements

Objective:
to be able to understand the parameters,

which define the UMTS radio network
requirements in terms of coverage, traffic and
quality of service
71
2.4
Definition of radio network requirements (1)

Traffic mix and distribution for traffic simulation with the aim to
predict power load in DL and UL noise rise (see 2.2)
Covered area
Polygon surrounding the area to be covered (focus zone for
RNP tool)
Definition of what coverage is
CPICH Ec/Io coverage
(CPICH Ec/Io)required=-15dB (Alcatel value coming from
simulations and field measurements)
Required coverage probability for CPICH Ec/Io:
e.g. Average probability {CPICH Ec/Io > (CPICH Ec/Io) req} >
95%
*other definitions of required coverage probability are possible,
(with this definition
minimum
quality
in the
e.g. 95% ofaarea
with CPICHaverage
Ec/Io > (CPICH
Ec/Io) required
covered area
is this
guaranteed*)
(with
definition, a minimum percentage of covered area is
guaranteed)
72
2.4

UL and DL service coverage
(Eb/No)reqspecific value for each service and for each direction (UL/DL), see 2.2
Required coverage probability for DL and UL services:
e.g. Average probability {Eb/No > (Eb/No) req} > 95% (for each direction UL/DL and for each
service)
Note: It is possible to define different required coverage probabilities for different services.
Eb/No values can not easily be measured, but nevertheless service coverage predictions are a good
source of information to improve the radio network design (to find the limiting resources).
73
2.4

CPICH RSCP coverage (optional)
(CPICH RSCP)required: it can be defined, if the maximum
allowed path loss is determined by calculating a link
budget and taking into account the CPICH output power (if
no traffic mix is available, the link budget would base on
the limiting service)
Required coverage probability for CPICH RSCP
e.g. Average probability {CPICH RSCP > (CPICH
RSCP)req}>95%
(To guarantee an average reliability, that the minimum
level is fulfilled in the covered area)
CPICH RSCP prediction is not mandatory, but:
it can be a help to guarantee a certain level of indoor
coverage from outdoor cells, taking into account
different indoor losses for different areas.
CPICH RSCP can easily be measured using a 3G
scanner.
74

Duratio
n:
4h00
3. Link Budget (in Uplink) and Cell

Range Calculation
75
Objective:
to be able to calculate the cell range for a given
service by doing a manual link budget in UL.
to be able to describe the typical UMTS radio effects
in UL and in DL.
Program:
3.1
Inputs for a manual UL link budget
3.2
UMTS propagation model
3.3
UMTS shadowing and fast fading modeling
3.4
Calculation of Node B reference sensitivity
3.5
UMTS interference modeling
3.6
Calculation of cell range
76
3.1

Objective:
to be able to define the necessary inputs for

an UL link budget (in order to prepare cell
range calculation).
77
3.1
Principle for Cell Range calculation
We consider a link budget in UL (assuming that the coverage is UL limited).

It is known that:
the pathloss Lpath depends on the distance UE-NodeB d (see 3.2).
Lpath = MAPL for d=Cell Range.
We calculate MAPLk for the limiting service k in UL:
Reference_
MAPLk dB EIRP
sensitivit
yNodeB,k dBm
UE dBm
dB Gains dB
Margins dB Losses
EIRPUE
(see 2.3)
UE
Reference_sensitivityNodeB,k
s
gin
r
a
M
ses
s
o
L
ns
Gai
(see 3.4)
d=Cell Range
Node
B
78
3.1
Inputs for the UL link budget
Margins
Shadowing margin*
see 3.3
Fast fading margin
see 3.3
Interference margin
see 3.5
Losses
Feeders and connectorsNodeB
typically 3dB (it depends on the feeder

length..)
Body loss
see 2.2
Penetration loss (indoor

margin)
see 2.2
Gains*
Antenna gainNodeB
typically 18dBi
*Soft/softer handover gain is included in the shadowing margin (see
79
3.2

Objective:
to be able to describe the parameters

involved in UL/DL wave propagation.
to find out the relationship between the

pathloss and the distance UE-NodeB
80
3.2
How to calculate the Pathloss Lpath?

In UMTS radio environment, the propagation waves are subject to complex
mechanisms:
Free Space Propagation
Slow fading (Shadowing)
Reflections/Refractions/Scatterin
g
Fast Fading (Multipath fading)
Diffraction
For UMTS link budget calculations, we have to find out the value of the
Pathloss Lpath between the NodeB and the UE using:
The free-space formula:
It cannot be used in mobile networks such as UMTS, because the
Fresnel ellipsoid is obstructed in the environment of the UE over a
big distance (due to low height above the ground of the UE).
Empirical formulas:
The most effective approach is based on the classical COST231Hata formula, extended for the usage on higher frequencies or
additional propagation effects.
e.g. Alcatel selected as UMTS propagation model a slightly modified
COST 231-Hata model, called the Standard Propagation Model*.
*see Appendix for the relationship between COST231- Hata and the Alcatel Standard
Propagation Model
81
3.2
Alcatel Standard Propagation Model

Lpath formula:
Lpath
K1 K 2 log d K 3 log H NodeBeff K 4 f (diffraction)
K 5 log d log H NodeBeff K 6 f ( H UEeff ) K clutter f clutter
with*
d : distanceNodeB- UE (m)
HNodeBeff : effective
antennaheightof NodeB(m)
HUEeff : effective
antennaheightof UE (m)
*see next slides for the values of the 7
multiplying factors K1, ..., K6, Kclutter and
the calculations of the 3 functions
f(diffraction), f(HUEeff), f(clutter)
Important: this formula takes into account

free space propagation, reflections /refractions/scattering and
diffraction
not slow and fast fading effects (never considered in
propagation model, but as margins see 3.3)
82
3.2

Can we consider for the antenna height in the Lpath formula the
height above the sea? the height above the ground?
What is the effective antenna height of NodeB and UE?
Typical values for the antenna height of NodeB and UE above
the ground level are:
HNodeB above ground = 20-25 m for urban and 30-35 m for suburban
HUE above ground = 1.5 m
These values and the topographic information between NodeB
and UE are used to calculate an effective antenna height HNodeB
eff and HUE eff , in order to model the real effect of antenna height
on the pathloss.
The effective height and the height above the ground :
are equal on a flat terrain (of course)
can be very different on a hilly terrain
Answer:
Height above the sea: no (Mexico isnt better than Shanghai due to its higher altitude!)
Height above ground: it is can be a strong approximation on a hilly terrain. Indeed assume a 20 m antenna is located on the top of a 500 m
hill. The height above ground is 20 m, but the antenna height shoud be 520 m.
83
3.2

Propagation model parameters (1)
Multiplying factors (directly derived from COST-Hata model)
Name
Value
Factor
related to
K1
23.6
(for f=
2140MHz)
constant
offset
K2
44.9
same comment as K1.
K3
5.83
HNodeB eff
same comment as K1.
K5
-6.55
d , HNodeB eff
same comment as K1.
K6
HUEeff
Comment
used to take into account free space propagation and
reflections/refractions/scattering mechanisms for a standard
clutter class.
same comment as K1. As the contribution of f(HUEeff) is close

to zero, K6 is set to zero.
84
3.2

Multiplying factors (not included in COST-Hata model)
Name
Value
Factor
related to
Comment
K4
f(diffracti
on)
used to take into account diffraction mechanisms see

further comments on f(diffraction).
Kclutter
f (clutter)
used to take into account the necessary correction compared to

the standard clutter class see further comments on
f(clutter).
85
3.2

clutter losses based on experienced values
1
2
3
4
5
6
7
8
9
10
Clutter Class*
buildings
dense urban
mean urban
suburban
residential
village
rural
industrial
open in urban
forest
Clutter
Loss-1.0
-3.0
-6.0
-8.0
-11.0
-14.0
-20.0
-14.0
-12.0
-9.0
11
parks
-15.0
12
open area
-24.0
13
water
-27.0
*BE CAREFUL: do not confuse clutter classes and environment classes (see 2.2)
86
3.2

Calculation of the diffraction loss f(diffraction)
Approximation: an obstacle of height H between NodeB and UE is
modeled as an infinite conductive plane of height H.
Case 1: one obstacle
h0
r
LOS
H
UE
Fresnel Ellipsoid
(first order)
Node
B
Infinite conductive plane
What is the diffraction loss in case 1 (use the curve on the

next page)?
Answer:
h0=r v=-1 f(diffraction)=14dB
87
3.2

Case 1: one obstacle (continuing)
Diffraction loss for one obstacle:
Knife-edge diffraction function
35
30
F(v) [dB]
25
20
15
10
5
0
-5
-9
-8
-7
-6
-5
-4
-3
-2
-1
Clearance of Fresnel ellipsoid (v)
v: clearance
parameter,
v=-h0/r
r: Fresnel ellipsoid
radius,
h0: height of obstacle
above line of sight
(LOS)
Note:
h0 = 0 v =0
88
3.2

Case 2: several obstacles
LOS
Node
B
UE
The diffraction loss in case 2 is not easy to calculate: it is

not equal to the sum of the contributions of each obstacle
alone (it is usually smaller).
Different calculations methods can be applied based on
the General method for one or more obstacles described in
ITU 526-5 recommendations, e.g Deygout, EpsteinPeterson or Millington
89
3.2

Calculation of f(clutter):
In the Lpath formula, the multiplying factors K1,..,K6 are
calculated for a standard clutter class: f(clutter) is a correction
factor compared to the standard clutter class.
f(clutter) is calculated taking into account a clutter loss*
average of all pixels located in the line of sight and in a circle
around the UE (the circle radius, called Max distance, is
*(also called200m).
clutter or morpho correction factor)
typically
Pixe
l
e
tanc
s
i
d
Max
UE
Forest clutter class pixel

clutter loss = -9 dB (typically)
Water clutter class pixel
clutter loss = -27 dB (typically)
Node
B
in this example, 3 pixels are

considered to calculate f(clutter)
90
3.2

Calculation of f(clutter):
How are provided the clutter loss values?
based on experienced values: simple, accuracy of +/-3 dB
(see previously)
based on calibration measurements: complex and
expensive way, but accuracy of +/-1 dB.
Is it possible to reuse GSM1800 calibration measurements(in
order to save costs of expensive measurement campaigns)?
The difference between 1850 MHz (middle of GSM1800 band)
and 2140 MHz (middle of DL UMTS FDD band) involves:
fixed offset of 0.9dB for all clutters taken into account in
K1:
K1=24.5 (COST-Hata value for f=2140MHz) 0.9dB = 23.6
no significant correction offset per clutter except if large
vegetation is penetrated
Conclusion: GSM 1800 calibrations can be reused. Only for
clutter type mainly covered by vegetation, additional
91
3.2

Calculation of f(clutter) (simplified*):
all the values are negative and are given compared to the
standard clutter class for which f(clutter) =0 dB (the worst
case)
Example:
Clutter Class
f(clutter)
(simplifed*)
Dense urban
-3
Urban
-6
Sub-urban
-8
Rural
*Assumption:
homogeneous
clutter class
around the UE
-20
92
3.2
Other Propagation Models
Other propagation models can be applied, especially for micro-cell

planning:
e.g. Walfish-Ikegami or Ray-Tracing
necessary to have building and road databases (expensive)
93
3.2
Alcatel Standard Propagation Model (simplified formula)

Exercise:
Lets consider the simplified* formula of the Alcatel Standard
Propagation Model:
Lpath[dB] = C1 + C2 x log(dUE-NodeB[km])
Can you complete the table?
*Assumptions:
-HNodeBeff=30m
-no diffraction
-homogeneous
clutter class
around the UE
Clutter
class
Dense
Urban
Suburba
n
dUENodeB
[km]
C1
[dB]
C2 x log(dUENodeB)
[dB]
Lpath
[dB]
0.5
1
2
0.5
1
2
94
3.3
UMTS shadowing and fast fading modeling

Objective:
to be able to find out the UL margins due to

fading effects (fast fading and shadowing)
to be able to describe the fading effects in

UL and in DL
95
3.3
UMTS shadowing and fast fading model
Definition of fading(1)
Lets consider a the received power level C of a UE at the cell edge,

taking into account the pathloss, all gains, all losses and all margins,
except shadowing and fast fading margins.
EIRPUE
UE
s
ain
G
es +
s
s
Lo
Reference_SensitivityNode
g)
n
i
h
t
d
a
L
a
p
pt f
e
B,k= Cthreshold
c
x
e
s(
n
i
g
Node (fxed value for a given
r
Ma
service k)
B
Cell Range
UE received power C
UE received power
C oscillates around
a mean value Cmean
equal to Cthreshold
Cmean
=Cthreshold
(fixed
value)
Time
96
3.3
UE received power C
Definition of fading(2)
Shadowing (or Slow Fading or

long-term fading )
Fast Fading (or Multipath fading
or small-scale fading or
Rayleigh fading)
Cmean
Cthreshold
(fixed value)
Time
Shadowing and fast fading

margins are necessary to maintain
the UE received power C above the
fixed Cthreshold during the most part of
the time
97
3.3
Shadowing (1)
Cause:
Shadowing holes appear in the
received power C when the UE
is in the shadow of large
objects (size>10m)
Modeling:
The received power C can be
modeled as a Log-normal
distribution with:
Signal distribution
std dev = 4dB
a mean value Cmean
Note: GSM1800
calibrations can be
reused for the values.
std dev= 2dB

std dev= 6dB
Probability
a standard deviation ,
typically =7-8 dB (clutter
dependent)
std dev=8 dB
Cmean
98
3.3
Shadowing (2)
Definition of reliability level and reliability margin:

Reliability level* =% of time for the received power C to be
above Cthreshold (for a sufficient observation time period) at a
given pixel
*also called local
coverage
Reliability marginx% =Cmean offset compared
to
the
fixed
probability or coverage
Cthreshold to get a reliability level of x% probability per pixel
UE received power C
UE received power C
50
%
Cmean
Cmean
Cthreshold
=Cthreshol
(fixed
value)
(fixed
value)
Wanted reliability level=50%
Reliability margin50%=0dB
Cmean = Cthreshold
95
%
Time
reliability margin
Time
Wanted reliability level=95%

Reliability margin95%=10dB (for =6)
Cmean = Cthreshold +10dB
(see next slide for calculation of Reliability margin
99
3.3
Shadowing (3)
Calculation of reliability margin*:

It depends on the reliability level and on the standard deviation
k
-
-0.5
0
1
1.3
1.65
2
2.33
+
Reliability
level
0%
30%
50%
Reliability margin*=k
Curve for a
standard
deviation =6dB
* be careful! the reliability
margin (defined above)
corresponds to the GSM
shadowing margin, but not to
the UMTS shadowing margin
(see further)
84%
90%
95%
97.7
%
99%
100%
Reliability level (also called local coverage

probability or coverage probability per pixel)
100%
95,2
80% %
60%
50%
probability
40%
for Fmed=Fthr
Reliability
margin95.2%=10dB
20%
0%
-20
-10
10
20
F = (Fmed - Fthr) /dB
100
3.3
Shadowing (4)
Values for the standard deviation :

Power level [dBm] (e.g CPICH RSCP):
it can be modeled as a log-normal variable with a standard
variation (clutter dependent value, typically 7dB or 8dB)
Ratio [dB] (e.g CPICH Ec/Io or UL/DL Eb/No)

it can normally NOT be modeled as a log-normal variable,
because the numerator and the denominator are modeled as
separate log-normal variables with separate standard deviations.
Approximation: a ratio is modeled as a log-normal variable with a
standard deviation which is estimated according to the
correlation between the numerator and the denominator:
CPICH Ec/Io : strong correlation between shadowing effect on Ec
and shadowing effect on Io. CPICH Ec/Io is constant (Field
value:3dB)
DL Eb/No: same as CPICH Ec/No
UL Eb/No: no specific correlation between Eb and No.

a clutter dependent value as for CPICH RSCP
UL Eb/No
is
101
3.3
Shadowing (5)
Definition of area (cell) coverage probability:

If the reliability levels are provided at each pixel of a area (or a
cell), it is easy to calculate the Area(or cell) coverage
probability as the average of all reliability levels.
Reliability level=95%
Average
Cell coverage probability=95%
Area (cell) coverage probability=% of time for the received

power C to be above Cthreshold (for a sufficient observation time
period) in average over the area(cell).
102
3.3
Shadowing (6)
Definition of shadowing margin:

If the area (cell) coverage probability is provided (from the
radio network requirement, see 2.4), it is possible to find out
the reliability levels in the area (cell).
Reliability level=?
Cell coverage probability=95%

Reliability level=?
Reliability level=?
Reliability Margincell edge=?
For a UE at cell edge:
Shadowing margin* = Reliability Margincell edge Soft/Softer HO Gai
*the UMTS shadowing margin (defined above) is NOT the same as the GSM shadowing margin(=Reliabili
103
3.3
Shadowing (7)
How to calculate the shadowing margin for a received power C?

It depends on:
Wanted cell coverage probability
Clutter class of the UE
UE soft/softer handover state and correlation factor
between UE radio links (0=no correlation, typically 0.5)
Examples in uplink (Source: Alcatel simulations)
Cell
coverage
probability
Shadowing Hole
95 %
90 %
Shadowing margin (dB)

(no SHO)
= 6
= 8 = 12
5.9
3.3
8.7
5.4
14.6
10.0
UL Shadowing margin (dB)

(SHO, 2 legs)
= 6
= 8
= 12
3.1
0.6
4.8
2.1
8.5
6.4
Note:in case of soft/er handover (it is

typically the case for a UE at cell
edge), the soft/er handover gain
partially compensates for the
Soft Handover Zone
additional path loss caused by
All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04 shadowing.
104
3.3
Fast Fading (1)
Cause: summation and cancellation of different signal components

of the same signal which travel on multiple paths
Modeling
Rayleigh distributed fading with correlation distance /2
Note: =15 cm for f=2GHz
positive fades are less strong than negative fades (unequal
power variance)
Rayleigh
PDF
Rayleigh
Small-Scale
Fading
105
3.3
UL Fast Fading (2)
How to compensate for fast fading losses in UPLINK?

Case 1: slow moving UE (0-50km/h)
Power control (inner loop at 1500Hz) compensates fairly well
with a TX power increase for the fast fading losses in the
serving cell, but:
It works only if the UE has enough TX power Power
Control Headroom (called Fast Fading Margin)
necessary, especially for the UEs at the cell edge (see
further)
Side effect: increase of f value (little i value) for the
surrounding cells (see further)
Case 2: fast moving UE (>50km/h)
Power Control loop is too slow to compensate for fast
fading
A margin is necessary to compensate for the fast fading
losses: this margin is not explicit, but implicitly included in
(Eb/No)
values (see 2.2)
All rights reserved Alcatel the
- 3FL 11194
ABAA WBZZA
req Ed.01P04
106
3.3
UL Fast Fading (3)
How to calculate Power Control Headroom (Fast Fading

Margin) for slow moving UEs (Case 1)?
Fast fading depends on:
required BER (or BLER)
UE speed
Multipath environment (Vehicular A, Pedestrian A)
UE soft/softer handover state and power difference
between UE radio links
Example for uplink (Source: Alcatel simulations)
Multipath
environment
Dense urban, urban,
suburban (Veh. 3km/h)
Rural (Veh. 50 km/h)
Fast fading margin (dB) for

several target BLER
-1
10
10-2
10-3
10-4
0.6
1.7
2.5
3.3
-0.3
-0.3
-0.3
-0.2
Assumption:
Soft handover
considered with 2
links and 3dB power
difference between
the 2 links
107
3.3
UL Fast Fading (4)
What about the side-effect for slow moving UE (Case 1)?

Fast fading in serving cell and in neighboring cells are not
correlated:
impact on neighboring cells due to UE TX power increase which
causes additional UL extra-cell interference (called average
power rise)
increase of15f value (little i value)
Transmitted
power
10
Average
transmit
power
dB
Power
rise
-5
Node-B
received
power
Channel
- 10
- 15
0.2
0.4
0.6
0.8
1
1.2
Seconds, 3km/h
1.4
1.6
1.8
108
3.3
DL Fast Fading (5)
How to compensate for fast fading losses in DOWNLINK?

Case 1: slow moving UE (0-50km/h)
As in uplink, power control compensates fairly well with a TX power increase
the loss due to fast fading in the serving cell, but:
Power Control Headroom (called Fast Fading Margin) necessary
for NodeB, but much smaller than in uplink, because:
NodeB TX power is a shared power resource: the NodeB has to
compensate channel variations due to fast fading for all UEs in the
cell
There is a very low probability that all UEs be in a fading dip at the
same time
Typical value: 2 dB on the overall available power
Case 2: fast moving UE

(>50km/h)
same as in UL (see previous
slides)
The
Theprobability
probabilitythat
that
aauser
at
the
other
user at the other
side
sideof
ofthe
thecell
cellfaces
faces
fading
at
hole ofhole
shadowing
at
the
same
time
is
very
the same time is very
low
low
Fading holes
TX Power
A margin for each

eeeacheacheacheach
link is not realistic !
109
3.4

Objective:
to be able to calculate the reference

sensitivity for a given service bit rate, BER,
UE speed and UE multipath environment
110
3.4
Definition of Reference_Sensitivity
Antenna
The received Eb/No for a given UE at the

NodeB reference point must apply:
Eb/No[dB] > (Eb/No)req[dB]
Feeder
Note:
Eb/No=C/(I+N C) + PG (definition, see 1.3)
NodeB reference point=NodeB antenna
connector (see 3GPP 25.104)
UE
Node
B
NodeB
antenna
connector
As a consequence, the minimum received power Cmin shall apply:
Cmin [dBm] (Eb/No)req [dB] PG [dB] (I N-Cmin )[dBm]

(Eb/No)req [dB] PG [dB] N[dBm]
I N-Cmin
[dB]
N
Reference_Sensitivity [dBm]
Interference Margin [dB]
defined with reference to N
= Noise Rise [dB] 10log{1+ (Ec/No)req
it is service dependent
see 3.5 for more details
111
3.4
Calculation of Reference_Sensitivity
Re ference_Sensitivity [dBm] (Eb/No)req [dB] PG [dB] N[dBm]
with:
N=-108.1dBm+ NFNodeB =-104.1dBm (assuming NFNodeB=4dB)
PG is the Processing Gain (service dependent):
PG=25dB for speech 12.2k
PG=17.8dB for CS 64k
PG=10dB for PS 384k
(Eb/No)req is a fixed value (see 2.2)
Note: (Eb/No)req depends in UE speed and UE multipath environment
(Vehicular A 50km/h...) in order to take into account the multipath
diversity effect:
gain due to multipath combining in the rake receiver
loss due to multipath fading holes (see 3.4)
112
3.5

Objective:
to be able to calculate the UL interference

margin for a given traffic load
to be able to describe the interference

effects in UL and in DL
113
3.5
Calculation of interference margin

The NodeB reference_sensitivity is defined with reference to the
fixed received thermal noise at receiver N: it is necessary to apply
a correction factor, called Interference Margin in order to take into
account the effect of the movable received interference I:
Interferen ce M arg in [dB] Noise Rise [dB] 10 log { 1 (Ec/No)req [linear ] }

with:
Noise Rise [dB] depends on the interference level I (ie on the
traffic load):
I=Cmin Noise Rise ~ 0,2dB
I=N Noise Rise=3dB
I=3N Noise Rise=6dB
{10 log {1+ (Ec/No)req[linear]}
typically between 0.1dB (for speech 12.2k) and 0.8dB (for
PS 384k)
small value because (Ec/No)req (linear value) <<1 (the
useful signal level is always far below the noise floor in WAll rights reserved Alcatel -CDMA
3FL 11194 ABAA
) WBZZA Ed.01P04
114
3.5
Noise Rise and Traffic load(1)

Definition:
Cj[dBm]: received power of the transmitter j (UEj in UL, NodeBj in
DL)
Xj[%]: load factor for j defined as the contribution of j to the total
noise (I+N)
Cj=Xj x (I+N)
X[%]: load factor defined as the sum of the contributions for all
transmitters
Example in Uplink
Noise Risel (dB)
XUL=sumall UEs in the network(Xj)35; XDL=sumall NodeBs in the network(Xj)

30
1
25
Noise Rise [dB] 10 log
20
1
max loading : 75%

We can demonstrate that:
15
50% of cell load
10
(3dB of interference)
5
0
0
11
21
31
41
51
61
71
81
91
100
XUL (%)
115
3.5
Noise Rise and Traffic load(2)

Uplink
Downlink
Noise Rise and XUL are cell

specific parameters (useful to
characterize UL cell load)
Noise Rise and XDL are UE

specific parameters (not
convenient)
XUL can tend toward 100% (just

by adding new UEs in the network)
Noise Rise can tend towards
infinity the system can be
unstable.
XDL can not tend toward 100%

(because the TX power of
NodeBs has a fix limit Noise
Rise can not tend towards
infinity the system can not be
unstable.
116
3.5
Traffic load and UL load factor (1)

Relationship between XUL and traffic load for one cell:
Does XUL depend on:
the traffic mix?
the user distribution in the serving cell?
the user distribution in the surrounding cells?
XUL can be calculated analytically with the assumption that
Iextra=f x Iintra with f constant value:
EbNo
[%] (1 f)
1 Eb
No
Activity
Factork
N
Chip rate
req,k
XUL
k1
Activity
ServiceBitRatek
Factork
Chip rate
req,k
withN numberof usersin theservingcell
ServiceBitRatek
Answer:
Does XUL depend on:
- the traffic mix? yes (due to different (Eb/No)req values and PG values)
- the user distribution in the serving cell? no (due to power control)
- the user distribution in the surrounding cells? yes, but the most polluting users in the surrounding cells should stop to pollut by taking the
serving cell in their active set (soft/softer handover) and being therefore power controlled by the serving cell
117
3.5
Traffic load and UL load factor (2)

XUL typical values (commonly used):
Very low loadXUL=5%Noise Rise=0.2dB
Medium loadXUL=50%Noise Rise=3dB(typical default value)
High loadXUL=75% Noise Rise=6dB (at the limit of system
instability)
118
3.5
What about DL load factor?

As Noise Rise and XDL are not convenient to characterize the DL cell
load, another parameter is commonly used:
DL powerload factor[%]
TXpowerNodeBfor thecell[W]
MaximumTXpowerNodeBfor thecell[W]
Orthogonality effect
In downlink, the orthogonality of channelization codes reduces
the intra-cell interference Iintra:
Iintra [W]=(1-) x sumDL users in the cell (Ci) with Orthogonality
Factor
=0no orthogonality Iintra= sumDL users in the cell (Ci)
=1perfect orthogonality Iintra= 0 W
3GPP values for Orthogonality Factor :

=0.6 for Vehicular A
=0.94 for Pedestrian A
Note: there is no orthogonality effect in UL because the codes of UL
physical channels come from different UEs and are therefore not
All rights reserved
Alcatel - 3FL 11194
ABAA
WBZZA Ed.01P04
synchronized
each
over.
119
3.6

Objective:
to be able to calculate the MAPL with a

manual UL link budget and to deduce the
cell range
120
3.6
Exercise: MAPLUL calculation (1)

Fixed assumptions:
Antenna gainUE + Internal lossesUE = 0dB
Antenna gainNodeB=18dBi
Feeder and Connector losses=3dB
Thermal noise=-108.1 dBm and NFNodeB=4dB
EXAMPLE 1:
Service/UE mobility assumptions are given (see table EXAMPLE 1)
Can you complete the table EXAMPLE 1?
EXAMPLE 2:
EIRP, Reference_sensitivity, margins, losses and MAPL are given (see
table EXAMPLE 2)
Can you find the service/UE mobility assumptions?
121
3.6

EXAMPLE 1 UL link budget for:
UE power class 4
Speech12.2kbits/s
Vehicular A 3km/h
UE in soft(or softer) handover
state with 2 radio links
Deep Indoor
Cell coverage probability=95%,
=8
UL load factor=50%
Comment
Value
in
f.a.=fxed
assumptio
n (see
previously
)
A. On the transmitter side

A1
UE TX power
dBm
A2
Antenna gainUE + Internal lossesUE
A3
EIRPUE
dB
dBm
see 2.3
f.a.
A1+A2
B. On the receiver side

B1
(Eb/No)req
dB
see 2.2
B2
Processing Gain
dB
see 1.3
B3
NFNodeB
dB
f.a.
B4
Thermal noise
dBm
f.a.
B5
Reference_SensitivityNodeB
dBm
B1B2+B3+B4
(continuing on next slide)

122
3.6

EXAMPLE 1 continuing
Value
in
Comment
f.a.=fxed
assumptio
n
(see
previously
)
C. Margins
C1
Shadowing margin
dB
see 3.3
C2
Fast fading margin
dB
see 3.3
C3
Noise Rise
dB
see 3.5
C4
10 log {1+ (Ec/No)req}
dB
see 3.5
C5
Interference margin
dB
C3-C4
D1 Feeders and connectors
dB
f.a.
D2 Body loss
dB
see 2.2
D3 Penetration loss (indoor

margin)
dB
see 2.2
dBi
f.a.
dB
=?
D. Losses
E. Gains
E1
Antenna gainNodeB
MAPL
123
3.6

UE power class ?
Service: ?
Multipath Environment: ?
state?
Indoor margin:?
Cell coverage probability=?, =?
UL load factor=?
Value
in
Comment
f.a.=fxed
assumptio
n
(see
previously
)

A1
UE TX power
24
A2
A3
EIRPUE
dBm
dB
see 2.3
f.a.
24
dBm
A1+A2
3.2
dB
see 2.2
17.8
dB
see 1.3
dB
f.a.

B1
(Eb/No)req
B2
Processing Gain
B3
NFNodeB
B4
Thermal noise
-108.1
dBm
f.a.
B5
118.7
dBm
B1B2+B3+B4

124
3.6

Value
in
Comment
f.a.=fxed
assumptio
n (see
previously
)
C. Margins
C1
Shadowing margin
4.8
dB
see 3.3
C2
Fast fading margin
-0.3
dB
see 3.3
C3
Noise Rise
dB
see 3.5
C4
0.1
dB
see 3.5
C5
Interference margin
2.9
dB
C3+C4
dB
f.a.
D2 Body loss
dB
see 2.2

margin)
dB
see 2.2
18
dBi
f.a.
139.3
dB
D. Losses
E. Gains
E1
Antenna gainNodeB
MAPL
125
3.6
Exercise: cell range calculation (6)

Can you complete the following table by using the simplified formula
of the Alcatel Standard propagation model (see exercise in 3.2)?
Limiting Service
Clutter class
Cell Range
[km]
Dense urban
Speech 12.2k
Urban
Suburban
Rural
Dense urban
PS64
Urban
Suburban
Rural
126

Duratio
n:
4h00
127
Objective:
to be able to have the theoretical background to
create an initial network design using a RNP tool*:
the aim is to fulfill the radio network requirements
with lowest possible costs.
Program:
4.1
Positioning the sites on the map
4.2
Coverage Prediction for CPICH RSCP
4.3
UMTS Traffic Simulations
4.4
Coverage Predictions for CPICH Ec/Io and DL/UL services
4.5
Traffic emulation approach or fixed load approach?

* the aim of this training is not to learn how to use A9155 RNP tool. There is
another training course for that purpose (3FL 11195 ABAA Alcatel 9155 RNP
Operation)
128
Overview
Initial Radio Network Design
Traffic emulation
approach
Traffic map
Traffic parameters
Propagation model parameters
Network design parameters
Cell range
calculatio
n (see 3)
Traffic
simulation
(4.3)
Positioning the
sites on the map
(4.1)
CPICH
RSCP
coverage
prediction
(4.2)
Change network
design parameters
NO
RNP
requirements
fulflled?
Fixed load
approach
Basic radio
network
optimization (6)
Fixed load
default
values
Coverage predictions(4.4)
- CPICH Ec/Io
-UL Eb/No
-DL Eb/No
NO
RNP
requirements
fulfilled?
Basic radio network

parameter defnition (5)
YES
129
4.1

Objective:
to be able to get a coarse positioning of NodeB

sites on the planning area and to apply a UMTS
parameter set for network design parameters.
130
4.1
Calculation of inter-site distance

Manual Method:
Description:
1. calculate MAPLUL for the limiting service by performing a
manual UL link budget (see 3)
2. deduce the cell range and the inter-site distance:
Inter-site distance = 1.5 x Cell Range for a 3-sectored site
Advantage:
quick, because it can be performed by hand even if RNP tool
and digital maps are not available yet.
Inconvenient:
imprecise, because topographic data and detailed clutter data
are not taken into account.
Typical inter-site distance: Dense urban: 350-450 m, Urban:
500-650 m, Sub-urban:900 -1200 m, Rural: 2000 - 3000 m
131
4.1
Site map
The sites are positioned in the planning area roughly respecting the
inter-site distance for each clutter class:
Existing GSM sites can be reused
The sites should be positioned close to the dense traffic zones
(see traffic map in 2.2)
The initial site map is

regularly updated based
on site acquisition and site
survey results.
Note: At this stage, search
radii may already be
issued, in order to start the
long process of site
acquisition
Planning area
Inte
distr-site
ance
Site map
132
4.1
Network Design Parameters (1)

Network
design parameters
.
site wise
Number of UL/DL hardware
resources
Number of sectors
Typical value
Comment
R2: 2BB boards

R3: 4 BB boards
see 2.3
133
4.1

Network
design parameters
.
sector wise
Number of carriers
no
model
azimuth
parameters
Comment
1
TMA usage
Antenna
Typical value
height
gain
downtil
t
65 horizontal beam
width
0, 120 and 240
3 sectored site
20-25m for urban

30-35 m for suburban
18dBi
6
RXdiv
yes
TXdiv
no
mechanical +electrical
downtilt
DL feeder and connector

losses
3dB
see 3.1
UL feeder and connector

losses
3dB
see 3.1
Noise Figure
4dB
see 2.3
134
4.1

Network
design parameters
.
cell wise
Typical value
Comment
also called Cell Parameters

see Appendix for a complete description of Cell Parameters. Here are only described the cell
parameters which have an impact on traffic simulations and coverage predictions (4)
Max. total power (for the

cell)
43dBm
see 2.3
CPICH (Pilot) power
33dBm
10% of Total power
Other common physical

channels power
35dBm
CPICH power + 2dB
AS threshold
maximum threshold
between the CPICH Ec/Io of
the best transmitter and
3dB the CPICH Ec/Io of another
transmitter so that this
transmitter becomes part
of the UE active set
135
4.2
Coverage Prediction for CPICH RSCP (=C CPICH=Pilot
level= Pilot field strength)
Objective:
to be able to check that the CPICH RSCP

coverage probability is in line with the
network requirements
perform, interpret and improve a CPICH RSCP

coverage prediction
136
4.2
Coverage Prediction for CPICH RSCP (=C CPICH =Pilot level)
How to perform the prediction?(1)

Step1: enter the prediction inputs
Planning Area
e.g. definition of Calculation Areas
NodeBj
Calculation
Area of
NodeBj
Calculation
Radius of
NodeBj
Virtual UE
scanning the
Calculation
Areas of all
NodeBs
137
4.2

Step2: the tool calculates the CPICH RSCP values for the virtual UE
(without considering shadowing effect)
L path
s
s
lo
Path
CPICH RSCP(=CPICH RX power)
CPICH TX power
Node
B
Virtual UE
No shadowing
at each pixel*:
(Shadowing margin=0dB in this

step)
CPICH RSCP[dBm] = CPICH TX power[dBm] +GainNodeB antenna

[dB]
*The
calculation is performed for a given resolution,
Loss
NodeB feeder cables [dB] Lpath [dB]
typically at each pixel of the Calculation Areas (see

Step1)
138
4.2

Step3: the tool calculates the reliability level for each CPICH RSCP
value (calculated in Step2) in order to consider the shadowing effect
(at each pixel)
CPICH RSCP- (CPICH RSCP)minimum=Reliability Margin
with (CPICH RSCP)minimum =fixed value
Reliability Margin = f(Reliability Level, Standard deviation )
is given by the clutter map
we can deduce a CPICH RSCP reliability level (per pixel)
Example:
assume CPICH RSCP=-94 dBm, (CPICH RSCP)minimum =-104dBm,
=6dB
What is the reliability level for this CPICH RSCP value (use the
curve in3.3)?
Reliability Margin=10dB Reliability level=95% (=6dB)

Answer:
139
4.2
How to interpret the prediction?
From the radio network requirements (see 2.4), it is known:

(CPICH RSCP)minimum
required Area Coverage Probability (typically 95%)
Area Coverage Probability:
it is the average of all Reliability Levels per pixel (calculated
in Step3) over the Planning Area
it can be calculated by a tool and has to be compared with
the required Area Coverage Probability
Plannin
Area coverage probability>required value?

if yes, network design is OK
else network design has to be improved
gArea
140
4.2
Exercise
1. What happens if you have a bad CPICH RSCP coverage in an area?

2. Does the CPICH RSCP coverage depend on traffic load?
3. Which are the input parameters for the CPICH RSCP coverage
prediction?
4. Shall the calculation radius be greater or smaller than the intersite distance?
5. Make some suggestions to improve the prediction results
141
4.3
UMTS Traffic Simulations

Objective:
to be able to check that the network capacity

is in line with the traffic demand by performing
traffic simulations with a RNP tool
142
4.3
UMTS traffic simulations
Why do we need traffic simulations?(1)

Can the capacity cope with the demand in UL and in DL?
Traffic Map (see2)

Traffic demand modeling
Site map (see 4.1)

Network capacity modeling
it is necessary to calculate the UL/DL network capacity to check

that it is in line with the traffic demand.
143
4.3
Why do we need traffic simulations?(2)

How to calculate the UL/DL network capacity?
Problem: the capacity depends on the user distribution (at least
in DL)
User distribution 1
User distribution 2
NodeB
Cell
NodeB
Cell
384k
12.2k
Suburban
environme
nt class
12.2k
384k (in outage)
Network capacity 1 > Network capacity 2 (for the same

traffic map)
Solution: a traffic simulation can be performed (= a snapshot
of UMTS network at a given time, one possible scenario among
infinite number of scenarii).
144
4.3
How to perform a traffic simulation?(1)

Step 1: enter the traffic simulation inputs
Traffic simulation
inputs
typical
value
Comment
Traffic simulation parameters (only used for traffic simulations)

Maximum UL load factor
75%
Number of iterations
100
Convergence criteria
3%
Orthogonality factor (per

clutter)
0.6
limit of system instability. If this threshold is

overcome, some UEs are put in outage.
RNP tool dependent values. Trade off between
precision and calculation time
0.6 for Vehicular A ; 0.94 for Pedestrian A
Traffic mapsee 2.2

Propagation model parameterssee 3.2
Network design parameterssee 4.1
145
4.3

Step 2: the RNP tool provides a realistic user distribution
Used input: traffic map
The RNP tool provides a snapshot of the network at a given time
(based on the traffic map and Monte-Carlo random algorithm):
a distribution of users (with terminal used, speed and multipath
environment) in the planning area
a distribution of services among the users
a distribution of activity factors among the speech users in order
to simulate the DTX (Discontinuous Transmission) feature
Example:
24 users
Mobile phone
Vehicular 50km/h
Speech 12.2k (active)
PDA
Vehicular 3km/h
PS384
146
4.3

Step 3: the RNP tool checks the UL/DL service availability for each user
Used inputs: user distribution (see Step1) +Propagation model
parameters+Network design parameters+ traffic simulations
parameters
UL/DL link loss calculations are performed iteratively due to (fast)
power control mechanisms in order to get:
needed UE TX power for each UE
needed NodeB TX power for each cell
Each of the following conditions is checked: if one of them is not
fulfilled, the concerned user will be ejected (service blocked):
Conditions in UL:
Conditions in DL:
1) CPICH Ec/Io < ( CPICH Ec/Io)required
1) needed UE TX power <
Maximum UE TX power
2) needed NodeB TX power < Maximum
2) UL load factor <
NodeB TX power (ie DL Power
Maximum UL load factor
load<100%)
(typical value: 75%)
3) (for each traffic channel) needed TX
3) enough UL NodeB
power < Max TX power per channel
processing capacity
4) enough DL NodeB processing capacity
5) needed number of codes < max number
of codes
147
4.3
Traffic simulation outputs
DL (power) load factor per cell

UL load factor per cell
Percentage of soft handover
Percentage of blocked service requests and reasons for blocking
(ejection causes)
Example of ejection causes with A9155 RNP tool:

the signal quality is not sufficient:
on downlink:
not enough CPICH quality: Ec/Io<(Ec/Io)min
not enough TX power for one traffic channel(tch): Ptch > Ptch max
on uplink:
not enough TX power for one UE (mob): Pmob > Pmob max
the network is saturated:
the maximum UL load factor is exceeded (at admission or
congestion).
not enough DL power for one cell (cell power saturation)
not enough UL/DL NodeB processing capacity for one site (channel
element saturation)
not enough DL channelization codes (code saturation)
148
4.3
Limitation of traffic simulation

Limitation:
a simulation is only based on one user distribution
another simulation based on the same traffic map but on a
different user distribution can give different results for DL/UL
service availabilities
Solution:
to average the results of several simulations (statistical effect)
to be closer to the reality
Other interest of traffic simulation
Some traffic simulation ouputs (that are DL (power) and UL load
factors per cell) can be used as inputs for CPICH Ec/Io and
DL/UL service coverage predictions (see 4.4).
149
4.4
Coverage Predictions for CPICH Ec/Io and DL/UL
services
Objective:
to be able to check that the coverage

probabilities for UL/DL services are in line with
the networks requirements by performing
coverage predictions with an RNP tool
150
4.4. Coverage Predictions for CPICH Ec/Io and DL/UL services (based on traffic
simulations)
Why do we need coverage predictions?
What is the probability for a user to get UL/DL services at a given

point of the planning area?
What is the coverage
probability at this pixel for:
-CPICH Ec/Io?
-UL service coverage?
-DL service coverage?
Problem: traffic simulations can be used, but it is necessary to

average an enormous number of traffic simulations (see4.3) to get
the answer for each service at each pixelunrealistic calculation
time
Solution: Coverage Predictions can be performed
151
simulations)
Different types of coverage predictions
CPICH RSCP prediction plot (see 4.2)

CPICH Ec/Io prediction plot
Only the pilot quality from best server is considered (no soft
handover)
Standard deviation: 3dB
no UL/DL service coverage if CPICH Ec/Io < (CPICH Ec/Io) minimum
UL Coverage area prediction plots for each service
soft/softer handover possible
Standard deviation: same as clutter map values
Uplink service area is limited by maximum terminal power.
DL Coverage area prediction plots for each service
soft/softer handover possible
Standard deviation: 3dB
Downlink service area is limited by maximum allowable traffic
channel power
152
simulations)
How to perform a coverage prediction?(1)
Step 1: enter the Coverage Prediction inputs

Traffic simulation inputs
typical
value
Comment
Coverage Predictions parameters (only used for predictions)

Calculation Radius (per cell)
4 km
same as for CPICH RSCP prediction (see 4.2)
Probe
UE
Terminal parameters
and indoor margin
see
2.2
The probe UE characterizes the

service/terminal/multipath environment for
which the Coverage Prediction is performed,
e.g. PS64/PDA/Vehicular 3km/h
UL load factor(per cell)
50%
DL(power) load factor(per cell)
50%
Service parameters
Multipath environment
Note: in case of CPICH/Io prediction, no

service parameters are entered.
used to simulate UL/DL interference level
Fixed load approach: same values for all cells
Traffic emulation approach: specific values for
each cell (see 4.5)
(ratio value)minimum
-15dB (typically) for CPICH Ec/Io ratio (see 2.4)

(Eb/No)req values for UL/DL (Eb/No) ratios (see 2.2)
Stand. deviation (per clutter)
3dB for CPICH Ec/Io and DL (Eb/No) ratios,

clutter map values for UL (Eb/No) ratio (typically 7-8dB)
Orthogonality factor (per

clutter)
0.6
0.6 for Vehicular A ; 0.94 for Pedestrian A

153
simulations)
Step 2: calculation of the ratio values (e.g. CPICH Ec/Io values) at

each pixel
A probe UE (causing no interference) is scanning each pixel of
the planning area.
Pathloss calculations are performed for this probe UE to get the
ratio values:
e.g. CPICH Ec/Io values per pixel or UL PS64 (Eb/No) values per
pixel
Probe UE scanning each pixel

of the calculation areas
154
simulations)
Step 3: calculation of the reliability level for each ratio value

(calculated in Step2) in order to consider the shadowing effect.
(at each pixel)
Ratio value - (ratio value)minimum=Reliability Margin
with (ratio value)minimum =fixed value
Reliability Margin = f(Reliability Level, Standard deviation )
is given by the prediction inputs (see Step 1)
we can deduce a reliability level (per pixel) for the ratio

value
Example:
what is the reliability level for the following pixels(use the curve in
3.3):
CPICH Ec/Io value = -12 dB?
Answer:
CPICH Ec/Io (CPICH Ec/Io)minimum =-15dBReliability Margin=3dBk=1 (=3dB) Reliability level=84%
UL (Eb/No)(Eb/(No)req=3.2dBReliability Margin=0.8dBk=0.1 (=8dB) Reliability level~50%
UL (Eb/No) value= 4dB (for PS64, Vehicular 50km/h)?
155
simulations)
How to interpret a coverage prediction?
From the radio network requirements (see 2.4), it is known:

(ratio value)minimum
required Area Coverage Probability (for a given ratio)
Area Coverage Probability (for a given ratio):
it is the average of all Reliability Levels per pixel (calculated
in Step3) over the Planning Area
it can be calculated by a tool and has to be compared with
the required Area Coverage Probability
Area coverage probability>required value?

if yes, network design is OK
else network design has to be improved
Planning
Area
Reliability
level=80%
156
4.5
Traffic emulation approach or fixed
load approach?
Objective:
to be able to describe the different

approaches which lead to an
acceptance test
157
4.5
Traffic emulation approach(1)
Traffic map (2.2)

Traffic simulations (4.3)
Fixed DL(power)/UL
load factors per cell
Field
traffic
emulation
Predictions (4.4)
Change
no
Network
Design
Parameter(
s)
RNP tool
Field
measurement
s
in line
with RNP
requirements?
yes
Result1
Result2
Field
Acceptance Test
Result1=Result2?
158
4.5
Traffic emulation approach(2)
Advantages:
accurate (but the accuracy depends on the accuracy of traffic
map)
Disadvantages:
complex:
traffic forecast and traffic map for the coming years must
be provided by the operator
traffic simulations must be performed with RNP tool and if
any parameter is changed, it is necessary to recalculate
traffic simulations before recalculating coverage
predictions
no acceptance test possible, because it is not realistic to
emulate the traffic map in the field.
159
4.5
Fixed load approach(1)
Default DL(power)/UL
load factors values for
each cellFixed
load
Field Fixed load
emulation
Predictions (4.4)
Change
Network
Design
Parameter(
s)
RNP tool
no
Field
measurement
s
in line
with RNP
requirements?
yes
Result1
Result2
Field
Acceptance Test
Result1=Result2?
160
4.5
Advantages:
simple: no need of traffic map and traffic simulations
acceptance test can be realized, because fixed load can be
emulated and measured in the field (at least in DL, see further)
Disadvantages:
inaccurate (no traffic map considered)
all planning efforts targeting to optimize the network by
reducing traffic per cell can not be modeled by this approach
(Fixed Load Trap effect):
adding cells/sites
real effect: big enhancement of the total network
capacity
modeled effect: little enhancement of the network
capacity
indeed, as the same load is mandatory for all cells
(fixed load), the new cell/site will add (artificial) load and therefore
bring a lot of (artificial) interference and only very little new capacity
downtilting antenna for one cell

real effect: cell load decrease (because it makes the
cell area smaller)
All rights reserved Alcatel - 3FL
ABAA WBZZA Ed.01P04
11194
modeled
effect: no cell load decrease (due to fixed
161
4.5
How to emulate DL fixed load in the field?
DL load can be emulated

with the OCNS (Orthogonal
Code Noise Simulator)
feature of the Alcatel
NodeB:
It generates artificial
interference in
downlink
It is used to emulate
downlink load and
perform tests with a
reduced number of UEs
Typical default value: 50%
for DL (power) load factor
DL _ load (%)
Common channels
OCNS channels
Dedicated channels
Maximum
output power
Simulated
traffic
Virtual
mobiles
(due to OCNS)
OCNS _ TX _ power Trace UE DL TX power

Maximum DL TX power Available
Node
B
Real
traffic
Trace
mobile
162
4.5
How to emulate UL fixed load in the field?

UL load could be emulated by generating artificial interference
at the NodeB receiver (a kind of UL OCNS feature): such a
feature is not provided by Alcatel NodeB.
Workaround:
UL load can be emulated at the MS side by
placing an Attenuator (Att) in the MS transmit
path
Tx
Tx
Rx
Rx
Att
Typical default value: 50% for UL load factor

(ie 3dB Noise Rise, ie 3dB Attenuation)
Tx
Rx
UE
163
4.5
A medium approach(1)
Traffic map (2.2)
Default UL load factor

values for each
cellFixed load
Traffic simulations (4.3)

Fixed DL(power)/UL
load factors per cell
DL(power) load
factor per cell
Field fxed
load
emulation
Predictions (4.4)
Change
Network
Design
Parameter(
s)
RNP tool
no
Field
measurement
s
in line
with RNP
requirements?
yes
Result1
Result2
Field
Acceptance Test
Result1=Result2?
164
4.5
A medium approach(2)
Alcatel strategy is to use the fixed load approach as it is measurable

on the field and less ambiguous if commitments have to be fulfilled.
Nevertheless, a medium approach can be considered to overcome
the disadvantages of the fixed load approach (see previous slide):
Advantages:
accurate (but the accuracy depends on the accuracy of
traffic map)
acceptance test can be realized
Constraints:
traffic forecast and traffic map for the coming years must
be provided by the operator
traffic simulations must be performed with RNP tool
DL: the operator shall agree that the DL field traffic
emulation is realized from the traffic simulation outputs of
the RNP tool
UL: default value for UL load factor must be taken for the
whole network (no UL OCNS feature)
165

Duratio
n:
1h00
5. Basic Radio Network Parameter

Definition
166
Objective:
to be able to define the basic radio network
parameters (neighborhood planning and code
planning parameters)
Program:
5.1
5.2
Neighborhood planning
167
5.1
Objective:
to be able to describe the criteria and methods

used to perform neighborhood planning.
168
5.1
Overview
The purpose of neighborhood planning is to define a neighbor set

(or monitored set) for each cell of the planning area
The neighbor set is broadcasted in each cell in the P-CCPCH
and can therefore be accessed by each UE
Each UE monitors the neighbor set to prepare a possible cell reselection or handover
The neighbor set may contain:
Intra-frequency neighbor list : cells on the same UMTS carrier
Inter-frequency neighbor list: cells on other UMTS carrier
Inter-system neighbor lists: for each neighboring PLMN a separate list is
needed.
Note: it is NOT the aim of neighborhood planning to define a ranking of the

cells inside the neighbor set. This ranking is performed by the UE using UE
measurements and criteria defined by UTRAN radio algorithms.
The neighborhood planning plays a key role in UMTS. Indeed, as

UMTS is strongly interference limited, a wrong neighbors plan will
bring interference increase and therefore capacity decrease.
e.g. if a possible soft handover candidate is not selected, because it is not

in the neighbor list, it is fully working as Pilot Polluter
169
5.1
Criteria and methods

Criteria:
Lets consider one cell (called cell A). One or several of the following
criteria can be used to decide to take a candidate cell as neighbor of
cell A :
the distance between cell A and the candidate cell is less than a
given maximum inter-site distance.
the overlap area between cell A and the candidate cell is more
than a given minimum value.
Note: overlap area between cell A and cell B = intersection between S A and SB, with
SA[km2]=area where
(CPICH RSCP)cellA and (CPICH Ec/Io)cellA better than given minimum values
(CPICH Ec/Io)cell A is the best
SB[km2]=area where
(CPICH RSCP)cellB better than given minimum value
(CPICH Ec/Io)cell B>(CPICH Ec/Io)cell A (a given margin)
the candidate cell is a co-site cell (=cell of the same NodeB).

cell A is neighbor of the candidate cell (neighbor symmetry).
Methods:
manually (not possible to consider the overlap area criterion)
with an RNP tool see example with A9155 tool on next slides
170
5.1
Automatic neighborhood allocation with

A9155(1)
Step1: enter input parameters
Neighborhood
parameters
Typical
value
Comment
Minimum CPICH RSCP
-105 dBm
Minimum CPICH Ec/Io
-18 dB
Ec/Io margin
8 dB
Reliability level
87%
Minimum covered area
2%
Maximum inter-site
distance
between 8km
and 25km
8 km for dense urban and urban,

10 km for sub-urban and around
25 km for rural areas
Force co-site cells as

neighbors
Yes
co-site cells=cells of the same

NodeB
Force neighbor symmetry
Yes
e.g. if cell A is neighbor of cell B,

cell B will be neighbor of cell A
Max number of neighbors
14
parameters used for overlap area

criterion
171
5.1
Automatic neighborhood allocation with

A9155(2)
Step2: for each cell, A9155 RNP tool calculates the neighbor
list as
follows
if Force co-site cells as neighbors=Yes, co-sites cells are taken
first in the neighbor list.
cells which fulfill the following criteria are taken in the neighbor
list:
the maximum inter-site distance criterion
the overlap area criterion
Note: if the maximum number of neighbors in the list is
exceeded, only the cells with the largest overlap area are
kept.
if Force neighbor symmetry=Yes, cells with a neighbor
symmetry are taken in the neighbor list, under the condition
that the maximum number of neighbors has not already been
exceeded.
172
5.2

Objective:
to be able to describe the criteria and the

methods used to perform the scrambling code
planning
173
5.2
Overview
Scrambling code planning in UMTS FDD is similar to frequency

planning in GSM. However it is not such a key performance factor:
it concerns only DL scrambling code (channelization codes and
UL scrambling codes are automatically assigned by the RNC)
In contrast to frequency planning, it is not crucial which
scrambling codes are allocated to neighbors as long as they
are not the same code.
174
5.2
DL scrambling code planning (1)

DL scrambling codes:
used to separate cells
restricted to 512 (primary) scrambling codes (easy planning)
Criteria:
the reuse distance between two cells using the same
scrambling code inside one frequency shall be higher than 4 x
inter-site distance
(preferable) the same scrambling code should not be used in
two cells of the same sector
Methods
manually
with a RNP tool (see see example with A9155 tool on next
slide)
175
5.2
DL scrambling code planning (2)
Method with a RNP tool:

Note: Neighborhood planning (see 5.1) must be performed before performing
scrambling code planning, because neighborhood relationships are used in the
following method.
1.
define the set of allowed codes for each cell (there can be some
restrictions for cells at country borders)
2.
(optional) define the set of allowed codes per domain (one domain per
frequency)
3.
define the minimum reuse distance
4.
define forbidden pairs (for known problems between two cells)
5.
run automatic code allocation and check consistency
A9155 assigns different primary scrambling codes to a given cell i and to its
neighbors.
For a cell j which is not neighbor of the cell i, A9155 gives it a different code:
If the distance between both cells is lower than the manually set minimum
reuse distance,
If the cell i / j pair is forbidden (known problems between cell i and cell j).
A9155 allocates scrambling codes starting with the most constrained cell and
lowest
constrained one. The cell constraint level depends on its
All rights reserved Alcatel - ending
3FL 11194with
ABAA the
WBZZA
Ed.01P04
176
5.2
Definition of UL scrambling code pool for a RNC

UL scrambling codes:
used to separate UEs
more than one million of codes available (very easy planning)
2 different UEs mustnt have the same code (inside one
frequency)
Criterion for definition of UL scrambling code pools: 2 RNC mustnt
have the same scrambling code in their pool
Method: each RNC is assigned manually a unique pool of codes
(e.g. 4096 codes in R2)
Note: when a UE performs a connection establishment to UTRAN (RRC
connection), the Serving RNC will assigned dynamically an UL scrambling
code out of its pool to the UE. The code is released after RRC connection
release.
177

Duratio
n:
2h30
6. Basic Radio Network

Optimization
178
Objective:
to be able to discuss optimization possibilities in
terms of capacity and coverage
Program:
6.1
Coverage and Capacity Improvement
features
6.2
Design optimization based on drive
measurements
179
6.1
Coverage and Capacity Improvement features

Objective:
to be able to describe the Alcatel R2/R3

UTRAN features in term of coverage/capacity
improvements in UL/DL
180
6.1
UTRAN
features
in UL
UTRAN features
Release 2 (R2)
RX diversity with 2 RX
chains (this is a standard
feature)
Release 3 (R3)
TMA (Tower Mounted

Amplifier)
in DL
High power amplifier (multicarrier TEU with 35W TX

power at antenna connector)
TX diversity (STTD mode and
TSTD mode)
in UL
and
in DL
support of 3 sectors per MBS support of 6 sectors per MBS

(support of 1 carrier (cell)
per sector)
support of 3 carriers (cells) per

sector
181
6.1
TMA - Tower Mounted Amplifier (1)

A TMA can be used at a UMTS Node B to improve
the effective receiver system noise figure when a
long feeder cable is used
The reduction in the receiver system noise figure
is translated into an improvement in the uplink
power budget
Antenna
Duplexer
TMA
Tx
Rx
Duplexer
This can be interpreted as compensating the

losses of the feeder and connectors between the
antenna and the input of the base station
Feeder
Tx / Rx
BTS /
Node B
Additional downlink loss (~0.5 dB)
182
6.1

For RX antenna diversity
operation, the configuration
has to be doubled
One TMA for each
antenna needed Dual
TMA
Antenna
Duplexer
Alcatel TMA is a dual TMA
Duplexer
TMA
Tx
Rx
Duplexer
Feeder
Tx / Rx
TMA
Tx
Rx
Duplexer
Feeder
Tx / Rx
Node B
183
6.1

Network Design and Planning
relevant TMA parameters
TX Part
TX passband:
19201980 MHz
Insertion Loss:
< 0.5dB
TX ANT Filter
out-of-band attenuation:
>35 dB in all GSM bands
RX Part
RX passband:
19201980 MHz
fixed nominal Gain:
10-12dB
Noise figure at 25C:
<= 2dB
Max. input power:
10 dBm
RX ANT Filter
out-of-band attenuation:
>60 dB in GSM TX band
>63 dB in DCS TX band
184
6.1

Calculation of the resulting NF with Friies-Formula
ncable 1
nDX 1
nBS 1
gTMA
gTMA gcable gTMA gcable g DX
ntot ,TMA nTMA
with nelement 10
4.3 dB gain
on total NF in
this example
due to TMA
NFelement
10
and gelement 10
Gelement
10
ntot ,no TMA ncable
DX means Diplexer or Filter
nBS 1
nDX 1
gcable
gcable g DX
Element
Noise Figure (NF)
Gain
TMA
2dB
12dB
Cable 25m
3dB
-3dB
Node B (incl. ANRU)
4dB
Noise Figure of TMA & cable & nodeB
Noise Figure of cable & node B
2.7dB
7dB
185
6.1
Total Interference I (dB)
18
16
Link Budget Curve with TMA
Link Budget Curve w/o TMA
I(R) for High_Traffic
I(R) for Low_Traffic
14
12
Uplink coverage gain

depends on the traffic
density!
TMA impacts Link Budget
curve but not Traffic curve
10
8
6
4
2
0
0
0.2
0.4
0.6
Cell Range R (km)
0.8
Typical reduction of the

required number of sites:
~40%
for low traffic
scenario
~30%
for high traffic
scenario
186
6.1

Example of Gain on
Coverage
Assuming UL
limited scenarios
Conclusion:
In UL limited
scenarios a TMA can
reduce the number of
required sites by 30
to 40 %
Dense Urban
Cell range/km
UL load
Site area /sqkm
# of sites for
reference coverage
area of 1000sqkm
Gain in # of sites
Cell range/km
UL load
Site area /sqkm
# of sites for
reference coverage
area of 1000sqkm
Gain in # of sites
Cell range/km
UL load
Site area /sqkm
# of sites for
reference coverage
area of 1000sqkm
Gain in # of sites
Cell range/km
UL load
Site area /sqkm
# of sites for
reference coverage
area of 1000sqkm
Gain in # of sites
Low Traffic Scenario

without TMA
with TMA
0,377
14%
0,277
3608

without TMA
with TMA
0,517
18%
0,520
1921

without TMA
with TMA
1,287
18%
3,230
310
High Traffic Scenario

without TMA
with TMA
0,481
0,318
18%
53%
0,451
0,197
2217
39%
Urban
5071

without TMA
with TMA
0,665
0,448
20%
50%
0,863
0,392
1159
40%
Suburban
2552

without TMA
with TMA
1,659
1,126
21%
49%
5,367
2,472
186
40%
Rural
404
0,383
63%
0,286
3496
31%
0,539
62%
0,567
1763
31%
1,377
61%
3,697
270
33%

without TMA
with TMA
without TMA
with TMA
4,945
6,273
4,397
5,305
26%
32%
51%
62%
47,691
76,721
37,699
54,882
21
13
38%
27
18
31%
187
6.1
In te r fe r e n c e le v e l
14
12
10
8
max. allowed
6 interference level
2
0
0
0.2
0.4
0.6
0.8
TMA allows x dB higher

interference level: gain in UL
budget
cell radius can be
maintained without
shrinking with x dB more
interference
can be translated in
capacity gain
increase of interference only
up to max. allowed level
high gain for low traffic (A)
negligible gain for high
traffic (B)
Cell Load
Capacity gain A
Capacity gain B
188
6.1

Example of UL capacity gain:
UL limited scenario
Low traffic Medium traffic High traffic
scenario
scenario
scenario
Interference before adding TMA
in dB
Noise Rise
Load before adding TMA

Gain in Throughput relative to
initial throughput
0,21
0,50
0,68
232,5%
50,4%
9,7%
Max UL load of
75% used in
simulation
Conclusion:
In UL limited scenarios a TMA can improve the overall UL
throughput, if the interference (noise rise) is not close to the
limit
Note: gain is service independent
189
6.1

Higher bit rate services
Compensate for introduction of

higher bit rate services
Required received level (sensitivity)
of high data rate services is bigger
than for low data rate services
E.g. difference between Rx
sensitivities of 128kbit/s and
384kbit/s services: 4.5 dB
Introduction of high data rate
service means potential
decrease of cell range
Gain through TMA in uplink budget
can be used to compensate for this
effect
Introduction
of 384kbps
384 kbps
coverage
128 kbps
coverage
Simultaneous introduction of
TMA and new service helps
keeping coverage range
190
6.1

Usage in co-siting scenarios
Dualband antenna
DC feed has to be resolved in case

of diplexer usage (DC block for
GSM band, DC pass of UMTS band)
TMA
Diplexer
DC block Band 1 (GSM)

DC pass Band 2 (UMTS)
Feeder
If a TMA is required for each

system, use separate feeders
It is not possible to use a common
TMA in case of broadband antenna
usage (interleaved UL and DL
signals)
Diplexer
GSM 900/
GSM1800
BTS
It is not possible to have more than

one TMA in case of feeder sharing
(alarm handling, DC feed)
UMTS
Node B
Feeder sharing solution

191
6.1

Blocking aspects
In-Band-Blocking
Potential Problem: Excess gain of TMA
Blocking performance decreases be the amount of
excess gain=amplifier gain feeder cable loss
Solution: Amplification reduction in node B to
Out-of-Band-Blocking and Co-Siting with GSM
RX ANT filter attenuates all out of band signals and
improves the out-of-band-blocking situation (better than
without TMA!)
192
6.1

Conclusion
Tower mounted amplifiers (TMA) enable to increase the uplink
coverage
The reduction of the number of sites to cover a given area with
TMA depends on the traffic density assumptions and is higher
for low traffic conditions than for high traffic conditions.
In the Uplink, setting up sites with TMA will require between
30% and 40% less sites than without TMA.
However, implementing TMA may accelerate DL power
limitation, A carrier on TX diversity may be required in such
cases.
193
6.1
TX diversity (1)
Basics
The transmit antenna diversity techniques consist in using
several transmit antennas, broadcasting de-correlated
complementary signals
2 modes :
Open loop (first phase : already available)
TSTD - Time Switch Transmit Diversity

(Synchronization channel only)
STTD - Space-Time transmit diversity
(Other physical channels)
Closed loop (second phase) : higher diversity gain
194
6.1
TX diversity (2)
STTD= Space-Time transmit diversity
Signal is shifted in space and in time to obtain the

second signal
b0 b 1 b 2 b3
Antenna 1
b0 b 1 b2 b 3
Channel bits
-b2 b3 b0 -b1 Antenna 2
STTD encoded channel bits

for antenna 1 and antenna 2.
Open-loop techniques (i.e. STTD) are statistical and rely on a

non-coherent combining in the receiver.
Performance gain due to ability to fight against fast fading
195
6.1
TX diversity (3)
Performance gain:
doubling the TX power by adding a power amplifier (PA or TEU)
Reducing the required transmit power for each downlink
channel (transmit power raise due to fast fading is reduced)
Improving the RX Eb/No (slight reduction for open loop TxDiv,
higher for closed loop TxDiv)
Speech 8 kbps, 1 rx antenna, downlink, pedestrian A
Target R x E b/N 0 (dB )
Without Tx diversity
STTD
0.8 dB
10
25
Speed (km/h)
50
120
196
6.1
TX diversity (4)
STTD-Gain on DL Capacity
Pure Diversity Gain:
Independent of cell range
Service dependent
High difference between multipath environments:
low to medium gain in Vehicular A (valid in
macrocells)
significant gain in Pedestrian A (valid in
microcells)
Gain through adding a second PA:
Highly dependent on cell range
197
6.1
TX diversity (5)
STTD-Gain on DL Capacity - Example

Monoservice NRT 128kbit/s, Urban, Vehicular A
NRT 128 kbps/ URBAN
Pure Diversity gain in

capacity: ~8%
Gain through 2nd PA:
dependent on cell
range
C a p a c ity g a in b y d o u b lin g th e m a x im a l d o w n lin k

tra n s m it p o w e r (% )
20,0%
18,0%
16,0%
14,0%
Typical uplink coveragelimited cell ranges
for NRT 128
12,0%
From(24W,1Carrier)
To (48W,1Carrier)
10,0%
8,0%
6,0%
Example for typical cell

range (0.6km):
4,0%
2,0%
0,0%
0
0,1
0,2
0,3
0,4
0,5
0,6
0,7
Cell range (km)
0,8
0,9
8%+3%=11% total gain

198
6.1
TX diversity (6)
STTD-Gain on DL Capacity
Typical Values Typical Values in Vehicular A environment
Dense Urban
Urban/ Suburban
Rural
~8%
~10%
~12%
~0%-2%
~1%-8%
~2%-11%
~8%
~15%
~20%
Capacity gain through

diversity
Capacity gain through 2nd PA
(for typical cell ranges)
Typical Total Capacity Gain
Typical Value in Pedestrian A environment (microcell)

Pure Diversity gain: ~20%
Gain through 2nd PA: negligible
199
6.1
TX diversity (7)
Implementation in Alcatel Node B V1

Carrier
Power Amplifer
TX
TRX1
PA
20 W
Antenna
Antenna 1
Adding second PA
doubling power
Carrier
Power Amplifer
TX
TRX1
PA
20 W
Antenna
Antenna 1
TXdiv
PA
20 W
Antenna 2
200
6.1
TX diversity (7bis)
Implementation in Alcatel MBS

TX Bus
Power Amplifer
TX1
PA
20 W
Antenna
Adding second TEU

doubling power
Antenna 1
TEU
TX Bus
Power Amplifer
TX1
PA
20 W
Antenna
Antenna 1
TEU
TX1div
PA
20 W
Antenna 2
TEU
201
6.1
TX diversity (8)
Conclusion
Transmit diversity enables to increase the DL capacity of a
UMTS cell.
2 different TxDiv Techniques are defined: STTD (open loop) and
closed loop (feedback from the UE to the node B)
Performance depending on the scenario.
Low multipath channel (Vehicular A) the performance is
better, but the potential improvement is lower compare to
a channel with higher multipath diversity (Pedestrian A).
The performances achieved depend also on the type of TxDiv
used: closed loop TxDiv is better for low speeds than STTD.
202
6.1
High Power Amplifier (1)
Basics
45
40
Impact of Node B power rise on capacity
35
Transmit power (Watt)
30
RURAL 7 km
RURAL 5 km
SUBURBAN 1,3 km
URBAN 0,5 km
URBAN DENSE 0,35 km
25
20
+9%
+3 %
+1,5%
15
high impact in
rural
10
0
100
200
300
400
500
600
Throughput NRT 128 (kbps)
700
800
900
negligible
impact in
urban
203
6.1
DL Capacity gain
The capacity curves show that the effect of doubling the
available transmit power is far from doubling the capacity
Due to downlink behaviour, higher transmit power will be
more efficient (in terms of capacity gain) in rural
environments than in urban environments
Capacity gain is higher when increasing the power from 5.3
Watts to 10 Watts than from 10 Watts to 20 Watts or 20
Watts to 40 Watts
At a given threshold of transmit power, increasing the
transmit power will not help in increasing the cell capacity
The Capacity gain depends on the cell range
204
6.1
Cell range and traffic dependency of capacity gain

NRT 128 kbps / URBAN
1000
900
Throughput per sector (kbit/s)
800
700
600
40 Watts per carrier -1 carrier

24 Watts per carrier - 1 carrier
Traffic Curve (low traffic/km)
Traffic Curve (high traffic/km)
500
400
300
200
100
0
0
0,2
0,4
0,6
0,8
1,2
1,4
1,6
1,8
Cell Radius (km)
205
6.1
Example of downlink capacity gain

results for fixed cell ranges in high traffic scenarios
(uplink coverage limited) :
Feature Name
Higher PA
Dense Urban
350m
1 carrier: 20W to 40W
1%
2 carriers: 10W to 20W
4%
3 carriers: 5.3W to 10W
6%
Max power per carrier
Urban
550m
2%
6%
9%
Suburban
1700m
4%
11%
17%
Rural
7km
8%
20%
31%
206
6.1
Conclusion
To increase the power per carrier is only interesting in
environments, where the MAPL allowed is high:
In suburban and rural environments
Where Low data rate services are offered in UL
Where coverage enhancement features are used in UL
such as TMA and 4RxDiv
207
6.1
6 sector site (1)
Coverage Gain
Results of simulation done with Alcatel RNP tool A9155V6
No topo or morpho
hexagonal site design , tilt optimized for each environment
NodeB power 46.8 dBm, fixed traffic scenario
Antenna height [m]

HPBW
Tilt (total)
Antenna Gain [dBi]
Intersite distance [m]
Coverage area / site [km]
Gain on coverage
Less sites required
More sectors required
URBAN
SUBURBAN
RURAL
3-sector
6-sector
3-sector
6-sector
3-sector
6-sector
20
20
25
25
30
30
65
32
65
32
65
32
5
5
3
3
1
1
18
21
18
21
18
21
1525
1950
4300
4500
13350
15000
2.0
3.3
16.0
17.5
154.3
194.9
64%
10%
26%
39%
9%
21%
22%
83%
58%
208
6.1
6 sector site (2)
Capacity Gain with NodeB V1

Simulations done with A9155V6 have shown, that the limiting
factor in terms of capacity is not the power, but mainly the
base band boards for V1.
As the BB boards are common resource of the NodeB it is
useless to install a 6 sector site for capacity reasons
NodeB V1
Number of carriers
Global Scaling Factor
Total number of rejections
Channel elements saturation
Multiple Causes
Ptch>PtchMAX
TX Power Saturation
#
%
%
%
%
%
1
8
5.0
2.4
1.4
0.0
1.2
3 sector site
2
8
4.2
4.2
0.0
0.0
0.0
3
8
4.4
4.4
0.0
0.0
0.0
6 sector site
1
2
8
8
4.9
5.0
4.8
5.0
0.1
0.0
0.0
0.0
0.0
0.0
209
6.1
6 sector site (2bis)
Capacity gain with MBS V2

for different configurations compared to 3x1 and 3x2 configurations
(dense urban, 500m inter-site distance)
Less transmit power

per carrier
MBS V2
Number of carriers
Max. Output Power
Global Scaling Factor
Capacity gain (rel. 3x1)
Capacity gain (rel. 3x2)
Total number of rejections
Channel elements saturation
Ec/Io < (Ec/Io)min
Multiple Causes
Ptch>PtchMAX
TX Power Saturation
#
dBm
%
%
%
%
%
%
%
%
1
46.8
11.7
5.0
0.0
2.5
0.0
0.4
2.1
3 sector site
2
43.0
19
62.4
5.0
0.0
0.0
0.0
0.0
5.0
Higher inter-sector interference

for 6 sector site
because less frequencies used
3
40.3
17
45.3
-11%
5.0
0.0
0.0
0.0
0.0
5.0
6 sector site
1
2
46.8
43.0
16.3
30
39.3
156.4
-14%
58%
5.1
5.0
0.0
0.0
4.2
0.2
0.0
0.1
0.2
0.0
0.7
4.7
210
6.1
Adding a carrier (1)
Assumptions
Adding a carrier leads to less transmit power per carrier, if no
additional Power Amplifier is installed
Even with less transmit power, there is a capacity gain possible
for high traffic areas (low cell range)
No adjacent channel interference considered in this simulation
Coverage gain strongly depended on traffic mix -> not
considered here
211
6.1
Uplink
Coverage:
Link Budget
curve stays the
same, traffic
curve depends
on # of carriers
Uplink Capacity:
doubling # of
carriers:
~doubled
uplink capacity
Total Interference I (dB)
Basics for Uplink
18
16
link budget curve
I(Traffic),1 carrier
I(Traffic), 2 Carriers
14
12
10
8
6
4
2
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
Cell Range R (km)

212
6.1
UL Coverage gain - Examples

Dense Urban
1 TRX
2 TRX
3 TRX
1 TRX
two TRX 3 TRX
0,377
0,386
0,389
0,318
0,357
0,370
14%
7%
5%
53%
29%
20%
0,277
0,291
0,295
0,197
0,249
0,267
Cell range/km
UL load
Site area /sqkm
Results consider
upgrade from 1
carrier to 2
carriers and
from 1 carrier to
3 carriers
# of sites for
reference coverage
area of 1000sqkm
Gain in # of sites
Cell range/km
UL load
Site area /sqkm
# of sites for
reference coverage
area of 1000sqkm
Gain in # of sites
3608
3442
5%
3389
6%
5071
4024
21%
3746
26%
Rural
1 TRX
2 TRX
3 TRX
1 TRX
two TRX 3 TRX
4,945
5,170
5,248
4,397
4,899
5,065
26%
14%
9%
51%
28%
20%
47,683
52,121
53,706
37,701
46,800
50,026
21
19
9%
19
11%
27
21
19%
20
25%
213
6.1
Adding a carrier means:
reducing power per carrier

(20W 2x10W)
Downlink Coverage:
Power Amplifer
Carrier
TX
Antenna 1
C1
PA
C2
Gain is dependent on traffic density and cell range
Antenna
10 W per carrier
TEU
Downlink Capacity:
Capacity is not doubled when doubling # of carriers because of power reduction
per carrier
Gain depends on the hardware configuration (Note of PA per sector, # of carriers,
etc) and cell range
214
6.1
DL Coverage gain - Example

NRT 128 kbps / URBAN
Throughput per sector (kbit/s)
2500
2000
24 Watts per carrier - 1 carrier
10 Watts per carrier - 2 carriers
5,3 watts per carrier - 3 carriers
Traffic Curve (low traffic/km)
Traffic Curve (high traffic/km)
1500
1000
500
0
0
0,2
0,4
0,6
0,8
Cell Radius (km)
215
6.1
DL capacity gain (rural)

Capacity gain due to add. carriers in RURAL area
NRT 128 kbps/ RURAL
100,0%
80,0%
Capacity gain (%)
60,0%
(24W,1C)>(24W,2C)
(24W,1C)>(10W,2C)
40,0%
(10W,2C)>(10W,3C)
(10W,2C)>(5.3W,3C)
20,0%
0,0%
0
10
11
12
13
14
15
-20,0%
Cell range (km)
216
6.1
DL capacity gain (urban)

Capacity gain due to add. carriers in URBAN area
NRT 128 kbps/ URBAN

100,0%
Capacity gain (%)
75,0%
(24W,1C)>(24W,2C)
50,0%
(24W,1C)>(10W,2C)
(10W,2C)>(10W,3C)
25,0%
(10W,2C)>(5.3W,3C)
0,0%
0
0,5
1,5
2,5
-25,0%
Cell range (km)
217
6.1
DL Capacity gain - Typical Values

Example for monoservice NRT 128kbit/s and fixed intersite
distances, high traffic scenarios
Carrier configuration
1C>2C
2C>3C
DL Capacity gain
1 PA
Dense Urban
Urban
Suburban
350m
550m
1700m
92%
87%
77%
41%
37%
27%
Rural
7km
60%
15%
218
6.2
Design optimization based on drive measurements

Objective:
to be able to describe briefly the principles of

optimization based on drive measurements
to be able to suggest countermeasures which

can be taken to solve typical problems
219
6.2
Overview
Step 1
Defne Measurement Areas
Step 2
Defne Measurement Test Cases
Step 3
Perform Measurements
Step 4
Analyze results and modify design
Step 5
Re-launch predictions
220
6.2
Step 1: define Measurement Areas
First, the regions and routes have to be defined on the map where
measurements (and, consequently, the measurement based
optimization) should be carried out.
In the first UMTS networks, there used to be a sub-division of the
network into so-called clusters of about seven sites. The
advantage of such a relatively small network region is the lower
complexity, the drawback is that there are a high number of border
regions between the clusters which are not optimally treated.
When sub-dividing into clusters, it is important not to define the
clusters at an early stage of the network planning process in a rigid
way, but with high flexibility during the TOC (turn-on-cycle). As soon
as a contiguous area of about seven node B is on air, they can
constitute a cluster to be measured.
221
6.2
Step 2: define Measurement Test Cases

Measurement test cases have to be fixed:
In general, 3G scanner measurements in combination with
trace mobile measurements on a dedicated channel are
performed. The 3G scanner measurements give the received
CPICH RSCP and Ec/Io values for all received cells.
The UE measurements give (among others) the SIR on the
dedicated channel and the cells in the active set. In addition,
they give an indication on critical points of network quality by
call drops, reduced bit rate etc.
Note that the settings of the network (office data, OCNS power)
have to be known at the time of the measurement, otherwise, no
analysis is possible.
222
6.2
Step 3 to 5
Step 3: Perform measurements

Measurements have to be performed according to test cases.
Please take care of detailed documentation (e.g. on office data
settings, on measurement conditions, points and routes....).
GPS coordinates have to be traced along with the measurements
Step 4: Analyze Measurement Results and Modify Design
The measurement result analysis has to identify critical points
and the reason for them being critical
see next slides for typical problem sources and the potential
countermeasures
Step 5: Re-Launch Prediction
The predictions (described in 4) have to be re-launched with the
modified design.
The planner has to repeat the loop (design modification
prediction) until she/he is satisfied with the result (interference
sufficiently low, coverage acceptable)
223
6.2
CPICH level coverage
Typical problems and potential

countermeasures (1)
CPICH coverage problems occur when the pathloss is getting too

high and the received CPICH level (RSCP) is dropping below the
minimum required value.
Problem indication:
RSCPBest < RSCPmin (RSCP of Scanner preferred), where RSCPmin
is the threshold value for CPICH RSCP reception
and/or
There is a call drop or significant bit rate reduction in a region
where the CPICH RSCP monitored by the scanner is very low.
Countermeasures: can you suggest some countermeasures?
Countermeasures for insufficient CPICH level coverage:
Adapt antenna direction (azimuth and/or tilt) of best possible server
Potential Problem of this solution:
There is a trade-off between CPICH level and CPICH quality coverage. This measure enhances RSCP but may decrease Ec/Io
Add new site
Increase the CPICH Power of the cell with RSCPBest.
Potential problems of this solution:
The interference for other cells may be increased. In addition, there is less downlink power for the DCH (i.e. the traffic channels) left.
This means a reduced capacity.
224
225
Countermeasures for insufficient CPICH quality:

Reduce the own cell size if the reason for low Ec/Io is mainly intra cell load, to reduce the load (does not work in fxed load
scenario!). Note: In this case, another cell has to overtake the remaining load.
Possibilities to reduce own cell size are
1. increase downtilt
2. reduce CPICH transmit power
(Note that in this case, not only the load and therefore Io is reduced, but also the useful signal, i.e. Ec is reduced, so that there
may be no amelioration of the situation)
Reduce cell overlap of serving and interfering cell if the reason for low Ec/Io is extra cell load, by changing
1.
antenna tilt,
2.
antenna azimuth
3.
antenna height
4.
CPICH transmit power.
First try to change the interferer (reduce Io). If this is not possible, change server (increase Ec).
Adding a site: If the reason for low Ec/Io is both extra-cell and intracell load, then adding a site will decrease the load in the serving
cell and in surrounding cells and will therefore decrease both intracell interference and extracell interference (does not work in fxed
load scenario! Therefore, adding a site should always reduce the fixed load requirements for acceptance.)
If the reason is low Ec and Io is close to No, then the CPICH level coverage is the problem (see previous slide)
CPICH quality
CPICH quality problems occur in case of high interference. The received
CPICH Ec/Io is dropping below the minimum required value. The CPICH
quality is in contrary to the CPICH level coverage depending on the intracell load, the extra-cell load and the interference caused by extra-cell
Common Channels.
Problem indication:
((Ec/IoBest < Ec/Iomin) AND (RSCPBest > RSCPmin)) (to be measured by
Scanner)
and/or
There is a call drop or significant bit rate reduction in a region where
the Ec/Io monitored by the scanner is very low and where the RSCP
has still a high enough value.
Countermeasures: can you suggest some countermeasures?
6.2

countermeasures (2)
6.2

countermeasures (3)
Pilot Pollution
Pilot pollution occurs if more received cells are fulfilling the criteria to enter
the active set than the number allowed by the active set size. The criterion
is the received CPICH quality given by the parameter Ec/Io. The cell
received with the highest Ec/Io is assumed to be serving cell, i.e. it is in the
active set. Cells with a Ec/Io value, which is not more than YdB (typically
5dB) lower than the best Ec/Io, are assumed to be in the active set as well
under the condition that the maximum active set size (typically 3) is not
exceeded. All other cells fulfilling the Ec/Io criterion are polluters.
Problem indication:
More than X CPICHs detected by Scanner with Ec/Io within the interval
[Ec/IoBest Y, Ec/IoBest] (Typically: X=3; Y=5dB)
Countermeasures:
Identify the cells received within [Ec/IoBest Y, Ec/Io Best]
Decide which cells should not be received within [Ec/Io Best Y, Ec/IoBest]
and change their design
Increase Ec/IoBest by changing design of best server
Following ranking is valid for design changes:
1. Adapt antenna tilt (i.e. reduce interference)
2. Adapt antenna azimuth (i.e. redirect interferers towards less critical
regions)
3. Adapt antenna height (i.e. reduce interference)
226
4.
Adapt
pilot
power
All rights reserved
Alcatel
- 3FL 11194
ABAA
WBZZA Ed.01P04
6.2
Handover definition

countermeasures (4)
Missing handover definitions (i.e. missing neighbors) can lead to sever

quality problems and call drops, since the missing neighbor is not only not
serving the mobile but in addition producing high interference.
Problem Indication:
The best cell shown in the 3G scanner measurement does not enter
the active set of the mobile.
Scrambling_CodeBestEc/Io(Scanner) Scrambling_CodeBestEc/Io(UE)
Countermeasures:
Declare missing neighbor definition at OMC if the cell with Ec/Io Best
reported by the scanner is wanted to be in the active set
Change the cell design of the cell reported by the scanner with Ec/Io Best
, if this cell is not wanted to be the best server resp. to be in the active
set
227

Duratio
n:
1h00
7. UMTS/GSM co-location and

Antenna Systems
228
7. UMTS/GSM co-location and Antenna Systems
Objective:
to be able to describe briefly the interference
mechanisms due to GSM/UMTS co-location (cositing) and the solutions for antenna systems
(antenna, feeder, diplexer)
Program:
Interference mechanisms due
to co-location
Spurious emissions
Receiver blocking
Intermodulation products
Summary on required
decoupling required for
the 3 interference
mechanisms
UMTS-UMTS co-location
Antenna solutions
Dual band sites GSM 1800
- UMTS FDD
Dual band sites GSM 900 UMTS FDD
Triple band sites GSM 900
- GSM 1800 - UMTS FDD
Feeder sharing impacts
TMA in co-location
configurations
TMA in feeder sharing solutions
229
The Interference Mechanisms

Overview
Transmitter noise/spurious emissions (in band interference)
The transmitter noise floor and the spurious
transmissions could fall into the receive band of the cosited system
Receiver blocking (out of band interference)
The transmit signal of one system could block the
receiver of the other system
Intermodulation products
Intermodulation products could interfere the receivers of
one or both systems
230
Transmitter Noise / Spurious Emissions

Most critical: GSM 1800/UMTS
Noise floor and spurious transmissions from the GSM
1800 BTS falling into the Node B receive band
Historical reason: GSM1800 Filter specification (ETSI)
Out of band interference for the

UMTS system (non ideal UMTS
receiver!)
additional filter required
GSM 1800 DL
In band interference
UMTS/FDD
UL
1880
1920
f/MHz
231
New 3GPP TS 05.05 (V8.5.1)

Stronger Requirements for GSM base stations co-located with 3G
Spurious Emissions of GSM Base Station in old spec:
< -45 dBm/100KHz means <-29 dBm/3.84MHz
Spurious Emissions of GSM Base Station in new spec:
Same service area, no co-location
<-62 dBm/100kHz means <-46dBm/3.84MHz
Same service area, co-location
Increase of
<-96 dBm/100kHz means <-80dBm/3.84MHz
decoupling
requirement in case
Values are valid in 3G receive band
of GSM UMTS colocation of 51 dB!
900-1920 TDD, 1920-1980 FDD UL, 2010-2025 TDD
232
Alcatel Values
Alcatel GSM 1800 BTS has a spurious emission :
-80 dBm/3.84MHz (3GPP co-location requirement)
Alcatel MBS 9100 has a limiting interference level
requirement of:
-114 dBm/3.84MHz (calculation in slide 8)
The disturbance of UMTS NodeB by Alcatel GSM 1800
spurious emissions can easily be avoided by
providing additional 34 dB decoupling
see following slides
233
Spurious Emissions GSM1800 UMTS (1)

Antenna system
Calculation on next slide

Spurious emissions
Old ETSI : < -29 dBm
Alcatel and new 3GPP < -80 dBm
Antenna
connectors
ANC
Attenuation in UMTS
TX/ RX
TRX
Limiting interference level:

< - 114 dBm
MBS 9100
Evolium TM BTS 1800
234
Equipment
type
Spurious
emissions
(at BTS/ Node
B antenna
connector)
Limiting
interference
level
ETSI specifcations (GSM 05.05)

up to v.8.4.1
v.8.5.1
-29dBm
-80dBm
Alcatel EVOLIUM GSM

1800 BTS
-80 dBm
Noise at UMTS receiver without GSM 1800 impact:

Thermal noise (-108 dBm) plus receiver noise figure (4 dB), i.e. 104 dBm
(Pnoise [dBm] = -174 dBm + System Noise Figure [dB] + 10 log (BW [Hz])
Degradation of sensitivity by 0.4 dB acceptable
(level 10 dB below noise floor)
-104 dBm 10 dBm = -114 dBm
Required
decoupling
up to v.8.4.1
v.8.5.1
-29 dBm
-80 dBm
decoupling = -114 decoupling = -114
dBm
dBm
-80 dBmdecoupling =
-114 dBm
Decoupling = 34 dB
Decoupling = 85 Decoupling = 34
dB
dB
235

For BTSs only compliant to the old ETSI GSM 05.05 v.8.4.1
the standard air antenna de-coupling is not sufficient in GSM
1800 and UMTS systems are co-located.
In case of a GSM 1800 BTS fulfilling only the old ETSI
GSM 05.05 v.8.4.1 requirements the air de-coupling has
to be 81 dB
In order to know the exact required de-coupling value,
the blocking performance of the according equipment
has to be known.
De-coupling measurements have to be performed in
order to determine the required minimum distance
between antenna panels.
236
Spurious Emissions GSM900 UMTS

No problem for any GSM 900 base station, conform to old ETSI
specification
For the minimum decoupling between the antenna ports of two colocated Node Bs, the following has to be valid:
-80 dBm decoupling = -114 dBm
Decoupling = 34 dB
Therefore, if we have a standard decoupling between the
antennas of 30dB and a feeder cable loss of 2dB on each side,
the decoupling requirement is fulfilled.
237
Receiver blocking
Critical: Node B transmitter blocking co-located GSM 900,
GSM 1800 or UMTS/FDD receiver
Reason: Filter in RX system (blocked system)
GSM antenna
UMTS antenna
Decoupling
Feeder
loss
RX blocking
GSM BTS
Feeder
loss
TX power
UMTS
Node B
238
Receiver blocking
Link Budget for Blocking Evaluation
Example: UMTS blocks receiver of GSM1800
Link budget
Value
UMTS Node B TX output power
43.0 dBm
Assumed antenna decoupling
- 30 dB
Assumed feeder and connector loss
0 dB
GSM 1800 received power (@ 2000 MHz)
13.0 dBm
Specifcation
3GPP
Alcatel
GSM 1800 blocking limit
0 dBm
23 dBm
Blocking limit fulflled
No
Yes
239
Receiver blocking
Critical: Node B being blocked by co-located GSM 900, GSM
1800 or UMTS/FDD
GSM antenna
UMTS antenna
Decoupling
Feeder
loss
Feeder
loss
TX power
GSM BTS
Problem doesnt occur

for Alcatel Node B
thanks to ANXU filter
specification
RX Blocking
UMTS
Node B
242
Receiver blocking
Link Budget for Blocking Evaluation
Example: GSM 1800 blocks receiver of UMTS
Link budget
GSM 1800 TX output power (high power)
Value
46.7 dBm
Assumed antenna decoupling
- 30 dB
Assumed feeder and connector loss

UMTS received power (@ 1800 MHz)
Specifcation
UMTS blocking limit
Blocking limit fulflled
0 dB
16.7 dBm
3GPP
Alcatel
-15 dBm
23 dBm
No
Yes
244
Receiver blocking
Conclusion
It can be stated that receiver blocking is no problem for
co-located Alcatel equipment assuming an antenna
decoupling of 30 dB (and even less). Co-location with
equipment from other suppliers needs to be checked
case-by-case.
245
Intermodulation Products
Cause: distortion in non-linear devices
Frequency spectrum of non-linear devices output signal has more components
than the input signal:
either harmonics of the input frequencies
or a combination of the input components (mixing).

fIM = m f1 + n f2
with m, n = 0, 1, 2, 3, ...
|m|+|n| is called order of the intermodulation product

The intermodulation interference is critical for co-located GSM 1800 and UMTS
systems.
The 3rd order intermodulation product is the most critical one
GSM 1800 TX within UMTS RX band (e.g. 2 x 1879.8 MHz 1 x 1820 MHz =
1939.6 MHz)
246
Intermodulation in the GSM 1800 transmitters.
The figure shows schematically the creation of the IM3
intermodulation product in the GSM 1800 transmitters, interfering
a co-sited UMTS Node B:
Towards the antenna / diplexer system
f1
f2
Diplexer or
air decoupling
TX/ RX
Antenna
coupling network
TX
RX
GSM BTS
TX/ RX
Antenna
coupling network
TX
RX IM3
UMTS Node B
247
Intermodulation in the UMTS receiver
Transmit signals from co-sited system are fed into the receivers
producing intermodulation
Towards the antenna / diplexer system
f2
f1
Diplexer or
air decoupling
TX/ RX
Antenna
coupling network
TX
RX
GSM BTS
TX/ RX
Antenna
coupling network
TX
RX
IM
UMTS Node B
248
Intermodulation at the diplexers
Combination of TX signals from different transmitters generate
intermodulation products
Towards the antenna
Diplexer
interfering transmit signals
Diplexer or
air decoupling
TX/ RX
Antenna
coupling network
TX
RX
GSM 1800 BTS

intermodulation
product
TX/ RX
Antenna
coupling network
TX
RX
This scenario is
very critical and must
be avoided with
accurate frequency
planning.
UMTS Node B
249
Intermodulation Products: conclusion

Interference in UMTS receive band:
3rd order product only critical if fIM = -1f1 + 2f2 falls within
UMTS receive band
For UMTS frequencies>1955 MHz, no IM3 products can occur.
In general if fIM = -1f1 + 2f2 <1920 MHz no
disturbance in UMTS system sue to IM products.
Interference in GSM bands:
Avoid intermodulation products by careful frequency planning
in the GSM bands
Diplexer or filter reduces some of the effects
More decoupling between the systems
250
Summary on the required Decoupling
It is assumed, that the

decoupling provided by
the antenna/diplexer
system is at least 30
dB. In fact, using Alcatel
EVOLIUM equipment
requires for certain
combinations even less
isolation than those
30dB
Intermodulation is
suppressed by
frequency planning
GSM 900 (RX)
GSM 1800 (RX)
GSM
05.05
GSM
05.05
Alcatel
3G TS
25.104
Alcatel
GSM 05.05
46 dB
Blocking
30 dB
v.8.5.1:
34dB
GSM
spurious
v.8.5.1:
34dB
GSM
spurious
Alcatel
46 dB
Blocking
30 dB
61 dB
Blocking
30 dB
v.8.4.1:
85 dB
v.8.4.1:
85 dB
v8.5.1:
34dB
GSM
spurious
v8.5.1:
34dB
GSM
spurious
62 dB
Blocking
Specification
according to:
Alcatel
GSM 900 (TX)
GSM 05.05
GSM 1800 (TX)
GSM 900-GSM 1800

decoupling values are
added for
completeness, although
not treated throughout
this document
UMTS (TX)
39 dB
Blocking
30 dB
Alcatel
39 dB
Blocking
30 dB
3G TS 25.104
35 dB
Blocking
30 dB
Alcatel
35 dB
Blocking
30 dB
43 dB
Blocking
43 dB
Blocking
UMTS (RX)
30 dB
58 dB
Blocking
34 dB
GSM
spurious
34 dB
Spurious
30 dB
58 dB
Blocking
34 dB
Spurious
251
UMTS - UMTS co-location (FDD)

Capacity Loss due to adjacent operators co-existence
Danger of Dead Zones in case of operator co-existence
f1
f2
Dead zone area
Serving cell (Operator A)

Interfering cell (Operator B)
Co-location of UMTS operators avoids occurrence of dead zones
252
Co-location: Conclusion
Co-siting of GSM and UMTS possible
Co-siting of two adjacent UMTS operators desirable to avoid
dead zones
Alcatel EVOLIUMTM base stations are prepared for co-siting
Alcatel can provide solutions for co-siting of Alcatel GSM
and/or UMTS base stations with equipment of any other
supplier
253
Antenna Solutions
Dual-band sites GSM 1800 - UMTS FDD
Triple-band sites GSM 900 - GSM 1800 - UMTS FDD
Multi-operator sites UMTS-UMTS
254
Dual-band Sites GSM 1800 - UMTS FDD

Air Decoupling with Single-band Antennas
GSM 1800 antenna
UMTS antenna
Vertical or cross
polarized
air decoupling
Feeder
GSM 1800
BTS
Feeder
UMTS
Node B
Vertical or horizontal
separation
Independent antenna
characteristics (pattern,
downtilt, gain)
255
Separation for air-decoupling
For Alcatel EVOLIUMTM

GSM1800 BTS
Horizontal Separation:
dh=0.6m
Vertical Separation:
GSM 1800
dh
dv=0.5m
dv
Provides already a
decoupling of >47dB
UMTS
GSM 1800
UMTS
Note: Values for RFS/CELWAVE antennas APX206515-2T (UMTS) and APX186515-2T

(GSM 1800)
256
Decoupling measurements
To determine the required minimum distance between the

antenna panels, decoupling measurements have to be performed.
d
-45 +45
GSM 1800
-45 +45
UMTS
Spectrum
analyzer
Decoupling between -45 plane of GSM 1800

antenna and +45 plane of UMTS antenna over
the frequency for distance d.
257

Broadband antenna with diplexer or filter
Less flexible - same antenna characteristic for both bands
Broadband antenna
Feeder
Diplexer
GSM 1800
BTS
UMTS
Node B
Example:
Celwave APX18/206515T6
258

Dual-band antenna with diplexers
Example: Celwave APX15D6/15W6
Independent on gain and electrical downtilt

feeder sharing
Dualband antenna
Diplexer
Feeder
Diplexer
GSM 1800
BTS
UMTS
Node B
259
Dual-band antenna with filters

Independent on gain and electrical downtilt
Four feeders per panel
Filter to reduce decoupling requirements
Dualband antenna
Dualband antenna
Feeder
Feeder
Feeder
Filter
Alcatel
Evolium
GSM 1800
BTS
Alcatel
Evolium
MBS
UMTS
GSM05.05
v.8.4.1.
GSM 1800
BTS
Feeder
Filter
TS 25.104
UMTS
Node B
260
Dual Band Sites GSM 1800 / UMTS FDD
Solutions with RFS Celwave components
DCS UMTS
DCS UMTS
DCS
+
UMTS
Diplexer
FD DW 6505-1S
75 dB
Broadband
Antenna
75 dB
BTS BTS
DCS UMTS
75 dB
75 dB
BTS BTS
DCS UMTS
BTS BTS
DCS UMTS
Band 1 : GSM1800
Band 2 : UMTS
Full DC block
75dB of decoupling
Series expected
04/2002
261
Antenna Solutions
262
Solutions without Feeder Sharing

GSM 900 antenna
UMTS antenna
GSM900/UMTS Dualband antenna

air decoupling
Feeder
Feeder
Feeder
GSM 900
BTS
UMTS
Node B
Single band antenna configuration

GSM 900
BTS
Feeder
UMTS
Node B
Dual band antenna configuration

263
Feeder Sharing solution
Also possible with single

band antennas
Dualband antenna
Diplexers have to
provide 30dB of
decoupling
Diplexer
Feeder
Diplexer
GSM 900
BTS
UMTS
Node B
264
Dual Band Sites GSM 900 / UMTS FDD
Solutions with RFS components
GSM UMTS
Diplexer
55 dB
Band 1: AMPS/GSM
Band 2: DCS/UMTS
FD GW 5504 -1S
->full DC pass
55 dB
BTS BTS
GSM UMTS
FD GW 5504-2S is:
->DC Block in lower bands
->DC Pass in higher bands
Product is available
01/2002
265
Antenna Solutions
266
Triple-band sites for GSM 900/1800 and UMTS

With three independent single-band antennas
With dual-band and single-band antennas
GSM 900 single-band, GSM 1800 / UMTS dual-band
GSM 1800 single-band (preferred), GSM 900 / UMTS dual-band
UMTS single-band, GSM 900 / GSM 1800 dual-band
With triple-band antennas
267
Triple-band antennas for GSM 900/1800 and UMTS
Triple-band antenna
Connection matrix
Filters not required

for Alcatel
EVOLIUM
equipment!
Diplexer
Feeder
Feeder
Feeder
Connection Matrix
Filter
Diplexer
GSM 1800
GSM 900
BTS
GSM 1800
BTS
UMTS
Node B
Feeder
UMTS
Diplexer application
Filter
GSM 1800
UMTS
Filter application
268
Antenna Solutions
269
Multi-operator sites: UMTS FDD-UMTS FDD

Solutions without feeder sharing. Two
completely separate systems with air
decoupling
Different sector orientation possible
Different tilt can be set up
Operator independence
UMTS antenna
UMTS antenna
air decoupling
Simple solution
Careful RNP: antenna patterns must
not interfere.
High visual impact
2 feeders needed for each operator
Feeder
UMTS
UMTS
Node B
Node B
Operator1
Feeder
Operator2
270

Solutions without feeder sharing. Two
operators sharing one antenna panel
Different electrical tilt can be set
up.
Low visual impact.
Dual UMTS antenna

(or Dual Broadband antenna)
Each operator can use TMA if

desired.
Sector orientation cannot be
chosen independently.
2 feeders needed for each
operator.
Feeder
UMTS
Node B
Operator 1
Feeder
UMTS
Node B
Operator 2
271

Two operator sharing one
antenna (feeder Sharing)
Low visual impact
2 feeders needed
UMTS antenna
Same electrical tilt, same

sector orientation
TMA not possible
High losses due to splitter:
3.3 dB
The two former solutions
are more recommendable!!
Feeder
~3.3dB loss!
UMTS
Node B
Operator 1
Hybrid
(Splitter/Combiner)
UMTS
Node B
Operator 2
272
Antenna Feeder Sharing for Dual-band Sites
Dual-band
antenna
Dual-band
antenna
+45
Diplexer
Without
diplexers
Feeder
Dual-band
With
integrated
diplexers
Diplexer
Feeder
Diplexer
Additional filter depending

on equipment type and
vendor required in the
GSM 1800 branch.
-45
Diplexer
Diplexers
at BTS/Node B
location
Dual-band
273
Antenna Feeder Sharing for Triple-band Sites
GSM 900
Triple-band
antenna
GSM 1800
GSM 900
Triple-band
antenna
UMTS
UMTS
30 dB isolation
Diplexer
Triplexer
Feeder system
Diplexer
Triplexer
Antenna system
Lower losses
Diplexer
sector
Four feeders per
Antenna system
Easy migration
Two feeders per sector
GSM 1800
50 dB isolation
Diplexer
GSM 900
GSM 1800
UMTS
Diplexer
Feeder system
Diplexer
BTS systems
GSM 900
GSM 1800
UMTS
BTS systems
274
Feeder sharing losses

The next table collects the additional losses.
Component
Loss
Diplexer GSM 900-GSM 1800
0.3 dB
Diplexer GSM 900-GSM 1800 / UMTS
0.3 dB
Diplexer GSM 900-UMTS
0.3 dB
Diplexer GSM 1800-UMTS
0.5 dB
GSM 1800 filter (not necessary for Alcatel

equipment!)
(0.4 dB)
275
Feeder Sharing losses

Additional losses due to diplexers: Example
GSM 900
Antenna systems
GSM 900
GSM 1800
Worst Case Values!
UMTS
Influence of feeder sharing (losses in dB)

Components
Diplexer
Diplexer
Triplexer
2 Diplexers GSM
900-GSM 1800
GSM
900
GSM
1800
UMTS
0.6
0.6
0.6
1.0
1.0
2 Diplexers GSM
1800-UMTS
Feeder system
Triplexer
Diplexer
Additional losses
(jumpers, connectors)
0.5
0.5
0.5
Total loss
1.1
2.1 1)
2.1 1)
Diplexer
GSM 900
BTS systems
GSM 900
GSM 1800
UMTS
1) Remark: GSM 1800/ UMTS signals have

50 % more signal attenuation compared
with GSM 900 signals over the same feeder
cable.
276
Antenna feeder sharing: conclusion

Feeder sharing is recommended or even mandatory when:
The building or tower does not allow to add more feeder cables.
If the distance between the BTS/Node B and the antenna is
rather long.
Additional diplexers are cheaper compared to the material
plus installation costs of the feeder cable. The losses due
to the diplexers are, compared to the feeder losses, not so
important any more.
Feeder sharing should not be used as general implementation when
not really necessary.
Especially for the higher frequency bands, the additional losses
due to the diplexers should be avoided.
277
TMA in co-location configurations
TMA improves the effective

receiver chain noise figure
(compensation of feeder losses)
Increase of cell range in case of
uplink limitation
Additional loss of 0.5 dB in
downlink
Antenna
Duplexer
TMA
Tx
Rx
Duplexer
Feeder
Tx / Rx
BTS /
Node B
278
TMA in co-location configurations
In case there are TMAs installed in the GSM 900 or GSM 1800 part of
the co-siting configuration, we have to check the following points:
Blocking limit of the BTS:
The signal delivered by the TMA to the base station receiver
will be higher which may be resulting in blocking. If the
blocking limit is too low, we have to increase the decoupling.
Blocking limit of the TMA:
The TMA must not be blocked by the incoming signal. If the
blocking limit is too low, we have to increase the decoupling.
For the Alcatel UMTS TMA and EVOLIUMTM MBS UMTS, these points have
already been checked and do not constitute a problem. In case other
suppliers equipment is used, an according check has to be performed.
279
Examples for TMA usage
Solutions with RFS components
Diplexer
DCS GSM UMTS
DCS UMTS
FD GW 5504-2S
(avail: 01/2002)
TMA
75 dB
TMA
DC pass
TMA
55 dB
DC block
DC block in Band1
(GSM900)
DC pass in Band 2
(UMTS)
Diplexer
FD DW 6505-2S
(avail: 04/2002)
55 dB
75 dB
75 dB
BTS BTS
DCS UMTS
+
PDU
DC block
DC pass
DC block in Band 1
(GSM1800)
DC pass in Band 2 (UMTS)
DC pass
BTS BTS BTS

DCS GSM UMTS
+
+
PDU
PDU
TMA
ATM W 1912-1
280
TMA in feeder sharing solutions

The Feeder sharing solutions require diplexers, avoiding DC passing
into antenna
DC on feeder is required to feed the TMA with power
It has to be noted that for each TMA a separate feeder cable has to
be used. Otherwise Evolium does not support
DC feed
Alarm handling
281
Antenna Systems: Conclusion

Wide variety of antenna system solutions for all co-location
combinations
No killer solution, pre-conditions and operator requirements have

to be checked case by case
282
Appendix
Open loop/Closed loop
Frequency coordination at country borders
COST231- Hata formula
Cell parameters (Network Design Parameters - cell wise)
283
Appendix
Open loop power control
Open loop power control
1
Node
B
2
1
Node
B
2
If UE receives a STRONG DL
If UE receives a weak DL
signal,
signal,
then UE will speak low.
then UE will speak LOUD.
Problem:
fading is not correlated on UL and DL due to separation of UL and
DL band.
Open loop Power Control is inaccurate.
284
Appendix
Closed loop power control

DL:
Inner loop: the Node-B controls the power of the UE by performing a SIR
estimation:
Outer loop: the RNC adjusts (SIR)target to fulfill the required service quality (e.g.
BER<10-2)
(SIR)measured > (SIR)target Power down command (Step=1 dB)
----------------<------------- Power up--------------------------------- UL:
Inner loop: same as DL, but SIR estimation performed by the UE

Outer loop: same as UL, but (SIR)target adjusted by the UE
The SIR estimation is performed

each 0,66 ms (1500 Hz command
Outer loop
Inner loop rate) Closed
loop Power Control is very fast
Example
in DL
RNC
SIR
targe
t
Node
B
SIR Power down

estimation
SIR
Power ...
estimation
...
285
Appendix
Frequency coordination at country borders(1)

Method based on ERC Recommendation (01) 01 to be found at
European Radiocommunications Office (http://www.ero.dk )
ERO is a associated with the CEPT (European Conference of Postal
and Telecommunications Administrations)
1) National frequency and code planning for the UMTS/IMT-2000 is
carried out by the operators and approved by the Administrations or
carried out by these Administrations in co-operation with the
operators.
2) Frequency and code planning in border areas will be based on
coordination between Administrations in co-operation with their
operators
286
Appendix

Administrations concerned shall agree on preferred code
groups / code group blocks if center frequencies are aligned
No coordination between is necessary if:
Band
[MHz]
Pre-conditions
(one must be fulfilled )
Predicted mean FS
level of each carrier
must be below
Where?
2110-2170
1) Preferential codes usage
45 dBV/m/5MHz
3 m above ground
at border line and
beyond1
2) Center frequencies not

aligned
FDD DL 3) No IMT2000 CDMA radio
1
to be negotiated
by both parties
interface used
1900-1980
2010-2025
1) Preferential codes usage
36 dBV/m/5MHz
3 m above ground
at border line and
beyond1
21 dBV/m/5MHz
3 m above ground
at border line and
beyond1
2) Center frequencies not

aligned
Any
FDD UL
1) no preferential codes used
TDD
287
Appendix

Administrations on both sites of the border
must agree on preferential, neutral and
non-preferential frequencies
e.g. the administrations agree on the
following split (assuming 3 available
Frequency type
Country A
frequencies):
Country B
Preferential
F1
F3
Neutral
F2
F2
Non-preferential
F3
F1
this split is leading to the following

allowed FS level thresholds
Used frequency type
Allowed max. FS level at

border and beyond1
Preferential
65 dBV/m/5MHz
Neutral
45 dBV/m/5MHz
Non-preferential
45 dBV/m/5MHz
288
Appendix
If a non preferential frequency is used, the operator accepts

possible capacity loss in his system due to interference
coming from the high allowed FS level on his side of the
border emitted by the operator of the other country
Country A
(Neutral)
Country B
(Neutral)
45 dBV/m/5MHz 45 dBV/m/5MHz
Country A
(Preferential)
Country B
(Non-preferential)
65 dBV/m/5MHz 45 dBV/m/5MHz
Interference to Rx accepted
(potential capacity loss)
Equal field strength limits at border
289
Appendix

at least the following characteristics should be forwarded to the
Administration affected (more details in ERO T/R 25-08 E)
frequency in MHz
name of transmitter station
country of location of
transmitter station
geographical co-ordinates
effective antenna height
antenna polarisation
antenna azimuth directivity
in antenna systems
effective radiated
power
expected coverage
zone
date of entry into
service.
code group number
used
antenna tilt
290
Appendix
Cost 231-Hata formula

Reminder: Cost-Hata formula
f
hT
hT
log
log
3
2
1
MHz
m
m
LCOST Hata A1 A2 log
d
log 3 C hR
m
Mapping between COST-Hata and Standard Propagation Model

Alcatel UMTS
COST-Hata
Standard Model
Parameter
K1
A1+A2log(f/MHz)3B1 0.87
K2
B1
K3
A33B2
K4
K5
B2
K6
C(hR)
KClutter
Compared to COST231-Hata
propagation model, the Alcatel
UMTS Standard Propagation Model:
has an additional diffraction
loss represented by K4 has
been added
can be calibrated by adding
a clutter dependent calibration
offset
291
Appendix Cell parameters
Network architecture dimensioning

parameters(1)
Defnition
Parameter
Cell Name
Default value
Cell name
Site0_0(0)
Identifier of the cell in the system
Transmitter
name
Carrier
Scrambling
code
Cell class
Sector Name to which the cell belongs
Numerical value between 0

and 268435455
Site0_0
Carrier on which the cell is transmitting

Dl primary scrambling code
0-2
0-511
Identifier of the geographical

environment of the cell. The network
tuner/planner can define his own classes.
Cell type
Type of the cell, there is only one type of

cell.
4 Evolium predefined
classes: Dense Urban,
Urban, Suburban and
Rural
Single
Local cell Id
292
Network architecture dimensioning

parameters(2)
Parameter
Description
LAC
Location Area Code: LAC is a fixed length code that identifies a location
area within a PLMN. O ne LA consists of a number of cells belonging to
RNCs that are connected to the same CN node (UMSC or 3G-MSC/VLR).
Values between 0-65535
Service area Code: SAC is a fixed length code identifying a service area
within a location area, service area consists of one or more cells. (LA
Domain RNC No. + NodeB No. + Sector No.). Values between 0-65535
Routing Area Code: O ne RA consists of a number of cells belonging to
RNCs that are connected to the same CN serving node, i.e. one UMSC or
one 3G_SGSN. Values between 0-255
This parameter defines the Mobil Country Code. It is used for defining the
PLMN identity and therefore the Location Area Identity (LAI) and the
Routing Area Identity (RAI).
This parameter defines the Mobil Network Code. It is used for defining
the PLMN identity and therefore the Location Area Identity (LAI) and the
Routing Area Identity (RAI).
SAC
RAC
MCC
MNC
Default
0
0
0
999
999
293
Transmit power parameters (1)
Parameter
Max. Total
Power
(dBm)
Pilot Power
(dBm)
Description
Transmitter maximum power per carrier (cell).
Depends on Node B configuration.
Default Value
43 dBm
Pilot channel Power: Part of the cell maximum

transmit power that is dedicated to the CPCIH. This
value is fixed by the user and remains constant.
33 dBm
(10% of total available
carrier power)
SCH Power
(dBm)
Average Synchronization Channel Power.

Default: 5 dB less than the CPICH, thus P-SCH
21 dBm
and S-SCH have 28 dBm.
This value is fixed by the user and remains constant.
0.63 W+0.63W=1.26W 31 dBm, taking into
account that the SCH are transmitted only 10% of the
time 31 dBm 10 dB = 21 dBm,
294
Transmit power parameters (2)

Other common channels power
Parameter
Description
Default
BCH Power
This parameter defines the transmit power of the Broadcast Channel

relatively to the P-CPICH power (offset).
This parameter defines the maximum FACH power carried on the SCCPCH
relatively to the P-CPICH power (offset). When more than one FACH are
carried on the same S-CCPCH, each FACH has the same power.
This parameter defines the transmit power of the Paging Channel relatively
to the P-CPICH power (offset).
This parameter defines the transmit power of the Paging Indicator Channel
relatively to the P-CPICH power (offset). In fact, this value depends of the
number of Paging Indicators (PI) that are carried on the PICH.
This parameter defines the transmit power of the AICH relatively to the PCPICH power (offset). It depends of the number of Acquisition Indicators.
-2 dB
MaxFACHpow
er
PCHpower
PICHpower
AICH power
-2dB
-2dB
-5 dB
-9 dB
These channels are not transmitted 100% of the time, however it

is assumed that around 34 dBm are continuously transmitted on
the these channels, designed in A9155 as other common
channels
295
Handover parameters
Parameter
Description
AS threshold The active set threshold is the maximum pilot quality difference
(dB)
between the best server and a certain transmitter so that this
transmitter becomes part of the active set of a certain UE.
HO Margin
HO margin. RNO interface
HO Mode
HO mode. RNO interface.
Qoffset_sn
It is used for cell reselection procedure in order to favor one
cell.
Default
3 dB
3 dB
0 dB
296
Cell selection/reselection parameters
Parameter
Description
Default
Value
Cell Individual
offset
This information shows Cell individual offset. For each

cell that is monitored, the offset is added to the
measurement quantity (for ex CPICH Ec/Io) before the UE
evaluates if an event has occurred
This information shows Qoffset, n that is used for cell
reselection procedure in order to favor one cell.
Hysteresis value of the serving cell during cell
selection/reselection. It is used with CPICH RSCP
Hysteresis value of the serving cell during cell
selection/reselection. It is used with CPICH Ec/Io
Minimum required quality level (CPICH Ec/Io) in the cell
during cell selection/reselection.
Minimum required RX level (CPICH RSCP) in the cell
during cell selection/reselection.
0 dB
QoffsetsN
Qhysts1
Qhysts2
Qqualmin
Qrxlevmin
0 dB
4 dB
4 dB
-15 dB
-115 dBm
297
Solution of the exercises
298

1.2 UMTS RNP notations and principles(1)
Be careful in this exercise with:
dBm#dBW :
e.g. Thermal Noise = -204dBW = -174dBm
do not add power values in dBm:

e.g. 2dBm + 2dBm = 5dBm (= 10log (100.2 +100.2))
1. What is the processing gain for speech 12.2kbits/s ?

10 log (3.84Mcps/12.2kbps)=25dB
2. The users in the serving cell are located at different distance from the NodeB: is it desirable and
possible to have the same received power C for each user?
desirable: yes to avoid near-far effect
possible: yes by using power control
3. What is the value of the Thermal Noise at receiver N?
N=Thermal Noise+NFNodeB = -108.1dBm + 4dB = -104.1dBm
299

1.2 UMTS RNP notations and principles(2)
4. Complete the following table:
Iintra=n x C
Ieytra=i x Iintra=0.55 x Iintra (homogeneous network with i=0.55)
I = Iintra +Iextra= 1.55 x n x C
Noise Rise=(I+N)/N (see question 3 for N value)
Ec/No=C/(I+N-C)
Note: the following approximation can be used: Ec/No ~ C/(I+N) (because C<<N for a speech call)
Eb/No=Ec/No +PG (see question 1 for PG value)
I +N
[users]
[dBm]
[dBm]
Noise
Rise
[dB]
Ec/No
Eb/No
[dB]
[dB]
Comment
-118.1
-103.9
0.2
-15.9
9.1
Eb/No >>(Eb/No)req UE TX power is much too high
10
-108.1
-102.6
1.5
-17.3
7.7
Eb/No >(Eb/No)req UE TX power is too high
25
-104.1
-101.1
3.0
-18.9
6.1
Eb/No ~(Eb/No)req UE TX power is adapted to the traffic

load
100
-98.1
-97.1
7.0
-22.9
2.1
Eb/No <<(Eb/No)req UE TX power is much too low or traffic

load much too high
300

3.2 UMTS propagation model (1)
Exercise:
Lets consider the simplified* formula of the Alcatel Standard Propagation Model:
Lpath[dB] = C1 + C2 x log(dUE-NodeB[km])
Can you complete the table?
Be careful that the distances are expressed in meter in the full Alcatel standard
propagation model formula and in kilometer in the simplifed formula:
C1 + C2 log (d [km]) = {C1 C2 log1000} + {C2 log (d [m])}
C2 = K2 + K5 log HNodeB =44.9 + (-6.55) log 30 = 35.22 (HNodeB=30m)
{C1 C2 log1000} =K1+K3 log HNodeB +K4 f(diffraction) + K6 f(HUE)+Kclutterf(clutter)
=23.6 + 5.83 log 30 + 0 + 0 + f(clutter) (no diffraction)
=32.21 + f(clutter)
C1 = 32.21 + f(clutter) + C2 log1000 = 137.8 + f(clutter)
with f(clutter) = -3dB for dense urban and -8dB for suburban (homogeneous clutter
class around UE)
(see table on the next page)
301

3.2 UMTS propagation model (2)
*Assumptions:
-HNodeBeff=30m
-no diffraction
-homogeneous
clutter class
around the UE
Clutter
class
dUENodeB
[km]
Dense
Urban
f(clutter)=3dB
Suburban
f(clutter)=8dB
C1
[dB]
0.5
C2.log(dUE-NodeB )
[dB]
(C2=35.22)
Lpath
[dB]
-10.6
124.2
134.8
10.6
145.4
0.5
-10.6
119.2
129.8
10.6
140.4
134.8
129.8
Note: C1 and Lpath values can easily be deduced:

for urban clutter class: C1= 131.8 dB (f(clutter)=6dB)
for rural clutter class: C1=117.8dB (f(clutter)=20dB)
302

3.6 Cell Range Calculation (1)
UE power class 4
Speech12.2kbits/s
Vehicular A 3km/h
Deep Indoor
=8
UL load factor=50%
Comment
Value
in
f.a.=fxed
assumptio
n (see
previously
)

A1
UE TX power
21
A2
A3
EIRPUE
dBm
dB
see 2.3
f.a.
21
dBm
A1+A2
5.8
dB
see 2.2
25
dB
see 1.3
dB
f.a.

B1
(Eb/No)req
B2
Processing Gain
B3
NFNodeB
B4
Thermal noise
-108.1
dBm
f.a.
B5
123.3
dBm
B1B2+B3+B4
303

Value
in
Comment
f.a.=fxed
assumptio
n
(see
previously
)
C. Margins
C1
Shadowing margin
4.8
dB
see 3.3
C2
Fast fading margin
1.7
dB
see 3.3
C3
Noise Rise
dB
see 3.5
C4
0.1
dB
see 3.5
C5
Interference margin
2.9
dB
C3-C4
dB
f.a.
D2 Body loss
dB
see 2.2
20
dB
see 2.2
18
dBi
f.a.
126.9
dB
=?
D. Losses

margin)
E. Gains
E1
Antenna gainNodeB
MAPL
304

UE power class 3
Service: PS64
Vehicular A 50km/h
Incar
=8
UL load factor=50%
Value
in
Comment
f.a.=fxed
assumptio
n
(see
previously
)

A1
UE TX power
24
A2
A3
EIRPUE
dBm
dB
see 2.3
f.a.
24
dBm
A1+A2
3.2
dB
see 2.2
17.8
dB
see 1.3
dB
f.a.

B1
(Eb/No)req
B2
Processing Gain
B3
NFNodeB
B4
Thermal noise
-108.1
dBm
f.a.
B5
118.7
dBm
B1B2+B3+B4
305

Value
in
Comment
f.a.=fxed
assumptio
n (see
previously
)
C. Margins
C1
Shadowing margin
4.8
dB
see 3.3
C2
Fast fading margin
-0.3
dB
see 3.3
C3
Noise Rise
dB
see 3.5
C4
0.1
dB
see 3.5
C5
Interference margin
2.9
dB
C3+C4
dB
f.a.
D2 Body loss
dB
see 2.2

margin)
dB
see 2.2
18
dBi
f.a.
139.3
dB
D. Losses
E. Gains
E1
Antenna gainNodeB
MAPL
306

Can you complete the following table by using the simplified formula of the Alcatel Standard
propagation model (see exercise in 3.2)?
MAPL[dB] = C1 + C2 x log(Cell Range [km]) (see exercise in 3.2)
Cell Range [km]= 10
(MAPL-C1)/C2
(see solution of exercise 3.1 for C1 and C2 values)
Limiting Service
Clutter class
Cell Range
[km]
Speech 12.2k
Deep Indoor
MAPL=126.9dB
(calculated on
previous slide)
Dense urban
0.60
Urban
0.73
Suburban
0.83
Rural
1.81
Dense urban
1.34
Urban
1.63
Suburban
1.86
Rural
4.08
PS64 Incar
MAPL=139.3dB
(calculated on
previous slide)
307

4.2 CPICH RSCP coverage prediction
1. What happens if you have a bad CPICH RSCP coverage in an area?
no service coverage
2. Does the CPICH RSCP coverage depend on traffic load?
no, this is the only coverage prediction which is independent on the traffic load (CPICH Ec/Io and
UL/DL service coverage predictions depends on traffic load)
3. Which are the input parameters for the CPICH RSCP coverage prediction?
look at the CPICH RSCP equation:
CPICH RSCP[dBm] = CPICH TX power[dBm] +GainNodeB antenna [dB]
LossNodeB feeder cables [dB] Lpath [dB]
You can see that the input parameters are:
CPICH TX power + Antenna Gain and radiation pattern + Feeder loss NodeB + propagation model
parameters (see 3.2) + Calculation radius
4. Shall the calculation radius be greater or smaller than the intersite distance?
greater. If not, CPICH RSCP will not be calculated on all pixels of the map.
Calculation radius shall be as big as necessary to correctly model interference and as small as
possible to allow fast predictions.
5. Make some suggestions to improve the prediction results
-modify antenna azymuth or downtilt (to increase GainNodeB Antenna on the pixels with bad coverage)
- increase CPICH TX power
308
Abbreviations and Acronyms (1)

3GPP
3rd Generation Partnership Project
3GPP2 3rd Generation Partnership Project 2
(cdma2000)
AAL ATM Adaptation Layer
AICH
Acquisition Indication Channel
ALCAP Access Link Control Application Part
AMRAdaptive Multi Rate
ANRU
Antenna Network Receiver UMTS
ANSI
American National Standard Institute (USA)
ARIB
Association of Radio Industries and Business
(Japan)
AS Active set
ATM Asynchronous Transfer Mode
BB Base Band
BCCH
Broadcast Control Channel
BCH Broadcast Channel
BHCA
Busy Hour Call Attempts
BMCBroadcast / Multicast Control
BSC Base Station Controller
BSS Base Station (sub)System
BTS Base Transceiver Station
CAMEL Customized Application for Mobile Enhanced
Logic
CC Call Control
CCCH
Common Control Channel
CCH Common Channels
CCTrCH Coded Composite Transport Channel
CE
CN
CPCH
CPICH
CRNC
CS
CTCH
CWTS
Standard
DCCH
DCH
DHO
DL
DPCCH
DPCH
DPDCH
DRNC
DS
DSCH
DTCH
DU
Channel Element
Core Network
Common Packet Channel
Common Pilot Channel
Controlling RNC
Circuit Switched
Common Traffic Channel
China Wireless Telecommunication
Dedicated Control Channel
Dedicated Channel
Diversity Handover
Downlink
Dedicated Physical Control Channel
Dedicated Physical Channel (in DL)
Dedicated Physical Data Channel
Drift RNC
Direct Sequence
Downlink Shared Channel
Dedicated Traffic Channel
Dense Urban
309

EDGE
Enhanced Data rates for GSM Evolution
EIRPEffective Isotropic Radiated Power
ETSI European Telecommunication Standard Institute
FACH
Forward Access Channel
FBI Feedback Information
FDD Frequency Division Duplex
FDMA
Frequency Division Multiple Access
FTP File Transfer Protocol
GERAN GSM/EDGE Radio Access Network
GGSN
Gateway GPRS Support Node
GMSC
Gateway MSC
GPRS
General Packet Radio Service
GSMGlobal System for Mobile Communications
GTP GPRS Tunnelling Protocol
HLR Home Location Register
HO Handover
IETF Internet Engineering Task Force
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
IMT International Mobile Telecommunication
IP Internet Protocol
ISCPInterference Signal Code Power
ISDN
Integrated Services Digital Network
ITU International Telecommunication Union
L1,L2,L3
LA
LAC
LAI
LCS
MAC
MAPL
MBS
MC
MCC
ME
MExE
MM
MNC
MRC
MSC
MUD
NAS
NBAP
NF
Layer 1, Layer 2, Layer 3

Location Area
Location Area Code
Location Area Identifier
Location Services
Medium Access Control
Maximum Allowed Path Loss
Multi-standard Base Station
Multiple Carrier
Mobile Country Code
Mobile Equipment
Mobile Execution Environment
Mobility Management
Mobile Network Code
Maximum Ratio Combining
Mobile-services Switching Center
Multi User Detection
Non Access Stratum
Node-B Application Part
Noise Figure
310

OCNS
Orthogonal Code Noise Simulator
OMC-UR Operation and Maintenance Center UMTS
Radio
OVSF
Orthogonal Variable Spreading Factor
P-CCPCH Primary Common Control Physical Channel
PCH Paging Channel
PCCH
Paging Control Channel
PCH Paging Channel
PDA Personal Digital Assistant
PG Processing Gain
PICH
Paging Indicator Channel
PLMN
Public Land Mobile Network
PRACH Physical Random Access Channel
PS Packet
Switched
P-SCH
Primary Synchronization Channel
QOSQuality Of Service
QPSK
Quadrature Phase Shift Keying
R
R1, R2, R3
releases
RA
RAB
RAC
RACH
RAN
RANAP
RB
RL
RLC
RNC
RNP
RNS
RNSAP
RNTI
RRC
RRM
RSCP
RSSI
Rural
1) 3GPP releases ; 2) Alcatel UTRAN
Routing Area
Radio Access Bearer
Routing Area Code
Random Access Channel
Radio Access Network
RAN Application Part
Radio Bearer
Radio Link
Radio Link Control
Radio Network Controller
Radio Network Planning
Radio Network Sub-System
RNS Application Part
Radio Network Temporary Identity
Radio Resource Control
Radio Resource Management
Received Signal Code Power
Received Signal Strength Indicator
311

SAC Service Area Code
S-CCPCH Secondary Common Control Physical Channel
SCH Synchronization Channel
SF Spreading Factor
SGSN
Serving GPRS Support Node
SHO Soft Handover
SIR Signal to Interference Ratio
SMS Short Message Service
SPM Standard Propagation Model
S-SCH
Secondary Synchronization Channel
STTD
Space Time Transmit Diversity
SU Sub Urban
SUMU
Station Unit Mobile Universal
T1 Committee T1 telecommunication of the ANSI (USA)
TD-CDMA
Time Division-CDMA (for UMTS TDD
mode)
TDD Time Division Duplex
TDMA
Time Division Multiple Access
TEU Transmit Equipment UMTS
TF Transport Format
TFC Transport Format Combination
TFCI Transport Format Combination Indicator
TFCS
Transport Format Combination Set
TFS Transport Format Set
TIA Telecommunication Industry Association (USA)
TMA
TMSI
TSTD
TTA
(Korea)
U
UARFCN
UE
UICC
UL
UMTS
USIM
URA
UTM
UTRAN
UWCC
Committee
VLR
W-CDMA
WGS
Tower Mounted Amplifier

Temporary Mobile Station Identity
Time Switch Transmit Diversity
Telecommunication Technology Association
Urban
UTRAN Absolute Frequency Channel Number
User Equipment
UMTS Integrated Circuit Card
Uplink
Universal Mobile Telecommunication System
UMTS Subscriber Identity Card
UTRAN Registration Area
Universal Transverse Mercator System
UMTS Terrestrial Radio Access Network
Universal Wireless Communications
Visitor Location Register
Wideband CDMA (for UMTS FDD mode)
World Geodetic System 1984
312

Module 6 Planning Details

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Module 6 Planning Details

Uploaded by

Copyright:

Available Formats

UMTS Radio Network Planning

UMTS Radio Network Planning Fundamentals

UMTS Radio Network Planning Fundamentals

UMTS RNP notations

UMTS RNP tool overview

UMTS RNP process overview

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

to be able to describe the UMTS network

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

UMTS network architecture(1)

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

UMTS network architecture(2)

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

Radio Network Optimizer

Network Manager (used to

3GPP: the UMTS standardization body

UMTS system specifications:

Releases defined for the UMTS system specifications:

3GPP UMTS specifications

"UE Radio transmission and Reception (FDD)"

"UTRA (BS) FDD; Radio transmission and Reception

"Requirements for support of radio resource management (FDD)"

"Base Station (BS) conformance testing (FDD)

"Physical layer procedures (FDD)".

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

Alcatel UTRAN releases

(Technical Status December

(Technical Status June 2001)

(Technical Status March 2002)

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

UMTS main radio mechanisms(1)

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

UMTS main radio mechanisms(2)

Multiple frequencies (carriers)

frequency (e.g. frequency 1) is used for the

UMTS main radio mechanisms(3)

Channelization and scrambling codes (UL side)

Channelization codes (spreading

UMTS main radio mechanisms(4)

Channelization and scrambling codes (DL side)

UMTS main radio mechanisms(5)

UMTS main radio mechanisms(6)

Pre-defined symbol sequence

a pre-defined symbol sequence

Tslot = 2560 chips , 20 bits = 10 symbols

UMTS main radio mechanisms(7)

an efficient and fast power control is necessary in UL to

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

UMTS main radio mechanisms(8)

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

UMTS main radio mechanisms(9)

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

UMTS RNP notations and principles

to be able to understand the vocabulary and

* unfortunately, UMTS RNP notations are not

Received power and

All rights reserved Alcatel - 3FL 11194 ABAA WBZZA Ed.01P04

Nth = k.T0 with k=1.38E-20mW/Hz/K

interference received from

Ec = Energy per chip=C/B

UMTS RNP notations and principles

interference received from

Total received power

Total received power