UMTS RNP Fundamentals R5 Ed01 AUM

Do not delete this graphic elements in here:
Radio Network Planning

Fundamentals UTRAN UA5
3FL 11194 ACAA Edition 01
All Rights Reserved Alcatel-Lucent @@YEAR

Section 1. - Module 1. - Page 1
Blank Page
@@SECTION @@MODULE 2
@@SECTIONTITLE @@MODULETITLE
@@PRODUCT @@COURSENAME
This page is left blank intentionally

Objectives
z
-
By the end of the course, participants will be able to:

Describe briefly the structure of an RNP tool and the steps
of an RNP process;
Describe the UMTS RNP inputs in regard to frequency spectrum,
traffic parameters, equipment parameters and RNP requirements;
Calculate the cell range for a given service by doing a manual link
budget in Uplink;Have the theoretical background to create an initial
network design using an RNP tool (the RNP tool is only used by the
trainer for demonstration);
Define basic radio network parameters (neighborhood and code
planning);
Discuss briefly optimization possibilities in terms of capacity and
coverage;
Describe briefly the interference mechanisms due to UMTS/GSM colocation and the solutions for antenna systems.

Objectives [cont.]

Table of Contents
z
Switch to notes view!
Page
1 UMTS Introduction
1.1 Session presentation
1.1.1 UMTS network architecture
1.1.2 3GPP: the UMTS standardization body
1.1.3 3GPP UMTS specifications
1.1.4 Alcatel-Lucents release overview
1.1.5 UMTS main radio mechanisms
1.2 UMTS RNP notations and principles
1.2.1 Notations
1.2.2 Exercise
1.3 UMTS RNP tool overview
1.3.1 RNP tool requirements
1.3.2 Example: A9155 UMTS/GSM RNP tool
1.4 RNP process overview
1.4.1 The 11 steps of RNP process
1.4.2 Step1: Definition of Radio Network Requirements
1.4.3 Step 2: Preliminary Network Design
1.4.4 Step 3: Project Setup and Management
1.4.5 Step 4: Initial Radio Network Design
1.4.6 Step 5: Site Acquisition Procedure
1.4.7 Step 6: Technical Site Survey
1.4.8 Step 7: Basic Parameter Definition
1.4.9 Step
8: Cell
Design CAE Data Exchange
@@SECTION
@@MODULE
5
@@SECTIONTITLE
@@MODULETITLECell Creation Import Planned Data
1.4.10 Massive
1.4.11 Step 9: Turn On Cycle
1.4.12 Step 10: Basic Network Optimization
1.4.13 Step 11: Network Acceptance
1.4.14 (Step 12: Further Optimization)
2 Inputs for Radio Network Planning
2.1.1 UMTS FDD frequency spectrum
2.1.1.1 Frequency spectrum
2.1.1.2 Carrier spacing
2.1.1.3 Frequency channel numbering
2.1.1.4 Center Frequency
2.1.1.5 Further comments
2.1.2 UMTS traffic parameters (UMTS traffic map)
2.1.2.1 Step 1: Terminal parameters
2.1.2.2 Step 2: Service parameters
2.1.2.3 Step 3: User Profile parameters
2.1.2.4 Step 4: Environment Class parameters
2.1.2.5 Step 5: Traffic Map definition
2.1.3 UMTS Terminal, NodeB and Antenna overview
2.1.3.1 UE characteristics
2.1.3.2 Alcatel-Lucent Node B
2.1.3.3 UMTS antennas
2.1.4 Radio Network Requirements
2.1.4.1 Definition of radio network requirements
3 Link Budget (in Uplink) and Cell Range Calculation
3.1.1 Principle for Cell Range calculation
3.1.2 Inputs for the UL link budget
3.1.3 How to calculate the Pathloss Lpath?
3.1.4 Alcatel-Lucent Standard Propagation Model
3.1.5 Other Propagation Models

7
8
9
11
12
13
14
31
32
36
38
39
41
42
43
44
45
46
47
48
49
50
51
52
53
56
57
58
59
60
61
62
63
64
65
66
67
68
69
71
72
73
74
75
76
81
83
84
87
88
89
90
91
92
103
Table of Contents [cont.]

z
Page

3.2 UMTS shadowing and fast fading modeling
3.2.1 Definition of fading
3.2.2 Shadowing
3.2.3 Fast Fading
3.2.4 UL Fast Fading
3.2.5 DL Fast Fading
3.3 Calculation of Node B reference sensitivity
3.3.1 Definition of Reference_Sensitivity
3.3.2 Calculation of Reference_Sensitivity
3.4 UMTS interference modeling
3.4.1 Calculation of interference margin
3.4.2 Noise Rise and Traffic load
3.4.3 Traffic load and UL load factor
3.4.4 What about DL load factor?
3.5 Calculation of cell range
3.5.1 Exercise: MAPLUL calculation
3.5.2 Exercise: cell range calculation
4 Initial Radio Network Design
4.1 Objective
4.2 Overview
4.2.1 Positioning the sites on the map
4.2.1.1
Calculation
of inter-site distance
@@SECTION
@@MODULE
6
@@SECTIONTITLE
@@MODULETITLE
4.2.1.2
Site map
4.2.1.3 Network Design Parameters
4.3.1 Coverage Prediction for
4.3.1.1 How to perform the prediction?
4.3.1.2 How to interpret the prediction?
4.3.1.3 Exercise
4.4.1 UMTS traffic simulations
4.4.1.1 Why do we need traffic simulations?
4.4.1.2 How to perform a traffic simulation?
4.4.1.3 Traffic simulation outputs
4.4.1.4 Limitation of traffic simulation
4.5.1 Coverage predictions for CPICH Ec/Io and DL/UL
4.5.1.1 Why do we need coverage predictions?
4.5.1.2 Different types of coverage predictions
4.5.1.3 How to perform a coverage prediction?
4.5.1.6 How to interpret a coverage prediction?
4.6.1 Traffic emulation or fixed load approach?
4.6.1.1 Traffic emulation approach
4.6.1.2 Fixed load approach
4.6.1.3 A medium approach
5 Basic Radio Network Parameter Definition
5.1.1 Neighborhood planning
1.5.1.1 Overview
5.1.1.1 Criteria and methods
5.1.1.2 Automatic neighborhood allocation with A9155
5.2.1 Scrambling code planning
5.2.1.1 Overview
5.2.1.2 DL scrambling code planning
5.2.1.3 Definition of UL scrambling code pool for a RNC

104
105
106
108
115
116
119
120
121
122
123
124
125
127
129
130
131
136
137
138
139
140
141
142
143
146
147
150
151
152
153
155
158
159
160
161
162
163
166
167
168
170
174
176
177
178
179
180
181
183
184
185
187
1 UMTS Introduction
(FDD mode, R5)

1 UMTS Introduction

z
Objective:
to get the necessary background information in regards of UMTS
basics and RNP principles for a good start in UMTS Radio
Network Planning.
Prerequisites:
GSM Radio Network Engineering Fundamentals
Introduction to UMTS
Program:
1.1.1
1.1.2
1.1.3
1.1.4
UMTS Basics
UMTS RNP notations
UMTS RNP tool overview
UMTS RNP process overview

1.1.1 UMTS network architecture

z
Entities and interfaces
Uu
(air)
Iu
Node B
Iub
USIM
Iu-CS
RNC
Node B
MSC/VLR
GMSC
PLMN, PSTN,
ISDN, ...
RNS
HLR
Iur
Cu
Node B
ME
Iub
Node B
UE
User
Equipment
RNC
SGSN
RNS
IP
networks
CN
External Networks
Iu-PS
UTRAN
UMTS Radio
Access
Network
GGSN
Core Network
UE ( User Equipment)
The UE consists of two parts:
The mobile equipment (ME) is the radio terminal used for radio communication over the Uu interface
The UMTS Subscriber Identity Module (USIM) is the equivalent smartcard to the SIM in GSM. It holds the
subscriber identity, performs authentication algorithms, stores authentication and encryption keys, etc.
- UTRAN (UMTS Radio Access Network)
The UTRAN consists of one or several Radio Network Subsystems (RNS) each containing one RNC and one
or several Node B:
Node B
The Node B is the correspondent element to the BTS in GSM. Within Alcatel-Lucent this part of the
network is called the Multi-standard Base Station (MBS), as it is possible to integrate GSM modules as
well (not in the early versions!)
RNC
The Radio Network Controller (RNC) owns and controls the radio resources of the connected Node Bs.
The RNC can have three different logical roles: CRNC, SRNC, DRNC. See more details in chapter 2.1.6.
- CN (Core network)
HLR
The Home Location Register is a database located in the users home system that stores the master copy
of the users service profile.
MSC/VLR
The Mobile Services Switching Center and Visitor Location Register are the switch (MSC) and database
(VLR) serving the UE in its current location for circuit switched services.
GMSC
The Gateway MSC (GMSC) is the MSC at the point where the UMTS PLMN is connected to external circuit
switched networks.
SGSN
1.1.1 UMTS network architecture [cont.]

z
Alcatel-Lucent WNMS
architecture
WNMS
Main
server
LAN
ItfB
Node B
Node B
RNC
1500
RNS
Node B
Iub
Node B
RNC
1500
RNS
UTRAN
Performance
server
ItfR
W-NMS consists of:
1 Main Server: this Sun server is
responsible for configuration and fault
management.
1 Performance Server: this Sun server is
responsible for collection, mediation and
post-processing of counters and call trace
data.
Clients: Windows PCs and / or Sun
workstations are used to run client
applications.
(Contd from previous page)

- External networks
The UMTS network is connected to two kinds of external networks:
Circuit switched
Examples for CS networks are: Existing telephone service, ISDN, PSTN
Packet switched
Best example today for a packet switched network is the Internet
- Interfaces
It is important to know, that all external UMTS interfaces are open interfaces. This means that theoretically
equipment of different vendors can be mixed if it fulfills the standards.
Cu interface
The Cu interface is a standard interface for smartcards. In the UE it is the connection between the USIM and
the UE.
Uu interface
The Uu interface is the WCDMA radio interface within UMTS. It is the interface through which the UE
accesses the fixed part of the network. This interface is the most important one to understand for RNP issues.
Iu interface
The Iu interface connects the UTRAN to the core network and is split in two parts. The Iu-CS is the interface
between the RNC and the circuit switched part of the core network. The Iu-PS is the interface between the
RNC and the packet switched part of the core network.
Iur interface
This RNC-RNC interface was initially designed in order to provide inter RNC soft HO, but more features were
added during the development. Four distinct functions are provided now:
Basic inter-RNC mobility
Dedicated channel traffic
Common channel traffic

1.1.2 3GPP: the UMTS standardization body

z
Members:
ETSI (Europe)
T1 (USA)
UMTS system specifications:
Access Network
Core Network
y
y
ARIB/TTC (Japan)
TTA (South Korea)
CWTS (China)
WCDMA (UTRAN FDD)

TD-CDMA (UTRAN TDD)
y Evolved GSM
y All-IP
Note: 3GPP has also taken over the GSM recommendations (previously written by ETSI)
z
Releases defined for the UMTS system specifications:
Release 99 (sometimes called Release 3)

Release 4
(former Release 2000)
Release 5
In the following material we will only deal with UMTS FDD
ARIB
CWTS
TTA
Association of Radio Industries and Business (Japan)

China Wireless Telecommunication Standard
Telecommunication Technology Association (Korea)

1.1.3 3GPP UMTS specifications

z
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:
3GPP TS 25.214:
3GPP TS 25.215:
3GPP TS 25.942:
r
nde
u
d
o un
f
e
"Physical layer procedures (FDD)".
b
can org
s
"Physical layer - Measurements (FDD)
tion 3gpp.
a
c
i
if
w.
"RF system scenarios".
pec ww
s
PP
3G
"Base Station (BS) conformance testing (FDD)
http://www.3gpp.org/ftp/Specs/archive/25_series/

1.1.4 Alcatel-Lucents release overview
UA 04
3GPP R4
UA 05
3GPP R5
UA 06
3GPP R6
Release 6
3GPP R6
Q2
Release 6
3GPP R6
Improvement
of coverage
RNC evolution
Q2
Q3
Q2
March
2006
UA 07
3GPP R7
March
2007
HSXPA
+
IMS
2008
GBR on HSDPA
HSDPA vs. DCH
QoS
E-DCH 2ms TTI
9370 RNC (x2
cap)
2009
HSPA +
MIMO 2X2 multi
streams
All IP UTRAN
VoIP over HSPA
To follow the evolution of the 3GPP standard and the growth of the network, the Alcatel-Lucent Solution is
made up of several releases.
The first release used commercially was the R3. It is the release of openness towards 2G systems to allow a
full 2G-3G interworking with hard handover based on service or radio reception. It also provides services
whatever the movement of the subscriber, with mechanisms like soft handover.
For the Operation and Maintenance, a suitable and centralized OMC is provided for the supervision, the
configuration, the optimization and the security of the network.
Release 4 provides the improvement of the coverage and mainly the adaptation of the coverage to the
context (hot spot or rural zone for instance). The other important evolution is the introduction of a new RNC
called RNC Evolution.
Release 5 provides the improvement of the performance with the introduction of a new channel dedicated to
the high data rate, the HSDPA, the introduction of the IMS(IP Multimedia Service) or the multi-RAB(Radio
Access Bearer) in PS.
All IP will be introduced in UTRAN at the Release 6 around 2008.

1.1.5 UMTS main radio mechanisms

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

1.1.5 UMTS main radio mechanisms [cont.]

z
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:
y
y
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
FDD
Frequence division duplex
UMTS to GSM /GPRS

CS domain
GSM/GPRS to UMTS
Hand over in dedicated mode

/ Cell reselection in idle mode
PS domain Cell or PLMN reselection
Cell or PLMN reselection

Cell or PLMN reselection
Look 3BK 10204 0532 DTZZA P.9


Channelization and scrambling codes (UL side)
Bit rateA
Physical channels
cch1
Bit rateB
cch 2
Bit rateC
.
.
.
UE
3.84 Mchips/s
3.84 Mchips/s
3.84 Mchips/s
3.84 Mchips/s
Modulator
cscrambling
air interface
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)
assigned by the RNC at connection setup
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


z
Channelization and scrambling codes (DL side)
Physical channels
Bit rateA
cch1
Bit rateB
cch 2
Bit rateC
.
.
.
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.
NodeB
sector
3.84 Mchips/s
cscrambling
Modulator
air interface
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
Note: it is also possible to define secondary scrambling
codes, but it is seldom used.

Physical channels
Physical channels are defined mainly by:

y
y
a specific frequency (carrier)

a 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:
y
y
used to separate the physical channels (2 physical channels must NOT have the same
combination channelization code / scrambling code)
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:
y
y
y
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)
CPICH: see next slide
DPDCH: dedicated physical data channel

DPCCH: dedicated physical control channel
DPCH: dedicated physical channel
P-CCPCH: Primary- Common Control Physical Channel
CPICH: Common Pilot Channel
Downlink channels
Uplink channels
Logical channels
Transport channels


z
CPICH (or Pilot channel)

DL common channel sent permanently in each cell to provide:
y 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)
y power reference: used to perform measurements for handover and cell
selection/reselection (function performed by time slot 0 used for BCCH in GSM)
y time and phase reference: used to aid channel estimation in reception at the UE side
Pre-defined symbol sequence
z The CPICH contains:

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
1 radio frame: Tf = 10 ms
Slot #14

HSDPA Channels- Physical Layer Structure
(DL) HS-PDSCH (High Speed Physical Downlink Shared CHannel)
Data information with fixed SF=16 (up to 15 per UE)

Supports QPSK modulation and 16-QAM in option
(DL) HS-SCCH (High Speed Shared Control CHannel)
Control information for only one UE with fixed SF=128
(allocated channelization codes, UE identity, Transport Block size, H-ARQ process )
3GPP specifies a max. of 4 HS-SCCH/cell, then up to 4 UEs/TTI
(UL) HS-DPCCH (High Speed Dedicated Physical Control CH.)
Control information (ACK/NACK and CQI) with fixed SF=256
(UL/DL) Associated DPDCH/DPCCH (associated DCH)
Control information (RRC/RLC level)

Data information (in UL at least)


3GPP Channel mapping in HSDPA (Downlink)
Logical Channels
DTCH
CTCH
DCH
HS-DSCH
DCCH
CCCH
PCCH
BCCH
FACH
PCH
BCH
Transport Channels
A
DP
HS
Physical Channels
DPDCH and DPCCH

multiplexed by time
DPDCH
+
DPCCH
HS-PDSCHs
P-CCPCH
A
DP
HS
Not associated
with transport channels
S-CCPCH
+
HS-SCCHs
AICH
PICH
CPICH
P-SCH
S-SCH
HS-DSCH definition: refer to [3GPP TS 25.301]

The HS-DSCH is a resource that exists in downlink only. It has only impact on the physical and transport channel
levels, so there is no definition of shared channel in the logical channels provided by MAC.
The HS-DSCH is a transport channel for which a common pool of radio resources is shared dynamically between
several UEs. The HS-DSCH is mapped to one or several physical channels such that a specified part of the downlink
resources is employed. For the HS-DSCH no macrodiversity is applied, i.e. a specific HS-DSCH is transmitted in a
single cell only.The HS-DSCH is defined as an extension to DCH transmission. Physical channel signalling is used for
indicating to a UE when it has been scheduled and then the necessary signalling information for the UE to decode the
HS-PDSCH.
In every HS-DSCH TTI, one or several HS-PDSCHs can be used in the downlink. Therefore, the HS-DSCH supports
code multiplexing. MAC multiplexing of different UEs shall not be applied within an HS-DSCH TTI, i.e. within one HSDSCH TTI an HS-PDSCH is assigned to a single UE. However, MAC multiplexing is allowed on a TTI by TTI basis, i.e.
one HS-PDSCH may be allocated to different UEs at each TTI.
Resource allocation and UE identification on HS-DSCH:
For each HS-DSCH TTI, each HS-SCCH carries HS-DSCH related downlink signalling for one UE, along with a UE
identity (via a UE specific CRC) that identifies the UE for which this information is necessary in order to decode the
scheduled HS-PDSCH.
Note: In Evolium R5, DCCH is not mapped on HS-DSCH


3GPP Channel mapping in HSDPA (Uplink)
Logical Channels
Transport Channels
DTCH
DCH1
DCCH
DCH2
CCCH
RACH
CCTrCH
Physical Channels
DPDCH and DPCCH

multiplexed by modulation
DPDCH
+
DPCCH
HS-DPCCH
A
DP
HS
PRACH
Note: In Evolium R5, DCCH is not mapped on HS-DSCH


HS-DSCH specific Characteristics
Fixed TTI, 2 Modulations, lower Coding Rates, Multi-Code

Transmission, Code Multiplexing
Ex.: QPSK
Coding rate=1/4
Ex.:16-QAM
Coding rate=3/4
Codes
User 5
User 3
User 5
UE 1
UE 2
UE 3
UE 4
UE 5
15 codes
(SF=16)
User 1
User 4
User 2
User 4
User 1
User 2
User 1
User 3
User 3
HS-PSDCH #5
Time
TTI=2ms
The HS-DSCH has specific characteristics in many ways compared with existing Release99 channels:
The Transmission Time Interval (TTI) or interleaving period has been defined to be 2 ms (3 slots) to achieve short roundtrip delay for the operation between the terminal and Node B for retransmissions. The HS-DSCH 2-ms TTI is short
compared to the 10-, 20-, 40- or 80-ms TTI sizes supported in Release99.
Adding higher order modulation scheme, 16 QAM, as well as lower encoding redundancy has increased the
instantaneous peak data rate.
In the code domain perspective, the SF is fixed; it is always 16, and multi-code transmission (up to 15 codes/UE) as
well as parallel transmission (up to 4 UE/TTI) of different users can take place. The maximum number of codes that
can be allocated is 15, but depending on the terminal (UE) capability, individual terminals may receive a maximum of
5, 10 or 15 codes.
Channel Coding
[25.858] HS-DSCH channel coding uses the existing rate 1/3 Turbo code and the existing Turbo code internal interleaver,
as outlined in 3G TS 25.212. Other code rates are generated from the basic rate 1/3 Turbo code by
applying rate matching by means of puncturing or repetition.
[Holma] turbo coding is the only coding scheme used. However, by varying the transport block size, the modulation
scheme and the number of multi-codes and turbo code rates other than 1/3 become available. In this manner, the
effective code rate can vary from to ; i.e.
the
number of bits per code can vary by changing the coding gain.

Example of Code Tree Allocation
z
z
For DCH : allocation of codes by signalling (RRC/NBAP)

(change possible but procedure is around 1s )
For HSDPA : allocation of codes to one UE by a new MAC protocol (change possible every 2 ms)
SF=1
SF=2
SF=4
Code used by
one R99 UE on
DCH requiring
high data rate
SF=8
SF=16
HS-PDSCHs
C16,0
Physical channels (codes) to which HS-DSCH

channel may be mapped
Codes reserved for

R99 UE on DCH
SFHSDPA = 16 (fixed)
Up to 15 codes to which HSDPA transmission is mapped.

Branch used to map

Common channels

Example of Code Tree Allocation
SF 16
C16,0
SF 32
SF 64
C64,1
S-CCPCH
HS-SCCH
C128,7
HS-SCCH
C128,6
physical channel used

to carry downlink
signalling related to
HS-DSCH transmission
DCH
C128,5
DCH
SF 128
C128,4
C256,2
associated DCH
channels for DL data
traffic for one of the UE
on HS-DSCH
C256,3
AICH
C256,0
C256,1
SF 256
PICH P-CCPCH P-CPICH
Common channels allocated

at cell creation
4 HS-SCCH codes can be allocated at the maximum in Evolium R5 (up to 4 is also the maximum according to 3GPP).
In this figure, an example using 2 HS-SCCH codes is given.


Structure of HS-DSCH-associated Channels
Tslot=2560 chips, Mx10x2k bits (k=4)
HS-PDSCH Structure
M=2 for QPSK

M=4 for 16-QAM
Data (N bits)
(Downlink Data Channel)
Slot #0
Slot #1
Slot #2
One HS-PDSCH subframe

(TTI=2ms =3 time slots)
Transport block size
H-ARQ related info.
TTI=2ms
Part-1
Part-2
Hybrid-ARQ process number

Redundancy version
New-data indicator
HS-SCCH Structure
CRC
(Downlink Control Channel)
Channelization codes to despread

Modulation scheme (QPSK or 16-QAM)
UE Identity via UE
specific CRC
HS-DPCCH Structure
ACK/NACK
Downlink CQI
(Uplink Control Channel)
Subframe #0
Subframe #i
Subframe #4
One radio frame (10 ms)

Frame structure for HS-PDSCH (SF=16, turbo coding) :

The High Speed Physical Downlink Shared Channel (HS- PDSCH) is used to carry the High Speed Downlink Shared
Channel (HS-DSCH).
A HS-PDSCH corresponds to one channelization code of fixed spreading factor SF=16 from the set of channelization
codes reserved for HS-DSCH transmission. Multi-code transmission is allowed, which translates to UE being assigned
multiple channelisation codes in the same HS-PDSCH subframe, depending on its UE capability.
An HS-PDSCH may use QPSK or 16QAM modulation symbols, but n HS-PDSCH codes transmitted in parallel for a UE
shall use the same modulation.
M is the number of bits per modulation symbols i.e. M=2 for QPSK and M=4 for 16QAM.
For FDD, following information is carried on the HS-SCCH (SF=128, convolution coding r=1/2):
refer to [3GPP TS 25.858]
Transport-format and Resource related Information (TFRI): Channelization-code set: 7 bits, Modulation scheme:
1 bit, Transport-block size: 6 bits
Hybrid-ARQ-related Information (HARQ information): Hybrid-ARQ process number: 3 bits (thus corresponding to
a maximum of 8 HARQ processes at UE), Redundancy version: 3 bits, New-data indicator: 1 bit (0 for the first MAChs PDU transmitted by a HARQ process), UE ID: 10 bits implicitly encoded in the CRC
Frame structure for Uplink HS-DPCCH (SF=256, 15 kbps channel bit rate) :
refer to [3GPP TS 25.211]
The HS-DPCCH carries uplink feedback signalling related to downlink HS-DSCH transmission.
ACAA Edition
01
The HS-DSCH-related feedback signalling consists3FL
of 11194
Hybrid-ARQ
Acknowledgement
(HARQ-ACK) and Channel-Quality
Indication (CQI). Each sub frame of length 2 ms (3*2560 chips) consists of 3 slots, each of length 2560 chips.

z
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
y an efficient and fast power control is necessary in UL to avoid near-far effect

y 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):
y open loop (without feedback information) for common physical channels

y closed loop (with feedback information) for dedicated physical channels (1500 Hz
command rate, also called fast power control)


RNC
W Soft/softer Handover (HO)

z a UE is in soft handover state if there
are two (or more) radio links between
this UE and the UTRAN
z it is a fundamental UMTS
mechanism (necessary to avoid nearfar effect)
UE
Soft handover
(different sectors of different NodeBs)
z only possible intra-frequency, ie

