BSC EDGE Dimension Ing

BSC3120 Nokia GSM/EDGE BSS12 System Documentation
BSC EDGE Dimensioning
DN7032469 Issue 3-0 en draft
# Nokia Corporation
1 (57)
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is not an official customer document and Nokia Networks does not take responsibility for any errors or omissions in this document. No part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia Networks and the customer. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. UNDER NO CIRCUMSTANCES SHALL NOKIA BE RESPONSIBLE FOR ANY LOSS OF USE, DATA, OR INCOME, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, PROPERTY DAMAGE, PERSONAL INJURY OR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES HOWSOEVER CAUSED. THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THIS DOCUMENT. NOKIA RESERVES THE RIGHT TO REVISE THIS DOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA and Nokia Connecting People are registered trademarks of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Corporation 2006. All rights reserved. Reproduction, transfer, distribution or storage of part or all of the contents in this document in any form without the prior written permission of Nokia is prohibited.
2 (57)
# Nokia Corporation
Contents
Contents
Contents 3 Summary of changes 5 1 2 3 4 5 5.1 6 6.1 6.2 6.3 6.3.1 6.3.2 6.4 6.5 6.6 7 7.1 7.2 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.4 7.4.1 7.4.2 7.4.3 7.4.4 7.5 8 BSC EDGE dimensioning 7 Planning process 9 Key strategies for EDGE dimensioning 11 Prerequisites for BSC EDGE dimensioning 13 BSC capacity 15 EGPRS-related BSC elements 16
Dimensioning process 23 Dimensioning of network elements and interfaces 23 BSC EDGE dimensioning process 27 Inputs for BSC EDGE dimensioning 29 Network capability 30 Input from Abis and BTS dimensioning 33 PCU calculations for BSC EDGE dimensioning 34 Outputs of BSC EDGE dimensioning 35 Evaluation of the BSC dimensioning results 37 Example of BSS connectivity dimensioning 39 BSS connectivity dimensioning 39 Dimensioning inputs 40 Radio interface capacity 41 Configuration before (E)GPRS 41 (E)GPRS deployment scenarios 43 Available capacity 44 Required capacity 48 Connectivity capacity 48 Default GPRS capacity (CDEF) 48 EDAP 49 PCU 53 Gb link dimensioning 55 Results of BSS connectivity dimensioning 55 BSC traffic monitoring principles 57
# Nokia Corporation
3 (57)
4 (57)
# Nokia Corporation
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 3-0 and 2-0
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. Chapter Prerequisites for BSC EDGE dimensioning has been added. Information related to the BSC capacity has been moved from chapter BSC EDGE dimensioning to chapter BSC capacity. In addition, information on digital signal processor (DSP) has been removed because it is not directly related to dimensioning. The contents of chapter Inputs for BSC EDGE dimensioning has been updated. Information on software related to dimensioning has been moved to the BTS EDGE Dimensioning document. Chapter BSC EDGE dimensioning process and calculations has been split into two separate chapters: BSC EDGE dimensioning process and PCU calculations for BSC EDGE dimensioning, and the content has been updated. In addition, the calculation formula has been simplified. Chapter Outputs of BSC EDGE dimensioning has been updated and reorganised according to the used strategy. Chapter Examples of BSC EDGE dimensioning has been removed. A dimensioning example is now included in chapter Example of BSS connectivity dimensioning.
# Nokia Corporation
5 (57)
Chapter Traffic monitoring principles has been moved to the EDGE and GPRS Key Performance Indicators document. Information on BSC3i 1000 and BSC3i 2000 has been added.
Changes made between issues 2-0 and 1-0
The general description of BSC has been moved to chapter Nokia Base Station Controller in Nokia Base Station Subsystem. Some PCU information has been moved to chapter Packet Control Unit (PCU) hardware in BSC in (E)GPRS System Feature Description. The information that the outputs of BSC dimensioning are used as inputs for Gb dimensioning has been added to BSC EDGE dimensioning and Outputs of BSC EDGE dimensioning. The inputs in Inputs for BSC EDGE dimensioning have been reorganised into the following categories:
.
Traffic and quality inputs Network capabilities
The calculations in Examples of BSC EDGE dimensioning have been modified.
BSC traffic monitoring principles has been added.

The radio timeslot terminology has been unified.
6 (57)
# Nokia Corporation
BSC EDGE dimensioning
BSC EDGE dimensioning

The aim of these guidelines is to give basic dimensioning information for BSC equipment when there is both circuit-switched (CS) and EGPRS traffic in the radio network. The dimensioning guidelines are related to EGPRS traffic and, therefore, only BSC hardware or software elements that have an impact on EGPRS traffic have been analysed. Voice traffic volume is not considered in BSC dimensioning and, because of this, Ater and transcoder dimensioning is not included in these guidelines. 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 are related to 3GPP Releases 4 and 5, Nokia software Release BSS12, the BSC products BSCi, BSC2i, and BSC3i, and to other relevant equipment related to these BSC products. BSC dimensioning results in specific outputs that are used as input in the next dimensioning phase, Gb EDGE dimensioning.
Terms and definitions
The following terms are used in these guidelines: GPRS General Packet Radio Service (GPRS) provides packet data radio access for GSM mobile stations. It upgrades GSM data services to allow an interface with local area networks (LANs), wide area networks (WANs), and the Internet. Enhanced data rates for GSM evolution (EDGE) enhances GSM networks with 3rd generation-type capabilities. With the new 8-PSK modulations, EDGE is capable of trebling the current GSM radio interface data throughputs. EDGE boosts packet-switched (PS) services. Enhanced GPRS (EGPRS) offers up to 59.2 kbit/s on one radio timeslot (RTSL). Refers to both the GPRS and the EDGE technology.
EDGE
(E)GPRS
# Nokia Corporation
7 (57)
EDAP
Master channel
Slave channel
In EDGE, the Abis interface has a dynamic part called EGPRS dynamic Abis pool (EDAP). It differs from the GSM (and GPRS) transmission networks, where the Abis interface is static. The shared timeslots can be shared by the TRXs belonging to the same BCF. A 16 kbit/s channel used for the allocation of an EGPRS channel out of the EDAP in the Nokia dynamic Abis. Not a part of the EDAP. A 16 kbit/s channel belonging to an EDAP used for the allocation of extra capacity required by an EGPRS call with a coding scheme that is different from CS-1 or MCS1.
Related topics
.
BTS EDGE Dimensioning Abis EDGE Dimensioning Gb EDGE Dimensioning SGSN EDGE Dimensioning
8 (57)
# Nokia Corporation
Planning process
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 modernisation
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 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 Corporation
9 (57)
Nokia has a wide range of services and training available to support all phases of system planning, deployment, and optimisation. Contact your local Nokia representative for details.
10 (57)
# Nokia Corporation
Key strategies for EDGE dimensioning
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.
All current resources in a cell Input information: Current network configuration Current equipments EDGE capability Current networks voice performance Current networks radio conditions (C/N, C/I)
Average voice traffic resource usage
Average available resources
Average voice traffic resource usage
EDGE data
Planned EDGE data resources are used for voice traffic when needed
Figure 1.
Available data capacity
# Nokia Corporation
11 (57)
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.
All current resources in a cell Average voice traffic resource usage Average available resources
Input information: Current network configuration Current equipments EDGE capability Current networks voice performance Current networks radio conditions (C/N, C/I) Required EDGE capacity Required EDGE performance
Required EDGE Capacity
Shared
Dedicated
EDGE data Average voice traffic resource usage
Planned EDGE data resources may be fully or are at least partially dedicated to data traffic. Dedicated resources are not used for voice traffic.
Figure 2.
Required data capacity
12 (57)
# Nokia Corporation
Prerequisites for BSC EDGE dimensioning
Prerequisites for BSC EDGE dimensioning

