RNP (Radio Network Planning) Fundamentals Umts Ua07: Student Guide

Do not delete this graphic elements in here:
UMTS RNP (Radio Network Planning) Fundamentals UMTS UA07

TMO54067 Issue 1
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent @@YEAR
Course objectives
Switch to notes view!
Course objectives [cont.]

Self-assessment of objectives
At
the end of each section you will be asked to fill this questionnaire Please, return this sheet to the trainer at the end of the training Switch to notes view! Do not delete this graphic elements in here:
Self-assessment of objectives [cont.]

RNP (Radio Network Planning) Fundamentals UTRAN UA7

TMO54067 Edition 01
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 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.
1 1 15
Part 1 RNP UA7 Fundamentals
All Rights Reserved Alcatel-Lucent 2009
Objectives [cont.]
1 1 16
1 UMTS Introduction
1 1 19
1 UMTS Introduction
1.1 Session presentation

Objective:
to get the necessary background information in regards of UMTS basics and RNP principles for a good start in UMTS Radio Network Planning.
Prerequisites:
GSM Radio Network Engineering Fundamentals Introduction to UMTS
1 1 20
1.1.1 UMTS network architecture

Entities and interfaces
Uu (air)
Iu Node B Iub RNC RNS Iur Node B HLR IP networks Node B Iu-CS MSC/VLR GMSC PLMN, PSTN, ISDN, ...
USIM Cu ME
Iub Node B
RNC RNS UTRAN Iu-PS
SGSN
GGSN
UE
CN
External Networks
User Equipme nt
1 1 21
UMTS Radio Access Network
Core Network
1.1.1 UMTS network architecture [cont.]

Alcatel-Lucent WNMS architecture
WNMS
Main server
LAN
ItfB
Performance server
Node B Node B RNC 1500 RNS
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.
Node B Iub Node B RNC 1500 RNS UTRAN

1 1 22
1.1.2 3GPP: the UMTS standardization body
Members: ETSI (Europe) T1 (USA)

Access Network Core Network

ARIB/TTC (Japan) TTA (South Korea)
CWTS (China)
UMTS system specifications:

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

Release 99 (sometimes called Release 3) Release 4 Release 5 (former Release 2000)
In the following material we will only deal with UMTS FDD
1 1 23
1.1.3 3GPP UMTS specifications
3GPP UMTS specifications are classified in 15 series (numbered from 21 to 37), 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:

"UE Radio transmission and Reception (FDD)" "UTRA (BS) FDD; Radio transmission and Reception "Requirements for support of radio resource management (FDD)"
3GPP TS 25.101: 3GPP TS 25.104: 3GPP TS 25.133: 3GPP TS 25.141: 3GPP TS 25.214: 3GPP TS 25.215: 3GPP TS 25.942:
de n "Base Station (BS) conformance testing (FDD) du n ou f "Physical layer procedures (FDD)". be n ca org s "Physical layer - Measurements (FDD) on gpp. i t ica w.3 f "RF system scenarios". i c ww pe s PP G 3
1 1 24
1.1.4 Alcatel-Lucents release overview
UA 05 3GPP R5
Release 6 3GPP R6
UA 06 3GPP R6
Q3
UA 07 3GPP R7
Release 6 3GPP R6
Near Nearcommercial commercial
Q2
March
Q2
March
2007
2008
GBR GBR on on HSDPA HSDPA HSDPA HSDPA vs. vs. DCH DCH QoS QoS E-DCH 2ms E-DCH 2ms TTI TTI 9370 9370 RNC RNC (x2 (x2 cap) cap)
2009 HSDPA HSDPA 21 21 Mbps Mbps

HSUPA HSUPA 5.7 5.7 Mb/s Mb/s AMR-NarrowB, AMR-NarrowB, AMR AMR low low rate, rate, AMR-WideBand AMR-WideBand Full Full IP IP transport transport interfaces interfaces Streaming Streaming over over HSDPA HSDPA Full Mobility (2G, Full Mobility (2G, 3G, 3G, HSPA) HSPA) DL DL 21 21 Mb/s Mb/s (64QAM) (64QAM) (*) (*)
DL DL 42 42 Mbps Mbps (MIMO) (MIMO) DL DL 42 42 Mbps Mbps (DC-HSPA) (DC-HSPA) VoIP VoIP services services 3G 3G - LTE LTE mobility mobility SON SON Geo-location Geo-location info info Streaming Streaming over over HSUPA HSUPA Active Active Antenna Antenna
HSxPA + IMS (IP Multimedia Subsystem )
1 1 25
1.1.5 UMTS main radio mechanisms

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 26
1.1.5 UMTS main radio mechanisms [cont.]

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

first step of UMTS deployment: a single frequency (e.g. frequency 1) is used for the whole network of an operator second step of UMTS deployment: additional frequencies can be used to enhance the capacity of the network: an additional frequency (e.g frequency 2) works as an overlap on the first frequency.
Frequency 2
Frequency 1
1 1 27
Part 1 RNP UA7 Fundamentals All Rights Reserved Alcatel-Lucent 2009

Channelization and scrambling codes (UL side)
Bit rateA 3.84 Mchips/s
Physical channels
UE
3.84 Mchips/s
cch1
Bit rateB
3.84 Mchips/s
cch 2
Bit rateC
3.84 Mchips/s
cscrambling
Modulat or
air interface
. . .
cch 3
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
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
1 1 28

Channelization and scrambling codes (DL side)
Bit rateA 3.84 Mchips/s
Physical channels
cch1
Bit rateB
NodeB sector
Modulat air interface or
3.84 Mchips/s
3.84 Mchips/s
cch 2
Bit rateC
3.84 Mchips/s
cscrambling
. . .
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.
1 1 29
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:
a specific frequency (carrier) a combination channelization code / scrambling code
used to separate the physical channels (2 physical channels must NOT have the same combination channelization code / scrambling code) physical channels are sent continuously on the air interface between start and stop instants
start and stop instants
Examples in UL:
DPDCH: dedicated to a UE, used to carry traffic and signalling between UE and RNC such as radio measurement report, handover command DPCCH: dedicated to a UE, used to carry signalling between UE and NodeB such as fast power control commands
Examples in DL:
DPCH: dedicated to a UE , same functions as UL DPDCH and UL DPCCH P-CCPCH: common channel sent permanently in each cell to provide system- and cell-specific information, e.g. LAI (similar to the time slot 0 used for BCCH in GSM) CPICH: see next slide
1 1 30

CPICH (or Pilot channel)
DL common channel sent permanently in each cell to provide:
srambling code of NodeB sector: the UE can find out the DL scrambling code of the cell through symbol-by-symbol correlation over the CPICH (used during cell selection) power reference: used to perform measurements for handover and cell selection/reselection (function performed by time slot 0 used for BCCH in GSM) time and phase reference: used to aid channel estimation in reception at the UE side
The CPICH contains: 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
1 1 31
Pre-defined symbol sequence Tslot = 2560 chips , 20 bits = 10 symbols
Slot #0
Slot #1
Slot #i 1 radio frame: Tf = 10 ms
Slot #14

3GPP Channel mapping in HSDPA (Downlink)
Logical Channels
DTCH CTCH DCCH CCCH PCCH BCCH
Transport Channels
DCH FACH PCH BCH
Physical Channels
DPDCH + DPCCH S-CCPCH P-CCPCH
DPDCH and DPCCH multiplexed by time
Not associated with transport channels

1 1 32
AICH
PICH
CPICH
P-SCH
S-SCH

3GPP Channel mapping in HSDPA (Uplink)
Logical Channels
DTCH DCCH CCCH
Transport Channels
DCH1
DCH 2
RACH
CCTrCH
Physical Channels
DPDCH + DPCCH PRACH
DPDCH and DPCCH multiplexed by modulation
Note: In Evolium R5, DCCH is not mapped on HS-DSCH
1 1 33

Example of Code Tree Allocation
SFHSDPA 16 = 16 chips (fixed) Up to 15 codes to HSDPA transmission are mapped.
For DCH : allocation of codes by signalling (RRC/NBAP) (change possible but procedure is around 1s )
SF=1 SF=2 SF=4 SF=8 SF=16

Code used by one R99 UE on DCH requiring high data rate
C16,0
Codes reserved for R99 UE on DCH
Branch used to map Common channels
NBAP - Node B Application Part RRC - Radio Resource Control

1 1 34

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 UE 2
an efficient and fast power control is necessary in UL to avoid near-far effect power control is also used in DL to reduce interference and consequently to increase the system capacity
Power control mechanisms
(see Appendix for more details):
open loop (without feedback information) for common physical channels closed loop (with feedback information) for dedicated physical channels (1500 Hz command rate, also called fast power control)
1 1 35

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

RNC Node B
UE
Softer handover (different sectors of the same NodeB)

Active Set (AS) and Macro Diversity Gain
All cells, which are involved in soft/softer handover for a given UE belong to the UE Active Set (AS):
usual situation: about 30% of UE with at least 2 cells in their AS. up to 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:
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 two physical signals (with the same content) sent by two different cells and received by one UE soft/softer handover: MRC in UE
DL

1 1 37
1 UMTS Introduction
1.2 HSXPA overview

This section will take a look at the main concepts of HSDPA and HSUPA.
1 1 38
1.2 HSXPA overview
1.2.1 HSDPA
HSDPA: High Speed Downlink Packet Access Part of 3GPP Release 5 (R5) and later releases
Purpose: Enhance 3G Mobile systems by offering higher data rates in the Downlink Direction

Direct evolution of 3GPP R99 networks (UMTS)
To further extend your UMTS network performances
1 1 39
1.2 HSXPA overview
1.2.2 New physical channels

HS-Physical Downlink Shared CHannel (HS-PDSCH) Downlink
HS data channel (Bit rate > 10 Mbps) up to 15 HS-PDSCHs SF = 16
User data on the HS-PDSCH (DL) & Signalling on the HS-SCCH (DL)
HS-Shared Control CHannel (HS-SCCH) Downlink
transmits format parameters (channelization code, modulation, TBS size) H-ARQ info (process, new data, redundancy version) up to 4 HS-SCCH per UE UE identification SF = 128 H-ARQ (ack/nack) Channel Quality Information (CQI) SF = 256
HS-Dedicated Physical Control CHannel (HS-DPCCH) Uplink

Channel Quality Feedback on the HS-DPCCH (UL)
1 1 40
1.2 HSXPA overview
1.2.3 HSDPA: Key features
Fast Scheduling
in the Node-B
Adaptive Modulation &Coding
AMC
HSDPA HARQ
For Fast retransmissions
High Speed Downlink Packet Access

1 1 41
Hybrid-Automatic Repeat Request
1.2 HSXPA overview
1.2.3 HSDPA: Key features [cont.]

Throughput vs. C/(I+N) [Vehicular A 30 km/h]
Throughput [Kbps]
Adaptive Modulation and Coding

HS-PDSCH
3500 QPSK_1_724 3000 2500 2000 1500 1000 500 0 -20 QPSK_2_1430 QPSK_3_2159 QPSK_5_3630 QPSK_10_7168 QPSK_15_10821 16QAM_1_1430 16QAM_2_2876 16QAM_5_7168 16QAM_15_21754 Envelope
uses adaptive
modulation (QPSK or 16 QAM) coding (Turbo Coding)

The
-15
-10
-5 C/(I+N) [dB]
10
Turbo encoder has fixed code rate of 1/3 Power Control and variable SF
Variable effective code rates are achieved by rate matching (puncturing or repetition)
Replaces
Higher dynamic More efficient for users close to Node-B
1 1 42
1.2 HSXPA overview
Fast Scheduling
in the Node-B
Fast
Scheduling in the Time domain (1):
Transmission Time Interval (TTI) of 2ms assigned to users the length of HS-DSCH sub-frame (TTI) is 3 slots (7680 chips)
Data Ndata1 bits Tslot = 2560 chips, M*10*2 bits (k=4)
k
Slot #0
Slot#1 1 HS-PDSCH subframe: T f = 2 ms
Slot #2
1 1 43
1.2 HSXPA overview
Fast Scheduling
in the Node-B
Fast
Scheduling in the Time domain (2):
Transmission is based on:

