Network Design

Radio Network Design Guideline

Revision History

Page 2 of 91

Table of Contents Revision History .......................................................................................................................... 2 Table of Contents........................................................................................................................ 3 1

Overview ............................................................................................................................. 5

2

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

3

4

5

6

2.1

BTS and NodeB Configuration..................................................................................... 6

2.2 2.3 2.4 2.5

Technical Specification of Antenna System ............................................................... 11 Antenna System Design Requirements ..................................................................... 12 Feeder and Jumper Requirements ............................................................................ 13 TMA Design Requirements........................................................................................ 14

2.6

RET Solution for Macro BTS ..................................................................................... 15

Coverage Planning Guideline ............................................................................................ 18 3.1 3.2 3.3 3.4

Coverage Design Requirement .................................................................................. 18 Propagation Model .................................................................................................... 19 Digital Map Resolution............................................................................................... 20 GSM Link Budget ...................................................................................................... 21

3.5 3.6

UMTS Link Budget .................................................................................................... 23 Planning Tool ............................................................................................................ 30

Capacity Planning Guideline.............................................................................................. 31 4.1 4.2 4.3

GSM Output Power Setting ....................................................................................... 31 GSM Time Slot/TRX Design Principle ........................................................................ 34 GSM Frequency Planning (SFH) ............................................................................... 35

4.4 4.5 4.6 4.7

Abis Dimensioning Guideline ..................................................................................... 36 UMTS Channel Power Setting ................................................................................... 40 CE Dimensioning Guideline ....................................................................................... 41 Iub Dimensioning Guideline ....................................................................................... 50

Radio Resource Capacity Management............................................................................. 60 5.1

General Aggregation Rule ......................................................................................... 60

5.2 5.3 5.4 5.5

TCH Utilization Evaluation Rule ................................................................................. 61 SDCCH Utilization Evaluation Rule............................................................................ 62 PDCH Evaluation Rule .............................................................................................. 62 Abis Utilization Evaluation Rule ................................................................................. 62

5.6 5.7 5.8 5.9

UMTS Power Utilization Evaluation Rule ................................................................... 63 CE Utilization Evaluation Rule ................................................................................... 64 Code Utilization Evaluation Rule ................................................................................ 64 RTWP Utilization Evaluation Rule .............................................................................. 65

5.10 5.11 5.12

Iub Utilization Evaluation Rule ................................................................................... 65 Common Channel Utilization Evaluation Rule ............................................................ 66 UMTS Multi Carrier Expansion Principle .................................................................... 67

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

Page 3 of 91

7

6.1

Due to Coverage Reasons ........................................................................................ 68

6.2 6.3

Due to Capacity Reasons .......................................................................................... 68 Other Factors ............................................................................................................ 68

BSC6900 Design Principle ................................................................................................ 69 7.1 7.2

8

9

10

BSC Capacity Planning Principle ............................................................................... 69 RNC Capacity Planning Principle............................................................................... 69

BSC6900 Capacity Management....................................................................................... 70 8.1 8.2

General Aggregation Rule ......................................................................................... 70 BSC6900 Board Resource and Expansion Threshold ................................................ 71

8.3 8.4 8.5 8.6

BSC6900 GSM License and Evaluation Threshold .................................................... 73 BSC6900 UMTS License and Evaluation Threshold .................................................. 73 BSC6900 A Interface Evaluation Rule ....................................................................... 73 BSC6900 Gb Interface Evaluation Rule ..................................................................... 74

8.7 8.8 8.9 8.10

BSC6900 SS7 Load Utilization Evaluation Rule ......................................................... 74 BSC6900 Ater Load Evaluation Rule ......................................................................... 74 BSC6900 Iu-CS Interface Evaluation Rule ................................................................. 74 BSC6900 Iu-PS Interface Evaluation Rule ................................................................. 74

Cell Detail Design.............................................................................................................. 75 9.1

BSIC Planning Principle ............................................................................................ 75

9.2 9.3 9.4 9.5

GSM LAC Planning Principle ..................................................................................... 75 UMTS LAC Planning Principle ................................................................................... 76 UMTS SAC Planning Principle................................................................................... 76 PSC Planning Principle ............................................................................................. 77

9.6 9.7

Tcell Planning Principle ............................................................................................. 80 PLMN Value Tag Planning Principle .......................................................................... 81

HSPA/HSPA+ and Multi Carrier and Layer Deployment Strategy ....................................... 82 10.1 10.2 10.3

UMTS (Single Carrier)/GSM Layering Design ............................................................ 82 UMTS (Dual Carrier)/GSM Layering Design............................................................... 85 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

Page 4 of 91

1

Overview

Page 5 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

Page 6 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.

Page 7 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 

Complete site solution including battery backup, power supply and space for 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..

Page 8 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.



Complete site solution including battery backup, power supply and space for 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

Page 9 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.

Page 10 of 91

2.2 Technical Specification of Antenna System Product

Model

Description

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 Antenna

ADU451900 A19452100

Dual Band Antenna, Quad port – 65° (XXPOL), 1710 – 2170MHz, 19.5dBi, Electrical Down tilt 2° ~ 8° XPOL Panel 1710 - 2170 -65° 21 dBi, Fixed tilt 0°.

ARCU02001

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

Antenna

RCU

TMA

ATA182000

TMA KIT

02230BUF

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 0.5 m AISG TMA Auxiliary Materials Kit (Not include TMA), GU

TMA SBT KIT

ATA212000 A00SMBT00

Cable AISG

