3g Radio Network Design

3G RADIO NETWORK DESIGN

RAN PlanningMTC Kuwait

3G Trial

April 19, 2023 3G Radio Network Design 2

Table of Contents

• Introduction• Trial Areas• Link Budget Calculations• Coverage Predictions• Estimated Capacity• Indoor Design• Panoramic View• Pre Hardware Requirements• Equipment Deployed• Scrambling Code Planning• LA/RA Planning• Neighbour Planning• RAN Acceptance / Optimization• Conclusion


INTRODUCTION


Introduction

• One of the Key Characteristic in UMTS Systems is the coverage area is intrinsically linked to the capacity of the system

• The more the traffic , the smaller the coverage range of the cell becomes-Cell Breathing

• Hence the goal is to reach a compromise between Coverage and Capacity

• The following presentation describes the estimated range and capacity for 3 main services

- Voice 12.2Kbps - Video 64.0Kbps - NRT 384.0Kbps


Introduction

• Architecture of a UMTS System


Introduction

• Iub– The Iub interface connects the BTS and RNC.

• Iu -CS– The Iu interface connects the UMTS radio network to the core network. Iu-CS is the circuit switched part of Iu.

• Iu -PS– The Iu interface connects the UMTS radio network to the core network. Iu-PS is the packer switched part of Iu.

• Iur– The Iur interface allows a soft handover between RNC’S.

• Node B– Node B refers to base station. The main purpose of the Node B is to perform air interface processing and part of radio resource management

• Uu– Uu is the interface between the mobile terminal and the BTS


Introduction

• Services are mixed together by power, but with different codes


Introduction

• 3 Handover states in UMTS

SOFTER SOFT HARD


TRIAL AREAS


Trial Areas

• 3 Trial areas + 1 indoor cell have been chosen to check the 3G Performance

• Area 1 is a cluster of 4 sites, mainly to check 3G cluster performance

• Area2 is a isolated cell to check Hard Handovers from Nokia UMTS cells to Nokia GSM cells

• Area3 is a isolated cell to check Hard Handovers from Nokia UMTS cells to Motorola GSM cells

• An indoor cell is installed at MTC Head office to compare the performance between Motorola and Nokia based on various services


Trial Areas

• AREA1 - 4527

- 4555

- 4501

- 4558

AREA1


Trial Areas

• AREA2 - 4262

AREA2


Trial Areas

• AREA3 - 1422

- Indoor

Motorola AREA3


LINK BUDGET CALCULATIONS


Link Budget Calculations

• Since UL is coverage limited we need to balance the UL Path Loss with DL Path Loss

• Noise figure of the WBTS is 5 dB better than the UE’s one. • Eb/No figures are better in UL link budget as the WBTS deploys 2-way

diversity • The DL transmit power is calculated in RNC based on the reference

service • Link Budget is calculated with the following procedure - Maximum Uplink Path Loss per service per user - Maximum Downlink Path Loss per service per user - Maximum Downlink EIRP per connection per service - Maximum TX power for UE / Needed power from BTS per service KJ• Correction factor is applied to the Maximum TX power per connection to

find the average power needed per connection since the users will be distributed all over the cell area



TYPE UL DL UL DL UL DL

LOADING FACTOR 50 70 50 70 50 70

USER DATA RATE (Kbps) 12.2 12.2 64 64 64 384

TX POWER (dbm) 21 28.51849 21 28.91849 21 36

CABLE Losses (db) 0 - 2 0 - 2 0 - 2

BODY Losses (db) 2 - 0 0 - 0 0 - 0

ANTENNA Gain (dbi) 1 + 18 1 + 18 1 + 18

EIRP 20 44.52 22 44.92 22 52.00

NOISE Power (dbm) -105.14 -100.14

-105.14 -100.14

-105.14 -100.14

REQUIRED Eb/No (db) 4.4 - 7.5 - 2 - 5.5 - 2 - 4.8 -

PROCESSING Gain (db) 24.97971 + 24.97971 + 17.78151 + 17.78151 + 17.78151 + 10 +

INTERFERENCE Margin (db) 3.0103 - 5.228787 - 3.0103 - 5.228787 - 3.0103 - 5.228787 -

SOFT HANDOVER MDC Gain (db) 0 + 1 + 0 + 1 + 0 + 1 +

POWER CONTROL Headroom (db) 1.8 - 0 - 1.8 - 0 - 1.8 - 0 -

CABLE Losses (db) 2 - 0 - 2 - 0 - 2 - 0 -

ANTENNA Gain (dbi) 18 + 1 + 18 + 1 + 18 + 1 +

BODY Losses (db) 0 - 2 - 0 - 0 - 0 - 0 -

SOFT HANDOVER Gain (db) 2 + 2 + 2 + 2 + 2 + 2 +

ISOTROPIC POWER (dbm) -138.909 -114.390 -134.111 -111.192 -134.111 -104.111

PATH LOSS (db) 158.91 158.91 156.11 156.11 156.11 156.11



• The CPICH Link budget is also calculated to notice the actual Cell footprint. This is then compared to the UL and DL services to find the Maximum Path loss

• The downlink service Eb/No requirement and processing gain are replaced by the CPICH Ec/Io requirement .