User data on the HS-PDSCH (DL) & Signalling on the HS-SCCH (DL)
Channel Quality UE Capabilities Current load in the cell (available resources / buffer status) Traffic Priority classes / QoS classes UE Feedback (ACK/NACK)
Fast
Scheduling in the code Domain
Up to 15 codes in parallel per TTI
Channel Quality Feedback on the HS-DPCCH (UL)
1 1 44
1.2 HSXPA overview

High
Order modulation: 16QAM Code Multiplexing: up to 15 codes in parallel User can be code and time multiplexed (TTI= 2ms)
q1
i1 i2 q2
1011 1001
1.3416
i2
0001 0011
1010
1000
0.4472
0000
0.4472
0010
1.3416
1110
1100
0100
0110
q2
1111
1101
0101
0111
Codes
TTI = 2ms
Fixed
Spreading Factor, SF=16
-> 3.84Mcps/16 = 240 K symbols/s -> @ 16QAM -> 240 x 4 = 960 kbps
User 3
-> @ code rate = 3/4 -> 720 kbps

720
User 2
kbps bit rate can be achieved per code -> 10.8 Mbps over 15 codes
User 1
Time and Code multiplexing in HSDPA

1 1 45
1.2 HSXPA overview

RLC ACK/NACK
HARQ
Hybrid-Automatic Repeat Request

Retransmission with soft combining or incremental redundancy Terminated in Node-B
Packet
L1 ACK/NACK
Packet
Retransmission
Retransmission
R99 DCH/DSCH
R5 HS-DSCH
1 1 46
1.2 HSXPA overview

MAC-hs
RLC
is a new MAC entity for controlling HS-DSCH

RLC MAC-d
MAC
MAC-hs PHY Uu
HS-DSCH HS-DSCH FP FP
HS-DSCH FP
MAC-hs is located in the Node-B
L2 L1
L2 L1 Iub/Iur SRNC
PHY UE
Node-B
Flow Control towards Iub Buffering of packet data (MAC-d PDUs) in priority queues Packet Scheduling and priority handling (Time & code domain) H-ARQ termination and handling
L1 H-ARQ using Incremental Redundancy or Chase Combining. The H-ARQ protocol is located in Node-B, i.e. there are only retransmissions via Iub coming from RLC protocol TFRC selection including power control and link adaptation
1 1 47
1.2 HSXPA overview
1.2.4 Terminal categories

HSDPA
will require new terminals to support:
a new protocol stack
new modulation & coding

12
categories have been defined by 3GPP for W-CDMA / FDD

HS-DSCH category 1 2 3 4 5 6 7 8 9 10 11 12
1 1 48
Maximum number Modulation Maximum of HS-DSCH codes supported (QPSK bit rate received and/or 16-QAM) (in Mbps) 5 5 5 5 5 5 10 10 15 15 5 5 Both Both Both Both Both Both Both Both Both Both QPSK only QPSK only 1.2 1.2 1.8 1.8 3.6 3.6 7.2 7.2 10.2 14.4 0.9 1.8
@ MAC-hs Layer
Currently supported by Alcatel-Lucent products
FDD HS-DSCH physical layer categories Rel 8

UEs of categories 21, 22, 23 or 24 also support dual cell operation without simultaneous support of MIMO
HS-DSCH category
Category 6 Category 8 Category 9 Category 10 Category 12 Category 13 Category 14 Category 15 Category 16 Maximum nb Nb of HS- Maximum nb of bits of Supported Supported of HS-DSCH DSCH an HS-DSCH transport modulations modulations codes transport block received within without MIMO simultaneous received block per TTI operation with MIMO a TTI 5 1 7298 10 1 14411 15 1 20251 15 1 27952 5 1 3630 15 1 35280 QPSK, 16QAM, 15 1 42192 64QAM 15 2 23370 QPSK, 16QAM 15 2 27952 QPSK, 16QAM, 1 35280 64QAM 15 2 23370 QPSK, 16QAM QPSK, 16QAM, 1 42192 64QAM 15 2 27952 QPSK, 16QAM 15 2 35280 QPSK, 16QAM, 64QAM 15 2 42192 23370 15 2 QPSK, 16QAM 15 2 27952 15 2 35280 QPSK, 16QAM, 64QAM 15 2 42192
Cat 21 UE supports code rates up to 0.823 with 16QAM Category 18 Cat 23 UE supports Category 19 code rates up to Category 20 0.823 with 64QAM Category 21
Category 22 Category 23 Category 24
1 1 49
Category 17
1.2 HSXPA overview
1.2.5 CQI table

CQI value 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Transport Block Size 137 173 233 317 377 461 650 792 931 1262 1483 1742 2279 2583 3319 3319 3319 3319 3319 3319 3319 3319 3319 3319 3319 3319 3319 3319 3319 3319 Maximum bit Number of Reference power rate (kbps) HS-PDSCH Modulation adjustment 68.5 86.5 116.5 158.5 188.5 230.5 325 396 465.5 631 741.5 871 1139.5 1291.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1659.5 1 1 1 1 1 1 2 2 2 3 3 3 4 4 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15
The
Channel Quality Indicator (CQI) returned by the mobile indicates what transport format it can support at a given instant table corresponds to mobiles of categories 11 & 12 tables exist for other UE categories
This
Similar
1 1 50
1.2 HSXPA overview
1.2.6 Summary of HSDPA key benefits
Adapted to variablethroughput flows
Adapted to bursty traffic (statistical Multiplexing benefit)
Throughputs of : Up to 3.6 Mbps with QPSK Up to 14 Mbps with 16QAM
High Speed Downlink Packet Access

Cost effective Quicker response time Mix of HSDPA and dedicated traffic possible on same carrier
1 1 51
1 UMTS Introduction
1.3 HSUPA basics
HSUPA: 3GPP
High Speed Uplink Packet Access
release 6 feature Also called Enhanced DCH or Enhanced Uplink

Purposes:
Boost uplink data performances in terms of higher throughput, reduced delay and higher capacity Balance uplink traffic performance with downlink HSDPA Mandatory step for VoIP
1 1 52
1.3 HSUPA basics
1.3.1 New Physical Channels
New UL dedicated transport channel: Enhanced dedicated Channel (E-DCH) New UL and DL physical channels for data and signalling
256) 128)
HSUPA UE
1 1 53
1.3 HSUPA basics
1.3.2 MAC-e and MAC-es
DTCH
DCCH
DCCH
DTCH
MAC-d
New MAC-e and MAC-es entities at UE, Node-B and SRNC levels
MAC-d
MAC-es MAC-es / MAC-e MAC

MAC-e
PHY
EDCH FP
TNL TNL TNL
EDCH FP
TNL
PHY
UE
Uu
NodeB
Iub
DRNC
Iur
SRNC
Request Grant Data HSUP A UE

1 1 54
ACK/NACK
1.3 HSUPA basics
1.3.3 Key features
Deployed on top of R99 networks By Software upgrade
Scheduling at Node-B
Shorter TTI 10 or 2ms
HSUPA
for fast retransmissions
HARQ
NB: No adaptive modulation in HSUPA (BPSK as in DCH QPSK is used when SF<4)
1 1 55
1.3 HSUPA basics
1.3.4 HSUPA key feature: H-ARQ

RLC ACK/NACK
H-ARQ
Hybrid-Automatic
Repeat Request
Packet
L1 ACK/NACK
Retransmission with chase combining or incremental redundancy Terminated in Node-B Smaller delay Packet Higher BLER target -> smaller Transmit Power and interference -> Higher capacity
Retransmission
Retransmission
R99 DCH
R6 E-DCH
1 1 56
1.3 HSUPA basics
1.3.5 HSUPA key feature Scheduling
Scheduling
in the Node-B
L3 Resource Allocation
Scheduling
in the Node-B
Data transmission
Not anymore handled by the RNC Whenever the UE stops the transmission or reduces the data rate, the free capacity can be quickly allocated to another UE Algorithm is vendor dependent
Scheduling Info
Scheduling Assignment
R6 E-DCH
1 1 57
1.3 HSUPA basics
1.3.5 HSUPA key feature Scheduling [cont.]
Scheduling
in the Node-B
RoT Maximu m UE 1 allowable noise UE 2 rise
UE 3 UE 2 UE 1
Shared resource is the total Uplink interference eg Rise over Thermal Noise, RoT or interference margin The Node B controls the allocation of this margin
UE 3 UE 2 UE 1
UE 1
Selects the best Transport Format Combination (TFC) for a given UE according to the available interference margin (left over R99) and schedules the UE
DCH services (eg voice and visio) TTI 0 TTI 1 TTI 2 TTI 3
Time
1 1 58
1.3 HSUPA basics
1.3.6 Network elements impacted
Node-B impact: New MAC-e function Scheduling CEM
RNC impact: New MAC-es function Support of higher throughputs
Iub impact: Support of higher UL throughputs
1 1 59
1.3 HSUPA basics
1.3.7 HSUPA UE categories

Mac-e data rates
Theoretical peak bit rate up to 5.76 Mbps 1.46 Mbps capability expected initially
1 1 60
1.3 HSUPA basics
1.3.8 Summary of HSUPA benefits
>
Deployed as an overlay of R99 networks

>
Better usage of the resources (interference)
Software upgrade only
UE Throughputs up to 5.8Mbps
Up to 1.4Mbps in a first step
>
>
30-70% increase in system capacity 50% increase in user packet call throughput
High Speed Uplink Packet Access

>
>
20-55% reduction in end-user packet call delay
New services VoIP, Mobile Gaming, Video Conferencing
UL coverage improvement for high data bit rate

1 1 61
New revenues for operators & better QoS for users
1 UMTS Introduction
1.4 UMTS RNP notations and principles
Objective: to be able to understand the vocabulary and notations* used in this course in regards of UMTS planning
* unfortunately, UMTS RNP notations are not clearly standardized, so that the meaning of a notation can be quite different from one reference to another one.
1 1 62
1.4.1 Notations
Received power and power density
Power [dBm]
Power Density [dBm/Hz]
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
Received (useful) signal Thermal Noise Thermal Noise at receiver Interference intra-cell Interference extra-cell Interference
C (or RSCP) -108.1 N Iintra (Iown) Iextra (Iother;Iinter) I
Ec Nth=-174 -
interference received from transmitters not located in the same cell as the receiver I=Iintra+ Iextra (no Thermal noise at receiver included)
1 1 63
1.4.1 Notations [cont.]
Received power and power density Total received power (Total noise) Total received power (Total noise without useful signal)
Power [dBm] I+N (RSSI) I+N-C
Power Density [dBm/Hz] Io No (Nt)
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)
1 1 64

Ratio in [dB] 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
Ec/Io
Received energy per chip over noise
Ec/No (C/I)*
Received energy per bit over noise Required energy per bit over noise
Eb/No
(Eb/No)req
*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)
1 1 65

Two more interesting ratios! f (or little i)
in [dB]
Comment In a homogenous network (same traffic and user distribution in each cell), f is a constant in uplink. Typical value for macro-cells with omni-directional antennas: 0.55 (in uplink) Very useful UMTS ratio to characterize the moving interference level I compare to the fixed Thermal Noise at receiver level N.
Iextra / Iintra
Noise Rise
(I+N)/N
(Other Cell Interference Factor (OCIF) -> Iextra/Iintra)

1 1 66
1.4.2 Exercise
Surrounding cells
link p U
ed r e si d n o c
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 1 67
1.4.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
[users]
I
[dBm]
I +N
[dBm]
Noise Rise [dB]
Ec/Io
[dB]
Eb/No
[dB]
Comment
1 10 25 100
1 1 68
1 UMTS Introduction
1.5 UMTS RNP tool overview

Objective: to be able to describe briefly the structure of a RNP tool
1 1 69
1.5.1 RNP tool requirements
Digital maps
topographic data (terrain height)
Resolution:

typically 20m for city areas and 50 m for rural areas possibly building and road databases for more accuracy important for interfacing with measurement tools e.g. UTM based on WGS-84 ellipsoid
Coordinates system

morphographic data (clutter type)

Resolution: same as topographic data
Propagation model dialog

e.g. setting Cost-Hata propagation model parameters importing sites (e.g GSM sites) setting site/sector/cell/antenna parameters (Network design parameters)
Note: in UMTS, sector and cell are not equivalent
Site/sector/cell/antenna dialog
1 1 70
1.5.1 RNP tool requirements [cont.]

Link
loss calculation Traffic simulation

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