Input summary
The results of BTS EDGE dimensioning and Abis dimensioning are used as the key input for BSC EDGE dimensioning. In addition, you need to check some information of the existing BSC configuration before starting the dimensioning. Table Input parameters for BSC EDGE dimensioning shows the required input information.
Table 1. Input
BSC variant
Input parameters for BSC EDGE dimensioning Status/value

BSCx PCUx Number Number Number Number Number (size) Number Number (size)
Activity
Verify (or upgrade) Verify (or upgrade) Verify Verify Verify Verify Abis dimensioning Abis dimensioning Abis dimensioning
Packet control unit (PCU) variant BTS object (cell) Segment Transceiver (TRX) Base control function (BCF) EGPRS dynamic Abis pool (EDAP) Associated BTSs per EDAP Radio timeslots (RTLSs) in the BTSs
Output summary
The BSC EDGE dimensioning output is described in table Output of BSC EDGE dimensioning. An important part of the dimensioning process is the evaluation of results and iteration, if required. The output is used as the input for Gb dimensioning.
# Nokia Corporation
13 (57)
Table 2. Output
BSC PCU Gb interface
Output of BSC EDGE dimensioning Value

Type Number Number/size
14 (57)
# Nokia Corporation
BSC capacity
BSC capacity
The BSC needs enough capacity for the Abis and A interfaces and for the internal processing of CS and PS traffic because all CS (erlang) and PS (Mbit/s) traffic from the radio network goes through the BSC to the core network. The capacity of different BSC hardware/software releases is usually compared by using the maximum values of TRXs or the number of Abis channels for GPRS/ EDGE use to be connected or delivered through the BSC. The capacity of BSCi, BSC2i, and BSC3i is presented in Table BSC comparison.
Table 3.
BSC comparison BSC3i 2000 BSC3i 1000

1000
BSC3i 660
660
BSC2i
512
BSCi
512
Max. number of TRXs
2000
2000 Max. number of base control functions (BCFs) Max. 2000 number of BTS objects Max. number of traffic channels (TCHs) Max. number of PCUs (logical) 16000
1000
504*
248
248
1000
660
512
512
8000
5280
4096
2048
100+10**
50+10**
24+4
16+2
8+1
# Nokia Corporation
15 (57)
Table 3.
BSC comparison (cont.) BSC3i 2000 BSC3i 1000

5+1
BSC3i 660
6+1
BSC2i
8+1
BSCi
8+1
Max. number of BSC signalling units (BCSUs) Max. number of E1(T1)s Traffic (Erl)
10+1
800
384
256
144
88
11880
5940
3920
3040
3040
* The maximum number of 504 BCF objects is supported in BSC3i 660 with AS7-C and GSW1KB hardware. ** Only applies to PCU2. For more information on the BSC, see the BSS Description document. Also see Product Description of Nokia BSC2i and BSCi High Capacity Base Station Controller and Product Description of Nokia BSC3i High Capacity Base Station Controller in BSC/TCSM documentation.
5.1
EGPRS-related BSC elements

To set up the dimensioning, a BSC audit needs to take place. The aim of the audit is to verify the existing configuration, that is, the BSC variant and the number of BCSUs and PCUs. The BSC variant and different elements define the connectivity to BTS which, at the end, may affect the BTS configuration and the Gb configuration. From this point of view, the EDGE network dimensioning is an iterative process. The following are the main EGPRS traffic related functional units of a BSC:
16 (57)
# Nokia Corporation
BSC capacity
Bit group switch (GSWB)
For information on the GSWB, see chapter Base Station Controller in the BSS Description document and chapter Bit Group Switch in Product Description of Nokia BSC3i High Capacity Base Station Controller in BSC/TCSM documentation.
BSC signalling unit (BCSU)
In the maximum configuration, BSCi and BSC2i contain eight active BCSUs and one redundant BCSU. In the maximum configuration, BSC3i 660 contains six active BCSUs and one redundant BCSU, whereas BSC3i 2000 contains 10 active BCSUs and one redundant BCSU. Each BCSU in BSCi can be equipped with zero or one PCU. Each BCSU in BSC2i or BSC3i 660 can be equipped with zero, one, or two PCU(s). Each BCSU in BSC3i 1000/2000 can be equipped with up to five PCU2s. For high EDGE traffic, two PCUs are required for each BCSU. Figure PCUs and BCSUs in the BSC2i shows an example layout of BCSU cartridges and PCU cards in BSC2i, where two PCU cards are implemented in one BCSU.
# Nokia Corporation
17 (57)
PSA20 PSFP
SW1C SW1C CLOC CLAC
PSA20 PSFP
ET5C BCSU BCSU BCSU
ET5C ET5C
MCMU
MCMU
WDDC
WDDC
BCSU
BCSU
ET5C
ET5C
BCSU
O MU
BCSU
Two PCU HW in every BCSU for high EDGE traffic
BCSU
BCSU
ET5C
Figure 3.
PCUs and BCSUs in the BSC2i
Possible BSC configurations:

.
One or two PCU1 units in every BCSU in BSC2i or BSC3i 660. One PCU1 and one PCU2 unit in every BCSU in BSC2i or BSC3i 660. One or two PCU2 units in every BCSU in BSC2i or BSC3i 660. In BSCi, one PCU1 or PCU2 unit can be configured in every BCSU.
One to five PCU2 units in every BCSU in BSC3i 1000/2000.
Packet control unit (PCU)
The PCU card limits the maximum number of radio timeslots that can be connected to a PCU card simultaneously.
18 (57)
# Nokia Corporation
ET5C
BSC capacity
Table 4. PCU type

PCU PCU-S PCU-T PCU-B PCU2-U PCU2-D
BTS and TRX capability of different PCU types BSC type BTSs TRXs
128 128 128 2 x 128 256 2 x 256
RTSLs
128 ch 128 ch 256 ch 2 x 256 ch 256 ch 2 x 256 ch
Abis channels
256 256 256 2 x 256 256 2 x 256
BSCi, BSC2i 64 BSCi, BSC2i 64 BSCi, BSC2i 64 BSC3i 2 x 64
BSCi, BSC2i 128 BSC3i 2 x 128
The PCU card also limits the maximum number of Abis channels. Table Abis configuration examples (PCU, PCU-S) gives examples of GPRS/EGPRS radio timeslot (RTSL) configurations when EDAP channels are also used.
Table 5. GPRS (16 kbit/s) channels

128 64 -
Abis configuration examples (PCU, PCU-S) EGPRS (16 EDAP (16 kbit/s) master kbit/s) slave channels channels
128 64 64 51 128 192 128 204
Total number of channels

128 256 256 256 255
Coding
CS1&2 MCS-5 MCS-7 MCS-6 MCS-9
The PCU variant depends on your needs and the PCU usage percentage has to be decided. The percentage is usually 75-80%. Table The capability of the Gb interface for different PCU types shows the PCU limitations for the Gb interface towards the SGSN with Gb over frame relay and Gb over IP.
Table 6. PCU type

PCU PCU-S
The capability of the Gb interface for different PCU types BSC type
BSCi, BSC2i BSCi, BSC2i
Gb over frame relay Gb over IP

32 x 64 kbit/s 32 x 64 kbit/s 2 Mbit/s 2 Mbit/s
# Nokia Corporation
19 (57)
Table 6. PCU type

