1 NOKIA Impact of EDGE on the BSS.

PPT / MRi
Company Confidential
Impact of EDGE on the BSS
Manuel Rios
[email protected]
972 374 0646
2 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Introduction :
Name :
Position :
Past experience :
Expectation from EDGE training:
3 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Contents and Preliminary Agenda
Impact of EDGE in the Base Station Subsystem (BSS)
The Abis interface
The Dynamic Abis feature
Dynamic Abis pool modeling & dimensioning
Abis branching tables with dynamic Abis pool
PCU dimensioning with EDGE
Gb interface considerations
Conclusions
4 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
EDGE = Enhanced Data Rates for GSM (or Global) Evolution
Enhancement results from introduction of new
modulation (8-PSK) +channel coding schemes
EGPRS (Enhanced GPRS): packet switched channels/ services
New modulation triples the nominal bit rates
Update of the GSM Standard towards 3rd generation
networks/mobiles
What is EDGE?
5 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Impact of EDGE in GSM/GPRS network
8-PSK coverage
EDGE capable TRX,
GSM compatible
GMSK coverage
A-bis
BTS
BTS
MSC
Gn
GGSN
EDGE capable
terminal,
GSM compatible
More capacity in interfaces
to support higher data usage
Gb
BSC
A
SGSN
EDGE functionality in
the network elements
6 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
The PCU in the BSC
7 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Impact of EDGE in the BSS
In the air interface, higher rates are achieved through the use 8-PSK.
Achievable transmission rates are in the order of 59.2 Kbit/s per Radio
Timeslot (RTSL).
Higher Capacity is needed in the Abis interface
The Dynamic Abis Pool (EDAP) is a shared extra Abis resource for EGPRS
channels and TRXs.
The increased data traffic volume and the use of EDAP puts additional
requirements of PCU and Gb capacity
Abis
BSC
SGSN
BTS
Um Gb
PCU
Impact
8 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
The Abis Interface
The Abis interface is also used for GPRS services.
In a traditional GSM/GPRS system, each TRX channel is mapped statically
to Abis PCM timeslots.
Abis
BSC
SGSN BTS
Um Gb
PCU
The Abis interface is situated between the BSC and the Base Station sites
9 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
GSM/GPRS Abis Interface
PCM frame structure
The figure shows the PCM frame
structure for the T1
Each frame of 192 payload bits
includes 8 bits for each 64-kbps
timeslot or 2 bits for each 16-kbps
sub-timeslot.
Each 2 bits sub-channel is going to
be called an Abis-channel
The sub-timeslots of 160 PCM frames
form a TRAU or PCU frame that has
320 bits and includes the data for a
radio block of 20 ms.
TS Bits used in timeslots
1 2 3 4 5 6 7 8
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
6
4
-
k
b
i
t
/
s