ACOAISG02

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 with 0.5m AISG cable Signal Cable, AISG Communication cable, 15M, D9M+D9(PS)(W), CC4P0, 5PB(S), RC85F(S)-1,

Aluminum Feeder Aluminum Feeder Aluminum Feeder

LCF 78-50JL LCF 114-50JL LCF 158-50JL

Aluminum Feeder, 7/8 100M Package Aluminum Feeder, 5/4 100M Package Aluminum Feeder, 13/8 100M Package

Page 11 of 91

2.3 Antenna System Design Requirements Antenna Gain Selection Rule: 

Dense Urban & Urban: 18dBi



Suburban & Rural:



Special cases for Rural: 21dBi

19dBi

Antenna Tilt Configuration Rule: 

Mechanical down tilt should be <= 2 degree for all clutter type.



In typical DU & U implementation, electrical tilt should be used instead of mechanical down tilt.

Antenna Port Selection Rule: 2-port antenna is applied for following cases: 

2G or 3G standalone site.



By default, 2G/3G co-location site should use two separate antennas on same height with minimum 1 meter horizontal separation from centre of antenna for both tower and roof top site.



If any space issue with horizontal separation, 2G/3G antenna height vertical separation should be no more than 1 meter from edge to edge of antenna for tower site.

4-port antenna is applied for following cases: 

2G/3G co-located site in case there is any space issue or tower loading issue for tower or roof top site.



GSM only site using DBS3900 solution with 2 physical RRU per sectors (5 ~ 8 TRXs).

Page 12 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 <= 25m, 7/8” feeder will be used.  For 25m < feeder length <= 43m, 5/4” feeder will be used.  For feeder length > 43m, 13/8” feeder will be used.  ½” jumper length <=3m

Page 13 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.

Page 14 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

Antenna

RCU

3m Jumper

SBT

Control cable

Feeder 1 (main)

Feeder 2 (diversity)

DC+control signals 3m Jumper TX/RXA RXB

BTS

Page 15 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.


1.5m Jumper

Antenna

RCU

DTMA

1.5m Jumper

NodeB0 NodeB1

Feeder 1 (main)

Feeder 2 (diversity) 3m Jumper

DC+control signals

TX/RXA RXB

BTS

Page 16 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

SBT

RCU

3m Jumper

RXB TX/RXA

RRU CPRI Cable less than 100m

BBU

Page 17 of 91

3

Coverage Planning Guideline 3.1 Coverage Design Requirement The nominal planning is calculated based on, as follows: ID 1 2 3 4 ID 1 2 3 4

Clutter Type Dense Urban Urban Suburban Rural Item Dense Urban Urban Suburban Rural

2G Design Level -64 dBm -68 dBm -75 dBm -82 dBm 3G Design Level -75 dBm -78 dBm -82 dBm -89 dBm

2G Acceptance Level -69 dBm -73 dBm -80 dBm -87 dBm 3G Acceptance Level -81 dBm -84 dBm -88 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.

Page 18 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 <= 1 dB and standard deviation of <=7 dB.

Page 19 of 91

3.3 Digital Map Resolution Below table summarize digital map resolution being in use during coverage planning. ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

Region

Clutter Dense Urban Urban Suburban Rural Dense Urban Urban Suburban Rural Dense Urban Urban Suburban Rural Dense Urban Urban Suburban Rural Urban Suburban Rural Urban Suburban Rural

Digital Map Resolution 5m 5m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m 20m

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

Page 20 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 Antenna Gain for SU & RU

18dBi 19dBi

Page 21 of 91

GSM Link Budget Dense urban UL Frequency Band(MHz)

Urban

DL

UL

1800

Propagation Model Environment

Suburb

DL

UL

1800

DL

Rural UL

1800

DL

1800

SPM

SPM

SPM

SPM

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) EIRP(dBm)

d

0

0

0

0

0

0

0

0

e=a+b-c+d

30

58

30

58

30

58

30

58

Slow Fading Margin Slow fading margin(dB)

f

Area coverage probability

9.9

8.4

6.8

4

95%

95%

95%

90%

14

12

10

6

Slow fading Standard Deviation(dB) 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

l

20

18

14

10

Penetration Loss(dB) Allowed Max Path Loss(dB)

m=e-(gh+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

Page 22 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

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

Indoor

Indoor

Indoor

Indoor

Indoor

Indoor

Indoor

Indoor

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

3

3

3

3

3

3

3

3

0.65

0.65

0.65

0.65

0.65

0.65

0.65

0.65

User Enviroment

Urban

Suburban

Rural

TMA

Nodeb Feeder Loss(dB) Cell Average Ioc/Ior SHO Overhead

20%

20%

20%

20%

Softer HO Overhead

10%

10%

10%

10%

Area Coverage Probability

92%

92%

92%

92%

10

10

10

10

HSDPA Power Allocation Ratio

65%

65%

65%

65%

Power Allocation Ratio Per HS-SCCH

5%

5%

5%

5%

1

1

1

1

HSDPA Parameters HSPA Max used Code Number for Single Carrier

HS-SCCH Number per Cell

Page 23 of 91

UMTS Link budget TCH Link Budget Morphology UL/DL

Dense Urban

Urban

Suburb

Rural

UL

DL

UL

DL

UL

DL

UL

DL

UE_U6_ D8

BS 3 Sector

UE_U6_ D8

BS 3 Sector

UE_U6_ D8

BS 3 Sector

UE_U6_ D8

BS 3 Sector

Project Parameters Equipment TMA Sector Type Diversity Mode

3 Sector 2 Rx No Diversity Diversity




Indoor

Indoor

Indoor

Indoor

Link Parameters User Environment Cell Edge Channel Model Cell Edge Continuous Coverage Service Cell Edge Service Rate(kbps)

AMR 12.2

TU3

SHO Supported

TU50 HSDPA

RA120 AMR 12.2 HSDPA

RA120 AMR 12.2 HSDPA

12.20

384.00

12.20

384.00

12.20

384.00

FALSE

TRUE

FALSE

TRUE

FALSE

TRUE

FALSE

21.00

41.00

21.00

41.00

21.00

41.00

21.00

41.00

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

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) NodeB/UE Noise Figure (dB)