PCU-T PCU-B PCU2-U PCU2-D
The capability of the Gb interface for different PCU types (cont.) BSC type
BSCi, BSC2i BSC3i BSCi, BSC2i BSC3i
Gb over frame relay Gb over IP

32 x 64 kbit/s 2 x 32 x 64 kbit/s 32 x 64 kbit/s 2 x 32 x 64 kbit/s 2 Mbit/s 2 Mbit/s 2 + 2 Mbit/s 2 + 2 Mbit/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.
Each logical PCU can be connected to the SGSN to provide EGPRS services in the cells controlled by the PCU. The Gb interface can be one of the following types:
.
Gb over IP: One PCU can be connected to one SGSN. The IP interface for a PCU can be either IPv4 or IPv6 but not both. Gb over frame relay: The PCM interfaces for the frame relay are routed by the GSWB in the BSC to the PCU.
A PCU can be connected to the SGSN either via Gb over frame relay or Gb over IP interface but not simultaneously via both interfaces. Gb over IP can be used with PCU1 and PCU2 units.
EDAPs in the PCU

The optimal size of the EDAP is planned in the Abis EDGE Dimensioning document. The following PCU boundary conditions are taken into account:
.
A maximum of 256 channels (16 kbit/s) in the PCU. The maximum EDAP size is 12 TSLs (64 kbit/s).
20 (57)
# Nokia Corporation
BSC capacity
It is recommended to use 1, 2, 4, or 8 EDAPs per PCU. This rule guarantees the same amount of resources for each equally weighted EDAP within the PCU. Other configurations may be used to increase PCU connectivity. However, the PCU resources might be distributed unevenly between the EDAPs and, therefore, some of the cells might have slightly different performance compared to the others. To ensure that the most important cells get more resources than the less important ones, the weight of the EDAP can be tuned. The weight is the number of 16 kbit/s EDAP channels plus the total number of RTSLs on default territories associated to the EDAP. One way to increase/decrease the relative weight of an EDAP is to increase/decrease the default territory by one in the most/least important cell which is associated to the EDAP.
The sum of EDAP sizes in the PCU is no more than 51 TSLs. However, if for some reason all 16 EDAPs are in use, the sum of the EDAP sizes is 48 TSLs at maximum.
For more information on the PCU, see Packet Control Unit (PCU) in BSC in (E) GPRS System Feature Description.
Exchange Terminal
All 2.048 Mbit/s (in the ETSI environment) or 1.544 Mbit/s (in the ANSI environment) interfaces for the MSC, SGSN, and BTSs are connected to the Exchange Terminals (ET). The ETs adapt the external PCM circuits to the GSWB. In BSC2i, a second PCU can be added to all configured BCSUs as a GPRS/ EGPRS extension. The addition of a second PCU board implies the extension of the GSWB from 192 to 256 PCMs and an optional E1/T1 extension from 112 to 144 (72 ET2E/A units). In the maximum configuration of BSC3i 660, one ET4C-B cartridge can contain up to 32 ET4 plug-in units. The total number of ET4 plug-in units in BSC3i 660 with GSW1KB is 64, and the total number of PCMs is 256. The ETs of the BSC3i 1000/2000 are housed in GT6C-A and/or GT4C-A cartridges. One GT4C-B cartridge can contain up to eight ET plug-in units and one GT6C-A cartridge can contain up to four ET plug-in units.
# Nokia Corporation
21 (57)
22 (57)
# Nokia Corporation
Dimensioning process
6
6.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 2 TSL TRX 3 4 5 6
Cell
PCU
Basic unit
BTS
Abis
BSC
Gb
2G SGSN
Figure 4.
Available data capacity process
# Nokia Corporation
23 (57)
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)). BTS dimensioning . Estimate throughput/timeslot (TSL). . Calculate the available capacity/number of TSLs based on the circuit-switched (CS) traffic needs. . Verify the dimensioning outcome. The dimensioning process results in throughput/TSL, territory size/BTS, guaranteed/not guaranteed throughput, TSL configuration of TRXs, amount of TRXs per cell, and the simulation results. 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. 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. 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.
2.
3.
4.
5.
24 (57)
# Nokia Corporation
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 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 2 TSL TRX 3 4 5 6
Cell
PCU
Basic unit
BTS
Abis
BSC
Gb
2G SGSN
Figure 5.
Required data capacity process
# Nokia Corporation
25 (57)
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). BTS dimensioning . Calculate the required throughput. . Estimate throughput/TSL. . Calculate the required number of TSLs. . Verify the dimensioning outcome. The dimensioning process results in throughput/TSL, territory size/BTS, guaranteed/not guaranteed throughput, TSL configuration of TRXs, amount of TRX/cell, and the simulation results. Abis dimensioning . Use the output of BTS dimensioning as the input. . Define the EDAP size. The dimensioning process results in the size each EDAP. 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. 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. 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.
2.
3.
4.
5.
26 (57)
# Nokia Corporation
6.
SGSN dimensioning . Use the output of BTS and Gb dimensioning as the input. . Define the required number of 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.
6.2
BSC EDGE dimensioning process

BSC dimensioning for EGPRS traffic is a straightforward process that starts from EDGE BTS and transmission dimensioning inputs, continues to the dimensioning of the PCU card, and then to the dimensioning of the Gb interface towards the SGSN (see figure BSC dimensioning flow). The number of required Abis and dynamic Abis channels (EGPRS dynamic Abis pool, EDAP), Exchange Terminal (ET) cards, packet control unit (PCU) cards, and Gb interface licences can be calculated from the voice, GPRS, and EGPRS traffic.
# Nokia Corporation
27 (57)
EDGE BSC dimensioning

Step 1: Inputs from BTS EDGE dimensioning
Traffic mix Total number of TCHs Total number of TRXs Total number of BTSs/BCFs
Step 2: PCU
Step 3: BSC
BSC type and BSS SW release BSC usage percentage Total number of BSCUs Total number of ETs
Step 4: Gb interface
Step 5: Outputs
Check PCU type and limitations PCU usage percentage Total number of EDAPs * BH Gb throughput to be handled PCU-EDAP association* Calculate the needed amount of PCUs
Gb interface FR or IP Gb capacity ETSI or ANSI Gb usage percentage User data * Overhead(%) Inputs from Gb planning
Total number of PCUs Type of PCUs Total number of BCSUs Total number of Gb interfaces Triggers for redimensioning
(*) EDGE transmission network planning: the calculation of the EDAP size
Figure 6.
BSC dimensioning flow
Before BSC dimensioning work can be started, some decisions related to system, radio network, and BSC configurations have to be made. It is important to know whether the system is European (ETSI) or American (ANSI). In the ANSI standard, for example, transmission is slightly different from the ETSI specifications. Next, the exact BSS software release (the assumption in these guidelines is BSS12) and BSC product version (the assumption in these guidelines is BSCi, BSC2i, or BSC3i) have to be known to identify the maximum Abis, PCU, and Gb capacities for the dimensioning work. When the BSS software release and the BSC product types are known, also the ET, PCU, and Gb interfaces can be selected. The BSC dimensioning work can be divided into the following steps: 1. Defining the BSC type, software, number of BSC signalling units (BCSUs) and ETs, and limitations. For more information, see Network capability in chapter Inputs for BSC EDGE dimensioning. 2. Collecting inputs from EDGE BTS and transmission dimensioning.
28 (57)
# Nokia Corporation
For more information, see Input from Abis and BTS dimensioning in chapter Inputs for BSC EDGE dimensioning. 3. Calculating the required number of PCUs. For more information, see chapter PCU calculations for BSC EDGE dimensioning. 4. Calculating the required number of Gb links for SGSN traffic. Gb traffic now also includes Gb overhead. Gb interface dimensioning is described in the Gb EDGE Dimensioning document. In these guidelines, the assumption is to use Gb over FR. The number of the Gb interface can be calculated, as can the number of required ET cards, depending on the standard (ETSI/ANSI). Always use the same usage criteria for the Gb interface and ET card as for the other BSC elements. The Gb interface capacity should be in line with the EDAP size. 5. Defining the BSC configuration and evaluating the results (redimensioning).
6.3
Inputs for BSC EDGE dimensioning