between cells with the same frequency
RNC
Note: hard handover is provided if

soft/er handover is not possible
z A softer handover is a soft handover
between different sectors of the same
Node B
Node B
Node B
Node B
UE
Softer handover
(different sectors of the same NodeB)


z
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):
y usual situation: about 30% of UE with at least 2 cells in their AS.
y up to 4(+2) cells in AS for a given UE
The different propagation paths in DL and UL lead to a diversity gain, called

Macro Diversity gain:
y 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
y DL
{
{
two physical signals (with the same content) sent by two different cells and received by one UE
soft/softer handover: MRC in UE


Channel Quality Feedback
The Channel Quality Indicator (CQI) is then reported to the Node B

on the UL control channel (HS-DPCCH)
UE
Category
Reported CQI
(estimated
by the UE)
Amount of data to
transmit
Configured
HS-PDSCH/HS-SCCH
total power
BLER<10%
SCHEDULER
(every TTI)
[TFRC selection]
Transport Block Size

H-ARQ parameters (RV)
Number of channelization codes
Allocated power
HS-PDSCH Modulation Type
Channel Quality
Feedback (CQI)
CQI ?
CQI 1
CQI 2
TFRC (Transport Format Resource Combination)

User data and

Signalling
CQI 30
A CQI mapping table example is shown below for UE category 10.

Modulation
Type
CQI
value
Transport
Block Size
Number of
HS-PDSCH
Modulation
Type
CQI
value
Transport
Block Size
Number of
HS-PDSCH
137
QPSK
16
3565
16-QAM
173
QPSK
17
4189
16-QAM
233
QPSK
18
4664
16-QAM
317
QPSK
19
5287
16-QAM
377
QPSK
20
5887
16-QAM
461
QPSK
21
6554
16-QAM
650
QPSK
22
7168
16-QAM
792
QPSK
23
9719
16-QAM
931
QPSK
24
11418
16-QAM
10
1262
QPSK
25
14411
10
16-QAM
11
1483
QPSK
26
17237
12
16-QAM
12
1742
QPSK
27
21754
15
16-QAM
13
2279
QPSK
28
23370
15
16-QAM
14
2583
QPSK
29
24222
15
16-QAM
15
3319
QPSK
30
25558
15
16-QAM

1 UMTS Introduction
1.1.2
UMTS RNP notations and principles
y 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.

1.2.1 Notations
Power
[dBm]
Power
Density
[dBm/Hz]
C
(or RSCP)
Ec
-108.1
Nth=-174
Interference intra-cell
Iintra
(Iown)
Interference extra-cell
Iextra
(Iother;Iinter)
Received power and

power density
Received (useful)
signal
Thermal Noise
Thermal Noise at
receiver
Interference
Comment
(Power Density=Power/B
with B=3.84MHz)
Ec = Energy per chip=C/B
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
interference received from transmitters not

located in the same cell as the receiver
I=Iintra+ Iextra
(no Thermal noise at receiver included)
RSCP - Received Signal Code Power

What is the reference point for these received powers and power densities?
UL: at the NodeB antenna connector
what about RX diversity?

DL: at the UE antenna connector
what about optional TX diversity?

NF: Noise Figure
thermal noise The noise generated by thermal agitation of electrons in a conductor. The noise
power, P , in watts, is given by P = kT f , where k is Boltzmann's constant in joules per kelvin, T is the
conductor temperature in kelvins, and f is the bandwidth in hertz. (188 )
Note 1: Thermal noise power, per hertz, is equal throughout the frequency spectrum, depending only
on k and T .
Note 2: For the general case, the above definition may be held to apply to charge carriers in any type
of conducting medium. Synonym Johnson noise.

1.2.1 Notations [cont.]
Received power and

power density
Power
[dBm]
Power
Density
[dBm/Hz]
Total received power

(Total noise)
I+N
(RSSI)
Io
I+N-C
No
(Nt)
Total received power

(Total noise
without useful signal)
Comment
Power Density=Power/B with
B=3.84MHz
I+N= Iintra+ Iextra +N
Note: C is included in (I+N)
No=( Iintra+ Iextra +N-C)/B
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)
RSSI - Received Signal Strength Indicator


Ratio
in [dB]
Ec/Io
Received
energy per
chip over
noise
Received
energy per
bit over
noise
Required
energy per
bit over
noise
Ec/No
(C/I)*
Eb/No
(Eb/No)req
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 P-CCPCH 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...
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)
P-CCPCH
Primary Common Control Physical Channel


Two more
interesting
ratios!
f
(or little i)
Noise Rise
in [dB]
Comment
Iextra / Iintra
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)
(I+N)/N
Very useful UMTS ratio to characterize the moving

interference level I compare to the fixed Thermal
Noise at receiver level N.

1.2.2 Exercise
Surrounding cells
in
Upl
n
k co
si
ed
der
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

1.2.2 Exercise [cont.]

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. Complete the following table:
n
I +N
[users]
[dBm]
[dBm]
Noise
Rise [dB]
Ec/No
Eb/No
[dB]
[dB]
1
10
25
100