• The CPICH is not combined during soft handover and so there are no soft handover gains for the CPICH link budget

• The terminal antenna gain is assumed to be 0 dB.



CPICH Link Budget

LOADING FACTOR 70

TX POWER (dbm) 33

CABLE Losses (db) 2

BODY Losses (db) 0

ANTENNA Gain (dbi) 18

EIRP 49

NOISE Power (dbm) -100.14

REQUIRED Ec/Io (db) -15

INTERFERENCE Margin (db) 5.22

BODY Losses (db) 2

ISOTROPIC POWER (dbm) -107.92

PATH LOSS (db) 156.92


Link Budget Calculations• From the Link budgets we can conclude that CPICH coverage is the limiting one and hence the Cell range is calculated based upon CPICH pathloss

OUTDOOR LOCATION Prob (%) 95

STANDARD Deviation (db) 7

FADING Margin (db) 11.515

PATHLOSS (db) 145.405

OUTDOOR CELL RANGE 1.69

INCAR LOCATION Prob (%) 95


INCAR Losses (db) 8



INCAR CELL RANGE 1.00

INDOOR LOCATION Prob (%) 95


INDOOR Losses (db) 15



INDOOR CELL RANGE 0.56



Outdoor Incar Indoor

1.69km 1.00km 0.56km

• Since all the cells are at an approximate height of 25-30m and have an average cable loss of 2db we can conclude the following cell range for all the UMTS cells


COVERAGE PREDICTIONS


Coverage Predictions

• The main aim was to ensure a very good indoor coverage within the Best Server area of all UMTS Cells.

• An aggressive tilting of 5 was used to ensure deep indoor coverage.

• We can notice from the various plots that 95% of the Best server area of the cells have very deep indoor coverage

• The predictions was subdivided into 3 separate areas. - Area1 (4257,4555,4558,4501) - Area2 (4262) - Area3 (1422)



• Antenna used in Netact

Simulation CS72761

• Antenna Gain - 18dbi

• Antenna HBW - 65degree

• Antenna VBW - 6 degree



• Parameters used in Netact Simulation


Coverage Predictions• AREA1 (Pilot Strength)


Coverage Predictions• AREA1 (Best Server)


Coverage Predictions• AREA3 (Pilot Strength)


Coverage Predictions• AREA3 (Best Server)



• Radio Parameters, Orientations, Heights and Tilts were tuned to ensure the following - A very small cell overlap (=15%) - Low value of little I (≈0.6) - A very Low noise level - Low value of Ec/Io (-2 to -6) - Well Defined Handover areas (Soft/Softer) - No pilot pollution (0 Polluters)

• The Coverage arrays were subdivided into 3 separate areas. - Area1 (4257,4555,4558,4501) - Area2 (4262) - Area3 (1422)


Coverage Predictions• AREA1 (Little i)


Coverage Predictions• AREA3 (Little i)


Coverage Predictions• AREA1 (Ec/Io)


Coverage Predictions• AREA3 (Ec/Io)


Coverage Predictions• AREA1 (Handover Regions)


Coverage Predictions• AREA3 (Handover Regions)


Coverage Predictions• AREA1 (Pilot Pollution)


Coverage Predictions• AREA3 (Pilot Pollution)



• Since traffic/UMTS users is not known Loading parameters like DL Traffic power and Noise Rise was used to depict per service coverage in cells• From the plots we can notice that the Cell range tends to decrease per service depending on the loading introduced• NRT 384Kbps has a very small cell range and most of it failures are due to DL Eb/No capacity failure, meaning the base station can meet the DL Eb/No criteria but has insufficient power to accommodate new user due to huge loading introduced and cell overlap• NRT 384Kbps is also showing some failures due to DL Eb/No range failure, meaning the base station cannot meet the DL Eb/No criteria because the transmit power would exceed the allowed power for a downlink connection• Many simulations were conducted by changing loading parameters to ensure a coverage for the following services and hence calculate Cell capacity based on Loading parameters - RT Voice 12.2Kbps - RT Video 64Kbps - NRT 384Kbps



• AREA1(Per service Coverage probability)



• AREA3(Per service Coverage probability)


CAPACITY CALCULATIONS


Capacity Calculations

• Capacity shown as a function of Load



• Based on the Loading factors used in service coverage prediction the approximate capacity of a cell can be calculated based on various other link parameters

• The fractional load per user is calculated for each service in UL and DL• Power allocation is done for various Control channels• A little I of 0.5 has been used as obtained from coverage predictions• An IPL correction factor is applied to the DL power per connection derived

from the link budget, since the users are distributed all over the cell and not all of them are at Cell edge

• DL power per connection calculated is then used with the Fractional Load per user to approximately calculate the number of users in a cell based on the UL and DL Load Factors

• Call mix is then created to approximate the users using different services in a cell



• The fractional load per user for the given service has been calculated

UL DL

UL DL

UL DL

USER DATA Rate (Kbps) 12.2 12.2 64 64 64 384

Eb/No (db) 4.4 7.5 2 5.5 2 4.8

W/R (db) 24.97971 24.97971 17.7815117.7815

1 17.78151 10

ACTIVITY Factor (Vj) 0.67 0.63 1 1 1 1

Little I (i) 0.5 0.5 0.5 0.5 0.5 0.5

