GB Interface Detailed Planning Final 1

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
2 NOKIA 2000 Gb interface detailed planning
Gb Interface
Gb interface
SGSN BSC
Frame Relay
PCU PAPU
BSS GPRS
Gb Interface Review
GPRS Interfaces
SMS-GMSC SMS-IW MSC E D MSC/VLR Gd A Um Gb Gs Gr Gn SGSN Gp GGSN other PLMN
Signalling & Data Transfer C Signalling
HLR
Gc Gi GGSN PDN TE
MS
BSS
Gn SGSN
Gf EIR
Gb Interface Review
GPRS Protocol Stack / transmission plane
Um APP TCP/UDP IP SNDCP LLC RLC MAC GSM RF MS RLC MAC GSM RF BSS Relay BSSGP NS L1 Relay SNDCP LLC BSSGP NS L1 GTP UDP IP LLC/SNAP MAC L1 SGSN USER PAYLOAD GTP UDP IP LLC/SNAP MAC L1 GGSN Gb Gn Gi APP TCP/UDP IP L2 L1
Radio interface
G703 Frame Relay
100 M bps Ethernet
GPRS IP Backbone
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
Gb Interface Review
GPRS Protocol Stack / signalling plane
GMM/SM GMM/SM
LLC
Relay
LLC
RLC
RLC
BSSGP
BSSGP
MAC
MAC
NS
NS
GSM RF
GSM RF
L1
L1
MS
Radio interface
BSS
G703 Frame Relay
SGSN
Gb Interface Review
Network Layers
Gb BSC Intra-site Gn SGSN Inter-site Gn SGSN Gb BSC
GPRS IP Backbone Network
GPRS
TCP/IP
ATM & FR
Transport/SDH
Gb Interface Review
Gb Interface
Gb BSC Frame Relay BSS PCU PAPU GPRS SGSN
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 NS-VC Own BVC for each cell NS-VC Own BVC for each cell
DLCI Data Link Connection Identifier (FR address) FR Bearer Channel Physical Link (= PCM TSL) NSE NS-VC DLCI Data Link Connection Identifier (FR address) Load Sharing FR Bearer Channel Physical Link (= PCM TSL) NSE = (PCU)
BVC 0 for signalling NS-VC Own BVC for each cell NS-VC Own BVC for each cell
SGSN
BVC = BSSGP Virtual Connection BSSGP = Base Station Subsystem GPRS Protocol NSE = Network Service Entity NS-VC = Network Service Virtual Connection FR = Frame Relay
BSC
10
BSSGP
BSS GPRS protocol (layer 3 protocol) delivering data packets and associated control information Supports BSSGP VIRTUAL CONNECTIONS (BVC)
One BVC for each cell One BVCI unique in the NSE
One NS-VC supports several BVCs
11
Id Unique in NSE
Gb Interface Review
Logical Structure
BSS 1
Bearer Channel_1
DLCI_16
NS_VCI unique in SGSN own BVC for each cell
Id Unique in bearer SGSN

PAPU 1
NSEI_1
BVCI_0 BVCI_3 NS-VCI_7 NS-VCI_2 DLCI_17
NSEI_1
NS-VCI_7 NS-VCI_2
PCU 1 LA RA 1
BTS_3 BTS_6
BVCI_0 BVCI_3
Bearer Channel_2
DLCI_16 DLCI_17
PCU 2
NS-VCI_5 NSEI_2 BVCI_0 NS-VCI_8 BVCI_6 NS-VCI_3
NSEI_2 NS-VCI_5
BVCI_0 NS-VCI_8 BVCI_6 NS-VCI_3
DLCI_18
Bearer Channel_3
DLCI_16 DLCI_17
RA 2
BTS_8
PAPU 2
BVCI_8 BVCI_0 BVCI_22
Bearer Channel_4 NSEI_3 NS-VCI_4

NS-VCI_1 NS-VCI_11 DLCI_16
PCU 3
NS-VCI_4 NSEI_3 BVCI_8 NS-VCI_1 NS-VCI_11 BVCI_0 BVCI_22
BTS_22
Bearer Channel_5
DLCI_16
BSS 2
NSEI_7
NS-VCI_6
PAPU 3
NSEI_7
BVCI_0 BVCI_22 NS-VCI_6 NS-VCI_9
DLCI_17
Bearer Channel_6
PCU 3
LA RA
BTS_22
BVCI_0 BVCI_22
BSSGP NS FR
Data Signal Data & Signal
NS-VCI_9
12
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 kbit/s) 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
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 S GS N - number of NS-VCs in SGSN = number of DLCI (up to 256 per PAPU)
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 Total 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 (%)
200 150 100

