BTS Dimentioning

BSC3153 Nokia GSM/EDGE BSS, Rel. BSS13, BSC and TCSM, Rel. S13, Product Documentation, v.
BTS EDGE Dimensioning
DN7032593 Issue 4-0 en 25/03/2008
# Nokia Siemens Networks
1 (50)
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 (50)
DN7032593 Issue 4-0 en 25/03/2008
Contents
Contents
Contents 3 List of tables 4 List of figures 5 Summary of changes 7 1 2 3 4 4.1 4.2 5 5.1 5.2 5.2.1 5.2.2 5.2.3 5.3 5.3.1 5.3.2 5.4 5.5 6 BTS EDGE dimensioning 9 Planning process 13 Key strategies for EDGE dimensioning 15 Prerequisites for BTS EDGE dimensioning 19 Input summary 19 Output summary 21 Dimensioning process 23 Dimensioning of network elements and interfaces Inputs for BTS EDGE dimensioning 27 Deployment strategy 27 Network capabilities 30 Traffic and quality inputs 39 BTS EDGE dimensioning calculations 43 Available capacity strategy 43 Required capacity strategy 45 Outputs of BTS EDGE dimensioning 47 Key parameters in BTS EDGE dimensioning 48 BTS traffic monitoring principles 49 23
DN7032593 Issue 4-0 en 25/03/2008
3 (50)
List of tables Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Table 7. Table 8. Table 9. Input parameters for available data capacity dimensioning Input parameters for required data capacity dimensioning Output parameters of BTS EDGE dimensioning Mean number of timeslots available for GPRS GSM/EDGE hardware compatibility 30 37 21 29 19 20
The number of free timeslots for different configurations
Input signal level (for a normal BTS) at reference performance (BLER < 10%) for GMSK modulated signals. 40 Input signal level (for a MS) at reference performance for 8-PSK (BLER < 10%) modulated signals. 41 Minimum C/I for BLER < 10% in interference-limited scenarios (900 MHz band). 42 48
Table 10. Parameters for territory management
4 (50)
DN7032593 Issue 4-0 en 25/03/2008
List of figures
List of figures Figure 1. Figure 2. Figure 3. Figure 4. Figure 5. Figure 6. Figure 7. Figure 8. Figure 9. Territory method example Available data capacity Required data capacity 11
16 17 23 25 32 33 34
Available data capacity process Required data capacity process
An example of a baseband hopping configuration
An example of a mixed configuration BB hopping group
An example of a configuration that uses Multi BCF Control Baseband hopping in the GSM/EDGE configuration 39 35
Figure 10. GPRS territory Figure 11.
BTS dimensioning process for the available capacity strategy
44 47
Figure 12. BTS dimensioning process for the required capacity strategy
DN7032593 Issue 4-0 en 25/03/2008
5 (50)
6 (50)
DN7032593 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-0 Added information about Nokia Flexi EDGE BTS. Added software requirements for new application software: Extended Cell Range. 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. Chapters Prerequisites of BTS EDGE dimensioning and Key parameters in BTS EDGE dimensioning have been added. Information on Dual Transfer Mode, Extended Dynamic Allocation, High Multislot Classes and available GPRS resources within the circuit-switched design have been added to chapter Inputs for BTS EDGE dimensioning. In addition, GPRS territory and BTS configuration information has been updated. Information on software the do not affect dimensioning has been removed.
DN7032593 Issue 4-0 en 25/03/2008
7 (50)
Information that the outputs of BTS dimensioning are used in all other dimensioning phases has been added to chapter Outputs of BTS dimensioning. Chapter Examples of BTS 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. Information on Enhanced Quality of Service (EQoS) has been removed because it is not supported in BSS12.
Changes made between issues 2-0 and 1-0 Information on that the outputs of BTS dimensioning are used as inputs for Abis dimensioning has been added to BTS EDGE dimensioning and Outputs of BTS EDGE dimensioning. The inputs in Inputs for BTS EDGE dimensioning have been reorganised into the following categories:
.
Traffic and quality inputs Network capabilities
The radio timeslot terminology has been unified.
8 (50)
DN7032593 Issue 4-0 en 25/03/2008
BTS EDGE dimensioning

