Nokia Standard Document Template

RU20NPO Recommended Parameters for RadioThe information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of NSN Networks' customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of NSN Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. NSN Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between NSN Networks and the customer. However, NSN Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. NSN Networks will, if necessary, explain issues which may not be covered by the document.

NSN Networks' liability for any errors in the document is limited to the documentary correction of errors. NSN Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according to the applicable laws.

NSN logo is a registered trademark of NSN Corporation.

Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only.

Copyright NSN Networks Oy XE "Copyright Nokia Telecommunications Oy" 2010. All rights reserved.Table of contents

32.Introduction

3.Idle mode parameters33.1Idle Mode WCDMA Parameters33.2Idle Mode GSM Parameters34.SHO parameters35.Inter-System Handover parameters36.Inter-frequency Handover parameters37.Power Control parameters38.Admission Control parameters39.Packet Scheduling parameters310.Telecom parameters311.Other parameters312.HSDPA related parameters312.1HSDPA power parameters312.2HSDPA Dynamic Code Allocation312.3Other Recommended HSDPA parameters313.Other Optional features313.1Priority Based Scheduling313.2Flexible Upgrade & Throughput Based Optimization313.3Narrowband AMR Codecs313.4Load and Service Based Handover314.RU10 Default changes with C-Iub315.HSUPA Parameters316.TECHNICAL NOTES3

Change History

IssueDateHandled byComments

1.0.020.12.2002RNC Technical SupportRAN1.5.1 & 1.5.2

2.0.031.12.2003OS/NPSRAN1.5.2 ED2

2.1.030.05.2004OS PerformanceRAN1.5.2 ED2, update

New parameters added:

Power control algorithm 1

TinTr and TigOr

MSactivitySupervision

CodeTreeOptimisation

Offset for activation time

PtxDLAbsMax

T3212

2.2.031.8.2004OS PerformanceCorrections to implementation of

Sib3compmask2 SIB3compmask5

QsearchC

FDD_Qmin

2.3.013.11.2004OS PerformanceCorrections to the parameters related to ROC BTS.

Corrections to the parameters related to MHA and Cable loss.

Correction to the Offset for activation time.

2.3.113.01.2005OS PerformanceReference to TN 047 added + corrections to the text.

2.4.014.3.2005OS PerformanceValid for RAN1.5.2 latest release + RAN04 first release, Also RAN1.5 parameters which has now optimal values as default values in parameter database has been taken out. Also RAN 1.5 parameters which cannot be changed, or are read only by the system have been taken out.

PowerRampStepPRACHpreample changed from 1 dB to 2 dB =default

RAN04 only parameters have been added as separate chapter.

ToAWS/ToAWE parameters added for NRT cases in RAN04.

2.5.010.6.2005OS PerformanceUpdated with the following info.

SDUdiscardModeRTPS (for RAN04 streaming service)

RAN04 Initial and minimum bitrate change in UL: 16-> 32 kbits/s

ATO change to 700ms for both 3.4 kbits/s and 13.6 kbits/s SRB.

GSM HO caused by DL DPCH TX Power change: false-> true

Combined LAU/RAU on BSS side (Gs interface).

T317 change : 180s-> 10s (time from cell_fach-> idle in case of out of service)

2.6.006.10.2005OS PerformanceModifications to cable loss parameter (TN62). Modifications to maximum measurement period (ISHO) parameter. CPICHtoRefRABOffset and PCRangeDL parameters added. AdjsSIB and AdjgSIB parameters added. Wait time RRC interactive and Wait time RRC background parameter added. IuBarringRecoveryTimer parameter added. Comments to the ToAWS and ToAWE parameters.

2.7.014.12.2005OS PerformanceDeleted default values defined in system compared to 2.6.0

3.0.05.4.2006C&IMain RAS5 update:Qhyst2: comment added

SIB3Compmask2 and SIB3Compmask5: value and comment modified

AdjgSIB and AdjsSIB: now modifiable

FddQmin: new recommended value. Parameter name orthograph changed.

FDD Qoffset (GSM): removed

GSM HO caused by UE Tx Power: added

Refrence to Soft Handover FMCS parameter: removed

Maximum Allowed DL User Bitrate in HHO: addedHHO triggers for NRT Services: added

IFHO caused by UE TxPower:added

CodeTreeOptimisation: modifiedT312: deleted

T317: deleted

ToAWS/ToAWE: deleted.

IuBarringRecoveryTimer: modified

StandAloneDCCHBitRate: added

Chapter 12: HSDPA: added

3.0.227.4.2006C&IModified SharedHSDPAFlowControlAllocation description

3.131.1.2007C&IMain RAS51 update:

Added T313,N313Added DedicatedMeasReportPeriodAltScramblingCodeCM: disabled when HSDPA is enabled

Added T315

Update for new RAS51 features: LSHO, TBO, HSDPA Dynamic power allocation, AMR MB codecs

Modified description of several parameters in 12.3 Other Recommended HSDPA Parameters, due to HSDPA Serving Cell Change feature.

3.224.8.2007CSINSN look and feel

4.04.12.2007CSIRemoved RAN4 default values

FDD_QMIN: removed pre-rel4 table valuesQhyst1 removed as default value was updated

Removed RASS5 static power allocation settings.

Added HSDPA RAS6 and HSUPA parameters section

4.131.3.2008NPOChange in Inter-Rat cell reselection parameters

Change in code tree usage with HSDPA enabled

Change in HS-PDSCH code upgrade margin for SF128 codes with 10/15 HSDPA code feature

Change in PtxMaxHSDPA with Dynamic resource allocation

Change to CPICHtoRefRABoffset with high HSDPA traffic

Change in Required received C/I on PRACH at WCDMA BTSChange in ISHO thresholds.

Change in AM RLC protocol parameters for NRT

Recent Techical Notes added

4.2 29.04.2008NPOSib3compmask parameters are hidden and fixed in RN2.1. Reference point for UL interference changed in RAS06 with MHA. DPCHOverHSPDSCHThreshold added to have to always allow NRT DCH over HSDPA code pre-emption

4.316.7.2008NPOPrxLoadMarginMaxDCH added

4.429.10.2008NPOSome range values added instead of pure numbers, some parameters were taken out (optimum value set as default), excel version added based on object classes.

4.4.118.12.2008NPO Minor corrections to HSPDSCHMarginSF128 and DPCHOverHSPDSCHThreshold parameters based on the field tests.

4.530.4.2009NPORU10 parameter recommendations added: TN SW 127, C-Iub changes, SHO parameters due to SRB blocking

4.621.9.2009NPOMinor corrections to cell range, RRC enable release and drop reporting interval, Prachdelay range added

4.723.4.2010NPOFirst Version for RU20.

Editor:Pekka Ranta

Date:23.4.2010

Version:1.1.1.1 4.6

Approved by:1.1.1.2 F. Reymond

2. Introduction

The purpose of this document is to provide NPO parameter modifications proposal to UTRAN and GERAN default values (as used in the corresponding UTRAN or GERAN parameter dictionary) in order to maximize network performance. The parameters mentioned in this document are valid up to RU20 releases. For RU20 release there is no changes to Radio.Each modification should be evaluated on a case-by-case basis, taking into account the local environnement and target network configuration. The parameters changes are categorized as

Idle more WCDMA/GSM parameters

Mobility

Soft HO Parameters

Inter-System handover parameters

Inter-Frequency handover parameters

RRM

Admission control parameters

Packet Scheduling parameters

Telecom Parameters Power Control parameters HSDPA (RAS05 onwards) and HSUPA (RAS06 onwards) parametersIt is possible to view/modify all listed 3G parameters using RNC RNW Object Browser. There are also some GSM parameters which have to be modified from BSC (MML commands).

Different Ues may have different impact to the performance, so there could be some modifications needed for Sanyo or NEC mobile phones compared to NSN. In this document there are some information related to those Ues.

3G network topology is varying a lot which means that the radio network ptimization activities will be needed anyway to improve the radio network performance. Thus these parameters are only better defaults to start the optimization.

3. Idle mode parameters

3.1 Idle Mode WCDMA Parameters

Idle mode parameters should be optimized to improve the call setup success rate.ParameterObjectDefault valuesOptimized valuesComments

Qhyst2 (Cell resection hysteresis 2, for EcNo)WCEL2 dB

4 dB

2 dB

0 dB4dB for WCDMA cells near different LA unless compensated by AdjsQoffset2 (per adj)

2 dB hysteresis between WCDMA cells can be used in Urban environment to avoid ping pong.

2dB (or less) enables faster cell reselection, which can contribute to improve HSDPA accessability.0 dB hysteresis can be used in the area of high mobility.

Cell reselection triggering time (Treselection)WCEL2 s

2 s0 s2s reselection time helps avoid too many cell reselections between cells and hence LA/RA updates when crossing LA/RA border. Thus there is less signaling and less call failures at LA/RA border due to LA/RA update.

0s can be used in areas having high mobility like in highways.

AdjSSIB

AdjGSIBAdjISIBADJS

ADJGADJI11

10

00All the neighbour cells are included into system information block (SIB11/12) by default. The parameters are set by the system to the default value 1 (yes). The value must be set to 0 for marginally used adjacencies if the total amout of neighbours for a given cell exceeds the SIB11 limit (typically 47 adjacencies).It is preferable to avoid removing intra-frequency adjancencies

3.2 Idle Mode GSM Parameters

ParameterObjectDefaultRecommended valueComments

MINIMUM FDD THRESHOLD (Fdd_Qmin)

BTS0 (-20 dB)

-6..-10 dB

Should be balanced with QqualMin and SsearchRAT to reduce ping-pong. 6-8 dB hysteresis recommended (if Qqualmin+ SsearchRAT=-16, Fdd_Qmin= -8 dB, Note: actual value based on UE interpretation.

Non GPRS Multi RAT MS Qual (QsearchI) (GSM), QSRIGPRS Multi RAT MS Qual

(QsearchP) (GSM), QSRPBTS15 (no meas)7 (=always)UE will measure always 3G cells if they are defined neighbours. On the other hand this will have effect to the UE battery life time.

Multi RAT MS Qual (QsearchC), QSRCHOC15 (no meas)7 (=always)If set to 15 Measurement Information (MI) is send anyway (even though UE should not measure 3G neighbours with that value 15), if ISHO_SUPPORT_IN_BSC or EMR_SUPPORT_IN_BSC features are used.

Note: In case ISHO_SUPPORT_IN_BSC or EMR_SUPPORT_IN_BSC features are used the parameter values set with QSRI, QSRP or QSRC do not affect to the Measurement Info message and MI is always send by Mobile. This is valid in S10.5, S10.5 ED and S11. Only if both features are not used, MI info is not send. 4. SHO parameters

Note: From RAS05 onwards, the default system value for FMCS parameters is equivalent to the optimal recommendation. However in RU10 there are some modifications needed.Several customers use 4 FMCS sets: for RT,NRT traffic, HSPA and AMR+ HSPA.

RT traffic uses default set of values of (4,6,2) dB for (Addition, Drop and Replacement Window) values, respectively

NRT traffic uses default set of values of (2.5,4,2) dB for (Addition, Drop and Replacement Window) values, respectively

ParameterObjectDefault valuesRecommendedvaluesComments

DropreportingIntervalFMCS0.5s1s (3) or disabled (0)This is to related to first observations about SRB blocking in RU10 -> decrease signaling with this change

ReplacementReportingIntervalFMCS0.5s1sThis is to related to first observations about SRB blocking in RU10 -> decrease signaling with this change

ReplacementWindowFMCS2 dB4-6 dBRU10 priorizes branch additions over branch deletions to enable fast addition of new cell and decrease call drop rate, Current default trigger setting of SHO event 1C causes plenty of events to be reported in RU10-> SRB blocking

ReplacementTimeFMCS100ms640msSRB Blocking, see above.

5. Inter-System Handover parameters

ParameterObjectDefault valuesRecommended valuesComments

GSM HO caused by CPICH Ec/No

FMCGDisabled Enabled

GSM HO caused by CPICH RSCP

FMCGDisabled Enabled

GSM HO caused by UE Tx PowerFMCGDisabled Enabled

UE TX Power Filter CoefficientFMCG10 ms60 msIn case GSM HO caused by UE Tx Power is enabled.10 ms, too short delay to trigger ISHO.

Consider using longer period, at least 60 ms.

GSM HO caused by DL DPCH TX PowerFMCGDisabled Enabled Some Ues are performing ISHO under good RF conditions due to peaks of high BLER, so DL power should be enabled to avoid dropped call.

Maximum Measurement PeriodFMCG6 measurement reports 12 measurement reports to 20 measurement reportsISHO delays of 5 s has been measured, also the delay depends on the length of neighbour list.

Decreases the probability for no cell found in ISHO.

6 is often too low in environment where 2G BCCH reuse is high.

It is recommended to use at least 12.

Handover of NRT PS Service to GSMRNC/HC&PCNoYesIn case PS ISHO is activated

FMCG needs to be added in cell parameter window.

Maximum Allowed UL User Bitrate in HHOWCEL32 kbits/s

384 kbits/s

Used only with high UE TX power level (RT&NRT) or bad uplink DCH quality triggers.

In case of bad uplink DCH quality, the bitrate threshold concerns only RT data (CS or PS) connections.

This parameter value should be aligned with MaxBitRateULPSNRT, which is by default 384 kbits/s in RAN04 / RAS05.

The RNC is not aware of which TF the UE is using.

CPICH Ec/No HHO Threshold, CPICH Ec/No HHO Cancel, CPICH RSCP HHO Threshold, CPICH RSCP HHO Cancel for NRT ServicesFMCS

NRT,

FMCS HSDPA-12dB, -9dB, -105dBm, -102dBm-16..-18 dB,-12..-14 dB, -115dBm, -110dBmLower values for for NRT services to increase the coverage area, valid for HSDPA also. Even EcNO trigger for NRT could be disabled.Due the signalling delays at inter-system change caused by LU and RAU, and due to the low bit rate available in GPRS network without EDGE, it is beneficial to leave UMTS as late as possible.

CPICH Ec/No HHO Threshold, CPICH Ec/No HHO Cancel, CPICH RSCP HHO Threshold, CPICH RSCP HHO Cancel for NRT ServicesFMCS RT-12dB, -9dB, -105dBm, -102dBm-14..-16 dB

-10..-12 dB

-108..-110 dBm

-105..-18 dBmLower values for RT to have more coverage.

Absolute Isho number (and ISHO) drops will be decreased.

DedicatedMeasReportPeriodWBTS2.5 s0.5 sThis parameter determines the reporting interval that Node B should use (by default, when initialized) for sending dedicated measurement reports to the RNC related the power on DCH channel.

When ISHO Downlink Link Power trigger is in use, reducing this parameter to 0.5 seconds allows faster ISHO and can help reduce drop rate.

Requires cell locking prior to change.

6. Inter-frequency Handover parametersParameterObjectDefault valuesRecommended valuesComments

IFHO caused by CPICH Ec/No

FMCIDisabled Enabled

IFHO caused by CPICH RSCP

FMCIDisabled Enabled

IFHO caused by UE TxPowerFMCIDisabled Enabled

UE TX Power Filter CoefficientFMCI10 ms60 msIn case IFHO caused by UE Tx Power is enabled (see above).

10 ms, too short delay to trigger IFHO.

Consider using longer period, at least 60 ms.

Maximum Measurement PeriodFMCI20 meas report

12 meas reportThis should be in line with ISHO delay.

7. Power Control parameters

ParameterObjectDefaultRecommended valueComments

CPICHtoRefRABoffset (Offset of the P-CPICH and reference service powers)WCEL2 dB0 dB

-1-2 dB (with high HSDPA traffic)This change means that the maximum link power for a connection is increased by 2 dB to improve the DL coverage. This change means also that the minimum power is increased as well (as the minimum power is Max power DL PC Range) which might lead to the situation where too high powers are allocated even in the good coverage conditions as a result power is wasted.

With high HSDPA traffic the increased interference will decrease the EcNo level, which could mean increased peak power for AMR, thus max radio link power for AMR should be increased also.

PcrangeDL (Radio link downlink power control range)RNC15 dB20 dB

This change is needed to compesate the increase of CPICHtoRefRABoffset mentioned above.21-22 dB can be used with negative CPICHtoRefRABOffset

Required received C/I on PRACH at WCDMA BTSWCEL-25 dB-20..-18 dBWith increased traffic and the fluctuation of noise levels the default value -25 just leads to unnecessary unanswered RRC connections or pages i.e. no response from BTS to RRC Connection Request (i.e. no AICH). This can be avoided by adjusting the parameter to -20dB. This has not any negative impact such as increased noise level or spikes.

8. Admission Control parametersParameterObjectDefaultRecommended valueComments

PrxLoadMarginMaxDCH (Interference margin for the maximum UL DCH load)WCEL2 dB (0 dB in RU10)0 dBIn RAS06 onwards UL AC could be based on both throughput and power based PS call algorithm depending on the parameter settings. It is recommended not to use throughput based AC algorithm for R99 PS service but for HSUPA.

9. Packet Scheduling parameters

ParameterObjectDefaultRecommended valueComments

MSActivitySupervision (MS activity supervision timer)

(Time supervision of user inactivity (for NRT RBs))RNC29 min 15 minMSActivitySupervision timer is used in Cell_PCH state for supervising the inactivity of NRT RAB(s). If the parameter value is set to zero: state transition to Cell_PCH is not allowed when inactivity is detected in Cell_FACH state and the MS will be switched to the Idle Mode.

PtxDLabsMax (Planned maximum downlink transmission power of a radio link)WCEL37 dBm35-37 dBmThis parameter is related to the Dynamic Link Optimization feature. It will limit the planned maximum limit for the radio link.

Bitrate downgrade due to DyLo happens if the current link power is 2 dB (fixed value) less than maximum link power. However with this parameter it is possible to optimize the NRT usage in different bitrates. The optimised value for PtxDLAbsMax is between 35-37dBm based on the various measurements.

Offset for activation timeRNC300ms400,500 ms

500 ms has been tested with success in some cases. Needs to be evaluated case-by-case based on Ue mix in network.

Can impact Packet RAB drop rate and AMR/Video RAB setup success rate.

300 ms optimizes call set up time, with the cost of lower CSSR & higher CDR.For full improvement in call setup time the SRB size should be set to 13.6 kbps.

MinAllowedBitRateDL/UL

(Initial and minimum allowed bit rate in DL/UL)WCELUplink 8 kbit/s

Downlink 8 kbit/s

UL/DL 8..32 kbit/s

Optionally consider using recommended values: UL/DL = 32/32 kbits/s. This is due to low throughput on FTP type of services by using TCP. If there is some TCP re-transmissions, these can cause large queue of TCP frames buffered in RLC and then pushed to higher layer. Since downlink TCP frames are received faster than feedback channel is able to transmits TCP acks, throughput will suffer.

Initial bit rate in downlink/uplinkWCEL64 kbits/s

8 or 16 kbits/sIn loaded networks it may be useful to use lower initial bitrates

10. Telecom parameters

ParameterObjectDefaultRecommended valueComments

Cell rangeWCELDefault value is not possible10 or 20 km

With extended cell licence this can be 35, 60 or even 180 km

The maximum cell range can be 20 km when using two antennas and AICH Transmission Timing has value 1. If AICH Transmission Timing has value 0 or four antennas are used the maximum value can be up to 10 km.

In RAS06 (and later) with the extended cell feature the cell range can be extented from 20 km up to 180 km (with AICH transmission timing of 1). Separate Licence keys for 35,60 and 180 km feature.

PRACHDelayRange

WCEL3 (20km)4(60km), 5(180 km)This is RU10 parameter,value should be set according to extended cell licence.

PRACH Preamble Retrans MaxWCEL87These parameters makes RACH procedure slightly longer, giving the BTS more time to catch the RACH, at the same time decreasing the maximum power used in PRACH power ramping.

If this change is not made, there may be a risk for excessive peaks in the uplink cell load when operating at a high load (>40 AMR calls)

RACH maximum number of preamble cyclesWCEL816

Wait Time RRC registrationRNC1s5sThe time indicates the how long UE shall wait before sending the same RRC connection request message to the same cell.This change means to decrease the number of RRC pollution, useful with high load cells also.

Wait Time RRC interactive/backgroundRNC5s 8sThis is similar to above indicating the RRC wait time due to NRT blocking. When AC has rejected call, PS is the lowest priority with the most consuming resource. Minimise the chance for NRT call to attempt is recommended.

T3212RNC0 decihours6hThe value depens how it is set in VLR/CN. It is recommended to be half of the value of VLR/CN. Default value in VLR is 12 h.

T313WCEL3s6-8sIn some case, can reduce NRT call drop rate (in OSS KPI) by allowing more time before Ue sends Radio Link Failure indication. Note that end user experience is likely not improved.

N313WCEL20 50In some case, can reduce NRT call drop rate (in OSS KPI) by allowing more time before Ue sends Radio Link Failure indication. Note that end user experience is likely not improved.

T315WCEL4 (180 s)1 (10 s)It has been observed that a few terminals were in some case unable to perform a 2G reselection before the expiry of timer T315. Reducing timer to 10s minimizes the impact while maintaining PS drop performance.

11. Other parameters

ParameterObjectDefaultRecommended valueComments

MHA used

Cable loss

WCEL/AC

WCEL/AC MHA: MHA='Offset used', CableLoss=Feeder loss,

No MHA: MHA='Offset not used', CableLoss=N/ARAS06 (rel5) implementation has been changed. With MHA: Reference point for UL interference is at the antenna/MHA connector. Reference point for Primary CPICH TX power is also at antenna/MHA connector.Without MHA: Reference point for both UL interference and Primary CPICH TX power at the WBTS output. This meas that same reference point is used in open loop power calculations for RACH and Initial power calculations for DPCCH. It is recommended to use real cable loss values in WBTS commissioning files.

RNC, ZLCCControl Plane creation

INGRESS CDVT_PCR

EGRESS CDVT_PCRCalculatedWhen creating the IuPS interface against NSN SGSN, use value 14msec for CDVT in control plane, (when creating VC for IuPS signalling connection) NSN SGSN ATM traffic scheduling sends ATM cells with such variation that RNC NIS card traffic policing deletes cells if the interface is created with default parameters

StandAloneDCCHBitRate (Signalling radio bearer bit rate at RRC connection establishment)RNC34 (3.4 kbps), 136 (13.6 kbps)The parameter UsedSRBALCSet (Used SRB ALC set) allows to use StandAloneDCCHBitRate=13.6 kbit/s to reduce call setup delays without impact on Iub AAL capacity by defining an activity factor. Default value for UsedSRBALCSet is 3, which corresponds to an activity factor of 7.5% for a StandAloneDCCHBitRate of 13.6 kbps.

ParameterObjectDefaultRecommended

ValueComments

DRRCprxMarginWCEL-0.5 dB0 dBDirected RRC connection Setup parameter ; based on field measurements, target cell does not need to be at lower load in UL

DRRCptxMarginWCEL- 2 dB-0.5 dBDirected RRC connection Setup parameter ; based on field measurements, easier access to another frequency especially in the case for 384 kbits/s service

NbrofSCCPCHsWCEL13 3 is the value if Service Area Broadcast (SAB) is used

NforCTCHWCEL24This value should be used here if NbrofSCCPCHs is 3.

ConfAreaLevelWSMLC0100%67 %This is related to LCS (=location based services. There is no default value mentioned for this, but 67 % is given value from product line.

Note: All other LCS parameters should be carefully set, for example all those Antenna related parameters, to have accurate LCS results.

12. HSDPA related parameters

12.1 HSDPA power parametersThe most important BTS power related parameters are summarized in the table below for 8, 20 and 40W PA per cell configuration. Target values are given with and without optional feature HSDPA Dynamic Resource Allocation.

Figure 1: Recommended HSDPA power setting for different PA powers.

Note 1. The full BTS Power Amplifier power can be allocated in downlink without margin, for optimal capacity performance. However, some operators privilege more conservative allocation. Parameter WCEL:PtxCellMax has a default value of 43 dBm, and it MUST be adapted to the BTS PAs. In case of Metrosite BTS, the value MUST be set to 39dBm (or less), as it will not be set automatically by the system. The same rule applies to Ultrasite and Flexi BTS with 40W PAs: the PtxCellMax value must be set to 46dBm to benefit from the full PA power range. In RU10 BTS link adaptation reduces HS-PDSCH power for low data rate users and users who are in good radio conditions.Note2. PtxMaxHSDPA parameter in RAS06 does have an impact on Dynamic Resource allocation also, so it should be set higher value or even equal to PtxCellMax, to allow all left over power for HSDPA with DRA. More info in TN 107-2008.If Dynamic Resouce Allocation feature is activated, default values for parameter PSPtxTargetPSMin and PSPtxTargetPSMax is 40dB and must be lowered in case of Metrosite BTS or Flexi 8W license to respect the maximal value for these configurations (39dBm). In case of Dedicated carrier configuration, RRC layering must be activated.

12.2 HSDPA Dynamic Code AllocationParameterObjectDefaultRecommendedValueComments

HSPDSCHMarginSF128

WCEL80-4

This parameter will be used only with HSDPA 10 or 15 code feature. The parameter defines the required number of free SF128 channelisation codes left for DPCHs. The number of free DPCH codes after the HS-PDSCH code upgrade has to be equal or higher than the parameter value, otherwise the HS-PDSCH code upgrade is not allowed. Also, if the number of free DPCH codes is lower than the value of the parameter, periodical HS-PDSCH code downgrade can be initiated.

Minimum margin of 5 SF128 codes allows the allocation of up to 14 HS-PDSCH codes. HSUPA + 15 codes is possible with value 0 and with 2 HS-SCCH. If HSPA with high throughput is favoured instead of PS NRT value 0 can be used.

DPCHOverHSPDSCHThreshold

WCEL01-4NRT DCH connections can pre-empt codes allocated to HSDPA but in this case, the pre-emption can happen in case there is room in codes: # HS-PDSCH codes > Maximum code set- DPCHOverHSPDSCHThreshold

parameter. This parameter is applied if there are active HSDPA connections in the cell.

If this is set to zero thre will be more RRC setups with RT over NRT pre-emption which causes then BTS to be frozen and during the pre-emption all new requests to be queued which in turn can cause some delays to RRC setups and queue overflow and therefore rejections.

HSPDSCHAdjustPeriodRNC10s5sFaster adjustement period allows faster code allocation to HSDPA users.

12.3 Other Recommended HSDPA parametersParameterObjectDefaultRecommendedValueComments

HSDPARRCdiversity

(SHO of HSDPA capable UE)

RNCAllowedNot allowedOnly if HSDPA Serving Cell Change is disabled.

When Not Allowed, parameters ReleaseMarginAverageEcNo and ReleaseMarginPeakEcNo are used to define threshold for neighbouring cell to be added in to active set while having only SRB

AdditionTimeFMCS (HSDPA Id)6 (100ms)13 (1280ms)Only if HSDPA Serving Cell Change is disabled.

AdditionWindowFMCS (HSDPA Id)

2.5 dB

0 dB

If HSDPA Serving Cell Change is enabled, it is beneficial to delay the measurement report in order to maintain HSDPA service longer. Also due to capacity reasons it is recommended to set window as 0 dB to to save BTS WSPC capacity in the target cell. This does not have impact to the HSDPA throughput degradation during SCC.

EnableRRCReleaseHOPS (RT,NRT,HSDPA Id)0 (No)1 (Yes)0 (no)This parameter is related to Handover control, where rrc connection is released in case SHO fails (RT,NRT, HSDPA) due to interference. If activated it is also possible to see dropped calls (rab_act_fail_bts) if there is no room in CE of the target Node B. In case there are some BTS fails, deactivation of this will improve the call success rate (decrease rab_act_fail_bts).

ReleaseMarginAverageEcNoHOPS (HSDPA Id)2.5dB2dBThis set will allow shorter time before RRC release: WSPC CE savings.

DynUsageHSDPAReturnChannelRNC0 (Disabled)1 (Enabled)In case of high UL Channel Element usage, it is recommended to allow the use of ThroughputBasedOptimization for the HSDPA UL return channel. Note that both Throughput Based Optimization and Flexible Uprade features need to be enabled.

HSDPA16KBPSReturnChannel

RNC0 (disabled)1 (Enabled)This parameter change will improve HSPDA accessibility and maintain the RAB with lower throughput (RB downgrade) without releasing it in case of capacity problems.

Initial bitrate for HSDPA associated UL DCHRNC64 kbits/s16 kbits/sIn loaded networks it is recommended to use lower Initial bitrate in order to save capacity.

HSDPAminAllowedBitrateURNC64 kbits/s16 kbits/sIn loaded networks it is recommended to use lower Initial bitrate in order to save capacity.

MaxBitRateNRTMACDFlowRNC3456 kbps3456kbps

6784kbps

9600 kbpsFor basic HSDPA 5 Codes (QPSK/16QAM), MaxBitRateNRTMACDFlow=3456kbps

For basic HSDPA 10/15 Codes, MaxBitRateNRTMACDFlow=6784kbps

For HSDPA 10Mbps per User, MaxBitRateNRTMACDFlow=9600 kbps.

Code Tree UsageWCEL 40 %60 %This is the default without HSDPA feature. With HSDPA enabled in the cell the code tree usage is already about 38 %. The recommendation is to use 60 %.

AM RLC maxRST transmissions for PS NRT with HS-DSCH (the amount of RESET PDUs)

RNC1224This parameter defines the value of the RLC protocol parameter MaxRST for the AM RLC entity of the PS interactive and background radio bearers when data is transferred over HS-DSCH. It has been hidden parameter before RAS06.

The change will have less RL failures and improved HSDPA retainability.RLC unrecoverable error with new settings = 15*300ms+24*300ms = 11.7s

RLC unrecoverable error with old settings = 15*200ms+12*200ms = 5.4sThe reason for increasing the timer values for PS NRT is to reduce the propability that the RLC does the unrecoverable error due to the retransmissions by reducing the RLC polling frequency.

AM RLC status period max for PS NRT with HS-DSCH (periodic polling and reset polling repeat interval from 200 to 300ms)

RNC133 %300 %This parameter defines the maximum status reporting period of the AM RLC in relation to the RLC round trip time for the PS interactive and background radio bearers when the data is transferred over HS-DSCH. It has been hidden parameter before RAS06.

The change will have less RL failures and improved HSDPA retainability.

AM RLC status period max for PS NRT with DCH (periodic polling and reset polling repeat interval from 200->300/400/500 ms depending on TTI length, 300ms in HSDPA return channel case)

RNC140 %300 %This parameter defines the maximum AM RLC status reporting period of the AM RLC in relation to the RLC round trip time for the PS interactive and background radio bearers when data is transferred with DCH. Hidden parameter before RAS06.

AM RLC MaxRST transmissions for PS NRT with DCH (the amount of RESET PDUs)

RNC 1224This parameter defines the value of the RLC protocol parameter MaxRST for the AM RLC entity of the PS interactive and background radio bearers when data is transferred with DCH. Hidden parameter before RAS06.

AM RLC maxRST transmissions for PS NRT with E-DCHRNC1224RLC parameter for HSUPA

AM RLC status period max for PS NRT with E-DCHRNC133 %300 %RLC parameter for HSUPA

13. Other Optional features

13.1 Priority Based SchedulingParameterObjectDefaultRecommendedValueComments

InitialBitRateDLWCEL64 kbps128 kbpsIf optional features PBS (Priority Based Scheduling) and TBO (Throughput Based Optimization) are enabled, it is beneficial for throughput time to start at a higher initial bitrate. If PBS is not enabled, a degradation of the Capacity Request success ratio is in some case possible.

MinAllowedBitRateDL

WCEL32 kbps (RAS5)

8 kbps (RAS51-RU10)8kbpsMinAllowedBitRateDL is now distinct from InitialBitRateDL and thus the lowest possible bitrate can be used to allow lowest avialble resource utilization when needed (in overload situation)

13.2 Flexible Upgrade & Throughput Based Optimization

ParameterObjectDefaultRecommendedValueComments

FlexUpgrUsageRNCOffOnTo allow all upgrade scenarios.

DCHUtilHighAveWin1000 ms0 msIf FlexUpgrUsage = on, DCHUtilHighAveWinshould be set to 0 to avoid detail in RAB upgrage

PSOpThroUsageRNC0b000000000b11110000If the PS Throughput Based Optimization feature is licensed, it should be enabled for all NRT traffic classes and traffic handling priorities

DCHUtilUpperAveWin

DCHUtilLowerAveWinRNC2s1sIf a high proportion of NRT traffic if of ip streaming type, faster reconfiguration to adequate bitrate is beneficial. The same value can be applied t obitrate in range 32..384.

DCHUtilUpperTimeToTrigger

RNC4s2sIf a high proportion of NRT traffic if of ip streaming type, faster reconfiguration to adequate bitrate is beneficial. The same value can be applied to bitrate in range 32..384.

DCHUtilLowerTimeToTriggerRNC1.4s0.8sIf a high proportion of NRT traffic if of ip streaming type, faster reconfiguration to adequate bitrate is beneficial. The same value can be applied to bitrate in range 32..384.

DCHUtilMeasGuardTimeRNC6s2sIf TimeToTrigger and AveWin are reduced as recommended above, then DCHUtilMeasGuardTime should be reduced to avoid being a bottleneck.

13.3 Narrowband AMR Codecs

ParameterObjectDefaultRecommendedValueComments

DLpuncturingLimit

RNC7 (68%) (RAS5)

5(60%) (RAS51)5 (60%)To allow SF256 usage with lower narroband AMR codec

DLmaxBitRateSF256RNC27 kbit/s35 kbit/sTo allow SF256 usage with lower narroband AMR codec

13.4 Load and Service Based Handover

ParameterObjectDefaultRecommendedValueComments

LHOHardBlockingRatioWCEL50%10%It is recommended to make the trigger more sensitive to be reacting faster to HW overload situation for LHO

LHOHardBlockingBaseLoadWCEL105It is recommended to make the trigger more sensitive to be reacting faster to HW overload situation for LHO

LHOPwrOffsetDLWCEL-1.5 dB0 to -0.8dBSetting the LHO trigger 1.5 dB below PtxTarget value might trigger unnecessary LHO, while DL load is still normally loaded.

14. RU10 Default changes with C-Iub

Related to Common Iub feature support in RU10 some RAS06 defaults have been changed. In case there is no need for common Iub RAS06 default values should be used instead.

ParameterObjectDefaultRecommendedValueComments

RRIndPeriod

WBTS400ms200msThe change was to align WBTS RRInd Period and NBxxx with Prx/PtxTotalReportPeriod, minimum value of 800 ms possible. Used with C-iub only.

PrxTargetPSAdjustPeriodWBTS510RAS06 default can be used without C-Iub

PtxTargetPSAdjustPeriodWCEL510RAS06 default can be used without C-iub

SchedulingPeriodWBTS100ms 200msRAS06 default can be used without C-iub

LoadControlPeriodPSWBTS2000ms1200msRAS06 default can be used without C-iub

PSAveragingWindowSizeWBTS42RAS06 default can be used without C-iub

15. HSUPA Parameters ParameterObjectDefaultRecommendedValueComments

MaxTotalUplinkSymbolRateWCEL1920 kbps3840 kbpsIn case HSUPA2.0 is used

FactorEDCHMaxBitRateRNC1.55In case HSUPA2.0 is used, to avoid having HLR as limiting factor in HSUPA throughput

NumberEDCHReservedSHOBranchAdditionsWCEL20-1With default of 2 used with 3 HSUPA license only it is not possible to have more than one HSUPA connection in the cell in case of HSUPA SHO.

Delay ThresholdMaxRNC8 ms100 msHSUPA cong. control,see TN SW_127

Delay ThresholdMidRNC4 ms 70 msHSUPA cong. Control,see TN_SW_127

Delay ThresholdMinRNC1 ms50 msHSUPA cong. Control, see TN_SW_127

ProbabilityFactorMaxRNC0.80.1HSUPA cong. Control, see TN_SW_127

16. TECHNICAL NOTES

Below is link to all Technical Notes to be recommended to be used, see the latest ones also.TS-RNC-SW-122RNC Licence Keys - Capacity Expansion Problem

TS-RNC-SW-123RN3.0 upgrade conversion corrections

TS-RNC-SW-124Monitoring of RNC DSP capacity usage

TS-RNC-SW-125RNC CDSP-C UPDATE

TS-RNC-SW-126Clearing OMS Alarm DB

TS-RNC-SW-127Modification to HSUPA Congestion Control default parameters

https://www.online.nokia.com/nols/doccenter/dcpageflow/viewDocumentDetails.do?parentObjectId=0b00cc928015f319