Coverage
predictions
displaying the results on the map showing the results as numerical tables
Automatic
neighborhood planning Automatic scrambling code planning Interworking with other tools (dimensioning tools, OMC-UR, measurements tools, transmission planning tool...)
1 1 71
1.5.2 Example: 9955 UMTS/GSM RNP tool
9955 screenshot
1 1 72
1.5.3 High-level ACCO overview

Fully
integrated with 9955 Performs the tasks that are tedious & time consuming to perform
Site selection Site placement Antenna tilt & azimuth optimisation Radio feature selection
Allows
a large RNP to be performed in substantially less time with greater consistency and repeatability Broken into two modules:
ACCO Greenfield
Primarily for site placement but also for site selection, tilt azimuth optimisation and radio features selection
Doesnt consider interference
ACCO Optimisation
Does everything except new site placement
Selected as the official ACP tool for AlcatelLucent
1 1 73
1.5.4 Cost benefit optimization

Existing Candidate Sites (in 9955) 9955 ACCO Automatic Cost and Efficiency Analysis
Efficient Implementation 31 sites (60%)
Full Implementation 50 sites
1 1 74
1.5.5 9955 ACCO

Plan in 9955 Improved plans in 9955
Case 1
Other considerations Case 1 Business case 2 Case Budget and cost Business case Case N Expected traffic Budget and cost
Business case Services Expected traffic Budget and cost Radio requirements Services Expected traffic Available technology Radio requirements Services Parameter ranges Available technology Radio requirements etc. Parameter ranges technology Available etc. Parameter ranges etc.
Better plans Very fast processing Cost efficiency analysis Implementation plans Project plans Best budget use Complementary to 9955
Case 2
Case N
1 1 75
1 UMTS Introduction
1.6 RNP process overview

Objective: to be able to briefly describe the RNP Process.
1 1 76
1.6.1 WCDMA RNP process

Radio
Network Dimensioning
Required receive levels for different morphos (based on LKB analysis) Site configuration for different morphos
No. Carriers, Max. Subs / Site, Radio Features, etc.
An indicative site count for the different morphos and areas
Next Step RNP study to confirm site count and locations

1 1 77
1.6.2 Overview
1 1 78
1.6.3 Inputs required

RNP
requires a set of inputs, in addition to those required for the Radio Network Dimensioning stage, including:
Topology, morphology and traffic information Site co-ordinates, heights, tilts, patterns and azimuths.
Morphology
Traffic Maps
Topology
1 1 79
1.6.4 RNP coverage predictions

Objective:
To fine tune the design outputs from stage (1) by reviewing the predicted coverage and quality
Can be assisted through use ACCO (the 9955 automatic optimisation module), that can optimise site selection, antenna heights, tilts, powers, etc
Traffic
loading important for WCDMA
Can have an appreciable impact on the network design (influenced by the user distribution) There are two common approaches for modeling the impact of traffic on the network design, these are:
Fixed Cell Load Analysis: A fixed loads are assumed for the UL and DL (derived from stage (1) of the radio network design process) Load Distribution Analysis: RNP network simulations can be used to randomly distribute mobiles over the design area according to detailed traffic maps and service usage profiles enhanced accuracy
1 1 80
1.6.4 RNP coverage predictions [cont.]

Acceptable
coverage is defined by several requirements that should be satisfied within the design coverage area:
CPICH RSCP (target thresholds derived from stage (1) of the design process)
According to link budget MAPL
CPICH Ec/Io -15 dB (based on field experience) Service Eb/No in DL UE service Eb/No for the target BLER Service Eb/No in UL Node-B service Eb/No for the target BLER HSDPA & HSUPA throughput Soft Handover status (for information purposes)
1 1 81
1.6.5 RNP network simulations

Objective:
To account for:
The dynamic nature of the interactions between users (through iterative power control simulations) and the typically non-uniform distribution of the traffic between sites (defined by the traffic map) Uniform loading assumptions implicit with simple predictions studies
Two
common types of RNP network simulation studies that are performed:

Load Distribution Simulation Studies for estimating the UL and DL loading on a per cell basis (to facilitate enhanced predictions studies) Detailed Simulation Studies to assess the network performance in a more rigorous manner in terms of call failures, hotspot analysis, radio feature evolution, rollout analysis
1 1 82
1.6.6 Key ND RNP steps

Typical
requirements as part of an RNP study include the following types of studies:

Pilot RSCP coverage predictions (always) Pilot Ec/Io quality predictions (almost always) Effective Service Area predictions (sometimes) HSDPA predictions (increasingly common) HSUPA predictions (imminent requirement) Simulations (rarely required)
1 1 83
2 Inputs for Radio Network Planning
1 1 84
2 Inputs for Radio Network Planning

Objective
to be able to describe the UMTS RNP inputs with regard to frequency spectrum, traffic parameters, equipment parameters and radio network requirements.
1 1 85
2.1.1 UMTS FDD frequency spectrum

Objective:
to be able to describe the UMTS FDD frequency parameters defined by the 3GPP
1 1 86
2.1.1.1 Frequency spectrum

Frequency spectrum (UMTS FDD mode)
UL: 1920 MHz 1980 MHz DL: 2110 MHz 2170 MHz Duplex spacing: 190 MHz
1920-1980
2110-2170
1 1 87
2.1.1.2 Carrier spacing

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

One operator gets typically 23 frequencies (carriers) So typically 46 licenses per country as a maximum
Required
bandwidth: 4.7MHz
The chip rate is 3.84Mchip/s, therefore at least 3.84MHz bandwidth are needed to avoid 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
1 1 88
2.1.1.3 Frequency channel numbering

UTRA Absolute Radio Frequency Channel Number (UARFCN)
UARFCN formula (3GPP 25.101 and 25.104):
UARFCNUplink/Downlink = 5 f Center Uplink/Downlink [MHz] with 0.0MHz f Center Uplink/Downlink 3276.6MHz
UARFCN is integer:
0 <= UARFCN <= 16383
1 1 89
2.1.1.4 Center frequency
Center Frequency fcenter

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

1922.4MHz <= fcenter <= 1977.6MHz 9612 <= UARFCN Uplink <= 9888 2112.4MHz <= fcenter <= 2167.6MHz 10562 <= UARFCN Downlink <= 10838
Downlink (2110Mhz-2170MHz)

1 1 90
2.1.1.5 Further comments

Frequency adjustment
If an overlap between frequency bands belonging to same operator is set, guard band between different operators will increase. This feature can be used to enlarge the guard band between frequency blocks belonging different operators and prevent dead zones.
Example: 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 0.3 MHz overlap
Operator 1 1920
0.6 MHz additional guard band
Operator 2 1940
Frequency coordination at country borders ( see Appendix)

1 1 91
2.1.2 UMTS traffic parameters (UMTS traffic map)
Objective: to be able to describe the method to create a traffic map
1 1 92
2.1.2.1 Step 1: Terminal parameters
1 1 93
2.1.2.2 Step 2: Service parameters
1 1 94
2.1.2.2 Step 2: Service parameters [cont.]
1 1 95
2.1.2.3 Step 3: User profile parameters

Traffic Density User Profile Service (see Step2) PS 384 PS 64 Speech 12.2 Speech 12.2 CS64 City user PS64 PS128 PS384 Standard user same as City User without PS384 service Mobile Phone Outdoor 0.2 40 200 Terminal (see Step1) PDA Deep Indoor PDA Deep Indoor Mobile phone Deep Indoor Calls/ hour 1 1 1 1 1 Duration (sec) 115.2 72 72
(Examples)
Surfing user Videocall user Phonecall user
Volume (Kb/sec) UL 8 5 DL 60 20 -
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.
1 1 96
2.1.2.4 Step 4: Environment class parameters

User
profiles have been used to describe single user types. Environment classes are used to distribute and quantify these user profiles on the planning area.
Environment class* (Examples) Dense Urban Urban Suburban Rural Geographical density (users/km2) User profiles ( see Step 3) city user city user city user standard user low traffic 1000 750 50 10 medium traffic 3000 1500 250 20 high traffic 6000 3000 500 40
*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)
1 1 97
2.1.2.5 Step 5: Traffic map definition

Mapping
of Environment Classes (see Step 4) on a map: Example with 4 environment classes: Dense Urban, Urban, Suburban, Rural Rural
Map Traffic map
Suburban
Dense Urban Planning Area Resolution: Urban 20m100m (also called Focus Area) 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)
1 1 98
2.1.3 UMTS terminal, NodeB and antenna overview
Objective: to be able to describe briefly the main characteristics of the UMTS radio equipment (UE, NodeB and antenna)
1 1 99
2.1.3.1 UE characteristics
According
to 3GPP 25.101 (Release 1999):

1: 2: 3: 4: (+33 (+27 (+24 (+21 +1/-3)dBm +1/-3)dBm +1/-3)dBm 2)dBm
UE power classes at antenna connector*: (see

Power class Power class Power class Power class
UE minimum output power: <-50dBm

According
to UE manufacturers:
UE Noise Figure: 8dB (typically) UE internal losses + UE antenna gain = 0dB

What
is EIRP for a UE of power class 4?

* the notation means e.g. for class 1: - Maximum output power: +33dBm - Tolerance: +1dBm/-3dBm
Answer: UE EIRP=UE TX Power+ UE Antenna Gain - UE Internal Loss=21dBm + 0 dB = 21 d

1 1 100
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 UMTS Iub Iub RNC
UE
UMTS
The Node B is in charge of radio transmission handling (with W-CDMA method)
UE
1 1 101
2.1.3.2 Alcatel-Lucent Node B [cont.]

Sector 2 Sector 1 RF Feeders Sector 3
Power supply: - 48 V DC AC main
BTS RF block
TX amplification (PA), coupling Interco module Rx signal
Tx signal
RNC
Iub
Digital shelf
Network interface Call processing Signal processing Frequency up/down conversion External alarms
1 1 102

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

1 1 103

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

1 1 104
2.1.3.3 CEM, iCEM and the Base Band Unit
iCEM128
H-BBU H-BBU
iCEM128
H-BBU D-BBU
iCEM (64/128) is HSDPA hardware ready but needs a specific software One BBU can not support both Standard (R99/R4) and HSDPA (R5)services
iCEM64
H-BBU
12.2/12.2 Speech
iCEM Capacity
PS 32/32 32 64 PS 64/64 16 32 PS 64/128 16 32 PS 64/384 8 16
iCEM64
D-BBU
iCEM64 iCEM128
64 128
CEM
D-BBU D-BBU
H-BBU D-BBU
HSDPA dedicated DCH dedicated
1 1 105
2.1.3.4 iCEM: HSDPA Scalable Configuration
iCEM128
H-BBU H-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)
iCEM128
H-BBU D-BBU
iCEM64
H-BBU
iCEM64
D-BBU
1 1 106
2.1.3.5 HSDPA solution

CEM 128 H-BBU Cell#1 H-BBU Cell#2 CEM 128 H-BBU Cell#3 D-BBU Cell#4 CEM alpha D-BBU Cell#5 D-BBU Cell#6
Network Interface
GPSAM TRM 1
f1 RX (M+D) f1 RX , , (M+D)
f1 f2 RX Main D PA HSDPA Cell #1, f1 Standard Cell #4, f2 HSDPA Cell #2, f1 Standard Cell #5, f2 HSDPA Cell #3, f1 Standard Cell #6, f2
f1, f2 TX driver
f1 f2 TX , ,
f1 f2 RX Div. f1 f2 RX Main
CCM
PA
TRM 2
f1, f2 TX driver
f1 f2 TX , , f2 RX , , (M+D)
f1 f2 RX Div. f1 f2 RX Main
D PA f1 f2 RX Div. D
f2 RX (M+D)
1 1 107
2.1.3.6 UMTS antennas
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
1 1 108
2.1.3.6 UMTS antennas [cont.]
Antenna parameters are key parameters which can be tuned to decrease interference in critical zones, especially:
Antenna downtilt
increasing the antenna downtilt of an interfering cell can optimize the RF conditions 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 by re-directing the beam direction of the interfering cell azimuth modifications of 10-20 compared to the previous value do not make sense
Antenna azimuth