These guidelines provide information on dimensioning Nokia base stations for EDGE into an existing GSM network. The guidelines concentrate on the dimensioning of Nokia base station products that support EDGE. These products are Nokia Flexi EDGE Base Station, Nokia UltraSite EDGE Base Station, and Nokia MetroSite EDGE Base Station. The focus is on calculating the needed hardware equipment and modules. That is, the number of transceivers (TRXs) that satisfies the required capacity for both voice and data services on a BTS. The EDGE dimensioning guidelines in the BSS system documentation set cover BTS, Abis, BSC, and Gb dimensioning and some parts of preplanning. An example of BSS connectivity dimensioning is included in the BSC EDGE Dimensioning document. BTS dimensioning results in specific outputs that are used as inputs in the next dimensioning phases, Abis EDGE dimensioning, BSC EDGE dimensioning, and Gb EDGE dimensioning. Terms and definitions BTS BTS equipment, including all the base control functions (BCFs) on the same site. Cell Logical cell at the BTS site, usually transmitting from the antennas of one sector. GB Guaranteed bit rate refers to dedicated data capacity (dedicated timeslots) or guaranteed throughput. This is per cell, not per user. Non-GB Non-guaranteed bit rate refers to non-dedicated (default) data capacity or non-guaranteed throughput. This is per cell, not per user. Circuit-switched territory The number of consecutive radio traffic timeslots reserved for circuit-switched (CS) GSM calls. It also includes the free radio timeslots (spare CS territory)
DN7032593 Issue 4-0 en 25/03/2008
9 (50)
kept free by the BSC (the spare CS territory size defined with a BSC configuration parameter). The use of additional radio channels requires a territory upgrade and a channel request from the CS territory. Dedicated EGPRS channels Dedicated radio timeslots for the packet service data in the EGPRS system. These are traffic timeslots not available for voice. That is, the amount of dedicated EGPRS channels can be less or equal to the amount of default EGPRS channels. The dedicated EGPRS capacity is measured in percentage and specified with the dedicated GPRS capacity (CDED) parameter. Default EGPRS channels Timeslots that can be used for both voice and packet data (voice has higher priority than packet data), because they are always allocated to EGPRS when the circuit switched load permits this. The use of default EGPRS channels does not require the packet control unit (PCU) to make a request from the CS entity for permission to use these channels. The default EGPRS capacity is measured in percentage and specified with the default GPRS capacity (CDEF) parameter. Additional GPRS capacity This term is used with radio timeslots that are above and beyond the default GPRS capacity and that the BSC has allocated for GPRS use according to the requests from the PCU. The size of the additional GPRS territory can be restricted by the usermodifiable max GPRS capacity (CMAX) parameter. The guard time of the GPRS territory update specifies how often the PCU can request new radio timeslots for GPRS use. EGPRS territory Dedicated plus default EGPRS radio timeslots. This corresponds to the timeslots available for the packetswitched (PS) data. The size of the EGPRS territory is usually defined in radio network planning. However, the capacity limitations of the BSC often have an effect on the overall number of traffic channels (TCHs) in the EGPRS territories of the BSC area. The EGPRS territory also includes additional capacity timeslots, if allocated to EGPRS use by the BSC.
10 (50)
DN7032593 Issue 4-0 en 25/03/2008
TRX 1 TRX 2
BCCH
Circuit Switched Territory GPRS Territory
Max GPRS Capacity
Additional GPRS Capacity
Dedicated GPRS Capacity Default GPRS Capacity
Territory border moves based on Circuit Switched and GPRS traffic load
Figure 1.
Territory method example
Related topics
.
Abis EDGE Dimensioning BSC EDGE Dimensioning Gb EDGE Dimensioning
DN7032593 Issue 4-0 en 25/03/2008
11 (50)
12 (50)
DN7032593 Issue 4-0 en 25/03/2008
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
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
DN7032593 Issue 4-0 en 25/03/2008
13 (50)
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.
14 (50)
DN7032593 Issue 4-0 en 25/03/2008
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 predefined 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.
DN7032593 Issue 4-0 en 25/03/2008
15 (50)
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 2.
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.
16 (50)
DN7032593 Issue 4-0 en 25/03/2008
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 3.
Required data capacity
DN7032593 Issue 4-0 en 25/03/2008
17 (50)
18 (50)
DN7032593 Issue 4-0 en 25/03/2008
Prerequisites for BTS EDGE dimensioning
4
4.1

Input summary
The needed input information depends on the chosen dimensioning strategy. When the EDGE implementation is based on the available capacity strategy, the dimensioning process is more straightforward. When the required capacity strategy is used, also the traffic mix has to be taken into account. The input parameters for both strategies are presented in tables Input parameters for available data capacity dimensioning and Input parameters for required data capacity dimensioning. Available capacity The available radio interface capacity for data services can be estimated when the existing BTS hardware and the current voice traffic load is considered. It is possible to estimate the average available timeslots (TSLs) for data by taking into account the voice traffic at a certain allowed voice blocking rate and calculating the needed free timeslots of the current configuration. By assuming a certain throughput per timeslot and estimating the proportion of GPRS/EDGE users, a value for the maximum average throughput per cell can be calculated. Voice blocking remains unchanged, as long as timeslots are not dedicated for data and voice traffic does not increase.
Table 1. Input
Input parameters for available data capacity dimensioning Status/value

EDGE compatibility EDGE compatibility Number of TSLs
Activity
Verify (or upgrade) Verify (or upgrade) Measure
Hardware capability Software capability Voice traffic load
DN7032593 Issue 4-0 en 25/03/2008
19 (50)
Table 1. Input
TRX configuration
Input parameters for available data capacity dimensioning (cont.) Status/value

Signalling channels Free TSLs (guard TSLs) GPRS territory (dedicated, default, and additional) Number of TRXs Number of TSLs Number of TSLs Number of TSLs
Activity
Verify Verify (or define) Define Define
Deployment
Coverage Interference Throughput/TSL GPRS/EDGE
Single/multi-layer C/N C/I kbit/s %
Define Simulate/measure Simulate/measure Estimate Estimate
Required capacity In the required capacity strategy, the operator estimates the number of data users and the network is dimensioned accordingly. Typically, different types of user profiles are used. The required need for voice capacity defines the number of TSLs and possibly the use of half rate. The data volume can be estimated per cell, based on the estimation of average throughput/TSL. Another approach is to use subscriber information, that is, the number of users and data usage profiles.
Table 2. Input
Input parameters for required data capacity dimensioning Status/value

