Network Design

Radio Network Design Guideline

of 91

Revision History

of 91

Table of Contents

Revision History .......................................................................................................................... 2

Table of Contents ........................................................................................................................ 3

1 Overview ............................................................................................................................. 5

2 Site Design Guideline .......................................................................................................... 6

2.1 BTS and NodeB Configuration ..................................................................................... 6 2.2 Technical Specification of Antenna System ............................................................... 11 2.3 Antenna System Design Requirements ..................................................................... 12 2.4 Feeder and Jumper Requirements ............................................................................ 13 2.5 TMA Design Requirements ........................................................................................ 14 2.6 RET Solution for Macro BTS ..................................................................................... 15

3 Coverage Planning Guideline ............................................................................................ 18

3.1 Coverage Design Requirement .................................................................................. 18 3.2 Propagation Model .................................................................................................... 19 3.3 Digital Map Resolution............................................................................................... 20 3.4 GSM Link Budget ...................................................................................................... 21 3.5 UMTS Link Budget .................................................................................................... 23 3.6 Planning Tool ............................................................................................................ 30

4 Capacity Planning Guideline.............................................................................................. 31

4.1 GSM Output Power Setting ....................................................................................... 31 4.2 GSM Time Slot/TRX Design Principle ........................................................................ 34 4.3 GSM Frequency Planning (SFH) ............................................................................... 35 4.4 Abis Dimensioning Guideline ..................................................................................... 36 4.5 UMTS Channel Power Setting ................................................................................... 40 4.6 CE Dimensioning Guideline ....................................................................................... 41 4.7 Iub Dimensioning Guideline ....................................................................................... 50

5 Radio Resource Capacity Management............................................................................. 60

5.1 General Aggregation Rule ......................................................................................... 60 5.2 TCH Utilization Evaluation Rule ................................................................................. 61 5.3 SDCCH Utilization Evaluation Rule ............................................................................ 62 5.4 PDCH Evaluation Rule .............................................................................................. 62 5.5 Abis Utilization Evaluation Rule ................................................................................. 62 5.6 UMTS Power Utilization Evaluation Rule ................................................................... 63 5.7 CE Utilization Evaluation Rule ................................................................................... 64 5.8 Code Utilization Evaluation Rule ................................................................................ 64 5.9 RTWP Utilization Evaluation Rule .............................................................................. 65 5.10 Iub Utilization Evaluation Rule ................................................................................... 65 5.11 Common Channel Utilization Evaluation Rule ............................................................ 66 5.12 UMTS Multi Carrier Expansion Principle .................................................................... 67

6 Trigger of New Site Planning ............................................................................................. 68

of 91

6.1 Due to Coverage Reasons ........................................................................................ 68 6.2 Due to Capacity Reasons .......................................................................................... 68 6.3 Other Factors ............................................................................................................ 68

7 BSC6900 Design Principle ................................................................................................ 69

7.1 BSC Capacity Planning Principle ............................................................................... 69 7.2 RNC Capacity Planning Principle............................................................................... 69

8 BSC6900 Capacity Management....................................................................................... 70

8.1 General Aggregation Rule ......................................................................................... 70 8.2 BSC6900 Board Resource and Expansion Threshold ................................................ 71 8.3 BSC6900 GSM License and Evaluation Threshold .................................................... 73 8.4 BSC6900 UMTS License and Evaluation Threshold .................................................. 73 8.5 BSC6900 A Interface Evaluation Rule ....................................................................... 73 8.6 BSC6900 Gb Interface Evaluation Rule ..................................................................... 74 8.7 BSC6900 SS7 Load Utilization Evaluation Rule ......................................................... 74 8.8 BSC6900 Ater Load Evaluation Rule ......................................................................... 74 8.9 BSC6900 Iu-CS Interface Evaluation Rule ................................................................. 74 8.10 BSC6900 Iu-PS Interface Evaluation Rule ................................................................. 74

9 Cell Detail Design.............................................................................................................. 75

9.1 BSIC Planning Principle ............................................................................................ 75 9.2 GSM LAC Planning Principle ..................................................................................... 75 9.3 UMTS LAC Planning Principle ................................................................................... 76 9.4 UMTS SAC Planning Principle ................................................................................... 76 9.5 PSC Planning Principle ............................................................................................. 77 9.6 Tcell Planning Principle ............................................................................................. 80 9.7 PLMN Value Tag Planning Principle .......................................................................... 81

10 HSPA/HSPA+ and Multi Carrier and Layer Deployment Strategy ....................................... 82

10.1 UMTS (Single Carrier)/GSM Layering Design ............................................................ 82 10.2 UMTS (Dual Carrier)/GSM Layering Design............................................................... 85 10.3 HCS Strategy ............................................................................................................ 87 10.4 HSPA/HSPA+ Rollout Strategy .................................................................................. 88

11 GSM & UMTS Key Parameter Design Guideline ................................................................ 89

12 BSS/RAN Feature Implementation Guideline ..................................................................... 90

13 Annexes ............................................................................................................................ 91

of 91

1 Overview

of 91

2 Site Design Guideline 2.1 BTS and NodeB Configuration Note: The following antenna solution pictures are only typical for reference; the detail antenna system is subject to the actual design condition.

i. BTS3900 (Macro indoor): GSM only

Software upgrade to increase GSM capacity from G2/2/2@20W to G4/4/4@20W

6 MRFU are required for G 4/4/4@20w and up to G8/8/8@20W

of 91

ii. BTS3900 (Macro indoor): GSM/UMTS SingleRAN

Software upgrade to increase GSM and UMTS capacity from G222/U1/1/1 to

G4/4/4U2/2/2

6 MRFU and 6 WRFU are required for G6/6/6 U2/2/2MIMO up to G8/8/8 U2/2/2 MIMO.

of 91

iii. BTS3900A (Macro outdoor): GSM only

Complete site solution including battery backup, power supply and space for

microwave transmission

Software upgrade to increase GSM capacity from G2/2/2@20W to G4/4/4@20W

6 MRFU are required for G6/6/6@20W and up to G8/8/8@20W

iv. BTS3900A (Macro outdoor): GSM/UMTS SingleRAN


microwave transmission

Software upgrade to increase GSM and UMTS capacity from G2/2/2 U1/1/1@20W

to G4/4/4 U2/2/2@20W

6 MRFU and 6 WRFU are required for G6/6/6 U2/2/2MIMO@20W up to G8/8/8

U2/2/2 MIMO@20W..

of 91

v. DBS3900 (Distributed Base Station Solution): GSM/UMTS SingleRAN

RRU 3804 is applied for UMTS feeder less solution, RRU 3908 is applied for GSM

feeder less solution.


microwave transmission and BBU

Remote radio units is installed as near as possible to the antenna, hence saving on

the feeders and improving coverage

Software upgrade to increase GSM and UMTS capacity from G2/2/2 U1/1/1@20W

to G4/4/4 U2/2/2@15W. RRU3908 is for GSM and RRU3804 is for WCDMA

of 91

Based on the distance between a BBU and an RRU, CPRI networking is classified into short-distance

remote networking and long-distance remote networking.

For the short-distance remote networking which using CPRI fiber optic cable between a BBU and an

RRU, the longest distance between an RRU and a BBU on a CPRI chain does not exceed 100 m.

For the long-distance remote networking which using single-mode fiber optic cable between a BBU and

an ODF or between an ODF and an RRU, the longest distance between an RRU and a BBU on a CPRI

chain ranges from 100 m to 40,000 m.

DBS Solution (RRU+BBU) should be only applied for feeder less scenario.

For GSM sites, DBS solution should be applied for scenario which saved loss compare to macro BTS is

more than 1.24dB (20W 15W = 43dBm 41.76dBm = 1.24 dB)

(Saved loss = loss of macro BTS solution loss of feeder less solution)

If one site planed with feeder less scenario, but final design (after engineering survey) result shows feeder

less solution is not applicable, Macro BTS (BTS 3900 OR BTS 3900A) should be applied instead of (DBS

3900)

If the RRU cannot mount close to the antenna, the RRU solution should change to Macro BTS solution.

of 91

2.2 Technical Specification of Antenna System

Product Model Description