60.0
Ohmax
108 72 54 50.0 30.0 20.0 15.0 42 11.7 36 27 10.0 7 .5 21 5 .9 4.0 3.0 14 11 9 2.4 7 2.0
50 0
OHmi n
100 150 200 256 300 400 512 750 1000 1250 1500
Packet length (octets)
17
Selecting the Burst Margin
Throughput
EIR=0 CIR
Discarded data Burst Margin, 100 -X% 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
BSC Dimensioning
Packet Control Unit - PCU
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 PCU controls cells, not TRXs like BCSU PCU does not handle the same TRXs as the BCSU where it is located
PSA20 PSFP SW1C SW1C PSA20 PSFP
ET5C
CLOC
CLAC
ET5C
ET5C
3rd SW64B cartridges
MCMU
MCMU
BCSU
WDDC
WDDC
BCSU
BCSU
BCSU
BCSU
BCSU
OMU
BCSU
ET5C
ET5C
PCU HW
in every BCSU
BCSU
BCSU
ET5C
ET5C
ET5C cartridges
19
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)
3 BSC (with capacity of 128 TRXs ) Input Calculations Result
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
Packet size of 400 bytes assumed

1. Minimum requirement: 3 BSC => 3 PCUs required (each for 128 TRX) => 3 PCUs required 2. 60 x 3 cells = 180 cells, 180/64=2.8 3. 12 TCH/BTS x 60 BTS=720 TCH, 720/256 => 3 PCUs required 4. GPRS traffic: 18.5 Mbit/s / 2 Mbit/s = 9.3 =>10 PCUs required
Take the biggest of the results above, I.e. 10 active PCUs required in total
Frame Relay Link Planning

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
Frame Relay Link Planning

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
Simple Dimensioning Example (Gb links)
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) links 2. GPRS traffic: 18.5 Mbit/s / 64 kbit/s = 289.1 links Take the bigger of the results above, I.e. 290 links ( 64 kbit/s) required in total (equals to 10 E1 PCM links) => 20 => 290
Input
24
Result
Calculations
SGSN Dimensioning
DX 200 SGSN
SGAC
PDFU 0 PDFU 1 0 PDFU 0 CL SU 1 SMMU 0 2 SMMU 1
SGBC
PDFU 1 CL BU 0 CL BU 1
One fully equipped SGSN element has the following design targets concerning connectivity: 120 physical 2Mbps E1-PCMs PCMs are freely selectable between Gbinterface and SS7 based interfaces (Gs, Gr, Gd, Gf) 96 SS7 signalling links (24 per SMMU) 1024 64kbps Frame Relay links for Gbinterface use (64 in each PAPU) E.g 100 BSCs each having 8x64kbps Gbinterface 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
PAPU 0
GSW 0
GSW 1
3 MCHU 0 SD MCHU 0 SD MCHU 1 MCHU 1 4 SMMU 2 SMMU 3 SMMU 4
5 OMU 0 SD OMU 0 SD OMU 1 OMU 1 6 PAPU 5 PAPU 6 PAPU 7 PAPU 8
7 ET 0 ( 32 * ET2E/A) ET 1 ( 28 * ET2E/A) 8 PAPU 9 PAPU 10 PAPU 11 PAPU 12
9 PAPU 1 PAPU 2 PAPU 3 PAPU 4 10 PAPU 13 PAPU 14 PAPU 15 PAPU 16
25
SGSN Dimensioning
SGSN Capacities
Data processing capacity of fully equipped SGSN: 48 Mbit/s Subscriber capacity: 120 000 Active PDP contexts: 240 000 1024 64kbit/s FR links for Gb-interface use (64 in each PAPU) 96 SS7 signalling link interfaces ( 64 kbit/s, 24 in each Fu lly eq uipped SGSN contains: S MM U) 16+1 PAPUs (Packet Processing Unit) 4+1 SMMUs (Signalling & Mobility Management Unit)
26
SGSN Dimensioning
SGSN Configuration Levels
Capacities: SGSN Basic Unit
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. 512 Gb IF (64kbit/s) 36 Mbit/s 90 000 subscr. 768 Gb IF (64kbit/s) 48 Mbit/s 120 000 subscr. 1024 Gb IF (64kbit/s)
Extension Units
4 PAPUs, 1 SMMU 4 PAPUs, 1 SMMU
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)
BSC
SGS N
4 PAPUs, 1 SMMU
BSC
4 PAPUs, 1 SMMU
BSC
10 active PCUs in 3 BSCs
4 PAPUs, 1 SMMU
290 links (64kibt/s) in 10 E1 PCM links
1 Basic Unit & 2 Extension Units in the SGSN
28
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
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 M SC Sites
Subscribe r Percentage of re gional 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 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 REGIONS South East Mid South West
PCU Distribution Among M SC Sites

