03 RN20023EN14GLN1 EGPRS BSS Dimensioning and Planning

(E)GPRS BSS Dimensioning and Planning
RN 2002
(E)GPRS Explain: Chapter 3
(E) GPRS BSS Dimensioning and

Planning
Nokia Siemens Networks
RNM20023EN14GLN1
RN20023EN14GLN1
Legal Notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and
slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive
property of Nokia Siemens Networks . Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation
or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute,
amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material.
Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same
individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia
Siemens Networks .
The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session
for development of groups without the prior written agreement of Nokia Siemens Networks.
RN20023EN14GLN1
RN20023EN14GLN1
Module objectives
After completing this learning element, the participant will be able to:
Theory:
Describe the Coverage Planning and Link Budget process

Know different ways to deploy (E)GPRS in the Network
Explain the main steps for the Dimensioning of the EGPRS system
Explain the impact of different features on the dimensioning process
Describe the connectivity limits of different PCU and BSC versions
Calculate the required number of PCUs
Calculate an example for a given scenario
Evaluate the impacts of Mobility planning
RN20023EN14GLN1
RN20023EN14GLN1
Network Dimensioning and Planning - Content

Coverage and Interference Planning
Capacity Planning (Deployment, TSL Data Rate and BSS connectivity)
Dimensioning Example
Mobility Planning
RN20023EN14GLN1
RN20023EN14GLN1
(E)GPRS Coverage Planning and Link Budget

The (E)GPRS coverage area depends on the GSM service area.
The coverage planning aspects concern the provision of sufficient C/N ratios across the
coverage area in UL and DL.
Each coding scheme is suited to a particular range of C/N (or Eb/No) for a given block
error rate (BLER)
The higher the level of error protection, the lower the required C/N.
Due to the different C/N requirements the relative coverage area of the coding schemes is
different:
The MCS-5 coverage is approx 50% of MCS-1, while MCS-8 coverage is approx 40%
of MCS-5
In urban areas the limiting factor is usually the interference caused by reused frequencies
not the coverage
-> C/I requirements
RN20023EN14GLN1
RN20023EN14GLN1
(E)GPRS Coverage Planning and Link Budget

(E)GPRS Coverage Relative to MCS-5 (Noise limited)
2.5
Relative Range
1.5
0.5
MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
RN20023EN14GLN1
RN20023EN14GLN1
Link Budget Calculation Voice/ (E)GPRS

Receiving End
Sensitivity
Additional fast fading margin
Connector, cable and body loss
Antenna gain
MHA and diversity (space, IUD, IDD)
gain
Transmitting End
Output power
Back-off
Isolator, combiner and filter loss
Connector, cable and body loss
Tx Antenna gain
Cell Range
BS and MS antenna height
Standard deviation
Building penetration loss
(BPL)
BPL deviation
Area Type correction factor
Location probability
BTS Area
k*R
Intelligent Uplink Diversity (IUD)

Intelligent Downlink Diversity (IDD)
7
RN20023EN14GLN1
RN20023EN14GLN1
(E)GPRS Link Budget Example

Receiving and Transmitting End
RECEIVING END:
RX RF-input sensitivity (as GSM05.05) for speech
dBm
BS
-109.0
MS
-102.00
dBm
Eb/No
6.00
-109
Eb/No
6.00
-102
Throghput kbit/s
Es/No,Eb/No [dB] | BLER [%] w/o IR
Required signal power (sensitivity)
S = BTS noise Power + Es/No
Addit fast fading marg (voice+CSdata)

Cable loss + connector
Body loss
Rx antenna gain
MHA Gain
Diversity gain
Isotropic power
Field strength
dB
dB
dB
dBi
dB
dB
dBm
dBV/m
TRANSMITTING END:
TX RF output peak power (GMSK)
(mean power over RF cycle)
Backoff for 8-PSK
Isolator + combiner + filter
RF-peak power, combiner output
Cable loss + connector
Body Loss
IDD
TX-antenna gain
Peak EIRP
(EIRP = ERP + 2dB)
Isotropic Path Loss Uplink / Downlink
Isotropic path loss
EPR
W
dBm
dB
dBm
dB
dBi
W
dBm
dB
2.00
2.00
0.00
18.00
0.00
4.00
-127.0
9.28
2.00
0.00
0.00
0.00
0.00
-100.0
36.28
MS
1.00
30.00
0.00
0.00
30.0
0.00
0.00
BS
28.18
44.50
0.00
3.80
40.7
2.00
0.00
0.00
1.00
30.00
157.00
156.7
18.00
467.74
56.70
156.70
295.12092
BS
MS
-108.5
-102.00
TP
TPIR
53.28
53.84
BLER w/oIR
Es/No
27.74
10.00
-88.33
-81.93
2.00
0.00
15.00
0.00
4.00
-105.3
30.95
MS
2.00
33.00
6.00
0.00
27.0
0.00
0.00
2.00
0.79
29.00
134.33
140.7
0.00
0.00
2.00
URBAN
1.00
-85.9
50.35
BS
28.18
44.50
2.00
2.00
38.8
2.00
0.00
1.00
15.00
302.00
54.80
140.73
190.54607
RN20023EN14GLN1
RN20023EN14GLN1
(E)GPRS Link Budget
Cell Range For Indoor and Outdoor

CELL SIZES
COMMON INFO
MS antenna height (m):
BS antenna height (m):
Standard Deviation (dB):
BPL Average (dB):
BPL Deviation (dB):
OKUMURA-HATA (OH)
Area Type Correction (dB)
Macro
1.5
25.0
7.0
15.0
10.0
4.0
INDOOR COVERAGE
Propagation Model
Slow Fading Margin + BPL (dB):
Coverage Threshold (dBV/m):
Coverage Threshold (dBm):
Location Probability over Cell Area(L%):
Macro
Cell Range (km):

OUTDOOR COVERAGE
Propagation Model
Slow Fading Margin (dB):
OH
26.7
63.0
-73.3
95%
0.91
Macro
OH
7.4
Coverage Threshold (dBV/m):

Coverage Threshold (dBm):
Location Probability over Cell Area(L%):
Cell Range (km):
43.6
-92.6
95%
3.16
Cell Area (km2)

3-sector (K=1.95)
2-sector (K=1.3)
Omni (K=2.6)
9
RN20023EN14GLN1
BPL Building Penetration Loss
19.44
12.96
25.92
OH Okomura-Hata
RN20023EN14GLN1
(E)GPRS Link Budget

Reference sensitivities
The reference sensitivity performance with 10 % BLER are defined in 3GPP 45.005 (new version
of GSM 05.05) for GPRS and EGPRS using GMSK or 8PSK for MS or BTS for different channel
types and different propagation conditions and different bands:
GSM 900 and GSM 850
Example for MS (DL) for

EGPRS using 8PSK
Table is only
Example!
There are
much more
in
3GPP 45.005
Type of
channel
Propagation conditions
static
TU50
(no FH)
TU50
(ideal FH)
RA250 (no
FH)
HT100 (no
FH)
PDTCH/M
CS-5
dBm
-98
-93
-94
-93
-92
PDTCH/M
CS-6
dBm
-96
-91
-91.5
-88
-89
PDTCH/M
CS-7
dBm
-93
-84
-84
-83**
PDTCH/M
CS-8
dBm
-90.5
-83**
-83**
PDTCH/M
CS-9
dBm
-86
-78.5**
-78.5**
USF/MCS5 to 9
dBm
-102
-97.5
-99
-100
-99
* cannot be measured
** in the table refers to a 30% block error rate
10
RN20023EN14GLN1
RN20023EN14GLN1
10
Frequency Planning: Timeslot capacity