ORTHOGONALITY Factor xxxxx 0.5 xxxxx 0.5 xxxxx 0.5

LOAD Per user 0.008743 0.011256 0.0386030.05913

6 0.038603 0.301995

TOTAL LOAD 50 70 50 70 50 70

NO OF Users (Fractional Capacity) 57 62 13 12 13 2



• Power per DL connection and Common control channel

power has been calculated

Service 12.2Kbps

64Kbps

384Kbps

Unit Watt dBm Watt dBm Watt dBm

Total NodeB Power 20 43 20 43 20 43

Max Load 10 40 10 40 10 40

Control Channel Power (20% of NodeB max power)

3 34.77121 3 34.77121 3 34.77121

CPICH Power for NodeB 2 33 2 33 2 33

Remaining Control Channel Power for Node B

1 30 1 30 1 30

Remaining Power 7 38.45098 7 38.45098 7 38.45098

Predicted UE Max Power/ Needed NodeB Power per connection

0.710966 28.51849 0.779559 28.91849 3.981072 36

IPL Correction Factor 6 6 0

Corrected UE Power/ Needed NodeB Power

0.18 22.52 0.20 22.92 3.98 36.00

No of Users 39 36 2



• A Call mix example is shown based on load and power calculations.• Node B HW Capacity has also been taken into consideration• The number of subscribers are calculated such that they do not exceed the

loading factors derived or else cell breathing would occur - DL power (40dBm) - UL noise rise (3db)

SERVICE

USERS

12.2 Kbps

64 Kbps

384 Kbps

12.2Kbps Voice 40 0 0

64Kbps Video 0 12 0

384Kbps PS 0 0 2

12.2Kbps Voice + 64Kbps Video 28 5 0

12.2Kbps Voice + 384Kbps PS 24 0 1

12.2Kbps Voice + 64Kbps Video + 384Kbps PS 14 3 1


INDOOR DESIGN


Indoor Design

• An existing design will be used to provide service coverage within MTC head office

• A 3 way splitter and combiners will be used to combine signals from the 2 Node B’s

• Losses per floor are computed and averaged to calculate Path loss

• Correction factor is applied to maximum path loss since users are distributed in various floors of the building

• Available user power is calculated based on Power usage of Common control channels and CPICH power

• Capacity calculations are carried out based on available power, Loading and Hardware resources


Indoor Design

• MTC HEAD OFFICE (Indoor Site)


Indoor Design

• Losses per floor are approximated to calculate average Loss

Floor Antenna

Splitter Cable

Total Loss Average Loss4 3 2 Losses (Db) 1/2 7/8 Losses (Db)

7 1 0 1 1 8 10 21 2.5592 13.5592

15.8094

6 1 0 1 2 11 10 18 2.3636 16.3636

51 0 1 2 11 10 15 2.168 16.168

2 0 1 2 11 10 15 2.168 16.168

4 1 0 1 1 8 10 12 1.9724 12.9724

3 1 0 1 2 11 10 9 1.7768 15.7768

2 1 0 1 2 11 10 6 1.5812 15.5812

1 1 1 1 0 11 10 3 1.3856 15.3856

Ground 1 1 1 0 11 10 0 1.19 15.19

Parking 1 1 1 0 11 10 3 1.3856 15.3856

Basement1 1 1 1 14 10 6 1.5812 18.5812

2 1 1 1 14 10 6 1.5812 18.5812


Indoor Design• Link Budget Calculations

TYPE UL DL

UL DL

UL DL

LOADING FACTOR 50 70 50 70 50 70

USER DATA RATE (Kbps) 12.2 12.2 64 64 64 384

TX POWER (dbm) 21 14.71849 21 16.71849 21 30.5

CABLE Losses (db) + Attenuator 0 - 26 0 - 26 0 - 26

BODY Losses (db) 2 - 0 0 - 0 0 - 0

ANTENNA Gain (dbi) 1 + 2 1 + 2 1 + 2

EIRP 20 -9.28 22 -7.28 22 6.50

NOISE Power (dbm) -105.14 -100.14 -105.14 -100.14 -105.14 -100.14

REQUIRED Eb/No (db) 9 - 9.5 - 6.5 - 7 - 5.5 - 6 -

PROCESSING Gain (db) 24.97971 + 24.97971 + 17.78151 + 17.78151 + 17.78151 + 10 +

INTERFERENCE Marfin (db) 3.0103 - 5.228787 - 3.0103 - 5.228787 - 3.0103 - 5.228787 -

SOFT HANDOVER MDC Gain (db) 0 + 1 + 0 + 1 + 0 + 1 +

POWER CONTROL Headroom (db) 5 - 0 - 5 - 0 - 5 - 0 -

CABLE Losses (db) + Attenuator 26 - 0 - 26 - 0 - 26 - 0 -

ANTENNA Gain (dbi) 2 + 1 + 2 + 1 + 2 + 1 +

BODY Losses (db) 0 - 2 - 0 - 0 - 0 - 0 -

SOFT HANDOVER Gain (db) 0 + 0 + 0 + 0 + 0 + 0 +

ISOTROPIC POWER (dbm) -89.10941 -118.3909 -84.41121 -113.6927 -85.41121 -100.9112