Note: Azimuth/downtilt modifications can be restricted or even forbidden due to antenna system installation constraints (especially the constraints for UMTS/GSM co-location)
1 1 109
2.1.4 Radio network requirements
Objective: to be able to understand the parameters, which define the UMTS radio network requirements in terms of coverage, traffic and quality of service
1 1 110
2.1.4.1 Definition of radio network requirements

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

(CPICH Ec/Io)required=-15dB (Alcatel-Lucent value coming from simulations and field measurements) Required coverage probability for CPICH Ec/Io: e.g. Average probability {CPICH Ec/Io > (CPICH Ec/Io)req} > 95% (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) All Rights Reserved Alcatel-Lucent 2009
1 1 111
2.1.4.1 Definition of radio network requirements [cont.]

UL and DL service coverage
(Eb/No)reqspecific value for each service and for each direction (UL/DL), 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).
1 1 112
2.1.4.1 Definition of radio network requirements [cont.]

CPICH RSCP coverage (optional)
(CPICH RSCP)required: it can be defined, if the maximum allowed path loss is determined by calculating a link budget and taking into account the CPICH output power (if no traffic mix is available, the link budget would base on the limiting service) Required coverage probability for CPICH RSCP e.g. Average probability {CPICH RSCP > (CPICH RSCP)req}>95% (To guarantee an average reliability, that the minimum level is fulfilled in the covered area)
CPICH RSCP prediction is not mandatory, but:

it can be a help to guarantee a certain level of indoor coverage from outdoor cells, taking into account different indoor losses for different areas. CPICH RSCP can easily be measured using a 3G scanner.
1 1 113
3 WCDMA RNP Predictions
1 1 114
3.1 CPICH RSCP predictions

Objective: Validate analytical LKB results by RNP Steps:
1) Determine CPICH RSCP Thresholds
UL harmonised link budget
2) Set Cell Parameters 3) Create Prediction

Set Prediction Conditions Set RSCP thresholds
1 1 115
3.1.1 Determine CPICH RSCP thresholds

2 main approaches:
Use Harmonised ALU link budget to derive fixed UL cell load MAPL
CPICH RSCP Level = [CPICH Tx Power + Antenna Gain Feeder losses] MAPL
Determine whether a DL limitation occurs before UL cell load limit
1 1 116
3.1.2 Set cell parameters

The
only cell parameter of importance for CPICH RSCP predictions is the Pilot Power
Use
the 9955 v6.x Cell Inputs Calculator calculator to determine correct cell inputs
Select the PA type, number of carriers, DL power loading, etc
Remember: The most important input is the Pilot Power

1 1 117
3.1.3 Create prediction

Select Coverage by Signal Level
Enter the CPICH RSCP Thresholds
Note: Ensure that both Shadowing taken into account and Indoor Coverage are not selected This is important because both shadowing margins and penetrations should already be accounted for in the MAPL calculations
1 1 118
3.2 Pilot Ec/Io predictions

Objective: Check the quality of the network by RNP Steps:
1) 2) 3) 4) Set Cell Parameters Define Penetration Margins (optional) Set Terminal Parameters Create Prediction
Set Prediction Conditions Set RSCP thresholds
1 1 119

The
cell parameters that impact the Pilot Ec/Io predictions are:
Pilot Power Total Power
Use
Select the PA type, number of carriers, DL power loading, etc Key inputs being the DL power loading assumptions
Unloaded (overheads only) => expect ~-8dB Ec/Io % DL power load, e.g. 100% => expect ~-15dB Ec/Io % available DL traffic power loading
Remember: The most important inputs are the Pilot Power and the Total Power
1 1 120
3.2.2 Define penetration margins (optional)

In most cases, the penetration margin will have a minimal impact on the Ec/Io predictions (exception being, for example, rural areas)
Generally the network will be interference limited Penetration margin impacts both Ec and Io in the same way (thus leaving the Ec/Io unchanged)
Can define per clutter Indoor Losses
1 1 121
3.2.3 Set terminal parameters

Only input that matters here is the Noise Figure
1 1 122

Select Pilot Reception Analysis
Define thresholds -15 to -8dB
Note: If considering shadowing for Ec/Io 9955 will use the Ec/Io std dev defined in the clutter properties window (should be set to 3dB) If Ec/Io reliability is a requirement then select shadowing option Select indoor losses if considering noise limited coverage
1 1 123
3.3 Effective service area predictions

Objective: Identify coverage areas for each service Steps:
1) 2) 3) 4) 5) 6) Set Transmitter Properties Set Cell Parameters Define Penetration Margins, Orthogonality & Shadowing Set Terminal Characteristics Define Service Parameters Create Prediction
1 1 124
3.3.1 Set transmitter properties

In the transmitters properties tab window:
Set the UL soft handover gain to 0 dB Activate MRC
1 1 125

The
cell parameters that impact the Service Area predictions are:
Max Power, Pilot Power, SCH Power, other CCH, Total Power, DL HSUPA Power
Use
1 1 126
3.3.3 Define pen. margins, orthog. & shad.

Like Pilot Ec/Io predictions, in most cases the penetration margin will have a minimal impact on the Eb/Nt predictions (exception being, for example, rural areas) Only used if indoor losses checked in prediction options
In the field it has been observed that the standard deviation of Eb/Nt is much less than that of Eb alone (i.e. is much less than the standard deviation of the RSCP level, (in the order of ~3dB) This is only used if shadowing is checked in the effective service area prediction options The recommended orthogonality factor is 0.6
1 1 127
3.3.4 Set terminal characteristics
Set Max Power to 21dBm for all but HSDPA UEs
No Gains or Losses
Set NF to 8dB
1 1 128
3.3.5 Define service parameters
Check the default Max TCH Power settings
Set the appropriate Body Loss Define the UL and DL Eb/Nt values for each service
1 1 129
Select the Effective Service Area (for all services) Alternatively the UL and DL effective service area can be predicted separately Note: If considering shadowing for service area predictions 9955 will use the Eb/Nt std. dev. defined in the clutter properties window (should be set to 3dB) If Eb/Nt reliability is a requirement then select shadowing option It is recommended to always select indoor losses if considering indoor coverage
1 1 130
3.4 HSDPA & HSUPA predictions

Objective: Demonstrate the HSPA throughputs over the area Steps:
1) 2) 3) 4) 5) 6) 7) 8) Set Transmitter Properties Set Cell Parameters Set Reception Equipment Parameters Set Terminal Characteristics Define Mobility Parameters Define Service Parameters Define HSPA Radio Bearers Create Prediction
1 1 131
3.4.1 Set transmitter properties

Set Nt computation to be Without Useful Signal Set CQI to be Based on HS-PDSCH Quality
1 1 132
3.4.2 Set DL power cell parameters 1/3

The
cell parameters that impact the HSDPA predictions are:
Max Power, Pilot Power, SCH Power, other CCH, Total Power, Available HSDPA Power, DL HSUPA Power
Use
1 1 133
3.4.3 Set cell parameters 2/3

DCH
Power Loading
% of the available traffic channel power DCH Power Loading + HSDPA Power Loading <= 100%
HSDPA
Power Loading
% of the available traffic channel power DCH Power Loading + HSDPA Power Loading <= 100%
Adjacent
DCH Power Loading
This is the loading of cells adjacent to the current cell Recommended value = 100% Make this less than 100% only when you wish to assume that the peak DCH loading is not simultaneous everywhere at the same time.)
Adjacent
HSDPA Power Loading
This is the loading of cells adjacent to the current cell This is particularly relevant when considering HSDPA performances, where you may wish to assume that the peak rates are not simultaneous everywhere at the same time Recommended value = 50%
1 1 134
3.4.4 Set UL cell parameters 3/3

The
cell parameters that impact the HSUPA predictions are:
Max UL Load Factor, UL Load Factor, UL Load Factor Due to HSUPA, UL Reuse Factor
Max UL Load Factor 50% UL Load Factor 50% UL Load Factor Due to HSUPA 0% UL Reuse Factor 1.8
Use
the 9955 v6.x Cell Inputs Calculator calculator to determine correct cell inputs:
Define UL Cell Load due to DCH traffic UL Cell Load Enter the UL Cell Load due to HSUPA traffic Define the Max UL Cell Load >= DCH + HSUPA
Total UL Cell Load HSUPA UL Cell Load Fraction 50% 25%
The recommended UL Reuse Factor is 1.8

1 1 135
3.4.5 Set reception equipment parameters: HSDPA

Note: The HSDPA Quality Graphs should not be defined
Must update the default CQI tables for each mobility model you want to use from WCDMA 9955 v6.x HSDPA Inputs
1 1 136
3.4.6 Set reception equipment parameters: HSUPA

Note: The HSUPA Quality Graphs should not be defined
Must update the default Bearer to Ec/Nt mappings for each mobility model you want to use from the file WCDMA 9955 v6.x HSUPA Inputs (the HSUPA Extended sheet for a 6.7dB SIR target)
1 1 137
3.4.7 Set terminal characteristics

Select the reception equipment for which the HSPA parameters have been defined Enable HSDPA and/or HSUPA and define UE categories
1 1 138
3.4.8 Define mobility parameters

The
new parameter for HSDPA is the HS-SCCH Ec/Nt target
This is used by 9955 to define the power used for the HS-SCCH based on the radio conditions This power is deduced from the HSDPA power specified in the Transmitters/Cells table
The
HS-SCCH Ec/Nt target value recommended is -13dB based on the Alcatel-Lucent calculation method
1 1 139
3.4.9 Define service parameters

Select HSDPA and/or HSUPA for the desired HSPA services
1 1 140
3.4.10 Define HSPA radio bearers

Both the HSUPA and HSDPA radio bearer tables should be updated with the values from the attached excel files
The HSDPA table is updated to account for a 10% BLER The HSUPA table is updated to make some corrections as well as to extend the number of bearer indicies from 24 to 101
HSUPA inputs can be found in WCDMA 9955 v6.x HSUPA Inputs
HSDPA inputs can be found in WCDMA 9955 v6.x HSDPA Inputs
1 1 141
3.4.11 Create prediction: HSDPA
Select RLC Peak Rates (kbps)
Note: Do not select shadowing Select indoor losses if considering noise limited coverage
1 1 142
3.4.12 Create prediction: HSUPA

Selecting Single User assumes that a single user takes the entire UL HSUPA cell load limit Selecting Shared means that the HSUPA cell load limit is shared amongst the number of user defined for HSUPA in the cell properties sheet Number of HSUPA Users Select RLC Peak Rates (kbps)
Note: Do not select shadowing Select indoor losses if considering noise limited coverage
1 1 143
4 WCDMA Traffic Simulations
1 1 144
4 WCDMA Traffic Simulations
4.1 UMTS traffic simulations
Objective: to be able to check that the network capacity is in line with the traffic demand by performing traffic simulations with a RNP tool
1 1 145
4.1.1 Why do we need traffic simulations?

Can the capacity cope with the demand in UL and in DL?
Traffic Map Traffic demand modeling
Site map Network capacity modeling
it is necessary to calculate the UL/DL network capacity to check that it is in line with the traffic demand.
1 1 146
4.1.1 Why do we need traffic simulations? [cont.]

How to calculate the UL/DL network capacity?
Problem: the capacity depends on the user distribution (at least in DL)
User distribution 1 NodeB Cell Cell User distribution 2 NodeB
384k
12.2k
Suburban environme nt class
12.2k
384k (in outage)
Network capacity 1 > Network capacity 2 (for the same traffic map)
Solution: a traffic simulation can be performed (= a snapshot of UMTS network at a given time, one possible scenario among infinite number of scenarii).
1 1 147
4.1.2 How to perform a traffic simulation?

Step 1: enter the traffic simulation inputs
Traffic simulation inputs
typical value 75% 100 3% 0.6
Comment
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.85 for Pedestrian A
Traffic simulation parameters (only used for traffic simulations) Maximum UL load factor Number of iterations Convergence criteria Orthogonality factor (per clutter)
Traffic map Propagation model parameters Network design parameters
1 1 148
4.1.2 How to perform a traffic simulation? [cont.]

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

Step 3: the RNP tool checks the UL/DL service availability for each user
Used inputs: user distribution (see Step1) +Propagation model parameters+Network design parameters+ traffic simulations parameters UL/DL link loss calculations are performed iteratively due to (fast) power control mechanisms in order to get:
needed UE TX power for each UE needed NodeB TX power for each cell
Each of the following conditions is checked: if one of them is not fulfilled, the concerned user will be ejected (service blocked):
Conditions in UL: 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 1 150
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.1.3 Traffic simulation outputs