Especially for EGPRS the individual user throughput depends a lot of the environment.
In the planning process, one can estimate the average Carrier over Interference level in
a certain Cell and determine the Timeslot capacity.
Other factors, which can lead to a reduction of the individual user throughput come from
Timeslot sharing. In the dimensioning process the main focus is on cell level
throughput and not user related so that these effects can be neglected.
In case of GPRS with CS 1 and 2 there is almost no reduction due to C/I
Peak throughput
C/I distribution
59.2 Kbps
TSL Capacity
TSL sharing
Average user throughput
per allocated TSL
Non-optimum protocols can

reduce further the effective
user throughput for some
services (TCP based)
EGPRS
1 TSL
11
RN20023EN14GLN1
RN20023EN14GLN1
11
Frequency Planning: GPRS

Simulations
Relative cell radius of different GPRS
Coding Schemes (CS1=100%)
Through-put for 1 Timeslot
kbps
Minimum
Average
16
14
12
10
8
6
4
2
0
CS-2
CS-4
CS-1
100
100
84
80
81
74
71 67
60
45
52
40
20
0
CS1
CS2
CS3
CS4
Hopping
12
Typical
NW C/I
CS-3
10
15
C/I
20
25
Non Hopping
RN20023EN14GLN1
RN20023EN14GLN1
12
Frequency Planning EGPRS

With impairments:
-The TSL data rate is C/I dependent
-Lower C/I can reduce the TSL data rate
significantly
-The figure shows that the TSL data rate is
around 35 kbps if the C/I is 15 dB.
Kbit/s
-The proper frequency plan of GSM network

is very important to maximize TSL data rate
Impairments are signal distortions

created by e.g. amplifier non-linearities
and they increase the
susceptibility to errors especially
for MCSs, which do not have strong
FEC (Forward Error Correction)
C/I
13
RN20023EN14GLN1
RN20023EN14GLN1
13
Frequency Planning
Frequency allocation and average C/I level
The existing frequency allocation has high impact on EGPRS performance. Loose re-use patterns will
provide better performance for all MCSs
Data rate and network capacity
EGPRS highest data rates require high C/I, typ > 20dB for MCS-7, 8 & 9. There is very likely no extra
spectrum for EDGE so efficient use of the existing spectrum is very important. EGPRS traffic suited to
BCCH use - typically the layer with highest C/I. But limited number of TSLs available on BCCH so that
the territory may require additional TSLs from TCH TRXs.
Sensitivity in tighter reuse and higher load
EDGE can utilize tighter reuse schemes and this is beneficial when planning for high load with limited
frequency resources. For systems with stringent spectrum constraints, EGPRS can offer good
performance even with tight re-use patterns (1/3 or 3/9). Load dependent
Typical values:
BCCH layer (reuse 12):
GPRS (CS-2): typ. = 11 Kbps
GPRS (CS-1/4): typ. = 14 Kbps
EGPRS (all MCS): typ. = 45 Kbps
Non-BCCH layer (hopping):
GPRS (CS-2): typ. = 10-11 Kbps
GPRS (CS-1/4): typ. = 11-14 Kbps
EGPRS (all MCS): typ. = 20-40 Kbps
Dedicated layer for (E)GPRS:
GPRS (CS-2): typ. = 10-12 Kbps
GPRS (CS-1/4): typ. = 10-16 Kbps
EGPRS (all MCS): typ. = 20-55 Kbps
14
RN20023EN14GLN1
RN20023EN14GLN1
14
EGPRS and GPRS Coverage Comparison

Es/No=42.3 dB
Path loss [dB]
120.8
132.1
138.8 143.5
147.1
150.1 152.6 154.8
156.7 158.4
160.0
DL Throughput per TSL [Kbps]
60
EGPRS
50
GPRS CS1-2
GPRS CS1-4
Average
gain: 2.3
40
Average
gain: 3.6
30
Es/No=8.3 dB
20
10
0
1
10
11
Pathloss distance [km]
15
RN20023EN14GLN1
RN20023EN14GLN1
15
Data rate vs. C/I in Time (Field Measurement 1)

Good quality environment (EGPRS, 2 Timeslots)
140
25
20
100
15
C/I (dB)
Throughput (kbps)
120
80
60
10
40
Data Throughput
Application Throughput
C/I-GMSK
C/I-GMSK Polynomial
20
0
0
0
10
20
30
40
Time (s)
16
RN20023EN14GLN1
RN20023EN14GLN1
16

Average quality environment (EGPRS, 2 Timeslots)
25
120
20
80
15
C/I (dB)
Throughput (kbps)
100
60
10
40
Data Throughput
C/I-GMSK
C/I-GMSK Polynomial
20
0
0
10
20
30
40
50
60
70
Time (s)
17
RN20023EN14GLN1
RN20023EN14GLN1
17

Changing quality environment (EGPRS, 2 Timeslots)
80
70
60
18
16
14
50
12
40
10
30
8
6
20
10
0
0
18
C/I (dB)
Throughput (kbps)
20
Data Throughput
C/I-GMSK
C/I-GMSK Polynomial
50
100
150
Time (s)
RN20023EN14GLN1
RN20023EN14GLN1
18

Mobility Planning
19
RN20023EN14GLN1
RN20023EN14GLN1
19
Deployment Planning
The aim behind the preparation of deployment plan is to
adapt the existing network configuration for (E)GPRS
maximize the TSL data rate (RLC/MAC) and multislot usage
minimize the impact of PSW services on CSW services (and vice versa)
take all the hardware and software considerations into account
keep investment controlled
Most of the networks can be described by few cell/segment options
The analysis of the different options can give exact picture about the network based on:
Hardware types, software releases
Features, parameters
Current network structure and functionality
Coverage, quality and capacity characteristics of BSS
20
RN20023EN14GLN1
RN20023EN14GLN1
20
Deployment Plan - Cell / Segment Option Creation

There are various options to deploy GPRS/EGPRS in the network. The following options cover
most of the cell/segment configurations of the network. These options can be analyzed in
details, so the time consuming cell/segment based analysis is not needed. All the options are
examples and can be deployed with different capacities and with territory on the BCCH TRX.
Cell / Segment
option 1
Cell / Segment
option 2
Cell / Segment
option 3
Cell / Segment
option 4
21
Layer 1
Layer strategy
BTSs
CSW, GPRS,
EGPRS
BTS1
Layer strategy
BTSs
Layer1
CSW, (E)GPRS
BTS1
Layer2
CSW only
BTS2
Layer strategy
BTSs
Layer1
CSW, GPRS
BTS1
Layer2
CSW, EGPRS
BTS2
Layer strategy
BTSs
Layer1
CSW, EGPRS
BTS1
Layer2
CSW, GPRS
BTS2
TRXs TSL0
TRX1 BCCH
TRX2 TCH/F
TRX3 TCH/F
TSL1
TCH/D
TCH/F
TCH/F
TSL2
TCH/D
TCH/F
TCH/F
TSL3
TCH/D
TCH/F
TCH/F
TSL4
TCH/D
TCH/F
TCH/F
TSL5
TCH/D
TCH/F
TCH/F
TSL6
TCH/D
TCH/F
Default
TRXs TSL0
TSL1
TRX1 CBCCH SDCCH
TRX2 TCH/F TCH/F
TRX3 TCH/F TCH/F
TSL2
TCH/D
TCH/F
TCH/F
TSL3
TCH/D
TCH/F
TCH/F
TSL4
TCH/D
Default
TCH/F
TSL5
TCH/D
Default
TCH/F
TSL6
TSL7
TCH/D TCH/D
Default Dedicated(E)GPRS
TCH/F TCH/F
TRXs TSL0
TSL1
TRX1 CBCCH SDCCH
TRX2 TCH/F TCH/F
TRX3 TCH/F TCH/F
TSL2
TCH/D
TCH/F
TCH/F
TSL3
TCH/D
TCH/F
TCH/F
TSL4
TCH/D
TCH/F
Default
TSL5
TCH/D
Default
Default
TSL6
TSL7
TCH/D TCH/D
Default Dedicated GPRS
Default Dedicated EGPRS
TRXs
TRX1
TRX2
TRX3
TRX4
TSL3
TCH/F
TCH/D
TCH/F
TCH/F
TSL4
TCH/F
TCH/D
TCH/F
TCH/F
TSL5
Default
TCH/D
TCH/F
Default
TSL6
Default
TCH/D
TCH/F
Default
TSL7
TSL8 PSW terr.
Default Dedicated EGPRS
TCH/D TCH/D
TCH/F TCH/F
Default Dedicated GPRS
TSL1
TSL2
CBCCH SDCCH
TCH/D TCH/D
TCH/F TCH/F
TCH/F TCH/F
TSL7 PSW terr.

