Dimension Ing Wcdma Ran

RNC3267_trial Nokia WCDMA RAN, Rel. RAS06, System Library, v.
Dimensioning WCDMA RAN
DN70118376 Issue 2-0 en 18/06/2007
# Nokia Siemens Networks
1 (113)
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 2007. All rights reserved.
2 (113)
DN70118376 Issue 2-0 en 18/06/2007
Contents
Contents
Contents 3 Summary of changes 5 1 2 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1 3.3.2 4 4.1 4.1.1 4.1.2 4.2 4.2.1 4.2.2 4.2.3 4.3 5 5.1 5.1.1 5.1.2 5.2 5.2.1 5.2.2 5.2.3 5.3 6 7 7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.2 7.2.1 Introduction to dimensioning WCDMA RAN 7 Dimensioning Air interface 11 R99 DCH dimensioning 15 Intoduction to R99 DCH dimensioning 15 R99 DCH coverage dimensioning 17 Uplink link budget 17 Downlink link budget 22 Cell range and coverage 26 R99 DCH capacity dimensioning 28 Load calculation based on traffic inputs 28 DL power calculation vs. load 30 HSDPA dimensioning 33 Introduction to HSDPA dimensioning HSDPA features in RAS06 35 Supporting R99 formulas 36 HSDPA coverage dimensioning 36 Uplink link budget 36 Downlink link budget 37 Cell range and coverage 41 HSDPA capacity dimensioning 42 HSUPA dimensioning 45 Introduction to HSUPA dimensioning HSUPA features in RAS06 47 Supporting R99 formulas 48 HSUPA coverage dimensioning 48 Uplink link budget 48 Downlink link budget 52 Cell range and coverage 52 HSUPA capacity dimensioning 53 33
45
Dimensioning transport network 57 Dimensioning BTS 61 Dimensioning Flexi WCDMA BTS 61 Capacity 62 Baseband capacity and HSDPA 63 Capacity licenses 64 Flexi WCDMA BTS and transmission 65 Dimensioning UltraSite WCDMA BTS 65 WSPA/C processing capacity 67
DN70118376 Issue 2-0 en 18/06/2007
3 (113)
7.2.2 7.2.3 7.2.4 7.3 7.3.1 7.4 7.5 7.6 7.7 7.7.1 7.7.1.1 7.7.1.2 7.7.1.3 7.7.1.4 7.7.1.5 7.7.1.6 7.7.1.7 7.7.2 8 9 9.1 9.1.1 9.1.2 9.1.3 9.1.4 9.1.5 9.1.6 9.1.7 9.1.8 9.1.9 9.2 9.3 9.4 9.5 9.6 9.7
UltraSite WCDMA BTS baseband capacity and HSDPA Dimensioning steps 69 HSPA sharing 71 HSDPA and BTS dimensioning 72 Tcell grouping 74 HSUPA and BTS dimensioning 75 Extended Cell 77 BTS counters 78 WCDMA BTS capacity allocation principles 79 UltraSite WCDMA BTS 79 Primary/Secondary WAM 80 Master/Slave WAM 80 WSP and WAM allocation within a subrack 81 Common Control Channel (CCCH) allocation 82 Dedicated Channel (DCH) allocation 84 Recovery actions 88 HSDPA 89 Flexi WCDMA BTS 94 Dimensioning RNC 95 Dimensioning interfaces 97 Dimensioning Iub interface 97 Transport Bearer Tuning 97 Hybrid transport 98 Iub VCC configuration 98 Protocol overheads 101 Connection Admission Control 102 Iub signalling links 102 Examples of Iub configurations 104 Interface capacity 105 BTS internal link configurations 106 HSDPA and Iub dimensioning 106 Dimensioning Iur interface 107 Dimensioning Iu-CS interface 109 Dimensioning Iu-PS interface 111 Dimensioning Iu-BC interface 112 Iu and Iur MTP3 links 112
68
4 (113)
DN70118376 Issue 2-0 en 18/06/2007
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 between issues 1-3 and 2-0
Dimensioning Air interface:

This section has been updated with information on R99 DCH dimensioning, HSDPA dimensioning and HSUPA dimensioning.
R99 DCH dimensioning:

This is a new section.
HSDPA dimensioning:
HSUPA dimensioning.
Dimensioning BTS:
Sections Dimensioning Flexi WCDMA BTS, Dimensioning UltraSite WCDMA BTS and HSDPA and BTS dimensioning have been updated. New sections HSUPA and BTS dimensioning, Extended Cell and BTS counters have been added.
Dimensioning RNC:
RNC-related dimensioning information has been updated to RAS06 level.
Dimensioning interfaces:
DN70118376 Issue 2-0 en 18/06/2007
5 (113)
Sections Dimensioning Iub interface and Iu and Iur MTP3 links have been updated.
Table 1. Changed chapter

Dimensioning BTS Dimensioning interfaces RAN features and dimensioning
Modified chapters in Dimensioning WCDMA RAN in issue 1-3 See

Dimensioning UltraSite BTS Dimensioning Iu-PS interface RAN features and dimensioning
Impact
The number of cells handled by one WSPC has been corrected. The steps of Iu-PS dimensioning have been simplified. A reference has been corrected.
Table 2. Changed chapter

Dimensioning BTS
Modified chapters in Dimensioning WCDMA RAN in issue 1-2 See

Flexi BTS
Impact
Information on the baseband Extension Module has been added. Carrier configurations have been updated. The number of cells and users for Flexi BTS have been updated. Information on the maximum size of AAL2 Path has been added.
Dimensioning BTS Dimensioning interfaces
HSDPA and BTS dimensioning Dimensioning Iub interface
6 (113)
DN70118376 Issue 2-0 en 18/06/2007
Introduction to dimensioning WCDMA RAN

Purpose
Dimensioning is the initial phase of network planning. During dimensioning, the first configuration estimates and requirements for coverage, capacity and quality of service are planned. The approximate number of necessary base station sites and base stations, the average values for the power budget, cell size, capacity, and initial network configuration are estimated at this phase. The capacity requirements and the overall quality of service targets determine the selection of the RAN transport network and the transport interfaces of base stations and RNC GSM operators can use dimensioning to estimate the service capability of the existing network in case of site reuse. Note that in the dimensioning phase, only average values for the network can be calculated. More exact values for individual sites are calculated in the actual planning phase. The dimensioning instructions given in this document apply to RAS06 system release, consisting of Nokia WCDMA BTS release WBTS4.0 and Nokia WCDMA RNC release RN3.0.
Before you start
Check:
.
Traffic expectations. An accurate traffic forecast is important in network dimensioning. Deviations must be taken into account in capacity planning. Population density in the area. Specify areas of population that should be covered in each phase of roll-out. Location probability. Specify system area availability indoors/ outdoors.
DN70118376 Issue 2-0 en 18/06/2007
7 (113)
Regulations, for example, spectrum allocations (FDD/TDD and licenced/unlicenced) and transmit power limitations. Specific system performance parameters.
The basic parameters for dimensioning are the following:

.
quality of service in terms of call blocking and coverage probability per service estimated traffic requirements for voice users estimated traffic requirements for real-time and packet data users development of service requirements, the service profile as a function of time radio network area information: the total area, division into different sub-areas or area types, and the user distribution for each sub-area
Summary
Radio network dimensioning activities include coverage, capacity, and quality of service analysis. The results of this analysis are the main input for the dimensioning of the transport network.
Steps
1. Estimate coverage. a. The coverage efficiency of WCDMA is defined by the average coverage area per site, for a predefined propagation environment, and supported traffic density. b. Check the size of the area. c. Take the area type into account and consider the suitability of the propagation model. d. Different area types are, for example, dense urban, urban, suburban, and rural. There can also be special areas within an area, for example an airport or an industrial area. Estimate capacity. a. Check the frequency range and the amount of spectrum that can be used. b. Estimate the amount of supported traffic per base station site. Estimate quality of service.
2.
3.
8 (113)
DN70118376 Issue 2-0 en 18/06/2007
Consider blocking and location probability. Typical values are 2% and 95% respectively. Location probability varies for different services according to the required data rates. For example, the location probability for a service that requires faster data rates may be smaller.
Expected outcome
A rough estimate of the required sites and network elements:

.
base stations base station configurations RNCs
and requirements and strategy for:

.
coverage quality capacity transport network per service based on the given input parameters.
Further information
For further information, see Dimensioning transport network. See also:

.
Dimensioning Air interface Introduction to RNC overload control in Overload Control in RNC Overview of Nokia WCDMA RAN configurations in Configuring WCDMA RAN Introduction to Nokia RAN configurations in Configuring WCDMA RAN
For instructions, see Planning radio network in Planning WCDMA RAN and Optimising and expanding WCDMA RAN in Optimising WCDMA RAN.
DN70118376 Issue 2-0 en 18/06/2007
9 (113)
10 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning Air interface

The air interface dimensioning is based on the predicted subscriber density (subscribers/km2), subscriber traffic profiles, propagation environment, and Quality of Service (QoS) targets. With Wideband Code Division Multiple Access (WCDMA), the dimensioning has to be done iteratively, considering the air interface load and cell range coupling. The iteration steps are presented in Figure BTS dimensioning flow. The calculations are based on the basic WCDMA formulas, propagation models, and statistical analysis. In practice, the dimensioning is done with network dimensioning or planning tools (such as NetDim or NetAct Planner, see NetAct Planner documentation).
Subscribers/km2 Traffic/Subscribe
Area types Antenna gains
Coverage targets Fading margins
Load Factor Calculation
Link Budget Calculation
Cell Range Calculation
Equipment Requirement
Capacity Requirement
Allowed blocking/ queuing
Figure 1.
BTS dimensioning flow
DN70118376 Issue 2-0 en 18/06/2007
11 (113)
For more information on dimensioning Air interface, see Introduction to R99 DCH dimensioning, Introduction to HSDPA dimensioning and Introduction to HSUPA dimensioning. See also Introduction to Nokia RAN configurations in Configuring WCDMA RAN. Air interface dimensioning in RAS06 increases in complexity with the introduction of HSUPA. HSUPA causes some changes into the dimensioning methodology, as RF resources have to be shared with R99 users (using DCH bearers). As both HSDPA and HSUPA (HSUPA works only with HSDPA) are optional features, dimensioning can be separated in three main cases:
.
Only R99 dimensioning Combined R99 + HSDPA dimensioning Combined R99 + HSPA (HSDPA + HSUPA) dimensioning
Also, additionally dedicated carriers for R99, R99 UL+HSDPA and HSUPA +HSDPA are possible. This section on Air interface dimensioning concentrates on Combined R99 + HSPA (HSDPA + HSUPA) dimensioning, as it can be seen as the most complex. This is due to the fact that R99 DCH traffic influences all other features, HSDPA and HSUPA.
12 (113)
DN70118376 Issue 2-0 en 18/06/2007
Air interface dimensioning, shared carrier DCH + HSPA
Additional capacity Node Bs HSDPA capacity dimensioning
Coverage dimensioning selection: - Link Budget R99 (based on service) - Link Budget HSDPA (based on cell edge throughput) - Link Budget HSUPA (based on cell edge throughput) - Output # of coverage sites # of Node Bs (coverage + capacity)
Input: available HSDPA capacity UL/DL Load, Node B DL power
Output: HSDPA throughput
Not OK
CE Calculation
R99 capacity dimensioning
Result evaluation
OK
Iu-b Dimensioning
Input: available HSUPA capacity
Output: HSUPA throughput
HSUPA capacity dimensioning
RNC Dimensioning
Coverage dimensioning
Capacity dimensioning
Dimensioning inputs and requirements
Figure 2.
Air interface dimensioning process for shared DCH + HSPA carrier
Tip
Channel Element (CE) is a capacity unit of BTS baseband processing. One CE is required in UL and DL for AMR 4.75 - 12.2 kbps and WBAMR 6.6 - 12.65 kbps. For MultiRAB calls, CE consumption is calculated by adding together the individual RAB CE needs.
Table 3.
CE consumption examples CE for single RAB Uplink Downlink

1 16 16 16
AMR 4.75-12.2 kbps, WB-AMR 6.612.65 kbps PS 64 / 384 kbps PS 128 / 384 kbps PS 384 / 384 kbps
1 4 4 16
DN70118376 Issue 2-0 en 18/06/2007
13 (113)
DCH traffic load has to be taken into account in capacity dimensioning of HSDPA in downlink and HSUPA in uplink. This sets some challenges on estimating the capacity available for different services, especially HSPA services. Overall, dimensioning can be based on different starting points, such as having the coverage dimensioning for HSUPA 64 kbps or for HSDPA cell edge throughput of 128 kbps. Similarly, capacity dimensioning can be based on DCH load estimation or HSUPA/HSDPA cell average throughput. Additionally, as there are more WCDMA frequencies available, the operating frequency can have a high influence on the dimensioning parameters. It affects, for example:
.
Node B noise figure (for example, Flexi ~2 GHz 2 dB, ~900 MHz 2.8 dB) Node B antenna gain (for example,. ~2 GHz =17.5 dBi, ~900MHz = 14.5 dBi) Cable loss (for example, ~2 GHz = 5.9 dB/100 m, ~900MHz = 3.7 dB/100 m) User equipment noise figure (for example,~2 GHz 8 dB, ~900 MHz 11 dB) Propagation. Lower frequency has better propagation performance. Therefore, carrier frequency has a big influence on cell range calculations.
For more detailed information on the dimensioning of R99 DCH, HSDPA and HSUPA, see Introduction to R99 DCH dimensioning, Introduction to HSDPA dimensioning and Introduction to HSUPA dimensioning. For more information on HSDPA and HSUPA, see High-speed packet access (HSPA) in HSPA Overview .
14 (113)
DN70118376 Issue 2-0 en 18/06/2007
R99 DCH dimensioning
3
3.1

Intoduction to R99 DCH dimensioning
R99 dedicated traffic channel (DCH) dimensioning has to be noted also in HSPA dimensioning. In case of shared DCH + HSPA, the R99 DCH traffic affects both HSDPA and HSUPA capacity as well as coverage. The general R99 dimensioning process is shown in Figure R99 dimensioning flow.
Air interface dimensioning, only DCH carrier

Additional capacity Node Bs Coverage dimensioning selection: - Link Budget R99 (based on service) - Output # of coverage sites CE Calculation
Not OK
# of Node Bs (coverage + capacity)
R99 capacity dimensioning

Input: available capacity Output: R99 UL/DL load
Result evaluation
OK
Iu-b Dimensioning
RNC Dimensioning
Figure 3.
R99 dimensioning flow
The figure shows the basic parts of the dimensioning flow, including inputs:
DN70118376 Issue 2-0 en 18/06/2007
15 (113)
Area type distribution, area parameters Subscriber density (subscribers / km2) per area type Busy hour (BH) traffic/subscriber by traffic types (for example, voice, CS data 64 kbps, PS data 64 kbps) Service targets Node B type, operational parameters (frequency, power, orthogonality)
The steps for air interface dimensioning are:

1. Coverage dimensioning
.
Calculate or estimate uplink/downlink load factor. Calculate uplink/downlink radio link budget. Calculate cell range and Node B coverage area for the selected coverage limiting service.
For more information, see R99 DCH coverage dimensioning.

2. Capacity dimensioning
.
Estimate and calculate the traffic and capacity demand based on traffic and subscriber profile inputs. Compare the capacity need with the number of coverage sites offered capacity. If R99 capacity is not enough, you can add new Node Bs for capacity, tune the parameters in link budget or capacity-related feature parameters, and add dedicated carriers.
For more information, see R99 DCH capacity dimensioning.

Expected outcome
.
Cell ranges Number of BTSs/area BTS configurations Subscribers/BTS, traffic/BTS
16 (113)
DN70118376 Issue 2-0 en 18/06/2007
3.2
R99 DCH coverage dimensioning

R99 DCH coverage dimensioning includes uplink link budget, downlink link budget, and cell range and coverage.
3.2.1
Uplink link budget

The uplink link budget can be used to define CS and PS service maximum path loss. Table Example of R99 UL DCH link budget shows the basic link budget for R99 UL DCH.
Table 4. Service
Example of R99 UL DCH link budget Speech

12.2
CD Data
64
PS Data
64
Service Rate (kbps)
Transmitter - Handset Max Tx Power (dBm) Tx Antenna Gain (dBi) Body Loss (dB) EIRP (dBm) 24 0 3 21 24 0 0 24 24 0 0 24
Receiver Node B Node B Noise Figure (dB) Thermal Noise (dBm) Uplink Load (%) Interference Margin (dB) Interference Floor Service Eb/No (dB) Service PG (dB) 4.4 25.0 2 17.8 -118.8 18.0 0.5 0 1.8 1.5 2 -108 50 3-0 -103.0 2 17.8 -118.8 18.0 0.5 0 1.8 1.5
Receiver Sensitivity (dB) -123.6 Rx Antenna Gain (dBi) Cable Loss (dB) Benefit of using MHA (dB) UL Fast Fade Margin (dB) UL Soft Handover Gain (dB) 18.0 0.5 0 1.8 1.5
DN70118376 Issue 2-0 en 18/06/2007
17 (113)
Table 4. Service
Example of R99 UL DCH link budget (cont.) Speech

