WCDMA19 Prfile Descriptions W19P8 08A APPR

PRFILE Descriptions
DN0948854
Issue 08A
Approval Date 2019-02-06

PRFILE Descriptions
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).
This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.
Copyright © 2019 Nokia. All rights reserved.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.
2 © 2019 Nokia. Nokia confidential. DN0948854 Issue: 08A
PRFILE Descriptions
Table of Contents
This document has 254 pages

Summary of changes................................................................... 10

Delta between current and last release........................................12

1 Overview of PRFILE descriptions................................................ 14
1.1 Modifying PRFILE parameters..................................................... 14

2 Parameter class 002 SYSTEM_FUNCT_CONFIGUR................. 16
2.1 002:0621 RNW_DATA_1..............................................................16
2.2 002:0740 RNW_DATA_2..............................................................16
2.3 002:0840 TIMER_ERQ................................................................ 17
2.4 002:0841 TIMER_REL................................................................. 18
2.5 002:0842 TIMER_MOD................................................................18
2.6 002:1047 AAL2_NNI_CONN_REL_TIMER................................. 19
2.7 002:1248 NE_LOGICAL_CONFIGURATION...............................20
2.8 002:1296 RN22_FEATURE_OPT_009........................................ 21
2.9 002:1297 RN22_FEATURE_OPT_008........................................ 22
2.10 002:1300 RN22_FEATURE_OPT_004........................................ 22
2.11 002:1370 AMR_LIC_WARN_IN_USE..........................................23
2.12 002:1371 AMR_LIC_WARN_THRESHOLD.................................24
2.13 002:1372 AMR_LIC_WARN_DUR............................................... 24
2.14 002:1373 AMR_LIC_WARN_DUR_CANCEL.............................. 25
2.15 002:1374 AMR_LIC_ALARM_IN_USE........................................ 26
2.16 002:1375 AMR_LIC_ALARM_DUR_CAL.................................... 26
2.17 002:1376 PS_LIC_WARN_IN_USE............................................. 27
2.18 002:1377 PS_LIC_WARN_THRESHOLD....................................28
2.19 002:1378 PS_LIC_WARN_DUR.................................................. 29
2.20 002:1379 PS_LIC_WARN_DUR_CANCEL..................................29
2.21 002:1380 PS_LIC_ALARM_IN_USE........................................... 30
2.22 002:1381 PS_LIC_ALARM_DUR_CAL........................................31
2.23 002:1546 ICSU_WINDOW_SIZE.................................................31
2.24 002:1632 HSUPA_SERVICE_INDICATOR.................................. 32
2.25 002:1649 IP_LINK_BREAK_REL_DELAY................................... 33
2.26 002:1662 REVERTIVE_SWO_IN_USE....................................... 34
2.27 002:1664 RN50_MAINT_02.........................................................34
2.28 002:1666 RN50_MAINT_03.........................................................35
2.29 002:1668 RN50_MAINT_05.........................................................36
2.30 002:1669 RN50_MAINT_06.........................................................37
2.31 002:1670 RN50_MAINT_07.........................................................37
2.32 002:1671 RN50_MAINT_08.........................................................38
2.33 002:1673 RN50_MAINT_10.........................................................39
2.34 002:1684 RN50_MAINT_11......................................................... 40
DN0948854 Issue: 08A © 2019 Nokia. Nokia confidential. 3
PRFILE Descriptions
2.35 002:1686 RN50_MAINT_13.........................................................40
2.36 002:1687 RN50_MAINT_14.........................................................41
2.37 002:1689 RN50_MAINT_15.........................................................42
2.38 002:1691 RN50_MAINT_16.........................................................43
2.39 002:1696 RN50_MAINT_20.........................................................44
2.40 002:1697 RN50_MAINT_21.........................................................44
2.41 002:1699 RN50_MAINT_23.........................................................45
2.42 002:1700 RN50_MAINT_24.........................................................46
2.43 002:1701 RN50_MAINT_25.........................................................47
2.44 002:1702 RN50_MAINT_26.........................................................47
2.45 002:1703 RN50_MAINT_27 and 002:1704 RN50_MAINT_28.... 49
2.46 002:1706 RN50_MAINT_29.........................................................50
2.47 002:1716 RN50_MAINT_38.........................................................52
2.48 002:1717 RN50_MAINT_39.........................................................53
2.49 002:1760 RN50_MAINT_43.........................................................54
2.50 002:1765 RN50_MAINT_48.........................................................55
2.51 002:1775 RN50_MAINT_57.........................................................56
2.52 002:1776 RN50_MAINT_58.........................................................57
2.53 002:1792 UP_CAP_UPGRADE................................................... 58
2.54 002:1798 OPT_BLOCK_MOVE_PREVENT................................ 59
2.55 002:1814 LCH_IN_USE............................................................... 59
2.56 002:1816 IPMUX_MUX_DELAY.................................................. 60
2.57 002:1817 DYNPWROFFSETUSAGE.......................................... 61
2.58 002:1818 LCH_TRAN_IN_USE................................................... 61
2.59 002:1819 LCH_DIR_SIZE............................................................62
2.60 002:1840 B_PHASE1_SWITCH.................................................. 63
2.61 002:1864 HSPA_OVER_IUR_EXT.............................................. 63
2.62 002:1868 EDPDCHPowerInterUsage.......................................... 64
2.63 002:1886 RN60_MAINT_10.........................................................65
2.64 002:1888 RN60_MAINT_12.........................................................66
2.65 002:1889 RN60_MAINT_13.........................................................67
2.66 002:1892 RN60_MAINT_16.........................................................68
2.67 002:1897 RN60_MAINT_22.........................................................69
2.68 002:1900 RN60_MAINT_25.........................................................69
2.69 002:1902 RN60_MAINT_26.........................................................70
2.70 002:1903 RN60_MAINT_27.........................................................71
2.71 002:1904 RN60_MAINT_28.........................................................72
2.72 002:1905 RN60_MAINT_29.........................................................74
2.73 002:1908 RN60_MAINT_32 and 002:1909 RN60_MAINT_33.... 75
2.74 002:1912 RN60_MAINT_36.........................................................77
2.75 002:1913 RN60_MAINT_38.........................................................77
2.76 002:1914 RN60_MAINT_39.........................................................78
2.77 002:1915 RN60_MAINT_40.........................................................79
2.78 002:1916 RN60_MAINT_41.........................................................80
2.79 002:1918 RN60_MAINT_37.........................................................83
2.80 002:1932 RN60_INT_FEAT_RES_03.......................................... 83
PRFILE Descriptions
2.81 002:1935 RN60_INT_FEAT_RES_06.......................................... 84
2.82 002:1939 RN60_INT_FEAT_RES_10.......................................... 85
2.83 002:1950 CPC_DL_DRX_RESTRICTED.................................... 86
2.84 002:2066 MIN_RE_EDPDCH_GF_TO_BTS................................87
2.85 002:2095 RU40_MAINT_01.........................................................88
2.86 002:2098 RU40_MAINT_02.........................................................89
2.87 002:2099 RU40_MAINT_03.........................................................90
2.88 002:2100 RU40_MAINT_04.........................................................91
2.89 002:2101 RU40_MAINT_05.........................................................92
2.90 002:2102 RU40_MAINT_06.........................................................93
2.91 002:2103 RU40_MAINT_07.........................................................93
2.92 002:2105 RU40_MAINT_09.........................................................95
2.93 002:2107 RU40_MAINT_11......................................................... 96
2.94 002:2109 RU40_MAINT_13.........................................................97
2.95 002:2110 RU40_MAINT_14......................................................... 99
2.96 002:2111 RU40_MAINT_15....................................................... 100
2.97 002:2112 RU40_MAINT_16....................................................... 102
2.98 002:2113 RU40_MAINT_17....................................................... 103
2.99 002:2115 RU40_MAINT_19....................................................... 104
2.100 002:2117 RU40_MAINT_21....................................................... 106
2.101 002:2119 RU40_MAINT_23....................................................... 108
2.102 002:2121 RU40_MAINT_25....................................................... 110
2.103 002:2122 RU40_MAINT_26....................................................... 111
2.104 002:2124 RU40_MAINT_28....................................................... 112
2.105 002:2125 RU40_MAINT_29....................................................... 113
2.106 002:2126 RU40_MAINT_30....................................................... 115
2.107 002:2128 RU40_MAINT_32....................................................... 116
2.108 002:2129 RU40_MAINT_33....................................................... 117
2.109 002:2131 RU40_MAINT_35....................................................... 118
2.110 002:2132 RU40_MAINT_36....................................................... 119
2.111 002:2134 RU40_MAINT_38.......................................................121
2.112 002:2136 RU40_MAINT_40.......................................................123
2.113 002:2139 RU40_MAINT_43 ......................................................126
2.114 002:2140 RU40_MAINT_44.......................................................127
2.115 002:2141 RU40_MAINT_45.......................................................128
2.116 002:2142 RU40_MAINT_46.......................................................129
2.117 002:2143 RU40_MAINT_47.......................................................130
2.118 002:2144 RU40_MAINT_48.......................................................131
2.119 002:2146 RU40_MAINT_50.......................................................132
2.120 002:2148 RU40_MAINT_52.......................................................134
2.121 002:2151 RU40_MAINT_55.......................................................134
2.122 002:2152 RU40_MAINT_56.......................................................135
2.123 002:2235 TOT_RESET_LIM_PER_SITE...................................136
2.124 002:2257 UDP_FILL_RATIO_HIGH ..........................................137
2.125 002:2258 LEG_ERROR_RATIO_HIGH..................................... 138
2.126 002:2259 DYN_HSPA_BLER_MULTI_RAB...............................139
PRFILE Descriptions
2.127 002:2264 RU50_SPARE_02...................................................... 139

2.128 002:2265 RU50_SPARE_03...................................................... 141
2.129 002:2266 RU50_SPARE_04...................................................... 142
2.130 002:2267 RU50_SPARE_05...................................................... 142
2.131 002:2268 RU50_SPARE_06...................................................... 143
2.132 002:2269 RU50_SPARE_07...................................................... 144
2.133 002:2272 RU50_SPARE_10...................................................... 145
2.134 002:2273 RU50_SPARE_11...................................................... 146
2.135 002:2276 RU50_SPARE_14...................................................... 147
2.136 002:2277 RU50_SPARE_15...................................................... 148
2.137 002:2278 RU50_SPARE_16...................................................... 149
2.138 002:2281 RU50_SPARE_19...................................................... 150
2.139 002:2282 RU50_SPARE_20...................................................... 152
2.140 002:2306 CSFB_WITH_RIM......................................................154
2.141 002:2345 PWSM_CANCEL_ENABLED.....................................155
2.142 002:2388 CTRL_MAINT_SPARE_01.........................................156
2.143 002: 2398 CTRL_MAINT_SPARE_02........................................157
2.144 002:2399 CTRL_MAINT_SPARE_03.........................................158
2.145 002:2400 CTRL_MAINT_SPARE_04.........................................162
2.146 002:2401 CTRL_MAINT_SPARE_05.........................................163
2.147 002:2402 CTRL_MAINT_SPARE_06.........................................166
2.148 002:2403 CTRL_MAINT_SPARE_07.........................................167
2.149 002:2404 CTRL_MAINT_SPARE_08.........................................168
2.150 002:2405 CTRL_MAINT_SPARE_09.........................................169
2.151 002:2407 CTRL_MAINT_SPARE_10.........................................170
2.152 002:2408 CTRL_MAINT_SPARE_11......................................... 171
2.153 002:2409 CTRL_MAINT_SPARE_12.........................................171
2.154 002:2410 CTRL_MAINT_SPARE_13.........................................172
2.155 002:2414 CTRL_MAINT_SPARE_17.........................................174
2.156 002:2417 CTRL_MAINT_SPARE_20.........................................175
2.157 002:2418 CTRL_MAINT_SPARE_21.........................................178
2.158 002:2421 CTRL_MAINT_SPARE_24.........................................179
2.159 002:2424 CTRL_MAINT_SPARE_25.........................................180
2.160 002:2425 CTRL_MAINT_SPARE_26.........................................180
2.161 002:2542 IPV6UDP_ZERO_CKSUM.........................................181

3 Parameter class 007 CALL_CONTROL.....................................183
3.1 007:0174 CN_INFORMATION_INFO.........................................183
3.2 007:0191 JAPAN_UE_CONTROL............................................. 183
3.3 007:0195 RN21_MAINT_003.....................................................185
3.4 007:0208 RNC_MAINT_001...................................................... 186
3.5 007:0227 RN30_MAINT_004.....................................................187
3.6 007:0238 RN30_MAINT_015.....................................................188
3.7 007:0239 RN30_MAINT_016.....................................................188
3.8 007:0240 RN30_MAINT_017.....................................................189
3.9 007:0241 RN30_MAINT_018.....................................................190
PRFILE Descriptions
3.10 007:0242 RN30_MAINT_019.....................................................191
3.11 007:0243 RN30_MAINT_020.....................................................192
3.12 007:0246 RN30_MAINT_023.....................................................193
3.13 007:0269 RN40_MAINT_001.....................................................194
3.14 007:0270 RN40_MAINT_002.....................................................195
3.15 007:0279 RN40_MAINT_009.....................................................196
3.16 007:0280 RN40_MAINT_010.....................................................197
3.17 007:0281 RN40_MAINT_011..................................................... 198
3.18 007:0283 RN40_MAINT_013.....................................................198
3.19 007:0284 RN40_MAINT_014.....................................................199
3.20 007:0285 RN40_MAINT_015.....................................................201
3.21 007:0286 RN40_MAINT_016.....................................................202
3.22 007:0287 RN40_MAINT_017.....................................................203
3.23 007:0290 RN40_MAINT_020.....................................................203
3.24 007:0291 RN40_MAINT_021.....................................................204
3.25 007:0295 RN40_MAINT_025.....................................................205
3.26 007:0296 RN40_MAINT_026.....................................................206
3.27 007:0297 RN40_MAINT_027.....................................................206
3.28 007:0299 RN40_MAINT_029.....................................................207
3.29 007:0304 RN40_MAINT_034.....................................................208
3.30 007:0306 RN40_MAINT_036.....................................................209
3.31 007:0307 RN40_MAINT_037.....................................................210
3.32 007:0308 RN40_MAINT_038..................................................... 211
3.33 007:0387 RNC_L3_CONTROL_022..........................................212
3.34 007:0388 RNC_L3_CONTROL_023..........................................213
3.35 007:0389 RNC_L3_CONTROL_024..........................................214
3.36 007:0390 RNC_L3_CONTROL_025..........................................215
3.37 007:0391 RNC_L3_CONTROL_026..........................................216
3.38 007:0394 RNC_L3_CONTROL_029..........................................217
3.39 007:0398 RNC_L3_CONTROL_033..........................................217
3.40 007:0518 CELL_FACH_RELOC_PREVENT............................. 218
3.41 007:0521 HSPA_DCH_MIN_RES.............................................. 219
3.42 007:0522 CS_CALL_RE_ESTB_OVR_IUR...............................220

4 Parameter class 009 SYSTEM_SUPERVISION........................ 222
4.1 009:0101 IUB_DATA_RECV_INTERVAL................................... 222
4.2 009:0102 IUB_CONN_POLLING_TIME.................................... 222
4.3 009:0130 IP_MSG_MON........................................................... 223

5 Parameter class 016 ALARM_SYSTEM.................................... 225
5.1 016:0000 ALARM_PRINT_END_MARK.................................... 225
5.2 016:0001 LAMP_PANEL_POLARITY........................................ 225
5.3 016:0002 ALARM_DRIVEN_OUTPUTS.................................... 226
5.4 016:0003 LAMP_PANEL_BUZZER............................................227
5.5 016:0004 PRINTING_MODE..................................................... 228
5.6 016:0008 HEARTBEAT_ALM_INTERVAL................................. 228
PRFILE Descriptions
5.7 016:0009 WBTS_LEVEL_ALARM_SWITCH............................. 229

5.8 016:0010 SUSPEND_MODE_SWITCH.....................................230
5.9 016:0011 WCEL_OUT_OF_USE_NUM..................................... 231
5.10 016:0012 HSPA_ACT_FAIL_NUM............................................. 231
5.11 016:0013 RNW_DATABASE_FAIL_NUM.................................. 232
5.12 016:0014 WBTS_LEVEL_ALARM_NUM................................... 233
5.13 016:0015 BUFFER_ALARM_THRESHOLD.............................. 233

6 Parameter class 038 MML_COMMAND_LOG...........................235
6.1 038:0001 STORAGE_LENGTH................................................. 235

7 Parameter class 055 LCS_PARAMETERS................................236
7.1 055:0003 EMERGENCY_CALL_ISHO_SUP.............................236
7.2 055:0011 AGPS_SUPPORT...................................................... 236
7.3 055:0012 INT_EMERG_CALL_ISHO_SUP............................... 237
7.4 055:0013 NW_AGPS_SUPPORT.............................................. 238
7.5 055:0015 IUPC_INTERFACE.................................................... 238

8 Parameter class 058 OAM_SECURITY.....................................240
8.1 058:0000 PW_POLICY_FEATURE, 058:0001
UA_POLICY_FEATURE, 058:0004
USER_ACCOUNT_LOCK_LIMIT, 058: 0005
CONF_INTERFACES_FEATURE, 058:0006
HTTPS_WEBGUI_INTERFACE.................................................240

9 Parameter class 069 TROUBLESHOOTING............................. 241
9.1 069:0001 CSUP_AUTO_RECOVERY_TIME.............................241

10 Appendix.................................................................................... 242
10.1 Appendix A: Non-valid PRFILE parameters...............................242
10.1.1 Non-valid PRFILE parameter from Parameter Class 000.......... 242
PRFILE Descriptions
List of Tables
Table 1 Values in HEX and effects.................................................................. 72
Table 2 Bitmask values for 0.X.0.0 and effects............................................... 72
Table 3 Bitmask values for X.0.0.0 and effects............................................... 73
Table 4 MML commands for checking the activation status of 002:2111
RU40_MAINT_15............................................................................ 101
Table 5 PRFILEMultiplier values................................................................... 107
Table 6 Other values..................................................................................... 107
Table 7 Parameter range interpretation value............................................... 136
Table 8 Accepted values for Bit0...................................................................140
Table 9 CPICH EcNo Mapping Table............................................................ 158
Table 10 CPICH RSCP Mapping Table........................................................... 159
Table 11 Z multiplier defined by 002:2417 CTRL_MAINT_SPARE_20........... 176
Table 12 Multiplier X defined by 002:2417 CTRL_MAINT_SPARE_20...........177

Summary of changes PRFILE Descriptions
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issues 08 (2018-11-02, WCDMA19) and 08A (2019-02-06,

WCDMA19)
The following parameters were added as they were missing from the document:
• 058:0005 CONF_INTERFACES_FEATURE
• 058:0006 HTTPS_WEBGUI_INTERFACE
002:1706 RN50_MAINT_29
• 002:1706 RN50_MAINT_29 has been updated.
002:1684 RN50_MAINT_11
• 002:1684 RN50_MAINT_11 has been updated.
The following PRFILE parameters were removed from the document and was added to
the Appendix Chapter as they are considered non-valid for this release:
• 002:2533 RRC_CONN_SETUP
• 002:2534 CS_RAB_SETUP
• 002:2535 PS_RAB_SETUP
• 002:2536 PACKET_CALL_TICK_SETUP
• 002:2537 PACKET_CALL_TICK_RELEA
• 002:2538 RAB_CALL_RELEASE
• 002:2539 NONPERFUNITRECOV
• 002:2540 NONPERFUNITRECOVDSPSTD
Appendix Chapter
An Appendix Chapter has been added to the document to list non-valid PRFILE
parameters for this release.
Changes between issues 07E (2018-10-16, WCDMA18) and 08 (2018-11-02,

WCDMA19)
002:2409 CTRL_MAINT_SPARE_12
• 002:2407 CTRL_MAINT_SPARE_12 has been added.

PRFILE Descriptions Summary of changes

Delta between current and last release PRFILE Descriptions
Delta between current and last release

Cumulative changes between WCDMA18 and WCDMA19 PRFILE parameters are listed
here.
Modified parameters
• 002:1546 ICSU_WINDOW_SIZE
• 002:1904 RN60_MAINT_28
• 002:1905 RN60_MAINT_29
• 002:2281 RU50_SPARE_19
• 002:2117 RU40_MAINT_21
• 002:2142 RU40_MAINT_46
• 002:2112 RU40_MAINT_16
• 002:2306 CSFB_WITH_RIM
• 002:1684 RN50_MAINT_11
• 002:1706 RN50_MAINT_29
Added parameters
• 002:2409 CTRL_MAINT_SPARE_12
• 002:2258 LEG_ERROR_RATIO_HIGH
• 002: 2398 CTRL_MAINT_SPARE_02
• 002:2148 RU40_MAINT_52
Removed parameters

PRFILE Descriptions Delta between current and last release

Overview of PRFILE descriptions PRFILE Descriptions
1 Overview of PRFILE descriptions

This document describes the PRFILE (General Parameter File) parameters used in IPA-
RNC and mcRNC.
The system has a group of functionalities that are not included in the basic software of
the network element delivery. Examples include the activation of new features or the
possibility to control additional settings on existing functionalities. The information for
controlling these features is assembled within the network element in the PRFILE or
General Parameter File.
Parameters are organized into parameter classes, each representing a specific
functional area.
During a software upgrade, the values of changeable parameters are copied from the old
software build of the network element into the new one. This way the customer's settings
are kept intact during the software upgrade.
g Note: Only the active parameters included in a particular software release are
described in detail in this document. Non-valid parameters are listed in the Appendix
section at the end of the document, and they should not be modified.
Individual parameter descriptions include the following information:
• Identifier: Consists of the parameter class number, parameter number (for example,
002:0433), and the parameter's official name, which is used, for example, in MML
printouts.
• Descriptive name: The name of the parameter in plain text form.
• Functional description: A description of the purpose and function of the parameter.
• PRFILE control: Instructions on how to modify parameter values, which can be found
in Modifying PRFILE parameters.
• Parameter values: Values are documented in hexadecimal (H) notation. Boolean
TRUE/FALSE values generally correspond to values 1H/0H, respectively.
– Allowed value(s): Values or value ranges impacting a selected functionality.
– Recommended value(s): Selected allowed values corresponding to
recommended functionality settings.
– Default value: Default value of the parameter within the PRFILE.
– Forbidden value(s): Any value which may cause conflicts with internal controller
functionalities.
• Dependence: Indicates whether the parameter functionality is dependent upon a
specific feature or parameter. In case of feature dependency, this means that the
parameter functionality is available only if the operator has installed the feature in
question.
1.1 Modifying PRFILE parameters

This section demonstrates how to check and modify PRFILE parameter values.

PRFILE Descriptions Overview of PRFILE descriptions
Purpose
During a software upgrade, the values of changeable parameters are copied from the old
software build of the network element into the new one using the PRFCNV/FIFCNV
conversion. This way the customer's settings are kept intact during the software upgrade.
For more detailed instructions on how the parameters are handled in mcRNC, see
Configuring PRFILE parameters in Managing Multicontroller RNC Software
Configuration. For more information on SCLI commands, see Multicontroller RNC SCLI
Commands.
For more detailed instructions on how the parameters are handled in IPA-RNC, see
Interrogating and modifying PRFILE parameters in Managing IPA-RNC Software
Configuration and WO-Parameter Handling.
• Checking the current parameter value
Select from the available options
– In IPA-RNC. use the following MML command:
ZWOI:<parameter class>,<parameter number>;
– In mcRNC use the following SCLI command:
show app-parameter configuration-parameter class
<parameter class> number <parameter number>
• Modifying the parameter value
Select from the available options
– In IPA-RNC, use the following MML command:
ZWOC:<parameter class>,<parameter number>,<HEX parameter
value>;
– In mcRNC use the following SCLI command:
set app-parameter configuration-parameter class
<parameter class> number <parameter number> value 0x<HEX
parameter value>
Example
• Checking the value of parameter 007:0272:
– In IPA-RNC: ZWOI:7,272;
– In mcRNC : show app-parameter configuration-parameter class
7 number 272
• Setting the value of parameter 007:0272 to 0:
– In IPA-RNC: ZWOC:7,272,0;
– In mcRNC : set app-parameter configuration-parameter class
7 number 272 value 0x0

Parameter class 002 SYSTEM_FUNCT_CONFIGUR PRFILE Descriptions
2 Parameter class 002

SYSTEM_FUNCT_CONFIGUR
This class includes parameters that modify the configuration of system functions.
2.1 002:0621 RNW_DATA_1

Descriptive name
Radio network parameter
Applicable controllers
IPA-RNC: RN5.0 onwards
mcRNC: mcRNC2.0 onwards
Functional description
This PRFILE parameter is used by the radio network (RNW) configuration dB (raquel)
conversion program.
PRFILE control
See #unique_169 to find information on how to interrogate and modify PRFILE
parameter values.
Parameter values
Default value Forbidden value(s)

FF00H (65280D) n/a
Dependence
n/a
2.2 002:0740 RNW_DATA_2

Descriptive name
Radio network parameter

PRFILE Descriptions Parameter class 002 SYSTEM_FUNCT_CONFIGUR
This PRFILE parameter is used by the radio network (RNW) configuration dB conversion
program.
PRFILE control
parameter values.
Parameter values

FF00H (65280D) n/a
Dependence
n/a
2.3 002:0840 TIMER_ERQ

Descriptive name
Value of AAL2 signaling establish timer
IPA-RNC
The PRFILE parameter 002:0840 TIMER_ERQ is used to set the value for AAL2
connection establishment timer in AAL2 signaling services. The possible timer value
range from five (5H) seconds to thirty (1EH) seconds. For more information, see
Configuring Signaling Connections in ATM Network (IPA-RNC).
PRFILE control
parameter values.
Parameter values
Allowed value(s) Effect

0005H - 001EH Timer value between five and thirty seconds.

001EH n/a
Dependence
n/a

2.4 002:0841 TIMER_REL

Descriptive name
AAL2 signaling release timer
IPA-RNC
The PRFILE parameter 002:0841 TIMER_REL is used to set the value for release
timer in AAL2 signaling services. The possible timer value range from two (2H) seconds
to sixty (3CH) seconds. For more information, see Configuring Signaling Connections in
ATM Network (IPA-RNC).
PRFILE control
parameter values.
Parameter values

0002H - 003CH Timer value between two and sixty seconds.

003CH n/a
Dependence
n/a
2.5 002:0842 TIMER_MOD

Descriptive name
AAL2 signaling modification timer
IPA-RNC
The PRFILE parameter 002:0842 TIMER_MOD is used to set the value for the
modification timer in AAL2 signaling services. The possible timer value range from five
(5H) seconds to thirty (1EH) seconds. For more information, see Configuring Signaling
Connections in ATM Network (IPA-RNC). The default value is ten seconds.

PRFILE control
parameter values.
Parameter values

0005H - 001EH Timer value between five and thirty seconds.

00AH n/a
Dependence
n/a
2.6 002:1047 AAL2_NNI_CONN_REL_TIMER

Descriptive name
Timer to delay AAL2 connection releases when NNI signaling link is broken
IPA-RNC
The PRFILE parameter 002:1047 AAL2_NNI_CONN_REL_TIMER is used to set the
time that the system waits before AAL2 connections using a broken NNI signaling links
are released. The timer is started when the system detects that the NNI signaling link
does not work. If the signaling link goes up before the time expires, AAL2 connections
are not released. If the time expires, AAL2 connections using a broken signaling link are
released. The possible timer value range from one (1H) second to 255 (FFH) seconds. If
the value is set to 0 (0H), then the AAL2 connections are released right after the
signaling link goes down. For more information, see Configuring Signaling Connections
in ATM Network (IPA-RNC).
PRFILE control
parameter values.
Parameter values

0000H - 00FFH Timer value between one and 255 seconds.


0000H n/a
Dependence
n/a
2.7 002:1248 NE_LOGICAL_CONFIGURATION

Descriptive name
Network Element’s system type
The value of the PRFILE parameter 002:1248 NE_LOGICAL_CONFIGURATION
determines the system type of the Network Element. See Parameter values for further
information.
PRFILE control
parameter values.
Parameter values

0000H Not configured with two SYM-MXUs. The RNC is RNC196 Capacity Step
1 - 5.
0001H Two SYM-MXUs configured. The RNC is RNC196 Capacity Step 6 - 7 or
RNC450 Capacity Step 1 - 3.
0004H The RNC is RNC2600 with SYM-MXU MX1G6/-A.

0000H n/a
Dependence
n/a

2.8 002:1296 RN22_FEATURE_OPT_009

Descriptive name
RN2.2 feature optionality 009
This PRFILE parameter controls a series of RN2.2 features, which have been improved
or changed from RN3.0 CD3.0 onwards with the following features:
• RAN1302: Non-Performing Cell Recovery
• RAN1810: Sleeping Cell Improvement
• RAN1823: Recovery Logging Improvement
For more details and activation instructions, see Features RAN1302, RAN1810 and

RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.
PRFILE control
parameter values.
Parameter values

0000H-FF00H As per the functionalities of the following features:

0000H n/a
Dependence
The following are the feature dependencies:
For dependencies on other parameters, see Features RAN1302, RAN1810 and


2.9 002:1297 RN22_FEATURE_OPT_008

Descriptive name
RAN914: Flexi WCDMA BTS 1900 feature is activated with this PRFILE parameter.
PRFILE control
parameter values.
Parameter values

0000H-FF00H As per RAN914: Flexi WCDMA BTS 1900 functionality.

0000H n/a
Dependence
RAN914: Flexi WCDMA BTS 1900
2.10 002:1300 RN22_FEATURE_OPT_004

Descriptive name
The value of this PRFILE parameter determines if the High-speed Packet Access
(HSPA) Service Indicator is enabled or not.
For instructions, refer to Activating HSPA Service Indicator within the RAN1164: HSPA
Service Indicator documentation.

PRFILE control
parameter values.
Parameter values

0000H High-speed Downlink Packet Access (HSDPA) Service Indicator is not
active.
0024H HSDPA Service Indicator is active.

0000H n/a
Dependence
RAN1164: HSPA Service Indicator
2.11 002:1370 AMR_LIC_WARN_IN_USE

Descriptive name
AMR license warning in use
IPA-RNC, mcRNC
This PRFILE parameter controls the license_capacity_warning alarm. When this value is
set to TRUE (1H), license_capacity_warning alarm is reported. Otherwise, no such alarm
is reported in AMR contexts.
PRFILE control
parameter values.
Parameter values

0000H No license_capacity_warning alarm is reported.
0001H The license_capacity_warning alarm is reported according to the AMR
amount and AMR license warning threshold.


0000H n/a
Dependence
n/a
2.12 002:1371 AMR_LIC_WARN_THRESHOLD

Descriptive name
AMR license warning threshold
IPA-RNC, mcRNC
This PRFILE parameter defines the threshold for the alarm
license_capacity_warning, which means that the AMR capacity has reached a
certain level of licensed_amr_capacity and has to warn the user. The given value
stands for the percentage of licensed_amr_capacity.
PRFILE control
parameter values.
Parameter values

0000H Threshold is set to 0% of licensed_amr_capacity.
005AH Threshold is set to 90% of licensed_amr_capacity.
0064H Threshold is set to 100% of licensed_amr_capacity.

005AH n/a
Dependences
n/a
2.13 002:1372 AMR_LIC_WARN_DUR

Descriptive name
AMR license warning duration
IPA-RNC, mcRNC

This PRFILE parameter defines the duration where AMR capacity exceeds the warning
threshold, which is one of the conditions that must be fulfilled to report the
license_capacity_warning alarm. The duration is given in seconds.
PRFILE control
parameter values.
Parameter values

0000H-0E10H Duration is set between 0 and 3600 seconds.

02058H (600 seconds) n/a
Dependence
n/a
2.14 002:1373 AMR_LIC_WARN_DUR_CANCEL

Descriptive name
AMR license cancel warning duration
IPA-RNC, mcRNC
This PRFILE parameter defines the duration where the AMR capacity cancels the status
of exceeding the warning threshold, which is one of the conditions that must be fulfilled
to cancel the license_capacity_warning alarm. The duration is given in days.
PRFILE control
parameter values.
Parameter values

0000H-001EH Duration is set between 0 and 30 days.


000AH (10 days) n/a
Dependence
n/a
2.15 002:1374 AMR_LIC_ALARM_IN_USE

Descriptive name
AMR license alarm in use
IPA-RNC, mcRNC
This PRFILE parameter controls the license_capacity_exceeded alarm. When this value
is set to TRUE, license_capacity_exceeded alarm works as defined. Otherwise, no such
alarm is reported in AMR contexts.
PRFILE control
parameter values.
Parameter values

0000H The license_capacity_exceeded alarm is not reported.
0001H The license_capacity_exceeded alarm is reported.

0000H n/a
Dependence
n/a
2.16 002:1375 AMR_LIC_ALARM_DUR_CAL

Descriptive name
AMR license cancel alarm duration

IPA-RNC, mcRNC
This PRFILE parameter defines the duration where the AMR capacity cancels the status
of exceeding the alarm threshold, which is one of the conditions that must be fulfilled to
cancel the license_capacity_exceeded alarm. The duration is given in days.
PRFILE control
parameter values.
Parameter values


00AH (10 days) n/a
Dependence
n/a
2.17 002:1376 PS_LIC_WARN_IN_USE

Descriptive name
PS license warning in use
IPA-RNC, mcRNC
This PRFILE parameter controls the license_capacity_warning alarm. When this value is
set to TRUE, the license_capacity_warning alarm works as defined. Otherwise, no such
alarm is reported in the context of PS throughput.
PRFILE control
parameter values.
Parameter values

0000H No license_capacity_warning alarm is reported.


0001H The license_capacity_warning alarm is reported according to the AMR
amount and PS license warning threshold.

0000H n/a
Dependence
n/a
2.18 002:1377 PS_LIC_WARN_THRESHOLD

Descriptive name
PS license warning threshold
IPA-RNC, mcRNC
This PRFILE parameter defines the threshold for the license_capacity_warning alarm,
which means that the PS throughput capacity has reached a certain level of
licensed_ps_capacity and needs to warn the user. The given value stands for the
percentage of licensed_ps_capacity.
PRFILE control
parameter values.
Parameter values

0000H Threshold set to 0% of licensed_amr_capacity.
005AH Threshold set to 90% of licensed_amr_capacity.
0064H Threshold set to 100% of licensed_amr_capacity.

005AH n/a
Dependence
n/a

2.19 002:1378 PS_LIC_WARN_DUR

Descriptive name
PS license warning duration
IPA-RNC, mcRNC
This PRFILE parameter defines the duration where the PS throughput capacity exceeds
the warning threshold, which is one of the conditions that must be fulfilled to report
license_capacity_warning alarm in PS situation. The duration is given in seconds.
PRFILE control
parameter values.
Parameter values

0000H-0E10H Duration is set between 0 and 3600 seconds.

0258H (600 seconds) n/a
Dependence
n/a
2.20 002:1379 PS_LIC_WARN_DUR_CANCEL

Descriptive name
PS license cancel warning duration
IPA-RNC, mcRNC
This PRFILE parameter defines the duration where the PS throughput capacity cancels
the status of exceeding the warning threshold, which is one of the conditions that must
be fulfilled to cancel the license_capacity_warning alarm in PS situation. The duration is
given in days.
PRFILE control

parameter values.
Parameter values

0000H - 001EH Duration is set between 0 and 30 days.

00AH n/a
Dependence
n/a
2.21 002:1380 PS_LIC_ALARM_IN_USE

Descriptive name
PS license alarm in use
IPA-RNC, mcRNC
This PRFILE parameter controls the license_capacity_exceeded alarm. When this value
is set to TRUE, the license_capacity_exceeded alarm works as defined. Otherwise, no
such alarm is reported in the PS context.
PRFILE control
parameter values.
Parameter values

0000H The license_capacity_exceeded alarm is not reported.
0001H The license_capacity_exceeded alarm is reported.

0000H n/a
Dependence
n/a

2.22 002:1381 PS_LIC_ALARM_DUR_CAL

Descriptive name
PS license cancel alarm duration
IPA-RNC, mcRNC
This PRFILE parameter defines the duration where the PS throughput capacity cancels
the status of exceeding the alarm threshold, which is one of the conditions that must be
fulfilled to cancel the license_capacity_exceeded alarm. The duration is given in days.
PRFILE control
parameter values.
Parameter values


00AH (10 days) n/a
Dependence
n/a
2.23 002:1546 ICSU_WINDOW_SIZE

Descriptive name
ICSU WINDOW SIZE
IPA-RNC: RN7.0
mcRNC: mcRNC3.0
The value of this PRFILE parameter limits the number of ongoing radio network (RNW)
initialization and recovery tasks, such as the following:
• Base transceiver station (BTS) initialization

• Cell setup and recovery
• Common channel creation and recovery
• Common measurement initialization and recovery
• Node B application part (NBAP) link establishment and release
• High-speed packet access (HSPA) configuration and recovery
PRFILE control
parameter values.
Parameter values

0000H ICSU WINDOW SIZE is not in use and there is no limit to the number of
ongoing RNW initialization and recovery tasks.
0001H-FF00H The number of tasks is limited to a value between 1 and 65280.

Current default value is 0190H (starting from n/a
RN7.0 and mcRNC 3.0). Earlier default value is
03CH.
Dependences
n/a
2.24 002:1632 HSUPA_SERVICE_INDICATOR

Descriptive name
HSUPA Service Indicator
IPA-RNC, mcRNC
The value of this PRFILE parameter indicates whether the High-speed Uplink Packet
Access (HSUPA) Service Indicator feature is in use or not. For more details, see
Activating HSPA Service Indicator in Activating and Verifying RU10 Features
PRFILE control
parameter values.
Parameter values

0000H HSUPA Service Indicator feature is not in use.


0066H HSUPA Service Indicator feature is in use.

0000H n/a
Dependence
For more information, see the following dependencies:
• RAN1164: HSDPA Service indicator
• RAN826: Basic HSUPA
• RAN763: Basic HSDPA with QPSK and 5 codes in the RNC
2.25 002:1649 IP_LINK_BREAK_REL_DELAY

Descriptive name
Delay for call release in IP link break
IPA-RNC, mcRNC
When IP-based transport is used, this PRFILE parameter defines the call resource
release delay in case of link failure. The PRFILE parameter is adjusted to allow a
suitable tolerance for short link breaks without releasing calls associated with the failed
link. The parameter value is given in seconds.
PRFILE control
parameter values.
Parameter values

0000H Release of calls is immediate.
0001H Release delay duration is 1 second.
00AH Release delay duration is 10 seconds.
0010H Release delay duration is 16 seconds.
001EH Release delay duration is 30 seconds.


0000H n/a
Dependence
n/a
2.26 002:1662 REVERTIVE_SWO_IN_USE

Descriptive name
Revertive Switchover is in use
IPA-RNC
The PRFILE parameter 002:1662 REVERTIVE_SWO_IN_USE indicates whether the
“Revertive Switchover” feature is in use or not.
PRFILE control
parameter values.
Parameter values

0000H The Revertive Switchover functionality is not in use.
00FFH The Revertive Switchover functionality is in use.

0000H n/a
Dependence
n/a
2.27 002:1664 RN50_MAINT_02

Descriptive name
RNC workaround for UE problem
IPA-RNC, mcRNC

This PRFILE parameter controls a workaround for call setup failures because of certain
user equipment (UE) problems in handling lossless PDU size change. With this
functionality RNC packs RB mapping info for the release 5 UE user plane RB again for
DCH/DCH allocation and sends explicit RLC information for SRB3.
For further instructions, as well as the list of possible values, see TS-RNC-SW-149
(section 5.5).
PRFILE control
parameter values.
Parameter values