The basic voice dimensioning of the BSC depends mainly on the number of base stations (BTSs) and transceivers (TRXs) connected to the BSC. For information on constraints related to the BSC signalling unit (BCSU), see BSC signalling unit (BCSU) in chapter BSC capacity. EGPRS traffic (kbit/s) is a key element in Abis, packet control unit (PCU), and Gb dimensioning. Because of very different coding schemes and throughput rates, it is extremely relevant to know whether the traffic is GPRS or EDGE. Therefore, the main decision needed for BSC dimensioning is the number of timeslots used, on average, for EGPRS traffic during a busy hour and the deviation of traffic between the peak and minimum values (this also provides the difference between the peak and average values). In these guidelines, it is assumed that the TRX and BTS limitations per PCU card are based on the 75% rule, where 25% of the capacity is reserved for future extensions. The same 75/25% rule is also used for the calculations of the maximum throughputs of the PCU cards and Abis and Gb/IP interfaces.
# Nokia Corporation
29 (57)
6.3.1
Network capability
BSC configuration
.
BSC variant (BSCi, BSC2i, BSC3i) PCU variant (PCU, PCU-B, PCU-S, PCU-T, PCU2-D, PCU2-U) installed software (BSS11, BSS11.5, BSS12) Abis channels . size and count of the EGPRS dynamic Abis pools (EDAPs) . total number of the radio timeslots (TSLs) in EGPRS territories in all TRXs under the PCUs . total of the packet common control channels (PCCCHs) / packet broadcast control channels (PBCCHs) in all TRXs under the PCU1s total number of the BTS objects (sectors) with GENA = Y under the PCUs total number of the SEGMENTs configured under the PCUs total number of the TRXs with GTRX = T under the PCUs
PCU connectivity
In PCU1 dimensioning, the following restrictions need to be taken into account:

.
The maximum amount of EDAPs connected to a PCU is 16. The recommendation is one, two, four, or eight EDAPs under one PCU. The maximum theoretical number of dynamic Abis pools in the BSC is 256 in BSC2i (16 EDAPs in each PCU and 16 PCUs in each BSC2i), and 384 in BSC3i (16 EDAPs in each PCU and 24 logical PCUs in each BSC3i). From BSS12 onwards there can be 1600 dynamic Abis pools in BSC3i (16 EDAPs in 100 logical PCUs).
30 (57)
# Nokia Corporation
Table 7. PCU variant

PCU
Connectivity of the first generation PCU (PCU1) Logical PCUs/ board

1
BSC type Capability
BSS10.5E D and BSS11

64 128 64 256 256
BSS11.5 and BSS12

64 128 64 128 256
BSCi, BSC2i
Max. BTSs Max. TRXs Max. SEGs Max. radio TSLs Max. Abis channels at 16 kbps Max. Gb channels at 64 kbps
32
32
PCU-S
BSCi, BSC2i
64 128 64 256 256
64 128 64 128 256
32
32
PCU-T
BSCi, BSC2i
64 128 64 256 256
64 128 64 256 256
32
32
# Nokia Corporation
31 (57)

PCU-B
Connectivity of the first generation PCU (PCU1) (cont.) Logical PCUs/ board
2
BSC type Capability

2 x 64 2 x 128 2 x 64 2 x 256 2 x 256
BSS11.5 and BSS12

2 x 64 2 x 128 2 x 64 2 x 256 2 x 256
BSC3i
2 x 32
2 x 32

PCU2-U
Connectivity of the second generation PCU (PCU2) Logical PCUs/ board

1
BSC type
BSCi, BSC2i
Capability

n/a n/a n/a n/a n/a
BSS11.5 and BSS12

128 256 64 256 256
n/a
32
32 (57)
# Nokia Corporation

PCU2-D
Connectivity of the second generation PCU (PCU2) (cont.) Logical PCUs/ board
2
BSC type
BSC3i
Capability

n/a n/a n/a n/a n/a
BSS11.5 and BSS12

2 x 128 2 x 256 2 x 64 2 x 256 2 x 256
n/a
2 x 32
6.3.2
Input from Abis and BTS dimensioning

The total number of required Exchange Terminal (ET) plug-in units per BSC is not taken into account in this BSC dimensioning because there is no Abis dimensioning. The total number of Abis and Gb (FR) links may not break the E1 (T1) connectivity limit of the BSC. Abis and dynamic Abis planning are described in the Abis EDGE Dimensioning document. Inputs from Abis and BTS planning:
.
number of BTS objects number of segments number of TRXs number of EDAPs number of associated EDAPs per BTS size of the radio timeslots in the BTSs
# Nokia Corporation
33 (57)
6.4
PCU calculations for BSC EDGE dimensioning

In the packet control unit (PCU) dimensioning phase, dimensioning inputs (or guidelines) have to be given to meet the network evolution and quality targets. First, only a certain maximum number of base stations (BTSs) and transceivers (TRXs) is connected to the PCU cards, and the minimum amount of PCU cards can be calculated. Next, the capacity extension criteria of different EGPRS traffic related elements have to be defined for the future capacity increase resulting from network evolution. In the EDGE dimensioning guidelines, the dimensioning criterion is that a maximum 75% of the total capacity of each configuration can be used and 25% is reserved for future extensions. This usage has to be used for the Exchange Terminal (ET) and PCU cards and for Gb interface licences. Therefore, similar calculations have to be made for the ET cards and Gb interfaces. It is recommended to leave some of the installed PCUs for future configuration upgrades and use the rest as efficiently as possible. This is achieved by dimensioning the PCUs using the formula in figure Needed PCU cards and the given design rules.
TSLs max. radio TLSs x U Abischs max.Abischs x U EDAPs , max. EDAPs BTSobjs L = roundup max max. BTSobjs SEGs max. SEGs TRXs max. TRXs , , , ,
BHGbThroughput max. BHGbThroughput x U
Figure 7.
Needed PCU cards
34 (57)
# Nokia Corporation
The equation is used to check that the PCU capabilities are not exceeded. In the equation:
.
RTSLs is the total number of RTSL in the GPRS and EGPRS territories that are associated to a given logical PCU. Abischs is the total number of Abis channels associated both to the master channels and EDAP channels of a given logical PCU. RTSLs + 4 x sum size of all EDAPs in a 64k TSL. EDAPs is the total number of EDAPs associated to a given logical PCU. BTSobjs is the total number of BTSobjects under SEGments with GENA = Y + other BTSobjects with GENA = Y associated to a given logical PCU. SEGs is the total number of SEGments with GENA = Y associated to a given logical PCU. TRXs is the total number of TRXs with GTRX = Y associated to a given logical PCU. BHGbThroughput is the total BHGb capacity required for the PS traffic for a given logical PCU as a number of 64k TSLs. U is the capacity reservation for territory upgrades. It is typically 75%. L is the number of needed logical PCUs. The maximum object counts are shown in tables BTS and TRX capability of different PCU types and Abis configuration examples (PCU, PCU-S).
The different maximum values in the equation depend on the selected PCU variant. If the PCU variant is PCU-B or PCU2-D (includes two logical PCUs), the number of needed physical cards (N) is (regardless of the installed software version): N = L/2 For all other PCU variants the number of needed physical cards (N) is: N=L
6.5
Outputs of BSC EDGE dimensioning

