Umts Outdoor RF Design Guidelines

Download as pdf or txt
Download as pdf or txt
You are on page 1of 207

UMTS OUTDOOR DESIGN GUIDELINES

Author T. ASZTALOS
Owner T. ASZTALOS
Organization NCS\Digital Network Design\RAN Expertise
Approver P.SABATIER
Document ID ULITPALIL5R3-1390467857-1964

Document location Sharepoint


Change History

Version Status Date Author Owner Reviewed by Reviewed Approver Approval Description of changes
date date

1.0 Approved 28-02-2003 P. SABATIER P. SABATIER ARFD Team 10-03-2003 M. LIEM 21-03-2003

2.0 Approved 07-03-2004 P. SABATIER P. SABATIER ARFD Team 10-03-2004 M. LIEM 22-03-2004

3.0 Approved 18-03-2005 P. SABATIER P. SABATIER ARFD Team 28-03-2005 M. LIEM 13-04-2005

3.1 Approved 18-11-2005 P. SABATIER P. SABATIER ARFD Team 28-11-2005 M. LIEM 10-12-2005

4.0 Approved 26-01-2007 P. SABATIER P. SABATIER ARFD Team 08-02-2007 M. LIEM 19-02-2007

5.0 Approved 04-01-2009 P. SABATIER P. SABATIER ARFD Team 16-01-2009 P. ARNAUD 27-01-2009

6.0 Approved 15-11-2010 P. SABATIER P. SABATIER ARFD Team 25-11-2010 P. ARNAUD 13-12-2010

7.0 Approved 21-07-2011 P. SABATIER P. SABATIER ARFD Team 31-07-2011 P. ARNAUD 17-08-2011

8.0 Approved 16-04-2012 P. SABATIER P. SABATIER ARFD Team 27-04-2012 P.SABATIER 12-05-2012 Update UA8x, UA9x

9.0 Approved 12-05-2013 T. ASZTALOS T. ASZTALOS ARFD Team 23-05-2013 P.SABATIER 07-06-2013

10.0 Approved 01-09-2014 T. ASZTALOS T. ASZTALOS ARFD Team 12-09-2014 P.SABATIER 26-09-2014

11.0 Approved 15-10-2015 T. ASZTALOS T. ASZTALOS ARFD Team 25-10-2015 P.SABATIER 10-11-2015

12.0 Approved 06-06-2016 T. ASZTALOS T. ASZTALOS ARFD Team 17-06-2016 P.SABATIER 28-06-2016

13.0 Approved 30-06-2017 T. ASZTALOS T. ASZTALOS ARFD Team 07-07-2017 P.SABATIER 21-07-2017

14.0 Approved 19-05-2020 T. ASZTALOS T. ASZTALOS RAN Expertise 26-05-2020 P. SABATIER 06-06-2020
Team

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
1 / 207
Contents
1 INTRODUCTION ..................................................................................................................... 11

1.1 Object ..................................................................................................................................... 11

1.2 Scope of this document ...................................................................................................... 11

1.3 Audience for this document ............................................................................................... 11

2 PRE-SALES PHASE OVERVIEW .............................................................................................. 12

2.1 TRAFFIC ASSUMPTIONS ....................................................................................................... 13

2.2 LINK BUDGET & CAPACITY OVERVIEW ................................................................................ 14

2.2.1 Uplink available path loss calculation ................................................................................ 14

2.2.2 Capacity R’99 ........................................................................................................................ 15

2.2.2.1 Uplink ...................................................................................................................................... 15

2.2.2.2 Downlink................................................................................................................................. 16

2.3 DIMENSIONING ...................................................................................................................... 17

3 BS PRODUCTS ....................................................................................................................... 17

3.1 MACRO-CELL BS Products .................................................................................................. 17

3.1.1 fALU WCDMA Node-B products .......................................................................................... 17

3.1.1.1 OneBTS .................................................................................................................................. 17

3.1.1.2 TRDU40-21 ........................................................................................................................... 18

3.1.1.3 TRDU60 product family ....................................................................................................... 18

3.1.1.4 TRDU2x60 product family ................................................................................................... 19

3.1.1.5 TRDU2x80-21 (TRDU2x80-B1) ........................................................................................... 20

3.1.1.6 MC-TRX-09 ............................................................................................................................ 20

3.1.2 fALU WCDMA RRH products ................................................................................................ 21

3.1.2.1 RRH40 product family .......................................................................................................... 21

3.1.2.2 RRH60 product family .......................................................................................................... 21

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
2 / 207
3.1.2.3 RRH2x60 product family ..................................................................................................... 22

3.1.2.4 MC-RRH .................................................................................................................................. 24

3.1.3 ALU WCDMA BS Configurations .......................................................................................... 25

3.1.3.1 2100 MHz Node-B ................................................................................................................ 25

3.1.3.2 850MHz/900MHz Node-B ................................................................................................... 25

3.1.3.3 2100MHz TRDU..................................................................................................................... 25

3.1.3.4 Multi-carrier configurations with TRDU2x60 .................................................................... 26

3.1.3.5 Multi-carrier configurations with TRDU2x80-B1 ............................................................. 27

3.1.3.6 Dual band Node-B UMTS900-UMTS2100MHz configuration supported..................... 28

3.1.3.7 Multi-standard with TRDU ................................................................................................... 28

3.1.3.8 Multi-standard BS configurations with MC-TRX .............................................................. 29

3.1.4 BS Configurations with RRHs .............................................................................................. 30

3.1.4.1 Multicarrier configurations with RRH60-xx ....................................................................... 30

3.1.4.2 Multicarrier configurations with RRH2x60-xx .................................................................. 31

3.1.5 Channel element capacity for Macro-cell NodeB & RRH ................................................ 31

3.1.6 Nokia WCDMA macro BS products ..................................................................................... 31

3.1.6.1 Flexi Multiradio 3TX RF Modules product family .............................................................. 32

3.1.6.2 Flexi Multiradio 6TX RF Modules product family .............................................................. 32

3.1.6.3 Flexi RRH 1TX RF Module product family .......................................................................... 33

3.1.6.4 Flexi RRH 2TX RF Module product family .......................................................................... 33

3.2 OUTDOOR SMALL CELLS PRODUCT................................................................................... 34

3.2.1 9364 Metro cell outdoor ..................................................................................................... 34

3.2.2 9764 LR MCO V1.0&V2.0 .................................................................................................... 34

3.3 REPEATER ............................................................................................................................... 35

3.3.1 Fiber optics repeater ........................................................................................................... 35

3.3.2 RF repeater............................................................................................................................ 35

4 HSxPA ...................................................................................................................................... 37

4.1 HSDPA .................................................................................................................................... 37

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
3 / 207
4.1.1 UPLINK IMPACT ..................................................................................................................... 37

4.1.2 DOWNLINK IMPACT ............................................................................................................... 38

4.1.2.1 HS-SCCH ................................................................................................................................ 38

4.1.2.2 CPICH dimensioning with HSDPA ....................................................................................... 39

4.1.3 MUG tables ............................................................................................................................ 39

4.2 HSUPA .................................................................................................................................... 39

4.2.1 UL IMPACT ............................................................................................................................. 40

4.2.1.1 Description ............................................................................................................................ 40

4.2.1.2 Analysis on different environments .................................................................................. 40

4.2.2 DL IMPACT ............................................................................................................................. 41

4.2.3 THROUGHPUT CALCULATION ............................................................................................. 42

4.3 HSxPA carrier deployment strategy .................................................................................. 42

4.4 HSPA+ ..................................................................................................................................... 43

4.4.1 Overview of Basic HSPA+ Principles ................................................................................... 44

4.4.2 Key Technologies of HSPA+ ................................................................................................ 45

4.4.2.1 Adaptive Modulation and Coding ......................................................................................... 45

4.4.2.2. HARQ ....................................................................................................................................... 45

4.4.2.3 Schedule .................................................................................................................................. 45

4.4.2.4 Layer 2 Enhancement ............................................................................................................ 46

4.4.2.5 64QAM High-Order Modulation ........................................................................................... 46

4.4.2.6 2x2MIMO .................................................................................................................................. 46

5 UMTS CO-EXISTENCE WITH OTHER TECHNOLOGIES ....................................................... 47

5.1 UMTS co-existence with other technologies in different or same frequency bands. 47

5.2 FREQUENCY OFFSET BETWEEN UMTS & GSM IN THE SAME BAND ................................. 49

5.3 FREQUENCY OFFSET BETWEEN UMTS & CDMA IN THE SAME BAND .............................. 52

5.4 FREQUENCY OFFSET BETWEEN LTE & UMTS IN THE SAME BAND .................................. 52

5.5 FREQUENCY OFFSET BETWEEN UMTS & UMTS IN THE SAME BAND .............................. 53

5.6 SOLUTIONS TO FREE FREQUENCY BAND .......................................................................... 54

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
4 / 207
6 900 MHz .................................................................................................................................. 54

6.1 ANTENNA SHARING SOLUTIONS ......................................................................................... 54

6.1.1 Dual Duplexer solution ........................................................................................................ 54

6.1.1.1 Description ............................................................................................................................ 54

6.1.1.2 2G Equipment requirements .............................................................................................. 56

6.1.2 UMTS900-GSM900 Twin TMA combiner solution ............................................................ 57

6.1.3 Double dual antenna solution ............................................................................................ 59

6.1.4 MC-RRH & MC-TRX ............................................................................................................... 60

6.2 LB COMPARISON UMTS900/UMTS2100 ........................................................................... 60

6.2.1 Description ............................................................................................................................ 60

6.2.2 Comparison between 2100MHz and 900MHz for TMA recommendations ................. 61

6.3 LB COMPARISON GSM900 vs UMTS900 ............................................................................ 62

6.4 UMTS900 vs UMTS2100 PERFORMANCES COMPARISON ............................................... 63

6.4.1 COVERAGE COMPARISON .................................................................................................... 63

6.4.2 CAPACITY COMPARISON ...................................................................................................... 64

6.4.2.1 Assumptions.......................................................................................................................... 64

6.4.2.2 Performances improvement ............................................................................................... 65

6.4.3 UMTS900 DEPLOYMENT STRATEGY ................................................................................... 66

6.4.3.1 Dense Urban / Urban ........................................................................................................... 66

6.4.3.2 Suburban/Rural ..................................................................................................................... 66

7 CAPACITY & COVERAGE IMPROVEMENT SOLUTIONS ....................................................... 68

7.1 RF solution for coverage improvement ............................................................................ 68

7.1.1 Height tower increase: ......................................................................................................... 68

7.1.2 Space diversity: ..................................................................................................................... 68

7.1.3 4 way receivers ..................................................................................................................... 68

7.1.4 RRH vs Macro-Node B .......................................................................................................... 69

7.1.5 REPEATER ............................................................................................................................... 70

7.1.6 EXTENDED & ULTRA-EXTENDED CELL SOLUTION ........................................................... 72

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
5 / 207
7.1.7 SAME CELL RADIUS WITH UL LOAD INCREASE (HSUPA) ................................................... 72

7.1.7.1 4 way receivers ..................................................................................................................... 73

7.1.7.2 21 dBi antennas .................................................................................................................... 73

7.1.7.3 UMTS 900 .............................................................................................................................. 74

7.2 RF SOLUTIONS FOR CAPACITY IMPROVEMENT ................................................................. 74

7.2.1 TX DIVERSITY FEATURE ........................................................................................................ 75

7.2.2 CAPACITY COMPARISON BETWEEN 1, 2&3 CARRIERS CONFIGURATIONS ..................... 75

7.2.3 Dual Cell ................................................................................................................................. 76

7.2.4 RRH vs Macro-NodeB ........................................................................................................... 77

7.2.5 UMTS900 implementation .................................................................................................. 78

7.2.6 SMALL CELL-CELL LAYER ..................................................................................................... 78

7.3 SITE SECTOR INCREASE........................................................................................................ 79

7.4 SITE DENSIFICATION ............................................................................................................. 79

8 RADIO DESIGN METHOD FOR MACRO-CELL NETWORK ................................................... 80

8.1 OVERVIEW............................................................................................................................... 80

8.2 MACRO-CELL SITE ACQUISITION ........................................................................................ 80

8.2.1 Site survey ............................................................................................................................. 81

8.2.2 Antenna characteristics & tilt optimization max values ................................................. 82

8.2.3 Co-sitting ............................................................................................................................... 84

8.3 RNP MAIN INPUTS ................................................................................................................. 85

8.3.1 GEOGRAPHICAL DATABASES ............................................................................................... 85

8.3.1.1 Digital Terrain Model (DTM)................................................................................................. 85

8.3.1.2 CLUTTER ................................................................................................................................ 87

8.3.2 PROPAGATION MODEL ......................................................................................................... 90

8.3.2.1 Sites or Cells radio configurations .................................................................................... 90

8.3.2.2 CW calibration measurements............................................................................................ 91

8.3.2.3 Standard Propagation Model .............................................................................................. 91

8.3.2.4 3D Models ............................................................................................................................. 93

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
6 / 207
8.3.3 ENGINEERING MARGINS ANALYSIS ...................................................................................... 96

8.3.3.1 Standard parameters........................................................................................................... 96

8.3.3.2 Shadow margin ..................................................................................................................... 97

8.3.3.3 Indoor/Incar penetration losses......................................................................................... 99

8.3.3.4 Fast fading margin ............................................................................................................... 101

8.3.3.5 UPLINK BUDGET .................................................................................................................... 102

8.3.3.6 DOWNLINK BUDGET.............................................................................................................. 104

8.4 DIMENSIONNING SERVICE RECOMMENDATIONS & TRAFFIC ASSUMPTIONS ................ 110

8.4.1 DIMENSIONING SERVICE....................................................................................................... 110

8.4.2 TRAFFIC ASSUMPTIONS ....................................................................................................... 110

8.5 RF DESIGN TARGETS ............................................................................................................. 111

8.5.1 RSCP targets ......................................................................................................................... 112

8.5.1.1 RSCP target for RNP analysis .............................................................................................. 112

8.5.1.2 RSCP target to consider for field validation ..................................................................... 113

8.5.2 Ec/Io target............................................................................................................................ 114

8.5.3 UL/DL effective service area & user rejection ................................................................. 114

8.5.4 Polluted area & overlap analysis ........................................................................................ 115

8.5.5 Overshooting and post azimuth/tilt optimization analysis ........................................... 115

8.6 OPTIMIZATION....................................................................................................................... 116

8.6.1 METHODOLOGY .................................................................................................................... 116

8.6.2 PRE-OPTIMIZATION PHASE WITH RNP & ACP TOOLS ...................................................... 117

8.6.2.1 Tilt and Azimuth Optimization............................................................................................ 117

8.6.2.2 Neighboring plan / Scrambling Code plan ........................................................................ 119

8.6.3 RF DESIGN FIELD IMPLEMENTATION & RF DESIGN VALIDATION .................................... 121

8.6.3.1 RF design parameters field implementation .................................................................... 121

8.6.3.2 RF design validation ............................................................................................................. 122

8.7 OUTDOOR SMALL CELL LAYER RF DESIGN PROCESS ..................................................... 125

8.7.1 SMALL CELLS PLACEMENT PROCESS OVERVIEW ............................................................. 125

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
7 / 207
8.7.2 MACRO-LAYER DENSIFICATION AND RF DESIGN OPTIMIZATION BASED ON TRAFFIC
GEOLOCATED DATA ............................................................................................................. 127

8.7.3 OUTDOOR SMALL CELLS DEPLOYMENT BASED ON GEOLOCALIZED TRAFFIC DATA OR


DEMOGRAPHIC MAPS ........................................................................................................... 127

8.8 STADIUM RF DESIGN RULES ................................................................................................ 128

9 9955 V7.4.0 PARAMETERS SETTING .................................................................................. 129

9.1 Global tool view..................................................................................................................... 129

9.2 SITES ....................................................................................................................................... 131

9.2.1 Table Description and Settings .......................................................................................... 131

9.2.2 GRID CREATION ..................................................................................................................... 131

9.3 TRANSMITTERS TABLE ......................................................................................................... 132

9.3.1 CELLS TABLE ......................................................................................................................... 134

9.3.2 Add a new cell to a transmitter .......................................................................................... 137

9.4 CLUTTER CLASSES TABLE .................................................................................................... 137

9.5 TRAFFIC PARAMETERS .......................................................................................................... 138

9.5.1 TERMINAL CHARACTERISTICS ............................................................................................. 138

9.5.2 MOBILITY PARAMETERS ....................................................................................................... 140

9.5.3 SERVICE TABLE ...................................................................................................................... 140

9.6 RADIO NETWORK SETTINGS................................................................................................. 142

9.6.1 GLOBAL PARAMETERS TABLE .............................................................................................. 142

9.6.2 FREQUENCY BANDS .............................................................................................................. 143

9.6.3 INTERFERENCE REDUCTION FACTOR ................................................................................. 143

9.6.4 R’99 RADIO BEARER TABLE .................................................................................................. 144

9.6.5 HSDPA RADIO BEARER.......................................................................................................... 145

9.6.6 HSUPA RADIO BEARER .......................................................................................................... 145

9.6.7 HSDPA and HSUPA UE Categories ..................................................................................... 146

9.6.8 SITES EQUIPMENT TABLE ..................................................................................................... 146

9.6.9 R99 Resource Consumption table ..................................................................................... 147

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
8 / 207
9.6.10 HSUPA Resource Consumption table ................................................................................ 148

9.6.11 RECEPTION EQUIPMENT....................................................................................................... 148

9.6.11.1 R’99/HSDPA/HSUPA Eb/Nt & BLER curves........................................................................ 149

9.7 NEIGHBORING PLAN ............................................................................................................. 149

9.8 SCRAMBLING CODE PLAN .................................................................................................... 150

9.9 SIMULATIONS ........................................................................................................................ 152

9.10 PREDICTION STUDIES ........................................................................................................... 153

9.10.1 9955 settings for coverage studies .................................................................................. 153

9.10.1.1 RSCP: Coverage By Signal Level Study .............................................................................. 153

9.10.1.2 Coverage by Transmitters................................................................................................... 154

9.10.2 Ec/Io........................................................................................................................................ 155

9.10.3 OVERLAPPING ANALYSIS ...................................................................................................... 155

9.10.4 RSSI ......................................................................................................................................... 156

9.10.5 9955 settings for Throughput studies ............................................................................. 157

9.10.5.1 HSDPA study ......................................................................................................................... 158

9.10.5.2 HSUPA study ......................................................................................................................... 161

9.10.6 MULTI-STOREY ...................................................................................................................... 161

9.11 SCANNER or CW DATAS IMPORT & COMPARISON WITH STUDIES .................................. 163

9.12 GEO DATABASES IMPORT .................................................................................................... 167

9.13 MULTI-RAT SETTINGS ........................................................................................................... 168

9.13.1 NETWORKS ............................................................................................................................. 169

9.13.2 PARAMETERS ......................................................................................................................... 171

9.13.3 GEO ......................................................................................................................................... 171

9.14 STREET TO CLUTTER MODULE TO UPDATE 2D GEODATABASE IN A 2.5D ACCURATE


DATABASE .............................................................................................................................. 172

10 9955 ASP/ACP METHOD & SETTINGS ................................................................................ 172

10.1 Greenfield RF design method with using ASP .................................................................. 173

10.2 Network densification with using ASP ............................................................................... 179

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
9 / 207
10.3 RF design optimization method with 9955 ACP .............................................................. 181

10.4 ACP parameters settings recommended for RF optimization ...................................... 182

10.4.1 Creating an ACP setup ......................................................................................................... 182

10.4.2 ACP Setup: Optimisation ..................................................................................................... 183

10.4.3 ACP Setup: Objectives ......................................................................................................... 186

10.4.3.1 Coverage targets .................................................................................................................. 187

10.4.3.2 Ec/Io target............................................................................................................................ 188

10.4.3.3 Overlapping targets ............................................................................................................. 189

10.4.4 ACP Setup: Antenna ............................................................................................................. 191

10.4.5 ACP Setup: Reconfiguration................................................................................................ 192

10.4.5.1 Site optimizations ................................................................................................................ 193

10.4.5.2 Transmitter parameter optimizations .............................................................................. 194

10.4.5.3 Cell parameter optimizations ............................................................................................. 196

10.4.6 ACP with traffic map and load balancing .......................................................................... 196

10.4.7 ACP: Running the optimization ........................................................................................... 197

10.4.8 ACP: Analyzing the results ................................................................................................... 198

10.5 HOW TO IMPLEMENT AN OPTIMUM SMALL CELLS NUMBER ........................................... 200

11 REFERENCE DOCUMENTATION .............................................................................................. 201

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
10 / 207
1 INTRODUCTION
1.1 Object

This document describes the process of dimensioning and designing the radio system of a UMTS
network. It provides a detailed presentation of the different steps to perform.

This document synthesizes several studies done by Core engineering team, on the impact or
gain expected by new features implementation.

The studies have been detailed in documents or presentations which are mentioned in this
document and referenced at its end.

1.2 Scope of this document

This document contains

UMTS radio design process

Design solutions for coverage and capacity problems

All the parameters settings for 9955 radio planning tool V7.3.2 build 11009 version and
Forsk ASP/ACP tools associated

1.3 Audience for this document

The audience for this document is the people involved in:

Radio Network design and Planning

Radio Network engineering

Radio Network optimization

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
11 / 207
2 PRE-SALES PHASE OVERVIEW
This section is an overview of the different stages to go through in order to perform a complete
radio planning of an UMTS network. As in GSM design this process is mainly divided in three
phases:

The radio and traffic assumption definition

The cell count estimation and the strategy definition

The radio network simulation and optimization

NOTE: In the case of an existing operator, reusing sites (for economical and administrative
reasons) has a great impact on the cell planning process and can lead to a large increase on the
total number of sites.

Figure 1: Radio Planning Process

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
12 / 207
The assumptions used for the design of an UMTS network will have a large impact in the final
radio planning results.

Depending on the target quality of service, the service availability, the number of carriers
available and the traffic forecast, the number of sites can dramatically be increased by a factor 2
or even more.

These assumptions should thus be specified in close relation with the customer needs, keeping
in mind all the possible implications in terms of cost, design constraints and global quality.

2.1 TRAFFIC ASSUMPTIONS

The traffic assumptions for a W-CDMA network are necessary to define the coverage objectives
together with the offered capacity.

Both are closely linked, and the size of a cell will depend on the services provided, but also on
the total number of captured users.

The traffic assumptions should be based on the busy hour, that is, the average traffic during the
busiest hour of the day.

It will describe, for each service (Speech, CS/ PS, data rate) the offered traffic density (in Erlang
per /km² or duration of communication per hour per km² for circuit switched data and speech,
and kbps/km² for packet switched data).

Services availability:

The first requirement is to define the services which should be supported by the network.

The UMTS specification proposes several services such as voice service, different data rates in
circuit switched mode (Long Constraint Delay mode), and in packet mode (Unconstraint Delay
Data).

Each of these services requires different radio quality in terms of Eb/No, and will have different
impact on the design.

In most of the cases the services required are: speech, PS64, CS64, PS128, PS384, HSDPA and
HSUPA.

The second step is to define:

Analyze areas

User characteristics (speed, call profile.) should be defined for each area

Quality of service required

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
13 / 207
Quality of coverage required per service

The cell count estimation is based on the link budget results.

It will help to determine if the design assumptions are not too constraining in terms of number
of sites, and if the traffic assumptions will be met.

It also helps to evaluate the limitation of the network, and gives baselines for the design
strategy. As in GSM, a W-CDMA network can be coverage or capacity limited.

Coverage limitation means that the total number of cells is determined by the target quality of
coverage.

Capacity limitation means that the final cell count is determined by the traffic assumptions.

When coverage limited, the noise rise assumption given (UL Interference margin) in the link
budget can be relaxed.

• The design should then be done in order to meet exactly the coverage
requirements, in order to minimize the number of sites.

When capacity limited, different solutions may be chosen, such as increasing the noise rise level
(load) in the link budget, resulting in reducing the size of the cells, adding a new carrier, or
implementing a second layer (small cells).

These solutions will depend on the target offered capacity. They will be treated in next parts.

2.2 LINK BUDGET & CAPACITY OVERVIEW

The parameters given in this chapter are based on the Link Budget guidelines (see [R1] & [R2]
linked in part 11 of this document)

2.2.1 Uplink available path loss calculation

The link budget helps to determine the UL available path loss in a cell for a given service at a
required quality of coverage, in a given environment, for a given capacity.

Link budget is essentially used in pre-sales, in order to calculate the Node B and site number for
the analyzed area.

The LB allows:

For each service, calculate the design threshold, based on engineering margin

Cell radius calculation for each environment type, using a propagation model

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
14 / 207
This will be used to define the number of sites necessary.

Several parameters like shadowing margin, Eb/No, orthogonality factor, UL load ….are re-used in
post-sales phase.

The main parameters are discussed hereafter in the paragraph 8.3.3 (for a more details see [R1]
& [R2] linked in part 11 of this document).

The default propagation model is Okumura Hata model @ 900MHz, or 850MHz and Cost-
Hata@1800MHz to 2100MHz. The cell size of the dimensioning service, for a given environment,
will then be used for the cell count estimation.

2.2.2 Capacity R’99

In the link budget is given the estimated uplink capacity per cell, given the noise rise. It is based
on the N-pole capacity equation:

2.2.2.1 Uplink

The number of simultaneous connected users, for a given service, that can be served per UMTS
cell carrier, in the uplink, is given by the N-pole capacity equation:

1  1 

N pole = 1+
(1 + f ).  (C / I )
 

X UL  1 

N= 1+
(1 + f ).  (C / I ) 

Where

Npole is the theoretical maximum uplink capacity of a CDMA system,


N is the actual capacity corresponding to the uplink cell load XUL . Here N
represents the number of simultaneously active users.

X UL uplink cell load = Actual number of users / Maximum number of users.


Typically, UL cell load = 65%, corresponding to 4.5dB noise rise.

f is the ratio between intercell and intracell interference


C/I= (Eb/No) / PG is the ratio of signal over interference + Noise target to reach a
given BLER quality for the service,

