Dimension Ing Wcdma Ran

download Dimension Ing Wcdma Ran

of 113

description

wcdma

Transcript of Dimension Ing Wcdma Ran

  • Dimensioning WCDMA RAN

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 1 (113)

    RNC3267_trialNokia WCDMA RAN, Rel. RAS06, SystemLibrary, v. 1

  • The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

    The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given as is and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

    Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

    This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

    The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia 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) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Contents

    Contents 3

    Summary of changes 5

    1 Introduction to dimensioning WCDMA RAN 7

    2 Dimensioning Air interface 11

    3 R99 DCH dimensioning 153.1 Intoduction to R99 DCH dimensioning 153.2 R99 DCH coverage dimensioning 173.2.1 Uplink link budget 173.2.2 Downlink link budget 223.2.3 Cell range and coverage 263.3 R99 DCH capacity dimensioning 283.3.1 Load calculation based on traffic inputs 283.3.2 DL power calculation vs. load 30

    4 HSDPA dimensioning 334.1 Introduction to HSDPA dimensioning 334.1.1 HSDPA features in RAS06 354.1.2 Supporting R99 formulas 364.2 HSDPA coverage dimensioning 364.2.1 Uplink link budget 364.2.2 Downlink link budget 374.2.3 Cell range and coverage 414.3 HSDPA capacity dimensioning 42

    5 HSUPA dimensioning 455.1 Introduction to HSUPA dimensioning 455.1.1 HSUPA features in RAS06 475.1.2 Supporting R99 formulas 485.2 HSUPA coverage dimensioning 485.2.1 Uplink link budget 485.2.2 Downlink link budget 525.2.3 Cell range and coverage 525.3 HSUPA capacity dimensioning 53

    6 Dimensioning transport network 57

    7 Dimensioning BTS 617.1 Dimensioning Flexi WCDMA BTS 617.1.1 Capacity 627.1.2 Baseband capacity and HSDPA 637.1.3 Capacity licenses 647.1.4 Flexi WCDMA BTS and transmission 657.2 Dimensioning UltraSite WCDMA BTS 657.2.1 WSPA/C processing capacity 67

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 3 (113)

    Contents

  • 7.2.2 UltraSite WCDMA BTS baseband capacity and HSDPA 687.2.3 Dimensioning steps 697.2.4 HSPA sharing 717.3 HSDPA and BTS dimensioning 727.3.1 Tcell grouping 747.4 HSUPA and BTS dimensioning 757.5 Extended Cell 777.6 BTS counters 787.7 WCDMA BTS capacity allocation principles 797.7.1 UltraSite WCDMA BTS 797.7.1.1 Primary/Secondary WAM 807.7.1.2 Master/Slave WAM 807.7.1.3 WSP and WAM allocation within a subrack 817.7.1.4 Common Control Channel (CCCH) allocation 827.7.1.5 Dedicated Channel (DCH) allocation 847.7.1.6 Recovery actions 887.7.1.7 HSDPA 897.7.2 Flexi WCDMA BTS 94

    8 Dimensioning RNC 95

    9 Dimensioning interfaces 979.1 Dimensioning Iub interface 979.1.1 Transport Bearer Tuning 979.1.2 Hybrid transport 989.1.3 Iub VCC configuration 989.1.4 Protocol overheads 1019.1.5 Connection Admission Control 1029.1.6 Iub signalling links 1029.1.7 Examples of Iub configurations 1049.1.8 Interface capacity 1059.1.9 BTS internal link configurations 1069.2 HSDPA and Iub dimensioning 1069.3 Dimensioning Iur interface 1079.4 Dimensioning Iu-CS interface 1099.5 Dimensioning Iu-PS interface 1119.6 Dimensioning Iu-BC interface 1129.7 Iu and Iur MTP3 links 112

    4 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Summary of changes

    Changes between document issues are cumulative. Therefore, the latestdocument 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 DCHdimensioning, HSDPA dimensioning and HSUPA dimensioning.

    R99 DCH dimensioning:

    This is a new section.

    HSDPA dimensioning:

    This is a new section.

    HSUPA dimensioning.

    This is a new section.

    Dimensioning BTS:

    Sections Dimensioning Flexi WCDMA BTS, Dimensioning UltraSiteWCDMA BTS and HSDPA and BTS dimensioning have been updated.New sections HSUPA and BTS dimensioning, Extended Cell and BTScounters have been added.

    Dimensioning RNC:

    RNC-related dimensioning information has been updated to RAS06 level.

    Dimensioning interfaces:

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 5 (113)

    Summary of changes

  • Sections Dimensioning Iub interface and Iu and Iur MTP3 links have beenupdated.

    Changes between issues 1-2 and 1-3

    Table 1. Modified chapters in Dimensioning WCDMA RAN in issue 1-3

    Changed chapter Impact See

    Dimensioning BTS The number of cells handled byone WSPC has been corrected.

    Dimensioning UltraSite BTS

    Dimensioning interfaces The steps of Iu-PS dimensioninghave been simplified.

    Dimensioning Iu-PS interface

    RAN features anddimensioning

    A reference has been corrected. RAN features and dimensioning

    Changes between issues 1-1 and 1-2

    Table 2. Modified chapters in Dimensioning WCDMA RAN in issue 1-2

    Changed chapter Impact See

    Dimensioning BTS Information on the basebandExtension Module has beenadded. Carrier configurations havebeen updated.

    Flexi BTS

    Dimensioning BTS The number of cells and users forFlexi BTS have been updated.

    HSDPA and BTS dimensioning

    Dimensioning interfaces Information on the maximum sizeof AAL2 Path has been added.

    Dimensioning Iub interface

    6 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 1 Introduction to dimensioning WCDMARAN

    Purpose

    Dimensioning is the initial phase of network planning. Duringdimensioning, the first configuration estimates and requirements forcoverage, capacity and quality of service are planned. The approximatenumber of necessary base station sites and base stations, the averagevalues for the power budget, cell size, capacity, and initial networkconfiguration are estimated at this phase. The capacity requirements andthe overall quality of service targets determine the selection of the RANtransport network and the transport interfaces of base stations and RNCGSM operators can use dimensioning to estimate the service capability ofthe existing network in case of site reuse.

    Note that in the dimensioning phase, only average values for the networkcan be calculated. More exact values for individual sites are calculated inthe actual planning phase.

    The dimensioning instructions given in this document apply to RAS06system release, consisting of Nokia WCDMA BTS release WBTS4.0 andNokia WCDMA RNC release RN3.0.

    Before you start

    Check:

    . Traffic expectations. An accurate traffic forecast is important innetwork dimensioning. Deviations must be taken into account incapacity planning.

    . Population density in the area. Specify areas of population thatshould be covered in each phase of roll-out.

    . Location probability. Specify system area availability indoors/outdoors.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 7 (113)

    Introduction to dimensioning WCDMA RAN

  • . Regulations, for example, spectrum allocations (FDD/TDD andlicenced/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 probabilityper 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 afunction of time

    . radio network area information: the total area, division into differentsub-areas or area types, and the user distribution for each sub-area

    Summary

    Radio network dimensioning activities include coverage, capacity, andquality of service analysis. The results of this analysis are the main inputfor the dimensioning of the transport network.

    Steps

    1. Estimate coverage.

    a. The coverage efficiency of WCDMA is defined by the averagecoverage area per site, for a predefined propagationenvironment, 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 anarea, for example an airport or an industrial area.

    2. Estimate capacity.

    a. Check the frequency range and the amount of spectrum thatcan be used.

    b. Estimate the amount of supported traffic per base station site.

    3. Estimate quality of service.

    8 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Consider blocking and location probability. Typical values are 2%and 95% respectively. Location probability varies for differentservices according to the required data rates. For example, thelocation probability for a service that requires faster data rates maybe 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 ConfiguringWCDMA RAN

    . Introduction to Nokia RAN configurations in Configuring WCDMARAN

    For instructions, see Planning radio network in Planning WCDMA RANand Optimising and expanding WCDMA RAN in Optimising WCDMA RAN.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 9 (113)

    Introduction to dimensioning WCDMA RAN

  • 10 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 2 Dimensioning Air interfaceThe air interface dimensioning is based on the predicted subscriberdensity (subscribers/km2), subscriber traffic profiles, propagationenvironment, and Quality of Service (QoS) targets. With Wideband CodeDivision Multiple Access (WCDMA), the dimensioning has to be doneiteratively, considering the air interface load and cell range coupling. Theiteration steps are presented in Figure BTS dimensioning flow. Thecalculations are based on the basic WCDMA formulas, propagationmodels, and statistical analysis. In practice, the dimensioning is done withnetwork dimensioning or planning tools (such as NetDim or NetActPlanner, see NetAct Planner documentation).

    Figure 1. BTS dimensioning flow

    CapacityRequirement

    Link BudgetCalculation

    Area typesAntenna gains

    Subscribers/kmTraffic/Subscribe

    2

    Load FactorCalculation

    EquipmentRequirement

    Cell RangeCalculation

    Coverage targetsFading margins

    Allowed blocking/queuing

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 11 (113)

    Dimensioning Air interface

  • For more information on dimensioning Air interface, see Introduction toR99 DCH dimensioning, Introduction to HSDPA dimensioning andIntroduction to HSUPA dimensioning.

    See also Introduction to Nokia RAN configurations in Configuring WCDMARAN.

    Air interface dimensioning in RAS06 increases in complexity with theintroduction of HSUPA. HSUPA causes some changes into thedimensioning methodology, as RF resources have to be shared with R99users (using DCH bearers). As both HSDPA and HSUPA (HSUPA worksonly with HSDPA) are optional features, dimensioning can be separated inthree 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 mostcomplex. This is due to the fact that R99 DCH traffic influences all otherfeatures, HSDPA and HSUPA.

    12 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 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 WB-AMR 6.6 - 12.65 kbps. For MultiRAB calls, CE consumption iscalculated by adding together the individual RAB CE needs.

    Table 3. CE consumption examples

    CE for single RAB

    Uplink Downlink

    AMR 4.75-12.2 kbps, WB-AMR 6.6-12.65 kbps

    1 1

    PS 64 / 384 kbps 4 16

    PS 128 / 384 kbps 4 16

    PS 384 / 384 kbps 16 16

    Air interface dimensioning,shared carrier DCH + HSPA

    Coverage dimensioningselection:

    - Link Budget R99(based on service)- Link Budget HSDPA(based on cell edgethroughput)- Link Budget HSUPA(based on cell edgethroughput)- Output # of coverage sites

    R99 capacitydimensioning

    Resultevaluation

    CECalculation

    HSDPA capacitydimensioning

    HSUPA capacitydimensioning

    Iu-bDimensioning

    RNCDimensioning

    Additionalcapacity Node Bs

    Dimensioning inputs and requirements

    Coverage dimensioning Capacity dimensioning

    Input: availableHSUPA capacity

    Output: HSUPAthroughput

    OK

    Not OK

    UL/DL Load,Node B DL power

    Output: HSDPAthroughput

    Input: availableHSDPA capacity

    # ofNode Bs

    (coverage +capacity)

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 13 (113)

    Dimensioning Air interface

  • DCH traffic load has to be taken into account in capacity dimensioning ofHSDPA in downlink and HSUPA in uplink. This sets some challenges onestimating the capacity available for different services, especially HSPAservices. Overall, dimensioning can be based on different starting points,such as having the coverage dimensioning for HSUPA 64 kbps or forHSDPA cell edge throughput of 128 kbps. Similarly, capacity dimensioningcan be based on DCH load estimation or HSUPA/HSDPA cell averagethroughput.

    Additionally, as there are more WCDMA frequencies available, theoperating frequency can have a high influence on the dimensioningparameters. 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.7dB/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 rangecalculations.

    For more detailed information on the dimensioning of R99 DCH, HSDPAand HSUPA, see Introduction to R99 DCH dimensioning, Introduction toHSDPA dimensioning and Introduction to HSUPA dimensioning.

    For more information on HSDPA and HSUPA, see High-speed packetaccess (HSPA) in HSPA Overview .

    14 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 3 R99 DCH dimensioning3.1 Intoduction to R99 DCH dimensioning

    R99 dedicated traffic channel (DCH) dimensioning has to be noted also inHSPA dimensioning. In case of shared DCH + HSPA, the R99 DCH trafficaffects both HSDPA and HSUPA capacity as well as coverage.

    The general R99 dimensioning process is shown in Figure R99dimensioning flow.

    Figure 3. R99 dimensioning flow

    The figure shows the basic parts of the dimensioning flow, including inputs:

    Air interface dimensioning,only DCH carrier

    Coverage dimensioningselection:

    - Link Budget R99(based on service)- Output # of coverage sites

    R99 capacitydimensioning

    Resultevaluation

    CECalculation

    Iu-bDimensioning

    RNCDimensioning

    Additionalcapacity Node Bs

    Dimensioning inputs and requirements

    Coverage dimensioning Capacity dimensioning

    OK

    Not OK

    # ofNode Bs

    (coverage +capacity)

    Input:available capacity

    Output:R99 UL/DL load

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 15 (113)

    R99 DCH dimensioning

  • . 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 selectedcoverage limiting service.

    For more information, see R99 DCH coverage dimensioning.

    2. Capacity dimensioning

    . Estimate and calculate the traffic and capacity demand based ontraffic and subscriber profile inputs.

    . Compare the capacity need with the number of coverage sitesoffered capacity.

    . If R99 capacity is not enough, you can add new Node Bs forcapacity, tune the parameters in link budget or capacity-relatedfeature 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) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 3.2 R99 DCH coverage dimensioning

    R99 DCH coverage dimensioning includes uplink link budget, downlinklink 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 maximumpath loss. Table Example of R99 UL DCH link budget shows the basic linkbudget for R99 UL DCH.

    Table 4. Example of R99 UL DCH link budget

    Service Speech CD Data PS Data

    Service Rate (kbps) 12.2 64 64Transmitter - Handset

    Max Tx Power (dBm) 24 24 24Tx Antenna Gain (dBi) 0 0 0Body Loss (dB) 3 0 0EIRP (dBm) 21 24 24

    Receiver Node B

    Node B Noise Figure(dB)

    2

    Thermal Noise (dBm) -108Uplink Load (%) 50Interference Margin (dB) 3-0Interference Floor -103.0

    Service Eb/No (dB) 4.4 2 2Service PG (dB) 25.0 17.8 17.8Receiver Sensitivity (dB) -123.6 -118.8 -118.8Rx Antenna Gain (dBi) 18.0 18.0 18.0Cable Loss (dB) 0.5 0.5 0.5Benefit of using MHA(dB)

    0 0 0

    UL Fast Fade Margin(dB)

    1.8 1.8 1.8

    UL Soft Handover Gain(dB)

    1.5 1.5 1.5

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 17 (113)

    R99 DCH dimensioning

  • Table 4. Example of R99 UL DCH link budget (cont.)

    Service Speech CD Data PS Data

    Gain against shadowing(dB)

    2.5 2.5 2.5

    Building PenetrationLoss (dB)

    12 12 12

    Indoor Location Prob.(%)

    90 90 90

    Indoor Standard Dev.(dB)

    10 10 10

    Shadowing margin (dB) 7.8 7.8 7.8Isotropic PowerRequired (dB)

    -123.5 -118.7 -118.7

    Allowed Prop. Loss(dB) 144.5 142.7 142.7

    UL PS services can have also other bit rates, for example 128 and 384kbps. Usually the coverage dimensioning is still made with 64 kbps CS orPS.

    Defining uplink link budget

    1. Define the service parameters.. Service bit rate

    The bit rate depends on service, which can vary in speechservice bit rates (for example, 4.75, 5.9, 7.95, 12.2 kbps) topacket service bit rates (for example, 64, 128 and 384 kbps) aswell as video service (for example, 64 kbps).

    . Service Processing Gain

    High processing gains correspond to services with low bitrates. These services tend to have more relaxed link budgetsand generate smaller increments in cell loading.

    . Service Eb/No. Eb/No value varies between services and alsobetween selected propagation channels. The following tableshows the recommended Eb/No values for commonly usedservices in dimensioning.

    Service Processing Gain = 10 * LOGChip Rate

    Bit Rate

    18 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Table 5. Eb/No values for network dimensioning

    Eb/No [dB] Speech 64 kbps 128 kbps 384 kbps

    Uplink

    3 km/h, macrocell

    4.4 2 1.4 1.7

    120 km/h, macrocell

    5.4 2.9 2.4 2.9

    Downlink

    3 km/h, macrocell

    7.9 5 4.7 4.8

    120 km/h, macrocell

    7.4 4.5 4.2 4.3

    Eb/Nos for lower and wideband AMR codecs and for lower PSdata services can be derived from the values (3 km/h) shownabove. See Table Eb/No values for lower and wideband AMRcodecs and lower PS data services.

    Table 6. Eb/No values for lower and wideband AMR codecs and lower PSdata services

    Narrowband AMR Wideband AMR Lower PS

    Bit rate(kbps)

    4.75 5.9 7.95 6.65 8.85 12.65 8 16 32

    Uplink Eb/No [dB]

    6.4 5.8 5.2 5.5 5.0 4.3 3.9 2.5 2.2

    DownlinkEb/No [dB]

    9.4 9.0 8.5 8.8 8.3 7.9 5.4 5.4 5.7

    2. Define parameters for the UE.. UE max power and antenna gain

    UE transmit power is dependent on the mobile type andusually varies between 21 and 24 dBm. Similarly, the antennagain varies from 0 dBi mobile terminals to 2 dBi data cards.

    . Body lossBody loss depends on service. Commonly during the calls themobile is located near the ear, and 3 dB body loss is noticed.

    . EIRP

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 19 (113)

    R99 DCH dimensioning

  • EIRP represents the effective isotropic radiated power fromthe transmit antenna. In uplink it is computed from thefollowing 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.8dB according to the frequency.

    . Antenna gainAntenna gain varies from sectorised to omni antennas. Theantenna gain can be seen from antenna data sheet.

    . Cable loss and Mast Head AmplifierCable loss can be assumed to be from 0.5 to 3 dB; in case ofFlexi WCDMA BTS the cable loss can be as low as 0.5 dB.When using MHA, the cable loss is compensated and thebenefit from MHA is the same as the assumed cable loss.

    4. 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:

    ul Uplink load factor. Generally uplink load of 0.5 0.7 is used in dimensioning.

    N Number of usersVj L1 activity factor of user j (0.67 for voice UL,

    0.63 for voice DL, 1.0 for data)Eb/Noj Received energy per bit-to-noise density ratio

    (Eb/No) of user jW WCDMA chip rate; 3.84 Mcps/s

    =UL

    Eb / Noj

    W / Rjv j

    j=1

    j=N

    * (1+ a * i)

    20 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Rj Data rate of user jA Power rise of user j due to power control,

    depending on UE speedi Ratio of other to own cell interference. In

    uplink, the value depends on the BTSsectorisation:Micro cell : Omni: 25% - 55%Macro cell: Omni: 55%, 2-sector: 55%, 3-sector: 65%, 4-sector: 75%, 6-sector: 85%

    It is recommended to use the maximum uplink load of 0.50.7, evenif in the initial phase of the network the subscriber traffic would notgenerate as much load. This is to avoid a situation where slightincreases in the traffic amounts may cause shrinkage of thecoverage areas. In rural areas, where major traffic is not expected, alower uplink load value may be used.

    Calculate interference margin. This is calculated from the load factor.

    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 theequation:

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

    Interference_margin= -10 * LOG 1-TARGET_LOAD

    100

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 21 (113)

    R99 DCH dimensioning

  • 9. Define clutter-related parameters.

    As shown in the example link budget, the maximum allowedpropagation loss calculation includes also a definition of indoorlosses and margins. Additionally, coverage can also be calculatedfor in-car and outdoor, but most commonly coverage should becalculated 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 thebuilding penetration loss and indoor standard deviation, as well asreceiver sensitivity and additional margins.

    Isotropic power required = Receiver sensitivity - RxAntennaGain +cable loss - MHA gain + UL fast fade margin Gain againstshadowing 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 servicemaximum path loss. Table Example of R99 DL DCH link budget shows thebasic link budget for R99 DL DCH.

    Table 7. Example of R99 DL DCH link budget

    Service Speech CD Data PS Data PS Data PS Data

    Service Rate (kbps) 12.2 64 64 128 384Transmitter - Node B

    Max Tx Power Total(dBm)

    43

    Max Tx Power (perRadiolink) (dBm)

    34.2 37.2 37.2 38.0 38.0

    Cable Loss (dB) 0.5 0.5 0.5 0.5 0.5MHA Insertion Loss 0 0 0 0 0

    Tx Antenna Gain (dBi) 18 18 18 18 18

    22 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Table 7. Example of R99 DL DCH link budget (cont.)

    Service Speech CD Data PS Data PS Data PS Data

    EIRP (dBm) 51.7 54.7 54.7 55.5 55.5Receiver Handset

    Handset Noise Figure(dB)

    7

    Thermal Noise (dBm) -108Downlink Load (%) 80Interference Margin (dB) 7.0Interference Floor (dBm) -94.0Service Eb/No (dB) 7.9 5 5 4.7 4.8Service PG (dB) 25.0 17.8 17.8 14.8 10.0Receiver Sensitivity(dBm)

    -111.1 -106.8 -106.8 -104.1 -99.2

    Rx Antenna Gain (dBi) 0 0 0 0 0Body Loss (dB) 3 0 0 0 0DL Fast Fade Margin(dB)

    0 0 0 0 0

    DL Soft Handover Gain(dB)

    2.5 2.5 2.5 2.5 2.5

    Gain against shadowing 2.5 2.5 2.5 2.5 2.5

    Building PenetrationLoss (dB)

    12 12 12 12 12

    Indoor Location Prob.(%)

    90 90 90 90 90

    Indoor Standard Dev.(dB)

    10 10 10 10 10

    Shadowing margin (dB) 7.8 7.8 7.8 7.8 7.8Isotropic PowerRequired (dB)

    -93.3 -92.0 -92.0 -89.3 -84.4

    Allowed Prop. Loss (dB) 145.0 146.7 146.7 144.8 139.9

    Commonly the service coverage is made based on the UL link budget, butit is good to verify the coverage also for downlink service.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 23 (113)

    R99 DCH dimensioning

  • Defining downlink link budget

    The parameter definition for downlink link budget is mostly the same as forR99 uplink DCH link budget, but with the some differences as describedhere.

    1. Define service parameters.

    Use downlink Eb/No values in Table Eb/No values for networkdimensioning 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 BNoise Figure is not defined.. Max Tx Power per radiolink is calculated based on set of

    parameters separately for real -time (MaxRTDLPower) andnon-real-time services (MaxNRTDLPower). For information onthe parameters related to the calculation, see AdmissionControl. As an example, Table Example of DL link powersshows DL link powers for different services.

    Table 8. Example of DL link powers

    Speech service, kbps Packet services, kbps

    Bit rate 4.75 5.9 7.95 12.2 64 128 384

    Max DLlink power(dBm)

    32.3 32.7 33.2 34.2 37.8 40.0 40.0

    In this example, Max total TX power is 20 W, PtxDPCHmax is -3 dB, PtxPrimaryCPICH is 33 dBm, andCPICHtoRefRABOffset is 0 dB.

    . Downlink EIRPDownlink EIRP = MaxRT/NRT)DLpower -Cableloss -MHAinsertionloss + Transmit Antenna Gain

    4. Calculate or estimate downlink load factor using WCDMA downlinkload equation:

    24 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • DL Downlink load factor, generally downlink loadof 0.5 _ 0.8 is used in dimensioning

    N Number of usersVj 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 jW WCDMA chip rate; 3.84 Mcps/sRj 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. Thevalue depends on the BTS sectorisation:. Micro cell: Omni: 25% - 55%. Macro cell: Omni: 55%, 2-sector: 55%, 3-

    sector: 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 wouldnot generate as much load. This is to avoid a situation where slightincreases in traffic amounts may cause shrinkage of the coverageareas. In rural areas, where major traffic is not expected, lower uplinkload 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 followingequation. Use downlink Eb/No values.

    Receiver Sensitivity = Interference_floor + Required Eb/No -Processing Gain

    7. Define additional parameters.

    =DL

    Eb / NojW / R j

    vj

    j=1

    j=N

    * (1 - + i)(1 + SHO_OH) *

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 25 (113)

    R99 DCH dimensioning

  • . DL fast fading margin. In DL fast fade margin is assumed to be0 dB in the downlink direction as a result of the limiteddownlink transmit power control dynamic range.

    . Gain against shadowing. In R99 DL DCH, the recommendedvalue is 2.5 dB, which is used to determine the selectionpossibility of stronger cell in normal cell overlapping network

    . DL SHO gain represents a reduction in Eb/No requirementwhen the UE is in soft handover state. The recommended celledge value is 2.5 dB (in capacity calculation DL SHO gain is1.2 dB as an average over the cell, for UL SHO gain isneglected 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 iscalculated to take into account the building penetration loss andindoor standard deviation, as well as receiver sensitivity andadditional margins.

    Isotropic power required = Receiver sensitivity - RxAntennaGain +Body loss + DL fast fading margin DL SHO gain Gain againstshadowing + 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 toidentify the allowed propagation loss in indoor location.

    The cell range calculation can be calculated by using either uplink ordownlink path loss. Most commonly the uplink path loss is used tocalculate the coverage. But in network dimensioning, the link budgetcalculation has to be made for every service, and the limiting one has to beselected 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, inindoor, in-car or outdoor

    . building penetration loss, car penetration loss or outdoor when nopenetration loss

    26 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • . location probability

    . standard deviation

    . calculating the cell range by using propagation model like Okumura-Hata 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 anexample Dense urban (30 dB), Urban (0-3 dB) and Suburban (-5-8 dB).For example, in urban macro environment, Node B antenna height is30 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. Forsuburban we can assume clutter correction factor for example, 8 dBand 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:

    Figure 4. Node B sectorisation

    R

    OmniA = 2,6 R1

    R

    Bi-sectorA = 1,73 R2

    R

    R

    Tri-sectorA = 1,95 R3

    2 2 2

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 27 (113)

    R99 DCH dimensioning

  • 3.3 R99 DCH capacity dimensioning

    3.3.1 Load calculation based on traffic inputs

    To calculate whether the capacity of coverage Node Bs supports the trafficestimation, you should estimate the load factor from the traffic. Also the ULload factor has to be calculated, as HSUPA utilises the load which is leftfrom DCH traffic.

    To calculate the maximum number of simultaneous uplink/downlink usersin a cell, you can utilise the following method where the subscribers percarrier per cell are calculated from the total number of subscribers, thenumber of Node Bs and the configuration of those Node Bs. The equationused is as follows:

    Total traffic is calculated over the subscribers, and after that you cancalculate the needed traffic channels per cell.

    For voice and RT data services the traffic channel calculations are basedon the Erlang B formula and for NRT data services they are based onthroughput. 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 canvary from 20-40%.

    NRT data

    For NRT, the activity for downlink and uplink can be different, and the needfor traffic channels can vary. Commonly UL and DL traffic is 1:10.

    Uplink:

    Subscribers per carrier per cell =Total number of subscribers

    No. of Node B * No. of cells per Node B * No. of carriers per cell

    tchs =traffic

    throughput * R

    28 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Downlink:

    In the equation, R is the service bit rate. The throughput is assumed to be79%. This figure includes the L2 re-transmission overhead of 10% and15% of buffer headroom to avoid overflow (peak to average load ratioheadroom) => (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 fromthe UL and DL load formulas wherein noticing the SHO gain (also calledMDC gain) and the number of interfering channels. In UL/DL the gain isdue to soft handover which influences the Eb/No. The reduction in Eb/Nois 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:

    where

    . m is the number of interfering channels

    . Eb/No is the target energy per bit to interference spectral densityratio

    . W is the chip rate

    . R is the bit rate

    . SHOgain_UL is the average macro diversity gain on the UL due tosoft handover which reduces the Eb/No

    tchs =traffic

    throughput * R* (1+ Soft_HO_oh)

    fL_UL=m * (1+ i_UL*PowerRiseUL)

    W1 +

    R*10

    Eb / N0_BTS-SHOgain_UL

    10

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 29 (113)

    R99 DCH dimensioning

  • . PowerRiseUL is the average increase in transmit power due topower 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 allservice classes.

    Downlink fractional load formula

    The formula for downlink fractional load is as follows:

    where

    . m is the number of interfering channels

    . Eb/No is the target energy per bit to interference spectral densityratio

    . W is the chip rate

    . R is the bit rate

    . SHOgain_UL is the average macro diversity gain on the UL due tosoft 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 fractionalloads over all service classes.

    3.3.2 DL power calculation vs. load

    Node B has a maximum power from which it allocates for control channelsand traffic channels. If the load is higher, also the interference from thecontrol 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

    fL_DL=m * * (1 - Orth_DL + i_DL)

    W

    10

    Eb / N0_MS-SHOgain_DL

    10 * R

    30 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 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. Inthat case the formula is as follows:

    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.

    Ptot_tx=

    1- DL_DCH

    PCCH_tx+ PN * L P

    (Eb / No) jW / R j

    * Vj*j

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 31 (113)

    R99 DCH dimensioning

  • 32 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 4 HSDPA dimensioning4.1 Introduction to HSDPA dimensioning

    HSDPA downlink data is carried on a shared channel. For this reason,different variables have to be considered in HSDPA dimensioningcompared to NRT DCH data bearer dimensioning. The most importantdimensioning target for HSDPA is the average throughput. The achievedaverage throughput depends on the amount of power allocated forHSDPA.

    The aim of the HDSPA air interface dimensioning is to specify how muchpower should be allocated for HSDPA. HSDPA power should be enough toachieve HSDPA throughput targets, but on the other hand, enough powerresources should be reserved for the DCH traffic as well.

    If DCH load is high, the shared carrier HSDPA+DCH is not feasible to fullysupport the growing data traffic in HSDPA, especially now when HSUPAcreates even higher demand to support data traffic. In case of high DCHload, a dedicated carrier for HSPA (HSDPA + HSUPA) is needed. In thiscase the capacity of the carrier is allocated fully to HSDPA (see FigureOverall dimensioning process for dedicated HSPA carrier in Introduction toHSUPA dimensioning.

    Figure Dimensioning process with DCH + HSDPA (+ HSUPA) shows thedimensioning process with shared carrier, either with or without HSUPA .From HSDPA point of view, the process is the same.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 33 (113)

    HSDPA dimensioning

  • Figure 5. Dimensioning process with DCH + HSDPA (+ HSUPA)

    The dimensioning process of HSDPA is basically as in R99; the first step iscoverage dimensioning, followed by capacity dimensioning. However, theprocess differs in that capacity dimensioning has to include also the R99capacity estimation if shared carrier is in use.

    The steps for air interface HSDPA dimensioning are:

    Coverage dimensioning

    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 edgethroughput

    Air interface dimensioning,dedicated carrier HSPA

    Coverage dimensioningselection:

    - Link Budget UL R99(based on HSDPAassociated UL DPCHservice)- Link Budget HSDPA(based on cell edgethroughput)- Link Budget HSUPA(based on cell edgethroughput)- Output # of coverage sites UL DPCH capacity

    dimensioning

    Resultevaluation

    CECalculation

    HSDPA capacitydimensioning

    Iu-bDimensioning

    RNCDimensioning

    Additionalcapacity Node Bs

    Dimensioning inputs and requirements

    Coverage dimensioning Capacity dimensioning

    Input: capacityfor HSUPA

    Output:HSUPAthroughput

    OK

    Not OK

    Output:HSDPAthroughput

    Input:availablecapacity# of

    Node Bs(coverage +capacity)

    HSUPA capacitydimensioning

    Input:availablecapacity

    34 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Capacity dimensioning

    . Estimate and calculate R99 traffic and capacity demand based ontraffic 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 edgethroughput or utilise the existing R99 service link budget to definewhat kind of HSDPA throughput can be achieved at the cell edge

    . Calculating the average cell throughput based on power available forHSDPA

    . Identifying the Node B configuration required to achieve a specificthroughput performance

    For more information on HSDPA, see High-speed Downlink PacketAccess (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 forHSDPA

    . 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

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 35 (113)

    HSDPA dimensioning

  • 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 powergenerated by R99.

    The HSDPA capacity calculation takes into consideration the Node B TXpower used for R99 services. As noticed in the Dynamic ResourceAllocation feature, the rest of the power after DCH traffic, HSUPA controlchannels and common channels is used for HSDPA. This means that tofind how much the power is left for HSDPA, it is necessary to make the DLpower calculation vs. load. Based on this information, the availableHSDPA power can be used to determine the HSDPA capacity. This isneeded if HSDPA has a shared carrier with R99 traffic.

    4.2 HSDPA coverage dimensioning

    4.2.1 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 forassociated DPCH are 16, 64, 128 and 384 kbps.

    However, additional margin is required in the UL link budget to take intoaccount the power requirements of HS-DPCCH. HS-DPCCH carrieschannel quality information (CQI) reports and Ack/Nack feedback forHARQ.

    HS-DPCCH is power controlled relative to the every slot period in uplinkDPCCH. The power offset parameters (ACK; NACK; CQI) arecontrolled by the RNC and reported to the UE using higher layer signalling.The HS-DPCCH power offset must be increased, since the UL HS-DPCCH power control is sub-optimal for HSDPA users in soft handovermode (that is, active set size larger than one). It is possible that thedominant link in the active set is not the one belonging to the cell which iscurrently transmitting the HS-PDSCH to the user. However, using themaximum HS-DPCCH power offset of 6 dB is not sufficient to ensure good

    36 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • UL HS-DPCCH quality under all conditions, unless Ack/Nack repetition isused. The average overhead generated by HS-DPCCH depends on ACK/NACK and CQI activity. Link budgets consider peaks rather than theaverage overhead.

    Figure 6. HS-DPCCH power offset parameters

    The additional margin in UL link budget due to CQI reports and Ack/Nackdepends 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 ULlink budget for packet services. The only difference is the HS-DPCCHoverhead, and it can be included in the EIRP formula:

    uplinkEIRP = UE Transmit Power - HS_DPCCHoverhead + TransmitAntenna Gain - BodyLoss

    4.2.2 Downlink link budget

    For downlink, the link budget can be used to calculate the cell range withrelated coverage requirements such as cell edge throughput. There aretwo most important link budgets in HSDPA that are for user and controltraffic. Table HSDPA downlink link budget for HS-PDSCH and HS-SCCHshows an example of both link budgets (HS-PDSCH and HS-SCCH).

    HS-DPCCH

    DPCCH

    Ack/Nack CQI report

    ACKi CQINACK CQI

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 37 (113)

    HSDPA dimensioning

  • Table 9. HSDPA downlink link budget for HS-PDSCH and HS-SCCH

    Downlink Service

    Cell Edge Throughput 384

    Channel HS-PDSCH HS-SCCH

    Service PS Data Control

    Service Rate (kbps) 384Transmitter - Node B

    Max Tx Power (dBm) 37.4 27Cable Loss (dBi) 0.5 0.5MHA Insertion Loss 0.0 0.0

    Tx Antenna Gain (dBi) 18 18EIRP (dBm) 54.9 44.5

    Receiver - Handset

    Handset Noise Figure (dB) 7 7Thermal Noise (dBm) -108 -108Downlink Load (%) 80 80Interference Margin (dB) 7.0 7.0Interference Floor (dBm) -94.0 -94.0SINR Requirement (dB) 4.5 1.5Spreading Gain (dB) 12.0 21.0Receiver Sensitivity (dBm) -101.5 -113.5Rx Antenna Gain (dBi) 2 2Body Loss (dB) 0 0DL Fast Fade Margin (dB) 0 0DL Soft Handover Gain (dB) 0 0Gain against shadowing (dB) 2.5 2.5Building Penetration Loss(dB)

    12 12

    Indoor Location Prob. (dB) 90 90Indoor Standard Dev. (dB) 10 10Shadowing margin (dB) 7.8 7.8Isotropic Power Required(dB)

    -86.3 -98.2

    Allowed Prop. Loss (dB) 141.2 142.7

    38 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 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 thechannel measurements. This means that the achieved throughput isdifferent in every TTI. The average throughput in a certain location can beestimated if the average SINR (Signal to Interference + Noise Ratio) isknown. Commonly simulation results are used for estimating the averageSINR. Figure Throughput and SINR comparison shows the SINR andthroughput table with different codes.

    Figure 7. Throughput and SINR comparison

    -10 -5 0 5 10 15 20 25 30 35 400

    2

    4

    6

    8

    10

    12

    SINR(dB)

    Throughput(M

    bits/s)

    5 codes, PedA

    5 codes VehA

    5 codes fit

    10 codes PedA

    10 codes VehA

    10 codes fit

    15 codes PedA

    15 codes VehA

    15 codes fit

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 39 (113)

    HSDPA dimensioning

  • As shown in the figure, in lower throughputs there is no huge advantage ofusing 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 forHSDPA. The reason to use SINR is that the HSDPA bit rate and thenumber of codes can change in every TTI. Using Eb/No or Es/No in thelink budget would require that either the bit rate or the number of the codesis 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 toestimate the power allocated to it, because that also affects the HSDPApower that is left for traffic. HS-SCCH depends on the user location and iscommonly assumed to be about 500 mW at the cell edge (around G-factor-5 dB).

    Figure 8. User location versus HS-SCCH

    As discussed, the link budget has to consider the cell edge throughput toget the average SINR, and HS-SCCH has to be estimated to calculate thepower left for HSDPA traffic. Similarly in case of shared carrier betweenthe DL DCH and HSDPA, also the DCH power has to be estimated andtaken into account.

    0

    Avg.req.HS-SCCHpower@

    1%

    BLEP[W

    ]

    -15 -10 -5 0 5 10 15

    0.5

    1.0

    1.5

    2.0

    2.5

    3.5

    4.0

    3.0

    NODE-B/CPICH POWER 12W/2W1x1-RAKE, 3KM/H, 6MS/1DB LA DELAY/ERROR

    Typical macrocellularenvironment (3GPP)

    Average G-factor [dB]

    Ped-AVeh-A

    40 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 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 SINRrequirement, which is needed for getting the wanted service atcell edge.

    2. Define UE parameters.

    Define RX Antenna Gain and Handset Noise Figure. CommonlyBody Loss is assumed to be 0.

    3. Define Node B parameters.

    Available HSDPA power notices also HS-SCCH power and in caseof shared carrier with DCH, the DCH power has to be noted as well.

    Note that feature RAN312: HSDPA Dynamic Resource Allocationdescribes HSDPA power in more detail.

    4. Additional differences compared to the R99 DCH downlink linkbudget.. HSDPA utilises only spreading factor 16.. Receiver sensitivity formula

    Receiver Sensitivity = Interference_floor +SINR - SpreadingGain (SF16)

    . HSDPA does not have soft handover, thus SHO gain are 0 dB.But because there are overlapping cells, the HSDPA mobilecan select at cell edge a stronger cell, which is referred to asGain against shadowing. The recommended value for Gainagainst shadowing in HSDPA is 2.5 dB.

    Other issues, formulas and parameters related to the HSDPA link budgetare same as those for R99. See R99 DCH coverage dimensioning.

    4.2.3 Cell range and coverage

    From the HSDPA perspective, the cell range and coverage are dependenton available power and wanted cell edge throughput.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 41 (113)

    HSDPA dimensioning

  • Figure 9. Example of dynamic power allocation

    As shown in the figure, all available power is allocated to HSDPA. Fromthe dimensioning perspective, it is important to estimate the average non-HSDPA power and calculate the average available power for HSDPA.Based on that you can estimate the coverage. In case of dedicatedHSDPA carrier, DCH traffic power can be neglected. For more informationon dynamic power allocation, see HSDPA dynamic resource allocation inRadio Resource Management of HSDPA.

    4.3 HSDPA capacity dimensioning

    HSDPA downlink link budget utilises the average SINR and throughputmapping, which are commonly based on the simulations. An accurateSINR can be calculated when you know HSDPA power, BTS total Txpower, orthogonality and G factor and the user throughput can beestimated. The calculation is done using the following formula:

    PtxMax

    Time

    HSDPA power PtxTargetPSMax

    PtxTargetPSMin

    Non-HSDPA power

    PtxTargetPS

    PtxMax is the cell maximum output powerdefined by the management parameterPtxCellMax and the BTS capabilityPtxTargetPS is the dynamically adjustedNRT DCH scheduling targetPtxTargetPSMax and PtxTargetPSMin arethe max and min values for PtxTargetPS

    SINR = SF16

    HSDPAP

    totP 1 - + 1

    G

    42 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 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. Atypical range is from -5 dB (Cell Edge) to 20 dB. G-factor is correlated toEc/Io:

    where

    . PCPICH = CPICH channel transmission power

    . PTOT = BS total transmission power at the time of Ec/Iomeasurement

    When the user SINR is known, the mapping on the simulated table can bemade and the user throughput identified. If you allocate all availableHSDPA power to one user, you can estimate the HSDPA cell throughput ina different location in the cell (ref. G-factor) within different radioenvironment (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 inbetween due to feature HSDPA Dynamic Resource Allocation

    Figure Example simulation results of HSDPA cell throughput shows anexample of how the different issues and UE enhancements affect HSDPAcell throughput.

    CPICHP

    TOTP 1 + 1

    G

    E

    IC

    O

    =

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 43 (113)

    HSDPA dimensioning

  • Figure 10. Example simulation results of HSDPA cell throughput

    0

    500

    1000

    1500

    2000

    2500

    3000

    3500

    4000

    4500

    Rake 1-ant Equalizer 1-ant Rake 2-ant Equalizer 2-ant

    kbps

    Round robin 5 codes

    Round robin 10 codes

    Proportional fair 5 codes

    Proportional fair 10 codes

    Proportional fair 15 codes

    44 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 5 HSUPA dimensioning5.1 Introduction to HSUPA dimensioning

    RAS06 provides a new advantage to uplink with HSUPA, which provideshigh data rates in uplink direction for packet services. HSUPA is providedonly in co-existence with HSDPA.

    The aim of the HSUPA air interface dimensioning is to specify how muchload should be allocated for HSUPA. HSUPA capacity should be enoughto achieve HSUPA throughput targets, but on the other hand, enoughresources should be reserved for DCH traffic and for HSDPA-associatedUL DPCH.

    In case of high DCH load, the shared carrier HSUPA+UL DCH is notfeasible to fully support the HSUPA demand. In high DCH load a dedicatedcarrier for HSPA (HSDPA+HSUPA) is needed. In this case the uplinkcapacity of the carrier is allocated to HSUPA and HSDPA associated ULDPCH, see Figure Overall dimensioning process for dedicated HSPAcarrier.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 45 (113)

    HSUPA dimensioning

  • Figure 11. Overall dimensioning process for dedicated HSPA carrier

    As shown in the figure, the UL calculation notices both HSDPA associatedUL DPCH load and HSUPA load. It is important that during dimensioningalso the HSDPA-associated UL DPCH capacity need is noticed andestimated.

    The overall process is as described in Introduction to HSDPAdimensioning and so the expected outcomes from HSUPA dimensioningare:

    . defining the HSUPA cell range and coverage based on cell edgethroughput

    . calculating the average cell throughput based on available load forHSUPA

    . identifying the Node B configuration required to achieve a specificthroughput performance.

    For more information, see High-speed Uplink Packet Access (HSUPA) inHSPA Overview.

    Air interface dimensioning,dedicated carrier HSPA

    Coverage dimensioningselection:

    - Link Budget UL R99(based on HSDPAassociated UL DPCHservice)- Link Budget HSDPA(based on cell edgethroughput)- Link Budget HSUPA(based on cell edgethroughput)- Output # of coverage sites UL DPCH capacity

    dimensioning

    Resultevaluation

    CECalculation

    HSDPA capacitydimensioning

    Iu-bDimensioning

    RNCDimensioning

    Additionalcapacity Node Bs

    Dimensioning inputs and requirements

    Coverage dimensioning Capacity dimensioning

    Input: capacityfor HSUPA

    Output:HSUPAthroughput

    OK

    Not OK

    Output:HSDPAthroughput

    Input:availablecapacity# of

    Node Bs(coverage +capacity)

    HSUPA capacitydimensioning

    Input:availablecapacity

    46 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 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 percell.

    The operator can choose to set a lower threshold for the maximumnumber of users per cell and per BTS.

    Transmission Time Interval (TTI) of 10 ms is used for maximising theresulting 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 isachieved using 59 RLC PDUs per TTI.

    HSUPA requires a static reservation of eight CE in WSPC (UltraSiteWCDMA BTS) and eight CE in Flexi Submodule (Flexi WCDMABTS) capacity. The rest of the HSUPA baseband capacity is fullypooled across cells, and also dynamically shared with R99 traffic. Upto two WSPCs (in Flexi Submodules) can be in HSUPA use, R99traffic allowing.

    The maximum peak data rate per user is 2.0 Mbps as coded L1 bitrate (error protection coding is not counted into bit rate whereas L1retransmissions are).

    One WSPC in UltraSite WCDMA BTS and one Submodule in FlexiWCDMA BTS supports up to 12 24 HSUPA users, depending onthe data rate.

    The maximum HSUPA bit rate per WSPC (Submodule in FlexiWCDMA BTS) is 6 Mbps, with three 2 Mbps users in separate cells.

    . RAN973: HSUPA Basic RRM

    . RAN968: HSUPA BTS Packet Scheduler

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 47 (113)

    HSUPA dimensioning

  • . 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 ResourceManagement 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 theload generated by R99, which can be due to pure DCH UL traffic orHSDPA associated UL DPCH traffic.

    The HSUPA capacity calculation takes into a consideration the DL loadused for R99 services and HSDPA-associated DPCH. This means that it isnecessary to make load calculation based on traffic inputs to find out howmuch load is reserved for R99 and associated UL DPCH. Based on thisinformation the available UL load can be used to determine the HSUPAcapacity. This is needed if the HSUPA has shared carrier with R99 traffic. Ithas to be taken into account also when dedicated HSPA carrier is used,because the HSDPA-associated UL DPCH utilises the UL load withHSUPA.

    5.2 HSUPA coverage dimensioning

    5.2.1 Uplink link budget

    As shown in Table Example of HSUPA link budget, the HSUPA link budgetis very similar to the R99 uplink packet service link budgets, especiallyregarding HSDPA associated UL bearer. The major differences are relatedto higher user throughputs, which generate higher own connectioninterference. Also the Eb/Nos used are better when compared to DCH.This is due to Node B based HARQ, which allows to tolerate additionalpacket losses and retransmissions without causing problems from thedelay perspective.

    48 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Table 10. Example of HSUPA link budget

    Uplink Service

    Cell Edge Throughput(kbps)

    64

    Target BLER (%) 10Propagation Channel Pedestrian A 3 km/h

    Channel HSUPA

    Service PS Data

    Service Rate (kbps) 64Transmitter - UE

    Max Tx Power 24

    HS-DPCCH Overhead 2.5

    Tx Antenna Gain (dBi) 2Body Loss (dB) 0EIRP (dBm) 23.5

    Receiver - Node B

    Node B Noise Figure (dB) 2Thermal Noise (dBm) -108Uplink Load (%) 50Interference Margin (dB) 3.0Own ConnectionInterference

    0.08

    InterferenceFloor (dBm) -103.1Service Eb/No (dB) 0.2Service PG (dB) 17.78Receiver Sensitivity (dBm) -120.65Rx Antenna Gain (dBi) 18Cable Loss (dB)s 0.5Benefit of using MHA (dB) 0UL Fast Fade Margin (dB) 1.8UL Soft Handover Gain(dB)

    1.5

    Gain against shadowing(dB)

    2.5

    Building Penetration Loss(dB)

    12

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 49 (113)

    HSUPA dimensioning

  • Table 10. Example of HSUPA link budget (cont.)

    Uplink Service

    Indoor Location Prob. (dB) 90Indoor Standard Dev. (dB) 10Shadowing margin (dB) 7.8Isotropic Power Required(dB)

    -120.6

    Allowed Prop. Loss (dB) 144.0

    Own connection interference has been neglected from R99 uplink linkbudget as it has such a low impact on system performance. This is mainlyrelated to the fact that uplink 64 kbps service is commonly used in R99dimensioning, and other to own interference is very low, around 0.08. InHSUPA, the link budget can be made even with throughputs higher than0.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/Novalue.The following table shows the simulated Eb/Nos for HSUPA.

    Table 11. Simulated Eb/Nos for HSUPA

    Pedestrian A 3 km/h

    10 % BLER

    Vehicular A 30 km/h

    10 % BLER

    Bit rate (kbps) Eb/No (dB) Bit rate (kbps) Eb/No (dB)

    32 0.8 32 2.3

    64 0.2 64 1.6

    128 -0.2 128 0.8

    256 -0.5 256 0.4

    384 -0.5 384 0.4

    512 -0.7 512 0.1

    768 -0.7 768 0.1

    50 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Table 11. Simulated Eb/Nos for HSUPA (cont.)

    Pedestrian A 3 km/h

    10 % BLER

    Vehicular A 30 km/h

    10 % BLER

    Bit rate (kbps) Eb/No (dB) Bit rate (kbps) Eb/No (dB)

    1024 -0.2 1024 0.6

    1440 1.3 1440 2.1

    . HS-DPCCH overhead. As mentioned in HSDPA uplink linkbudget, the same HS-DPCCH overhead is implemented inHSUPA, which is dependent on the bit rate. The following tableshows the overhead values for soft handover and without softhandover.

    Table 12. HS-DPCCH overhead for HSUPA

    SHO Bit Rate (kbps) 35.4 69 102.6 169.8 474 810 1146DS-DPCCHOverhead (dB)

    3.03 2.46 1.93 1.27 0.087 0.60 0.39

    No SHO Bit Rate (kbps) 35.4 69 102.6 169.8 474 810 1146DS-DPCCHOverhead (dB)

    1.48 1.16 0.88 0.55 0.37 0.25 0.16

    . HSUPA EIRP. You can calculate HSUPA EIRP using thefollowing 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. Commonlybody loss is assumed to be 0.

    3. Define Node B parameters.

    Node B parameters are the same as in R99 DCH link budget. SeeR99 DCH coverage dimensioning.

    4. Additional differences compared to the R99 DCH uplink link budget

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 51 (113)

    HSUPA dimensioning

  • . Own connection interference. Own connection interferencefactor reduces the uplink interference floor by the UEs owncontribution to the uplink interference, that is, by the desireduplink signal power. This means that the own connectioncontribution has to be noted in the interference floorcalculation. The formula for calculating own connectioninterference contribution is as follows:

    . Interference floor. Based on the above mentioned modificationthe 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 budgetare the same as the link budgets in R99. See R99 DCH coveragedimensioning.

    5.2.2 Downlink link budget

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

    5.2.3 Cell range and coverage

    From the HSUPA perspective, the cell range and coverage are dependenton uplink link budget and defined cell edge throughput.

    By defining the cell edge throughput, the Eb/No will be selected and theoverall link budget and cell range estimation are as in R99 DCH linkbudget.

    HSUPA has additional features that affect the cell range. One whichaffects the load generated to the cell and also the cell range is then higherdue to the lower interference margin.

    Own_connection_int = 10LOG 1+

    Eb

    No

    W

    R

    52 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 5.3 HSUPA capacity dimensioning

    Capacity dimensioning can include one user throughput estimation orwhole cell throughput estimation. The following issues affect capacitydimensioning:

    . Available load for HSUPA

    . User location

    . Number of users

    . Load equation parameters, that is, intercell interference ratio whichdepends on sectorisation

    Follow these steps to perform HSUPA capacity dimensioning.

    1. Estimate the uplink load of DCH users and define the target uplinkload margin.

    As mentioned earlier, HSUPA capacity dimensioning has to take intoaccount also the capacity used for R99 DCH traffic. If the R99 uplinkload is 36 % and the maximum target UL load is set to 80 %, HSUPAcapacity is 80%-36% = 44%. This 44% can be used to define thecapacity for HSUPA. Figure Load estimation for R99 DCH andHSUPA shows the load estimation between R99 DCH and HSUPA.

    Figure 12. Load estimation for R99 DCH and HSUPA

    0

    2

    4

    6

    8

    10

    12

    IncreaseinInterference(dB)

    Uplink Loadgenerated byR99 DCH

    Uplink Loadavailable forHSUPA UE

    0 20 40 60 80 100

    Uplink Load (%)Example TargetUplink Load

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 53 (113)

    HSUPA dimensioning

  • As shown in the figure, it is important to estimate the R99 load inuplink in order to define the HSUPA capacity. To calculate the loadused in R99 DCH traffic you can utilise the formula discussed inSupporting R99 formulas.

    The uplink load is translated to uplink C/I using the uplink loadequation:

    C/I is translated to HSUPA bit rate using the Eb/No look-up tablederived from link level simulations.

    This information can be used to estimate the throughput in the areawith estimated parameters. To go into more detail, the available loadcan be divided into expected amount of HSUPA users.

    2. Divide the available uplink load between the expected number ofHSUPA users.

    The available HSUPA load has to be divided equally to everyHSUPA user. When increasing the number of users, each user willhave lower throughput due to the decreasing available load, thusinfluencing at the end the C/I. As a result of this step, all users willhave the same available load and also the same C/I.

    To go into more detail, also the estimated HSUPA user location canbe used to estimate user throughput.

    =

    54 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 3. Estimate the link losses between the expected locations of HSUPAusers and the BTS. This way you can get the average cellthroughput by estimating the share of bad coverage HSUPA usersand good coverage users, for example. Figure Example of HSUPAuser distribution on cell area shows an example distribution of fiveusers.

    Figure 13. Example of HSUPA user distribution on cell area

    The location can be estimated by introducing path loss offsets todetermine the path loss for each UE. C/I can be calculated asfollows.

    where. Wanted signal is the signal strength which is calculated from

    the link budget, assuming that the UE is transmitting atmaximum power. The path loss offset can be introduced todetermine 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.

    0.0

    500.0

    1000.0

    1500.0

    2000.0

    2500.0

    3000.0

    3500.0

    4000.0

    0.0 1000.0 2000.0 3000.0 4000.0

    UE5

    UE4

    UE3

    UE2

    UE1

    antenna

    link budgetprovidesthe cell edgepath loss

    ylocation

    x location

    C / I = 10xLOGWantedSignal

    Interf.Floor - WantedSignal

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 55 (113)

    HSUPA dimensioning

  • 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 totheir maximum achievable C/I, and you can utilise the load with otherusers 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, whichcan influence the load and C/I.

    56 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 6 Dimensioning transport networkPurpose

    The most critical task in dimensioning a transport network is to find atransmission solution for the connection between the transmission networkand the base station site. The network rollout can depend on how fast thisconnection can be built. Leasing a Time Division Multiplexing (TDM) orAsynchronous Transfer Mode (ATM) line can be very expensive and time-consuming. Microwave radio links can be more efficient if you build yourown network and copper or fibre-based options are not available. Theradio 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 capacityincrease on each HSDPA-enabled base station. Iub efficiency featuressuch as BTS AAL2 Multiplexing help operators to more efficientlyimplement HSDPA if more than one active WAM is utilised. If an ownmicrowave radio network is chosen, environmental factors such as line ofsight, restrictions in building permissions or access to microwave radiofrequency licences may have an impact.

    Check:

    . the number of subscribers

    . the number of services per subscriber.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 57 (113)

    Dimensioning transport network

  • Summary

    Figure 14. Dimensioning transport network

    Steps

    1. Calculate the required transport network capacity.

    Calculate the required transmission capacity for the BaseTransceiver Station (BTS) and Radio Network Controller (RNC).

    The needed transport network capacity depends on the radionetwork configuration, which again is based on the estimatednumber of the subscribers and services that the subscribers use.

    2. Select transport network media.

    Depending on the environment and network configuration, you canchoose from cables, radios, and leased lines. Check thegranularities and capacities offered in radio links, fibre, and leasedlines.

    Services persubscriber

    Requiredtransmissioncapacity/RNC

    Requiredtransmissioncapacity/core NW

    Transmission network planning(capacity, media, topology, protection...)

    QoS requirementsfor the traffic

    Radio networkplanning

    Number ofsubscribers

    58 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 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 newequipment is taken into use.

    Expected outcome

    . transmission topology

    . capacity of the transmission connections between the nodes in thetransmission network

    Further information

    You can purchase Nokia planning services for dimensioning transportnetwork.

    See also Planning synchronisation in Planning WCDMA RAN.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 59 (113)

    Dimensioning transport network

  • 60 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 7 Dimensioning BTS7.1 Dimensioning Flexi WCDMA BTS

    A new Base Transceiver Station (BTS) type called Flexi WCDMA BTS hasbeen available since RAS05.1. Flexi Wideband Code Division MultipleAccess (WCDMA) BTS is a new, truly modular, very compact, and highcapacity wide-area WCDMA BTS that can be used in various indoor andoutdoor 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 NokiaUltraSite 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 ascontrol and transmission functionalities.

    System Module provides up to 240 CE capacity. The number of CEsactivated can be increased by licence control.

    HSDPA is activated in the Flexi WCDMA BTS dynamically, and thecapacity reserved for HSDPA is defined using features SharedHSDPA Scheduler for Baseband Efficiency and HSDPA 48 Usersper Cell. One to six cells may have HSDPA activated with FlexiWCDMA BTS.

    The baseband Extension Module is also available, increasing FlexiWCDMA BTS capacity to 2*240 = 480 CE.

    . Optional power supply module.

    Optional Outdoor Cabinet is also available.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 61 (113)

    Dimensioning BTS

  • Figure 15. Flexi WCDMA BTS modules

    7.1.1 Capacity

    Flexi WCDMA BTS provides 12-carrier capacity. Up to six sectors and fourcarriers per configuration are supported by HW. The output power optionsmin 8/20/40W are available. The following Flexi 20/40 W per carrierconfigurations are available: 1, 1+1, 1+1+1, 2, 2+2, 2+2+2 and 2+1+1. 1omni configuration is also available with 8W option.

    One Radio Module can support one or two sectors. For 1+1+1 (min 40Wper carrier) or 2+2+2 (min 20W per carrier) configurations one SystemModule and two Radio Modules are required for a complete a WCDMABTS setup. Baseband capacity of the system module can be addedremotely 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)

    ExtensionSystem Module

    BTS SystemModule

    RF Module

    RF Module

    RF Module

    AC(Optional)

    AC > DC BBU

    62 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Table 13. Flexi WCDMA BTS (1+1+1) processing capacity

    User data CE UL / Min SF CE DL / Min SF

    AMR (voice) 1) 1 / SF64 1 / SF128WB-AMR 2) 1 / SF64 1 / SF128

    PS 16 kbps 1 / SF64 1 / SF128

    PS 32 kbps 2 / SF32 2 / SF64

    PS 64 kbps 4 / SF16 4 / SF32

    PS 128 kbps 4 / SF8 4 / SF16

    PS 256 kbps 8 / SF4 8 / SF8

    PS 384 kbps 16 / SF4 16 / SF8

    CS 64 kbps 4 / SF16 4 / SF32

    CS 57.6 kbps 4 / SF16 4 / SF32

    CS 14.4 kbps 1 / SF64 1 / SF128

    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 inthe following table. The table refers to BTS baseband capacity only. In realnetworks, air interface and transport capacity issues have to beconsidered as well. For more information, see Dimensioning Air interfaceand Dimensioning Iub interface.

    Table 14. Flexi WCDMA BTS (1+1+1) baseband capacity and HSDPA

    Feature 5 codes 15 codes

    CE required Maxthroughputper cell

    Maxthroughputper BTS

    CErequired

    Maxthroughputper cell

    Maxthroughputper BTS

    HSDPA 16 Users per BTS 32 CE 3.6 Mbps 3.6 Mbps n/a n/a n/a

    HSDPA 16 Users per Cell 96 CE 3.6 Mbps 10.8 Mbps n/a n/a n/a

    Shared HSDPA Schedulerfor Baseband Efficiency(48 users per BTS)

    80 CE 3.6 Mbps 10.8 Mbps 80 CE 3.6 (7.2)Mbps

    10.8 Mbps

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 63 (113)

    Dimensioning BTS

  • Table 14. Flexi WCDMA BTS (1+1+1) baseband capacity and HSDPA (cont.)

    Feature 5 codes 15 codes

    +with HSDPA CodeMultiplexing feature

    n/a n/a n/a 80 CE 10.8 Mbps 10.8 Mbps

    HSDPA 48 Users per Cell 240 CE 3.6 Mbps 10.8 Mbps 240 CE 3.6 (7.2)Mbps

    10.8 (21.6)Mbps

    +with HSDPA CodeMultiplexing feature

    n/a n/a n/a 240 CE 10.8(14.4)Mbps

    32.4 (43.2)Mbps

    The figures in parentheses assume that either 10- or 15-code phones areused in the network.

    7.1.3 Capacity licenses

    Flexi WCDMA BTS licensed capacity defines the capacity that theoperator has purchased. Licensed capacity can be less than the maximumhardware capacity.

    Flexi WCDMA BTS baseband capacities are allocated according to thecapacity license file. Because the ATM Cross-Connection (AXC) and theBTS exist in high volumes in the network, Nokia Siemens Network doesnot generate licenses for these network elements directly (NE licences),but so-called pool licenses are used. This means that the user gets thelicense 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 distributedtowards 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 poollicense and the help of the license management tools in NetAct you candistribute the capacity according to capacity needs, for example, 120channel elements for BTS-1, 70 channel elements for BTS-2, and so on.For this purpose, NetAct generates appropriate license files anddownloads them to the network elements.

    For more information on licences, see Pool licences in LicenceManagement in WCDMA RAN.

    64 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • 7.1.4 Flexi WCDMA BTS and transmission

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

    7.2 Dimensioning UltraSite WCDMA BTS

    Figure UltraSite WCDMA BTS architecture depicts Nokia MetroSite andNokia UltraSite WCDMA BTS units. Wideband Signal Processor A(WSPA) and Wideband Signal Processor C (WSPC) capacities arepresented in WSPA/C processing capacity.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 65 (113)

    Dimensioning BTS

  • Figure 16. UltraSite WCDMA BTS architecture

    UltraSite WCDMA BTS units are explained in the following table.

    Table 15. BTS units

    Unit Description

    WAF Wideband Antenna Filter. Combines and isolates Tx/Rx signalsand amplifies the received signals. One WAF is required persector.

    R-busWAF

    WTR RR-bus

    RT-bus

    T-bus

    WPA

    WAF

    WPA

    WTR

    DSC-bus

    RR-bus

    RT-bus

    R-busWAF

    WTR RR-bus

    RT-bus

    T-bus

    WPA

    WAF

    WPA

    WTR

    DSC-bus

    RR-bus

    RT-bus

    R-busWAF

    WTR RR-bus

    RT-bus

    T-bus

    WPA

    WAF

    WPA

    WTR

    DSC-bus

    RR-bus

    RT-bus

    IFU

    WSC

    AXU

    lub

    CarrierInterface

    WSCMAIN

    WSCREDU

    WAM

    WAM

    WAM

    WAM

    WAM

    WAM

    ST-busSR-bus

    ST-busSR-bus

    ST-busSR-bus

    ST-busSR-bus

    WSM

    WSM

    WSM

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    WSP

    66 (113) # Nokia Siemens Networks DN70118376Issue 2-0 en18/06/2007

    Dimensioning WCDMA RAN

  • Table 15. BTS units (cont.)

    Unit Description

    WPA Power Amplifier. A multicarrier amplifier with an operatingbandwidth of any 20 MHz section on the whole 60 MHz WCDMAallocation (WPAC/D), on a 10 MHz section of two neighbourcarriers (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 therequired output power per carrier.

    WTR WCDMA Transmitter and Receiver unit. One Wideband Transmitterand Receiver version B or D (WTRB/D) can serve two cells of 2-way uplink diversity, WTRA can serve one cell.

    WSM Summing and Multiplexing unit. Sums Tx signals from the signalprocessing units or other WSMs.

    WSP Signal Processing unit. Performs Rx and Tx code channelprocessing, coding, and decoding functions. The number of WSPsis planned according to the expected traffic on the BTS. WSPcapacities are presented in Tables WSPA processing capacity andWSPC processing capacity.

    WAM Application Manager. There can be up to six WAM units installedin 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&Mmaster unit (Master WAM) by the system. Master WAM unit takescare of the control functions on BTS cabinet level. Those includeBTS start-up, temperature control, configuration, and O&Mprocessing.All WAM units perform telecom control functions, logical resourcemanagement, ATM processing, and transport channel frameprotocol processing.

    AXU Each UltraSite WCDMA and MetroSite WCDMA/50 Base Stationhas an integrated ATM switch, called the ATM Cross-connect(AXC) Node, for communication between the sectors inside theBTS, towards the RNC, and towards other BTSs. The AXU unitperforms the main ATM functionality for the communication withinthe BTS and provides the connections to other network elements.

    IFU The IFUs provide the physical connection to the network. Theysupport the following transmission interfaces: E1/JT1, STM-0/STM-1, E1, Nokia Flexbus.

    7.2.1 WSPA/C processing capacity

    The following table presents the WSPA processing capacity.

    DN70118376Issue 2-0 en18/06/2007

    # Nokia Siemens Networks 67 (113)

    Dimensioning BTS

  • Table 16. WSPA processing capacity

    User data rate /kbps

    Decodingcapacity

    Min SF Encodingcapacity

    Min SF

    AMR voice 32 64 32 128

    16 32 64 32 128

    32 16 32 16 64

    64 8 16 16 32

    128 8 8 8 16

    256 4 4 4