262433688 prfile descriptions issue 03f by Emerson Rodrigues Setim

PRFILE Descriptions DN0948854 Issue 03F Approval Date 2014-05-07 Â

PRFILE Descriptions

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR 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. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Solutions and Networks 2014. All rights reserved

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 Solutions and Networks 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 Solutions and Networks for any additional information.

DN0948854

Issue: 03F

PRFILE Descriptions

Table of Contents This document has 171 pages

Summary of changes..................................................................... 8

Issue: 03F

Introduction to PRFILE and FIFILE parameters...........................10

2 2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 2.1.9 2.1.10 2.1.11 2.1.12 2.1.13 2.1.14 2.1.15 2.1.16 2.1.17 2.1.18 2.1.19 2.1.20 2.1.21 2.1.22 2.1.23 2.1.24 2.1.25 2.1.26 2.1.27 2.1.28 2.1.29 2.1.30 2.1.31 2.1.32 2.1.33 2.1.34 2.1.35 2.1.36

PRFILE and FIFILE parameter descriptions................................ 12 Parameter class 002 SYSTEM_FUNCT_CONFIGUR................. 12 Parameter 002:0621 RNW_DATA_1............................................12 Parameter 002:0740 RNW_DATA_2............................................13 Parameter 002:0840 TIMER_ERQ.............................................. 13 Parameter 002:0841 TIMER_REL............................................... 14 Parameter 002:0842 TIMER_MOD..............................................15 Parameter 002:1047 AAL2_NNI_CONN_REL_TIMER................15 Parameter 002:1248 NE_LOGICAL_CONFIGURATION............. 16 Parameter 002:1296 RN22_FEATURE_OPT_009...................... 17 Parameter 002:1297 RN22_FEATURE_OPT_008...................... 18 Parameter 002:1300 RN22_FEATURE_OPT_004...................... 18 Parameter 002:1370 AMR_LIC_WARN_IN_USE........................ 19 Parameter 002:1371 AMR_LIC_WARN_THRESHOLD...............20 Parameter 002:1372 AMR_LIC_WARN_DUR............................. 21 Parameter 002:1373 AMR_LIC_WARN_DUR_CANCEL.............22 Parameter 002:1374 AMR_LIC_ALARM_IN_USE...................... 23 Parameter 002:1375 AMR_LIC_ALARM_DUR_CAL...................24 Parameter 002:1376 PS_LIC_WARN_IN_USE........................... 24 Parameter 002:1377 PS_LIC_WARN_THRESHOLD.................. 25 Parameter 002:1378 PS_LIC_WARN_DUR................................ 26 Parameter 002:1379 PS_LIC_WARN_DUR_CANCEL................27 Parameter 002:1380 PS_LIC_ALARM_IN_USE..........................28 Parameter 002:1381 PS_LIC_ALARM_DUR_CAL......................29 Parameter 002:1546 ICSU_WINDOW_SIZE............................... 29 Parameter 002:1632 HSUPA_SERVICE_INDICATOR................ 30 Parameter 002:1649 IP_LINK_BREAK_REL_DELAY................. 31 Parameter 002:1662 REVERTIVE_SWO_IN_USE......................32 Parameter 002:1664 RN50_MAINT_02....................................... 33 Parameter 002:1666 RN50_MAINT_03....................................... 34 Parameter 002:1668 RN50_MAINT_05....................................... 34 Parameter 002:1669 RN50_MAINT_06....................................... 35 Parameter 002:1670 RN50_MAINT_07....................................... 36 Parameter 002:1671 RN50_MAINT_08....................................... 36 Parameter 002:1673 RN50_MAINT_10....................................... 37 Parameter 002:1684 RN50_MAINT_11....................................... 38 Parameter 002:1686 RN50_MAINT_13....................................... 38 Parameter 002:1687 RN50_MAINT_14....................................... 39

DN0948854

PRFILE Descriptions

2.1.37 2.1.38 2.1.39 2.1.40 2.1.41 2.1.42 2.1.43 2.1.44 2.1.45 2.1.46 2.1.47 2.1.48 2.1.49 2.1.50 2.1.51 2.1.52 2.1.53 2.1.54 2.1.55 2.1.56 2.1.57 2.1.58 2.1.59 2.1.60 2.1.61 2.1.62 2.1.63 2.1.64 2.1.65 2.1.66 2.1.67 2.1.68 2.1.69 2.1.70 2.1.71 2.1.72 2.1.73 2.1.74 2.1.75 2.1.76 2.1.77 2.1.78 2.1.79 2.1.80 2.1.81

Parameter 002:1689 RN50_MAINT_15....................................... 40 Parameter 002:1691 RN50_MAINT_16....................................... 41 Parameter 002:1696 RN50_MAINT_20....................................... 41 Parameter 002:1697 RN50_MAINT_21....................................... 42 Parameter 002:1699 RN50_MAINT_23....................................... 43 Parameter 002:1700 RN50_MAINT_24....................................... 44 Parameter 002:1701 RN50_MAINT_25....................................... 45 Parameter 002:1702 RN50_MAINT_26....................................... 46 Parameters 002:1703 RN50_MAINT_27 and 002:1704 RN50_MAINT_28.........................................................................48 Parameter 002:1706 RN50_MAINT_29....................................... 50 Parameter 002:1716 RN50_MAINT_38....................................... 51 Parameter 002:1717 RN50_MAINT_39....................................... 53 Parameter 002:1760 RN50_MAINT_43....................................... 54 Parameter 002:1765 RN50_MAINT_48....................................... 55 Parameter 002:1775 RN50_MAINT_57....................................... 56 Parameter 002:1776 RN50_MAINT_58....................................... 58 Parameter 002:1792 UP_CAP_UPGRADE................................. 59 Parameter 002:1798 OPT_BLOCK_MOVE_PREVENT.............. 60 Parameter 002:1814 LCH_IN_USE............................................. 61 Parameter 002:1816 IPMUX_MUX_DELAY.................................62 Parameter 002:1817 DYNPWROFFSETUSAGE.........................63 Parameter 002:1818 LCH_TRAN_IN_USE................................. 64 Parameter 002:1819 LCH_DIR_SIZE.......................................... 65 Parameter 002:1840 B_PHASE1_SWITCH.................................65 Parameter 002:1876 RN60_MAINT_20....................................... 66 Parameter 002:1886 RN60_MAINT_10....................................... 67 002:1868 EDPDCHPowerInterUsage ......................................... 68 Parameter 002:1888 RN60_MAINT_12....................................... 69 Parameter 002:1889 RN60_MAINT_13....................................... 71 Parameter 002:1892 RN60_MAINT_16....................................... 72 Parameter 002:1897 RN60_MAINT_22....................................... 72 Parameter 002:1900 RN60_MAINT_25....................................... 73 Parameter 002:1902 RN60_MAINT_26....................................... 74 Parameter 002:1904 RN60_MAINT_28....................................... 75 Parameter 002:1905 RN60_MAINT_29....................................... 77 Parameter 002:1906 RN60_MAINT_30....................................... 78 Parameter 002:1912 RN60_MAINT_36....................................... 80 Parameter 002:1913 RN60_MAINT_38....................................... 81 Parameter 002:1914 RN60_MAINT_39....................................... 83 Parameter 002:1915 RN60_MAINT_40....................................... 84 Parameter 002:1916 RN60_MAINT_41....................................... 85 Parameter 002:1918 RN60_MAINT_37....................................... 87 Parameter 002:1935 RN60_INT_FEAT_RES_06........................ 88 Parameter 002:1939 RN60_INT_FEAT_RES_10........................ 89 Parameter 002:2066 MIN_RE_EDPDCH_GF_TO_BTS..............90

DN0948854

Issue: 03F

PRFILE Descriptions

2.1.82 2.1.83 2.1.84 2.1.85 2.1.86 2.1.87 2.1.88 2.1.89 2.1.90 2.1.91 2.1.92 2.1.93 2.1.94 2.1.95 2.1.96 2.1.97 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.2.7 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 2.2.15 2.2.16 2.2.17 2.2.18 2.2.19 2.2.20 2.2.21 2.2.22 2.2.23 2.2.24 2.2.25 2.2.26 2.2.27 2.2.28 2.2.29

Issue: 03F

Parameter 002:2067 MIN_RE_EDPDCH_GF_VAL..................... 91 Parameter 002:2095 RU40_MAINT_01....................................... 93 Parameter 002:2098 RU40_MAINT_02 (case 1)......................... 94 Parameter 002:2098 RU40_MAINT_02 (case 2)......................... 95 Parameter 002:2099 RU40_MAINT_03....................................... 96 Parameter 002:2101 RU40_MAINT_05....................................... 97 Parameter 002:2102 RU40_MAINT_06....................................... 98 Parameter 002:2103 RU40_MAINT_07....................................... 99 Parameter 002:2105 RU40_MAINT_09..................................... 100 Parameter 002:2107 RU40_MAINT_11..................................... 101 Parameter 002:2109 RU40_MAINT_13 .................................... 102 Parameter 002:2110 RU40_MAINT_14 .................................... 104 Parameter 002:2111 RU40_MAINT_15......................................105 Parameter 002:2113 RU40_MAINT_17..................................... 107 Parameter 002:2115 RU40_MAINT_19 .................................... 108 Parameter 002:2117 RU40_MAINT_21......................................110 Parameter class 007 CALL_CONTROL..................................... 113 Parameter 007:0174 CN_INFORMATION_INFO....................... 113 Parameter 007:0191 JAPAN_UE_CONTROL............................114 Parameter 007:0195 RN21_MAINT_003................................... 115 Parameter 007:0208 RNC_MAINT_001.....................................116 Parameter 007:0238 RN30_MAINT_015................................... 117 Parameter 007:0239 RN30_MAINT_016................................... 117 Parameter 007:0240 RN30_MAINT_017................................... 118 Parameter 007:0241 RN30_MAINT_018................................... 119 Parameter 007:0242 RN30_MAINT_019................................... 120 Parameter 007:0243 RN30_MAINT_020................................... 121 Parameter 007:0269 RN40_MAINT_001................................... 122 Parameter 007:0270 RN40_MAINT_002................................... 123 Parameter 007:0279 RN40_MAINT_009................................... 124 Parameter 007:0280 RN40_MAINT_010................................... 125 Parameter 007:0281 RN40_MAINT_011................................... 126 Parameter 007:0283 RN40_MAINT_013................................... 127 Parameter 007:0284 RN40_MAINT_014................................... 128 Parameter 007:0285 RN40_MAINT_015................................... 129 Parameter 007:0286 RN40_MAINT_016................................... 130 Parameter 007:0287 RN40_MAINT_017................................... 131 Parameter 007:0290 RN40_MAINT_020................................... 132 Parameter 007:0291 RN40_MAINT_021................................... 133 Parameter 007:0295 RN40_MAINT_025................................... 133 Parameter 007:0296 RN40_MAINT_026................................... 134 Parameter 007:0297 RN40_MAINT_027................................... 135 Parameter 007:0299 RN40_MAINT_029................................... 136 Parameter 007:0304 RN40_MAINT_034................................... 137 Parameter 007:0306 RN40_MAINT_036................................... 138 Parameter 007:0307 RN40_MAINT_037................................... 139

DN0948854

PRFILE Descriptions

2.2.30 2.2.31 2.2.32 2.2.33 2.2.34 2.2.35 2.2.36 2.2.37 2.2.38 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.6 2.4.7 2.4.8 2.4.9 2.4.10 2.4.11 2.4.12 2.4.13 2.5 2.5.1 2.6 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7 2.7.1

Parameter 007:0308 RN40_MAINT_038................................... 140 Parameter 007:0387 RNC_L3_CONTROL_022........................ 141 Parameter 007:0388 RNC_L3_CONTROL_023........................ 142 Parameter 007:0389 RNC_L3_CONTROL_024........................ 143 Parameter 007:0390 RNC_L3_CONTROL_025........................ 145 Parameter 007:0391 RNC_L3_CONTROL_026........................ 147 Parameter 007:0394 RNC_L3_CONTROL_029........................ 148 Parameter 007:0397 RNC_L3_CONTROL_032........................ 149 Parameter 007:0398 RNC_L3_CONTROL_033........................ 150 Parameter class 009 SYSTEM_SUPERVISION........................ 151 Parameter 009:0101 IUB_DATA_RECV_INTERVAL................. 151 Parameter 009:0102 IUB_CONN_POLLING_TIME...................152 Parameter 009:0130 IP_MSG_MON......................................... 153 Parameter class 016 ALARM_SYSTEM.................................... 155 Parameter 016:0000 ALARM_PRINT_END_MARK.................. 155 Parameter 016:0001 LAMP_PANEL_POLARITY...................... 156 Parameter 016:0002 ALARM_DRIVEN_OUTPUTS.................. 156 Parameter 016:0003 LAMP_PANEL_BUZZER..........................157 Parameter 016:0004 PRINTING_MODE................................... 158 Parameter 016:0008 HEARTBEAT_ALM_INTERVAL................159 Parameter 016:0009 WBTS_LEVEL_ALARM_SWITCH........... 160 Parameter 016:0010 SUSPEND_MODE_SWITCH................... 161 Parameter 016:0011 WCEL_OUT_OF_USE_NUM................... 161 Parameter 016:0012 HSPA_ACT_FAIL_NUM........................... 162 Parameter 016:0013 RNW_DATABASE_FAIL_NUM.................163 Parameter 016:0014 WBTS_LEVEL_ALARM_NUM................. 164 Parameter 016:0015 BUFFER_ALARM_THRESHOLD............ 165 Parameter class 038 MML_COMMAND_LOG...........................165 Parameter 038:0001 STORAGE_LENGTH............................... 166 Parameter class 055 LCS_PARAMETERS................................166 Parameter 055:0003 EMERGENCY_CALL_ISHO_SUP........... 167 Parameter 055:0011 AGPS_SUPPORT.................................... 168 Parameter 055:0012 INT_EMERG_CALL_ISHO_SUP............. 168 Parameter 055:0013 NW_AGPS_SUPPORT............................ 169 Parameter 055:0015 IUPC_INTERFACE...................................170 Parameter class 058 OAM_SECURITY.....................................171 Parameters 058:0000 PW_POLICY_FEATURE, 058:0001 UA_POLICY_FEATURE, 058:0004 USER_ACCOUNT_LOCK_LIMIT.............................................. 171

DN0948854

Issue: 03F

PRFILE Descriptions

List of Tables Table 1

Issue: 03F

Supported parameters......................................................................154

DN0948854

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 03E (2014-03-07, RU40) and 03F (2014-0507, RU40) This issue of the document is valid for RN7.0 3.0 SW, mcRNC3.0 2.0 SW and ADA5.0 1.0 SW. • • • •

Parameter 002:1993 EXTENDED_RNCID_IN_USE has been removed. The feature control has been moved to Parameter 007:0394 RNC_L3_CONTROL_029. Parameter 002:1864 HSPA_OVER_IUR_EXT has been removed. Parameter 002:0241 RNW_DATA_1 has been removed. Parameter 053:0009 DSCP_FOR_SIGNALLING has been removed.

Parameter 002:1876 RN60_MAINT_20 •

Parameter 002:1876 RN60_MAINT_20 has been added.

Parameter 002:2111 RU40_MAINT_15 •

Parameter 002:2111 RU40_MAINT_15 has been added.

Parameter 002:2113 RU40_MAINT_17 •

Parameter 002:2113 RU40_MAINT_17 has been added.

Parameter 002:2117 RU40_MAINT_21 •

Parameter 002:2117 RU40_MAINT_21 has been added.

Parameter 007:0394 RNC_L3_CONTROL_029 •

Parameter 007:0394 RNC_L3_CONTROL_029 has been added.

Changes between issues 03D (2014-01-27, RU40) and 03E (2014-0307, RU40) This issue of the document is valid for RN7.0 2.1 SW, mcRNC3.0 1.0 SW and ADA5.0 1.0 SW. Parameter 002:2115 RU40_MAINT_19 •

Parameter 002:2115 RU40_MAINT_19 has been added.

Changes between issues 03C (2013-10-31, RU40) and 03D (2014-0127, RU40) This issue of the document is valid for RN7.0 2.0 SW, mcRNC3.0 1.0 SW and ADA5.0 1.0 SW. The following parameters have been updated: •

Parameter 002:1906 RN60_MAINT_30

The following parameters have been added: •

Parameter 002:2109 RU40_MAINT_13

DN0948854

Issue: 03F

PRFILE Descriptions

Summary of changes

•

Parameter 002:2110 RU40_MAINT_14

The following parameters have been removed: • • •

Issue: 03F

Parameter 002:1938 RN60_INT_FEAT_RES_09 Parameter 007:0249 RN30_MAINT_026 Parameter 007:0301 RN40_MAINT_031

DN0948854

Introduction to PRFILE and FIFILE parameters

PRFILE Descriptions

1 Introduction to PRFILE and FIFILE parameters Purpose The system has a group of features which are not included in the basic software of the network element delivery. The customer can choose them to be included in the software. All the information about controlling these features is assembled in the network element in the PRFILE (General Parameter File) and FIFILE (Feature Information Control File). Scope This document describes the PRFILE (General Parameter File) and FIFILE (Feature Information Control File) parameters used in the IPA-RNC, mcRNC and Flexi Direct RNC. Only the parameters that are intended for modification at the IPA-RNC, mcRNC and Flexi Direct RNC level are listed in this document. The parameters are organized into parameter classes, each of which represents a specific functional area. The description of an individual parameter includes the following information: •

• • •

•

• •