Antenna A19451803 Dual Band Antenna -65 (XPOL, 1710 - 2170MHz, 18.0 dBi, V7, Electrical Down tilt 2 ~ 10

Antenna A19451901 Dual band Antenna 65 (XPOL, 1710-2170MHz, 19.5 dBi, V7, Electrical Down tilt 2 ~ 8

Antenna ADU451802 Dual Band Antenna, Quad Port -65 (XXPOL), 1710 - 2170MHz, 18 dBi,v7, Electrical Down tilt.2 ~ 10

Antenna ADU451900 Dual Band Antenna, Quad port 65 (XXPOL), 1710 2170MHz, 19.5dBi, Electrical Down tilt 2 ~ 8

Antenna A19452100 XPOL Panel 1710 - 2170 -65 21 dBi, Fixed tilt 0.

RCU ARCU02001 Antenna Feeder Accessories, Agisson RET Antenna Driving Motor RCU089, 10 ~ 30V, AISG2.0

TMA ATA182000

Triplex Tower Mounted Amplifier Module, DTMA 1800 - GSM 1800 - Tx: 1805 ~ 1880MHz, Rx : 1710 ~ 1785 MHz, 12.2. 6,7/16 DIN Female, 9~30V(DC), AISG2.0

TMA KIT 02230BUF 0.5 m AISG TMA Auxiliary Materials Kit (Not include TMA), GU

TMA ATA212000

Triplex Tower Mounted Amplifier Module, DTMA 2100 - WCDMA NodeB Tx: 2110 ~ 2170MHz, Rx : 1920 ~ 1980 MHz, 12.2. 2,7/16 DIN Female, 9~30V(DC), AISG2.0

SBT KIT A00SMBT00 SBT with 0.5m AISG cable

Cable AISG ACOAISG02 Signal Cable, AISG Communication cable, 15M, D9M+D9(PS)(W), CC4P0, 5PB(S), RC85F(S)-1,

Aluminum Feeder LCF 78-50JL Aluminum Feeder, 7/8 100M Package Aluminum Feeder LCF 114-50JL Aluminum Feeder, 5/4 100M Package Aluminum Feeder LCF 158-50JL Aluminum Feeder, 13/8 100M Package

of 91

2.3 Antenna System Design Requirements

Antenna Gain Selection Rule: Dense Urban & Urban: 18dBi

Suburban & Rural: 19dBi

Special cases for Rural: 21dBi

Antenna Tilt Configuration Rule: Mechanical down tilt should be

of 91

2.4 Feeder and Jumper Requirements As per RFP, total cable loss (feeder+connector+jumper) should never exceed 3dB.

There should only be a single continuous feeder run from the base station to any given sector.

By default, it should use one jumper at the top of cabinet and one jumper at the antenna.

Ideally, all feeders and jumpers at any given site shall be of the same brand and jumper smust be pre-fabricated (not manmade jumper).

Feeder and jumper length shall meet the following criteria:

For feeder length

of 91

2.5 TMA Design Requirements In order to avoid link imbalance issue between downlink and uplink path, TMA should be applied in the following scenario:

Feeder length > 50M or

Total transmits power on top of cabinet per TRX (for GSM) / Cell (UMTS) more than 20W.

of 91

2.6 RET Solution for Macro BTS Note: RET solution should be applied to 2G and 3G antennas with electrical tilt.

RET Solution without DTMA

Configure by using SBT and 0.5m AISG cable connected to RCU (remote control unit).

For tower case, the number of 15m cascade AISG cable is determined by RCU (remote control unit) number.

For rooftop case, 1 SBT and 1 AISG cable is required for each sector.

Typical RET implementation for tower site

Feeder 1 (main)

Antenna

BTS

RCU

SBT

Feeder 2 (diversity)

Control cable

TX/RXA RXB

DC+control signals

3m Jumper

3m Jumper

of 91

RET Solution with DTMA

Configure by using DTMA and 2m AISG cable connected to RCU (remote control unit).

It is applicable for both tower and roof top site solution.


Antenna

RCU

DTMA

Feeder 1 (main)

BTS

Feeder 2 (diversity)

TX/RXA RXB

DC+control signals

NodeB0 NodeB1

1.5m Jumper

1.5m Jumper

3m Jumper

of 91

RET Solution for RRU:

Configure by using 0.5m AISG cable connected to remote control unit (RCU).

It is applicable for both tower and roof top site solution.


Antenna

RRU

RCU

SBT

BBU

TX/RXA RXB

3m Jumper

CPRI Cable less than 100m

of 91

3 Coverage Planning Guideline 3.1 Coverage Design Requirement

The nominal planning is calculated based on, as follows:

ID Clutter Type 2G Design Level 2G Acceptance Level 1 Dense Urban -64 dBm -69 dBm 2 Urban -68 dBm -73 dBm 3 Suburban -75 dBm -80 dBm 4 Rural -82 dBm -87 dBm ID Item 3G Design Level 3G Acceptance Level 1 Dense Urban -75 dBm -81 dBm 2 Urban -78 dBm -84 dBm 3 Suburban -82 dBm -88 dBm 4 Rural -89 dBm -95 dBm

Notes:

1. 95% of area shall meet design level during planing phase;

2. The acceptance level shall be measured based on outdoor level without in car loss.

of 91

3.2 Propagation Model The Standard Propagation Model (SPM) is used for the Coverage Planning. The Model Formula as well as Parameter explanation is listed as follows:

Path Loss=

Propagation Models parameter used are as below:

Note: The radio propagation model used shall have a mean error of

of 91

3.3 Digital Map Resolution Below table summarize digital map resolution being in use during coverage planning.

ID Region Clutter Digital Map Resolution 1 Dense Urban 5m 2 Urban 5m 3 Suburban 20m 4 Rural 20m 5 Dense Urban 20m 6 Urban 20m 7 Suburban 20m 8 Rural 20m 9 Dense Urban 20m 10 Urban 20m 11 Suburban 20m 12 Rural 20m 13 Dense Urban 20m 14 Urban 20m 15 Suburban 20m 16 Rural 20m 17 Urban 20m 18 Suburban 20m 19 Rural 20m 20 Urban 20m 21 Suburban 20m 22 Rural 20m

* For big city, 5m digital map resolution shall be applied.

of 91

3.4 GSM Link Budget Link Budget mainly target is to calculate maximum unlink/downlink pass loss.

Cell Coverage Radius is calculated based on SPM Propagation model.

GSM Link Budget Parameters

Mobile Mobile Rx Sensitivity -102dBm Mobile Tx Power 30dBm Mobile Antenna Gain 0dBi Mobile Antenna Height 1.5m

BTS BTS Antenna Diversity Gain 3.5dB Feeder, Connector & Jumper Loss 3dB

General Losses Body Loss (Voice only) 3dB Interference Margin 2dB Dense Urban Indoor Penetration Loss 20dB Urban Indoor Penetration Loss 18dB Suburban Indoor Penetration Loss 14dB

Rural Indoor Penetration Loss 10dB

Rural outdoor Penetration Loss 8dB Fading Margin 95% coverage probability 3dB

BTS Antenna Antenna Gain for DU& U 18dBi Antenna Gain for SU & RU 19dBi

of 91

GSM Link Budget

Dense urban Urban Suburb Rural

UL DL UL DL UL DL UL DL

Frequency Band(MHz) 1800 1800 1800 1800

Propagation Model SPM SPM SPM SPM

Environment Indoor Indoor Indoor Indoor

EIRP Calculation

Max power of TCH(dBm) a 30 43 30 43 30 43 30 43

Antenna gain Tx(dBi) b 0 18 0 18 0 19 0 19

Feeder Loss(dB) c 3 3 3 3 3 3 3 3

BTS Rx/Tx Diversity Gain(dB) d 0 0 0 0 0 0 0 0

EIRP(dBm) e=a+b-c+d 30 58 30 58 30 58 30 58

Slow Fading Margin

Slow fading margin(dB) f 9.9 8.4 6.8 4

Area coverage probability 95% 95% 95% 90% Slow fading Standard Deviation(dB) 14 12 10 6

Allowed Max Path Loss

Receiver Sensitivity(dBm) g -113 -102 -113 -102 -113 -102 -113 -102

Antenna Gain(dBi) h 18 0 18 0 19 0 19 0

Interference margin(dB) i 2 2 2 2

Fast Fading Margin(dB) j 3 3 3 3

Body Loss(dB) k 3 3 3 3

Penetration Loss(dB) l 20 18 14 10

Allowed Max Path Loss(dB) m=e-(g-

h+i+j+k+i) 124 122 127 126 135 133 141 140

Cell Radius

Antenna Height(m) n 1.5 25 1.5 30 1.5 40 1.5 45

Cell Radius(km) o 0.34 0.31 0.55 0.5 1.52 1.37 3.21 3

Cell Radius Output(km) =min(o1,o2) 0.31 0.5 1.37 3

of 91

3.5 UMTS Link Budget Link Budget mainly target is to calculate maximum unlink/downlink pass loss.

Cell Coverage Radius is calculated based on SPM Propagation model.

HSDPA and HSUPA cell edge throughput calculation for DU class A will be presented in this section as a reference.

UMTS Link Budget Parameters

Morphology Dense Urban Urban Suburban Rural

Link UL DL UL DL UL DL UL DL

Frequency(MHz) 1935 2125 1935 2125 1935 2125 1935 2125

Propagation Model SPM SPM SPM SPM SPM SPM SPM SPM

User Enviroment Indoor Indoor Indoor Indoor Indoor Indoor Indoor Indoor

TMA

Equipment UE BS UE BS UE BS UE BS

UE/NodeB Antenna Height(m) 1.5 25 1.5 30 1.5 40 1.5 45

Nodeb Feeder Loss(dB) 3 3 3 3 3 3 3 3

Cell Average Ioc/Ior 0.65 0.65 0.65 0.65 0.65 0.65 0.65 0.65

SHO Overhead 20% 20% 20% 20%

Softer HO Overhead 10% 10% 10% 10%

Area Coverage Probability 92% 92% 92% 92%

HSDPA Parameters

HSPA Max used Code Number for Single Carrier 10 10 10 10

HSDPA Power Allocation Ratio 65% 65% 65% 65%

Power Allocation Ratio Per HS-SCCH 5% 5% 5% 5%

HS-SCCH Number per Cell 1 1 1 1

of 91

UMTS Link budget

TCH Link Budget

Morphology Dense Urban Urban Suburb Rural

UL/DL UL DL UL DL UL DL UL DL

Project Parameters

Equipment UE_U6_

D8 BS 3

Sector UE_U6_

D8 BS 3

Sector UE_U6_

D8 BS 3

Sector UE_U6_

D8 BS 3

Sector

TMA

Sector Type 3 Sector 3 Sector 3 Sector 3 Sector

Diversity Mode 2 Rx

Diversity No

Diversity 2 Rx

Diversity No

Diversity 2 Rx

Diversity No

Diversity 2 Rx

Diversity No

Diversity

Link Parameters

User Environment Indoor Indoor Indoor Indoor

Cell Edge Channel Model TU3 TU50 RA120 RA120 Cell Edge Continuous Coverage Service

AMR 12.2 HSDPA

AMR 12.2 HSDPA

AMR 12.2 HSDPA

AMR 12.2 HSDPA

Cell Edge Service Rate(kbps) 12.20 384.00 12.20 384.00 12.20 384.00 12.20 384.00

SHO Supported TRUE FALSE TRUE FALSE TRUE FALSE TRUE FALSE

TX

Max. TCH TX Power (dBm) 21.00 41.00 21.00 41.00 21.00 41.00 21.00 41.00

Feeder Loss (dB) 0.00 3.00 0.00 3.00 0.00 3.00 0.00 3.00

Body Loss (dB) 3.00 0.00 3.00 0.00 3.00 0.00 3.00 0.00

Antenna Gain (dBi) 0.00 18.00 0.00 18.00 0.00 18.00 0.00 18.00

UL Power Back off (dB) 0.00 - 0.00 - 0.00 - 0.00 -

EIRP (dBm) 18.00 56.00 18.00 56.00 18.00 56.00 18.00 56.00

RX

Antenna Gain (dBi) 18.00 0.00 18.00 0.00 18.00 0.00 18.00 0.00

Feeder Loss (dB) 3.00 0.00 3.00 0.00 3.00 0.00 3.00 0.00

Body Loss (dB) 0.00 3.00 0.00 3.00 0.00 3.00 0.00 3.00 NodeB/UE Noise Figure (dB) 4.60 7.00 4.60 7.00 4.60 7.00 4.60 7.00

Required Eb/No(Ec/No) (dB) 4.27 -6.73 4.92 -5.92 3.83 -5.48 3.83 -5.48

Receiver Sensitivity (dBm) -124.26 -107.89 -123.62 -107.08 -124.71 -106.64 -124.71 -106.64

Target Load 50.00% 90.00% 50.00% 90.00% 50.00% 90.00% 50.00% 90.00%

Interference Margin (dB) 3.01 5.53 3.01 8.78 3.01 7.48 3.01 7.48 DL Max. TCH TX Power Required

FFM(dB) 1.11 0.00 0.00 0.00 0.00 0.00 0.00 0.00 Min. Received Signal Strength (dBm) -138.14 -99.36 -138.61 -95.30 -139.70 -96.16 -139.70 -96.16

Path Loss

Penetration Loss (dB) 20.00 16.00 12.00 8.00

Area Coverage Probability 95.00% 95.00% 95.00% 90.00% Slow Fading Standard Deviation (dB) 11.70 9.40 7.20 6.00

SFM(dB) 8.28 14.16 6.80 11.56 4.30 7.81 0.90 3.57

Path Loss (dB) 127.86 121.20 133.81 123.74 141.40 132.35 148.80 140.58

Cell Radius

of 91

UE Antenna Height (m) 1.50 1.50 1.50 1.50

NodeB Antenna Height (m) 25.00 30.00 40.00 45.00

Frequency (MHz) 1935 2125 1935 2140 1935 2125 1935 2125

Propagation Model SPM SPM SPM SPM

Cell Radius (km) 0.37 0.24 1.67 0.69 3.62 1.86 6.93 3.86

TCH Cell Radius (km) 0.24 0.69 1.86 3.86

Pilot RSCP And EcIo Dimensioning For Simulation Pilot Channel TX Power (dBm) 33.00 33.00 33.00 33.00

Outdoor RSCP (dBm) -90.36 -90.30 -95.16 -99.16

Pilot Channel Ec/Io (dB) -14.00 -14.00 -14.03 -14.09

of 91

HSDPA Cell Edge Throughput Calculation (Class A) HSDPA Cell Edge Throughput

Path Loss

Morphology Dense Urban

Frequency (MHz) 2125

Channel Model TU3

Propagation Model SPM

UE Antenna Height (m) 1.50

NodeB Antenna Height (m) 25.00

Cell Coverage Radius (km) 0.40

Path Loss (dB) 128.91

Max Couple Loss (dB)

User Environment Indoor

NodeB Antenna Gain (dBi) 18.00

NodeB Feeder Loss (dB) 3.00

UE Antenna Gain (dBi) 0.00

UE Feeder Loss (dB) 0.00

Penetration Loss (dB) 20.00

Area Coverage Probability 95.00%

Slow Fading Standard Deviation (dB) 11.70

Path Loss Slope 3.59

HHO Gain (dB) 1.50

SFM With HHO (dB) 12.66

Max Couple Loss (dB) 146.57

Cell Edge EcNo

HSDPA UE Type CAT6

HSDPA Receiver Type Type3

HSDPA Technology

NodeB Max Power (dBm) 43.00

Power Allocation Ratio Per HS-SCCH 5.00%

HS-SCCH Number Per Cell 1

HSDPA Power Allocation Ratio 70.00%

DL Total Load 90.00%

of 91

DL Cell Edge Ioc/Ior 1.78

UE Noise Figure (dB) 7.00

HSDPA Max Avaiable Code Number 10

Ec/Ior (dB) -1.41

Ior/Ioc (dB) -5.70

HSDPA Cell Edge Ec/No (dB) -4.47

Cell Edge Throughput (kbps)

Max Rate UE Support (kbps) 3463.81

HSDPA Max Code Rate (kbps) 9118.10 HSDPA Cell Edge Throughput (kbps) 635.81

of 91

HSUPA Cell Edge Throughput Calculation (Class A)

HSUPA Cell Edge Throughput

Path Loss

Morphology Dense Urban

Frequency (MHz) 1935

Channel Model TU3

Propagation Model SPM

UE Antenna Height (m) 1.50

NodeB Antenna Height (m) 25.00

Cell Coverage Radius (km) 0.40

NodeB RX Diversity 2 Rx Diversity

Path Loss (dB) 128.91

Max Throughput of UE

HSUPA UE Type CAT6

UE TTI (ms) 10

HSUPA SBLER 30.00%

Max RLC Throughput of UE(kbps) 1331.62

Receiver Sensitivity

HSUPA SHO Supported TRUE

User Environment Indoor

Penetration Loss (dB) 20.00

UE Max Power (dBm) 24.00

UE Antenna Gain (dBi) 0.00

UE Feeder Loss (dB) 0.00

HSUPA Power Backoff (dB) 1.50

NodeB Antenna Gain (dBi) 18.00

UL Target Load 50.00%

FFM(dB) 0.20

HHO Gain (dB) 1.50

Interference Margin (dB) 3.01

Area Coverage Probability 95.00%

Slow Fading Standard Deviation (dB) 11.70

of 91

Path Loss Slope 3.59

SFM (dB) 8.28

Receiver Sensitivity (dBm) -119.90

Cell Edge Throughput (kbps)

TMA

NodeB Feeder Loss (dB) 3.00

NodeB Antenna Top Noise Figure (dB) 4.60

HSUPA Cell Edge Ec/No (dB) -16.34

UL Cell Average IocIor 0.65

HSUPA Ec/No Limitation based on Target Load (dB) -3.62

Actual Available Cell Edge Ec/No (dB) -16.24

CCPIC Corrected Cell Edge Ec/No -16.24

HSUPA Cell Edge Throughput Based on Ec/No (kbps) 51.32

HSUPA Cell Edge Throughput (kbps) 51.32

of 91

3.6 Planning Tool As a reference, Asset 3G simulation tool will be used to validate nominal planning instead of U-NET.

of 91

4 Capacity Planning Guideline 4.1 GSM Output Power Setting

No.TRX in one MRFU Static TRX Power(W) Static TRX Power(dBm) TOC Power

1 60 47.78 TRX power- power level






Notes:

The maximum active TRX per MRFU is set to 4 in accordance with the RFP requirement (TOC power= 20 W/TRX).

Default of power level is set to 0

In some special cases to activate 3 TRX per MRFU as follow:

a. The TOC power still less than Ericsson after power mapping in Jabo Swap project

b. Whenever antenna type change and lead to gain reduction.

of 91

2. Macro BTS3012/3900 Solution with GRFU V1:

TOC power = TRX power- power level (the default value of power level=0)

No.TRX per Sector Static TRX Power(W) Static TRX Power(dBm) TOC Power







Notes:

The maximum active TRX per MRFU is set to 4 in accordance with the RFP requirement (TOC power= 20 W/TRX).


In some special cases to activate 3 TRX per MRFU as follow:

c. The TOC power still less than Ericsson after power mapping in Jabo Swap project

d. Whenever antenna type change and lead to gain reduction.

3. Macro BTS3012 Solution with DRFU:

TOC power = TRX power- power level (the default value of power level=0)

TRX/Sector 2 Ports Antenna DRFU TRX Power TOC Power

1~2 1 Uncombined 40W TRX power- power level

3~4 1 Combine 18W TRX power- power level

Notes:


4. Macro BTS Solution with DTRU:

TRX/Sector 2 Ports Antenna DTRU TRX Power TOC Power

1~2 1 Uncombined + DDPU 40W TRX power- power level-1

3~4 1 Combine + DDPU 18W TRX power- power level-4.5

Notes:


of 91

5. DBS3900 Solution with MRRU V1

Single MRRU per Sector with Single Transmit (not applicable for current project):






5 7.5 38.75 TRX power- power level


Single MRRU per Sector with Dual Transmit:








Notes:

Default Solution with Macro BTS:

A maximum of 4 TRX /MRFU is applied in GSM network.

In case of configuration 5 ~ 8 TRXs per sector, 2 MRFU module + 1pcs 2 port antenna per sector is applied.

Default Solution with DBS:

A maximum of 4 TRX/MRRU with dual transmitter is applied in GSM network.

In case of configuration 5 ~ 8 TRXs per sector, 2 MRRU module + 2pcs 2 port antenna or 1pcs 4 port antenna per sector is applied.

of 91

4.2 GSM Time Slot/TRX Design Principle 1. General Requirement

SDCCH GOS0.5%

TCH GOS1%

TCH utilization80%

Half rate 50% (AMR Half Rate45%)

Blocked CS: To be considered during capacity demand calculation as correctional element

2. Channel Configuration

Once PDCH configuration is depends on the TCH channel, 4static PDCH and 60% Maximum Rate Threshold of PDCHs in a Cell configuration are recommended.

Static PDCH shall be configured in same TRX.

Following table describes the minimum configuration.

TRX Fixed SDCCH Static PDCH

1 1 1

2 1 3

3 2 4

4 2 4

5 3 4

6 3 4

Notes:

The above SDCCH configuration is applicable for all BTS (including swap sites). Any additional SDCCH should be dynamic.

The condition of adding static or dynamic SDCCH must consider TCH capacity.

3. Default TRX configuration must follow rules below:

Hardware for all expansion BTS must support up to S444;

Software license for TRX configuration for in-filled BTS is S444;

Software license for TRX configuration for new coverage sites is S222;

of 91

4.3 GSM Frequency Planning (SFH)

Note:

1. BCCH use 8*3 frequency re-use both for Macro & IBS

2. TCH use 1*3 SFH

3. Maximum configuration will support to S6/6/6, TCH fractional load should not exceed 36%.

(Fractional load factor =ARFCN

TRX

NN

)

4. If S6/6/6 cannot fulfill the capacity, split cell is required.

5. If IBS & Macro is collocated, choose BCCH range frequency for IBS TCH and use Base band hopping instead of SFH.

6. SFH implementation might be considered in area after network modernization finished.

of 91

4.4 Abis Dimensioning Guideline Abis Configuration

2G Average Abis Bandwidth Requirement 2011 Abis totalKbps) 2012 Abis totalKbps) 2013 Abis totalKbps) S222 1025 S222 1087 S222 1280 S444 2204 S444 2337 S444 2337

2G Peak Abis Bandwidth Requirement

2011 Abis Peak totalKbps)

S222 2416.64

S444 5017

Abis Dimensioning

Abis interface support TDM and IP. The Abis transmission bandwidth can be calculated if the cell configurations are fixed.

Abis interface transmission bandwidth calculation procedure is as the following figure:

Abis Interface Transmission Calculation Procedure

Abis interface bandwidth calculation sample

(1) Bandwidth based on TDM (Fixed Abis)

Formula:

Roundup ((P+R*4+4+I)/124)

P TCH+PDCH number per site

R Ts for RSL (64K)

I Idle Ts required for PS

TRX Number per

Cell

HR Ratio

PDCH Number per

Cell

Calculation Based on

TDM / IP?

Abis Interface Transmission Bandwidth

Based on TDM / IP

Input Output

of 91

Output Sample

Related Performance Counter

ABIS Resource Capability Measurement R9101 Number of Application Attempts of Abis Timeslot R9102 Number of Successful Application Attempts of Abis Timeslot R9103 Number of Release Requests of Abis Timeslot R9104 Number of Successful Releases of Abis Timeslot R9105 Number of Application Attempts of IP PATH or HDLC Bandwidth (16K) R9106 Number of Successful Application Attempts of IP PATH or HDLC Bandwidth (16K) R9107 Number of Release Requests of IP PATH or HDLC Bandwidth (16K) R9108 Number of Successful Releases of IP PATH or HDLC Bandwidth (16K) R9109 Number of Unsuccessful Application Attempts of Abis Timeslot Because of no Idle Timeslot R9110 Number of Unsuccessful Application Attempts of Abis Timeslot for Connecting Network Failure R9111 Number of Unsuccessful Application Attempts of Abis Timeslot for Sending Network Configuration

to BTS Failure R9112 Number of Unsuccessful Application Attempts of Abis Timeslot for Other Cause R9115 Number of Unsuccessful Application Attempts of Abis Timeslot for the limit of BTS DSP

ABIS Resource Capability Measurement L1151A Mean number of occupied timeslots on the Abis interface L1121A Abis Timeslot Fault Times of the Site

(2) Bandwidth based on IP (IP over E1)

Formula:

(Bandwidth on control plane/0.2+ Bandwidth on user plane)/ Transmission load factor

Output Sample:

of 91

4.5 UMTS Channel Power Setting Common Channel Power setting is as below:

Parameter ID Parameter Meaning Default Value Level MaxTxPower Maximum cell transmit

power 430, that is, 43 dBm Cell

PCPICHPower PCPICH transmit power 330, that is, 33 dBm

PSCHPower Transmit power of PSCH and SSCH

-50, that is, -5 dB

SSCHPower

BCHPower BCH transmit power -20, that is, -2 dB

MaxFachPower Maximum FACH transmit power

10, that is, 1 dB FACH

PCHPower PCH transmit power 20, that is, 2 dB Cell

PICHPowerOffset PICH transmit power -3 dB

AICHPowerOffset AICH transmit power -6 dB

Dedicate Channel power setting is as below:

Service Type Max. Downlink Transmission Power (in the parentheses is the dB value)

Min. Downlink Transmission Power (in the parentheses is the dB value)

CS Service

12.2K AMR 0(0) -150(-15)

64K transparent

data

30(3) -120(-12)

PS Service

384K 40(4) -110(-11)

256K 40(4) -130(-13)

144K 20(2) -150(-15)

128K 20(2) -150(-15)

64K 20(2) -150(-15)

32K 0(0) -190(-19)

16K -20(-2) -210(-21)

8K -40(-4) -230(-23)

Notes:

Only in suburban and rural areas, PCPICH power can be increase to 12~15% of cell total power, and should be applied case by case, since PCPICH power increase will impact to downlink cell capacity.

Cell downlink loading maximum: 75% for R99 only, 90% for R99+HSDPA

Cell uplink loading maximum: 50% for R99 only, 75% for R99 + HSUPA

of 91

4.6 CE Dimensioning Guideline CE Board type

For BTS 3900/3900A and DBS 3900

Board Number of Cells Number of UL CEs Number of DL CEs Baseband Transfer Capacity

WBBPa 3 128 256 N/A

WBBPb1 3 64 64 Twelve 1T2R cells




WBBPd1 6 192 192 Twenty-four 1T2R cells



For BTS 3812/3812E/3812AE

Board Number of Cells Number of UL CEs Number of DL CEs

EBBI 6 384 384

EULP 6 384 0

EDLP 6 0 384

HULP 6 128 0

HDLP 6 0 512

HBBI 6 128 256

CE Configuration

Despite of CE dimensioning result, the default CE configuration per NodeB is applied to all clutter type: Hardware board capacity: UL 384 / DL 384 (Wbbp4 for BTS3900 series) Software License: UL 192 / DL 192 (Initial stage)

of 91

CE dimensioning flow chart:

CE dimensioning for R99

Service CE Consume (UL/DL)

AMR 12.2K 1/1

64Kbps 3/2

128Kbps 5/4

384Kbps 10/8

HSDPA 0

Common Channel 0

CE dimensioning principles have the following general features:

CE license is pooled in one NodeB

No need extra CE resource for CCH

No need extra CE resource for TX diversity

No need extra CE resource for compressed mode

No need extra CE resource for softer handover (V2 NodeB)

1 2 3 1 2 3

of 91

CE resource for R99 and HSDPA services are designed separately and have no impact on each other

No need extra CE resource for HSDPA service traffic channel if SRB over HSDPA is adopted.

, CE configuration is designed in following fomular:

AveragePSAverageCStotal CECECE __

iCEFactor1i ierNodeBCSTrafficPAverageCSCE Overhead) SH(_

iontransmissireibursti

iAveragePS CEFactorRRerNodeBPSTrafficpCE )1)1Overhead) SH1( __ Where:

Soft handover factor= 20%

Burst Ratio= 25%

Re-transmission ratio for R99= 5%

Re-transmission ratio for HSPA=10%

For practice CE configuration, use 64CE as a step

R99 CS CE Dimensioning Sample:

1. Assumptions Subscriber number per NodeB: 2000 Voice traffic per subscriber: 0.02Erl CS over HSPA traffic per subscriber: 0.001Erl Soft Handover Overhead: 20% GoS requirement of voice: 2% GoS requirement of VP: 2%

2. Calculation 1 Peak CE Dimension

Traffic of voice: 0.02*2000*(1+20%) = 48 Erl Traffic of CS over HSPA: 0.001*2000*(1+20%) = 2.4 Erl Voice peak CE demand are 59 CEs in uplink and 59 CEs in downlink respectively. CS over HSPA peak CE demands are 14CEs ((1+1)*7=14) in uplink and 7(1*7=7) CEs in downlink respectively. Considering the CE resource share between voice and CS over HSPA services, by multidimensional ErlangB algorithm, the final total peak CEs demand are 68 CEs in uplink and 61 CEs in downlink.

2 Average CE Dimension

Voice average CE demands are 2000*0.02*(1+20%)*1=48 CEs in uplink and 48 CEs in downlink respectively. CS over HSPA average CE demands are 2000*0.001*(1+20%)*(1+1) = 5 CEs in uplink and 2000*0.001*(1+20%)*1= 3 CEs in downlink respectively. The final total average CEs demand are 48+5=53 CEs in uplink and 48+3=51 CEs in downlink respectively.

3 Final CE Dimension

Since the peak values are bigger than the average ones, so the final CE consumption is 68 in uplink and 61 in downlink.

R99 PS CE Dimensioning Sample:

Assumption:

of 91

Subscriber number per NodeB: 2000 UL PS64k throughput per user: 50kbit

DL PS64k throughput per user: 100kbit DL PS128k throughput per user: 80kbit

Soft Handover Overhead: 20% PS traffic burst: 20%

Retransmission rate of R99 PS services: 5%

Channel element utilization rate: 0.7

Then,

CE for UL PS64k: 5%)(1*20%)(1*20%)(1*3*3600*0.7*6450*2000

3 CEs

CE for DL PS64k: 5%)(1*20%)(1*20%)(1*2*3600*0.7*64

100*20004 CEs

CE for DL PS128k: 5%)(1*20%)(1*20%)(1*4*3600*0.7*12880*2000

3 CEs

Total CE for UL PS services is ULPSCE _ = 3 CEs And total CE for DL PS services is DLPSCE _ =4+3= 7 CEs

of 91

CE Dimensioning for HSPA

1. HSDPA Uplink CE dimensioning ( ULHSDPACE _ )

On the uplink, uplink A-DCH (associated DCH) can be used for signalling and transmission of HSDPA uplink traffic. A-DCH has variable SF of 4, 8 and 16 and its corresponding data transmission rate is 384kbps, 128k and 64k, respectively.

Number of uplink CEs for HSDPA ( ULHSDPACE _ ) can be calculated according to number of simultaneously connected HSDPA users ( LinksHSDPAN _ ) and CE factors. Table 2-3 shows the UL

A-DCH needed for specified HSDPA bearers and related CE consumption per link.

HSDPA A-DCH links could be calculated by the following formulas

LinksHSDPAN _ = ata___

DHSDPAAvg

HSDPATr

RateThroughput

(1.)

Where,

LinksHSDPAN _ is the online HSDPA links number

HSDPATrThroughput _ is the total traffic of HSDPA services

DataHSDPAAvgRate __ is the online average HSDPA services throughput per user Thus the final CE consumption of the A-DCH links of HSDPA services could be calculated by

the following formulas:

ULHSDPACE _ = LinksHSDPAN _ * i (2.)

Where i is the CE map in Table 3-3.

UL A-DCH bear rate and CE factor of HSDPA services mapping

HSDPA AveRate (kbps)

UL A-DCH BearRate

UL A-DCH CE (over DCH)

UL A-DCH CE (over HSUPA)

128 16 1 1.00 384 32 1.5 1.00

3600 64 3 1.85 7200 128 5 3.17 14400 384 10 5.59

of 91

2. HSDPA Downlink CE dimensioning ( DLHSDPACE _ )

The SF of A-DCH is 256 on downlink, with the rate of 3.4 kbps. When an HSDPA subscriber accesses the network, a downlink A-DCH is set up, which will consume CE. A-DCH in downlink will consume one CE per link.

If SRB over HSDPA feature is activated, then no CE will be consumed by HSDPA service in downlink. There is dedicated H/W in Node B to support HSDPA service processing, so HSDPA traffic does not consume any CE.

The HSDPA links in the downlink can be calculated by formulas below:

Assumption: Subscriber number per NodeB: 2000 Traffic model of HSDPA: 3600kbit Requirement of average data throughput per user: 400Kbps Requirement of average online throughput per user: 50Kbps

HSDPA traffic burst: 0

HSDPA retransmission rate: 10%

SRB over HSDPA feature is off, A-DCH of HSDPA bears on R99 PS.

Soft handover ratio of R99/HSUPA services is 20%.

No MIMO or DC-HSDPA is involved. Then,

CE in downlink:

1*%)101(*%)01(*50*3600

3600*20001*_ HSDPADLHSDPA LinksCE = 44 CEs CE in uplink:

DCHACEFactor =1.5 CE (400Kbps HSDPA throughput mapping to 32Kbps A-DCH, which consumes 1.5 CE in R99 PS)

)(*_ HSDPAAOnlineHSDPDCHAHSDPAAULHSDPA LinksLinksCEFactorLinksCE =

%)201(*%)101(*%)01(*}1*)400*36003600*2000