2.5 12 90 10 7.8 -123.5 144.5
CD Data
2.5 12 90 10 7.8 -118.7 142.7
PS Data
2.5 12 90 10 7.8 -118.7 142.7
Gain against shadowing (dB) Building Penetration Loss (dB) Indoor Location Prob. (%) Indoor Standard Dev. (dB) Shadowing margin (dB) Isotropic Power Required (dB) Allowed Prop. Loss(dB)
UL PS services can have also other bit rates, for example 128 and 384 kbps. Usually the coverage dimensioning is still made with 64 kbps CS or PS.
Defining uplink link budget
1.
Define the service parameters. . Service bit rate The bit rate depends on service, which can vary in speech service bit rates (for example, 4.75, 5.9, 7.95, 12.2 kbps) to packet service bit rates (for example, 64, 128 and 384 kbps) as well as video service (for example, 64 kbps). . Service Processing Gain
Service Processing Gain = 10 * LOG
Chip Rate Bit Rate
High processing gains correspond to services with low bit rates. These services tend to have more relaxed link budgets and generate smaller increments in cell loading. Service Eb/No. Eb/No value varies between services and also between selected propagation channels. The following table shows the recommended Eb/No values for commonly used services in dimensioning.
18 (113)
DN70118376 Issue 2-0 en 18/06/2007
Table 5. Eb/No [dB]

Uplink
Eb/No values for network dimensioning Speech 64 kbps 128 kbps 384 kbps
3 km/h, macro cell 120 km/h, macro cell Downlink 3 km/h, macro cell 120 km/h, macro cell
4.4 5.4
2 2.9
1.4 2.4
1.7 2.9
7.9 7.4
5 4.5
4.7 4.2
4.8 4.3
Eb/Nos for lower and wideband AMR codecs and for lower PS data services can be derived from the values (3 km/h) shown above. See Table Eb/No values for lower and wideband AMR codecs and lower PS data services.
Table 6.
Eb/No values for lower and wideband AMR codecs and lower PS data services Wideband AMR
6.65 5.5 8.8 8.85 5.0 8.3 12.65 4.3 7.9
Narrowband AMR
Bit rate (kbps) Uplink Eb/ No [dB] 4.75 6.4 5.9 5.8 9.0 7.95 5.2 8.5
Lower PS
8 3.9 5.4 16 2.5 5.4 32 2.2 5.7
DownlinkEb/ 9.4 No [dB]
2.
Define parameters for the UE. . UE max power and antenna gain UE transmit power is dependent on the mobile type and usually varies between 21 and 24 dBm. Similarly, the antenna gain varies from 0 dBi mobile terminals to 2 dBi data cards. . Body loss Body loss depends on service. Commonly during the calls the mobile is located near the ear, and 3 dB body loss is noticed. . EIRP
DN70118376 Issue 2-0 en 18/06/2007
19 (113)
EIRP represents the effective isotropic radiated power from the transmit antenna. In uplink it is computed from the following equation: Uplink EORP = UE Transmit Power + Transmit Antenna Gain Body Loss 3. Define Node B parameters. . Node B noise figure NF varies according to frequency and Node B performance. For example, for Flexi WCDMA BTS NF varies from 2 to 2.8 dB according to the frequency. . Antenna gain Antenna gain varies from sectorised to omni antennas. The antenna gain can be seen from antenna data sheet. . Cable loss and Mast Head Amplifier Cable loss can be assumed to be from 0.5 to 3 dB; in case of Flexi WCDMA BTS the cable loss can be as low as 0.5 dB. When using MHA, the cable loss is compensated and the benefit from MHA is the same as the assumed cable loss. Calculate thermal noise according to the following formula: ThermalNoiseDensity= k x T x B = -108 dBm where: . k = Boltzmanns constant, 1.43 E-23 Ws/K . T = Receiver temperature, 293 K . B = Bandwidth, 3 840 000 Hz 5. Calculate or estimate uplink load factor. Calculate uplink load factor by WCDMA uplink load equation:
j=N UL
4.
=
j=1
vj
Eb / N oj W / Rj
* (1 + a * i)
ul N Vj Eb/Noj W
Uplink load factor. Generally uplink load of 0.5 0.7 is used in dimensioning. Number of users L1 activity factor of user j (0.67 for voice UL, 0.63 for voice DL, 1.0 for data) Received energy per bit-to-noise density ratio (Eb/No) of user j WCDMA chip rate; 3.84 Mcps/s
20 (113)
DN70118376 Issue 2-0 en 18/06/2007
Rj A i
Data rate of user j Power rise of user j due to power control, depending on UE speed Ratio of other to own cell interference. In uplink, the value depends on the BTS sectorisation: Micro cell : Omni: 25% - 55% Macro cell: Omni: 55%, 2-sector: 55%, 3sector: 65%, 4-sector: 75%, 6-sector: 85%
It is recommended to use the maximum uplink load of 0.50.7, even if in the initial phase of the network the subscriber traffic would not generate as much load. This is to avoid a situation where slight increases in the traffic amounts may cause shrinkage of the coverage areas. In rural areas, where major traffic is not expected, a lower uplink load value may be used. Calculate interference margin. This is calculated from the load factor.
TARGET_LOAD Interference_margin= -10 * LOG 1100
6.
Calculate Interference Floor. Interference Floor is calculated from the load factor. Interference_floor = Thermal noise + Node B noise figure + intereference_margin
7.
Define receiver thermal sensitivity. The receiver thermal sensitivity is computed according to the equation: Receiver Sensitivity = Interference_floor + Required Eb/No Processing Gain This represents the receiver sensitivity when the system is loaded, that is, an interference margin has been included.
8.
Define additional parameters. . UL fast fade margin, that is, power control headroom. The recommended value for slow moving mobiles is 1.8 dB. For fast moving mobiles it is 0 dB. . Gain against shadowing. The recommended value is 2.5 dB. . UL soft handover gain. The recommended value is 1.5 dB.
DN70118376 Issue 2-0 en 18/06/2007
21 (113)
9.
Define clutter-related parameters. As shown in the example link budget, the maximum allowed propagation loss calculation includes also a definition of indoor losses and margins. Additionally, coverage can also be calculated for in-car and outdoor, but most commonly coverage should be calculated for indoors. . Slow fading margin, outdoor: 6 8 dB (lower for suburban and rural) . Slow fading margin, indoor: 10 15 dB (lower for suburban and rural)
10.
Define the required Isotropic power. The required signal power is calculated to take into account the building penetration loss and indoor standard deviation, as well as receiver sensitivity and additional margins. Isotropic power required = Receiver sensitivity - RxAntennaGain + cable loss - MHA gain + UL fast fade margin Gain against shadowing UL SHO gain + BPL + shadowing margin
11.
Define allowed propagation loss. Allowedprop loss = EIRP - Isotropic power required
3.2.2
Downlink link budget

The downlink link budget can be used for defining CS and PS service maximum path loss. Table Example of R99 DL DCH link budget shows the basic link budget for R99 DL DCH.
Table 7. Service
Service Rate (kbps)
Example of R99 DL DCH link budget CD Data

64
Speech
12.2
PS Data
64
PS Data
128
PS Data
384
Transmitter - Node B Max Tx Power Total (dBm) Max Tx Power (per Radiolink) (dBm) Cable Loss (dB) MHA Insertion Loss Tx Antenna Gain (dBi) 34.2 0.5 0 18 37.2 0.5 0 18 37.2 0.5 0 18 43 38.0 0.5 0 18 38.0 0.5 0 18
22 (113)
DN70118376 Issue 2-0 en 18/06/2007
Table 7. Service
EIRP (dBm)
Example of R99 DL DCH link budget (cont.) CD Data

54.7
Speech
51.7
PS Data
54.7
PS Data
55.5
PS Data
55.5
Receiver Handset Handset Noise Figure (dB) Thermal Noise (dBm) Downlink Load (%) Interference Margin (dB) Interference Floor (dBm) Service Eb/No (dB) Service PG (dB) Receiver Sensitivity (dBm) Rx Antenna Gain (dBi) Body Loss (dB) DL Fast Fade Margin (dB) DL Soft Handover Gain (dB) Gain against shadowing Building Penetration Loss (dB) Indoor Location Prob. (%) Indoor Standard Dev. (dB) Shadowing margin (dB) Isotropic Power Required (dB) Allowed Prop. Loss (dB) 7.9 25.0 -111.1 0 3 0 2.5 2.5 12 90 10 7.8 -93.3 145.0 5 17.8 -106.8 0 0 0 2.5 2.5 12 90 10 7.8 -92.0 146.7 5 17.8 -106.8 0 0 0 2.5 2.5 12 90 10 7.8 -92.0 146.7 7 -108 80 7.0 -94.0 4.7 14.8 -104.1 0 0 0 2.5 2.5 12 90 10 7.8 -89.3 144.8 4.8 10.0 -99.2 0 0 0 2.5 2.5 12 90 10 7.8 -84.4 139.9
Commonly the service coverage is made based on the UL link budget, but it is good to verify the coverage also for downlink service.
DN70118376 Issue 2-0 en 18/06/2007
23 (113)
Defining downlink link budget
The parameter definition for downlink link budget is mostly the same as for R99 uplink DCH link budget, but with the some differences as described here. 1. Define service parameters. Use downlink Eb/No values in Table Eb/No values for network dimensioning in Defining uplink link budget. 2. Define UE parameters You need to define RX Antenna Gain and Body Loss. Define Handset Noise Figure (no Node B Noise Figure defined). 3. Define Node B parameters. Node B parameters are the same as for UL, except that Node B Noise Figure is not defined. . Max Tx Power per radiolink is calculated based on set of parameters separately for real -time (MaxRTDLPower) and non-real-time services (MaxNRTDLPower). For information on the parameters related to the calculation, see Admission Control. As an example, Table Example of DL link powers shows DL link powers for different services.
Table 8.
Example of DL link powers Speech service, kbps Packet services, kbps