Identifier: consists of the parameter class number and parameter number (for example, 002:0433), and of the parameter's official name, which is used, for example, in MML printouts. Descriptive name: The name of the parameter in plain text form. Description: A description of the purpose and function of the parameter. Indication of whether the parameter is modifiable: Modifiable parameters have been marked with a YES indicator, which shows that the parameter value can be changed by using the WOC command of the Parameter Handling MML. In case of FIFILE parameters, the indicator is ON/OFF. If the feature is delivered to the customer, the default value of the parameter is OFF, that is, the feature has to be activated before it can be used. The value can be changed from OFF into ON by using the WOA command. During a software upgrade, the values of changeable parameters are copied from the network element's old software build into the new one using the PRFCNV/FIFCNV conversion. In this way, the customer's settings are kept intact during the software upgrade. Default value, allowed values and forbidden values: The values are documented in decimal (D), hexadecimal (H) or binary numbers (B), but in user interface the values are only handled as hexadecimal values. The boolean values TRUE/FALSE compare to the hexadecimal values 0FFH/0, and the bool values T/F to the decimal values 1/0, respectively. Increments: A multiple of allowed values. Dependence: Name of a feature on which the parameter is dependent. This means that the parameter is effective only if the operator has bought the feature in question.

A feature parameter is not visible if the feature is not delivered to the customer. Further information and parameter handling Only a description of the parameters and parameter classes included in this software release are given here. In IPA-RNC, MML commands are used to handle PRFILE parameters: •

interrogating parameter value can be done with the ZWOI command:

DN0948854

Issue: 03F

PRFILE Descriptions

Introduction to PRFILE and FIFILE parameters

•

syntax: ZWOI:<parameter class>,<parameter number>; example: ZWOI:7,272; changing parameter value can be done with the ZWOC command: syntax: ZWOC:<parameter class>,<parameter number>,<HEX parameter value>; example: ZWOC:7,272,0;

For more detailed instructions on how the parameters are handled in IPA-RNC, see Interrogating and modifying PRFILE and FIFILE parameters in Managing IPA-RNC Software Configuration and WO-Parameter Handling. In mcRNC and Flexi Direct RNC, sCLI commands are used to handle PRFILE parameters: •

•

interrogating parameter value can be done with the show app-parameter command: syntax: show app-parameter configuration-parameter class <parameter class> number <parameter number> example: show app-parameter configuration-parameter class 7 number 272 changing parameter value can be done with the set app-parameter command: syntax: set app-parameter configuration-parameter class <parameter class> number <parameter number> value 0x<HEX parameter value> example: set app-parameter configuration-parameter class 7 number 272 value 0x0

For more detailed instructions on how the parameters are handled in mcRNC, see Configuring PRFILE and FIFILE parameters in Managing Multicontroller RNC Software Configuration. For more information on sCLI commands, see WCDMA Flexi Direct RNC SCLI Commands.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2 PRFILE and FIFILE parameter descriptions Here are listed the descriptions of the PRFILE and FIFILE parameters.

2.1 Parameter class 002 SYSTEM_FUNCT_CONFIGUR Descriptive Name System functions configuration

Description Parameters in this class specify the functional configuration of each delivery, that is the functions that are included or excluded.

2.1.1 Parameter 002:0621 RNW_DATA_1 Descriptive name Radio network parameter

Applicable controllers IPA-RNC from RN5.0 onwards mcRNC from mcRNC2.0 onwards

Modifiable YES

Description This parameter is used by the RNW configuration dB (raquel) conversion program.

Default value(s) QX: 65280D

Allowed values Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.2 Parameter 002:0740 RNW_DATA_2 Descriptive name Radio network parameter

Applicable controllers IPA-RNC from RN5.0 onwards mcRNC from mcRNC2.0 onwards

Modifiable YES

Description This parameter is used by the RNW configuration dB conversion program.

Default value(s) QX: 65280D

Allowed values Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.3 Parameter 002:0840 TIMER_ERQ Descriptive name Value of AAL2 signalling establish timer

Applicable controllers IPA-RNC

Modifiable YES

Description This parameter is used to set the value for AAL2 connection establishment timer in AAL2 signalling 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).

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Default value(s) QX: 1EH

Allowed values 5H-1EH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.4 Parameter 002:0841 TIMER_REL Descriptive name AAL2 signalling release timer

Applicable controllers IPA-RNC

Modifiable YES

Description This parameter is used to set the value for release timer in AAL2 signalling 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).

Default value(s) QX: 3CH

Allowed values 2H-3CH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.5 Parameter 002:0842 TIMER_MOD Descriptive name AAL2 signalling modification timer

Applicable controllers IPA-RNC

Modifiable YES

Description This parameter is used to set the value for for the modification timer in AAL2 signalling 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) .

Default value(s) QX: AH

Allowed values 5H-1EH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.6 Parameter 002:1047 AAL2_NNI_CONN_REL_TIMER Descriptive name Timer to delay AAL2 connection releases when NNI signalling link is broken

Applicable controllers IPA-RNC

Modifiable YES

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description This parameter is used to set the time that the system waits before AAL2 connections using a broken NNI signalling links are released. The timer is started when the system detects that the NNI signalling link does not work. If the signalling link goes up before the time expires, AAL2 connections are not released. If the time expires, AAL2 connections using a broken signalling link are released.The possible timer value range from 1 (1H) second to 255 (FFH) seconds. If the value is set to 0 (0H), then the AAL2 connections are released right after the signalling link goes down. For more information, see Configuring Signaling Connections in ATM Network (IPA-RNC).

Default value(s) QX: 0H

Allowed values 0H-FFH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.7 Parameter 002:1248 NE_LOGICAL_CONFIGURATION Descriptive name Network Element’s system type

Applicable controllers IPA-RNC from RN5.0 onwards

Modifiable YES

Description The value of this parameter determines the Network Element’s system type.

Value

Meaning

Not configured with two SYM-MXUs. The RNC is RNC196 Capacity Step 1 - 5. This is the default value.

Two SYM-MXUs configured. The RNC is RNC196 Capacity Step 6 - 7 or RNC450 Capacity Step 1 - 3.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

The RNC is RNC2600 with SYM-MXU MX1G6/-A.

Default value(s) QX: 0H

Allowed values 0H, 1H, 4H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.8 Parameter 002:1296 RN22_FEATURE_OPT_009 Descriptive name RN2.2 Feature optionality 009

Applicable controllers IPA-RNC from RN5.0 onwards mcRNC from mcRNC2.0 onwards Flexi Direct RNC from I-ADA4.0 onwards

Modifiable YES

Description A new feature in RN2.2 which is improved/changed from RN3.0 CD3.0 onwards with features RAN1810: Sleeping Cell Improvement and RAN1823: Recovery Logging Improvement. For more details and activation instructions, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Forbidden values Dependence For dependencies on other parameters, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Feature RAN1302: Non-Performing Cell Recovery (RAN1810: Sleeping Cell Improvement, RAN1823: Recovery Logging Improvement)

2.1.9 Parameter 002:1297 RN22_FEATURE_OPT_008 Descriptive name RN2.2 Feature optionality 008

Applicable controllers IPA-RNC from RN5.0 onwards mcRNC from mcRNC2.0 onwards Flexi Direct RNC from I-ADA4.0 onwards

Modifiable YES

Description RAN914: Flexi WCDMA BTS 1900 feature can be activated with this parameter.

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN914: Flexi WCDMA BTS 1900

2.1.10 Parameter 002:1300 RN22_FEATURE_OPT_004 Descriptive name RN2.2 Feature optionality 004

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Applicable controllers IPA-RNC from RN5.0 onwards mcRNC from mcRNC2.0 onwards Flexi Direct RNC from I-ADA4.0 onwards

Modifiable YES

Description The value of this parameter determines if the feature is enabled or not. For instructions, see Activating HSPA Service Indicator.

Value

Meaning

Feature is not in use.

24H

Feature is in use.

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.11 Parameter 002:1370 AMR_LIC_WARN_IN_USE Descriptive name AMR license warning in use

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description This parameter controls the license_capacity_warning alarm. When this value is set to T, license_capacity_warning alarm can work as defined. Otherwise, no such alarm is reported in AMR situation.

Value

Meaning

license_capacity_warning alarm is reported according to the AMR amount and AMR license warning threshold.

no license_capacity_warning alarm can be reported.

Default value(s) QX: 0 (F)

Allowed values 1 (T) / 0 (F)

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.12 Parameter 002:1371 AMR_LIC_WARN_THRESHOLD Descriptive name AMR license warning threshold

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the threshold for the license_capacity_warning alarm which means that the AMR capacity has reached a certain level of licensed_amr_capacity and needs to warn the user. The value here stands for the percentage of licensed_amr_capacity.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

64H

100% of licensed_amr_capacity

5AH

90% of licensed_amr_capacity

0% of licensed_amr_capacity

Default value(s) QX: 05AH

Allowed values 0H - 064H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.13 Parameter 002:1372 AMR_LIC_WARN_DUR Descriptive name AMR license warning duration

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the duration in which the AMR capacity has exceeded the warning threshold. It is one of the conditions that must be fulfilled so that the license_capacity_warning alarm can be reported. The value here stands for seconds.

Issue: 03F

Value

Meaning

the duration is 0s

E10H

the duration is 3600s

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Default value(s) QX: 0258H

Allowed values 0H-E10H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.14 Parameter 002:1373 AMR_LIC_WARN_DUR_CANCEL Descriptive name AMR license cancel warning duration

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the duration in which the AMR capacity has canceled the status of exceeding the warning threshold. It is one of the conditions that must be fulfilled to cancel the license_capacity_warning alarm. The value here stands for days.

Value

Meaning

the duration is 0 days

1EH

the duration is 30 days

Default value(s) QX: 0AH

Allowed values 0H-1EH

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.15 Parameter 002:1374 AMR_LIC_ALARM_IN_USE Descriptive name AMR license alarm in use

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter controls the license_capacity_exceeded alarm. When this value is set to T, license_capacity_exceeded alarm can work as defined. Otherwise, no such alarm is reported in AMR situation.

Value

Meaning

the alarm is reported

the alarm is not reported

Default value(s) QX: 0 (F)

Allowed values 1 (T) / 0 (F)

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.1.16 Parameter 002:1375 AMR_LIC_ALARM_DUR_CAL Descriptive name AMR license cancel alarm duration

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the duration in which the AMR capacity has canceled the status of exceeding the alarm threshold. It is one of the conditions that must be fulfilled to cancel the license_capacity_exceeded alarm. The value here stands for days.

Value

Meaning

the duration is 0 days

1EH

the duration is 30 days

Default value(s) QX: 0AH

Allowed values 0H-1EH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.17 Parameter 002:1376 PS_LIC_WARN_IN_USE Descriptive name PS license warning in use

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Value

Meaning

license_capacity_warning alarm can report according to the AMR amount and PS license warning threshold.

no license_capacity_warning alarm can be reported.

Default value(s) QX: 0 (F)

Allowed values 1 (T) / 0 (F)

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.18 Parameter 002:1377 PS_LIC_WARN_THRESHOLD Descriptive name PS license warning threshold

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This 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 value here stands for the percentage of licensed_ps_capacity.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value

Meaning

64H

100% of licensed_amr_capacity

5AH

90% of licensed_amr_capacity

0% of licensed_amr_capacity

Default value(s) QX: 05AH

Allowed values 0H-64H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.19 Parameter 002:1378 PS_LIC_WARN_DUR Descriptive name PS license warning duration

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the duration in which the PS throughput capacity has exceeded the warning threshold. It is one of the conditions that must be fulfilled so that the license_capacity_warning alarm can be reported in PS situation. The value here stands for seconds.

Value

Meaning

the duration is 0s

E10H

the duration is 3600s

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Default value(s) QX: 0258H

Allowed values 0H-E10H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.20 Parameter 002:1379 PS_LIC_WARN_DUR_CANCEL Descriptive name PS license cancel warning duration

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the duration in which the PS throughput capacity has canceled the status of exceeding the warning threshold. It is one of the conditions that must be fulfilled to cancel the license_capacity_warning alarm in PS situation. The value here stands for days.

Value

Meaning

the duration is 0 days

1EH

the duration is 30 days

Default value(s) QX: 0AH

Allowed values 0H-1EH

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.21 Parameter 002:1380 PS_LIC_ALARM_IN_USE Descriptive name PS license alarm in use

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter controls the license_capacity_exceeded alarm. When this value is set to T, the license_capacity_exceeded alarm can work as defined. Otherwise, no such alarm is reported in PS situation.

Value

Meaning

the alarm is reported

the alarm is not reported

Default value(s) QX: 0 (F)

Allowed values 1 (T) / 0 (F)

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.22 Parameter 002:1381 PS_LIC_ALARM_DUR_CAL Descriptive name PS license cancel alarm duration

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the duration in which the PS throughput capacity has canceled the status of exceeding the alarm threshold. It is one of the conditions that must be fulfilled to cancel the license_capacity_exceeded alarm. The value here stands for days.

Value

Meaning

the duration is 0 days

1EH

the duration is 30 days

Default value(s) QX: 0AH

Allowed values 0H-1EH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.23 Parameter 002:1546 ICSU_WINDOW_SIZE Descriptive name ICSU WINDOW SIZE

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Modifiable YES

Description The value of this parameter limits the number of ongoing RNW initialization and recovery tasks (such as BTS initialization, cell setup/recovery, common channel creation/recovery, common measurement initialization/recovery, NBAP link establishment/release, HSPA configuration/recovery).

Value

Meaning

ICSU WINDOW SIZE is not in use, and there is no limit to the number of ongoing RNW initialization and recovery tasks.

Default value(s) QX: 0AH

Allowed values 0H - 0FF00H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.24 Parameter 002:1632 HSUPA_SERVICE_INDICATOR Descriptive name HSUPA Service Indicator

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description The value of this parameter indicates whether the HSUPA Service Indicator feature is in use or not. For more details see Activating HSPA Service Indicator in Activating and Verifying RU10 Features

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

HSUPA Service Indicator feature is not in use

66H

HSUPA Service Indicator feature is in use

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1164: HSDPA Service indicator RAN826: Basic HSUPA RAN763: Basic HSDPA with QPSK and 5 codes in the RNC

• • •

2.1.25 Parameter 002:1649 IP_LINK_BREAK_REL_DELAY Descriptive name Delay for call release in IP link break.

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Description This parameter defines the call resource release delay in case of link failure when IP based transport is used, it can be adjusted to allow a suitable tolerance for short link breaks without releasing calls associated with the failed link. Parameter value is given in seconds. Please see the following for default, and example values.

Issue: 03F

Value

Meaning

Immediate release of calls.

The release delay duration is 1 second.

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value

Meaning

The release delay duration is 10 seconds.

10H

The release delay duration is 16 seconds.

1EH

The release delay duration is 30seconds.

Default value(s) QX: 0H

Allowed values 0H - 1EH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.26 Parameter 002:1662 REVERTIVE_SWO_IN_USE Descriptive name Revertive Switchover is in use.

Applicable controllers IPA-RNC

Modifiable YES

Description The parameter indicates whether the “Revertive Switchover” feature is in use or not.

Value

Meaning

0H (FALSE)

The Revertive Switchover is not in use.

0FFH (TRUE)

The Revertive Switchover is in use.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Default value(s) QX: 0H

Allowed values 0H/0FFH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.27 Parameter 002:1664 RN50_MAINT_02 Descriptive name RNC workaround for UE problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Call setup failures due to iPhone 3GS problems in handling lossless PDU size change, RNC to pack RB mapping info for the release 5 UE user plane RB again for DCH/DCH allocation and RNC to send explicit RLC information for SRB3 For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 5.5). After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.1.28 Parameter 002:1666 RN50_MAINT_03 Descriptive name RU10 Relocation restriction

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description 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. The 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 P8 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).

Default value(s) QX: 0H

Allowed values 0H-1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.29 Parameter 002:1668 RN50_MAINT_05 Descriptive name RU10/RU20 counter functionality

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Description This parameter is used for counter functionality activation. For instructions, see TS-RNCSW-148 (section 5.2 and 6.1).

Value

Meaning

RU20 counter functionality is used (default).

RU10 counter functionality is used.

Default value(s) QX: 0H

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.30 Parameter 002:1669 RN50_MAINT_06 Descriptive name RNC workaround for UE problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description UE using Qualcomm chipset does not register to the NW in case the SB1 and any SIB information are in the same segment (frame) For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 5.1)

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.31 Parameter 002:1670 RN50_MAINT_07 Descriptive name RNC workaround for CN problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Release 5/6 Qualcomm based UEs are unable to make PS calls in Release 7 network when a release 7 QoS is provisioned to the subscriber. For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 6) After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.32 Parameter 002:1671 RN50_MAINT_08 Descriptive name RNC workaround for UE problem

Applicable controllers mcRNC, Flexi Direct RNC

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Description This parameter is used to handle RNC workarounds for UE problems, for further instructions as well as default/possible values, see TS-RNC-SW-149.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.33 Parameter 002:1673 RN50_MAINT_10 Descriptive name RNC workaround for UE problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description RL failures when SRB of UE with Qualcomm chipset is assigned to a certain DL Spreading Code. For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 5.2) After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.1.34 Parameter 002:1684 RN50_MAINT_11 Descriptive name SIB optimizations

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter is used to reduce the size of SIB messages. If the function is activated, the SIB files contain only mandatory information and some messages are not sent at all (if the information is already included in other messages).

Value

Meaning

Function deactivated (default).

Function activated.

Note that after parameter value has been modified, cell lock/unlock needs to be performed for the change to be implemented.