Eb/No is the UL performance requirement and PG the processing gain (ratio


between the service bit rate and the 3.84Mcps chip rate.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
15 / 207
In this formula, all the parameters are service or environment dependent.

It should be noted here that the number of radio links available in a cell is dependent on the
loading of the cell, which is determined by the RF designer in the link budget. Based on this
loading the interference margin is automatically processed in the tool, in order to determine the
total margin to be applied in the cell.

2.2.2.2 Downlink

A downlink capacity equation is also available. It characterizes the fact that the total power
available in the base station PA is shared between the power used for common channels, the
power reserved for SHO, and all the users.

The following formula gives a simplified approach to derive the DL capacity per service type.
  Eb  
−1

  N (i)  
OF +  0 Target
   (PA − CCCH Pwr − SharedPwr )
  PG (i )  G SHO  
   
1    
DL Sector Capacity (i) = 
AF (i ) ( DL MeanF + OF )  PA + UE Th. Noise  DL Mean Total PL
With

AF (i ) : Activity factor

DL MeanF : mean ratio between interference extra-cell and intra-cell typically equal to 0.6 - 0.8

CCCH Pwr : Total power used for common channels

SharedPwr : Power reserved for SHO

DL Mean Total PL : mean DL path loss from Node-B connector to UE antenna

PG (i ) : processing gain

GSHO
: is the average gain obtained on the Eb/No due to uplink reselection diversity in soft
handoff.

Such simple UL and DL monoservice capacity formulas are implemented in an Excel sheet [R5]
linked in part 11 of this document.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
16 / 207
2.3 DIMENSIONING

All the dimensioning approach done in pre-sales is detailed in [R6] linked in part 11 of this
document.

3 BS PRODUCTS
All the technical values specified are typical ones

3.1 MACRO-CELL BS Products

For more detailed information about fALU WCDMA macro BS (Node-B or RRH) products see
product engineering guides [R14], [R15], [R16] and [R25] of linked in part 11 of this document.

In this section, the RF front-end performances are summarized (except Eb/No values which are
detailed in section 8.5).

3.1.1 fALU WCDMA Node-B products

3.1.1.1 OneBTS

• MCPA output power:

o 1900/AWS

▪ 45W total PA power: 2 carrier supported,

▪ 60W total PA power: 3 carriers supported

o 850MHz

▪ 45W total PA power: 2 carrier supported,

• Noise Figure (NF): 2.2dB

• TMA supported

• ACLR: 61dB

• ACS: 55dB

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
17 / 207
3.1.1.2 TRDU40-21

• Band of operation: 2100 MHz 3GPP band B1 frequency band (TRDU40-21)

• Number of carriers : up to 2 adjacent carriers (2x5MHz=10 MHz BW)

• RF output power @antenna port: 40W nominal RF power (TRDU40-21): 40W x 1 carrier -
20W x 2 carriers

• RX diversity: 2-way diversity

• Noise Figure (NF): 2.7 dB typical (typical sensitivity is –124,5 dBm)

• TMA supported: RETA HW ready (AISG1.1 and AISG 2.0 RET and TMA support with
additional AISG primary controller)

• ACLR: 61dB

• ACS: 55dB

3.1.1.3 TRDU60 product family

• Products: TRDU60-08, TRDU60-09, TRDU60-18, TRDU60-19, TRDU60-21 & 21B

• Bands of operation:

o 850 MHz 3GPP Band B5 (TRDU60-08)

o 900MHz 3GPP Band B8 (TRDU60-09)

o 1800 MHz 3GPP Band B3 (TRDU60-18)

o PCS 1900MHz 3GPP Band B2 (TRDU60-19)

o 2100 MHz 3GPP Band B1 (TRDU60-21 & 21B)

• Number of carriers : up to 4 adjacent carriers (4 times 5 MHz BW)

• RF output power @antenna port:1x60W nominal RF power; 60W x 1 carrier, … 4x15W x4


carriers

• RX diversity: 2-way diversity

• LTE ready

• Noise Figure (NF): 2.0 dB typical (typical sensitivity is –125,5 dBm)

• TMA supported

• ACLR: 61dB

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
18 / 207
• ACS: 55dB

• RF features:

o internal AISG 2.0 RET

o VSWR meter on TX antenna path (3 thresholds report) - TX port VSWR

3.1.1.4 TRDU2x60 product family

Note: fALU TRDUs with double PA (TRDU2x WCDMA products) includes 2 RF transmitters
(MCPAs), allowing it to support of VAM (Virtual Antenna Mapping, used to optimize WCDMA power
pooling across PAs) and 2x2 MIMO (allowing increased W-CDMA throughputs). It is LTE-capable,
and ready to supporting mixed mode (Multi-Standard radio, or MSR) WCDMA-LTE.

• Products: TRDU2x60-08, TRDU2x60-09, TRDU2x60-18, TRDU2x60-19

• Bands of operation:

o 850 MHz 3GPP Band B5 (TRDU2x60-08)

o 900MHz 3GPP Band B8 (TRDU2x60-09)

o 1800 MHz 3GPP Band B3 (TRDU2x60-18)

o PCS 1900MHz 3GPP Band B2 (TRDU2x60-19)

• Number of carriers: up to 4 carriers (in 2 times 20 MHz BW)

• discontinuous spectrum across the two PA (support for disaggregated spectrum usage)

• RF output power @antenna port:2x60W nominal RF power; 120W x 1 carrier, … 4x30W x4


carriers

• RX diversity: 2-way/4-way diversity

• MIMO / VAM ready

• LTE ready

• Noise Figure (NF): 2.0 dB typical (typical sensitivity is –125,5 dBm)

• TMA supported

• ACLR: 61dB

• ACS: 55dB

• RF features:

o internal AISG 2.0 RET

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
19 / 207
o VSWR meter on TX antenna path (3 thresholds report) - TX port VSWR

3.1.1.5 TRDU2x80-21 (TRDU2x80-B1)

• Band of operation: 2100 MHz 3GPP band B1 frequency band

• Number of carriers : up to 4 x 40W carriers (in 2 times 20 MHz BW); HW ready to


support up to 8 x 20W carriers

• discontinuous spectrum across the two PA (support for disaggregated spectrum usage)

• RF output power @antenna port:2x60W nominal RF power; 120W x 1 carrier, … 4x30W x4


carriers

• RX diversity: 2-way/4-way diversity

• MIMO / VAM ready

• LTE ready

• Noise Figure (NF): 1.8 dB typical (typical sensitivity is –125,7 dBm)

• TMA supported

• ACLR: 61dB

• ACS: 55dB

• RF features:

o internal AISG 2.0 RET

o VSWR meter on TX antenna path (2 thresholds report) - TX port VSWR

3.1.1.6 MC-TRX-09

The 9100 Base Station product allows implementation of the UMTS and GSM standard defined
by ETSI in one single cabinet. The MC-TRX-09 module is usable in GSM as well as in WCDMA 900
MHz. Herein we are looking on some aspects of this later quality.

• Band of operation: 900 MHz 3GPP band B8 frequency band

• Number of carriers: up to 3 x 20W carriers (in a 20 MHz BW);

• RF output power @antenna port:20W, 40W and up to 60W nominal RF power;

• RX diversity: 2-way

• Noise Figure (NF): 2.2 dB typical (typical sensitivity is –125,4 dBm)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
20 / 207
• TMA: can support TMA via the Antenna Network. TMA power supply and supervision is
provided by the AND or ANC Evolution

3.1.2 fALU WCDMA RRH products

3.1.2.1 RRH40 product family

• Products: RRH40-08, RRH40-19, RRH40-AWS

• Bands of operation:

o 850 MHz 3GPP Band B5 (RRH60-08)

o PCS 1900MHz 3GPP Band B2 (RRH40-19)

o 2100/1700 MHz AWS 3GPP Band B4 (RRH40-AWS)

• RF power configuration:

o Single PA: 1x40W

• 2 carriers in the lower B5 & 3 carrier in the upper bands supported

• Supported from 9326 d2U

• LTE compliant

• RX diversity: 2-way

• Noise Figure (NF): 3.0 dB typical in the lower 850MHz band (typical sensitivity is –124,5
dBm) & 2.7 dB in the upper PCS &AWS bands (-124.8 dBm sensitivity)

• TMA supported: RETA HW ready (AISG 1.1 - class 1 RET); AISG 2.0

3.1.2.2 RRH60 product family

• Products: RRH60-09, RRH60-09A, RRH60-21A, RRH60-21C, RRH60-08, RRH60-19

• Bands of operation:

o 850 MHz 3GPP Band B5 (RRH60-08)

o 900MHz 3GPP Band B8 (RRH60-09)

o 1800 MHz 3GPP Band B3 (RRH60-18)

o PCS 1900MHz 3GPP Band B2 (RRH60-19)

o 2100 MHz 3GPP Band B1 (RRH60-21A, RRH60-21C)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
21 / 207
• Number of carriers :

o up to 3 adjacent carriers (3x20W in 15MHz BW) in the 900MHz band and

o Up to 4 adjacent carriers in the 2100 MHz band (4x15W in 20 MHz BW);

• Nominal operation band: 15MHz & 20MHz; RRH 60-09A provides compatibility with
RRH60-09, but with operational bandwidth increased to 19.6MHz; 20MHz BW in the
upper bands

• RF output power @antenna port:1x60W nominal RF power; 60W x 1 carrier, … 4x15W x4


carriers

• RX diversity: 2-way

• LTE compliant

• Noise Figure (NF): 2.0 dB typical in the lower 900MHz band (typical sensitivity is –125,5
dBm) & 1.8 dB in the upper 2100 MHz band (-125.7 dBm sensitivity)

• TMA supported: RETA HW ready (AISG 1.1 - class 1 RET); AISG 2.0

Figure 2: fALU RRH 60W 2100C, with solar shield

3.1.2.3 RRH2x60 product family

Note: fALU RRHs with double PA (RRH2x WCDMA products) includes 2 RF transmitters (MCPAs),
allowing it to support of VAM (Virtual Antenna Mapping, used to optimize WCDMA power pooling
across PAs) and 2x2 MIMO (allowing increased W-CDMA throughputs). It is LTE-capable, and
ready to supporting mixed mode (Multi-Standard radio, or MSR) WCDMA-LTE.

• Products: RRH2x60-08, RRH2x60-21, RRH2x60-21A, RRH2x60-19, RRH2x60-19A

• Bands of operation:

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
22 / 207
o 850 MHz 3GPP Band B5 (RRH2x60-08)

o PCS 1900MHz 3GPP Band B2 (RRH2x60-19 &19A)

o 2100 MHz 3GPP Band B1 (RRH2x60-21 & 21A)

• Number of carriers :

o up to 3 carriers (3 times 40W in 15MHz BW)

o up to 4 carriers (4 times 30W in 20 MHz BW)

o HW ready to support up to 8 carriers (8 times 15W)

• discontinuous spectrum across the two PA (support for disaggregated spectrum usage)

• RF output power @antenna port:2x60W nominal RF power; 120W @ 1 carrier, … 4x30W @ 4


carriers

• RX diversity: 2-way/4-way diversity

• MIMO / VAM ready

• LTE ready

• Noise Figure (NF): 1.8 dB typical (typical sensitivity is –125,7 dBm)

• TMA supported

• ACLR: 61dB

• ACS: 55dB

• RF features:

o internal AISG 2.0 RET

o VSWR meter on TX antenna path (2 thresholds report) - TX port VSWR

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
23 / 207
3.1.2.4 MC-RRH

Figure 3: MC-RRH principle

MC-RRH 900MHz MC-RRH 1800MHz

880-915 MHz / 925-960 1710-1785 MHz / 1805-1880


Working frequency bands
MHz MHz

Noise Figure 2.2 dB 2 dB

Volume < 29 liters


Volume / Weight
Weight < 17 kg

Rx Sensitivity GSM: -112 dBm

(typical) W-CDMA: -125.5 dBm

Instantaneous bandwidth 20 MHz

MTBF ≥ 150 000 hours

Between -40°C and 50°C (Automatic fan activation for MC-


Operating Temperature
RRH900 at high temperature).

Figure 4: MC-RRH general characteristics

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
24 / 207
3.1.3 ALU WCDMA BS Configurations

3.1.3.1 2100 MHz Node-B

• Up to 6 CEM cards supported

• MCPA output power:

o 2100MHz

▪ 45W total PA power: 2 carrier supported,

▪ 60W total PA power: 3 carriers supported (STSR3)

Combination between 45W and 60W PA can be done on a same Node-B with STSRx+y
configuration

For 3 carriers supported solutions are STRS2+1 or STSR3

For more information about STSRx see documents [R14], [R15], [R16] and [R25] linked in part
11 of this document

3.1.3.2 850MHz/900MHz Node-B

• 2 carrier per sector supported in STSR1+1 configuration

3.1.3.3 2100MHz TRDU

• Up to 6 TRDU supported

• PA size :

o 40W TRDU supports 3 carriers per PA

o 60W TRDU supports 3 carriers per PA

• Up to 3 xCEM cards supported

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
25 / 207
Figure 5: Node-B configuration with TRDU

Figure 6: TRDU description

3.1.3.4 Multi-carrier configurations with TRDU2x60

TRDU2x60 provides up to 120W of RF power in a single compact unit, providing excellent


support for higher carrier counts and higher power per carrier. This leads directly to improved
coverage, in-building penetration and throughput.
Examples include:
• Up to 6 GSM carriers at 20 W / carrier
• Up to 4 WCDMA carriers at 30W/ carrier
• A high bandwidth LTE carrier of up to 60W+60W MIMO

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
26 / 207
3.1.3.5 Multi-carrier configurations with TRDU2x80-B1

TRDU2x80-B1 architecture follows the rules below:

• 1, 2, 3 or 4 carriers per TRDU2x80-B1 anywhere in the band (in 2 groups of 45 MHz) if


MIMO or VAM is not used (STSR1 to STSR2+2); Hardware-ready for STSR4+4; availability
dependent on software support release plan; max 6 carriers with current WCDMA use of
CPRI rate 2.

• 1, 2, or 3 carriers per TRDU2x80-B1 (in 45 MHz) if MIMO or VAM is used (STSR1-VAM to


STSR3-VAM).

• 80W RF power per PA is shared among the allocated carriers

a) Single TRDU2x80-21 per sector: STSR1, STSR2 & STSR3

TRDU2x80-21 may be used as an TRDU1x, with only one active PA, supporting configurations
including STSR1, STSR2 and STSR3, without VAM or MIMO.

b) Single TRDU2x80-21 per sector: STSRx+y

TRDU2x80-21 use of 4 receivers makes it possible to manage up to 8 carriers in two


independent blocks of 45 MHz (dependent on software support)

By using one TRDU2x80-21 per sector, the following STSRx+y configurations are supported:

• STSR1+1, i.e. 2 carriers providing 80W per carrier

• STSR2+2, i.e. 4 carriers configuration providing 40W per carrier

• STSR3+3, i.e. 6 carriers configuration providing 26W per carrier

• STSRx+y configurations with x≠y, like STSR3+1, are also supported (x≤3 and y≤3)

Note: support of >3 carriers dependent on future software support

STSRx+y configurations using TRDU2x80-21 are perfectly suited to support UTRAN sharing.

c) VAM or MIMO support

TRDU2x80-21 is designed to support VAM and MIMO features without the need for a second
TRDU per sector. This allows an efficient deployment of MIMO and VAM with only 3 TRDU per
Node B.

When MIMO or VAM are used, STSR1-VAM (80W+80W per carrier), STSR2-VAM
(40W+40W/carrier), STSR3-VAM (26W+26/carrier) configurations are supported.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
27 / 207
3.1.3.6 Dual band Node-B UMTS900-UMTS2100MHz configuration supported

• 2 carrier for 2100MHz with 45W or 60W PA power


• 1 carrier for 900MHz with 55W PA power
iCEM 2100MHz
D sector
MCPA ‘alpha’
900MHz
iCEM D

6 RX
iCEM D sector
iCCM xTRM MCPA ‘beta’
3 TX D
iCEM

D sector
MCPA ‘gamma’
iCEM
D
Iub

D sector
MCPA ‘alpha’
D

6 RX
D sector
xTRM MCPA ‘beta’
3 TX D

D sector
MCPA ‘gamma’
D

Figure 7: Dual-band Node-B

3.1.3.7 Multi-standard with TRDU

Based on 2G Evolium BTS with 4 GSM TRX. GSM1800/ GSM900 combination is possible d2U unit
implementation which supports 3 CEM cards
40W TRDU supports 2 carriers per PA

Figure 8: Multi-standard BTS description

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
28 / 207
3.1.3.8 Multi-standard BS configurations with MC-TRX

Figure 9: fALU MBI5 cabinet with GSM+WCDMA modules

The table below is not exhaustive, but gives some configurations that would make sense on the
field when introducing one or several WCDMA carriers. The MC-TRX module has the full flexibility
to support other mixed configuration in the limit of the Power Amplifier capacity.

Multi-mode Output power Output power


configuration @ module level TOC
1 GSM + 1 W-CDMA 1x21W + 1x54W 1x16W + 1x40W
1 GSM + 1 W-CDMA 1x45W + 1x27W 1x32W + 1x20W
2 GSM + 1 W-CDMA 2x21W + 1x27W 2x16W + 1x20W
3 GSM + 1 W-CDMA 3x13W + 1x27W 3x9W + 1x20W
1 GSM + 2 W-CDMA 1x21W + 2x27W 1x16W + 2x20W
2 GSM + 2 W-CDMA 2x14W + 2x27W 2x10W + 2x20W
Figure 10: MC-TRX multi-mode performances

Initial configuration: Intermediary step: Final stage:


4 GSM Carriers 2 GSM + 1 UMTS 2 UMTS carriers

GSM
GSM
AN AN 3G AN
3G

MC-TRX AN MC-TRX AN MC-TRX AN

GSM f1… f4 UMTS GSM f1,f2 UMTS f1,f2

MHz MHz MHz

Figure 11: Summary of multi-mode GSM/WCDMA configurations; MC-TRX modules

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
29 / 207
3.1.4 BS Configurations with RRHs

The Remote Radio Head is a product used to relocate the full radio part from the base station
cabinet to a more adapted location.

For the same capacity, RRH introduces more flexibility on deployment and reduces its cost. On
the other hand, it can eliminate the main losses inside antenna’s chain.

Figure 12: Description of D2U+RRH configuration

3.1.4.1 Multicarrier configurations with RRH60-xx

a) Single RRH60-xx per sector: STSR2 & STSR3

RRH60-xx (or RRH1x60-xx) with only one active PA, may support configurations including STSR1,
STSR2 and STSR3, without VAM or MIMO.

b) Two RRH60-xx per sector: STSRx+y

With two RRH60-xx on a sector you may use up to 2 transmitters and 4 receivers in various
configurations including Tx diversity, VAM and MIMO & various STSRx+y modes.

By using two RRH60-xx per sector, the following STSRx+y configurations are supported:

• STSR1+1, i.e. 2 carriers providing 60W per carrier

• STSR2+1, i.e. 3 carriers configuration providing 30W per carrier

• STSR2+2, i.e. 4 carriers configuration providing 30W per carrier (or 4 carriers providing

20W/ carrier for RRH60-09A)

STSRx+y configurations using RRH60-xx are perfectly suited to support UTRAN sharing.

STSRx+y configurations each pair of RRHs must be the same type of RRH.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
30 / 207
3.1.4.2 Multicarrier configurations with RRH2x60-xx

a) Single RRH2x60-xx per sector: STSR2 & STSR3 & STSR4

RRH2x60-xx may be used as an RRH1x60-xx, with only one active PA, supporting configurations
including STSR1, STSR2, STSR3 and STSR4, without VAM or MIMO.

b) Single RRH2x60-xx per sector: STSRx+y

RRH2x60-xx’s use of 4 receivers makes it possible to manage up to 8 carriers in two


independent blocks of 20 MHz (45MHz for RRH2x60-21A, dependent on software support)

By using one RRH2x60-xx per sector, the following STSRx+y configurations are supported:

• STSR1+1, i.e. 2 carriers providing 60W per carrier

• STSR2+2, i.e. 4 carriers configuration providing 30W per carrier

• STSR3+3, i.e. 6 carriers configuration providing 20W per carrier

• STSR4+4, i.e. 8 carriers configuration providing 15W per carrier

• STSRx+y configurations with x≠y, like STSR3+1, are also supported (x≤4 and y≤4)

Note: support of >4 carriers dependent on future software support

STSRx+y configurations using RRH2x60-xx are perfectly suited to support UTRAN sharing.

c) VAM or MIMO support

RRH2x60-xx is designed to support VAM and MIMO features without the need for a second RRH
per sector. This allows an efficient deployment of MIMO and VAM with only 3 RRH per Node B.

When MIMO or VAM are used, STSR1-VAM (60W+60W per carrier), STSR2-VAM
(30W+30W/carrier), STSR3-VAM (20W+20/carrier) configurations are supported.

3.1.5 Channel element capacity for Macro-cell NodeB & RRH

All the information concerning Node-B and RRH iCEM, xCEM & eCEM capabilities are available
with the link detailed in [R28].

3.1.6 Nokia WCDMA macro BS products

Note: Nokia WCDMA Flexi Multiradio products including RF Modules and RRH Equipments are
described in details by document [R58] linked in part 11. These, with few exceptions, are with
Software programmable technologies, i.e. are LTE-capable, ready to support mixed mode (Multi-
radio) GSM-WCDMA-LTE.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
31 / 207
3.1.6.1 Flexi Multiradio 3TX RF Modules product family

• Products: Flexi RFM 3-pipe 850 (FXCA), Flexi RF Module 3TX 850 (FXCB), Flexi RF Module 3TX
900 (FXDA, FXDJ), Flexi RFM 3-pipe 900 (FXJB), Flexi RF Module 3TX 1800 (FXEA, FXEB), Flexi
RF Module 3TX 1900 (FXFB, FXFC), Flexi RF Module 3TX 2100 (FRGP, FRGT), Flexi RF Module
3TX 1700/2100 (FRIE)

• Bands of operation:

o 850 MHz 3GPP Band B5 (FXCA, FXCB)

o 900MHz 3GPP Band B8 (FXDA, FXDB, FXDJ, FXJB)

o 1800 MHz 3GPP Band B3 (FXEA, FXEB)

o PCS 1900MHz 3GPP Band B2 (FXFB, FXFC)

o 2100MHz 3GPP Band B1 (FRGP, FRGT)

o 1900MHz(Rx)/ 2100MHz(Tx) (FRIE)

• Number of carriers: up to 4 carriers (typically in 2 times 20 MHz BW or more)

• RF output power (max total power):

o 3x60W nominal RF power distributed amongst supported number of sectors


(typical:3→ 60W/sector) and number of carriers/sector: FXCA, FXDA, FXDJ,FXEA,
FXFB, FRGP, FRIE;

o 3x80W nominal RF power distributed amongst supported number of sectors


(typical:3→ 80W/sector) and number of carriers/sector: FXCB, FXDB, FXJB,FXEB,
FXFC, FRGT, FRGS;

• RX diversity: 2-way/4-way diversity

• MIMO ready

• LTE ready

• Noise Figure (NF): 2.0 dB typical

3.1.6.2 Flexi Multiradio 6TX RF Modules product family

• Product: Flexi RFM 6-pipe 2100 360W (FRGU)

• Bands of operation: 2100MHz 3GPP Band B1 (FRGU)

• Number of carriers: up to 4 carriers (in 2 times 60 MHz BW)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
32 / 207
• RF output power (max total power): 6x60W nominal RF power distributed amongst
supported number of sectors (typical:6→ 60W/sector) and number of carriers/sector;

• RX diversity: 2-way/4-way diversity

• MIMO ready

• LTE ready

• Noise Figure (NF): 2.0 dB typical

3.1.6.3 Flexi RRH 1TX RF Module product family

• Product: Flexi Remote Radio Head 1TX 2100 (FRGG)

• Bands of operation: 2100MHz 3GPP Band B1 (FRGU)

• Number of carriers: up to 4 carriers (in 2 times 20 MHz BW)

• RF output power (max total power): 1x60W nominal RF power distributed amongst
supported number of carriers/sector;

• RX diversity: 2-way

• MIMO: no

• LTE ready: wcdma only

• Noise Figure (NF): 2.0 dB typical

3.1.6.4 Flexi RRH 2TX RF Module product family

• Products: Flexi RRH 2-pipe 900 80W (FHDA), Flexi Remote Radio Head 2TX 900 (FHDB), Flexi
Remote Radio Head 2TX 2100 (FRGQ)

• Bands of operation:

o 900MHz 3GPP Band B8 (FHDA, FHDB)

o 2100MHz 3GPP Band B1 (FRGQ)

• Number of carriers: up to 4 carriers (in 2x35 MHz or 2x60MHz BW)

• RF output power (max total power):

o 2x40W nominal RF power distributed amongst supported number of sectors


(typical:1→ 2x40W/sector) and number of carriers/sector: FHDA, FRGQ;

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
33 / 207
o 2x60W nominal RF power distributed amongst supported number of sectors
(typical:1→ 2x60W/sector) and number of carriers/sector: FHDB;

• RX diversity: 2-way

• MIMO ready

• LTE ready

• Noise Figure (NF): 2.0 dB typical

3.2 OUTDOOR SMALL CELLS PRODUCT

3.2.1 9364 Metro cell outdoor

• Frequency bands: 850MHz/1900MHz, 2100MHz

• 16/24/32 user capacity

• Max power: 250 mW

• Rx diversity

• Full rate HSPA

• 64QAM capable

• A-GPS

• PoE+

• NF: 13dB

• 2 external omnidirectional antennas

3.2.2 9764 LR MCO V1.0&V2.0

• Cube based

• Frequency bands: 1900MHz, 2100MHz

• 16/24/32 user capacity

• Max power: 1W

• Rx Diversity

• NF: 9dB

• GbE backhaul

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
34 / 207
• Wi-Fi optional

• 2 integrated directional antennas with 8 dBi gain

3.3 REPEATER

They can be differentiated by their means of connecting to the Node-B:

Fiber Link repeater

RF link repeater

3.3.1 Fiber optics repeater

Advantages:

The repeater can be located far from the Node-B

Possibility to feed several repeaters

Drawbacks:

High Cost

Propagation delay in the fiber limits the distance between the remote unit and the
NodeB

3.3.2 RF repeater

This repeater type is composed of two antennas:

Donor Antenna between the repeater and the Node-B: Highly directive antenna

Serving Antenna between the users and the repeater

It amplifies the signal both in the UL and in the DL independently or equally depending on the
repeater type.

The amplification concerns useful signal and all type of interferences

Advantages:

Cheap solution (can be frequency-translating to reduce interference)

Lower transmission delay than optical fibber

Drawbacks:

Mainly efficient in LOS

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
35 / 207
Requires good isolation between donor and serving antenna

RF noise amplification in UL and DL

RF noise constraint

The gain setting is very important for a repeater; extra noise is created by the repeater at the
Node-B for the uplink:

Noisewith _ repeater = Noisew / o _ repeater + ( Noiserepeater * GUL _ repeater ) / Coupling_ lossrepeater _ NodeB

With

Coupling_ lossrepeater _ NodeB


: UL path loss between Tx repeater connector and Rx Node-B
connector

GUL _ repeater
: repeater gain set in UL

For more details concerning repeater types see [R19] & [R4] linked in part 11 of this document.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
36 / 207
4 HSxPA
All the HSxPA parameters settings are detailed in [R7]and [R37] linked in part 11 of this
document.

4.1 HSDPA

The general approach is to assign a lower priority to HSDPA service than to the R’99 ones.
HSDPA introduces new common channels HS-DPCCH in UL and HS-SCCH in DL. This part
analyzes the impact of these channels and, also presents the throughput calculation method.

4.1.1 UPLINK IMPACT

The introduction of a new UL common channel induces a new spread signal value weight βhs for
HS-DPCCH added to existing R’99 spread signal value weight βc for DPCCH, and βd for DPDCH.
This has a direct impact on the PDCH UL power calculation, and on the UL Eb/No values.

The PDCH power calculation is given by the following formula

  2 + 2 
PDCH (dB ) = MaxUETxPow er (dB ) + 10 * log  2 c 2 d 
2 

 c +  d +  hs 

The Eb/No loss created by HS-DPCCH is given by the following formula:

 2 + 2 
LOSS = 10 log  2 d 2 c 2 
  d +  c +  hs 
The Eb/No loss values calculated for each UL R’99 service are the following ones. These losses
must be added UL Eb/No values for only HSDPA users in the cell and not all the cell users.

Eb/No loss (dB) for iCEM

PS64 1.9

PS128 1

PS384 0.4

Figure 13: HS-DPCCH Impact on UL iCEM Eb/No

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
37 / 207
Eb/No loss (dB) for xCEM

PS64 0.9

PS128 0.55

PS384 0.3
Figure 14: HS-DPCCH impact on UL xCEM Eb/No

4.1.2 DOWNLINK IMPACT

4.1.2.1 HS-SCCH

HS-SCCH is power controlled. It is calculated, based on an iterative process using the table
below.

Power relative to CPICH Power


CQI
(dB)

1–7 0

8–9 -3

10 – 12 -5

13 – 30 -8

Figure 15: HS-SCCH Power Control

In 9955, the HS-SCCH power control has not been implemented like this. The HS-SCCH power
control is based on Ec/No calculation, and the user had to specify an Ec/No target value. The
Ec/No formula is the following one.

PHS − SCCH
Ec / No =
Ie 1 1
( . Rxdiv _ gain / 10 +  ).PBS −  .PHS − SCCH + Pn .L. Rxdiv _ gain / 10
I i 10 10

With

PHS-SCCH: HS-SCCH power


L: path loss between MS and Node B
Ie: extra-cell interference (R99+HSDPA)
Ii: intra-cell interference

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
38 / 207
 : orthogonality factor

Pn: noise power


Pn = kTB +NF with k = 1.38.10-23 J/K, T = 293K, B = 3.84MHz, NF: mobile noise figure
PBTS: total transmitted power
 : advance receiver gain

After many simulations, based on the same path loss matrix, with our internal RF simulator, and
comparison with 9955 results, the Ec/No target value which provides realistic results in term of
cell throughput, throughput distribution, and area where HSDPA is supported is the following
one: Ec/No= -13dB

4.1.2.2 CPICH dimensioning with HSDPA

The aim is to have the same equivalence path loss point in UL and DL between two cells. This
point has been analyzed in part 2.2 of this document.

4.1.3 MUG tables

In order to calculate cell throughput in 9955, MUG tables have been extrapolated from Alcatel-
Lucent RF simulator considering 55% of PedB profile and 45% of PedA profile.

MUG tables have been provided by R&D and are set in 9955 RNP tool

4.2 HSUPA

The general approach is to assign a lower priority to HSUPA service than to the R’99 ones.

All the HSxPA parameters settings are detailed in [R7] linked in part 11 of this document.

HSUPA is only available on carriers where HSDPA is supported.

HSUPA introduces new channels

E-DPCCH in UL,

UL dedicated traffic channel: E-DPDCH

E-AGCH (Absolute Grant Channel), E-HICH (HARQ Indicator Channel) and E-RGCH (Relative
Grant Channel) in DL

This part analyzes the impact of these channels and the throughput calculation method

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
39 / 207
4.2.1 UL IMPACT

4.2.1.1 Description

The UL impact is very important.

As HSDPA, HSUPA has a lower priority compared to R’99.

E-DCH traffic is assigned the unused UL load up to the max. A R99 call cannot be dropped due
to an UL load increase caused by HSUPA.However, an increase in E-DCH RoT is comparable to an
increase of R’99 RoT (since R’99 UEs must transmit at higher level to be received correctly by
NodeB), which –if UL iRM Scheduling is activated– could cause the downgrade of high speed UL
PS calls (e.g. PS384 downgraded in PS128).

The Node-B noise figure is required in order to estimate correctly the UL load. It is highly
important to have a good reference value for the Node-B noise as it is the main input for UL
load computation

In R99/R5 networks, the design is usually done assuming 3dB max UL load (50% UL load).

In order to support high E-DCH throughput, this value should be increased, drawback is:

Coverage reduction for R99 traffic (mix carrier) considering the same R’99 dimensioning
service without downgrading
Higher interference
In order to limit the amount of interference, correct neighboring declaration is needed => UL
RSSI cleaning strategy required

The UL load recommended for HSUPA is 75%, so 6dB, in order to have good throughputs, which
can induce a reduction on R’99 UL coverage for mixed carrier configuration.

4.2.1.2 Analysis on different environments

This is confirmed by simulations on different environments Results obtained:


Dense Urban Urban Suburban

% UL load 50% 65% 75% 50% 65% 75% 50% 65% 75%

% of area supported for each UL load

(delta between supported service area supported @ 50% UL load & with other %of UL load)

UMTS 2100 93% 88% 83% 91% 86% 76% 91% 84% 70%
(-5%) (-5%) (-15%) (-6%) (-21%)
(-10%)

Figure 16: UMTS2100 study results

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
40 / 207
Based on these results, increasing the UL load to 75% reduces significantly the network service
area, and has a direct impact on the QoC and QoS.

In such cases a user which was able to establish a call at cell edge with 50% UL load; will have a
high risk of CAC failure at the same position with 75% UL load.

4.2.2 DL IMPACT

E-AGCH is enough for early deployment. In case there are two users, 2 TTI will be necessary to
grant both users.

E-RGCH is enough (up 15 signatures). The E-RGCH power is negligible, it carries one bit per user
signature

The activity factor of the E-AGCH and E-HICH should be low in early E-DCH deployment.

E-AGCH is not transmitted all the time (as for the HS-SCCH). Once the user is granted, E-AGCH
is not transmitted again.