TCH/D
TCH/F
Default (E)GPRS
RN20023EN14GLN1
RN20023EN14GLN1
21
Deployment Plan - Cell / Segment Option

Analyses
Cell / Segment
option 1
Cell / Segment
option 2
Cell / Segment
option 3
Options 1 and 2 have only one territory and so GPRS and

EGPRS MSs may be multiplexed onto the same Radio
Timeslots. This multiplexing leads to potential reduction of the
throughput mainly for the EGPRS user in case of PCU1. In
case of PCU2 the reduction is not so big, because PCU2
supports USF granularity 4.
Anyway with not so much traffic good option for PCU1.
Options 3 and 4 have seperate territories for GPRS and

EGPRS MSs. Such configuration can be recommended in
case of many GPRS/EGPRS users and PCU1. With PCU2 the
impact of timeslot sharing is minor and one territory is enough.
Cell / Segment
option 4
22
RN20023EN14GLN1
RN20023EN14GLN1
22
Deployment Plan - Cell / Segment Option 1

Detailed Analysis
Layer strategy
No multiBCF/CBCCH
GPRS and EGPRS in one territory data rate degradation due to multiplexing
There is not any dedicated territory (CDED) The implementation of NMO1 is not
recommended, because the MS cannot be served if there is not any GPRS territory
Signaling strategy
Combined signaling structure load check is needed

TCH usage (CSW)
TRX1 has TCH/D TSLs - which can lead to heavy signaling.

The CSW calls will be allocated to FR firstly.
AMR packing can provide more capacity for PSW traffic
TCH usage (PSW)
CDEF is 2 TSLs only - the 4 TSL DL capable terminals require territory upgrade, which takes
time
23
RN20023EN14GLN1
RN20023EN14GLN1
23

Detailed Analysis
Layer strategy
The Cell / Segment Option 2 has segment configuration.

GPRS and EGPRS in one territory possibility for GPRS-EGPRS multiplexing
The PSW territory has 4 TSLs for 4 TSL DL capable terminals.
Dedicated territory for providing PSW services even when CSW traffic high
NMO1 well supported
Layer 2 is only and preferably used for CSW traffic (GENA = N).
Signaling
SDCCH has enough capacity for LA updates (used by GPRS attached MSs only if NMO1 is not
implemented)
The SDCCH TSL is reducing the available capacity for user traffic.
TCH (CSW)
TRX1 has TCH/D TSLs, which can lead to heavy signaling TRXsig size
AMR packing
Can provide more time slots available for (E)GPRS traffic

Bad C/I - the quality of AMR HR calls might suffer
TCH (PSW)
GPRS and EGPRS multiplexing likely impact depends on the penetration of GPRS and EGPRS users
and CSW traffic
Dedicated territory provides minimum PSW capacity for cell
24
RN20023EN14GLN1
RN20023EN14GLN1
24

Detailed Analysis
Layer strategy
The Cell / Segment Option 3 has several BTSs configuration.

GPRS and EGPRS have separated territory GPRS-EGPRS multiplexing less likely
EGPRS has 4 TSLs territory for 4 TSL DL capable terminals.
There is dedicated territory for providing PSW services even in high CSW traffic, too.
NMO1 well supported
Signaling
SDCCH/8 SDCCH has probably enough capacity

The SDCCH TSL is reducing the available capacity for user traffic.
TCH (CSW)
TRX1 has TCH/D TSLs, which can lead to heavy signaling TRXsig size
AMR packing
More time slots available for (E)GPRS traffic without more hardware
TCH (PSW)
25
Layer1 has GPRS territory only (EGENA = N) with three TSLs.

Layer2 has the EGPRS territory with 4 TSLs, support for 4 RTSL MSs
Less GPRS - EGPRS multiplexing
Both layers have dedicated territory for minimum PSW capacity
RN20023EN14GLN1
RN20023EN14GLN1
25

Detailed Analysis
Layer strategy
The Cell / Segment Option 3 has segment configuration.

GPRS and EGPRS have separated territory GPRS-EGPRS multiplexing less likely
Both layers have 4 TSLs territory for 4 TSL DL capable terminals.
There is dedicated territory for providing PSW services even in high CSW traffic, too.
NMO1 well supported
EGPRS territory is allocated to TRX1. It is useful if BCCH frequency has good C/I
Signaling
The SDCCH has enough capacity

The CSW traffic should be moved from TRX1, because of the limited resources for CSW.
AMR packing
More time slots available for (E)GPRS traffic without more hardware
TCH (CSW)
TRX1 has only two TCH/F TSLs.
TCH (PSW)
26
Layer1 has EGPRS territory (EGENA = Y) with 4 TSLs.

Layer2 has GPRS territory with 4 TSLs support for 4 RTSL MS
Multiplexing is still possible in case of high PSW and CSW traffic, but the possibility is reduced.
Both layers have dedicated territory for minimum PSW capacity
RN20023EN14GLN1
RN20023EN14GLN1
26
Capacity Calculations
After the network audit the following has to be calculated:
Air Interface Capacity Calculations:
TSL data rate
Multislot usage
Available / required capacity calculation
BSS Connectivity Calculations:
PCU calculation
Gb link calculation
- The accuracy of BSS dimensioning depends on the accuracy of the input values
- The capacity of the radio interface has a significant role in defining the capacity of
the rest of the network elements (BSC, SGSN and transmission interfaces between
the different network elements)
- Changes in the BTS configurations have direct impact on the BSC and SGSN
configuration
- The BSC has a limited number of PCUs and each PCU can handle a limited
number of BTSs, TRXs and timeslot.
27
RN20023EN14GLN1
RN20023EN14GLN1
27
Capacity Planning Inputs

The following information should be available to define the available/required capacity:
BSC
BTS
Abis
BSC variant
TRXs
Available time slots
PCU variant
Time slots (Territory)
EDAP
Restrictions (EDAPs, pools,

DSPs)
Voice traffic load
EDAP sharing probability
TRX configuration
Signaling channels
TRX/PCM
BTS
Segment
Free timeslots (Guard TSL)
TRX
GPRS Territory
(DED/DEF/ADD.)
SW version
Deployment
Half rate
DFCA
PCU pooling
Coverage
PCM usage
TRX signaling
Link management
E1/T1 links
Interference
Throughput/TSL
GPRS/EDGE
Data volume
Traffic mix Voice/Data
28
RN20023EN14GLN1
RN20023EN14GLN1
28
Air Interface Capacity Calculations