Correction Factor 8 6 0

PATH LOSS (db) 109.11 109.11 106.41 106.41 107.41 107.41


Indoor Design• Since the indoor cell is isolated we have used a little i of 0.2 and orthogonality factor of 0.8 in load calculations

UL DL

UL DL

UL DL

USER DATA Rate (Kbps) 12.2 12.2 64 64 64 384

Eb/No (db) 9 9.5 6.5 7 2 6

W/R (db) 24.97971 24.97971 17.78151 17.78151 17.78151 10

ACTIVITY Factor (Vj) 0.65 0.63 1 1 1 1

Little I (i) 0.2 0.2 0.2 0.2 0.2 0.2

ORTHOGONALITY Factor xxxxx 0.8 xxxxx 0.8 xxxxx 0.8

LOAD Per user 0.019367 0.007136 0.083147 0.033412 0.030882 0.159243

TOTAL LOAD 50 70 50 70 50 70

NO OF Users (Fractional Capacity) 26 98 6 21 16 4


Indoor Design• Approximate number of users have been calculated based on Node B power, Common Control channel power

Service 12.2

64

384

Unit Watt dBm Watt dBm Watt dBm

Total NodeB Power 8 39 8 39 8 39

Max Loading 5 37 5 37 5 37

CPICH Power for NodeB 1 30 1 30 1 30

Remaining Control Channel Power for Node B

1 30 1 30 1 30

Remaining Power 3 3 3

Predicted Power per user 0.029638 14.71849 0.046973 16.71849 1.122018 30.5

No of Users 101 64 3


Indoor Design

• Combining the results of users calculated based on Fractional Load and users calculated based on Power availability we can approximate the users for various services as follows keeping into mind the HW channel capacity of the Node B

CALL MIX

USERS

12.2Kbps

64Kbps384Kbp

s

12.2Kbps Voice 25 0 0

64Kbps Video 0 6 0

PS 384Kbps 0 0 2

12.2Kbps Voice + 64kbps Video 17 2 0

12.2Kbps Voice + PS 384Kbps 22 0 1

64Kbps Video + PS 384Kbps 0 5 1

12.2Kbps Voice + 64Kbps Video + PS 384Kbps 12 3 1


PANORAMIC VIEW


Panoramic View4501 – Sector 1, Sector 2, Sector 3


PRE HARDWARE REQUIREMENTS


Pre Hardware Requirements

CELLNAME Bore Antenna Type Antenna Height Tilt

4527A 100 CS72761 30 5

4527B 230 CS72761 25 5

4527C 350 CS72761 25 5

4555A 30 CS72761 30 5

4555B 165 CS72761 30 5

4555C 270 CS72761 30 5

4501A 70 CS72761 20 5

4501B 220 CS72761 25 5

4501C 330 CS72761 20 5

4558A 60 CS72761 30 5

4558B 180 CS72761 25 5

4558C 300 CS72761 30 5

4262A 60 CS72761 25 3

4262B 175 CS72761 23 3

4262C 300 CS72761 23 3

1422A 60 CS72761 15 3

1422B 160 CS72761 15 3

1422C 330 CS72761 15 3


EQUIPMENT DEPLOYED


Equipment Deployed

Nokia UltraSiteWCDMA BTS Supreme

Indoor Outdoor

Nokia MetroSiteWCDMA BTS

• NODE-B Types


Equipment Deployed

• Nokia UltraSite WCDMA BTS Supreme Indoor

WEA, EXTERNAL ALARMS

WFA, FAN

AXU, ATM MULTIPLEXER

WPS, POWER SUPPLY

WPA, POWER AMPLIFIER

WTR, TRANSMITTER AND RECIEVER WIC, INPUT COMBINER

IFU X 5, INTERFACE UNIT

WAF, ANTENNA FILTER

WSC, SYSTEM CLOCK

WSM, SUMMING AND MULTIPLEXING

WSP x 6, SIGNAL PROCESSOR

WAM x 2, APPLICATION MANAGER


Equipment Deployed

• NODE-B Specification (SUPREME)

PARAMETER SUPREME INDOOR SUPREME OUTDOOR

Height 1800mm 1940mm

Width 600mm 770mm

Depth 600mm 790mm

TX Frequency Range 2110-2170 MHz 2110-2170 MHz

RX Frequency Range 1920-1980 MHz 1920-1980 MHz

Channel Spacing 5 MHz 5 MHz

TX Power at Antenna Connector

10-40 W 10-40 W


Equipment Deployed

• Nokia MetroSite WCDMA BTS


Equipment Deployed

• NODE-B Specification (METRO)

PARAMETER METRO

Height 1072mm

Width 273mm

Depth 418mm

TX Frequency Range 2110-2170 MHz

RX Frequency Range 1920-1980 MHz

Channel Spacing 5 MHz

TX Power at Antenna Connector

8 W / 4 W


Equipment Deployed

• NODE-B Installed

SITE Quantity Power Configuration WSP WAMHW

ChannelsType

4527 1 20 1+1+1 1 2 64Supreme

Indoor

4555 1 20 1+1+1 1 2 64Supreme outdoor

4501 1 201+1+1

1 2 64Supreme outdoor

4558 1 20 1+1+1 1 2 64Supreme

Indoor

4262 1 20 1+1+1 1 2 64Supreme

Indoor

1422 1 20 1+1+1 1 2 64Supreme

Indoor

MTC-HQ 1 8 1 1 1 64 Metro


Equipment Deployed

• NODE-B Possible upgrades (SUPREME)

CONFIGURATION NO. OF CABINETS Power HW Channels

1+1+1 1 20 1152

1+1+1 1 40 1152

2+2+2 1 20 1152

2+2+2 1 10 1152

3+3+3 1 20 1152

4+4+4 1 10 1152

4+4+4 1 20 1152

1+1+1+1+1+1 1 20 1152

2+2+2+2+2+2 1 20 1152

1 carrier, omni 1 20 1152


Equipment Deployed

• NODE-B Possible upgrades (METRO)

CONFIGURATION NO. OF CABINETS Power HW Channels

1 1 8 128

2 1 4 64

2 1 4 128


Equipment Deployed

RNC Front View RNC Internal View


Equipment Deployed

RNC Specifications

• Height 1800 mm• Width 600 mm• Depth 600 mm • Weight (fully loaded) 220 kg• Power Consumption 3.0 kW• Capacity 48 - 196 Mbit/s• Nominal Voltage - 48 V DC


Equipment Deployed

• RNC Configurations

PD

20

TB

UF

TB

UF

NIU

NB

MX

62

2

CC

PC

3IC

SU

CD

SP

DM

CU

TS

S3

TB

UF

CC

PC

3O

MU

0

PD

20

HD

S9

MC

PC

2

NE

MU

EB

R

NI4

S1

CC

PC

3R

RM

U 0

CC

PC

3R

CM

U 0

HD

S9

SF

10

SF

U 0

TS

S3

TB

UF

CC

PC

3O

MU

1

PD

20

HD

S9

NI4

S1

CC

PC

3R

RM

U

1C

CP

C3

RC

MU

1

HD

S9

SF

10

SF

U 1

MO

D

NIU

NB

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CC

PC

3IC

SU

MX

62

2

CC

PC

3G

TP

U

A2LS

PD

20

TB

UF

TB

UF

NIU

NB

MX

62

2

CC

PC

3IC

SU

CD

SP

DM

CU

NIU

NB

CD

SP

DM

CU

CD

SP

DM

CU

CC

PC

3IC

SU

MX

62

2

CC

PC

3G

TP

U

A2LS

PD

20

TB

UF

TB

UF

NIU

NB

MX

62

2

CC

PC

3IC

SU

CD

SP

DM

CU

NIU

NB

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CC

PC

3IC

SU

MX

62

2

CC

PC

3G

TP

U

A2LS

CD

SP

DM

CU

PD

20

TB

UF

TB

UF

NIU

NB

MX

62

2

CC

PC

3IC

SU

CD

SP

DM

CU

NIU

NB

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CC

PC

3IC

SU

MX

62

2

CC

PC

3G

TP

U

A2LS

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

NIU

NB

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

NIU

NB

CC

PC

3G

TP

UC

CP

C3

ICS

U

A2LS

A2LS

CD

SP

DM

CU

CD

SP

DM

CU

NI4

S1

NI4

S1

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

PD

20

TB

UF

TB

UF

NIU

NB

MX

62

2

CC

PC

3IC

SU

CD

SP

DM

CU

NIU

NB

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CC

PC

3IC

SU

MX

62

2

CC

PC

3G

TP

U

A2LS

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

PD

20

TB

UF

TB

UF

NIU

NB

MX

62

2

CC

PC

3IC

SU

CD

SP

DM

CU

NIU

NB

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CC

PC

3IC

SU

MX

62

2

CC

PC

3G

TP

U

A2LS

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

CD

SP

DM

CU

2

3

4

5

1


Equipment Deployed

• Five Different RNC configurations

Configuration

Max. capacity in different configurations

Iub traffic capacity Interfaces

Iub Mbit/s

Carriers STM-1 E1

1 48 384 16 96

2 85 576 16 128

3 122 768 16 160

4 159 960 16 192

5 196 1152 16 224


Equipment Deployed• NODE-B – RNC Connections

WAM

BS

WAM

WAM

ATM connection TableHW VPI VCI

x x x

VCI

x

VPI

x

HW

x

Term-1Term-1Term-1Term-1Term-1Term-1Term-1

1111111

1234567

TCP/IPAXC

NMS

C-NBAP

TCP/IP

D-NBAP

UP

C-NBAP

TCP/IP

UP

AAL2 sig

C-NBAP

TCP/IP

D-NBAP

UP

UP

AAL2 sig

D-NBAP

UP

UP

AAL2 sig

RNC

AXU

78910111213

5555555

Term-2Term-2Term-2Term-2Term-2Term-2Term-2

ATM VPC’S (DNC)

To other BTSs


Equipment Deployed

NOKIA SGSN

CASE 1

IP PLAN (NOKIA SGSN)


Equipment Deployed

MOTOROLA SGSN

CASE 2

IP PLAN (MOTOROLA SGSN)

MOTOROLA CORE NETWORK


SCRAMBLING CODE PLANNING


Scrambling Code Planning

• 3G standard specifies that there are 512 downlink primary scrambling codes • 3G standard specifies that the 512 downlink primary scrambling codes are