0000H n/a
Dependence
n/a
2.28 002:1666 RN50_MAINT_03

Descriptive name
RU10 relocation restriction
IPA-RNC, mcRNC
If a UE makes a cell reselection in Cell_FACH from the DRNC cell during an ongoing
state transition from Cell_DCH to Cell_FACH in the SRNC, then the SRNC in RU20
sends the current configuration of the UE to the Target RNC in the relocation container.
RU10 RNC cannot handle it correctly in this case. This causes the Target RNC to include
the RB-Information-Reconf information in the CUC, but the UE rejects it since it has not
completed the previous reconfiguration of state transition.
From RN5.0 onwards a change has been made on the SRNC side to check the release
version of the Target RNC. If the Target RNC release version is 6 or lower, then the RNC
does not pack the dual mapping for user plane RBs when the UE has made a cell
reselection during an ongoing state transition to Cell_FACH on the SRNC side. For more
instructions, see TS-RNC-SW-148 (section 5.5 and 6.1).
PRFILE control
parameter values.

Parameter values

0000H The functionality is not active.
0001H The functionality is active.

0000H n/a
Dependence
n/a
2.29 002:1668 RN50_MAINT_05

Descriptive name
RU10/RU20 counter functionality.
IPA-RNC, mcRNC
PRFILE parameter 002:1668 RN50_MAINT_05 is used to activate counter
functionality. For instructions, see TS-RNC-SW-148 (section 5.2 and 6.1).
PRFILE control
parameter values.
Parameter values

0000H RU20 counter functionality is used.
0001H RU10 counter functionality is used.

0000H n/a
Dependence
n/a

2.30 002:1669 RN50_MAINT_06

Descriptive name
RNC workaround for UE problem.
IPA-RNC: RN7.0, RN8.0, RN8.1
mcRNC: mcRNC 3.0, mcRNC4.1
UE using Qualcomm chipset does not register to the NW in case the SB1 and any SIB
information are in the same segment (frame). A workaround has been implemented,
where the SIB scheduling mechanism always sends SB1 information in separate frames.
For further information, see technical support note TS-RNC-SW-149
PRFILE control
parameter values.
Parameter values

0000H The workaround is active.
0001H
0002H The workaround is not active.

0000H n/a
Dependence
n/a
2.31 002:1670 RN50_MAINT_07

Descriptive name
RNC workaround for CN problem
IPA-RNC: RN7.0, RN8.0, RN8.1 onwards
mcRNC: mcRNC3.0, mcRNC4.1 onwards

Release 5/6 Qualcomm-based user equipment (UE) cannot make PS calls in Release 7
network when a release 7 quality of service (QoS) is provisioned to the subscriber. A
workaround is controlled via the 1stbit of this PRFILE parameter.
For more information, refer to technical support note TS-RNC-SW-149.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.32 002:1671 RN50_MAINT_08

Descriptive name
This PRFILE parameter controls how E-DCH information in RRC:Physical Channel
Reconfiguration and RRC:Transport Channel Reconfiguration are sent when E-DCH
related parameters are changed by the base transceiver station (BTS). It is
recommended to activate the workaround when 2 ms TTI for high-speed uplink packet
access (HSUPA) is activated in the network.
PRFILE control
parameter values.

Parameter values


0000H n/a
Dependence
n/a
2.33 002:1673 RN50_MAINT_10

Descriptive name
This PRFILE parameter controls a workaround for radio link (RL) failures that take place
when SRB of a Qualcomm chipset-based user equipment (UE) is assigned to a certain
DL Spreading Code.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a

2.34 002:1684 RN50_MAINT_11

