Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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-IWMSC E D MSC/VLR Gd A Um Gb Gs Gr Gn SGSN Gp GGSN other PLMN
4 NOKIA 2000 Gb interface detailed planning
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 GTP UDP IP LLC/SNAP MAC L1 USER PAYLOAD Gb Gn Gi APP TCP/UDP IP L2 L1
Radio interface
SGSN
GGSN
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
5 NOKIA 2000 Gb interface detailed planning
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
SGSN
G703 Frame Relay
Gb Interface Review
Network Layers
Gb BSC SGSN
GPRS IP Backbone Network
Intra-site Gn
Inter-site Gn SGSN
Gb BSC
GPRS
TCP/IP
ATM & FR
Transport/SDH
Gb Interface Review
Gb Interface
Gb BSC SGSN Frame Relay BSS PCU PAPU GPRS
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
11
Id Unique in NSE
Gb Interface Review
Logical Structure
BSS 1
Bearer Channel_1
DLCI_16
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
PCU 3 PAPU 2
BVCI_8 BVCI_0 BVCI_22
BTS_22
Bearer Channel_5
DLCI_16
BSS 2
PCU 3
NSEI_7
NS-VCI_6 BVCI_0 BVCI_22
PAPU 3
NSEI_7
BVCI_0 BVCI_22 NS-VCI_6 NS-VCI_9
DLCI_17
Bearer Channel_6
LA RA
BTS_22
BSSGP NS FR
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
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
Gb Inteface Planning
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 (%)
Ohmax
108 72 54 50.0 30.0 42 20.0 15.0 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
Gb Inteface Planning
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)
18 NOKIA 2000 Gb interface detailed planning
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 PSA20 PSFP
SW1C
SW1C
ET5C
CLOC
CLAC
ET5C
ET5C
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
Take the biggest of the results above, I.e. 10 active PCUs required in total
22
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
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 Fully equipped SGSN contains: SMMU) 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
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
4 PAPUs, 1 SMMU
28
29
31
32
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
33
SGSN area 1 SGSN area 2 SGSN area 3 SGSN area 4 SGSN 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
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
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
GPRS Traffic (Mbps) 1.39 2.05 2.40 1.05 1.37 3.50 3.73 4.10 3.54 3.97
34
1.39 3.50
19 500 49 200
CALCULATION RESULTS PCU (Active) PCU (Hardware) Gb Interface Functionality SGSN PAPU (Active) PAPU (Hardware) SMMU 2001 18 162 22 1 4 4 1 2002
57 10 12 3
35
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
Existing E1 lines are utilized for Frame Relay traffic Voice Traffic and Frame Relay Traffic combined Throughgoing 64Kbps TS for Frame Relay traffic
TSs 25-31 can carry Frame Relay traffic (to the Gb interface).
36
Time Slot allocation of a dedicated E1 signal for carrying the Gb / Frame Relay traffic to the SGSN.
37
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
39 NOKIA 2000 Gb interface detailed planning
PHYSICAL TOPOLOGY - 2
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
PHYSICAL TOPOLOGY - 3
MSC/SGSN Site 1
Transcoders MSC
Ater
SGSN Ethernet Switch GGSN #1 GGSN #2
MUX
MSC/SGSN Site 2
BSC Transcoders MSC
Abis
Ater
PHYSICAL TOPOLOGY - 4
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 ADM BSC Abis 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
42 NOKIA 2000 Gb interface detailed planning
PHYSICAL TOPOLOGY - 5
MSC/SGSN site
Abis
BSC
Transcoders
MSC
BSC
BSC
FR Switch
FR Switch
Gb Interface
GPRS traffic is concentrated and carried e.g. in a packet data network over the Gb interface
43 NOKIA 2000 Gb interface detailed planning
44
45
46
47
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 NOKIA 2000 Gb interface detailed planning
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
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
51 NOKIA 2000 Gb interface detailed planning
BEARER CH. 1
DLCI_17
CIR
BSC 2
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 NOKIA 2000 Gb interface detailed planning
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 PAPU_2 DLCI_19 E1 BEARER CH. 3 DLCI_20 DLCI_21 E1 NSE3 NSVC_3 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
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
SGSN 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 PAPU_1
NSE1
NSVC_1 NSVC_2
NSE2
NSVC_3 NSVC_4
DLCI_19
54
55
SGSN
One PAPU
FR links
BSC BSC1 is connected with 2 FR links while BSC2 has one FR link connection
57
SGSN
22 TS = 22*64kbps
NSE3 NSVC_3/4
E1(2)
DLCI_16 DLCI_17
58
SGSN
NSVC_5/6
BEARER CH.3
BSC 2 1 BSCU
PCU-1
NSE1 NSVC_1 /2
BSC 1 2 BCSUs
PCU-2
BEARER CH. 2
NSVC_5/6
BEARER CH.3
PCU-1
DLCI_16 E1(1) E1(1) CIR DLCI_17 CIR 3 x64 kbps (31 - n) x64 kbps
NSVC_5/6
60
BSC 1 2 BCSUs
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
PCU1 PCU-2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
BSC 2 1 BSCU
PCU-1
61
62
GSM architecture
Air Interface
BSS
Abis Interface
BSC
NSS
A Interface
Ater Interface
BTS
TC MSC/VLR
TCSM
Ater Interface
O&M Interface
NMS
63