Subscribe r Percentage of re gional 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% 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
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
REGIONS South East Mid South West
33
GPRS Service Areas

Coding Schemes CS 1 CS 2 CS 3 CS 4 9.05 13.4 15.6 21.4 Attached Subs Active Subs 2 PDP Contexts 1 PDP Context M ean PDP / sub PDCH per cell CS2 (Kbps) thru per cell (Kbps) traf_sub (KBytes BH) Overhead thru_sub (Kbytes BH) thru_sub (Kbps) SG SN fill rate 100% 50% 50% 50% 1.5 3 13.4 40.2 50 25% 62.5 142.22 70%
SG SN area 1 SG SN area 2 SG SN area 3 SG SN area 4 SG SN area 5
City 1 Cities 2 and 3 Cities 4, 5, 6, 7 and 8 Cities 9, 10, 11 and 12 Cities 13 and 14
SG SN 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
GPRS Subs 19 500 28 850 33 750 14 750 19 250 49 200 52 440 57 600 49 800 55 800
Attached GPR S 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
GPRS Traffic (M bps) 1.39 2.05 2.40 1.05 1.37 3.50 3.73 4.10 3.54 3.97
34
SGSN AREA CALCULATIONS

Initial Dimensioning Figures Covered Regions SGSN area 1 City 1 Radio Network Estimates Covered Regions S GS N area 1 City 1 GPRS Traffic (M bps) 2001 2002 GPRS Attached Subscribers 2001 2002 Number of Cells 1 115 Min. No. of PDCH (during BHT ) 3 345 Number of S ubscribers 19 500 Number of Cells 1 115 Min. No. of PDCH (during BHT ) 3 345
Nokia B SC 's Nokia B CSU's Non- Nokia PCU Non- Nokia Gb Interface Total Gb Interfaces 2001 2002 GPRS Active subscribers 9'750 24'600 18 162 0 0 80 Active PDP C ontexts 14'625 36'900
1.39 3.50
19 500 49 200
CALCULATION RESULTS PCU (Active) PCU (Hardware) Gb Interface Functionality SGSN PAPU (Active) PAPU (Hardware) SMM U 2001 18 162 22 1 4 4 1 2002
57 10 12 3
35
Ater TIMESLOT ALLOCATION

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

Channels of ET2E 0, interface 1
Existing E1 lines are utilized for Frame Relay traffic Voice Traffic and Frame Relay Traffic combined Throughgoing 64Kbps TS for Frame Relay traffic
2 6 10 14 18 22 26 30 2 6 10 14 18 22 26 30 64 kbit/s 64 kbit/s 64 kbit/s 64 kbit/s 64 kbit/s 64 kbit/s 64 kbit/s
TSs 25-31 can carry Frame Relay traffic (to the Gb interface).
36
DEDICATED PCM SIGNAL