The dimensioning of the radio network can be based on two different approaches:
Available capacity:
Calculation determines how (E)GPRS resources are available in a given system
The calculation input is a pre-defined system configuration
The calculation output is the available traffic capacity
Alternatively, the available capacities for different alternative configurations can be
calculated
Required capacity:
It is calculated to design a network that supports the defined amount of traffic and
targeted performance level
The inputs are additional traffic volume, type, and performance requirements
The output is the needed amount of traffic dependent hardware and associated software
configurations
29
RN20023EN14GLN1
RN20023EN14GLN1
29
Air interface Capacity Calculations Available

Capacity
The available capacity for data services can be estimated when the existing BTS hardware
and the current voice traffic load is known.
The next step is to calculate the capacity of the air interface related to the different cell /
segment options analyzed before.
The air interface capacity calculation contains the following items:
TSL data rate estimation

PSW Multislot usage (with CSW traffic volume and free TSLs)
The TSL data rate calculations and the territory figures together for all the cells/segments can
give the calculation results of available air interface capacity
Load CS - (Erlang-B)
Margin
Available for
(E)GPRS
Total Capacity = CS + Margin (free TSL in CS) + (E)GPRS Traffic x Territory Occupancy
30
RN20023EN14GLN1
RN20023EN14GLN1
30
Air Interface Capacity Planning Required

Capacity
The required capacity calculation is the calculation of number of TSLs needed for both circuit switched traffic
and packet switched traffic in each cell in order to achieve a given blocking probability for circuit switched traffic
and required throughput for packet switched traffic. Using subscriber information is more complicated, data user
penetration must be known and user data amount per busy hour must be estimated
User profile for BH (example)
PSW BH traffic in kbps and in MB

CSW BH traffic in Erlang
Service Mix: e.g. 45 % Voice, 10 % Video Streaming, 20 % PoC, et
Traffic distribution
Number of users
Traffic density
GPRS/EGPRS multiplexing
Application
Voice
Video (Streaming) GBR
PoCTHP=ARP=1 NBR
Browsing (Interactive) NBR
Email (Background) NBR
MMS (Background) NBR
BH Traffic
12 mErl
1(UL)/32 (DL) kbps
8 (UL)/8 (DL) kbps
0.5 (UL)/3(DL) kbps
0.25(UL)/1(DL) kbps
0.1(UL)/0.1(DL) kbps
GBR = Guaranteed Bit Rate = RT

NBR = Non-Guaranteed Bit Rate = NRT
31
BH Traffic in MB
Voice
0.45 //2.8
2.8
1.8 /1.8
0.225/1.35
0.1125/0.45
0.045/0.045
Bearer
Voice channel
32kbps
8kbps
NRT
NRT
NRT
THP = Traffic Handling Priority

ARP = Allocation Retention Priority
RN20023EN14GLN1
RN20023EN14GLN1
31
PCU Connectivity Capacity Planning

The aim of connectivity capacity planning is to calculate the amount of required PCUs and
allocate the sites (BCFs) among these PCUs (BSCs) for avoiding connectivity limits and
maximizing QoS.
PCU type
BSCi type
#logical PCU
per PIU
#Abis/BTS/TRX/RTSL/Gb
per logical PCU
# EDAP per
logical PCU
PCU
BSCi, BSC2i
256 / 064 / 128 / 128 / 32
16
PCU-S
BSCi, BSC2i
256 / 064 / 128 / 128 / 32
16
PCU-T
BSCi, BSC2i
256 / 064 / 128 / 256 / 32
16
PCU-B
BSC3i*
256 / 064 / 128 / 256 / 32
16
PCU2-U
BSC2i
256 / 128 / 256 / 256 / 32
16
PCU2-D
BSC3i*
256 / 128 / 256 / 256 / 32
16
PCU2-E
BSC3i**
1024 / 384 /1024/1024/ 128
60
* BSC3i refers to BSC3i 660, BSC3i1000/2000 and BSC3i 3000 (Flexi BSC)
** Values here for BSC3i 3000 (Flexi BSC), BSC3i 660, BSC3i1000/2000 reduced values!
32
RN20023EN14GLN1
RN20023EN14GLN1
32
PCU Connectivity Planning

The connectivity planning for maximum capacity is based on the proper set of CDEF and DAP
size
To provide enough capacity for territory upgrade the 75 % utilization in the connectivity
limits is recommended by NSN
The CDEF* is allocated to the cells (BTSs in segment)- if the default capacity is too big
more PCUs are needed.
The Dynamic Abis Pool (DAP)** is allocated to the sites (BCFs). Higher DAP size provides
more MCS9 capable TSLs on air interfaces, but on the other side, higher DAP size needs
more capacity on E1s and more PCUs as well.
Abis channels limits for different logical PCUs, in brackets 75%:
PCU + PCU-S:
128 (92)
PCU-T + PCU-B + PCU2-U + PCU2-D: 256 (192)
PCU2-E:
1024 (768) or 512 (384) in BSC 3i 660/1000/2000
*PCU and PCU-S have 128 radio TSL (not Abis) and 64 BTS limit, which can cause limitations in GPRS only networks.
**Recommended number of EDAPs per PCU1 is 1,2,4 or 8. There is no such recommendation for PCU2!
33
RN20023EN14GLN1
RN20023EN14GLN1
33
Connectivity in PCU
L = Limit
U = Utilization (recommendation: 75%)
Example: PCU2-D supports 256 BTSs

128 TRXs
256 RTSL
256 Abis subslots
32 x 64 kbps Gb throughput
34
RN20023EN14GLN1
RN20023EN14GLN1
34
Abis PCU
In EGPRS networks the main limitation defining the number of PCUs is the Abis channels limits. The
available capacity depends on the PCU version, in case of PCU pooling the amount of pooled PCUs. In
this case one has to assume the summed capacity of all PCUs in the pool. The 75% connecty limit
should still be considered. The distribution of the individual Pools along with the associated Radio
resources between the PCUs will be done by the system.
Abis Capacity of PCU or PSE

Capacity for dynamic territory upgrades in a certain BTS
BTS 19
BTS 16
BTS 20
BTS 17
BTS 18
BTS 12
BTS 13
BTS 14
BTS 15 BTS 5
BTS 8
BTS 9
BTS 10
BTS 11
BTS 1
BTS 2
BTS 3
BTS 4
DAP 3
35
BTS 6
BTS 7
DAP 5
DAP 4
DAP 2
DAP 1
BTS 1
75%
BTS 21
BTS 9
From planning's point of view the Default Capacity is used for each BTS,
1 RTSL = 1 Abis channel
RN20023EN14GLN1
RN20023EN14GLN1
35
Gb dimensioning
The dimensioning of the Gb interface can be based on two different approaches:
Gb EDGE dimensioning based on EDAP:
Each PCU has typically one Gb link towards the SGSN. In case of redundant Gb, two
independent links are needed.
The Gb should be capable of supporting the instantaneous data traffic being carried by all
cells connected to a particular PCU.
Gb size = k * Maximum EDAP size for that network area.
The k-factor is based on the estimate of the short term traffic distribution. If no specific
information about the distribution is available the minimum (k=1.25) may be used, which
means one fully used Abis pool takes all the Gb capacity (can be seen as minimum)
K-factor can range from 1.25, 1.4, 2, 3, .(values above 2 are normally not used)
Gb EDGE dimensioning based on traffic figures:
The basic dimensioning of the Gb interface depends mainly on EGPRS traffic. Because of
very different coding schemes and data rates, it is extremely relevant to know whether the
traffic is GPRS or EDGE.
Therefore, the main decision needed for Gb dimensioning is the amount of payload used,
on average, for EGPRS traffic during a busy hour and the deviation of the traffic between
the peak and minimum values.
Data volume per PCU can be calculated (or estimated) as the total data volume per PCU
or based on subscriber information.
36
RN20023EN14GLN1
RN20023EN14GLN1
36
Multipoint Gb dimensioning aspects