t
i
m
e
s
l
o
t
s
1
24
192-bit
PCM frame,
repeat rate
8000 Hz
10 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Static (traditional)Abisallocation principle
One RF traffic channel reserves a 2
bit 16 Kbit/s Abis channel in the
PCM
Two entire 64Kbit/s timeslots per
each TRX.
One 16 kbit/s, 32 Kbit/s or 64 Kbit/s
LAPD signaling channel per each TRX.
These can be allocated in , or
one (1) 64 Kbit/s timeslot.
One 16 kbit/s, 32 Kbit/s or 64 Kbit/s
LAPD signaling channel per each BCF.
These can be allocated in , or
one (1) 64 Kbit/s timeslot
TS Bits used in timeslots
1 2 3 4 5 6 7 8
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24 Reserved
TRX 2
TRX 5
TRX 6
TRX 9
TRX 10
BCFSIG16K:BCF1 TRXSIG16K:1:2
TRXSIG16K:1:1 TRXSIG16K:1:6
TRXSIG16K:1:5 TRXSIG16K:1:10
TRXSIG16K:1:9
TCH:1:1:5 TCH:1:1:6 TCH:1:1:7 TCH:1:1:8
TCH:1:1:1 TCH:1:1:2 TCH:1:1:3 TCH:1:1:4
11 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
New requirements for EDGE
In the air interface, higher rates are achieved through the use 8-
PSK. Achievable transmission rates are in the order of 59.2 Kbit/s per
Radio Timeslot (RTSL).
Higher data rates dont fit in 16 kbit/s A-bis channels.
32, 48, 64 or 80 kbit/s Abis links are needed
Fixed Abis allocation of such links would be expensive and
would lack flexibility.
The Dynamic Abis Pool is a shared extra Abis resource for EGPRS
channels and TRXs.
The Dynamic Abis functionality allocates Abis transmission capacity
to cells when needed instead of reserving full fixed transmission link
per TRX.
12 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Dynamic Abis
PCU frame types
PCU data frame
used when TRX not in EDGE mode
only able to carry CS-1 and CS-2
PCU master data frame
used when TRX is in EDGE mode
carries CS-1 or MCS-1 on its own and CS-2...CS-4
and MCS-2...MCS-9 with the help of slave frame(s)
includes pointers to the slave frames
PCU slave data frame
carries additional data that does not fit in PCU
master data frames
MCS-1 M
M
M
M
M
M
M
M
M
S
S
S
CS-4
CS-3
CS-2
CS-1
MCS-2
MCS-3
MCS-4
MCS-5
MCS-6
MCS-7
MCS-8
MCS-9
S
S
S
S
S
S
S
S
S
M
M
M
M
S
S
S
S
S
S
S
S
CS-2
CS-1
D
D
non-EDGE TRX
EDGE TRX
D
M
S
PCU data frame
PCU master data frame
PCU slave data frame
+
+
+
+
+
+
+
+
+
+
+
retrans M
13 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Fixed channels and EDAP
For each GPRS radio timeslot on each
EDGE TRX, one fixed 16-kbps channel is
allocated on the Abisfor the transfer
for PCU master data frames.
PCU slave data frames are allocated in
a common pool, the EDAP (EDGE
Dynamic AbisPool).
We are still going to make a static
allocation of 16 kbit/s per TCH, (used
for voice or data)
In a PSD call, this sub TS is called as a
master Abischannel and if required
system can allocate up to 4 extra slave
Abissub-timeslots for same master
from dynamic pool
Dynamic Abis (2)
TS Bits used in timeslots
1 2 3 4 5 6 7 8
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Master
Slave
Reserved
Dynamic Abis Pool
14 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Dynamic Abispointers
Each downlink PCU master data frame
includes a pointer to downlink slave
frames on the same block period, and
a pointer to uplink slave frames on the
next block period.
M M
S S S
S S S S
downlink PCM
frames during
one block period
uplink PCM
frames during
next block period
Dynamic Abis (3)
15 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Transmission requirement for EGPRS coding schemes
in Abis -interface
Abis PCM allocation (fixed +
pool)
Coding Scheme Bit rate (bps)
CS-1 8,000
CS-2 12,000
CS-3 14,400
CS-4 20,000
MCS-1 8,800
MCS-2 11,200
MCS-3 14,800
MCS-4 17,600
MCS-5 22,400
MCS-6 29,600
MCS-7 44,800
MCS-8 54,400
MCS-9 59,200
When EDGE is activated, CS-2 uses the pool
Slave Groups
16 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Management of the Dynamic Abis pool (1)
The Dynamic Abis is managed by the PCU (i.e. resource allocation and
scheduling of EDAP channels)
The management is necessary because of the EDAP is a limited resource
to be shared between EDGE-TRXs and EGPRS channels
The management functions include:
EDAP based EGPRS scheduling for EDGE TRXs.
Resource Management
In the DL the MCS can be limited for RTSLsif not enough EDAP
resources are available.
In the UL a transmission turn will be skipped for RTSLs if not
EDAP resources are available.
Pointer re-transmission used for EGPRS retransmissions to
optimize Abis.
17 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Management of the Dynamic Abis pool (2)
The pool does not represent a hard blocking bottleneck. A pool not big
enough to assign slave EDAP channels to every RTSL as requested reduces
the MCS scheme granted for transmission.
In practice PCU shares capacity evenly with users who will experience
rate reduction.
18 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
DL Data Scheduling Example adequate resources
available
Requests
Grants
- - CS-2 MCS-9 MCS-7 MCS-1 MCS-7
RTSL
TRX 1
0 1 2 3 4 5 6 7
- - CS-2 MCS-9 MCS-7 MCS-1 MCS-7
There are enough EDAP resources to handle adequately all the data transfers
and MCS requests. (e.g PS Active EGPRS ch. =< EDAP PCM TSL)
P
C
M