50*36003600*2000(5.1*

400*36003600*2000{

= 56 CE

of 91

3. CE Dimensioning for HSUPA

The following table shows the CE factors consumed by HSUPA service

CE Mapping for HSUPA Services

MinSF HSUPA Rate(kbps) RAN 12.0

10ms TTI 2ms TTI

SF32 32 1

SF16 64 2

SF8 128 4

SF4 672 640 8 2*SF4 1399 1280 16 2*SF2 2886 2720 32

2*SF2+2*SF4 5742 5440 48

* Notes: 10ms TTI is supported by HSUPA phase 1, while 2ms TTI is supported by HSUPA

phase 2.

1) CE consumed by HSUPA traffic

CE numbers consumed by HSUPA traffic channel depends on the simultaneous connected links number. (3.)

Where:

)1(*

)Re1(*)1(*)(

)(

Burstratio

ontransmissiSHOfactorkbitUseroughputPerAverageThr

kbitPerNodeBThroughputLinks

HSUPA

HSUPAHSUPA

(4.) Considering the impact on CE consumption of soft handover overhead, HSUPA traffic burst and retransmission caused by error transmission, more CEs are needed by HSUPA traffic channel.

HSUPACEFactor is the CE mapping in Table 3-4. 2) CE consumed by A-DCH of HSUPA CE consumed by A-DCH of HSUPA depends on the number of A-DCH. One A-DCH is needed for one HSUPA service link. (1)In Uplink ( AULHSUPACE _ )

The same to HSDPA, when an HSDPA subscriber accesses the network, a uplink A-DCH is set up, which will possibly consume CE. If SRB over HSUPA feature is activated, then no CE will be consumed, otherwise this A-DCH in uplink will consume one CE per link, calculated by the following formulas:

AULHSUPACE _ = HSUPALinks *1 (5.)

HSUPALinks is simultaneous connected HSUPA link, can be calculated by formulas (6).

HSUPAHSUPATrafficHSUPA CEFactorLinksCE *_

of 91

(2)In Downlink ( ADLHSUPACE _ ) If HSUPA shares the same carrier with HSDPA, A-DCH of HSUPA can be loaded on HSDPA, thus no extra CE is needed for A-DCH of HSUPA in downlink. Assumption:

Subscriber number per NodeB: 2000

Traffic model of HSUPA: 500kbit

Requirement of average throughput per user: 128kbps

Requirement of average online throughput per user: 20Kbps

Soft Handover Overhead: 20%

Burst ratio of HSUPA is 0%, re-transmission rate is 11%.

SRB over HSUPA feature is off.

SRB over HSDPA feature is adopted.

RAN version: RAN11.0, 2ms TTI is adopted.

Then,

1. CEs in downlink

HSUPA is borne on HSDPA, No CE consumed.

2. CEs in uplink

CE for SRB

1*%)111(*%)201(*3600*20

500*2000HSUPALinks = 19 CE

CE for traffic

MAC-e throughput for 128Kbps is 151Kbps, which consumes 4.1 CE

ULTrafficCE _ = %)111(*%)201(*}1*)3600*128500*2000

3600*20500*2000(1.4*

3600*128500*2000{ 28 CE

Total CE in uplink

19+28 = 47 CE

of 91

CE Dimensioning for Mixed services

PS services including HSPA packet services adopts the access strategies called Best Effort, which means PS services could only occupy the remaining CE resource after all the CS services are satisfied. The real-time CE resources assignment between CS and PS within NodeB is clearly demonstrated in 1.1.1.1 1.1)a.Figure 1.

Figure 1 CE Shared between PS and CS Services

When HSUPA and HSDPA co-exist in the network, the uplink and downlink A-DCH can be shared between HSUPA and HSDPA.

),( ___ AULHSDPAAULHSUPAULA CECEMaxCE ),( ___ ADLHSDPAADLHSUPADLA CECEMaxCE

AULHSUPACE _ : CE consumed by uplink A-DCH of HSUPA;

AULHSDPACE _ : CE consumed by uplink A-DCH of HSDPA;

ADLHSUPACE _ : CE consumed by downlink A-DCH of HSUPA;

ADLHSDPACE _ : CE consumed by downlink A-DCH of HSDPA;

Therefore, according to the previous presentation, the total CE dimension in uplink and downlink can be summarized respectively as the following formulas:

),( _______ HSUPAULAULPSULAverageCSULPeakCSTotalUL CECECECECEMaxCE ),( _______ DLADLPSDLAverageCSDLPeakCSTotalDL CECECECEMaxCE

of 91

4.7 Iub Dimensioning Guideline Iub Configuration

3G Average Iub Bandwidth Requirements

Iub (kbps) 2011 2012 2013

UL DL UL DL UL DL DU 1,175 2,078 2,483 6,284 3,918 10,926 U 821 1,475 2,060 5,119 3,918 10,926 SU 821 1,475 1,485 3,756 2,582 7,239 RU 821 1,475 1,485 3,756 2,582 7,239 3G Peak Iub Bandwidth Requirements

Iub (kbps) 2011 2012 2013 DL 7.2Mbps 14.4Mbps 21Mbps

Notes: For singleRAN implementation, dedicated transmission port shall be assigned to Iub and

Abis interface either TDM or IP based (no co-transmission between Iub and Abis).

Iub Dimensioning

For the multi-services in UMTS, has carried out in-depth research in the field of multi-service network dimensioning and adopts multidimensional ErlangB model to estimate the Iub bandwidth of CS, CS/VoIP over HSPA multi-services. Apart from services bandwidth, Iub bandwidth dimensioning includes calculation of Iub bandwidth occupied by MBMS, common channels and O&M. Shows the Iub dimensioning procedure.

of 91

For mixed CS, CS/VoIP over HSPA, PS and HSPA services Iub bandwidth dimensioning, best effort characteristic of PS and HSPA is used. In other words, the spare part of Iub bandwidth which is not used by CS services can be utilized by PS and HSPA services. Error! Reference source not found. illustrates sharing of Iub bandwidth by CS, CS/VoIP over HSPA, PS and HSPA.

Therefore, the total Iub bandwidth can be obtained through the following formula:

MOCCHMBMSRateExperienceusedEndHSPA

HSPAAvgPAVoIPoverHSCSCSAvgPSPeakPAVoIPoverHSCSCSTotal

IubIubIubIubIubIubIubIubMaxMaxIub

&___

_/,__/,

]

)]),(,[[(

The ultimate Iub configuration is decided by the larger one of uplink and downlink Iub bandwidth.

CS Traffic Voice Traffic VP Traffic CS/VoIP over HSPA Traffic

GoS Requirements

Subscribers Subs per NodeB

PS Traffic PS64 Throughput PS128 Throughput PS384 Throughput PS Retransmission

HSPA Traffic

Erlang Services Iub Peak Bandwidth

PS Iub Bandwidth

Service Iub Bandwidth

HSPA Iub Bandwidth

Common Channel Bandwidth

O&M Bandwidth

Iub Bandwidth

Input Iub Dimensioning Output

HSPA End-user Experience Rate Bandwidth

Erlang Services Iub Average Bandwidth

max

max

of 91

Based on the protocol structure, the Iub bandwidth/overhead for R99, CS/VoIP over HSPA and HSPA service could be calculated and the results are given in Table1.

Table1 R99, CS/VoIP over HSPA service Iub bandwidth

Notes:

The Iub bandwidth per link in above table already considered:

1) The activity factor of AMR12.2k and CS/VoIP over HSPA is 0.65, and that of the other

services is 1;

2) The Iub bandwidth occupied by SRB (3.4kbps) is included and the SRB activity factor is 0.1;

3) The Duty Ratio of CS/VoIP over HSPA is 0.1.

Table2 HSPA service Iub Overhead

Notes:

1) Terminal Type 1: supports HSDPA( lower than 14.4Mbps) and phase 1 / phase 2

HSUPA( 1.96Mbps or 5.76Mbps);

2) Terminal Type 2: supports 64QAM or MIMO or 64QAM+MIMO or DC-HSDPA in downlink, and

16QAM in uplink.

Table3 MBMS/O&M/CCH Iub bandwidth

of 91

1. CS and CS/voIP over HSPA services peak Iub bandwidth

CS and CS/voIP over HSPA services peak Iub bandwidth is calculated by multidimensional ErlangB algorithm in. Multidimensional ErlangB can estimate the respective blocking probability of various CS and CS/voIP over HSPA services. Under a fixed Iub bandwidth, different services have different blocking probabilities, which depend on their Iub bandwidth usages. Multidimensional ErlangB model is illustrated in Figure 2.

Figure 2 Multidimensional ErlangB model

The resource is shared by all services in multidimensional ErlangB model, which takes good advantage of the fact that the probability of simultaneous bursts from many independent traffic sources is very small. The following figure illustrates the gain when the resource is shared compared to when the resource is partitioned.

Figure 3 Partitioning Resources vs. Resources Shared

Once we know the GoS requirement of CS and CS/voIP over HSPA services, the CS and CS/voIP over HSPA traffic per NodeB (after considering soft handover ratio) and the service Iub bandwidth, we can calculate the CS and CS/voIP over HSPA services peak Iub bandwidth using multidimensional ErlangBMDEmodel. This idea is shown in Figure 4. Note:

Iub factors means Iub bearer bandwidth including FP, AAL2 and ATM or IP overhead for