DL (power) load factor per cell UL load factor per cell Percentage of soft handover Percentage of blocked service requests and reasons for blocking (ejection causes)
Example of ejection causes with 9955 RNP tool: the signal quality is not sufficient: on downlink:
not enough CPICH quality: Ec/Io<(Ec/Io)min not enough TX power for one traffic channel(tch): Ptch > Ptch max not enough TX power for one UE (mob): Pmob > Pmob max 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)
on uplink: the network is saturated:

1 1 151
4.1.4 Limitation of traffic simulation

Limitation:
a simulation is only based on one user distribution another simulation based on the same traffic map but on a different user distribution can give different results for DL/UL service availabilities
Solution:
to average the results of several simulations (statistical effect) to be closer to the reality
Other
interest of traffic simulation
Some traffic simulation ouputs (that are DL (power) and UL load factors per cell) can be used as inputs for CPICH Ec/Io and DL/UL service coverage predictions (see 1.4.4).
1 1 152
4.1.4 Limitation of traffic simulation
1 1 153
5 Link Budget (in Uplink)
1 1 154

Objective: to be able to calculate the cell range for a given service by doing a link budget in UL. to be able to describe the typical UMTS radio effects in UL.
1 1 155
5.2 Main characteristics

Mobiles
UPLINK Analysis
transmit on same frequency simultaneously Other UEs interfere System is interference limited to Power Control instructions, Mobiles adjust their power to:
Achieve target C/I Overcome Pathloss (impacted by distance) Overcome Interference (impacted by Traffic)
Interference Perceived by user 1 Total Interference @ Node-B KTB
Asynchronous
According
Transmit Power P1
Interference
(Iintra and Iextra) is independent of UEs locations
Transmit Power Pi Transmit Power P3
Transmit Power P2
1 1 156
5.3 Main concepts
UPLINK Analysis
Link
Budget is performed for one mobile located at cell edge (for each service) transmitting at max power interference (Intra-cell and extra-cell) perceived by this UE is calculated @ Node-B, including the entire traffic mix (Traffic Model) is a shared resource
The
Interference
UPLINK Analysis is an MAPL analysis
MAPL Max UE transmit Power Required Received Signal cell radius
1 1 157
5.4 Link budget
UPLINK Analysis
UL link budget elaborated for user of service k at cell edge transmitting at maximum power
Uplink Path
Transmit Power
Losses and Margins
Gains
Receiver Sensitivity
Interference
= MAPL
Maximu m Allowable Path Loss
UE Transmit power (21 or 24dBm)
Derived from Eb/No Penetration Loss Node-B Antenna Gain performance (outdoor/indoor) UE Antenna Gain s Shadowing margin (including SHO Gain) Fast Fading Margin
1 1 158
Feeder losses
Interference Margin (depends on cell load)
Body Loss
5.5 Example for one service

Dense Urban
Service Bit Rate kbps Target Eb/No dB Target C/I dB Node-B Noise Figure dB Speech 12.2 4.3 -20.7 2.5 -126.3 18 0.4 0.4 3 0 95% 8.0 8.6 4.0 1.7 20 65% 4.6 4.5 21 0 131.1 0.63 -80.5 -89.1 130
Used for sensitivity calculation Equipment dependent Calculated from above figures
Node-B Sensitivity dBm Antenna Gain Cable & Connector Losses Cable & Connector Losses with TMA Body Loss Additional Losses Cell Area Coverage Probability Outdoor Shadowing Standard Deviation Outdoor Shadowing Margin SHO Gain Fast Fading Margin Penetration Margin Cell Load Noise Rise Interference Margin dBi dB dB dB dB % dB dB dB dB dB % dB dB
UE Max Transmit Power dBm UE Antenna Gain dBi MAPL without TMA dB Cell Range without TMA km RNP Design Level (CPICH RSCP) dBm Acceptance Level (CPICH RSCP) dBm Nsites without TMA Sites
1 1 159
5.6 Eb/No and C/I

Eb/No Relation with C/I
C/I
Despreading PG =
ChipRate UserBitRate
Decoder
Eb/No
(C/I)
target
= (Eb/No) target - Processing Gain
(in dB)
Eb/No target depends on: Target quality expressed in BLER Radio bearer service (bit rate, coding) Multipath channel considered and mobile speed (eg. VehA 3km/h, VehA 50km/h)
Radio features (RxDiv on UL, TxDiv on DL,) Derived from link level simulations and equipment measurements
1 1 160
5.7 Receiver sensitivity
Receiver
Sensitivity Minimum required signal level to reach a given quality (C/I target) when facing only thermal noise in dB Reference Sensitivity = (C/I) k+NF + 10log(NthW) in dBm
and (C/I) k= (Eb/N0)k - PG
= NF +10log(Nth)+ (Eb/N0)k + 10log(Rk)

Service dependent
Where: Nth Thermal Noise density, 10log(Nth) =-174 dBm/Hz (Eb/N0)k : Service k target Eb/No Rk: Service k bit rate NF: Node-B Noise figure in dB
1 1 161
5.8 Exercise
Compute Node-B sensitivity in Veh A 3km/h

for speech 12.2kbps @ 1% BLER For CS64 @ 0.5% BLER
1 1 162
5.9 Exercise
Compute Node-B sensitivity in Veh A 3km/h

for speech 12.2kbps @ 1% BLER For CS64 @ 0.5% BLER
Example of equipment parameter values:

Typical Node-B Noise Figure: 2.5dB @ 2GHz Eb/No figures: 4.9 dB for speech, 3.0dB for CS64
1 1 163

Dense Urban
Typical gain of Tri-sectored antenna, depends on frequency band Depends on feeder type and length an frequency band
3dB body loss when speech usage (UE near head), 0dB boldy loss when data usage
For any additional losses that could be introduced (eg diplexer)
1 1 164
5.10 Example for one service [cont.]

Dense Urban
1 1 165
Depends on UE Class
5.11 UE transmit power

UE transmit power
Depends on UE power class Typically 21 or 24dBm output power with 0dBi antenna gain As far as one type of 21dBm terminal is offered by the operator, the network should be dimensioned for 21dBm output power Even if 24dBm UEs are used, 21dBm should be considered for speech (network parameter limiting the transmit power for speech to 21dBm) but 24dBm for other data services.
1 1 166

Dense Urban
Depends on depth of coverage (e.g. deep indoor, indoor daylight, outdoor). Also accounts for the indoor shadowing margin A single shadowing standard deviation is considered
1 1 167
5.13 Penetration margin

Penetration margin
Depends on indoor coverage level (deep indoor, indoor daylight, outdoor) Defined as a mean value + shadowing margin Typical mean + shadowing margin values @ 2GHz:
Dense urban: 20dB Urban: 17dB Suburban: 14dB Incar: 8dB
1 1 168
5.13 Penetration margin [cont.]

Impact of frequency on Penetration margin
2dB lower penetration margins are considered at 850/900MHz
Penetration margins depend on wall materials Some measurements showed around 3dB lower penetration margins at 900MHz vs 2GHz
Isle of Man measurements

1 1 169
NIST measurements

Dense Urban
Cell area coverage probability different from cell edge coverage probability
Shadowing margin due to the outdoor shadowing standard deviation (excluding the SHO gain) Soft Handoff Gain that is achievable for the given shadowing standard deviation
1 1 170
5.15 Shadowing margin

Shadowing Shadowing:
margin
Slow fading signal level variations due to obstacles Modelled (in dB) as a Gaussian variable with zero-mean and standard deviation depending on the environment
Impact
on link budget :
Take a margin to ensure the received signal is well received (above required sensitivity) with a given probability (e.g. in 95% of the cell) Computation as in GSM. However, in UMTS, a mobile at cell edge is likely to be in soft-handover (SHO). In that case, the best-received signal will be considered. So there is a SHO gain: it is more unlikely to have a large attenuation for all links at the same time than for only one link.
1 1 171
5.15 Shadowing margin [cont.]
Shadowing margin including SHO gain:

Depends on
Shadowing standard deviation Area coverage probability Pathloss exponent K2 (Hata: K1+K2log R) Number of SHO legs Correlation between shadowing of different legs
Same carrier
BS1
BS2
Area coverage probability
UL Shadowing margin (dB) UL Shadowing margin (dB) (no SHO) (SHO, 2 legs) =6 =8 = 12 =6 =8 = 12
5.9 3.3 8.7 5.4 14.6 10.0 3.1 0.6 4.8 2.1 8.5 6.4
95 % 90 %
1 1 172
Fast fading margin Also known as Power Control Headroom
1 1 173
5.17 Fast fading margin

Fast
Fading (Rayleigh) margin Fast fading:

Fast fading signal level variations due to multi-paths (with different delays and amplitudes) Modelled by superposition of mutiple paths with Rayleigh distribution
UMTS
Fast Power control:
The UMTS system tries to fight against fast fading with fast power control (every 0.666ms) When the mobile transmits at its maximum power, it will not be able to compensate for fast fading due to this power limitation Power control is not anymore efficient at cell edge: the performance at cell edge becomes close to the one without power control
1 1 174

Received Power at Node-B (dBm)
5.17 Fast fading margin [cont.]
Impact of power control:

Fight the fading dips
0 1000 2000 3000
Slot Number (0,666 ms)
25
20
Fast fading samples (dB) Transmit power (dBm)
For slow-moving mobiles, Power control is efficient and will compensate the fading
15
Power (dBm) Fast fading values (dB)
10
-5
-10
-15
-20 0 1000 2000 3000
Slot Number (0,666 ms)
1 1 175
Impact on link budget:

Sensitivity was calculated for Eb/No with power control A margin must be considered to compensate power control performance degradation at cell edge : this is the fast fading margin also sometimes called Power Control headroom
Eb Eb Fast_fadin g_margin = N N 0 PC off 0 PC on

Note that macrodiversity due to soft handoff at cell edge decreases the fast fading margin (less received power variation due to selection combining of the different links involved in SHO)
1 1 176
Depends on:
1 0,1 BLER 0,01 0,001 0,0001 2 3 4 5 6 7 8 Required Eb/No (dB)
Morpho-structure
Without power control With power control
Channel model (Vehicular, Pedestrian) Speed BLER service target
FAST FADING MARGIN (DB) FOR SEVERAL TARGET BLER 10-1 10-2 1.7 10-3 2.5 10-4 3.3
VEHICULAR A 3KM/H
For For medium medium to to high high speeds speeds the the margin margin is is equal equal to to zero zero because because the the power power control control is is no no more more efficient efficient
(DENSE URBAN, URBAN) VEHICULAR A 50 KM/H (RURAL) OR 120KM/H
0.6
1 1 177

Dense Urban
The sensitivity is calculated for noise level only. A margin must be considered for interference above noise: interference margin For a fixed cell load of 65%, the noise rise is 4.6dB Here a fixed cell load approach is considered. An iterative cell load approach can alternatively be considered i.e. computing the cell load corresponding the traffic mix captured within the cell The cell load contribution of the considered service is subtracted from the noise rise (in this case the contribution is very small)
1 1 178
5.19 Cell load and noise rise
Noise Rise (dB)
Cell load and Noise rise By definition, cell load and total interference rise (noise rise) are linked: Itotal itot_ dB = 10 log N W = 10 log (1 xUL ) o where Itotal is the total received power at the node B (including the useful signal Ck ) The interference rise includes 30 the useful signal 25 -> it is not the noise rise 20 perceived by a user!
15 10 5 0 0 10 20 30 40 50 60 70 80 90 100 50% cell load 3dB Noise Rise
Cell Load (%)
1 1 179
5.20 Interference margin
The interference rise perceived by a user of service k to be added to the MAPL calculation is then equal to :
Itotal Ck Itotal Itotal i0 dB = 10 log = 10 log 10 log N oW No W Itotal Ck C = 10 log(1 xUL ) 10 log 1 + I k
Numerical
iodB = itot _ dB k
UL cell load, depend on number of users in the cell
Example for a PS 128 user with -12dB target C/I in a cell loaded at 50%: i = 3dB - 0.2dB = 2.8 dB
k is negligible for low data rate services, but significant for high data rate services!
1 1 180