T
S
L
PCM subTSL
1 2 3 4
8
11
10
9
5
2
5
-
5
-
-
-
7 7 7 -
4 4 4 4
12
- - - -
19 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
4
Because EDAP is a shared resource between a higher number of EGPRS TSL it
is possible to encounter the situation where there are not enough EDAP
resources to handle adequately all the data transfers (e.g PS Active EGPRS ch >
EDAP PCM TSL)
DL Data Scheduling Example adequate resources not
available
Grants
RTSL
Requests
TRX 1
0 1 2 3 4 5 6 7
- - CS-2 MCS-5 MCS-9 MCS-8 MCS-1 MCS-7
- - CS-2 MCS-5 MCS-7 MCS-7 MCS-1 MCS-6
PCU-TRX 0
5
3
5 5
7
4 4 -
P
C
M

T
S
L
PCM subTSL
1 2 3 4
11
12
10
- 7 2
20 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Abis Pool Features and Limitations
The Dynamic pool (EDAP) is used only for PSD
The maximum pool size is of 12 PCM timeslots
DAP can be shared for multiple TRXs in the same base station cabinet
Only EDGE TRXs can use EDAP
Several pools can be created in to the same PCM.
The traffic and signaling timeslots including the dynamic pool for each TRX
must be located in the same T1 frame and cant be distributed across different
T1s.
All timeslots that make the pool should be contigous
The actual size and number of DAPs needed for a site depend on the amount
of traffic that is expected to be handled by the siteas well as the site
configuration.
21 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
How big should EDAP be?
EDAP is a common resource shared dynamically among several
TRXs:
More data traffic More EGPRS active channels Larger pool
needed.
Different MCS make use of the pool differently
Some savings are achieved thanks to pointer retransmissions
What are the performance targets for the pool? How often can
we tolerate that the pool cant grant the requested MCS? (e.g.
Target below 2% of the time)
22 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
EDAP Modeling (1)
In its basic form, the EDAP can be modeled by understanding the rate at which
RTSL will be requesting EDAP resources. Rate =RTLS data utilization
TRX 1
TS TS TS TS TS TS
TS
TS PBCCH BCCH
TS
TS
EGPRS TSL
Voice
TRX 2
TS TS TS TS TS TS TS TS PBCCH BCCH
P
C
M

T
S
L
PCM subTSL
1 2 3 4
11
10
9
- - - -
- - - -
- - - -
4 RTSL contending for 3 PCM TSL
23 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
EDAP Modeling (2)
When we know the pool size and how many air-timeslots are
competing of the usage of the pool we can calculate the Abis
overflow value. Pool overflow can be calculated using the
binomial distribution.
,where x is the number of successes in trials, p is theutilization of
the slave (E)GPRS channels (CS-1, CS-2, MCS-1 and re-transmission
are not included in it), n are the EGPRS RF-timeslots in use.
Probability of pool overflow (blocking) will be:
B(n,N,p)=
, where N is the available pool size.
x n x
p p
x
n
x P