BSC dimensioning results in specific outputs. These outputs are used as input in the next dimensioning phase, Gb EDGE dimensioning.
# Nokia Corporation
35 (57)
Available capacity strategy
BSC dimensioning outputs:

.
number and type of BSCs Note that if EDGE is deployed into an existing network, the number and type of BSCs is an input.
number of BSC signalling units (BCSUs) number and type of packet control units (PCUs) number of Gb interfaces
Required capacity strategy
BSC dimensioning outputs:

.
total number and type of BSCs total number and type of PCUs total number of BCSUs total number of Gb interfaces
Triggers for redimensioning:

.
too many BTSs per BSC too many PCUs per BSC too many radio timeslots/Abis channel per PCU too many EGPRS dynamic Abis pools (EDAPs) per PCU too much Gb traffic per PCU
To do in redimensioning:
.
Optimise the number of BTSs for each BSC. Re-estimate traffic to avoid over dimensioning. Optimise the EDAP size. Optimise the size of the radio timeslots.
36 (57)
# Nokia Corporation
6.6
Evaluation of the BSC dimensioning results

The dimensioning process is often very iterative. If the number of required BSCs is too high, for example, new BTS dimensioning is required: coverage and traffic estimations need to be re-evaluated. A higher BSC usage level may help. Also a new transmission plan, including the optimisation of the number and size of the EGPRS dynamic Abis pools (EDAPs), has an impact on the number of packet control units (PCUs) and digital signal processor (DSP) capacity. First, only a certain maximum number of base stations and transceivers (TRXs) is connected to the PCU cards, and the minimum amount of PCU cards can be calculated. Next, based on the traffic demand coming from the radio network, the final number of required PCU cards is calculated. The average traffic demand is used because we need to take into account the maximum use of the PCU card that future extension needs and peak traffic cause. The BSC and PCU can be selected according to the dimensioning results, keeping in mind the different possible configurations. For example, because of N+1 redundancy principles one PCU1 or PCU2 plug-in unit is required for each BSC signalling unit (BCSU), the number of activated PCUs is selected according to the dimensioning results. It is important to apply the 75% usage criterion to a fully equipped BSC, for example, BSC2i with 8+1 BCSU and 16+2 PCU units. If, according to the calculations, a full BSC configuration is not needed, a higher usage level can be used. Network growth can be achieved by adding extra hardware when needed. Figure BSC redimensioning process illustrates what triggers redimensioning and what needs to be done during redimensioning.
# Nokia Corporation
37 (57)
BSC dimensioning
BSC configurations: -Total number and type of BSCs -Total number and type of PCUs -Total number of BCSUs -Total number of Gb interfaces
To do in redimensioning: -Optimise the number of BTSs under BSC -Re-estimate traffic to avoid over dimensioning -Optimise the EDAP size -Optimise the size of the radio timeslots
Triggers for redimensioning: -Too many BTSs per BSC -Too many PCUs per BSC -Too much Gb traffic per PCU -New BTS/TRX
Figure 8.
BSC redimensioning process
38 (57)
# Nokia Corporation
Example of BSS connectivity dimensioning
7
7.1

BSS connectivity dimensioning
The EDGE dimensioning guidelines include an example of BSS connectivity dimensioning. The example shows one calculation method for dimensioning the following:
.
default GPRS capacity (CDEF) The value of the default GPRS capacity parameter is calculated in chapter Radio interface capacity.
dynamic Abis pool (DAP) size The size of the EGPRS dynamic Abis pool (EDAP) is calculated in chapter Connectivity capacity.
number of packet control units (PCUs) The number of PCUs is calculated in chapter Connectivity capacity.
Gb link size The size of the Gb link is calculated in chapter Connectivity capacity.
The dimensioning is not based on a detailed network audit with all the configuration, parameter, and software information (such as the BSC types, number of available PCUs, and location area (LA) / routing area (RA) borders). Instead, the dimensioning is based on data about the number of base control functions (BCFs), BTSs, and transceivers (TRXs) with traffic volume assumption of existing circuit-switched (CS) traffic and requirements on packet-switched (PS) data rate (if there is any). The BSS connectivity dimensioning example uses all PCU1 variants. PCU2 is not taken into account in the calculations.
# Nokia Corporation
39 (57)
7.2
Dimensioning inputs
The aim of the dimensioning is to calculate the default GPRS capacity (CDEF), EGPRS dynamic Abis pool (EDAP) size, number of packet control units (PCUs), and the size of the Gb link because EDGE/GPRS is implemented on top of existing CS voice. The following inputs are used in the calculation example:
.
one BSC with 40 base control functions (BCFs) three BTSs per BCF site configurations . 2+2+2, 25 BCFs: "surrounding area" (light blue in figure Site configurations) Configuration 1 . 4+4+4, 15 BCFs: "central area" (deep blue in figure Site configurations) Configuration 2
Figure 9.
.
Site configurations
BCF voice traffic
40 (57)
# Nokia Corporation
. . .
2+2+2 site has traffic of 8 Erl per BTS on average 4+4+4 site has traffic of 18 Erl per BTS on average blocking criteria is 2%
data traffic . streaming user support requirement per BTS ~ 50 kbit/s . average data throughput per BTS (by operator): "central area": 200 kbit/s "surrounding area": 100 kbit/s other considerations . average mobile station (MS) multislot support in the network: 4 timeslots (TSLs) . all BTSs and TRXs are EDGE capable . frame relay planned as the Gb implementation
To simplify the BSS connectivity dimensioning example, it is assumed that all BTSs within the site/BCF have a similar traffic profile. In addition, it is assumed that the data traffic need for the 4+4+4 configuration is higher than for the 2+2+2 configuration. In reality this might not be the case, and some 2+2+2 configurations could have higher data traffic and need for higher data capacity than 4+4+4 configurations. Note that it is assumed that the given data amount per BTS does not need to be supported simultaneously in all BTSs. This information is used for EDAP and Gb link dimensioning.
7.3
7.3.1
Radio interface capacity