BIT-> TS-> 1 0 1 2 3 4 5 6 7 8..31 2 3 4 5 6 LINK MANAGEMENT 64 kbit/s (Frame Relay) 64 kbit/s (Frame Relay 64 kbit/s (Frame Relay) 64 kbit/s (Frame Relay) 64 kbit/s (Frame Relay 64 kbit/s (Frame Relay) 64 kbit/s (Frame Relay) XXXX 7 8
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) 2 - Drop-and-Insert equipment (inbuilt 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
DN 2
2 Mbit/s
2 Mbit/s
CH
CH
PHYSICAL TOPOLOGY - 1
BSC Abis Transcoders MUX MUX Ater MSC MSC/SGSN site
BSC Abis
E1 PCM (Ater + Frame Relay) SGSN Ethernet Switch GGSN #1 GGSN #2 Frame Relay Gb-int. BSC
Abis
Voice and Data Traffic are multiplexed on the same physical connection as used for the GSM traffic on the Ater interface
BSC Abis Transcoders MUX Dedicated E1/ PCM for BSC Abis E1 PCM for Ater traffic Frame Relay Gb-int. BSC Abis Frame Relay traffic SGSN Ethernet Switch GGSN #1 GGSN #2 MUX Ater MSC MSC/SGSN site
Voice and Data Traffic are allocated on separate E1 / PCM signal

MSC/SGSN Site 1
Transcoders MSC
SGSN 1 SERVICE AREA

BSC
Ater
SGSN Ethernet Switch GGSN #1 GGSN #2
Abis MUX Dedicated E1/ PCM for

BSC
MUX
Frame Relay Gb-int.
Frame Relay traffic
Abis E1 PCM for Ater traffic
MSC/SGSN Site 2
BSC Transcoders MSC
Abis
Ater
SGSN 2 SERVICE AREA

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

MSC/SGSN Site 1 Transcoders MUX Ater SGSN 1 SERVICE AREA BSC Abis E1/PCM for FR ADM Ater TRANSPORT NETWORK E1/PCM for FR Ater MSC/SGSN Site 2 BSC Abis ADM E1/PCM for FR Ater SGSN 2 SERVICE AREA SGSN Frame Relay Gb-int. Ethernet Switch GGSN #1 GGSN #2 MUX Ater Transcoders MSC Frame Relay Gb-int. SGSN Ethernet Switch GGSN #1 GGSN #2 MSC
BSC Abis
ADM
For large capacity networks such as SDH networks Separate E1s for Ater and Frame Relay traffic
MSC/SGSN site
Abis
BSC
Transcoders
MSC
BSC
BSC
SGSN Packet Data Network (FR, ATM, etc.)
Ethernet Switch GGSN #1 GGSN #2
FR Switch
FR Switch
Gb Interface
GPRS traffic is concentrated and carried e.g. in a packet data network over the Gb interface
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
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 deactivate the solution in future
49
50
2 BSCs terminated into same PAPU

NORTEL PCU BSC 1 BSC 1 SGSN PAPU_1 NSE1 NSVC_1 NSE1 NS-VC1
BEARER CH. 1
NSE2 NSVC_2
DLCI_16 E1 BSC 2 DLCI_17 BSC 2 NSE2 NS-VC2 CIR (31 - n) x64 kbps E1 CIR 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
2 BSCs terminated into different PAPUs

NORTEL PCU BSC 1 BSC 1 NSE1 NS-VC1 IF 50% of E1 per BSC, FULL E1 REQUIRED SGSN PAPU_1 NSE1 NSVC_1
BEARER CH. 1
CIR n x64 kbps, n=1..31 E1
DLCI_16 E1 BSC 2 NSE2 NS-VC1

BEARER CH. 2
DLCI_17
CIR
(31 - n) x64 kbps
BSC 2
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
Typical Gb
SGSN NORTEL PCU BSC 1 BSC 1 NSE1 NS-VC1 BSC 2
E1 E1 BEARER CH. 1 DLCI_16 DLCI_17 BEARER CH. 2 DLCI_18 DLCI_19 E1 BEARER CH. 3 DLCI_20 DLCI_21 E1 NSE3 NSVC_3 PAPU_2 NSE4 NSVC_4 E1 CIR n x64 kbps E1 PAPU_1 NSE1 NSVC_1 NSE2 NSVC_2 CIR (31 - n) x64 kbps CIR n x64 kbps
BSC 2
NSE2 NS-VC2 BSC 3
BSC 3
NSE3 NS-VC3
BSC 4 BSC 4 NSE4 NS-VC4 BSC 5 BSC 5 NSE5 NS-VC5 BSC 6 BSC 6 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
NSE5 NSVC_5 PAPU_3 NSE6 NSVC_6
53
Gb with Redundancy
NORTEL PCU BSC 1 BSC 1 NSE1
NSVC_1 NSVC_2 E1 E1 BEARER CH. 1 DLCI_16 DLCI_17 BEARER CH. 2 DLCI_18 E1 E1
SGSN
PAPU_1
NSE1
NSVC_1 NSVC_2
NSE2
NSVC_3 NSVC_4
BSC 2 BSC 2 NSE2

NSVC_3 NSVC_4
DLCI_19
54
Detailed planning exercise

Exercise 2
55
Input for exercise

BSC
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
SGSN
One PAPU
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, NS-VCIs, 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* 64 kbps BS C1
2 BCSUs
PCU1 BEARER CH. 1
DLCI_16 E1(1) DLCI_17 E1(1)
CIR 4 x64 kbps
SGSN
22 TS = 22*64kbps
NSE3 NSVC_3/4
PCU-2 BEARER CH. 2
PAPU_1 NSE1 NSVC_1/2
E1(2)
DLCI_16 DLCI_17
E1(2) NSE2 NSVC_5/6
6 TS = C2 6*64BS kbps 1 BSCU
BEARER CH.3 PCU-1
DLCI_16 E1(1) DLCI_17 CIR 3 x64 kbps E1(1)
58
Overview of the network output BC

Bearer channel = 8 TS = 8*64kbps = 512kbps
BSC 1 2 BCSUs
BEARER CH. 1 PCU1
Bearer channel = 8 TS = 8*64kbps = 512kbps

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

NSE1 NSVC_1 /2
Overview of the network output NSEI/NS-VCI

BEARER CH. 1 PCU1
BSC 1 2 BCSUs
DLCI_16 E1(1) DLCI_17 E1(1)
CIR 4 x64 kbps
SGSN PAPU_1 NSE1 NSE2 NSVC_3/4
PCU-2
NSE2 NSVC_3/4 E1(2)
BEARER CH. 2
NSVC_1 /2 DLCI_16 DLCI_17 E1(2) NSE3
NSVC_5/6
BEARER CH.3
BSC 2 1 BSCU NSE3
PCU-1
DLCI_16 E1(1) E1(1) CIR DLCI_17 CIR 3 x64 kbps (31 - n) x64 kbps
NSVC_5/6
60
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
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
61
Thank you !!!
62
GSM architecture
Air Interface
BSS
Abis Interface
BSC
NSS
A Interface
Ater Interface
BTS
TC MSC/VLR
HLR/ AC/ EIR
TCSM
Ater Interface
O&M Interface
NMS
63

GB Interface Detailed Planning Final 1

Загружено:

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

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

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

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

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

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

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

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

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

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

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

GB Interface Detailed Planning Final 1

Загружено:

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

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

Core Network Planning Gb Interface Detailed Planning

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

Signalling & Data Transfer C Signalling

G703 Frame Relay

100 M bps Ethernet

G703 Frame Relay

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 Mbps FR Bearer channel: 64 kbps 1.92 Mbps

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

One NS-VC supports several BVCs

NOKIA 2000 Gb interface detailed planning

NS_VCI unique in SGSN own BVC for each cell

Id Unique in bearer SGSN

Bearer Channel_4 NSEI_3 NS-VCI_4

Data Signal Data & Signal

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

Frame Relay Link Parameters - 1

Frame Relay Link Parameters - 2

NOKIA 2000 Gb interface detailed planning

200 150 100

NOKIA 2000 Gb interface detailed planning

CIR calculation should include burst margin

3rd SW64B cartridges

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

Packet size of 400 bytes assumed

NOKIA 2000 Gb interface detailed planning

Frame Relay Link Planning

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

At least one 64 kbit/s PCM TSL is required per active PCU

NOKIA 2000 Gb interface detailed planning

Frame Relay Link Planning

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

3 MCHU 0 SD MCHU 0 SD MCHU 1 MCHU 1 4 SMMU 2 SMMU 3 SMMU 4

5 OMU 0 SD OMU 0 SD OMU 1 OMU 1 6 PAPU 5 PAPU 6 PAPU 7 PAPU 8

7 ET 0 ( 32 * ET2E/A) ET 1 ( 28 * ET2E/A) 8 PAPU 9 PAPU 10 PAPU 11 PAPU 12

9 PAPU 1 PAPU 2 PAPU 3 PAPU 4 10 PAPU 13 PAPU 14 PAPU 15 PAPU 16

NOKIA 2000 Gb interface detailed planning

NOKIA 2000 Gb interface detailed planning

4 PAPUs, 1 SMMU 4 PAPUs, 1 SMMU

NOKIA 2000 Gb interface detailed planning

10 active PCUs in 3 BSCs

290 links (64kibt/s) in 10 E1 PCM links

1 Basic Unit & 2 Extension Units in the SGSN

NOKIA 2000 Gb interface detailed planning