= ) 1 ( ) (

+ =
n
N x
x P
1
) (
24 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
EDAP Modeling (3)
Example:
RTSL utilization
3 EGPRSRTSLs (Dedicated + Default territory)
Data Traffic = 1.5 Data Erlangs traffic
RTSL utilization = 30% (Channel_utilization = Erlang_PS /
Available_TLS)
3 sectors X 3 EGPRS channels =9 EGPRS channels
EDAP =5 PCM TSLs
9 EGPRS channels contending for 5 PCM TSLs
TRX 2
TRX 1
TS TS TS TS TS TS
TS TS T TS TS TS TS TS S SDCCH BCCH
TS TS
TS
TS
Dedicated EGPRS TSL
Default territory
EGPRS TSL
25 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
97.5%
Probability of not having enough DL EDAP resources
Probability of pool not suffering overflow
Pool slave utilization
PCM RTSL 0.05 0.1 0.15 0.2 0.25 0.3 0.35 0.4 0.45 0.5 0.55 0.6 0.65 0.7 0.75 0.8
4 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
4 5 1 1 1 1 0.999 0.998 0.995 0.99 0.982 0.969 0.95 0.922 0.884 0.832 0.763 0.672
4 6 1 1 1 0.998 0.995 0.989 0.978 0.959 0.931 0.891 0.836 0.767 0.681 0.58 0.466 0.345
4 7 1 1 0.999 0.995 0.987 0.971 0.944 0.904 0.847 0.773 0.684 0.58 0.468 0.353 0.244 0.148
4 8 1 1 0.997 0.99 0.973 0.942 0.894 0.826 0.74 0.637 0.523 0.406 0.294 0.194 0.114 0.056
4 9 1 0.999 0.994 0.98 0.951 0.901 0.828 0.733 0.621 0.5 0.379 0.267 0.172 0.099 0.049 0.02
5 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
5 6 1 1 1 1 1 0.999 0.998 0.996 0.992 0.984 0.972 0.953 0.925 0.882 0.822 0.738
5 7 1 1 1 1 0.999 0.996 0.991 0.981 0.964 0.938 0.898 0.841 0.766 0.671 0.555 0.423
5 8 1 1 1 0.999 0.996 0.989 0.975 0.95 0.912 0.855 0.78 0.685 0.572 0.448 0.321 0.203
5 9 1 1 0.999 0.997 0.99 0.975 0.946 0.901 0.834 0.746 0.639 0.517 0.391 0.27 0.166 0.086
5 10 1 1 0.999 0.994 0.98 0.953 0.905 0.834 0.738 0.623 0.496 0.367 0.249 0.15 0.078 0.033
5 11 1 1 0.997 0.988 0.966 0.922 0.851 0.753 0.633 0.5 0.367 0.247 0.149 0.078 0.034 0.012
5 12 1 0.999 0.995 0.981 0.946 0.882 0.787 0.665 0.527 0.387 0.261 0.158 0.085 0.039 0.014 0.004
MCS-9
26 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
EDAP MCS adjustment
MCS-7 44,800
MCS-7 coding scheme uses EDAP of the EDAP PCM TSL
(3*16kbit/s sub-channels)
For example:
EDAP pool of size 4 PCM timeslots is big enough to accommodate
4*4/3 = 5 MCS-7 calls
P
C
M

T
S
L
PCM subTSL
1 2 3 4
8
11
10
9
1
5
1
5
1
5
2
6
3 4 4 4
2 2 3 3
27 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
EDAP Modeling (3)
Example:
RTSL utilization
3 EGPRSRTSLs (Dedicated + Default territory)
Data Traffic = 1.5 Data Erlangs traffic
RTSL utilization = 30% (Channel_utilization = Erlang_PS /
Available_TLS)
3 sectors X 3 EGPRS channels =9 EGPRS channels
EDAP =5 PCM TSLs
9 EGPRS channels contending for 5 PCM TSLs
Avg. MCS used in the network: MCS-7
TRX 2
TRX 1
TS TS TS TS TS TS
TS TS T TS TS TS TS TS S SDCCH BCCH
TS TS
TS
TS
Dedicated EGPRS TSL
Default territory
EGPRS TSL
28 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
99.6%
Probability of not having enough DL EDAP resources
7 3 Pool slave utilization
PCM TSL RTSL 0.05 0.1 0.15 0.2 0.25 0.3 0.35 0.4 0.45 0.5 0.55 0.6 0.65 0.7 0.75 0.8
4 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
4 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
4 6 1 1 1 1 1 0.999 0.998 0.996 0.992 0.984 0.972 0.953 0.925 0.882 0.822 0.738
4 7 1 1 1 1 0.999 0.996 0.991 0.981 0.964 0.938 0.898 0.841 0.766 0.671 0.555 0.423
4 8 1 1 1 0.999 0.996 0.989 0.975 0.95 0.912 0.855 0.78 0.685 0.572 0.448 0.321 0.203
4 9 1 1 0.999 0.997 0.99 0.975 0.946 0.901 0.834 0.746 0.639 0.517 0.391 0.27 0.166 0.086
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
5 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
5 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
5 7 1 1 1 1 1 1 0.999 0.998 0.996 0.992 0.985 0.972 0.951 0.918 0.867 0.79
5 8 1 1 1 1 1 0.999 0.996 0.991 0.982 0.965 0.937 0.894 0.831 0.745 0.633 0.497
5 9 1 1 1 1 0.999 0.996 0.989 0.975 0.95 0.91 0.85 0.768 0.663 0.537 0.399 0.262
5 10 1 1 1 0.999 0.996 0.989 0.974 0.945 0.898 0.828 0.734 0.618 0.486 0.35 0.224 0.121
5 11 1 1 1 0.998 0.992 0.978 0.95 0.901 0.826 0.726 0.603 0.467 0.332 0.21 0.115 0.05
5 12 1 1 0.999 0.996 0.986 0.961 0.915 0.842 0.739 0.613 0.473 0.335 0.213 0.118 0.054 0.019
MCS7
MCS-7
29 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Dynamic Abis counters
The counters of Dynamic Abis Measurement give information
about the usage of Dynamic Abis Pools.
TOTAL NUMBER OF PCM SUB-TSLs IN EDAP
AVERAGE DL EDAP USAGE AVERAGE UL EDAP USAGE
PEAK DL EDAP USAGE PEAK UL EDAP USAGE
UL TBFs WITHOUT EDAP RESOURCES DL TBFs WITHOUT EDAP RESOURCES
DL TBFs WITH INADEQUATE EDAP
RESOURCES
Approximation to pool overflow
30 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
How can I plan the branching tables with EDAP
1. Understand the site configuration (TRXs, Cabinets, EDGE TRXs)
2. Identify the EDGE TRXs that need to be connected to a DAP (GTRX=Y)
3. Remember:
DAP can be shared for multiple TRXs in the same base station cabinet
The traffic and signaling timeslots including the dynamic pool for
each TRX must be located in the same T1 frame and cant be
distributed across different T1s.
All timeslots that make the pool should be contigous
4. A ball park number:
Depending on the pool size, we may be able to transport about 6 TRXs
with a pool and signaling in the same T1
31 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
2+2+2 site structure
24V
Cabinet # 1
TRX#1
TRX#2 A: 1900*
TRX#5
TRX#6 B: 1900*
TRX#9
TRX#10 C: 1900*
1900 TRX
Transmission Unit:
FXC E1/T1
Cabinet 1
T1-1
32 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
2+2+2 site structure (2)
Name: E222A
Configuration of BTSs: Timeslot allocation:
BTS: Actual config: Forecasted config: BCF sig: TS Bits used in timeslots
BCF 1 2,2,2 16k 1 2 3 4 5 6 7 8
1
2
3
TRX numbering: 4
TRX numbers: 5
BTS: Segment BTS actual: 6
BCF 1 1 1,2 7
2 5,6 8
3 9,10 9
10
11
12
13
Legend: 14
cross-connect TimeSlot 15
unused TimeSlot 16
17
18
TRX Legend: TRX A-B 19
A: BCF # 20
B: TRX # 21
22
BCFSIG Legend: BCFSIG:X:Y 23
TRXSIG Legend: TRXSIG:X:Y:Z 24
X: Bit Rate
Y: BCF # EDAP Pool Cabinet TRX # Band
Z: TRX # 1 1 1,2,5,6,9,10 1900
TRXSIG16K:1:5 TRXSIG16K:1:6
Reserved
TRXSIG16K:1:9 TRXSIG16K:1:10
T1-1
TRX 1-9
EDAP Pool 1
TRX 1-1
TRX 1-2
TRX 1-10
TRX 1-6
TRX 1-5
TRXSIG16K:1:1 TRXSIG16K:1:2
BCFSIG16K:1
TRXs connected to EDAP
33 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
5+5+5 site structure
Cell A
SEG 1
BTS1
Cell C
SEG 3
BTS 3
Cell C
SEG 2
BTS 2
Cabinet 1 Cabinet 2
Cell Cell Ch Cabinet TRX Cell Cell Ch Cabinet TRX
A 1 1 C 1 1
A 2 2 C 2 2
A 3 3 C 3 3
A 4 4 C 4 4
A 5 5 C 5 5
B 1 7
B 2 8
B 3 9
B 4 10
B 5 11
34 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
5+5+5 site structure (2)
Timeslot allocation: Timeslot allocation:
TS Bits used in timeslots TS Bits used in timeslots
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
20 20
21 21
22 22
23 23
24 24
EDAP Pool Cabinet TRX # Band
1 1 1,2,3,7,8,91900/850
2 2 1,2,3,4 1900/850
EDAP 2
T1-1
TRX 1-3
TRX 1-8
TRX 1-7
TRX 1-2
Reserved for Cingular
TRXSIG16K:1:8
TRXSIG16K:1:2
BCFSIG16K:BCF1
TRX 1-9
TRX 1-1
TRXSIG16K:1:1
TRXSIG16K:1:3
TRXSIG16K:1:7
TRXSIG16K:1:9 TRXSIG16K:1:5
EDAP 1
T1-2
TRX 2-1
TRX 2-2
TRX 2-3
TRX 2-4
TRX 1-4
TRX 1-10
TRX 1-11
TRXSIG16K:1:10 TRXSIG16K:2:5
TRXSIG16K:1:11
TRXSIG16K:2:4 TRXSIG16K:1:4
Reserved for Cingular
BCFSIG16K:BCF2 TRXSIG16K:2:1
TRXSIG16K:2:2 TRXSIG16K:2:3
TRX 2-5 TRX 1-5
TRXs connected to EDAP
35 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
5+5+5 site structure (3)
Transmission Unit:
FXC E1/T1
T1-1
To BSC
T1 A-B
Cabinet 1
Cabinet 2
To BSC
T1-2
36 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
PCU Dimensioning - 1
Each BSC can now have up to 16 PCUs installed.
00253244
LEGEND:
1.
Extension
4th SW64B
Plug in Unit
2.
Extensions
GPRS/EDGE
3.
Cartridges 8 & 9
GSWB 192-> 256
2nd PCU cards, 8+1
EXTRA 2*ET5Cs
2nd PCU for GPRS/EDGE
GSWB extension kit (192->256 PCMs)
External PCM extensions to increase
PCMs in BSC2i from 112 to 144, ET5Cs 8 &
9, requires GSWB (256)
PSA20
PSFP
PSA20
PSFP
S
W
1
C
M
C
M
U
S
D
3
C
-
S
O
M
U
M
C
M
U
B
C
S
U
B
C
S
U
B
C
S
U
B
C
S
U
B
C
S
U
B
C
S
U
E
T
5
C
E
T
5
C
E
T
5
C
E
T
5
C
E
T
5
C
E
T
5
C
B
C
S
U
B
C
S
U
B
C
S
U
S
W
1
C
C
L
O
C
C
L
A
C
E
T
5
C
E
T
5
C
E
T
5
C
1
2
2
2
2
2
2
2
3 3
2
2
1
37 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
PCU Dimensioning - 2
The PCUs have the following dimensioning criteria
PCU connectivity towards the Abis interface supports 256 Abis channels,
including (including PBCCH/PCCCH +default GPRS +EDAP channels and
additional GPRS territory)
PCU supports 128 Abis channels, including: PBCCH/PCCCH +default GPRS +
and additional GPRS territory
PCU connectivity towards the Gb interface is 31*64 Kbit/s channels. Data
throughput up to full Gb capacity utilization (31*64K =1984 Kbit/s) is
supported.
38 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
PCU Dimensioning - 3
PCU supports up to 128 TRXs
64 BTS (Note that BTS is defined as a group of TRXs sharing a same
configuration, a sector which is now defined as a SEGMENT, starting in
S.10)
The theoretical maximum number of TRXs per DAP is 20. However,
sinceTRXs using DAP resources must be allocated to the sameAbis
ETPCM line with EDAP, the maximum TRX count for a DAP about 7-8 in
the ANSI environment.
The serving PCU must be the same for all theTRXs under one
segment
39 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
PCU Dimensioning - 4
Internal PCU restrictions:
A PCU has 16 DSP cores. One DSP core can handle only one EDAP, but
one EDAP can be shared by several DSP cores. The maximum number of
EDAPs per PCU is 16.
One DSP core can handle 020 channels (16 kbit/s) including active
EDAP channels, EGPRS channels, GPRS channels and PBCCH/PCCCHs.
Some possible but bad configuration examples:
One EDAP containing 12 TSLs and 15EDAPs containing 2 TSLs each are
configured to one PCU. The first EDAP is handled in one DSP core, and
the EDAP has 48 channels. Only 16 EDAP channels of the first EDAP can
be used by 4 EGPRS channels.
16EDAPs that each contain 3 TSLs are configured to a PCU. The TRXs
that are connected to one EDAP have 20 default GPRS channels (total
count). No single EDAP channel can be used and only MCS 1 or CS 1
traffic is possible in theTRXs.
40 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
How many PCUs do I need?
We need to understand the kind of sites that I will be connecting,
different sites produce different load
For example, 2+2+2 site
Site type 222
GPRS Defaul territory (includes dedicated) 0
Number of BTSs per site 0
Abis channels for GPRS territory 0
EGPRS Defaul territory (includes dedicated) 3
Number of BTSs per site 3
Abis channels for EGPRS territory 9
EDAP 1 Pool size (DS0s) 5
Abis channels for EDAP 1 20
EDAP 2 Pool size (DS0s) 0
Abis channels for EDAP 2 0
Total fixed Abis channels per site 29
41 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
How many PCUs do I need? (2)
Dont forget to leave a margin to allow for GPRS territory upgrades !!
If we expect to utilize additional territory channels for example 15% of
the time, then we need to adjust the PCU planning capacity limit
PCU Abis channel capacity 256
PCU utilization factor (to account for
additional territory and possible addition of
PBCCH) 85%
PCU planning capacity 218
Calculate how many sites can be supported with one PCU and with
different sets
BSC Utilization 100% 75%
Number of sites per PCU 7
Number of sites per 8 PCUs 8 56 42
Number of sites per 12 PCUs 12 84 63
Number of sites per 16 PCUs 16 112 84
Leave an additional margin to support site additions without need to modify
PCU count and Gb plan
42 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Gb interface considerations
The number of PCUs selected has an impact on the Gb interface
and SGSN dimensioning
BSC
PCU
SGSN
Frame Relay
Gb
PAPU
BSS GPRS
43 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
GPRS logical to physical channels mapping
NSVC1
NSVC2
PCU1/NSE100
NSVC1
DLCI 16
CIR=384 Kbit/s
AR=384 Kbit/s
NSVC5
NSVC6
PCU2/NSE101
NSVC9
NSVC10
PCU3/NSE102
NSVC13
NSVC14
PCU4/NSE103
BSC1
T1-1
BCH1
NSVC5
DLCI 18
CIR=384 Kbit/s
AR=384 Kbit/s
BCH3
NSVC9
DLCI 20
CIR=384 Kbit/s
AR=384 Kbit/s
BCH5
NSVC13
DLCI 22
CIR=384 Kbit/s
AR=384 Kbit/s
BCH7
With 4 PCUs and 1 T1, F.R. Bearer Channel size is 384 Kbit/s
=6 x 64 Kbit/s
Bearer channel size should as be able to transport as
an absolute minimum: Mobile Max RTSL * 64kbit/s
e.g: If we plan to have 3 TSL mobiles in the network,
the absolute minimum size for the bearer channels
should be 3*64k = 192 Kbit/s
44 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
CONCLUSIONS
With EDGE it is necessary to activate a new feature called Dynamic
Abis
The Dynamic Abis functionality allocates Abis transmission capacity
to cells when needed instead of reserving full fixed transmission link
per TRX.
It is necessary to properly size the EDAP to achieve good BSS
transmission performance
The size and number of EDAPs in a BSC has an impact on the PCU
dimensioning
It is necessay to optimize the whole chain: RF + EDAP + PCU
dimensioning + Gb
45 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
More Questions
?
46 NOKIA Impact of EDGE on the BSS.PPT / MRi
Company Confidential
Thank you
Juan-Manuel Rios
[email protected]