service i.

of 91

Figure 4 Estimate peak Iub bandwidth using multidimensional ErlangB model

2. CS and CS/voIP over HSPA services Average Iub bandwidth

Of course, the average Iub bandwidth for CS and CS/voIP over HSPA services can also be obtained, which does not guarantee the GoS requirements. The formula below is used to calculate CS and CS/voIP over HSPA services average bandwidth:

_*)1(*i

iIubSHOigeHSPA_AveravoIP over CS and CS/ RRNodeBTrafficPerIub

SHOR : Soft handover overhead which does not include softer handover;

iIubR _ : Iub bandwidths for CS and CS/voIP over HSPA service I, shown in Figure 1Table1.

3. PS Iub bandwidth

The calculation for PS Iub bandwidth is almost the same as that for CS and CS/voIP over HSPA services average Iub bandwidth except that PS traffic calculation should also consider the PS characteristics, e.g. PS burstiness, retransmission. The formula below is used to calculate PS Iub bandwidth:

i

iIubtransBurstSHOiAveragePS RRRRNodeBTrafficPerIub _Re_ *)1(*)1(*)1(*

transRRe : Retransmission factor of PS services, which is equal to BLER/(1-BLER);

BurstR : Burst ratio of PS services and this parameter reflects the Qos requirement of PS services.

4. HSUPA Iub bandwidth

HSUPA usually bears Best Effort (BE) services; the calculation procedure of Iub bandwidth for HSUPA is almost same as that for PS. HSUPA Iub bandwidth is calculated by the below formula:

GoS Requirements

Traffic & Service Iub Bandwidth

Peak Iub Bandwidth

MDE

of 91

)1(*)1(*)1(*)1(* _Re overheadIubtransBurstSHOHSUPA RRRRNodeBTrafficPerIub

overheadIubR _ : HSUPA service Iub Overhead, shown in Figure 1Table2.

5. HSDPA Iub bandwidth

Iub bandwidth for average traffic model The calculation procedure of Iub bandwidth for HSDPA is almost same as that for HSUPA. However, it should be noted that HSDPA does not support SHO and therefore there is no Iub SHO overhead for HSDPA. HSDPA Iub bandwidth is calculated by the below formula:

)1(*)1(*)1(* _Re overheadIubtransBurstHSDPA RRRNodeBTrafficPerIub

overheadIubR _ : HSDPA service Iub Overhead, shown in Figure 1Table2.

Iub bandwidth for HSPA End-user Experience Rate Bandwidth requirement If HSPA End-user Experience Rate Bandwidth such as 3.6Mbps and 7.2Mbps is given, the Iub bandwidth needed by peak rate can be calculated by the following formula:

)1(*)1(* _Re_ overheadIubtransPeakHSDPA RRrNodeBPeakRatePeIub

It should be noted that the PeakRatePerNodeB is the application layer rate and the relationship between application layer rate and physical layer rate is given in the following table:

Table4 Physical layer rate & application layer rate

Physical Layer Rate

Application Layer Rate

3.6Mbps 3.2Mbps 7.2Mbps 6.4Mbps 14.4Mbps 12.7Mbps

Notes:

Since peak rate is used for Iub calculation, there is no need to consider additional burst ratio;

6. Iub bandwidth for CCH and O&M

Iub bandwidth for common control channels (CCH) Iub bandwidth for common channel mainly includes FACH and PCH for downlink while RACH for uplink for one cell. The Iub bandwidth for downlink CCH depends on the configurations of FACH and PCH. FACH and PCH are mapped onto the same physical channel S-CCPCH. Generally, the typical configuration of RACH and S-CCPCH are both one for each cell. Herein, common Channels also includes NBAP, ALCAP consuming Iub bandwidth (For IP transport, there is no ALCAP signaling). As the services speed gets bigger, the ratio of Iub bandwidth consumed by NBAP, ALCAP gets so lower as to be ignored. Iub bandwidth for O&M O&M Iub bandwidth is configurable and the typical recommended value is 64kbps for both uplink and downlink for one NodeB.

This chapter gives a case study for ATM over E1/T1 and IP over E1/T1 Iub bandwidth calculations. Since the uplink and downlink Iub bandwidth calculation procedures are the same, only downlink Iub bandwidth calculations are shown.

Input for Iub bandwidth dimensioning The Iub bandwidth calculation is exemplified with a case study using the following traffic model given in Table5 and the peak rate requirement of HSDPA is 7.2Mbps.

Table5 Traffic Model

Traffic Model (Single User @ Busy Hour)

of 91

Bearers Uplink Downlink GoS AMR12.2k (mErl) 20 20 2%

CS64k mErl) 2 2 2% PS64k (Kbits) 125 100 N/A

PS128k (Kbits) 0 200 N/A PS384k (Kbits) 0 200 N/A HSPA (Kbits) 200 2000 N/A

Assuming that each NodeB (S111) supports 2000 subscribers and the soft handover overhead is 20%. The ratio of Iub data retransmission for R99 service, HSDPA and HSUPA is 1%. The burst ratio of PS and HSPA traffic is 20%.In addition, the voice activity factor of AMR12.2k is 0.5. CS peak Iub bandwidth

CS peak Iub bandwidth for ATM over E1/T1 CS peak Iub bandwidth calculation is exemplified with a case study using the following traffic model: Different service bearer needs different Iub bandwidth, the table below shows detailed Iub bandwidth for several typical service bearers: For UL direction: Voice traffic: ErlNodeBuseruserErl 48%201/2000/02.0 Video call traffic: ErlNodeBuseruserErl 8.4%201/2000/002.0 The peak Iub bandwidth needed by voice service is: kbpskbpsErlangB 5835.02002.0,48 The peak Iub bandwidth needed by video call is:

kbpskbpsErlangB 7708002.0,8.4 Using MDE, the CS peak Iub bandwidth for voice and video call is

kbpsIub PeakCS 1313_ CS peak Iub bandwidth for IP over E1/T1

For DL direction: Voice traffic: ErlNodeBuseruserErl 48%201/2000/02.0 Video call traffic: ErlNodeBuseruserErl 8.4%201/2000/002.0 The peak Iub bandwidth needed by voice service is:

kbpskbpsErlangB 4955.01702.0,48 The peak Iub bandwidth needed by video call is:

kbpskbpsErlangB 6837102.0,8.4 Using MDE, the CS peak Iub bandwidth for voice and video call is

kbpsIub PeakCS 1063_ CS Average Iub bandwidth

ATM over E1/T1 For ATM over E1/T1, the average Iub bandwidth for CS services can be calculated as: Average Iub needed by voice: kbpskbpsNodeBErl 4805.020/48

Average Iub needed by Video Call: kbpskbpsNodeBErl 38480/8.4 Average Iub needed by voice and video call is:

kbpskbpskbpsAverageCSIub 864384480_

IP over E1/T1 For IP over E1/T1, the average Iub bandwidth for CS services can be calculated as: Average Iub needed by voice: kbpskbpsNodeBErl 4085.017/48

Average Iub needed by Video Call: kbpskbpsNodeBErl 34171/8.4 Average Iub needed by voice and video call is:

of 91

kbpskbpskbpsIub AverageCS 749341408_

R99 PS Iub bandwidth ATM over E1/T1

Assuming the ratio of traffic business is 20%, the ratio of data retransmission for R99 is 1% and the soft handover ratio is 20%, DL R99 PS Iub bandwidth for each NodeB is:

kbps

Iub AveragePS

520

492%11%201%20136003842002000

165%11%201%2013600128

200200083%11%201%201360064

1002000_

IP over E1/T1 For IP over E1/T1, the DL R99 PS Iub bandwidth for each NodeB is:

kbps

Iub AveragePS

447

418%11%201%20136003842002000

141%11%201%2013600128

200200074%11%201%201360064

1002000_

HSDPA Iub bandwidth

ATM over E1/T1 Assuming the ratio of traffic business is 20% and the ratio of data retransmission for HSDPA is 1%, the HSDPA Iub bandwidth is: Average HSDPA Iub bandwidth for each NodeB:

kbpsIub HSDPA 1791%331%11%201360020002000

Since the 7.2Mbps physical layer rate corresponding to application layer rate 6.24Mbps, Peak HSDPA Iub bandwidth for each NodeB is:

MbpsMbpsIubHSDPA 96.8%331%1124.6 IP over E1/T1 For IP over E1/T1, the DL average HSDPA Iub bandwidth for each NodeB is:

kbpsIub HSDPA 1508%121%11%201360020002000

Since the 7.2Mbps physical layer rate corresponding to application layer rate 6.24Mbps, Peak HSDPA Iub bandwidth for each NodeB is:

MbpsMbpsIubHSDPA 55.7%121%1167.6 Iub bandwidth for signaling, CCH and O&M

Iub bandwidth for signaling For ATM over E1/T1 and IP over E1/T1, the Iub bandwidths for signaling are about 10% of traffic Iub bandwidth.

Iub bandwidth for CCH For ATM over E1/T1, the typical Iub bandwidth of CCH for S111 is

kbpsIub DLCCH 213371_

For IP over E1/T1, the typical Iub bandwidth of CCH for S111 is kbpsIub DLCCH 183361_

Iub bandwidth for O&M For ATM over E1/T1 and IP over E1/T1, the Iub bandwidths for O&M are both 64kbps.

Total Iub bandwidth ATM over E1/T1

of 91

DL total Iub bandwidth is: MbpsKbpsMaxIubtotal 1.10643*711.1*)bpsKbps,8.96M1791520Kbps864,1313Kbps(

IP over E1/T1 DL total Iub bandwidth is:

MbpsKbpsMaxIubtotal 5.8643*611.1*)bpsKbps,7.55M1508447Kbps749,1063Kbps(

of 91

5 Radio Resource Capacity Management Detail formula & performance counters used in evaluation will be provided by separate documentation.

5.1 General Aggregation Rule In general for all considerations in this document based upon performance measurement data, regarding in particular the dimensioning or utilization calculations, following rules have to be applied:

All calculation is based on hourly values. If only 15mins values are available, the MAXIMUM 15mins value of the observed hour has to be used.

Daily Aggregation: The Busy Hour is defined as the maximum hourly value of the observed characteristic in one day,

Weekly aggregation: The average BH value of highest 5 daily BH values,

Monthly aggregation: The average of 4 weeks weekly aggregation value,

For description of the utilization of any resource or considerations of up-/downgrade capacity of any resource, the monthly aggregation has to be used

Note:

A calendar month is NOT defined by all calendar days (28-31) included, but always by the a) previous 4 weeks (floating) or b) by the weeks of the first 4 Wednesdays of a calendar month (calendar)