A fix power is reserve at the RNC level for DL E-DCH channels. This power is preempted from
HSDPA max power and is taken into account in the R99 RNC CAC.

Power rel. to CPICH [dB]

-2.5 dB
E-AGCH
per user signature

-8.0 dB
E-HICH
per user signature

Figure 17: HSUPA DL power settings

The maximum HSDPA power signaled to the Node-B will be reduced.

The R99 CAC will reject R99 calls earlier than before in case of highly loaded cell.
2100MHz Node-B 45W PA
Speech CS 64 PS 64 PS 128 PS 384
30 m cable + 0.4dB jumper

Without HSUPA DL CCH


273kbps 565.8kbps 604.9kbps 681.5kbps 840.4kbps
impact

With HSUPA DL CCH impact 246.7kbps 511.2kbps 546.4kbps 615.6kbps 759.1kbps

DL capacity decrease due to


-9.6% -9.6% -9.6% -9.6% -9.6%
HSUPA

Figure 18: DL capacity loss due to HSUPA

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
41 / 207
9.6% capacity is a worst case, as it takes into account cells full loaded all the time. Around 5%
capacity loss can be expected, in standard case. This has been confirmed by studies and detailed
in document [R28].

4.2.3 THROUGHPUT CALCULATION

With HSUPA, the shared resource in the uplink is noise rise.

Based on the following inputs, the HSUPA throughput is calculated.

Max UL noise rise (R’99 + HSUPA)

Eb/No target table extracted from R&D simulations

For each cell, the remained UL noise rise available is evaluated, considering R’99 has the highest
priority.

Based on this, the path loss prediction, the UE power acceptable is evaluated in order to respect
the max UL load in the cell.

Then with the intra cell and extra cell interferences calculation, the max Eb/No value is calculated
per HSUPA mobile.

The throughput is obtained with the correspondence table between Eb/No value and
Throughput.

4.3 HSxPA carrier deployment strategy

The carrier strategy allocation for HSxPA deployment based on simulations is detailed in [R7]and
[R37] linked in part 11 of this document

fALU HSxPA implementation recommendations on existing R’99 outdoor networks are the
following ones:

• 2 carriers available
o 2 shared carrier R’99 & HSxPA
• 3 carriers available
o Option 1
▪ 1 carrier R’99
▪ 2 shared carriers R’99 & HSxPA
or
o Option 2:
▪ 3 shared carriers R’99 & HSxPA

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
42 / 207
4.4 HSPA+

HSPA+ is introduced in the 3GPP Release 7. It is an enhancement to HSDPA introduced in the


WCDMA protocol of R6. The use of the HSPA+ technology helps provide higher data rate on
downlink radio links and improve the throughput of a single user and cell capacity. Therefore,
the HSPA+ further improves the service experience of end users.

The HSPA+ benefits mobile operators and end users in the following aspects:

64QAM: DL 64QAM allows the use of 64QAM in HSDPA to increase the number of bits per
symbol and thus to obtain higher transmission rates. The peak rate at the MAC layer can reach
21 Mbit/s.

2x2MIMO: MIMO increases transmission rates through space multiplexing and improves channel
qualities through space diversity. The network side can dynamically select single- or dual-stream
transmission according to channel conditions. The peak rate at the MAC layer can reach 28
Mbit/s.

DL Enhanced Layer 2: This feature allows Uu L2 to use flexible PDU size on RLC layer and
segmentation on MAC layer. The feature prevents the L2 from becoming the bottleneck of
higher Uu rate increased by MIMO and 64QAM.

CPC: CPC allows the uplink and downlink transmissions to take place at periodic intervals. This
feature reduces the transmitted power (and thus increases the UE battery life) because the UE
does not have to monitor and transmit overhead channels every TTl. This reduction in the
transmitted power also helps to increase the uplink capacity by decreasing the total
interference. This improvement is especially significant when there are users who transmit data
infrequently as VoIP users. CPC feature consists of DL-DRX, UL DTX and HS-SCCH Less
Operation.

Enhanced CELL_FACH: Enhanced CELL_FACH operation allows the use of HSDPA technologies
for the UEs in the CELL_FACH, CELL_PCH, and URA_PCH state. The purpose is to increase the
peak rates in these states and reduce the signaling transmission delay during service setup or
state transition with the result improving the user experience.

The 64QAM and MIMO are the most important and commercialized features of the HSPA+
technology.

From the aspects of mobile operators and terminal users, the HSPA+ has the following
advantages:

- Expand the downlink capacity of the network and obtain higher spectral efficiency in the
case of higher SNR.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
43 / 207
The HSPA+ 64QAM provides a higher data transmission rate than the HSDPA.
Theoretically, if the 64QAM technology is adopted, the peak rate is 21.096 Mbit/s
(Formula: TB_Size/TTI = 42192 / 2ms = 21.096 Mbit/s).

Using the space diversity method, the MIMO technology adopts the multi-antenna
technology on the transmitting side and receiving side to improve the transmission
capacity of the radio communication system by several times without increasing transmit
power and bandwidth in the high SNR environment (the transmission capacity is in
proportion to the number of antennas). Theoretically, if the HSPA+ MIMO technology is
adopted, the peak rate is 27.952 Mbit/s (Formula: TB_Size/TTI = 27952 / 2ms x 2 (double
data stream) = 27.952 Mbit/s).

For operators, the use of the HSPA+ can reduce the unit cost for transmitting every
mega bytes of data stream, increase average system capability, enhance downlink data
service performance of a UE, and improves the cell throughput.

- Improve service performance of end users.

The HSPA+ offers a higher data transmission rate, short service response time, and
reliable service performance for a UE. Therefore, it improves the service experience of
the UE.

- Upgrade on the existing WCDMA network.

Mobile operators concern about the expenses for building an HSPA+ network. This
depends on the equipment price and the service strategies of a single operator. As a
high-rate data service enhancement technology in the WCDMA R5, the HSPA+ is
compatible with the HSPA of earlier versions and R99. The operator can upgrade NodeBs
in the existing WCDMA R99 network to introduce the HSPA+ with little impact on the
existing architecture. This helps shorten the network construction period and protect the
investments of the operator.

UE requirement

In R7, six categories of UEs (Category 13–Category 18) are increased to support the HSPA+;
category 13 and category 14 support only the 64QAM; category 15 and category 16 support
only the MIMO; category 17 and category 18 support the 64QAM and MIMO, but cannot use the
two technologies at the same time.

4.4.1 Overview of Basic HSPA+ Principles

In R6, the HSDPA increases a transmission channel (HS-DSCH) and three physical channels, that
is, HS-SCCH, HS-PDSCH, and HS-DPCCH. The HSPA+ still uses the preceding channels of the

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
44 / 207
HSDPA. However, the channel structure changes. At Node B, the HSDPA increases the multi-user
scheduling function and rapid retransmission function in the physical layer, Adaptive Modulation
and Coding (AMC), Hybrid Automatic Repeat Request (HARQ), and fast scheduling. These
technologies aim at improving the downlink user throughput and resource utilization. However,
the HSPA cannot support the rapid power control function and there is no combining gain of
downlink HSPA channels during soft handover. To support the high-speed data transmission
capability of the HSPA+, the Layer 2 Enhancement technology is introduced in R7 to flexibly
adapt to changes of the Uu interface. In addition, the 64 QAM and MIMO must be based on the
Layer Enhancement technology, that is, the two technologies can be implemented only when the
Layer Enhancement technology is supported. The R7 protocol specifies that a UE cannot adopt
both the 64 QAM and the MIMO at the same time

4.4.2 Key Technologies of HSPA+

4.4.2.1 Adaptive Modulation and Coding

The basic method of implementing the adaptive modulation and coding (AMC) technology is to
measure the quality of downlink channels and adjust the coding and modulation solution in an
adaptive manner based on the measurement result (expressed by CQI) to select the appropriate
modulation and coding rate to maximize the data transmission rate. The 1/3 Turbo code is the
basic code. The modulation modes include QPSK, 16QAM, and 64QAM. The 64QAM high-order
modulation which is a new function of the HSPA+ is used to improve the downlink peak rate.

4.4.2.2. HARQ

The Hybrid Automatic Repeat Request (HARQ) is an error correction technology. The HARQ
combines the forward error code (FEC) and automatic Repeat Request (ARQ) technologies. R99
adopts the traditional ARQ method that is implemented on the RLC layer. Similar to the HSDPA,
the HSPA+ adopts the SAW HARQ protocol. If the SAW HARQ protocol is adopted, for each
channel, the next data packet is transmitted only when the correct acknowledgement
information of the previous data packet is received. The protocol is simple, but the channel
utilization is low. The SAW HARQ protocol can solve the problem of low channel utilization.

4.4.2.3 Schedule

Similar to the HSDPA, the HSPA+ provides downlink HS-DSCHs for all the users to transmit data.
Resources are shared through code multiplexing and time multiplexing.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
45 / 207
4.4.2.4 Layer 2 Enhancement

Before the Layer 2 Enhancement technology is introduced in the R7 protocol, RLC PDU Size is
set to a fixed value. Due to the great change of the transmission of the Uu interface, RLC PDU
Size is usually set to 320 bits or 640 bits. By default, RLC Window Size is set to 2048. According
to the preceding typical configuration, the RTT delay between the data sending to the receiving
of the acknowledge message is 100 ms, and the supported highest transmission rate is
13.1Mbps (Formula: 640bits x 2048/0.1s = 13.1Mbps). This cannot meet the high-speed
requirement of the HSPA+. Therefore, the Layer 2 Enhancement technology is introduced. The
basic principle of the Layer 2 Enhancement technology is to introduce a variable length PDU in
the RLC layer. According to the protocol, the RLC layer supports up to 1500-byte PDU. In
addition, to support the Layer 2 Enhancement technology, MAC-ehs is introduced in the MAC,
and the related HS-DSCH FP changes.

4.4.2.5 64QAM High-Order Modulation

The 64QAM technology adopts higher order modulation to provide data traffic higher than the
HSDPA by quickly adjusting downlink modulation and coding mode in better radio environment.
Theoretically, if the 64QAM technology is adopted, the peak rate is 21.096 Mbit/s (Formula:
TB_Size/TTI = 42192 / 2ms = 21.096 Mbit/s)

4.4.2.6 2x2MIMO

Using the space diversity method, the MIMO technology adopts the multi-antenna technology
on the transmitting end and receiving end to improve the transmission capacity of the radio
communication system by several times without increasing transmit power and bandwidth in the
high SNR environment (the transmission capacity is in proportion to the number of antennas).
Currently, the typical scenario is 2x2MIMO, that is, dual-fed and dual-receiving mode.
Theoretically, if the MIMO technology is adopted, the peak rate is 27.952 Mbit/s (Formula:
TB_Size/TTI = 27952 / 2ms x 2 (double data stream) = 27.952 Mbit/s) Note that the 64QAM and
MIMO cannot be configured in the R7 protocol at the same time.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
46 / 207
5 UMTS CO-EXISTENCE WITH OTHER
TECHNOLOGIES
5.1 UMTS co-existence with other technologies in different or same frequency bands

Below a table where all the isolation required between UMTS and other technologies (except
LTE) is summarized. More details are available in guideline referenced in [R30] in part 11.

Figure 19: Isolation between UMTS and other technologies

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
47 / 207
In tables below isolation required between UMTS & LTE are detailed/More information on these
isolation are available in guidelines referenced as [R26], [R29], [R30], [R31],[R33], [R34],[R35]
and [R36] in part 11.

Figure 20: LTE vs. UMTS co-existence(1)

Figure 21: LTE vs. UMTS co-existence(2)

UMTS CO-EXISTENCE WITH LTE IN SAME FREQUENCY BAND

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
48 / 207
Figure 22: LTE vs. UMTS co-existence(3)

5.2 FREQUENCY OFFSET BETWEEN UMTS & GSM IN THE SAME BAND

UMTS allocated band is inside GSM or TDMA band

3GPP recommends blocking -47dBm GMSK signal with a 2.8MHz offset in UL, and -56dBm in DL.

To guarantee these recommendations, frequency spacing must respect 2.8MHz frequency


spacing should be respected between UMTS and TDMA or GSM Technologies. This is
corresponding to 200kHz frequency gap.

TCH on the 5 first adjacent channels

Figure 23: Frequency spacing rule between an UMTS carrier and


TDMA band

For both case analyzed below the degradation target is to have a sensitivity degradation less
than 0,5dB or a capacity loss lower than 5%.

Recommendations below have been done considering hopping TCH as GSM adjacent channels
of UMTS900 band.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
49 / 207
The best way to optimise frequency band used is to implement UMTS band in sandwich mode
like above

UMTS band positioning:

In order to avoid interferences provided by:

UE transfer from BCCH to TCH over the UMTS band,

Hopping between TCH over the UMTS band

The GSM channels adjacent of the UMTS band must support TCH with frequency hopping.

Below two cases are analyzed case where GSM and UMTS are co-localized on a same site and
case where they are not and so the worst configuration then is when GSM cell edge is close to
UMTS site

We have now two types of filters in our product,

• Standard filter whose attenuation starts at 2.2MHz offset from center frequency
which provides an attenuation higher than 50dB after 2.4MHz frequency offset
from center frequency

• Reduced filter whose attenuation starts at 2.0MHz offset from frequency band
center and provides more than 50dB attenuation after 2.2MHz frequency offset
from frequency band center. The impact reduced filter in DL is negligible

None co-located case:

Standard filter

ALU recommendation is to have 2,6MHz frequency offset

This implies that 5MHz must be free in upper or lower edge of the operator GSM
frequency band.

Reduced filter

ALU recommendation is to have 2,4MHz frequency offset

This implies that 4.6MHz must be free in upper or lower edge of the operator GSM
frequency band.

Co-located case:

Standard filter used in NodeB

Frequency hopping is done over less than 10 frequencies

ALU recommendation is to have 2,4MHz frequency offset

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
50 / 207
This implies that 4.6MHz must be free in the GSM frequency band on the area where
UMTS is deployed.

For the surrounded area of UMTS900/GSM900 cluster where only GSM900 is deployed, a
2.2MHz frequency offset is sufficient; this induces to free 4.2MHz.

GSM uses all 900MHz


band

Figure 24: Illustration of the buffer zone

Frequency hopping is done over more than 10 frequencies

ALU recommendation is to have 2,2MHz frequency offset

This implies that 4.2MHz must be free in upper or lower edge of the operator GSM frequency
band.

Reduced filter used in NodeB

ALU recommendation is to have 2,2MHz frequency offset without any frequency hopping
constraint

This implies that 4.2MHz must be free in the GSM frequency band on the area where UMTS is
deployed.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
51 / 207
All the analyses are included in the documents of [R8], [R26], [R29]and [R30] linked in part 11 of
this document.

In order to avoid interferences between GSM900 area where all operator 900MHz band is used
and UMTS900 cluster, it is necessary to have a buffer zone around UMTS900 cluster where only
channels which respect the previous recommendations are used.

This buffer zone is not homogeneous because generally environment is not homogeneous, as
sites can be positioned on a small mountain, so they have more coverage impact than those in
city center.

For this reason the rule to respect to define sites where all 900MHz band of an operator can be
used without impact UMTS900 cluster is the following one:

Let’s consider cell A as a UMTS900 cell of a UMTS 900MHz cluster, and cell B a GSM900 cell to
re-use channels inside UMTS900 band. BCCH cell B must respect

For RSCPcellA ≤ -100dBm: DL Rxlev_cellB ≤ RSCPcellA -10dB

5.3 FREQUENCY OFFSET BETWEEN UMTS & CDMA IN THE SAME BAND

3.385MHz frequency spacing should be respected between UMTS and CDMA frequency band

3.385MHz

270 kHz

Figure 25: Frequency spacing rule between an UMTS carrier and a CDMA carrier

All the analysis is detailed in the document [R31] linked in part 11 of this document.

5.4 FREQUENCY OFFSET BETWEEN LTE & UMTS IN THE SAME BAND

The requirement is that there is less than 0.5dB degradation on thermal noise floor on each
technology

No frequency gap required between LTE and UMTS. Studies for LTE& UMTS collocated and non-
collocated cases case have been done in guidelines referenced as [R34],[R35]and [R36] in part
11. For both cases no guard band is required to ensure less than 5% capacity degradation which
corresponds to less than 0.5dB sensitivity degradation.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
52 / 207
Figure 26: LTE and UMTS on a same frequency band

5.5 FREQUENCY OFFSET BETWEEN UMTS & UMTS IN THE SAME BAND

5MHz frequency spacing should be respected between two UMTS frequency bands.

Figure 27: Frequency spacing rule between two UMTS carriers

The following curves have been established considering the Tx filter and Rx filter of ALU product.
They show the capacity loss vs the frequency offset between two adjacent UMTS frequency
bands.

Figure 28: UMTS capacity vs adjacent UMTS interferer spacing (MHz) for co-located case (doted
line) and not co-located case

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
53 / 207
5.6 SOLUTIONS TO FREE FREQUENCY BAND

Several solutions are proposed for having 4,2MHz (co-located case) or 5MHz free (non co-
located case)

Fine GSM frequency plan with AFP tool

Decrease C/I targets but still maintain network quality

Increase the GSM1800 capacity by modifying the frequency plan to reduce the traffic on
GSM900. This can be possible when inter-site GSM 900 is in the same order than the
GSM1800, so generally in dense urban/urban.

Re-optimize the GSM900 frequency plan, in order to reduce the band used.

6 900 MHz
900 MHZ has been created in order to support UMTS technology in rural areas as 2100MHz
necessitates too many sites compared to 900MHz.

Anyway reusing GSM frequency band for UMTS imposes some frequency spacing rules.

We also see in this part what we can expect with 900 MHZ in rural environments and in dense
urban/urban environments where the limitation is essentially due to interferences.

6.1 ANTENNA SHARING SOLUTIONS

All the solutions specified here for antenna sharing between UMTS900 and GSM900 are also
available for other frequencies like UMTS850/GSM850 or UMTS1900/GSM1900.

6.1.1 Dual Duplexer solution

6.1.1.1 Description

GSM and UMTS emissions must be separated to avoid inter-modulation. This solution is a “Full
band” solution which means there is no need of frequency planning.

GSM BTS receives the RX signals of the both networks (high linearity LNA)

Attenuators allow reducing the UMTS signals, to be compatible with UMTS Node B.

UMTS Node B is in mode mix TMA. DC Blocks are used on the two 3G ways.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
54 / 207
Impact on the link budget

DL impacts:

Nothing in GSM (if GSM is transmitted on one antenna port before UMTS900
implementation)

0.5dB loss (0.7 max) in UMTS

UL impacts:

1 dB loss on GSM (not critical if DL limited)

0.3 dB on UMTS M&D

Drawbacks

UMTS900 and GSM900 transmissions must use separated antenna ports

• If GSM transmissions done on the two antenna ports before UMTS900


implementation then new Hybrid duplexer risk to be required: 3 dB impact on the
GSM link budget.

o To correct this, the solutions are:

▪ Increase PA power

▪ Increase antenna gain

RF cables shared in emissions and reception

• GSM and UMTS cable length must be identical

• GSM BTS and UMTS Node-B must be at the same distance from the antenna

Cabinets must be close from each other

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
55 / 207
6.1.1.2 2G Equipment requirements

Whatever the site configuration, RF interface have to be met in any case

• GSM specs 3GPP TS 05.05 are applicable

• UMTS specs 3GPP TS 25.104 are applicable

UMTS BTS performance shall not be degraded by 2G BTS

Alcatel-Lucent defines a system requirement, that translates into 2G BTS requirements and
Dual-duplexer requirements.

RX_link definition is part of system specification:

Without TMA

Figure 29: Configuration without TMA

RX_link = Dual-duplexer+W4+2G BTS+W5+Dual-duplexer+W6

With TMA

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
56 / 207
Figure 30: Configuration with TMA

RX_link = TMA+W2+Feeder+W3 +Dual-duplexer+W4+2G BTS+W5+ Dual-duplexer+W6

The 2G BTS must be able to receive useful signal in UMTS Bandwidth

In this band the following criteria must be respected, by the 2G BTS

Gain RX_link 9 dB ±1.5 dB

NF < 3.5 dB

at BTS input access < 5 dB (DDM in TMA Mode)

UMTS blocking level

In RX Band at @ ±10 MHz - 40 dBm

Out of RX band @ ±20Mhz - 15 dBm

6.1.2 UMTS900-GSM900 Twin TMA combiner solution

GSM and UMTS emissions are separated.

Figure 31: example of UMTS-GSM combiner type

The combiner must be placed at BTS level and not at antenna level in order to avoid doubling
the cables along the pylon

Several way of implementation

▪ Case1: no existing TMA on GSM site, 2 options:

▪ Option 1 :TMA supported by GSM BTS

▪ Configure BTS UMTS is in mode mix TMA.

▪ TMA required for UMTS900

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
57 / 207
▪ UMTS-GSM combiner can be configured in active
mode with 9dB to 10dB TMA gain depending
on the product
Figure 32: Configuration with UMTS-GSM combiner only

▪ The impact on the link budget is

▪ DL impacts: 0.5dB loss in UMTS &GSM

▪ UL impacts: 0,4dB loss in UMTS &GSM

▪ Option 2: TMA not supported by GSM BTS

▪ Configure BTS UMTS is in mode no TMA.

▪ UMTS-GSM combiner can be configured in passive mode

▪ The impact on the link budget is

▪ DL impacts: 0.5dB loss in UMTS &GSM

▪ UL impacts: 4.5dB loss in UMTS &GSM

▪ Case2: Existing TMA on GSM site,

▪ Solution 1:

▪ Remove TMA and implement UMTS-GSM combiner


in active mode to obtain the same configuration than
case 1 option 1 configuration analysed above

▪ Solution2: if TMA is not removed

▪ BTS UMTS is in mode mix TMA.

▪ UMTS-GSM combiner should be configured in passive mode

▪ Impact on the link budget

▪ DL impacts: 0.5dB loss in UMTS &GSM

▪ UL impacts:

▪ 4.5dB loss for GSM compare to


configuration before UMTS900 implementation

▪ UMTS: no loss compared to a configuration


without TMA
Figure 33: Configuration with existing TMA and UMTS-GSM combiner

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
58 / 207
Drawbacks

UMTS900 and GSM900 transmissions must use separated antenna ports

If GSM transmissions done on the two antenna ports before UMTS900 implementation
then new Hybrid duplexer risk to be required: 3 dB impact on the GSM DL link budget

Some GSM BTS cannot manage TMA; an attenuator must be added when combiner is used in
active mode with 8dB gain

6.1.3 Double dual antenna solution

Figure 34: Double dual antenna

Currently this type of antenna exists only in 900MHz band, but RFS, and power wave are
studying to combine 900MHz, and 1800-2100MHz band, in order to have a solution for bi-band
or tri-band antennas.

Advantages:

Tilt can be changed independently per sector without any impact on the existing sites

Max efficiency if well installed

No signal mixed on the same antenna (avoid blocking, or inter-mod problems)

The RF problems are minimized.

Same pylon than a standard dual antenna can be used

No impact on GSM even if GSM900 used two antenna ports before UMTS900
implementation which is not the case for combiner solutions

Drawbacks:

• Antenna width 1.5 larger which induces a highest wind loading than a single
antenna. The pylon must support it

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
59 / 207
• Number of cables along pylon are doubled

6.1.4 MC-RRH & MC-TRX

MC-RRH & MC-TRX are solutions to deploy UMTS900 & GSM900 sharing Xpol antenna.

For summary of these products see parts of 3.1.1.6 and 3.1.2.4.

6.2 LB COMPARISON UMTS900/UMTS2100

6.2.1 Description

The table below summarizes the different parameters change between 900MHz and 2100 MHz.

+ qualify a gain provides by 900MHz compared to 2100MHz

- qualify a loss provides by 900MHz compared to 2100MHz

45W MCPA output power is used at 2100MHz and 55W SCPA is used at 900MHz.

Dense urban
Rural Suburban
/Urban

Radio propagation path loss + 7 dB + 8dB + 10dB

Node-B sensitivity -0,5dB

Node-B antenna gain -1 dB -1 dB -1 dB

UE antenna gain 0 dB 0 dB 0 dB

Feeder losses + 3dB/100m

PA power difference +1dB

UE noise figure (DL only) - 3 dB -3dB -3 dB

Penetration losses ( incar for


+2dB +2dB +2dB
rural, indoor for urban, suburban)

Figure 35: parameters comparision between 900MHz and 2100MHz

Based on this table, the following gain can be expected, for

40 meters cable length in rural,

30 meters cable length in dense urban, urban, suburban

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
60 / 207
Rural Dense urban
Configurations Suburban
Incar/outdoor /Urban

+6,5 dB/+4,5dB in
+ 7,5dB in UL +10,5dB in UL
2100 MHz with TMA and UL

900MHz without TMA


+ 7,5 dB in DL +10,5 dB in DL
+7dB/+ 5dB in DL

+9 dB/+7dB in UL + 9,5dB in UL +12,5dB in UL


2100 MHz without TMA and

900MHz without TMA


+6 dB/+4dB in DL +6,5dB in DL +9,5dB in DL

Figure 36: 900MHz gain expected per environment

6.2.2 Comparison between 2100MHz and 900MHz for TMA recommendations

TMA impact is the UL cables losses reduction.

In rural environments, UMTS 900 should be positioned on GSM 900 sites, and the aim is to have
the same coverage. As GSM900 do not have any TMA, it seems not necessary to use one for
UMTS.

If 900 MHz should replace a 2100MHz site in order to extend coverage, TMA using is not
necessary.

Based on the previous table, the comparison between 900MHz and 2100MHz with TMA, for 40m
cable length in rural area, shows 3 dB UL gain with 900MHz configuration. Such difference
represents more than 70m 7/8” cable length. So 900MHz configuration does not require TMA
since 7/8” cable length do not exceed 110m.

For urban areas TMA are used at 2100MHz to increase chances to cover deep indoor areas, but
with 900MHz, the TMA using is not necessary as the indoor coverage is ensure due to the lower
frequency.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
61 / 207
6.3 LB COMPARISON GSM900 vs UMTS900

The both link budget have been compared for rural environment considering the following
assumptions:

UE antenna gain: 0dBi

Slant loss: 2.5dB

7/8” cable length: 40m

Node B antenna gain: 17 dBi

GSM UE output power: 2W and 0.8W

UMTS UE output power: 24dBm

Voice available path CS 64 available path loss


Available pathloss
loss (dB) (dB)

GSM900

UE output power: 2W 143,9/ 144,5

(PA 30W/ PA 60W)

GSM900
140,5
UE output power: 0.8W

UL load: 30%

UMTS900 144 141,5

UL load: 50%

UMTS900 142.5 140

Figure 37: UMTS900 link budget comparison with GSM900

Based on the previous analysis, TMA is required in order to ensure same coverage as GSM900
in case where UL CS64 is the dimensioning service.
For an UL load higher than 30%, a TMA is required for UMTS900 to reach the same coverage
radius than with GSM900.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
62 / 207
6.4 UMTS900 vs UMTS2100 PERFORMANCES COMPARISON

6.4.1 COVERAGE COMPARISON

The impact of 900 MHz on the number of sites compared to 2100 MHz has been simulated
with 9955. The design approach is exactly the same than for 2100MHz, but the UL
dimensioning service could be PS64 in rural, and PS128 in urban.
Based on this study, a 40% reduction on the number of sites can be expected with 900 MHz
compared to UMTS 2100, in rural environment.
900 MHz allows deploying sites at the same positions than GSM 900 ones. 900 MHZ antennas
can re-use GSM900 antennas with dual duplexer using without impacting significantly GSM900
cell radius.

With this solution, the azimuths and tilts cannot be changed without impacting GSM900
network.

The study done is summarized below.

18 sites, 48 cells for 300km²

Inter-site distance around 7km

Mean antenna height: 40m

Dimensioning service considered is: CS64 UL.

10% CPICH power ratio

36dBm output cabinet pilot power at 900MHz

35 dBm output cabinet pilot power at 2100MHz

The RSCP targets to guarantee CS64 UL service are

-92 dBm at 900MHz

-94.5 dBm at 2100MHz

Results:

With 47% less 900MHz sites the coverage CDF is quite indentical than with 2100MHz network

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
63 / 207
6.4.2 CAPACITY COMPARISON

6.4.2.1 Assumptions

A study based on simulations has been done in order to show the impact and possible benefits
of UMTS 900 compared to UMTS 2100, for R’ 99, HSDPA and HSUPA.

Several assumptions have been done in order to guarantee a correct performance comparison
between UMTS2100 and UMTS900.

This study has been done based on the same R’99 call profile, on urban environment

Different cases of UMTS900 sites deployment have been considered:

Case 1: Same number of site between UMTS 900 & UMTS 2100. This case characterise a
dense UMTS900 deployment in urban area

Case 2: Number of UMTS900 sites deployed must be sufficient to support the same R’99
traffic density over the same area. This case characterise a mature UMTS900
deployment in urban area

Case 3: Number of UMTS900 sites deployed must be sufficient in order to guarantee the
same CPICH QoC than with UMTS2100.

The UMTS 900 sites are positioned only where there are UMTS2100 existing sites. Only electrical
tilt can be changed.

The main RF assumptions are detailed in the following table:


UMTS 2100 UMTS 900

Node-B Antenna Gain [dBi] 18 17

Node-B Noise Figure [dB] 2.5 3

Cable Losses [dB per 100m] 7 3.8

PA [W] 45 (i.e. 45.2dBm 55 (i.e. . 46.1dBm


output cabinet) output cabinet)

CPICH Tx Power 10% * PA

TMA Used Not used

Body Loss [dB] Speech: 3dB, Data: 1dB

UE Antenna Gain [dBi] 0

UE Noise Figure [dB] 7 10


Figure 38: Assumptions

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
64 / 207
6.4.2.2 Performances improvement