0.00

3.00

0.00

3.00

0.00

3.00

0.00

3.00

4.60

7.00

4.60

7.00

4.60

7.00

4.60

7.00

HSDPA

AMR 12.2

12.20

384.00

TRUE

Max. TCH TX Power (dBm) Feeder Loss (dB)

TX

RX

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) DL Max. TCH TX Power Required

3.01

5.53

3.01

8.78

3.01

7.48

3.01

7.48

FFM(dB) Min. Received Signal Strength (dBm)

1.11

0.00

0.00

0.00

0.00

0.00

0.00

0.00

-138.14

-99.36

-138.61

-95.30

-139.70

-96.16

-139.70

-96.16

Path Loss Penetration Loss (dB) Area Coverage Probability Slow Fading Standard Deviation (dB) SFM(dB) Path Loss (dB)

20.00

16.00

12.00

8.00

95.00%

95.00%

95.00%

90.00%

11.70

9.40

7.20

6.00

8.28

14.16

6.80

11.56

4.30

7.81

0.90

3.57

127.86

121.20

133.81

123.74

141.40

132.35

148.80

140.58

Cell Radius

Page 24 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

Propagation Model Cell Radius (km) TCH Cell Radius (km)

2125

1935

0.24

1.67

SPM 0.37

2140

1935

0.69

3.62

SPM

0.24

2125

1935

1.86

6.93

SPM

2125 SPM 3.86

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

Page 25 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


1.50


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%

Page 26 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

Page 27 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


1.50


25.00

Cell Coverage Radius (km)

0.40

NodeB RX Diversity Path Loss (dB)

2 Rx Diversity 128.91

Max Throughput of UE HSUPA UE Type UE TTI (ms)

CAT6 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 Slow Fading Standard Deviation (dB)

95.00% 11.70

Page 28 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

Page 29 of 91

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

Page 30 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

2

40

46.02


3

27

44.31


4

20

43.01


5

16

42.04


6

12

40.79


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.

Page 31 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)


TOC Power

1

60

47.78


2

40

46.02


3

27

44.31


4

20

43.01


5

12

40.79


6

10

40.00


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


3~4

1

Combine

18W


Notes: Default of power level is set to 0

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: Default of power level is set to 0

Page 32 of 91

5. DBS3900 Solution with MRRU V1 Single MRRU per Sector with Single Transmit (not applicable for current project): No.TRX per Sector

Static TRX Power(W)


TOC Power

1

40

46.02


2

20

43.01


3

13

41.14


4

10

40.00


5

7.5

38.75


6

6

37.78



TOC Power

Single MRRU per Sector with Dual Transmit: No.TRX per Sector

Static TRX Power(W)

1

40

46.02


2

40

46.02


3

20

43.01


4

15

41.76


5

12

40.79


6

10

40.00


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.

Page 33 of 91

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

SDCCH GOS≤0.5%



TCH GOS≤1%



TCH utilization≤80%



Half rate ≤50% (AMR Half Rate≤45%)



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;

Page 34 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 =

NTRX ) NARFCN

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.

Page 35 of 91

4.4 Abis Dimensioning Guideline Abis Configuration 2G Average Abis Bandwidth Requirement 2011

Abis total（Kbps)

2012

Abis total（Kbps)

2013

Abis total（Kbps)

S222

1025

S222

1087

S222

1280

S444

2204

S444

2337

S444

2337

2G Peak Abis Bandwidth Requirement 2011

Abis Peak total（Kbps)

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:

TRX Number per Cell Input HR Ratio

Calculation Based on TDM / IP?

Output

Abis Interface Transmission Bandwidth Based on TDM / IP

PDCH Number per Cell

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

Page 36 of 91



Output Sample



Related Performance Counter

ABIS Resource Capability Measurement R9101 R9102 R9103 R9104 R9105 R9106 R9107 R9108 R9109 R9110 R9111

Number of Application Attempts of Abis Timeslot Number of Successful Application Attempts of Abis Timeslot Number of Release Requests of Abis Timeslot Number of Successful Releases of Abis Timeslot Number of Application Attempts of IP PATH or HDLC Bandwidth (16K) Number of Successful Application Attempts of IP PATH or HDLC Bandwidth (16K) Number of Release Requests of IP PATH or HDLC Bandwidth (16K) Number of Successful Releases of IP PATH or HDLC Bandwidth (16K) Number of Unsuccessful Application Attempts of Abis Timeslot Because of no Idle Timeslot Number of Unsuccessful Application Attempts of Abis Timeslot for Connecting Network Failure 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:

Page 37 of 91

Page 38 of 91

Page 39 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

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

SSCHPower

Dedicate Channel power setting is as below: Service Type Max. Downlink Transmission Power (in Min. Downlink Transmission Power (in the parentheses is the dB value) the parentheses is the dB value) CS Service 12.2K AMR