12.2 34.2 64 37.8 128 40.0 384 40.0
Bit rate
4.75
5.9 32.7
7.95 33.2
Max DL 32.3 link power (dBm)
In this example, Max total TX power is 20 W, PtxDPCHmax is 3 dB, PtxPrimaryCPICH is 33 dBm, and CPICHtoRefRABOffset is 0 dB. Downlink EIRP Downlink EIRP = MaxRT/NRT)DLpower -Cableloss MHAinsertionloss + Transmit Antenna Gain
4.
Calculate or estimate downlink load factor using WCDMA downlink load equation:
24 (113)
DN70118376 Issue 2-0 en 18/06/2007
j=N DL
= (1 + SHO_OH) *
j=1
vj
E b / N oj W / Rj
* (1 - + i)
DL
Downlink load factor, generally downlink load of 0.5 _ 0.8 is used in dimensioning N Number of users Vj L1 activity factor of user j (0.67 for voice ul, 0.63 for voice dl, 1.0 for data) Eb/Noj Received Eb/No of user j W WCDMA chip rate; 3.84 Mcps/s Rj Data rate of user j Orthogonality dependant upon the propagation channel condition (commonly selected to 0.5 (can vary between 0.4 to 0.9) i Ratio of other to own cell interference. The value depends on the BTS sectorisation: . Micro cell: Omni: 25% - 55% . Macro cell: Omni: 55%, 2-sector: 55%, 3sector: 65%, 4-sector: 75%, 6-sector: 85% It is recommended to use the maximum downlink load of 0.50.8, even if in the initial phase of the network the subscriber traffic would not generate as much load. This is to avoid a situation where slight increases in traffic amounts may cause shrinkage of the coverage areas. In rural areas, where major traffic is not expected, lower uplink load value may be used. Interference margin is calculated similarly as in uplink.
5.
Define Interference Floor. Calculate thermal noise as in uplink link budget. Interference_floor = Thermal noise + Handset noise figure + interference_margin
6.
Define receiver thermal sensitivity. Receiver thermal sensitivity is computed according to the following equation. Use downlink Eb/No values. Receiver Sensitivity = Interference_floor + Required Eb/No Processing Gain
7.
Define additional parameters.
DN70118376 Issue 2-0 en 18/06/2007
25 (113)
DL fast fading margin. In DL fast fade margin is assumed to be 0 dB in the downlink direction as a result of the limited downlink transmit power control dynamic range. Gain against shadowing. In R99 DL DCH, the recommended value is 2.5 dB, which is used to determine the selection possibility of stronger cell in normal cell overlapping network DL SHO gain represents a reduction in Eb/No requirement when the UE is in soft handover state. The recommended cell edge value is 2.5 dB (in capacity calculation DL SHO gain is 1.2 dB as an average over the cell, for UL SHO gain is neglected in the capacity calculation).
8.
Define clutter-related parameters. Set these parameters as in uplink link budget.
9.
Define the isotropic power required. Required signal power is calculated to take into account the building penetration loss and indoor standard deviation, as well as receiver sensitivity and additional margins. Isotropic power required = Receiver sensitivity - RxAntennaGain + Body loss + DL fast fading margin DL SHO gain Gain against shadowing + BPL + Shadowing margin
10.
Define allowed propagation loss. Allowedprop.loss = EIRP - Isotropic power required
3.2.3
Cell range and coverage

As shown, the link budget can already include the margins, for example to identify the allowed propagation loss in indoor location. The cell range calculation can be calculated by using either uplink or downlink path loss. Most commonly the uplink path loss is used to calculate the coverage. But in network dimensioning, the link budget calculation has to be made for every service, and the limiting one has to be selected for the cell range. The cell range and coverage is based on:
.
system parameters as shown in link budget taking into account margins to guarantee service for example, in indoor, in-car or outdoor building penetration loss, car penetration loss or outdoor when no penetration loss
26 (113)
DN70118376 Issue 2-0 en 18/06/2007
location probability standard deviation calculating the cell range by using propagation model like OkumuraHata model when also noticing the frequency, for example, 2100 MHz Node B antenna height, for example, 30 meters UE antenna height, for example, 1.5 meters Clutter correction factor, which is related to the type of clutter. As an example Dense urban (30 dB), Urban (0-3 dB) and Suburban (5-8 dB). For example, in urban macro environment, Node B antenna height is 30 m, MS antenna height is 1.5 m and carrier frequency is 1950 MHz L = 137.4 + 35.2*log(R). Where L is the path loss and R is the range in kilometres. For suburban we can assume clutter correction factor for example, 8 dB and calculate the path loss as follows: L = 129.4 + 35.2*log(R).
Indoor cell range (taking into account the speech UL path loss) R = 10^((142.5-137.4) / 35.2) = 1.4 km
Node B coverage area calculation (depending on the number of sectors in Node B) A=K*R2 K-factor; depending on the Node B sectorisation:
R R
Omni 2 A = 2,6 R1
Bi-sector 2 A = 1,73 R2
Tri-sector 2 A = 1,95 R3
Figure 4.
Node B sectorisation
DN70118376 Issue 2-0 en 18/06/2007
27 (113)
3.3
3.3.1
R99 DCH capacity dimensioning

Load calculation based on traffic inputs
To calculate whether the capacity of coverage Node Bs supports the traffic estimation, you should estimate the load factor from the traffic. Also the UL load factor has to be calculated, as HSUPA utilises the load which is left from DCH traffic. To calculate the maximum number of simultaneous uplink/downlink users in a cell, you can utilise the following method where the subscribers per carrier per cell are calculated from the total number of subscribers, the number of Node Bs and the configuration of those Node Bs. The equation used is as follows:
Total number of subscribers No. of Node B * No. of cells per Node B * No. of carriers per cell
Subscribers per carrier per cell =
Total traffic is calculated over the subscribers, and after that you can calculate the needed traffic channels per cell. For voice and RT data services the traffic channel calculations are based on the Erlang B formula and for NRT data services they are based on throughput. The two equations are given here:
Voice and RT data
Uplink: UL_tchs = ErlangBchs(bloc_prob;traffic) Downlink: DL_tchs = UL_tchs x (1 + Soft_HO_oh) The blocking probability is typically assumed to be 2%. Soft_HO_oh can vary from 20-40%.
NRT data
For NRT, the activity for downlink and uplink can be different, and the need for traffic channels can vary. Commonly UL and DL traffic is 1:10. Uplink:
traffic throughput * R
tchs =
28 (113)
DN70118376 Issue 2-0 en 18/06/2007
Downlink:
traffic * (1 + Soft_HO_oh) throughput * R
tchs =
In the equation, R is the service bit rate. The throughput is assumed to be 79%. This figure includes the L2 re-transmission overhead of 10% and 15% of buffer headroom to avoid overflow (peak to average load ratio headroom) => (1+0.10) x (1+0.15) = 1.265 => 26.5% overhead => throughput is 79% of user traffic. Soft_HO_oh can vary from 20% to 40%. The fractional load generated by the services can then be calculated from the UL and DL load formulas wherein noticing the SHO gain (also called MDC gain) and the number of interfering channels. In UL/DL the gain is due to soft handover which influences the Eb/No. The reduction in Eb/No is commonly assumed to be 0 dB in UL and 1.2 dB in DL.
Uplink fractional load formula
The formula for uplink fractional load is as follows:

m W Eb / N0_BTS-SHOgain_UL 10 * (1 + i_UL*PowerRiseUL)
fL_UL= 1+ R*10
where
.
m is the number of interfering channels Eb/No is the target energy per bit to interference spectral density ratio W is the chip rate R is the bit rate SHOgain_UL is the average macro diversity gain on the UL due to soft handover which reduces the Eb/No
DN70118376 Issue 2-0 en 18/06/2007
29 (113)
PowerRiseUL is the average increase in transmit power due to power control. i_UL is the ratio of other to own cell interference.
The total UL load is obtained by summing the UL fractional loads over all service classes.
Downlink fractional load formula
The formula for downlink fractional load is as follows:
fL_DL=
m * 10
Eb / N0_MS-SHOgain_DL 10 W
* R * (1 - Orth_DL + i_DL)
where
.
m is the number of interfering channels Eb/No is the target energy per bit to interference spectral density ratio W is the chip rate R is the bit rate SHOgain_UL is the average macro diversity gain on the UL due to soft handover which reduces the Eb/No Orth_DL is the downlink orthogonality i_DL is the ratio of other to own cell interference.
The total downlink load is obtained by summing the downlink fractional loads over all service classes.
3.3.2
DL power calculation vs. load

Node B has a maximum power from which it allocates for control channels and traffic channels. If the load is higher, also the interference from the control channel is higher and causes power increase related to the load. Total power is basically calculated as shown in the formula below: Ptot_tx=PCCH_tx+PDCH_tx
30 (113)
DN70118376 Issue 2-0 en 18/06/2007
where
.
Ptot_tx is the total transmission power Pcch_tx is the control channel power Pdch_tx is the traffic channel power
When going into details, the formula also includes the DL load factor. In that case the formula is as follows:
(E b / N o ) j
j
P tot_tx =
PCCH_tx + PN * L P * 1-
W / Rj
DL_DCH
* Vj
where
.
PN is the noise power Lp is the average path loss = Isotropic Path Loss Antenna gain Cable loss + SHO gain IPL correction factor Other parameters are the same as in the DL load formula.
DN70118376 Issue 2-0 en 18/06/2007
31 (113)
32 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSDPA dimensioning
4
4.1
HSDPA dimensioning
Introduction to HSDPA dimensioning
HSDPA downlink data is carried on a shared channel. For this reason, different variables have to be considered in HSDPA dimensioning compared to NRT DCH data bearer dimensioning. The most important dimensioning target for HSDPA is the average throughput. The achieved average throughput depends on the amount of power allocated for HSDPA. The aim of the HDSPA air interface dimensioning is to specify how much power should be allocated for HSDPA. HSDPA power should be enough to achieve HSDPA throughput targets, but on the other hand, enough power resources should be reserved for the DCH traffic as well. If DCH load is high, the shared carrier HSDPA+DCH is not feasible to fully support the growing data traffic in HSDPA, especially now when HSUPA creates even higher demand to support data traffic. In case of high DCH load, a dedicated carrier for HSPA (HSDPA + HSUPA) is needed. In this case the capacity of the carrier is allocated fully to HSDPA (see Figure Overall dimensioning process for dedicated HSPA carrier in Introduction to HSUPA dimensioning. Figure Dimensioning process with DCH + HSDPA (+ HSUPA) shows the dimensioning process with shared carrier, either with or without HSUPA . From HSDPA point of view, the process is the same.
DN70118376 Issue 2-0 en 18/06/2007
33 (113)
Air interface dimensioning, dedicated carrier HSPA

Not OK Input: available capacity Output: HSDPA throughput
Coverage dimensioning selection: - Link Budget UL R99 (based on HSDPA associated UL DPCH service) - Link Budget HSDPA (based on cell edge throughput) - Link Budget HSUPA (based on cell edge throughput) - Output # of coverage sites
CE Calculation
Result evaluation
OK Input: available capacity Output: HSUPA throughput
Iu-b Dimensioning
UL DPCH capacity dimensioning
RNC Dimensioning
Input: capacity for HSUPA
Figure 5.
Dimensioning process with DCH + HSDPA (+ HSUPA)
The dimensioning process of HSDPA is basically as in R99; the first step is coverage dimensioning, followed by capacity dimensioning. However, the process differs in that capacity dimensioning has to include also the R99 capacity estimation if shared carrier is in use. The steps for air interface HSDPA dimensioning are:
Coverage dimensioning can be based on:

.
R99 service link budget HSDPA link budget with selected cell edge throughput (n case HSUPA, HSUPA link budget with selected cell edge throughput
34 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSDPA dimensioning
.
Estimate and calculate R99 traffic and capacity demand based on traffic and subscriber profile inputs. Estimate HSDPA capacity from capacity left after R99 traffic. (Estimate HSUPA capacity from capacity left after R99 traffic). If R99 and/or HSDPA (+HSUPA) capacity is not enough, you can: . Add new Node Bs . Tune the parameters in link budget or capacity-related feature parameters . Add dedicated carrier for HSPA.
The expected outcome from the HSDPA dimensioning is as follows:

.
Defining the HSDPA cell range and coverage based on cell edge throughput or utilise the existing R99 service link budget to define what kind of HSDPA throughput can be achieved at the cell edge Calculating the average cell throughput based on power available for HSDPA Identifying the Node B configuration required to achieve a specific throughput performance
For more information on HSDPA, see High-speed Downlink Packet Access (HSDPA) in HSPA Overview.
4.1.1
HSDPA features in RAS06

RAS06 introduces the following HSDPA features:
.
RAN1013: 16 kbit/s Return Channel DCH Data Rate Support for HSDPA RAN852: HSDPA 15 Codes RAN1033: HSDPA 48 Users per Cell RAN853: HSDPA Code Multiplexing RAN1034: Shared HSDPA Scheduler for Baseband Efficiency RAN1011: HSPA Layering for UEs in Common Channels RAN312: HSDPA Dynamic Resource Allocation
DN70118376 Issue 2-0 en 18/06/2007
35 (113)
For more information, see RAS06 Feature Descriptions. See also Radio Resource Management of HSDPA and HSDPA in BTS
4.1.2
Supporting R99 formulas

Due to the shared carrier, HSDPA needs to take into account the power generated by R99. The HSDPA capacity calculation takes into consideration the Node B TX power used for R99 services. As noticed in the Dynamic Resource Allocation feature, the rest of the power after DCH traffic, HSUPA control channels and common channels is used for HSDPA. This means that to find how much the power is left for HSDPA, it is necessary to make the DL power calculation vs. load. Based on this information, the available HSDPA power can be used to determine the HSDPA capacity. This is needed if HSDPA has a shared carrier with R99 traffic.
4.2
4.2.1
HSDPA coverage dimensioning

Uplink link budget
The UL data of the HSDPA connection is carried on associated DPCH, which is a normal NRT data bearer. The supported data rates for associated DPCH are 16, 64, 128 and 384 kbps. However, additional margin is required in the UL link budget to take into account the power requirements of HS-DPCCH. HS-DPCCH carries channel quality information (CQI) reports and Ack/Nack feedback for HARQ. HS-DPCCH is power controlled relative to the every slot period in uplink DPCCH. The power offset parameters (ACK; NACK; CQI) are controlled by the RNC and reported to the UE using higher layer signalling. The HS-DPCCH power offset must be increased, since the UL HSDPCCH power control is sub-optimal for HSDPA users in soft handover mode (that is, active set size larger than one). It is possible that the dominant link in the active set is not the one belonging to the cell which is currently transmitting the HS-PDSCH to the user. However, using the maximum HS-DPCCH power offset of 6 dB is not sufficient to ensure good
36 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSDPA dimensioning
UL HS-DPCCH quality under all conditions, unless Ack/Nack repetition is used. The average overhead generated by HS-DPCCH depends on ACK/ NACK and CQI activity. Link budgets consider peaks rather than the average overhead.
HS-DPCCH
Ack/Nack
CQI report
ACKi
NACK
CQI
CQI
DPCCH
Figure 6.
HS-DPCCH power offset parameters
The additional margin in UL link budget due to CQI reports and Ack/Nack depends on the UL bearer data rate:
.
UL 16 kbps: 4.6 dB UL 64 kbps: 2.8 dB UL 128 kbps: 1.6 dB UL 384 kbps: 1.1 dB
Overall, the HSDPA-associated UL link budget corresponds to the R99 UL link budget for packet services. The only difference is the HS-DPCCH overhead, and it can be included in the EIRP formula: uplinkEIRP = UE Transmit Power - HS_DPCCHoverhead + Transmit Antenna Gain - BodyLoss
4.2.2

For downlink, the link budget can be used to calculate the cell range with related coverage requirements such as cell edge throughput. There are two most important link budgets in HSDPA that are for user and control traffic. Table HSDPA downlink link budget for HS-PDSCH and HS-SCCH shows an example of both link budgets (HS-PDSCH and HS-SCCH).
DN70118376 Issue 2-0 en 18/06/2007
37 (113)
Table 9.
HSDPA downlink link budget for HS-PDSCH and HS-SCCH
Downlink Service
Cell Edge Throughput Channel Service Service Rate (kbps) 384 HS-PDSCH PS Data 384 HS-SCCH Control
Transmitter - Node B Max Tx Power (dBm) Cable Loss (dBi) MHA Insertion Loss Tx Antenna Gain (dBi) EIRP (dBm) 37.4 0.5 0.0 18 54.9 Receiver - Handset Handset Noise Figure (dB) Thermal Noise (dBm) Downlink Load (%) Interference Margin (dB) Interference Floor (dBm) SINR Requirement (dB) Spreading Gain (dB) Receiver Sensitivity (dBm) Rx Antenna Gain (dBi) Body Loss (dB) DL Fast Fade Margin (dB) DL Soft Handover Gain (dB) 7 -108 80 7.0 -94.0 4.5 12.0 -101.5 2 0 0 0 7 -108 80 7.0 -94.0 1.5 21.0 -113.5 2 0 0 0 2.5 12 90 10 7.8 -98.2 142.7 27 0.5 0.0 18 44.5
Gain against shadowing (dB) 2.5 Building Penetration Loss (dB) Indoor Location Prob. (dB) Indoor Standard Dev. (dB) Shadowing margin (dB) Isotropic Power Required (dB) Allowed Prop. Loss (dB) 12 90 10 7.8 -86.3 141.2
38 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSDPA dimensioning
HSDPA throughput depends directly on the radio channel conditions. These conditions change rapidly due to fast fading of the radio channel. BTS is able to change the link adaptation for each 2ms TTI based on the channel measurements. This means that the achieved throughput is different in every TTI. The average throughput in a certain location can be estimated if the average SINR (Signal to Interference + Noise Ratio) is known. Commonly simulation results are used for estimating the average SINR. Figure Throughput and SINR comparison shows the SINR and throughput table with different codes.
12
5 codes, PedA 10 5 codes VehA 5 codes fit 10 codes PedA 8

Throughput (Mbits/s)
10 codes VehA 10 codes fit 15 codes PedA 15 codes VehA
15 codes fit
0 -10
-5
10
15 SINR(dB)
20
25
30
35
40
Figure 7.
Throughput and SINR comparison
DN70118376 Issue 2-0 en 18/06/2007
39 (113)
As shown in the figure, in lower throughputs there is no huge advantage of using 5, 10 or 15 codes, and also the average SINR is roughly the same. Using average SINR gives a possibility to create a DL link budget for HSDPA. The reason to use SINR is that the HSDPA bit rate and the number of codes can change in every TTI. Using Eb/No or Es/No in the link budget would require that either the bit rate or the number of the codes is known. The bit rate at cell edge is commonly lower than 384 kbps. From the HS-SCCH link budget point of view, it is most important to estimate the power allocated to it, because that also affects the HSDPA power that is left for traffic. HS-SCCH depends on the user location and is commonly assumed to be about 500 mW at the cell edge (around G-factor -5 dB).
NODE-B/CPICH POWER 12W/2W 1x1-RAKE, 3KM/H, 6MS/1DB LA DELAY/ERROR Ped-A Veh-A
Avg. req. HS-SCCH power @ 1% BLEP [W]
Typical macrocellular environment (3GPP)
4.0 3.5 3.0 2.5 2.0 1.5 1.0 0.5 0 -15 -10 -5 0 5 Average G-factor [dB] 10 15
Figure 8.
User location versus HS-SCCH
As discussed, the link budget has to consider the cell edge throughput to get the average SINR, and HS-SCCH has to be estimated to calculate the power left for HSDPA traffic. Similarly in case of shared carrier between the DL DCH and HSDPA, also the DCH power has to be estimated and taken into account.
40 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSDPA dimensioning
Defining downlink link budget
The parameter definition is the same as for R99 uplink DCH link budget, but with some differences, described here. 1. Define service parameters. . Service rate. You can define the throughput for HSDPA to calculate the allowed propagation loss. This affects the SINR requirement, which is needed for getting the wanted service at cell edge. Define UE parameters. Define RX Antenna Gain and Handset Noise Figure. Commonly Body Loss is assumed to be 0. 3. Define Node B parameters. Available HSDPA power notices also HS-SCCH power and in case of shared carrier with DCH, the DCH power has to be noted as well. Note that feature RAN312: HSDPA Dynamic Resource Allocation describes HSDPA power in more detail. 4. Additional differences compared to the R99 DCH downlink link budget. . HSDPA utilises only spreading factor 16. . Receiver sensitivity formula Receiver Sensitivity = Interference_floor +SINR - Spreading Gain (SF16) . HSDPA does not have soft handover, thus SHO gain are 0 dB. But because there are overlapping cells, the HSDPA mobile can select at cell edge a stronger cell, which is referred to as Gain against shadowing. The recommended value for Gain against shadowing in HSDPA is 2.5 dB.
2.
Other issues, formulas and parameters related to the HSDPA link budget are same as those for R99. See R99 DCH coverage dimensioning.
4.2.3

From the HSDPA perspective, the cell range and coverage are dependent on available power and wanted cell edge throughput.
DN70118376 Issue 2-0 en 18/06/2007
41 (113)
PtxMax HSDPA power PtxTargetPSMax PtxTargetPS PtxTargetPSMin Non-HSDPA power Time PtxMax is the cell maximum output power defined by the management parameter PtxCellMax and the BTS capability PtxTargetPS is the dynamically adjusted NRT DCH scheduling target PtxTargetPSMax and PtxTargetPSMin are the max and min values for PtxTargetPS
Figure 9.
Example of dynamic power allocation
As shown in the figure, all available power is allocated to HSDPA. From the dimensioning perspective, it is important to estimate the average nonHSDPA power and calculate the average available power for HSDPA. Based on that you can estimate the coverage. In case of dedicated HSDPA carrier, DCH traffic power can be neglected. For more information on dynamic power allocation, see HSDPA dynamic resource allocation in Radio Resource Management of HSDPA.
4.3
HSDPA capacity dimensioning

HSDPA downlink link budget utilises the average SINR and throughput mapping, which are commonly based on the simulations. An accurate SINR can be calculated when you know HSDPA power, BTS total Tx power, orthogonality and G factor and the user throughput can be estimated. The calculation is done using the following formula:
P HSDPA Ptot 1 - +1 G
SINR = SF
16
42 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSDPA dimensioning
where
.
PHSDPA = HSDPA Tx power Ptot = total WBTS Tx power = DL orthogonality factor SF16 = spreading factor of 16 G = G-factor
G-factor reflects the distance between the MS and the BS antenna. A typical range is from -5 dB (Cell Edge) to 20 dB. G-factor is correlated to Ec/Io:
EC IO
P CPICH PTOT 1 + 1 G
where
.
PCPICH = CPICH channel transmission power PTOT = BS total transmission power at the time of Ec/Io measurement
When the user SINR is known, the mapping on the simulated table can be made and the user throughput identified. If you allocate all available HSDPA power to one user, you can estimate the HSDPA cell throughput in a different location in the cell (ref. G-factor) within different radio environment (orthogonality). Other issues to take into account when estimating the cell throughput are:
.
Scheduler type: cell-specific or shared Proportional fair resource scheduler usage Number of codes used in the cell: 5 or even 15 or something in between due to feature HSDPA Dynamic Resource Allocation
Figure Example simulation results of HSDPA cell throughput shows an example of how the different issues and UE enhancements affect HSDPA cell throughput.
DN70118376 Issue 2-0 en 18/06/2007
43 (113)
Round robin 5 codes Round robin 10 codes Proportional fair 5 codes Proportional fair 10 codes Proportional fair 15 codes 4500 4000 3500 3000
kbps
2500 2000 1500 1000 500 0 Rake 1-ant Equalizer 1-ant Rake 2-ant Equalizer 2-ant
Figure 10.
Example simulation results of HSDPA cell throughput
44 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSUPA dimensioning
5
5.1
HSUPA dimensioning
Introduction to HSUPA dimensioning
RAS06 provides a new advantage to uplink with HSUPA, which provides high data rates in uplink direction for packet services. HSUPA is provided only in co-existence with HSDPA. The aim of the HSUPA air interface dimensioning is to specify how much load should be allocated for HSUPA. HSUPA capacity should be enough to achieve HSUPA throughput targets, but on the other hand, enough resources should be reserved for DCH traffic and for HSDPA-associated UL DPCH. In case of high DCH load, the shared carrier HSUPA+UL DCH is not feasible to fully support the HSUPA demand. In high DCH load a dedicated carrier for HSPA (HSDPA+HSUPA) is needed. In this case the uplink capacity of the carrier is allocated to HSUPA and HSDPA associated UL DPCH, see Figure Overall dimensioning process for dedicated HSPA carrier.
DN70118376 Issue 2-0 en 18/06/2007
45 (113)
Air interface dimensioning, dedicated carrier HSPA

Not OK Input: available capacity Output: HSDPA throughput
Coverage dimensioning selection: - Link Budget UL R99 (based on HSDPA associated UL DPCH service) - Link Budget HSDPA (based on cell edge throughput) - Link Budget HSUPA (based on cell edge throughput) - Output # of coverage sites
CE Calculation
Result evaluation
OK Input: available capacity Output: HSUPA throughput
Iu-b Dimensioning
UL DPCH capacity dimensioning
RNC Dimensioning
Input: capacity for HSUPA
Figure 11.
Overall dimensioning process for dedicated HSPA carrier
As shown in the figure, the UL calculation notices both HSDPA associated UL DPCH load and HSUPA load. It is important that during dimensioning also the HSDPA-associated UL DPCH capacity need is noticed and estimated. The overall process is as described in Introduction to HSDPA dimensioning and so the expected outcomes from HSUPA dimensioning are:
.
defining the HSUPA cell range and coverage based on cell edge throughput calculating the average cell throughput based on available load for HSUPA identifying the Node B configuration required to achieve a specific throughput performance.
For more information, see High-speed Uplink Packet Access (HSUPA) in HSPA Overview.
46 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSUPA dimensioning
5.1.1
HSUPA features in RAS06

RAS06 introduces the following HSUPA-related features:
.
RAN826: Basic HSUPA HSUPA is supported only with the co-existence of HSDPA. All cells in the BTS can be enabled for HSUPA. The maximum number of HSUPA users is 24 per BTS and 19 per cell. The operator can choose to set a lower threshold for the maximum number of users per cell and per BTS. Transmission Time Interval (TTI) of 10 ms is used for maximising the resulting uplink range. The highest supported user peak data rate on E-DCH is 1.888 Mbps, corresponding to two parallel codes of spreading factor two (2*SF2) and 10 ms TTI. RLC PDU size 320 bit is used. This bit rate is achieved using 59 RLC PDUs per TTI. HSUPA requires a static reservation of eight CE in WSPC (UltraSite WCDMA BTS) and eight CE in Flexi Submodule (Flexi WCDMA BTS) capacity. The rest of the HSUPA baseband capacity is fully pooled across cells, and also dynamically shared with R99 traffic. Up to two WSPCs (in Flexi Submodules) can be in HSUPA use, R99 traffic allowing. The maximum peak data rate per user is 2.0 Mbps as coded L1 bit rate (error protection coding is not counted into bit rate whereas L1 retransmissions are). One WSPC in UltraSite WCDMA BTS and one Submodule in Flexi WCDMA BTS supports up to 12 24 HSUPA users, depending on the data rate. The maximum HSUPA bit rate per WSPC (Submodule in Flexi WCDMA BTS) is 6 Mbps, with three 2 Mbps users in separate cells.
RAN973: HSUPA Basic RRM RAN968: HSUPA BTS Packet Scheduler
DN70118376 Issue 2-0 en 18/06/2007
47 (113)
RAN970: HSUPA Handovers RAN974: HSUPA with Simultaneous AMR Voice Call
For more information, see RAS06 Feature Descriptions. See also Introduction and feature structure of Radio Resource Management of HSUPA in Radio Resource Management of HSUPA.
5.1.2
Supporting R99 formulas

Due to the shared carrier case the HSUPA has to take into account the load generated by R99, which can be due to pure DCH UL traffic or HSDPA associated UL DPCH traffic. The HSUPA capacity calculation takes into a consideration the DL load used for R99 services and HSDPA-associated DPCH. This means that it is necessary to make load calculation based on traffic inputs to find out how much load is reserved for R99 and associated UL DPCH. Based on this information the available UL load can be used to determine the HSUPA capacity. This is needed if the HSUPA has shared carrier with R99 traffic. It has to be taken into account also when dedicated HSPA carrier is used, because the HSDPA-associated UL DPCH utilises the UL load with HSUPA.
5.2
5.2.1
HSUPA coverage dimensioning

Uplink link budget
As shown in Table Example of HSUPA link budget, the HSUPA link budget is very similar to the R99 uplink packet service link budgets, especially regarding HSDPA associated UL bearer. The major differences are related to higher user throughputs, which generate higher own connection interference. Also the Eb/Nos used are better when compared to DCH. This is due to Node B based HARQ, which allows to tolerate additional packet losses and retransmissions without causing problems from the delay perspective.
48 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSUPA dimensioning
Table 10.
Example of HSUPA link budget
Uplink Service
Cell Edge Throughput (kbps) Target BLER (%) Propagation Channel Channel Service Service Rate (kbps) 64 10 Pedestrian A 3 km/h HSUPA PS Data 64
Transmitter - UE Max Tx Power HS-DPCCH Overhead Tx Antenna Gain (dBi) Body Loss (dB) EIRP (dBm) 24 2.5 2 0 23.5 Receiver - Node B Node B Noise Figure (dB) Thermal Noise (dBm) Uplink Load (%) Interference Margin (dB) Own Connection Interference InterferenceFloor (dBm) Service Eb/No (dB) Service PG (dB) Receiver Sensitivity (dBm) Rx Antenna Gain (dBi) Cable Loss (dB)s Benefit of using MHA (dB) UL Fast Fade Margin (dB) UL Soft Handover Gain (dB) Gain against shadowing (dB) Building Penetration Loss (dB) 2 -108 50 3.0 0.08 -103.1 0.2 17.78 -120.65 18 0.5 0 1.8 1.5 2.5 12
DN70118376 Issue 2-0 en 18/06/2007
49 (113)
Table 10.
Example of HSUPA link budget (cont.)
Uplink Service
Indoor Location Prob. (dB) Indoor Standard Dev. (dB) Shadowing margin (dB) Isotropic Power Required (dB) Allowed Prop. Loss (dB) 90 10 7.8 -120.6 144.0
Own connection interference has been neglected from R99 uplink link budget as it has such a low impact on system performance. This is mainly related to the fact that uplink 64 kbps service is commonly used in R99 dimensioning, and other to own interference is very low, around 0.08. In HSUPA, the link budget can be made even with throughputs higher than 0.5 Mbps, which creates more interference.
Defining uplink link budget
The parameter definition is similar to R99 uplink DCH link budget. However, there are the following differences: 1. Define service parameters. . Service rate. You can define the throughput for HSUPA to calculate the allowed propagation loss. This affects the Eb/No value. The following table shows the simulated Eb/Nos for HSUPA.
Table 11.
Simulated Eb/Nos for HSUPA Vehicular A 30 km/h 10 % BLER Eb/No (dB)

0.8 0.2 -0.2 -0.5 -0.5 -0.7 -0.7
Pedestrian A 3 km/h 10 % BLER Bit rate (kbps)

32 64 128 256 384 512 768
Bit rate (kbps)

32 64 128 256 384 512 768
Eb/No (dB)
2.3 1.6 0.8 0.4 0.4 0.1 0.1
50 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSUPA dimensioning
Table 11.
Simulated Eb/Nos for HSUPA (cont.) Vehicular A 30 km/h 10 % BLER Eb/No (dB)
-0.2 1.3
Pedestrian A 3 km/h 10 % BLER Bit rate (kbps)

1024 1440
.
Bit rate (kbps)

1024 1440
Eb/No (dB)
0.6 2.1
HS-DPCCH overhead. As mentioned in HSDPA uplink link budget, the same HS-DPCCH overhead is implemented in HSUPA, which is dependent on the bit rate. The following table shows the overhead values for soft handover and without soft handover.
Table 12.
SHO Bit Rate (kbps) DS-DPCCH Overhead (dB) No SHO Bit Rate (kbps) DS-DPCCH Overhead (dB)
.
HS-DPCCH overhead for HSUPA

69 2.46 69 1.16 102.6 1.93 102.6 0.88 169.8 1.27 169.8 0.55 474 0.087 474 0.37 810 0.60 810 0.25 1146 0.39 1146 0.16
35.4 3.03 35.4 1.48
HSUPA EIRP. You can calculate HSUPA EIRP using the following formula: HSUPA EIRP = UE Transmit Power - HS_DPCCH overhead + Transmit Antenna Gain - Body Loss
2.
Define UE parameters. Define RX Antenna Gain and Handset Noise Figure. Commonly body loss is assumed to be 0.
3.
Define Node B parameters. Node B parameters are the same as in R99 DCH link budget. See R99 DCH coverage dimensioning.
4.
Additional differences compared to the R99 DCH uplink link budget
DN70118376 Issue 2-0 en 18/06/2007
51 (113)
Own connection interference. Own connection interference factor reduces the uplink interference floor by the UEs own contribution to the uplink interference, that is, by the desired uplink signal power. This means that the own connection contribution has to be noted in the interference floor calculation. The formula for calculating own connection interference contribution is as follows:
Eb R No Own_connection_int = 10LOG 1+ W
Interference floor. Based on the above mentioned modification the interference floor is calculated as follows: Interference_floor = Thermal noise + Node B noise figure + interference_margin - own_connection_interference
Other issues, formulas and parameters related to the HSUPA link budget are the same as the link budgets in R99. See R99 DCH coverage dimensioning.
5.2.2

HSUPA connections make use of HSDPA in the downlink direction. For the SRB, DPCH 3.4 kbps is needed.
5.2.3

From the HSUPA perspective, the cell range and coverage are dependent on uplink link budget and defined cell edge throughput. By defining the cell edge throughput, the Eb/No will be selected and the overall link budget and cell range estimation are as in R99 DCH link budget. HSUPA has additional features that affect the cell range. One which affects the load generated to the cell and also the cell range is then higher due to the lower interference margin.
52 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSUPA dimensioning
5.3

Capacity dimensioning can include one user throughput estimation or whole cell throughput estimation. The following issues affect capacity dimensioning:
.
Available load for HSUPA User location Number of users Load equation parameters, that is, intercell interference ratio which depends on sectorisation
Follow these steps to perform HSUPA capacity dimensioning. 1. Estimate the uplink load of DCH users and define the target uplink load margin. As mentioned earlier, HSUPA capacity dimensioning has to take into account also the capacity used for R99 DCH traffic. If the R99 uplink load is 36 % and the maximum target UL load is set to 80 %, HSUPA capacity is 80%-36% = 44%. This 44% can be used to define the capacity for HSUPA. Figure Load estimation for R99 DCH and HSUPA shows the load estimation between R99 DCH and HSUPA.
Uplink Load generated by R99 DCH 12
Increase in Interference (dB)
Uplink Load available for HSUPA UE
10 8 6 4 2 0 0 20 40 60 80 Example Target Uplink Load 100 Uplink Load (%)
Figure 12.
Load estimation for R99 DCH and HSUPA
DN70118376 Issue 2-0 en 18/06/2007
53 (113)
As shown in the figure, it is important to estimate the R99 load in uplink in order to define the HSUPA capacity. To calculate the load used in R99 DCH traffic you can utilise the formula discussed in Supporting R99 formulas. The uplink load is translated to uplink C/I using the uplink load equation:
C/I is translated to HSUPA bit rate using the Eb/No look-up table derived from link level simulations. This information can be used to estimate the throughput in the area with estimated parameters. To go into more detail, the available load can be divided into expected amount of HSUPA users. 2. Divide the available uplink load between the expected number of HSUPA users. The available HSUPA load has to be divided equally to every HSUPA user. When increasing the number of users, each user will have lower throughput due to the decreasing available load, thus influencing at the end the C/I. As a result of this step, all users will have the same available load and also the same C/I. To go into more detail, also the estimated HSUPA user location can be used to estimate user throughput.
54 (113)
DN70118376 Issue 2-0 en 18/06/2007
HSUPA dimensioning
3.
Estimate the link losses between the expected locations of HSUPA users and the BTS. This way you can get the average cell throughput by estimating the share of bad coverage HSUPA users and good coverage users, for example. Figure Example of HSUPA user distribution on cell area shows an example distribution of five users.
4000.0 3500.0 3000.0 UE1 link budget provides the cell edge path loss
y location
2500.0 UE2 2000.0 1500.0 UE4 1000.0 UE5 500.0 antenna 0.0 0.0 1000.0 2000.0 x location 3000.0 4000.0 UE3
Figure 13.
Example of HSUPA user distribution on cell area
The location can be estimated by introducing path loss offsets to determine the path loss for each UE. C/I can be calculated as follows.
WantedSignal Interf.Floor - WantedSignal
C / I = 10 x LOG
where . Wanted signal is the signal strength which is calculated from the link budget, assuming that the UE is transmitting at maximum power. The path loss offset can be introduced to determine the user location from the cell edge. . Interference floor is calculated as: Interference_floor = Thermal noise + Node B noise figure + interference_margin 4. Verify that the user receives the service.
DN70118376 Issue 2-0 en 18/06/2007
55 (113)
If the UE furthest from the cell cannot achieve the equal share C/I (step 2.), their share of the uplink load is decreased to correspond to their maximum achievable C/I, and you can utilise the load with other users who can achieve the level. As a result of capacity dimensioning, you can:
.
estimate the user throughput based on its location and available load estimate user throughput based on C/I estimation estimate the cell throughput based on users equal load and C/I estimate the cell throughput based on different user location, which can influence the load and C/I.
56 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning transport network

Purpose
The most critical task in dimensioning a transport network is to find a transmission solution for the connection between the transmission network and the base station site. The network rollout can depend on how fast this connection can be built. Leasing a Time Division Multiplexing (TDM) or Asynchronous Transfer Mode (ATM) line can be very expensive and timeconsuming. Microwave radio links can be more efficient if you build your own network and copper or fibre-based options are not available. The radio links can be either point-to-point or point-to-multipoint solutions.
Before you start
Note that the introduction of HSDPA means initially a moderate capacity increase on each HSDPA-enabled base station. Iub efficiency features such as BTS AAL2 Multiplexing help operators to more efficiently implement HSDPA if more than one active WAM is utilised. If an own microwave radio network is chosen, environmental factors such as line of sight, restrictions in building permissions or access to microwave radio frequency licences may have an impact. Check:
.
the number of subscribers the number of services per subscriber.
DN70118376 Issue 2-0 en 18/06/2007
57 (113)
Summary
Services per subscriber
Number of subscribers
Radio network planning
QoS requirements for the traffic
Required transmission capacity/RNC
Required transmission capacity/core NW
Transmission network planning (capacity, media, topology, protection...)
Figure 14.
Steps
1. Calculate the required transport network capacity. Calculate the required transmission capacity for the Base Transceiver Station (BTS) and Radio Network Controller (RNC). The needed transport network capacity depends on the radio network configuration, which again is based on the estimated number of the subscribers and services that the subscribers use. 2. Select transport network media. Depending on the environment and network configuration, you can choose from cables, radios, and leased lines. Check the granularities and capacities offered in radio links, fibre, and leased lines.
58 (113)
DN70118376 Issue 2-0 en 18/06/2007
3.
Plan transport network topology. Topology options are: . point-to-point . chain . loop . tree . mesh
4.
Plan transport network protection. Transport network protection can be achieved by: . securing the connections, so that information is transferred via two different routes (requires loop or mesh topology) . equipment redundancy, which means that if the equipment fails, the broken equipment is switched off and a new equipment is taken into use.
Expected outcome
.
transmission topology capacity of the transmission connections between the nodes in the transmission network
Further information
You can purchase Nokia planning services for dimensioning transport network. See also Planning synchronisation in Planning WCDMA RAN.
DN70118376 Issue 2-0 en 18/06/2007
59 (113)
60 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
7
7.1
Dimensioning BTS
Dimensioning Flexi WCDMA BTS
A new Base Transceiver Station (BTS) type called Flexi WCDMA BTS has been available since RAS05.1. Flexi Wideband Code Division Multiple Access (WCDMA) BTS is a new, truly modular, very compact, and high capacity wide-area WCDMA BTS that can be used in various indoor and outdoor installation options (such as floor, wall, stand, pole, mast, cabinet, 19" rack) and site applications (mini, macro, and distributed site solution). This solution can also be used as a multimode upgrade to existing Nokia UltraSite EDGE BTS with WCDMA carriers. Flexi WCDMA BTS consists of the following self-supporting BTS modules:
.
Radio Module, which provides the Radio Frequency (RF) functionality. System Module, which provides baseband processing as well as control and transmission functionalities. System Module provides up to 240 CE capacity. The number of CEs activated can be increased by licence control. HSDPA is activated in the Flexi WCDMA BTS dynamically, and the capacity reserved for HSDPA is defined using features Shared HSDPA Scheduler for Baseband Efficiency and HSDPA 48 Users per Cell. One to six cells may have HSDPA activated with Flexi WCDMA BTS. The baseband Extension Module is also available, increasing Flexi WCDMA BTS capacity to 2*240 = 480 CE.
Optional power supply module.
Optional Outdoor Cabinet is also available.
DN70118376 Issue 2-0 en 18/06/2007
61 (113)
RF Module
RF Module
RF Module
Extension System Module BTS System Module AC (Optional)
AC > DC
BBU
Figure 15.
Flexi WCDMA BTS modules
7.1.1
Capacity
Flexi WCDMA BTS provides 12-carrier capacity. Up to six sectors and four carriers per configuration are supported by HW. The output power options min 8/20/40W are available. The following Flexi 20/40 W per carrier configurations are available: 1, 1+1, 1+1+1, 2, 2+2, 2+2+2 and 2+1+1. 1 omni configuration is also available with 8W option. One Radio Module can support one or two sectors. For 1+1+1 (min 40W per carrier) or 2+2+2 (min 20W per carrier) configurations one System Module and two Radio Modules are required for a complete a WCDMA BTS setup. Baseband capacity of the system module can be added remotely with a SW license when needed. RAS06 (WBTS4.0) Flexi WCDMA BTS System Module capacity is:
.
240 CE, no common channels 240 CE - 26 CE = 214 CE with 1-3 cells (26 CE needed for CCCHs) 240 CE - 52 CE = 188 CE with 4-6 cells (52 CE needed for CCCHs)
62 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
Table 13. User data

AMR (voice) WB-AMR
2)
Flexi WCDMA BTS (1+1+1) processing capacity CE UL / Min SF

1)
CE DL / Min SF
1 / SF128 1 / SF128 1 / SF128 2 / SF64 4 / SF32 4 / SF16 8 / SF8 16 / SF8 4 / SF32 4 / SF32 1 / SF128
1 / SF64 1 / SF64 1 / SF64 2 / SF32 4 / SF16 4 / SF8 8 / SF4 16 / SF4 4 / SF16 4 / SF16 1 / SF64
PS 16 kbps PS 32 kbps PS 64 kbps PS 128 kbps PS 256 kbps PS 384 kbps CS 64 kbps CS 57.6 kbps CS 14.4 kbps
1) AMR codecs 12.2, 7.95 and 5.90 and 4.75 kbps supported 2) WB-AMR codecs 12.65, 8.85 and 6.6 kbps supported
7.1.2
Baseband capacity and HSDPA