Case1
R99 capacity gain with UMTS900 (Dense urban/ suburban) + 20%/ +40%

HSDPA mean cell throughput gain with UMTS900 (Dense urban/ suburban) + 21%/28%

E-DCH mean cell throughput gain with UMTS900 (Dense urban/ suburban) + 5%

Difference of area supported with 75% UL load between UMTS900 and


+ 15%/+20%
UMTS2100 (Dense urban/ suburban)

Figure 39: Case1 results

Case2

Site reduction with UMTS900 for a same capacity network (Dense urban/
29% / 44%
suburban)

HSDPA mean cell throughput gain with UMTS900(Dense urban/ suburban) 16% / 21%

E-DCH mean cell throughput gain with UMTS900 (Dense urban/ suburban) + 5%

Difference of area supported with 75% UL load between UMTS900 and


12% / 20%
UMTS2100 (Dense urban/ suburban)

Figure 40: Case2 results

Case3

Site reduction for a same pilot QoC (Dense urban/ suburban) 58%/ 48%

R99 capacity gain with UMTS900(Dense urban/ suburban) -60% / -20%

HSDPA mean cell throughput gain with UMTS900 (Dense urban/ suburban) 16% /21%

E-DCH mean cell throughput gain with UMTS900 ( Dense urban/ suburban) + 1%

Difference of area supported with 75% UL load between UMTS900 and


7%/12%
UMTS2100 ( Dense urban/ suburban)

Figure 41: Case3 results

Based on these results, our recommendation is to start a deployment in UMTS900, in order to


support same pilot QoC like case3, then to evaluate to case2, if the traffic demand increase.

The improvement from case2 to case1 doesn’t seem significant and required 30% more sites.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
65 / 207
6.4.3 UMTS900 DEPLOYMENT STRATEGY

6.4.3.1 Dense Urban / Urban

Three scenarios can be considered

Hot spot

 UMTS 900 could be deployed in limited area, in order to

• Improve deep indoor penetration

• Improve capacity

UMTS900 sites deployed to ensure better deep indoor RSCP and complete 2100MHz
layer (case3)

 This ssolution allows having a homogenous layer with around 50% less
sites than 2100MHz layer.

 It supports HSUPA max throughput without coverage reduction, and also a


better HSDPA cell throughput.

 This solution is appropriate for an earlier phase which requires only deep
indoor coverage improvement but not necessarily a capacity
improvement, as the traffic density supported is 40% to 58% less than
2100MHz layer.

UMTS900 deployed to ensure a better deep indoor RSCP and same capacity than
2100MHz layer

 Deployment to support same traffic density than 2100MHz layer ( case2)

• Solution for mature network

• Required 25% less sites than 2100MHz layer

• Improve HSUPA max throughput area

• Improve HSDPA cell throughput and traffic density

6.4.3.2 Suburban/Rural

Deployment to support same RSCP distribution than 2100MHz layer (Suburban)

• Recommended to have a homogenous layer with at least 48% less sites

• Support HSUPA max throughput without coverage reduction

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
66 / 207
Better HSDPA cell throughput

• Best compromise as the traffic density supported is between 20% less than
2100MHz layer

Deployment without any existing UMTS layer

• Suburban

 Deploy the number of sites required to reach -95dBm RSCP value over
95% of the area. Re-use a maximum of existing GSM sites

• Rural

 Re-use GSM900 sites in order to deploy UMTS900 layer which complete


UMTS2100 layer essentially deployed in urban areas.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
67 / 207
7 CAPACITY & COVERAGE IMPROVEMENT
SOLUTIONS
7.1 RF solution for coverage improvement

This part details basic solutions to improve coverage, essentially for rural.

7.1.1 Height tower increase:

The coverage gain expected is between 15% (from 30m to 40m) to 40% (from 30m to 60m).

The drawback of this solution is the cost, and the difficulty to negotiate some sites over 40
meters.

7.1.2 Space diversity:

It cancels the slant polar loss which provides 1.5 dB gains in urban and 2.5 dB gain in rural, but
requires at least a 10 wavelength spacing between antennas. So it can only applied in rural due
to the lack of place and the difficulty of adding an antenna on the roof tops in urban areas.

7.1.3 4 way receivers

The gain expected by 4 way receiver is around 2 dB in uplink, but it requires:

4 Vpolar antennas per sector which is not realistic even in rural or 2 Xpolar antennas.

2 ddm per sector are required

Cable length must be identical between each way

But in that case, 4 way receivers just cancel slant polar loss, and it is as efficient as space
diversity.

The only way to have an improvement compare to space diversity solution is to use 21 dBi H65°
antenna, which is possible only in rural, and at 2100MHz.

These antennas are only available in Xpolar. The combination with such antennas and 4 way
receiver gives a better improvement than space diversity.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
68 / 207
7.1.4 RRH vs Macro-Node B

This is a good solution to eliminate cables losses for any rural site.

It can be easily applied in chain configuration along railways, motorways as optical fiber is
available.

For coverage comparison two cases have been analyzed, considering the UL coverage limitation

Macro without TMA vs RRH

The UL path loss difference between Node-B configuration and RRH configuration
is equal to the cable losses between Node-B cabinet and 7/8” top mast
connector.

Generally based on same UL service with same antenna type:

RRH cell radius configuration > Node-B cell radius configuration is except if

RRH - antenna connector cable losses= Node-B- antenna connector cable losses

Macro with TMA vs RRH

UL cable loss with TMA is 0.8 dB (0.4dB due to jumper between TMA an antenna,
0.4 dB between Node-B and TMA) for any cable length.

Generally based on same UL service with same antenna type:

RRH cell radius configuration = Node-B cell radius only if

RRH - antenna connector cable losses < 0.8 dB

As 0.4 dB jumper loss can not be reduce, the cable losses which can be add
between RRH and antenna should be lower than 0.4 dB.

Based on this the max cable length between RRH and jumper supported in order
to have RRH 20W cell radius configuration = Node-B cell radius configuration, is
6m.

In case of the cable is higher than 6m which can happen if the pylon cannot
support RRH + antennas then RRH can be positioned at the same area than Node-
B, with a TMA; so the cell radius is the same than with the Node-B configuration

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
69 / 207
Figure 42: Node-B and RRH configurations

7.1.5 REPEATER

Repeater can be used to extend coverage in all environment types, but the approaches are
different.

In rural, repeaters are used to resolve hole of coverage problems, due to local obstacles.
Generally RF repeaters are used particularly in hilly environment, as optical fibers are not
available.

The requirements for RF repeaters in rural conditions are:

To be in LOS conditions with Source Node-B

Highly Directive donor antenna in LOS

High Output Power Repeater for big cell range

RX diversity increases UL available path loss

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
70 / 207
Repeaters can also be used in urban environment. The aim is to resolve local hole of coverage or
to enhance indoor coverage.

Repeater should not be linked to a cell already full loaded.

RF repeater UL and DL gains should be set taking into account the following aspects:

UL repeater gain increase risks decreasing Node-B sensitivity

A repeater placed far from the Node-B needs to have a high UL gain in order to be able
to transmit and receive signal.

The aim is to find the best compromise in order to extend coverage enough without polluting
Node-B.

The repeater should be placed not at cell border but before: leads to better signal for users at
cell border (TX Power saved) and reduces desensitization effect

The gains are set to ensure the coverage expected, and not necessarily at maximum output
power (to limit noise rise)

The rule to avoid an UL interference increase due to repeater using is to have


( Noiserepeater * GUL _ repeater ) / Coupling_ lossrepeater _ NodeB
equals to 0dB in order to have

Noisewith _ repeater = Noisew / o _ repeater


see the equation part 3.3.2.

Gt = G BS − L + G Donor + GUL
This rule is also written with another equation: (in dB)

With

GBS
: Node-B antenna gain

GDonor
: Donor antenna gain

GUL
: UL repeater gain set

L : path loss between Node-B antenna and the Donor antenna


Gt
must be equal to 0 dB in order to avoid interference increase at the Node-B level.

The % of capacity improvement is directly linked to the % of traffic in the area covered by the
repeater compared to the traffic supported by the serving cell.

This is detailed in the presentation [R4] linked in part 11 of this document.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
71 / 207
7.1.6 EXTENDED & ULTRA-EXTENDED CELL SOLUTION

The software feature extended and ultra extended cell allows the extension of the
synchronization window in order to support time delay which corresponds to cell radius up to
150km.

The Cell size and Tcell parameters setting are described in document [R18] linked in part 11 of
this document.

Even if the time delay can be managed in order support such cell radius, the radio propagation
conditions must be ideal to reach such distance which means that they must be near the free
space conditions.

In free space 142dB path loss can cover 150km distance.

Such conditions can only be found over sea, big lakes, or other 200km flat area; no obstacle is
allowed to support such distance.

The second aspect is the earth rotundity; which start to have an impact on a radio link when
distance exceeds 30km, even if the environment is flat.

To avoid the earth interference on the radio link the transmitter and receiver must be in visibility
(LOS).

Considering a 200km flat environment and a receiver height between 1.5m and 2m, the
transmitter height must at least have the following values in order to ensure the different cell
radius.

Cell radius 50km 60km 70km 80km 100km 150km

Transmitter
antenna height 90m 140m 200m 250m 400m 900m
@2100MHz

Transmitter
antenna height 70m 100m 140m 200m 350m 800m
@900MHz

Figure 43: Transmitter height required in flat environment to support long cell radius

7.1.7 SAME CELL RADIUS WITH UL LOAD INCREASE (HSUPA)

The UL load increase has a direct impact on the cell radius. The aim of this part is to propose
solutions in order to keep the same cell radius even with UL load increase. The UL load increase
appears only in dense urban and urban areas, so only these environments area considered here.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
72 / 207
7.1.7.1 4 way receivers

This is the same solution, than the one used to increase cell radius in rural environment.

The hardware constraints are the same than those detailed in part 7.1.4.

Advantages Drawbacks

Second antenna implementation per


2dB UL gain sector is required

Very hard to negotiate in urban area

Figure 44: 4 way receiver gain and constraints

7.1.7.2 21 dBi antennas

One solution to compensate coverage reduction due to UL load increase is to increase antenna
gain.

65° H beam antennas

There is some existing 21dBi 65°antenna “Cellmax.

The drawback is the height increase compared to 18dBi antenna, which can be hard to
negotiate.

30° H beam antennas

As antenna height is limited in urban areas in major European countries, using 30°
antennas instead of 65° ones is one way to increase by 3dB antenna gain.

30° horizontal beam antennas allows a high gain considering 7° vertical beam width like
current 65° H beam antennas used in urban areas.

To keep same overlap between sectors of a same site is to increase the number of
sector per site.

The current Node-B can support 6 sectors by adding 6 MCPA.

The mix cabinet (classical Node-B and RRH, see the picture below) can also be used in
order to increase the number of sectors per sites.

It is a classical cabinet modified to create mix cabinet able to deploy 1 standard 3 cells
site and in addition up to 3 RRH modules.

The drawbacks are:

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
73 / 207
Increase the number of sector per site required increasing the number of
antennas which is very hard to negotiate

Adding some sectors required azimuth re-optimization of all around sectors

Changing antenna type can be a problem on GSM/UMTS sites with shared


antennas as 30° antennas are not necessary for GSM.

New neighboring plan required

New scrambling code plan required

Figure 45: 6 sectors mix cabinet configuration

7.1.7.3 UMTS 900

All the details of 900MHz coverage impact have been analyzed in parts 6.2 to 6.3.

7.2 RF SOLUTIONS FOR CAPACITY IMPROVEMENT

In the design strategy the solutions to support capacity increases should be analyzed according
to the customer

Features

New carrier implementation

RRH

900 MHz

HCS network

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
74 / 207
Sites densification…

7.2.1 TX DIVERSITY FEATURE

Transmit diversity feature is a solution to improve capacity of an existing network.

Transmit diversity gain in term of Eb/Io

Eb/Io gain vs. no Tx Div speed “<10km/h” speed “~50km/h” High speed “>50km/h”

Open loop 1 dB 1 dB 1 dB

Close loop 3 dB 1 dB 0 dB

Figure 46: Tx div gain table

CPICH power transmitted on two ways requires 1 dB more power

HSDSCH traffic use same Tx div scheme as associated DCH - scheduler selection impacts
performance gain as Tx div reduces power variance

Use Cases

HSDPA throughput increase for slow UE: +15% to +30% (system level simulation)

DCH capacity: +15 to 44% - STSR1+1: one carrier for HSDPA, one for DCH

Spectrum efficiency need for re-farming 900 MHz frequency band

[R20] linked in part 11 of this document detail this feature.

The gain expected is around 10% of capacity improvement, with a main constraint of adding a
second PA. This feature is not supported yet.

7.2.2 CAPACITY COMPARISON BETWEEN 1, 2&3 CARRIERS CONFIGURATIONS

In case of large area lacking capacity, a second or third carrier can be added.

The capacity with 2 carriers is expected to be a little bit less than 2 times the capacity of 1
carrier with an optimized management of the carriers.

Using 2 or 3 carriers over one MCPA may imply reduction of power available per carrier; this
method is essentially used in interference limited areas. If the power reduction per carrier has an
impact on the DL cell radius because the pilot Ec/Io or RSCP is not reached, the solution is then
to add a new PA dedicated to the new carrier, in order to keep the cell size and to improve
sector capacity.

The table below presents the capacity for different PA power and different number of carrier.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
75 / 207
Dense Urban environment

Cell size – service dimensioning CS 64; Cell size = 620 m;

Cable losses: 3 dB; TMA + jumper: 0.8 dB UL loss

User profile: VehA 3km/h

UE NF=7dB

Total Power Speech CS64 PS 64 PS 128 PS 384 HSDPA


@cabinet connector # Carriers
(@ output PA) (kbps) (kbps) (kbps) (kbps) (kbps) (kbps)

20 W (30W) 1 440,4 842,7 923,4 995 1088 1591.7

30 W (45W) 1 545,7 980,3 1074,2 1157,4 1266,6 1873,7

2610,4

2 667 1286,6 1497,6 1613,6 1763,8 (If HSDPA on 2


freq)

40 W (60W) 1 615,3 1062,5 1164,3 1254,4 1372,8 2157.1.0

3183,4

2 880,8 1685,4 1846,8 1990 2176 (If HSDPA on 2


freq)

3973,4

3 1000,5 1969,9 2246,4 2420,4 2648,7 (If HSDPA on 3


freq)

Figure 47: DL capacity obtained with different number of carriers and power configurations

7.2.3 Dual Cell

Dual Cell feature allow to a UE to use two carriers in order to increase the potential peak
throughput.

This feature allows flexibility in resource management.

The capacity gain between Dual cell vs two carriers without dual cell feature has been estimated
by simulation around 7%. The simulation conditions are detailed below:

• Propagation model: Okumura Urban

• Cell radius: 1km (or inter-site distance = 1732m) on a hexagonal grid

• NodeB antenna height: 12m; UE antenna height: 1.6m

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
76 / 207
• RRH 40W

• No cable loss (i.e. cable from NodeB to antenna)

• 10 UE per cell

• Cat-14 for single carrier baseline;

• Cat-24 for DC HSDPA.

• 12 cell network with wrap around

• FTP with file size of 20GB (i.e. the FTP continues throughout the simulation)

• Composite channel:25% AWGN 1.5km/h, 37% Ped.A 3km/h, 13% Ped.A 30km/h, 12%
Veh.A 30km/h, 13% Ped.A 120km/h

• No UE Rx diversity

urban 1km 40w: user gain=7.6%, cell gain=7.6%


1

0,9

0,8

0,7

0,6
CDF

0,5
cat-14 user
0,4
cat-24 cell
0,3 cat-14 user
0,2 cat-14 cell
0,1

0
0 1000 2000 3000 4000 5000 6000 7000 8000

kbps

Anyway such gain seems very difficult to evaluate on the field

7.2.4 RRH vs Macro-NodeB

The comparison between RRH and Macro NodeB is done in the table below, what is the main
information to extract from this table is more the relative capacity comparison between each
solution instead of the absolute capacity value per comparison which depends one user profile
and other parameters

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
77 / 207
Cell radius PS64 PS128 PS384 HSDPA
Speech (kbps)
(m) (kbps) (kbps) (kbps) (kbps)

Without TMA

RRH 20W/carrier with 0.4dB


660 942.3 1032.6 1112.5 1217.5 1820.1
jumper loss

NodeB 45W PA (30W TOC) with


550 545.7 1074.2 1157.4 1266.8 1874.2
30m cable +0.4dB jumper loss

NodeB 60W PA (45W TOC) with


550 620 1169 1258 1381 2020
30m cable +0.4dB jumper loss

TRDU 40W or RRH 40W with 30m


550 625 1176 1269 1389 2032
cable +0.4dB jumper loss

RRH 40W with 0.4dB jumper loss 660 779 1322 1434.8 1568.3 2309

TRDU 60W & RRH 60W with 30m


550 799.9 1371.7 1468.6 1608.2 2342
cable +0.4dB jumper loss

RRH 60W with 0.4dB jumper loss 660 909.9 1481.7 1572.6 1698.2 2445

With TMA

NodeB 45W PA (30W TOC) with


660 541.7 1070 1151 1262 1870
30m cable +0.4dB jumper loss

NodeB 60W PA (45W TOC) with


660 610 1158 1247 1368.8 2008
30m cable +0.4dB jumper loss

TRDU 40W or RRH 40W with 30m


660 615.3 1164.3 1254.4 1372.8 2012
cable +0.4dB jumper loss

TRDU 60W & RRH 60W with 30m


660 782 1353.7 1458.6 1596 2335
cable +0.4dB jumper loss

Figure 48: Capacity comparison between Macro NodeB and RRH configuration

7.2.5 UMTS900 implementation

All the details of 900MHz capacity impact have been analyzed in part 6.4.2.

7.2.6 SMALL CELL-CELL LAYER

In part 8.7, small cell-cell layer deployment is analyzed. The gain expected, the constraints and
limitations of each strategy are detailed.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
78 / 207
7.3 SITE SECTOR INCREASE

The current Node-B can support 6 sectors by adding 3 MCPA to an existing 3 sector site.

The mix cabinet (classical Node-B and RRH, see figure 34) can be used in order to increase the
number of sectors per sites. It is a classical cabinet modified to create mix cabinet able to
deploy 1 standard 3 cells site and in addition up to 3 RRH modules.

This allows increasing site capacity.

If more than 4 sectors are implemented on a same roof top, then it is advised to use 30°
horizontal beam width antenna, in order to avoid a too important overlap between sectors.

Adding some sectors required:

Azimuth re-optimization of all around sectors

As 30° antenna gain is 21dBi, this increase the sector cell radius, and a down-tilt
optimization.

All the hardware constraints and drawbacks are the same than those described in part 7.1.7.2.

The capacity improvement expectation is at least 70% compared to a 3 sector site.

Anyway considering the heavy impact on RF optimization, site negotiation; the first solutions to
improve capacity is increasing the number of carrier, by adding if necessary another new PA
(STSR2+1) or changing the existing one to a powerful one (STSR3 with 60W PA).

Such configuration provides 47% capacity improvement, and requires less HW change and RF
activities.

7.4 SITE DENSIFICATION

The last solution to increase network capacity is to density the number of sites.

This solution is the most expensive, and the most complex, that’s why it is only used when all
others have been applied.

Adding sites necessitate

Finding new sites (hard negotiation)

A RF survey and site acquisition (see part 8.2 of this document)

A RF re-optimization of the existing sites all around the new one

This induces change of antennas azimuths and tilts.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
79 / 207
8 RADIO DESIGN METHOD FOR MACRO-CELL
NETWORK
8.1 OVERVIEW

Propagation model calibration


GSM sites reused for UMTS Geographical databases

Sites candidate validated after CW measurements


RF survey

LB max available path loss based on:


Service dimensioning

RSCP & Ec/Io targets Engineering margins

Traffic load

RF Design done with Radio network


Planning (RNP) and Automatic Cell Planning
(RNP)

• Site selection
• Antenna tilt and azimuth optimization
• Neighbors Planning realization
• Scrambling code planning realization

Radio parameters field


implementation

Field network validation

Figure 49: Roll out phase steps

8.2 MACRO-CELL SITE ACQUISITION

The site acquisition problems must be taken into account at the beginning of the radio planning,
as the sites analyzed must correspond to those which are going to be implemented on the field.

Generally the customer should provide the site candidates positions, and the GSM existing sites
positions which generally should be re-used.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
80 / 207
The customer request is generally to re-use a maximum of existing sites and to not have any
new sites implementation.

Based on this request, it is better to have two UMTS sites implemented in existing GSM sites
positions instead of having 1 new site implemented only for UMTS. Anyway sometimes, there is
no other way than implementing a new 3G site, in order to reach radio QOC and QOS, the aim is
to reduce a number lowest as possible.

8.2.1 Site survey

Even if the sites positions are proposed by the customer, they must be analyzed and validated
by Nokia.

Radio site search and validation is an important step in the UMTS radio network planning and
implementation.

It allows identifying

If a site is good for coverage required, by detecting some masks which have not been
seen with radio planning tool.

Detection of pattern distortion risk due to the environment and the structure near the
antenna

Analysis of the antenna height compare to the nearest environment. A site must not be
too high relative to its environment, except if only coverage is the constraint, because it
increases inter-cell interferences.

All the type of equipment available on the rooftop, and their frequency band. Based on
that it can be deduced what type of antenna is required, and where to position it in order
to avoid interferences created by co-sitting.

Spurious signals in the UL band.

The difficulty in finding sites is a critical issue for UMTS projects since UMTS come after GSM and
several other radio systems; the available sites are very limited in most of the cities. The
constraint on site construction is more and more important.

[R8] & [R10] linked in part 11 of this document intend to give radio engineers the guidelines
and rules on radio site engineering, search and validation.

Antenna selection and co-sitting rules are described in the following parts.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
81 / 207
8.2.2 Antenna characteristics & tilt optimization max values

The basic rules for antenna selection are summarized in the following items:

• Frequency band

o VSWR stability in the frequency band

o Stability of the gain in the frequency band

• Gain

• Polarization:

o The two main possibilities are dual- polarized antennas in +/-45°


polarization or vertical polarized antennas.

o Selection depends on the environment as the vertical polarization


has a coverage advantage essentially on rural environment, but it is
constraining in term of place as two antennas are required to
support Rx diversity; that’s why dual-polarized antennas are used
most of the time whatever the environment is

o Antenna decoupling is with dual polarized antenna as 30dB are


ensured inside a same radom.

o Two linear antennas must be separated by a minimum of 0.5m


which induces another mast or on the roof top , which is very
constraining

• Directivity antenna type: omni-directional or sector antenna.

o For outdoor macro-cells network, the antennas essentially used are


sectors, as it allows a better efficiency to manage interferences,
with azimuth and tilt.

o Omni-directional antennas do not have variable tilt

• Radiating pattern must be adapted with the area to cover

o Vertical beam width: vertical angular sector in which the


attenuation is lower than 3dB.

▪ From 6° to 9° for common sector antennas used in 900MHz


band to 2.6GHz band

▪ 15° for common sector antennas used in 700MHz band

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
82 / 207
o Horizontal beam width: horizontal angular sector in which the
attenuation is lower than 3dB. The most common H beam width
sector antenna used is 65°; but 90° are also used on the field

o Front to back ratio: essentially for sector antennas, must be at


least equal to 25dB

• Mechanical tilt range

o 2° to 12° for antennas in frequency bands 850MHz and 900MHz

o 2° to 8° for antennas in frequency band range 1800MHz to


2600MHz

o 2° to 15° for antennas in 700MHz frequency band

Antenna & OEM basics are detailed in the presentation referenced as [R25] in part 11 of this
document.

In the document [R24] the process to validate antenna link is detailed, even with TMA.

For 850MHz, 900MHz, 1800MHz, 1900MHz, AWS, and 2100MHz bandwidth:

• XXpol antennas are already available and well known to support a technology in
1800MHz band & another one in 2100MHz band.

• XXpol antennas are already available and well known to support a technology in
900MHz band (or 850MHz band) & 1800MHz( or 1900MHz or AWS or 2100MHz )
band.

• XXXpol antennas are already available and well known to support a technology in
900MHz band (or 850MHz band), another one in 1800MHz (or 1900MHz) band &
another one 2100MHz band.

The main providers used by Nokia are:

• RFS

• Kathrein

• Comba

But other providers can be used like KMW; Powerwave &Jaybeam wireless.

Antenna guidelines are respectively in [R24] and [R25] linked in part 11 of this document.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
83 / 207
8.2.3 Co-sitting

Several rules have been studied in order to be able to do co-sitting between different
technologies without having some interference problems.

A minimum isolation must be guaranteed between technologies. This isolation depends on the
technologies.

[R8] and [R30] linked in part 11 of this document; provide an analysis on antenna decoupling
solutions and GSM-UMTS co-location solution; and also UMTS vs other technologies isolation
required

This isolation can be obtained by different way; antenna sharing which provides 30dB isolation
between antenna ports,. In case it is not sufficient some filters modules are required, or a
second antenna must be implemented on the roof top with a significant spacing distance to
ensure isolation required.

All the information are detailed in documents [R29] linked in part 11

The table below shows the isolation measured for different horizontal separation and vertical
separation and for different frequency bands.
Antenna Frequency Band Combination Vertical Isolation
0.5m 3m
Antennas in the same frequency bands
700MHz with 700MHz 43 51
850/900MHz with 850/900MHz 48 59
1800/1900MHz with 1800/1900MHz 58 72
AWS/2100MHz with AWS/2100MHz 60 73
2300MHz with 2300MHz 62 76
2600MHz with 2600MHz 63 78

Antennas in different frequency bands


700MHz with 850/900MHz 46 55
700MHz with 1800/1900MHz 65 75
700MHz with AWS/2100MHz 66 78
700MHz with 2300MHz 67 80
700MHz with 2600MHz 69 81
850/900MHz with 1800/1900MHz 65 74
850/900MHz with AWS/2100MHz 66 76
850/900MHz with 2300MHz 67 77
850/900MHz with 2600MHz 70 80
1800/1900MHz with AWS/2100MHz 61 75
1800/1900MHz with 2300MHz 62 78
1800/1900MHz with 2600MHz 64 79
AWS/2100MHz with 2300MHz 62 75
AWS/2100MHz with 2600MHz 63 77
2300MHz with 2600MHz 65 78
Figure 50: Isolation provided by horizontal separation for different frequency bands

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
84 / 207
Antenna Frequency Band Combination Horizontal Isolation
0.5m 3m
Antennas in the same frequency bands
700MHz with 700MHz 30 39
850/900MHz with 850/900MHz 35 47
1800/1900MHz with 1800/1900MHz 45 58
AWS/2100MHz with AWS/2100MHz 47 60
2300MHz with 2300MHz 49 62
2600MHz with 2600MHz 50 63

Antennas in different frequency bands


700MHz with 850/900MHz 37 46
700MHz with 1800/1900MHz 54 63
700MHz with AWS/2100MHz 55 65
700MHz with 2300MHz 57 67
700MHz with 2600MHz 59 70
850/900MHz with 1800/1900MHz 56 65
850/900MHz with AWS/2100MHz 57 67
850/900MHz with 2300MHz 58 69
850/900MHz with 2600MHz 59 71
1800/1900MHz with AWS/2100MHz 50 61
1800/1900MHz with 2300MHz 52 63
1800/1900MHz with 2600MHz 53 63
AWS/2100MHz with 2300MHz 51 64
AWS/2100MHz with 2600MHz 53 65
2300MHz with 2600MHz 55 67

Figure 51: Isolation provided by horizontal separation for different frequency bands

8.3 RNP MAIN INPUTS

8.3.1 GEOGRAPHICAL DATABASES

Geographical databases are not necessarily provided by the customer. This paragraph provides
some fundamental rules to select the correct database type corresponding to our need.

Two geographic database categories

Altitude database: Digital Terrain Model

Environment database: Clutter

8.3.1.1 Digital Terrain Model (DTM)

Contains altitude values of the region

Characterized by a latitude Y, a longitude X, and an accuracy

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
85 / 207
Resolution is directly linked to original satellite, or topographic data which are provided with a
given scale

This scale guarantees the effective resolution of the database.

Based on the original data scale, it is possible to verify if:

The database resolution and precision correspond to those expected after considering
the original data scale

The provider has re-sampled the database in order to obtain the resolution required
based on a worst database resolution.

Figure 52: Correspondence between original data scale and final resolution product

Effective Resolution
original Resolution Accuracy
delivered
Carte 1/250K DTM @ 100m Re-sample @ 50m

X,Y = 100m

Carte 1/50K DTM @ 20m Re-sample @ 50m

X,Y = 20m

Figure 53: original data scale impact on the final accuracy

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
86 / 207
8.3.1.2 CLUTTER

Characterized by a latitude Y, a longitude X

As for DTM databases, resolution is linked to original data (same correspondence table)

There are two type of clutter database: Raster and building outlines

8.3.1.2.1 Raster
Include geographic environnent distribution:

Natural environments: river, forest...

Housing areas: dense urban, urban…

No clutter height information

8.3.1.2.1.1 Clutter definition


Two clutter databases with same resolution on the same areas can be totally different.

Clutter types must be chosen the most efficiently for radio propagation study.

Clutter types can be different between a country database and a city one

A minimum number of clutter types must be defined to have enough details for clutter
description

Below an example of the difference in clutter details due to the original data scale

Figure 56: Original data: Figure 55: Original data: 20-30m Figure 54: Original data: 10m
1/200k topo map satellite or 1/50k topo satellite or 1/25k topo map

A resolution higher than 30m is not accurate enough to describe a big city. Below there is an
example of clutter type definition which must be delivered by the geo database provider.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
87 / 207
Forest Forested land with dense & sparse
tree canopy

Villages Small built-up area in rural


surrounding

Mean_urban Residential, commercial and industrial


