Core Network Planning GB Interface Detailed Planning

Core Network Planning
Gb Interface Detailed Planning
NOKIA 2000 Gb interface detailed planning
Agenda
Gb interface introduction
Gb review ( protocol stack / ntw layers )
Gb in detail ( NSE / logical connections )
Frame relay interface planning
BSC dimensioning
Frame relay dimensioning
SGSN dimensioning
Gb Detail planning ( e.g. Topology )
Exercise 1: case study Nortel BSS
Nokia SGSN
Exercise 2: detailed planning
Gb Interface
Gb interface
SGSN
BSC
F ra m e R e la y
PCU
BSS
PAPU
GPRS
Gb Interface Review
GPRS Interfaces
Signalling &
Data Transfer
SMS-GMSC
SMS-IWMSC
C
Signalling
MSC/VLR
HLR
Gd
Gs
MS
Um
BSS
Gb
Gn
SGSN
Gr
SGSN
Gp
GGSN
other PLMN
Gn
Gc
GGSN
Gf
EIR
Gi
PDN TE
Gb Interface Review
GPRS Protocol Stack / transmission plane

Um
Gb
Gi
Gn
APP
USER
PAYLOAD
TCP/UDP
Relay
IP
SNDCP
RLC
RLC
BSSGP
GTP
GTP
L2
UDP
UDP
L1
BSSGP
IP
LLC/SNAP
MAC
L1
MAC
MAC
NS
NS
GSM RF
L1
L1
Radio
interface
BSS
IP
LLC
GSM RF
MS
TCP/UDP
SNDCP
Relay
LLC
APP
G703
Frame Relay
SGSN
IP
LLC/SNAP
MAC
L1
100 Mbps
Ethernet
GPRS IP Backbone
GGSN
Internet
SNDCP: Sub-Network Dependent Convergence Protocol

The primary function of BSSGP is to provide the radio-related, QoS, and routing information that is
required to transmit user data between a BSS and an SGSN. A secondary function is to enable two
physically distinct nodes, the SGSN and BSS, to operate node management control function .
BSSGP: Base Station System GPRS Protocol
NS: Network Service
SNAP: Subnetwork access protocol
5
Gb Interface Review
Network Layers
Intra-site
Gn
Gb
BSC
Inter-site
Gn
Gb
BSC
SGSN
GPRS IP
Backbone
Network
SGSN
GPRS
TCP/IP
ATM & FR
Transport/SDH
Gb Interface Review
Gb Interface
Gb
BSC
BSS
PCU
SGSN
Frame Relay
PAPU
GPRS
Gb Interface; planning issues

2 Mbps Channelised E1 link
NS-VC capacity: 16 kbps1.92

Mbps
FR Bearer channel: 64 kbps 1.92
Mbps
Gb Interface Review
Network Service Entity (NSE)
BVC 0
for
signalling
BVC 0
for
signalling
DLCI Data Link Connection Identifier

(FR address)
FR Bearer Channel
NS-VC
NS-VC
Physical Link (= PCM TSL)

Own BVC
for
each cell
NSE
NS-VC
Own BVC
for
each cell
SGSN
10
NSE
= (PCU)
NS-VC
DLCI Data Link Connection Identifier
(FR address)
Load Sharing FR Bearer Channel
Physical Link (= PCM TSL)
BVC = BSSGP Virtual Connection

BSSGP = Base Station Subsystem GPRS Protocol
NSE = Network Service Entity
NS-VC = Network Service Virtual Connection
FR = Frame Relay
Own BVC
for
each cell
NS-VC
Own BVC
for
each cell
BSC
Gb Interface Review
BSS 1
Id Unique in NSE
NS_VCI unique in SGSN

own BVC for each cell
Logical Structure
Id Unique in bearer
SGSN
PAPU 1
Bearer Channel_1
NSEI_1
BVCI_0
NS-VCI_7
BVCI_3
NS-VCI_2
PCU 1
NSEI_1
DLCI_16
NS-VCI_7
BVCI_0
NS-VCI_2
BVCI_3
DLCI_17
Bearer Channel_2
RA 1
DLCI_16
PCU 2
DLCI_17
NSEI_2 NS-VCI_5
NS-VCI_5 NSEI_2
BVCI_0
NS-VCI_8
BVCI_6
DLCI_18
BVCI_0
Bearer Channel_3
NS-VCI_8
BVCI_6
DLCI_16
DLCI_17
PCU 3
NS-VCI_4 NSEI_3
BVCI_8
DLCI_16
NS-VCI_1
BVCI_8
BVCI_0
NS-VCI_1
BVCI_22
NS-VCI_11
BTS_6
BTS_8
Bearer Channel_4
NSEI_3 NS-VCI_4
BTS_3
RA 2
NS-VCI_3
NS-VCI_3
PAPU 2
LA
BTS_22
BVCI_0
NS-VCI_11
BVCI_22
BSS 2
Bearer Channel_5
DLCI_16
PAPU 3
DLCI_17
NSEI_7
BVCI_0
NS-VCI_6
BVCI_22
NS-VCI_9
BSSGP
NS
FR
12
NSEI_7
Bearer Channel_6
NS-VCI_6
Data
Signal
Data & Signal
NS-VCI_9
PCU 3
BVCI_0
BVCI_22
LA
RA
BTS_22
Gb Interface Review
Logical Channels in Physical Link

