Académique Documents
Professionnel Documents
Culture Documents
RU20
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.
Table of contents
2. Introduction.......................................................................................................................................6 3. Idle mode parameters.......................................................................................................................7 3.1 Idle Mode WCDMA Parameters..................................................................................................7 3.2 Idle Mode GSM Parameters........................................................................................................7 4. SHO parameters...............................................................................................................................8 5. Inter-System Handover parameters..................................................................................................9 6. Inter-frequency Handover parameters............................................................................................11 7. Power Control parameters..............................................................................................................12 8. Admission Control parameters........................................................................................................13 9. Packet Scheduling parameters.......................................................................................................13 10. Telecom parameters.....................................................................................................................15 11. Other parameters..........................................................................................................................17 12. HSDPA related parameters...........................................................................................................19 12.1 HSDPA power parameters......................................................................................................19 12.2 HSDPA Dynamic Code Allocation...........................................................................................20 12.3 Other Recommended HSDPA parameters..............................................................................21 13. Other Optional features.................................................................................................................24 13.1 Priority Based Scheduling.......................................................................................................24 13.2 Flexible Upgrade & Throughput Based Optimization...............................................................24 13.3 Narrowband AMR Codecs.......................................................................................................25 13.4 Load and Service Based Handover.........................................................................................25 14. RU10 Default changes with C-Iub.................................................................................................25 15. HSUPA Parameters .....................................................................................................................25 16. TECHNICAL NOTES....................................................................................................................26
Change History Issue 1.0.0 2.0.0 2.1.0 Date 20.12.2002 31.12.2003 30.05.2004 Handled by Comments RNC Technical Support RAN1.5.1 & 1.5.2 RAN1.5.2 ED2 OS/NPS RAN1.5.2 ED2, update OS Performance
31.8.2004
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. Corrections to the parameters related to MHA and Cable loss. Correction to the Offset for activation time. Reference to TN 047 added + corrections to the text. Valid 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. Updated 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) Modifications 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. Deleted default values defined in system compared to 2.6.0 Main 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: added HHO triggers for NRT Services: added IFHO caused by UE TxPower:added CodeTreeOptimisation: modified T312: deleted T317: deleted ToAWS/ToAWE: deleted. IuBarringRecoveryTimer: modified StandAloneDCCHBitRate: added Chapter 12: HSDPA: added Modified SharedHSDPAFlowControlAllocation description Main RAS51 update: Added T313,N313
2.5.0
10.6.2005
OS Performance
2.6.0
06.10.2005 OS Performance
2.7.0 3.0.0
3.0.2 3.1
27.4.2006 31.1.2007
C&I C&I
3.2 4.0
24.8.2007 4.12.2007
CSI CSI
Added DedicatedMeasReportPeriod AltScramblingCodeCM: 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. 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. 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. Change in AM RLC protocol parameters for NRT Recent Techical Notes added Sib3compmask 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 PrxLoadMarginMaxDCH added Some range values added instead of pure numbers, some parameters were taken out (optimum value set as default), excel version added based on object classes. Minor corrections to HSPDSCHMarginSF128 and DPCHOverHSPDSCHThreshold parameters based on the field tests. RU10 parameter recommendations added: TN SW 127, C-Iub changes, SHO parameters due to SRB blocking Minor corrections to cell range, RRC enable release and drop reporting interval, Prachdelay range added First Version for RU20.
4.1
31.3.2008
NPO
29.04.2008 NPO 16.7.2008 NPO 29.10.2008 NPO 18.12.2008 NPO 30.4.2009 21.9.2009 23.4.2010 NPO NPO NPO
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 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
It 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 6ptimization activities will be needed anyway to improve the radio network performance. Thus these parameters are only better defaults to start the optimization.
3. 3.1
Idle mode parameters should be optimized to improve the call setup success rate.
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. 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) WCEL 2s 2s 2s 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. All 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 Comments
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.2
Parameter
Non GPRS Multi RAT MS Qual (QsearchI) (GSM), QSRI GPRS Multi RAT MS Qual (QsearchP) (GSM), QSRP Multi RAT MS Qual (QsearchC), QSRC
BTS
15 (no meas)
7 (=always)
HOC
15 (no meas)
7 (=always)
UE interpretation. 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. 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 Parameter DropreportingInterval ReplacementReporting Interval ReplacementWindow Object FMCS FMCS FMCS Default values 0.5s 0.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, Current default trigger setting of SHO event 1C causes plenty of events to be reported in RU10-> SRB blocking SRB Blocking, see above.
ReplacementTime
FMCS
100ms
640ms
5.
Parameter
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
FMCG
Disabled
Enabled
FMCG
6 measurement reports
No 32 kbits/s
CPICH Ec/No HHO Threshold, CPICH Ec/No HHO Cancel, CPICH RSCP HHO Threshold, CPICH RSCP HHO Cancel for NRT Services
Lower 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. Lower values for RT to have more coverage. Absolute Isho number (and ISHO) drops will be decreased. This 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.
CPICH Ec/No HHO Threshold, CPICH Ec/No HHO Cancel, CPICH RSCP HHO Threshold, CPICH RSCP HHO Cancel for NRT Services DedicatedMeasReportPeriod
FMCS RT
WBTS
6.
Parameter
IFHO caused by CPICH Ec/No IFHO caused by CPICH RSCP IFHO caused by UE TxPower UE TX Power Filter Coefficient
FMCI
20 meas report
12 meas report
7.
Parameter
RNC
15 dB
20 dB
WCEL
-25 dB
-20..-18 dB
8.
Parameter
9.
Parameter
MSActivitySupervision (MS activity supervision timer) (Time supervision of user inactivity (for NRT RBs))
WCEL
37 dBm
35-37 dBm
RNC
300ms
400,500 ms
setup time the SRB size should be set to 13.6 kbps. MinAllowedBitRateDL/UL (Initial and minimum allowed bit rate in DL/UL) WCEL Uplink 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. In loaded networks it may be useful to use lower initial bitrates
WCEL
64 kbits/s
8 or 16 kbits/s
10.
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, 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. 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. This is RU10 parameter,value should be set according to extended cell licence. These 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) The 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. This 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. The 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.
PRACHDelayRange PRACH Preamble Retrans Max RACH maximum number of preamble cycles
3 (20km) 8 8
RNC
1s
5s
RNC
5s
8s
T3212
RNC
0 decihours
6h
T313
WCEL
3s
6-8s
N313
WCEL
20
50
T315
WCEL
4 (180 s)
1 (10 s)
In 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. In 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. 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.
Parameter MHA used
OTHER PARAMETERS
Object WCEL/AC Default Recommended value MHA: MHA='Offset used', CableLoss=Fee der loss, No MHA: MHA='Offset not used', CableLoss=N/A Comments RAS06 (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. 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, ZLCC
Calculated
StandAloneDC CHBitRate (Signalling radio bearer bit rate at RRC connection establishment)
34 (3.4 kbps),
When creating the IuPS interface against NSN SGSN, use value 14msec for CDVT in control plane, (when creating VC for IuPS signalling connection) 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.
Parameter
Object
Default
Recommended Value
Comments
DRRCprxMargin DRRCptxMargin
WCEL WCEL
-0.5 dB - 2 dB
0 dB -0.5 dB
1 2 0100%
3 4 67 %
Directed RRC connection Setup parameter ; based on field measurements, target cell does not need to be at lower load in UL Directed RRC connection Setup parameter ; based on field measurements, 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. 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. 12.1
The 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.
PtxCellMax PtxCPICH, dBm PtxTarget
PtxTarget (in Watts)
Default 43
20.0
dBm
W
33 40
10.0
33 42
15.8
36 45
31.6
29 38
6.3
33 42
15.8
36 45
31.6
29 38
6.3
dBm dBm
W
PtxOffset
PtxTarget+PtxOffset (in Watts)
1.0
12.6
0.8
19.1
0.8
38.0
0.8
7.6
0.8
19.1
0.8
38.0
0.8
7.6
dBm
W
36
4.0
39
7.9
32
1.6
36
4.0
39
7.9
32
1.6
dBm
W
PtxTargetPSMax
PtxTargetPSMax (in Watts) Min. power available for HSDPA
40
10.0 10.0
42
15.8 4.1
45
31.6 8.2
38
6.3 1.6
40
10.0 10.0
43
20.0 19.9
36
4.0 4.0
dBm
W W
PtxHighHSDPAPwr
PtxHighHSDPAPwr (in Watts)
42
15.8
42.5
17.8
45.5
35.5
38.5
7.1
42
15.8
45
31.6
38
6.3
dBm
W
42.0
15.8
45.0
31.6
38.0
6.3
42.0
15.8
45.0
31.6
38.0
6.3
dBm
W
PtxTargetHSDPA
PtxTargetHSDPA (in Watts)
37.8
6.0
40
10.0
43
20.0
37
5.0
40
10.0
43
20.0
37
5.0
dBm
W
PtxOffsetHSDPA
PtxTargetHSDPA+PtxOffsetHSDPA (in Watts) Min. power available for HSDPA
0.8
7.2 7.1
0.8
12.0 7.9
2
31.6 8.2
0.8
6.0 1.9
0.8
12.0 7.9
2
31.6 8.2
0.8
6.0 1.9
dBm
W W
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
Parameter
HSPDSCHMarginSF128
DPCHOverHSPDSCHThreshold
WCEL
1-4
HSPDSCHAdjustPeriod
RNC
10s
5s
12.3
Parameter
AdditionTime AdditionWindow
6 (100ms) 2.5 dB
13 (1280ms) 0 dB
EnableRRCRelease
0 (No)
1 (Yes) 0 (no)
2.5dB 0 (Disabled)
2dB 1 (Enabled)
HSDPA16KBPSReturnCh annel
RNC
0 (disabled)
1 (Enabled)
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, MaxBitRateNRTMACDFlow=9600 kbps. 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 %. 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. 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.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.
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, 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. It has been hidden parameter before RAS06. The change will have less RL failures and improved HSDPA retainability. 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.
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. Hidden parameter before RAS06. RLC parameter for HSUPA
RNC RNC
12 133 %
24 300 %
13. 13.1
Parameter
InitialBitRateDL
MinAllowedBitRateDL
WCEL
8kbps
13.2
Parameter
Recommended Value On 0 ms
0b11110000
Comments To allow all upgrade scenarios. If FlexUpgrUsage = on, DCHUtilHighAveWinshould be set to 0 to avoid detail in RAB upgrage If the PS Throughput Based Optimization feature is licensed, 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.4s
0.8s
DCHUtilMeasGuardTime
RNC
6s
2s
If 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. If 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. If 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. If TimeToTrigger and AveWin are reduced as recommended above, then DCHUtilMeasGuardTime should be reduced to avoid being a bottleneck.
13.3
Parameter
DLpuncturingLimit
DLmaxBitRateSF256
RNC
35 kbit/s
13.4
Parameter
14.
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.
Parameter RRIndPeriod Object WBTS Default 400ms Recommended Value 200ms Comments The change was to align WBTS RRInd Period and NBxxx with Prx/PtxTotalReportPeriod, minimum value of 800 ms possible. Used with C-iub only. 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
5 5 100ms 2000ms 4
10 10 200ms 1200ms 2
15.
Parameter
HSUPA PARAMETERS
Object WCEL RNC WCEL Default 1920 kbps 1.5 2 Recommended Value 3840 kbps 5 0-1 Comments In case HSUPA2.0 is used In case HSUPA2.0 is used, to avoid having HLR as limiting factor in HSUPA throughput With default of 2 used with 3 HSUPA
HOBranchAdditions Delay ThresholdMax Delay ThresholdMid Delay ThresholdMin ProbabilityFactorMax RNC RNC RNC RNC 8 ms 4 ms 1 ms 0.8 100 ms 70 ms 50 ms 0.1
license only it is not possible to have more than one HSUPA connection in the cell in case of HSUPA SHO. HSUPA cong. control,see TN SW_127 HSUPA cong. Control,see TN_SW_127 HSUPA cong. Control, see TN_SW_127 HSUPA 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-122 TS-RNC-SW-123 TS-RNC-SW-124 TS-RNC-SW-125 TS-RNC-SW-126 TS-RNC-SW-127
RNC Licence Keys - Capacity Expansion Problem RN3.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.online.nokia.com/nols/doccenter/dcpageflow/viewDocumentDetails.do? parentObjectId=0b00cc928015f319