Gb Interface Dimensioning

Gb interface Dimensioning

1 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 1
Gb Interface Dimensioning

Nokia Siemens Networks

Academy
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.

2 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 2
Gb Interface Dimensioning

Module Objectives

After completing the module, the student will be able to:

• List different types of Gb interface according to the used transmission
technology
– Gb over FR
– Gb over IP
• Identify the steps to perform Gb dimensioning based on traffic figures
• Explain basic redundancy and load sharing principles in Gb interface

Practice:
• Gb interface dimensioning exercise

Refer to RG20 Documentation:

• Plan and Dimension/Gb EDGE dimensioning

3 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 3
Gb Interface Dimensioning

Gb Interface Dimensioning (BSC-SGSN)

Inputs Needed Output

• Estimated GB interface capacity, • Number of PCU due to Gb capacity

comprising: • Number of NSVCs
– User plane / Control plane • In case of Gb over FR:
– Overhead – Number of Frame Relay Bearer
channels and capacity of the links
– Redundancy and load sharing
– Number of PCM between BSC
• Type of Gb transport solution: and SGSN
– Gb over frame Relay • In case of GB over IP:
– Gb over IP (IPv4 or IPv6) – Capacity in Kbps for Gb
• BSC Type
• PCU type and capacity
• SGSN Capacity
• Used Architecture on the PS Core
network (with or without Gs)
• Use of optional features (Multiple Gb)
4 © Nokia Siemens Networks RA2020AEN20GLN0

Gs is the interface between SGSN and MSC

RA2020AEN20GLN0 4
Gb Interface Dimensioning

Gb Interface Transport technologies

In the Gb interface, two different transport technologies can be used:
 Gb over frame relay (FR)
 Gb over IP (IPv4/IPv6)
Gb over IP has a higher overhead than Gb over frame relay and this has an effect
on the bandwidth usage.

PCU

Abis
Gb over Frame Relay
Gb over IPv4/IPv6

5 © Nokia Siemens Networks RA2020AEN20GLN0

There is no single correct solution that could be used in every planning case. The optimum
transmission solution is case specific and depends on the availability and cost of alternative
transmission solutions and on the existing network infrastructure of theoperator.

RA2020AEN20GLN0 5
Gb Interface Dimensioning

Transmission Solutions for Gb over FR

The transmission solution for the Gb interface can be implemented in different
ways.
1
1 Data Channel going through
TCSM & MSC ET ET
TCSM

2 Using dedicated E1 PCM MSC

lines 2
Transmission ET
3 Data Channel going through ET
a FR Network Network

ET Frame Relay ET
network

SGSN BSC

6 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 6
Gb Interface Dimensioning

Gb-Interface Protocol (FR)

Subnetwork Dependent
SNDCP Convergence Protocol

LLC Logical Link Control

BSSGP BSSGP BSS GPRS protocol layer

Network Service Network Service Network Service

control part control part control part Network
GPRS Service
Signalling FR FR Frame Relay

L1 bis L1 bis Layer 1 physical connection

State of BSC
Services
SGSN
Gb-IF
Physical
Layer

7 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 7
Gb Interface Dimensioning

Gb-Interface Identifier (FR)

BSC

BSSGP BVCI BSSGP Virtual Connection Identifier

Network Service NSEI Network Service Entity

control part NS-VCI Network Service Virtual Connection Identifier

FR DLCI
BC
Data Link Connection Identifier
Bearer Channel

L1 bis

8 © Nokia Siemens Networks RA2020AEN20GLN0

The Frame Relay parameter DLCI (Data Link Connection Identifier) has to be defined unique
between neighbours while the Network Service Parameter NS-VCI (Network Service Virtual
Connection Identifier) and BVCI (BSSGP Virtual Connection Identifier) have to be defined
unique at the end devices. In a simple BSC-SGSN point-to-point connection neighbours are
consequentially end devices.  Parameters have to be the same in BSC and SGCN.
While creation BC, DLCI NS-VCI and NSEI have to be defined. The BVCI will be created
automatically by the System.

RA2020AEN20GLN0 8
Gb Interface Dimensioning

Gb over FR: Capacity of NS-VCI

Given by CIR=Committed Information Rate

TSL PCM-frame
e.g . NS-VCI 16 --> CIR = 64 kBit/s
NS-VCI 17 --> CIR = 96 kBit/s 0
NS-VCI 18 --> CIR = 64 kBit/s

Bearer Channel
1

4
 CIR min = 16 kBit/s
Could be discarded
 Configurable in steps of 16 kBit/s in case of congestion
 Range of CIR can exceed TLS borders
 Sum of CIR capacity of bearer channel