0(0)

-150(-15)

64K transparent data

30(3)

-120(-12)

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)

PS Service

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

Page 40 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

WBBPb2

3

128

128

Twelve 1T2R cells

WBBPb3

6

256

256

Twelve 1T2R cells

WBBPb4

6

384

384

Twelve 1T2R cells

WBBPd1

6

192

192

Twenty-four 1T2R cells

WBBPd2

6

384

384


WBBPd3

6

256

256


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)

Page 41 of 91

CE dimensioning flow chart:

1

2 2

1

3 3

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)

Page 42 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:

CE total  CE CS _ Average  CE PS _ Average CE

  CSTrafficP i

CS _ Average

erNodeB

i

 ( 1  SH Overhead)

 CEFactor

i

CE PS _ Average   PSTrafficp erNodeB i  (1  SH Overhead) （1＋R burst _ i ) （1＋R retransmissi on )  CEFactori i

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:

Page 43 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,

2000 * 50 * 3 * (1  20%) * (1  20%) * (1  5%)  3 CEs 64 * 0.7 * 3600 2000 *100 * 2 * (1  20%) * (1  20%) * (1  5%)  4 CEs CE for DL PS64k: 64 * 0.7 * 3600 2000 * 80 * 4 * (1  20%) * (1  20%) * (1  5%)  3 CEs CE for DL PS128k: 128 * 0.7 * 3600 CE for UL PS64k:

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

Page 44 of 91

CE Dimensioning for HSPA 1.

HSDPA Uplink CE dimensioning (

CE HSDPA _ UL

)

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 (

CE HSDPA _ UL

) can be calculated according to number of

simultaneously connected HSDPA users ( N HSDPA _ Links ) 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：

Throughput Tr _ HSDPA N HSDPA _ Links

=

Rate Avg _ HSDPA _ Data

(1.)

Where,

N HSDPA _ Links Throughput

is the online HSDPA links number Tr _ HSDPA

Rate Avg _ HSDPA _ Data

is the total traffic of HSDPA services

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:

CE HSDPA _ UL Where

= N HSDPA _ Links *

i

(2.)

i is the CE map in Table 3-3. UL A-DCH bear rate and CE factor of HSDPA services mapping HSDPA AveRate (kbps) 128 384 3600 7200 14400

UL A-DCH BearRate 16 32 64 128 384

UL A-DCH CE (over DCH) 1 1.5 3 5 10

UL A-DCH CE (over HSUPA) 1.00 1.00 1.85 3.17 5.59

Page 45 of 91

2.

HSDPA Downlink CE dimensioning (

CE HSDPA _ DL

)

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:

CE HSDPA _ DL  LinksHSDPA *1 

2000 * 3600 * (1  0%) * (1  10%) *1 = 44 CEs 3600 * 50

CE in uplink:

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

CE HSDPA _ AUL  Links HSDPA * CEFactor A  DCH  ( Links OnlineHSDP A  Links HSDPA ) = 2000*3600 2000*3600 2000* 3600 { *1.5  (  ) *1}* (1  0%)* (110%)* (1 20%) 3600* 400 3600*50 3600* 400 = 56 CE

Page 46 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) 10ms 2ms TTI TTI

RAN 12.0

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

48 5742 5440 * 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.)

CE HSUPA _ Traffic  Links HSUPA * CEFactor HSUPA Where:

Links HSUPA 

Throughput PerNodeB HSUPA ( kbit ) * (1  SHOfactor ) * (1  Re transmissi on ) AverageThr oughputPer UserHSUPA (kbit )