Configuration before (E)GPRS
Figures 2+2+2 configuration and 4+4+4 configuration show the TRX configurations used in the BSS connectivity dimensioning example.
BCCH TCH
TSL0 MBCCH TCH/F
TSL1 SDCCH TCH/F
TSL2 TCH/F TCH/F
TSL3 TCH/F TCH/F
TSL4 TCH/F TCH/F
TSL5 TCH/F TCH/F
TSL6 TCH/F TCH/F
TSL7 TCH/F TCH/F
Figure 10.
2+2+2 configuration
# Nokia Corporation
41 (57)
BCCH TCH TCH TCH
TSL0 MBCCH TCH/F SDCCH TCH/F
TSL1 SDCCH TCH/F TCH/F TCH/F
TSL2 TCH/F TCH/F TCH/F TCH/F
Figure 11.
4+4+4 configuration
In the 2+2+2 configuration, two radio timeslots (RTSLs) are reserved for uncombined signalling (broadcast control channel (BCCH) and stand-alone dedicated control channel (SDCCH)), while the rest of the RTSLs are full rate RTSLs (no dual rate (DR) / half rate (HR) implemented). In the 4+4+4 configuration, there are three RTSLs that are used for signalling (one BCCH and two SDCCHs), while the rest of the RTSLs are full rate RTSLs (no DR/HR implemented). Regardless of the configuration, each base control function (BCF) has its own E1 for transmission.
42 (57)
# Nokia Corporation
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TRXSIG1 TRXSIG3 TRXSIG5 BCFSI G
TCH 1 TCH 5 TCH 1 TCH 5 TCH 1 TCH 5 TCH 1 TCH 5 TCH 1 TCH 5 TCH 1 TCH 5
TCH 2 TCH 6 TCH 2 TCH 6 TCH 2 TCH 6 TCH 2 TCH 6 TCH 2 TCH 6 TCH 2 TCH 6 TRXSIG2 TRXSIG4 TRXSIG6
TCH 3 TCH 7 TCH 3 TCH 7 TCH 3 TCH 7 TCH 3 TCH 7 TCH 3 TCH 7 TCH 3 TCH 7
Q1 m anagement
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4 TCH 0 TCH 4
TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5 TCH1 TCH5
TRXSIG1 TRXSIG2 TRXSIG3 TRXSIG4 TRXSIG5 TRXSIG6 TRXSIG7 TRXSIG8 TRXSIG9 TRXSIG1 0 TRXSIG1 1 TRXSIG1 2 BCFSIG Q1 m anagemen t
Figure 12.
E1 setup for 2+2+2 and 4+4+4 configurations
7.3.2
(E)GPRS deployment scenarios

All the TRXs are GPRS and EGPRS capable, so the following parameter setup is used:
.
TRX: GTRX = Y BTS: GENA = Y, EGENA = Y, CMAX = 100%
The TSL data rate depends on the signal level and interference. The capacity limitations are not taken into account in this example. Figure RLC/MAC data rate dependency on signal level and C/I shows the dependency for two timeslots.
# Nokia Corporation
43 (57)
RL C/MAC d ata rate (FTP d o w n l o ad on 2 TSL s )

120 100 80
kbp s
No Interference C/I 25 dB C/I 20 dB C/I 15 dB
60 40 20 0 -65 -70 -75 -80 -85 -90 -95 -100 -105 Si gn al l eve l (d B m)
Figure 13.
RLC/MAC data rate dependency on signal level and C/I
In the BSS connectivity dimensioning example, the following average EGPRS radio link control (RLC) / medium access control (MAC) TSL data rate is used: 35 kbit/s (BCCH layer). Typically the best carrier-to-interference ratio (C/I) TRX is preferred for maximum throughput. Depending on the frequency plan, this can be either a BCCH or TCH TRX. In the BSS connectivity dimensioning example, the BCCH TRX is preferred.
7.3.3
Available capacity
Before the calculations, the size of the free RTSL must be defined. Figure Territories shows how two TRXs are divided into territories.
44 (57)
# Nokia Corporation
TRX 1
BCCH SDCCH
TS
TS
TS
TS
TS
TS
GTRX GENA
Territory border
TRX 1
EGENA CMAX TS TS TS GTRX
TRX 2
TS
TS
TS
TS
TS
BCCH TS TS TS TS
= Signalling = Free TSL for CS = Default GPRS capacity
TS TS TS TS TS TS
= CS territory = (E)GPRS territory/additional capacity = Dedicated GPRS capacity
Figure 14.
Territories
Free RTSLs between the circuit-switched (CS) and packet-switched (PS) territory are required to serve the immediate incoming CS calls without blocking.
.
CS downgrade: If there are less RTSLs free in the CS territory than required, a PS territory downgrade is triggered. CS upgrade: A PS territory upgrade can be triggered if at least the required amount of RTSLs are free.
Free TSLs for upgrade and downgrade can be controlled with BSC parameters (see table CSD and CSU parameter setup).
Table 9.
CSD and CSU parameter setup
TSL number after CS downgrade

TRX number Free TSLs for CS downgrade (%) (CSD) 70 95 99 1 0 1 1 2 0 1 1 3 0 1 2 4 1 2 2 5 1 2 2
TSL number after CS upgrade
# Nokia Corporation
45 (57)
Table 9.
TRX number
CSD and CSU parameter setup (cont.)

1 1 4 7 10 0 1 1 2 2 1 2 2 3 3 1 2 3 4 4 1 3 4 5 5 2 4 5 6
Free TSLs for CS upgrade (sec.) (CSD)
The default value for parameter free TSL for CS downgrade (CSD) is 95%. The default value for parameter free TSL for CS upgrade (CSU) is 4. In the calculations for 2+2+2 and 4+4+4 configurations, the following free TSL values are used:
.
mean free RTSLs for two TRXs: (1+2)/2 1.5 mean free RTSLs for four TRXs: (3+2)/2 2.5
Calculations for the 2+2+2 configuration
BTS capacity calculations

.
2 TRXs, 16 RTSLs . 2 RTSLs for signalling . 14 RTSLs for CS traffic CS busy hour (BH) traffic: 8 Erl per BTS (all BTSs have the same amount of BH traffic) erlang B table: 1.7% CS blocking during BH mean free RTSLs = 1.5 average RTLSs available for PS traffic during CS BH: amount_of_TRXs x 8 - signalling_RTSLs - CS_BH_traffic-free_RTSLs = 2 x 8 - 2 - 8 - 1.5 = 4.5 RTSLs
average PS traffic during CS BH: 4.5 x 35 kbit/s = 157.5 kbit/s (> 100 kbit/s)
This means that we are well above the average data throughput per BTS (required by the operator), which is 100 kbps for the "surrounding area."
Default territory calculations
46 (57)
# Nokia Corporation
mobile station (MS) multislot capability (4 RTSLs) data throughput: 100 kbit/s radio interface: 35 kbit/RTSL RTSLs to support 100 kbit/s 100/35 = 2.9 TSLs ~ 3 RTSLs
Default territory size: max(MS_multislot, traffic) = max(4, 3) = 4 RTSLs

BTS capacity calculations

.
4 TRXs, 32 RTSLs . 3 RTSLs for signalling . 29 RTSLs for CS traffic CS BH traffic: 18 Erl per BTS (all BTSs have the same amount of BH traffic) erlang B table: 0.4% CS blocking during BH mean free RTSLs = 2.5 average RTLSs available for PS traffic during CS BH: amount_of_TRXs x 8 - signalling_RTSLs - CS_BH_traffic-free_RTSLs = 4 x 8 - 3 - 18 - 2.5 = 8.5 RTSLs
average PS traffic during CS BH: 8.5 x 35 kbit/s = 297.5 kbit/s (> 200 kbit/s)
This means that we are well above the average data throughput per BTS (required by the operator), which is 200 kbps for the "central area."
Default territory calculations

.
MS multislot capability (4 RTSLs) data throughput: 200 kbit/s radio interface: 35 kbit/RTSL RTSLs to support 200 kbit/s 200/35 = 5.7 TSLs ~ 6 RTSLs
Default territory size:
# Nokia Corporation
47 (57)
max(MS_multislot, traffic) = max(4, 6) = 6 RTSLs
7.3.4
Required capacity
The required capacity is the required streaming user support per BTS (one streaming user). Streaming requires 50 kbit/s (required by the customer). (50kbit/s) / (35 kbit/s / RTSL) = 2 RTSLs need to be dedicated (CDED) per BTS to support streaming
.
available RTSLs for CS traffic per BTS . 14 - 2 (CDED) = 12 RTSLs traffic per BTS = 8 Erl . erlang B (8 Erl, 12 TSLs) = 5.1% CS blocking . 5.1% > 2% - NOK needed channels for 2% CS blocking . erlang B (8 Erl, 2%) = 14 channels . either two more RTSLs (dual rate / half rate) are needed or a new TRX In this case, the capacity increase is achieved with dual rate RTSLs.

