PRFILE Descriptions Issue
Comments
Description
Nokia NetworksPRFILE Descriptions DN0948854 Issue 03H Approval Date 2014-10-01 PRFILE Descriptions The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent 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 © 2014 Nokia Solutions and Networks. All rights reserved. f Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set. Nokia 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. 2 DN0948854 Issue: 03H PRFILE Descriptions Table of Contents This document has 180 pages Summary of changes..................................................................... 8 Issue: 03H 1 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 3 .. 64 Parameter 002:1819 LCH_DIR_SIZE......................62 2..69 2....................... 80 Parameters 002:1908 RN60_MAINT_32 and 002:1909 RN60_MAINT_33........1......66 2................................1..1.....................1....................... 91 DN0948854 Issue: 03H .............1.43 2............ 84 Parameter 002:1913 RN60_MAINT_38.........60 2.............................44 2.50 2......77 2.......................................1............... 89 Parameter 002:1918 RN60_MAINT_37. 59 Parameter 002:1798 OPT_BLOCK_MOVE_PREVENT........76 2................ 55 Parameter 002:1775 RN50_MAINT_57...................1................ 88 Parameter 002:1916 RN60_MAINT_41.....80 4 Parameter 002:1689 RN50_MAINT_15................. 41 Parameter 002:1697 RN50_MAINT_21.. 51 Parameter 002:1717 RN50_MAINT_39.......65 2... 65 Parameter 002:1840 B_PHASE1_SWITCH....... 50 Parameter 002:1716 RN50_MAINT_38...................................................1..1...........1........81 Parameter 002:1912 RN60_MAINT_36.........1.....63 Parameter 002:1818 LCH_TRAN_IN_USE. 72 Parameter 002:1897 RN60_MAINT_22.....1......................68 2.............. 67 002:1868 EDPDCHPowerInterUsage .........................72 2.1......................................PRFILE Descriptions 2......1....................................... 71 Parameter 002:1892 RN60_MAINT_16......................1.................. 44 Parameter 002:1701 RN50_MAINT_25........1.........................71 2........1. 69 Parameter 002:1889 RN60_MAINT_13..........1........1......1....1.....52 2.....46 2.....................39 2..........45 2........................1...............1................40 2............................. 54 Parameter 002:1765 RN50_MAINT_48.....................49 2.......74 2.......1..............1.............................54 2......................................62 Parameter 002:1817 DYNPWROFFSETUSAGE......................................48 2....75 2.... 41 Parameter 002:1696 RN50_MAINT_20..............65 Parameter 002:1876 RN60_MAINT_20...................1..61 2...............1................. 53 Parameter 002:1760 RN50_MAINT_43.......................................................................64 2... 66 Parameter 002:1886 RN60_MAINT_10. 73 Parameter 002:1902 RN60_MAINT_26...1.......................51 2............. 56 Parameter 002:1776 RN50_MAINT_58..............38 2.1.............. 40 Parameter 002:1691 RN50_MAINT_16.78 2.1...........70 2...1...42 2...55 2........56 2........1.............. 74 Parameter 002:1903 RN60_MAINT_27.................58 2... 58 Parameter 002:1792 UP_CAP_UPGRADE.............1..............1... 87 Parameter 002:1915 RN60_MAINT_40.....................1.. 76 Parameter 002:1905 RN60_MAINT_29................................................... 46 Parameters 002:1703 RN50_MAINT_27 and 002:1704 RN50_MAINT_28......................... 61 Parameter 002:1816 IPMUX_MUX_DELAY.......67 2..................................1..37 2.......... 72 Parameter 002:1900 RN60_MAINT_25.....................63 2.............1...... 43 Parameter 002:1700 RN50_MAINT_24.......47 2...... 68 Parameter 002:1888 RN60_MAINT_12.1........................................1...1..................... 85 Parameter 002:1914 RN60_MAINT_39........53 2.........................................57 2............................... 42 Parameter 002:1699 RN50_MAINT_23....................1........... 78 Parameter 002:1906 RN60_MAINT_30......1........1.............. 75 Parameter 002:1904 RN60_MAINT_28.. 45 Parameter 002:1702 RN50_MAINT_26....48 Parameter 002:1706 RN50_MAINT_29..........59 2.....................................79 2...........................73 2..... 60 Parameter 002:1814 LCH_IN_USE....41 2......1.... ...............1........102 2..... 142 Parameter 007:0295 RN40_MAINT_025...............1...1............... 92 Parameter 002:1939 RN60_INT_FEAT_RES_10..................................... 135 Parameter 007:0283 RN40_MAINT_013.... 127 Parameter 007:0240 RN30_MAINT_017.................... 139 Parameter 007:0287 RN40_MAINT_017...1....... 108 Parameter 002:2111 RU40_MAINT_15.. 120 Parameter class 007 CALL_CONTROL...... 129 Parameter 007:0243 RN30_MAINT_020...2.......... 140 Parameter 007:0290 RN40_MAINT_020......95 2..............................2..98 2...........................1..................................... 141 Parameter 007:0291 RN40_MAINT_021.....................1............111 Parameter 002:2115 RU40_MAINT_19 .. 104 Parameter 002:2107 RU40_MAINT_11...................12 2................ 137 Parameter 007:0285 RN40_MAINT_015............93 2.....1.....2.......................................2....2........ 134 Parameter 007:0281 RN40_MAINT_011.2..............1....... 126 Parameter 007:0239 RN30_MAINT_016.113 Parameter 002:2117 RU40_MAINT_21................................... 99 Parameter 002:2099 RU40_MAINT_03... 103 Parameter 002:2105 RU40_MAINT_09.........................5 2.2 2......87 2....1 2...1...14 2...............1......................84 2..................... 136 Parameter 007:0284 RN40_MAINT_014............................23 Issue: 03H Parameter 002:1935 RN60_INT_FEAT_RES_06..97 2............110 Parameter 002:2113 RU40_MAINT_17.... 142 DN0948854 5 ......3 2..................1....91 2..........................88 2........2....2...1.............1...................................................86 2.......................2...............2..........123 Parameter 007:0195 RN21_MAINT_003.... 132 Parameter 007:0279 RN40_MAINT_009...................83 2...81 2.96 2.....2.................2...........................20 2... 98 Parameter 002:2098 RU40_MAINT_02 (case 2)........1...............4 2.........6 2......99 2....94 2......11 2............. 128 Parameter 007:0242 RN30_MAINT_019........1......13 2.......... 133 Parameter 007:0280 RN40_MAINT_010. 127 Parameter 007:0241 RN30_MAINT_018...............2..1........2 2..... 95 Parameter 002:2095 RU40_MAINT_01....122 Parameter 007:0174 CN_INFORMATION_INFO............... 125 Parameter 007:0238 RN30_MAINT_015...................... 102 Parameter 002:2103 RU40_MAINT_07...................................2...7 2..............................92 2............... 107 Parameter 002:2110 RU40_MAINT_14 ..17 2...........................................2....100 2..........................................................1.....1....................82 2.....19 2.......94 Parameter 002:2067 MIN_RE_EDPDCH_GF_VAL.122 Parameter 007:0191 JAPAN_UE_CONTROL.90 2.2......101 2..2...........21 2....... 97 Parameter 002:2098 RU40_MAINT_02 (case 1)................PRFILE Descriptions 2........ 93 Parameter 002:2066 MIN_RE_EDPDCH_GF_TO_BTS................................16 2............ 131 Parameter 007:0270 RN40_MAINT_002................15 2............................2........ 100 Parameter 002:2101 RU40_MAINT_05.......... 106 Parameter 002:2109 RU40_MAINT_13 ........115 Parameter 002:2119 RU40_MAINT_23...2......................................2...........................2.18 2...117 Parameter 002:2121 RU40_MAINT_25...10 2..........................89 2...9 2...................2....2...........1..............1....22 2.... 124 Parameter 007:0208 RNC_MAINT_001................. 130 Parameter 007:0269 RN40_MAINT_001.. 101 Parameter 002:2102 RU40_MAINT_06......1.1.......85 2...8 2..... 138 Parameter 007:0286 RN40_MAINT_016.......... 119 Parameter 002:2122 RU40_MAINT_26.................. ..35 2.........166 Parameter 016:0004 PRINTING_MODE... 169 Parameter 016:0010 SUSPEND_MODE_SWITCH..............5 2..........25 2............6........36 2............... 170 Parameter 016:0012 HSPA_ACT_FAIL_NUM.........2...........................4.2..13 2.......... 169 Parameter 016:0011 WCEL_OUT_OF_USE_NUM..4......31 2................. 177 Parameter 055:0013 NW_AGPS_SUPPORT.............5 2.......6.8 2.....2........ 163 Parameter 016:0000 ALARM_PRINT_END_MARK................ 154 Parameter 007:0391 RNC_L3_CONTROL_026.... 158 Parameter 007:0398 RNC_L3_CONTROL_033...2................4....3 2..........2 2........2.....4......2 2.. 160 Parameter 009:0102 IUB_CONN_POLLING_TIME.....29 2............................................... 162 Parameter class 016 ALARM_SYSTEM.26 2.2 2...............2...........................1 6 Parameter 007:0296 RN40_MAINT_026.......... 173 Parameter class 038 MML_COMMAND_LOG.............. 167 Parameter 016:0008 HEARTBEAT_ALM_INTERVAL.....2........3 2...........1 2........179 Parameter class 058 OAM_SECURITY.....5 2................... 152 Parameter 007:0390 RNC_L3_CONTROL_025...168 Parameter 016:0009 WBTS_LEVEL_ALARM_SWITCH..................4.6 2.1 2..2......2.....................24 2..32 2.......161 Parameter 009:0130 IP_MSG_MON...........174 Parameter 038:0001 STORAGE_LENGTH.................................... 145 Parameter 007:0304 RN40_MAINT_034..........7.......... 178 Parameter 055:0015 IUPC_INTERFACE... 164 Parameter 016:0001 LAMP_PANEL_POLARITY.........28 2...9 2.....4......172 Parameter 016:0014 WBTS_LEVEL_ALARM_NUM........... 156 Parameter 007:0394 RNC_L3_CONTROL_029...............10 2.....................12 2...............4...........4 2....................30 2...................... 149 Parameter 007:0387 RNC_L3_CONTROL_022.......6....3 2.....7 2........... 175 Parameter class 055 LCS_PARAMETERS..................4.4 2........34 2.......... 148 Parameter 007:0308 RN40_MAINT_038........7 2.............4........3......................................2...... 147 Parameter 007:0307 RN40_MAINT_037............11 2............37 2...............1 2......... 171 Parameter 016:0013 RNW_DATABASE_FAIL_NUM.2...........6............4............... 150 Parameter 007:0388 RNC_L3_CONTROL_023....3...............PRFILE Descriptions 2.....4.......180 Parameters 058:0000 PW_POLICY_FEATURE.......5. 146 Parameter 007:0306 RN40_MAINT_036.... 173 Parameter 016:0015 BUFFER_ALARM_THRESHOLD..........33 2...........4.......................2......2........1 2................... 159 Parameter class 009 SYSTEM_SUPERVISION..................3 2.... 164 Parameter 016:0002 ALARM_DRIVEN_OUTPUTS..............2.... 144 Parameter 007:0299 RN40_MAINT_029...175 Parameter 055:0003 EMERGENCY_CALL_ISHO_SUP....6...... 165 Parameter 016:0003 LAMP_PANEL_BUZZER... 058:0004 USER_ACCOUNT_LOCK_LIMIT...27 2......38 2................4 2.. 175 Parameter 055:0011 AGPS_SUPPORT.............6 2.. 180 DN0948854 Issue: 03H ...................... 157 Parameter 007:0397 RNC_L3_CONTROL_032.........2..... 143 Parameter 007:0297 RN40_MAINT_027...3............... 058:0001 UA_POLICY_FEATURE.4.... 176 Parameter 055:0012 INT_EMERG_CALL_ISHO_SUP.. 160 Parameter 009:0101 IUB_DATA_RECV_INTERVAL... 151 Parameter 007:0389 RNC_L3_CONTROL_024..... ...................................163 DN0948854 7 ..................................PRFILE Descriptions List of Tables Table 1 Issue: 03H Supported parameters.. 0 2.0 1.0 SW and ADA5.0 SW and ADA5.0 SW. RU40 and 03H (2014-1001. Summary of changes PRFILE Descriptions Summary of changes Changes between document issues are cumulative. mcRNC3. Parameters 002:1908 RN60_MAINT_32 and 002:1909 RN60_MAINT_33 • Parameters 002:1908 RN60_MAINT_32 and 002:1909 RN60_MAINT_33 has been added. RU40) This issue of the document is valid for RN7.0 SW. Parameter 002:2113 RU40_MAINT_17 8 DN0948854 Issue: 03H .0 4. Changes between issues 03E (2014-03-07. Changes between issues 03G (2014-08-27. RU40) This issue of the document is valid for RN7. RU40) This issue of the document is valid for RN7. Parameter 002:2111 RU40_MAINT_15 • Parameter 002:2111 RU40_MAINT_15 has been added. the latest document issue contains all changes made to previous issues. The feature control has been moved to Parameter 007:0394 RNC_L3_CONTROL_029. Parameter 002:2121 RU40_MAINT_25 • Parameter 002:2121 RU40_MAINT_25 has been added. Parameter 002:0241 RNW_DATA_1 has been removed.0 3. Parameter 053:0009 DSCP_FOR_SIGNALLING has been removed.0 SW . Parameter 002:2122 RU40_MAINT_26 • Parameter 002:2122 RU40_MAINT_26 has been added.0 SW and ADA5.0 3. Therefore. Parameter 002:1876 RN60_MAINT_20 • Parameter 002:1876 RN60_MAINT_20 has been added. Parameter 002:1864 HSPA_OVER_IUR_EXT has been removed. • • • • Parameter 002:1993 EXTENDED_RNCID_IN_USE has been removed. Changes between issues 03F (2014-05-07. mcRNC3.0 1. mcRNC3. Parameter 002:2119 RU40_MAINT_23 • Parameter 002:2119 RU40_MAINT_23 has been added. RU40) and 03G (2014-0827.0 SW.0 3.0 4.0 1.0 SW.0 SW. RU40) and 03F (2014-0507. Parameter 002:1903 RN60_MAINT_27 • Parameter 002:1903 RN60_MAINT_27 has been added. RU40) This issue of the document is valid for RN7. PRFILE Descriptions Summary of changes • Parameter 002:2113 RU40_MAINT_17 has been added.0 SW. mcRNC3.0 SW and ADA5. Changes between issues 03D (2014-01-27.1 SW.0 SW.0 1. mcRNC3. Parameter 002:2115 RU40_MAINT_19 • Parameter 002:2115 RU40_MAINT_19 has been added. Changes between issues 03C (2013-10-31.0 1.0 1. RU40) and 03E (2014-0307. The following parameters have been updated: • Parameter 002:1906 RN60_MAINT_30 The following parameters have been added: • • Parameter 002:2109 RU40_MAINT_13 Parameter 002:2110 RU40_MAINT_14 The following parameters have been removed: • • • Issue: 03H Parameter 002:1938 RN60_INT_FEAT_RES_09 Parameter 007:0249 RN30_MAINT_026 Parameter 007:0301 RN40_MAINT_031 DN0948854 9 . Parameter 002:2117 RU40_MAINT_21 • Parameter 002:2117 RU40_MAINT_21 has been added.0 SW and ADA5.0 1.0 2. Parameter 007:0394 RNC_L3_CONTROL_029 • Parameter 007:0394 RNC_L3_CONTROL_029 has been added. RU40) This issue of the document is valid for RN7.0 2. RU40) and 03D (2014-0127.0 SW. the feature has to be activated before it can be used. for example. In case of FIFILE parameters. the default value of the parameter is OFF. the customer's settings are kept intact during the software upgrade. mcRNC and Flexi Direct RNC. that is. Only the parameters that are intended for modification at the IPA-RNC. The value can be changed from OFF into ON by using the WOA command. In IPA-RNC. Description: A description of the purpose and function of the parameter. hexadecimal (H) or binary numbers (B). A feature parameter is not visible if the feature is not delivered to the customer. Default value. which shows that the parameter value can be changed by using the WOC command of the Parameter Handling MML. The boolean values TRUE/FALSE compare to the hexadecimal values 0FFH/0. During a software upgrade. This means that the parameter is effective only if the operator has bought the feature in question. each of which represents a specific functional area. Descriptive name: The name of the parameter in plain text form. which is used. but in user interface the values are only handled as hexadecimal values. 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 values of changeable parameters are copied from the network element's old software build into the new one using the PRFCNV/FIFCNV conversion. allowed values and forbidden values: The values are documented in decimal (D). The parameters are organized into parameter classes. respectively. 002:0433). 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). Increments: A multiple of allowed values. and the bool values T/F to the decimal values 1/0. The description of an individual parameter includes the following information: • • • • • • • Identifier: consists of the parameter class number and parameter number (for example. mcRNC and Flexi Direct RNC level are listed in this document. Indication of whether the parameter is modifiable: Modifiable parameters have been marked with a YES indicator. Further information and parameter handling Only a description of the parameters and parameter classes included in this software release are given here. Scope This document describes the PRFILE (General Parameter File) and FIFILE (Feature Information Control File) parameters used in the IPA-RNC. If the feature is delivered to the customer. in MML printouts. and of the parameter's official name. Dependence: Name of a feature on which the parameter is dependent. MML commands are used to handle PRFILE parameters: • 10 interrogating parameter value can be done with the ZWOI command: DN0948854 Issue: 03H . the indicator is ON/OFF. In this way. 272. example: ZWOC:7.0. changing parameter value can be done with the ZWOC command: syntax: ZWOC:<parameter class>.<parameter number>. 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. For more detailed instructions on how the parameters are handled in IPA-RNC. For more information on sCLI commands. Issue: 03H DN0948854 11 . see Interrogating and modifying PRFILE and FIFILE parameters in Managing IPA-RNC Software Configuration and WO-Parameter Handling. see Configuring PRFILE and FIFILE parameters in Managing Multicontroller RNC Software Configuration. PRFILE Descriptions Introduction to PRFILE and FIFILE parameters • syntax: ZWOI:<parameter class>.<parameter number>.272.<HEX parameter value>. example: ZWOI:7. In mcRNC and Flexi Direct RNC. see WCDMA Flexi Direct RNC SCLI Commands. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 2 PRFILE and FIFILE parameter descriptions Here are listed the descriptions of the PRFILE and FIFILE parameters.1. 2.0 onwards mcRNC from mcRNC2. 2. Feature - 12 DN0948854 Issue: 03H .0 onwards Modifiable YES Description This parameter is used by the RNW configuration dB (raquel) conversion program.1 Parameter class 002 SYSTEM_FUNCT_CONFIGUR Descriptive Name System functions configuration Description Parameters in this class specify the functional configuration of each delivery.1 Parameter 002:0621 RNW_DATA_1 Descriptive name Radio network parameter Applicable controllers IPA-RNC from RN5. Default value(s) QX: 65280D Allowed values Forbidden values Dependence Dependence on other parameters does not exist. that is the functions that are included or excluded. see Configuring Signaling Connections in ATM Network (IPA-RNC). The possible timer value range from five (5H) seconds to thirty (1EH) seconds.0 onwards Modifiable YES Description This parameter is used by the RNW configuration dB conversion program.2 Parameter 002:0740 RNW_DATA_2 Descriptive name Radio network parameter Applicable controllers IPA-RNC from RN5.0 onwards mcRNC from mcRNC2.1.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2. Feature - 2. For more information.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. Default value(s) QX: 65280D Allowed values Forbidden values Dependence Dependence on other parameters does not exist. Issue: 03H DN0948854 13 . Feature - 2. For more information.1. see Configuring Signaling Connections in ATM Network (IPA-RNC). Feature - 14 DN0948854 Issue: 03H . Default value(s) QX: 3CH Allowed values 2H-3CH Forbidden values Dependence Dependence on other parameters does not exist. The possible timer value range from two (2H) seconds to sixty (3CH) seconds. 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.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. 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: 03H DN0948854 15 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. 16 Value Meaning 0H Not configured with two SYM-MXUs. The RNC is RNC196 Capacity Step 1 - 5. This is the default value. 1H Two SYM-MXUs configured. The RNC is RNC196 Capacity Step 6 - 7 or RNC450 Capacity Step 1 - 3. DN0948854 Issue: 03H PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning 4H 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: 03H DN0948854 17 Feature RAN1302: Non-Performing Cell Recovery (RAN1810: Sleeping Cell Improvement. see Features RAN1302.0 onwards mcRNC from mcRNC2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Forbidden values Dependence For dependencies on other parameters.1.0 onwards Modifiable YES Description RAN914: Flexi WCDMA BTS 1900 feature can be activated with this parameter. Feature Activation Manual.1.2 Feature optionality 008 Applicable controllers IPA-RNC from RN5.2 Feature optionality 004 18 DN0948854 Issue: 03H . RAN1823: Recovery Logging Improvement) 2.10 Parameter 002:1300 RN22_FEATURE_OPT_004 Descriptive name RN2.0 onwards Flexi Direct RNC from I-ADA4. RAN1810 and RAN1823: Non-Performing Cell Recovery. Feature RAN914: Flexi WCDMA BTS 1900 2.9 Parameter 002:1297 RN22_FEATURE_OPT_008 Descriptive name RN2. Default value(s) QX: 0H Allowed values 0H - 0FF00H Forbidden values Dependence Dependence on other parameters does not exist. 0 onwards mcRNC from mcRNC2. 24H Feature is in use.1. For instructions.0 onwards Flexi Direct RNC from I-ADA4. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Applicable controllers IPA-RNC from RN5. Default value(s) QX: 0H Allowed values 0H - 0FF00H Forbidden values Dependence Dependence on other parameters does not exist. see Activating HSPA Service Indicator. Value Meaning 0H Feature is not in use. mcRNC. Feature - 2.0 onwards Modifiable YES Description The value of this parameter determines if the feature is enabled or not.11 Parameter 002:1370 AMR_LIC_WARN_IN_USE Descriptive name AMR license warning in use Applicable controllers IPA-RNC. Flexi Direct RNC Modifiable YES Issue: 03H DN0948854 19 . Feature - 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description This parameter controls the license_capacity_warning alarm. When this value is set to T. Default value(s) QX: 0 (F) Allowed values 1 (T) / 0 (F) Forbidden values Dependence Dependence on other parameters does not exist. Value Meaning T license_capacity_warning alarm is reported according to the AMR amount and AMR license warning threshold.12 Parameter 002:1371 AMR_LIC_WARN_THRESHOLD Descriptive name AMR license warning threshold Applicable controllers IPA-RNC.1. F no license_capacity_warning alarm can be reported. 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. Otherwise. 20 DN0948854 Issue: 03H . license_capacity_warning alarm can work as defined. The value here stands for the percentage of licensed_amr_capacity. no such alarm is reported in AMR situation. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning 64H 100% of licensed_amr_capacity 5AH 90% of licensed_amr_capacity 0H 0% of licensed_amr_capacity Default value(s) QX: 05AH Allowed values 0H - 064H Forbidden values Dependence Dependence on other parameters does not exist.13 Parameter 002:1372 AMR_LIC_WARN_DUR Descriptive name AMR license warning duration Applicable controllers IPA-RNC. mcRNC. 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: 03H Value Meaning 0H the duration is 0s E10H the duration is 3600s DN0948854 21 .1. Feature - 2. Flexi Direct RNC Modifiable YES Description This parameter defines the duration in which the AMR capacity has exceeded the warning threshold. 14 Parameter 002:1373 AMR_LIC_WARN_DUR_CANCEL Descriptive name AMR license cancel warning duration Applicable controllers IPA-RNC. Feature - 2. Value Meaning 0H the duration is 0 days 1EH the duration is 30 days Default value(s) QX: 0AH Allowed values 0H-1EH 22 DN0948854 Issue: 03H . The value here stands for days. 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.1. 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. It is one of the conditions that must be fulfilled to cancel the license_capacity_warning alarm. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values Dependence Dependence on other parameters does not exist. Otherwise. no such alarm is reported in AMR situation. license_capacity_exceeded alarm can work as defined. Feature - Issue: 03H DN0948854 23 . When this value is set to T.1. mcRNC. Flexi Direct RNC Modifiable YES Description This parameter controls the license_capacity_exceeded alarm. Value Meaning T the alarm is reported F 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 - 2.15 Parameter 002:1374 AMR_LIC_ALARM_IN_USE Descriptive name AMR license alarm in use Applicable controllers IPA-RNC. 17 Parameter 002:1376 PS_LIC_WARN_IN_USE Descriptive name PS license warning in use Applicable controllers IPA-RNC.1.1. Feature - 2. mcRNC. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 2. 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. The value here stands for days. Value Meaning 0H 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.16 Parameter 002:1375 AMR_LIC_ALARM_DUR_CAL Descriptive name AMR license cancel alarm duration Applicable controllers IPA-RNC. It is one of the conditions that must be fulfilled to cancel the license_capacity_exceeded alarm. Flexi Direct RNC 24 DN0948854 Issue: 03H . PRFILE Descriptions PRFILE and FIFILE parameter descriptions Modifiable YES Description This parameter controls the license_capacity_warning alarm. Otherwise. mcRNC.18 Parameter 002:1377 PS_LIC_WARN_THRESHOLD Descriptive name PS license warning threshold Applicable controllers IPA-RNC. Feature - 2. Default value(s) QX: 0 (F) Allowed values 1 (T) / 0 (F) Forbidden values Dependence Dependence on other parameters does not exist. Value Meaning T license_capacity_warning alarm can report according to the AMR amount and PS license warning threshold. When this value is set to T. no such alarm is reported in PS throughput. Issue: 03H DN0948854 25 . F no license_capacity_warning alarm can be reported. The value here stands for the percentage of licensed_ps_capacity. license_capacity_warning alarm can work as defined.1. 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. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning 64H 100% of licensed_amr_capacity 5AH 90% of licensed_amr_capacity 0H 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. 26 Value Meaning 0H the duration is 0s E10H the duration is 3600s DN0948854 Issue: 03H 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 0H the duration is 0 days 1EH the duration is 30 days Default value(s) QX: 0AH Allowed values 0H-1EH Issue: 03H DN0948854 27 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 T the alarm is reported F 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 - 28 DN0948854 Issue: 03H Feature - 2. mcRNC. Value Meaning 0H 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. mcRNC.1.23 Parameter 002:1546 ICSU_WINDOW_SIZE Descriptive name ICSU WINDOW SIZE Applicable controllers IPA-RNC. It is one of the conditions that must be fulfilled to cancel the license_capacity_exceeded alarm. Flexi Direct RNC Issue: 03H DN0948854 29 .1. The value here stands for days. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2. 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.22 Parameter 002:1381 PS_LIC_ALARM_DUR_CAL Descriptive name PS license cancel alarm duration Applicable controllers IPA-RNC. and there is no limit to the number of ongoing RNW initialization and recovery tasks.1. Flexi Direct RNC Modifiable YES Description The value of this parameter indicates whether the HSUPA Service Indicator feature is in use or not. HSPA configuration/recovery). Feature - 2. common channel creation/recovery. Value Meaning 0H ICSU WINDOW SIZE is not in use. Default value(s) QX: 0AH Allowed values 0H - 0FF00H Forbidden values Dependence Dependence on other parameters does not exist. cell setup/recovery. NBAP link establishment/release. common measurement initialization/recovery.24 Parameter 002:1632 HSUPA_SERVICE_INDICATOR Descriptive name HSUPA Service Indicator Applicable controllers IPA-RNC. 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. For more details see Activating HSPA Service Indicator in Activating and Verifying RU10 Features 30 DN0948854 Issue: 03H . mcRNC. 25 Parameter 002:1649 IP_LINK_BREAK_REL_DELAY Descriptive name Delay for call release in IP link break. Issue: 03H Value Meaning 0H Immediate release of calls. and example values. Please see the following for default.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning 0H 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. DN0948854 31 . Applicable controllers IPA-RNC. Feature RAN1164: HSDPA Service indicator RAN826: Basic HSUPA RAN763: Basic HSDPA with QPSK and 5 codes in the RNC • • • 2. mcRNC Modifiable YES Description This parameter defines the call resource release delay in case of link failure when IP based transport is used. 1H The release delay duration is 1 second. 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. DN0948854 Issue: 03H . Default value(s) QX: 0H Allowed values 0H - 1EH Forbidden values Dependence Dependence on other parameters does not exist. Applicable controllers IPA-RNC Modifiable YES Description The parameter indicates whether the “Revertive Switchover” feature is in use or not. 10H The release delay duration is 16 seconds. 1EH The release delay duration is 30seconds. Feature - 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning AH The release delay duration is 10 seconds.26 Parameter 002:1662 REVERTIVE_SWO_IN_USE Descriptive name Revertive Switchover is in use.1. 0FFH (TRUE) The Revertive Switchover is in use. 32 Value Meaning 0H (FALSE) The Revertive Switchover is not in use. 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: 03H DN0948854 33 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 34 DN0948854 Issue: 03H 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 0 RU20 counter functionality is used (default). 1 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: 03H DN0948854 35 1. see TS-RNC-SW-149 (section 6) After the parameter value has been changed.32 Parameter 002:1671 RN50_MAINT_08 Descriptive name RNC workaround for UE problem Applicable controllers mcRNC. the change is implemented within 10 minutes. as well as the list of possible values.31 Parameter 002:1670 RN50_MAINT_07 Descriptive name RNC workaround for CN problem Applicable controllers IPA-RNC. For further instructions. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. 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. Feature - 2. Flexi Direct RNC 36 DN0948854 Issue: 03H . PRFILE and FIFILE parameter descriptions PRFILE Descriptions Default value(s) QX: 0H Dependence Dependence on other parameters does not exist.1. Feature - 2. mcRNC. 1. mcRNC.33 Parameter 002:1673 RN50_MAINT_10 Descriptive name RNC workaround for UE problem Applicable controllers IPA-RNC. the change is implemented within 10 minutes. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist.2) After the parameter value has been changed. 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. Feature - 2. Feature - Issue: 03H DN0948854 37 . Flexi Direct RNC Modifiable YES Description RL failures when SRB of UE with Qualcomm chipset is assigned to a certain DL Spreading Code. as well as the list of possible values. For further instructions. see TS-RNC-SW-149. see TS-RNC-SW-149 (section 5. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. 38 DN0948854 Issue: 03H .35 Parameter 002:1686 RN50_MAINT_13 Descriptive name RNC workaround for UE problem. the SIB files contain only mandatory information and some messages are not sent at all (if the information is already included in other messages). Feature - 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 2. 1 Function activated. If the function is activated. Default value(s) QX: 0H Allowed values 0H/1H Forbidden values Dependence Dependence on other parameters does not exist. cell lock/unlock needs to be performed for the change to be implemented. g Value Meaning 0 Function deactivated (default).1. Flexi Direct RNC Modifiable YES Description This parameter is used to reduce the size of SIB messages. Note that after parameter value has been modified.34 Parameter 002:1684 RN50_MAINT_11 Descriptive name SIB optimizations Applicable controllers IPA-RNC. mcRNC.1. mcRNC. the RNC waits for RRCConnectionComplete for a time specified by PRFILE parameter.g. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. For further instructions. as well as the list of possible values. mcRNC. the change is implemented within 10 minutes. For further instructions. 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. Flexi Direct RNC Modifiable YES Description Some UE models are behaving erroneously.1. If RRCConnectionSetupComplete is received during waiting time.36 Parameter 002:1687 RN50_MAINT_14 Descriptive name RNC workaround for UE problem Applicable controllers IPA-RNC. Issue: 03H DN0948854 39 . With this parameter. see TS-RNC-SW-149 (section 5. Sometimes UE retransmits RRCConnectionRequest very fast with protocol error indication. see TS-RNC-SW-149 (section 5. Samsung Galaxy S).6). then RRCConnectionRequest with protocol error indication is not processed. as well as the list of possible values. Feature - 2. After the parameter value has been changed. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Applicable controllers IPA-RNC.7). even before UE has received the original RRCConnectionSetup. the change is implemented within 10 minutes.75} Codec Set causes UL muting for some old R99 UEs. Feature - 2. see TS-RNC-SW-149 (section 5. Feature - 40 DN0948854 Issue: 03H . Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. 4. the change is implemented within 10 minutes.8). 4. PRFILE and FIFILE parameter descriptions PRFILE Descriptions After the parameter value has been changed. For further instructions.9.1. mcRNC. NSN RNC does not use AMR {5.75} Codec Set for R99 UE if workaround is activated.9.37 Parameter 002:1689 RN50_MAINT_15 Descriptive name RNC workaround for UE problem Applicable controllers IPA-RNC.75} is enabled by cell level RWN parameter CSAMRmodeSET. even {5. 4. as well as the list of possible values.9. Flexi Direct RNC Modifiable YES Description Usage of AMR {5. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. PRFILE controlled workaround for this UE problem is implemented to NSN RNC. After the parameter value has been changed. For further instructions.38 Parameter 002:1691 RN50_MAINT_16 Descriptive name RNC workaround for UE problem. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. 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.1.3). 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. mcRNC Modifiable YES Issue: 03H DN0948854 41 .39 Parameter 002:1696 RN50_MAINT_20 Descriptive name CM Plan upload fails. Feature - 2. Applicable controllers IPA-RNC. mcRNC. see TS-RNC-SW-149 (section 5. After the parameter value has been changed. the change is implemented within 10 minutes. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2. Applicable controllers IPA-RNC. as well as the list of possible values.1. Length of the delay timer is defined by the value of the parameter. Flexi Direct RNC Modifiable YES 42 DN0948854 Issue: 03H . After the parameter value has been changed.1. Value Meaning 0 Delay timer is set to 10 minutes.40 Parameter 002:1697 RN50_MAINT_21 Descriptive name RNC improvement to prevent unnecessary RL signaling during BTS transport congestion. Applicable controllers IPA-RNC. 1-3C Delay timer is set to 1 - 60 minutes. value 0H is used for 10 minutes. the change is implemented within 10 minutes. mcRNC. 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. Feature - 2. and values from 1H to 3CH define the delay time in minutes (60 minutes maximum). Default value(s) QX: 0H Allowed values 0H-3CH Forbidden values Dependence Dependence on other parameters does not exist. For further instructions. Issue: 03H DN0948854 43 . mcRNC. After the parameter value has been changed. 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. Applicable controllers IPA-RNC. Default value(s) QX: 0H Allowed values 0H/1H Forbidden values Dependence Dependence on other parameters does not exist.41 Parameter 002:1699 RN50_MAINT_23 Descriptive name RNC workaround for UE problem.9). it prevents the unnecessary RL signaling during BTS transport congestion. Feature - 2.1. the change is implemented within 10 minutes. Value Meaning 0 Change is not activated. see TS-RNC-SW-149 ( Section 5. as well as the list of possible values. 1 Change is activated. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Description When this parameter is active. 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. 1-FF00 The delay timer is active (from 10 seconds to 652800 seconds). when the state of Iu links is changing multiple times. the change is implemented within 10 minutes. Flexi Direct RNC Modifiable YES Description PRFILE controllable timer is implemented to RNC. Feature - 2. Value Meaning 0 No delay. The parameter value indicates the timer duration in seconds multiplied by 10. After the parameter value has been changed.1. 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 change is implemented within 10 minutes. Timer is recommended to be used in case of continuous Core Network problems.42 Parameter 002:1700 RN50_MAINT_24 Descriptive name Workaround to manage SIB update delay functionality in RN5.0. Applicable controllers IPA-RNC. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. PRFILE and FIFILE parameter descriptions PRFILE Descriptions After the parameter value has been changed. Default value(s) QX: 0H Allowed values 0H-FF00H 44 DN0948854 Issue: 03H . mcRNC. 1.43 Parameter 002:1701 RN50_MAINT_25 Descriptive name Data forwarding support for PS service during SRNS relocation. The protocol type bit in GTP header is set again when forwarding PDUs to target RNC. the change is implemented within 10 minutes. Platform part will route data correctly based on the indication from PDCP layer. RNC L3 commands PDCP layer to start data forwarding. Applicable controllers IPA-RNC. Feature - 2. For the forwarded data. After the parameter value has been changed. 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. Default value(s) 0H Issue: 03H DN0948854 45 . PDCP layer clears the protocol type bit in GTP header to distinguish it from normal UL data. mcRNC. When data forwarding is enabled during SRNS relocation. the new DL data coming in will be forwarded to target RNC directly by interface unit (GTPU/EIPU). Value Meaning 0 Data forwarding is disabled (default value) 1 Data forwarding is enabled. When data forwarding is disabled during SRNS relocation. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values Dependence Dependence on other parameters does not exist. there is no change compared to current implementation. and starts data forwarding. That is buffered data will be dropped by PDCP layer and. 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 UE reports lower EcNo value the DRRC is not done but the UE stays in current layer. mcRNC. Threshold value for low EcNo can be also configured with same PRFILE parameters. This prevents DRRCs from too poor radio conditions. It is possible that calculated initial power for DRRC is equal to maximum initial power (Ptc. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Allowed values 0H-1H Forbidden values - Dependence Dependence on other parameters does not exist. If RRC connection setup fails without DRRC in HSDPA cell.1. is calculated using maximum HSDPA traffic power instead of last reported power value from the BTS. Possible Bit values: 46 DN0948854 Issue: 03H . In this situation it might be that this is not enough for DRRC to succeed.init = Ptx. 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. it might be due to too low initial power with low EcNo. There is also possibility to set EcNo threshold which defines the lowest reported EcNo for DRRC. 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. If separately activated. initial DL transmission power for the UE that has reported low EcNo. With PRFILE it is possible to configure that DRRC is not started if calculated initial power equals to maximum initial power.max). Feature - 2.44 Parameter 002:1702 RN50_MAINT_26 Descriptive name RRC Access Failure due to RADIO Applicable controllers IPA-RNC. Range -23. • 2nd bit to 7th bit: Are used to configure wanted EcNo threshold value. the change is implemented within 10 minutes.init = Ptx. Issue: 03H DN0948854 47 .5 to 0 dB step 0. Default value(s) QX: 0H Allowed values 0H-255H Forbidden values Dependence Dependence on other parameters does not exist. Here are some examples for EcNo threshold values (when functionality is activated only for DRRC): – – – – – – x000 000x xxxx xxxx: -23.5 to 0 dB.max functionality is on) 9th bit: Is used to control feature activation for non-DRRC case – – • 3H (00000011): -23.5 dB.init = Ptx. PRFILE Descriptions PRFILE and FIFILE parameter descriptions • 1st bit: Is used to control feature activation with DRRC.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.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. Activation with default EcNo threshold value (-11dB) is done with 1H (00000001). 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.5 dB.max functionality is off) – Value 1: ON (DRRC cancel when Ptc. with step 0. RNC subtracts the configured value from the SIRDPCCHInitialEDCH. and the EDCH TTI value. or SCC. Applicable controllers IPA-RNC.128) 03 02 01 00 LSB HIGH DPCCH PO The offset values are defined for 002:1704 RN50_MAINT_28 PRFILE parameter as follows: MSB 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 LOW DPPCH PO LOW DPPCH PO LOW DPCCH PO LOW DPCCH PO 2xSF2+10ms TTI 2xSF2+2ms TTI 2xSF4 + 10ms TTI 2xSF4+2ms TTI LSB Complete mapping table of individual offset values: 48 DN0948854 Issue: 03H . the spreading factor. the parameter values corresponding to high power offsets are used. mcRNC. The change applies only to first RL setup. There are no changes to RL reconfiguration.64. and no branch additions either. It is also checked that the minimum SIR target parameter is not higher than the subtracted SIR value. and to decrease RTWP values.45 Parameters 002:1703 RN50_MAINT_27 and 002:1704 RN50_MAINT_28 Descriptive name HSUPA Initial SIR target offset enhancement and DynPwrOffsetUsage alignment. Dynamic HSUPA Power Offsets feature. which is dependent on the selected high or low DPCCH power offsets.16. When the functionality is enabled. If Dynamic HSUPA Power Offset feature is disabled. 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. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Feature - 2.1. The offset values are defined for 002:1703 RN50_MAINT_27 PRFILE parameter as follows: MSB 15 14 13 12 11 10 09 08 07 06 05 04 LOW DPPCH PO LOW DPPCH PO LOW DPCCH PO SF4+10ms TTI SF4+2ms TTI (SF8.32. 0 11 5.0 7 3.0 9 4.0 3 1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions PRFILE value (dec) SIR offset (dB) 0 0.5 2 1. Default value(s) 0H Allowed values 0H-CH Forbidden values - Dependence Dependence on other parameters does not exist.0 5 2. For detailed description and activation method see TS-RNC-SW-159.5 6 3.5 10 5. Feature - Issue: 03H DN0948854 49 .5 8 4.5 12 6.0 1 0.5 4 2.0 After the parameter value has been changed. the change is implemented within 10 minutes. This timer setting is possible.1. PRFILE controlled change has been made which will release the RRC connection if the Location Update procedure is looped for UE. A Timer is set to 20 s. 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. 6 Timer is set to 10 s. 16 Timer is set to 90 s. If UE repeats the Location Update procedure. 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. 1A Timer is set to 120 s. It can also happen that Location Update attempts fail. If UE does not start location update procedure during that time. 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. Applicable controllers IPA-RNC. For example. DN0948854 Issue: 03H . In addition. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 2. E Timer is set to 30 s. Then UE can initiate the Location Update procedure again. 12 Timer is set to 60 s. if RL failure happens during ongoing Location Update and RNC loses the “Location Update-Accept” due to RLC re-establishment. Flexi Direct RNC Modifiable YES Description After SRNS relocation from another RNC. 50 Value (hex) Meaning 0 Timer is not active (default value). and move the problematic UE to idle mode. the reattempt is not handled correctly in RNC and the Location Update message is lost. PRFILE parameter can be configured to set timer duration after a location update reject has been sent by the CN. only if this functionality has been activated. if UE initiates Location Update procedure. then the ongoing call will be dropped.46 Parameter 002:1706 RN50_MAINT_29 Descriptive name Location Update handling in case of RL failure to release the CS CN signaling connection. and forward it to the RANAP signaling entity for establishment of Iu connection. mcRNC. It has been noticed that certain Rel6 UE models are not able to handle RB reconfiguration involving RLC change with AT.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. After this workaround is activated. 6H.1. The RNC does not need to send any extra RLC parameters or RRC signaling to the UE. EH. Applicable controllers IPA-RNC. Feature - 2. When UE has to perform SL switch with AT and has same time RLC parameters changing and something to schedule. 12H. 1AH. mcRNC. Issue: 03H DN0948854 51 . AH. Flexi Direct RNC Modifiable YES Description RLC parameters for SRB on HSPA RNC uses 2ms TTI for SRB on HSUPA also for Rel6 UEs. the change is implemented within 8 minutes. 1EH Forbidden values - Dependence Dependence on other parameters does not exist. RLC parameters for SRB on HSPA will use the same values as SRB on DCH. After the parameter value has been changed. certain Rel6 UE models interpret this wrongly. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (hex) Meaning 1E Timer is set to 240 s. 16H. Default value(s) 0H Allowed values 0H. 13H Forbidden values - Dependence Dependence on other parameters does not exist.6 UEs cannot handle 2ms TTI allocation correctly. 01 Usage of 2ms for Rel. 52 DN0948854 Issue: 03H . 22H. Default value(s) 0H Allowed values 0H. 02 Usage of 2ms for Rel.6 and Rel. PRFILE and FIFILE parameter descriptions PRFILE Descriptions RNC workaround: Disabling of 2ms TTI based on UE release Some Rel.6 UEs is restricted. • • • • Value Meaning 0 Workaround is not active (default value). 2ms allocation will not be attempted for the following scenarios: user plane setup. After the parameter value has been changed. 03 Usage of 2ms for both Rel.7 UEs is restricted. 11H. With this workaround. TTI switch. 10 Only RLC parameters for SRB on HSPA workaround is active. 10H. 11 Usage of 2ms for Rel. handovers. 03H. 13 Usage of 2ms for both Rel.7 UEs is restricted.7 UEs is restricted and RLC parameters for SRB on HSPA workaround is active. 12 Usage of 2ms for Rel. 01H.7 UEs is restricted and RLC parameters for SRB on HSPA workaround is active. the change is implemented within 10 minutes.6 and Rel. channel type switch. causing thus setup failure counters to be impacted.6 UEs is restricted and RLC parameters for SRB on HSPA workaround is active. 02H. and SRB DCH 3. SRB 3. This can be seen as an RRC connection setup failures. Instead.6 kbps and SRB DCH 3. 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.6 kbps.4 kbps consume the same amount of BTS HW capacity. 1 Correction is active.4 kbps reserves SF 256. SRB 3. Issue: 03H Value Meaning 0 Correction is not active.6 kbps (SF 128) experiences code tree congestion. If SRB DCH 13. that is Core Network domain is CS and Establishment Cause is Conversational Call (Originating/Terminating) or Emergency Call.6 kbps is congested. SRB DCH 13. Currently. then SRB 3. DN0948854 53 . RNC makes a useless retry for SRB with a lower bit rate in case of BTS congestion. if SRB DCH 13. In case of spreading code congestion another retry with lower SRB DCH bit rate 3. where Core Network domain and Establishment Cause indicates AMR speech call.4 kbps is done in case SRB DCH 13. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Feature - 2. because SRB DCH 13.6 kbps (SF 128) experiences code tree congestion.4 kbps (SF 256) retry will not be performed.4 kbps (SF 256) retry will be done.6 kbps experiences BTS HW congestion. pre-emption can be started directly with SRB DCH 13. because AMR CS (DCH) speech call typically needs SF 128.6 kbps reserves SF 128. In this case. mcRNC. This problem results in an extra NBAP signaling in case of BTS congestion.1.4 kbps consume the same amount of BTS HW capacity. An exception to this rule is RRC connection request. Applicable controllers IPA-RNC. BTS congestion of standalone signaling link does not depend on the SRB DCH bit rate.6 kbps and SRB DCH 3.4 kbps retry will not be performed.48 Parameter 002:1717 RN50_MAINT_39 Descriptive name Incorrect SRB congestion handling. Both SRB DCH 13. SRB bit rate does not affect BTS CE consumption. If SRB DCH 13. unnecessary retry with SRB DCH 3.4 kbps was not performed. set with this PRFILE parameter. DN0948854 Issue: 03H .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. a default reporting threshold value 28H (40 dec) is used instead.1H Forbidden values - Dependence Dependence on other parameters does not exist. If the DSP severe error amount drops under the threshold those alarms are canceled. within eight minutes. Reporting threshold is in valid range AH - FEFFH (10 - 65279 dec).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. 000AH-FEFFH Alarming functionality is enabled. 0001H-0009H Alarming functionality is enabled. Applicable controllers IPA-RNC. Feature - 2. Default reporting threshold value 28H (40 dec) is used. RN6.0 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Default value(s) 0H Allowed values 0H. value is used as such. FF00H Alarming functionality is disabled. Threshold is in invalid range. 54 Value Meaning 0000H Alarming functionality is enabled. they can be defined if the RSCP is used to calculate EcNo. Issue: 03H Value Meaning 0H The RNC uses the RSCP that UE has reported when calculating the DL initial power. it requires changing of the intra-frequency measurement quantity needs from EcNo to RSCP. It is defined with RACHIntraFreqMesQuant parameter.50 Parameter 002:1765 RN50_MAINT_48 Descriptive name HS-DSCH and E-DCH success rate decreased after Blind IFHO activation. mcRNC. the measured EcNo is not available for DL initial power calculation anymore. PRFILE Descriptions PRFILE and FIFILE parameter descriptions After the parameter value has been changed. the change is implemented within 10 minutes. 2H-30B4H The functionality is enabled (see the detailed description of the values below). Applicable controllers IPA-RNC.1. Additionally. After this. With this parameter the values of the RSCP0 and BackgroundEcNo can be defined. Flexi Direct RNC Modifiable YES Description When Blind IFHO is activated. DN0948854 55 . 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. 1H The functionality is disabled. resulting in -11 dB 0001 1100 0000 0010. resulting in -23. resulting in -100 dB 0000 0000 0101 0000. 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 -80 dB 0000 0000 1000 1100. 56 DN0948854 Issue: 03H . the change is implemented within 10 minutes. resulting in -10 dB 0010 0000 0000 0010. Default value(s) 0H Allowed values 0H-30B4H Forbidden values Dependence Dependence on other parameters does not exist. resulting in -0 dB After the parameter value has been changed. with a step of 0. See the following examples: • • • • • • 0000 0000 0000 0010. Values range from -119 dB to -30 dB.5 dB 0000 0010 0000 0010.51 Parameter 002:1775 RN50_MAINT_57 Descriptive name RNC workaround for UE problems. 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. resulting in -50 dB 0000 0000 1011 0100. with a step of 1 dB. resulting in -23 dB 0001 1010 0000 0010.5 dB. resulting in -8 dB 0011 0000 0000 0010.1. Feature - 2. resulting in -110 dB 0000 0000 0010 1000. resulting in -119 dB 0000 0000 0001 0100. Special value of 0000 0000 0000 0000 is used to indicate special (default) value of -80 dB. Values range from -23.5 dB to 0 dB. resulting in -30 dB Bits from 9th to 14th define the BackgroundEcNo value. as needed based on which problem is seen in the network: Releasing UE after a failed Integrity Check for UL message and stuck. 1H Releasing UE after a failed Integrity Check for UL message and stuck functionality is enabled. • • Value (HEX) Meaning 0H Both functionalities are disabled. 3H Both functionalities are enabled. Flexi Direct RNC Modifiable YES Description This PRFILE is used to control UE release in hanging situations. mcRNC. With this PRFILE activated. 2H Releasing UE after a failed RRC message decoding for UL message and stuck is enabled. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Applicable controllers IPA-RNC. Feature - Issue: 03H DN0948854 57 . After the parameter value has been changed. the change is implemented within 10 minutes. functionalities can be activated separately. the RNC will release RRC connection of such UEs and update failure counter for RRC connection. Releasing UE after a failed RRC message decoding for UL message and stuck. This workaround is implemented to two detected problem scenarios. so that activation of this workaround is visible in the KPIs and user can re-activate the session after release. Default value(s) 0H Allowed values 0H-3H Forbidden values Dependence Dependence on other parameters does not exist. When Directed RRC connection setup (DRRC) is done. g 58 Please note that as an exception there are two frequency bands which have two same frequencies. UE support is not the problem with HSDPA layering. DRRC is also more likely to fail between frequency bands than within the same frequency band even though the UE supports both frequency bands. DRRC is not allowed between frequency bands (change introduced from RN6. By default. layering for UEs in common channel is allowed between frequency bands. there are two frequency bands which have two same frequencies. but it can be now enabled with this PRFILE parameter. but it can be disabled with this PRFILE parameter. DRRC between these frequency bands is always allowed. 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. Flexi Direct RNC Modifiable YES Description Directed RRC connection setup (DRRC) RRC Connection Request message does not include information about UE frequency band capability. These frequency bands are V and VI. 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.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. These frequency bands are V and VI. By default.0 1. 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. The problem become visible when layer change is done from lower frequency band to higher frequency band. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 2. 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.1. g Please note that as an exception. DN0948854 Issue: 03H . mcRNC.4 onwards). DRRC is always allowed. DRRC between these frequency bands. 1H HSDPA layering for UEs in common channel is enabled. DRRC is disabled. PRFILE Descriptions g PRFILE and FIFILE parameter descriptions Value Meaning 0H HSDPA layering for UEs in common channel is enabled. Flexi Direct RNC Modifiable YES Issue: 03H DN0948854 59 . 11H HSDPA layering for UEs in common channel is disabled.11H Forbidden values Dependence Dependence on other parameters does not exist.53 Parameter 002:1792 UP_CAP_UPGRADE Descriptive name Flexible user plane capacity Applicable controllers IPA-RNC. mcRNC.1H. DRRC is enabled. the change is implemented within 10 minutes. Default value(s) 0H Allowed values 0H.1. 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. DRRC is disabled. 10H HSDPA layering for UEs in common channel is disabled. Feature - 2. DRRC is enabled. After the parameter value has been changed.10H. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description This parameter is used to control Flexible user plane capacity functionality. 60 DN0948854 Issue: 03H . Default value(s) 0H Allowed values 0H/1H Forbidden values Dependence Dependence on other parameters does not exist. the change is implemented within 10 minutes. Applicable controllers IPA-RNC Modifiable YES Description The parameter determines whether automated load balancing between A2SU/A2SP units is prevented or not.1.54 Parameter 002:1798 OPT_BLOCK_MOVE_PREVENT Descriptive name Automated A2SU/A2SP load balancing prevention. After the parameter value has been changed. Value Meaning 0H Flexible user plane capacity functionality is disabled (default value). 1H Flexible user plane capacity functionality is enabled. Feature RAN2261: Flexible User Plane Capacity in RNC196 and RNC450 2. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning 0H Automated load balancing between A2SU/A2SP units is allowed.1. 1H Automated load balancing between A2SU/A2SP units is prevented.0 Modifiable YES Description This parameter indicates whether the alarm triggered log collection functionality is in use or not. DN0948854 61 . Feature - 2. the change is implemented within 10 minutes.55 Parameter 002:1814 LCH_IN_USE Descriptive name Alarm triggered log collection functionality Applicable controllers IPA-RNC. Issue: 03H Value (hex) Meaning 0 Alarm triggered log collection functionality is not in use. Default value(s) 0H Allowed values 0H-1H Forbidden values Dependence Dependence on other parameters does not exist. from RN7. and notice alarm will be set after log zip file is generated. After the parameter value has been changed. 1 Alarm triggered log collection functionality is in use. 2 Delay for multiplexed packet in multiplexing is set to 2 ms (default value). from RN6. but notice alarm will not be set after log zip file is generated.1. Feature RAN1805: RNC Event Triggered Symptom Data Collection 2.56 Parameter 002:1816 IPMUX_MUX_DELAY Descriptive name The max delay of multiplexed PDU Applicable controllers IPA-RNC. the change is implemented within 10 minutes.0 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value (hex) Meaning 2 Alarm triggered log collection functionality is in use. 3 Delay for multiplexed packet in multiplexing is set to 3 ms. DN0948854 Issue: 03H .2 Modifiable YES Description This parameter is used to set delay for multiplexed packet in multiplexing in miliseconds. After the parameter value has been changed. Default value(s) QX: 0H Allowed values 0H-2H Forbidden values Dependence Dependence on other parameters does not exist. 62 Value (hex) Meaning 1 Delay for multiplexed packet in multiplexing is set to 1ms. 57 Parameter 002:1817 DYNPWROFFSETUSAGE Descriptive name DynPwrOffsetUsage Applicable controllers IPA-RNC.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (hex) Meaning 4 Delay for multiplexed packet in multiplexing is set to 4 ms. Flexi Direct RNC Modifiable YES Description This parameter enables/disables the usage of dynamic power offsets for Rel-6 UE. mcRNC. Feature RAN1886: Efficient transport for small IP packet 2. Please note that NPGE unit restart is needed for new value to be taken into account. Value (hex) Meaning 0 Feature enabled 1 Feature disabled Default value(s) QX: 0H Issue: 03H DN0948854 63 . Default value(s) QX: 2H Allowed values 1H-4H Forbidden values Dependence Dependence on other parameters does not exist. Feature - 2.1.0 Modifiable YES Description This parameter indicates whether the alarm triggered log was transferred to OMS or not.58 Parameter 002:1818 LCH_TRAN_IN_USE Descriptive name Alarm triggered log transfer functionality Applicable controllers IPA-RNC. from RN7. Value (hex) Meaning 0 The alarm triggered log was not transferred to OMS 1 The alarm triggered log was transferred to OMS. Feature RAN1805: RNC Event Triggered Symptom Data Collection 64 DN0948854 Issue: 03H . Default value(s) QX: 1H Allowed values 0H/1H Forbidden values Dependence Dependence on other parameters does not exist. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Allowed values 0H/1H Forbidden values Dependence Dependence on other parameters does not exist. Applicable controllers IPA-RNC. from RN7.0 Modifiable YES Description This parameter indicates the size of the alarm triggered log in Mbytes. Feature RAN1805: RNC Event Triggered Symptom Data Collection 2.1.59 Parameter 002:1819 LCH_DIR_SIZE Descriptive name Alarm triggered log directory size Applicable controllers IPA-RNC. Default value(s) QX: 14H Allowed values 9H-FFH Forbidden values Dependence Dependence on other parameters does not exist.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2. default value 14H (20 decimal). means that size of 20 Mbytes is used. Issue: 03H DN0948854 65 .60 Parameter 002:1840 B_PHASE1_SWITCH Descriptive name Switch for source based route phase1 function. for example. mcRNC Modifiable YES Description This parameter can be used to switch on/off source-based route phase1 function. 1 Source based route phase1 function is ON. that is if they have the same IP-based route ID (IPBR ID). Default value(s) 1H Allowed values 0H/1H Forbidden values Dependence Dependence on other parameters does not exist.0 2. As an exception. Feature RAN2190: Source Based Routing in the NPGE 2. RT-over-NRT.1. Without this pre-emption functionality enhancement on the Iur and Iu-CS interfaces. from ADA4. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning 0 Source based route phase1 function is OFF.0 onwards Modifiable YES Description This PRFILE parameter is used to control enhancement to pre-emption functionality that enables CS-over-CS. (However. 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.61 Parameter 002:1876 RN60_MAINT_20 Descriptive name Pre-emption functionality for Iur enhancement Applicable controllers Flexi Direct RNC. pre-emption functionality is supported if there is an Iu congestion) DN0948854 Issue: 03H . the preemption on Iur / Iu-CS is not triggered in the following cases: • • 66 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. in case of UE-involved relocation. it is not possible to use RT-over-NRT functionality to make AMR calls possible. when F-DPCH is enabled Applicable controllers IPA-RNC.0 BTS hardware reservation to be done also with E-TFCI table 1. Issue: 03H Value (HEX) Meaning 0 Functionality is deactivated (default value) DN0948854 67 . Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. the change is implemented within 10 minutes.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (HEX) Meaning 0 Functionality is deactivated (default value) 1 Functionality is activated After the parameter value has been changed. mcRNC. and stability of HSUPA services for 10ms TTI users with F-DPCH enabled. BTS sub unit(s) capacity can be used more efficiently. will be better when E-TFCI table 1 is used. in case of BTS BB hardware limitation. in case of BTS base band HW limitiation with WN7. Feature - 2. Flexi Direct RNC Modifiable YES Description With this PRFILE activated it is possible for WN7.62 Parameter 002:1886 RN60_MAINT_10 Descriptive name Unstable HSUPA service for 10ms TTI users.0 BTS SW. Thanks to this change. 0 onwards Modifiable Yes Description PRFILE parameter 002:1868 EDPDCHPowerInterUsage (Usage of EDPDCH Power Interpolation) is active by default after RN7.0 combination and there can be a minor increase in HSDPA/HSUPA drops due to radio 68 DN0948854 Issue: 03H . from ADA5. In RU30.63 002:1868 EDPDCHPowerInterUsage Descriptive name E-DPDCH power interpolation for 2ms and 10ms TTI Applicable controllers IPA-RNC. from RN7. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist.0-WN7. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value (HEX) Meaning 1 Functionality is activated After the parameter value has been changed. It is recommended to set this functionality off until all BTSs connected to the RNC have been upgraded to WN8.0 onwards mcRNC.0 upgrade.0 onwards Flexi Direct RNC. however. the change is implemented within 10 minutes. RU30 has the hard coded prohibition. the parameter has also default value 0 (feature is enabled). from mcRNC3.1. Feature - 2.0 as the functionality is not fully supported with RN7. Applicable controllers IPA-RNC. • • • Value Meaning 0 Functionality is enabled. Flexi Direct RNC Modifiable YES Description PRFILE parameter controllable workarounds are implemented to the RNC. The following MML commands are used for: checking the status: ZWOI:2. 1 Functionality is disabled. This can be activated/deactivated for PS and CS service. mcRNC. The functionality is disabled by setting PRFILE parameter 002:1868 EDPDCHPowerInterUsage to value 1. Feature - 2.0. 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). Issue: 03H DN0948854 69 .1868.1868. default value/enabling the functionality: ZWOC:2. disabling the functionality: ZWOC:2.1.64 Parameter 002:1888 RN60_MAINT_12 Descriptive name RNC workaround to UE problems with blind IFHO for PS services. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist.1868.1. the values of 1st bit and 4th bit need to be set to “0”. If activated for PS. IFHO using Physical Channel Reconfiguration. needs to be set to “1”. IFHO using Physical Channel Reconfiguration. • To deactivate PS workaround. RB setup. Feature - 70 DN0948854 Issue: 03H . Forbidden values - Dependence Dependence on other parameters does not exist. To ensure that SRBs mapping is done based on source cell measurement results during RB setup procedure. Transport Channel Reconfiguration or Radio Bearer Reconfiguration procedure. • To activate CS workaround. the value of 6th bit. RB setup. To activate the prevention for blind IFHO for R99 capable UEs in PS NRT RAB setup. the values of 1st bit. • To deactivate CS workaround. if there are no measurement results available from target cell after blind IFHO. 2nd bit. • To activate PS workaround. • • • • After the parameter value has been changed. • To activate both CS and PS workarounds. With this value the workaround is enabled. It is also possible to prevent (with 5th bit) a blind IFHO for R99 capable UEs in PS NRT RAB setup. the value of 5th bit needs to be set to “1”. 2nd bit. the RNC will do blind IFHO for PS RAB in Cell_DCH state in two stages: 1. 2. Transport Channel Reconfiguration or Radio Bearer Reconfiguration procedure. and 4th bit need to be set to “0”. the value of 7th bit. To ensure that with PS workaround the same transport channel which is used in the source cell is kept in the target cell. 2. the value of 2nd bit needs to be set to “0”. • To deactivate both CS and PS workarounds. the values of 1st bit. the change is implemented within 10 minutes. the RNC will do blind IFHO for AMR RAB in Cell_DCH state in two stages: 1. and 4th bit need to be set to “1”. the value of 5th bit needs to be set to “0”. the values of 1st bit and 4th bit need to be set to “1”. PRFILE and FIFILE parameter descriptions PRFILE Descriptions If activated for CS. needs to be set to “0”. the value of 2nd bit needs to be set to “1”. To deactivate the prevention for 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. the change is implemented within 10 minutes.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. Flexi Direct RNC Modifiable YES Description With this PRFILE active. The cause value IE can have "normal" and "abnormal" value. Value (HEX) Meaning 0 Cause value is included (default value). mcRNC. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2. Feature - Issue: 03H DN0948854 71 . BTS will use abnormal cause value to save failure call related statistics/data for the root cause investigations. the "Cause" value IE is added as a Private Annex Z IE in NBAP:Radio Link Deleltion Request/Radio Link Reconfiguration Cancel message. After the parameter value has been changed.1. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. 1 Cause value is not included. For further instructions. 72 DN0948854 Issue: 03H .1. Feature - 2. see TS-RNC-SW-149. After the parameter value has been changed.66 Parameter 002:1892 RN60_MAINT_16 Descriptive name RNC workaround for UE problem Applicable controllers IPA-RNC. Applicable controllers IPA-RNC. 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.1. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 2. mcRNC. it is possible to disable the use of monitored cell (intrafrequency neighbor cell) in RACH measurement results. as well as the list of possible values.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. Flexi Direct RNC Modifiable YES Description With this PRFILE parameter. the change is implemented within 10 minutes. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. mcRNC. Flexi Direct RNC Modifiable YES Description This parameter is used to handle RNC workarounds for UE problems. After the parameter value has been changed. mcRNC. Flexi Direct RNC Modifiable YES Description With this workaround active RNC delivers maxReportedCellsOnRACH as CurrentCell. Feature - 2. the change is implemented within 10 minutes. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (HEX) Meaning 0 Monitored cell (intra-frequency neighbor cell) measurement results on RACH can be used to define the source cell for blind IFHO.1. 1 Monitored cell (intra-frequency neighbor cell) measurement results on RACH cannot be used to define the source cell for blind IFHO. Issue: 03H DN0948854 73 .68 Parameter 002:1900 RN60_MAINT_25 Descriptive name RNC workaround for UE problem Applicable controllers IPA-RNC. when RACH Intra Frequency Measurement Quantity is CPICH-RSCP in SIB11. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. HSDPA with compressed mode is not supported with NSN drift RNC. then NSN DRNC rejects such request. If serving RNC setups compressed mode inactive or active when HSDPA is active over Iur. Flexi Direct RNC Modifiable YES Description Originally.69 Parameter 002:1902 RN60_MAINT_26 Descriptive name UE mobility in Inter-RNC scenario Applicable controllers IPA-RNC. therefore it does not support HSDPA over Iur if compressed mode is both inactive or active. the change is implemented within 10 minutes. mcRNC. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value (HEX) Meaning 0 Functionality is deactivated (default value) 1 Functionality is activated After the parameter value has been changed. Feature - 2. NSN RNC will accept HSDPA over Iur with compressed mode inactive or active. 74 DN0948854 Issue: 03H .1. As an improvement to allow UE mobility in Inter-RNC scenario with different RAN vendors. the change is implemented within 10 minutes. 1 Fuctionality is activated. The operator may tune the threshold so that it triggers the use of low bit rate optimized HSUPA power offsets later than the current default.70 Parameter 002:1903 RN60_MAINT_27 Descriptive name Delayed Start of Dynamic HSUPA Power offsets due to number of HSPA users Applicable controllers IPA-RNC: RN6. Feature - 2. Issue: 03H DN0948854 75 .0 2. After the parameter value has been changed. then only CPICH RSCP or CPICH EcNo reported by the UE are taken into account in the Dynamic HSUPA Power Offsets algorithm in order to determine when to trigger low bit rate optimized HSUPA power offsets. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (HEX) Meaning 0 Functionality is deactivated (default value).0 onwards Modifiable YES Description This parameter defines an additional threshold for starting Dynamic HSUPA Power Offsets based on the number of HSPA users in a cell. While the total number of HSPA users in the cell is below the threshold. 0 2. Default value(s) 0H Allowed values 0H-7FH Forbidden values - Dependence Dependence on other parameters does not exist.2 Modifiable YES 76 DN0948854 Issue: 03H . Feature - 2. Value (HEX) Meaning 00 Functionality is deactivated (default value). RN6. After the parameter value has been changed. PRFILE and FIFILE parameter descriptions PRFILE Descriptions The number of HSPA users in the cell is the sum of HSPA users with E-TTI=10 ms.71 Parameter 002:1904 RN60_MAINT_28 Descriptive name Recovery of non-performing DSPs Applicable controllers IPA-RNC. The value is the threshold of the number of HSPA users in the cell. see TS-RNC-SW-159 Recommended parameter set and enhanced algorithms for optimizing RRM functionalities. HSPA users with E-TTI=2ms and HSPA Equivalent users. g For more information. 01-7F Functionality is activated. the change is implemented within 10 minutes.1. 0. described in a separate table below. "Non-performing DSP" in this context means an abnormally behaving DSP unit impacting Operator's Services/KPIs.0.0. Value (HEX) Meaning 0 Default value - functionality is enabled. See the following tables for detailed values and their meaning.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 Issue: 03H DN0948854 77 . transient hardware issues. which has not been detected by system as a faulty unit. X. 0. 0.0 0 F F DSP pool related settings. Used to avoid restarts due to short burst of errors.X. The reason may be software issues.0 0 E 0 Bitmask value for 0.0.0.0. Value (HEX) Meaning Mask Min Max Default 0.0 0 F 3 Waiting time of automatic DSP restart after triggering. Actual value in minutes is obtained by multiplication decimal value by 5. Interpreted as 0F34H. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 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.0. There is no pool specific control for CDSP-C specific pools.X 1 F 4 Maximum number of allowed DSP restarts per pool per day. FF00 Functionality is disabled.X. or permanent hardware issues.X. from ADA5.0.0 onwards 78 DN0948854 Issue: 03H . from RN7.1.0 4th Bit 3rd Bit Meaning 2nd Bit 1st Bit X 0 - restarts disabled for HS-DCH Pool 1 - restarts enabled for HS-DCH Pool X 0 - restarts disabled for CCH Pool 1 - restarts enabled for CCH Pool X 0 - restarts disabled for HS CCH Pool 1 - restarts enabled for HS CCH Pool After the parameter value has been changed. the change is implemented within 10 minutes.X.0 1. from mcRNC3. Feature - 2.72 Parameter 002:1905 RN60_MAINT_29 Descriptive name TFCS reduction in the TFCS capability limitation of UE Applicable controllers IPA-RNC.0 onwards FD RNC. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Bitmask value for 0. 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.0 onwards mcRNC. Both methods can be reasonable to be activated together with multimode AMR features RAN580: Load Based AMR Codec Mode Selection. Value (HEX) Limitation of PS NRT DCH for the TFCS capability of UE Limitation of the multimode AMR for the PS DCH 0 Not used Not used 1 Used Not used 10 Not used Used 11 Used Used Default value(s) 0H Issue: 03H DN0948854 79 . This method is called as Limitation of the multimode AMR for the PS DCH in this context. RAN830: AMR Codec Sets and RAN831. Limitation may result to the decreased PS DCH throughputs. then the UE’s capability limitation in the TFCS size can be easily met especially in UL. while it can transmit freely with the other than PS NRT bearers. while established on top of the multimode AMR call in progress. If AMR is established on top of the PS DCHs as the TFO/TrFO call. While the UE has the multimode AMR established. or the multimode AMR is set up on top the PS R99 or HSDPA connections. UEs are able to use bigger TFCSs in DL than in UL. it can be activated with the first bit (LSB) of the parameter. if the UE has also a non-zero PS interactive or background DCH established. and more than one active PS bearers are added in the R99 or HSDPA configurations. by limiting the UL TFCS so that UE can transmit with one PS NRT DCH at a time in the TTI of the DCH. even down to 0 kbps. thereby reducing the probability of dropping the call in radio link reconfigurations. so in most cases DL TFCS capability limitations are avoided by reducing intermediate bit rates of the DL PS DCHs. Bit rate limitations of the PS NRT DCHs for the UE’s TFCS capability limitations. AMR setup is possible without releasing a PS DCH only by reducing further the UL TFCS size. how the Transport Format Combination Set (TFCS) is limited if its size exceeds the TFCS capability of UE. Generally. Fifth bit of the parameter controls. This method is called as the Limitation of PS NRT DCHs for the TFCS capability of UE in this context. Practically same PS DCH bit rates can then be used as with single mode AMR calls. Downgrading and upgrading of the AMR modes may become visible in the speech quality. the AMR codec set cannot be limited in the AMR setup phase. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Modifiable YES Description Parameter defines two methods. whether the multimode AMR call is allowed to be downgraded to its lowest AMR mode. This method shortens also RRC messages. can be avoided by limiting the AMR to its lowest mode while UE has a PS NRT DCH active. 80 DN0948854 Issue: 03H .1. . 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 6 seconds is added. Applicable controllers Flexi Direct RNC from ADA4. Default value of this PRFILE parameter is 0. with this value functionality is disabled.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. 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. After the parameter value has been changed. the change is implemented within 10 minutes. and therefore the CPICH power is increased to normal value 36 seconds after Iu-link recovery .For example value 3 means 30 seconds and on top of that an internal delay of 18 seconds is added. The range is 1-15 dBm (0-FH). For example value 3 means that low power is set to 23 dBm. The range is 0 - 150 seconds (0-FH) and the step is 10 seconds.0 2. and therefore the CPICH power is decreased to low value 48 seconds after Iu-link break has been detected . PRFILE and FIFILE parameter descriptions PRFILE Descriptions Allowed values 0H//1H/10H/11H Forbidden values - Dependence - Feature - 2. CellCpichPowerOffDelayTimer (xxxx YYYY xxxx xxxx).73 Parameter 002:1906 RN60_MAINT_30 Descriptive name Default Iu-link failures customization for Flexi Direct. 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. Feature - 2.0 (CN RN70_0607). Before the correction in RN7.0 3.0 1. The default value of the VCEL- Issue: 03H DN0948854 81 .1. As a result.0 1. mcRNC3.0 2. but the I-BTS Sharing feature license remains disabled. mcRNC3.74 Parameters 002:1908 RN60_MAINT_32 and 002:1909 RN60_MAINT_33 Descriptive name Workaround for RAN1231 HSPA over Iur: CS voice setup failures due to AC over Iur interface Applicable controllers IPA-RNC: RN7. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Default value(s) 0H Allowed values 0H-0FFFH Forbidden values - Dependence There are no dependencies.0 onwards Modifiable YES Description Reason for the fault A correction for the RAN1231: HSPA over Iur feature (related to CS voice setup failures due to AC) has been introduced in RN7. Thus. VCEL parameters that are used during anchoring are controlled with the RAN1759: IBTS Sharing feature license.0 3. VCEL-CSAMRModeSET and VCELCSAMRModeSETWB parameters are modifiable in RNW-database only if the I-BTS Sharing license is enabled.0 (CN RN70_0607). and in RN8.0 (CN mcRNC30_0118). VCEL-parameters were used during anchoring only if the HSPA over Iur extension (RNC-HSPAoverIurExt parameter) was enabled.0 onwards mcRNC: mcRNC3.0 3.0 (CN mcRNC30_0118).0. operator is not able to configure the desired value for these parameters when the HSPA over Iur feature license is enabled.0. and in RN8. 1). Impact to operator and end user Because of this problem AMR call setup is not successful and the M1001C80 RAB_STP_FAIL_CS_VOICE_AC counter is increased for BTSs with the anchoring connections (Iur interface). PRFILE parameters can be used instead of the cell level (WCEL/VCEL) parameters for enabling the use of AMR codec set on RNC level with one MML command once the feature has been activated with FIFILE (the AMR_CODEC_SET_SUPPORT or WAMR_CODEC_SET parameter). The feature needs to be enabled before the workaround can be used. 002:1909 RN60_MAINT_33 It can be used for activating all the NB-AMR codec mode sets that are supported in the RNC. NB AMR codec set usage The RNC level configuration is controlled with the 002:1909 RN60_MAINT_33 PRFILE parameter. In future releases (starting from RN8. any AMR codec set can be established also over Iur-interface even if the sets are disabled by the VCELCSAMRModeSET and VCEL-CSAMRModeSETWB parameters. Workaround As a workaround. PRFILE and FIFILE parameter descriptions PRFILE Descriptions CSAMRModeSET and VCEL-CSAMRModeSETWB parameters is ”OFF”. The 002:1908 RN60_MAINT_32 PRFILE parameter can be used to activate all the WB-AMR codec mode sets that are supported in the RNC. Special conditions for installation To work around the problem related to modification of VCEL-CSAMRModeSET and VCELCSAMRModeSETWB. Note that the general pre-condition is that related AMR code set support feature is enabled. The 002:1909 RN60_MAINT_33 PRFILE parameter can be used to activate all the NB-AMR codec mode sets that are supported in the RNC. that is the AMR_CODEC_SET_SUPPORT or WAMR_CODEC_SET FIFILE parameter. 1. If the PRFILE parameter is enabled (see the activation instructions). AMR coded set can be enabled on RNC level with the following PRFILE parameters: • • 002:1908 RN60_MAINT_32 It can be used for activating all the WB-AMR codec mode sets that are supported in the RNC. RNC level NB AMR support Pre-condition: AMR codec set support The feature is controlled with the AMR_CODEC_SET_SUPPORT FIFILE parameter. SW correction will be provided where VCELCSAMRModeSET and VCEL-CSAMRModeSETWB will be made modifiable also without enabling of the I-BTS Sharing license. It means that there is no AMR codec supported over Iur which results in AMR setup failures during anchoring. 82 DN0948854 Issue: 03H . 1. for mcRNC the 002:1909 RN60_MAINT_33 PRFILE parameter needs to be configured to value 1H with the following SCLI command: set app-parameter configuration-parameter class 2 number 1909 value 1 Deactivation of RNC level NB AMR codec set usage To disable the use of NB AMR codec set on RNC level: • • for IPA-RNC the 002:1909 RN60_MAINT_33 PRFILE parameter needs to be configured to value 0H with the following MML command: ZWOC:2. for mcRNC the 002:1909 RN60_MAINT_33 PRFILE parameter needs to be configured to value 0H with the following SCLI command: set app-parameter configuration-parameter class 2 number 1909 value 0 2. use the following SCLI command: show app-parameter configuration-parameter class 2 number 1909 Activation of RNC level NB AMR codec set usage To enable the use of NB AMR codec set on RNC level: • • for IPA-RNC the 002:1909 RN60_MAINT_33 PRFILE parameter needs to be configured to value 1H with the following MML command: ZWOC:2.1.1909. WB AMR codec set usage RNC level configuration is controlled with the 002:1908 RN60_MAINT_32 PRFILE parameter. Feature activation status of RNC level WB AMR codec set usage To check the activation status of the PRFILE parameter: • • for IPA-RNC. in mcRNC.1909.1908. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Feature activation status of RNC level NB AMR codec set usage To check the activation status of the PRFILE parameter: • • in IPA-RNC. use the following MML command: ZWOI:2.0.1908. The feature needs to be enabled before the workaround can be used. for mcRNC. RNC level WB AMR support Pre-condition: WB AMR codec set support The feature is controlled with the WB AMR_CODEC FIFILE parameter.1909. use the following MML command: ZWOI:2. use the following SCLI command: show app-parameter configuration-parameter class 2 number 1908 Activation of RNC level WB AMR codec set usage To enable the use of WB AMR codec set on RNC level: • • for IPA-RNC the 002:1908 RN60_MAINT_32 PRFILE parameter needs to be configured to value 1H with the following MML command: ZWOC:2. for mcRNC the 002:1908 RN60_MAINT_32 PRFILE parameter needs to be configured to value 1H with the following SCLI command: set app-parameter configuration-parameter class 2 value 1908 number 1 Deactivation of RNC level WB AMR codec set usage To disable the use of WB AMR codec set on RNC level: Issue: 03H DN0948854 83 . g 84 Please note that in order to complete the activation.1 onwards mcRNC. PRFILE and FIFILE parameter descriptions • • PRFILE Descriptions for IPA-RNC the 002:1908 RN60_MAINT_32 PRFILE parameter needs to be configured to value 0H with the following MML command: ZWOC:2. for mcRNC the 002:1908 RN60_MAINT_32 PRFILE parameter needs to be configured to value 0H with the following SCLI command: set app-parameter configuration-parameter class 2 value 1908 number 0 Default value(s) 0H Allowed values 0H/1H Forbidden values NA Dependence Features AMR codec set support/WB AMR codec set support Feature RAN1231: HSPA over Iur RAN1759: I-BTS Sharing 2. from mcRNC2.0 2.1.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). from RN 6.0 onwards Flexi Direct RNC. from ADA4.75 Parameter 002:1912 RN60_MAINT_36 Descriptive name SIB optimization enhancement Applicable controllers IPA-RNC. cell lock/unlock procedure needs to be performed after changing the parameter value DN0948854 Issue: 03H .1908.0.0 2.0 2. 0 2. Issue: 03H DN0948854 85 . from RN 6. it is possible to define the “Delta” value for the following EcNoUE formula. Ptx_total is the carrier power of the cell.CPICH is the code power of primary CPICH.1. Applicable controllers IPA-RNC. when CPICH Ec/No value has not been reported to the RNC. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (HEX) Delta value 0 Sending of Q_offset2 parameter when SIB optimization enhancement is enabled is disabled (default value) 2 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 - 2. which produces calculated CPICH Ec/No UE on cases.76 Parameter 002:1913 RN60_MAINT_38 Descriptive name Higher initial code power during Inter-freq hard handover. Ptx. EcNoUE in producing the initial code power of the radio link to be set up.2 onwards Modifiable YES Description With this workaround active. PRFILE and FIFILE parameter descriptions 86 PRFILE Descriptions Value (HEX) Delta value 0 4dB 1 1dB 2 2dB 3 3dB 4 4dB 5 5dB 6 6dB 7 7dB 8 8dB 9 9dB A 10dB B 11dB C 12dB D 13dB E 14dB F 15dB 10 16dB 11 17dB 12 18dB 13 19dB 14 20dB 15 21dB 16 22dB 17 23dB 18 24dB DN0948854 Issue: 03H . • 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.0 onwards Modifiable YES Description This PRFILE is used to control two functionalities: Issue: 03H • 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.1 onwards Flexi Direct RNC.3 onwards mcRNC. 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.0 2.77 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 mcRNC2.1.0 2. PRFILE Descriptions PRFILE and FIFILE parameter descriptions After the parameter value has been changed. from ADA4. Feature - 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. Default value(s) 0H Allowed values 0H-18H Forbidden values - Dependence Dependence on other parameters does not exist. DN0948854 87 . the change is implemented within 10 minutes.0 2. from RN6. 0 2.0 2.78 Parameter 002:1915 RN60_MAINT_40 Descriptive name RNC workaround for cccasional long delay during plan provisioning.0 onwards Modifiable YES Description With this PRFILE parameter. the change is implemented within 10 minutes. Applicable controllers IPA-RNC. 88 DN0948854 Issue: 03H . from mcRNC2. Default value(s) 0H Allowed values 0H. Feature RAN2262: Flexi Multiradio System Modules 2.0 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 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 0 Disabled Disabled 1 Enabled Disabled 10 Disabled Enabled After the parameter value has been changed. from RN 6. from ADA4.0 onwards Flexi Direct RNC.10H Forbidden values - Dependence Dependence on other parameters does not exist.1H.1.2 onwards mcRNC. 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. from mcRNC3. Feature - 2. from ADA5. Applicable controllers IPA-RNC. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (HEX) Meaning 0 Functionality is activated (default value). 1 Functionality is deactivated.0 onwards Modifiable YES Description This PRFILE parameter is used to control the following: • • Issue: 03H 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 DN0948854 89 .0 onwards Flexi Direct RNC.79 Parameter 002:1916 RN60_MAINT_41 Descriptive name Control of UEs redirection limitation to LTE in case of RAN2717: Smart LTE Layering. from RN7.1.0 onwards mcRNC. 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. After the parameter value has been changed. PRFILE and FIFILE parameter descriptions • PRFILE Descriptions 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 • 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 xxXx • xXxx • 0 (default value): – 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 E-UTRAN Service Handover IE 'Handover to E-UTRAN shall not be performed' is not remembered after the related RAB is released – • 1: – 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 E-UTRAN Service Handover IE 'Handover to E-UTRAN shall not be performed' is not remembered after the related RAB is released – • 2: – Signalling connection only are not redirected to LTE – UE is not redirected to LTE if all its RABs has 'Handover to EUTRAN 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: – 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 E-UTRAN 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 – • 90 5: – 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 E-UTRAN Service Handover IE DN0948854 Issue: 03H . Maximum additional value is 7.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. Default value(s) 0H Allowed values 0H-511H Forbidden values - Dependence Dependence on other parameters does not exist.0) then the PRFILE parameter value is added to it. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Used hexdigits Possible values and Meaning – '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 After the parameter value has been changed. Feature RAN2717: Smart LTE Layering 2.0 2.2 onwards mcRNC. from mcRNC2. If RsrvdSignaturesOffset parameter is set to value 11 (max value in RN6. from RN 6. from ADA4.1. Issue: 03H DN0948854 91 .80 Parameter 002:1918 RN60_MAINT_37 Descriptive name Temporary offset increase for E-RGCH/E-HICH signatures Applicable controllers IPA-RNC.0 onwards Flexi Direct RNC.0 2. the change is implemented within 10 minutes. With additional offset new E-RGCH/EHICH code can be allocated earlier and released later. 81 Parameter 002:1935 RN60_INT_FEAT_RES_06 Descriptive name RANAP Interface signaling change. the change is implemented within 10 minutes. mcRNC. 6 Value 6 is added to the RsrvdSignaturesOffset parameter value. 4 Value 4 is added to the RsrvdSignaturesOffset parameter value. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value (HEX) Meaning 0 Functionality is deactivated (default value). Feature - 2. Flexi Direct RNC Modifiable YES 92 DN0948854 Issue: 03H . 7 Value 7 is added to the RsrvdSignaturesOffset parameter value. 3 Value 3 is added to the RsrvdSignaturesOffset parameter value. 1 Value 1 is added to the RsrvdSignaturesOffset parameter value. After the parameter value has been changed. 2 Value 2 is added to the RsrvdSignaturesOffset parameter value. 5 Value 5 is added to the RsrvdSignaturesOffset parameter value.1. Default value(s) 0H Allowed values 0H-7H Forbidden values - Dependence Dependence on other parameters does not exist. Applicable controllers IPA-RNC. 82 Parameter 002:1939 RN60_INT_FEAT_RES_10 Descriptive name H-RNTI allocation algorithm change. Issue: 03H DN0948854 93 . 10 Signaling change is active. Applicable controllers IPA-RNC. mcRNC.1. Feature - 2. 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. which is that as soon as SRNS relocation has been completed and new U-RNTI has been successfully exchanged with the UE. 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. Value Meaning 0 Signaling change is not active. After the parameter value has been changed. Default value(s) 0H Allowed values 0H/10H Forbidden values Dependence Dependence on other parameters does not exist. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Description This PRFILE is used to control signaling change in RNC. the change is implemented within 10 minutes. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning 0 Cell level H-RNTI pool is used.0 onwards Flexi Direct RNC. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. from ADA4.0 onwards mcRNC. 94 DN0948854 Issue: 03H .0 2.0 2. After the parameter value has been changed.83 Parameter 002:2066 MIN_RE_EDPDCH_GF_TO_BTS Descriptive name Minimum reduced E-DPDCH gain factor Applicable controllers IPA-RNC. 1 BTS level H-RNTI pool is used.0 onwards Modifiable YES Description This PRFILE is used to define whether the minimum reduced E-DPDCH gain factor (also called βed. from RN7.min) is sent to the UE and which value is used. from mcRNC2. the change is implemented within 1 minute.1. Feature - 2. 0 2. Feature - 2.0 onwards mcRNC.0 onwards Modifiable YES Issue: 03H DN0948854 95 .1.0 onwards Flexi Direct RNC. Default value(s) 0H Allowed values 0H-3H Forbidden values - Dependence Dependence on other parameters does not exist.84 Parameter 002:2067 MIN_RE_EDPDCH_GF_VAL Descriptive name Minimum reduced E-DPDCH gain factor Applicable controllers IPA-RNC. from RN7. from mcRNC2.0 2. from ADA4. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value (HEX) Meaning 0 Functionality is deactivated (default value). 3 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. the change is implemented within 10 minutes. 1 The RNC sends the same value as for the UE also to the BTS in Minimum Reduced E-DPDCH Gain Factor IE 2 The SRNC sends the same value as for the UE also over Iur to the DRNC in Minimum Reduced E-DPDCH Gain Factor IE. After the parameter value has been changed. when the Minimum reduced E-DPDCH gain factor IE is sent to UE and in which value. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description This PRFILE is used to define whether the minimum reduced E-DPDCH gain factor (also called βed. the change is implemented within 10 minutes. Minimum reduced E-DPDCH gain factor IE is not sent to UE. 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). After the parameter value has been changed. If there is value 0000 in corresponding place. See the following list for available values. RAB combination does not affect sending these values. 96 DN0948854 Issue: 03H . If the value is set to 0.min) is sent to the UE. Value is reconfigured if needed when TTI is reconfigured between 2 ms and 10 ms TTI. then the value 8/15 is used. For Rel-7 and older UEs Minimum reduced E-DPDCH gain factor IE is not sent in any situation. 1 Correction is used.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. the change is implemented within 10 minutes.0 onwards mcRNC. After the parameter value has been changed. Value Meaning 0 Correction is not used. Issue: 03H DN0948854 97 . PRFILE Descriptions PRFILE and FIFILE parameter descriptions Default value(s) 0H Allowed values 0H-FFH Forbidden values - Dependence Dependence on other parameters does not exist.85 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.1. from ADA5. from mcRNC3.0 onwards Flexi Direct RNC. from RN7. Feature - 2. DCH to PCH was controlled with PRFILE 007: 0307 for HS users. This PRFILE parameter gives option for operator to have DCH to PCH transition as in RU30. there can be more transitions from Cell_DCH to Cell_PCH if the direct transition for HSPA users was allowed in RU30. Therefore when upgrading from RU30 to RU40. The parameter is controlled with the 1st bit. Feature - 2. After the parameter value has been changed. the change is implemented within 10 minutes.0 P8 onwards mcRNC. the RNC moved them directly from Cell_DCH to Cell_PCH if the PRFILE allowed it. resource usage and UE battery drainage. from RN7. when the state transition is done due to PRFILE 007: 0307.0 onwards Flexi Direct RNC.1. from ADA5. 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. This is intended functionality in RU40 to reduce the NW signaling.86 Parameter 002:2098 RU40_MAINT_02 (case 1) Descriptive name DCH to PCH for release 99 users Applicable controllers IPA-RNC.0 onwards Modifiable YES Description In RU30. DCH to PCH is controlled with Management parameter DCHtoPCHEnabled but it applies also to Rel99 PS allocation. from mcRNC3. that is only HS users. In RU40. 98 DN0948854 Issue: 03H . Upon inactivity detection for HSDPA or HSPA users. RNC assumes the UE does not support HSPA configuration and does not allocate HSPA to the UE anymore. Issue: 03H DN0948854 99 . 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. 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.0 onwards Modifiable YES Description When RAN2494 Fast Cell PCH switch feature is enabled.87 Parameter 002:2098 RU40_MAINT_02 (case 2) Descriptive name HSPA allocation problem with RAN 2494 Fast Cell PCH switching Applicable controllers IPA-RNC.0 onwards mcRNC. Additionally. This impacts the HSUPA Setup Success Ratio KPIs. Feature - 2. from mcRNC3. 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. from RN7.0 1. as well as the list of possible values. So the workaround is not recommended to be activated by default. The workaround is under PRFILE and not active by default. RNC will provide the information in the state transition command to Cell_DCH still to the UE. For further instructions.0 onwards Flexi Direct RNC. from ADA5. see TS-RNC-SW-149.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Default value(s) 0H (recommended) Allowed values According to instructions Forbidden values - Dependence Dependence on other parameters does not exist. When the timer expires and RAB Release Request is sent.0 onwards Flexi Direct RNC. Feature - 2. failure counters in measurements M1001 and M1022 are updated.1.0 onwards mcRNC.88 Parameter 002:2099 RU40_MAINT_03 Descriptive name PS RAB release guard timer Applicable controllers IPA-RNC. from RN7.0 onwards Modifiable YES Description This PRFILE parameter defines the guard timer how soon after receiving GTP error indication from PS-CN. from mcRNC3. the RNC sends RAB Release Request to SGSN. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Functionality 5th bit RNC workarounds for release 6 UE problems X RNC workarounds for release 7 UE problems RNC workarounds for release 8 UE problems 6th bit 7th bit X X After the parameter value has been changed. from ADA5. Default value(s) 0H (recommended) Allowed values According to instructions Forbidden values - Dependence Dependence on other parameters does not exist. the change is implemented within 10 minutes. If however the SGSN releases the RAB before the timer expires in 100 DN0948854 Issue: 03H . 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. Issue: 03H DN0948854 101 . Default value(s) 0H Allowed values 0H-FF00H Forbidden values - Dependence Dependence on other parameters does not exist. PRFILE Descriptions PRFILE and FIFILE parameter descriptions the RNC. the change is implemented within 10 minutes. The maximum supported time is 2000 ms. it is counted as a normal PS RAB release.0 onwards mcRNC. After the parameter value has been changed. from RN7. 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.0 onwards Flexi Direct RNC. Default value zero means that guard timer of 1000 ms is used. The unit of the parameter is milliseconds.1. Applicable controllers IPA-RNC. Feature - 2. any higher value is interpreted as 2000 ms.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. from ADA5. from mcRNC3.89 Parameter 002:2101 RU40_MAINT_05 Descriptive name Control of Automatic Access Class Restriction information sending in SIB3. For more information on the feature see RAN2480: Automatic Access Class Restriction in RU40 Feature Descriptions and Instructions. 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.0 onwards Modifiable YES 102 DN0948854 Issue: 03H . the change is implemented within 10 minutes.90 Parameter 002:2102 RU40_MAINT_06 Descriptive name The algorithm for logical channel ID and DDI allocation Applicable controllers IPA-RNC. Feature - 2. from RN7. from ADA5.1. Value of 1 means that the CS domain specific access class restriction list is excluded from SIB3 with RNC overload triggered AACR.0 onwards mcRNC. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 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. from mcRNC3. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist.0 onwards Flexi Direct RNC. Value of 1 means that the PS domain specific access class restriction list is excluded from SIB3 with RNC overload triggered AACR. After the parameter value has been changed. Value Meaning 0 Workaround is disabled. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Description PRFILE parameter controllable workaround is implemented to NSN RU40 RNC. 1 Workaround is enabled.1. the change is implemented within 10 minutes.0 onwards Flexi Direct RNC. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. After the parameter value has been changed. from mcRNC3.0 onwards mcRNC. from ADA5.91 Parameter 002:2103 RU40_MAINT_07 Descriptive name Dynamic HSUPA BLER Applicable controllers IPA-RNC. from RN7.0 onwards Modifiable YES Issue: 03H DN0948854 103 . 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. Feature - 2. 0 1.92 Parameter 002:2105 RU40_MAINT_09 Descriptive name IFHO/ISHO can fail due to incorrect UE behavior Applicable controllers IPA-RNC. • • Value of 1st Bit of PRFILE parameter controls whether the dynamic power offset algorithm affects the Dynamic HSUPA BLER functionality. for more information see RAN2302: Dynamic HSUPA BLER in RU40 Feature Descriptions and Instructions. 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'. 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). Feature RAN2302: Dynamic HSUPA BLER 2. Value of 2nd Bit to 7th Bit indicates threshold for number of HSUPA users in the cell in the Dynamic HSUPA BLER functionality. 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. from RN7. the change is implemented within 10 minutes.1. Otherwise. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description This PRFILE parameter is used to control used BLER values of continuous BLER state of 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. Default value(s) 0H Allowed values 0H-FFH Forbidden values - Dependence Dependence on other parameters does not exist. Dynamic HSUPA algorithm BLER parameters are used.0onwards 104 DN0948854 Issue: 03H . After the parameter value has been changed. calls cannot be handed over to another frequency or RAT. 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. For older UEs measurement is always released and it is ensured (by Layer 3) that state transition will not be cancelled. In case this kind of problems are detected in a live network.By default. new functionality is disabled. 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. from mcRNC3. measurement related compressed mode information is also cleared from RNC and BTS. 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. The problem is visible to end user so that if compressed mode and new inter-frequency/inter-system measurement cannot be started. 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. Also UE release is not taken into account when deciding if state transition to CELL_FACH state can be cancelled or not. it is recommended to enable workaround. ongoing inter-frequency/intersystem measurement is always released when CELL_FACH state transition is indicated. 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.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. When state transition is completed. Value 1 means that for UEs equal or older than Rel6. However. When state transition from CELL_DCH to CELL_FACH needs to be made. This workaround functionality is controlled by PRFILE parameter 002:2105 RU40_MAINT_09. Default value(s) 0H Allowed values 0H/1H Issue: 03H DN0948854 105 . PRFILE Descriptions PRFILE and FIFILE parameter descriptions mcRNC. from ADA5.0 onwards Flexi Direct RNC. Also for such UEs CELL_FACH state transition is not cancelled if compressed mode is ongoing. These checks were made in the admission control phase. Feature - 2.0 onwards Flexi Direct RNC.0 onwards mcRNC. from mcRNC3.0 1. The RNC does not allow more HSDPA users than indicated within those limits. Value 1 means that LCG and BTS specific HSDPA user amount check against limits sent by BTS is not active. and HSDPA capacity received from the BTS (cell- and HSDPA scheduler-specific limits for HSDPA user and HS-DSCH MAC-d flow amounts).1. Value 0 means that LCG and BTS specific HSDPA user amount check against limits sent by BTS is active. Default value(s) 0H Allowed values 0H/1H 106 DN0948854 Issue: 03H . 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. Radio Network parameters. The new functionality allows the BTS to indicate also its maximum LCG- and BTSspecific HSDPA user amounts to the RNC. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Forbidden values Dependence Dependence on other parameters does not exist. Originally.93 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 Applicable controllers IPA-RNC. RNC limited the HSDPA user amount depending on the HSDPA capacity features used. from RN7. If the value of the PRFILE parameter is 0 (default value).0 1. That can be visible to operator as increase of the counter M1004C168 (SHO BRANCH SETUP FAIL DUE TO IUR). If the value of the PRFILE parameter is 1. from ADA5. SRNC limits the number of RLs in RNSAP: RADIO LINK SETUP/ADDITION REQUEST message to one RL.94 Parameter 002:2109 RU40_MAINT_13 Descriptive name Control for maximum number of RLs in RNSAP Radio Link Setup/Addition procedure Applicable controllers IPA-RNC. SRNC and DRNC do not limit the number of RLs. 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. The maximum length of the SCCP message is 16 segments (16 * 255 = 4080 bytes) in RU40. from RN7. and thus eliminate too long RNSAP: RADIO LINK SETUP/ADDITION RESPONSE messages. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values - Dependence Dependence on other parameters does not exist.0 2. If the maximum length of RANAP Radio Link SETUP/ADDITION RESPONSE message is reached due to high number of neighboring cells (for example.0 onwards Flexi Direct RNC. when multiple RLs are used for DRNC). Feature RAN2124: HSPA 128 Users per Cell 2. Issue: 03H DN0948854 107 . from mcRNC3.0 1. If the number of neighboring cells is high and two RLs are required in DRNC.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. 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. and DRNC limits the number of RLs in RNSAP: RADIO LINK SETUP/ADDITION RESPONSE message to one RL.0 onwards mcRNC. it can cause problems in RL setup over Iur interface. 2109. from mcRNC3. The activation status of the PRFILE parameter can be checked with the following MML command: ZWOI:2.2109. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 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. Default value 0 means that SRNC and DRNC do not limit the number of RLs in the RNSAP Radio Link Setup/Addition procedure.1. 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).0 1. Default value(s) 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist.95 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.1. 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. Feature - 2.0 onwards Flexi Direct RNC. G is the number of GSM neighbour cells. from ADA5. Y is the number of intra- and inter-frequency neighbour cells whose CRNC is other that the DRNC in question.0. 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. from RN7.0 onwards mcRNC.0 1.2109.0 onwards 108 DN0948854 Issue: 03H .0 2. • • Value 0 of the 1st bit of the parameter means that the functionality is off.46. Value of the 1st bit of the parameter controls the activation/deactivation of correction to set Bursty BLER target value. Threshold value can be set from 0 to 127. The default value of PRFILE parameter RU40_MAINT_14 (002:2110) is 0. configure the parameter value to 46H using the following MML: ZWOC: 2. 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 . 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. If the threshold is exceeded. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 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. configure the parameter to value 47H using the following MML: ZWOC: 2. 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. There is no special handling for configuring Bursty BLER target value.47. Value of 2nd to 8th bit of the parameter defines the threshold value for the number of HSUPA UEs in a cell. then values of Continuous BLER state parameters are configured for bursty BLER state-related information elements signalled to u-plane.2110. 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. The recommended value for the PRFILE parameter RU40_MAINT_14 (002:2110) is 47H. Default value(s) 0H Allowed values 0H-0FF00H Forbidden values - Issue: 03H DN0948854 109 . which means there is no special handling for configuring Bursty BLER target value.2110. from mcRNC3. Feature - 2.1.0 3. for example.0 2. The measurement result of the source cell is used in the decision criteria in the target cell for the following functionalities: • • • 110 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 DN0948854 Issue: 03H .0 onwards Flexi Direct RNC. 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 1.0 onwards 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.0 1. In case of bands I (2100 MHz) and VIII (900 MHz).96 Parameter 002:2111 RU40_MAINT_15 Descriptive name Scaling of RSCP measurement result in blind IFHO between frequency bands Applicable controllers IPA-RNC. from ADA5. 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 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.0 onwards mcRNC. the difference is about 7 dB. from RN7. If the value of the PRFILE parameter is 0 (default value). PRFILE and FIFILE parameter descriptions PRFILE Descriptions Dependence Dependence on other parameters does not exist. Feature RAN2172: Multi-Band Load Balancing 2. Activation/Deactivation The activation status of the PRFILE parameter is checked with the following MML command: ZWOI:2.0 onwards Issue: 03H DN0948854 111 . Default value(s) QX: 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist.1. from mcRNC3. providing better control for the above mentioned functionalities in blind IFHO between frequency bands.0 3.2111.0 onwards Flexi Direct RNC. from ADA5. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Scaling of RSCP measurement result improves the accuracy of CPICH RSCP value.0 onwards mcRNC. SF8.0. and all inferior SFs Support Indicators in Cell Capability Container when cell supports HSUPA Applicable controllers IPA-RNC.2111.0 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.1.97 Parameter 002:2113 RU40_MAINT_17 Descriptive name DRNC handling of E-DCH SF4.2111. from RN7.0 1. 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. If the 002:2113 RU40_MAINT_17 PRFILE parameter is activated (value 1). SF8 and all inferior SF Support Indicators to value 1 (“Supported”) in the Cell Capability Container.2113. DRNC sets the SF4. 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. 1: When Cell supports HSUPA. The PRFILE parameter is required to control the use of the eleventh and twelfth bits of the Cell Capability Container.2113. Status check/Activation/Deactivation The activation status of the PRFILE parameter can be checked with the following MML command: ZWOI:2. Allowed values: 0: DRNC does not set the E-DCH SF4. and DRNC sets the Cell Capability Container E-DCH Support Indicator “Supported”. 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. Default value(s) QX 0H Allowed values 0H-0FF00H 112 DN0948854 Issue: 03H .0. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 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. legacy handling for setting the E-DCH SF SI’s is used (11th and 12th bits are set to 0). 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”.2113. SF8 and all inferior SF Support Indicators.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. If the 002:2113 RU40_MAINT_17 PRFILE parameter is not activated (value 0). 0 2. it is critical to secure DL signaling data (SRB) with F-DPCH.0 1.0 onwards Flexi Direct RNC. Currently.1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values - Dependence Dependence on other parameters does not exist. Feature - 2. This can cause essential delay in RRC messages sent in DL over the HS-DSCH. Degradation of MAC HS efficiency KPIs is also observed when either or both of the following functionalities are used: • Issue: 03H Dynamic HSUPA Power Offsets feature or/and DN0948854 113 . The amplitude ratio of HS-DPCCH is relative to the amplitude ratio of DPCCH when ACK/NACK is sent on HS-DPCCH. from mcRNC3. When BTS is not able to decode information. Call drops are the result of failing Serving Cell Change (SCC). as there is only one branch where the DL SRB information is signaled to UE.0 onwards Modifiable YES Description This change is needed to prevent call drops with F-DPCH due to SCC failures. Therefore.1 onwards mcRNC. from ADA5. from RN7. 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. To obtain better SCC success rate with F-DPCH configuration.98 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. 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. it makes blind repetition to UE. The reason for the drops has been challenging air condition for fast mobility UEs. UEs in soft HO state have had problems with F-PDCH that led to the drop of the calls. HS-DPCCH ACK power offset and NACK power offset. 24/15 or 30/15.2115. It means that the existing values are used with E-DCH based on Soft HO state of the UE. 19/15. • • • • 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 g The value defined by the PRFILE parameter is used regardless of soft handover state (soft HO or non-soft HO). based on Soft HO state of the UE. the lower DPCCH power is used. 6H. Default value(s) 0H Allowed values 0H.0.7. it may happen that BTS has problems in decoding information correctly. the ACK and NACK power offsets are read from the PRFILE. a PRFILE controllable solution has been introduced to enable to set the ACK and NACK power offsets to the following values: 15/15. The new function can be activated by setting PRFILE parameter within the range with the following MML command (for example. The default value of the parameter is ‘0’. 7H. The new functionality can be deactivated by changing PRFILE parameter back to the default value: 0H with the following MML command: ZWOC:2. g It is recommended to use value 24/15 regardless of Soft HO state by setting the PRFILE parameter to value 7H. or when the high BLER condition is effective. In both cases. where the new functionality is disabled. When the PRFILE parameter is configured within the range from 0x05H to 0x08 and EDCH is present. to the recommended value: 7H): ZWOC:2. 8H 114 DN0948854 Issue: 03H . 5H. the existing values are used. when low bit rate optimized HSUPA POs are used. if UE is located on the edge of cell. PRFILE and FIFILE parameter descriptions • PRFILE Descriptions Dynamic HSUPA BLER feature This is because both features are meant to decrease the interference level to achieve more room for data transmission.2115. This is done using the 002:2115 RU40_MAINT_19 PRFILE parameter. When the PRFILE parameter has value out of the 0x05H to 0x08 range and E-DCH is present. Status check/Activation/Deactivation The activation status of the PRFILE parameter can be checked with the following MML command: ZWOI:2. In such a situation.2115. To avoid unnecessary stuck/retransmission of DL data in BTS over HS-DSCH. 0 onwards mcRNC. 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).1.0 onwards Flexi Direct RNC. It is information that is signaled only towards BTS within NBAP: ‘E-DCH Maximum Bitrate’ IE.0 3. 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. Feature - 2. 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.0 1. Thus.99 Parameter 002:2117 RU40_MAINT_21 Descriptive name PRFILE control for setting Maximum E-DCH Bit Rate signaled towards BTS Applicable controllers IPA-RNC. especially when the used RAB maximum bit rate values differed from each other. 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). Fast variation of E-TFCI causes high BLER rate with the highest size of Transport Blocks (TB). from ADA5. from mcRNC3.0 onwards Modifiable YES 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). a new EDCH maximum bit rate calculation is applied to HSUPA 2 ms connections using maximum uplink total symbol rate 2*SF2 +2*SF4.0 2. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values - Dependence Dependence on other parameters does not exist. Issue: 03H DN0948854 115 . If the 002:2117 RU40_MAINT_21 PRFILE PRFILE parameter value is 0 (the default value). A better average throughput of the call can be therefore achieved with the stable use of E-TFCIs. from RN7. the new value becomes effective within 10 minutes. 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 1 . 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). In mcRNC or FD-RNC use the following SCLI command: show app-parameter configuration-parameter class 2 number 2117 g 116 After the parameter value has been changed. . 002:2117 RU40_MAINT_21 PRFILE parameter bits from 1st bit to 5th bit are used to define multiplier (PRFILEMultiplier) for E-DCHMaxBitRate calculation introduced above. xxxx xxxx xxx1 1111 31 It means that the range defined for E-DCH with 2*SF2+2*SF4 and E-TTI=2 ms but without 16QAM configuration is from 2700 kbps up to 5700 kbps in 100 kbps steps.. Default value 0 means that the existing way is used to define E-DCH maximum bit rate and the equation above is not used..2117.. xxxx xxxx xxx1 1111 1F 31 The value defined by the 002:2117 RU40_MAINT_21 PRFILE parameter with bits from 1st bit to 5th 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. .. the recommended/optimal value for E-DCH maximum bit rate is 5000 kbps. PRFILE and FIFILE parameter descriptions PRFILE Descriptions If the value defined by the 002:2117 RU40_MAINT_21 PRFILE parameter with bits from 1st bit to 5th bit is different than 0. Based on the field tests. 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..... . Other values than 0 are used as such in the equation in the following manner: g Binary Hex Decimal xxxx xxxx xxx0 0001 1 1 xxxx xxxx xxx0 0010 2 2 xxxx xxxx xxx0 0011 3 3 .. then E-DCH maximum bit rate is calculated and signaled to BTS in the following manner: EDCHMaxBitRate = 2600 kbps + 100 kbps * PRFILEMultiplier.. DN0948854 Issue: 03H . 2117. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 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.100 Parameter 002:2119 RU40_MAINT_23 Descriptive name No recovery mechanism in RNC for voice quality problem caused by ciphering desynchronization Applicable controllers IPA-RNC: RN7.2117.1.0 onwards FD-RNC: I-Ada5.0 onwards mcRNC: mcRNC3. In IPA-RNC use the following MML command: ZWOC:2. Feature - 2.18. 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 Forbidden values - Dependence Dependence on other parameters does not exist.0 onwards Issue: 03H DN0948854 117 .0 3.0 5.0 1.0. 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. If handover complete message is not received within this time. If the UL message arrives too late in the UTRAN. When IFHO command is sent. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Modifiable YES Description If there is a procedure requiring TM RLC ciphering reconfiguration.0. then UTRAN needs to apply the activation time and START value received from the UE in the UL response message. then it can happen that UTRAN applies the new ciphering too late while UE has already incremented the HFN. a 3 second timer is started. Interrogate activation status To interrogate the current value of this parameter: • • In IPA-RNC use MML command: ZWOI:2. during which the ciphering is re-initialized again. voice call re-establishment is performed with ciphering re-initialized for TM RLCs. the PRFILE parameter value should be changed back to default value 0H. Although it is visible in the NW logs that ciphering would have gone out of sync in the scenario. • • In IPA-RNC use MML command: ZWOC:2. then it is assumed that cipher activation time came too late and local state change is made. In mcRNC or FD-RNC use sCLI command: set app-parameter configuration-parameter class 2 number 2119 value 0x 0 Default value(s) 0H Allowed values 0H-3H 118 DN0948854 Issue: 03H .2119. RNC removes the new Radio Links and waits for Cell Update from UE to perform call re-establishment. When UE sends CU. Thus.2119. In mcRNC or FD-RNC use sCLI command: show app-parameter configuration-parameter class 2 number 2119 Activation To activate this change. An improvement has been made in the RNC to recover garbled voice call if it happens due to ciphering out of sync during IFHO procedure. In mcRNC or FD-RNC use sCLI command: set app-parameter configuration-parameter class 2 number 2119 value 0x3 Deactivation To deactivate this change. there is no recovery mechanism in the RNC for this resulting garbled voice call during the RRC connection until the end user disconnects the call or there is another procedure requiring ciphering reconfiguration. PRFILE parameter value should be changed to 3H: • • In IPA-RNC use MML command: ZWOC:2.3.2119. 0 onwards FD-RNC: I-Ada6.0 3. the new value becomes effective within 10 minutes. see TS-RNC-SW-149 (section 5. Activation Issue: 03H DN0948854 119 . Interrogate activation status To interrogate the current value of this parameter: • • g In IPA-RNC use MML command: ZWOI:2.2121. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values - Dependence Dependence on other parameters does not exist.0 Modifiable YES Description If Enhanced Cell_FACH features are enabled and direct transition from Cell_DCH to Cell_PCH is performed for the legacy commercial devices supporting E-FACH. then UE goes into signaling loop when later it wants to move to Cell_FACH from Cell_PCH state.18). Feature - 2. This causes degradation in the Cell_PCH to E-FACH state transition KPIs. It should be set to value 3 to activate the workaround. PRFILE controllable workaround has been made behind the 002:2121 RU40_MAINT_25 PRFILE parameter. The workaround is made for Rel7 and Rel8 commercial devices supporting E-RACH/EFACH that those UEs are always moved to Cell_FACH from Cell_DCH after NW or UE detected inactivity. In mcRNC or FD-RNC use sCLI command: show app-parameter configuration-parameter class 2 number 2121 After the parameter value has been changed.0 onwards mcRNC: mcRNC3.0 4. as well as the list of possible values.1.101 Parameter 002:2121 RU40_MAINT_25 Descriptive name UE problem with HS-FACH with feature RAN1913: High Speed Cell_FACH Applicable controllers IPA-RNC: RN7. For further instructions. Feature RAN1913: High Speed Cell_FACH 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions To activate this change.102 Parameter 002:2122 RU40_MAINT_26 Descriptive name PRFILE controlled additional conditions for PrxNoise auto tuning triggering and updating of R99 power related counters Applicable controllers IPA-RNC: RN7.2121. it is checked that the cell and other cells in the same frequency layer in the BTS are empty.0 3.0 onwards Modifiable YES Description Before PrxNoise auto tuning can trigger and adjust the current PrxNoise value.2121. • • In IPA-RNC use MML command: ZWOC:2.0 onwards FD-RNC: I-Ada6. Currently used conditions to check cell empty condition in UL includes only checking of 120 DN0948854 Issue: 03H . the PRFILE parameter value should be changed back to default value 0H.1.0 4. • • In IPA-RNC use MML command: ZWOC:2.3. In mcRNC or FD-RNC use sCLI command: set app-parameter configuration-parameter class 2 number 2121 value 0x0 Default value(s) 0H Allowed values 0H-03H Forbidden values - Dependence Dependence on other parameters does not exist. PRFILE parameter value should be changed to 3H.0 onwards mcRNC: mcRNC3.0. In mcRNC or FD-RNC use sCLI command: set app-parameter configuration-parameter class 2 number 2121 value 0x3 Deactivation To deactivate this change. In mcRNC or FD-RNC use sCLI command: set app-parameter configuration-parameter class 2 number 2122 value 0 Deactivation Setting back the legacy functionality can be done by setting “1st bit to 1” for the 002:2122 RU40_MAINT_26 PRFILE parameter: • • In IPA-RNC use MML command: ZWOC:2.0. Interrogate activation status To interrogate the current value of this parameter: • • g In IPA-RNC use MML command: ZWOI:2. EDCH usage in common channels can trigger the PrxNoise auto tuning functionality causing unwanted variation for the PrxNoise level. also the cell specific EDCH LF reported by the BTS must be zero. In mcRNC or FD-RNC use sCLI command: set app-parameter configuration-parameter class 2 number 2122 value 1 Default value(s) 0H Issue: 03H DN0948854 121 . When the HS-RACH feature is used. the updating the following R99 power related counters now requires the same empty cell condition: • • • M1000C0 AVE_PRXTOT_CLASS_0 M1000C34 AVE_LNRT_CLASS_0 M1000C24 AVE_LRT_CLASS_0 The recommended value to be used for 002:2122 RU40_MAINT_26 1st bit is 0. Before PrxNoise auto tuning can trigger in a cell. new extended conditions to define the cell to be empty is used.1. 2122. indicating that there are no EDCH transmission in the cell. In mcRNC or FD-RNC use sCLI command: show app-parameter configuration-parameter class 2 number 2122 After the parameter value has been changed. 2122. the new value becomes effective within 10 minutes. This is used in parallel with the current conditions. 2122. but not any checking of common channel usage. it can cause high RTWP values in a cell even with low number of UEs using the high speed common channel. PRFILE Descriptions PRFILE and FIFILE parameter descriptions UE allocation (DCH or E-DCH) in CELL_DCH state or checking if load factor (LF) thresholds are exceeded. which is active by default. To avoid the triggering of PrxNoise noise auto tuning in a cell due to usage of HS-RACH. Activation The recommended value setting “1st bit to 0” for the 002:2122 RU40_MAINT_26 parameter is performed as follows: • • In IPA-RNC use MML command: ZWOC:2. This check is valid only in case when the RNP parameter HSRACHEnabled is set to enabled state and the PRfile parameter 002:2122 RU40_MAINT_26 1st bit is set to 0. Similarly to the change of the PrxNoise auto tuning functionality. 3. section 10. for example.1 Parameter 007:0174 CN_INFORMATION_INFO Descriptive name CN Information Info information element for CELL/URA UPDATE CONFIRM Applicable controllers IPA-RNC.2. 2. For more information on IEs. mcRNC. for HomeZone feature purposes. 122 DN0948854 Issue: 03H . see 3GPP TS 25.2 Parameter class 007 CALL_CONTROL Descriptive Name Call control Description This class includes call control definitions. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Allowed values 0H-01H Forbidden values - Dependence Dependence on other parameters does not exist.1.331. 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. Feature RAN1913: High Speed Cell_FACH 2. With this parameter the operator can define if this information element is always included in those messages. The operator can use this parameter.3. If the parameter is in position T (True). This is the usual case. xttt xxx1 The RNC/RRC never moves NEC-VTX-UE to Cell_FACH-state. If the parameter is in position F (False). Flexi Direct RNC Modifiable YES Description A non-zero value of this parameter affects the RRC signaling between RNC and UE. the RNC moves it directly to Idle state (DCH->Idle). Issue: 03H Value Meaning 0000 0000 No special handling for a UE. mcRNC. Default value(s) QX: 0 (F) Allowed values 1 (T)/0 (F) Forbidden values Dependence Dependence on other parameters does not exist. By individual bits and bit string (ttt) you can get special handling for a UE in order to cope (also) with early UEs. the CN Information Info IE is included only during the SRNS relocation (UE not involved).2. DN0948854 123 . Instead. Feature - 2. the CN Information Info IE is always included in the CELL/URA UPDATE CONFIRM message. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning T. F.2 Parameter 007:0191 JAPAN_UE_CONTROL Descriptive name Special control due to early UEs Applicable controllers IPA-RNC. Thus. 0000 xxxx = 00H0FH Tx interruption after trigger = Pending time after trigger. 0-6. it is independent of Pending time after trigger.e.0 onwards: the branch addition can be handled in a different way and the operator can define which method is used. This is due to NEC-VTB-UE behavior. the branch addition is handled immediately. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning xttt xx1x The RNC/RRC sends ActivationTime to all UEs in PS 0/0 RB setup. 1000 xxxx = 80H8FH ttt=0 -> RNC/RRC never sends Tx interruption after trigger to UE.2. This is the usual case. Method 1: as earlier. 124 DN0948854 Issue: 03H . Flexi Direct RNC Modifiable YES Description A new functionality which can be activated by the PRFILE from RN2. also during the CM start. Default value(s) QX: 00000000B Allowed values 00000000B - 11111111B Forbidden values Dependence Dependence on other parameters does not exist.3 Parameter 007:0195 RN21_MAINT_003 Descriptive name SHO Branch addition during CM starting phase Applicable controllers IPA-RNC. mcRNC.1 CD2. Feature - 2. 1ttt xxxx = 90HFFH ttt=1-7 -> Tx interruption after trigger index is ttt-1 i. Parameter needs to be set to value 1. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 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 0. For more details and activation instructions. When the CM starting timer expires. the branch addition is handled. Parameter needs to be set to value 2. Feature Activation Manual.2 which is improved/changed from RN3. To deactivate the change.2. Default value(s) QX: 0H Allowed values 0H - 2H Forbidden values Dependence Dependence on other parameters does not exist.4 Parameter 007:0208 RNC_MAINT_001 Descriptive name Cell Recovery Improvement Applicable controllers IPA-RNC.0 onwards with features RAN1810: Sleeping Cell Improvement and RAN1823: Recovery Logging Improvement. Feature - 2. Method 3: the branch addition is saved during the CM start. see Features RAN1302. mcRNC Modifiable YES Description A new feature in RN2.0 CD3. RAN1810 and RAN1823: Non-Performing Cell Recovery. Default value(s) QX: 0H Allowed values 0H - 0FF00H Issue: 03H DN0948854 125 . Feature Activation Manual. overlapping GSM frequencies and missing ADJG definitions. that is. RAN1810 and RAN1823: Non-Performing Cell Recovery. 126 DN0948854 Issue: 03H . see Features RAN1302. Default value(s) QX: 0H Allowed values 0H / 1H Forbidden values Dependence Dependence on other parameters does not exist. where BSIC is always verified also in case of PS NRT calls. so the implementation is configurable with a PRFILE parameter. That is against the current RNC specifications. mcRNC Modifiable YES Description From RN3.1 onwards. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Forbidden values Dependence For dependencies on other parameters.2.5 Parameter 007:0238 RN30_MAINT_015 Descriptive name BSIC verification in case of PS NRT calls Applicable controllers IPA-RNC. where the inter-system adjacencies are better defined. RAN1823: Recovery Logging Improvement) 2.0 ED2. 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. a new functionality is added to solve possible problems with PS ISHO due to the GSM radio network planning. Feature RAN1302: Non-Performing Cell Recovery (RAN1810: Sleeping Cell Improvement. This problem can be also avoided with a new RNC implementation. mcRNC Modifiable YES Description This change refers to two new features: RAN1810: Sleeping Cell Improvement and RAN1823: Recovery Logging Improvement.2.2. RAN1810: Sleeping Cell Improvement. Feature Activation Manual.0 onwards. For more details and activation instructions. Feature Activation Manual. These features can be considered as improvements to RAS05. Feature RAN1302: Non-Performing Cell Recovery. see Features RAN1302. RAN1823: Recovery Logging Improvement 2.0 CD3. RAN1810 and RAN1823: Non-Performing Cell Recovery. see Features RAN1302.6 Parameter 007:0239 RN30_MAINT_016 Descriptive name Non-performing cell recovery improvement Applicable controllers IPA-RNC.7 Parameter 007:0240 RN30_MAINT_017 Descriptive name Non-performing cell recovery improvement Issue: 03H DN0948854 127 . Default value(s) QX: 0H Allowed values 0H - 0FF00H Forbidden values Dependence For dependencies on other parameters.1 ED feature - RAN1302: Non-Performing Cell Recovery. RAN1810 and RAN1823: Non-Performing Cell Recovery. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Feature - 2. The features can be activated from RN3. see Features RAN1302. Feature Activation Manual.1 ED feature - RAN1302: Non-Performing Cell Recovery.2. RAN1810 and RAN1823: Non-Performing Cell Recovery. The features can be activated from RN3. These features can be considered as improvements to RAS05. Feature RAN1302: Non-Performing Cell Recovery. Flexi Direct RNC Modifiable YES 128 DN0948854 Issue: 03H .0 CD3. Feature Activation Manual. RAN1823: Recovery Logging Improvement 2. RAN1810 and RAN1823: Non-Performing Cell Recovery.0 onwards. mcRNC. RAN1810: Sleeping Cell Improvement. mcRNC. Default value(s) QX: 0H Allowed values 0H - 0FF00H Forbidden values Dependence For dependencies on other parameters. For more details and activation instructions. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Applicable controllers IPA-RNC.8 Parameter 007:0241 RN30_MAINT_018 Descriptive name Non-performing cell recovery improvement Applicable controllers IPA-RNC. Flexi Direct RNC Modifiable YES Description This change refers to two new features: RAN1810: Sleeping Cell Improvement and RAN1823: Recovery Logging Improvement. see Features RAN1302. see Features RAN1302.1 ED feature - RAN1302: Non-Performing Cell Recovery. RAN1810 and RAN1823: Non-Performing Cell Recovery. mcRNC Modifiable YES Description This change refers to two new features: RAN1810: Sleeping Cell Improvement and RAN1823: Recovery Logging Improvement.9 Parameter 007:0242 RN30_MAINT_019 Descriptive name Non-performing cell recovery improvement Applicable controllers IPA-RNC. RAN1810 and RAN1823: Non-Performing Cell Recovery. Feature Activation Manual. RAN1810 and RAN1823: Non-Performing Cell Recovery. The features can be activated from RN3. These features can be considered as improvements to RAS05.0 CD3. see Features RAN1302. Feature RAN1302: Non-Performing Cell Recovery. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Description This change refers to two new features: RAN1810: Sleeping Cell Improvement and RAN1823: Recovery Logging Improvement. Feature Activation Manual. These features can be considered as improvements to RAS05.2. For more details and activation instructions. RAN1810: Sleeping Cell Improvement.0 CD3. RAN1823: Recovery Logging Improvement 2. The features can be activated from RN3. Feature Activation Manual.1 ED feature - RAN1302: Non-Performing Cell Recovery.0 onwards. For more details and activation instructions. Default value(s) QX: 0H Allowed values 0H - 0FF00H Forbidden values Dependence For dependencies on other parameters.0 onwards. see Features RAN1302. Issue: 03H DN0948854 129 . 0 CD3. For more details and activation instructions.10 Parameter 007:0243 RN30_MAINT_020 Descriptive name Non-performing cell recovery improvement Applicable controllers IPA-RNC. see Features RAN1302. RAN1810: Sleeping Cell Improvement. Default value(s) QX: 0H Allowed values 0H - 0FF00H 130 DN0948854 Issue: 03H . Feature RAN1302: Non-Performing Cell Recovery. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Default value(s) QX: 0H Allowed values 0H - 0FF00H Forbidden values Dependence For dependencies on other parameters. RAN1810 and RAN1823: Non-Performing Cell Recovery. Feature Activation Manual. see Features RAN1302. RAN1823: Recovery Logging Improvement 2. RAN1810 and RAN1823: Non-Performing Cell Recovery. The features can be activated from RN3.0 onwards. Feature Activation Manual. Flexi Direct RNC Modifiable YES Description This change refers to two new features: RAN1810: Sleeping Cell Improvement and RAN1823: Recovery Logging Improvement. mcRNC.1 ED feature - RAN1302: Non-Performing Cell Recovery. These features can be considered as improvements to RAS05.2. requires that RNC makes load sharing routing for ImsiPageResponse message in case CN is not known. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values Dependence For dependencies on other parameters. Instead. If that parameter is activated. when Femto wants to reset UE and move it to the WCDMA. then all Global RNC Ids which are sent to CN include the Common PLMN Id as the PLMN Id. CTP request for other PLMN Issue: 03H DN0948854 131 . mcRNC. All other vendors’ Core Networks cannot manage MOCN if the RNC uses the CN's own PLMN id in the Global RNC id. Flexi Direct RNC Modifiable YES Description MOCN improvement Correction for RAN966: Multi-Operator Core Network compatibility with other vendors Core Networks. when Paging message itself was not sent via RNC. see Features RAN1302. the UE request will be rejected. RNC support for Femto based UE resetting With this functionality. A new functionality is added to improve the compatibility with other vendors’ Core Networks.0 CD1. if UE sends attach request inside ImsiPagingResponse message. the RNC does not have that temporary data. Support to this Femto based UE resetting. it waits for MOCN RNC to always use the Common PLMN id in the RNC Id.11 Parameter 007:0269 RN40_MAINT_001 Descriptive name MOCN improvements Applicable controllers IPA-RNC. Feature RAN1302: Non-Performing Cell Recovery. Also. RAN1823: Recovery Logging Improvement 2. As a result. This functionality can be activated from RN4. the RNC cannot forward the request to any CN.2. Feature Activation Manual. RAN1810 and RAN1823: Non-Performing Cell Recovery. RAN1810: Sleeping Cell Improvement.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. mcRNC. With this functionality. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Some UE models sends invalid selected PLMN to the RNC in MOCN configuration. Value Meaning 0 Both fuctionalities are not active. Default value(s) QX: 0H Allowed values 0H / 201H / 2001H / 2201H Forbidden values - Dependence Dependence on other parameters does not exist. 201H Ignore received Initial UE message when UE selects PLMN ID which was not available under this RNC/Cell. 2001H MOCN / IuFlex improvement and the RNC support for Femto based UE (to manage paging responses handling when UE respond by IMSI).Default functionality is to ignore only that selected PLMN and continue routing as that selected PLMN not received. Wrong selected PLMN info will be ignored and by default UE request will be handled as like non-supported UE (No Selected PLMN).12 Parameter 007:0270 RN40_MAINT_002 Descriptive name MOCN improvement Applicable controllers IPA-RNC. 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. Feature RAN966: Multi-Operator Core Network 2.2. Flexi Direct RNC Modifiable YES 132 DN0948854 Issue: 03H . 2201H Both functionalities are active. then the ICSU computer log is written. causes an overload when there is enough capacity allocation.13 Parameter 007:0279 RN40_MAINT_009 Descriptive name BTS power measurement improvement Applicable controllers IPA-RNC. From RN4. Default value(s) QX: 0H Allowed values 0H-0FF00H Forbidden values - Dependence See Activating RAN966: Multi-Operator Core Network. Sometimes the WBTS reports constantly show the nonHDSPAPtx power as zero. it is rejected. a supervision has been added: if the WBTS reports show the nonHSDPAtx power as zero for 5 minutes. then it is converted to the initial CPICH value. Additionally. thus. Feature RAN966: Multi-Operator Core Network 2.0 CD1. and if the WBTS reports show the nonHDSPAPtx power as zero. then the zero measurements are not accepted. The more cells the site has. in consequence.0 onwards. a new functionality can be controlled by the PRFILE parameter. When the parameter has a non-zero value. This is considered an invalid measurement value in the RNC.2. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Description Additional configuration parameters for RAN966: Multi-Operator Core Network feature. Flexi Direct RNC Modifiable YES Description A new functionality which prevents problems when the initialization of BTS power measurement fails in certain BTSs. When the parameter value is 0 (default). Issue: 03H DN0948854 133 . mcRNC. This. the higher the probability of failure initialization. Feature - 2.280.0 CD1.14 Parameter 007:0280 RN40_MAINT_010 Descriptive name IP defragmentation support on NPS1(P) Applicable controllers IPA-RNC Modifiable YES Description From RN4. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Default value(s) QX: 0H Allowed values 0H-0FF00H Forbidden values Dependence Dependence on other parameters does not exist. In order to minimize the traffic-break time due to this restart.2. a new functionality is implemented and now NPS1(P) can support a reassemble of the received fragmented IP packets. The fragmentation of IP packets is not supported. NOTE: If it is NPS1P. it is recommended to enable the PRFILE parameter and perform a required reconfiguration before the CD installation. WO and SP states. AAL2 switching and ATM Iu-CS need separate unit(s).1 onwards. the command should be given to the unit in the WO state.<unit index>. Restart the NPS1(P) to load the IP defragmentation support with Iu-PS only function: ZUSU: <unit type NPS1 or NPS1P>. then in both. see TS-RNC-SW-130. Activation of the IP defragmentation support on NPS1(P): • • Use the following MML command: ZWOC:7. For further instructions. 134 DN0948854 Issue: 03H .1. the NPS1P restarts. The NPS1(P) defragmentation requires card(s) to be dedicated to IuPS only. NPS1(P) runs a dedicated SW for IP defragmentation which needs to be activated via a PRFILE parameter. therefore the MTU size in NPS1 IPoAtm interface should be big enough to avoid the fragmentation when sending the traffic. It is used by the outer loop power control of the RNC. Default value(s) QX: 0H Allowed values 0H / 1H Forbidden values - Dependence Dependence on other parameters does not exist. It is highly recommended that the preparations and step 1 are performed before the CD installation. that is. and step 2 is performed as part of CD installation. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Restarting the NPS1P causes a traffic break. The parameter value 20 (014H) means that the RNC utilizes the value - 2.15 Parameter 007:0281 RN40_MAINT_011 Descriptive name Adjustable HSUPA BLER target for PS NRT Applicable controllers IPA-RNC. Flexi Direct RNC Modifiable YES Description The HSUPA L1 BLER target for PS NRT parameter is changed as an operatormodifiable PRFILE parameter from RN4. Feature - 2. The value of the parameter equals the log10 of the BLER value. The parameter value 9 means that the RNC utilizes the value - 0. the system restart.2.0 (1% BLER). mcRNC. Parameter values 21 (015H) and higher mean that the RNC utilizes the default value - 1 (10% BLER). etc.9 (13% BLER). This parameter defines the L1 BLER target for the E-DCH MAC-d flow of the PS NRT service.0 CD1. DN0948854 135 . The parameter value 8 means that the RNC utilizes the value - 0. The parameter has the following alternatives: • • • • • Issue: 03H Parameter values 0…7 mean that the RNC utilizes the default value - 1 (10% BLER).2 onwards.8 (16% BLER). Feature RAN2170: Adjustable HSUPA BLER target for PS NRT 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Default value(s) QX: 0H Allowed values 0H-0FF00H Forbidden values - Dependence Dependence on other parameters does not exist. 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. 136 DN0948854 Issue: 03H .2. mcRNC. possible values and activation instructions. Default value(s) QX: 0H Allowed values 0H-FFH Forbidden values - Dependence Dependence on other parameters does not exist.16 Parameter 007:0283 RN40_MAINT_013 Descriptive name Optimization of the RRM algorithms in RNC Applicable controllers IPA-RNC. Flexi Direct RNC Modifiable YES Description Parameter is used to control the enhancements of the admission control and packet scheduling algorithms in RNC. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Feature - 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. Issue: 03H DN0948854 137 PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning 0 Both workaround are disabled (default value). 1H SIR error to trigger CTS workaround is enabled. 3H 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. 138 DN0948854 Issue: 03H PRFILE Descriptions PRFILE and FIFILE parameter 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. Issue: 03H DN0948854 139 See TS-RNC-SW-136 for a detailed description and activation instructions. Feature - 2.2. See TS-RNC-SW-136 for a detailed description and activation instructions. PRFILE and FIFILE parameter descriptions PRFILE Descriptions When a new parameter set is taken into use. Default value(s) QX: 0H Allowed values 0H-0FF00H 140 DN0948854 Issue: 03H . a change of policing parameters can be controlled via the PRFILE parameter. 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. From RN4. The downside is a slight drop in capacity for other traffic in the uplink (UL) direction. the UL CAC reservation is bigger and the risk for RT traffic packets dropping is removed.3 onwards.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.0 CD1. 2.21 Parameter 007:0290 RN40_MAINT_020 Descriptive name Limitation of new HS-DSCH allocations Applicable controllers IPA-RNC. Flexi Direct RNC Modifiable YES Description From RN4. The maximum time for a single limitation in the HSDPA cell group is set to 10 sec.4 and CD2. when HS-DSCH allocations fails due to the BTS user amount congestion. the RNC limits the new HS-DSCH allocations until some of the existing HS-DSCH allocations are released. Default value(s) QX: 0H Allowed values 0H / 1H Forbidden values - Dependence Dependence on other parameters does not exist. a new functionality is added to the RNC to cope better with situations.0 CD1. Feature - Issue: 03H DN0948854 141 . Limitation of new allocations is performed on the HSDPA cell group level. In this kind of congestion. This functionality is active by default in the RNC.0 onwards. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Forbidden values - Dependence Dependence on other parameters does not exist. Feature - 2. mcRNC. 2. mcRNC.1 dB step).22 Parameter 007:0291 RN40_MAINT_021 Descriptive name Dynamic link optimization Applicable controllers IPA-RNC.0 onwards.5 dB is set (default) 1 - 0.0 CD1. Flexi Direct RNC Modifiable YES Description From RN4. To set own value for Dynamic Link Optimization. Example values: • • • • 0 - 1.4 and CD2.23 Parameter 007:0295 RN40_MAINT_025 Descriptive name AAL2 signaling workaround 142 DN0948854 Issue: 03H . a new functionality is added to the RNC with this parameter.2. 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.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. 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. PRFILE and FIFILE parameter descriptions PRFILE Descriptions 2. If other vendor's MGW is used. Feature - 2.2) onwards. mcRNC. Default value(s) QX: 0H Allowed values 0H-0FF00H Forbidden values - Dependence Dependence on other parameters does not exist. the recommended value is 1 or 2 (otherwise it should be 0).0 CD2. value 2 (= 20 ms) is used. This solution is proposed because of problems with handling of AAL2 signaling sequences (CID release collision) in other vendors' MGWs. It defines how many 10 ms periods the RNC waits after a successful outgoing release request (it causes a certain AAL2 protocols’ waiting time).0 MP0 (and RN4.24 Parameter 007:0296 RN40_MAINT_026 Descriptive name SAB Failure/Restart messages on RNC-initiated CBC connection Applicable controllers IPA-RNC.2. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Applicable controllers IPA-RNC Modifiable YES Description From RN5. When the maximum value (200) is exceeded. a new functionality is added to the RNC with this parameter. Flexi Direct RNC Modifiable YES Issue: 03H DN0948854 143 . PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description From RN5.25 Parameter 007:0297 RN40_MAINT_027 Descriptive name Direct PCH to DCH state transition Applicable controllers IPA-RNC. the RNC sends data on FACH. The value defines the threshold of data (in bytes) in the RLC buffers of SRB3. With this improvement. a new functionality has been added to the RNC with this parameter.0 CD2.0 PP0. Flexi Direct RNC Modifiable YES Description From RN5.1 (and RN4. and all NRT RBs that trigger the downlink traffic volume measurement report (capacity request) on MAC.0 PP0. Feature - 2.0 CD2. when UE is in Cell_FACH state. Values greater than 0 mean that SA3 initiates an IuBC connection attempt towards CBC. SRB4. 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.2) onwards.2) onwards. mcRNC. Values and respective thresholds: • • 144 0H - 128 bytes 8H - 8 bytes DN0948854 Issue: 03H . Default value(s) QX: 0H Allowed values 0H-0FF00H Forbidden values - Dependence Dependence on other parameters does not exist. Otherwise. It means that SA3 does not initiate IuBC connection establishment towards CBC.2. this parameter should be disabled (value = 0).1 (and RN4. 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. a new functionality has been added to the RNC with this parameter. 2. Default value(s) QX: 0H Issue: 03H DN0948854 145 . The T314 timer offset used by the RRC can be set with this parameter. a new functionality is added to the RNC with this parameter.0 MP1 (and RN4. mcRNC. PRFILE Descriptions PRFILE and FIFILE parameter 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. Values from 1 to 60 (0H-3CH) mean that the offset is 1-60 seconds. Flexi Direct RNC Modifiable YES Description From RN5.26 Parameter 007:0299 RN40_MAINT_029 Descriptive name T314 timer offset Applicable controllers IPA-RNC.0 CD2.2) onwards. Any other values (including 0) mean that a four-second offset is used. Feature - 2. the RNC should be restarted to apply change to all the BTSs under the RNC. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Allowed values 0H-0FF00H Forbidden values - Dependence Dependence on other parameters does not exist. mcRNC. In those cases. 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. 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.2.27 Parameter 007:0304 RN40_MAINT_034 Descriptive name NBAP overload control functionality for narrow Iub configurations Applicable controllers IPA-RNC. DN0948854 Issue: 03H . It is recommended to use default NBAP overload control functionality. Other alternative is to perform COCO detach/attach or BTS restart in case parameter value needs to be applied only to certain BTSs. Flexi Direct RNC Modifiable YES Description With this parameter. NBAP overload control functionality can be adjusted if needed. g 146 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. After parameter is changed. Feature - 2. It is possible to select two levels of more aggressive NBAP overload control functionality. Default value(s) See TS-RNC-HW-076 (section 6). 1 Min and start levels of overload control functionality are lower than automatic link capacity detection would set it.28 Parameter 007:0306 RN40_MAINT_036 Descriptive name PS memory supervision Applicable controllers IPA-RNC. see TS-RNC-HW-076 (section 6). 3 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. For possible values and activating instructions. mcRNC Modifiable YES Description This parameter controls the PS memory supervision procedure. Max level is according to link capacity. Issue: 03H DN0948854 147 . Feature - 2.2. Default value(s) QX: 0H Allowed values 0H-3H Forbidden values Dependence Dependence on other parameters does not exist. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning 0 Recommended overload control functionality for recommended Iub transport configurations. For further instructions. Direct State Transfer from Cell_DCH to Cell_PCH 148 DN0948854 Issue: 03H . mcRNC.2.29 Parameter 007:0307 RN40_MAINT_037 Descriptive name This PRFILE parameter is used for three different issues: 1. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Allowed values See TS-RNC-HW-076 (section 6). Disabling of RNC support for lossless PDU size change This parameter is used for disabling RNC support for lossless PDU size change. RNC workarounds for UE problems This parameter is used to handle RNC workarounds for UE problems. 2. Flexi Direct RNC Modifiable YES Description Default and recommended value for this PRFILE parameter is 0H Functionality 6th bit RNC workarounds for UE problems X 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 X X 1. Feature - 2. Disabling of RNC support for lossless PDU size change 3. see TS-RNC-SW-149. as well as the list of possible values. Forbidden values Dependence Dependence on other parameters does not exist. RNC workaround for UE problem 2. see TS-RNC-SW-167. Direct State Transfer from Cell_DCH to Cell_PCH Applicable controllers IPA-RNC. as well as the list of possible values. 3. For further instructions. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2nd lowest bit of this parameter is used to control the use of Direct State Transfer from Cell_DCH to Cell_PCH.2.30 Parameter 007:0308 RN40_MAINT_038 Descriptive name Terminating Low Priority Signaling initiates RT over NRT Applicable controllers IPA-RNC. Feature - 2. This is the recommended value and should not be disabled unless separately discussed with NSN Technical Support. After parameter value has been changed. Default value(s) QX: 0H Dependence Dependence on other parameters does not exist. 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): Issue: 03H Value Meaning 0 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 1 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 149 . new functionality takes effect within 10 minutes. mcRNC. RT-over-NRT can be triggered in resource congestion cases. Value 0 means that Direct State Transfer from Cell_DCH to Cell_PCH is enabled. 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. 31 Parameter 007:0387 RNC_L3_CONTROL_022 Descriptive name This PRFILE parameter is to control the usage of more ADJx per cell.2. Applicable controllers IPA-RNC. Workaround consits of two parts: 150 DN0948854 Issue: 03H . PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning 2 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 3 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. 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). 2. Feature - 2. Alarm 7775 is raised if ADJx are terminated. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Extra ADJx are removed (ADJI and ADJG are removed in round robin order).0 onwards Modifiable YES Issue: 03H DN0948854 151 . Applicable controllers IPA-RNC from RN6.0 1. 2 Functionality is activated. Default value(s) QX: 0H Allowed values 0H/2H Forbidden values - Dependence Dependence on other parameters does not exist.0 2.0 onwards Flexi Direct RNC frm ADA4.32 Parameter 007:0388 RNC_L3_CONTROL_023 Descriptive name HSUPA allocation failures with limited WN7.2 onwards mcRNC from mcRNC2. 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.0 HSUPA baseband HW resources / control the NRT DCH bit rate limitations due to the “BTS baseband hardware congestion”. After activating PRFILE parameter. • • Value (HEX) Meaning 0 Functionality is deactivated.0 1. Value (HEX) Meaning 0 The NRT DCH bit rate limitations are not applied (default value) 1 Limitations for HSDPA uplink DCH return channels are applied.0 onwards Flexi Direct RNC frm ADA4. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description This parameter defines the NRT DCH services .0 onwards 152 DN0948854 Issue: 03H . After parameter value has been changed workaround is activated after 10 minutes.0 1.2. Default value(s) QX: 0H Allowed values 0H-3H Forbidden values - Dependence Dependence on other parameters does not exist.33 Parameter 007:0389 RNC_L3_CONTROL_024 Descriptive name HSUPA allocation failures with limited WN7. which bitrates are limited due to BTS baseband HW congestion algorithm (HSUPA_CONG_ALG).0 1. For more information see see TS-RNC-SW-189.2 onwards mcRNC from mcRNC2.0 HSUPA baseband HW resources / control the initial bit rate limitation threshold (INI_THRESH). 2 Limitations for R99 uplink and downlink DCHs are applied.0 2. Feature - 2. Applicable controllers IPA-RNC from RN6. 3 Both limitations are applied (recommended value). B INI_THRESH is set to 11. C INI_THRESH is set to 12. See the Parameter 007:0391 RNC_L3_CONTROL_026 for more information on the HSUPA_CONG_ALG algorithm. which is used to trigger the HSUPA_CONG_ALG algorithm. See the Parameter 007:0390 RNC_L3_CONTROL_025 for more information on MIN_THRESH condition. 3 INI_THRESH is set to 3. it triggers the algorithm status to “HW limited”. 9 INI_THRESH is set to 9. D INI_THRESH is set to 13. DN0948854 153 . Issue: 03H Value (HEX) Meaning 0 INI_THRESH is set to 5 (default value). If the averaged value is lower than both INI_THRESH and MIN_THRESH. If the averaged value is equal or higher than the INI_THRESH. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Modifiable YES Description This PRFILE parameter is used to control the initial bit rate limitation threshold (INI_THRESH). 5 INI_THRESH is set to 5. F INI_THRESH is set to 15. E INI_THRESH is set to 14. 6 INI_THRESH is set to 6. the algorithm status is "normal". 1 INI_THRESH is set to 1. MIN_THRESH condition triggering has higher priority that the INI_THRESH condition. A INI_THRESH is set to 10. 7 INI_THRESH is set to 7. 4 INI_THRESH is set to 4. 8 INI_THRESH is set to 8. 2 INI_THRESH is set to 2. 2 onwards mcRNC from mcRNC2. 11 INI_THRESH is set to 17. 14 INI_THRESH is set to 20. 12 INI_THRESH is set to 18.0 onwards Flexi Direct RNC frm ADA4.0 onwards Modifiable YES 154 DN0948854 Issue: 03H .0 1.2. After parameter value has been changed workaround is activated after 10 minutes.0 1. Applicable controllers IPA-RNC from RN6. 13 INI_THRESH is set to 19. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value (HEX) Meaning 10 INI_THRESH is set to 16.0 2. 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.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). See the Parameter 007:0391 RNC_L3_CONTROL_026 for more information on the HSUPA_CONG_ALG algorithm. 1 MIN_THRESH is set to 1. 5 MIN_THRESH is set to 5. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Description This PRFILE parameter is used to control the minimum bit rate limitation threshold (MIN_THRESH). E MIN_THRESH is set to 14. it triggers the algorithm status to “No EDCH capacity”. A MIN_THRESH is set to 10. the algorithm status is "normal". MIN_THRESH condition triggering has higher priority that the INI_THRESH condition. 4 MIN_THRESH is set to 4. B MIN_THRESH is set to 11. 9 MIN_THRESH is set to 9. Issue: 03H Value (HEX) Meaning 0 MIN_THRESH is set to 15 (default value). If the averaged value is lower than both INI_THRESH and MIN_THRESH. 8 MIN_THRESH is set to 8. See the Parameter 007:0389 RNC_L3_CONTROL_024 for more information on INI_THRESH condition. 7 MIN_THRESH is set to 7. C MIN_THRESH is set to 12. D MIN_THRESH is set to 13. 6 MIN_THRESH is set to 6. If the averaged value is equal or higher than the MIN_THRESH. 2 MIN_THRESH is set to 2. 3 MIN_THRESH is set to 3. 10 MIN_THRESH is set to 16. DN0948854 155 . F MIN_THRESH is set to 15. which is used to trigger the HSUPA_CONG_ALG algorithm. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value (HEX) Meaning 11 MIN_THRESH is set to 17.35 Parameter 007:0391 RNC_L3_CONTROL_026 Descriptive name HSUPA allocation failures with limited WN7. Feature - 2.2 onwards mcRNC from mcRNC2. 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. 12 MIN_THRESH is set to 18. 13 MIN_THRESH is set to 19.0 2.2.0 HSUPA baseband HW resources / number of samples used to calculate average reported measurement value. After parameter value has been changed workaround is activated after 10 minutes. 14 MIN_THRESH is set to 20.0 1.0 1.0 onwards Flexi Direct RNC frm ADA4.0 onwards Modifiable YES 156 DN0948854 Issue: 03H . Applicable controllers IPA-RNC from RN6. one sample is collected from each received measurement. Feature - 2. Default value of this PRFILE parameter is 0. Default value(s) QX: 0H Allowed values 0H-C8H Forbidden values - Dependence Dependence on other parameters does not exist. After parameter value has been changed workaround is activated after 10 minutes.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. The number can be configured in range from 1 to 200. C8 Number of samples is set to 200.0 onwards Issue: 03H DN0948854 157 . 1 Number of samples is set to 1.0 2.2. with this value 40 samples are used. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Description This PRFILE parameter is used to control the number of samples used to calculate the average reported measurement value. See the following table for example values. 64 Number of samples is set to 100. Value (HEX) Meaning 0 Number of samples is set to 40 (default value). 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. 2. however.3 onwards 158 DN0948854 Issue: 03H . it is activated after 10 minutes. For more information on the feature. After parameter value has been changed. Value (HEX) Meaning 0 SIB3/SIB4 Cell Identity IE is encoded with 12 bits used for RNC-Id and 16 bits for Cell-Id (default). Feature Descriptions document.0 2. It requires another trigger that can be. 1 SIB3/SIB4 Cell Identity IE is encoded with 16 bits used for RNC-Id and 12 bits for Cell-Id. Feature RAN2054: Extension of RNC ids 2. for example. happen automatically. see RAN2054: Extension of RNC ids feature in Flexi Direct RU30. PRFILE and FIFILE parameter descriptions PRFILE 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. SIB update according to the new PRFILE value does not. Default value(s) QX: 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist.37 Parameter 007:0397 RNC_L3_CONTROL_032 Descriptive name CS RAB Active Failure Counter improvement Applicable controllers IPA-RNC. from RN6. a cell lock/unlock or an update of a radio network parameter that requires SIB update. 0 2.2. 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 0 Functionality is Disabled (default) 1 Functionality is Enabled. If this PRFILE is not enabled the counters are updated for WBTS-0/WCEL-0 (Anchor WBTS) object in such a situation. PRFILE Descriptions PRFILE and FIFILE parameter descriptions mcRNC. 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).38 Parameter 007:0398 RNC_L3_CONTROL_033 Descriptive name RNC workaround for UE problem Issue: 03H DN0948854 159 . from ADA4. After parameter value has been changed workaround is activated after 10 minutes.1 onwards Flexi Direct RNC.0 onwards Modifiable YES Description When this functionality is enabled.0 2. Default value(s) QX: 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. from mcRNC2. Feature - 2. 0 2. Default value(s) QX: 0H Allowed values 0H/1H Forbidden values - Dependence Dependence on other parameters does not exist. from ADA4. as well as the list of possible values. see TS-RNC-SW-149 (section 4. A PRFILE controllable workaround is needed in RNC to disable CPC for these users. Feature - 2.0 2.4 onwards mcRNC.2 onwards Flexi Direct RNC.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.13). PRFILE and FIFILE parameter descriptions PRFILE Descriptions Applicable controllers IPA-RNC. from RN6.0 2. from mcRNC2.1 onwards Modifiable YES Description Some UE models restart during ongoing data transfer if CPC is activated.1 Parameter 009:0101 IUB_DATA_RECV_INTERVAL Descriptive name IUB O&M TCP/IP connection data receive interval 160 DN0948854 Issue: 03H .3. 2. For further instructions. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Applicable controllers IPA-RNC. Feature 7992 . mcRNC Modifiable YES Description Data receive interval defines how often the IUB TCP/IP data received by the RNC is read. mcRNC Modifiable YES Issue: 03H DN0948854 161 . Default value(s) : 5D Allowed values 1D-100D Increments 1 Forbidden values - Dependence Dependence on other parameters does not exist.2 Parameter 009:0102 IUB_CONN_POLLING_TIME Descriptive name IUB O&M TCP/IP connection polling interval Applicable controllers IPA-RNC.3. Value Meaning 5 Received IUB TCP/IP data is read every 5 ms.IUB-CORBA MEDITATION (DX) 2. IUB-CORBA MEDITATION (DX) 2. PRFILE and FIFILE parameter descriptions PRFILE 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 05 The BS O&M receiving socket is polled for IUB O&M TCP/IP data every 5 ms. mcRNC Modifiable YES Description This parameter determines whether the RNC Support for Traffica feature is active or not.3.3 Parameter 009:0130 IP_MSG_MON Descriptive name RNC Support for Traffica Applicable controllers IPA-RNC. Feature 7992 . Default value(s) : 5D Allowed values 1D-100D Increments 1 Forbidden values - Dependence Dependence on other parameters does not exist. 162 DN0948854 Issue: 03H . If the IMEI is available to the RNC. • IMEI is sent to Traffica if it is available to the RNC. DN0948854 163 . 0xFE 0x1FF 0x1FE RU30 RU40 RU40 • For more information. The IMEI is available to Traffica only if it is available to the RNC. see theRAN1150: RNC Support for Traffica feature activation instructions. 0x1FF. • Only the first six digits of the IMSI are sent to Traffica. • • Only the first six digits of the IMSI are sent to Traffica IMEI is not sent to Traffica. • IMEI is not sent to Traffica. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Table 1 Supported parameters PRFILE Parameter Format of reports 1) sent by RNC IMSI and IMEI 2) availability in reports 0xFF RU30 • IMSI is sent to Traffica. only the first eight digits of the IMEI are sent to Traffica. 0x1FE Forbidden values - Dependence Dependence on other parameters does not exist. 0xFE. Feature RAN1150: RNC Support for Traffica 2. • IMSI is sent to Traffica.4 Parameter class 016 ALARM_SYSTEM Descriptive Name Alarm system 1) 2) Issue: 03H This refers specifically to RRC/RAB and packet call failure Traffica reports. Default value(s) QX: 00H (FALSE) Allowed values 0xFF. Feature - 2.4. Value Meaning 0 No end text 1 END OF MESSAGE text Default value(s) GX: 0D Allowed values 0D/1D Forbidden values - Dependence Dependence on other parameters does not exist.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.2 Parameter 016:0001 LAMP_PANEL_POLARITY Descriptive name Lamp panel polarity 164 DN0948854 Issue: 03H .4. 2. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description This class includes the alarm system parameters. 4. Value Meaning 0 Reverse polarity 1 Normal polarity Default value(s) GX: 1D Allowed values 0D/1D Forbidden values - Dependence Dependence on other parameters does not exist.3 Parameter 016:0002 ALARM_DRIVEN_OUTPUTS Descriptive name Number of alarm outputs directed by alarms Applicable controllers IPA-RNC Modifiable YES Issue: 03H DN0948854 165 . PRFILE Descriptions PRFILE and FIFILE parameter descriptions Applicable controllers IPA-RNC Modifiable YES Description The parameter determines the lamp panel polarity. Feature - 2. by default. The lamp panel is controlled by the alarm outputs and.4. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Description The parameter defines the number of alarm outputs which can be controlled on the basis of the alarms handled by the alarm system. Default value(s) GX: 10D Allowed values 0D/8D/10D Forbidden values - Dependence Dependence on other parameters does not exist. Feature - 2. 8 8 first outputs out of a maximum of 16 can be directed by alarms. 10 All outputs (16) can be directed by alarms.4 Parameter 016:0003 LAMP_PANEL_BUZZER Descriptive name Activation of lamp panel buzzer by alarms Applicable controllers IPA-RNC Modifiable YES 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. Value Meaning 0 There are no outputs directed by alarms. The rest of the alarm outputs can be used for other purposes. the buzzer of the lamp panel is activated only when a new lamp is lit. 166 DN0948854 Issue: 03H . 4. Issue: 03H DN0948854 167 . Printing mode can be long (= 0000H) or short (= 00FFH). PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning 0 The state of alarm outputs is updated only when the first alarm controlling a certain alarm output is set. The default mode is the long mode. the lamp panel buzzer is activated each time a new alarm controlling an alarm output is set.5 Parameter 016:0004 PRINTING_MODE Descriptive name Printing mode Applicable controllers IPA-RNC 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). Feature - 2. Default value(s) GX: 0D Allowed values 0D / 1D Forbidden values - Dependence Dependence on other parameters does not exist. the state of all the alarm outputs is first reset and then immediately set again according to the current alarm situation. 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. With this. 1 Each time a new alarm controlling an alarm output is set. New alarms controlling an alarm output which is already in alarm state do not cause activation of the buzzer. or when the last alarm controlling a certain alarm output is canceled. 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. Feature - 168 DN0948854 Issue: 03H . Default value(s) GX: 5D Allowed values 0-1440D Forbidden values Dependence Dependence on other parameters does not exist. Feature - 2.4. The configured value must match in both ends in order to have working supervision for the O&M interface. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Default value(s) GX: 0H Allowed values 0H / 00FFH Forbidden values - Dependence Dependence on other parameters does not exist. at which the heartbeat alarm is sent from a certain NE to NetAct. The parameter value defines the interval in minutes. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2. For instructions. see Activating RAN1461: RNC RNW alarm reduction. Flexi Direct RNC Modifiable YES Description This parameter controls the usage of WBTS level alarm to reduce the alarms in RNC.4. mcRNC.8 Parameter 016:0010 SUSPEND_MODE_SWITCH Descriptive name Suspended Mode Switch Applicable controllers IPA-RNC.7 Parameter 016:0009 WBTS_LEVEL_ALARM_SWITCH Descriptive name WBTS Level Alarm Switch Applicable controllers IPA-RNC. mcRNC. Feature RAN1461 . Flexi Direct RNC Issue: 03H DN0948854 169 .4.RNC RNW Alarm Reduction 2. Value Meaning 0 the feature is OFF 1 the feature is ON Default value(s) GX: 1D Allowed values 0-1D Forbidden values Dependence Dependence on other parameters does not exist. Flexi Direct RNC Modifiable YES Description This parameter defines the number of WCEL out of use alarm. mcRNC.RNC RNW Alarm Reduction 2. For instructions. see Activating RAN1461: RNC RNW alarm reduction. For instructions. Feature RAN1461 . PRFILE and FIFILE parameter descriptions PRFILE Descriptions Modifiable YES Description This parameter is used to control the usage of suspend mode alarm to reduce the RNC alarms. 170 DN0948854 Issue: 03H . see Activating RAN1461: RNC RNW alarm reduction. Value Meaning 0 the feature is OFF 1 the feature is ON Default value(s) GX: 1D Allowed values 0-1D Forbidden values Dependence Dependence on other parameters does not exist.9 Parameter 016:0011 WCEL_OUT_OF_USE_NUM Descriptive name WCEL Out Of Use Alarm Number Applicable controllers IPA-RNC.4. Value Meaning 100D 100 alarms Default value(s) GX: 100D Issue: 03H DN0948854 171 . the following alarms of this kind will be in suspend mode and cannot be seen by alarm database. Flexi Direct RNC Modifiable YES Description This parameter defines the number of HSDPA/HSUPA activation failure for a WCEL alarm for suspend mode.RNC RNW Alarm Reduction 2. mcRNC. Default value(s) QX: 300D Allowed values 0-1000D Forbidden values Dependence Dependence on other parameters does not exist. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Value Meaning 300D After the number of WCEL being out of use alarm is over 300. Feature RAN1461 . For instructions.4.10 Parameter 016:0012 HSPA_ACT_FAIL_NUM Descriptive name HSPA Activation Failure Number Applicable controllers IPA-RNC. see Activating RAN1461: RNC RNW alarm reduction. the following alarms of this kind will be in suspend mode and cannot be seen by rnw database. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Allowed values 0-500D Forbidden values Dependence Dependence on other parameters does not exist. For instructions.11 Parameter 016:0013 RNW_DATABASE_FAIL_NUM Descriptive name RNW Database Fail Alarm Number Applicable controllers IPA-RNC. Flexi Direct RNC Modifiable YES Description This parameter defines the number of RNW Database Fail Alarm for suspend mode. Value Meaning 20D After the number of rnw database fail alarm is over 20. 172 DN0948854 Issue: 03H . Feature RAN1461 . see Activating RAN1461: RNC RNW alarm reduction. Default value(s) GX: 20D Allowed values 0-100D Forbidden values Dependence Dependence on other parameters does not exist. mcRNC.RNC RNW Alarm Reduction 2.4. RNC RNW Alarm Reduction 2. 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. Value Meaning 100D when the number of wbts level alarm over 100.4. mcRNC.13 Parameter 016:0015 BUFFER_ALARM_THRESHOLD Descriptive name Buffered Alarm Threshold Issue: 03H DN0948854 173 . Flexi Direct RNC Modifiable YES Description This parameter defines the number of WBTS level alarm for suspend mode.4. see Activating RAN1461: RNC RNW alarm reduction.12 Parameter 016:0014 WBTS_LEVEL_ALARM_NUM Descriptive name WBTS Level Alarm Number Applicable controllers IPA-RNC. Feature RAN1461 .RNC RNW Alarm Reduction 2. PRFILE Descriptions PRFILE and FIFILE parameter descriptions Feature RAN1461 . For instructions. When the alarms is lower than the number then the alarm can be written to database again. Value Meaning 80D When the alarm number is lower than 80% level. For instructions. see Activating RAN1461: RNC RNW alarm reduction. Default value(s) GX: 80D Allowed values 0-100D Forbidden values Dependence Dependence on other parameters does not exist. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Applicable controllers IPA-RNC. the suspended alarm can be written to alarm database. Feature RAN1461 .5 Parameter class 038 MML_COMMAND_LOG Descriptive Name MML Command Log parameters Description The parameter class includes parameters to define timeout values and disk usage restrictions of the MML Command Log. mcRNC. Flexi Direct RNC Modifiable YES Description This parameter with the alarm number parameter such as rnw_database_fail_num defines the limitation. 174 DN0948854 Issue: 03H .RNC RNW Alarm Reduction 2. PRFILE Descriptions PRFILE and FIFILE parameter descriptions 2.5.6 Parameter class 055 LCS_PARAMETERS Descriptive Name Location-related parameters Description This class includes parameters related to Location Services (LCS).1 Parameter 055:0003 EMERGENCY_CALL_ISHO_SUP Descriptive name Directed emergency call inter-system handover feature Issue: 03H DN0948854 175 . The minimum value is three (3H) days and the maximum value is sixty (3CH) days.6.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. 2. Default value(s) GX: 3CH Allowed values 3H-3CH Forbidden values - Dependence Dependence on other parameters does not exist. Feature - 2. Feature - 2. mcRNC. 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. Default value(s) GX: FALSE Allowed values TRUE/FALSE Forbidden values - Dependence Dependence on other parameters does not exist. If the parameter is disabled.2 Parameter 055:0011 AGPS_SUPPORT Descriptive name A-GPS location method support Applicable controllers IPA-RNC. Value Meaning FALSE The location of emergency call is done in UTRAN. the location of the emergency call is done in UTRAN. mcRNC.6. If the parameter is enabled. Flexi Direct RNC 176 DN0948854 Issue: 03H . Flexi Direct RNC Modifiable YES Description This parameter activates the Directed Emergency Call Inter-System Handover feature.0. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Applicable controllers IPA-RNC. 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. The feature is optional. The feature is optional. 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. the location of the emergency call is done in UTRAN. FALSE Usage of the A-GPS method is not allowed. If the parameter is enabled. Default value(s) GX: FALSE Allowed values TRUE/FALSE Forbidden values - Dependence Dependence on other parameters does not exist.3 Parameter 055:0012 INT_EMERG_CALL_ISHO_SUP Descriptive name Intelligent Directed Emergency Call Inter-system Handover feature Applicable controllers IPA-RNC.6. Flexi Direct RNC Modifiable YES Description This parameter activates the intelligent directed emergency call inter-system handover feature. Issue: 03H DN0948854 177 . PRFILE Descriptions PRFILE and FIFILE parameter descriptions Modifiable YES Description Usage of the A-GPS method is allowed for location services. Feature - 2. mcRNC. If the parameter is disabled. Value Meaning TRUE Usage of the A-GPS method is allowed. Default value(s) GX: FALSE Allowed values TRUE/FALSE Forbidden values - Dependence Dependence on other parameters does not exist.6. Flexi Direct RNC Modifiable YES Description Usage of the NW-based A-GPS method is allowed for location services. mcRNC. 178 Value Meaning TRUE Usage of the NW-based A-GPS method is allowed. DN0948854 Issue: 03H . FALSE Usage of the NW-based A-GPS method is not allowed. Feature - 2. 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.4 Parameter 055:0013 NW_AGPS_SUPPORT Descriptive name NW-based A-GPS location method support Applicable controllers IPA-RNC. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Value Meaning FALSE The location of the emergency call is done in UTRAN. Value Meaning TRUE Usage of the IUPC interface is allowed.5 Parameter 055:0015 IUPC_INTERFACE Descriptive name IUPC interface support Applicable controllers IPA-RNC.6. Flexi Direct RNC Modifiable YES Description Usage of the IUPC interface is allowed. Feature - 2. FALSE Usage of the IUPC interface is not allowed. 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. mcRNC. Default value(s) GX: FALSE Allowed values TRUE/FALSE Forbidden values - Issue: 03H DN0948854 179 . 7. Feature Descriptions and Instructions. 058:0001 UA_POLICY_FEATURE. RU40.7 Parameter class 058 OAM_SECURITY Descriptive Name O&M Security Parameters Description This parameter class includes parameters concerning O&M security. Rel. for more information. PRFILE and FIFILE parameter descriptions PRFILE Descriptions Dependence Dependence on other parameters does not exist. see WCDMA RAN. 058:0004 USER_ACCOUNT_LOCK_LIMIT These parameters are used to control RAN2883: User Security Policy for RNC196/450/2600.1 Parameters 058:0000 PW_POLICY_FEATURE. 2. Feature - 2. 180 DN0948854 Issue: 03H . Documents Similar To PRFILE Descriptions IssueSkip carouselcarousel previouscarousel nextMcRNC Commissioning Guide Document-V1.0Replacing McRNC Hardware UnitsAlm Mcrnc AlarmsMcRNC U AND C PLANEMcrnc Configuration Principles - How to Improve Accessibility UMTS NokiaHSDPA Performance Improvement Discussion_NSN_2007051801 01 RN33821EN40GLA0 McRNC ArchitecturePRFILE Descriptions Issue 03FGeneral McRNC CLI Commands IntroductionMcRNC Transport Introduction01_RN33861EN50GLA0_mcRNC_Architecture.pdfRAN2874 McRNC HW Capacity Expansion SupportRU40 BB Dimensioning Rules for SM Rel.2RU50 PRFILE DescriptionsProcessing SetsCME_Poster_Data_Check(02).pdf9781439806500-11.pdfGSM_3G_WCDMA_HSPA_LTE_Fact_Sheet_150511.pdf9781439806500-11RRC and RABhsdpaUL CE Utilization Issue After SRB Over HSUPA 20140828123576527 NPO Rec Parameters for Radio RU20UMTS Evolution From 3GPP Release 7 to Release 8Mobile WiFi Product Description E5330 03 Englishcv1Evaluation of Statistical Models in 3G and 4GFast Radio Bearer Setup.pdfCoverage Analysis of Skype VoIP Services over HSUPAMore From nitoys531Skip carouselcarousel previouscarousel nextIntroduccion ATM--IP.pdfTS-RNC-SW-038-I14Fundamentos de La Tecnología Gsm Cap1TS-RNC-SW-038-I13Empieza a Utilizar IMAP y POP3TS-RNC-SW-038-I26GSM-07GSM-07.pdfArquitectura GSM y UMT.pdfFooter MenuBack To TopAboutAbout ScribdPressOur blogJoin our team!Contact UsJoin todayInvite FriendsGiftsLegalTermsPrivacyCopyrightSupportHelp / FAQAccessibilityPurchase helpAdChoicesPublishersSocial MediaCopyright © 2018 Scribd Inc. .Browse Books.Site Directory.Site Language: English中文EspañolالعربيةPortuguês日本語DeutschFrançaisTurkceРусский языкTiếng việtJęzyk polskiBahasa indonesiaSign up to vote on this titleUsefulNot usefulYou're Reading a Free PreviewDownloadClose DialogAre you sure?This action might not be possible to undo. Are you sure you want to continue?CANCELOK
Copyright © 2024 DOKUMEN.SITE Inc.