* (1  Burstratio ) (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. CEFactorHSUPA 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 ( CE HSUPA _ AUL ) 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:

CE HSUPA _ AUL = Links HSUPA *1 (5.)

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

Page 47 of 91

(2)In Downlink ( CE HSUPA _ ADL ) 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

Links HSUPA  

2000 * 500 * (1  20%) * (1  11%) *1 = 19 CE 20 * 3600

CE for traffic

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

CE Traffic _ UL = { 

2000 * 500 2000 * 500 2000 * 500 * 4.1  (  ) * 1} * (1  20%) * (1  11%)  28 CE 128 * 3600 20 * 3600 128 * 3600

Total CE in uplink 19+28 = 47 CE

Page 48 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.

CE A _ UL  Max (CE HSUPA _ AUL , CE HSDPA _ AUL ) CE A _ DL  Max (CE HSUPA _ ADL , CE HSDPA _ ADL )

CE HSUPA _ AUL : CE consumed by uplink A-DCH of HSUPA; CE HSDPA _ AUL : CE consumed by uplink A-DCH of HSDPA; CE HSUPA _ ADL : CE consumed by downlink A-DCH of HSUPA; CE HSDPA _ ADL : 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:

CE UL _ Total  Max (CE CS _ Peak _ UL , CE CS _ Average _ UL  CE PS _ UL  CE A _ UL  CE HSUPA ) CE DL _ Total  Max (CE CS _ Peak _ DL , CE CS _ Average _ DL  CE PS _ DL  CE A _ DL )

Page 49 of 91

4.7 Iub Dimensioning Guideline Iub Configuration 3G Average Iub Bandwidth Requirements 2011 Iub (kbps) UL DL DU

2012 UL

2013

DL

UL

DL

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 RU

821 821

1,475 1,475

1,485 1,485

3,756 3,756

2,582 2,582

7,239 7,239

3G Peak Iub Bandwidth Requirements Iub (kbps) DL

2011 7.2Mbps

2012 14.4Mbps

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

Page 50 of 91

Input Subscribers Subs per NodeB

Iub Dimensioning

Ou

Erlang Services Iub Peak Bandwidth

Iub B CS Traffic Voice Traffic VP Traffic

CS/VoIP over HSPA Traffic GoS Requirements PS Traffic

Erlang Services Iub Average Bandwidth max

PS Iub Bandwidth HSPA Iub Bandwidth max

PS64 Throughput PS128 Throughput PS384 Throughput

Service Iub Bandwidth

PS Retransmission HSPA Traffic

HSPA End-user Experience Rate Bandwidth Common Channel Bandwidth O&M Bandwidth

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:

IubTotal  Max[( Max[ IubCS ,CS / VoIPoverHSPA _ Peak , ( IubPS _ Avg  IubCS , CS / VoIPoverHSPA _ Avg  IubHSPA )]), IubHSPA _ End used _ Experience _ Rate ]  IubMBMS  IubCCH  IubO & M The ultimate Iub configuration is decided by the larger one of uplink and downlink Iub bandwidth.

Page 51 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

Page 52 of 91

Page 53 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 ErlangB（MDE）model. 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.

Page 54 of 91

Traffic & Service Iub Bandwidth

GoS Requirements

MDE

Peak Iub Bandwidth 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:

IubCS and CS/voIP over HSPA_Average  ∑TrafficPerNodeBi * (1  RSHO ) * RIub _ i i

RSHO : Soft handover overhead which does not include softer handover; R Iub _ i 3.

: Iub bandwidths for CS and CS/voIP over HSPA service I, shown in Figure 1Table1. 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:

IubPS _ Average 

∑TrafficPerNodeBi * (1  RSHO ) * (1  RBurst ) * (1  RRe trans ) * RIub _ i i

RRe trans : Retransmission factor of PS services, which is equal to BLER/(1-BLER); RBurst : 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:

Page 55 of 91

Iub HSUPA  TrafficPer NodeB * ( 1  R SHO ) * ( 1  R Burst ) * ( 1  R Re trans ) * ( 1  R Iub _ overhead ) RIub _ overhead: 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:

Iub HSDPA  TrafficPer NodeB * (1  R Burst ) * (1  R Re trans ) * (1  R Iub _ overhead ) RIub _ overhead: 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: Iub HSDPA _ Peak  PeakRatePe rNodeB * ( 1  R Re trans ) * ( 1  R Iub _ overhead ) 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 3.6Mbps 7.2Mbps 14.4Mbps

Application Layer Rate 3.2Mbps 6.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)

Page 56 of 91

Bearers AMR12.2k (mErl) CS64k mErl) PS64k (Kbits) PS128k (Kbits) PS384k (Kbits) HSPA (Kbits)

Uplink 20 2 125 0 0 200

Downlink 20 2 100 200 200 2000

GoS 2% 2% N/A N/A N/A 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:  0.02 Erl / user  2000user / NodeB  1  20%  48 Erl Video call traffic:  0.002 Erl / user  2000user / NodeB  1  20%  4.8 Erl The peak Iub bandwidth needed by voice service is:  ErlangB 48,0.02 20  0.5kbps  583kbps The peak Iub bandwidth needed by video call is:  ErlangB 4.8,0.02   80kbps  770kbps

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

IubCS _ Peak  1313 kbps CS peak Iub bandwidth for IP over E1/T1 For DL direction: Voice traffic:  0.02 Erl / user  2000user / NodeB  1  20%  48 Erl Video call traffic:  0.002 Erl / user  2000user / NodeB  1  20%  4.8 Erl The peak Iub bandwidth needed by voice service is:

 ErlangB48,0.02  17  0.5kbps  495kbps The peak Iub bandwidth needed by video call is:

 ErlangB4.8,0.02  71kbps  683kbps Using MDE, the CS peak Iub bandwidth for voice and video call is

IubCS _ Peak  1063 kbps  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:  48 Erl / NodeB  20  0.5kbps  480kbps Average Iub needed by Video Call:  4.8 Erl / NodeB  80 kbps  384 kbps Average Iub needed by voice and video call is: Iub CS _ Average  480 kbps  384 kbps  864 kbps 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:  48 Erl / NodeB  17  0.5kbps  408kbps Average Iub needed by Video Call:  4.8 Erl / NodeB  71kbps  341kbps Average Iub needed by voice and video call is:

Page 57 of 91

IubCS _ Average  408 kbps  341kbps  749 kbps  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: 2000 100 2000 200 IubPS _ Average   1  20%  1  20%  1  1%  83   1  20%  1  20%  1  1%  165 64  3600 128 3600 2000 200   1  20%  1  20%  1  1%  492 384 3600  520kbps  IP over E1/T1 For IP over E1/T1, the DL R99 PS Iub bandwidth for each NodeB is: 2000 100 2000 200 IubPS _ Average   1  20%  1  20%  1  1%  74   1  20%  1  20%  1  1%  141 64  3600 128 3600 2000 200   1  20%  1  20%  1  1%  418 384 3600  447kbps  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: 2000  2000 Iub HSDPA   1  20 %   1  1%   1  33 %   1791 kbps 3600 Since the 7.2Mbps physical layer rate corresponding to application layer rate 6.24Mbps, Peak HSDPA Iub bandwidth for each NodeB is:

Iub HSDPA  6.24 Mbps  1  1% 1  33%  8.96 Mbps  IP over E1/T1 For IP over E1/T1, the DL average HSDPA Iub bandwidth for each NodeB is: 2000  2000 Iub HSDPA   1  20 %   1  1 %   1  12 %   1508 kbps 3600 Since the 7.2Mbps physical layer rate corresponding to application layer rate 6.24Mbps, Peak HSDPA Iub bandwidth for each NodeB is:

Iub HSDPA  6.67 Mbps  1  1% 1  12%  7.55 Mbps  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 Iub CCH _ DL  71  3  213 kbps For IP over E1/T1, the typical Iub bandwidth of CCH for S111 is Iub CCH _ DL  61  3  183 kbps 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

Page 58 of 91

DL total Iub bandwidth is:

Iubtotal  Max(1313Kbps,864Kbps  520Kbps  1791Kbps,8.96Mbps) * 1.1  71* 3  64  10.1 Mbps IP over E1/T1 DL total Iub bandwidth is:

Iubtotal  Max(1063Kbps,749Kbps  447 Kbps  1508Kbps,7.55Mbps ) * 1.1  61 * 3  64  8.5 Mbps

Page 59 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 week’s 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%.

Page 60 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.

Page 61 of 91

5.3 SDCCH Utilization Evaluation Rule 


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.

Page 62 of 91

5.6 UMTS Power Utilization Evaluation Rule 


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 hour（BH）are 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

Page 63 of 91

5.7 CE Utilization Evaluation Rule 


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: 1）The mean CE utilization ratio should not exceed 70% due to’s 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 doesn’t 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 


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% 


If 1）is 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

Page 64 of 91

5.9 RTWP Utilization Evaluation Rule 


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 there’s 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 


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 2

nd

carrier implementation could reduce RTWP.

5.10 Iub Utilization Evaluation Rule 


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

Page 65 of 91

5.11 Common Channel Utilization Evaluation Rule 


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%, 


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.

Page 66 of 91

5.12 UMTS Multi Carrier Expansion Principle nd

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

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

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

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

Page 67 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.

Page 68 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

Page 69 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 week’s 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%.

Page 70 of 91

8.2 BSC6900 Board Resource and Expansion Threshold GSM related Board: Board name XPU

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

DPU

Average Busy Hour CPU Usage > 70%

INT


GCU


TNU


SCU


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

Page 71 of 91

UMTS Related Board Board name SPU

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

DSP


INT


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

SPUb

140,000

180

600

Active Users 9000

Notes: 


DPU Board:

Specification Board DPUe 

PS Throughput (Mbps) 335

Erlang

Cells

Active Users

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.

Page 72 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

Traffic _ per _ circuit 

TCH _ traffic _ BSC N um_idle_ci rcuits_A interface  Num_busy_ci rcuits_A interface

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

Page 73 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.

Page 74 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 9 etc sites will used reserved NCC set

th

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.

Page 75 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.

Page 76 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

Reserved

0 1

2

3

4

5 Macro Cell

Code Group

6

7

8

9

10

11

Scrambling Set 0

1

Sector

2

3

4

5

6

7

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

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

7

56

57

58

59

60

61

62

63

1

8

64

65

66

67

68

69

70

71

2

9

72

73

74

75

76

77

78

79

3

10

80

81

82

83

84

85

86

87

1

11

88

89

90

91

92

93

94

95

2

12

96

97

98

99

100

101

102

103

3

13

104

105

106

107

108

109

110

111

1

14

112

113

114

115

116

117

118

119

2

15

120

121

122

123

124

125

126

127

3

16

128

129

130

131

132

133

134

135

1

17

136

137

138

139

140

141

142

143

2

18

144

145

146

147

148

149

150

151

3

19

152

153

154

155

156

157

158

159

1

20

160

161

162

163

164

165

166

167

2

21

168

169

170

171

172

173

174

175

3

22

176

177

178

179

180

181

182

183

1

23

184

185

186

187

188

189

190

191

2

24

192

193

194

195

196

197

198

199

3

25

200

201

202

203

204

205

206

207

1

26

208

209

210

211

212

213

214

215

2

27

216

217

218

219

220

221

222

223

3

28

224

225

226

227

228

229

230

231

1

29

232

233

234

235

236

237

238

239

2

30

240

241

242

243

244

245

246

247

3

31

248

249

250

251

252

253

254

255

1

32

256

257

258

259

260

261

262

263

2

33

264

265

266

267

268

269

270

271

3

Page 77 of 91

Allocation

SC Set

Reserved

12

Macro Cell

13

14

15

16

Reserved

1

Indoor Cell

2 3 4

Reserved

Code Group

Scrambling Set

Sector

0

0

1

2

3

4

5

6

7

34

272

273

274

275

276

277

278

279

1

35

280

281

282

283

284

285

286

287

2

36

288

289

290

291

292

293

294

295

3

37

296

297

298

299

300

301

302

303

1

38

304

305

306

307

308

309

310

311

2

39

312

313

314

315

316

317

318

319

3

40

320

321

322

323

324

325

326

327

1

41

328

329

330

331

332

333

334

335

2

42

336

337

338

339

340

341

342

343

3

43

344

345

346

347

348

349

350

351

1

44

352

353

354

355

356

357

358

359

2

45

360

361

362

363

364

365

366

367

3

46

368

369

370

371

372

373

374

375

1

47

376

377

378

379

380

381

382

383

2

48

384

385

386

387

388

389

390

391

1

49

392

393

394

395

396

397

398

399

2

50

400

401

402

403

404

405

406

407

1

51

408

409

410

411

412

413

414