With multipoint Gb several SGSNs (PAPUs) are connected to one PCU/PSE.
-Each Gb will take part of the capacity
-Is only implemented in Gb over IP option and capacity considerations are less critical,
but need to be checked
-If resiliency is target the physical capacity of one Gb link should be able to carry normal
traffic plus in case of failure of one SGSN part of this traffic
Area 2
PCU/PSE
Gb3
Gb2
Gb1
SGSN pool
SGSN 1
37
SGSN 3
SGSN 2
RN20023EN14GLN1
RN20023EN14GLN1
37

Mobility Planning
38
RN20023EN14GLN1
RN20023EN14GLN1
38
Dimensioning Inputs
Example Network
Network/BSC with 40 BCFs.

EGPRS implementation on top of existing GSM network
3 BTSs per BCF
Site configurations & amounts
4+4+4 15 BCFs central area

2+2+2 25 BCFs surrounding area
BCF voice traffic
2+2+2 site on average has traffic of 8 Erl per BTS

4+4+4 site on average has traffic of 18 Erl per BTS
Blocking criteria 2%
Data traffic
Data user support requirement per BTS ~ 50 kbit/s
Average data throughput per BTS (requested by operator)
Central area - 200 kbit/s

Surrounding area 100 kbit/s
Other considerations
All BTSs and TRXs EDGE capable

Gb implementation planned as Frame Relay
39
RN20023EN14GLN1
RN20023EN14GLN1
39
Dimensioning Inputs
Abis Configurations
TRX and Abis Configurations before EGPRS

Implementation
TRX configurations
Only Full Rate voice implementation
Abis configurations
Each BCF has own E1
TRX Configurations
2+2+2 configuration
TSL0
MBCCH
TCH/F
BCCH
TCH
TSL1
SDCCH
TCH/F
TSL2
TCH/F
TCH/F
TSL3
TCH/F
TCH/F
TSL4
TCH/F
TCH/F
TSL5
TCH/F
TCH/F
TSL6
TCH/F
TCH/F
TSL7
TCH/F
TCH/F
TSL3
TCH/F
TCH/F
TCH/F
TCH/F
TSL4
TCH/F
TCH/F
TCH/F
TCH/F
TSL5
TCH/F
TCH/F
TCH/F
TCH/F
TSL6
TCH/F
TCH/F
TCH/F
TCH/F
TSL7
TCH/F
TCH/F
TCH/F
TCH/F
4+4+4 configuration
BCCH
TCH
TCH
TCH
40
TSL0
MBCCH
TCH/F
SDCCH
TCH/F
TSL1
SDCCH
TCH/F
TCH/F
TCH/F
TSL2
TCH/F
TCH/F
TCH/F
TCH/F
2+2+2
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TRXSIG1
TRXSIG3
TRXSIG5
BCFSIG
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TRXSIG2
TRXSIG4
TRXSIG6
Q1-management
4+4+4
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH0
TCH4
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH1
TCH5
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH2
TCH6
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TCH3
TCH7
TRXSIG1 TRXSIG2 TRXSIG3 TRXSIG4

BCFSIG
Q1-management
RN20023EN14GLN1
RN20023EN14GLN1
40
Dimensioning Inputs Deployment Scenarios

TRX configurations
No DR/HR implementation
GTRX = Y
BTS configuration
GENA = Y, EGENA = Y, CMAX = 100 %
RF-environment
Average C/I = 16 dB (BCCH-layer)
Average RxLevel = -85 dBm
Average RLC/MAC throughput for EDGE: 35 kbit/s (BCCH layer)

Typically best C/I TRX preferred for maximum throughput Depending on frequency plan this
can be either BCCH or TCH TRX
Features impacting location selection:
DR RTSL location needs to be considered with 2+2+2 configuration
DR RTSLs should not be allocated close to GPRS territory boundary
41
RN20023EN14GLN1
RN20023EN14GLN1
41
Dimensioning Inputs Free timeslots on Air IF

Free RTSLs between CS and PS territory are required in order to serve incoming CS calls without
blocking
CS downgrade if less RTSLs free in CS territory, PS territory downgrade triggered

CS upgrade PS territory upgrade can be triggered if at least that amount of RTSLs free
Free TSLs for up and downgrade can be controlled by BSC parameters
free TSL for CS downgrade

free TSL for CS upgrade
Mean free RTSLs for 2 TRXs: 1.5 (default)
Mean free RTSLs for 4 TRXs: 2.5 (default)
42
RN20023EN14GLN1
RN20023EN14GLN1
42
Air Interface Available Capacity

2+2+2 configuration
4+4+4 configuration
2 TRXs, 16 RTSLs
2 RTSLs for signaling

14 RTSLs for CS traffic
CS BH traffic 8 Erl per BTS all BTSs have
same BH traffic
Erlang B table 1.7% CS blocking @ BH
Mean free RTSLs = 1.5
4 TRXs, RTSLs
3 RTSLs for signaling
29 RTSLs for CS traffic
CS BH traffic 18 Erl per BTS all BTSs have
same BH traffic
Erlang B table 0.4% CS blocking @ BH
Mean free RTSLs = 2.5
Average available for PS traffic @ CS BH

Amount_of_TRXs*8 Amount_of_TRXs*8 signaling_RTSLs CS_BH_traffic-free_RTSLs
signaling_RTSLs CS_BH_traffic-free_RTSLs
= 4*8-3-18-2.5 = 8.5 RTSLs
= 2*8-2-8-1.5 =4.5 RTSLs
Average PS traffic @ CS BH
Average PS traffic @ CS BH
8.5*35 kbit/s = 297.5 kbit/s (> 200 kbit/s)
4.5*35 kbit/s = 157.5 kbit/s (> 100 kbit/s)
Average available for PS traffic @ CS BH
43
RN20023EN14GLN1
RN20023EN14GLN1
43
Air Interface Available Capacity (Default Territory

Size)
2+2+2 territory considerations
4+4+4 territory considerations
MS multislot capability (4 RTSLs)

Data throughput 100 kbit/s
Air interface 35 kbit/RTSL
=> RTSLs to support 100 kbit/s
100/35 = 2.9 TSLs ~ 3 RTSLs
MS multislot capability (4 RTSLs)

Data throughput 200 kbit/s
Air interface 35 kbit/RTSL
=> RTSLs to support 200 kbit/s
200/35 = 5.7 TSLs ~ 6 RTSLs
Default territory size

Max(MS_multislot, traffic) = 4 RTSLs
Default territory size

Max(MS_multislot, traffic) = 6 RTSLs
44
RN20023EN14GLN1
RN20023EN14GLN1
44
Air Interface Required Capacity (Dedicated

Territory Size)
Streaming user support required per BTS (one streaming user)
Streaming requires 50 kbit/s
=> (50kbit/s)/(35 kbit/s/RTSL) = 2 RTSLs needs to be dedicated (CDED) per BTS in order
to support streaming
2+2+2 configuration
4+4+4 configuration
Available RTSLs for CS traffic per BTS
14 2 (CDED) = 12 RTSLs
Available RTSLs for CS traffic per BTS
Traffic per BTS = 8 Erl

Erlang B (8Erl, 12 TSLs) = 5.1% CS blocking
29-2 (CDED) = 27 RTSLs