organized into 64 groups of 8 • Each cell within the radio network plan must be assigned a primary

scrambling code • The most important rule for scrambling code planning is that the isolation

between cells which are assigned the same scrambling code should be sufficiently great to ensure that a UE never simultaneously receives the same scrambling code from more than a single cell.

• scrambling codes 0 to 7 belong to the same group, as do scrambling codes 8 to 15 and scrambling codes 16 to 23.

• The organization of scrambling codes into groups allows the UE to complete a three step cell synchronization procedure using the primary and secondary synchronization channels (P-SCH and S-SCH) and the CPICH

• This procedure is applied whenever a UE needs to access a cell or measure the quality of a cell



• The three step synchronization procedure is:

- UE uses the P-SCH to achieve slot synchronization

- UE uses the S-SCH to achieve frame synchronization and to identify

the scrambling code group

- UE uses the CPICH to identify the primary scrambling code• Step 2 involves selecting 1 group out of 64, whereas step 3 involves selecting 1

code out of 8. Step 3 is likely to be more reliable but also requires more UE processing, i.e. has a greater potential impact upon UE battery life.

• Placing the emphasis upon step 2 can be achieved by planning the scrambling codes such that neighbours belong to different scrambling code groups. This helps reduce UE power consumption

• Placing the emphasis upon step 3 can be achieved by planning the scrambling codes such that neighbours belong to the same scrambling code group. This helps to improve the reliability of the cell synchronization procedure



Name Scope Range Default

PriScrCode WCEL 0 to 511, step 1 None

AdjsScrCode ADJS 0 to 511, step 1 None

AdjiScrCode ADJI 0 to 511, step 1 None

Tcell WCEL0 to 2304, step 256

chips0, 256, 512 for the 3 cells of a 3 sector Node B

RNC databuild parameters relevant to scrambling code planning



CELLNAME CI

PLAN1 - STEP3 PLAN2 - STEP2

Scrambling CodeScrambling Code

GroupScrambling Code Scrambling Code Group

34527A 30001 0 1 0 1

34527B 30002 1 1 0 2

34527C 30003 2 1 0 3

34555A 30004 3 1 0 4

34555B 30005 4 1 0 5

34555C 30006 5 1 0 6

34501A 30007 6 1 0 7

34501B 30008 7 1 0 8

34501C 30009 0 2 0 9

34558A 30010 1 2 0 10

34558B 30011 2 2 0 11

34558C 30012 3 2 0 12

34262A 30013 0 1 0 13

34262B 30014 1 1 0 14

34262C 30015 2 1 0 15

31422A 30016 3 1 0 16

31422B 30017 4 1 0 17

31422C 30018 5 1 0 18

MTC Indoor A 30019 6 1 0 19


LA/RA PLANNING


LA/RA PLANNING

• Mobility Management in the Core network maintains the UE location in UMTS network

• In CS Idle mode, Core network knows the location of a UE with the accuracy of LA, and in PS Idle mode, Core network knows the location of a UE with the accuracy of LA/RA

• A Location Area (LA) is defined as an area within which a UE can move without having to update the VLR.

• A Routing Area (RA) is defined as an area within which a UE can move, in certain operation modes, without having to update the SGSN


LA/RA PLANNING

CELLNAME CI LAC SAC RAC

34527A 30001 3000 300 30

34527B 30002 3000 300 30

34527C 30003 3000 300 30

34555A 30004 3000 300 30

34555B 30005 3000 300 30

34555C 30006 3000 300 30

34501A 30007 3000 300 30

34501B 30008 3000 300 30

34501C 30009 3000 300 30

34558A 30010 3000 300 30

34558B 30011 3000 300 30

34558C 30012 3000 300 30

34262A 30013 3000 300 30

34262B 30014 3000 300 30

34262C 30015 3000 300 30

31422A 30016 3000 300 30

31422B 30017 3000 300 30

31422C 30018 3000 300 30

MTC Indoor 30019 3000 300 30


NEIGHBOUR PLANNING


Neighbour Planning

• 3G intra-frequency neighbour list planning is absolutely critical to network performance as the missing neighbours are regarded as interference. Typically the neighbour list tuning gives the greatest gain during RF optimization. • Each UTRAN cell shall have separate neighbour cell definitions for intra-frequency, inter-frequency and inter-RAT (GSM) measurements. The maximum number of neighbouring cells that can be signalled to the UE is:

- 31 intra-frequency neighbours

- 48 inter-frequency neighbours

- 32 inter-RAT (GSM) neighbours • Neighbour were defined per cell based on Best Server predictions and antenna orientation• All 3G Neighbours defined are mutual neighbours while all 2G neighbours are one way


Neighbour Planning


AdjsId ADJS 1 to 31, step 1 None

AdjsMCC ADJS 0 to 999, step 1 None

AdjsMNC ADJS 0 to 999, step 1 None

AdjsMNCLength ADJS 2, 3 None

AdjsLAC ADJS 1 to 65535, step 1 None

AdjsRAC ADJS 0 to 255, step 1 None

AdjsRNCid ADJS 1 to 4095, step 1 None

AdjsCI ADJS 1 to 65535, step 1 None

AdjsScrCode ADJS 0 to 511, step 1 None