Default value(s) QX: 0H

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.35 Parameter 002:1686 RN50_MAINT_13 Descriptive name RNC workaround for UE problem.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description 10 ms to 2 ms TTI reconfiguration problem causing call drops – iPhone 4 and some Qualcomm chipset based UE (e.g. Samsung Galaxy S). For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 5.7). After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.36 Parameter 002:1687 RN50_MAINT_14 Descriptive name RNC workaround for UE problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Some UE models are behaving erroneously. Sometimes UE retransmits RRCConnectionRequest very fast with protocol error indication, even before UE has received the original RRCConnectionSetup. With this parameter, the RNC waits for RRCConnectionComplete for a time specified by PRFILE parameter. If RRCConnectionSetupComplete is received during waiting time, then RRCConnectionRequest with protocol error indication is not processed. For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 5.6).

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.37 Parameter 002:1689 RN50_MAINT_15 Descriptive name RNC workaround for UE problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Usage of AMR {5.9, 4.75} Codec Set causes UL muting for some old R99 UEs. PRFILE controlled workaround for this UE problem is implemented to NSN RNC. NSN RNC does not use AMR {5.9, 4.75} Codec Set for R99 UE if workaround is activated, even {5.9, 4.75} is enabled by cell level RWN parameter CSAMRmodeSET. For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 5.8). After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.38 Parameter 002:1691 RN50_MAINT_16 Descriptive name RNC workaround for UE problem.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Root cause of voice quality problems with Apple iPhone 3G/3Gs/4 smart phone models was that those UE models are not able to handle DRRC (Directed RRC connection setup) functionality during CCH to DCH state transition. Another type of voice quality problems are caused by the iPhone inability to handle CS Voice on DCH setup with transparent mode RLC configuration if the procedure is done with state transition from Cell_FACH to Cell_DCH. For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 5.3). After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.39 Parameter 002:1696 RN50_MAINT_20 Descriptive name CM Plan upload fails.

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description Controllable timer is implemented to the RNC which can be used to allow more time for compression in case of very big XML plans. Length of the delay timer is defined by the value of the parameter, value 0H is used for 10 minutes, and values from 1H to 3CH define the delay time in minutes (60 minutes maximum).

Value

Meaning

Delay timer is set to 10 minutes.

1-3C

Delay timer is set to 1 - 60 minutes.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-3CH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.40 Parameter 002:1697 RN50_MAINT_21 Descriptive name RNC improvement to prevent unnecessary RL signaling during BTS transport congestion.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Description When this parameter is active, it prevents the unnecessary RL signaling during BTS transport congestion. It is recommended to activate parameter only if continuous Iub AAL2 signaling congestion occurs (alarms 1192 SSCOP TRANSMIT BUFFER OVERFLOW) with very bandwidth limited (less than 3xE1/T1) Iub configurations.

Value

Meaning

Change is not activated.

Change is activated.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.41 Parameter 002:1699 RN50_MAINT_23 Descriptive name RNC workaround for UE problem.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Certain Rel-5 UE models are not able to handle direct transition from Cell_DCH to Cell_PCH command from network correctly. For further instructions, as well as the list of possible values, see TS-RNC-SW-149 ( Section 5.9).

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.42 Parameter 002:1700 RN50_MAINT_24 Descriptive name Workaround to manage SIB update delay functionality in RN5.0.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description PRFILE controllable timer is implemented to RNC. Timer is recommended to be used in case of continuous Core Network problems, when the state of Iu links is changing multiple times. This timer prevents sending of SIB updates while timer is running which will reduce number of registration attempts generated by UEs in this kind of conditions. The parameter value indicates the timer duration in seconds multiplied by 10.

Value

Meaning

No delay.

1-FF00

The delay timer is active (from 10 seconds to 652800 seconds).

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-FF00H

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.43 Parameter 002:1701 RN50_MAINT_25 Descriptive name Data forwarding support for PS service during SRNS relocation.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description New PRFILE controlled workaround is implemented 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).

Value

Meaning

Data forwarding is disabled (default value)

Data forwarding is enabled.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Allowed values 0H-1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.44 Parameter 002:1702 RN50_MAINT_26 Descriptive name RRC Access Failure due to RADIO

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description PRFILE configurable functionality is implemented which uses maximum HSDPA traffic power (Pmax) from target cell in initial power calculation. If separately activated, initial DL transmission power for the UE that has reported low EcNo, is calculated using maximum HSDPA traffic power instead of last reported power value from the BTS. Threshold value for low EcNo can be also configured with same PRFILE parameters. This increases the initial DL power for low EcNo reported UEs when DRRC is done to HSDPA layer increasing DRRC success rate in this kind of conditions. It is possible that calculated initial power for DRRC is equal to maximum initial power (Ptc,init = Ptx,max). In this situation it might be that this is not enough for DRRC to succeed. With PRFILE it is possible to configure that DRRC is not started if calculated initial power equals to maximum initial power. If RRC connection setup fails without DRRC in HSDPA cell, it might be due to too low initial power with low EcNo. To prevent this problem similar new PRFILE configurable functionality is implemented which uses maximum HSDPA traffic power (Pmax) of cell in initial power calculation without DRRC. There is also possibility to set EcNo threshold which defines the lowest reported EcNo for DRRC. If UE reports lower EcNo value the DRRC is not done but the UE stays in current layer. This prevents DRRCs from too poor radio conditions. Possible Bit values:

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

•

1st bit: Is used to control feature activation with DRRC. Activation with default EcNo threshold value (-11dB) is done with 1H (00000001).

•

2nd bit to 7th bit: Are used to configure wanted EcNo threshold value. Range -23.5 to 0 dB step 0.5 dB. Here are some examples for EcNo threshold values (when functionality is activated only for DRRC): – – – – – –

•

8th bit: Is used to configure that DRRC is not started if calculated initial power equals to maximum initial power: –

Value 0: OFF (DRRC cancel when Ptc,init = Ptx,max functionality is off)

–

Value 1: ON (DRRC cancel when Ptc,init = Ptx,max functionality is on)

9th bit: Is used to control feature activation for non-DRRC case –

–

•

3H (00000011): -23.5 dB 5H (00000101): -23 dB 35H (00110101): -11dB 39H (00111001): -10dB 41H (01000001): -8dB 61H (01100001): 0dB

Value 0: OFF (using Pmax in initial power calculation for non-DRRC case functionality is off) Value 1: ON (using Pmax in initial power calculation for non-DRRC case functionality is on)

10th bit to 15th bit: Are used configure lowest EcNo threshold value which enables the DRRC. Range -23.5 to 0 dB, with step 0.5 dB. Here are some examples for EcNo threshold values (when functionality is activated only for DRRC): – – – – – –

x000 000x xxxx xxxx: -23.5 dB x000 010x xxxx xxxx: -23 dB x011 010x xxxx xxxx: -11 dB x011 100x xxxx xxxx: -10 dB x100 000x xxxx xxxx: -8 dB x110 000x xxxx xxxx: 0 dB

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-255H

Forbidden values Dependence Dependence on other parameters does not exist.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Feature -

2.1.45 Parameters 002:1703 RN50_MAINT_27 and 002:1704 RN50_MAINT_28 Descriptive name HSUPA Initial SIR target offset enhancement and DynPwrOffsetUsage alignment.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description New PRFILE controlled workaround is implemented to RNC to allow HSUPA initial SIR target offset value to be configured in order to reduce the RL power, and to decrease RTWP values. The change applies only to first RL setup. There are no changes to RL reconfiguration, or SCC, and no branch additions either. 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 EDCH TTI value. It is also checked that the minimum SIR target parameter is not higher than the subtracted SIR value. If Dynamic HSUPA Power Offset feature is disabled, the parameter values corresponding to high power offsets are used. The offset values are defined for 002:1703 RN50_MAINT_27 PRFILE parameter as follows: MSB

LOW DPPCH PO

LOW DPCCH PO

SF4+10ms TTI

SF4+2ms TTI

(SF8,16,32,64,128)

LSB

HIGH DPCCH PO

The offset values are defined for 002:1704 RN50_MAINT_28 PRFILE parameter as follows: MSB

LOW DPPCH PO

LOW DPCCH PO

2xSF2+10ms TTI

2xSF2+2ms TTI

2xSF4 + 10ms TTI

2xSF4+2ms TTI

LSB

Complete mapping table of individual offset values:

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

PRFILE value (dec)

SIR offset (dB)

0.0

0.5

1.0

1.5

2.0

2.5

3.0

3.5

4.0

4.5

5.0

5.5

6.0

After the parameter value has been changed, the change is implemented within 10 minutes. For detailed description and activation method see TS-RNC-SW-159.

Default value(s) 0H

Allowed values 0H-CH

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.1.46 Parameter 002:1706 RN50_MAINT_29 Descriptive name Location Update handling in case of RL failure to release the CS CN signaling connection.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description After SRNS relocation from another RNC, if UE initiates Location Update procedure, it can fail in a situation when UE loses radio connection before the first DL message for CS CN has been sent to the UE. If UE repeats the Location Update procedure, the reattempt is not handled correctly in RNC and the Location Update message is lost. This can cause the UE to get stuck with the Location Update procedure and RNC would not release RRC connection also due to ongoing PS. It can also happen that Location Update attempts fail. For example, if RL failure happens during ongoing Location Update and RNC loses the “Location Update-Accept” due to RLC re-establishment. Correction has been made to handle Location Update in case of RL failure to release the CS CN signaling connection and handle next Location Update correction correctly anew, and forward it to the RANAP signaling entity for establishment of Iu connection. In addition, PRFILE controlled change has been made which will release the RRC connection if the Location Update procedure is looped for UE, and move the problematic UE to idle mode. Then UE can initiate the Location Update procedure again. PRFILE parameter can be configured to set timer duration after a location update reject has been sent by the CN. If UE does not start location update procedure during that time, then the ongoing call will be dropped. This timer setting is possible, only if this functionality has been activated.

Value (hex)

Meaning

Timer is not active (default value).

Timer is set to 10 s.

Timer is set to 20 s.

Timer is set to 30 s.

Timer is set to 60 s.

Timer is set to 90 s.

Timer is set to 120 s.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (hex)

Meaning

Timer is set to 240 s.

After the parameter value has been changed, the change is implemented within 8 minutes.

Default value(s) 0H

Allowed values 0H, 6H, AH, EH, 12H, 16H, 1AH, 1EH

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.47 Parameter 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.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description RLC parameters for SRB on HSPA RNC uses 2ms TTI for SRB on HSUPA also for Rel6 UEs. It has been noticed that certain Rel6 UE models are not able to handle RB reconfiguration involving RLC change with AT. When UE has to perform SL switch with AT and has same time RLC parameters changing and something to schedule, certain Rel6 UE models interpret this wrongly. After this workaround 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.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

RNC workaround: Disabling of 2ms TTI based on UE release Some Rel.6 UEs cannot handle 2ms TTI allocation correctly, causing thus setup failure counters to be impacted. With this workaround, 2ms allocation will not be attempted for the following scenarios: user plane setup, channel type switch, TTI switch, handovers.

• • • •

Value

Meaning

Workaround is not active (default value).

Only RLC parameters for SRB on HSPA workaround is active.

Usage of 2ms for Rel.6 UEs is restricted.

Usage of 2ms for Rel.6 UEs is restricted and RLC parameters for SRB on HSPA workaround is active.

Usage of 2ms for Rel.7 UEs is restricted.

Usage of 2ms for Rel.7 UEs is restricted and RLC parameters for SRB on HSPA workaround is active.

Usage of 2ms for both Rel.6 and Rel.7 UEs is restricted.

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

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H, 01H, 10H, 11H, 02H, 22H, 03H, 13H

Forbidden values -

Dependence Dependence on other parameters does not exist.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Feature -

2.1.48 Parameter 002:1717 RN50_MAINT_39 Descriptive name Incorrect SRB congestion handling.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description RNC mishandles SRB code tree congestion Spreading code consumption of standalone signaling link depends on the SRB DCH bitrate. SRB DCH 13.6 kbps reserves SF 128, and SRB DCH 3.4 kbps reserves SF 256. In case of spreading code congestion another retry with lower SRB DCH bit rate 3.4 kbps was not performed. This can be seen as an RRC connection setup failures. If SRB DCH 13.6 kbps (SF 128) experiences code tree congestion, then SRB 3.4 kbps (SF 256) retry will be done. An exception to this rule is RRC connection request, 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 a useless retry for SRB with a lower bit rate 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. Currently, unnecessary retry with SRB DCH 3.4 kbps is done in case SRB DCH 13.6 kbps is congested. This problem results in an extra NBAP signaling in case of BTS congestion. If SRB DCH 13.6 kbps experiences BTS HW congestion, SRB 3.4 kbps retry will not be performed, because SRB DCH 13.6 kbps and SRB DCH 3.4 kbps consume the same amount of BTS HW capacity. Instead, pre-emption can be started directly with SRB DCH 13.6 kbps.

Issue: 03F

Value

Meaning

Correction is not active.

Correction is active.

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Default value(s) 0H

Allowed values 0H,1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.49 Parameter 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.

Applicable controllers IPA-RNC, RN6.0 2.2

Modifiable YES

Description Alarms 3700 DSP POOL SEVERE ERRORS and 3688 DSP SEVERE ERROR EXCEEDS THRESHOLD are set if the reported DSP severe errors amount exceeds the threshold, set with this PRFILE parameter, within eight minutes. If the DSP severe error amount drops under the threshold those alarms are canceled.

Value

Meaning

0000H

Alarming functionality is enabled. Default reporting threshold value 28H (40 dec) is used.

0001H-0009H

Alarming functionality is enabled. Threshold is in invalid range, a default reporting threshold value 28H (40 dec) is used instead.

000AH-FEFFH

Alarming functionality is enabled. Reporting threshold is in valid range AH - FEFFH (10 - 65279 dec), value is used as such.

FF00H

Alarming functionality is disabled.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-FF00H

Forbidden values Dependence Parameter 002:1760 RN50_MAINT_43 - defines recovery of non-performing DSPs.

Feature -

2.1.50 Parameter 002:1765 RN50_MAINT_48 Descriptive name HS-DSCH and E-DCH success rate decreased after Blind IFHO activation.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description When Blind IFHO is activated, it requires changing of the intra-frequency measurement quantity needs from EcNo to RSCP. It is defined with RACHIntraFreqMesQuant parameter. After this, the measured EcNo is not available for DL initial power calculation anymore. With this parameter the values of the RSCP0 and BackgroundEcNo can be defined. Additionally, they can be defined if the RSCP is used to calculate EcNo.

Issue: 03F

Value

Meaning

The RNC uses the RSCP that UE has reported when calculating the DL initial power.

The functionality is disabled.

2H-30B4H

The functionality is enabled (see the detailed description of the values below).

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

1st bit determines whether the RSCP is used to calculate EcNo: • •

value 0 (0000 0000 0000 0000) means that RSCP is used to define EcNo value 1 (0000 0000 0000 0001) means that RSCP is not used to define EcNo

Bits from 2nd to 8th define the RSCP0 value. Values range from -119 dB to -30 dB, with a step of 1 dB. Special value of 0000 0000 0000 0000 is used to indicate special (default) value of -80 dB. See the following examples: • • • • • •

0000 0000 0000 0010, resulting in -119 dB 0000 0000 0001 0100, resulting in -110 dB 0000 0000 0010 1000, resulting in -100 dB 0000 0000 0101 0000, resulting in -80 dB 0000 0000 1000 1100, resulting in -50 dB 0000 0000 1011 0100, resulting in -30 dB

Bits from 9th to 14th define the BackgroundEcNo value. Values range from -23.5 dB to 0 dB, with a step of 0.5 dB. Special value of 0000 0000 0000 0000 is used to indicate special (default) value of -10 dB. See the following examples: • • • • • •

0000 0001 0000 0010, resulting in -23.5 dB 0000 0010 0000 0010, resulting in -23 dB 0001 1010 0000 0010, resulting in -11 dB 0001 1100 0000 0010, resulting in -10 dB 0010 0000 0000 0010, resulting in -8 dB 0011 0000 0000 0010, resulting in -0 dB

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-30B4H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.51 Parameter 002:1775 RN50_MAINT_57 Descriptive name RNC workaround for UE problems.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This PRFILE is used to control UE release in hanging situations. With this PRFILE activated, the RNC will release RRC connection of such UEs and update failure counter for RRC connection, so that activation of this workaround is visible in the KPIs and user can re-activate the session after release. This workaround is implemented to two detected problem scenarios, functionalities can be activated separately, as needed based on which problem is seen in the network: 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.

• •

Value (HEX)

Meaning

Both functionalities are disabled.

Releasing UE after a failed Integrity Check for UL message and stuck functionality is enabled.

Releasing UE after a failed RRC message decoding for UL message and stuck is enabled.

Both functionalities are enabled.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-3H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.1.52 Parameter 002:1776 RN50_MAINT_58 Descriptive name Control for both DRRC and HSDPA layering functionalities between different frequency bands is implemented under PRFILE

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Directed RRC connection setup (DRRC) RRC Connection Request message does not include information about UE frequency band capability. When Directed RRC connection setup (DRRC) is done, 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 the UE supports both frequency bands. This is due to possible big difference in wave length (for example in case of 2100 MHz and 900 MHz) leading to different propagation and the difference in cell coverage. By default, DRRC is not allowed between frequency bands (change introduced from RN6.0 1.4 onwards), but it can be now enabled with this PRFILE parameter.

Please note that as an exception, there are two frequency bands which have two same frequencies. These frequency bands are V and VI. DRRC between these frequency bands, DRRC is always allowed. HSDPA layering for UEs in common channel HDSPA Layering for UEs in common channel has the same risk to fail between frequency bands as DRRC. UE support is not the problem with HSDPA layering, but due to possible big difference in wave length (for example in case of 2100 MHz and 900 MHz) leading to different propagation and the difference in cell coverage. The problem become visible when layer change is done from lower frequency band to higher frequency band. By default, layering for UEs in common channel is allowed between frequency bands, but it can be disabled with this PRFILE parameter.

Please note that as an exception there are two frequency bands which have two same frequencies. These frequency bands are V and VI. DRRC between these frequency bands is always allowed.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

HSDPA layering for UEs in common channel is enabled, DRRC is disabled.