9 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 9
Gb Interface Dimensioning

BSS1
Gb Interface ( over FR) SGSN
NSEI_1 PCU1

PAPU1 NS-VCI_7 BVCI_0

NSEI_1 Bearer Channel_1

BVCI_0 NS-VCI_7 DLCI_16 NS-VCI_2 BVCI_3

DLCI_17 LA
BVCI_3 NS-VCI_2 RA 1
Bearer Channel_2 NSEI_2 PCU2
DLCI_16 BTS_3
NS-VCI_5
NSEI_2 BVCI_0
DLCI_17
NS-VCI_5 BTS_6
BVCI_0 DLCI_18 NS-VCI_8
BVCI_6
NS-VCI_8 NS-VCI_3 RA 2
BVCI_6 Bearer Channel_3
BTS_8
NS-VCI_3 DLCI_16
NSEI_3 PCU3
DLCI_17 BTS_22
NS-VCI_4
BVCI_8
PAPU2 NSEI_3 Bearer Channel_4
NS-VCI_1 BVCI_0
NS-VCI_4
BVCI_8 DLCI_16
NS-VCI_11 BVCI_22
BVCI_0 NS-VCI_1

BVCI_22 NS-VCI_11
Bearer Channel_5

DLCI_16 BSS2
PAPU3 DLCI_17
NSEI_7 NSEI_7 PCU3
LA
BVCI_0 NS-VCI_6 NS-VCI_6 BVCI_0
Bearer Channel_6 RA
BTS_22
BVCI_22 NS-VCI_9 NS-VCI_9 BVCI_22

BSSGP Data
NS Signal

10 © Nokia Siemens Networks FR

RA2020AEN20GLN0 Data & Signal

The following rules have to be heeded:

• NESI must be identical and unique at BSS and SGSN side
• One PCU is equivalent to one NSE (Network Service Entity)
• 1 NSE is connected with one ore more permanent virtual connections called NS-VC
• The BC (Bearer Channel) is defined by PCM and TLS in 64kbit/s steps
• DLCI is unique within one bearer channel
• DLCI has to be identical one both sides only in case of point-to-point FR connections
• NS-VCI capacity can be controlled with Committed Information Rate (CIR) in 16kbit/s steps
• One BC supports several DLCs and can also shared by several NS-VCIs
• The sum of the CIR on the BC has to be less or equal to the capacity of BC
• BVCI has an end-to-end significance
• A cell can be identified by one BVCI
• one NS-VCI supports several BVCs
• BVCI = 0 is reserved for signalling purposes inside one NSE.

Note:
In GB over FR, we don’t have new parameter PSEI.
In GB over IP, we have new parameter PSEI.

RA2020AEN20GLN0 10
Gb Interface Dimensioning

Transmission Solution for Gb over IP

With Gb over IP, it is possible to configure the subnetwork of the Gb interface so

that the subnetwork is IP-based and the physical layer is Ethernet.

Gb Interface

SGSN Flexi BSC

PAPU ESB24
IP network

BCSU P
C
U

11 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 11
Gb Interface Dimensioning

Gb Interface Protocol (IP)

Subnetwork Dependent
SNDCP Convergence Protocol

LLC Logical Link Control

BSS GPRS protocol

BSSGP BSSGP layer
Network Service Network Service Network Service
control part control part control part
GPRS
Signalling UDP UDP User Datagram Protocol layer

IP IP IP address routing

State of L2 L2 Layer 2 data link layer

Services
L1 L1 Layer 1 physical connection
GboIP-IF
Physical
layer BSC SGSN

12 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 12
Gb Interface Dimensioning

Gb Interface Identifier (IP)

BSC

BSSGP BVCI BSSGP Virtual Connection Identifier

NSEI Network Service Entity
Network Service PSEI Packet Network Service Entity
control part Network Service Virtual Connection Identifier
NS-VCI
UDP LPNBR Local User Datagram Protocol Port Number
RPNBR Remote User Datagram Protocl Port Number

IP RIP Remote IP address

RHOST Remote Host Name (If DNS exists)
L2
L1

13 © Nokia Siemens Networks RA2020AEN20GLN0

The Network Service Parameter NS-VCI (Network Service Virtual Connection Identifier) and
BVCI (BSSGP Virtual Connection Identifier) have to be defined unique at the end devices. In a
simple BSC-SGSN point-to-point connection neighbours are consequentially end devices. 
Parameters have to be the same in BSC and SGSN.
While creation LPNBR, RPNBR, NS-VCI and NSEI have to be defined. The BVCI will be
created automatically by the System.
-RDW and RSW are parameters which determine load sharing statuses between NS-VC’s
-RDW and RSW can be considered as part of the Network Service control part since the NSEI
controls load sharing between NS-VC’s