An example of Flexi WCDMA BTS capacity with HSDPA is presented in the following table. The table refers to BTS baseband capacity only. In real networks, air interface and transport capacity issues have to be considered as well. For more information, see Dimensioning Air interface and Dimensioning Iub interface.
Table 14. Feature 5 codes
Flexi WCDMA BTS (1+1+1) baseband capacity and HSDPA 15 codes

Max throughput per BTS 3.6 Mbps 10.8 Mbps 10.8 Mbps CE required n/a n/a 80 CE Max Max throughput throughput per cell per BTS n/a n/a 3.6 (7.2) Mbps n/a n/a 10.8 Mbps
CE required Max throughput per cell HSDPA 16 Users per BTS 32 CE HSDPA 16 Users per Cell 96 CE 3.6 Mbps 3.6 Mbps 3.6 Mbps
Shared HSDPA Scheduler 80 CE for Baseband Efficiency (48 users per BTS)
DN70118376 Issue 2-0 en 18/06/2007
63 (113)
Table 14. Feature

+with HSDPA Code Multiplexing feature HSDPA 48 Users per Cell +with HSDPA Code Multiplexing feature
Flexi WCDMA BTS (1+1+1) baseband capacity and HSDPA (cont.) 15 codes
n/a 3.6 Mbps n/a n/a 10.8 Mbps n/a 80 CE 240 CE 240 CE 10.8 Mbps 10.8 Mbps 3.6 (7.2) Mbps 10.8 (14.4) Mbps 10.8 (21.6) Mbps 32.4 (43.2) Mbps
5 codes
n/a 240 CE n/a
The figures in parentheses assume that either 10- or 15-code phones are used in the network.
7.1.3
Capacity licenses
Flexi WCDMA BTS licensed capacity defines the capacity that the operator has purchased. Licensed capacity can be less than the maximum hardware capacity. Flexi WCDMA BTS baseband capacities are allocated according to the capacity license file. Because the ATM Cross-Connection (AXC) and the BTS exist in high volumes in the network, Nokia Siemens Network does not generate licenses for these network elements directly (NE licences), but so-called pool licenses are used. This means that the user gets the license to use a dedicated amount of features or capacity (pool license) and it is up to the user to determine how these NE licenses are distributed towards the network elements. As an example, you buy a pool license for 10.000 code channels for BTSs. You get a pool license file that allows using this capacity. With this pool license and the help of the license management tools in NetAct you can distribute the capacity according to capacity needs, for example, 120 channel elements for BTS-1, 70 channel elements for BTS-2, and so on. For this purpose, NetAct generates appropriate license files and downloads them to the network elements. For more information on licences, see Pool licences in Licence Management in WCDMA RAN.
64 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
7.1.4
Flexi WCDMA BTS and transmission