HSDPA layering for UEs in common channel is enabled, DRRC is enabled.

10H

HSDPA layering for UEs in common channel is disabled, DRRC is disabled.

11H

HSDPA layering for UEs in common channel is disabled, DRRC is enabled.

Please also note that this parameter does not have any effect for the DRRC and HSDPA layering for UEs in common channels done inside one frequency band. After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H,1H,10H,11H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.53 Parameter 002:1792 UP_CAP_UPGRADE Descriptive name Flexible user plane capacity

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description This parameter is used to control Flexible user plane capacity functionality.

Value

Meaning

Flexible user plane capacity functionality is disabled (default value).

Flexible user plane capacity functionality is enabled.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN2261: Flexible User Plane Capacity in RNC196 and RNC450

2.1.54 Parameter 002:1798 OPT_BLOCK_MOVE_PREVENT Descriptive name Automated A2SU/A2SP load balancing prevention.

Applicable controllers IPA-RNC

Modifiable YES

Description The parameter determines whether automated load balancing between A2SU/A2SP units is prevented or not.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

Automated load balancing between A2SU/A2SP units is allowed.

Automated load balancing between A2SU/A2SP units is prevented.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.55 Parameter 002:1814 LCH_IN_USE Descriptive name Alarm triggered log collection functionality

Applicable controllers IPA-RNC, from RN7.0

Modifiable YES

Description This parameter indicates whether the alarm triggered log collection functionality is in use or not.

Issue: 03F

Value (hex)

Meaning

Alarm triggered log collection functionality is not in use.

Alarm triggered log collection functionality is in use, and notice alarm will be set after log zip file is generated.

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value (hex)

Meaning

Alarm triggered log collection functionality is in use, but notice alarm will not be set after log zip file is generated.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-2H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1805: RNC Event Triggered Symptom Data Collection

2.1.56 Parameter 002:1816 IPMUX_MUX_DELAY Descriptive name The max delay of multiplexed PDU

Applicable controllers IPA-RNC, from RN6.0 2.2

Modifiable YES

Description This parameter is used to set delay for multiplexed packet in multiplexing in miliseconds.

Value (hex)

Meaning

Delay for multiplexed packet in multiplexing is set to 1ms.

Delay for multiplexed packet in multiplexing is set to 2 ms (default value).

Delay for multiplexed packet in multiplexing is set to 3 ms.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (hex)

Meaning

Delay for multiplexed packet in multiplexing is set to 4 ms.

Please note that NPGE unit restart is needed for new value to be taken into account.

Default value(s) QX: 2H

Allowed values 1H-4H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1886: Efficient transport for small IP packet

2.1.57 Parameter 002:1817 DYNPWROFFSETUSAGE Descriptive name DynPwrOffsetUsage

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter enables/disables the usage of dynamic power offsets for Rel-6 UE.

Value (hex)

Meaning

Feature enabled

Feature disabled

Default value(s) QX: 0H

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.58 Parameter 002:1818 LCH_TRAN_IN_USE Descriptive name Alarm triggered log transfer functionality

Applicable controllers IPA-RNC, from RN7.0

Modifiable YES

Description This parameter indicates whether the alarm triggered log was transferred to OMS or not.

Value (hex)

Meaning

The alarm triggered log was not transferred to OMS

The alarm triggered log was transferred to OMS.

Default value(s) QX: 1H

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1805: RNC Event Triggered Symptom Data Collection

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.59 Parameter 002:1819 LCH_DIR_SIZE Descriptive name Alarm triggered log directory size

Applicable controllers IPA-RNC, from RN7.0

Modifiable YES

Description This parameter indicates the size of the alarm triggered log in Mbytes, for example, default value 14H (20 decimal), means that size of 20 Mbytes is used.

Default value(s) QX: 14H

Allowed values 9H-FFH

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1805: RNC Event Triggered Symptom Data Collection

2.1.60 Parameter 002:1840 B_PHASE1_SWITCH Descriptive name Switch for source based route phase1 function.

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Description This parameter can be used to switch on/off source-based route phase1 function.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value

Meaning

Source based route phase1 function is OFF.

Source based route phase1 function is ON.

Default value(s) 1H

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN2190: Source Based Routing in the NPGE

2.1.61 Parameter 002:1876 RN60_MAINT_20 Descriptive name Pre-emption functionality for Iur enhancement

Applicable controllers Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description This PRFILE parameter is used to control enhancement to pre-emption functionality that enables CS-over-CS, RT-over-NRT, RT-over-RT and NRT-over-NRT functionalities over the Iur interface, or over combined Iur and Iu-CS interfaces if they share the same physical transport, that is if they have the same IP-based route ID (IPBR ID). Without this pre-emption functionality enhancement on the Iur and Iu-CS interfaces, it is not possible to use RT-over-NRT functionality to make AMR calls possible. As an exception, the preemption on Iur / Iu-CS is not triggered in the following cases: • •

if there is Iu congestion in the target RNC as case of an AMR relocation if there is Iu congestion related to role switch or a UE-not-involved relocation. (However, in case of UE-involved relocation, pre-emption functionality is supported if there is an Iu congestion)

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (HEX)

Meaning

Functionality is deactivated (default value)

Functionality is activated

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.62 Parameter 002:1886 RN60_MAINT_10 Descriptive name Unstable HSUPA service for 10ms TTI users, in case of BTS base band HW limitiation with WN7.0 BTS SW, when F-DPCH is enabled

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description With this PRFILE activated it is possible for WN7.0 BTS hardware reservation to be done also with E-TFCI table 1. Thanks to this change, in case of BTS BB hardware limitation, BTS sub unit(s) capacity can be used more efficiently, and stability of HSUPA services for 10ms TTI users with F-DPCH enabled, will be better when E-TFCI table 1 is used.

Issue: 03F

Value (HEX)

Meaning

Functionality is deactivated (default value)

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value (HEX)

Meaning

Functionality is activated

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.63 002:1868 EDPDCHPowerInterUsage Descriptive name E-DPDCH power interpolation for 2ms and 10ms TTI

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable Yes

Description PRFILE parameter 002:1868 EDPDCHPowerInterUsage (Usage of EDPDCH Power Interpolation) is active by default after RN7.0 upgrade. In RU30, the parameter has also default value 0 (feature is enabled), however, RU30 has the hard coded prohibition. It is recommended to set this functionality off until all BTSs connected to the RNC have been upgraded to WN8.0 as the functionality is not fully supported with RN7.0-WN7.0 combination and there can be a minor increase in HSDPA/HSUPA drops due to radio

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

(HS-DSCH/DCH PACKET CALL REL DUE TO RL FAIL / HS-DSCH/E-DCH PACKET CALL REL DUE TO RL FAIL). The functionality is disabled by setting PRFILE parameter 002:1868 EDPDCHPowerInterUsage to value 1. The following MML commands are used for: checking the status: ZWOI:2,1868; default value/enabling the functionality: ZWOC:2,1868,0; disabling the functionality: ZWOC:2,1868,1;

• • •

Value

Meaning

Functionality is enabled.

Functionality is disabled.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.64 Parameter 002:1888 RN60_MAINT_12 Descriptive name RNC workaround to UE problems with blind IFHO for PS services.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description PRFILE parameter controllable workarounds are implemented to the RNC. This can be activated/deactivated for PS and CS service.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

If activated for CS, the RNC will do blind IFHO for AMR RAB in Cell_DCH state in two stages: 1. IFHO using Physical Channel Reconfiguration, Transport Channel Reconfiguration or Radio Bearer Reconfiguration procedure. 2. RB setup. If activated for PS, the RNC will do blind IFHO for PS RAB in Cell_DCH state in two stages: 1. IFHO using Physical Channel Reconfiguration, Transport Channel Reconfiguration or Radio Bearer Reconfiguration procedure. 2. RB setup. It is also possible to prevent (with 5th bit) a blind IFHO for R99 capable UEs in PS NRT RAB setup. The following list of default and possible values: Default value of this parameter is 0H. With this value the workaround is enabled. •

To activate CS workaround, the values of 1st bit and 4th bit need to be set to “0”.

•

To deactivate CS workaround, the values of 1st bit and 4th bit need to be set to “1”.

•

To activate PS workaround, the value of 2nd bit needs to be set to “0”.

•

To deactivate PS workaround, the value of 2nd bit needs to be set to “1”.

•

To activate both CS and PS workarounds, the values of 1st bit, 2nd bit, and 4th bit need to be set to “0”.

•

To deactivate both CS and PS workarounds, the values of 1st bit, 2nd bit, and 4th bit need to be set to “1”. To activate the prevention for blind IFHO for R99 capable UEs in PS NRT RAB setup, the value of 5th bit needs to be set to “1”. To deactivate the prevention for blind IFHO for R99 capable UEs in PS NRT RAB setup, the value of 5th bit needs to be set to “0”. To ensure that with PS workaround the same transport channel which is used in the source cell is kept in the target cell, the value of 6th bit, needs to be set to “0”. To ensure that SRBs mapping is done based on source cell measurement results during RB setup procedure, if there are no measurement results available from target cell after blind IFHO, the value of 7th bit, needs to be set to “1”.

•

After the parameter value has been changed, the change is implemented within 10 minutes.

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.65 Parameter 002:1889 RN60_MAINT_13 Descriptive name Cause value IE in NBAP: RL DELETION REQUEST and NBAP: RL RECONF CANCEL message

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description With this PRFILE active, the "Cause" value IE is added as a Private Annex Z IE in NBAP:Radio Link Deleltion 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.

Value (HEX)

Meaning

Cause value is included (default value).

Cause value is not included.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.1.66 Parameter 002:1892 RN60_MAINT_16 Descriptive name RNC workaround for UE problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter is used to handle RNC workarounds for UE problems. For further instructions, as well as the list of possible values, see TS-RNC-SW-149. After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.1.67 Parameter 002:1897 RN60_MAINT_22 Descriptive name Usage of monitored cell measurement results on RACH to define the source cell for blind IFHO.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description With this PRFILE parameter, it is possible to disable the use of monitored cell (intrafrequency neighbor cell) in RACH measurement results. This means that blind IFHO can be triggered only from the current cell and the current cell’s RSCP value is used when defining the initial power for blind IFHO.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (HEX)

Meaning

Monitored cell (intra-frequency neighbor cell) measurement results on RACH can be used to define the source cell for blind IFHO.

Monitored cell (intra-frequency neighbor cell) measurement results on RACH cannot be used to define the source cell for blind IFHO.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.68 Parameter 002:1900 RN60_MAINT_25 Descriptive name RNC workaround for UE problem

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description With this workaround active RNC delivers maxReportedCellsOnRACH as CurrentCell, when RACH Intra Frequency Measurement Quantity is CPICH-RSCP in SIB11.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value (HEX)

Meaning

Functionality is deactivated (default value)

Functionality is activated

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.69 Parameter 002:1902 RN60_MAINT_26 Descriptive name UE mobility in Inter-RNC scenario

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Originally, HSDPA with compressed mode is not supported with NSN drift RNC, therefore it does not support HSDPA over Iur if compressed mode is both inactive or active. If serving RNC setups compressed mode inactive or active when HSDPA is active over Iur, then NSN DRNC rejects such request. As an improvement to allow UE mobility in Inter-RNC scenario with different RAN vendors, NSN RNC will accept HSDPA over Iur with compressed mode inactive or active.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (HEX)

Meaning

Functionality is deactivated (default value).

Fuctionality is activated.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.70 Parameter 002:1904 RN60_MAINT_28 Descriptive name Recovery of non-performing DSPs

Applicable controllers IPA-RNC, RN6.0 2.2

Modifiable YES

Description The purpose of "Recovery of non-performing DSP" is to perform automatic DSP unit restart in attempt to recover from a failure that cannot be resolved with less invasive operation. "Non-performing DSP" in this context means an abnormally behaving DSP unit impacting Operator's Services/KPIs, which has not been detected by system as a faulty unit. The reason may be software issues, transient hardware issues, or permanent hardware issues. See the following tables for detailed values and their meaning.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value (HEX)

Meaning

Default value - functionality is enabled. Interpreted as 0F34H.

FF00

Functionality is disabled.

Value (HEX)

Meaning

Mask

Min

Max

Default

0.0.0.X

Maximum number of allowed DSP restarts per pool per day.

0.0.X.0

Waiting time of automatic DSP restart after triggering. Used to avoid restarts due to short burst of errors. Actual value in minutes is obtained by multiplication decimal value by 5.

0.X.0.0

DSP pool related settings, described in a separate table below. There is no pool specific control for CDSP-C specific pools.

X.0.0.0

Bitmask value for 0.X.0.0

4th Bit

3rd Bit

2nd Bit

Reserved for future use and has no effect

Meaning

1st 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

0 - restarts disabled for HS-DCH Pool 1 - restarts enabled for HS-DCH Pool

0 - restarts disabled for CCH Pool 1 - restarts enabled for CCH Pool

0 - restarts disabled for HS CCH Pool 1 - restarts enabled for HS CCH Pool

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Parameter 002:1760 RN50_MAINT_43 - defines threshold for triggering on DSP severe errors.

Feature -

2.1.71 Parameter 002:1905 RN60_MAINT_29 Descriptive name TFCS reduction in the TFCS capability limitation of UE

Applicable controllers IPA-RNC, from RN7.0 1.0 onwards mcRNC, from mcRNC3.0 onwards FD RNC, from ADA5.0 onwards

Modifiable YES

Description Parameter defines two methods, how the Transport Format Combination Set (TFCS) is limited if its size exceeds the TFCS capability of UE. While the UE has the multimode AMR established, and more than one active PS bearers are added in the R99 or HSDPA configurations, or the multimode AMR is set up on top the PS R99 or HSDPA connections, then the UE’s capability limitation in the TFCS size can be easily met especially in UL. Limitation may result to the decreased PS DCH throughputs, even down to 0 kbps. Both methods can be reasonable to be activated together with multimode AMR features RAN580: Load Based AMR Codec Mode Selection, RAN830: AMR Codec Sets and RAN831. If AMR is established on top of the PS DCHs as the TFO/TrFO call, the AMR codec set cannot be limited in the AMR setup phase. AMR setup is possible without releasing a PS DCH only by reducing further the UL TFCS size, by limiting the UL TFCS so that UE can transmit with one PS NRT DCH at a time in the TTI of the DCH, while it can transmit

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

freely with the other than PS NRT bearers. Generally, UEs are able to use bigger TFCSs in DL than in UL, so in most cases DL TFCS capability limitations are avoided by reducing intermediate bit rates of the DL PS DCHs. This method is called as the Limitation of PS NRT DCHs for the TFCS capability of UE in this context; it can be activated with the first bit (LSB) of the parameter. Bit rate limitations of the PS NRT DCHs for the UE’s TFCS capability limitations, while established on top of the multimode AMR call in progress, can be avoided by limiting the AMR to its lowest mode while UE has a PS NRT DCH active. Practically same PS DCH bit rates can then be used as with single mode AMR calls. This method shortens also RRC messages, thereby reducing the probability of dropping the call in radio link reconfigurations. Downgrading and upgrading of the AMR modes may become visible in the speech quality. Fifth bit of the parameter controls, whether the multimode AMR call is allowed to be downgraded to its lowest AMR mode, if the UE has also a non-zero PS interactive or background DCH established. This method is called as Limitation of the multimode AMR for the PS DCH in this context.

Value (HEX)

Limitation of PS NRT DCH for the TFCS capability of UE

Limitation of the multimode AMR for the PS DCH

Not used

Used

Not used

Used

Default value(s) 0H

Allowed values 0H//1H/10H/11H

Forbidden values -

Dependence -

Feature -

2.1.72 Parameter 002:1906 RN60_MAINT_30 Descriptive name Default Iu-link failures customization for Flexi Direct.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Applicable controllers Flexi Direct RNC from ADA4.0 2.0 onwards

Modifiable YES

Description The parameter is used to define the next three values: •

•

CPICH power value (xxxx xxxx xxxx YYYY) Bits from 1st bit to 4th bit are used to define how many dBm over 20 dBm the low power is. The range is 1-15 dBm (0-FH). For example value 3 means that low power is set to 23 dBm. CellCpichPowerOnDelayTimer (xxxx xxxx YYYY xxxx) Bits from 5th bit to 8th bit are used to define the delay after which CPICH power is increased back to normal after Iu-link recovery. The range is 0 - 150 seconds (0-FH) and the step is 10 seconds. . For example value 3 means 30 seconds and on top of that an internal delay of 6 seconds is added, and therefore the CPICH power is increased to normal value 36 seconds after Iu-link recovery . CellCpichPowerOffDelayTimer (xxxx YYYY xxxx xxxx). Bits from 9th bit to 16th bit are used to define the delay after which CPICH power is decreased to low power after Iu-link break has been detected. The range is 0 - 254 seconds (0-FEH) and the step is 10 seconds.For example value 3 means 30 seconds and on top of that an internal delay of 18 seconds is added, and therefore the CPICH power is decreased to low value 48 seconds after Iu-link break has been detected .

Default value of this PRFILE parameter is 0, with this value functionality is disabled. After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-0FFFH

Forbidden values -

Dependence There are no dependencies.

Feature -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.1.73 Parameter 002:1912 RN60_MAINT_36 Descriptive name SIB optimization enhancement

Applicable controllers IPA-RNC, from RN 6.0 2.1 onwards mcRNC, from mcRNC2.0 2.0 onwards Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description This PRFILE is used to enable the sending of Q_offset2 parameter when SIB optimization enhancement is enabled (see the Parameter 002:1684 RN50_MAINT_11).

Please note that in order to complete the activation, cell lock/unlock procedure needs to be performed after changing the parameter value

Value (HEX)

Delta value

Sending of Q_offset2 parameter when SIB optimization enhancement is enabled is disabled (default value)