Traffic per BTS = 18 Erl
Erlang B (18Erl, 27 TSLs) = 1.1% CS
blocking
5.1% > 2% - NOK

Needed channels for 2% CS blocking
Erlang B (8Erl,2%) = 14 channels
Either 2 more RTSLs (DR/HR) are needed or one
new TRX
1.1% < 2% - OK
Capacity increase done with DR RTSLs
45
RN20023EN14GLN1
RN20023EN14GLN1
45
Air Interface Calculations Summary

2+2+2 configurations
4+4+4 configurations
46
Territory located in BCCH TRX

2 RTSL dedicated territory to support streaming
4 RTSL default territory for 2+2+2 configuration
2 additional DR RTSLs needed to get blocking
less than 2%
Territory located in BCCH TRX

2 RTSL dedicated territory per BTS for streaming
support
6 RTSL default territory for 4+4+4 configuration
No additional DR RTSLs or TRXs needed
RN20023EN14GLN1
RN20023EN14GLN1
46
Connectivity Capacity - EDAP Size

General EDAP size considerations:
At least full support for one MS with Multislot class 4 RTSL should be given (multislot capability may
be already considerred with default territory calculations). The minimum EDAP size can be set to
Min_EDAP_1 = MS_Multislot capability (= 4 TSLs)
If support for MCS-9 in all EGPRS territory timeslots of BTSs is required
Min_EDAP_2 = Max_Default_Territory_size_of one_BTS
Minimum EDAP size can be calculated from above input
Min_EDAP_size = Max(Min_EDAP_1, Min_EDAP_2)
If EDAP has more than one BTS attached, BTS multiplexing factor k can be taken into account if
EDAP peak load is estimated to exceed one BTSs territory size

BTS multiplexing factor can be estimated e.g. by
k = 2/(1+1/x), where
x= amount of BTSs in one EDAP
EDAP size can be estimated by
# of BTSs
1
2
3
k
1.0
1.3
1.5
EDAP_size = k * Min_EDAP_size
47
RN20023EN14GLN1
RN20023EN14GLN1
47
Connectivity Capacity - EDAP Size Considerations

2+2+2 configuration
MS Multislot capability = 4 RTSLs
Default territory size per BTS = 4 RTSLs
=> Min_EDAP_size = Max(4,4) = 4
# of BTSs
1
2
3
k
1.0
1.3
1.5
4+4+4 configuration
MS Multislot capability = 4 RTSLs
Default territory size per BTS = 6 RTSLs
=> Min_EDAP_size = Max(4,6) = 6
2+2+2
4.0
5.3
6.0
4+4+4
6.0
8.0
9.0
EDAP sizes with different configurations

Capacity for EDAPs in E1 for 2+2+2 is 16 and for 4+4+4 configuration 2 TSLs
2+2+2 configuration fits easily into existing E1
4+4+4 configuration does not fit into existing E1
Abis TSL allocation of 4+4+4 configuration needs redesign
48
RN20023EN14GLN1
RN20023EN14GLN1
48

4+4+4 configuration
Two options for Abis TSL allocation
TRXs are grouped by function so that all EDGE TRXs and EDAP are allocated to one E1 while the nonEDGE resources are mapped to other E1 frame. One EDAP is enough to serve all cells (BTS objects)
TRXs are grouped by cell so that two cells are allocated to one E1 and the third one to the second E1. In
this case EDAP is created for both groups.
Pros and cons.
TRXs grouped by function (the 1st E1: 2+2+2 & EDAP, the 2nd E1 2+2+2 non-EDGE)
+ maximum trunking gain of the EDAP can be achieved less total Abis capacity is required (#TSLs
for EDAP = 9)
+ smaller number of EDAPs saves PCU resources

- Special care needed to maintain and upgrade the configuration to keep the original slit.
TRXs grouped by cell (the 1st E1: 4+4 & EDAP1, the 2nd E1 4 & EDAP2)
+ Straightforward to maintain and upgrade

- trunking gain of the EDAPs is smaller or non more total Abis capacity is required (#TSLs for EDAP
= 8+6 = 14)
- bigger number of EDAPs needs more PCU resources
49
RN20023EN14GLN1
RN20023EN14GLN1
49

4+4+4 configuration
0
1 TCH0
TCH1
TCH2
TCH3
2 TCH4
TCH5
TCH6
TCH7
3 TCH0
TCH1
TCH2
TCH3
4 TCH4
TCH5
TCH6
TCH7
5 TCH0
TCH1
TCH2
TCH3
6 TCH4
TCH5
TCH6
TCH7
7 TCH0
TCH1
TCH2
TCH3
8 TCH4
TCH5
TCH6
TCH7
9 TCH0
TCH1
TCH2
TCH3
10 TCH4
TCH5
TCH6
TCH7
11 TCH0
TCH1
TCH2
TCH3
12 TCH4
TCH5
TCH6
TCH7
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28 TRXSIG1 TRXSIG2 TRXSIG3 TRXSIG4
29 TRXSIG5 TRXSIG6
30 BCFSIG
31
Q1-management
EGDE resources
50
0
1 TCH0
TCH1
TCH2
TCH3
2 TCH4
TCH5
TCH6
TCH7
3 TCH0
TCH1
TCH2
TCH3
4 TCH4
TCH5
TCH6
TCH7
5 TCH0
TCH1
TCH2
TCH3
6 TCH4
TCH5
TCH6
TCH7
7 TCH0
TCH1
TCH2
TCH3
8 TCH4
TCH5
TCH6
TCH7
9 TCH0
TCH1
TCH2
TCH3
10 TCH4
TCH5
TCH6
TCH7
11 TCH0
TCH1
TCH2
TCH3
12 TCH4
TCH5
TCH6
TCH7
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29 TRXSIG7 TRXSIG8
30 TRXSIG9TRXSIG10TRXSIG11TRXSIG12
31
Q1-management
0
1 TCH0
TCH1
TCH2
TCH3
2 TCH4
TCH5
TCH6
TCH7
3 TCH0
TCH1
TCH2
TCH3
4 TCH4
TCH5
TCH6
TCH7
5 TCH0
TCH1
TCH2
TCH3
6 TCH4
TCH5
TCH6
TCH7
7 TCH0
TCH1
TCH2
TCH3
8 TCH4
TCH5
TCH6
TCH7
9 TCH0
TCH1
TCH2
TCH3
10 TCH4
TCH5
TCH6
TCH7
11 TCH0
TCH1
TCH2
TCH3
12 TCH4
TCH5
TCH6
TCH7
13 TCH0
TCH1
TCH2
TCH3
14 TCH4
TCH5
TCH6
TCH7
15 TCH0
TCH1
TCH2
TCH3
16 TCH4
TCH5
TCH6
TCH7
17
18
19
20
21
22
23
24
25
26
27
30 BCFSIG
31
Q1-management
Non-EGDE resources
Cell A & B resources
0
1 TCH0
TCH1
TCH2
TCH3
2 TCH4
TCH5
TCH6
TCH7
3 TCH0
TCH1
TCH2
TCH3
4 TCH4
TCH5
TCH6
TCH7
5 TCH0
TCH1
TCH2
TCH3
6 TCH4
TCH5
TCH6
TCH7
7 TCH0
TCH1
TCH2
TCH3
8 TCH4
TCH5
TCH6
TCH7
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30 TRXSIG9TRXSIG10TRXSIG11TRXSIG12
31
Q1-management
Cell C resources
TRXs grouped by function requires
TRXs grouped by cells requires
one EDAP with 9 TSL.
two EDAPs with 8 TSL and 6 TSL
RN20023EN14GLN1
RN20023EN14GLN1
50
Connectivity Capacity - EDAP Summary