Dense Urban
The cell range depends on the propagation model
COST-231 Propagation Model Frequency Node-B Antenna Height UE Antenna Height Morpho Correction Factor UE Correction Factor K1 K2 1920 MHz 25.0 m 1.5 m 0 -0.0009 dB 138.3 dB 35.7 dB
1 1 181
5.22 Propagation model
Cell range calculation assuming a Hata-like model for the attenuation MAPL = K1+K2 log (R) Where: K1: 1km path loss K2: Path loss exponent Use the correction factors corresponding to the project country/towns (calibration campaign)
1 1 182
5.23 Extension to multi-service

Dense Urban
Service Bit Rate kbps Target Eb/No dB Target C/I dB Node-B Noise Figure dB Speech 12.2 4.3 -20.7 2.5 -126.3 18 0.4 0.4 3 0 95% 8.0 8.6 4.0 1.7 20 65% 4.6 4.5 21 0 131.1 0.63 -80.5 -89.1 130 CS64 64 1.5 -16.3 2.5 -121.9 18 0.4 0.4 0 0 95% 8.0 8.6 4.0 2 20 65% 4.6 4.5 21 0 129.4 0.57 -78.8 -87.5 161 PS64 64 1.4 -16.4 2.5 -122.0 18 0.4 0.4 0 0 95% 8.0 8.6 4.0 1.7 20 65% 4.6 4.5 21 0 129.8 0.58 -79.2 -87.9 153 PS64 & HSDPA 64 2.3 -15.5 2.5 -121.1 18 0.4 0.4 0 0 95% 8.0 8.6 4.0 1.7 20 65% 4.6 4.4 24 0 131.9 0.66 -81.3 -90.0 117
Different bit rates Different Eb/Nos
Different sensitivities Total interference calculated for all the subs and services Different levels of interference margin Different MAPL and cell ranges: the most constraining offered service will define the cell range
1 1 183
5.23 Extension to multi-service [cont.]

Cell Range in multiservice
Depends on the bit rate to be guaranteed at cell edge Generally 64 or 128 kbps on uplink 384 kbps can be offered in the cell with bit rate downgrade at cell edge
So the 384 kbps cell range should not be considered as the limiting cell range unless the operator explicitely requires 384kbps at cell edge
Consider the most limiting service to derive the cell range

e.g. for the previous link budget example
the CS64 service is the limiting one
1 1 184
5.24 Impact of TMA

TMA
also called Mast Head Amplifier (MHA)
Antenna
Vertical Polarisation
Impact
on link budget
Duplexer LNA Duplexer
Jumper Cable
Dual TMA
Duplexer LNA Duplexer
Slightly Reduce the global Noise Figure Compensate the cable losses
0.4dB insertion losses
Usage
Feeder
recommended for UL coverage-limited scenarios
TX / RX
Jumper Cable
TXdiv / RXdiv
Node-B
1 1 185
5.24 Impact of TMA [cont.]
Friis formula to compute the overall noise figure of the receiver chain with TMA:
Typical gain on uplink link budget (Macro site):

2.7dB gain for sites with 3dB cable losses 3.5 dB gain for sites with 4dB cable losses
noverall = nTMA +
nelement = 10
n feeder 1 gTMA
n 1 + Node B gTMA g feeder

Gelement 10
NFelement 10
g element = 10
With
and
Typical gain on uplink link budget (RRH site):

0.3dB gain for sites with 0.4dB cable losses Note: TMA should not be considered for RRH sites
Where NFfeeder =-Gfeeder =Feeder Losses Typical TMA characteristics: NFTMA =2 dB dB GTMA =12
Insertion losses = 0.4dB
1 1 186
5.24 Impact of TMA [cont.]

Dense Urban
Service Bit Rate kbps Target Eb/No dB Target C/I dB Node-B Noise Figure Node-B Noise Figure with TMA dB dB Speech 12.2 4.3 -20.7 2.5 2.4 -126.3 -126.4 18 3.0 0.4 3 0 95% 8.0 8.6 4.0 1.7 20 65% 4.6 4.5 21 0 128.5 0.53 182 131.1 0.63 129 CS64 64 1.5 -16.3 2.5 2.4 -121.9 -122.0 18 3 0.4 0 0 95% 8.0 8.6 4.0 2 20 65% 4.6 4.5 21 0 126.8 0.48 225 129.5 0.57 159 PS64 64 1.4 -16.4 2.5 2.4 -122.0 -122.1 18 3 0.4 0 0 95% 8.0 8.6 4.0 1.7 20 65% 4.6 4.5 21 0 127.2 0.49 214 129.9 0.58 151 PS64 & HSDPA 64 2.3 -15.5 2.5 2.4 -121.1 -121.2 18 3 0.4 0 0 95% 8.0 8.6 4.0 1.7 20 65% 4.6 4.4 24 0 129.3 0.56 163 132.0 0.67 116
Reduced Noise figure (based on Friis formula) No cable losses but 0.4dB TMA insertion losses
Node-B Sensitivity dBm Node-B Sensitivity with TMA dBm Antenna Gain Cable & Connector Losses Cable & Connector Losses with TMA Body Loss Additional Losses Cell Area Coverage Probability Outdoor Shadowing Standard Deviation Outdoor Shadowing Margin SHO Gain Fast Fading Margin Penetration Margin Cell Load Noise Rise Interference Margin dBi dB dB dB dB % dB dB dB dB dB % dB dB
Around 2.7dB gain on MAPL for sites with 3dB cable losses
UE Max Transmit Power dBm UE Antenna Gain dBi MAPL without TMA dB Cell Range without TMA km Nsites without TMA Sites MAPL with TMA dB Cell Range with TMA km Nsites with TMA Sites
Around 28% less sites thanks to TMA
1 1 187
5.25 Impact of RRH

Uplink
& Downlink Feature Radio Head (RRH)
Remote 1
sector, up to 3 carriers on link budget No feeder losses on UL & DL Higher output power @ antenna connector than classical macro Node-B
Impact
Connection
between remote and local part is optical (max ~10-20 km)

Optical Fibre Iub
1 1 188
5.25 Impact of RRH [cont.]

With RRH Same Typical Noise Figure
Lower cable losses depending on RRH location
From 23 to 29% less sites thanks to RRH
1 1 189
5.26 Relation between number of users and cell load

Cell load according to captured traffic Assuming perfect power control and uniform cell loading
UPLINK Analysis
Nserv ( CI ) j ( CI ) k Ck C Ck = .Itotal Iintra = Nj. .Itotal = 1 + ( CI ) k 1 + ( CI ) j I k Itotal Ck j=1
As
Iextra = f . Iintra
OCIF factor
I total = N 0 .W + I int ra + I extra = N 0 .W 1 xUL
Multi - Service Cell Load
Note: C/I in non-logarithmic values
(CI ) j xUL = (1 + f ). N j . 1+ ( C I ) j j =1
N serv
Other Cell Interference Factor (OCIF)

1 1 190
5.27 Uplink factor f
UPLINK Analysis
Other Cell Interference Factor (OCIF) is defined as
f is derived from System Level simulations (monte-carlo like or dynamic simulations) Values are depending on parameters such as:
Environment (dense urban, urban)
propagation Pathloss coefficient shadowing standard deviation
f = extra I intra
Fast fading (transmit power raise) Soft-handover conditions Sectorization
OTHER-CELL INTERFERENCE FACTOR
Morpho-structure
DENSE URBAN URBAN SUBURBAN RURAL
=4 =6 =8 = 10 = 12
0.69 0.69 0.71 0.70
0.78 0.78 0.79 0.89
0.84 0.84 0.86 0.89
0.87 0.87 0.89 0.93
0.93 0.93 0.95 1.00
Impact on capacity and cell load calculations
1 1 191
5.28 Uplink cell load interpretation