Utilization definition:

0 Utilization mean entire certain resource is not used.

Idle utilization such as uplink resource, background noise rise, common channel, and signaling load are taken in to account of utilization definition.

E.G.

For UMTS cell, assume that

Downlink common channel power = total power * 20%,

Service channel power usage so power utilization = 30%

So downlink power utilization = 20% + 30% = 50%.

of 91

5.2 TCH Utilization Evaluation Rule Resource Description:

TCH is traffic channel to support CS traffic in GSM system.

Criteria If the TCH congestion ratio > 1%, and TCH utilization > 80% with 50%HR, and the TCH availability >= 98%, then need to start capacity evaluation.

Evaluation and Recommendation:

TCH congestion may be caused by high traffic, RF interference and equipment problem, so before we come to need expansion conclusion, optimization and troubleshooting should be executed first. Then if the TCH utilization exceeds the certain threshold, expansion is necessary.

of 91

5.3 SDCCH Utilization Evaluation Rule Resource Description:

SDCCH is channel for location update, IMSI attachment, service setup, SMS, type 3 fax and so on. SDCCH congestion can lead to call setup failure and HO call drop.

Criteria

If the SDCCH congestion ratio > 0.5%, and the SDCCH availability>98%,

Evaluation and Recommendation:

Except for high traffic, SDCCH congestion may be caused by other non capacity reasons such as RF problem and poor parameter configuration. Before we make the decision of SDCCH expansion, the optimization and equipment trouble shooting should be finished.

SDCCH expansion or TRX expansion are proposed if the SDCCH congestion is caused by high traffic.

5.4 PDCH Evaluation Rule Resource description:

PDCH is channel supporting PS service in GSM system.

PDCH utilization = PS busy hour traffic / PS traffic supported

PS traffic supported is calculated base on:

Assume average coding scheme MCS6 applied for all cells

BH Bandwidth per PDCH(Mbit) = 29 Kbps* 3600/1024=102 Mbit/PDCH

Criteria PDCH Utilization > 80%

Evaluation and recommendation

High PDCH utilization may be caused by high traffic, RF interference and equipment problem, so before we come to need expansion conclusion, optimization and troubleshooting should be executed first. Then if the PDCH utilization exceeds the certain threshold, expansion is necessary.

5.5 Abis Utilization Evaluation Rule Resource Description

Abis interface carries both signaling & traffic data transmission between BSC and BTS,

Criteria:

If the Abis Utilization of IP > 80%, expansion or re-plan is needed.

Evaluation and recommendation

For Abis base on IP, high IUB utilization might caused by wrong bandwidth configuration.

If high Abis utilization is not caused by issue mentioned above, expansion is recommended.

of 91

5.6 UMTS Power Utilization Evaluation Rule Resource Description:

TCP (transmit carrier power) is used to evaluate the downlink power consumption, which represents the downlink loading status. Evaluation of TCP power is helpful to avoid the congestion due to the insufficient power in downlink.

Please be aware that the big TCP utility ratio may be caused also by the bad coverage. Coverage problem must be eliminated before we come to the conclusion that power resources are not enough because of too much traffic.

TCP for R99 services at busy hour (BH), Total TCP both with R99 services and HSPA services at busy hourBHare under assessment here.

Criteria:

Principles for the TCP utilization are:

1) The mean R99 TCP Utility Ratio should not exceed 75%

2) The mean total TCP Utility Ratio ( R99+HSPA+Common channel) should not exceed 90%.

3) Congestion caused by insufficient TCP power is less than 0.5%.

Evaluation & recommendation

If principle 1) is not met, then more carrier or more sites are suggested,

If principle 2) is met, then more research are needed on the HSDPA user perception experiences.

If principle 3) is not met and exist for a long period of time, then expansion may need.

Formulas are:

R99_TCP_Utility_Ratio = R99_Mean_TCP_in_BH / Configured_Total_Cell_TCP

Total_TCP_Utility_Ratio = Total_Mean_TCP_in_BH / Configured_Total_Cell_TCP

of 91

5.7 CE Utilization Evaluation Rule Resource Description:

CE is the base band resources for services in NodeB. CE utilization ratio represents the base band resources consumption status of the NodeB. If the CE utilization ratio exceeds one specified threshold of the total CE, that means CE resources are going to be the limitation of the network. CE expansion is needed in this case.

Mean CE consumption and Max CE consumption in one NodeB at Busy Hour (BH) are used for the evaluation.

Criteria:

The CE utilization ratio analysis principle is shown below:

1The mean CE utilization ratio should not exceed 70% due tos experiences, if yes, expansion is recommended.

2) Congestion ratio due to insufficient CE resources should be less than 0.5%.

Evaluation & Recommendation:

If the mean CE utilization ratio doesnt exceed 70%, but he max CE consumption (UL_Max_Used_CE_Number, DL_Max_Used_CE_Number) exceeds the CE license configuration for one NodeB, congestion due to CE problems are also happened a lot at the same time, then expansion is suggested.

Formulas to get the mean CE consumption in one NodeB are:

UL Mean CE Utility Ratio = UL_Mean_Used_CE_Number_in_BH / Configured_UL_CE_Number

DL Mean CE Utility Ratio = DL_Mean_Used_CE_Number_in_BH / Configured_DL_CE_Number

5.8 Code Utilization Evaluation Rule Resource Description:

Codes here are the OVSF codes for both R99 and HSPA services. If the codes utilization ratio exceeds one specified threshold, which means codes resources are going to be the limitation of the network.

Normally mean codes consumption in one NodeB at Busy Hour (BH) is used for the evaluation.

Criteria:

1) The mean codes utilization for R99 services should not exceed 70%.

2) Congestions due to insufficient codes in busy hour of the cell should not exceed 0.5%.

3) The mean codes utilization for total services should not exceed 70%

Evaluation & Recommendation:

If 1is not met, the codes allocation between R99 services and HSDPA services can be adjusted firstly according to the service distribution. If it is still not OK, then more carriers and sites are suggested. If 2) is not met for a period of time, the adjustment suggestion is the same to 1).

If 3) is not met, then more investigation is needed for the HSDPA single user perception.

Formulas to get the mean R99 codes utilization ratio in one NodeB are:

R99_Code_Utility_Ratio = R99_Mean_Used_Code_in_BH / R99 Available Codes

of 91

5.9 RTWP Utilization Evaluation Rule Resource Description:

RTWP (Received Total Wideband Power) analysis is used to evaluate the uplink interference and loading status. High RTWP may be caused by high traffic or serious interference, interference factor must be eliminated before RTWP value used for uplink loading evaluation.

If theres no external interference, RTWP value in the daytime could represent the traffic status in the uplink.

Criteria: For macro cells, hourly average RTWP should not exceed -100 dBm

For In-building cells (owned DAS and multi-operator DAS), hourly average RTWP should not exceed -95 dBm

Evaluation & Recommendation: Since RTWP is easily influenced by the external interference, so the RTWP results are just for reference and cannot be used for the direct reason of expansion.

Besides interference clearance, split cell and 2nd carrier implementation could reduce RTWP.

5.10 Iub Utilization Evaluation Rule Resource Description:

Iub transmission utilization ratio is used to understand the transmission configuration between NodeB and RNC is enough or not.

Criteria:

The basic principle is that Iub utility ratio of each NodeB should not exceed 80%.

Additionally, a limit of 60% has to be used, if the transmission is based upon TDM and the maximum transmission bandwith consists of only 1 E1.

Evaluatoin and recommendation: For Iub base on ATM, high IUB utilization might caused by E1 flicker or failure.

For Iub base on IP, high IUB utilization might caused by wrong bandwidth configuration.

If high Iub utilization is not caused by issue mentioned above, expansion is recommended.

Formulas are shown below:

Iub utility ratio_ DL = NODEB_Throughput_DL / NODEB_Trans_Cap_DL

Iub utility ratio_ UL = NODEB_Throughput_UL / NODEB_Trans_Cap_UL

of 91

5.11 Common Channel Utilization Evaluation Rule Resource Description:

RACH/FACH channel is common channel which support signaling and few traffic when UE in Cell-FACH state.

Criteria:

RACH Utilization should be less than 50%,

FACH Utilization should be less than 50%,

Evaluation & Recommendation: For high RACH utilization, new carrier/new site or re-planning is needed.

For high FACH utilization additional FACH (max FACH per cell is 2), split cell or 2nd carrier is recommended.

of 91

5.12 UMTS Multi Carrier Expansion Principle If 2nd carrier is available, Multi Carrier Expansion will be triggered once threshold below are reached:

Max (Cell level Code Utilization, UMTS DL Power Utilization) > 80%

Prior to active 2nd carrier due to capacity reasons, optimization or load balance should be done.

2nd carrier planning has to take clusterization rules with minimum 3 sites per cluster into consideration as below:

.

of 91

6 Trigger of New Site Planning 6.1 Due to Coverage Reasons New site will be proposed when criteria below are met:

Input from drive test report + simulation that Coverage level less than minimum signal level requirement of each respective clutter after RF optimization (justification is required);

6.2 Due to Capacity Reasons New site will be proposed 1 or more criteria below are met:

For UMTS:

Power utilization exceed expansion threshold mentioned in Chapter 5 after optimization/rebalance (justification is required) and no additional carrier are available,

Code utilization above expansion threshold mentioned in Chapter 5 after optimization/rebalance (justification is required) and no additional carrier are available,

For GSM:

TRX utilization exceed expansion threshold mentioned in Chapter 5 after optimization/rebalance (justification is required) and no additional TRX are available,

6.3 Other Factors New site SAR (Search area radius) will be of cell radius according to the link budget, and site

nominal planning and SAR will provide by team using digital map with 5m resolution inner Jakarta and 20m resolution outer Jakarta.

Site candidate selection will be based on analysis in digital map, Google earth and survey report with obstacle checking.

Strategy for existing site which cannot meet design guideline is:

a. Site justified totally no need, dismantle will be proposed.

b. Site justified not in right position, but will create coverage hole if dismantle, keep the site until new site on air.