RA2020AEN20GLN0 13
Gb Interface Dimensioning

BSS1
Gb Interface (IP) NSEI_1
PCU1
SGSN
PAPU1 NS-VCI_7 UDP33301 BVCI_0
NSEI_1
NS-VCI_7 UDP33302 BVCI_3
BVCI_0 UDP50001 NS-VCI_2

IP:10.2.77.82 LA
BVCI_3 UDP50002 NS-VCI_2
RA 1
NSEI_2 PCU2
BTS_3
NSEI_2 NS-VCI_5 UDP33303 BVCI_0
NS-VCI_5 BTS_6
UDP50003
BVCI_0 NS-VCI_8 UDP33304
BVCI_6
UDP50004 NS-VCI_8
UDP33305 RA 2
BVCI_6
NS-VCI_3 BTS_8
UDP50005 NS-VCI_3 IP:10.2.77.83
IP:10.2.10.10 NSEI_3 PCU3 BTS_22

PAPU2 NSEI_3 IP
IP BVCI_8
NS-VCI_4 UDP33306
UDP50006 NS-VCI_4
BVCI_8 Network
Network BVCI_0
NS-VCI_1 UDP33307
BVCI_0 UDP50007
NS-VCI_1
UDP33308 BVCI_22
BVCI_22 UDP50008 NS-VCI_11
NS-VCI_11
IP:10.2.77.84
IP:10.2.10.11 BSS2
PAPU3 PCU 1
NSEI_7 NSEI_7
LA
BVCI_0 UDP50009 NS-VCI_6 NS-VCI_6 UDP33301 BVCI_0 RA
BTS_22
BVCI_22 UDP50010 NS-VCI_9 NS-VCI_9 UDP33302 BVCI_22

BSSGP
IP:10.2.10.12 Data IP:10.2.77.113
NS Signal
UDP Data & Signal
IP
14 © Nokia Siemens Networks RA2020AEN20GLN0

• NESI must be identical and unique at BSS and SGSN side

• One PCU is equivalent to one NSE (Network Service Entity)
• 1 NSE is connected with one ore more permanent virtual connections called NS-VC
• The BC (Bearer Channel), DLCI and CIR parameter are NOT existing in the Gb over IP
• BVCI has an end-to-end significance
• A cell can be identified by one BVCI
• one NS-VCI supports several BVCs
• BVCI = 0 is reserved for signalling purposes inside one NSE.
• Each PAPU and PCU has its own IP address..
• When the NS-VC is created the remote IP address and local and remote UDP port numbers
should be specified.

RA2020AEN20GLN0 14
Gb Interface Dimensioning

Gb Dimensioning Overview

• 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 (more relevant).

• Therefore, the main decision needed for Gb dimensioning is the amount of

payload used, on average, for EGPRS traffic during a busy hour.

• In this chapter it is described the Gb EDGE dimensioning based on traffic

figures.

15 © Nokia Siemens Networks RA2020AEN20GLN0

Usually, the Gb traffic value is taken during a busy hour.

RA2020AEN20GLN0 15
Gb Interface Dimensioning

Gb EDGE dimensioning based on traffic figures

•Calculating traffic using subscriber information is more complicated:
– First of all, the total number of subscribers must be known (or the data user
penetration rate)
– Then, a user data amount per busy hour has to be estimated as a total value or based
on assumptions of data usage (WWW, FTP, e-mail, and so on).
•Lets provide example for 2 different Data user profiles (Gb interface Protocols
Headers not included):

EGPRS best effort user information: EGPRS streaming user information:

• 70% of the data users • 10% of the data users
• one e-mail (5 kB) • one e-mail (5 kB)
• three WWW pages (30 kB) • two WWW pages (20 kB)
• one MMS (30 kB) • three minutes streaming @ 50 kbps
• a total of 65 kB per busy hour (BH)  180 sec * 50 kbps= 9 Mb ~ 1 MB)
 520 Kbit/BH • a total of 9.2 Mbit/BH

16 © Nokia Siemens Networks RA2020AEN20GLN0

This method can be used to calculate Gb interface size for both Abis realization:
Dynamic Abis and Packet Abis.

RA2020AEN20GLN0 16
Gb Interface Dimensioning

Gb dim based on traffic figures – The peak margin