For the RNC, both Flexi WCDMA BTS and UltraSite WCDMA BTS look the same. The Asynchronous Transfer Mode (ATM) layer terminates at the Wideband Application Manager (WAM) of the UltraSite WCDMA BTSs. In Flexi WCDMA BTSs the termination point is the System Module unit.
7.2
Dimensioning UltraSite WCDMA BTS

Figure UltraSite WCDMA BTS architecture depicts Nokia MetroSite and Nokia UltraSite WCDMA BTS units. Wideband Signal Processor A (WSPA) and Wideband Signal Processor C (WSPC) capacities are presented in WSPA/C processing capacity.
DN70118376 Issue 2-0 en 18/06/2007
65 (113)
SR-bus
WTR
ST-bus R-bus
WAM WAM
WAF WPA WAF WPA
RR-bus T-bus
WSP WSP
Carrier Interface
WSP WSP WSP
WTR
RR-bus RT-bus
WSM
WSP
RT-bus
WSC MAIN WSC DSC-bus ST-bus R-bus

WAM WAM
SR-bus RR-bus
WSC REDU
WTR
WAF WPA WAF WPA
T-bus
WSP WSP WSP WSP WSP WSP
RT-bus
WTR
RR-bus RT-bus
WSM
AXU
DSC-bus SR-bus RR-bus T-bus

WSP WSP WSP WSP WSP
ST-bus R-bus
WAM WAM
IFU lub
WSP
WPA WAF WPA
WTR
WAF
RT-bus
WTR
RR-bus RT-bus SR-bus
WSM
ST-bus
DSC-bus
Figure 16.
UltraSite WCDMA BTS architecture
UltraSite WCDMA BTS units are explained in the following table.
Table 15. Unit

WAF
BTS units Description

Wideband Antenna Filter. Combines and isolates Tx/Rx signals and amplifies the received signals. One WAF is required per sector.
66 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
Table 15. Unit

WPA
BTS units (cont.) Description

Power Amplifier. A multicarrier amplifier with an operating bandwidth of any 20 MHz section on the whole 60 MHz WCDMA allocation (WPAC/D), on a 10 MHz section of two neighbour carriers (WPAI/J) or on a 15 MHz section of two neighbour carriers (WPAK). The number of WPAs depends on the number of sectors, carriers, Rollout Optimised Configuration (ROC) utilisation, and the required output power per carrier. WCDMA Transmitter and Receiver unit. One Wideband Transmitter and Receiver version B or D (WTRB/D) can serve two cells of 2way uplink diversity, WTRA can serve one cell. Summing and Multiplexing unit. Sums Tx signals from the signal processing units or other WSMs. Signal Processing unit. Performs Rx and Tx code channel processing, coding, and decoding functions. The number of WSPs is planned according to the expected traffic on the BTS. WSP capacities are presented in Tables WSPA processing capacity and WSPC processing capacity. Application Manager. There can be up to six WAM units installed in the BTS: Three WAMs act as primary WAMs (WAM in slots Nr. 0) and three WAMs act as secondary WAMs (WAMs in slots Nr. 1). One primary WAM at a time is selected as a Telecom and O&M master unit (Master WAM) by the system. Master WAM unit takes care of the control functions on BTS cabinet level. Those include BTS start-up, temperature control, configuration, and O&M processing. All WAM units perform telecom control functions, logical resource management, ATM processing, and transport channel frame protocol processing.
WTR
WSM WSP
WAM
AXU
Each UltraSite WCDMA and MetroSite WCDMA/50 Base Station has an integrated ATM switch, called the ATM Cross-connect (AXC) Node, for communication between the sectors inside the BTS, towards the RNC, and towards other BTSs. The AXU unit performs the main ATM functionality for the communication within the BTS and provides the connections to other network elements. The IFUs provide the physical connection to the network. They support the following transmission interfaces: E1/JT1, STM-0/STM1, E1, Nokia Flexbus.
IFU
7.2.1
WSPA/C processing capacity

The following table presents the WSPA processing capacity.
DN70118376 Issue 2-0 en 18/06/2007
67 (113)
Table 16.
WSPA processing capacity Decoding capacity

32 32 16 8 8 4 2
User data rate / kbps

AMR voice 16 32 64 128 256 384
Min SF
64 64 32 16 8 4 4
Encoding capacity
32 32 16 16 8 4 2
Min SF
128 128 64 32 16 8 8
The following table presents the WSPC processing capacity.
Table 17.
WSPC processing capacity Decoding capacity

64 64 32 16 16 8 4
User data rate / kbps

AMR voice 16 32 64 128 256 384
Min SF
64 64 32 16 8 4 4
Encoding capacity
64 64 32 16 16 8 4
Min SF
128 128 64 32 16 8 8
Support for mixed WSPA/C configurations has been available from RAN04 onwards.
7.2.2
UltraSite WCDMA BTS baseband capacity and HSDPA

An example of UltraSite WCDMA BTS capacity with HSDPA is presented in the following table. The table refers to BTS baseband capacity only. In real networks, air interface and transport capacity issues have to be considered as well. For more information, see Dimensioning Air interface and Dimensioning Iub interface.
68 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
Table 18. Feature 5 codes

CE required HSDPA 16 Users per 32 CE BTS HSDPA 16 Users per 96 CE cell Shared HSDPA Scheduler for Baseband Efficiency (48 users per BTS) + with HSDPA Code Multiplexing feature 64 CE
UltraSite WCDMA BTS (1+1+1) baseband capacity and HSDPA 15 codes

Max throughput per cell 3.6 Mbps 3.6 Mbps 3.6 Mbps Max throughput per BTS 3.6 Mbps 10.8 Mbps 10.8 Mbps CE required n/a n/a 64 CE Max Max throughput throughput per cell per BTS n/a n/a 3.6 (7.2) Mbps n/a n/a 10.8 Mbps
n/a
n/a 3.6 Mbps n/a 3.6 Mbps
n/a 10.8 Mbps n/a 3.6 Mbps
64 CE 192 CE 192 CE n/a
10.8 Mbps 3.6 (7.2) Mbps
10.8 Mbps 10.8 (21.6) Mbps
HSDPA 48 Users per 192 CE Cell + with HSDPA Code Multiplexing feature Baseband Capacity and HSPA Sharing n/a 64 CE
10.8 (14.4) 32.4 (43.2) Mbps Mbps n/a n/a
The figures in parentheses assume that either 10- or 15-code phones are used in the network.
7.2.3
Dimensioning steps
1. Dimension the WSP.
The number of WSPs/BTSs is determined by the expected traffic types and amounts, and the number of HW channels required for the Common Control Channels (CCCH). The basic capacity unit is Channel Element (CE), corresponding to the processing requirement for one AMR call. The CE consumption is calculated separately for UL and DL DCH traffic according to DCH rates. The following table is applicable for WSP card types A/C, but it is not applicable for common control channel signalling.
Table 19.
Required numbers of HW channels per bearer Required Channel Elements

1
Bearer data rate (kbps)

16 or voice
DN70118376 Issue 2-0 en 18/06/2007
69 (113)
Table 19.
Required numbers of HW channels per bearer (cont.) Required Channel Elements

2 Downlink: WSPA 2 / WSPC 4 Uplink: 4
Bearer data rate (kbps)

32 64
128 256 384
4 8 16
MultiRAB configurations are supported: one MS can have simultaneously, for example, AMR call + 2 PS calls.
2. Dimension the WSP common control channel.
The physical common control channels supported are:

.
Physical Random Access Channel (PRACH) Common Pilot Channel (CPICH) Primary Common Control Physical Channel (Primary CCPCH) Synchronisation Channel (SCH) Secondary Common Control Physical Channel (Secondary CCPCH) Acquisition Indicator Channel (AICH) Page Indicator Channel (PICH)
These physical channels are created in the BTS and require certain hardware processing capacities at the BTS.
.
WSPA and Common Control Channels WSPA can support simultaneously the common control channels of up to four cells. Every reserved cell deducts the available capacity for dedicated usage by eight channels. In 1+1+1 ROC configurations, 24 CEs for CCCHs processing is required. The WCDMA test loop reserves eight channel elements when WCDMA test loop is performed.
WSPC and Common Control Channels One WSPC is capable of handling one to three cells.
70 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
The WCDMA test loop reserves one channel element when WCDMA test loop is performed.
.
Mixed configuration (WSPA/C) If both different WSP types exist in the same BTS, CCCH is allocated according to the following priorities: 1. Assign all required signalling resources on WSPA. 2. WSPC card is used for signalling if A-type is already loaded or does not exist.
3. Allocate WSP DCH.
A single call needs to be processed on a single WSP unit. If the resource is not available on a single WSP card in the BTS, the system rejects the setup if a lower bit rate is not suitable for the connection. For example, a WSPA with 16 channels reserved for signalling has the capacity of 16 channels for user traffic. These channels are allocated to the incoming traffic requests until the sum of the used channel elements reaches 16. Requests exceeding the number of available channels on that WSP (see Table WSPA processing capacity) are rejected by the BTS if there is no free capacity on any other WSP unit in the BTS. However, in case of Real Time (RT) over RT (priority) and RT over Non-Real Time (NRT), the RNC can perform pre-emption type procedures. For accepting, for example, a PS 128 kbps call the BTS requires four free hardware channels on a single WSP card. If these resources are not available, the call is rejected.
Further information
For more information, see Nokia WCDMA RAN BTS configuration principles and Introduction to Nokia RAN configurations in Configuring WCDMA RAN. See also UltraSite and MetroSite BTS Commissioning in UltraSite WCDMA BTS Product Documentation.
7.2.4
HSPA sharing
In case of limited WSPC capacity (typically one WSPC and several WSPAs in the BTS), HSUPA and 5 codes HSDPA can be allocated to the same WSPC. No other channels are possible in the HSPA shared card.
DN70118376 Issue 2-0 en 18/06/2007
71 (113)
7.3
HSDPA and BTS dimensioning

New schedulers, namely Shared HSDPA Scheduler for Baseband Efficiency and HSDPA 48 Users per Cell, are introduced to support bit rates beyond 3.6 Mbps. HSDPA with schedulers that allow a maximum of 5 HS-PDSCH codes takes 32 CE capacity in the WSPC / Flexi Submodule that handles HSDPA cells (MAC-hs). Other CEs left can be used for other types of traffic. HSDPA with 15 HS-PDSCH codes takes 64 CE capacity in WSPC and 80 CE capacity in Flexi Submodule. No CE is left in the WSPC / Flexi Submodule for other channels. HSDPA 48 Users per Cell and Shared HSDPA Scheduler for Baseband Efficiency require 64 CE in WSPC and 80 CE in Flexi Submodule, with 5 or 15 codes. The following table gives the maximum numbers of HSDPA schedulers that can be simultaneously active per scheduler type. Note that only one type of schedulers can be activated in the BTS at a time.
Table 20.
Maximum number of HSDPA schedulers simultaneously active per scheduler type
HSDPA scheduler type Maximum number of schedulers simultaneously active UltraSite WCDMA BTS
HSDPA 16 Users per BTS HSDPA 16 Users per Cell Shared HSDPA Scheduler for Baseband Efficiency HSDPA 48 Users per Cell 4* 12 4* 12
Flexi WCDMA BTS, 1 System Module

3* 3 2* 2
Flexi WCDMA BTS, 2 System Modules

4 6 4* 5
*) Tcell parameter tuning is required in the RNC. Associated UL/DL DCH of the HSDPA user requires the capacity in the same way as normal DCH. Associated UL/DL DCH channels can be allocated to all WSPs / Flexi Submodules. See Table Associated DCH rates and CE usage.
72 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
Table 21. User data

PS 16 kbps PS 64 kbps PS 128 kbps PS 384 kbps
Associated DCH rates and CE usage CE required in UL / Min SF

1 / SF64* 4 / SF16 4/ SF8 16 / SF4
CE required in DL / Min SF
1 / SF128** 1/ SF128** 1/ SF128** 1/ SF128**
*) If SF is 32, 2 CE is required in UL **) 1 CE for DL signalling is required per HSDPA user The earlier WBTS3.0/WBTS3.2 HSDPA configurations can still be used, with existing baseband usage for 16 HSDPA users per BTS or 16 HSDPA users per cell. Capacity is reserved for HSDPA when needed according to HSDPA-related commissioning parameters. The baseband alternatives are Minimum Baseband Allocation, Shared Scheduler for Baseband Efficiency, HSDPA 16 Users per Cell, and HSDPA 48 Users per Cell.
Minimum Baseband Allocation
With this scheduler, one WSPC/ Flexi Submodule supports one to three HSDPA cells. A maximum of 16 HSDPA users per WSPC/ Flexi Submodule are supported. HSDPA users can be divided freely between three cells. Up to 3.6 Mbps is supported per WSPC/ Flexi Submodule with 5 codes and 16QAM. 32 CE is reserved from WSPC/ Flexi Submodule. The bit rate to be allocated to the uplink DCH is 16 kbps, 64 kbps, 128 kbps or 384 kbps. Up to 12 HSDPA cells can be served with 4 WSPC for HSDPA.
Shared HSDPA Scheduler for Baseband Efficiency
With this scheduler, a maximum of 48 HSDPA users per WSPC/ Flexi Submodule are supported. HSDPA users can be divided freely between three cells. Up to 10.8 Mbps is supported per WSPC/ Flexi Submodule with 5 codes and 16QAM. 64CE is reserved from WSPC and 80 CE from Flexi Submodule per BTS. The bit rate to be allocated to the uplink DCH is 16 kbps, 64 kbps, 128 kbps or 384 kbps. Up to 12 HSDPA cells can be served with 4 WSPC for HSDPA. For more information on this feature, see RAN1034: Shared HSDPA Scheduler for Baseband Efficiency in RAS06 Feature Descriptions.
DN70118376 Issue 2-0 en 18/06/2007
73 (113)
HSDPA 16 Users per Cell
With this scheduler, one WSPC/ Flexi Submodule unit per HSDPA cell is earmarked for HSDPA. This enables a maximum of 16 HSDPA users per cell to be supported. Up to 3.6 Mbps with 16QAM is supported per cell. 32 CE is reserved from each WSPC or Flexi Submodule. The bit rate to be allocated to the uplink DCH is 16 kbps, 64 kbps, 128 kbps or 384 kbps.
HSDPA 48 Users per Cell
With this scheduler, one WSPC/ Flexi Submodule unit per HSDPA cell is earmarked for HSDPA. The whole card is reserved for HSDPA. A maximum of 48 HSDPA users per cell are supported. Up to 14.4 Mbps with 16QAM is supported per cell. The bit rate to be allocated to the uplink DCH is 16 kbps, 64 kbps, 128 kbps or 384 kbps. For more information on this feature, see RAN1033: HSDPA 48 Users per Cell in RAS06 Feature Descriptions. For more information, see HSDPA functionality in HSDPA in BTS.
7.3.1
Tcell grouping
RNC parameter Tcell (Frame timing offset of a cell) can be used for grouping schedulers to cells. For example, the HSDPA 16 Users per Cell feature requires a processing capacity of 32 CE to be enabled for one to three cells in the BTS. Another 32 CEs can be added so that cell A is handled by the first 32 CE and cells B and C by the second 32 CEs. See Figure Tcell grouping example, 1+1+1: 2 x32 CE.
B 11 users Tcell = 4 5 users Tcell = 3 A 16 users Tcell = 0
Example 1: 1+1+1: 2x32 CE
Figure 17.
Tcell grouping example, 1+1+1: 2 x 32 CE
74 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
The following figure shows an example with a 2+2+2 configuration.