AdjsCPICHTxPwr ADJS -10 to 50, step 0.1 dBm None

AdjsTxPwrRACH ADJS -50 to 33, step 1 dBm 21 dBm

AdjsEcNoOffset ADJS -10 to 10, step 0.5 dB 0 dB

AdjsDERR ADJS 0 (enable), 1 (disable) 0

AdjsTxDiv ADJS 0 (not used), 1 (used) 0

RtHopsIdentifier ADJS 1 to 100, step 1 None

NrtHopsIdentifier ADJS 1 to 100, step 1 None

RNC databuild parameters for Intra frequency Neighbours


Neighbour Planning

3G <- > 3G

CELLNAME N1 N2 N3 N4 N5 N6 N7

3G_45271 3G_45272 3G_45273 3G_45581 3G_45582 3G_45011

3G_45272 3G_45271 3G_45273 3G_45552 3G_45011 3G_45012 3G_45013

3G_45273 3G_45271 3G_45272 3G_45581 3G_45582 3G_45583 3G_45551 3G_45552

3G_45551 3G_45552 3G_45553 3G_45273 3G_45581 3G_45582 3G_45583

3G_45552 3G_45551 3G_45553 3G_45273 3G_45272 3G_45011 3G_45013

3G_45553 3G_45551 3G_45552 3G_45013 3G_45583 3G_45012

3G_45011 3G_45012 3G_45013 3G_45552 3G_45272 3G_45271

3G_45012 3G_45011 3G_45013 3G_45553 3G_45272

3G_45013 3G_45011 3G_45012 3G_45552 3G_45553 3G_45272

3G_45581 3G_45582 3G_45583 3G_45271 3G_45273

3G_45582 3G_45581 3G_45583 3G_45551 3G_45271 3G_45272 3G_45273

3G_45583 3G_45581 3G_45582 3G_45551 3G_45553

3G_42621 3G_42622 3G_42623

3G_42622 3G_42621 3G_42623

3G_42623 3G_42622 3G_42621

3G_14221 3G_14222 3G_14223

3G_14222 3G_14221 3G_14223

3G_14223 3G_14221 3G_14222

• Following are the 3G to 3G Neighbour Definitions


Neighbour Planning


AdjgId ADJG 0 to 31, step 1 None

AdjgBandIndicator ADJG 1 (1900), 0 (1800) None

AdjgBCCH ADJG 0 to 1023, step 1 None

AdjgBCC ADJG 0 to 7, step 1 None

AdjgNCC ADJG 0 to 7, step 1 None

AdjiMCC ADJG 0 to 999, step 1 None

AdjiMNC ADJG 0 to 999, step 1 None

AdjiMNCLength ADJG 2, 3 None

AdjiLAC ADJG 1 to 65535, step 1 None

AdjiCI ADJG 1 to 65535, step 1 None

AdjiTxPwrRACH ADJG -50 to 33, step 1 dBm None

AdjiTxPwrTCH ADJG 0 to 43, step 1 dBm None

RtHopiIdentifier ADJG 1 to 100, step 1 None

NrtHopiIdentifier ADJG 1 to 100, step 1 None

RNC databuild parameters for Inter frequency Neighbours


Neighbour Planning

3G - > 2G

CELLNAME N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15

3G_45271 45271 45272 45583 45581 45582 45011 65051 65052

3G_45272 45271 45272 45273 45552 45011 45012 45013 65051 65052 55111 55112 55113

3G_45273 45271 45272 45273 45581 45582 45583 45551 45552 55111 55113 65051 65052

3G_45551 45551 45552 45553 45273 45581 45582 45583 55111 55113 45162 45301

3G_45552 45551 45552 45553 45273 45272 45011 45013 65052 55111 55112 55113

3G_45553 45551 45552 45553 45013 45583 45012 45162 45301 45302 45901 55113

3G_45011 45011 45012 45013 45552 45272 45271 65051 65052 55111 55112 55113

3G_45012 45011 45012 45013 45553 45272 45471 65052 55112 45302

3G_45013 45011 45012 45013 45552 45553 45272 45901 45302 55112 55113 45471

3G_45581 45581 45582 45583 45271 45273 44151 45301

3G_45582 45581 45582 45583 45551 45271 45272 45273 55111 65051 65052

3G_45583 45581 45582 45583 45551 45553 45161 45162 44151 45301

3G_42621 42621 42622 42623 42382 42383 42053 42462 42282 42262

3G_42622 42621 42622 42623 42382 42053 42101 42103 42933

3G_42623 42621 42622 42623 42282 42283 42262 42462 42933 42103 42053

3G_14221 14221 14222 14223 14081 14082 14083 14153 14212 14731 14733 14741 14913 24031 24101 24102

3G_14222 14221 14222 14223 14082 14151 14153 14731 14732 14733 14741 14742 14831 14912 14913 24411

3G_14223 14221 14222 14223 14082 14083 14733 14741 14742 14743 24021 24022 24031 24101 24102 24411

• Following are the 3G to 2G Neighbour Definitions


RAN ACCEPTANCE & OPTIMIZATION


RAN Acceptance & Optimization

• Following procedures shall be carried out to verify Network Performance

- Acceptance process

- Measurement methodologies