Sending of Q_offset2 parameter when SIB optimization enhancement is enabled is enabled (default value)

Default value(s) 0H

Allowed values 0H/2H

Forbidden values -

Dependence Parameter 002:1684 RN50_MAINT_11

Feature -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.74 Parameter 002:1913 RN60_MAINT_38 Descriptive name Higher initial code power during Inter-freq hard handover.

Applicable controllers IPA-RNC, from RN 6.0 2.2 onwards

Modifiable YES

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

Issue: 03F

Value (HEX)

Delta value

4dB

1dB

2dB

3dB

4dB

5dB

6dB

7dB

8dB

9dB

10dB

11dB

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value (HEX)

Delta value

12dB

13dB

14dB

15dB

16dB

17dB

18dB

19dB

20dB

21dB

22dB

23dB

24dB

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-18H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.1.75 Parameter 002:1914 RN60_MAINT_39 Descriptive name Limitation of multi PS bearer uplink transmission in DCH configuration for RAN2262

Applicable controllers IPA-RNC, from RN6.0 2.3 onwards mcRNC, from mcRNC2.0 2.1 onwards Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description This PRFILE is used to control two functionalities: •

1st bit (LSB) of the parameter controls whether the UL TFCS limitation is done when the number of the Turbo encoded UL PS DCHs exceeds 1. Limitation is done by restricting the transmission in UL PS NRT DCHs so that not more than one of the UL PS NRT DCHs can transfer at a time in its TTI.

•

5th bit of the parameter controls whether the UL TFCS limitation is done when the number of the Turbo encoded UL PS DCHs exceeds 2. Also in this case the limitation is done by restricting the transmission in UL PS NRT DCHs so that not more than one of the UL PS NRT DCHs can transfer at a time in its TTI.

Value (HEX)

Limitation of the UL TFCS if more than 1 UL PS DCs

Limitation of the UL TFCS if more that 2 UL PS DCHs

Disabled

Enabled

Disabled

Enabled

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H,1H,10H

Forbidden values -

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Dependence Dependence on other parameters does not exist.

Feature RAN2262: Flexi Multiradio System Modules

2.1.76 Parameter 002:1915 RN60_MAINT_40 Descriptive name RNC workaround for cccasional long delay during plan provisioning.

Applicable controllers IPA-RNC, from RN 6.0 2.2 onwards mcRNC, from mcRNC2.0 2.0 onwards Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description With this PRFILE parameter, the radio network plan manager (RAY module) can be changed to address issues such as "ray hand busy" and reserving BTSs only for objects (or related sub objects) where there is a change in RNW confguration for them.

Value (HEX)

Meaning

Functionality is activated (default value).

Functionality is deactivated.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Dependence Dependence on other parameters does not exist.

Feature -

2.1.77 Parameter 002:1916 RN60_MAINT_41 Descriptive name Control of UEs redirection limitation to LTE in case of RAN2717: Smart LTE Layering.

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description This PRFILE parameter is used to control the following: • • •

Whether the redirection to LTE is allowed for all UE or only for these that had been previously redirected from LTE Whether the LTE bands supported by UE are checked and compared against the region-available LTE bands before the redirection to LTE How the redirection to LTE is limited according of the E-UTRAN Service Handover information from Core Network

Used hexdigits

Possible values and Meaning

xxxX

• •

xxXx

•

xXxx

•

0 - Redirection to LTE is allowed to all UEs (default value) 1 - Redirection to LTE is allowed only to UEs redirected from LTE 0 - Redirection can be done only to LTE frequency that belongs to LTE band that is indicated to be supported by the UE (default value) 1 - LTE frequency is not checked against LTE bands supported by the UE 0 (default value): –

Issue: 03F

Signalling connection only are not redirected to LTE

DN0948854

PRFILE and FIFILE parameter descriptions

Used hexdigits

PRFILE Descriptions

Possible values and Meaning –

–

•

1: – –

–

•

–

Signalling connection only are not redirected to LTE UE is not redirected to LTE if all 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

4: – –

–

•

No limitation for signalling connection redirection to LTE UE is not redirected to LTE if at least one its RABs has 'Handover to E-UTRAN shall not be performed' in EUTRAN Service Handover IE 'Handover to E-UTRAN shall not be performed' is not remembered after the related RAB is released

2: –

•

UE is not redirected to LTE if at least one its RABs has 'Handover to E-UTRAN shall not be performed' in EUTRAN Service Handover IE 'Handover to E-UTRAN shall not be performed' is not remembered after the related RAB is released

Signalling connection only are not redirected to LTE UE is not redirected to LTE if at least one its RABs has 'Handover to E-UTRAN shall not be performed' in EUTRAN Service Handover IE 'Handover to E-UTRAN shall not be performed' is remembered after the related RAB is released as long as RRC connection exist and it prevents redirection to LTE

5: – –

–

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Allowed values 0H-511H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN2717: Smart LTE Layering

2.1.78 Parameter 002:1918 RN60_MAINT_37 Descriptive name Temporary offset increase for E-RGCH/E-HICH signatures

Applicable controllers IPA-RNC, from RN 6.0 2.2 onwards mcRNC, from mcRNC2.0 2.0 onwards Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description This PRFILE parameter can be used to define additional offset value which is added to the RsrvdSignaturesOffset parameter value. With additional offset new E-RGCH/EHICH code can be 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.

Issue: 03F

Value (HEX)

Meaning

Functionality is deactivated (default value).

Value 1 is added to the RsrvdSignaturesOffset parameter value.

Value 2 is added to the RsrvdSignaturesOffset parameter value.

Value 3 is added to the RsrvdSignaturesOffset parameter value.

Value 4 is added to the RsrvdSignaturesOffset parameter value.

Value 5 is added to the RsrvdSignaturesOffset parameter value.

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value (HEX)

Meaning

Value 6 is added to the RsrvdSignaturesOffset parameter value.

Value 7 is added to the RsrvdSignaturesOffset parameter value.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-7H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.79 Parameter 002:1935 RN60_INT_FEAT_RES_06 Descriptive name RANAP Interface signaling change.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This PRFILE 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.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

Signaling change is not active.

Signaling change is active.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/10H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.80 Parameter 002:1939 RN60_INT_FEAT_RES_10 Descriptive name H-RNTI allocation algorithm change.

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description With this PRFILE it is possible to select whether the BTS or cell level H-RNTI (highspeed downlink shared channel radio network identifier) pool in the RNC is used.

Issue: 03F

Value

Meaning

Cell level H-RNTI pool is used.

BTS level H-RNTI pool is used.

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

After the parameter value has been changed, the change is implemented within 1 minute.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.81 Parameter 002:2066 MIN_RE_EDPDCH_GF_TO_BTS Descriptive name Minimum reduced E-DPDCH gain factor

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC2.0 2.0 onwards Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description This PRFILE is used to define whether the minimum reduced E-DPDCH gain factor (also called βed,min) is sent to the UE and which value is used.

Value (HEX)

Meaning

Functionality is deactivated (default value).

The RNC sends the same value as for the UE also to the BTS in Minimum Reduced E-DPDCH Gain Factor IE

The SRNC sends the same value as for the UE also over Iur to the DRNC in Minimum Reduced E-DPDCH Gain Factor IE.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (HEX)

Meaning

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

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-3H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.82 Parameter 002:2067 MIN_RE_EDPDCH_GF_VAL Descriptive name Minimum reduced E-DPDCH gain factor

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC2.0 2.0 onwards Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description This PRFILE is used to define whether the minimum reduced E-DPDCH gain factor (also called βed,min) is sent to the UE. If the value is set to 0, Minimum reduced E-DPDCH gain factor IE is not sent to UE. See the following list for available values, when the Minimum reduced E-DPDCH gain factor IE is sent to UE and in which value. If there is value 0000 in corresponding place, then the value 8/15 is used.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value

Meaning

0000 0000 0000 0000

Minimum reduced E-DPDCH gain factor IE is not sent to UE

0000 0000 yyyy 0000

8/15 value is used for 2 ms TTI

0000 0000 yyyy 0001

11/15 value is used for 2 ms TTI

0000 0000 yyyy 0010

15/15 value is used for 2 ms TTI

0000 0000 yyyy 0011

21/15 value is used for 2 ms TTI

0000 0000 yyyy 0100

30/15 value is used for 2 ms TTI (recommended value)

0000 0000 yyyy 0101

42/15 value is used for 2 ms TTI

0000 0000 yyyy 0110

60/15 value is used for 2 ms TTI

0000 0000 yyyy 0111

84/15 value is used for 2 ms TTI

0000 0000 0000 xxxx

8/15 value is used for 10 ms TTI

0000 0000 0001 xxxx

11/15 value is used for 10 ms TTI

0000 0000 0010 xxxx

15/15 value is used for 10 ms TTI (recommended value)

0000 0000 0011 xxxx

21/15 value is used for 10 ms TTI

0000 0000 0100 xxxx

30/15 value is used for 10 ms TTI

0000 0000 0101 xxxx

42/15 value is used for 10 ms TTI

0000 0000 0110 xxxx

60/15 value is used for 10 ms TTI

0000 0000 0111 xxxx

84/15 value is used for 10 ms TTI

Minimum reduced E-DPDCH gain factor IE is sent to the Rel-8 or newer UE always when E-DCH is configured or reconfigured so that there is no DPDCH configured (full HSPA configuration). RAB combination does not affect sending these values. Value is reconfigured if needed when TTI is reconfigured between 2 ms and 10 ms TTI. For Rel-7 and older UEs Minimum reduced E-DPDCH gain factor IE is not sent in any situation. After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-FFH

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.83 Parameter 002:2095 RU40_MAINT_01 Descriptive name RNC recovery correction to avoid unnecessary SAB block and unblocking in case of missing HSPA / HSDPA power measurements

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description This PRFILE is used to control the RNC recovery correction to avoid unnecessary SAB block and unblocking in case of missing HSPA / HSDPA power measurements.

Value

Meaning

Correction is not used.

Correction is used.

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.84 Parameter 002:2098 RU40_MAINT_02 (case 1) Descriptive name DCH to PCH for release 99 users

Applicable controllers IPA-RNC, from RN7.0 P8 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description In RU30, DCH to PCH was controlled with PRFILE 007: 0307 for HS users. Upon inactivity detection for HSDPA or HSPA users, the RNC moved them directly from Cell_DCH to Cell_PCH if the PRFILE allowed it. In RU40, DCH to PCH is controlled with Management parameter DCHtoPCHEnabled but it applies also to Rel99 PS allocation. Therefore when upgrading from RU30 to RU40, there can be more transitions from Cell_DCH to Cell_PCH if the direct transition for HSPA users was allowed in RU30. This is intended functionality in RU40 to reduce the NW signaling, resource usage and UE battery drainage. This PRFILE parameter gives option for operator to have DCH to PCH transition as in RU30, that is only HS users, when the state transition is done due to PRFILE 007: 0307. The parameter is controlled with the 1st bit. After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H (recommended)

Allowed values According to instructions

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.85 Parameter 002:2098 RU40_MAINT_02 (case 2) Descriptive name HSPA allocation problem with RAN 2494 Fast Cell PCH switching

Applicable controllers IPA-RNC, from RN7.0 1.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description 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 that even if RAN2494 is enabled and RNC knows that UL E-DCH transport channel information has not changed, RNC will provide the information in the state transition command to Cell_DCH still to the UE. The workaround is under PRFILE and not active by default. Additionally, it is not expected this problem to be visible in the live network since new UE models should already have a correction for this problem. So the workaround is not recommended to be activated by default. For further instructions, as well as the list of possible values, see TS-RNC-SW-149.

Functionality

5th bit

RNC workarounds for release 6 UE problems

RNC workarounds for release 7 UE problems RNC workarounds for release 8 UE problems

Issue: 03F

DN0948854

6th bit

7th bit

X X

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H (recommended)

Allowed values According to instructions

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.86 Parameter 002:2099 RU40_MAINT_03 Descriptive name PS RAB release guard timer

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description This PRFILE parameter defines the guard timer how soon after receiving GTP error indication from PS-CN, the RNC sends RAB Release Request to SGSN. When the timer expires and RAB Release Request is sent, failure counters in measurements M1001 and M1022 are updated. If however 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. Default value zero means that guard timer of 1000 ms is used. The maximum supported time is 2000 ms, any higher value is interpreted as 2000 ms. Increase of the guard timer may be necessary in some network configurations where the interaction between SGSN and GGSN causes GTP tunnel to be released in core network side so that the release command to the RNC is sent more than 1000 ms later. After the parameter value has been changed, the change is implemented within 10 minutes.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Default value(s) 0H

Allowed values 0H-FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.87 Parameter 002:2101 RU40_MAINT_05 Descriptive name Control of Automatic Access Class Restriction information sending in SIB3.

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description This PRFILE parameter is used to control the access restriction information regarding the RAN2480: Automatic Access Class Restriction as follows: 1st Bit value of 0 (default value) means that the access class barred list for Rel-5 and older UEs is not included in SIB3 with Core Network and the RNC overload triggered AACR. Value of 1 means that the access class barred list for Rel-5 and older UEs is included in SIB3 with CN and RNC overload triggered AACR. 2nd Bit value of 0 (default value) means that the CS domain specific access class restriction list is included in SIB3 with RNC overload triggered AACR. Value of 1 means that the CS domain specific access class restriction list is excluded from SIB3 with RNC overload triggered AACR. 3rd Bit value of 0 (default value) means that the PS domain specific access class restriction list is included in SIB3 with RNC overload triggered AACR. Value of 1 means that the PS domain specific access class restriction list is excluded from SIB3 with RNC overload triggered AACR.

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

For more information on the feature see RAN2480: Automatic Access Class Restriction in RU40 Feature Descriptions and Instructions. After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.88 Parameter 002:2102 RU40_MAINT_06 Descriptive name The algorithm for logical channel ID and DDI allocation

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description PRFILE parameter controllable workaround is implemented to NSN RU40 RNC, where in RU40 logical channel ID and DDI allocation algorithm is executed by default but can be switched back to RU30 algorithm using this PRFILE parameter.

Value

Meaning 0

Workaround is disabled.

Workaround is enabled.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.89 Parameter 002:2103 RU40_MAINT_07 Descriptive name Dynamic HSUPA BLER

Applicable controllers IPA-RNC, from RN7.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description This PRFILE parameter is used to control used 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. • •

Value of 1st Bit of PRFILE parameter controls whether the dynamic power offset algorithm affects the Dynamic HSUPA BLER functionality. Value of 2nd Bit to 7th Bit indicates threshold for number of HSUPA users in the cell in the Dynamic HSUPA BLER functionality.

If the 1st Bit of this PRFILE parameter is set to 0 (no effect) and number of HSUPA users in the cell is more or equal (after this allocation) than this PRFILE parameter value of Bits from 2nd to 7th indicates, or If the 1st Bit of this PRFILE parameter is set to 1 and dynamic power offset algorithm allocates low power offsets/low initial SIR target (also in case of E-DPDCH interpolation method) for the UE, Dynamic HSUPA algorithm BLER

Issue: 03F

DN0948854

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

parameters are used. Otherwise, Continuous BLER state OLPC is configured for this UE with parameter values which are used when Dynamic HSUPA BLER is not activated (L1 BLER from parameter L1BLERTargetEDCH and DynHSUPABLERContDataRx2 and DynHSUPABLERContDataRx10 parameter values fixed as value 1). Recommended value for this PRFILE parameter is 6H meaning that the Dynamic power offset algorithm effects is 'No Effect' and maximum number of HSUPA users in a cell is '3'. After the parameter value has been changed, the change is implemented within 10 minutes.

Default value(s) 0H

Allowed values 0H-FFH

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN2302: Dynamic HSUPA BLER

2.1.90 Parameter 002:2105 RU40_MAINT_09 Descriptive name IFHO/ISHO can fail due to incorrect UE behavior

Applicable controllers IPA-RNC, from RN7.0 1.0onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description After state transition to CELL_FACH is cancelled, conflicting compressed mode information exists inside RNC and between RNC and BTS. The problem is visible to end user so that if compressed mode and new inter-frequency/inter-system measurement cannot be started, calls cannot be handed over to another frequency or RAT.

100

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

When state transition from CELL_DCH to CELL_FACH needs to be made, ongoing interfrequency or inter-system measurement has been stopped due to incorrectly behaving UEs which will not stop these measurements when moving to CELL_FACH state. When state transition is completed, measurement related compressed mode information is also cleared from RNC and BTS. However, if state transition is cancelled (for example due to UE activity) the compressed mode information is left hanging in RNC and BTS even though corresponding measurement has been stopped. This can cause conflict situation if a new inter-frequency or inter-system measurement needs to be started after the state transition has been cancelled and compressed mode needs to be prepared for the measurement. An improved functionality for this kind of scenario is that for UEs newer than Rel6 measurement is not released since they should be able to stop the measurement when moving to CELL FACH state. For older UEs measurement is always released and it is ensured (by Layer 3) that state transition will not be cancelled. This workaround functionality is controlled by PRFILE parameter 002:2105 RU40_MAINT_09.By default, new functionality is disabled. In case this kind of problems are detected in a live network, it is recommended to enable workaround. Value 0 (default) means that UE release is not taken into account when need for ongoing Compressed mode and inter-frequency/inter-system measurement release due to state transition from CELL_DCH to CELL_FACH state is decided by the RNC. Also UE release is not taken into account when deciding if state transition to CELL_FACH state can be cancelled or not. Value 1 means that for UEs equal or older than Rel6, ongoing inter-frequency/intersystem measurement is always released when CELL_FACH state transition is indicated. Also for such UEs CELL_FACH state transition is not cancelled if compressed mode is ongoing.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.1.91 Parameter 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

Issue: 03F

DN0948854

101

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Applicable controllers IPA-RNC, from RN7.0 1.0 onwards mcRNC, from mcRNC3.0 onwards Flexi Direct RNC, from ADA5.0 onwards