16 users Tcell = 0 Tcell = 2 16 users Tcell = 3 16 users Tcell = 6 Tcell = 1
f1
f2
16 users Tcell = 9
Example 2: 2+2+2: 4x32 CE
Figure 18.
Tcell grouping example, 2+2+2: 4 x 32 CE
The principles of grouping (maximum 4 groups) are as follows:

.
Group 1: Tcell values 0, 1 and 2 Group 2: Tcell values 3, 4 and 5 Group 3: Tcell values 6, 7 and 8 Group 4: Tcell value 9
For more information on Tcell, see also WCDMA RAN Parameter Dictionary and HSDPA resource allocations in the BTS inHSDPA in BTS.
7.4
HSUPA and BTS dimensioning

Capacity is reserved for HSUPA on need basis. The capacity reservation may be changed dynamically between DCH and HSUPA use. In the CE allocation, DCH has a higher priority than HSUPA. HSUPA reserves CEs in uplink and downlink. Additionally, DPCCH for HSPA needs one extra CE per HSUPA user in UL and DL. HSUPA is supported only with co-existence of HSDPA.
DN70118376 Issue 2-0 en 18/06/2007
75 (113)
The minimum capacity reserved for HSUPA is 8 CE. In this case, only HSUPA MAC-e is active. With WBTS4.0, at maximum two WSPCs / Flexi Submodules can be used for HSUPA. The operator can define the minimum HSUPA-reserved capacity to have the guaranteed service level. BTS reserves minimum capacity for HSUPA based on commissioning parameters Minimum baseband decoding capability Mbps and Minimum number of HSUPA UE per BTS.
Minimum baseband decoding capability Mbps value is the sum of all HSUPA users' bit rates.
See the following tables for example CE utilisation figures of UltraSite WCDMA BTS and Flexi WCDMA BTS HSUPA. For example, BTS HSUPA traffic is expected to be at maximum of eight users simultaneously and total HSUPA traffic to be up to 2.8 Mbps on L1. According to Table UltraSite WCDMA BTS and HSUPA CE utilisation, 48 CEs are required for HSUPA.
Table 22.
UltraSite WCDMA BTS and HSUPA CE utilisation Baseband decoding capability, Mbps L1
<1.4 8 32 32 48 48 64 64 1.4 8 32 48 48 64 64 64 2.8 8 48 48 64 88 88 88 4.2 8 64 64 64 88 108 108 5.6 8 88 88 88 88 108 128
UltraSite WCDMA BTS

Number of HSUPA 0 UE per BTS 0 1-4 5-8 9-12 13-16 17-20 21-24 8 8 8 8 8 8 8
76 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
Table 23.
Flexi WCDMA BTS and HSUPA CE utilisation Baseband decoding capability, Mbps
<1.4 8 32 32 56 56 80 80 1.4 8 32 56 56 80 80 80 2.8 8 56 56 80 112 112 112 4.2 8 80 80 80 112 136 136 5.6 8 112 112 112 112 136 160
Flexi WCDMA BTS

Number of HSUPA 0 UE per BTS 0 1-4 5-8 9-12 13-16 17-20 21-24 8 8 8 8 8 8 8
For more information, see HSUPA in BTS.
7.5
Extended Cell
For more information on the Extended Cell feature, see RAN1127: Extended Cell (180km) in RAS06 Feature Descriptions. Note that in RAS06, Extended Cell has been tested up to 100 km. The basic principles for Extended Cell in WCDMA BTS are as follows:
.
A cell is called Extended Cell when its radius is >20km. Cells with radius 20 km are treated according to normal baseband dimensioning rules. CE dimensioning needs to be calculated separately for each Extended Cell. For example, if there is a 1+1+1 configuration, with 1 * 20 km cell and 2 * 100 km cell, it is needed to calculate 1* 20 km cell according to normal common channel dimensioning rules and 2 * 100 km cells according to Extended Cell dimensioning rules. Extended Cell CE dimensioning rules are the same for all WCDMA frequencies. One or several of the cells in the BTS (supported configurations) can be configured as Extended Cells.
DN70118376 Issue 2-0 en 18/06/2007
77 (113)
Extended Cell and Flexi WCDMA BTS
Extended Cell common channel dimensioning rules for Flexi WCDMA BTS are as follows:
.
Up to 60 km cell: 27 CE Up to 120 km cell: 54 CE Up to 180 km cell: 80 CE
Extended Cell and UltraSite WCDMA BTS
For UltraSite WCDMA BTS, it is advisable to have at least one WSPC per Extended cell (+WSP for normal CCCH) for optimal CE consumption. Extended Cell common channel dimensioning rules for UltraSite WCDMA BTS are as follows, provided that every Extended Cell has its own WSPC. (WSP capacity for normal CCCH):
.
Up to 60 km cell: 16 UL / 16 DL CE Up to 120 km cell: 40 UL/ 16 DL CE Up to 180 km cell: 64 UL / 64 DL CE
7.6
BTS counters
Channel Element counters
The TCOM counts available and used capacity values using Channel Elements measure. Counters are reported to BTS Mgr and OMS via BTSOM. WBTS3.2 supported counters include maximum/minimum/average available HW capacity and maximum/minimum/average used capacity for UL and DL. New counters in WBTS4.0 include maximum/minimum/average used capacity for HSUPA. For more information, see UltraSite WCDMA BTS and Flexi WCDMA BTS product documentation.
78 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
7.7
7.7.1
WCDMA BTS capacity allocation principles

UltraSite WCDMA BTS
This section provides an overview of managing the DSP and Asynchronous Transfer Mode (ATM) resources required for the common and dedicated channels in the Wideband Code Division Multiple Access (WCDMA) Base Transceiver Station (BTS). In the WCDMA, the amount of users in the air interface can be relatively large, and therefore the allocation and efficient use of the resources are important. The reason for this functionality is that the DSP processing and ATM transmission capacity have been distributed inside the BTS. The amount of mobile users the BTS can carry depends on the services the users have. For example, a video call takes much more resources than a traditional speech call. In the BTS, the Telecom (TCOM) software (SW) runs Resource Management(RM)-related tasks. In practice, the BTS TCOM RM SW receives resource requests for different channel allocations from the Radio Network Controller (RNC). The BTS TCOM calculates the resource need for the channel based on the parameters received in the resource request and selects the appropriate resources for the requests. In case a WSP unit does not have enough resources, the call can be allocated to another Wideband Signal Processor (WSP) unit under a specific Wideband Application Manager (WAM) unit. Another important feature in the TCOM RM software is the load balancing between the BTS subracks and units. The BTS TCOM RM software has been divided into Global and Local RMs. Figure BTS TCOM RM overall presents the overall RM SW within the BTS. In brief, the Global RM takes care of the WAM and the Local RM of the WSP selection.
WSPs
WSP
WSP
WSP
WSP
WSP
WSP
On each WAM
Local RM
Local RM
Master WAM
Global RM
Figure 19.
BTS TCOM RM overall
DN70118376 Issue 2-0 en 18/06/2007
79 (113)
7.7.1.1
Primary/Secondary WAM
In the UltraSite WCDMA BTS, each subrack has two slots for the WAM units, that is the Primary and Secondary slots, except for the MetroSite 50/ WCDMA BTSs, which only have the Primary WAM slot available. The first WAM in the subrack is always installed in the Primary unit slot which has access to every control bus and can thus start and drive the subrack. The Secondary WAM is required when there are more than three WSPs installed in a subrack. It provides ATM/ATM Adaptation Layer type 2 (AAL2) capacity and telecom functions for the allocated WSPs. However, it does not have access to all control and data buses and cannot drive the subrack in case of a Primary WAM failure.
Secondary Primary WAM WAM WAF WPA WAF WPA RR-bus T-bus
WSP WSP WSP WSP WSP
R-bus
WAM WAM
WTR
WTR
RR-bus RT-bus
WSM
DSC-bus
Figure 20. 7.7.1.2
Primary/Secondary WAMs in subrack
Master/Slave WAM
One of the Primary WAMs in a cabinet is the Master WAM. The WAM is the master controller for the whole BTS and performs common O&M and telecom functions such as operational software local storing and distributing, configuration management, alarm collection, handling, and cabinet level telecom resource management. Other Primary WAMs, which are not in a Master mode, are called Slave WAMs. A Slave WAM can be allocated to be a Master WAM in case of a current Master WAM failure. A new Master WAM selection requires a BTS site reset.
80 (113)
WSP
RT-bus
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
SR-bus
WTR
ST-bus R-bus
Secondary WAMs, Primary WAMs can always in Slave either be in Master or WAM mode Slave WAM mode Carrier Interface
WAM WSP WSP WSP WAM
WAF WPA WAF WPA
RR-bus T-bus
WSP WSP
WTR
RR-bus RT-bus
WSM
WSP
RT-bus
WSC MAIN WSC DSC-bus ST-bus R-bus

WAM WAM
SR-bus RR-bus
WSC REDU
WTR
WAF WPA WAF WPA
T-bus
WSP WSP WSP WSP WSP WSP
RT-bus
WTR
RR-bus RT-bus
WSM
AXU
DSC-bus SR-bus RR-bus T-bus

WSP WSP WSP WSP WSP
ST-bus R-bus
WAM WAM
IFU lub
WSP
WPA WAF WPA
WTR
WAF
RT-bus
WTR
RR-bus RT-bus SR-bus
WSM
ST-bus
DSC-bus
Figure 21. 7.7.1.3
WSP and WAM allocation within a subrack
WSP and WAM allocation within a subrack
When a call setup procedure is started and a request is sent to the BTS, several decisions are required relating to resource allocations and their management. A basic guideline for a subrack/WAM selection is sharing the load equally between the subracks and WAMs. This can be based on WSP load, ATM load, and AAL2 capacity. When a subrack/WAM (or the ATM termination point) is selected, it cannot be changed. A call can be moved within the WSPs under the selected WAM.
DN70118376 Issue 2-0 en 18/06/2007
81 (113)
A WAM can handle up to three WSPs. The served WSPs are allocated to WAMS based on a unit slot number so that the lowest three WSP units found are allocated to the Primary WAM and the last 1....3 units found for the Secondary WAM. This kind of allocation is called a WAM pool, that is WAM + 1...3*WSP. Example Four WSPs installed in bb-subrack slots 1, 3, 5, and 6, two WAMs
Two WAM pools are created. The Primary WAM handles the WSPs in slots 1, 3, and 5. The WSP in slot 6 is allocated to the Secondary WAM.
Secondary Primary WAM WAM WAF WPA WAF WPA RR-bus T-bus
WSP 5 WSP 6 WSP 3
R-bus
WAM WSP 1 WAM
WTR
RT-bus
WTR
RR-bus RT-bus
WSM
DSC-bus
Figure 22. 7.7.1.4
WSP to WAM allocation
Common Control Channel (CCCH) allocation
The following list summarises the different WSP units and their capacity alternatives in an Adaptive Multi-Rate speech codec (AMR)/CCCH mode. WSPA:
.
32 AMR users, no common channels 24 AMR users, common channels for one cell 16 AMR users, common channels for two cells 8 AMR users, common channels for three cells
WSPC:
82 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
64 AMR users, no common channels 48 AMR users, common channels for one - three cells
The CCCH allocation order is: 1. 2. WSPA WSPC
The CCCHs are allocated between the subracks to different WSP units for redundancy and load balancing reasons. The basic principles for a CCCH allocation are:
.
Common connrol channels are primarily allocated to WSPA units if available. Select a WAM that does not yet handle any common channels and has a WSPA. If such a WAM is not found, select a WAM that handles the least common channels and has a WSPA. If there is no WAM with a WSPA, select a WAM with a WSPC. The same WAM is also selected to handle the common channels of one three cells.
When the CCCHs are allocated, they can be located in any subrack within a cabinet. In the following figures, the WSPAs are depicted as a four-DSP (RAKE-CODEC pair) environment having eight Channel Elements (CE) in each. The WSPC is depicted as a one-DSP environment having 64 CEs. In the figures, one slot depicts one CE. Example 1+1+1 configuration with two WSPA units in different subracks
The CCCHs are allocated so that subrack 1 has 2-cell CCCHs and subrack 2 has 1-cell CCCH as shown in Figure Common control channel allocation example for 1+1+1 onfiguration with two WSPAs.
DN70118376 Issue 2-0 en 18/06/2007
83 (113)
WSPA (1) Subrack 1
WSPA (2) Subrack 2
Figure 23.
Common control channel allocation example for 1+1+1configuration with two WSPAs
Example
1+1+1 configuration with two WSPC units in different subracks
The CCCHs are allocated so that subrack 1 has all 3-cell CCCHs as shown in Figure Common control channel allocation example for 1+1+1 configuration with two WSPCs.
WSPC (1)
WSPC (2)
Subrack 1
Subrack 2
Figure 24.
Common control channel allocation example for 1+1+1 configuration with two WSPCs
CCCH allocation with single WPA and several TRXs
A special case is when a WPA is divided between, for example, two TRXs. In this case, the CCCHs are allocated to WSPs which are allocated to the same WAM unit due to WPA unit power control functions.
7.7.1.5 Dedicated Channel (DCH) allocation Load sharing principles between WSP, WAM, and subrack
When a new Radio Access Bearer (RAB) service or a call setup is requested, the following selections are done:
84 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
Subrack/WAM selection, ATM termination WSP selection DSP environment selection
A basic rule for the subrack/WAM selection is sharing the load equally between the subracks and WAMs. Criteria for this are the WSP load, ATM load and AAL2 capacity. Based on a reference value calculated for each WAM, the subrack and WAM which has the most unlimited capacity available are selected. With the WSP/DSP selection for a new RAB request, the RRM primarily allocates the RAB to the most fully loaded WSP/DSP environment possible within the WAM pool WSPs. In other words, the RRM keeps a maximum number of resources free to enable high data rate calls. From RAN04 onwards, the RRM favours the WCPC units for a new AMR call due to a possible reconfiguration or a new RAB request, until the free capacity between the subracks or units is equal. The following table depicts the use of the CEs for different calls and data rates.
Table 24.
The use of CEs with different data rate calls Number of CEs #
1 2 4 8 16 1 4 4
User data rate required