zones in suburban environment.
These areas typically feature sparse
density and some vegetation

Dense_urban Areas of dense development within


the urban perimeter

Industrial Areas outside the urban perimeter


including buildings with large
footprints and rather low, separated
by large streets

Residential Houses in suburban environment.


Suburban density typically involves
laid out street patterns in which
streets are visible. Lots may be as
small as 30m by 30m, but are typically
larger and include vegetation cover.

Figure 57: Type of clutter definition

8.3.1.2.1.2 Data extraction method

Figure 58:10m satellite imagery Figure 59: Automatic Extraction Figure 60: Manual Extraction

The data extraction method has an important impact on the clutter distribution.

The pictures above show the extraction method has a big impact on the clutter distribution, so
on the database accuracy. Automatic extraction method provides a worst result than the
manual one.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
88 / 207
8.3.1.2.2 Building outlines
It corresponds to very accurate geographic databases, which contain all building details,
including their heights.

Resolution <= 5m

Height accuracy: 1m

A layer of 3D building vectors can be added.

The face of each building is described

Only 3D ray-tracing models can use the 3D vectors in order to predict small cell-cell and mini-
cell coverage.

Several format of building outline databases can be imported into 9955:

Buildings are defined as clutter class per height range with 1m step. For forest or other
clutter the step is 5m

Two files are available, one clutter class for the clutter distribution, and another clutter
height for the height value in each bin of the area analyzed.

3D vector database file, which is necessary when using ray tracing model

These database types are very expensive and generally used by operators more than by network
vendors.

8.3.1.2.3 Databases usage recommendations


For big and medium cities are:

Building outlines without 3D vectors, if a small cell-cell design is not required. These
databases are described in the previous section

Or

Raster databases with 10m resolution depending on budget

For small cities:

Raster databases with 25m resolution

For rural areas:

Raster databases with 50m resolution

Each raster database should have at least 12 clutter types, with at least 8 different housing
clutter types.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
89 / 207
8.3.2 PROPAGATION MODEL

In this part the different model solutions for outdoor macro-cells and outdoor small cells are
mentioned. All links to useful guidelines on propagation models are detailed

The aim of a radio coverage simulation with a propagation model is to provide a prediction of
the coverage, which has to be as close as possible to reality.

In order to make reliable simulations with an accurate propagation model, the propagation
modeling is of capital importance.

It is very important to calibrate an accurate propagation model, to be sure about radio


predictions quality in the RNP tool.
At the end the aim is be confident in coverage, SINR, Cell ID plan and neighbors plan, as all the
aspects are based on path loss prediction accuracy.
A good tuned model guarantees,

A good RF design in term of site position, azimuth, tilt

A good interference analysis

A good simulation quality, for LTE performances

For more details concerning propagation models principles overview see [R9] linked in part 11 of
this document.

In [R44] all the default ALU recommended models proposed in each technology template are
described. It is highly recommended to refer to this guideline before using them

8.3.2.1 Sites or Cells radio configurations

Models are recommended depending on the database type, the frequency bands and the site or
cell surrounded configuration.

3 types of configurations can be defined

• Macro-cell configuration: Antennas above surrounded roof tops

• Mini-cell configuration: Antennas 5m or less below surrounded roof tops

• Micro cell configuration: Antennas more than 5m below surrounded roof tops

Model to use depends on these radio configurations and not on the type of product used

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
90 / 207
8.3.2.2 CW calibration measurements

CW measurements must be done very precisely, as these measurements are reference to tune a
propagation model.

• Some specific Tx/Rx equipments must be used and

• A specific geo positioning approach must be followed as it can have a huge on


model accuracy is samples are not positioned correctly

• Samples must follow Lee criterion to minimize fast fading

A model cannot be tuned based on scanner drive tests or UE drive tests, result is never
acceptable for this kind of activity.

The measurements must be done following NEA/ RF Design team recommendation in order to
guarantee a good accuracy in the signal strength measured, and also a very precise geo
positioning of the samples on the database used, whatever the database precision is.

The essential points which should be respected are detailed in chapter 2 of the document
referenced as [R38] linked in part 11 of this document.

The process and the application method are detailed in [R38].

8.3.2.3 Standard Propagation Model

This model is specific to 9955 planning tool, but similar model are available on each planning
tool.

SPM can be used on all databases except 3D building vectors and all environments and the most
commonly used.

SPM model calibration

-Having a bad model calibration is generally worst that using default models
-To avoid any problem in the model tuning, ask ARFD team support by contacting Paula
Sauer or Pierre Sabatier

-This model can be automatically calibrated in 9955. It has been tested and validated in
all the databases types (see the complete calibration method and model description in
[R40] & [R44] linked in part of this document)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
91 / 207
-For more details concerning the choice in the different parameter, the use of the
propagation model in 9955, and the calibration method (see [R40] & [R9] linked in part
11 of this document).

-The frequency domain of default SPM parameters is from 300MHz to 2GHz, but this can
be extended as SPM can be tuned on measurements

-The validity domain of such model depends on measurement range of distance, and
measurement antenna height on which it has been calibrated.

Default recommended SPM tuned models

In case no tuned model is available, and there is no time to make CW measurements and to
tune one, some default SPM models are available in default UMTS templates which can be
created with 9955V730.

These default models are detailed in xls file referenced as [R44] in part 11.

The SPM default models are proposed for 2D and 2.5D geographical databases

SPM 2D macro-cells models and SPM 2.5D macro cells models must be used on cells with
same configurations than in macro cell and mini cell description in part 8.3.2.1

SPM 2D metro-cells models and SPM 2.5D metro cells models must be used on cells with
same configuration than in micro cell description in part 8.3.2.1

-These models have been tuned on CW measurements all around the world.
-They are not as accurate as a specific tuned model on a given area but ensure a limited risk
I<ERR>I <2dB & standard deviation <8dB

- Warning! in 9955 atl templates


• SPM 2.5D macro and SPM 2.5D metro default

• these models should be used like they are set in 9955 template without adding
any clutter losses as all the attenuation is compute with diffraction. The user
must use them like they are otherwise results are not guaranteed

• SPM 2D macro and SPM 2D metro default models required to have clutter losses
updated by the user as K1 to K5 values are set.

o K1 to K7 values must not be changed the user has to set K clutter values
based on document [R44] in part 11.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
92 / 207
8.3.2.4 3D Models

The two following propagation models should be used for micro-cell or mini-cell configurations.

Micro-cell configuration corresponds to antenna height between ground level to 10m in dense
urban and urban areas.

Mini-cell configuration corresponds to antenna height between 5m to 10m below nearest


surrounded rooftops.

In 9955 planning tool, for macro-cell configuration with 2D or 2.5D databases it is


recommended to use SPM model as it is free and provide good results.

Winprop propagation model

Winprop is a propagation model built and supported by AWE-communications.

It is not a free model by as NOKIA has a global agreement with AWE for unlimited number of
license, any NOKIA RF designer can ask for one. For a license please send an email at
rnp-tools@nokia.com

It is a complete model as it can perform predictions for any cell type.

Winprop UDP uses a dominant path calculation method which is not a full ray tracing but allow
the same accuracy for a shorter computation time.

The frequency domain is from 300MHz to 3.5GHz.

The Winprop model user manual is linked as [R45]

As any ray tracing model Winprop can be tuned. We recommend anticipating and planning model
calibration any project, and project funding and planning should consider it. This model has an
automatic calibration module. Winprop model calibration still quite specific and requires
experience.

• Having a bad model calibration is generally worst that using default models
• To avoid any problem in the model tuning, ask ARFD team support by contacting
Paula Sauer or Pierre Sabatier
• In case it is tuned, the validity domain of such model depends on measurement
range of distance, and measurement antenna height on which it has been
calibrated

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
93 / 207
As model calibration is not systematically planned, existing tuned model may not be available,
and/or there is no time to make CW measurements and to tune one, we (ARFD team) have
defined some default Winprop models are available in V7.3.2 9955 default UMTS template.

• The Winprop default models are proposed for 3D geographical databases only

• Winprop macro-cells models must be used on cells with same configurations than in
macro cell and mini cell description in part 8.3.2.1

• Winprop metro-cells models must be used on cells with same configuration than in micro
cell description in part 8.3.2.1

Winprop macro and Winprop metro default models defined in template should be used like they
are set in 9955 template.

Winprop default models include indoor losses so in 9955 no indoor losses should be included
in clutter table or for each study “Indoor coverage” must not be selected

The user must not change some coefficient except indoor losses ( see explanation in [R45])
otherwise results are not guaranteed

To be sure that the models used in project atl are the default ones, the user should open a
default template , by clicking on File/New/From a Document Template/ UMTS then go in
Parameters/Propagation models, and compare the default model settings with the one used in
the project

Winprop default models standard deviation should be considered as 8dB with 0dB mean error

Crosswave propagation model

Crosswave is a propagation model developed by Orange Labs and distributed and supported By
Forsk as an option in Atoll (9955). Each ALU entity fund their own licenses and should send an
email to rnp-tools@nokia.com to ask for a Crosswave license.

It is a complete model as it can perform predictions for any cell type, recommended for macro
and metro cell type of deployment.

The frequency domain is from 200MHz to 5GHz.

This model has an automatic calibration module.

As Winprop, Crosswave uses dominant path method. Crosswave has much better performances
than Winprop but is much more expensive

Crosswave model user manual is linked as [R47]

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
94 / 207
As any ray tracing model Crosswave can be tuned. We recommend to anticipate and plan model
calibration any project, and project funding and planning should consider it. This model has an
automatic calibration module. Crosswave model calibration still quite specific and requires
experience.

• Having a bad model calibration is generally worst that using default models
• To avoid any problem in the model tuning, ask ARFD team support by contacting
Paula Sauer or Pierre Sabatier
• In case it is tuned, the validity domain of such model depends on measurement
range of distance, and measurement antenna height on which it has been
calibrated

As model calibration is not systematically planned, existing tuned model may not be available,
and/or there is no time to make CW measurements and to tune one, we (ARFD team) have
defined some default Crosswave models are available in V7.3.2 9955 default UMTS template.

Crosswave macro-cells models must be used on cells with same configurations than in macro
cell and mini cell description in part 8.3.2.1

• On such macro-cells and mini cells configurations Crosswave default models


can use 2.5D and 3D databases

Crosswave metro-cells models must be used on cells with same configuration than in micro cell
description in part 8.3.2.1, but for such metros cells configurations Crosswave default models
must have 3D databases

Crosswave macro and Crosswave metro default models defined in template should be used like
they are set in 9955 template.

Crosswave default models include indoor losses so in 9955 no indoor losses should be
included in clutter table or for each study “Indoor coverage” must not be selected

The user must not change some coefficient except indoor losses ( see explanation in [R47])
otherwise results are not guaranteed.

To be sure that the models used in project atl are the default ones, the user should open a
default template , by clicking on File/New/From a Document Template/ UMTS then go in
Parameters/Propagation models, and compare the default model settings with the one used in
the project.

Crosswave default models standard deviation should be considered as 8dB with 0dB mean error.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
95 / 207
8.3.3 ENGINEERING MARGINS ANALYSIS

All the inputs must have been validated by the customer.

The goal of the uplink budget review is to validate the customer thresholds for the design and
for the acceptance. If link budget with customer assumptions is more constraining, there will
have some reservation on KPI commitments or exclusion areas. In the opposite case, a full
validation of customer thresholds is required.

These inputs are:

All engineering margins and engineering targets

Traffic load assumptions

Service dimensioning

In the following parts the parameters detailed are those currently used, but they can be
modified after discussion with the customer.

This chapter also describes how some parameters are taken into account in the Link Budget, and
their settings in 9955.

8.3.3.1 Standard parameters

Body loss for Speech application 3 dB

Body loss for Data application 0 dB

MS antenna gain 0 dBi@2100MHz & 900MHz

Standard macro-cell Antenna 18 dBi, H beam width 65°@2100MHz

17dBi, H beam width 65°@900MHz

Standard small cell-cell Antenna 8 dBi, sector antenna

5dBi omni-directionnal antenna

Standard Cable Loss depends on average site height, default


cable used is 7/8” with 7dB/100m
loss@2100MHz or
3.7dB/100m@900MHz

Figure 61: standard parameters

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
96 / 207
8.3.3.2 Shadow margin

Link Budget approach


Shadow margin calculation for QoC
Nokia Networks considers there are four independent propagation phenomena which are log
normal fading of the outdoor propagation, building penetration variation, indoor propagation
inside the building and power control variation due to fast fading effect. Then, according to
statistical laws, a global standard deviation is calculated which characterizes the whole
propagation channel:

 Tot =  Outdoor
2

With σOutdoor: STD for outdoor shadowing


RNP 9955 approach
The approach recommended is to set the engineering margins in 9955, as it is necessary to
consider shadowing for mobile launch in UMTS simulations

Set total standard deviation (calculation detailed in part 2.2) in model standard deviation
column in 9955 clutter table (see part 9.4).

Set indoor penetration recommended values (detailed in part 2.2) in 9955 clutter table
(see part 9.4).

Set Ec/Io (or Eb/No) standard deviation recommended values (calculation detailed in part
2.2) in the corresponding column in 9955 clutter table (see part 9.4).

Select Handoff supported in service table (detailed in part 9.5.3) for R’99, and HSUPA
(macro-diversity supported).

Shadow margin calculation for QoC


Total standard deviation is set in Clutter table ( see part 9.4) in the Model standard deviation
column. The values set in this table are used for the UMTS predictions studies to apply a
shadowing on each mobile

The standard values are not changed except for σOutdoor which has the value of the tuned
propagation model used for the deployment.

 Tot =  Outdoor
2

With

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
97 / 207
σOutdoor: Standard deviation of tuned propagation model used for deployment
Ec/Io & Eb/Nt shadow margin calculation in 9955

Considering two signals correlated by  factor

A= n1

B=  .n1 + n2 (1 −  ²)

n1 and n2 totally uncorrelated with the same standard deviation  Outdoor

The ( A − B)² calculation provides the following formula

 C / I =  Tot 2(1 −  )

With  the correlation between Ec and Io

 Outdoor standard deviation of the calibrated model

 value is between 0.9 and 0.95

The range values for  C / I varied between 2.5dB to 3.5dB depending on standard deviation

These values have been validated with system level simulation and field measurements

This has been confirmed by system level simulation. Here is an example of results that
shows that a 1dB standard deviation is a good approximation:

Figure 62: Simulation done to define C/I standard deviation

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
98 / 207
Based on such comparison, the table below shows the defaults C/I standard deviation
values to set depending on different propagation model ones. These values should be
used for RNP analysis and should be set in 9955 RNP Customer table detailed in part 9.4 of
this guideline.

Propagation model Standard deviation for C/I


Standard Deviation calculation

8 dB 2 dB

7 dB 1 dB

6 dB 0 dB

Figure 63: Standard deviation for C/I calculation

8.3.3.3 Indoor/Incar penetration losses

The penetration loss values are detailed in the tables below. Penetration losses depends on how
the equipments and antennas are implemented see the description in part 8.3.2.1

Environment Outdoor Macro Layer * : Outdoor to Indoor Penetration Losses (dB)

Frequency Band: 850/900MHz 1700/1800/1900, 2100MHz

Dense Urban 18 20

Urban 15 17

Suburban 12 14

Suburban & Rural in car 6 8

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
99 / 207
Environment Outdoor Metro cells** : Outdoor to Indoor Penetration Losses (dB)

Frequency Band: 850/900MHz 1700/1800/1900, 2100MHz

Dense Urban 13 15

Urban 12 14

Suburban 11 13

Suburban & Rural in car 6 8

Figure 64: Penetration loss according type of radio configuration, environment type and frequency
band

* This table refers to Macro radio configuration and not necessary to equipment used. Macro
radio configuration doesn’t depends on the product but more on where is placed the equipment
antennas. Indoor losses assigned to outdoor macro layer are applied in reference of the radio
configuration description in part 9 ( antennas should be above surrounded rooftops or less than
5m lower)

Example: RF design of a small cell placed above surrounded rooftops should consider
indoor losses for outdoor macro layer

** This table refers to Metro radio configuration and not necessary to equipment used. Macro
radio configuration doesn’t depends on the product but more on where is paced the equipment
antennas. Indoor losses assigned to outdoor macro layer are applied in reference of the radio
configuration description in part 9 ( antennas should be more than 5m below surrounded
rooftops)

The penetration loss values recommended to use with 9955 are the same than those used in
the LB. considering the clutter description of the table below

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
100 / 207
Clutter name in RNP Description

Isolated high buildings separated by large streets,


Buildings generally situated in suburb.

Suburban or dense individual


or residential high 2-4 stories buildings close together
Suburban
penetration loss Residential or mean individual 1-2 stories houses with garden surrounding cities

Village 1-2 stories houses in rural areas

Factories, warehouse, garages, shopping centers,


Industrial offices, airports

Rural Wide area with agriculture and isolated farm

Open in urban streets and open places in Dense urban /urban areas

Forest All kind of forest inside or outside a city


Incar penetration
loss All kind of green areas inside a city with low trees
Parks density

Open area normally outside a city, but some


Open manufacturer use it also in place of open in urban

Water, inland water Lakes, rivers, sea

Core Urban City center with high buildings concentrated

High density of 8-20 stories buildings, generally in the


Dense urban
Dense blockbuildings city center or business quarter
penetration loss
High density of 6-15 stories buildings, generally in the
Dense urban city center

Block of two or three buildings separated by large


Urban penetration Blockbuildings streets or avenue generally situated in suburb.
loss Mean urban or mean High density of 4-6 stories buildings, generally in the
collective city center

Figure 65: Mapping between penetration losses with clutter types find in clutter geo databases

8.3.3.4 Fast fading margin

The fast fading margin models the impact of fast power control which is not any more efficient
at cell edge (the mobile reaching its maximum transmit power).

This margin is calculated based on layer 1 simulations.

It is extracted by making the difference between the DL TX Eb/No and DL Rx Eb/No with and
without power control.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
101 / 207
The different environment values are the following ones:

Fast fading Fast fading Fast fading


Fast fading
Environment margin for margin for margin for
margin for PS
Voice CS64 HSxPA
Dense Urban 1.7 2 1.7 0.6

Urban 1.7 2 1.7 0.6

Suburban 1.7 2 1.7 0.6


Suburban &
0 0 0 0
Rural in car

Figure 66: Fast fading margin according to environment

8.3.3.5 UPLINK BUDGET

Environment parameters

The table below presents parameters linked to environment definition.

Dense Urban Urban Suburban Rural

Uplink load with R’99 only 65% (75%) 65%(75%) 65%(75%) 65%by default but it
(with HSUPA) can be reduced,

Modeling Channel for C/I Vehicular A Vehicular A Vehicular A Vehicular A


performance

Mobile speed 3 km/h 3 km/h 50 km/h 50 km/h

Coverage type Indoor Indoor Indoor Indoor/incar/outdoor


Figure 67: Environment global parameters

The model standard deviation used is the calibrated model one.

UL radio performances

Usually, all sites are integrated with mounted head amplifier (TMA) in order to push back uplink
coverage limitation. Node-B radio performance in uplink is mainly characterized by two
parameters, noise figure and Eb/No values or SIR performance.

TMA impact on NF and UL losses

Typical Node-B (or RRH) noise figure value is increase from 2.5dB without TMA to 3.3 dB with
TMA configuration.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
102 / 207
As it is detailed in Link Budget guideline ( [R1]& [R2] linked in part 11 of this document), TMA
impact is calculated using Friis formula which is reminded below:

In the configuration with TMA recommended, the total NF stays equal to BTS NF without TMA.

Typical TMA figures are 2 dB NF and 12 dB Gain.

Node-B noise figure is impacted by TMA using .Anyway the overall calculation with Friis formula
find a global NF degradation equals to 0.2dB between with and without TMA

Nokia considers TMA annihilates the feeder loss without any additional reception gain, and the
remain loss is the jumper loss between TMA and antenna connector

To go faster with Radio Planning tool and to avoid a Friis formula calculation for each site, which
takes time when it concerns huge urban area; TMA impact can be approximated. In that case it is
considered that the UL feeder losses are reduced to 0.4dB which is the jumper loss between
TMA and antenna.

It is recommended to use MHA when cable losses ≥1dB including jumpers.

Below for each frequency band, the minimum cable length value to use MHA considering 2
jumpers (0.3dB each) required

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
103 / 207
7/8’ 1’ 1/4

700MHz 20m 25m

850-900MHz 15m 18 m

1800MHz/1900MHz/AWS 10m 12m

2100MHz 8m 10m

2600MHz 5m 6m

Figure 68: Minimum cable length for MHA usage

Eb/No performances

Nokia Networks performances are computed for the different standard ITU channel profiles,
focusing on Vehicular A (VehA), Pedestrian A (PedA) and Pedestrian B (PedB).

PedA is a multi-path channel with a dominant path when PedB is composed of two main paths.

For macro cell application, according to measurements in typical European city, the profile PedA
is statistically observed 45% of the time while the profile PedB represents 55% of the samples.

Looking at Eb/No performances, this mixture of multi-path channel profile is well represented by
the performances of the VehA multi-path performances.

All the Eb/No values are detailed in the Link Budget tool, or in the RNP tool. The values come
from R&D are internal only, and should not be changed

8.3.3.6 DOWNLINK BUDGET

UMTS downlink budgets are always built the same way. In fact there are two downlink budgets,
first one deals with pilot dimensioning and second one with service dimensioning.

The pilot dimensioning phase allows as well fixing common channels contribution as their power
is relative to pilot one.

Max power setting

Global recommendations

Basically there is no maximum power limitation, when there is one MCPA per sector, it means
that max power setting can be set to any value, generally it is recommended to set it to max PA
power

If there are several MCPA per sector, each MCPA must have the same max power setting.

Special case: several MCPA per sector with different number of carriers (STSR2+1)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
104 / 207
The recommended approach is to have, for all carriers of a sector, the same power available on
each carrier.

To obtain that power per carrier is defined based on carrier power available with MCPA where
the highest number of carrier is supported.

Then MCPA max power which supports the lower number of carrier must be limit to

Power per carrier x number of carrier supported by MCPA

Example:

For STSR2+1 configuration, with 2 45W MCPA; the power available in STSR2 configuration,
considering an equal power distribution, is 22.5 W per carrier.

Then on second MCPA which support only one carrier; max power must be limited to 22,5W.

Remark:

It possible to increase CPICH power & max Tx Power of the 3rd carrier but the interest is very
limited

 No gain for HSUPA carrier (FDD3) as the limitation comes from UL load

 Gain only in areas with DL limitation and low interferences => Deep Indoor

 PCIPCH & MaxTxPower must be homogeneous across cells to ensure mobility

 Possible to favor HSDPA carrier (FDD2) : improve Indoor coverage and PA power
for HSDPA capacity

CPICH power calculation

The aim is to determine the minimum CPICH power ratio to insure a certain pilot quality at cell
edge. The max allowable path loss is fixed by the uplink budget and usually based on the
dimensioning service. Pilot quality is estimated by the ratio of energy chip over interference
Ec/Io.

The recommended CPICH power ratio is 10%, this value has been deduced considering

• Pilot Ec/Io target = -15dB in full traffic load conditions.

Under such value ALU considers pilot good detection by the mobile can be problematic.

Extra-cell interference has been evaluated to DL Ie/Ii= 200% compared to intra-cell, considering

• two neighboring macro-cells received with the same RSCP than the serving cell

• pilot ratio is the same for the serving cell and the two neighbors

• serving cells and the two neighbors have the same traffic load

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
105 / 207
• In order to estimate the Io value at cell edge, in addition of the path loss, the
following inputs are required:

Mobile noise figure and antenna gain are used to determine the noise floor

In an UMTS network where TMA are implemented, the variation of the cable losses between
neighbor sectors has a tiny influence on UL coverage whereas the DL coverage is strongly
dependent of cable losses.

In order to avoid significant asymmetry between UL and DL soft HO areas it is recommended to


have for the whole network less than 3dB difference on pilot power at antenna connector (after
TMA). Ideally pilot power at antenna port should be the same for the whole network.

UL/DL Unbalanced

The CPICH power evaluation depends on the cells configurations.

The aim is to have the same equivalence path loss point in UL and DL between two cells. This
requirement is important for HSDPA as macro-diversity is not available. The aim is to avoid to
receive cell A in DL and to be received by cell B in UL, because in that case there is an HSDPA call
drop, instead of having a hard handover.

UL analysis:

UL_diff= Cell_A_sensitivity – Cell_B_sensitivity + external_ losses_ Cell_A - external_


losses_ Cell_B
DL analysis:

DL diff= Cell_A_CPICH_output_cabinet power – Cell_B_CPICH_output_cabinet_power +


external_ losses_ Cell_A – external_ losses_ Cell_B
With external loss= all losses between Node-B or RRH cabinet connector and antenna
connector

The CPICH power must be set in order to have:

8%of total power<CPICH power<12%

IUL_diff – DL_diffI< 3dB

This requirement is resolved, between Node-B with quite the same cable length, by setting the
same CPICH power value at the antenna connector for all the cells.

The CPICH must be tuned differently for all the neighboring relations like:

45W Node-B vs 20W RRH

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
106 / 207
45W Node-B vs small cell-Node-B

Between two 45W Node-B if the cable length are very different (20m difference) without
TMA

Between two Node-B, one without TMA, and the other with TMA

Common Channels power setting

Common channels are always fixed relatively to pilot power.

The table below contains the common channel power settings recommended.

Common Channels Power Distribution

DL Ie/Ii Target for AR=90% 200%

CPICH Ec/Io Target [dB] -15.0 dB

CPICH Power Ratio [%] Between 8% and 12%

Power rel. to CPICH Time


[dB] multiplexed

P-CPICH 100% of time

P-SCH -5.0 dB ----

S-SCH -5.0 dB ----

P-CCPCH -2.0 dB 100% of time

S-CCPCH -1.0 dB 30% of time

PICH -5.0 dB 100% of time

AICH -7.0 dB 100% of time

Common Control Channels Power Ratio [%] 22%

Shared Power reserved for R'99 Traffic [%] 10.00%

Figure 69: Common channels power settings

As mentioned in the table above the recommended % of CPICH power ratio is between 8% to
12%;

• 8% for Dense urban, urban and some suburban areas which are interference limited

• 12% Suburban and rural zones essentially noise limited

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
107 / 207
Some of fALU customers have different recommendations and can use 5% CPICH power ratio, in
that case fALU will use these recommendations, but the Ec/Io target should change too.

For instance with 5% CPICH power ratio the Ec /Io target value for 80% network traffic load
should be -18dB instead of -15dB with fALU recommended power settings.

Power overhead (SHO margin)

SHO margin is considered equal to 15% of the traffic power, which represents around 10% of
the total power. Based on this the max downlink power allowed including Common channels is
90% of the PA power.

Parameters and assumptions


2100MHz/1900MHz 900MHz/850MHz

Thermal Noise (3840 MHz) -108 dBm -108 dBm

MS noise figure 8 dB 9 dB

MS antenna gain 0 dBi 0 dBi

Interference factor @ cell edge 2 (Ie=2*Ii) 2 (Ie=2*Ii)

CPICH Ec/Io target -15 dB -15 dB