Modifiable YES

Description This PRFILE parameter is used to deactivate the LCG and BTS level HSDPA user amount check against LCG and BTS specific limits sent by the BTS in cases where the limitation does not work properly. Originally, RNC limited the HSDPA user amount depending on the 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). These checks were made in the admission control phase. The new functionality allows the BTS to indicate also its maximum LCG- and BTSspecific HSDPA user amounts to the RNC. The RNC does not allow more HSDPA users than indicated within those limits. Value 0 means that LCG and BTS specific HSDPA user amount check against limits sent by BTS is active. Value 1 means that LCG and BTS specific HSDPA user amount check against limits sent by BTS is not active.

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN2124: HSPA 128 Users per Cell

2.1.92 Parameter 002:2109 RU40_MAINT_13 Descriptive name Control for maximum number of RLs in RNSAP Radio Link Setup/Addition procedure

102

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Applicable controllers IPA-RNC, from RN7.0 2.0 onwards mcRNC, from mcRNC3.0 1.0 onwards Flexi Direct RNC, from ADA5.0 1.0 onwards

Modifiable YES

Description The length of the RNSAP: RADIO LINK SETUP/ADDITION RESPONSE message depends on the number of requested RLs (cells) and the number neighboring cells that have been defined for the requested cells in the 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 may become so long that SCCP cannot handle the message and this will cause SRNC to send Error Indication. The maximum length of the SCCP message is 16 segments (16 * 255 = 4080 bytes) in RU40. If the maximum length of RANAP Radio Link SETUP/ADDITION RESPONSE message is reached due to high number of neighboring cells (for example, when multiple RLs are used for DRNC), it can cause problems in RL setup over Iur interface. That can be visible to operator as increase of the counter M1004C168 (SHO BRANCH SETUP FAIL DUE TO IUR). The PRFILE parameter is required to control the maximum number of RLs in the RNSAP Radio Link Setup/Addition procedure if the number of neighbor cells is high, and thus eliminate too long RNSAP: RADIO LINK SETUP/ADDITION RESPONSE messages. If the value of the PRFILE parameter is 0 (default value), SRNC and DRNC do not limit the number of RLs. If the value of the PRFILE parameter is 1, SRNC limits the number of RLs in RNSAP: RADIO LINK SETUP/ADDITION REQUEST message to one RL, and DRNC limits the number of RLs in RNSAP: RADIO LINK SETUP/ADDITION RESPONSE message to one RL. 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 65 cells. The following formula takes into account also type of the adjacency: (22 + 29 * X) + (22 + 15 * Y) + (7 + 11 * G) + 129 < 4080 bytes Where: • • •

X is the number of intra- and inter-frequency neighbour cells controlled by the DRNC in question (DRNC equals to CRNC). Y is the number of intra- and inter-frequency neighbour cells whose CRNC is other that the DRNC in question. G is the number of GSM neighbour cells.

Default value 0 means that SRNC and DRNC do not limit the number of RLs in the RNSAP Radio Link Setup/Addition procedure. The activation status of the PRFILE parameter can be checked with the following MML command: ZWOI:2,2109; The maximum number of RLs in the RNSAP Radio Link Setup/Addition procedure is limited to one RL by setting the 1st bit (Bit0) of the PRFILE parameter 002:2109 to value 1 with the MML command: ZWOC:2,2109,1;

Issue: 03F

DN0948854

103

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

The limitation on the maximum number of RLs in the RNSAP Radio Link Setup/Addition Procedure is deactivated by setting the 1st bit (bit0) of the PRFILE parameter 002:2109 to value 0 with the MML command: ZWOC:2,2109,0;

Default value(s) 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.93 Parameter 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

Applicable controllers IPA-RNC, from RN7.0 2.0 onwards mcRNC, from mcRNC3.0 1.0 onwards Flexi Direct RNC, from ADA5.0 1.0 onwards

Modifiable YES

Description The RU40_MAINT_14 (002:2110) PRFILE parameter 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 1st bit of the parameter controls the activation/deactivation of correction to set Bursty BLER target value. • •

104

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 value of the 2nd to 7th bit of PRFILE parameter.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value of 2nd to 8th bit of the parameter defines the threshold value for the number of HSUPA UEs in a cell. If the threshold is exceeded, then values of Continuous BLER state parameters are configured for bursty BLER state-related information elements signalled to u-plane. Threshold value can be set from 0 to 127. The default value of PRFILE parameter RU40_MAINT_14 (002:2110) is 0, which means 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. It means that Continuous BLER target value is configured for Bursty BLER target value in case number of HSUPA UEs is above the threshold value and the threshold value for the number of HSUPA UEs in a cell is 35. Activation/Deactivation For setting the Continuous BLER target value to Bursty BLER target value in case number of HSUPA users in a cell is ‘35’ with the 1st to 8th bit of the PRFILE parameter, configure the parameter to value 47H using the following MML: ZWOC: 2,2110,47; For setting no special handling for configuring Bursty BLER target value in case number of HSUPA users in a cell is ‘35’ with the 1st to 8th bit of the PRFILE parameter , configure the parameter value to 46H using the following MML: ZWOC: 2,2110,46;

Default value(s) 0H

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.94 Parameter 002:2111 RU40_MAINT_15 Descriptive name Scaling of RSCP measurement result in blind IFHO between frequency bands

Applicable controllers IPA-RNC, from RN7.0 3.0 onwards mcRNC, from mcRNC3.0 2.0 onwards Flexi Direct RNC, from ADA5.0 1.0 onwards

Issue: 03F

DN0948854

105

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Modifiable YES

Description 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) and Layering in state transition to Cell_DCH state (MBLB) this may result in non-optimal behavior when the measurement result of the source cell is used in the target cell after a blind IFHO or layering if the blind IFHO or layering has taken place between different frequency bands. If the value of the 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 or layering 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 Blind IFHO in RAB setup phase (MBLB) or Layering in state transition to Cell_DCH state (MBLB) takes place between frequency bands. The measurement result of the source cell is used in the decision criteria in the target cell for the following functionalities: • • •

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

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. Activation/Deactivation The activation status of the PRFILE parameter is checked with the following MML command: 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; 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;

Default value(s) QX: 0H

106

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN2172: Multi-Band Load Balancing

2.1.95 Parameter 002:2113 RU40_MAINT_17 Descriptive name DRNC handling of E-DCH SF4, SF8, SF16 etc Support Indicators in Cell Capability Container when cell supports HSUPA

Applicable controllers IPA-RNC, from RN7.0 3.0 onwards mcRNC, from mcRNC3.0 1.0 onwards Flexi Direct RNC, from ADA5.0 1.0 onwards

Modifiable YES

Description 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. The PRFILE parameter is required to control the use of the eleventh and twelfth bits of the Cell Capability Container. If the 002:2113 RU40_MAINT_17 PRFILE parameter is activated (value 1), 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 Indicator to “Supported” and 12th bit: E-DCH SF8 and all inferior SF Support Indicator to “Supported”. If the 002:2113 RU40_MAINT_17 PRFILE parameter is not activated (value 0), legacy handling for setting the E-DCH SF SI’s is used (11th and 12th bits are set to 0). 002:2113 RU40_MAINT_17 bit 0 (the least significant bit) Default value 0 means that DRNC does not set the 11th (E-DCH SF4 and all inferior SF SI) and 12th (E-DCH SF8 and all inferior SF SI) bits of the Cell Capability Container to value 1. Allowed values:

Issue: 03F

DN0948854

107

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

0: DRNC does not set the E-DCH SF4, SF8 and all inferior SF Support Indicators. 1: When Cell supports HSUPA, DRNC sets the SF4, SF8 and all inferior SF Support Indicators to value 1 (“Supported”) in the Cell Capability Container. Status check/Activation/Deactivation The activation status of the PRFILE parameter can be checked with the following MML command: ZWOI:2,2113; The DRNC filling of the SF4 and inferior SFs SIs in the Cell Capability Container is activated by setting the first bit of the 002:2113 RU40_MAINT_17 PRFILE parameter to value 1 with the following MML command: ZWOC:2,2113,1; The filling of the SF4 and inferior SF is deactivated by setting the 1st bit of the 002:2113 RU40_MAINT_17 PRFILE parameter to value 0 with the following MML command: ZWOC:2,2113,0;

Default value(s) QX 0H

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.96 Parameter 002:2115 RU40_MAINT_19 Descriptive name HS-DPCCH ACK/NACK power offset parameter control to prevent call drops with FDPCH due to SCC failure

Applicable controllers IPA-RNC, from RN7.0 2.1 onwards mcRNC, from mcRNC3.0 1.0 onwards Flexi Direct RNC, from ADA5.0 onwards

108

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Description This change is needed to prevent call drops with F-DPCH due to SCC failures. Currently, HS-DPCCH ACK power offset and NACK power offset, fixed amplitude ratio of HS-DPCCH value 15/15 or 24/15 is used depending on the soft HO state of the UE with E-DPDCH. The amplitude ratio of HS-DPCCH is relative to the amplitude ratio of DPCCH when ACK/NACK is sent on HS-DPCCH. UEs in soft HO state have had problems with F-PDCH that led to the drop of the calls. The reason for the drops has been challenging air condition for fast mobility UEs. Call drops are the result of failing Serving Cell Change (SCC). To obtain better SCC success rate with F-DPCH configuration, more power to send “Amplitude Ratio of ACK” and “Amplitude Ratio of NACK” by UE to BTS is needed so that BTS is able to decode information correctly. Too low ACK/NACK power offsets may result in reconfiguration of UE which increases the retransmission of data in DL and causes delays for RRC messages. When 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 the 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 either or both of the following functionalities are used: • •

Dynamic HSUPA Power Offsets feature or/and Dynamic HSUPA BLER feature

This is because both features are meant to decrease the interference level to achieve more room for data transmission. In both cases, when low bit rate optimized HSUPA POs are used, or when the high BLER condition is effective, the lower DPCCH power is used. In such a situation, if UE is located on the edge of cell, it may happen that BTS has problems in decoding information correctly. To avoid unnecessary stuck/retransmission of DL data in BTS over HS-DSCH, a PRFILE controllable solution has been introduced to enable to set the ACK and NACK power offsets to the following values: 15/15, 19/15, 24/15 or 30/15. This is done using the 002:2115 RU40_MAINT_19 PRFILE parameter. The default value of the parameter is ‘0’, where the new functionality is disabled. It means that the existing values are used with E-DCH based on Soft HO state of the UE. When the PRFILE parameter is configured within the range from 0x05H to 0x08 and EDCH is present, the ACK and NACK power offsets are read from the PRFILE. • • • •

Issue: 03F

5H 15/15 value is used for ACK and NACK with E_DCH 6H 19/15 value is used for ACK and NACK with E-DCH 7H 24/15 value is used for ACK and NACK with E-DCH 8H 30/15 value is used for ACK and NACK with E-DCH

The value defined by the PRFILE parameter is used regardless of soft handover state (soft HO or non-soft HO).

DN0948854

109

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

It is recommended to use value 24/15 regardless of Soft HO state by setting the PRFILE parameter to value 7H. When the PRFILE parameter has value out of the 0x05H to 0x08 range and E-DCH is present, the existing values are used, based on Soft HO state of the UE. Status check/Activation/Deactivation The activation status of the PRFILE parameter can be checked with the following MML command: ZWOI:2,2115; The new function can be activated by setting PRFILE parameter within the range with the following MML command (for example, to the recommended value: 7H): ZWOC:2,2115,7; The new functionality can be deactivated by changing PRFILE parameter back to the default value: 0H with the following MML command: ZWOC:2,2115,0;

Default value(s) 0H

Allowed values 0H, 5H, 6H, 7H, 8H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.1.97 Parameter 002:2117 RU40_MAINT_21 Descriptive name PRFILE control for setting Maximum E-DCH Bit Rate signaled towards BTS

Applicable controllers IPA-RNC, from RN7.0 3.0 onwards mcRNC, from mcRNC3.0 2.0 onwards Flexi Direct RNC, from ADA5.0 1.0 onwards

Modifiable YES

110

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Description Live network experiences and test results have shown that limiting of the E-DCH bit rate makes connection more stable when high bit rates are used (around 4 Mbps). Fast variation of E-TFCI causes high 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 parameterization 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 Bit Rate signaled towards BTS. Thus, a new EDCH 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 RAB(s) 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 0 (the default value), then the already existing method is used where 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 bit (BIT0) to 5th bit (BIT4) is different than 0, then 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 in the following manner: xxxx xxxx xxx0 0000

not used

xxxx xxxx xxx0 0001

...

xxxx xxxx xxx1 1111

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 kbps up to 5700 kbps in 100 kbps steps. Based on the field tests, the recommended/optimal value for E-DCH maximum bit rate is 5000 kbps. It can be defined by setting the 002:2117 RU40_MAINT_21 PRFILE parameter to value 0x18H(24 dec => 2600 kbps + 100 kbps * 24 = 5000 kbps). 002:2117 RU40_MAINT_21 PRFILE parameter bits from 1st bit (BIT0) to 5th bit (BIT4) are used to define multiplier (PRFILEMultiplier) for E-DCHMaxBitRate calculation introduced above. Default value 0 means that the existing way is used to define E-DCH maximum bit rate and the equation above is not used. Other values than 0 are used as such in the equation in the following manner:

Issue: 03F

DN0948854

111

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Binary

Hex

Decimal

xxxx xxxx xxx0 0001

xxxx xxxx xxx0 0010

xxxx xxxx xxx0 0011

...

xxxx xxxx xxx1 1111

The value defined by the 002:2117 RU40_MAINT_21 PRFILE parameter with bits from 1st (BIT0) bit to 5th (BIT4) bit is used in configuration E-TTI=2 ms and uplink total symbol rate set 2*SF2+2*SF4 if 16QAM has not been configured. Status check/Activation/Deactivation The activation status of the PRFILE parameter can be checked as follows: In IPA-RNC use the following MML command: ZWOI:2,2117; In mcRNC or FD-RNC use the following SCLI command: show app-parameter configuration-parameter class 2 number 2117

After the parameter value has been changed, the new value becomes effective within 10 minutes. The recommended value for E-DCH Maximum bit rate 5000 kbps can be used by setting the 002: 2117 RU40_MAINT_21 PRFILE parameter to value 0x18H. In IPA-RNC use the following MML command: ZWOC:2,2117,18; In mcRNC or FD-RNC use the following SCLI command: set app-parameter configuration-parameter class 2 number 2117 value 0x18 The new functionality can be deactivated by changing the 002:2117 PRFILE parameter to value 0: In IPA-RNC use the following MML command: ZWOC:2,2117,0; In mcRNC or FD-RNC use the following SCLI command: set app-parameter configuration-parameter class 2 number 2117 value 0x0

Default value(s) 0H

Allowed values 0H-0FF00H

112

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2 Parameter class 007 CALL_CONTROL Descriptive Name Call control

Description This class includes call control definitions.

2.2.1 Parameter 007:0174 CN_INFORMATION_INFO Descriptive name CN Information Info information element for CELL/URA UPDATE CONFIRM

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description 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 this parameter the operator can define if this information element is always included in those messages. The operator can use this parameter, for example, for HomeZone feature purposes. For more information on IEs, see 3GPP TS 25.331, section 10.3.1.3.

Issue: 03F

Value

Meaning

T; F;

If the parameter is in position T (True), the CN Information Info IE is always included in the CELL/URA UPDATE CONFIRM message. If the parameter is in position F (False), the CN Information Info IE is included only during the SRNS relocation (UE not involved).

DN0948854

113

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Default value(s) QX: 0 (F)

Allowed values 1 (T)/0 (F)

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.2.2 Parameter 007:0191 JAPAN_UE_CONTROL Descriptive name Special control due to early UEs

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description A non-zero value of this parameter affects the RRC signaling between RNC and UE. By individual bits and bit string (ttt) you can get special handling for a UE in order to cope (also) with early UEs.

114

Value

Meaning

0000 0000

No special handling for a UE. This is the usual case.

xttt xxx1

The RNC/RRC never moves NEC-VTX-UE to Cell_FACH-state. Instead, the RNC moves it directly to Idle state (DCH->Idle).

xttt xx1x

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

0000 xxxx = 00H0FH

Tx interruption after trigger = Pending time after trigger. This is the usual case.

1000 xxxx = 80H8FH

ttt=0 -> RNC/RRC never sends Tx interruption after trigger to UE.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

1ttt xxxx = 90HFFH

ttt=1-7 -> Tx interruption after trigger index is ttt-1 i.e. 0-6. Thus, it is independent of Pending time after trigger.

Default value(s) QX: 00000000B

Allowed values 00000000B - 11111111B

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.2.3 Parameter 007:0195 RN21_MAINT_003 Descriptive name SHO Branch addition during CM starting phase

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description A new functionality which can be activated by the PRFILE from RN2.1 CD2.0 onwards: the branch addition can be handled in a different way and the operator can define which method is used. Method 1: as earlier, the branch addition is handled immediately, also during the CM start. Method 2: the branch addition is ignored during the CM start and it responds to HA3 by a parallel procedure failure, Parameter needs to be set to value 1. Method 3: the branch addition is saved during the CM start. When the CM starting timer expires, the branch addition is handled. Parameter needs to be set to value 2. To deactivate the change, parameter needs to be set to value 0.

Issue: 03F

DN0948854

115

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Default value(s) QX: 0H

Allowed values 0H - 2H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.2.4 Parameter 007:0208 RNC_MAINT_001 Descriptive name Cell Recovery Improvement

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence For dependencies on other parameters, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

116

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Feature RAN1302: Non-Performing Cell Recovery (RAN1810: Sleeping Cell Improvement, RAN1823: Recovery Logging Improvement)