AMR/16 kbit/s PS 32 PS 64/128 PS 256 PS 384 CS 14.4 CS 57.7 CS 64
Example
Load sharing principles between the WSP, WAM, and a subrack with 1+1+1 configuration with two WSPA units in different subracks
The CCCHs are allocated so that the subrack 1 gets 2-cell CCCHs and subrack 2 gets 1-cell CCCH. The AMR calls 1...8 are allocated to subrack 2 due to load balancing as presented in Figure CCCHs and eight AMR calls in WSPA. The additional AMR calls are allocated one by one between the subracks until the full capacity is used.
DN70118376 Issue 2-0 en 18/06/2007
85 (113)
WSPA (1) Subrack 1
WSPA (2) Subrack 2
Figure 25.
CCCHs and eight AMR calls in WSPA
In case of higher data rate calls, the RRM checks the possibility to allocate a call to any existing eight-call environment if there are enough free resources available. If not, the allocation is done to another subrack WSPA unit and a new eight-call environment is taken into use. Example Load sharing principles between the WSP, WAM, and a subrack with 1+1+1 configuration with two WSPC units in different subracks
The CCCHs are allocated so that subrack 1 gets all the 3-cell CCCHs. The AMR calls 1...16 are allocated to subrack 2. After that each new call is allocated one-by-one equally between the subracks as presented in Figure CCCHs and 16 AMR calls in WSPCs.
WSPC (1)
WSPC (2)
Subrack 1
Subrack 2
Figure 26.
CCHCs and 16 AMR calls in WSPCs
In case of higher data rate calls which request more capacity, the following new AMR call is allocated to the other subrack due to load balancing. Example Load sharing principles between the WSP, WAM, and a
86 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
subrack with 1+1+1 configuration with WSPA and WSPC units in different subracks In case of a mixed WSPx configuration, all CCCHs are allocated to a WSPA unit, as presented in Figure CCCH allocation in mixed WSPA/C case. After that all resource requests are allocated to a WSPC until there is space for eight AMR calls in both units, as presented in Figure Resource allocation until equal amount of free resources.
WSPA (1)
WSPC (2)
Subrack 1
Subrack 2
Figure 27.
CCCH allocation in mixed WSPA/C case
WSPA (1)
WSPC (2)
Common channels 16 kbps or AMR 64 kbps 128 kbps 384 kbps
Subrack 1
Subrack 2
Figure 28.
Resource allocation until equal amount of free resources
In Figure Resource allocation until equal amount of free resources above, the WSPC capacity is reserved for one 384 kbit/s, one 128 kbit/s, and two 64 kbit/s PS data calls, and 28 AMR calls.
RAB reconfiguration
In case of a RAB reconfiguration, for exampl,e 64 kbit/s to 384 kbit/s, a call can be re-allocated to another WSP unit under the same WAM pool, provided there are not enough free resources in the original WSP unit. In case of lacking resources under the specific WAM pool WSPs, the requested RAB reconfiguration is rejected and the original 64 kbit/s service is maintained. In RAN1.5 with only the WSPA supported, the allocation is
DN70118376 Issue 2-0 en 18/06/2007
87 (113)
done so that the fullest WSP unit (and in case of a WSPA also the fullest 8call environment) that has enough capacity to handle the call is selected. From RAN04 onwards, WSPC is supported and the same principles apply as in RAN1.5.
MultiRAB support
In MultiRAB configurations, the RAB requests more resources than an AMR call. The principle is the same as in other cases, so that the total RAB-requested resource amount is compared to the existing free environment, and based on the load balancing principles, the most unrestricted WAM environment is selected.
Asymmetric Uplink/Downlink (UL/DL) bit rate
Asymmetric UL/DL means that the UL and DL directions have different bit rate requirements. The rule for allocating resources for asymmetric bit rates is based on a higher data rate requirement. In practise, this means that the UL has some free resources reserved due to a higher DL bit rate.
7.7.1.6 Recovery actions WSP failure
In case of a WSP failure with common channels, the cell is temporarily out of service while the CCCHs are re-allocated. If during the CCCH reallocation no free resources are available, the cell stays down, and from RAN04 onwards there will be an alarm related to that. In case of an allocated WSP failure for active calls, the calls are lost and must be redialled.
WAM failure
1.
RAN1.5: In case of a Slave or Secondary WAM failure, the specific WSPs controlled by the failed WAM are lost, and the calls are dropped. The recovery is through a site reset and the RF network is maintained, but with less WAM/WSP capacity. In case of a Master WAM failure, the recovery is not possible, and the whole BTS is down. The WAM must be replaced to recover the situation. After an unwanted Slave WAM reset, for example by power reset, the specific WTRs stay in a disabled state. The recovery is through a site reset.
2.
RAN04: In addition to RAN1.5, the Master WAM failure is the following:
88 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
The Master WAM is switched over to another Master WAM (=Primary WAM) candidate through a site reset. The failed Master WAM and the associated Secondary WAM are lost, as is the associate WSP capacity. Also the cell behind the Master WAM is lost.
7.7.1.7 HSDPA
When a High-Speed Downlink Packet Access (HSDPA) call is established, there are needed capacity allocations or reservations on the Virtual Channel Connection (VCC), WAM, and WSP level. The VCC selection is done by the RNC. Either a HSDPA Dedicated VCC or a Shared VCC is used. With BTS AAL2 multiplexing, the WAM and WSP selection are done by the BTS. With Basic AAL2 multiplexing, the WAM selection is done by the VCC selection. For more information on the Shared VCC, see HSDPA Transport with Best Effort AAL2 QoS in RAN04 and RAS05 Transmission and Transport Features . For more information on the Dedicated VCC, see RAN1020: Route selection in RAS05.1 Transmission and Transport Features. For more information on WAM allocation, see HSDPA functionality in HSDPA in BTS. Example Shared VCC is used with BTS AAL2 multiplexing
1+1+1 BTS with 4*WSPC, 4*E1 Iub, Iub U-plane configured as 8000 cps + 8000 cps Shared VCCs.
DN70118376 Issue 2-0 en 18/06/2007
89 (113)
WSPC3 Uplane 8000 cps
WAM1
WAM3
Figure 29.
Uplane 8000 cps
BTS configuration example
The call allocation goes as: CCH Allocation: The first WSPC is selected: WSPC1 and WAM1. HSDPA allocation:
.
"16 users BTS" and "16 users cell" the first HSDPA cell: the WAM with the most free WSP capacity is selected (WAM3). WSPC3 is selected. "16 users cell" 2nd HSDPA cell: the WAM with the most free WSPC capacity is selected (WAM1). The WSPC2 with the most free CE capacity is selected. "16 users cell", 3rd HSDPA cell: the WAM with the most free WSPC capacity is selected (WAM3). The WSPC with the most free CE capacity is selected. (WSPC4).
90 (113)
WSPC4
WSPC2
WSPC1
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
CCCH
2nd HSDPA
1st HSDPA
3rd HSDPA
WSPC1 WAM1 Common channels HSDPA
WSPC2
WSPC3 WAM3
WSPC4
Figure 30.
HSDPA allocation example
Example
The BTS is in operation, and there are several calls allocated around the WAMs and WSPs
The total traffic/BTS is 53*AMR, 6*64 kbps, 1*128 kbps, and 1*384 kbps. WSPC1: 40 CE used, 24 free WSPC2: 32 CE used, 32 free WSPC3: 28 CE used, 36 free WSPC4: 13 CE used, 51 free
WAM1: CCCH + 36 AMR + 5*64, 3375 cps WAM3: 17 AMR + 1*128 + 1*384, 3473 cps
DN70118376 Issue 2-0 en 18/06/2007
91 (113)
Then a HSDPA call is established. The HSDPA is allocated to the WAM which has the most free WSP capacity: WAM3 with 87 free CEs is selected. Then the least loaded WSP, which has enough capacity for the HSDPA, that is the WSPC4 is selected. After that the load is: WSPC1: 40 CE used, 24 free WSPC2: 32 CE used, 32 free WSPC3: 28 CE used, 36 free WSPC4: 45 CE used, 19 free
WAM1: CCCH + 36 AMR + 5*64, 3375 cps WAM3: 17 AMR + 1*128 + 384, 3473 cps The associated DCH, that is 64 kbps, is allocated to the WAM1 and there to the WSPC1. WSPC1: 44 CE used, 20 free WSPC2: 32 CE used, 32 free WSPC3: 28 CE used, 36 free WSPC4: 45 CE used, 19 free
WAM1: CCCH + 36 AMR + 6*64, 3591 cps WAM3: 17 AMR + 1*128 + 1*384, 3473 cps If another HSDPA cell is needed, it is allocated to the WAM3, as it still has more free CEs in the WSPCs (55 vs 52) and enough free CEs on the WSPC3 to allocate the HSDPA the 32 CEs needed. So after the second HSDPA allocation, the WSP load is: WSPC1: 44 CE used, 20 free WSPC2: 32 CE used, 32 free WSPC3: 60 CE used, 4 free
92 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning BTS
WSPC4: 45 CE used, 19 free If the third HSDPA cell is needed, it is generated on the WSPC2, which is the only WSPC with enough free CE capacity available and not yet having HSDPA allocated. Start:
CCCH
WSPC1 WAM1 Common channels HSDPA AMR or 8-16 kbps 64 kbps 128 kbps 384 kbps
WSPC2
WSPC3 WAM3 WSPC1: WSPC2: WSPC3: WSPC4: WAM1: WAM2: 40 used, 24 free 32 used, 32 free 28 used, 36 free 13 used, 51 free
WSPC4
53 * AMR 6 * 64 1 * 128 1 * 384
CCCH + 36 AMR + 5 * 64, 3375 cps 17 AMR + 1 * 128 + 1 * 384, 3473 cps
Figure 31.
BTS CCCH and DCH allocation example
The BTS load after the three HSDPA cells have been activated:
DN70118376 Issue 2-0 en 18/06/2007
93 (113)
CCCH
2nd HSDPA
1st HSDPA
3rd HSDPA
WSPC1
WSPC2
WSPC3
WSPC4
Figure 32.
BTS CCCH, DCH, and HSDPA allocation example
7.7.2
Flexi WCDMA BTS

Allocation of common control channels
The TCOM selects the least loaded System Module to handle the first cell's CCCHs. The second and third cell's CCCHs are also allocated on the same Submodule unit. If there are more than three cells, the TCOM selects the another least loaded Submodule unit to handle the fourth to sixth cell's CCCHs.
Allocation of dedicated channels
The RM of the TCOM allocates a new DCH user to the most loaded baseband Submodule with sufficient capacity for that DCH. The TCOM tries to keep some baseband Submodule free as long as possible, so that when a higher data rate request comes from the RNC, there are enough resources for that. The non-HSPA baseband Submodules are favoured for the DCH traffic. For HSDPA, the baseband Submodule with the most free capacity is selected.
94 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning RNC
Dimensioning RNC
Radio Network Controller (RNC) dimensioning is based on the RNC throughput requirement in Mbps and Erlangs, the number of the Base Transceiver Stations (BTSs) and cells to be connected with the RNC, and the total sum of the ATM Adaptation Layer Type 2 (AAL2) connectivity for the Iub, Iur, and Iu-CS interfaces. Therefore, RNC dimensioning requires that the preliminary dimensioning of the BTSs, Uu, Iub, Iur, and Iu interfaces has been done, or is done in addition to RNC dimensioning. For information on new capacity steps, see Nokia WCDMA RNC Product Description for RNC450 and Nokia WCDMA RNC Product Description for RNC196. RNC connectivity calculation has been modified with the UBR+ feature. see RNC product descriptions for more information. For RNC, RAS06 release is only a SW release since neither any changes in RNC configurations nor any new plug-in-units are introduced. Therefore, the configurations and capacity steps are as in RAS05.1 system release. Due to the discontinuity of the support of the CCPC2-A, CDSP-B and MCPC2-A in RN3.0 release, all these old HW units must be upgraded into their new PIU variants. Capacity step 1 to 5 of RNC196 may currently include old HW. So, in all these five capacity steps of RNC196, the old PIUs should be replaced at minimum as listed here:
.
Replace CCPC2-A with CCP10 /CCP18-A Replace CDSP-B with CDSP-C Replace MCPC2-A with MCP18-B
Foe RNC configurations and capacity figures, see Nokia WCDMA RNC Product Description for RNC450 and Nokia WCDMA RNC Product Description for RNC196. RAN Capacity Planner can be utilised for RNC dimensioning.
DN70118376 Issue 2-0 en 18/06/2007
95 (113)
New HSPA rates on different layers (Air interface, RLC payload, Frame Protocol, ATM rate) are presented in the following table.
Table 25. HSPA
HSPA rates L1 rate (Uu), RLC Mbps per payload user rate, kbps
1.8 3.6 7.2 10 1600 3360 6720 9600
FP rate, Mbps
1.7 3.6 6.9 9.9
ATM rate, cps

4710 9900 19200 27400
HSDPA QPSK HSDPA 16 QAM, 5 codes HSDPA 16 QAM, 10 codes HSDPA 16 QAM, 15 codes HSUPA
1888
5530
However, in RNC dimensioning, FP OH 1.1 for HSPA is used. Iu-CS signalling link dimensioning figures are presented in the following table.
Table 26. Erlangs

1000 3000 5000 7000 9000 11000
Iu-CS signalling link dimensioning # links

2 4 6 8 10 12
Needed BW (cps)
2000 4000 6000 8000 10000 12000
Link size (cps)

1000 1000 1000 1000 1000 1000
96 (113)
DN70118376 Issue 2-0 en 18/06/2007
Dimensioning interfaces
9
9.1
Dimensioning Iub interface
RAS06 introduces several new features affecting Iub utilisation:
.
RAN759: Path Selection RAN1099: Dynamic Scheduling for HSDPA with Path Selection RAN1100: Dynamic Scheduling for NRT DCH with Path Selection RAN1142: ATM over Ethernet for BTS RAN1063: Hybrid BTS Backhaul RAN1064: Ethernet+E1/T1/JT1 Interface Unit (Iub User Plane) for Flexi WCDMA BTS RAN1097: Ethernet Interface Unit IFUH (Iub User Plane) for AXC RAN1095: UBR+ for Iub User Plane RAN1096: Transport Bearer Tuning
For more information on these features, see RAS06 Feature Descriptions. For a description of the Iub interface, see Iub interface in WCDMA RAN Interfaces.
9.1.1
Transport Bearer Tuning

Transport Bearer Tuning (TBT) affects the Iub dimensioning; instead of 100 % activity of PS DCHs, lower activity factors (AF) may be utilised. The effects can be investigated with the RAN Capacity Planner.
DN70118376 Issue 2-0 en 18/06/2007
97 (113)
Activity Factor with Dynamic NRT DCH Scheduling
If AF is set to too low with TBT feature (384 kbps: AF < 0.5, for other rate AF< 0.6) the defaults (0,5 for 384 kbps and 0,6 for other speeds) are used. This limitation applies only to AFs for DL NRT bearers. This changing of AFs is done only if the dynamic scheduling for NRT DCH with Path Selection feature is enabled for a BTS.
Activity Factors with Dynamic NRT DCH Scheduling with Path Selection
If the feature is enabled, an internal default value of AF=0.75 is used for NRT DCH DL and UL bearers. If the Transport Bearer Tuning feature (TBT) is enabled, the default value is not used. Instead, the operator configurable AFs are used.
9.1.2
Hybrid transport
Hybrid transport solution enables BTSs to be backhauled over packetswitched technologies, IP and Ethernet in particular. Usage of Ethernet may increase the delay over the Iub; however, current estimation is that HSUPA can tolerate delays of up to 160 ms, after which the Macro Diversity Combining does not work properly. However, the estimated value should be verified. For more information, see RAN1063: Hybrid BTS Backhaul in RAS06 Feature Descriptions.
9.1.3
Iub VCC configuration

The Iub bandwidth is divided between:
.
signalling links carried on AAL5 (Common Node B Application Protocol (CNBAP), Dedicated Node B Application Protocol (DNBAP), Asynchronous Transfer Mode (ATM) Adaptation Layer 2 Signalling (AAL2Sig)) Operation and Maintenance (O&M) on AAL5 User plane (U-plane) Virtual Channel Connections (VCCs) carried on AAL2.
User plane VCCs also transport Common Control Channels (CCCHs), Dedicated Control Channels (DCCHs), and Dedicated Traffic Channels (DTCHs). Therefore, the capacity for Iub is as follows: Iub capacity = U-Plane + CNBAP + DNBAP + AAL2sig + O&M
98 (113)
DN70118376 Issue 2-0 en 18/06/2007
For the O&M, 150 cps (~64 kbps) is recommended per BTS. The maximum number of the AAL2 connections per VCC is 248. The CCCHs of one cell require 4-6 AAL2 connections, depending on the Secondary Common Control Physical Channel (S-CCPCH) usage. Each Adaptive Multirate (AMR)/Packet Switched (PS)/Circuit Switched (CS) call requires 2 AAL2 connections (DTCH + DCCH). The maximum size of AAL2 Path (AAL2UP VCC) in RAS05.1 RNC is 41000 cps. The Iub configuration principles are shown in Figure BTS AAL2 multiplexing and Table Number of VCCs. Note that in RAS05.1, the AXC ATM layer configuration management for BTS function makes the BTS internal VCC configuration between the Wideband Application Manager (WAM)-ATM Cross-Connect Unit (AXU) automatic. Therefore, you do not see WAM-AXU commissioning at all; only Iub VCCs need to be commissioned.
DN70118376 Issue 2-0 en 18/06/2007
99 (113)
1 WSPC: 64 Code Channels WAM1
VC1-UPLANE (DCH) VC2-AAL2 SIG VC3-DNBAP VC4-CNBAP
1 WSPC: 64 Code Channels
VC5-O&M RNC VC6-UPLANE (DCH) VC7-AAL2 SIG WAM2 VC8-DNBAP VC9-UPLANE (HSDPA) AXC (AXUA, AXUC, AXUD)
lub
BTS with basic AAL2 multiplexing
1 WSPC: 64 Code Channels WAM1 BTS internal VCCs configured automatically by the RNS Split feature BTS AAL2 Multiplexing
VC1-UPLANE (DCH) VC2-AAL2 SIG VC3-DNBAP VC4-CNBAP VC5-O&M VC6-DNBAP WAM2 VC7-UPLANE (HSDPA)
AXC (AXUB, AXCC, AXCD)
RNC
1 WSPC: 64 Code Channels BTS with BTS AAL2 multiplexing
lub
Figure 33.
BTS AAL2 multiplexing
100 (113)
DN70118376 Issue 2-0 en 18/06/2007
Note that the High-Speed Downlink Packet Access (HSDPA) and Dedicated Channel (DCH) traffic can also share the same VCC.
Table 27. VCC
Number of VCCs Flexi WCDMA BTS

One per BTS (DCH) (*) One per BTS (HSDPA) One per BTS One per BTS One per BTS One per BTS AAL5 AAL5 AAL5 AAL5
BTS with basic BTS with BTS AAL2 multiplexing AAL2 multiplexing
One per WAM (DCH) (*) One per BTS (HSDPA) (**) One per BTS (DCH) (*) One per BTS (HSDPA) One per BTS One per WAM One per BTS One per BTS
ATM adaptation layer

AAL2
U-plane
CNBAP DNBAP AAL2sig O&M
One per BTS One per WAM One per WAM One per BTS
* One VCC can contain up to 248 AAL2 connections. In cases where the BTS capacity exceeds 248 AAL2 connections, more user plane VCCs per WAM or per BTS can be required. ** Used with the RAS05.1 Route Selection function. Alternatively, multiple VCCs can be configured for HSDPA .
9.1.4
Protocol overheads
The following protocol overheads are included in the Iub:
.
Radio Link Control (RLC) (PS services): 5% Frame Protocol (FP): variable, depends on the data rate AAL2: 3 Bytes per AAL2 packet (payload max 45 Bytes) + 1 Byte/ ATM cell ATM cell overhead: 10.4% = (53-48)/48
Note that partially filled ATM cells can be filled with padding that causes slight increase in the overhead.
DN70118376 Issue 2-0 en 18/06/2007
101 (113)
9.1.5
Connection Admission Control