of 91

7 BSC6900 Design Principle 7.1 BSC Capacity Planning Principle

Refer to attachment GBSS12.0 BSC6900 Capacity Calculation

7.2 RNC Capacity Planning Principle Refer to attachment RAN12.0 BSC6900 Capacity Calculation

of 91

8 BSC6900 Capacity Management Note: The detail formula & performance counters used in evaluation will be provided by separate documents.

8.1 General Aggregation Rule In general for all considerations in this document based upon performance measurement data, regarding in particular the dimensioning or utilization calculations, following rules have to be applied:

All calculation is based on hourly values. If only 15mins values are available, the MAXIMUM 15mins value of the observed hour has to be used.

Daily Aggregation: The Busy Hour is defined as the maximum hourly value of the observed characteristic in one day,

Weekly aggregation: The average BH value of highest 5 daily BH values,

Monthly aggregation: The average of 4 weeks weekly aggregation value,

For description of the utilization of any resource or considerations of up-/downgrade capacity of any resource, the monthly aggregation has to be used

Note:

A calendar month is NOT defined by all calendar days (28-31) included, but always by the a) previous 4 weeks (floating) or b) by the weeks of the first 4 Wednesdays of a calendar month (calendar)

Utilization definition:

0 Utilization mean entire certain resource is not used.

Idle utilization such as uplink resource, background noise rise, common channel, and signaling load are taken in to account of utilization definition.

E.G.

For UMTS cell, assume that

Downlink common channel power = total power * 20%,

Service channel power usage so power utilization = 30%

So downlink power utilization = 20% + 30% = 50%.

of 91

8.2 BSC6900 Board Resource and Expansion Threshold GSM related Board:

Board name Expansion/Rebalance Trigger XPU Average Busy Hour CPU Usage > 50%

DPU Average Busy Hour CPU Usage > 70%

INT Average Busy Hour CPU Usage > 70%

GCU Average Busy Hour CPU Usage > 70%

TNU Average Busy Hour CPU Usage > 70%

SCU Average Busy Hour CPU Usage > 70%

Additional resource utilization needs to be monitored with criteria that resource utilization should be less than 70%:

XPU Board:

Specification

Board BHCA BTS Cells TRX XPUb 1,050,000 640 640 640

Notes:

The specifications are the maximum capability base on user profile.

DPUc Board:

Specification

Board TCH IWF flow DPUc 960 3740

DPUd Board:

Specification

Board Total PDCH PDCH per Cell DPUd 1,024 48

of 91

UMTS Related Board

Board name Expansion/Rebalance Trigger SPU Average Busy Hour CPU Usage > 50%

DSP Average Busy Hour CPU Usage > 60%

INT Average Busy Hour CPU Usage > 70%

Additional resource utilization needs to be monitored with Criteria that resource utilization should be less than 70%:

SPU Board:

Specification

Board BHCA Node B Cells Active Users SPUb 140,000 180 600 9000

Notes:


DPU Board:

Specification

Board PS

Throughput (Mbps)

Erlang Cells Active Users

DPUe 335 3350 300 5880


Interface Board:

Notes:

The preceding specifications are the maximum capability regarding the corresponding service.

The data service in the CS domain indicates the 64 kbit/s video phone service.

The number of session setup/release times indicates the signaling processing capacity of an Iub/Iu/Iur-interface board.

The Iur-interface service processing specifications of the board are the same as its Iub-interface service processing specifications.

of 91

8.3 BSC6900 GSM License and Evaluation Threshold BSC capacity evaluation mainly includes CPU utilization, signal link load and resource usage. It should be evaluated one by one. The main expansion triggers are as follows:

TRX configuration exceeds the maximum number of TRX BSC allowed, add new BSC or re-plan the BSC area.

BHCA > 80% of the maximum BHCA allowed by BSC, add new BSC or re-plan the BSC area.

PDCH Usage > 80% of the maximum PDCH allowed by BSC, add new BSC or re-plan the BSC area.

8.4 BSC6900 UMTS License and Evaluation Threshold RNC license evaluation gives operators a picture what is the license utilization status and help to expand license before it gets congested.

RNC license evaluation includes: CS, PS, HSDPA, HSUPA, etc.

The basic principle is that expansion is needed if RNC license utility ratio exceeds 70%.

Formulas are:

CS license utility ratio= CS_Traffic_BH/ CS_License

PS license utility ratio= PS_Traffic_BH/ PS_License

HSDPA license utility ratio= HSDPA_Traffic_BH / HSDPA_License

HSUPA license utility ratio= HSUPA_Traffic_BH / HSUPA_License

8.5 BSC6900 A Interface Evaluation Rule Method for A interface evaluation is traffic per circuit, the total TCH traffic in BSC is taken into consideration.

Principle

If traffic per circuit > 0.7 Erl. Expansion or re-plan is needed.

Formula

interfacercuits_A um_busy_ci interfacercuits_A um_idle_ci____

NNBSCtrafficTCHcircuitperTraffic

Where,

TCH_traffic_BSC Total traffic volume on TCHs in the BSC

Num_idle_circuits_A interface: Average number of idle circuits on the A interface

Num_busy_circuits_A interface: Average number of busy circuits on the A interface

of 91

8.6 BSC6900 Gb Interface Evaluation Rule

Gb Link (FR) Utilization (UL):

Uplink bandwidth actually used on the BC(kbit/s) / Configured bandwidth of the BC(kbit/s) * 100%

Gb Link (FR) Utilization (DL):

Downlink bandwidth actually used on the BC(kbit/s) / Configured bandwidth of the BC(kbit/s)* 100%

GB Link (Over IP) Utilization (UL):

Highest Receive Rate of the FEGE Ethernet Port(kbit/s) / Min of (Board Capacity,Configured Backbone Link

GB Link (Over IP) Utilization (DL):

Highest Transmit Rate of the FEGE Ethernet Port(kbit/s) / Min of (Board Capacity,Configured Backbone Link

Principle

GB Link Utilization > 60%, expansion is needed.

8.7 BSC6900 SS7 Load Utilization Evaluation Rule SS7 Load Utilization (UL): Transmission bandwidth usage of the MTP2 link

SS7 Load Utilization (DL): Receiving bandwidth usage of the MTP2 link

SS7 Loading > 40%, expansion is needed.

8.8 BSC6900 Ater Load Evaluation Rule Ater Load =

Mean number of busy circuits on the Ater interface / ( (Mean number of busy circuits on the Ater interface) + (Mean number of idle circuits on the Ater interface ) * 100%

Principle

Average Busy Hour Ater Load > 60%, expansion is needed.

8.9 BSC6900 Iu-CS Interface Evaluation Rule Iu-CS Contron plan Load = > 50%, expansion or re-plan is needed.

Iu-CS User Plan Load > 70%, expansion or re-plan is needed.

8.10 BSC6900 Iu-PS Interface Evaluation Rule Iu-PS Contron plan Load > 50%, expansion or re-plan is needed.

Iu-PS User Plan Load > 70%, expansion or re-plan is needed.

of 91

9 Cell Detail Design 9.1 BSIC Planning Principle

BSIC (BCC+NCC) group are defined as below:

BSIC Group NCC BCC 1 0 0 1 2 3 4 5 6 7 2 1 0 1 2 3 4 5 6 7 3 2 0 1 2 3 4 5 6 7 4 3 0 1 2 3 4 5 6 7 5 4 0 1 2 3 4 5 6 7 6 5 0 1 2 3 4 5 6 7

Reserved 6 0 1 2 3 4 5 6 7 Reserved 7 0 1 2 3 4 5 6 7

BSIC are planned follow rules below:

NCC border are created where 1 NCC Set (8 BCC Set) are able to be implemented in 1 border

There will be max 8 sites in 1 NCC border, if later on we have more than the 9th etc sites will used reserved NCC set

Area of each border are defined as 1.5 km * 1.5 km

9.2 GSM LAC Planning Principle Support Traffic/LAC 2500Erl

Support TRX/LAC 1000TRX

Paging times per LAC suggest less than 220000/Hour.

To minimize the location update, the geographic factors and mobile behavior should be taken into accounts:

Try best to utilize geographic factors, the mountains, rivers, or other natural resources set as LAC boundary

The streets and land mark building should not set as LAC boundary

LAC boundary should not be parallel or vertical to the streets but beveled to the streets

LAC boundary should follow with least traffic area instead of high traffic areas

LAC boundary should not cross BSC/RNC border

Split LAC should be triggered if the paging times per LAC more than 220000/Hour.

of 91

9.3 UMTS LAC Planning Principle Support 500 paging per message per second cell

Paging Channel Utilization should less than 50%

To minimize the location update, the geographic factors and mobile behavior should be taken into accounts:

Try best to utilize geographic factors, the mountains, rivers, or other natural resources set as LAC boundary

The streets and land mark building should not set as LAC boundary

LAC boundary should not be parallel or vertical to the streets but beveled to the streets

LAC boundary should follow with least traffic area instead of high traffic areas

LAC boundary should not cross BSC/RNC border

UMTS LAC boundary should overlap with GSM LAC boundary to reduce the location update from GSM to UMTS network.

LAC Splitting should be triggered if paging Congestion Ratio > 0.5%, while paging utilization > 50%.

9.4 UMTS SAC Planning Principle The Service Area Code (SAC) together with the PLMN-Id and the LAC will constitute the Service Area Identifier.

- SAI = PLMN-Id + LAC + SAC

The Service Area Identifier (SAI) is used to identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN.

Thus, SAC = Cell ID Rule is applied for SAC Planning.

of 91

9.5 PSC Planning Principle Primary scrambling codes (PSC) are divided into 21 groups as below:

16 + 1 = 17 groups for Macro sites

4+1 =5 groups for Indoor sites

Allocation SC Set Code Group Scrambling Set Sector

Reserved 0 0 1 2 3 4 5 6 7

Mac

ro C

ell

1 1 8 9 10 11 12 13 14 15 1 2 16 17 18 19 20 21 22 23 2 3 24 25 26 27 28 29 30 31 3

2 4 32 33 34 35 36 37 38 39 1 5 40 41 42 43 44 45 46 47 2 6 48 49 50 51 52 53 54 55 3

3 7 56 57 58 59 60 61 62 63 1 8 64 65 66 67 68 69 70 71 2 9 72 73 7

Network Design

Documents

Transcript of Network Design