2.2.5 Parameter 007:0238 RN30_MAINT_015 Descriptive name BSIC verification in case of PS NRT calls

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Description 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 the current RNC specifications, so the implementation is configurable with a PRFILE parameter.

Default value(s) QX: 0H

Allowed values 0H / 1H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.2.6 Parameter 007:0239 RN30_MAINT_016 Descriptive name Non-performing cell recovery improvement

Issue: 03F

DN0948854

117

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Description 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. The features can be activated from RN3.0 CD3.0 onwards. For more details and activation instructions, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence For dependencies on other parameters, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Feature RAN1302: Non-Performing Cell Recovery, RAN1810: Sleeping Cell Improvement, RAN1823: Recovery Logging Improvement

2.2.7 Parameter 007:0240 RN30_MAINT_017 Descriptive name Non-performing cell recovery improvement

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

118

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence For dependencies on other parameters, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Feature RAN1302: Non-Performing Cell Recovery, RAN1810: Sleeping Cell Improvement, RAN1823: Recovery Logging Improvement

2.2.8 Parameter 007:0241 RN30_MAINT_018 Descriptive name Non-performing cell recovery improvement

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Issue: 03F

DN0948854

119

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence For dependencies on other parameters, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Feature RAN1302: Non-Performing Cell Recovery, RAN1810: Sleeping Cell Improvement, RAN1823: Recovery Logging Improvement

2.2.9 Parameter 007:0242 RN30_MAINT_019 Descriptive name Non-performing cell recovery improvement

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

120

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values Dependence For dependencies on other parameters, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Feature RAN1302: Non-Performing Cell Recovery, RAN1810: Sleeping Cell Improvement, RAN1823: Recovery Logging Improvement

2.2.10 Parameter 007:0243 RN30_MAINT_020 Descriptive name Non-performing cell recovery improvement

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Default value(s) QX: 0H

Allowed values 0H - 0FF00H

Forbidden values Dependence For dependencies on other parameters, see Features RAN1302, RAN1810 and RAN1823: Non-Performing Cell Recovery, Feature Activation Manual.

Feature RAN1302: Non-Performing Cell Recovery, RAN1810: Sleeping Cell Improvement, RAN1823: Recovery Logging Improvement

Issue: 03F

DN0948854

121

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.2.11 Parameter 007:0269 RN40_MAINT_001 Descriptive name MOCN improvements

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description 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).

122

Value

Meaning

Both fuctionalities are not active.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

201H

Ignore received Initial UE message when UE selects PLMN ID which was not available under this RNC/Cell.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.

Default value(s) QX: 0H

Allowed values 0H / 201H / 2001H / 2201H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN966: Multi-Operator Core Network

2.2.12 Parameter 007:0270 RN40_MAINT_002 Descriptive name MOCN improvement

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Additional configuration parameters for RAN966: Multi-Operator Core Network feature.

Default value(s) QX: 0H

Issue: 03F

DN0948854

123

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Allowed values 0H-0FF00H

Forbidden values -

Dependence See Activating RAN966: Multi-Operator Core Network.

Feature RAN966: Multi-Operator Core Network

2.2.13 Parameter 007:0279 RN40_MAINT_009 Descriptive name BTS power measurement improvement

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

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

Default value(s) QX: 0H

Allowed values 0H-0FF00H

124

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.2.14 Parameter 007:0280 RN40_MAINT_010 Descriptive name IP defragmentation support on NPS1(P)

Applicable controllers IPA-RNC

Modifiable YES

Description 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. Activation of the IP defragmentation support on NPS1(P): • •

Use the following MML command: ZWOC:7,280,1; Restart the NPS1(P) to load the IP defragmentation support with Iu-PS only function: ZUSU: <unit type NPS1 or NPS1P>,<unit index>;

NOTE: If it is NPS1P, the command should be given to the unit in the WO state; then in both, WO and SP states, the NPS1P restarts. Restarting the NPS1P causes a traffic break. It is highly recommended that the preparations and step 1 are performed before the CD installation, and step 2 is performed as part of CD installation, that is, the system restart.

Default value(s) QX: 0H

Issue: 03F

DN0948854

125

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Allowed values 0H / 1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.15 Parameter 007:0281 RN40_MAINT_011 Descriptive name Adjustable HSUPA BLER target for PS NRT

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description The HSUPA L1 BLER target for PS NRT parameter is changed as an operatormodifiable PRFILE parameter from RN4.0 CD1.2 onwards. This parameter defines the L1 BLER target for the E-DCH MAC-d flow of the PS NRT service. It is used by the outer loop power control of the RNC. The value of the parameter equals the log10 of the BLER value. The parameter has the following alternatives: • • • • •

Parameter values 0…7 mean that the RNC utilizes the default value - 1 (10% BLER). The parameter value 8 means that the RNC utilizes the value - 0.8 (16% BLER). The parameter value 9 means that the RNC utilizes the value - 0.9 (13% BLER), etc. The parameter value 20 (014H) means that the RNC utilizes the value - 2.0 (1% BLER). Parameter values 21 (015H) and higher mean that the RNC utilizes the default value - 1 (10% BLER).

Default value(s) QX: 0H

Allowed values 0H-0FF00H

126

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN2170: Adjustable HSUPA BLER target for PS NRT

2.2.16 Parameter 007:0283 RN40_MAINT_013 Descriptive name Optimization of the RRM algorithms in RNC

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

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

Default value(s) QX: 0H

Allowed values 0H-FFH

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

127

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.2.17 Parameter 007:0284 RN40_MAINT_014 Descriptive name PRFILE control for “SIR error to trigger CTS” and “HSPA reconfiguration to DCH after SCC”

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description 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

Please see the following table for the list of possible parameter values.

128

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

Both workaround are disabled (default value).

SIR error to trigger CTS workaround is enabled.

Both workarounds are enabled.

Default value(s) 0H

Allowed values 0H,1H,3H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.18 Parameter 007:0285 RN40_MAINT_015 Descriptive name Limitation for HSDPA UL DCH return channel

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description 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 the PRFILE parameter, and 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 the 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.

Issue: 03F

DN0948854

129

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Parameter values: • •

0 (384 kbps): The maximum bitrate for the HSDPA UL DCH return channel is 384 kbps in the RNC for AMR+HSDPA multirab (default value). 1 (64 kbps): The maximum bitrate for the HSDPA UL DCH return channel is 64 kbps in the RNC for AMR+HSDPA multirab.

Default value(s) QX: 0H

Allowed values 0H / 1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.19 Parameter 007:0286 RN40_MAINT_016 Descriptive name Transport changes for RACH capacity

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description The RACH capacity of Ultrasites is limited by the traffic shaping applied on the transport side. This creates a mis-match 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 a new PRFILE parameter 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.

130

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

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.

Default value(s) QX: 0H

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.20 Parameter 007:0287 RN40_MAINT_017 Descriptive name STM-1 interface capacity overbooking

Applicable controllers IPA-RNC

Modifiable YES

Description 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 the PRFILE parameter. See TS-RNC-SW-136 for a detailed description and activation instructions.

Default value(s) QX: 0H

Allowed values 0H-0FF00H

Issue: 03F

DN0948854

131

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.21 Parameter 007:0290 RN40_MAINT_020 Descriptive name Limitation of new HS-DSCH allocations

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description 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. This functionality is active by default in the RNC.

Default value(s) QX: 0H

Allowed values 0H / 1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

132

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.2.22 Parameter 007:0291 RN40_MAINT_021 Descriptive name Dynamic link optimization

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description From RN4.0 CD1.4 and CD2.0 onwards, a new functionality is added to the RNC with this parameter. It 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. To set own value for Dynamic Link Optimization, use the following instructions: The range of the parameter value is 0-121 (they refer to values between 0 and 12 dB with a 0,1 dB step). Example values: • • • •

0 - 1,5 dB is set (default) 1 - 0,1 dB is set 120 - 12dB is set 121 - 0db is set (parameter has no effect)

Default value(s) QX: 0H

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN866: Dynamic Link Optimization for NRT Traffic Coverage

2.2.23 Parameter 007:0295 RN40_MAINT_025 Descriptive name AAL2 signaling workaround

Issue: 03F

DN0948854

133

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Applicable controllers IPA-RNC

Modifiable YES

Description From RN5.0 MP0 (and RN4.0 CD2.2) onwards, a new functionality is added to the RNC with this parameter. 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.

Default value(s) QX: 0H

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.24 Parameter 007:0296 RN40_MAINT_026 Descriptive name SAB Failure/Restart messages on RNC-initiated CBC connection

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

134

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Description From RN5.0 PP0.1 (and RN4.0 CD2.2) onwards, a new functionality has been added to the RNC with this parameter. 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). It means that SA3 does not initiate IuBC connection establishment towards CBC. Values greater than 0 mean that SA3 initiates an IuBC connection attempt towards CBC.

Default value(s) QX: 0H

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.25 Parameter 007:0297 RN40_MAINT_027 Descriptive name Direct PCH to DCH state transition

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description From RN5.0 PP0.1 (and RN4.0 CD2.2) onwards, a new functionality has been added to the RNC with this parameter. 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. Values and respective thresholds: • •

Issue: 03F

0H - 128 bytes 8H - 8 bytes

DN0948854

135

PRFILE and FIFILE parameter descriptions

• • • • • • • •

PRFILE Descriptions

10H - 16 bytes 20H - 32 bytes 40H - 64 bytes 80H - 128 bytes 100H - 256 bytes 200H - 512 bytes 400H - 1024 bytes FF00H - 0 bytes

Default value(s) QX: 0H

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.26 Parameter 007:0299 RN40_MAINT_029 Descriptive name T314 timer offset

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description From RN5.0 MP1 (and RN4.0 CD2.2) onwards, a new functionality is added to the RNC with this parameter. The T314 timer offset used by the RRC can be set with this parameter. Values from 1 to 60 (0H-3CH) mean that the offset is 1-60 seconds. Any other values (including 0) mean that a four-second offset is used.

Default value(s) QX: 0H

136

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Allowed values 0H-0FF00H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.27 Parameter 007:0304 RN40_MAINT_034 Descriptive name NBAP overload control functionality for narrow Iub configurations

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description With this parameter, NBAP overload control functionality can be adjusted if needed. 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.

Issue: 03F

Note that, unnecessary usage of this more aggressive NBAP overload control functionality can result in unnecessary increase of M1006C203 RRC CONN REJECT DUE TO IUB OVERLOAD CTRL counter even if link capacity would allow more RRC connection requests.

DN0948854

137

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Value

Meaning

Recommended overload control functionality for recommended Iub transport configurations.

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.

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.

Default value(s) QX: 0H

Allowed values 0H-3H

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.2.28 Parameter 007:0306 RN40_MAINT_036 Descriptive name PS memory supervision

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Description This parameter 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).

138

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Allowed values See TS-RNC-HW-076 (section 6).

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.2.29 Parameter 007:0307 RN40_MAINT_037 Descriptive name This PRFILE parameter is used for three different issues: 1. RNC workaround for UE problem 2. Disabling of RNC support for lossless PDU size change 3. Direct State Transfer from Cell_DCH to Cell_PCH

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Default and recommended value for this PRFILE parameter is 0H

Functionality

6th bit

RNC workarounds for UE problems

Disabling of RNC support for lossless PDU size change Direct State Transfer from Cell_DCH to Cell_PCH

5th bit

2nd bit

1st bit X

1. RNC workarounds for UE problems This parameter is used to handle RNC workarounds for UE problems. For further instructions, as well as the list of possible values, see TS-RNC-SW-149. 2. Disabling of RNC support for lossless PDU size change This parameter is used for disabling RNC support for lossless PDU size change. For further instructions, as well as the list of possible values, see TS-RNC-SW-167. 3. Direct State Transfer from Cell_DCH to Cell_PCH

Issue: 03F

DN0948854

139

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2nd lowest bit of this parameter is used to control the use of Direct State Transfer from Cell_DCH to Cell_PCH. Value 0 means that Direct State Transfer from Cell_DCH to Cell_PCH is enabled. This is the recommended value and should not be disabled unless separately discussed with NSN Technical Support. After parameter value has been changed, new functionality takes effect within 10 minutes.

Default value(s) QX: 0H

Dependence Dependence on other parameters does not exist.

Feature -

2.2.30 Parameter 007:0308 RN40_MAINT_038 Descriptive name Terminating Low Priority Signaling initiates RT over NRT

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Parameter 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. Just the two least significan bits (in binary format) of the parliamentary are used (one bit per establishment cause) and so the used values are the following (in hexadecimal format):

140

Value

Meaning

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

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

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

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

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

Default value(s) QX: 0H

Allowed values 0H-3H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.31 Parameter 007:0387 RNC_L3_CONTROL_022 Descriptive name This PRFILE parameter is to control the usage of more ADJx per cell.

Applicable controllers IPA-RNC, mcRNC and Flexi Direct RNC

Modifiable YES

Pre-conditions: Cell remains 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 cell.

Description With this workaround activated the wcel does not get blocked, instead extra ADJx (ADJI and ADJG only) are dropped (not sent in SIB 11/11bis). Workaround consits of two parts:

Issue: 03F

DN0948854

141

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Extra ADJx are removed (ADJI and ADJG are removed in round robin order). Alarm 7775 is raised if ADJx are terminated.

• •

Value (HEX)

Meaning

Functionality is deactivated.

Functionality is activated.

After activating PRFILE parameter, RNC will start truncation of extra inter frequency and Inter RAT neighbouring information whenever it receives SIB update request. In case if RNC is taking recovery actions then truncation of extra inter frequency and Inter RAT neighbouring information will be visible but if system is not doing any recovery action then manual WCEL lock/unlock is required.

Default value(s) QX: 0H

Allowed values 0H/2H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.32 Parameter 007:0388 RNC_L3_CONTROL_023 Descriptive name HSUPA allocation failures with limited WN7.0 HSUPA baseband HW resources / control the NRT DCH bit rate limitations due to the “BTS baseband hardware congestion”.

Applicable controllers IPA-RNC from RN6.0 2.2 onwards mcRNC from mcRNC2.0 1.0 onwards Flexi Direct RNC frm ADA4.0 1.0 onwards

Modifiable YES

142

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Description This parameter defines the NRT DCH services , which bitrates are limited due to BTS baseband HW congestion algorithm (HSUPA_CONG_ALG). For more information see see TS-RNC-SW-189.

Value (HEX)

Meaning

The NRT DCH bit rate limitations are not applied (default value)

Limitations for HSDPA uplink DCH return channels are applied.

Limitations for R99 uplink and downlink DCHs are applied.

Both limitations are applied (recommended value).

After parameter value has been changed workaround is activated after 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-3H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.33 Parameter 007:0389 RNC_L3_CONTROL_024 Descriptive name HSUPA allocation failures with limited WN7.0 HSUPA baseband HW resources / control the initial bit rate limitation threshold (INI_THRESH).

Applicable controllers IPA-RNC from RN6.0 2.2 onwards mcRNC from mcRNC2.0 1.0 onwards Flexi Direct RNC frm ADA4.0 1.0 onwards

Issue: 03F

DN0948854

143

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Modifiable YES

Description This PRFILE parameter is used to control the initial bit rate limitation threshold (INI_THRESH), which is used to trigger the HSUPA_CONG_ALG algorithm. If the averaged value is equal or higher than the INI_THRESH, it triggers the algorithm status to “HW limited”. If the averaged value is lower than both INI_THRESH and MIN_THRESH, the algorithm status is "normal". MIN_THRESH condition triggering has higher priority that the INI_THRESH condition. See the Parameter 007:0390 RNC_L3_CONTROL_025 for more information on MIN_THRESH condition. See the Parameter 007:0391 RNC_L3_CONTROL_026 for more information on the HSUPA_CONG_ALG algorithm.

144

Value (HEX)

Meaning

INI_THRESH is set to 5 (default value).

INI_THRESH is set to 1.

INI_THRESH is set to 2.

INI_THRESH is set to 3.

INI_THRESH is set to 4.

INI_THRESH is set to 5.

INI_THRESH is set to 6.

INI_THRESH is set to 7.

INI_THRESH is set to 8.

INI_THRESH is set to 9.

INI_THRESH is set to 10.

INI_THRESH is set to 11.

INI_THRESH is set to 12.

INI_THRESH is set to 13.

INI_THRESH is set to 14.

INI_THRESH is set to 15.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (HEX)

Meaning

INI_THRESH is set to 16.

INI_THRESH is set to 17.

INI_THRESH is set to 18.

INI_THRESH is set to 19.

INI_THRESH is set to 20.

After parameter value has been changed workaround is activated after 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-14H

Forbidden values -

Dependence Value of INI_THRESH should not be higher than the value of MIN_THRESH (Parameter 007:0390 RNC_L3_CONTROL_025)

Feature -

2.2.34 Parameter 007:0390 RNC_L3_CONTROL_025 Descriptive name HSUPA allocation failures with limited WN7.0 HSUPA baseband HW resources / control the minimum bit rate limitation threshold (MIN_THRESH).

Applicable controllers IPA-RNC from RN6.0 2.2 onwards mcRNC from mcRNC2.0 1.0 onwards Flexi Direct RNC frm ADA4.0 1.0 onwards

Modifiable YES

Issue: 03F

DN0948854

145

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description This PRFILE parameter is used to control the minimum bit rate limitation threshold (MIN_THRESH), which is used to trigger the HSUPA_CONG_ALG algorithm. If the averaged value is equal or higher than the MIN_THRESH, it triggers the algorithm status to “No EDCH capacity”. If the averaged value is lower than both INI_THRESH and MIN_THRESH, the algorithm status is "normal". MIN_THRESH condition triggering has higher priority that the INI_THRESH condition. See the Parameter 007:0389 RNC_L3_CONTROL_024 for more information on INI_THRESH condition. See the Parameter 007:0391 RNC_L3_CONTROL_026 for more information on the HSUPA_CONG_ALG algorithm.