In Mono-Service
Pole capacity (100% cell load) : theoretical uplink capacity limit
x 1 Nj = UL 1 + 1+ f ( C / I) j
UPLINK Analysis
xUL = 1
pole ) N( j
1 1 = 1+ (1 + f ). ( C / I) j
Cell Load : proportion of users according to pole capacity
xUL =
Nj
pole ) N( j
In Multi Service, an equivalent relationship can be derived

j = Nj N where N = N j
(pole ) Nmix =
x N.( j . j ) = UL 1+ f j=1
Nserv
(1 + f ). j . j
j=1
Nserv
xUL =
Nmix
(pole ) Nmix
Note: the repartition of users of the services has to be known!
1 1 192
5.29 Example
Compute the cell load generated by one user per cell of each service:
Speech 12.2kbps, C/I=-20 dB CS 64, C/I= -15 dB PS 128, C/I= -12 dB F factor = 0.8
How many simultaneous speech users (speech only traffic mix) can we support for a 50% cell load and for a 75% cell load?
1 1 193
5.29 Example [cont.]

Compute the cell load generated by one user per cell of each service:
Speech 12.2kbps, C/I=-20 dB -> 1% CS 64, C/I= -15 dB -> 3% PS 128, C/I= -12 dB -> 6% To be multiplied by 1.8 (to consider extracell interference) :1.75%, 5.8%,10.3% per user How many simultaneous speech users (speech only traffic mix) can we support for a 50% cell load and for a 75% cell load? 50% -> 50%/ 1.75% = 29 simultaneously active users 75% -> 75%/ 1.75% = 43 simultaneously active users
1 1 194
5.30 Numerical example

Example: Mix of 3 services
Speech 12.2kbps, C/I=-19.7 dB CS 64, C/I= -15.2 dB PS 128, C/I= -13.2 dB
Nserv
UPLINK Analysis
(CI ) j xUL = (1 + f ). Nj . 1 + (CI ) j F factor =j= 0.8 1
Speech 12.2 CS 64 PS 128
Number of simultaneous active users per sector 1 0 0 26 15 12 0 0 1 0 0 4 2 0 0 0 1 0 0 2 6 Cell load 1.9% 5.3% 8.3% 50% 50% 50% 50% Throughput (kbps/sector) 12.2 64 128 317.2 439 585.2 768
Different combinations of users lead to the same cell load A same cell load can lead to different throughputs (capacity)
1 1 195
5.31 Interaction with traffic modelling stage
UPLINK Analysis
The traffic modeling stage enables to assess the variation of the number of simultaneous users of each service according to traffic intensity and traffic mix inputs Thanks to the relationship between cell load and the number of simultaneous users of each, the variation of the uplink cell load according to traffic inputs is therefore taken into account The peak cell load satisfying the GoS can therefore be derived by the traffic model and converged with the link budget analysis (iterative process)
For each service:
Average traffic intensity at busy hour

Traffic Model
(CI ) j Individual contribution to cell load(1 + f ). 1 + (CI ) j

1 1 196
Grade of service (blocking,delay)
XUL
5.32 Needs for iterative process

Thanks to traffic density
UPLINK Analysis
Coverage and capacity trade-off
Need Need of of an an Cell Range iterative iterative process process between between traffic traffic analysis analysis
Thanks to Link budget
Multi-service Traffic in the cell
& & link link budget budget analysis analysis Interference

Understanding the network behaviour allows a better tailored network
Thanks to capacity formula
1 1 197
5.33 Interest of iterative process
UPLINK Analysis
Network Sized by Fixing Cell load to an arbitrary constant value (e.g. 50% = 3dB) in UL Does not Reflect real Network Evolution, does not run Traffic forecasts Does not allow to set up optimised and customised Network deployment strategy
515 500 Cell Range (m) 475 450 425 400

Feature adding Fixed Cell load Cell Range
Coverage Holes
Phase 3 Phase 4
Phase 1
Phase 2
Rollout Phases
Therefore, Iterative Multi-service Link Budget is required

1 1 198
5.34 Iterative process
UPLINK Analysis
Assume an interference level of I0 Compute cell range through link budget calculation Apply Traffic Model to captured traffic with this cell range : deduce Icalc No, adjust Io Icalc = I0 ? UL Radius
limiting one of all services radii
knowing nb of sub/sqkm per service and the QoS required per service Traffic Model
Yes
1 1 199
5.35 Visualising the iterative process
UPLINK Analysis
Total Interference I(R) above Noise Rise (dB)
18 16 14 12 10 8 6 4 2 0 0 0.2 0.4 0.6 Cell range (km)

Link Budget Curves MOST LIMITING SERVICE Service 1 Service 2 I(R) according to traffic Density
ITERATIONS
0.8
1 1 200
5.35 Visualising the iterative process [cont.]
UPLINK Analysis
18 Total Interference I(R) above Noise Rise (dB) 16 14 12 10 8 6 4 2 0 0 0.2 0.4 0.6 Cell range (km)
Link Budget Curves Service 1 Service 2 I(R) for High traffic Density
Impact of traffic density assumptions
I(R) for Low traffic Density
0.8
1 1 201
5.36 Summary
UPLINK Analysis
Multi-service
Link Budget is required in UMTS for Uplink Analysis Uplink Analysis is a conventional MAPL analysis Link Budget is performed for one user of each service located at cell edge Interference perceived by this user is generated by all the mobiles in the cell and all the services The link budget can be derived for a fixed interference margin (typically 50 to 75% cell load) or for the interference margin corresponding to the traffic captured within the cell (derived from an iterative process) The shared resource in Uplink is the Interference (related to cell loading) The peak interference is calculated with a multi-service traffic model
1 1 202
1 1 203
6 Basic Radio Network Parameter Definition
1 1 204
6 Basic Radio Network Parameter Definition

Objective:
to be able to define the basic radio network parameters (neighborhood planning and code planning parameters)
1 1 205
6.1.1 Neighborhood planning

Objective: to be able to describe the criteria and methods used to perform neighborhood planning.
1 1 206
6.1.1.1 Overview
The purpose of neighborhood planning is to define a neighbor set (or monitored set) for each cell of the planning areas
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:
Intra-frequency neighbor list : cells on the same UMTS carrier Inter-frequency neighbor list: cells on other UMTS carrier Inter-system neighbor lists: for each neighboring PLMN a separate list is needed.
Note: it is NOT the aim of neighborhood planning to define a ranking of the cells inside the neighbor set. This ranking is performed by the UE using UE measurements and criteria defined by UTRAN radio algorithms.
The neighborhood planning plays a key role in UMTS. Indeed, as UMTS is strongly interference limited, a wrong neighbors plan will bring interference increase and therefore capacity decrease.
e.g. if a possible soft handover candidate is not selected, because it is not in the neighbor list, it is fully working as Pilot Polluter
1 1 207
6.1.1.2 Criteria and methods
Criteria: Lets consider one cell (called cell A). One or several of the following criteria can be used to decide to take a candidate cell as neighbor of cell A :
the distance between cell A and the candidate cell is less than a given maximum inter-site distance. the overlap area between cell A and the candidate cell is more than a given minimum value.
Note: overlap area between cell A and cell B = intersection between S A and SB, with SA[km2]=area where

SB[km2]=area where

(CPICH RSCP)cellA and (CPICH Ec/Io)cellA better than given minimum values (CPICH Ec/Io)cell A is the best (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). manually (not possible to consider the overlap area criterion) with an RNP tool see example with 9955 tool on next slides
1 1 208
Methods:

6.1.1.3 Automatic neighborhood allocation with 9955

Step1:
enter input parameters

Typical value -105 dBm -15 dB 4 dB Selected Selected parameters used for overlap area criterion co-site cells=cells of the same NodeB e.g. if cell A is neighbor of cell B, cell B will be neighbor of cell A Comment
Neighborhood parameters Signal level (pilot) Minimum CPICH Ec/Io Ec/Io margin Force co-site as neighbors Force adjacent cells as neighbors Force symmetry Force exceptional pairs Reset neighbors
1 1 209
Force reciprocity of a neighbourhood No specific recommendation link. Force forbid some neighbourhood No specific recommendation relationship defined by the user No specific recommendation if selected all the existing neighbours are deleted before computation.
6.1.1.3 Automatic neighborhood allocation with 9955 [cont.]
Step2:
for each cell, 9955 RNP tool calculates the neighbor list as follows
if Force co-site cells as neighbors=Yes, co-sites cells are taken first in the neighbor list. cells which fulfill the following criteria are taken in the neighbor list:
the maximum inter-site distance criterion the overlap area criterion Note: if the maximum number of neighbors in the list is exceeded, only the cells with the largest overlap area are kept.
if Force neighbor symmetry=Yes, cells with a neighbor symmetry are taken in the neighbor list, under the condition that the maximum number of neighbors has not already been exceeded.
1 1 210
6.1.2 Scrambling code planning

Objective: to be able to describe the criteria and the methods used to perform the scrambling code planning
1 1 211
6.1.2.1 Overview
Scrambling code planning in UMTS FDD is similar to frequency planning in GSM. However it is not such a key performance factor:
it concerns only DL scrambling code (channelization codes and UL scrambling codes are automatically assigned by the RNC) In contrast to frequency planning, it is not crucial which scrambling codes are allocated to neighbors as long as they are not the same code.
1 1 212
6.1.2.2 DL scrambling code planning
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 9955 tool on next slide)
1 1 213
6.1.2.2 DL scrambling code planning [cont.]

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. 2. 3. 4. 5. define the set of allowed codes for each cell (there can be some restrictions for cells at country borders) (optional) define the set of allowed codes per domain (one domain per frequency) define the minimum reuse distance define forbidden pairs (for known problems between two cells) run automatic code allocation and check consistency
9955 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, 9955 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).
9955 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.
1 1 214
6.1.2.3 Definition of UL scrambling code pool for RNC
UL scrambling codes:
used to separate UEs more than one million of codes available (very easy planning) 2 different UEs mustnt have the same code (inside one frequency)
Criterion for definition of UL scrambling code pools: 2 RNC mustnt have the same scrambling code in their pool Method: each RNC is assigned manually a unique pool of codes (e.g. 4096 codes in R2)
Note: when a UE performs a connection establishment to UTRAN (RRC connection), the Serving RNC will assigned dynamically an UL scrambling code out of its pool to the UE. The code is released after RRC connection release.
1 1 215
7 Deltas and Modifications
1 1 216

Objective:
to be able to distinguish between planning parameters of different software releases.
1 1 217
7.1.1 Delta UA5.x UA6 - UA7

Objective:
Differences between software releases UA5.x, UA6 and UA7
1 1 218
7.1.1.1 mac-d PDU size management

In UA5.1, the flag to restrict primary cell to 336 bits was was MaxCellRadius (isHsdpaCellHighPerformance in UA6.0). Basically, in UA5.1, the mac-d PDU size does not change during the call whatever the configuration of the primary cell. The difference between UA5.1 and UA6.0 is the possibility to reconfigure the mac-d PDU size during the call. This reconfiguration is allowed in UA6.0 if the flag isHighPerformancePduSizeReconfAllowed is set to True.
1 1 219
7.1.1.2 CQI adjustement according to Bler

In UA5.0, the purpose of the feature HSDPA performance enhancements Configurable CQI adjustment according to BLER target algorithm is to put the parameters of this algorithm at the OMC-B so that the operator can tune its BLER target. In UA6.0, the algorithm of CQI adlustement according to Bler is further enhanced by supporting multiple BLER targets (configurable via OMC-B) and auto selection of one of these targets depending upon the average CQI and the UE speed.
1 1 220
7.1.1.3 HSDPA OCNS HSDPA OCNS PRINCIPLE

OCNS for HSDPA (HSDPA-OCNS) simulates virtual HSDPA users on the air interface. The main purpose of HSDPA-OCNS is to create load in the HSDPA scheduler that will assign resources for virtual (OCNS) users, and therefore will need to schedule these virtual users together with the real users. Namely load on both HSDPA scheduler and air interface transmit power can be generated by HSDPA- OCNS. This HSDPA-OCNS functionality would be of use in lab testing for measurements and optimization when testing the HSDPA scheduler with real users, particularly when there are limited HSDPA test terminals. An HSDPA-OCNS setup can be requested by an operator from an user interface in OMC-R WIPS in a similar way as in R99 OCNS. The request is passed to RNC, which then replay it to Node B and the scheduler will finally assign resources for the virtual users in HSPDA-OCNS.
OCNS
Orthogonal Code Noise Simulator

1 1 221
7.1.1.4 ActivityFactorCch

In UA5.0, ActivityFactorCch is hard coded to 66%. In UA6.0, ActivityFactorCch is defined by the parameter activityFactorCcch.
1 1 222
7.1.1.5 Management of UL power profile for HSDPA calls
In UA5.1, the management of UL power profile (lower bound for UL SIR Target) for HSDPA calls was handled by UA5.1.2 High quality UL R99 RAB for High HSDPA DL data rate feature. In UA6, the management of UL power profile (initial value, lower bound and upper bound for UL SIR Target) for HSDPA calls is handled by Management of UL power profiles depending on whether HSDPA is mapped on the DL subfeature of UA6 34246 Power Control Enhancements feature. Management of UL power profiles sub-feature of UA6 includes all the functionalities of UA5.1 regarding the upper bound for UL SIR Target, and introduces the same concept for the initial value and the lower bound
1 1 223
7.1.1.6 M-BBU Support
In UA6.0, up to 4 M-BBU per xCEM board are possible. An xCEM supports only M-BBU type starting with this release (UA6.0). Previous UA5.1 configurations based on D/H/E-BBUs are no more supported for the xCEM in UA6.0. For details in UA5.1 configuration and capacity figures, please see the appropriate version of this document (UA5.1 version).
1 1 224
7.1.1.7 M-BBU Support
xCEM M-BBU structure
1 1 225
7.1.1.8 L2 improvements : flexible RLC and MAC-ehs
Support of flexible RLC PDU sizes

Overcome RLC limitations high bit rates with 64-QAM and MIMO Overcome UE processing limits (RLC reassembly) by using larger RLC PDU size up to 1504 bytes
Support of MAC-ehs
Increasing the user throughput by decreasing MAC-hs padding. Allow to schedule a UE in very bad radio conditions when the MAC-ehs transport block cannot fit an RLC PDU (thanks to segmentation at MAC-ehs level)
Enabler for 64-QAM but applicable to any Rel 7 UE supporting L2+ Support on xCEM
RLC SDU RLC PDU MAC -d PDU (=MAC -ehs SDU) MAC -ehs PDU
1 1 226
MAC-ehs header
Userpayload
MAC -d PDU 1
MAC -d PDU 2
MAC -d PDU 3
Pad
Reordering SDU 1
Reordering SDU 2
MAC-ehs
R LCSD U U serpa ylod
header
R LCPD U M AC-d PDU MA C-dPD U1 ( =MAC -ehs S DU) MA C-dPD U2 MA -dPDC U3
MA -ehsC R eordi ngSDU 2 M AC-e hs Reor dingS DU1 headr P DU he ader Reo rding PDU Re ordein gPDU Pad
MAC-e hs
Reordering PDU PDU

Reordering Reordering PDU PDU
7.1.1.9 MAC-ehs PDU Format (3GPP TS 25.321)

Reordering SDU = complete MAC-d PDU or a segment of a MAC-d PDU Reordering PDU = one or more Reordering SDUs of the same Priority Queue (PQ) MAC-ehs header fields present per reordering PDU:
r dh r dh r dh RLC PDU RLC PDU RLC PDU
RLC SDU
Flexible size RLC PDU = MAC-d PDU
RLC SDU Segmentation
TSNi = Transmission Sequence Number for reordering SDUi SIi = Segmentation Indication for reordering SDUi 3GPP limits: Max. 26 reord. SDUs per MAC-ehs PDU
Iub
PQ1
Reordering SDU Reord. SDU Reord. SDU Reord. SDU
r dh
MAC-ehs PDU
MAC-ehs header
Segmentation and Concatenation

Reordering PDU PQ1 MAC-ehs PDU size selected by scheduler MAC-ehs header
Note : Multiplexing of reord SDU from different queues (to the same UE) into a MAC-ehs PDU is not supported in UA07
#bits: 4
LCH-ID1
11
L1
6
TSN1
SI1
F1
LCH-ID2
L2
TSN2
SI2
F2
LCH-IDk
Lk
TSNk
SIk
Fk
MAC-hs header
Reordering PDU
Reordering PDU Mac-ehs payload
Padding (opt)
1 1 227
7.1.1.10 Performance comparison with fix PDU size

Lab results
For currently used HSDPA UE category enhanced Layer 2 feature provides a small gain for highest data rate: 3% for a cat 8 and up to 7% for cat 10 (not shown)
1 1 228
7.1.1.11 L2 improvements : flexible RLC and MAC-ehs