- Measurement test plan

- Key Performance Indicators (KPI’S)



Network Planning Rollout Phase

Processing of Data

Cluster Test result versus cluster target value

Execution of Drive Test in Cluster1 to n

Processing of Data

Network/ RAN Area Test result versus Network/ RAN Area target value

Execution of Drive Test in Whole Network or RAN Area 1 to n

Cluster Acceptance Certificate

Network Acceptance Certificate

Cluster Acceptance

Network Acceptance

NW optimisation



Measurement routes have to be classified for cluster and Network Acceptance

It is recommended to measure different type of routes like

- Streets (city, urban)

- Highways (suburban, rural)

- Major roads (urban, suburban, rural)

Cluster to be measured

Network Measurement Route

Cluster measurement Route


RAN Acceptance & Optimization• The acceptance test shall consist of drive tests using Field Measurement Tools (FMT)

to verify that the call set-up and soft handovers are working properly, to detect bad quality and interference areas, to detect unexpected lack of coverage and to test the Radio Access Bearers (RAB).

• The UE shall measure at least the following and report these measurements to the FMT:

- CPICH Received Signal Code Power (RSCP)

- UTRA Carrier Received Signal Strength Indicator (RSSI)

- Common Pilot Channel (CPICH) Ec/No

- UE transmitted power• Measurements shall be restricted to

the coverage border of a cluster

Valid Measurement sampleInvalid Measurement sample


RAN Acceptance & Optimization• The purpose of cluster acceptance test is to divide the whole network

into smaller regions as to perform RF design verification, identify and categorize coverage and quality problems.

• All sites in the cluster must have Site Acceptance completed before the measurements. The drive route in the cluster shall be planned in such a way that it covers highway, main roads and major streets,

• The measurement samples will be filtered according to the CPICH RSCP and Ec/No thresholds

- 105dBm

- 92dBm

- 80dBm

Time

RSCP

Call OK

Call OK

Call OK

Call NOK

Call OK

- 12dB

- 5dB

- 20dB

Ec/No

Threshold

Example of Call Success Criteria

– Case 1

Discard sample

OR

- 105dBm

- 92dBm

- 80dBm

Time

RSCP

Call OK

Call OK

Call OK

Call NOK

Call OK

-

- 5dB

- 20dB

Ec/No

Threshold


– Case 1

Discard sample

- 105dBm

- 92dBm

- 80dBm

Time

RSCP

Call OK

Call OK

Call OK

Call NOK

Call OK - 5dB

- 20dB

Ec/No

Threshold


– Case 1

Discard sample

OR OR


RAN Acceptance & Optimization• The Measurement/Cluster plan shall include

- Identification of the Sites forming the Cluster

- Identification of cells within the Cluster scheme;

- Drive test routes within the Cluster.

- Identification of measurements to be obtained during the Drive Test;

- Test duration, scheduled date and time

• Upon completion of the processing of data per Cluster, a Cluster specific Test report will be prepared and submitted to the customer. The cluster test report shall include:

- Cluster and Sites Information

- RNC Parameters database.

- Coverage Prediction Plots.

- CPICH RSCP and Ec/No plotted on the measurement route.

- Measurement Results

- Outstanding Issues and Further Actions



• The main Hardware and Parameter adjustments to be made involve:– Tilting– Antenna height– CPICH Power– Cell selection/reselection parameters– Neighbour List tuning– SHO Parameters like “Add", "Drop” and “Replace” windows– Intersystem Handover/Cell Selection Parameters



• Key Performance Indicators (KPIs) should be used as conclusive results of the RAN performance

• Typical KPIs Classes:– Service Performance KPI’S

– Coverage KPI’S

– Performance Management KPI’S


RAN Acceptance & Optimization• SERVICE PERFORMANCE KPI’S

- Voice Success Rate > 95%

- Video Success Rate > 95%

- PS Success Rate > 95%

- Voice Drop Rate < 4%

- Video Drop Rate < 4%

- PS Drop Rate < 4%

- Throughput for NRT Traffic

> 58Kbps for 90% of time (64kbps)

> 112Kbps for 90% of time (128kbps)

> 340Kbps for 90% of time (384Kbps)


RAN Acceptance & Optimization• COVERAGE KPI’S

- CPICH RSCP > -92dbm (90% OF SAMPLES)

- CPICH Ec/Io > -9db (90% OF SAMPLES


RAN Acceptance & Optimization• PERFORMANCE MANAGEMENT KPI’S

- Voice RAB Setup Success Rate > 95%

- Voice RAB Drop Rate < 4%

- Video RAB Setup Success Rate > 95%

- Video RAB Drop Rate < 4%

- PS RAB Setup Success Rate > 95%

- PS RAB Drop Rate < 4%

- Soft Handover Overhead > 95%


CONCLUSION


Conclusion

• The planning process for UMTS is an iterative process, as both coverage and capacity demands must be achieved

• The process can be broken down into two main stages:– Stage 1

• Link Budget Calculations• Coverage Plots and Simulations• Data Analysis and Hardware Tuning• Capacity Calculations (within loading, power and physical

channel limitations)

– Stage 2 • Network Implementation• Performance measurements• Network Optimization

3g Radio Network Design

Documents

Transcript of 3g Radio Network Design