Comment
1 UMTS Introduction
y Objective:
{
to be able to describe briefly the structure of a RNP tool

1.3.1 RNP tool requirements
Digital maps
topographic data (terrain height)

y
Resolution:
{
{
Coordinates system
{
{
Resolution: same as topographic data
Propagation model dialog
important for interfacing with measurement tools

e.g. UTM based on WGS-84 ellipsoid
morphographic data (clutter type)

y
typically 20m for city areas and 50 m for rural areas

possibly building and road databases for more accuracy
e.g. setting Cost-Hata propagation model parameters
Site/sector/cell/antenna dialog
importing sites (e.g GSM sites)

setting site/sector/cell/antenna parameters (Network design
parameters)
Note: in UMTS, sector and cell are not equivalent

1.3.1 RNP tool requirements [cont.]
z
z
Link loss calculation

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

z
Coverage predictions
displaying the results on the map
showing the results as numerical tables
z
z
z
Automatic neighborhood planning

Automatic scrambling code planning
Interworking with other tools (dimensioning tools, OMC-UR,
measurements tools, transmission planning tool...)

1.3.2 Example: A9155 UMTS/GSM RNP tool
A9155
screenshot

1 UMTS Introduction
1.1.4
y Objective:
{
to be able to describe briefly the 11 steps of the RNP Process, starting with Radio
Network Requirements definition and ends with Radio Network Acceptance.

1.4.1 The 11 steps of RNP process

1. Radio Network Requirements
7. Basic Parameter Definition
2. Preliminary Network Design
8. Cell Design CAE Data

Exchange over COF
3. Project Setup and

Management
9. Turn On Cycle
4. Initial Radio Network Design
10. Basic Network Optimization
5. Site Acquisition Procedure

6. Technical Site Survey
11. Network Acceptance

(12. Further Optimization)

1.4.2 Step1: Definition of Radio Network Requirements

z
The Request for Quotation (RfQ) from the operator prescribes the
requirements which consists mainly in:
Coverage
Traffic
QoS
CSR = CSSR x (1 - CDR)

1.4.3 Step 2: Preliminary Network Design

z
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
DCM (digital city map)
clutter type
traffic density
of roll out phases
Areas to be covered
Number of sites to be installed
Date, when the roll out takes
place.
zNetwork
architecture design
Planning of RNC, MSC and SGSN

locations and their links
Definition of standard equipment

configurations dependent on
zDefinition
zFrequency
conditions
spectrum from license

1.4.4 Step 3: Project Setup and Management

z
z
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
y 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 (e.g. MatrixX)

1.4.5 Step 4: Initial Radio Network Design

z
Area surveys
As well check of correctness of geo data
z
z
Frequency spectrum partitioning design

RNP tool calibration
For the different morpho classes:
y Performing of drive measurements
y 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
z
z
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

1.4.6 Step 5: Site Acquisition Procedure

z
Delivery of site candidates
Find alternative sites
Several site candidates shall be

the result out of the site location
search
If the reported site is accepted as

candidate, then it is ranked according
to its quality in terms of
y Radio transmission
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)
Site candidate acceptance and ranking
High visibility on covered area

No obstacles in the near field of the
antennas
{No interference from other
systems/antennas
{
{
y Installation costs
Installation possibilities
Power supply
{Wind and heat
{
{
y Maintenance costs
{
Location information
Land usage
Object (roof top, pylon, grassland)
information
Site plan
Accessibility
Rental rates for object
{Durability of object
{
SAM Search Area Map

1.4.7 Step 6: Technical Site Survey

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

1.4.8 Step 7: Basic Parameter Definition

z
After installation of equipment

the basic parameter settings are
used for
Commissioning
y
z
z
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
zCell
parameters definition
LAC/RAC...
Frequencies
Neighborhood/cell handover
relationship
Transmit power
Cell type (macro, micro, umbrella,
)
Scrambling code planning

1.4.9 Step 8: Cell Design CAE Data Exchange
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
ACIE ASCII Configuration Import Export
PRC Provisioning Radio Configuration

SC Supervised Configuration
COF CMA Offsite
CMA Customer Management Application
CAE Customer Application Engineering

1.4.10 Massive Cell Creation Import Planned Data

z
Import Planned Data

NM
Forward planned
UMTS Cell design
at cell creation
Cell Reload
RNP
Planned design
Import RNP
project
Planned
UMTS cell
files
Planned UMTS
Adjacency files
RNO
U_CEL_xxee.rnp
UU_ADJ_xxee.rnp
Planned GSM
cell files
G_CEL_xxee.rnp
UG_ADJ_xxee.rnp
Planned Network Configuration

The OMC-R is designed to cooperate with an external system responsible for radio network planning
(RNP). This external system manages all radio network planning data such as:
Planned cells with most of their design attributes
Planned antennae sites with their names
Geographical coordinates, sector azimuth and cell mapping
Planned cell neighborhood relationships.
it is assumed that RNP files (with cell and adjacency information) are provided. If this is not the case,
refer to the Create RNP Project Manually in the customer documentation.

RNP: Radio Network Planning
Show the objects location on a map (coordinates)
Computes cell design of sub-nets
Calculates scrambling code plan, handover relationships and interferences
Calculates network design parameters
Predicts coverage
RNP provides data export function to RNO
Without RNP: a manual import is possible
RNO f
d l
d UMTS
ll d i

t NM
1.4.11 Step 9: Turn On Cycle

z
z
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
Provisioning Radio Configuration

1.4.11 Step 9: Turn On Cycle [cont.]

z
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
y 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.

1.4.11 Step 9: Turn On Cycle [cont.]

z
HW / SW Problem Detection
Problems can be detected due to drive tests or equipment monitoring

y Defective equipment
{
will trigger replacement by operation field service
y Software bugs
y Incorrect parameter settings
{
are corrected by using the OMC or in the next TOC
y Faulty antenna installation

{
Wrong coverage footprints of the site will trigger antenna re-alignments
If the problem is serious

y
y
y
y
Lock BTS/NodeB
Detailed error detection
Get rid of the fault
Eventually adjusting antenna tilt and orientation

1.4.12 Step 10: Basic Network Optimization

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

1.4.13 Step 11: Network Acceptance

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

1.4.14 (Step 12: Further Optimization)

z
z
z
Network is in commercial operation

Network optimization can be performed
Significant traffic allows to use OMC based statistics by using A9156
RNO and A9185 NPA



Objective
to be able to describe the UMTS RNP inputs with regard to

frequency spectrum, traffic parameters, equipment parameters
and radio network requirements.
Program:
1.2.1
1.2.2
1.2.3
1.2.4
UMTS FDD frequency spectrum

UMTS traffic parameters
UMTS Terminal, NodeB and Antenna overview
UMTS Radio Network Requirements

WObjective:
z
to be able to describe the UMTS FDD frequency parameters defined by the 3GPP

2.1.1.1 Frequency spectrum

zFrequency
spectrum (UMTS FDD mode)
UL: 1920 MHz 1980 MHz

DL: 2110 MHz 2170 MHz
Duplex spacing: 190 MHz
1920-1980
IMT-2000: International Mobile Telecommunications 2000

2110-2170
2.1.1.2 Carrier spacing

zCarrier
spacing: 5MHz
2110 MHz 2170 MHz = 60 MHz; 60 MHz / 5 MHz =12 frequencies

y One operator gets typically 23 frequencies (carriers)
y So typically 46 licenses per country as a maximum
zRequired
bandwidth: 4.7MHz
The chip rate is 3.84Mchip/s, therefore at least 3.84MHz bandwidth are needed to avoid intersymbol 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
Note: Original planned chip rate was 4.096Mchip/s leading to 5 MHz required bandwidth

2.1.1.3 Frequency channel numbering

zUTRA
Absolute Radio Frequency Channel Number (UARFCN)
UARFCN formula (3GPP 25.101 and 25.104):
UARFCN Uplink/Dow nlink = 5 f Center Uplink/Dow nlink [MHz]

with
0.0 MHz f Center Uplink/Dow nlink 3276 .6 MHz
UARFCN is integer:
y 0 <= UARFCN <= 16383

2.1.1.4 Center Frequency
zCenter
Frequency fcenter
Consequence of UARFCN formula (see previous slide):

y fcenter must be set in steps of 0.2MHz (Channel Raster=200 kHz)
y fcenter must terminate with an even number (e.g 1927.4 not 1927.5)
fcenter values
y Uplink (1920Mhz-1980MHz)
{
{
1922.4MHz <= fcenter <= 1977.6MHz

9612 <= UARFCN Uplink <= 9888
y Downlink (2110Mhz-2170MHz)
{
{
2112.4MHz <= fcenter <= 2167.6MHz

10562 <= UARFCN Downlink <= 10838

2.1.1.5 Further comments

z
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:
it shows an overlap of 0.3 MHz between two carriers of one operator0.6 MHz additional channel
separation between the operators is created.
5 MHz
5 MHz
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
WFrequency coordination at country borders (see Appendix)


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

2.1.2.1 Step 1: Terminal parameters

Terminal parameters
Tx power
(dBm)
(typical values)
Min
Max
Antenna
Gain
(dB)
Deep Indoor
15
Incar
8
0
-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.

Parameter
Description
Name
User equipment name (mobile phone, PDA, in-car navigator

device, etc)
UE minimum transmission power
(According 3GPP 25.101)
UE maximum transmission power
Class 1/2/3/4 -> 33/27/24/21 dBm
PDAs are assumed to be class 3 mobiles (24 dBm).
UE antenna gain (default = 0 dB, because it is assumed to
compensate with internal losses)
Internal losses are assumed to be 0, as they compensate with the
UE antenna gain.
(Indoor penetration margin can be added here)
UE internal thermal noise factor
Definition of Terminal Parameters:
Min. Power
(dBm)
Max. Power
(dBm)
Gain(dB)
Internal Losses
(dB)
Noise Factor
(dB)
Active set size
Number of transmitters that can be simultaneously connected to

the UE (soft/softer handover).
Alcatel-Lucent UTRAN can handle up to 6 cells in active set (4 in
soft handover and 2 in softer handover). A955 V6 is limited to 4

Speech 12.2
CS 64
PS 64
PS 128
PS 384
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
0.6
1
1
3
-50
+15
Activity factor and Body loss are part of service parameters
Definition of Service Parameters

Parameter
Description
Name
Type
Priority
Service name for RNP purposes: e.g. AMR or Web

Packet switched service or circuit switched service
Number >=0 that indicates the priority of a service. 0 is the lowest
priority.
Soft handover allowed for this service. Depends on used channels.
SHO only possible for DCH connection, not for RACH/FACH or DSCH.
User bit rate in Kbits/sec for each service.
SHO allowed
Nominal rate for UL
and DL (kbits/sec)
Coding factor for UL
and DL
Activity factor for UL
and DL
The coding factor is set to 1, since the Alcatel-Lucent Eb/No values

already consider all overhead including coding.
Occupancy factor of a circuit switched connection, i.e. percentage
of the time that the active user is transmitting while the connection is
established.
Parameter
Description
Efficiency factor for

UL and DL
The efficiency factor shall model the additional data volume due to
retransmission.
Its value depends on the BLER considered for the Rx Eb/No target.
Voice services (BLER 0.01) :1.01
Other CS services (BLER 0.0001) :1.0001
PS services (BLER 0.05) :1.01
Allowed Downlink
power minimum
and maximum
(dBm)
Body loss (dB)
Eb/Nt (UL) and
Eb/Nt DL
1 can be taken as default value.

Downlink power control dynamic range. In TS25.104, it is defined as:
Maximum power: BS maximum output power -3 dB or greater
Minimum power:
BS maximum output power 28 dB or less
Signal attenuation due to the users body
Minimum signal to noise ratio that must be received in the UL/DL for that
service. These values depend on the user mobility and the service.
Max
Body loss
(dB)
DL
Activity Factor
(UL/DL)
UL
DL
Coding Factor
UL/DL
120 km/h
UL
DL
DL nominal rate
(Kb/sec)
50 km/h
UL
UL nominal rate
(Kb/sec)
3 Km/h
Priority
(typical
values)
(Eb/No)req (dB)
Type
Service
parameters
SHO allowed
2.1.2.2 Step 2: Service parameters
+40
0
2.1.2.2 Step 2: Service parameters [cont.]

(Eb/No)req typical values
fixed values which depends on link
direction (UL or DL )service bit rate, BLER
(or BER), UE speed, UE multipath
environment, TX/RX diversity and
processing/hardware imperfection margin
(2dB)
Speech services for a target BLER of 0.01(10-2)
PS services for a target BLER of 0.05

PACKET 64
Vehicular A - 3 km/h
PACKET 128
Uplink Downlink
2 rx ants
1 tx ant
SPEECH 12.2
5,8
6,2
7,1
7,6
8,1
8,7
CS services for a target BLER of 0.0001 (10-4)

Uplink Downlink
2 rx ants
1 tx ant
CIRCUIT 64
3,2
3,5
4,4
6,2
6,5
7,1
PACKET 384
Uplink Downlink
2 rx ants
1 tx ant
2,8
3,2
4,2
Uplink Downlink
2 rx ants
1 tx ant
2,1
2,5
3,4
1,8
2,2
3,0
Description
Occupancy factor of a circuit switched connection, i.e. percentage

of the time that the active user is transmitting while the connection is
established.
Parameter
Description
Efficiency factor for

UL and DL
The efficiency factor shall model the additional data volume due to
retransmission.
Its value depends on the BLER considered for the Rx Eb/No target.
Voice services (BLER 0.01) :1.01
Other CS services (BLER 0.0001) :1.0001
PS services (BLER 0.05) :1.01
Allowed Downlink
power minimum
and maximum
(dBm)
Body loss (dB)
Eb/Nt (UL) and
Eb/Nt DL
1 can be taken as default value.

Downlink power control dynamic range. In TS25.104, it is defined as:
Maximum power: BS maximum output power -3 dB or greater
Minimum power:
BS maximum output power 28 dB or less
Signal attenuation due to the users body
Minimum signal to noise ratio that must be received in the UL/DL for that
service. These values depend on the user mobility and the service.
5,2
6,1
6,8
Source: Alcatel-Lucent simulations
Name
Service name for RNP purposes: e.g. AMR or Web
Definition
Type of Service Parameters
Packet switched service or circuit switched service
Priority
Number >=0 that indicates the priority of a service. 0 is the lowest
priority.
SHO allowed
Soft handover allowed for this service. Depends on used channels.
SHO only possible for DCH connection, not for RACH/FACH or DSCH.
Nominal rate for UL
User bit rate in Kbits/sec for each service.
and DL (kbits/sec)
Coding factor for UL The coding factor is set to 1, since the Alcatel-Lucent Eb/No values
and DL
already consider all overhead including coding.
Activity factor for UL
and DL
4,8
5,5
6,1
Uplink Downlink
2 rx ants
1 tx ant
Parameter
5,5
6,2
6,7
2.1.2.3 Step 3: User Profile parameters

Traffic Density
User Profile
(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.
User profile = one type of user

A user profile reflects the typical behavior for one type of user:
used service(s): single service (e.g surfing user) or multiple service (e.g. city user)
service usage: traffic density for each service
Traffic density:
for circuit switched services the parameter duration must be provided
for packet switched services the volume in Kbytes in UL and DL must be provided
Note: never both duration and volume for the same service

2.1.2.4 Step 4: Environment Class parameters

z
z
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
class*
(Examples)
User profiles
(see Step 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)

2.1.2.5 Step 5: Traffic Map definition

z
Mapping of Environment Classes (see Step 4) on a map:

Example with 4 environment classes: Dense Urban, Urban, Suburban,
Rural
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)

y Objective:
{
to be able to describe briefly the main characteristics of the UMTS radio equipment
(UE, NodeB and antenna)

2.1.3.1 UE characteristics
zAccording
to 3GPP 25.101 (Release 1999):
UE power classes at antenna connector*:

y
y
y
y
Power
Power
Power
Power
class 1: (+33 +1/-3)dBm

class 2: (+27 +1/-3)dBm
class 3: (+24 +1/-3)dBm
class 4: (+21 2)dBm
UE minimum output power: <-50dBm

zAccording
to UE manufacturers:
UE Noise Figure: 8dB (typically)

UE internal losses + UE antenna gain = 0dB
zWhat
is EIRP for a UE of power class 4?

* the notation means e.g. for class 1:
- Maximum output power: +33dBm
Answer:
UE EIRP=UE TX Power+ UE Antenna Gain - UE Internal Loss=21dBm + 0 dB = 21 dBm
- Tolerance: +1dBm/-3dBm
Note: UE antenna gain is supposed to compensate for UE internal losses

2.1.3.2 Alcatel-Lucent Node B

The Alcatel-lucent BTS 12010 (indoor):
is a fully integrated self-contained cell-site

with up to 3 sectors & 3 carriers in a single cabinet
Node B
UE
UE
UMTS
UMTS
Iub
RNC
Iub
UE

The Node B is in
charge of radio
transmission handling
(with W-CDMA
method)
2.1.3.2 Alcatel-Lucent Node B [cont.]

Sector 2
Sector 1
Sector 3
RF Feeders
BTS
Power supply:
- 48 V DC
AC main
RF block
TX amplification (PA), coupling
Interco
module
Iub
RNC
Rx
signal
Tx
signal
Digital shelf
Network interface
Call processing
Signal processing
Frequency up/down conversion
External
alarms
The
UMTS BTS is built around two main blocks: the Digital shelf and the RF block.
The main functions of the Digital shelf are:
network interface,
call processing,
signal processing,
frequency up/down conversion.
The main functions of the RF block are:
TX amplification (Power Amplifier),

coupling (Duplexer).
The Interco module is a passive module that carries digital signals between the two blocks.


OA&M Bus
Alarm connectivity
MCA
Digital shelf
GPSAM
RF block
Tx Splitter
(optional)
CEM
TRM
CCM
Transmit/
Receive/
Channelizer
Call
Processing
Transmit/
Receive
Baseband
Processing
CCM
DDM
PA
Rx
Tx
OA&M
Iub, to/from RNC

All the modules included in the cabinet (except MCA), can be gathered into two separate units:
The Digital shelf: CEM, CCM, TRM, GPSAM.

The RF block: DDM and MCPA.
The call processing and the transmit and receive baseband signal processing functions are
performed by the CEM/iCEM (Channel Element Module).
The OAM management and part of the call processing and internal/external data flow
switching / combining is carried out by the CCM/iCCM (Core Control Module).
The receive / transmit channelizer function and the support of RF Block connectivity interface
goes to the TRM/iTRM/xTRM (Transmit Receive Module).
The external / internal alarm connectivity and the external synchronization reference interface
is achieved by the GPSAM/cGPSAM (GPS and Alarm).
The Tx RF signal amplification is performed by the PA (Power Amplifier).
The RF input signal separation is achieved by the Tx-Splitters, (in OTSR configuration only).
The isolation of Tx / Rx frequency bands as well as the filtering is done by the DDM (Dual
Duplexer Modules).
The MCA (Manufacturing Commissioning and Alarm module) is in charge of storing all
commissioning information and collecting manufacturer alarms.


OA&M Bus
Alarm connectivity
MCA
Digital shelf
GPSAM
RF block
Tx Splitter
(optional)
CEM
Call
Processing
Transmit/
Receive
Baseband
Processing
TRM
CCM
CCM
Transmit/
Receive/
Channelizer
DDM
PA
Rx
Tx
OA&M
Iub, to/from RNC

All the modules included in the cabinet (except MCA), can be gathered into two separate units:
The Digital shelf: CEM, CCM, TRM, GPSAM.

The RF block: DDM and MCPA.
The call processing and the transmit and receive baseband signal processing functions are
performed by the CEM/iCEM (Channel Element Module).
The OAM management and part of the call processing and internal/external data flow switching /
combining is carried out by the CCM/iCCM (Core Control Module).
The receive / transmit channelizer function and the support of RF Block connectivity interface goes
to the TRM/iTRM/xTRM (Transmit Receive Module).
The external / internal alarm connectivity and the external synchronization reference interface is
achieved by the GPSAM/cGPSAM (GPS and Alarm).
The Tx RF signal amplification is performed by the PA (Power Amplifier).

The RF input signal separation is achieved by the Tx-Splitters, (in OTSR configuration only).
The isolation of Tx / Rx frequency bands as well as the filtering is done by the DDM (Dual Duplexer
Modules).
The MCA (Manufacturing Commissioning and Alarm module) is in charge of storing all
commissioning information and collecting manufacturer alarms.


Digital shelf
CEM 1
GPSAM
RF block
TRM 1
PA 1
MCPA
CEM 2
DDM 1
Sector 1
D
CCM 1
CEM 3
TRM 2
PA 2
MCPA
CEM 4
OA&M
DDM 2
Sector 2
CEM 5
TRM 3
CEM 6
PA 3
MCPA
Network Interface: Iub, to the RNC
(E1 and ATM/AAl2 capability)
DDM 3
D
Solid lines indicate plane 0 interconnect, dashed lines plane 1.

The Digital shelf includes four types of modules:
one CCM (or two iCCM) - Core Controller Module,

up to 6 CEM - Channel Element Module,
up to 3 TRM - Transmitter/Receiver Module,
one GPSAM - Global Positioning System and Alarm Module.
The RF block contains the RF modules:
1 to 6 Multi Carrier Power Amplifiers (MCPA),

3 or 6 Dual Duplexer Modules (DDM),
1 or 2 Tx splitter(s), in OTSR configuration only.
The RF ports are connected to the two antenna connectors of the three or six DDMs.

Sector 3
2.1.3.3 UMTS antennas

z
Constraints for antenna system installation:
visual impact
space or building constraints
co-siting with existing GSM BTS
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

2.1.3.3 UMTS antennas [cont.]

z
Antenna parameters are key parameters which can be tuned to

decrease interference in critical zones, especially:
Antenna downtilt
y
y
y
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 choose for GSM
Antenna azimuth
y
y
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)

y Objective:
{
to be able to understand the parameters, which define the UMTS radio network
requirements in terms of coverage, traffic and quality of service

2.1.4.1 Definition of radio network requirements

z
Traffic mix and distribution for traffic simulation with the aim to
predict power load in DL and UL noise rise
Covered area
Polygon surrounding the area to be covered (focus zone for RNP tool)
Definition of what coverage is

CPICH Ec/Io coverage
y (CPICH Ec/Io)required=-15dB (Alcatel-Lucent value coming from simulations and field
measurements)
y Required coverage probability for CPICH Ec/Io:
e.g. Average probability {CPICH Ec/Io > (CPICH Ec/Io)req} > 95%
(with this definition a minimum average quality in the covered area is
guaranteed*)
*other definitions of required coverage probability are possible,
e.g. 95% of area with CPICH Ec/Io > (CPICH Ec/Io)required
(with this definition, a minimum percentage of covered area is
guaranteed)

2.1.4.1 Definition of radio network requirements [cont.]

UL and DL service coverage
y (Eb/No)reqspecific value for each service and for each direction (UL/DL),
y 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).

2.1.4.1 Definition of radio network requirements [cont.]

CPICH RSCP coverage (optional)
y (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)
y 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.

3 Link Budget (in Uplink) and Cell Range

Calculation


z
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:
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
Inputs for a manual UL link budget

UMTS propagation model
UMTS shadowing and fast fading modeling
Calculation of Node B reference sensitivity
UMTS interference modeling
Calculation of cell range

3.1.1 Principle for Cell Range calculation

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

Lpath = MAPL for d=Cell Range.
We calculate MAPLk for the limiting service k in UL:
MAPL
[dB ]= EIRP UE [dBm ] Reference_ sensitivit y NodeB, k [dBm ]

Margins [dB ] Losses [dB ]+ Gains [dB ]
EIRPUE
Reference_sensitivityNodeB,k
gins
Mar
es
Loss
ns
Gai
UE
d=Cell Range
MAPL = Maximum Allowed Path Loss

Node
B
3.1.2 Inputs for the UL link budget

Margins
Shadowing margin*
see 3.2.2
Fast fading margin
see 3.2.3
Interference margin
see 3.4.1
Losses
Feeders and connectorsNodeB
typically 3dB (it depends on the feeder length..)
Body loss
see 2.1.2.2
Penetration loss (indoor

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

3.1.3 How to calculate the Pathloss Lpath?

W In UMTS radio environment, the propagation waves are subject to complex
mechanisms:
z Free Space Propagation
z Slow fading (Shadowing)
z Reflections/Refractions/Scattering
z Fast Fading (Multipath fading)
z Diffraction
z
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).( http://en.wikipedia.org/wiki/Free_space_loss)
Empirical formulas:
The most effective approach is based on the classical COST 231-Hata formula,
extended for the usage on higher frequencies or additional propagation effects.
e.g. Alcatel-Lucent selected as UMTS propagation model a slightly modified COST 231Hata model, called the Standard Propagation Model*.
*see Appendix for the relationship between COST231- Hata and the Alcatel-Lucent Standard
Propagation Model
Note: the Pathloss is also called Propagation Loss

COST 231-Hata has been used for GSM 900 and GSM 1800 and it can be reused for UMTS:
This is stated and verified by different publications
E.g. M. Hata: Propagation Loss Prediction Models - in Wireless Communications in the 21st Century,
published by IEEE, 2002.

What about the influence of rain attenuation on the pathloss Lpath in UMTS?
In the UMTS frequency spectrum (2GHz) the attenuation due to rain can be neglected. Rain attenuation shall
be considered for higher frequency bands (>5 GHz) used for microwaves or for satellite communications.
Recall on diffraction:
Occurs at objects which sizes are in the order of the wavelength
Radio waves are bent or curved around objects
Bending angle increases if object thickness is smaller compared to wavelength
Influence of the object causes an attenuation: diffraction loss
radio
obstacle
shadow
zone

diffracted
radio

z
Lpath formula:
K1 + K2 log(d ) + K3 log H NodeBeff + K4 f (diffraction) +
Lpath =
(
)
(
)
K
d
H
+
K
f
H
+
K
f
clutter
log
log
(
)
NodeBeff
6
UEeff
clutter
5
with*
d : distanceNodeB-UE (m)
HNodeBeff : effectiveantennaheight of NodeB(m)
HUEeff : effectiveantennaheight of UE (m)

Important: this formula takes into account
*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)
free space propagation, reflections /refractions/scattering and diffraction

not slow and fast fading effects (never considered in propagation model, but
as margins)

3.1.4 Alcatel-Lucent Standard Propagation Model [cont.]

z
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 :
y are equal on a flat terrain (of course)
y 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.
Comments:
there is no standard definition of the effective antenna height. Different methods exist which all
provide good or bad results depending on the terrain profile.
Example of effective antenna height calculation method (one of the five methods available in A9155
RNP tool):
Height above average profile: the transmitter antenna height is determined relative to an average
ground height calculated along the profile between NodeB and UE.
The HNodeB eff and HUE eff values are used directly in the Lpath formula and to calculate f(diffraction) as
well.


z
Propagation model parameters (1)

Multiplying factors (directly derived from COST-Hata model)
Nam
e
Comment
Value
Factor
related to
constant
offset
K2
23.6
(for f=
2140MHz
)
44.9
same comment as K1.
K3
5.83
HNodeB eff
same comment as K1.
K5
-6.55
d , HNodeB
same comment as K1.
K6
K1
used to take into account free space propagation and

reflections/refractions/scattering mechanisms for a
standard clutter class.
eff
HUEeff
same comment as K1. As the contribution of f(HUEeff) is

close to zero, K6 is set to zero.
Comment:
The K1 values is calculated for a fixed frequency f=2140 MHz (middle of DL band).
As a consequence, the UL pathloss is overestimated
(+0.8dB compared to the DL one) due to a
Duplex-Spacing of 190MHz.


z

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

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

compared to the standard clutter class see further
comments on f(clutter).


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



z
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
LO S
H
UE
Fresnel Ellipsoid
(first order)
Node
B
Infinite conductive plane

y What is the diffraction loss in case 1 (use the curve on the next page)?

Answer:
h0=r v=-1 f(diffraction)=14dB

z

Case 1: one obstacle (continuing)
y Diffraction loss for one obstacle:
v: clearance
parameter,
v=-h0/r
r: Fresnel ellipsoid
radius,
h0: height of obstacle
above line of sight
(LOS)
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)

Note:
h0 = 0 v =0
F(v) = 6 dB

z

Case 2: several obstacles
LO S
Node
B
UE
y 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).
y Different calculations methods can be applied based on the General method for one
or more obstacles described in ITU P.526-5 (08/97) recommendations, e.g Deygout,
Epstein-Peterson or Millington


z
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 typically 200m).
*(also called clutter or morpho correction factor)
Pixel
e
stanc
i
d
x
Ma
UE
Node
B
Forest clutter class pixel

clutter loss = -9 dB (typically)
in this example, 3 pixels are

considered to calculate f(clutter)
Water clutter class pixel

clutter loss = -27 dB (typically)
Clutter loss in A9155 version6.x (experienced values)

You can see that:
- the maximum clutter loss is reached for building / skyscrapers
- the minimum clutter loss for water.
Clutter Class
Clutter Loss
buildings
-1.0
dense urban
-3.0
mean urban
-6.0
suburban
-8.0
residential
-11.0
village
-14.0
rural
-20.0
industrial
-14.0
open in urban
-12.0
10
forest
-9.0
11
parks
-15.0
12
open area
-24.0
13
water
-27.0


z
Calculation of f(clutter):
How are the clutter loss provided values?
y based on experienced values: simple, accuracy of +/-3 dB (see previously)
y 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:
y 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

y 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 calibration is recommended.
Details on fixed offset:

Small correction due to overestimation of frequency impact necessary
According to Hata, the propagation loss is increasing with 20*log(f/MHz) over the whole Mobile
Communication Band
The COST-Hata model states 33*log(f/MHz)
For a DL frequency of 2140 MHz, 0.9dB have to be substracted from the Pathloss
Details on Correction Offset per clutter:

-The reflection coefficient shows no explicit frequency dependency.
-Up to 0.6 dB higher diffraction loss in urban environments due to increase f the diffraction coefficient (in
linear scale) by .
-Significant increase of pathloss is possible if large vegetation is penetrated.
E.g. 0.7 dB higher Pathloss for 2140 MHz compared to 1850 MHz if the vegetation object is 50 m long
-For open areas there is no to low influence of reflection/diffraction, as these effects are not dominant there.
Conclusion on correction offset per clutter:
Except for clutter types manly covered by vegetation, there should be only low influence of the frequency and bandwidth
on reflection/diffraction behavior, and therefore on the clutter correction offset.


z
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:
f(clutter)
(simplified*)
Clutter Class
Dense urban
-3
Urban
-6
Sub-urban
-8
Rural
*Assumption:
homogeneous
clutter class around
the UE
-20
What is a clutter class (also called morpho class)?

Clutter databases (also called Morpho or Landuse) are a kind of geodata giving information about the
landuse of different areas. E.g. where do we have urban environments, where do we have rural
environments etc. The clutter database is beside the topographical database (DEM Digital Elevation Model)
the basic input for radio network planning. Areas with similar wave propagation conditions are grouped in
clutter classes, e.g Skyscrapers/Buildings, water, rural, urban, dense urban
How many clutter classes are there?
In the Alcatel-Lucent Radio Network Planning Tool A9155 Version 6.x. you can define up to 256 different
clutter classes(!), but it is usually sufficient to take about 15 clutter classes or even less depending on the
diversity of your environment.
What is the resolution of the clutter databases?

it should be adapted to the necessary planning resolution. In most cases the resolution of the
rasterdatabases for clutterstructure is 20 m for city areas and 50 m for areas outside of the cities. With those
values an optimum between calculation time and resolution of the prediction is reached in most radio
network planning projects. In dense urban areas a more accurate prediction might be required using
building databases instead of a clutter database.

3.1.5 Other Propagation Models

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


z
Exercise:
Lets consider the simplified* formula of the Alcatel-Lucent 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
dUE-
Clutter
class
NodeB
[km]
C1
[dB]
C2 x log(dUE-NodeB)
[dB]
0.5
Dense
Urban
1
2
0.5
Suburban
1
2

Lpath
[dB]
y 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

3.2.1 Definition of fading

z
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
UE received power C
L path
Lo
+
sses
ins
arg
M
ns
Gai
)
ding
a
f
t
ep
(exc
Reference_SensitivityNodeB
,k= Cthreshold
Node
B
Cell Range
UE received power C
oscillates around a
mean value Cmean
equal to Cthreshold
Cmean
=Cthreshold
(fixed value)
Time
(fixed value for a given

service k)

3.2.1 Definition of fading [cont.]

Shadowing (or Slow Fading or longterm fading )
UE received power C
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
Remark: especially Slow Moving Mobiles suffer from fading, because the time suffering from a fading notch
is longer.

3.2.2 Shadowing
z
Cause:
Shadowing holes appear in the
received power C when the UE is
in the shadow of large objects
(size>10m)
zModeling:
The received power C can

be modeled as a Log-normal
distribution with:
std dev=8 dB
std dev = 4dB
std dev= 2dB
std dev= 6dB
Probability
a mean value Cmean

a standard deviation , typically
=7-8 dB (clutter dependent)
Note: GSM1800 calibrations can be
reused for the values.
Signal distribution
Cmean
Note: The shadowing margin is an even function (variances are equal around the medium
value).
Reuse of GSM800 calibrations for Clutter Std. Deviation values
Due to higher frequency in 3G and depending on the environment, a very low increase in standard
deviation is possible.
Empirical Slow fading modeling:

Measurements in different environments show that the density distribution
function of a shadowing signal can be modeled with a Log-normal distribution

of zero mean and a standard deviation that is characteristic on the
environment.

3.2.2 Shadowing [cont.]

z
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
Reliability marginx% =Cmean offset compared to the fixed Cthreshold to get a
reliability level of x%
UE received power C
*also called local coverage

probability or coverage probability
per pixel
50
%
UE received power C
Cmean
Cmean
Cthreshold
=Cthreshol
d
(fixed
value)
Wanted reliability level=50%

Reliability margin50%=0dB
Cmean = Cthreshold
95
%
Time
(fixed
value)
reliability margin
Time
Wanted reliability level=95%

Reliability margin95%=10dB (for =6)
Cmean = Cthreshold +10dB
(see next slide for calculation of Reliability marginx%)


z
Calculation of reliability margin*:

It depends on the reliability level and on the standard deviation
k
-0.5
1.3
1.65
2.33
Reliability
level
0%
30%
50%
84%
90%
95%
97.7
%
99%
100
%
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)
Reliability level (also called local coverage

probability or coverage probability per pixel)
100%
95,2
80% %
60%
50%
probability
40%
for
Fmed=Fthr
20%
0%
-20
-10
Reliability
margin95.2%=10dB
0

10
20
F = (Fmed - Fthr) /dB

z
Values for the standard deviation :
Power level [dBm] (e.g CPICH RSCP):
Ratio [dB] (e.g CPICH Ec/Io or UL/DL Eb/No)
y
y
it can be modeled as a log-normal variable with a standard variation (clutter

dependent value, typically 7dB or 8dB)
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. UL Eb/No is a clutter dependent value as
for CPICH RSCP


z
Definition of area (cell) coverage probability:

If the reliability levels are provided at each pixel of an 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%
z 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).


z
Definition of shadowing margin:

If the area (cell) coverage probability is provided (from the radio network
requirement, see 1.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 Gain

*the UMTS shadowing margin (defined above) is NOT the same as the GSM shadowing margin(=Reliability Margin)


z
How to calculate the shadowing margin for a received power C?

It depends on:
y Wanted cell coverage probability
y Clutter class of the UE
y UE soft/softer handover state and correlation factor between UE radio links (0=no
correlation, typically 0.5)
Examples in uplink (Source: Alcatel-Lucent simulations)

Cell
coverage
probability
Shadowing Hole
Soft Handover Zone

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 additional path loss
caused by shadowing.

3.2.3 Fast Fading

z
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
Rayleigh
Small-Scale

3.2.4 UL Fast Fading

z
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:
y 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)
y Side effect: increase of f value (little i value) for the surrounding cells (see further)
Case 2: fast moving UE (>50km/h)

y Power Control loop is too slow to compensate for fast fading
y A margin is necessary to compensate for the fast fading losses: this margin is not
explicit, but implicitly included in the (Eb/No)req values

3.2.4 UL Fast Fading [cont.]

z
How to calculate Power Control Headroom (Fast Fading Margin) for

slow moving UEs (Case 1)?
Fast fading depends on:
y
y
y
y
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-Lucent simulations)
Multipath
environment
Dense urban, urban,
suburban (Veh. 3km/h)
Rural (Veh. 50 km/h)
Fast fading margin (dB) for

several target BLER
10-1
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
3.2.4 UL Fast Fading [cont.]

z
What about the side-effect for slow moving UE (Case 1)?

Fast fading in serving cell and in neighboring cells are not correlated:
9 impact on neighboring cells due to UE TX power increase which causes
additional UL extra-cell interference (called average power rise)
9 increase of f value (little i value)
15
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

3.2.5 DL Fast Fading

z
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:
y
y
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
useratatthe
theother
other
side
sideof
ofthe
thecell
cellfaces
faces
fading
at
hole ofhole
shadowing
at
the
thesame
sametime
timeisisvery
very
low
low
Fading holes
TX Power

A margin for each

link is not realistic !
y Objective:
{
to be able to calculate the reference sensitivity for a given service bit rate,
BER, UE speed and UE multipath environment

3.3.1 Definition of Reference_Sensitivity

z
The received Eb/No for a given UE at the

NodeB reference point must apply:
Antenna
Eb/No[dB] > (Eb/No)req [dB]
Note:
Eb/No=C/(I+N C) + PG (definition, see 1.3)
NodeB reference point=NodeB antenna connector (see

3GPP 25.104)
Feeder
UE
Node
B
NodeB
antenna
connector
WAs 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 1.3.5 for more details

3.3.2 Calculation of Reference_Sensitivity
Re ference_Se nsitivity [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):

y
y
y
PG=25dB for speech 12.2k

PG=17.8dB for CS 64k
PG=10dB for PS 384k
(Eb/No)req is a fixed value

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

y 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

3.4.1 Calculation of interference margin

z
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:
Interference 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):
y I=Cmin Noise Rise ~ 0,2dB
y I=N Noise Rise=3dB
y I=3N Noise Rise=6dB
{10 log {1+ (Ec/No)req[linear]}
y typically between 0.1dB (for speech 12.2k) and 0.8dB (for PS 384k)
y small value because (Ec/No)req (linear value) <<1 (the useful signal level is always
far below the noise floor in W-CDMA )
y it can be neglected except for very high bit rates

3.4.2 Noise Rise and Traffic load

z
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
XUL=sumall UEs in the network(Xj) ; XDL=sumall NodeBs in the network(Xj)
We can demonstrate that:

Noise Risel (dB)
1
Noise Rise [dB] = 10 log
1 X
Example in Uplink
35
30
25
20
15
max loading : 75%
50% of cell load

(3dB of interference)
10
5
0
0
11
21
31
41
51
61
71
81
91
100
XUL (%)
Cj =
X =
( Xj (I
I
I + N
+ N
)) = (I
+ N
)(
Xj
I + N N
N
1
= 1
= 1
I + N
I + N
N oiseRice

3.4.2 Noise Rise and Traffic load [cont.]

Downlink
Uplink
zNoise Rise and XUL are cell specific
parameters (useful to characterize UL
cell load)
zNoise Rise and XDL are UE

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

adding new UEs in the network)
Noise Rise can tend towards infinity
the system can be unstable.
zXDL 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.

3.4.3 Traffic load and UL load factor

z
Relationship between XUL and traffic load for one cell:

Does XUL depend on:
y the traffic mix?

y the user distribution in the serving cell?
y 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 Factor
ServiceBit Ratek
k
Chip
rate
req,k
XUL
k =1
Activity Factor
ServiceBit Ratek
k
Chip rate
req,k
with N number of users in the servingcell
N
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
Side effect of fast fading on f (little i)
System limit
In reality the system will not operate beyond a certain limit of the cell loading since the system can become
unstable for a high cell load. This maximum value is usually between 65% and 75%. It is therefore still
reasonable to dimension for an uplink cell load of 50% in order to maintain a certain capacity margin before
reaching the maximum allowed cell load.

3.4.3 Traffic load and UL load factor [cont.]
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)
Side effect of fast fading on little f
System limit
In reality the system will not operate beyond a certain limit of the cell loading since the system can become
unstable for a high cell load. This maximum value is usually between 65% and 75%. It is therefore still
reasonable to dimension for an uplink cell load of 50% in order to maintain a certain capacity margin before
reaching the maximum allowed cell load.

3.4.4 What about DL load factor?

z
As Noise Rise and XDL are not convenient to characterize the DL cell
load, another parameter is commonly used:
DL power load factor [%] =

z
TX power NodeB for the cell[W]

Maximum TX power NodeB for the cell[W]
Orthogonality effect
In downlink, the orthogonality of channelization codes reduces the intracell interference Iintra:
Iintra [W]=(1-) x sumDL users in the cell (Ci) with Orthogonality Factor
y =0no orthogonality Iintra= sumDL users in the cell (Ci)
y =1perfect orthogonality Iintra= 0 W
3GPP values for Orthogonality Factor :

y =0.6 for Vehicular A
y =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 synchronized each
over.

y Objective:
{
to be able to calculate the MAPL with a manual UL link budget and to deduce
the cell range

3.5.1 Exercise: MAPLUL calculation

z
Fixed assumptions:
EXAMPLE 1:
Antenna gainUE + Internal lossesUE = 0dB

Antenna gainNodeB=18dBi
Feeder and Connector losses=3dB
Thermal noise=-108.1 dBm and NFNodeB=4dB
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?

3.5.1 Exercise: MAPLUL calculation [cont.]
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%
Value
in
Comment
f.a.=fixed
assumption
(see
previously)
A. On the transmitter side

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

B1
(Eb/No)req
dB
see 1.2.2
B2
Processing Gain
dB
see 1.1.3
B3
NFNodeB
dB
f.a.
B4
Thermal noise
dBm
f.a.
B5
dBm
B1-B2+B3+B4
(continuing on next slide)



EXAMPLE 1 continuing
Value
in
Comment
f.a.=fixed
assumption
(see
previously)
C. Margins
C1
Shadowing margin
dB
see 1.3.3
C2
Fast fading margin
dB
see 1.3.3
C3
Noise Rise
dB
see 1.3.5
C4
10 log {1+ (Ec/No)req}
dB
see 1.3.5
C5
Interference margin
dB
C3-C4
D. Losses
D1
Feeders and connectors
dB
f.a.
D2
Body loss
dB
see 1.2.2
D3
Penetration loss (indoor margin)
dB
see 1.2.2
dBi
f.a.
dB
=?
E. Gains
E1
Antenna gainNodeB
MAPL


UE power class ?
Service: ?
Multipath Environment: ?
UE in soft(or softer) handover state?
Indoor margin:?
Cell coverage probability=?, =?
UL load factor=?
Value
in
Comment
f.a.=fixed
assumption
(see
previously)

A1
UE TX power
A2
A3
EIRPUE
24
dBm
dB
see 1.2.3
f.a.
24
dBm
A1+A2
3.2
dB
see 1.2.2
17.8
dB
see 1.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
B1-B2+B3+B4



Value
in
Comment
f.a.=fixed
assumption
(see
previously)
C. Margins
C1
Shadowing margin
4.8
dB
see 1.3.3
C2
Fast fading margin
-0.3
dB
see 1.3.3
C3
Noise Rise
dB
see 1.3.5
C4
0.1
dB
see 1.3.5
C5
Interference margin
2.9
dB
C3+C4
D. Losses
D1
dB
f.a.
D2
Body loss
dB
see 1.2.2
D3
dB
see 1.2.2
18
dBi
f.a.
139.3
dB
E. Gains
E1
Antenna gainNodeB
MAPL

3.5.2 Exercise: cell range calculation

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


4.1 Objective
z
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.
W Program:
1.4.1
Positioning the sites on the map
1.4.2
Coverage Prediction for CPICH RSCP
1.4.3
UMTS Traffic Simulations
1.4.4
Coverage Predictions for CPICH Ec/Io and DL/UL services
1.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-Lucent 9155 RNP Operation)

4.2 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)
CPICH RSCP
coverage
prediction
(4.2)
Positioning the
sites on the map
(4.1)
Change network
design parameters
NO
RNP
requirements
fulfilled?
Basic radio network

optimization (6)
Fixed load
approach
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 definition (5)

YES
4.2 Overview
y 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.

4.2.1.1 Calculation of inter-site distance

z
Manual Method:
Description:
1. calculate MAPLUL for the limiting service by performing a manual UL link
budget (see 1.3.1.1)
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

4.2.1.2 Site map

z
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 1.2.2)
W The initial site map is

regularly updated based on
site acquisition and site
survey results.
Planning area
Inter
dista-site
nce
Note: At this stage, search

radii may already be
issued, in order to start the
long process of site
acquisition
Site map

4.2.1.3 Network Design Parameters

z

site wise
Number of UL/DL hardware
resources
Typical value
R2:
R3:
R4:
R5:
2
4
4
6
CEM boards
CEM boards
CEM boards
CEM boards
3-6
Number of sectors
Comment

see 1.2.3
4.2.1.3 Network Design Parameters [cont.]

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

30-35 m for suburban
gain
18dBi
downtilt
RXdiv
TXdiv
mechanical +electrical
downtilt
yes
no
DL feeder and connector losses
3dB
see 1.3.1
UL feeder and connector losses
3dB
see 1.3.1
Noise Figure
4dB
see 1.2.3

4.2.1.3 Network Design Parameters [cont.]

z .
Network
design parameters
cell wise
also called Cell Parameters
Typical value
Comment
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
Max. total power (for the cell)
43dBm
see 1.2.3
CPICH (Pilot) power
33dBm
10% of Total power
Other common physical

channels power
35dBm
CPICH power + 2dB
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
AS threshold

4.3 Name of Level 2
CPICH RSCP (=CCPICH=Pilot level= Pilot field strength)

y 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

4.3.1.1 How to perform the prediction?

W 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

4.3.1.1 How to perform the prediction? [cont.]

W Step2: the tool calculates the CPICH RSCP values for the virtual UE
(without considering shadowing effect)
loss
Path
L path
CPICH RSCP(=CPICH RX power)
CPICH TX power
Node
B
Virtual UE
No shadowing
(Shadowing margin=0dB in this
step)
at each pixel*:
CPICH RSCP[dBm] = CPICH TX power[dBm] +GainNodeB antenna [dB]
LossNodeB feeder cables [dB] Lpath [dB]
*The calculation is performed for a given resolution, typically at each pixel of the Calculation Areas (see
Step1)

4.3.1.1 How to perform the prediction? [cont.]

W 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)
z CPICH RSCP- (CPICH RSCP)minimum=Reliability Margin
with (CPICH RSCP)minimum =fixed value
zReliability 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
in1.3.3)?
Reliability Margin=10dB Reliability level=95% (=6dB)
Answer:

4.3.1.2 How to interpret the prediction?

z
From the radio network requirements (see 1.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
Planning
Area coverage probability>required value?

if yes, network design is OK
else network design has to be improved
Area

4.3.1.3 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.
What are the input parameters for the CPICH RSCP coverage
prediction?
4.
Shall the calculation radius be greater or smaller than the inter-site

distance?
5.
Make some suggestions to improve the prediction results

4.4 Name of Level 2
y 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

4.4.1.1 Why do we need traffic simulations?

WCan the capacity cope with the demand in UL and in DL?
Traffic Map (see1.2)

Traffic demand modeling
Site map (see 1.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.

4.4.1.1 Why do we need traffic simulations? [cont.]

z
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
NodeB
Cell
Cell
384k
12.2k
Suburban
environment
class
12.2k
384k (in outage)
y Network capacity 1 > Network capacity 2 (for the same traffic map)
z Solution: a traffic simulation can be performed (= a snapshot of

UMTS network at a given time, one possible scenario among infinite
number of scenarii).

4.4.1.2 How to perform a traffic simulation?

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

Propagation model parameterssee 1.3.2
Network design parameterssee 1.4.1

4.4.1.2 How to perform a traffic simulation? [cont.]

z
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
y
a distribution of services among the users
y
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

4.4.1.2 How to perform a traffic simulation? [cont.]

z
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:
y
y
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:
1) needed UE TX power <
Maximum UE TX power
2) UL load factor <
Maximum UL load factor
(typical value: 75%)
3) enough UL NodeB
processing capacity
1)
2)
3)
4)
5)
Conditions in DL:
CPICH Ec/Io > ( CPICH Ec/Io)required
needed NodeB TX power < Maximum
NodeB TX power (ie DL Power load<100%)
(for each traffic channel) needed TX power
< Max TX power per channel
enough DL NodeB processing capacity
needed number of codes < max number of
codes

4.4.1.3 Traffic simulation outputs

z
z
z
z
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:
y
y
not enough CPICH quality: Ec/Io<(Ec/Io)min

not enough TX power for one traffic channel(tch): Ptch > Ptch max
on uplink:
y
not enough TX power for one UE (mob): Pmob > Pmob max
the network is saturated:

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

4.4.1.4 Limitation of traffic simulation

z
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 1.4.4).

4.5 Name of Level 2
4.5.1 Coverage predictions for CPICH Ec/Io and DL/UL
y 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

4.5.1 Coverage Predictions for CPICH Ec/Io and DL/UL services
4.5.1.1 Why do we need coverage predictions?

z
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?
z Problem: traffic simulations can be used, but it is necessary to

average an enormous number of traffic simulations to get the answer
for each service at each pixelunrealistic calculation time
z Solution: Coverage Predictions can be performed

4.5.1.2 Different types of coverage predictions

z
z
CPICH RSCP prediction plot

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

4.5.1.3 How to perform a coverage prediction?

z
Step 1: enter the Coverage Prediction inputs
typical
Comment
value
Coverage Predictions parameters (only used for predictions)
Calculation Radius (per cell)
4 km
same as for CPICH RSCP prediction
Service parameters
The probe UE characterizes the
service/terminal/multipath environment for
Multipath environment
which the Coverage Prediction is performed,
Probe
e.g. PS64/PDA/Vehicular 3km/h
UE
Terminal parameters and
Note: in case of CPICH/Io prediction, no
indoor margin
service parameters are entered.
used to simulate UL/DL interference level
UL load factor(per cell)
50%
Fixed load approach: same values for all cells
Traffic emulation approach: specific values for
DL(power) load factor(per cell)
50%
each cell
-15dB (typically) for CPICH Ec/Io ratio
(ratio value)minimum
(Eb/No)req values for UL/DL (Eb/No) ratios
3dB for CPICH Ec/Io and DL (Eb/No) ratios,
Stand. deviation (per clutter)
clutter map values for UL (Eb/No) ratio (typically 7-8dB)
Orthogonality factor (per
0.6
0.6 for Vehicular A ; 0.94 for Pedestrian A
clutter)
Propagation model parameters + Network design parameters
Traffic simulation inputs

4.5.1.3 How to perform a coverage prediction? [cont.]

z
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

4.5.1.3 How to perform a coverage prediction? [cont.]
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?
UL (Eb/No) value= 4dB (for PS64, Vehicular 50km/h)?
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%
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%

4.5.1.6 How to interpret a coverage prediction?

z
From the radio network requirements, 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

4.6 Name of Level 2
4.6.1 Traffic emulation or fixed load approach?
y Objective:
{
to be able to describe the different approaches which lead to an acceptance test

4.6.1 Traffic emulation approach or fixed load approach?
4.6.1.1 Traffic emulation approach

Traffic map
Traffic simulations
Fixed DL(power)/UL
load factors per cell
Field
traffic
emulation
Predictions
Change
no
Network
Design
Parameter(s)
RNP tool
Field
measurements
in line
with RNP
requirements?
yes
Result2
Result1
Acceptance Test
Result1=Result2?

Field
4.6.1.1 Traffic emulation approach [cont.]

z
Advantages:
accurate (but the accuracy depends on the accuracy of traffic map)
Disadvantages:
complex:
y traffic forecast and traffic map for the coming years must be provided by the
operator
y 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.

4.6.1.2 Fixed load approach
Default DL(power)/UL
load factors values for
each cellFixed
load
Field Fixed load
emulation
Predictions
Change
Network
Design
Parameter(s)
RNP tool
no
Field
measurements
in line
with RNP
requirements?
yes
Result1
Result2
Acceptance Test
Result1=Result2?

Field
4.6.1.2 Fixed load approach [cont.]

z
Advantages:
Disadvantages:
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)
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):
y 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
y downtilting antenna for one cell

{
{
real effect: cell load decrease (because it makes the cell area smaller)
modeled effect: no cell load decrease (due to fixed load)


z
How to emulate DL fixed load in the field?

DL load can be emulated with the
OCNS (Orthogonal Code Noise
Simulator) feature of the AlcatelLucent NodeB:
Common channels
Node
B
OCNS channels
Dedicated channels
y It generates artificial interference in

downlink
y It is used to emulate downlink load
and perform tests with a reduced
number of UEs
Maximum
output power
Typical default value: 50% for DL

(power) load factor
Simulated
traffic
Virtual
mobiles
(due to OCNS)
DL _ load(%) =
OCNS_ TX _ power + TraceUEDL TX power
MaximumDL TX poweravailable
Trace
mobile

Real
traffic

z
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.
Tx
z Workaround:
UL load can be emulated at the MS side by
placing an Attenuator (Att) in the MS transmit path
Tx
Rx
Rx
Att
Typical default value: 50% for UL load factor (ie

3dB Noise Rise, ie 3dB Attenuation)
Tx
Rx
UE

4.6.1.3 A medium approach
Default UL load factor

values for each
cellFixed load
Traffic map
Traffic simulations
Fixed DL(power)/UL
load factors per cell
DL(power) load
factor per cell
Field fixed
load
emulation
Predictions
Change
Network
Design
Parameter(s)
no
Field
measurements
in line
with RNP
requirements?
yes
RNP tool
Result1
Result2
Acceptance Test
Result1=Result2?

Field
4.6.1.3 A medium approach [cont.]

z
Alcatel-Lucent 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:
y accurate (but the accuracy depends on the accuracy of traffic map)
y acceptance test can be realized
Constraints:
y traffic forecast and traffic map for the coming years must be provided by the
operator
y traffic simulations must be performed with RNP tool
y DL: the operator shall agree that the DL field traffic emulation is realized from the
traffic simulation outputs of the RNP tool
y UL: default value for UL load factor must be taken for the whole network (no UL
OCNS feature)

5 Basic Radio Network Parameter

Definition

5 Basic Radio Network Parameter Definition

z
Objective:
Program:
to be able to define the basic radio network parameters

(neighborhood planning and code planning parameters)

1.5.3 HSDPA Concepts and Modelling


y Objective:
{
to be able to describe the criteria and methods used to perform neighborhood

planning.

1.5.1.1 Overview
z
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 re-selection
or handover
The neighbor set may contain:
y
y
y
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.
z
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.
y
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
The neighboring list of a cell coincides with the monitored set of the cell. A cell that is not entered in this cell will not be recognized by
the UE and cause additional DL interference.
For each cell in the UTRAN a set of neighboring cells has to be defined in the radio network configuration database, located in the
RNC.A neighbor cell can be located in the same or in a different frequency, in the same or in a different system.
In idle and in connected mode the UE searches continuously for new cells on the current carrier frequency.
Once the mobile has camped on a cell, it monitors its corresponding neighbors that are communicated to the UE by the RNC in System
information contained in the PCH and PICH.
In dedicated mode, the following neighbor lists need to be defined for each cell incase the corresponding HO has to be supported: the
UE has to be able to monitor these lists
- Intra-frequency monitoring list : min 32 cells on the same UMTS carrier (SHO)
- Inter-frequency neighbor list: min 32 cells on other UMTS carrier (HO)
- Inter-system neighbor lists: for each neighboring PLMN a separate list is needed. A maximum of 32 inter-frequency neighbors must be
supported by the UE
The RAN broadcasts the initial neighbor cell list(s) of a cell in the system information messages on the BCCH. In case an active set
update has been performed, a new neighbor list is combined in the RNC based on the neighbor lists of the cells in the new active set
and then sent to the UE on the DCCH.When in connected mode the Ue continuosly measures the serving and neighboring cells
(indicated by the RNC) on the current carrier. The UE compares the measurement results with the HO thresholds provided by the RNC
and sends a meas. Report to the RNC if the report criteria are fulfilled

5.1.1.1 Criteria and methods

z
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 SA and SB, with
SA[km2]=area where
{
SB
[km2]=area
{
{
(CPICH RSCP)cellA and (CPICH Ec/Io)cellA better than given minimum values
(CPICH Ec/Io)cell A is the best
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
The neighboring list of a cell coincides with the monitored set of the cell. A cell that is not entered in this cell will not be recognized by
the UE and cause additional DL interference.
For each cell in the UTRAN a set of neighboring cells has to be defined in the radio network configuration database, located in the
RNC.A neighbor cell can be located in the same or in a different frequency, in the same or in a different system.
In idle and in connected mode the UE searches continuously for new cells on the current carrier frequency.
Once the mobile has camped on a cell, it monitors its corresponding neighbors that are communicated to the UE by the RNC in System
information contained in the PCH and PICH.
In dedicated mode, the following neighbor lists need to be defined for each cell incase the corresponding HO has to be supported: the
UE has to be able to monitor these lists
- Intra-frequency monitoring list : min 32 cells on the same UMTS carrier (SHO)
- Inter-frequency neighbor list: min 32 cells on other UMTS carrier (HO)
- Inter-system neighbor lists: for each neighboring PLMN a separate list is needed. A maximum of 32 inter-frequency neighbors must be
supported by the UE
The RAN broadcasts the initial neighbor cell list(s) of a cell in the system information messages on the BCCH. In case an active set
update has been performed, a new neighbor list is combined in the RNC based on the neighbor lists of the cells in the new active set
and then sent to the UE on the DCCH.When in connected mode the Ue continuosly measures the serving and neighboring cells
(indicated by the RNC) on the current carrier. The UE compares the measurement results with the HO thresholds provided by the RNC
and sends a meas. Report to the RNC if the report criteria are fulfilled

5.1.1.2 Automatic neighborhood allocation with A9155

z
Step1: enter input parameters
Minimum CPICH RSCP

Minimum CPICH Ec/Io
Typical
value
-105 dBm
-18 dB
Ec/Io margin
8 dB
Reliability level
87%
Minimum covered area
2%
Neighborhood parameters
Maximum inter-site distance

Force co-site cells as
neighbors
Force neighbor symmetry
Max number of neighbors
Comment
parameters used for overlap area

criterion
8 km for dense urban and urban, 10

between 8km
km for sub-urban and around 25 km
and 25km
for rural areas
co-site cells=cells of the same
Yes
NodeB
e.g. if cell A is neighbor of cell B,
Yes
cell B will be neighbor of cell A
14
Criteria linked with a logical AND: Default values are conservative.

1. Minimum pilot signal level:The received pilot signal level is measured at every pixel of the network. If the received
signal level coming from more than one cell is equal or greater than the minimum pilot signal level parameter, these cells
are considered as neighbors.
2. Minimum pilot Ec/Io:The received pilot Ec/Io is measured at every pixel of the network. If the received Ec/Io coming
from more than one cell is equal or greater than the Minimum pilot Ec/Io parameter, these cells are considered as
neighbors.
3. Ec/Io margin:The received pilot Ec/Io is measured at every pixel of the network. If the difference between the received
Ec/Io coming from more than one cell is equal or smaller than the Ec/Io margin parameter, these cells are considered as
neighbors. Ec/Io (A)> Ec/Io(B)+ Ec/Io margin
This margin should be larger than the active set threshold, so that there are more neighbors than active set cells.
4. Coverage probability:The coverage probability and the shadowing standard deviation (that can be entered for each
clutter type in the clutter database) are the required as input for the tool in order to calculate an uplink shadowing margin.
5. Maximum intersite distance: A transmitter "A" will consider transmitter '"B" as neighbor if:The distance between both
transmitters is lower than the maximum intersite distance.
6. %minimum covered area: Minimum % of surface covered by transmitter A where the transmitter B can enter the active
set so that transmitter B can be considered as a neighbor.
7. Max. Note of neighbors: Maximum number of neighbors allocated to each transmitter; of course it must be less than
the total number of transmitters in the project.
8. Force co-site tx as neighbors: Forces the co-site transmitters to be taken into account in the neighbor allocation.
9. Force neighbor Symmetry:Forces the reciprocity of a neighborhood link. This reciprocity is allowed only if the neighbor
list is not completely full.

5.1.1.2 Automatic neighborhood allocation with A9155 [cont.]
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:
y the maximum inter-site distance criterion
y 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.
Criteria linked with a logical AND: Default values are conservative.

1. Minimum pilot signal level:The received pilot signal level is measured at every pixel of the network. If the received
signal level coming from more than one cell is equal or greater than the minimum pilot signal level parameter, these cells
are considered as neighbors.
2. Minimum pilot Ec/Io:The received pilot Ec/Io is measured at every pixel of the network. If the received Ec/Io coming
from more than one cell is equal or greater than the Minimum pilot Ec/Io parameter, these cells are considered as
neighbors.
3. Ec/Io margin:The received pilot Ec/Io is measured at every pixel of the network. If the difference between the received
Ec/Io coming from more than one cell is equal or smaller than the Ec/Io margin parameter, these cells are considered as
neighbors. Ec/Io (A)> Ec/Io(B)+ Ec/Io margin
This margin should be larger than the active set threshold, so that there are more neighbors than active set cells.
4. Coverage probability:The coverage probability and the shadowing standard deviation (that can be entered for each
clutter type in the clutter database) are the required as input for the tool in order to calculate an uplink shadowing margin.
5. Maximum intersite distance: A transmitter "A" will consider transmitter '"B" as neighbor if:The distance between both
transmitters is lower than the maximum intersite distance.
6. %minimum covered area: Minimum % of surface covered by transmitter A where the transmitter B can enter the active
set so that transmitter B can be considered as a neighbor.
7. Max. Note of neighbors: Maximum number of neighbors allocated to each transmitter; of course it must be less than
the total number of transmitters in the project.
8. Force co-site tx as neighbors: Forces the co-site transmitters to be taken into account in the neighbor allocation.
9. Force neighbor Simetry:Forces the reciprocity of a neighborhood link. This reciprocity is allowed only if the neighbor list
is not completely full.

5.2 Name of Level 2

y Objective:
{
to be able to describe the criteria and the methods used to perform the scrambling
code planning

5.2.1.1 Overview
z
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.

5.2.1.2 DL scrambling code planning

z
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)
Note: the 512 primary scrambling codes are distributed among 64 code groups (8 codes per code group)

5.2.1.2 DL scrambling code planning [cont.]

z
Method with a RNP tool:

Note: Neighborhood planning 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

y
y
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 ending with the lowest constrained one.
The cell constraint level depends on its number of neighbors and whether the cell is neighbor of other cells.
Scrambling code group planning for different carriers can be done independently.

5.2.1.3 Definition of UL scrambling code pool for a RNC

z
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.
Note:
In fact, there are two types of scrambling codes:
Long codes:
Length: 38400 chips (Gold codes)

used with Rake Receiver
used in Alcatel Release 2 (R2) and Release 3 (R3)
Short codes:
Length : 256 chips

used with advanced multi-user detector (MUD)
(likely to be used later)

End of Course
End of Module

CEM, iCEM and the Base Band Unit
iCEM128
H-BBU
H-BBU
iCEM128
H-BBU
iCEM (64/128) is HSDPA hardware ready

but needs a specific software
One BBU can not support both
Standard (R99/R4) and HDSPA (R5)services
D-BBU
iCEM64
iCEM64
D-BBU
CEM
D-BBU
D-BBU
iCEM Capacity
H-BBU
12.2/12.2
Speech
PS
32/32
PS
64/64
PS
64/128
PS
64/384
iCEM64
64
32
16
16
iCEM128
128
64
32
32
16
H-BBU
HSDPA dedicated
D-BBU
DCH dedicated
The iCEM boards are composed of Base Band Units (BBUs): iCEM64 contains one BBU, iCEM128 contains two
BBUs.
With the introduction of HSDPA, we do the difference between two types of BBUs:
The D-BBU: it is in charge of the R99/R4 channels processing (the DCHs including SRB and TRB, and
the common control channels: pCPICH, p/sCCPCH, PICH, AICH, pRACH). The D-BBU process also the
DCHs associated to HSDPA users (eg. IB 64 UL- 0 DL + SRB). The D-BBU has a capacity of 64 CEs.
The H-BBU is in charge of the new channels introduced by HSDPA (HS-PDSCH, HS-SCCH and HSDPCCH). The H-BBU has four limitations:
- max cells: 3 HSDPA cells.
- max simultaneous HSDPA users: 20 (UA 4.2) and 64 (UA 5.0).
- max throughput: 10.2Mbps of user traffic (HS-PDSCH) at RLC.
- max OVSF codes: 15 codes in each cell (=max limit of the OVSF tree).
The D-BBU is able to process the traffic of any sector of the BTS (and up to two carriers).
The H-BBU can be either shared between HSDPA cells (up to 3 cells/H-BBU) or dedicated to one cell. When the
H-BBU is shared, its processing is shared among active cells. An active cell is a cell where at least one
HSDPA user received data. If all users of one cell have a HS-DPCCH but do not receive data, the cell is not
considered as active.

iCEM: HSDPA Scalable Configuration
iCEM128
H-BBU
H-BBU
iCEM128
H-BBU
D-BBU
iCEM64
H-BBU
iCEM64
D-BBU
The 4 H-BBU limitations:

3 cells
Simultaneous users:
20 (UA 4.2)
64 (UA 5.0)
User traffic: 10.2 Mbps
OVSF codes:
15 SF 16 (HS-PDSCH)
4 SF 128 (HS-SCCH)
The HSDPA support on UMTS BTS requires second generation of CEM i.e. iCEM64 or iCEM128. Alcatel-Lucent
CEM Alpha is not HSDPA hardware ready.
Nevertheless, HSDPA support on UMTS BTS is possible assuming already installed CEM Alpha modules. CEM
Alpha and iCEM modules can coexist within the Digital shelf while providing HSDPA service with UMTS BTS.
Base Band processing is performed by BBUs of CEM and iCEM. One restriction of current BBUs is that one BBU
cannot process both Dedicated and HSDPA services.
The partition between H-BBU and D-BBU is done by the BTS at BTS startup, using OMC-B configuration
information.
Once this allocation is done, it can only change after a BTS-iCCM reset or an iCEM plug-in or plug-out.

HSDPA Solution
CEM 128
H-BBU
Cell#1
GPSAM
TRM 1
H-BBU
Cell#2
f1 RX
(M+D)
CEM 128
H-BBU
Cell#3
f1, f2
TX driver
HSDPA
Cell #1,
f1
Standard
Cell #4,
f2
HSDPA
Cell #2,
f1
Standard
Cell #5,
f2
HSDPA
Cell #3,
f1
Standard
Cell #6,
f2
PA
f1 f2 TX
, ,
f1 f2 RX Div.
f1 f2 RX Main
PA
TRM 2
f1 f2 TX
f1, f2
TX driver
CEM alpha
D-BBU
Cell#5
f1 f2 RX Main
CCM
D-BBU
Cell#4
D-BBU
Cell#6
f1 RX
, ,
(M+D)
f2 RX
(M+D)
, ,
f1 f2 RX Div.
f1 f2 RX Main
f2 RX
, ,
(M+D)
PA
f1 f2 RX Div.
Network
Interface
HSDPA is supported on STSR-1, STSR-2 and STSR 1+1, but can be deployed on one frequency only.
Introduction of HSDPA is simpler by dedicating a new additional carrier for HSDPA and leaving current carrier for
standard (R99) services with its related existing engineering dimensioning.

Appendix
Radio Network Planning Fundamentals UTRAN UA5

Blank Page

Objectives
By the end of the course, participants will be able to:

-Describe briefly the structure of an RNP tool and the steps of an RNP process;
-Describe the UMTS RNP inputs in regards of frequency spectrum, traffic parameters, equipment parameters and RNP
requirements;
-Calculate the cell range for a given service by doing a manual link budget in Uplink;Have the theoretical
background to create an initial network design using an RNP tool (the RNP tool is only used by the trainer for
demonstration);
-Define basic radio network parameters (neighborhood and code planning);
-Discuss briefly optimization possibilities in terms of capacity and coverage;
-Describe briefly the interference mechanisms due to UMTS/GSM co-location and the solutions for antenna systems.

Objectives [cont.]

Table of Contents
z
Page
1 Basic Radio Network Optimization

1.1 Coverage and capacity improvement features
1.1.1 TMA - Tower Mounted Amplifier
1.1.2 TX diversity
1.1.3 TX diversity
1.1.4 High Power Amplifier
1.1.5 6-sector site
1.1.6 6-sector site
1.1.7 6-sector site (2bis)
1.1.8 Adding a carrier
1.1.9 Capacity RNC
1.1.10 Open Iur
1.1.11 Handover Procedure: Cell Change Order (CCO)
1.1.12 AMR mode
1.1.13 AMR mode selection based on load: Principle
1.1.14 AMR mode selection based on load: Algorithm
1.1.15 Antenna Remote Control
1.1.16 Overview
1.1.17 Step 1: define Measurement Areas
1.1.18 Step 2: define Measurement Test Cases
1.1.19 Step 3 to 5
2 HSXPA
2.1
HSDPA
@@SECTION
@@MODULE 5
@@SECTIONTITLE
@@MODULETITLE
2.1.1 HSDPA
CONCEPTS
2.1.2 HSDPA MODELLING
2.1.3 HSDPA Terminals UE Categories
2.2 HSUPA
2.2.1 HSUPA concepts
2.2.2 HSUPA new channels
2.2.3 HSUPA concepts: UA05 UE Capabilities
2.2.4 HSUPA terminal properties
2.2.5 HSUPA service properties
2.2.6 HSUPA bearer properties
2.2.7 HSUPA User Equipment categories
2.2.8 Process of HSUPA users
2.2.9 Admission control
2.2.10 Noise rise scheduling
2.3 UMTS, HSDPA AND HSUPA PREDICTIONS
2.3.1 AVAILABLE PREDICTIONS
2.3.2 UMTS PREDICTION
2.3.2.1 UMTS PREDICTION
2.3.3 HSDPA PREDICTIONS
2.3.4 HSUPA PREDICTIONS
3 UMTS/GSM co-location and Antenna Systems
3.1 Contents
3.1.1 The interference mechanisms
3.1.1.1 Transmitter Noise / Spurious Emissions
3.1.1.2 Receiver blocking
3.1.1.3 Intermodulation Products
3.1.1.4 Intermodulation Products : conclusion
3.1.1.5 Summary on the required Decoupling
3.1.1.6 UMTS - UMTS co-location (FDD)
3.1.1.7 Co-location: Conclusion
3.1.2 Antenna Solutions

7
8
9
20
26
27
32
33
34
35
43
44
46
47
48
49
50
52
53
54
55
56
57
58
61
62
63
71
72
73
74
75
77
78
79
80
81
82
85
86
98
99
100
109
117
118
119
120
126
134
138
139
140
141
142
Table of Contents [cont.]

z
Page
3.1.2.1 Dual-band Sites GSM 1800 - UMTS FDD

3.1.2.2 Separation for air-decoupling
3.1.2.3 Decoupling measurements
3.1.2.5 Solutions with RFS Celwave components
3.1.2.7 Solutions with RFS components
3.1.2.8 Triple-band sites for GSM 900/1800 and UMTS
3.1.2.9 Multi-operator sites: UMTS FDD-UMTS FDD
3.1.2.10 Antenna Feeder Sharing for Dual-band Sites
3.1.2.11 Antenna Feeder Sharing for Triple-band Sites
3.1.2.12 Feeder sharing losses
3.1.2.13 Antenna feeder sharing: conclusion
3.1.2.14 TMA in co-location configurations
3.1.2.16 TMA in feeder sharing solutions
3.1.2.17 Antenna Systems: Conclusion
4 Cell parameters (Network Design Parameters - cell wise)
4.1 Open loop power control
4.2 Closed loop power control
4.3 Frequency coordination at country borders
4.4 Cost 231-Hata formula
4.5
Network
architecture
dimensioning
parameters
All Rights
Reserved Alcatel-Lucent @@YEAR
@@SECTION
@@MODULE
6
@@SECTIONTITLE
@@MODULETITLE
4.6
Transmit
power parameters
4.7 Handover parameters
4.8 Cell selection/reselection parameters
5 Solutions of the exercises
5.2 UMTS propagation model
5.3 Cell Range Calculation
5.4 CPICH RSCP coverage prediction

143
144
145
146
149
150
152
153
155
158
159
160
162
163
165
166
167
168
169
170
171
176
177
179
181
182
183
184
186
188
193

WObjective:
z
to be able to describe the Alcatel-Lucent R3/R4 UTRAN features in terms of

coverage/capacity improvements in UL/DL
- Coverage and capacity improvement features

- Design optimization based on drive measurements

1.1.1 TMA - Tower Mounted Amplifier

z
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
Additional downlink loss (~0.5 dB)

Feeder
Tx / Rx
BTS /
Node B
1.1.1 TMA - Tower Mounted Amplifier [cont.]

z
For RX antenna diversity

operation, the configuration has
to be doubled
One TMA for each antenna needed
Dual TMA
Alcatel-Lucent TMA is a dual

TMA
Antenna
Duplexer
Duplexer
TMA
Tx
Rx
Duplexer
Feeder
Tx / Rx
TMA
Tx
Rx
Duplexer
Feeder
Tx / Rx
Node B
[1]
Within the TMA, the diplexers separate and recombine the signals on the RX and the Tx paths. They also
provide sufficient out-of-band filtering and isolation between the two paths. Only the Rx signals get
amplified, thus, improving the quality of the uplink branch.
The DC supply of the TMA is done via the RF feeder cable from the Bias-T included in the node Bs antenna
unit ANXU.


z
Network Design and Planning

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


z
Calculation of the resulting NF with Friies-Formula

ncable 1
nBS 1
nDX 1
+
+
gTMA
gTMA gcable gTMA gcable gDX
ntot ,TMA = nTMA +

NFelement
10
with nelement = 10
4.3 dB gain on
total NF in this
example due
to TMA
Gelement
10
and gelement = 10
ntot ,noTMA = ncable +
DX means Diplexer or Filter
n 1
nDX 1
+ BS
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
[1]
In the UL dimensioning, the impact of TMA cannot be treated by adding a simple TMA gain within the power
budget.
Since the TMA reduces the total noise figure on the reception chain the total noise figure of the RX chain has
to be applied in the calculations. The Rx chain contains as elements the TMA, the Node B, cables and
connectors and perhaps diplexers or filters.
The overall noise figure of the reception chain is calculated with the Friies Formula. For this example the link
budget is improved by 4.3 dB
In the DL link budget, the TMA will add a DL insertion loss of 0.5 dB.


z
18
Total Interference I (dB)
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
Typical reduction of the

required number of sites:
~40%
for low traffic scenario
~30%
for high traffic scenario
4
2
0
0
0.2
0.4
0.6
0.8
Cell Range R (km)
[1]
The coverage gain is defined as the percentage gain on the number of sites required when the TMA is used compared to the number of sites without TMA.
The gain on cell range is fully available in case of UL limitation. If the system is DL limited, a TMA will show no effect on the cell range.
Moreover, the gain in the UL LB has to be mapped onto a gain on cell range, in UMTS there is the coverage-capacity trade off to be considered.
The coverage gain is highly depending on the traffic and the radius.
FIGURE EXPLANATION: it shows the effect of traffic density on the coverage gain brought by TMA.
The link budget curves show (in yellow and red) the influence of total interference on the cell radius for the most limiting service (PS 128 for this example)
without TMA and with TMA respectively.
The curves I(R) for low traffic (green) and I(R) for high traffic (blue) show the effect of cell radius on interference taking into account 2 traffic scenarios:
one with a low subscriber density for each service and one with high subscriber density.
The intersection of the link budget curves with the traffic curve gives the according cell range. One can see directly that the gain in cell range
through adding a TMA is smaller in case of higher traffic.


Dense Urban
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 %
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
High Traffic Scenario

without TMA
with TMA
0,481
0,318
18%
53%
0,451
0,197
2217
39%
Urban
0,665
20%
0,863

without TMA
with TMA
0,448
50%
0,392
1159
40%
Suburban
1,659
21%
5,367
310
5071
2552

without TMA
with TMA
1,126
49%
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%
[1]
The tables provide results on a coverage gain study performed with a mix of 2 services for different
environments.
The typical coverage gain (reduction of the number of sites required to cover a given area) achieved thanks
to a TMA is between 30% and 40%.


z
14
Interference level
12
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
10
8
max. allowed
6 interference level
increase of interference only

up to max. allowed level
0
0
0.2
0.4
0.6
0.8
Cell Load
Capacity gain A
high gain for low traffic (A)

negligible gain for high
traffic (B)
Capacity gain B
Example: TMA allows x dB higher Interference level

Case A: starting from low interference scenario
Case B: starting from high interference level scenario
Less gain due to max. load threshold

Less gain due to steep rise in function


z
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%
Max UL load of 75%

used in simulation
9,7%
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
[1]
Calculated for 4.3 dB of gain in LB and 75% max. allowed load
Calculated for fixed cell radius
Capacity gain is independent of service or morpho-structure
Attention: If uplink capacity is not the limiting factor but downlink capacity is critical, an increase in uplink capacity will not solve the problem


Higher bit rate services
z
z
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
Introduction
of 384kbps
384 kbps
coverage
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
128 kbps
coverage
Simultaneous introduction of
TMA and new service helps
keeping coverage range
[1]
Tma is mainly known as a coverage enhancement feature.
It can however be used to address other issues. Indeed it can compensate for loss of sensitivity due to
introduction of higher bit rate services later in the NW roll out. For example difference in sensitivity between
PS 144 and PS 384 services is around 4dB.


z
Blocking aspects
In-Band-Blocking
y Potential Problem: Excess gain of TMA
{
Blocking performance decreases be the amount of

excess gain=amplifier gain feeder cable loss
y Solution: Amplification reduction in node B to

z
Out-of-Band-Blocking and Co-Siting with GSM

y RX ANT filter attenuates all out of band signals
y


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

1.1.2 TX diversity
z
Basics
The transmit antenna diversity techniques consist in using several transmit
antennas, broadcasting de-correlated complementary signals
2 modes :
y Open loop (first phase : already available)
{
TSTD - Time Switch Transmit Diversity

(Synchronization channel only)
STTD - Space-Time transmit diversity
(Other physical channels)
y Closed loop (second phase) : higher diversity gain
The transmit antenna diversity technique consists in using at the transmitter several antennas, broadcasting
complementary signals. The aim of transmit diversity is to alleviate fast fading and therefore to increase the
capacity of the DL transmission. Several tx div techniques have been standarised in the FDD mode of UMTS
for 2 tx antennas.
OPEN LOOP tx div: No feedback information is sent from the UE to the Node B.
- TSTD consists in transmitting the signal alternatively on each antenna every slot. This technique is only used
for DL synchronization channels and therefore has few impact on the capacity of the cell. It is implemented in
the Alcatel-Lucent Node B from day one.
- STTD is a coding in time and space that enables the receiver to demodulate the data without additional
complexity compared without the non-diversity case. This technique can be used for all the DL channels
except for the S-SCH and P-SCH for which the TSTD is used instead. STTD is therefore the diversity technique
applied on the traffic channels. STTD is implemented in the Node B from day one.
The open loop techniques are statistical and rely on a non-coherent combining in the receiver. Therefore,
they do not enable to have a 3dB coherence gain like the receive antenna diversity and their performance
gain is only due to their ability to fight against fading.

1.1.2 TX diversity [cont.]

z
STTD= Space-Time transmit diversity

Signal is shifted in space and in time to obtain the second
signal
b0 b1 b2 b3
Antenna 1
b0 b1 b2 b3
-b2 b3 b0 -b1 Antenna 2
Channel bits
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
CLOSED LOOP rx div: the signals tx by the 2 antennas are weighted. The UE sends periodically weight
information to the Node B, which will adjust the amplitudes and the phases of the 2 tx antennas according to
this feedback.
This way coherent combining is performed in the RX, enabling (theoretically) to have up to 3 dB performance
gain as with receive ant div.
In the practise coherent combining cannot be perfect and less than 3 dB gain are achieved.
This coherent gain of feedback mode transmit diversity makes it possible to have even larger gain than with
open loop techniques.
However, feedback mode tx div degrades more rapidly as the speed increases because of the feedback loop
delay. Thus open loop and closed loop techniques are complementary.


z
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 Rx Eb/N0 (dB)
0.8 dB
Without Tx diversity
STTD
10
25
Speed (km/h)
50

120

z
STTD-Gain on DL Capacity
Pure Diversity Gain:
y Independent of cell range
y Service dependent
y 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:

y Highly dependent on cell range


WSTTD-Gain on DL Capacity - Example
Monoservice NRT 128kbit/s, Urban,
NRT 128 kbps/ URBAN
Vehicular A
Capacity gain by doubling the maximal downlink

transmit power (%)
20,0%
18,0%
16,0%
Pure Diversity gain in

capacity: ~8%
Gain through 2nd PA:
dependent on cell range
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
0,8
0,9
Cell range (km)
8%+3%=11% total gain


z
STTD-Gain on DL Capacity
Typical Values Typical Values in Vehicular A environment
Capacity gain through

diversity
Capacity gain through 2 nd PA
Dense Urban
Urban/Suburban
Rural
~8%
~10%
~12%
~0%-2%
~1%-8%
~2%-11%
~8%
~15%
~20%
(for typical cell ranges)

Typical Total Capacity Gain
Typical Value in Pedestrian A environment (microcell)

y
y
Pure Diversity gain: ~20%

Gain through 2nd PA: negligible

1.1.3 TX diversity
z
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.
y 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.

1.1.4 High Power Amplifier

WBasics
45
Impact of Node B power rise on capacity

40
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
10
0
100
200
300
400
500
600
700
800
900
Throughput NRT 128 (kbps)

high impact in
rural
negligible
impact in
urban
1.1.4 High Power Amplifier [cont.]

z
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


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



z
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%
1 carrier
2 carriers
3 carriers
Urban
550m
2%
6%
9%
Max power per carrier
Output Powers
(Node-B v2)
24 Watts
10 Watts per carrier
5.3 Watts per carrier
Suburban
1700m
4%
11%
17%
Output Powers
(theoretical extended Node-B)
40 Watts

Rural
7km
8%
20%
31%

z
Conclusion
To increase the power per carrier is only interesting in environments, where
the MAPL allowed is high:
y In suburban and rural environments
y Where Low data rate services are offered in UL
y Where coverage enhancement features are used in UL such as TMA and 4RxDiv

1.1.5 6-sector site

z
Coverage Gain
Results of simulation done with RNP tool A9155V6

y
y
y
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
3-sector
6-sector
20
20
65
32
5
5
18
21
1525
1950
2.0
3.3
64%
39%
22%
SUBURBAN
3-sector
6-sector
25
25
65
32
3
3
18
21
4300
4500
16.0
17.5
10%
9%
83%
RURAL
3-sector
6-sector
30
30
65
32
1
1
18
21
13350
15000
154.3
194.9
26%
21%
58%
From study of Michael Mair.

Traffic scenario:For the coverage evaluation three traffic scenarios are created. In the first scenario the
whole area is defined as urban, the second scenario consists of a single suburban area, the third one is
defined as rural.
Coverage evaluation procedure:For this evaluation the matching inter-site distance which leads to a
rejection rate of approximately 5 % has to be found. For the calculation of the rejection rates an average of
10 simulations is taken and only mobiles which are best served by one of the transmitters of the inner 18
sites are considered. Also all mobiles with connection status Ec/Io < (Ec/Io)min (which therefore have no
best server) are not considered if they are positioned out of an inner rectangle which represents the service
area of the inner sites.
The results of the coverage evaluation are taken out of 10 simulations.
It is interesting that 6 sector sites lead to a coverage gain of more than 60 % in urban areas and of more
than 25 % in rural areas while the gain in suburban areas can be described as not mentionable.

1.1.6 6-sector site

z
Capacity Gain with Node B 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 Node B 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
See document of Michael Mair

For the capacity evaluation of Node B V1 the number of channel elements is set to 240 per site with a bit
rate of 16 kbit/s for all simulations. In fact this is the maximum number of channel elements for a 3 sector
site with Node B V1, for a 6 sector site 3 additional baseband boards are needed for signaling, so that only
192 channel elements can be used for traffic. The maximum output power is defined to be 43 dBm which is
a simplification because in reality the output power decreases when using more than one carrier.

1.1.7 6-sector site (2bis)

z
Capacity gain
for different configurations compared to 3x1 and 3x2 configurations
(dense urban, 500m inter-site distance)
Higher inter-sector
interference for 6 sector site
because less frequencies used
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
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
For the following simulations the number of channel elements is set to 768 with a bit rate of 24 kbit/s. This value is the same for 3 and 6 sector sites, because Node B V2 does not use
baseband boards for signaling like V1 does. The maximum output power for the different configurations is defined as shown in Table 13. This values correspond to the usage of two
power amplifiers per sector which is needed to realize Tx diversity.
It is interesting to see that a configuration with 3 sector sites and 3 carrier frequencies has less capacity than 3 sector sites with 2 carriers. Main reason is the lower output power when
using 3 carriers, so that the transmitters run into Tx power saturation. A second surprising effect is the difference of the possible capacity gain achieved with 6 sector sites. While 6
sector sites with 1 carrier lead only to a 39.3% higher capacity than 3 sector sites with 1 carrier, the capacity gain increases to 57.9% when using 2 carriers for both 3 and 6 sector
sites. This could be the consequence of the higher overlapping interferences of 6 sector sites and the high maximum output power of 1 carrier configurations. The interferences are so
high that mobiles located in the overlapping areas do not receive a carrier signal. Therefore Ec/Io < (Ec/Io)min is the main rejection reason when using 6 sector sites with 1 carrier
frequency (Table 15). 3 sector configurations are less affected from this problem because of the lower number of receivable transmitters in the overlapping areas. As consequence of
the decreasing maximum output power this effect also widely disappears when using 2 carriers, so that Tx power saturation is the major rejection reason.
As shown in Table six sector sites seem only to cause a mentionable capacity gain if combined with the usage of 2 carrier frequencies. So there are 3 configurations which can be
recommended to run with Node B V2:
- 3 sector sites, 1 carrier
(for low capacity networks or rural areas)
- 3 sector sites, 2 carriers
(for medium capacity networks or urban/suburban areas)
- 6 sector sites, 2 carriers
(for high capacity networks or business/dense urban areas)

1.1.8 Adding a carrier

z
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

1.1.8 Adding a carrier [cont.]
Basics for Uplink

Uplink Coverage:
18
Link Budget curve

traffic curve
depends on # of
carriers
Uplink Capacity:
doubling # of
Total Interference I (dB)
stays the same,
16
12
10
8
6
4
carriers:
~doubled uplink
capacity
link budget curve

I(Traffic),1 carrier
I(Traffic), 2 Carriers
14
0.1
0.2
0.3
0.4
0.5
Cell Range R (km)


0.6
0.7

WUL 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%
Adding a carrier means:
Power Amplifier
Carrier
TX
reducing power per carrier

(20W 2x10W)
z
Antenna 1
C1
PA
C2
10 W per carrier
TEU
Downlink Coverage:
Antenna
Gain is dependent on traffic density and cell range
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


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



z
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
-20,0%
Cell range (km)

15

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

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%
1.1.9 Capacity RNC
Cells
Node B
9370 RNC UA05)
200
Speech
1200
Transport Node
3900
Iub
ATM
Backbone
BTS
BTS
Iu/Iur/O&M
Iub

1.1.10 Open Iur

z
Principle: The Iur is compliant with 3GPP specifications. It can be linked

to an RNC from another manufacturer. It is used in case of inter-RNC soft
handover.
Interest: To perform a soft handover anywhere in the network and so, to
improve the quality for the user.
Iu
From Alcatel-Lucent
From Alcatel
Iu
Core
Network
SRNC
RNC
Iub
Node B 1
Node B 2
From another
manufacturer
Iub
Hard Handover!
Short cut
during the call
Node B 3
Node B 4
Without
Open Iur
An Open Iur can link an RNC from Alcatel-Lucent and an RNC from another manufacturer. It is useful in
case of soft handover when cells dont belong to the same RNC.
Without Open Iur, it is not possible to interconnect both RNCs. The only solution is to perform a hard
handover, but the perceived quality may be degraded when the user crosses the boundary.

1.1.10 Open Iur [cont.]

z
z
Principle: The Iur is compliant with 3GPP specifications. It can be linked to an

RNC from another manufacturer. It is used in case of inter-RNC soft handover.
Interest: To perform a soft handover anywhere in the network and so, to
improve the quality for the user.
Iur
Iu
Iu
From Alcatel-Lucent
From Alcatel
Core
Network
SRNC
RNC
DRNC
Iub
Node B 1
Node B 2
From another
manufacturer
Iub
Soft Handover!
No cut
during the call
Node B 3
Node B 4
With
Open Iur
With Open Iur, it is possible to interconnect both RNCs. So, in case of soft handover, there is no degradation
of the quality.

1.1.11 Handover Procedure: Cell Change Order (CCO)

z
Change of Cell from 3G to 2G during a Packet Call:

UTRAN can trigger 3G>2G mobility before the radio conditions become
drastically deteriorated.
The CCO provides shorter interruption time than the Cell Update process.
Bad radio
conditions
Transport
Node
GPRS
RNC
MBS
CCO
The Cell Change Order, or CCO, allows to request the UE to trigger a cell reselection towards the GPRS. It
can be used if the user has only one PS RAB and if the UE supports both UMTS and GPRS.
With a Cell Change Order (CCO) message, the UTRAN itself can trigger the cell reselection towards the
GPRS.
When a UE detects bad radio conditions, it informs the RNC it is attached to which launches the compressed
mode. This mode allows the UE to make measurements on GPRS cells. When a suitable cell is found, the
RNC triggers the Cell Change Order and the UE is instructed to reselect this GPRS cell.

1.1.12 AMR mode

z
z
Principle: The voice can be transmitted at different rates according to

the context, e.g the load.
Interest: To increase the capacity.
Voice sample
101
01
100
Class
A
Class
B
Class
C
QoS 1
QoS 2
QoS 3
Thanks to this principle, 8 rates are available:

4.75 Kbit/s
5.15 Kbit/s
5.90 Kbit/s
6.70 Kbit/s
7.40 Kbit/s
7.95 Kbit/s
10.20 Kbit/s
12.20 Kbit/s
Thanks to this feature, the voice can be transmitted at different rates. The interest is, in case of high traffic, to
transmit the data at a lower rate and so to increase the capacity.
The Adaptative Multi Rate (AMR) is a speech codec. It supplies 3 classes of bits which are sorted according to
their sensitivity to errors: class A (the most sensitive), class B and class C. According to their class, bits are
sent with different QoSs. Thanks to this principle, the AMR codec offers 8 AMR modes between 4.75 Kbit/s
and 12.2 Kbit/s.

1.1.13 AMR mode selection based on load: Principle

z
z
In the R3, only one rate is available, usually 12.20 Kbit/s.

In the R4, the RNC can choose between two rates:
y 12.20 Kbit/s,
y One specific rate defined in the Office Data (OD).
Quality
of reception:
low
CSCN/
PSCN
RNC
MBS
Rate selection:
7.40 Kbit/s
for example
RAB establishment
In the R3, only one rate is available, usually 12.2 Kbit/s.

In the R4, the RNC can choose between 2 rates :
12.2 Kbit/s which is the better rate.
Another specific rate defined in the Office Data (OD).
The selection is performed from the measurement report coming from the UE. The measured quantity is the
quality of reception of the CPICH. If this value exceeds a given threshold, the RNC selects the better rate,
12.2 Kbit/s. If not, the RNC selects the other rate.
Using lower rate allows to use less power in transmission and so, to save radio resources. That is why this
feature increases the capacity.

1.1.14 AMR mode selection based on load: Algorithm

z
Algorithm:
CPICH_Ec/No
measurement
provided by the UE
RRC connection request
CPICH_Ec/No
>= Threshold?
No
Yes
AMR mode:
AMR mode:
Alternative rate
12.2 Kbps
When the call is established, Ue will report the measured CPICH Ec/No by the RRC CONNECTION
REQUEST message with the IE Measured results on RACH
RNC compares the reported CPICH Ec/No with CPICH Ec/No threshold for AMR mode selection defined in
office data. If it is equal or above the threshold, the AMR 12kbps is selected, otherwise the alternative rate is
used.

1.1.15 Antenna Remote Control

z
Principle: The tilt (vertical orientation) of the antenna can be controlled from
the OMC-R or the Local Maintenance Tool (LMT).
OMC
Server
LAN
Motor unit
Tilt control
from remote OMC-R
client stations
Itf-B/E1
Itf-B
STM1
Transport
Node
Control
unit
ATM
Backbone
Radio Network
Planning tool
provides the tilt value
RNC
MBS
Tilt control
from LMT
This feature allows to control the tilt of each antenna locally from the Local Maintenance Tool, or LMT, and
remotely from the OMC-R. It is called the Remote Electrical Tilt or RET.
Due to error at initial deployment, dynamic behavior for hot spot or optimization, modifications of the tilt
may be frequent. And without the RET, the operator has to perform an on-site adjustment of the down tilt. So
it allows time and cost savings.
The RET system is composed of a Control Unit capable of controlling several motor units. The Control Unit is
linked to the MBS by an RS232 and can be installed inside the cabinet for the outdoor MBS.
Locally, the tilt can be adjusted from the LMT via a dedicated application.
Remotely, the tilt can be adjusted from OMC-R client stations via the same application.
The Radio Network Planning, usually called RNP, provides the tilt value.

1.1.15 Antenna Remote Control [cont.]

z
Interest: Due to a complex relationship in WCDMA between capacity, coverage

and interference, frequent down tilt modifications are expected. So it allows to
avoid on-site tilt modification.
Due to complex relationship in W-CDMA between capacity, coverage and interference, frequent down tilt
modifications are expected
Partial compensation of cell breathing
Inaccuracies or errors at initial aerial deployment
Footprint can be adjusted by combining down tilt and power

Without RET, the operator will have to perform site visits for the adjustment of down tilt
Expensive in terms of OPEX
May require node B to be taken out of service for some sites (revenue loss)
Only feasible if few adjustments needed
In addition to situations where adjusting the antenna tilt is necessary on a long term basis [static], some
situations may require short term optimization [dynamic]
Rush hours: the network can concentrate on train stations or airports.
Special events: music festivals, exhibitions, major sporting events

1.1.16 Overview
Step 1
Define Measurement Areas
Step 2
Define Measurement Test Cases
Step 3
Perform Measurements
Step 4
Analyze results and modify design
Step 5
Re-launch predictions

1.1.17 Step 1: define Measurement Areas

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

1.1.18 Step 2: define Measurement Test Cases

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

1.1.19 Step 3 to 5
z
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 1.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)

2 HSXPA

2 HSXPA
2.1 HSDPA
z
HSDPA (High Speed Downlink Packet Access) IS A 3GPP RELEASE 5

FEATURE FOR UMTS
Designed for data service applications
Aimed at provide, for the downlink, significant reduced delays and peak rates
up to 8-10 Mbps
Fully Release 99 backward compatible
Can co-exist on the same RF carrier with R99 UMTS traffic

2.1 HSDPA
2.1.1 HSDPA CONCEPTS
TECHNICAL ASPECTS
New physical channels (modelled in A9155)

Fast link adaptation (modelled in A9155)
Fast retransmission mechanism
Fast scheduling at Node B

2.1 HSDPA
2.1.1 HSDPA CONCEPTS [cont.]

z
NEW PHYSICAL AND TRANSPORT CHANNELS ON THE DOWNLINK

HS-DSCH (High Speed Downlink Shared Channel)
y HS-PDSCH (High Speed Physical Downlink Shared Channel): Associated physical
channel
y Carries user data
y Both time and codes shared between users
y Within each 2 ms transmission time interval (TTI), a constant spreading factor of 16
is used with a maximum of 15 parallel codes
{
2 to 4 users can share the code resources with the same TTI
y Always associated to a R99 DCH (Dedicated Channel)
HS-SCCH (High Speed Shared Control Channel)

y Carries information to decode HS-DSCH (Modulation, Transport block size,)
y Spreading factor = 128

2.1 HSDPA
2.1.1 HSDPA CONCEPTS [cont.]

z
NEW PHYSICAL CHANNEL ON THE UPLINK

HS-DPCCH (High Speed Dedicated Physical Control Channel)
y Indicates the Channel Quality Indicator (CQI) used for fast link adaptation
y Carries the acknowledgement signal for retransmission process
y Spreading factor = 256
FAST LINK ADAPTATION INSTEAD OF POWER CONTROL

The HS-DSCH is transmitted at constant power over a TTI
Adaptive DL data rate by changing:
y The modulation scheme
y The coding
y The number of codes
Based on:
y The reported CQI
y UE category
z
NO SOFT HANDOVER ON DL
The mobile has only one link from its best-server

2.1 HSDPA

z
CELLS
Cell HSDPA capabilities
y Power available for HSDPA (i.e for HS-PDSCH and HS-SCCH)
{
Cell HSDPA power must be estimated and fixed => this is a fixed part of
the cell total power used
y Maximum number of OVSF codes available for HS-PDSCH channels


2.1 HSDPA
2.1.3 HSDPA Terminals UE Categories

z
HSDPA will require new terminals to support:
a new protocol stack

new modulation & coding
12 categories have been defined by 3GPP
New categories introduced

for first terminals (QPSK only)
Max bit rate: 1.8 Mbps
HS-DSCH
category
Maximum number of HSDSCH codes received
L1 peak rates
[Mbps]
Modulation
QPSK/16-QAM
Category 1
Category 2
Category 3
Category 4
Category 5
Category 6
Category 7
Category 8
Category 9
Category 10
Category 11
Category 12
5
5
5
5
5
5
10
10
15
15
5
5
1.2
1.2
1.8
1.8
3.6
3.6
7.3
7.3
10.2
14
0.9
1.8
Both
Both
Both
Both
Both
Both
Both
Both
Both
Both
QPSK only
QPSK only

2.1 HSDPA

z
USER EQUIPMENT (UE) CATEGORY

User equipment capabilities defined in 3GPP specifications
Table available from the Terminals context menu
Each HSDPA terminal is assigned to a UE category

2.1 HSDPA
2.1.4 HSDPA MODELLING [cont.]

z
TERMINALS PROPERTIES
HSDPA supported or not

UE category
MUD factor taken into account to
calculate the DL interference

2.1 HSDPA

z
SERVICES PROPERTIES
HSDPA supported or not
Parameters used to calculate the DL
application throughput: scaling
scaling factor
between the application throughput
and the RLC (Radio Link Control)
throughput and throughput offset
MOBILITY TYPE PROPERTIES
Minimum quality required on the HSHSSCCH channel in order for the HSDPA
link to be available

2.1 HSDPA

z
HSDPA RADIO BEARER

Transport Format Resource Combination (TFRC) selected by
the scheduler during fast link adaptation
y
y
y
y
Transport block size

Number of HS-PDSCH channels used
Modulation supported (16QAM or 8PSK)
Peak rate
Table available from the Services context menu

2.1 HSDPA

z
IN MONTE CARLO SIMULATION

A9155 takes into account the HSDPA power in the total downlink
used power
y This models the influence of HSDPA traffic on the simulation results for
R99 traffic Do not consider HSDPA traffic in traffic maps
IN A DEDICATED HSDPA STUDY

Possibility to display on each pixel
y
y
y
y
The
The
The
The
reported CPICH/HS-PDSCH Channel Quality Indicator (CQI)

HS-PDSCH Ec/Nt
peak rate
application throughput
Fast link adaptation modelling

CPICH/HSCPICH/HS-PDSCH
Ec/Nt evaluation
CQI
calculation
HSDPA
bearer
selection
Peak
rate
calculation

Application
throughput
calculation
2.1 HSDPA

z
FAST LINK ADAPTATION MODELLING IN THE DEDICATED

HSDPA STUDY
1st step HS-PDSCH CQI determination
1. A9155 determines either the
CPICH EcNt or the HSHS-PDSCH Ec/Nt
2. Knowing the CPICH/HSCPICH/HS-PDSCH

Ec/Nt,
A9155
deduces
the
corresponding CQI from the graph.
This graph is defined for the terminal
reception equipmentequipment-mobility type pair

2.1 HSDPA

z

HSDPA STUDY
2nd step: HSDPA bearer selection
y Best bearer selection
Knowing the HSHS-PDSCH CQI, A9155
finds the best bearer from the graph.
reception equipmentequipment-mobility type pair
y A9155 checks if best bearer characteristics are compliant

with cell and terminal user equipment capabilities
{
{
If they are compliant: A9155 keeps the best bearer

Otherwise, it chooses a suitable bearer
3rd step: Peak rate calculation

y Once the bearer selected, A9155 reads in the HSDPA Bearer
table the peak rate supported

2.1 HSDPA

z

HSDPA STUDY
4th step: Application throughput calculation
y BLER Determination
Knowing the HSHS-PDSCH Ec/Nt, A9155

finds the BLER from the graph.
reception equipmentequipment-bearerbearer-mobility type
triplet
y A9155 evaluates the application throughput: net throughput after

deduction of coding (redundancy, overhead, addressing,...)
Applicatio n_throughp ut =
peak_rate ( 1 BLER) scaling_fa ctor throughput _offset

min _nb_TTI

2 HSXPA
2.2 HSUPA
The main characteristics of HSUPA are:
z E-DCH, an enhanced Dedicated channel
z Fast scheduling at Node B level
z (TTI: 10ms => mandatory), 2ms =>optional)
z Fast retransmission of data
z QPSK modulation (~2 BPSK)
z Uplink Noise Rise management in nodeB
z Uplink resource management in nodeB.

2.2 HSUPA
2.2.1 HSUPA concepts

z
z
z
z
z
z
z
z
Rule: HSUPA-HSDPA interaction

HSUPA works only together with HSDPA in DL.
Restriction: HSUPA TTI in UA5.0
In UA5.0, only TTI 10 ms is supported
Restriction: HSUPA Macro-Diversity
In UA5.0 the macro-diversity on UL E-DCH channels is not supported.
The E-RGCH is not supported either.
Restriction: E-DPDCH spreading factor
The UL SF 2 is not supported in UA5. The maximum throughput is
performed with 2xSF4.

2.2 HSUPA
2.2.2 HSUPA new channels

Logical
DCCH
Traffic
TRB
Mobile y
DCH
Transport
DTCH
DTCH
Signaling
SRB
Mobile x
HS-DSCH
Traffic
TRB
Mobile x
E-DCH
UL
UL
DL
DL
E-DPDCH
Physical
DPDCH
DPDCH
HS-PDSCH
E-HICH
HS-SCCH
E-DPCCH
HS-DPCCH
DPCCH
E-AGCH
E-DCH
E-DPDCH
E-DPCCH
E-HICH
E-AGCH
E-RGCH
Transport
Physical
Physical
Physical
Physical
Physical
Enhanced Dedicated CHannel

E-DCH Dedicated Physical Data CHannel
E-DCH Dedicated Physical Control CHannel
E-DCH HARQ Indicator CHannel
E-DCH Absolute Grant CHannel
E-DCH Relative Grant CHannel

E-RGCH
2.2 HSUPA
2.2.3 HSUPA concepts: UA05 UE Capabilities
E-DCH
Category
Maximum
number of eDCH codes
transmitted
Minimum
spreading
factor
Support for 10
and 2ms TTI eDCH
Maximum number of bits

of an e-DCH transport
block transmitted within a
10 ms e-DCH TTI
Air
Interface
data rate
Maximum number of bits

of an e-DCH transport
block transmitted within
a 2 ms e-DCH TTI
Category 1
SF4
10ms TTI only
7296
700kbps
Category 2
SF4
10ms and 2ms

TTI
14592
1.4Mbps
2919
Category 3
SF4
10ms TTI only
14592
1.4Mbps
Category 4
SF2
10ms and 2ms

TTI
20000
2Mbps
5837
Category 5
SF2
10ms TTI only
20000
2Mbps
Category 6
2
2
SF2
SF4
10ms and 2ms

TTI
20000
2Mbps
11520

Air
Interface
data rate
1.4Mbps
2.9Mbps
5.7Mbps
2.2 HSUPA
2.2.4 HSUPA terminal properties
User Equipment category
Multi User Detection Factor

(between 0 and 1)
User Equipment category
* Note
From the terminal capability point of view, an HSUPA-capable terminal is required to support HSDPA as well.

2.2 HSUPA
2.2.4 HSUPA terminal properties [cont.]
HSDPA and HSUPA

options
Terminal name
Minimum and maximum

transmission power
Reception equipment
Gain and loss in terminal
Terminal noise figure

Possible management of
compressed mode
Maximum number of
transmitters to which a
terminal can be connected
Enables A9155 to take into account the

self-interference produced by the
terminal (Signal Cleanness)
DL rake factor used for

the signal recombination
at the terminal
* Note: Reception equipment may be defined in the Reception Equipment Type table. You can open it by selecting
Reception Equipment in the Terminals folder context menu. Service quality targets (DL and UL Eb/Nt) as well as quality
indicators (BER, BLER, FER) are closely dependent on the service, the mobility and the type of reception equipment. For
each of them, quality graphs (quality indicator as a function of a quality measure) may be entered; they are specified for
the receiver equipment - service - mobility triplet.

2.2 HSUPA
2.2.5 HSUPA service properties
A-DPCH-EDPCCH bearer service

required by a HSUPA user
A-DPCH-EDPCCH activity factor
Average requested rate during a

HSUPA call
Scaling factor between the

application and RLC throughputs
and throughput offset

2.2 HSUPA
2.2.6 HSUPA bearer properties
Defined in 3GPP Specifications

2.2 HSUPA
2.2.7 HSUPA User Equipment categories
UE capabilities standardised into 6 categories according to 3GPP

specifications

2.2 HSUPA
2.2.8 Process of HSUPA users

z
HSUPA USERS EITHER CONNECTED OR DELAYED IN THE

HSDPA PART
They are considered in the order established during the user
distribution generation
REJECTION OF HSUPA USERS

When the maximum number of users per cell is exceeded

2.2 HSUPA
2.2.9 Admission control

z
FOR EACH HSUPA USER

A9155 selects a list of HSUPA bearers compatible with the
user equipment capabilities
Then, it checks that the lowest compatible HSUPA bearer
(the one with the lowest E-DPDCH Ec/Nt required) does not
require a terminal power higher than the maximum terminal
power allowed
REJECTION OF THE HSUPA USER

When the terminal power required to obtain the lowest
compatible HSUPA bearer exceeds the maximum terminal
power

2.2 HSUPA
2.2.10 Noise rise scheduling

z
NOISE RISE SCHEDULING PROCESS
Calculation of the c
remaining load
Load
sharing d
between users
Calculation of the
e
maximum
E-DPDCH
Ec/Nt allowed
HSUPA bearer
selection
Look-up of
peak rate
HSUPA BEARER SELECTION BASED ON LOOK-UP TABLE
Double-click the reception equipment

RLC
2.2 HSUPA
2.2.10 Noise rise scheduling [cont.]

z
1st STEP: LOAD SHARING BETWEEN USERS

For each cell, A9155 calculates the remaining cell load factor
on uplink
y Maximum load factor allowed on uplink minus the uplink load
produced by the served R99 traffic
A9155 evenly shares the remaining cell load factor between

the admitted HSUPA users
y Each admitted HSDPA user is assigned a right to interfere
2nd STEP: CALCULATION OF THE MAXIMUM E-DPDCH Ec/Nt

ALLOWED
It depends on:
y The part of the uplink load factor that each admitted HSUPA user
can produce
y The uplink reuse factor of the cell

2.2 HSUPA
2.2.10 Noise rise scheduling [cont.]

z
3rd STEP: HSUPA BEARER SELECTION

Depending on the maximum E-DPDCH Ec/Nt and on UE capabilities
Among the HSUPA compatible bearers
This is the bearer with the highest potential throughput (ratio
between the RLC peak rate and the number of retransmissions)
where:
y The required E-DPDCH Ec/Nt the maximum E-DPDCH Ec/Nt
y The required terminal power the maximum terminal power
4th STEP: LOOK-UP OF RLC PEAK RATE

Once the bearer selected, A9155 reads in the HSUPA Bearer table the
RLC peak rate supported
HAPPY BIT MECHANISM IS MODELLED

A user is Happy if the RLC peak rate provided by the HSUPA bearer
exceeds the average requested rate and unhappy if not
Collection of the unused load of happy users and redistribution
among unhappy users

2 HSXPA
AVAILABLE PREDICTIONS
UMTS PREDICTIONS
HSDPA PREDICTION
HSUPA PREDICTION

2.3.1 AVAILABLE PREDICTIONS

z
COVERAGE PREDICTIONS
UMTS Dedicated Coverage
Predictions
y Quality Studies
{
Ec/Io, Eb/Nt, Service Areas
y Handover Study
y Noise Studies
{
Nt, Pilot pollution
HSDPA Dedicated Coverage Study

y Quality Studies
y Rate/Throughput Studies
HSUPA Dedicated Coverage Study

y Quality Study
y Rate/Throughput Studies
z
POINT PREDICTION

2.3.1 AVAILABLE PREDICTIONS [cont.]

z
UMTS PREDICTIONS ARE CALCULATED

FOR
Given load conditions
y UL Load Factor
y DL Power Used
A non-interfering user with

y A service
y A mobility
y A terminal type


z
LOAD CONDITONS ARE DEFINED IN THE CELLS TABLE
Values taken into consideration in

predictions for each cell


z
SERVICE PROPERTIES
PARAMETERS USED IN PREDICTIONS
R99 Bearer Parameters

Handover Capabilities
Possible Carriers
Body Loss


z
R99 BEARER PROPERTIES
Double-click the record in the table

Type: Traffic Class
Max Downlink Traffic Power per
Channel
UL and DL Eb/Nt Admission
Thresholds (per mobility)


z

Ec/Io threshold (AS): this value is verified for the best server


z
TERMINAL PROPERTIES
Receiver equipment
Maximum terminal power
Gain and losses
Noise figure
Active Set size
DL rake factor
Rho factor
Compressed mode capability


z COVERAGE PREDICTION SETTINGS
If no simulation is selected
Prediction based on DL power and
UL load from Cells table
User and carrier specification
Display type template
Tip text content and legend


z DISPLAY OPTIONS FOR UMTS COVERAGE PREDICTIONS
Note
It is possible to know the probability to have a given quality indicator (BER, BLER, FER,) per pixel. This kind of study is not
directly available in the list of standard studies proposed by A9155. In order to calculate it, you have to proceed in three steps:
- The quality indicator you want to study and the used quality measure must be correctly indicated in the Quality Indicators table
(To open this table, select Quality indicators in the Services folder context menu).
- The quality graph giving the correspondence between the measured quality and the quality indicator must be defined (the
graph can be defined in the receiver equipment properties).
- Finally, depending on the quality measure selected for the quality indicator, select either the Pilot reception analysis (Ec/Io)
option, or the Service area (Eb/Nt) downlink option, or the Service area (Eb/Nt) uplink option from the study types window. Then,
choose suitable settings in the Simulation (service, mobility type) and Display (BER, BLER, FER,) tabs.


z EXAMPLES Ec/Io
Pilot Reception Analysis Study
Pilot Pollution Study


z EXAMPLES Eb/Nt
Service Area (Eb/Nt) Uplink Study
Effective Service Area Study


z EXAMPLES Handover + Downlink Noise
Handover Status Prediction Study
Downlink Total Noise Study


POINT ANALYSIS TOOL (1)
z RADIO RECEPTION DIAGNOSIS AT A GIVEN POINT
In the Tool bar, click
Select the AS Analysis tab in the Point Analysis window
Define AS analysis settings
* Notes
No saturation is taken into account when using a probe mobile !
When using the active set analysis to analyse a specific UMTS study, be sure to have the same settings between the coverage
and the point analysis (Shadowing effect taken into account or not, indoor reception or not, user description, load condition)

2.3.2.1 UMTS PREDICTION

POINT ANALYSIS TOOL (2)
Active Set /
Handover Status
also shown in the
Map-Window
Choice of UL&DL load conditions : If no simulation

is selected
Analysis based on DL power and UL load from
Cells table
Definition of a userdefinable probe"

receiver, Indoor or not
Analysis on a
specific carrier or
all (carrier selection
as set in site
equipment)
Pilot
availability
None
Transmitters of
the mobile active
set (greyed zone)
Transmitters out
of the active set
(white zone)
Service
availability in UL
and DL
Lower limit of the active

set (best pilot quality Best server threshold to be part of
Active set threshold)
the active set (depending on the
mobility type)
* Note
The reason of unavailability of the considered service is given by double-clicking the related red cross (in UL and/or DL)

2.3.3 HSDPA PREDICTIONS

z
PRINCIPLES OF HSDPA PREDICTIONS
HSDPA PREDICTION CAN BE CALCULATED

y
To analyse the UL and DL A-DPCH qualities
To analyse the HS-SCCH quality/power
To model fast link adaptation for a single user within the cell
To model fast link adaptation for many users within the cell
HSDPA PREDICTION INPUTS

y
The cell total power
The cell HSDPA power
The number of HSDPA users within the cell if the study is calculated for several
users
HSDPA user description: Terminal, service and mobility type

2.3.3 HSDPA PREDICTIONS [cont.]

z
HSDPA SERVICE PROPERTIES

Possible Carriers
Body Loss
HSDPA Capability and Application Throughput Parameters


z
HSDPA BEARER PROPERTIES

TRANSPORT FORMAT RESOURCE COMBINATION (TFRC) SELECTED BY
THE SCHEDULER DURING FAST LINK ADAPTATION
y Defined in 3GPP Specifications


z

Ec/Io threshold (AS): this value is verified for the best server
HS-SCCH Ec/Nt threshold (dB): minimum quality required for
HSDPA link


z
HSDPA CAPABLE TERMINAL PROPERTIES
Receiver equipment
Gain and losses
Noise figure
DL rake factor
Rho factor
HSDPA capability and HSDPA specific parameters
y UE category
y MUD factor


z
HSDPA UE CATEGORY PROPERTIES

USER EQUIPMENT (UE) CAPABILITIES DEFINED IN 3GPP
SPECIFICATIONS


z DISPLAY OPTIONS FOR HSDPA PREDICTIONS


z
FAST LINK ADAPTATION MODELLING

A9155 DETERMINES THE BEST HSDPA BEARER THAT EACH USER CAN
OBTAIN
PROCESS : PREDICTION DONE VIA LOOK-UP TABLES

CPICH/HS-PDSCH
Ec/Nt evaluation
CQI calculation
HSDPA bearer
selection
Look-up of RLC
peak rate
MODELLING FOR A SINGLE USER

y Each pixel of the map is considered as one HSDPA user
y Each HSDPA user is processed as if he is the only user in the cell => He uses
the entire available HSDPA power of the cell
MODELLING FOR SEVERAL USERS

y A9155 considers several HSDPA users per pixel
y The cell HSDPA power is shared between users


z HSDPA PREDICTION EXAMPLE
z HSDPA Study Display per RLC peak rate for a single user

2.3.4 HSUPA PREDICTIONS

z
PRINCIPLES OF HSUPA PREDICTIONS

HSUPA PREDICTION CAN BE CALCULATED TO ANALYSE
y The power required by the terminal
y The required E-DPDCH quality
y The rates and throughputs
HSUPA PREDICTION INPUTS

The cell UL load factor
The cell UL load factor due to HSUPA
The cell UL reuse factor
The maximum cell UL load factor
The number of HSUPA users within the cell if the study is
calculated for several users
y HSUPA user description: Terminal, service and mobility type
y
y
y
y
y
TWO CALCULATION OPTIONS

y HSUPA resources are dedicated to a single user
y HSUPA resources are shared by several users

2.3.4 HSUPA PREDICTIONS [cont.]

z
HSUPA SERVICE PROPERTIES

Possible Carriers
Body Loss
HSUPA Capability and Application Throughput Parameters


z
HSUPA BEARER PROPERTIES

TRANSPORT FORMAT COMBINATION (TFC) SELECTED BY
THE SCHEDULER
y Defined in 3GPP Specifications


z
HSUPA CAPABLE TERMINAL PROPERTIES
Receiver equipment
Gain and losses
Noise figure
DL rake factor
Rho factor
HSDPA and HSUPA capabilities
y UE category
y MUD factor


z
HSUPA UE CATEGORY PROPERTIES

USER EQUIPMENT (UE) CAPABILITIES DEFINED IN 3GPP SPECIFICATIONS


z
DISPLAY OPTIONS FOR HSUPA PREDICTIONS

ON EACH PIXEL, YOU CAN DISPLAY
y The E-DPDCH Ec/Nt required to otain the HSUPA bearer
y The terminal power required to obtain the HSUPA bearer
y The RLC peak rate that the HSUPA bearer can provide
y The minimum RLC throughput that the HSUPA bearer can provide
y The application throughput that the HSUPA bearer can provide
y Etc.


z
NOISE RISE SCHEDULING MODELLING

A9155 DETERMINES THE BEST HSUPA BEARER THAT EACH USER CAN
OBTAIN
PROCESS : PREDICTION DONE VIA LOOK-UP TABLES
Calculation of the c
remaining load
Load
sharing d
between users
calculation of the e
maximum
E-DPDCH
Ec/Nt allowed
HSUPA bearer
selection
Look-up of
peak rate
MODELLING FOR A SINGLE USER

y Each pixel of the map is considered as one HSUPA user
y Each HSUPA user is processed as if he is the only user in the cell => He uses
the entire remaining load of the cell
MODELLING FOR SEVERAL USERS

y A9155 considers several HSUPA users per pixel
y The remaining load of the cell is equally shared between users

RLC

z HSUPA PREDICTION EXAMPLE
z HSUPA Study Display per RLC peak rate for a single user

3 UMTS/GSM co-location and Antenna

Systems

3 UMTS/GSM co-location and Antenna Systems
3.1 Contents
Interference mechanisms due to co-location

y Spurious emissions
y Receiver blocking
y Intermodulation products
y Summary on required decoupling required for the 3 interference
mechanisms
y UMTS-UMTS co-location
Antenna solutions
y Dual band sites GSM 1800 - UMTS FDD
y Dual band sites GSM 900 - UMTS FDD
y Triple band sites GSM 900 - GSM 1800 - UMTS FDD
Feeder sharing impacts

TMA in co-location configurations
TMA in feeder sharing solutions

3.1 Contents
1.7.1.1 Transmitter noise/spurious emissions (in band interference)

The transmitter noise floor and the spurious transmissions could fall into the
receive band of the co-sited system
1.7.1.2 Receiver blocking (out of band interference)

The transmit signal of one system could block the receiver of the other
system
1.7.1.3 Intermodulation products

Intermodulation products could interfere the receivers of one or both
systems

3.1.1.1 Transmitter Noise / Spurious Emissions

z
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
UMTS/FDD
UL
1880
In band interference
1920

f/MHz
3.1.1.1 Transmitter Noise / Spurious Emissions [cont.]

z
z
z
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
y <-62 dBm/100kHz means <-46dBm/3.84MHz
Same service area, co-location

y <-96 dBm/100kHz means <-80dBm/3.84MHz
z
Values are valid in 3G receive band

900-1920 TDD, 1920-1980 FDD UL, 2010-2025 TDD

Increase of decoupling
requirement in case of
GSM UMTS colocation of 51 dB!

Spurious Emissions GSM1800 UMTS (1)
Antenna system
Calculation on next slide

Spurious emissions
Old ETSI : < -29 dBm
Alcatel-Lucent and new
3GPP
< -80
dBm
Antenna
connectors
Limiting interference level:

< - 114 dBm
ANC
Attenuation in UMTS
MBS 9100
TX/ RX
TRX
BTS


Equipment
type
Spurious
emissions
(a t BTS/
N od e B
a n tenn a
con nector )
Limiting
interference
level
ETSI specifica tions (GSM 05.05)

up to v.8.4.1
v.8.5.1
- 29dBm
- 80dBm
Alca tel- Lucent GSM 1800

BTS
- 80 dBm
N oise a t UMTS receiver without GSM 1800 impa ct:

Th er m a l n oise (- 108 d Bm ) p lus r eceiver noise fig ur e (4 d B), i.e.
104
d Bm
(Pn oi se [d Bm ] = - 174 d Bm + System N oise Fig ur e [d B] + 10 log
(BW [Hz])
Deg r a d a tion of sen sitivity b y 0.4 d B a ccep ta b le
(level 10 d B b elow n oise floor )
- 104 dBm 10 dBm = - 114 dBm
Required
decoupling
up to v.8.4.1
v.8.5.1
- 29 d Bm
d ecoup lin g = 114 d Bm
- 80 d Bm
d ecoup lin g = 114 d Bm
Decoupling = 85
dB
Decoupling = 34
dB
- 80 d Bm d ecoup lin g =
- 114 d Bm
Decoupling = 34 dB


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.


z
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.
GSM 900- UMTS

The ANC-module of the GSM 900 BTS provides 65 dB attenuation in the 2 GHz band. It is therefore fully compliant to the GSM 05.05
v.8.5.1 and even fulfills a decoupling requirement of 30dB for co-located UMTS sites.
It has to be noted that the GSM 900 sites have to fulfill the same GSM 05.05 requirements as stated in above chapter, resulting in the
same decoupling values. This implies that for BTS which are only compliant to the old GSM 05.05 v.8.4.1, a decoupling of 85 dB is
required. However, the GSM 900 band being very far from the UMTS band, and the GSM 1800 band (for which the requirements are
very strict) lying in between them, this is very unlikely to occur. It can therefore be assumed, that also other suppliers equipment with
their integrated antenna network comply with the 34dB decoupling demand of the new GSM 05.05 v.8.5.1
UMTS-UMTS
According to the 3GPP standardisation (TS 25.104 chapter 6.6.3.2.1), the level of spurious emissions of a Node B within the UMTS/FDD
uplink band (1920-1980MHz) must not exceed -96 dBm with a frequency bandwidth measurement of 100 kHz. A Mapping on the
effective carrier bandwidth of 3.84 MHz results in an acceptable spurious level of 80 dBm within one carrier.
If we accept a sensitivity degradation of 0.4 dB of the co-located Node B, the acceptable level in the receiver Bandwidth becomes -114
dBm.
This means that for the minimum decoupling between the antenna ports of two co-located 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.

3.1.1.2 Receiver blocking
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
Feeder
loss
RX blocking
TX power
GSM BTS
UMTS
Node B

3.1.1.2 Receiver blocking [cont.]

z
Link Budget for Blocking Evaluation
Example: UMTS blocks receiver of GSM1800
Link budget
Va lue
UMTS N ode B TX output power
43.0 dBm
Assum ed a ntenna d ecoup ling
- 30 d B
Assum ed feed er a nd connector loss
0 dB
GSM 1800 received power (@ 2000 MHz)
13.0 dBm
Specifica tion
3GPP
Alca telLucent
GSM 1800 b lock in g lim it
0 d Bm
23 d Bm
No
Yes
Blocking limit fulfilled


z

Example: UMTS blocks receiver of GSM900
Link budget
Va lue
43.0 dBm
- 30 d B
0 dB
GSM 900 received power (@ 2000 MHz)
13.0 dBm
Specifica tion
3GPP
Alca telLucent
GSM 900 b lock ing lim it
8 d Bm
35d Bm
No
Yes



z

Example: UMTS blocks receiver of UMTS
Link budget
Va lue
43.0 dBm
- 30 d B
0 dB
UMTS received power (@ 2000 M Hz)
13.0 dBm
Specifica tion
UMTS b lock ing lim it


3GPP
Alca telLucent
- 15 d Bm
30 d Bm
No
Yes

z
Critical: Node B being blocked by co-located GSM 900, GSM 1800

or UMTS/FDD
GSM antenna
UMTS antenna
Decoupling
Problem doesnt occur for

Alcatel-Lucent Node B
Feeder
loss
TX power
GSM BTS
Feeder
loss
RX Blocking
UMTS
Node B


z

Example: GSM 900 blocks receiver of UMTS
Link budget
Va lue
GSM 900 TX output power
46.0 dBm
Assum ed a ntenna d ecoup lin g
- 30 d B
0 dB
UMTS received power (@ 900 M Hz)
16.0 dBm
Specifica tion
UMTS b lock in g lim it


3GPP
Alca telLucent
- 15 d Bm
25 d Bm
No
Yes

z

Example: GSM 1800 blocks receiver of UMTS
Link budget
Value
GSM 1800 TX output power (high power)
46.7 dBm
Assumed antenna decoupling
- 30 dB
Assumed feeder and connector loss
0 dB
UMTS received power (@ 1800 MHz)
16.7 dBm
Specification
UMTS blocking limit
3GPP
AlcatelLucent
-15 dBm
23 dBm
No
Yes

Conclusion
It can be stated that receiver blocking is no problem for co-located
Alcatel-Lucent 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.

3.1.1.3 Intermodulation Products

z
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)
Intermodulation, also called non-linear distortion, is generated in non-linear devices due to the transfer
characteristic of such devices, e.g. amplifiers, diodes
The output signal of a non-linear device will not have the same shape as the input signal. Its frequency
spectrum will have more components than the input signal. The new frequency components are either
harmonics of the input frequencies or a combination of the input components (mixing). These new
frequencies are called intermodulation products. If the input signal is made up of two sinewave signals with
frequencies f1 and f2, the output signal will contain frequency components at
fIM = m f1 + n f2
product
with m, n = 0, +1, +2, +3, where /m/+/n/ is the order of the IM
Intermodulation problems due to co-location might rise, if transmit carriers from the co-located system "A"
generate intermodulation products falling into a used receive channel of system "B" or vice versa.

3.1.1.3 Intermodulation Products [cont.]

z
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
TX/ RX
Antenna
coupling network
TX
RX
GSM BTS
Antenna
coupling network
TX
RX IM3
UMTS Node B
According to the GSM recommendation 05.05, the iNoteand intermodulation attenuation has to be 70 dBc
in 300 kHz bandwidth. For a transmit power of 46 dBm, this means 24 dBm intermodulation power. The TX
filter within the ANC module of the Alcatel-Lucent GSM 1800 BTS suppresses this level by at least additional
40dB within the UMTS receive band. At the GSM 1800 antenna connector the intermodulation level is
therefore 64 dBm. To achieve the required intermodulation level of 114 dBm at the UMTS antenna
connector, an additional attenuation of 50 dB by the GSM/ UMTS diplexer or air decoupling is required. An
additional margin of 5 to 10 dB should be taken into account, because the total intermodulation power is
distributed over a 600 kHz bandwidth (additional 3 dB) and more than one GSM intermodulation product
may fall inside a UMTS receive channel. The required decoupling therefore would be 55 dB to 60 dB


z
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
TX/ RX
Antenna
coupling network
TX
RX
TX
GSM BTS
Antenna
coupling network
RX
IM
UMTS Node B
According to the ETSI 3GPP specification TS 25.104, the iNoteand interfering signal level for the UMTS
receiver has to be 48 dBm. At this interfering level a wanted signal with a level of -115 dBm can be
received. An additional margin of 5 dB for the interfering level is taken into account in order not to degrade
a wanted signal at a level of 124 dBm (reference sensitivity level, Alcatel-Lucent). The allowed interfere level
without UMTS receive filter would be 48dBm 5 dB = -53 dBm. For GSM 1800 transmit signals the AlcatelLucent receive filter will provide 90 dB suppression. With this filter the allowed interfere level at the UMTS
antenna connector is +37 dBm. Therefore 9 dB decoupling is already sufficient (TX power = 46 dBm). This is
less than in case 1.


z
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
At the antenna connector of the diplexer the GSM transmitters have power levels of about 46 dBm. The
allowed intermodulation power level is 114 dBm. The attenuation has to be 160 dBc. This value is very critical
for the diplexer and the antenna system. It is suggested to avoid this scenario by careful frequency planning.

3.1.1.4 Intermodulation Products : conclusion

z
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.
y
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

3.1.1.5 Summary on the required Decoupling

GSM 900 (RX)
It is assumed, that the

decoupling provided by
the antenna/diplexer
system is at least 30 dB.
In fact, using AlcatelLucent equipment
requires for certain
combinations even less
isolation than those 30dB
Intermodulation is
suppressed by frequency
planning
3G TS
25.104
AlcatelLucent
GSM 05.05
46 dB
Blocking
30 dB
v.8.5.1:
34dB
GSM
spurious
v.8.5.1:
34dB
GSM
spurious
AlcatelLucent
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
GSM 05.05
GSM 1800 (TX)
AlcatelLucent
39 dB
Blocking
30 dB
AlcatelLucent
39 dB
Blocking
30 dB
3G TS 25.104
35 dB
Blocking
30 dB
AlcatelLucent
35 dB
Blocking
30 dB
UMTS (TX)
UMTS (RX)
AlcatelLucent
GSM
05.05
GSM 900 (TX)
GSM 900-GSM 1800

decoupling values are
added for completeness,
although not treated
throughout this
document
GSM 1800 (RX)

GSM
05.05
Specification
according
to:
62 dB
Blocking
43 dB
Blocking
43 dB
Blocking

30 dB
30 dB
34 dB
GSM
spurious
58 dB
34 dB
Blocking Spurious
58 dB
34 dB
Blocking Spurious
3.1.1.6 UMTS - UMTS co-location (FDD)

z
z
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)
WCo-location of UMTS operators avoids occurrence of dead zones
UMTS -UMTS co-existence scenarios where the adjacent band operators are not necessarily sharing the
same sites but merely operating in the same region.
UL case
In the uplink, the adjacent channel interference causes noise rise, meaning an increase of the wideband
interference level over the thermal noise in the base station reception of operator B. The effect of the
adjacent channel interference can be seen as a reduced uplink capacity.
DL case
Operator As mobile is receiving adjacent channel interference in the downlink from operator Bs Node B,
this will bring the need to increase the power allocated to that connection in order to compensate the
increased interference in the mobile reception. Since the limited resource in the downlink is the common
power, this means directly a reduction in capacity.
Dead zone
The dead zone area has been defined as the area close to a base station, where mobiles operating in an
adjacent frequency receive such a high level of downlink interference from the interfering base station that
the connection with the serving cell is dropped.
In addition, mobiles close to the base station also create a high level of interference in uplink, at least
before the communication is dropped due to the downlink interference level. Note that dead zone areas
exist in pure macrocell scenarios as well as in macro/micro scenarios, however the latter are usually more
critical since the mobile can get much closer to a microcell antenna, causing a small coupling loss between
mobile and base station.

3.1.1.7 Co-location: Conclusion
Co-siting of GSM and UMTS possible
Co-siting of two adjacent UMTS operators desirable to avoid dead zones
Alcatel-Lucent base stations are prepared for co-siting
Alcatel-Lucent can provide solutions for co-siting of Alcatel-Lucent

GSM and/or UMTS base stations with equipment of any other supplier
Solutions
reduce the ACI problems. This can be done by avoiding scenarios where a mobile is far away from its
serving cell (belonging to operator A) but very close to a Node B of operator B which then leads to
minimising the phenomenon of dead zones.
The solution consists therefore in a co-location of Node Bs of two operators. This means that site
sharing has a positive impact of the performance of both operators systems (if the RF requirements of
the previous chapters are fulfilled).

3.1 Contents
1.7.2.1 Dual-band sites GSM 1800 - UMTS FDD
W 1.7.2.2 Dual-band sites GSM 900 - UMTS FDD
W 1.7.2.3 Triple-band sites GSM 900 - GSM 1800 - UMTS FDD
W1.7.2.4 Multi-operator sites UMTS-UMTS
Co-located antenna systems can be composed of separated single-band antennas. The visual
impact, however, is in a majority of cases a challenge for the site engineering. The use of multi-band
antennas offers a good solution. With multi-band antennas (dual-band or triple-band), the necessary
amount of antennas per site is minimized. By using additional diplexer or triplexer, the requested amount of
feeder cables per sites can be reduced.
The impact on the network planning needs to be evaluated. Adding diplexers to an existing system
increases the losses, which could reduce the coverage area. With multi-band antennas, the
same azimuth applies for all bands. As the network plan for the existing system should not be changed,
the planning process for the new system has to take care about such limitations.
The following sub-chapters reflect on possible antenna solutions for co-located sites.


z
Air Decoupling with Single-band Antennas
GSM 1800 antenna
UMTS antenna
air decoupling
Vertical or cross polarized
Vertical or horizontal
separation
Feeder
Feeder
Independent antenna
characteristics (pattern,
downtilt, gain)
GSM 1800
BTS
UMTS
Node B
Dual-band sites can be set up with single-band antennas or dual band antennas.
Description
Single band antennas with air decoupling, two pairs of feeders
Advantage
Existing GSM1800 antenna system does not have to be modified
Different mechanical and electrical downtilt for GSM1800 and UMTS antenna possible
Disadvantage
High visual impact of additional UMTS antenna
High antenna distance required
Two pairs of feeder cables required (Diversity operation)

3.1.2.2 Separation for air-decoupling

z
For Alcatel-Lucent GSM1800

BTS
Horizontal Separation:
y dh=0.6m
Vertical Separation:
GSM 1800
dh
y 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)
In order to know the exact required decoupling value, the blocking performance of the according
equipment has to be known.
In order to determine then the required minimum distance between the antenna panels, decoupling
measurements were performed. As typical examples, two cross-polarized single-band antennas have
been used, both antennas with 17 dBi gain and a horizontal beamwidth of 65 degree (APX206515-2T
for UMTS, APX186515-2T for GSM 1800, supplier: RFS/ CELWAVE).

3.1.2.3 Decoupling measurements

zTo
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.
For a required decoupling of 81 dB, air antenna decoupling is not a solution, as the required distance would
be too difficult to achieve as the antennas would have to be too apart form each other, for this reason,
another solution is required: see next slide (broadband antenna+diplexer)


z
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/206515-T6
Broadband antenna with one diplexer and one feeder. This combination has to be doubled for the second
antenna branch.
The diplexer has to provide 34dB (in case of Alcatel EVOLIUM GSM 1800 equipment and GSM 05.05
v8.5.1 equipment, 85 dB for ETSI GSM 05.05 v8.4.1 equipment) from the GSM 1800 transmit port to the
UMTS receive port. From the UMTS transmit port to the GSM 1800 receive port, 30 dB of isolation is
required.
Advantage:
Only two feeder cables required
Low visual impact (existing GSM1800 antenna can be replaced by broadband antenna)
Disadvantage
No different mechanical or electrical downtilt for GSM1800 and UMTS
Diplexer for each feeder branch required

3.1.2.4 Dual-band Sites GSM 1800 - UMTS FDD [cont.]

Dual-band antenna with diplexers
Independent on gain and electrical downtilt
feeder sharing
Example: Celwave APX15D6/15W6
Dualband antenna
Diplexer
Feeder
Diplexer
GSM 1800
BTS
UMTS
Node B
Dual band antenna with one feeder and two diplexers. This combination has to be doubled for the second
antenna branch.
Advantage
Only two feeder cables required
Different electrical downtilt possible
Low visual impact
Disadvantage
Two diplexers for each feeder branch required (one of them expensive)
No different mechanical downtilt


z
Dual-band antenna with filters
Independent on gain and electrical downtilt
Four feeders per panel
Filter to reduce decoupling requirements

Dualband antenna
Dualband antenna
-Lucent
Feeder
Feeder
Feeder
Filter
Alcatel
Lucent
GSM 1800
BTS
Alcatel
Lucent
MBS
UMTS
GSM05.05
v.8.4.1.
GSM 1800
BTS
Feeder
Filter
TS 25.104
UMTS
Node B
Dual band antenna with 4 feeders and external filter.This combination has to be doubled for the second
antenna branch.
Using Alcatel-Lucent equipment, no filter is required. In case of another suppliers UMTS Node B only
fulfilling the TS 25.104 blocking requirements, an external filter is required in the UMTS branch. In case of
another suppliers GSM 1800 BTS only fulfilling the GSM 05.05 8.4.1, the solution includes an external filter
directly after the GSM 1800 BTS.
Advantage:
No diplexer required
Low visual impact (existing GSM1800 antenna can be replaced by dual band antenna)
Disadvantage
No different mechanical downtilt,External filters required,4 feeders required

3.1.2.5 Solutions with RFS Celwave components
DCS UMTS
DCS UMTS
DCS
+
UMTS
Diplexer
FD DW 6505-1S
75 dB
75 dB
BTS BTS
DCS UMTS
Broadband
Antenna
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


z
Solutions without Feeder Sharing

GSM 900 antenna
UMTS antenna
GSM900/UMTS Dualband antenna

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

Feeder
UMTS
Node B
Dual band antenna configuration
Description
Advantage
Disadvantage
Existing GSM 900 antenna system

does not have to be modified
High visual impact of additiona

UMTS antenna
Different mechanical and electrical

downtilt for GSM 900 and UMTS
antenna possible
Two feeder cables required
Dual band antenna with two

feeders

No diplexer required
Low visual impact
Two feeder cables required

Dual band antenna with one
Only one feeder cable required
Two diplexers required
feeder and two diplexers

Low visual impact
Single band antennas with air

decoupling, two feeders


z
Feeder Sharing solution
Dualband antenna
Also possible with single

band antennas
Diplexers have to provide

30dB of decoupling
Diplexer
Feeder
Diplexer
GSM 900
BTS
UMTS
Node B

GSMUMTS
Diplexer
Band 1: AMPS/GSM
Band 2: DCS/UMTS
55 dB
FD GW 5504 -1S
->full DC pass
FD GW 5504-2S is:
->DC Block in lower bands
->DC Pass in higher bands
55 dB
BTS BTS
GSMUMTS
Product is available 01/2002

3.1.2.8 Triple-band sites for GSM 900/1800 and UMTS

z
z
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
With respect to the visual impact, triple-band antenna systems will be preferably realised either with singleband and dual-band antennas or with triple-band antennas. Nevertheless, configurations with mono-band
antennas are also feasible. The conditions concerning the decoupling requirements can be taken from the
dual-band co-located sites.
The preferred configuration is dependent on the existing antenna system and the evolution steps to a tripleband site. The network planning aspects pose a further requirement on the antenna arrangement.

3.1.2.8 Triple-band sites for GSM 900/1800 and UMTS [cont.]
Triple-band antenna
Connection matrix Filters not required
for Alcatel
Lucent
equipment!
Diplexer
Feeder
Feeder
Connection Matrix
Feeder
Filter
Diplexer
GSM 1800
GSM 900
BTS
GSM 1800
BTS
UMTS
Node B
UMTS
Diplexerapplication
Feeder
Filter
GSM 1800
UMTS
Filter application
If GSM 1800 equipment is not from Alcatel-Lucent, an isolation of 30 dB might not be enough for the
decoupling between GSM 1800 and UMTS. In this case, additional components must be implemented in
order to fulfil the decoupling requirements (use of diplexer), or to decrease the decoupling requirements (use
of GSM 1800 TX filter).

3.1.2.9 Multi-operator sites: UMTS FDD-UMTS FDD

zSolutions
without feeder sharing. Two

completely separate systems with air
decoupling
Different sector orientation possible

Different tilt can be set up
Operator independence
Simple solution
UMTS antenna
air decoupling
Careful RNP: antenna patterns must not

interfere.
High visual impact
2 feeders needed for each operator
Feeder
Feeder
UMTS
UMTS
Node B
Node B
Operator1
UMTS antenna

Operator2
3.1.2.9 Multi-operator sites: UMTS FDD-UMTS FDD [cont.]

zSolutions
without feeder sharing. Two

operators sharing one antenna panel
Dual UMTS antenna

(or Dual Broadband antenna)
Different electrical tilt can be set up.

Low visual impact.
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
3.1.2.9 Multi-operator sites: UMTS FDD-UMTS FDD [cont.]

zTwo
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
In case the visual impact of the site plays a major role, there is the option to share a UMTS antenna as well as the
feeder cable between two operators. However, since the RX and TX signal are already duplexed at each antenna
connector, a diplexer solution does not make sense. We have to keep in mind that the uplink and downlink signals of the
two operators are in any case interleaved, so a diplexer would not separate the two systems signals. Therefore, there is
only the solution to use a so called Hybrid, which is a combiner in the upstream direction and a splitter in the
downstream direction, so that the transmit signals are combined on the very same antenna and the received signal is
split on the two systems (see figure)
Note that there is no filtering taking place, each Node B receives the whole UMTS RX band and picks out its own useful
signal. The big drawback of this solution are the high losses in both directions, which are 3dB in theory (the power is
divided between the two ports) and around 3.3dB in reality. In most of the cases, 3.3dB of additional losses are not
tolerable. Compared with the separate systems solution, the operator will lose their independence in radio network
planning. They necessarily have to use the same sector orientation and the same downtilt, and have to agree on the
operation and maintenance. A tower mounted amplifier is not possible in this scenario, since DC feed and alarm
handling would not be possible.

3.1.2.10 Antenna Feeder Sharing for Dual-band Sites
Dual-band
antenna
Dual-band
antenna
+45
Diplexer
-45
With
integrated
diplexers
Diplexer
Without
diplexers
Feeder
Feeder
Diplexer
Diplexer
Additional filter depending

on equipment type and
vendor required in the
GSM 1800 branch.
Dual-band
Diplexers
at BTS/Node B
location
Dual-band
By upgrading the dual-band antennas with additional diplexers (often integrated in the antenna radome), the
number of antenna connectors will be reduced by a factor of two. The required feeder system will be the
same as for a single-band antenna system. This kind of application requires further base station diplexers
with a corresponding resplit function.
The additional costs for the diplexers will be justified, if the reduced expenditure of the feeder system is
predominant. Especially for the case of migrating a single-band to a dual-band system, the existing feeder
system can be used ensuring a fast installation during retrofit. It has to be checked, however, whether the
feeder cable fulfils the demands for both systems in terms of losses (the feeder attenuation increases with
higher frequencies).
Diplexing is possible for each combination of the three mobile systems:
GSM 900 with GSM 1800
GSM 900 with UMTS
GSM 1800 with UMTS

3.1.2.11 Antenna Feeder Sharing for Triple-band Sites
GSM 900
Triple-band
antenna
Triple-band
antenna
Four feeders per sector
UMTS
GSM 1800
UMTS
Antenna system
30 dB isolation
Diplexer
Triplexer
Feeder system
Diplexer
50 dB isolation
Triplexer
Antenna system
Diplexer
Lower losses
Diplexer
Easy migration
Two feeders per sector
GSM 1800
GSM 900
Feeder system
Diplexer
GSM 900
GSM 1800
UMTS
Diplexer
BTS systems
GSM 900
GSM 1800
UMTS
BTS systems
A separated triple-band antenna system with diversity support needs at least six feeders per sector.
With feeder sharing, this amount can be reduced. The minimum number per sector is two.
In order to fulfil the need to have only two feeder cables per sector for all three bands, the use of
triplexers are necessary. The following picture illustrates the triplexer application consisting of two
diplexers in combination with a triple-band antenna.
If only diplexing between two mobile systems is applied, please refer to chapter , four antenna feeder
cables per sector are then required.
One representative application is the diplexing of the GSM 1800 and UMTS mobile system. This leads to
separated feeder cables between the GSM 900 and the GSM 1800/ UMTS systems. Further benefits are:
Flexible choice of the feeder type (because the feeder attenuation increases with the frequency)
Diplexers improve simultaneously the decoupling between the systems

3.1.2.12 Feeder sharing losses

z
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 AlcatelLucent equipment!)

(0.4 dB)
3.1.2.12 Feeder sharing losses [cont.]

z
Additional losses due to diplexers: Example
GSM 900
Antenna systems
Worst Case Values!

GSM 900
GSM 1800
UMTS
Components
Diplexer
Diplexer
Influence of feeder sharing (losses in dB)
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.

3.1.2.13 Antenna feeder sharing: conclusion

z
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.
y 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.

3.1.2.14 TMA in co-location configurations
z
z
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

3.1.2.14 TMA in co-location configurations [cont.]
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:

y
Blocking limit of the TMA:

y
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.
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-Lucent UMTS TMA, 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.
For the noise/spurious response calculation, the feeder loss can no longer be taken into consideration for
reducing the interference signal.
Specified Alcatel-Lucent TMA possesses additional filters to suppress out-of-band signals (reduces out-ofband blocking problem)
Alcatel-Lucent Node B reduces amplification to compensate TMA excess gain: avoids increased in-band
blocking of Node B due to TMA
No blocking limit for Alcatel-Lucent TMA due to specification
The DC feed of the TMA has to be resolved for diplexer configuration, avoiding DC passing into antenna
Noise reduction of ANXU has to be set manually during NodeB installation
Step size is 0.25 dB
Rule of thumb: excess gain= (TMA gain - cable loss)
Respecting this rule guarantees 3GPP compliance for blocking requirements, as blocking compliance is
measured for the complete system

Diplexer
DCS GSMUMTS
FD GW 5504-2S
DCS UMTS
(avail: 01/2002)
TMA
TMA
75 dB
DC pass
DC block in Band1
(GSM900)
DC pass in Band 2 (UMTS)
TMA
55 dB
DC block
Diplexer
FD DW 6505-2S
(avail: 04/2002)
55 dB
75 dB
BTS BTS
DCS UMTS
+
PDU
DC pass
75 dB
DC block
DC pass
BTS BTS BTS

DCS GSMUMTS
+
+
PDU
PDU
DC block in Band 1
(GSM1800)
DC pass in Band 2 (UMTS)
TMA
ATM W 1912-1
Gain muss bei der Installation festgelegt werden. Die amplification reduction kann in 0,5dB Schritten
vorgenommen werden. Per default-Empfehlung vom BTS-CC sollte sie = excess gain= (TMA gain - cable
loss) sein. Dann bleibt man garantiert 3GPP compliant (Blocking compliance wird nmlich am
Gesamtsystem gemessen!)
Wenn man mit blocking keine Probleme erwartet, kann man auch weniger reduction einstellen, dann
gewinnt man etwas in der Gesamt-noise figure (aber der Gewinn lohnt sich eigentlich nicht).

3.1.2.16 TMA in feeder sharing solutions

z
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

3.1.2.17 Antenna Systems: Conclusion

z
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

4 Cell parameters (Network Design

Parameters - cell wise)

4.1 Open loop power control
Open loop power control
Node
B
Node
B
If UE receives a STRONG DL
If UE receives a weak DL
signal,
signal,
then UE will speak LOUD.
then UE will speak low.
Problem:
fading is not correlated on UL and DL due to separation of UL and DL
band.
Open loop Power Control is inaccurate.
How is made Power Control?

Open loop power control (also called slow power control):
it consists for the mobile station of making a rough estimate of path loss
by means of a DL beacon signal: far too inaccurate and only used to
provide a coarse initial power setting of the mobile station at the
beginning of a connection
Closed-loop power control:
See next transparency

4.2 Closed loop power control

z
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 rate) Closed loop
Power Control is very fast
Outer loop
Inner loop
Example
in DL
RNC
SIR
target
Node
B
SIR
Power down
estimation
SIR
estimation
Power ...
...
Closed-loop power control:

Inner Loop (also called Fast Loop Power Control)
The Node-B makes frequent estimates of the received SIR (Signal-to-Interference) of the UE and
compared it to a SIR target.
If SIR received > SIR target, Node-B will command UE to lower its power (Power Down) else
Node-B will command UE to increase its power (Power Up).
Power Control step size: about 1 dB.
Measure-command react cycle is performed at 1500 Hz, i.e. at a rate faster than any significant
change of path loss.
Outer Loop
The RNC checks the quality of the signal using for example a CRC-based approach (Cyclic
Redundancy Check) and uses this result to adjust SIR target for the inner loop.
The big issue is to meet constantly the required quality: no worse and also no better, because it
would be a waste of capacity.
The required quality may change with the multipath profile (related to the environment) and with
the UE speed.
The outer loop resides in the RNC because a soft HO may be performed.
Frequency of the outer loop: 10-100 Hz typically
Note: in GSM only slow power control is employed (about 2 Hz)
4.3 Frequency coordination at country borders

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

4.3 Frequency coordination at country borders [cont.]

z
z
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
1
to be negotiated
by both parties
FDD DL3) No IMT2000 CDMA radio

interface used
1900-1980
2010-2025
Any
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
FDD UL
1) no preferential codes used
TDD
Note 1: The distance beyond the border where the thresholds has to be kept, must be agreed
between the different administrations in the concerned countries. This is also depending on the used
propagation model.
Note 2: Higher thresholds (typically 15-20dB) can be agreed between administrations of the
concerned countries.


z
Administrations on both sites of the border

must agree on preferential, neutral and nonpreferential frequencies
e.g. the administrations agree on the following
split (assuming 3 available frequencies):
Frequency type
Country A
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
Note 1: The distance beyond the border where the thresholds has to be kept, must be agreed
between the different administrations in the concerned countries. This is also depending on the used
propagation model.

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)
Country A
(Preferential)
45 dBV/m/5MHz 45 dBV/m/5MHz
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


z
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

4.4 Cost 231-Hata formula

z
Reminder: Cost-Hata formula
h
h d
f
LCOSTHata = A1 + A2 log
+ A3 log T + B1 + B2 log T log 3 C(hR )
MHz
m
m m
z Mapping between COST-Hata and Standard Propagation Model
Alcatel-Lucent
COST-Hata
UMTS
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 AlcatelLucent UMTS Standard Propagation
Model:
z has an additional diffraction
loss represented by K4 has been
added
z can be calibrated by adding a
clutter dependent calibration
offset

4.5 Network architecture dimensioning parameters
Definition
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

4.5 Network architecture dimensioning parameters [cont.]
Parameter
Description
LAC
Location Area Code: LAC is a fixed length code that identifies a location
area within a PLMN. One 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: One 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
999
999
4.6 Transmit power parameters
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,

4.6 Transmit power parameters [cont.]

z
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
1.8.
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
zThese 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
Other Common Channels Power: part of the cell maximum transmit power that is dedicated to the other
control channels. This value is fixed by the user and remains constant.
Other common control channels:
P-CCPCH (BCH) 31 dBm
S-CCPCH (FACH,PCH)31 dBm
Both CCPCHtogether: 34 dBm
Values are calculated under assumption of 43 dBm carrier power.

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


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

5.1 UMTS RNP notations and principles [cont.]

4. Complete the following table:
Iintra=n x C
Iextra=f x Iintra=0.55 x Iintra (homogeneous network with f=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)
n
[users]
I
[dBm]
I +N
[dBm]
Noise
Rise [dB]
Ec/No
[dB]
Eb/No
[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

5.2 UMTS propagation model

z
Exercise:
Lets consider the simplified* formula of the Alcatel-Lucent 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-Lucent standard
propagation model formula and in kilometer in the simplified 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)

5.2 UMTS propagation model [cont.]
Clutter
class
*Assumptions:
-HNodeBeff=30m
Dense
Urban
f(clutter)=3dB
-no diffraction
-homogeneous
Suburban
clutter class around f(clutter)=8dB
the UE
dUENodeB
[km]
C1
[dB]
C2x log(dUE-NodeB )
[dB]
(C2=35.22)
0.5
-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)
Lpath
[dB]

5.3 Cell Range Calculation

UE power class 4
Speech12.2kbits/s
Vehicular A 3km/h
Deep Indoor
UL load factor=50%
Value
in
Comment
f.a.=fixed
assumption
(see
previously)

A1
UE TX power
A2
A3
EIRPUE
21
dBm
dB
see 1.2.3
f.a.
21
dBm
A1+A2
5.8
dB
see 1.2.2
25
dB
see 1.1.3

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


5.3 Cell Range Calculation [cont.]

Value
in
Comment
f.a.=fixed
assumption
(see
previously)
C. Margins
C1
Shadowing margin
4.8
dB
see 1.3.3
C2
Fast fading margin
1.7
dB
see 1.3.3
C3
Noise Rise
dB
see 1.3.5
C4
0.1
dB
see 1.3.5
C5
Interference margin
2.9
dB
C3-C4
D. Losses
D1
dB
f.a.
D2
Body loss
dB
see 1.2.2
D3
20
dB
see 1.2.2
18
dBi
f.a.
126.9
dB
=?
E. Gains
E1
Antenna gainNodeB
MAPL


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

A1
UE TX power
24
A2
A3
EIRPUE
dBm
dB
see 1.2.3
f.a.
24
dBm
A1+A2
3.2
dB
see 1.2.2
17.8
dB
see 1.1.3

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



Value
in
Comment
f.a.=fixed
assumption
(see
previously)
C. Margins
C1
Shadowing margin
4.8
dB
see 1.3.3
C2
Fast fading margin
-0.3
dB
see 1.3.3
C3
Noise Rise
dB
see 1.3.5
C4
0.1
dB
see 1.3.5
C5
Interference margin
2.9
dB
C3+C4
D. Losses
D1
dB
f.a.
D2
Body loss
dB
see 1.2.2
D3
dB
see 1.2.2
18
dBi
f.a.
139.3
dB
E. Gains
E1
Antenna gainNodeB
MAPL


z
Can you complete the following table by using the simplified formula of the Alcatel-Lucent Standard
propagation model (see exercise in 1.3.2)?
MAPL[dB] = C1 + C2 x log(Cell Range [km]) (see exercise in 1.3.2)
Cell Range [km]= 10 (MAPL-C1)/C2
(see solution of exercise 3.2 for C1 and C2 values)
Limiting Service
Speech 12.2k
Deep Indoor
MAPL=126.9dB
(calculated on
previous slide)
PS64 Incar
MAPL=139.3dB
(calculated on
previous slide)
Clutter class
Cell Range
[km]
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

5.4 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 lossNodeB + 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

Abbreviations and Acronyms

Abbreviations and Acronyms (1)

3GPP3rd Generation Partnership Project
3GPP2
3rd Generation Partnership Project 2 (cdma2000)
AAL
ATM Adaptation Layer
AICH Acquisition Indication Channel
ALCAP
Access Link Control Application Part
AMR
Adaptive 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
BMC
Broadcast / 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
CDMA
Code Division Multiple Access
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


EDGE
Enhanced Data rates for GSM Evolution
EIRP Effective 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
GPRSGeneral Packet Radio Service
GSM
Global 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
ISCP Interference Signal Code Power
ISDN Integrated Services Digital Network
ITU
International Telecommunication Union
KPI
L1,L2,L3
LA
LAC
LAI
LCS
MAC
MAPL
MBS
MC
MCC
ME
MExE
MM
MNC
MRC
MSC
MUD
NAS
NBAP
NF
Key Performance Indicator

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


OCNS
Orthogonal Code Noise Simulator
OMC-UR Operation and Maintenance Center UMTS Radio
OVSFOrthogonal 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
QOS
Quality Of Service
QPSKQuadrature 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-Lucent 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


SAC
Service Area Code
S-CCPCH Secondary Common Control Physical Channel
SCH
Synchronization Channel
SF
Spreading Factor
SGSNServing GPRS Support Node
SHO
Soft Handover
SIR
Signal to Interference Ratio
SMS
Short Message Service
SPM
Standard Propagation Model
S-SCH
Secondary Synchronization Channel
STTDSpace 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
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 Committee
Visitor Location Register
Wideband CDMA (for UMTS FDD mode)
World Geodetic System 1984


16-QAM
3GPP
16-Quadrature Amplitude Modulation

3rd Generation Partnership Project
(WCDMA)
3GIP
3rd Generation partnership for Internet
Protocol
AAL
ATM Adaptation Layer
ACELP
Algebraic Code Excited Linear Prediction
ACK
Acknoledgement
ADN
Abbreviated Dialling Number
AID
Alarm Instance Identification
ALCAP
Access Link Control Application Part
AMPS
Advanced Mobile Phone System
AMR
Adaptive Multi Rate
AN (C,XU) Antenna Network
ANRU
Antenna Network Receiver UMTS
ANSI
American National Standard Institute (USA)
ARIB
Association of Radio Industries and Business
(Japan)
ATC
ATM Traffic Contract
ATM
Asynchronous Transfer Mode
BB
Base Band
BCCH
Broadcast Control Channel
BER
Bit Error Rate
BHCA
Busy Hour Call Attempts
BLER
BMC
BM-IWF
BPMT
BSC
BSS
BTS
BWC
CAC
CAMEL
CC
CCCH
CCT
CCTrCH
CDMA
CDR
CDV
CE
CLR
CM
CN
CONT
Block Error Rate

Broadcast Multicast Control
Broadcast Multicast Inter-Working
Function
Node B Performance Monitoring Tool
Base Station Controller
Base Station (sub)System
Base Transceiver Station
Bandwidth Control
Connection Admission Control
Customised Application for Mobile
Enhanced Logic
Call Control
Common Control Channel
Call Context Template
Coded Composite Transport Channel
Code Division Multiple Access
Call Data Record
Cell Delay Variation
Channel Element
Cell Loss Ratio
Configuration Management
Core Network
Controller


CPCH
CPCS
CPS
CPU
CQI
CRC
CS
CS
CTCH
CTD
DB
DCA
DCCH
DCH
DCN
DHO
DHT
DL
DPCH
DPCCH
DPDCH
DRAC
Common Packet Channel

Common Part Convergence Sub-layer
Command Part Sub-layer
Central Processing Unit
Channel Quality indicator
Cyclic Redundant Check
Circuit Switched
Convergence/Adaptation to Services (ATM)
Common Traffic Channel
Cell Transfer Delay
Debug
Dynamic Channel Allocation
Dedicated Control Channel
Dedicated Channel
Data Communication Network
Diversity HandOver
Diversity HandOver Trunk
Downlink
Dedicated Physical Channel
Dedicated Physical Control Channel
Dedicated Physical Data Channel
Dynamic Resource Allocation Control
DRNC
DS
DSCH
DTCH
E-DCH
EDGE
EFR
E-GSM
E-GPRS
EM
ERAN
ETSI
FACH
FBI
FDD
FDL
FDMA
FER
FTP
FW
GCRA
GERAN
Drift RNC
Direct Sequence
Downlink Shared CHannel
Dedicated Traffic Channel
Enhanced Dedicated CHannel
Enhanced Data rates for GSM Evolution
Enhanced Full Rate
Enhanced GSM
Enhanced GPRS
Element (or Equipment) Manager
EDGE Radio Access Network (all-IP)
European Telecommunication Standard Institute
Forward Access Channel
Feed-Back Information
Frequency Division Duplex
File Download (EM application)
Frequency Division Multiple Access
Frame Error Rate
File Transfer Protocol
Firmware
Generic Cell Rate Algorithm
GSM/EDGE Radio Access Network


GGSN
Gateway GPRS Support Node
GMSC
Gateway MSC
GMSK
Gaussian Minimum Shift Keying
GP
Granularity Period
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communications
GTP
GPRS Tunneling Protocol
GTP-U
GPRS Tunneling Protocol-User Plane
GUI
Graphical User Interface
HHO
Hard HandOver
HIF
High speed Interface
HLR
Home Location Register
HO
HandOver
HSDPA
High Speed Downlink Packet Access
HS-DPCCHHigh Speed Dedicated Physical Control CH.
HS-DSCH High Speed Downlink Shared CHannel
HSS
Home Subscriber Service
HS-SCCH High Speed Shared Control CHannel
HSUPA
High Speed Uplink Packet Access
HPLMN
Home PLMN
IMEI
International Mobile Equipment Identity
IMS
IP Multimedia Subsystem
IMSI
IMT
IMT-DS
IMT-MC
IMT-SC
IMT-TC
IOT
IOR
IP
IR
ISC
ISDN
Itf-b
Itf-r
ITU
Iub
Iur
Iu-CS
Iu-PS
Kbps
L1, L2, L3
LA
International Mobile Subscriber Identity

International Mobile Telecommunication
Direct Sequence
Multi Carrier
Single Carrier
Time Code
Inter Operability Tests
Interoperable Object Reference
Internet Protocol
Incremental Redundancy
Internetworking Services Card
Integrated Services Digital Network
Interface Node B - OMC-R
Interface RNC - OMC-R
International Telecommunication Union
Interface Node B - RNC
Interface RNC - RNC
Interface RNC - CN Circuit Switch
Interface RNC - CN Packet Switch
Kilobits per second
Layer , Layer 2, Layer3
Local Area


LAC
LAN
LCS
LED
LLC
LoS
LM
LMT
LIF
LQC
MAC
MAC-hs
MAP
MBS
MBS
MCR
MIMO
MM
MSC
MSP
MTP3
MTP-3B
Local Area Code

Local Area Network
LoCation Services
Light Emitting Diode
Logical Link Control
Line of Sight
Load Module
Local Maintenance Terminal
Low speed Interface
Link Quality Control
Medium Access Control
Medium Access Control - High Speed
Mobile Application Part
Multi-standard Base Station (UTRAN)
Maximum Burst Size (ATM)
Minimum Cell Rate
Multiple Input / Multiple Output
Mobility Management
Mobile Switching Centre
Multiple Subscriber Profile
Message Transfer Part level 3
Message Transfer Part level 3 Broadband
NAS
NBAP
NE
N/E
NEM
NM
NML
NMS
NPA
NTP
OAM
O&M
OD
ODMA
ODT
ODTM
OFDM
OMC-R
OPEX
ORB
OS
OSA
Non Access Stratum

Node-B Application Part
Network Element
Normal/ Emergency
New element manager
Combined EM and SNM
Network Management Layer
Network Management System
Network Performance Analyser
Network Time Protocol
Operation And Maintenance
Operation And Maintenance
Office Data
Opportunity Driven Multiple Access
Office Data Tool
Office Data Tool Macro
Orthogonal Frequency Division Multiplexing
Operation & Maintenance Centre - Radio
OPerational EXpenditures
Object Request Broker
Operating System
Open Service Architecture


OTDOA
-IPDL
OTSR
OVSF
PFS
NACK
NBAP
PCCH
PCR
PCU
PDA
PDC
PDP
PDU
PLMN
PM
PRACH
PS
PSK
PSTN
QoS
QPSK
Observed Time Difference of Arrival

- Idle Period Downlink
Omni directional Tx/Sectorised Rx
Orthogonal Variable Spreading Factor
Proportional Fair Scheduling
Non-Acknoledgement
Node B Application Protocol
Paging Control Channel
Peak Cell Rate
Packet Control Unit
Personal Digital Assistant
Personal Digital Cellular (2G Japan)
Packet Data Protocol
Protocol Data Unit
Public Land Mobile Network
Performance Measurement (O&M)
Physical Random Access Channel
Packet Switched
Phase Shift Keying
Public Switched Telephone Network
Quality of Service
Quadrature Phase Shift Keying
R5
R99
RA
RAB
RAC
RAC
RACH
RAID
RAN
RANAP
RB
RR
RF
RLC
RNC
RNO
RNS
RNSAP
RNTI
RP
RPMT
Release 5
Release 99
Routing Area
Radio Access Bearer
Routing Area Code
Radio Admission control
Random Access Channel
Redundant Array Independent
(or Inexpensive) Disk
Radio Access Network
RAN Application Part
Radio Bearer
Round Robin
Radio Frequency
Radio Link Control
Radio Network Controller
Radio Network Optimiser
Radio Network Sub-System
RNS Application Part
Radio Network Temporary Identity
Reporting Period
RNC Performance Monitoring Tool


RRC
RRM
RV
SAC
SAP
SAR
SAT
SC
SC
SCF
SCR
SDH
SF
SGSN
SHO
SIR
SL
SMS
SNMP
SPU
SQL
SRNC
Radio Resource Control

Radio Resource Management
Redundancy Version
Service Area Code
Service Access Point
Segmentation And Re-assembly
SIM Application Toolkit
Short Cell
System Configuration
System Configuration File
Sustainable Cell Rate
Synchronous Digital Hierarchy
Spreading Factor
Serving GPRS Support Node
Soft HandOver
Signal to Interference Ratio
Scheduling List
Short Message Service
Simple Network Management Protocol
Signaling Processing Unit
Structured Query Language
Serving RNC
SSCOP
SSCP
STM
STTD
SU
TC
TC
TCP
TD-CDMA
TDD
TDMA
TEU
TF
TFC
TFCI
TFCS
TFRC
TFRI
TFS
TIA
TMA
TMN
Service Specific Connection Oriented Protocol

Signaling Connection Control Part
Synchronous Transfer Mode
Space Time transmit diversity
Signalling Unit
Transcoder
Transmission Convergence (ATM)
Transport Control Protocol
Time Division & CDMA
Time Division Duplex
Time Division Multiple Access
Transmitter Equipment UMTS
Transport Format
Transport Format Combination
Transport Format Combination Indicator
Transport Format Combination Set
Transport Format Resource Combination
Transport Format Resource Indicator
Transport Format Set
Telecommunication Industry Association (USA)
Tower Mounted Amplifier
Telecommunication Management Network


TMSI
TPA
TPC
TQL
TRE
TRX
TS
TSAL
TSTD
TTA
TTI
UARFCN
UDP
UE
UICC
UL
UMTS
URA
USB
USIM
Temporary Mobile Subscriber Identify

Transmit Power Amplifier
Transmission Power Control
Query Language for semi-structured data
Transceiver Equipment (GSM)
Transceiver (UMTS V1)
Tunning Session
Tunning Session Application Log
Time Switch Transmit Diversity
Telecommunication Technology Association
(Korea)
Transmission Time Interval
UTRA Absolute Radio Frequency Channel
Number
User Datagram Protocol
User Equipment
UMTS Integrated Circuit Card
Uplink
Universal Mobile Telecommunication System
UTRAN Registration Area
Universal Serial Bus
UMTS Subscriber Identity Card
USM
USSD
UTRA
UTRA
UTRAN
UWCC
VC
VCI
VHE
VLR
VoIP
VP
VPI
VSWR
W3C
WAP
W-CDMA
WIM
XML
User Service Manager

Unstructured Supplementary Service Data
UMTS Radio Access Network (ETSI)
Universal Radio Access Network (3GPP)
UMTS Terrestrial Radio Access Network
Universal Wireless Communications Committee
Virtual Channel
Virtual Channel Identifier
Virtual Home Environment
Visitor Location Register
Voice over IP
Virtual Path
Virtual Path Identifier
Voltage Standing Wave Ratio
World Wide Web Consortium
Wireless Application Protocol
Wide-band Code Division Multiple Access
WAP Identity Module
Extensible Mark-up Language

End of Course
End of Module


UMTS RNP Fundamentals R5 Ed01 AUM

Uploaded by

Copyright:

Available Formats

UMTS RNP Fundamentals R5 Ed01 AUM

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

UMTS RNP Fundamentals R5 Ed01 AUM

Uploaded by

Copyright:

Available Formats

Do not delete this graphic elements in here:

Radio Network Planning

All Rights Reserved Alcatel-Lucent @@YEAR

3FL 11194 ACAA Edition 01

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

3FL 11194 ACAA Edition 01

By the end of the course, participants will be able to:

All Rights Reserved Alcatel-Lucent @@YEAR

3FL 11194 ACAA Edition 01

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

3FL 11194 ACAA Edition 01

Switch to notes view!

3FL 11194 ACAA Edition 01

Table of Contents [cont.]

Switch to notes view!

3.1.6 Alcatel-Lucent Standard Propagation Model

3FL 11194 ACAA Edition 01

All Rights Reserved Alcatel-Lucent @@YEAR

3FL 11194 ACAA Edition 01

1.1 Session presentation

All Rights Reserved Alcatel-Lucent @@YEAR

3FL 11194 ACAA Edition 01

1.1 Session presentation

1.1.1 UMTS network architecture

Entities and interfaces

All Rights Reserved Alcatel-Lucent @@YEAR

Section 1. - Module 1. - Page 9

1.1 Session presentation

1.1.1 UMTS network architecture [cont.]

(Contd from previous page)

3FL 11194 ACAA Edition 01

1.1 Session presentation

1.1.2 3GPP: the UMTS standardization body

UMTS system specifications:

WCDMA (UTRAN FDD)

Releases defined for the UMTS system specifications:

Release 99 (sometimes called Release 3)

In the following material we will only deal with UMTS FDD

All Rights Reserved Alcatel-Lucent @@YEAR

Association of Radio Industries and Business (Japan)

3FL 11194 ACAA Edition 01

1.1 Session presentation

1.1.3 3GPP UMTS specifications

3GPP UMTS specifications are classified in 15 series (numbered from 21

Interesting specifications for UMTS Radio Network Planning:

"UE Radio transmission and Reception (FDD)"

"UTRA (BS) FDD; Radio transmission and Reception

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

All Rights Reserved Alcatel-Lucent @@YEAR

3FL 11194 ACAA Edition 01

1.1 Session presentation

1.1.4 Alcatel-Lucents release overview

All Rights Reserved Alcatel-Lucent @@YEAR

3FL 11194 ACAA Edition 01

1.1 Session presentation

1.1.5 UMTS main radio mechanisms

Sector and cell are not equivalent anymore in UMTS:

All Rights Reserved Alcatel-Lucent @@YEAR