Descriptive name
SIB Optimizations
RNC RNC19
mcRNC mcRNC19
When AdjgTxPwrMaxRACH inter-system adjacency (ADJG) parameter of the GSM
neighbour cell is set to the maximum value (33 dBm), the second bit of this PRFILE
parameter is used to disable the sending of the information element (IE) Maximum
allowed UL TX power for the GSM neighbour cell in the SIB11/11bis/12 message.
The absence of this IE in the SIB11/SIB11bis/SIB12 message means that the UE can
use its maximum output power (according to the UE's radio access capability) when
accessing the GSM cell on the RACH.
g Note: After parameter value has been modified, cell lock/unlock needs to be performed
for the change to take effect.
PRFILE control
See Modifying PRFILE parameters to find information on how to interrogate and modify
PRFILE parameter values.
Parameter values

0000H Disabling the sending of the IE: "Maximum allowed UL TX power" for the
GSM neighbour cell in the SIB11/11bis/12 message is not active.
0002H Enabling the sending of the IE: "Maximum allowed UL TX power" for the
GSM neighbour cell in the SIB11/11bis/12 message is active.
Default value(s) Effect

0000H The functionality is disabled.
Dependences
n/a
2.35 002:1686 RN50_MAINT_13

Descriptive name
RNC workaround for UE TTI reconfiguration problem

This PRFILE parameter controls a workaround for 10 ms to 2 ms TTI reconfiguration
problem causing call drops for some Qualcomm chipset-based user equipments.
For more information see technical support note TS-RNC-SW-149.
PRFILE control
parameter values.
Parameter values

0001H The workaround is active for all user equipments.
0002H The workaround is active for Release 6 and older user equipments.

0000H n/a
Dependence
n/a
2.36 002:1687 RN50_MAINT_14

Descriptive name
It has been identified that some user equipments retransmit RRCConnectionRequest too
soon, indicating a protocol error even before the user equipment receives the original
RRCConnectionSetup.
This PRFILE parameter enables a workaround in which the RNC waits for
RRCConnectionComplete for a specific time. If RRCConnectionSetupComplete is
received during waiting time, then RRCConnectionRequest with protocol error indication
is not processed.

For further instructions, refer to technical support note TS-RNC-SW-149.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.37 002:1689 RN50_MAINT_15

Descriptive name
Usage of AMR {5.9, 4.75} Codec Set causes UL muting for some R99 UEs
This PRFILE parameter controls a workaround for UL muting in Release 99 user
equipment (UE). If the workaround is activated, the RNC does not use AMR {5.9, 4.75}
Codec Set for Release 99 UE even if {5.9, 4.75} is enabled by cell level RWN
CSAMRmodeSET parameter.
PRFILE control
parameter values.
Parameter values



0000H n/a
Dependence
n/a
2.38 002:1691 RN50_MAINT_16

Descriptive name
RNC workaround for UE voice quality problem
This PRFILE parameter controls two separate workarounds for user equipment (UE)
voice quality issues:
• Some UE models are not able to handle Directed RRC connection setup (DRRC)
functionality during CCH to DCH state transition. The first bit of this PRFILE
parameter controls whether DRRC is to be used during CCH-to-DCH state transition.
• If the procedure is done with state transition from Cell_FACH to Cell_DCH, some
UEs are not able to handle CS voice on DCH setup with transparent mode RLC
configuration. The fifth bit of this PRFILE parameter controls whether additional RRC
messages are sent so that Release 5 UEs might differentiate state transition
procedures from interfrequency hard handover procedures.
PRFILE control
parameter values.
Parameter values

0000H Both workarounds are disabled.
0001H Workaround 1 is enabled.
0010H Workaround 2 is enabled.

0000H n/a

Dependence
n/a
2.39 002:1696 RN50_MAINT_20

Descriptive name
Timer correction for CM Plan upload failure.
IPA-RNC, mcRNC
PRFILE parameter 002:1696 RN50_MAINT_20 defines the value of an RNC timer
allowing extra compression time for the upload of big XML plans.
The value of the parameter corresponds to the timer duration in minutes, with a
maximum value of 60 minutes and an incremental step of one minute.
PRFILE control
parameter values.
Parameter values

0000H The delay timer is set to 10 minutes.
0001H - 003CH The value of the delay timer is set between 1 and 60 minutes.

0000H n/a
Dependence
n/a
2.40 002:1697 RN50_MAINT_21

Descriptive name
RNC improvement to prevent unnecessary RL signaling during BTS transport
congestion.
IPA-RNC, mcRNC

PRFILE parameter 002:1697 RN50_MAINT_21 prevents unnecessary RL signaling
during BTS transport congestion. It is recommended to activate this functionality only if
continuous Iub AAL2 signaling congestion (alarm 1192 SSCOP TRANSMIT BUFFER
OVERFLOW) occurs in Iub configurations with very limited bandwidth (less than
3xE1/T1).
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.41 002:1699 RN50_MAINT_23

Descriptive name
RNC workaround for UE problem: Direct transition problem for CELL DCH to CELL/URA
PCH
RNC: RN7.0, RN8.0, RN8.1 onwards
Certain Release 5 user equipment (UE) models are not able to correctly handle direct
transition from Cell_DCH to Cell_PCH network commands.This PRFILE parameter
controls a workaround which disables the direct transitions for Release 5 and older UEs.
PRFILE control
parameter values.
Parameter values



0000H n/a
Dependence
n/a
2.42 002:1700 RN50_MAINT_24

Descriptive name
Workaround to manage SIB update delay functionality in RN5.0.
IPA-RNC, mcRNC
PRFILE controllable timer is implemented to RNC. Timer is recommended to be used in
case of continuous Core Network problems, when the states of Iu links change
repeatedly. This timer prevents sending SIB updates while the timer is running, which
reduces the number of registration attempts generated by UEs.
The parameter value defines the timer duration in steps of 10 seconds. The range is 10
to 652800 seconds.
PRFILE control
parameter values.
Parameter values

0000H The delay timer is not active.
0001H - FF00H The delay timer is active. Values range from 10 to 652800 seconds, with a
10 second step.

0000H n/a
Dependence
n/a

2.43 002:1701 RN50_MAINT_25

Descriptive name
Data forwarding support for PS service during SRNS relocation.
IPA-RNC, mcRNC
PRFILE parameter 002:1701 RN50_MAINT_25 controls a workaround functionality to
forward the buffered data in PDCP/RLC layer to target RNC during SRNC relocation.
When data forwarding is enabled during SRNS relocation, RNC L3 commands PDCP
layer to start data forwarding. For the forwarded data, PDCP layer clears the protocol
type bit in GTP header to distinguish it from normal UL data, and starts data forwarding.
Platform part will route data correctly based on the indication from PDCP layer. The
protocol type bit in GTP header is set again when forwarding PDUs to target RNC.
When data forwarding is disabled during SRNS relocation, there is no change compared
to current implementation. That is buffered data will be dropped by PDCP layer and, the
new DL data coming in will be forwarded to target RNC directly by interface unit
(GTPU/EIPU).
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.44 002:1702 RN50_MAINT_26

Descriptive name
RRC Access Failure due to RADIO

IPA-RNC, mcRNC
PRFILE parameter 002:1702 RN50_MAINT_26 controls the use of maximum HSDPA
traffic power (Pmax) from target cell in initial power calculation.
By default the initial DL transmission power for UEs reporting low EcNo is calculated on
the basis of the last reported value from the BTS. PRFILE parameter 002:1702
RN50_MAINT_26 establishes a threshold value for low EcNo, and enables the use of
maximum HSDPA traffic power so that the initial DL power is increased and there is a
higher DRRC to HSDPA layer success rate.
It cases when the calculated initial power for DRRC is equal to the maximum initial
power (Ptc,init = Ptx,max) DRRC has less chances to succeed. PRFILE parameter
002:1702 RN50_MAINT_26 can also determine whether the DRRC is to start in these
cases.
In cases where there is too low initial power with low EcNo, RRC connection setup
without DRRC may also fail. To prevent this problem PRFILE parameter 002:1702
RN50_MAINT_26 implements a functionality which uses maximum HSDPA traffic power
(Pmax) in initial power calculation in non-DRRC cases.
PRFILE parameter 002:1702 RN50_MAINT_26 can also be used to set the EcNo
threshold which defines the lowest reported EcNo for DRRC. If an UE reports lower
EcNo value, DRRC is not done and the UE stays in current layer. This prevents DRRCs
from too poor radio conditions.
PRFILE control
parameter values.
Value masks Effect
1st bit xxxx xxxx xxxx Determines whether the functionality is active. Default value 0

xxx0 equals inactive functionality.
xxxx xxxx xxxx
xxx1
2nd to 7th xxxx xxxx x000 Determine EcNo threshold value. Range -23.5 dB to 0 dB with a

bit 000x step of 0.5 dB.
xxxx xxxx x110 Value XX01H has the same effect as value XX35H, with a
000x threshold of -11 dB.
8th bit xxxx xxxx 0xxx Determines whether DRRC is canceled if Ptc,init = Ptx,max.

xxxx Default value 0 means DRRC is not canceled in those cases.
xxxx xxxx 1xxx
xxxx
9th bit xxxx xxx0 xxxx Determines the use of Pmax in initial power calculation for non-

xxxx DRRC cases. Default value 0 means the functionality is not
enabled.
xxxx xxx1 xxxx
xxxx
10th to 15th x000 000x xxxx Determine the lowest EcNo threshold value which enables

bit xxxx DRRC. Range -23.5 dB to 0 dB with a step of 0.5 dB.

Value masks Effect

x110 000x xxxx
xxxx
Default value Allowed value(s) Forbidden value(s)

0000H 0000H - 61E1H n/a
Dependence
n/a
2.45 002:1703 RN50_MAINT_27 and 002:1704

RN50_MAINT_28
Descriptive name
HSUPA Initial SIR target offset enhancement and DynPwrOffsetUsage alignment.
IPA-RNC, mcRNC
PRFILE parameters 002:1703 RN50_MAINT_27 and 002:1704 RN50_MAINT_28
control an RNC workaround to configure the HSUPA initial SIR target offset value, in
order to reduce RL power and decrease RTWP values. The change applies only to first
RL setup. There are no changes to RL reconfiguration or SCC. There also are no branch
additions.
When the functionality is enabled, RNC subtracts the configured value from the
SIRDPCCHInitialEDCH, which is dependent on the selected high or low DPCCH
power offsets, Dynamic HSUPA Power Offsets feature, the spreading factor, and the E-
DCH TTI value. The minimum SIR target parameter is also checked, so that it is not
higher than the subtracted SIR value.
If the Dynamic HSUPA Power Offset feature is disabled, the parameter values
corresponding to high power offsets are used.
For detailed description and activation method see TS-RNC-SW-159.
PRFILE control
parameter values.
Parameter values
The offset values for PRFILE parameter 002:1703 RN50_MAINT_27 are defined as
follows:

MS 16 15 14 13 12 11th 10 9th 8th 7th 6th 5th 4th 3rd 2nd 1st LS
B th th th th th th B
LOW DPPCH PO LOW DPPCH PO LOW DPCCH PO HIGH DPCCH PO

SF4+10ms TTI SF4+2ms TTI (SF8,16,32,64,128)
The offset values for PRFILE parameter 002:1704 RN50_MAINT_28 are defined as
follows:
MS 16 15 14 13 12 11th 10 9th 8th 7th 6th 5th 4th 3rd 2nd 1st LS
B th th th th th th B
LOW DPPCH PO LOW DPPCH PO LOW DPCCH PO LOW DPCCH PO

2xSF2+10ms TTI 2xSF2+2ms TTI 2xSF4 + 10ms TTI 2xSF4+2ms TTI
Each of the individual nibbles of the parameters carries SIR offset information:
Individual nibble Effect

value
0H The SIR offset is set to 0.0 dB.
AH The SIR offset is set to 5.0 dB.
BH The SIR offset is set to 5.5 dB.
CH The SIR offset is set to 6.0 dB.

0000H 0000H - CCCCH n/a
Dependence
n/a
2.46 002:1706 RN50_MAINT_29

Descriptive name

Workaround to release RRC connection if Location Area Update procedure is rejected by
CN
RNC RNC19
mcRNC mcRNC19
If the CS CN rejects the Location Area Update (LAU) procedure, a workaround can be
activated with PRFILE to release the RRC connection soon (even if there is an active PS
connection). Such a forced release is the last-ditch attempt to push UE to re-attempt the
LAU procedure (if no successful LAU soon enough) and meant to guarantee that the UE
is reachable for terminating CS calls.
PRFILE parameter 002:1706 RN50_MAINT_29 sets the value of a timer that is used
to release the RRC connection after the CN has rejected the LAU and if the UE has not
made a LAU re-attempt while the timer is running. A couple of re-attempts are allowed,
but if they are again rejected by the CN, then the RRC connection is released. By default
(value 0000 in the PRFILE), this workaround functionality is not active. If this workaround
is activated, the timer value should be set at least 20s, anyway longer than typical NAS
procedure timers used by the UEs and CNs.
PRFILE control
Parameter values

0000H The timer functionality is not active.
0006H The timer is set to 10 seconds.
g Note: This value is not recommended.
000AH The timer is set to 20 seconds.
000EH The timer is set to 30 seconds.
001AH The timer is set to 120 seconds.
001EH The timer is set to 240 seconds.
Default value(s) Effect

Dependences
n/a

2.47 002:1716 RN50_MAINT_38

Descriptive name
Improvements for RLC parametrization for SRB on HSPA and RNC workaround to
prevent the 2ms TTI usage based on UE releases.
IPA-RNC, mcRNC
PRFILE parameter 002:1716 RN50_MAINT_38 controls the following improvements:
RLC parameters for SRB on HSPA
By default RNC uses 2ms TTI for SRB on HSUPA for Rel.6 UEs. It has been noticed that
certain Rel.6 UE models are not able to handle RB reconfiguration involving RLC change
with AT. Certain UE have trouble interpreting changes in RLC parameters if these
changes take place while they perform SL switch with AT.
When the new functionality is activated, RLC parameters for SRB on HSPA will use the
same values as SRB on DCH. The RNC does not need to send any extra RLC
parameters or RRC signaling to the UE.
RNC workaround: Disabling of 2ms TTI based on UE release
Some Rel.6 and Rel.7 UEs cannot handle 2ms TTI allocation correctly, causing setup
failure counters to be impacted.
When the new functionality is activated, 2ms allocation will not be attempted for the
following scenarios:
• user plane setup
• channel type switch
• TTI switch
• handovers
PRFILE control
parameter values.
Parameter values

0010H The RLC parameters for SRB on HSPA workaround is active.
0001H Usage of 2ms for Rel.6 UEs is restricted.
0011H Usage of 2ms for Rel.6 UEs is restricted and the RLC parameters for SRB
on HSPA workaround is active.
0002H Usage of 2ms for Rel.7 UEs is restricted.


0012H Usage of 2ms for Rel.7 UEs is restricted and the RLC parameters for SRB
on HSPA workaround is active.
0003H Usage of 2ms for both Rel.6 and Rel.7 UEs is restricted.
0013H Usage of 2ms for both Rel.6 and Rel.7 UEs is restricted and the RLC
parameters for SRB on HSPA workaround is active.

0000H n/a
Dependence
n/a
2.48 002:1717 RN50_MAINT_39

Descriptive name
Incorrect SRB congestion handling.
IPA-RNC, mcRNC
PRFILE parameter 002:1717 RN50_MAINT_39 can be used to activate a correction
on SRB congestion handling.
RNC mishandles SRB code tree congestion
Spreading code consumption of standalone signaling link depends on the SRB DCH bit
rate. SRB DCH 13.6 kbps reserves SF 128, and SRB DCH 3.4 kbps reserves SF 256.
By default, in case of spreading code congestion, retrial with lower SRB DCH bit rate 3.4
kbps is not performed. This can result in RRC connection setup failures.
By activating PRFILE parameter 002:1717 RN50_MAINT_39, SRB 3.4 kbps (SF 256)
retrials will take place in cases when SRB DCH 13.6 kbps (SF 128) experiences code
tree congestion.
g Note: An exception to this rule are RRC connection requests, where Core Network
domain and Establishment Cause indicates AMR speech call, that is Core Network
domain is CS and Establishment Cause is Conversational Call (Originating/Terminating)
or Emergency Call. In this case, if SRB DCH 13.6 kbps (SF 128) experiences code tree
congestion, SRB 3.4 kbps (SF 256) retry will not be performed, because AMR CS
(DCH) speech call typically needs SF 128.
RNC makes unnecessary retrials for lower bit rate SRB in case of BTS congestion.

SRB bit rate does not affect BTS CE consumption. BTS congestion of standalone
signaling link does not depend on the SRB DCH bit rate. Both SRB DCH 13.6 kbps and
SRB DCH 3.4 kbps consume the same amount of BTS HW capacity. By default,
unnecessary retrials with SRB DCH 3.4 kbps are done in case SRB DCH 13.6 kbps is
congested. This results in extra NBAP signaling in these BTS congestion scenarios.
By activating PRFILE parameter 002:1717 RN50_MAINT_39, SRB 3.4 kbps retrials
will not be performed if SRB DCH 13.6 kbps experiences BTS HW congestion. Pre-
emption can be started directly with SRB DCH 13.6 kbps, which consumes the same
BTS HW capacity as SRB DCH 3.4 kbps.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.49 002:1760 RN50_MAINT_43

Descriptive name
Threshold value for setting and canceling alarms 3700 DSP POOL SEVERE ERRORS
and 3688 DSP SEVERE ERROR EXCEEDS THRESHOLD.
IPA-RNC: RN6.0 2.2 onwards
PRFILE parameter 002:1760 RN50_MAINT_43 can be used to set a threshold value
for the amount of DSP severe errors reported within eight minutes. When this threshold
is exceeded, alarms 3700 DSP POOL SEVERE ERRORS and 3688 DSP SEVERE
ERROR EXCEEDS THRESHOLD are raised. The alarms are cancelled when the
amount of DSP severe error drops below the threshold value.
PRFILE control
parameter values.

Parameter values

0000H - 0009H The alarm functionality is enabled. A default reporting threshold value of
40 is used.
000AH - FEFFH The alarm functionality is enabled. The reporting threshold is set between
10 and 65279.
FF00H The alarm functionality is disabled.

0000H n/a
Dependence
002:1760 RN50_MAINT_43 defines recovery of non-performing DSPs.
2.50 002:1765 RN50_MAINT_48

Descriptive name
HS-DSCH and E-DCH success rate decreased after Blind IFHO activation.
IPA-RNC, mcRNC
PRFILE control
parameter values.
Parameter values
Allowed Effect
value(s)
0000H The RNC uses the RSCP that UE has reported when calculating the DL initial
power.
0001H The functionality is disabled. RSCP is not used to define EcNo.
0002H - 30B4H The functionality is enabled. RSCP0 is defined by the 2nd to 8th bits, and
BackgroundEcNo is defined by bits 9th to 14th.
XX02H - XXB4H RSCP0 is assigned values from -119 dB to -30 dB, with a
step of 1 dB.
00XXH - 30XXH BackgrounEcNo is assigned values from -23.5 dB to 0 dB,
with a step of 0.5 dB.

0000H n/a

Dependence
n/a
2.51 002:1775 RN50_MAINT_57

Descriptive name
RNC workaround for UE problems.
IPA-RNC, mcRNC
PRFILE parameter 002:1775 RN50_MAINT_57 is used to control UE release in
hanging situations. When the functionality is activated, the RNC will release RRC
connection of such UEs and update failure counter for RRC connection. Users can re-
activate the session after release and the effects of this workaround are visible in KPIs.
This workaround is implemented for two problem scenarios, and each functionality can
be activated separately.
• Releasing UE after a failed Integrity Check for UL message and stuck.
• Releasing UE after a failed RRC message decoding for UL message and stuck.
PRFILE control
parameter values.
Parameter values

0000H Both functionalities are disabled.
0001H Releasing UE after a failed Integrity Check for UL message and stuck
functionality is enabled.
0002H Releasing UE after a failed RRC message decoding for UL message and
stuck is enabled.
0003H Both functionalities are enabled.

0000H n/a
Dependence
n/a

2.52 002:1776 RN50_MAINT_58

Descriptive name
Control for both DRRC and HSDPA layering functionalities between different frequency
bands
IPA-RNC, mcRNC
Directed RRC connection setup (DRRC)
RRC Connection Request messages do not include information about UE frequency
band capability. When Directed RRC connection setup (DRRC) is enabled, the RNC is
not able to distinguish which frequency bands UE supports and if UE is directed to
frequency band it does not support this will lead failed DRRC attempt.
DRRC is also more likely to fail between frequency bands than within the same
frequency band, even though both frequency bands are supported by the UE.
Substantial differences in wave length (for example between 2100 MHz and 900 MHz)
lead to differences in propagation and differences in cell coverage.
By default (RN6.0 1.4 onwards) DRRC is not allowed between frequency bands. It is
possible to enable this functionality with PRFILE parameter 002:1776
RN50_MAINT_58.
g Note: There are two exceptional frequency bands sharing the same two frequencies:
bands V and VI. DRRC between these frequency bands is always allowed.
HSDPA layering for UEs in common channel

HDSPA layering for UEs in common channel can also fail due to substantial differences
in wave length (for example between 2100 MHz and 900 MHz). These differences lead
to differences in propagation and differences in cell coverage. The problem becomes
visible when layer changes are done from lower frequency bands to higher frequency
bands.
By default layering for UEs in common channel is allowed between frequency bands. It is
possible to disable this functionality with PRFILE parameter 002:1776
RN50_MAINT_58.
g Note: This parameter does not have any effect on DRRC and HSDPA layering for UEs
in common channels done within one frequency band.
PRFILE control
parameter values.
Parameter values


0000H HSDPA layering for UEs in common channel is enabled, DRRC is
disabled.
0001H Both HSDPA layering for UEs in common channel and DRRC are
enabled.
0010H Both HSDPA layering for UEs in common channel and DRRC are
disabled.
0011H HSDPA layering for UEs in common channel is disabled, DRRC is
enabled.

0000H n/a
Dependence
n/a
2.53 002:1792 UP_CAP_UPGRADE

Descriptive name
Flexible user plane capacity
IPA-RNC, mcRNC
PRFILE parameter 002:1792 UP_CAP_UPGRADE is used to control the Flexible user
plane capacity functionality.
PRFILE control
parameter values.
Parameter values

0000H The flexible user plane capacity functionality is not active.
0001H The flexible user plane capacity functionality is active.

0000H n/a
Dependence
RAN2261: Flexible User Plane Capacity in RNC196 and RNC450

2.54 002:1798 OPT_BLOCK_MOVE_PREVENT

Descriptive name
Automated A2SU/A2SP load balancing prevention.
IPA-RNC
PRFILE parameter 002:1798 OPT_BLOCK_MOVE_PREVENT determines whether
automated load balancing between A2SU/A2SP units is prevented or not.
PRFILE control
parameter values.
Parameter values

0000H Automated load balancing between A2SU/A2SP units is allowed.
0001H Automated load balancing between A2SU/A2SP units is prevented.

0000H n/a
Dependence
n/a
2.55 002:1814 LCH_IN_USE

Descriptive name
Alarm triggered log collection functionality
PRFILE parameter 002:1814 LCH_IN_USE controls whether the alarm triggered log
collection functionality is in use or not.
PRFILE control

parameter values.
Parameter values

0000H Alarm triggered log collection functionality is not in use.
0001H Alarm triggered log collection functionality is in use. Notice alarm will be
set after the log zip file is generated.
0002H Alarm triggered log collection functionality is in use. Notice alarm will not
be set the after log zip file is generated.

0000H n/a
Dependence
RAN1805: RNC Event Triggered Symptom Data Collection
2.56 002:1816 IPMUX_MUX_DELAY

Descriptive name
Maximum delay of multiplexed PDU
PRFILE parameter 002:1816 IPMUX_MUX_DELAY sets the delay for multiplexed
packets. The value is given in milliseconds.
g Note: NPGE unit restart is needed for the new value to be taken into account.
PRFILE control
parameter values.
Parameter values

0001H The delay for multiplexed packets is set to 1ms.


0002H n/a
Dependence
RAN1886: Efficient transport for small IP packet
2.57 002:1817 DYNPWROFFSETUSAGE

Descriptive name
Dynamic Power Offset Usage
IPA-RNC, mcRNC
This parameter enables/disables the usage of dynamic power offsets for Rel.6 UE.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.58 002:1818 LCH_TRAN_IN_USE

Descriptive name
Alarm triggered log transfer functionality

This parameter indicates whether the alarm triggered log is transferred to OMS or not.
PRFILE control
parameter values.
Parameter values

0000H The alarm triggered log is not transferred to OMS.
0001H The alarm triggered log is transferred to OMS.

0001H n/a
Dependence
2.59 002:1819 LCH_DIR_SIZE

Descriptive name
Alarm triggered log directory size
This parameter indicates the size of the alarm triggered log in Mbytes. Default value 14H
(20 decimal) means that 20 Mbytes are used.
PRFILE control
parameter values.
Parameter values

0009H - 00FFH The size of the alarm triggered log is set between 9 and 255 Mbytes.

0014H n/a

Dependence
2.60 002:1840 B_PHASE1_SWITCH

Descriptive name
Switch for source based route phase1 function
IPA-RNC, mcRNC
PRFILE parameter 002:1840 B_PHASE1_SWITCH controls the source-based route
phase1 function.
PRFILE control
parameter values.
Parameter values

0000H Source based route phase1 is not active.
0001H Source based route phase1 is active.

0000H n/a
Dependence
n/a
Feature
RAN2190: Source Based Routing in the NPGE
2.61 002:1864 HSPA_OVER_IUR_EXT

Descriptive name
Extension of HSPA Over Iur
IPA-RNC, mcRNC

This parameter is used to control the use of Extension of HSPA Over Iur functionality.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.62 002:1868 EDPDCHPowerInterUsage

Descriptive name
EDPDCH power interpolation for 2ms and 10ms TTI
This PRFILE parameter controls the usage of EDPDCH Power Interpolation, which is
active by default.
However, this functionality is not fully supported by the RN7.0/WN7.0 SW combination,
and there is a minor increase in HSDPA/HSUPA drops due to radio link fails (HS-
DSCH/DCH PACKET CALL REL DUE TO RL FAIL / HS-DSCH/E-DCH PACKET CALL
REL DUE TO RL FAIL).
It is recommended to disable the EDPDCH Power Interpolation functionality until:
• all the base transceiver stations connected to the RNC are upgraded to WN8.0 or
higher
• RNC is upgraded to RN7.0 3.0 or higher
PRFILE control

parameter values.
Parameter values

0000H EDPDCH Power Interpolation is active.
0001H EDPDCH Power Interpolation is not active.

0000H n/a
Dependence
n/a
2.63 002:1886 RN60_MAINT_10

Descriptive name
Workaround for unstable HSUPA service for 10ms TTI users, in case of BTS base band
HW limitation in WN7.0 BTS SW when F-DPCH is enabled
IPA-RNC, mcRNC
PRFILE parameter 002:1886 RN60_MAINT_10 controls a workaround for unstable
HSUPA service, defining whether WN7.0 BTS hardware reservation can be done with E-
TFCI table 1. When this functionality is active, the capacity of the BTS sub unit(s) can be
used more efficiently in case of BTS BB hardware limitation. This improves the stability
of HSUPA services for 10ms TTI users with F-DPCH enabled.
PRFILE control
parameter values.
Parameter values


0000H n/a

Dependence
n/a
2.64 002:1888 RN60_MAINT_12

Descriptive name
RNC workaround to UE problems with blind IFHO for PS services.
IPA-RNC, mcRNC
PRFILE parameter 002:1888 RN60_MAINT_12 controls a series of workarounds for
UE problems with blind IFHO. These workarounds can be set up independently for PS
and CS service.
If activated for CS, the RNC will do blind IFHO for AMR RAB in Cell_DCH state. In the
PS case, the RNC will do blind IFHO for PS RAB in Cell_DCH state. Both CS and PS
blind IFHO will be made in two stages:
• IFHO using Physical Channel Reconfiguration, Transport Channel Reconfiguration or
Radio Bearer Reconfiguration procedure.
• RB setup.
Additionally, it is also possible to prevent blind IFHO for R99 capable UEs in PS NRT
RAB setup.
g Note: The default setting has R99 prevention inactive and both PS and CS
workarounds active.
PRFILE control
parameter values.
Parameter values
7th 6th 5th 4th 3rd 2nd 1st Effect

bit bit bit bit bit bit bit
x x Both bits need to carry the same value:
• 0: CS workaround is active.
• 1: CS workaround is not active.
x • 0: PS workaround is active.
• 1: PS workaround is not active.
x • 0: Prevention of blind IFHO for R99 capable UEs in
PS NRT RAB is not active.

7th 6th 5th 4th 3rd 2nd 1st Effect

bit bit bit bit bit bit bit
• 1: Prevention of blind IFHO for R99 capable UEs in
PS NRT RAB is active.
x • 0: Ensures that the PS workaround keeps the same
transport channel in use both in target and source
cells.
• 1: The PS workaround may use different transport
channels.
x • 0: Ensures that SRB mapping is based on source
cell measurement results during RB setup in case
there are no measurement results available from
the target cell after blind IFHO.
• 1: No constraint on SRB mapping.

0000H 0000H - 007BH n/a
Dependence
n/a
2.65 002:1889 RN60_MAINT_13

Descriptive name
Cause value IE in NBAP: RL DELETION REQUEST and NBAP: RL RECONF CANCEL
message
IPA-RNC, mcRNC
With this PRFILE active, the "Cause" value IE is added as a Private Annex Z IE in the
NBAP:Radio Link Deletion Request/Radio Link Reconfiguration Cancel message. The
cause value IE can have "normal" and "abnormal" value. BTS will use abnormal cause
value to save failure call related statistics/data for the root cause investigations.
PRFILE control
parameter values.
Parameter values

0000H Cause value is included.


0001H Cause value is not included.

0000H n/a
Dependence
n/a
2.66 002:1892 RN60_MAINT_16

Descriptive name
IPA-RNC: RN7.0, , RN8.0, RN8.1 onwards
This PRFILE parameter controls the RNC workaround for Core Network problems,
where for some customers Core Networks require transport layer addresses to be sent in
a particular format so that video calls might become possible. Activating the workaround
solves the issue and does not impact other CNs.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a

2.67 002:1897 RN60_MAINT_22

Descriptive name
Usage of monitored cell measurement results on RACH to define the source cell for blind
IFHO.
IPA-RNC, mcRNC
PRFILE parameter 002:1897 RN60_MAINT_22 makes it possible to disable the use
of monitored cell (intra-frequency neighbor cell) in RACH measurement results. By
default RACH measurement results from the monitored cell can be used to define the
source cell for blind IFHO. Setting the 1st bit of parameter 002:1897
RN60_MAINT_22 to 1 ensures that:
• Blind IFHO is triggered only from the current cell.
• The RSCP value of the current cell is used when defining the initial power for blind
IFHO.
PRFILE control
parameter values.
Parameter values

0000H Monitored cell measurement results on RACH can be used to define the
source cell for blind IFHO.
0001H Monitored cell measurement results on RACH cannot be used to define
the source cell for blind IFHO.

0000H n/a
Dependence
n/a
2.68 002:1900 RN60_MAINT_25

Descriptive name

IPA-RNC, mcRNC
When RACH Intra Frequency Measurement Quantity is CPICH-RSCP in SIB11, this
PRFILE parameter controls a workaround in which active RNC delivers
maxReportedCellsOnRACH as CurrentCell.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.69 002:1902 RN60_MAINT_26

Descriptive name
UE mobility in Inter-RNC scenario
IPA-RNC, mcRNC
Originally, HSDPA with compressed mode is not supported by NSN drift RNC, therefore
it does not support HSDPA over Iur if compressed mode is either active or inactive. If the
serving RNC wants to modify the compressed mode status when HSDPA is active over
Iur, the DRNC rejects such request.
As an improvement to allow UE mobility in Inter-RNC scenario with different RAN
vendors, the RNC will accept HSDPA over Iur with compressed mode inactive or active.
PRFILE control
parameter values.
Parameter values



0000H n/a
Dependence
n/a
2.70 002:1903 RN60_MAINT_27

Descriptive name
Delayed Start of Dynamic HSUPA Power offsets due to number of HSPA users
PRFILE parameter 002:1903 RN60_MAINT_27 defines an additional threshold for
starting Dynamic HSUPA Power Offsets based on the number of HSPA users in a cell.
The operator may modify the threshold so that the use of low bit rate optimized HSUPA
power offsets is triggered later than by default.
The number of HSPA users in the cell is the sum of HSPA users with E-TTI=10 ms,
HSPA users with E-TTI=2ms and HSPA Equivalent users.
While the total number of HSPA users in the cell is below the threshold defined, only
CPICH RSCP or CPICH EcNo reported by the UE are taken into account in the Dynamic
HSUPA Power Offsets algorithm in order to determine when to trigger low bit rate
optimized HSUPA power offsets.
g Note: For more information, see TS-RNC-SW-159 Recommended parameter set and

enhanced algorithms for optimizing RRM functionalities.
PRFILE control
parameter values.
Parameter values

0000H The functionality is deactivated
0001H - 007FH The functionality is activated. The value sets the threshold of cell HSPA
users.


0000H n/a
Dependence
n/a
2.71 002:1904 RN60_MAINT_28

Descriptive name
Recovery of non-performing DSPs
IPA-RNC: RN6.0 2.2
g Note: This is not applicable to mcRNC.
The parameter performs an automatic DSP unit restart to recover from a failure that
cannot be resolved with a less invasive operation. In this context, a non-performing DSP
is a DSP unit that behaves abnormally and impacts operator services or KPIs. It has not
been detected by the system as a faulty unit. It might have been brought by software
issues, transient hardware issues, or permanent hardware issues.
The following tables provide the detailed values:
Table 1 Values in HEX and effects
Value (HEX) Effect
Mask Min Max Defaul
t
0.0.0.X 1 F 4 Maximum number of allowed DSP restarts per pool per day
0.0.X.0 0 F 3 Waiting time of automatic DSP restart after triggering (used
to avoid restarts because of short burst of errors and actual
value in minutes equals five times the value introduced)
0.X.0.0 0 F F DSP pool related settings, described separately (there is no
pool specific control for CDSP-C specific pools)
X.0.0.0 0 F 3 Leg setup error related settings (described separately)
Table 2 Bitmask values for 0.X.0.0 and effects
Bitmask value for 0.X.0.0 Effect
4th Bit 3rd Bit 2nd 1st Bit
Bit
X 0 - WO state in any pool when restarting is not considered.
1 - Check if >= 50% of WO DSPs per pool to allow restart.

Table 2 Bitmask values for 0.X.0.0 and effects (Cont.)
Bitmask value for 0.X.0.0 Effect
4th Bit 3rd Bit 2nd 1st Bit
Bit
X 0 - Restarts are disabled for HS-DCH Pool.
1 - Restarts are enabled for HS-DCH Pool.
X 0 - Restarts are disabled for CCH Pool.
1 - Restarts are enabled for CCH Pool.
X 0 - Restarts are disabled for HS CCH Pool.
1 - Restarts are enabled for HS CCH Pool.
Table 3 Bitmask values for X.0.0.0 and effects
Bitmask value for X.0.0.0 Effect
bit3 bit2 bit1 bit0
X 0 - DSP restarts are disabled for excessive leg setup errors.
1 - DSP restarts are enabled for excessive leg setup errors.
X 0 - DMPG restarts are disabled for excessive leg setup
errors.
1 - DMPG restarts are enabled for excessive leg setup
errors.
PRFILE control
parameter values.
Parameter values
Recommended Effect
value(s)
0000H This is the default value. Feature is enabled. Interpreted as 3F34H.
FF00H Feature is disabled.

0000H 0000H-FF00H n/a
Dependences
002:2258 LEG_ERROR_RATIO_HIGH parameter defines the threshold for triggering
excessive leg setup errors.

2.72 002:1905 RN60_MAINT_29

Descriptive name
TFCS reduction in the TFCS capability limitation of UE
RNC RN7.0 1.0 onwards
mcRNC mcRNC3.0 onwards
This PRFILE parameter defines two methods for limiting transport format combination
set (TFCS) when its size exceeds the user equipment (UE) capability. The TFCS
capability of the UE might be easily exceeded in the following situations:
• UE has multi-mode AMR established and more than one active PS bearers are
added in Release 99 or high-speed downlink packet access (HSDPA) configurations.
• Multi-mode AMR is set up on top of PS Release 99 or HSDPA connections.
On the other hand, the lack of TFCS capability might result in decreased PS DCH
throughputs (as low as 0 kbit/s).
If AMR is established on top of the PS DCHs as the TFO/TrFO call, the AMR codec set
is not limited in the AMR setup phase. AMR setup is only possible without releasing PS
DCH by further reducing the UL TFCS size (limiting the UL TFCS so that the UE can
transmit with one PS NRT DCH at a time in the TTI of the DCH, while it can transmit
freely with the remaining bearers). UEs are generally able to use bigger TFCSs in
downlink (DL) than in uplink (UL), so in most cases DL TFCS capability limitations are
avoided by reducing intermediate bit rates of the DL PS DCHs. The method is called
Limitation of PS NRT DCHs for UE TFCS capability, which is activated with the first bit
(LSB) of this parameter.
The TFCS capability bit rate limitations of the PS NRT DCHs established on top of the
multi-mode AMR call in progress are avoided by limiting the AMR to its lowest mode,
while the UE has PS NRT DCH active. Since PS DCH bit rates are practically equal
between multi-mode and single mode AMR calls, TFCS is limited by allowing the
downgrade of multi-mode AMR to its lowest mode. The process also shortens RRC
messages, reducing the probability of call drops during radio link reconfigurations. The
method is called Limitation of multi-mode AMR for PS DCH, which is activated with
the fifth bit of this parameter.
g Note: Modifying the AMR mode might impact speech quality.
Both methods that limit TFCS are compatible with the following multi-mode AMR
features:
• RAN580: Load Based AMR Codec Mode Selection
• RAN830: AMR Codec Sets
• RAN831: Wideband AMR Codec Set (12.65, 8.85, 6.6)
• RAN1838: Load Based HD Voice Rate

PRFILE control
Parameter values

0000H No limiting functionality is active.
0001H Limitation of PS NRT DCHs for UE TFCS capability is active.
0010H Limitation of multi-mode AMR for PS DCH is active.
0011H Limitation of PS NRT DCHs for UE TFCS capability and limitation of multi-
mode AMR for PS DCH are active.

0000H n/a
Dependences
n/a
2.73 002:1908 RN60_MAINT_32 and 002:1909

RN60_MAINT_33
Descriptive name
Workaround for RAN1231 HSPA over Iur: CS voice setup failures due to AC over Iur
interface
IPA-RNC: RN8.0, not valid for RN8.1
mcRNC: mcRNC3.0 2.0 onwards
PRFILE parameters 002:1908 RN60_MAINT_32 and 002:1909 RN60_MAINT_33
are used to control a correction for feature RAN1231: HSPA over Iur (CS voice setup
failures due to AC).
Before the correction,VCEL parameters were only used during anchoring if the HSPA
over Iur extension or RNC-HSPAoverIurExt parameter was enabled. The VCEL
parameters were controlled with the RAN1759: I-BTS Sharing feature license, which
means that the VCEL-CSAMRModeSET and VCEL-CSAMRModeSETWB parameters
could only be modified in RNW-database if the I-BTS Sharing license was enabled.
Operators were unable to configure the desired value for the parameters when the HSPA
over Iur feature license was enabled while the I-BTS Sharing feature license was
disabled.
The default value of VCEL-CSAMRModeSET and VCEL-CSAMRModeSETWB parameters
is OFF. There was no AMR codec supported over Iur by default, which resulted in AMR
setup failures during anchoring.

The workaround enables the use of AMR codec sets over the Iur interface, overriding the
values of VCEL-CSAMRModeSET and VCEL-CSAMRModeSETWB parameters. The
functionality is controlled with the following PRFILE parameters:
• 002:1908 RN60_MAINT_32
It is used for activating all the WB-AMR codec mode sets that are supported in the
RNC.
• 002:1909 RN60_MAINT_33
It is used for activating all the NB-AMR codec mode sets that are supported in the
RNC.
g Note: The general precondition is that the related AMR code set support feature is
enabled (WAMR_CODEC_SET or AMR_CODEC_SET_SUPPORT FIFILE parameters for
WB-AMR or NB-AMR, respectively.)
From RN8.1, a SW correction is provided where VCEL-CSAMRModeSET and VCEL-
CSAMRModeSETWB are modified without enabling the I-BTS Sharing license.
PRFILE control
parameter values.
Parameter values for 002:1908 RN60_MAINT_32

0000H Usage of WB-AMR codec mode sets are disabled.
0001H Usage of WB-AMR codec mode sets are enabled.

0000H n/a
Parameter values for 002:1909 RN60_MAINT_33

0000H Usage of NB-AMR codec mode sets are disabled.
0001H Usage of NB-AMR codec mode sets are enabled.

0000H n/a
Dependence
The following features are supported by AMR or WB AMR codec set:
RAN1231: HSPA over Iur
RAN1759: I-BTS Sharing

2.74 002:1912 RN60_MAINT_36

Descriptive name
SIB optimization enhancement
IPA-RNC: RN 6.0 2.1 onwards
This PRFILE parameter is used to enable the sending of the information element (IE)
Qoffset2 for an intra- and inter-frequency neighbour cell in the SIB11/11bis/12
message even when AdjsQoffset2/AdjiQoffset2 intra-frequency handover path
(HOPS) and inter-frequency handover path (HOPI) parameter of the intra- and inter-
frequency neighbour cell is set to the 3GPP default value (0 dB).
If the functionality is not active, the IE Qoffset2 is not sent in the SIB11/11bis/12
message (that is, if the corresponding radio network database parameter is set to the
3GPP default value of 0 dB).
g Note: In order to complete the activation, cell lock/unlock procedure needs to be
performed after changing the parameter value.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
2.75 002:1913 RN60_MAINT_38

Descriptive name
Higher initial code power during Inter-freq hard handover.

With this workaround active, it is possible to define the “Delta” value for the following
EcNoUE formula, which produces calculated CPICH Ec/No UE on cases, when CPICH
Ec/No value has not been reported to the RNC.
Ptx,CPICH is the code power of primary CPICH.
Ptx_total is the carrier power of the cell.
EcNoUE in producing the initial code power of the radio link to be set up.
PRFILE control
parameter values.
Parameter values

0000H Delta value is set to 4 dB as default value.
0001H - 0018H Delta value is set between 1 dB to 24 dB, with a step of one unit.

0000H 0000H - 0018H n/a
Dependence
n/a
2.76 002:1914 RN60_MAINT_39

Descriptive name
Limitation of multi-PS bearer uplink transmission in DCH configuration for RAN2262
This PRFILE parameter is used to control two functionalities:

• The first bit (LSB) of the parameter controls whether the UL TFCS limitation is done if
the number of the Turbo encoded UL PS DCHs exceeds 1.
• The fifth bit of the parameter controls whether the UL TFCS limitation is done if the
number of the Turbo encoded UL PS DCHs exceeds 2.
Both limitations also restrict the transmission in UL PS NRT DCHs so that no more than
one UL PS NRT DCHs is transferred in its TTI.
PRFILE control
parameter values.
Parameter values

0001H Value sets the limitation of UL TFCS if there is more than 1 UL PS DCs.
0010H Value sets the limitation of the UL TFCS if there is more than 2 UL PS
DCHs.

0000H n/a
Dependence
For more information, see RAN2262: Flexi Multiradio System Modules.
2.77 002:1915 RN60_MAINT_40

Descriptive name
RNC workaround for occasional long delay during plan provisioning
By modifying this PRFILE parameter, the radio network plan manager (RAY module) is
changed to address issues such as ray hand busy and reserve BTSs only for objects (or
related sub-objects), where a change in radio network (RNW) configuration is expected.
PRFILE control
parameter values.
Parameter values


0000H Functionality is activated.
0001H Functionality is deactivated.

0000H n/a
Dependence
n/a
2.78 002:1916 RN60_MAINT_41

Descriptive name
Control of LTE layering limitations
All values of hex digits xxxXH, xxXxH (except 2 and 4), xXxxH, and XxxxH
Values 2 and 4 of hex digit xxXxH
IPA-RNC: RNC17 2.0 onwards
IPA-RNC: mcRNC17 2.0 onwards
This PRFILE parameter is used to control the following:
• Whether the redirection to LTE is allowed for all user equipments or only for user
equipments that were previously redirected from LTE
• Whether the LTE bands supported by a user equipment are checked and compared
against the available LTE bands in the region before the redirection to LTE
• How the redirection to LTE is limited according to the E-UTRAN service handover
information from the Core Network
• Whether the user equipments that are placing emergency calls are redirected or
handed over to LTE
– Addresses issues when the network uses CS RAB pre-emption capability for
other than identifying emergency calls

Values
Hex Effect
digits
xxxXH 0 Redirection to LTE is allowed to all user equipments.
(default
value)
1 Blind redirection to LTE is only allowed to user equipments redirected from
LTE. There is no limitation for measurement-based redirection or handover.
3 Blind redirection, measurement-based redirection, and handover to LTE are
only allowed to user equipments redirected from LTE.
xxXxH 0 Redirection is performed only to LTE frequencies that belong to LTE bands
(default supported by the user equipment. Full LTE capabilities are used in all cases.
value)
1 LTE frequencies are not checked against LTE bands supported by the user
equipment. Full LTE capabilities are only used in LTE handover cases.
2 Starting from WCDMA17 2.0 onwards, redirection is performed only to an LTE
frequency that belongs to an LTE band that is supported by the user
equipment with the E-UTRA measurement capabilities. However, full LTE
capabilities are always used in LTE handover cases. If available, these full
capabilities are also used in other cases.
4 Starting from WCDMA17 2.0 onwards, redirection is performed only to an LTE
frequency that belongs to an LTE band that is supported by the user
equipment with the E-UTRA measurement capabilities. Full LTE capabilities
are not inquired even in LTE handover cases. However, if available the full
capabilities are used in all cases.
Note that if handover to LTE is needed but the LTE handover without full
capabilities is prevented by 002:2136 RU40_MAINT_40, or the core or LTE
network does not support the LTE handover without full capabilities, the value
should not be used because the handover to LTE will not work.
xXxxH 0 The following applies:
(default
value) • Only signaling connection is not redirected to LTE
• User equipment is not redirected to LTE if at least one of its RABs has
Handover to E-UTRAN shall not be performed in E-UTRAN
service handover IE
• Handover to E-UTRAN shall not be performed is not
remembered after the related RAB is released
1 The following applies:
• No limitation for signaling connection redirection to LTE
service handover IE
• Only signaling connection is not redirected to LTE
• User equipment is not redirected to LTE if all of its RABs have
service handover IE

Values
Hex Effect
digits

• Only signaling connection is not redirected to LTE
service handover IE
• Handover to E-UTRAN shall not be performed is
remembered after the related RAB is released, as long as RRC
connection exists and prevents redirection to LTE
• No limitation for signaling connection redirection to LTE
service handover IE
• Handover to E-UTRAN shall not be performed is
remembered after the related RAB is released, as long as RRC
connection exists and prevents redirection to LTE
XxxxH 0 Emergency calls of user equipments are not redirected or handed over to
(default LTE.
value)
1 Emergency calls, including all calls with pre-emption capability, are redirected
or handed over to LTE.
PRFILE control
parameter values.
Parameter values

0000H 0000H-1511H n/a
Dependence
• RAN2717: Smart LTE Layering
• RAN2980: Measurement based LTE Layering
• RAN2264: Smart LTE Handover

2.79 002:1918 RN60_MAINT_37

Descriptive name
Temporary offset increase for E-RGCH/E-HICH signatures
This PRFILE parameter is used to define additional offset value which is added to the
RsrvdSignaturesOffset parameter value. With additional offset, new E-RGCH/E-
HICH code is allocated earlier and released later. If RsrvdSignaturesOffset
parameter is set to value 11 (max value in RN6.0), then the PRFILE parameter value is
added to it. Maximum additional value is 7.
PRFILE control
parameter values.
Parameter values

0000H The functionality is deactivated.
0001H Value 1 is added to the RsrvdSignaturesOffset parameter value.

0000H n/a
Dependence
n/a
2.80 002:1932 RN60_INT_FEAT_RES_03

Descriptive name

Increase of HS Release due to counter pegging correction of M1002 RL failure counters
The following counter pegging faults were present in RU20:
• In RU20 when state transition to Cell_DCH with HS-DSCH/E-DCH configuration
failed because there was no synchronization indication (Radio Link Restore
Indication) was received from the base transceiver station (BTS), radio link failure
counters M1002 were not updated.
• In case of upgrades from releases prior to RU20 MP3 (the fault was corrected in
RU20 MP3) if user plane RLC made a reset error and state transition to Cell_FACH
was started to re-establish the RLC, counters M1002 were not updated.
Radio link failure counters M1002 were updated to monitor all radio link failures. In RU30
and later releases, the two counter pegging faults were corrected which led to an
increase of HS Release because of radio link (RL) failure traffic counters. However, with
the correction the counters showed the real number of radio link failures.
g Note: No end-user impact is expected. Though the change increases the number of
M1002, there is no real performance degradation. The increase in radio link failures
visible in counters M1002 is only the result of counter pegging correction.
PRFILE control
parameter values.
Parameter values

0000H PRFILE value 0000 is used to see real numbers of radio link failures.
Counters are pegged correctly in RU30 and later releases.
0001H For temporary tests, RU20 behavior can be configured.

0000H n/a
Dependences
n/a
2.81 002:1935 RN60_INT_FEAT_RES_06

Descriptive name
RANAP Interface signaling change.

IPA-RNC, mcRNC
PRFILE parameter 002:1935 RN60_INT_FEAT_RES_06 is used to control signaling
change in RNC, which is that as soon as SRNS relocation has been completed and new
U-RNTI has been successfully exchanged with the UE, RNC sends Location Report to
the CN (if Location Reporting Control was received) followed by Relocation Complete so
SGSN will have valid SAC information available early enough.
PRFILE control
parameter values.
Parameter values

0000H Signaling change is not active.
0010H The signaling change is active.

0000H n/a
Dependence
n/a
2.82 002:1939 RN60_INT_FEAT_RES_10

Descriptive name
H-RNTI allocation algorithm change.
IPA-RNC, mcRNC
With this PRFILE it is possible to select whether BTS level or cell level H-RNTI (high-
speed downlink shared channel radio network identifier) pool is to be used by the RNC.
PRFILE control
parameter values.
Parameter values


0000H Cell level H-RNTI pool is used.
0001H BTS level H-RNTI pool is used.

0000H n/a
Dependence
n/a
2.83 002:1950 CPC_DL_DRX_RESTRICTED

Descriptive name
Workarounds for F-DPCH failure with some Rel. 7 UEs
IPA-RNC: onwards
mcRNC: onwards
The change addresses issues found in live networks when fractional DPCH (F-DPCH) is
activated with CPC.
The CPC Discontinuous DL Reception (DL DRX) functionality has high correlation with
CPC retainability problems. Some user equipments are more sensitive to the values
used in DL DRX parametrization, thus experience an increase in call drops when the
values are modified. Since DL DRX behavior might not be the same for different
networks, a workaround is implemented to deactivate DL DRX functionality to decrease
the retainability problems with CPC when it is in use.
The following are the CPC functionalities:
• DPCCH Gating (UL DTX)
• CQI Reporting reduction
• Discontinuous UL Reception (MAC DTX)
• Discontinuous DL Reception (DL DRX)
The DL DRX restriction functionality is controlled with this PRFILE parameter. The
parameter enables the restriction of DL DRX when:
• first bit (bit 0) applies to the configuration using E-TTI = 2 ms
• fifth bit (bit 4) applies to the configuration using E-TTI = 10 ms
When the DL DRX restriction is enabled and the UE has a scheduled transmission (ST)
RB, RNC does not activate the UE DRX functionality although CPC is enabled. The
method makes it possible to send RRC messages in DL without any extra delay and
effect to UL interference, with only a minimal increase in UE battery consumption.

PRFILE control
parameter values.
Parameter values

0011H DL DRX restriction for E-TTI = 10 ms and E-TTI = 2 ms
0010H DL DRX restriction for E-TTI = 10 ms
0001H DL DRX restriction for E-TTI = 2 ms
0000H No DL DRX restrictions

0000H n/a
Dependence
This parameter depends on Release 7 and newer UE models supporting CPC. It also
depends on RAN1201: Fractional DPCH feature.
2.84 002:2066 MIN_RE_EDPDCH_GF_TO_BTS

Descriptive name
Minimum reduced E-DPDCH gain factor
PRFILE control
parameter values.
Parameter values

0000H The functionality is deactivated.
0001H The RNC sends the same value as what the user equipment (UE) sends
to base transceiver station (BTS) in Minimum Reduced E-DPDCH Gain
Factor IE.
0002H The serving radio network controller (SRNC) sends the same value as
what the UE sends over Iur to drift radio network controller (DRNC) in
Minimum Reduced E-DPDCH Gain Factor IE.


0003H Both above functionalities are active. If the DRNC receives Minimum
Reduced E-DPDCH Gain Factor IE from the SRNC, it sends it to the BTS.

0000H n/a
Dependence
n/a
2.85 002:2095 RU40_MAINT_01

Descriptive name
RNC recovery correction to avoid unnecessary SAB block and unblocking in case of
missing HSPA or HSDPA power measurements
This PRFILE is used to control the RNC recovery correction to avoid unnecessary SAB
block and unblocking in case of missing high-speed packet access (HSPA) or high-
speed downlink packet access (HSDPA) power measurements.
PRFILE control
parameter values.
Parameter values

0000H RNC recovery correction is not used.
0001H RNC recovery correction is used.

0000H n/a
Dependence
n/a

2.86 002:2098 RU40_MAINT_02

Descriptive name
HSPA allocation problem with RAN 2494 Fast Cell PCH switching and Direct DCH to
PCH transition for release 99 users
IPA-RNC:
• HSPA allocation problem with RAN 2494 Fast Cell PCH switching from RN7.0 1.0
onwards
• Direct DCH to PCH transition for release 99 users from RN7.0 onwards
mcRNC: from mcRNC3.0 onwards
HSPA allocation problem with RAN 2494 Fast Cell PCH switching
When RAN2494 Fast Cell PCH switch feature is enabled, certain specific UEs cannot
handle state transition from Cell_FACH to Cell_DCH if RRC message commanding state
transition to Cell_DCH does not include full E-DCH transport channel information for
each Radio Bearer. After UE rejects the state transition command, RNC assumes the UE
does not support HSPA configuration and does not allocate HSPA to the UE anymore.
This impacts the HSUPA Setup Success Ratio KPIs.
A workaround has been made in the RNC so that even in cases when RAN2494 is
enabled and the RNC is aware that UL E-DCH transport channel information has not
changed, RNC will continue to provide the UE with information in the state transition
command to Cell_DCH. The workaround is controlled via PRFILE Parameter 002:2098
RU40_MAINT_02 and not active by default.
g Note: This problem is not expected to have much impact in live networks as new UE
models already include corrections for this problem. This is the reason why the
workaround is by default deactivated. For further instructions, as well as the list of
possible values, see TS-RNC-SW-149.
Direct DCH to PCH transition for Release 99 users

In RU30, Direct DCH to PCH transition for HS users was controlled with PRFILE
parameter 007:0307 RN40_MAINT_037. In RU40, this functionality is controlled
through Management parameter DCHtoPCHEnabled. When detecting the inactivity of
HSDPA or HSPA users, the RNC moved those directly from Cell_DCH to Cell_PCH.
Contrary to RU30, in RU40 this functionality is also applied to Release 99 users in order
to reduce NW signaling, resource usage and UE battery drainage.
It is possible to fall back to RU30 functionality by modifying the first bit of PRFILE
Parameter 002:2098 RU40_MAINT_02. This means that when both Management
parameter DCHtoPCHEnabled and PRFILE Parameter 002:2098 RU40_MAINT_02
are set to its activate values, direct DCH to PCH transitions will only affect HS users. By
default this functionality is inactive.
PRFILE control

parameter values.
Parameter values
Functionality 1st bit 5th bit 6th bit 7th bit

Direct DCH to PCH transition for release 99 X
users
RNC workarounds for release 6 UE problems X

0000H n/a
Dependence
n/a
2.87 002:2099 RU40_MAINT_03

Descriptive name
PS RAB release guard timer
This PRFILE parameter defines the guard timer, on how soon the RNC sends RAB
Release Request to serving GPRS support node (SGSN) after receiving GTP error
indication from PS-CN . When the timer expires and the RAB Release Request is sent,
failure counters in measurements M1001 and M1022 are updated. If the SGSN releases
the RAB before the timer expires in the RNC, it is counted as a normal PS RAB release.
The unit of the parameter is milliseconds. The default value of zero means that the guard
timer of 1,000 ms is used. The maximum supported time is 2,000 ms (any higher value is
interpreted as 2,000 ms). Increase of the guard timer might be necessary in some
network configurations where the interaction between SGSN and gateway GPRS
support node (GGSN) causes the GTP tunnel to be released in the core network side, so
that the release command to the RNC is sent more than 1,000 ms later.
PRFILE control
parameter values.
Parameter values


0000H - 03E8H The guard timer is set between 1,000 ms and 2,000 ms.
03E8H - FF00H The guard timer is kept at the maximum value of 2,000 ms.

0000H n/a
Dependence
n/a
2.88 002:2100 RU40_MAINT_04

Descriptive name
Transfer mode for the periodical intrafrequency CPICH Ec/No measurement
RNC RN7.0 onwards
This parameter defines the transfer mode of the Measurement Reporting Mode for the
periodical intrafrequency CPICH Ec/No measurement. The RNC uses the measurement,
as a part of high-speed downlink packet access (HSDPA), for transport channel type
selection and for the decision of the HSDPA serving cell changes. Acknowledged mode
RLC is used by default as the transfer mode, which means that the AM SRB2 is used for
reporting.
Periodic reporting on AM SRB2 results to the performance problems of the SRB2. RRC
messages received from the user equipment (UE), on top of other measurement reports,
are delayed for the AM RLC retransmissions because the AM RLC receiver delivers the
received messages in sequence to L3. Each measurement report generates an RLC
status report in DL. The status reports are prioritized over the AM SRB2 data PDUs,
which increases the latency in the DL RRC signaling and the dropping probability in the
synchronized RRC procedures. The UE also performs several event-based
measurements reported on AM SRB2 (contributing continually to the signaling load of
AM SRB2).
UM RLC is sufficient for the periodic measurement reporting (assured transmission is not
needed). Additionally, missing report is replaced with the next received periodic report.
This parameter is used for changing the transfer mode to Unacknowledged mode RLC.
Reporting happens then on UM SRB1.
PRFILE control
parameter values.
Parameter values


0000H Acknowledged mode RLC.
0001H Unacknowledged mode RLC.
g Note: The change is implemented within 10 minutes after the parameter value is
changed.

0000H n/a
Dependences
n/a
2.89 002:2101 RU40_MAINT_05

Descriptive name
Control of Automatic Access Class Restriction information sending in SIB3
This PRFILE parameter is used to control the access restriction information in RAN2480:
Automatic Access Class Restriction, as follows:
• The first bit value 0 means that the access class barred list for Release 5 and older
user equipments is not included in SIB3 with Core Network (CN) and RNC overload-
triggered AACR. Value 1 means that the access class barred list for Release 5 and
older user equipments is included in SIB3 with CN and RNC overload triggered
AACR.
• The second bit value 0 means that the CS domain-specific access class restriction
list is included in SIB3 with RNC overload-triggered AACR. Value 1 means that the
CS domain-specific access class restriction list is excluded from SIB3 with RNC
overload-triggered AACR.
• The third bit value 0 means that the PS domain-specific access class restriction list is
included in SIB3 with RNC overload-triggered AACR. Value 1 means that the PS
domain-specific access class restriction list is excluded from SIB3 with RNC
overload-triggered AACR.
For more information, see RAN2480: Automatic Access Class Restriction in RU40

Feature Descriptions and Instructions.
PRFILE control
parameter values.
Parameter values


0000H 0000H-0007H n/a
Dependence
For more information, see RAN2480: Automatic Access Class Restriction.
2.90 002:2102 RU40_MAINT_06

Descriptive name
The algorithm for logical channel ID and DDI allocation
A workaround is implemented to NSN RU40 RNC, where it is possible to fall back into
the RU30 logical channel ID and DDI allocation algorithm. The functionality is controlled
by this PRFILE parameter.
PRFILE control
parameter values.
Parameter values

0000H The workaround is disabled, RU40 algorithm is user.
0001H The workaround is enabled, RU30 algorithm is user.

0000H n/a
Dependence
n/a
2.91 002:2103 RU40_MAINT_07

Descriptive name
Dynamic HSUPA BLER

This PRFILE parameter is used to control used block error ratio (BLER) values of
continuous BLER state of the Dynamic HSUPA BLER functionality. For more information,
see RAN2302: Dynamic HSUPA BLER in RU40 Feature Descriptions and Instructions.
The following are controlled by this PRFILE parameter:
• The value of the first bit controls the dynamic power offset algorithm whether it
affects the Dynamic HSUPA BLER functionality.
• The values of second to seventh bits indicate the high-speed uplink packet access
(HSUPA) user equipment (UE) threshold within the cell, where the Dynamic HSUPA
BLER functionality is active. The threshold value is set from 0 to 127.
Dynamic HSUPA algorithm BLER parameters are used when either:
• The first bit of this PRFILE parameter is set to 0 and the number of HSUPA users in
the cell is equal or higher than the threshold defined in the second to seventh bits of
this PRFILE parameter.
• The first bit of this PRFILE parameter is set to 1 and the dynamic power offset
algorithm allocates low power offsets/low initial SIR target (also in case of E-DPDCH
interpolation method) for the UE.
Otherwise, Continuous BLER state OLPC is configured with its corresponding
parameters:
• L1BLERTargetEDCH
• DynHSUPABLERContDataRx2
• DynHSUPABLERContDataRx10
PRFILE control
parameter values.
Parameter values
Recommended Effect
value(s)
0006H The dynamic power offset algorithm is disabled and the cell HSUPA UE
threshold is 3.

0000H 0000H-00FFH n/a
Dependence
For more information, see RAN2302: Dynamic HSUPA BLER.

2.92 002:2105 RU40_MAINT_09

Descriptive name
IFHO/ISHO can fail due to incorrect UE behavior
IPA-RNC: RN7.0 1.0onwards
After the state transition to CELL_FACH is cancelled, conflicting compressed mode
information exist inside RNC and between RNC and base transceiver station (BTS). The
issue is visible to end user that if compressed mode and new interfrequency or
intersystem measurement are not started, calls are not handed over to another
frequency or radio access technology (RAT).
When the state transition from CELL_DCH to CELL_FACH is made, ongoing
interfrequency or intersystem measurement is stopped because of user equipment (UE)
that behaves incorrectly. However, the situation does not stop the measurements from
moving to CELL_FACH state. When the state transition is completed, measurement-
related compressed mode information is cleared from RNC and BTS. On the other hand,
if the state transition is cancelled (for example, because of UE activity) the compressed
mode information is left hanging in RNC and BTS though corresponding measurement is
stopped. If a new interfrequency or intersystem measurement is started, a conflicting
situation arises after the state transition is cancelled and the compressed mode is
prepared for the measurement.
The improved functionality allows for measurement to not be released for UEs newer
than Release 6, since the UEs are able to stop the measurement from moving to
CELL_FACH state. For older UEs, measurement is always released while Layer 3
ensures that the state transition is not cancelled. The workaround functionality is
controlled by this PRFILE parameter. The new functionality is disabled by default.
PRFILE control
parameter values.
Parameter values

0000H When the RNC identifies the need for ongoing compressed mode and
interfrequency or intersystem measurement release because of state
transition from CELL_DCH to CELL_FACH, UE release is not taken into
account. When assessing the cancellation of state transition to
CELL_FACH state, UE release is not taken into account either.
0001H For Release 6 or older UEs, ongoing interfrequency or intersystem
measurement is always released when CELL_FACH state transition is
indicated. If compressed mode is ongoing, CELL_FACH state transition
for the same UEs is also not cancelled.


0000H n/a
Dependence
n/a
2.93 002:2107 RU40_MAINT_11

Descriptive name
Activation/deactivation of LCG and BTS level HSDPA user amount check against LCG
and BTS specific limits sent by BTS
This PRFILE parameter is used to deactivate the local cell group (LCG) and base
transceiver station (BTS)-level high-speed downlink packet access (HSDPA) user
amount check against LCG and BTS-specific limits that are sent by the BTS, in
scenarios where the limitations are not working properly.
Originally, RNC limited the HSDPA user amount depending on HSDPA capacity features
used, Radio Network parameters, and HSDPA capacity received from the BTS (cell- and
HSDPA scheduler-specific limits for HSDPA user and HS-DSCH MAC-d flow amounts).
The checks were made in the admission control phase.
The new functionality also allows the BTS to indicate its maximum LCG- and BTS-
specific HSDPA user amounts to the RNC. The RNC does not allow more HSDPA users
than the limit indicates.
PRFILE control
parameter values.
Parameter values

0000H LCG- and BTS-specific HSDPA user amount check against limits that are
sent by BTS is active.
0001H LCG- and BTS-specific HSDPA user amount check against limits that are
sent by BTS is not active.

0000H n/a

Dependence
RAN2124: HSPA 128 Users per Cell
2.94 002:2109 RU40_MAINT_13

Descriptive name
This PRFILE parameter controls the following:
• maximum number of radio link (RL) in RNSAP Radio Link Setup/Addition procedure
• initial DL power calculation when MBLB layering takes place during Fast Call Setup
Maximum number of RLs in RNSAP Radio Link Setup/Addition procedure:
Initial DL power calculation when MBLB layering takes place during Fast Call Setup
Maximum number of RLs in RNSAP Radio Link Setup/Addition procedure
The length of the RNSAP: Radio Link Setup/Addition Response message
depends on the number of requested RLs (cells) and the number of neighboring cells
defined for the requested cells in the drift radio network controller (DRNC) side. If the
number of neighboring cells is high and two RLs are required in DRNC, the RNSAP:
Radio Link Setup/Addition Response message might become very long that
the signaling connection control part (SCCP) might not be able to handle the message,
which might cause SRNC to send Error Indication. The maximum length of the SCCP
message is 32 segments (32 * 255 = 8160 bytes) starting from RU50 onwards.
If the maximum length of RANAP Radio Link Setup/Addition Response message
is reached because of the high number of neighboring cells (for example, when multiple
RLs are used for DRNC), problems occur in RL setup over Iur interface, which is visible
to operator because of increase of the counter M1004C168 (SHO BRANCH SETUP
FAIL DUE TO IUR).
This PRFILE parameter controls the maximum number of RLs in the RNSAP Radio Link
Setup/Addition procedure when the number of neighbor cells is high, which eliminates
very long RNSAP: Radio Link Setup/Addition Response messages.
If the value of the first bit in the PRFILE parameter is 0 (default value), serving radio
network controller (SRNC) and DRNC do not limit the number of RLs. If the value of the
first bit in the PRFILE parameter is 1, SRNC limits the number of RLs in RNSAP:
Radio Link Setup/Addition Request message to one. With the same value of
1, the DRNC limits the number of RLs in RNSAP: Radio Link Setup/Addition
Response message to also one.

It is recommended to limit the number of RLs to one RL in the RNSAP Radio Link
Setup/Addition procedure if the number of neighbor cells exceeds about 130 cells. The
following formula also take into account the type of the adjacency: (22 + 29 * X) + (22 +
15 * Y) + (7 + 11 * G) + (6 + 27 * E) + 129 < 8160 bytes, where:
• X is the number of intra- and inter-frequency neighbor cells controlled by the DRNC
in question (DRNC equals to CRNC).
• Y is the number of intra- and inter-frequency neighbor cells whose CRNC is other
than the DRNC in question.
• G is the number of GSM neighbor cells.
• E is the number of E-UTRA (LTE) neighbor cells.
Initial DL power calculation when MBLB layering takes place during Fast Call
Setup
In case of layering in state transition to Cell_DCH state (MBLB), there are no
measurement results available from the target cell so the decision criteria is based on
the CPICH RSCP measurement result of the source cell. The CPICH RSCP
measurement result of the source cell is used as the decision criteria in the target cell for
the following:
• determination of the initial downlink power of a radio link
• allocation of F-DPCH in RRC connection setup phase and RRC connection
establishment with standalone SRBs on high-speed packet access (HSPA)
• selection of the UL E-TTI to be used for E-DCH
However, in case of Fast Call Setup from Cell_PCH state because of downlink data
activity (and because of any other network-initiated reason), radio resources are
allocated in the target cell before the CPICH RSCP measurement result of the source
cell is received from the user equipment (UE) within the RRC: CELL UPDATE
message.
This PRFILE parameter is required to define whether the value of the WCEL
CUCRSCPThreshold parameter or an old CPICH RSCP measurement result of the
source cell, which is received from the UE before the state transition from Cell_PCH
state, is used in the decision criteria in the target cell when MBLB layering takes place
during state transition from Cell_PCH state because of downlink data activity.
If the fifth bit of this PRFILE parameter is set to value 0 (default value), an old CPICH
RSCP measurement result of the source cell that is received from the UE before the
state transition from Cell_PCH state is used in the decision criteria in the target cell. If
the fifth bit of this PRFILE parameter is set to value 1, the value of the WCEL
CUCRSCPThreshold parameter of the source cell is used instead of the old CPICH
RSCP measurement result in the decision criteria in the target cell.
The preferred value for the fifth bit of this PRFILE parameter is 1.
PRFILE control
parameter values.
Parameter values


0000H There is no limitation on the maximum number of RLs in the RNSAP
Radio Link Setup/Addition procedure. An old CPICH RSCP measurement
result of the source cell is used in the decision criteria in the target cell.
0001H The maximum number of RLs in the RNSAP Radio Link Setup/Addition
procedure is limited to one. An old CPICH RSCP measurement result of
the source cell is used in the decision criteria in the target cell.
0010H There is no limitation on the maximum number of RLs in the RNSAP
Radio Link Setup/Addition procedure. The value of the
CUCRSCPThreshold parameter is used in the decision criteria in the
target cell. The functionality is activated in RNC16 4.0 and mcRNC16 4.0
onwards.
0011H The maximum number of RLs in the RNSAP Radio Link Setup/Addition
procedure is limited to one. Value of the CUCRSCPThreshold parameter
is used in the decision criteria in the target cell. The functionality is
activated in RNC16 4.0 and mcRNC16 4.0 onwards.

0000H n/a
Dependence
The following are the related features:
• RAN2172: Multi-Band Load Balancing
• RAN1232: Fast Call Setup from Cell_PCH State
2.95 002:2110 RU40_MAINT_14

Descriptive name
Control for the Bursty BLER target value for a new E-DCH allocation in case number of
HSUPA UEs are above the threshold value
PRFILE parameter 002:2110 RU40_MAINT_14 controls the Bursty BLER target
value for a new E-DCH allocation in case number of HSUPA UEs are above the
threshold value.
Value of the 1 st bit of the parameter controls the activation/deactivation of correction to
set Bursty BLER target value.
• Value 0 of the 1st bit of the parameter means that the functionality is off. There is no
special handling for configuring Bursty BLER target value.

• Value 1 of the 1st bit of the parameter means that the Continuous BLER target value
is configured for Bursty BLER target value in case number of HSUPA UEs is above
the threshold value defined by the values of the 2nd to 8th bits of the parameter.
The values of bits 2nd to 8th define the threshold for HSUPA UEs in a cell. If the threshold
is exceeded, values of Continuous BLER state parameters are configured for bursty
BLER state-related information elements signalled to u-plane. The threshold value can
be set from 0 to 127.
The default value of PRFILE parameter RU40_MAINT_14 (002:2110) is 0,
indicating that there is no special handling for configuring Bursty BLER target value.
The recommended value for the PRFILE parameter RU40_MAINT_14 (002:2110) is
47H, which sets the HSUPA UEs cell threshold to 35.
PRFILE control
parameter values.
Parameter values
Recommended Effect
value(s)
0047H Continuous BLER target value is configured for Bursty BLER target value
in case the number of HSUPA UEs is higher than 35.

0000H 0000H - 00FFH n/a
Dependence
n/a
2.96 002:2111 RU40_MAINT_15

Descriptive name
Scaling of RSCP measurement result in blind IFHO between frequency bands
The current implementation of the RAN2172: Multi-Band Load Balancing (MBLB) feature
does not take into account that path loss and RSCP are proportional to the frequency of
the radio signal. In case of bands I (2100 MHz) and VIII (900 MHz), for example, the
difference is about 7 dB.

In case of Blind IFHO in RAB setup phase (MBLB), Layering in state transition to
Cell_DCH state (MBLB) as well as in case of Directed RRC connection setup, Directed
RRC connection setup for HSDPA layer, and HSDPA layering for UEs in common
channels, this may cause a significant defect when the measurement result of the source
cell is used in the target cell after a blind IFHO, Layering or DRRC if the blind IFHO,
Layering or DRRC has taken place between different frequency bands. The
measurement result of the source cell is used in the decision criteria in the target cell for
the following:
• determining the initial downlink power of radio link
• allocating F-DPCH in RRC connection setup phase and establishing RRC
connection with standalone SRBs on HSPA
• selecting the UL TTI to be used for E-DCH
If the value of this PRFILE parameter is 0 (default value), the CPICH RSCP
measurement result of the source cell is not scaled before it is used in the decision
criteria in the target cell even if blind IFHO, layering or DRRC takes place between
frequency bands.
If the value of the PRFILE parameter is 1, the CPICH RSCP measurement result of the
source cell is scaled before it is used in the decision criteria in the target cell if Directed
RRC connection setup, Directed RRC connection setup for HSDPA layer, HSDPA
layering for UEs in common channels, Blind IFHO in RAB setup phase (MBLB) or
Layering in state transition to Cell_DCH state (MBLB) takes place between frequency
bands.
The preferred value of the PRFILE parameter 002:2111 RU40_MAINT_15 is 1.
Scaling of RSCP measurement result improves the accuracy of CPICH RSCP value,
providing better control for the above mentioned functionalities in blind IFHO between
frequency bands.
The activation status of the PRFILE parameter is checked with the following MML
command:
Table 4 MML commands for checking the activation status of 002:2111
RU40_MAINT_15
Command Description
ZWOI:2,2111; The scaling of RSCP measurement result is
activated in blind IFHO between frequency
bands by setting the 1st bit (Bit0) of the PRFILE
parameter to value 1 with the following MML
command: ZWOC:2,2111,1;
ZWOC:2,2111,1; The scaling of RSCP measurement result is
deactivated in blind IFHO between frequency
bands by setting the 1st bit (Bit0) of the PRFILE
parameter to value 0 with the following MML
command:ZWOC:2,2111,0;
PRFILE control
parameter values.
Parameter values


0000H The functionality is not activated.
0001H Source cell CPICH RSCP measurement results are scaled before their
use as decision criteria.

0000H n/a
Dependence
RAN2172: Multi-Band Load Balancing
2.97 002:2112 RU40_MAINT_16

Descriptive name
E-UTRA frequency ordering
RNC RN8.1 onwards
Operators have asked a clear way to manage the order of LTE frequencies that are
given to a user equipment (UE) in the redirection procedure and are broadcasted in
SIB19 for cell reselection. RAN2980: Measurement based LTE layering feature
introduces the possibility to prioritize LTE frequencies for redirection, but that is at
present enhanced with a secondary prioritization. LTE frequency prioritization in SIB19 is
a new functionality.
The change in the redirection functionality provides that if several LTE frequencies have
the same priority value set with the HOPL- AdjLFreqPriority parameter, then
those frequencies can be prioritized according to the values of the ADJL-ADJLId
parameter. This secondary prioritization can be activated or deactivated with the 1st bit of
002:2112 RU40_MAINT_16 PRFILE parameter.
On the other hand, the change in the SIB19 handling provides that LTE frequencies
broadcast with SIB19 are put to SIB19 primarily according to the HOPL-
AdjLAbsPrioCellReselec values and secondarily according to the ADJL-ADJLId
values. This prioritization can be activated or deactivated with the 5th bit of 002:2112
RU40_MAINT_16 PRFILE parameter.
The new functionalities are used to optimize LTE frequency selection made by the UE so
that an operator can set the order of the frequencies given to the UEs. The functionalities
also help to control possible defects when the UEs handle LTE frequencies.
002:2112 RU40_MAINT_16 PRFILE parameter controls if:
• the LTE frequencies with the same HOPL- AdjLFreqPriority value given to the
UE for redirection are in the priority order defined by the ADJL-ADJLId parameter.

The order defined with the HOPL- AdjLFreqPriority values is used anyway,
but the PRFILE parameter controls if the secondary prioritization is based on ADJL-
ADJLId parameter.
• the LTE frequencies put to SIB19 for cell reselection are in the priority order defined
by the HOPL- AdjLAbsPrioCellReselec and the ADJL-ADJLId parameters.
PRFILE control
Parameter values

0000H Secondary prioritization is not in use for redirection. Frequencies for cell
reselection in SIB19 are not given in the priority order.
0001H Secondary prioritization is in use for redirection. Frequencies for cell
reselection in SIB19 are not given in the priority order.
0010H Secondary prioritization is not in use for redirection. Frequencies for cell
reselection in SIB19 are given in the priority order.
0011H Secondary prioritization is in use for redirection. Frequencies for cell
reselection in SIB19 are given in the priority order.

0000H n/a
Dependences
RAN3088: E-UTRA Frequency Ordering
2.98 002:2113 RU40_MAINT_17

Descriptive name
DRNC handling of E-DCH SF4, SF8, and all inferior SFs Support Indicators in Cell
Capability Container when cell supports HSUPA
DRNC sends the Cell Capability Container of the target cell and its neighbor cells
attached to the RADIO LINK SETUP/ADDITION RESPONSE messages that indicate the
RRM capabilities of the target and neighboring cells.
PRFILE parameter 002:2113 RU40_MAINT_17 controls the use of the eleventh and
twelfth bits of the Cell Capability Container.

If the PRFILE functionality is activated and DRNC sets the Cell Capability Container E-
DCH Support Indicator “Supported”, then DRNC also sets the 11th bit: E-DCH SF 4 and
all inferior SF support Indicators to “Supported” and 12th bit: E-DCH SF8 and all inferior
SF Support Indicators to “Supported”. Otherwise these 11th and 12th bits are kept at
value 0.
PRFILE control
parameter values.
Parameter values

0001H The functionality is active. DRNC sets the SF4, SF8 and all inferior SF
Support Indicators to value 1 (“Supported”) in the Cell Capability
Container.

0000H n/a
Dependence
n/a
2.99 002:2115 RU40_MAINT_19

Descriptive name
HS-DPCCH ACK/NACK power offset parameter control to prevent call drops with F-
DPCH and degradation of MAC-HS efficiency/HSDPA throughput generally with E-DCH
configuration
This new functionality is implemented to prevent F-DPCH call drops due to SCC failures.
Historically HS-DPCCH ACK power offset and NACK power offset use fixed amplitude
ratio values 15/15 or 24/15, depending on the soft HO state of the E-DPDCH UE. The
amplitude ratio of HS-DPCCH is relative to the amplitude ratio of DPCCH when
ACK/NACK is sent on HS-DPCCH.

Fast mobility UEs in soft HO state have suffered F-PDCH call drops caused by
challenging air conditions. These call drops are the result of failing Serving Cell Change
(SCC). To increase the SCC success rate in F-DPCH configuration, it is needed to
increase power when sending “Amplitude Ratio of ACK” and “Amplitude Ratio of NACK”
from UE to BTS so that the BTS is able to correctly decode the information.
Too low ACK/NACK power offsets may result in UE reconfiguration, which increases the
retransmission of data in DL and causes delays for RRC messages. When the BTS is
not able to decode information, it makes blind repetition to UE. This can cause essential
delay in RRC messages sent in DL over HS-DSCH. Therefore, it is critical to secure DL
signaling data (SRB) with F-DPCH, as there is only one branch where the DL SRB
information is signaled to UE.
Degradation of MAC HS efficiency KPIs is also observed when any of the following
functionalities are used:
• Dynamic HSUPA Power Offsets feature
• Dynamic HSUPA BLER feature
• Basic PIC
• Enhanced PIC
• IRC functionalities in generally applied with E-DCH UL transport channel
This is because both features are meant to decrease the interference level to achieve
more room for data transmission. Lower DPCCH power is used in both low bit rate
optimized HSUPA POs and when the high BLER condition is effective. If the UE is
located on the edge of cell in such a situation, the BTS may have problems in correctly
decoding information.
To avoid unnecessary stuck/retransmission of DL data in BTS over HS-DSCH, a PRFILE
controllable solution has been introduced to enable setting the ACK and NACK power
offsets to the following values: 15/15, 19/15, 24/15 or 30/15. The values are selected
with PRFILE parameter 002:2115 RU40_MAINT_19.
The default value of the parameter is 0, meaning that the new functionality is disabled. In
this scenario power offset will be based on the UE soft HO state.
When the PRFILE parameter is configured within the 5H to 8H range and E-DCH is
present, ACK and NACK power offsets are read from the PRFILE. Values outside of the
5H-8H range have no effect and in those situations power offset will be based on the UE
soft HO state.
g Note: The value defined by the PRFILE parameter is used regardless of handover
state (soft HO or non-soft HO).
PRFILE control
parameter values.
Parameter values

0000H The functionality is disabled
0005H 15/15 PO for ACK and NACK with E_DCH


Default value Recommended value(s) Forbidden value(s)

0000H 0007H n/a
Dependence
n/a
2.100 002:2117 RU40_MAINT_21

Descriptive name
PRFILE control for setting maximum E-DCH bit rate signaled towards BTS
Live network experiences and test results have shown that limiting of the enhanced
dedicated transport channel (E-DCH) bit rate makes connection more stable when high
bit rates are used (around 4 Mbit/s). Fast variation of E-TFCI causes high block error
ratio (BLER) rate with the highest size of transport blocks (TB). A better average
throughput of the call can be therefore achieved with the stable use of E-TFCIs.
The current parametrization has been too complicated to set the maximum E-DCH bit
rate based on the RAB maximum bit rate received from the core network (CN),
especially when the used RAB maximum bit rate values differed from each other.
A new 002:2117 RU40_MAINT_21 PRFILE parameter has been introduced to allow
the operator to set the maximum E-DCH 1st bit rate signaled towards the base
transceiver station (BTS). Thus, a new E-DCH maximum bit rate calculation is applied to
HSUPA 2 ms connections using maximum uplink total symbol rate 2*SF2 +2*SF4. It is
information that is signaled only towards BTS within NBAP: E-DCH Maximum Bitrate IE.
The 002:2117 RU40_MAINT_21 PRFILE parameter can be used to define the
signaled E-DCH maximum bit rate when E-DCH allocations for NRT RABs exist with
2*SF2+2*SF4, irrespective of the SRB configuration used (SRB can be mapped either to
E-DCH/DCH or E-DCH/HS-DSCH).
If the 002:2117 RU40_MAINT_21 PRFILE PRFILE parameter value is 0H (the default
value), the existing method is used where user equipment (UE)-specific packet
scheduler defines E-DCH maximum bit rate based on the maximum uplink user bit rate
of the RAB (for more information, see HSUPA FAD).

If the value defined by the 002:2117 RU40_MAINT_21 PRFILE parameter with bits
from 1st to 5th is different than 0, E-DCH maximum bit rate is calculated and signaled to
BTS in the following manner:
EDCHMaxBitRate = 2600 kbps + 100 kbps * PRFILEMultiplier,
where PRFILEMultiplier value is defined using the 002:2117 RU40_MAINT_21
PRFILE parameter as follows:
Table 5 PRFILEMultiplier values
Binary Decimal
xxxx xxxx xxx0 0000 not used
xxxx xxxx xxx0 0001 1
... ...
xxxx xxxx xxx1 1111 31
It means that the range defined for E-DCH with 2*SF2+2*SF4 and E-TTI=2 ms but
without 16QAM configuration is from 2700 kbit/s up to 5700 kbit/s in 100 kbit/s steps.
Based on the field tests, the recommended or optimal value for E-DCH maximum bit rate
is 5000 kbit/s. It can be defined by setting the 002:2117 RU40_MAINT_21 PRFILE
parameter to value 0x18H (24 dec => 2600 kbit/s + 100 kbit/s * 24 = 5000 kbit/s).
002:2117 RU40_MAINT_21 PRFILE parameter bits from 1 st to 5th are used to define
multiplier (PRFILEMultiplier) for the E-DCHMaxBitRate calculation.
Default value 0H means that the existing way is used to define E-DCH maximum bit rate
and the equation is not used. Other values than 0H are used in the equation as follows:
Table 6 Other values
Binary Hex Decimal
xxxx xxxx xxx0 0001 0001H 1
... ... ...
xxxx xxxx xxx1 1111 001FH 31
g Note: The value defined by the 002:2117 RU40_MAINT_21 PRFILE parameter with

bits from 1st to 5th is used in configuration E-TTI=2 ms and uplink total symbol rate set
2*SF2+2*SF4, if 16QAM has not been configured.
The recommended values for 002:2117 RU40_MAINT_21 PRFILE parameter and
the HSUPA 16QAM issues are presented in Technical Support Note TS-RNC-SW-228
recommended parameter set for optimizing radio resource manager (RRM)
functionalities.
PRFILE control
Parameter values

Recommended Effect
value(s)
0000H The standard E-DCH bit rate control functionality remains unchanged.
0018H This sets the maximum E-DCH bit rate to 5000 kbit/s.

0000H 0000H-001FH n/a
Dependences
n/a
2.101 002:2119 RU40_MAINT_23

Descriptive name
No recovery mechanism in RNC for voice quality problems caused by ciphering
desynchronization
IFHO workaround
IPA-RNC: RN7.0 4.1, RN7.0 5.0, RN8.0 1.0 onwards
mcRNC: mcRNC3.0 3.0, mcRNC4.1 onwards
AMR workaround
IPA-RNC: RN7.0 5.0, RN8.1 1.0 onwards
mcRNC: mcRNC3.0 4.0, MCRNC4.1 1.0 onwards
Counters M1006C333 and M1006C334

mcRNC: mcRNC17 2.0 onwards
g Note: It is advised to contact customer support in case this improvement is planned to
be activated in live networks.
When reconfiguring TM RLC ciphering, the UMTS terrestrial radio access network
(UTRAN) needs to consider the activation time and START value received from the user
equipment (UE) in the uplink (UL) response message. If the UL message is received too
late, the UE might increment the hyperframe number (HFN) and the new ciphering might
apply too late. Instances when ciphering goes out of sync are visible in network logs,
however recovery mechanism is needed in the RND for the resulting garbled voice
during RRC connection. Meanwhile, the garbled voice is only addressed when the user
disconnects the call or when another procedure requires ciphering reconfiguration.
RNC is improved to recover garbled voice calls caused by out-of-sync ciphering during
IFHO procedure. When IFHO commands are sent, a 3-second timer is started. If the
handover complete message is not received within 3 seconds, the cipher activation time

is assumed late and the local state change to DCH is made. RNC releases the radio
links and waits for the cell update from the UE to perform call re-establishment, during
which the ciphering is also re-initialized. Once the UE sends the cell update, the voice
call is re-established with re-initialized ciphering for TM RLCs.
RNC is further enhanced to cover out-of-sync ciphering during adaptive multirate (AMR)
setup. Garbled voice occurs in AMR (or CS-NT, CS-T RAB) setup when the response of
the UE to the radio bearer setup message arrives later than its TM ciphering activation
time. The improvement in the AMR causes re-establishment if the acknowledgment of
the UE to the radio bearer setup message takes more than 3 seconds to arrive. In this
case, the radio links are released and the UE is forced to make a cell update. The
ciphering is reconfigured when the call is re-established to the DCH state.
The following counters are updated with this PRFILE parameter:
• Counter M1006C333 is used to measure the number of ciphering resynchronization
attempts while the UE responds to radio bearer setup only after the timer expires,
and the RNC deletes the radio links to recover the call without a ciphering mismatch.
The timer is configurable with this PRFILE parameter, and its default value is 3
seconds.
• Counter M1006C334 is used to measure the number of ciphering resynchronization
attempts while the UE responds to the interfrequency handover command only after
the timer expires, and the RNC deletes the radio links to recover the call without a
ciphering mismatch. The timer is configurable with this PRFILE parameter, and its
default value is 3 seconds.
PRFILE control
parameter values.
Parameter values
g Note: The TM cipher activation control timer is set by this PRFILE parameter whenever
the AMR, IFHO, or both workarounds are active. There are allowed timer values for
each workaround, and the timer values are automatically set at the same time that their
respective parameter values are set. The following table lists the allowed timer values
for each active workaround:
AMR workaround IFHO workaround active Both AMR and IFHO

active workarounds active
0009H: 3 seconds 0003H: 3 seconds timer (default) 000BH: 3 seconds timer
timer (default) (default)
0019H: 2.5 seconds 0013H: 2.5 seconds timer 001BH: 2.5 seconds timer
timer
0029H: 3 seconds 0023H: 3 seconds timer 002BH: 3 seconds timer
timer
timer
timer
timer

AMR workaround IFHO workaround active Both AMR and IFHO

active workarounds active
timer
timer

0000H (no active workarounds) n/a
Dependence
n/a
2.102 002:2121 RU40_MAINT_25

Descriptive name
UE problem with HS-FACH with feature RAN1913: High Speed Cell_FACH
IPA-RNC: RN7.0 4.0, RN8.0 1.0, RN8.1 onwards
If Enhanced Cell_FACH features are enabled and direct transition from Cell_DCH to
Cell_PCH is performed for legacy commercial devices supporting E-FACH, UEs may
enter into a signaling loop when attempting to move to Cell_FACH from Cell_PCH state.
This results in a degradation of the Cell_PCH to E-FACH state transition KPIs.
A workaround has been implemented for Rel.7 and Rel.8 commercial devices supporting
E-RACH/E-FACH, which ensures that those UEs are always moved to Cell_FACH from
Cell_DCH after NW or UE detected inactivity.
The PRFILE parameter 002:2121 RU40_MAINT_25 controls the activation of the
workaround. The workaround is active when the parameter value is set to 3H.
g Note: The activation of this functionality is mandatory in case feature
RAN1913: High Speed Cell_FACH UL and/or feature
RAN1637: High Speed Cell_FACH DL are enabled.
For further information see technical support notes TS-RNC-SW-149 and TS-RNC-SW-
216
PRFILE control
parameter values.
Parameter values


0003H The workaround is active. Activation is required whenever features
RAN1913 and/or RAN1637 are active in the network.

0000H n/a
Dependence
RAN1913: High Speed Cell_FACH UL
RAN1637: High Speed Cell_FACH DL
RAN2494: Fast Cell_PCH Switching
2.103 002:2122 RU40_MAINT_26

Descriptive name
PRFILE controlled additional conditions for PrxNoise auto tuning triggering and updating
of R99 power related counters
Before PrxNoise auto tuning can be triggered to adjust the current PrxNoise value, it is
necessary to check that the affected cell and other cells in the same BTS frequency layer
are empty. The existing method to check cell empty condition in UL comprises either:
• Checking UE allocation (DCH or E-DCH) in CELL_DCH state.
• Checking if load factor (LF) thresholds are exceeded.
The existing method does not check common channel usage. When the RAN1913: High
Speed Cell_FACH feature is used, high RTWP (Received Total Wideband Power) values
can be present in cells despite low number of UEs using the high speed common
channel. EDCH usage in common channels can trigger PrxNoise auto tuning, which may
cause unwanted variations of the PrxNoise level.
To avoid triggering PrxNoise noise auto tuning due to HS-RACH usage, extended
conditions for defining a cell as empty are used. These conditions work in parallel to the
existing functionalities. Before PrxNoise auto tuning is triggered in a cell, the cell's
specific EDCH LF reported by the BTS must be zero, indicating that there are no EDCH
transmission in the cell. This check is valid only in case when the RNP parameter
HSRACHEnabled is set to enabled state and the PRFILE parameter 002:2122
RU40_MAINT_26 1st bit is set to 0.

Similarly to the change of the PrxNoise auto tuning functionality, the same empty cell
conditions are required in updating the following R99 power related counters:
• M1000C0 AVE_PRXTOT_CLASS_0
• M1000C34 AVE_LNRT_CLASS_0
• M1000C24 AVE_LRT_CLASS_0
The default and recommended value for the 1 st bit of PRFILE parameter 002:2122
RU40_MAINT_26 is 0. It is possible to fall back to legacy conditions by setting this same
bit to 1.
PRFILE control
parameter values.
Parameter values

0000H The extended conditions are enabled. Common channel usage is checked
when defining cells as empty.
0001H The extended conditions are disabled. Only legacy conditions apply when
defining cells as empty.

0000H n/a
Dependence
RAN1913: High Speed Cell_FACH
2.104 002:2124 RU40_MAINT_28

Descriptive name
PRFILE controlled functionality of Compressed mode support for SRB with PS NRT RAB
mapped to 0/0
The parameter 002:2124 RU40_MAINT_28 controls support of DCH compressed
mode measurement for SRB + PS NRT DCH 0/0 in RNC. This parameter enables and
disables DCH compressed mode measurement for SRB + PS NRT DCH 0/0 in RNC. If
enabled, RNC is able to apply DCH compressed mode to SRB + PS NRT DCH 0/0.

When the functionality is enabled, there is no need to keep dedicated resources
reserved just because of measurement, and so holding times of resources are
shortened. That is especially good in cases where HSDPA or HSUPA compressed mode
is not in use, because then, the connection needs to be reconfigured first to DCH/DCH or
to DCH/HS-DSCH before measurements, which means that PS RABs need to be placed
into the PS scheduling queue for the allocation of DCH resources. If the PS queue is full,
then the measurement start will be unnecessarily delayed.
A change has been implemented into the MBLB inactivity trigger to allow compressed
mode measurements for those cases when the only possibility is to reconfigure the
connection to SRB + PS NRT DCH 0/0. The change ensures that the connection is
directly reconfigured to SRB + PS NRT DCH 0/0 when the MBLB inactivity trigger is
active. With this change, the RNC does not need to wait for the allocation of DCH
resources. There is no need to keep inactive resources reserved, and available capacity
is increased.
A change has also been implemented to LTE measurements where LTE is measured
before layering or handover to LTE. The change makes it possible to release the
dedicated PS resources before the measurement (PS resources are released for
inactivity), and it is possible to do measurement when PS service is already mapped to
DCH 0/0 (before measurement is triggered).
If the parameter is enabled when an SRB is mapped to E-DCH/HS-DSCH or to E-
DCH/DCH, the SRB will be then reconfigured to DCH/DCH and DCH compressed mode
will be applied to SRB + PS NRT DCH 0/0.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
RAN1668 - HSUPA Compressed Mode for LTE and Inter-frequency Handover
RAN2172 - Multi-Band Load Balancing
RAN2980 – Measurement based LTE layering
RAN2264 – Smart LTE Handover
2.105 002:2125 RU40_MAINT_29

Descriptive name

PRFILE controlled condition in RLC Downlink buffer check algorithm for state transition
Description
In RU50, state transition procedure from CELL_DCH to CELL_PCH has been improved
to avoid packet drop during state transitions. The already started state transition from
Cell_DCH to Cell_PCH is cancelled if uplink data is received or data is present in uplink
or downlink RLC buffer after decision to start the state transition. In such a case,
Cell_FACH RRC state is chosen instead of Cell_PCH so that UE can still send data.
During customer pilots it was observed that while the downlink buffer check algorithm is
performed and target state is chosen as cell_FACH, minor increase (0.2%) in PS RAB
drop can be seen in cases where UE does not respond in Cell_FACH state.
The new 002:2125 RU40_MAINT_29 PRFILE parameter-based implementation is
done for controlling the current RU50 default implementation where packet loss is
avoided. The optional configurable value of the 002:2125 RU40_MAINT_29 PRFILE
parameter (8000H) can be used to control cases with minor increase in PS RAB drop
counter.
It is recommended to use the current default 002:2125 RU40_MAINT_29 value to
avoid packet drops. For more information, see chapter Control for avoiding loss of end
user PS data in Cell_DCH to PCH transition in the RNC Generic Algorithm Changes and
Impact on Counters and KPIs document.
g Note: Note that once the parameter value has been changed, the change is
implemented within 10 minutes.
PRFILE control
parameter values.
Parameter values

8000H Value used to control conditions of minor increase in PS RAB drop
counter

0000H n/a
Dependence
n/a

2.106 002:2126 RU40_MAINT_30

Descriptive name
UE workaround for device crash during HSPA to DCH channel switch with interpolation
IPA-RNC: RN7.0 4.1, RN8.1 onwards
If UTRAN configures interpolation whenever the UE was initially configured for EDCH by
the network with a spreading factor combination of 2xSF2 + 2xSF4 and at least one
reference ETFCI requiring this combination, then, whenever this connection is released,
the UE crashes. This can happen during an E-DCH to DCH switch for the SRBs. In
network KPIs the problem is seen as a retainability drop for PS because RNC does not
receive response from the UE during the channel switch from HSPA to DCH for
Signalling RBs. If the channel switch was performed to setup CS voice call, then also the
voice call setup fails.
The problem has been observed in commercial devices with the XMM62xx and
XMM6360v1 platforms. The device fix is already available in the XMM7160 platform and
beyond.
A network workaround has been made so that it does not allow the use of interpolation
when E-DCH is configured in uplink and the device supports it. The workaround can be
separately activated for either Release 7 or Release 8 or both devices.
g Note: It is recommended to activate the workaround only if there are devices that crash
during the channel switch when interpolation is used. After the change, the channel
switch is successful and the call is continued without interruptions.
The workaround is controlled with the 002:2126 RU40_MAINT_30 PRFILE
parameter. Its default 0H value is recommended.
• 1st bit: turns the functionality on for Release 7 devices (value 1H).
• 5th bit: turns the functionality on for Release 8 devices (value 10H).
If both Release 7 and Release 8 workarounds are to be activated then PRFILE
parameter 002:2126 RU40_MAINT_30 should be set to 11H.
PRFILE control
parameter values.
Parameter values

Recommended Effect
value(s)
0000H The functionality is not activated.
0001H The functionality is activated for Release 7 devices.
0010H The functionality is activated for Release 8 devices.
0011H The functionality is activated for Release 7 and Release 8 devices.

0000H 0000H - FF00H n/a
Dependence
n/a
2.107 002:2128 RU40_MAINT_32

Descriptive name
Increasing IFC V2 slow start bit rate for HSDPA
IPA-RNC: RN8.1 2.0
mcRNC: mcRNC 4.1 2.0
A series of benchmark tests performed over Nokia RNCs found that in multiple file
download scenarios, the first download taking place after having a HSPA/HSDPA call
established was performing at a slower rate. The root cause was identified in the Slow
Start period of the IFCv2 (Internal Flow Control version 2) algorithm. During this Slow
Start phase, data rates are controlled through an internal parameter called
slowstartbitratehsdpa.
In order to improve performance, the Slow Start bitrate for HSDPA has been increased
from 68kbps to 1024kbps. This functionality is controlled via SKFILE, the configuration
file containing specific values for the User Plane processing unit, along with other IFCv2
parameters.
After this change, SKFILE has now two sets of IFCv2 parameters, which are selected
based on the value of 002:2128 RU40_MAINT_32. Depending on the value of this
parameter the RMDPRB (the platform process configuring UP applications) reads either
legacy or new values from SKFILE. The corresponding value is then sent to UP
applications via P_FC_server, the platform process responsible for the routing of internal
flow control messages.
PRFILE control
parameter values.

Parameter values

0000H The functionality is not active, legacy SKFILE values are taken.
0001H The functionality is active, new SKFILE values are taken.

0000H n/a
Dependence
n/a
2.108 002:2129 RU40_MAINT_33

Descriptive name
Releasing RRC connection when RNC has not received IMSI from core network
IPA-RNC: RNC16 onwards
mcRNC: mcRNC16 onwards
It has been noticed that on certain occasions core network SGSNs do not to send the
IMSI of a UE to the RNC, either because the authentication procedure has not been
completed or due to a bug in the implementation. The RNC does not know the reason for
not having received said IMSI in either case. In these cases, the RNC cannot page
devices with missing IMSI in Cell_PCH state if the RNC performed state transition after
device inactivity.
A two-phase workaround has been implemented. In phase 1, the RNC does not allow
the transition to PCH state for UEs whose IMSI has not been received from the CN.
These UEs are left in FACH state, at the cost of additional network resources.
Phase 2 complements the previous workaround by freeing devices that go inactive in
Cell_FACH state. When a UE whose IMSI has not been received is in Cell_FACH state
and the RNC detects further inactivity in Cell_FACH, the RNC releases the user's RRC
connection instead if performing a state transition to Cell_PCH. Note that the release of
RRC connections will have an impact on RNC counters.
Phase 2 of the workaround is controlled by the 1st bit of the 2nd byte, or 9th bit, of the
002:2129 RU40_MAINT_33 parameter.
9thbit of the parameter Phase 2 workaround status
xxxx xxx0 xxxx xxxx Active. IMSI issues impact RNC counters.
xxxx xxx1 xxxx xxxx Inactive. IMSI issues do not impact RNC
counters.

PRFILE control
parameter values.
Parameter values
Recommended Effect
value(s)
0000H Phase 2 of the workaround is active. IMSI issues impact RNC counters.
0100H Phase 2 of the workaround is NOT active. IMSI issues do not impact RNC
counters

0000H 0000H - FF00H n/a
Dependence
n/a
References
Further information on this workaround can be found on the RNC Generic Algorithm
Changes and Impact on Counters and KPIs document. This document can be found in
NOLS under the Care section, within the Release Documentation package for each
relevant product.
2.109 002:2131 RU40_MAINT_35

Descriptive name
Correction of paging load increase after RN8.1 1.0 or mcRNC4.1 1.0 SW update
PRFILE parameter 002:2131 RU40_MAINT_35 adds the possibility to deactivate the
RNC wide UTRAN paging repetition enhancement, in order to avoid strong paging load
increases identified after upgrading mcRNC3.0 4.0 to mcRNC4.1.
Up to a threefold increase in RNC level average paging load increase has been
observed in upgraded live environments. This is caused by an increased amount of
Paging Type1 messages originating in the RNC. If RNC does not reach UE (in Cell URA
/Cell PCH state) with the U-RNTI identified Paging Type1 (in RAN originated Paging),
RNC repeats the paging attempt with the IDLE mode (IMSI) Paging Type1 RNC wide.

The primary correction for the problem is that RNC wide repetition is not used if the
UTRAN originated paging is triggered due to call release (Iu Release Command from
Core Network), as in many cases the UE has left the UTRAN and moved to other RAT.
This is expected to decrease the paging amounts to a tolerable level.
PRFILE parameter control has been added to this RN8.1 / mcRNC4.1 correction,
allowing operators to switch off the RNC wide IMSI paging repetition for UTRAN
originated Paging in case the primary correction does not solve the paging load problem.
By default, the original RN8.1 / mcRNC4.1 correction is enabled as it is expected that the
main contributor for the increased paging load is solved with the primary correction.
PRFILE control
parameter values.
Parameter values
Recommended Effect
value(s)
0000H RNC wide IMSI paging repetition for UTRAN originated paging is used
0003H RNC wide IMSI paging repetition for UTRAN originated paging is not used

0000H n/a
Dependence
n/a
References
Further information on this workaround can be found on issue 01F of the RNC Generic
Algorithm Changes and Impact on Counters and KPIs document. This document can be
found in NOLS under the Care section, within the Release Documentation package for
each relevant product.
2.110 002:2132 RU40_MAINT_36

Descriptive name
Solution to improve CSSR for voice calls that drop immediately after inter-RAT handover
from GSM to 3G because of RL failure
IPA-RNC: RN8.1 3.0, RNC16 onwards
mcRNC: mcRNC4.1 3.0, mcRNC16 onwards

In the current inter-radio access technology (RAT) handover from 2G to 3G, UMTS
terrestrial radio access network (UTRAN) triggers a synchronized reconfiguration
procedure immediately after the completion of the handover procedure. In parallel to this
trigger, UTRAN also commences several measurements on the user equipment (UE) in
order to handle the call based on UE measurement reports. Further obligatory signaling
is required in the inter-RAT handover procedure:
• integrity protection start
• UE timer and connected mode constant value updates
• block error ratio (BLER) target provision for DCH signaling
After completing the obligatory procedures, UTRAN starts a synchronized
reconfiguration procedure. UTRAN is not able to handle measurement reports from the
UE until the reconfiguration procedure has completed (3GPP TS 25.331). A separate
synchronized reconfiguration is performed because ISHO is performed on 12.2k in
multimode AMR (RNC initiates reconfiguration to actual codec after the ISHO procedure
has completed). The initial design of the inter-RAT GSM to 3G handover assumes that
the default configuration identity 3 (SRB3.4k 12.2k AMR) is supported by all UEs. Failure
in the synchronized reconfiguration procedure for AMR modification is visible to the end
user as a dropped call, which negatively impacts call completion success rate (CSSR)
KPIs.
The new solution avoids the separate reconfiguration procedure during 2G to 3G
handover. Instead of using the default configuration identity 3 (corresponding to 12.2k
AMR 3GPP TS 25.331, chapter 13.7), RNC configures actual codec configuration
parameters during the inter-RAT handover signaling parameters. RNC does not start the
synchronized reconfiguration procedure to set up SRB4 after the handover has
completed.
The new functionality is activated via PRFILE, and applies to Release 6 or newer UEs
only. Older UEs always perform inter-RAT handovers following the legacy procedure,
which reduces potential issues on UEs that do not support the default configuration
identities introduced in 3GPP TS 25.331.
The improvement is visible in the CSSR KPIs and is expected to improve user
experience by reducing the number of dropped calls during GSM to 3G inter-RAT
handovers.
It is recommended to activate the functionality in scenarios with visible CS drops
because of UE counters increase after activation of inter-RAT handover from GSM to
3G, or when it is noticed that radio connections are being dropped during AMR
reconfiguration after inter-RAT handover.
PRFILE control
parameter values.
Parameter values
Recommended Effect
value(s)
0000H The improvement is not active.
0001H The improvement is active.


0000H n/a
Dependence
n/a
References
n/a
2.111 002:2134 RU40_MAINT_38

Descriptive name
Device issues when configuration management (CM) for LTE measurements are
activated and network starts reconfiguration procedures during ongoing LTE CM
If RAN2980: Measurement Based Layering is activated in the network with high-speed
packet access (HSPA) compressed mode in Cell_DCH, some devices cannot handle
reconfiguration procedures during ongoing E-UTRA measurements. The following are
the issues visible in Release 8 devices that support E-UTRA compressed mode
measurements (in connection mode) in Cell_DCH:
1. If RRC reconfiguration message is sent to the user equipment (UE) during an
ongoing compressed mode in an HSPA call (the reconfiguration message includes
DPCH Compressed Mode Info IE with only TGPS-ID and TGCFN), the UE loses the
radio connection or the UE crashes during or after the completion of the
reconfiguration procedure. The situation happens during HSPA serving cell change
procedure, HSPA channel switches, and so on.
2. If CPC is activated in the call and E-UTRA compressed mode measurements are
started, the UE loses the radio connection or the UE crashes.
3. If the UE is dual cell high-speed downlink packet access (HSDPA)-capable and dual
cell is activated in the network, RNC reconfigures the UE to single cell HSDPA before
the activation of E-UTRA compressed mode measurements. If E-UTRA
measurements do not result in any redirection to LTE, the compressed mode
measurements are stopped and the UE is immediately switched back to dual cell
HSDPA. Some devices lose the radio connection after the single cell to dual cell
HSDPA switch.
4. If E-TTI reconfiguration procedure is started during an ongoing E-UTRA
measurement, the UE loses the radio connection or the UE crashes.

5. If E-UTRA measurement is run on Release 8 UE with E-DCH transport channel, an
unspecified UE behavior is observed (for example, loss of radio connection). This
blanket case covers all issues that might be triggered by running E-UTRA
measurement with E-DCH transport channel on Release 8 UE (including but not
limited to issues 1 to 4).
The following are the respective workarounds of the issues visible in Release 8 devices
that support E-UTRA compressed mode measurements (in connection mode) in
Cell_DCH:
1. When sending RRC reconfiguration message to the UE during ongoing E-UTRA
measurements, radio network controller (RNC) will send the DPCH Compressed
Mode Info IE, including the full parameters, for compressed mode.
2. If E-UTRA measurements are to start in Cell_DCH state for Release 8 HSPA call
with CPC activated, RNC will deactivate CPC and afterwards activate E-UTRA
measurements. Only if E-UTRA measurements did not result in any redirection to
LTE and the criteria for allocating CPC were met during the next reconfiguration
procedure that the CPC is reactivated for the same UE.
3. If E-UTRA compressed mode measurements are stopped and the UE is dual cell-
capable, RNC will initiate forced state transition to Cell_FACH.
4. If E-UTRA measurement is to start, RNC will first reconfigure E-TTI from 2 ms to 10
ms. Reconfiguration back to 2 ms during the measurement will be denied.
5. If E-UTRA measurement is to start on Release 8 UE, RNC will reconfigure UE uplink
(UL) transport channel from E-DCH to DCH and will keep that transport channel until
LTE CM measurement is stopped. When this workaround is activated, it overrides
workarounds 1 to 4 for Release 8 UEs.
Depending on the deployed features in the network, each workaround can be activated
separately. It is recommended to activate the workarounds depending on the features
being used in the network. For example if CPC and dual dell HSDPA are not activated in
the entire network, workarounds for activated CPC and dual cell HSDPA-capable UE,
respectively, do not need to be used.
PRFILE control
parameter values.
Parameter values

0x0321 Workarounds 1, 2, and 3 are activated.
0x0221 Workarounds 1 and 3 are activated.
0x0021 Only workaround 1 is activated.
0x2321 Workarounds 1, 2, 3, and 4 are activated.


0x1321 Workarounds 1, 2, 3, and 5 are activated.

0H If HSPA CM for E-UTRA n/a
measurement is activated, it is
recommended to at least
enable workaround 1.
If DC or CPC is activated in the
network and is not needed,
workarounds 2 and 3 need to
be activated.
If HSUPA 2 ms TTI is activated
in the network, it is
recommended to activate
workaround 4.
If no resolution is found by the
activation of workarounds 1 to
4, it is the only time that
activation of workaround 5 is to
be considered.
For further instructions on
recommended usage, see TS-
RNC-SW-149.
Dependence
The workarounds are dependent on Release 8 UE issues during E-UTRA compressed
mode measurements for ongoing HSPA call in Cell_DCH.
• RAN2980: Measurement Based LTE Layering
• RAN1668: HSUPA Compressed Mode for LTE and Interfrequency
2.112 002:2136 RU40_MAINT_40

Descriptive name
E-UTRA capability enquiry changes
RNC RN8.1 4.0

RNC16 1.0 onwards
mcRNC mcRNC4.1 4.0
mcRNC16 1.0 onwards
The increasing number of supported E-UTRA bands results in an increased number of
CA combinations, which increases the size of the user equipment (UE) E-UTRA
capability information element (IE) within RRC CONNECTION SETUP COMPLETE and
UE CAPABILITY INFORMATION messages. The IE increase may lead to RRC
connection setup failures and increased RRC connection setup time, since the maximum
RRC message size can be exceeded. With the introduction of newer UE models, the
issue can happen with increasing frequency.
The mechanism is modified so that it is possible to limit the scope of UE EUTRA
capabilities enquiry to a limited set of LTE frequency bands. In order to further prevent
failures of the UE capability enquiry procedure that are caused by the excessive size of
the UE E-UTRA capability IE, the enquiry procedure is only triggered when fast SRB is
available.
The change implements the following functionalities:
• RNC verifies whether UE E-UTRA capability requests apply to the limited set of LTE
frequency bands applicable to Release 10 and newer UEs. If the check is positive,
RNC only requests the UE E-UTRA capabilities for this limited set of LTE frequency
bands.
• When E-UTRA capabilities are requested from the UE during RRC connection setup
procedure, SRBs are either:
– mapped to dedicated channel (DCH) using 13.6 kbit/s bit rate (if SRB DCH 13.6
kbit/s experiences congestion 3.4 kbit/s may be retried, and even if DCH 3.4
kbit/s SRB is allocated the E-UTRA capabilities are still requested)
– mapped to E-DCH in UL (in Cell_FACH or Cell_DCH state)
• RRC:RRC CONNECTION SETUP repetitions are stopped when UP indicates UL
data on SRB2/3.
• The request of UE E-UTRA capabilities during UE capability enquiry procedures is
only triggered when UL SRB is mapped to E-DCH (in Cell_FACH or Cell_DCH state).
• Handovers to LTE are not allowed when UE E-UTRA capabilities are not available.
• UE E-UTRA capabilities are not requested in emergency call cases.
The activation of the functionalities can be configured individually by modifying the value
of PRFILE parameter 002:2136 RU40_MAINT_40. The functionalities are active by
default.
PRFILE control
parameter values.
Parameter values
Hex Value Effect

Digit (Hex)
xxxXH 1 UE E-UTRA capabilities are requested for all UE-supported LTE bands.

Hex Value Effect

Digit (Hex)
0 UE E-UTRA capabilities are requested only for the limited set of LTE
frequency bands.
xxXxH 1 SRB mapping (CCH/DCH) and bit rate during RRC connection setup are
controlled by the establishment cause and legacy parameters.
0 During RRC connection setup, SRBs are mapped to either:
• dedicated channels (DCH) using 13.6 kbit/s bit rate
• E-DCH in UL (in Cell_FACH or Cell_DCH state)
xXxxH 1 RRC:RRC CONNECTION SETUP repetitions are stopped after the
reception of RRC:RRC CONNECTION SETUP COMPLETE.
0 RRC:RRC CONNECTION SETUP repetitions are stopped when UP
indicates UL data on SRB2/3.
XxxxH 1 Sending RRC:UE CAPABILITY ENQUIRY with E-UTRA capability update
requirement is allowed regardless of UL SRB mapping. Handovers to LTE
are not allowed when UE E-UTRA capabilities are not available.
2 Sending RRC:UE CAPABILITY ENQUIRY with E-UTRA capability update
requirement is only allowed when UL SRB is mapped on E-DCH.
Handovers to LTE are allowed when UE E-UTRA capabilities are not
available. Note that if handovers to LTE are attempted without the UE E-
UTRA capabilities, the handovers may fail.
requirement is allowed regardless of UL SRB mapping. Handovers to LTE
are allowed when UE E-UTRA capabilities are not available. Note that if
handovers to LTE are attempted without the UE E-UTRA capabilities, the
handovers may fail.
requirement is only allowed when UL SRB is mapped on E-DCH.
Handovers to LTE are not allowed when UE E-UTRA capabilities are not
available.

0000H 0000H, 0001H, 0010H, 0011H, n/a
0100H, 0101H, 0110H, 0111H,
1000H, 1001H, 1010H, 1011H,
1100H, 1101H, 1110H, 1111H,
2000H, 2001H, 2010H, 2011H,
2100H, 2101H, 2110H, 2111H,
3000H, 3001H, 3010H, 3011H,
3100H, 3101H, 3110H, 3111H
Dependences
The parameter may override the settings of the following parameters:
• HSFACHRel7ConSetupEC
• SRBMapRRCSetupEC
• SRBBitRateRRCSetupEC
The parameter impacts the following features:

• RAN1797: Common Channel Setup

• RAN2717: Smart LTE Layering
• RAN2980: Measurement based LTE Layering
2.113 002:2139 RU40_MAINT_43

Descriptive name
Mechanism to recover from invalid UE cipher configuration without PS call drop
RNC RNC16 2.0
mcRNC mcRNC16 2.0
During PS call setup, faulty user equipments in some periods include count-C-
ActivationTime parameter in radio bearer setup complete message that is meant for
TM RBs only (specification reference: RRC 25.331 specification, section 10.2.34). The
invalid cipher configuration leads to PS call drops in RNC. A similar issue is also
observed at times during PS RAB reconfiguration. The issue is solely on user equipment.
The workaround provides recovery from the cipher configuration error of the user
equipment by initiating RNC RLC RESET to avoid PS data call drop. The workaround is
also recommended to be enabled permanently by the operator.
Impact on KPI counters might be present in a few scenarios. The change depends on
the number of faulty user equipments in the network. For instance, if there is a large
number of faulty user equipments sending invalid cipher configuration (that results in PS
call drop) in a particular cell, enabling 002:2139 RU40_MAINT_43 will cause a slight
decrease to the following counters:
• M1001C190 (RAB ACTIVE FAILURES DUE TO RNC FOR PS DATA
INTERA)
STREAM)
BACKG)
Enabling 002:2139 RU40_MAINT_43 will also in turn cause a slight increase to the
following counter:
• M1022C237 (DL reset due to RNC)
PRFILE control
parameter values.
Parameter values



0000H n/a
Dependences
n/a
2.114 002:2140 RU40_MAINT_44

Descriptive name
Workarounds for F-DPCH failure with some Release 7 UEs
RNC RN8.1 4.0
RNC16 1.0 onwards
mcRNC mcRNC4.1 4.0
mcRNC16 1.0 onwards
The change addresses the following issues found on Release 7 UEs in networks when
fractional DPCH (F-DPCH) is activated:
1. A workaround modifies the high-speed downlink shared channel (HS-DSCH)
category that is signaled to the base transceiver station (BTS) during RRC
connection setup phase, which is later on updated when UP is set up. The
workaround changes the default HS-DSCH category 11 to category 12, the same
used in HS-FACH. This workaround is enabled by default, but might be disabled by
modifying the 1st bit (bit 0) of this PRFILE parameter.
2. A workaround ensures that Release 7 UEs has no access to F-DPCH at any phase
(RRC connection setup, state transition to Cell_DCH, HSPA allocation in Cell_DCH
during UP setup or channel switches). This workaround is disabled by default, but
might be enabled by the 5th bit (bit 4) of this PRFILE parameter.
PRFILE control
parameter values.
Parameter values

0010H Workaround 1 is enabled. Workaround 2 is enabled.
0001H Workaround 1 is disabled. Workaround 2 is disabled.
0000H Workaround 1 is enabled. Workarounds 2 is disabled.


0000H n/a
Dependences
This PRFILE parameter is dependent on Release 7 UE in networks where F-DPCH is
activated.
The following is the feature dependency:
• RAN1201: Fractional DPCH
2.115 002:2141 RU40_MAINT_45

Descriptive name
RRM Optimization for better MOS
RNC RNC16 3.0 onwards
RNC17
mcRNC mcRNC16 3.0 onwards
mcRNC17
New functionalities for improving Voice quality are introduced.
Control of sending erroneous AMR frames from RNC to MGW is added for RNC. In
certain situations, bursts of bad quality AMR frames may be sent from RNC to MGW
which reduce the voice quality measured by Traffica tool. With the new functionality,
erroneous AMR frames can be dropped in RNC of up-link side. In down-link direction,
those erroneous frames are dropped by RNC, so for end user this functionality does not
have an effect.
Outer Loop Power Control (OLPC) modification: The new functionality allows UL SIR
target modifications between Reconfiguration command and Connection Frame Number
(CFN) when the Reconfiguration is done. This may reduce erroneous frames over the
air-interface and improve voice quality. With legacy implementation, UL SIR target is not
modified between Reconfiguration command and the actual CFN.
The AMR DCH can be set to be in Semi Active state and OLPC may send SIR up
commands.
These features improve the voice call quality.
PRFILE control
parameter values.
Parameter values


0100H The functionality is used for preventing erroneous SDU sending from
RNC.
0200H The functionality is used for allowing UL SIR commands during
Reconfigurations.
0400H The functionality is used for activating AMR DCH bearer to be in Semi
Active state.
0700H All functionalities active.

0000H n/a
Dependences
n/a
2.116 002:2142 RU40_MAINT_46

Descriptive name
Alarm setting for duplicate primary CPICH scrambling codes in mcRNC
mcRNC: mcRNC4.1 4.0, mcRNC16 2.0, mcRNC17 onwards
Alarms 3484 CONFLICTING SCRAMBLING CODES and 3485 SCRAMBLING CODE
CONFLICT indicate duplicate primary common pilot channel (CPICH) scrambling code in
neighbor cells (monitored ADJS and detected ADJD cells). RAN3271: Optimized
Neighbor Cell Processing feature supports these alarms for chained neighbor cells.
Earlier, these alarms were enabled only in Classic RNC but because of RAN3271:
Optimized Neighbor Cell Processing there is also a need for these alarms in
Multicontroller RNC (mcRNC). Some operators might not want to make these alarms
visible, therefore, a mechanism was developed to disable alarms 3484 and 3485 in
mcRNC.
The value of PRFILE 002:2142 RU40_MAINT_46 parameter defines if alarms 3484
and 3485 can be enabled in mcRNC. By default (0H), the alarms are not enabled and
the operator will not see any change in the alarm system.
In Classic RNC (IPA_RNC), these alarms are always enabled regardless of the value of
002:2142 RU40_MAINT_46.
PRFILE control
parameter values.
Parameter values


0001H Alarms 3484 CONFLICTING SCRAMBLING CODES and 3485
SCRAMBLING CODE CONFLICT are enabled. The alarms can be set.
0000H Alarms 3484 CONFLICTING SCRAMBLING CODES and 3485
SCRAMBLING CODE CONFLICT are not enabled. The alarms will not be
set.

0000H n/a
Dependences
RAN3271: Optimized Neighbor Cell Processing
2.117 002:2143 RU40_MAINT_47

Descriptive name
Active Set RSCP threshold for LTE measurement setup
mcRNC: mcRNC16 2.0 onwards
When features RAN2980: Measurement Based LTE Layering or RAN2264: Smart LTE
Handover are activated, RNC allows LTE measurement to be set up on UE regardless of
the strength of the signal UE receives from WCDMA radio links. This increases the risk
of call drops at locations with weak LTE coverage , because the required set up of
WCDMA IFHO or GSM ISHO measurement at end of WCDMA cell coverage will be
delayed until the LTE measurement has been finished.
Additionally, UE reconfiguration procedures associated with LTE measurement set-up at
weak WCDMA signal conditions also increase the risk of call drops, regardless of the
delay effect on WCDMA IFHO/GSM ISHO measurements.
As a workaround to this problem, a threshold for the WCDMA signal strength is
introduced as a precondition for the initiation of LTE measurements. This received signal
strength (RSCP) threshold can be activated and configured by modifying PRFILE
parameter 002:2143 RU40_MAINT_47. If the workaround is active, RNC will not start
the LTE measurement on UE unless the RSCP of an Active Set cell, as reported by UE,
meets or exceeds the set threshold value.
PRFILE control
parameter values.
Parameter values


0001H - 005CH The RSCP threshold is enabled. Values range from -116 dBm to -25 dBm,
with a 1 dBm step.
0000H The RSCP threshold is disabled.

0000H 0000H - 005CH n/a
Dependence
Feature dependencies: RAN2980: Measurement Based LTE Layering, RAN2264: Smart
LTE Handover
2.118 002:2144 RU40_MAINT_48

Descriptive name
Correction to HSPA setup rejection counters.
RNC RNC17
mcRNC mcRNC17
In case of state transition from CCH to CELL_DCH or NRT User Plane setup in
CELL_DCH state, when SRB allocation on E-DCH/HS-DSCH or E-DCH/DCH is tried in
conjunction with NRT User Plane setup on E-DCH/HS-DSCH (RAN1201 and/or
RAN1470), HSPA Admission Control (AC) is performed first for the SRB and then for the
NRT RAB. If there is congestion due to HSDPA user or HSUPA user amount, HSPA AC
fails for the SRB and no HSPA AC is performed for the NRT RAB. This results in HSPA
setup rejection due to AC counters being updated only based on the SRB, which means
that traffic class specific HSPA setup rejection counters are not getting updated, when
DCH is selected for the NRT RAB instead of HS channel.
To improve the situation, RNC is corrected to update HSPA setup rejection counters for
the failed NRT HS(D)PA setup regardless of the SRB channel type. Expected impact of
the correction is that HSPA setup rejection due to AC counters will reflect reality. New
RNC SW correction is activate by default, but can be deactivated with PRFILE parameter
002:2144 RU40_MAINT_48.
With the correction activated, the following counters showing HSDPA or HSUPA setup
rejection due to AC are expected to increase:
• M1002C475 DCH_SEL_MAX_HSDPA_USERS_INT
• M1002C476 DCH_SEL_MAX_HSDPA_USERS_BGR
• M1002C515 UL_DCH_SEL_MAX_HSUPA_USR_INT
• M1002C516 UL_DCH_SEL_MAX_HSUPA_USR_BGR
• M1002C517 UL_DCH_SEL_BTS_HW_INT
• M1002C518 UL_DCH_SEL_BTS_HW_BGR

• M1002C681 SETUP_REJ_EDCH_AC_INT
• M1002C682 SETUP_REJ_EDCH_AC_BGR
As a result, following KPIs are expected to degrade:
• HSDPA Resource Accessibility for NRT Traffic (RNC_605b)
• HSUPA Resource Accessibility for NRT Traffic (RNC_913b)
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependences
n/a
2.119 002:2146 RU40_MAINT_50

Descriptive name
Handover control optimizations
RNC RNC16 4.0
RNC17
mcRNC mcRNC16 4.0
mcRNC17
Change 1:
From RU10 onwards, there has been a functionality when UE reports e1c for not good
enough candidate that radio link replacement can be denied, and poor active set radio
links can be removed instead, thus preventing a continuous loop of replacing bad cells
with almost equally bad cells.
It has been observed in some RU50 level networks that when a call is in poor coverage
and/or quality field, it is possible that a call might be dropped because radio links are
removed from the active set due to this functionality because the remaining radio link is
not good enough to keep the call ongoing. Usually, this also involves ongoing inter-
frequency or inter-system (either GSM or LTE) measurement, which is ongoing to
transfer the poor quality call to a better WCDMA frequency or system.

As a workaround to the problem, this PRFILE parameter is provided for disabling the
functionality, which can convert received e1c to radio link deletion in case there is an
ongoing inter-frequency or inter-system measurement, and e1c report is received during
an ongoing handover control procedure. This will improve the possibility that a call can
be successfully handed over to a better WCDMA frequency or to GSM/LTE.
Change 2:
FMCS network configuration parameters contain parameters for both soft handover
(SHO)-related reporting events (e1a, e1b, and e1c) and for event-based triggers for
inter-frequency and inter-system measurements (e1f and e1e). It is customary that
operators configure several FMCS parameter sets in a network for different types of
traffic. Handover control sends these parameters to the UE if the used FMCS set needed
by the current traffic type and active set cell configuration changes. Handover control
sends this data to the UE in two different RRC MEASUREMENT CONTROL (MC)
messages: for e1a/e1b/e1c (SHO parameters) and for e1f/e1e.
It has been observed in some RU50 level networks that when there are maximum
amount of intra-frequency neighbour cells (ADJS) configured for WCEL objects, the
number of RRC MEASUREMENT CONTROL message for e1a/e1b/e1c is high. This is
because both full neighbor cell list information (ADJS neighbors) and SHO event-related
FMCS parameters are included in MC when the used measurement command is setup.
The setup command is used, for example, when there are Radio Bearer (RB) changes
or a user plane is created and needed FMCS set changes. It has also been observed
that in many cases, the only difference between changed FMCS sets is related to
e1f/e1e parameters and not SHO parameters, or that there is no difference at all. This
means that there is lot of redundant data sent to the UE. This causes load to the
signalling link, and in worst case scenario, a call might drop if it is already in poor
quality/coverage.
As a workaround to the problem, this PRFILE parameter is provided so that only
changed data can be sent to the UE with the measurement command modify instead of
setup. If there are RB changes, only changed e1a/e1b/e1c-related information is sent to
UE, thus reducing the size of the MC.
PRFILE control
parameter values.
Parameter values

0x0000 Optimizations are not active.
0x0001 Changing e1c to active set radio link deletion optimization is active.
0x0002 FMCS SHO parameter checking and MC optimization is active.
0x0003 Both e1c and FMCS optimizations are active.

0x0000 n/a
Dependences
RAN1266 Soft Handover Based on Detected Set Reporting

RAN2738 Fast HSPA Mobility II
2.120 002:2148 RU40_MAINT_52

Descriptive name
This PRFILE parameter is used to activate LCS Capacity Enhancement functionality.
RNC RNC18
mcRNC mcRNC18
The value of this PRFILE parameter determines if the LCS Capacity Enhancement is
enabled or not. By default, it is set to 0H (disabled).
PRFILE control
parameter values.
Parameter values

0000H, 0002H- The functionality is not active.
FF00H

0000H n/a
Dependences
n/a
2.121 002:2151 RU40_MAINT_55

Descriptive name
Including PS 0/0 RABs in RAB TrCH Mapping list in SRNC relocation.
RNC RNC16 4.0
RNC17
mcRNC mcRNC16 4.0
mcRNC17

This parameter is used to allow inclusion of PS 0/0 RABs in RAB TrCH Mapping list of
the Source RNC to Target RNC Transparent Container in the IU RELOCATION
REQUIRED and IU RELOCATION REQUEST messages.
Normally, Nokia RNC does not include the 0/0 PS RABs because they are not connected
over Iur, and because the necessary information of them is included elsewhere in the
RELOCATION REQUEST message. If, however, some other RNC requires this
information to handle the incoming relocation correctly, the PRFILE parameter can be
activated. Then also the relevant target RNC’s must be indentified by marking their type
as 4 in the “Neighbor RNC type” field in the Iur list of the Nokia RNC.
By default, this PRFILE parameter has a value of "0". in this case the function is not
active, and the PS 0/0 RAB’s are not included.
To activate the feature, the value "3" (two lowest bits of the PRFILE parameter set) shall
be written to the parameter. Then, the PS 0/0 RAB’s are included if the target RNC has
neighbor RNC type value 4 in Iur list.
This feature should be activated, if necessary, after consultation with Nokia’s support
personnel.
PRFILE control
parameter values.
Parameter values

0 The functionality is not active.
3 The functionality is active.

0 n/a
Dependences
n/a
2.122 002:2152 RU40_MAINT_56

Descriptive name
UL interference parameter
RNC RNC16 5.0
RNC17 1.0
mcRNC mcRNC16 5.0
mcRNC17 1.0

This parameter contains UL interference value that RNC uses in RIM procedure as a
fixed value.
g Note: After the modification of the PRFILE parameter 002:2152 RU40_MAINT_56

or taking the new default value into use, the RAN3086 feature needs to be deactivated
in RNC. 1 minute after the PRFILE action (or if the default value is used no need for
modification), the RAN3086 can be activated again and then the new value is in use.
PRFILE control
parameter values.
Parameter values

0H The functionality is active with the default value.
6EH The functionality is active.

0H n/a
g Note: The acceptable range for this parameter is from 46H to 6EH. The parameter
rage is reversed to the interpreted range:
Table 7 Parameter range interpretation value
Parameter Value Interpreted Value
0H (default) -100 dBm
46H (minimum) -70 dBm (maximum)
6EH (maximum) -110 dBm (minimum)
Dependences
n/a
2.123 002:2235 TOT_RESET_LIM_PER_SITE

Descriptive name
Total restart limit per site
If the restart is recurring daily, the value of this PRFILE parameter determines the
number of times RNC is allowed to totally restart a base transceiver station (BTS).

As a recovery action, non-performing cell recovery performed by the RNC triggers a BTS
restart to recover the non-performing (because of a failure) cells otherwise recovered
with less invasive operation. If the restart is recurring daily, the value of this PRFILE
parameter controls the number of times RNC is allowed to totally restart a BTS.
PRFILE control
parameter values.
Parameter values

0000H The non-performing cell recovery functionality is disabled.
0001H-0014H The functionality is enabled. The maximum number of consecutive BTS
restarts is set between 1 and 20.

000AH n/a
Dependence
CR E0699 Total restart limit per site for Non-Performing Cell
2.124 002:2257 UDP_FILL_RATIO_HIGH

Descriptive name
UDP port reservation ratio threshold
This PRFILE parameter defines the threshold for the User Datagram Protocol (UDP) port
reservation ratio. If the UDP port reservation ratio of IP address exceeds the threshold
value, alarm UDP PORTS RUNNING OUT is set.
PRFILE control
parameter values.
Parameter values



0001H-0063H The alarm is enabled and the threshold is set between 1 and 99.
0064H-FF00H The alarm is enabled. The maximum value (99) is used.

005AH n/a
Dependence
n/a
2.125 002:2258 LEG_ERROR_RATIO_HIGH

Descriptive name
Leg setup error ratio threshold
g Note: This is not applicable to mcRNC.
If the leg setup error ratio exceeds the threshold value that is defined by this parameter,
alarm EXCESSIVE LEG SETUP ERRORS is set.
If the leg setup error ratio drops below the threshold value that is defined by this
parameter, alarm EXCESSIVE LEG SETUP ERRORS is canceled.
If the alarm is not cancelled within the restart waiting time set with PRFILE 002:1904
parameter, and if the unit restarts are enabled with the same, alarm LEG SETUP UNIT
FAILURE is set. Consequently, the recovery system restarts the unit because of this
alarm.
PRFILE control
parameter values.
Parameter values

0000H-0064H Leg setup error ratio threshold is set to a value between 0 to 100 %.

000AH n/a
Dependences

002:1904 RN60_MAINT_28 functionality is enabled or disabled via the parameter
setting.
2.126 002:2259 DYN_HSPA_BLER_MULTI_RAB

Descriptive name
Multi PS RAB Support for Dynamic HSUPA BLER
Description
This parameter controls the Multi PS RAB support for Dynamic HSUPA BLER
functionality.
With this functionality active in Peak data rate cases, OLPC controller decides the BLER
state change from Bursty/Continuous data to Peak data based on total throughput (sum
of effective throughput received from each OLPC entity) measured at E-DCH level.
The default and recommended value is 0, meaning that the Target BLER state
(Peak/Bursty/Continuous data) is decided by OLPC entities.
PRFILE control
parameter values.
Parameter values

0000H Target BLER state (Peak/Bursty/Continuous data) is decided by OLPC
entities.
0001H OLPC controller decides the BLER state change from Bursty/Continuous
data to Peak data based on total throughput measured at E-DCH level.

0000H n/a
Dependence
RAN2302: Dynamic HSUPA BLER
2.127 002:2264 RU50_SPARE_02

Descriptive name

This is a PRFILE parameter control for the RAN3266 Enhanced Mass Event Handler

feature.
RNC RNC17
mcRNC mcRNC17
This parameter is used for setting the RAN3266 Enhanced Mass Event Handler feature
functionality.
Default values should be used. Only if there is need for tuning the EMEH algorithm, then
some EMEH PRFILE parameter changes can be done. But this information is given,
case by case, from Nokia to the customer.
The decision-making is controlled by the Bit0 of the PRFILE 002:2264
RU50_SPARE_02 parameter. The following table shows the values accepted for Bit0:
Table 8 Accepted values for Bit0
Value Description
0 This is the default value. The decision making based on the serving cell
only is disabled (any AS cell may trigger).
1 The decision making based on the serving cell only is enabled.
The decision-making is controlled by the Bit0 of the PRFILE 002:2264
RU50_SPARE_02 parameter in case of the following three functions:
• Dynamic allocation of low data rate HSUPA power offsets and HSUPA Initial SIR
target offset enhancement
• High BLER target (continuous low bit rate) configuration for HSUPA user
g Note: For these two functions, in case of DC-HSUPA, the decision-making is
based on the EMEH cell state of the primary layer. The same configuration is
allocated to both the primary and secondary layers for these two functions.
• Periodicity increase of the UE measurement reporting
If the decision-making is based on all active set cells (Bit0 = 0), the following logic is
followed:
• If any cell of the active set is in EMEH load state, the EMEH load state actions are
applied to the UE.
• If any cell of the active set is in EMEH reactive state but none of them is in EMEH
load state, the EMEH reactive state actions are applied to the UE.
• If any cell of the active set is in EMEH preventive state, but none of them is in either
EMEH load state or EMEH reactive state, the EMEH preventive state actions are
applied to the UE.
PRFILE control
parameter values.

Parameter values

0x0 n/a n/a
Dependences
RAN3266 Enhanced Mass Event Handler feature
2.128 002:2265 RU50_SPARE_03

Descriptive name
feature.
RNC RNC17
mcRNC mcRNC17
functionality. This parameter is used for setting the EMEH_L_MIN_NRT_DYN_MIN and
EMEH_L_MIN_NRT_DYN_MAX values used by the Cell PS for the dynamic L_MIN_NRT
algorithm.
Default values should be used. Only if there is need for tuning the EMEH algorithm, then
some EMEH PRFILE parameter changes can be done. But this information is given,
case by case, from Nokia to the customer.
PRFILE control
parameter values.
Parameter values

EMEH_L_MIN_NRT Range 1... 100%, Step 1%, Default 10% if all bits 0.
_DYN_MIN (Bit0...
Bit7)
EMEH_L_MIN_NRT Range 1... 100%, Step 1%, Default 80% if all bits 0.
_DYN_MAX (Bit8...
Bit15)

0x0 n/a
Dependences

2.129 002:2266 RU50_SPARE_04

Descriptive name
feature.
RNC RNC17
mcRNC mcRNC17
functionality. This parameter is used for setting the
EMEH_L_MIN_NRT_HSUPA_MIN_USER_THRESHOLD and
EMEH_L_MIN_NRT_HSUPA_MAX_USER_THRESHOLD values used by the Cell PS for
the dynamic L_MIN_NRT algorithm.
Only if there is need for tuning the EMEH algorithm, then some EMEH PRFILE
parameter changes can be done. But this information is given, case by case, from Nokia
to the customer.
PRFILE control
parameter values.
Parameter values

EMEH_L_MIN_NRT Range 1.0... 5.0, Step 0.1, Default 1.0 if all bits 0.
_HSUPA_MIN_USE
R_THRESHOLD
(Bit0... Bit7)
EMEH_L_MIN_NRT Range 0.1... 1.0, Step 0.1, Default 1.0 if all bits 0.
_HSUPA_MAX_USE
R_THRESHOLD
(Bit8... Bit15)

0x0 n/a
Dependences
2.130 002:2267 RU50_SPARE_05

Descriptive name


feature.
RNC RNC17
mcRNC mcRNC17
functionality. This parameter is used for setting the
EMEH_AVERAGING_PERIOD_MEAS_LONG and
EMEH_AVERAGING_PERIOD_MEAS_SHORT values used by the Cell PS for the
averaging of the dynamic HSUPA user limitation (EMEH DMHU) algorithm.
to the customer.
PRFILE control
parameter values.
Parameter values

EMEH_AVERAGING Range 1... 255 secs, Step 1 sec, Default 20 secs if all bits 0.
_PERIOD_MEAS_L
ONG (Bit0... Bit7)
_PERIOD_MEAS_S
HORT (Bit8... Bit14)

0x0 n/a
Dependences
2.131 002:2268 RU50_SPARE_06

Descriptive name
RAN3266 EMEH feature PRfile parameter control
RNC RNC17
mcRNC mcRNC17

This parameter is used for setting the RAN3266 EMEH feature functionality wherein the
the EMEH_NORMAL_PRX_OFFSET parameter value is set and is to be used by the Cell
PS for the dynamic HSUPA user limitation (EMEH DMHU) algorithm.
g Note: Changes in the EMEH PRFILE parameter can be done only if there is need for
tuning the EMEH algorithm. This information is given, case by case, from Nokia to
customer.
PRFILE control
parameter values.
Parameter values

0x0 -3 dB. This is derived through the following formula:
EMEHNormalPrxTarget(dBm) = EMEHPrxBaseline(dBm) +
EMEH_NORMAL_PRX_OFFSET(dB) + MIN(0,
EMEHPreventivePrxOffset(dB))
EMEH_NORMAL_PR The functionality is active. The allowed range for which this value can be
X_OFFSET (Bit0... set is -0.5...-10 dB at a step increment of -0.5 dB. The default value is
Bit7) -3dB if all bits is 0.

0x0 n/a
Dependences
RAN3266 EMEH
g Note: This PRFILE parameter is used in WCDMA17 after the PR180094
implementation.
2.132 002:2269 RU50_SPARE_07

Descriptive name
feature.
RNC RNC17
mcRNC mcRNC17
functionality. This parameter is used for setting the EMEH_DMHU_STEP_SIZE and
EMEH_DMHU_ADJUST_PERIOD values used by Cell PS for the dynamic HSUPA user
limitation (EMEH DMHU) algorithm.

to the customer.
PRFILE control
parameter values.
Parameter values

EMEH_DMHU_STEP Range 0... 50 users, Step 1 user, Default 5 users if all bits 0.
_SIZE (Bit0... Bit7)
EMEH_DMHU_ADJU Range 0... 127 secs, Step 1 sec, Default 20 secs if all bits 0.
ST_PERIOD (Bit8...
Bit15)

0x0 n/a
Dependences
2.133 002:2272 RU50_SPARE_10

Descriptive name
feature.
RNC RNC17
mcRNC mcRNC17
functionality. This parameter is used for controlling activation of EMEH functions is
different EMEH cell states.
to the customer.
For more information, refer to the RAN3266 Enhanced Mass Event Handler feature.
PRFILE control
parameter values.
Parameter values


Value 0 (dec) Function is disabled in all EMEH cell states
Value 1 (dec) Function is enabled in EMEH load state
Value 2 (dec) Function is enabled in EMEH reactive state and EMEH load state
Value 3 (dec) Function is enabled in EMEH preventive state, EMEH reactive state and
EMEH load state
The following are the information about the different bits:
• (Bit0... Bit1): Dynamic allocation of low data rate HSUPA power offsets
• (Bit2... Bit3): High BLER target (continuous low bit rate) configuration for HSUPA
user
• (Bit4... Bit5): HSUPA 2 ms TTI limitation
• (Bit6... Bit7): TVM pending time increase
• (Bit8... Bit9): UL load based AC for HSPA+ features
• (Bit10... Bit11): Limitation of UL DCH NRT bit rates
• (Bit12... Bit13): Periodicity increase of the UE measurement reporting

0x0 For the recommended values, n/a
refer to RAN3266 Feature
Activation Manual.
Dependences
2.134 002:2273 RU50_SPARE_11

Descriptive name
This is a PRFILE parameter control for the RAN3266: Enhanced Mass Event Handler
feature.
RNC RNC17
mcRNC mcRNC17
This parameter is used for setting the RAN3266: Enhanced Mass Event Handler feature
functionality. This parameter is used for controlling EMEH_AVERAGING_PERIOD_USER
and EMEH_PREVENTIVE_MIN_DUR values used by the Cell PS for setting EMEH cell
states.
If there is a need to tune the EMEH algorithm, then some EMEH PRFILE parameter
changes can be done. However, this information is given case-by-case from Nokia to the
customer.
PRFILE control

parameter values.
Parameter values

_PERIOD_USER
(Bit0... Bit7)
EMEH_PREVENTIV Range 0... 127 secs, Step 1 sec, Default 20 secs if all bits 0.
E_MIN_DUR (Bit8...
Bit14)

0x0 n/a
Dependences
RAN3266: Enhanced Mass Event Handler
2.135 002:2276 RU50_SPARE_14

Descriptive name
Avoid RTWP spiking with RAN1913: High Speed CELL_FACH feature when implicit
release is used with value > 0 TTIs
RNC RNC16 CD2.0 onwards
mcRNC mcRNC16 CD2.0 onwards
When the RAN1913: High Speed CELL_FACH feature is enabled, there are times that
HS-RACH-capable user equpiments seem to follow transmit power control (TPC)
commands send in DL by using common enhanced dedicated transport channel (E-
DCH) resource originally assigned to it (although the implicit release is already triggered
and the user equipment has informed the base transceiver station or BTS). When an
implicit release is received by BTS, assigned common E-DCH resource is released (=
free resource) from the user equipment. The released common E-DCH resource can be
assigned to another HS-RACH capable user equipment by BTS. The result is two user
equipments follow the same TPC UP (power up) commands, which causes received total
wideband power (RTWP) spiking in the cell. The problem occurs mainly when implicit
release is used with value > 0 TTIs. By using value 0 TTIs for implicit release, RTWP
spiking can be reduced.
The workaround allows for the common E-DCH implicit release time 0 TTIs to be used. If
the workaround is activated, value 0 is signaled within SIB5 IE of E-DCH transmission
continuation back off (in cases where the implicit release is configured by using
HSRACHImplicitRelease or common E-DCH implicit release for HS-RACH
parameter). PRFILE 002:2276 RU50_SPARE_14 controls the workaround activation.
The workaround is active when the parameter value is set to 1H (recommended value).

PRFILE control
parameter values.
Parameter values


0000H 0001H n/a
Dependences
The following is the feature dependency:
• RAN1913: High Speed CELL_FACH
2.136 002:2277 RU50_SPARE_15

Descriptive name
Overlapping security mode control procedure improvement.
RNC RNC16 3.0
RNC17
mcRNC mcRNC16 3.0
mcRNC17
The parameter allows taking into use a general improvement to overlapping security
mode control procedures. In the scenario a SMC is started almost simultaneously from
both core networks, and due to a lost DL L2 ACK on radio interface, the second
procedure fails with UE sending cause value “incompatible simultaneous configuration”.
If the feature / improvement is active, the RNC sends the second SMC again to the UE,
and if the first procedure is complete on L2 level by then (very likely), the second SMC
sending attempt will succeed, and the SMC overall will succeed from the core network’s
point of view.
If the feature is not active, there will be at least additional delay affecting the procedures
initiated from the core network, since the core network will have to repeat the SMC
before further procedures can take place. With the correction, the unnecessary SMC
failure is avoided and operation will be smoother. The end user will see smoother, more
rapid operation after the UE has moved between location areas, and the operator sees
less security mode failure counter incrementation in these situations.
PRFILE control

parameter values.
Parameter values
Dependences
n/a
2.137 002:2278 RU50_SPARE_16

Descriptive name
PRFILE parameter to include Rel7/Rel8 HS-FACH users to the scope of RAN3082
device detection feature.
RNC RNC16 4.0
RNC17
mcRNC mcRNC16 4.0
mcRNC17
The PRILE parameter 002:2278 RU50_SPARE_16 has the activation of RAN3082
Device Detection feature for HS-FACH-capable rel7/rel8 UEs. This is needed as there
are rel7/rel8 HS-FACH-capable UEs that are not able to use the HS-FACH channel
correctly. With the Device Detection feature, those UEs can be restricted from using the
HS-FACH channel.
The PRILE has the switches for the following:
• Device detection activation for HS-FACH-capable Rel-7 UE
• Device detection activation for HS-FACH-capable Rel-8 UE
• Cell_PCH state usage HS-FACH forbidden Rel-7/Rel8 UE
This functionality is recommended to be used for Rel7 and/or Rel8 HS-FACH-capable
UEs if it is noticed that they cannot use HS-FACH. The details for device detection usage
can be found in the RAN3082 feature material.
PRFILE control
parameter values.
Parameter values
Recommended Effect
value(s)
0000H The functionality is not active:
• Device detection not activated for HS-FACH-capable Rel-7 UE
• Device detection not activated for HS-FACH-capable Rel-8 UE
• Cell_PCH state allowed for HS-FACH forbidden Rel-7/Rel-8 UE

Recommended Effect
value(s)
0003H The functionality is active: device detection activated for HS-FACH-
capable Rel-7 UE.
capable Rel-8 UE.
capable Rel7 UE and Rel-8 UE.
000BH The functionality is active: device detection activated for HS-FACH-
capable Rel-7 UE and cell_PCH state not allowed for HS-FACH-forbidden
Rel-7 UE.
000DH The functionality is active: device detection activated for HS-FACH-
capable Rel-8 UE and cell_PCH state not allowed for HS-FACH-forbidden
Rel-8 UE.
000FH The functionality is active: device detection activated for HS-FACH-
capable Rel7 UE and Rel-8 UE and cell_PCH state not allowed for HS-
FACH-forbidden Rel-7 and Rel-8 UE.

0000H 0000H - 000FH n/a
Dependences
Feature dependencies: RAN3082: Device Detection feature
2.138 002:2281 RU50_SPARE_19

Descriptive name
Voice call setup time improvements
RNC RNC16 4.0
RNC17 1.0
mcRNC mcRNC16 4.0
mcRNC17 1.0
g Note: In case of a call directed from LTE (8th bit) functionality, delaying of routing area
update (RAU) is not recommended to be used before RNC17 5.0 and mcRNC17 5.0.
If the functionality is used with an earlier release, the amount of redirections to LTE
might decrease.
This parameter controls voice call setup time improvements, as well as the:
• activation time offset (ATO) of voice calls with step size of 10 ms (a value 30 means
300 ms).

• ignoring of MBLB in case of circuit-switched (CS) voice call setup for users moved
from LTE.
• delaying of RAU in case of call directed from LTE.
• delaying of RAU in case of CS fallback (CSFB) HO call from LTE.
The idea is to prevent or delay mechanisms that increase voice call setup time. If the
value of this PRFILE parameter is changed, then the new value is taken into use after 15
min at the latest.
ATO of voice calls (1st to 6th bit)
For cases where voice call is set up, a shorter ATO can be defined. Its value is used in
case there is no need to reconfigure anything else except the reconfiguration of
signalling radio bearer (SRB) on dedicated traffic channel (DCH). The value is used for
users of 3G and also for users who moved from LTE because of voice call (CSFB).
However, this value is not used in the following cases:
• SRBs are on E-DCH/HS-DSCH when a voice call is setup.
• User has PS service mapped to DCH/HS-DSCH or DCH/DCH (>0 kbps).
• E-TTI is changed between 2 ms and 10 ms.
• User has radio link (RL) over Iur.
• User has RL over satellite Iub.
Ignoring of MBLB in case of CS voice call setup for users moved from LTE (7th bit)
A functionality can be activated where layering is not done by multi-band load balancing
functionality for a user who is moving from LTE and is setting up a voice call. Detection
of LTE cases is performed based on:
• existence of pre-redirection info IE in RRC:RRC CONNECTION REQUEST message.
• existence of CSFB Indication IE in RRC: RRC CONNECTION REQUEST message.
• existence of CSFB Information IE in RANAP: RELOCATION REQUEST message.
Delaying of RAU in case of call directed from LTE (8th bit)

A functionality can be activated where the handling of the RRC: INITIAL DIRECT
TRANSFER for PS CN is delayed until the CS voice RAB is established or the timer is
expired (fixed 8 s) for a user who moved from LTE. Detection of LTE cases is performed
based on:
• existence of pre-redirection info IE in RRC:RRC CONNECTION REQUEST message.
• existence of CSFB Indication IE in RRC: RRC CONNECTION REQUEST message.
Delaying of RAU in case of CSFB HO call from LTE (9th bit)

A functionality can be activated where the handling of the RRC: DIRECT TRANSFER
for PS CN containing the NAS message GMM: ROUTING AREA UPDATE REQUEST is
delayed until the CS voice RAB is established or the timer is expired (fixed 8 s) for a user
who moved from LTE with CSFB PS ISHO procedure. Detection of LTE cases is
performed when there is existence of CSFB Information IE or Cause IE with value CS
Fallback Triggered in the RANAP: RELOCATION REQUEST message.
PRFILE control
parameter values.

Parameter values

0 The functionality is not active.
xxxx xxxx xxXX XXXX The functionality is active. Activation time offset for voice
calls in steps of 10 ms.
xxxx xxxx x0xx xxxx The functionality is not active and the legacy functionality is
used. MBLB is performed in normal way for users moved
from LTE.
xxxx xxxx x1xx xxxx The functionality is active. MBLB is not performed in voice
call setup phase for users moved from LTE.
xxxx xxxx 0xxx xxxx The functionality is not active and the legacy functionality is
used. RAU is not delayed until CS RAB is established for call
redirected from LTE.
xxxx xxxx 1xxx xxxx The functionality is active. RAU is delayed until CS RAB is
established for call redirected from LTE.
xxxx xxx0 xxxx xxxx The functionality is not active and the legacy functionality is
used. RAU is not delayed until CS RAB is established for
CSFB HO call from LTE.
xxxx xxx1 xxxx xxxx The functionality is active. RAU is delayed until CS RAB is
established for CSFB HO call from LTE.

0 n/a
g Note: If the voice call setup time is improved, then all the functionalities can be
activated and ATO value 300 ms is used when the value 0x1DE is set to this parameter.
Dependences
• RAN2172: Multi-band load balancing
• RAN3903: Enhanced MBLB
2.139 002:2282 RU50_SPARE_20

Descriptive name
No UM DL RRC SN skip-over in incoming Inter-RNC HHO when the SN is at 15, which is
the maximum value.
RNC RNC16 5.0
RNC17 1.0
mcRNC mcRNC16 5.0
mcRNC17 1.0

This parameter disables the PR171546 correction. By default, the correction is in use. If,
however, the correction is incompatible with the RNC of other vendor, the correction can
be disabled with this PRFILE parameter.
Normally, in incoming inter-RNC HHO and relocation, the (DL) RRC sequence number is
incremented in Nokia RNC by 1 (or 2) in addition to the fact that the first used value must
be bigger than the value received in the RRC container (which means incrementation by
1 since the RRC container has the values, which were the latest sent to the UE). For
example, if RRC container includes (DL) SN = 3, then Nokia RNC uses next value 5: it
skips over the value 4.
However, this skip-over can be problematic if the incoming sequence number is the
value 15 (the maximum value, which means that rollover to a smaller value is about to
happen) if the RNC does not send messages through this channel to the UE before the
call moves to still another RNC through a UE-not-involved relocation (so that the RNC’s
and the UE’s sequence numbers are not thus synchronized, and the ambiguity is thus
not dissolved before the UE-not-involved relocation), and if there is a security mode
control procedure executed where integrity is reconfigured. In this case, the relocation
and integrity activation of UM DL would happen simultaneously when the relocation UMI
(UTRAN MOBILITY INFORMATION message) is sent in the target RNC. The problem
can happen especially with the UM channel (SRB1) because not many messages are
sent through that channel. The problem does not occur if, instead of incoming HHO, the
call starts with an incoming UE-not-involved relocation since, in that case, the UM
channel is already used to send the relocation UMI. If the call starts with RRC connection
setup or incoming ISHO, then there is no ambiguity either. In the problem case, it may be
ambiguous (subject to interpretation of the RRC specification) if the HFN should be
incremented or not when the relocation UMI is handled in the target RNC and the UE
(this UMI message uses the UM channel).
The ambiguity does not arise in the problematic incoming HHO case either if the RNC
does not do the additional UM DL RRC SN incrementation in the problematic case where
SN is equal to 15. If the correction is present, then, if the UM DL channel was not used,
the UM DL RRC SN = 15 in the outgoing relocation RRC container. This is the pronto
correction and is compatible in Nokia-Nokia relocations/handovers. Otherwise, if the
different handling in this case causes problems in relocations/inter-RNC-HHO’s with
other vendor RNCs, then the correction can be disabled through this PRFILE parameter.
In that case, Nokia RNC makes the additional incrementation of the UM DL RRC SN
even in the case when SN is equal to 15 in incoming inter-RNC HHO so that it would
skip over one value. In this case, the UM DL RRC SN would be 0 in the outgoing
relocation RRC container if the UM DL channel was not used (and the target RNC would
not increment the HFN even if several UE types do).
There is no ambiguity, either, if the SN has the value of 15 if the UM DL is sent before
the next relocation since, in that case, both the RNC and the UE shall unambiguously
increment the HFN.
If ambiguity exists in the relocation (if UE and target RNC have different opinion if the
HFN needs to be incremented in this case), the next relocation fails, and the call is
released. This is because the UE rejects the relocation UMI due to integrity failure.
g Note: This situation is not very common, which should be clear from the description
above.
PRFILE control
parameter values.

Parameter values


0000H n/a
Dependences
n/a
2.140 002:2306 CSFB_WITH_RIM

Descriptive name
CSFB_WITH_RIM
RNC RNC16
RNC18
mcRNC mcRNC16
mcRNC18
PRFILE 002:2306 CSFB_WITH_RIM parameter has switches for the deactivation of
functionalities that can cause capacity problems. This is only a documentation update
and there is no change in the existing functionality of the parameter.
The parameter has switches for:
• inclusion of the SIB11 in System Information Container to LTE
• inclusion of Access Class Restriction Information in the System Information
Container to LTE
• definition of the maximum number of simultaneous RIM messages sent out from the
radio network controller (RNC)
• dynamic uplink (UL) interference for RIM functionality activation
PRFILE control
parameter values.
Parameter values

0000H The functionality is not active:
• SIB11 is never included in the System Information Container to LTE.


• Access Class Restriction Information is included in the System
Information Container to LTE.
• Maximum number of simultaneous RIM messages sent out from the
RNC is 400.
• Dynamic UL Interference for RIM functionality is active, and the
dynamic UL interference time to trigger is 8 s.
0001H–07FFH The functionality is active.
For an alternative setting, set 1H + the wanted Hex value or Hex values:
• For SIB 11 handling:
– 2H: SIB11 is included in the System Information Container
according to the Deferred SIB Reading (not included if Deferred
SIB Reading is ON, included if Deferred SIB Reading is OFF).
– 4H: SIB 11 is always included in the System Information
Container to LTE.
• For Access Class Restriction handling:
– 8H: Access Class Restriction Information is not included in the
System Information Container to LTE.
• For maximum number of simultaneous RIM messages sent out from
the RNC handling:
– 10H: Maximum number of simultaneous RIM messages sent out
from the RNC is 100.
• For dynamic UL interference:
– 40H: Dynamic UL interference functionality is not active.
– 80H–780H: Time to trigger for Dynamic UL interference
functionality is scale from 1 seconds to 15 seconds (4 bits).

0000H n/a
Dependences
n/a
2.141 002:2345 PWSM_CANCEL_ENABLED

Descriptive name
PWSM cancellation in case of BTS HW failure.

A new functionality has been introduced in feature RAN955 Power Saving Mode for BTS
(PWSM), enabling the automatic reactivation of cells shut down by PWSM if an active
cells is disabled by BTS. This helps to maintain service levels in case of BTS failures.
PRFILE parameter 002:2345 PWSM_CANCEL_ENABLED controls whether the
RAN955 PWSM functionality is prevented in scenarios where BTS indicates a “disabled”
value for the operational state of a cell.
PRFILE control
parameter values.
Parameter values

0001H The change is active. The PWSM functionality is prevented.
0000H The change is inactive. The PWSM functionality is not prevented.

0000H n/a
Dependence
RAN955 Power Saving Mode for BTS
2.142 002:2388 CTRL_MAINT_SPARE_01

Descriptive name
Subscriber-specific deactivation of the CS call setup related accelerated procedures
RNC RNC18 onwards
mcRNC mcRNC18 onwards
PRFILE 002: 2388 CTRL_MAINT_SPARE_01 parameter is a switch for deactivating
the RAN3376: Accelerated Voice Setup CS call setup-related procedures. The switch is
subscriber-specific, that is, subscriber A (MOC) and subscriber B (MTC) exist for the
following accelerated CS call setup procedures:
• Accelerated security mode command procedure
• Accelerated RAB assignment procedure

The default value of the parameter is 0, where the accelerated procedures are used for
both subscriber A (MOC) and subscriber B (MTC).
PRFILE control
Parameter values

0H Accelerated security mode command and accelerated RAB assignment
(including late assignment for subscriber B) procedures are used for both
subscriber A (MOC) and subscriber B (MTC).
1H Accelerated security mode command procedure is deactivated for
subscriber A.
2H Accelerated RAB assignment procedure is deactivated for subscriber A.
3H Both accelerated procedures are deactivated for subscriber A.
10H Accelerated security mode command procedure is deactivated for
subscriber B.
20H Accelerated RAB assignment procedure, including late assignment
procedure, is deactivated for subscriber B.
30H Both accelerated procedures are deactivated for subscriber B.
g Note: Combination is also allowed. Subscriber A value + subscriber B value is allowed,
for example, both accelerated procedures are deactivated for subscriber A (3H) +
accelerated security mode command procedure is deactivated for subscriber B (10H) =
13H.
Maximum value 33H is not recommended as it deactivates all the
RAN3376: Accelerated Voice Setup accelerated setup functionalities.

0000H n/a
Dependences
RAN3376: Accelerated Voice Setup
2.143 002: 2398 CTRL_MAINT_SPARE_02

Descriptive name
Maximum wait time for initiating the re-establishment during CS call setup
RNC RNC18
mcRNC mcRNC18

During the wait time, the radio network controller (RNC) expects the RRC:CELL
UPDATE from the user equipment (UE) after the UE has lost its RRC connection during
the RB SETUP procedure. When the RNC receives the RANAP: IU RAB
ASSIGNMENT REQUEST from CS core, the timer is started.
PRFILE control
parameter values.
Parameter values

0000H The default value is 8 s.
0008H-0014H The minimum value is 8 s and the maximum value is 20 s.

0000H n/a
Dependences
n/a

Descriptive name
Radio quality threshold values for using RAN3376: Accelerated Voice Setup
RNC RNC18
mcRNC mcRNC18
PRFILE 002:2399 CTRL_MAINT_SPARE_03 parameter can be used to modify the
required radio conditions for triggering the RAN3376: Accelerated Voice Setup signaling.
The parameter defines the minimum CPICH RSCP and CPICH EcNo precondition levels
for using RAN3376: Accelerated Voice Setup.
Table 9 CPICH EcNo Mapping Table
Reported value from UE Measured quantity value Unit
(dec)
CPICH_Ec/No _01 -24 ≤ CPICH Ec/Io < -23.5 dB
CPICH_Ec/No _02 -23.5 ≤ CPICH Ec/Io < -23 dB

Table 9 CPICH EcNo Mapping Table (Cont.)
(dec)
Table 10 CPICH RSCP Mapping Table
(dec)
CPICH_RSCP_LEV _3 -113 ≤ CPICH RSCP < -112 dBm

Table 10 CPICH RSCP Mapping Table (Cont.)
(dec)

Table 10 CPICH RSCP Mapping Table (Cont.)
(dec)
PRFILE control
Parameter values

0000H This is the default value where the precondition of -113 dBm CPICH
RSCP and -24 dB CPICH EcNo are used as required minimum levels
when CPICH RSCP or CPICH EcNo measurements are available during
voice call setup. Even if RSCP or EcNo values are not available,
accelerated voice setup is used.
g Note: With the default value, the required radio conditions are so
low that RAN3376: Accelerated Voice Setup signaling is likely to
trigger.
2H-5BCBH The following are the bits value:
• bit 0 = 1, values other than the default value are used.
• bit 1 to bit 6, where CPICH EcNo is other than the default value
(integer, scale from 1 to 37 where minimum 1 = -24 dB and maximum
37 = -6 dB).
• bit 7 to bit 13, where CPICH RSCP is other than the default value
(integer, scale from 3 to 55 where minimum 3 = -113 dBm and
maximum 55 = -61 dBm).


• bit 14 has the following available values:
– 0, where the accelerated voice setup is used even if the CPICH
RSCP or CPICH EcNo values are not available and which is the
default value.
– 1, where the accelerated voice setup is not used if the CPICH
RSCP or CPICH EcNo values are not available.

0000H 0000H-5BCBH n/a
Dependences
n/a

Descriptive name
High Rate HD Voice usage needs to be controlled according to UE release valid for
releases and maintenance packets
RNC RNC18 onwards
PRFILE 002:2400 CTRL_MAINT_SPARE_04 parameter is used for enabling and
disabling RAN3372: High Rate HD Voice based on user equipment (UE) release.
PRFILE control
parameter values.
Parameter values

0000H This is the default value. This is allowed for all release UEs.
0001H This is allowed for Release 6 and newer UEs.
Other values These are allowed for all release UEs.


0000H n/a
Dependences
n/a

Descriptive name
AACR level adjustment based on eMEH DMHU value
RNC RNC17 5.0
RNC18
mcRNC mcRNC17 5.0
mcRNC18
This parameter controls the following values used in automatic access class restriction
(AACR) level adjustment based on enhanced mass event handler (eMEH) dynamic
HSUPA user limitation (DMHU) value:
EMEH_AACR_DMHU_E This controls the activation of AACR level adjustment
NABLED (Bit0) based on eMEH DMHU value: Range 0…1, step 1,
default 0. Value 0 indicates that AACR level adjustment
based on eMEH DMHU is enabled. Value 1 indicates that
it is disabled.
EMEH_AACR_DMHU_S This controls the synchronization of AACR level
YNCH (Bit1) adjustments in RNC: Range 0…1, step 1, default 0. Value
0 indicates that AACR level adjustments are not
synchronized in RNC. Value 1 indicates that AACR
adjustments are synchronized in RNC.
EMEH_AACR_HSUPA_U This controls the usage of high-speed uplink packet
SERS_TRIGGER (Bit2) access (HSUPA) user amount as criterion to decrease
AACR level: Range 0…1, step 1, default 0. Value 0
indicates that HSUPA user amount is not used as criterion
to decrease AACR level. Value 1 indicates that HSUPA
user amount is used as criterion to decrease AACR level.
EMEH_AACR_DMHU_2S This controls the AACR level increase by two steps when
TEP (Bit3) the DMHU value is in DMHU range in next AACR level:
Range 0…1, step 1, default 0. Value 0 indicates that
AACR level increase by two steps is not applied. Value 1
indicates that AACR level increase by two steps is
applied.
EMEH_AACR_DMHU_G This defines the guard time between AACR level
UARD_TIME adjustment and start of next AACR level verification:
(Bit8…Bit15) Range 10...180 seconds, step 10 seconds, default 60
seconds if all bits 0. Guard time is recommended to be at
least 1.5 times the length of SYSTEM INFORMATION 3
update period of AACR. The RNAC-
AutoACRLevelUpdInt parameter indicates the

Automatic Access Class Restriction Level Update
Interval. If SYSTEM INFORMATION 3 message has been
recently updated and new update is needed (for example,
because of AACR adjustment), the update is made after
45 seconds.
PRFILE control
parameter values.
Parameter values

0000H The effects are the following:
• For EMEH_AACR_DMHU_ENABLED, AACR level adjustment based
on eMEH DMHU is enabled.
• For EMEH_AACR_DMHU_SYNCH, AACR level adjustments are not
synchronized in radio network controller (RNC).
• For EMEH_AACR_HSUPA_USERS_TRIGGER, HSUPA user amount
is not used as criterion to decrease AACR level.
• For EMEH_AACR_DMHU_2STEP, AACR level increase by two steps
is not applied.
• For EMEH_AACR_DMHU_GUARD_TIME, default is 60 seconds.
• For EMEH_AACR_DMHU_SYNCH, AACR adjustments are
synchronized in RNC.
is not applied.
is used as criterion to decrease AACR level.
is not applied.


is not applied.
is applied.
000AH The effects are the following:
is applied.
000CH The effects are the following:
is applied.
000EH The effects are the following:
is applied.
xx01H For EMEH_AACR_DMHU_ENABLED, AACR level adjustment based on
eMEH DMHU is disabled.


xx0BH For EMEH_AACR_DMHU_ENABLED, AACR level adjustment based on
xx0DH For EMEH_AACR_DMHU_ENABLED, AACR level adjustment based on
xx0FH For EMEH_AACR_DMHU_ENABLED, AACR level adjustment based on
01xxH–12xxH Values define EMEH_AACR_DMHU_GUARD_TIME value 10-180.

0000H n/a
Dependences

Descriptive name
RNC RNC17 5.0
RNC18
mcRNC mcRNC17 5.0
mcRNC18
EMEH_AACR_DMHU_IN This defines high-speed uplink packet access (HSUPA)
IT (Bit0…Bit7) user limit value of DMHU, when AACR limit initially
triggers: Range 1 … 100, step 1, default 70 if all bits 0.
Used value in algorithms is interpreting the PRFILE value
as percentage (70 corresponds to 70%, that is, 0.7).
EMEH_AACR_DMHU_H This defines hysteresis from DMHU minimum limit to
YST_RATIO DMHU maximum level: Range 1…100, step 1, default 20
(Bit8…Bit15) if all bits 0. Used value in algorithms is determined by
dividing the PRFILE value by 100 (indicates the
percentage).
PRFILE control

parameter values.
Parameter values

• For EMEH_AACR_DMHU_INIT, default is 70.
• For EMEH_AACR_DMHU_HYST_RATIO, default is 20.
0001H–0064H The values define EMEH_AACR_DMHU_INIT value 1-100 and default for
EMEH_AACR_DMHU_HYST_RATIO.
01xxH–64xxH The values define EMEH_AACR_DMHU_HYST_RATIO value 1-100.

0000H n/a
Dependences

Descriptive name
RNC RNC17 5.0
RNC18
mcRNC mcRNC17 5.0
mcRNC18
EMEH_AACR_DMHU_H This defines minimum high-speed uplink packet access
YST_MIN (Bit0…Bit7) (HSUPA) user amount difference between maximum and
minimum DMHU limits: Range 1…20, step 1, default 10 if
all bits 0.
EMEH_AACR_DMHU_H This defines maximum HSUPA user amount difference
YST_MAX (Bit8…Bit15) between maximum and minimum DMHU limits: Range
5…40, step 1, default 20 if all bits 0.
PRFILE control
parameter values.
Parameter values


• For EMEH_AACR_DMHU_HYST_MIN, default is 10.
• For EMEH_AACR_DMHU_HYST_MAX, default is 20.
0001H-0014H Values define EMEH_AACR_DMHU_HYST_MIN value 1-20 and default
for EMEH_AACR_DMHU_HYST_MAX.
05xxH-28xxH Values define for EMEH_AACR_DMHU_HYST_MAX value 5-40.

0000H n/a
Dependences

Descriptive name
RNC RNC17 5.0
RNC18
mcRNC mcRNC17 5.0
mcRNC18
EMEH_AACR_DMHU_H This defines the time during which the criteria for AACR
YST_INC (Bit0…Bit7) level increase because DMHU has to be continuously
fulfilled: Range 5…240 seconds, step 5 seconds, default
30 seconds if all bits 0.
EMEH_AACR_DMHU_H This defines the time during which the criteria for AACR
YST_DEC (Bit8…Bit15) level decrease because DMHU has to be continuously
fulfilled: Range 5…240 seconds, step 5 seconds, default
30 seconds if all bits 0.
PRFILE control
parameter values.
Parameter values



• For EMEH_AACR_DMHU_HYST_INC, default is 30 seconds.
• For EMEH_AACR_DMHU_HYST_DEC, default is 30 seconds.
0001H–0030H Values define EMEH_AACR_DMHU_HYST_INC value 5-240 and default
for EMEH_AACR_DMHU_HYST_DEC.
01xxH–30xxH Values define EMEH_AACR_DMHU_HYST_DEC value 5-240.

0000H n/a
Dependences

Descriptive name
RNC RNC17 5.0
RNC18
mcRNC mcRNC17 5.0
mcRNC18
EMEH_AACR_MIN_HSU This defines the cell level limit for high-speed uplink
PA_USER_LIMIT packet access (HSUPA) maximum user amount indicating
(Bit0…Bit7) the usage of AACR adjustment based on DMHU value in
cell: Range 1…128, step 1, default 40 if all bits 0.
EMEH_AACR_DMHU_MI This defines the absolute minimum DMHU value for
N_LIMIT_START AACR level 0. This value is used in determining the
(Bit8…Bit15) minimum DMHU values for other AACR levels. Range
0...128, step 1, default value 0 indicating that the absolute
value is disabled.
PRFILE control
parameter values.
Parameter values



• For EMEH_AACR_MIN_HSUPA_USER_LIMIT, default is 40.
• For EMEH_AACR_DMHU_MIN_LIMIT_START, the absolute value is
disabled.
0001H–0080H Values define EMEH_AACR_MIN_HSUPA_USER_LIMIT value 1-128 and
disable the absolute value.
01xxH–80xxH Values define EMEH_AACR_DMHU_MIN_LIMIT_START value 1-128.

0000H n/a
Dependences

Descriptive name
Control of T302 adjustment enabling or disabling and the functionality that ignores the
first TVM if T302 adjustment is enabled
RNC RNC19
mcRNC mcRNC19
The parameter controls the enabling or disabling of T302 adjustment. If T302 adjustment
is enabled, the parameter also controls the functionality that ignores the first traffic
volume measurement (TVM).
PRFILE control
parameter values.
Parameter values

0000H T302 adjustment and Cell_FACH avoidance are not used. First TVM is not
ignored.
0001H T302 adjustment and Cell_FACH avoidance are used. First TVM is not
ignored.
0003H T302 adjustment and Cell_FACH avoidance are used. First TVM is
ignored.

0000H n/a

Dependences

Descriptive name
Control of T302 value used if T302 adjustment is allowed
RNC RNC19
mcRNC mcRNC19
If T302 adjustment is allowed, the parameter controls the T302 value used.
PRFILE control
parameter values.
Parameter values

0000H Adjusted value of T302 is 8 seconds.

0000H n/a
Dependences
n/a

Descriptive name
Control of enabling or disabling the functionality that ignores the first TVM after the active
NRT user is released
RNC RNC19
mcRNC mcRNC19

This parameter controls the enabling or disabling of the functionality that ignores the first
traffic volume measurement (TVM) after an active non-real time (NRT) user is released.
PRFILE control
parameter values.
Parameter values

0000H First TVM is not ignored.
0001H First TVM is ignored.

0000H n/a
Dependences
RAN3110: HSPA Queuing and Resource Rotation with QoS
RAN3388: Dynamic Voice Call Prioritization
RAN3341: Guaranteed Voice Calls in High Load

Descriptive name
Control of Mute Call Prevention during inter-RNC HHO, UE not involved relocations, and
ISHO from 2G and 4G
RAN2961: Load Based AMR Code Selection Causing Mute Call feature delays sending
the rate control requests of the RRC: Transport Format Combination
Control message from Core NW to user equipment (UE) until CONNECT ACK is
received from UE.
In certain intra-RNC hard handovers, UE not involved relocations, and ISHO from 2G
and 4G, RNC has no information whether the UE has already sent the CONNECT ACK
or not. In return, the UE is not downgraded to a lower set of 5.9 kbit/s but remains at 12.2
kbit/s in NB AMR 12.2 kbit/s.
The fault was corrected by adding CONNECT ACK handling in RAN2961: Load Based
AMR Code Selection Causing Mute Call during the intra-RNC hard handover,
relocations, as well as 2G and 4G ISHO cases. When the correction is activated, RNC

assumes that CONNECT ACK is sent by the UE and forwards transport format
combination control (TFCC) commands to it. The correction is activated by this PRFILE
parameter and is OFF by default.
The bits are described as follows:
• bit 0: Rate Control forwarding in UE not involved relocations
When activated with bit 0 value 1, RNC assumes that the UE has sent the
CONNECT ACK. RNC then forwards the rate control commands to the UE. When
deactivated with bit 0 value 0 (default), RNC assumes that that no CONNECT ACK is
received from the UE. In return, RNC does not forward the rate control requests to
the UE (legacy functionality) unless CONNECT ACK is received after the relocation.
• bit 1: Rate Control forwarding in inter-RNC HHO
deactivated with bit 1 value 0 (default), RNC assumes that no CONNECT ACK is
received from the UE. In return, RNC does not forward rate control requests to the
UE (legacy functionality) unless CONNECT ACK is received after the inter-RNC
HHO.
• bit 2: Rate Control forwarding after 2G ISHO
UE (legacy functionality) unless CONNECT ACK is received after the 2G ISHO.
• bit 3: Rate Control forwarding after 4G ISHO
UE (legacy functionality) unless CONNECT ACK is received after the 4G ISHO.
Parameter values

0000H The functionalities are OFF.
0001H Rate control forwarding after UE not involved relocations is activated.
0002H Rate control forwarding after inter-RNC HHO is activated.
0004H Rate control forwarding after 2G ISHO is activated.
0008H Rate Control forwarding after 4G ISHO is activated.
g Note: Combinations of the values are allowed.

0000H (By default, new 000FH (It is recommended to n/a
functionalities are not activated activate all functionalities.)
for forwarding rate control
commands from RNC to UE
after UE not involved
relocation, inter-RNC HHO,


ISHO from 2G, and ISHO from
4G.)
Dependences

Descriptive name
Limitation of STATUS messages in DL RRC buffer
If there are more STATUS messages in the buffer than what 02:2414
CTRL_MAINT_SPARE_17 PRFILE limitation indicates when the correction is activated,
the following occurs:
• If the user equipment (UE) has PS connection only, the UE-specific radio resource
controller (RRC) entity moves the UE to idle without sending the buffered STATUS
messages to this UE.
• If the UE has CS connection, the correction does not trigger.
This correction to a specific DL buffer overload situation is valid for releases and
maintenance packets.
For more information, see CN RNC17_329.
PRFILE control
parameter values.
Parameter values

0000H Correction is activated by default (minimum value). RRC limits the buffer
size of STATUS messages in DL NAS signaling buffer (SRB3 and SRB4)
to 10.
0005H–000FH The maximum value is 000FH (15 DEC). Correction is activated. RRC
limits the buffer size of STATUS messages in DL NAS signaling buffer
(SRB3 and SRB4) to the indicated value.
0001H Correction is not active.

0000H 0002H-0004H

Dependences
n/a

Descriptive name
AMR load check period
RNC RNC18 onwards
PRFILE 002:2417 CTRL_MAINT_SPARE_20 parameter is used for configuring the
following functionalities for features RAN580: Load Based AMR Mode, RAN3372: High
Rate HD Voice, and RAN1838: Load Based HD Voice Rate:
Faster Radio network controller (RNC) checks the cell load status triggers
adaptive (power load, code load, and transmission load) periodically in each
multi-rate cell. The load checking period is 10 s. By setting PRFILE 002:2417
(AMR) load CTRL_MAINT_SPARE_20 parameter to value 1H, the AMR load
check period check period value 5 s is used in RNC. The 5 s value is applicable for
features RAN580: Load Based AMR Mode, RAN3372: High Rate HD
Voice, and RAN1838: Load Based HD Voice Rate. With the 5 s load
check period, RNC can react faster to changes in the cell load status.
In Nokia internal testing with RAN3372: High Rate HD Voice, the
lower load check period improved the call setup success rate KPIs.
Fast Ptx load Periodical Ptx load check can be reduced to 1 s by setting PRFILE
check period 002:2417 CTRL_MAINT_SPARE_20 parameter to value 3H.
When the 1 s Ptx load check period is used, Ptx powers might
prevent allocation of high rate codecs. Codec downgrading might be
triggered at the next AMR load check period. Code load and Iub loads
are checked by 5/10 s period. The 1 s value is applicable for features
RAN580: Load Based AMR Mode, RAN3372: High Rate HD Voice,
and RAN1838: Load Based HD Voice Rate.
Ptx load Ptx load checks can be further enhanced with averaging the load
averaging measurements. By setting PRFILE 002:2417
CTRL_MAINT_SPARE_20 parameter to value 4H, one second
averaging window is used. With value 8H, two seconds averaging
window is used. With the other values other than 4H or 8H, the Ptx
load is averaged with period defined by parameters
WinAcRabSetupDL * SchedulingPeriod. With the default values of
these parameters, the Ptx averaging window is 500 ms. The 1-2 s
value is applicable for features RAN580: Load Based AMR Mode,
RAN3372: High Rate HD Voice, and RAN1838: Load Based HD
Voice Rate.
It is recommended to use value BH with RAN3372: High Rate HD
Voice feature. Value BH activates a 5 s AMR load check period with 1
s Ptx load check period and 2 s Ptx load averaging window.

The parameter is also used in configuring the following functionalities for feature
RAN3388: Dynamic Voice Call Priorization:
DMHD load RAN3388: Dynamic Voice Call Priorization feature sets RAN3372: High
ratio Rate HD Voice load state in the cell when DMHD ≤
DynVCPMinHSDPAUsers + ( Z * ( MaxNumberOfHSDPAUsers -
DynVCPMinHSDPAUsers )), where:
DMHD is the dynamic maximum number of high-speed downlink packet
access (HSDPA) users
Z is the multiplier defined by values 002x – 00Ex of PRFILE 002:2417
CTRL_MAINT_SPARE_20 parameter
Table 11 Z multiplier defined by 002:2417
CTRL_MAINT_SPARE_20
Value Multiplier
000xH 0.80 (default value used when PRFILE
value is xx0x and RAN3388: Dynamic
Voice Call Priorization activation bit is
enabled)
001xH 0.00002xH
002xH 0.05
003xH 0.10
004xH 0.15
005xH 0.20
006xH 0.25
007xH 0.30
008xH 0.40
009xH 0.50
00AxH 0.60
00BxH 0.70
00CxH 0.80
00DxH 0.90
00ExH 1.00
DMHD RAN3388: Dynamic Voice Call Priorization sets RAN3372: High Rate HD

overload Voice overload state in the cell when DMHD ≤ DynVCPMinHSDPAUsers
ratio + ( X * ( MaxNumberOfHSDPAUsers - DynVCPMinHSDPAUsers )),
where:
Multiplier X is defined by PRFILE 002:2417
CTRL_MAINT_SPARE_20 parameter

Table 12 Multiplier X defined by 002:2417
CTRL_MAINT_SPARE_20
Value Multiplier
00xxH 0.25 (default value used when PRFILE
value is 00xxH and RAN3388:
Dynamic Voice Call Priorization
activation bit is enabled)
01xxH 0.00
02xxH 0.05
03xxH 0.10
04xxH 0.15
05xxH 0.20
06xxH 0.25
07xxH 0.30
08xxH 0.40
09xxH 0.50
0AxxH 0.60
0BxxH 0.70
0CxxH 0.80
0DxxH 0.90
0ExxH 1.00
PRFILE control
Parameter values

0H Legacy 10 s AMR load check period is used.
1H Faster AMR load check period 5 s is used.
2H Fast Ptx load check period 1 s is used.
4H Ptx load averaging of 1 s is used.
8H Ptx load averaging of 2 s is used.
1xH–FxH These define the DMHD load ratio.
1xxH–FxxH These define the DMHD overload ratio.
g Note: Combination of the values above is allowed.


0H It is recommended to use n/a
value BH with RAN3372: High
Rate HD Voice feature. Value
BH activates the 5 s AMR load
check period with 1 s Ptx load
check period and 2 s Ptx load
averaging window.
Dependences
n/a

Descriptive name
Automatic recovery of RNC RNW initialization program block after failed hand creation
attempts
This parameter is used to activate the automatic recovery of radio network controller
(RNC) radio network (RNW) initialization program block from hand creation unsync
issue, that is, if this parameter is enabled then the RNC will automatically restart the SP
side RNW initialization program block after an X number (defined by this parameter) of
failed hand creation attempts.
PRFILE control
Parameter values

0000H The functionality is disabled. This is the default value.
0001H-FF00H The functionality is enabled. The value defines number X = limit value for
hand creation failures. SP REZINI process restarts after an X amount
(defined by PRFILE parameter) of failed hand creation attempts. The
recommended value is hex value 0A (decimal value10).

0000H 000A (decimal value of 10) n/a
Dependences
n/a


Descriptive name
E-DCH maximum bit rate calculation
RNC18 1.0 onwards
mcRNC18 1.0 onwards
PRFILE 002:2421 CTRL_MAINT_SPARE_24 parameter is used for controlling
enhanced dedicated transport channel (E-DCH) maximum bit rate-related calculation. E-
DCH maximum bit rate is calculated from the maximum uplink bit rate received from
Core NW by multiplying the rate by RNHSPA FactorEDCHMaxBitRate parameter.
When the signaling radio bearer (SRB) is mapped on E-DCH, the SRB rate is also added
to the E-DCH maximum bit rate.
When PRFILE 002:2421 CTRL_MAINT_SPARE_24 parameter has a value 01H, the
SRB rate is not added to the E-DCH maximum bitrate.
g Note: In case of standalone SRB on high-speed packet access (HSPA), the HSPA
maximum bitrate includes the SRB rate. This only applies to WCDMA17 5.2
, WCDMA18 2.0, and later releases.
PRFILE control
parameter values.
Parameter values

0000H By default, the SRB rate is added to the E-DCH maximum bit rate.
0001H SRB rate is not added to the E-DCH maximum bit rate.

0000H n/a
Dependences
When RNHSPA FactorEDCHMaxBitRate has a special value (0), the E-DCH
maximum bit rate is not restricted and PRFILE 002:2421 CTRL_MAINT_SPARE_24
parameter value has no effect.


Descriptive name
Counter updates for inter-RNC intra-frequency HHOs
RNC RNC19
mcRNC mcRNC19
The objective of this functionality is for the operator to be able to monitor the inter-RNC
intra-frequency hard handover (HHO) per neighbouring cell relations. When the inter-
RNC soft handover (SHO) is not supported (for example, when the Iur is missing or the
SHO is not activated over Iur) and when a call moves from one RNC to another, the call
performs an HHO.
In the legacy system, M1013 measurement counters indicate SHO events between cell
neighbour pairs. SHO CPICH EcNo differences and RSCP levels are also updated. In
the new functionality, M1013 counters are also updated because of the inter-RNC intra-
frequency HHOs.
PRFILE control
parameter values.
Parameter values

X00H This is the default value. The M1013 counters are not updated because of
inter-RNC intra-frequency HHOs.
X01H The M1013 counters are updated also because of inter-RNC intra-
frequency HHOs.

0000H n/a
Dependences
M1013 counters are controlled by RAN189: Automatic Definition of Neighbouring Cells
or RAN1189: CPICH Ec/No Difference Counters per Cell Pair licenses. M1013 counters
are updated just when features RAN189: Automatic Definition of Neighbouring Cells and
RAN1191: Detected Set Reporting and Measurements are active.

Descriptive name
Number of reported cells in CPICH Ec/No and RSCP measurement for MDT

RNC RNC19
mcRNC mcRNC19
This parameter controls the maximum number of monitored set cells (in addition to active
set cells) that can be reported in the periodic CPICH Ec/No and RSCP measurement for
UE Periodic Measurement Report (also known as Minimization of Drive Tests or MDT)
purposes.
PRFILE control
parameter values.
Parameter values

0000H The maximum number of monitored set cells that can be reported in the
measurement report is 2.
0001H The maximum number of monitored set cells that can be reported in the
measurement report is 6.

0000H n/a
Dependences
n/a
2.161 002:2542 IPV6UDP_ZERO_CKSUM

Descriptive name
IPv6 and UDP Checksums for Tunnelled Packets
mcRNC mcRNC19
This PRFILE parameter adds control of IPv6 UDP checksum validation at IuPS interface.
IPv6 and UDP Checksums for Tunnelled Packets relaxes IPv6 UDP checksum
requirement for tunnel protocols, whose header information can be protected on the
"inner" packet being carried. Removing unnecessary IPv6 UDP checksum validation can
improve the IuPS traffic performance.
With this change, for IUPS traffic based on IPv6/UDP, UDP checksum validation is
optional according to the setting of this PRFILE parameter. If this PRFILE parameter is
set to "1", IPv6 UDP packets with zero UDP checksum will be considered as valid
packets without any validation: traffic processing performance for IUPS traffic over
IPv6/UDP will be improved.

If IPv6 based transport is used for IUPS traffic, it is recommended for the operator to
activate this PRFILE parameter: set its value to "1".
PRFILE control
parameter values.
Parameter values

0000H The functionality is not active. IPv6 UDP checksum validation is
mandatory. UDP checksum of all the incoming IPv6 UDP packets shall be
validated. If UDP checksum validation fails, packets shall be dropped.
Zero UDP checksum is always treated as invalid.
0001H The functionality is active. IPv6 UDP checksum validation is optional at
the IuPS interface. Non-zero checksum of all the incoming IPv6 UDP
packets at the IuPS interface (with destination UDP port 2152) shall be
validated. If UDP checksum validation fails, packets shall be dropped.
Zero UDP checksum is always treated as valid without validation.

0001H n/a
Dependences
This PRFILE parameter has no dependencies with other PRFILE parameters.

PRFILE Descriptions Parameter class 007 CALL_CONTROL
3 Parameter class 007 CALL_CONTROL

This class includes parameters that modify call control definitions.
3.1 007:0174 CN_INFORMATION_INFO

Descriptive name
CN Information Info information element for CELL/URA UPDATE CONFIRM
IPA-RNC, mcRNC
At the moment the CN Information Info IE element is added to the RRC:CELL UPDATE
CONFIRM or RRC:URA UPDATE CONFIRM message if the SRNS Relocation is in
question. With PRFILE parameter 007:0174 CN_INFORMATION_INFO the operator
can define if this information element is always included in those messages. A use case
of this functionality may be HomeZone feature purposes.
g Note: For more information on IEs, see 3GPP TS 25.331, section 10.3.1.3.
PRFILE control
parameter values.
Parameter values

0000H CN Information Info IE is always included in the CELL/URA UPDATE
CONFIRM message.
0001H CN Information Info IE is included only during the SRNS relocation (UE
not involved).

0000H n/a
Dependence
n/a
3.2 007:0191 JAPAN_UE_CONTROL

Descriptive name
Special control due to early UEs

Parameter class 007 CALL_CONTROL PRFILE Descriptions
IPA-RNC, mcRNC
PRFILE parameter 007:0191 JAPAN_UE_CONTROL impacts RRC signaling between
RNC and UE, enabling UE special handling functionalities. The first byte of the
parameter controls particular functionalities, and the second byte defines the interruption
time after trigger.
PRFILE control
parameter values.
Parameter values
Second byte First byte Effect

(HEX) (HEX)
000XH 0000H The functionality is not active. No special handling.
0001H • Tx interruption after trigger = Pending time after trigger.
• RNC/RRC never moves NEC-VTX-UE to Cell_FACH-
state. Instead, the RNC moves it directly to Idle state
(DCH->Idle).

• RNC/RRC sends ActivationTime to all UEs in PS 0/0
RB setup. This is due to NEC-VTB-UE behavior.

• NEC-VTX-UE is moved directly to Idle state.
RB setup.
008XH 0081H • RNC/RRC never sends Tx interruption after trigger to

UE.
0082H • RNC/RRC never sends Tx interruption after trigger to

UE.
RB setup.
0083H • RNC/RRC never sends Tx interruption after trigger to

UE.
RB setup.
009XH - 00FXH 00[9..F]1H • Tx interruption after trigger is set between 0-6. It is

independent of Pending time after trigger.

Second byte First byte Effect

(HEX) (HEX)
00[9..F]2H • Tx interruption after trigger is set between 0-6. It is
RB setup.
00[9..F]3H • Tx interruption after trigger is set between 0-6. It is

RB setup.

0000H 0000H - 00F3H n/a
Dependence
n/a
3.3 007:0195 RN21_MAINT_003

Descriptive name
SHO Branch addition during CM starting phase
IPA-RNC, mcRNC
PRFILE parameter 007:0195 RN21_MAINT_003 controls the handling of: branch
additions, so that one of the following methods is used.
1. Default setting. The branch addition is handled immediately, also during CM start.
2. Branch addition is ignored during CM start and it responds to HA3 by a parallel
procedure failure.
3. Branch addition is saved during CM start. Branch addition is handled when the CM
starting timer expires.
This functionality is available from RN2.1 CD2.0 onwards
PRFILE control
parameter values.
Parameter values


0000H Default functionality.
0001H Branch addition is ignored during CM start. It responds to HA3 by a
parallel procedure failure.
0002H Branch addition is saved during CM start. Branch addition is handled
when the CM starting timer expires.

0000H n/a
Dependence
n/a
3.4 007:0208 RNC_MAINT_001

Descriptive name
Cell Recovery Improvement
IPA-RNC, mcRNC
PRFILE parameter 007:0208 RNC_MAINT_001 impacts features RAN1810: Sleeping
Cell Improvement and RAN1823: Recovery Logging Improvement. These RN3.0 CD3.0
features improve on RN2.2 feature RAN1302: Non-Performing Cell Recovery.
PRFILE control
parameter values.
Parameter values

0000H 0000H - FF00H n/a
Dependence

3.5 007:0227 RN30_MAINT_004

Descriptive name
RNC does not have relocation inhibition timer for ping pong relocations in Cell_FACH
IPA-RNC: RN7.0 5.0, RN8.1 onwards
This is a new PRFILE based workaround for 3rd party SGSN problem. When UE in one
RNC area moves to another RNC in a non-Cell_DCH state, the Serving RNC initiates
SRNS relocation procedure. If the UE moves back to the previous Serving RNC area
very soon after SRNS relocation, the new Serving RNC starts a new relocation
procedure. This kind of ping-pong relocations between the RNCs are supported in Nokia
RAN, but all other vendors’ SGSNs cannot handle frequent relocations which results in
their failures.
To prevent such problems, a new PRFILE-based inhibition timer has been implemented
into Nokia RNC as a workaround for SGSN problem. The introduction of configurable
relocation inhibition timer allows to prevent the ping pong relocations based on UE
mobility.
The new timer is controlled PRFILE parameter 007:0227 RN30_MAINT_004. By
default (value 0000H), the timer is not used.
The PRFILE parameter for the timer value can be calculated in the following manner:
PRFILE value = decimal value of target timer timer value in milliseconds / 10
g Note: Note that in IPA-RNC the parameter value needs to be given in HEX format. For
example, timer value of 10s (10000ms) translates into the following: PRFILE value =
10000 / 10 = 1000d = 03E8H
PRFILE control
parameter values.
Parameter values

0001H - 03E8H The functionality is active.

0000H n/a
Dependence

n/a
3.6 007:0238 RN30_MAINT_015

Descriptive name
BSIC verification in case of PS NRT calls
IPA-RNC, mcRNC
From RN3.0 ED2.1 onwards, a new functionality is added to solve possible problems
with PS ISHO due to the GSM radio network planning, that is, overlapping GSM
frequencies and missing ADJG definitions, which can cause unsuccessful handovers
from WCDMA to GSM if BSIC of target cell is not verified before triggering the handover
which can cause a decrease of the success rate in ISHO 3G to 2G for PS calls (in case
of this kind of network configuration).
The problem is corrected with a better network planning, where the inter-system
adjacencies are better defined. This problem can be also avoided with a new RNC
implementation, where BSIC is always verified also in case of PS NRT calls. That is
against current RNC specifications, so the implementation is configurable with PRFILE
parameter 007:0238 RN30_MAINT_015.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
3.7 007:0239 RN30_MAINT_016

Descriptive name
Non-performing cell recovery improvement

IPA-RNC, mcRNC
This change refers to two new features: RAN1810: Sleeping Cell Improvement and
RAN1823: Recovery Logging Improvement. These features can be considered as
improvements to RAS05.1 ED feature - RAN1302: Non-Performing Cell Recovery.
These features can be activated from RN3.0 CD3.0 onwards.
PRFILE parameter 007:239 RN30_MAINT_016 defines the percentage of successful
RRC connection setups out of the monitoring window size dictated by the 007:0242
RN30_MAINT_019 parameter. The procedure is considered successful if the “RRC
connection setup” message is sent and the “RRC connection setup complete” message
is received. The procedure is considered unsuccessful if the “RRC connection setup"
message is sent, but “RRC connection setup complete” message is not received. The
parameter value range is 1 to 100.
PRFILE control
parameter values.
Parameter values

0001H - 0064H The functionality is active. The percentage of successful RRC connection
setups is set between 1 and 100, with a step of one unit.

0000H n/a
Dependence
007:0242 RN30_MAINT_019
3.8 007:0240 RN30_MAINT_017

Descriptive name
IPA-RNC, mcRNC

improvements to RAS05.1 ED feature - RAN1302: Non-Performing Cell Recovery. The
features can be activated from RN3.0 CD3.0 onwards.
Constant radio link failure monitoring and the corresponding recovery action triggering is
configured with PRFILE parameter 007:240 RN30_MAINT_017. This parameter
indicates the number of consecutive failed RRC connection setups after which the non-
performing cell recovery is started.
PRFILE control
parameter values.
Parameter values

0000H 0000H - FF00H n/a
Dependence
3.9 007:0241 RN30_MAINT_018

Descriptive name
IPA-RNC, mcRNC
The change refers to the following features that are activated from RN3.0 CD3.0
onwards, and which are considered as improvements to RAN1302: Non-Performing Cell
Recovery RAS05.1 ED feature:

PRFILE control

parameter values.
Parameter values

0000H 0000H-FF00H n/a
Dependence
For more information, see Features RAN1302, RAN1810 and RAN1823: Non-Performing
Cell Recovery, Feature Activation Manual.
3.10 007:0242 RN30_MAINT_019

Descriptive name
IPA-RNC, mcRNC
improvements to RAS05.1 ED feature - RAN1302: Non-Performing Cell Recovery. The
features can be activated from RN3.0 CD3.0 onwards.
PRFILE parameter 007:0242 RN30_MAINT_019 defines the size of the FACH RRC
connection success ratio window, that is, the number of consecutive events over which
the success ratio is calculated. The parameter value ranges from 1 to 10000.
PRFILE control
parameter values.
Parameter values

0001H - 2710H The FACH RRC connection success ratio window is set between 1 and
10000, with a step of one unit.


0000H n/a
Dependence
3.11 007:0243 RN30_MAINT_020

Descriptive name
IPA-RNC, mcRNC
The change refers to the following features that are activated from RN3.0 CD3.0
onwards, and which are considered as improvements to RAN1302: Non-Performing Cell
Recovery RAS05.1 ED feature:
After the restart fo the RNC, the non-performing cell recovery block time is defined with
this PRFILE parameter. The parameter value indicates the block time in hours. The
range of the parameter is 0 to 720 and the recommended value is 6. If the range is
exceeded, the maximum value of 720 is used.
PRFILE control
parameter values.
Parameter values

0001H-02D0H The non-performing cell recovery block time is set between 1 and 720
hours, with a one step of one hour.

0000H 0006H n/a

Dependence
For more information, see Features RAN1302, RAN1810 and RAN1823: Non-Performing
Cell Recovery, Feature Activation Manual.
3.12 007:0246 RN30_MAINT_023

Descriptive name
Overload control mechanism
This change is effective across all IPA-RNC SW versions.
PRFILE parameter 007:0246 RN30_MAINT_023 is used to modify an overload
control functionality implemented to protect the RNC, the IU-CS/IU-PS links, and CS/PS
CN from overload. The overload control mechanism limits the number of simultaneous
ongoing Location Update and Routing Area Update operations under the RNC.
This mechanism is enabled by default. The RNC-level limit is determined by the number
of WO-ICSU units in the configuration:
Number of WO-ICSU units RNC-level limit

1 to 18 800
19 to 28 1200
29 or higher 1600
Each ICSU calculates the unit-level limit by dividing the RNC-level limit by the number of
WO-ICSU units, and rounding the result upwards.
If the value is set to 0, the default settings will be used. With other values, the parameter
value is used directly as RNC-level limit and each ICSU will calculate its unit-level limit
by dividing the given parameter value by the number of WO-ICSU units.
Example
To double the limit of a 18 WO-ICSU configuration from 800 to 1600 operations, the
<LIMIT> value will be 0640H.
PRFILE control
parameter values.
Parameter values

0000H The functionality is active and default settings are used.


0001H - F000H The functionality is active and the parameter value is used as RNC-level
limit.

0000H n/a
Dependence
n/a
3.13 007:0269 RN40_MAINT_001

Descriptive name
MOCN improvements
IPA-RNC, mcRNC
MOCN improvement
Correction for RAN966: Multi-Operator Core Network compatibility with other vendors
Core Networks. All other vendors’ Core Networks cannot manage MOCN if the RNC
uses the CN's own PLMN id in the Global RNC id. Instead, it waits for MOCN RNC to
always use the Common PLMN id in the RNC Id.
A new functionality is added to improve the compatibility with other vendors’ Core
Networks. This functionality can be activated from RN4.0 CD1.3 onwards when RAN966
is in use with the PRFILE parameter. The parameter defines which PLMN Id is used in
the Global RNC Id that is included in the RANAP messages. If that parameter is
activated, then all Global RNC Ids which are sent to CN include the Common PLMN Id
as the PLMN Id.
RNC support for Femto based UE resetting
With this functionality, when Paging message itself was not sent via RNC, the RNC does
not have that temporary data. Also, if UE sends attach request inside
ImsiPagingResponse message, the RNC cannot forward the request to any CN. As a
result, when Femto wants to reset UE and move it to the WCDMA, the UE request will be
rejected.
Support to this Femto based UE resetting, requires that RNC makes load sharing routing
for ImsiPageResponse message in case CN is not known.
CTP request for other PLMN
Some UE models sends invalid selected PLMN to the RNC in MOCN configuration. With
this functionality, the RNC does not check UE selected PLMN before saving it, therefore
when UE makes new CN connection establishment it will use wrong PLMN info in SAI
and LAI data. Wrong selected PLMN info will be ignored and by default UE request will
be handled as like non-supported UE (No Selected PLMN).

PRFILE control
parameter values.
Parameter values

0000H The functionalities are not active.
0201H Received Initial UE messages are ignored when UE selects an PLMN ID
which was not available under its RNC/Cell. The default functionality is to
ignore only that selected PLMN and continue routing as that selected
PLMN not received.
2001H MOCN / IuFlex improvement and the RNC support for Femto based UE
(to manage paging responses handling when UE respond by IMSI).
2201H Both functionalities are active.

0000H n/a
Dependence
RAN966: Multi-Operator Core Network
3.14 007:0270 RN40_MAINT_002

Descriptive name
MOCN improvement
IPA-RNC, mcRNC
Additional configuration parameters for RAN966: Multi-Operator Core Network feature.
PRFILE control
parameter values.
Parameter values

0000H 0000H - FF00H n/a
Dependence
See Activating RAN966: Multi-Operator Core Network.

3.15 007:0279 RN40_MAINT_009

Descriptive name
BTS power measurement improvement
IPA-RNC, mcRNC
A new functionality which prevents problems when the initialization of BTS power
measurement fails in certain BTSs. The more cells the site has, the higher the probability
of failure initialization.
Sometimes the WBTS reports constantly show the nonHDSPAPtx power as zero. This is
considered an invalid measurement value in the RNC, thus, it is rejected. This, in
consequence, causes an overload when there is enough capacity allocation.
From RN4.0 CD1.0 onwards, a new functionality can be controlled by the PRFILE
parameter.
When the parameter value is 0 (default), and if the WBTS reports show the
nonHDSPAPtx power as zero, then it is converted to the initial CPICH value.
When the parameter has a non-zero value, then the zero measurements are not
accepted.
Additionally, a supervision has been added: if the WBTS reports show the nonHSDPAtx
power as zero for 5 minutes, then the ICSU computer log is written.
PRFILE control
parameter values.
Parameter values

0000H WBTS reports showing the nonHDSPAPtx power as zero are converted to
the initial CPICH value.
0001H WBTS reports showing the nonHDSPAPtx power as zero are not
accepted.

0000H n/a
Dependence
n/a

3.16 007:0280 RN40_MAINT_010

Descriptive name
IP defragmentation support on NPS1(P)
IPA-RNC
From RN4.0 CD1.1 onwards, a new functionality is implemented and now NPS1(P) can
support a reassemble of the received fragmented IP packets. NPS1(P) runs a dedicated
SW for IP defragmentation which needs to be activated via a PRFILE parameter. The
fragmentation of IP packets is not supported, therefore the MTU size in NPS1 IPoAtm
interface should be big enough to avoid the fragmentation when sending the traffic.
The NPS1(P) defragmentation requires card(s) to be dedicated to IuPS only. AAL2
switching and ATM Iu-CS need separate unit(s).
In order to minimize the traffic-break time due to this restart, it is recommended to enable
the PRFILE parameter and perform a required reconfiguration before the CD installation.
For further instructions, see TS-RNC-SW-130.
g Note: Activating this functionality requires restarting the NPS1(P) to load the IP
defragmentation support with Iu-PS only function. Restarting the NPS1P causes a
traffic break. It is highly recommended that the preparations and activation are
performed before the CD installation, and that system restart be performed as part of
CD installation.
PRFILE control
parameter values.
Parameter values

0001H IP defragmentation support on NPS1(P) is active.

0000H n/a
Dependence
n/a

3.17 007:0281 RN40_MAINT_011

Descriptive name
Adjustable HSUPA BLER target for PS NRT
IPA-RNC, mcRNC
The HSUPA L1 BLER target for PS NRT parameter is changed as an operator-
modifiable PRFILE parameter from RN4.0 CD1.2 onwards.
PRFILE parameter 007:0281 RN40_MAINT_011 defines the L1 BLER target for the
E-DCH MAC-d flow of the PS NRT service. This target is used by the outer loop power
control of the RNC. The value of the parameter equals the log10 of the BLER value.
PRFILE control
parameter values.
Parameter values

0000H - 0007H RNC uses the default value 1 (10% BLER)
0008H - 0014H RNC uses values from 0.8 (16% BLER) to 2.0 (1% BLER), with a step of
0.1 units.
0015H - FF00H RNC uses the default value 1 (10% BLER)

0000H n/a
Dependence
RAN2170: Adjustable HSUPA BLER target for PS NRT
3.18 007:0283 RN40_MAINT_013

Descriptive name
Optimization of the RRM algorithms in RNC
IPA-RNC, mcRNC

PRFILE Parameter 007:0283 RN40_MAINT_013 is used to control the
enhancements of the admission control and packet scheduling algorithms in RNC.
See TS-RNC-SW-137 (Admission control modifications) and TS-RNC-SW-189
(Enhanced algorithms for optimizing RRM functionalities of RU30) for detailed
descriptions, possible values and activation instructions.
PRFILE control
parameter values.
Parameter values

0000H n/a
Dependence
n/a
3.19 007:0284 RN40_MAINT_014

Descriptive name
PRFILE control for SIR error to trigger CTS and HSPA reconfiguration to DCH after SCC
and F-DPCH retainability improvement when SIR error measurement is enabled
• SIR error to trigger CTS and HSPA reconfiguration to DCH after SCC
IPA-RNC, mcRNC
• F-DPCH retainability improvement when SIR error measurement is enabled
SIR error to trigger CTS
During poor UL SIRerror conditions HSDPA calls which have only one cell in active set
or where are switched from HSDPA to DCH. Also HSDPA calls in soft handover might be
switched to DCH if other active set cell's are not suitable HSDPA serving cell candidates.
Problem can be detected by HSDPA retainability decreasing and channel type switches
due to UL SIRerrormight occur frequently.
As a correction, new PRFILE controlled change prevents channel type switch to DCH
due UL SIRerror measurement without preventing the possibility to use UL SIRerror
measurement to trigger HSDPA serving cell change.
HSPA reconfiguration to DCH after SCC

HSDPA retainability is decreased due to channel type switches from HSDPA/HSPA to
DCH. This occurs when serving cell is deleted from the active set and suitable serving
cell candidate is not found due to low UL SIR error measurement in the target cell.
With this workaround, if the serving cell change (SCC) is triggered by such an event or
measurement report, where the serving cell is to be deleted from the active set, RNC will
not use UL SIR error measurement of the target cell as criterion.
Serving cell can be deleted from the active set due to following reasons:
• Measurement Event 1B reported by the UE
• Measurement Event 1C reported by the UE
• RL failure (loss of UL synchronisation) reported by the BTS
• RL removal due to Rx-Tx time difference reported by the UE
UL SIR error measurement of the target cell can be used as criterion according to the
legacy principles if SCC is triggered due to following reasons:
• Periodical CPICH Ec/No reported by the UE
• UL SIR error measurement reported by the BTS
F-DPCH retainability improvement when SIR error measurement is enabled

The prevention of HSPA serving cell changes (SCC) to Active Set cells under poor UL
SIRerror conditions is expected network behavior, triggering a reconfiguration from F-
DPCH to basic HSPA. It has been detected, however, that the first UL SIRerror reports
received from NBAP for newly added radio links contain unreliable data, as the result
has not yet been stabilized to its real value.
This behavior can now be modified through PRFILE 007:0284 RN40_MAINT_014, so
that Handover Control can ignore the first 1..3 SIR error reports received for a newly
added Radio Link. This affects Radio Link setup, so softer handover scenarios will not be
affected. Ignoring these first reports reduces the probability of unstable SIR error
resulting in the unnecessarily blockage of SCC to valid cells. SCC to cells without
available SIR error result continues to be allowed.
PRFILE control
parameter values.
Parameter values
Allowed Binary Effect

value(s)
0000H 0000 All workarounds are disabled (default value)
0001H 0001 Enables SIR error to trigger CTS workaround
0003H 0011 Enables SIR error to trigger CTS workaround and HSPA
reconfiguration to DCH after SCC
0004H 0100 Enables F-DPCH retainability improvement when SIR error
measurement is enabled, with first SIR Error reports ignored
0008H 1000 Enables F-DPCH retainability improvement when SIR error
measurement is enabled, with 2 first SIR Error reports
ignored

Allowed Binary Effect

value(s)
000CH 1100 Enables F-DPCH retainability improvement when SIR error
measurement is enabled, with 3 first SIR Error reports
ignored
0007H 0111 Enables all three workarounds, with first SIR Error report
ignored
000BH 1011 Enables all three workarounds, with 2 first SIR Error reports
ignored
000FH 1111 Enables all three workarounds, with 3 first SIR Error reports
ignored

0000H n/a
Dependence
n/a
3.20 007:0285 RN40_MAINT_015

Descriptive name
Limitation for HSDPA UL DCH return channel
IPA-RNC, mcRNC
RAS06ED introduced the feature RAN1727: Enhancement to HSDPA with Simultaneous
AMR Voice Call, and it was an OSW feature. That feature allowed all the HSDPA return
channel of the UL DCH data rates (16, 64, 128 and 384) to be transmitted
simultaneously with the AMR call. That was controlled via PRFILE parameter 007:0285
RN40_MAINT_015. By default, the data rates of 128 kbps and 384 kbps are not allowed
for HSDPA return channel of UL DCH simultaneously with the AMR call.
In RN4.0, before CD1.2, the data rates of 128 kbps and 384 are allowed for HSDPA
return channel of UL DCH simultaneously with the AMR call, without any control as a
generic SW. From RN4.0 CD1.2 onwards, the HSDPA return channel of UL DCH with
AMR can be limited to 64 kbps by the PRFILE parameter.
PRFILE control
parameter values.
Parameter values


0000H The maximum bitrate for the HSDPA UL DCH return channel for
AMR+HSDPA multirab is set to 384 kbps.
0001H The maximum bitrate for the HSDPA UL DCH return channel for
AMR+HSDPA multirab is set to 64 kbps.

0000H n/a
Dependence
n/a
3.21 007:0286 RN40_MAINT_016

Descriptive name
Transport changes for RACH capacity
IPA-RNC, mcRNC
The RACH capacity of Ultrasites is limited by the traffic shaping applied on the transport
side. This creates a mismatch between the air-interface capacity (72kb/s by default) and
the transport capacity (20.8kb/s). It can result in the deletion of RACH messages in the
BTS which affects end-user experience in periods of high RACH load.
From RN4.0 CD1.3 onwards, a new functionality is controlled by PRFILE parameter
007:0286 RN40_MAINT_016, which can be used for selecting RACH ALC/IPTD
parameter set.
Either a common RACH parameter set (used by default) is used for a normal cell and an
extended cell without depending on the RACH capacity parameter, or a RACH
parameter set depending on the RACH capacity step parameter from 1 to 4 and the Cell
Range parameter that indicates if the cell is normal or with an extended coverage.
When a new parameter set is taken into use, the UL CAC reservation is bigger and the
risk for RT traffic packets dropping is removed. The downside is a slight drop in capacity
for other traffic in the uplink (UL) direction. See TS-RNC-SW-136 for a detailed
description and activation instructions.
See TS-RNC-SW-140 for a detailed description and activation instructions.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
3.22 007:0287 RN40_MAINT_017

Descriptive name
STM-1 interface capacity overbooking
IPA-RNC
NPS1(P) ATM CBR VP and VC shaping inaccuracy requires a change of policing
parameters.
From RN4.0 CD1.3 onwards, a change of policing parameters can be controlled via
PRFILE parameter 007:0287 RN40_MAINT_017.
See TS-RNC-SW-136 for a detailed description and activation instructions.
PRFILE control
parameter values.
Parameter values

0000H n/a
Dependence
n/a
3.23 007:0290 RN40_MAINT_020

Descriptive name
Limitation of new HS-DSCH allocations
IPA-RNC, mcRNC

From RN4.0 CD1.4 and CD2.0 onwards, a new functionality is added to the RNC to cope
better with situations, when HS-DSCH allocations fails due to the BTS user amount
congestion. In this kind of congestion, the RNC limits the new HS-DSCH allocations until
some of the existing HS-DSCH allocations are released. Limitation of new allocations is
performed on the HSDPA cell group level. The maximum time for a single limitation in
the HSDPA cell group is set to 10 sec.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
3.24 007:0291 RN40_MAINT_021

Descriptive name
Dynamic link optimization
IPA-RNC, mcRNC
From RN4.0 CD1.4 and CD2.0 onwards, a new functionality is added to the RNC with
PRFILE parameter 007:0291 RN40_MAINT_021. The parameter defines an
additional offset to prevent an immediate upgrade if the radio link (DL DCH bit rate) has
been downgraded due to dynamic link optimization in the cell.
PRFILE control
parameter values.
Parameter values


0000H The Dynamic Link Optimization offset is set to a default value of 1,5 dB.
0001H - 0078H The Dynamic Link Optimization offset is set between 0,1 and 12 dB, with a
step of 0,1 dB.
0079H - FF00H The Dynamic Link Optimization offset is set to 0 dB.

0000H n/a
Dependence
RAN866: Dynamic Link Optimization for NRT Traffic Coverage
3.25 007:0295 RN40_MAINT_025

Descriptive name
AAL2 signaling workaround
IPA-RNC
From RN5.0 MP0 (and RN4.0 CD2.2) onwards, a new functionality is added to the RNC
with PRFILE parameter 007:0295 RN40_MAINT_025. It defines how many 10 ms
periods the RNC waits after a successful outgoing release request (it causes a certain
AAL2 protocols’ waiting time). This solution is proposed because of problems with
handling of AAL2 signaling sequences (CID release collision) in other vendors' MGWs.
If other vendor's MGW is used, the recommended value is 1 or 2 (otherwise it should be
0). When the maximum value (200) is exceeded, value 2 (= 20 ms) is used.
PRFILE control
parameter values.
Parameter values

0001H - 00C8H The waiting period is set between 10 to 2000 ms, with a step of 10 ms.

0000H n/a
Dependence

n/a
3.26 007:0296 RN40_MAINT_026

Descriptive name
SAB Failure/Restart messages on RNC-initiated CBC connection
IPA-RNC, mcRNC
From RN5.0 PP0.1 (and RN4.0 CD2.2) onwards, a new functionality has been added to
the RNC with PRFILE parameter 007:0296 RN40_MAINT_026. It determines if SA3
should initiate an IuBC connection establishment with CBC for sending
FAILURE/RESTART messages. If the CBC does not accept the RNC-initiated
connection, this parameter should be disabled (value = 0). By default SA3 does not
initiate IuBC connection establishment towards CBC.
PRFILE control
parameter values.
Parameter values

0001H The functionality is active. SA3 initiates an IuBC connection attempt
towards CBC.

0000H n/a
Dependence
n/a
3.27 007:0297 RN40_MAINT_027

Descriptive name
Direct PCH to DCH state transition
IPA-RNC, mcRNC

From RN5.0 PP0.1 (and RN4.0 CD2.2) onwards, a new functionality has been added to
the RNC with PRFILE parameter 007:0297 RN40_MAINT_027. With this
improvement, the RRC performs a direct PCH to DCH state transition if it receives the
dl_data_amount greater than or equal to the value defined by this PRFILE parameter.
The value defines the threshold of data (in bytes) in the RLC buffers of SRB3, SRB4,
and all NRT RBs that trigger the downlink traffic volume measurement report (capacity
request) on MAC, when UE is in Cell_FACH state. Otherwise, the RNC sends data on
FACH.
PRFILE control
parameter values.
Parameter values

0000H Threshold set to 128 bytes as default value.
0008H Threshold set to 8 bytes.
FF00H Threshold set to 0 bytes.

0000H n/a
Dependence
n/a
3.28 007:0299 RN40_MAINT_029

Descriptive name
T314 timer offset
IPA-RNC, mcRNC

From RN5.0 1.0 (and RN4.0 CD2.2) onwards, PRFILE parameter 007:0299
RN40_MAINT_029 can be used to manually modify the value of the T314 timer offset
used by the RRC.
PRFILE control
parameter values.
Parameter values

0000H T314 timer offset set to 4 seconds as default value.
0001H - 003CH T314 timer offset set to 1 to 60 seconds, with an incremental step of one
second.

0000H n/a
Dependence
n/a
3.29 007:0304 RN40_MAINT_034

Descriptive name
NBAP overload control functionality for narrow Iub configurations
IPA-RNC, mcRNC
PRFILE parameter 007:0304 RN40_MAINT_034 can be used to adjust the NBAP
overload control functionality. It is recommended to use default NBAP overload control
functionality.
It is possible to select two levels of more aggressive NBAP overload control functionality.
In those cases, NBAP overload control restricts the number of simultaneous RRC
connection requests earlier and faster by rejecting new RRC Connection Requests what
is done by default functionality based on automatic link capacity detection. This can be
used in case of situations where continues AAL2 signaling link congestion occurs
(alarms 1192 SSCOP TRANSMIT BUFFER OVERFLOW) with very bandwidth limited
(less than 3xE1/T1) Iub configurations.
After parameter is changed, the RNC should be restarted to apply change to all the
BTSs under the RNC. Other alternative is to perform COCO detach/attach or BTS restart
in case parameter value needs to be applied only to certain BTSs.

g Note: Unnecessary usage of this more aggressive NBAP overload control functionality
can result in unnecessary increase of counter M1006C203 RRC CONN REJECT DUE
TO IUB OVERLOAD CTRL, even if actual link capacity would allow more RRC
connection requests.
PRFILE control
parameter values.
Parameter values

0000H Recommended overload control functionality for recommended Iub
transport configurations.
0001H Min and start levels of overload control functionality are lower than
automatic link capacity detection would set it. Max level is according to
link capacity.
0003H In addition to Min and start levels of overload control functionality, also
Max level of is lower than value set by automatic link capacity detection in
default mode.

0000H n/a
Dependence
n/a
3.30 007:0306 RN40_MAINT_036

Descriptive name
PS memory supervision
IPA-RNC, mcRNC
PRFILE parameter 007:0306 RN40_MAINT_036 controls the PS memory
supervision procedure. For possible values and activating instructions, see TS-RNC-HW-
076 (section 6).
Default value(s)
See TS-RNC-HW-076 (section 6).
Allowed values
See TS-RNC-HW-076 (section 6).

Dependence
n/a
3.31 007:0307 RN40_MAINT_037

Descriptive name
PRFILE parameter 007:0307 RN40_MAINT_037 controls the following functionalities:
1. UE problem workaround for direct transition to PCH
2. RNC support for lossless PDU size change
IPA-RNC: RN7.0
mcRNC: mcRNC3.0
1. The 1st bit of PRFILE Parameter 007:0307 RN40_MAINT_037 (bit0) controls a
workaround on UE-specific PS RAB failures during Cell reselection.
g Note: Deactivating this workaround may lead to PS call drops. Nokia
recommends not modifying the default value of this bit. For more information see
technical support note TS-RNC-SW-149.
2. The 6th bit of PRFILE Parameter 007:0307 RN40_MAINT_037 (bit5) controls a
workaround on Cell update handling problems during direct transitions to PCH for
Rel.5 Apple UEs.
3. The 5th bit of Parameter 007:0307 RN40_MAINT_037 (bit6) is used for disabling
RNC support for lossless PDU size change.
PRFILE control
parameter values.
Parameter values

0000H Disables UE problem workaround for direct transition to PCH
Enables RNC support for lossless PDU size change
Enables UE-specific PS RAB failures during Cell reselection

Disables UE-specific PS RAB failures during Cell reselection


Disables RNC support for lossless PDU size change

0020H Enables UE problem workaround for direct transition to PCH





0000H 0000H, 0010H, 0020H, 0030H n/a
Dependence
n/a
3.32 007:0308 RN40_MAINT_038

Descriptive name
Terminating Low Priority Signaling initiates RT over NRT
IPA-RNC, mcRNC
PRFILE parameter 007:0308 RN40_MAINT_038 defines RT-over-NRT triggered in
RRC connection establishment phase if the establishment is made with Originating or
Terminating Low Priority Signaling establishment cause values. RT-over-NRT can be
triggered in resource congestion cases.
PRFILE control

parameter values.
Parameter values

0000H RT-over-NRT is triggered in RRC connection setup phase with Originating
Low Priority Signaling establishment cause and not triggered with
Terminating Low Priority Signaling establishment cause
0001H RT-over-NRT is not triggered in RRC connection setup phase with
Originating Low Priority Signaling establishment cause and not triggered
with Terminating Low Priority Signaling establishment cause
0002H RT-over-NRT is triggered in RRC connection setup phase with Originating
Low Priority Signaling establishment cause and triggered with Terminating
Low Priority Signaling establishment cause
0003H RT-over-NRT is not triggered in RRC connection setup phase with
Originating Low Priority Signaling establishment cause and triggered with
Terminating Low Priority Signaling establishment cause

0000H n/a
Dependence
n/a
3.33 007:0387 RNC_L3_CONTROL_022

Descriptive name
Usage of extra ADJx per cell.
RNC: RNC16 onwards
Case scenarios have been identified where cells remain in state Blocked by the system
(BL-S) or Blocked by Initialization (BL-I) and an alarm 7771 WCDMA CELL OUT OF
USE or 7761 RNW O&M Scenario Failure (BCCH scheduling error or BCCH info sending
failure) is reported for such cells.
PRFILE parameter 007:0387 RNC_L3_CONTROL_022 controls a workaround for
preventing the wcel blockage. Instead of blockage, extra ADJx (ADJI and ADJG only)
are dropped (not sent in SIB 11/11bis).
Workaround consists of two parts:
• Extra ADJx are removed (ADJI and ADJG are removed in round robin order).

• Alarm 7775 is raised if ADJx are terminated.
After activating the PRFILE functionality, RNC will start truncating extra inter frequency
and Inter RAT neighbouring information whenever it receives SIB update request. In
case if RNC is taking recovery actions, the truncation of extra inter frequency and Inter
RAT neighbouring information will be visible. Manual WCEL lock/unlock is required if the
system is not doing any recovery action.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
3.34 007:0388 RNC_L3_CONTROL_023

Descriptive name
HSUPA allocation failures with limited WN7.0 HSUPA baseband HW resources or control
the NRT DCH bit rate limitations due to BTS baseband hardware congestion
This PRFILE parameter defines the NRT DCH services , which bitrates are limited due to
base transceiver station (BTS) baseband hardware (HW) congestion algorithm
(HSUPA_CONG_ALG). More information is found in TS-RNC-SW-189.
PRFILE control
parameter values.
Parameter values


0000H The NRT DCH bit rate limitations are not applied.
0001H Limitations for high-speed downlink packet access (HSDPA) uplink
dedicated traffic channel (DCH) return channels are applied.
0002H Limitations for Release 99 uplink and downlink DCHs are applied.
0003H Both limitations are applied.

0000H 0003H n/a
Dependence
n/a
3.35 007:0389 RNC_L3_CONTROL_024

Descriptive name
the initial bit rate limitation threshold (INI_THRESH)
This PRFILE parameter controls the initial bit rate limitation threshold (INI_THRESH),
which is used to trigger the HSUPA_CONG_ALG algorithm. If the average value is equal
or higher than the INI_THRESH, the algorithm status is triggered to hardware (HW)
limited.
If the average value is lower than both INI_THRESH and minimum bit rate limitation
threshold (MIN_THRESH), the algorithm status is normal. MIN_THRESH condition
triggering has higher priority than the INI_THRESH condition.
See the 007:0390 RNC_L3_CONTROL_025 for more information on MIN_THRESH
condition.
See the 007:0391 RNC_L3_CONTROL_026 for more information on the
HSUPA_CONG_ALG algorithm.
PRFILE control
parameter values.
Parameter values


0000H INI_THRESH is set to 5 as default value.
0001H - 0014H INI_THRESH is set between values 1 to 20 with a step of one unit.

0000H n/a
Dependence
Value of INI_THRESH should not be higher than the value of MIN_THRESH. For more
information, see 007:0390 RNC_L3_CONTROL_025.
3.36 007:0390 RNC_L3_CONTROL_025

Descriptive name
the minimum bit rate limitation threshold (MIN_THRESH)
This PRFILE parameter controls the minimum bit rate limitation threshold
(MIN_THRESH), which is used to trigger the HSUPA_CONG_ALG algorithm. If the
average value is equal or higher than the MIN_THRESH, the algorithm status is
triggered to no EDCH capacity.
If the average value is lower than both initial bit rate limitation threshold (INI_THRESH)
and MIN_THRESH, the algorithm status is normal. MIN_THRESH condition triggering
has higher priority than the INI_THRESH condition.
See the 007:0389 RNC_L3_CONTROL_024 for more information on INI_THRESH
condition.
See the 007:0391 RNC_L3_CONTROL_026 for more information on the
HSUPA_CONG_ALG algorithm.
PRFILE control
parameter values.
Parameter values

0000H MIN_THRESH is set to 15 as default value.


0001H - 0014H MIN_THRESH is set to a value between 1 and 20 with a step of one unit.

0000H n/a
Dependence
Value of INI_THRESH should not be higher than the value of MIN_THRESH. For more
information, see 007:0389 RNC_L3_CONTROL_024.
3.37 007:0391 RNC_L3_CONTROL_026

Descriptive name
HSUPA allocation failures with limited WN7.0 HSUPA baseband HW resources or
number of samples used to calculate average reported measurement value
This PRFILE parameter controls the number of samples used to calculate the average
reported measurement value. One sample is collected from each received
measurement. The average value is used to define the HSUPA BTS HW congestion
status detection (HSUPA_CONG_ALG) algorithm, as described in 007:0389
RNC_L3_CONTROL_024 and 007:0390 RNC_L3_CONTROL_025.
PRFILE control
parameter values.
Parameter values

0000H The number of samples is set to 40 as default value.
0001H - 00C8H The number of samples is set between 1 and 200, with a step of one unit.

0000H n/a
Dependence
n/a

3.38 007:0394 RNC_L3_CONTROL_029

Descriptive name
RNC-Id and Cell-Id usage for RAN2054: Extension of RNC ids feature
RNC: RNC16 onwards
PRFILE parameter 007:0394 RNC_L3_CONTROL_029 is used to control the number
of bits of RNC-Id and Cell-Id in Cell Identity IE of SIB type 3 or SIB type 4.
g Note: SIB update according to the new PRFILE value does not happen automatically.
Another trigger such as a cell lock/unlock or a radio network parameter update are
required as well.
For more information on the feature, see RAN2054: Extension of RNC ids feature in

Flexi Direct RU30, Feature Descriptions document.
PRFILE control
parameter values.
Parameter values

0000H SIB3/SIB4 Cell Identity IE is encoded with 12 bits used for RNC-Id and 16
bits for Cell-Id.
0001H SIB3/SIB4 Cell Identity IE is encoded with 16 bits used for RNC-Id and 12
bits for Cell-Id.

0000H n/a
Dependence
RAN2054: Extension of RNC ids
3.39 007:0398 RNC_L3_CONTROL_033

Descriptive name
RNC workaround for UE problem.

IPA-RNC: RN7.0, RN8.1 onwards
Some UE models restart during ongoing data transfer if CPC is activated. PRFILE
parameter 007:0398 RNC_L3_CONTROL_033 controls a workaround that disables
CPC for these users.
For further information see technical support note TS-RNC-SW-149.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
3.40 007:0518 CELL_FACH_RELOC_PREVENT

Descriptive name
Cell_FACH Relocation Prevention
The change is needed because of problem with Cell_FACH relocation. When UE makes
a cell reselection during an ongoing relocation, the relocation fails in NSN RNC area.
When a cell reselection happens immediately after UMI-C has been sent by the UE, then
there is a problem where UE cannot receive CELL UPDATE CONFIRM since SRB1 is
stopped. UEs keep looping for a while if there is a second cell reselection after relocation
was initiated because of the first cell reselection. Such a behavior is typical of many
different networks and UEs, it is not just one chipset-related problem. This has also been
confirmed that this is not an UE fault. UEs that get stuck work according to standards.

To address the issue, DSCR procedure can be used for inter RNC mobility of Cell_PCH
UEs. The problem to activate DSCR feature is that Cell_FACH relocation needs to be
disabled first and that requires disabling Cell FACH relocation as a whole.
As an improvement a new 007:0518 CELL_FACH_RELOC_PREVENT PRFILE
parameter has been introduced to prevent Cell_FACH relocations on RNC level without
disabling Cell_FACH relocation as a whole.
When the Cell_FACH relocation prevention functionality is activated, Cell_FACH
relocation is prevented on RNC level. DSCR procedure is used for inter RNC mobility of
Cell_FACH state UEs regardless of the state of parameters
NRncRelocationSupport, CellFACHnRncRelocSupport, and
CellFACHrelocSupport.
PRFILE control
parameter values.
Parameter values


0000H n/a
Dependence
n/a
3.41 007:0521 HSPA_DCH_MIN_RES

Descriptive name
Capacity reservation for Cell_DCH state HSPA users and prioritization of HSPA users
over HS Cell_FACH users
IPA-RNC: RN16 onwards
Feature RAN2869 introduced HSPA capacity licensing to WCDMA16 RNCs. With this
feature Radio Resource Manager (RRM) is able to count HSPA users so that the
licensed number is not exceeded. This total of licensed users is equivalent to the sum of
HSPA Cell_DCH users and High Speed Cell_FACH users.

PRFILE parameter 007:0521 HSPA_DCH_MIN_RES controls the reservation of a
given number of Cell_DCH state HSPA users by the RNC, ensuring that the total number
of licensed users is distributed between DCH and FACH states.
This reserved Cell_DCH number is called ‘DCH_HSPA_min’ and is defined by the
following formula:
DCH_HSPA_min = MIN (PRFILE *maxHSPA, HSPA legacy AC limit)
Where:
• PRFILE corresponds the value of the first four bits of parameter 007:0521
HSPA_DCH_MIN_RES.
• maxHSPA is the cell’s licensed capacity with RAN2869 for number of HSPA users.
• HSPA legacy AC limit as calculated from the Cell's licensed capacity, considering
possible limits set by WCEL parameters and/or BTS capability.
The 8th bit of parameter 007:0521 HSPA_DCH_MIN_RES indicates whether
DCH_HSPA state users shall have higher priority than HS-FACH users, so that HS-
FACH users are released from the cell in order to allow access of Cell_DCH state HSPA
users until the maximum number of HSPA users in Cell_DCH state is achieved. When
this 8th bit is set to ‘0’ there will be no such pre-emption of HS Cell-FACH users.
PRFILE control
parameter values.
Parameter values

0000H Deactivated HS-FACH user pre-emption and deactivated minimum
reservation for HSPA users on the Cell_DCH state.
0001H - 000AH Deactivated HS-FACH user pre-emption, minimum reservation for HSPA
users on the Cell_DCH state between 10% and 100%, with a step of 10%.
0080H Active HS-FACH user pre-emption and deactivated minimum reservation
for HSPA users on the Cell_DCH state.
0081H - 008AH Active HS-FACH user pre-emption, minimum reservation for HSPA users
on the Cell_DCH state between 10% and 100%, with a step of 10%.

0000H n/a
Dependence
RAN2869 HSPA Subscriber Increase
3.42 007:0522 CS_CALL_RE_ESTB_OVR_IUR

Descriptive name
RAN3228-specific PRFILE parameter

RNC RNC17 onwards
When RAN3228 CS call re-establishment over Iur is activated for CS call re-
establishment over Iur with serving radio network controller (SRNC) relocation, the CS
call re-establishment over Iur with serving radio network subsystem (SRNS) relocation is
performed only for Release 9 user equipment (UE) and newer by default. Because of
problems of some Release 8 UE models in CS call re-establishment over Iur with SRNS
relocation scenario, the CS call re-establishment over Iur is performed for Release 8 and
older UEs in anchoring by default. With this PRFILE parameter, it will also be possible to
activate the CS call re-establishment over Iur with SRNS relocation for UEs that are
older than Release 9.
g Note: Even if the CS call re-establishment over Iur is performed in anchoring, SRNS
relocation triggers if the criteria for SRNS relocation are met after the CS call re-
establishment over Iur in anchoring procedure has completed.
PRFILE control
parameter values.
Parameter values

0H Even if the relocation mode of RAN3228 is activated, CS call re-
establishment over Iur with SRNS relocation is performed only for Release
9 and newer UEs. For Release 8 and older UEs, the CS call re-
establishment over Iur is performed in anchoring.
3H When the relocation mode of RAN3228 is activated, CS call re-
establishment over Iur is performed with SRNS relocation for all UEs
regardless of the release version.

0H n/a
Dependences
n/a

Parameter class 009 SYSTEM_SUPERVISION PRFILE Descriptions
4 Parameter class 009 SYSTEM_SUPERVISION

This class includes parameters that control limit values related to the monitoring of
system functions.
4.1 009:0101 IUB_DATA_RECV_INTERVAL

Descriptive name
IUB O&M TCP/IP connection data receive interval
IPA-RNC, mcRNC
PRFILE parameter 009:0101 IUB_DATA_RECV_INTERVAL sets the IUB O&M
TCP/IP connection data receive interval, which defines how often the IUB TCP/IP data
received by the RNC is read.
PRFILE control
parameter values.
Parameter values

0001H - 0064H Sets the period by which received IUB TCP/IP data is read. The interval
can be set from 1 to 100 ms, with an incremental step of one millisecond.

0005H n/a
Dependence
7992 - IUB-CORBA MEDITATION (DX)
4.2 009:0102 IUB_CONN_POLLING_TIME

Descriptive name
IUB O&M TCP/IP connection polling interval
IPA-RNC, mcRNC

PRFILE Descriptions Parameter class 009 SYSTEM_SUPERVISION
PRFILE parameter 009:0102 IUB_CONN_POLLING_TIME sets the IUB O&M TCP/IP
connection polling interval, which defines how often the IUB TCP/IP data received by the
RNC on the BS O&M receiving socket is read.
PRFILE control
parameter values.
Parameter values

0001H - 0064H Sets the period by which the BS O&M receiving socket for IUB O&M
TCP/IP data is sampled. The interval can be set from 1 to 100 ms, with an
incremental step of one millisecond.

0005H n/a
Dependence
7992 - IUB-CORBA MEDITATION (DX)
4.3 009:0130 IP_MSG_MON

Descriptive name
RNC Support for Traffica
IPA-RNC, mcRNC
This parameter determines whether the RNC Support for Traffica feature is active or not.
PRFILE Parameter Format of reports 1) sent by IMSI and IMEI 2) availability

RNC in reports
FFH RU30 • IMSI is sent to Traffica.
• IMEI is not sent to Traffica.
FEH RU30 • Only the first six digits of

the IMSI are sent to
Traffica
• IMEI is not sent to Traffica.
1FFH RU40 • IMSI is sent to Traffica.
1) This refers specifically to RRC/RAB and packet call failure Traffica reports.
2) The IMEI is available to Traffica only if it is available to the RNC.

Parameter class 009 SYSTEM_SUPERVISION PRFILE Descriptions
PRFILE Parameter Format of reports 1) sent by IMSI and IMEI 2) availability

RNC in reports
• IMEI is sent to Traffica if it
is available to the RNC.
1FEH RU40 • Only the first six digits of

the IMSI are sent to
Traffica.
• If the IMEI is available to
the RNC, only the first
eight digits of the IMEI are
sent to Traffica.
For more information, see theRAN1150: RNC Support for Traffica feature activation

instructions.
PRFILE control
parameter values.
Parameter values
Allowed value(s) Default value Forbidden value(s)

FFH 0H (FALSE n/a
FEH
1FFH
1FEH
Dependence
RAN1150: RNC Support for Traffica
1) This refers specifically to RRC/RAB and packet call failure Traffica reports.
2) The IMEI is available to Traffica only if it is available to the RNC.

PRFILE Descriptions Parameter class 016 ALARM_SYSTEM
5 Parameter class 016 ALARM_SYSTEM

This class includes alarm system parameters.
5.1 016:0000 ALARM_PRINT_END_MARK

Descriptive name
Alarm print end mark
IPA-RNC
PRFILE parameter 016:0000 ALARM_PRINT_END_MARK determines the end mark of
an alarm printout.
PRFILE control
parameter values.
Parameter values

0000H No end text
0001H END OF MESSAGE text

0000H n/a
Dependence
n/a
5.2 016:0001 LAMP_PANEL_POLARITY

Descriptive name
Lamp panel polarity
IPA-RNC

Parameter class 016 ALARM_SYSTEM PRFILE Descriptions
PRFILE parameter 016:0001 LAMP_PANEL_POLARITY determines the lamp panel
polarity.
PRFILE control
parameter values.
Parameter values

0000H Reverse polarity
0001H Normal polarity

0001H n/a
Dependence
n/a
5.3 016:0002 ALARM_DRIVEN_OUTPUTS

Descriptive name
Number of alarm outputs directed by alarms
IPA-RNC
PRFILE parameter 016:0002 ALARM_DRIVEN_OUTPUTS defines the number of
alarm outputs which can be controlled on the basis of the alarms handled by the alarm
system. The rest of the alarm outputs can be used for other purposes.
PRFILE control
parameter values.
Parameter values

0000H There are no outputs directed by alarms.
0008H 8 first outputs out of a maximum of 16 can be directed by alarms.


000AH All outputs (16) can be directed by alarms.

000AH n/a
Dependence
n/a
5.4 016:0003 LAMP_PANEL_BUZZER

Descriptive name
Activation of lamp panel buzzer by alarms
IPA-RNC
PRFILE parameter 016:0003 LAMP_PANEL_BUZZER defines the way in which the
state of alarm outputs is updated, in order to control the lamp panel buzzer. The lamp
panel is controlled by the alarm outputs and, by default, the buzzer in the lamp panel is
only activated when a new lamp is lit.
PRFILE control
parameter values.
Parameter values

0000H The state of alarm outputs is updated only when the first alarm controlling
a certain alarm output is set, or when the last alarm controlling a certain
alarm output is canceled.
The lamp panel buzzer is activated only when no alarms controlling a
certain alarm output are active and the first alarm of the kind is set. New
alarms controlling an alarm output which is already in alarm state do not
cause activation of the buzzer.
0001H Each time a new alarm controlling an alarm output is set, the state of all
the alarm outputs is first reset and then immediately set again according
to the current alarm situation. The lamp panel buzzer is then activated
each time a new alarm controlling an alarm output is set.


0000H n/a
Dependence
n/a
5.5 016:0004 PRINTING_MODE

Descriptive name
Printing mode
IPA-RNC
PRFILE parameter 016:0004 PRINTING_MODE is used to define alarm printing mode
between local output or MML output (active alarms listing or alarm history listing).
Printing mode can either be long or short . The default setup is long mode.
PRFILE control
parameter values.
Parameter values

0000H Enables long printing mode.
00FFH Enables short printing mode.

0000H n/a
Dependence
n/a
5.6 016:0008 HEARTBEAT_ALM_INTERVAL

Descriptive name
Heartbeat alarm interval

IPA-RNC
PRFILE parameter 016:0008 HEARTBEAT_ALM_INTERVAL is used for defining the
interval at which heartbeat alarm are sent from a certain NE to NetAct. The interval is
defined minutes.
g Note: The configured value must match in both ends in order to have working
supervision for the O&M interface.
PRFILE control
parameter values.
Parameter values

0000H - 05A0H Sets the heartbeat alarm interval between 0 and 1440 minutes with a step
of one minute.

0005H (5 minutes) n/a
Dependence
n/a
5.7 016:0009 WBTS_LEVEL_ALARM_SWITCH

Descriptive name
WBTS level alarm switch
IPA-RNC, mcRNC
This PRFILE parameter controls the usage of WBTS level alarms in order to reduce
number of alarms in RNC.
For instructions, see Activating RAN1461: RNC RNW alarm reduction.
PRFILE control
parameter values.
Parameter values



0001H n/a
Dependence
RAN1461: RNC RNW Alarm Reduction
5.8 016:0010 SUSPEND_MODE_SWITCH

Descriptive name
Suspended mode switch
IPA-RNC, mcRNC
This PRFILE parameter is used to control the usage of alarm suspend mode to reduce
the number of visible RNC alarms.
PRFILE control
parameter values.
Parameter values


0001H n/a
Dependence
RAN1461:RNC RNW Alarm Reduction

5.9 016:0011 WCEL_OUT_OF_USE_NUM

Descriptive name
WCEL out-of-use alarm number
IPA-RNC, mcRNC
This PRFILE parameter defines a maximum number of visible alarms for WCEL out-of-
use, over which similar alarms are raised in suspend mode.
PRFILE control
parameter values.
Parameter values

0000H-03E8H Value sets a maximum number of alarms for WCEL out-of-use. Once this
number is reached, future alarms are raised in suspend mode. The
interval runs from 0 to 1000 alarms, with a step of one unit.

012CH (300) n/a
Dependence
5.10 016:0012 HSPA_ACT_FAIL_NUM

Descriptive name
HSPA activation failure number
IPA-RNC, mcRNC
This parameter defines the maximum number of visible high-speed downlink packet
access (HSDPA) or high-speed uplink packet access (HSUPA) activation failure for
WCDMA cell (WCEL) alarms, over which similar alarms are raised in suspend mode.

PRFILE control
parameter values.
Parameter values

0000H-01F4H Value sets a maximum number of HSDPA or HSUPA activation failure for
WCEL alarms. Once this number is reached, future alarms are raised in
suspend mode. The interval runs from 0 to 500 alarms, with a step of one
unit.

0064H (100) n/a
Dependence
RAN1461:RNC RNW Alarm Reduction
5.11 016:0013 RNW_DATABASE_FAIL_NUM

Descriptive name
RNW database fail alarm number
IPA-RNC, mcRNC
This PRFILE parameter defines a maximum number of visible radio network (RNW)
database fail alarm, over which similar alarms are raised in suspend mode.
PRFILE control
parameter values.
Parameter values

0000H-0064H Value sets a maximum number of RNW database fail alarms. Once this
number is reached, future alarms are raised in suspend mode. The
interval runs from 0 to 100 alarms, with a step of one unit.


0014H (20) n/a
Dependence
5.12 016:0014 WBTS_LEVEL_ALARM_NUM

Descriptive name
WBTS level alarm number
IPA-RNC, mcRNC
This PRFILE parameter defines a maximum number of visible WBTS level alarms, over
which similar alarms are raised in suspend mode.
PRFILE control
parameter values.
Parameter values

0000H-01F4H Value sets a maximum number of WBTS level alarms. Once this number
is reached, future alarms are raised in suspend mode. The interval runs
from 0 to 500 alarms, with a step of one unit.

0064H (100) n/a
Dependence
5.13 016:0015 BUFFER_ALARM_THRESHOLD

Descriptive name
Buffered alarm threshold

IPA-RNC, mcRNC
This PRFILE parameter defines a limitation for alarm number parameters such as
rnw_database_fail_num. The alarms are written into the database only when their
level is lower than the threshold set by this parameter.
For further instructions, see Activating RAN1461: RNC RNW alarm reduction.
PRFILE control
parameter values.
Parameter values

0000H-0064H Value sets a threshold level from 0 to 100%, over which alarms are not
written into the database. The incremental step is one unit (1%).

0050H (80%) n/a
Dependence

PRFILE Descriptions Parameter class 038 MML_COMMAND_LOG
6 Parameter class 038 MML_COMMAND_LOG

This class includes parameters defining timeout values and disk usage restrictions of the
MML Command Log.
6.1 038:0001 STORAGE_LENGTH

Descriptive name
MML Command Log: storage length of log contents
IPA-RNC
This parameter defines the maximum time that MML command log files are kept on
disks. The minimum value is three (0003H) days and the maximum value is sixty
(003CH) days.
PRFILE control
parameter values.
Parameter values

0003H - 003CH Maximum time during which MML logs are kept can be set between 3 and
60 days, with an incremental step of one day.

003CH n/a
Dependence
n/a

Parameter class 055 LCS_PARAMETERS PRFILE Descriptions
7 Parameter class 055 LCS_PARAMETERS

This class includes parameters related to Location Services (LCS).
7.1 055:0003 EMERGENCY_CALL_ISHO_SUP

Descriptive name
Directed emergency call intersystem handover feature
IPA-RNC
This PRFILE parameter activates the directed emergency call intersystem handover
feature, which is optional. If the parameter is enabled, emergency calls from UMTS
terrestrial radio access network (UTRAN) are directed to the GSM network to allow E-
OTD location service instead of the cell id and RTT-based location service included in
RAN2.0. If the parameter is disabled, the location of the emergency calls is done in
UTRAN.
PRFILE control
parameter values.
Parameter values

0000H The location of emergency calls is done in UTRAN.
0001H Emergency calls from UTRAN are directed to the GSM network to allow
E-OTD location service instead of the cell id and RTT-based location
service.

0000H n/a
Dependences
n/a
7.2 055:0011 AGPS_SUPPORT

Descriptive name
A-GPS location method support

PRFILE Descriptions Parameter class 055 LCS_PARAMETERS
IPA-RNC
This PRFILE parameter controls whether the usage of the A-GPS method is allowed for
location services.
PRFILE control
parameter values.
Parameter values

0000H Usage of the A-GPS method is not allowed.
0001H Usage of the A-GPS method is allowed.

0000H n/a
Dependences
n/a
7.3 055:0012 INT_EMERG_CALL_ISHO_SUP

Descriptive name
Intelligent directed emergency call intersystem handover feature
IPA-RNC
This PRFILE parameter activates the intelligent directed emergency call intersystem
handover feature, which is optional. If the parameter is enabled and if the requested
accuracy is not fulfilled by CI+RTT or A-GPS location methods included in RAS2.2,
emergency calls from UMTS terrestrial radio access network (UTRAN) are directed to
the GSM network. If the parameter is disabled, the location of the emergency calls is
done in UTRAN.
PRFILE control
parameter values.
Parameter values

Parameter class 055 LCS_PARAMETERS PRFILE Descriptions

0000H The location of the emergency calls is done in UTRAN.
0001H If the requested accuracy is not fulfilled by CI+RTT or A-GPS location
methods, emergency calls from UTRAN are directed to the GSM network.

0000H n/a
Dependences
n/a
7.4 055:0013 NW_AGPS_SUPPORT

Descriptive name
NW-based A-GPS location method support
IPA-RNC
This PRFILE parameter controls whether the usage of the NW-based A-GPS method is
allowed for location services.
PRFILE control
parameter values.
Parameter values

0000H Usage of the NW-based A-GPS method is not allowed.
0001H Usage of the NW-based A-GPS method is allowed.

0000H n/a
Dependences
n/a
7.5 055:0015 IUPC_INTERFACE

Descriptive name
Iupc interface support

PRFILE Descriptions Parameter class 055 LCS_PARAMETERS
IPA-RNC
This PRFILE parameter controls whether the usage of the Iupc interface is allowed.
PRFILE control
parameter values.
Parameter values

0000H Usage of the Iupc interface is not allowed.
0001H Usage of the Iupc interface is allowed.

0000H n/a
Dependences
n/a

Parameter class 058 OAM_SECURITY PRFILE Descriptions
8 Parameter class 058 OAM_SECURITY

This class includes parameters related to O&M security.
8.1 058:0000 PW_POLICY_FEATURE, 058:0001

UA_POLICY_FEATURE, 058:0004
USER_ACCOUNT_LOCK_LIMIT, 058: 0005
CONF_INTERFACES_FEATURE, 058:0006
HTTPS_WEBGUI_INTERFACE
These parameters are used to control the feature RAN2883: User Security Policy for

RNC196/450/2600:
• 058:0000 PW_POLICY_FEATURE
• 058:0001 UA_POLICY_FEATURE
• 058:0004 USER_ACCOUNT_LOCK_LIMIT
For more information, see WCDMA RAN, Rel. RU40, Feature Descriptions and

Instructions.

PRFILE Descriptions Parameter class 069 TROUBLESHOOTING
9 Parameter class 069 TROUBLESHOOTING

This parameter class includes parameters concerning troubleshooting.
9.1 069:0001 CSUP_AUTO_RECOVERY_TIME

Descriptive name
Time of automatic CSUP recovery after 3870 alarm is raised
The 069:0001 CSUP_AUTO_RECOVERY_TIME PRFILE parameter controls the time
at which the automatic recovery is triggered for the CSUP unit. A recovery is triggered
when it is detected that the internal memory resources have fallen below a pre-defined
threshold and have not recovered until the default scheduled recovery time.
The default value of CSUP_AUTO_RECOVERY_TIME is 2 AM. It is set to 78 Hex, that is
120 minutes from 00:00 hours.
Value 0 means the automatic recover procedure will be triggered immediately. Value
other than 0 is considered as offset in minutes from 00:00 hours to start the automatic
recovery procedure.
PRFILE control
parameter values.
Parameter values

0000H Automatic recover procedure will be triggered immediately.
0001H - 10E0H Offset for the automatic recovery procedure is set between 1 and 120
minutes, with a step of one minute.

0078H 10E1H - FFFFH
Dependences
n/a

Appendix PRFILE Descriptions
10 Appendix
The Appendix section shows supplementary and additional information regarding the
PRFILE Descriptions document.
10.1 Appendix A: Non-valid PRFILE parameters

This appendix section displays all non-valid PRFILE parameters for RNC19/mcRNC19.
This command was used to retrieve all the parameters in this section: show app-
parameter configuration-parameter.
10.1.1 Non-valid PRFILE parameter from Parameter Class 000

The PRFILE parameters listed in this section are considered non-valid for Parameter
Class 000.
• 000:0024 ANN_DEF_NBR_OF_CYCLES

Class 002.
• 002:0009 DPABX_CHARGING
• 002:0035 PRIMARY_RATE_INTERFACE
• 002:0062 CIWF_MODE
• 002:0115 FREE_CIC_NUMBERING
• 002:0188 T1_ENVIRONMENT
• 002:0241 Q3_DX_ALARMS_FORW_ON
• 002:0266 ANALYSIS_MAX_COUNT
• 002:0289 SSF_FUNCTION_ON
• 002:0361 NORTH_AMERICAN_NUMBER
• 002:0366 NOKIA_ACM_SUPPORT
• 002:0461 BIN_HEADER_TYPE
• 002:0603 NE_CONFIG_REDUNDANT
• 002:0629 TRUNK_INTERFACE_TYPES
• 002:0671 IMA_GRP_DIFF_DELAY_MAX
• 002:0693 FIRST_FREE_NUMBERED_CGR
• 002:0711 NEMU_IS_PRESENT
• 002:0757 USE_OF_TTY
• 002:0775 PCM_ENCODING_LAW
• 002:0817 DSCP_FOR_USER_PLANE
• 002:0921 HW_CHANGE_NOTIF_IN_USE
• 002:0946 AAL2_CAC_STAT_SAMP_PER
• 002:0950 RTCP_FOR_UP_MONITORING

PRFILE Descriptions Appendix
• 002:0972 CAC_PATH_ALARM_SET
• 002:0973 CAC_PATH_ALARM_RESET
• 002:0974 CAC_A2SP_ALARM_SET
• 002:0975 CAC_A2SP_ALARM_RESET
• 002:0976 CAC_PATH_CHECK_PER
• 002:0977 CAC_A2SP_CHECK_PER
• 002:1120 LAN_ADMINISTRATION
• 002:1188 MIN_RTP_PORT
• 002:1196 CONGEST_IND_RESO
• 002:1197 CONGEST_ALARM_LIMIT
• 002:1233 AUTOMATIC_HW_CONFIGURAT
• 002:1283 RN22_FEATURE_OPT_001
• 002:1287 DSCP_FOR_SEMIPER_TDM_IP
• 002:1288 PHB_FOR_SEMIPER_TDM_IP
• 002:1289 PORTS_FOR_SEMIPER
• 002:1290 RN22_FEATURE_OPT_002
• 002:1291 RN22_FEATURE_OPT_003
• 002:1298 RN22_FEATURE_OPT_007
• 002:1299 RN22_FEATURE_OPT_006
• 002:1301 RN22_FEATURE_OPT_005
• 002:1302 RN22_FEATURE_OPT_010
• 002:1303 RN22_FEATURE_OPT_011
• 002:1304 RN22_FEATURE_OPT_012
• 002:1306 WBAMR_IN_ROUTE_SELECT
• 002:1307 LBCU_WBAMR_PRIORITY
• 002:1308 EQUIPMENT_DB_UPDATE
• 002:1318 SPRM_ALARM_SET_LIMIT
• 002:1319 SPRM_ALARM_CANCEL_LIMIT
• 002:1553 AAL2_SW_CAPA_AL
• 002:1623 PROP_ACM_SUPPORT
• 002:1626 RNC_UPG_FINAL_WAIT_TIME
• 002:1627 RNC_UPG_PING_WAIT_TIME
• 002:1643 MGW_IP_RTT
• 002:1644 MGW_TDM_RTT
• 002:1645 MGW_ATM_RTT
• 002:1654 LONG_CICS_FOR_TUP
• 002:1663 RN50_MAINT_01
• 002:1667 RN50_MAINT_04
• 002:1672 RN50_MAINT_09
• 002:1685 RN50_MAINT_12
• 002:1693 RN50_MAINT_17
• 002:1694 RN50_MAINT_18
• 002:1695 RN50_MAINT_19
• 002:1698 RN50_MAINT_22
• 002:1707 RN50_MAINT_30
• 002:1708 RN50_MAINT_31
• 002:1710 RN50_MAINT_32

• 002:1711 RN50_MAINT_33
• 002:1712 RN50_MAINT_34
• 002:1713 RN50_MAINT_35
• 002:1714 RN50_MAINT_36
• 002:1715 RN50_MAINT_37
• 002:1718 RN50_MAINT_40
• 002:1758 RN50_MAINT_41
• 002:1759 RN50_MAINT_42
• 002:1761 RN50_MAINT_44
• 002:1762 RN50_MAINT_45
• 002:1763 RN50_MAINT_46
• 002:1764 RN50_MAINT_47
• 002:1766 RN50_MAINT_49
• 002:1768 RN50_MAINT_50
• 002:1769 RN50_MAINT_51
• 002:1770 RN50_MAINT_52
• 002:1771 RN50_MAINT_53
• 002:1772 RN50_MAINT_54
• 002:1773 RN50_MAINT_55
• 002:1774 RN50_MAINT_56
• 002:1777 RN50_MAINT_59
• 002:1778 RN50_MAINT_60
• 002:1779 RN5_EP1_FUNCTION_CTRL
• 002:1815 HSUPA_IC
• 002:1841 PS_GTP_CAPA_STEP_1
• 002:1845 PS_GTP_BYTES_AVG_PERIOD
• 002:1855 CONV_IN_ACTIVATION
• 002:1863 HSPA_OVER_IUR
• 002:1866 CERM_CONF_DATA
• 002:1876 RN60_MAINT_20
• 002:1877 RN60_MAINT_01
• 002:1878 RN60_MAINT_02
• 002:1879 RN60_MAINT_03
• 002:1880 RN60_MAINT_04
• 002:1881 RN60_MAINT_05
• 002:1882 RN60_MAINT_06
• 002:1883 RN60_MAINT_07
• 002:1884 RN60_MAINT_08
• 002:1885 RN60_MAINT_09
• 002:1887 RN60_MAINT_11
• 002:1890 RN60_MAINT_14
• 002:1891 RN60_MAINT_15

• 002:1893 RN60_MAINT_17
• 002:1894 RN60_MAINT_18
• 002:1895 RN60_MAINT_19
• 002:1896 RN60_MAINT_21
• 002:1898 RN60_MAINT_23
• 002:1899 RN60_MAINT_24
• 002:1906 RN60_MAINT_30
• 002:1907 RN60_MAINT_31
• 002:1909 RN60_MAINT_33
• 002:1910 RN60_MAINT_34
• 002:1911 RN60_MAINT_35
• 002:1917 RN60_MAINT_42
• 002:1919 RN60_MAINT_43
• 002:1920 RN60_MAINT_44
• 002:1921 RN60_MAINT_45
• 002:1922 RN60_MAINT_46
• 002:1923 RN60_MAINT_47
• 002:1924 RN60_MAINT_48
• 002:1925 RN60_MAINT_49
• 002:1926 RN60_MAINT_50
• 002:1927 RN60_INT_FEAT_RES_01
• 002:1928 RN60_INT_FEAT_RES_02
• 002:1933 RN60_INT_FEAT_RES_04
• 002:1934 RN60_INT_FEAT_RES_05
• 002:1936 RN60_INT_FEAT_RES_07
• 002:1937 RN60_INT_FEAT_RES_08
• 002:1938 RN60_INT_FEAT_RES_09
• 002:1955 DISABLE_HSPA_CONGESTION
• 002:1957 DISABLE_HS_CCH_REBAL
• 002:1958 DISABLE_CELL_HOME_REBAL
• 002:1967 H248_CGR_HB_SUP_IN_MGW
• 002:1993 EXTENDED_RNCID_IN_USE
• 002:2015 TDM_HUNTING_QUEUE_SIZE
• 002:2018 DYNAMIC_HSUPA_BLER
• 002:2039 FAST_CELL_PCH_SWITCHING
• 002:2053 UE_DRX_CELL_FACH
• 002:2063 THRPUT_REPORTING_TIMER
• 002:2064 BTS_LOGGING_ENAB
• 002:2067 MIN_RE_EDPDCH_GF_VAL
• 002:2069 ETWSREPETITION
• 002:2077 ETWSSEQUENCINGINTERVAL
• 002:2086 RTP_SEQ_CHK
• 002:2089 REBAL_UE_TIMER
• 002:2093 GIVAXI_PORT
• 002:2104 RU40_MAINT_08
• 002:2106 RU40_MAINT_10
• 002:2108 RU40_MAINT_12

• 002:2114 RU40_MAINT_18
• 002:2116 RU40_MAINT_20
• 002:2118 RU40_MAINT_22
• 002:2120 RU40_MAINT_24
• 002:2123 RU40_MAINT_27
• 002:2127 RU40_MAINT_31
• 002:2130 RU40_MAINT_34
• 002:2133 RU40_MAINT_37
• 002:2135 RU40_MAINT_39
• 002:2137 RU40_MAINT_41
• 002:2138 RU40_MAINT_42
• 002:2145 RU40_MAINT_49
• 002:2147 RU40_MAINT_51
• 002:2149 RU40_MAINT_53
• 002:2150 RU40_MAINT_54
• 002:2153 RU40_MAINT_57
• 002:2154 RU40_MAINT_58
• 002:2155 RU40_MAINT_59
• 002:2156 RU40_MAINT_60
• 002:2157 RU40_MAINT_61
• 002:2158 RU40_MAINT_62
• 002:2159 RU40_MAINT_63
• 002:2160 RU40_MAINT_64
• 002:2161 RU40_MAINT_65
• 002:2162 RU40_MAINT_66
• 002:2163 RU40_MAINT_67
• 002:2164 RU40_MAINT_68
• 002:2165 RU40_MAINT_69
• 002:2166 RU40_MAINT_70
• 002:2167 RU40_MAINT_71
• 002:2168 RU40_MAINT_72
• 002:2169 RU40_MAINT_73
• 002:2170 RU40_MAINT_74
• 002:2171 RU40_MAINT_75
• 002:2172 RU40_MAINT_76
• 002:2173 RU40_MAINT_77
• 002:2174 RU40_MAINT_78
• 002:2175 RU40_MAINT_79
• 002:2176 RU40_MAINT_80
• 002:2263 RU50_SPARE_01
• 002:2270 RU50_SPARE_08
• 002:2271 RU50_SPARE_09
• 002:2274 RU50_SPARE_12
• 002:2275 RU50_SPARE_13
• 002:2279 RU50_SPARE_17
• 002:2280 RU50_SPARE_18
• 002:2294 MSG_QUE_TPUT_TIME

• 002:2295 UNIT_LOAD_CTRL_LIMITS
• 002:2327 HSRACH_OC_THRESHOLD
• 002:2328 AQM_MIN_BUF_THRESHOLD
• 002:2364 USPU_SCALE_IN_NVCA
• 002:2365 USPU_SCALE_IN_HO
• 002:2366 USPU_SCALE_IN_MAX_TIME
• 002:2367 CSPU_SCALE_IN_NVCA
• 002:2368 CSPU_SCALE_OUT_NVCA
• 002:2369 CSPU_SCALING_HO
• 002:2375 SIR_TARGET_CTRL_PARAM
• 002:2386 CCH_LP_RESCHEDULE_COUNT
• 002:2387 UDC_INTERNAL_CONFIG
• 002:2389 DEMADDITIONALCONFIG
• 002:2390 DEMREPORTCONFIGURATION
• 002:2393 IMSI_BASE_LTEHO_ENABLED

• 002:2506 DOS_CONFIG_PARAMS_1
• 002:2517 QUEUE_TIME_OPT
• 002:2563 NPMXUSAMPINTERVAL
• 002:2564 SAMPCOUNTOFMXU
• 002:2565 NPMXUERRCOUNTTHR
• 002:2566 NPDSPRATIOPERMXU
• 002:2567 FAILRATIOPERDSP
• 002:2568 CELL_HOME_CONCEPT
• 002:2569 RECOV_TRIGG_CSPU_REBAL
• 002:2581 KASUMI_CONFIGURATION
• 002:2592 ICIC_ICLC_CONTROL_1

Class 007.
• 007:0165 IU_CR_INCLUDED
• 007:0193 RN21_MAINT_001
• 007:0194 RN21_MAINT_002
• 007:0196 RN21_MAINT_004
• 007:0197 RN21_MAINT_005
• 007:0198 RN21_MAINT_006
• 007:0199 RN21_MAINT_007
• 007:0200 RN21_MAINT_008
• 007:0201 RN21_MAINT_009
• 007:0202 RN21_MAINT_010
• 007:0209 RNC_MAINT_002

• 007:0210 RNC_MAINT_003
• 007:0211 RNC_MAINT_004
• 007:0212 RNC_MAINT_005
• 007:0213 RNC_MAINT_006
• 007:0214 RNC_MAINT_007
• 007:0215 RNC_MAINT_008
• 007:0216 RNC_MAINT_009
• 007:0217 RNC_MAINT_010
• 007:0224 RN30_MAINT_001
• 007:0225 RN30_MAINT_002
• 007:0226 RN30_MAINT_003
• 007:0228 RN30_MAINT_005
• 007:0229 RN30_MAINT_006
• 007:0230 RN30_MAINT_007
• 007:0231 RN30_MAINT_008
• 007:0232 RN30_MAINT_009
• 007:0233 RN30_MAINT_010
• 007:0234 RN30_MAINT_011
• 007:0235 RN30_MAINT_012
• 007:0236 RN30_MAINT_013
• 007:0237 RN30_MAINT_014
• 007:0244 RN30_MAINT_021
• 007:0245 RN30_MAINT_022
• 007:0247 RN30_MAINT_024
• 007:0248 RN30_MAINT_025
• 007:0249 RN30_MAINT_026
• 007:0250 RN30_MAINT_027
• 007:0251 RN30_MAINT_028
• 007:0252 RN30_MAINT_029
• 007:0271 RN40_MAINT_003
• 007:0272 RN40_MAINT_004
• 007:0274 RN40_MAINT_005
• 007:0275 RN40_MAINT_006
• 007:0276 RN40_MAINT_007
• 007:0278 RN40_MAINT_008
• 007:0282 RN40_MAINT_012
• 007:0288 RN40_MAINT_018
• 007:0289 RN40_MAINT_019
• 007:0292 RN40_MAINT_022
• 007:0293 RN40_MAINT_024
• 007:0294 RN40_MAINT_023
• 007:0298 RN40_MAINT_028
• 007:0300 RN40_MAINT_030
• 007:0301 RN40_MAINT_031
• 007:0302 RN40_MAINT_032
• 007:0303 RN40_MAINT_033
• 007:0305 RN40_MAINT_035

• 007:0309 RN40_MAINT_039
• 007:0310 RN40_MAINT_040
• 007:0365 RNC_L3_CONTROL_001
• 007:0366 RNC_L3_CONTROL_002
• 007:0367 RNC_L3_CONTROL_003
• 007:0369 RNC_L3_CONTROL_004
• 007:0370 RNC_L3_CONTROL_005
• 007:0371 RNC_L3_CONTROL_006
• 007:0372 RNC_L3_CONTROL_007
• 007:0373 RNC_L3_CONTROL_008
• 007:0374 RNC_L3_CONTROL_009
• 007:0375 RNC_L3_CONTROL_010
• 007:0376 RNC_L3_CONTROL_011
• 007:0377 RNC_L3_CONTROL_012
• 007:0378 RNC_L3_CONTROL_013
• 007:0379 RNC_L3_CONTROL_014
• 007:0380 RNC_L3_CONTROL_015
• 007:0381 RNC_L3_CONTROL_016
• 007:0382 RNC_L3_CONTROL_017
• 007:0383 RNC_L3_CONTROL_018
• 007:0384 RNC_L3_CONTROL_019
• 007:0385 RNC_L3_CONTROL_020
• 007:0386 RNC_L3_CONTROL_021
• 007:0392 RNC_L3_CONTROL_027
• 007:0393 RNC_L3_CONTROL_028
• 007:0395 RNC_L3_CONTROL_030
• 007:0396 RNC_L3_CONTROL_031
• 007:0397 RNC_L3_CONTROL_032
• 007:0399 RNC_L3_CONTROL_034
• 007:0400 RNC_L3_CONTROL_035
• 007:0401 RNC_L3_CONTROL_036
• 007:0402 RNC_L3_CONTROL_037
• 007:0403 RNC_L3_CONTROL_038
• 007:0404 RNC_L3_CONTROL_039
• 007:0405 RNC_L3_CONTROL_040
• 007:0450 T323
• 007:0481 MIN_CPU_LOAD_TRIG_THR
• 007:0482 CPU_LOAD_DIFF_THR
• 007:0483 MINRRCHANDCOUNTTRIGTHR
• 007:0484 RRCHANDCOUNTDIFFTHR
• 007:0498 SIMULT_L2_RES_ENABLED
• 007:0501 OVERALL_L2UTILTHRES_MED
• 007:0503 OVERALL_L2UTILTHRES_LOW
• 007:0504 FACH_ACT_TIMERFACTORMED
• 007:0505 FACH_ACT_TIMERFACTORLOW
• 007:0517 HRNTIFACTORFORHSCELLPCH


Class 009.
• 009:0010 CRC4_TRH_FOR_DEGRAD_MIN
• 009:0011 CRC4_TRH_FOR_ERRORE_SEC
• 009:0028 SEC_EVENT_ALARM_LIMIT
• 009:0029 SEC_EVENT_MON_PERIOD
• 009:0049 BITMAP_CHECK_RECORDS
• 009:0050 BITMAP_CHECK_BYTES
• 009:0051 BITMAP_SUPERV_INTERVAL
• 009:0052 CHKSUM_SUPERV_INTERVAL
• 009:0088 STAT_REP_BACK_COMP
• 009:0137 SEC_EVENT_LOAD_LIMIT
• 009:0138 SEC_EVENT_UNSUC_LIMIT
• 009:0181 OPERA_FEEDBACK_INTERVAL

Class 010.
• 010:0004 PCM_MAINT_ANNOUNCE_TL

Class 012.
• 012:0039 NAMETBL_MAX_SERV
• 012:0079 NAMETBL_INCREMENT
• 012:0081 AAL2_OLC_ENABLED

Class 016.
• 016:0016 USERPLANE_ERR_THRESHOLD

Class 038.

• 038:0000 WRITE_CACHE_TIMEOUT
• 038:0002 MAX_FILE_COUNT
• 038:0003 ADMINISTRATION_HOUR
• 038:0004 ADMINISTRATION_MINUTES

Class 043.
• 043:0009 USED_TONE_SET

Class 044.
• 044:0000 PW_CHAR_TO_PRINT
• 044:0001 FIRST_MMI_LOGIN_DELAY
• 044:0002 MAX_MMI_LOGIN_DELAY
• 044:0003 OVERFLOW_LOGIN_DELAY
• 044:0005 DISCLAIMER_TEXT
• 044:0006 DEF_MAIN_HEADING_TEXT

Class 050.
• 050:0001 MEA_REPORT_FORMATS
• 050:0002 OMES_REPORT_FORMATS
• 050:0003 PERM_PDH_STATISTICS

Class 053.
• 053:0009 DSCP_FOR_SIGNALLING

Class 055.
• 055:00014 ADIF_INTERFACE


Class 056.
• 056:0000 LOG_ON

Class 058.
• 058:0004 USER_ACCOUNT_LOCK_LIMIT

Class 060.
• 060:0013 NE3S_UM
• 060:0016 NE3S
• 060:0019 MGW_SW_RELEASE

Class 065.
• 065:0000 MGW_LICENCE_WL_HYSTERES
• 065:0001 MGW_LIS_CON_CAPA_HYSTER
• 065:0002 MGW_LIS_CON_CAPA_WL
• 065:0003 MGW_IU_PORT_CAPA_HYSTE
• 065:0004 MGW_IU_PORT_CAPA_WL
• 065:0005 MGW_IUIP_PORT_CAPA_HYST
• 065:0006 MGW_IUIP_PORT_CAPA_WL
• 065:0007 MGW_NB_PORT_CAPA_HYSTE
• 065:0008 MGW_NB_PORT_CAPA_WL
• 065:0009 MGW_MB_PORT_CAPA_HYSTE
• 065:0010 MGW_MB_PORT_CAPA_WL
• 065:0011 MGW_ATER_PORT_CAPA_HYST
• 065:0012 MGW_ATER_PORT_CAPA_WL
• 065:0013 MGW_EC_CAPA_HYST
• 065:0014 MGW_EC_CAPA_WL
• 065:0015 MGW_AIP_PORT_CAPA_HYSTE
• 065:0016 MGW_AIP_PORT_CAPA_WL
• 065:0017 MGW_LTE_PORT_CAPA_HYST

• 065:0018 MGW_LTE_PORT_CAPA_WL

Class 069.
• 069:0001 CSUP_AUTO_RECOVERY_TIME

WCDMA19 Prfile Descriptions W19P8 08A APPR

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WCDMA19 Prfile Descriptions W19P8 08A APPR

Uploaded by

Copyright:

Available Formats

PRFILE Descriptions

f Important Notice on Product Safety

2.127 002:2264 RU50_SPARE_02...................................................... 139

5.7 016:0009 WBTS_LEVEL_ALARM_SWITCH............................. 229

Changes between issues 08 (2018-11-02, WCDMA19) and 08A (2019-02-06,

Changes between issues 07E (2018-10-16, WCDMA18) and 08 (2018-11-02,

Delta between current and last release

1 Overview of PRFILE descriptions

1.1 Modifying PRFILE parameters

Select from the available options

Select from the available options

2 Parameter class 002

2.1 002:0621 RNW_DATA_1

Default value Forbidden value(s)

2.2 002:0740 RNW_DATA_2

Default value Forbidden value(s)

2.3 002:0840 TIMER_ERQ

Allowed value(s) Effect

Default value Forbidden value(s)

2.4 002:0841 TIMER_REL

Allowed value(s) Effect

Default value Forbidden value(s)

2.5 002:0842 TIMER_MOD

Allowed value(s) Effect

Default value Forbidden value(s)

2.6 002:1047 AAL2_NNI_CONN_REL_TIMER

Allowed value(s) Effect

Default value Forbidden value(s)

2.7 002:1248 NE_LOGICAL_CONFIGURATION

Allowed value(s) Effect

Default value Forbidden value(s)

2.8 002:1296 RN22_FEATURE_OPT_009

For more details and activation instructions, see Features RAN1302, RAN1810 and

Allowed value(s) Effect

Default value Forbidden value(s)

For dependencies on other parameters, see Features RAN1302, RAN1810 and

2.9 002:1297 RN22_FEATURE_OPT_008

Allowed value(s) Effect

Default value Forbidden value(s)

2.10 002:1300 RN22_FEATURE_OPT_004

Allowed value(s) Effect

Default value Forbidden value(s)

2.11 002:1370 AMR_LIC_WARN_IN_USE

Allowed value(s) Effect

Default value Forbidden value(s)

2.12 002:1371 AMR_LIC_WARN_THRESHOLD

Allowed value(s) Effect

Default value Forbidden value(s)

2.13 002:1372 AMR_LIC_WARN_DUR

Allowed value(s) Effect

Default value Forbidden value(s)

2.14 002:1373 AMR_LIC_WARN_DUR_CANCEL

Allowed value(s) Effect

Default value Forbidden value(s)

2.15 002:1374 AMR_LIC_ALARM_IN_USE

Allowed value(s) Effect

Default value Forbidden value(s)

2.16 002:1375 AMR_LIC_ALARM_DUR_CAL

Allowed value(s) Effect

Default value Forbidden value(s)

2.17 002:1376 PS_LIC_WARN_IN_USE

Allowed value(s) Effect

Allowed value(s) Effect

Default value Forbidden value(s)