•To make sure that the Gb link is not the bottleneck for EGPRS usage, the peak
margin should also be taken into consideration.
•The peak margin of the data volume can deviate a lot depending on, for example,
the amount of data volume, different coding schemes, throughput rates, and
offered services.
•The smaller the size of the Gb link, the bigger its effect on a single user.
•Figure: Peak margin correlation to the Gb link:

In the examples, a 10% peak traffic margin is used.

17 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 17
Gb Interface Dimensioning

Gb dim based on traffic figures – The safety margin

•The safety margin (over dimension) in the Gb link is 25% in all examples.
•The safety margin is used to avoid reaching 100% of the transmission capacity
that can cause several problems, such as the rejection of service and decreased
quality.
•The usage percentage operates as a buffer, so that small changes in user
penetration or data usage do not require re-dimensioning of the Gb interface.

18 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 18
Gb Interface Dimensioning

Gb Overhead

•Nokia Siemens Networks recommends an average IP packet size of 512 bytes

(including the IP header).
•In addition to the length of the IP packets also the overheads vary according to
the different application and protocols used in the Gb interface.
•A smaller packet size would result in a larger overhead percentage

Configuration Layers Userdata + headers, Userdata + headers, Min % Max % Avg %

minimum (Bytes) maximum (Bytes)
Frame Relay SNDCP+LLC+BSSGP 512+3+6+12+4+6=543 512+4+40+63+4+6=629 6.0% 22.8% 14.4 %
Rel'4+NS+FR
Gb over IPV4 SNDCP + LLC + BSSGP 512+3+6+12+4+8+20=565 512+4+40+63+4+8+20=651 10.4% 27.1% 18.8%
Rel'4 + NS + UDP + IP
Gb over IPV6 SNDCP + LLC + BSSGP 512+3+6+12+4+8+40=585 512+4+40+63+4+8+40=671 14.3% 31.1% 22.7%
Rel'4 + NS + UDP + IP

For the overhead (OH), Nokia Siemens Networks recommends that you take the average
of the minimum and maximum overhead percentages to obtain a more realistic figure.
An overhead of 14.5% has been used in the examples with Gb over frame relay.
An overhead of 18.8% has been used in the examples with Gb over IP (IPv4).

19 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 19
Gb Interface Dimensioning

Gb Dimensioning - Exercise

• Dimension the Gb interface based on traffic figures

• The BSC serves 100000 subscribers
• User the Data User profiles from previous slides
• Peak margin: 10%
• Safety Margin: 25%
• Gb over IP solution (Average overhead: 18.8%)

Calculate amount of PCU2-E to support this Gb

20 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 20
Gb Interface Dimensioning

Exercise solution

• EGPRS Best Effort Users – Throughput:

520 kbps
70000 x 520kbps/BH = 70000 x = 10 .08 Mbps
3600 s
• EGPRS Streaming Users – Throughput:
9.2 Mbps
10000 x 9.2Mbps/BH = 10000 x = 25 .56 Mbps
3600 s
• Total:
25 .56 Mbps + 10 .08 Mbps = 35 .64 Mbps
• Including the Peak Margin (+10%) = 39.2Mbps
• Including the Safety Margin (+25%) = 49Mbps
• Including the “Gb over IP” protocols Overhead (+18.8%) = 58.2Mbps
SOLUTION
 Gb Throughput= 58.2 Mbps
 Amount of PCUs = Roundup (58.2 Mbps/ 8 Mbps/PCU) =Roundup ( 7.27) = 8 PCU2-E

21 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 21
Gb Interface Dimensioning

Gb Redundancy and load sharing (Gb over FR)

The need for redundancy in the link depends on the offered services and the market needs.

Figure: one network service entity (NSE) is connected with the SGSN using one NS-VC. The
NS-VC is mapped into one FR bearer channel that goes in one E1 PCM line.
Disadvantages:
1.- NO REDUNDANCY: if E1 is lost, all the PCU traffic will be lost.
2.- PCU throughput on Gb interface can not be maximised:
 Max PCU throughput capacity (all PCU1, PCU2-U, PCU2-D)= 2048 kbps
 Max FR Bearer channel size= 31 TSL x 64 kbps= 1984 kbps
 Max CIT parameter for NS-VC= 1984 kbps
22 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 22
Gb Interface Dimensioning

Gb Redundancy and load sharing (Gb over FR)