2+2+2 configuration
4+4+4 configuration
EDAP size 6 TSLs

EDAP fits in existing E1
EDAP size 9 TSLs

EDGE TRXs grouped for same E1
A new E1 needed for each 4+4+4
BCF -> need for 15 new E1s
51
RN20023EN14GLN1
RN20023EN14GLN1
51
Connectivity Capacity - PCU Planning

Considerations
Target is to calculate the optimal number of PCUs to serve the given network.
- PCU utilization 75%
- Recommended number of EDAPs per PCU1 is 1,2,4 or 8 (not needed for PCU2)
The optimal number of EDAPs and associated default RTSL is calculated for each PCU
configuration.
E.g. up to 5 EDAPs of size 6 TSL serving three cells each having default territory size 4 RTSL
can be allocated to PCU without exceeding the 75%.
To full fill the 1,2,4 and 8 recommendation (only with PCU1) the number of EDAPs would be 4
#EDAPs
EDAP size
#RTSL in territory
#cells (territories) per EDAP
#EDAP TSLs
#RTSLs
PCU Utilization
5
6
4
3
6
6
6
1
4
8
6
2
3
9
6
3
30
60
70%
36
36
70%
32
48
69%
27
54
63%
When using PCU

pooling feature, allocation
of DAPs and RTSL to
PCUs would be performed
by the system. At any time
rebalance command can
be given to redistribute the
Cells among the PCUs
Example is for PCU-T or PCU-B or PCU2-U or PCU2-D (256 Abis channels)

52
RN20023EN14GLN1
RN20023EN14GLN1
52
Connectivity Capacity - PCU Configurations and

Requirements
Table below lists possible PCU combinations:
BTS configuration
2+2+2 (12)
4+4+4 (18)
total PCU Abis load
PCU load%
EDAP size
6
0
9
4
4
216
84%
0
3
3
162
63%
1
3
4
198
77%
3
2
4
3
5
2
2
1
1
0
5
4
5
4
5
216
180 198 162 180
84% 70% 77% 63% 70%
4
0
4
144
56%
4+4+4 configurations -> 3 sites per PCU- load too low, 4 sites per PCU load too high
2+2+2 configuration -> 5 sites per PCU provides reasonable load
When considering total network, 15 (4+4+4) and 25 (2+2+2) configurations one possibility is to
have
5 PCUs with 1 (2+2+2) and 3 (4+4+4) configurations
4 PCUs with 5 (2+2+2) configurations
Example is for PCU-T or PCU-B or PCU2-U or PCU2-D (256 Abis channels)
53
RN20023EN14GLN1
RN20023EN14GLN1
53
Connectivity Capacity - Gb Link Size

Requirements
Gb over FR:
Gb EDGE dimensioning based on EDAP (K = 5/4) (can be seen as absolute minimum
requirement)
Gb link size can be calculated from maximum EDAP size of PCU
Gb_link_size=5/4*Max_EDAP_size as minimum
Inputs from PCU planning
5 PCUs with 1 EDAP of 6 TSLs and 3 EDAPs of 9 TSLs
4 PCUs with EDAP of 6 TSLs
Gb link sizes / PCU
Gb_link1 = 5/4*9 = 11.25 TSLs ~ 11 TSLs
Gb_link2 = 5/4*6 = 7.5 TSLs ~ 8 TSLs
Example here: Gb EDGE dimensioning based on EDAP not on traffic figures!
54
RN20023EN14GLN1
RN20023EN14GLN1
54
Connectivity Capacity - Gb Links

When Gb links are combined into E1s maximum 31 TSLs can be used
#PCU
5
4
Gb
links
11
8
3
0
33
2
0
22
2
1
30
1
2
27
2
2
38
Table above shows that 1 E1 can fit well either

2 Gb links of 11 TSLs and one link of 8 TSL
1 Gb link of 11 TSL and two links of 8 TSLs
9 PCUs can therefore be fitted into 3 E1 links
55
RN20023EN14GLN1
RN20023EN14GLN1
55
Connectivity Capacity - Summary

DR RTSLs
PCUs
E1s for Abis
E1s for Gb
150
9
15
3
Configuration
2+2+2
4+4+4
CDED
2
2
# of PCUs BTS Configurations

5
3*(4+4+4) 1*(2+2+2)
4
5*(2+2+2)
56
CDEF
4
6
EDAP
6
9
Abis util. Gb Link

77%
11
70%
8
RN20023EN14GLN1
RN20023EN14GLN1
56

Mobility Planning
57
RN20023EN14GLN1
RN20023EN14GLN1
57
Mobility Planning
The aim of mobility planning is to reduce the cell outage time during cell re-selection.
Cell outage can be reduced by
Providing enough signaling capacity for cell re-selection (the RACH, PCH, AGCH and
SDCCH channel are not limiting the signaling flow)
Allocating BCFs to PCUs properly (the important neighbors are allocated to the same PCU)
Allocating LA/RA borders properly
Using Network Assisted Cell Change (NACC) feature
-Intra PCU, intra SGSN, intra PAPU
-Inter PCU, intra SGSN, intra PAPU
-Inter PCU, intra SGSN, inter PAPU
-Inter PCU, inter SGSN, inter PAPU
-Inter PCU, inter PLMN
Different Test cases
-Same RA
same LA
-Different RA same LA
-Different RA different LA
58
RN20023EN14GLN1
RN20023EN14GLN1
58
Mobility Planning
Outage measurements: Trace example:
Event name
20:42.0 PACCH "EGPRS_PACKET_DOWNLINK_ACK/NACK"
Layer 3 Downlink
20:42.0
BCCH
Layer 3 Downlink
20:42.0
BCCH "SYSTEM_INFORMATION_TYPE_2"
Layer 3 Downlink
20:42.0
Layer 3 Downlink
20:42.0
20:42.8
Layer 3 Downlink
20:42.8
20:42.6
Cell Reselection
"SYSTEM_INFORMATION_TYPE_1"
Layer 3 Downlink
from CI 5032 to CI 5033
Layer 3 Downlink
20:43.1
Layer 3 Uplink
20:43.1
RACH "CHANNEL_REQUEST"
Layer 3 Downlink
20:43.2
CCCH "IMMEDIATE_ASSIGNMENT"
Layer 3 Downlink
20:43.2
CCCH "PAGING_REQUEST_TYPE_1"
Layer 3 Downlink
20:43.2
Layer 3 Downlink
20:43.3
Layer 3 Downlink
20:43.3
Data Outage
RLC/MAC Uplink
20:43.8 PACCH "PACKET_RESOURCE_REQUEST"
RLC/MAC Downlink
20:44.0 PACCH "PACKET_UPLINK_ASSIGNMENT"
RLC/MAC Downlink
20:44.0 PACCH "PACKET_DOWNLINK_DUMMY_CONTROL_BLOCK"
RLC/MAC Downlink
RLC/MAC Downlink
RLC/MAC Downlink
20:44.2 PACCH "PACKET_DOWNLINK_ASSIGNMENT"
RLC/MAC Uplink
20:44.3 PACCH "EGPRS_PACKET_DOWNLINK_ACK/NACK"
Cell Outage
20:43.8
Layer 3 Downlink
59
Time Channel Message
RLC/MAC Uplink
RN20023EN14GLN1
RN20023EN14GLN1
59
Cell Outage Time witin one PCU

