GB Edge Dimensioning

BSC3153
Nokia GSM/EDGE BSS, Rel. BSS13, BSC and

TCSM, Rel. S13, Product Documentation, v.1
Gb EDGE Dimensioning
DN7032484 # Nokia Siemens Networks 1 (38)

Issue 4-0 en
25/03/2008
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.
2 (38) # Nokia Siemens Networks DN7032484

Issue 4-0 en
25/03/2008
Contents
Contents
Contents 3
List of tables 4
List of figures 5
Summary of changes 7
1 Gb EDGE dimensioning 9
1.1 Gb over frame relay 10
1.2 Gb over IP 14
2 Planning process 17
3 Key strategies for EDGE dimensioning 19
4 Dimensioning process 23
4.1 Dimensioning of network elements and interfaces 23
4.2 Gb EDGE dimensioning based on EDAP 27
4.3 Gb EDGE dimensioning based on traffic figures 29
4.3.1 Traffic and quality inputs 29
4.3.2 Network capabilities 33
4.4 Outputs of Gb EDGE dimensioning 35
5 Gb traffic monitoring principles 37

Issue 4-0 en
25/03/2008
List of tables
Table 1. k-factor: short-term traffic distribution 28

Table 2. Overhead with different applications and protocols 31
Table 3. Gb interface connectivity for different PCU types 34

Issue 4-0 en
25/03/2008
List of figures
List of figures
Figure 1. EGPRS traffic multiplexed on the same physical connection as for GSM
traffic on the Ater interface 10
Figure 2. EGPRS traffic multiplexed on the same physical connection as for GSM
Figure 3. GPRS traffic multiplexed on the same physical connection as for GSM
Figure 4. GPRS traffic is concentrated and carried in a packet data network over the
Gb interface 13
Figure 5. GPRS data traffic is carried in dedicated 2 Mbit/s E1 PCM links 14
Figure 6. Available data capacity 20
Figure 7. Required data capacity 21
Figure 8. Available data capacity process 23
Figure 9. Required data capacity process 25
Figure 10. Peak margin correlation to the Gb link size 30
Figure 11. NS-VC load sharing 32
Figure 12. PCU connection 33
Figure 13. Triggers for optimisation 37

Issue 4-0 en
25/03/2008

Issue 4-0 en
25/03/2008
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.
Changes made between issues 4-0 and 3-1
Updated the Gb EDGE dimensioning process with the new computation

method.
Changes made between issues 3-1 and 3-0 lists the changes made to the
document after the Nokia GSM/EDGE BSS, Rel. BSS12, System
Documentation pilot release. The following changes have been made:
.
Table Gb interface connectivity for different PCU types has been
updated in the Network capabilities section in chapter Inputs for Gb
EDGE dimensioning.
The document has been restructured for better usability and the focus is
more on the actual dimensioning process. The following changes have
been made:
. Chapter EDGE dimensioning has been renamed as Planning

process. The dimensioning strategy information has been moved to
chapter Key strategies for EDGE dimensioning and an overview of
the dimensioning steps has been moved to chapter Dimensioning of
network elements and interface and the content has been updated.
. All steps in the dimensioning process are now under the main
chapter Dimensioning process.
. The impact of the used transport technology (Gb over IP or Gb over
frame relay) on PCU output and bandwidth has been added to the
Transport technologies section in chapter Gb EDGE dimensioning.

Issue 4-0 en
25/03/2008
. Calculations for trunk line dimensioning has been added to the Gb

over IP section in chapter Gb EDGE dimensioning.
. A check for peak throughput has been added to chapter Gb EDGE
dimensioning process and to the final step in all examples in chapter
Example cases of Gb EDGE dimensioning.
.
Gb over IP information has been added to table The capability of the
Gb interface for different PCU types in chapter Inputs for Gb EDGE
dimensioning. In addition, information on related software has been
removed because their effect on dimensioning has been taken into
consideration in earlier dimensioning phases.
. Chapter Examples of Gb EDGE dimensioning has been removed. A
dimensioning example is now included in the BSC EDGE
Dimensioning document, in chapter Example of BSS connectivity
dimensioning.
.
Chapter Traffic monitoring principles has been moved to the EDGE
and GPRS Key Performance Indicators document.

Issue 4-0 en
25/03/2008
Gb EDGE dimensioning
1 Gb EDGE dimensioning
These guidelines provide information on dimensioning the Gb interface for
EDGE into an existing GSM network.
The aim is to ensure that the Gb link is large enough to handle the short
term peak traffic of any single EDAP. In addition to this, the target is to
estimate that the Gb link is large enough to support simultaneous traffic of
several EDAPs. This is highly dependent on the traffic distribution.
The EDGE dimensioning guidelines in the BSS system documentation set