.
available RTSLs for CS traffic per BTS . 29 - 2 (CDED) = 27 RTSLs traffic per BTS = 18 Erl . erlang B (18 Erl, 27 TSLs) = 1.1% CS blocking . 1,1% > 2% - OK
7.4
7.4.1
Connectivity capacity
Default GPRS capacity (CDEF)
The results of default territory size calculations determine the value of the default GPRS capacity (CDEF) parameter.
48 (57)
# Nokia Corporation
CDEF is specified with the following formula: max(MS_multislot, traffic). max(4, 2.9) => 4 The value of the default GPRS capacity (CDEF) parameter is set to 4 radio timeslots (RTSLs).
CDEF is specified with the following formula: max(MS_multislot, traffic). max(4, 5.7) => 6 The value of the default GPRS capacity (CDEF) parameter is set to 6 RTSLs.
7.4.2
EDAP
General EDAP considerations
The following must be taken into consideration when considering the size of the EGPRS dynamic Abis pool (EDAP):
.
Whether support for MCS-9 at least with one mobile station (MS) in one BTS of the base control function (BCF) is required. (This is needed if the MS multislot capability is not taken into account in the default territory calculations.) min_EDAP_1 = MS_multislot_capability (= 4 TSLs)
Whether support for MCS-9 in all GPRS territory timeslots of the BTSs is required. min_EDAP_2 = max_default_territory_size_of_one_BTS
If the EDAP has more than one BTS attached to it, the BTS multiplexing factor can be taken into account if it is estimated that the EDAP peak load exceeds one BTSs territory size.
You can calculate the minimum EDAP size from the input with the following formula: min_EDAP_size = max(min_EDAP_1, min_EDAP_2) You can calculate the EDAP size with the following formula:
# Nokia Corporation
49 (57)
EDAP_size = k x min_EDAP_size Table BTS multiplexing factor shows the value for k for a different number of BTSs.
Table 10.
BTS multiplexing factor k

1.0 1.3 1.5
Number of BTSs
1 2 3
The EDAP size with different configurations can be calculated by using the information in table EDAP sizes with different configurations.
Table 11. Number of BTSs

1 2 3
EDAP sizes with different configurations k

1.0 1.3 1.5
Configuration 1 (2 +2+2)
4.0 5.3 6.0
Configuration 2 (4 +4+4)
6.0 8.0 9.0
The EDAP size for Configuration 1 (2+2+2) is min_EDAP_size = max(min_EDAP_1, min_EDAP_2) = max(4, 6) = 6 TSLs (64 kbps) The EDAP size for Configuration 2 (4+4+4) is min_EDAP_size = max(min_EDAP_1, min_EDAP_2) = max(4, 9) = 9 TSLs (64 kbps)
Abis timeslot allocation
There are two options for Abis TSL allocation:
50 (57)
# Nokia Corporation
TRXs are grouped by function so that all EDGE TRXs and EDAP are allocated to one E1. The non-EDGE resources are mapped to another E1 frame. One EDAP is enough to serve all cells (BTS objects). Figure TRXs grouped by function illustrates grouping based on the function. Cell A is shown in grey.
0 1 TCH 0 TCH1 TCH 2 TCH3 2 TCH 4 TCH5 TCH 6 TCH7 3 TCH 0 TCH1 TCH 2 TCH3 4 TCH 4 TCH5 TCH 6 TCH7 5 TCH 0 TCH1 TCH 2 TCH3 6 TCH 4 TCH5 TCH 6 TCH7 7 TCH 0 TCH1 TCH 2 TCH3 8 TCH 4 TCH5 TCH 6 TCH7 9 TCH 0 TCH1 TCH 2 TCH3 10 TCH 4 TCH5 TCH 6 TCH7 11 TCH 0 TCH1 TCH 2 TCH3 12 TCH 4 TCH5 TCH 6 TCH7 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 TRXSIG1 TRXSIG2 TRXSIG3 TRXSIG4 29 TRXSIG5 TRXSIG6 30 BCFSIG 31 Q1 m anagement
0 1 TCH 0 TCH1 TCH 2 TCH3 2 TCH 4 TCH5 TCH 6 TCH7 3 TCH 0 TCH1 TCH 2 TCH3 4 TCH 4 TCH5 TCH 6 TCH7 5 TCH 0 TCH1 TCH 2 TCH3 6 TCH 4 TCH5 TCH 6 TCH7 7 TCH 0 TCH1 TCH 2 TCH3 8 TCH 4 TCH5 TCH 6 TCH7 9 TCH 0 TCH1 TCH 2 TCH3 10 TCH 4 TCH5 TCH 6 TCH7 11 TCH 0 TCH1 TCH 2 TCH3 12 TCH 4 TCH5 TCH 6 TCH7 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 TRXSIG7 TRXSIG8 30 TRXSIG9 TRXSIG1 0 TRXSIG1 1 TRXSIG1 2 31 Q1 m anagement
Figure 15.
.
TRXs grouped by function
TRXs are grouped by cell so that two cells are allocated to one E1. The third cell is allocated to the second E1. In this case, and EDAP is created for both groups. Figure TRXs grouped by cells illustrates grouping based on the cells. Cell A is shown in grey.
# Nokia Corporation
51 (57)
0 1 TCH0 TCH1 TCH 2 TCH 3 2 TCH4 TCH5 TCH 6 TCH 7 3 TCH0 TCH1 TCH 2 TCH 3 4 TCH4 TCH5 TCH 6 TCH 7 5 TCH0 TCH1 TCH 2 TCH 3 6 TCH4 TCH5 TCH 6 TCH 7 TCH0 TCH1 TCH 2 TCH 3 7 8 TCH4 TCH5 TCH 6 TCH 7 9 TCH0 TCH1 TCH 2 TCH 3 10 TCH4 TCH5 TCH 6 TCH 7 11 TCH0 TCH1 TCH 2 TCH 3 12 TCH4 TCH5 TCH 6 TCH 7 13 TCH0 TCH1 TCH 2 TCH 3 14 TCH4 TCH5 TCH 6 TCH 7 15 TCH0 TCH1 TCH 2 TCH 3 16 TCH4 TCH5 TCH 6 TCH 7 17 18 19 20 21 22 23 24 25 26 27 28 TRXSIG1 TRXSIG2 TRXSIG3 TRXSIG4 29 TRXSIG5 TRXSIG6 TRXSIG7 TRXSIG8 30 BCFSI G 31 Q1 m anagement
0 1 TCH0 TCH1 TCH2 TCH3 2 TCH4 TCH5 TCH6 TCH7 3 TCH0 TCH1 TCH2 TCH3 4 TCH4 TCH5 TCH6 TCH7 5 TCH0 TCH1 TCH2 TCH3 6 TCH4 TCH5 TCH6 TCH7 7 TCH0 TCH1 TCH2 TCH3 8 TCH4 TCH5 TCH6 TCH7 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 TRXSIG 9 TRXSIG1 0 TRXSIG 1 1 TRXSIG1 2 31 Q1 m anag ement
Figure 16.
TRXs grouped by cells
Both options have their advantages and disadvantages. These are shown in tables TRXs grouped by function and TRXs grouped by cells.
Table 12.
TRXs grouped by function Disadvantages
Advantages
The maximum trunking gain of the EDAP Special care is needed to maintain and can be achieved because less of total upgrade the configuration to keep with the Abis capacity is required (number of TSLs original split. for EDAP = 9). A smaller number of EDAPs saves PCU resources and Abis capacity. The number of EDGE TRXs which can be connected to the EDAP is smaller. This leads to a smaller maximum theoretical territory size.
52 (57)
# Nokia Corporation
Table 13.
TRXs grouped by cells Disadvantages