BVCs
NS-VCs, CIR=161.984 Mbit/s
FR bearer channels, 131 TSL
PCM Link 32 TSL
PCU
FR bearer channels run on PCM links (641984 kbit/s)

Max. 4 NS-VCs configured on FR bearers (CIR of each 161984 k
CIR doesnt stand in relation to subscriber datarate / cell
Max. 4 NS-VCs per NSE (PCU), and 256 NS-VCs per PAPU
13
Frame Relay Link Parameters - 1

BVC
- 1 BVC (BVCI) for each CELL - unique within an NSE
- 1 BVC (BVCI) can be mapped into 2 NS-VC (load sharing)
- 1 or MORE BVCs (BVCI's) are mapped into 1 or more NS-VC
- 1 SIGNALING BVC per PCU, BVCI = 0000HEX
NS-VC
- NS-VCI = DLCI and FR BEARER CHANNEL IDENTIFIER
- 14 NS-VCs per NSE (=PCU)
- up to 256 per PAPU
- 1 NS-VC supports several BVC
- capacity controlled by CIR in steps of 16 Kbps up to the
BEARER CHANNEL capacity
- NS-VCI is unique within a SGSN, identical on BOTH ENDS
(end to end) ; range 065535
PCU
- 1 PCU = 1 NSE (NSEI)
- 1 PCU handles maximum 64 cells
14
Frame Relay Link Parameters - 2

NSE
- NSEI is unique within a BSC, identical on BOTH ENDS (end to end) range
065535
- on BOTH ENDS are connected by 1 or MORE NS-VC
- within 1 NSE, NS-VCs are shared by all BVCs
DLCI
- up to 124 DLCI on 1 BEARER CHANNEL - unique within 1 BEARER CHANNEL,
identical on BOTH SIDES
- range 16991
BEARER CHANNEL
- capacity from 64 to 1984 Kbps (1 to 31 TS of an E1) in multiples of 64Kbps
PAPU
- supports up to 64 PCU per PAPU
SGSN
- number of NS-VCs in SGSN = number of DLCI (up to 256 per PAPU)
15
Gb Inteface Planning
3 Sections of Gb Inteface Planning
BSC Planning - defining the number
of active
PCUs
Frame Relay Link Planning
Topology Planning
Frame Relay Link Dimensioning
SGSN Dimensioning - defining the
number of
PAPU & SGSN
equipments and extension units
16
Selecting the Protocol Overhead

Percentage of Overhead in GPRS Traffic at the Gb Interface
Gb I/F Protocol Stack
Protocol Min Header size (oct.) Max Header size (oct.) Reference
SNDCP
3
4
GSM 04.65
LLC
5
40
GSM 04.64
BSSGP
12
54
GSM 08.18
NS
4
4
GSM 08.16
FR
6
6
GSM 03.60
30
108 Packet size Min OH % Max OH %

50
60.00
216.00
60
50.00
180.00
100
30.00
108.00
150
20.00
72.00
200
15.00
54.00
256
11.72
42.19
300
10.00
36.00
400
7.50
27.00
512
5.86
21.09
750
4.00
14.40
1000
3.00
10.80
1250
2.40
8.64
1500
2.00
7.20
300
216
250
180
Overhead (%)
Total
Ohmax
200
150
108
100
72
60.0
50
0
OHmi
n
54
50.0
30.0
20.0
15.0
42
11.7
36
10.0
27
7.5
21
14
11
4.0
3.0
2.4
2.0
5.9
100 150 200 256 300 400 512 750 1000 1250 1500
Packet length (octets)
17
Selecting the Burst Margin
Throughput
EIR=0
Discarded
data
Burst
Margin, 100
-X%
CIR
Actual traffic
load, X %
time
Packet data traffic is bursty in nature

Nokia PCU implements a Static Frame Relay
Data above the CIR is discarded (EIR = 0)
CIR calculation should include burst margin
18
BSC Dimensioning
Packet Control Unit - PCU
19
BCSU
BCSU
ET5C
ET5C
ET5C
CLAC
BCSU
BCSU
BCSU
ET5C
ET5C
BCSU
MCMU
OMU
WDDC
ET5C
CLOC
SW1C
SW1C
MCMU
WDDC
ET5C
BCSU
BCSU
PCU controls cells, not TRXs

like BCSU PCU does not
handle the same TRXs as the
BCSU where it is located
PSA20
PSFP
PSA20
PSFP
BCSU
All BSC's BCSU units must be

fully equipped with PCUs
(max. 8+1 per BSC)
GSWB expanded from 128 to
192 PCMs (if not already
done)
BSC2E/A:
Extra
ET5C
Cartridges to increase PCMs
from 80 to 112
3rd SW64B
cartridges
PCU HW
in every BCSU
ET5C
cartridges
BSC Dimensioning
Defining the active number of PCUs

Dimensioning Criteria for the number of
active PCUs:
1. Each BSC in GPRS coverage area has to
contain at least one active PCU (minimum
requirement)
2. PCU can supports 256 TCHs

3. PCU Data processing capacity is 2 Mbit/s
4. PCU can support up to 64 cells
5. PCU can supports 128 TRX's
20
BSC Dimensioning
Simple Dimensioning Example (PCU)
21
Coverage area contains 60 BTS sites, each having 2+2+2 cell/TRX

configuration
4 TCHs/cell used by GPRS on average
Estimated GPRS traffic: 15 Mbit/s + 19% Overhead = 18.5 Mbit/s
Calculations
Packet size of 400 bytes assumed
1.
2.
3.
4.
Result
Input
3 BSC (with capacity of 128 TRXs )
Take the biggest of the results above,

I.e. 10 active PCUs required in total
Minimum requirement: 3 BSC

=> 3 PCUs required (each
60 x 3 cells = 180 cells, 180/64=2.8
=> 3 PCUs requir
12 TCH/BTS x 60 BTS=720 TCH, 720/256 => 3 PCUs require
GPRS traffic: 18.5 Mbit/s / 2 Mbit/s = 9.3 =>10 PCUs require

Link Dimensioning
Frame Relay traffic is carried in logical
64 kbit/s PCM time slots.
Each active PCU has its own separate
Gb interface connection, I.e. FR
connection
Capacity: n * 64 kbit/s, where n =

131.
64 kbit/s 1.984 Mbit/s (E1 speed)
At least one 64 kbit/s PCM TSL is

required per active PCU
22

Link Dimensioning
Dimensioning criteria for the number of 64kbit/s
links:
1. At least two 64 kbit/s channels per BSC is

recommended (due to bursty nature of data)
2. At least one 64 kbit/s channel per active PCU
3. Dimensioning is based on estimated GPRS traffic
during the Busy Hour, + the estimated protocol
overhead on the Gb interface traffic + margin for
bursting
23
Gb Link Dimensioning
Result
Calculations
Input
Simple Dimensioning Example (Gb links)
24
Total number of PCUs in 3 BSCs: 10 PCUs

Estimated total GPRS traffic during the BH: 15 Mbit/s
Overhead correction: + 19%
Packet size of 400 bytes assumed
15 Mbit/s * 19% = 18.5 Mbit/s
1. Two 64 kbit/s links per PCU (10 * 2)

2. GPRS traffic: 18.5 Mbit/s / 64 kbit/s = 289.1
links
=> 20 links
=> 290
Take the bigger of the results above,

I.e. 290 links ( 64 kbit/s) required in total
(equals to 10 E1 PCM links)
SGSN Dimensioning
DX 200 SGSN
SGAC
PDFU 0
PAPU
0
SGBC
PDFU 1
GSW
0
GSW
1
CL
SU
PDFU 0
PDFU 1
CL
BU
0
CL
BU
1
SMMU
0
SMMU
1
SMMU
2
SMMU
3
SMMU
4
PAPU
5
PAPU
6
PAPU
7
PAPU
8
PAPU
9
PAPU
10
PAPU
11
PAPU
12
PAPU
13
PAPU
14
PAPU
15
PAPU
16
MCHU
0
OMU
0
SD
MCHU
0
SD
MCHU
1
MCHU
1
SD
OMU
0
SD
OMU
1
OMU
1
7
ET 0
( 32 * ET2E/A)
ET 1
( 28 * ET2E/A)
8
9
PAPU
1
PAPU
2
PAPU
3
PAPU
4
10
25
One fully equipped SGSN element has

the following design targets
concerning connectivity:
120 physical 2Mbps E1-PCMs
PCMs are freely selectable between
Gb-interface and SS7 based interfaces
(Gs, Gr, Gd, Gf)
96 SS7 signalling links (24 per
SMMU)
1024 64kbps Frame Relay links for
Gb-interface use (64 in each PAPU)
E.g 100 BSCs each having 8x64kbps
Gb-interface connection could be
connected into one SGSN
16 100-baseTX Ethernet connections
for Gn-interface use (one in each
PAPU)
Maximum of 16 000 Routing Areas, 2
000 Location Areas
SGSN Dimensioning
SGSN Configuration Levels

Capacities:
SGSN
Basic Unit
4 PAPUs, 1 SMMU
4 PAPUs, 1 SMMU
Extension
Units
4 PAPUs, 1 SMMU
4 PAPUs, 1 SMMU
12 Mbit/s
30 000 subscr.
256 Gb IF (64kbit/s)
24 Mbit/s
60 000 subscr.
36 Mbit/s
90 000 subscr.
48 Mbit/s
120 000 subscr.
SGSN can be configured in four steps. The right configuration level for
each case is determined by the dimensioning rules.
27
Gb Interface Dimensioning
Simple Dimensioning Example (Summary)
SGS
N
BSC
4 PAPUs, 1 SMMU
BSC
4 PAPUs, 1 SMMU
BSC
10 active PCUs
in 3 BSCs
28
4 PAPUs, 1 SMMU
290 links (64kibt/s)

in 10 E1 PCM links
1 Basic Unit &

2 Extension Units
in the SGSN
Gb INTERFACE DETAILED
PLANNING
29
GPRS Dimensioning
Considerations
FUTURE SCENARIOS
- Operator's short and long term plans
concerning the network expansions and
evolution to new technologies
CAPACITY DEMAND
- Subscriber volume
- GPRS traffic estimation
- GPRS coverage area
EXISTING NETWORK INFRASTRUCTURE
- Existing Transmission, Data Communication
backbone and GSM network infrastructures
30
Topology and Dimensioning

Requirements
BSC Distribution
PCU Distribution among MSC
sites
Network Topology
Network Architecture
Subscriber Distribution
GPRS Traffic Distribution
Overhead % Requirement
Burst Margin
Future Network Expansion
31
GPRS Coverage Planning

From the requirements stated on the
previous slide we can determine the
following :
- GPRS coverage areas
- Topology and Capacity of the Frame relay
links in a GPRS service area
- GPRS network dimension per coverage areas
32
BSC & PCU Distribution Among

MSC Sites
BSC Distribution Among MSC Sites
1
2
3
4
5
6
7
8
9
10
11
12
City A
City B
City C
City D
City E
City F
City G
City H
City I
City J
City K
City L
Total
Subscriber Percentage of regional BSCs

13.9%
89.4%
1.7%
10.6%
14.0%
75.3%
4.6%
24.7%
11.2%
40.3%
8.0%
28.9%
10.8%
74.4%
8.6%
36.4%
8.5%
30.8%
9.6%
40.6%
5.4%
23.0%
3.7%
25.6%
100.0%
2000
55
6
50
17
33
24
37
33
26
37
21
13
352
Num ber of BSCs in year

2001
2002
2003
70
70
70
8
8
8
65
65
65
21
21
21
43
43
43
31
31
31
48
48
48
42
42
42
33
33
33
47
47
47
27
27
27
16
16
16
451
451
451
2004
70
8
65
21
43
31
48
42
33
47
27
16
451
2000
110
12
100
34
10
7
74
66
7
74
42
26
562
Num ber of PCUs in year

2001
2002
2003
140
140
140
16
16
16
130
130
130
42
42
42
12
12
13
9
9
9
96
96
96
84
84
84
10
10
10
94
94
94
54
54
54
32
32
32
719
719
720
2004
140
16
130
42
13
9
96
84
10
94
54
32
720
REGIONS
South
East
Mid
South
West
PCU Distribution Among MSC Sites
1
2
3
4
5
6
7
8
9
10
11
12
33
City A
City B
City C
City D
City E
City F
City G
City H
City I
City J
City K
City L
Total
Subscriber Percentage of regional PCUs

13.9%
89.4%
1.7%
10.6%
14.0%
75.3%
4.6%
24.7%
11.2%
40.3%
8.0%
28.9%
10.8%
74.4%
8.6%
36.4%
8.5%
30.8%
9.6%
40.6%
5.4%
23.0%
3.7%
25.6%
100.0%
REGIONS
South
East
Mid
South
West
GPRS Service Areas

Coding Schemes
CS1
CS2
9.05
13.4
CS3
CS4
15.6
21.4
SGSN area 1
SGSN area 2
SGSN area 3
SGSN area 4
SGSN area 5
SGSN Areas
2001 AREA 1
2001 AREA 2
2001 AREA 3
2001 AREA 4
2001 AREA 5
2002 AREA 1
2002 AREA 2
2002 AREA 3
2002 AREA 4
2002 AREA 5
34
Attached Subs
Active Subs
2 PDP Contexts
1 PDP Context
Mean PDP / sub
PDCH per cell
CS2 (Kbps)
thru per cell (Kbps)
traf_sub (KBytes BH)
Overhead
thru_sub (Kbytes BH)
thru_sub (Kbps)
SGSN fill rate
City 1
Cities 2 and 3
Cities 4, 5, 6, 7 and 8
Cities 9, 10, 11 and 12
Cities 13 and 14
GPRS
Subs
19 500
28 850
33 750
14 750
19 250
49 200
52 440
57 600
49 800
55 800
Attached GPRS Subs

19 500
28 850
33 750
14 750
19 250
49 200
52 440
57 600
49 800
55 800
Active GPRS Subs

9 750
14 425
16 875
7 375
9 625
24 600
26 220
28 800
24 900
27 900
Active PDP Contexts

14 625
21 638
25 313
11 063
14 438
36 900
39 330
43 200
37 350
41 850
100%
50%
50%
50%
1.5
3
13.4
40.2
50
25%
62.5
142.22
70%
GPRS Traffic
(Mbps)
1.39
2.05
2.40
1.05
1.37
3.50
3.73
4.10
3.54
3.97
SGSN AREA CALCULATIONS

Initial Dimensioning Figures
Covered Regions
SGSN area 1
City 1
Number of
Subscribers
19 500
Number of Cells
1 115
Covered Regions
Number of Cells
SGSN area 1
City 1
1 115
Min. No. of PDCH

(during BHT)
3 345
Active PDP
Contexts
9'750
24'600
14'625
36'900
18
162
Non-Nokia PCU
Non-Nokia Gb Interface
0
0
Total Gb Interfaces
GPRS Traffic (Mbps)

2001
2002
80
1.39
3.50
19 500
49 200
CALCULATION RESULTS
PCU (Active)
PCU (Hardware)
Gb Interface Functionality
SGSN
PAPU (Active)
PAPU (Hardware)
SMMU
35
2001
2002
Nokia BSC's
Nokia BCSU's
Radio Network Estimates
GPRS Attached Subscribers

2001
2002
GPRS Active
subscribers
Min. No. of PDCH

(during BHT)
3 345
2001
18
162
22
1
4
4
2002
57
10
12
Ater TIMESLOT ALLOCATION

TS
00
Bits
3
4
01
02
03
04
05
06
07
08
LAPD
4
8
12
16
20
24
28
1
5
9
13
17
21
25
29
2
6
10
14
18
22
26
30
3
7
11
15
19
23
27
31
09
10
11
12
13
14
15
16
4
8
12
16
20
24
28
1
5
9
13
17
21
25
29
2
6
10
14
18
22
26
30
3
7
11
15
19
23
27
31
17
18
19
20
21
22
23
24
4
8
12
16
20
24
28
1
5
9
13
17
21
25
29
2
6
10
14
18
22
26
30
3
7
11
15
19
23
27
31
25
26
27
28
29
30
31
Ater Time Slot

Allocation
TS 0
64 kbit/s
64 kbit/s
64 kbit/s
64 kbit/s
64 kbit/s
64 kbit/s
64 kbit/s
Channels of
ET2E 0,
interface 1
Channels of
ET2E 1,
interface 0
Channels of
ET2E 1,
interface 1
Channels of
ET2E 2,
interface 0
TSs 25-31 can carry Frame Relay traffic (to the Gb interface).
36
Existing E1 lines are

utilized for Frame Relay
traffic
Voice Traffic and Frame
Relay Traffic combined
Throughgoing 64Kbps TS
for Frame Relay traffic
DEDICATED PCM SIGNAL
Time Slot allocation of a dedicated E1

signal for carrying the Gb / Frame Relay
traffic to the SGSN.
37
DN2 DXC EQUIPMENT OVERVIEW

1 - Cross-connection Node
- 2 Mbit/s
- 64 kbits
- nx8 kbit/s
- up to 40 2 Mbit/s interfaces
(G.703)
DN 2
2 Mbit/s
2 Mbit/s
2 - Drop-and-Insert equipment
(in-built DB 2)
3 - Primary Multiplexing
Equipment (in-built DM 2)
Three cartridge sizes:
20 T
(four units)
40 T
(eight units)
19 Subrack (sixteen units)
40-port DN 2 uses two subracks and
interconnecting cables
38
CH
CH
PHYSICAL TOPOLOGY - 1
MSC/SGSN site
BSC
Abis
Transcoders
MUX
MUX
MSC
Ater
E1 PCM (Ater + Frame Relay)
BSC
Abis
SGSN
Ethernet Switch
GGSN #1
Frame
Relay Gb-int.
GGSN #2
BSC
Abis
Voice and Data Traffic are multiplexed on the

same physical connection as used for the GSM traffic
on the Ater interface
39
MSC/SGSN site
BSC
Abis
Transcoders
MUX
MUX
MSC
Ater
Dedicated E1/ PCM for

Frame Relay traffic
BSC
Abis
SGSN
E1 PCM for Ater traffic
Frame
Relay Gb-int.
Ethernet Switch
GGSN #1
GGSN #2
BSC
Abis
Voice and Data Traffic are allocated on separate E1

/ PCM signal
40
MSC/SGSN Site 1
Transcoders
SGSN 1 SERVICE AREA
MSC
Ater
BSC
SGSN
Ethernet Switch
Abis
MUX
GGSN #1
GGSN #2
Frame
Relay Gb-int.
MUX
Dedicated E1/ PCM for
BSC
Frame Relay traffic
Abis
E1 PCM for Ater traffic
MSC/SGSN Site 2
Transcoders
BSC
Abis
MSC
Ater
SGSN 2 SERVICE AREA

SGSN
Frame
Relay Gb-int.
Ethernet Switch
GGSN #1
GGSN #2
Voice and Data Traffic are allocated on different

E1s
41
MSC/SGSN Site 1
Transcoders
MSC
MUX
Ater
SGSN 1 SERVICE AREA

BSC
ADM
BSC
ADM
Abis
SGSN
E1/PCM for FR
Abis
Ater
Frame
Relay Gb-int.
Ethernet Switch
GGSN #1
GGSN #2
TRANSPORT
NETWORK
E1/PCM for FR
Ater
MSC/SGSN Site 2
BSC
Abis
ADM
E1/PCM for FR
Transcoders
MSC
MUX
Ater
Ater
SGSN 2 SERVICE AREA

SGSN
Frame
Relay Gb-int.
For large capacity networks such as SDH networks

Separate E1s for Ater and Frame Relay traffic
42
Ethernet Switch
GGSN #1
GGSN #2
MSC/SGSN site
Abis
BSC
Transcoders
MSC
BSC
BSC
SGSN
FR Switch
Packet Data Network

(FR, ATM, etc.)
Ethernet Switch
GGSN #1
GGSN #2
FR Switch
Gb Interface
GPRS traffic is concentrated and carried e.g. in a packet

data network over the Gb interface
43
EXAMPLE BSC / PCU

CONFIGURATION
44
EXAMPLE SGSN/PAPU
Configuration
45
Nortel BSS - Nokia SGSN

Exercise 1 - Case Study
46
Tasks for Exercise

Make a draft of 2 BSCs connected to Nortel PCU
Nortel PCU interfaces Nokia SGSN
You can assume 10 timeslots of traffic in E1
frame per BSC (10 x 64kbps)
Allocate bearer channels, NS-VCs, DLCIs, SGSN,
PAPUs
Show some redundancy options
47
Background to Encountered
Problems
Frame Relay over E1 must be used

Timeslots reserved for FR bearer channels are specified in SGSN
Nokia assumes that channelised FR is supported by Nortel PCU, as
it is a standard FR feature and normally supported by Nortel
Passport.
Nortel BSS - Nokia SGSN interoperability tests not complete

enough
Tests were carried out with one NSE/bearer channel so the full
capability of Nokia SGSN was not tested
Nokia SGSN supports several NSEs per bearer channel

Blu in Italy, upto 5 NSEs/bearer channel
Depending in the FR capabilities of the PCU in question, Nokia may
deploy different FR solutions
48
Solution
Nokia and Nortel together implement the technical
solutions proposed in the following slides in the
Dutchtone network
Both vendors will document the test results for
Dutchtone and for their own interoperability
documentation
Nokia proposes to take an action point to

Carry out the interoperability test with Nortel in the
Dutchtone network
Fully document the SGSN Frame Relay capabilities

Changes to SGSN software or Change Deliveries would
not de-activate the solution in future
49
50
2 BSCs terminated into same PAPU

SGSN
NORTEL PCU
PAPU_1
BSC 1
BSC 1
NSE1
NSE2
NSVC_1
NSVC_2
NSE1
NS-VC1
BEARER CH. 1
DLCI_16
E1
E1
CIR n x64 kbps
BSC 2
DLCI_17
BSC 2
NSE2
NS-VC2
CIR
(31 - n) x64 kbps
Remarks:
A Bearer channel can be associated to several NSEs, channel rate n x 64 Kbps
Bearer channel minimum rate = 64 Kbps
EIR set to null
Maximum 50 NS-VCs/bearer channel
If NS-VCs are terminated into same PAPU, they can be carried over same bearer channels
51
2 BSCs terminated into different PAPUs

SGSN
NORTEL PCU
PAPU_1
BSC 1
BSC 1
IF 50% of E1 per BSC,
FULL E1 REQUIRED
NSE1
NS-VC1
BEARER CH. 1
NSE1
NSVC_1
CIR n x64 kbps, n=1..31
DLCI_16
E1
BSC 2
BSC 2
NSE2
NS-VC1
E1
BEARER CH. 2
DLCI_17
CIR
(31 - n) x64 kbps
PAPU_2
NSE2
NSVC_1
Remarks:
A Bearer channel can be associated to several NSEs, channel rate n x 64 Kbps
Bearer channel minimum rate = 64 Kbps
EIR set to null
Maximum 50 NS-VCs/bearer channel
If NS-VCs are terminated into different PAPUs, they have to be carried over separate bearer channels
52
Typical Gb
SGSN
NORTEL PCU
BSC 1
BSC 1
E1
NSE1
NS-VC1
BSC 2
BSC 2
NSE2
NS-VC2
BSC 3
BSC 3
NSE3
NS-VC3
BEARER CH. 1
DLCI_16
E1
PAPU_1
NSE1
NSVC_1
NSE2
NSVC_2
CIR n x64 kbps
CIR
(31 - n) x64 kbps
DLCI_17
E1
BEARER CH. 2
E1
CIR n x64 kbps
DLCI_18
PAPU_2
DLCI_19
E1
BEARER CH. 3
E1
NSE3
NSVC_3
NSE4
NSVC_4
DLCI_20
DLCI_21
BSC 4
PAPU_3
BSC 4
NSE4
NS-VC4
NSE5
NSVC_5
NSE6
NSVC_6
BSC 5
BSC 5
NSE5
NS-VC5
BSC 6
BSC 6
53
NSE6
NS-VC6
REMARKS:
About 1/2 E1 required per BSC
PAPU processing capacity 3 Mbps
-> 1 BSC can be connected into same PAPU, each
occupying 15 x 64 k FR
Gb with Redundancy
SGSN
NORTEL PCU
BSC 1
BSC 1
E1
NSE
1
BEARER CH. 1
E1
BEARER CH. 2
BSC 2
NSE
2
NSVC_3
NSVC_4
54
DLCI_19
NSE
1
NSVC_1
DLCI_17
DLCI_18
BSC 2
E1
DLCI_16
NSVC_1
NSVC_2
PAPU_1
E1
NSVC_2
NSE
2
NSVC_3
NSVC_4
Detailed planning exercise

Exercise 2
55
Input for exercise

BSC
SGSN
One PAPU
2 BSCs (geographically split)

1. BSC ( 16 sites connected each 2
cells)
2 BCSUs
8 x 64k TS GPRS traffic for 8 sites
on each PCU
2. BSC (6 sites connected each 2
cells)
1 BCSUs
6 x 64k TS GPRS traffic for 6 sites
56
FR links
BSC
BSC1 is connected with 2
FR links while BSC2 has one
FR link connection
Considerations for the planning

Prepare an overview of the network
Dimension FR links (Bearer channels)
Allocated all ids : NSEI,BVCIs, NSVCIs, DLCIs, and define the capacity
of all Bearer channels and DLCs. Also
include some examples of load
sharing or protection
This is a freestyle exercise so there
is no really a right solution of this
exercise.
57
Overview of the network - output

16 TS =
16*64kbps
BSC 1
2 BCSUs
BEARER CH. 1
PCU1
PCU-2
E1(1)
DLCI_1
6
DLCI_17
E1(1)
CIR
4 x64 kbps
SGSN
PAPU_1
BEARER CH. 2
E1(2)
DLCI_16
E1(2)
DLCI_16
E1(1)
DLCI_17
CIR
58
NSE3
NSVC_1/2
NSVC_3/4
NSVC_5/6
BEARER CH.3
E1(1)
NSE1
NSE2
DLCI_17
6 TS =
BSC 2
PCU-1
6*64kbps
1 BSCU
22 TS =
22*64kbps
3 x64 kbps
Overview of the network output BC

BSC 1
2 BCSUs
Bearer channel = 8
TS = 8*64kbps =
512kbps
Bearer channel = 8
TS = 8*64kbps =
512kbps
BEARER CH. 1
PCU1
PCU-2
E1(1)
DLCI_1
6
DLCI_17
E1(1)
CIR
4 x64 kbps
SGSN
PAPU_1
BEARER CH. 2
E1(2)
DLCI_16
E1(2)
NSE1
NSE2
NSVC_1 /2
NSVC_3/4
NSE3
DLCI_17
NSVC_5/6
BEARER CH.3
BSC 2
1 BSCU
PCU-1
DLCI_16
E1(1)
E1(1)
DLCI_17
CIR
3 x64 kbps
Data link connection = 2x 3*64kbps = 2 x

128kbps
Bearer channel = 6*64kbps = 384kbps
59
NSE1
NSVC_1 /2
Overview of the network output

NSEI/NS-VCI
BSC 1
2 BCSUs
BEARER CH. 1
PCU1
PCU-2
E1(1)
NSE2
DLCI_1
6
DLCI_17
E1(1)
CIR
4 x64 kbps
SGSN
PAPU_1
BEARER CH. 2
NSVC_3/4
E1(2)
DLCI_16
NSE1
NSE2
NSVC_1 /2
NSVC_3/4
E1(2)
NSE3
DLCI_17
NSVC_5/6
BEARER CH.3
BSC 2
1 BSCU
PCU-1
DLCI_16
E1(1)
E1(1)
NSE3
NSVC_5/6
CIR
DLCI_17
CIR
60
3 x64 kbps
(31 - n) x64 kbps
Overview of the network output BVCI

BSC PCU 1 - 8 sites
site
cell
BVCI
1
1
1
2
2
3
2
4
3
5
3
6
4
7
4
8
5
9
5
10
6
11
6
12
7
13
7
14
8
15
8
16
61
BSC 1
2 BCSUs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
PCU1
PCU-2
BSC PCU 2 - 8 sites

site
cell
BVCI
1
1
1
2
2
3
2
4
3
5
3
6
4
7
4
8
5
9
5
10
6
11
6
12
7
13
7
14
8
15
8
16
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
BSC 2
1 BSCU
PCU-1
Thank you !!!
62
GSM architecture
Air
Interface
Abis
Interface
Ater
Interface
BSS
A
Interface
BSC
BTS
NSS
TC
HLR/
AC/
EIR
MSC/VLR
TCSM
Ater
Interface
NMS
63
O&M
Interface

Core Network Planning GB Interface Detailed Planning

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Core Network Planning GB Interface Detailed Planning

Загружено:

Авторское право:

Доступные форматы

Core Network Planning

Gb Interface Detailed Planning

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

GPRS Protocol Stack / transmission plane

SNDCP: Sub-Network Dependent Convergence Protocol

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

Gb Interface; planning issues

NS-VC capacity: 16 kbps1.92

NOKIA 2000 Gb interface detailed planning

Network Service Entity (NSE)

DLCI Data Link Connection Identifier

Physical Link (= PCM TSL)

NOKIA 2000 Gb interface detailed planning

BVC = BSSGP Virtual Connection

NS_VCI unique in SGSN

NOKIA 2000 Gb interface detailed planning

Logical Channels in Physical Link

FR bearer channels run on PCM links (641984 kbit/s)

NOKIA 2000 Gb interface detailed planning

Frame Relay Link Parameters - 1

NOKIA 2000 Gb interface detailed planning

Frame Relay Link Parameters - 2

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

Selecting the Protocol Overhead

108 Packet size Min OH % Max OH %

NOKIA 2000 Gb interface detailed planning

Selecting the Burst Margin

Packet data traffic is bursty in nature

NOKIA 2000 Gb interface detailed planning

Packet Control Unit - PCU

NOKIA 2000 Gb interface detailed planning

PCU controls cells, not TRXs

All BSC's BCSU units must be

Defining the active number of PCUs

2. PCU can supports 256 TCHs

NOKIA 2000 Gb interface detailed planning

Simple Dimensioning Example (PCU)

Coverage area contains 60 BTS sites, each having 2+2+2 cell/TRX

Packet size of 400 bytes assumed

3 BSC (with capacity of 128 TRXs )

Take the biggest of the results above,

Minimum requirement: 3 BSC

NOKIA 2000 Gb interface detailed planning

Frame Relay Link Planning

Capacity: n * 64 kbit/s, where n =

64 kbit/s 1.984 Mbit/s (E1 speed)

At least one 64 kbit/s PCM TSL is

NOKIA 2000 Gb interface detailed planning

Frame Relay Link Planning

1. At least two 64 kbit/s channels per BSC is

NOKIA 2000 Gb interface detailed planning

Simple Dimensioning Example (Gb links)

Total number of PCUs in 3 BSCs: 10 PCUs

1. Two 64 kbit/s links per PCU (10 * 2)

Take the bigger of the results above,

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning