P. 1
NPO_Rec_Parameters_for_Radio_ RU20

NPO_Rec_Parameters_for_Radio_ RU20

|Views: 477|Likes:
Published by djemai chergui
NPO Recommended Parameters for Radio RU20-
3G optimization NSN
NPO Recommended Parameters for Radio RU20-
3G optimization NSN

More info:

Published by: djemai chergui on Feb 03, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

09/06/2014

pdf

text

original

Guideline NPO NSN/SBU/MS 23.04.

2010 For internal use only

RU20

NPO Recommended Parameters for Radio

Guideline NPO NSN/SBU/MS 23.04.2010 For internal use only

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is 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 2013. All rights reserved.

..............................19 12...........................................................................................................04......... RU10 Default changes with C-Iub.................................................................................4 Load and Service Based Handover.........................21 13............................................................ SHO parameters......................................................................... Idle mode parameters....................................2 Flexible Upgrade & Throughput Based Optimization.............. Packet Scheduling parameters....................................11 7.........2 HSDPA Dynamic Code Allocation............. Other parameters.......6 3................ TECHNICAL NOTES...........................................................................................12 8..Guideline NPO NSN/SBU/MS 23.......................................... Inter-System Handover parameters.................................................. HSDPA related parameters....................................................................................................................................................................................7 3...........7 3..........................................................................24 13.............................................17 12..........................................................................1 Priority Based Scheduling.7 4................................2 Idle Mode GSM Parameters.............................................................24 13...................................................... Inter-frequency Handover parameters...............13 10.........................................25 15........................................25 16......... Telecom parameters..........................................................................................................................................1 Idle Mode WCDMA Parameters...........3 Narrowband AMR Codecs................ Power Control parameters............................................................................19 12.............................................................................................26 .............................9 6..............................................................................................................................................................................15 11...............25 13......................................................................................13 9..............................1 HSDPA power parameters..............................................................2010 For internal use only Table of contents 2............3 Other Recommended HSDPA parameters..................................20 12................25 14................................. Admission Control parameters....................................................................................8 5..................................... HSUPA Parameters ....24 13................................. Introduction........................................................................................................ Other Optional features..............................................................................................................

Correction to the Offset for activation time.2004 OS Performance 13.12.3.2.01.2005 OS Performance 2. IuBarringRecoveryTimer: modified StandAloneDCCHBitRate: added Chapter 12: HSDPA: added Modified SharedHSDPAFlowControlAllocation description Main RAS51 update: Added T313.2 3. Reference to TN 047 added + corrections to the text. PowerRampStepPRACHpreample changed from 1 dB to 2 dB =default RAN04 only parameters have been added as separate chapter. Deleted default values defined in system compared to 2.4. AdjsSIB and AdjgSIB parameters added.5.4.2 RAN1.2 latest release + RAN04 first release.0 2. Also RAN 1.6.0.0 3.4 kbits/s and 13.2010 For internal use only Change History Issue 1.0 14.0 31.1.2005 OS Performance New parameters added: Power control algorithm 1 TinTr and TigOr MSactivitySupervision CodeTreeOptimisation Offset for activation time PtxDLAbsMax T3212 Corrections to implementation of Sib3compmask2 SIB3compmask5 QsearchC FDD_Qmin Corrections to the parameters related to ROC BTS.6. Corrections to the parameters related to MHA and Cable loss.4. T317 change : 180s-> 10s (time from cell_fach-> idle in case of “out of service”) Modifications to cable loss parameter (TN62). Wait time RRC interactive and Wait time RRC background parameter added.2005 OS Performance 5.3.Guideline NPO NSN/SBU/MS 23.7.5. or are read only by the system have been taken out.2006 C&I 3.5 parameters which cannot be changed. GSM HO caused by DL DPCH TX Power change: false-> true Combined LAU/RAU on BSS side (Gs interface).2003 30.1 27.N313 2.5 parameters which has now optimal values as default values in parameter database has been taken out.1 2.2004 Handled by Comments RNC Technical Support RAN1.1 & 1.2005 OS Performance 2.0 2.0. IuBarringRecoveryTimer parameter added.12.2002 31. Modifications to maximum measurement period (ISHO) parameter.12. update OS Performance 2.6 kbits/s SRB. SDUdiscardModeRTPS (for RAN04 streaming service) RAN04 Initial and minimum bitrate change in UL: 16-> 32 kbits/s ATO change to 700ms for both 3.2005 OS Performance 14.10. CPICHtoRefRABOffset and PCRangeDL parameters added.0 2.6.0. Comments to the ToAWS and ToAWE parameters. ToAWS/ToAWE parameters added for NRT cases in RAN04.0 2.2 ED2 OS/NPS RAN1.0 06.8.2 ED2. Valid for RAN1. Updated with the following info.2006 31.0 10. Also RAN1.0 Date 20.04. 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: added HHO triggers for NRT Services: added IFHO caused by UE TxPower:added CodeTreeOptimisation: modified T312: deleted T317: deleted ToAWS/ToAWE: deleted.5.3.2007 C&I C&I .5. Parameter name orthograph changed.11.05.5.5.0.2004 OS Performance 13.0 Main RAS´5 update: Qhyst2: comment added SIB3Compmask2 and SIB3Compmask5: value and comment modified AdjgSIB and AdjsSIB: now modifiable FddQmin: new recommended value.1.

2007 4.2 4. Reference point for UL interference changed in RAS06 with MHA. Added HSDPA RAS6 and HSUPA parameters section Change 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 BTS Change in ISHO thresholds.10.2 F.6 Approved by: 1. TBO.7 29.1 31.1.0 24.2008 NPO 18. C-Iub changes.7. Change in AM RLC protocol parameters for NRT Recent Techical Notes added Sib3compmask parameters are hidden and fixed in RN2. RU10 parameter recommendations added: TN SW 127.4.2007 CSI CSI Added DedicatedMeasReportPeriod AltScramblingCodeCM: disabled when HSDPA is enabled Added T315 Update for new RAS51 features: LSHO.Guideline NPO NSN/SBU/MS 23.2008 NPO 29.1. AMR MB codecs Modified description of several parameters in “12.04. Minor corrections to HSPDSCHMarginSF128 and DPCHOverHSPDSCHThreshold parameters based on the field tests. due to HSDPA Serving Cell Change feature.2 4.1 4. Reymond .2009 21.9. excel version added based on object classes.2010 NPO NPO NPO Editor: Pekka Ranta Date: 23.2010 Version: 1. NSN look and feel Removed RAN4 default values FDD_QMIN: removed pre-rel4 table values Qhyst1 removed as default value was updated Removed RASS5 static power allocation settings.3 Other Recommended HSDPA Parameters”.5 4.4 4.3. Prachdelay range added First Version for RU20.4.1.12.2008 NPO 16.2008 NPO 30.3 4.4. HSDPA Dynamic power allocation.2009 23.4. RRC enable release and drop reporting interval. DPCHOverHSPDSCHThreshold added to have to always allow NRT DCH over HSDPA code pre-emption PrxLoadMarginMaxDCH added Some range values added instead of pure numbers.8.2008 NPO 4.1. 4.04.1.12. SHO parameters due to SRB blocking Minor corrections to cell range.2010 For internal use only 3.1 4.6 4. some parameters were taken out (optimum value set as default).

Thus these parameters are only better defaults to start the optimization. There are also some GSM parameters which have to be modified from BSC (MML commands). . so there could be some modifications needed for Sanyo or NEC mobile phones compared to NSN.04. In this document there are some information related to those Ues. 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.Guideline NPO NSN/SBU/MS 23. 3G network topology is varying a lot which means that the radio network 6ptimization activities will be needed anyway to improve the radio network performance. Each modification should be evaluated on a case-by-case basis. For RU20 release there is no changes to Radio. The parameters changes are categorized as • • Idle more WCDMA/GSM parameters Mobility o o o • RRM o o o o • Admission control parameters Packet Scheduling parameters Telecom Parameters Power Control parameters Soft HO Parameters Inter-System handover parameters Inter-Frequency handover parameters HSDPA (RAS05 onwards) and HSUPA (RAS06 onwards) parameters It is possible to view/modify all listed 3G parameters using RNC RNW Object Browser. taking into account the local environnement and target network configuration.2010 For internal use only 2. Different Ues may have different impact to the performance.

. Note: actual value based on MINIMUM FDD THRESHOLD (Fdd_Qmin) . 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). 6-8 dB hysteresis recommended (if Qqualmin+ SsearchRAT=-16. 0 dB hysteresis can be used in the area of high mobility. 0s can be used in areas having high mobility like in highways.-10 dB Comments Should be balanced with QqualMin and SsearchRAT to reduce ping-pong. It is preferable to avoid removing intra-frequency adjancencies Comments Qhyst2 (Cell resection hysteresis 2.Guideline NPO NSN/SBU/MS 23. for EcNo) 4dB for WCDMA cells near different LA unless compensated by AdjsQoffset2 (per adj) 0 dB 0s AdjSSIB ADJS 1 0 AdjGSIB AdjISIB ADJG ADJI 1 1 0 0 3.2010 For internal use only 3.2 Parameter Idle Mode GSM Parameters Object BTS Default 0 (-20 dB) Recommended value -6.1 IDLE MODE PARAMETERS Idle Mode WCDMA Parameters Idle mode parameters should be optimized to improve the call setup success rate. which can contribute to improve HSDPA accessability. The parameters are set by the system to the default value 1 (yes). Parameter Object WCEL Default values 2 dB Optimized values 4 dB 2 dB 2 dB hysteresis between WCDMA cells can be used in Urban environment to avoid ping pong. Thus there is less signaling and less call failures at LA/RA border due to LA/RA update. 2dB (or less) enables faster cell reselection.04. All the neighbour cells are included into system information block (SIB11/12) by default. Cell reselection triggering time (Treselection) WCEL 2s 2s 2s reselection time helps avoid too many cell reselections between cells and hence LA/RA updates when crossing LA/RA border. 3. Fdd_Qmin= -8 dB.

MI info is not send. ReplacementTime FMCS 100ms 640ms . QSRI GPRS Multi RAT MS Qual (QsearchP) (GSM). HSPA and AMR+ HSPA.2) dB for (Addition. If set to 15 Measurement Information (MI) is send anyway (even though UE should not measure 3G neighbours with that value 15). This is valid in S10.4. Only if both features are not used. Drop and Replacement Window) values.5s 0. UE will measure always 3G cells if they are defined neighbours.6.5. QSRC BTS 15 (no meas) 7 (=always) HOC 15 (no meas) 7 (=always) UE interpretation. see above. respectively Parameter DropreportingInterval ReplacementReporting Interval ReplacementWindow Object FMCS FMCS FMCS Default values 0. SHO PARAMETERS Note: From RAS05 onwards. QSRP Multi RAT MS Qual (QsearchC). Current default trigger setting of SHO event 1C causes plenty of events to be reported in RU10-> SRB blocking SRB Blocking. Note: In case ISHO_SUPPORT_IN_BSC or EMR_SUPPORT_IN_BSC features are used the parameter values set with QSRI.5 ED and S11. respectively NRT traffic uses default set of values of (2.Guideline NPO NSN/SBU/MS 23.5. 4.2) dB for (Addition.NRT traffic. Drop and Replacement Window) values.2010 For internal use only Non GPRS Multi RAT MS Qual (QsearchI) (GSM). QSRP or QSRC do not affect to the Measurement Info message and MI is always send by Mobile. However in RU10 there are some modifications needed. the default system value for FMCS parameters is equivalent to the optimal recommendation. if ISHO_SUPPORT_IN_BSC or EMR_SUPPORT_IN_BSC features are used. On the other hand this will have effect to the UE battery life time.5s 2 dB Recommended values 1s (3) or disabled (0) 1s 4-6 dB Comments This is to related to first observations about SRB blocking in RU10 -> decrease signaling with this change This is to related to first observations about SRB blocking in RU10 -> decrease signaling with this change RU10 priorizes branch additions over branch deletions to enable fast addition of new cell and decrease call drop rate. Several customers use 4 FMCS sets: for RT. RT traffic uses default set of values of (4.04. S10.

which is by default 384 kbits/s in RAN ´04 / RAS´05. the bitrate threshold concerns only RT data (CS or PS) connections. It is recommended to use at least 12. In case of bad uplink DCH quality. Comments GSM HO caused by CPICH Ec/No GSM HO caused by CPICH RSCP GSM HO caused by UE Tx Power UE TX Power Filter Coefficient GSM HO caused by DL DPCH TX Power FMCG Disabled Enabled Maximum Measurement Period FMCG 6 measurement reports 12 measurement reports to 20 measurement reports Handover of NRT PS Service to GSM Maximum Allowed UL User Bitrate in HHO RNC/H C&PC WCEL No 32 kbits/s Yes 384 kbits/s . Decreases the probability for ‘no cell found’ in ISHO. so DL power should be enabled to avoid dropped call. also the delay depends on the length of neighbour list. The RNC is not aware of which TF the UE is using.Guideline NPO NSN/SBU/MS 23. at least 60 ms.04.2010 For internal use only 5. Used only with high UE TX power level (RT&NRT) or bad uplink DCH quality triggers. Some Ues are performing ISHO under good RF conditions due to peaks of high BLER. Parameter INTER-SYSTEM HANDOVER PARAMETERS Object FMCG FMCG FMCG FMCG Default values Disabled Disabled Disabled 10 ms Recommended values Enabled Enabled Enabled 60 ms In case GSM HO caused by UE Tx Power is enabled. too short delay to trigger ISHO. This parameter value should be aligned with MaxBitRateULPSNRT. ISHO delays of 5 s has been measured. In case PS ISHO is activated FMCG needs to be added in cell parameter window. 10 ms. 6 is often too low in environment where 2G BCCH reuse is high. Consider using longer period.

-105dBm. -9dB. CPICH RSCP HHO Cancel for NRT Services DedicatedMeasReportPeriod FMCS RT -12dB. CPICH Ec/No HHO Cancel.5 s -14.-110 dBm -105. -105dBm. Even EcNO trigger for NRT could be disabled. Requires cell locking prior to change.. When ISHO “Downlink Link Power” trigger is in use. when initialized) for sending dedicated measurement reports to the RNC related the power on DCH channel. Due the signalling delays at inter-system change caused by LU and RAU..-18 dB..04. reducing this parameter to 0. it is beneficial to leave UMTS as late as possible.. CPICH RSCP HHO Threshold..-16 dB -10.-18 dBm 0. -110dBm Lower values for for NRT services to increase the coverage area. -9dB. This parameter determines the reporting interval that Node B should use (by default. -102dBm -16. FMCS HSDPA -12dB. Absolute Isho number (and ISHO) drops will be decreased. CPICH Ec/No HHO Threshold.Guideline NPO NSN/SBU/MS 23. CPICH RSCP HHO Cancel for NRT Services FMCS NRT. -115dBm.. Lower values for RT to have more coverage.5 seconds allows faster ISHO and can help reduce drop rate. valid for HSDPA also. -102dBm 2.5 s WBTS .-14 dB. -12. CPICH RSCP HHO Threshold. and due to the low bit rate available in GPRS network without EDGE. CPICH Ec/No HHO Cancel.-12 dB -108.2010 For internal use only CPICH Ec/No HHO Threshold.

Parameter INTER-FREQUENCY HANDOVER PARAMETERS Object FMCI FMCI FMCI FMCI Default values Disabled Disabled Disabled 10 ms Recommended values Enabled Enabled Enabled 60 ms In case IFHO caused by UE Tx Power is enabled (see above).2010 For internal use only 6. This should be in line with ISHO delay. Consider using longer period. Comments IFHO caused by CPICH Ec/No IFHO caused by CPICH RSCP IFHO caused by UE TxPower UE TX Power Filter Coefficient Maximum Measurement Period FMCI 20 meas report 12 meas report . at least 60 ms.04.Guideline NPO NSN/SBU/MS 23. 10 ms. too short delay to trigger IFHO.

This change is needed to compesate the increase of CPICHtoRefRABoffset mentioned above. CPICHtoRefRABoffset (Offset of the P-CPICH and reference service powers) PcrangeDL (Radio link downlink power control range) RNC 15 dB 20 dB Required received C/I on PRACH at WCDMA BTS WCEL -25 dB -20. no AICH). This has not any negative impact such as increased noise level or spikes. 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.Guideline NPO NSN/SBU/MS 23.e. no response from BTS to RRC Connection Request (i. 21-22 dB can be used with negative CPICHtoRefRABOffset With increased traffic and the fluctuation of noise levels the default value -25 just leads to unnecessary unanswered RRC connections or pages i. This can be avoided by adjusting the parameter to -20dB. thus max radio link power for AMR should be increased also..-18 dB .04. With high HSDPA traffic the increased interference will decrease the EcNo level. which could mean increased peak power for AMR. Parameter POWER CONTROL PARAMETERS Object WCEL Default 2 dB Recommended value 0 dB -1…-2 dB (with high HSDPA traffic) Comments This change means that the maximum link power for a connection is increased by 2 dB to improve the DL coverage.2010 For internal use only 7.e.

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. For full improvement in call MSActivitySupervision (MS activity supervision timer) (Time supervision of user inactivity (for NRT RBs)) PtxDLabsMax (Planned maximum downlink transmission power of a radio link) WCEL 37 dBm 35-37 dBm Offset for activation time RNC 300ms 400. It will limit the planned maximum limit for the radio link. It is recommended not to use throughput based AC algorithm for R99 PS service but for HSUPA. This parameter is related to the Dynamic Link Optimization feature. with the cost of lower CSSR & higher CDR. Needs to be evaluated case-by-case based on Ue mix in network.2010 For internal use only 8. Parameter ADMISSION CONTROL PARAMETERS Object WCEL Default 2 dB (0 dB in RU10) Recommended value 0 dB Comments In RAS06 onwards UL AC could be based on both throughput and power based PS call algorithm depending on the parameter settings. 500 ms has been tested with success in some cases. Can impact Packet RAB drop rate and AMR/Video RAB setup success rate. PrxLoadMarginMaxDCH (Interference margin for the maximum UL DCH load) 9.500 ms . The optimised value for PtxDLAbsMax is between 3537dBm based on the various measurements. Parameter PACKET SCHEDULING PARAMETERS Object RNC Default 29 min Recommended value 15 min Comments MSActivitySupervision timer is used in Cell_PCH state for supervising the inactivity of NRT RAB(s).Guideline NPO NSN/SBU/MS 23.04. 300 ms optimizes call set up time. 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.

If there is some TCP re-transmissions. MinAllowedBitRateDL/UL (Initial and minimum allowed bit rate in DL/UL) WCEL Uplink 8 kbit/s Downlink 8 kbit/s UL/DL 8. This is due to low throughput on FTP type of services by using TCP. Since downlink TCP frames are received faster than feedback channel is able to transmits TCP acks.6 kbps..2010 For internal use only setup time the SRB size should be set to 13. In loaded networks it may be useful to use lower initial bitrates Initial bit rate in downlink/uplink WCEL 64 kbits/s 8 or 16 kbits/s . these can cause large queue of TCP frames buffered in RLC and then pushed to higher layer.32 kbit/s Optionally consider using recommended values: UL/DL = 32/32 kbits/s.04.Guideline NPO NSN/SBU/MS 23. throughput will suffer.

Minimise the chance for NRT call to attempt is recommended. 5(180 km) 7 16 Wait Time RRC registration RNC 1s 5s Wait Time RRC interactive/background RNC 5s 8s T3212 RNC 0 decihours 6h . This is RU10 parameter.This change means to decrease the number of RRC pollution. Parameter Cell range TELECOM PARAMETERS Object WCEL Default Default value is not possible Recommended value 10 or 20 km With extended cell licence this can be 35.Guideline NPO NSN/SBU/MS 23. Separate Licence keys for 35.2010 For internal use only 10. If this change is not made. 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). PRACHDelayRange PRACH Preamble Retrans Max RACH maximum number of preamble cycles WCEL WCEL WCEL 3 (20km) 8 8 4(60km). PS is the lowest priority with the most consuming resource.60 and 180 km feature. 60 or even 180 km Comments The maximum cell range can be 20 km when using two antennas and AICH Transmission Timing has value 1. When AC has rejected call.value should be set according to extended cell licence. useful with high load cells also. These parameters makes RACH procedure slightly longer. It is recommended to be half of the value of VLR/CN. Default value in VLR is 12 h.04. This is similar to above indicating the RRC wait time due to NRT blocking. The value depens how it is set in VLR/CN. giving the BTS more time to catch the RACH. there may be a risk for excessive peaks in the uplink cell load when operating at a high load (>40 AMR calls) The time indicates the how long UE shall wait before sending the same RRC connection request message to the same cell. at the same time decreasing the maximum power used in PRACH power ramping.

Guideline NPO NSN/SBU/MS 23.2010 For internal use only T313 WCEL 3s 6-8s N313 WCEL 20 50 T315 WCEL 4 (180 s) 1 (10 s) In some case. Reducing timer to 10s minimizes the impact while maintaining PS drop performance. . It has been observed that a few terminals were in some case unable to perform a 2G reselection before the expiry of timer T315. Note that end user experience is likely not improved. Note that end user experience is likely not improved. can reduce NRT call drop rate (in OSS KPI) by allowing more time before Ue sends Radio Link Failure indication.04. In some case. can reduce NRT call drop rate (in OSS KPI) by allowing more time before Ue sends Radio Link Failure indication.

CableLoss=N/A Comments RAS06 (rel5) implementation has been changed. (when creating VC for IuPS signalling connection) 136 (13.2010 For internal use only 11.Without MHA: Reference point for both UL interference and Primary CPICH TX power at the WBTS output. Reference point for Primary CPICH TX power is also at antenna/MHA connector. No MHA: MHA='Offset not used'. which corresponds to an activity factor of 7. Parameter MHA used OTHER PARAMETERS Object WCEL/AC Default Recommended value MHA: MHA='Offset used'. ZLCC Control Plane creation INGRESS CDVT_PC R EGRESS CDVT_PC R RNC Calculated StandAloneDC CHBitRate (Signalling radio bearer bit rate at RRC connection establishment) 34 (3. .6 kbps. It is recommended to use real cable loss values in WBTS commissioning files.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.Guideline NPO NSN/SBU/MS 23. use value 14msec for CDVT in control plane.5% for a StandAloneDCCHBitRate of 13. This meas that same reference point is used in open loop power calculations for RACH and Initial power calculations for DPCCH. With MHA: Reference point for UL interference is at the antenna/MHA connector.04. 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 Cable loss WCEL/AC RNC. When creating the IuPS interface against NSN SGSN.6 kbps) The parameter UsedSRBALCSet (Used SRB ALC set) allows to use StandAloneDCCHBitRate=13.4 kbps). CableLoss=Fee der loss.

2010 For internal use only Parameter Object Default Recommended Value Comments DRRCprxMargin DRRCptxMargin WCEL WCEL -0. to have accurate LCS results. easier access to another frequency especially in the case for 384 kbits/s service 3 is the value if Service Area Broadcast (SAB) is used This value should be used here if NbrofSCCPCHs is 3. target cell does not need to be at lower load in UL Directed RRC connection Setup parameter . .04. based on field measurements. for example all those Antenna related parameters.Guideline NPO NSN/SBU/MS 23. based on field measurements. There is no default value mentioned for this.5 dB .5 dB NbrofSCCPCHs NforCTCH ConfAreaLevel WCEL WCEL WSMLC 1 2 0…100% 3 4 67 % Directed RRC connection Setup parameter .2 dB 0 dB -0. This is related to LCS (=location based services. but 67 % is given value from product line. Note: All other LCS parameters should be carefully set.

the value MUST be set to 39dBm (or less).0 0.6 8.1 0.8 7.1 42 15.9 32 1.9 32 1.6 36 4. Note2. Parameter WCEL:PtxCellMax has a default value of 43 dBm.8 4.0 39 7.9 2 31.8 38.0 43 20. However.0 31.5 PtxMaxHSDPA (in Watts) 7. In RU10 BTS link adaptation reduces HS-PDSCH power for low data rate users and users who are in good radio conditions.8 45.8 6.0 Shared HSDPA carrier 43 46 39 20.0 7. The full BTS Power Amplifier power can be allocated in downlink without margin.0 6.1 HSDPA RELATED PARAMETERS HSDPA power parameters The most important BTS power related parameters are summarized in the table below for 8.6 dBm W Dynamic resource allocation (RAS06) PtxTargetPSMin 36 PtxTargetPSMin (in Watts) 4.0 43 20.6 0.6 dBm W PtxTargetPSMax PtxTargetPSMax (in Watts) Min.0 6.04. PtxMaxHSDPA parameter in RAS06 does have an impact on Dynamic Resource allocation also.0 0.8 45.6 38. PtxCellMax PtxCPICH.2 0.8 7.0 43 20.0 39.0 40 10. so it should be set higher value or even equal to PtxCellMax.6 8.1 42.5 35.8 6. some operators privilege more conservative allocation.0 15.0 37 5.8 45 31. Target values are given with and without optional feature “HSDPA Dynamic Resource Allocation”.9 dBm W W Figure 1: Recommended HSDPA power setting for different PA powers.8 6.0 31.6 0.6 38.0 33 42 15.6 40 10. In case of Metrosite BTS. 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).1 0.5 38.Guideline NPO NSN/SBU/MS 23.0 10. and it MUST be adapted to the BTS PAs.0 1.3 dBm W PtxTargetHSDPA PtxTargetHSDPA (in Watts) 37.3 42.9 Dedicated HSDPA carrier 43 46 39 20.5 7. RRC layering must be activated.8 36 45 31.0 1.2010 For internal use only 12.3 33 42 15.8 7. Note 1.6 38 6.3 dBm dBm W PtxOffset PtxTarget+PtxOffset (in Watts) 1.0 dBm W PtxOffsetHSDPA PtxTargetHSDPA+PtxOffsetHSDPA (in Watts) Min.5 17.6 8.0 15.6 29 38 6. 20 and 40W PA per cell configuration.9 2 31.0 4.8 7. power available for HSDPA 40 10.0 19.8 38.0 12.8 12.2 0.0 42 15.1-RAS06) PtxMaxHSDPA 38.2 7.2 38 6. More info in TN 107-2008. dBm PtxTarget PtxTarget (in Watts) Default 43 20.0 37 5. 12.1 45 31.8 42.1 0.8 19.9 0.9 dBm W 33 40 10.0 39. In case of Dedicated carrier configuration.6 29 38 6.8 36 45 31. . power available for HSDPA 0.0 10. to allow all left over power for HSDPA with DRA. If Dynamic Resouce Allocation feature is activated.0 7.0 dBm W W PtxHighHSDPAPwr PtxHighHSDPAPwr (in Watts) 42 15.8 45.3 1. as it will not be set automatically by the system.8 19.9 36 4.3 dBm W Dynamic Power allocation (RAS5.8 7.0 40 10.8 12. 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.0 39 7.0 36 4. for optimal capacity performance.

Guideline NPO NSN/SBU/MS 23. This parameter is applied if there are active HSDPA connections in the cell. The parameter defines the required number of free SF128 channelisation codes left for DPCHs. periodical HS-PDSCH code downgrade can be initiated. The number of free DPCH codes after the HSPDSCH code upgrade has to be equal or higher than the parameter value.2 Parameter HSDPA Dynamic Code Allocation Object WCEL Default 8 Recommended Value 0-4 Comments This parameter will be used only with HSDPA 10 or 15 code feature. If HSPA with high throughput is favoured instead of PS NRT value 0 can be used. Also.04. If this is set to zero thre will be more RRC setups with RT over NRT preemption 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. otherwise the HS-PDSCH code upgrade is not allowed. if the number of free DPCH codes is lower than the value of the parameter. NRT DCH connections can pre-empt codes allocated to HSDPA but in this case. HSUPA + 15 codes is possible with value 0 and with 2 HS-SCCH. Faster adjustement period allows faster code allocation to HSDPA users. Minimum margin of 5 SF128 codes allows the allocation of up to 14 HSPDSCH codes. HSPDSCHMarginSF128 DPCHOverHSPDSCHThreshold WCEL 0 1-4 HSPDSCHAdjustPeriod RNC 10s 5s . the pre-emption can happen in case there is room in codes: # HSPDSCH codes > Maximum code setDPCHOverHSPDSCHThreshold parameter.2010 For internal use only 12.

HSDP A Id) 0 (No) 1 (Yes) 0 (no) ReleaseMarginAverageE cNo DynUsageHSDPAReturn Channel HOPS (HSDPA Id) RNC 2. This set will allow shorter time before RRC release: WSPC CE savings. where rrc connection is released in case SHO fails (RT. In case there are some BTS fails. This does not have impact to the HSDPA throughput degradation during SCC. MaxBitRateNRTMACDFlow=3456kbps For basic HSDPA 10/15 Codes. parameters ReleaseMarginAverageEcNo and ReleaseMarginPeakEcNo are used to define threshold for neighbouring cell to be added in to active set while having only SRB Only if HSDPA Serving Cell Change is disabled. For basic HSDPA 5 Codes (QPSK/16QAM). it is beneficial to delay the measurement report in order to maintain HSDPA service longer. This parameter change will improve HSPDA accessibility and maintain the RAB with lower throughput (RB downgrade) without releasing it in case of capacity problems. Note that both Throughput Based Optimization and Flexible Uprade features need to be enabled. HSDPA) due to interference. HSDPARRCdiversity (SHO of HSDPA capable UE) AdditionTime AdditionWindow FMCS (HSDPA Id) FMCS (HSDPA Id) 6 (100ms) 2.NR T. deactivation of this will improve the call success rate (decrease rab_act_fail_bts). This parameter is related to Handover control. 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.5dB 0 (Disabled) 2dB 1 (Enabled) HSDPA16KBPSReturnCh annel RNC 0 (disabled) 1 (Enabled) Initial bitrate for HSDPA associated UL DCH HSDPAminAllowedBitrate U MaxBitRateNRTMACDFl ow RNC RNC RNC 64 kbits/s 64 kbits/s 3456 kbps 16 kbits/s 16 kbits/s 3456kbps 6784kbps 9600 kbps .2010 For internal use only 12.Guideline NPO NSN/SBU/MS 23.5 dB 13 (1280ms) 0 dB EnableRRCRelease HOPS (RT. In loaded networks it is recommended to use lower Initial bitrate in order to save capacity.3 Parameter Other Recommended HSDPA parameters Object RNC Default Allowed Recommended Value Not allowed Comments Only if HSDPA Serving Cell Change is disabled. In case of high UL Channel Element usage. Also due to capacity reasons it is recommended to set window as 0 dB to to save BTS WSPC capacity in the target cell. it is recommended to allow the use of ThroughputBasedOptimization for the HSDPA UL return channel.NRT.04. When “Not Allowed”. In loaded networks it is recommended to use lower Initial bitrate in order to save capacity. If HSDPA Serving Cell Change is enabled.

4s The 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. RLC unrecoverable error with new settings = 15*300ms+24*300ms = 11. It has been hidden parameter before RAS06. With HSDPA enabled in the cell the code tree usage is already about 38 %. MaxBitRateNRTMACDFlow=9600 kbps.7s RLC unrecoverable error with old settings = 15*200ms+12*200ms = 5. The change will have less RL failures and improved HSDPA retainability. The recommendation is to use 60 %. 300ms in HSDPA return channel case) AM RLC MaxRST transmissions for PS NRT with DCH (the amount of RESET PDUs) AM RLC maxRST transmissions for PS NRT with E-DCH AM RLC status period max for PS NRT with EDCH RNC 140 % 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.Guideline NPO NSN/SBU/MS 23. This is the default without HSDPA feature. Hidden parameter before RAS06. 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. AM RLC status period max for PS NRT with HSDSCH (periodic polling and reset polling repeat interval from 200 to 300ms) RNC 133 % 300 % 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. It has been hidden parameter before RAS06. This 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.2010 For internal use only Code Tree Usage WCEL 40 % 60 % AM RLC maxRST transmissions for PS NRT with HS-DSCH (the amount of RESET PDUs) RNC 12 24 MaxBitRateNRTMACDFlow=6784kbps For HSDPA 10Mbps per User. RLC parameter for HSUPA RNC RNC 12 133 % 24 300 % RLC parameter for HSUPA . Hidden parameter before RAS06. The change will have less RL failures and improved HSDPA retainability.04. RNC 12 24 This 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.

2010 For internal use only .Guideline NPO NSN/SBU/MS 23.04.

then DCHUtilMeasGuardTime should be reduced to avoid being a bottleneck. MinAllowedBitRateDL 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) InitialBitRateDL MinAllowedBitRateDL WCEL 32 kbps (RAS5) 8 kbps (RAS51RU10) 8kbps 13.2010 For internal use only 13.384. it should be enabled for all NRT traffic classes and traffic handling priorities RNC DCHUtilUpperAveWin<XX> DCHUtilLowerAveWin<XX> RNC 2s 1s DCHUtilUpperTimeToTrigger<XX > RNC 4s 2s DCHUtilLowerTimeToTrigger<XX> RNC 1.Guideline NPO NSN/SBU/MS 23.384. it is beneficial for throughput time to start at a higher initial bitrate.8s DCHUtilMeasGuardTime RNC 6s 2s If a high proportion of NRT traffic if of ip streaming type.2 Parameter Flexible Upgrade & Throughput Based Optimization Object RNC Default Off 1000 ms 0b00000000 FlexUpgrUsage DCHUtilHighAveWin PSOpThroUsage Recommended Value On 0 ms 0b11110000 Comments To allow all upgrade scenarios. If a high proportion of NRT traffic if of ip streaming type.. If PBS is not enabled. DCHUtilHighAveWinshould be set to 0 to avoid detail in RAB upgrage If the PS Throughput Based Optimization feature is licensed. If FlexUpgrUsage = on. faster reconfiguration to adequate bitrate is beneficial.4s 0.04. faster reconfiguration to adequate bitrate is beneficial. faster reconfiguration to adequate bitrate is beneficial. The same value can be applied t obitrate in range 32. 13. a degradation of the Capacity Request success ratio is in some case possible.. . If TimeToTrigger and AveWin are reduced as recommended above.384. The same value can be applied to bitrate in range 32.1 Parameter OTHER OPTIONAL FEATURES Priority Based Scheduling Object WCEL Default 64 kbps Recommended Value 128 kbps Comments If optional features PBS (Priority Based Scheduling) and TBO (Throughput Based Optimization) are enabled. The same value can be applied to bitrate in range 32.. If a high proportion of NRT traffic if of ip streaming type.

Parameter HSUPA PARAMETERS Object WCEL RNC WCEL Default 1920 kbps 1.0 is used. Parameter RRIndPeriod Object WBTS Default 400ms Recommended Value 200ms Comments The change was to align WBTS RRInd Period and NBxxx with Prx/PtxTotalReportPeriod.5 dB below PtxTarget value might trigger unnecessary LHO. In case there is no need for common Iub RAS06 default values should be used instead.2010 For internal use only 13.5 dB Recommended Value 10% 5 0 to -0. to avoid having HLR as limiting factor in HSUPA throughput With default of 2 used with 3 HSUPA MaxTotalUplinkSymbolRa te FactorEDCHMaxBitRate NumberEDCHReservedS .Guideline NPO NSN/SBU/MS 23. Used with C-iub only.4 Parameter Load and Service Based Handover Object WCEL WCEL WCEL Default 50% 10 -1.8dB Comments It is recommended to make the trigger more sensitive to be reacting faster to HW overload situation for LHO It is recommended to make the trigger more sensitive to be reacting faster to HW overload situation for LHO Setting the LHO trigger 1.0 is used In case HSUPA2.5 2 Recommended Value 3840 kbps 5 0-1 Comments In case HSUPA2. while DL load is still normally loaded. minimum value of 800 ms possible. RU10 DEFAULT CHANGES WITH C-IUB Related to Common Iub feature support in RU10 some RAS06 defaults have been changed. RAS06 default can be used without C-Iub RAS06 default can be used without C-iub RAS06 default can be used without C-iub RAS06 default can be used without C-iub RAS06 default can be used without C-iub PrxTargetPSAdjustPeriod PtxTargetPSAdjustPeriod SchedulingPeriod LoadControlPeriodPS PSAveragingWindowSize WBTS WCEL WBTS WBTS WBTS 5 5 100ms 2000ms 4 10 10 200ms 1200ms 2 15.3 Parameter Narrowband AMR Codecs Object RNC Default 7 (68%) (RAS5) 5(60%) (RAS51) 27 kbit/s Recommended Value 5 (60%) Comments To allow SF256 usage with lower narroband AMR codec To allow SF256 usage with lower narroband AMR codec DLpuncturingLimit DLmaxBitRateSF256 RNC 35 kbit/s 13. LHOHardBlockingRatio LHOHardBlockingBaseLo ad LHOPwrOffsetDL 14.04.

04.1 license only it is not possible to have more than one HSUPA connection in the cell in case of HSUPA SHO.2010 For internal use only HOBranchAdditions Delay ThresholdMax Delay ThresholdMid Delay ThresholdMin ProbabilityFactorMax RNC RNC RNC RNC 8 ms 4 ms 1 ms 0. Control.see TN SW_127 HSUPA cong. Control.Guideline NPO NSN/SBU/MS 23. Control.nokia.do? parentObjectId=0b00cc928015f319 .com/nols/doccenter/dcpageflow/viewDocumentDetails.online.8 100 ms 70 ms 50 ms 0. see the latest ones also. HSUPA cong. TS-RNC-SW-122 TS-RNC-SW-123 TS-RNC-SW-124 TS-RNC-SW-125 TS-RNC-SW-126 TS-RNC-SW-127 RNC Licence Keys . control. see TN_SW_127 HSUPA cong. TECHNICAL NOTES Below is link to all Technical Notes to be recommended to be used.Capacity Expansion Problem RN3.see TN_SW_127 HSUPA cong. see TN_SW_127 16.0 upgrade conversion corrections Monitoring of RNC DSP capacity usage RNC CDSP-C UPDATE Clearing OMS Alarm DB Modification to HSUPA Congestion Control default parameters https://www.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->