cover BTS, Abis, BSC, and Gb dimensioning and some parts of pre-
planning. An example of BSS connectivity dimensioning is included in the
BSC EDGE Dimensioning document.
Gb dimensioning results in specific outputs that are used as input in the

next dimensioning phase, SGSN EDGE dimensioning.
Transport technologies
In the Gb interface, two different transport technologies can be used: Gb

over frame relay or Gb over IP. Gb over IP has a higher overhead than Gb
over frame relay. This has an effect on bandwidth usage.
The transmission solution for the Gb interface can be implemented in

different ways. 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 the operator.

Issue 4-0 en
25/03/2008
1.1 Gb over frame relay

GSM voice traffic is carried between the BTSs and the MSCs through the
Abis (BTS to BSC) and Ater (BSC to transcoders) interfaces. The physical
layers of the Abis and Ater interfaces are based on the ITU-T
recommendations G.703/G.704, where traffic is carried in E1 PCM frames.
The bit rate of one bearer channel is N x 64 kbps, where N is 1-31 (ETSI)
and 1-24 (ANSI).
Voice and data multiplexed
Voice and data traffic can be multiplexed on the same transmission links
that are used for GSM voice traffic on the Ater interface (see figure EGPRS
traffic multiplexed on the same physical connection as for GSM traffic on
the Ater interface). At the BSC, some of the 64 kbps PCM timeslots are
permanently reserved for GPRS traffic and some for GSM traffic. EGPRS
and GSM traffic are transferred together to the digital cross-connection
device (for example, DN2) residing at the MSC/SGSN site. In the digital
cross-connection device, the EGPRS and GSM traffic are separated so
that the EGPRS traffic is carried in dedicated E1/T1 links to the SGSN.
2 Mbit/s PCM
Abis BSC Ater + Frame Relay MSC/SGSN
MUX Transcoders MSC
BSC
BSC
Frame SGSN Ethernet Switch

Relay
Gb-Int. GGSN #1
GGSN #2
Gb
Figure 1. EGPRS traffic multiplexed on the same physical connection as for

GSM traffic on the Ater interface

Issue 4-0 en
25/03/2008
Voice and data separated in the transcoder
EGPRS traffic is multiplexed into the same transmission links that are used
for GSM voice traffic on the Ater interface (see figure EGPRS traffic
multiplexed on the same physical connection as for GSM traffic on the Ater
interface). In the transcoder, the EGPRS and GSM traffic are separated so
that 64 kbps frame relay traffic timeslots are through-connected to the
dedicated E1 links, which are connected to the SGSN.
2 Mbit/s PCM
Abis BSC Ater + Frame Relay MSC/SGSN
Transcoders MSC
BSC
BSC
Frame SGSN Ethernet Switch

Relay
Gb-Int. GGSN #1
GGSN #2
Gb
Figure 2. EGPRS traffic multiplexed on the same physical connection as for

Channels going through the transcoders and MSC
EGPRS traffic is multiplexed into the same transmission links that are used
for GSM voice traffic on the Ater interface. In the transcoder, channels that
go through the transcoder are created and the EGPRS data traffic is
forwarded to the MSC switching matrix. At the MSC, the 64 kbps virtual
channels (VCs) are multiplexed into one or more ET2E cards, which are
connected to the SGSN.

Issue 4-0 en
25/03/2008
Abis BSC MSC/SGSN site

Transcoders MSC
BSC
BSC
2M PCM
SGSN Ethernet Switch
Frame
Relay GGSN #1
GGSN #2
Gb Interface
Figure 3. GPRS traffic multiplexed on the same physical connection as for

Traffic streams concentrated in the FR switch
To use the capacity more efficiently or cost effectively, it is possible to

concentrate the traffic streams coming from several BSCs and packet
control units (PCUs) into one aggregate line towards the SGSN.
This concentrated traffic can be multiplexed into the same physical link
that is used for GSM traffic on the Ater interface. Alternatively, it can be
carried over to the SGSN site in a compatible packet data network (PDN)
(see figure GPRS traffic is concentrated and carried in a packet data
network over the Gb interface).
There are several solutions that can be used to implement this method.
Again, there is no single correct solution that works with each planning
case. However, there are a few basic rules for the implementation and
dimensioning. The data network used for transmission does not
necessarily have to be a frame relay network. The frame relay traffic can
be run over different kinds of networks, such as ATM. At either end of the
connection, a frame relay switch or similar equipment is required for the
connection to the packet data network. The switches must be able to
connect to the E1/T1 link coming from the BSC with a physical interface,
such as G.703, and to adapt to the PDN access point interface. In addition,
the switch must be able to do the correct protocol conversion (for example,
convert FR into ATM, and vice versa).

Issue 4-0 en
25/03/2008

Transcoders MSC
BSC
BSC

Packet Data GGSN #1
FR Switch Network GGSN #2
(FR, ATM, etc.)
FR Switch
Gb Interface
Figure 4. GPRS traffic is concentrated and carried in a packet data network

over the Gb interface
Dedicated 2 Mbit/s E1 PCM links
In this transmission option, one or more (a maximum of eight per BSC) E1/
T1 PCM links per BSC are dedicated only for GPRS data traffic (see figure
GPRS data traffic is carried in dedicated 2 Mbit/s E1 PCM links). If, for
example, 15 or more 64 kbps Gb interfaces are required for one BSC, it is
reasonable to dedicate the needed amount of 2 Mbit/s E1 interfaces only
for data traffic. If, for example, 18 PCM timeslots are needed for a BSC,
one E1 PCM interface of an ET2E card at the BSC and SGSN could be
dedicated only for GPRS data traffic.

Issue 4-0 en
25/03/2008

Transcoders MSC
BSC
BSC

2 M PCM E1 links GGSN #1
GGSN #2
Frame Relay
Gb Interface
Figure 5. GPRS data traffic is carried in dedicated 2 Mbit/s E1 PCM links
For more information on Gb over frame relay, see chapter Nokia GPRS,
section Frame Relay and Gb Interface in (E)GPRS System Feature
Description.
1.2 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.
When Gb over IP is used, the data from all PCUs and the data from the
elements that use IP traffic in other BSCs can be combined with switches
or routers into one or two trunk lines. The dimensioning of the trunk line
can be based on one of the following calculations:
.
The capacity of the trunk line = PCU + the total amount of traffic of
the other elements
. The capacity of the trunk line = the amount of traffic of the largest
traffic-generating element
Often the capacity of the trunk line is a combination of the above-

mentioned calculations.
For more information on Gb over IP, see Gb over IP System Feature

Description.

Issue 4-0 en
25/03/2008
Related topics
. document BTS EDGE Dimensioning

. document Abis EDGE Dimensioning
. document BSC EDGE Dimensioning

Issue 4-0 en
25/03/2008

Issue 4-0 en
25/03/2008
Planning process
2 Planning process
Dimensioning is the part of network planning that produces a master plan
indicating the selected network architecture and the number of network
nodes and communication links required during the roll-out of the network.
The following phases are included in the network planning process:
. dimensioning
. pre-planning
. detailed planning
. implementation
.
optimisation
Network dimensioning is done by creating a traffic model of the network

and selecting the equipment to support it. Dimensioning takes into account
the available equipment specifications, business plans, site availability and
type, quality of service (QoS) requirements, and charging cases.
The EDGE dimensioning guidelines in the BSS system documentation set

cover BTS, Abis, BSC, Gb, and SGSN dimensioning and some parts of
pre-planning.
These guidelines focus on dimensioning. Network optimisation is not

included in the guidelines.
The dimensioning guidelines consist of both hardware dimensioning and

software dimensioning. Hardware dimensioning defines how many traffic
type and traffic volume dependent hardware units are needed in the BTS,
BSC, and SGSN to support the targeted traffic and service performance.
Software dimensioning defines the key system settings associated with
traffic dependent units. You can modify the existing configuration once the

Issue 4-0 en
25/03/2008
amount of needed traffic dependent hardware and the associated software

settings have been defined. If necessary, you can place an order for
additional products and licences, based on the agreed standard
configurations.
Nokia Siemens Networks has a wide range of services and training

available to support all phases of system planning, deployment, and
optimisation. Contact your local Nokia Siemens Networks representative
for details.

Issue 4-0 en
25/03/2008
Key strategies for EDGE dimensioning
3 Key strategies for EDGE dimensioning

The dimensioning of a network can be based on two different approaches:
.
available data capacity
. required data capacity
The dimensioning strategy must be selected before the BTS dimensioning

begins.
Available data capacity
Available data capacity strategy is used when you want to introduce EDGE
to an existing network. Dimensioning determines how much traffic is
available through the current system. The dimensioning input is a pre-
defined system configuration. The dimensioning output is the available
traffic volume with a defined performance level. Alternatively, you can
calculate available capacities for different alternative configurations.

Issue 4-0 en
25/03/2008
All current resources in a cell

Input information:
Current network configuration
Current equipment’s
EDGE capability
Average voice traffic Average
resource usage available Current network’s voice
resources performance
Current network’s radio

conditions (C/N, C/I)
Planned EDGE data resources

Average voice traffic EDGE data are used for voice traffic
resource usage when needed
Figure 6. Available data capacity
Required data capacity
Required data capacity strategy is used when you want to design a

network that supports the defined amount of traffic and targeted
performance level. The dimensioning inputs are traffic volume, type, and
performance requirements. The dimensioning output is the needed
amount of traffic dependent hardware and the associated software
configurations.

Issue 4-0 en
25/03/2008
Key strategies for EDGE dimensioning
All current resources in a cell Input information:
Average voice traffic Current network configuration

resource usage
Current equipment’s
Average available EDGE capability
resources
Current network’s voice
performance
Current network’s radio

conditions (C/N, C/I)
Required EDGE Capacity
Required EDGE capacity
Required EDGE performance
Shared Dedicated
Planned EDGE data
resources may be fully or
EDGE data are at least partially
dedicated to data traffic.
Average voice traffic Dedicated resources are not
resource usage used for voice traffic.
Figure 7. Required data capacity

Issue 4-0 en
25/03/2008

Issue 4-0 en
25/03/2008
Dimensioning process
4 Dimensioning process
4.1 Dimensioning of network elements and interfaces

The dimensioning of GSM EDGE network elements and interfaces is
proposed to be done as described in this section. Depending on the
dimensioning strategy, you can use either the available capacity strategy
or the required capacity strategy. At first, the input for BTS dimensioning
has to be agreed. Once this has been done, the output of each element or
interface serves as the input for the next phase.
Available data capacity strategy
The dimensioning process of the available data strategy is illustrated in

figure Available data capacity process.
1. Estimate the average available data capacity and

throughput.
2. Use existing TRX hardware capacity.
3.-6. Dimension the rest of the elements according to the
available capacity estimate done in step 1.
1 3 4 5 6
2
TSL
TRX
Cell PCU Basic unit
Abis Gb
BTS BSC 2G SGSN
Figure 8. Available data capacity process

Issue 4-0 en
25/03/2008
The available data capacity strategy consists of the following steps:
1. Definition of the input information

. Select the data deployment strategy.
.
Calculate the existing traffic load.
. Review the hardware/software capability.
.
Define the BTS/transceiver (TRX) configuration.
. Simulate the coverage and interference performance (carrier-
to-noise ratio (C/N), carrier-to-interference ratio (C/I)).
2. BTS dimensioning
.
Estimate throughput/ radio timeslot (RTSL).
. Calculate the available capacity/number of RTSLs based on
the circuit-switched (CS) traffic needs.
. Verify the dimensioning outcome.
The dimensioning process results in throughput/RTSL, territory size/
BTS, guaranteed/not guaranteed throughput, RTSL configuration of
TRXs, numbers of TRXs per cell, and the simulation results.
3. Abis dimensioning
. Use the output of BTS dimensioning as the input.
.
Define the EGPRS dynamic Abis pool (EDAP) size.
The dimensioning process results in the size of each EDAP.
4. BSC dimensioning
. Use the output of BTS and Abis dimensioning as the input.
. Verify the amount of packet control units (PCUs).
.
Verify the number of BSC signalling units (BCSU) and
Exchange Terminals (ETs).
.
Verify the Gb requirements for BSC dimensioning.
. Define the BSC configuration.
.
Perform a use check.
The dimensioning process results in the number and type of BSCs,
the number and type of PCUs, and the number and size of Gb
interfaces.
5. Gb dimensioning
. Use the output of BTS and BSC dimensioning as the input.
. Calculate the amount of payload.
.
Verify the number of network service elements (NSEs) and
BCSUs.
.
Estimate the need for redundant links.
. Evaluate the results.

Issue 4-0 en
25/03/2008
The dimensioning process results in the number of timeslots,

number of payloads, number of network service virtual connections
(NS-VCs), and number of frame relay timeslots/data transfer
capacity.
6. SGSN dimensioning
.
Use the output of BTS and Gb dimensioning as the input.
. Define the maximum number of attached subscribers and
packet data protocol (PDP) contexts to be expected in the
routing area (RA) served by the SGSN.
.
Calculate the amount of total data payload (generated user
traffic) during a busy hour.
. Verify the needed basic units/SGSN according to the
previously calculated generated traffic and the expected
subscribers served in the area.
.
Check all other restrictions, especially the expected mobility
profiles of the users versus the dynamic capacity of the SGSN.
The dimensioning process results in the number of packet
processing units (PAPUs) and signalling and mobility management
units (SMMUs).
Required data capacity strategy
The dimensioning process of the required data strategy is illustrated in

figure Required data capacity process.
1. Calculate the required TSL count based on required data

capacity and throughput.
2. Calculate the required amount of TRX hardware.
3.-6. Dimension the rest of the elements according to the
required capacity calculation done in step 1.
1 3 4 5 6
2
TSL
TRX
Cell PCU Basic unit
Abis Gb
BTS BSC 2G SGSN
Figure 9. Required data capacity process

Issue 4-0 en
25/03/2008
The required data capacity strategy consists of the following steps:
1. Definition of the input information

. Select the data deployment strategy.
.
Determine the targeted traffic capacity.
. Estimate the traffic mix.
.
Review the hardware/software capability.
. Define the BTS/TRX configuration.
.
Simulate the coverage and interference performance (C/N, C/
I).
2. BTS dimensioning
. Calculate the required throughput.
. Estimate throughput/RTSL.
. Calculate the required number of RTSLs.
. Verify the dimensioning outcome.
The dimensioning process results in throughput/RTSL, territory size/
BTS, guaranteed/not guaranteed throughput, TSL configuration of
TRXs, number of TRXs/cell, and the simulation results.
3. Abis dimensioning
.
Use the output of BTS dimensioning as the input.
. Define the EDAP size.
The dimensioning process results in the size of each EDAP.
4. BSC dimensioning
. Use the output of BTS and Abis dimensioning as the input.
.
Calculate the needed amount of PCUs.
. Calculate the number of BCSUs and ETs.
.
Calculate the Gb requirements for BSC dimensioning.
. Define the BSC configuration.
.
Perform a use check.
The dimensioning process results in the number and type of BSCs,
the number and type of PCUs, and the number and size of Gb
interfaces.
5. Gb dimensioning
. Use the output of BTS and BSC dimensioning as the input.
. Calculate the amount of payload.
.
Calculate the required number of NSEs and BCSUs.
. Estimate the need for redundant links.
.
Evaluate the results.

Issue 4-0 en
25/03/2008
The dimensioning process results in the number of timeslots, the

number payloads, the number of NS-VCs, and the number of frame
relay timeslots/data transfer capacity.
6. SGSN dimensioning
. Use the output of BTS and Gb dimensioning as the input.
.
Define the required number of attached subscribers and PDP
contexts to be expected in the RA served by the SGSN.
.
Calculate the amount of total data payload (generated user
traffic) during a busy hour.
.
Calculate the needed basic units/SGSN according to the
previously calculated generated traffic and the expected
subscribers served in the area.
. Check all other restrictions, especially the expected mobility
profiles of the users versus the dynamic capacity of the SGSN.
The dimensioning process results in the number of PAPUs and
SMMUs.
4.2 Gb EDGE dimensioning based on EDAP

The dimensioning of Gb for EGPRS traffic is a straightforward process.
Each PCU has typically one Gb link towards the SGSN. In case of
redundant Gb, two independent links are needed. The outcome of the Gb
link dimensioning process is the average size of the Gb link to carry the
data traffic forecast. This part of the process affects SGSN dimensioning
and should be conducted together with PS Core planning. The Gb should
be capable of supporting the instantaneous data traffic being carried by all
cells connected to a particular PCU. If there is insufficient capacity the
effective user rate at the radio cell will be reduced.
The following equation is used to calculate the average Gb link size (=

Frame Relay Bearer Channel capacity).
Average Gb size = k * Average EDAP size for that network area.
The k-factor is based on the estimate of the short term traffic distribution. If
no specific information about the distribution is available, it is
recommended to use the default values.
The table below gives the k-values. The theoretical minimum k-value
(1.25) is assuming that the short term traffic is totally unequal, meaning
that when one EDAP is full of traffic the others within the same PCU have
no traffic. The theoretical maximum k-value is the number of EDAPs

Issue 4-0 en
25/03/2008
allocated into one PCU. This assumes that all the EDAPs are heavily
loaded at the same short term period and the Gb link is supposed to carry
such traffic without additional delays. The %-value in the table indicates
the portion of traffic in the second most loaded EDAP when the most
loaded EDAP is full of traffic. And in general it indicates the portion of traffic
in ith loaded EDAP comaper to (i-1)th loaded EDAP. In reality, some delay
is allowed during heavy simultaneous short term traffic bursts and thus it is
assumed that k-values greater than 2 are rare.
Table 1. k-factor: short-term traffic distribution
Unequal (low likelihood of heavy Default Equal (high likelihood of heavy

simultaneous short term traffic) simultaneous short term traffic)
30% 50% 70%
1.4 2 3
During the planning phase, when individual EDAPs are associated to

PCUs, more accurate values for individual Gb links are calculated taking
into account the usage of individual E1/T1 links. To make it easier to
consider other than recommended k-values some impact calculations is
done. selections.
Upgrading existing Frame Relay based links into IP based links
The Gb link traffic is measured for periods long enough to contain at least
weekly behavior of the mobile users. The highest sum of hourly Gb link
traffic figures over the links, which are going to share the planned WAN
connection is taken as a base traffic. This base traffic is corrected using
traffic growth estimate. The individual WAN link load by the corrected base
traffic and possible other traffic shall not exceed 70%. The measured traffic
contains the Gb protocol overhead and thus the overhead calculation is
not required.
Dimensioning Gb over IP
Typically, there are some estimates available for the total traffic volumes
between the SGSN and the BSC site. The individual cell level figures are
typically given for cell level busy hour (BH). Due to the fact that the cell
level BHs do not occur at the same time, the sum of cell level BH could
lead to over dimensioning. The theoretical maximum Gb traffic is 2Mbps *
the number of logical PCUs. The minimum practical WAN capacity for Gb
is 2 * E1/T1 to support redundancy. It is rare to have peak PS traffic on all
PCUs at the same time and thus the practical estimate for required WAN
capacity for Gb traffic is 10% to 40% of the theoretical maximum, however,
at least the 2 * E1/T1.

Issue 4-0 en
25/03/2008
4.3 Gb EDGE dimensioning based on traffic figures
4.3.1 Traffic and quality inputs
Data volume
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.
Therefore, the main decision needed for Gb dimensioning is the amount of
payload used, on average, for EGPRS traffic during a busy hour and the
deviation of the traffic between the peak and minimum values (this also
provides the difference between the peak and average values).
Data volume per BSC can be calculated (or estimated) as the total data
volume per BSC or based on subscriber information. One option is to
estimate the total data volume going through a BSC during a busy hour,
based on the available average throughput for EGPRS enabled timeslots
in the BSC. A more accurate option is to use traffic monitoring for the
flawless calculation of peak traffic during the busiest moment of a busy
hour.
Calculating traffic using subscriber information is more complicated. First

of all, the total number of subscribers must be known (or the data user
penetration value). 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).
EGPRS best effort user information (example values, headers included):
.
70% of the data users
. one e-mail (5 kB)
.
three WWW pages (30 kB)
. one MMS (30 kB)
. a total of 65 kB per busy hour (BH) = 520 kbit/BH
EGPRS streaming user information:
. 10% of the of the data users

.
one e-mail (5 kB)
. two WWW pages (20 kB)

Issue 4-0 en
25/03/2008
. three minutes streaming (~ 50 kbps → 9 Mb ~ 1 MB)

. a total of 9.2 Mbit/BH
To make sure that the Gb link is not the bottleneck for EGPRS usage, also
the peak margin should 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. In the examples, a 10% peak traffic margin is used. Figure
Peak margin correlation to the Gb link size shows an example of how peak
margins correlate to link capacity.
Peak margin % example

100
90
80
70
Peak margin %
60
50
40
30
20
10
0
00
0
00
00
00
0
0
0
0
0
0
50
90
70
30
10
13
11
19
15
17
Gb link size
GPRS
EDGE
Figure 10. Peak margin correlation to the Gb link size
The safety margin in the Gb link is 25% in all examples. The safety margin
is used to avoid reaching 100% of the PCM usage situations 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 redimensioning of the Gb
interface.

Issue 4-0 en
25/03/2008
Gb overhead
Usually, the Gb traffic per user value is taken during a busy hour. The
average packet size of 512 bytes, including the IP header, is
recommended.
In addition to the length of the IP packets also the overheads vary

according to the different application and protocols. A smaller packet size
results in a larger overhead percentage.
Table 2. Overhead with different applications and protocols
Configuration Layers Userdata + Userdata Min. Max.

headers, + headers % %
minimum maximum
Frame relay SNDCP+LLC 512+3+6+12+ 512+4+40 Min. Max. %
+BSSGP 4+6 = 543 +63+4+6 = %
Rel'4+NS+FR 629
Gb over IP SNDC +LLC 512+3+6+12+4 512+4+40 10.4 27.1
(IPv4/IPv6) +BSSGP +8+ 20/40 = +63+4+8+
Rel'4+NS 565/585 20/40 =
+UDP+IP 656/676
USERPACKET = IPHEADER + USERDATA
For the overhead (OH), it is recommended to 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 examples with Gb
over IP.
Percentage OH = GbOH/USERPACKETSIZE
[{(OHmax/packetsize) + (OHmin/packetsize)}/2] %
Frame relay: [{(117/512) + (31/512)}/2] % = 14.5%
Gb over IP, IPv4: [{(139/512) + (53/512)}/2] % = 18.8%

Issue 4-0 en
25/03/2008
Redundancy and load sharing
The need for redundancy in the link depends on the offered services and
the market needs. When the payload from the BSC exceeds the capacity
of transmission (one PCM), it is recommended to perform dimensioning of
the Gb interface so that it also supports redundancy and load sharing. This
means that one network service entity (NSE) is divided into two or more
network service virtual connections (NS-VCs): the NS-VCs are divided into
separate transmissions.
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. The pacet control unit (PCU) decides the load
sharing of the NS-VCs in uplink for the time one TBF is allocated. The PCU
decision is based on the temporary logical link identity (TLLI), which in turn
is allocated by the SGSN.
E1 E1
BSC SGSN
Bearer CH. 1
NSE1
PCU 1
NSVC_1
NSE 1
NSVC 1
E1 E1
BSC SGSN
Bearer CH. 1 NSE1

PCU 1
NSE 1 NSVC_1
NSVC 1
NSVC 2 Bearer CH. 2
NSVC_2
Figure 11. NS-VC load sharing

Issue 4-0 en
25/03/2008
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.
4.3.2 Network capabilities
BSC type and capacity (the number of PCUs)
In Gb dimensioning, the PCU capacity may be the limiting factor in the

BSC.
SGSN
ETs GSWB Gb
Abis ET
ETs Packets in FR
Packets in
TRAU frames
4 Mbit/s internal PCM FR: bearer channel + optional

256 channels load sharing redundant bearer (2 Mbit/s)
PCU
Figure 12. PCU connection
Usually, the performance of different BSC hardware/software releases is

compared by using the maximum values of the transceivers (TRXs)
supported by a BSC or throughput (kbps) delivered through a BSC. The
maximum number of TRXs that can be connected to a BSC depends on
the type of the BSC:
. BSCi: 512
. BSC2i: 512
. BSC3i 660: 660
. BSC3i 1000: 1000
.
BSC3i 2000: 2000

Issue 4-0 en
25/03/2008
Table Gb interface connectivity for different PCU types shows the PCU
capability for the Gb interface towards the SGSN. The table shows the
physical PCUs. Note that there are two logical PCUs in PCU-B and PCU-
2D.
Table 3. Gb interface connectivity for different PCU types
PCU type BSC type Gb over FR

PCU BSCi, BSC2i 32 x 64 kbit/s
PCU-S BSCi, BSC2i 32 x 64 kbit/s
PCU-T BSCi, BSC2i 32 x 64 kbit/s
PCU-B BSC3i 2 x 32 x 64 kbit/s
PCU2-U BSC2i 32 x 64 kbit/s
PCU2-D BSC3i 2 x 32 x 64 kbit/s
Note
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.
A PCU can be connected to the SGSN either via the Gb over frame relay
or Gb over IP interface but not via both interfaces simultaneously. The IP
interface for a PCU can be IPv4 or IPv6 but not both.
The PCU capacity of the Abis channels, BTS, TRX, and EGPRS dynamic
Abis pool (EDAP) under the PCU cannot be exceeded. For more
information, see the BSC EDGE Dimensioning document.
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.

Issue 4-0 en
25/03/2008
Gb connection type
The selection of the connection type depends on the hardware and

software versions in the SGSN and BSC and on the available transmission
alternatives in the backbone network.
The capacity of the Gb interface remains the same in BSC, regardless of

whether IP or FR is used as the transport technology.
4.4 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 redimensioning 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 redimensioning:
. 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.

Issue 4-0 en
25/03/2008
. 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 NS-VC 1 = timeslots 1-15, NSE 2 NS-VC 1 = timeslots 15-31)
to save transmission costs.
The objective of the redimensioning 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.

Issue 4-0 en
25/03/2008
Gb traffic monitoring principles
5 Gb traffic monitoring principles

The most important Gb traffic monitoring areas are the following.
.
downlink Gb load
. total EGPRS uplink/downlink payload in BSC
.
SGSN data (the amount of data passed in the uplink and downlink
direction in the SGSN, and the resource usage)
. GPRS session management counters (PDP context related
information)
Monitoring these measurements gives the operator an initial idea of how

well the current data traffic reflects the Gb dimensioning (including the
three main capacity restrictions) and whether there is a need to
reconfigure the Gb capacity (see figure Triggers for optimisation).
Triggers for redimensioning:

-Too many TSLs per NSE/PCU
Gb dimensioning -Too much Gb traffic per PCU
-SGSN capacity
-Transmission capacity exceeded
Configurations: To do in redimensioning:
-Total number and type of Gb -Optimise the number of PSCs
-Total number and type of PCUs -Re-estimate traffic to avoid
-Peak payload and services over dimensioning
-SGSN limitations -Optimise transmission
Figure 13. Triggers for optimisation

Issue 4-0 en
25/03/2008
For information on EDGE-related KPIs, see EDGE and GPRS Key

Performance Indicators.

Issue 4-0 en
25/03/2008

GB Edge Dimensioning

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

GB Edge Dimensioning

Enviado por

Direitos autorais:

Formatos disponíveis

BSC3153

Nokia GSM/EDGE BSS, Rel. BSS13, BSC and

DN7032484 # Nokia Siemens Networks 1 (38)

2 (38) # Nokia Siemens Networks DN7032484

3 Key strategies for EDGE dimensioning 19

5 Gb traffic monitoring principles 37

DN7032484 # Nokia Siemens Networks 3 (38)

Table 1. k-factor: short-term traffic distribution 28

4 (38) # Nokia Siemens Networks DN7032484

DN7032484 # Nokia Siemens Networks 5 (38)

6 (38) # Nokia Siemens Networks DN7032484

Changes between document issues are cumulative. Therefore, the latest

Changes made between issues 4-0 and 3-1

Updated the Gb EDGE dimensioning process with the new computation

Changes made between issues 3-1 and 3-0

Changes made between issues 3-0 and 2-0

. Chapter EDGE dimensioning has been renamed as Planning

DN7032484 # Nokia Siemens Networks 7 (38)

. Calculations for trunk line dimensioning has been added to the Gb

8 (38) # Nokia Siemens Networks DN7032484

The EDGE dimensioning guidelines in the BSS system documentation set

Gb dimensioning results in specific outputs that are used as input in the

In the Gb interface, two different transport technologies can be used: Gb

The transmission solution for the Gb interface can be implemented in

DN7032484 # Nokia Siemens Networks 9 (38)

1.1 Gb over frame relay

Voice and data multiplexed

Frame SGSN Ethernet Switch

Figure 1. EGPRS traffic multiplexed on the same physical connection as for

10 (38) # Nokia Siemens Networks DN7032484

Voice and data separated in the transcoder

Frame SGSN Ethernet Switch

Figure 2. EGPRS traffic multiplexed on the same physical connection as for

Channels going through the transcoders and MSC

DN7032484 # Nokia Siemens Networks 11 (38)

Abis BSC MSC/SGSN site

Figure 3. GPRS traffic multiplexed on the same physical connection as for

Traffic streams concentrated in the FR switch

To use the capacity more efficiently or cost effectively, it is possible to

12 (38) # Nokia Siemens Networks DN7032484

Abis BSC MSC/SGSN site

SGSN Ethernet Switch

Figure 4. GPRS traffic is concentrated and carried in a packet data network

Dedicated 2 Mbit/s E1 PCM links

DN7032484 # Nokia Siemens Networks 13 (38)

Abis BSC MSC/SGSN site

SGSN Ethernet Switch

Figure 5. GPRS data traffic is carried in dedicated 2 Mbit/s E1 PCM links

Often the capacity of the trunk line is a combination of the above-

For more information on Gb over IP, see Gb over IP System Feature

14 (38) # Nokia Siemens Networks DN7032484

. document BTS EDGE Dimensioning

DN7032484 # Nokia Siemens Networks 15 (38)

16 (38) # Nokia Siemens Networks DN7032484

The following phases are included in the network planning process:

Network dimensioning is done by creating a traffic model of the network

The EDGE dimensioning guidelines in the BSS system documentation set

These guidelines focus on dimensioning. Network optimisation is not

The dimensioning guidelines consist of both hardware dimensioning and

DN7032484 # Nokia Siemens Networks 17 (38)

amount of needed traffic dependent hardware and the associated software

Nokia Siemens Networks has a wide range of services and training