146

Value (HEX)

Meaning

MIN_THRESH is set to 15 (default value).

MIN_THRESH is set to 1.

MIN_THRESH is set to 2.

MIN_THRESH is set to 3.

MIN_THRESH is set to 4.

MIN_THRESH is set to 5.

MIN_THRESH is set to 6.

MIN_THRESH is set to 7.

MIN_THRESH is set to 8.

MIN_THRESH is set to 9.

MIN_THRESH is set to 10.

MIN_THRESH is set to 11.

MIN_THRESH is set to 12.

MIN_THRESH is set to 13.

MIN_THRESH is set to 14.

MIN_THRESH is set to 15.

MIN_THRESH is set to 16.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value (HEX)

Meaning

MIN_THRESH is set to 17.

MIN_THRESH is set to 18.

MIN_THRESH is set to 19.

MIN_THRESH is set to 20.

After parameter value has been changed workaround is activated after 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-14H

Forbidden values -

Dependence Value of INI_THRESH (Parameter 007:0389 RNC_L3_CONTROL_024) should not be higher than the value of MIN_THRESH.

Feature -

2.2.35 Parameter 007:0391 RNC_L3_CONTROL_026 Descriptive name HSUPA allocation failures with limited WN7.0 HSUPA baseband HW resources / number of samples used to calculate average reported measurement value.

Applicable controllers IPA-RNC from RN6.0 2.2 onwards mcRNC from mcRNC2.0 1.0 onwards Flexi Direct RNC frm ADA4.0 1.0 onwards

Modifiable YES

Issue: 03F

DN0948854

147

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description This PRFILE parameter is used to control 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 Parameter 007:0389 RNC_L3_CONTROL_024 and Parameter 007:0390 RNC_L3_CONTROL_025. Default value of this PRFILE parameter is 0, with this value 40 samples are used. The number can be configured in range from 1 to 200. See the following table for example values.

Value (HEX)

Meaning

Number of samples is set to 40 (default value).

Number of samples is set to 1.

Number of samples is set to 100.

Number of samples is set to 200.

After parameter value has been changed workaround is activated after 10 minutes.

Default value(s) QX: 0H

Allowed values 0H-C8H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.36 Parameter 007:0394 RNC_L3_CONTROL_029 Descriptive name RNC-Id and Cell-Id usage for RAN2054: Extension of RNC ids feature

Applicable controllers Flexi Direct RNC from ADA4.0 2.0 onwards

148

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Description This PRFILE 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. For more information on the feature, see RAN2054: Extension of RNC ids feature in Flexi Direct RU30, Feature Descriptions document.

Value (HEX)

Meaning

SIB3/SIB4 Cell Identity IE is encoded with 12 bits used for RNC-Id and 16 bits for Cell-Id (default).

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

After parameter value has been changed, it is activated after 10 minutes. SIB update according to the new PRFILE value does not, however, happen automatically. It requires another trigger that can be, for example, a cell lock/unlock or an update of a radio network parameter that requires SIB update.

Default value(s) QX: 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN2054: Extension of RNC ids

2.2.37 Parameter 007:0397 RNC_L3_CONTROL_032 Descriptive name CS RAB Active Failure Counter improvement

Applicable controllers IPA-RNC, from RN6.0 2.3 onwards

Issue: 03F

DN0948854

149

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

mcRNC, from mcRNC2.0 2.1 onwards Flexi Direct RNC, from ADA4.0 2.0 onwards

Modifiable YES

Description When this functionality is enabled, CS RAB Active Failures are reported to last Serving RNC cell also in situation where both PS and CS connection exists and after radiolink failure UE makes CellUpdate from DRNC (over Iur). If this PRFILE is not enabled the counters are updated for WBTS-0/WCEL-0 (Anchor WBTS) object in such a situation. The following counters are affected: M1001C146 RAB ACTIVE FAILURES DUE TO RADIO INT FOR CS VOICE M1001C162 RAB ACTIVE FAILURES DUE TO RADIO INT FOR CS DATA STREAM

• •

Value (HEX)

Meaning

Functionality is Disabled (default)

Functionality is Enabled.

After parameter value has been changed workaround is activated after 10 minutes.

Default value(s) QX: 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.2.38 Parameter 007:0398 RNC_L3_CONTROL_033 Descriptive name RNC workaround for UE problem

150

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Applicable controllers IPA-RNC, from RN6.0 2.4 onwards mcRNC, from mcRNC2.0 2.2 onwards Flexi Direct RNC, from ADA4.0 2.1 onwards

Modifiable YES

Description Some UE models restart during ongoing data transfer if CPC is activated. A PRFILE controllable workaround is needed in RNC to disable CPC for these users. For further instructions, as well as the list of possible values, see TS-RNC-SW-149 (section 4.13).

Default value(s) QX: 0H

Allowed values 0H/1H

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.3 Parameter class 009 SYSTEM_SUPERVISION Descriptive Name System supervision limit values

Description This class includes limit values related to the monitoring of system functions.

2.3.1 Parameter 009:0101 IUB_DATA_RECV_INTERVAL Descriptive name IUB O&M TCP/IP connection data receive interval

Issue: 03F

DN0948854

151

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Description Data receive interval defines how often the IUB TCP/IP data received by the RNC is read.

Value

Meaning

Received IUB TCP/IP data is read every 5 ms.

Default value(s) : 5D

Allowed values 1D-100D

Increments 1

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature 7992 - IUB-CORBA MEDITATION (DX)

2.3.2 Parameter 009:0102 IUB_CONN_POLLING_TIME Descriptive name IUB O&M TCP/IP connection polling interval

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

152

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Description IUB O&M TCP/IP connection polling interval defines how often the IUB TCP/IP data received by the RNC on the BS O&M receiving socket is read.

Value

Meaning

The BS O&M receiving socket is polled for IUB O&M TCP/IP data every 5 ms.

Default value(s) : 5D

Allowed values 1D-100D

Increments 1

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature 7992 - IUB-CORBA MEDITATION (DX)

2.3.3 Parameter 009:0130 IP_MSG_MON Descriptive name RNC Support for Traffica

Applicable controllers IPA-RNC, mcRNC

Modifiable YES

Description This parameter determines whether the RNC Support for Traffica feature is active or not.

Issue: 03F

DN0948854

153

PRFILE and FIFILE parameter descriptions

Table 1

PRFILE Descriptions

Supported parameters

PRFILE Parameter

Format of reports 1) sent by RNC

IMSI and IMEI 2) availability in reports

0xFF

RU30

• •

0xFE

RU30

•

0x1FF

RU40

• •

0x1FE

RU40

•

IMSI is sent to Traffica. IMEI is not sent to Traffica. Only the first six digits of the IMSI are sent to Traffica IMEI is not sent to Traffica. IMSI is sent to Traffica. IMEI is sent to Traffica if it is available to the RNC. 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.

Default value(s) QX: 00H (FALSE)

Allowed values 0xFF, 0xFE, 0x1FF, 0x1FE

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature RAN1150: RNC Support for Traffica

1) 2)

154

This refers specifically to RRC/RAB and packet call failure Traffica reports. The IMEI is available to Traffica only if it is available to the RNC.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.4 Parameter class 016 ALARM_SYSTEM Descriptive Name Alarm system

Description This class includes the alarm system parameters.

2.4.1 Parameter 016:0000 ALARM_PRINT_END_MARK Descriptive name Alarm print end mark

Applicable controllers IPA-RNC

Modifiable YES

Description The parameter determines the end mark of an alarm printout.

Value

Meaning

No end text

END OF MESSAGE text

Default value(s) GX: 0D

Allowed values 0D/1D

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

155

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.4.2 Parameter 016:0001 LAMP_PANEL_POLARITY Descriptive name Lamp panel polarity

Applicable controllers IPA-RNC

Modifiable YES

Description The parameter determines the lamp panel polarity.

Value

Meaning

Reverse polarity

Normal polarity

Default value(s) GX: 1D

Allowed values 0D/1D

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.4.3 Parameter 016:0002 ALARM_DRIVEN_OUTPUTS Descriptive name Number of alarm outputs directed by alarms

Applicable controllers IPA-RNC

156

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Description The parameter 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.

Value

Meaning

There are no outputs directed by alarms.

8 first outputs out of a maximum of 16 can be directed by alarms.

All outputs (16) can be directed by alarms.

Default value(s) GX: 10D

Allowed values 0D/8D/10D

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.4.4 Parameter 016:0003 LAMP_PANEL_BUZZER Descriptive name Activation of lamp panel buzzer by alarms

Applicable controllers IPA-RNC

Modifiable YES

Issue: 03F

DN0948854

157

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description The parameter defines the way in which the state of alarm outputs is updated in order to control the lamp panel buzzer in case an alarm controlling the alarm output is set. The lamp panel is controlled by the alarm outputs and, by default, the buzzer of the lamp panel is activated only when a new lamp is lit.

Value

Meaning

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

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. With this, the lamp panel buzzer is activated each time a new alarm controlling an alarm output is set.

Default value(s) GX: 0D

Allowed values 0D / 1D

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.4.5 Parameter 016:0004 PRINTING_MODE Descriptive name Printing mode

Applicable controllers IPA-RNC

158

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Description The parameter is used for alarm printing by selecting the printing mode for local output or MML output (active alarms listing or alarm history listing). Printing mode can be long (= 0000H) or short (= 00FFH). The default mode is the long mode.

Default value(s) GX: 0H

Allowed values 0H / 00FFH

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.4.6 Parameter 016:0008 HEARTBEAT_ALM_INTERVAL Descriptive name Heartbeat alarm interval

Applicable controllers IPA-RNC

Modifiable YES

Description The parameter is used for defining the interval, at which the heartbeat alarm is sent from a certain NE to NetAct. The parameter value defines the interval in minutes. The configured value must match in both ends in order to have working supervision for the O&M interface.

Default value(s) GX: 5D

Allowed values 0-1440D

Issue: 03F

DN0948854

159

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Forbidden values Dependence Dependence on other parameters does not exist.

Feature -

2.4.7 Parameter 016:0009 WBTS_LEVEL_ALARM_SWITCH Descriptive name WBTS Level Alarm Switch

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter controls the usage of WBTS level alarm to reduce the alarms in RNC. For instructions, see Activating RAN1461: RNC RNW alarm reduction.

Value

Meaning

the feature is OFF

the feature is ON

Default value(s) GX: 1D

Allowed values 0-1D

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1461 - RNC RNW Alarm Reduction

160

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.4.8 Parameter 016:0010 SUSPEND_MODE_SWITCH Descriptive name Suspended Mode Switch

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter is used to control the usage of suspend mode alarm to reduce the RNC alarms. For instructions, see Activating RAN1461: RNC RNW alarm reduction.

Value

Meaning

the feature is OFF

the feature is ON

Default value(s) GX: 1D

Allowed values 0-1D

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1461 - RNC RNW Alarm Reduction

2.4.9 Parameter 016:0011 WCEL_OUT_OF_USE_NUM Descriptive name WCEL Out Of Use Alarm Number

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Issue: 03F

DN0948854

161

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Modifiable YES

Description This parameter defines the number of WCEL out of use alarm. For instructions, see Activating RAN1461: RNC RNW alarm reduction.

Value

Meaning

300D

After the number of WCEL being out of use alarm is over 300, the following alarms of this kind will be in suspend mode and cannot be seen by alarm database.

Default value(s) QX: 300D

Allowed values 0-1000D

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1461 - RNC RNW Alarm Reduction

2.4.10 Parameter 016:0012 HSPA_ACT_FAIL_NUM Descriptive name HSPA Activation Failure Number

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the number of HSDPA/HSUPA activation failure for a WCEL alarm for suspend mode. For instructions, see Activating RAN1461: RNC RNW alarm reduction.

162

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Value

Meaning

100D

100 alarms

Default value(s) GX: 100D

Allowed values 0-500D

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1461 - RNC RNW Alarm Reduction

2.4.11 Parameter 016:0013 RNW_DATABASE_FAIL_NUM Descriptive name RNW Database Fail Alarm Number

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the number of RNW Database Fail Alarm for suspend mode. For instructions, see Activating RAN1461: RNC RNW alarm reduction.

Value

Meaning

20D

After the number of rnw database fail alarm is over 20, the following alarms of this kind will be in suspend mode and cannot be seen by rnw database.

Default value(s) GX: 20D

Issue: 03F

DN0948854

163

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Allowed values 0-100D

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1461 - RNC RNW Alarm Reduction

2.4.12 Parameter 016:0014 WBTS_LEVEL_ALARM_NUM Descriptive name WBTS Level Alarm Number

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter defines the number of WBTS level alarm for suspend mode. For instructions, see Activating RAN1461: RNC RNW alarm reduction.

Value

Meaning

100D

when the number of wbts level alarm over 100, the following this kind of alarm will be suspend mode

Default value(s) GX: 100D

Allowed values 0-500D

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1461 - RNC RNW Alarm Reduction

164

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.4.13 Parameter 016:0015 BUFFER_ALARM_THRESHOLD Descriptive name Buffered Alarm Threshold

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter with the alarm number parameter such as rnw_database_fail_num defines the limitation. When the alarms is lower than the number then the alarm can be written to database again. For instructions, see Activating RAN1461: RNC RNW alarm reduction.

Value

Meaning

80D

When the alarm number is lower than 80% level, the suspended alarm can be written to alarm database.

Default value(s) GX: 80D

Allowed values 0-100D

Forbidden values Dependence Dependence on other parameters does not exist.

Feature RAN1461 - RNC RNW Alarm Reduction

2.5 Parameter class 038 MML_COMMAND_LOG Descriptive Name MML Command Log parameters

Issue: 03F

DN0948854

165

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description The parameter class includes parameters to define timeout values and disk usage restrictions of the MML Command Log.

2.5.1 Parameter 038:0001 STORAGE_LENGTH Descriptive name MML Command Log: storage length of log contents

Applicable controllers IPA-RNC

Modifiable YES

Description This parameter defines the maximum time for keeping MML command log files on disks. The minimum value is three (3H) days and the maximum value is sixty (3CH) days.

Default value(s) GX: 3CH

Allowed values 3H-3CH

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.6 Parameter class 055 LCS_PARAMETERS Descriptive Name Location-related parameters

Description This class includes parameters related to Location Services (LCS).

166

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

2.6.1 Parameter 055:0003 EMERGENCY_CALL_ISHO_SUP Descriptive name Directed emergency call inter-system handover feature

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description This parameter activates the Directed Emergency Call Inter-System Handover feature. The feature is optional. If the parameter is enabled, emergency calls from UTRAN are directed to the GSM network in order 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 call is done in UTRAN.

Value

Meaning

FALSE

The location of emergency call is done in UTRAN.

TRUE

Emergency calls from UTRAN are directed to the GSM network in order to allow E-OTD location service instead of the cell id and RTTbased location service.

Default value(s) GX: FALSE

Allowed values TRUE/FALSE

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

Issue: 03F

DN0948854

167

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

2.6.2 Parameter 055:0011 AGPS_SUPPORT Descriptive name A-GPS location method support

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Usage of the A-GPS method is allowed for location services.

Value

Meaning

TRUE

Usage of the A-GPS method is allowed.

FALSE

Usage of the A-GPS method is not allowed.

Default value(s) GX: FALSE

Allowed values TRUE/FALSE

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.6.3 Parameter 055:0012 INT_EMERG_CALL_ISHO_SUP Descriptive name Intelligent Directed Emergency Call Inter-system Handover feature

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

168

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Modifiable YES

Description This parameter activates the intelligent directed emergency call inter-system handover feature. The feature is optional. If the parameter is enabled, emergency calls from UTRAN are directed to the GSM network if the requested accuracy is not fulfilled by CI+RTT or A-GPS location methods included in RAS2.2. If the parameter is disabled, the location of the emergency call is done in UTRAN.

Value

Meaning

FALSE

The location of the emergency call is done in UTRAN.

TRUE

The emergency calls from UTRAN are directed to the GSM network if the requested accuracy is not fulfilled by CI+RTT or A-GPS location methods.

Default value(s) GX: FALSE

Allowed values TRUE/FALSE

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.6.4 Parameter 055:0013 NW_AGPS_SUPPORT Descriptive name NW-based A-GPS location method support

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Issue: 03F

DN0948854

169

PRFILE and FIFILE parameter descriptions

PRFILE Descriptions

Description Usage of the NW-based A-GPS method is allowed for location services.

Value

Meaning

TRUE

Usage of the NW-based A-GPS method is allowed.

FALSE

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

Default value(s) GX: FALSE

Allowed values TRUE/FALSE

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.6.5 Parameter 055:0015 IUPC_INTERFACE Descriptive name IUPC interface support

Applicable controllers IPA-RNC, mcRNC, Flexi Direct RNC

Modifiable YES

Description Usage of the IUPC interface is allowed.

170

Value

Meaning

TRUE

Usage of the IUPC interface is allowed.

FALSE

Usage of the IUPC interface is not allowed.

DN0948854

Issue: 03F

PRFILE Descriptions

PRFILE and FIFILE parameter descriptions

Default value(s) GX: FALSE

Allowed values TRUE/FALSE

Forbidden values -

Dependence Dependence on other parameters does not exist.

Feature -

2.7 Parameter class 058 OAM_SECURITY Descriptive Name O&M Security Parameters

Description This parameter class includes parameters concerning O&M security.

2.7.1 Parameters 058:0000 PW_POLICY_FEATURE, 058:0001 UA_POLICY_FEATURE, 058:0004 USER_ACCOUNT_LOCK_LIMIT These parameters are used to control RAN2883: User Security Policy for RNC196/450/2600, for more information, see WCDMA RAN, Rel. RU40, Feature Descriptions and Instructions.

Issue: 03F

DN0948854

171