EDGE compatibility EDGE compatibility Number of TSLs Per cell
Activity
Verify (or upgrade) Verify (or upgrade Measure Estimate
Hardware capability Software capability Voice traffic load Data volume
20 (50)
DN7032593 Issue 4-0 en 25/03/2008
Table 2. Input
Traffic mix
Input parameters for required data capacity dimensioning (cont.) Status/value

Voice Data % % Single/multi-layer C/N C/I kbit/s %
Activity
Estimate Estimate Define Simulate/measure Simulate/measure Estimate Estimate
Deployment
Coverage Interference Throughput/TSL GPRS/EDGE
4.2
Output summary
The output of BTS EDGE dimensioning results in the BTS configuration and the estimation of EDGE performance. The main output parameters are presented in table Output parameters of BTS EDGE dimensioning.
Table 3. Output
TRX configuration
Output parameters of BTS EDGE dimensioning Value

Signalling channels Free TSLs (guard TSLs) GPRS territory (dedicated, default, and additional) Number of TRXs Number of TSLs Number of TSLs Number of TSLs kbit/s Coverage
Throughput/TSL Simulation results
DN7032593 Issue 4-0 en 25/03/2008
21 (50)
22 (50)
DN7032593 Issue 4-0 en 25/03/2008
Dimensioning process
5
5.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
DN7032593 Issue 4-0 en 25/03/2008
23 (50)
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 (carrierto-noise ratio (C/N), carrier-to-interference ratio (C/I)). 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. 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 (50)
DN7032593 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 2 TSL TRX 3 4 5 6
Cell
PCU
Basic unit
BTS
Abis
BSC
Gb
2G SGSN
Figure 5.
Required data capacity process
DN7032593 Issue 4-0 en 25/03/2008
25 (50)
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/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. 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. 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.
2.
3.
4.
5.
26 (50)
DN7032593 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.
5.2
5.2.1
Inputs for BTS EDGE dimensioning

Deployment strategy
An operator may have more than one layer (frequency or logical) in use in the network. The way data is deployed on different layers has an impact on the achieved throughput per timeslot. This section discusses different deployment strategies in detail. Single band network An operator with a single frequency band and narrow bandwidth has a challenging task for frequency planning. In such a case, even the broadcast control channel (BCCH) frequencies can be relatively interfered, at least in macro cells. To lower the interference level in the network, the operator may introduce half rate and start building micro and indoor cells. If the operator has a fairly wide bandwidth in use, it is possible to divide the frequencies for BCCH and traffic channel (TCH) usage to ensure better quality on the BCCH frequencies. Packet data can then be used on the BCCH transceivers (TRXs) to guarantee as large a data coverage as possible. In addition, half rate and micro and indoor cells may be used to lower the overall interference.
DN7032593 Issue 4-0 en 25/03/2008
27 (50)
Dual band network A dual band network allows the operator to use two different frequency bands for both voice and data services. In areas of high traffic density, the propagation loss of the higher frequency band ensures a lower interference level in the network. Macro/micro cells The location of the BTS antennas dictates the propagation environment. Macro cells have antennas above the average height of the rooftops, whereas micro cells have antennas clearly below roof tops, increasing the propagation loss significantly. In a dense traffic environment, micro cells lower the total interference level in the network, because the signals attenuate rapidly. This allows the operator to build a high-capacity network even if the bandwidth is fairly narrow. In a macro cell environment, signals propagate further, causing interference. When building macro sites, it is important to use antenna tilting and avoid situations where antennas point towards water areas or cause interference to remote areas (in other areas where radio waves propagate easily). In addition, it is recommended to use antennas with a narrow vertical beam width. A useful way to lower the interference from macro cells is to use natural or man-made obstacles to point antennas to. This attenuates the signal propagation towards a certain direction. Indoor/outdoor locations Operators need to build coverage almost anywhere where customers require service. This includes indoor locations, such as office buildings, shopping centres, airports, and underground parking garages. In these areas, interference is not usually as big a problem as in an outdoor environment. Walls, ceilings, and other materials in buildings or other indoor locations absorb signal energy. This decreases interference. However, it makes building indoor coverage more challenging, especially in large indoor areas. In indoor areas, interference tends to be very low regardless of the signal level. This allows very high data rates for packet-switched (PS) services if the signal level is adequate.
28 (50)
DN7032593 Issue 4-0 en 25/03/2008
Throughput per timeslot estimates If the network has already been launched with data (GPRS) services, the operator can monitor the average throughput values on a cell level and estimate the average throughput per timeslot (TSL). If the operator has not started with data services, measuring the average coverage and interference levels in the network helps to estimate the average data throughput values. If the network has not been launched or if the measuring would take too much time and resources, it is possible to use radio network planning tools to predict the average coverage and interference levels and estimate the average throughput values for EGPRS services. Available GPRS resources within the circuit-switched design A system designed for circuit-switched (CS) traffic usually allows basic GPRS throughput. Since the system has been designed for a sufficient margin to permit a low blocking level, some of the extra instantaneous capacity can be used for packet data transmission. As long as the packet traffic can be temporarily interrupted to accommodate the peaks in circuitswitched traffic, there is no decrease in the CS services. Table Mean number of timeslots available for GPRS shows the mean number of timeslots available for GPRS, for different numbers of TRXs per cell and for circuit-switched blocking probabilities of 1% and 2%. The free timeslots between territories are taken into account.
Table 4.
Mean number of timeslots available for GPRS GSM traffic (Erl) at 2% blocking
2.9 8.2 14.9
Number of GSM traffic TRXs (TCHs) (Erl) at 1% blocking

1 (7) 2 (14) 3 (22) 2.5 7.3 13.6
Mean free TCHs for GPRS at 1% blocking

3.5 5.2 6.9
Mean free TCHs for GPRS at 2% blocking

3.1 4.3 5.6
DN7032593 Issue 4-0 en 25/03/2008
29 (50)
5.2.2
Network capabilities
Hardware capabilities The Flexi EDGE BTS has 12 DTRX modules that can each carry 2 TRX objects. All the TRX objects in Flexi EDGE BTS are EGPRS capable. In UltraSite EDGE BTS, the GSM/EDGE radio frequency (RF) unit (TSxB) always requires an EDGE-capable baseband unit (BB2E or BB2F) even if it operates in GSM mode only. The EDGE-capable baseband unit (BB2E or BB2F) is backward compatible and also supports the GSM RF unit, TSxA. Table GSM/EDGE hardware compatibility shows the compatibility for the different BB2x and TSxx combinations. EGPRS support requires an EDGE-capable baseband unit (BB2E or BB2F) and an EDGE-capable RF unit (TSxB).
Table 5. Unit
GSM/EDGE hardware compatibility Compatibility

OK NOK OK OK OK OK
BB2A + TSxA BB2A + TSxB BB2E + TSxA BB2E + TSxB BB2F + TSxA BB2F + TSxB
BTS configurations This section describes the different BTS configurations in detail and includes recommendations for EGPRS. 1.
Low configurations (one or two TRX per cell)

The options are limited for one TRX per cell. EGPRS must be on the same TRX as the BCCH. It is recommended to set the dedicated/ default EGPRS territory to start from the last TSL 7 to maintain the data continuity. For two TRXs per cell, it is possible to decide whether EGPRS is set on the BCCH or TCH TRX. Setting the EGPRS territory on the BCCH TRX may ensure better carrier-to-
30 (50)
DN7032593 Issue 4-0 en 25/03/2008
interference ratio (C/I) performance if the operator has a limited frequency band in use for the TCH TRXs. It is recommended to introduce EGPRS in the BCCH layer first and then, when required (when there are no more TSLs available in the BCCH TRX), use the hopping layer. If an EDGE TRX (TSxB) is used, the baseband unit must be BB2E or BB2F. If TsxA is used, any baseband unit can be selected. 2.
High configurations (more than three TRXs per cell)

The same information applies as in the previous sections. If baseband (BB) hopping is used in a cell (preferably at least three TRXs), there are a few alternatives for the hardware configuration.
GSM hardware configuration: BB2A + TSxA

No limitations in baseband hopping: BB hopping can be used in the GSM mode. This configuration supports GPRS only.
GSM hardware configuration with EDGE BB unit: BB2E or BB2F + TsxA

No limitations in baseband hopping: BB hopping can be used in the GSM mode. This configuration supports GPRS only.
GSM/EDGE hardware configuration: BB2E or BB2F + TSxB

No limitations in baseband hopping. This configuration also supports BB hopping when EGPRS is activated.
Mixed GSM hardware with GSM/EDGE hardware configurations

In mixed configurations GSM and GSM/EDGE hardware are in the same sector/layer. In mixed configurations, baseband hopping is supported in the GSM mode only. In mixed configurations where baseband hopping is possible, only GPRS is supported. However, in the "Mixed GSM hardware: GSM/EDGE hardware configuration", also EGPRS is supported.
Mixed GSM hardware: BB2A and BB2E or BB2F with TSxA

Nokia UltraSite EDGE BTS SW CX3.3-1 allows baseband hopping in configurations where GSM RF units (TSxA) are controlled by any baseband unit. This is not possible with BTS software releases prior to CX3.3-1. Figure An example of a baseband hopping configuration illustrates a baseband hopping configuration with four TSxAs controlled by one BB2A and one BB2E or BB2F
DN7032593 Issue 4-0 en 25/03/2008
31 (50)
TS0
BCCH* BB2A
TS1
TS2
TS3
TS4
TS5
TS6
TS7 TSxA f1
TSxA f2
BB2E or BB2F
TSxA f3
TSxA f4
Timeslot 0 of TRXs 2-4 hop over MA (f2-f4) * BCCH timeslot does not hop
All 7 timeslots hop over MA (f1-f4)
Figure 6.
.
An example of a baseband hopping configuration
Mixed GSM hardware: BB2A and BB2E with TSxA and TSxB
Baseband hopping between TSxA and TSxB is not possible in this configuration without Multi BCF Control. The TSxB and TSxA units need to be configured in their own hopping groups and have separate BTS objects for TSxA and TSxB units.
Mixed GSM hardware: BB2A and BB2F with TSxA and TSxB
CX3.3-1 software and BB2F unit enable a mixed configuration BB hopping groups to be formed within UltraSite EDGE BTS. Mixed configuration BB hopping has the following constraints: a mixed configuration hopping group is restricted to GMSK calls only and each new TSxB that is configured for mixed configuration BB hopping requires a BB2F unit to control it. In this way, TSxB may be used to replace TSxA without loss of GMSK. Figure An example of a mixed configuration BB hopping group illustrates a possible mixed configuration BB hopping group with two TSxAs and two TSxBs, controlled by one BB2A and one BB2F.
32 (50)
DN7032593 Issue 4-0 en 25/03/2008
TS0
BCCH* BB2A
TS1
TS2
TS3
TS4
TS5
TS6
TS7 TSxA f1
TSxA f2
TSxB f3
BB2F
TSxB f4
Figure 7.
.
An example of a mixed configuration BB hopping group
Mixed GSM hardware: GSM/EDGE hardware configuration

When EGPRS is enabled, the EDGE-capable TRXs have to be configured to separate hopping groups from the GSM TRXs. In mixed GSM hardware with GSM/EDGE hardware configurations, the EDGE TRXs can be configured to separate hopping groups by using Multi BCF Control. For more information on Multi BCF Control, see Overview of Multi BCF Control in BSC.
DN7032593 Issue 4-0 en 25/03/2008
33 (50)
BTS-1: NON-EDGE TRXs TRX-1 BTS-1 TRX-2 BB2A
TS0
BCCH*
TS1
TS2
TS3
TS4
TS5
TS6
TS7 TSxA f1 TSxA f2 TSxB f3 TSxB f4
TRX-3 BTS-1' TRX-4
BB2E or BB2F
BTS-1': EDGE TRXs
Timeslot 0 of TRXs 3-4 hop over MA (f3-f4)
Timeslot 0 of TRX2 is using MA (f2)
All 7 timeslots hop over MA (f3, f4)
* BCCH timeslot does not hop
All 7 timeslots hop over MA (f1, f2)
Figure 8.
.
An example of a configuration that uses Multi BCF Control
GSM/EDGE hardware configuration

There are no limitations in baseband hopping in the GSM/EDGE configuration when EGPRS is enabled.
34 (50)
DN7032593 Issue 4-0 en 25/03/2008
TS0
BCCH* BB2E or BB2F
TS1
TS2
TS3
TS4
TS5
TS6
TS7 TSxB f1
TSxB f2
BB2E or BB2F
TSxB f3
TSxB f4
Figure 9.
Baseband hopping in the GSM/EDGE configuration
Software capabilities This section describes the interaction of the key data features that have an effect on EDGE dimensioning.
.
Extended Cell Range In Extended Cell Range, the PCU and DX count EGTCHs just as they count normal EGPRS TCHs into the EGPRS and EDAP channel capacities of the PCU. The DX counts EGTCHs into the BCSU TCH capacity during TRX creation, TRX modification, and TRX swap procedures. Further, EGTCHs which are not connected to a PCU are counted into the active TCH channels of the BCSU. Both PCU and DX consider EGTCH territory as separate from that constituted by normal EGPRS TCHs in the BCCH BTS. Also, the handling of an EGTCH territory differs from that of a normal EGPRS territory - most notably in that dynamic territory operations are not applied to an EGTCH territory.
DN7032593 Issue 4-0 en 25/03/2008
35 (50)
In order to keep PCU appropriately informed about EGPRS TCHs and their division into EGTCH and normal EGPRS territories, separate fields for EGTCHs and EGTCH territory information shall be added as necessary to any PCUSIG messages carrying information about EGPRS TCHs and EGPRS territories.
.
GPRS coding schemes CS-3 and CS-4 (GPRS rel2) GPRS coding schemes CS-3 and CS-4 contain less error correction and offer higher bit rates (up to 14.4 kbit/s with CS-3 and 21.4 kbit/s with CS-4) per timeslot. This has an impact on BSC dimensioning because the PCU card has a maximum processing capacity that is exceeded earlier when higher bit rates per timeslot are used. GPRS coding schemes CS-3 and CS-4 require PCU2 (PCU2-U or PCU2D). GPRS coding schemes CS-3 and CS-4 are used in the example cases in the EDGE dimensioning guidelines. CS-3 and CS-4 do not fit into one 16 kbit/s Abis/PCU channel. They require the use of Dynamic Abis and EDGE TRXs.
Dual Transfer Mode Dual Transfer Mode (DTM) means a simultaneous voice and data connection that can be supported in cells that include GPRS territory. A DTM temporary block flow (TBF) is established in EGPRS mode if the mobile station (MS) is EGPRS capable and if the DTM call is allocated from an EGPRS-capable PS territory. If not, the DTM TBF is established in GPRS mode. DTM is licence controlled and an active licence is required to operate DTM. For more information on DTM, see Dual Transfer Mode System Feature Description.
Extended Dynamic Allocation (EDA), and High Multislot Classes (HMC) High Multislot Classes (HMC) and Extended Dynamic Allocation (EDA) enable a combined downlink and uplink timeslot sum of 6. The new maximum allocations are 5+1 or 4+2. With EDA support, also 3+3 and 2+4 are possible. EGPRS must be available and active in the network for HMC and EDA to work. Certain DTM channel configurations can be supported only if Gs interface is also supported. With paging coordination the MS can make or receive voice calls even when it is in packet transfer mode. This is enabled by Network Operating Mode I (NOM I) that requires the optional Gs interface between MSC and SGSN. EDA and HMC are licence controlled and an active licence is required to operate these.
36 (50)
DN7032593 Issue 4-0 en 25/03/2008
For more information on HMC, see High Multislot Classes System Feature Description. For more information on EDA, see Extended Dynamic Allocation System Feature Description. Free timeslot (guard timeslot) The guard TSLs are used to cope with voice pre-emption. There are timeslots between the CS and the PS territory. They are used temporarily by voice while a downgrade in the PS territory is being performed to allocate a new voice call. Preliminary values for the number of free timeslots in the CS territory are given in table The number of free timeslots for different configurations. The mean number of free timeslots in the CS territory is also given. The assumption is that there are, on average, an equal number of upgrades and downgrades.
Table 6. TRXs
The number of free timeslots for different configurations Free TSLs (after a CS downgrade)
1 1 1 2 2 2
Free TSLs (after a CS upgrade)

1 2 2 3 4 4
Mean free TSLs in the CS territory

1 1.5 1.5 2.5 3 3
1 2 3 4 5 6
Signalling channels
Common BCCH
The usage of a common BCCH has an effect only on dual band sectors where the cell signalling channels of the other band are not needed, leaving more timeslots for voice and data.
GSM and EGPRS sharing a common control channel (CCCH)
DN7032593 Issue 4-0 en 25/03/2008
37 (50)
According to GSM, GPRS and EDGE Performance by Halonen, Romero, and Melero, one CCCH supports from one to two TRXs with the combined configuration and from two to seven TRXs with the non-combined configuration. The blocking probability is 0-2%. For voice, a non-combined configuration is normally needed for just two TRXs. According to GSM, GPRS and EDGE Performance by Halonen, Romero and Melero, one paging control channel (PCCH) allocated on one packet data channel (PDCH) supports more than six TRXs dedicated to EGPRS. The blocking probability is 0-2%. If the PCCH is used, EGPRS does not have an impact on the access grant channel (AGCH) and paging channel (PCH). Dedicated, default, and additional GPRS territories It is possible to define, per cell, dedicated timeslots exclusively for GPRS. Only GPRS can use these TSLs that can cause additional blocking for voice services. By using dedicated timeslots, the operator can ensure a minimum throughput for PS services. Circuit switched traffic has priority outside the dedicated territory. Within the default GPRS territory, timeslots are allocated for GPRS when the CS load permits this. A dedicated territory is a subset of the default territory. When the default GPRS capacity is allocated for GPRS, and the GPRS load increases, the PS radio resource management (RRM) can request additional TSLs. Based on the circuit-switched load, the CS RRM controls the allocation of additional TCHs. The territories consist of consecutive timeslots which is important for multislot operation. The maximum GPRS territory is defined by the capacity parameter max GPRS capacity. The default territory size should be carefully considered. If the territory is large, multislot MSs are well supported. This, however, leads to frequent territory downgrades by the CS RRM, after which upgrade and intra-cell handover may be triggered. The network (including the PCU and the Abis interface) must also be capable of supporting large territories. If the territory is small, multislot MSs cannot be fully used. In addition, the number of territory upgrades grows, leading to intra-cell handovers. A typical rule used in determining the default territory is: CDEF = max(MS capability, GPRS traffic in cell) Figure GPRS territory illustrates the concept of the GPRS territory.
38 (50)
DN7032593 Issue 4-0 en 25/03/2008
TRX 1 TRX 2
BCCH
Circuit Switched Territory GPRS Territory
Max GPRS Capacity
Additional GPRS Capacity
Dedicated GPRS Capacity Default GPRS Capacity
Territory border moves based on Circuit Switched and GPRS traffic load
Figure 10.
GPRS territory
5.2.3
Traffic and quality inputs

This section presents the minimum requirements for carrier-to-noise ratio (C/N, coverage) and C/I (interference) for different coding schemes and describes the theory behind calculating (or estimating) the throughput per TSL. The TSL throughput calculation is important because the required number of timeslots for data is totally dependent on the throughput of a single timeslot. Experiences from different networks show that the average throughput per timeslot for EDGE is about 30-36 kbps. Minimum requirements for coverage In a PS network, the quality of service perceived by the user is typically measured by the data throughput and the effective delay of the transmitted data. Detailed network planning of the radio interface should ensure that the required coverage, capacity, and user throughput is available for the system launch. The coverage planning aspects of GPRS implementation include the provision of sufficient C/N ratios across the coverage area to allow successful data transmission, on both uplink and downlink. Each coding scheme defined for GPRS is suited to a particular range of C/N (or Eb/No) for a given block error rate (BLER). Generally, the higher the level of error protection, the lower required C/N.
DN7032593 Issue 4-0 en 25/03/2008
39 (50)
Due to the differing C/N requirements of the coding schemes, their relative coverage areas are different. In addition to the existing GSM voice service, it is useful to compare the relative predicted coverage areas of the coding scheme. In a mobile network, cells have to overlap to ensure mobility. This results in a better overall coverage than in a case of an isolated cell. In urban areas, cells tend to be much closer to each other. In this case, the interference caused by reused frequencies is usually the limiting factor, not the coverage. For example, in a dense urban environment where indoor coverage has to be good, handovers may take place at very high RX level values. In this case, it is possible that even the highest coding schemes can be used almost everywhere within that cell if the interference level is low. Tables Input signal level (for a normal BTS) at reference performance (BLER < 10%) for GMSK modulated signals and Input signal level (for an MS) at reference performance for 8-PSK (BLER < 10%) modulated signals give reference values for the minimum signal level for different coding schemes. That is, the received signal level (without interference) has to be at a certain level to achieve the maximum throughput per TSL. For example, for an MS receiving with the coding scheme MCS-6 (8-PSK modulated signal), the signal level has to be at least -91 dBm without any interference (in the typical urban 50 km/h propagation model without frequency hopping) to achieve the maximum throughput of 29.6 kbps per TSL. Below this signal level, a lower coding scheme has to be used. The tables are from 3GPP specifications.
Table 7.
Input signal level (for a normal BTS) at reference performance (BLER < 10%) for GMSK modulated signals. Propagation conditions
Static TU50 (no FH) TU50 (ideal FH) -104 (x) -101 -99 -90 RA250 (no FH) -104 (x) -101 -98 * HT100 (no FH) -103 -99 -96 *
Type of channel
PDTCH/CS1 PDTCH/CS2 PDTCH/CS3 PDTCH/CS4
dBm dBm dBm dBm
-104 (x) -104 -104 (x) -100 -104 (x) -98 -101 -90
40 (50)
DN7032593 Issue 4-0 en 25/03/2008
* PDTCH for MCS-x cannot meet the reference performance for some propagation conditions.
Table 8.
Input signal level (for a MS) at reference performance for 8-PSK (BLER < 10%) modulated signals. Propagation conditions
Static TU50 (no FH) -93 -91 -84 -83** 78.5** TU50 (ideal FH) -94 -91.5 -84 -83** 78.5** RA250 (no FH) -93 -88 * * * HT100 (no FH) -92 -89 -83** * *
Type of channel
PDTCH/ MCS-5 PDTCH/ MCS-6 PDTCH/ MCS-7 PDTCH/ MCS-8 PDTCH/ MCS-9
dBm dBm dBm dBm dBm
-98 -96 -93 -90.5 -86
* PDTCH for MCS-x cannot meet the reference performance for some propagation conditions ** Performance is specified at 30% BLER. Minimum requirements for interference The minimum BTS and MS performance in interference-limited scenarios have been included in the 3GPP specifications. The minimum performance is specified as the minimum carrier-to-interference (C/I) required to achieve 10% BLER for different channel conditions. In addition to the fact that the signal level has to be at a minimum level for certain throughput, it also has to exceed the minimum required C/I value for that particular coding scheme. For example, an MS receiving with coding scheme MCS-6 (minimum signal level -91 dBm) can use the maximum throughput per TSL if the current interference level is 18 dB below the current signal level. The values in the table are minimum required values. The real throughput achieved is affected by the MS and BTS properties. The current interference situation in a mobile network depends on the deployment strategy.
DN7032593 Issue 4-0 en 25/03/2008
41 (50)
Table 9.
Minimum C/I for BLER < 10% in interference-limited scenarios (900 MHz band). Propagation conditions
TU3 (no FH) TU3 (ideal FH) 9 13 15 23 TU50 (no FH) 10 14 16 23 TU50 (ideal FH) 9 13 15 23 RA250 (no FH) 9 13 16 Perform ance not met 9 13 16 Perform ance not met 16 21 26.5 (30% BLER) Perform ance not met Perform ance not met
Type of channel
PDTCH/CS-1 13 PDTCH/CS-2 15 PDTCH/CS-3 16 PDTCH/CS-4 19
PDTCH/ MCS-1 PDTCH/ MCS-2 PDTCH/ MCS-3 PDTCH/ MCS-4 PDTCH/ MCS-5 PDTCH/ MCS-6 PDTCH/ MCS-7 PDTCH/ MCS-8 PDTCH/ MCS-9
13 15 16 21
9 13 15 23
9 13 16 27
9 13 16 27
18 20 23.5
14.5 17 23.5
15.5 18 24
14.5 17.5 24.5
28.5
29
30
30
30
32
33
35
42 (50)
DN7032593 Issue 4-0 en 25/03/2008
5.3
BTS EDGE dimensioning calculations

The accuracy of BTS dimensioning depends on the accuracy of the input values. The capacity of the radio interface has a significant role in defining the capacity of the rest of the network elements in the BSS and GPRS core network (the BSC, SGSN, and transmission interfaces between the different network elements). Changes in the BTS configurations have direct impact on the BSC and SGSN configuration. The BSC can handle a limited number of BTSs, transceivers (TRXs), and timeslots (TSLs). The packet control units (PCUs) have maximum data traffic limitations and restrictions for the number of packet processing units (PAPUs) in the SGSN.
5.3.1
Available capacity strategy

Using the existing BTS hardware, the operator can, with minimum effort, estimate the available radio interface capacity for data services on top of voice. As the current voice traffic is known, it is fairly easy to calculate the average available capacity for data services. It is possible to estimate the average available timeslots for data by taking into account the current voice traffic at a certain allowed voice blocking rate and calculating the needed free timeslots of the current configuration. By assuming certain throughput per timeslot and estimating the proportion of GPRS/EDGE users, a value for the maximum average throughput per cell can be calculated. Voice blocking remains unchanged, as long as timeslots are not dedicated for data if voice traffic does not increase. Calculations 1. Calculate the available data timeslots . Calculate/measure the current voice traffic per cell. . If the measured traffic is not available, use the current configuration for voice traffic calculations (that is, based on the number of available traffic). . Make a note of the signalling channels and free timeslots. . Calculate the available timeslots for data traffic. . 8 x the number of TRXs signalling channels free TSLs voice erlangs Calculate the achieved TSL throughput. . Consider the coverage and interference situation. . deployment strategy . Estimate the GPRS/EGPRS division.
2.
DN7032593 Issue 4-0 en 25/03/2008
43 (50)
Estimate the average throughput per TSL for GPRS and EDGE. . Calculate the average throughput on different cell layers. Calculate the average throughput per TSL. . Use the GPRS/EGPRS traffic division.
3.
Calculate the achieved average throughput. . Multiply the number of data TSLs by the average throughput per TSL. . Calculate the average throughput on different cell layers. Check the result. . If the data throughput is too low, consider introducing half rate or dual rate for voice to increase the number of TSLs for data.
4.
Figure BTS dimensioning process for the available capacity strategy presents the process of dimensioning data traffic on top of voice traffic.
STEP 1: Calculate the available data TSLs

1.1 Calculate/measure the current voice traffic (based on measurements or configuration) 1.2 Make a note of the signalling channels and free timeslots 1.3 Calculate the available timeslots for data traffic The available TSL for data is: 8 X TRX - signalling channels - free TSLs voice erlangs
STEP 2: Calculate the achieved TSL throughput
STEP 3: Calculate the achieved TSL throughput
STEP 4: Check the result

4.1 If the data throughput is too low consider introducing half/ dual rate for voice to increase the number of TSLs for data
2.1 Consider the coverage 3.1 Multiply the data TSLs and interference situation by the average throughput (deployment strategy) per TSL (calculate the average throughput on 2.2 Estimate the GPRS/ different cell layers) EGPRS division 2.3 Estimate the average throughput for GPRS and EDGE 2.4 Calculate the average throughput per TSL
Figure 11.
BTS dimensioning process for the available capacity strategy
44 (50)
DN7032593 Issue 4-0 en 25/03/2008
5.3.2
Required capacity strategy

The operator may want to estimate the needed capacity based on assumptions on the number of data users in the network and on the average user traffic during busy hour. Different types of user profiles can be in use. Traffic mix
Voice
For voice traffic, the operator has a few options on how the voice capacity is used in the radio interface. The most significant impact on the number of needed timeslots is whether half rate is used. In addition, the maximum allowed voice blocking must be defined. EGPRS cannot be used on half rate TRXs. However, it can be used on dual rate timeslots. In these guidelines, the voice traffic/user is assumed to be 25 mErl.
Data
Data volume per cell can be calculated (or estimated) as the total data volume per cell or it can be based on subscriber information. The simplest way is to estimate the total data volume going through a cell during a busy hour, based on the available average throughput for EGPRS-enabled timeslots. Calculating traffic using subscriber information is more complicated. First, the total number of subscribers (or the data user penetration value) must be known. Then, the user data amount per busy hour must be estimated as a total value or based on assumptions of data usage (for example, Internet, FTP, and e-mail). A significant factor in the dimensioning of the radio interface is the coding scheme. The coding scheme has a significant role when the total throughput on cell basis is calculated. For GPRS, the slowest coding scheme (CS-1) has a user bit rate of 9.05 kbps; the fastest (CS-4) has a user bit rate of 21.4 kbps. For EGPRS, the respective values are 8.8 kbps for MCS-1 and 59.2 kbps for MCS-9. Calculations 1. Calculate the required throughput. . Calculate the payload per cell during busy hour. . the number of data users or data user penetration . data user profile(s)
DN7032593 Issue 4-0 en 25/03/2008
45 (50)
. .
Transfer payload to throughput (kbps). Make a note of whether the throughput has to be guaranteed or not (GB or non-GB).
2.
Estimate the average data throughput per timeslot, based on assumptions of the applied deployment strategy. . frequency band . indoor/outdoor . GPRS/EGPRS division . Estimate the achieved throughput/TSL of the different layers. Calculate the needed TSLs/TRXs and the final throughput. . Calculate the needed data TSLs. . Make a note of the needed voice TSLs at the required blocking rate. . GB/non-GB . Calculate the needed signalling channels. . combined/non-combined . stand-alone dedicated control channel (SDCCH) configuration . Make a note of the free TSLs. . Calculate the number of required TRXs. . Calculate the achieved throughput with the required configuration. Check the result. . OK . over-dimensioned . Introduce half rate/dual rate. . Lower throughput requirements: Check if there is enough bandwidth (C/I requirements can be met) for the number of TRXs. . OK . If not OK, take the necessary actions.
3.
4.
Figure BTS dimensioning process for the required capacity strategy presents the process of dimensioning data traffic for the required capacity strategy.
46 (50)
DN7032593 Issue 4-0 en 25/03/2008
STEP 1: Calculate the required throughput

1.1 Calculate the payload per cell during a busy hour - the number of data users or data user penetration - data user profile(s) 1.2 Transfer payload to the required throughput 1.3 Define whether GB or non-GB is used
STEP 2: Estimate the achieved TSL throughput

2.1 Make a note of the coverage and interface situation - deployment strategy 2.2 Estimate the GPRS/ EGPRS division 2.3 Estimate the average throughput for GPRS and EDGE
STEP 3: Calculate the needed TSL/TRX and final throughput

3.1 Calculate the needed data TSL 3.2 Make a note of the needed voice TSLs at a certain blocking rate - GB/non-GB 3.3 Calculate the needed signalling channels
STEP 4: Check the result

4.1 Check whether the BTS is over dimensioned - introduce half rate/ dual rate - lower the throughput requirements 4.2 Check that the C/I requirements are met
3.4 Make a note of the 2.4 Calculate the average free TSLs throughput per TSL 3.5 Calculate the required TRXs 3.6 Calculate the achieved throughput with the required configuration
Figure 12.
BTS dimensioning process for the required capacity strategy
5.4
Outputs of BTS EDGE dimensioning

The outputs of dimensioning BTS are used as inputs in the next dimensioning phases. The BTS output information includes the following:
.
throughput/timeslot (TSL) data TSL/transceiver (TRX) TSL configuration of TRXs number of TRXs/cell simulation results
The key output of BTS dimensioning is the number of TRX units.
DN7032593 Issue 4-0 en 25/03/2008
47 (50)
5.5
Key parameters in BTS EDGE dimensioning

The key parameters that need to be taken into consideration in BTS EDGE dimensioning and planning are listed in table Parameters for territory management.
Table 10. Parameter
Parameters for territory management Value

Y/N Y/N % % Y/N sec % sec %
Level
BTS TRX BTS BTS BTS BSC BTS BSC BSC
EGPRS enabled GPRS enabled TRX dedicated GPRS capacity default GPRS capacity prefer BCCH frequency GPRS GPRS territory update guard time max GPRS capacity free TSL for CS upgrade free TSL for CS downgrade
48 (50)
DN7032593 Issue 4-0 en 25/03/2008
BTS traffic monitoring principles
BTS traffic monitoring principles

BTS dimensioning focuses on defining the number of required timeslots and, consequently, the number of transceiver (TRX) units. The packet data traffic channel (PDTCH) congestion key performance indicators (KPIs) Downlink multislot allocation blocking, Downlink multislot soft blocking, and Downlink TBFs per timeslot are very useful in BTS traffic monitoring and detecting the potential need to optimise the configuration. For more information on the KPIs, see chapter Congestion KPIs in the EDGE and GPRS Key Performance Indicators document. If the operator has not dedicated any capacity for EGPRS, voice blocking is not affected by data traffic, because voice always has priority over data in such a case. If dedicated data capacity is used, voice blocking caused by data traffic may occur. When dedicated data capacity is used, increased voice blocking is fairly easy to notice compared to a situation where dedicated data capacity is not used. If voice blocking increases (without increased voice traffic) after a dedicated EGPRS territory is introduced, it is obvious that the dedicated data capacity causes the voice blocking. This should trigger a capacity expansion or a review of the number of dedicated data timeslots in the cells that suffer from blocking. Alternatively, if the voice capacity usage is very low, the data territory can be increased (if necessary) or the TRX count lowered. If the dimensioned data capacity is too low, both the data usage and the territory upgrade rejection ratio can be very high. In this case, the dedicated data capacity should be increased. If the dimensioned data capacity is too high, the data usage and territory upgrade ratio are very low. In this case, the dedicated data capacity can be lowered. If the statistics show that according to the Downlink multislot allocation blocking KPI there is blocking but there are no upgrade requests yet, the reason may be that the territory is smaller than defined in the default settings (circuit-switched (CS) use). The packet control unit (PCU) will not
DN7032593 Issue 4-0 en 25/03/2008
49 (50)
make an upgrade request. This is because the CS side returns the default channels back to the packet-switched (PS) territory as soon as the CS load allows this. This means that territory upgrade rejections may not happen even if there is a lack of resources.
50 (50)
DN7032593 Issue 4-0 en 25/03/2008

BTS Dimentioning

Загружено:

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

Исходное описание:

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

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

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

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

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

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

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

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

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

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

BTS Dimentioning

Загружено:

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

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

BSC3153 Nokia GSM/EDGE BSS, Rel. BSS13, BSC and TCSM, Rel. S13, Product Documentation, v.

BTS EDGE Dimensioning

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning

# Nokia Siemens Networks

DN7032593 Issue 4-0 en 25/03/2008

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning

The number of free timeslots for different configurations

Table 10. Parameters for territory management

# Nokia Siemens Networks

DN7032593 Issue 4-0 en 25/03/2008

Available data capacity process Required data capacity process

An example of a baseband hopping configuration

An example of a mixed configuration BB hopping group

Figure 10. GPRS territory Figure 11.

BTS dimensioning process for the available capacity strategy

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning

# Nokia Siemens Networks

DN7032593 Issue 4-0 en 25/03/2008

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning

Traffic and quality inputs Network capabilities

The radio timeslot terminology has been unified.

# Nokia Siemens Networks

DN7032593 Issue 4-0 en 25/03/2008

BTS EDGE dimensioning

BTS EDGE dimensioning

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning

# Nokia Siemens Networks

DN7032593 Issue 4-0 en 25/03/2008

BTS EDGE dimensioning

Circuit Switched Territory GPRS Territory

Max GPRS Capacity

Additional GPRS Capacity

Dedicated GPRS Capacity Default GPRS Capacity

Territory method example

Abis EDGE Dimensioning BSC EDGE Dimensioning Gb EDGE Dimensioning

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning

# Nokia Siemens Networks

DN7032593 Issue 4-0 en 25/03/2008

dimensioning pre-planning detailed planning implementation optimisation

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning

# Nokia Siemens Networks

DN7032593 Issue 4-0 en 25/03/2008

Key strategies for EDGE dimensioning

Key strategies for EDGE dimensioning

available data capacity required data capacity

DN7032593 Issue 4-0 en 25/03/2008

# Nokia Siemens Networks

BTS EDGE Dimensioning