Outage measurements:
-Cell Outage (MS - PCU) is measured between the first BCCH observation and Packet
Uplink Assignment
-Data Outage (MS - SGSN) is measured between the first BCCH observation and
Packet Downlink Assignment
Measurement examples:
From EGPRS PACKET DOWNLINK ACK/NACK
till Packet Uplink Assign. (ms) till Packet Downlink Assign. (ms)
2.07
3.07
2.09
2.10
2.09
2.11
2.10
2.09
2.11
2.10
6.00
2.12
2.094
2.09
2.14
2.07
2.10
2.10
2.37
60
2.341
3.349
2.354
2.358
2.375
2.393
2.658
2.355
2.395
2.38
6.254
2.379
2.629
2.631
2.7
4.011
2.379
2.385
2.80
Diff. Between BSS and

full cell-outage (ms)
0.27
0.28
0.26
0.26
0.28
0.28
0.56
0.26
0.28
0.28
0.26
0.26
0.54
0.54
0.56
1.94
0.28
0.28
0.43
Big variations can be

seen, values are only
examples
RN20023EN14GLN1
RN20023EN14GLN1
60
Cell Outage Time with LAU/RAU change

from 5691 to 5753
"CHANNEL_REQUEST"
"IMMEDIATE_ASSIGNMENT"
"LOCATION_UPDATING_REQUEST"
"MEASUREMENT_REPORT"
"CLASSMARK_CHANGE"
"CIPHERING_MODE_COMMAND"
"GPRS_SUSPENSION_REQUEST"
"CIPHERING_MODE_COMPLETE"
"IDENTITY_REQUEST"
"IDENTITY_RESPONSE"
"LOCATION_UPDATING_ACCEPT"
"MM_INFORMATION"
"CHANNEL_RELEASE"
Outage measurements as seen by

MS:
Cell Outage (MS - PCU) is measured
between the first BCCH observation
and Packet Uplink Assignment with LA
and RA Update procedure
Data Outage (MS - SGSN) is
measured between the first BCCH
observation and Packet Downlink
ACK/NACK after Routing Area Update
Complete
"ROUTING_AREA_UPDATE_REQUEST"
"PACKET_RESOURCE_REQUEST"
"PACKET_UPLINK_ASSIGNMENT"
"PACKET_DOWNLINK_ASSIGNMENT"
"ROUTING_AREA_UPDATE_ACCEPT"
"ROUTING_AREA_UPDATE_COMPLETE"
"EGPRS_PACKET_DOWNLINK_ACK/NACK"
8:44:17.886 PACCH
8:44:18.950 PDTCH
8:44:18.964 PDTCH
8:44:19.119 PACCH
Message
8:44:16.258 PDTCH
8:44:17.401 PACCH
8:44:17.607 PACCH
61
Layer 3 Downlink
Layer 3 Uplink
RLC/MAC Uplink
RACH
CCCH
SDCCH
SACCH
SACCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SACCH
SDCCH
SDCCH
SACCH
SDCCH
SACCH
SDCCH
RLC/MAC Downlink
8:44:11.997
8:44:12.101
8:44:12.313
8:44:12.353
8:44:12.388
8:44:12.548
8:44:12.764
8:44:12.784
8:44:13.020
8:44:13.224
8:44:13.350
8:44:13.490
8:44:13.697
8:44:13.799
8:44:14.168
8:44:14.284
8:44:14.399
Layer 3 Uplink
RLC/MAC Uplink
RLC/MAC Downlink
8:44:10.797 BCCH
8:44:10.906
8:44:11.018 BCCH
Layer 3 Uplink
Layer 3 Downlink
Layer 3 Uplink
Layer 3 Downlink
Layer 3 Uplink
Layer 3 Uplink
Layer 3 Downlink
Layer 3 Uplink
Layer 3 Uplink
Layer 3 Downlink
Layer 3 Uplink
Layer 3 Uplink
Layer 3 Downlink
Layer 3 Uplink
Layer 3 Downlink
Layer 3 Uplink
Layer 3 Downlink
8:44:05.801 BCCH
Layer 3 Downlink
Cell Reselection
Layer 3 Downlink
Channel
Layer 3 Downlink
Time
Event name
RN20023EN14GLN1
RN20023EN14GLN1
61
PCU Allocation Plan

The proper allocation of the cells among PCUs can help to maximize the number of intra PCU
cell re-selections, which is the most stable cell re-selection event.
RLC/MAC layer: The intra PCU cell re-selection takes less time compared with inter PCU cell
reselection
LLC layer: In case of intra PCU cell re-selection the un-transferred data is moved to new cell
(BVCI) and the transfer can be continued on new cell without packet loss on higher layer,
while in case of inter PCU cell re-selection the un-transferred data is not moved to new cell
(BVCI).
The following rules can be followed:
The cells of one BCF should be connected to the same PCU

The neighbor relations with high re-selection traffic should be connected to the same PCU
The neighbor relations in very bad signal and quality environment should be connected to the
same PCU
NACC* and NCCR can be used to enhance the performance of cell reselections, because
offsets can be defined avoiding too many inter PCU cell reselections for example
(* NACC is working inside BSCs only)
62
RN20023EN14GLN1
RN20023EN14GLN1
62
LA/RA Design Radio Aspects

Radio Aspect of LA/RA Design
too big LA/RA will increase the paging, while too small LA/RA will increase the amount of
LA/RA Updates. So the balance should be found between too big and too small LA/RAs.
a bad LA/RA border design can significantly increase the amount of signaling what can lead
to an increase of the cell-reselection outage on the LA/RA border.
The LA/RA border should be moved from those areas where the normal CSW and PSW
traffic is very high.
The combined RAU (NMO I with Gs) is shorter compared to NMO II
A class B MS (and class A MS without DTM support) has to suspend GPRS services while in
dedicated mode. Once the dedicated connection is finished, GPRS services have to be
resumed. This can be done by an RA update. Since S11.5 the Resumption is provided by the
BSC without need for RA update.
63
RN20023EN14GLN1
RN20023EN14GLN1
63

03 RN20023EN14GLN1 EGPRS BSS Dimensioning and Planning

Uploaded by

Copyright:

Available Formats

03 RN20023EN14GLN1 EGPRS BSS Dimensioning and Planning

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

03 RN20023EN14GLN1 EGPRS BSS Dimensioning and Planning

Uploaded by

Copyright:

Available Formats

(E)GPRS BSS Dimensioning and Planning

(E) GPRS BSS Dimensioning and

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Describe the Coverage Planning and Link Budget process

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Network Dimensioning and Planning - Content

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

(E)GPRS Coverage Planning and Link Budget

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

(E)GPRS Coverage Planning and Link Budget

MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Link Budget Calculation Voice/ (E)GPRS

Intelligent Uplink Diversity (IUD)

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

(E)GPRS Link Budget Example

S = BTS noise Power + Es/No

Addit fast fading marg (voice+CSdata)

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

(E)GPRS Link Budget

Cell Range For Indoor and Outdoor

Cell Range (km):

Coverage Threshold (dBV/m):

Cell Area (km2)

Nokia Siemens Networks

BPL Building Penetration Loss

(E)GPRS BSS Dimensioning and Planning

(E)GPRS Link Budget

Example for MS (DL) for

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Frequency Planning: Timeslot capacity

Non-optimum protocols can

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Frequency Planning: GPRS

Through-put for 1 Timeslot

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Frequency Planning EGPRS

-The proper frequency plan of GSM network

Impairments are signal distortions

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

Nokia Siemens Networks

(E)GPRS BSS Dimensioning and Planning

EGPRS and GPRS Coverage Comparison

150.1 152.6 154.8

DL Throughput per TSL [Kbps]

Pathloss distance [km]

Nokia Siemens Networks