RadioAccessService.isMacehsAllowed : Boolean (global flag to activate/deactivate this feature) HsdpaRncConf.macehsMaximumPduSizePsIb : 42..1504 bytes (maximum RLC PDU size allowed, which has mainly two purposes : limit PDU size on the transport + baseline for Iub/Iur flow control which drives the granularity of the credits) this is used for PS I/B radio-bearers. FDDCell.isMacehsAllowed : Boolean (flag to activate the feature on the cell, if the Node B cell capability also reports that the cell supports MAC-ehs) RlcConfClass.DlRlcAckFlexibleMode optional MO created : RLC parameters when RLC flexible mode is used (MAC-ehs). It contains the same set of parameters than DlRlcAckMode, except minimumTransmissionWindowSize (no interest for Rel7+ UE) and addition of nbrOfBytesBetweenPolling (polling based on a number of bytes)
1 1 229
7.1.1.11 L2 improvements : flexible RLC and MAC-ehs [cont.]

Same restrictions applies Capacity impact on baseband : None to 64QAM due to L2+ The Layer2 Enhancements feature has the following restrictions: dependency Not supported on iCEM : the RB are reconfigured to Mac-hs
On iCEM UE category 13 and above are handled as category 10.
Not supported over Iur : the RB are reconfigured to Mac-hs.

Reconfiguration to MAC-hs/fix PDU size in case of serving cell change to a drift RNC. Reconfiguration to MAC-ehs / flex PDU size following SRNS relocation
The Maximum PDU size is recommended not to be set to too high value on Live Network (for optimal PSFP performance).
UA07.0 : recommended value is 378 bytes
No intra Node B reconfiguration from MAC-ehs to MAC-hs and vice versa

This could happen in case an inter-freq HO is triggered from one cell with HSPA handled by xCEM to a cell with HSPA handled with iCEM (not L2+ support) Fallback to DCH
1 1 230
7.1.1.12 64-QAM modulation for HSDPA

Q Q
UA07.0
FEATURE DESCRIPTION 34386

Support of 64 Quadrature Amplitude Modulation (64-QAM) for HSDPA in addition to 16-QAM and QPSK 64-QAM is selected whenever allowed by radio conditions and resources (i.e. high SNR) and amount of data in buffer New UE categories 13 and 14 (64-QAM only), 17 and 18 (64-QAM or MIMO) 64QAM applicable to all existing HSDPA RAB and combinations Only PS I/B tested due to UE support restricted to data cards xCEM required
QPSK
16-QAM
64-QAM
Macro layer 64-QAM coverage Cell Throughput ~18% ~+4%
Indoor coverage ~45% ~+20%
Max peak rate 21 Mbps (+50% versus cat 10) at MAC-hs layer Max peak rate at TCP layer > 18 Mbps (target in lab) > 14 Mbps (target in field)
1 1 231
7.1.1.12 64-QAM modulation for HSDPA [cont.]

Q Overview of Modulation schemes BLER vs. SINR
9%
16-QAM
Fixed block size: 11520, Number of HS-PDSCH codes = 8
64-QAM
16-QAM performs better at low SINRs but 64- QAM performs better at high SINRs 64-QAM helps if high SINRs can be achieved and reliably identified.
1 1 232
7.1.1.12 64-QAM modulation for HSDPA [cont.]

Overview of TFRC & CQI
The selection of the modulation scheme is done in the MAC-ehs as part of the Transport Format Resource Combination (TFRC) selection function. A TFRC is a triplet of transport block size, modulation alphabet and number of channelization codes. A new transport block size set is defined to include higher transport block size and to allow support of 64-QAM by the MAC layer.
TFRC selection
45000 40000 35000 30000 25000 20000 15000 10000 5000 0 0 5 10 15 20 25 30
With 64QAM larger TB size can be selected at high CQI
selected transport block size
actual CQI
Cat.14 Cat.10
1 1 233
7.1.1.13 64QAM for indoor coverage
45% users benefit from of 64QAM
With indoor coverage and advanced UE receiver (e.g. type 3), 64QAM can boost the cell throughput (+20%)
1 1 234
7.1.1.14 64QAM for isolated micro-cell

Single micro-cell scenario, advanced receivers required
10000 9000 8000 throughput/ kbps 7000 6000 5000 4000 3000 2000 1000 0 Cat 10/ 15 users average user throughput Cat 14/ 15 users 95% user throughput ave. cell throughput
Without 64-QAM Average Cell Throughput 95%-tile Throughput

1 1 235
With 64-QAM 7.65 Mbit/s 8.7 Mbit/s
Gain 10.7% 22.5%
6.9 Mbit/s 7.1 Mbit/s

7.1.1.15 64QAM for the macro layer
In macro layer assuming advanced receiver type 3 (equalization and receive diversity) on the UE side, around 18% of the users could benefit from 64QAM Estimation obtained from a case study considering
Field data information were collected (throughput, CQI distribution, RSCP, Ec/Io) Real monitored network load: traffic mix includes of CS voice over DCH and HSDPA traffic. Simulated traffic load increased to 6 times the current load. Influence of new UE type receiver has been modeled in term of performance, i.e. reported CQI
CQI Mapping versus UE receiver

30
Ped A @ 3km/h
25
Field measurement
20
15
10
Uerxdiv_Eq - Type 3 Uerxdiv_NoEq - Type 1 NoUerxdiv_Eq - Type 2
+
22 24
CQI
Traffic load x6
5 10 12 14 16 18 20
Reference CQI
1 1 236
7.1.1.16 Feature configuration
The 64QAM modulation is configured for a new HSDPA call if the following conditions are fulfilled: 1- The NodeB is 64QAM capable, i.e. xCEM is used to enable HSDPA The Node B on is not handled by a drift RNC 2- The UE is 64QAM capable: The UE informs the RNC of its HSDPA category (should be 13,14,17 or 18) 3- The NodeB is allowed to used the 64QAM: RadioAccessService.isDl64QamOnRncAllowed = True FDDCell.isDl64QamAllowed = True MAC-ehs is enabled 4- The UE category is allowed to used the 64QAM: HsdpaRncConf.is64QamAllowedForUeCategory = 1 for all the UE categories supporting 64QAM, that is to say 13,14,17,18 If all these conditions are fulfilled, then the NodeB will send the new HS-SCCH to inform the UE of the modulation used (QPSK, 16QAM or 64QAM)
1 1 237
7.1.1.17 64QAM deployment in UA07
64QAM and Layer 2 enhancements can be enabled on all HSDPA carriersto improve HSDPA cell performance without specific mobility policy
No negative impact foreseen on legacy UE with ALU implementation No PA power back off. The scheduler ensures power allocation for 64QAM users does not lead to EVM degradation
UA07 F4 (R99/HSPA) with 64QAM F3 (R99/HSPA) with 64QAM F2 (R99/HSPA) with 64QAM F1 (Rel 99) F1 layer reserved for Rel 99 ensure coverage, i.e. the accessibility to the network HSPA traffic can be distributed over HSPA layers with iMCRA
1 1 238
UA07 F4 (R99/HSPA) with 64QAM F3 (R99/HSPA) with 64QAM F2 (R99/HSPA) with 64QAM F1 (R99/HSPA) with 64QAM
Best solution for system capacity
7.1.1.18 Pre-requisites
The
following pre-requisites are needed in order to reach the maximum throughput with 64QAM and transport dependencies
Feature
HSUPA in UL 15 or 14 HS-PDSCH have to be available to reach maximum throughput with 64QAM: Fair Sharing has to be enable in order to have up to 15 HS-PDSCH available. Multiple S-CCPCH, HS-SCCH and DL HSUPA have to be configured in order to reserve only 1 SF16 : for example: 1 S-CCPCH + 2 HS-SCCH + 1 E-AGCH + 1 EHICH/E-RGCH Hybrid Iub or Native IP (xCCM and GigE on RNC needed): In order to achieve high throughput, ATM BW (8 E1s) is not sufficient.
RF
conditions
Low cell load, high SNR, high CQI in order to reach high data rates
1 1 239
7.1.1.19 34386 : 64-QAM modulation for HSDPA Mono and Multi UE (4 users) - Same average CQI AWGN
UE category cat13 & 17 with 64QAM cat14 & 18 with 64QAM cat13 & 17 with 64QAM cat14 & 18 with 64QAM Radio environment Live (*) Live (*) Ideal (**) Ideal (**) Target max throughput (TCP layer) 12 Mbps 14 Mbps 15 Mbps 18 Mbps
Cat 8 : 6 Mbps Cat 10 : 10 Mbps
(*) throughput that can be demonstrated in real life assuming no load, good SNR and Iub bandwidth (**) Best in class measurement in lab environment (AWGN)
1 1 240
7.1.1.16 34386 : 64-QAM modulation for HSDPA Cat 14 (64QAM) comparison with Cat 10 (16QAM)
UE cat 14 (with 64QAM)
UDP Throughput vs. CQI
Lab results
>19 Mbps!
20000 18000 16000 14000 Throughput (kbps) 12000 10000 8000 6000 4000
UE cat 14 - PA3 UE cat 14 - AWGN UE cat 10 - AWGN
2000 0 11 12 13 14 15 16 17 18 19 20 CQI 21 22 23 24 25 26 27 28 29 30
15 HS-PDSCH codes
1 1 241
7.1.1.16 34386 : 64-QAM modulation for HSDPA User Throughput (multi-UE) in PA3 and AWGN
Lab results
14 HS-PDSCH codes
1 1 242
7.1.1.16 34386 : 64-QAM modulation for HSDPA
64QAM can provide significant user throughput boost for pico/micro and indoor coverage It is expected that 64QAM could be used around 18% of the cell area in the macro layer delivering a small cell throughput gain Especially if weighted with UE support availability 64QAM requires enhanced UE receiver which largely benefits to user and cell throughput even beyond 64QAM coverage area It is expected that 64QAM activation on HSDPA capable cells has no negative impact on legacy UE, system performance and cell capacity
1 1 243
1 1 244
End of Module
End of Course
1 1 245

RNP (Radio Network Planning) Fundamentals Umts Ua07: Student Guide

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RNP (Radio Network Planning) Fundamentals Umts Ua07: Student Guide

Transféré par

Droits d'auteur :

Formats disponibles

Do not delete this graphic elements in here:

UMTS RNP (Radio Network Planning) Fundamentals UMTS UA07

All Rights Reserved Alcatel-Lucent @@YEAR

Do not delete this graphic elements in here:

All Rights Reserved Alcatel-Lucent @@YEAR

Course objectives [cont.]

Do not delete this graphic elements in here:

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

Self-assessment of objectives [cont.]

Do not delete this graphic elements in here:

All Rights Reserved Alcatel-Lucent @@YEAR

Do not delete this graphic elements in here:

RNP (Radio Network Planning) Fundamentals UTRAN UA7

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation

GSM Radio Network Engineering Fundamentals Introduction to UMTS

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation

1.1.1 UMTS network architecture

RNC RNS UTRAN Iu-PS

UMTS Radio Access Network

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation

1.1.1 UMTS network architecture [cont.]

Node B Node B RNC 1500 RNS

Node B Iub Node B RNC 1500 RNS UTRAN

1.1 Session presentation

1.1.2 3GPP: the UMTS standardization body

Members: ETSI (Europe) T1 (USA)

ARIB/TTC (Japan) TTA (South Korea)

UMTS system specifications:

Releases defined for the UMTS system specifications:

In the following material we will only deal with UMTS FDD

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation

1.1.3 3GPP UMTS specifications

Interesting specifications for UMTS Radio Network Planning:

1.1 Session presentation

1.1.4 Alcatel-Lucents release overview

Near Nearcommercial commercial

2009 HSDPA HSDPA 21 21 Mbps Mbps

HSxPA + IMS (IP Multimedia Subsystem )

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation

1.1.5 UMTS main radio mechanisms

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation

1.1.5 UMTS main radio mechanisms [cont.]

Multiple frequencies (carriers)

1.1 Session presentation

1.1.5 UMTS main radio mechanisms [cont.]

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation

1.1.5 UMTS main radio mechanisms [cont.]

1.1 Session presentation

1.1.5 UMTS main radio mechanisms [cont.]

start and stop instants

All Rights Reserved Alcatel-Lucent 2009

1.1 Session presentation