415

2

52

416

417

418

419

420

421

422

423

1

53

424

425

426

427

428

429

430

431

2

54

432

433

434

435

436

437

438

439

3

55

440

441

442

443

444

445

446

447

1

56

448

449

450

451

452

453

454

455

2

57

456

457

458

459

460

461

462

463

3

58

464

465

466

467

468

469

470

471

1

59

472

473

474

475

476

477

478

479

2

60

480

481

482

483

484

485

486

487

3

61

488

489

490

491

492

493

494

495

1

62

496

497

498

499

500

501

502

503

2

63

504

505

506

507

508

509

510

511

3

Page 78 of 91

PSC are planned by following these rules below: •

This method is only applicable for new city/area.

•

PSC border are created where 1 SC Set (8 Scrambling Set) are able to be implemented in 1 border

•

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

•

Same PSC shall not be reused within 10km.

th

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

Page 79 of 91

9.6 Tcell Planning Principle Tcell (Time offset of cell) defines the difference between the system frame number (SFN) and NodeB Frame Number (BFN) of the NodeB which the cell belongs to. Tcell of different cells under one NodeB should be unique. Thus, Tcell Planning Rule are listed below:

Cell ID

Tcell Value

Cell 1

CHIP0

Cell 2

CHIP256

Cell 3

CHIP512

Cell 4

CHIP768

Cell 5

CHIP1024

Cell 6

CHIP1280

Cell 7

CHIP1536

Cell 8

CHIP1792

Cell 9

CHIP2048

Cell 10

CHIP2304

Page 80 of 91

9.7 PLMN Value Tag Planning Principle Parameter ID

Parameter Name

MML Command

NE

PlmnValTa gMax

Max PLMN value tag

ADD LAC (Mandatory) ADD RAC (Mandatory)

RNC

PlmnValTa gMin

Min PLMN value tag

ADD LAC (Mandatory) ADD RAC (Mandatory)

RNC

Meaning

Maximum PLMN tag value corresponding to a LAC. It is defined by the operator. For detailed information of this parameter, refer to 3GPP TS 25.331. Minimum PLMN tag value corresponding to a LAC. It is defined by the operator. For detailed information of this parameter, refer to 3GPP TS 25.331.

Value Type

GUI Valu e Rang e

Actua l Value Rang e

Interval Type

1~25 6

1~256

Interval Type

1~25 6

1~256

The value range of plmnvaltag(both LAC and RAC) is 1~256, “+8” rule is applied in order to define 64 adjacent LAC or RAC plmnvaltag. Example: LAC 0001

PlmnValTagMin(LAC) 17

PlmnValTagMax(LAC) 24

0002 0003

25 33

32 40

RAC 0001

PlmnValTagMin(RAC) 17

PlmnValTagMax(RAC) 24

0002

25

32

0003

33

40

Page 81 of 91

10

HSPA/HSPA+ and Multi Carrier and Layer Deployment Strategy

10.1 UMTS (Single Carrier)/GSM Layering Design 3G equipment supports inter-connection with other 2G/2.5G network. Since same PLMN is employed on both WCDMA and GSM network, can support CS/PS roaming and handover from 3G to 2G. 3G/2G handover solutions are planned as below: 

UMTS to GSM handover for service continuity when loosing UMTS coverage in both idle and connected mode; and when connected mode with only voice service are detected in UMTS network;



GSM to UMTS mobility in idle mode, to allow dual mode mobiles to return on the 3G coverage as quick as possible;



GSM to UMTS mobility in packet active mode, to benefit from higher bit rates and QoS services provided by the UMTS network. The 3G 2G inter-working solution can be explained in figure below:

PS Handover CS Handover

Coverage based Handover to 2G Cell Reselection to 3G

Service based intersystem change Coverage based Handover to 2G

3G Coverage

2G Coverage only

• CS Handover Strategy: 3G handover to 2G based on Service, return back to 3G by cell reselection • PS Handover Strategy: 3G and 2G bi-direction service handover by cell reselection

UMTS/GSM/GPRS inter-working solution

UMTS/GSM handover procedures are depicted in figure 2.

Page 82 of 91

3G Coverage Handover to 2G

2G Coverage only Camping on WCDMA in idle mode

Voice Call

Handover to 2G

Staying in 2G during the call

Cell Reselection to 3G

Connected mode

Data Service Service begin

Cell Reselection to GPRS

Cell Reselection to 3G

Cell Reselection to GPRS

Figure 1 CS and PS handover procedures

3G/2G Cell selection and reselection strategy are planned as below: Cell selection and reselection mechanisms are the key technologies to pilot the dual-mode terminal to connect to 3G network with high priority. In UMTS, the mobile terminal performs cell reselection 

In idle mode and PS connected mode



Immediately after a CS call

When camped on a cell, the UE will regularly search for a better cell in terms of cell reselection criteria among the cells in the lists of system information. If there is, the better cell is selected and the terminal will camp on that cell. In a pure GSM or UMTS network, the system only contains neighbor cell lists with the same access technology. In order to implement the smooth roaming in UMTS and GSM system, neighbor cell information of different radio access technology and inter-RAT cell criteria for performing and reporting measurements should be contained in combined 3G/2G coverage. Dual-mode mobile terminal measures signal strength both of GSM and WCDMA cells. Different types of measurements are used in different RAT and modes for the cell reselection. So the change of cell may imply a change of RAT between GSM and UMTS.

Page 83 of 91

For Single Carrier scenario, neighbor strategy below shall be defined as below:  Neighboring of F1 cells 