The ATM Connection Admission Control (CAC) evaluates whether there is enough bandwidth for every new requested bearer. The ATM CAC Iub AAL2 capacity requirement depends on, for example, the service mix, average and peak service data rate, Transmission Time Interval (TTI), allowed delays, and cell losses. The accurate way for Iub dimensioning is to use Radio Access Network (RAN) Capacity Planner using the same AAL2 CAC algorithm as the RNC. The RAN configurations contain examples of the actual Iub capacities (see Introduction to Nokia RAN configurations). The recommended parameters related to the RNC CAC algorithm are:
.
Maximum packet loss on Iub/IuCS/Iur: 0.001 (10-3) Maximum allowed AAL2 queuing delay on Iub/IuCS/Iur: 10 ms
9.1.6
Iub signalling links

The Iub signalling links are CNBAP, DNBAP, and AAL2Sig carried on AAL5. Note that the presented dimensioning recommendation is based on the Nokia internal assumptions on traffic mixes. The traffic in operating networks can have different characteristics causing different signalling loads. Note that it has been assumed that the used PS data rates are 64 kbps or more; with the lower rates and 3GPP Iub, the DNBAP capacity may need to be increased. The main loading components of the CNBAP links are:
.
Radio Link setup requests and responses Radio Resource Indication (RRI) messages
Therefore, the CNBAP bandwidth requirement depends on the call setup and radio link addition (soft handover) amounts, as well as the RRI period. DNBAP transfers are, for example:
.
Radio Link Measurement (RLM) Reports Radio Link Deletion commands
102 (113)
DN70118376 Issue 2-0 en 18/06/2007
Radio Link Re-configuration messages Radio Link branch addition commands (softer handovers)
Therefore, the DNBAP capacity requirement depends, for example, on the number of calls, call lengths, number of softer handovers, and RLM report period. AAL2sig is used for transmitting commands to set up and release AAL2 connections inside user plane virtual channel connections.
Iub signalling link dimensioning recommendations
The Iub signalling amounts depend on the BTS configurations (cell amounts, RRI periods), subscriber amounts with related signalling as Location Area/Routing Area (LA/RA) update procedures and registrations, and subscriber traffic amounts as the number of call setups, handovers, and so on. During normal operation, the signalling link load should usually not exceed 80%. The estimated signalling bandwidth requirement for the Iub is that 6-7% of the Iub capacity has to be reserved for signalling. The signalling bandwidth division between the CNBAP, DNBAP, and AAL2Sig should be done in the ratios of 1:2:1. With multiple WAM sites, the DNBAP bandwidth is divided according to the WSP unit capacities configured behind each WAM. Without advanced AAL2 multiplexing (AXUA) and multiple WAM sites, the AAL2sig bandwidth is divided according to the Wideband Signalling Process (WSP) unit capacities configured behind each WAM. The minimum link size for the CNBAP, DNBAP, and AAL2Sig is 39 cps. The maximum size is 2100 cps per WAM. From the operating networks, the CNBAP load can be estimated by:
CNBAP Load [cps] = 3 + RL_Setups / s * RL_Setup_Resp_Msg_Size + RRI_Msg_Size/ RR_Ind_Period

where:
DN70118376 Issue 2-0 en 18/06/2007
103 (113)
RL_Setups/s is the number of the Radio Link Setups per second. RL_Setup_Resp_Msg_Size is the size of the RL Setup Response message in ATM cells. It can be estimated to be 2 ATM cells. RRI_Msg_Size is the Radio Resource Indication Message Size. It can be estimated to be 4 ATM cells for 1-3 WCDMA cells. RR_Ind_Period is the reporting period of the Radio Resource Indication messages. The default value is 200 ms.
For the DNBAP, the required bandwidth depends on the number of simultaneous PS calls. Approximately 13 cps is needed for each PS call. Depending on the traffic mix, these values for DNBAP can exceed the values achieved by the basic 6-7% rule with 1:2:1 division.
Table 28.
Bandwidth needed for DNBAP cps needed

260 520 760 1010 1260
Number of PS calls
20 40 60 80 100
9.1.7
Examples of Iub configurations

1+1+1 BTS, 2*WSPC, 1*WAM, 1*E1
Max. users/BTS Num cells/BTS Link capacities CNBAP DNBAP AAL2Sig Sum cps Kbps 80 3 cps 78 150 78 306 129.7 6.8% of Iub
The capacity of E1 is ~80 AMR calls.
104 (113)
DN70118376 Issue 2-0 en 18/06/2007
1+1+1 BTS with BTS AAL2 multiplexing, 3*WSPC, 2*WAM, 2*E1

Max. users/BTS Num cells/BTS Link capacities CNBAP DNBAP AAL2Sig Sum cps Kbps 160 3 cps 150 300 150 600 254.4 6.9% of Iub
The capacity of 2*E1 is ~160 AMR calls. The DNBAP has to be configured as 200+100 cps links.
9.1.8
Interface capacity
The following table presents the Iub physical interface types. Cell rate means the available VCC size of the interface expressed as ATM cells/ second. With n*E1, n* VC-12, and n*JT1, the Inverse Multiplexing ATM (IMA) parameter has an effect on the transfer bit rates. The cell rates correspond to the default IMA parameter value 128.
Table 29.
Iub interface types Nominal bit rate Mbit/s

1,544 2,048 n*1,544 n*2,048 155,52 155,52 155,52
Iub interface type

JT1, T1 E1, ATM VC n*JT1, n*T1 n * E1 IMA, ATM VC STM1, ATM VC4, OC3 STM1, ATM n*VC12 STM1, ATM n*VC12 IMA
Transfer Bit Rate Cell rate cps Mbit/s

1,536 1,920 n*1,487274 n*1,904070 149,76 n*1,920 n*1,904070 3622 4528 n*3592 n*4490 353207 n*4528 n* 4490
DN70118376 Issue 2-0 en 18/06/2007
105 (113)
9.1.9
BTS internal link configurations

In RAS05.1, the AXC ATM layer configuration management for BTS function makes the BTS internal VCC configuration between WAM-AXU automatic. In other words, the BTS internal VCCs do not need to be dimensioned any more. Only Iub VCCs need to be commissioned.
9.2
HSDPA and Iub dimensioning

HSDPA protocol stack is presented in the following figure.
NRT source TCP IP RNC PDCP RLC MAC-d FP AAL2 ATM FP AAL2 ATM BTS MAC-hs PHY
Destination TCP IP PDCP RLC MAC-d MAC-hs PHY
Figure 34.
HSDPA protocol stack
The following overheads are present below the PDCP level:

.
RLC: PDU size 320 bits payload + 16 bits header = 336 bits, overhead is 16/320 = 5%. Dedicated Medium Access Control (MAC-d): No header. FP: HS-DSCH data frames FP-header and tail produces nine bytes overhead and each MAC-d Protocol Data Unit (PDU) produces one padding byte overhead. There can be 1 34 PDUs in the HS-DSCH frame. Thus, the FP overhead varies between 3 19%. For example, for 10 PDUs in a frame the FP overhead is 9 + 10 = 19 bytes = 152 bits, and 152 / 3360 = 4.5%. FP data rate = 100*3512 = 351 kbps.
106 (113)
DN70118376 Issue 2-0 en 18/06/2007
Table 30.
HSDPA Protocol overheads RLC

Payload Mbps
MAC
+ RLC headers Mbps 1.68 3.53
FP rate (Iub)
Payload + RLC headers + FP Mbps 1.756 3.65
RAS05 RAS05.1
1.6 3.36
The total Iub overhead requirements for HSDPA are 10% overhead from RLC rate to FP rate, or 30% overhead from RLC rate to ATM rate. Additionally, 0-25% overhead is required on the Iub so that it does not limit the rates and the full rates over the air interface can be achieved. This additional overhead depends on whether high utilisation of the air interface or the Iub interface is preferred, as the simulation results in the following table indicate.
Table 31.
HSDPA Iub overhead versus HSDPA RF capacity

85% 0% 90% 15% 95% 25%
Relative HSDPA capacity compared to the maximal Additional Iub margin over average capacity
For information on HSPA rates, see Table HSPA rates in Dimensioning RNC.
9.3
Dimensioning Iur interface

Purpose
Iur is the interface between two RNCs. Iur carries traffic and signalling that is generated when a mobile station is in soft handover state and attached to two base stations that belong to different RNCs. This procedure describes the dimensioning of the Iur interface, in other words, how to calculate the needed capacity for the interface. For more information on Iur, see Iur interface in WCDMA RAN Interfaces.
DN70118376 Issue 2-0 en 18/06/2007
107 (113)
Before you start
Traffic calculations have been completed and thus the number of RNCs is known. For RNC throughput based dimensioning, the Iur traffic has to be considered as part of Iub traffic. For Iur dimensioning, check:
.
number of RNCs RNC area border traffic between RNCs
Steps
1. Dimension the Iur interface. The following figure explains the generic method for dimensioning the Iur interface.
Total user traffic in the area
Iub traffic per RNC
Iur traffic per RNC
Nokia assumption is that Iur traffic is 4-9 % of the Iu traffic.
Iurs per RNC
From NW topology the number of adjacent RNCs needs to be considered. From the traffic model the simultaneous traffic mixes can be determined.
Voice erlangs
CS-data erlangs
PS Data
Iur VCC size and amounts
When determining the VCC size the maximum bitrate for each service need to be considered.
Figure 35.
Iur dimensioning
108 (113)
DN70118376 Issue 2-0 en 18/06/2007
Iur traffic amounts between RNCs depend on the network configuration and topology. Typically, Iur traffic amounts could be in the range of 4 9 % of Iu traffic, but the actual values should be checked according to the radio network plan. The recommended way for Iur dimensioning is to use a minimum of 1xE1 per E1 and, within this, a maximum of 4377 cps for user traffic (and the rest for signalling).
Expected outcome
The capacities of Iur connections have been calculated successfully.
9.4
Dimensioning Iu-CS interface

Purpose
The purpose of dimensioning the Iu-CS interface is to calculate the needed capacity for the interface. The Iu-CS is the interface between the RNC and the 3G MSC and/or 3G SGSN. For more information on the interface, see Iu-CS interface in WCDMA RAN Interfaces.
Before you start
Make sure that the traffic calculations have been completed and the number of the RNCs is known. Check the following:
.
RNC area (covered number of subscribers and mix of traffic classes and usage).
Based on the total CS side traffic and number of RNCs, the required Iu-CS traffic can be determined assuming that the Iu-CS side traffic is equally divided between the RNCs. Therefore, the Iu-CS traffic can be calculated as follows:
DN70118376 Issue 2-0 en 18/06/2007
109 (113)
Total user traffic in the area

User traffic per RNC - total traffic/amount of RNCs
User traffic per RNC
Voice erlangs
CS-data erlangs
Iu VCC size and amounts
Voice erlangs CS data erlangs - Assuming 12.2 AMR mode and - CS data divided into erlangs by each service bit rates
Figure 36.
Iu-CS dimensioning
The actual VCC sizes must be determined by using the Nokia RAN Capacity Planner or by checking the recommended values for the certain call mixes from the RAN configurations. For more information, see Introduction to Nokia RAN configurations in Configuring WCDMA RAN. Example As a simplified example, VCC with 9000 cps can support 248 AMR calls or 49 CS 64 calls.
Steps
1. 2. 3. Calculate the total CS traffic in Erlangs in the RNC area. Calculate the total CS traffic in Mbps in the RNC area. Calculate the required transport network capacity for CS traffic.
Expected outcome
The number and capacities of Iu-CS links have been calculated.
110 (113)
DN70118376 Issue 2-0 en 18/06/2007
9.5
Dimensioning Iu-PS interface

Purpose
The purpose of dimensioning the Iu-PS interface is to calculate the capacity needed for it. Iu-PS is the interface between the RNC and 3G MSC and/or 3G-SGSN. For more information, see Iu-PS interface in WCDMA RAN Interfaces. For accurate dimensioning, perform Iu-PS dimensioning with the NetAct Transmission Planner.
Before you start
The traffic calculations have been completed and the number of RNCs is known. Estimate the average size of the packet in order to calculate the amount of overhead. For Iu-PS dimensioning, check:
.
RNC area (covered number of subscribers and mix of traffic classes and usage).
Steps
1. 2. Calculate the total PS traffic amount in Mbps from the RNC area. Calculate the required Iu-PS bandwith in Mbps. The amount of overhead depends on the length of the IP packet. The longer the packet is, the smaller the relative amount of overhead. You have to assume some packet length for dimensioning purposes. Nokia's recommendation is to use Unspecified Bit Rate (UBR) VCCs in Iu-PS side where a single VCC is created in each GPRS Tunnelling Protocol-User Plane (GTPU). As the Iu-PS interface is implemented by AAL5, it does not affect the user plane AAL2 connectivity dimensioning.
Expected outcome
The capacity needed for the Iu-PS interface has been calculated.
DN70118376 Issue 2-0 en 18/06/2007
111 (113)
9.6
Dimensioning Iu-BC interface

Purpose
The purpose of dimensioning the Iu-BC interface is to calculate the required capacity between the RNC and the Cell Broadcast Center (CBC). For more information on the interface, see Iu-BC interface in WCDMA RAN Interfaces.
Steps
1. Dimension the Iu-BC interface. Iu-BC interface recommendation is 64 kbps for each Iu-BC link between the CBC and the RNC.
9.7
Iu and Iur MTP3 links

The current dimensioning rules recommend that the Iu Radio Access Network Application Part (RANAP) signalling is 6% of the user planes. This can be used as a guideline and a dimensioning rule, but to simplify the rules, the following guidelines are recommended in RAS06:
Table 32. Erlangs

1000 3000 5000 7000 9000 11000
Iu-CS MTP3 dimensioning Needed BW (cps)

2000 4000 6000 8000 10000 12000
Number of links
2 4 6 8 10 12
Link size (cps)

1000 1000 1000 1000 1000 1000
112 (113)
DN70118376 Issue 2-0 en 18/06/2007
Table 33. User plane BW
Iu-PS MTP3 dimensioning Needed BW

(CPS) 2000 4000 6000 8000 14000 20000
Number of links
#
Iu-PS
link size (CPS) 1000 1000 1000 1000 1000 1300
85 122 159 196 300 450
2 4 6 8 14 16
For the Iur interface, the recommendation is 64 kbit/s, that is, 150 cps link for each Iur connection between two RNCs. For instructions, see:
.
Dimensioning Iub interface Dimensioning Iu-CS interface Dimensioning Iu-PS interface Dimensioning Iur interface Dimensioning Iu-BC interface
See also Iur interface in WCDMA RAN Interfaces.
DN70118376 Issue 2-0 en 18/06/2007
113 (113)

Dimension Ing Wcdma Ran

Uploaded by

Document Information

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

Dimension Ing Wcdma Ran

Uploaded by

Copyright:

Available Formats

RNC3267_trial Nokia WCDMA RAN, Rel. RAS06, System Library, v.

Dimensioning WCDMA RAN

DN70118376 Issue 2-0 en 18/06/2007

# Nokia Siemens Networks

Dimensioning WCDMA RAN

# Nokia Siemens Networks

DN70118376 Issue 2-0 en 18/06/2007

DN70118376 Issue 2-0 en 18/06/2007

# Nokia Siemens Networks

Dimensioning WCDMA RAN

# Nokia Siemens Networks

DN70118376 Issue 2-0 en 18/06/2007

Dimensioning Air interface:

R99 DCH dimensioning:

DN70118376 Issue 2-0 en 18/06/2007

# Nokia Siemens Networks

Dimensioning WCDMA RAN

Table 1. Changed chapter

Modified chapters in Dimensioning WCDMA RAN in issue 1-3 See

Changes between issues 1-1 and 1-2

Table 2. Changed chapter

Modified chapters in Dimensioning WCDMA RAN in issue 1-2 See

Dimensioning BTS Dimensioning interfaces

HSDPA and BTS dimensioning Dimensioning Iub interface

# Nokia Siemens Networks

DN70118376 Issue 2-0 en 18/06/2007

Introduction to dimensioning WCDMA RAN

Introduction to dimensioning WCDMA RAN

DN70118376 Issue 2-0 en 18/06/2007

# Nokia Siemens Networks

Dimensioning WCDMA RAN

The basic parameters for dimensioning are the following:

# Nokia Siemens Networks

DN70118376 Issue 2-0 en 18/06/2007

Introduction to dimensioning WCDMA RAN

A rough estimate of the required sites and network elements:

base stations base station configurations RNCs

and requirements and strategy for:

For further information, see Dimensioning transport network. See also:

DN70118376 Issue 2-0 en 18/06/2007

# Nokia Siemens Networks

Dimensioning WCDMA RAN

# Nokia Siemens Networks

DN70118376 Issue 2-0 en 18/06/2007

Dimensioning Air interface

Dimensioning Air interface

Area types Antenna gains

Coverage targets Fading margins

Load Factor Calculation

Link Budget Calculation

Cell Range Calculation

Allowed blocking/ queuing

BTS dimensioning flow

DN70118376 Issue 2-0 en 18/06/2007

# Nokia Siemens Networks

Dimensioning WCDMA RAN

# Nokia Siemens Networks

DN70118376 Issue 2-0 en 18/06/2007

Dimensioning Air interface

Air interface dimensioning, shared carrier DCH + HSPA

Additional capacity Node Bs HSDPA capacity dimensioning

Input: available HSDPA capacity UL/DL Load, Node B DL power

Output: HSDPA throughput

R99 capacity dimensioning