Orthogonality factor 0.6 in dense urban/urban (@3km/h

(0 no orthogonality) 0.5 in suburban(@3km/h)/rural (@50km/h

TMA insertion loss 0.4 dB

TMA to antenna jumper loss 0.4 dB

Figure 70: DL budget parameter

The orthogonality factor values have been deduced considering PedA profile 45% of time and
PedB profile 55% of time as it has been statistically evaluated on the field.

Penetration losses are the same than for uplink

The DL shift values represent the delta dB in path loss due to UL and DL frequency differences.
The values presented below come from Cost-Hata model.
DL/UL conversion factor

Okumura Hata model (850MHz, 900MHz) 0.5dB

Cost Hata model (1850MHz, 1900MHz; 2GHz) 1.35 dB

Figure 71: DL/UL frequency shift for urban

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
108 / 207
Downlink service performances target
RAB Parameters CS Voice AMR CS PS PS PS

UL user bit rate 12.2 kbits/s 64 kbits/s 64 kbits/s 128 kbits/s 384 kbits/s

Processing Gain 25 dB 17.8 dB 17.8 dB 14.8 dB 10.0 dB

QoS BLER ≤ 2% BLER≤0.5% BLER ≤ 1% BLER ≤ 1% BLER ≤ 1%

Figure 72: DL service parameters

Nokia calculates downlink performances obtained with simulator.

The table below presents the figures according to this methodology.


Channel 3km/h 50km/h 120km/h

Service Eb/No Eb/No Eb/No

2100MHz

Voice 12.2 7.1 7.6 7.7

CS 64 5 5.4 5.5

PS 64 5.5 6.3 6.5

PS 128 4.8 5.6 5.7

PS 384 5.1 6.1 6.3

1850MHz

Voice 12.2 7.1 7.5 7.55

CS 64 5 5.3 5.35

PS 64 5.5 6.2 6.35

PS 128 4.8 5.5 5.55

PS 384 5.1 6 6.15

900MHz

Voice 12.2 7.05 7.2 7.15

CS 64 4.95 5 4.95

PS 64 5.45 5.9 5.85

PS 128 4.75 5.2 5.05

PS 384 5.05 5.7 5.65

Figure 73: DL Eb/No performances

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
109 / 207
8.4 DIMENSIONNING SERVICE RECOMMENDATIONS & TRAFFIC ASSUMPTIONS

8.4.1 DIMENSIONING SERVICE

The process of the design is based on the coverage requirements of the worst link budget in the
uplink (or the dimensioning service negotiated with the customer).

The recommended dimensioning service is generally PS128 with 65% UL load

Dimensioning with this service allows having an enough path loss to support

DL PS128 service at cell edge for 90% traffic load with 95% area probability

DL PS384 service at cell edge for 50% traffic load with 95% area probability

256kbps HSUPA throughput at cell edge with 75% UL load

The available UL path loss has been calculated in the LB with the parameter settings validated
with the customer.

8.4.2 TRAFFIC ASSUMPTIONS

The traffic analysis is the second stage of the simulation. The traffic load should have been
defined or validated by the customer.

In the following are presented in detail the service and traffic information necessary to complete
an UMTS design. Traffic assumption has a large impact on the cell count and radio planning
results. They should thus be detailed for each of the required services.

The traffic assumptions can be defined in different ways:

• A % of traffic load or total power used is specified between 75% to 90% of traffic
load including common channels and shared power are usually considered
according to the customer this value can change. This is taken into account in
9955, by setting in Cells table, the Total Power column to power values in dBm
corresponding to the % of total PA power

• A mixed traffic is provided by the customer. This mixed traffic is based on a user
call profile which contains each service activity and their duration or data volume
transmitted during a busy hour. First it is necessary to determine exhaustively all
the services the network will have to support. A service is the conjunction of a
data type (voice or data), a transport mode (circuit switched or packet switched),
and a data rate.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
110 / 207
The services which can commonly be met on projects are the following:

Conversational Speech 12.2; CS64; PS64; PS128; PS384; HSDPA; HSUPA

The area where each service has to be provided must be clearly defined (like high data rate is
required in urban center.)

These areas are generally defined per environment type, but traffic can also be defined per
service and per user type, and per sector.

The user type (indoor, outdoor, in car 50km/h, 120km/h) per service, per area is necessary as
well.

Indeed the required Eb/No for a given service in a given environment may be different according
to the profile of the user.

UMTS simulations must be run, in order to take into account the right traffic in 9955

8.5 RF DESIGN TARGETS

Based on dimensioning service and traffic assumptions, the RF design can be completed and
optimized.

The first step is then to select the correct candidate sites in order to fulfill the required QoC and
QoS per area.

During the design, it is important to keep in mind that a W-CDMA network is an interference
limited system, and that in such cases, the sites should be positioned so as to limit inter site
interference.

Therefore, high sites or sites on top of hills or mountains should be avoided (in very hilly
environment, some bi-sector sites could be chosen) the sites should be regularly positioned
over homogeneous areas, electrical down tilt based on the site height and the cell size should be
used…

In order to ensure a good network, the following criteria must be completed.

The RF performances are analyzed with 9955 using the predictions templates and UMTS
simulation module.

The ways how to realize, in 9955, the predictions and simulations to complete the following
design targets are detailed in parts 9.9 & 9.10

The different design targets are the following ones:

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
111 / 207
8.5.1 RSCP targets

8.5.1.1 RSCP target for RNP analysis

It depends on the dimensioning service selected (see part 8.4). The % of QoC is 95%, except for
rural areas where it is 90%.

It means that, when shadowing margin is taken into account, for a 100% covered area obtained
in prediction with radio planning tool for RSCP>=RSCP target criteria, 95% of this area has
RSCP>=RSCP target criteria on the field.

With 9955 there is no solution to take into account the SHO gain for coverage signal analysis.

So only for this study, the easiest way to realize a prediction is to use LB available path loss
without including penetration loss

Set penetration margin to 0 in the LB

Set the standard deviation of the propagation model used (If it is the ALU default model, then
the STD is 8dB). Here the example is for a 7dB tuned model

Figure 74: UMTS LB

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
112 / 207
An RSCP design targets computed by LB are in indoor then and include fast fading margin;
shadowing margin; and SHO gain.

To use this RSCP target with 9955 penetration losses should be set in 9955 clutter table (see
part 9.4), in line with the values detailed in part 8.3.3

Use for this the clutter description detailed in part 8.3.3

Select indoor loss in 9955 coverage prediction study (see part 9.10.1)

Do not select “Shadowing taken into account” in 9955 coverage prediction study

8.5.1.2 RSCP target to consider for field validation

Figure 75: UMTS LB

Acceptance level is the outdoor RSCP target value to at least measured or above over 95% of
the area to be sure that UL service at cell edge targeted will be ensured in indoor over 95% of
the zone.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
113 / 207
RSCP design level and RSCP acceptance level are different due to prediction incertitude but both
guaranteed the same UL service at cell edge.

8.5.2 Ec/Io target

The Ec/Io target value depends on the traffic load. The values detailed below considers CPICH
power ratio between 8% to 12%; if CPICH ratio is out of this range then Ec/Io target should be
modified in consequence (5% CPICH ratio induce a 3dB decrease on the target values detailed
below)

• 95% of the design area should have a Ec/Io value higher than -15dB, with 85% DL
load

• 95% of the design area should have a Ec/Io value higher than-14dB, with 75% DL
load

• 95% of the design area should have a Ec/Io value higher than -12dB, with 50% DL
load

• 95% of the design area should have a Ec/Io value higher than -9dB, with 25% DL load

Such Ec/Io criteria allow managing interferences in order to obtain a RF network design able to
support

• PS384 service at cell edge when surrounded cells have 50% traffic load or
PS128 at cell edge when surrounded cells have 80% traffic load.

• 400kbps HSDPA throughput at cell edge when surrounded cells have 75%
traffic load

• 400kbps HSUPA throughput at cell edge with UE category 12.

Scrambling code planning must be done, using the automatic code planning in 9955 (see part
9.8).

8.5.3 UL/DL effective service area & user rejection

UL & DL effective service area

Coverage target for each service must complete 95% of the design area. A service is considered
to be supported when UL and DL Eb/No are reached. As we have seen Eb/No values take into
account all the profile characteristics, speed, orthogonality factor…

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
114 / 207
User rejection: should not exceed 2% for each service.

8.5.4 Polluted area & overlap analysis

The aim is to optimize tilt in order to reduce the number of servers covering the same area,
thereby minimizing interference without impacting coverage, quality and at the same time
enhancing the SINR

Pollution and interference analysis

• Within 4dB of the best server

o % area with 4 servers should be < 2%.

o % of area with 2 servers should be < 35%.

• Within 10dB of the best server

o % of area with 7 servers or more should be < 2%.

The optimization method to reach these targets is detailed in the part below.

8.5.5 Overshooting and post azimuth/tilt optimization analysis

This analysis should be done after tilt and azimuth optimization so after several ACP iterations
analysis to reach the coverage quality and overlapping targets, and before neighbors list and cell
ID attribution

This analysis consists in verifying the several following aspects over the area which has just been
optimized

• Ensure that best server area is continuous and there is no interruption in best
serving zone by a neighbor cell which would have higher signal strength.

• Verify that all targets are respected and try to improve them manually on the
areas where it is not the case

• Check that the sites the most far away which create some interference have the
maximum down-tilt value applied.

o If it is not the case on the site has a bad impact on Ec/Io, overlapping, or
Eb/Nt, increase its down-tilt by 2° steps and see the impact.

• Verify that the solution propose is applicable; the highest sites must be the most
down-tilted ones compare to low height sites.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
115 / 207
o ACP can propose solution where some high sites are not down-tilted much
and low sites have a big down-tilt, this must be corrected. If it impacts too
much sites then ACP must be re-run with a specific tilt range for high sites
and another one for low sites.

8.6 OPTIMIZATION

8.6.1 METHODOLOGY

The methodology consists in analyzing the area optimized; verify the interference and quality
targets, neighbor plan and scrambling code plan.

The scrambling code plan and polluters reduction should take care about the following points

• The SC of the optimized area re-used in the 2nd external site ring or further are
not necessarily the last polluters in term of ranking (4th, 5th … servers).

• If all polluters are belonging to the first ring, it can be due to a design issue
(missing site, non homogeneous design, high sites) or an environment issue
(Open in urban, hill, mask). In this case, the goal is to create dominance from one
or two sectors increasing their influence and decreasing other influences. Most of
the time tilt manipulations are not sufficient and azimuth changes are required.

• There are also some fine tuning changes that consist in reducing the sector BTS
side while keeping the coverage in the main direction. It’s realized by electrical
down-tilts associated with a mechanical up-tilt.

These methods are identical in all radio system in order to limit inter cell interference, or to
improve the QOC.

In case of pilot unavailability pilot power may also be tuned, in order to provide a dominant
server. The pilot signal should be decoded in every location, as it is required to enter a cell, to
start a communication, and for handoff. When the Ec/Io is insufficient then the interference of
the neighbors should be minimized, and/or the best server received energy increased.

Such optimizations can be done manually, for a low number of sites but the optimization can be
done by an Automatic Cell Planning tool (ACP) allowing a treatment of a higher number of sites
in a short time delay.

This tool extracts/uses from the RF planning tool, all the information necessary to the
optimizations:

Path loss

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
116 / 207
Call profile

Traffic assumptions

Mobile types

Node-B Characteristics

Antennas

…..

Based on these information, and with some KPI targets values like

RSCP level,

QOS target

Ec/Io target,

GOS target,

Pollution window,

Active set size,

The ACP is able to optimize the Network, by changing the different parameters the user allowed
(CPICH power, mechanical tilt, electrical tilt, azimuth, antenna type).

The user is able to define a % for each KPI, and to weight them.

The users can configure the ACP in order to

Re-use a maximum of existing 2G sites

Implement a minimum of new 3G ones

The network optimization stage is done according to the simulation results in order to reach the
target quality thresholds, and to optimize the final radio planning results.

The optimization of the network radio planning is based on the results of the analysis.
Depending on the blocking level, or coverage holes location and size, different solutions can be
used.

8.6.2 PRE-OPTIMIZATION PHASE WITH RNP & ACP TOOLS

8.6.2.1 Tilt and Azimuth Optimization

This phase is done systematically, before making any field analysis

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
117 / 207
Based on existing or candidates sites locations, traffic assumptions and RF targets which are
only based on propagation model prediction

The main part of tilt, azimuth, CPICH power adjustments is done in this phase.

CPICH power must be configured without using ACP in order to have the same value at the
antenna port.

It is highly recommended to use ACP to

• Select sites over all the candidates

• Optimize tilt, azimuth

o Tilt optimization constraints:

▪ 900MHz/850MHz up to 12° overall tilt ( mechanical + electrical) can be


required

▪ 2100MHz/AWS/1900MHz/1800MHz: up to 10° overall tilt ( mechanical +


electrical) can be required

o Azimuth optimization constraint:

▪ Minimum inter-sector angle should be at least equal to the highest


antenna H beam width value of the two sectors.

Examples:

60°inter-sector angle between two 60° H beam width antennas, or one 60°H beam width
antenna and one 30°H beam width

Or

90° inter-sector angle between two 90° H beam width antennas, or one 60°H beam
width antenna and one 90°H beam width

The recommended method is the following one:

o Identify the cluster to optimize, the number of sites for this cluster should not
exceed 500 sites.

• The cluster must be surrounded by a ring of sites which have


already been implemented on the field but which would not be
optimized and used as interferer.

• This can be done with RNP tool and ACP tool using focus zone
which includes sites to optimize; and computation whose sites

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
118 / 207
outside the focus zone are activated and considered as interferers
but not optimized ( this is described in part 10)

o Run ACP with the parameter settings detailed in part 10

o Commit on optimization results (an implementation plan).

o Same approach can be applied to an adjacent cluster sites of an already


optimized cluster; first optimized adjacent sites must be included in the
computation zone, but not in the focus zone which should contain only the sites
to optimize

o Then when everything has been verified and is ok , neighbors and Scrambling
Code allocation can be done

RNP parameters setting is given in the section 9.4 of this document

8.6.2.2 Neighboring plan / Scrambling Code plan

At the end of this phase a neighboring plan is automatically generated with 9955. This
neighboring plan is implemented on the field.

The main planning rule is to re-use cell ID with a sufficient distance in order to avoid radio
interferences.

This distance depends on propagation path loss, the environment and the frequency.

A correct RF design and optimization allow having an average number of neighbors per cell
between 16 and 22 .

The main criterion is radio constraint detailed below:

Considering two cells cell A and cell B, on the same frequency carrier using the same scrambling
code, the distance between those must satisfy the following criteria:

At cell A edge (RSCPcellA ≤ -95dBm): RSCPcellA ≥ RSCPcellB + 10dB

At cell B edge (RSCPcellB ≤ -95dBm): RSCPcellB ≥ RSCPcellA + 10dB

To complete radio constraint, a distance criterion can be added but it can not be used alone as
it assumes a homogeneous environment and a flat terrain area

The distance detailed below represents the minimum distance to consider a cell not as a
neighbor, or to consider that scrambling code can be re-used

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
119 / 207
Dense urban/ urban

Considering mean cell radius around 700m @ 1800MHz and 2100MHz, the minimum
inter-site distance is 2,4km

Considering mean cell radius around 1,5km @ 850MHz and 900MHz, the minimum inter-
site distance is 5,5km

Suburban

Considering mean cell radius around 2,2km @ 1800MHz and 2100MHz, the minimum
inter-site distance is: 7km

Considering mean cell radius around 5,5km @ 850MHz and 900MHz, the minimum inter-
site distance is 18km

Rural

Considering mean cell radius around 7km @ 1800MHz and 2100MHz, the minimum
inter-site distance is: 21km

Considering mean cell radius around 18km @ 850MHz and 900MHz, the minimum inter-
site distance is: 53km

Scrambling code information is provided by SCH broadcast physical channel which contains P-
SCH and S-SCH. The cell search process is the following one:

• In the fist step P-SCH is used for providing slot synchronization

• Second step S-SCH is decoded to provide frame synchronization and scrambling


code group used in the cell

• Third step the scrambling code is found by correlating symbol by symbol over P-
CPICH with the codes in the group found in step2.

A more complete analysis and explanation is done in the [R17] linked in part 11 of this
document

Planning strategy:

Two strategies are possible. The first one is to use a low number of groups with a maximum
number of codes on each group; the second one is to use a high number of groups with a low
number of codes per group.

The table below summarizes the advantages and drawbacks of each strategy.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
120 / 207
Strategy Code Planning Advantages Drawbacks
Rule

Strategy 1 Small number of * Fast Synchronization * Extra load on UE


Code groups Acquisition processing

* Handover procedure * Reduced UE


Strategy 2 High number of efficiency
* Decrease the UE battery
* Low life
Code groups processing load Synchronization
time
* Longer UE battery life
* Probably not
enough time for HO
Figure 76: Advantages and drawbacks of each scrambling code planning strategy
* Potential QoS
Like for neighboring plan, one rule of the scrambling code planning is todegradation
re-use scrambling code
with a sufficient distance in order to avoid interferences.

To improve synchronisation time vs. UE processing load since bad synchronisation will finally
impact the network performance and the quality of service

Check network topology:

Multi-layer networks: Use 1st Strategy

Macro-cell environment with no high speed users: Use 2nd strategy

Same site scrambling code strategy (tcell parameter setting)

On one site, it is possible to apply an offset using tcell parameter setting in order to
desynchronize the SCH channels. Default parameters are 0, 3, and 6 for the 3 cells. Moreover
the SC group is identical over the 3 cells.

The following recommendation has been extracted from the presentation [R18] linked in part
11 of this document.

Recommendation:

To keep different tcell values in order to better distribute the interference generated by the
SCH channels over the time.

8.6.3 RF DESIGN FIELD IMPLEMENTATION & RF DESIGN VALIDATION

8.6.3.1 RF design parameters field implementation

When all the azimuth, electrical and mechanical tilts have been optimized during the pre-
optimization, then the next step is the field implementation.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
121 / 207
All the recommended RF design parameters should be implemented with the maximum of
accuracy.

WARNING! :Particularly attention should be done for azimuth and mechanical tilt settings

• Azimuth settings must be also considered with a particular attention and we must
take into account that Radio Planning tool recommendations are geographical azimuth
and on the field we measure magnetic azimuth.

o The difference between geographic azimuth and magnetic azimuth depends on


each regions around the world.

o The method to evaluate the difference and define the magnetic azimuth
corresponding to the recommended geographic ones is described in document
linked as [R48] in part 11.

• Mechanical tilt as it is also manual operation and requires measurements to ensure field
match recommendations

8.6.3.2 RF design validation

This part describes the field measurement process used to finalize and validate the RF
parameters in order to obtain the best network performances.

A drive test measurement campaign using

RF measurements must be done with scanners and reception antenna positioned on car
rooftop

WARNING!

In the document [R32] some indoor measurements have been performed on the same roads, to
compare values measured with calibrated scanner vs with UE considering 10 different UE. The
average UE error is around 13dB. This should not be considered as a stable value as depending
on UE the error variation is between 7dB to 22dB lower than the scanner. Such results can be
extrapolated for outdoor scanner and UE measured same macro along the same roads

All the runs done for RF design control and validation must be done with scanner (JDSU scanner)
and rooftop antenna as UE cannot be reliable for absolute measured values.
The tilt and azimuth can be changed only after the analysis of these runs. No tilt and azimuth
can be updated based on a UE drive test where the load is not fixed and constant
Any UE measurements are not reliable for RF design since, their measurements accuracy is very
poor as mentioned above and most of them don’t have the possibility to use external antennas.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
122 / 207
Then UE are inside the car with no view of incar penetration considered for such measurements,
which add incertitude on measurements already inaccurate.

Test mobiles, are only used for the other optimization steps!

Post-treatment process

• A drive test measurement campaign using RF measurement scanners with reception


antenna positioned on car rooftop for 1st run and 2nd run

• The complete description of scanner using and measurement process is done in the
document [R11] of part 11 of this guideline.

• Post treatment can be done using EDAT software (internal fALU) or other software
like Gladiator (Agilent). An internal macro with associated guidelines has been
developed for the scanner measurement post-treatment. It is available for JDSU &
PCTEL scanner, as Edat may face issues to extract some RF design criterion.

• Internal macro with associated guidelines is available in link [R39]. All measurement
process is detailed in [R11]

• Also a detailed description and presentation of equipments Nixt and MT8222 is done
on the referenced documents [R49]& [R50] in part 11.

1st Run : RF design control

• Done just after the implementation of the pre-optimization results (see part 8.6.2).

• Fixed load must be applied with OCNS on the entire zone which should be validated. The
recommended OCNS value are 50% or 100%

• In case of commercial network densification, fixed load is not possible; the


option is to consider for each position the number of cells measured,by
the scanner and considering their RSCP and the Pilot power settings to
extrapolate EC/Io for 100% load.

• This has been tested and validate for trials and POC over more
than 150 metros.

• Do not hesitate to ask ARFD support for this ( contact Guillaume


Roland, Pierre Sabatier)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
123 / 207
• The following criteria must be analyzed.

• Overlapping criteria

• The targeted values detailed in part 8.5.4 must be respected

• Ec/Io

• The targeted values detailed in parts 8.5.2 must be ensured over more
than 95% of the area.

• RSCP coverage level

• The targeted values detailed in Link Budget tool as “Outdoor Acceptance


level” (see part 8.5.1.2) must be ensured over more than 95% of the area.

• With drives test measurements, the scanner measured all the servers in 20dB
range. The analysis of such data provides the right information to see if
Neighboring and Cell ID plans done with the RNP are correct or if some cells must
be added

• Post processing will mainly be on radio conditions to check which change should be
applied to optimize network

• For the areas where the targets are not ensured this can be improved by decreasing
interferes impact with down-tilt optimization. This can also be done by increasing best
server coverage area

• In the list of the significant interferers, the one which should be tilted in priority is the
further one not necessarily the one with the lowest level

• The best tilt change configuration suggested must be the one which respects all targets
criteria and/or provides the best improvement for all over the area analyzed.

2nd Run: RF design control fine tuning + neighbour list control tuning,

• Done just after the implementation of change derived from 1st Run, to validate change
efficiency

• Fixed load must be applied with OCNS on the entire zone which should be validated. The
recommended OCNS values are 50% or 100%, and obviously the same load should be
used for run 1 and 2.

• Post processing will be on radio conditions to validate or update the changes


recommended after the first drive in term of

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
124 / 207
• Tilt

• Azimuth

• Neighbor and Cell ID plans.

A 3rd run may be necessary to validate the RF design in case new changes have been done after
the 2nd run. This 3rd run is done in the same conditions than the two previous one, fixed load
scanner.

More information required

• UTRAN parameters settings are detailed in [R12] for LR15.x and in [R13] for
LR14.x linked in part 11 of this document

• HSxPA parameters settings are detailed in [R37] for UA8.0 linked in part 4 of this
document

8.7 OUTDOOR SMALL CELL LAYER RF DESIGN PROCESS

8.7.1 SMALL CELLS PLACEMENT PROCESS OVERVIEW

Small cells deployment allows offloading macro layer and support traffic & network capacity
increase.

Small cells can be deployed in shared channel conditions with macro-layer, or in dedicated
channel. .

All the capacity gain analysis and constraints for a small cells deployment in shared or dedicated
channel are detailed in 3G small cells guideline linked as [R41] in part 11.

For outdoor small cells RF design cell radius vs macro signal strength can be extrapolated from
the tables detailed in document [R51] or in guideline linked as [R41] in part 11.

Outdoor Small cells Link Budgets can provide a first view of small cells footprint vs macro signal
strength . It is based on the tables detailed in [R51]. For more information concerning indoor
and outdoor small cells link budgets using, check the doc following documents whose link are in
in part 11:

• [R3]: UMTS Outdoor Small cells LKB guidelines and Tool

To define the macro signal strength on a given position there are two options.

• RNP analysis

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
125 / 207
o It requires to have all the macro layer information: position, antenna type,
height, azimuth and tilts. Then the user can perform a macro signal strength
analysis and based on the tables document [R51]or in guideline linked as
[R41] in part 11; see where the small cells can be implemented.

▪ Since the user has all the information we recommend to perform the
complete footprint analysis as detailed in the points below

o With RNP the user can also analyze any candidates positions and check the
small cells radius obtained using coverage by transmitter table in 9955. For
more information see all 9955 settings in part 8.7

▪ The minimum recommended cell radius value for metro which cover a
road is to have 50m cell radius along this road to allow the incar UE
staying a minimum of time on the cell.

▪ To check quickly if a small cell is above after the analysis with coverage
by transmitter, the user has the possibility to define a grid per site see
part 9.2.2.

▪ A new module has been created to evaluate on automatic way the cells
radius achievable for each candidate position for each azimuth range.
This module description and settings are available in the link [R55] in
part 11

o For RNP analysis the user should take care about the propagation models
used for macros and metros, see the documents [R44] and [R9] linked in part
11.

• Scanner measurements

o In case there is no access to the macro layer information. Some outdoor


scanner data should be performed in the zone of interest. Then after the
post-treatment, and based on the tables detailed in document [R51]or in
guideline linked as [R41] in part 11; the user can see where the small cells can
be implemented.

All interference RF design targets detailed in part 8.5 must be followed and respected.

In case where RNP analysis is possible interference criteria can be checked and RF design
updated to match them in a pre-optimization phase for each candidates position where cell
radius is acceptable. Then after implementation the verification is performed on the field, during
RF design field validation phase see part 8.6.3.2

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
126 / 207
In case there is no macro info for RNP analysis then such verification can only be performed on
the field, during RF design field validation phase see part 8.6.3.2

All the analysis and constraints for a small cells deployment in shared or dedicated channel are
detailed in UMTS small cells guideline linked as [R41] in part 11.

All the documents detailing tools using method for small cells placement and optimization
[R52], [R53] and [R56] referenced in part 11

Some documents detailing offload analysis area referenced as [R57] in part 11.

8.7.2 MACRO-LAYER DENSIFICATION AND RF DESIGN OPTIMIZATION BASED ON TRAFFIC


GEOLOCATED DATA

ATD module has been developed in order to create a focus zone an traffic map based on geo-
location.

Based on PCDM data, such module allows creating traffic map inside 9955. Then based on the
traffic map created ASP/ACP can load balanced the traffic by optimizing tilts and azimuth
depending on the settings.

With ATD module a traffic map can also be created based on data volume transferred per cell
and demographic map.

Such optimization allows a better traffic distribution, users will be scheduled more times so
higher user throughput is expected, and better network efficiency.

All the process and method is detailed in the document linked as [R56] in part 11.

8.7.3 OUTDOOR SMALL CELLS DEPLOYMENT BASED ON GEOLOCALIZED TRAFFIC DATA OR


DEMOGRAPHIC MAPS

A new module named ATD; has been developed in order to create a focus zone an traffic map
based on geo-location.

ATD internal module has been developed inside 9955 in order to create a focus zone an traffic
map based on geo-location.

Based on PCDM data, such module allows creating traffic map inside 9955. Then based on the
traffic map created ASP/ACP can place and optimize small cells in the areas where there is the
highest traffic load. Depending on the settings macro-cells can have their electrical tilts
optimized too.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
127 / 207
With ATD module a traffic map can also be created based on data volume transferred per cell
and demographic map.

Such analysis allows optimum small cell placement; traffic offload from macro layer to small cell
layer distribution, users will be scheduled more times so higher user throughput is expected,
and better network efficiency

All the process and method is detailed in the document linked as [R56] in part 11.

8.8 STADIUM RF DESIGN RULES

For RF design done with macro-cells, principles, targets and rules are the same than those
detailed in previous parts. The main constraint of such deployment is capacity and users/km²
density to support.

To better manage interference small cells can be a better approach vs. macro-cells

All recommendations; constraints and RF design rules for small cells deployment in stadium, in
shared or dedicated channel with macro-layer, are detailed in document [R41] in part 11.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
128 / 207
9 9955 V7.4.0 PARAMETERS SETTING
In this part several tables are described, all the parameters are not detailed, but only the most
useful and significant for RF design.

For more details and information concerning 9955, see [R21]and [R22] linked in part 11 of this
document.

A 9955 default template is available when the user clicks on File/New/ ‘From a Document
Template’/’UMTS ALU’; all the recommended settings have been defined including all the
bearers, equipment settings, including Quality tables, MUG & MIMO tables, and Bearer selection
thresholds.

9.1 Global tool view

Since release V7.1.0 , 9955 has its interface completely updated. Now, in V7.3.2, as it is shown in
the picture below , there are 4 different tab.

• Parameters:

o Propagation models: contains all propagation used

o Traffic parameters: contains Services, Mobility Type, Terminals, User profiles and
Environment folders

o Radio Network Settings: contains Station Templates, Frequency Bands,


Scrambling codes, Radio Bearers, UE categories, Radio Resource Management,
Reception Equipment; Schedulers; and Quality Indicators folders

o Radio Network Equipment: Antennas, Smart Antennas, TMA, Feeders, Transmitter


Equipment, Inter-technology Interference Reduction Factors, Repeater
Equipment

• Geo: (same as in previous 9955 versions)

o All geographic database files, clutter, DTM; vector

o Zones folder which allow to draw filtering, computation or focus zones

o Traffic folder: which allows settings traffic map

o On-line maps

• Network:

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
129 / 207
o Sites: same contains and possible settings as in previous 9955 release

o Transmitters: same contains and possible settings as in previous 9955 release

o Predictions: same contains and possible settings as in previous 9955 release

o Simulations: same contains and possible settings as in previous 9955 release

o CW Measurements: same contains and possible settings as in previous 9955


release

o Drive test Data: updated contains and possible settings as in previous 9955
release

• Site Explorer:

o Displays transmitter/cell configurations of a given selected site

The different tabs detailed above

Figure 77: Network window menu

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
130 / 207
9.2 SITES

9.2.1 Table Description and Settings

Go In Network tab, double click on Sites folder

Figure 78: 9955 Sites table

Set the latitude Y and longitude X for each site

Do not set the altitude; it is done automatically with the DTM database

Columns for Pylon height or Support types are just information and not used for any calculation
Parameter Unit Value Remarks
Name Set site name
X Set longitude
Y Set latitude
Altitude Automatically set when there is a DTM database
Max nb of CE UL See document [R28]
Max nb of CE DL See document [R28]
Max Iub UL Backhaul 12288
Throughput (kbps)
Max Iub DL Backhaul 12288
Throughput (kbps)
Pylon Height (m)
Equipment Macro Used to indicate the site equipment type
Figure 79: Sites table parameters description

9.2.2 GRID CREATION

This is used more for small cells, to quickly check if their footprint is sufficient after running
coverage by transmitter analysis ( see part 9.10.1.2)

In Network right click on Site, select Grid the following window appears

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
131 / 207
Figure 80: window to create grid distance for each site

To visualize if the small cell footprint respect a critical threshold, 50m in vehicular traffic area
recommended as a minimum, set 50m as Maximum cell radius , and 20 m for circle spacing.

9.3 TRANSMITTERS TABLE

In Network tab; double click on Transmitters folder

Figure 81: Transmitters table

Parameter Unit Value Remarks


Height meter

Azimuth degrees

Mechanical Downtilt degrees

Additional Electrical
degrees Calculated with 3D interpolation
Downtilt

Frequency Band Indicates the working frequency band of this transmitter

Inter-carrier power If selected the power between two carrier can be shared in order
sharing to support an optimum number of users in the cell

Number of Reception
if set to 1 then reception diversity is not applied
Antenna ports

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
132 / 207
NO TMA: set real cables losses if they are known; if not set
3dB in case of Node-B ( or RRH positioned like a Node-B)

0.6dB in case of RRH positioned near antenna


Tx cable losses values must be set

Case with TMA:


Transmission loss dB If no TMA equipment is specified in TMA equipment column (see
below) : real cable losses +0.8dB if known or 3.8dB by default

If a TMA equipment is specified in TMA equipment column (see


below): real cable losses if known or 3 dB by default

Warning!!! If the power specified in cell table is at antenna


connector, the Tx losses should be 0dB
NO TMA: real cable losses if known or 3 dB by default

Case with TMA


If a TMA equipment is specified in TMA equipment column (see
below) , TMA impact is automatically calculated using the friis
Reception loss dB formula
Real cable losses values must be included in the value set

If a no TMA equipment is specified in TMA equipment column


(see below) , real Rx cable losses values is set

BTS Noise Figure dB 2.5 set the typical value according to the chosen equipment
Receiver antenna 0
dB Already included in the Eb/No values
diversity gain
Transmitter
Indicates the transmitter’s type of equipment
equipment
Possibility to select a TMA type if it has been specified in the
directory by Right click on Transmitters\equipment\TMA
TMA equipment
Warning: if TMA impact has already been considered in Reception
& transmission loss column, nothing must be set here
Possibility to select a feeder type if it has been specified in the
Feeder equipment
directory by Right click on Transmitters\equipment\Feeder
Defined the cable length, only used if no value has been
Transmission feeder
meter specified in transmission loss, and if a feeder equipment has
length
been specified
Defined the cable length, only used if no value has been
Reception feeder
meter specified in reception loss, and if a feeder equipment has been
length
specified
Use the tuned model established for the area where the Rf
Main propagation design is done, and if none is available the use the default
model models detailed in document

Main Calculation Should be equal to the geo database resolution, or to the half of
meter
Radius the database resolution
Number of
1,2,4; Set if it is set to 1 then TX diversity can not be applied
Transmission Antenna 1
Ports

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
133 / 207
No Diversity
Open loop
Transmission No
Close loop
Diversity Type diversity
No Diversity when there is only one Tx antenna; Close loop for
low speed UE; Open loop for UE speed > 30km/h
None
DL Multi-cell
Multi-cell Mode None
Should be set to DL Multi-cell only when Dual-cell, 3C, 4C, 6C or
8C feature is used
Figure 82: Transmitters table parameters description

9.3.1 CELLS TABLE

Right click on Transmitters folder → Cells → Open Table

Figure 83: Cells table

Parameter Unit Value Remarks

A frequency band can be defined per cell. The carrier number is


Carrier one of those defined in frequency band table ( Parameters/Radio
Network Settings/Frequencies folder → select Bands table)

Active If selected the cell is active

Total PA power:

3 possibilities:

set the output PA power


Max power dBm set the power at the Node-B connector

set the power at the antenna connector

fALU reference is the antenna connector, in that case no


transmitter losses must be specified in the transmitter table

10% of total PA power


Pilot power dBm
fALU recommends the same CPICH power on all the cells after the

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
134 / 207
TMA, or at the antenna connector.

dB or
SCH power Pilot PA power -7dB
dBm

dB or
Other CCH power Pilot PA power+0.6 dB
dBm

Power used by the cell for all common channels and traffic.

It represents the DL load of the cell taken into account during the
prediction.
Total Power dBm For a design it can be set to 50%, 75%, 90% of the total PA
power, this impacts the Ec/Io target (see part 8.5.2).

This column is set automatically after a simulation when the user


commit the simulation results

R’99 UL load taken into account during the prediction.

If the user does not set any value, the default value is 50.

If the user wants to calculate HSUPA throughput without R’99 UL


load the value must be set to 0.
UL Load Factor % 50
In 9955 the priority is given to R’99, it means UL load considered
for HSUPA is the remained load between max UL load and R’99 UL
load.

This column is set automatically after a simulation when the user


commit the simulation results

Nokia recommends an Active set threshold value equal to 6dB, as


AS threshold dB 6 on the field 4dB threshold is used to add a server, 8dB threshold
to exclude a server

Scrambling Code Define the SC domain corresponding to the cell. SC domain are
domain defined

SC Reuse Distance Minimum distance between a SC reuse

Primary Scrambling
Cell SC defined using automatic allocation
Code

Max UL load allowed R’99+HSUPA UL load cannot be higher


Max UL Load Factor % 75 Nokia recommends 50% max UL load if there R’99 only, and 75%
with HSUPA

Max DL Load % 100 Nokia recommends 100% max DL load

Scrambling Code
domain

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
135 / 207
HSPA Support HSPA+ Allow to select No, or HSDPA, HSPA or HSPA+

Remain power used for HSDPA, include HS-SCCH power. Not


Available HSDPA Power dBm need to be set when HSDPA power dynamic allocation is selected (
see below)

Max total power available= Max PA power – power headroom

0.5 db , if HSDPA is inactive, to reserve shared power for SHO


Power headroom dB 1
1dB when HSDPA is active, is the power reserved to shared power
for SHO+ to compensate the interferences created by HSDPA

HSDPA Dynamic Power Allows automatic remain HSDPA power calculation when a UMTS
selected
Allocation simulation is launch. Must be selected

Allows automatic remain HS-SCCH power calculation when a UMTS


HS-SCCH Dynamic
selected simulation is launch, based on the Ec/Nt target, specified in
Power Allocation
mobility tables. Must be selected

Power used for HS-SCCH. Not need to be set when HS-SCCH


HS-SCCH power dBm
power dynamic allocation is selected

Max number of HSDPA Input used in simulation to have a limitation in the number of
15
users users per cell

Number of HSDPA Output from simulation to indicate the number of users for each
users cell

Max number of HS- Limit the maximum number of PDSCH codes allocated to a HSDPA
15
PDSCH codes user

30 ( for 43 dBm Dl power assigned to DL common channels dedicated to HSUPA


DL HSUPA power dBm PA power per
carrier) Should corresponds to 5% of total PA power

Max number of HSUPA Input used in simulation to have a limitation in the number of
15
users users per cell

Number of HSUPA Output from simulation to indicate the number of users for each
users cell

DL Max Throughput
kbps 1000 Input for simulation
per user

UL Max Throughput per


kbps 1000 Input for simulation
user

Number of HSUPA Output from simulation to indicate the number of users for each
users cell

Can be set by users, or is an output from simulation. It should


UL load factor due to
% 50 correspond to remained load when R’99 UL load has been
HSUPA
deduced. and should be equal to

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
136 / 207
Max UL noise rise - UL noise

Warning!!! to ensure 3dB noise rise 50% must be set even if 50%
is set in the column UL load column dedicated to R’99

Reuse Factor 1.5 Indicate the intra-cell/ extra-cell interference ratio

Max number of intra-


32
carrier neighbours

Max number of inter-


32
carrier neighbours

Max number of inter-


32
technology neighbours

HSDPA Scheduler Proportional HSDPA Scheduler type from the Schedulers table. Select
Algorithm Fair ‘Proportional Fair’ to be in-line with ALU product.

MIMO Support None Allows to select: None, Transmit Diversity, Spatial Multiplexing

Inter-technology DL
dB 0 Indicates the level of inter-technology interference in DL
noise rise

Inter-technology UL
dB 0 Indicates the level of inter-technology interference in UL
noise rise

Figure 84: Cells table parameters description

9.3.2 Add a new cell to a transmitter

Right click to an existing transmitter

Select: Add new cell

A new cell is automatically created at an adjacent frequency of the cell on the same sector

9.4 CLUTTER CLASSES TABLE

This table contains all the information concerning the clutter type characteristics.

Figure 85: 9955 clutter table

These ones are detailed in the table below

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
137 / 207
Parameter Unit Value Remarks
Height m Set when the clutter heights are well known , and if the propagation
model has been calibrated with the clutter heights

Model standard dB
8 Set total standard deviation ( calculation detailed in part 8.3)
deviation
Ec/Io standard dB
deviation 2 Set Ec/Io (or Eb/No) standard deviation recommended values
(calculation detailed in part 8.5)
Eb/Nt UL standard dB
2
deviation
Eb/Nt DL standard dB
2
deviation
Indoor loss Set indoor penetration recommended values (detailed in part 8.3) in
9955 clutter table.
Or set the values provided by the customer
Orthogonality factor Set the values detailed in part 8.3 of this document

Spatial Multiplexing linear 1 Linear gain applied to the throughput when MIMO is supported
Gain Factor
Additional Diversity dB 0
gain (DL)
Pilot finger % 100 Used to evaluated an orthogonality factor impact on the pilot

Orthogonality factor Set the values detailed in part 8.3 of this document

Figure 86: Cutter table parameters

9.5 TRAFFIC PARAMETERS

9.5.1 TERMINAL CHARACTERISTICS

In Parameters tab/Traffic Parameters double click on Terminal

Figure 87: Terminals table

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
138 / 207
Parameter Unit Value Remarks
Min power dBm -50
Max power dBm 21 or 24 21dBm for voice
24 dBm for data
To simulate that, generally 2 terminal types are set, mobile
phone only for voice, and PDA for data
Main Frequency For dual band mobiles Allow to indicate the main frequency
band band use during simulation or prediction. If no frequency
band has been selected, all bands are considered available
Second Frequency Used if main frequency band is full loaded
band
Third Frequency Used if terminal is with supporting three frequency bands
band
Losses dB 0
Gain dBi 0 0 dBi @ 1850MHz; 2GHz; & 900MHz

Losses dB 0
Noise figure ( main dB 8 The terminal noise figure for the frequency band identified
frequency band) as the main one. Depends on customer inputs otherwise use
default values
Noise figure ( second dB 8 The terminal noise figure for the frequency band identified
frequency band) as the second one. Depends on customer inputs otherwise
use default values
Noise figure ( third dB 8 The terminal noise figure for the frequency band identified
frequency band) as the third supported one. Depends on customer inputs
otherwise use default values
Rake factor 1 Enables to model rake receiver

Active Set size 3


Compressed Mode Not selected Selected if a 2G-3G analysis is done

Only for data mobiles. Allow to select No, or HSDPA, HSPA,


HSPA Support HSPA
DB-HSDPA DB-HSPA
HSDPA UE category 1 to 36 Depends on what is required. Links to the defined list of
HSDPA UE Categories
HSUPA UE category 1 to 9 Depends on what is required. Links to the defined list of
HSUPA UE Categories
Reception select standard Select the one where the Nokia curves have been set.
equipment or the one set
MUD Value 0 Not supported yet
between 0
and 1
Rho factor Enable to take into account distortion at the Tx level. These
distortions are taken into account in the interference
calculation.
Number of 1 Indicates number of Rx antenna ports (1 or 2)
Reception Antenna
ports
Figure 88: Terminals table parameters description

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
139 / 207
9.5.2 MOBILITY PARAMETERS

In Parameters tab / Traffic Parameters double click on the folder Mobility Types

Figure 89: UMTS Mobility Types

As specified previously, CPICH Ec/Io target is set to -15dB, the new parameter is HS_SCCH Ec/Nt
target which 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 calculation method.

9.5.3 SERVICE TABLE

In Parameters tab/Traffic Parameters double click on the folder Services

Figure 90: Service table

A service can be created and saved without any R99 radio bearer assigned, but for any
simulation a R99 radio bearer must be assigned to a service.
Parameter Unit Value Remarks
Type of service: Circuit(R99), Packet(R99),
Packet(HSDPA-Best effort), Packet(HSPA-Best
Type Effort), Packet(HSPA-Constant bit rate),
Packet(HSDPA-Variable bit rate), Packet(HSPA-
Variable bit rate),
Carrier Support -1 all the carriers, or selection between the

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
140 / 207
different carriers created ( see 5.1.2)
Priority given to each service, highest priority is
Priority
recommended for voice, lowest for HSDPA.
Selected for all R’99 services
HSUPA when macro-diversity will be supported
Handoff supported
Not selected for HSDPA as it does not support
soft handover
Bearer downgrading YES Bearer downgrading is allowed (Yes/No)
List of preferred carrier numbers
Requested minimum throughput in UL in case
Min Throughput Demand UL kbps
of HSPA Variable Bit Rate type of service
Requested minimum throughput in DL in case
Min Throughput Demand DL kbps of HSPA or HSDPA Variable Bit Rate type of
service
Requested maximum throughput in UL in case
Max Throughput Demand UL kbps
of HSPA Variable Bit Rate type of service
Requested maximum throughput in DL in case
Max Throughput Demand DL kbps of HSPA or HSDPA Variable Bit Rate type of
service
UL activity factor For CS services
0.5 for voice
DL activity factor 1 for CS64

A-DPCH Activity Factor For HSDPA

E-DPCCH Activity Factor For HSUPA


Give a probability of an UL packet success
UL packet efficiency 0.9
transmission
Give a probability of an DL packet success
DL packet efficiency 0.9
transmission
Requested average DL Throughput kbps Default value

Requested average UL Throughput kbps Default value


% used to evaluate the throughput for higher
Throughput scale factor % 100
level than RLC.
Offset used to evaluate the throughput at TCP
Throughput offset dB 0
levels
Average number of packet call in a UL
Default value
session
Average number of packet call in a DL
Default value
session
Inter-arrival time between DL packets ms Default value

Inter-arrival time between UL packets ms Default value

Reading time between two DL packet calls ms Default value

Reading time between two UL packet calls ms Default value

UL packet size Bytes Default value


DL packet size Bytes Default value

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
141 / 207
Min length of a packet stream in UL kBytes Default value

Min length of a packet stream in DL kBytes Default value

Max length of a packet stream in UL kBytes Default value

Max length of a packet stream in DL kBytes Default value


Figure 91: Service table parameters description

9.6 RADIO NETWORK SETTINGS

In this part several tables are described, all the parameters are not detailed, but only the most
useful and significant for RF design.

For more details and information concerning 9955, see [R21] & [R22] linked in part 11 of this
document

9.6.1 GLOBAL PARAMETERS TABLE

These parameters are already set in the default template; click on File/New/ From a Document
Template/ UMTS; all the recommended settings have been defined including all the bearers,
equipment settings, including Quality tables, MIMO tables, and Bearer selection threshold.

Go In Parameters tab, double click on Network settings to have the properties

Figure 92: Transmitters global parameters

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
142 / 207
Parameter Unit Value Remarks

Allows defining the power setting mode in 9955.

DL power Absolute: power value set are in dBm

Relative: power are defined relative to CPICH, offset is in dB

For R’99 only, Nokia recommends calculation of the pilot Ec/Io with the
Io Total
signal pilot considered.

Without useful For R’99 only, Nokia recommends calculation Eb/Nt without the useful
Nt
signal signal.

RSCP Activation
dBm -100dBm RSCP signal threshold for compressed mode start
threshold

Ec/Io CPICH Ec/Io threshold to start compressed mode

Eb/Nt UL & DL
dB Eb/Nt increase due to compressed mode introduction.
Target increase

Without useful For HSDPA only, Nokia recommends calculation Eb/Nt without the
Nt
signal useful signal.

based on Nokia recommends CQI calculation “based on HS-PDSCH quality, as


CQI HS-PDSCH the tables that Nokia recommends are based on this calculation
quality method.

Figure 93: global parameters definition

9.6.2 FREQUENCY BANDS

In Parameters tab/Radio Network Settings/ Frequencies double click on Bands

Figure 94: Frequency bands definition

9.6.3 INTERFERENCE REDUCTION FACTOR

In Parameters tab/Radio Network Settings/Frequencies double click on Inter-carrier Interference


Reduction Factor

Figure 95: Interference reduction factor

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
143 / 207
The recommended value which should be set is the most restrictive one between UL & DL and
between Node-B vs UE ACLR & ACS performances.

As UE ACLR and ACS values are worst than Node-B ones, and equal to 33dB; the recommended
value to set in 9955 is 33dB.

9.6.4 R’99 RADIO BEARER TABLE

In Parameters tab/Radio Network Settings/ Radio Bearers double click on R99 Bearers

Figure 96: Radio bearer table

Parameter Unit Value Remarks

Nominal UL rate kbps

Nominal DL rate kbps

Nothing except
interactive for ADPCH For info only it corresponds to the traffic class the bearer
Type
used for R’99 RAB can fulfill
assign for HSDPA

Model the data rate increase due to coding operations (


Cyclic redundancy check, attachment, transport block
UL coding factor 1 concatenation, code block segmentation, channel coding,
radio frame equalization, interleaving, radio frame
segmentation and rate matching).

DL coding factor 1

UL DPCCH/DPCH Used for simulation and prediction in order to know the part
0.125
power ratio of power used for Control channel

DL DPCCH/DPCH
0.179
power ratio

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
144 / 207
Min TCH power dBm -30 Define the min power assign to one user

Define the max power assign to one user. the user updates
Max TCH power dBm Depends on service this value if necessary in order to reduce the user rejection
% during an UMTS simulation

DL spreading factor
Depends on service Possibility to define the spreading factor for active users
(Active users)

DL spreading factor
Depends on service Possibility to define the spreading factor for inactive users
(Inactive users)

Figure 97: Radio bearer table parameters description

9.6.5 HSDPA RADIO BEARER

In Parameters tab/Network Settings/ Radio Bearers double click on HSDPA Radio Bearer

Figure 98: HSDPA radio bearer table

The Max RLC Throughput values don’t take into account BLER.

The BLER is taken into account in prediction and simulation if the “application throughput” is
considered, instead of “peak rate” where BLER is not taken into account.

9.6.6 HSUPA RADIO BEARER

In Parameters tab/Radio Network Settings/ Radio Bearers double click on HSUPA Radio Bearer

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
145 / 207
Figure 99: HSUPA radio bearer table

The Max RLC Throughput values don’t take into account BLER.

The BLER is taken into account in prediction and simulation if the “Effective throughput” or
“Application Throughput” are considered, instead of “peak rate” where BLER is not taken into
account.

Values in this table should not be changed

9.6.7 HSDPA and HSUPA UE Categories

In Parameters tab/Network Settings/ UE Categories double click on HSDPA UE categories or on


HSUPA UE categories.

This table is for information only. It should not be changed.

Important in any prediction/simulation is that UE Categories will define the UE ultimate


capabilities, hence with impact on scenario selection. See also 9.5.1 Terminal characteristics.

9.6.8 SITES EQUIPMENT TABLE

In Parameters tab /Radio Network Settings/ Radio Resource Management double click on Sites
Equipment

Figure 100: 9955 sites equipment table

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
146 / 207
Parameter Unit Value Remarks

MUD factor 0 Not supported yet by our equipment

Rake factor 1

Carrier selection In case of multi-carrier network, the selection is based on Min UL


Load factor

DL Overhead
resources for common
channels/cell

UL Overhead
resources for common
channels/cell

AS restricted to Not selected AS is not necessary restricted to neighbours


neighbours

Compressed mode Not selected Used for hard handover from 2G to 3G.

Overhead Iub
Throughput /cell

HSDPA Iub Backhaul


Overhead

Throughput supported Not selected Used for hard handover from 2G to 3G.
per E1/T1 Ethernet
link (kbps)

Dual-band HSDPA Inactive Used to allow dual-band HSDPA operation

Multi-cell HSDPA Proportional HSDPA scheduling algorithm is selected when in multi-cell mode of
scheduling algorithm Fair operation

Figure 101: 9955 site equipment parameters

9.6.9 R99 Resource Consumption table

In Parameters tab/Radio Network Settings/ Radio Resource Management double click on R99
Consumption Resource

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
147 / 207
Figure 102: 9955 R99 Resource Consumption table

9.6.10 HSUPA Resource Consumption table

In Parameters tab /Radio Network Settings/ Radio Resource Management double click on HSUPA
Consumption Resource

Figure 103: 9955 HSUPA Resource Consumption table

9.6.11 RECEPTION EQUIPMENT

In Parameters tab /Radio Network Settings double click on Reception equipment, the table
below appears

Figure 104: reception equipment window

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
148 / 207
For each reception equipment categories, to have access to HSDPA or HSUPA bearer selection
and BLER curves double click on it.

9.6.11.1 R’99/HSDPA/HSUPA Eb/Nt & BLER curves

This part concern all following items

• R’99 bearer selection

• HSDPA bearer selection

• HSDPA Quality Graphs

• HSUPA bearer selection

• HSUPA Quality Graphs

• MIMO

They should not be changed without RAN Expertise support as linked to product characteristics

9.7 NEIGHBORING PLAN

In Network tab Right click on transmitters then select Neighbours\Automatic allocation

Figure 105: 9955 neighboring automatic allocation

Setting recommended

Carriers: set the carrier corresponding, if several carriers should be selected, set them
like follow: 1; 2; 3

Max inter-site distance values are the following ones

Dense urban/ urban

2400m @ 1800MHz and 2100MHz

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
149 / 207
5500m @ 850MHz and 900MHz

Suburban

7000m @ 1800MHz and 2100MHz

18000m @ 850MHz and 900MHz

Rural

21000m @ 1800MHz and 2100MHz

53000m @ 850MHz and 900MHz

Force co-site as neighbours: force in the candidate neighbour list cells located on the
same reference cell site. Selected

Force adjacent cells as neighbours: force in the candidate neighbour list cells
geographically adjacent to the reference cell. Selected

Force symmetry: force the reciprocity of a neighborhood link. No specific


recommendation

Force exceptional pairs: force forbid some neighborhood relationship defined by the
user. No specific recommendation

Reset neighbours: if selected all the existing neighbours are deleted before computation.
No specific recommendation

Coverage conditions setting

Signal level (Pilot) > -105 dBm

Ec/Io -15dB

Ec/Io margin equals to 10 dB, margin should be between 10dB and 15dB

9.8 SCRAMBLING CODE PLAN

Go in Transmitters/Cells/Primary Scrambling Code, define a domain and split scrambling code in


4 different groups.

Then assign the different groups as follow. In the picture below each scare is a minimum of 100
sites cluster.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
150 / 207
SC group 1 SC group 2 SC group1

SC group3 SC group 4 SC group 3

SC group 2 SC group1 SC group 2

Figure 106: Scrambling code group strategy allocation

Automatic allocation is launch by right clicking on transmitters then Primary Scrambling


Codes\Automatic allocation

Figure 107: 9955 scrambling codes allocation window

Constraints recommended

Existing neighbours selected

Additional Ec/Io conditions selected

Min Ec/Io: -15dB

Ec/Io margin between 10dB to 15dB, by default 10dB

Shadow margin should not be selected

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
151 / 207
Default reuse distance

Dense urban/ urban

2400m @ 1800MHz and 2100MHz

5500m @ 850MHz and 900MHz

Suburban

7000m @ 1800MHz and 2100MHz

18000m @ 850MHz and 900MHz

Rural

21000m @ 1800MHz and 2100MHz

53000m @ 850MHz and 900MHz

Strategy

Four strategies proposed

A cluster is a number of consecutive codes. This number is set in “Nb of codes per
cluster”.

Clustered: choose scrambling codes for a group of mutually constrained cells. A


minimum of clusters should be used

Distributed per cell: allocate a maximum number of cluster. 9955 can allocate codes
from different clusters.

One cluster par site: 1 cluster per site, and 1 code of cluster par cell. If there aren’t
enough clusters then they are reused without using “Default reuse distance” but trying
to assign clusters space out as possible.

Distributed per site: 3 adjacent clusters per site, 1 cluster per transmitter, 1 code per
cell. If there aren’t enough clusters then they are reused without using “Default reuse
distance” but trying to assign clusters space out as possible.

9.9 SIMULATIONS

For information concerning monte carlo simulation settings and method , see the
document [R22] in part 11 of this guideline.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
152 / 207
9.10 PREDICTION STUDIES

The studies available in 9955 are detailed in the following figures.

Figure 108: 9955 studies

9.10.1 9955 settings for coverage studies

9.10.1.1 RSCP: Coverage By Signal Level Study

The coverage study has a separate setting in 9955, as it is not possible to take into account
easily the SHO gain for coverage if the shadowing margin is calculated directly with 9955.

On the other side, if the RSCP target are only based on LB, as there one RSCP target per
environment it is not easy to set it in 9955 study to have a clear coverage map in one shot.

The method proposed is detailed in part 8.5.1.1.

• Select “indoor loss” in 9955 coverage study as in the picture below

Do not select “shadowing taken into account “icon as it is already done in RSCP target calculated
below (see figure below)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
153 / 207
Figure 109: Coverage study setting in 9955

9.10.1.2 Coverage by Transmitters

Coverage by transmitter is a useful study to verify if there are some overshoots and also check
if small cells footprint is sufficient particularly above 50m in vehicular traffic area

The overshooting analysis is done with 9955 after ACP optimization.

Right click on Predictions folder in 9955 then go in Standard Predictions and select “Coverage by
transmitter”.

Figure 110: Coverage by transmitters study in Standard Predictions

For both analysis the settings are those defined below.

Figure 111: Conditions table settings in Coverage by transmitters study

To have one colour per transmitter, go on Transmitters/properties/display and select automatic

Figure 112: Transmitters color code update

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
154 / 207
9.10.2 Ec/Io

Right click on Predictions/New Predictions.

In Customized Prediction, select Pilot Quality (Ec/Io)

Figure 113:Ec/Io study selection in Customized studies

Verify that the values set in clutter table is in line ( +/-1) with the default value set in 9.4.
indicated values

Select Shadowing margin take into account and

Figure 114: Conditions table settings in Ec/Io study

9.10.3 OVERLAPPING ANALYSIS

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
155 / 207
Right click on Predictions/NewPredictions. In Customized Predictions Select UMTS Overlapping
Zones studies

Figure 115: Overlapping studies selection in Customized studies

Set Condition table as follow:

In the box “with a margin”, set the different values (4dB and 10dB).

Minimum signal level should be set: it is Pilot signal level which is considered

Recommended setting is -115dBm

Figure 116: Conditions table settings in Overlapping studies

9.10.4 RSSI

Right click on Predictions/NewPredictions

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
156 / 207
Select Total Noise level study

In Conditions table do not select “ Shadowing margin taken into account”

9.10.5 9955 settings for Throughput studies

The approach recommended is to set the engineering margins in 9955, as it is necessary to


consider shadowing for mobile launch in UMTS simulations.

Set total standard deviation value (calculation detailed in part 8.3) in model standard
deviation column in 9955 clutter table (see part 9.4).

Set indoor penetration recommended values (detailed in part 8.3) in 9955 clutter table
(see part 9.4).

Set Ec/Io (or Eb/No) standard deviation recommended values (calculation detailed in part
8.5) in the corresponding column in 9955 clutter table (see part 9.4).

Select Handoff supported in service table (detailed in part 9.5.3) for R’99, and HSUPA
(macro-diversity supported)

Select the icon corresponding to “shadowing taken into account”.

Considering the % of area reliability target and the equivalence in cell edge reliability detailed in
part 8.4, set the following % in front of “Cell Edge Coverage Probability”.

Dense Urban Urban Suburban Rural

86% 86% 86% 86%

Figure 117: % of cell edge probability for each environment to set in 9955

Select “indoor coverage” checkbox in 9955 coverage study (see figure above)

For each study, if no simulation has been done, the load taken into account is the lowest
between:

Total power value and max DL load (%) set in Cells table

UL load factor (%) and max UL load (%) set in Cells table

In case of no value set in Total power and UL load, the default value taken into account is 50%

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
157 / 207
If a simulation has been done, it should be specified in the Simulation table of each study, and
an average on all the simulation should be selected, like in the figure below.

Figure 118: Service area study setting in 9955

9.10.5.1 HSDPA study

Figure 119: 9955 HSDPA study

The recommended settings is Average RLC Throughput

Peak Rate is the radio bearer throughput

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
158 / 207
Peak throughput is Peak.rate/ TTi with TTi is the minimum number of TTi between two TTi
used.

Average RLC throughput is RLC Peak throughput taking into account BLER:
( Peak .rate.(1 − BLER )) / TTi

Application throughput use the throughput scale factor and throughput offset (see [R22]) in
order to calculate throughput for higher protocol level than RLC.

Multi-cell HSDPA Study

Prerequisites:

- ‘Multi-cell mode’ parameter in the Transmitters table allows ‘DL multi-cell’ operation
mode, see part 9.3

- Throughput prediction is run for a terminal type which is with a configured HSDPA UE
Category supporting one of the multi-cell modes of Dual-cell, 3C (3-cell), 4C (4-cell), 6C
(6-cell) or 8C (8-cell), see part 9.6.7

- There are defined in the main operating frequency band at least as many active HSDPA
cells as the number of cells supported by the terminal

Note: in one frequency band there can be no more than 4 cells

Figure 120: 9955 3-cell HSDPA analysis example

Dual-band Multi-cell HSDPA Study

Prerequisites:

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
159 / 207
- Site Equipment is with HSDPA Dual-band operation activated, see part 9.6.8

- ‘Multi-cell mode’ parameter in the Transmitters table allows ‘DL multi-cell’ operation
mode, , see part 9.3

- Terminal is configured with a HSPA support mode of either DB‐HSDPA or DB‐HSPA, see
part 9.5.1

- Throughput prediction is run for a terminal type which is with a configured HSDPA UE
Category supporting one of the multi-cell modes of Dual-cell, 3C (3-cell), 4C (4-cell), 6C
(6-cell) or 8C (8-cell), see part 9.6.7

- There are defined in the main and second operating frequency bands at least as many
active HSDPA cells as the number of cells supported by the terminal

Figure 121: 9955 4-cell DB-HSDPA analysis example

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
160 / 207
9.10.5.2 HSUPA study

Figure 122: 9955 HSUPA study

The recommended settings is Average RLC Throughput

The difference between peak rate, throughput and application throughput are exactly the same
than those detailed in the HSDPA study part, just before.

WARNING!!!

Soft handover gain is not taken into account in HSUPA study even, if it is selected in the service
table

9.10.6 MULTI-STOREY

This feature allows performing the predictions on several user heights.

Multi-storey predictions can be useful for:

Air to ground design, where predictions for several altitude ranges are requested

Checking RF design criteria in upper floors of a design

High RSSI levels observed in upper floors during some indoor projects

Can be improved checking 1-7th server criteria

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
161 / 207
The main interest is for 3D database where we want to launch the analysis over several floor s to
see radio conditions in upper storey.

• Click on the Multi-storey prediction icon and a dialog box will appear

Under existing prediction to calculate at different heights, select the coverage


prediction that you wish to calculate. The list contains the coverage predictions
available in the predictions folder (Network tab).

You can enter a name other than the name of the selected coverage prediction.
The predictions will be created using this name suffixed with the receiver height
of each prediction.

You can enter a resolution other than the resolution of the selected coverage
prediction.

Under receiver heights, enter the nb of storeys and the Rx heights for the first
and next storeys. The nb of coverage predictions calculated by the add-in will
correspond to the nb of storeys.

The add-in extrapolates Rx heights corresponding to the next storeys from the
values you enter for the first two storeys when checking the automatically adjust
receiver heights for the next storeys box.

Figure 123: Multi-storey prediction

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
162 / 207
ACP/ASP can optimize a multistorey scenario by computing and reporting quality indicators at
different storey levels. In 9955 7.3.2 it is now possible to specify a maximum number of storeys
for a building to be considered by the ACP multi-storey function by setting the MaxStoreyNb
parameter in the [ACPTplMultistoreyPage] section of the ACP.ini file. The maximum number of
storeys can also be specified by using the Maximum number of storeys option on the
Optimisation -> Multi-Storey tab.

9.11 SCANNER or CW DATAS IMPORT & COMPARISON WITH STUDIES

Below the process on how to import Drive Test data is presented, and it is quite the same than
the one done for CW measurements, when there is a difference, it is specified.

Right click on “Drive Test Data” folder and select import

Figure 124: Drive test import in 9955

Select the file corresponding to the drive tests measurements done; the format should be .txt
or .csv

When the measurement file has been opened by 9955

Select the right separator (here in the example it is “;”)

Specify the first measurement row

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
163 / 207
Figure 125: Drive tests import settings in 9955

Then specify the first measurement row, (here in the example it is the line 2), it will automatically
update the name in the “Field” line, as the values set in line 1

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
164 / 207
Figure 126: Drive test import settings

Then click on Setup and select the right name corresponding to X and Y column, also set
manually the column name where Primary Scrambling Code (PSC) or, alternatively, Physical cell ID
is provided (for CW measurements it is not Physical Cell ID which should be indicated manually
but column where CW measurements are set).

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
165 / 207
Figure 127: Drive tests columns identification in 9955

Then select import

To select a criterion measured right click on “Drive Test Data” (for CW measurements it should
be on “CW measurement” folder) select properties, then go on Display table, select in Display
Type “Value Intervals”, and then the measured criterion required in “Field”

Figure 128: Measurement display in 9955

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
166 / 207
Then the criterion will be displayed on the map and a comparison can be done with the
predictions, using the same scale between predictions and measurements.

A much accurate comparison is possible by doing it point by point based on the steps

Right click on Drive Test Data and select Calculations, Create a New Prediction

Then select Point signal level prediction type

Go back to calculations and select Calculate all the Predictions

Figure 129: Prediction types in Drive Test Data

For CW measurements the comparison with predictions is done in a similar way, point by point,
by following some similar steps

Right click on CW measurements and select Calculations,

Then right click on CW measurements and select Display Statistics to have the results

9.12 GEO DATABASES IMPORT

3 types of geo databases as detailed in part 8.3.1

2D databases contain 2 files

• clutter classes file ( can be named clutter or DLU) imported as Clutter Classes in 9955

• Terrain file ( names also as DTM or height) imported as Altitude in 9955

For 2.5D database, there is a third file which contains each database bin height, it can be named
Clutter height, or DLH and should be imported as Clutter Heights in 9955

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
167 / 207
For 3D database, added to 2.5D database file, there is a vector file which contains all database
3D details and should be imported as Vectors in 9955

9.13 MULTI-RAT SETTINGS

To create a MULTI-RAT project click on File/New/From Document Template / 3GPP Multi-Rat,


then the following window appears where you can select the technologies to include in the
project.

Only GSM/UMTS/LTE are concerned

Figure 130: Multi-RAT technologies selection

Then when the project is opened the users an interface update

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
168 / 207
9.13.1 NETWORKS

Figure 131: Multi-RAT Networks window

Sites table is exactly the same as described for UMTS template in part 9.2

LTE Transmitters table has the same structure than what is described in part 9.3.

Also same functionalities are kept, by right clicking on LTE Transmitters, the user can:

• Open Cells table whose structure is the same than in part 9.3.1

• Launch Neighbors allocation like described in part 9.7

• Launch Scrambling code allocation like described in part 9.8

• For LTE predictions, like for any LTE template, right click on
Predictions/New the following window appears

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
169 / 207
Figure 132: Multi-Rat predictions menu

Then display “ Customized Predictions UMTS” to have all ALU prediction settings, like in the
following window

Figure 133: Multi-Rat customized predictions menu

To perform Monte Carlo simulations see the process described in document linked as [R22] in
part 11.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
170 / 207
For UMTS drive test data import and analysis, the user you consider UMTS Drive Test data then
all the process is the same than description in part 9.11

9.13.2 PARAMETERS

Figure 134: Multi-Rat Parameters window

Network settings structure and data are the same than the description in part 9.6

In Services the only difference is all the services are defined including GSM, UMTS and LTE ones,
otherwise UMTS field in services table are the same than those described in part 9.5.3

Some services like FTP Download are common to all technologies

In Terminals table each technology terminal is defined and related to its Reception equipment
performances like described in part 9.5.1 for UMTS.

Mobility table is the same as part 9.5.2, as it is common to all technologies

In User Profiles, there is the possibility to define a multi-technology user, for services common
to technology download; each profile will be attached to a technology by the type of terminal
used

No change in Propagation models, as previously they should be assigned according to the


frequency band used.

Also for Radio Network Equipment, there is no modification compare to what is available in UMTS
template

9.13.3 GEO

This part has not changed, only the clutter table contains separated column per technology for
Model standard deviation, C/I standard deviation...

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
171 / 207
The user has to take care and set the correct values in purpose like described in part 9.4

9.14 STREET TO CLUTTER MODULE TO UPDATE 2D GEODATABASE IN A 2.5D ACCURATE


DATABASE

• For small cells analysis it is highly recommended to have accurate database to position
small cells in the streets. So 2.5D databases is the best option to place and optimize
small cells using SPM2.5D small cells default models.

• In case only 2D raster database is available, an internal module named “Street2Clutter”


has been created to be able to improve 2D raster database accuracy by updating it with
all existing streets. Then by setting average height per clutter and using 2.5D models,
accurate more analysis and small cells placement can be done than using 2D models.

• All the process is detailed in the document [R27] in part 11.

10 9955 ASP/ACP METHOD & SETTINGS


Since December 2014 fALU RF designers have had the possibility to use Forsk ASP/ACP tool in
parallel of ACCO, allowing a ramp up period to this new tool and keep having the possibility to
use ACCO. Starting with release V7.3.0 of 9955 these Forsk modules come integrated into 9955.

• All the process and description for Forsk ASP/ACP settings and using is available on the
document linked as [R55] in part 11 of this guideline.

To take into account backhauling constraints Small Cell Selection module can be used. All
settings are detailed in document [R53] referenced in part 11.

For small cell placement based on geo-localized data all the process is detailed in document
referenced as [R53] in part 11.

Main characteristics of ASP/ACP modules are:

• ASP/ACP are fully integrated in 9955

• provided as a new integrated modules they reuse 9955 project network design, zones,
clutter classes and templates

• all pathloss (PL) calculation done in ASP/ACP can be reused in the 9955 platform

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
172 / 207
• reuse of existing path loss files calculated by 9955 platform

• ASP/ACP implementation plan can be committed in 9955 project

Figure 135: ASP/ACP functionalities available in Network explorer window

10.1 Greenfield RF design method with using ASP

ASP can be used to deploy new sites for a greenfield network. This can be the case for
countrywide coverage projects (regulatory aspects), where a 2D database is used.

Before launching ASP, make sure that there is a site template per environment (DU / U / SU / RU)
configured according to your project’s need:

• Frequency band;

• Antenna types;

• Sites’ height;

• Propagation model

Figure 136: Available Station templates (used by ASP)

ASP design steps:

• Create a new ASP scenario

• Launch calculation

• Commit results

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
173 / 207
Create a new ASP scenario by choosing target working layer and analysis resolution. Choose the
‘Smart design’ option case in which new site positioning will be path-loss based
calculated/computed. This positioning process will use a CPICH RSCP based signal level criterion.

Figure 137: Define a new ASP Scenario, choose ‘Smart design’

Figure 138: Configure scenario: choose target area and Station template to use

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
174 / 207
Figure 139: Configure scenario: set target objective and other (optional) design rules

Figure 140: Configure scenario: review/update target objective, (optional) set clutter specific design
thresholds

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
175 / 207
Figure 141: Configure scenario: go for indoor design conditions

Note: in case of indoor coverage is used please review/update accordingly all the design
thresholds configured for the existing ‘Gold’, ‘Silver’ and ‘Bronze’ objectives.

Figure 142: ASP computation & results

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
176 / 207
Figure 143: ASP results: choose an implementation plan (example: for 95% signal level coverage of the
area)

Figure 144: ASP results: commit results and computed path-losses

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
177 / 207
Figure 145: ASP committed results

Figure 146: Checking CPICH RSCP predicted performance

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
178 / 207
10.2 Network densification with using ASP

ASP can be used to deploy new sites for an existing 3G network (network densification). This can
be the case when coverage/capacity performances of existing network need to be improved.
Note that there is no restriction regarding type of new sites to add to the current design (it can
be either macro or metro) it is specified in the same way as for the Greenfield option, see
section 10.1, by choosing an appropriate existing ‘Station templates’.

Before launching ASP, make sure that there is an appropriate site template per environment (DU
/ U / SU / RU) configured according to your project:

• Frequency band;

• Antenna type;

• Sites’ height;

• Propagation model

Figure 147: Existing network’s CPICH RSCP predicted performance

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
179 / 207
Figure 148: Adding new sites (red dots) by using ASP; target 95% indoor CPICH RSCP coverage

Figure 149: Network densification: checking indoor CPICH RSCP coverage

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
180 / 207
10.3 RF design optimization method with 9955 ACP

This part details the method how to prepare 9955 environment before accessing 9955 ACP
functionalities.

The aim is to select the right candidate sites and to optimize tilt and azimuth. This exercise can
be done in the all along the site selection phase, and during the pre-optimization phase.

In order to realize an optimization in line with RF design targets recommended in part 8.5, 9955
transmitters table and cell tables should be set as it is recommended in parts 9.2 & 9.3 ; and
ACP targets should be those detailed in part 10.4

• Identify the cluster to optimize, the number of sites for this cluster should not exceed
500 sites.

o The cluster must be surrounded by a ring of sites which have already been
implemented on the field but which would not be optimized and used as
interferer.

Figure 150: Example of computation zone & focus zone setup in 9955 before using ACP

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
181 / 207
o To ensure this a computation zone must be defined in 9955 which must contains
the sites to optimize but also a circle of surrounded activated sites which will not
be optimized, but whose interference will be considered during optimization

o A focus zone can be defined which contains exclusively the sites to optimize. The
focus zone must be inside the computation zone.

Note: ACP is very flexible with using the different zones at Geo tab, in case there are some hot-
spot zones defined they can be used as well for target area to be optimized (we can have several
different non-intersecting polygons defined!) or in case of focus zone is not defined it can
optimize all the sites found inside the computation zone.

• Launch pathloss matrix computation before creating an ACP setup

• Create ACP setup with the recommended parameter settings

• Run ACP optimization and commit optimization results in-line with a chosen optimization
strategy

• Same approach can be applied to an adjacent cluster sites of an already optimized


cluster; first optimized adjacent sites must be included in the computation zone, but not
in the focus zone which should contain only the sites to optimize

10.4 ACP parameters settings recommended for RF optimization

10.4.1 Creating an ACP setup

After the computation or focus zone definition which delimits the area where the
optimization should be done; the user should respect the following steps

Please note, if a site selection is expected, then it is recommended the sites concerned not
to be activated. Then, these sites will be considered as ‘Current Candidate’ ones while a
current candidate selection process will take place with applying some defined selection
policies as of described in section 10.4.5. Hence we can ensure a very selective and rf
optimized site activation (example strategy: the most appropriate one single site is activated
out of five possible candidates).

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
182 / 207
Figure 151: Creating a new ACP Setup

10.4.2 ACP Setup: Optimisation

Figure 152: ACP Setup - Optimisation

‘Optimisation’ tab of a new ACP setup allows designers to set/choose the main design
optimization parameters:

- Set ‘Number of iterations’; value shall be higher than then minim need one in order to
achieve convergence (minim value is indicated as ‘Recommended value)

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
183 / 207
- Analysis ‘resolution’; the resolution defined should be between the database resolution
values and twice time the database resolution value.

- Optimization environment, analysis options and other global parameter options grouped
into the subfolders of:

o Technology layers

o Zones

o Cost Control

o Constraints

By default only used in the project technology layers will be displayed and be available to
work with. In case of a MultiRAT project you may have several entries, belonging to different
technologies, available. Be aware that ACP will work simultaneously with all the selected
layers, hence ensure that you have the complete network setup for all the considered
technology layers before creating ACP setup.

There are two important optimization mode selection options available as simple
checkboxes:

- ‘Reconfiguration’ – only active sites/sectors from within the optimization area will be
considered for optimization (reconfiguration). Only this option selected will allow to
chose one or more of the transmitter/cell parameters of an active site to be optimized:
antenna type, electrical tilt, mechanical tilt, antenna height, sector azimuth and pilot
power, see 10.4.5.

- ‘Site selection’ – with this option we might go for current site selection (even with
shouting down some currently active sites, sectors) or for candidate site selection
(activate some new candidate sites) with a possible option to import/add new possible
candidates into the working site list, see 10.4.5.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
184 / 207
Figure 153: ACP Setup/Optimisation/Zones

At the ‘Zones’ subfolder you can specify options for area accounted for objectives’
evaluation but as well option for area to be optimized. By default you are recommended to
do the evaluation over the full computation zone but optimize only the sites falling inside
the focus area. At ‘Zone parameters’ you will be indicated with some details of these existing
zones but as well the option to change priorities of these.

Figure 154: ACP cost control

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
185 / 207
Cost figures can be introduced to each kind of network change the tool can perform (tilt,
azimuth, etc). Cost is not taken into account by default (i.e. ‘No cost control’ is checked).

Figure 155: ACP global constraints

It is possible to limit the max number of active sites when working with candidates. Although
this is only a global limit on total number of sites, would you need more control on site
candidate’s activation please check section 10.4.5.

10.4.3 ACP Setup: Objectives

Figure 156: ACP Setup/Objectives

At ACP Setup/Objectives the optimization targets to be used can be specified. By default the
3G objectives of ‘UMTS RSCP Coverage’ and ‘UMTS EcIo’ objectives are defined, see figure
above.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
186 / 207
New Objectives can be added. Right click on ‘Objectives’ to add a new target.

Figure 157: Adding a new ACP 3G design target

10.4.3.1 Coverage targets

o For Coverage target, the user should define the RSCP target based on Link
budget max available path loss (MAPL). As ACP use the clutter losses set in RNP
clutter table with setting detailed in part 9.4, a common target can be set for all
clutter types.

▪ RSCP target for a given clutter and a given service is:

• RSCP target =Pilot power –Tx cable losses + Antenna gain –


Dimensioning service MAPL

• The user has to identify each clutter to the four case in the LB,
which are Dense urban, urban suburban or rural

• Target coverage (%) shall correspond to that of LKB assumed one

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
187 / 207
Figure 158: ACP Coverage target setting

10.4.3.2 Ec/Io target

o For Ec/Io target, for all the clutter set -15dB, in case of 90% cell load assumption
(90% of load in 9955 Total power column in cell table), which is our
recommendation but if the customer required another target, the user should
set this one.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
188 / 207
Figure 159: ACP Ec/Io target setting

10.4.3.3 Overlapping targets

To ensure that 4dB overlapping criterion is respected the objective of ‘UMTS 1st –Nth
difference’ should be used and set as below in order to ensure a minimum of 4dB delta
between the serving cell and the 2nd server in more than 65% of the area (max. 35% of the
area with 2 and more servers in 4 dB range)

Figure 160: 4dB Overlapping target setting

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
189 / 207
To ensure that 10dB overlapping criterion is respected the same objective of ‘UMTS 1st –Nth
difference’ can be used and set as below in order to ensure a minimum of 10dB delta
between the serving cell and the 7th server in more than 98% of the area (max. 2% of the
area with 7 and more servers in 10dB range)

Figure 161: 10dB Overlapping target setting

Alternatively, the objective of ‘UMTS Pilot pollution’ can be used, configured according to a
formerly created ‘Overlapping Zones’ prediction type defined with a margin of 10dB (as well,
you can define this manually but mandatorily before creating the objective), and set as below
in order to ensure a minimum of 10dB delta between the serving cell and the 7th server in at
least 98% of the area (max. 2% of the area with 7 or more servers in 10dB range).

Figure 162: 10dB Overlapping target setting, variant

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
190 / 207
10.4.4 ACP Setup: Antenna

Figure 163: Antenna pattern grouping into antenna element

Before setting any optimization parameter by accessing the ‘Reconfiguration’ tab you may
define the way ACP will work with the antennas during optimization, i.e. for example, in case of
antenna electrical tilt optimization you may want to have all the pattern variants of a given
antenna type indicated. This can be buy grouping antenna patterns. Select all antenna patterns
belonging to the same antenna (different electrical tilts and click on the arrow to group them
under a specified antenna element name. You may define several different antenna elements
ACP to work with. Note that antenna elements shall contain patterns standing for given
frequency band. In case of a multiband antenna, you may define antenna elements as per
different supported frequency band and then grouping them into a physical antenna definition.
Unless multiband is your case physical antennas will be defined based on single antenna
elements.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
191 / 207
Figure 164: ACP Physical Antenna definition

10.4.5 ACP Setup: Reconfiguration

This is the place where you can indicate design parameters which are going to be optimized.
They are grouped into three groups: belonging either to Sites, Transmitters or UMTS Cells.

Figure 165: ACP Setup - Reconfiguration

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
192 / 207
10.4.5.1 Site optimizations

Option only available if ‘Site Selection’ checkbox at ACP Setup/Optimisation/Tehnology layer was
selected. If not selected there will be no sites displayed in the list at Reconfiguration/Sites.

Figure 166: No site parameters are available for reconfiguration

Figure 167: Sites parameters ACP may work with

Having Site reconfiguration disabled, i.e. not allowing site optimization can be useful when
handling small cells design where macro layer shall not be changed. Otherwise existing site
sector or entire site can be removed, candidate sites can be activated (they were defined but
formerly not active) or even new candidates can be added into the project.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
193 / 207
Figure 168: New candidate site selection

Note that adding new candidate sites is not equivalent to ASP which is with positioning new
UMTS sites. ACP’s new candidate site selection is requiring a site list with known site locations
indicated. This list can be populated either from the current Sites table, by considering current
entries with no transmitters linked to, or importing new site locations from a file or, in case of a
MultiRAT project, imported from the other technology layers’ sites tables.

10.4.5.2 Transmitter parameter optimizations

At ACP Setup/Reconfiguration/Transmitters tab you may select those transmitter parameters


which are going to be reconfigured (optimized). These are: Antenna Type, Electrical Tilt, Azimuth,
Mechanical Tilt, Antenna Height.

Recommended optimization ranges are:

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
194 / 207
For UMTS tilt & antenna type optimization; whatever option selected; the range required
depends on the frequency band and the environment. The most constraining environment is
dense urban/ urban.
 Concerning maximum tilt values; the recommendations done below must be respected in
a range of +/-2° The main reason is because in RNP the obstacles (hence their impacts)
are generally not considered whereas on the field these are with the highest impact on tilt
optimization.

 A too high tilt value will induce to have the main path impacted by side lobes antenna
pattern zone which is not stable and so not predictable

o 900MHz/850MHz up to 12° can be required overall tilt ( mechanical + electrical) can be


required but not higher

o 2100MHz/AWS/1900MHz/1800MHz: up to 10° can be required overall tilt ( mechanical


+ electrical) can be required but not higher

WARNING!

• Minimum step between two tilt values must be at least 2°, having 1° doesn’t change the
design and increase computation time

Several configurations can be done

Notes:

- the electrical tilt optimization required to set in 9955 an antenna pattern per antenna type and
tilt value. Antenna pattern grouping, in-line with recommendations of 10.4.4, is recommended.
Doing this allows for a given sector to optimize tilts only based on the pattern included in the
same group (under same antenna element name) than the one already assigned before ACP
launch.

- Do not select too much groups and patterns, it increases exponentially computation time

- “Electrical Tilt range should be from 0° to 10° or 12°, and sometimes 16° (depends on
environment & availability of pattern files as per tilt)

- Mechanical tilt optimization should be combined with Electrical tilt optimization if the pattern list
per antenna model is not exhaustive or if the tilt range on the antenna models which must be
used is not sufficient

- Mechanical tilt max ranges shall be specified in order not to exceed the recommended total tilt
value (in case of electrical tilt is used) or set the same range as for electrical tilt (see above) in case
of only mechanical tilts alone (no e-tilt pattern files are available for different e-tilt values!) are
optimized

For UMTS azimuth optimization the recommended settings are:

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
195 / 207
• -60° to 60° range, with 20° step ( 20° steps are set in Optimization options table,
a 5° step increase computation time without added efficiency

10.4.5.3 Cell parameter optimizations

Figure 169: ACP Reconfiguration - Cells parameters

10.4.6 ACP with traffic map and load balancing

ACP may take into account a known traffic distribution in the optimization process via ‘pixel
weighting’ of one or more defined objectives.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
196 / 207
A traffic map can be created with 9955 as it is detailed in part 9.5 of this document. At an
Objective definition you can select the ‘pixel weighting’ option and then attaché a defined traffic
map. This will change the importance of Objective’s evaluated values at each map pixel
according to the indicated traffic map (high load areas will have a higher impact)

Figure 170: ACP using existing traffic definitions

10.4.7 ACP: Running the optimization

Right click on a newly created ACP Setup and select ‘Run…’ This will launch the ACP optimization
process in-line with the ACP Setup options/selections.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
197 / 207
Figure 171: ACP RUN

During the ACP run you can check the real-time evolution of the optimization process, not only
as a graph on the progress of Objectives’ achievement (in %-age) but in detailed views by
accessing the successive tabs of “Changes’, ‘Quality’ and ‘Objectives’

10.4.8 ACP: Analyzing the results

As soon as ACP run is finished an ‘Optimisation’ result folder is created under the Setup one with
details on ACP results.

Figure 172: ACP Optimization results

The presented information is allowing you to check all the results in forms of statistics, detailed
plots on before-after performances of different objectives, histograms, implementation plan
proposal and option to commit on results.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
198 / 207
Figure 173: ACP results' analysis

Figure 174: ACP results - choosing an implementation plan

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
199 / 207
Note: chosen implementation plan can be committed while reconfiguration info will be
written into the appropriate 9955 tables (Sites, transmitters, Cells) but as well, where is
the case PL matrices updated.

10.5 HOW TO IMPLEMENT AN OPTIMUM SMALL CELLS NUMBER

ACP can be used to optimize the number of outdoor small cells implemented in a macro-layer.

All ACP settings and different steps are described in part 11.2 of guidelines linked as [R54] in
section 11. This includes the tables which make the link between macro cell RSRP level where
small cells are placed and metro cells radius achieved.

In complement to the guideline a dedicated ASP/ACP settings presentation is referenced as


[R55] in part 11.

To take into account backhauling constraints Small Cell Selection module can be used. All
settings are detailed in document [R53] referenced in part 11.

For small cell placement based on geo-localized data all the process is detailed in document
referenced as [R56] in part 11.

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
200 / 207
11 REFERENCE DOCUMENTATION
[R1] “W-CDMA ALU Link Budget guideline & training”

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68125231&objAction=browse&viewType=1

[R2] “W-CDMA ALU Link Budget tool”

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68125231&objAction=browse&viewType=1

[R3] Outdoor Small Cells Link Budget Guidelines and Tool

https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=67696328&objAction=browse&viewType=1

[R4] “Repeater capacity”

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68551080&objAction=browse&viewType=1

[R5] Monoservice Capacity Excel Sheet

https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68549511&objAction=browse&viewType=1

[R6] “W-CDMA Air Interface Dimensioning Rules”

https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68125231&objAction=browse&viewType=1

[R7] “HSxPA Parameters User Guide 7.0”

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=53160351&objAction=browse&sort=name&viewType=1

[R8] “Interference Detection”

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080962&objAction=browse&viewType=1

[R9] “Propagation model KTS”

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078989&objAction=browse&viewType=1

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
201 / 207
[R10] RF and Environment survey guideline

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080961&objAction=browse&viewType=1

[R11] UMTS RF Design Network Optimization Guideline based on scanner drives

Kiosklive reference: LTE/IRC/APP/032644

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080970&objAction=browse&viewType=1

[R12] UTRAN Parameters User Guide LR15.x

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68170433&objAction=browse&viewType=1

[R13] UTRAN Parameters User Guide LR14.x

Livelink https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=67320862&objAction=browse&viewType=1

[R14] PEG BTS and RRH LR 15.x

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68404785&objAction=browse&viewType=1

[R15] PEG BTS and RRH LR13.x


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=67309104&objAction=browse&viewType=1

[R16] PEG BTS and RRH LR14.x


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=66997605&objAction=browse&viewType=1

[R17] “Scrambling code planning”


Livelink : https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68551080&objAction=browse&viewType=1

[R18] “Scrambling code group & Tcell recommendation”


Livelink https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68551080&objAction=browse&viewType=1

[R19] “Repeater guidelines”


Livelink https://wcdma-ll.app.alcatel-

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
202 / 207
lucent.com/livelink/livelink.exe?func=ll&objId=68551080&objAction=browse&viewType=1

[R20] “TxDiv for HSDPA”


Livelink : https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68551080&objAction=browse&viewType=1

[R21] Atoll User Manual


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68561222&objAction=browse&viewType=1

[R22] 9955 Technical guideline


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68016206&objAction=browse&viewType=1

[R23] PEG RRH V14.x


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=67276925&objAction=browse&viewType=1

[R24] Antenna link validation


Kiosklive reference: LTE/IRC/APP/032642

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078685&objAction=browse&viewType=1

[R25] “Antenna & OEM”


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078685&objAction=browse&viewType=1

[R26] “UMTS900 GSM900 Co-existence Simulation Study Based on ALU UMTS900 ProductV4”
Livelink https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68079333&objAction=browse&sort=name

[R27] Street to Clutter


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68559730&objAction=browse&viewType=1

[R28] CEM capacity engineering guide


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68456879&objAction=browse&viewType=1

[R29] Antenna Isolation Implementation Guideline


Kiosklive reference: LTE/IRC/APP/032635

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
203 / 207
Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078685&objAction=browse&viewType=1

[R30] " Guidelines for Antenna Isolation between ALU UMTS and other techno“
Kiosklive reference: UMT/IRC/APP/032700

Livelink https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68079333&objAction=browse&sort=name

[R31] "UMTS850 CDMA 850 coexistence simulation study“


Livelink https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68079334&objAction=browse&viewType=1

[R32] Risks linked to UE RF measurements inaccuracy


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080965&objAction=browse&viewType=1

[R33] ” Guidelines for Antenna Isolation between LTE and other technologies ”
Kiosklive reference: LTE/IRC/APP/032647

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68079333&objAction=browse&sort=name

[R34] LTE co-existence vs UMTS in same bands


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68079334&objAction=browse&viewType=1

[R35] LTE 800 vs UMTS 850


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68079334&objAction=browse&viewType=1

[R36] LTE 1900 vs UMTS 2100


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68079334&objAction=browse&viewType=1

[R37] HSxPA Parameters User Guide UA 8.0


Livelink : https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=64440702&objAction=browse&viewType=1

[R38] "CW measurements“


Kiosklive reference: LTE/IRC/APP/032633

Livelink: https://wcdma-ll.app.alcatel-

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
204 / 207
lucent.com/livelink/livelink.exe?func=ll&objId=68080959&objAction=browse&viewType=1

[R39] Internal macro & guideline associated for scanner post-treatment


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080971&objAction=browse&viewType=1

[R40] “Propagation model calibration method”


Kiosklive : LTE/IRC/APP/032645

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078989&objAction=browse&viewType=1

[R41] 3G Small Cell RF guideline


Kiosklive reference: UMT/IRC/APP/035547

Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68081433&objAction=browse&viewType=1

[R42] SPM Default models.xls


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078999&objAction=browse&viewType=1

[R43] RNP simulation white paper


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078648&objAction=browse&viewType=1

[R44] 9955 default propagation models recommended for 400 - 5500 MHz frequency bands
Kiosklive : LTE/IRC/APP/032646

Livelink : https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078989&objAction=browse&viewType=1

[R45] Winprop description and settings


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078998&objAction=browse&viewType=1

[R46] Volcano user guide


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078990&objAction=browse&viewType=1

[R47] Crosswave user manual


Livelink: https://wcdma-ll.app.alcatel-

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
205 / 207
lucent.com/livelink/livelink.exe?func=ll&objId=68078997&objAction=browse&viewType=1

[R48] Magnetic declination to consider for azimuth field implementation


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080961&objAction=browse&viewType=1

[R49] General RF Tools Presentation


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080958&objAction=browse&viewType=1

[R50] NiXT & MT 8222 Presentations


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080958&objAction=browse&viewType=1

[R51] “Outdoor LTE & UMTS metro-cell radio positioning rules”


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68562728&objAction=browse&viewType=1

[R52] Metrocell - tilt & azimuth alignment and control methodology


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68080964&objAction=browse&viewType=1

[R53] Small Cell Selection module


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68582046&objAction=browse&viewType=1

[R54] LTE and UMTS Outdoor Metro cells capacity offload


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68562728&objAction=browse&viewType=1

[R55] ASP/ACP tool description


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078692&objAction=browse&viewType=1

[R56] ATD module with ASP/ACP tool


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078653&objAction=browse&viewType=1

[R57] Footprint Module


Livelink: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=68078652&objAction=browse&viewType=1

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
206 / 207
[R58] Flexi Multiradio BTS RF Module and Remote Radio Head Description

30-06-2016 <Nokia - Proprietary - Use pursuant to Company © Nokia 2021


instruction >
207 / 207

You might also like