The trunking gain of the EDAPs is smaller, and more total Abis capacity is required (number of TSLs for EDAP = 8 +6 = 14). A larger number of EDAPs consumes more PCU resources.
Advantages
Straightforward to maintain and upgrade.
All TRXs can be connected into the EDAP, and the maximum territory size does not depend on the Abis configuration.
In Configuration 1 (2+2+2), the EDAP fits in the existing E1. In Configuration 2 (4+4+4), additional transmission capacity is required.
7.4.3
PCU
The target is to calculate the optimal number of packet control units (PCUs) to serve the network. The calculation is based on table Connectivity of the first generation PCU (PCU1) in chapter Inputs for BSC EDGE dimensioning. The following are taken into account in this example:
.
PCU usage is recommended to be around 75% for Abis timeslots (TSLs). (25% connectivity is available for territory upgrades.) The number of BTSs and TRXs can reach the maximum value (as specified in table Connectivity of the first generation PCU (PCU1)). The recommended number of EGPRS dynamic Abis pools (EDAPs) per PCU1 is 1, 2, 4, or 8. With PCU2, the recommendation is a maximum of 8 EDAPs per PCU. However, this example uses only PCU1. The optimal number of EDAPs and associated default radio timeslots (RTSLs) is calculated for each PCU configuration. . For example, up to 5 EDAPs of size 6 TSLs, serving three cells each with a default territory size of 4 RTSLs, can be allocated to the PCU without exceeding 75% (see table Different configurations and their Abis and RTSL load). . To meet the 1, 2, 4, and 8 recommendation, the number of EDAPs would be 4.
# Nokia Corporation
53 (57)
Table 14. EDAP splitting strategy Configurations N/A Configuration 1

6
Different configurations and their Abis and RTSL load TRX grouped by cells Configuration 2 (cells A and B)
6 6 1
TRX grouped by function Configuration 2 (cells A, B, and C)

9 6 3
Configuration 2 (cell C)
8 6 2
EDAP size
Number of RTSLs 4 in the territory Number of BTSs (territories) per EDAP Number of EDAP subTSLs 3
24
24 6 30
32 12 44
36 18 54
Number of RTSLs 12 Number of Abis subTSLs 36
From table Different configurations and their Abis and RTSL load, Configuration 2 with TRXs grouped by function is used in this example. Table Possible PCU configurations lists the possible PCU combinations. Configuration 1 has 36 subTSLs and Configuration 2 has 54 subTSLs in the Abis interface.
PCU configuration
Number of BCFs with Configuration 1 Number of BCFs with Configuration 2
A
0 4
B
0 3 162 63
C
1 3 198 77
D
3 2 216 84
E
2 2 180 70
F
4 1 198 77
G
3 1 162 63
H
5 0 180 70
I
4 0 144 56
Total PCU Abis load 216 (TSLs) Total PCU load (%) 84
In PCU configurations A, B, G, and I, the PCU usage is too far from the 75% goal. In PCU configurations C, E, F, and H, the PCU usage is reasonably close to the target value. In this example, PCU configurations C and H are used. However, also other configurations could be used.
54 (57)
# Nokia Corporation
With the selected PCU configurations (C and H), we can calculate the needed number of PCUs:
.
5 PCUs with configuration C 4 PCUs with configuration H
(5 x (Configuration 1 + 3 x Configuration 2) + 4 x (5 x Configuration 1) = 15 x Configuration 2 + 25 x Configuration 1
7.4.4
Gb link dimensioning
TBD
7.5
Results of BSS connectivity dimensioning

Table Dimensioning results shows the results of the BSS connectivity dimensioning example.
Table 15.
Dimensioning results
150 9 15 3
Dual rate RTLSs PCUs E1s for Abis E1s for Gb
Table Radio interface setup shows the radio interface setup of the BSS connectivity dimensioning example.
Table 16.
Radio interface setup

CDED 2 2 CDEF 4 6 EDAP 6 9
Configuration Configuration 1 Configuration 2
Table PCU usage shows the Abis timeslot usage of the PCUs.
# Nokia Corporation
55 (57)
Table 17.
Number of PCUs 5 4
PCU usage
PCU configurations C H Usage of Abis TSLs 77% 70% Gb link size per PCU configuration 11 8
56 (57)
# Nokia Corporation
BSC traffic monitoring principles
BSC traffic monitoring principles

When the BSC dimensioning has been done accurately, traffic flow is at an optimal level, that is, traffic flow is as high as possible. You can use counters related to the radio interface to monitor the use and congestion level of the BSC. It is also useful to monitor the performance of all hardware units of the BSC. Good tools for this are EDGE key performance indicators (KPIs) and overload alarms related to the hardware units. For more information on EDGE KPIs, see the EDGE and GPRS Key Performance Indicators document. To check whether dimensioning has been successful, you need to compare real traffic against the traffic estimations done during the dimensioning. If there is a serious discrepancy, you have to re-plan the network.
# Nokia Corporation
57 (57)

BSC EDGE Dimension Ing

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC EDGE Dimension Ing

Uploaded by

Copyright:

Available Formats

BSC3120 Nokia GSM/EDGE BSS12 System Documentation

BSC EDGE Dimensioning

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

DN7032469 Issue 3-0 en draft

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

DN7032469 Issue 3-0 en draft

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

Changes made between issues 2-0 and 1-0

Traffic and quality inputs Network capabilities

The calculations in Examples of BSC EDGE dimensioning have been modified.

BSC traffic monitoring principles has been added.

DN7032469 Issue 3-0 en draft

BSC EDGE dimensioning

BSC EDGE dimensioning

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

DN7032469 Issue 3-0 en draft

dimensioning pre-planning detailed planning implementation optimisation modernisation

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

DN7032469 Issue 3-0 en draft

Key strategies for EDGE dimensioning

Key strategies for EDGE dimensioning

available data capacity required data capacity

Average voice traffic resource usage

Average available resources

Average voice traffic resource usage

Available data capacity

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

Required data capacity

Required EDGE Capacity

EDGE data Average voice traffic resource usage

Required data capacity

DN7032469 Issue 3-0 en draft

Prerequisites for BSC EDGE dimensioning

Prerequisites for BSC EDGE dimensioning

Input parameters for BSC EDGE dimensioning Status/value

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

Output of BSC EDGE dimensioning Value

DN7032469 Issue 3-0 en draft

BSC comparison BSC3i 2000 BSC3i 1000

Max. number of TRXs

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

BSC comparison (cont.) BSC3i 2000 BSC3i 1000

EGPRS-related BSC elements

DN7032469 Issue 3-0 en draft

Bit group switch (GSWB)

DN7032469 Issue 3-0 en draft

BSC EDGE Dimensioning

Two PCU HW in every BCSU for high EDGE traffic

PCUs and BCSUs in the BSC2i

Possible BSC configurations:

One to five PCU2 units in every BCSU in BSC3i 1000/2000.

Packet control unit (PCU)

DN7032469 Issue 3-0 en draft

Table 4. PCU type

BSCi, BSC2i 64 BSCi, BSC2i 64 BSCi, BSC2i 64 BSC3i 2 x 64