Intra-frequency F1 neighbours



GSM cells

 Neighboring of GSM cells  Intra-frequency DCS neighbours  Inter-RAT neighbors only for F1 UMTS cells

Single carrier neighbor Strategy:

Page 84 of 91

10.2 UMTS (Dual Carrier)/GSM Layering Design For Dual Carrier scenario, 3G/2G Cell selection and reselection and handover strategy are planned same as UMTS single carrier scenario. >

Selection of second carrier can be based on current network performance and traffic management strategy

>

The second carrier will be activated based on the following strategy.

Mobility Strategy in idle mode as below:

a. Camp on F1 an F2 randomly b. UE makes cell selection and reselection between F1 and F2 cells

Page 85 of 91

Mobility Strategy in connected mode as below:

a. All 3G cells provide services of CS Speech (AMR), CS Video, R99 PS, and HSDPA b. Allow intra-frequency handover based on coverage both for F1 & F2; c. Allow handover based on coverage only from F2 to F1 at the coverage edge of F2, no handover based on coverage from F1 to F2; d. Configure blind handover neighboring relationships between F1 and F2 cells within the same coverage range; allow bi-directional blind handover between F1 and F2 in the area both F1 and F2 covered. Thus, neighbor strategy below shall be defined as below:  Neighboring of F1 cells 




GSM cells



Twin cell (parent) only for inter-frequency neighbors

 Neighboring of F2 cells 




Twin Cell (parent) only for inter-frequency neighbors



GSM cells (same as F1 cells)

 Neighboring of GSM cells  Intra-frequency DCS neighbours  Inter-RAT neighbors only for F1 UMTS cells

Page 86 of 91

10.3 HCS Strategy 

micro cell/IBC cell will apply Layer1 and Macro Cell will apply Layer2

Two layers of a GSM 1800 system Layer

Description

2 macro

This layer consists of the GSM 1800MHz macro cells.

1 micro

This layer consists of the mini cells of GSM 1800.They are designed for covering hotspot areas and dead zones.

Handover Design in HCS network provide varies of Handover Algorithm to handle HCS network, to make sure continuous of mobile connection. 

Layer HO Algorithm, provide the process to make IBC/Micro cell with higher priority to absorb more traffic.



Fast moving MS HO Algorithm, provide the process to make fast moving MS handover to a macro cell with larger coverage area to avoid frequency handover.



Rx_Level_Drop_HO Algorithm and Edge HO Algorithm, provide the process to handle special case like corner area, or border area of Micro, Macro area handover. In those scenario, due to building blocking or the small coverage area of micro cells, MS might experience fast Rx_Level decreasing

General Handover Procedure

Page 87 of 91

10.4 HSPA/HSPA+ Rollout Strategy Area/Year

2011

2012

2013

Dense Urban

HSUPA 1.4Mbps/HSDPA 14.4Mbps HSUPA 1.4Mbps/HSDPA 21Mbps

HSUPA 11.5Mbps/HSDPA 42Mbps

Urban

HSUPA 1.4Mbps/HSDPA 14.4Mbps HSUPA 1.4Mbps/HSDPA 14.4Mbps HSUPA 1.4Mbps/HSDPA 21Mbps

Suburban

HSUPA 1.4Mbps/HSDPA 7.2Mbps

HSUPA 1.4Mbps/HSDPA 14.4Mbps HSUPA 1.4Mbps/HSDPA 14.4Mbps

Rural




The following table summarize the pre-requisite for HSPA/HSPA+ implementation:



Feature

System

HSDPA

UMTS

HSUPA

UMTS

HSPA+

UMTS

Implementation pre-requisite Minimum Iub bandwidth requirement is 11 Mbps (or equivalent to 5E1)to support 7.2Mbps, and 10 HS-PDCH code per cell. Minimum Iub bandwidth requirement is 3 Mbps (or equivalent to 2 E1) to support 1.4Mbps with 10ms TTI and 2 * SF4 per cell. HSDPA/HSUPA is enabled, capable terminal (cat 13 ~ 14 and 17 ~ 20) penetration > 30%, and 15 HS-PDCH code per cell.

Note:  Capable terminal penetration = Certain feature capable terminal number / all UMTS capable terminal number * 100%

Page 88 of 91

11 GSM & UMTS Key Parameter Design Guideline GSM & UMTS parameter dictionary and common parameter setting refer to annex “2G/ 3G Parameters Dictionary”. GSM common parameter setting including: 1. Cell basic attributes parameters 2. Cell idle parameters 3. Cell call control parameters 4. Cell handover parameter 5. Cell power control parameter 6. 2G/3G Interoperability 7. GPRS / EDGE channel attributes UMTS common parameter setting including: 1. Cell Selection & Reselection 2. Intra-frequency handover 3. Inter-frequency handover 4. Inter-system handover 5. Call admission control 6. Load control 7. HSPA Notes: In case of any parameter tuning required due to cluster optimization, the parameter changed shall be done through CR and MOP.

Page 89 of 91

12 BSS/RAN Feature Implementation Guideline Refer to attachment “RAN and BSS Feature Activation Guideline”.

Page 90 of 91

13 Annexes 01. Antenna System Specification

02. Feeder & jumper Specification

03. 2G/3G Parameter Dictionary

04. Marketing Polygon

05. BSS and RAN Feature Activation Guideline

06. BSC and RNC Capacity Calculation Method

07. GSM and UMTS Link Budget Table

Page 91 of 91

Network Design

Recommend Documents