Figure: one network service entity (NSE) is divided into two or more network service virtual
connections (NS-VCs); the NS-VCs are mapped into different E1 transmissions lines.
Advantages:
1.- REDUNDANCY: if one E1 is lost, PCU is still connected to the SGSN via 2 nd E1.
2.- PCU throughput on Gb interface can be maximised:
 Max PCU throughput capacity (all PCU1, PCU2-U, PCU2-D)= 2048 kbps
 Size of each FR Bearer = 16 TSL x 64 kbps= 1024 kbps
 CIR parameter for each NS-VC= 1024 kbps
 Total Capacity = 1024 kbps/NSVC x 2 NSVC= 2048kbps
23 © Nokia Siemens Networks RA2020AEN20GLN0

Frame relay load sharing is supported in 2G SGSN. It allows the sending of traffic above the
committed information rate (CIR) on another NS-VC on the same bearer channel.

RA2020AEN20GLN0 23
Gb Interface Dimensioning

Gb Redundancy and load sharing (Gb over FR)

Disadvantage:
 If the NS-VC is 128 kbps and both NS-VCs have traffic of 117 kbps, there is no room for
a new subscriber demanding 22 kbps.
 One big NS-VC of 256 kbps and 234 kbps of load can take one more 22 kbps
subscriber. One NS-VC of double capacity is more efficient than two small ones.
 Therefore, it is recommend to keep the NS-VC links as big as possible.

24 © Nokia Siemens Networks RA2020AEN20GLN0

RA2020AEN20GLN0 24
Gb Interface Dimensioning

Network capabilities
BSC & PCU Type a& Capacity
• In Gb dimensioning, the PCU capacity may be the limiting factor in the BSC, specially
when Gb over IP is used.

SGSN capacity
• The packet processing capacity depends on various factors, such as the packet length
ciphering, use of data compression, and the selected LLC mode. Therefore the actual
SGSN data rate may vary depending on the factors mentioned above. The SGSN
should be able to handle all traffic from the Gb interface.
Gb connection type
• On Gb over IP, the bandwidth of the interface does not limit the throughput.
25 © Nokia Siemens Networks RA2020AEN20GLN0

The maximum rate of one frame relay bearer channel is 31 x 64k (ETSI) or 24 x 64k (ANSI). If
there is more than one bearer in a logical PCU, their maximum summary rate is 32 x 64k.
In the ANSI environment, the Gb interface must be split between two physical ET ports to
support the maximum PCU capacity for Gb over FR.
In case of Packet Abis only PCU2-D and PCU2-E can be taken into account.

RA2020AEN20GLN0 25
Gb Interface Dimensioning

Outputs of Gb EDGE dimensioning

Gb dimensioning outputs:
• total number of timeslots in the Gb interface
• total number payloads in the Gb interface
• total number of network service virtual connections (NS-VCs)
• total number of needed frame relay timeslots or needed data transfer capacity

The values of these outputs should be analysed.

• Based on the analysis, a decision about implementing the Gb interface or re-
dimensioning the interface should be made.
•
The objective of the re-dimensioning should be to:
• optimise the number of PCUs to each BSC,
• re-estimate the traffic to avoid over dimensioning
• optimise the network, based on needs and transmission.

26 © Nokia Siemens Networks RA2020AEN20GLN0

Outputs of Gb EDGE dimensioning

Gb dimensioning results in specific outputs. These outputs are used as input in the next
dimensioning phase, SGSN EDGE dimensioning.
Gb dimensioning outputs:
- total number of timeslots in the Gb interface
- total number payloads in the Gb interface
- total number of network service virtual connections (NS-VCs)
- total number of needed frame relay timeslots or needed data transfer capacity
The values of these outputs should be analysed. Based on the analysis, a decision about
implementing the Gb interface or re-dimensioning the interface should be made. As described
earlier, the dimensioning is often an iterative process, and redoing the dimensioning
calculations may be needed if the output values are not acceptable.
Possible triggers for re-dimensioning:
- too many timeslots per network service entity (NSE) / packet control unit (PCU)
- too much Gb traffic per NSE/PCU
- if the payload is very low (for example, less than six timeslots or if a few simultaneous users
can overload the Gb link) the peak traffic margin should perhaps be higher.
- If the payload is very low (for example, less than six timeslots) there may be a need for
redundancy.
- If the needed capacity is 16 timeslots or higher, it might be better (for transmission reasons)
to implement more NS-VCs so that two NS-VCs belonging to different NSEs are connected to
the same PCM (NSE1 NSVC 1 = timeslots 1-15, NSE 2 NS-VC 1 = timeslots 15-31) to save
transmission costs.
The objective of the re-dimensioning should be to:
- optimise the number of PCUs to each BSC,
- re-estimate the traffic to avoid over dimensioning, and
- optimise the network, based on needs and transmission.

RA2020AEN20GLN0 26