Wcdma16 Feature Descriptions and Instructions

Nokia

WCDMA RAN, Rel. WCDMA 17, Operating Documentation, Issue 01 WCDMA 16 Feature Descriptions and Instructions DN09203161 Issue 02 Approval Date 2016-07-15

WCDMA 16 Feature Descriptions and Instructions

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

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.

2

©2016Nokia

DN09203161Issue:02


Table of Contents This document has 546 pages Summary of changes................................................................... 25 1

Introduction to WCDMA 16 features............................................ 27

2

WCDMA 16 Basic Support with NetAct 15.5 + INES PP337....... 28

3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5

RAN3045 Benefits........................................................................ 31 RAN3045 Functional description..................................................31 RAN3045 System impact............................................................. 31 RAN3045 Reference data............................................................ 32 Activating RAN3045: Activity Based UL Power Control for Rel99 DCH............................................................................................. 33

3.1.6

Verifying RAN3045: Activity Bas ed UL Power Control for Rel99 DCH............................................................................................. 34

3.1.7

Deactivating RAN3045: Activity Based UL Power Control for Rel99 DCH................................................................................... 35 Testing RAN3045: Activity Based UL Power Control for Rel99 DCH............................................................................................. 36 Phase 1: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature deactivated..................................37 Phase 2: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature activated......................................38 RAN3043: Advanced HSUPA Time Division Scheduling............. 39

3.1.8 3.1.8.1 3.1.8.2 3.2 3.2.1 3.2.2 3.2.3 3.2.4

RAN3043 Benefits........................................................................ 39 RAN3043 Functional description.................................................. 40 RAN3043 System impact............................................................. 40 RAN3043 Reference data............................................................ 41

3.2.5

Activating RAN3043: Advanced HSUPA Time Division Scheduling. 42 Verifying RAN3043: Advanced HSUPA Time Division Scheduling.. 43 Deactivating RAN3043: Advanced HSUPA Time Division Scheduling................................................................................... 44

3.2.6 3.2.7

DN09203161Issue:02

Radio resource management features.........................................31 RAN3045: Activity Based UL Power Control for Rel99 DCH....... 31

3.3 3.3.1

RAN3218: Enhanced Cell Change from HSPA to 2G..................45 RAN3218 Benefits........................................................................45

3.3.2 3.3.3

RAN3218 Functional description..................................................46 RAN3218 System impact............................................................. 46

3.3.4 3.3.5

RAN3218 Reference data............................................................ 47 Activating RAN3218: Enhanced Cell Change from HSPA to 2G..... 48

3.3.6 3.3.7

Verifying RAN3218: Enhanced Cell Change from HSPA to 2G... 50 Deactivating RAN3218: Enhanced Cell Change from HSPA to 2G. 51

©2016Nokia

3


3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.5.1 3.4.5.2 3.4.5.3 3.4.5.4 3.4.5.5 3.4.5.6 3.4.5.7 3.4.6 3.4.6.1 3.4.6.2 3.4.6.3 3.4.6.4 3.4.6.5 3.4.6.6 3.4.6.7 3.4.7 3.4.7.1 3.4.7.2 3.4.7.3 3.4.7.4 3.4.7.5

4

RAN3093: Enhanced MBLB......................................................... RAN3093 Benefits........................................................................ RAN3093 Functional description.................................................. RAN3093 System impact.............................................................

52 52 52 54

RAN3093 Reference data............................................................54 Activating RAN3093: Enhanced MBL B........................................ 57 Activating Enhanced load balancing............................................ 58 Activating Enhanced layering during voice call setup - Blind IFHO in RRC setup................................................................................ 59 Activating Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state................................................. 60 Activating MBLB HSPA load state by pass................................... 61 Activating Enhanced inactivity-trigger ed layering without compressed mode measurements...............................................62 Activating Enhanced mobility triggere d layering.......................... 65 Activating Enhanced inactivity triggered layering in state transition to CCH state.................................................................................66 Verifying RAN3093: Enhanced MBL B..........................................67 Verifying Enhanced load balancing.............................................. 67 Verifying Enhanced layering during v oice call setup - Blind IFHO in RRC setup................................................................................ 69 Verifying Enhanced layering during v oice call setup - Blind IFHO for CS voice call from CCH state................................................. 71 Verifying the MBLB HSPA load state bypass............................... 72 Verifying Enhanced inactivity-triggered layering without compressed mode measurements...............................................75 Verifying Enhanced mobility-triggere d layering............................ 78 Verifying Enhanced inactivity-triggere d layering in state transition to CCH state.................................................................................79 Deactivating RAN3093: Enhanced M BLB....................................81 Deactivating Enhanced load balancin g........................................ 81 Deactivating Enhanced layering during voice call setup - Blind IFHO in RRC setup...................................................................... 82 Deactivating Enhanced layering durin g voice call setup - Blind IFHO for CS voice call from CCH state........................................83 Deactivating the MBLB HSPA load state bypass......................... 84 Deactivating Enhanced inactivity triggered layering without compressed mode measurements...............................................85

3.4.7.6

Deactivating Enhanced mobility triggered layering...................... 86

3.4.7.7 3.5 3.5.1 3.5.2 3.5.3

Deactivating Enhanced inactivity triggered layering in state transition to CCH state................................................................. 87 RAN2518: High Speed Cell_FACH Enhanced.............................88 RAN2518 Benefits........................................................................88 RAN2518 Functional description..................................................89 RAN2518 System impact............................................................. 89

3.5.4 3.5.5 3.5.6

RAN2518 Reference data............................................................90 Activating RAN2518: High Speed Cell_FACH Enhanced............ 93 Verifying RAN2518: High Speed Cell_FACH Enhanced..............95

©2016Nokia

DN09203161Issue:02


3.5.7 3.5.8 3.5.8.1

3.6 3.6.1

Deactivating RAN2518: High Speed Cell_FACH Enhanced........ 97 Testing RAN2518: High Speed Cell_FACH Enhanced................ 99 Testing the RAN2518: High Speed C ell_FACH Enhanced related counters....................................................................................... 99 Testing the subunits consumption of reserved HSUPA resource steps for HS-RACH users............................................................ 99 RAN2869: HSPA Subscriber Increase....................................... 101 RAN2869 Benefits...................................................................... 102

3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.6.7 3.7 3.7.1

RAN2869 Functional description................................................ 102 RAN2869 System impact........................................................... 102 RAN2869 Reference data.......................................................... 103 Activating RAN2869: HSPA Subscrib er Increase.......................104 Verifying RAN2869: HSPA Subscriber Increase........................ 106 Deactivating RAN2869: HSPA Subsc riber Increase.................. 107 RAN3046: Interference Cancellation for 4Rx............................. 108 RAN3046 benefits......................................................................108

3.7.2 3.7.3 3.7.4 3.7.5

RAN3046 system impact............................................................ 109 RAN3046 reference data............................................................110 Activating RAN3046................................................................... 112

3.7.6 3.7.7 3.8

Verifying RAN3046..................................................................... 112 Deactivating RAN3046............................................................... 113 RAN3040: IRC Receiver............................................................. 114

3.8.1 3.8.2 3.8.3 3.8.4

RAN3040 Benefits...................................................................... 114 RAN3040 Functional description................................................ 114 RAN3040 System impact........................................................... 115 RAN3040 Reference data.......................................................... 115

3.8.5 3.8.6 3.8.7 3.8.8

Activating RAN3040: IRC Receiver............................................116 Verifying RAN3040: IRC Receiver.............................................. 117 Deactivating RAN3040: IRC Receiver........................................118 Testing RAN3040: IRC Receiver................................................ 119

3.9 3.9.1 3.9.2 3.9.3

RAN3235: Optimized Packet Handlin g at RNC ........................ 121 RAN3235 Benefits......................................................................121 RAN3235 Functional description................................................121 RAN3235 System impact........................................................... 122

3.9.4 3.9.5 3.9.6 3.9.7

RAN3235 Reference data.......................................................... 123 Activating RAN3235: Optimized Packet Handling at RNC.........124 Verifying RAN3235: Optimized Packet Handling at RNC...........125 Deactivating RAN3235: Optimized Packet Handling at RNC.....126

3.10 3.10.1

RAN2902: RACH Capacity Increase..........................................127 RAN2902 Benefits......................................................................127

3.10.2 3.10.3 3.10.4

RAN2902 Functional description................................................128 RAN2902 System impact........................................................... 129 RAN2902 Reference data.......................................................... 129

3.10.5 3.10.6

Activating RAN2902: RACH Capacity Increase.........................131 Verifying RAN2902: RACH Capacity Increase...........................133

3.5.8.2

DN09203161Issue:02

RAN3046 functional description.................................................

©2016Nokia

108

5


3.10.7 3.10.8 3.11 3.11.1

Deactivating RAN2902: RACH Capac ity Increase.....................134 Testing RAN2902: RACH Capacity In crease............................. 135 RAN2892: WCDMA-LTE Load Balancing.................................. 140 RAN2892 Benefits......................................................................140

3.11.2 3.11.3 3.11.4 3.11.5

RAN2892 Functional description................................................ 141 RAN2892 System impact........................................................... 144 RAN2892 Reference data.......................................................... 144 Activating RAN2892: WCDMA-LTE L oad Balancing..................146

3.11.6 3.11.7

Verifying RAN2892: WCDMA-LTE Lo ad Balancing....................148 Deactivating RAN2892: WCDMA-LTE Load Balancing..............150

4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 4.2 4.2.1 4.2.2

6

Telecom features........................................................................ RAN3086: CSFB with RIM......................................................... RAN3086 Benefits...................................................................... RAN3086 Functional description................................................ RAN3086 System impact........................................................... RAN3086 Reference data..........................................................

151 151 151 151 154 154

Activating RAN3086: CSFB with RIM ........................................ 156 Verifying RAN3086: CSFB with RIM.......................................... 157 Deactivating RAN3086: CSFB with R IM.................................... 158 RAN3082: Device Detection...................................................... 159 RAN3082 Benefits...................................................................... RAN3082 Functional Description...............................................

160 160

4.2.3 4.2.4

RAN3082 System impact........................................................... 162 RAN3082 Reference data.......................................................... 162

4.2.5 4.2.5.1 4.2.6

Activating RAN3082: Device Detectio n......................................164 Activating generic IMEI query in the R NC..................................166 Verifying RAN3082: Device Detection ........................................167

4.2.6.1 4.2.7 4.2.7.1

Verifying generic IMEI query in the R NC....................................169 Deactivating RAN3082: Device Detec tion..................................170 Deactivating a Whitelist or Blacklist fu nctionality....................... 170

4.2.7.2

Deactivating generic IMEI query in th e RNC..............................171

5

Transmission and transport features..........................................173

5.1 5.1.1 5.1.2 5.1.3

RAN3112: mcRNC Integrated Ethernet Switching..................... 173 RAN3112 Benefits...................................................................... 173 RAN3112 Functional description................................................ 173 RAN3112 System impact........................................................... 174

5.1.4

RAN3112 Reference data.......................................................... 175

5.2 5.2.1 5.2.2

RAN3193: OSPF Authentication for Controller.......................... 176 RAN3193 Benefits......................................................................177 RAN3193 Functional description................................................177

5.2.3 5.2.4

RAN3193 System impact........................................................... 178 RAN3193 Reference data.......................................................... 178

6

Operability features.................................................................... 180

6.1

RAN3242: Category for Obsolete Parameters...........................180

©2016Nokia

DN09203161Issue:02


6.1.1 6.1.2 6.1.3 6.1.4

RAN3242 Benefits...................................................................... 180 RAN3242 Functional description................................................180 RAN3242 System impact........................................................... 181 RAN3242 Reference data.......................................................... 182

6.2

RAN2706: Delta Configuration and Change Notification for BTS Transport....................................................................................183 RAN2706 Benefits...................................................................... 183 RAN2706 Functional description................................................184

6.2.1 6.2.2 6.2.3 6.2.4 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4 6.4.1 6.4.2 6.4.3 6.4.4 6.4.5 6.4.5.1

RAN3247/LTE2507/RG602496Refe rence data........................ 194 Activating RAN3247: Energy Efficien cy Shut Down Mode with RF Sharing.......................................................................................194

6.4.5.1.1 6.4.5.1.2

Activating RG301936: Intelligent MC PA TRX shutdown in GSM..... 195 Activating RG301936: Intelligent MCPA TRX shutdown............ 195 Verifying RG301936: Intelligent MCP A TRX shutdown.............. 195

6.4.5.1.3 6.4.5.2 6.4.5.2.1 6.4.5.2.2

Deactivating RG301936: Intelligent MCPA TRX shutdown........197 Activating RAN955: Power Saving Mode for BTS in WCDMA...197 Activating RAN955: Power Saving Mode for BTS......................197 Verifying RAN955: Power Saving Mo de for BTS....................... 200

6.4.5.2.3 6.4.5.3

6.5 6.5.1

Deactivating RAN955: Power Saving Mode for BTS................. 201 Activating LTE1103: Load Based Po wer Saving for Multi-layer Networks in LTE......................................................................... 202 Activating LTE1103: Load Based Power Saving for Multi-layer Networks.................................................................................... 202 Deactivating LTE1103: Load Based Power Saving for Multi-layer Networks.................................................................................... 204 RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing........... 205 RAN3060 Benefits......................................................................205

6.5.2 6.5.3

RAN3060 Functional description................................................205 RAN3060 System impact........................................................... 207

6.5.4 6.5.5

RAN3060 Reference data.......................................................... 208 Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing. 210 Verifying RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing... 212

6.4.5.3.1 6.4.5.3.2

6.5.6

DN09203161Issue:02

RAN2706 System impact........................................................... 188 RAN2706 Reference data.......................................................... 189 RAN2367: DNS Support for Certifica te Examination................. 190 RAN2367 Benefits...................................................................... 190 RAN2367 Functional description................................................190 RAN2367 System impact........................................................... 191 RAN2367 Reference data.......................................................... 192 RAN3247/LTE2507/RG602496: Energy Efficiency Shut Down Mode with RF Sharing................................................................193 RAN3247/LTE2507/RG602496Bene fits....................................193 RAN3247/LTE2507/RG602496 Functional description..............193 RAN3247/LTE2507/RG602496Syst em impact......................... 193

©2016Nokia

7


6.5.7

6.5.8.1 6.5.8.2 6.5.8.3 6.6

Deactivating RAN3060: Flexi Multirad io BTS Antenna Rx RFsniffing........................................................................................ 215 Testing RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing..... 216 Test case 1: RF-scanning........................................................... 216 Test case 2: PIM simulation....................................................... 220 Test case 3: PIM desensitization................................................221 RAN2872: IPA-RNC Symptom Repor t....................................... 223

6.6.1 6.6.2 6.6.3 6.6.4 6.6.5 6.6.6 6.6.6.1 6.6.6.2

RAN2872 Benefits...................................................................... 224 RAN2872 Functional description................................................224 RAN2872 System impact........................................................... 225 RAN2872 Reference data.......................................................... 225 Configuring RAN2872: IPA-RNC Symptom Report....................226 Testing RAN2872: IPA-RNC Symptom Report...........................233 Symptom report collection using OMS CLI................................ 234 Symptom report collection using RNC MML commands............235

6.7 6.7.1 6.7.2 6.7.3

RAN3063 Benefits...................................................................... 238 RAN3063 Functional description................................................238 RAN3063 System impact........................................................... 238

6.7.4 6.7.5 6.7.6

RAN3063 Reference data.......................................................... 238 Activating RAN3063: KPI Reporting Based on Cell Type .......... 239 Verifying RAN3063: KPI Reporting Based on Cell Type............ 240

6.7.7 6.8 6.8.1 6.8.2

Deactivating RAN3063: KPI Reporting Based on Cell Type...... 242 RAN3150: mcRNC Event Based Symptom Data Collection......24 2 RAN3150 Benefits...................................................................... 243 RAN3150 Functional description................................................ 243

6.8.3 6.8.4 6.9 6.9.1

RAN3150 System impact........................................................... 244 RAN3150 Reference data.......................................................... 244 RAN2991: Modification of WCDMA F requency......................... 245 RAN2991 Benefits...................................................................... 245

6.9.2 6.9.3 6.9.4 6.9.5

RAN2991 Functional description................................................ 246 RAN2991 System impact........................................................... 248 RAN2991 Reference data.......................................................... 249 Testing RAN2991: Modification of WCDMA Frequency............. 250

6.5.8

8

RAN3063: KPI Reporting Based on C ell Type........................... 238

6.10 6.10.1 6.10.2 6.10.3

RAN2268: Multi-Layer Certificate Authorities.............................251 RAN2268 Benefits......................................................................251 RAN2268 Functional description................................................252 RAN2268 System impact........................................................... 253

6.10.4 6.11

RAN2268 Reference data.......................................................... 254 RAN3096: OMS HP Gen9 HW...................................................255

6.11.1 6.11.2 6.11.3

RAN3096 Benefits......................................................................255 RAN3096 Functional description................................................255 RAN3096 System impact........................................................... 255

6.11.4 6.12

RAN3096 Reference data.......................................................... 256 RAN2702: Parameter Level Logging of BTS User Events.........256

©2016Nokia

DN09203161Issue:02


6.12.1 6.12.2 6.12.3 6.12.4

RAN2702 Benefits......................................................................257 RAN2702 Functional description................................................ 257 RAN2702 System impact........................................................... 258 RAN2702 Reference data.......................................................... 259

6.12.5 6.13 6.13.1

Testing RAN2702: Parameter level lo gging of BTS user events...... 259 RAN2571: Support of TLS 1.2................................................... 260 RAN2571 Benefits......................................................................260

6.13.2 6.13.3 6.13.4

RAN2571 Functional description................................................ 261 RAN2571 System impact........................................................... 262 RAN2571 Reference data.......................................................... 263

7 7.1 7.1.1 7.1.2 7.1.3

Performance monitoring features............................................... 264 RAN2164: Compensated CQI Meas urement.............................264 RAN2164 Benefits......................................................................264 RAN2164 Functional descriptio n................................................264 RAN2164 System impact........................................................... 264

7.1.4 7.2

RAN2164 Reference data.......................................................... 264 RAN2973: Enhanced IMSI Based Ca ll Monitoring.....................267

7.2.1 7.2.2 7.2.3 7.2.4


7.2.5

Activating and configuring RAN2973 : Enhanced IMSI-based Monitoring.................................................................................. 274 Activating RAN2973: Enhanced IMSI-based Monitoring on IPARNC........................................................................................... 274 Configuring GIVAXI/givClient..................................................... 274 Installing licenses for IPA-RNC.................................................. 275 Installing L3 Data Collector........................................................ 276

7.2.5.1 7.2.5.1.1 7.2.5.1.2 7.2.5.1.3 7.2.5.1.4 7.2.5.1.5 7.2.5.1.6 7.2.5.1.6.1

Authorizing Pre-Shared Key (PSK)............................................ 276 Configuring MSGMONPSK for data encryption......................... 276 Configuring and verifying additional steps for IPA-RNC.............277 Configuring NPEG(P) towards OMU..........................................277

7.2.5.1.6.2 7.2.5.1.6.3 7.2.5.1.6.4 7.2.5.1.6.5

Configuring static IP route to external monitoring tool............... 279 Configuring site routers.............................................................. 279 Configuring external monitoring tool (alternative to DHCP)....... 280 Verifying IP configuration........................................................... 280

7.2.5.2

Activating RAN2973: Enhanced IMSI-based Monitoring on

7.2.5.2.1 7.2.5.2.2 7.2.5.2.3 7.2.5.2.4 7.2.6

mcRNC.......................................................................................281 Configuring IP connection at mcRNC........................................ 281 Configuring Givaxi/givClient....................................................... 283 Installing licenses for mcRNC.................................................... 283 Installing L3 Data Collector........................................................ 284 Verifying RAN2973: Enhanced IMSI-based Monitoring............. 284

7.2.6.1

DN09203161Issue:02

Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on IPA-RNC........................................................284

©2016Nokia

9


7.2.6.2

7.2.10 7.2.10.1 7.2.10.2

Verifying RAN2973: Enhanced IMSI-based call monitoring on mcRNC.......................................................................................284 Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on mcRNC.......................................................... 286 Deactivating RAN2973: Enhanced IMSI-based Monitoring....... 286 Deactivating RAN2973: Enhanced IM SI-based call monitoring in IPA-RNC.....................................................................................286 Deactivating RAN2973: Enhanced IM SI-based call monitoring in mcRNC.......................................................................................287 Analyzing monitored data and trouble shooting.......................... 288 Analyzing monitored data...........................................................288 Troubleshooting RAN2973: Enhance d IMSI-based Call Monitoring ................................................................................................... 288 Configuring mcRNC to support Layer 3 routing towards Megamon. 290 RAN2930: IMSI-based Call Monitoring...................................... 293 RAN2930 Benefits......................................................................293 RAN2930 Functional description................................................ 294

7.2.10.3 7.2.10.4 7.2.10.5

RAN2930 System impact........................................................... 298 RAN2930 Reference data.......................................................... 298 Activating and configuring RAN2930: IMSI-based Monitoring... 300

7.2.10.5.1 7.2.10.5.1.1 7.2.10.5.1.2

Activating RAN2930: IMSI-based Monitoring on IPA-RNC........ 300 Configuring GIVAXI/givClient..................................................... 300 Installing licenses for IPA-RNC.................................................. 301

7.2.10.5.1.3 7.2.10.5.1.4 7.2.10.5.1.5 7.2.10.5.1.6 7.2.10.5.2

Installing L3 Data Collector........................................................ 301 Authorizing Pre-Shared Key (PSK)............................................ 301 Configuring MSGMONPSK for data encryption......................... 302 Configuring and verifying additional s teps for IPA-RNC.............302 Activating RAN2930: IMSI-based Monitoring on mcRNC.......... 306

7.2.10.5.2.1 7.2.10.5.2.2 7.2.10.5.2.3 7.2.10.5.2.4

Configuring IP connection at mcRN C........................................ 306 Configuring Givaxi/givClient....................................................... 308 Installing licenses for mcRNC.................................................... 309 Installing L3 Data Collector........................................................ 309

7.2.10.6 7.2.10.6.1

Verifying RAN2930: IMSI-based Monitoring...............................309 Verifying RAN2930: IMSI-based Monitoring from L3 Data Collector on IPA-RNC................................................................................309

7.2.10.6.2 7.2.10.6.3

Verifying RAN2930: IMSI-based call monitoring on mcRNC......311 Verifying RAN2930: IMSI-based Monitoring from L3 Data Collector on mcRNC..................................................................................313

7.2.10.7 7.2.10.7.1

Deactivating RAN2930: IMSI-based Monitoring.........................314 Deactivating RAN2930: IMSI-based call monitoring in IPA-RNC..... 314

7.2.10.7.2 7.2.10.8

Deactivating RAN2930: IMSI-based call monitoring in mcRNC.315 Analyzing monitored data and troubleshooting..........................316

7.2.10.8.1 7.2.10.8.1.1 7.2.10.8.1.2

Analyzing monitored data...........................................................316 Analyzing monitored data from IPA-RNC...................................316 Analyzing monitored data from mcRNC.....................................317

7.2.6.3 7.2.7 7.2.7.1 7.2.7.2 7.2.8 7.2.8.1 7.2.8.2 7.2.9

10

©2016Nokia

DN09203161Issue:02


7.2.10.8.2 7.3 7.3.1 7.3.2

Troubleshooting RAN2930: IMSI-bas ed Call Monitoring ...........317 RAN3104: HSPA User Amount Mo nitoring................................ 319 RAN3104 Benefits......................................................................319 RAN3104 Functional description................................................ 319

7.3.3 7.3.4 7.3.5 7.4

RAN3104 System impact........................................................... 320 RAN3104 Reference data.......................................................... 320 Testing RAN3104: User Amount Mon itoring.............................. 322 RAN2862: Multi-RAB Dedicated Cou nter Set............................ 323

7.4.1 7.4.2 7.4.3 7.4.4 7.4.5 7.4.6 7.4.7 7.5 7.5.1 7.5.2

RAN2862 Benefits......................................................................324 RAN2862 Functional description................................................ 324 RAN2862 System impact........................................................... 324 RAN2862 Reference data.......................................................... 324 Activating RAN2862: Multi-RAB Ded icated Counter Set........... 326 Verifying RAN2862: Multi-RAB Dedicated Counter Set............. 326 Deactivating RAN2862: Multi-RAB D edicated Counter Set....... 327 RAN2304: VSWR Monitoring..................................................... 328 RAN2304 Benefits...................................................................... 328 RAN2304 Functional description................................................ 329

7.5.3 7.5.4 7.5.5

RAN2304 Reference data.......................................................... 330 Testing RAN2304: VSWR Monitoring .........................................331

8

RNC solution features................................................................

8.1 8.1.1

RAN2646: External Alarm Input Sup port of mcRNC..................333 RAN2646 Benefits...................................................................... 333

8.1.2 8.1.3 8.1.4 8.1.5 8.1.6 8.1.7

RAN2646 Functional description................................................ RAN2646 System impact........................................................... RAN2646 Reference data..........................................................

333

333 334 334

8.2 8.2.1 8.2.2

Activating RAN2646: External Alarm Input Support of mcRNC. 335 Verifying RAN2646: External Alarm I nput Support of mcRNC... 340 Deactivating RAN2646: External Ala rm Input Support of mcRNC... 341 RAN3057: mcRNC Signaling Capacity License.........................342 RAN3057 Benefits......................................................................342 RAN3057 Functional description................................................342

8.2.3 8.2.4 8.2.5 8.3

RAN3057 System impact........................................................... 346 RAN3057 Reference data.......................................................... 346 Testing RAN3057: mcRNC Signaling Capacity License............ 348 RAN3005: Network Resiliency for mcRNC................................ 350

8.3.1 8.3.2 8.3.2.1

RAN3005 Benefits......................................................................350 RAN3005 Functional description................................................350 Differences between RAN3005: Network Resiliency for mcRNC and RAN2512: Network Resiliency for RNC2600 features........ 352 Planning for Network Resiliency................................................ 353 Planning IP addressing solutions on RNC-cl............................. 353 Planning Iupc interface configuration.........................................354

8.3.2.2 8.3.2.2.1 8.3.2.2.2

DN09203161Issue:02

RAN2304 System impact........................................................... 330

©2016Nokia

11


8.3.2.2.3 8.3.2.2.4 8.3.2.2.5 8.3.2.2.6

Planning Iu-BC interface configu ration for mcRNC BkPRNC.... 354 Planning Iub interface configuration ..........................................355 Planning Iu and Iur interfaces.................................................... 355 Planning management plane configur ation................................357

8.3.2.2.7 8.3.2.2.8 8.3.2.3 8.3.2.3.1

Planning transport network configuration ..................................357 Principles for NW operations with net work resiliency.................357 Operating principles................................................................... 358 Auto-adaptation in mcRNC........................................................ 358

8.3.2.3.2 8.3.2.3.3 8.3.2.3.4 8.3.2.3.5 8.3.2.3.6 8.3.2.3.6.1 8.3.2.3.6.2 8.3.2.3.6.3 8.3.2.3.6.4 8.3.2.3.6.5

Operating and Maintaining overview.......................................... 358 NetAct topology view.................................................................. 359 Backup Physical RNC System management............................. 360 Interpreting of the system logs................................................... 364 Redundancy switch.................................................................... 366 Activity model............................................................................. 366 Use cases.................................................................................. 367 Detecting redundancy switch necessi ty..................................... 372 Comparison of prepared and unprepared redundancy switch... 372 Redundancy conflict................................................................... 373

8.3.2.3.7 8.3.2.4

Network Resiliency operations in OMS Element Manager (OMS EM).............................................................................................374 Network Resiliency related terms............................................... 377

8.3.2.5 8.3.3

Miscellaneous notes...................................................................380 RAN3005 System impact........................................................... 381

8.3.4 8.3.5

12

RAN3005 Reference data.......................................................... 382 Activating RAN3005: Network Resilie ncy for mcRNC................385

8.3.5.1 8.3.5.1.1 8.3.5.1.2

Enlarging QNDRBD................................................................... 386 Modifying the VG_System LDAP con figuration..........................386 Re-initialize hard disk to enlarge VG_ System manually............ 387

8.3.5.1.3 8.3.5.1.4

Enlarging QNDRBD logical volume and corresponding DRBD file system........................................................................................393 Troubleshooting..........................................................................395

8.3.5.2 8.3.5.3 8.3.5.4 8.3.5.5

Commission PrPRNC.................................................................398 Commission PRNC to StPRNC (mcRNC)..................................399 Commission PRNC to BkPRNC (mcRNC).................................401 Create BkPRNC object at PrPRNC (mcRNC)............................402

8.3.5.6 8.3.5.7 8.3.5.8 8.3.5.9

Create RNCSRV at BkPRNC (mcRNC)..................................... 403 Configuring secure RNC-cl O&M interface................................ 404 Configuring dedicated cluster interface......................................407 Synchronization (mcRNC)..........................................................408

8.3.5.10 8.3.5.11

Configuring RNCSRV at BkPRNC (mcRNC)............................. 410 Configure network interfaces......................................................411

8.3.5.12 8.3.5.13

MSC configuration for Core Network (mcRNC)..........................411 Configuring SGSN for Core Network in resilient network with mcRNC.......................................................................................414

8.3.5.14 8.3.5.15

Configuring Iur interface for mcRNC network resiliency............ 416 Committing the IP address pre-configuration.............................419

©2016Nokia

DN09203161Issue:02


8.3.5.16 8.3.6 8.3.7 8.3.8

Mapping IP address................................................................... 420 Verifying RAN3005: Network Resilie ncy for mcRNC................. 422 Deactivating RAN3005: Network Re siliency for mcRNC........... 423 Other instructions....................................................................... 425

8.3.8.1 8.3.8.1.1 8.3.8.1.2 8.3.8.1.3

Operating instructions................................................................ 425 Testing IP connectivity for mcRNC in resilient network.............. 425 Performing controlled redundancy s witch.................................. 426 Performing forced redundancy swit ch (mcRNC)........................428

8.3.8.1.4 8.3.8.1.5 8.3.8.1.6 8.3.8.1.6.1 8.3.8.1.6.2 8.3.8.1.6.3 8.3.8.1.6.4 8.3.8.1.7 8.3.8.1.8

Performing controlled redunda ncy switchback...........................429 Performing forced redundancy switc hback for mcRNC............. 430 Network Resiliency operations in OMS......................................431 Configuring network resiliency using OMS Element Manager... 431 Performing forced redundancy switc h using OMS EM...............432 Performing redundancy switch using OMS EM..........................433 Performing redundancy switchback using OMS EM.................. 433 Reconfiguring BTS for Network Resi liency................................ 434 Configuring IP addresses in backup build for BkPRNC (mcRNC)... 435

8.3.8.1.9 8.3.8.1.10 8.3.8.1.10.1

Performing IP auto adaptation................................................... 435 mcRNC SW builds upgrade on BkPRNC...................................437 Creating BPS fallback................................................................ 438

8.3.8.1.10.2 8.3.8.1.10.3

Upgrading mcRNC SW builds and B PS on BkPRNC................ 439 Activating new BPS on BkPRNC (mcRNC)............................... 442

8.3.8.1.10.4 8.3.8.1.10.5 8.3.9

Operating BPS on BkPRNC with the Activity Mode: Loaded or Active................................................................................. 444 Deleting BPS fallback.................................................................447 RAN2512: Network Resiliency for RNC2600............................. 449

8.3.9.1 8.3.9.2 8.3.9.3 8.3.9.4


8.3.9.5

Activating, operating, and maintainin g RAN2512: Network Resiliency for RNC2600............................................................. 460 RAN2512: Network Resiliency for RNC2600 activation procedure overview..................................................................................... 460

8.3.9.5.1

DN09203161Issue:02

8.3.9.5.2

Activating RAN2512: Network Resiliency for RNC2600............ 460

8.3.9.5.2.1

Commissioning BkPRNC........................................................... 461

8.3.9.5.2.2 8.3.9.5.2.3

Configuring network resiliency using OMS Element Manager... 464 Configuring network resiliency using MML commands.............. 465

8.3.9.5.2.4 8.3.9.5.2.5

Activating PrPRNC for RNC resiliency ......................................467 Configuring secure RNC-cl O&M interface................................ 469

8.3.9.5.2.6 8.3.9.5.2.7

Synchronizing RNCSRV.............................................................472 Configuring associations to the core network............................ 476

8.3.9.5.2.8 8.3.9.5.2.9 8.3.9.5.2.10

Configuring Iur interface towards neighboring RNCs.................480 Planning Iupc interface configuration......................................... 481 Planning Iu-BC interface configuration for RNC2600 BkPRNC. 482

©2016Nokia

13


14

8.3.9.5.2.11 8.3.9.5.2.12 8.3.9.5.2.13 8.3.9.5.2.14

Committing changes and backup con figuration test.................. 482 Reconfiguring BTS for Network Resili ency................................ 483 Configuring RNCSRV.................................................................483 IP addresses mapping............................................................... 487

8.3.9.5.2.15 8.3.9.5.2.16 8.3.9.5.3

Auto-adaptation in RNC2600..................................................... 488 Testing IP connectivity (optional)................................................489 Operating and Maintaining RAN2512 : Network Resiliency for RNC2600................................................................................... 491

8.3.9.5.3.1 8.3.9.5.3.2 8.3.9.5.3.3 8.3.9.5.3.4 8.3.9.5.3.5 8.3.9.5.3.6 8.3.9.5.3.7 8.3.9.5.3.8 8.3.9.6 8.3.9.7

Operating and Maintaining overview.......................................... 491 NetAct topology view..................................................................492 Managing Software.................................................................... 493 Updating SW builds on BkPRNC............................................... 495 Synchronizing.............................................................................497 Maintaining IP connectivity ........................................................498 Interpreting of the system logs................................................... 499 Network Resiliency operations...................................................502 Verifying RAN2512: Network Resilien cy for RNC2600.............. 514 Deactivating RAN2512: Network Res iliency for RNC2600........ 515

8.3.9.8 8.3.9.8.1 8.3.9.8.2

Testing RAN2512: Network Resilienc y for RNC2600.................516 Setup the Network Resiliency for RN C...................................... 517 Normal redundancy switch from PrPR NC to BkPRNC.............. 526

8.3.9.8.3

Redundancy switchback from BkPRN C to PrPRNC.................. 527

9 9.1 9.1.1 9.1.2

BTS solution features................................................................. 529 RAN3308: Flexi RFM 3T6R 2100 (FRGX)................................. 529 RAN3308 Benefits...................................................................... 529 RAN3308 Functional description................................................ 529

9.1.3 9.1.4 9.2 9.2.1

RAN3308 System impact........................................................... 529 RAN3308 Reference data.......................................................... 530 RAN3158: Flexi RFM 6T6R 2100 (FRGU) ................................530 RAN3158 Benefits...................................................................... 531

9.2.2 9.2.3 9.2.4 9.3

RAN3158 Functional description................................................ 531 RAN3158 System impact........................................................... 531 RAN3158 Reference data.......................................................... 532 RAN3246: Flexi RRH 2T2R 850 120W (FRCG)........................ 532

9.3.1 9.3.2 9.3.3 9.3.4

RAN3246 Benefits......................................................................533 RAN3246 Functional description................................................533 RAN3246 System impact........................................................... 533 RAN3246 Reference data.......................................................... 533

9.4 9.4.1 9.4.2 9.4.3

RAN3103: Flexi RRH 4T4R 1900 (FHFB)..................................534 RAN3103 Benefits......................................................................534 RAN3103 Functional description................................................535 RAN3103 System impact........................................................... 535

9.4.4 9.5 9.5.1

RAN3103 Reference data.......................................................... 535 RAN3324: FRIJ AirScale RRH 4T4R B66 160 W...................... 536 RAN3324 Benefits......................................................................536

©2016Nokia

DN09203161Issue:02


9.5.2 9.5.3 9.5.4 9.6

RAN3324 Functional description................................................537 RAN3324 System impact........................................................... 537 RAN3324 Reference data.......................................................... 538 RAN3237: HSUPA Scheduler Capacity Increase for FSMF.......538

9.6.1 9.6.2 9.6.3 9.6.4

RAN3237 Benefits......................................................................539 RAN3237 Functional description................................................539 RAN3237 System impact........................................................... 539 RAN3237 Reference data.......................................................... 539

9.6.5

9.8.1 9.8.2 9.8.3

Testing RAN3237: HSUPA Scheduler capacity increase for FSMF. 540 RAN2249: Support for Multi-Antenna RET Device.................... 541 RAN2249 Benefits......................................................................541 RAN2249 Functional description................................................541 RAN2249 System impact........................................................... 542 RAN2249 Reference data.......................................................... 542 RAN3238: WCDMA BTS Support for Harmonized MHA Family...... 543 RAN3238 Benefits...................................................................... 543 RAN3238 Functional description................................................544 RAN3238 System impact........................................................... 544

9.8.4

RAN3238 Reference data.......................................................... 545

9.7 9.7.1 9.7.2 9.7.3 9.7.4 9.8

DN09203161Issue:02

©2016Nokia

15


List of Figures

16

Figure 1

Example of values of the M5005C58 counter obtained during Phase 2 of RAN3045 testing............................................................................ 38

Figure 2

Example of values of the M5005C59 cou nter obtained during Phase 2 of RAN3045 testing............................................................................ 39

Figure 3

Example of values of the M5005C60 cou nter obtained during Phase 2 of RAN3045 testing............................................................................ 39

Figure 4 Figure 5

HSUPA settings................................................................................ 100 Overview of the RAN2892: WCDMA-LTE Load Balancing feature in Nokia-based radio network...............................................................143

Figure 6

Signaling of RIM UTRA SI procedure............................................... 152

Figure 7

Signaling of RIM UTRA SI Procedure Err or..................................... 153

Figure 8

The IMEI collection and feature operation concept.......................... 161

Figure 9

mcRNC SFP ports............................................................................ 174

Figure 10

OSPF site solution............................................................................ 177

Figure 11

Add/Delete configurator model......................................................... 186

Figure 12

Send parameters options in BTSSM................................................ 187

Figure 13

OSPF with BFD in BTSSM............................................................... 188

Figure 14

Local IP address............................................................................... 188

Figure 15

RFI and PIM testing in commissioning BTS settings........................ 211

Figure 16

RF Monitoring................................................................................... 212

Figure 17

RF-scan visualization....................................................................... 214

Figure 18

PIM desensitization visualization......................................................215

Figure 19

RF monitoring in BTSSM.................................................................. 217

Figure 20

RF-scanning measurement result for Raw Composite Rx or Composite Rx................................................................................... 218

Figure 21

RF-scanning measurement result for Car rier Rx..............................219

Figure 22

PIM simulation test result................................................................. 221

Figure 23

PIM desensitization test result..........................................................223

Figure 24

Configuration management selection window..................................241

Figure 25

High level overview of the HIT base Fishing macro in mcRNC16.... 243

Figure 26

Frequency modification workflow..................................................... 247

Figure 27

NetAct CM Editor view in modifying UARFCN ................................ 251

Figure 28

RUEM Log File Format.....................................................................258

Figure 29 Figure 30

SIEM system GUI.............................................................................258 Overview of RAN2973: IMSI-based Call Monitoring.........................269

Figure 31

User Plane monitored data on Iu-PS interface.................................270

Figure 32

End-to end IPv4 packet TCP/UDP/ICMP......................................... 270

Figure 33

User Plane monitored data on Iu-CS interface.................................270

Figure 34

User Plane monitored data on Iub interface for PS and CS calls.....271

Figure 35

Transport Plane monitored data on Iu-PS interface......................... 271

©2016Nokia

DN09203161Issue:02


DN09203161Issue:02

Figure 36

Transport Plane monitored data on Iu-CS interface (RTP) (1 of 2) . 271

Figure 37


Figure 38

Transport Plane monitored data on Iub in terface............................. 271

Figure 39

Site solution deployment for IPA-RNC..............................................277

Figure 40

IP interfaces between units in the IPA-RNC..................................... 278

Figure 41

Site solution deployment for mcRNC................................................ 281

Figure 42

Overview of RAN2930: IMSI-based Call Monitoring.........................294

Figure 43

User Plane monitored data on Iu-PS interface................................. 295

Figure 44

End-to end IPv4 packet TCP/UDP/ICMP......................................... 296

Figure 45

User Plane monitored data on Iu-CS interface.................................296

Figure 46

User Plane monitored data on Iub interface for PS and CS calls.....296

Figure 47

Transport Plane monitored data on Iu-PS interface......................... 296

Figure 48


Figure 49


Figure 50

Transport Plane monitored data on Iub in terface............................. 297

Figure 51

Site solution deployment for IPA-RNC..............................................303

Figure 52

IP interfaces between units in the IPA-RNC..................................... 303

Figure 53

Site solution deployment for mcRNC................................................ 307

Figure 54

Monitor VSWR dialog box................................................................ 329

Figure 55

Antenna line supervision in use parameter set.................................332

Figure 56 Figure 57

External alarm interface....................................................................336 Connecting external alarm inputs..................................................... 336

Figure 58

Connecting external alarm inputs..................................................... 337

Figure 59

RNW Measurement report for RNC Capacity usage........................349

Figure 60

Network resiliency transport network concept..................................352

Figure 61

Activity model................................................................................... 367

Figure 62

Normal redundancy switch............................................................... 368

Figure 63

Forced redundancy switch................................................................369

Figure 64

Changing any RNCSRV to RNCSRV-Z at BkPRNC.........................370

Figure 65

Redundancy Switchback.................................................................. 371

Figure 66

System recovery from redundancy conflict.......................................372

Figure 67

RNC Resiliency menu for BkPRNC..................................................375

Figure 68

RNC Resiliency menu for PrPRNC.................................................. 375

Figure 69

Settings panel...................................................................................376

Figure 70

Show RNW Topology context menu.................................................377

Figure 71

PrPRNC icon.................................................................................... 381

Figure 72

BkPRNC icon....................................................................................381

Figure 73

PrPRNC icon.................................................................................... 381

Figure 74

BkPRNC icon....................................................................................381

Figure 75

Network transport plan..................................................................... 386

©2016Nokia

17


18

Figure 76

Example view of BkPRNC managed object visible in OMS GUI...... 432

Figure 77

Network resiliency transport network concept..................................451

Figure 78

PrPRNC icon.................................................................................... 452

Figure 79

BkPRNC icon....................................................................................452

Figure 80

Network transport plan..................................................................... 461

Figure 81

Example view of BkPRNC managed object visible in OMS GUI...... 464

Figure 82

RNC and PRNC objects in Topology Browser of OMS GUI............. 469

Figure 83

RNCSRV configuration..................................................................... 484

Figure 84

Phases of SW update.......................................................................496

Figure 85

Activity model................................................................................... 502

Figure 86

Normal redundancy switch............................................................... 504

Figure 87

Forced redundancy switch................................................................505

Figure 88

Changing any RNCSRV to RNCSRV-Z at BkPRNC.........................506

Figure 89

Redundancy Switchback.................................................................. 507

Figure 90

System recovery from redundancy conflict.......................................508

©2016Nokia

DN09203161Issue:02


List of Tables

DN09203161Issue:02

Table 1

RAN3045 hardware and software require ments................................ 32

Table 2

New counters introduced by RAN3045.............................................. 32

Table 3

Existing counters related to RAN3045................................................ 32

Table 4

New parameters introduced by RAN304 5.......................................... 33

Table 5

RAN3045 Sales information............................................................... 33

Table 6 Table 7

RAN3043 hardware and software require ments................................ 41 New counters introduced by RAN3043.............................................. 41

Table 8

Existing counters related to RAN3043................................................41

Table 9

New parameters introduced by RAN304 3.......................................... 41

Table 10


Table 11

RAN3218 hardware and software requirements................................ 47

Table 12


Table 13


Table 14

New parameters introduced by RAN3218.......................................... 48

Table 15

Parameters modified by RAN3218..................................................... 48

Table 16

RAN3218 sales information................................................................ 48

Table 17

RAN3093 hardware and software requirements................................ 54

Table 18


Table 19


Table 20


Table 21


Table 22

Existing parameters related to RAN3093 ........................................... 56

Table 23


Table 24

RAN2518 hardware and software require ments................................ 90

Table 25

Alarms modified by RAN2518............................................................ 90

Table 26


Table 27

Existing counters related to RAN2518................................................91

Table 28


Table 29


Table 30

Existing parameters related to RAN2518........................................... 92

Table 31


Table 32

RAN2869 hardware and software requirements.............................. 103

Table 33

New counters introduced by RAN2869............................................ 103

Table 34

Existing counters related to RAN2869..............................................104

Table 35

New parameters introduced by RAN2869........................................ 104

Table 36

Existing parameters related to RAN2869......................................... 104

Table 37

New PRFILE parameters introduced by RAN2869.......................... 104

Table 38

RAN2869 Sales information............................................................. 104

©2016Nokia

19


Table 39

20

RAN3046 hardware and software requirements...............................110

Table 40

Existing counters related to RAN3046.............................................. 111

Table 41

Existing key performance indicators relat ed to RAN3046.................111

Table 42

RAN3046 sales information.............................................................. 112

Table 43

RAN3040 hardware and software require ments...............................115

Table 44

New faults introduced by RAN3040.................................................. 116

Table 45

New counters introduced by RAN3040.............................................116

Table 46

New parameters introduced by RAN3040 ........................................ 116

Table 47


Table 48


Table 49


Table 50

New parameters introduced by RAN3235 ........................................ 123

Table 51

Parameters modified by RAN3235...................................................123

Table 52


Table 53

Available preamble signature combinations..................................... 128

Table 54


Table 55

Existing alarms related to RAN2902................................................. 130

Table 56


Table 57


Table 58

Parameters modified by RAN2902................................................... 131

Table 59 Table 60

RAN2902 sales information.............................................................. 131 RAN2892 hardware and software requirements.............................. 144

Table 61


Table 62


Table 63


Table 64

Parameters modified by RAN2892................................................... 146

Table 65

RAN2892 sales information.............................................................. 146

Table 66


Table 67


Table 68


Table 69

PRFILE parameters related to RAN3086......................................... 155

Table 70


Table 71


Table 72


Table 73


Table 74


Table 75


Table 76

RAN3112 hardware and software requirements...............................175

Table 77

New counters introduced by RAN3112.............................................175

Table 78


©2016Nokia

DN09203161Issue:02


DN09203161Issue:02

Table 79

RAN3193 hardware and software require ments.............................. 178

Table 80


Table 81


Table 82


Table 83


Table 84


Table 85


Table 86


Table 87

Alarms.............................................................................................. 192

Table 88

Parameters....................................................................................... 192

Table 89


Table 90


Table 91


Table 92

Parameters used for activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networksfeature................................ 202

Table 93


Table 94

New parameters introduced by RAN306 0........................................ 209

Table 95


Table 96

RAN2872 hardware and software requir ements.............................. 225

Table 97

Existing alarms related to RAN2872.................................................226

Table 98

Existing OMS LDAP parameters related to RAN2872......................226

Table 99


Table 100


Table 101


Table 102


Table 103


Table 104


Table 105


Table 106


Table 107


Table 108


Table 109

New alarms introduced by RAN2268............................................... 254

Table 110


Table 111


Table 112


Table 113


Table 114


Table 115

Ciphers in priority..............................................................................261

Table 116


Table 117


©2016Nokia

21


Table 118

22


Table 119


Table 120


Table 121

RAN2973 Software requirements..................................................... 272

Table 122

External monitoring tool requirements..............................................273

Table 123

Maximum number of calls that be monitor ed based on RNC and monitoring configuration................................................................... 274

Table 124 Table 125

RAN2973 Sales information............................................................. 274 Licenses for RAN2973: IMSI-based Monitoring............................... 275

Table 126

Licenses for RAN2973: IMSI-based Monitoring............................... 283

Table 127

RAN2973 symptoms and recovery actions...................................... 289

Table 128

Overload control............................................................................... 298

Table 129

Software requirements..................................................................... 298

Table 130

External monitoring tool requirements..............................................299

Table 131

Sales information.............................................................................. 300

Table 132


Table 133


Table 134

RAN2930 symptoms and recovery actions...................................... 318

Table 135


Table 136


Table 137

Existing counters related to RAN3104..............................................321

Table 138


Table 139


Table 140


Table 141


Table 142


Table 143


Table 144


Table 145

External Input .................................................................................. 333

Table 146


Table 147


Table 148

External alarm pin mapping..............................................................337

Table 149

External Input .................................................................................. 339

Table 150

Signaling capacity license................................................................ 344

Table 151


Table 152

New alarms introduced by RAN3057............................................... 347

Table 153

Existing alarms modified by RAN3057............................................. 347

Table 154


Table 155

New key performance indicators introduced by RAN3057...............347

Table 156

New parameters introduced by RAN3057........................................347

©2016Nokia

DN09203161Issue:02


DN09203161Issue:02

Table 157


Table 158

Backup capacity step matrix............................................................. 350

Table 159

Required number of SCTP associations in Iu and Iu-PC compared to a basic situation without network resiliency .....................................356

Table 160

Required number of SCTP associations in Iur compared to a basic situation without network resiliency.................................................. 356

Table 161

Supported IP mapping relationships.................................................357

Table 162

Resilient operation exclusion principle ............................................ 360

Table 163

Resiliency operations impact on BPS operations.............................361

Table 164

Forbidden switch cases.................................................................... 363

Table 165

RNC Resiliency Logs........................................................................364

Table 166

Use cases......................................................................................... 367

Table 167

RNC Resiliency operations menu.....................................................375

Table 168

Descriptions of feature-related terms .............................................. 377

Table 169

Limitations........................................................................................ 380

Table 170


Table 171

New alarms.......................................................................................382

Table 172

Related existing alarms.................................................................... 382

Table 173


Table 174


Table 175

BTS Parameters............................................................................... 385

Table 176


Table 177

Warning prompts ............................................................................. 395

Table 178

Error prompts ...................................................................................396

Table 179

Error prompts ...................................................................................397

Table 180

MSC configuration ........................................................................... 411

Table 181

SGSN configuration ......................................................................... 414

Table 182

BTS configuration values..................................................................434

Table 183

Software requirements..................................................................... 453

Table 184

New alarms introduced in RAN2512................................................ 453

Table 185

Existing alarms related to RAN2512.................................................454

Table 186


Table 187


Table 188

BTS Parameters...............................................................................456

Table 189 Table 190

Sales information.............................................................................. 456 Descriptions of feature-related terms .............................................. 457

Table 191

Limitations........................................................................................ 459

Table 192

Configuration matrix......................................................................... 477

Table 193

BTS configuration values..................................................................483

Table 194

Configuration list BkPRNC............................................................... 484

Table 195


©2016Nokia

23


24

Table 196

BPS operation mutual exclusion.......................................................494

Table 197

Resilient operation mutual exclusion................................................ 494

Table 198

RNC Resiliency Logs........................................................................500

Table 199

Use cases.........................................................................................503

Table 200


Table 201


Table 202


Table 203


Table 204


Table 205


Table 206


Table 207


Table 208


Table 209


Table 210


Table 211


Table 212


Table 213


Table 214


Table 215


Table 216 Table 217

MHAs in harmonized MHA family..................................................... 544 RAN3238 hardware and software requirements.............................. 545

Table 218

New BTS faults introduced by RAN3238: WCDMA BTS Support for Harmonized MHA Family..................................................................545

Table 219

Modified parameters......................................................................... 545

Table 220


©2016Nokia

DN09203161Issue:02


Summary of changes

Summary of changes

g

Flexi Lite’s features are planned separately. Please contact HetRAN Product Management for further information. Note:

Changes between issues 01H (2016-07-11, WCDMA 16) and 02 (2016-07-15, WCDMA 17)

RAN2991: Modification of WCDMA Frequency • •

RAN2991 Functional description has been updated. Step1 in Testing RAN2991 has been updated.

RAN3005: Network Resiliency for mcRNC • • • • •

Miscellaneous notes has been updated. RAN3005 System impact has been updated. BkPRNC-related alarms in Net Act has been removed. NetAct topology view has been added. Create BkPRNC object at PrPRNC (mcRNC) has been updated.

Changes between issues 01G (2016-06-13, WCDMA 16) and 01H (2016-07-11, WCDMA 16) RAN3046: Interference Cancellation for 4Rxhas been added. Changes between issues 01F (2016-04-12, WCDMA 16) and 01G (2016-06-13, WCDMA 16) RAN2504: Configurable Service Accounts has been added.

RAN3086: CSFB with RIM •

002:2306 CSFB_WITH_RIM PRFILE parameter has been added toRAN3086

Reference data.

RAN2991: Modification of WCDMA Frequency •

RAN2991 Functional description has been updated.

•

Step1 in Testing RAN2991 has been updated.

RAN3057: mcRNC Signaling Capacity License • •

RAN3057 Functional description has been updated. Alarm 3295 licence_capacity_exceeded_ahas been added toRAN3057 Reference data.

RAN3324: Flexi RRH 4-pipe 1700/2100 160W

DN09203161Issue:02

©2016Nokia

25

Summary of changes


• • •

26

RAN3324 Benefits has been updated. RAN3324 Functional description has been updated. RAN3324 Reference data has been updated.

©2016Nokia

DN09203161Issue:02


Introduction to WCDMA 16 features

1 Introduction to WCDMA 16 features This document provides feature descriptions and instructions for the WCDMA 16 release. Note that the subchapter Interdependencies between features lists only dependencies among Nokia RAN WCDMA features. If the feature has no specific hardware requirements, it means that only WCDMA System Module must be used.

g

DN09203161Issue:02

Note: WCDMA 16 is supported by NetAct 16.2 and NetAct 15.5 + INES PP337. For INES support, seeWCDMA 16 Basic Support with NetAct 15.5 + INES PP337 .

©2016Nokia

27

WCDMA 16 Basic Support with NetAct 15.5 + INES PP337


2 WCDMA 16 Basic Support with NetAct 15.5 + INES PP337 INES (Instant Network Element Support) with NetAct 15.5 + PP337 provides basic NetAct management support and compatibility with WCDMA 16. No NetAct SW upgrade is needed, only OSS metadata and configurations for WCDMA 16 are updated to NetAct. INES support in PP337 includes: •

•

WCDMA 16 level Fault Management (FM) and Configuration Management(CM) metadata to be used by NetAct Monitor and Configurator, and FM and CM Northbound Interfaces. Compatibility for several NetAct applications, forexample, NetAct SW Manager.

INES support in PP337 does NOT include: •

•

WCDMA 16 level Performance Management (PM) metadata (new KPIs, measurements, or counters) to be used by NetAct Performance Manager and PM NBI. The new PM data is visible via OMS applications. Any advanced features like 3G Rehosting or WCDMA Frequency Modification.

Recommendations and workarounds: •

Site Rehosting –

•

Performance Management - counters/KPIs – –

•

Rehosting should be donewith the RU50 or RU50 EP1 level SW if BTS rehosting between RNCs is needed.

New counters introducedin WCDMA 16 are visible in OMS. Reports with the new counters can be created with OMS tools.

Documentation of WCDMA 16 alarms, parameters, and counters –

Complete documentation ofthe new or modified alarms, parameters, and counters can be found in the WCDMA 16 operating documentation.

Features supported by INES PP337: •

Radio resource management and Telecom features –

RAN3045: Activity BasedUL Power Control for Rel99 DCH

–

RAN3043: Advanced HSUPA Time Division Scheduling RAN3218: Enhanced CellChange from HSPA to 2G

– – – – – – – –

28

RAN3093: Enhanced MBLB RAN2518: High Speed Cell_FACH Enhanced RAN2869: HSPA Subscriber Increase RAN3040: IRC Receiver RAN3235: Optimized Packet Handling at RNC RAN2902: RACH capacity increase RAN2892: WCDMA-LTE Load Balancing

©2016Nokia

DN09203161Issue:02


– – •

–

RAN3112: mcRNC Integrated Ethernet Switching RAN3193: OSPF Authentication for Controller

Operability features – – – – – – – – –

•

RAN3086: CSFB with RIM RAN3082: Device Detection

Transmission and transport features –

•


RAN2367: DNS Support for Certificate Examination RAN3247: Energy Efficiency ShutDown Mode with RF Sharing RAN2973: Enhanced IMSI Based Call Monitoring RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing RAN2872: IPA-RNC Symptom Report RAN3150: mcRNC Event Based Symptom Data Collection RAN2268: Multi-Layer Certificate Authorities RAN3096: OMS HP Gen9 HW RAN2571: Support of TLS 1.2

Performance monitoring features

g

Note: PM counter management via OMS16. NetAct 16.2 required for NetAct management support. – – – – •

RAN2862: Multi-RAB Dedicated Counter Set RAN2304: VSWR Monitoring

RNC solution features – – –

•

RAN2164: Compensated CQI Measurement RAN3104: HSPA User Amount Monitoring

RAN2624: External Alarm Input Support of mcRNC RAN3057: mcRNC Signaling Capacity License RAN3005: Network Resiliency for mcRNC

BTS solution features – – – – – – – –

RAN3308: Flexi RFM 3T6R 2100 (FRGX) RAN3158: Flexi FRM 6T6R 2100 (FRGU) RAN3246: RAN3103: RAN3324: RAN3237: RAN2249: RAN3238:

Flexi RRH 2T2R 850 120W (FRCG) Flexi RRH 4T4R 1900 (FHFB) Flexi RRH 4-pipe 1700/2100 160W HSUPA Scheduler Capacity Increasefor FSMF Support for Multi-Antenna RET Device WCDMA BTS Support for Harmonized MHA Family

Features not supported by INES PP337: •

Operability features (NetAct 16.2 required) –

DN09203161Issue:02

RAN3242: Category for Obsolete Parameters

©2016Nokia

29


–

RAN2706: Delta Configuration and Change Notifications forBTS Transport RAN3063: KPI Reporting Based on Cell Type RAN2991: Modification of WCDMA Frequency

–

RAN2702: Parameter Level Logging of BTS User Events

– –

30


©2016Nokia

DN09203161Issue:02


Radio resource management features

3 Radio resource management features 3.1 RAN3045: Activity Based UL Power Control for Rel99 DCH Introduction to the feature With the RAN3045: Activity Based UL Power Control for Rel99 DCHfeature, when a UE is in CELL_DCH state using R99 DCH in uplink (UL) and no data needs to be sent at the moment, its transmission power is lowered to minimum. Thus, the uplink interference from the R99 DCH UL control channel is reduced.

3.1.1

RAN3045 Benefits End-user benefits In case of HSPA cell with R99 UEs, end user benefits from improved HSPA throughput. In case of a R99 cell, more users can be accepted to the cell. Operator benefits Operator benefits from reduced uplink interference (coming from Rel99 UE L1 control channel when there is no data to be sent) and improved HSPA cell throughput. The feature significantly improves the cell capacity when the dominating traffic is in discontinuous or burst patterns, for example, AMR calls.

3.1.2

RAN3045 Functional description In the current implementation, when a UE is in a CELL_DCH state using R99 DCH, it does not have control channel gating, that means, signaling over uplink control channel DPCCH continues even if there is no UL data to be sent. With the RAN3045: Activity Based UL Power Control for Rel99 DCHfeature, BTS detects the uplink data channel inactivity and commands a UE to reduce transmitting power of the UL DPCCH control channel, when UL data channel is inactive. Thus, the UL interference from R99 DCH UEs is reduced, and cell HSPA data capacity increases.

g

Note: The activity based power control is not used when UL TFCI number is greater than 16 or when a UE is in a compressed mode. This feature can work together withRAN3040: IRC Receiver and RAN1308: HSUPA Interference Cancellation Receiverfeatures, which also reduce UL interference.

3.1.3

RAN3045 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools.

DN09203161Issue:02

©2016Nokia

31



Impact on system performance and capacity With this feature, uplink interference from R99 DCH UE uplink control channel is reduced. It also provides higher HSPA data cell throughput. With this feature, the cell capacity gain for PA3 channel is up to 5% for voice and PS64 services (assuming 50% activity).

3.1.4

RAN3045 Reference data Requirements Table 1

RAN3045 hardware and software requirements

RAS

I PA - R N C

mc R N C

WCDMA 16

Support not required


OMS

NetAct


NetAct 16.2

MS C


Flexi Multiradio BTS

WBTS16

S GSN


Flexi Flexi Lite Multiradio 10 BTS BTS

WBTS16

MGW


Under planning UE


This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms There are no alarms related to this feature. Measurements and counters Table 2

New counters introduced by RAN3045

C o u n t e rI D

C o u n t e rn a me

M eas u re me n t

M5005C58

SUM OF R99 USERS

HSPA in WBTS Extension

M5005C59

SUM OF ABPC USERS


M5005C60

R99 AND ABPC USERS DENOMINATOR

Table 3


Existing counters related to RAN3045

C o u n t e rI D

C o u n t e rn a me

M1000C320÷M 1000C341

RECEIVED TOTAL WIDEBAND POWER CLASS 0÷RECEIVED TOTAL WIDEBAND POWER CLASS 21

Cell Resource

M eas u re me n t

M5000C151

HSUPA MINIMUM MAC-D THROUGHPUT

HSPA in WBTS

M5000C152

HSUPA MAXIMUM MAC-D THROUGHPUT HSPA in WBTS

M5000C153

HSUPA AVERAGE MAC-D THROUGHPUT HSPA in WBTS

Key performance indicators There are no key performance indicators related to this feature. Parameters

32

©2016Nokia

DN09203161Issue:02


Table 4


New parameters introduced by RAN3045 F u l ln a m e

A b b r e v i at e dn a m e

Activity based UL power control for Rel99 DCH enabled

activityBasedULPowCtr lEnabled

M a n a g e do b j e c t

BTSSCW

Commands There are no commands related to this feature. Sales information Table 5

RAN3045 Sales information

B SW/AS W

ASW

3.1.5

S W c o mp o n e n t

RAN

L i c e n s e c o n t r o l i n n e t w o r k e l e me n t

BTS LK

Activating RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to activate this feature. Before you start Restart of the RNC or the BTS is not required after the activation of this feature. This procedure does not cause downtime and it can be activated at any time of the day. Make sure you have access to the following applications: •

BTS Site Manager

The RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is controlled by a license and requires a valid license file. The feature code for this feature is 5578. Make sure you have the license file installed and the license state is 'Valid'.

DN09203161Issue:02

©2016Nokia

33



Procedure

1

Open BTS Site Manager and establish a connection to the BTS.

2

From the menu on the left-hand side, select Commissioning.

3

In Commissioning type, select Reconfiguration, then deselect TRS.

4

Proceed to the BTS Settings page by clicking Next.

5

Select the 'Activity based UL power control for Rel99 DCH' checkbox.

6

Proceed to the Send Parameters page by clicking Next.

7

Click Send parameters.

8

Proceed to the Commissioning Report page by clicking Next, and then click Finish.

Expected outcome The RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is activated.

3.1.6

Verifying RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to verify if the RAN3045: Activity Based UL Power Control for Rel99 DCH feature works properly in the network. Before you start Make sure you have access to the following applications:

34

•

RNW Measurement Management

•

RNW Measurement Presentation

©2016Nokia

DN09203161Issue:02



Procedure

1

Open the RNW Measurement Management application in the Application Launcher.

2

Start the measurement for the M5005C59 SUM OF ABPC USERS counter. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3

Set up one R99 call that meets the following conditions: •

• •

•

Transport format combination indicator (TFCI) number in uplink is less than or equal to 16. This can be checked from the TFCS IE in RADIO LINK SETUP message. There are less than or equal to 16 TFCS instances in the TFCS (UL) IE. TFCI 0 is decoded with good quality. No compressed mode is activated in the UE. This can be checked from the Radio Link Reconfiguration Procedure - no compressed mode configuration and activation in the procedure. The UE is not set up for test purpose (test mode, loop test, and so on).

Note that even if the above conditions are fulfilled, the RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is not used on the R99 UE in case when TFCI = 0 does not correspond to UL data discontinuous transmission (DTX) in UL transport format combination set (TFCS) configuration (although such case is very rare).

4

g

Open the RNW Me asurement Presentation application and check the value of the counter M5005C59. Note: Measurement results are available in the application at the next full hour plus 10 minutes. For example, if you start the measurement at 11:22, the collected data is available in OMS at 12:10.

Expected outcome The value of the M5005C59 counter is a non-zero value between 0 and 36000.

3.1.7

Deactivating RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to deactivate this feature. Before you start Make sure you have an access to the following applications:

DN09203161Issue:02

©2016Nokia

35



BTS Site Manager

•

Procedure

1

Open BTS Site Manager and establish a connection to the BTS.

2


3

In Commissioning type, select Reconfiguration, then deselect TRS.

4


5

Deselect the 'Activity based UL power control for Rel99 DCH' checkbox.

6


7


8


Expected outcome The RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is deactivated.

3.1.8

Testing RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose

g

Note: This is an example of verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks. The purpose of this test case is to verify that the RAN3045: Activity Based UL Power Control for Rel99 DCH feature is working on BTS. The following counters are to be checked: • • •

M5005C58 SUM_NUM_R99_USERS M5005C59 SUM_NUM_ABPC_USERS M5005C60 R99_AND_ABPC_USERS_DENOM

Test environment: • •

36

Operational Radio Access Network and Core Network. FSMr2 or FSMr3 platform

©2016Nokia

DN09203161Issue:02


•


HW configuration: FSME+FSME+2FRGP/2FRGT 20W (F222-x-146-1TX-4RX E Type), FSMF+FRGT (F111)

Before you start Preconditions: • •

• •

3.1.8.1

WBTS has an 'On Air' status Valid license for the RAN3045: Activity Based UL Power Control for Rel99 DCH feature (feature code: 5578) is installed on the BTS. 2-10 cell phones are available for testing. The RAN3045: Activity Based UL Power Control for Rel99 DCHmust be deactivated before you startphase 1 of testing.

Phase 1: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature deactivated Procedure

1

Check values of the co unters M5005C58, M5005C59, and M5005C60 and record them.

2

Set up 2-10 AMR calls, and then mute the UEs to trigger DTX.

3

Release the calls.

4

Check values of the counters M5005C58, M5005C59, and M5005C60, and compare them with the values recorded in step 1.

Expected outcome Values of the counters M5005C58 and M5005C59 are not updated. Value of the M5005C60 counter is updated and different from 0.

DN09203161Issue:02

©2016Nokia

37


3.1.8.2


Phase 2: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature activated Procedure

1

Check values of the co unters M5005C58, M5005C59, and M5005C60 and record them.

2

Activate t he RAN3045: Activity Based UL Power Control for Rel99 DCHfeature. For more information, seeActivating RAN3045: Activity Based UL Power Control for Rel99 DCH.

3

Set up 2-10 AMR calls, and then mute the UEs to trigger DTX.

4

Release the calls.

5

Check values of the counters M5005C58, M5005C59, and M5005C60, and compare them with the values recorded in step 1.

Expected outcome Only with the RAN3045: Activity Based UL Power Control for Rel99 DCH(ABPC) feature activated, values of the counters M5005C58, M5005C59, and M5005C60 are updated and different from 0. Figure 1

38

Example of values of the M5005C58 counter obtained during Phase 2 of RAN3045 testing

©2016Nokia

DN09203161Issue:02



Figure 2


Figure 3


3.2 RAN3043: Advanced HSUPA Time Division Scheduling Introduction to the feature The RAN3043: Advanced HSUPA Time Division Schedulingfeature introduces extension of 2 ms TTI one HARQ scheduling to higher bitrates (one HARQ peak bitrate of 320kbit/s - 1 Mbit/s, or average bitrate of 40-120 kbit/s) to improve HSUPA throughput when there is a medium number of 2 ms TTI UEs in a cell.

3.2.1

RAN3043 Benefits End-user benefits End users benefit from:

DN09203161Issue:02

©2016Nokia

39


•

•


Improved HSUPA throughput for 2 msTTI UEs when there is 8-16 of such UEs in a cell (assuming continuous UL traffic). The number of UEs may be bigger if the UEs generate bursty traffic. Better average RTT timings of the UEs.

Operator benefits This feature provides gain in a cell capacity as a result of reduced UL intra-cell interference thanks to time division scheduling of the users.

3.2.2

RAN3043 Functional description The RAN3043: Advanced HSUPA Time Division Schedulingfeature introduces support for higher average bitrates (between 40 kbit/s and 120 kbit/s) for 2 ms TTI one HARQ scheduling. In current implementation all available HARQ processes are allocated for those bitrates. The 2 ms TTI one HARQ scheduling was introduced in RU20 SW release with the RAN1470: HSUPA 2ms TTIfeature. With RAN3043: Advanced HSUPA Time Division Scheduling feature, this scheduling mechanism is extended to higher bitrates. Thanks to this, the intra-cell interference and E-DPCCH signaling are reduced when there is a medium number of 2 ms UEs in a cell (about 8-16 assuming continuous UL traffic users; this number may be slightly bigger when there are users with UL bursty traffic in a cell).

g

Note: This feature does not affect the scheduling done for the 10 ms UEs (that is, UEs with 10 ms TTI), since 10 ms UEs do not support HARQ-specific scheduling. For 10 ms UEs, always all available HARQ processes are activated. The 2 ms UEs are scheduled with higher bitrates based on various factors, for example, number of UEs in a cell, radio conditions, cell load, QoS parameters, and so on. This means that the cell can have mixed set of UEs (with 2 ms TTI one HARQ with higher bitrate UEs, 2 ms one HARQ with lower bitrate UEs, 2 ms all HARQ UEs, and 10 ms all HARQ UEs) at any point in time. One HARQ allocation with higher throughput is applied only for the scheduled MAC-d flows.

3.2.3

RAN3043 System impact Interdependencies between features The RAN1470: HSUPA 2ms TTI feature is a prerequisite for using this feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity With this feature, the cell capacity gain is expected to be up to 30% (assuming 16 UEs generating continuous UL traffic in PA3 channel conditions). Also, the cell throughput is improved when there is about 8-16 users in a cell. Gain is also possible with slightly higher number of users, when the users have bursty UL traffic.

40

©2016Nokia

DN09203161Issue:02



This feature has no impact on baseband dimensioning.

3.2.4



RAS

I PA - R N C

mc R N C

WCDMA 16



OMS

NetAct


NetAct 16.2

Fl exi Multiradio BTS WBTS16

MS C


S GSN


Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16

Under planning

MGW

UE





C o u n t e rI D M5000C477

C o u n t e rn a me HSUPA USERS WITH 2MS TTI DENOMINATOR

M e as u r e m e n t HSPA in WBTS

M5000C478

HSUPA USERS WITH 10MS TTI DENOMINATOR

HSPA in WBTS

M5000C479

SUM OF HSUPA USERS USING HSPA in WBTS ADVANCED SCHEDULING FOR EACH TTI

M5000C480

HSUPA USER USING ADVANCED SCHEDULING DENOMINATOR

Table 8

HSPA in WBTS


C o u n t e rI D

C o u n t e rn a me

M e as u r e m e n t

M5000C324

SUM OF HSUPA USERS WITH 2MS TTI

HSPA in WBTS

M5000C325


HSPA in WBTS

Key performance indicators There are no key performance indicators related to this feature. Parameters Table 9


A b b r e v i at e dn a m e


Advanced HSUPA Time Division advHSUPATimeDivSchedE BTSSCW Scheduling enabled nabled

DN09203161Issue:02

©2016Nokia

41





BSW/ASW

ASW

3.2.5

S W comp on en t

RAN


BTS LK

Activating RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to activate this feature. Before you start Restart of the RNC or the BTS is not required after the activation of this feature. This procedure does not cause downtime and it can be activated at any time of the day. Make sure you have access to the following applications: •

BTS Site Manager

The RAN3043: Advanced HSUPA Time Division Schedulingfeature is controlled by a license and requires a valid license file. The feature code for this feature is 5498. Make sure you have the license file installed. The license state must be set to ON.

42

©2016Nokia

DN09203161Issue:02



Procedure

1

Open the BTS Site Manager and establish a connection to the BTS.

2


3

In Commissioning type, select Reconfiguration, and then click Next.

4

Proceed to the HSUPA Settings page by clicking Next.

5

Select the 'Advanced HSUPA Time Division Scheduling' checkbox.

6


7


8


Expected outcome The RAN3043: Advanced HSUPA Time Division Schedulingfeature is activated.

3.2.6

Verifying RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to verify if the RAN3043: Advanced HSUPA Time Division Scheduling feature works properly in the network. Before you start Make sure you have access to the following applications:

DN09203161Issue:02

•


•


©2016Nokia

43



Procedure

1


2

Start the measurement for the M5000C479 SUM OF HSUPA USERS USING ADVANCED SCHEDULING FOR EACH TTI and M5000C480 HSUPA USER USING ADVANCED SCHEDULING DENOMINATOR counters. For details on starting the measurements in the RNW Measurement Management application, seeStarting radio network measurementsin Managing and viewing RNC measurements.

g

Note: Advanced HSUPA Time Division Scheduling may be applied immediately or even after a few hours, depending on the number of UEs with 2ms TTI, cell load, traffic profile, and so on. As soon as the RAN3043 scheduling is applied, the counters' values are increased.

3

Open the RNW Me asurement Presentation application and check the value of the M5000C479 and M5000C480 counters. For details on checking the counter values in the RNW Measurement Presentation application, seeViewing and modifying radio network measurement parametersin Managing and viewing RNC measurements.

Expected outcome The M5000C479 and M5000C480 counters' values are increased.

3.2.7

Deactivating RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to deactivate this feature. Before you start Restart of the RNC or the BTS is not required after the deactivation of this feature. Make sure you have an access to the following applications: •

44

BTS Site Manager

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3


4

Proceed to the HSUPA Settings page by clicking Next.

5

Clear the 'Advanced HSUPA Time Division Scheduling' checkbox.

6


7


8


Expected outcome The RAN3043: Advanced HSUPA Time Division Schedulingfeature is deactivated. Further information After deactivating the feature set the feature license state to OFF.

3.3 RAN3218: Enhanced Cell Change from HSPA to 2G Introduction to the feature The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH before the GSM measurements.

g 3.3.1

Note: The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature supports MultiRAB (AMR + HSPA) CM.

RAN3218 Benefits End-user benefits This feature provides higher end-user data capacity since there are more HSPA/HSDPA configurations operated within the network when comparing to R99 DCH.

DN09203161Issue:02

©2016Nokia

45



Operator benefits This feature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH. This means decreased signaling and optimized resource consumption at the moment of measurements. The DCH resource allocations are not needed before the measurements.

3.3.2

RAN3218 Functional description The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH before the GSM measurements. This means that the GSM is measured with or without the compressed mode when the UE has HSPA/HSDPA configuration. When the feature is not activated, then the users are reconfigured to the DCH configuration before the GSM measurements. This feature does not change the triggers and conditions for the inter-system handover and cell change procedures meaning for example handling of different RAB combinations. The use of the feature can be allowed or denied for certain UEs with the Device Detection mechanism. For more information on Device Detection mechanism, see RAN3082: Device Detection.

3.3.3

RAN3218 System impact Interdependencies between features The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature requires the following features: •

RAN1.5009: WCDMA - GSM Inter-System Handover If RAN1.5009 is not enabled, ISHO from WCDMA to GSM cannot be triggered.

•

RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Features RAN3218 and RAN1668 work under the same feature license.

g

Note: The features work under the same feature license. Impact on interfaces This feature impacts interfaces in the following way: •

The CM measurement parameters for GSMare adapted to the HSPA/HSDPA configurations.

Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature impacts system performance and capacity in the following way:

46

©2016Nokia

DN09203161Issue:02


•

3.3.4


The procedure of the inter-system handover isperformed from the HSPA/HSDPA without changing the configuration to the DCH which provides better performance at the moment of the GSM measurements.

RAN3218 Reference data Requirements Table 11 RAS

WCDMA 16

RAN3218 hardware and software requirements I PA - R N C

RNC16

mc R N C

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2

Fl exi Multiradio BTS


MS C


S GSN



Support not required MGW


Support not required UE


This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters Table 12 C o u n t e rI D

C o u n t e rn a m e

Me as u re me n t

M1002C695

ALLOCATION FOR HSPA 2G ISHO COMPRESSED MODE

Traffic

M1002C696

ALLOCATION DURATION FOR HSPA 2G ISHO COMPRESSED MODE

Traffic

M1010C274

ISHO ATTEMPTS TO 2G WITH HSPA COMPRESSED MODE

Inter System Hard Handover

M1010C275

SUCCESSFUL ISHO TO 2G WITH COMPRESSED MODE


Table 13 C o u n t e rI D

DN09203161Issue:02


Existing counters related to RAN3218 C o u n t e rn a m e

Me as u re me n t

M1002C357

REQ FOR COM MODE UL TO INT SYST HHO IN SRNC

Traffic

M1002C358

REQ FOR COM MODE DL TO INT SYST HHO IN SRNC

Traffic

M1002C367

ALLO FOR COM MODE UL TO INT SYS HHO IN SRNC

Traffic

M1002C368

ALLO FOR COM MODE DL TO INT SYS HHO IN SRNC

Traffic

M1002C369

ALLO DURA FOR COM MODE UL TO INT SYS HHO IN SRNC

Traffic

©2016Nokia

47


Table 13


Existing counters related to RAN3218 (Cont.)

C o u n t e rI D

M1002C370


Me as u re me n t

ALLO DURA FOR COM MODE DL TO INT SYS HHO IN SRNC

Traffic


New parameters introduced by RAN3218 F u l ln am e

A b b r e v i a t e dn a me

Transmission Gap Pattern Length for GSM measurements with HSPA/HSDPA

Table 15

M an a g e do b j e c t

RNHSPA

TGPLForHSGSMMeas

Parameters modified by RAN3218 F u l ln am e


BTS support for HSPA CM


WBTS

BTSSupportForHSPACM

Max number of UEs in HSDPA CM due to critical HO

MaxNumberUEHSPACmHO

WCEL

Max number of UEs in HSDPA CM due to NCHO

MaxNumberUEHSPACmNCHO

WCEL

Whitelist features

Whitelist

WDEV

Blacklist features

Blacklist

WDEV


RAN3218 sales information

B S W /A S W

ASW

3.3.5


RAN


RNC LK

Activating RAN3218: Enhanced Cell Change from HSPA to 2G Purpose Follow this procedure to activate the RAN3218: Enhanced Cell Change from HSPA to 2G feature. Before you start After activating this feature, there is no need to restart RNC or BTS. Activation procedure does not require cell-locking and does not cause a down-time in the network.

48

©2016Nokia

DN09203161Issue:02



Activate the licence key and set feature state to ON for the following features: •

RAN1.5009: WCDMA - GSM Inter-System Handover

g

Note: Ensure that in the corresponding FIFILE this feature is enabled. To set the feature state to ON, use the following command: for IPA-RNC: ZWOA:2,747,A;

–

Check feature status: ZWOS:2,747; for mcRNC

–

g •

g

Note: For mcRNC, all FIFLE controlled ASW features are enabled by default. Consequently, for mcRNC those features do not need to be set separately. RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Note: The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature uses the same license as the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handoverfeature. To set the feature state to ON, use the following command: –

for IPA-RNC:

–

for mcRNC:

ZW7M:FEA=4783:ON; set license feature-mgmt code 0000004783 feature-adminstate on

Ensure the GSM configuration exist in 3G.

DN09203161Issue:02

©2016Nokia

49



Procedure

1

Open OMS Element Manager.

2

Go to Topology and expand the ROOT directory.

3

Configure the WBTS object: Sub-steps

a) Go to the WBTS object using the following path: RNC object ► WBTSs folder ► WBTS object

b) Right-click on the WBTS object and select Edit parameters.

c) On the Packet Scheduler tab, set the value of the BTSSupportForHSPACM parameter to HSDPA CM for IFHO, LTE and GSMor HSPA CM for IFHO, LTE and GSM.

g

Note: Activation of HSPA/HSDPA CM for GSM also activates HSPA/HSDPA CM for IFHO and LTE.

Further information To set the transmission gap pattern length, use theTGPLForHSGSMMeas RNHSPA parameter. To set the maximum number of UEs that are simultaneously in a HSDPA compressed mode in the cell due to a non-critical handover measurement, use the MaxNumberUEHSPACmNCHO WCEL parameter. To blacklist or whitelist UEs for this feature, use the parameters of WDEV object (provided by theRAN3082: Device detection feature).

3.3.6

Verifying RAN3218: Enhanced Cell Change from HSPA to 2G Purpose Follow this procedure to verify if the RAN3218: Enhanced Cell Change from HSPA to 2G feature works properly in the network. Before you start Make sure you have access to the following applications:

50

•


•


©2016Nokia

DN09203161Issue:02



Procedure

1

Open the RNW Measurement Management application.

2

Start the M1002 Traffic and M1010 Inter System Hard Handover measurements. Wait for the measurement interval to begin.

g

Note: In case of 15-minute interval, data collection starts every quarter. For example 11:00, 11:15, 11:30, 11:45. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3

In an area with GSM coverage, make a PS call mapped to HSPA or HSDPA services. Keep the service active for 15 minutes. The purpose of this step is to trigger compressed mode measurements of the GSM layer and subsequent handover from WCDMA to GSM.

4

Open the RNW Measurement Presentation application.

5

Check if the values of the following counters have been collected: • • •

M1002C695: ALLOCATION FOR HSPA 2G ISHO COMPRESSED MODE M1010C274: ISHO ATTEMPTS TO 2G WITH HSPA COMPRESSED MODE M1010C275: SUCCESSFUL ISHOTO 2G WITH COMPRESSED MODE

Expected outcome The values of counters M1002C695, M1010C274, and M1010C275 increased.

3.3.7

Deactivating RAN3218: Enhanced Cell Change from HSPA to 2G Purpose Follow this procedure to deactivate theRAN3218: Enhanced Cell Change from HSPA to 2G feature.

DN09203161Issue:02

©2016Nokia

51



Procedure

1


2


3

Configure the WBTS object: Sub-steps

a) Go to the WBTS object using the following path: RNC object ► WBTSs folder ► WBTS object

b) Right-click on the WBTS object and select Edit parameters.

c) On the Packet Scheduler tab, set the BTSSupportForHSPACM parameter to a value other than HSDPA CM for IFHO, LTE and GSMand HSPA CM for IFHO, LTE and GSM.

3.4 RAN3093: Enhanced MBLB Introduction to the feature The RAN3093: Enhanced MBLB feature enhances load balancing, layering during voice call setup, inactivity-triggered layering and mobility-triggered layering functionalities of the RAN2172: Multi-Band Load Balancingfeature. It introduces new counters for monitoring SLHO Load State and HSPA Load State in correlation with MBLB decisions. The enhancements are based on live-network experience.

3.4.1

RAN3093 Benefits End-user benefits The user is directed to the optimal frequency layer, which improves the overall end-user experience. Operator benefits Multi-Band Load Balancing enables the optimal usage of frequencies within a network according to and operator preferences, UE capabilities, network capabilities, loadbalancing balancing possibilities, services. With the RAN3093: Enhanced MBLB feature, load is made more sensitive, radio resource utilization is more efficient, and radio network performance is higher. In general, operator strategies on how to use the frequency layers can be better supported. Operator has greater control over utilization of the frequency layers.

3.4.2

RAN3093 Functional description Enhanced load balancing

52

©2016Nokia

DN09203161Issue:02



Enhanced load balancing enables to use theRAN2172: Multi-Band Load Balancing feature just for balancing HSPA load between the layers (without any preferred layer definitions). It is also possible to prevent useless load balancing actions when the HSPA load level is low. When Enhanced load balancing is enabled, Multi-band load balancing can be done just because of the load balancing reasons if both ot the following conditions are met: • •

HSPA load level of the source cell/layer hasreached a specified threshold. HSPA load difference betweenthe source and target cells/layers exceeds a specified threshold.

Enhanced load balancing and the related load thresholds are controlled by radio network parameters. Enhanced layering during voice call setup - Blind IFHO for the standalone SRB Currently, it is possible to perform Multi-Band Load Balancing (MBLB) layer change for voice calls in RAB setup phase. The RAN3093: Enhanced MBLB feature enables changing preferred layer for CS voice call already in the RRC connection setup phase or when starting CS voice call from CCH state. Less signaling is needed for layering as the correct layer is already known before the RAB setup. Enhanced layering during voice call setup - HSPA load state bypass Currently, MBLB sets theHSPA load state for a cell based on the following indications:

•

downlink power and provided average bit rate (HSDPA) uplink noise rise and provided average bit rate (HSUPA)

• •

maximum number of HSDPA users HSUPA resource status in the BTS

•

If the HSPA load state of cell is set by any of these indications, the MBLB does not consider such a cell as possible target cell for the layer change. This is valid for both CS and PS services. However, as theHSPA load state can only be caused by the HSPA load, it does not necessarily indicate congestion for CS AMR speech RAB. The RAN3093: Enhanced MBLB feature provides an option to bypass theHSPA load state. This is possible for CS AMR speech RAB. Voice calls can be moved by MBLB to a target cell even if the target cell is in HSPA load state. This bypass can be set to ON or OFF. This feature is applicable to any MBLB function, which utilizes the HSPA load state for decision making for the CS AMR speech RAB layering. Such MBLB functions are the MBLB Blind IFHO and the MBLB Mobility HO. Enhanced inactivity-triggered layering without compressed mode measurements Inactivity-triggered layer by change is handover. currently being done by using compressed mode measurements followed a hard When enhanced inactivity-triggered layering is enabled and the radio conditions in the source cell are good enough, the decision on the inactivity-triggered layer change is done without compressed mode measurements. Inactivity-triggered layer change can be prevented completely if the radio conditions in the source cell are bad. and the Enhanced inactivity-triggered layering without compressed mode measurements related thresholds for radio conditions are controlled by radio network parameters.

DN09203161Issue:02

©2016Nokia

53



Enhanced mobility-triggered layering Mobility-triggered layer change is currently being done when the preferred layer definitions change during the active set update (ASU) or serving HS-DSCH cell change (SCC) procedures, or when the UE is detected to moving fast. When Enhanced mobility-triggered layering is enabled, the need for mobility triggered layering is additionally checked after the first RAB setup is completed, and in case of multi-RABs, after the AMR RAB setup is completed. Enhanced mobility triggered layeringis enabled with an radio network parameter. Enhanced inactivity-triggered layering in state transition to CCH state Inactivity-triggered layer change is currently being done by using compressed mode measurements followed by a hard handover. When enhanced inactivity-triggered layering is enabled in the state transition to CCH state, inactivity-triggered layer change is done by state transition instead of hard handover when UE is moving from Cell_DCH to Cell_FACH/PCH or URA_PCH state. Enhanced inactivity-triggered layering in state transition to CCH state is enabled by an radio network parameter. Load counters The new counters bring more visibility to a cell load state. Both Load State and HSPA Load State can be monitored in correlation with MBLB decisions.

3.4.3

RAN3093 System impact Interdependencies between features This feature requires theRAN2172: Multi-Band Load Balancingfeature.

g

Note: The features work under the same license. Impact on interfaces Enhanced layering during voice call setupand Enhanced-inactivity triggered layering reduce NBAP and RRC signaling during layering procedures. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

3.4.4


WCDMA 16

54


RNC16

mc R N C

mcRNC16

©2016Nokia






DN09203161Issue:02


Table 17


RAN3093 hardware and software requirements (Cont.)

OMS

NetAct

WCDMA OMS16

NetAct 16.2

MS C


S GSN


MGW


UE


This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters Table 18


C o u n t e rI D

M1000C409

DN09203161Issue:02

C o u n t e rn a me

SUM OF HSPA LOAD LEVEL SAMPLES


Cell Resource

M1000C410

HSPA LOAD LEVEL DENOMINATOR

Cell Resource

M1000C411

MAX HSPA LOAD LEVEL

Cell Resource

M1000C412

HSPA IN LOAD STATE SAMPLES

M1006C323

SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITH CM

RRC signalling

M1006C324

FAILED LAYER CHANGES IN DCH TO PCH/FACH WITH CM

RRC signalling

M1006C325

SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM

RRC signalling

M1006C326

FAILED LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM

RRC signalling

M1008C308

MBLB BLIND HO ATTEMPTS WITH UE BAND CAPA

Intra System Hard Handover

M1008C309

MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA


M1008C310

MBLB BLIND HO ATTEMPTS WITH RSCP


M1008C311

MBLB BLIND HO ATTEMPTS WITH LOAD


M1008C312

MBLB BLIND HO ATTEMPTS USING HSPA LOAD BYPASS


M1008C313

MBLB IFHO ATTEMPTS USING HSPA LOAD BYPASS


M1008C314

BLOCKED MBLB IFHO DUE SLHO LOAD


M1008C315

BLOCKED MBLB BLHO DUE SLHO LOAD


M1008C316

BLOCKED MBLB IFHO DUE HSPA LOAD


M1008C317

BLOCKED MBLB BLHO DUE HSPA LOAD


M1008C318

SUCCESSFUL MBLB BLIND HO


©2016Nokia

Cell Resource

55


Table 19



C o u n t e rI D

C o u n t e rn a me

M eas u re me n t

M1001C259

RRC CONN SETUP COMPLETED AFTER DIRECTED

Service Level

M1001C260

RRC CONN SETUP COMPLETED AND DIRECTED

Service Level



A b b r e v i a t e dn a m e


MBLBEnhancementsEnabl ed

WCEL

HSPA Load Threshold

HSPALoadThreshold

PFL

HSPA Load Margin

HSPALoadMargin

PFL

MBLB Enhancements Enabled

MBLB due to Inactivity RSCP Threshold

Table 21

FMCI

Parameters modified by RAN3093 F u l ln a m e


Layer Selection Weight of Preferred Layer

Table 22

MBLBInactivityRSCPThr


LaySelWeightPrefLayer PFL

Existing parameters related to RAN3093 F u l ln a m e



Blind HO RSCP threshold

BlindHORSCPThr

HOPI

MBLB in RAB Setup Enabled

MBLBRABSetupEnabled

WCEL

MBLBStateTransEnabled

WCEL

MBLB in Inactivity Enabled

MBLBInactivityEnabled

WCEL

MBLB in Mobility Enabled

MBLBMobilityEnabled

WCEL

MBLB Load Information Distribution

MBLBLoadInfoDistr

WCEL

MBLB in RAB Setup for Multi

MBLBRABSetupMultiRAB

WCEL

MBLB in State Transition Enabled

RAB

Commands There are no commands related to this feature. Sales information

56

©2016Nokia

DN09203161Issue:02


Table 23


B SW/AS W

ASW

3.4.5



RAN


RNC LK

Activating RAN3093: Enhanced MBLB Purpose Follow these procedures to activate the functionalities of RAN3093: Enhanced MBLB feature: • • •

• •

• •

Activating Enhanced load balancing Activating Enhanced layering during voicecall setup - Blind IFHO in RRC setup Activating Enhanced layering during voicecall setup - Blind IFHO for CS voice call from CCH state Activating the MBLB HSPA load state bypass Activating Enhanced inactivity triggered layering without compressed mode measurements Activating Enhanced mobility triggered layering Activating Enhanced inactivity triggered layering i n state transition to CCH state

Before you start

g

Note: After activating this feature, there is no need to restart RNC or BTS. Activating procedure does not require cell-locking. The RAN3093: Enhanced MBLB feature uses the same license as theRAN2172: MultiBand Load Balancing feature. Install the license key for the RAN2172: Multi-Band Load Balancingfeature in the RNC and set the feature state to ON. For more information, see Activating RAN2172: MultiBand Load Balancing. To set the feature state to ON, use the following command: •

for IPA-RNC:

•

for mcRNC:


The RAN2172: Multi-Band Load Balancingfeature is enabled in the cell when it's state is set to ON and one or more of the following WCEL parameters is set to value Enabled:

DN09203161Issue:02

•

MBLBRABSetupEnabled

•

MBLBStateTransEnabled

•

MBLBInactivityEnabled

•

MBLBMobilityEnabled

©2016Nokia

57


3.4.5.1


Activating Enhanced load balancing Purpose Follow this procedure to activate the Enhanced load balancingfunctionality of the RAN3093: Enhanced MBLB feature. Before you start Activate the appropriate phases of the RAN2172: Multi-Band Load Balancingfeature in the cells by setting the parameter value toEnabled in one or more of the following WCEL parameters: •

MBLBRABSetupEnabled defining if Multi-Band Load Balancing is enabled in the

RAB setup phase •

•

•

MBLBStateTransEnabled defining if Multi-Band Load Balancing is enabled in the

state transition to Cell_DCH state. MBLBInactivityEnabled defining if Multi-Band Load Balancing is enabled when inactivity is detected in Cell_DCH state MBLBMobilityEnabled defining if Multi-Band Load Balancing is enabled due to mobility in Cell_DCH state

For more information, seeActivating RAN2172: Multi-Band Load Balancing .

g

Note: The LaySelWeightLoad PFL parameter value must be greater than zero in the PFL objects attached to the appropriate cells before HSPA load is used in the layer selection. Verify that the activation of Multi-Band Load Balancing has been successful for the selected phases. For more information, seeVerifying RAN2172: Multi-Band Load Balancing.

58

©2016Nokia

DN09203161Issue:02



Procedure

1

Open the OMS Element Manager.

2


3

Expand the RNC.

4

Configure the PFL object: Sub-steps

a) Right-click on the PFL object and select Edit parameters.

b) For each cell where the enhanced load balancing is activated, configure the following PFL paramaters in the PFL object attached to the cell in question: •

HSPALoadThreshold

•

HSPALoadMargin

Leave the default value or change it according to needs.

5

Expand the RNC object then expand the WCEL object.

6

Configure the WCEL object: Sub-steps

a) Right-click on the WCEL object and select Edit para meters.

b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.

c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced load balancing parameter to True.

7

3.4.5.2

Select Apply to save the changes.

Activating Enhanced layering during voice call setup - Blind IFHO in RRC setup Purpose Follow this procedure to activateEnhanced layering during voice call setup - Blind IFHO in RRC setup functionality of the RAN3093: Enhanced MBLB feature.

DN09203161Issue:02

©2016Nokia

59



Before you start Set the value of the MBLBRABSetupEnabled parameter to Enabled for Blind IFHO in RAB setup phase according to theRAN2172: Multi-Band Load Balancingfeature activation instructions. Procedure

1


2


3


4

Configure the WCEL object. Sub-steps



c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO in RRC setup parameter to True.

5


Further information The following PFL parameters are used by this functionality:

3.4.5.3

•

PrefLayerDCHSDAMR

•

PrefLayerHSPAAMR

•

PrefLayerHSDPAAMR

•

PrefLayerR99AMR

Activating Enhanced layering CS voice call from CCH state during voice call setup - Blind IFHO for Purpose Follow this procedure to activate the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality of the RAN3093: Enhanced MBLB feature.

60

©2016Nokia

DN09203161Issue:02



Before you start In the cells, activate the Blind IFHO in RAB setupand MBLB in RAB Setup for Multi RAB functionalities by configuring the following WCEL parameters: •

•

Set the value of the MBLBRABSetupEnabled parameter to Enabled for Blind IFHO in RAB setup. Set the value of the MBLBRABSetupMultiRAB parameter to eitherEnabled when UE is in Cell_FACH/Cell_PCH stateor Enabled when UE is in Cell_DCH/Cell_FACH/Cell_PCH.

For more information, seeActivating RAN2172: Multi-Band Load Balancing . Verify if the activation of Multi-Band Load BalancingBlind IFHO in RAB setupand MBLB in RAB Setup for Multi RAB has been successful. For more information, seeVerifying RAN2172: Multi-Band Load Balancing. Procedure

1


2


3


4




c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO for CS voice call from CCH states parameter to True.

5

3.4.5.4


Activating MBLB HSPA load state bypass Purpose Follow this procedure to activate the MBLBHSPA load state bypass function of the RAN3093: Enhanced MBLBfeature. This function is possible for AMR CS speech call.

DN09203161Issue:02

©2016Nokia

61



Before you start Enable and configure at least one of theRAN2172: Multi- Band Load Balancingfeature's functions that utilize HSPA load state for decision making, using the following WCEL parameters: •

MBLBRABSetupEnabled

•

MBLBRABSetupMultiRAB

•

–

value: enabled when UE is in Cell_FACH/Cell_PCH state

– –

value: enabled when UE is in Cell_DCH state value: enabled when UE is in Cell_DCH/Cell_FACH/Cell_PCH

MBLBMobilityEnabled

For more information, seeActivating RAN2172: Multi-Band Load Balancing . Procedure

1


2


3


4




c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Bypass of HSPA load state in case of CS voice call parameter to True.

5

3.4.5.5


Activating Enhanced inactivity-triggered layering without compressed mode measurements Purpose Follow this procedure to activate the Enhanced inactivity-triggered layering without compressed mode measurementsfunctionality of the RAN3093: Enhanced MBLB feature.

62

©2016Nokia

DN09203161Issue:02



Before you start Activate the RAN2172: Multi-Band Load Balancingfeature due to inactivity by setting the MBLBInactivityEnabled WCEL parameter value toEnabled. Verify that the activation of Multi-Band Load Balancing due to inactivity has been successful. For more information, seeActivating RAN2172: Multi-Band Load Balancing .

Procedure 1


2


3

Expand the RNC object then expand the FMCI object.

4

Configure the FMCI object. Sub-steps

a) Right-click on the FMCI object and select Edit pa rameters.

b) For each cell where the enhanced inactivity triggered layering without compressed mode measurements is activated, configure the MBLBInactivityRSCPThr parameter. Leave the default value or change it according to needs. • •

5

When the DL channel type is DCH, the FMCI parameter set is defined by the NrtFmciIdentifier WCEL parameter. When the DL channel type is HS-DSCH, the FMCIparameter set is defined by the HSDPAFmciIdentifierWCEL parameter.

Define neighbor cells. For each cell where the enhanced inactivity-triggered layering without compressed mode measurements is activated, define the Intra-RNC inter-frequency neighbor cells that can be target cells for blind inactivity-triggered layering by configuring the BlindHOTargetCell ADJI parameter.

DN09203161Issue:02

©2016Nokia

63



Sub-steps

a) In Topology Tree view, click the WCEL object and go to Adjacencies tab.

b) Select ADJIs tab and click Create.

c) Under Handover Control tab, set the value of the BlindHOTargetCell ADJI parameter to Enabled.

d) Apply the changes.

g

64

Note: Under one WCEL object it is possible to configure only one ADJI-neighbor per frequency. Define the ADJI-neighbor by setting the value of the BlindHOTargetCell ADJI parameter to Enabled.

©2016Nokia

DN09203161Issue:02


6


Configure the HOPI object. Sub-steps

a) Right-click on the HOPI object and select Edit pa rameters.

b) For the Intra-RNC inter-frequency neighbor cells configured in the previous step, configure the BlindHORSCPThr HOPI parameter. Leave the default value or change it according to needs.

7




c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering without CM parameter to True.

8

3.4.5.6


Activating Enhanced mobility triggered layering Purpose Follow this procedure to activate the Enhanced mobility triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature. Before you start Activate the RAN2172: Multi-Band Load Balancingfeature due to mobility by setting the value of the MBLBMobilityEnabled WCEL parameter toEnabled. For more information, seeActivating RAN2172: Multi-Band Load Balancing . Verify that the activation of theRAN2172: Multi-Band Load Balancingfeature due to mobility has been successful. For more information, seeVerifying RAN2172: Multi-Band Load Balancing.

DN09203161Issue:02

©2016Nokia

65



Procedure

1


2


3


4




c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced mobility-triggered layering parameter to True.

5

3.4.5.7


Activating Enhanced inactivity triggered layering in state transition to CCH state Purpose Follow this procedure is to activate the Enhanced inactivity triggered layering in state transition to CCH state functionality of the RAN3093: Enhanced MBLB feature. Before you start Activate the RAN2172: Multi-Band Load Balancingfeature due to inactivity by setting the value of the MBLBInactivityEnabled WCEL parameter toEnabled. For more information, seeActivating RAN2172: Multi-Band Load Balancing . Verify that the activation ofMulti-Band Load Balancingdue to inactivity has been successful. For more information, seeVerifying RAN2172: Multi-Band Load Balancing .

66

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3


4




c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering to CCH states parameter to True.

5

3.4.6 3.4.6.1


Verifying RAN3093: Enhanced MBLB Verifying Enhanced load balancing Purpose Follow this procedure to verify if the Enhanced load balancingfunctionality of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Activate MBLB in the RAB setup phaseby setting the value of the MBLBRABSetupEnabledWCEL parameter toEnabled in the source cell. For more information, seeActivating RAN2172: Multi-Band Load Balancing .

g

Note: Enhanced load balancing functionality can be used in all MBLB phases but it is easier to verify it in RAB setup phase. In the PFL objects attached to the source cell, set the values of the following weighting factors to 0:

DN09203161Issue:02

•

LaySelWeightBand

•

LaySelWeightPrefLayer

•

LaySelWeightRSCP

©2016Nokia

67


g


Note: There is no restriction to use HSPA load, band capability, RSCP and preferred layer definitions together in the layer selection but it is easier to verify the Enhanced load balancingfunctionality when band capability, RSCP and preferred layer definitions are not used in the layer selection. Make sure you have access to the following applications: • •

RNW Measurement Management RNW Measurement Presentation

Procedure

1


2

Start the M1000 CELL RESOURCE and M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15-minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3

Wait until th e measurement int erval sta rts.

4

In the cell where the enhanced load balancing functionality is ac tivated (source cell), make several PS NRT data calls with 5-second intervals .

5

Keep making PS NRT data calls until HSPA load level in the source cell exceeds the threshold determined by theHSPALoadThreshold parameter in the PFL object attached to the source cell. : The HSPA load level can be verified from the counters: • • •

g

68

M1000C409: SUM OF HSPA LOAD LEVEL SAMPLES M1000C410: HSPA LOAD LEVEL DENOMINATOR M1000C411: MAX HSPA LOAD LEVEL Note: Load balancing does not start until the HSPA load level in the source cell exceeds the threshold determined by the HSPALoadThreshold PFL parameter. When the threshold is exceeded, the UE is handed over to a less-loaded cell in the RAB setup phase

©2016Nokia

DN09203161Issue:02



6


7

Check the values of the following counters after the measurement data has been collected: •

M1008C311 MBLB BLIND HO ATTEMPTS WITH LOAD

•

M1008C318: SUCCESSFUL MBLB BLIND HO

For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.

Expected outcome Values of the counters M1008C311 and M1008C318 have been incremented.

g

Note: Counters M1008C311 and M1008C318 are not updated until the HSPA load level in the source cell exceeds the threshold determined by theHSPALoadThreshold PFL parameter. Unexpected outcome Blind handover in RAB setup phase has failed, which is indicated by the value increase of counter M1008C311: MBLB BLIND HO ATTEMPTS WITH LOAD.

3.4.6.2

Verifying Enhanced layering during voice call setup - Blind IFHO in RRC setup Purpose Follow this procedure to verify if the Enhanced layering during voice call setup Blind IFHO in RRC setup function of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Make sure you have access to the following applications: • •

DN09203161Issue:02


©2016Nokia

69



Procedure

1


2

Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3


4

Configure the RAN2172: Multi-Band Load Balancingfeature so that the source cell is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE. For more information, seeActivating RAN2172: Multi-Band Load Balancing .

5

Make an AMR CS s peech RAB call in the source cell.

6


7

Monitor if MBLB moves UE to the target cell by Blind IFHO in RRC setup phase. The M1008C309: MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA counter indicates the Blind IFHO in RRC setup. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.

Expected outcome The AMR CS speech RAB was moved to the target cell by the Blind IFHO in RRC setup phase and value of the counter M1008C309 has been incremented. Unexpected outcome The AMR CS speech RAB was not moved to the target cell by the Blind IFHO in RRC setup phase but the establishment was done in the source cell. Further information This functionality uses the following PFL parameters:

70

•

PrefLayerDCHSDAMR

•

PrefLayerHSPAAMR

•

PrefLayerHSDPAAMR

©2016Nokia

DN09203161Issue:02


•

3.4.6.3


PrefLayerR99AMR

Verifying Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state Purpose Follow this procedure to verify if the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state function of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Ensure the Blind IFHO for CS voice call from CCH state function of the RAN3093: Enhanced MBLB feature is activated and theBlind IFHO in RRC setup function is deactivated. Make sure you have access to the following applications: • •


Procedure

1


2


3

Wait until th e measurement int erval s tarts.

4

Configure the Blind IFHO in RAB setup and MBLB in RAB Setup for Multi RAB functionalities of theRAN2172: Multi-Band Load Balancingfeature so that the source cell is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE. For more information, seeActivating RAN2172: Multi-Band Load Balancing

DN09203161Issue:02

©2016Nokia

71



5

Make a PS NRT data call.

6

Make the PS NRT RAB to s top all data transfer and wait until the inactivity is detected for the UE and the UE is transferred to Cell_FACH/Cell_PCH.

7

Make an AMR CS speech call.

g

Note: To verify the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality, the RSCP value reported by a UE is needed. However, reporting the RSCP value is optional for the UE and it is possbile that UE does not report it.

8


9

Monitor if when the UE is transferred to Cell_DCH state, the UE is a lso moved to the correct layer based on its capabilities (service is always AMR in this case). The M1008C309: MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA counter indicates the Blind IFHO for CS voice call from CCH state. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.

Expected outcome The AMR CS speech RAB was moved to the target cell by the Blind IFHO for CS voice call from CCH state and value of the M1008C309 counter has been incremented. Unexpected outcome The AMR CS speech RAB was not moved to the target cell by the Blind IFHO for CS voice call from CCH state but the establishment was done in the source cell.

3.4.6.4

Verifying the MBLB HSPA load state bypass Purpose Follow this procedure to verify if the MBLB HSPA load state bypassfunction of the RAN3093: Enhanced MBLB feature works properly in the network. This function is possible for AMR CS speech call. Before you start Ensure the MBLB HSPA load state bypassfunctionality of the RAN3093: Enhanced MBLB feature is activated and the Blind IFHO functionality of the RAN2172: Multi-Band Load Balancing feature is activated and configured. Alternatively,Mobility IFHO functionality of the RAN2172: Multi-Band Load Balancingfeature can be used. For more information, see theActivating RAN2172: Multi-Band Load Balancing feature activation.

72

©2016Nokia

DN09203161Issue:02



Make sure you have access to the following applications: • •


Procedure

1

W ith th e RAN2172: Multi-Band Load Balancing feature, configure layer definitions (PFL-Preferred Frequency Layer parameters) sothe thatpreferred the target cell has higher preference score than the source cell. For more information about the MBLB preference score and preferred layer definitions, see the Handover Control Functional Area Description.

2

Arrange HSPA load state in the MBLB target cell. This can be achieved by loading the target cell so that any of the four triggers turns the HSPA load state on in the target cell: • • • •

downlink power and provided average bit rate (HSDPA) uplink noise rise and provided average bit rate (HSUPA) maximum number of HSDPA users HSUPA resource status in the BTS

For example, set the maximum number of HSDPA users to a desired value in the target cell using the MaxNumberHSDPAUsers WCEL parameter. Then, allocate PS NRT HSDPA calls so that the maximum level is reached. For more information aboutHSPA load state, see the Handover Control Functional Area Description.

3


4


DN09203161Issue:02

©2016Nokia

73



5


6

Make an AMR CS speech call in the source cell. Use MBLB Blind IFHO for triggering the layer change.

7


8

Monitor if MBLB moves UE to the target cell irrespective of the HSPA load state. The M1008C312: MBLB BLIND HO ATTEMPTS USING HSPA LOAD BYPASS counter indicates theHSPA load state bypass. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.

Expected outcome The AMR CS speech call is moved to the target cell by the MBLB and the value counters M1008C312 increased. Unexpected outcome The AMR CS speech call is not moved to the target cell by the MBLB but the establishment is done in the srcinal source cell. Further information: The following counters indicate the blocking due to the MBLBHSPA load state. The new feature decreases the blocking of AMR speech call due to MBLB HSPA load state: • •

M1008C316: BLOCKED MBLB IFHO DUE HSPA LOAD M1008C317: BLOCKED MBLB BLHO DUE HSPA LOAD

The following counters indicate the MBLB layer change attempts using the new HSPA load state bypass feature: •

M1008C312: MBLB BLINDHO ATTEMPTS USING HSPA LOAD BYPASS

•

M1008C313: MBLB IFHOATTEMPTS USING HSPA LOAD BYPASS

MBLB layer change attempts using theHSPA load state bypass are visible also in the following MBLB counters: • • • • • •

74

M1008C296: MBLB IFHO ATTEMPTS WITH UE BAND CAPA M1008C297: MBLB IFHOATTEMPTS WITH SERVICE AND UE FEATURE CAPA M1008C298: M1008C299: M1008C308: M1008C309: CAPA

MBLB IFHO ATTEMPTS WITH RSCP MBLB IFHO ATTEMPTS WITH LOAD MBLB BLIND HO ATTEMPTS WITH UE BAND CAPA MBLB BLINDHO ATTEMPTS WITH SERVICE ANDUE FEATURE

©2016Nokia

DN09203161Issue:02


• •


M1008C310: MBLB BLIND HO ATTEMPTS WITH RSCP M1008C311: MBLB BLIND HO ATTEMPTS WITH LOAD

Also increase in the legacy AMR speech call and signaling link HHO DCH request counters can be seen because theHSPA load state bypass allows AMR speech call setup attempt even if the cell is in HSPA load state: • •

M1002C339 Network elementname: DCH HHO REQ FOR SIG LINK IN SRNC M1002C341 Network element name:RT DCH HHO REQ FOR CS VOICE CALL IN SRNC

If the AMR setup fails in the MBLB target cell due to blocking, the re-attempt in the srcinal source cell is made. In this kind of failure scenario, the attempt is seen both in the target cell and the source cell: • •

3.4.6.5

M1002C0 Network elementname: DCH REQ FOR SIG LINK IN SRNC M1002C12 Network element name:RT DCH REQ FOR CS VOICE CALL IN SRNC

Verifying Enhanced inactivity-triggered layering without compressed mode measurements Purpose Follow this procedure to verify if the Enhanced inactivity-triggered layering without compressed mode measurementsfunctionality of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Make sure you have access to the following applications: • •


Procedure

1


2

Start the M1006 RRC SIGNALLING and M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15-minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

DN09203161Issue:02

©2016Nokia

75



3


4

Make a PS NRT data call in the cell where the Enhanced inactivity triggered layering without compressed mode measurementsfunctionality is activated. The call should be made in the cell which is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE.

5

Make the PS NRT RAB to s top all data transfer and wait until the inactivity is detected for the UE.

6

When the PS NRT RAB becomes inactive and if the call is made in the cell where the activation parameters are enabled, the UE is transferred to the correct layer based on its capabilities and allocated RAB combination.

7

Check the value of Enhanced inactivity-triggered layering to CCH states parameter in the MBLBEnhancementsEnabled parameter parent structure.

8


9

Check the values of the following counters after the measurement data has been collected: • • • • • • • • • • • •

M1008C296: MBLB IFHO ATTEMPTS WITH UE BAND CAPA M1008C297: MBLB IFHO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA M1008C298: MBLB IFHO ATTEMPTS WITH RSCP M1008C299: MBLB IFHO ATTEMPTS WITH LOAD M1008C300: SUCCESSFUL MBLB IFHO M1008C308: MBLB BLIND HO ATTEMPTS WITH UE BAND CAPA M1008C309: MBLB BLINDHO ATTEMPTS WITH SERVICE ANDUE FEATURE CAPA M1008C310: MBLB BLIND HO ATTEMPTS WITH RSCP M1008C311: MBLB BLIND HO ATTEMPTS WITH LOAD M1008C318: SUCCESSFUL MBLB BLIND HO M1006C323: SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITH CM M1006C325: SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM

Expected outcome

76

©2016Nokia

DN09203161Issue:02



The proper working of theEnhanced inactivity-triggered layering without compressed mode measurementsfunctionality of the RAN3093 Enhanced MBLB feature is indicated by one of the following outcomes: •

•

The RRC connection is transferredto Cell_FACH/PCH orURA_PCH state in the current layer if the CPICH RSCP measurement result of the source cell is below the threshold defined with theMBLBInactivityRSCPThr FMCI parameter. The values of the above listed counters have not been incremented. The RRC connection is transferredfrom the current layer to the frequency layer which is defined as the for the the UE threshold if the CPICH RSCP measurement result of the source cell preferred is equal toone or above defined with the MBLBInactivityRSCPThr FMCI parameter and below the threshold defined with the BlindHORSCPThr HOPI parameter. –

If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states

–

parameter is set toFalse, one of the counter values: M1008C296, M1008C297, M1008C298, M1008C299 increases in a source WCEL and thus the value of M1008C300 also increases in a handover target WCEL (target cell depends on PFL settings). If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states

parameter is set toTrue, the M1006C323 counter value increases. •

The RRC connection is transferredfrom the current layer to the frequency layer which is defined as the preferred for the UE if the CPICH RSCP measurement result of the source cell is equal to or above the thresholds defined with MBLBInactivityRSCPThr FMCI parameter and BlindHORSCPThr HOPI parameter. –

If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states

–

parameter is set toFalse, one of the counter values: M1008C308, M1008C309, M1008C310, M1008C311 increases in a source WCEL and thus the value of M1008C318 also increases in a handover target WCEL (target cell depends on PFL settings). If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states

parameter is set toTrue, the M1006C325 counter value increases. Unexpected outcome The inter-frequency handover attempt or state transition to the preferred layer has failed. In this case, one of the following counter values are incremented: • • • • •

g

DN09203161Issue:02

M1008C301: M1008C302: M1008C303: M1006C324: M1006C326:

FAILED MBLB IFHO DUE TO UTRAN FAILED MBLB IFHO DUE TO UE NACK FAILED MBLB IFHO DUE TO UE LOST FAILED LAYER CHANGES IN DCH TO PCH/FACH WITH CM FAILED LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM

Note: MBLB blind handover has attempt and success counters but no failure counters.

©2016Nokia

77


3.4.6.6


Verifying Enhanced mobility-triggered layering Purpose Follow this procedure to verify if the Enhanced mobility-triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Set the value of the MBLBRABSetupEnabled WCEL parameter toDisabled.

g

Note: The Enhanced mobility-triggered layeringis not done if Blind IFHO (layering) has been already done in RAB Setup Phase. Make sure you have access to the following applications: • •


Procedure

1


2


3


4

Make an AMR call in the cell where the enhanced mobility-triggered layering functionality is activated. The call should be made in the cell which is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE.

5

The UE is handed over to the correct layer immediately after the AMR RAB setup.

6


7

Check if the val ues of the following counters after the measurement data have been collected: •

78

M1008C296: MBLB IFHO ATTEMPTS WITH UE BAND CAPA

©2016Nokia

DN09203161Issue:02


• • • •


M1008C297: MBLB IFHO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA M1008C298: MBLB IFHO ATTEMPTS WITH RSCP M1008C299: MBLB IFHO ATTEMPTS WITH LOAD M1008C300: SUCCESSFUL MBLB IFHO

For details on using the RNW Measurement see Using. RNW Measurement Presentation in ManagingPresentation and viewing application, RNC measurements

Expected outcome One of the counter values: M1008C296, M1008C297, M1008C298, M1008C299 increases in a source WCEL and thus the value of M1008C300 also increases in a handover target WCEL (target cell depends on PFL settings). The Enhanced mobility-triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature has been activated successfully. Unexpected outcome The inter-frequency handover attempt has failed. The values of the following counters are incremented:

3.4.6.7

•

M1008C301: FAILED MBLB IFHO DUE TO UTRAN

• •

M1008C302: FAILED MBLB IFHO DUE TO UE NACK M1008C303: FAILED MBLB IFHO DUE TO UE LOST

Verifying Enhanced inactivity-triggered layering in state transition to CCH state Purpose Follow this procedure to verify if the Enhanced inactivity-triggered layering in state transition to CCH state functionality of the RAN3093: Enhanced MBLB feature has been successful. Before you start Make sure you have access to the following applications: • •

DN09203161Issue:02


©2016Nokia

79



Procedure

1


2

Start the M1006 RRC SIGNALLING measurement with 15-minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3


4

Make a PS NRT da ta call in the cell where the enhanced inactivity triggered layering in state transition to CCH state functionality is activated. The call should be made in the cell which is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE.

5

Make the PS NRT RAB to s top all data transfer and wait until the inactivity is detected for the UE. When the PS NRT RAB becomes inactive and the call is made in the cell where the activation parameters are enabled, the UE is transferred to the CCH state in the correct layer based on its capabilities and allocated RAB combination.

6

Check the value of Enhanced inactivity-triggered layering without CM parameter in the MBLBEnhancementsEnabled parameter parent structure.

7


8

Check if the values of the following counters have been collected: • •

M1006C323 SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITH CM M1006C325 SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM


Expected outcome The RRC connection is transferred from the current layer to CCH state in the frequency layer defined as the preferred one for the UE, which is indicated by one of the following outcomes:

80

©2016Nokia

DN09203161Issue:02


•

•

•


If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to False, the value of counter M1006C323 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by theMBLBInactivityRSCPThr FCMI parameter and below the threshold defined by theBlindHORSCPThr HOPI parameter, the value of counter M1006C323 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by theMBLBInactivityRSCPThr FCMI parameterand the threshold defined by theBlindHORSCPThr HOPI parameter, the value of counter M1006C325 increases.

Unexpected outcome The state transition to preferred layer has failed. In this case, one of the following counters values are incremented: • •

M1006C324: FAILED LAYER CHANGES IN DCH TO PCH/FACH WITH CM M1006C326: FAILED LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM

If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to False, the value of counter M1006C324 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by the MBLBInactivityRSCPThr FCMI parameter and below the threshold defined by the BlindHORSCPThr HOPI parameter, the value of counter M1006C324 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by the MBLBInactivityRSCPThr FCMI parameter and the threshold defined by the BlindHORSCPThr HOPI parameter, the value of counter M1006C326 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is below the threshold defined by the MBLBInactivityRSCPThr FCMI parameter, the RRC connection is transferred to Cell_FACH/PCH or URA_PCH state in the current layer and no MBLB counters have been incremented.

3.4.7 3.4.7.1

Deactivating RAN3093: Enhanced MBLB Deactivating Enhanced load balancing Purpose Follow this procedure to deactivate theEnhanced load balancingfunctionality of the RAN3093 Enhanced MBLB feature.

DN09203161Issue:02

©2016Nokia

81



Procedure

1


2


3


4



b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced load balancing parameter to False.

5

3.4.7.2


Deactivating in RRC setupEnhanced layering during voice call setup - Blind IFHO Purpose Follow this procedure to deactivate theEnhanced layering during voice call setup - Blind IFHO in RRC setup functionality of the RAN3093 Enhanced MBLB feature.

82

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3


4



b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO in RRC setup parameter to False.

5

3.4.7.3


Deactivating Enhanced layering for CS voice call from CCH state during voice call setup - Blind IFHO Purpose Follow this procedure to deactivate theEnhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality of the RAN3093: Enhanced MBLB feature.

DN09203161Issue:02

©2016Nokia

83



Procedure

1


2


3


4



b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO for CS voice call from CCH states parameter to False.

5

3.4.7.4


Deactivating the MBLB HSPA load state bypass Purpose Follow this procedure to deactivate the MBLBHSPA load state bypass functionality of the RAN3093: Enhanced MBLB feature.

84

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3


4



b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Bypass of HSPA load state in case of CS voice call parameter to False.

5

3.4.7.5


Deactivating Enhanced inactivity triggered layering without compressed mode measurements Purpose Follow this procedure to deactivate theEnhanced inactivity triggered layering without compressed mode measurementsfunctionality of the RAN3093: Enhanced MBLB feature.

DN09203161Issue:02

©2016Nokia

85



Procedure

1


2


3


4



b) For each cell where the Enhanced inactivity triggered layering without compressed mode measurementsis deactivated, under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering without CM parameter to False.

5

3.4.7.6


Deactivating Enhanced mobility triggered layering Purpose Follow this procedure to deactivate theEnhanced mobility triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature.

86

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3


4



b) For each cell where the Enhanced mobility triggered layeringis deactivated, under theMBLBEnhancementsEnabled parameter parent structure, set the value of theEnhanced mobility triggered layering parameter to False.

5

3.4.7.7


Deactivating Enhanced inactivity triggered layering in state transition to CCH state Purpose Follow this procedure to deactivate theEnhanced inactivity triggered layering in state transition to CCH state functionality of the RAN3093 Enhanced MBLB feature.

DN09203161Issue:02

©2016Nokia

87



Procedure

1


2


3


4



b) For each cell where the Enhanced inactivity triggered layering in state transition to CCH stateis deactivated, under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering to CCH states parameter to False.

5


3.5 RAN2518: High Speed Cell_FACH Enhanced Introduction to the feature The RAN2518: High Speed Cell_FACH Enhancedfeature increases the share of air interface capacity for the RAN1913: High Speed Cell_FACHfeature, which means that the maximum number of common enhanced dedicated transport channel (E-DCH) resources per cell is increased from 10 to 32 users.

3.5.1

RAN2518 Benefits End-user benefits More users can transfer small and medium-sized packets in a more efficient manner. Operator benefits With this feature, cell capacity and throughput is increased by transferring a bigger share of small and medium-sized data bursts using theRAN1913: High Speed Cell_FACH feature, where High Speed Cell_FACH is the most efficient.

88

©2016Nokia

DN09203161Issue:02


3.5.2


RAN2518 Functional description The RAN2518: High Speed Cell_FACH Enhancedfeature increases the number of uplink common channel resources for smartphone UEs for enhanced dedicated transport channel (E-DCH) transmission in Cell_FACH state. Rel8+ UEs in the uplink use the common E-DCH to transfer the application packets to the network. For transferring small packet data, the common E-DCH is privileged, whereas large application data bursts and uploads need to be transferred through the dedicated E-DCH (HSUPA). Currently, the RAN1913: High Speed Cell_FACHfeature allows to configure the maximum number of simultaneous common E-DCH users up to 10 per cell. With the RAN2518: High Speed Cell_FACH Enhancedfeature this limit is increased from 10 to 32 common E-DCH resources allowing up to 32 active HS-RACH users per cell, however in an inactive state there can be more than 32 HS-RACH users in the cell. The RAN2518: High Speed Cell_FACH Enhancedfeature extends the range of BTS baseband resource allocation per Local Cell Group (LCG), for HS Cell FACH uplink usage. Without the RAN2518: High Speed Cell_FACH Enhancedfeature up to four HSUPA resource steps could be statically allocated for HS Cell FACH. With the RAN2518: High Speed Cell_FACH Enhancedfeature the maximum is increased from four to eight HSUPA Resource Steps. For more information, see High Speed Cell_FACH feature dimensioningin the Dimensioning WCDMA RAN: Flexi BTS Baseband document.

3.5.3

RAN2518 System impact Interdependencies between features The following features must be enabled before activating theRAN2518: High Speed Cell_FACH Enhanced feature: •

RAN1913: High Speed Cell_FACH

•

RAN1686: HSPA 72 Users Per Cell

The RAN2902: RACH Capacity Increasefeature is recommended whenRAN2518: High Speed Cell_FACH Enhancedfeature is configured with increased number of common EDCH resources to fully use the system capacity. Impact on interfaces •

Iub –

•

message NBAP: CAPABILITY INDICATION. NWI3 –

•

DN09203161Issue:02

In the NBAP: PHYSICAL SHAREDCHANNEL RECONFIGURATIONmessage, the Common E-DCH System Information IE carries the configuration for up to 32 instances of the Common E-DCH Resource Combination Information IE. BTS level capability reporting to RNC is indicated by extending the private Iub

The value of the commissioning parameterto configure the number of HSUPA Resource Steps allocated for HS-RACH already exists but its range is increased.

RNC - UE interface

©2016Nokia

89


–


SIB5 and SIB5bis indicate the numberof common E-DCH resources. In SIB5 and SIB5bis, the IE Common E-DCH system info carries the configuration of the common E-DCH resources (the maximum number of signaled resources is 32) which is a multiple instance of IE Common E-DCH Resource Configuration information list.

Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity There is an improvement in latency for HS-RACH users in the cell because of the increased number of resources. With one UE in the cell the performance is not impacted. Packet loss and latency in both low and high load cells is comparable to the RAN1913: High Speed Cell_FACH feature performance. The RAN2518: High Speed Cell_FACH Enhancedfeature allows for an increase in the overall HS-RACH throughput in a cell. Because of that a greater number of users requiring short data transfers is allocated to HS-RACH. The increase in HS-RACH capacity reduces the number of state transitions of users to CELL DCH leading to a reduction in the number of dedicated resource requests in a cell. The uplink capacity is better utilized by common E-DCH users since the interference created by common E-DCH transmission is quite small in comparison to dedicated EDCH transmission for the same size of data. As a result, the dedicated E-DCH users have better average throughput.

3.5.4


WCDMA16


mc R N C

RNC16

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2

MS C



WBTS16

S GSN



WBTS16

Under planning

MGW


UE

3GPP Rel-8

This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms Table 25

Alarms modified by RAN2518 A l arm ID

A l ar m n ame

7796

HIGHSPEEDCOMMONCHANNEL PROBLEM

Measurements and counters

90

©2016Nokia

DN09203161Issue:02


Table 26


C o u n t e rI D

C o u n t e rn a me


M1006C327

HS-FACH ABNORMAL RELEASE

M5000C481

SUM OF USERS IN HS CELL FACH WITH HS UL

HSPA in WBTS (WBTS)

M5000C482

MAX NUMBER OF USERS IN HS CELL FACH WITH HS UL

HSPA in WBTS (WBTS)

M5000C483

SUM OF USERS IN HS CELL FACH

M5000C484

MAX NUMBER OF USERS IN HS CELL FACH

HSPA in WBTS (WBTS)

M5000C485

DENOMINATOR FOR HS CELL FACH USERS

HSPA in WBTS (WBTS)

M5000C486

MINIMUM HIGH SPEED CELL FACH USERS LOAD

HSPA in WBTS (WBTS)

M5000C487

AVERAGE HIGH SPEED CELL FACH USERS LOAD

HSPA in WBTS (WBTS)

M5000C488

MAXIMUM HIGH SPEED CELL FACH USERS LOAD

HSPA in WBTS (WBTS)

M5000C489

AVERAGE COMMON EDCH RESOURCE USAGE

HSPA in WBTS (WBTS)

M5000C490

MAXIMUM COMMON EDCH RESOURCE USAGE

HSPA in WBTS (WBTS)

M5000C491

AVAILABLE COMMON E-DCH RESOURCES

HSPA in WBTS (WBTS)

M5000C492

DENOMINATOR FOR HS CELL FACH USERS WITH HS UL

HSPA in WBTS (WBTS)

M5006C71

AVERAGE NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH

WBTS R99 HW Resource (WBTS)

M5006C72

MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH


M5006C73

AVERAGE NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS


M5006C74

MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS


M5006C75

AVAILABLE NUMBER OF HIGH SPEED CELL_FACH USERS WITH HS RACH


Table 27

RRC signalling

HSPA in WBTS (WBTS)


C o u n t e rI D

DN09203161Issue:02


C o u n t e rn a me


M1006C318

MAX NUMBER OF HS-FACH/R99-RACH USERS PER CELL

RRC signalling

M1006C319

MAX NUMBER OF HS-FACH/HS-RACH USERS PER CELL

RRC signalling

M1006C320

MAX NUMBER OF PCH USERS WITH HRNTI ALLOCATED PER CELL

RRC signalling

©2016Nokia

91


Table 27


Existing counters related to RAN2518 (Cont.)

C o u n t e rI D

C o u n t e rn a me

M eas u re me n t

M1006C321

MAX NUMBER OF HSPA AND HS-FACH USERS PER CELL

RRC signalling

M5000C460

CONFIGURED HS-RACH SIGNATURES

HSPA in WBTS (WBTS)

M5000C461

NUMBER OF SUCCESSFULLY ACKNOWLEDGED HS-RACH

HSPA in WBTS (WBTS)

PREAMBLES




Table 29


RNC

Minimum Reduced E-DPDCH gain MinRedEDPDCH factor



Number of Common E-DCH Resources for HS-RACH High Speed RACH Enabled

HSRACHCommonEDCHRes


WCEL WCEL

HSRACHEnabled

HSPA 72 Users per Cell

HSPA72UsersPerCell

WCEL

RNCOptions

RncOptions

RNC

Table 30

Existing parameters related to RAN2518 F u l ln a m e


HSUPA enabled High Speed Cell_FACH DL Enabled

HSDPAenabled

Flexible UL RLC Enabled

FlexULRLCEnabled

HSDPA Dynamic Resource Allocation

WCEL

HSFACHEnabled

HSDPA enabled


WCEL

HSUPAEnabled

WCEL RNFC

HSDPADynamicResourceA llocation

RNFC


92

©2016Nokia

DN09203161Issue:02


Table 31


B SW/AS W

ASW

3.5.5



RAN


RNC LK

Activating RAN2518: High Speed Cell_FACH Enhanced Instructions to activate and configure RAN2518: High Speed Cell_FACH Enhanced using the OMS Element Manager. Purpose Follow this procedure to activate the RAN2518: High Speed Cell_FACH Enhanced feature. Before you start Restart of RNC not required after the activation of this feature. Ensure that RNC SW release is the same as (or newer than) BTS SW release. Ensure BTS has the WBTS16 software release installed. This procedure requires cell locking and causes downtime. Make sure you have access to the following applications: • •

OMS Element Manager Application Launcher

Ensure that RAN2518: High Speed Cell_FACH Enhancedlicense exists. The feature code for this feature is 5577. This feature is controlled by the long-term ON/OFF license key. For more information on licensing, see Licensing.

g

Note: Ensure an appropriate amount of BTS baseband resources has been commissioned for HS Cell FACH uplink. This can be done by changing the commissioning of the numOfHsRachResourceStepsRes parameter, which defines the number of HSUPA resource steps per LCG, allocated for HS RACH users. Each resource step supports up to maximum 10 HS RACH users. For more information, see High Speed Cell_FACH feature dimensioningin the Dimensioning WCDMA RAN: Flexi BTS Basebanddocument. The following features must be enabled before activating of theRAN2518: High Speed Cell_FACH Enhanced feature: • •

DN09203161Issue:02

RAN1913: High Speed Cell FACH RAN1686: HSPA 72 users per cell

©2016Nokia

93



Procedure

1

Set the RAN2518: High Speed Cell_FACH Enhancedfeature state to ON: •

For IPA-RNC, use the following MML command:

•

For mcRNC, use the following SCLI command:


2


3


4

Expand the RNC object and t hen the WCEL object.

5

Lock the cell Sub-steps

a) Select the WCEL object.

b) Right click on the cell and select Administrative State Change ► Lock Cell.

6


a) From the drop-down menu select Edit Parameters.

b) Set the the HSRACHCommonEDCHRes parameter to value greater than 10 (up to 32). The HSRACHCommonEDCHRes parameter defines the amount of configured common E-DCH resources of the HS-RACH configuration in the cell.

94

©2016Nokia

DN09203161Issue:02


7

Select Apply button to save the changes.

8

Unlock t he cell.


Sub-steps

a) Select the WCEL object b) Right click on the cell and select Administrative State Change ► Unlock Cell.

Result Expected outcome The BTS indicates support of theRAN2518: High Speed Cell_FACH Enhancedfeature by using Private NBAP message: Capability Indication with the IE, BTS Capability Container. The BTS indicates support of theRAN2518: High Speed Cell_FACH Enhancedfeature by using Private NBAP message: Capability Indication with the IE, BTS Capability Container. If the BTS is compatible, then PSCR Req sent by RNC to setup HS-RACH is acked with PSCR complete message by the BTS. Cell is unlocked. Unexpected outcome If BTS is not capable of the RAN2518: High Speed Cell_FACH Enhancedfeature, and RNC configuration of common E-DCH resources is greater than 10, RNC raises alarm 7796. RNC does not initiate HS-RACH setup and waits for an operator to fix the problem.

3.5.6

Verifying RAN2518: High Speed Cell_FACH Enhanced Purpose Follow this procedure to verify that the RAN2518: High Speed Cell_FACH Enhanced feature has been activated successfully. Procedure

1

Open the RNW Measurement Management application. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.

DN09203161Issue:02

©2016Nokia

95


2


Use the RNW Measurement Management application to start the M1006 measurement. Alternatively the measurement can be started using NetAct Administration of Measurements Application.

3

Wait for the next 60-minute interval to begin. The me asurement interval then starts.

4

Make at least 32 simultaneous connections with Rel-8 UE that supports HSRACH. Use Internet radio application, which utilizes TCP/IP as transport and connect each UE to a low bit rate radio station.

5

Wait until the current 60-minute interval ends and then another 10 minutes. After the measurement collection, it takes additional up to 10 minutes for the measurement data to be transferred to the OMS.

6

Open the RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.

7

Check if the following counters have been updated: • • • • • • •

M1006C319 MAX NUMBER OF HS-FACH/HS-RACH USERS PERCELL M5000C460 CONFIGURED HS-RACH SIGNATURES M5000C461 NUMBER OF SUCCESSFULLY ACKNOWLEDGED HS-RACH PREAMBLES M5000C489 AVERAGE COMMON EDCH RESOURCE USAGE M5000C490 MAXIMUM COMMON EDCH RESOURCE USAGE M5000C491 AVAILABLE COMMON E-DCH RESOURCES M5006C72 MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH

Expected outcome As many UEs as defined by the HSRACHCommonEDCHRes WCEL parameter can transmit simultaneously over HS-RACH channel. The following counters are updated successfully: • • •

96

M1006C319 MAX NUMBER OF HS-FACH/HS-RACH USERS PER CELL M5000C460 CONFIGURED HS-RACH SIGNATURES M5000C461 NUMBER OF SUCCESSFULLY ACKNOWLEDGED HS-RACH PREAMBLES

©2016Nokia

DN09203161Issue:02


• • • •

g 3.5.7


M5000C489 AVERAGE COMMON EDCH RESOURCE USAGE M5000C490 MAXIMUM COMMON EDCH RESOURCE USAGE M5000C491 AVAILABLE COMMON E-DCH RESOURCES M5006C72 MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH

Note: With the RAN2518: High Speed Cell_FACH Enhancedfeature (HS RACH Enhanced) up to 32 simultaneously active HS RACH users per cell is supported, as RNC can send maximum 32 common E-DCH resources configurations per cell.

Deactivating RAN2518: High Speed Cell_FACH Enhanced Purpose Follow this procedure to deactivate theRAN2518: High Speed Cell_FACH Enhanced feature.

DN09203161Issue:02

©2016Nokia

97



Procedure

1


2


3

Expand the RNC object and t hen the WCEL object.

4

Lock the cell Sub-steps

a) Select the WCEL object.

b) Right click on the cell and select Administrative State Change ► Lock Cell.

5

Expand the RNC object and configure the WCEL object. Sub-steps

a) From the drop-down menu select Edit Parameters.

b) Set the HSRACHCommonEDCHRes parameter to the value from 1 to 10.

6


7

Unlock t he cell. Sub-steps

a) Select the WCEL object

b) Right click on the cell and select Administrative State Change ► Unlock Cell.

8

Set the RAN2518: High Speed Cell_FACH Enhancedfeature state to OFF: •

For IPA-RNC, use the following MML command:

•

For mcRNC, use the following SCLI command:

ZW7M:FEA=5577:OFF;

98

©2016Nokia

DN09203161Issue:02



set license feature-mgmt code 0000005577 feature-adminstate off

Expected outcome Cell is up and running. Number of common E-DCH resources is reduced to the value defined by the RAN1913: High Speed Cell_FACH feature. Unexpected outcome The 7796 alarm is raised.

3.5.8

Testing RAN2518: High Speed Cell_FACH Enhanced Purpose

g 3.5.8.1

Note: This is an example of the verification. Do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples, and they can vary in different networks.

Testing the RAN2518: High Speed Cell_FACH Enhanced related counters Purpose The purpose of this test case is to verify that the RAN2518: High Speed Cell_FACH Enhanced feature works on BTS and counters related to this feature are correctly collected by BTS Site Manager. This test is performed in the Verifying RAN2518: High Speed Cell_FACH Enhanced chapter of feature activation instruction.

3.5.8.2

Testing the subunits consumption of reserved HSUPA resource steps for HS-RACH users Purpose The purpose of this test case is to verify the subunits consumption of reserved HSUPA resource steps for HS-RACH users. In comparison to theRAN1913: High Speed Cell_FACHfeature 8 instead of 4 HSUPA resource steps can be statically reserved for HS-RACH users. This means that one subunit consumption is visible in the case of Flexi System Module release 3, and two subunits are visible for Flexi System Module release 2. The following counter is checked via BTS Site Manager and RNW Measurement Presentation: •

DN09203161Issue:02

M5008C50 CONFIGURED HS-FACH SUBUNITS IN BTS (The amount of subunits configured for EFACH in uplink in BTS.

©2016Nokia

99



Test environment • • • • •

PC connected to BTS via LMP port or remotely. BTS Site Manager compatible with BTS SW version. Operational Radio Access Network and Core Network. Both FSMr2 and FSMr3 System Module platform can be used in this testing. Access to RNW Measurement Management.

Preconditions •

•

•

The M5012 FSM Level Monitoring measurement isstarted with RNW Measurement Management application. License for the RAN2518: High Speed Cell_FACH Enhancedfeature is installed on RNC. Maximum number of HSUPA Resource steps for HS-RACH users is commissioned as stated below: –

From HSUPA Settings page in HSUPA resource allocation set Number of HSUP A resource steps reserved for HS-RACH users to8.

Procedure

1

Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.

2

Ensure that BTS i s commissioned according to Preconditions.

3

Perform recommissioning procedure with the below HSUPA resource allocation settings. Figure 4

100

HSUPA settings

©2016Nokia

DN09203161Issue:02



4

After a full clock hour wait, an additional 15 minutes and open BTS PM Tab in BTS Site Manager.

5

Open Counters Tab.

6

Select BTS from Objects.

7

Expand WBTS BB su bunits usage from Counters.

8

Select the M5008C50 CONF_HSFACH_SU_WBTS counter.

9

Check the same counter via Application Launcher.

10 Use the RNW Measurement Management application to start the M5008 measurement.

11 Wait for the next 60-minute interval to begin. The measurement interval then starts.

12 Wait until the current 60-minute interval ends and then another 10 minutes.

13 Check if the M5008C50 CONF_HSFACH_SU_WBTS counter has been updated.

Expected outcome For Flexi System Module Rel3: •

1 subunit consumption is visible incomparison to 0.5 for the RAN1913: High Speed Cell_FACH feature (4 resource steps).

For Flexi System Module Rel2: •

2 subunits consumption is visible incomparison to 1 for the RAN1913: High Speed Cell_FACH feature (4 resource steps).

3.6 RAN2869: HSPA Subscriber Increase Introduction to the feature The RAN2869: HSPA Subscriber Increasefeature provides a new set of HSPA subscriber capacity steps which operators can choose based on their own traffic profiles. The current limit introduced by theRAN2124: HSPA 128 Users per Cellfeature is 128 HSPA users per cell. TheRAN2869: HSPA Subscriber Increasefeature adds additional

DN09203161Issue:02

©2016Nokia

101



capacity steps which allow to increase the maximum number of HSPA users per cell up to 208. The operator can purchase a pool size of subscriber capacity licenses for the RNC. The pool of additional 16 HSPA users can be allocated between cells (steps from 1 to 5) based on the subscriber amount that needs to be supported for each cell.

3.6.1

RAN2869 Benefits End-user benefits The RAN2869: HSPA Subscriber Increasefeature increases the maximum number of HSPA users per cell over the 128 in high-speed common channels so that more subscribers can be served at the same time. Operator benefits The feature benefits the operator as follows: •

•

3.6.2

It allows the operatorto define/purchase the neededamount of HSPA user capacity per cell. It introduces a flexible capacity step upgrade capability based on traffic increase, resulting in savings due to smaller and more flexible capacity steps.

RAN2869 Functional description The RAN2869: HSPA Subscriber Increasefeature increases the maximum number of HSPA users per cell over the current limit of 128 by adding additional capacity steps. The size of one step is 16 HSPA users and the number of selected steps can vary from 1 to 5, resulting in increasing the maximum number of HSPA users per cell up to 208, depending on HSPATotIncreaseStep parameter HSPATotIncreaseStep defines the capacity stepssettings. used inThe each cell. When the operator allocates one pool of additional 16 HSPA users to some cell, the system reduces the pool size of subscriber capacity licenses.

g

Note: Note that when the operator changes the 16 HSPA users amount (steps) between the cells, the system reduces the pool size of subscriber capacity licenses. The amount of HSPA users per cell is calculated with the following formula: HSPAtot = HSPA + HSDPA/DCH + HS-FACH/RACH + HS-FACH/HS-RACH The limitation for the number of subscribers per cell is set by the, for example, system performance, supported traffic profile, RL interference evolution. If the operator does not enable the RAN2869: HSPA Subscriber Increasefeature, RNC restricts the HSPA user amount to the number indicated by the existing HSPA (HSDPA) license.

3.6.3

RAN2869 System impact Interdependencies between features The following features need to be activated before activation of the RAN2869: HSPA Subscriber Increase feature: • • •

102

RAN1637: HS Cell_FACH DL RAN1913: HS Cell_FACH UL RAN2124: HSPA 128 Users per Cell

©2016Nokia

DN09203161Issue:02



The following features are related to theRAN2869: HSPA Subscriber Increasefeature:

•

RAN1644: Continuous Packet Connectivity RAN1308: HSUPA Interference CancellationReceiver RAN1201: Fractional DPCH RAN2302: Dynamic HSUPA BLER RAN2879: Mass Event Handler RAN2902: RACH Capacity Increase

• •

RAN2518: High Speed Cell_FACH Enhanced RAN3104: HSPA User Amount Monitoring

• • • • •

Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity when the number of users does not exceed the licensed maximum.

3.6.4



RAS

I PA - R N C

WCDMA 16

RNC16

mc R N C

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2


WBTS16

MS C


WBTS16

S GSN



Not planned

MGW

UE




New counters introduced by RAN2869 C o u n t e rI D

M1006C317

DN09203161Issue:02


HSFACH_REJECT_MAX_USE RS

©2016Nokia

M e as ur e men t

RRC signalling

103


Table 34


Existing counters related to RAN2869 C o u n t e rI D


M1000C282

M e as ur e men t

MAX_HSDPA_USERS_IN_CE LL

Cell Resource

M1006C318

MAX_HSFACH_R99_USERS

RRC signalling

M1006C319

MAX_HSFACH_HSRACH_US ERS

RRC signalling

M1006C320

MAX_PCH_WITH_RNTI_USE RS

RRC signalling

M1006C321

MAX_HSPA_TOTAL_USERS

RRC signalling


New parameters introduced by RAN2869 F u l ln a me


HSPA total increase step

Table 36


WCEL

HSPATotIncreaseStep

Existing parameters related to RAN2869 F u l ln a me

HSPA 128 Users per Cell

Table 37



WCEL

HSPA128UsersPerCell

New PRFILE parameters introduced by RAN2869 P ar a me t e rI D

P a r a me t e rn a me

007:0521

HSPA_DCH_MIN_RES


RAN2869 Sales information BSW /ASW

BSW+Long-term capacity


RAN

L i cen secon tro l in n etwo rk element

RNC LK

license

3.6.5

Activating RAN2869: HSPA Subscriber Increase Purpose Follow this procedure to activate the RAN2869: HSPA Subscriber Increasefeature.

104

©2016Nokia

DN09203161Issue:02



Before you start After the activation of this feature, there is no need to restart RNC or BTS. Activating procedure does not require cell-locking and does not cause downtime in the network. The RAN2869: HSPA Subscriber Increasefeature is enabled by selecting the appropriate amount of HSPA users by theHSPATotIncreaseStep parameter. The parameter introduces 5 capacity steps, where one step introduces 16 additional HSPA users per cell. When operator pool of additional HSPA users to some cell, the systemthe reduces theallocatesone poolsize of subscriber capacity16 licenses.

g

Note: Note that even when the operator changes the 16 HSPA users amount (steps) between the cells, the system reduces the pool size of subscriber capacity licenses. Before activating the RAN2869: HSPA Subscriber Increasefeature, activate the following features: • • •

RAN1637: HS Cell_FACH DL RAN1913: HS Cell_FACH UL RAN2124: HSPA 128 Users per Cell

The monitoring of HSPAtot is enabled by theRAN3104 HSPA User Amount Monitoring feature. The following features are recommended to be activated/configured before activation of the RAN2869: HSPA Subscriber Increasefeature: • • • • • • • •

RAN1644: Continuous Packet Connectivity RAN1308: HSUPA Interference CancellationReceiver RAN1201: Fractional DPCH RAN2302: Dynamic HSUPA BLER RAN2879: Mass Event Handler RAN2902: RACH Capacity Increase RAN2518: High Speed Cell_FACH Enhanced RAN3104: HSPA User Amount Monitoring

The RAN2518: High Speed Cell_FACH Enhancedfeature increases common E-DCH resources from 10 to 32. The RAN2902: RACH capacity increase feature increases the number of RACH signatures from 4 to 16. Activate the license for the RAN2869: HSPA Subscriber Increasefeature. To set the feature state to ON, use the following command: •

for IPA-RNC:

•

for mcRNC:


For information on managing licenses, seeLicensing.

DN09203161Issue:02

©2016Nokia

105



Procedure

1


2


3

Go to WCEL object by the path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object

4

Enable the HSPATotIncreaseStep parameter by setting one of the following values: • • • • •

g

1 2 3 4 5

(144 HSPA users (160 HSPA users (176 HSPA users (192 HSPA users (208 HSPA users

on cell) on cell) on cell) on cell) on cell)

Note: The HSPATotIncreaseStep parameter cannot be enabled if the HSPA128UsersPerCell parameter is set toDisabled.

Further information The minimum capacity can be defined for HSPA Cell_DCH state users with the PRFILE parameter 007:0521 HSPA_DCH_MIN_RES with the configuration of the first four bits, counted from right, within 0000 0000 x000 1011. When this minimum reservation is determined, HS-FACH users are not permitted to use this capacity. By default, the minimum reservation, determined with this PRFILE parameter, is not active. There is an additional functionality to activate the pre-emption for HS Cell_FACH users with the PRFILE parameter 007:0521 HSPA_DCH_MIN_RES. The pre-emption is determined with the eighth bit within 0000 0000 1000 xxxx. When the pre-emption is activated and the maximum number of HSPA and HS-FACH users per cell is obtained/surpassed, the HS-FACH users are transferred to Cell_PCH state until the number of users is below the maximum licensed number of users. Target UEs for preemption are chosen on their time of HS-FACH allocation.

3.6.6

Verifying RAN2869: HSPA Subscriber Increase Purpose Follow this procedure to verify if the RAN2869: HSPA Subscriber Increasefeature works properly in the network. Before you start Verify the amount of HSPA users selected by theHSPATotIncreaseStep parameter.

106

©2016Nokia

DN09203161Issue:02



Make sure you have access to the following applications: RNW Measurement Management RNW Measurement Presentation

• •

Procedure

1


2

Start the M1006 RRC SIG NALLING measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3


4

Check if the values of counters M1006C317, M1006C318, M1006C319, M1006C320, M1006C321 are updated. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.

Unexpected outcome The M1006C317 counter, counting the number of users which are not allocated at the HSPA, HSDPA/DCH, HS-FACH/RACH, and HS-FACH/HS-RACH because of the HSPA maximum licensed user amount restriction, is increased.

g 3.6.7

Note: When the M1006C317 counter is increased, the operator needs to allocate more HSPAtot increase steps with theHSPATotIncreaseStep parameter.

Deactivating RAN2869: HSPA Subscriber Increase Purpose Follow this procedure to deactivate theRAN2869: HSPA Subscriber Increasefeature.

DN09203161Issue:02

©2016Nokia

107



Procedure

1


2


3

Go to WCEL object by the path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object

4

Determine the value of the HSPATotIncreaseStep parameter to Disabled.

g

Note: After deactivation of the RAN2869: HSPA Subscriber Increasefeature, the amount of HSPA users in the cell is based on the owned license and parameter settings.

3.7 RAN3046: Interference Cancellation for 4Rx Benefits, functionality, system impact, reference data, instructions of the feature The RAN3046: Interference Cancellation for 4Rxfeature enhances theRAN1308: HSUPA Interference Cancellation Receiverand RAN2250: Enhanced HSUPA IC features, which interwork with RAN1269: 4-Way RX Diversity, through extending the parallel interference cancelation (PIC) support up to 4-way radio receiver (Rx) diversity cells. Flexi Multiradio 10 Base Station and above versions support the RAN3046: Interference Cancellation for 4Rxfeature, and up to 12 cells per BTS are supported.

3.7.1

RAN3046 benefits The RAN3046: Interference Cancellation for 4Rxfeature provides the following benefits: • • •

3.7.2

Higher uplink cell throughput Higher uplink user throughput Lower interference from 2-ms TTI UEs

RAN3046 functional description The RAN3046: Interference Cancellation for 4Rxfeature enables interference cancelation (IC) at the base transceiver station (BTS) of up to a maximum of 12 4Rx cells per BTS (for example, 4+4+4 or 2+2+2+2+2+2 site configuration). IC at the BTS reduces the interference caused by a high-speed uplink packet access (HSUPA) 2-ms transmission timing interval (TTI) user. In the earlier implementation, IC is supported for 2Rx only. With theRAN3046: Interference Cancellation for 4Rxfeature, IC is now supported also for 4Rx. IC and 4Rx can be activated together in the same cell for

108

©2016Nokia

DN09203161Issue:02



Flexi System Module Rel3 (FSMr3) (that is, FSMr3, FSMr3+FSMr3) or above releases. For Flexi System Module Rel2 (FSMr2), simultaneous activation of 4Rx and IC remains unsupported. For FSMr3 (master) + FSMr2 (slave) configuration, theRAN3046: Interference Cancellation for 4Rx feature is disabled on both FSMr3 master and FSMr2 slave. If FSMr2 is hot inserted as an extension of FSMr3 that has activated the feature, the cells on that FSMr3 will have the feature disabled. The BTSSM performs the restriction. On the other hand, if FSMr2 is hot removed during runtime, the cells on FSMr3 (which has deactivated the feature) will have the feature enabled if either of the following conditions is met (BTSSM removes the restriction): •

•

RAN1308: HSUPA Interference CancellationReceiver , RAN2250: Enhanced HSUPA IC, and RAN1269: 4-Way RX Diversityare activated for the cell. RAN1308: HSUPA Interference CancellationReceiver and RAN1269: 4-Way RX Diversity are activated for the cell.

With the RAN3046: Interference Cancellation for 4Rxfeature, a mixed configuration is supported in PIC pools, so the cells with 2Rx or 4Rx can be located in same PIC pool. The maximum number of cells supported in one PIC pool is calculated based on the PIC pool capacity and the Rx configuration of the cell. •

•

•

•

Maximum of three cells in a single PIC pool having three cells with4Rx and no cell with 2Rx Maximum of four cells ina single PIC pool having two cells with 4Rx andup to two cells with 2Rx Maximum of five cells in asingle PIC pool having onecell with 4Rx and upto four cells with 2Rx Maximum of six cells in asingle PIC pool having nocell with 4Rx and upto six cells with 2Rx

The RAN3046: Interference Cancellation for 4Rxfeature is supported in Flexi Multiradio 10 Base Station and above versions, and up to 12 cells per BTS are supported. Effect of RAN3046 on cell capacity with HSUPA The RAN3046: Interference Cancellation for 4Rxfeature provides higher cell throughput gain as compared to ePIC+2Rx diversity and 4Rx diversity. The cell throughput is decreased with more users in the cell. However, the cell throughput is expected to be higher than that in the same test environment with ePIC+2Rx or with 4Rx and with the same number of users.

3.7.3

RAN3046 system impact RAN3046: Interference Cancellation for 4Rx impact on features, network management tools, and system performance and capacity Interdependencies between features Any of the following feature combinations must be activated to automatically activate the RAN3046: Interference Cancellation for 4Rxfeature: •

DN09203161Issue:02

RAN1308: HSUPA Interference CancellationReceiver , RAN2250: Enhanced HSUPA IC, and RAN1269: 4-Way RX Diversity

©2016Nokia

109


•


RAN1308: HSUPA Interference CancellationReceiver and RAN1269: 4-Way RX Diversity

Impact on interfaces The RAN3046: Interference Cancellation for 4Rxfeature has no impact on interfaces. Impact on network management tools The RAN3046: Interference Cancellation for 4Rxfeature impacts network management tools as follows: • BTS Site Manager (BTSSM) –

–

–

g

Restriction of PIC+4Rx or ePIC+4Rx onpure FSMr3 or above releases is removed during commissioning or recommissioning. Restriction of PIC+4Rx or ePIC+4Rx onFSMr3 + FSMr2 or pure FSMr2 is performed during commissioning or recommissioning. Cells in one PIC pool can be configured with different Rx streams (thatis, 2Rx or 4Rx).

Note: No separate license is required for this feature. Impact on system performance and capacity The RAN3046: Interference Cancellation for 4Rxfeature impacts system performance and capacity as follows: • •

3.7.4

Better signal quality and higher throughput are achieved. Higher cell throughputcan be obtained in the uplink (UL) direction.

RAN3046 reference data RAN3046: Interference Cancellation for 4Rx requirements, measurements and counters, KPIs, and sales information Requirements Table 39


RAS

I PA - R N C

mc R N C



WCDMA 16



Not planned

WBTS16 3.0


OMS Support not required

NetAct Support not required

MS C Support not required

S GSN Support not required

MGW Support not required

UE Support not required

Alarms There are no alarms related to theRAN3046: Interference Cancellation for 4Rxfeature. Commands

110

©2016Nokia

DN09203161Issue:02



There are no commands related to theRAN3046: Interference Cancellation for 4Rx feature. Measurements and counters Table 40


C o u n t e rI D

C o u n t e rn a me

M5000C151

HSUPA MINIMUM MAC-D THROUGHPUT

5000 - HSPA in WBTS (WBTS)

M eas u re me n t

M5000C152

HSUPA MAXIMUM MAC-D THROUGHPUT


M5000C153

HSUPA AVERAGE MAC-D THROUGHPUT


M5000C322

HSUPA MACE PDU DATA WITH 2MS TTI


M5000C323

HSUPA MACE PDU DATA WITH 10ms TTI


M5000C324



M5000C325



M5008C49

CONFIGURED PIC SUBUNITS IN BTS

5008 - WBTS level monitoring (WBTS)

M5005C40

PIC INDICATION FOR ACTIVE STATE

5005 - HSPA in WBTS Extension (WBTS)

M5005C41

PIC INDICATION FOR INACTIVE STATE

5005 - HSPA in WBTS Extension (WBTS)

For counter descriptions, seeWBTS and Flexi Performance Measurements. Key performance indicators Table 41

Existing key performance indicators related to RAN3046

KIP DI

KnPaIme

RNC_2050b

Active HSUPA 2ms TTI throughput

RNC_2051b

Active HSUPA 10ms TTI throughput

RNC_1883c

Active HSUPA Cell throughput

RNC_5460a

Average HSUPA user throughput

RNC_5118a

Peak number of HSUPA users in WBTS

RNC_1036b

Average number of simultaneous HSUPA users

For KPI descriptions, see WCDMA RAN Key Performance Indicators. Parameters There are no parameters related to theRAN3046: Interference Cancellation for 4Rx feature. Sales information

DN09203161Issue:02

©2016Nokia

111


Table 42


RAN3046 sales information BSW /ASW

S o f t w a r e c o mp o n e n t

ASW

3.7.5

RAN

L i cen se con tro l in n etwo rk element

BTS LK

Activating RAN3046 Instructions to activate the RAN3046: Interference Cancellation for 4Rx feature Purpose Follow this procedure to activate the RAN3046: Interference Cancellation for 4Rx feature. Before you start •

Feature interdependencies – – –

•

•

•

RAN1308: HSUPA Interference CancellationReceiver RAN2250: Enhanced HSUPA IC RAN1269: 4-Way RX Diversity

Licensing No separate license is required for this feature. Hardware requirement FSMr3, FSMr3+FSMr3, and above versions are supported. Software requirement WBTS16 3.0 or WBTS17 is required.

•

To activate the RAN3046: Interference Cancellation for 4Rxfeature, activate any of the following feature combinations: – –

g

RAN1308: HSUPA Interference CancellationReceiver , RAN2250: Enhanced HSUPA IC, and RAN1269: 4-Way RX Diversity RAN1308: HSUPA Interference CancellationReceiver and RAN1269: 4-Way RX Diversity

Note: See the feature activation instructions of each of the listed features for activation procedures.

Result Expected outcome The RAN3046: Interference Cancellation for 4Rxfeature is automatically activated.

3.7.6

Verifying RAN3046 Instructions to verify if the RAN3046: Interference Cancellation for 4Rx feature works properly in the network

112

©2016Nokia

DN09203161Issue:02



Before you start Required tools and equipment: •

RAN1308: HSUPA Interference CancellationReceiver , RAN2250: Enhanced HSUPA IC, and RAN1269: 4-Way RX Diversityare activated for the cell.

•

FSMr3 or FSMr3+FSMr3 version is used.

Procedure

1

Run a test with each of the following: • •

2

4 HSUPA UEs (4*2 ms TTI or 2*2 ms TTI + 2*10ms TTI), each doing FTP uplink in AWGN/VA30/VA120/PA3 channel model 19 HSUPA 2 ms TTI UEs, each doingFTP uplink in AWGN channel model

Compare the throughput and performance of each test run with ePIC+4Rx (RAN3046: Interference Cancellation for 4Rx -activated) against ePIC+2Rx (RAN2250: Enhanced HSUPA IC-activated) in the same configuration.

Result Expected outcome The uplink throughput of the UE and the cell with ePIC+4RxRAN3046: ( Interference Cancellation for 4Rx-activated) is higher than ePIC+2Rx R ( AN2250: Enhanced HSUPA IC-activated). The KPIs and counters related toRAN3046: Interference Cancellation for 4Rxare improved.

3.7.7

Deactivating RAN3046 Instructions to deactivate the RAN3046: Interference Cancellation for 4Rx feature Purpose Follow this procedure to deactivate theRAN3046: Interference Cancellation for 4Rx feature. Before you start •

The RAN3046: Interference Cancellation for 4Rxfeature is activated.

•

To deactivate the RAN3046: Interference Cancellation for 4Rxfeature, deactivate any of the following features: – –

DN09203161Issue:02

RAN1308: HSUPA Interference CancellationReceiver RAN1269: 4-Way RX Diversity

©2016Nokia

113


g


Note: See the feature activation instructions of each of the listed features for deactivation procedures. Result Expected outcome The RAN3046: Interference Cancellation for 4Rxfeature is automatically deactivated.

3.8 RAN3040: IRC Receiver Introduction to the feature This feature introduces the Interference Rejection Combining (IRC) mechanism which provides protection for the R99 UL and HSUPA end users against the interference. The IRC mechanism at base station removes dominant interference from an uplink signal before demodulation and before probable further reduction of interference.

3.8.1

RAN3040 Benefits End-user benefits This feature provides higher end-user throughput within the uplink. Operator benefits This feature provides the IRC mechanism which makes the interference within the uplink decreased to offer improved signal quality, higher end-user and cell throughput and consequently provides more capacity within the uplink. Moreover, the IRC mechanism permits to maintain the cell coverage at the moment of interference.

3.8.2

RAN3040 Functional description The RAN3040: IRC Receiver feature introduces the Interference Rejection Combining (IRC) mechanism which provides protection for the R99 UL and HSUPA end users against the interference. The IRC mechanism at base station removes dominant interference from an uplink signal before demodulation and before probable further reduction of interference. The interference within the uplink is decreased then to offer improved signal quality, higher UE throughput and consequently more capacity within the uplink. Moreover, the IRC mechanism also permits to maintain the cell coverage at the moment of interference. The IRC mechanism protects against intra-cell, inter-cell, and external interference notably when there are not many dominant interferers. The IRC mechanism can remove approximately N-1 dominant interferers where N is the number of antennas per one cell. Note that the IRC mechanism can remove a certain part of dominant interference even when the number of dominant interferers is greater than N-1. The IRC mechanism is based on combining the antenna signals from more than one antenna and estimating the covariance of interference between the antennas, aiming to whitening the interference. Note the difference with the Interference Cancellation (IC) mechanism. The IC mechanism, contrary to IRC mechanism, is based on removing demodulated signals of interferers from the other signals. When compared to Maximum Ratio Combining (MRC) mechanism which maximizes the SNR for white noise, the IRC mechanism provides greater SINR than MRC mechanism after combining. The IRC

114

©2016Nokia

DN09203161Issue:02



mechanism removes dominant interference with proper phasing and weighting of the antenna signals to be combined. The IRC mechanism is an alternative to the MRC mechanism at the receiver chain when summarizing the comparison with the MRC mechanism. This feature can operate with and without the features which provide the IC mechanism. When the feature works without the IC mechanism, the IRC mechanism decreases dominant interference independent on whether the interference srcinates from the enduser at the same cell, surrounding cells and external sources. When the feature is activated together with the IC mechanism, the IC mechanism provides the most efficient protection against own cell interference, whereas the IRC mechanism protects against dominant interference from the sources which are not managed with the IC mechanism.

3.8.3

RAN3040 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •

•

3.8.4

The IRC mechanism provides morecombining gain than the MRC mechanism which means improved signal quality, higher end-user and cell throughput and consequently more capacity within the uplink. Moreover, the IRC mechanism also permits to maintain the cell coverage at the moment of interference. The IRC mechanism alternates theMRC mechanism at the receiver chain and protects against the type of interference which is not managed with the IC mechanism.



RAS

I PA - R N C

mc R N C

WCDMA 16



OMS

NetAct


NetAct 16.2

MSC



WBTS16

SGSN



WBTS16

MGW


Under planning

UE


This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.

DN09203161Issue:02

©2016Nokia

115



This feature requires more than one antenna per one cell. With one antenna N-1=0. Faults Table 44

New faults introduced by RAN3040

F au l tI D

F a u l tn a m e

4248

R e p o r t e da l ar m s

IRC Receiver not available for pure single RX BTS configuration

7652 BASE STATION NOTIFICATION

Measurements and counters Table 45


C o u n t e rI D


Me as u re me n t

M5005C55

SUM OF IRC PROCESSED USERS

M5005C56

SUM OF ALL USERS

M5005C57

ALL AND IRC USERS DENOMINATOR

HSPA in WBTS Extension HSPA in WBTS Extension HSPA in WBTS Extension


New parameters introduced by RAN3040 F u l ln am e


IRC receiver enabled

ircReceiverEnabled


BTSSCW



B S W /A S W

ASW

3.8.5


RAN


BTS LK

Activating RAN3040: IRC Receiver Purpose Follow this procedure to activate this feature. Before you start Restart of the RNC or the BTS is not required after the activation of this feature. This procedure does not cause downtime and it can be activated any time of the day. Make sure you have access to the following applications: •

116

BTS Site Manager

©2016Nokia

DN09203161Issue:02



The RAN3040: IRC Receiver feature is controlled by a license and requires a valid license file. The feature code for this feature is 5428. Make sure you have the license file installed. The license state must be set to ON.

g

Note: This feature can be activated only on the BTS level. Procedure

1


2


3


4


5

On the BTS Settings page, select the 'Activate IRC Receiver' checkbox.

6


7


8


Expected outcome The RAN3040: IRC Receiver feature is activated.

3.8.6

Verifying RAN3040: IRC Receiver Purpose Follow this procedure to verify if the RAN3040: IRC Receiver feature works properly in the network. Before you start Make sure you have access to the following applications: • •

DN09203161Issue:02


©2016Nokia

117



Procedure

1


2

Start the measurement for the M5005C55 SUM_NUM_IRC_PROC_USERS and M5005C56 SUM_NUM_ALL_USERS counters. For details on starting the measurements in the RNW Measurement Management application, seeStarting radio network measurementsin Managing and viewing RNC measurements.

3

Set up one AMR, R99, or HSUPA call.

4

Run the measurement for one full hour.

5

Open the RNW Me asurement Presentation application and check values of the M5005C55 and M5005C56 counters. For details on checking the counter values in the RNW Measurement Presentation application, seeViewing and modifying radio network measurement parametersin Managing and viewing RNC measurements.

Expected outcome The M5005C55 and M5005C56 counter values are changed from0 to approximately 36000.

3.8.7

Deactivating RAN3040: IRC Receiver Purpose Follow this procedure to deactivate this feature. Before you start Make sure you have access to the following applications: •

118

BTS Site Manager

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3


4


5

On the BTS Settings page, clear the 'Activate IRC Receiver' checkbox.

6


7


8


Expected outcome The RAN3040: IRC Receiver feature is deactivated. Further information After deactivating the feature set the feature license state to OFF.

3.8.8

Testing RAN3040: IRC Receiver Purpose

g

Note: This is an example of the verification; do not use it for the feature as such in live network. The configuration and parameter settings described are only examples and they can vary in different networks. The purpose of this test case is to verify that the RAN3040: IRC Receiver feature is working on BTS and that the counters related to this feature are correctly collected and fetched by the BTS Site Manager. The following counters are to be checked: • M5005C55 SUM OF IRC PROCESSED USERS Sum of IRC processed users in a cell, obtained by sampling with predefined sampling period the current number of IRC processed users in a cell, and summing all the samples together. •

DN09203161Issue:02

M5005C56 SUM OF ALL USERS

©2016Nokia

119


•


Sum of all users in a cell, obtained by sampling with predefined sampling period the current number HSUPA and R99 users in a cell, and summing all the samples together. M5005C57 ALL AND IRC USERS DENOMINATOR Number of samples taken to calculate M5005C55 and M5005C56

Test environment: •

PC connected to BTS via LMP port or remotely

• •

BTS Site Manager compatible with BTS SW version Operational Radio Access Network and Core Network FSMr2 or FSMr3 System Module platform Access to RNW Measure Management

• •

Before you start Preconditions: • • •

•

M5005 HSPA in WBTS Extension measurement is started. BTS is working and has been 'On Air' for more than one full clock hour. Valid license for the RAN3040: IRC Receiver feature (feature code: 5428) is installed on the BTS. The RAN3040: IRC Receiver feature is enabled on the BTS (seeActivating RAN3040: IRC Receiver).

Procedure 1

Within one full clock hour make several AMR and HSUPA calls via tested BTS.

2

After furher 15 minutes (after the full clock hour finishes), in the BTS Site Manager, go to BTS PM tab on the left-hand side.

3

In the BTS PM tab, open 'Counters' tab.

4

From ‘Objects’ select Local cell which has been used in test.

5

From ‘Counters’ expand ‘HSPA in WBTS E xtension’ and go to ‘Cell IRC users amount’ tab.

6

Check the values of the three IRC-related counters: M5005C55, M5005C56, M5005C57.

Result Three IRC-related counters are visible: M5005C55, M5005C56, M5005C57.

120

©2016Nokia

DN09203161Issue:02



The value of the counter M5005C55 is greater than 0 and the CPU load on BTS equals M5005C56. The value of the counter M5005C57 should be around 36000.

g

Note: Samples of counters M5005C55, M5005C56, M5005C57 are collected every 100 ms.

3.9 RAN3235: Optimized Packet Handling at RNC Introduction to the feature

The RAN3235: Optimized Packet Handling at RNCfeature introduces the Active Queue Management (AQM) mechanism to improve packet handling at RNC for DL data transmission from CN. The feature pertains to the HSPA data transmission. The mechanism provides that even with the most demanding TCP configurations, packet drops are controlled while ensuring fairness among the traffic flows. The optional mechanism of the HTTP incubation is introduced to ensure that, in specific cases, the performance of the HTTP data transmission is not compromised at the congestion moment.

3.9.1

RAN3235 Benefits End-user benefits The RAN3235: Optimized Packet Handling at RNCfeature provides that even with the most demanding TCP configurations, packet drops are controlled while ensuring fairness among the traffic flows. It also provides decreased amount of dropped DL HSPA packets within RNC PDCP, improved faireness of traffic among competing TCP flows, and, optionally, in specific cases, incubation of HTTP traffic during congestion. Operator benefits This feature optimizes the operator network to manage the TCP and UDP configuration demands within modern portable communication units and consequently, the TCP and UDP end-to-end performance is improved with stable throughput, fairness among the traffic flows, and decreased amount of dropped DL HSPA packets within the RNC PDCP. In specific cases, the performance of the HTTP data transmission is not compromised at the congestion moment within the RNC PDCP.

3.9.2

RAN3235 Functional description The modern communication units have demanding TCP and UDP configurations where greater amount of data is transmitted from CN to RNC and consequently, increased buffer at RNC or advanced queue management are needed to prevent degradation of TCP/UDP performance. The RAN3235: Optimized Packet Handling at RNCfeature introduces the Active Queue Management mechanism to improve TCP and UDP packet managing at RNC for DL data transmission from CN. The feature pertains to the HSPA data transmission. The mechanism optimizes the operator network to manage the TCP and UDP configuration demands within modern portable communication units and consequently the TCP and UDP end-to-end performance is improved with stable throughput, improved faireness of traffic among competing TCP flows, and decreased amount of dropped DL HSPA packets within the RNC PDCP. The Active Que Management mechanism at PDCP

DN09203161Issue:02

©2016Nokia

121



provides high link utilization without introducing undue delays within the end-to-end path through the active monitoring of buffer fill state and performing preventive actions before the queue fills up and incoming HSPA packets are dropped. The mechanism appends a timestamp to each of the incoming HSPA packets and then performs a comparison between the age of the oldest packet and the threshold determined through the percentage of tunable time. Once the oldest packet is older than determined threshold, a probability is computed for each of the incoming HSPA packets. Once the sum of probability computed for incoming HSPA packets is greater than determined threshold, the latest packet is dropped and the computation is started again. This feature optionally introduces the HTTP incubation mechanism ensuring that the HTTP performance is not compromised at the congestion moment during the Active Queue Management mechanism activity within the RNC PDCP. When the Active Queue Management mechanism is enabled without the HTTP incubation mechanism, the HTTP data is not incubated at the congestion moment during the Active Queue Management mechanism activity and the TCP/UDP and HTTP data is dropped. When the Active Queue Management mechanism is enabled with the HTTP incubation mechanism, the HTTP data is incubated at the congestion moment during the Active Queue Management mechanism activity and the HTTP data is not dropped when HTTP is not the dominant traffic. Note that the recommended option is to activate the feature with the mechanisms for AQM only. The dimension of PDCP buffer is retained at optimum value of 1MB size and aligned with the Active Que Management(AQM) algorithm .

g 3.9.3

Note: Single stream FTP download might occasionally face deviations in Download time observations towards the negative side, because of the lower stabilized throughput achieved due to AQM packet drops.

RAN3235 System impact Interdependencies between features This feature has a functional dependency with theRAN2510: In-Bearer Application Optimization feature. When the Active Queue Management mechanism works with the In-Bearer Application Optimization mechanism, the Active Queue Management mechanism performs actions preventing the queue fills up starting with the packet of low priority. When the low priority data is not present, the high priority data is dropped based on the Active Queue Management mechanism through the probability computation. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •

122

The operator network performance isoptimized to managethe TCP configuration demands within modern portable communication units making the TCP end-to-end performance improved with stable throughput, fairness among the traffic flows, and decreased amount of dropped DL HSPA packets within the RNC PDCP.

©2016Nokia

DN09203161Issue:02


•

•

3.9.4


The goodput performance is muchmore stable and fairness is improved among different traffic flows for the UE. In specific cases, theperformance of the HTTP data transmission is not compromised at the congestion moment within the RNC PDPC.



RAS

I PA - R N C

WCDMA 16

RNC16

mc R N C


mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2


MS C



S GSN



MGW


UE





C o u n t e rI D


M1022C241

RLC DL SDU BYTES DROPPED

Me as u re me n t

Packet Call





Optimized TCP Packet Handling at RNC Enabled

TCPOptimizeEnabled

RNFC

AQM Delay Threshold Time

AQMDelayThresholdTime

RNHSPA

Table 51

Parameters modified by RAN3235 F u l ln a me

RNC Options

A b b r e v i a t e dn a me RncOptions


RNC


DN09203161Issue:02

©2016Nokia

123


Table 52


B S W /A S W

ASW

3.9.5



RAN


RNC LK

Activating RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to activate the RAN3235: Optimized Packet Handling at RNC feature in RNC. Before you start This activating procedure does not require cell locking. After the activation of this feature, there is no need to restart RNC or BTS. Install the license for the RAN3235: Optimized Packet Handling at RNCfeature and set the feature state to ON using the following command: •

for IPA-RNC:

•

for mcRNC:


Procedure

1


2


3

Configure the RNFC object: Sub-steps

a) Go to the RNFC object using the following path: RNC object ► RNFCs folder ► RNFC object.

b) Right-click the RNFC object and select Edit parameters.

c) On the Packet Scheduler tab, set the value of the TCPOptimizeEnabled parameter to: •

124

AQM RED Enabled , for activating the AQM RED mechanism at RNC PDCP. When only the Active Queue Management Random Early Detection (AQM RED) mechanism is activated, both the TCP/UDP and the HTTP packets are dropped during congestion or overflow scenarios.

©2016Nokia

DN09203161Issue:02


g


Note: AQM RED Enabled is the recommended value of the TCPOptimizeEnabled parameter. •

AQM RED Enabled + HTTP Incubation Enabled, for activating both the AQM RED and the HTTP incubation mechanisms at RNC PDCP. When both the AQM RED and the HTTP incubation mechanisms are active, during congestion or overflow scenarios the TCP/UDP packets are dropped and the HTTP packets are incubated (not dropped) in specific scenarios.

d) Click Apply to save the changes.

g 3.9.6

Note: After activating, the RAN3235: Optimized Packet Handling at RNCfeature is applied only to new RRC Connections. Ongoing connections are not affected.

Verifying RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to verify if the RAN3235: Optimized Packet Handling at RNC feature works properly in the network. Before you start Make sure that theRAN3235: Optimized Packet Handling at RNCfeature is activated with the RNFC- TCPOptimizeEnabled parameter valueAQM RED Enabled . Make sure you have access to the following applications: • • •

OMS Element Manager RNW Measurement Management RNW Measurement Presentation

Procedure

1

Set the value of the RNHSPA - AQMDelayThresholdTime parameter to 20 ms.

2


3

Start the M1022 Packet Call measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and Viewing RNC Measurements.

DN09203161Issue:02

©2016Nokia

125



4

Initiate data transfers with 2 applications (for example HTTP and FTP) in a single UE for producing high traffic load to have congestion.

5


6

Check the value of the counter M1022C241: RLC DL SDU BYTES DROPPED. Under congestion conditions, the value of counter M1022C241 is expected to be lower when the RAN3235: Optimized Packet Handling at RNCfeature is activated than when the feature is not activated. Before comparing the measurement results, ensure that the similar load conditions and measurement period were applied to both cases. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.

Expected outcome Packets drop is expected to be reduced at RNC PDCP. The drop reduction can be verified with the counter M1022C241. Troubleshooting actions If the packet drop is not reduced, increase the RNHSPAAQMDelayThresholdTime parameter value by 10 ms and repeat the verifying procedure.

g 3.9.7

Note: Optionally, to configure the PDCP buffer size to 2MB, contact your local customer support.

Deactivating RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to deactivate theRAN3235: Optimized Packet Handling at RNC feature in RNC.

126

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3


a) Go to the RNFC object using the following path: RNC object ► RNFCs folder ► RNFC object.

b) Right-click the RNFC object and select Edit parameters.

c) On the Packet Scheduler tab, set the value of the TCPOptimizeEnabled parameter to Disabled.

d) Click Apply to save the changes.

g

Note: After deactivating, the RAN3235: Optimized Packet Handling at RNCfeature is still applied to ongoing connections. Only the new RRC connections are not affected by this feature.

3.10 RAN2902: RACH Capacity Increase Introduction to the feature With the RAN2902: RACH Capacity Increase feature, the maximum number of RACH preamble signatures per cell is increased from 4 to 16.

3.10.1

RAN2902 Benefits End-user benefits This feature provides the end user with faster network access, especially in the highloaded cells. Operator benefits This feature decreases uplink interference thanks to fewer signature collisions and fewer RACH cycles needed. Having more RACH preamble signatures available also improves the performance of theRAN1913: High Speed Cell_FACHand the RAN2518: High Speed Cell_FACH Enhancedfeatures.

DN09203161Issue:02

©2016Nokia

127


3.10.2


RAN2902 Functional description The RAN2902: RACH Capacity Increasefeature increases the number of RACH preamble signatures available in a cell from 4 to 16. Increased number of signatures decreases the probability of collision during the physical RACH procedure. In consequence, RACH procedure needs fewer repetitions and the network access is faster. Additionally, the interference in the uplink is decreased. Increasing the number of RACH preamble signatures is especially beneficial when the RAN1913: High Speed Cell_FACHfeature is in use, and even more beneficial with the RAN2518: High Speed Cell_FACH Enhancedfeature on top of it. The number of subscribers with the HS-Cell_FACH-capable UEs is growing. Using the High Speed Cell_FACH results in significant capacity gain: higher number of users can be served in a cell and/or higher volume of user data can be transferred in a cell (on account of reduced signaling). However, in the current system implementation there is only one preamble signature available for HS RACH. With the RAN2902: RACH Capacity Increase and the RAN1913: High Speed Cell_FACHfeatures activated, the operator can enable up to 12 preamble signatures for HS RACH. The number of RACH preamble signatures can also be increased with the RAN2902: RACH Capacity Increase feature. Operator can allocate up to 8 RACH signatures and up to 12 HS RACH signatures (but no more than 16 signatures in total). Allocating preamble signatures is managed with the RACHPreambleSignatures WCEL parameter. Modification of this parameter requires cell locking and unlocking. Table 53

Available preamble signature combinations RAN1913 deactivated

RAN1913 activated

RACHPreambleSignatures Number of RACH Number of RACH parameter value preamble preamble signatures signatures

RACH 1 signature

1

RACH 2 signatures

2

2

1

RACH 3 signatures

3

3

1

RACH 4 signatures

4

3+3 RACH and HS RACH signatures

1

3 N/A

RACH 8 signatures

g

1

Number of HS RACH preamble signatures

8

1 3

3

7

1


N/A

4

4


N/A

4

8


N/A

4

12

Note: To enable HS RACH allocation, theRAN1913: High Speed Cell_FACHfeature has to be activated in the cell. RACH or HS RACH peak throughputs are not increased by this feature, however the average utilization of RACH/HS RACH can improve.

128

©2016Nokia

DN09203161Issue:02



The preamble signatures are signaled to BTS over NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST (HS-RACH) and NBAP: COMMON TRANSPORT CHANNEL SETUP REQUEST (RACH) messages. Total amount of signatures is indicated to BTS by NBAP: CONFIGURATION DATA (Private NBAP message). BTS indicates its capability for using the RAN2902: RACH Capacity Increase feature in the NBAP: CAPABILITY INDICATION (Private NBAP message). The operator can check if BTS is capable of using the RAN2902: RACH Capacity Increase feature by looking up the value of theBTSRACHCapaIncCapability WBTS parameter. The signatures in use are broadcast to UE in SIB5/SIB5bis. For more information, see 3GPP TS 25.433 UTRAN Iub interface Node B Application Part (NBAP) signalling .

g

Note: Certain configurations of: • • • •

Cell range ( cellRange WCEL parameter) Number of cells in Local Cell Group Number of signatures in BTS ( RACHPreambleSignatures WCEL parameter) Rx diversity

impact the Baseband available capacity since more resources for Common Control Channels (CCCH) processing is needed. For more information, see Common Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband .

3.10.3

RAN2902 System impact Interdependencies between features This feature improves performance of the following features: • RAN1913: High Speed Cell_FACH • RAN2518: High Speed Cell_FACH Enhanced Impact on interfaces This feature reduces interference on the Uu interface in the uplink direction. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity Certain configurations of:

•

Cell range ( cellRange WCEL parameter) Number of cells in Local Cell Group Number of signatures in BTS ( RACHPreambleSignatures WCEL parameter)

•

Rx diversity

• •

impact the Baseband available capacity since more resources for Common Control Channels (CCCH) processing is needed. For more information, seeCommon Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband .

3.10.4

RAN2902 Reference data Requirements

DN09203161Issue:02

©2016Nokia

129


Table 54 RAS

WCDMA 16



mc R N C

RNC16

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2

MS C



WBTS16


WBTS16

S GSN


Under planning

MGW


UE


This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms Table 55

Existing alarms related to RAN2902

A l arm ID

A l ar m n a me

7775

INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

3325

INCONSISTENCY IN CONFIGURATION PARAMETERS

Measurements and counters Table 56

130


C o u n t e rI D M5000C455

C o u n t e rn a m e CONFIGURED R99 RACH SIGNATURES

Me as u re me n t HSPA in WBTS

M5000C456

NUMBER OF SUCCESSFULLY ACKNOWLEDGED HSPA in WBTS R99 RACH PREAMBLES

M5000C457

NUMBER OF NEGATIVELY ACKNOWLEDGED R99 RACH PREAMBLES

HSPA in WBTS

M5000C458

NUMBER OF SUCCESSFULLY DECODED R99 RACH MESSAGES

HSPA in WBTS

M5000C459

NUMBER OF UNSUCCESSFULLY DECODED R99 RACH MESSAGES

HSPA in WBTS

M5000C460

CONFIGURED HS-RACH SIGNATURES

M5000C461

NUMBER OF SUCCESSFULLY ACKNOWLEDGED HSPA in WBTS HS-RACH PREAMBLES

M5000C462

NUMBER OF NEGATIVELY ACKNOWLEDGED HS-RACH PREAMBLES

HSPA in WBTS

M5000C463

NUMBER OF SUCCESSFULLY DECODED HSRACH MESSAGES

HSPA in WBTS

M5000C464

NUMBER OF UNSUCCESSFULLY DECODED HSRACH MESSAGES

HSPA in WBTS

M5000C465

R99 RACH SIGNATURES UTILIZATION - CLASS 1 HSPA in WBTS

M5000C466


©2016Nokia

HSPA in WBTS

DN09203161Issue:02


Table 56


New counters introduced by RAN2902 (Cont.)

C o u n t e rI D


Me as u re me n t

M5000C467


M5000C468


M5000C469


M5000C470


M5000C471

HS RACH SIGNATURES UTILIZATION - CLASS 1

HSPA in WBTS

M5000C472


HSPA in WBTS

M5000C473


HSPA in WBTS

M5000C474


HSPA in WBTS

M5000C475


HSPA in WBTS

M5000C476


HSPA in WBTS




Man age d object

RACH and HS-RACH Preamble Signatures

RACHPreambleSignatures

WCEL

BTS RACH capacity increase capability

BTSRACHCapaIncCapability

WBTS

Table 58


High Speed RACH Enabled

A b b r e v i at e dn a m e HSRACHEnabled

M a n ag e d object

WCEL

Commands There are no commands related to this feature. Sales information Table 59 BSW /ASW

ASW

3.10.5

RAN2902 sales information S W c o mp o n e n t

RAN


RNC LK

Activating RAN2902: RACH Capacity Increase Purpose Follow this procedure to activate the RAN2902: RACH Capacity Increasefeature.

DN09203161Issue:02

©2016Nokia

131



Before you start Activating procedure requires cell locking. After the activation of this feature, there is no need to restart RNC or BTS. Activate the license for the RAN2902: RACH Capacity Increasefeature using RACH capacity increase license key. To set the feature state to ON, use the following command: •

for IPA-RNC:

•

for mcRNC:


Procedure

1


2


3


a) Go to the WCEL object using the following path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object

b) Right-click on the WCEL object and select Edit parameters.

c) On the System Info tab, set the RACHPreambleSignatures parameter to the desired value.

g

Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing. To enable HS RACH allocation, theRAN1913: High Speed Cell_FACHfeature has to be activated in the cell.

Unexpected outcome The cell cannot be unlocked. Troubleshooting actions If you have assigned HS RACH preamble signatures by setting the RACHPreambleSignatures parameter to one of the following values:

132

©2016Nokia

DN09203161Issue:02


•

3+3 RACH and HS RACH signatures 4+4 RACH and HS RACH signatures 4+8 RACH and HS RACH signatures

•


• •


ensure that theRAN1913: High Speed Cell_FACHfeature is activated in the cell and the RAN2902: RACH Capacity Increase feature state is ON. If you have assigned 8 RACH signatures by setting the value of the RACHPreambleSignatures parameter 8 RACH signatures, ensure that the RAN2902: RACH Capacity Increase featuretostate is ON.

Ensure that the BTS is capable of using the RAN2902: RACH Capacity Increase by checking the value of theBTSRACHCapaIncCapability WBTS parameter. Further information If alarm 3325: INCONSISTENCY IN CONFIGURATION PARAMETERS or 7775: INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS was raised, ensure that the defined number of signatures, cell Rx diversity, and cell range form a compatible configuration. In case of incompatible configuration, system sets the cell up with the default number of signatures (4 signatures) and the default cell range (20 km). For more information, seeCommon Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband.

3.10.6

Verifying RAN2902: RACH Capacity Increase Purpose Follow this procedure to verify if the RAN2902: RACH Capacity Increasefeature works properly in the network. Before you start Make sure you have access to the following applications: • •


Procedure

1


2

Start the M5000 HSPA in WB TS measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

DN09203161Issue:02

©2016Nokia

133


3


Wait until t he next full hour plus 10 mi nutes. For example, if you start the measurements at 11:22, the collected data is available in OMS at 12:10.

4


5

Check if the values of the following counters have been collected: • •

M5000C455: CONFIGURED R99 RACH SIGNATURES M5000C460: CONFIGURED HS-RACH SIGNATURES


Expected outcome The values of counters M5000C455 and M5000C460 match the number of RACH and HS RACH signatures configured using theRACHPreambleSignatures parameter. Unexpected outcome The values of counters M5000C455 and M5000C460 do not match the number of RACH and HS RACH signatures configured using theRACHPreambleSignatures parameter. Troubleshooting actions Ensure that theRAN1913: High Speed Cell_FACHfeature is activated in the cell if you assigend any HS RACH signatures. Ensure that the BTS is capable of using theRAN2902: RACH Capacity Increase feature by checking the value of theBTSRACHCapaIncCapability WBTS parameter. If alarm 3325: INCONSISTENCY IN CONFIGURATION PARAMETERS or 7775: INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS was raised, ensure that the defined number of signatures, cell Rx diversity, and cell range form a compatible configuration. In case of incompatible configuration, system sets the cell up with the default number of signatures (4 signatures) and the wcdmadefault cell range (20 km). For more information, seeCommon Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband .

3.10.7

Deactivating RAN2902: RACH Capacity Increase Purpose Follow this procedure to deactivate theRAN2902: RACH Capacity Increasefeature. Before you start Deactivating procedure requires cell locking.

134

©2016Nokia

DN09203161Issue:02



Procedure

1


2


3




c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 1, 2, 3, or 4 RACH signatures.

g

4

Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing.

Set the feature state to OFF. Use the following commands: •

for IPA-RNC:

•

for mcRNC:

ZW7M:FEA=5449:OFF; set license feature-mgmt code 0000005449 feature-adminstate off

Unexpected outcome The cell cannot be unlocked. Troubleshooting actions When the cell cannot be unlocked make sure that you have assigned no more than four RACH signatures and none of the HS RACH signatures.

3.10.8

Testing RAN2902: RACH Capacity Increase Purpose

g

DN09203161Issue:02

Note: It is strongly recommended to test this feature in a live network to observe network performance improvement.

©2016Nokia

135



Before you start Testing procedure requires cell locking. There is no need to restart RNC or BTS. Procedure

1


2


3

Deactivate t he RAN1913: High Speed Cell_FACHfeature using the HSRACHEnabled WCEL parameter. For detailed instructions, seeDeactivating RAN1913: High Speed Cell_FACH .

4




c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 4 RACH signatures.

g


5


6

Start the M5000 HSPA in WB TS measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

7

Wait until t he next full hour plus 10 mi nutes. For example, if you start the measurements at 11:22, the collected data is available in OMS at 12:10.

136

©2016Nokia

DN09203161Issue:02



8


9

Check the values of all counters in the range M5000C455–C476 Expected outcome •

The value of the M5000C455 counter is 4.

•

The value of the M5000C460 counter is 0. Values of counters in the range M5000C461–C464are 0. Values of counters in the range M5000C471–C476are 0.

• •

10 In OMS Element Manager, reconfigure the WCEL object: Sub-steps



c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 8 RACH signatures.

g


11 In the RNW Measurement Management application, start the M5000 HSPA in WBTS measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

12 Wait until the next full hour plus 10 minutes. For example, if you start the measurements at 12:22, the collected data is available in OMS at 13:10.

13 In the the RNW Measurement Presentation application, check the values of all counters in the range M5000C455–C476 Expected outcome

DN09203161Issue:02

©2016Nokia

137


• • • • •

•


The value of the M5000C455 counter is 8. The value of the M5000C460 counter is 0. Values of counters in the range of M5000C461–C464 are 0. Values of counters in the range of M5000C471–C476 are 0. Values of counters M5000C456and M5000C458 are higher in comparision to results from step 8. Values counters results of from step 8.M5000C457and M5000C459 are lower in comparision to

Further information Counters M5000C465–C470 represent the percentage of R99 RACH signatures utilization. The higher utilization class, the higher load for R99 RACH signatures. Enabling more signatures for use should be reflected by lower R99 RACH signatures utilization and, consequently, a decrease of utilization class.

g

Note: These predictions are based on the assumption that traffic load in the cell is constant.

14 Activate t he RAN1913: High Speed Cell_FACHfeature using the HSRACHEnabled WCEL parameter. For detailed instructions, seeActivating RAN1913: High Speed Cell_FACH .




c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 4+4 RACH and HS RACH signatures.

g

138


©2016Nokia

DN09203161Issue:02



16 In the RNW Measurement Management application, start the M5000 HSPA in WBTS measurement.


18 In the the RNW Measurement Presentation application, check the values of all counters in the range M5000C455–C476 Expected outcome • • • •

g

The value of the M5000C455 counter is 4. The value of the M5000C460 counter is 4. Values of counters in the range M5000C461–C464 are different than 0. Values of counters in the range M5000C471–C476 are different than 0. Note: These predictions are based on the assumption that UEs with HS RACH support are present in the cell.




c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 4+12 RACH and HS RACH signatures.

g


20 In the RNW Measurement Management application, start the M5000 HSPA in WBTS measurement.


DN09203161Issue:02

©2016Nokia

139



22 In the the RNW Measurement Presentation application, check the values of all counters in the range of M5000C455–C476. Expected outcome • • • • • •

The value of the M5000C455 counter is 4. The value of the M5000C460 counter is 12. Values of counters in the range of M5000C456–C459 aresimilar to results from step 16. Values of counters in the range of M5000C465–C470 aresimilar to results from step 16. Values of counters M5000C461and M5000C463 are higher in comparision to results from step 16. Values of counters M5000C462and M5000C464 are lower in comparision to results from step 16.

Further information Counters M5000C465–C470 represent the percentage of R99 RACH signatures utilization. The higher utilization class, the higher load for R99 RACH signatures. Enabling more signatures for use should be reflected by lower R99 RACH signatures utilization and, consequently, a decrease of utilization class.

g

Note: These predictions are based on the assumption that in the cell the traffic load is constant and UEs with HS RACH support are present.

3.11 RAN2892: WCDMA-LTE Load Balancing Introduction to the feature With RAN2892: WCDMA-LTE Load Balancing feature, all traffic steering actions towards high-loaded LTE cells are suspended.

3.11.1

RAN2892 Benefits End-user benefits Blocking of redirections and handovers to high-loaded LTE cells improves the end-user experience. Operator benefits Load balancing between WCDMA and LTE is needed when LTE network starts to get high-loaded. Preventing the redirection and handover attempts to high-loaded LTE cells reduces the need for further redirections and handovers.

140

©2016Nokia

DN09203161Issue:02


g

Note: This feature is beneficial only in the following cases: •

In the operator's network the LTE1357: LTE-UTRAN load balancingfeature (or other feature supporting the 'Reduce Load in Serving Cell' cause value in RANAP: RELOCATION REQUEST message) and at least one of the following WCDMA RAN features are enabled: – – –

•

3.11.2


RAN2264: Smart LTE Handover RAN2717: Smart LTE Layering RAN2980: Measurementbased LTE Layering

In the operator's network the LTE57: Inter RAT handover from UTRANfeature (or other feature supporting the 'No Radio Resources Available in Target cell' cause value in RANAP: RELOCATION PREPARATION FAILURE message) and the RAN2264: Smart LTE Handoverfeature are enabled.

RAN2892 Functional description The RAN2892: WCDMA-LTE Load Balancingfeature prevents redirections and handovers from WCDMA layer to high-loaded LTE cells. WCDMA to LTE traffic steering is enabled by the following features:

•

RAN2264: Smart LTE Handover RAN2717: Smart LTE Layering

•

RAN2980: Measurement based LTE Layering

•

When high load of LTE cell is identified, redirections and handovers from WCDMA to this LTE cell are stopped and a penalty timer for that cell is started. After the penalty timer expires, RNC returns to the normal traffic steering. The penalty timer is operator-tunable and controlled with thePenaltyTimerLTELoadHo RNMOBI parameter. High load in LTE cells is identified when: •

g

Note: Sending the RANAP message with the 'Reduce Load in Serving Cell' cause value in case of LTE to WCDMA handover is provided by the LTE1357: LTE-UTRAN load balancingfeature. •

g

LTE eNodeB initiates handover toWCDMA due to load reasons and the target RNC receives RANAP: RELOCATION REQUEST with the 'Reduce Load in Serving Cell' cause. This is indicated by the non-zero value of theRANAPCause1LTELoadInHo and/or the RANAPCause2LTELoadInHo RNMOBI parameter.

WCDMA initiates handover to LTE cell which experiences high load andeNodeB rejects the handover due to load reasons. Source RNC receives RANAP: RELOCATION PREPARATION FAILURE message with the 'No Radio Resources Available in Target cell' cause. This is indicated by the non-zero value of the RANAPCause1LTELoadOutHo and/or the RANAPCause2LTELoadInHo RNMOBI parameter. Note: Sending the RANAP message with 'No Radio Resources Available in Target cell' cause value in case of WCDMA to LTE handover rejection is provided by the LTE57: Inter RAT handover from UTRANfeature.

If the RNC receives another high-load indication from the LTE cell before the penalty timer has expired, the penalty timer is restarted for that cell.

DN09203161Issue:02

©2016Nokia

141



When redirection from WCDMA to LTE is initiated, the under-penalty LTE cells belonging to the LTE frequency layers selected for redirection are signaled to UE in the RRC CONNECTION RELEASE message asblacklisted cells. While attempting to switch to the suitable LTE cell, UE does not consider any of the under-penalty cells. The source RRM Handover Control entity informs all the other RRM Handover Control entities in the RNC about the under-penalty LTE cells.

142

©2016Nokia

DN09203161Issue:02


Figure 5


Overview of the RAN2892: WCDMA-LTE Load Balancing feature in Nokiabased radio network. RAN2176: LTE PS Handoveractivated + RAN2892: Dynamic WCDMA-LTE Load Balancing activated

LTE57: Inter RAT handover from UTRAN activated + WCDMA to LTE handover failure due to high load of LTE cell

AND/OR

LTE1357: LTEUTRAN load balancing activated + LTE to WCDMA handover request due to high load of LTE cell

Cell ID

Cell ID

LTE cell overload indication

Penalty timer start (or restart if already running) for high-loaded LTE cells

Handover from WCDMA to LTE RAN2264: ( Smart LTE Handover) is not initiated if target LTE cellis under penalty due to high load. Redirection from WCDMA to LTE RAN2717: ( Smart LTE Layering, RAN2980: Measurement BasedLTE Layering) is prevented if all qualified neighboring LTE cells on all target frequencies are under penalty duetotoLTE highsystem load . Otherwise, UEs commanded to redirect receive a list of the neighboring under-penalty LTE cells belonging to the target LTE frequency as a blacklist.

g

DN09203161Issue:02

Note: Some early Rel-8 UEs have problems during e-UTRA Compressed Mode measurements. For more information on this issue, seeTechnical Support Note 149, section 5.20, available inProduct Information Center.

©2016Nokia

143


3.11.3


RAN2892 System impact Interdependencies between features This feature requires that the following feature is activated in RNC: •

RAN2176: LTE PS Handover

This feature is beneficial only in the following cases: •


•



Impact on interfaces This feature impacts Iu interface. Reduced number of redirections and handovers results in reduced signaling load. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature prevents the redirection and handover attempts to high-loaded LTE cells and therefore reduces need for further redirections and handovers.

3.11.4


WCDMA 16


mc R N C

RNC16

mcRNC16

OMS

NetAct

WCDMA OMS 16

NetAct 16.2

MS C



Support not required S GSN






3GPP Rel-8

This feature does not require any new or additional hardware. Alarms

144

©2016Nokia

DN09203161Issue:02



There are no alarms related to this feature. Measurements and counters Table 61


C o u n t e rI D

g


Me as u re me n t

M1010C270

INCOMING HANDOVERS FROM LTE DUE TO LTE Inter System Hard CELL LOAD Handover

M1010C271

LTE ISHO PREPARATION FAIL DUE TO LTE CELL Inter System Hard LOAD Handover

M1010C272

BLOCKED HANDOVERS TO LTE DUE TO LTE CELL LOAD


M1010C273

BLOCKED REDIRECTIONS TO LTE DUE TO LTE CELL LOAD


M1006C322

RRC CONN REL WITH BLACKLISTED LTE CELLS RRC signalling

Note: Along with the M1006C322: RRC CONN REL WITH BLACKLISTED LTE CELLS counter update, one of the following counters is also updated: M1006C262, M1006C263, M1006C291, M1006C310. Table 62


C o u n t e rI D


Me as u re me n t

M1006C262

RRC CONN RELEASE LTE REDIR DUE TO INACTIVITY

RRC signalling

M1006C263

RRC CONN RELEASE LTE REDIR DUE TO CH TYPE SWITCH

RRC signalling

M1006C291

RRC CONN RELEASE LTE REDIR DUE TO CS CALL RELEASE

RRC signalling

M1006C310

RRC CONN RELEASE LTE REDIR IN DCH

RRC signalling



DN09203161Issue:02


Man age d object

WCDMA LTE Load Balancing Enabled

WCDMALTELoadBalEnabled

WCEL

RANAP Cause 1 LTE Load Incoming Handover

RANAPCause1LTELoadInHo

RNMOBI

RANAP Cause 2 LTE Load Incoming Handover

RANAPCause2LTELoadInHo

RNMOBI

RANAP Cause 1 LTE Load Outgoing Handover

RANAPCause1LTELoadOutHo

RNMOBI

RANAP Cause 2 LTE Load Outgoing Handover

RANAPCause2LTELoadOutHo

RNMOBI

©2016Nokia

145


Table 63


New parameters introduced by RAN2892 (Cont.) F u l ln a me


Penalty Timer LTE Load Handover

Table 64

PenaltyTimerLTELoadHo

M an age d object

RNMOBI



Mobject an ag e d

RNCOptions

RncOptions

RNC

ADJE Identifier

ADJEId

ADJE

Tracking Area Code

AdjeTAC

ADJE


RAN2892 sales information

B S W /A S W

ASW


RAN


RNC LK

3.11.5 Activating RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to activate the RAN2892: WCDMA-LTE Load Balancingfeature. Before you start After the activation of this feature, there is no need to restart RNC or BTS. Activation procedure does not require cell locking. This feature requires that the following feature is activated in RNC: •

RAN2176: LTE PS Handover

This feature is beneficial only in the following cases: •


•

146



©2016Nokia

DN09203161Issue:02



Activate the license for the RAN2892: WCDMA-LTE Load Balancingfeature using WCDMA-LTE Load Balancinglicense key. To set the feature state to ON, use the following command: •

for IPA-RNC:

•

for mcRNC:


To enable WCDMA to LTE load balancing, WCDMA cells need to have neighboring LTE cells defined with the ADJE object. The ADJE object is required to activate RAN2264: Smart LTE Handover feature. If the RAN2264: Smart LTE Handoverfeature is not active in the cell, then the operator needs to configure ADJE object. Creating ADJE object in the cell does not require license or activation of theRAN2264: Smart LTE Handover feature. Configuring ADJE object requires assigning values to the following parameters: •

AdjLIdentifier

•

AdjeCellId

•

AdjeENodeBId

•

AdjeMCC

•

AdjeMNC

•

AdjeMNCLength

•

AdjePhysicalCellId

•

AdjeTAC

The value of the AdjeTAC parameter is not used by theRAN2892: WCDMA-LTE Load Balancing feature.

g

DN09203161Issue:02

Note: Some early Rel-8 UEs have problems during e-UTRA Compressed Mode measurements. For more information on this issue, seeTechnical Support Note 149, section 5.20, available inProduct Information Center.

©2016Nokia

147



Procedure

1


2


3




c) On the Handover Control tab, set the value of the WCDMALTELoadBalEnabled parameter to Enabled.

3.11.6 Verifying RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to verify if the RAN2892: WCDMA-LTE Load Balancingfeature works properly in the network. Before you start Activate the following features: •

in WCDMA cell: –

•

RAN2264: Smart LTE Handover

in LTE cell, which is defined in the ADJE object of the WCDMA cell: –

–

LTE57: Inter RAT handover from UTRAN or other feature supporting the 'No Radio Resources Available in Target cell' cause value in RANAP: RELOCATION PREPARATION FAILURE message LTE1357: LTE-UTRAN load balancing or other feature supporting the 'Reduce Load in Serving Cell' cause value in RANAP: RELOCATION REQUEST message

Make sure you have access to the following applications: • •

148


©2016Nokia

DN09203161Issue:02



Procedure

1


2

Start the M1006 RRC signalling and M1010 Inter System Hard Handover measurements. Wait for the measurement interval to begin.

g

Note: In case of 15-minute interval, data collection starts every quarter. For example 11:00, 11:15, 11:30, 11:45. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3

Generate a high load in the LTE cell defined in the ADJE object of the WCDMA cell. The purpose of this step is to trigger handovers from LTE to WCDMA due to high load in the LTE cell.

4

During the high load of LTE cell, trigger WCDMA to LTE handover. The purpose of this step is to obtain rejection of WCDMA to LTE handover attempt due to high load in the LTE cell. Triggers for WCDMA to LTE handover of HSDPA users are specified in theRAN2264: Smart LTE Handover feature description.

5


6

Check if the values of the following counters have been collected: • • •

M1010C270: INCOMING HANDOVERS FROM L TE DUE TO LTE CELL LOAD M1010C271: LTE ISHO PREPARATION FAIL DUE TO LTE CELL LOAD M1010C272: BLOCKED HANDOVERS TOLTE DUE TO LTE CELL LOAD


Expected outcome The values of the following counters have increased: • • •

M1010C270: INCOMING HANDOVERS FROM L TE DUE TO LTE CELL LOAD M1010C271: LTE ISHO PREPARATION FAIL DUE TO LTE CELL LOAD M1010C272: BLOCKED HANDOVERS TOLTE DUE TO LTE CELL LOAD

Further information

DN09203161Issue:02

©2016Nokia

149



Verifying the RAN2892: WCDMA-LTE Load Balancingfeature can be also conducted with RAN2717: Smart LTE Layeringor the RAN2980: Measurement based LTE Layering feature instead of the RAN2264: Smart LTE Handoverfeature. Then in step 4, during the high load of LTE cell, trigger WCDMA to LTElayering procedure. Triggers for WCDMA to LTE layering are specified in theRAN2717: Smart LTE Layeringand the RAN2980: Measurement based LTE Layeringfeature descriptions. The purpose of this step is to obtain sending to UE the RRC CONNECTION RELEASE message with EUTRA Target Info IE containig blacklisted LTE cell that is in the high load. If the RAN2717: Smart LTE Layering and/or the RAN2980: Measurement based LTE Layeringfeatures are used for verification, the values of counters M1006C322: RRC CONN REL WITH BLACKLISTED LTE CELLS and M1010C270: INCOMING HANDOVERS FROM LTE DUE TO LTE CELL LOAD are expected to increase.

3.11.7 Deactivating RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to deactivate theRAN2892: WCDMA-LTE Load Balancingfeature. Procedure

1


2


3




c) On the Handover Control tab, set the value of the WCDMALTELoadBalEnabled parameter to Disabled.

150

©2016Nokia

DN09203161Issue:02


Telecom features

4 Telecom features 4.1 RAN3086: CSFB with RIM Introduction to the feature The RAN3086: CSFB with RIM feature introduces RAN Information Management (RIM) signaling support for circuit-switched call fallback (CSFB). With the RIM procedure, LTE evolved Node B (eNB) is able to retrieve 3G System Information (SI) from RNC.

4.1.1

RAN3086 Benefits End-user benefits This feature improves the overall end-user experience by accelerating a voice call setup time. Operator benefits This feature enables exchanging information between different Radio Access Technologies via Core Network. With RIM, circuit-switched call fallback is faster.

4.1.2

RAN3086 Functional description The RAN3086: CSFB with RIM feature introduces the RAN Information Management (RIM) procedure to RNC. The RIM procedure is a 3GPP standard. With the RAN3086: CSFB with RIM feature, RNC supports the UTRA System Information (SI) RIM procedure. The RIM procedure enables exchanging information between different Radio Access Technologies via the Core Network. The RIM UTRA procedure signaling happens between LTE (eNB) and RNC. The eNB requests the Single/Multiple Reporting from RNC's reporting cell. The RIM PDUs (RAN INFORMATION REQUEST/RAN INFORMATION/RAN INFORMATION ACK) are sent between the eNB and RNC inside the DIRECT INFORMATION TRANSFER via the CN. For more information, seeSignaling of RIM UTRA SI procedurefigure and Signaling of RIM UTRA SI Procedure Errorfigure.

DN09203161Issue:02

©2016Nokia

151

Telecom features


Figure 6

Signaling of RIM UTRA SI procedure

RNC

eNB eNB request Single or Multiple Reporting from RNC’s cell or Stops the Multiple Report

RAN INFORMATION REQUEST Single Report/Multiple Report/Stop

RAN INFORMATION Single Report/Initial Multiple Report/Stop

RAN INFORMATION Multiple Report RAN INFORMATION ACK

RAN INFORMATION End

RAN INFORMATION ACK

152

©2016Nokia

RNC updates SIB modification of a cell with Multiple Report

RNC terminates the Multiple Reporting (for example reporting cell is deleted in RNC)

DN09203161Issue:02


Figure 7

Telecom features

Signaling of RIM UTRA SI Procedure Error

RNC

eNB RAN INFORMATION REQUEST/ RAN INFORMATION ACK

RAN INFORMATION ERROR

eNB notices RIM protocol error in incoming message

eNB notices RIM application error in incoming message

RNC notices RIM protocol error in incoming message

RAN INFORMATION

RAN INFORMATION ERROR

RAN INFORMATION RAN INFORMATION APPLICATION ERROR

RAN INFORMATION ACK

RAN INFORMATION REQUEST Single Report/Multiple Report

RAN INFORMATION Single Report/Initial Multiple Report (Application Error Container)

RNC notices RIM application error in incoming message

With the UTRA SI RIM procedure, LTE eNB can inquire cell-specific System Information from RNC. The RNC replies to the request with the relevant System Information Block (SIB) and the Master Information Block (MIB) of a particular cell. RNC includes the MIB, SIB1, SIB3, SIB5, SIB7 in UTRA SI RIM procedure. LTE eNB uses the RNC's System Information for directing the UE to the WCDMA cell with RRC CONNECTION RELEASE (UTRA BCCH container, Rel-9) message, so that the UE reads the SI of the WCDMA cell from the release message. During a circuit-

DN09203161Issue:02

©2016Nokia

153

Telecom features


switched call fallback (CSFB), UE indicates that it establishes the connection towards the RNC based on the SI from UTRA SI RIM procedure. The indication is included in the RRC CONNECTION REQUEST (System Information Stored Indicator, Rel-9). For more information about the RIM procedure, see3GPP TS 48.018 General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP).

4.1.3

RAN3086 System impact Interdependencies between features The Deferred SIB reading functionality of theRAN2746: Fast HSPA Mobilityfeature is recommended to be used with theRAN3086: CSFB with RIM feature. With Deferred SIB reading, the large SIB11 is not needed in RAN INFORMATION report from RNC, as the UE is allowed to send RRC Connection Request without reading SIB11. The following Access Class Restriction features impact working of the RAN3086: CSFB with RIM feature: • • • •

RAN801: Radio Network Access Regulation Function RAN1167: Domain Specific Access Class Restriction RAN2480: Automatic Access Class Restriction RAN3018: BTS Load Based AACR

If any of the Access Class Restriction (ACR) features is active, it updates the SIB3 with cell's access class restriction information. The frequency of updating is 1-6 times/minute. Depending on the ACR feature, the access class restriction procedure is triggered automatically due to the detected overload or manually by the user. This increases the signaling ofRAN3086: CSFB with RIM feature between the RNC and LTE eNB. The increased signaling is seen in a number of INFORMATION DIRECT TRANSFER/RAN INFORMATION (Multiple Report) sending from RNC to LTE and the acknowledge for each message DIRECT INFORMATION TRANSFER/RIM INFORMATION ACK. Impact on interfaces The RAN3086: CSFB with RIM feature impacts interfaces as follows: •

Iu –

A new RANAP:INFORMATIONDIRECT TRANSFER messageis introduced to carry UE – CN signaling messages over the Iu Interface.

Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

4.1.4


154

©2016Nokia

DN09203161Issue:02


Table 66 RAS

WCDMA 16

Telecom features


RNC16

mc R N C


mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2


MS C



S GSN


SG8.0

MGW



3GPP Rel-9

This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 67


RIM UTRA System Information Application Enabled

Table 68

Deferred Measurement Control Reading

RNFC

RIMUtraSIEnab

A b b r e v i a t e dn a m e DefMeasCtrlReading

Man age d object

WCEL

PRFILE parameters related to RAN3086 P a r a m e t e rI D

002:2306

g

Man age d object

Existing parameters related to RAN3086 F u l ln a me

Table 69


P a r a m e t e rn a m e CSFB_WITH_RIM

Note: For information on 002:2306 CSFB_WITH_RIM PRFILE parameter settings, see PRFILE Descriptions. Commands There are no commands related to this feature. Sales information

DN09203161Issue:02

©2016Nokia

155

Telecom features


Table 70


BSW/ASW

ASW

4.1.5

S W comp on en t

RAN


RNC LK

Activating RAN3086: CSFB with RIM Purpose Follow this procedure to activate the RAN3086: CSFB with RIM feature. Before you start After activating this feature there is no need to restart RNC or BTS. Activating procedure does not require cell-locking and does not cause downtime in the network. Make sure you have access to the following applications: • •

OMS Element Manager Application Launcher

Install the license key for the RAN3086: CSFB with RIM feature in the RNC and set the feature state to ON. The feature code for this feature is 5418. To set the feature state to ON, use the following command: •

for IPA-RNC:

•

for mcRNC:


For information on managing licenses, seeLicensing. Before activating this feature the DefMeasCtrlReading WCEL parameter must be set to Enabled.

g

156

Note: For enabling the DefMeasCtrlReading parameter, license of the RAN2746: Fast HSPA Mobilityfeature is required.

©2016Nokia

DN09203161Issue:02


Telecom features

Procedure

1


2


3

Expand the RNC and expand the RNFC object.

4


a) Right-click on the RNFC object and select Edit par ameters.

b) Set the RIMUtraSIEnab parameter value to Enabled.

g

5

4.1.6

Note: If all the needed license/feature states are not active (On), the system does not allow to set the RIMUtraSIEnab RNFC parameter to valueEnabled. Otherwise the feature is able to be activated and deactivated without any locking/unlocking of any objects, which means that the new value shall be use after the change.


Verifying RAN3086: CSFB with RIM Purpose Follow this procedure to verify if the RAN3086: CSFB with RIM works properly in the network. Before you start Message monitoring must be used to verify the message flow between the eNB and the RNC. Procedure

DN09203161Issue:02

1

Generate/expect a RAN INFORMATION REQUEST (Single Report) or RAN INFORMATION REQUEST (Multiple Report) from eNB via Core Network in IU:DIRECT INFORMATION TRANSFER.

2

Check that RNC has answered to the RAN INFORMATION REQUEST with RAN INFORMATION (Single Report) or RAN INFORMATION-REQUEST (Multiple

©2016Nokia

157

Telecom features


report) responses inside the IU:DIRECT INFORMATION TRANSFER towards Core Network. 3

Ensure that eNB and UE use the RIM information from RNC in the CSFB of the UE to the RNC, the UE is able to indicate it in the RNC in RRC:RRC CONNECTION REQUEST. The UE indicates it with the System Information Stored Indicator (Rel-9).

Expected outcome RNC replies with RAN INFORMATION to eNB via the Core Network. In CSFB, the UE informs the RNC in RRC CONNECTION REQUEST System Information Stored Indicatorthat it uses the system information from RIM procedure. Unexpected outcome RNC does not respond to the RAN INFORMATION REQUEST or replies with RAN INFORMATION ERROR message.

4.1.7

Deactivating RAN3086: CSFB with RIM Purpose Follow this procedure to deactivate theRAN3086: CSFB with RIM feature.

158

©2016Nokia

DN09203161Issue:02


Telecom features

Procedure

1


2


3

Expand the RNC object then expand the RNFC object.

4


a) Right-click on the RNFC object and select Edit par ameters.

b) Set the RIMUtraSIEnab parameter value to Disabled.

5


Expected outcome • •

The RNC sends the RAN INFORMATION (End) to eNB. The RNC rejects the new RAN INFORMATION REQUESTs from eNB with RAN INFORMATION ERROR.

Unexpected outcome • •

The RNC does not send the RAN INFORMATION (End) to eNB. The RNC does not reject the new RAN INFORMATION REQUESTs from eNB with RAN INFORMATION ERROR.

Further information The RIM messages: RAN INFORMATION REQUEST, RAN INFORMATION, and RAN INFORMATION ERROR are sent inside the IU:DIRECT INFORMATION TRANSFER message.

4.2 RAN3082: Device Detection Introduction to the feature

The RAN3082: Device Detection feature enables device type detection in the RNC based on the IMEI Type Allocation Code (TAC) and Software Version Number (SVN) information. The UE model is detected based on the TAC and SVN part of the International Mobile Station Equipment Identity and Software Version Number (IMEISV) information requested from the UE.

DN09203161Issue:02

©2016Nokia

159

Telecom features


The RAN3082: Device Detection feature introduces Whitelist and Blacklist mechanisms based on the IMEI TAC and SVN information. Whitelisting a feature means that only the listed IMEI (TAC, SVN) codes are allowed to use the feature, like for exampleContinuous Packet Connectivity (CPC). Blacklisting a feature means that defined IMEI codes are not allowed to use the feature.

4.2.1

RAN3082 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature permits to control the feature or functionality usage in the network as per UE model basis. It enables to quickly rule out some misbehaving UEs from the feature usage in case problems are seen in the network. The trialing period can be easily organized for a certain feature with a limited set of UE models, should such a need arise.

4.2.2

RAN3082 Functional Description The RAN3082: Device Detection feature enables device type detection in the RNC based on the International Mobile Equipment Identity (IMEI) Type Allocation Code (TAC) and Software Version Number (SVN) information. A certain feature or functionality usage can be allowed or blocked for a set of UE models based on device detection framework. The IMEI information retrieval for the device detection is performed during the PS RAB setup phase. Alternatively, if the Core Network has the IMEI query enabled, the RNC is able to retrieve the IMEISV information from the related Non-Access Stratum (NAS) signaling. Whitelist and Blacklist functionality The RAN3082: Device Detection feature introduces Whitelist and Blacklist mechanisms based on the IMEI TAC and SVN information. Whitelisting and Blacklisting is done per feature. A specific feature or functionality under the control of Device Detection feature framework can be either Whitelisted or Blacklisted at the time. Whitelisting a feature means that only the listed IMEI (TAC, SVN) codes are allowed to use the feature. However, the listed UE types can use the feature only if they have the capability. By Whitelisting a feature, operator can limit the UE types using it to only a few chosen models. A blacklist functionality contains IMEIs (TAC+SVN) codes that are not allowed to use the feature. Blacklisted UE types are blocked from using the feature even if they have a capability to use it. By Blacklisting a feature operator can rule out misbehaving UEs from using the feature. The feature or functionality allocations can be controlled with the RAN3082: Device Detection framework. The framework always contains a possibility to operate Whitelist or Blacklist based definitions. The feature can be kept available for the UE models that operate properly with the feature. At the same time the feature can be blocked from the UE models that for some reason do not work correctly with the given feature even though claiming to have the capability. Supported RAN features

160

©2016Nokia

DN09203161Issue:02


• •

Telecom features

RAN1644: Continuous Packet Connectivity RAN3218: Enhanced Cell Change from HSPA to 2G

Generic IMEI query Additionally for the UE model information collection, RNC provides a generic IMEI query functionality for operator. It can be used, for example together with Traffica connected to RNC, to collect UE model behavior information from the network. The generic IMEI query is available without a license control. The overallconcept operation environment is presented inThe IMEI collection and operation figure. The left side of the figure presents the means to feature collect the UE behavior information collection from the network. The operator may either directly filter out a specific UE model based on the official IMEI list provided by the corresponding authorities. Further the information can be collected with monitoring the network functionality via the tools like Traffica connected to the RNC. The detailed message monitoring and analysis based on that can be performed with L3 Data Collector (Megamon) system. Figure 8

The IMEI collection and feature operation concept

Manage/RAN3082

Monitor, collect/Generic TÜV TAC

Full TAC list

NetAct L3 Data Collector (Monitoring)

Equipment Identity Register (EIR)

NWI3 CM plan interface

TAC list collection for example with Excel

GUI

CN Traffica (IMEI query enabled at CN)

RNW plan XML

OMS BTS O&M

Traffica reporting with IMEI information (xx% out of calls)

RNC Traffica (IMEI delivery from RNC)

RNC

WDEV object class The RAN3082: Device Detection feature implements a new RNW object class: WCDMA Device Detection (WDEV). The WDEV object class contains the attributes for the UE Type Allocation Code (TAC) and Software Version Number (SVN) based on the feature Blacklist and Whitelist functionality. The WDEV object class is located to the main level of the RNC object hierarchy and is present in the local UI and within the RNW plan interface. Measurement type for device detection

DN09203161Issue:02

©2016Nokia

161

Telecom features


A new measurement type: M1029 Device Detection is introduced where the object id includes the feature information for the Whitelist/Blacklist counter. The target object of the measurement is feature code that refers to the blacklisted or whitelisted feature. A feature code zero is used for counter M1029C0. The measurement is always available regardless of Whitelist/Blacklist features, but no specific statistics data is produced when blacklisting is not activated.

4.2.3

RAN3082 System impact Interdependencies between features The RAN3082: Device Detection feature framework is applied generically to all new applicable features in RRM and Telecom area. The applicable features are specified and implemented to be ready to support the device detection. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

4.2.4

RAN3082 Reference data Requirements Table 71: RAN3082 hardware and software requirementslists the software required for this feature. Table 71 RAS

WCDMA 16


mc R N C

RNC16

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2



MS C


S GSN







This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters Table 72: New counters introduced by RAN3082lists counters introduced with this feature.

162

©2016Nokia

DN09203161Issue:02


Table 72


C o u n t e rI D

g

Telecom features

C o u n t e rn a me

Me as u re me n t

M1029C0

IMEI QUERY SENT BY RNC

Device Detection

M1029C1

FEATURE WHITELIST OPERATIONS

Device Detection

M1029C2

FEATURE BLACKLIST OPERATIONS

Device Detection

Note: M1029 Device Detection is a new new measurement type. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 73: New parameters introduced by RAN3082lists parameters introduced with this feature. Table 73



WDEV

WDEVname

WDEVName

WDEV

List of TAC entries

TACList

WDEV

SVN software version number Whitelist features

SVN Whitelist

WDEV WDEV

Blacklist features

Blacklist

WDEV

Change origin

WDEVChangeOrigin

WDEV

WDEV control activation

WDEVControlEnabled

RNFC

IMEIQuery

g

A b b r e v i at e dn a m e WDEVId

WDEV identifier

IMEIQuery

RNC

Note: WCDMA Device Detection (WDEV) is a new object class. Table 74: Parameters modified by RAN3082lists parameters modified by this feature. Table 74


RNCOptions

A b b r e v i at e dn a m e RNCOptions


RNC


DN09203161Issue:02

©2016Nokia

163

Telecom features


Table 75


BSW/ASW

ASW

4.2.5

S W comp on en t

RAN


RNC LK

Activating RAN3082: Device Detection Purpose Follow this procedure to activate the RAN3082: Device Detection feature. Before you start After activating this feature there is no need to restart RNC. Activating procedure does not require cell-locking. This feature becomes active for the UEs connecting after the feature has been configured. The ongoing connections/calls are not affected. Ensure that the features that are to be controlled with theRAN3082: Device Detection feature are already running in the network. This feature is controlled by a license. For information on managing licenses, see Licensing. The feature code for this feature is 5586. To set the feature state toON, use the following command: •

for IPA-RNC:

•

for mcRNC:


The RAN3082: Device Detection feature is a capacity license controlled feature. The number of capacity steps corresponds to the number of simultaneously active Whitelist and Blacklist controlled features. The Blacklist/Whitelist activation consumes one capacity step. It is allowed to activate one Blacklist/Whitelist feature/functionality per one license capacity step. Maximum amount of capacity steps is 16. The upper capacity limit is defined via the Whitelist and Blacklist parameters bitmask length. The feature can be managed via the normal RNW configuration management interfaces: RNW local UI and NetAct. The feature planning related UE model and feature behavior information can be collected from various network and system monitoring tools like Traffica, L3 Data Collector, and the PM measurements providing overall information.

164

©2016Nokia

DN09203161Issue:02


Telecom features

Procedure

1


2


3


4

Configure the RNFC object. Sub-steps

a) Right-click on the RNFC object and select Edit parameters.

b) Set the value of the WDEVControlEnabled parameter to Enabled. The feature and UE control attributes within the WDEV instances do not have any effect to system behavior unless the feature main control parameter is enabled.

5

Expand the RNC.

6

Create the WDEV object instance(s). Sub-steps

a) Right-click on the RNC object and select Create New Object ► WDEV. Create the needed amount of the WDEV objects with planned TAC, SVN and feature control information. The WDEV object instance contains Whitelist and Blacklist control parameters against which UE models defined within the TAC list are being controlled.

g

Note: The same feature can be controlled via several WDEV instances. The TAC entries defined for a certain feature have to be unique in all WDEV instances containing the same feature control information. The new value is used for the next new calls after the parameter modification. The ongoing calls are not affected. Whitelist: RNC allows to use this feature only for the defined TAC values. Blacklist: RNC blocks the given feature use for the defined TAC values. A particular feature cannot be Blacklisted and Whitelisted simultaneously. The same bit value cannot be set to value 1 in both Whitelist and Blacklist bit masks. This applies to all configured WDEV instances.

DN09203161Issue:02

©2016Nokia

165

Telecom features


7

Configure the WDEV object. Sub-steps

a) Right-click on the WDE V object and sele ct Edit par ameters.

b) Set the Whitelist parameter value as needed in relation to defined WDEV objects.

c) Set the Blacklist parameter value as needed in relation to defined WDEV objects.

8

4.2.5.1


Activating generic IMEI query in the RNC Purpose The RNC provides the option to collect the IMEI information along with the detailed network behavior monitoring via RNC Traffica. This can be used to collect additional UE behavior detailed monitoring data in the network. The generic IMEI information inquiry performed by the RNC can be activated via the RNC level parameter. RNC performs the IMEI query for the defined percentage of the RAB establishments. The RNC query is performed in addition to the CN-initiated IMEI queries. The RNC level IMEI query can be activated for example in case the query is not activated at the core network elements. RNC is able to retrieve the IMEI from the CNperformed queries providing the similar result with the RNC level query.

g

166

Note: The generic IMEI query functionality is available without any license.

©2016Nokia

DN09203161Issue:02


Telecom features

Before you start Procedure

1


2


3

Configure the RNC object. Sub-steps

a) Right-click on the RNC obje ct and select Edit parameters.

b) Set the value of the IMEIQuery parameter within range 1-100. The IMEIQuery parameter provides the control over generic IMEI query performed by the RNC after RAB establishment.

4

4.2.6


Verifying RAN3082: Device Detection Purpose Follow this procedure to verify that the activation of the RAN3082: Device Detection feature has been successful. Before you start Define the set of UEs and features to be controlled with the RAN3082: Device Detection feature functionality. Plan both Whitelisted and Blacklisted features in order to validate the overall feature behavior. The features that are controlled with the device detection, have to be properly configured in the network.

DN09203161Issue:02

©2016Nokia

167

Telecom features


Procedure

1

Select the features to be controlled with the device detection. Sub-steps

a) Ensure that the features are configured and running in the network.

b) Check if the UEs are in the network where, for example, Blacklisted TAC codes correspond with to UE IMEI information.

2


3


4

Wait for the next 15-minutes interval to begin. The measurement interval then starts.

5

Make a PS call with the UE that is whitelisted or blacklisted. CPC black/whitelisting is only checked when making a PS call. Without a PS call there are no counter updates.

6


7


8

Check if any of the following counters have value greater than 0: • •

168

M1029C1 FEATURE WHITELIST OPERATIONS M1029C2 FEATURE BLACKLIST OPERATIONS

©2016Nokia

DN09203161Issue:02


Telecom features

For the Blacklist configuration the related counter should be updated according to the feature blocking operations the network system performs based on the device detection configuration.

Expected outcome The values of counters M1029C1 and M1029C2 are updated according to the Whitelist and Blacklist operations performed according to theRAN3082: Device Detection feature configuration.

4.2.6.1

Verifying generic IMEI query in the RNC Purpose Follow this procedure to verify that the activation of the IMEI query functionality has been successful. Procedure

1


2


3

Wait for the next 15-minutes interval to begin. The measurement interval then starts.

4

Make a PS call.

5


6


DN09203161Issue:02

©2016Nokia

169

Telecom features


7

Check if the following counter has value greater than 0: •

M1029C0 IMEI QUERY SENT BY RNC

Expected outcome The counter M1029C0 IMEI QUERY SENT BY RNC is updated by the system.

4.2.7

Deactivating RAN3082: Device Detection Purpose Follow this procedure to fully deactivate the RAN3082: Device Detection feature. Procedure

1


2


3


4


a) Right-click on the RNFC object and select Edit Parameters.

b) Set the value of the WDEVControlEnabled parameter value to Disabled.

5

4.2.7.1


Deactivating a Whitelist or Blacklist functionality Purpose Follow this procedure to deactivate a specific feature Whitelist or Blacklist functionality.

170

©2016Nokia

DN09203161Issue:02


Telecom features

Procedure

1


2


3

Expand the RNC object then expand the WDEV object.

4

Configure the WDEV object: Sub-steps

a) Right-click on the WDEV object and select Edit Parameters.

b) Set the feature-specific bit value of the Whitelist or Blacklist parameter to 0 to deactivate a specific feature control. The control has to be disabled in all related WDEV instances. The feature control does not affect already ongoing connections/calls.

5


Expected outcome The RAN3082: Device Detection feature does not control the feature use anymore.

4.2.7.2

Deactivating generic IMEI query in the RNC Purpose Follow this procedure to deactivate generic IMEI query functionality.

DN09203161Issue:02

©2016Nokia

171

Telecom features


Procedure

1


2


3

Configure the RNC object. Sub-steps

a) Right-click on the RNC obje ct and select Edit parameters.

b) Set the value of the IMEIQuery parameter to 0.

4

172


©2016Nokia

DN09203161Issue:02


Transmission and transport features

5 Transmission and transport features 5.1 RAN3112: mcRNC Integrated Ethernet Switching Introduction to the feature The Multicontroller RNC (mcRNC) has an option to aggregate Ethernet traffic from different external interface processing units (EIPU) within different box controller node (BCN) modules to a single 10 GE interface using the integrated Ethernet Switching. This feature provides new counters that measure both the backplane and the external interfaces Ethernet performance characteristics. These counters allow identifying possible bottlenecks for traffic switched among different BCN modules and assist in the proper connectivity dimensioning and design.

5.1.1

RAN3112 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows the operator to dimension the number of physical 10 GE interfaces to the required capacity of the mcRNC independently of the number of BCN modules and EIPU units conforming to the mcRNC setup. The traffic at the mcRNC external physical interfaces and backplane interfaces can be monitored via the generic PM framework. This provides a possibility to follow the interface utilization and react timely to the traffic increase by planning for the mcRNC connectivity. The backplane link load can be monitored via Ethernet Traffic counters, which allow the system/the operator to verify if the configuration works as intended also from the backplane link load point of view.

5.1.2

RAN3112 Functional description The mcRNC has an option to aggregate Ethernet traffic from different EIPU within different BCN modules to a single 10 GE interface using the integrated Ethernet Switching. This feature provides new counters that measure both the backplane and external interfaces Ethernet performance characteristics. These counters allow identifying possible bottlenecks for traffic switched among different BCN modules and assist in the proper dimensioning and design of the number of 10 GE interface to be used for the connection of the mcRNC to the site router. It provides the benefit to dimension the number of physical 10 GE interfaces to the required capacity of the mcRNC independently of the number of BCN modules and EIPU units conforming the mcRNC setup. The mcRNC provides solution to optimize the external connectivity based on the actual traffic data volume in the network while fully utilizing the processing capacity for the signaling-dominated traffic profile. Within the 10 GE connectivity optimized solution traffic from several EIPU units, that can be located to different BCN modules, can be aggregated to the shared 10GE port located in any BCN module. The physical interface Ethernet measurement supports 1 GE and 10 GE ports including the ports shared by several computing nodes. The RAN3112: mcRNC Integrated Ethernet Switchingfeature introduces new measurement type M805 to measure mcRNC Ethernet interface traffic.

DN09203161Issue:02

©2016Nokia

173



Using the 10 GE interfaces for external connectivity requires a capacity license, which is based on the number of 10 GE interfaces applied for the external connectivity. The mcRNC can support the BCN module front panel 1 GE and 10 GE physical port M805 measurement for the BCN-B HW module variant. TheM805 measurements are supported for all mcRNC capacity steps for all configured and active physical ports that are used for BCN external transport (SFP ports) and for the backplane connectivity. The M805 measurement type can be used even ifRAN3112: mcRNC Integrated Ethernet Switching feature is deactivated . Switch ports used for BCN internal traffic cannot be measured. The external interface SFP ports covered by this feature are the backplane ports from SFP+0 to SFP+6, and external connectivity port from SFP+11 to SFP+12 and SFP13 to SFP22, see Figure 9: mcRNC SFP ports. Figure 9

mcRNC SFP ports

The mcRNC provides new measurementM805 BCN Ethernet Statistics. The M805 BCN Ethernet Statistics measurement provides Ethernet layer statistics of mcRNC interfaces whose operational state is enabled. The object of the measurement is BCN/ETHPORT where BCN refers to the BCN module number and ETHPORT is the port identifier like SFP11.

5.1.3

RAN3112 System impact Interdependencies between features This feature implements the licenses forRAN2696: mcRNC 10 Gigabit Ethernet Based Network Connectivity feature. The 10 GE interfaces licenses are now under a capacitybased license referring to the number of 10 GE physical interfaces applied for the external connectivity (SFP+11 and SFP+12). Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools

174

©2016Nokia

DN09203161Issue:02



This feature has no impact on network and network element management tools. Impact on system performance and capacity This feature improves the current mcRNC solution to optimize the external connectivity based on the actual traffic data volume in the network.

5.1.4



RAS

I PA - R N C

mc R N C

WCDMA 16


mcRNC16

OMS

NetAct

WOMS16

NetAct 16.2

MS C










This feature is implemented for the BCN-B hardware. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults and reported alarms related to this feature. Commands There are no commands related to this feature. Measurements and counters Table 77


C o u n t eIrD

C o u n t en r a me

M805C0

etherStatsDropEvents

M805C1

etherStatsDropEvents

M805C2

etherStatsUndersizePkts

M805C3

etherStatsOversizePkts

M805C4

etherStatsFragments

M805C5

etherStatsJabbers

M805C6

etherStatsCollisions

M805C7

etherStatsPkts64Octets

M805C8

etherStatsPkts65to127Octets

M805C9


M805C10


DN09203161Issue:02

M e asu r eme n t

BCN Ethernet Statistics

©2016Nokia

175


Table 77


C o u n t eIrD

M805C11


C o u n t en r a me

M e asu r eme n t


M805C12


M805C13

iflnDiscards

M805C14

iflnErrors

M805C15

iflnUnknownProtos

M805C16

ifOutDiscards

M805C17

ifOutErrors

M805C18

ifHClnOctets

M805C19

ifHClnUcastPkts

M805C20

ifHClnMulticastPkts

M805C21

ifHClnBroadcastPkts

M805C22

ifHCOutOctets

M805C23

ifHCOutUcastPkts

M805C24

ifHCOutMulticastPkts

M805C25

ifHCOutBroadcastPkts

M805C26

ifHighSpeed

Key performance indicators There are no KPIs related to this feature. Parameters There are no parameters related to this feature. Sales information Table 78


BSW


RAN


-

5.2 RAN3193: OSPF Authentication for Controller Introduction to the feature This feature allows the operator to secure the routing messages that are exchanged between the controller and the site router(s). This increases the robustness of the site's routing configuration by preventing accidental open shortest path first (OSPF) misconfiguration. By using cryptographic keys, the chances for attackers to modify the routing configuration using OSPFv2 are even further limited.

176

©2016Nokia

DN09203161Issue:02


5.2.1


RAN3193 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows the operator to secure the OSPF routing messages to prevent accidental OSPFv2 misconfigurations.

5.2.2

RAN3193 Functional description OSPFv2 authentication is supported in RNC2600, mcRNC, and mcBSC according to RFC2328 appendix D.3. The authentication prevents malicious or accidental changes of the controller site routing configuration by discarding received OSPFv2 packets that do not carry a configured key. When using the cryptographic message digest algorithm version 5 (MD5) option, the security is improved as keys will not be transmitted in clear text and thus cannot be gathered by simple packet sniffing. The OSPF site setup is represented in Figure 10: OSPF site solution. The following authentication options are supported in mcRNC: • • •

null key (clear text) MD5 (cryptographic key)

Figure 10

OSPF site solution

The RAN3193: OSPF Authentication for Controllerfeature requires OSPFv2 authentication support in the site routers. The listed authentication methods are supported through all controller products except the MD5 option that is not supported for RNC2600. The RNC2600 supports only the clear text simple password.

DN09203161Issue:02

©2016Nokia

177



Several MD5 authentication keys are supported simultaneously within the configuration and the authentication key update procedure is supported by the mcRNC. The preferred way for the update procedure is to modify the router side authentication keys first and then update the network element accordingly. The mcRNC, for example, always applies the key with the highest index for the outgoing messages. The OSPF site solution setup with authentication is recovered automatically after any unit/network element/router restarts, reset cases, or link failures. The configuration and the applied key values remain at the same level as configured before the restart.

5.2.3

RAN3193 System impact Interdependencies between features The OSPF authentication belongs to the OSPF feature content. The RAN1510: OSPF for redundancy feature license is required for the OSPF functions. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network and network element management tools. Impact on system performance and capacity This feature has no impact on system performance and capacity.

5.2.4


WCDMA 16


mc R N C

RNC16

mcRNC16

OMS

NetAct





MS C


S GSN







This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults and reported alarms related to this feature. Commands The OSPF configuration, including the optional authentication, is configurable locally via the SCLI and via the IP plan interface from NetAct.

178

©2016Nokia

DN09203161Issue:02



The related SCLI command for this feature isset routing ospf interface authtype. This is to set the OSFP routing interfaceauthentication type. Measurements and counters There are no new measurements or counters related to this feature. Key performance indicators There are no KPIs related to this feature. Parameters Table 80

Existing parameters related to RAN3193 F u l l n am e

A b b re v i ate dn ame

Key ID

M an age dob j e ct

keyId

MD5 Secret

secret

Authtype

authType

BFD detect multiplier

bfdDetectMult

BFD monitoring

bfdMonitoring

BFD RX interval

bfdRxInterval

BFD TX interval

bfdTxInterval

Dead interval

deadInterval

Election priority

electionPriority

O2IFC Fast hello interval for interface Hello interval

fastHelloInterval helloInterval

Interface

interface

OSPFcost

ospfCost

Passive

passive

Password

password

Retransmit interval

retransmitInterval

Sales information Table 81

RAN3193 Sales information BS W/ASW

ASW

DN09203161Issue:02


RAN

©2016Nokia

L i c e n s e c on t ro l i n n et w o rk element

RNC license key

179

Operability features


6 Operability features 6.1 RAN3242: Category for Obsolete Parameters Introduction to the feature The RAN3242: Category for Obsolete Parametersfeature enhances the current parameter categorization in the NetAct application. The feature introduces a new parameter categoryObsolete, and improves theAdvanced category by displaying both the basic and advanced parameters.

6.1.1

RAN3242 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature benefits the operator as follows: •

•

•

Operating expenses (OPEX)is reduced because of the simplified plan file, and limitation of the number of parameters to be displayed in NetAct configuration management (CM) tools. The categorization of the parameters prevents the occurrence of mistake, which leads to a faster search of the needed parameter. The operators are allowed to modify the categorized obsoleteparameters if the parameters are still in use and to give feedback before the parameters are completely removed.

6.1.2

RAN3242 Functional description The RAN3242: Category for Obsolete Parametersfeature improves the parameter categorization in NetAct CM Editor and NetAct CM Plan Editor. The feature introduces a new parameter categoryObsolete. This feature makes the NetAct parameter categorization to have four category views: •

All

•

Basic Advanced Obsolete

• •

The child parameters are also supported to be categorized as Basic, Advanced, or Obsolete. The child parameters can be categorized differently from the parent parameter. And if the child parameter is uncategorized, it is displayed in the view corresponding to the category of the parent parameter. Parameter category views The following are the definition of each category view: •

180

The All view displays all the parameters.This view displays the Basic, Advanced, Obsolete, and the uncategorized parameters.

©2016Nokia

DN09203161Issue:02


g


Note: Uncategorized parameters may be found in network elements that can no longer be modified. This feature targets only the operator configurable RNW and IP parameters. The RNC ATM configuration parameters are not categorized. There might be some cases where a parameter has been categorized differently than the category expected by the operator. In such cases,All view provides an efficient way for the operator to find such parameters. •

•

•

The Basic view displays the parameters that are essential for RNC or BTS integration and deployment and parameters that are used regularly to manage the network. As a default view, the NetAct Configurator displays the parameters under Basic view. The Advanced view displays both the basic and advanced parameters. Advanced parameters are used in network optimization or for fine-tuning functionalities that are related to complex features. Operators often depend on basic parameters, the reason why basic and advanced parameters are combined. The Obsolete view displays only the obsolete parameters that are intended to be removed in the future release.

Nokia Networks' engineering team derives obsolete parameters by gathering the usage of each configuration management parameters at operators' live networks. When the parameter utilization factor is below or equal to the defined target value of 90%-100%, the parameters are categorized as obsolete. These obsolete parameters are the: • •

parameters that are always used as default parameters that are not used by operators

These obsolete parameters are still modifiable and visible in the NetAct Configurator display but will soon be removed. The operators can modify the parameters categorized asObsolete. If they assessed that a certain parameter in theObsolete category is still used in their networks, then they can modify the category and justify the reason why they need to keep the parameter to Nokia Networks customer support. Operators can also create their own user-defined view if they are not satisfied with the pre-defined categorization. This leads to an efficient means for parameter configuration administration and ease the possibility of error or mistake by removing parameters that are not frequently used in the NetAct Configurator display. When the obsolete parameter is in the user-defined view, then it is displayed differently than other parameters to alert the operator that the parameter is a candidate for removal.

6.1.3

RAN3242 System impact Interdependencies between features There are no features interdependent with this feature. This feature is related to LTE2506: Category for Obsolete Parametersfeature. Impact on interfaces There are no impacts on interfaces for this feature.

DN09203161Issue:02

©2016Nokia

181



Impact on network and network element management tools The impact for NetAct are as follows: • • •

•

A new parameter category view Obsolete is introduced. The default view is changed from All to Basic. NetAct displays differentparameter category values for different parameters in the same structure. NetAct displays the obsoleteparameters that arein the user-defined view ina visually different way that alerts the operator that the parameter is intended to be removed.

Impact on system performance and capacity There are no impacts on system performance or system capacity for this feature.

6.1.4



RAS

I PA - R N C

mc R N C

WCDMA 16



OMS

NetAct


NetAct 16.2



MS C


S GSN





MGW


UE


This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters For the complete list of parameters that are categorized asObsolete, see: •

RNC –

Multicontroller RNC IP Parameters

–

Multicontroller RNC RNW Parameters IPA-RNC IP Parameters IPA-RNC RNW Parameters

– – •

182

BTS

©2016Nokia

DN09203161Issue:02


– –


Flexi Multiradio BTS WCDMA Parameters Flexi Transport Module Parameters


RAN3242 Sales information BS W/ASW


BSWNetAct

RAN


NetActRadioWCDMA Standard SW

6.2 RAN2706: Delta Configuration and Change Notification for BTS Transport Introduction to the feature The RAN2706: Delta Configuration and Change Notification for BTS Transport feature supports the creation, pre-validation, download, and activation of a delta configuration plan for the base transceiver station's (BTS) transport subsystem (TRS) parameters. A delta configuration plan may consist of updates for both BTS and TRS parameters that are sent to a target set of BTSs. NetAct is able to send a single delta configuration plan to each target BTS. The feature also supports the sending of a configuration change notification (CCN) that is used to synchronize the current configuration of the BTS maintained in NetAct. The BTS sends a CCN to NetAct for every transport configuration managed object (MO) that is modified.

6.2.1

RAN2706 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature benefits the operator as follows: • • •

DN09203161Issue:02

The unnecessary restartof the BTS (and co-located BTS transport)initiated during the complete transport configuration plan activation is prevented. Less service interruptions because theunnecessary BTS transport module reset is avoided. The unnecessary upload of BTS transport configuration isprevented.

©2016Nokia

183


6.2.2


RAN2706 Functional description The RAN2706: Delta Configuration and Change Notification for BTS Transport feature supports the on-line configuration plan activation of transport configuration modifications. The following transport provisioning operations are also used in any planned configuration change: • • • • •

creation of a delta configuration planof on-line modifications pre-validation of the delta configuration plan download of the delta configuration plan activation of the configuration plan viewing of the updated transport configuration inNetAct

Creation of a delta configuration plan of on-line modifications The creation of a delta configuration plan containing transport configuration modifications is initiated at NetAct. In using the NetAct Configuration Management (CM) applications, the operator specifies the needed modifications for MOs to:

•

add delete

•

update

•

NetAct provides notification if the specified modification requests are possible and whether the changes to all transport managed objects (MO) may be updated on line.

g

Note: Only the managed objects and parameters that are specified as on-line modifiable do not require a BTS restart. Otherwise, NetAct provides notification that the specified modifications include a change that require a BTS restart. Pre-validation of a delta configuration plan containing transport configuration The delta configuration plan containing transport configuration needs to be pre-validated prior to download. NetAct creates a partial site configuration file (SCF) containing each modification specified in the delta configuration plan for each target BTS. This results in a decrease in download time compared to a complete configuration plan. The Validation operation in NetAct invokes the pre-validation of the delta configuration plan. For more information, seeNetAct documentation CM Operations Manager Help► Provisioning plans. NetAct pre-validates the delta configuration plan for each target BTS, and reports any validation errors.

g

Note: NetAct invokes a BTS site manager (BTSSM) provided plug-in for pre-validation. Download of the delta configuration plan containing transport configuration In this phase, the operator selects a configuration plan containing transport configuration modifications to download to a set of target BTSs. NetAct requests the download of the partial SCF to the set of target BTSs, and tracks the progress of the configuration plan download. During the download operation, the configuration plan is also validated by thePre-activate operation in NetAct.

184

©2016Nokia

DN09203161Issue:02



For more information, seeNetAct documentation CM Operations Manager Help► Provisioning plans.

g

Note: NetAct invokes a BTSSM provided plug-in for pre-validation. Activation of configuration plan containing transport configuration The operator now selects a configuration plan, which has been downloaded to the target set of BTSs, and requests the activation of the parameter modifications by invoking the Activate pre-activated operation addition/deletion/update of the transport parameters values do not require in theNetAct. BTS toThe restart if all the transport managed objects are marked as on-line.

g

Note: NetAct provides a notification if the specified modifications include a change that requires a BTS restart. Activate is another provisioning operation in NetAct, which includes download, validation, and activation in a single operation. For more information, seeNetAct documentation CM Operations Manager Help► Provisioning plans. NetAct tracks the progress of the configuration plan activation of each target BTS and reports the success or failure of the operation. Viewing of the updated transport configuration in NetAct The BTS activates the downloaded configuration plan and includes each MO that is modified during the activation in a configuration change notification (CCN) that is sent to NetAct. CCNs are also sent to NetAct by the BTS in case transport configuration is modified using BTSSM. NetAct updates the data of the BTS configuration to match the changed data indicated in the CCN. Thus, this prevents the need to upload the full transport configuration file from the BTS. NetAct can then display the current data of the BTS configuration. Exceptions in using the delta configuration plan There are exceptions in using the delta configuration plan with regards to MOs that are asynchronous transfer mode (ATM) and non-ATM. Different configuration scenarios and special handling are needed for the ATM and non-ATM MOs that involve the delta configuration plan. Configuration scenarios for ATM MOs The configuration of ATM MOs with the delta configuration plan must be done in a certain order because of the parent-child relationship and interconnection of the MOs. Thus, the use of multiple delta on-line configuration updates in NetAct is needed. If the parameter of any, MO notCreate on-linethe modifiable, only way tooperation modify the parameter is byDelete and is then MO. Thethe configuration order of the MOs in Add/Delete configurator model must be followed:

DN09203161Issue:02

©2016Nokia

185



Figure 11

Add/Delete configurator model

PPTT or SDHIF or IMAG

Physical layer interface

n io t a r u ig f n o c d d A

ACCP

TCCT

TRDE

TRDE

VPCT

VPTT

TRDE

VCCT

ATM adaptation layer (AAL) profile pointer

VCTT

A2ST

A2UT

IAIF

}

AAL2

}

AAL5- for IP over ATM (IPoA)

n io t a r u ig f n o c e t e l e D

ANBA }

AAL5

A special handling is needed for TRDE MO and M-plane connections. The TRDE MO is interrelated to both VPCT and VCCT MOs. Therefore, VPCT and VCCT MOs must be deleted or updated first prior to the delete operation of TRDE MO. All the parameters of the TRDE are on-line configurable if the TRDE is not used in any ATM connection yet. For VCCT that is used for M-plane, the delete operation of the VCCT and the reconfiguration of the new VCCT for M-plane must be done in a single delta configuration plan. Otherwise, the M-plane connection is lost, and site visit is needed if the BTS does not supportRAN2554: Transport configuration fallback for M-plane recovery feature. Configuration scenarios for Non-ATM MOs The online modification of the transport mode and BTS ID parameters are not allowed with the delta configuration plan. A full on-line configuration plan is forced by NetAct or BTSSM in re-commissioning the BTS to modify the parameters. The LinkOAM (LOAM) must be disabled E ( THLK.linkOAMEnabled) using BTSSM for an Ethernet link before LOAM profile can be edited. Otherwise, the modification of the Ethernet LOAM profile is rejected by the BTS. For more information, see BTSSM Online Help>TRS Hardware- Ethernet LinkOAM.

186

©2016Nokia

DN09203161Issue:02



The BTS rejects the swapping of VLAN IDs or IP addresses of two existing IP interfaces (VLAN or plain Ethernet) using a single delta configuration plan. When the BTS tries to apply the new ID on the 1st VLAN, the BTS finds that there is another VLAN already existing with the same ID. The same problem happens when the existing IP addresses are swapped between IP interfaces (VLAN or plain Ethernet). The operator needs multiple delta configuration plans to do VLAN IDs or IP addresses swapping. The following are examples of delta configuration plans on how to swap a VLAN ID of the IP interfaces: 1. Temporary assign an unused VLAN ID to one of the VLAN IP interfaces. 2. Modify the other VLAN IP interface to the previous VLAN ID. 3. Modify the second VLAN IP interface to the first VLAN ID.

g

Note: Same procedures are used to swap IP addresses. Plesiochronous digital hierarchy (PDH) interface type is not allowed to modify using delta configuration plan if there are inverse multiplexing for ATM (IMA) or any ATM configuration objects in the PDH interface. A full configuration plan is forced by NetAct to update the PDH parameter. Manual commissioning or re-commissioning During manual commissioning or re-commissioning using BTSSM, the operator can select, as shown in Figure 12: Send parameters options in BTSSM , either of the following options to send the parameters to the BTS: • •

Only changes- to send only the delta configuration All parameters- to send the full SCF

Figure 12

Send parameters options in BTSSM

Special handling is needed in terms of Bidirectional Forwarding Detection (BFD) in executing manual commissioning or re-commissioning of the BTS. To disable OSPF withdelta BFD configuration that is pre-configured as enabled and BFD option. MO exists, the operator can use the by selecting theOnly changes To enable OSPF with BFD that is pre-configured as disabled and BFD MO does not exist, the operator needs to split the operation using multiple delta configurations in the following order:

DN09203161Issue:02

•

Create BFD MO

•

Enable OSPF with BFD

©2016Nokia

187



The OSPF with BFD can be enabled and disabled in the IP view as shown in Figure 13: OSPF with BFD in BTSSM. Figure 13

OSPF with BFD in BTSSM

To modify Ethernet-based IP interface (IEIF) or VLAN interface (IVIF) local IP address (localIpAddr), and there is an existing BFD MO that is bounded to this address, the operator needs to send full SCF by selecting theAll parameters option. Figure 14

6.2.3

Local IP address

RAN2706 System impact Interdependencies between features This feature is related to the following:

188

©2016Nokia

DN09203161Issue:02


•

•


RAN885: Remote BTS SCF Management feature supports configuration updates using delta configuration files and synchronization between NetAct and BTS using configuration change notifications (CCN) for non-transport configuration in WCDMA networks. RAN2554: Transport Configuration Fallback feature supports the creation of a full transport configuration fallback file when activating a full transport subsystem (TRS) configuration file.

Other related features: •

LTE552: Delta Configuration for Transport

Impact on interfaces There are no impacts on interfaces for this feature. Impact on network and network element management tools There are no impacts on network and network element management tools for this feature. Impact on system performance and capacity This feature has an impact on O&M system performance. The time to download a configuration plan and the time to synchronize the configuration changes between the NetAct and target set of BTSs are reduced. There is no impact on system capacity for this fearure.

6.2.4



RAS

I PA - R N C

mc R N C

WCDMA 16



OMS

NetAct


NetAct 16.2

MS C



WBTS16

S GSN



WBTS16

MGW


Not planned

UE


This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no new measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters

DN09203161Issue:02

©2016Nokia

189



There are no parameters related to this feature. Commands There are no commands related to this feature. Sales information Table 85


BSW


RAN


-

6.3 RAN2367: DNS Support for Certificate Examination Introduction to the feature The RAN2367: DNS Support for Certificate Examinationfeature supports the replacement of the fixed IP address of a certificate revocation repository server with the fully qualified domain name (FQDN) indicated within the certificate or in manually configured certificate revocation list (CRL). The feature enables the BTS to query the domain name server (DNS) to acquire the IP address of the repository server by using the FQDN.

6.3.1

RAN2367 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature leads to OPEX savings by eliminating the need to renew all the certificates with fixed IP address that is used in revocation repository in the network. With the introduction of FQDN, only the DNS server needs to be updated when the revocation server is changed.

6.3.2

RAN2367 Functional description It is required to check if the certificates of the remote peers and configured trust anchors are valid and are not revoked. To make this checking possible, each certificate can contain the uniform resource locator (URL) of the corresponding revocation repository server or the URL can be preconfigured manually. It is a drawback for the operators when the address of the repository server is changed. All the certificates integrated to the link of the modified repository server address become invalid and the renewal of certificates is needed. RAN2367: DNS Support for Certificate Examinationfeature supports the DNS resolution in retrieving the addresses of the revocation distribution points. The fully qualified domain name (FQDN) is integrated within the certificates or to the manually configured CRL distribution points (CDP) that direct the certificate examination query to the DNS and retrieve the URL or the IP address of the revocation repository servers.

190

©2016Nokia

DN09203161Issue:02



The DNS client, which is the BTS, sends the FQDN to the DNS and in return, provides the corresponding IP address of the repository server. In this case, only the DNS server needs to be updated when the revocation server address is changed. Domain name server (DNS) DNS is a generic solution that is utilized by several applications and for this feature, it is the certificate examination of network elements (NEs). The DNS IP address must be configured in the NE. The configuration is available in the BTS configuration or in element (EM). A secondary DNS IP address can be configured plan as well, it the is used whenmanager the primary DNS is unreachable. If the DNS query has failed for both primary and secondary DNS, the DNS client indicates the failure and aborts the query. The BTS raises the 61074: CRL Update failurealarm if the CRL update fails. This alarm is raised for one of the following reasons: • • • •

LDAP binding failure LDAP search is empty (no CRL found) LDAP search containing multiple entry CRL signature validation failure

•

CRL file exceeding BTS storage limit BTS certificate being part of the CRL

•

DNS resolution failure

•

The feature supports the following functions: • •

g

6.3.3

DNS Protocol according to RFC1034 and RFC1035 Name lookup to resolve FQDN allocation of the IP address Note: The network elements support both User Datagram Protocol (UDP) and Transmission Control Protocol (TCP) for the DNS queries. If the DNS response is exceeded to 512 bytes, the server replaces it by an explicitly truncated packet and the client retries using TCP.

RAN2367 System impact Interdependencies between features The RAN2084: Support for certificate revocation (BTS)feature is needed to be activated and running. This feature introduces certificate revocation support in BTS. Other related feature isRAN2268: Multi-Layer Certificate Authorities . Impact on interfaces There are no impacts on interfaces for this feature. Impact on network and network element management tools There are no impacts on network and network element management tools for this feature. Impact on system performance and capacity There are no impacts on system capacity for this fearure.

DN09203161Issue:02

©2016Nokia

191


6.3.4




RAS

I PA - R N C

mc R N C

WCDMA 16

Support requirednot

Support required not

OMS

NetAct



MSC


WBTS16


WBTS16

S GSN


MGW


Not planned UE



This feature requires no new or additional hardware. Alarms Table 87

Alarms A l arm ID

A l ar m n ame

61074

CRLupdatefailure

Measurements and counters There are no new measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 88

Parameters F u l ln a me



Primary DNS Server IPv4 address

IDNS.serverIpAddress

WBTS

Secondary DNS Server IPv4 address

IDNS.serverIpAddress2

WBTS



BSW

192


NetActRadioWCDMA Standard SW

©2016Nokia


-

DN09203161Issue:02



6.4 RAN3247/LTE2507/RG602496: Energy Efficiency Shut Down Mode with RF Sharing Introduction to the feature The RAN3247: Energy Efficiency Shut Down Mode with RF Sharingfeature introduces a power saving mode for RF sharing configurations.

6.4.1

RAN3247/LTE2507/RG602496 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature helps to reduce OPEX due to energy savings provided by a power saving mode for RF sharing configurations.

6.4.2

RAN3247/LTE2507/RG602496 Functional description The RAN3247: Energy Efficiency Shut Down Mode with RF Sharingfeature releases RAT resources from the RF module during low traffic conditions or when required by the operator-defined profile. The Power Amplifier automatically goes into stand-by mode when both conditions are met: •

Depending on RF sharing configuration, at least twoRAT specific features are activated: – RG301936: Intelligent MCPA TRX Shutdown – RAN955: Power Saving Mode for BTS – LTE1103: Load based Power Saving for multi-layer networks

•

6.4.3

There are no radio resources reserved.

RAN3247/LTE2507/RG602496 System impact Interdependencies between features Depending on RF sharing configuration, at least two of the following features must be activated before starting up theRAN3247: Energy Efficiency Shut Down Mode with RF Sharing feature: • • •

g

RG301936: Intelligent MCPA TRX Shutdown RAN955: Power Saving Mode for BTS LTE1103: Load based Power Saving for multi-layer networks Note: NOTE: RAN3247 works under the terms of RG301936, RAN955, and LTE1103 licenses.

Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools

DN09203161Issue:02

©2016Nokia

193



This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

6.4.4

RAN3247/LTE2507/RG602496 Reference data Requirements Table 90


RAS

I PA - R N C

mc R N C

WCDMA 16



OMS

NetAct



MS C



WBTS16

S GSN



WBTS16

MGW


Not relevant

UE


This feature does not require any new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 91

6.4.5


BSW/ASW

SW component

License control in network element

ASW

RAN

RNC LK

Activating RAN3247: Energy Efficiency Shut Down Mode with RF Sharing Depending on RF sharing configuration, at least two of the following features must be activated before starting up theRAN3247: Energy Efficiency Shut Down Mode with RF Sharing feature: •

194

RG301936: Intelligent MCPA TRX Shutdown

©2016Nokia

DN09203161Issue:02


• •


RAN955: Power Saving Mode for BTS LTE1103: Load based Power Saving for multi-layer networks

Follow activation procedures in order to activate features in respective technologies.

6.4.5.1 6.4.5.1.1

Activating RG301936: Intelligent MCPA TRX shutdown in GSM Activating RG301936: Intelligent MCPA TRX shutdown Before you start • The license for the RG301936: Intelligent MCPA TRX shutdownfeature has to be installed. • The BSS20984: 2G TRX Automatic Power Downfeature has to be activated. • The Flexi Multiradio licencehas to be installed and enabled. • The BSC release S16.1 or greater. • The Flexi Multiradio 10with BTS GF1 1.0.0 release or greater. Procedure

1

Change value of the 2G TRX Automatic Power Down feature state to ON using the W7M command. ZW7M:FEA=1236:ON;

2

Change value of the Intelligent MCPA TRX shutdownfeature state to ON using the W7M command. ZW7M:FEA=4438:ON;

3

Ensure that the feature state was changed successfully using the W7I command. ZW7I:FEA,FULL:FEA=4438;

6.4.5.1.2

Verifying RG301936: Intelligent MCPA TRX shutdown Purpose Activation of the feature RG301936: Intelligent MCPA TRX shutdowncan be verified by checking the value of the2G TRX Power Down Threshold parameter. This feature is activated when both conditions are met: •

•

The value of the 2G TRX Power Down Threshold parameter is different from zero. Licenses of the RG301936: Intelligent MCPA TRX shutdownand BSS20984: 2G TRX Automatic Power Downfeatures are enabled.

Follow this procedure to verify that RG301936: Intelligent MCPA TRX shutdownfeature has been activated successfully.

DN09203161Issue:02

©2016Nokia

195



Before you start At least two MCPAs configured in a segment. Procedure

1

Ensure that the licence for the 2G TRX Automatic Power Downfeature has been installed (W7I). ZW7I:FEA,FULL:FEA=1236,;

2

Ensure that the licence for the Intelligent MCPA TRX shutdownfeature has been installed (W7I). ZW7I:FEA,FULL:FEA=4438;

3

Modify the Power Saving measurement (TPM). ZTPM:MEASUR,POWER_SAV:,,;

4

Start the measurement (TPS). ZTPS:MEASUR,POWER_SAV;

5

Wait until the measurement is enabled and interrogate it (TPI). ZTPI:MEASUR,POWER_SAV;

The operational state of the measurement changes toEnabled within 15 minutes.

6

Check the operational state of the TRX(s) (EEI). If the operational state of the TRX(s) is BLOCKED - AUTOMATIC POWER DOWN (BL-PWS), the TRX(s) has been powered down.

7

Check the measurement data. At the end of the measurement period, check the 113009 counter of the Power Saving Measurement in NetAct or in the BSC using the MEFICO tool. For more information, see: • •

Reporter and Performance ManagementPrinciples in NetAct Product Documentation Converting BSC Measurement and Observation Result Files with MEFICO

Step result 113009 MCPA POWER DOWNTIME DUE TRAFFICcounter of the Power Saving Measurement has been updated. The counter is updated when all TRX(s) in the MCPA have been shut down and their operational state isBL-PWS.

196

©2016Nokia

DN09203161Issue:02


8


Stop the Power Saving measurement (TPE). ZTPE:MEASUR,POWER_SAV;

6.4.5.1.3

Deactivating RG301936: Intelligent MCPA TRX shutdown Purpose Follow this procedure to deactivate theRAN955: Power Saving Mode for BTSfeature. Procedure

1

Change value of the Intelligent MCPA TRX shutdownfeature state to OFF/CONF using the W7M command. ZW7M:FEA=4438:OFF;

6.4.5.2 6.4.5.2.1

Activating RAN955: Power Saving Mode for BTS in WCDMA Activating RAN955: Power Saving Mode for BTS Purpose The following procedures activate theRAN955: Power Saving Mode for BTSfeature. For more information on the feature, see theRAN955: Power Saving ModeFeature Description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start This feature belongs to the application software and is under license key management. Ensure that you have a valid license. For information on managing licenses, see . The feature code for this feature is 1459. Before a license feature can be activated, the license has to be transferred to and installed in the RNC. The license can be installed by usingNetAct or a local MML interface. If the installation is done using NetAct, the feature covered by the license is automatically set to the ON state. If the installation is done using an MML interface, the feature state (ON/CONFIG/OFF) has to be set by the user. In new installations, the default state is set to OFF. The parameters for this feature can be configured with the RNC RNW Object Browser GUI. The Power Saving Mode feature can be activated only on the Flexi BTS with software release WBTS6.0 onwards. Ensure that theO&M DCN link status is set to Enabled. (Check it in the RNC RNW Object Browser in WCDMA BTS object.) Preconditions: The following criteria have to be fulfilled to activate HSPA05 reconfiguration : •

DN09203161Issue:02

The BTS has cells on two frequencies.

©2016Nokia

197



• • • •

•

•

•

• •

All cells in the BTS belong to the same Power Saving Mode cell group. The value of the PWSMCellGroup parameter is not zero. All cells of the BTS belong to the same Local Cell Group. Every non-remaining cell in a given frequency has PWSMShutdownOrder parameter value set to1 and the PowerSaveHSPAType parameter in all these cells is set to HSPA5. Every remaining cell in a given frequency has PWSMShutdownOrder parameter value set to 0 and the PowerSaveHSPAType parameter in all these cells is set to HSPA0. The HSDPA is enabled in all cells in the BTS. (HSDPAenabled parameter has value set to Enabled in all cells in the BTS.) The remaining cells are not allowed to be shut down. ( PWSMShutdownRemCell parameter value in all remaining cells is set toNo.) The DCN is working and WBTS is the FlexiBTS type. Licence is installed in the RNC.

If one or more criteria are not fulfilled, the HSPA05 reconfiguration is not required. The cell shutdown decision is based on the other cell shutdown criteria. If HSPA05 reconfiguration is required, HSPA0 cells are reconfigured to HSPA5 cells, and HSPA5 cells are reconfigured to HSPA0 cells before shutdown. Power Saving Mode instructions: •

The usage of gradual power ramp-down in the Cell Deletion procedureis recommended. During gradual common pilot channelCPICH ( ) power ramp-down, the UE initiates a soft handover branch removal. During or after gradual CPICH power the RNC a need for handover (inter-frequency or intersystemramp-down handover) and startsdetects the procedure.

•

•

After CPICH power decrease, the RNC performs a forced inter-frequency handover for the remaining UEs. When the gradual CPICH power ramp-down is used, the success rate of branch removals and inter-frequency/inter-system handovers is increased. (The number of lost calls during cell shutdown is smaller because of the RNC capability to handle simultaneous inter-frequency/inter-system handovers.) The number of remaining UEs in a cell is lower. The following features supporttraffic balancing betweencells after shutdown or activation, and are recommended for use in the RNC: – – –

•

•

198

Service and Load Based Handover Direct RRC Connection Setup HSPA Capability Based Handover.

The multi-operator RAN ( MORAN) has to be taken into consideration according to the definitions of the feature management parameters. The MORAN network operators have to define thePWSMCellGroup and PWSMShutdownOrder parameters correctly. The RNC does not verify the MORAN definitions in the Power Saving Mode. If the operator's actions leadto the situation when the Power Saving Mode environment is not consistent with the Power Saving Mode concept, the network can turn off the Power Saving Mode feature in the BTS by thePWSMInUse parameter. For example, if both a non-remaining cell and a remaining cell in the Power Saving Mode two-cell group are shut down and the operator deletes the remaining cell from the RNC, the non-remaining cell cannot be activated for traffic by means of the Power Saving Mode.

©2016Nokia

DN09203161Issue:02



HSPA05 reconfiguration instructions: •

•

•

•

•

•

•

•

The HSPA05 reconfiguration (resource swapping inthe BTS) can be made only between cells belonging to the same Local Cell Group (LCG). The network operator has to take the LCG cell mapping into consideration when setting the PWSMCellGroup and PowerSaveHSPAType parameters. The RNC Tcell parameter (Frame timing offset of a cell) selects cells controlled by the shared MAC high speed entity. The BTS maps cells from the one Tcell group to the same MAC high speed entity. This rule applies only for shared schedulers. The cell and Tcell mapping have to bedefined correctly by network operator, sothat the MAC high speed entity in HSPA0 - HSPA5 reconfiguration is made correctly (the HSPA5 and HSPA0 cells using same scheduler are defined to the same Tcell group). Some of HSPA functionalities might not be available, if theHSPA05 reconfiguration is made between different system module releases. In the Flexi BTS, the Rel2 system module supports HSPA+ functionalities, but the Rel1 system module does not. For working HSPA0 and HSPA5 configuration and reconfiguration, all cells have to be assigned to the same Power Saving Mode cell group. If the HSPA05 reconfiguration is used,the parameter HSDPAenabled has to be set to value Enabled in both HSPA5 and HSPA0 cells. In cell setup, the HSDPA is not configured to a cell with PowerSaveHSPAType parameter value set toHSPA0, even if the HSDPAenabled parameter is set to value Enabled. The activation status of the Power Saving Mode for the BTS feature is not relevant. When HSUPA services and HSPA05 reconfiguration are used,the HSUPAenabled parameter has to be set to valueEnabled in both HSPA5 and HSPA0 cells.

Procedure

1

Check the RNC time setting. For the RNC use the MML command:ZDCD. For the mcRNC/ADA use the sCLI command:show networking-service ntp.

2

Open the RNC RNW Object Browser GUI.

3

Configure the WBTS object. Set the non-remaining cell shutdown start time by configuring the PWSMShutdownBeginHour and the PWSMShutdownBeginMin parameters. Set the non-remaining cell shutdown end time by configuring the PWSMShutdownEndHour and the PWSMShutdownEndMin parameters and

ensure that the current RNC time is within this shutdown duration.

Set the remaining cell shutdown start time by configuring the PWSMRemCellSDBeginHour and the PWSMRemCellSDBeginMin parameters. Set the remaining cell shutdown end time by configuring the PWSMRemCellSDEndHour and the PWSMRemCellSDEndMin parameters. Set the remaining cell shutdown day by configuring thePWSMWeekday parameter.

DN09203161Issue:02

©2016Nokia

199



4

Configure the WCEL object.

g

Note: NOTE: The HSPA5 and shutdown criteria have to be fulfilled: • •

g

The BTS has cells on two frequencies. Two different cells with different frequencies arenot assigned to the same shutdown order.

Note: NOTE: Before configuring thePowerSaveHSPAType parameter, the related WCEL object has to be locked. Set two cells with the same frequency as remaining cells, by configuring the PWSMShutdownOrder parameter to value0, and set the PowerSaveHSPAType parameter to valueHSPA0. Set the third cell as a non-remaining cell, by configuring the PWSMShutdownOrder parameter to value1, and set the PowerSaveHSPAType parameter to value HSPA5. Configure the PWSMShutdownReCell parameter to valueNo to avoid shutdown of the remaining cell.

5

Configure the BTS object. Set the PWSMinUse parameter to valueON.

6

Cell s hutdown Cell 3 shuts down after five minutes when the following conditions are met: • • •

Cell does not have any emergency calls or Wireless Priority Service calls. Traffic in the cell is low. The shutdown criteria are met.

When HSPA05 reconfiguration is triggered, cell 3 reconfiguration to HSPA0 and cells 1 and 2 reconfiguration to HSPA5 is performed.

Expected outcome RAN955: Power Saving Mode for BTSfeature is activated in the RNC. Further information After activating the feature, the RNC or the BTS restart is not required.

6.4.5.2.2

Verifying RAN955: Power Saving Mode for BTS Purpose Follow this procedure to verify that the activation of the RAN955: Power Saving Mode for BTS feature has been successful.

200

©2016Nokia

DN09203161Issue:02



Procedure

1

In the RNC object, under the general tab, set timer to trigger PWSM faster.

2

In the WCEL-1 object, under the general tab, set the PWSM cell group of a cell as 1, the shutdown order of cells in one PWSM cell group as 0, and HSPA Type of Cell in Power Saving Mode as HSPA0.

3

In the WCEL-2 object, under the general tab, set the PWSM cell group of a cell as 1, the shutdown order of cells in one PWSM cell group as 1, and HSPA Type of Cell in Power Saving Mode as HSPA5.

4

In the WBTS object, enable PWSM by setting the PWSM usage in BTS as ON, and modify the shutdown time period.

Result If no call exists in WCEL-2, the cell state changes to BL(P) and shutdown is performed.

6.4.5.2.3

Deactivating RAN955: Power Saving Mode for BTS Purpose Follow this procedure to deactivate theRAN955: Power Saving Mode for BTSfeature. Procedure

1

Open the RNC RNW Object Browser GUI in the RNC Element Manager.

2

Configure the BTS object. Set the PWSMinUse parameter value toOFF.

g

Note: When deactivating Power Saving Mode,PowerSaveHSPAType parameter has to be changed toNo HSPA05_Reconfig value, otherwise HSPA operational state cannot be enabled. The cells that were shutdown, are to be activated.

Result The RAN955: Power Saving Mode for BTSfeature has been deactivated. Post requisites • •

DN09203161Issue:02

Set the feature license state to OFF. Restart of the RNC or the BTS is not required.

©2016Nokia

201


6.4.5.3 6.4.5.3.1


Activating LTE1103: Load Based Power Saving for Multi-layer Networks in LTE Activating LTE1103: Load Based Power Saving for Multi-layer Networks Before you start The Activate load-based power saving (actLBPowerSaving) parameter is used to activate the feature. Modification of this parameter does not require eNB restart or object locking. Table 92

Parameters used for activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networksfeature P a r am e t e r

202

Pu rp ose

R e q u i r e se N Br e s t a r to r object locking

Activate load-based power saving (actLBPowerSaving)

Mandatory

No

Power saving group identifier (psGrpId)

Mandatory

No

Load-based power saving last cell minimum load (lbpsLastCellMinLoad)

Mandatory

No

Load-based power saving last cell switch off enabled (lbpsLastCellSOEnabled)

Mandatory

No

Load-based power saving maximum load (lbpsMaxLoad)

Mandatory

No

Load-based power saving minimum load (lbpsMinLoad)

Mandatory

No

Load-based power saving PDCCH load offset (lbpsPdcchLoadOffset)

Mandatory

No

LTE cell configuration identifier (lnCelId)

Mandatory

No

Load-based power saving cell switch off order (lbpsCellSOOrder)

Mandatory

No

Load-based power saving day of week (lbpsDayOfWeek)

Mandatory

No

Load-based power saving duration (lbpsDuration)

Mandatory

No

Load-based power saving start time hour (lbpsStartTimeHour)

Mandatory

No

Load-based power saving start time minute (lbpsStartTimeMinute)

Mandatory

No

Load-Based Power Saving Suspended (lbpsSuspended)

Mandatory

No

©2016Nokia

DN09203161Issue:02



Procedure

1

Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings)of the general procedure, perform the steps described in this procedure.

2

Set the activation flag. a) b) c) d)

3

Go to the Radio Network Configurationpage. Expand the MRBTS object. Select the LNBTS object. Set the Activate load-based power saving (actLBPowerSaving) parameter value toTrue.

Create new PSGRP object. a) Right click the selected LNBTS object. b) Create new PSGRP object. c) Define the value for the following parameters: •

Power saving group identifier (psGrpId)

•

Load-based power saving last cell minimum

•

load (lbpsLastCellMinLoad) Load-based power saving last cell switch off enabled (lbpsLastCellSOEnabled) Load-based power saving maximum load (lbpsMaxLoad)

•

Load-based power saving minimum load (lbpsMinLoad)

•

Load-based power saving PDCCH load offset (lbpsPdcchLoadOffset)

•

4

Define the serving cells and switch-off order in the power saving group. a) Expand the selected PSGRP object. b) Select the Load-based power saving cell list (lbpsCellList) parameter. c) Perform the following configurations: •

Create an entry in the LTE cell configuration identifier (lnCelId) parameter for each cells in the power saving group.

g

DN09203161Issue:02

Note: A cell must have a unique value for lnCelId parameter and should be only in one power saving group.

©2016Nokia

203



•

Set the Load-based power saving cell switch off order (lbpsCellSOOrder) parameter with a unique value for each cells ranging from 1 to 100.

g

5

Note: The cell assigned with a value of100 will not be switched off if the lbpsLastCellSOEnable parameter is set to false. Multiple cells can also be assigned with a value of 100.

Define the time periods for energy saving. a) Select the Load-based power saving period list (lbpsPeriodList) parameter. b) Define the value for the following parameters: •

Load-based power saving day of week (lbpsDayOfWeek)

•

Load-based power saving duration (lbpsDuration)

•

Load-based power saving start time hour (lbpsStartTimeHour) Load-based power saving start time minute (lbpsStartTimeMinute) Load-Based Power Saving Suspended (lbpsSuspended)

• •

6

Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.

Expected outcome The LTE1103: Load Based Power Saving for Multi-layer Networks feature is activated in the eNB. The control parameters and power saving groups are downloaded and activated in the eNB.

6.4.5.3.2

Deactivating LTE1103: Load Based Power Saving for Multi-layer Networks Before you start The Activate load-based power saving (actLBPowerSaving) parameter deactivates the feature. Modification of this parameter does not require eNB restart or object locking. Procedure

1

Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings)of the general procedure, perform the steps described in this procedure.

204

©2016Nokia

DN09203161Issue:02


2


Configure the Activate load-based power saving (actLBPowerSaving) parameter a) b) c) d)

Go to the Radio Network Configurationpage. Expand the MRBTS object. Select the LNBTS object. Set the Activate load-based power saving (actLBPowerSaving) parameter value tofalse.

3

Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.

Expected outcome The LTE1103: Load Based Power Saving for Multi-layer Networks feature is deactivated in the eNB.

6.5 RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Introduction to the feature RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffingfeature supports the monitoring, detection, and evaluation of radio frequency interference (RFI) and passive intermodulation (PIM) remotely by means of the BTS site manager (BTSSM).

6.5.1

RAN3060 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature benefits the operator as follows: •

The feature introduces OPEX savingsby eliminating the need of expensive and labor extensive site portable PIM analyzer to detect degraded uplink performance caused by poor site infrastructure or cabling.

•

The feature provides the automatic detection andevaluation of RFI and PIM. The feature provides a faster and easier approach to monitor radio frequency performance that can be used to optimize and alleviate disturbances.

•

6.5.2

RAN3060 Functional description The RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffingfeature supports the monitoring, locating, and analyzing external disturbances such as RFI and PIM by means of the BTS site manager (BTSSM). The RF-sniffing device is a built-in spectrum analyzer inside the BTS, thus enables the capability to monitor the RF performance and to detect RFI and PIM in an automated and non-intrusive manner.

DN09203161Issue:02

©2016Nokia

205



Radio-frequency interference (RFI) RFIs are external disturbances caused by adjacent sites, illegal emitter, harmonics, and faulty equipment that are common problems for operators. These disturbances must be detected and resolved as early as possible during the BTS installation or commissioning phase. The continuous monitoring of RFI determines if the BTS is degraded or is degrading slowly over a period of time. Passive inter-modulation (PIM) PIM occurs when two or more signals are present in a passive element such as coaxial cable, connecting bolts, duplexer, and so on. PIM distortion indicates spurious signals commonly occurs in the BTSs with multi-carrier configuration. Multi-carrier configuration refers to BTSs with two or more signal carriers shared in a single antenna. These spurious signals are inevitable in multi-carrier BTS. However, they are only hazardous to the network when they appear in the receiver (Rx) frequency band that causes interference with the radio reception. The introduction of this feature provides an automated tool set for RF-sniffing or scanning and PIM test, which allow operators to retrieve RF performance data that can identify the occurrence of RFI and PIM. The retrieved RF data can be visualized and analyzed remotely by using BTSSM. BTS test mode •

On-line tests refer to the retrieval of RF measurements that are executed exclusively within the BTSSM.

•

Off-line test refers to the retrieval of RF measurement that sets the BTS to test dedicated mode.

On-line tests: RF-sniffing/scanning and PIM simulation mode •

RF-sniffing/scanning RF-sniffing or scanning supports the measurements of RFI sources in the uplink (UL) channel after the installation or commissioning of a new site to ensure that there is no internal and external interference or to investigate if the UL performance is degraded or degrading slowly over time. RF-sniffing/scanning has the following options: – – –

g

Raw composite Rx Composite Rx Carrier Rx

Note: Not all radio modules supportComposite Rx and Carrier Rx. •

PIM simulation mode The test involves the capturing of potential interference based on the BTS actual configuration.

Off-line test: PIM channel desensitization PIM channel desensitization This test verifies if the cell configuration is causing uplink channel desensitization. Desensitization happens when the receiver is unable to receive the desired signal because the radio signal is too weak and is interrupted by the nearby interference.

206

©2016Nokia

DN09203161Issue:02



The actRfiTesting and actPimTesting parameters must be set totrue to enable RF-sniffing/scanning and PIM channel desensitization test respectively. For more information on activating the parameters, seeActivation of RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing. PIM and RF-sniffing/scanning visualization The RF-sniffing/scanning and PIM data that are generated in the base transceiver station (BTS) are automatically uploaded in the BTS Site Manager (BTSSM). In the BTSSM, operators are allowed to view and monitor the RF performance and PIM simulation test. The data can be exported in an external destination within the operator's network or it can be stored locally on a removable storage unit, which is essential in RF performance management.

g

Note: The real-time visualization of the streaming data is not supported. Only the visualization of the post-processed or captured data is provided. BTSSM supports the following reports: •

mean square spectrum This is a two-dimensional plot that shows power density versus frequency. It describes the power distribution of the intermediate frequency (IF) signal with respect to the frequency

•

spectrogram This is a three-dimensional plot, which shows the distribution of the received power over frequency, that is changing over time. max, min, average-power This is a two-dimensional plot that is based on the spectrogram with the frequency

•

and power as the x and y axes, respectively. It shows the maximum, minimum, and average power depending on the frequency. RF-sniffing/scanning and PIM data file in HDF5 format Filename for RF-sniffing/scanning and PIM tests follow this naming convention: [bts_site_name]_[test_name]_[mmddyyhhmmss]_[file#].smdf

where: test_name=scan_test for RF-sniffing/scanning orpim_desen for PIM channel desensitization test bts_site_name= wbtsName mmddyyhhmmss= date and start time of the test file#= uniquely identifies the file created within the same test .smdf= special extension dedicated to the suite of tests

g 6.5.3

Note: PIM simulation test does not require a file transfer and therefore, not defined in the naming convention.

RAN3060 System impact Interdependencies between features This feature is related to LTE1434: Flexi Multiradio BTS antenna Rx RF-sniffing

DN09203161Issue:02

©2016Nokia

207



Impact on interfaces BTSSM - BTS The BTSSM sends a new request message to the BTS for the on-line, off-line, and new types of test report to be retrieved. The message contains the following information: • • • • • •

cellIDList– list of cells associated with the antenna where the test is executed antennaNumber – antenna number within the cell txPwrList- desired Tx power per cell/carrier test model – method for downlink signal generation commissioned Rx frequencies commissioned Tx frequencies

Impact on network and network element management tools BTS site manager (BTSSM) BTSSM introduces the following functions with this feature: • • • • •

RF snapshot fetching PIM desensitization test results fetching RF snapshot visualization PIM simulation calculation and visualization license checking

Impact on system performance and capacity There are no impacts on system performance or capacity for this feature.

6.5.4



RAS

I PA - R N C

mc R N C

WCDMA 16



OMS

NetAct



MS C



WBTS16

S GSN



WBTS16

MGW


Not planned

UE


This feature supports the following hardware: •

RF module for RFI – – – – –

208

FXEB FXCB FXDB FHDB FHFB*

©2016Nokia

DN09203161Issue:02


FRCG* FRGS FRGT

– – –

FRGU* FRGY* FXFC FRGP-B FXFA

– – – – –

FXFB FXEA FXCA FXDA FXDJ FHDA

– – – – – –

g

Note: The RFI support for FHFB, FRCG, FRGU, and FRGY RF modules will be available in future maintenance releases. •

RF module for PIM: FXEB FXCB

– –

FXDB FHDB

– –

FHFB* FRCG* FRGS FRGT FXFC

– – – – –

g


Note: The PIM support for FHFB, and FRCG will be available in future maintenance releases. Alarms There are no new alarms related to this feature. Measurements and counters There are no new measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 94


DN09203161Issue:02

A b b r e v i a t e dn am e


Activate RFI testing

actRfiTesting

BTS

Activate PIM testing

actPimTesting

BTS

©2016Nokia

209





ASW

6.5.5


RAN


BTS licence key (LK)

Activating RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Purpose Follow the procedure to activate the feature. For more information on the feature, seeRAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature description. Before you start BTS restart is not required after the activation of this feature. The procedure is a non-service-affecting activity and does not cause downtime. BTS is up and running. Make sure you have access to BTS site manager (BTSSM). The RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffingfeature is an optional application with two licenses control: • •

RF Scanning: 5445 PIM channel desensitization: 5446

The licenses must be transferred and installed in the BTS for the feature to be activated. For more information on licensing, seeLicensing. Procedure

1

Open the License Management dialog box in the BTS site manager. Go to Configuration ► License Management

Step result Listed are the BTS features and licenses.

210

©2016Nokia

DN09203161Issue:02


2


Select the required license file. Sub-steps

a) Select the RF scanning/PIM channel desensitization license file.

b) Go to Download License to Site ► Browse c) Select RF scanning/PIM channel desensitization license file.

3

Download the licenses to the BTS. Select Download to BTS button.

g

g

Note: The feature has two separate license codes, therefore perform step 2 and 3 for each license.

4

Select Close to close the dialog box.

5

Set actPimTesting and actRfiTesting parameters to TRUE. Note: NetAct application can alternatively be used. Sub-steps

a) Select Commissioning ► BTS Settings.

b) Select Activate RFI testing and Activate PIM testing. Figure 15

DN09203161Issue:02

RFI and PIM testing in commissioning BTS settings

©2016Nokia

211



6

Finish the BTS commissioning.

Result Expected outcome: The RAN3060: Flexi are Multiradio BTS Antenna RF-sniffingfeature has been activated. RFI and PIM testing now supported in the Rx BTS.

6.5.6

Verifying RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Before you start The BTS is commissioned. The BTS is configured with RF HW 2.2 onwards. The BTS is configured with multiple carriers. MATLAB Compiler Runtime (MCR) is installed. The installation package can be downloaded in http://www.mathworks.se/products/compiler/mcr. Make sure you have access to BTS site manager (BTSSM). Procedure

1

Open BTS s ite manager.

2

Select RF Monitoring Figure 16

212

RF Monitoring

©2016Nokia

DN09203161Issue:02


3


Verify th e RF -scanning test. Sub-steps

a) Select RF scan in the Test tab.

b) Choose a folder where RF scan result will be saved. c) Select an antenna to be scanned.

d) Select Capture type.

e) Click S tart. A message box will appear notifying that download is completed.

f)

Click Visualize. You will be transferred toFile tab where the measurement is visible.

4

Verify the PIM desensitization test.

g

Note: In PIM channel desensitization test, the BTS is required to set in Test dedicated state and needed BTS restart.

g

Note: PIM desensitization works with RF HW 2.3 onwards. Sub-steps

a) Select PIM desensitization in the Test tab.

b) Choose a folder where RF scan result will be saved.

c) Select an antenna to be scanned.

d) Select power (in dBm) of the cells to be tested. Start with the lowest possible TX power.

DN09203161Issue:02

©2016Nokia

213



e) Click S tart. A message box will appear notifying that download is completed.

f)


Result Expected outcome: RF scan data is retrieved and visualized in BTSSM. PIM desensitization is retrieved and visualized in BTSSM.

g

Note: If the result does not show too high desensitization value, then increase the TX power value gradually inStep 4. Figure 17

214

RF-scan visualization

©2016Nokia

DN09203161Issue:02


Figure 18

6.5.7


PIM desensitization visualization

Deactivating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing Purpose Follow this procedure to deactivate the feature. Before you start Make sure you have access to BTS site manager (BTSSM). Procedure

1

Open the License Management dialog box in the BTS site manager. Go to Configuration ► License Management Step result Listed are the BTS features and licenses.

DN09203161Issue:02

©2016Nokia

215



2

Select the required license file. Sub-steps

a) Select the RF scanning/PIM channel desensitization license file.

b) Select Delete button.

g

Note: The feature has two separate license codes, therefore perform step 2 for each license.

3

Select Close to close the dialog box.

4

Set actPimTesting and actRfiTesting parameters to FALSE.

g

Note: NetAct application can alternatively be used. Sub-steps

a) Select Commissioning ► BTS Settings.

b) Deselect Activate RFI testing and Activate PIM testing.

5

Finish the BTS commissioning.

Result Expected outcome: RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffingfeature has been deactivated. RFI scanning and PIM desensitization testing are now disabled in the BTSSM.

6.5.8

Testing RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Purpose This is an example of the verification; do not use it for the feature as such in live network. The configuration and parameter settings described are only examples and they can vary in different networks.

6.5.8.1

Test case 1: RF-scanning Purpose

216

©2016Nokia

DN09203161Issue:02



This test verifies RF-scanning function introduced in RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature. Before you start The license for RF-scannning (license key: 5445) is installed in BTS. For license activation, see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing. The ‘Activate RFI testing’ checkbox is enabled in Commissioning BTS settings. For enabling ‘Activate RFI testing’, see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing. Required test environment: • • • • • •

One computer is connected to BTS via LMP port or remotely. The BTS site manager (BTSSM) is compatible with the BTS SW version. The MATLAB Compiler Runtime (MCR) is installed. Operational radio access network (RAN)and core network (CN). FSMr2 or FSMr3 System Module (SM) The BTS is configured with RF HW 2.2 or beyond.

Procedure

1

Select RF Monitoring in BTSSM sidebar. Figure 19

2

DN09203161Issue:02

RF monitoring in BTSSM

Select RF scan in the Test tab.

©2016Nokia

217



3

Choose a folder where RF scan results will be saved.

4

Select an antenna to be scanned.

5

Select Capture type ► Raw Composite Rx (RxADC) or Composite Rx (HBF0).

6

Click Start. A message box will appear notifying that download is completed.

7

Click Visualize. You will be transferred toFile tab where the measurement is visible. Figure 20

218

RF-scanning measurementresult for Raw Composite Rx or Composite Rx

©2016Nokia

DN09203161Issue:02


8


Repeat Step 4 to Step 8 using different antenna. Sub-steps

a) Repeat Step 4 to choose another antenna.

b) Select Carrier Rx (FIR9). c) Select the cell on which this antenna type is available.

9

Click Start. You will be transferred toFile tab where the measurement is visible. Figure 21

RF-scanning measurement result for Carrier Rx

Result Expected outcome: The operator is notified that the test results file has been retrieved. The operator is presented a view of the test files specifying:

DN09203161Issue:02

•

Filename– name of the test file

•

testType– type of test data that the file contains

©2016Nokia

219



•

dateExecuted – date and time the file was created (representing the time of test

execution) The BTSSM does the following: • •

displays RF-scanning results as plot makes the RF-scanning test results fileavailable to the operator in hdf5 format

Test results are possible to save in the OS managed file system and as well as to save as picture to the desired folder.

6.5.8.2

Test case 2: PIM simulation Purpose This test case is used to validate the BTS configuration by using PIM simulation mode. Before you start Required test environment: • • • • • •

One computer is connected to BTS via LMP port or remotely. The BTS site manager (BTSSM) is compatible with the BTS SW version. The MATLAB Compiler Runtime (MCR) is installed. Operational radio access network (RAN) and core network (CN). FSMr2 or FSMr3 System Module (SM) The BTS is configured with RF HW 2.2 or beyond.

Procedure

1

Select RF Monitoring in BTSSM sidebar.

2

Select Simulation tab.

3

Choose Simulated antenna ► Ne w antenna.

4

Specify the needed parameters. Specify the following parameters for the cell ID Sim 1, Sim 2, Sim 3, and frequency band: • • • • • • •

220

Center frequency 1 Bandwidth for Center frequency 1 Center frequency 2 Bandwidth for Center frequency 2 Center frequency 3 Bandwidth for Center frequency 3 Intermodulation value(IM3, IM5, IM7, IM9)

©2016Nokia

DN09203161Issue:02


5

Click S imulate. Figure 22

6


PIM simulation test result

Repeat Step 3 to Step 5 for a different WCDMA bands. From the options antenna ► Existing antenna , and3perform simulation. If thereinSimulated is only one cell on antenna, add Sim 2 & Sim Cell IDs as in previous steps.

7

Check result plots.

Result Expected outcome: PIM simulation test is executed in BTSSM. BTSSM displays PIM Simulation results as plot. Unexpected outcome: If not all of the required parameters are specified or values are out of range, then the operator is notified of the error via an error message. All the required parameters must meet the criteria.

6.5.8.3

Test case 3: PIM desensitization Purpose This test case verifies the cell configuration is causing UL Channel interference using the PIM desensitization function.

DN09203161Issue:02

©2016Nokia

221



Before you start The license for PIM channel desensitization (license key: 5446) is installed in BTS. For license activation, see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing. The ‘Activate PIM testing’ checkbox is enabled in Commissioning BTS settings. For enabling ‘Activate PIM testing’, see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing. The BTS is in Test Dedicated state. Required test environment: • • • • • • •

One computer is connected to BTS via LMP port or remotely. The BTS site manager (BTSSM) is compatible with the BTS SW version. The MATLAB Compiler Runtime (MCR) is installed. Operational radio access network (RAN) and core network (CN). FSMr2 or FSMr3 System Module (SM) The BTS is configured with RF HW 2.2 or beyond. 2 or 3 carriers per antenna are configured.

Procedure

1

Select RF Monitoring in BTSSM sidebar.

2

Select PIM d esensitization in th e Test tab.

3

Choose a folder where PIM desensitization results will be saved.

4

Select an antenna to b e tested.

5

Click Start. A message box will appear notifying that download is completed.

6


222

©2016Nokia

DN09203161Issue:02


Figure 23

7


PIM desensitization test result

Repeat Step 4 to Step 8 for the rest of the antenna and different cell powers.

Result Expected outcome: The PIM Desensitization test is executed in BTSSM. If all the required parameters meet the criteria, then PIM Desensitization test is started. The BTSSM displays PIM Desensitization Test results as plot. Test results are possible to save in the OS managed file system and as well as to save as picture to the desired folder.

6.6 RAN2872: IPA-RNC Symptom Report Introduction to the feature RAN2872: IPA-RNC Symptom Reportfeature provides extended functionality and new data collection profiles for the operator to use when collecting IPA-RNC symptom data (troubleshooting logs). This feature improves and extends the RAN2446: Emergency Symptom Data Collection for IPA-RNCfeature. Symptom data can be collected with either Basic or Standard profiles. This influences the type of data collected, and the storage requirements and load placed on the RNC to collect the data. In certain troubleshooting cases the collection of traffic data is unnecessary in order to resolve the issue, and does not need to be performed. Data

DN09203161Issue:02

©2016Nokia

223



collection can be triggered either from an OMS or through new MMI commands on the RNC. The new profiles give the operator finer control over what data collection is performed on the RNC, without requiring them to log in remotely and use the CLI.

6.6.1

RAN2872 Benefits End-user benefits This feature has no direct impact on the end-user experience, but may reduce the length of network outages if they occur. Operator benefits This feature benefits the operator by providing a quicker and simpler means to collect relevant troubleshooting data required by Nokia Networks. This reduces the time taken to identify and resolve potential network problems.

6.6.2

RAN2872 Functional description The RAN2872: IPA-RNC Symptom Reportfeature enables the operator to collect symptom report data from the RNC using multiple profiles. It extends RAN2446: Emergency Symptom Data Collection for IPA-RNCby adding configurable Standard and Basic profiles for the symptom report. The symptom report is a collection of configuration data and logs that are essential for problem investigation, and is a mandatory part of every problem report submitted by the operator to Nokia Networks. The data collection for each profile can be initiated with a single command from RNC MML, or from OMS CLI. The profiles are based on the log collection options from Technical Note TS-RNC-SW-038 RNC PROBLEM REPORT INSTRUCTIONS(TN38). The Standard profile collects all the symptom reports that are collected by the Standard log collection option, whereas the Basic profile collects the same symptom reports but without message monitorings. The symptom report is compressed into a single archive file as soon as the data collection is completed. The symptom report archive file is stored on the RNC hard disk and is automatically uploaded to OMS once it is created. An RNC alarm notice is used to indicate to the operator the beginning and end of symptom data collection and the creation of the compressed symptom report. Triggering symptom report collection To start the report collection process, the user must be logged in to the IPA-RNC command shell or the OMS CLI. For more information, refer to Testing RAN2872: IPARNC Symptom Report

g

Note: When the RAN1805: RNC Event Triggered Symptom Data Collectionfeature is used, the symptom report collection process in the IPA-RNC can be triggered by certain pre-defined alarms. This event-triggered data collection procedure is aborted if a new user-triggered collection is requested. Editing the report profiles The symptom report profiles are stored as simple XML files which can be tailored to specific operator situations as required. For more information, refer to Configuring RAN2872: IPA-RNC Symptom Report

224

©2016Nokia

DN09203161Issue:02


6.6.3


RAN2872 System impact Interdependencies between features This feature is an extension of the troubleshooting data collection feature RAN2446: Emergency Symptom Data Collection for IPA-RNCand provides two new collection profiles. Other related features are: • •

•

RAN1805: Alarm triggered log collection for RNC - The centralized function to collect an RNC's self triggered troubleshooting data in OMS. RAN1873: OMS trouble shooting data collection - Troubleshooting data from OMS is collected to a single location on the OMS disk. RAN2229: Troubleshooting Data Management by NetAct - Troubleshooting data is automatically collected by NetAct.

Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity Symptom data collection consumes system processing resources. It is not recommended to collect data: • •

6.6.4

during system start-upand trial as it might increase the start-up time during SW fallback package creationbecause the limitation of the ZWQB MML command might lead to fallback operation failure.



RAS

I PA - R N C

WCDMA16

RNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2

mcRNC

Support not required MS C

Support requirednot

F l ex i Multiradio BTS



Flexi Lite BTS

Flexi Multiradio 10 BTS



MGW


UE


This feature requires no new or additional hardware. Alarms

DN09203161Issue:02

©2016Nokia

225



Table 97

Existing alarms related to RAN2872

A l arm ID

A l ar m n a me

0199

SYMPTOM DATA COLLECTION STATUS NOTIFICATION

71106

TROUBLESHOOTING DATA RECEIVED

71129

TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED

Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 98

Existing OMS LDAP parameters related to RAN2872 A tt r i bu te

M e an i n g

ClusterRoot/OMS/OMSPlatform/ SS_NELogManager/NELogManager/ dwAlarmForUploadCompleted

If set to 1, OMS triggers the alarm 71106 TROUBLESHOOTING DATA RECEIVED once the symptom report is uploaded to OMS. If set to 0, the alarm is not triggered.

ClusterRoot/OMS/OMSPlatform/ SS_NELogManager/NELogManager/ dwNetActNotifyEnabled

If set to 1, the symptom report is uploaded to NetAct and removed from OMS after collection. If set to 0, the symptom report remains on OMS after collection.

Sales information Table 99 B S W /A S W

BSW

6.6.5

RAN2872 Sales information S W c omp o n en t

RAN

Li cen se co n tr ol i n n etwor k el emen t

-

Configuring RAN2872: IPA-RNC Symptom Report Purpose The Standard and Basic profiles forRAN2872: IPA-RNC Symptom Reportcan be customized by the operator to add or remove certain types of data from the final report. The profiles are configured by means of an XML definition file on the RNC hard disk. This section defines the file format and describes the procedure to update the profiles. Procedure

1

Download the XML file for the required profile from the RNC. The XML must be downloaded, edited externally and uploaded again to the RNC. The profile XMLs are located under the path/RUNNING/LFILES/and are named RNCSTAND.XML and RNCBASIC.XML

226

©2016Nokia

DN09203161Issue:02


2


Edit the XML file in an XML editor For information on the XML structure and available options, please consult Symptom report profile XML structure. Ensure that the edited file is valid XML.

3

Upload the edited XML file to the srcinal location in the RNC. The new profile can be tested by following the procedures outlined in Testing RAN2872: IPA-RNC Symptom Report.

Result The symptom report profile is updated and collects the data that was configured by the operator. Symptom report profile XML structure The XML has a root element that depends on the profile type: •

•

Within the root element, there are three possible sub-elements: 1. The element can appear multiple times in the root. It defines one type or source of data to be collected. The element has exactly three attributes: •

log_type

This is a pre-defined name of a log type. If the name is not recognized by RAN2872, the entry is ignored. •

enabled

"T" means this symptom log will be collected, "F" disables collection. It can be used to toggle off certain types temporarilywithout deleting the whole element. •

priority

The logs with priority 1 are collected first, and then 2, 3, etc. The value range is from 1 to 255. Only integers are allowed. If none of the elements can be parsed succesfully,RAN2872 will use the default log type configuration to collect data for the symptom report. 2. The element can appear multiple times in the root. It defines parameters for collecting message monitoring data. The element has five attributes: •

unit_type

This is a mandatory attribute. The unit type should be valid for RNC, otherwise the corresponding element configuration is skipped. •

round

This determines in which round to start msgmon collections with configuration of this element, similar to the 'run' option in TN38 default_config.ini. round may have the value 1, 2, or 3. All monitoring elements with the same value of round are collected simultaneously.

DN09203161Issue:02

©2016Nokia

227



•

duration

This determines how long msgmon will collect messages for the specified unit type. The value is in seconds. It should be less than the value of col_timeout in the def_option element. •

bufsize

This determines how much buffer space is reserved for msgmon. The value is in bytes. It should be less than half of the unit's free memory size. •

conditions

This attribute specifies the messages that will be collected. It has the format :monitoring conditions. The meaning is the same as the instructions of the ZOEC command in RNC shell: EC(N):COMP*16/FUNIT::monitoring_conditions ! WORD ! Give functional unit name (max 6 characters) Monitoring points: S = Send, A = Arrive R = Receive Compare operators: <, <=, >, >=, =, <> Logical operations: AND, OR, NOT Data field access: ABS or DAT ABS from msg start, DAT from data start; : B / W / D : msg offset (hex, starting from 0) Byte Word Dword Message header fields: LEN = length COM = computer (in msg) CCOM = Co-computer FAM = family (in msg) CFAM = Co-family OFAM = Obj. family PRO = process_id (in msg) CPRO = Co-process OPRO = Obj. process FOC = focus (in msg) CFOC = Co-focus OFOC = Obj. focus ATT = attributes GRO = group NUM = number PHY = physical address Numeric values must start with a number (eg. 1, 1234, 0A, 0C000) Examples: ZOEC::SA:FAM=0CO,0C1,0BE,0BF; ZOEC:4:S:DATB4=2,4; ZOEC::SAR:(FAM=0A0)AND(NUM=1,2); ZOEC::SA:(FAM=0FC)AND(PRO=1,2,3,4); ZOEC:4,5,6:S:(OFAM=0D0)AND(NOT(ATT=1,2)); ZOECN:OMU:S:(OFAM=0D0)AND(NOT(ATT=1,2))AND(GRO>=1);

All monitoring elements that are configured with round="1" are started in the first round, and keep the collecting for a period which is specified by the attribute duration. When that timer expires, all monitoring is stopped, and the elements that are configured with round="2" will be started. After the second round is over, round="3" will be started. If all the conditions are invalid, the default configuration is used for msgmon collection. 3. The element appears once in the root. It defines default and generic collections options. The element can have up to eight attributes: •

col_timeout

This defines the collection timeout. This value is in minutes, and collecting is stopped if it has not finished when the time is up. •

228

olc_enabled

©2016Nokia

DN09203161Issue:02



This defines whether overload control is enabled or disabled. "T" means overload control is enabled during symptom report collecting, "F" means overload control is disabled. •

olc_timeout

This defines the overload control timeout. This value takes effect only if olc_enabled="T". It is specified in minutes and must be greater than the value of col_timeout. Because collection will take a longer time in an overloaded system, the value ofolc_timeout will be used for collecting timeout rather than col_timeout. •

olc_cmd_wait

This defines the overload control command waiting time. The value is given in seconds. If CPU overload occurs during symptom report collecting, a timer is started before MML/STE command execution, for the time specified for olc_cmd_wait. The MML/STE command will be executed if CPU load comes down to normal levels before the timer expires. Otherwise (if CPU overload continues) the MML/STE command will ABORT and the data will not be collected. •

disk_space_limit

This defines the minimum percentage of free space required to perform msgmon and HPL data collection. For example, ifdisk_space_limit="15" then msgmon and HPL data collection will only be allowed if the free disk space divided by the total disk space is >= 15%. •

turbo_mode

This enables or disables turbo mode, which removes some internal delays from the Chorus service terminal actor so that Chorus unit service terminal output becomes faster. This primarily affects long outputs from Chorus (bblog, rmd logs, perhaps some longer NIU counter outputs). "T" means enabled, "F" means disabled. •

health_check

This option is for performing a health check when collecting the RNW database. "T" means health check is enabled , "F" means disabled. •

zip_rnw

This option compresses the files when collecting the RNW database. "T" means compression is enabled, "F" means disabled. If any of the attributes are missing or invalid, RAN2872 will use the default values. Example Symptom report profile XML file: RNCSTAND.XML
DN09203161Issue:02

©2016Nokia

229



enabled="T" priority="7">
230

©2016Nokia

DN09203161Issue:02



enabled="T" priority="1">

DN09203161Issue:02

©2016Nokia

231



232

©2016Nokia

DN09203161Issue:02



6.6.6

Testing RAN2872: IPA-RNC Symptom Report Purpose The symptom report is a collection of configuration data and logs that are essential for problem investigation, and is a mandatory part of every problem report submitted by the operator to Nokia Networks. The symptom report can be triggered manually either through the IPA-RNC command shell or via OMS CLI.

DN09203161Issue:02

©2016Nokia

233


6.6.6.1


Symptom report collection using OMS CLI Before you start NetAct:

•

– –

the Alarm Monitor application is available No blocking or filtering of alarm 71106 TROUBLESHOOTING DATA RECEIVED and 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED

RNC: The SOKERI user account exists. To check the existence of the SOKERI account, use theZIAI:USERID=SOKERI; MML command. To create a SOKERI account, use theZIAH:SOKERI:PROFILE:; MML command. The password is arbitrary and does not need to be retained. The SOKERI account remains in the system through NE restarts, but may need to be recreated after software fallback or upgrades are applied. OMS: The logged-in user must belong to the_nokNELogManage user group. The user can be added to the_nokNELogManage group by an administrator with the command fsgpasswd -a _nokNELogmanage. To keep the logs stored on OMS and prevent them from being uploaded to NetAct, the OMS configuration parameter

•

•

ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dw NetActNotifyEnabled must be set to 0. The default value of 1 will cause the

collected logs to be uploaded to NetAct and removed from the OMS.

g

Note: The alarm 3319 NORMAL LOAD OF SECURITY EVENTS EXCEEDEDmay be raised during the collection of symptom report data. This is due to the number of concurrent login sessions made during collection exceeding the defined limit in the parameter (9, 137) SEC_EVENT_LOAD_LIMIT. Multiple concurrent logins are made for efficiency reasons.

g

Note: If the RAN2872 log collection is performed under high CPU load, both OMU login sessions can become occupied by running collection processes. These processes may take several minutes to finish due to the load, during which time it will not be possible for the user to log in to OMU. The typical error message will be that both sessions are already in use by the SOKERI account and the CBYPRB process. In this case, the user must wait until the RAN2872 process is completed before logging in.

Procedure

1

Log in to OMS CLI.

2

Trigger the data collection on the NE with the zcollectNElogs command: Select from available options

234

©2016Nokia

DN09203161Issue:02


•


zcollectNElogs -n -p RNCSTAND collects data according to

the standard profile. •

zcollectNElogs –n –p RNCBASIC collects data according to

the basic profile. 3

Wait for the alarm 71106 TROUBLESHOOTING DATA RECEIVEDto be raised. The alarm is raised when the collection process has finished and the symptom report is already uploaded to OMS.

Result The Symptom report is stored on the OMS disk in the location /var/opt/OMSftproot/NE/TroubleshootingData with a name in the format TSUPL__..zip. The date-time format is YYYYMMDDhhmmss. Error messages There are no error messages in OMS CLI during data collection, instead the network element will raise the alarm71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED if an error occurs during collection or upload of the symptom report.

6.6.6.2

Symptom report collection using RNC MML commands Before you start •

NetAct: – –

•

g

DN09203161Issue:02

the Alarm Monitor application is available No blocking or filtering of alarms 71106 TROUBLESHOOTING DATA RECEIVED and 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED

RNC: The SOKERI user account exists. To check the existence of the SOKERI account, use theZIAI:USERID=SOKERI; MML command. To create a SOKERI account, use theZIAH:SOKERI:PROFILE:; MML command. The password is arbitrary and does not need to be retained. The SOKERI account remains in the system through NE restarts, but may need to be recreated after software fallback or upgrades are applied. Note: The alarm 3319 NORMAL LOAD OF SECURITY EVENTS EXCEEDEDmay be raised during the collection of symptom report data. This is due to the number of concurrent login sessions made during collection exceeding the defined limit in the parameter (9, 137) SEC_EVENT_LOAD_LIMIT. Multiple concurrent logins are made for efficiency reasons.

©2016Nokia

235



g

Note: If the RAN2872 log collection is performed under high CPU load, both OMU login sessions can become occupied by running collection processes. These processes may take several minutes to finish due to the load, during which time it will not be possible for the user to log in to OMU. The typical error message will be that both sessions are already in use by the SOKERI account and the CBYPRB process. In this case, the user must wait until the RAN2872 process is completed before logging in.

g

Note: Do NOT delete the SOKERI account while RAN2872 report collection is ongoing. The report collection will fail and in addition, the account login will be blocked for an extended time period for security reasons (multiple failed logins), leading to long delays or even failure the next time symptom report data is collected. In the event that the SOKERI account is accidentally deleted during report collection, the login delay must be reset by using the commandZIAQ:TYPE=MML; after recreating the SOKERI account. This will reset the internal security mechanism for protecting against login attacks.

Procedure

1

Log in to the RNC MML console.

2

Trigger the data collection using the D5C command. Select from available options • D5C:S; collects data according to the standard profile. • D5C:B; collects data according to the basic profile. Step result The execution printout should resemble the following: RNC

IPA2800

2015-03-04 16:25:40

COLLECTING SYMPTOM DATA. USE 'E' COMMAND TO CHECK THE STATUS. COMMAND EXECUTED

3

Check the progress of the collection on the RNC from the notification alarm 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION , or wait for the alarm 71106 TROUBLESHOOTING DATA RECEIVEDto be raised on OMS. The notification alarm0199 is raised to indicate the progression of the symptom report collection. The alarm can be checked with the commandZAHP::NR=0199;. There should be three alarm events during collection:

236

©2016Nokia

DN09203161Issue:02


•


Collection started HST (07633) IPA2800 EQUIPM 04 09:29:42.40 NOTICE NONE 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION LCHPRO OMU-0 NMS RNCBASIC.XML NULL NULL

•

Collection finished and stored to disk HST (07636) IPA2800 EQUIPM 04 09:33:27.02 NOTICE NONE 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION LCHPRO OMU-0 NMS RNCBASIC.XML SYMP0468 NULL

•

2015-06-

2015-06-

Symptom report uploaded to OMS HST (07637) IPA2800 EQUIPM 04 09:33:57.54 NOTICE NONE 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION LCHPRO OMU-0 NMS RNCBASIC.XML NULL SYMP0468.ZIP

2015-06-

The OMS alarm is raised when the collection process has finished and the symptom report is uploaded successfully.

Result The Symptom report is stored on the RNC hard disk in the location /eclipse/var/symptom/ with a name in the formatSYMPxxxx.ZIP The report is also uploaded and stored on the OMS disk in the location /var/opt/OMSftproot/NE/TroubleshootingData with a name in the format TSUPL__..zip. Error messages •

/*** COLLECTION IS ONGOING. TRY AGAIN LATER ***/

A second symptom data collection was attempted while the first is ongoing. Wait until the current collection finishes, and try the command again. •

/*** SOKERI ACCOUNT DOES NOT EXIST ***/

The SOKERI account should be created before the symptom report can be collected. •

/*** COLLECTION REQUEST REJECTED DUE TO SYSTEM OVERLOAD. ***/

Symptom data collection does not start when the CPU load is over 80%. Wait until the load drops below this level to start the command. In addition to the error message, the network element will raise the alarm 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILEDif an error occurs during collection or upload of the symptom report.

DN09203161Issue:02

©2016Nokia

237



6.7 RAN3063: KPI Reporting Based on Cell Type Introduction to the feature The RAN3063: KPI Reporting Based on Cell Typefeature provides a new cell classification type identification to the RNC, allowing operators to filter the existing KPIs based on cell type.

6.7.1

RAN3063 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits With the RAN3063: KPI Reporting Based on Cell Typefeature, customers are now able to define their own criteria for cell type classification. Customers can analyze, manage, and optimize network performance based on the cell type through prime KPI values. This introduces OPEX saving, when the cell type can be identified unambiguously.

6.7.2

RAN3063 Functional description The RAN3063: KPI Reporting Based on Cell Typefeature introduces a new BTS cell classification identification type to the RNC to identify the micro, pico, or any other type of low power level node (LPN) from the current macro cells. This classification can be used later to identify those cells that need special actions from either system or operability point of view. Additionally, as an alternative, the operator can use this new identification for making his own BTS categorizations, allowing the operator to get subgroup KPIs from a smaller group of BTSs.

6.7.3

RAN3063 System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network and network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

6.7.4


238

©2016Nokia

DN09203161Issue:02


Table 100 RAS



WCDMA 16

RNC16

mc R N C

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2



MS C

S GSN








There are no hardware requirements for this feature. Alarms There are no alarms related to this feature. Counters There are no counters related to this feature. Key performance indicator There are no key performance indicators related to this feature. Parameter Table 101

New parameters introduced by RAN3063

F u l ln a me

CellType

A b b r e v i a t e dn am e

CellType


WCEL



BS W/ASW

ASW

6.7.5


RAN


RNC LK

Activating RAN3063: KPI Reporting Based on Cell Type Purpose Follow this procedure to activate the feature. Before you start Make sure that WCEL object with the specified CellType parameter is already created.

DN09203161Issue:02

©2016Nokia

239



Procedure

1

Set the feature state to ON. The feature code for this feature is 5574. Use the following commands: •

for IPA-RNC :

•

for mcRNC:


2

6.7.6

Modify CellType parameter to a predefined value or user defined value.

Verifying RAN3063: KPI Reporting Based on Cell Type Purpose The purpose of this procedure is to verify the usage of the KPI reporting based on cell type. Before you start The RAN3063: KPI Reporting Based on Cell Typefeature is activated. Make sure that you have access to NetAct Performance Manager.

240

©2016Nokia

DN09203161Issue:02



Procedure

1

Click on Reporting Tools ► Report Creator ► CM Viewer Sub-steps

a) Select Technology

b) Select Hierarchy containing WCEL

c) Select Object Level

d) Select Object Filtering

e) Click Edit configuration Management Selection

2

On the WCEL CM Parameter Set, click Cell Type and then click > to transfer on the Aggregation pane. Figure 24

g

DN09203161Issue:02

Configuration management selection window

Note: You can select Filtering to see available values, and filter the output by cell type.

©2016Nokia

241



3

Edit time selection

4

Edit KPI/counter selection

5

Select KPI > Preview Report

6

Generate Report

g 6.7.7

Note: In order to have the cell type available in reporter, Reporting Suites WCDMA 16 package should be installed.

Deactivating RAN3063: KPI Reporting Based on Cell Type Purpose Follow this procedure to deactivate the feature. Before you start The RAN3063: KPI Reporting Based on Cell Typefeature is activated. Procedure

1

Modify CellType parameter to "Not_defined".

2

Set the feature state to OFF. The feature code for this feature is 5574. Use the following commands: •

for IPA-RNC:

•

for mcRNC:

ZW7M:FEA=5574:OFF; set license feature-mgmt code 0000005574 feature-adminstate off

6.8 RAN3150: mcRNC Event Based Symptom Data Collection The RAN3150: mcRNC Event Based Symptom Data Collectionfeature introduces event based symptom data collection in the mcRNC. Given that the RNC software is large and complex, fault tracking and troubleshooting take considerable time. Most often, the information available on the problem ticket is inadequate and delays the solution.

242

©2016Nokia

DN09203161Issue:02


6.8.1


RAN3150 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits Operators benefit from faster troubleshooting.

6.8.2

RAN3150 Functional description The RAN3150: mcRNC Event Based Symptom Data Collectionfeature helps overcome the hurdles of the large RNC software and its complexity. The feature also provides an easier and faster means for symptom-data collection from customer sites. With this feature, the mcRNC automatically collects the symptom data related to a failure event based on the user's selected or predefined filter conditions. Figure 25: High level overview of the HIT base Fishing macro in mcRNC16is the overview of this feature. Figure 25

High level overview of the HIT base Fishing macro in mcRNC16

This feature provides the operator the option to: •

•

select the triggering events: RNWcounters, mcRNC (RNW and platform) alarms, master syslog writing or DMX message. select the required symptom data among: – – – –

g

DN09203161Issue:02

CP message monitoring UP message monitoring master syslog WCDMA BTS snapshot Note: WDMA BTS snapshot is offered only if the selected trigger is related to a WCDMA BTS.

©2016Nokia

243



For more information on using the HIT based fishing macro, see TN38 available in Product Information Center.

6.8.3

RAN3150 System impact Interdependencies between features This feature is interdependent withRAN2973: Enhanced IMSI based call monitoring . If there is a user plane resource unit common betweenRAN3150 and RAN973, the latter request is rejected as a multi session for the user plane message monitoring. This feature can be used in parallel with: • •

g

General DMX message monitoring from Megamon mcRNC symptom report collection Note: Only one monitoring session (SCLI-based or RAN3150) can be running for mcRNC. The mcRNC must be reserved before running this feature or another SCLI monitoring session.

Impact on interfaces This feature has no impact on interfaces. Impact on commands There are no commands related to this feature. Impact on network and network element management tools There are no impact on network and network element management tools. Impact on system performance and capacity Relative increase in USPU/CSPU Linux CPU load at base load of around 68% is at around 10.14%. Relative increase in USPU Simple Executive load at base load of 75% is at around 13%. There is no overload control applied for Control Plane message monitoring using this feature. Instead, when this feature is active on an overloaded unit, Control Plane message monitoring shall continue, but there would be an increase in rejection of new RRC connection requests. As a result, an impact is seen on related KPIs from the overloaded Control Plane units. This feature does be not impact the stability of the system, meaning that there would not be any unit or system restarts. There would not be any impacts to WBTS connectivity from the mcRNC.

g 6.8.4

Note: For User Plane monitoring initiated by this feature, upon detection of overload is detected, monitoring is be paused in the impacted unit. User Plane Monitoring is resumed when the overload situation has been rectified.

RAN3150 Reference data Reference

244

©2016Nokia

DN09203161Issue:02


Table 103 RAS



WCDMA 16

OMS


Planned for later releases

mcRNC

mcRNC16

NetAct



MS C



Flexi Multiradio 10 BTS


SGSN

MGW



Flexi Lite BTS



There are no hardware requirements for this feature. Alarms There are no alarms related to this feature. Counters There are no counters related to this feature. Key performance indicator There are no key performance indicators related to this feature. Parameters Call acceptability related KPIs are impacted if Control Plane units being monitored are overloaded. Sales information Table 104


BS W/ASW

BSW


RAN


-

6.9 RAN2991: Modification of WCDMA Frequency The RAN2991: Modification of WCDMA Frequencyfeature allows the operators to modify the BTS cell frequency within the same frequency band by using NetAct planning tools without the need for BTS reset and the delete/re-create of WCEL object in using new frequency.

6.9.1

RAN2991 Benefits End-user benefits

This feature lessens the possibility that the end-user might experience service interruptions and degradations during frequency modification activity. Operator benefits This feature benefits the operator as follows:

DN09203161Issue:02

©2016Nokia

245



•

•

•

6.9.2

This feature does not require BTS reset and therefore, reduces the numberof BTS outages when operators are performing frequency modification activity. This feature enables thecell frequency as amodifiable parameter in theRNC, and only requires a single configuration plan instead of the earlier implementation that needs two separate configuration plans for deletion and re-creation of cells. This feature introduces a faster implementation ofcell frequency modification.

RAN2991 Functional description Operators perform frequency refarming yearly for more efficient use of the existing frequency spectrum. Frequency refarming is the reallocation of regulated radio frequency spectrum to another use. For instance, the existing 2G frequency bands are to be used in 3G or LTE. Frequency refarming requires the modification of the cell frequency. The RAN2991: Modification of WCDMA Frequencyfeature supports the change of cell frequency without the need of BTS reset that leads to lesser BTS outages and disturbances to the traffic. The feature also introduces the use of a single RNW configuration plan to modify the cell frequency unlike the earlier implementation that requires two separate configuration plans to delete and re-create related cells. The RAN2991: Modification of WCDMA Frequencyis a NetAct-licensed feature wherein the license is installed and controlled in NetAct under the feature name CM Assisted WCDMA Frequency Retune for WCDMAand license code 10193. Operators are able to modify the cell frequency using the NetAct Configurator. NetAct also provides the notification if the requested task has been successful, or if a failure occurs during the activation of the frequency changing plan.

g

Note: The modification of frequency bySend to Network option is not supported in NetAct. This means that the Direct Activation (DA) operation cannot be used in modifying the cell frequency. TheSend to Network feature enables operator to create, modify, and delete managed objects without the need to create an RNW plan in the CM editor. For more information, seeNetAct 16.2 CM Editor Help in Send to network chapter. The modification of cell frequency in RAN2991: Modification of WCDMA Frequency feature is possible only in the following conditions:

•

Cell frequency changes are within the same frequency band. All the cells within the BTS from the frequency layer have been modified. The BTS is capable of changing the cell frequencywithout a BTS reset.

•

Cell frequency changes are within the radio hardware frequency capability.

• •

g

Note: Specific care must be applied when planning the frequency changes for individual BTS sites. The ensuring of frequency correctness for a specific BTS HW variant or BTS multi-RAT configuration is not checked automatically by the system, and changing the frequency can lead to failed cell setup.

g

Note: Other technology RF sharing cells (other than RF sharing WBTSs) experience temporary disturbances during the implementation of cell frequency changes. describes how RAN2991: Modification of WCDMA Frequencyfeature works.

246

©2016Nokia

DN09203161Issue:02


Figure 26


Frequency modification workflow

NetAct Configurator CM Editor

Operator creates the RNW plan

RNC

CM Operation Management

Operator initiates the download of RNW plan

Notify operator operation abort

BTS

Download RNW plan

Download fails: error report

Consistency check: OK

Notify operator operation abort

Validation fails: error report

RNW plan downloaded

Operator selects the RNW plan commands

Activation request

Activation Notify operator operation abort

RNW configuration modification

BTS does not incur reset

Activation fails: error report

Operation successful

Report

The operator creates the radio network (RNW) configuration plan for changing the cell frequency using the NetAct planning tool CM Editor, or the operator has the option to import the RNW configuration plan using the CM Operations Manager from an external source. After the completion of the RNW configuration plan, the operator initiates the RNW configuration plan download to the network elements using NetAct CM Operations Manager. But if the download fails, the RNC reports the errors to NetAct and aborts the operation. During the RNW configuration plan download, the RNC validates the RNW configuration plan by conducting the usual consistency checks and the following additional consistency checks that are introduced with this new feature: • • •

Are the cell frequency modification within the same frequency band? Are the cells within the BTS from the frequency layer possible to modify? Is the BTS capable of changing the cell frequency without aBTS reset?

The BTS indicates the feature support by setting theCell Frequency Change Without Reset capability in NBAP: CAPABILITY INDICATIONmessage and sends this message to the RNC. All the consistency checks must be satisfied and if the validations fail, the RNC reports the error to NetAct and the operation is aborted. The BTSs using older than WN8.0 SW build are capable to support the frequency change but are incapable to reportCell Frequency Change Without Resetcapability. For those BTSs, Consistency Check Rule Mask parameter with BTS Frequency

DN09203161Issue:02

©2016Nokia

247



Change Allowed capability is introduced. The Consistency Check Rule Mask parameter defines the functionalities that are allowed to be used bypassing the corresponding consistency check rule for the function. Thus,BTS Frequency Change Allowed capability allows the frequency change, even though the BTS does not report the Cell Frequency Change Without Resetcapability to the RNC.

g

Note: The BTSs using equal or newer than WN8.0 SW build but older than WBTS16 SW build are incapable to support the frequency change without reset. Setting BTS Frequency Change Allowedcapability in Consistency Check Rule Mask parameter for those BTSs might cause unnecessary disturbances to the end user traffic. The operator then selects the RNW configuration plan to be activated in the network elements and gives the activation command using CM Operations Manager. The RNC receives the activation command and activates the RNW configuration plan. During the activation, the RNC performs the following tasks: • • •

g

Lock and unlock each cell while performingthe RNW configuration changes. Send CM events to NetAct for each change that has been made. Distribute the RNW configuration changes to the BTSs. Note: If the activation fails, the RNC reports the errors to NetAct and the operation is aborted.

The operator can select the activation mode of RNC RNW plan by means of optional features such as Object by Object (Slow), Use Activation Groups (Moderate), All Objects Parallel(Fast). For more information, seeNetAct 16.2 CM Operations Manager Helpin Provisioning plans, Service impact level for RNC plan activation and RAN212: Selectable RNW Plan Activation Mechanism feature. The BTS performs the RNW configuration modifications and changes the value of the defaultCarrier parameter based on theUARFCN. The value of the defaultCarrier parameter can be modified on-line by NetAct or BTSSM but the new value is taken into use in that case after the next BTS restart. However, the merging of frequency layers is prevented because this leads to rollback failure in NetAct. Ensure the cells that share the same antennas are configured with the same frequency layer.

6.9.3

RAN2991 System impact Interdependencies between features There are no interdependencies between any other features. Impact on interfaces BTS-RNC The BTS informs the RNC about the capability of supporting cell frequency changes without a BTS reset by setting the Cell Frequency Change Without Resetbit in NBAP: Capability Indication message. Impact on network and network element management tools There are no impacts on the network and network element management tools for this feature.

248

©2016Nokia

DN09203161Issue:02



Impact on system performance and capacity There are no impacts on system capacity for this feature.

6.9.4



RAS

I PA - R N C

WCDMA 16

mc R N C

RNC16

mcRNC16

OMS

NetAct


NetAct 16.2


WBTS16

MS C

S GSN




WBTS16

Not planned

MGW


UE


This feature does not require additional hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no new measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 106

Existing parameters related to RAN2991

F ul l n ame

A b b r e v i a t e d n a me

Networ k elemen t

UTRA Absolute Radio Frequency Channel Number

UARFCN

RNC

Default carrier

defaultCarrier BTS

Consistency check rule mask

ConsCheckRuleMas RNC k

M an ag e d o bj e c t

WCEL

LCELW WBTS



BS W/ASW

ASW NetAct

DN09203161Issue:02


RAN

©2016Nokia


NetAct

249


6.9.5


Testing RAN2991: Modification of WCDMA Frequency Purpose This test case verifies that BTS restart, deletion, and re-creation of a cell are not needed in modifying cell frequency when all the following feature conditions are fulfilled: The cell frequency changes shallbe within the same frequency band. The cell frequency changes arewithin the radio hardware frequency capability.

• •

All the cells within the BTS from the frequency layer are modified. The frequency and cell adjacency is modified consistently. The BTS is capable of changing the cell frequencywithout a BTS reset.

• • •

g

Note: Other technology RF sharing cells will experience an outage when performing cell frequency changes for RF sharing WBTSs.

g

Note: This is an example of the verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks. Before you start The following are the equired test environment and settings: •

The Radio Access Network (RAN) andOperational Core network(CN) are operational.

•

•

The BTS is connected to OMS and NetAct. The BTS configuration is F222 or F333. The system module is rel2 or rel3.

•

The RF module is FXDA for 900MHz or FRGT/FRGP for 2100MHz.

•

Procedure

1

Create the RNW plan for changing the cell frequency (UARFCN) with CM Editor, or import the RNW plan with CM Operations Manager from an external source. The plan should fulfill the feature limitations. For more information regarding procedures for existing adjaciencies, see NetAct documentation- CM Editor Help section 2.3 Modifying UARFCN parameter .

2

Download the RNW plan t o the network elements with CM Operations Manager. The RNC validates the downloaded RNW plan.

3

Select and activate the RNW plan in CM Operations Manager. NetAct notifies that the operation is successful.

250

©2016Nokia

DN09203161Issue:02



Result Expected result: The cell frequency is modified without the need of BTS restart, and the deletion/creation of cells. Other information: Figure 27

NetAct CM Editor view in modifying UARFCN

6.10 RAN2268: Multi-Layer Certificate Authorities Introduction to feature The RAN2268: Multi-Layer Certificate Authoritiesfeature brings WCDMA BTS to parity with LTE eNB in terms of certificate management. This feature applies to WBTS Flexi.

6.10.1

RAN2268 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits

DN09203161Issue:02

©2016Nokia

251



The customer is able to set up a commercial public key infrastructure (PKI) with a Root certificate Authority on top and subordinate certificate authorities (CA) in charge for signing the nodes. 3GPP compliant life cycle management allows a harmonized networkwide and inter-RAT handling, which leads to considerable OPEX reductions.

6.10.2

RAN2268 Functional description The RAN2268: Multi-Layer Certificate Authoritiesfeature adds the support for automated and 3GPP compliant operator certificate life cycle management and revocation list management for multi-layer hierarchical PKI structures to BTS. Operator certificate management and trust anchor enrolment The certificate life cycle management between the BTS and the operator PKI is based on CMPv2 for initial operator certificate enrollment (initial key signing) and the automated operator certificate update (key update), in case the certificate lifetime is close to expire. The BTS supports CMP message signing by an RA, that is, although the certificate is issued and signed by a CA, the CMP messages are signed by an RA acting as gatekeeper in front of the signing CA. The common rules for certificates and the enrolment of operator BTS certificates follow 3GPP Release i11 "TS 33.310 Network Domain Security - Authentication Framework":

•

The BTS uses the vendor certificate for initial authentication toCA. If no Vendor certificate available, then theNB is able to use PSK/Refnum if it was pre-configured by the operator. SHA-1 and SHA-256 are supported as hash algorithms for certificate signs.

•

The signing CA key length can be 2048, 4096, or 8192 bit.

• •

The own trust chain of Root CA and sub-ordinate CA certificates is delivered via CMP protocol exchange from the signing CA or manually via the element managers. The operator is able to use the element managers to trigger the repetition of certificate initialization and key update on demand and to remove a trust anchor from the trust pool. With the NetAct CERMA tool, the operator is able to trigger for all or a list of BTS the certificate initialization and key update and trust anchor removal.

g

Note: The update of an expiring operator certificate is authenticated by the current operator certificate while the enrolment for BTS uses the vendor certificate or PSK/Refnum for the initial authentication for both BTS. Trust Anchor and Cross-signed certificate enrolment for BTS The BTS supports the integration of a second operator PKI. If the trust relation is established either by a second trust anchor or a cross-certification, the operator is able to store a second trust anchor or cross signed certificate into the BTS trust pool by the following options: •

manually with the BTS site manager (BTSSM) per individual BTS

•

with a NetAct script utilizing the BTSSM command line for a list of BTS

The operator can update a stored additional trust anchor or cross-signed CA certificate at any point in time. Nevertheless, the BTS sends an alarm to NetAct whena trust anchor a cross-certificate is close to expire. The BTS applies the same pre-warning time value as used for the own CA signing certificate expiry supervision.

252

©2016Nokia

DN09203161Issue:02



If notified, the operator can now add a trust anchor or cross-signed CA certificate manually via the BTSSM, either individual per BTS or with NetAct scripting for a list of BTS. The available trust anchor or cross-signed certificate is not automatically removed to allow a smooth migration to a new trust relation. Thus, for a certain time, two trust anchors and two cross-certified certificates can be handled by the BTS. Trust Anchor and Cross-signed certificate removal from BTS An expired or unneeded trust anchor or cross-signed certificate can be deleted from the trust pool with the NetAct CERMA Tool or with the BTSSM. The BTS does not remove trust anchors or expired cross-signed certificates autonomously. Revocation List Management The revocation list management enhances the existing BTS CRL management for the single CRL distribution point (CRLDP) learned from the own operator BTS certificate by the download of further CRLDPs given within sub-ordinate CA certificates of the own certification path and by the capability to configure additional CRLDP. Overall CRL Activation The operator is able to activate or deactivate CRL execution for the whole BTS by a configurable attribute with the Element Manger and NetAct Configurator. Configurable CRL distribution points The BTS ignores all CRLDP contained within the entity certificate of the remote peer and within all sub-ordinate CA certificates of the remote peers trust chain received as part of the secured connection establishment. To extend the revocation checks in addition to the existing CRL handling of the own certification path, the BTS supports configurable CRL sources. The BTS offers up to 10 primary and 10 secondary CRLDP entries, which can be configured for LDAP download individually as static IP address with path to directory or FQDN with path to directory. The parameters can be set with the element mangers and NetAct Configurator. The operator can use them to configure CRLDP in addition or instead to the CRLDP within the certificates of the own certification path and/or further certification paths of the own operators' PKI.

6.10.3

RAN2268 System impact Interdependencies between features The RAN2268: Multi-Layer Certificate Authoritiesfeature enhances the network element certificate management feature family. The certificate mangement lifecycle management for BTS OMS requires the following OMS features:

•

RAN2267: Certificate management for OMS products RAN2367: DNS Support for Certificate Examination

•

RAN2919: OMS Certificate update and revocation support

•

Impact on interfaces There is no impact on interfaces. Impact on network and network element management tools There is no impact on network and network element management tools. Impact on system performance and capacity

DN09203161Issue:02

©2016Nokia

253



There is no impacts on system performance and capacity.

6.10.4



RAS

I PA - R N C

mc R N C

WCDMA16


OMS

NetAct

WCDMA OMS16

NetAct 16.2

Planned for later releases MS C

Flexi Multiradio BTS WBTS16

S GSN


Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16

MGW


Not planned

UE



There are no hardware requirements for this feature. Alarms Table 109

New alarms introduced by RAN2268 A l a r mI D

A l a r mn a m e

D e s c ri p ti o n

61618

BTS Trust Anchor expired or due to expire

61074

CRL Update Failure

This alarm is set when all trust anchor certificate lifetime below a configurable time or its own trust anchor is expired This alarm is raised if the BTS cannot update any of the certificate revocation list. An update of the CRL is attempted on request of the operator.

Counters There are no counters related to this feature. Key performance indicators There are no KPIs related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature. Sales information Table 110


BSW /ASW

BSW

254


RAN

©2016Nokia


-

DN09203161Issue:02



6.11 RAN3096: OMS HP Gen9 HW Introduction to the feature The RAN3096: OMS HP Gen9 HW feature introduces new hardware (HW) for WCDMA standalone OMS, particularly the HP Proliant Gen9 blade and rack servers, to replace the HP Proliant Gen8 server. For more details, see HP Proliant DL360 Gen9 and HP Proliant BL460c Gen9 inOMS Product Description.

6.11.1

RAN3096 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides better performance as compared to Gen8. Gen9 uses less time for event handling and task processing commanded by NetAct. Thus, Network management works faster end to end. It also makes OMS less sensitive to unexpected and extremely high overload situations. The OMS connectivity remains the same as with Gen8 HW.

6.11.2

RAN3096 Functional description With the RAN3096: OMS HP Gen9 HW feature, standalone OMS HW can be replaced with the new HP ProLiant DL360 Gen9 and HP ProLiant BL460c Gen9. The technical details of WCDMA OMS Gen9 are as follows: •

Server model: DL360 (rack-mounted) –

CPU: 2 x 12-core

–

RAM: 64 GB HDD capacity: 4 x 600 GB / 15k rpm Ethernet Connectivity: 4 x 1 Gbe Ethernet ports ( two ports areused, as in Gen8 and G6)

– –

•

Server model: BL460c (blade) – – – –

6.11.3

CPU: 2 x 12-core RAM: 64 GB HDD capacity: 2 x 600GB / 15k rpm Ethernet Connectivity: 2 x 10 Gb Ethernet ports (1 Gb Ethernet is also supported)

RAN3096 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools

DN09203161Issue:02

©2016Nokia

255



This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

6.11.4



RAS

I PA - R N C

mc R N C


Flexi Flexi Lite Multiradio 10 BTS

WCDMA 16





OMS

WCDMA OMS16

NetAct

MS C


S GSN


MGW





This feature requires the HP Proliant DL360 Gen9 and HP Proliant BL460c Gen9. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 112


BSW /ASW

BSW


RAN


-

6.12 RAN2702: Parameter Level Logging of BTS User Events Introduction to the feature The RAN2702: Parameter Level Logging of BTS User Eventsfeature is an enhancement to remote user event log management (RUEM) for the BTS. It provides Parameter Level Logging of User Events invoked from the BTS site manager (BTSSM). Once the NetAct retrieves the logged content using the existing RUEM mechanism, the user can then

256

©2016Nokia

DN09203161Issue:02



view the details on the Security Information and Event Management (SIEM) system. With the SIEM system, an operator can audit configuration changes done by the BTSSM with enhanced details of parameter name, parameter value, and execution status.

6.12.1

RAN2702 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The operator can monitor user events initiated from the BTSSM on the SIEM system with additional details, including target object name, parameter name, and parameter value to be. Done and missed configurations can be identified much faster thus, limiting network problems or even network outages.

6.12.2

RAN2702 Functional description The RAN2702: Parameter Level Logging of BTS User Eventsfeature adds parameter level details to the RUEM log for user requests initiated from the BTS Site Manager. User requests initiated from the BTS Site Manager Parameter level details of this type of request and the corresponding response are added to the RUEM log. Parameter details typically include parameter name and parameter value it would be changed into. Some requests also include object name, for example, RAML Request. For the user requests and responses that are currently logged, parameter's level details are added to RUEM log. A RAML Request contains multiple operations on multiple objects and parameters. The operations impacting BTS configuration or service are logged along with the targeting objects and parameters. Requests and corresponding responses are correlated. A single RUEM log entry generated for each operation and targeting object pair. Configuration files, such as SiteConf files, can be downloaded from BTS Site Manager. When activated, they introduce many configuration changes to the BTS. However, those changes are not recorded in RUEM log, thus excluded from this feature. The user can retrieve the configuration files from the BTS Site Manager to get details. Execution failures related to the configuration files are logged in other type of logs.

DN09203161Issue:02

©2016Nokia

257


6.12.3


Figure 28

RUEM Log File Format

Figure 29

SIEM system GUI

RAN2702 System impact Interdependencies between features This feature is an enhancement to RU10RAN616: Centralised User Event Log Management for BTS feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network and network element management tools. Impact on system performance and capacity

258

©2016Nokia

DN09203161Issue:02



With the additional parameter level details, the amount of logs to be uploaded from the BTS to NetAct are expected to increase. This would result in more frequent upload of logfiles and the average logfile size also increases. There are no performance degradation in NetAct, the BTS, or the communication between the two. Additional memory space and processing time on the BTS and NetAct needs to be allocated to handle the extra parameter level logging. But BTS and NetAct must have enough capacity to support the additional memory space.

6.12.4



RAS

I PA - R N C

mc R N C

WCDMA 16



OMS

NetAct


NetAct 16.2

MS C



WBTS16


WBTS16

S GSN


MGW


Not planned

UE


There are no hardware requirements for this feature. Alarms There are no alarms related to this feature. Measurements and counters There are no measurments and counters related to this feature. Key performance indicators There are no KPIs related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature. Sales information Table 114 BSW /ASW

ASW NetAct

6.12.5

RAN2702 Sales information S Wc o m p o n e n t

RAN

L i c e n s ec o n t r o li nn e t w o r k element

-

Testing RAN2702: Parameter level logging of BTS user events Purpose

DN09203161Issue:02

©2016Nokia

259



The purpose of this test is to verify if the RAN2702: Parameter level logging of BTS user events feature is activated and working correctly. Before you start The following are the required test environment: Operational Radio Access Network and Core Network FSMr2 or FSMr3 platform.

• •

The following are the required software: RNC16 NetAct 16.2 OMS16 WBTS16 Audit Trail16

• • • • •

Procedure

1

Enable Automatic RUEM files uploading to Audit Trail.

2

In BTS Site Manager perform basic actions, for example enable/disable SSH.

3

Wait for about two to three hours.

4

Open NetAct Audit Trial and confirm if perfomed actions were logged.

5

Disable Automatic RUEM DB files uploading to Audit Trail.

Result Every action perfomed in BTS Site Manager should be visible in Audit Trail.

g

Note: Reboot BTS and Recover BTS are not logged in RUEM logs when BTS resets happens quickly before the log can be written. This also happens if the BTS is in a state that prevents writing of RUEM log, for example, Linux reboot, watchdog reset, system crash, and so on.

6.13 RAN2571: Support of TLS 1.2 Introduction to the feature As the support of TLS 1.0 is discontinued by 3GPP Rel 9, TLS 1.2 is now used as the default protocol together with the cipher suites specified for TLS 1.1 and TLS 1.2. The new version fixes well known TLS/SSL MAC security flaw vulnerabilities.

6.13.1


260

©2016Nokia

DN09203161Issue:02



This feature does not affect the end-user experience. Operator benefits The Flexi Multiradio BTS is compliant with 3GPP security recommendation, requiring TSL 1.2 support.

6.13.2

RAN2571 Functional description The RAN2571: Support of TLS 1.2feature enhances the Transport Layer Security Protocol (TLS) support on the network elements in WCDMA RAN and other related tools, so that they are compliant with the regulations specified in 3GPP Release 12 TS 33.310. The purpose is to mitigate security vulnerabilities identified in TLS 1.0 and remedied in TLS 1.2. This feature also improves the security of RAN system by using stronger ciphers for TLS connections. The 3GPP Release 12 requires the TLS end points to support TLS 1.1 and TLS 1.2. Prior to this feature, the network elements in RAN support only TLS 1.0. In this feature, OMS, OMS Element Manager, BTS, and BTS Site Manager (BTSSM) are upgraded to support TLS 1.2. They continue to support TLS 1.0 when needed to be compliant with release backward compatibility. The RNC remains unchanged in this feature, so the RNC only supports TLS 1.0. The 3GPP Release 12 also requires the TLS end points to support the cipher suites mandatory to TLS 1.1 and TLS 1.2, and the stop of use of cipher suites with RC4. In this feature, OMS, OMS Element Manager, BTS, and BTSSM are installed with a list of stronger cipher suites, including the mandatory cipher for TLS 1.1 in RFC4346, the mandatory cipher for TLS 1.2 in RFC5246, and the mandatory cipher specified in 3GPP Release 12 TS 33.310. Some of those ciphers support Forward Secrecy. Prior to this feature, TLS_RSA_WITH_RC4_128_SHA cipher is used for file transfer on some interfaces. To support backward compatibility, this feature keeps the cipher supported on OMS, OMS Element Manager, BTS, and BTSSM, but with lowest priority. This feature does not change the cipher suites on the RNC. Some of the ciphers in the list of stronger ciphers proposed by this feature are already supported on the RNC prior to this feature. With the changes on OMS and BTS, their interfaces to the RNC no longer use RC4 cipher, instead, of one of the stronger ciphers is used. Additionally, 3GPP Release 12 requires TLS end points to support TLS 1.2 without compression, that is, CompressionMethod.null. Table 115: Ciphers in priorityis the list of ciphers in priority (first cipher as the most preferred and the last cipher as the least preferred) to be used by BTS and OMS on its interfaces. Table 115

Ciphers in priority List of supported ciphers

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256

DN09203161Issue:02

©2016Nokia

261



Table 115

Ciphers in priority (Cont.) List of supported ciphers

TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA

The RAN2571: Support of TLS 1.2feature covers Flexi BTS on FSMr3 platform, Flexi Lite BTS, and Flexi Zone Pico BTS. BTS on FSMr1 or FSMr2, UltaSite BTS, and SIMO BTS are out of scope.

6.13.3

RAN2571 System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces This feature is supported the following interfaces for BTS: • • • • • • • •

g

HTTPS interface between OMS and BTS HTTPS interface between BTS Site Manager and BTS TLS interface between OMS and BTS TLS interface between BTS Site Manager and BTS HTTPS interface between TransportWebPage and BTS TLS interface between TransportWebPage and BTS TLS interface between CNUM LDAP Server and BTS TLS interface between RNC/OMU and BTS Note: TLS interface between CNUM LDAP Sever and RNC/OMU to the BTS will only support TLS 1.0.

This feature is also supported for the following interfaces for the OMS: •

HTTPS interface between NetAct and OMS

• •

HTTPS interface between NE and OMS BTSOM interface between NE and OMS

•

HTTPS interface betweenOMS AL based element manager and OMS

• •

COBRA interface betweenOMS AL based element manager and OMS HTTPS interface between OMS Web UI and OMS

Impact on network and network element management tools There are no impact on network and network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

262

©2016Nokia

DN09203161Issue:02


6.13.4




RAS

I PA - R N C

WCDMA 16


OMS

NetAct

WCDMA OMS16

NetAct 16.2

mc R N C

Planned for later releases MS C


Not planned S GSN



WBTS16 MGW



Not planned UE


There are no hardware requirements for this feature. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no KPIs related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature. Sales information Table 117


BS W/ASW

BSW

DN09203161Issue:02


RAN

©2016Nokia


-

263



7 Performance monitoring features 7.1 RAN2164: Compensated CQI Measurement Introduction to the feature RAN2164: Compensated CQI Measurementfeature introduces WCEL level counters to show the compensated channel quality indicator (CQI) value that the BTS HSDPA scheduler algorithm is using for downlink scheduling decisions.

7.1.1

RAN2164 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature brings OPEX savings via reduced manual activity in investigating radio performance because of dedicated counters for compensated CQIs.

7.1.2

RAN2164 Functional description RAN2164: Compensated CQI Measurementfeature introduces the HSPA in WBTS extension counter group. This counter group consists of 36 Compensated CQI distribution class counters (COMPENSATED CQI DISTRIBUTION-CLASS 0, CLASS 1, ... CLASS 35). This feature compensates the reported CQI for the distortion caused by the RAN1224: HSDPA Dynamic Power Allocationfeature. The retrieved measurement reports are used to optimize the HSDPA scheduler algorithm in the BTS. The BTS gives a maximum throughput for sophisticated UEs when compensated CQI values 31..35 are used (raw values are only from 0…30). For the detailed counter list, seeMeasurements and counters.

7.1.3

RAN2164 System impact Interdependencies between features There are no features interdependent withRAN2164: Compensated CQI Measurement. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network and network element management tools. Impact on system performance and capacity This feature has no impact on system performance and capacity.

7.1.4


264

©2016Nokia

DN09203161Issue:02


Table 118 RAS

WCDMA 16



RNC16

mc R N C

mcRNC16

OMS

NetAct


NetAct 16.2


WBTS16

MS C


S GSN



WBTS16

Not planned

MGW


UE


This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurement and counters Table 119

DN09203161Issue:02


C o u n t e rI D

C o u n t e rn a me

M e a s u r e me n t

M5005C0

COMPENSATED CQI DISTRIBUTION - CLASS 0


M5005C1



M5005C2

COMPENSATED CQI


M5005C3

DISTRIBUTION - CLASS 2 COMPENSATED CQI DISTRIBUTION - CLASS 3


M5005C4



M5005C5



M5005C6



M5005C7



M5005C8



M5005C9



M5005C10

COMPENSATED CQI


M5005C11



M5005C12



M5005C13



©2016Nokia

265


Table 119



C o u n t e rI D

C o u n t e rn a me

M e asu r eme n t

M5005C14



M5005C15



M5005C16

COMPENSATED CQI


M5005C17



M5005C18



M5005C19



M5005C20



M5005C21



M5005C22



M5005C23



M5005C24

COMPENSATED CQI


M5005C25



M5005C26



M5005C27



M5005C28



M5005C29



M5005C30



M5005C31



M5005C32



M5005C33



M5005C34



M5005C35



Key performance indicators

266

©2016Nokia

DN09203161Issue:02



There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Commands There are no commands related to this feature. Sales information Table 120


BS W/ASW

BSW


HSPA


-

7.2 RAN2973: Enhanced IMSI Based Call Monitoring Introduction to the feature This feature provides following enhancements for RAN2930: IMSI based Call Monitoring: • •

• •

User and Transport Plane monitoring in mcRNC User Plane monitoring forCell_FACH state for mcRNC and IPA-RNC, where PDCP, RLC and MAC-d protocol headers are monitored in FACH, HS-FACH and HS-RACH transport channels Monitoring at Drift RNC side in IPA-RNC and mcRNC Enhanced decoding and graphical analysis of monitored data

This feature activation covers the combined functionality of RAN2930 and RAN2973 features. This functionality allows operator to collect and analyze data from Control, User and Transport planes for individual calls based on the specified IMSI numbers in IPARNC and mcRNC. Typical use cases for troubleshooting individual calls include (based on 3GPP TS 32.421 Subscriber and equipment trace; Trace concepts and requirements): • • • • • •

Multivendor UE validation: check howdifferent vendor's UEs are working Subscriber complaint: check howthe subscriber's services areworking in order to find out the reason for the complaint Malfunctioning UE: when the operator suspects thata UE is not working according to the specifications Checking radio coverage on a particular geographicalarea Testing a new feature Fine-tuning and optimization of algorithms/procedures

As the data is collected for monitored IMSI numbers only, the monitored data has very small size comparing to traditional methods of monitoring all calls in RNC. This also allows much more extensive data content including data from User and Transport Planes. Note that the monitored data content is limited to protocol headers and signaling messages, meaning that no end-user communication content, i.e. end-user speech and data, is collected due to legal requirements.

DN09203161Issue:02

©2016Nokia

267


7.2.1


RAN2973 Benefits End-user benefits Faster resolution of subscribers' complaints. Operator benefits Remote and fast network troubleshooting, verification and optimization of call related issues in Control, Transport and User Planes in mcRNC and IPA-RNC. Reduced need for external tracing equipment, such as Wireshark and NetHawk. Standard Windows PC hardware can support simultaneous monitoring in multiple RNCs.

7.2.2

RAN2973 Functional description Functional overview

268

©2016Nokia

DN09203161Issue:02


Figure 30


Overview of RAN2973: IMSI-based Call Monitoring GEO interface Extension option

L3DC

PS/CS Core IPA RNC/ mcRNC Control Plane + User Plane + Transport Plane:messages, logs, packetheaders

RNC

In IPA-RNC and mcRNC, this feature introduces collection of Control, User, and Transport planes monitoring data for individual calls based on given IMSI numbers. The data capturing is done with the help of the L3 Data Collector running on a standard Windows PC, and connected remotely to the monitored RNC. The data processing and analysis is done with the L3 Data Analyzer running on the same or on a different machine from the L3 Data Collector. The L3 Data Analyzer has the capability of analyzing Control, User and Transport Plane monitored data. The main benefit of this feature is that it allows a small size of the monitored data while providing comprehensive monitored data content for individual monitored calls. Note that neither end-user communication content, that is end-user speech and data, nor messages related to any other call(s) (uninterested calls) is collected by this feature.

DN09203161Issue:02

©2016Nokia

269



Data that could reveal customer identity such as the IMSI, the end user or the remote server IP addresses is encrypted at the RNC using a configurable encryption key. The same key is required for analyzing the monitored data at the L3 Data Analyzer tool. Monitored data content 1. Control Plane in control plane processing units (ICSU in RNC2600 and USCP in mcRNC): •

DMX messages from most of call handling program families

2. User Plane in user plane processing units (DMPG/DSP in RNC2600, USUP in mcRNC): •

•

Protocol headers on Iu-PS: The whole end-to-end IPv4 protocol header is monitored except for source and destination IP addresses. From the source and destination IP addresses, only the last octet of the four is captured. The other bits of the IP addresses are marked as zeroes in the monitoring data. The whole end-to-end TCP/UDP/ICMP header is monitored. Nothing is captured from the IPv4 packet payload. Figure 31

User Plane monitored data on Iu-PS interface

Figure 32

End-to end IPv4 packet TCP/UDP/ICMP

Protocol headers on Iu-CS: RTP, RTCP (not in RNC2600) and Iu-CS UP Figure 33

270

User Plane monitored data on Iu-CS interface

©2016Nokia

DN09203161Issue:02


g

Note: Only with CS Voice over HSPA.

g

Note: RTCP monitored only in mcRNC. •

Protocol headers onIub: FP, MAC, RLC and PDCP Figure 34

• •


User Plane monitored data on Iub interface for PS and CS calls

Internal messages related to L3-L2 interfaces L2 internal protocol interfaces(such as RLC-MAC), internal data(such as scheduling info), minor and severe errors, exceptions

3. Transport Plane in transport plane processing units (NPGE in RNC2600, EITP in mcRNC): •

Protocol headers on Iu-PS: outer IP , UDP, GTP-U, inner IP, inner TCP/ICMP/UDP Figure 35

•

Iu-CS: IP/UDP/RTP/IuUP headers, IP/UDP/RTCP full packet Figure 36 Transport Plane monitored data on Iu-CS interface (RTP) (1 of 2)

Figure 37

•

DN09203161Issue:02

Transport Plane monitored data on Iu-CS interface (RTP) (2 of 2)

Iub: IP/UDP/FP headersand MAC/RLC headers of the first PDU Figure 38

g

Transport Plane monitored data on Iu-PS interface

Transport Plane monitored data on Iub interface

Note: Tail only for DCH transport

©2016Nokia

271



Site configuration • •

7.2.3

In RNC2600, the monitored data collection is performedvia O&M connection to RNC. In mcRNC, it is required to install Ethernet switch onsite as the monitored data collection is done via one SFP port in each BCN box. Existing Megamon/L3Analyzer installed solution can be re-used.

RAN2973 System impact Interdependencies between features 1. Operations causing high OMU load, for example IPA-RNC symptom report collection or file compress/uncompress operations, can cause pausing of RAN2973 monitorings 2. General Control Plane monitoring using L3 Data collector can be used in parallel with this feature in a different L3 Data collector session 3. General Control Plane/User Plane monitoring using MML/SCLI can be performed in parallel with this feature 4. General/ Event triggered Symptom report collection in mcRNC can be performed in parallel with this feature. Impact on network and network element management tools No impact. CPU loads of the monitored units can increase up to 10% (relative). There is no additional CPU load increase in Control Plane units in case RAN2973 feature is activated additionally to general L3 Data Collector (Megamon) message monitoring. Impact on system performance and capacity No impacts to KPIs. CPU loads on monitored units will increase to maximum 10%.

7.2.4

RAN2973 Reference data Requirements Software requirements Table 121

RAS

RAN2973 Software requirements

IPA-RNC

WCDMA 16 RNC16

mcRNC

mcRNC16

Flexi Flexi Multiradi Multiradio o BTS 10 BTS

Support not


Flexi Lite BTS


required

OMS

NetAct

MSC

SGSN

MGW

Support not Support not Support not Support not Support not required required required required required

272

©2016Nokia

UE


DN09203161Issue:02


Table 122


External monitoring tool requirements

Tool name

P ur p o se

R e l eas e

L oc at i on

L3 Data collector

For collecting TSS16 the monitored data

From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Data Collector (Megamon) → Release: LDC TSS16 → Standard Update → Maintenance Packet .

L3 Data Analyzer

For decoding TSS16 the monitored data

From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Analyzer/Viewer (Emil) → Release: LDC TSS16 → Standard Update → Maintenance Packet .

Hardware requirements This feature requires external monitoring machine with standard Windows PC HW to run L3 Data Collector (Megamon) SW. No high performance server HW is required to support simultaneous motoring in multiple RNCs. Transport requirements In IPA-RNC, O&M interface is utilized to control and stream monitored data to remote L3 Data Collector (Megamon). In mcRNC, a private monitoring network needs to be created, where SFP21 or SFP22 ports (or both ports) of each mcRNC module and L3 Data Collector (Megamon) are interconnected via 1G Ethernet Switch. The monitoring network is the same as used in general L3 Data Collector (Megamon) solution, allowing simultaneous usage of RAN2930/RAN2973 and general L3 Data Collector (Megamon) message monitoring. This feature requires TCP/UDP ports 8020 and 8021 be enabled in the transport network. This feature requires at minimum 5 Mbps bandwidth to support the maximum amount of monitored calls. Average monitored data throughput for a single call: • • •

Control Plane – 50 kbps (BA compressed) User Plane – 1 Mbps (varies significantly based on monitoring condition) Transport Plane – 5% of end-user throughput. Forexample, 20 Mbps end-user throughput results in 1 Mbps monitoring data throughput

Restrictions for RAN2973: Enhanced IMSI-based Call Monitoring

g

Note: Real time analysis of monitored data in L3 Data analyzer is not supported for User Plane and Transport Plane monitoring • •

Only IP transport (IPV4) is supported for troubleshooting. User Plane monitoring cannot bestarted for branchesof ongoing calls. Only calls created after monitoring is started can be monitored.

General The number of IMSIs that can be monitored per RNC simultaneously is limited.

DN09203161Issue:02

©2016Nokia

273


Table 123


Maximum number of calls that be monitored based on RNC and monitoring configuration Fi l ter

M a x i m u mn u m b e ro f c a l l s t h a t c an b e monitored

Control Plane only

16: IPA-RNC (RNC2600), mcRNC

Control Plane and User Plane

4: IPA-RNC (RNC2600), 16: mcRNC

Control Plane and Transport Plane


Control Plane, Transport Plane, and User Plane


Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 124


BSW/ASW

SW component


ASW

RAN

RNC LK

For external monitoring tool sales information (that is, Megamon and IMSIMon3G), see the appropriate Technical Support Solutions (TSS) in NOLS.

7.2.5 7.2.5.1 7.2.5.1.1

Activating and configuring RAN2973: Enhanced IMSIbased Monitoring Activating RAN2973: Enhanced IMSI-based Monitoring on IPA-RNC Configuring GIVAXI/givClient Purpose Givaxi is an application in IPA-RNC that implements L3 Data collector interface for control and data protocols

274

©2016Nokia

DN09203161Issue:02



Procedure

1

Check Givaxi port status. ZQRS:OMU,0;

Step result The output must include: The output must include: UNIT: OMU-0 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address State tcp 0 0 *.8021 LISTEN

Foreign Address *.*

If not displayed correctly, execute the following command: ZWOC:2,2093,002;

Wait until port 8021 status shows LISTEN. It takes approximately 20 seconds.

7.2.5.1.2

Installing licenses for IPA-RNC Procedure 1

To set the feature state to ON, use the following command: ZW7M:FEA=:ON;

The following features need to be turned on: Table 125

Licenses for RAN2973: IMSI-based Monitoring Ty p e

Feature

g

DN09203161Issue:02

Co de

0000005261

Objec Nta m e

IMSI-based Call Monitoring

SW Licence Key SI

RU00552

IMSI-based Call Monitoring Test LK

Software SI

RU00551.T

IMSI-based Call Monitoring LTU

SW Licence Key SI

RU00551

IMSI-based Call Monitoring LK

Note: The feature code should be added to the command.

©2016Nokia

275


7.2.5.1.3


Installing L3 Data Collector Procedure

1

7.2.5.1.4

From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Data Collector (Megamon)

Authorizing Pre-Shared Key (PSK) It is required that PSK authentication is successfully completed before the solution works. This requires that the same PSK is administered in both the external monitoring tool and IPA-RNC. Procedure

1

Set message monitoring encryption preshared key for L3 Data Collector (Megamon) interface. The (AES256 crypted) shared key (256bit) must be set by Q4-mml. 256bits/8=32 bytes so the key must be 32 bytes long. ZQ4A:GIVAXIPSK,S:K:H:;

Step example >ZQ4A:GIVAXIPSK,S:K:H:; ENTER KEY(MAX 64 HEXADECIMAL DIGITS): 1234567890ABCDEFFEDCBA09876543211234567890ABCDEFFEDCBA0987654321

7.2.5.1.5

Configuring MSGMONPSK for data encryption Procedure

1

For data encryption key authentication, use the following command: ZQ4A:MSGMONPSK,S:K:H;

Step example ENTER KEY(MAX 64 HEXADECIMAL DIGITS): 1234567890123456789012345678901234567890123456789012345678901234

This key is then required to be provided at the L3 Data Analyzer tool while opening the monitored Control Plane data. This is unrelated to the GIVAXIPSK that was set in the previous step.

g

276

Note: This key must always be 64 ASCII characters in size.

©2016Nokia

DN09203161Issue:02


7.2.5.1.6 7.2.5.1.6.1


Configuring and verifying additional steps for IPA-RNC Configuring NPEG(P) towards OMU These steps need to be followed if Transport Plane monitoring is needed. If NPGE is used instead of NPGE(P), use the physical IP address. In the commands, use PHY or P instead of LOG or L. Purpose 1. In case each interface (IuPS,IuCS,Iub/Iur) has its own NPGE/NPGEP, then an IPoA must be created between each of these NPGE/NPGEPs with unique IP on each NPGEP/NPGEP. The interface must be the same Eg: IFAI10 for all. 2. In L3 Data collector, only the interface that has been configured for IPoA between NPGEs/NPGEPs and OMU must be added to the external interfaces dialog. Before you start Figure 39

Site solution deployment for IPA-RNC Emil/Megamon PC

RNC site OMS

RNC

O&M data

Site Router

DMCU0-n

OMU(WO)

ESA

Monitored control/data

ICSU0-n

NPGE(WO)

User traffic

DCN

L3 (aggregation)

DCN

RSMU

This does not require any additional cables to the NPGEs. However, from external monitoring tool machine, one ethernet cable is sufficient to connect to the DCN. It is sufficient to have one interface card on the monitoring machine In this case, the user needs to login/directly use the external monitoring tool machine to monitor the IPA-RNC. If a second interface card is available at the external monitoring tool machine, then that could be used for using the external monitoring tool remotely.

DN09203161Issue:02

©2016Nokia

277



IP interfaces between units in the IPA-RNC

Figure 40

External monitoring tool

IPA RNC

UP monitored data using DMX

OMU

DMPG

Centralized Monitoring Entity GIVAXI User inputs

User Plane monitoring agent

ELO: 10.58.239.114 TP Monitoring AAO: 10.10.10.6 LAN Write to UP, CP monitored data file

ESA switch

CP, Up monitoring data

UP, CP monitored data over IP

TP monitoring data TP monitored data using IPoA

10.58.239.142 NPGE Encrypt + write to TP monitored data file

CP Monitored data using DMX ICSU

Transport Plane monitoring agent

Control Plane monitoring agent

IFAI4: 10.10.10.5

Procedure

1

Configure TCP/IP ATM interface for internal use at the IFAI interface of the NPGE(P) towards ATM interface of the OMU. ZQMC:NPGEP,0,L:IFAI4:OMU,0,L:AA0:;

2

Configure IFAI interface at NPGE(P) with destination IP as that of the OMU. ZQRN:NPGEP,0:IFAI4,:10.10.10.5(IFAI4),L:24:10.10.10.6:;

For NPGE, use: ZQRN:NPGE,0:IFAI4,:10.10.10.5(IFAI4),P:24:10.10.10.6:;

3

Configure AA0 (ATM) network interface at OMU wit h destination IP as tha t of NPGE(P). ZQRN:OMU,0:AA0,N:10.10.10.6,L:24:10.10.10.5(IFAI4):;

4

Interrog ateto neO&M. twork status to check whether there is a lready an IP con figured from OMU ZQRS:OMU,0;

Check the output whether the foreign address is that of the O&M (indicated as BSO&M) with state as ESTABLISHED. The Local address is the OMU’s IP address in the output.

278

©2016Nokia

DN09203161Issue:02


7.2.5.1.6.2


Configuring static IP route to external monitoring tool Create a static route from NPGE(P) (with gateway IP being that of OMU’s AA0 interface) to the external monitoring tool. The destination IP address with netmask depends on the external monitoring tool machine’s IP address. Procedure

1

Create a static route from NPGE(P) via gateway AA0 interface to external monitoring tool. ZQKC:NPGEP,0: 10.58.239.0,24:10.10.10.6:LOG:;

2

Enable IP forwarding for both OMUs towards the external monitoring tool. ZQRT:OMU,0:IPF=YES; ZQRT:OMU,1:IPF=YES;

No configuration needed for transfer of UP and CP monitoring data as those involve DMX message based communication.

7.2.5.1.6.3

Configuring site routers If there are site routers between RNC and external monitoring tool, static routes to both NPGE and External Monitoring Tool side need to be configured on site routers. Commands to configure the site routers depend on the type of router: Cisco, Huawei, or Juniper. Without the static route configurations, site router will drop the packets with destination to NPGEP. Also, configure the routing table at the External Monitoring Tool workstation and provide the first hop site router’s IP address instead of the OMU’s IP address. Procedure

1

Cisco3750G(config)#ip route 1.1.1.0 255.255.255.0 2.2.2.1 Step example NPGE IFAI 1.1.1.1/24 ---- OMU EL 2.2.2.1/24 ----2.2.2.2/24 cisco 3.3.3.2/24 ------ 3.3.3.1/24 Emil

Packets with destination NPGE to be sent to 2.2.2.1 but no static route is needed with destination Emil 3.3.3.0/24 because they are in same subnet. Cisco3750G(config)#ip route 1.1.1.0 255.255.255.0 2.2.2.1

Step example NPGE IFAI 1.1.1.1/24 ---- OMU EL 2.2.2.1/24 ----2.2.2.2/24 cisco1 3.3.3.2/24 ------ 3.3.3.1/24 cisco2 4.4.4.1 --- 4.4.4.2 Emil

DN09203161Issue:02

©2016Nokia

279



Packets with destination as 1,1,1,0/24 to be sent to 2.2.2.1 Cisco1(config) towards NPGE #ip route 1.1.1.0 255.255.255.0 2.2.2.1

Packets towards 4.4.4.0/24 to be sent to 3.3.3.1 Cisco1(config) towards Emil: #ip route 4.4.4.0 255.255.255.0 3.3.3.1

Packets towards 1.1.1.0/24 to be sent to 3.3.3.2 Cisco2 towards NPGE ip route 1.1.1.0 255.255.255.0 3.3.3.2

Cisco2 towards Emil is not needed as they are in same subnet.

7.2.5.1.6.4

Configuring external monitoring tool (alternative to DHCP) Procedure

1

As an alternative to DHCP, assign an IP address to the external monitoring tool workstation.

2

For the external monitoring tool, configure the routing table so that al l packets sent to NPGE(P) (IFAIx) are sent via gateway EL0/EL1 interface on OMU or via site router. Step example route -p ADD 10.10.10.0 MASK 255.255.255.0 10.58.239.114

7.2.5.1.6.5

Verifying IP configuration Procedure

1

Ping from NPGE(P) to ex ternal mon itoring tool. ZQRX:NPGE,0:IP=10.58.239.142:PING;

2

Ping to NP GE(P) from external mon itoring tool. Ping 10.10.10.5

Result Ping is successfully received from either NPGE(P) or external monitoring tool. If not, execute tracert from either side to check where the packets are getting lost or are looping. Possibilities are that the site routers might not have been configured properly or static routes are not present.

280

©2016Nokia

DN09203161Issue:02



Pinging between NPGE and OMU must also work fine. If there are no site routers between external monitoring tool and OMU, pinging between them can be checked as well.

7.2.5.2 7.2.5.2.1

Activating RAN2973: Enhanced IMSI-based Monitoring on mcRNC Configuring IP connection at mcRNC Before you start If L3 Data Collector machine’s IP is in a different subnet than the one configured in mcRNC, then refer to section Configuring mcRNC to support Layer 3 routing towards Megamon. Otherwise, route configuration is not needed. This needs a 1GE cable from the SFP port (eg. SFP22) of each BCN to the switch. From L3 Data Collector machine, one Ethernet cable is sufficient to connect to the switch. It is sufficient to have one interface card on the L3 Data Collector machine. In this case, the user needs to login/directly use the L3 Data Collector machine to monitor the RNC. If a second interface card is available at the L3 Data Collector machine, then that could be used for using the L3 Data Collector remotely. IP switch is needed (at least 8 port on mcRNC side and one on the L3 Data Collector side). As an example, 24*1Gbit/s + 2*10Gbit/s. Figure 41

Site solution deployment for mcRNC

McRNC BCN #1

Monitoring Conditions

EITP-0

Monitored data

USPU-n

Control unit

USPU-0

Monitored unit

USUP-y USUP-0 SFP21/22 of two BCNs and Emil PC Should be in the same Vlan

USCP-x USCP-0

CFPU-0

Monitoring SFP port (SFP21/22) Switch

McRNC BCN #2

Emil PC

EITP-2 USPU-n USPU-1 USUP-z USUP-x

USCP-y USCP-x

CFPU-1

DN09203161Issue:02

Monitoring SFP port (SFP21/22)

©2016Nokia

281


g


Note: When this feature must be used alongside general monitoring, two 1GigE ports SFP21 and SFP22 per mcRNC module need to be setup to avoid message monitoring drops. For further details, see Megamon documentation. Procedure

1

Configure the port for the L3 Data Collector in every module. add troubleshooting megamon network 192.10.XX.0/24 port sfp21/22

Verify that the L3 Data Collector port configuration was successful.

2

Enable the L3 Data collector port. set troubleshooting centralized-monitoring administrate ifport ENABLE

3

Set message monitoring encryption preshared key for L3 Data Collector (Megamon) interface. set troubleshooting centralized-monitoring administrate ifpsk abcdef1234567890abcdef1234567890abcdef1234567890abcdef12345 67890

4

Set preshared key for opening the call-based monitoring message data (msgmon-psk). set troubleshooting centralized-monitoring administrate msg-mon-psk abcdef1234567890abcdef1234567890abcdef1234567890abcdef12345 67890

g

Note: Note that these two keys can have different values. This key must always be 64 ASCII characters in size.

5

Verify s tatus. show troubleshooting centralized-monitoring administration info

Step example Administration information: System ID PSK for EXT interface PSK for opening data Activation code for TP Port status Remote IP1

282

: : : : : :

393128 SET SET NOT SET ENABLED 192.10.10.2

©2016Nokia

modified 14/12/16 modified 14/12/05 modified 14/12/17

DN09203161Issue:02


Remote IP2 Remote IP3

7.2.5.2.2


: : -

Configuring Givaxi/givClient Procedure

1

Check that Givaxi is running correctly and is waiting for external tool to connect. netstat -taunp | grep giv

Step example # netstat -taunp | grep giv tcp 0 0 192.10.11.4:8021 LISTEN 7229/givclient

7.2.5.2.3

0.0.0.0:*

Installing licenses for mcRNC Procedure

1

To set the feature state to ON, use the following command: set license feature-mgmt id feature-adminstate on



Feature

g

Co de

0000005261

Objec Nta m e


SW Licence Key SI

RU00552


Software SI

RU00551.T


SW Licence Key SI

RU00551


Note: The feature code should be added to the command. In mcRNC, the code should form a 10-digit number, so it should be preceded with zeros.

DN09203161Issue:02

©2016Nokia

283


7.2.5.2.4



1

7.2.6 7.2.6.1


Verifying RAN2973: Enhanced IMSI-based Monitoring Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on IPA-RNC Purpose Refer to the Nokia IMSIMon3G IMSI Trace User Manualfor instructions.

7.2.6.2

Verifying RAN2973: Enhanced IMSI-based call monitoring on mcRNC Follow this procedure to verify that this feature has been activated successfully. Procedure

1

Connect to CFPU-0 through O&M network.

2

Show centralized-monitoring in troubleshooting. show troubleshooting centralized-monitoring administration info

Step result Administration information: System ID PSK for EXT interface PSK for opening data Activation code for TP Port status Remote IP1 Remote IP2 Remote IP3

: : : : : : : :

393128 SET SET NOT SET ENABLED 192.10.10.2 -


COMMAND OK.

3

Verify troubleshooting configuration for external monitoring tool connectivity from all nodes of the mcRNC to see if they are available. show troubleshooting megamon

284

©2016Nokia

DN09203161Issue:02



Step result Port group configuration: Port group --------------mmon-1

Physical port -------------------LMP-1-1-1:sfp22

Admin state ----------up

mmon-2 mmon-3 mmon-4

LMP-1-2-1:sfp22 LMP-1-3-1:sfp22 LMP-1-4-1:sfp22

up up up

Total count: 4

Ethernet Interface and IP Address configuration: Owner ---------/CFPU-0 /CFPU-1 /CSPU-0 /CSPU-1 /CSPU-2 /CSPU-3 /CSPU-4 /CSPU-5

Port group --------------mmon-1 mmon-2 mmon-1 mmon-2 mmon-1 mmon-2 mmon-3 mmon-4

Interface ------------mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext

Address -----------------192.10.10.9/24 192.10.10.10/24 192.10.10.11/24 192.10.10.18/24 192.10.10.14/24 192.10.10.21/24 192.10.10.25/24 192.10.10.33/24

/CSPU-6 /EIPU-0 /EIPU-1 /EIPU-2 /EIPU-3 /EIPU-4 /EIPU-5 /EIPU-6 /EIPU-7 /USPU-0 /USPU-1 /USPU-10 /USPU-11 /USPU-12 /USPU-13 /USPU-14 /USPU-2 /USPU-3 /USPU-4 /USPU-5 /USPU-6 /USPU-7 /USPU-8 /USPU-9

mmon-3 mmon-1 mmon-2 mmon-1 mmon-2 mmon-3 mmon-4 mmon-3 mmon-4 mmon-1 mmon-2 mmon-3 mmon-4 mmon-3 mmon-4 mmon-4 mmon-1 mmon-2 mmon-1 mmon-2 mmon-3 mmon-4 mmon-3 mmon-4

mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext

192.10.10.31/24 192.10.10.13/24 192.10.10.20/24 192.10.10.17/24 192.10.10.24/24 192.10.10.28/24 192.10.10.36/24 192.10.10.32/24 192.10.10.40/24 192.10.10.12/24 192.10.10.19/24 192.10.10.29/24 192.10.10.37/24 192.10.10.30/24 192.10.10.38/24 192.10.10.39/24 192.10.10.15/24 192.10.10.22/24 192.10.10.16/24 192.10.10.23/24 192.10.10.26/24 192.10.10.34/24 192.10.10.27/24 192.10.10.35/24

Total count: 32

DN09203161Issue:02

©2016Nokia

285



Ping each of those IP addresses above from the L3 Data collector machine and verify that they are responding.

7.2.6.3

Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on mcRNC Purpose Refer to the Nokia IMSIMon3G IMSI Trace User Manualfor instructions.

7.2.7 7.2.7.1

Deactivating RAN2973: Enhanced IMSI-based Monitoring Deactivating RAN2973: Enhanced IMSI-based call monitoring in IPARNC Follow this procedure to deactivate this feature. Procedure

1

Remove the RAN2973 configured network interface from the OMU towards the external monitoring tool. ZQRG:OMU,0:EL0:;

2

Remove the configured TCP/IP ATM internal interface of NPGE(P) towards OMU. (OPTIONAL) Step example ZQMD:INT:NPGE,0:IFAI4::OMU,0,AA0;

g

Note: This step is necessary only if TP monitoring has been configured and activated.

3

Remove IFAI interface at NPGE(P). Step example ZQRG:NPGEP,0:IFAI4,:10.10.10.5;

Or ZQRG:NPGE,0:IFAI4,:10.10.10.5;

4

Remove the static route from NPGE(P) to the external monitoring tool. For static route from NPGE(P) via AA0 to Emil use the following command: ZQKA:;

286

©2016Nokia

DN09203161Issue:02



Step example < ZQKB; LOADING PROGRAM VERSION 2.72-0 RNC

IPA2800

2014-07-25

17:18:22

INTERROGATED STATIC ROUTES ROUTE UNIT DESTINATION SESSION ID -------- -----------------------OMU-0 DEFAULT ROUTE NPGE-0 DEFAULT ROUTE NPGE-0 10.56.17.0/24

5

BFD GATEWAY ADDRESS

TYPE

PREF NBR

------------------ ----- ---- ------ ---10.56.17.1 10.56.8.97 10.10.10.6

LOG PHY PHY

0 0 0

1 2 6

-

Delete the pre-shared key using this command: ZQ4D:GIVAXIPSK; ZQ4D:MSGMONPSK;

g

Note: Deleting the PSK impacts also general monitoring.

6

Set the feature state to OFF. ZW7M:FEA=:OFF;

7.2.7.2

Deactivating RAN2973: Enhanced IMSI-based call monitoring in mcRNC Follow this procedure to deactivate this feature. Procedure

1

Delete configured ports. delete troubleshooting megamon

This deletes assigned IP address for each node of a BCN and also deletes the assigned SFP port and subnet for transferring monitoring data from the BCN

2

Set the feature state to OFF. set license feature-mgmt id feature-adminstate off

DN09203161Issue:02

©2016Nokia

287


7.2.8 7.2.8.1


Analyzing monitored data and troubleshooting Analyzing monitored data Checking the contents of the messages monitored using this feature requires the use of the IMSIMon3G which supports the RAN2973 feature. This must be ordered from NOLS. Procedure

1

Care → Software Supply Tool → Product Related Tools / Rad io Access Network Tools → L3 Data Collector (Megamon) or L3 Analyzer/Viewer (Emil) → Release: LDC TSS16 SW → Standard Update → Maintenance Packet . The L3 Data collector and L3 Analyzer tools’ support for the RAN2973 Enhanced IMSI-based Call monitoring feature is delivered in the TSS16 release (in NOLS, see release LDC TSS16 SW for Megamon and release LA TSS16 SW for Emil).

g 7.2.8.2

Note: The type of license key is an on/off license. A valid license needs to be requested from Contact Point, Message Analyser (NSN - FI).

Troubleshooting RAN2973: Enhanced IMSI-based Call Monitoring Purpose Follow these steps to collect necessary logs for Nokia to investigate monitoring data collection problems. Procedure

1

Enable Megamon interface logging. Select “action -> if logging -> set logging” in L3 Data Collector.

2

Start DMX message monitoring of SW proc esses responsible for monitoring. This can be done by using conventional L3 Data Collector or MML/SCLI commands. • •

288

For IPA-RNC, monitor OMU and ICSU units with filter “SR:OFAM=728” For mcRNC, monitor CFPU unit with filter “SR:OFAM=728,0B12” and USCP unit with filter “SR:OFAM=0A56”

©2016Nokia

DN09203161Issue:02



3

Reproduce th e p roblem.

4

Collect Megamon interface logging file and DMX message monitoring.

5

Collect RNC symptom report. • •

For IPA-RNC, use TN38 Rnclogcol.exe to collect symptom reportwith Basic profile. For mcRNC, execute the following SCLI command: save symptom-report name include group-RNC

6

In cases where IPA-RNC Transport Plane monitoring does not collect any data, the following logs should be additionally collected from NPGE(P) units. DMX message monitoring for Transport Plane monitoring agent from the NPGE(P). loadext dmxmon <=Loads dmxmon service terminal extension dmxmon –f a83 <=Starts DMX monitoring for family a83 (XAGENT)

Monitoring can be stopped by pressing . Before and after monitoring:jane kuostat. When IMSI-based call monitoring is ongoing and monitored call(s) are active: jane prtree mon_dst_addr jane jane jane jane jane jane jane jane clog

prtree prtree prtree prtree prtree prtree prtree prtree –sa

Table 127

mon_src_addr ipv4_fwd load_sharing ls_path l3l2 gtp_trace udp_trace_ing udp_trace_egr

RAN2973 symptoms and recovery actions

P ro bl e m (o b s er v e d i n L3 D at a C ol l e c t or )

After “Get Units” is done, No units are visible in Megamon or only some units are visible

Tr o u b l e s h o o t i n g s t e p

1. Check that Givaxi is running correctly and is waiting for external tool to connect.

2. Verify that the Pre-shared key is administered correctly.

3. In mcRNC: a) Check the port configuration for the L3 Data Collector in every module.

b) Ping from the L3 Data collector machine to IP address of each port configured for the L3 Data Collector in every module. Verify reply is available for all.

DN09203161Issue:02

©2016Nokia

289


Table 127


RAN2973 symptoms and recovery actions (Cont.)

P ro bl e m (o b se r v e d i n L 3 D at a C ol l e c t or )

Tr o u b l e s h o o t i n g s t e p

c) If not, checking if cable has been connected to every module of the mcRNC.

No Transport Plane monitoring data available (IPA-RNC)

1. Check IPoA configuration and ping

After “Set Filter”, “Start” button does not get enabled which means that

Set the monitoring conditions correctly.

In L3 Data collector event window, file_open_error_ec (0x0000386E) is encountered

Create the msg-mon-psk (for encryption)

If INVALID_IMSI_EC is returned

Check and make sure IMSI length is not more than 15 characters

If Transport Plane monitoring fails with the error: Setup failed: Could not set monitoring filters for unit NPGE-0 (TransportPlaneMonitoring). Error: illegal_value_of_param_ec (0x00003829)

Check whether the IPoA connections are setup between the Transport Plane units, the OMU and the Emil/Megamon.

Control Plane monitoring data from the beginning of the call is not available

If holding time has been increased (to handle network delays) and buffer size is not correspondingly increased then Buffer size needs to be increased in this case as per the guidance specified in the user manuals of the L3 Data collector.

Setting up monitoring for one of the selected units fails

The reason for the failure must be corrected or the unit must be omitted from the list of monitored units for the monitoring to be started.

in L3 Data collector, in the “setup -> Output files”, the “Operating mode -> IMSI monitoring” option does not appear

It means that the RAN2973 specific license is not available. Previously working Megamon license for the PC cannot be used for RAN2973 operations.

between NPGE/NPGE(P) and the External machine 2. Check site router configuration

NPGE/NPGE(P) IP addresses are not available IPoA configuration is not correct after the “Get Units” operation in the L3 Data collector IPA-RNC: Start monitoring fails with error: “No connection could be made because the target machine actively refused it” or “Could not establish TCP connection”

7.2.9

Check Givaxi port status. If Port 8021 is not in LISTEN status, then execute ZWOC:2,2093,002; And wait until port 8021 status shows LISTEN. It takes approximately 20 seconds

Configuring mcRNC to support Layer 3 routing towards Megamon Follow this procedure to configure mcRNC to support L3 routing towards Megamon. Purpose In this case, the mcRNC units are on the 10.13.159.0/24 subnet while the megamon server and the NetAct GW are on a separate 10.10.1.0/24 subnet. The NetAct GW in the

290

©2016Nokia

DN09203161Issue:02



figure is a sample configuration only. Separate mcRNC Subnets can be configured this way as well: 1. O&M connectivity -> OMS -> NetAct 2. Traffic subnet 3. Monitoring subnet -> Megamon For the sample scenario in figure, the following steps are to be executed to setup a path from the monitored mcRNC units to the Megamon server machine. Before you start 1. The megamon network and the SFP ports for the BCNs must have been setup already using the add troubleshooting megamon network and add networking switch port-group name. 2. Megamon interface must have been configured for both active and standby CFPUs using the add networking ether /CFPU-0 port mmon- iface mmonext SCLI. 3. The AGGSWs (L3 switches) in the above picture must have been configured (out of scope of this document) such that they can communicate with the Megamon server successfully and vice-versa. Procedure

1

Configure the physical interface at each USPU in the mcRNC modules for Megamon. add networking ether /USPU-1 port mmon-2 iface mmonext

g

Note: For , the SCLI command offers eithermmon-1 or mmon-2 depending on which of those were configured for the mcRNC module in which the unit resides.

2

Assign an IP a ddress to the unit. Step example add networking address dedicated /USPU-1 iface mmonext ip-address 10.13.159.19/24 role megamon

3

Create a static route from the unit to the Megamon server via the Layer 3 switch. Step example set routing node USPU-1 static-route 10.10.1.213/32 nexthop gateway address 10.13.159.1 on

DN09203161Issue:02

©2016Nokia

291


4


Set the route such that packets from <10.13.159.19> are forwarded to the gateway without checking the subnet. Step example set routing node USPU-1 static-route 10.10.1.213/32 source 10.13.159.19

g

Note: This will not impact the user traffic meant for Iub,IuPs, or IuCS interfaces.

5

Verfiy t he p rocedure. show routing node USPU-1 static-route config all Instance: default Static route: 10.10.1.213/32 Next hop type: normal Rank: not defined MTU: not defined Source: 10.13.159.19 Gateway: 10.13.159.1 Preference: 1

6

Show troubleshooting megamon. Port group configuration: Port group --------------mmon-1 mmon-2

Physical port -------------------LMP-1-1-1:sfp21 LMP-1-2-1:sfp21

Admin state ----------up up

Ethernet Interface and IP Address configuration: Owner Port group Interface Address ---------- --------------- ------------- -----------------…. /USPU-1 mmon-2 mmonext 10.13.159.19/24 ….

7

If super user rights are available, connect to the USPU-1 via ssh, check the routing table and verify that the USPU-1 is able to ping the Megamon IP address successfully. # ssh USPU-1 # route -n Kernel IP routing table Destination Gateway Use Iface 10.10.1.213 10.13.159.1 0 mmonext

292

©2016Nokia

Genmask

Flags Metric Ref

255.255.255.255 UGH

0

0

DN09203161Issue:02


… 10.13.159.0 0.0.0.0 0 mmonext … # ping 10.10.1.213 Static route: 10.10.1.213/32 Next hop type: normal


255.255.255.0

U

0

0

Rank: not MTU: not defined defined Source: 10.13.159.19 Gateway: 10.13.159.1 Preference: 1

8

Verify also from the megamon side that it is able to ping the USPU-1.

9

Megamon shall now be able to set the monitoring filters on the USPU-1 and start monitoring it.

10 Repeat the above steps for all USPUs to be monitored.

7.2.10

RAN2930: IMSI-based Call Monitoring Introduction to the feature Troubleshooting solutions available before RU50 EP1 have had the following drawbacks: 1. Provide too little information on Control Plane messaging (Subscriber trace functionality based on 3GPP TS 32.421) which is not sufficient for troubleshooting majority of problems. 2. Require capturing of Control Plane messaging for all calls in RNC in order to extract monitoring for needed calls (RAN L3 Data Collector and Analyzer) which generate heavy amount of data (several TBytes per day) and require high performance dedicated HW to store and process the data. 3. Wherein the root cause of the problem lies outside Control Plane, for example in Transport or User Plane, additional troubleshooting methods and tools are engaged, such as monitoring data for all calls in units handling user plane and RAN interfaces tracing with Wireshark. Those limitations result in heavy effort needed currently in capturing, extracting and analyzing individual calls. The RAN2930: IMSI- based Call Monitoring feature allows the operator to start the UE monitoring from L3 Data collector by specifying the calls (via their IMSIs) and planes to be monitored (For IPA-RNC, among Control, User and Transport Planes; for mcRNC, only Control Plane can be monitored). Monitored data can then be loaded into L3 Data analyzer for analysis. Monitored data is adequate and small enough to provide inputs on possible error causes.

7.2.10.1


DN09203161Issue:02

©2016Nokia

293



Faster resolution of subscribers' complaints. Operator benefits Remote and fast network troubleshooting, verification and optimization of call related issues in Control and User Planes. Reduced need for external tracing equipment, such as Wireshark and NetHawk. Standard Windows PC hardware can support simultaneous monitoring in multiple RNCs.

7.2.10.2

RAN2930 Functional description Functional overview Figure 42

Overview of RAN2930: IMSI-based Call Monitoring GEO interface Extension option

L3DC

PS/CS Core IPA RNC/ mcRNC Control Plane + User Plane + Transport Plane:messages, logs, packetheaders

RNC

In IPA-RNC, this feature introduces collection of Control, User, and Transport planes monitoring data for individual calls based on given IMSI numbers.

294

©2016Nokia

DN09203161Issue:02



In mcRNC, this feature introduces collection of Control planes monitoring data for individual calls based on given IMSI numbers. The data capturing is done with the help of the L3 Data Collector running on a standard Windows PC, and connected remotely to the monitored RNC. The data processing and analysis is done with the L3 Data Analyzer running on the same or on a different machine from the L3 Data Collector. The L3 Data Analyzer has the capability of analyzing Control, User and Transport Plane monitored data. The main comprehensive benefit of this feature is that it allows a small size of the monitored data while providing monitored data content for individual monitored calls. Note that neither end-user communication content, that is end-user speech and data, nor messages related to any other call(s) (uninterested calls) is collected by this feature. Data that could reveal customer identity such as the IMSI, the end user or the remote server IP addresses is encrypted at the RNC using a configurable encryption key. The same key is required for analyzing the monitored data at the L3 Data Analyzer tool. Monitored data content 1. Control Plane in control plane processing units (ICSU in RNC2600 and USCP in mcRNC): •

DMX messages from most of call handling program families

2. User Plane in user plane processing units (DMPG/DSP in RNC2600, not supported in mcRNC in this release): •

Protocol headers on Iu-PS: The whole end-to-end IPv4 protocol header is monitored except for source and destination IP addresses. From the source and destination IP addresses, only the last octet of the four is captured. The other bits of the IP addresses are marked as zeroes in the monitoring data. The whole end-to-end TCP/UDP/ICMP header is monitored. Nothing is captured from the IPv4 packet payload. Figure 43

DN09203161Issue:02

User Plane monitored data on Iu-PS interface

©2016Nokia

295


Figure 44

•

End-to end IPv4 packet TCP/UDP/ICMP

Protocol headers on Iu-CS: RTP, RTCP (not in RNC2600) and Iu-CS UP Figure 45

g g


User Plane monitored data on Iu-CS interface

Note: Only with CS Voice over HSPA. Note: RTCP monitored only in mcRNC. •

Protocol headers onIub: FP, MAC, RLC and PDCP Figure 46

• •

User Plane monitored data on Iub interface for PS and CS calls

Internal messages related to L3-L2 interfaces L2 internal protocol interfaces(such as RLC-MAC), internal data(such as scheduling info), minor and severe errors, exceptions

3. Transport Plane in transport plane processing units (NPGE in RNC2600, supported only via a separate L3 Data Collector session in mcRNC in this release): •

Protocol headers on Iu-PS: outer IP , UDP, GTP-U, inner IP, inner TCP/ICMP/UDP Figure 47

296

Transport Plane monitored data on Iu-PS interface

©2016Nokia

DN09203161Issue:02


•

•

Iu-CS: IP/UDP/RTP/IuUP headers, IP/UDP/RTCP full packet Figure 48


Figure 49


Iub: IP/UDP/FP headersand MAC/RLC headers of the first PDU Figure 50

g


Transport Plane monitored data on Iub interface

Note: Tail only for DCH transport

Site configuration • •

In RNC2600, the monitored data collection is performedvia O&M connection to RNC. In mcRNC, it is required to install Ethernet switch onsite as the monitored data collection is done via one SFP port in each BCN box. Existing Megamon/L3Analyzer installed solution can be re-used.

Overload control The feature employs overload control such that if one of the monitored computer units gets overloaded, the monitoring is paused on that unit, till the overload situation is rectified. This way the feature does not endanger normal functioning of the unit even while under overload. These overload related parameters are fixed in the L3 Data collector: • • • •

Maximum threshold: percentagevalue of the computer unit load beyond which the CPU is deemed to be overloaded Minimum threshold: percentagevalue of the computer unit load below which the CPU is deemed to be rectified of overload Checkpoint(A): Frequency of checking the computer load Sequential count(B): –

DN09203161Issue:02

For overload controlactions to be applied: the number of continuous samples of CPU load during which the percentage value of the CPU load is above the maximum threshold

©2016Nokia

297


–


For overload controlactions to be stopped: the number of continuous samples of CPU load during which the percentage value of the CPU load is below the minimum threshold

Table 128

Overload control

P l an e

7.2.10.3

Th r esh o l d

Ch eckpoint

S e q u e n t i a lc o u n t

Control Plane(IPARNC/ mcRNC)

85 (max)/ 75 (min)

100/ 100

5/ 10

User Plane, Transport Plane (IPA-RNC)

60 (max)/ 55 (min)

100/ 100

5/ 10

RAN2930 System impact Interdependencies between features 1. Operations causing high OMU load, for example RAN2446 / TN38 Rnclogcol log collection or file compress/uncompress operations, can cause pausing of RAN2930 monitorings 2. General Control Plane monitoring using L3 Data collector can be used in parallel with this feature in a different L3 Data collector session 3. General Control Plane/User Plane monitoring using MML/SCLI can be performed in parallel with this feature Impact on network and network element management tools No impact. CPU loads of the monitored units can increase up to 10% (relative). There is no additional CPU load increase in Control Plane units in case RAN2930 feature is activated additionally to general L3 Data Collector (Megamon) message monitoring. Impact on system performance and capacity No impacts to KPIs. CPU loads on monitored units will increase to maximum 5%.

7.2.10.4


Software requirements

RAS

Flexi Direct IPA-RNC

RU50 EP1

Not planned RN8.1

mcRNC

mcRNC4.1

Flexi Direct OMS RNC

Not planned Support not required

Flexi BTS


298

©2016Nokia

DN09203161Issue:02


Table 130


External monitoring tool requirements

To on l ame

P ur p ose

Lo c ati o n

L3 Data collector

For collecting the monitored data

From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Data Collector (Megamon) → Release: LDC TSS15A → Standard Update → Maintenance Packet .

L3 Data

For decoding

From NOLS: Care → Software Supply Tool → Product Related

Analyzer

the monitored data

Tools / Radio Access Network Tools → L3 Analyzer/Viewer (Emil) → Release: LDC TSS15A → Standard Update → Maintenance Packet .

Flexi Lite Flexi 10 BTS BTS


NetAct


MSC

SGSN

MGW

Support not Support not Support not Support not required required required required

UE


For IPA-RNC: 1. An Ethernet cable from the L3 Data Collector tool to the OMU via O&M connection is needed. 2. No separate Ethernet cabling needed towards the NPGE/NPGE(P) For mcRNC: 1. An external IP switch is needed 2. 1GE cable from the SFP22 port of each module to the switch 3. One Ethernet cable to connect the switch to the L3 Data Collector machine Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information

DN09203161Issue:02

©2016Nokia

299


Table 131


Sales information

BSW/ASW

SW component


ASW

RAN

RNC LK

The following additional sales items need to be purchased as well: 1. L3DC SW + RAN2930 L3DC license to collect Control, User and Transport Plane monitored data 2. L3DA SW + RAN2930 L3DA license to analyze collected Control, User and Transport Plane monitored data

7.2.10.5 7.2.10.5.1 7.2.10.5.1.1

Activating and configuring RAN2930: IMSI-based Monitoring Activating RAN2930: IMSI-based Monitoring on IPA-RNC Configuring GIVAXI/givClient Purpose Givaxi is an application in IPA-RNC that implements L3 Data collector interface for control and data protocols Procedure

1

Check Givaxi port status. ZQRS:OMU,0;

Step result The output must include: The output must include: UNIT: OMU-0 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address State tcp 0 0 *.8021 LISTEN

Foreign Address *.*

If not displayed correctly, execute the following command: ZWOC:2,2093,002;

Wait until port 8021 status shows LISTEN. It takes approximately 20 seconds.

Related descriptions Configuring GIVAXI/givClienton page 300 Backup Physical RNC System managementon page 360

300

©2016Nokia

DN09203161Issue:02



Related procedures Configuring GIVAXI/givClienton page 300 Deleting BPS fallback on page 447 Activating new BPS on BkPRNC (mcRNC) on page 442 Upgrading mcRNC SW builds and BPS on BkPRNCon page 439 Creating BPS fallbackon page 438 7.2.10.5.1.2

Installing licenses for IPA-RNC Procedure

1

To set the feature state to ON, use the following command: ZW7M:FEA=:ON;



Co de

Feature

g 7.2.10.5.1.3

0000005261

Objec Nta m e


SW Licence Key SI

RU00552


Software SI

RU00551.T


SW Licence Key SI

RU00551


Note: The feature code should be added to the command.


1

7.2.10.5.1.4


Authorizing Pre-Shared Key (PSK) It is required that PSK authentication is successfully completed before the solution works. This requires that the same PSK is administered in both the external monitoring tool and IPA-RNC.

DN09203161Issue:02

©2016Nokia

301



Procedure

1

Set message monitoring encryption preshared key for L3 Data Collector (Megamon) interface. The (AES256 crypted) shared key (256bit) must be set by Q4-mml. 256bits/8=32 bytes so the key must be 32 bytes long. ZQ4A:GIVAXIPSK,S:K:H:;

Step example >ZQ4A:GIVAXIPSK,S:K:H:; ENTER KEY(MAX 64 HEXADECIMAL DIGITS): 1234567890ABCDEFFEDCBA09876543211234567890ABCDEFFEDCBA0987654321

7.2.10.5.1.5

Configuring MSGMONPSK for data encryption Procedure

1

For data encryption key authentication, use the following command: ZQ4A:MSGMONPSK,S:K:H;

Step example ENTER KEY(MAX 64 HEXADECIMAL DIGITS): 1234567890123456789012345678901234567890123456789012345678901234

This key is then required to be provided at the L3 Data Analyzer tool while opening the monitored Control Plane data. This is unrelated to the GIVAXIPSK that was set in the previous step.

g 7.2.10.5.1.6 7.2.10.5.1.6.1

Note: This key must always be 64 ASCII characters in size.

Configuring and verifying additional steps for IPA-RNC Configuring NPEG(P) towards OMU These steps need to be followed if Transport Plane monitoring is needed. If NPGE is used instead of NPGE(P), use the physical IP address. In the commands, use PHY or P instead of LOG or L. Purpose 1. In case each interface (IuPS,IuCS,Iub/Iur) has its own NPGE/NPGEP, then an IPoA must be created between each of these NPGE/NPGEPs with unique IP on each NPGEP/NPGEP. The interface must be the same Eg: IFAI10 for all. 2. In L3 Data collector, only the interface that has been configured for IPoA between NPGEs/NPGEPs and OMU must be added to the external interfaces dialog.

302

©2016Nokia

DN09203161Issue:02



Before you start Figure 51

Site solution deployment for IPA-RNC Emil/Megamon PC

RNC site

O&M data

OMS

RNC

Site Router

DMCU0-n

OMU(WO)

ESA

Monitored control/data

ICSU0-n

NPGE(WO)

User traffic

DCN

L3 (aggregation)

DCN

RSMU

This does not require any additional cables to the NPGEs. However, from external monitoring tool machine, one ethernet cable is sufficient to connect to the DCN. It is sufficient to have one interface card on the monitoring machine In this case, the user needs to login/directly use the external monitoring tool machine to monitor the IPA-RNC. If a second interface card is available at the external monitoring tool machine, then that could be used for using the external monitoring tool remotely. Figure 52

IP interfaces between units in the IPA-RNC External monitoring tool

IPA RNC

UP monitored data using DMX

OMU

DMPG

Centralized Monitoring Entity G IVAXI User inputs

User Plane monitoring agent

ELO: 10.58.239.114 TP Monitoring AAO: 10.10.10.6 LAN Write to UP, CP monitored data file

ESA switch

CP, Up monitoring data

UP, CP monitored data over IP

TP monitoring data TP monitored data using IPoA

10.58.239.142 NPGE Encrypt + write to TP monitored data file

CP Monitored data using DMX ICSU

Transport Plane monitoring agent

Control Plane monitoring agent

IFAI4: 10.10.10.5

Procedure

1

Configure TCP/IP ATM interface for internal use at the IFAI interface of the NPGE(P) towards ATM interface of the OMU. ZQMC:NPGEP,0,L:IFAI4:OMU,0,L:AA0:;

DN09203161Issue:02

©2016Nokia

303


2


Configure IFAI interface at NPGE(P) with destination IP as that of the OMU. ZQRN:NPGEP,0:IFAI4,:10.10.10.5(IFAI4),L:24:10.10.10.6:;

For NPGE, use: ZQRN:NPGE,0:IFAI4,:10.10.10.5(IFAI4),P:24:10.10.10.6:;

3

Configure AA0 (ATM) network interface at OMU wit h destination IP as tha t of NPGE(P). ZQRN:OMU,0:AA0,N:10.10.10.6,L:24:10.10.10.5(IFAI4):;

4

Interrogate network status to check whether there is a lready an IP con figured from OMU to O&M. ZQRS:OMU,0;

Check the output whether the foreign address is that of the O&M (indicated as BSO&M) with state as ESTABLISHED. The Local address is the OMU’s IP address in the output.

7.2.10.5.1.6.2

Configuring static IP route to external monitoring tool Create a static route from NPGE(P) (with gateway IP being that of OMU’s AA0 interface) to the external monitoring tool. The destination IP address with netmask depends on the external monitoring tool machine’s IP address. Procedure

1

Create a static route from NPGE(P) via gateway AA0 interface to external monitoring tool. ZQKC:NPGEP,0: 10.58.239.0,24:10.10.10.6:LOG:;

2

Enable IP forwarding for both OMUs towards the external monitoring tool. ZQRT:OMU,0:IPF=YES; ZQRT:OMU,1:IPF=YES;

No configuration needed for transfer of UP and CP monitoring data as those involve DMX message based communication.

7.2.10.5.1.6.3

Configuring site routers If there are site routers between RNC and external monitoring tool, static routes to both NPGE and External Monitoring Tool side need to be configured on site routers. Commands to configure the site routers depend on the type of router: Cisco, Huawei, or Juniper. Without the static route configurations, site router will drop the packets with destination to NPGEP. Also, configure the routing table at the External Monitoring Tool workstation and provide the first hop site router’s IP address instead of the OMU’s IP address.

304

©2016Nokia

DN09203161Issue:02



Procedure

1

Cisco3750G(config)#ip route 1.1.1.0 255.255.255.0 2.2.2.1 Step example NPGE IFAI 1.1.1.1/24 ---- OMU EL 2.2.2.1/24 ----2.2.2.2/24 cisco 3.3.3.2/24 ------ 3.3.3.1/24 Emil

Packets with destination NPGE to be sent to 2.2.2.1 but no static route is needed with destination Emil 3.3.3.0/24 because they are in same subnet. Cisco3750G(config)#ip route 1.1.1.0 255.255.255.0 2.2.2.1

Step example NPGE IFAI 1.1.1.1/24 ---- OMU EL 2.2.2.1/24 ----2.2.2.2/24 cisco1 3.3.3.2/24 ------ 3.3.3.1/24 cisco2 4.4.4.1 --- 4.4.4.2 Emil

Packets with destination as 1,1,1,0/24 to be sent to 2.2.2.1 Cisco1(config) towards NPGE #ip route 1.1.1.0 255.255.255.0 2.2.2.1

Packets towards 4.4.4.0/24 to be sent to 3.3.3.1 Cisco1(config) towards Emil: #ip route 4.4.4.0 255.255.255.0 3.3.3.1

Packets towards 1.1.1.0/24 to be sent to 3.3.3.2 Cisco2 towards NPGE ip route 1.1.1.0 255.255.255.0 3.3.3.2

Cisco2 towards Emil is not needed as they are in same subnet.

7.2.10.5.1.6.4

Configuring external monitoring tool (alternative to DHCP) Procedure

1

As an alternative to DHCP, assign an IP address to the external monitoring tool workstation.

2

For the external monitoring tool, configure the routing table so that al l packets sent to NPGE(P) (IFAIx) are sent via gateway EL0/EL1 interface on OMU or via site router. Step example route -p ADD 10.10.10.0 MASK 255.255.255.0 10.58.239.114

DN09203161Issue:02

©2016Nokia

305


7.2.10.5.1.6.5


Verifying IP configuration Procedure

1

Ping from NPGE(P) to ex ternal mon itoring tool. ZQRX:NPGE,0:IP=10.58.239.142:PING;

2

Ping to NP GE(P) from external mon itoring tool. Ping 10.10.10.5

Result Ping is successfully received from either NPGE(P) or external monitoring tool. If not, execute tracert from either side to check where the packets are getting lost or are looping. Possibilities are that the site routers might not have been configured properly or static routes are not present. Pinging between NPGE and OMU must also work fine. If there are no site routers between external monitoring tool and OMU, pinging between them can be checked as well.

7.2.10.5.2 7.2.10.5.2.1

Activating RAN2930: IMSI-based Monitoring on mcRNC Configuring IP connection at mcRNC Before you start If L3 Data Collector machine’s IP is in a different subnet than the one configured in mcRNC, then route configuration is needed in the switch. Otherwise, route configuration is not needed. This needs a 1GE cable from the SFP port (eg. SFP22) of each BCN to the switch. From L3 Data Collector machine, one Ethernet cable is sufficient to connect to the switch. It is sufficient to have one interface card on the L3 Data Collector machine. In this case, the user needs to login/directly use the L3 Data Collector machine to monitor the RNC. If a second interface card is available at the L3 Data Collector machine, then that could be used for using the L3 Data Collector remotely. IP switch is needed (at least 8 port on mcRNC side and one on the L3 Data Collector side). As an example, 24*1Gbit/s + 2*10Gbit/s.

306

©2016Nokia

DN09203161Issue:02


Figure 53


Site solution deployment for mcRNC

mcRNC BCN #1 USPU-4 USPU-2 USPU-0 CSPU-2 CSPU-0 EIPU-0 EIPU-2 CFPU-0

Monitoring SFP port (SFP20)

mcRNC BCN #2

SFP20 of two BCNs and Emil PC Should be in the same Vlan

Emil PC

Switch

USPU-5 USPU-3 USPU-1 CSPU-3 CSPU-1 EIPU-1 EIPU-3 CFPU-1

g

Monitoring SFP port (SFP20)

Note: When this feature must be used alongside general monitoring, two 1GigE ports SFP21 and SFP22 per mcRNC module need to be setup to avoid message monitoring drops. For further details, see Megamon documentation. Procedure

1

Configure the port for the L3 Data Collector in every module. add troubleshooting megamon network 192.10.XX.0/24 port sfp21/22

Verify that the L3 Data Collector port configuration was successful.

DN09203161Issue:02

©2016Nokia

307


2


Enable the L3 Data collector port. set troubleshooting centralized-monitoring administrate ifport ENABLE

3

Set the Pre-Shared Key (PSK) To enable monitoring. set troubleshooting centralized-monitoring administrate ifpsk abcdef1234567890abcdef1234567890abcdef1234567890abcdef12345 67890

4

Set preshared key for opening the call-based monitoring message data (msgmon-psk). set troubleshooting centralized-monitoring administrate msg-mon-psk abcdef1234567890abcdef1234567890abcdef1234567890abcdef12345 67890

g

Note: Note that these two keys can have different values. This key must always be 64 ASCII characters in size.

5

Verify s tatus. show info troubleshooting centralized-monitoring administration

Step example Administration information: System ID PSK for EXT interface PSK for opening data Activation code for TP Port status Remote IP1 Remote IP2 Remote IP3

7.2.10.5.2.2

: : : : : : : :

393128 SET SET NOT SET ENABLED 192.10.10.2 -


Configuring Givaxi/givClient Procedure

1

Check that Givaxi is running correctly and is waiting for external tool to connect. netstat -taunp | grep giv

308

©2016Nokia

DN09203161Issue:02



Step example # netstat -taunp | grep giv tcp 0 0 192.10.11.4:8021 LISTEN 7229/givclient

7.2.10.5.2.3

0.0.0.0:*

Installing licenses for mcRNC Procedure

1

To set the feature state to ON, use the following command: set license feature-mgmt id feature-adminstate on



Co de

Feature

g

0000005261

Objec Nta m e


SW Licence Key SI

RU00552


Software SI

RU00551.T


SW Licence Key SI

RU00551


Note: The feature code should be added to the command. In mcRNC, the code should form a 10-digit number, so it should be preceded with zeros.

7.2.10.5.2.4


1


7.2.10.6 7.2.10.6.1

Verifying RAN2930: IMSI-based Monitoring Verifying RAN2930: IMSI-based Monitoring from L3 Data Collector on IPARNC Follow this procedure to start IMSI-based call monitoring from L3 Data Collector.

DN09203161Issue:02

©2016Nokia

309



Procedure

1

After launching the L3 Data collector, go to “Setup” menu and open the “License” menu item. Provide the path of the license file and click OK.

2

Go to “Setup-> Connections” menu tab. Enter the OMU IP. Control and data ports as 8021 and 8020 respectively and the Pre-Shared Key administered at the RNC.

3

In the Setup -> Output files, set the output directory as needed and set the “Operating mode” to “IMSI monitoring”.

4

Verify that “Setup -> Default Filter Condition” menu brings up the “L3 Data collector message filters” box that has the following: Control Plane monitoring filter for RAN2930: SR:(OFAM=4FD,509,508,0A49,9F6,997,507,4B7)

•

Go to “Setup -> IMSI conditions”. Create a new “IMSI Set name”, add the IMSIs to be monitored, retain the holding time of 5 and save it. To enable Transport Plane monitoring, goto “Set up -> Interfaces” The IFAI interface at the NPGE that has been configured for monitoring must be specified here for Transport Plane monitoring to work. Eg. IFAI4 in the aforementioned example.

•

5

In the main window of the L3 Data Collector, Click on “Get Units”. The monitorable units get populated in the units window.

g

Note: Do not select anything for the OMU rows. a) b) c) d)

Navigate to the ICSU row, select the Control Plane monitoring filter for RAN2930. In the “Via” column, select “CntrlUnit” In the IMSI(CP) column, select the IMSI filter. Right click on the row and set the filters to all ICSU units.

If User Plane monitoring is needed, navigate to the row with DMPG, apply the “CntrlUnit” to the “Via” column. a) For the “UP(Dch)” column, select the User Plane monitoring filter which has this as filter condition:–k2 IUUP_CTRL_OUT -k3 PDCP_BUF_LOAD -k4 -k1the IUUP_CTRL_IN RLC_CONTROL –k5 MAC_SCHEDULER -k6 FP_CTRL_IN –k7 FP_CTRL_OUT –k8 L2L2_MSG_IN –k9 L2L2_MSG_OUT –k10 ERROR_ALL –m1 0x520F –m2 0x5211 b) Right click on the row and set the filters to all DMPG units. If Transport Plane monitoring is needed, navigate to the row with NPGE/NPGEP.

310

©2016Nokia

DN09203161Issue:02



a) For the “IMSI(TP)” column, set the IMSI filter. b) Right click and apply the filter to all WO-Ex NPGE/NPGEP units. Click on “Set Filters” button and verify that the “Status” column for all selected units shows OK in blue. Select from available options •

Otherwise, check the L3 Data Collector log windowfor the error message.

Once the filters are applied successfully, the “Start” button is enabled. a) Click on it to begin monitoring. b) If calls matching the IMSIs in the IMSI filter are running or are setup, the Incoming Kbits/s starts showing the monitoring throughput.

6

Stop the monitoring. Monitored data from each plane and unit is saved into its own file.

7

7.2.10.6.2

Collected Control Plane, Transport Plane, and User P lane files can be loaded to the L3 Data analyzer for decoding.

Verifying RAN2930: IMSI-based call monitoring on mcRNC Follow this procedure to verify that this feature has been activated successfully. Procedure

1

Connect to CFPU-0 through O&M network.

2

Show centralized-monitoring in troubleshooting. show troubleshooting centralized-monitoring administration info

Step result Administration information:

DN09203161Issue:02

System ID

: 393128

PSK interface PSK for for EXT opening data Activation code for TP Port status Remote IP1 Remote IP2 Remote IP3

: : : : : : :

©2016Nokia

SET SET NOT SET ENABLED 192.10.10.2 -

modified modified 14/12/16 14/12/05 modified 14/12/17

311



COMMAND OK.

3

Verify troubleshooting configuration for external monitoring tool connectivity from all nodes of the mcRNC is available. show troubleshooting megamon

Step result Port group configuration: Port group --------------mmon-1 mmon-2 mmon-3 mmon-4

Physical port -------------------LMP-1-1-1:sfp22 LMP-1-2-1:sfp22 LMP-1-3-1:sfp22 LMP-1-4-1:sfp22

Admin state ----------up up up up

Total count: 4

Ethernet Interface and IP Address configuration:

312

Owner ---------/CFPU-0 /CFPU-1 /CSPU-0 /CSPU-1 /CSPU-2 /CSPU-3 /CSPU-4 /CSPU-5 /CSPU-6 /EIPU-0 /EIPU-1 /EIPU-2 /EIPU-3 /EIPU-4 /EIPU-5 /EIPU-6 /EIPU-7 /USPU-0

Port group --------------mmon-1 mmon-2 mmon-1 mmon-2 mmon-1 mmon-2 mmon-3 mmon-4 mmon-3 mmon-1 mmon-2 mmon-1 mmon-2 mmon-3 mmon-4 mmon-3 mmon-4 mmon-1

Interface ------------mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext

Address -----------------192.10.10.9/24 192.10.10.10/24 192.10.10.11/24 192.10.10.18/24 192.10.10.14/24 192.10.10.21/24 192.10.10.25/24 192.10.10.33/24 192.10.10.31/24 192.10.10.13/24 192.10.10.20/24 192.10.10.17/24 192.10.10.24/24 192.10.10.28/24 192.10.10.36/24 192.10.10.32/24 192.10.10.40/24 192.10.10.12/24

/USPU-1 /USPU-10 /USPU-11 /USPU-12 /USPU-13 /USPU-14 /USPU-2 /USPU-3

mmon-2 mmon-3 mmon-4 mmon-3 mmon-4 mmon-4 mmon-1 mmon-2

mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext

192.10.10.19/24 192.10.10.29/24 192.10.10.37/24 192.10.10.30/24 192.10.10.38/24 192.10.10.39/24 192.10.10.15/24 192.10.10.22/24

©2016Nokia

DN09203161Issue:02


/USPU-4 /USPU-5 /USPU-6 /USPU-7 /USPU-8 /USPU-9

mmon-1 mmon-2 mmon-3 mmon-4 mmon-3 mmon-4


mmonext mmonext mmonext mmonext mmonext mmonext

192.10.10.16/24 192.10.10.23/24 192.10.10.26/24 192.10.10.34/24 192.10.10.27/24 192.10.10.35/24

Total count: 32

7.2.10.6.3

Verifying RAN2930: IMSI-based Monitoring from L3 Data Collector on mcRNC Follow this procedure to start IMSI-based call monitoring from L3 Data Collector. Procedure

1

After launching the L3 Data collector, go to “Setup” menu and open the “License” menu item. Provide the path of the license file and click OK.

2

Go to “Setup-> Connections” menu tab. Set the mcRNC IP address. This must be the IP address configured to working CFPU. Control and data ports as 8021 and 8020 respectively and the Pre-Shared Key administered at the RNC.

3

In the Setup -> Output files, set the output directory as needed and set the “Operating mode” to “IMSI monitoring”.

4

Verify that “Setup -> Filter Condition” menu brings up the “Filter conditions” box that has USCP_IMSI filter with the following: •

SR:(OFAM=4FC,4FD,509,508,0A49,9F6,997,507,4B7) as conditions

Go to “Setup -> IMSI conditions”. Create a new “IMSI Set name”, add the IMSIs to be monitored, retain the holding time of 5 and save it.

5

In the main window of the L3 Data Collector, Click on “Get Units”. The monitorable units get populated in the units window. a) Navigate to one of the rows containing a USCP select the “USCP_IMSI” filter. b) In the IMSI(CP) column, select the IMSI filter. c) Right click on the row and set the filters to all USCP units.

DN09203161Issue:02

©2016Nokia

313


6


Click on “Set Filters” button and verify that the “Status” column for all selected units shows OK in blue. Select from available options •

Otherwise, check the L3 Data Collector log windowfor the error message.

Once the filters are applied successfully, the “Start” button is enabled. Click on it to begin monitoring. If calls matching the IMSIs in the IMSI filter are running or are setup, the Incoming Kbits/s starts showing the monitoring throughput.

7

Stop the monitoring. Monitored data from each plane and unit is saved into its own file.

8

7.2.10.7 7.2.10.7.1

Collected Control Plane files can be loaded to the L3 Data analyzer for decoding.

Deactivating RAN2930: IMSI-based Monitoring Deactivating RAN2930: IMSI-based call monitoring in IPA-RNC Follow this procedure to deactivate this feature. Procedure

1

Remove the RAN2930 configured network interface from the OMU towards the external monitoring tool. ZQRG:OMU,0:EL0:;

2

Remove the configured TCP/IP ATM internal interface of NPGE(P) towards OMU. ZQMD:INT:NPGE,0:IFAI4::OMU,0,AA0;

3

Remove IFAI interface at NPGE(P). ZQRG:NPGEP,0:IFAI4,:10.10.10.5;

Or ZQRG:NPGE,0:IFAI4,:10.10.10.5;

4

Remove the static route from NPGE(P) to the external monitoring tool. For static route from NPGE(P) via AA0 to Emil use the following command: ZQKA:;

314

©2016Nokia

DN09203161Issue:02



Step example < ZQKB; LOADING PROGRAM VERSION 2.72-0 RNC

IPA2800

2014-07-25

17:18:22

INTERROGATED STATIC ROUTES ROUTE UNIT DESTINATION SESSION ID -------- -----------------------OMU-0 DEFAULT ROUTE NPGE-0 DEFAULT ROUTE NPGE-0 10.56.17.0/24

5

BFD GATEWAY ADDRESS

TYPE

PREF NBR

------------------ ----- ---- ------ ---10.56.17.1 10.56.8.97 10.10.10.6

LOG PHY PHY

0 0 0

1 2 6

-

Delete the pre-shared key using this command: ZQ4D:GIVAXIPSK; ZQ4D:MSGMONPSK;

g

Note: Deleting the PSK impacts also general monitoring.

6

Set the feature state to OFF. ZW7M:FEA=:OFF;

7.2.10.7.2

Deactivating RAN2930: IMSI-based call monitoring in mcRNC Follow this procedure to deactivate this feature. Procedure

1

Delete configured ports. delete troubleshooting megamon

This deletes assigned IP address for each node of a BCN and also deletes the assigned SFP port and subnet for transferring monitoring data from the BCN

2

Set the feature state to OFF. set license feature-mgmt id feature-adminstate off

DN09203161Issue:02

©2016Nokia

315


7.2.10.8 7.2.10.8.1


Analyzing monitored data and troubleshooting Analyzing monitored data Checking the contents of the messages monitored using this feature requires the use of the L3 Data collector (Emil) which supports the RAN2930 feature. This must be ordered from NOLS.

Procedure 1

Care → Software Supply Tool → Product Related Tools / Rad io Access Network Tools → L3 Data Collector (Megamon) or L3 Analyzer/Viewer (Emil) → Release: LDC TSS15A SW → Standard Update → Maintenance Packet . The L3 Data collector and L3 Analyzer tools’ support for the RAN2930 IMSI-based Call monitoring feature is delivered in the TSS15A release (in NOLS, see release LDC TSS15A SW for Megamon and release LA TSS15A SW for Emil).

g 7.2.10.8.1.1

Note: The type of license key is an on/off license. A valid license needs to be requested from Contact Point, Message Analyser (NSN - FI).

Analyzing monitored data from IPA-RNC Procedure

1

For analyzing Control Plane and Transport Plane messages, load the Emil and in the “Select Emil mode” options, choose “RNC IMSI trace”.

2

Provide the correct encryption key for analyzing Control Plane monitored data. Load the file for analysis.

g

Note: For opening Control Plane monitored data, the encryption key (MSGMONPSK) which was set in the IPA-RNC must be administered in L3 Data Analyzer.

3

Open the needed messages and analyze the contents.

4

For analyzing User Plane messages, load the Emil and in the “Select Emil mode” options, choose “RNC UP”.

5

Load the file for analysis.

6


Monitored data from the IPA-RNC from Control Plane, User Plane and Transport Plane will be in the following formats:

316

©2016Nokia

DN09203161Issue:02


• • •

7.2.10.8.1.2


Control Plane: <>_<>_<>_<>.mgb User Plane: <>_<>_<>_<>_us.dat Transport Plane: <>_<>_<>_<>.mgt

Analyzing monitored data from mcRNC Procedure 1

For analyzing Control Plane messages, load the Emil and in the “Select Emil mode” options, choose “RNC IMSI trace”.

2

Provide the correct encryption key for analyzing Control Plane monitored data.

g

Note: For opening Control Plane monitored data, the encryption key (MSGMONPSK) which was set in the mcRNC must be administered in L3 Data Analyzer.

3

Load the file for analysis.

4


Monitored data from the mcRNC Control Plane will be in the following format: •

7.2.10.8.2

Control Plane: mcRNC_USCP-<>_<>_<>.mgj

Troubleshooting RAN2930: IMSI-based Call Monitoring Purpose Follow these steps to collect necessary logs for Nokia to investigate monitoring data collection problems. Procedure

1

Enable Megamon interface logging. Select “action -> if logging -> set logging” in L3 Data Collector.

2

Start DMX message monitoring of SW proc esses responsible for monitoring. This can be done by using conventional L3 Data Collector or MML/SCLI commands. • •

DN09203161Issue:02

For IPA-RNC, monitor OMU and ICSU units with filter “SR:OFAM=728” For mcRNC, monitor CFPU unit with filter “SR:OFAM=728,0B12” and USCP unit with filter “SR:OFAM=0A56”

©2016Nokia

317



3

Reproduce th e p roblem.

4

Collect Megamon interface logging file and DMX message monitoring.

5

Collect RNC symptom report. • •

For IPA-RNC, use TN38 Rnclogcol.exe to collect symptom reportwith Basic profile. For mcRNC, execute the following SCLI command: save symptom-report name include group-RNC

6

In cases where IPA-RNC Transport Plane monitoring does not collect any data, the following logs should be additionally collected from NPGE(P) units. DMX message monitoring for Transport Plane monitoring agent from the NPGE(P). loadext dmxmon <=Loads dmxmon service terminal extension dmxmon –f a83 <=Starts DMX monitoring for family a83 (XAGENT)

Monitoring can be stopped by pressing . Before and after monitoring:jane kuostat. When IMSI-based call monitoring is ongoing and monitored call(s) are active: jane prtree mon_dst_addr jane jane jane jane jane jane jane jane clog

prtree prtree prtree prtree prtree prtree prtree prtree –sa

Table 134

mon_src_addr ipv4_fwd load_sharing ls_path l3l2 gtp_trace udp_trace_ing udp_trace_egr

RAN2930 symptoms and recovery actions Symp tom

After “Get Units” is done, No units are visible in Megamon or only some units are visible

R e c o v e r ya c t i o n

1. Check that Givaxi is running correctly and is waiting for external tool to connect.

2. Verify that the Pre-shared key is administered correctly. the in port configuration 3. In themcRNC, L3 Datacheck Collector every module. for

318

No Transport Plane monitoring data available (IPA-RNC)

1. Check IPoA configuration and ping

After “Set Filter”, “Start” button does not get enabled

Set the monitoring conditions correctly.

©2016Nokia

between NPGE/NPGE(P) and the External machine 2. Check site router configuration

DN09203161Issue:02


Table 134


RAN2930 symptoms and recovery actions (Cont.) Symp tom

R e c o v e r ya c t i o n

In L3 Data collector event window, file_open_error_ec (0x0000386E) is encountered

Create the msg-mon-psk (for encryption)

If INVALID_IMSI_EC is returned

Check and make sure IMSI length is not more than 15 characters

If Transport failsmonitoring with the error: Setup Plane failed:monitoring Could not set filters for unit NPGE-0 (TransportPlaneMonitoring). Error: illegal_value_of_param_ec (0x00003829)

Check whether the IPoA connections setup between the Transport Plane units, theare OMU and the Emil/Megamon.

Control Plane monitoring data from the beginning of the call is not available

If holding time has been increased (to handle network delays) and buffer size is not correspondingly increased then Buffer size needs to be increased in this case as per the guidance specified in the user manuals of the L3 Data collector.

Setting up monitoring for one of the selected units fails

The reason for the failure must be corrected or the unit must be omitted from the list of monitored units for the monitoring to be started.

in L3 Data collector, in the “setup -> Output files”, the “Operating mode -> IMSI monitoring” option does not appear

RAN2930 specific license is not available. Previously working Megamon license for the PC cannot be used for RAN2930 operations.

NPGE/NPGE(P) IP addresses are not available IPoA configuration is not correct after the “Get Units” operation in the L3 Data collector

7.3 RAN3104: HSPA User Amount Monitoring Introduction to the feature The existing counters are capable of counting the maximum number of HSDPA and HSPA users on Cell_DCH. TheRAN3104: HSPA User Amount Monitoringfeature introduces new cell level counters, which allow the HSPA subscriber amount monitoring per cell including HS-FACH.

7.3.1

RAN3104 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables to follow HSPA subscriber evolution in the network.

7.3.2

RAN3104 Functional description The RAN3104: HSPA User Amount Monitoringfeature introduces new counters to 1006 RRC signalling measurement. These counters enable to monitor the amount of HSPA subscribers per cell.

DN09203161Issue:02

©2016Nokia

319



For counting the maximum number of HS-FACH/HS-RACH users per cell, a new HSPAtot value is introduced: •

HSPAtot = HSPA + HSDPA/DCH + HS-FACH/RACH + HS-FACH/HS-RACH The HSPAtot value represents the peak number of HSPA-related users in one cell.

To calculate HSPAtot, the following counters are introduced: •

•

M1006C318: MAX NUMBER OF HS-FACH/R99-RACH USERSPER CELL The peak number of users in CELL-FACH state on DL/UL HS- FACH/DCH channels per cell during the measurement period. M1006C319: MAX NUMBER OF HS-FACH/HS-RACH USERSPER CELL The peak number of users in CELL-FACH state on DL/UL HS- FACH/HS-RACH channels per cell during the measurement period.

The monitoring checks the HSPA user amount on a cell level and the reported value is based on the discovered peak value upon the measurement period. For monitoring HSPA subscriber amount per cell, the following counters are introduced: •

•

7.3.3

M1006C321: MAX NUMBEROF HSPA AND HS-FACH USERS PER CELL The actual maximum amount of HS users in CELL_FACH state and CELL_DCH state per cell. M1006C320: MAX NUMBER OF PCH USERS WITH H-RNTI ALLOCATED PER CELL The amount of users that are in CELL_PCH state but with RNTIs and HS-FACH L2 resources allocated.

RAN3104 System impact Interdependencies between features The following features must be activated for proper working of the RAN3104: HSPA User Amount Monitoring feature: • •

g

RAN1637: High Speed Cell_FACH DL RAN1913: High Speed Cell_FACH Note: If the HS-FACH features are not enabled the counters introduced by the RAN3104: HSPA User Amount Monitoringfeature do not show valid values.

Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

7.3.4


320

©2016Nokia

DN09203161Issue:02


Table 135



RAS

I PA - R N C

WCDMA 16

RNC16

mc R N C

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2



MS C


S GSN






3GPP Rel-8



C o u n t e rI D


MAX NUMBER OF HS-FACH/R99-RACH USERS PER CELL

RRC Signalling

M1006C319

MAX NUMBER OF HS-FACH/HS-RACH USERS PER CELL

RRC Signalling

M1006C320

MAX OF PCH RNTI NUMBER ALLOCATED PERUSERS CELL WITH H-

RRC Signalling

M1006C321

MAX NUMBER OF HSPA AND HS-FACH USERS PER CELL

RRC Signalling

Table 137


C o u n t e rI D

g

C o u n t e rn a me

M1006C318

C o u n t e rn a me


M1000C282

MAX NUMBER OF HSDPA USERS PER CELL

Cell Resource (RNC)

M1000C283

MAX NUMBER OF HSUPA USERS PER CELL

Cell Resource (RNC)

Note: •

The M1000C282 counter means Cell_DCH state users withprimary carrier HSDSCH downlink in the cell.

•

The M1000C283 counter means Cell_DCH state users withprimary E-DCH carrier uplink in the cell.

Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature.

DN09203161Issue:02

©2016Nokia

321





BSW/ASW

BSW

7.3.5

S W comp on en t

RAN


Notdefined

Testing RAN3104: User Amount Monitoring Purpose

g

Note: This is an example of the verification. Do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples, and they can vary in different networks. The purpose of this test case is to verify if the counters introduced by the RAN3104 HSPA User Amount Monitoringfeature are triggered: • • •

•

M1006C318: Maximum number of users in cell with HS-FACH/RACH M1006C319: Maximum number of users in cell with HS-FACH/HS-RACH M1006C320: Maximum number of users in Cell_PCH with dedicated C/H/E-RNTI allocated M1006C321: Maximum numberof total HS users in Cell_DCH state and HS-DSCH users in HS CELL_FACH state (with R99 RACH or HS-RACH UL)

Before you start For the test case, the following network elements must be at least on the following software level:

•

RNC: RNC16/mcRNC16 OMS: WOMS16

•

WBTS: WBTS16

•

For the test case, the following network elements and equipment are used: • •

•

IU-PS WRAB one WBTS

• •

one IPNB some WCELs to be created

• •

322

RNC IU-CS

©2016Nokia

DN09203161Issue:02



Procedure

1


2

Start the M1006 measurement. Wait for the measurement interval to begin. Note: In case of a 15-minute interval, data collection starts every quarter. For example 11:00, 11:15, 11:30, 11:45.

g 3

Run a HS-FACH/RACH user, a HS-FACH/HS-RACH user, Cell_PCH with a dedicated C/H/E-RNTI allocated user and a HSPA user separately in cell level during 15 min time window.

4

Stop all calls before 15 min time interval has passed.

5

Open the RNW Me asurement Presentation application and check the values of counters M1006C318, M1006C319, M1006C320 and M1006C321.

g

Note: Measurement results are available in the application after the measurement interval ends plus 10 minutes. For example, if you start the measurement at 11:22, the collected data is available in OMS at 11:55.

Result Expected outcome The value of counters M1006C318, M1006C319, M1006C320 and M1006C321 have incremented in a selected 15 min time interval. Unexpected outcome The value of counters M1006C318, M1006C319, M1006C320 and M1006C321 in a selected 15 min time interval is zero and have not incremented.

7.4 RAN2862: Multi-RAB Dedicated Counter Set Introduction to the feature The RAN2862: Multi-RAB Dedicated Counter Setfeature introduces additional counters for monitoring CS + PS multi-RAB performance for the following cases:

•

Accessibility of CS Voice RAB setup on top of active PS user plane Retainability of CS Voice RAB on top of active PS user CS Voice RAB duration with active PS user plane

•

CS + PS Multi-RAB handover

• •

DN09203161Issue:02

©2016Nokia

323


7.4.1


RAN2862 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature improves monitoring capabilities by adapting measurements to the operator’s needs.

7.4.2

RAN2862 Functional description The RAN2862: Multi-RAB Dedicated Counter Setfeature introduces additional counters for monitoring CS + PS multi-RAB performance. This optional feature adds new counters for: •

CS Voice setup attempts, setup failures, accessfailures, access completions, and active failures while at least one PS RAB has REL99 DCH, HS-DSCH/DCH, or HSDSCH/E-DCH PS user plane at the moment of failure

•

Measuring how long CS Voice RAB and active PS RAB is working together SHO, IFHO, and ISHO success rate forCS Voice + PS Multi-RAB

•

7.4.3

RAN2862 System impact Interdependencies between features This feature has no impact on other features. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network and network element management tools. Impact on system performance and capacity This feature has no impact on system performance and capacity.

7.4.4



mc R N C


WCDMA 16

324

RNC16

mcRNC16

OMS

NetAct

WCDMA OMS16

NetAct 16.2

MS C


©2016Nokia








DN09203161Issue:02



This feature requires no new or additional hardware. Alarms There are no new alarms related to this feature. BTS faults and reported alarms There are no BTS faults and reported alarms related to this feature. Commands There are no new commands related to this feature. Measurements and counters Table 140


C o u n t eIrD

C o u n t enr a m e

M e a s u r e me n t

M1001C751

RAB SETUP ATTEMPT CS AMR WITH ACTIVE PS

M1001C752

RAB SETUP FAILURE CS AMR WITH ACTIVE PS

M1001C753

RAB ACCESS FAILURE CS AMR WITH ACTIVE PS

M1001C754

RAB ACCESS COMPLETE CS AMR WITH ACTIVE PS

M1001C755

RAB ACTIVE FAILURE CS AMR WITH PS R99

M1001C756

RAB ACTIVE FAILURE CS AMR WITH HSDPA

M1001C757

RAB ACTIVE FAILURE CS AMR WITH HSUPA

M1001C758

RAB HOLDING TIME CS AMR WITH ACTIVE PS

M1007C73

SHO SUCCESS FOR CS + PS ACTIVE MULTI-RAB

M1007C74

SHO FAILURE FOR CS + PS ACTIVE MULTI-RAB

M1008C319

IFHO SUCCESS FOR CS + PS ACTIVE MULTI-RAB

M1008C320

IFHO FAILURE FOR CS + PS ACTIVE MULTI-RAB

M1010C276

ISHO SUCCESS FOR CS + PS ACTIVE MULTI-RAB

M1010C277

ISHO FAILURE FOR CS + PS ACTIVE MULTI-RAB

Service Level (RNC)

Soft Handover (RNC)

Intra System Hard Handover (RNC) Inter System Hard Handover (RNC)

Key performance indicators There are no KPIs related to this feature. Parameters There are no new parameters related to this feature. Sales information Table 141


BS W/ASW

ASW

DN09203161Issue:02


RAN

©2016Nokia


RNC ON/OFF License key

325


7.4.5


Activating RAN2862: Multi-RAB Dedicated Counter Set Purpose Follow this procedure to activate the feature. Before you start RNC and BTS restart is not required after the activation of this feature. The procedure is a non-service-affecting activity and does not cause downtime. The RAN2862: Multi-RAB Dedicated Counter Setfeature is controlled by the long-term ON/OFF license key. For more information on licensing, seeLicensing.

g

Note: The feature code for this feature is5571.

Procedure

1

Set the feature state to ON Use this commands to activate the feature: •

For IPA-RNC:

•

For mcRNC:


Result Expected outcome: The RAN2862: Multi-RAB Dedicated Counter Setfeature has been activated. The OMS shows the counter values in RNW measurement presentation GUI and forwards data to NetAct if related measurements M1001, M1007, M1008 and M1010 are active. Further information: If the RNC does not have the license installed and feature activated, counters have zero value in RNW Measurement Presentation GUI and are not sent to NetAct.

7.4.6

Verifying RAN2862: Multi-RAB Dedicated Counter Set Purpose Follow this procedure to verify the feature. Before you start The RAN2862: Multi-RAB Dedicated Counter Setfeature is activated. Make sure you have an access to the following applications:

326

©2016Nokia

DN09203161Issue:02


• •



Procedure

1


2

Start th e M1001 me asurements. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.

3

Wait for the next 60-minute interval to begin. The measurement interval then starts. For example, if you press the Start button at 11:22, the data collection starts at 12:00.

4

Make a CS Voice call.

5

Make a PS call on top of the CS Voice RAB with the same UE.

6

Download a file using PS connection.

7

Release both calls. Wait until the current 60-minute interval ends for the measurement collection and an additional 10 minutes for the measurement data to be transferred to the OMS.

8

Check with RNW Measurement Presentation GUI that counter M1001C758 has greater than zero value.

Result Expected outcome: Counter M1001C758 RAB HOLDING TIME CS AMR WITH ACTIVE PS shows higher than zero value. If the counter value is zero, the feature is not activated.

7.4.7

Deactivating RAN2862: Multi-RAB Dedicated Counter Set Purpose Follow this procedure to deactivate the feature. Before you start The RAN2862: Multi-RAB Dedicated Counter Setfeature is activated.

DN09203161Issue:02

©2016Nokia

327



Procedure

1

Set the feature state to OFF

g

Note: The feature code for this feature is5571. Use this commands to deactivate the feature: •

For IPA-RNC: ZW7M:FEA=5571:OFF;

•

For mcRNC: set license feature-mgmt code 0000005571 feature-adminstate off

Result Expected outcome: The RAN2862: Multi-RAB Dedicated Counter Setfeature has been deactivated. The OMS shows the counters have zero value in RNW Measurement Presentation GUI and are not sent to NetAct.

7.5 RAN2304: VSWR Monitoring Introduction to the feature VSWR (Voltage Standing Wave Ratio) provides information on how much transmitting power is reflected back (lost from destination) to the antenna line. The smaller the VSWR value, the better. In addition VSWR is used during installation and tuning transmitting antennas, as well as during troubleshooting cases and as an aid when tuning VSWR alarm thresholds. Purpose ofRAN2304: VSWR Monitoringfeature is to deliver quasi real time VSWR samples from selected radios antenna lines to BTS Site Manager. Monitoring is possible for 3TX and 6TX RFMs, 2TX and 4TX RRHs.

7.5.1

RAN2304 Benefits End-user benefits This feature does not affect end user experience. Operator benefits RAN2304: VSWR Monitoringfeature enables the operator to monitor VSWR (Voltage Standing Wave Ratio) information via BTS Site Manager from all active transmitter antenna lines. Information is updated with 10 seconds intervals. VSWR monitoring leads to better remote monitoring capability and faster problem solving, creating CAPEX saving to network maintenance. Performance monitoring counters are provided to enable whole network monitoring for current VSWR values.

328

©2016Nokia

DN09203161Issue:02


7.5.2


RAN2304 Functional description RAN2304: VSWR Monitoring feature is enabled via license. Performance Monitoring counters RAN2304: VSWR Monitoringfeature introduces a new PM counter for each antenna line. The counter shows the average value of VSWR during the measurement period (1h by default). Live VSWR monitoring RAN2304: VSWR Monitoring feature enables VSWR live monitoring via the BTS Site Manager. The corresponding dialog box is opened by navigating through the menu:Antenna ► Tune and Monitor VSWR ► Monitor VSWR. Figure 54

Monitor VSWR dialog box

The radio module table enables the user to select and activate VSWR monitoring for specified modules. Only applicable radio modules are listed. The user sets a monitoring interval between 10 and 3600 seconds, default value is 60 seconds. On pressing start, BTS Site Managers collects and stores VSWR data to a temporary file. It is possible to save the temporary data to user defined file by: • •

DN09203161Issue:02

Stopping the monitoring and choosing the Save As... option. Starting the VSWR monitoring when temporary file already exists.

©2016Nokia

329



Exiting the BTS Site Manager or disconnecting theBTS while temporary file closes. If not saved, temporary file is deleted.

•

Saving the data to a user defined file, clears the temporary file. When monitoring begins, elapsed time and values are displayed. Possible statuses are: Starting monitoring... -monitoring is requested, but is yet to start. Monitoring... - monitoring isongoing and values are displayed and stored to the temporary file.

• •

Starting monitoring failed -Monitoring cannot bestarted or license is missing. Stopping monitoring ...- stopping monitoring is requested,but has not yet stopped. Monitoring completed - monitoringis stopped and data can be saved to a user defined file.

• • •

Values are displayed in theMonitored values table for each antenna.

g

Note: For following FRM/RHH, even if the measured VSWR value is lower than 1.5, the fixed value of 1.5 is reported: • •

7.5.3

FHxA RRH modules FRGF FRM modules with FFGFsmanufactured by PW (SW version N_00V010507)

RAN2304 System impact Interdependencies between features This feature shares the same license withRAN907: Antenna Line Supervision. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

7.5.4



mc R N C


WCDMA 16

330


OMS

NetAct

WCDMA OMS16

NetAct 16.2

Support not required MS C


©2016Nokia

WBTS16

S GSN


Flexi

Flexi Lite

Multiradio 10 BTS BTS

WBTS16

MGW


Not planned

UE


DN09203161Issue:02



Monitoring is possible for FRGF and all Rel.2.1 and onwards RFM and RRH modules. Alarms There are no alarms related to this feature. Measurements and counters Table 143

New counters introduce d by RAN2304

C o u n t e rI D

M5010C0

C o u n t e rn a me


AVERAGE VALUE OF VSWR

5010 - WBTS Antenna Line (WBTS)

Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 144


B SW/AS W

ASW

7.5.5


RAN


BTS LK

Testing RAN2304: VSWR Monitoring Before you start Test environment: • • •

Operational Radio Access Network and Core Network. Both FSMr2 and FSMr3 platform can be used for these tests. HW configuration: Radio modules FRGFand all Rel.2.1 and onwards RFM and RRH modules.

Preconditions:

•

WBTS is required to be in On Air status Commissioning parameter Antenna line supervision in use must be enabled, see Figure 55: Antenna line supervision in use parameter set. .

•

License key Antenna Line Supervision (key:309) is available.

•

DN09203161Issue:02

©2016Nokia

331


Figure 55


Antenna line supervision in use parameter set.

Procedure

1

Open the BTS Site Manager and go to: Antenna -> Tune and Monitor VSWR…

2

Open Monitoring and go to Monitor VSWR.

3

Press the "Start" button.

4

VSWR measurements are collected during the defined interval (default interval is 60s).

5

Press the "Stop" button.

6

Save the results, using the "Save As..." button.

7

Verify if the file is saved in desired location.

Result If the antenna is properly set up, current VSWR values should be visible and a saved data file should contain all the measured parameter values: PC time, Ant X VSWR, Ant X+1 VSWR.

332

©2016Nokia

DN09203161Issue:02


RNC solution features

8 RNC solution features 8.1 RAN2646: External Alarm Input Support of mcRNC Introduction to the feature This feature enables the utilization of mcRNC-integrated external alarm inputs, which can be used for indicating changes in the condition of supervised external entities. mcRNC reacts to the state changes of the alarm inputs, and raises or clears the related user-defined external alarms accordingly. External alarm inputs need to be configured into the system before these inputs and their related external alarms can be put into use. External alarms, for example door alarms or fire alarms, are managed by normal alarm operations. They can be monitored like regular mcRNC alarms, via SCLI, OMS EM Fault Management GUI, and NetAct Monitor.

8.1.1

RAN2646 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits Easier alarms management solution for external device. Cost reduction due to changes in the condition of supervised external entities. These can be converted to normal alarm events and reported to operating personnel via the same user interfaces as the internal alarms of mcRNC.

8.1.2

RAN2646 Functional description The RAN2646: External Alarm Input Support of mcRNCfeature enables mcRNC to collect triggering signals and use them to raise or clear a series of user-defined external alarms accordingly. These alarms can be managed by regular alarm operations. External alarms are not triggered by the mcRNC itself. External alarms are triggered by other external equipment at the RNC site, which indicates changes in the condition of supervised entities: for example, if a door is opened or if the temperature of the equipment premises exceeds a certain threshold. There are eight alarm inputs per BCN module. The maximum supported input amount in the mcRNC step 7 configuration is 64. The external alarm input can be assigned to an external alarminput-id ID, which run in increments of 8, depending on the number of mcRNC modules in the deployment. External Input shows input-id ranges per module number. Table 145

External Input

module number input-id

1 2

DN09203161Issue:02

0 -7 8 - 15

©2016Nokia

333



Table 145

External Input (Cont.)

module number input-id

3

16 - 23

4

24 - 31

5

32 - 39

6

40 - 47

7

48 - 55

8

56 - 63

The operator is able to define input description, input polarity, input severity and input admin state for certain external alarm inputs. It is also possible to assign a predefined alarm number to the external alarm input. This configuration is performed via the Structured Command Line Interface (SCLI), and the definition or definition update take effect at the mcRNC running time. There are two RJ45 connectors per module for external alarm input connections. Inputs are voltage sensitive, with a pull-up resistor which allows the connection of direct contacts or optical couplers as alarm sources to these alarm inputs.

8.1.3

RAN2646 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.

8.1.4


334


RAS

I PA - R N C

mc R N C

WCDMA16


mcRNC16

©2016Nokia






DN09203161Issue:02


Table 146


RAN2646 hardware and software requirements (Cont.)

OMS

NetAct

MS C

S GSN





MGW


UE


This feature does not require any new or additional hardware. Alarms There are no such alarms related to this feature, which would indicate incorrect functionality of the feature. However, the feature raises and clears predefined external alarms, alarm numbers of which are in the range 70400-70431. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 147


BS W/ASW

BSW

8.1.5

L i ce n s e c on tr ol i n n e t w or k element

RAN

Activated by default

-

Activating RAN2646: External Alarm Input Support of mcRNC This feature does not require activation. These instructions only illustrate how to enable its functionality. Purpose Enabling external alarm inputs in mcRNC. Before you start Functionality of the external alarm inputs needs to be verified before connecting them to the controller. As shown in Figure 56: External alarm interface, each BCN module provides eight external alarm interfaces on two RJ45 connectors in the front panel. The inputs are voltage sensitive. Alarms are activated by closing the alarm circuit with an external switch. Both closing and opening the loop will generate an IPMI event to the hardware management system.

DN09203161Issue:02

©2016Nokia

335



Figure 56

External alarm interface +

+

Alarm input interface 8 x voltage input (RJ45) The closed loop current of the alarm circuit is 1 mA. Attention needs to be paid on the contact materials of the switch to prevent contamination of the contact surfaces. It is also possible to use a transistor output, such as an optical isolator, to close the circuit. Glitches shorter than 10 ms are filtered out by hardware. The alarm inputs are not galvanically isolated in the BCN. When remote external equipment is used to drive the inputs, galvanical isolation (relays, optical isolators) should be used. Figure 57

Connecting external alarm inputs

2

2

Shielded twisted pair cable

5 4 J R

2

2

Level shifting, filtering




CH1

CH2

CH3

LMP

CH4

CH5-8

Galvanic isolation between customer equipment and BCN

Procedure

1

g

336

Prepare and validate functionality of external alarm equipment. Note: External hardware and external alarm inputs should be tested. The operation of the external alarm input ports need to be verified before connecting equipment in to the ports. Port working status can be found out by manually testing each input with working external equipment, for example manually triggering an input polarity change and checking that the alarm equipment reacts accordingly.

©2016Nokia

DN09203161Issue:02


2


Connect the external alarm equipment to the mcRNC. Figure 58: Connecting external alarm inputsshows how to connect external equipment to the mcRNC. Figure 58

Connecting external alarm inputs +

+

Table 148: External alarm pin mappingprovides a map of the RJ-45 pins for each of the external alarm interfaces. Table 148

External alarm pin mapping A l a r mi n t e r f a c e1

DN09203161Issue:02

A l a r mi n t e r f a c e2

Pin P i nn a me number

D e s cr i p t i o n

1

EXT_ALARM_P_3

Alarm 3 positive input

EXT_ALARM_P_7


2

EXT_ALARM_N_3

Alarm 3 negative input

EXT_ALARM_N_7


3

EXT_ALARM_P_2


EXT_ALARM_P_6


4

EXT_ALARM_P_1


EXT_ALARM_P_5


5

EXT_ALARM_N_1


EXT_ALARM_N_5


6

EXT_ALARM_N_2


EXT_ALARM_N_6


7

EXT_ALARM_P_4

Alarm input 4 positive

EXT_ALARM_P_8

Alarm input 8 positive

8

EXT_ALARM_N_4


EXT_ALARM_N_8


©2016Nokia

P i nn a m e

D e s c ri p ti o n

337



3

Check available external alarm inputs. To check what are the currently available external alarm inputs that can be used for the new device, use the following command: show hardware config ext-alarm-input free

Step example 0 3 4 5 6 7 8 10 11 12 13 14 15

4

Verify existing alarms type mappings if there is already a suitable alarm type to map for the new external alarm device. Enter this command: show hardware config ext-alarm-type all

Depending on the result do one of the following sub-steps: Sub-steps

a) Take note of the suitable exiting alarms to map to the new external alarm device Step example Specific problem Title Default severity Mapping status

: : : :

70421 CUSTOMIZABLE EXTERNAL HW ALARM_1 major Free

Specific problem Title

: 70401 : CHANGE THE TITLLE NUMBER_2

Default Mapping severity status

: : major mapped

b) If there is no suitable alarm yet, check which alarms are unused and modify such unused alarm text to match needs for the new device. The alarm text is modified with the following command:

338

©2016Nokia

DN09203161Issue:02



set hardware config ext-alarm-type specific-problem title Step example set hardware config ext-alarm-type specific-problem 70400 title "EXT ALARM EQUIPMENT NUMBER 1" 5 Create mapping between alarm type and external alarm input. To map external alarm input to an alarm type you need to specify the input-specific attributes that define its characteristics. Use the following command: f Only minor, major or critical severity shouldbe set with SCLI for external alarm input. OMS Fault Management will clear warning severity alarms automatically and NetAct will not display warning severity alarms. add hardware config ext-alarm-input input-id <input-id> specific-problem <specific-problem> description <description> polarity <polarity> severity <severity> admin-state <admin-state rel="nofollow"> t Tip: Table 149: External Inputshows input-id ranges per module number. Table 149 External Input module number input-id 1 0- 7 2 8 - 15 3 16 - 23 4 24 - 31 5 32 - 39 6 40 - 47 7 48 - 55 8 56 - 63 Step example add hardware config ext-alarm-input input-id 0 specificproblem 70400 description DOOR_SWITCH_1 polarity open severity critical admin-state enabled DN09203161Issue:02 ©2016Nokia 339 RNC solution features WCDMA 16 Feature Descriptions and Instructions Result The operator has successfully configured an external alarm. 8.1.6 Verifying RAN2646: External Alarm Input Support of mcRNC This feature does not require verification. These instructions only illustrate how to verify its functionality. Purpose Verify that external alarms are properly configured. Procedure 1 Check if any alarm exists. Use the following command: show hardware config ext-alarm-input input-id <input-id> specific-problem <specific-problem> Step example show hardware config ext-alarm-input input-id 0 specificproblem 70400 Step example Input-id Specific problem Description Polarity Severity Admin-state 2 : : : : : : 0 70400 DOOR_SWITCH_1 open critical Enabled Trigger an external device alarm. Step example Assuming alarm DOOR_SWITCH_1 is mapped to a door sensor, open said door. 3 Verify if the predefined external alarm was raised in mcRNC. Enter the following command: show alarm active filter-by specific-problem <ext-alarmnumber> Step example 340 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features show alarm active filter-by specific-problem 70400 Step result Alarm ID Specific problem Managed object Severity Cleared Clearing Acknowledged Ack. user ID Ack. time Alarm time Event type Application : : : : : : : : : : : : 115661 70400 - DOOR_SWITCH_1 fsManagedObjectId=external_hw 2 (critical) no automatic no N/A N/A 2015-08-31 09:32:37:829 CST x3 (environmental) fshaRecoveryGroupName=HPIMonitor,fsFrag mentID=RecoveryGroups,fsFragmentId=HA, fsCluster=ClusterRoot Identif appl. addl. info : input-id=0 Appl. addl. info : Description={efg} Unit={BCNMB-B} Positi on=/chassis-1/motherboard-1 Sensor={num ber=254,Name=External alarm} Result The operator has successfully verified external alarm. 8.1.7 Deactivating RAN2646: External Alarm Input Support of mcRNC This feature does not require deactivation. These instructions only illustrate how to disable its functionality. Purpose Disabling external alarm inputs in mcRNC. Procedure 1 Set the alarm admin state to disabled. Any active alarm mapped to the input is cleared automatically when entering the following command: set hardware config ext-alarm-input input-id <input-id> admin-state disabled Step example set hardware config ext-alarm-input input-id 0 admin-state disabled DN09203161Issue:02 ©2016Nokia 341 RNC solution features WCDMA 16 Feature Descriptions and Instructions Result The operator has successfully disabled the external alarm input. 8.2 RAN3057: mcRNC Signaling Capacity License Introduction to the feature The RAN3057: mcRNC Signaling Capacity Licensefeature introduces a new license to control signaling capacity. w This feature must not be removed from the system. It is mandatory to activate the feature, which means to install the license on the controller before the system runs for the first time with the new software in the live network. The constant growth of smartphone usage demands higher signaling capacity. Signalingrelated tasks comprise management, connection establishment, and connection control. Signaling capacity usage is monitored by CS+PS session Successful Busy Hour Call Attempt (SBHCA) counters. After activation the user is obliged to monitor the signaling capacity. If more signaling capacity is necessary, the users receive a relevant notification through an alarm. More signaling capacity requires the installation of signaling capacity license, delivered as signaling capacity license files. 8.2.1 RAN3057 Benefits End-user benefits This feature does not bring any benefits to the end-user. Operator benefits This feature benefits the operator as follows: • 8.2.2 With "Buy as You Grow" sales approach the customer saves CAPEX whenthe signaling load in his network is low and can later buy more signaling capacity licenses when the signaling load grows. RAN3057 Functional description Overview A new signaling capacity license is introduced in mcRNC16 to control the usage of signaling capacity on mcRNC HW Rel.2 controller. This license carries the 5385 feature code and is required to be installed in the controller before the system can be taken to live network use. w If the user did not installed the signaling license there is a high risk of major system fault-the RNC PS throughput capacity will be severely limited, to approximately 100Mbps in total. In practice this is equivalent to no PS data throughput. Signaling capacity is defined by the total number of the following procedures taking place simultaneously within the system: • 342 CS voice RAB setup ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions • • RNC solution features PS user plane allocation in radio network Cell_PCH to Enhanced Cell_FACH transition The RAN3057: mcRNC Signaling Capacity Licensefeature monitors the controller's signaling load in the background by measuring CS+PS session SBHCA and comparing this value with the licensed signaling capacity limit value. When the signaling load approaches the licensed capacity limitation, the feature provides an alarm notification. As a result the customer gets information about the necessity to buy more capacity with the license file. License preparations The user is responsible for calculating the required license. Data for the calculations may be obtained through these possible scenarios: • • The operator has the controller installed inthe live network andis able to run specified measurements. The operator purchases new controller and must estimate what the license size is basing on the relevant traffic profile. Calculation of the required capacity license size using data obtained from the live network. In case the operator is able to obtain data from the network, he collects measurement from the counters listed inMeasurements and counterand use measured values in the relevant Signaling capacity license size formula. After the feature the user indicators measures required license size using Measurements and counter and activation Key performance Estimating the license size on the basis of the user's traffic profile. The RNC Control Plane load strongly depends on the number of subscribers and the related traffic profile. Data for the calculation is taken from the user-specific traffic profile or from default smartphone traffic profile. Primary method for calculating the license size is RNC_5537a Average Signaling Capacity Usage KPI. If the counters for the KPI are not available, the needed amount of signaling capacity must be calculated with the following formula: Procedure of estimating the license size on the basis of the user's traffic profile. 1. Basing on Smartphone traffic profile referencedetermine the following values: • CS BHCA per subscriber • • PS session BHCA for human per subscriber PS session BHCA for pollings per subscriber 2. Predict the number of subscribers. 3. Calculate the signaling load with the formula: Signaling load=(CS BHCA per subscriber + PS session BHCA per subscriber) * number of subscribers 4. Read out required signaling capacity license size using Signaling capacity license DN09203161Issue:02 ©2016Nokia 343 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 150 Signaling capacity license C a p a c i t yl i c e n s e Basic capacity S 1 -B 2 S 3 -B 2 2 927 Separately licensed capacity 642 Extended capacity 3 569 7 317 1 605 8 922 S 7- B 2 16 586 3 638 20 224 Example of calculations CS BHCA per subscriber = 1 PS session BHCA for human per subscriber = 3.2 PS session BHCA for pollings per subscriber = 12.8 Predicted number of subscribers = 50 000. PS session BHCA per subscriber = PS session BHCA for human per subscriber + PS session BHCA for pollings per subscriber PS session BHCA per subscriber = 3.2 + 12.8 = 16 Signaling load = (CS BHCA per subscriber + PS session BHCA per subscriber) * number of subscribers Signaling load = (1 + 16) * 50 000 = 850 000 BHCA = 850 kBHCA Interpreting the results According to the controller's capacity step the user reads out the required signaling capacity license size and compares it with calculations results. If: • Signaling load > Basic capacity the user must extended the signaling capacity. • Signaling load < Basic capacity the userdoes not need to extend the signaling capacity because basic capacity license is enough. Monitoring the signaling capacity license usage The controller performs signaling capacity license control by collecting CS+PS session SBHCA counters value every 30 seconds. Based on these calculations, the controller measures average signaling capacity usage, compares it with the actual licensed signaling capacity, and reports the average signaling capacity usage to the operator within a defined statistics reporting period. The licensed signaling capacity limitation defines the maximum CS+PS SBHCA value, measured in kBHCA. Because of this control, the feature requires the user to monitor the usage of the capacity license and compare it against the signaling load amount in order to purchase licenses when signaling increases. show The user can interrogate the usage controllercode for the used signaling capacity with the license feature-mgmt 0000005385 SCLI command. In reply the controller displays the current average signaling capacity usage. root@CFPU-0 [RNC-37] > show license feature-mgmt usage code 0000005385 CFPU-0@RNC-37 [2015-03-05 14:26:12 +0800] Feature Name : mcRNCSignalingCapacity Feature Code : 0000005385 Allowed Capacity : 155 344 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Used Capacity : 100 Combined Operational State: on Feature Description : RAN3057 mcRNC signaling capacity Allowed Capacity is a sum of the installed signaling capacity license files. Used Capacity indicates the currently used signaling capacity. There are two options as a result of the initial signaling capacity control: • The controller begins operatingwith the new software environment with traffic • unblocked if Allowed Capacity is greater than Used Capacity. The controller's application limits thePS data service, withoutblocking the AMR voice service if Used Capacity is greater than Allowed Capacity. If Used Capacity is greater than Allowed Capacity then: 1. The operator calculates, orders, and installs required, signaling capacity license file to mcRNC. 2. After the license file installation, the existing licensed signaling capacity are accumulated. In the resultAllowed Capacity increases. 3. The controller immediately cancels the warning alarm and terminates PS throughput limiting if Allowed Capacity is greater than Used Capacity. The operator is responsible to continuously monitor the used signaling capacity by collecting data from the M802 measurement counters listed inMeasurements and counter. Alerts and warnings for the signaling capacity license In case the license has not been installed because the feature is disabled or license has expired, O&M software raises alarm3360 LICENSE NOT READY to inform the user about failure. RNC PS throughput capacity will be severely limited, to approximately 100Mbps in total. In practice this is equivalent to no PS data throughput. This alarm is also raised when: • • • The feature has been disabled. The license has been removed. The license has expired. In this case the operator is responsible for license installation or license renewal. The controller checks the signaling capacity usage and warns the operator. The 3294 LICENCE CAPACITY WARNINGalarm is raised if the signaling capacity usage is close to licensed limitation. This checking helps to remind the operator that more signaling capacity is necessary. The operator must buy signaling capacity to avoid throughput penalty on PS interfaces. In case signaling capacity usage in the mcRNC exceeds the licensed capacity, the 3295 licence_capacity_exceeded_a alarm is raised. • • DN09203161Issue:02 mcRNC checks the signaling capacity usageand sets alarm if signaling capacity usage exceeds the predefined threshold, to let operator know throughput penalty has started. mcRNC cancels alarm 3295 while signaling capacity load has decreased. ©2016Nokia 345 RNC solution features WCDMA 16 Feature Descriptions and Instructions For more information seeAlerting signaling capacity license in SW License Key Controlled IPA-RNC and mcRNC Capacity. Troubleshooting When the user does not activate the feature correctly before system upgrade, he can still perform the operation afterward. After successful feature activation the controller cancels the related alarm and PS traffic is not limited. The user must not cancel this alarm manually. This action does not require system restart. Activating the feature for the factory pre-commissioned controller License must be installed by the operator right after the commissioning of the controller. Activating the feature after software clean installation License must be installed a by the operator right after the clean installation procedure was performed. Operating algorithm details The feature algorithm details are available inSW License Key Controlled IPA-RNC and mcRNC. 8.2.3 RAN3057 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature impacts interfaces as follows: • Iu-PS interface traffic is limited in case the feature is inactive. The PS limit is approximately 100Mbps in total. In practice this is equivalent to no PS data throughput. Impact on network and network element management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature impacts system performance and capacity as follows: • 8.2.4 signaling capacity is controlled by the license RAN3057 Reference data Requirements Table 151 346 RAN3057 hardware and software requirements RAS I PA - R N C mc R N C WCDMA 16 Support not required mcRNC16 ©2016Nokia Flexi Multiradio BTS Support not required Flexi Flexi Lite Multiradio 10 BTS BTS Support not required Support not required DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 151 RNC solution features RAN3057 hardware and software requirements (Cont.) OMS NetAct MS C WCDMA OMS16 NetAct 16.2 S GSN Support not required Support not required MGW UE Support not required Support not required This feature is mandatory from WCDMA16 release and the license is relevant only to mcRNC HW Rel.2. Alarms Table 152 New alarms introduced by RAN3057 A l arm ID A l arm n ame 3360 LICENSENOTREADY 3295 LICENSECAPACITYEXCEEDED Table 153 Existing alarms modified by RAN3057 A l arm ID A l arm n ame 3294 LICENCECAPACITYWARNING Measurements and counter Table 154 New counters introduced by RAN3057 C o u n t e rI D C o u n t e rn a me M802C26 SIGNALING_CAPA_USE_AVE M802C27 SIGNALING_CAPA_USE_MAX M802C28 SIGNALING_CAPA_LICENSED M802C29 PS_THR_LIMIT_DUR_SIGN M e as u r e m e n t RNC capacity usage measurement Key performance indicators Table 155 New key performance indicators introduced by RAN3057 KIP DI KnPaIm e Average Signaling Capacity Usage RNC_5537a Parameters Table 156 New parameters introduced by RAN3057 F u l ln a me A b b r e v i a t e dn am e M a n a g e do b j e c t Maximum Signaling Capacity MaxSignalingCapacity RNC Signaling Capacity License Warning Threshold SigCapLicWarnThreshold RNC Sales information DN09203161Issue:02 ©2016Nokia 347 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 157 RAN3057 Sales information BSW /ASW BSW 8.2.5 L i c e n s e co n tr ol i n n e t w or k element RNC LK Activated by default No Testing RAN3057: mcRNC Signaling Capacity License Before you start • • This license has been prepared according to License preparations Required test environment: – – – operational radio access network and core network HW: mcRNC HW Rel.2 (license is relevant only for this HW) SW: • • • • • NetAct 16.2 OMS16 mcRNC16 WBTS16/Flexi16 PET tester is needed to generate traffic. Procedure 1 Test the traffic after the lic ense has been installed with zero capacity. In case the license has not been installed because the feature is disabled or license has expired, O&M software raises alarm3360 LICENSE NOT READY to inform the user about failure. RNC PS throughput capacity will be severely limited, to approximately 100Mbps in total. In practice this is equivalent to no PS data throughput. Run the traffic described with the following parameters: • • 100 HSDPA 14.4M call 1000 AMR 12.2K with call duration 20s Step result • • 2 t 348 RNC PS throughput capacity islimited to 100Mbps in total. Alarm 3360LICENSE NOT READY is raised. Test the traffic when the license has been installed with a particular capacity. Tip: This example assumes that signaling license capacity is 100 KBHCA ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Sub-steps a) Install the license and enable feature with 100 KBHCA capacity. b) Run t he traffic Run the traffic described with the following parameters: • 100 HSDPA 14.4M call • 1000 AMR 12.2K with call duration 20s c) Interrogate the signaling capacity value in mcRNC root@CFPU-0 [RNC-1001] > show license feature-mgmt usage code 0000005385 Step result Allowed Capacity < Used Capacity CFPU-0@RNC-1001 [2015-03-05 14:26:12 +0800] Feature Name : mcRNCSignalingCapacity Feature Code : 0000005385 Allowed Capacity : 100 Used Capacity : 155 Combined Operational State: on Feature Description : RAN3057 mcRNC signaling capacity Step result Alarm 3294LICENCE CAPACITY WARNING is active. 3 Check measurement and counter registered values. Check Measurements and countervalues in OMS Application Launcher. These values are updated according to the real signaling capacity value Figure 59 g DN09203161Issue:02 RNW Measurement report for RNC Capacity usage Note: For mcRNC HW Rel.1 new counters added for this feature hold zero value. ©2016Nokia 349 RNC solution features WCDMA 16 Feature Descriptions and Instructions 8.3 RAN3005: Network Resiliency for mcRNC Introduction to the feature The feature improves network availability. This feature allows RAN recovery from fatal HW failure of a single controller or the controller's site. When one physical controller has failed, the operator is able to command the earlier-configured and synchronized backup physical controller to take over the responsibility of the failed physical controller. This feature helps to avoid long outages, lasting many hours or days. The feature improves network availability. This feature allows RAN recovery from fatal HW failure of a single controller or the controller's site. When one physical controller has failed, the operator is able to command the earlier-configured and synchronized backup physical controller to take over the responsibility of the failed physical controller. This feature helps to avoid long outages, lasting many hours or days. 8.3.1 RAN3005 Benefits End-user benefits This feature improves network services availability in case of catastrophes. Operator benefits This feature shortens the controller's outage time in the radio network. 8.3.2 RAN3005 Functional description The feature improves network availability during single outages and the controllers site outages. This feature introduces the following definitions: • • • Physical RNC (PRNC) which is a RNC HW with SW installed. Backup PRNC (BkPRNC) which is a PRNC configured only for redundancy purposes; it does not have its own radio access network under control. Protected PRNC (PrPRNC) which is a PRNC with running network services protected by BkPRNC. With this feature, the operator can introduce BkPRNC to protect a PRNC in the network. In case a PrPRNC fails, the BkPRNC is commanded by the operator to take over the RAN and interfaces, and to run the PrPRNC's services. One mcRNC configured as BkPRNC is able to protect up to 16 mcRNCs. One PrPRNC has one BkPRNC configured, so that the redundancy mode is N+1. The PrPRNC and the BkPRNC can be in the same physical site or in different sites. To fulfill the capacity requirement, required BkPRNC capacity step must be at least the same as the highest capacity step of PrPRNC in the resilient network. Table 158 Backup capacity step matrix BkPRNC cap acity ste p Supported PrPR NC capacit y steps in the res ilien t networ k S1-B2 (Step 1) 350 • S1-B2 (Step 1) ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 158 RNC solution features Backup capacity step matrix (Cont.) BkPRNC cap acity ste p Supported PrPRN C capacit y steps in the res ilien t networ k S3-B2 (Step 3) S7-B2 (Step 7) • S3-B2 (Step 3) • S1-B2 (Step 1) • S7-B2 (Step 7) • S3-B2 (Step 3) • S1-B2 (Step 1) The graphic shows in general the resiliency idea and introduces an example network concept. DN09203161Issue:02 ©2016Nokia 351 RNC solution features WCDMA 16 Feature Descriptions and Instructions Network resiliency transport network concept Figure 60 NetAct OMS RNC SGSN SGSN O&M CBC server Core SiteA PrPRNC SAS server MSS/MGW Site B PrPRNC BkPRNC PrPRNC PrPRNC BkPRNC Backhaul Active Standby RNC-cl O&M OMS NetAct NetAct connection 8.3.2.1 The link exists only if BkPRNC is activated. Differences between RAN3005: Network Resiliency for mcRNC and RAN2512: Network Resiliency for RNC2600 features This topic describes differences between Network Resiliency features. RAN3005: Network Resiliency for mcRNC feature introduces the same functionality as the RAN2512: Network Resiliency for RNC 2600 . Planning and operating principles are the same in both features. Also there are no differences from other network elemements point ov view. However, because of dissimilarities between SW and HW platforms composing two available RNCs, some difference occurs inRAN3005: Network Resiliency for mcRNC: 352 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions • • • • • • • 8.3.2.2 RNC solution features Smaller number of system resets is neededsince the IP Auto Adaptation (IPAA) can be done in both: base build and backup build. Iub control plane is included in IPAA which is managed with IP subnet mapping between PrPRNC and BkPRNC. Support for M:N mapping for both IP addresses and IP subnets. Longer resiliency-related operations Task queue in base build identifying ongoing resiliency operation as wellas the pending resiliency-related tasks of all RNCSRVs. Iubc source address setting follows genericmcRNC principle instead ofhaving a dedicated command. Differences in alarms. Planning for Network Resiliency The feature requires changes in several configuration, thus the user must plan: • • • • • • • 8.3.2.2.1 RNC-cl interface configuration Iu, Iur and Iu-PC interface control plane(CP) configuration Iu and Iur interface UP configuration Iu-BC interface configuration Iub interface configuration Transport network configuration Configuration of the interface with OMS and NetAct Planning IP addressing solutions on RNC-cl This chapter describes possible solutions for RNC-cl interface addressing. RNC-cl interface configuration RNC-cl is a new, proprietary interface between PrPRNC and BkPRNC. This interface does not have strict capacity requirements. The capacity of the interface must be enough for the system to transfer files from the PrPRNC to the BkPRNC in the desired maintenance window. g Note: Typical configuration package size is 1 MB. Length of PrPRNC’s maintenance window is four hours. RNC-cl interface is verified implicitly at every synchronization, thus special verification of configuration is not needed. Planning IP addressing solution For IP addressing on RNC-cl there are two alternatives for both PrPRNC and BkPRNC • • Shared IP address solution Dedicated IP addresses solution In the planning phase it is necessary to consider that: DN09203161Issue:02 ©2016Nokia 353 RNC solution features WCDMA 16 Feature Descriptions and Instructions • • After the RNCSRV has been created, any O&M IP addressing change introduced to the base configuration will not be automatically populated to the RNCSRV. The addressing change must be done manually for each of the RNCSRVs. All PrPRNCs must be configured with the selected solution, because the BkPRNC only allows only one solution to be configured at a time. Shared IP address solution This solution utilizes shared IP address for common RNC-cl traffic and other O&M traffic. It means that in addition to RNC-cl traffic all the other O&M traffic, like BTSOM traffic and RNC-OMS traffic, is terminated to the same IP address. This solution does not require additional IP layer configuration in the RNC. The activated feature automatically assigns existing O&M IP address. Examples in this Activation Instruction assume that the user uses shared IP address solution. This solution requires an additional IP address for RNC-cl forrnccl role in QNOMU. Dedicated IP addresses solution This solution requires an additional IP address for RNC-cl to the OMU’s CFPU interface, which the system uses for the separate RNC-cl and O&M traffic. The procedure is described in Configuring dedicated cluster interface . 8.3.2.2.2 Planning Iupc interface configuration The Iu-PC configurations enhancement is required to ensure this interface is working after the redundancy switch. This requirement impacts on the BkPRNC’s configuration and the CP configuration of each connected NE. RNC is a client on the Iupc interface. In case SAS validates the RNC’s source IP address, the validation rule is that the SCTP connection establishment is allowed from the PrPRNC and the BkPRNC. The SAS does not need to support the two simultaneous SCTP connections because the PrPRNC and BkPRNC are not online at the same time. 8.3.2.2.3 Planning Iu-BC interface configuration for mcRNC BkPRNC The Iu-BC configuration enhancement is required to ensure this interface is working after the redundancy switch. This has an impact on the BkPRNC’s CP configuration as well as to the CP configuration of the cell broadcast centre (CBC). The Iu-BC configuration follows the existing mcRNC principle. If this interface is not enabled in the system the Iu-BC role is not defined in any IP address in CFPU unit. CBC and RNC are able to have both the client and the server roles on Iu-BC ,even though CBC takes mainly the client's role. The client has to know the server's destination IP address whilst the server validates the address. In RNC, the Iu-BC source and destination IP addresses are defined in RNW DB. When RNW DB is copied from PrPRNC to BkPRNC, the Iu-BC source address is not valid in BkPRNC anymore and must be changed by the user. To change the source address give the iubc to a new IP address in CFPU unit and restart the system. 354 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features CBC has to know both the PrPRNC’s and the BkPRNC’s IP addresses in order to establish the interface, so CBC has to support the primary IP address, which refers to PrPRNC and the secondary IP address, which refers to BkPRNC. The secondary address is used when connection establishment to the primary address does not work, which is the case after a redundancy switch. It is possible that CBC validates the secondary IP addresses meaning that the same secondary IP address must not be used for multiple RNCs. In that case, in BkPRNC each RNCSRV has to have a unique source IP address. If CBC does not support the secondary IP address, the primary IP address has to be changed manually after the redundancy switch. In this case it is also necessary to manually verify if the broadcasts are ongoing or whether they should be restarted. When the primary RNC (in this case any of PrPRNC) is disabled, the secondary RNC (in this case BkPRNC) starts operating and sends a reset request to the CBC. This operation indicates to the CBC that it has to restart the broadcast, because it is impossible to establish a TCP/IP connection to the PrPRNC. The CBC must establish a connection to the BkPRNC and restart the broadcast. However, the actual CBC behavior is vendor specific and may vary from the described example. 8.3.2.2.4 Planning Iub interface configuration Iub interface configuration In BTS, the O&M and NBAP configuration must guarantee the connection establishment between BTS and BkPRNC, by adding additional BkPRNCconfiguration, which corresponds to the PrPRNC. Total required capacity remains the same as without network resiliency. The operator plans and configures Iub routing in the BkPRNC and does not configure the BkPRNC for Iub separately The controller does not support the IP SEC and thus an external security gateway is needed, if the operator wants to have an IPSEC at Iub. If IPSEC is enabled in the network, the compatibility of the security solution has to be verified together with the feature, meaning that the solution works also after the redundancy switch and redundancy switchback. It is important to ensure that the BkPRNC is able to access the primary security GW if redundant IPSEC tunnel does not exist between the security end points. If the access is disturbed and insecure connections cannot be established to peers, there is the risk that the network may become insecure or remain down An example of a working IPSEC solution is another IPSEC tunnel to a peer which the BkPRNC could utilize. 8.3.2.2.5 Planning Iu and Iur interfaces Iu and Iur interface control plane (CP) configuration Iu and Iur CP configurations enhancement is required to ensure these interfaces are working after the redundancy switch. This requirement impacts upon the BkPRNC’s configuration and the CP configuration of each connected NE. Total required capacity for Iu and Iur interfaces remains the same as without network resiliency. DN09203161Issue:02 ©2016Nokia 355 RNC solution features WCDMA 16 Feature Descriptions and Instructions Each PRNC requires its own SCTP associations. It is assumed, that N SCTP associations are needed in a situation where network resiliency is not applied. The number of required SCTP associations in Iu is doubled to2N, when network resiliency is introduced for the controller. The number of required SCTP associations for the Iur interface varies depending on whether network resiliency is applied at both ends of the Iur interface or at only one end. Table 159: Required number of SCTP associations in Iu and Iu-PC compared to a basic situation without network resiliency and Table 160: Required number of SCTP associations in Iur compared to a basic situation without network resiliency summarize the SCTP associations in the Iu, Iu-PC and Iur interfaces. Table 159 Required number of SCTP associations in Iu and Iu-PC compared to a basic situation without network resiliency C as e R e q u i r e d n u mb e r o f S C T P associations in RNC Required number of SCTP associations in CN NE RNC without network resiliency N N RNC with network resiliency 2N: N in PrPRNC, N in BkPRNC 2N Table 160 Required number of SCTP associations in Iur compared to a basic situation without network resiliency C as e Req ui r ed n umber of SCTP associations in RNC1 Required number of SCTP associations in RNC2 RNC1 without network resiliency, RNC2 without network resiliency N N RNC1 with network resiliency, RNC2 without network resiliency 2N: N in PrPRNC, N in BkPRNC 2N RNC1 without network resiliency, RNC2 with network resiliency 2N RNC1 with network resiliency, RNC2 with network resiliency 4N: 2N in PrPRNC, 2N in BkPRNC 2N:NinPrPRNC,Nin BkPRNC 4N: 2N in PrPRNC, 2N in BkPRNC Iu and Iur interface user plane (UP) configuration Proper routing between CN and BkPRNC must exist. The feature does not have an impact on the user plane (UP) configuration in CN or in neighboring logical RNCs. The BkPRNC can adapt the RNC’s source UP IP addresses from the PrRNC’s physical environment to its own physical environment. The IP mapping tables in the BkPRNC must be configured manually. All source UP IP addresses used on the PrPRNC must be mapped with at least one valid IP address on the BkPRNC, as shown in Table 161: Supported IP mapping relationships. 356 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 161 RNC solution features Supported IP mapping relationships I P ma p p i n g r e l a t i o n s h i p S ou rce UP IP selecti on 1:1 ThesourceIPofPrPRNCisreplacedwiththe source IP of BkPRNC n:1 ThesourceIPofPrPRNCisreplacedwiththe source IP of BkPRNC 1:n (only RAN3005 support) The source IP of PrPRNC is replaced with the source IP of BkPRNC with round robin mechanism 8.3.2.2.6 Planning management plane configuration Configuration of interface with OMS and NetAct It is recommended that BkPRNC is in the same NetAct regional cluster as the PrPRNCs. It allows to easier manage the logical RNC (RNC object) in Net Act. With this solution the same NetAct holds alarm and PM data of both physical RNCs. The alarm and PM history do not moves accidentally from one NetAct to another when making a redundancy switch from PrPRNC to BkPRNC or redundancy switchback to PrPRNC. The BkPRNC must be connected to a particular OMS, which may be different to the OMSs of the PrPRNCs. The BkPRNC uses its own OMS when there is no active RNCSRV in it. The BkPRNC uses the OMS of the logical RNC, when the related RNCSRV is active in the BkPRNC. The OMS configuration of the logical RNC is automatically synchronized from the PrPRNC NetAct does not need any new configuration due to the network resiliency of the RNC. 8.3.2.2.7 Planning transport network configuration The transport network configuration must be enhanced to guarantee the connection to the RNC after the redundancy switch for all NEs behind the Iu, Iu-PC, Iu-BC, Iur and Iub interfaces. The capacity of the transport network in the BkPRNC must be as high as in the PrPRNC in order to avoid performance problems after the redundancy switch. This requires care, particularly if BkPRNC is on a different site to the PrPRNC. IP connectivity can be verified by doing IP connectivity test in the BkPRNC. 8.3.2.2.8 Principles for NW operations with network resiliency Daily operation and maintenance • • • It is not recommended to change the RNW configuration, when the RNCSRV is active in BkPRNC. Since there is no backwards synchronization, the operator must reconfigure PrPRNC after redundancy switchback to obtain the required configuration. It is recommended to move the BkPRNC into LOADEDActivity mode and run IP connectivity test regularly to ensure that the transport network is working properly. It is recommended to perform redundancy switch and run each RNCSRV in BkPRNC regularly (for example, during night every now and then) to ensure that signaling connectivity and the BkPRNC’s SW image works properly. Checking the correctness of CP configuration DN09203161Issue:02 ©2016Nokia 357 RNC solution features WCDMA 16 Feature Descriptions and Instructions To check the CP configuration at Iu, Iu-PC, Iub, and Iur the user must perform a redundancy switch to BkPRNC and keep the RNCSRV active there for a while. Currently there is no existing solution to verify the signaling configuration in the background, without disturbing the network. The available IP connectivity test in the BkPRNC, verifies transport connectivity without checking the higher layers. 8.3.2.3 8.3.2.3.1 Operating principles Auto-adaptation in mcRNC Overview This feature allows to perform the auto-adaptation operation in both: base and backup build. In both cases the IP address and IP subnet mapping is required between PrPRNC and BkPRNC. PRNCs collect the found User Plane IP addresses and Iub Control Plane subnets to the mapping files which are managed with SCLI commands. The user maps PrPRNCs and BkPRNCs IP addresses and IP subnets manually to enable the system to choose for the logical interfaces: correct source IP address and IP subnet at BkPRNC. The mappings are managed per RNCSRV in BACKUP or LOADED mode. IP Auto-adaptation in base build The system is able to perform the IP Auto-adaptation in base build without system reset if the operation is enabled for RNCSRV and synchronization is scheduled. The operation is considerably faster than made in backup build. After completed synchronization of the concerned RNCSRV and during other resiliency-related operations are ongoing, the RNCSRV operation is added in task queue to wait for the IP Auto-adaptation. The queue can be interrogated to see the all the pending operations. The IP Auto-adaptation in base build cannot perform all of the possible configuration tasks related to RNCSRV and many of them must be done in backup build. IP Auto-adaptation in backup build The user is able to perform the operation also in backup build. If the IP Auto-adaptation is disabled, the user must switch the RNCSRV to LOADED state and trigger the operation manually. Some configuration require manual work and must be done at LOADED mode: • • • • • • 8.3.2.3.2 Configuring SIGTRAN's signaling Configuring IP addresses Configuring TWAMP Routing (partially) Enabling BFD (both in RNC and BTS) after resiliency switch Configuring IP address and IP subnet mappiing Operating and Maintaining overview Software operation and maintenance are necessary to ensure resiliency in the protected part of the network. It is essential to ensure that SW builds and configurations of PRNCs are up-to-date, and necessary IP connectivity exists. The main user interface utilized to manage the feature are text commands. With them you are able to fully manage the feature. Besides of text commands, the OMS Element Manager (OMS EM) supports most of functionalities related to the feature. 358 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features In addition to legacy functions, like alarm management and the RNW DB parameter management, the following operations are supported in OMS: • • • • • redundancy switch (RNC Service Activation and Forced RNC Service Activation) redundancy switchback (RNC Service activation in PrPRNC) enabling BACKUP Mode or LOADED Mode in BkPRNC deleting RNC Service configuration Data synchronization schedule configuration Moreover, you can use OMS EM to monitor the BkPRNC and the feature in general. In practice this means that feature-related objects like BKPRNC, RNCSRV and DATSYN can be managed in OMS EM. OMS EM allows to upload and download corresponding RNCSRV's IP plan when BkPRNC is in LOADED mode. When using OMS EM you cannot perform operations like: commissioning and preconfiguration, manual data synchronization, and IP connectivity test. For more information seeOMS documentation. 8.3.2.3.3 NetAct topology view Deployment and removal of the Topology View of PRNC objects in NetAct NetAct allows to present the Topology View of the PRNC objects with the RAN3226: NetAct Topology View to Network Resiliency of RNCfeature. It requires installing NetAct software license. After installation, the RAN3226: NetAct Topology View to Network Resiliency of RNC is always active. The topology view deployment processes automatically. The OMS collects the data required for deployment from a particular Physical RNC (PRNC). NetAct receives the data from the OMS to perform its desired functions in the variety of different user scenarios. The topology of a resilient network (configured PRNCs) is automatically visible on NetAct after upgrading the software of PRNC and OMS. NetAct Monitor tool automatically receives topology information on the defined protected PRNCs (PrPRNC), backup PRNCs (BkPRNC), and RNC objects. It displays them on the user's interface. According to OMS information, the Monitor tool (NetAct) updates its topology. New PRNC object will be seen in Monitor and CM tools (CM Editor, CM Operations Manager). NetAct automatically removes obsolete topology information related to the standard PRNCs after NetAct, OMS and RNCs have been upgraded to WCDMA17. NetAct operability for the resilient network The operator uses NetAct Monitor to launch Element Management operations for the protected PRNCs and backup PRNCs viewable on NetAct. The NetAct Topology View to Network Resiliency of RNCfeature allows the user RAN3226: to utilize NetAct for: • Displaying the alarmsrelated to the PRNC on the NetAct Monitor. • Uploading CM plan for PRNCs. Collecting HW inventoryinformation from the protected PRNCs, and backup PRNCs. NetAct CM tools (CM Editor) displays the HW inventory information. • Reporting alarms by NetAct DN09203161Issue:02 ©2016Nokia 359 RNC solution features WCDMA 16 Feature Descriptions and Instructions NetAct receives hardware and transport alarms from the protected PRNCs and backup PRNCs. When the PRNC detects a fault condition that requires notification to the operator, it displays the alarms on the user's interface. In case of hardware or transport failure, NetAct Monitor displays • • hardware and transport alarms againstthe corresponding protectedor backup PRNC alarms specific for the network resiliency of RNC, for the respective PRNC objects In case of radio network failure, detected in the active RNC service of a protected or backup PRNC, alarms are visible on NetAct Monitor against the RNC object. 8.3.2.3.4 Backup Physical RNC System management Backup Physical RNC System (BPS) management information, impacts and safety limitations. BPS concept overview The feature introduces a Backup Physical RNC System (BPS) containing one base build and up to 16 backup builds. All of the builds are in the same SW version (release and CD version) The BkPRNC is able to hold more than one BPS. A BPS which contains a running SW build is called a running BPS. The purpose of BPS fallback is similar to a single-build fallback, which the operator utilizes to create BPS backup for a recovery purpose. User's operations supported on BPS: • Show particular or all BPS information existing inthe system. • Create a particular BPS fallback, and inquire the BPS fallback progress. • Delete the BPS. • Upgrade the BPS. • Activate the BPS. At one time, the user is allowed to execute only one of the following operations: BPS fallback creation, BPS deletion, and BPS upgrade. Mutual impacts and exclusion for simultaneous BPS, and resilient operations If the user requests to start an operation, and a BPS operation is ongoing, the system accepts or rejects the requested operation execution according to the exclusion rule. Table 162 Resilient operation exclusion principle R e q u e s t e d o p e r at i o n O n go i n g B PS op e rat i on BPS F al lb ac k Service Creation x x x Service Deletion x x x Y x x x Downloading Basic adaptation 360 BP S del et io n (d el et e no n-BPS Upgrade default BPS) Y x ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 162 RNC solution features Resilient operation exclusion principle (Cont.) R e q ue s t e d o p e r ati o n O n go i n g B PS op e rat i on BPS F al lb ac k IPauto-adaptation x Pre-configuration x x Configurationdeletion ServiceActivation Servicedeactivation - BPS Fallback x x x Y Y BPS deletion(delete non-default BPS) BPS Upgrade x x - IPconnectivitytest BP S del et io n (d el et e no n-BPS Upgrade default BPS) x x x x - Y - x x x x x x x x Y The requested resiliency operation execution is allowed. x The requested resiliency operation execution is rejected. - Not applicable Resilient specific operation might be impacted by running BPS operation, thus the system needs to follow the exclusive rule to allow or deny BPS operation when resilient operation is ongoing: Table 163 Resiliency operationsimpact on BPS operations. Current RNCSRV status Idle Activi ty M ode B PS f al l bac k creation request Waitfor Synchronization Backup Y Y Creating Service Downloading x x x Backup - Active Loaded - Y x x x x x x - Wait for Synchronization x x x Active Loaded DN09203161Issue:02 BPS upgrade request Y Y Y Wait for Synchronization Backup Y Y Active Loaded BPS deletion request ©2016Nokia x - 361 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 163 Resiliency operationsimpact on BPS operations. (Cont.) Current RNCSRV status Loading RNC Service A c ti v i t y M o d e B PS f al l bac k creation request Wait for Synchronization Backup x Wait for Synchronization Backup x - Wait for Synchronization Y Backup Y - Wait for Synchronization - Backup - Active - Loaded x x Wait for Synchronization Backup x Loaded x Wait for Synchronization Backup x - Active Y x Y x x x x Active - Loaded x x Wait for Synchronization Backup x x x x x Active x x - Loaded 362 Y - Loaded Waiting x - Active IP auto adapting x - Loaded Testing IP connectivity x - Active Activating RNC service x - Loaded Build failure BPS upgrade request - Active Deleting service configuration BPS deletion request - ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 163 RNC solution features Resiliency operationsimpact on BPS operations. (Cont.) Current RNCSRV status Doing basic adaptation Activi ty M ode B PS f al l bac k creation request Wait for Synchronization Backup x x x BPS upgrade request x x Active x - Loaded Deleting Service BPS deletion request - Wait for Synchronization Backup x x x x x Active x - Loaded - Y The requested BPS operation execution is allowed. x The requested BPS operation execution is rejected. - Not applicable. BPS safety limitations Even though builds belong to one BPS, it is possible for the operator to execute a command for a as single-build build operation below: operation. It means that BPS can be impacted by a single• • Single-build switch (forexample during redundancy switch/switch backand load/unload) might cause an alarm3361 NE CONFIGURATION IS WRONG if a running build or a new, activated build is a backup build. A Single-build deletion request mightcause a deletion of a build belonging to a BPS without any warning. Safety limitation to prevent the listed problems: • • Single-build switch is forbidden, or mustbe confirmed if the running build or a new build is a backup build. For a list of exact rules see Table 164: Forbidden switch cases Legacy single-build deletion request is rejectedif a build that is going to be deleted belongs to a BPS. The operator must use a respective RNCSRV deletion command to delete an RNCSRV including the backup build. Table 164 Forbidden switch cases C u r r e n tr u n n i n gb u i l d Normal build (neither base nor backup) Basebuild Backup build DN09203161Issue:02 N e wb u i l d Backup build Backup Normal build ©2016Nokia R ul e Ask for confirmation Reject Ask for confirmation 363 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 164 Forbidden switch cases (Cont.) C u r r e n tr u n n i n gb u i l d N e wb u i l d R ul e Backupbuild Basebuild Reject Backupbuild Backupbuild Reject Related procedures Configuring GIVAXI/givClienton page 300 Deleting BPS fallback on page 447 Activating new BPS on BkPRNC (mcRNC) on page 442 Upgrading mcRNC SW builds and BPS on BkPRNCon page 439 Creating BPS fallbackon page 438 8.3.2.3.5 Interpreting of the system logs Table 198: RNC Resiliency Logscontains information helpful for interpreting logs: • • • • Test: type of performed test Description: detailed description of performed test with a list of possible statuses obtained Result: detailed description of possible statuses obtained Logs: log file name Table 165 Te s t RNC Resiliency Logs Descr ip ti on RNC Resiliency The Commit configuration test log records Note: RNC service This test adaptation and is done configuration in test results BkPRNC during in synchronization Backup or manual mode configuration only. commit phase. The test results fall into three classes: INCOMPLETE, R es u l t s • L og s INCOMPLETE: means MISSING or MISMATCH. g UNNECESSAR Y and COMPLETE. – – – – MISSING means that records exist in PrPRNC but do not exist in BkPRNC. MISMATCH means that records exist both in PrPRNC and BkPRNC,but parameters do not match. CURRENT means that IPBR/IPRO configurations exist on BkPRNC. EXPECTED means that PrPRNC IPBR/IPRO configurations adapt to configtest_rnc srv<RNCSRVID>.log BkPRNC according to IP mapping table. Auto-adaption requires complete IP mapping configuration. If there is log indicating 'NO IP-MAPPING' or 'INVALID IP-MAPPING', operator needs to check IP mapping configuration. 364 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 165 Te s t RNC solution features RNC Resiliency Logs (Cont.) Descr ip ti on R e su l t s • • unused in BkPRNC. UNNECESSARY IPBR/IPRO means that there is extra IPRO configuration in BkPRNC side comparing with PrPRNC. There is risk that later when a different IPRO is configured in PrPRNC. It may result in an inconsistent state in BkPRNC after synchronization. CURRENT and EXPECTED are same as previous explanations. COMPLETE: configuration items in BkPRNC are correct. g RNC Resiliency IPtestlog IP Test records system configuration Note: issues and IP This test connectivity is done status which are only in found during IP BkPRNC connectivity in testing. Test Loaded results are and classified as Active WARNING, modes. UNSUCCESS, IP Test PART cannot SUCCESS, be SUCCESS and triggered NOT TEST. in Backup mode. • RNC Resiliency Sync log Sync records RNC service adaptation and configuration test result in synchronization phase. Test results are classified as INCOMPLETE, • g DN09203161Issue:02 • • • • ©2016Nokia L og s Auto-adaption is calculated bases on IPBR, all the IPROs binding to same IPBR are only counted as 1. UNNECESSARY: records which exist in BkPRNC are not found in PrPRNC or records which is Note: If EXPECTED SPC is N/A it means that a SPC is found in RNW DB but corresponding configuration does not exist in platform. WARNING: configuration error found. UNSUCCESS: pinging from source to destination fails, all packets lost. PART SUCCESS:some packets lost, but connectivity is ok. Packet lost rate provided, 20 percent lost rate means 1 packet dropped(5 packets sent during ip test). SUCCESS: pinging from source to destination succeeds, no packet lost. NOT TEST: pinging has not been executed. iptest_rncsrv< RNCSRV-ID>.log INCOMPLETE: means MISSING or MISMATCH. configtest_rnc srv<RNCSRVID>.log – – MISSING means that records exist in PrPRNC but do not exist in BkPRNC. MISMATCH means that records exist both in PrPRNC and BkPRNC,but parameters do not match. 365 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 165 RNC Resiliency Logs (Cont.) Te s t g Note: This test is done in BkPRNC in Descr ip ti on R es u l t s UNNECESSAR Y and COMPLETE. – – Backup mode only. L og s CURRENT means that IPBR/IPRO configurations exist on BkPRNC. EXPECTED means that PrPRNC IPBR/IPRO configurations adapt to BkPRNC table. according to IP mapping • • Auto-adaption requires complete IP mapping configuration. If there is log indicating 'NO IP-MAPPING' or 'INVALID IP-MAPPING', operator needs to check IP mapping configuration. Auto-adaption is calculated bases on IPBR, all the IPROs binding to same IPBR are only counted as 1. UNNECESSARY: records which exist in BkPRNC are not found in PrPRNC or records which is unused in BkPRNC. UNNECESSARY IPBR/IPRO means that there is extra IPRO configuration in BkPRNC side comparing with PrPRNC. There is risk that later when a different IPRO is configured in PrPRNC. It may result in an inconsistent state in BkPRNC after synchronization. CURRENT and EXPECTED are same as previous explanations. COMPLETE: configuration items in BkPRNC are okay. g Note: If EXPECTED SPC is N/A it means that a SPC is found in RNW DB but corresponding configuration does not exist in platform. The directories which store the logs are available with the following commands: show file content local /log/configtest_rncsrv223.log and show file content local /log/iptest_rncsrv223.log For more information, refer to SCLI Commands. 8.3.2.3.6 8.3.2.3.6.1 Redundancy switch Activity model Figure 85: Activity modelshows available Activity Modes of BkPRNC and PrPRNC and transitions between them. 366 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Figure 61 RNC solution features Activity model Transitions in Backup PRNC Waiting for synchronization System restart 5 Transitions in protected PRNC Active 6 1 Active 21 21 7 3 Backup 4 Loaded Loaded 1. RNCSRV Activation. 2. RNCSRV Inactivation; 3GPP interfaces are blocked. 3. RNCSRV is set from BACKUP mode to LOADED mode; a backup build is loaded to memory for configuration and testing. 4. In BkPRNC, the base configuration package is loaded to memory. 5. RNCSRV configuration has been deleted, or the conversion in SW upgrade has failed. 6. Initial synchronization has been completed. 7. Another RNCSRV is loaded to memory. g 8.3.2.3.6.2 Note: Synchronization is done at Backup mode, configuration is done at LOADED mode Use cases Overview of possible use cases Table 166 Use cases U s ec a s e D e s cr i p t i o n Normal redundancy switch Performing normal redundancy switch from PrPRNC to BkPRNC Forced redundancy switch Forced redundancy switch Performing forced redundancy switch from PrPRNC to BkPRNC Changing RNCSRV-X to RNCSRV-Z at BkPRNC Redundancy Switchback System recovery from redundancy conflict w In stru cti on Normal redundancy switch Changing any RNCSRV to RNCSRV-Z at BkPRNC - Redundancy Switchback Redundancy switchback System recovery from redundancy conflict Redundancy conflict NOTICE: In the following simplified examples RNCSRV, PrPRNC and BkPRNC with fixed ID numbers show the NE behavior in different use cases. Normal redundancy switch Preconditions • • DN09203161Issue:02 Resiliency association betweenPrPRNC and BkPRNC was created. RNC-cl interface is established. ©2016Nokia 367 RNC solution features WCDMA 16 Feature Descriptions and Instructions BkPRNC is in BACKUP mode. • 1. Redundancy switch is executed at BkPRNC (using text commands when directly connected to RNC or with OMS GUI). 2. After self-validation BkPRNC restarts. 3. RNCSRV-X switches to LOADED mode. 4. PrPRNC wants to establish a connection and BkPRNC acknowledges it. 5. Once BkPRNC started and RNC-cl is up, BkPRNC orders PrPRNC to deactivate its RNCSRV. 6. After getting acknowledgment from PrPRNC, BkPRNC activates the RNCSRV-X. g Note: Redundancy switch might be executed also if BkPRNC-Y has RNCSRV-X already in LOADED mode. Figure 62 Normal redundancy switch PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X Redundancy switch RNCSRV-X 1 Validation 2 RESET 3 RNCSRV-X to LOADED mode RNC-cl establishment/ acknowledgement 4 Deactivate 5 Deactivating RNCSRV-X to LOADED mode OK 6 RNCSRV-X to ACTIVE mode ALARM; RNCSRV ACTIVATION Forced redundancy switch g 368 Note: In forced redundancy switch BkPRNC does not try to shutdown the PrPRNC even though RNC-cl interface is up and running. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Preconditions RNC-cl interface is established or not working. Resiliency association betweenPrPRNC and BkPRNC was created. BkPRNC is in BACKUP mode. • • • 1. Normal redundancy switch fails, which is indicated by no reply from PrPRNC or PrPRNC replies with error. 2. a) BkPRNC does not recognize the verify statusthe of PrPRNC, whilst RNCSRV-X disabled or enabled. User must status and isolate PrPRNC.is b) Timer expires and alarm is raised. 3. Forced redundancy switch is executed. Figure 63 Forced redundancy switch PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X Redundancy switch RNCSRV-X Validation RESET 1 RNCSRV-X to LOADED mode Deactivate 2a No-reply timer expires 2b BkPRNC does not recongnise the status of PrPRNC, whilst RNCSRV-X is disabled or enabled. User must verify the status and isolate PrPRNC. ALARM: Deactivation failed 3 Forced redundancy switch RNCSRV-X Validation RNCSRV-X to ACTIVE mode ALARM; RNCSRV ACTIVATION Changing any RNCSRV to RNCSRV-Z at BkPRNC Preconditions DN09203161Issue:02 ©2016Nokia 369 RNC solution features WCDMA 16 Feature Descriptions and Instructions RNC-cl interface is established. Redundancy switch wasexecuted some time ago. BkPRNC-Y is running RNCSRVX. PrPRNC-X has no active RNCSRV. Request reported for BkPRNC-Y running RNCSRV-Z instead of RNCSRV-X. • • • 1. Command BkPRNC-Y from the ACTIVE to the LOADED mode. 2. Load RNCSRV-Z. 3. Execute redundancy switch. 4. After validation, BkPRNC-Y orders PrPRNC-Z to deactivate its service. 5. After getting acknowledgment, BkPRNC-Y activates the RNCSRV-Z. Figure 64 Changing any RNCSRV to RNCSRV-Z at BkPRNC BkPRNC-Y RNCSRV-X RNCSRV-Z PrPRNC-X RNCSRV-X BkPRNC-Z RNCSRV-Z RNCSRV-X in Active mode Deactivate RNCSRV 1 RNCSRV-X in LOADED mode Load RNCSRV-Z 2 RESET RNCSRV-Z in LOADED mode Redundancy switch RNCSRV-Z 3 Deactivate 4 Deactivating RNCSRV-Z to LOADED mode OK 5 RNCSRV-Z to ACTIVE mode ALARM; RNCSRV ACTIVATION Redundancy Switchback Preconditions • 370 Redundancy switch was executed. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features PrPRNC was restored (HW, SW and configuration). PrPRNC is in LOADED mode RNC-cl interface is established. • • 1. Redundancy switchback is triggered at PrPRNC. 2. After command validation, PrPRNC orders BkPRNC to deactivate RNCSRV-X. 3. After getting acknowledgment PrPRNC activates RNCSRV-X and sets an alarm. BkPRNC stays in LOADED mode. 4. Verification of PrPRNC proper behavior after switchback. Figure 65 Redundancy Switchback PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X RNCSRV-X in LOADED mode 1 Redundancy switchback Validation 2 Deactivate Deactivating RNCSRV-X to LOADED mode 3 OK RNCSRV-X to ACTIVE mode 4a ALARM; RNCSRV ACTIVATION System recovery from redundancy conflict Preconditions • • • 1. 2. 3. 4. DN09203161Issue:02 Forced redundancy switch has been executed. BkPRNC-Y isrunning RNCSRV-X. PrPRNC-X has been just powered off. PrPRNC-X has not been isolated. RNC-cl is established. PrPRNC is started and it runs RNCSRV-X. PrPRNC establishes the RNC-cl and performs ”activity mode query”. When replied, PrPRNC detects the redundancy conflict PrPRNC shuts down the interfaces and remains in the LOADED mode. The redundancy conflict is cleared. ©2016Nokia 371 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 66 1 System recovery from redundancy conflict PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X RNCSRV-X to ACTIVE mode RNCSRV-X in ACTIVE mode RNC-cl establishment 2 Activity mode query 3 4 Redundancy conflict detected Deactivating RNCSRV-X to LOADED mode 8.3.2.3.6.3 Detecting redundancy switch necessity The user considers redundancy switch in the case of: • • • planning and performing any maintenance actions whichmay cause a break in delivering controller's services catastrophe in the area where the controller's site isplaced occurrence of a breakdown precluding animmediate restoration ofthe controller Although there is no automatic detection or triggering mechanism for redundancy switch, some existing symptoms like alarms in peer NEs, drop of KPIs or even loss of O&M connection inform the user about the necessity of the redundancy switch execution. g 8.3.2.3.6.4 Note: Note that if the O&M connection to PrPRNC is interrupted and forced redundancy switch was performed, there is a danger of redundancy conflict unless PrPRNC had been isolated physically. Comparison of prepared and unprepared redundancy switch The redundancy switch can be considered either as a prepared redundancy switch or as an unprepared redundancy switch. The difference between these two lies in the activity mode the BkPRNC is in when redundancy switch is being executed. The unprepared redundancy switch takes place when redundancy switch is executed while BkPRNC is in backup mode (for example base build SW is in memory). After redundancy switch command, a system reset takes place and the wanted RNCSRV is activated. In prepared redundancy switch, the RNCSRV you want to activate is already in LOADED mode (for example the respective backup build SW is already in memory) when the redundancy switch is executed. 372 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features The benefit of prepared redundancy switch is that no system reset, which takes several minutes, is needed when command is being executed because the correct sW is already in RNC’s memory and the RNCSRV is faster back online. Both the prepared and unprepared redundancy switch can be done in normal or forced mode. 8.3.2.3.6.5 Redundancy conflict Origin of redundancy conflict Redundancy conflict is an undesired situation where both PrPRNC and BkPRNC are online with same RNCSRV active. This leads to a situation where both the PrPRNC and BkPRNC attempt to establish an Iub control plane connection with BTS. Because only one PRNC has BTSs under control, the PRNC which does not control the BTSs will fail with the call setup attempts received from CN. This means, that roughly half of the connection setup attempts srcinated in CN will fail. In the result, bad end user experience arise, as well as KPIs which measure Core Network decrease. Thus it is crucial to solve the redundancy conflict quickly. Redundancy conflict emerges if PrPRNC is restarted accidentally after forced redundancy switch operation. The reason is that the PrPRNC which becomes active after restart and has not been isolated properly, is not aware of the previous redundancy switch and goes online in the network. Thus the best way to prevent a redundancy conflict is to isolate the PrPRNC after redundancy switch. Avoiding and solving redundancy conflict When PrPRNC restarts and becomes active, it establishes the RNC-cl O&M interface and performs activity mode query towards BkPRNC. If BkPRNC is active, the PrPRNC switches to LOADED mode, which means it shuts down the interfaces and goes offline. If there is RNC-cl O&M interface, the system is able to recover the redundancy conflict in few minutes after the RNC-cl O&M interface establishment. Without the interface BkPRNC does not reply to the activity mode query and it is impossible to resolve the redundancy conflict automatically. Another redundancy conflict situation is when both PRNCs try to establish the Iub control plane (CP) connections to BTS. If BTS has working control plane connection, it rejects the CP establishment attempt from colliding PRNC. Redundancy conflict in NetAct Redundancy conflict is problematic for NetAct, because NetAct cannot determine which of the connected RNCs is the correct one. In redundancy conflict situation, all RNC management operations and events in NetAct are related to the connected RNC, and not necessarily to the RNC to which the WBTSs are connected to. If redundancy conflict takes place there will be two PRNCs online with same RNCSRV active. In redundancy conflict the second PRNC reports the RNC to the NetAct topology without knowing the same RNCSRV is already active in another PRNC. As NetAct topology has only one instance of the RNC, the latter RNC will replace the srcinal RNC in NetAct topology. In case the latter RNC is activated accidentally, only this one will be visible in the NetAct but not the RNC which has the control of the related WBTSs. The ActivePRNC parameter of the RNC object in NetAct can be used to identify which PRNC is actually connected to NetAct. BTS behavior in a redundancy conflict DN09203161Issue:02 ©2016Nokia 373 RNC solution features WCDMA 16 Feature Descriptions and Instructions A BTS is able to tolerate a redundancy conflict. It operates in a way that both the Iub control plane and O&M connections are towards the same PRNC. If a BTS has an existing Iub control plane connection to PRNC (for example to PrPRNC) and another PRNC (for example a BkPRNC) has been started accidentally, the BTS rejects the control plane connection establishment from the BkPRNC. The O&M connection follows the control plane connection in order to have them terminated in the same PRNC. If no PRNC is online, the BTS has neither an O&M nor a CP connection. As soon as the PRNC establishes the CP connection, the BTS establishes the O&M connection to the same PRNC. When the PrPRNC is not isolated properly after the redundancy switch and is able to establish a control plane connection to some of the BTSs, those BTSs are beyond the BkPRNC’s control. Therefore, it is crucial to isolate the PrPRNC after the redundancy switch. 8.3.2.3.7 Network Resiliency operations in OMS Element Manager (OMS EM) Network Resiliency operations available in the OMS EM In the OMS EM the operator can perform the following Network Resiliency operations: • Showing RNW Topology RNC Service Activation RNC Service Force Activation RNC Service Deactivation Loading RNC Service for Configuration • Unloading RNC Service • Deleting RNC Service Backup Configuration • • • • The user performs the operations on the respective RNCSRV either on PrPRNC or BkPRNC from RNC Resiliency menu. • RNC Resiliency ► (The following options are dependent on the PRNC activity mode.) – – – – – – Activate (available forboth Protected PRNC and Backup PRNC) Force Activation (availablefor both Protected PRNC and Backup PRNC) Deactivate (available forboth Protected PRNC and Backup PRNC) Load for Configuration (available only forBackup PRNC with activity mode "Backup") Unload (available only for Backup PRNC) Delete Backup Configuration (available onlyfor Backup PRNC with activity mode "Backup") RNC Resiliency menu Figure 67: RNC Resiliency menu for BkPRNCand Figure 68: RNC Resiliency menu for PrPRNC presents RNC resiliency menus according to RNW object in OMS EM 374 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Figure 67 RNC Resiliency menu for BkPRNC Figure 68 RNC Resiliency menu for PrPRNC Table 167 RNC Resiliency operations menu O p e rat i on D e sc r i p t i on Activate Activates RNCSRV for particular PrPRNC Force Activation Forces the activation of RNCSRV for particular PrPRNC Deactivate Deactivates RNCSRV for particular PrPRNC Load for Configuration Loads RNC Service for configuration Unload Unloads the RNC Service from configuration Delete Backup Configuration Deletes RNC Service backup R e p r e s e n t i n gi c o n configuration PRNC visibility toggle view The user is able to toggle between PRNC visibility mode ON/OFF. This can be done by matching Do not show PRNC objects at topology listin OMS EM Settings Panel as shown in the Figure 69: Settings panel. DN09203161Issue:02 ©2016Nokia 375 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 69 Settings panel RNW Topology view Topology Browser for RNW topology of RNC Service is a special view designed solely for the purpose of RNC Resiliency feature. It resembles ordinary Topology Browser, but can be displayed only for RNC Services with ActivityMode parameter set to Loaded. This view is designed for the convenience of user who wants to check and/or modify RNW topology which is stored at Backup PRNC, awaiting activation in case of emergency problems or maintenance activities. This view may be also used to view and edit RNW plan at Protected PRNC which at particular moment does not host active RNC Service because its RNC Service was moved to Backup PRNC. The Figure 70: Show RNW Topology context menushows action available for RNCSRV object with ActivityMode parameter set to Loaded (which is indicated using L character at RNCSRV object’s icon). 376 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Figure 70 RNC solution features Show RNW Topology context menu After the user chooses Show RNW Topology option, the OMS displays RNW topology structure of certain RNC Service in a separate tab. Using Element Manager in OMSshows impacts from the feature on OMS Element Manager. 8.3.2.4 Table 168 Network Resiliency related terms Descriptions of feature-related terms Te r m D e s cr i p t i o n s Adaptation Replacing the local information of PrPRNC by local information of BkPRNC. Auto-adaptation Adaptation done automatically according to mapping tables configured by the user. Automatic procedure of autoadaptation The sequence of auto-adaptations of all BkPRNC RNCSRVs one after the other. Backup build A build that BkPRNC runs when certain RNC service was selected for operation. t DN09203161Issue:02 Tip: See also: Base build. ©2016Nokia 377 RNC solution features Table 168 WCDMA 16 Feature Descriptions and Instructions Descriptions of feature-related terms (Cont.) Te r m Backup configuration D e s cr i p t i o n s Configuration package of a backup build. Backup configuration consists of global part that is copied from PrPRNC and local part that is configured by operator using text commands or OMS EM. t Base build A build that BkPRNC runs when no RNC service has been selected for operation. t Base configuration Tip: See also: Base configuration, Preconfiguring Tip: See also: Backup build. Configuration package of the base build. t Tip: See also: Backup configuration. BkPRNC Backup PRNC - PRNC that can back up the RNC services of up to 16 PrPRNCs. BPS Backup Physical RNC System. One BPS contains one base build and up to 16 backup builds. All of the builds are in the same SW version (release and CD version) BTS(WBTS) WCDMABTS BTSOM BTS O&M application protocol - the protocol used in RNC O&M I/F, BTS O&M I/F and RNC-cl O&M I/F. BTS O&M I/F BTS O&M interface - O&M interface between RNC and BTS, using BTSOM as the protocol. t Tip: See also RNC O&M I/F and RNC-cl O&M I/F. BTSSM BTSsitemanager Build Collection of programs and files performing required functions of a system. BkPRNC has a base build for the PRNC and a backup build per each related PrPRNC. In mcRNC build consists of configuration data and SW image. Configuration (package) The whole configuration of a build, which does not contain the SW image. t Tip: See also: Build. Configuration committing A command which tells to the system that the user configuration is done and is ready for configuration adaptation and integrity check. Conversion Converting a configuration package from old SW build to new SW build. g Note: Conversion is not particularly related to RNC resiliency. Conversion is done at any SW upgrade, with or without resiliency. LRNC Logical RNC - RNC as defined by 3GPP. See also PRNC, RNC, RNC service. In standard system, LRNC is 1-1 with RNC and PRNC. In RAN3005, LRNC is 1-1 with RNC but 1-2 with PRNC. mcRNC Multicontroller RNC - RNC with BCN HW 378 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 168 RNC solution features Descriptions of feature-related terms (Cont.) Te r m D e s cr i p t i o n s • HW: 2-8 BCN modules that have Octeon processors. • OS: Linux or Simple executive • Platform: FlexiPlatform + IL (IPA Light) NetAct Nokia product for network management OMS O&MserverforRNC. Object configuration Configuration of the local part of a backup configuration, which includes the adaptation rules. Operator configure required objects any time after first synchronization but before activating the RNC service. A manual configuration step must be done when RNCSRV is created in BkPRNC, and at certain modifications. PRNC Physical RNC - RNC HW and SW. This term is introduced because BkPRNC cannot be called as a RNC. It does not run RNC service but waits to be switched on in case of PrPRNC outage. t Tip: See also LRNC, RNC, RNC service. PrPRNC Protected RNC - PRNC whose RNC service has a backup in a BkPRNC Redundancy conflict The undesirable situation where certain RNC is active in more than one PRNC simultaneously. Redundancy switch Switch of (activity of) certain RNC from PrPRNC to BkPRNC. Two redundancy types can be distinguished: • • Prepared redundancy switch: redundancy switch where the activating RNCSRV has been raised to LOADED mode before commanding the switch. Unprepared redundancy switch: redundancy switch where the activating RNCSRV not been raised LOADED mode before commanding the switch. Redundancy switchback Switch of (activity of) certain RNC from BkPRNC to PrPRNC. RNC Common meaning: Radio network controller. In RNC pool context also: Logical functionality that can run simultaneously as an RNC service in a PRNC. RNC activity mode Defines the state in which the RNCSRV is. Values are: waiting for synchronization, backup, loaded and active. RNC area Geographical area covered by the BTSs and cells that the RNC controls. RNC-cl O&M I/F RNC cluster O&M interface (Informally Cluster O&M interface) - O&M interface between two RNCs, using BTSOM as the protocol. t RNC O&M I/F RNC O&M interface - O&M interface between OMS and RNC, using BTSOM as the protocol. t RNC resiliency group DN09203161Issue:02 Tip: See also BTS O&M I/F and RNC O&M I/F. Tip: See also BTS O&M I/F and RNC-cl O&M I/F. A BkPRNC and all the PrPRNCs protected by it. ©2016Nokia 379 RNC solution features Table 168 WCDMA 16 Feature Descriptions and Instructions Descriptions of feature-related terms (Cont.) Te r m RNC service (RNCSRV) D e s cr i p t i o n s The instance of an RNC in certain PRNC. t RNCSRV activation / deactivation Tip: See also LRNC, PRNC, RNC. Transition between different RNC modes which can be a separate operation or a phase of redundancy switch or switchback. • • RNCSERV activation refers to RNC mode changed from LOADED to ACTIVE RNCSERV deactivation refers to RNC mode changed from ACTIVE to LOADED Service status Defines what the BkPRNC is actually doing. This is useful with long lasting operations. Some values are: Idle, creating RNC service, synchronizing data. StPRNC Standard PRNC - PRNC that does not participate in RNC resiliency. Synchronization Automatic fetching of configuration package of certain RNC service from corresponding PrPRNC and adaptation to BkPRNC according to adaptation rules. 8.3.2.5 Table 169 Miscellaneous notes Limitations L i mi t e da r e a Network and network element management tools D e s c r i p t i o no ft h el i m i t a t i o n • • • Software management • BkPRNC is not visible in NetAct as individual RNC object if RNCSRV is not active in BkPRNC. In this case, the status of BkPRNC is visible in NetAct through parameters of RNC object of PrPRNC. When RNCSRV is active, BkPRNC takes the role of PrPRNC in NetAct. This feature can be managed in NetAct using the optional RAN3226: NetAct Topology View to Network Resiliency of RNC feature. Do not to execute RNW or IP plan uploads or downloads at PrPRNC during synchronization because of high risk of plan operation failure. Do not execute synchronization when planned operation is ongoing because of risk of synchronization failure. The failure or success of the operation depends on the phase of other ongoing operation. TRIAL configuration TRIAL configuration is a standard upgrade method applicable only when updated PrPRNC's RNCSRV is in ACTIVE mode. Nevertheless, there are some restrictions related to this method: 1. During TRIAL configuration resiliency relevant operation are rejected. 2. When RNCSRV is in LOADED mode, any TRIAL relevant operation is rejected. g 380 Note: TRIAL is strongly forbidden in BkPRNC. Because BkPRNC operates after the user performed redundancy switch, there is usually no active RNCSRV. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 8.3.3 RNC solution features RAN3005 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature introduces a new RNC-cl O&M interface. Impact on network and network element management tools This feature can be managed in NetAct using the optionalRAN3226: NetAct Topology View to Network Resiliency of RNC feature. See RAN3226: NetAct Topology View to Network Resiliency of RNC and NetAct topology view for more information. This feature introduces a new RNW object called PRNC, which represents PrPRNC or BkPRNC. The object can be seen in OMS EM regardless of whether the feature is activated or not. The BkPRNC object can be seen in NetAct only after RAN3226: NetAct Topology View to Network Resiliency of RNChas been activated. Figure 71 PrPRNC icon Figure 72 BkPRNC icon This feature impacts network management or network element management tools as described in Miscellaneous notes This feature can be managed in NetAct using the optional RAN3226: NetAct Topology View to Network Resiliency of RNC feature. See RAN3226: NetAct Topology View to Network Resiliency of RNC and NetAct topology view for more information. This feature introduces a new RNW object called PRNC, which represents PrPRNC or BkPRNC. The object can be seen in OMS EM regardless of whether the feature is activated or not. The BkPRNC object can be seen in NetAct only after RAN3226: NetAct Topology View to Network Resiliency of RNChas been activated. Figure 73 PrPRNC icon Figure 74 BkPRNC icon This feature impacts network management or network element management tools as described in Miscellaneous notes Impact on system performance and capacity This feature impacts system performance and capacity as follows: • • DN09203161Issue:02 For every 1-16 protected controllers, at least onebackup BkPRNC is required, with the highest configuration (the amount of BkPRNCs depends on the required redundancy level). Transport links between BTSs under PrPRNCs and BkPRNC and between BkPRNC and core or other controllers must be sufficient to carry whole traffic ©2016Nokia 381 RNC solution features WCDMA 16 Feature Descriptions and Instructions The user must install the following capacity licenses in BkPRNC: • • • • Iub throughput 1 Mbit/s license capacity that definesthe maximum PS downlink Iub throughput. The unit used is Mbit/s. AMR capacity 1 Erl license capacity thatdefines the maximum number of simultaneous AMR radio access bearers. Carrier connectivity license capacitythat defines the maximum number of cells that can be unlocked in the RNC. Signaling capacity license capacity thatdefines the maximum signaling capacity usage in kBHCA (relevant only for mcRNC HW Rel.2) Capacity licenses must be included in data synchronization between PrPRNC and BkPRNC 8.3.4 RAN3005 Reference data Requirements Table 170 RAN3005 hardware and software requirements RAS I PA - R N C mc R N C WCDMA 16 Available in mcRNC16 earlier release OMS NetAct WCDMA OMS16 NetAct 16.2 MS C Support not required Flexi Multiradio BTS WN9.1 S GSN Support not required Flexi Flexi Lite Multiradio 10 BTS BTS WN9.1 MGW Support not required WL9.1 UE Support not required This feature requires Multicontroller RNC HW Rel.2 Alarms Table 171 New alarms A l a r mI D A l a r mn a me Schedule problem 3367 RNC RESILIENCY SYNCHRONIZATION TOO OLD Configuration problem Operation problems and notices 3362 RNC SERVICE OVER 24h IN LOADED MODE 3361 NE CONFIGURATION IS WRONG Table 172 A l a r mI D 821 Related existing alarms A l a r mn a m e OMS SWITCHOVER HAS BEEN PERFORMED 3295 LICENCE CAPACITY EXCEEDED 3360 LICENSE NOT READY Measurements and counters 382 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 173 New parameters introduced by RAN3005 F u l lN am e A b b r e v i a t e dn am e ConnectionRetryCounter PRNC OMS backup IP Address OMSBackupIpAddress OMS IP Address OMSIpAddress PRNC PRNC Physical RNC Change Origin PRNCChangeOrigin PRNC Physical RNC IPv4 Address PRNCIP4Address PRNC Physical RNC Identifier PRNCId PRNC Physical RNC Mode PRNCMode PRNC Physical RNC name PRNCName PRNC PRNC Client TLS Mode PrncClientTLSMode PRNC Restart R eason RestartReason PRNC Secondary OMS IP address SecOMSIpAddress Serving OMS ServingOMS PRNC PRNC Serving OMS Admin setting ServingOMSAdminSetting PRNC Serving OMS Switchover Request ServingOMSSwoRequest Activity Mode ActivityMode PRNC PRNC/RNCSRV RNC service Change Origin RNCSRVChangeOrigin PRNC/RNCSRV RNC SERVICE Identifier RNCSRVId PRNC/RNCSRV RNC service status DN09203161Issue:02 M a n a g e do b j e c t OAM Connection Establishment Retry Counter ServiceStatus PRNC/RNCSRV Automatically Triggered Operations AutomTriggOper PRNC/RNCSRV/DATSYN Backup completeness of the backup BackupCompleteness PRNC/RNCSRV/DATSYN Backup update Time for RNC configured data BackupUpdateTime PRNC/RNCSRV/DATSYN ©2016Nokia 383 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 173 New parameters introduced by RAN3005 (Cont.) F u l lN am e A b b r e v i a t e dn a m e Data synchronization Change Origin DATSYNChangeOrigin PRNC/RNCSRV/DATSYN Data Synchronization identifier DATSYNId PRNC/RNCSRV/DATSYN Day of the week for periodic data synchronization DataSyncDays PRNC/RNCSRV/DATSYN Time of the day for periodic data synchronization hours DataSyncHours PRNC/RNCSRV/DATSYN Time of the day for periodic data synchronization minutes DataSyncMinutes PRNC/RNCSRV/DATSYN Data synchronization state DataSynchState PRNC/RNCSRV/DATSYN RNC cluster O&M interface link status RNCClusterOMLnkState PRNC/RNCSRV/DATSYN Backup PRNC current Activity Mode ActivityMode RNC/BKPRNC Alarm status at backup PRNC AlarmStatus RNC/BKPRNC BKPRNC Change Origin BKPRNCChangeOrigin RNC/BKPRNC Backup Physical RNC Identifier BKPRNCId RNC/BKPRNC Backup PRNC client TLS Mode for RNC cl O&M link BKPRNCTLSClientMode RNC/BKPRNC Backup RNC IPv4 Address used for establishing RNC cluster O&M interface BackUpRNCIP4Address RNC/BKPRNC Configuration completeness at backup PRNC BackupCompleteness RNC/BKPRNC Backup update time at BackupUpdateTime RNC/BKPRNC backup PRNC Backup PRNC name PRNCName RNC/BKPRNC RNC cluster O&M interface link status RNCClusterOMLnkState RNC/BKPRNC Backup PRNC unknown status UnknownStatus RNC/BKPRNC Active Physical RNC 384 M a n a g e do b j e c t ActivePRNC ©2016Nokia RNC DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 173 RNC solution features New parameters introduced by RAN3005 (Cont.) F u l lN am e A b b r e v i a t e dn am e OMS IP Address OMSIpAddress RNC RNC Secondary OMS IP address SecOMSIpAddress Serving OMS Admin setting ServingOMSAdminSetting RNC Serving OMS Switchover Request ServingOMSSwoRequest OAM Connection Establishment Retry Counter ConnectionRetryCounter RNC RNC Client TLS Mode Table 174 RncClientTLSMode RNC RNC Parameters modified by RAN3005 F u l lN am e A b b r e v i a t e dn am e M a n a g e do b j e c t RNC Identifier RNCId RNC RNC Options RNCOptions RNC Table 175 BTS Parameters F u l ln a me A b b r e v i a t e dn am e M a n a g e do b j e c t Additional RNC configuration structure addRncConfig TMPAR Currently used far end SCTP tunnel IP address currentSctpIpAddress TMPAR Far End SCTP Subnet IP Address farEndSctpSubnetIpAddress TMPAR Far End SCTP Subnet Mask g M a n a g e do b j e c t farEndSctpSubnetMask TMPAR Note: Far End SCTP Subnet IP Address and Far End SCTP Subnet Mask are placed under Backup RNC configuration in BTS Site Manager. Sales information Table 176 RAN3005 Sales information BS W/ASW L i ce n s e c on tr ol i n n e t w or k Activated by default element ASW 8.3.5 RNC LK No Activating RAN3005: Network Resiliency for mcRNC Purpose This chapter provides procedures on how to activateRAN3005: Network Resiliency for mcRNC feature. Assumed and expected network plan is shown in the Figure 75: Network transport plan. DN09203161Issue:02 ©2016Nokia 385 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 75 Network transport plan OMS 10.69.44.254 OMS O&M interface connection PrPRNC-223 BkPRNC-200 O&M RNCId-223 RNCId-200 RNC Cluster O&M interface SSH IP: 10.43.51.226/32 role oms: 10.43.51.234/32 role btsom: 10.43.51.235/32 SSH IP: 10.43.52.226/32 role oms: 10.43.52.234/32 role btsom: 10.43.52.235/32 in standby for backup service activation 8.3.5.1 8.3.5.1.1 Enlarging QNDRBD Modifying the VG_System LDAP configuration. Before you start Ensure you have root login credentials. Log in as a root. Procedure 1 Confirm that both CFPUs are running correctly. Refer to SCLI commands: Step example show has state managed-object /CFPU-* Step result CFPU-0@RNC-207 [2015-01-19 09:46:21 +0800] OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE PROCEDURAL DYNAMIC /CFPU-0 UNLOCKED ENABLED ACTIVE /CFPU-1 UNLOCKED ENABLED ACTIVE - 386 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 2 RNC solution features Confirm that the LDAP servers are running correctly. Refer to SC LI commands: Step example show has state managed-object /CFPU-*/FSDirectoryServer Step result CFPU-0@RNC-207 [2015-01-19 09:48:49 +0800] OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE DYNAMIC /CFPU-0/FSDirectoryServer UNLOCKED ENABLED ACTIVE ACTIVE /CFPU-1/FSDirectoryServer UNLOCKED ENABLED IDLE COLDSTANDBY - 3 PROCEDURAL NOTINITIALIZED Modify the VG_System LDAP configuration. Step example #/opt/nsn/SS_ILCommon/bin/enlargeQNDRBD.01.modify_LDAP.sh Step result This command will prompt the following printout: ********************* WARNING ******************** This script will modify LDAP partition 3 configurable size to 50494 MB ********************* WARNING ******************** Are you sure you want to proceed? [Y/n]: y<ENTER> The operation is successful if this printout occurred. Modify VG_System LDAP configuration successfully Please refer to QNDRBD enlarge guide to synchronize hard disk 8.3.5.1.2 Re-initialize hard disk to enlarge VG_System manually Procedure for initializing the disk in both controller modules to enlarge VG_System manually. Before you start Ensure logging in as root authority. g DN09203161Issue:02 Note: The <node_name> indicates the node which is the peer to the one the user is currently logged into. When you log into CFPU-0, the <node_name> is CFPU-1 respectively, and vice verse. During the lock and unlock procedure, wait for the card to come up. The RNC with a larger configuration is more time-consuming. ©2016Nokia 387 RNC solution features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Lock CFPU: > set has lock force managed-object /<node_name> Step example > set has lock force managed-object /CFPU-1 Step result /CFPU-1 locked successfully 2 Power off node: > set has power off managed-object /<node_name> Step example > set has power off managed-object /CFPU-1 Step result /CFPU-1 is powered OFF successfully 3 Enable network boot for the node. Sub-steps a) Log in as root: Step example > set user username root b) Power-up the node. Wait a few seconds before proceeding to the next step. hwcli -np on <node_name> Step example hwcli -np on CFPU-1 Step result Powering on CFPU-1 [ok] c) Reset the node: hwcli -nr -B 3 <node_name> 388 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step example hwcli -nr -B 3 CFPU-1 Step result Resetting CFPU-1 [ok] g Note: The CFPU takes some time to reboot and the availability can be checked by logging through the SSH. d) Exit root: Step example exit 4 Disable watchdog: ssh <node_name> \ wdctl -d exit Step example ssh CFPU-1 \ wdctl -d exit g Note: To disable the watchdog on the node through SSH, enter the following command. If connecting to the node by SSH failed, you should wait for about three minutes and then try again, because previous step may take some time to reboot the system. S7-B2 capacity step setup might take more than three minutes. Don't proceed to next step until watchdog is disabled. 5 Initialize hard disk for node. Step example > initialise hw Wait for about 15 minutes. Step result CFPU-0@RNC-1947 [2015-10-08 14:59:37 +0530] ***************** WARNING ********************* The command will erase all data on the node(s) which are ready for DN09203161Issue:02 ©2016Nokia 389 RNC solution features WCDMA 16 Feature Descriptions and Instructions initialization. The operation cannot be undone. The following node is currently ready for initialization: CFPU-1 ******************* WARNING ******************* Are you sure you want to proceed? [y/N]: y Wait for about 15 minutes. After this time the following output is displayed: Hardware successfully initialized 6 Reboot the node from local d isk: > set user username root # hwcli -nr -B 2 <node_name> # exit Step example > set user username root # hwcli -nr -B 2 CFPU-1 # exit Step result Resetting CFPU-1 [ok] It takes 20 minutes to synchronize all DRBD completely. Actual time depends on the size of DRBD. The node will restart and synchronize the Distributed Replicated Block Devices (DRBD).To see how the synchronization is progressing execute watch -n 10 cat /proc/drbd If the command fails check the process log cat /proc/drbd The oos (out of synch) value is zero if a block is synchronized. 0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---ns:512081 nr:0 dw:635 dr:512860 al:4 bm:32 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0 For block 3, the synchronization is in process and progress is displayed 3: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r---n s:2890764 nr:0 dw:46448 dr:2882497 al:32 bm:190 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:12469416 [==>.................] sync'ed: 18.9% (12176/14996)M finish: 0:05:37 speed: 36,872 (30,744) K/sec The synchronization is finished if the oos value for all blocks is 0. 390 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions g RNC solution features Note: Do not restart the node during the DRBD synchronization. The initialization process of the new disk is not ready until the synchronization is successfully completed. 7 Check that serving and backup CMF are working normally: Sub-steps a) Check the serving CMF: The serving CMF is the one related to the node that you are actually logged into. Use the command: show cmf status recovery-unit node-name /<node_name> Step example show cmf status recovery-unit node-name /CFPU-1 Step result Compare the blocks. They should be identical for both managed objects. Recovery units with DRBD resources for managed object /CFPU-1: /CFPU-1/FSDirectoryServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd1: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/FSAlarmSystemLightServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd5: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/QNOMUServer-1: 1/1 (peer[s]/drbd device[s] up) /dev/drbd9: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/FSPM9Server: 1/1 (peer[s]/drbd device[s] up) /dev/drbd8: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/FSClusterStateServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd4: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/FSLogServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd3: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/FSSSHServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd2: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/QNEMServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd10: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/FSCLMServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd6: DRBD_SECONDARY 1/0 (peer/wait secondary) /CFPU-1/FSHotSwapMonitorServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd7: DRBD_SECONDARY 1/0 (peer/wait secondary) b) Check the backup CMF: The backup CMF is the one related to the second, redundant node. Use the command: show cmf status recovery-unit node-name /<node_name> DN09203161Issue:02 ©2016Nokia 391 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step example show cmf status recovery-unit node-name /CFPU-0 Step result Recovery units with DRBD resources for managed object /CFPU-0: /CFPU-0/FSPM9Server: 1/1 (peer[s]/drbd device[s] up) /dev/drbd8: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/FSClusterStateServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd4: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/FSLogServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd3: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/FSSSHServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd2: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/QNEMServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd10: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/FSCLMServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd6: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/FSHotSwapMonitorServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd7: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/FSAlarmSystemLightServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd5: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/FSDirectoryServer: 1/1 (peer[s]/drbd device[s] up) /dev/drbd1: DRBD_PRIMARY 1/0 (peer/wait secondary) /CFPU-0/QNOMUServer-0: 1/1 (peer[s]/drbd device[s] up) /dev/drbd9: DRBD_PRIMARY 1/0 (peer/wait secondary) 8 Unlock CFPU: > set has unlock managed-object <node_name> Step example > set has unlock managed-object CFPU-1 Step result /CFPU-1 unlocked successfully. 9 Switchover S SH t o an other CF PU: Step example > set has switchover force managed-object /SSH > set has switchover force managed-object /QNOMU The SSH connection breaks when the switchover command is executed, and the SSH session must be started again. 392 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features 10 Repeat the procedure for the second CFPU. Perform steps Lock CFPU: to Switchover SSH to another CFPU:. If you have synchronized CFPU-1 as above, then replace <node_name> to CFPU-0, and vice verse. 8.3.5.1.3 Enlarging QNDRBD logical volume and corresponding DRBD file system Procedure 1 Log in as a root. 2 Confirm that both CFPUs are running correctly. Refer to SCLI commands: Step example show has state managed-object /CFPU-* Step result CFPU-0@RNC-207 [2015-01-19 09:46:21 +0800] OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE PROCEDURAL DYNAMIC /CFPU-0 UNLOCKED /CFPU-1 UNLOCKED 3 ENABLED ENABLED ACTIVE ACTIVE - - - Check if QNOMU recovery group is active: Step example show has state managed-object /CFPU-*/QNOMUServer-* Step result CFPU-0@RNC-207 [2015-01-19 10:03:14 +0800] OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE PROCEDURAL DYNAMIC /CFPU-0/QNOMUServer-0 UNLOCKED ENABLED ACTIVE ACTIVE RESOURCE_STATE=FUNCTIONAL RESOURCE_LEVEL=100 /CFPU-1/QNOMUServer-1 UNLOCKED ENABLED ACTIVE HOTSTANDBY RESOURCE_STATE=FUNCTIONAL RESOURCE_LEVEL=100 4 Run the script: Step example #/opt/nsn/SS_ILCommon/bin/enlargeQNDRBD.02.resize_DRBD.sh DN09203161Issue:02 ©2016Nokia 393 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result Checking SSH connection... SSH connection for nodes CFPU-1 CFPU-0: OK Checking QNDRBD size in node CFPU-1... Current QNDRBD volume size in node CFPU-1: 2900 MB Checking QNDRBD size in node CFPU-0... Current QNDRBD volume size in node CFPU-0: 2900 MB QNDRBD device name: /dev/drbd2 Checking VG_System VFree size in node CFPU-1... Checking VG_System VFree size in node CFPU-0... VG_System free size is enough for resizing Checking QNDRBD DRBD state QNDRBD disk state: OK Checking QNDRBD DRBD role QNDRBD DRBD state: OK ************************ WARNING ************************ QNDRBD logical volume size will be resized to 20400 MB ************************ WARNING ************************ Are you sure you want to proceed? [Y/n]: Y<ENTER> Start to resize QNDRBD logical volume, DO NOT operate the cluster! QNDRBD logical volume size in LDAP: 2900 Modifying QNDRBD LDAP configuration... ldap_initialize( ldap://directory:389 ) Saving snapshot... Note: This command might take a long time before showing any results. Please be patient. Overwriting configuration config-R_IL_14.12.1.5.bcn.r.20141223.6-FB20141224112056 completed successfully Running startup actions for the configuration config-R_IL_14.12.1.5.bcn.r.20141223.6FB20141224112056 Running mkboot /mnt/config/R_IL_14.12.1.5.bcn.r.20141223.6/FB20141224112056/kernelmap for node CFPU-0 Running mkboot -n CFPU-1 /mnt/config/R_IL_14.12.1.5.bcn.r.20141223.6/FB20141224112056/kernelmap --nodist for node CFPU-1 Resizing QNDRBD logical volume in node CFPU-1... Rounding up size to full physical extent 2.88 GiB Extending logical volume QNDRBD to 2.88 GiB Logical volume QNDRBD successfully resized QNDRBD logical volume is resized successfully Scanning volume groups in node CFPU-1... Reading all physical volumes. This may take a while... Found volume group "VG_CFPU-1" using metadata type lvm2 Found volume group "VG_System" using metadata type lvm2 Volume groups are scanned Resizing QNDRBD logical volume in node CFPU-0... 394 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Rounding up size to full physical extent 2.88 GiB Extending logical volume QNDRBD to 2.88 GiB Logical volume QNDRBD successfully resized QNDRBD logical volume is resized successfully Scanning volume groups in node CFPU-0... Reading all physical volumes. This may take a while... Found volume group "VG_CFPU-0" using metadata type lvm2 Found volume group "VG_System" using metadata type lvm2 Volume groups are scanned Resizing DRBD device... DRBD device is resized successfully Resizing DRBD filesystem... resize2fs 1.41.9 (22-Aug-2009) Filesystem at /dev/drbd2 is mounted on /var/opt/nsn/SS_ILOMU; on-line resizing required old desc_blocks = 1, new_desc_blocks = 1 Performing an on-line resize of /dev/drbd2 to 755679 (4k) blocks. The filesystem on /dev/drbd2 is now 755679 blocks long. DRBD filesystem is resized successfully Waiting DRBD synchronization to complete after resizing Synchronization completed QNDRBD logical volume is resized successfully! After this procedure, run below commands to verify the DRBD size: 1. # vgs VG #PV #LV #SN Attr VSize VFree VG_CFPU-0 1 9 0 wz--n- 229.08g 179.53g VG_System 1 11 0 wz--n- 49.31g 9.89g 2. # df -kh |grep -i omu /dev/mapper/VG_CFPU--0-QNOMU 2.0G 35M 1.8G 2% /mnt/QNOMU /dev/drbd1 20G 75M 19G 1% /var/opt/nsn/SS_ILOMU 8.3.5.1.4 g Troubleshooting Note: <CFPU>: “CFPU-0” or “CFPU-1”. <disc>: “disc0” or “disc1”. Troubleshooting for modifying VG_System LDAP If after modifying VG_System LDAP configuration any unsuccessful prompts occur, please find the solution proper to the following corresponding prompts: Table 177 Warning prompts Wa r n i n g A n al y s i s <Warning> This script has been executed. There is no need to execute it again. DN09203161Issue:02 The prompt indicates that you have performed this operation, VG_System configuration has been modified in LDAP. ©2016Nokia So l uti o n You can continue to perform stepRe-initialize hard disk to enlarge VG_System manually.. 395 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 177 Warning prompts (Cont.) Wa r n i n g A n al y s i s <Warning> All QNDRBD volumes have been enlarged. There is no need to re-size again. Table 178 The prompt indicates that you have enlarged QNDRBD volume to expected size in the system. No need to perform any step. Error prompts Er ro r 396 So l uti on A n al y s i s So l uti on <Error> Connecting to <CFPU> by SSH failed. Cannot connect to <CFPU> by SSH. Check the network connection for target node. <Error> VG_CFPU free space is not enough. There is not enough free space on the disc partition to enlarge VG_System volume. You need at least 28G free space in VG_CPFU. You can remove useless deliveries or snapshots, and check free space by using the vgs command: VG #PV #LV #SN Attr VSize VFree VG_CFPU-0 1 11 0 wz--n86.68g 37.39g VG_System 1 11 0 wz--n49.31g 9.89g <Error> Saving snapshot failed, current LDAP modification will be lost after system restart. VG_System configuration in LDAP has been modified, but saving snapshot failed. The modification will be lost after system restart. You can check fsconfigure log (/var/log/fsconfigure. log). After the issue is solved, you can save a snapshot by the SCLI save snapshot command, or you can run this script again, it will attempt to save the snapshot for you. <Error> Getting disc partition information from LDAP failed, please check LDAP dn: The modification of LDAP configuration has failed. Please check the LDAP server state by using the proper command. If it is active, please collect syslog and screen output. <Error> Searching LDAP DN:FP2CLADefaultSysVG failed. - <Error> Getting disc See partition information from LDAP failed, please check LDAP dn: <Error> Removing fshwPartitionId:Partition3 from LDAP DN:FP2CLADefaultSysVG failed. - <Error> Getting disc See partition information from LDAP failed, please check LDAP dn: <Error> Adding new fshwPartitionId:Partition3 in LDAP FP2CLADefaultSysVG failed. - <Error> Getting disc See partition information from LDAP failed, please check LDAP dn: ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 178 RNC solution features Error prompts (Cont.) Er r or A n al y s i s So l uti o n <Error> Modifying LDAP <disc> Partition3 instance failed. - <Error> Getting disc See partition information from LDAP failed, please check LDAP dn: Any other error prompt. - If any error prompt occurs, collect andNOKIA screen TS output, syslog and contact and R&D team for investigation. Troubleshooting for enlarging VG_System LDAP configuration If after enlarging VG_System LDAP configuration any unsuccessful prompts occur, please find the solution proper to the following corresponding prompts: Table 179 Error prompts Er r or A n al y s i s So l uti o n <Error> Connecting to <CFPU> by SSH failed. Cannot connect to <CFPU> by SSH. Check the network connection for target node. <Error> Cannot get QNDRBD logical volume size in node <node>, please run lvs and check the output. Qndrbd_resize.sh needs to check the QNDRBD logical volume size by using the lvs command. If the QNDRBD Run the lvs command and check what error is reported. logical volume size cannot be obtained by using the lvs command, this error will occur. <Error> Cannot get QNDRBD device name by command fscmfcli -su /<hostname>, please check this command result. Qndrbd_resize.sh needs to get a QNDRBD device name (for example drbd2) by using the command fscmfcli –su /<hostname>. If the fscmfcli report fails, qndrbd_resize.sh will indicate this error. Check the device name with this command and after solving the problem, rerun qndrbd_resize.sh <Error> VFree size is not enough for QNDRBD re-size, please enlarge VG_System logical group first. Qndrbd_resize.sh will report this error if there is not enough free space for QNDRBD resizing (VFree should at least 18G). The most likely reason is that you have Enlarge the VG_System in both CFPU nodes before running this script. notboth enlarged VG_System in CFPUthe nodes. <Error> DRBD device Enlarging QNDRBD requires (<DRBD_device>) disk state is DRBD disk state is not “UpToDate/UpToDate”. “UpToDate/UpToDate”, if the disk state is not “UpToDate”, this error will be raised. DN09203161Issue:02 ©2016Nokia Please check QNOMU RU and confirm it is active. 397 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 179 Error prompts (Cont.) Er ro r A n al y s i s <Error> DRBD device (<DRBD_device>) role abnormal:<abnormal status rel="nofollow"> Enlarge QNDRBD requires DRBD disk role to be “Primary/Secondary” or “Secondary/Primary”. If one of OMU RU or OMU RG is locked, this error will be So l uti on Ensure both OMUs are unlocked. indicated. <Error> Saving snapshot failed, current LDAP modification will be lost after system restart. VG_System configuration in LDAP has been modified, but saving snapshot failed. The modification will be lost after system restart. <Error> Extending logical volume failed! - PleasecontactNOKIATS team and R&D team for investigation. <Error> Resizing DRBD device failed! PleasecontactNOKIATS team and R&D team for investigation. <Error> Resizing DRBD file system failed! PleasecontactNOKIATS team and R&D team for - You can check fsconfigure log (/var/log/fsconfigure. log). After the issue is solved, you can save a snapshot by the SCLI save snapshot command, or you can run this script again, it will attempt to save the snapshot for you. investigation. 8.3.5.2 Commission PrPRNC Before you start Add oms, btsom and rnccl role IP address on PrPRNC and BkPRNC, which are used for OMS O&M interface and RNC cluster O&M interface. Procedure 1 Add OMS and BTSOM IP addresses on PrPRNC. Configure addresses used for OMS O&M interface and RNC cluster O&M interface. Step example add networking address /QNOMU iface eth0 ip-address 10.43.51.234/32 user /QNHTTPD role oms role rnccl add networking address /QNOMU iface eth0 ip-address 10.43.51.235/32 role btsom 2 Add OMS and BTSOM IP addresses on BkPRNC. Configure addresses used for OMS O&M interface and RNC cluster O&M interface. 398 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step example add networking address /QNOMU iface eth0 ip-address 10.43.52.234/32 user /QNHTTPD role oms role rnccl add networking address /QNOMU iface eth0 ip-address 10.43.52.235/32 role btsom 8.3.5.3 Commission PRNC to StPRNC (mcRNC) Procedure 1 Commission PRNC to StPRNC Step example >set radio-network omsconn-prnc prnc-mode primary prncid 223 pri-oms-ip 10.43.12.98 prncname RNC-223 sec-oms-ip 10.43.7.18 Step result CFPU-0@RNC-223 [2014-11-19 15:48:49 +0800] PRNC-223 creation (mode: primary) completed successfully at 19-11-2014 15:48:50.63 2 Interrogate PRNC in formation Step example >show radio-network omsconn Step result CFPU-0@RNC-223 [2014-11-19 15:48:58 +0800] RNC-OMS connectivity configuration data: ---------------------------------------------------------------------RNC ID: 223 RNC name: RNC-223 Primary OMS IP address: 10.43.12.98 Secondary OMS IP address: 10.43.7.18 Backup OMS IP address: 0.0.0.0 Current serving OMS: 1 (primary OMS) Serving OMS selection: 0 (automatic) Connection retry count: 15 RNC-BTS O&M connection TLS mode: 0 (Off) RNC Client TLS mode: 2 (Probing) ---------------------------------------------------------------------RNC-OMS O&M connection status: ACTIVE ---------------------------------------------------------------------- DN09203161Issue:02 ©2016Nokia 399 RNC solution features WCDMA 16 Feature Descriptions and Instructions PRNC information: ----------------------------------------------------PRNC ID: 223 PRNC name: RNC-223 PRNC mode: 1 (Primary) PRNC IP address: 10.43.51.226 Restart reason: 0 (Normal restart) Primary OMS IP address: 10.43.12.98 Secondary OMS IP address: 10.43.7.18 Backup OMS IP address: 0.0.0.0 Current serving OMS: 1 (primary OMS) Serving OMS selection: 0 (automatic) Connection retry count: 15 RNC Client TLS mode: 0 (Probing) ----------------------------------------------------- 3 Interrogate RNC type Step example >show network-resiliency association Step result CFPU-0@RNC-223 15:58:51 +0800] 4 [2014-11-19 RNC type PRNC ID PRNC IP : StPRNC : 223 : 10.43.51.226 RNCSRV ID Activity mode Service status : 223 : active : idle Configure RNC related objects by RNWPLAN The following eight Managed Objects must be created: RNC, RNAC, RNPS, RNHSPA, RNRLC, RNTRM, RNMOBI, RNFC. Copy the file with RNW PLAN (for example RNWPLAND.XML) to /mnt/QNOMU/plan and execute it. 400 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 5 8.3.5.4 RNC solution features Install all t he required licenses in the PrPRNC. Commission PRNC to BkPRNC (mcRNC) Procedure 1 Commission PRNC to BkPRNC Step example >set radio-network omsconn-prnc prnc-mode backup pri-oms-ip 10.43.12.98 prncid 200 prncname RNC-200 sec-oms-ip 10.43.7.18 Step result CFPU-0@RNC-200 [2014-11-19 16:12:18 +0800] PRNC-200 creation (mode: backup) completed successfully at 19-11-2014 16:12:20.20 2 Interrogate PRNC in formation Step example >show radio-network omsconn Step result CFPU-0@RNC-200 [2014-11-19 16:12:56 +0800] PRNC information: ----------------------------------------------------PRNC ID: 200 PRNC name: RNC-200 PRNC mode: 2 (Backup) PRNC IP address: 10.43.52.226 Restart reason: 0 (Normal restart) Primary OMS IP address: 10.43.12.98 Secondary OMS IP address: 10.43.7.18 Backup OMS IP address: 10.43.12.98 Current serving OMS: 1 (primary OMS) Serving OMSretry selection: 0 Connection count: 15(automatic) RNC Client TLS mode: 2 (Probing) ----------------------------------------------------RNC-OMS O&M connection status: ACTIVE DN09203161Issue:02 ©2016Nokia 401 RNC solution features WCDMA 16 Feature Descriptions and Instructions 3 Interrogate RNC type Step example >show network-resiliency association Step result CFPU-0@RNC-200 RNC type PRNC ID PRNC IP Loaded RNCSRV [2014-11-19 16:25:35 +0800] : : : : BkPRNC 200 10.43.52.226 - Number of RNCSRV displayed = 0. 8.3.5.5 Create BkPRNC object at PrPRNC (mcRNC) Procedure 1 Create BkPRNC object add. The network-resiliency backup-prnc Use command id <id> ip > <ip> ip variable specifies the association backup PRNC IPv4 address with rnccl role. Step example > add network-resiliency association backup-prnc id 200 ip 10.43.52.234 Step result CFPU-0@RNC-223 [2014-11-19 16:08:47 +0800] BkPRNC-200 is added successfully. 2 Interrogate BkPRNC object on PrPRNC Step example >show network-resiliency association Step result CFPU-0@RNC-223 402 [2014-11-19 16:08:55 +0800] ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10.43.51.226 RNCSRV ID Activity mode Service status : 223 : active : idle BkPRNC ID BkPRNC name BkPRNC IP BkPRNC activity mode BkPRNC TLS client mode BkPRNC alarm status Backup completeness BkPRNC backup update time BkPRNC unknown status RNC cluster O&M link state : : : : : : : : : : 8.3.5.6 RNC solution features 200 not updated 10.43.52.234 not updated off not updated not updated not updated true disabled Create RNCSRV at BkPRNC (mcRNC) Procedure 1 Create RNC service Step example >add network-resiliency association rnc-service id 223 Step result CFPU-0@RNC-200 [2014-12-12 16:38:34 +0800] The creation of RNC service 223 is executed. 2 Interrogate service status Step example >show network-resiliency association rnc-service-id 223 Step result CFPU-0@RNC-200 RNC type PRNC ID PRNC IP DN09203161Issue:02 [2014-12-12 16:38:45 +0800] : BkPRNC : 200 : 10.43.52.226 ©2016Nokia 403 RNC solution features WCDMA 16 Feature Descriptions and Instructions RNC service ID : 223 Activity mode : waiting for synchronization Service status : creating service Auto trigger operation : datasync, ipaa Data synchronization state : unblocked Data synchronization schedule : -,00:00 Backup update time : no backup data for rnc service Backup completeness : 0% RNC cluster O&M link state : enabled Number of RNCSRV displayed = 1. Creating service takes approximately one and a half minutes. When Service status changed from creating service to idle the service has been created successfully. Service status 8.3.5.7 : idle Configuring secure RNC-cl O&M interface This chapter describes how to enable security for RNC-cl interface. Procedure 1 Configure cluster O&M interface. Perform these steps in both PrPRNC and BkPRNC. Sub-steps a) Copy the certificate files into both the PrPRNC and BkPRNC under /home folder. • OMU_cert.pem • ca-certificate.pem • OMU_private.pem b) Check the files presence. ls -a /home c) Install the certificates. Install the previously copied certificates with the following commands: In BkPRNC: 404 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features 1. set security cert BTSOMServer ca-cert cert-file /home/ca-certificate.pem ca-id rootca 2. set security cert BTSOMServer ee-cert cert-file /home/OMU_cert.pem key-file /home/OMU_private.pem In PrPRNC: 1. set security cert BTSOMClient ca-cert cert-file /home/ca-certificate.pem ca-id rootca 2. set security cert BTSOMClient ee-cert cert-file /home/OMU_cert.pem key-file /home/OMU_private.pem d) Create SSL/TLS layer definition. e) Change the Client TLS mode to FORCED in PrPRNC. >set network-resiliency association backup-prnc tls-mode forced Step result CFPU-0@RNC-223 Parameter of BkPRNC-200 is modified. Previous TLS client mode : off Current TLS client mode : forced [2015-07-25 14:25:14 +0530] Check that the cluster link is enabled. CFPU-0@RNC-223 RNC type PRNC ID PRNC IP >show network-resiliency association [2015-07-25 14:25:23 +0530] : PrPRNC : 223 : 10.43.51.226 RNC service ID Activity mode Service status : 223 : active : idle BkPRNC ID BkPRNC name : 200 : BkPRNC BkPRNC IP BkPRNC activity mode BkPRNC TLS client mode BkPRNC alarm status Backup completeness BkPRNC backup update time BkPRNC unknown status RNC cluster O&M link state : : : : : : : : DN09203161Issue:02 10.43.52.234 backup forced critical less than 100% 24-07-2015;18:14 false enabled ©2016Nokia 405 RNC solution features WCDMA 16 Feature Descriptions and Instructions Check the 8023 port is opened. # netstat -taunp | grep 8023 tcp 0 0 10.43.51.234:62254 ESTABLISHED 8525/boimed f) 10.43.52.234:8023 Check the con figuration cor rectness. Step result 2 Configure RNC -OMS in terface. Sub-steps a) Copy the certificate files to OMS. Copy the certificate files to /tmp folder with the following commands: Step example • cp /home/Nemuadmin/ca-certificate.pem /tmp • • cp /home/Nemuadmin/cert.pem /tmp cp /home/Nemuadmin/private.pem /tmp b) Install th e certificates. In OMS, enter the following commands: 1. omscertificate install-ca-cert -cert-file /tmp/cacertificate.pem 2. omscertificate install-ee-cert -cert-file /tmp/cert.pem -key-file /tmp/private.pem c) Activate the RAN1102: Secure Management Interface feature: set license feature-mgmt code 0000001244 feature-adminstate on Step result Feature Name Feature Code Type 406 : SecureMngtInterface : 0000001244 : on/off Admin State + License State = Combined Operational State : on + on = on Feature Description : RAN1102 RAN1206 Secure Mngt Interface ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features d) Change the Client TLS mode to PROBING (in OMS). Access the relevant parameter by the path: Application Launcher ► ParameterTool ► ClusterRoot ► OMS ► System ► Network ► TLS ► TLSModeOM ► omsParameterValue e) Change the Client TLS mode to PROBING (in RNC). set radio-network omsconn-config client-tls-mode probing f) Check th e configuration correctness: Step result Port 8003 is used. 8.3.5.8 Configuring dedicated cluster interface Procedure of creating the dedicated cluster interface IP`s and the respective routes on both the PrPRNC and the BkpRNC. Purpose The operator must add new IP address at both PrPRNC and BkPRNC. The new IP must be added at both the PrPRNC and BkPRNC with thernccl assigned role. The same IP is given as input for creating BKPRNC object in PrPRNC. There must be only one IP configured with rolernccl. The rnccl role must not be assigned to multiple IPs in either BkPRNC or PrPRNC. Procedure 1 Create dedicated interface for Bk PRNC's O MU. Step example add networking address dedicated /QNOMU iface eth0 ipaddress 10.43.51.236/32 user /QNHTTPD role rnccl 2 Check the address assigned to rnccl Step example show networking address role rnccl DN09203161Issue:02 ©2016Nokia 407 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result CFPU-0@RNC-223 IP addresses in default instance: eth0 address : 10.43.51.236/32 owner : /QNOMU user role [2015-07-13 16:14:55 +0530] : /QNHTTPD : rnccl 8.3.5.9 Synchronization (mcRNC) Before you start Subnet mapping should be configured on base build of BkPRNC. add network-resiliency subnet-mapping rnc-service-id 223 protect-rnc-vrf iub1 protect-rnc-subnet 10.43.51.42/32 backuprnc-vrf iub1 backup-rnc-subnet 10.43.52.42/32 Type the following SCLI:start network-resiliency synchronize rncservice-id 223 ipaa off The result is indicated by the following command: CFPU-0@RNC-200 [2015-01-08 09:11:37 +0800] This command is executed successful. Procedure 1 Start Manual Synchronization with ipaa(IP auto adaption) off Step example fsclish > start network-resiliency synchronize rnc-serviceid 223 ipaa off Step result CFPU-0@RNC-200 [2015-01-08 09:11:37 +0800] This command is executed successful. 2 Interrogate Synchronization status Step example >show network-resiliency association rnc-service-id 223 408 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step result CFPU-0@RNC-200 [2015-01-08 09:11:45 +0800] RNC type PRNC ID PRNC IP : BkPRNC : 200 : 10.43.52.226 RNC service ID : Activity mode : Service status : Auto trigger operation : Data synchronization state : Data synchronization schedule : Backup update time : Backup completeness : RNC cluster O&M link state : Number of RNCSRV displayed = 1. g 223 waiting for synchronization downloading datasync, ipaa unblocked -,00:00 no backup data for rnc service 0% enabled Note: during synchronization, the “Service status” will change on different phases: downloading doing basic adaptionidle; after synchronization succeeds, the “Backup update time” will be updated, the “Activity mode” should be “backup”, /srv/Log/log/configtest_rncsrv223.log will be generated. 3 g Before starting periodic synchronization, set th e schedule time firstly. Note: When the time is expired, the synchronization starts automatically. 4 Start Periodic Synchronization with ipaa (IP auto adaption) off Before starting periodic synchronization, set the schedule time firstly; when the time is expired, the synchronization starts automatically. Step example set network-resiliency association rnc-service id 223 autotrigger enable-datasync datasync-weekdays ALL datasync-time 10-40 Step result CFPU-0@RNC-200 [2015-07-24 16:09:47 +0530] Parameters of RNC service 223 are modified. Previous data synchronization schedule : -,00:00 Current data synchronization schedule : MON,TUE,WED,THU,FRI,SAT,SUN,10:40 Previous auto trigger operation : datasync, ipaa Current auto trigger operation : datasync DN09203161Issue:02 ©2016Nokia 409 RNC solution features WCDMA 16 Feature Descriptions and Instructions Display the result with show network-resiliency association CFPU-0@RNC-200 : BkPRNC PRNC ID PRNC IP Loaded RNC service : 200 : 10.43.52.226 : - RNC service ID Activity mode Service status Auto trigger operation Data synchronization state Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state : : : : : : : : : 8.3.5.10 [2015-07-24 16:09:47 +0530]RNC type 223 waiting for synchronization idle datasync unblocked MON,TUE,WED,THU,FRI,SAT,SUN,10:40 no backup data for rnc service 0% enabled Configuring RNCSRV at BkPRNC (mcRNC) Procedure 1 Load RNC s ervice Type the following SCLI: Step example >start network-resiliency load rnc-service-id 223 Step result CFPU-0@RNC-200 Are you sure you want to proceed? [Y/n]: y CFPU-0@RNC-200 [2015-01-08 15:58:44 +0800] [2015-01-08 15:58:53 +0800] Note: This command might take a long time. Please be patient. 2 Interrogate using SCLI command: Step example >show network-resiliency association rnc-service-id 223 Step result CFPU-0@RNC-200 410 [2015-01-08 16:10:51 +0800] ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features RNC type PRNC ID PRNC IP : BkPRNC : 200 : 10.43.52.226 RNC service ID Activity mode Service status : 223 : backup : loading rnc service Auto trigger operation Data synchronization state Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state : : : : : : 3 datasync, ipaa unblocked -,00:00 08-01-2015;09:17 0% enabled Do configuration on backup build. On backup build, configure the resources such as: CBC ip address, QNUP&QNIUB ip address, ipro. If ipaa is on when do data synchronization, ipro is unnecessary. Result 8.3.5.11 Configure network interfaces Procedure 1 Add CBC IP address. Step example add networking address /QNCFCP iface eth0 ip-address 2.2.2.2/32 role cbc 2 8.3.5.12 Configure VRRP loadsharing. MSC configuration for Core Network (mcRNC) Purpose Table 180 MSC configuration kPRN C 10.43.52.66 Association2 IP 10.43.52.162 Pointcode DN09203161Issue:02 B Association1 IP 8364 ©2016Nokia MSC 10.63.24.36 10.63.24.36 8526 411 RNC solution features WCDMA 16 Feature Descriptions and Instructions Configure alternate IP address of BkPRNC acting as PrPRNC-1 towards MSC Procedure 1 Add a new signaling service access point. Step example add signaling service-access-point id 1 name SAP1 networkappearance 1 network-indicator NA0 network-type itu 2 Add a new local AS and remote AS. Step example add signaling ss7 local-as id 1 name LASMSC routing-context 8526 routing-key-dpc 8364 service-access-point-name SAP1 traffic-mode loadshare add signaling ss7 remote-as id 1 name MSC communication-type ipsp pending-timer 3 routingcontext 8526 routing-key-dpc 8526 service-access-point-name SAP1 traffic-mode loadshare 3 Add two M3UA associations. Step example add signaling ss7 association id 1 vrf-name iuiurcp communication-type ipsp local-as-name LASMSC remote-as-name MSC primary-local-ip-addr 10.43.52.66 local-client-port 2906 primary-remote-ip-addr 10.63.24.36 remote-port 2905 node /EIPU-0 role client exchange-mode double sctp-profile SS7 add signaling ss7 association id 2 vrf-name iuiurcp communication-type ipsp local-as-name LASMSC remote-as-name MSC primary-local-ip-addr 10.43.52.162 local-client-port 2906 primary-remote-ip-addr 10.63.24.36 remote-port 2905 node /EIPU-1 role client exchange-mode double sctp-profile SS7 4 Add a new SCCP own point code and destination point code. Step example add signaling sccp own-point-code id 1 local-as-name LASMSC name LASMSC add signaling sccp destination-point-code id 4 remote-as-name MSC name MSC 5 412 Add a new subsystem (for RANAP). ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step example add signaling sccp subsystem id 1 name SSNRNCMSC point-code-name LASMSC ssn 142 add signaling sccp subsystem id 4 name SSNMSCRNC point-code-name MSC ssn 142 add signaling sccp concerned-subsystem name CSS1 subsystem-name SSNRNCMSC affectedsubsystem-name SSNMSCRNC add signaling sccp concerned-point-code name CPC1 point-code-name MSC affected-subsystemname SSNRNCMSC 6 Enable the M3UA associations. Step example set signaling ss7 association admin-state enabled id 1 set signaling ss7 association admin-state enabled id 2 Step result root@CFPU-0 [RNC-223] > show signaling ss7 association all CFPU-0@RNC-223 [2015-07-02 13:00:11 +0530] M3UA Association -----------------------------------------------------------------------------association id : 1 local-as-name : LASMSC primary-local-ip-addr : 10.43.52.66 local-client-port : 2906 vrf-name : iuiurcp node : /EIPU-0 remote-as-name : MSC primary-remote-ip-addr : 10.63.24.36 remote-port : 2905 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : client priority : 1 status : connection_down -----------------------------------------------------------------------------M3UA Association -----------------------------------------------------------------------------association id DN09203161Issue:02 : 2 ©2016Nokia 413 RNC solution features WCDMA 16 Feature Descriptions and Instructions local-as-name : LASMSC primary-local-ip-addr : 10.43.52.162 local-client-port : 2906 vrf-name : iuiurcp node : /EIPU-1 remote-as-name : MSC primary-remote-ip-addr : 10.63.24.36 remote-port : 2905 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : client priority : 1 status : connection_down ------------------------------------------------------------------------------ 8.3.5.13 Configuring SGSN for Core Network in resilient network with mcRNC Procedure for configuration of alternate IP address of BkPRNC acting as PrPRNC-1 towards SGSN. Purpose Table 181 SGSN configuration k P R N CB SGSN Association1 IP 10.43.52.98 10.71.4.176 Association2 IP 10.43.52.178 10.71.4.179 Point code 8364 8412 Procedure 1 Add a new signaling service access point. Step example add signaling service-access-point id 2 name SAP2 networkappearance 2 network-indicator NA0 network-type itu 2 Add a new local AS and remote AS Step example add signaling ss7 local-as id 2 name LASSGSN routing-context 8412 routing-key-dpc 8364 service-access-point-name SAP2 traffic-mode loadshare 414 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features add signaling ss7 remote-as id 2 name SGSN communication-type ipsp pending-timer 3 routing-context 8412 routing-key-dpc 8412 service-access-point-name SAP2 traffic-mode loadshare 3 Add two M3UA associations Step example add signaling ss7 association id 3 vrf-name iuiurcp communication-type ipsp local-as-name LASSGSN remote-as-name SGSN primary-local-ip-addr 10.43.52.98 local-client-port 2906 primary-remote-ip-addr 10.71.4.176 remote-port 2906 node /EIPU-0 role client exchange-mode double sctp-profile SS7 add signaling ss7 association id 4 vrf-name iuiurcp communication-type ipsp local-as-name LASSGSN remote-as-name SGSN primary-local-ip-addr 10.43.52.178 local-client-port 2906 primary-remote-ip-addr 10.71.4.179 remote-port 2906 node /EIPU-1 role client exchange-mode double sctp-profile SS7 4 Add a new SCCP own point code and destination point code Step example add signaling sccp own-point-code id 2 local-as-name LASSGSN name LASSGSN add signaling sccp destination-point-code id 5 remote-as-name SGSN name SGSN 5 Add a new subsystem Step example add signaling sccp subsystem id 2 name SSNRNCSGSN point-code-name LASSGSN ssn 142 add signaling sccp subsystem id 5 name SSNSGSNRNC point-code-name SGSN ssn 142 add signaling sccp concerned-subsystem name CSS2 subsystem-name SSNRNCSGSN affectedsubsystem-name SSNSGSNRNC add signaling sccp concerned-point-code name CPC2 point-code-name SGSN affected-subsystemname SSNRNCSGSN 6 Enable the M3UA associations Step example set signaling ss7 association admin-state enabled id 3 set signaling ss7 association admin-state enabled id 4 DN09203161Issue:02 ©2016Nokia 415 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result M3UA Association -----------------------------------------------------------------------------association id local-as-name : 3 : LASSGSN primary-local-ip-addr : 10.43.52.98 local-client-port : 2906 : iuiurcp node : /EIPU-0 remote-as-name : SGSN primary-remote-ip-addr : 10.71.4.176 remote-port : 2906 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : client priority : 1 status : connection_down -----------------------------------------------------------------------------vrf-name M3UA Association -----------------------------------------------------------------------------association id : 4 local-as-name : LASSGSN primary-local-ip-addr : 10.43.52.178 local-client-port : 2906 vrf-name : iuiurcp node : /EIPU-1 remote-as-name : SGSN primary-remote-ip-addr : 10.71.4.179 remote-port : 2906 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : client priority : 1 status : connection_down ------------------------------------------------------------------------------ 8.3.5.14 Configuring Iur interface for mcRNC network resiliency Procedure for Iur interface configuration. Purpose BkPRNC P eer PR NC Association1 IP 10.43.52.130 10.43.46.193 416 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BkPRNC RNC solution features P eer PR NC Association2 IP 10.43.52.146 10.43.46.202 Point code 8364 8370 Procedure 1 Add a n ew signaling service access point (AP). Step example add signaling service-access-point id 3 name SAP3 network-appearance 3 network-indicator NA0 network-type itu 2 Add a new local AS and remote AS. Step example add signaling ss7 local-as id 3 name LASIUR routing-context 8370 routing-key-dpc 8364 service-access-point-name SAP3 traffic-mode loadshare add signaling ss7 remote-as id 3 name IUR communication-type ipsp pending-timer 3 routing-context 8370 routing-key-dpc 8370 serviceaccess-point-name SAP3 traffic-mode loadshare 3 Add two M3UA associations Step example add signaling ss7 association id 5 vrf-name iuiurcp communicationtype ipsp local-as-name LASIUR remote-as-name IUR primary-local-ipaddr 10.43.52.130 local-server-port 2906 primary-remote-ip-addr 10.43.46.193 remote-port 2906 node /EIPU-0 role server exchange-mode double sctp-profile SS7 add signaling ss7 association id 6 vrf-name iuiurcp communicationtype ipsp local-as-name LASIUR remote-as-name IUR primary-local-ipaddr 10.43.52.146 local-server-port 2906 primary-remote-ip-addr 10.43.46.202 remote-port 2906 node /EIPU-1 role server exchange-mode double sctp-profile SS7 4 Add a new SCCP own point code and destination point code. Step example add signaling sccp own-point-code id 3 local-as-name LASIUR name LASIUR DN09203161Issue:02 ©2016Nokia 417 RNC solution features WCDMA 16 Feature Descriptions and Instructions add signaling sccp destination-point-code id 6 remote-as-name IUR name IUR 5 Add a new subsystem. Step example add signaling sccp subsystem id 6 name SSNRNCIUR point-code-name LASIUR ssn 143 add signaling sccp subsystem id 7 name SSNIURRNC point-code-name IUR ssn 143 add signaling sccp concerned-subsystem name CSS3 subsystem-name SSNRNCIUR affected-subsystem-name SSNIURRNC add signaling sccp concerned-point-code name CPC3 point-code-name IUR affected-subsystem-name SSNRNCIUR 6 Enable the M3UA associations Step example set signaling ss7 association admin-state enabled id 5 set signaling ss7 association admin-state enabled id 6 Step result M3UA Association ----------------------------------------------------------------------------association id : 5 local-as-name : LASIUR primary-local-ip-addr : 10.43.52.130 local-server-port : 2906 vrf-name : iuiurcp node : /EIPU-0 remote-as-name : IUR primary-remote-ip-addr : 10.43.46.193 remote-port exchange-mode : 2906 : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : server priority : 1 status : connection_down 418 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features ----------------------------------------------------------------------------M3UA Association ----------------------------------------------------------------------------association id : 6 local-as-name : LASIUR primary-local-ip-addr : 10.43.52.146 local-server-port : 2906 vrf-name : iuiurcp node : /EIPU-1 remote-as-name : IUR primary-remote-ip-addr : 10.43.46.202 remote-port : 2906 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : server priority : 1 status : connection_down ----------------------------------------------------------------------------- 8.3.5.15 Committing the IP address pre-configuration Procedure 1 Commit the configuration. Step example start network-resiliency commit ipaa off Step result CFPU-0@RNC-223 This command is executed successfully 2 [2015-01-08 16:39:18 +0800] Interrogate network association Step example show network-resiliency association rnc-service-id 223 DN09203161Issue:02 ©2016Nokia 419 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result CFPU-0@RNC-223 [2015-01-14 16:39:53 +0800] RNC type PRNC ID PRNC IP : BkPRNC : 200 : 10.43.52.226 RNC service ID Activity mode Service status Auto trigger operation Data synchronization state Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state 3 : : : : : : : : : 223 loaded doing basic adaptation datasync, ipaa unblocked -,00:00 14-01-2015;09:17 less than 100% enabled Ensure that the commitment is finished During the commitment Service status may change as follows Service status Service status : idle : doing basic adaptation Service status : idle After the commit is finished, the Backup completeness factor is 100%. Step example fsclish > show network-resiliency association rnc-serviceid 223 Step result Backup completeness g : 100% Note: If completeness factor is not 100 Backup completeness : less than 100% refer to commit log /srv/Log/log/configtest_rncsrv223.log. 8.3.5.16 Mapping IP address Purpose This procedure is necessary to perform auto-adaptation successfully. The mapping is specific for RNCSRV, thus it must be done at BkPRNC. 420 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Procedure 1 Interrogate unmapped IP addressing data from RNCSRV of PrPRNC Step example show network-resiliency ip-unmapping rnc-service-id 223 Step result CFPU-0@RNC-223 [2015-07-09 14:33:31 +0530] RNC service [223] unmapped IP: PrPRNCvrf PrPRNCIP BkPRNCvrf BkPRNCIP ----------------- ----------------- ----------------- ----------------iub1 10.43.51.36 iub2 10.43.51.52 iuiurup1 10.43.51.4 iuiurup1 10.43.51.5 iuiurup1 10.43.51.6 iuiurup2 10.43.51.20 iuiurup2 10.43.51.21 iuiurup2 10.43.51.22 iuiurup1 10.43.52.4 iuiurup1 10.43.52.5 iuiurup1 10.43.52.6 iuiurup2 10.43.52.20 iuiurup2 10.43.52.21 iuiurup2 10.43.52.22 PrPRNC total unmapped IP count: 8. BkPRNC total unmapped IP count: 6. 2 Map PrPRNC IP address to BkPRNC IP address Step example add network-resiliency ip-mapping protect-rnc-ip 10.43.51.4 protect-rnc-vrf iuiurup1 backup-rnc-ip 10.43.52.4 backuprnc-vrf iuiurup1 rnc-service-id 223 info IUIURUP1 Step result CFPU-0@RNC-223 [2015-07-09 14:41:36 +0530] Successfully add IP mapping record. g Note: All the unmapped IPs of the PrPRNC should be mapped with proper BkPRNC IP. There should not be any unmapped IPs under the PrPRNCIP section. 3 Interrogate mapped IP addressing data from RNCSRV of PrPRNC Step example DN09203161Issue:02 ©2016Nokia 421 RNC solution features WCDMA 16 Feature Descriptions and Instructions show network-resiliency ip-mapping rnc-service-id 223 Step result CFPU-0@RNC-223 [2015-07-09 14:45:13 +0530] RNC service [223] IP mapping: PrPRNCvrf PrPRNCIP BkPRNCvrf BkPRNCIP STATUS INFO ----------------- ----------------- ----------------- ----------------- ------- ----iuiurup1 10.43.51.4 iuiurup1 10.43.52.4 VALID IUIURUP1 iuiurup1 10.43.51.5 iuiurup1 10.43.52.5 VALID IUIURUP1 iuiurup1 10.43.51.6 iuiurup1 10.43.52.6 VALID IUIURUP1 iuiurup2 10.43.51.20 iuiurup2 10.43.52.20 VALID IUIURUP2 iuiurup2 10.43.51.21 iuiurup2 10.43.52.21 VALID IUIURUP2 iuiurup2 10.43.51.22 iuiurup2 10.43.52.22 VALID IUIURUP2 Total matched IP mapping count: 6 8.3.6 Verifying RAN3005: Network Resiliency for mcRNC Before you start Correct configuration of PrPRNC and BkPRNC provides synchronization possibility between PrPRNC and BkPRNC, which is verified by performing redundancy switch. Procedure 1 Trigger the s witchover with SCLI or vi a OMS. Follow the instructions described in Performing normal redundancy switch from PrPRNC to BkPRNC. Result When configuration is done properly, the PrPRNC automatically shuts down 3GPP services and BkPRNC starts the services. After restart, the BkPRNC starts and the 3GPP services are back online. Troubleshooting in case of redundancy switch failure If the RNC-cl O&M interface is down, the PrPRNC cannot be shut down from BkPRNC but it has to be shutdown manually. An alarm indicates the loss of RNC-cl O&M interface. IP connectivity test helps to find any problems in IP layer, what might be a reason of verification failure. 422 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 8.3.7 RNC solution features Deactivating RAN3005: Network Resiliency for mcRNC Procedure 1 Remove RNC association at PrPRNC. Delete BkPRNC object via SCLI command: >delete network-resiliency association backup-prnc Step result CFPU-0@RNC-223 Are you sure you want to proceed? [Y/n]: y CFPU-0@RNC-223 BkPRNC-200 is removed successfully. 2 [2015-07-24 15:29:08 +0530] [2015-07-24 15:29:12 +0530] Verify that the RNC association has been successfully removed. Execute the below SCLI command: root@CFPU-0 [RNC-223] > show network-resiliency association Step result CFPU-0@RNC-223 [2015-07-24 15:40:32 +0530] RNC type PRNC ID PRNC IP RNC service ID Activity mode Service status : : : : : : 3 StPRNC 223 10.43.51.226 223 active idle Verify that the successful deletion information has been sent. The O&M application SW sends BTS O&M interface ConfigurationChangeNotification message to OMS when BkPRNC object is deleted successfully. 4 Delete the BKPRNC object at the PrPRNC object using OMS GUI. 5 Verify that the BKPRNC object in OMS has been successfully deleted. 6 Delete RNCSRV object in BkRNC. Delete the RNCSRV in BkPRNC using SCLI command: DN09203161Issue:02 ©2016Nokia 423 RNC solution features WCDMA 16 Feature Descriptions and Instructions > delete network-resiliency association rnc-service id 223 CFPU-0@RNC-200 [2015-07-24 15:59:51 +0530] Are you sure you want to proceed? [Y/n]: y CFPU-0@RNC-200 [2015-07-24 15:59:53 +0530] The deletion of RNC service 223 is executed. Step result Verify the deletion of RNCSRV using below command: > show network-resiliency association rnc-service-id 223 CFPU-0@RNC-200 [2015-07-24 16:00:01 +0530] RNC type PRNC ID PRNC IP Loaded RNC service RNC service ID Activity mode Service status Auto trigger operation Data synchronization state Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state 7 : : : : : : : : : : : : : BkPRNC 200 10.43.52.226 223 backup deleting service datasync, ipaa unblocked -,00:00 09-07-2015;15:13 less than 100% disabled Verify that the RNCSRV object has been successfully deleted. Interrogate using the below command: > show network-resiliency association Step result CFPU-0@RNC-200 [2015-07-24 16:00:44 +0530] RNC type PRNC ID PRNC IP Loaded RNC service : : : : BkPRNC 200 10.43.52.226 - Number of RNC service displayed = 0. 8 Verify that the corresponding backup build presence has been deleted. Execute the below command to check if the backup build is deleted: > show swmanage app-sw-mgmt builds all 424 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step result CFPU-0@RNC-200 [2015-07-24 16:00:35 +0530] SW Build name: 20150706_A SW Build status: BU (Active) SW Delivery: R_QNCB.15.26.0_4.WR.mips.dmp LDAP Configuration: config-R_QNCB.15.26.0_4.WR.mips.dmp-INITIAL 8.3.8 8.3.8.1 8.3.8.1.1 Other instructions Operating instructions Testing IP connectivity for mcRNC in resilient network Instructions for running the IP connectivity test. Purpose Procedure 1 Execute IP connectivity test When the activity mode of RNCSRV in BkPRNC is LOADED the IP connectivity test is automatically enabled and SCTP/TCP filter is applied for all of the EIPU Ethernet interfaces. Step example Execute the SCLI to start IPCT: start network-resiliency ipct ran-interface all ran-plane all Step result CFPU-0@RNC-167 This command is executed successfully. 2 [2015-01-08 17:20:57 +0800] Display IP connectivity test results Step example show network-resiliency ipct-info Step result CFPU-0@RNC-223 [2015-01-08 17:22:34 +0800] I/F Plane Total Unsuccess Part Success Success Warning Not Test --- ----- ----- --------- ------------ ------- ------- -------- DN09203161Issue:02 ©2016Nokia 425 RNC solution features IUB IUB IUB IU IU SUM O&M CP UP CP UP - WCDMA 16 Feature Descriptions and Instructions 00080 00080 00080 00064 00008 00312 RNC service ID Test start time Test end time 00000 00000 00000 00000 00000 00000 00000 00000 00000 00000 00000 00000 00000 00000 00000 00003 00000 00003 00000 00000 00000 00000 00000 00000 00080 00080 00080 00061 00008 00309 : 223 : 2015-01-08 17:22:16.21 : 2015-01-08 17:27:39.48 g Note: Refer to /srv/Log/log/iptest_rncsrv223.log file for the IP connectivity test results. 8.3.8.1.2 Performing controlled redundancy switch Purpose After the redundancy switch, the BKPRNC object (under RNC object) will be removed from topology of BkPRNC implicitly. t Tip: Redundancy switch over can be triggered from Backup and Loaded modes in BkPRNC. Procedure 1 Activate RNCSRV-223 on BkPRNC. Step example start network-resiliency activate rnc-service-id 223 mode controlled Step result CFPU-0@RNC-223 [2015-01-08 17:28:57 +0800] ********************************WARNING********************************** Activation will be executed. If the completeness of the RNC service to be activated is less than 100, backup PRNC may not perform the full functionality of protected PRNC. If forced way is used, make sure the RNC service in peer RNC has been deactivated or isolated, otherwise backup PRNC and protected PRNC will be alive at the same time. ********************************WARNING********************************** 426 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Are you sure you want to proceed? [Y/n]: y CFPU-0@RNC-223 RNC solution features [2015-01-08 17:28:59 +0800] RNC service 223 is activated. 2 Perform controlled redundancy switch. Step example show network-resiliency association rnc-service-id 223 Step result After controlled redundancy switch succeed: • Activity mode is changed to Active • on BkPRNC and the BkPRNC starts serving RNC service. Activity mode is changed to Loaded on PrPRNC and the PrPRNC stops serving RNC service. 3 Interrogate Activity mode on BkPRNC Step example show network-resiliency association rnc-service-id 223 Step result CFPU-0@RNC-223 [2015-07-09 12:48:29 +0530] RNC type PRNC ID PRNC IP : BkPRNC : 200 : 10.43.52.226 RNC service ID Activity mode Service status : 223 : active : idle Auto operation Data trigger synchronization state Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state : : : : : : DN09203161Issue:02 datasync, unblocked ipaa -,00:00 07-07-2015;13:28 100% enabled ©2016Nokia 427 RNC solution features WCDMA 16 Feature Descriptions and Instructions 4 Interrogate Activity Mode on PrPRNC Step example show network-resiliency association Step result CFPU-0@RNC-223 [2015-07-09 10:54:47 +0530] RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10.43.51.226 RNC service ID Activity mode Service status : 223 : loaded : idle BkPRNC ID BkPRNC name BkPRNC IP BkPRNC activity mode BkPRNC TLS client mode BkPRNC alarm status Backup completeness BkPRNC backup update time BkPRNC unknown status RNC cluster O&M link state : : : : : : : : : : g 200 RNC-200 10.43.52.234 active off critical 100% 07-07-2015;13:28 false enabled Note: If during resiliency switch the system restarts spontaneously or on operator's demand, the alarm 3361 MISMATCH BETWEEN SW BUILD CONFIGURATION AND CONFIGURATION NE may occur. It means NE file restoration has been interrupted and NE configuration is mismatched with running SW build. 8.3.8.1.3 Performing forced redundancy switch (mcRNC) Forced redundancy switch command for and procedure prerequisites. Before you start w 428 Redundancy conflict, where both PrPRNC and BkPRNC are online at the same time, may occur when forced redundancy switchback is executed. Prevent it by isolating manually the PrPRNC. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Procedure 1 Perform forced redundancy switch on Bk PRNC: Step example start network-resiliency activate rnc-service-id 223 mode forced Step result • Activity mode changes to Active • on BkPRNC. BkPRNC starts serving RNC service. Result After forced redundancy switch succeed, the Activity mode is changed to Active on BkPRNC, the BkPRNC starts serving RNC service. 8.3.8.1.4 Performing controlled redundancy switchback Purpose After the redundancy switchback, the BKPRNC object will be created (under RNC object) into topology of PrPRNC implicitly. Procedure 1 Perform controlled redundancy switchback on PrPRNC. Step example start network-resiliency activate rnc-service-id 223 mode controlled 2 Interrogate the a ctivity mode of t he PrPRNC Step example show network-resiliency association Step result CFPU-0@RNC-223 RNC type PRNC ID PRNC IP DN09203161Issue:02 [2015-07-25 10:52:21 +0530] : PrPRNC : 223 : 10.43.51.226 ©2016Nokia 429 RNC solution features WCDMA 16 Feature Descriptions and Instructions RNC service ID Activity mode Service status : 223 : active : idle BkPRNC ID BkPRNC name BkPRNC IP : 200 : BkPRNC : 10.43.52.234 BkPRNC activity mode BkPRNC TLS client mode BkPRNC alarm status Backup completeness BkPRNC backup update time BkPRNC unknown status RNC cluster O&M link state : : : : : : : loaded off critical less than 100% 24-07-2015;18:14 false enabled Result • The Activity mode is ACTIVE • on PrPRNC and the PrPRNC starts serving RNCSRV. The Activity mode is LOADED on BkPRNC and the BkPRNC stops serving RNCSRV. 8.3.8.1.5 Performing forced redundancy switchback for mcRNC Forced redundancy switchback command for and procedure prerequisites. Before you start w Redundancy conflict, where both PrPRNC and BkPRNC are online at the same time, may occur when forced redundancy switchback is executed. Prevent it by isolating manually the BkPRNC. Procedure 1 Perform forced redundancy switchback on PrPRNC. Step example start network-resiliency activate rnc-service-id 223 mode forced 2 Interrogate the Activity mode in PrPRNC show network-resiliency association 430 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step result CFPU-0@RNC-223 [2015-07-25 11:08:23 +0530] RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10.43.51.226 RNC service ID Activity mode Service status : 223 : active : idle BkPRNC ID BkPRNC name BkPRNC IP BkPRNC activity mode BkPRNC TLS client mode BkPRNC alarm status Backup completeness BkPRNC backup update time BkPRNC unknown status RNC cluster O&M link state : : : : : : : : : : 200 BkPRNC 10.43.52.234 loaded off critical less than 100% 24-07-2015;18:14 false enabled Result • Activity mode changes to Active • 8.3.8.1.6 8.3.8.1.6.1 on PrPRNC. PrPRNC starts serving RNC service. Network Resiliency operations in OMS Configuring network resiliency using OMS Element Manager Purpose This chapter instructs how to configure OMS in order to act in the resilient network. The operator is able to connect 20 PRNC/RNC pairs to one OMS and additionally 10 PRNCs (without RNC service). BKPRNC object is on the feature license and there is no restriction for creating it. This object needs to point out to the PRNC object that is already in the topology. Procedure 1 t DN09203161Issue:02 Commission Bk PRNC. Tip: Commission BkPRNC only if this procedure has not been done yet. If it has been done, ensure BkPRNC managed object presence in GUI and proceed with step Create RNCSRV in BkPRNC. ©2016Nokia 431 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result BkPRNC is present on OMS as shown in the Figure 81: Example view of BkPRNC managed object visible in OMS GUI Figure 76 2 Example view of BkPRNC managed object visible in OMS GUI Create RNCSRV in BkPRNC. Open OMS Element Manager. Go to the specific BkPRNC ID. Right-click on it and create RNCSRV usingCreate new objectoption. 3 Create BkPRNC ob ject f or P rPRNC. BkPRNC object must occur under the following pathROOT ► RNC-<ID> ► BkPRNCs. BkPRNC IP address is visible under Backup RNC IPv4 Address used for establishing RNC cluster O&M interface. 4 Add another PrPRNC. Repeat steps Create RNCSRV in BkPRNC. and Create BkPRNC object for PrPRNC. if you want to add another PrPRNC. 8.3.8.1.6.2 Performing forced redundancy switch using OMS EM Purpose This chapter introduces example procedure of forced redundancy switch from PrPRNC221 to BkPRNC-301 with RNCSRV-221. Procedure 1 Search for respective RNCSRVby DN in the Navigation bar. Perform Search for respective RNCSRVby DN in the Navigation bar. . 432 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 2 RNC solution features Activate RNCSRV-221 i n Bk PRNC In BkPRNC, right-click on the RNCSRV-221 and select Resiliency menu. 8.3.8.1.6.3 from RNC Performing redundancy switch using OMS EM Purpose This chapter introduces example procedure of redundancy switch from PrPRNC-221 to BkPRNC-301 with RNCSRV-221. Procedure 1 Search for respective RNCSRVby DN in the Navigation bar. Type in RNCSRV-221 in the search line under the Topology tab. Step result The list of NEs containing searched content is displayed: • PRNC-221/RNCSRV-221 - directs to PrPRNC which contain representing RNCSRV. • PRNC-301/RNCSRV-221 - directs to BkPRNC which contain RNCSRV representing PrPRNC-221. Click on either first or second result. You can recognize where have you been brought either by checking which PRNC is indicated by respective icon, according to Impact on network and network element management tools , or by right-click on the RNCSRV-221 and checking which RNC Resiliency menu appears. 2 Activate RNCSRV-221 i n Bk PRNC In BkPRNC, right-click on the RNCSRV-221 and select Resiliency menu. g from RNC Note: The values of the ActivityMode parameter may differ between the Main Parameters application and the Parameter Viewer/Editor applications, as long as the topology data is parsed by OMS. The Main Parameters application displays all the main parameters of the selected object which are stored in the OMS topology database, while Parameter (in thisthe case PRNC). Editor/Viewer applications display data directly from the related NE 8.3.8.1.6.4 Performing redundancy switchback using OMS EM Purpose This chapter introduces example procedure of redundancy switchback from BkPRNC301 to PrPRNC-221. DN09203161Issue:02 ©2016Nokia 433 RNC solution features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Search for respective RNCSRVby DN in the Navigation bar. Perform Search for respective RNCSRVby DN in the Navigation bar. . 2 Activate RNCSRV-221 in PrPRNC. In PrPRNC, right-click on the RNCSRV-221 and select Resiliency menu. 8.3.8.1.7 from RNC Reconfiguring BTS for Network Resiliency Purpose The user reconfigures BTS in order to add a BkPRNC configuration, which is an additional RNC configuration. Before you start Primary BTS configuration has been already done. Procedure 1 Commission BTS using additional PrPRNC and BkPRNC IP addresses. Provide the following information in BTS SM, on the Iub interface configuration page within the Backup RNC configuration: Table 182 BTS configuration values P a r a me t e r Far end SCTP subnet address Va l u e BkPRNC IP address for example: 10.43.52.42 Far end SCTP subnet address mask BkPRNC FAREND SCTP for example: 255.255.255.255 (/32) OAMaddress BkPRNCIPaddress for example: 10.43.52.235 g 434 Note: Re-homing BTS may require changing of BkPRNC information to values related to the new controller. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 8.3.8.1.8 RNC solution features Configuring IP addresses in backup build for BkPRNC (mcRNC) Procedure 1 Configure IP ad dress re sources Configure: CBC IP address QNUP and QNIUB IP addresses IPRO BFD • • • • g 8.3.8.1.9 Note: If IP Auto-adaptation is set to ON when data synchronization is processing, IPRO configuration is not needed. Performing IP auto adaptation Purpose Purpose The user can perform the IP auto adaptation • to trigger automatically during scheduled synchronization • • to trigger automatically during manual synchronization to trigger manually on demand g Note: If IP auto adaptation is set to trigger automatically then it begins after data synchronization. Otherwise, the user has to perform manual IP auto adaptation for RNCSRV set to LOADED mode. • Configure IP auto adaptation to trigger automatically during scheduled synchronization. Change the Current auto trigger operation to datasync, ipaa Step example set network-resiliency association rnc-service id 223 autotrigger enable-datasync-ipaa Step result CFPU-0@RNC-200 [2015-07-09 15:06:07 +0530] Parameter of RNC service 223 is modified. DN09203161Issue:02 ©2016Nokia 435 RNC solution features WCDMA 16 Feature Descriptions and Instructions Previous auto trigger operation : datasync Current auto trigger operation : datasync, ipaa – When the schedule synchronizationstarts, check Service Status to monitor which operation is currently ongoing. Check it with the command:show network-resiliency association – rnc-service-id 223 IP auto adaptation is indicated by Service status : doing IP auto adaptation Service Status changes in the following way CFPU-0@RNC-200 (...) Service Status (...) Service Status (...) [2015-07-09 15:16:11 +0530 :downloading :doing basic adaptation CFPU-0@RNC-200 [2015-07-09 15:16:11 +0530] RNC type PRNC ID : BkPRNC : 200 PRNC IP : 10.43.52.226 RNC service ID Activity mode Service status Auto trigger operation Data synchronization state Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state : : : : : : : : : g 223 backup doing IP auto adaptation datasync, ipaa unblocked -,00:00 08-07-2015;11:25 less than 100% enabled Note: Refer to /srv/Log/log/configtest_rncsrv223.log file for the IP auto adaptation results. • Configure IP auto adaptation to trigger automatically during manual synchronization. Sub-steps 1 Trigger manual synchronization. Step example 436 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features start network-resiliency synchronize rnc-service-id 223 ipaa on Step result CFPU-0@RNC-223 [2015-07-09 15:12:58 +0530] This command is executed successfully. • Manual IP auto adaptation on d emand. Sub-steps 1 Switch RNCSRV to LOADED mode. 2 Trigger commit with IPAA. Step example start network-resiliency commit ipaa on Step result CFPU-0@RNC-223 This command is executed successfully. 8.3.8.1.10 [2015-07-09 16:21:19 +0530] mcRNC SW builds upgrade on BkPRNC Recommendations for particular types of SW upgrades on PRNCs in the resilient network. For instructions see Upgrading mcRNC SW builds and BPS on BkPRNC PrPRNC's SW upgrade Upgrade of software build on PrPRNC progress the same as the normal mcRNC upgrade. For detailed instructions refer toRelease upgrade instructionsattached to particular SW build. BkPRNC's SW upgrade Upgrade of BkPRNC is to upgrade an active BPS to a new specified BPS (base build and all backup builds). BPS upgrade procedure on BkPRNC Activity ( mode : Backup) This procedure contains the following steps: • BPS upgrade – DN09203161Issue:02 Base build upgrade ©2016Nokia 437 RNC solution features WCDMA 16 Feature Descriptions and Instructions – • Backup builds upgrade BPS activation For the operating instruction, seeUpgrading mcRNC SW builds and BPS on BkPRNC. BPS upgrade procedure on BkPRNC Activity ( mode : Loaded or Active) For the backup build in Activity mode : Loaded or Active the upgrade progresses the same as normal RNC upgrade. No new BPS is created as part of this upgrade and newly created build is not part of any BPS. For the operating instruction, seeOperating BPS on BkPRNC with the Activity Mode: Loaded or Active. Full release / Change Delivery (CD) update / OnTop installation on the Activity mode: Active or Loaded. This is supported because it is possible that BkPRNC runs one of RNC’s service for a longer time (for example more than one month). In this time SW upgrade/update might be necessary for the backup build in Active mode. In Active/Loaded mode, BkPRNC upgrade covers only running backup build. The upgrade instructions are the same as a regular SW update/upgrade at normal controller. The new SW build does not belong to any BPS. If the operator need to return to old base build the after the new SW build has been activated: 1. Activate old backup build with set sw-manage app-sw-mgmt activate swbuild-name/sw-build-status. 2. Performs resiliency switch back command to switch back to old base build. 8.3.8.1.10.1 Creating BPS fallback Instructions for obtaining BPS fallback. Procedure 1 Create BPS fallback. Step example > save sw-manage bps name BPSFB1 Step result Running BPS name : 20140929_A Base build : 20140929_A RNC service : 00001 Each build fallback copying may need several minutes, please be patient!! Base build: Build on copying ... Copying is successful 438 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Backup build for RNC service 00001: Build on copying ... Copying is successful BPS fallback messages for creation abort. When BPS fallback creation was aborted while last build was being copied to the BPS, the following message occurs: root@CFPU-0 [BCN_211] > save sw-manage bps name BPSFB2 BPS name is already used by other BPS, please try again with new BPS name! root@CFPU-0 [RNC-221] > save sw-manage bps name BPSFB3 CFPU-0@RNC-221 [2015-10-08 11:50:42 +0530] Prepare fallback copying for running BPS! Running BPS name : BPS_152620 Base build : BPS_152620 RNCservice : 222 Start fallback copying! Each build fallback copying need several minutes, please be patient!! Base build: Build on copying ... Copying is successful Backup build for RNC service 222: Build on copying ... The last build copying is ongoing and cannot be aborted. Please wait until it finishes Copying is successful Interruption attempted by user - but the task was completed and executed successfully When BPS fallback creation was aborted while base build was being copied to the BPS, the following message occurs: root@CFPU-0 [BCN_211] > save sw-manage bps name BPSFB2 Start fallback copying for running BPS! Running BPS name : 20140929_A Base build : 20140929_A RNC service : 00001 Each build fallback copying may need several minutes, please be patient!! Base build: Build on copying ... Try to abort build copying ... Build copying is aborted [warning] The left BPS is incomplete! BPS copying is aborted Related descriptions Configuring GIVAXI/givClienton page 300 Backup Physical RNC System managementon page 360 8.3.8.1.10.2 Upgrading mcRNC SW builds and BPS on BkPRNC Purpose This procedure describe steps necessary to upgrade base build and backup build in BkPRNC's BPS. There are several optional ways to perform the upgrade. DN09203161Issue:02 ©2016Nokia 439 RNC solution features WCDMA 16 Feature Descriptions and Instructions • Upgrade all builds (base build backup builds) simultaneously. Sub-steps 1 Upgrade both base build and all backup builds belonging to the current, running BPS. Step example set sw-manage bps install all new-bps-name 152603_bps delivery /mnt/backup/backup/R_QNCB.15.26.0_3.WR.mips.dmp.iso Step result BPS installation request is sent successfully. Please check installation task by SCLI "show sw-manage bps upgrade-task". 2 Check the upgrade task information Step example show sw-manage bps upgrade-task Step result Upgrade start time: 2015-04-29 16:56:14 Current BPS name: 20150702_A New BPS name: 152603_bps Base build : 152603_bps --> Ongoing RNC service: 223 --> Queuing RNC service: 224 --> Queuing t Tip: Detailed installation log is placed insrv/Log/log/bps_upgrade.log 3 Check new BPS Step example show sw-manage bps all • Upgrade base build and backup builds one by one Sub-steps 1 Upgrade base build The user upgrades base build and creates new BPS. 440 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step example set sw-manage bps install base-build new-bps-name 152603_bps delivery /mnt/backup/backup/R_QNCB.15.26.0_3.WR.mips.dmp.iso Step result Result: CFPU-0@RNC-200 [2015-07-03 12:06:08 +0530] BPS installation request is sent successfully. Please check installation task by SCLI "show sw-manage bps upgrade-task". 2 Check the installation task information Step example show sw-manage bps upgrade-task Step result CFPU-0@RNC-200 Upgrade start time: 2015-07-03 12:06:09 Current BPS name: 20150702_A New BPS name: 152603_bps Base build : 152603_bps --> t [2015-07-03 12:06:17 +0530] Ongoing Tip: The base build upgrade is completed when status changed from Ongoing to Done . 3 Upgrade backup builds set sw-manage bps install backup-build new-bps-name <new bps name> specified-service-id id <rnc-service-id> id <rnc-service-id> | all t Tip: The parameter all triggers the upgrade of all backup builds (RNCSRVs) of running BPS to the new BPS. Step example set sw-manage bps install backup-build bps-name 152603_bps specified-service-id id 223 id 224 DN09203161Issue:02 ©2016Nokia 441 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result CFPU-0@RNC-200 [2015-07-06 10:29:04 +0530] BPS installation request is sent successfully. Please check installation task by SCLI "show sw-manage bps upgrade-task". 4 Check the upgrade task information Step example show sw-manage bps upgrade-task Step result CFPU-0@RNC-200 Upgrade start time: 2015-07-06 10:29:06 Current BPS name: 20150702_A New BPS name: 152603_bps RNC service: 223 --> Ongoing RNC service: 224 --> Queuing t [2015-07-06 10:29:14 +0530] Tip: Detailed installation log is placed insrv/Log/log/bps_upgrade.log 5 Check new BPS Step example show sw-manage bps all Related descriptions Configuring GIVAXI/givClienton page 300 Backup Physical RNC System managementon page 360 8.3.8.1.10.3 Activating new BPS on BkPRNC (mcRNC) Purpose This procedure contains steps to activate new BPS after update or upgrade of SW builds on BkPRNC Procedure 1 w 442 Activate new BPS. System restart is triggered by this operation. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step example set sw-manage bps activate bps-name 152603_bps Step result *********** WARNING *************** BPS activate requested ************* WARNING ************* Are you sure you want to proceed? [Y/n]: y NOTE: This command might take a few minutes before showing any results. Please be patient. And do not terminate the command execution, for example do not press buttons Ctrl and C at the same time. 2 Check the new BPS in formation. Step example show sw-manage bps name 152603_bps Step result BPS has been switched to the BPS 152603_bps BPS name : 152603_bps Default: Y Base : SW build name : 152603_bps SW build status : NW SW delivery : R_QNCB.15.26.0_3.WR.mips.dmp LDAP configuration: config-R_QNCB.15.26.0_3.WR.mips.dmp-INITIAL ILMFS files : SS_ILMFS/R_QNCB.15.26.0_3.WR.mips.dmp RNW database : DB/R_QNCB.15.26.0_3.WR.mips.dmp NE files : SWBuilds/ID_20150629181954640523_UNDEF/NEFiles RNC service ID : 223 SW build name : BK_223_90 SW build status : UD SW delivery : R_QNCB.15.26.0_3.WR.mips.dmp LDAP configuration: config-R_QNCB.15.26.0_3.WR.mips.dmp-BK20150701155422 ILMFS files : SS_ILMFS/R_QNCB.15.26.0_3.WR.mips.dmp-BK20150701155422 RNW database : DB/R_QNCB.15.26.0_3.WR.mips.dmp-BK20150701155422 NE files : SWBuilds/ID_20150701155422762718_BACKUP/NEFiles RNC service ID : 224 SW build name : BK_224_72 SW build status : UD SW delivery : R_QNCB.15.26.0_3.WR.mips.dmp LDAP configuration: config-R_QNCB.15.26.0_3.WR.mips.dmp-BK20150701152306 ILMFS files : SS_ILMFS/R_QNCB.15.26.0_3.WR.mips.dmp-BK20150701152306 DN09203161Issue:02 ©2016Nokia 443 RNC solution features WCDMA 16 Feature Descriptions and Instructions RNW database NE files : DB/R_QNCB.15.26.0_3.WR.mips.dmp-BK20150701152306 : SWBuilds/ID_20150701152306517419_BACKUP/NEFiles Related descriptions Configuring GIVAXI/givClienton page 300 Backup Physical RNC System managementon page 360 8.3.8.1.10.4 Operating BPS on BkPRNC with the Activity Mode: Loaded or Active Procedure for the BPS upgrade on the BkPRNC with theActivity Mode: Loaded or Active. • Upgrading the BPS on the BkPRNC with the Activity Mode: Loaded or Active. Sub-steps 1 Install the new delivery. > set sw-manage install delivery /mnt/backup/R_QNCB.15.26.2_11.WR.mips.rmp.iso Step result CFPU-0@RNC-223 [2016-02-05 12:26:01 +0530] WARNING: Forcing upgrade path from R_QNCB.15.26.2_10.WR.mips.rmp to R_QNCB.15.26.2_11.WR.mips.rmp INFO: installing /mnt/backup/R_QNCB.15.26.2_11.WR.mips.rmp.iso INFO: This might take several minutes... 2 Check if the new build is created. > show sw-manage app-sw-mgmt builds all Step result The following output shows the status of the new build: SW Build status: NW CFPU-0@RNC-223 [2016-02-05 13:36:04 +0530] SW Build name: 20160204_A SW Build status: UT SW Delivery: R_QNCB.15.26.2_10.WR.mips.rmp LDAP Configuration: config-R_QNCB.15.26.2_10.WR.mips.rmp-Rakesh Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.15.26.2_10.WR.mips.rmp/ 444 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Path to RNW database dump: /var/opt/nsn/SS_ILOMU/DB/R_QNCB.15.26.2_10.WR.mips.rmp/ SW Build name: BK_223_15 SW Build status: BU (Active) SW Delivery: R_QNCB.15.26.2_10.WR.mips.rmp LDAP Configuration: config-R_QNCB.15.26.2_10.WR.mips.rmpBK20160205092927 Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.15.26.2_10.WR.mips.rmpBK20160205092927/ Path to RNW database dump: /var/opt/nsn/SS_ILOMU/DB/R_QNCB.15.26.2_10.WR.mips.rmpBK20160205092927/ SW Build name: 20160205_A SW Build status: NW SW Delivery: R_QNCB.15.26.2_11.WR.mips.rmp LDAP Configuration: config-R_QNCB.15.26.2_11.WR.mips.rmp-INITIAL Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.15.26.2_11.WR.mips.rmp/ Path to RNW database dump: N/A (No dump created for this build) 3 Activate the upgraded build. Activate the upgraded build with status SW Build status: NW. Step example > set sw-manage activate delivery-label R_QNCB.15.26.2_11.WR.mips.rmp Confirm to proceed. CFPU-0@RNC-223 13:38:09 +0530] Are you sure you want to proceed? [y/N]: y CFPU-0@RNC-223 [2016-02-05 Step result The upgraded build is activated. To check the result enter:> show sw-manage app-sw-mgmt builds active. SW Delivery: R_QNCB.15.26.2_11.WR.mips.rmp is in SW Build status: NW (Active). CFPU-0@RNC-223 [2016-02-05 13:46:35 +0530] SW Build name: 20160205_A SW Build status: NW (Active) SW Delivery: R_QNCB.15.26.2_11.WR.mips.rmp DN09203161Issue:02 ©2016Nokia 445 RNC solution features WCDMA 16 Feature Descriptions and Instructions LDAP Configuration: config-R_QNCB.15.26.2_11.WR.mips.rmp-INITIAL Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.15.26.2_11.WR.mips.rmp/ Path to RNW database dump: N/A (No dump created for this build) The upgraded build is not a part of the BPS.To check the result enter: > show swmanage bps all. SW Delivery: R_QNCB.15.26.2_11.WR.mips.rmp is not present: CFPU-0@RNC-223 [2016-02-05 13:46:10 +0530] BPS name : 20160204_A Default: N Base : SW build name : 20160204_A SW build status : UT SW delivery : R_QNCB.15.26.2_10.WR.mips.rmp LDAP configuration: config-R_QNCB.15.26.2_10.WR.mips.rmp-Rakesh ILMFS files : SS_ILMFS/R_QNCB.15.26.2_10.WR.mips.rmp RNW database : DB/R_QNCB.15.26.2_10.WR.mips.rmp NE files : SWBuilds/ID_20160204224726209596_UNDEF/NEFiles RNC service ID : 223 SW build name : BK_223_15 SW build status : BU SW delivery : R_QNCB.15.26.2_10.WR.mips.rmp LDAP configuration: config-R_QNCB.15.26.2_10.WR.mips.rmpBK20160205092927 ILMFS files : SS_ILMFS/R_QNCB.15.26.2_10.WR.mips.rmpBK20160205092927 RNW database : DB/R_QNCB.15.26.2_10.WR.mips.rmpBK20160205092927 NE files : SWBuilds/ID_20160205092927985228_BACKUP/NEFiles • Returning to the base build of an old BPS after a new SW build has been activated. Sub-steps 1 Activate the old backup build. If the operator wants to return to the base build of an old BPS after the new SW build has been activated, the operator must activate the old backup build first with: > set sw-manage app-sw-mgmt activate sw-build-status BU Step result CFPU-0@RNC-223 [2016-02-05 14:58:48 +0530] ****************** WARNING ***************** System restart requested 446 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features ****************** WARNING ***************** Are you sure you want to proceed? [y/N]: y CFPU-0@RNC-223 [2016-02-05 14:58:49 +0530] Note: This command might take a few minutes before showing any results. Please be patient. The target build is the backup build belongs to BPS 20160204_A. Do you want to continue? [y/n]:y 2 Perform resiliency switch back and unload RNCSRV. > start network-resiliency unload Step result CFPU-0@RNC-223 13:47:22 +0530] Are you sure you want to proceed? [y/N]: y CFPU-0@RNC-223 13:47:23 +0530] [2016-02-05 [2016-02-05 Note: This command might take a long time. Please be patient. The unloading of RNC service 223 is executed. Post requisites Deactivation and activation of RNCSRV can be done with the resiliency commands when the upgraded build is active. > start network-resiliency deactivate CFPU-0@RNC-223 [2016-02-05 13:47:07 +0530] Are you sure you want to proceed? [y/N]: y CFPU-0@RNC-223 [2016-02-05 13:47:09 +0530] The deactivation of RNC service 223 is executed. The unload is not possible as the upgraded build is not a part of the BPS. 8.3.8.1.10.5 Deleting BPS fallback Instructions for deleting BPS fallback. Before you start The user cannot delete BPS which is currently operating. Procedure 1 Delete BPS fallback. Step example DN09203161Issue:02 ©2016Nokia 447 RNC solution features WCDMA 16 Feature Descriptions and Instructions > delete sw-manage bps name BPSFB3 Step result ************ WARNING ************* The BPS deletion is requested! ************* WARNING ************* Are you sure you want to proceed? [Y/n]: y Delete backup physical rnc system! BPS name : BPSFB3 Base build : BPSFB3 RNC service: 00001 All backup builds and base build will be deleted from disk! Each RNC service deletion may need several minutes, please be patient!! Backup build for RNC service 00001: Build on deleting ... Deletion is successful Base build: Build on deleting ... Deletion is successful BPS fallback messages for deletion abort. When BPS fallback deletion was aborted while backup build was deleted, the following message occurs: root@CFPU-0 [BCN_211] > delete sw-manage bps name BPSFB1 ************** WARNING *************** The BPS deletion is requested! ************** WARNING *************** Are you sure you want to proceed? [Y/n]: y Delete backup physical rnc system! BPS name : BPSFB1 Base build : BPSFB1 RNC service: 00001 All backup builds and base build will be deleted from disk! Each RNC service deletion may need several minutes, please be patient!! Backup build for RNC service 00001: Build on deleting ... Try to abort build deleting ... 448 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Build deleting is aborted [warning] The left BPS is incomplete! When BPS fallback deletion was aborted while the base build deletion is ongoing, the following message occurs: root@CFPU-0 [RNC-221] > delete sw-manage bps name BPSFB3 CFPU-0@RNC-221 [2015-10-08 12:20:40 +0530] ***************** WARNING ****************** The BPS deletion is requested! ***************** WARNING ****************** Are you sure you want to proceed? [Y/n]: y CFPU-0@RNC-221 Prepare for deleting Backup Physical RNC System! BPS name : BPSFB3 Base build : BPSFB3 RNC service: 222 [2015-10-08 12:20:42 +0530] Start deletion! All backup builds and base build will be deleted from disk! Each RNC service deletion need several minutes, please be patient!! Backup build for RNC service 222: Build on deleting ... Deletion is successful Base build: Build on deleting ... The last is build deletion is ongoing and cannot be aborted. Please wait until it finishes Deletion successful Interruption attempted by user - but the task was completed and executed successfully Related descriptions Configuring GIVAXI/givClienton page 300 Backup Physical RNC System managementon page 360 8.3.9 RAN2512: Network Resiliency for RNC2600 General information on RAN2512: Network Resiliency for RNC2600 feature for RNC2600 radio access network controller. Introduction to the feature The RAN2512: Network Resiliency for RNC2600feature is dedicated for the WCDMA Radio Network Controller- RNC2600. The feature improves network availability. This feature allows RAN recovery from fatal HW failure of a single controller or the controller's site. When one physical controller has failed, the operator is able to command the earlier-configured and synchronized backup physical controller to take over the responsibility of the failed physical controller. This feature helps to avoid long outages, lasting many hours or days. 8.3.9.1 RAN2512 Benefits End-user benefits DN09203161Issue:02 ©2016Nokia 449 RNC solution features WCDMA 16 Feature Descriptions and Instructions This feature improves network services availability in case of catastrophes. Operator benefits This feature shortens the controller's outage time in the radio network. 8.3.9.2 RAN2512 Functional description Functional overview The RAN2512: Network Resiliency for RNC2600feature is related to RNC2600 WCDMA RAN network controller. The feature improves network availability during single outages and the controllers site outages. This feature introduces the following definitions: • • • Physical RNC (PRNC) which is a RNC HW with SW installed. Backup PRNC (BkPRNC) which is a PRNC configured only for redundancy purposes; it does not have its own radio access network under control. Protected PRNC (PrPRNC) which is a PRNC with running network services protected by BkPRNC. With this feature, the operator can introduce BkPRNC to protect a PRNC in the network. In case a PrPRNC fails, the BkPRNC is commanded by the operator to take over the RAN and interfaces, and to run the PrPRNC's services. RNC2600 capacity step3 can backup RNC2600 capacity step1/step2/step3. One RNC2600 configured as BkPRNC is able to protect up to 16 RNC2600s. One PrPRNC has one BkPRNC configured, so that the redundancy mode is N+1. The PrPRNC and the BkPRNC can be in the same physical site or in different sites. The intra-site resiliency is useful when the operator wants to do on-site maintenance to the PrPRNC. With the activation of redundancy switch the BkPRNC takes over the PrPRNC's responsibilities. This makes it possible to shut down or isolate the PrPRNC. The benefits of intra-site resiliency are that the network's KPIs do not decrease and that scheduled or sudden maintenance work can be done. The inter-site resiliency is needed in case there is, for example, a fire or a natural disaster like an earthquake that can destroy the whole site. To improve network stability and availability in this case, the BkPRNC must be placed in another site.This site must not be affected by a disaster when the disaster happens in the area where the PrPRNC is placed. This feature introduces a new RNC-cluster (RNC-cl) O&M interface, which connects PrPRNC with BkPRNC. This new interface is used for synchronizing the BkPRNC configuration with the PrPRNCs' configurations. The file transfer between PrPRNC and BkPRNC is necessary. Because a configuration package, which is synchronized between PrPRNC and BkPRNC, contains sensitive data the secure file transfer is possible and advised. System supports both secure and insecure file transfer in RNC-cl O&M interface. The graphic shows in general the resiliency idea and introduces an example network concept. 450 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Network resiliency transport network concept Figure 77 NetAct RNC solution features OMS RNC SGSN SGSN MSS/MGW O&M CBC server Core SiteA PrPRNC SAS server Site B PrPRNC BkPRNC PrPRNC PrPRNC BkPRNC Backhaul Active Standby RNC-cl O&M OMS NetAct NetAct connection 8.3.9.3 The link exists only if BkPRNC is activated. RAN2512 System impact Interdependencies between features This feature requires full IP protocol support, thus the following features' activation is required: • • • • • DN09203161Issue:02 RAN74: IP Based Iub for Flexi WCDMA BTS feature RAN75 IP based Iu-CS feature RAN2276 IP based Iu-BC feature RAN750 IP based Iu-PS feature RAN76 IP based Iur feature ©2016Nokia 451 RNC solution features WCDMA 16 Feature Descriptions and Instructions RAN1874: Automatic OMS Resiliencyfeature supportsRAN2512: Network Resiliency for RNC2600 feature. RAN2512: Network Resiliency for RNC2600does not impact on RAN1874: Automatic OMS Resiliency Impact on interfaces This feature introduces a new RNC-cl O&M interface. The feature introduces non-active backup SCTP associations in IP based Iu and Iur interface. This may cause unnecessary alarm. With RNC2600, the unnecessary alarm can be configuration suppressed by tagging backup associations described in Creating M3UA in Configuring SS7 SCTP Signaling Transportas over IP for IPA-RNC . Impact on commands This feature introduces new commands, which are listed and described in Managing Software This feature is managed by the parameters listed inParameters. Impact on network and network element management tools This feature can be managed in NetAct using the optionalRAN3226: NetAct Topology View to Network Resiliency of RNC feature. See RAN3226: NetAct Topology View to Network Resiliency of RNC and NetAct topology view for more information. This feature introduces a new RNW object called PRNC, which represents PrPRNC or BkPRNC. The object can be seen in OMS EM regardless of whether the feature is activated or not. The BkPRNC object can be seen in NetAct only after RAN3226: NetAct Topology View to Network Resiliency of RNChas been activated. Figure 78 PrPRNC icon Figure 79 BkPRNC icon This feature impacts network management or network element management tools as described in Miscellaneous notes Impact on system performance and capacity This feature impacts system performance and capacity as follows: • • 8.3.9.4 For every 1-16 protected controllers, at least onebackup BkPRNC is required, with the highest configuration (the amount of BkPRNCs depends on the required redundancy level). Transport links between BTSs under PrPRNCs and BkPRNC and between BkPRNC and core or other controllers must be sufficient to carry whole traffic RAN2512 Reference data Requirements 452 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 183 Software requirements RAS F l e x iD i r e c t RU50 EP1 Support not required BTS Flexi 10 WN9.1 RNC solution features I PA - R N C RN8.1 NetAct mcRNC OMS Support not required OMS3.1 MSC NetAct 8 EP2 (NetAct 15) Support not required SGS N Support not required B T SF l e x i WN9.1 MGW Support not required F l e x iL i t e WL9.1 UE Support not required This feature requires the following hardware: • • • g To configure BkPRNC- RNC2600 capacity step3 with full CCP1D-A is required. To configure PrPRNC- RNC2600capacity step1 or step2, orstep3. Both CCP18-C and CCP1D-A configurations are supported. Flexi Multimode System Module FSMC/D/E or Flexi Multiradio SystemModule FSMF or Flexi Lite BTS. Note: We recommend to purchase new hardware (capacity step 3) to configure BkPRNC on the dedicated PRNC. Only network configured with full IP Iub, Iur, Iu-PS, Iu-CS interfaces allow to fully use the advantages provided by this feature. It requires BTS sites to be connected to the protected RNCs via IP Iub interface in order to have them controlled by BkPRNC after redundancy switch. This is the precondition to enable RNC resiliency synchronization and switchover operations. It is possible to enable the feature in networks where some BTSs have ATM Iub or Dual Iub configuration. In case of a disaster or prepared redundancy switch, only the IP sites are switched over to backup RNC. ATM Iub sites are not switched over, but they do not prohibit the resiliency operations for the IP Iub BTS sites. After redundancy switch, the ATM/dual Iub BTSs remain online as the PrPRNC’s ATM interfaces are not shut down. However, when PrPRNC loses Iu connection, it sends system information block (SIB) that there is no Iu service to the UE connected to BTS configured with ATM Iub interface. After receiving this information, the UEs might not connect to the indicated BTSs. The actual UE behavior depends on the vendor’s implementation. The SIB sending is managed using RNC-IUO-IuBarring* parameters. t Tip: You may restore protected and/or srcinal RNC with the full initial configuration using the normal RNC restore functionality. Alarms Table 184 New alarms introduced in RAN2512 A l a r mI D A l a r mn a m e Schedule problem 3877 RNC RESILIENCY SYNCHRONIZATION MISSING 3876 RNC RESILIENCY ADAPTION MISSING Configuration problem DN09203161Issue:02 ©2016Nokia 453 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 184 New alarms introduced in RAN2512 (Cont.) A l a r mI D A l a r mn a m e 3835 RNC SERVICE CONFIGURATION MISSING OR INCOMPLETE Operation problems and notices 3831 DATA SYNCHRONIZATION FAILURE 3834 BACKUP BUILD FAILURE 0226 RNC SERVICE ACTIVATION 3833 RNC SERVICE DEACTIVATION FAILED IN PEER PRNC 3839 ACTIVITY CHECK WITH BACKUP ASSOCIATED PRNC FAILED 3832 ACTIVATION OF RNC SERVICE FAILURE 3734 RNC CLUSTER O&M CONNECTION FAILURE 3429 CRITICAL FAULT IN BKPRNC 3436 MAJOR FAULT IN BKPRNC 3361 NE CONFIGURATION IS WRONG Table 185 Existing alarms related to RAN2512 A l a r mI D A l a r mn a m e 2081 OMS SWITCHOVER HAS BEEN PERFORMED 3295 LICENCE CAPACITY EXCEEDED Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 186 New parameters introduced by RAN2512 F u l ln a m e A b b r e v i a t e dn am e OAM Connection Establishment Retry Counter OMS backup IP Address OMSBackupIpAddress OMSIPAddress OMSIpAddress Physical RNC Change Origin Physical RNC Identifier PRNCChangeOrigin PRNCId Physical RNC IPv4 Address PRNCIP4Address M a n a g e do b j e c t PRNC PRNC PRNC PRNC PRNC PRNC PhysicalRNCMode PRNCMode PRNC PhysicalRNCName PRNCName PRNC PRNC Client TLS Mode 454 ConnectionRetryCounter PrncClientTLSMode ©2016Nokia PRNC DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 186 RNC solution features New parameters introduced by RAN2512 (Cont.) F u l ln am e A b b r e v i a t e dn am e Secondary OMS IP address ServingOMS SecOMSIpAddress ServingOMS M a n a g e do b j e c t PRNC PRNC Serving OMS admin setting ServingOMSAdminSetting PRNC Serving OMS Switchover Request ServingOMSSwoRequest PRNC Activity Mode ActivityMode PRNC/RNCSRV RNC service Change Origin RNCSRVChangeOrigin RNC SERVICE Identifier RNCSRVId PRNC/RNCSRV PRNC/RNCSRV RNC service status ServiceStatus PRNC/RNCSRV Source IP address for IuBC interface CBCSourceIPAddress PRNC/RNCSRV Automatic adaption control AutoAdaptation PRNC/RNCSRV/DATSYN Backup completeness of the backup configuration BackupCompleteness PRNC/RNCSRV/DATSYN Backup update Time for RNC configured data BackupUpdateTime PRNC/RNCSRV/DATSYN Data synchronization Change Origin DATSYNChangeOrigin PRNC/RNCSRV/DATSYN Data Synchronization DATSYNId PRNC/RNCSRV/DATSYN Data synchronization state DataSynchState PRNC/RNCSRV/DATSYN RNC cluster O&M interface link status RNCClusterOMLnkState PRNC/RNCSRV/DATSYN Scheduling periodic data synchronization in days DataSyncDays PRNC/RNCSRV/DATSYN Scheduling periodic data synchronization in hours DataSyncHours PRNC/RNCSRV/DATSYN Scheduling periodic data synchronization in minutes DataSyncMinutes PRNC/RNCSRV/DATSYN Active Physical RNC ActivePRNC RNC Alarm status at backup PRNC AlarmStatus RNC/BKPRNC Backup Physical RNC Identifier BkPRNCId RNC/BKPRNC Backup PRNC client TLS BKPRNCTLSClientMode RNC/BKPRNC Mode for RNC Rlc O&M link Backup PRNC current Activity Mode ActivityMode RNC/BKPRNC Identifier Backup PRNC name Backup PRNC unknown status DN09203161Issue:02 PRNCName UnknownStatus ©2016Nokia RNC/BKPRNC RNC/BKPRNC 455 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 186 New parameters introduced by RAN2512 (Cont.) F u l ln a m e A b b r e v i a t e dn am e Backup RNC IPv4 Address used for establishing RNC cluster O&M interface M a n a g e do b j e c t RNC/BKPRNC Backup update time at backup BackupUpdateTime PRNC RNC/BKPRNC BKPRNC Change Origin BKPRNCChangeOrigin Configuration completeness at BackupCompleteness backup PRNC RNC/BKPRNC RNC/BKPRNC RNC cluster O&M interface link status RNC/BKPRNC Table 187 RNCClusterOMLnkState Parameters modified by RAN2512 Full name Abbreviated name Managed object RNC Identifier RncId RNC RNC Options RNC Table 188 RncOptions BTS Parameters F u l ln a me Additional RNC configuration structure A b b r e v i a t e dn a m e addRncConfig TMPAR Currently used far end SCTP tunnel IP address currentSctpIpAddress TMPAR Far End SCTP Subnet IP Address farEndSctpSubnetIpAddress TMPAR Far End SCTP Subnet Mask g BackUpRNCIP4Address farEndSctpSubnetMask M a n a g e do b j e c t TMPAR Note: Far End SCTP Subnet IP Address and Far End SCTP Subnet Mask are placed under Backup RNC configuration in BTS Site Manager. Sales information Table 189 Sales information BSW/ASW SW component License control in network element ASW RAN RNC Resiliency LK in PrPRNC. For SFTP enabled, SSH license is necessary. Term Bank 456 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 190 RNC solution features Descriptions of feature-related terms Te r m D e s cr i p t i o n s Adaptation Replacing the local information of PrPRNC by local information of BkPRNC. Auto-adaptation Adaptation done automatically according to mapping tables configured by the user. Automatic procedure of auto- The sequence of auto-adaptations of all BkRNCSRVs, including adaptation automatic loading of each BkBuild before doing the auto-adaptation for it. Backup build A build that BkPRNC runs when certain RNC service was selected for operation. t Backup configuration Configuration package of a backup build. Backup configuration consists of global part that is copied from PrPRNC and local part that is configured by operator using MML (or using OMS EM, when it becomes available). t Base build BTS(WBTS) Tip: See also: Backup build. Configuration package of the base build. t BkPRNC Tip: See also: Base configuration, Preconfiguring A build that BkPRNC runs when no RNC service has been selected for operation. t Base configuration Tip: See also: Base build. Tip: See also: Backup configuration. Backup PRNC - PRNC that can back up the RNC services of up to 16 PrPRNCs. WCDMABTS BTSOM BTS O&M application protocol - the protocol used in RNC O&M I/F, BTS O&M I/F and RNC-cl O&M I/F. BTS O&M I/F BTS O&M interface - O&M interface between RNC and BTS, using BTSOM as the protocol. t Tip: See also RNC O&M I/F and RNC-cl O&M I/F. BTSSM BTSsitemanager Build Collection of programs and files performing required functions of a system. BkPRNC has a base build for the PRNC and a backup build per each related PrPRNC. In RNC2600 build consists of configuration data and SW image. cRNC ClassicRNC t Configuration (package) DN09203161Issue:02 Tip: See IPA-RNC The whole configuration of a build, which does not contain the SW image. ©2016Nokia 457 RNC solution features Table 190 WCDMA 16 Feature Descriptions and Instructions Descriptions of feature-related terms (Cont.) Te r m D e s cr i p t i o n s t Tip: See also: Build. Configuration committing A command which tells to the system that the user configuration is done and is ready for configuration adaptation and integrity check. Conversion Converting a configuration package from old SW build to new SW build. g IPA-RNC LRNC Note: Conversion is not particularly related to RNC resiliency. Conversion is done at any SW upgrade, with or without resiliency. IPA-RNC-OldRNCHW • HW: Cabinets, subracks, different PIUs • OS: DMX, Chorus, OSE • Platform: IPA2800 Logical RNC - RNC as defined by 3GPP. See also PRNC, RNC, RNC service. In standard system, LRNC is 1-1 with RNC and PRNC. In RAN2512, LRNC is 1-1 with RNC but 1-2 with PRNC. NetAct Nokia product for network management OMS O&MserverforRNC. Object configuration Configuration of the local part of a backup configuration, which includes the adaptation rules. Operator configure required objects any time after first synchronization but before activating the RNC service. A manual configuration step must be done when RNCSRV is created in BkPRNC, and at certain modifications. PRNC Physical RNC - RNC HW and SW. This term is introduced because BkPRNC cannot be called as a RNC. It does not run RNC service but waits to be switched on in case of PrPRNC outage. t Tip: See also LRNC, RNC, RNC service. PrRNC Protected RNC - RNC that has more than one redundant RNC service, one in PrPRNC and another in BkPRNC Redundancy conflict The undesirable situation where certain RNC is active in more than one PRNC simultaneously. Redundancy conflict is a new fault scenario introduced by RNC resiliency. Redundancy conflict could happen for example, if redundancy switch to BkPRNC is done when PrPRNC is down and thus the RNC service in PrPRNC cannot be deactivated. If then PrPRNC recovers and if operator has not physically isolated it, there will be redundancy conflict. In redundancy conflict, network may not work, because other NEs may connect to more than one PRNC simultaneously. Redundancy switch Switch of (activity of) certain RNC from PrPRNC to BkPRNC. Two redundancy types can be distinguished: • 458 Prepared redundancy switch: redundancy switch where the activating RNCSRV has been raised to LOADED mode before commanding the switch. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 190 RNC solution features Descriptions of feature-related terms (Cont.) Te r m D e s cr i p t i o n s • Unprepared redundancy switch: redundancy switch where the activating RNCSRV not been raised LOADED mode before commanding the switch. Redundancy switchback Switch of (activity of) certain RNC from BkPRNC to PrPRNC. RNC Common meaning: Radio network controller. In RNC pool context also: Logical functionality that can run simultaneously as an RNC service in a PRNC. Defines the state in which the RNCSRV is. Values are: waiting for synchronization, backup, loaded and active. RNC activity mode RNC area Geographical area covered by the BTSs and cells that the RNC controls. RNC-cl O&M I/F RNC cluster O&M interface (Informally Cluster O&M interface) - O&M interface between two RNCs, using BTSOM as the protocol. t RNC O&M I/F Tip: See also BTS O&M I/F and RNC O&M I/F. RNC O&M interface - O&M interface between OMS and RNC, using BTSOM as the protocol. t Tip: See also BTS O&M I/F and RNC-cl O&M I/F. RNC resiliency group A BkPRNC and all the PrPRNCs protected by it. RNC service The instance of an RNC in certain PRNC. t RNCSRV activation / deactivation Tip: See also LRNC, PRNC, RNC. Transition between different RNC modes which can be a separate operation or a phase of redundancy switch or switchback. • • RNCSERV activation refers to RNC mode changed from LOADED to ACTIVE RNCSERV deactivation refers to RNC mode changed from ACTIVE to LOADED . Service status Defines what the BkPRNC is actually doing. This is useful with long lasting operations. Some values are: Idle, creating RNC service, synchronizing data. StPRNC Standard PRNC - PRNC that does not participate in RNC resiliency. Synchronization Automatic fetching of configuration package of certain RNC service from corresponding PrPRNC and adaptation to BkPRNC according to adaptation rules. Miscellaneous notes Table 191 Limitations L i mi t e da r e a Network and network element management tools DN09203161Issue:02 D e s c r i p t i o no ft h el i m i t at i o n • BkPRNC is not visible in NetAct as individual RNC object if RNCSRV is not active in BkPRNC. In this case, the status of ©2016Nokia 459 RNC solution features Table 191 WCDMA 16 Feature Descriptions and Instructions Limitations (Cont.) L i mi t e da r e a D e s c r i p t i o no ft h el i m i t a t i o n • • Software management • BkPRNC is visible in NetAct through parameters of RNC object of PrPRNC. When RNCSRV is active, BkPRNC takes the role of PrPRNC in NetAct. This feature can be managed in NetAct using the optional RAN3226: NetAct Topology View to Network Resiliency of RNC feature. Do not to execute RNW or IP plan uploads or downloads at PrPRNC operationduring failure.synchronization because of high risk of plan Do not execute synchronization when planned operation is ongoing because of risk of synchronization failure. The failure or success of the operation depends on the phase of other ongoing operation. TRIAL configuration TRIAL configuration is a standard upgrade method applicable only when updated PrPRNC's RNCSRV is in ACTIVE mode. Nevertheless, there are some restrictions related to this method: 1. During TRIAL configuration resiliency relevant operation are rejected. 2. When RNCSRV is in LOADED mode, any TRIAL relevant operation is rejected. g Note: TRIAL is strongly forbidden in BkPRNC. Because BkPRNC operates after the user performed redundancy switch, there is usually no active RNCSRV. 8.3.9.5 Activating, operating, and maintaining RAN2512: Network Resiliency for RNC2600 8.3.9.5.1 RAN2512: Network Resiliency for RNC2600 activation procedure overview Important f Keep the BkPRNC always powered on, also in resiliency idle (when RNCSRV is not active on BkPRNC). Trying to save energy by powering off the BkPRNC can cause serious problems because PrPRNC and BkPRNC are not synchronized. Troubleshooting In case of any alarm described inRAN2512: Network Resiliency for RNC2600 management data occurs, follow the instructions given by alarm help or refer to Reference documentation. 8.3.9.5.2 Activating RAN2512: Network Resiliency for RNC2600 Purpose This chapter provides procedures on how to activateRAN2512: Network Resiliency for RNC2600 feature. Assumed and expected network plan is shown in the Figure 80: Network transport plan 460 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Network transport plan Figure 80 OMS-1 OMS-2 10.43.7.18 10.58.239.68 PrPRNC-221 BkPRNC-301 O&M RNCId-221 ICSU ... RNCId-221 ICSU ICSU 10.43.12.1/26 NPGE ... ... ICSU 10.43.7.192/26 NPGE NPGE 10.43.5.1/24 ... NPGE 10.43.6.1/24 O&M:10.63.56.215 O&M:10.62.85.16 in standby for backup service activation 8.3.9.5.2.1 Commissioning BkPRNC Before you start Before performing of this procedure make sure: • • Capacity licenses of BkPRNCare equal or bigger than capacity licenses inPrPRNC. IDs of PRNCs in resilient network do not collide. Procedure 1 Install an d activate licenses. The feature requires: • licenses mandatory only for PrPRNC – • 4784: RAN2512 RNC Resiliency licenses mandatory in both PrPRNC and BkPRNC – – RAN1198 Iub throughput 1 Mbit/s RAN1198 AMR capacity 1 Erl – RAN1623 Carrier connectivity w These license will compare the capacity of BkPRNC against capacity of PrPRNC. If capacity of BkPRNC is less than PrPRNC, then Data Sync will not be performed. 2 DN09203161Issue:02 Commission PRNC to BkPRNC. ©2016Nokia 461 RNC solution features WCDMA 16 Feature Descriptions and Instructions Sub-steps a) Log in to active OMU: > ZDDS; b) Start remote session with the following command in order to create a PRNC object: 0000-MAN>ZLE:1,RUOSTEQX c) Create RNC with the following command: 0000RUO>Z1CM:<prnc_id>,<pri_oms_ip>,[<prnc_mode>] ,[<prnc_name>],[<sec_oms_ip>],[<serving_oms>],[<retries>] ; g Note: The PRNCId of every created BkPRNC must be unique. It cannot collide with the RNCId of any of the PrPRNC’s configured into resilient network. Step example Assign ID to PRNC (301), Primary OMS IP address (10.43.7.18), switch controller to backup mode (2), name of the BkPRNC (Brine), Secondary OMS IP address (10.58.239.68), serving_oms(0), retries (10) with the following command: 0000-RUO>Z1CM:301,10.43.7.18,2,Brine,10.58.239.68,0,10 Step result Connecting to RNW database... PRNC-301 creation (mode: backup) completed successfully at 26-03-2014 18:47:16.28 Closing RNW database connection... 0000-RUO> C Operation starting at: 26-03-2014 18:47:21.95 Connecting to RNW database... RNC object not found. PRNC information: ----------------------------------------------------PRNC ID: 301 PRNC mode: 2 (Backup) PRNC IP address: 10.62.85.16 Restart reason: 0 (Normal restart) ----------------------------------------------------- 462 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 3 RNC solution features Check if the BkPRNC commissioning is successful. Type the following command:0000-RUO>Z1C Step result Operation starting at: 13-08-2014 23:45:27.32 Connecting to RNW database... RNC object not found. PRNC information: ----------------------------------------------------PRNC ID: 301 PRNC name: Brine PRNC mode: 2 (Backup) PRNC IP address: 10.62.85.16 Restart reason: 0 (Normal restart) Primary OMS IP address: 10.43.7.18 Secondary OMS IP address: 10.58.239.68 Backup OMS IP address: 0.0.0.0 Current serving OMS: 1 (primary OMS) Serving OMS selection: 0 (automatic) Connection retry count: 10 RNC Client TLS mode: 2 (Probing) ----------------------------------------------------Closing RNW database connection... 0000-RUO> The BkPRNC is connected to OMS automatically after BkPRNC commissioning and PRNC object was created. 4 Ensure that one BPS has been generated after the commissioning. < ZWMI; Step result LOADING PROGRAM VERSION 1.5-0 BPS NAME ENVIRONMENT DEF ROLE BUILD STATUS RNC-SERVICE-ID DIRECTORY PACKAGE-ID (REP-ID) DELIVERY QX143060DEV 14.30-60 CD-ID Y BASE BU QX143060DEV QX QX 14.30-60 CID000QX 15.1-0 TOTAL BPS: 1 DN09203161Issue:02 ©2016Nokia 463 RNC solution features WCDMA 16 Feature Descriptions and Instructions COMMAND EXECUTED 8.3.9.5.2.2 Configuring network resiliency using OMS Element Manager Purpose This chapter instructs how to configure OMS in order to act in the resilient network. The operator is able to connect 20 PRNC/RNC pairs to one OMS and additionally 10 PRNCs (without RNC service). BKPRNC object is on the feature license and there is no restriction for creating it. This object needs to point out to the PRNC object that is already in the topology. Procedure 1 t Commission BkPRNC. Tip: Commission BkPRNC only if this procedure has not been done yet. If it has been done, ensure BkPRNC managed object presence in GUI and proceed with step Create RNCSRV in BkPRNC. Step result BkPRNC is present on OMS as shown in the Figure 81: Example view of BkPRNC managed object visible in OMS GUI Figure 81 2 Example view of BkPRNC managed object visible in OMS GUI Create RNCSRV in BkPRNC. Open OMS Element Manager. Go to the specific BkPRNC ID. Right-click on it and create RNCSRV usingCreate new objectoption. 464 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 3 RNC solution features Create BkPRNC ob ject for P rPRNC. BkPRNC object must occur under the following pathROOT ► RNC-<ID> ► BkPRNCs. BkPRNC IP address is visible under Backup RNC IPv4 Address used for establishing RNC cluster O&M interface. 4 Add another PrPRNC. Repeat steps Create RNCSRV in BkPRNC. and Create BkPRNC object for PrPRNC. if you want to add another PrPRNC. 8.3.9.5.2.3 Configuring network resiliency using MML commands Purpose This is an example configuration ofRNCSRV, which shows the rule of network configuration. t Tip: It is also possible to create RNCSRV using OMS Element Manager. Omit this chapter if it has been already done. Before you start All commands in this procedure are given in base build ( ACTIVITY MODE: BACKUP). Ensure that RNC is operating on it with the following commandZE1I;. Procedure 1 Create RNC service ( RNCSRV). Type the following command: [ZE1A:<PrPRNC_ID>] Step example ZE1A:221:; Step result t Tip: This action takes approximately 6 minutes in background, after the following system output has been displayed. LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION FOR RNCSRV-221 IS ADDED SUCCESSFULLY COMMAND EXECUTED DN09203161Issue:02 ©2016Nokia 465 RNC solution features WCDMA 16 Feature Descriptions and Instructions 2 Check service status. Check whether SERVICE STATUS is CREATING SERVICE . < ZE1I; Step result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: CREATING SERVICE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: DISABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED 3 Ensure RNC resiliency association was correctly added to the RNC service. Check the RNC service statuses by displaying it several times using the following command: < ZE1I; LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 466 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED Step result RNC resiliency association was correctly added to the RNCSRV when RNC CLUSTER LINK STATUS is ENABLED. 4 In OMS, check topology after RNCSRV object creation at BkPRNC. 5 Ensure that new backup build has been added to BPS. < ZWMI; Step result COMMAND EXECUTED < ZWMI; LOADING PROGRAM VERSION 1.5-0 BPS NAME ENVIRONMENT DEF ROLE BUILD STATUS RNC-SERVICE-ID DIRECTORY PACKAGE-ID (REP-ID) DELIVERY CD-ID QX143060DEV 14.30-60 Y BASE NW QX143060DEV QX QX 14.30-60 CID000QX 15.1-0 BKUP UD BK00301_13 QX 14.30- 60 00301 QX 14.30-60 CID000QX 15.1-0 TOTAL BPS: 1 COMMAND EXECUTED 8.3.9.5.2.4 Activating PrPRNC for RNC resiliency RNC is automatically configured as a standard PRNC after RU50 EP1 SW upgrade. DN09203161Issue:02 ©2016Nokia 467 RNC solution features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Interrogate PRNC object. Check RNC is configured as standard PRNC with the following command: < ZE1I; Step result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: STANDARD RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE 2 Install RAN2512 feature license and activate it. Enter the following command: ZW7L:; Step result Feature code 4784 is ON. 3 Add RNC resiliency association with BkPRNC. Add RNC resiliency association with BkPRNC by creating BKPRNC object in RNW DB. This enables the RNC-cl O&M at PrPRNC. Type the following command: ZE1A:<BkPRNC ID>:<BkPRNC IP>; Step example < ZE1A:301:10.62.85.16:; Step result RNC RESILIENCY ASSOCIATION WITH PRNC-301 WAS ADDED SUCCESSFULLY COMMAND EXECUTED 4 Check that the RNC resiliency association has been successfully added. Display RNC status and check BACKUP PRNC IP is visible. 468 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features < ZE1I; LOADING PROGRAM VERSION 1.17-0 RNC TYPE: PROTECTED RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE BACKUP PRNC ID: 301 BACKUP PRNC NAME: NOT UPDATED BACKUP PRNC IP: 10.62.85.16 BKPRNC ACTIVITY MODE: NOT UPDATED BKPRNC TLS CLIENT MODE: OFF BKPRNC ALARM STATUS: NOT UPDATED BACKUP COMPLETENESS: NOT UPDATED BKPRNC BACKUP UPDATE TIME: NOT UPDATED BKPRNC UNKNOWN STATUS: TRUE RNC CLUSTER O&M LINK STATE: DISABLED COMMAND EXECUTED Result Suitable objects appear in OMS EM Figure 82 8.3.9.5.2.5 RNC and PRNC objects in Topology Browser of OMS GUI Configuring secure RNC-cl O&M interface This chapter describes how to enable security for RNC-cl interface. DN09203161Issue:02 ©2016Nokia 469 RNC solution features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Configure cluster O&M interface. Perform these steps in both PrPRNC and BkPRNC. Sub-steps a) Copy the certificate files into both the PrPRNC and BkPRNC under /shadows folder. b) Check the files presence. Execute the following commands 1. 2. 3. 4. < ZDDS; 0000-MAN>ZLP:M,MAS 0000-MAS>ZMX:W0-/ ZIWX:,:WS,::%,%,,:; Step result In the /shadows folder in the RNC the files from the list below are present: • CERTXXXX.BIN • CACERT.BIN • PRIVATE.BIN c) Install the certificates. Install the previously copied certificates with the following commands: 1. ZQ4A:TLSPRIVATE,P:F,"W0-/PRIVATE.BIN":; 2. ZQ4A:TLSCERT,C:F,"W0-/CERTXXXX.BIN":; 3. ZQ4A:TLSCACERT,C:F,"W0-/CACERT.BIN":; d) Create SSL/TLS layer definition. ZI3C:OMU:TLSCERT,TLSPRIVATE:TLSCACERT:; e) Change the Client TLS mode to FORCED in PrPRNC. ZE1M:::FORCED; 470 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step result LOADING PROGRAM VERSION 1.19-0 PARAMETER OF BKPRNC-301 IS MODIFIED PREVIOUS TLS CLIENT MODE: OFF CURRENT TLS CLIENT MODE: FORCED COMMAND EXECUTED f) Check th e configuration correctness. ZQRS:OMU,0; g) Enable secure FTP ZI2H:PROTOCOL=SFTP:; Step result Port 8023 is used. 2 Configure RN C-OMS in terface. Sub-steps a) Copy the certificate files to OMS. Copy the certificate files to /tmp folder with the following commands: • cp /home/Nemuadmin/ca-certificate.pem /tmp • cp /home/Nemuadmin/cert.pem /tmp • cp /home/Nemuadmin/private.pem /tmp b) Install the c ertificates. Execute these commands in OMS root privilege mode: 1. omscertificate install-ca-cert -cert-file /tmp/cacertificate.pem 2. omscertificate install-ee-cert -cert-file /tmp/cert.pem -key-file /tmp/private.pem c) Change the Client TLS mode to PROBING (in OMS). Access the relevant parameter by the path: Application Launcher ► Parameter Tool ► ClusterRoot ► OMS ► System ► Network ► TLS ► TLSModeOM ► omsParameterValue DN09203161Issue:02 ©2016Nokia 471 RNC solution features WCDMA 16 Feature Descriptions and Instructions d) Change the C lient TLS mode to PROBING (in RNC). 1. ZDDS; 2. ZLE:1,RUOSTEQX; 3. 1 4. Z1CT:2; Step result This command may cause re-establishment of RNC-OMS O&M connection. Do you want to continue (Y/N) ? Y Connecting to RNW database... ----------------------------------------------------------Targeting operation to RNC object. ----------------------------------------------------------Current value for RncClientTLSMode: 2 - Probing. Changing value to: 2 - Probing. ----------------------------------------------------------Operation starting at: 23-07-2015 17:33:09.50 Request sent, waiting for acknowledgement... Operation succeeded. Closing RNW database connection... e) Check the configuration correctness: ZQRS:OMU,0; Step result Port 8003 is used. 8.3.9.5.2.6 Synchronizing RNCSRV Purpose This chapter provides procedures for manual and scheduled RNC service synchronization. Before you start It is recommended that the synchronization takes place when the PrPRNC's OMU load is low. synchronization schedules may overlap, also recommended that at someAlthough phasing the is considered so that the synchronization of itallisPrPRNCs does not start the same time. During synchronization BkPRNC must be in Backup mode. To switch to the mode, use the following commandZE1C:UNLOAD:; t 472 Tip: Rough time estimated for synchronization process is approximately 15 minutes per PrPRNC. This time period depend on factors like PrPRNC load, available bandwidth and overall network condition. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Synchronization works only if PrPRNC and BkPRNC have the same software versions. If PrPRNC and BkPRNC have different software versions, synchronization does not work, but redundancy switch and redundancy switch back can be executed. When the user modifies parameters in active BkPRNC and then does the redundancy switchback, the modified parameters are not populated to the PrPRNC which was protected. Procedure 1 Check RNC service status. Check RNC service in BkPRNC with the following command: ZE1I; Step result ACTIVITY MODE changes to BACKUP after adaptation and tests of downloaded configuration package. RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED 2 Set s cheduled s ynchronization ( optional). To schedule a synchronization in BkPRNC, type the following command: ZE1M:<PRNC ID>::::DAYS=xxx,TIME=HH-MM:; <xxx> implies following options: /* IDENTIFY DATA SYNC SCHEDULE DAYS: MON ... DATA SYNC ON MONDAYS DN09203161Issue:02 ©2016Nokia 473 RNC solution features WCDMA 16 Feature Descriptions and Instructions TUE WED THU FRI SAT SUN ... ... ... ... ... ... DATA DATA DATA DATA DATA DATA SYNC SYNC SYNC SYNC SYNC SYNC ON ON ON ON ON ON TUESDAYS WEDNESDAYS THURSDAYS FRIDAYS SATURDAYS SUNDAYS WOR HOL ALL NON ... ... ... ... DATA DATA DATA DATA SYNC SYNC SYNC SYNC ON HOLIDAYS( WORKDAYS( SAT,SUN MON,TUE,WED,THU,FRI ) ON ) ON EVERYDAY DAYS ALL CLEAR (FOUR &-SEPARATORS MAXIMUM, AND 'NON' WILL BE IGNORED WHILE USING &-SEPERATOR) */ Step example ZE1M:221::::DAYS=THU,TIME=08-13:; Step result PARAMETER OF RNCSRV-221 IS MODIFIED PREVIOUS DATA SYNC SCHEDULE: -,00:00 CURRENT DATA SYNC SCHEDULE: THU,08:13 COMMAND EXECUTED 3 Check the RNC service status. Check the RNC service status with the following command: < ZE1I; t Tip: It is recommended to check the status at time when the synchronization is ongoing. Step result ACTIVITY MODE changes from WAITING FOR SYNCHRONIZATION to BACKUP after synchronization is finished. SERVICE STATUS changes from SYNCHRONIZING DATA 474 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features to IDLE after synchronization is finished. a) LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: THU,08:13 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED b) LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: SYNCHRONIZING DATA CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: THU,08:13 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED DN09203161Issue:02 ©2016Nokia 475 RNC solution features WCDMA 16 Feature Descriptions and Instructions c) LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: BACKUP SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: THU,08:13 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: LESS THAN 100% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED 4 Test ba ckup c onfiguration. The backup configuration tests are triggered automatically after each synchronization and transport configuration commit. 5 Start manual sy nchronization ( optional). Start manual synchronization with the following command: ZE1S:START:<PrPRNC_ID>; Step example ZE1S:START:221:; SYNCHRONIZATION OF RNCSRV-221 IS STARTED COMMAND EXECUTED 8.3.9.5.2.7 Configuring associations to the core network Before you start Because all of the presented commands must be executed in LOADED mode, switch to the LOADED using the following command: < < ZE1C:LOAD:221; 476 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Perform described steps after RNC has started. Associations, which must be configured are shown in the Configuration matrix. Table 192 Configuration matrix Already done in base build No Necessary for entire BkPRNC 1. Cabling configuration Necessary for each RNCSRV 1. 2. 3. 4. 5. 6. Ethernet configurations VLAN configuration Configure IP addresses Configure Iu-CS control plane Configure Iu-PS control plane Configure Iu-CS user plane 1 7. Configure Iu-PS user plane 1 8. Configure IuB user plane 1 9. Configure BTS O&M Yes 1. Ethernet configurations 2. VLAN configuration 3. Configure IP addresses 4. Configure Iu-CS control plane 2 5. Configure Iu-PS control plane 2 1 Optional if auto-adaptation is enabled. Optional if RNCSRVs have common destinations. 2 Procedure 1 Configure alternate IP address of BkPRNC acting as PrPRNC-1 towards MSC. a) Create an association set. Type the following command: ZOYC:MSC2:C:M3UA:; b) Add associations to the association set. Type the following command: ZOYA:MSC2:ICSU,0:IETF:; ZOYA:MSC2:ICSU,1:IETF:; c) Configure association IP addresses: ZOYP:M3UA:MSC2,0:"10.43.6.18","10.43.6.26",:"10.71.4.215" ,25,"10.58.251.21",25,:; ZOYP:M3UA:MSC2,1:"10.43.6.19","10.43.6.27",2906:"10.71.4. 214",25,"10.58.251.18",25,2906:; d) Modify association set: ZOYM:MSC2:NETWORK=8:; e) Modify association state: ZOYS:M3UA:MSC2,0:ACT:; ZOYS:M3UA:MSC2,1:ACT:; DN09203161Issue:02 ©2016Nokia 477 RNC solution features WCDMA 16 Feature Descriptions and Instructions 2 Modify the own signaling point data. Type the following command: ZOCM:0:27,1:; Type the following command: ZNRP:NA0,D'8331,RNC:::; 3 Define the signaling service information data of own signaling point. Type the following command: ZNPC:NA0,03,SCCP:Y:Y,::; 4 Create a Signaling Connection Control Part (SCCP) for the signaling point. Type the following command: ZNFD:NA0,D'8331,0:8E,RANAP,0:; 5 Modify the parameter values of the existing SCCP signaling point parameter set. Type the following command: ZOCM:0:27,1:; a) MSC 1. Create IP type of signaling link set: ZNSP:NA0,D'8438,MSC2:0:MSC2:; 2. Create signaling route set: ZNRC:NA0,D'8438,MSC2,0,:,,,7::::; 3. Allow the activation of a signaling link: ZNLA:0:; 4. Allow the activation of a signaling route: ZNVA:NA0,D'8438::; 5. Change the signaling link state: ZNLC:0,ACT; 6. Change the signaling route state: ZNVC:NA0,D'8438::ACT:; 7. Define SCCP for signaling points with subsystem copy: ZNFD:NA0,D'8438,0:8E,RANAP,0,Y:::::; 8. Modify local broadcast status of SCCP subsystems: ZOBC:NA0,D'8438,01:NA0,8E:Y:; ZOBC:NA0,D'8438,8E:NA0,8E:Y:; 9. Modify broadcast status of SCCP signaling points: ZOYP:M3UA:RNCIUR1,0:"10.43.6.50","10.43.6.58",:"10.43. 5.172",27,"10.43.5.174",27,:; ZOYP:M3UA:RNCIUR1,1:"10.43.6.51","10.43.6.59",:"10.43. 5.173",27,"10.43.5.175",27,:; 10. Change the SCCP state of the signaling point: ZNGC:NA0,D'8332:ACT; 478 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features 11. Change the state of an SCCP subsystem: ZNHC:NA0,D'8332:8E:ACT; 12. Change the SCCP state of the signaling point: ZNGC:NA0,D'8438:ACT; 13. Change the state of an SCCP subsystem: ZNHC:NA0,D'8438:8E:ACT; Result Configuration visible at MSC: Configuration at MSC ASSOCIATION SET NAME -------------------RNC221 ASSOC SET ID -----------88 SCTP USER --------M3UA ROLE -------SERVER ASSOC. ASSOC ID PARAMETER SET IND UNIT IN UNIT NAME STATE --------- --------- ---------------- -------------------0 SIGU-0 --IETF SCTP-DOWN SOURCE ADDRESS 1 . . . . . : 10.71.4.215 SOURCE ADDRESS 2 . . . . . : 10.58.251.21 SOURCE PORT . . . . . . . : 2905 PRIMARY DEST. ADDRESS . . : 10.43.5.2/26 SECONDARY DEST. ADDRESS . : 10.43.5.3/26 DESTINATION PORT . . . . . : EPHEMERAL DATA STREAM COUNT . . . . : 16 ASSOC. ASSOC ID PARAMETER SET IND UNIT IN UNIT NAME STATE --------- --------- ---------------- -------------------1 SIGU-1 --IETF SCTP-DOWN SOURCE ADDRESS 1 . . . . . : 10.71.4.214 SOURCE ADDRESS 2 . . . . . : 10.58.251.18 SOURCE PORT . . . . . . . : 2905 PRIMARY DEST. ADDRESS . . : 10.43.5.10/26 SECONDARY DEST. ADDRESS . : 10.43.5.11/26 DESTINATION PORT . . . . . : EPHEMERAL DATA STREAM COUNT . . . . : 16 ASSOC. ASSOC ID PARAMETER SET IND UNIT IN UNIT NAME STATE --------- --------- ---------------- -------------------2 SIGU-0 --IETF DOWN-BY-USER SOURCE ADDRESS 1 . . . . . : 10.71.4.215 SOURCE ADDRESS 2 . . . . . : 10.58.251.21 SOURCE PORT . . . . . . . : 2905 PRIMARY DEST. ADDRESS . . : 10.43.6.2/26 SECONDARY DEST. ADDRESS . : 10.43.6.3/26 DESTINATION PORT . . . . . : EPHEMERAL DN09203161Issue:02 ©2016Nokia 479 RNC solution features WCDMA 16 Feature Descriptions and Instructions DATA STREAM COUNT . . . . : 16 ASSOC. ASSOC ID PARAMETER SET IND UNIT IN UNIT NAME STATE --------- --------- ---------------- -------------------3 SIGU-1 --IETF DOWN-BY-USER SOURCE ADDRESS 1 . . . . . : 10.71.4.214 SOURCE ADDRESS 2 . . . . . : 10.58.251.18 SOURCE PORT . . . . . . . : 2906 PRIMARY DEST. ADDRESS . . : 10.43.6.10/26 SECONDARY DEST. ADDRESS . : 10.43.6.11/26 DESTINATION PORT . . . . . : 2906 DATA STREAM COUNT . . . . : 16 Post requisites Similar configuration has to be done for IUPS and other relevant interfaces as well. 8.3.9.5.2.8 Configuring Iur interface towards neighboring RNCs Purpose This chapter describes steps for configuration of Iur interface between BkPRNC and neighboring RNCs. Before you start Ensure RNC is in LOADED mode with the following< ZE1I;. Procedure 1 Configure Iur i nterface's control plane. a) Create an association set. t Tip: In the command: C stands for "Client" and S stands for "Server". ZOYC:RNCIUR1:C:M3UA:; b) Add associations to the association set. Type the following command: ZOYA:RNCIUR1:ICSU,0:IETF:; ZOYA:RNCIUR1:ICSU,2:IETF:; c) Configure association IP addresses: Configure resilient IP addresses for M3UA association. First given IP address is the source IP address, second one is destination IP address (BkPRNCs IP address). Type the following command: ZOYP:M3UA:RNCIUR1,0:"10.43.6.50","10.43.6.58",:"10.43.5.1 72",27,"10.43.5.174",27,:; ZOYP:M3UA:RNCIUR1,1:"10.43.6.51","10.43.6.59",:"10.43.5.1 73",27,"10.43.5.175",27,:; d) Modify NETWORK appearance in the association set. Type the following command: ZOYM:RNCIUR1:NETWORK=8:; e) Modify associations state with the following commands: ZOYS:M3UA:RNCIUR1,0:ACT:; ZOYS:M3UA:RNCIUR1,1:ACT:; 480 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 2 RNC solution features Configure Iur in terface's us er plane (IP BR). a) Configure a new network interface with the following command: ZQRN:NPGEP,0:VL1260:10.43.7.2,L:28::::; b) Add a new IP-based routes with the following command: ZQRU:ADD:3,"IUR-1":100000:100000:0:0:::; c) Configure IP-based route network parameters with the following commands: ZQRC:NPGEP,0:VL1260:IPV4=10.43.7.2:ID=3::; 3 Modify the parameter values of the existing SCCP signaling point parameter set. a) Create IP type of signaling link set: ZNSP:NA0,D'8332,CRNC1:2:RNCIUR1:; b) Create signaling route set: ZNRC:NA0,D'8332,CRNC1,0,:,,,7::::; c) Allow the activation of a signaling link: ZNLA:2:; d) Allow the activation of a signaling route: ZNVA:NA0,D'8332::; e) Change the signaling link state: ZNLC:2,ACT; f) Change the signaling route state: ZNVC:NA0,D'8332::ACT:; g) Add a subsystem to signaling points: ZNFB:NA0,D'8331:8F,RNSAP,0,Y:; h) Define SCCP for signaling points with subsystem copy: ZNFD:NA0,D'8332,0:8F,RNSAP,0,Y:::::; i) Modify local broadcast status of SCCP subsystems: ZOBC:NA0,D'8332,01:NA0,8F:Y:; ZOBC:NA0,D'8332,8F:NA0,8F:Y:; j) Modify broadcast status of SCCP signaling points: ZOBM:NA0,D'8331,01:NA0,D'8332:Y:; ZOBM:NA0,D'8331,8F:NA0,D'8332:Y:; k) Change the SCCP state of the signaling point: ZNGC:NA0,D'8332:ACT; l) Change the state of an SCCP subsystem: ZNHC:NA0,D'8332:8F:ACT; 8.3.9.5.2.9 Planning Iupc interface configuration The Iu-PC configurations enhancement is required to ensure this interface is working after the redundancy switch. This requirement impacts on the BkPRNC’s configuration and the CP configuration of each connected NE. RNC is a client on the Iupc interface. In case SAS validates the RNC’s source IP address, the validation rule is that the SCTP connection establishment is allowed from the PrPRNC and the BkPRNC. DN09203161Issue:02 ©2016Nokia 481 RNC solution features WCDMA 16 Feature Descriptions and Instructions The SAS does not need to support the two simultaneous SCTP connections because the PrPRNC and BkPRNC are not online at the same time. 8.3.9.5.2.10 Planning Iu-BC interface configuration for RNC2600 BkPRNC Iu-BC interface configuration The Iu-BC configuration enhancement is required to ensure this interface is working after the redundancy switch. This has an impact on the BkPRNC’s CP configuration as well as to the CP configuration of the cell broadcast centre (CBC). If this interface is not enabled in the system, IP address is 0.0.0.0 to be used as the source address in the BkPRNC. CBC and RNC are able to have both the client and the server roles on Iu-BC ,even though CBC takes mainly the client's role. The client has to know the server's destination IP address whilst the server validates the address. In RNC, the Iu-BC source and destination IP addresses are defined in RNW DB. When RNW DB is copied from PrPRNC to BkPRNC, the Iu-BC source address is not valid in BkPRNC anymore and must be changed by the user. To change the source address useZE1M command when the BkPRNC is running in the LOADED mode. The redundancy switch has no impact on the destination address from the BkPRNC's point of view. CBC has to know both the PrPRNC’s and the BkPRNC’s IP addresses in order to establish the interface, so CBC has to support the primary IP address, which refers to PrPRNC and the secondary IP address, which refers to BkPRNC. The secondary address is used when connection establishment to the primary address does not work, which is the case after a redundancy switch. It is possible that CBC validates the secondary IP addresses meaning that the same secondary IP address must not be used for multiple RNCs. In that case, in BkPRNC each RNCSRV has to have a unique source IP address. If CBC does not support the secondary IP address, the primary IP address has to be changed manually after the redundancy switch. In this case it is also necessary to manually verify if the broadcasts are ongoing or whether they should be restarted. When the primary RNC (in this case any of PrPRNC) is disabled, the secondary RNC (in this case BkPRNC) starts operating and sends a reset request to the CBC. This operation indicates to the CBC that it has to restart the broadcast, because it is impossible to establish a TCP/IP connection to the PrPRNC. The CBC must establish a connection to the BkPRNC and restart the broadcast. However, the actual CBC behavior is vendor specific and may vary from the described example. 8.3.9.5.2.11 Committing changes and backup configuration test Enabling backup configuration test The user must commit any manual change of BkPRNC configuration done with MML commands. For example, when the user changes Iu /Iur signaling or transport configuration, committing it with ZE1X command must be executed as the last action. This command triggers the test, which checks the RNCSRV’s configuration health. Without the test, the faulty configuration may remain undetected. Only activation of RNCSRV, so the initiation of network resiliency, causes late malfunction detection. In case of auto-adaptation, the commitment is executed automatically and followed by the test. 482 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Backup configuration test results When the test detects problems in the configuration: • PRNC-RNCSRV-DATSYN-BackupCompleteness value is set to Less than 100% • 3835 RNC SERVICE CONFIGURATION MISSING OR INCOMPLETEalarm is raised Troubleshooting Details regarding the problems are stored in commit log file. 8.3.9.5.2.12 Reconfiguring BTS for Network Resiliency Purpose The user reconfigures BTS in order to add a BkPRNC configuration, which is an additional RNC configuration. Before you start Primary BTS configuration has been already done. Procedure 1 Commission BTS using additional PrPRNC and BkPRNC IP addresses. Provide the following information in BTS SM, on the Iub interface configuration page within the Backup RNC configuration: Table 193 BTS configuration values P a r a me t e r Far end SCTP subnet address Va l u e BkPRNC IP address for example: 10.43.52.42 Far end SCTP subnet address mask BkPRNC FAREND SCTP for example: 255.255.255.255 (/32) OAMaddress BkPRNCIPaddress for example: 10.43.52.235 g 8.3.9.5.2.13 Note: Re-homing BTS may require changing of BkPRNC information to values related to the new controller. Configuring RNCSRV Purpose RNCSRV configuration must be done in the LOADED mode. The general idea of RNCSRV configuration is shown on theFigure 83: RNCSRV configuration. DN09203161Issue:02 ©2016Nokia 483 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 83 RNCSRV configuration RNCSRV Specific configuration RNW DB BFD IPBR ... IPRO IP address Planned commonly to all RNCSRVs VLAN Ethernet Cabling Every RNCSRV/backup build must contain the whole configurations presented in Figure 83: RNCSRV configuration. The lower part of the figure is planned only once as it is common to all RNCSRVs, but also it has to be configured in each RNCSRV. The upper part of the figure must be unique in all RNCSRVs. Also the SIGTRAN signaling interfaces need to be configured separately to each RNCSRV. However, the lower part of the figure (as well as SIGTRAN configuration) is also configured in the base build. It means that the existing configuration is copied to RNCSERV configuration when RNCSERV is created, but after that any changes to the base build configuration are not populated to the alre ady created RNCSERVs or vice versa. Before you start Table 194: Configuration list BkPRNCshow RNC configuration items, which must be configured when configuring BkPRNC. Table 194 Configuration list BkPRNC R N C c on f i g ur at i o n i t e m RNC NE account (User Ids) R N C S RV p re configuration necessity No Synchronized from PrPRNC RNC system name (by default is IPA2800) No Synchronized from PrPRNC RNC time setting (zone, DST) No Synchronized from PrPRNC RNC HW configuration No (functional unit configuration) 484 Notes RNClicenses No Certifications and keys Yes ©2016Nokia SharesPRNC'sHW configuration SynchronizedfromPrPRNC RNCSRV shares PRNC's certifications and licenses. Operator installs certification and keys on the base build or the backup build. Resiliency framework aligns the configuration between the builds. DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 194 RNC solution features Configuration list BkPRNC (Cont.) R N C c on f i g u rat i on i t e m R N C S RV p re configuration necessity Notes Delivery dependent functional configuration (parameter values) No Synchronized from PrPRNC Transport configuration Yes • • • RNCSRV inherits the PRNC's transport configuration. After first configuration synchronization, the mapping XML needs to be completed for autoadaptation The source IP address for Iubc has to be defined with MML g RNW measurement plan Transport and HW measurement plan No Yes Note: The IPBR MOs and IPRO MOs are synchronized from PrPRNC when autoadaption is successful. In other case, operator must configure IPBR and IPRO. Synchronized from PrPRNC Alarm definitions and filtering No Synchronized from PrPRNC Subscriber trace settings No Synchronized from PrPRNC DSP resource configuration No Synchronized from PrPRNC Procedure 1 Configure BkPRNC. Configure BkPRNC according to the Table 195: Configuration matrix. Table 195 Configuration matrix Already done in base build No DN09203161Issue:02 Necessary for entire BkPRNC a) Cabling configuration ©2016Nokia Necessary for each RNCSRV a) b) c) d) e) f) Ethernet configurations VLAN configuration Configure IP addresses Configure Iu-CS control plane Configure Iu-PS control plane Configure Iu-CS user plane 1 485 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 195 Configuration matrix (Cont.) Already done in base build Necessary for entire BkPRNC Necessary for each RNCSRV g) Configure Iu-PS user plane 1 h) Configure IuB user plane 1 Yes 2 i) Configure BTS O&M a) b) c) d) e) Ethernet configurations VLAN configuration Configure IP addresses Configure Iu-CS control plane 2 Configure Iu-PS control plane 2 1 Optional if auto-adaptation is enabled. 2 Optional if RNCSRVs have common destinations. Commit transport configuration. a) Commit configuration < ZE1X:START; LOADING PROGRAM VERSION 1.17-0 COMMITTING CONFIGURATION CHANGE IS STARTED COMMAND EXECUTED b) Check configuration committing status • < ZE1X:SHOW; LOADING PROGRAM VERSION CONFIGURATION COMMITTING RESULT: START TIME = 2014-01-22 10:43:10.94 TERMINATE TIME = 2014-01-22 10:45:17.25 CONFIGURATION TEST = SUCCESS ADAPTATION = SUCCESS DETAILED REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/commit221.log COMMAND EXECUTED • < ZE1I; LOADING PROGRAM VERSION 1.18-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 221 486 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: ADAPTING CONFIGURATION CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: OFF DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: BACKUP UPDATE TIME: MON,TUE,WED,THU,FRI,SAT,SUN,14:45 11-08-2014;14:49 BACKUP COMPLETENESS: 100% RNC CLUSTER O&M LINK STATE: ENABLED Step result After successful operation, service status is changed to IDLE. Refer to the Reference documentation in case alarm3835 RNC SERVICE CONFIGURATION MISSING OR INCOMPLETEis set. t Tip: If you commit transport configuration because you are performing transport configuration/IP connectivity test, use ZE1C to switch to the base build after the test is completely done. 3 Switch to the base build When transport configuration/IP connectivity test is completely done, switch to the base build with the following command: ZE1C:UNLOAD:; Step result COMMAND EXECUTION WILL CAUSE SYSTEM RESTART CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... 8.3.9.5.2.14 IP addresses mapping Purpose IP addresses mapping is needed for auto-adaptation functionality. IP address mapping is RNCSRV-specific. Procedure 1 Interrogate mapped IP data from RNCSRV of protected PrPRNC. < ZE1P:MAPPED:221; DN09203161Issue:02 ©2016Nokia 487 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result LOADING PROGRAM VERSION 1.18-0 INTERROGATING MAPPED IP DATA OF RNCSRV-221 IDX PrPRNCIP BkPRNCIP STATUS INFO ------------------------------------------------------------------------------1 10.43.5.116 10.43.6.116 VALID BTSTRANSPORT 2 10.43.5.117 10.43.6.117 VALID BTS2TRANSPORT 3 10.43.5.124 10.43.6.124 VALID IUCSTRANSPORT 4 10.43.5.132 10.43.6.132 VALID IUPSTRANSPORT COMMAND EXECUTED 2 Interrogate unmapped data from RNCSRV of protected PrRNC. < ZE1P:UNMAPPED:221; Step result Listed BkPRNC's IP addresses are not paired with PrRNC's IP addresses so they are not used in auto-adaptation. LOADING PROGRAM VERSION 1.18-0 INTERROGATING UNMAPPED IP DATA OF RNCSRV-221 IDX PrPRNCIP BkPRNCIP -------------------------------------1 10.43.6.254 2 10.43.6.68 3 10.43.6.84 4 10.43.6.100 5 10.43.6.253 6 10.43.6.76 7 10.43.6.92 8 10.43.6.108 9 10.43.6.140 COMMAND EXECUTED 8.3.9.5.2.15 Auto-adaptation in RNC2600 Auto-adaptation requires IP addresses mapping between PrPRNCs and BkPRNC. PRNCs collect the found UP IP addresses to the mapping files which are managed with MML command. You have to map PrPRNCs and BkPRNCs IP addresses manually to enable the system to choose correct source IP address at BkPRNC for the logical interfaces. Following actions still require manual work in RAN2512 in RU50EP1 release: 488 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features configuring SIGTRAN's signaling configuring IP addresses configuring TWAMP • • • Routing (partially) Enabling BFD (both in RNC and BTS) after resiliency switch • • Auto-adaptation requires IP addresses mapping between PrPRNCs and BkPRNC. Auto-adaptation example for new BTS added or deleted in PrPRNC 1. Changes are done to PrPRNC. 2. Synchronization to BkPRNC is done. 3. When download is finished, configuration test is done, need for auto-adaptation is noticed. 4. RNCSRV is loaded and auto-adapted. 5. After auto-adaptation is completed, system waits for input for example IP connectivity test execution request. 6. If no input, next RNCSRV needing auto-adaptation is loaded. 7. When all RNCSRVs are auto-adapted, base build is loaded and system waits for the next synchronization round. g Note: If system cannot automatically perform the configuration, an alarm 3835 is set and commit log is written to, for example errors are not silently included. g Note: If auto-adaptation would lead to making ”configured BTS ” to ”non-configured BTS” (for example due to lacking IP address mapping) the adaptation is not done. 8.3.9.5.2.15.1 Performing manual adaptation Purpose If auto-adaptation parameter isON, then after data synchronization, adaptation is triggered automatically. Otherwise, the user performs manual adaptation in LOADED mode . g Note: Auto-adaptation works also with synchronized scheduling. Procedure 1 Add Iu/Iub UP IP address mapping rule for RNCSRV1. Type the following command: ZE1P:ADD:<RNCSRV_ID>:<source IP(UP IP address) in PrPRNC>:<source IP in BkPRC>:INFO="<comment>";; 2 Trigger data synchronization for RN CSRV1 . ZE1S:START:<RNCSRV_ID>:<source IP(UP IP address) in PrPRNC>:<source IP in BkPRC>:INFO="<comment>";; 8.3.9.5.2.16 Testing IP connectivity (optional) Purpose DN09203161Issue:02 ©2016Nokia 489 RNC solution features WCDMA 16 Feature Descriptions and Instructions The IP connectivity test verifies that RNCSRV at BkPRNC has IP layer connectivity. This test can be run after a major configuration change or before redundancy switch to check the network's condition. Procedure 1 Pre-check external IP co nnectivity. External IP connectivity pre-check for the RNC service in the BkPRNC helps to ensure that intermediate transport is correct. This is important when BkPRNC and PrPRNC are innetwork differentconfiguration sites. t Tip: Perform this test only when RNCSRV is LOADED. Enter the following command: < ZE1T:ENABLE; Step result LOADING PROGRAM VERSION 1.17-0 IP CONNECTIVITY TEST IS ENABLED COMMAND EXECUTED 2 Execute the test. Enter the following command: < ZE1T:START; Step result The test is being executed. This will take several minutes. 3 g Show test's results Note: The exact time of the IP connectivity test depends on many factors, such as: test scope, network condition, network size. Because it is difficult to determine the test time precisely, the best way to check whether the test is still ongoing is to check TEST TERMINATE TIME field in the SUMMARY OF THE TEST: message. No value in this field means the test is still ongoing. Enter the following command: < ZE1T:SHOW; 490 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step result LOADING PROGRAM VERSION *CCI* IP CONNECTIVITY TEST MODE: ENABLE INTERROGATING IP CONNECTIVITY TEST RESULT RNCSRV 017 I/F IUB IU PLANE O&M CP UP CP UP TOTAL 050 050 000 005 000 UNSUCCESS 000 050 000 004 000 PARTSUCCESS 000 000 000 000 000 SUCCESS 000 000 000 000 000 WARNING 050 000 000 001 000 SUMMARY OF THE TEST: TEST START TIME = 2014-01-22 10:49:31.98 TEST TERMINATE TIME = 2014-01-22 10:54:01.90 UNSUCCESS TEST = 054 PARTSUCCESS TEST = 000 SUCCESS TEST = 000 CONFIGURATION WARNING = 051 TOTAL TEST = 0105 DETAILED TEST REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/iptest221.log 4 Close Ethernet ports. Enter the following command: ZE1T:DISABLE; 8.3.9.5.3 8.3.9.5.3.1 Operating and Maintaining RAN2512: Network Resiliency for RNC2600 Operating and Maintaining overview Software operation and maintenance are necessary to ensure resiliency in the protected part of the network. It is essential to ensure that SW builds and configurations of PRNCs are up-to-date, and necessary IP connectivity exists. The main user interface utilized to manage the feature are text commands. With them you are able to fully manage the feature. Besides of text commands, the OMS Element Manager (OMS EM) supports most of functionalities related to the feature. In addition to legacy functions, like alarm management and the RNW DB parameter management, the following operations are supported in OMS: • • • • • DN09203161Issue:02 redundancy switch (RNC Service Activation and Forced RNC Service Activation) redundancy switchback (RNC Service activation in PrPRNC) enabling BACKUP Mode or LOADED Mode in BkPRNC deleting RNC Service configuration Data synchronization schedule configuration ©2016Nokia 491 RNC solution features WCDMA 16 Feature Descriptions and Instructions Moreover, you can use OMS EM to monitor the BkPRNC and the feature in general. In practice this means that feature-related objects like BKPRNC, RNCSRV and DATSYN can be managed in OMS EM. OMS EM allows to upload and download corresponding RNCSRV's IP plan when BkPRNC is in LOADED mode. When using OMS EM you cannot perform operations like: commissioning and preconfiguration, manual data synchronization, and IP connectivity test. For more information seeOMS documentation. 8.3.9.5.3.2 NetAct topology view Deployment and removal of the Topology View of PRNC objects in NetAct NetAct allows to present the Topology View of the PRNC objects with the RAN3226: NetAct Topology View to Network Resiliency of RNCfeature. It requires installing NetAct software license. After installation, the RAN3226: NetAct Topology View to Network Resiliency of RNC is always active. The topology view deployment processes automatically. The OMS collects the data required for deployment from a particular Physical RNC (PRNC). NetAct receives the data from the OMS to perform its desired functions in the variety of different user scenarios. The topology of a resilient network (configured PRNCs) is automatically visible on NetAct after upgrading the software of PRNC and OMS. NetAct Monitor tool automatically receives topology information on the defined protected PRNCs (PrPRNC), backup PRNCs (BkPRNC), and RNC objects. It displays them on the user's interface. According to OMS information, the Monitor tooltools (NetAct) its topology. New PRNC object will be seen in Monitor and CM (CMupdates Editor, CM Operations Manager). NetAct automatically removes obsolete topology information related to the standard PRNCs after NetAct, OMS and RNCs have been upgraded to WCDMA17. NetAct operability for the resilient network The operator uses NetAct Monitor to launch Element Management operations for the protected PRNCs and backup PRNCs viewable on NetAct. The RAN3226: NetAct Topology View to Network Resiliency of RNCfeature allows the user to utilize NetAct for: • • • Displaying the alarmsrelated to the PRNC on the NetAct Monitor. Uploading CM plan for PRNCs. Collecting HW inventoryinformation from the protected PRNCs, and backup PRNCs. NetAct CM tools (CM Editor) displays the HW inventory information. Reporting alarms by NetAct NetAct receives hardware and transport alarms from the protected PRNCs and backup PRNCs. When the PRNC detects a fault condition that requires notification to the operator, it displays the alarms on the user's interface. In case of hardware or transport failure, NetAct Monitor displays • • 492 hardware and transport alarms againstthe corresponding protectedor backup PRNC alarms specific for the network resiliency of RNC, for the respective PRNC objects ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features In case of radio network failure, detected in the active RNC service of a protected or backup PRNC, alarms are visible on NetAct Monitor against the RNC object. 8.3.9.5.3.3 Managing Software Backup Physical RNC System management The feature introduces a Backup Physical RNC System (BPS) containing one base build and up to 16 backup builds. All of the builds are in the same SW version (release and CD version) The BkPRNC is able to hold more than one BPS. A BPS which contains a running SW build is called a running BPS. The purpose of BPS fallback is similar to a single-build fallback, which the operator utilizes to create BPS backup for a recovery purpose. User's operations supported on BPS: • • • • • Show particular or all BPS information existing inthe system. Create a particular BPS fallback, and inquire the BPS fallback progress. Delete the BPS. Upgrade a running BPS by running a HIT macro. Activate a particular BPSby using the single-build activation MMLcommand. The user activates the BPS by activating its base build. At one time, the user is allowed to execute only one of the following operations: BPS fallback creation, BPS deletion, and BPS upgrade. Forbidden single-build operations It is forbidden to delete using the respective single-build deletion MML command a build belonging to any BPS. Deletion attempt is rejected with THIS PACKAGE BELONGS TO BPS system notification. Operator must not use a single-build switch command to switch a build in the following cases: • • • • Base build to the same BPS's backup build Base build to another BPS's backup build Backup build to the same BPS's backup build Backup build to another BPS's backup build The only allowed switch case is one BPS's base build to another BPS's base build. Mutual impacts and exclusionfor simultaneous BPS and resilient operations Operations from the BPS-related operation group, and the resilient-related operation group affect each other, thus some of them must not be executed simultaneously. If the user requests to start a BPS operation, and a resilient operation is ongoing, the system will accept or reject the requested operation execution according to mutual exclusion. DN09203161Issue:02 ©2016Nokia 493 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 196 BPS operation mutual exclusion Operations Ongoing resilient operation Requested BPS operation BPS Fallback BPS deletion (delete non-default BPS) ServiceCreation x Y ServiceDeletion x Y DataSynchronization x Y Pre-configuration x x Pre-configuration commitment - - Configurationdeletion x Y Serviceactivation x Servicedeactivation - IPconnectivitytest x - - BPS fallback - x BPS deletion (delete non-default BPS) Y x x x The operation executionis allowed x The operation execution is rejected - Not applicable If the user requests to start a resilient operation, and a BPS operation is ongoing, the system will accept or reject the requested operation execution according to the mutual exclusion. Table 197 Resilient operation mutual exclusion Operations Requested resilient operation Ongoing BPS operation BPS Fallback BPS deletion(delete non-default BPS) ServiceCreation x Y ServiceDeletion x Y DataSynchronization x Y Pre-configuration x Y Pre-configuration commitment Configuration deletion x Serviceactivation Y Servicedeactivation - IPconnectivitytest - Y Y - (WM) BPSHAN - Backup Physical RNC System Handling 494 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Program's function: New command(s) and menu text(s): 8.3.9.5.3.4 RNC solution features Use the commands in this command group to interrogate Backup Physical RNC System(BPS) information, start BPS fallback copying, check the BPS fallback copying status, quit BPS fallback copying, and delete BPS. D DELETE BACKUP PHYSICAL RNC SYSTEM I INTERROGATE BACKUP PHYSICAL RNC SYSTEM INFORMATION S START BACKUP PHYSICAL RNC SYSTEM FALLBACK COPYING P INTERROGATE BACKUP PHYSICAL RNC SYSTEM FALLBACK COPYING Q QUIT BACKUP PHYSICAL RNC SYSTEM FALLBACK COPYING Updating SW builds on BkPRNC This chapter describes procedure the user updates SW builds by upgrading PrPRNC1 build, PrPRNC2 build and BkPRNC's base build from CD1 to the CD2. g Note: Build update time is approximately one hour (1h). PrPRNC requires approximately one hour to be updated. BkPRNC update requires upgrading both base build and backup builds. Approximated time depends on number of builds stored in BkPRNC. SW update phases See Phases of SW update to check what are the phases of SW update. DN09203161Issue:02 ©2016Nokia 495 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 84 Phases of SW update Bu ilds be fo re updat e PrPRNC1 BkPRNC QX 14.26-0 CD1 RNCSRV1: QX 14.26-0 CD1 RNCSRV2: QX 14.26-0 CD1 PrPRNC2 QX 14.26-0 CD1 Base Build QX 14.26-0 CD1 Bu il ds af te r exec ut in g SWupdat e scri pt at Pr PR NC PrPRNC1 BkPRNC QX 14.26-0 CD2 RNCSRV1: QX 14.26-0 CD1 RNCSRV2: QX 14.26-0 CD1 PrPRNC2 QX 14.26-0 CD2 Base Build QX 14.26-0 CD1 Builds after executing SW udat p e script at BkPRNC PrPRNC1 BkPRNC QX 14.26-0 CD2 RNCSRV1: QX 14.26-0 CDr2 RNCSRV2: QX 14.26-0 CD2 PrPRNC2 QX 14.26-0 CD2 Configuration synchronized Configuration desynchronized Synchronizing configuration Base Build QX 14.26-0 CD2 SW build User runs SW upgrade script Prerequisites for BkPRNC software update • 496 BkPRNC is commissioned and SW build is stored in target BkPRNC. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions • • • • • • • Data synchronization hadbeen disabled by update script: ongoing synchronization is stopped and DataSynchState is Blocked. BkPRNC update is performed at backup mode. Updating BkPRNC takes along time. Plan the update schedule as several parts within the maintenance window. Resiliency maintenance operations(adding or deleting resiliency service)is allowed during two separate update parts. If PrPRNC is out of service, it is possible to execute resiliency switch even during BkPRNC update. After completion of the update, switch to base build's new version. In case some backup builds' update fail or operator wants to activate new base build earlier FORCE option is provided. Perform backup build verification after update.There is no need to activate backup build immediately after update. This verification is combined together with preconfigure verification, made with the following steps: – – – • 8.3.9.5.3.5 RNC solution features switch backup build to LOADED state update verification, like units state checking, database integrity checking connectivity verification After updating the software, store the old backup build for restore or rollback purposes. Remove it only at next update. Synchronizing Purpose To match RNCSRV's configuration at BkPRNC with PrPRNCs configuration. Before you start t Tip: Rough time estimated for synchronization process is approximately 15 minutes per PrPRNC. This time period depend on factors like PrPRNC load, available bandwidth and overall network condition. Synchronization contains: • RNCSRV data collection • download basic adaptation configuration test • • • Manual synchronization Trigger this synchronization when the cluster interface is inEnabled state and service status is IDLE. Use the following command: ZE1S:START:RNCSRVID Step example ZE1S:START:221; DN09203161Issue:02 ©2016Nokia 497 RNC solution features WCDMA 16 Feature Descriptions and Instructions t Tip: 221 is the RNC service ID SYNCHRONIZATION OF RNCSRV-204 WAS STARTED COMMAND EXECUTED Step result Synchronization is over whenACTIVITY MODE is BACKUP and SERVICE STATUS changes from SYNCHRONIZING to IDLE. • Scheduled Syn chronization Go the specific BkPRNC and corresponding RNCSRV of the PrPRNC to be synchronized. Right-click and select Show all parameters option. Set the synchronization time by providing values forScheduling periodic data synchronization in hours and Scheduling periodic data synchronization in minutes. • Auto-adaptation Performing auto-adaptation manually 8.3.9.5.3.6 Maintaining IP connectivity Purpose This chapter describes how to perform IP external connectivity test on BkPRNC. Perform this procedure when in LOADED mode. Procedure 1 Enable external IP connectivity test possibility. Enable the test with the following command: ZE1T:ENABLE; Step result LOADING PROGRAM VERSION 1.17-0 IP CONNECTIVITY TEST IS ENABLED COMMAND EXECUTED 2 Start the test. ZE1T:START; 498 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Step result LOADING PROGRAM VERSION 1.17-0 ALL IP CONNECTIVITY WILL BE TESTED COMMAND EXECUTED 3 Display test results and analyze it. ZE1T:SHOW; Step result LOADING PROGRAM VERSION *CCI* IP CONNECTIVITY TEST MODE: ENABLE INTERROGATING IP CONNECTIVITY TEST RESULT RNCSRV 0204 I/F IUB IU PLANE O&M CP UP CP UP TOTAL 001 001 001 003 000 UNSUCCESS 000 000 000 000 000 PARTSUCCESS 000 000 000 000 000 SUCCESS 001 001 001 002 000 WARNING 000 000 000 001 000 SUMMARY OF THE TEST: TEST START TIME = 2013-10-14 16:21:54.79 TEST TERMINATE TIME = 2013-10-14 16:21:56.07 UNSUCCESS TEST = 000 PARTSUCCESS TEST = 000 SUCEESS TEST = 005 CONFIGURATION WARNING = 001 TOTAL TEST = 006 DETAILED TEST REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00204A/ASWDIR/iptest00 204.log COMMAND EXECUTED t 8.3.9.5.3.7 Tip: Detailed test is in log file: /eclipse/BK00204A/ASWDIR/iptest00204.log Interpreting of the system logs Table 198: RNC Resiliency Logscontains information helpful for interpreting logs: • • • DN09203161Issue:02 Test: type of performed test Description: detailed description of performed test with a list of possible statuses obtained Result: detailed description of possible statuses obtained ©2016Nokia 499 RNC solution features WCDMA 16 Feature Descriptions and Instructions • Logs: log file name Table 198 RNC Resiliency Logs Te s t Descr ip ti on RNC Resiliency The Commit configuration test log records Note: RNC service R es u l t s • g This test is done in BkPRNC in Backup mode only. L og s INCOMPLETE: means MISSING or MISMATCH. – adaptation and configuration test results during synchronization or manual configuration commit phase. The test results fall into three classes: INCOMPLETE, UNNECESSAR Y and COMPLETE. – – – MISSING means that records configtest_rnc srv<RNCSRVID>.log exist exist in in PrPRNC BkPRNC.but do not MISMATCH means that records exist both in PrPRNC and BkPRNC,but parameters do not match. CURRENT means that IPBR/IPRO configurations exist on BkPRNC. EXPECTED means that PrPRNC IPBR/IPRO configurations adapt to BkPRNC according to IP mapping table. Auto-adaption requires complete IP mapping configuration. If there is log indicating 'NO IP-MAPPING' or 'INVALID IP-MAPPING', operator needs to check IP mapping configuration. • • Auto-adaption is calculated bases on IPBR, all the IPROs binding to same IPBR are only counted as 1. UNNECESSARY: records which exist in BkPRNC are not found in PrPRNC or records which is unused in BkPRNC. UNNECESSARY IPBR/IPRO means that there is extra IPRO configuration in BkPRNC side comparing with PrPRNC. There is risk that later when a different IPRO is configured in PrPRNC. It may result in an inconsistent state in BkPRNC after synchronization. CURRENT and EXPECTED are same as previous explanations. COMPLETE: configuration items in BkPRNC are correct. g RNC Resiliency IPtestlog IP Test records system configuration issues and IP 500 • ©2016Nokia Note: If EXPECTED SPC is N/A it means that a SPC is found in RNW DB but corresponding configuration does not exist in platform. WARNING: configuration error found. iptest_rncsrv< RNCSRV-ID>.log DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Table 198 RNC solution features RNC Resiliency Logs (Cont.) Te s t Descr ip ti on R e su l t s connectivity Note: status which are This test found during IP is done connectivity only in testing. Test BkPRNC results are in classified as Loaded WARNING, and UNSUCCESS, Active PART modes. SUCCESS, IP Test SUCCESS and cannot NOT TEST. be triggered in Backup mode. • RNC Resiliency Sync log Sync records RNC service Note: adaptation and This test configuration is done test result in in synchronization BkPRNC phase. Test in results are • g • • • g Backup mode only. INCOMPLETE: means MISSING or MISMATCH. – – – • DN09203161Issue:02 rate means packetipdropped(5 packets sent1 during test). SUCCESS: pinging from source to destination succeeds, no packet lost. NOT TEST: pinging has not been executed. – classified as INCOMPLETE, UNNECESSAR Y and COMPLETE. ©2016Nokia L og s UNSUCCESS: pinging from source to destination fails, all packets lost. PART SUCCESS:some packets lost, but connectivity is ok. Packet lost rate provided, 20 percent lost MISSING means that records exist in PrPRNC but do not exist in BkPRNC. MISMATCH means that records exist both in PrPRNC and BkPRNC,but parameters configtest_rnc srv<RNCSRVID>.log do not match. CURRENT means that IPBR/IPRO configurations exist on BkPRNC. EXPECTED means that PrPRNC IPBR/IPRO configurations adapt to BkPRNC according to IP mapping table. Auto-adaption requires complete IP mapping configuration. If there is log indicating 'NO IP-MAPPING' or 'INVALID IP-MAPPING', operator needs to check IP mapping configuration. Auto-adaption is calculated bases on IPBR, all the IPROs binding to same IPBR are only counted as 1. UNNECESSARY: records which exist in BkPRNC are not found in PrPRNC or records which is unused in BkPRNC. UNNECESSARY IPBR/IPRO means that there is extra IPRO configuration in BkPRNC side comparing with PrPRNC. There is risk that later when a different IPRO is configured in PrPRNC. It may result in an inconsistent state 501 RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 198 Te s t RNC Resiliency Logs (Cont.) Descr ip ti on R es u l t s L og s in BkPRNC after synchronization. CURRENT and EXPECTED are same as previous explanations. COMPLETE: configuration items in BkPRNC are okay. • g Note: If EXPECTED SPC is N/A it means that a SPC is found in RNW DB but corresponding configuration does not exist in platform. The directories which store the logs are available with the following commands: show file content local /log/configtest_rncsrv223.log and show file content local /log/iptest_rncsrv223.log For more information, refer to SCLI Commands. 8.3.9.5.3.8 8.3.9.5.3.8.1 8.3.9.5.3.8.1.1 Network Resiliency operations Redundancy switch Activity model Figure 85: Activity modelshows available Activity Modes of BkPRNC and PrPRNC and transitions between them. Figure 85 Activity model Transitions in Backup PRNC Waiting for synchronization System restart 5 6 Transitions in protected PRNC Active 1 Active 21 21 7 Backup 3 4 Loaded Loaded 1. RNCSRV Activation. 2. RNCSRV Inactivation; 3GPP interfaces are blocked. 3. RNCSRV is set from BACKUP mode to LOADED mode; a backup build is loaded to memory for configuration and testing. 4. In BkPRNC, the base configuration package is loaded to memory. 5. RNCSRV configuration has been deleted, or the conversion in SW upgrade has failed. 6. Initial synchronization has been completed. 7. Another RNCSRV is loaded to memory. g 502 Note: Synchronization is done at Backup mode, configuration is done at LOADED mode ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 8.3.9.5.3.8.1.2 RNC solution features Use cases Overview of possible use cases Table 199 Use cases U s ec a s e D e s cr i p t i o n Normal redundancy switch Normal redundancy switch Performing normal redundancy switch from PrPRNC to BkPRNC Forced redundancy switch Forced redundancy switch Performing forced redundancy Changing RNCSRV-X to RNCSRV-Z at BkPRNC Redundancy Switchback System recovery from redundancy conflict w In stru cti on Changing any RNCSRV to RNCSRV-Z at BkPRNC switch from PrPRNC to BkPRNC - Redundancy Switchback Redundancy switchback System recovery from redundancy conflict Redundancy conflict NOTICE: In the following simplified examples RNCSRV, PrPRNC and BkPRNC with fixed ID numbers show the NE behavior in different use cases. Normal redundancy switch Preconditions • • • Resiliency association betweenPrPRNC and BkPRNC was created. RNC-cl interface is established. BkPRNC is in BACKUP mode. 1. Redundancy switch is executed at BkPRNC (using text commands when directly connected to RNC or with OMS GUI). 2. After self-validation BkPRNC restarts. 3. RNCSRV-X switches to LOADED mode. 4. PrPRNC wants to establish a connection and BkPRNC acknowledges it. 5. Once BkPRNC started and RNC-cl is up, BkPRNC orders PrPRNC to deactivate its RNCSRV. 6. After getting acknowledgment from PrPRNC, BkPRNC activates the RNCSRV-X. g DN09203161Issue:02 Note: Redundancy switch might be executed also if BkPRNC-Y has RNCSRV-X already in LOADED mode. ©2016Nokia 503 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 86 Normal redundancy switch PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X Redundancy switch RNCSRV-X 1 Validation 2 RESET 3 RNCSRV-X to LOADED mode RNC-cl establishment/ acknowledgement 4 Deactivate 5 Deactivating RNCSRV-X to LOADED mode OK 6 RNCSRV-X to ACTIVE mode ALARM; RNCSRV ACTIVATION Forced redundancy switch g Note: In forced redundancy switch BkPRNC does not try to shutdown the PrPRNC even though RNC-cl interface is up and running. Preconditions • • • RNC-cl interface is established or not working. Resiliency association betweenPrPRNC and BkPRNC was created. BkPRNC is in BACKUP mode. 1. Normal redundancy switch fails, which is indicated by no reply from PrPRNC or PrPRNC replies with error. 2. a) BkPRNC does not recognize the status of PrPRNC, whilst RNCSRV-X is disabled or enabled. User must verify the status and isolate PrPRNC. b) Timer expires and alarm is raised. 3. Forced redundancy switch is executed. 504 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Figure 87 RNC solution features Forced redundancy switch PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X Redundancy switch RNCSRV-X Validation RESET 1 RNCSRV-X to LOADED mode Deactivate 2a No-reply timer expires 2b BkPRNC does not recongnise the status of PrPRNC, whilst RNCSRV-X is disabled or enabled. User must verify the status and isolate PrPRNC. ALARM: Deactivation failed 3 Forced redundancy switch RNCSRV-X Validation RNCSRV-X to ACTIVE mode ALARM; RNCSRV ACTIVATION Changing any RNCSRV to RNCSRV-Z at BkPRNC Preconditions • RNC-cl interface is established. Redundancy switch wasexecuted some time ago. BkPRNC-Y is running RNCSRVX. PrPRNC-X has no active RNCSRV. Request reported for BkPRNC-Y running RNCSRV-Z instead of RNCSRV-X. 1. 2. 3. 4. 5. Command BkPRNC-Y from the ACTIVE to the LOADED mode. Load RNCSRV-Z. Execute redundancy switch. After validation, BkPRNC-Y orders PrPRNC-Z to deactivate its service. After getting acknowledgment, BkPRNC-Y activates the RNCSRV-Z. • • DN09203161Issue:02 ©2016Nokia 505 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 88 Changing any RNCSRV to RNCSRV-Z at BkPRNC BkPRNC-Y RNCSRV-X RNCSRV-Z PrPRNC-X RNCSRV-X BkPRNC-Z RNCSRV-Z RNCSRV-X in Active mode Deactivate RNCSRV 1 RNCSRV-X in LOADED mode Load RNCSRV-Z 2 RESET RNCSRV-Z in LOADED mode Redundancy switch RNCSRV-Z 3 Deactivate 4 Deactivating RNCSRV-Z to LOADED mode OK 5 RNCSRV-Z to ACTIVE mode ALARM; RNCSRV ACTIVATION Redundancy Switchback Preconditions • Redundancy switch was executed. PrPRNC was restored (HW, SW and configuration). PrPRNC is inLOADED mode • RNC-cl interface is established. • 1. Redundancy switchback is triggered at PrPRNC. 2. After command validation, PrPRNC orders BkPRNC to deactivate RNCSRV-X. 3. After getting acknowledgment PrPRNC activates RNCSRV-X and sets an alarm. BkPRNC stays in LOADED mode. 4. Verification of PrPRNC proper behavior after switchback. 506 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions Figure 89 RNC solution features Redundancy Switchback PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X RNCSRV-X in LOADED mode 1 Redundancy switchback Validation 2 Deactivate Deactivating RNCSRV-X to LOADED mode 3 OK RNCSRV-X to ACTIVE mode 4a ALARM; RNCSRV ACTIVATION System recovery from redundancy conflict Preconditions • • • 1. 2. 3. 4. DN09203161Issue:02 Forced redundancy switch has been executed. BkPRNC-Y isrunning RNCSRV-X. PrPRNC-X has been just powered off. PrPRNC-X has not been isolated. RNC-cl is established. PrPRNC is started and it runs RNCSRV-X. PrPRNC establishes the RNC-cl and performs ”activity mode query”. When replied, PrPRNC detects the redundancy conflict PrPRNC shuts down the interfaces and remains in the LOADED mode. The redundancy conflict is cleared. ©2016Nokia 507 RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 90 1 System recovery from redundancy conflict PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X RNCSRV-X to ACTIVE mode RNCSRV-X in ACTIVE mode RNC-cl establishment 2 Activity mode query 3 4 Redundancy conflict detected Deactivating RNCSRV-X to LOADED mode 8.3.9.5.3.8.1.3 Detecting redundancy switch necessity The user considers redundancy switch in the case of: • • • planning and performing any maintenance actions whichmay cause a break in delivering controller's services catastrophe in the area where the controller's site isplaced occurrence of a breakdown precluding animmediate restoration ofthe controller Although there is no automatic detection or triggering mechanism for redundancy switch, some existing symptoms like alarms in peer NEs, drop of KPIs or even loss of O&M connection inform the user about the necessity of the redundancy switch execution. g 8.3.9.5.3.8.1.4 Note: Note that if the O&M connection to PrPRNC is interrupted and forced redundancy switch was performed, there is a danger of redundancy conflict unless PrPRNC had been isolated physically. Comparison of prepared and unprepared redundancy switch The redundancy switch can be considered either as a prepared redundancy switch or as an unprepared redundancy switch. The difference between these two lies in the activity mode the BkPRNC is in when redundancy switch is being executed. The unprepared redundancy switch takes place when redundancy switch is executed while BkPRNC is in backup mode (for example base build SW is in memory). After redundancy switch command, a system reset takes place and the wanted RNCSRV is activated. In prepared redundancy switch, the RNCSRV you want to activate is already in LOADED mode (for example the respective backup build SW is already in memory) when the redundancy switch is executed. 508 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features The benefit of prepared redundancy switch is that no system reset, which takes several minutes, is needed when command is being executed because the correct sW is already in RNC’s memory and the RNCSRV is faster back online. Both the prepared and unprepared redundancy switch can be done in normal or forced mode. 8.3.9.5.3.8.1.5 Redundancy conflict Origin of redundancy conflict Redundancy conflict is an undesired situation where both PrPRNC and BkPRNC are online with same RNCSRV active. This leads to a situation where both the PrPRNC and BkPRNC attempt to establish an Iub control plane connection with BTS. Because only one PRNC has BTSs under control, the PRNC which does not control the BTSs will fail with the call setup attempts received from CN. This means, that roughly half of the connection setup attempts srcinated in CN will fail. In the result, bad end user experience arise, as well as KPIs which measure Core Network decrease. Thus it is crucial to solve the redundancy conflict quickly. Redundancy conflict emerges if PrPRNC is restarted accidentally after forced redundancy switch operation. The reason is that the PrPRNC which becomes active after restart and has not been isolated properly, is not aware of the previous redundancy switch and goes online in the network. Thus the best way to prevent a redundancy conflict is to isolate the PrPRNC after redundancy switch. Avoiding and solving redundancy conflict When PrPRNC restarts and becomes active, it establishes the RNC-cl O&M interface and performs activity mode query towards BkPRNC. If BkPRNC is active, the PrPRNC switches to LOADED mode, which means it shuts down the interfaces and goes offline. If there is RNC-cl O&M interface, the system is able to recover the redundancy conflict in few minutes after the RNC-cl O&M interface establishment. Without the interface BkPRNC does not reply to the activity mode query and it is impossible to resolve the redundancy conflict automatically. Another redundancy conflict situation is when both PRNCs try to establish the Iub control plane (CP) connections to BTS. If BTS has working control plane connection, it rejects the CP establishment attempt from colliding PRNC. Redundancy conflict in NetAct Redundancy conflict is problematic for NetAct, because NetAct cannot determine which of the connected RNCs is the correct one. In redundancy conflict situation, all RNC management operations and events in NetAct are related to the connected RNC, and not necessarily to the RNC to which the WBTSs are connected to. If redundancy conflict takes place there will be two PRNCs online with same RNCSRV active. In redundancy conflict the second PRNC reports the RNC to the NetAct topology without knowing the same RNCSRV is already active in another PRNC. As NetAct topology has only one instance of the RNC, the latter RNC will replace the srcinal RNC in NetAct topology. In case the latter RNC is activated accidentally, only this one will be visible in the NetAct but not the RNC which has the control of the related WBTSs. The ActivePRNC parameter of the RNC object in NetAct can be used to identify which PRNC is actually connected to NetAct. BTS behavior in a redundancy conflict DN09203161Issue:02 ©2016Nokia 509 RNC solution features WCDMA 16 Feature Descriptions and Instructions A BTS is able to tolerate a redundancy conflict. It operates in a way that both the Iub control plane and O&M connections are towards the same PRNC. If a BTS has an existing Iub control plane connection to PRNC (for example to PrPRNC) and another PRNC (for example a BkPRNC) has been started accidentally, the BTS rejects the control plane connection establishment from the BkPRNC. The O&M connection follows the control plane connection in order to have them terminated in the same PRNC. If no PRNC is online, the BTS has neither an O&M nor a CP connection. As soon as the PRNC establishes the CP connection, the BTS establishes the O&M connection to the same PRNC. When the PrPRNC is not isolated properly after the redundancy switch and is able to establish a control plane connection to some of the BTSs, those BTSs are beyond the BkPRNC’s control. Therefore, it is crucial to isolate the PrPRNC after the redundancy switch. 8.3.9.5.3.8.2 8.3.9.5.3.8.2.1 Performing redundancy switch operations with MML commands Performing normal redundancy switch Procedure 1 g Execute the redundancy switch. Note: This action requires a confirmation. After the confirmation system is restarted automatically. At BkPRNC, enter the following command: ZE1C:ACTIVATE:221; Step result LOADING PROGRAM VERSION 1.17-0 PLEASE NOTE THAT THIS RNC SERVICE'S BACKUP COMPLETENESS IS NOT 100% COMMAND EXECUTION WILL CAUSE SYSTEM RESTART CONFIRM COMMAND EXECUTION: Y/N ? CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNCSRV-221 WILL BE ACTIVATED COMMAND EXECUTED 2 Check the Interface status (optional). Interrogate the state of an SCCP subsystem and its replication. Correct state indicator is STATE: AV . Execute below command after system restart: < ZNHI; Step result LOADING PROGRAM VERSION 7.6-0 RNC 510 IPA2800 2013-10-17 ©2016Nokia 09:48:12 DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features SUBSYSTEM STATES NETWORK: NA0 POINT H/D: 0391/00913 SP NAME: LIISA ============ ============================= ========================= DESTINATION: ROUTING: SP NO H/D SS NAME STATE RM NET SP CODE H/D NAME STATE ------ ------- ----- -- --- ------------------ ---------------- ------01/001 SCMG AV NA0 0391/00913 LIISA AV-EX 8E/142 RANAP AV - NA0 0391/00913 LIISA AV-EX NETWORK: NA0 POINT H/D: 0607/01543 SP NAME: SGSN ============ ============================= ========================= DESTINATION: ROUTING: SP NO H/D SS NAME STATE RM NET SP CODE H/D NAME STATE ------ ------- ----- -- --- ------------------ ---------------- ------AV 01/001 SCMG NA0 0607/01543 SGSN AV-EX 8E/142 RANAP AV - NA0 0607/01543 SGSN AV-EX NETWORK: NA0 POINT H/D: 2704/09988 SP NAME: PATE4 ============ ============================= ========================= DESTINATION: ROUTING: SP NO H/D SS NAME STATE RM NET SP CODE H/D NAME STATE ------ ------- ----- -- --- ------------------ ---------------- ------01/001 SCMG AV NA0 2704/09988 PATE4 AV-EX 8E/142 RANAP AV - NA0 2704/09988 PATE4 AV-EX WPS:P; DMPG PQ PROCESSING CAPACITY AVAILABILITY: ID PPC SETUP CURRENT % AVERAGE % LOWEST % UNITS ----------------------------------------------------------------------DSP_POOL 99 99 99 4 0 DSP_POOL : PPC SETUP FOR DMPGS USING DSP POOLING DSP CAPACITY AVAILABILITY: 3 ID SERVICE POOL CURRENT % AVERAGE % LOWEST % UNITS -------------------------------------------------------------------97 99 97 1 8 HS_DCH 100 100 100 6 11 HS_CCH 100 100 100 1 CCH SERVICE POOL DESCRIPTIONS: CCH HS_DCH HS_CCH : CCH DSP : HS_DCH DSP : HS-FACH SERVICE ALLOCATION COUNTERS: ID 3 CCH 3 SERVICE POOL CURRENT_NUMBER PEAK_NUMBER TOTAL_NUMBER ---------------------------------------------------------------------------2 2 2 8 HS_DCH 0 0 0 11 HS_CCH 0 0 0 Check the status of BkPRNC and PrPRNC. Enter the following command: DN09203161Issue:02 ©2016Nokia 511 RNC solution features WCDMA 16 Feature Descriptions and Instructions < ZE1I; Step result Activity mode in PrPRNC must be LOADED . LOADING PROGRAM VERSION 1.17-0 RNC TYPE: PROTECTED RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: IDLE BACKUP PRNC ID: 301 BACKUP PRNC NAME: BRINE BACKUP PRNC IP: 10.62.85.16 BKPRNC ACTIVITY MODE: ACTIVE BKPRNC TLS CLIENT MODE: OFF BKPRNC ALARM STATUS: CRITICAL BACKUP COMPLETENESS: 100% BKPRNC BACKUP UPDATE TIME: 19-11-2014;14:22 BKPRNC UNKNOWN STATUS: FALSE RNC CLUSTER O&M LINK STATE: ENABLED COMMAND EXECUTED Result Check the output of < ZE1I;. Activity in mode BkPRNC must be ACTIVE. LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 102 RNC SERVICE ID: 102 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: OFF DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: 19-11-2014;14:22 BACKUP COMPLETENESS: 100% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 512 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features COMMAND EXECUTED 8.3.9.5.3.8.2.2 Performing forced redundancy switch Procedure 1 Execute forced redundancy switch. f When forced redundancy switch is executed, there is no communication between PrPRNC and BkPRNC even though RNC-cl O&M interface exists. When you execute the forced redundancy switch, you have to isolate the PrPRNC manually to prevent the redundancy conflict where both PrPRNC and BkPRNC would be online at the same time. g Note: This action requires a confirmation. After the confirmation system is restarted automatically. At BkPRNC, enter the following command: < ZE1C:ACTIVATE::221:FCD; Step result LOADING PROGRAM VERSION 1.17-0 PLEASE MAKE SURE THE RNC SERVICE IN PEER RNC HAS BEEN DEACTIVATED OR ISOLATED CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNC SRV-221 IS ACTIVATED FORCEDLY COMMAND EXECUTED 8.3.9.5.3.8.2.3 Performing redundancy switch back Procedure 1 Execute the redundancy switchback At PrPRNC, execute below command to start the switch back < ZE1C:ACTIVATE; Step result LOADING PROGRAM VERSION 1.17-0 CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNC SERVICE IS ACTIVATED COMMAND EXECUTED 8.3.9.5.3.8.3 Performing redundancy switch using OMS EM Purpose DN09203161Issue:02 ©2016Nokia 513 RNC solution features WCDMA 16 Feature Descriptions and Instructions This chapter introduces example procedure of redundancy switch from PrPRNC-221 to BkPRNC-301 with RNCSRV-221. Procedure 1 Search for respective RNCSRVby DN in the Navigation bar. Type in RNCSRV-221 in the search line under the Topology tab. Step result The list of NEs containing searched content is displayed: PRNC-221/RNCSRV-221 - directs to PrPRNC which contain representing RNCSRV. PRNC-301/RNCSRV-221 - directs to BkPRNC which contain RNCSRV representing PrPRNC-221. • • Click on either first or second result. You can recognize where have you been brought either by checking which PRNC is indicated by respective icon, according to Impact on network and network element management tools , or by right-click on the RNCSRV-221 and checking which RNC Resiliency menu appears. 2 Activate RNCSRV-221 i n Bk PRNC In BkPRNC, right-click on the RNCSRV-221 and select Resiliency menu. g 8.3.9.6 from RNC Note: The values of the ActivityMode parameter may differ between the Main Parameters application and the Parameter Viewer/Editor applications, as long as the topology data is parsed by OMS. The Main Parameters application displays all the main parameters of the selected object which are stored in the OMS topology database, while the Parameter Editor/Viewer applications display data directly from the related NE (in this case PRNC). Verifying RAN2512: Network Resiliency for RNC2600 Before you start Correct configuration of PrPRNC and BkPRNC provides synchronization possibility between PrPRNC and BkPRNC, which is verified by performing redundancy switch. Procedure 1 Trigger the s witchover with MML o r via O MS. Follow the instructions described in Performing normal redundancy switch from PrPRNC to BkPRNC. Result 514 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features When configuration is done properly, the PrPRNC automatically shuts down 3GPP services and BkPRNC starts the services. After restart, the BkPRNC starts and the 3GPP services are back online. Troubleshooting in case of redundancy switch failure If the RNC-cl O&M interface is down, the PrPRNC cannot be shut down from BkPRNC but it has to be shutdown manually. An alarm indicates the loss of RNC-cl O&M interface. IP connectivity test helps to find any problems in IP layer, what might be a reason of verification failure. 8.3.9.7 Deactivating RAN2512: Network Resiliency for RNC2600 Procedure 1 Remove RNC association at PrPRNC. Delete BkPRNC object via MML command: ZE1R; Step result LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION WITH PRNC-221 WILL BE REMOVED CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y RNC RESILIENCY ASSOCIATION WITH PRNC-221 IS REMOVED SUCCESSFULLY COMMAND EXECUTED 2 Verify that the RNC association has been successfully removed. ZE1I; Step result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: STANDARD RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE COMMAND EXECUTED RNC RESILIENCY ADMINISTRATION COMMAND <E1_> DN09203161Issue:02 ©2016Nokia 515 RNC solution features WCDMA 16 Feature Descriptions and Instructions 3 Verify that the successful deletion information has been sent. The O&M application SW sends BTS O&M interface ConfigurationChangeNotification message to OMS when BkPRNC object is deleted successfully. 4 Delete the BKPRNC object at the PrPRNC object using OMS GUI. 5 Verify that the BKPRNC object in OMS has been successfully deleted. 6 Delete RNCSRV object in BkRNC. Delete RNCSRV object via MML command: ZE1R:<PrPRNC_ID> LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION FOR CONFIRM COMMAND EXECUTION: Y/N CONFIRM COMMAND EXECUTION: Y/N RNC RESILIENCY ASSOCIATION FOR COMMAND EXECUTED RNCSRV-221 WILL BE REMOVED ? Y ? Y RNCSRV-221 IS REMOVED SUCCESSFULLY Step result Check the result with the following command: < ZE1I; LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: NUMBER OF RNC SERVICES DISPLAYED = 0 COMMAND EXECUTED 7 Verify that the RNCSRV object has been successfully deleted. 8 Verify that the corresponding backup build presence has been deleted. Verify that the backup build is deleted from disk, including relevant temporary files. RNC00xxxSYC is a unzip temporary folder and it only exists after data synchronization. 8.3.9.8 Testing RAN2512: Network Resiliency for RNC2600 This is an example of the verification; do not use it for the feature as such in live network. The configuration and parameter settings described are only examples and they can vary in different networks. 516 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Purpose The purpose of the test case is to verify if the RNC resiliency function is working after activating this feature. Before you start For the test case, the following network elements and equipment is used: • Three RNCs (All have RU50EP1 installed) – Assume PrPRNC-221, StPRNC-1, BkPRNC-301 – – PrPRNC-221 and StPRNC-1 has Iur connection. BkPRNC-301 is commissioned and is not integrated. BkPRNC-301 has physical connection forIu, Iur and Iub. BkPRNC-301 has licensecapacity equal or larger than the PrPRNC-221 – – • • • • Two Flexi BTSes, one is ATM based, the other is IP based. One CS CN (the IuBC and IuPC is optional.) One PS CN One UE The following feature related licenses need to be activated for this test case: • • • The basic licenses arerequired for the basic AMR all and PS call SFTP and SSH license RAN2512_Network_Resiliency_for_RNC2600 No parameter needs modification to perform this test case. 8.3.9.8.1 Setup the Network Resiliency for RNC Before you start The PrPRNC is upgraded to RU50EP1. The user installs BkPRNC from scratch. The SW build is the same as PrPRNC's. Procedure 1 g Commission BkPRNC for resiliency. Note: Commands are executed in BkPRNC which ID is 301 (BkPRNC-301). a) Install the RU50EP1 software package b) Install the license and make sure the license capacity is equal or larger than the PrPRNC's. c) Execute the following procedure to commission as BkPRNC: 1. < ZDDS:OMU; 2. 0000-MAN>ZLE:1,RUOSTEQX 3. 0000-RUO>Z1CM:301,2 DN09203161Issue:02 ©2016Nokia 517 RNC solution features WCDMA 16 Feature Descriptions and Instructions g Note: 301 is RNC ID, 2 is backup mode Connecting to RNW database... PRNC-301 creation (mode: backup) completed successfully at 2101-2014 14:47:05.63 Closing RNW database connection... 4. < ZE1I; LOADING PROGRAM VERSION RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: NUMBER OF RNC SERVICES DISPLAYED = 0 COMMAND EXECUTED 2 Create RNC service ( RNCSRV). Type the following command: [ZE1A:<PrPRNC_ID>] Step example ZE1A:221:; Step result t Tip: This action takes approximately 6 minutes in background, after the following system output has been displayed. LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION FOR RNCSRV-221 IS ADDED SUCCESSFULLY COMMAND EXECUTED 3 Interrogate RN C as sociation. Check RNC is configured as standard BkPRNC with the following command: < ZE1I; Step result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 RNC SERVICE ID: 301 518 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: CREATING SERVICE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: DISABLED COMMAND EXECUTED 4 Install RAN2512 feature license and activate it. Enter the following command: ZW7L:; Step result Feature code 4784 is ON. 5 Add RNC resiliency association with BkPRNC. Add RNC resiliency association with BkPRNC by creating BKPRNC object in RNW DB. This enables the RNC-cl O&M at PrPRNC. Type the following command: ZE1A:<BkPRNC ID>:<BkPRNC IP>; Step example < ZE1A:301:10.62.85.16:; Step result RNC RESILIENCY ASSOCIATION WITH PRNC-301 WAS ADDED SUCCESSFULLY COMMAND EXECUTED 6 Start ma nual sy nchronization Start manual synchronization with the following command: ZE1S:START:<PrPRNC_ID>; t DN09203161Issue:02 Tip: Rough time estimated for synchronization process is approximately 15 minutes per PrPRNC. This time period depend on factors like PrPRNC load, available bandwidth and overall network condition. ©2016Nokia 519 RNC solution features WCDMA 16 Feature Descriptions and Instructions Step example ZE1S:START:221:; SYNCHRONIZATION OF RNCSRV-221 IS STARTED COMMAND EXECUTED 7 Check the RNC service status. Check the RNC service status with the following command: < ZE1I; t Tip: It is recommended to check the status at time when the synchronization is ongoing. Step result ACTIVITY MODE changes from WAITING FOR SYNCHRONIZATION to BACKUP after synchronization is finished. SERVICE STATUS changes from SYNCHRONIZING to IDLE after synchronization is finished. LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: SYNCHRONIZING DATA CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED 520 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED 8 Pre-configure RNCSRV. The commands are executed in BkPRNC-301. a) Switch to backup build: < ZE1C:LOAD:221; COMMAND EXECUTION WILL CAUSE SYSTEM RESTART CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNCSRV-221 WILL BE LOADED COMMAND EXECUTED b) Show software package information: < ZWQO:CR; LOADING PROGRAM VERSION 15.10-0 PACKAGES CREATED IN OMU: SW-PACKAGE DEF ACT STATUS DIRECTORY ENVIRONMENT PACKAGE-ID (REP-ID) DELIVERY CD-ID QX144600 Y Y BU BK00301 Y QX144600 NW QX 14.46-0 QX 14.46-0 CID000QX 15.1-0 BK00301_11 QX 14.26-2 QX 14.26-2 CID000QX 15.2-0 c) Check whether BACKUP COMPLETENESS is INCOMPLETED before transport configuration is done. Interrogate RNC association: DN09203161Issue:02 ©2016Nokia 521 RNC solution features WCDMA 16 Feature Descriptions and Instructions < ZE1I; LOADING PROGRAM VERSION *CCI* RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 221 RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: 19-11-2014;14:22 BACKUP COMPLETENESS: LESS THAN 100% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 9 Configure BkPRNC. Configure BkPRNC according to theTable 195: Configuration matrix. Table 200 Configuration matrix Already done in base build No Necessary for entire BkPRNC a) Cabling configuration Necessary for each RNCSRV a) b) c) d) e) f) g) h) i) a) b) c) d) Yes Ethernet configurations VLAN configuration Configure IP addresses Configure Iu-CS control plane Configure Iu-PS control plane Configure Iu-CS user plane 1 Configure Iu-PS user plane 1 Configure IuB user plane 1 Configure BTS O&M Ethernet configurations VLAN configuration Configure IP addresses Configure Iu-CS control plane 2 e) Configure Iu-PS control plane 2 522 1 Optional if auto-adaptation is enabled. 2 Optional if RNCSRVs have common destinations. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features 10 Commit transport configuration. a) Commit configuration < ZE1X:START; LOADING PROGRAM VERSION 1.17-0 COMMITTING CONFIGURATION CHANGE IS STARTED COMMAND EXECUTED b) Check configuration committing status • < ZE1X:SHOW; LOADING PROGRAM VERSION CONFIGURATION COMMITTING RESULT: START TIME = 2014-01-22 10:43:10.94 TERMINATE TIME = 2014-01-22 10:45:17.25 CONFIGURATION TEST = SUCCESS ADAPTATION = SUCCESS DETAILED REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/commit221.log COMMAND EXECUTED • < ZE1I; LOADING PROGRAM VERSION 1.18-0 RNC BACKUP RNC PRNCTYPE: ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 221 RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: 19-11-2014;14:22 BACKUP COMPLETENESS: 100% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED Step result After successful operation, service status is changed to IDLE. DN09203161Issue:02 ©2016Nokia 523 RNC solution features WCDMA 16 Feature Descriptions and Instructions Refer to the Reference documentation in case alarm3835 RNC SERVICE CONFIGURATION MISSING OR INCOMPLETE is set. t Tip: If you commit transport configuration because you are performing transport configuration/IP connectivity test, use ZE1C to switch to the base build after the test is completely done. 11 Pre-check external IP connectivity. External IP connectivity pre-check for the RNC service in the BkPRNC helps to ensure that intermediate transport network configuration is correct. This is important when BkPRNC and PrPRNC are in different sites. t Tip: Perform this test only when RNCSRV is LOADED. Enter the following command: < ZE1T:ENABLE; Step result LOADING PROGRAM VERSION 1.17-0 IP CONNECTIVITY TEST IS ENABLED COMMAND EXECUTED 12 Execute the test. Enter the following command: < ZE1T:START; Step result The test is being executed. This will take several minutes. 13 Show test's results g Note: The exact time of the IP connectivity test depends on many factors, such as: test scope, network condition, network size. Because it is difficult to determine the test time precisely, the best way to check whether the test is still ongoing is to check TEST TERMINATE TIME field in the SUMMARY OF THE TEST: message. No value in this field means the test is still ongoing. 524 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions RNC solution features Enter the following command: < ZE1T:SHOW; Step result LOADING PROGRAM VERSION *CCI* IP CONNECTIVITY TEST MODE: ENABLE INTERROGATING IP CONNECTIVITY TEST RESULT RNCSRV 017 I/F IUB IU PLANE O&M CP UP CP UP TOTAL 050 050 000 005 000 UNSUCCESS 000 050 000 004 000 PARTSUCCESS 000 000 000 000 000 SUCCESS 000 000 000 000 000 WARNING 050 000 000 001 000 SUMMARY OF THE TEST: TEST START TIME = 2014-01-22 10:49:31.98 TEST TERMINATE TIME = 2014-01-22 10:54:01.90 UNSUCCESS TEST = 054 PARTSUCCESS TEST = 000 SUCCESS TEST = 000 CONFIGURATION WARNING = 051 TOTAL TEST = 0105 DETAILED TEST REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/iptest221.log 14 Execute the test. Enter the following command: < ZE1T:START; Step result The test is being executed. This will take several minutes. 15 Show test's results g Note: The exact time of the IP connectivity test depends on many factors, such as: test scope, network condition, network size. Because it is difficult to determine the test time precisely, the best way to check whether the test is still ongoing is to check TEST TERMINATE TIME field in the SUMMARY OF THE TEST: message. No value in this field means the test is still ongoing. DN09203161Issue:02 ©2016Nokia 525 RNC solution features WCDMA 16 Feature Descriptions and Instructions Enter the following command: < ZE1T:SHOW; Step result LOADING PROGRAM VERSION *CCI* IP CONNECTIVITY TEST MODE: ENABLE INTERROGATING IP CONNECTIVITY TEST RESULT RNCSRV 017 I/F IUB IU PLANE O&M CP UP CP UP TOTAL 050 050 000 005 000 UNSUCCESS 000 050 000 004 000 PARTSUCCESS 000 000 000 000 000 SUCCESS 000 000 000 000 000 WARNING 050 000 000 001 000 SUMMARY OF THE TEST: TEST START TIME = 2014-01-22 10:49:31.98 TEST TERMINATE TIME = 2014-01-22 10:54:01.90 UNSUCCESS TEST = 054 PARTSUCCESS TEST = 000 SUCCESS TEST = 000 CONFIGURATION WARNING = 051 TOTAL TEST = 0105 DETAILED TEST REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/iptest221.log 8.3.9.8.2 Normal redundancy switch from PrPRNC to BkPRNC Before you start • • • • • Resiliency association betweenPrPRNC-221 and BkPRNC-301 has been created. RNC-cl O&M is configured and permeable. BkPRNC-301 is in BACKUP mode. The RNC supports basic CS call, PS call. Iur interface is working. Procedure 1 Make the CS call, PS call and do inter-RNC handover to StPRNC-1. Step result Calls and Iur handover are successful. 526 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 2 RNC solution features Execute the redundancy switch. ZE1C:ACTIVATE:221:; LOADING PROGRAM VERSION 1.17-0 PLEASE NOTE THAT THIS RNC SERVICE'S BACKUP COMPLETENESS IS NOT 100% COMMAND EXECUTION WILL CAUSE SYSTEM RESTART CONFIRM COMMAND EXECUTION: Y/N ? CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNCSRV-221 WILL BE ACTIVATED COMMAND EXECUTED Step result BkPRNC-301 restarts and switch to active RNCSRV-221. PrPRNC-221 deactivates its RNCSRV-221. No relevant alarm raise up. • • • g Note: There some other expect behaviors which might be seen during testing: • • • • • • • 3 PrPRNC-221 switches to LOADED mode permanently. BTSOM and IuB connection will re-establish to BkPRNC-301. CN connection will re-establish to BkPRNC-301. IuR connection will re-establish to BkPRNC-301. OMS connection will re-establish to BkPRNC-301. IuBC connection will re-establish to BkPRNC-301. IuPC connection will establish to BkPRNC-301. Make the CS call, PS call and do inter-RNC handover to StPRNC-1. After all the signaling links in BkPRNC-301 are created, make the CS call, PS call and do the Inter-RNC handover to StPRNC-1. Step result Performing calls finished with success. 8.3.9.8.3 Redundancy switchback from BkPRNC to PrPRNC Before you start • • • DN09203161Issue:02 Resiliency switchover has been done. RNC-cl O&M is configured and permeable. PrPRNC-221 is in LOADED mode. ©2016Nokia 527 RNC solution features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Make the CS call, PS call and do inter-RNC handover to StPRNC-1. Make the CS call, PS call and do Inter-RNC handover to StPRNC-1 when the RNCSRV-221 is in BkPRNC-301. Step result Calls and Iur handover are successful. 2 Start the switch back from PrPRNC. Execute the below command to start the switch back from PrPRNC: < ZE1C:ACTIVATE; Step result LOADING PROGRAM VERSION 1.17-0 CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNC SERVICE IS ACTIVATED COMMAND EXECUTED 3 Make the CS call, PS call and do inter-RNC handover to StPRNC-1. After all the signaling links in PrPRNC-221 are created, make the CS call, PS call and do the Inter-RNC handover to StPRNC-1. Step result Performing calls finished with success. 528 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BTS solution features 9 BTS solution features 9.1 RAN3308: Flexi RFM 3T6R 2100 (FRGX) Introduction to the feature The RAN3308: Flexi RFM 3T6R 2100 (FRGX)feature introduces Flexi Multiradio RF Module (FRGX) for 3GPP 2100 MHz band (uplink: 1920 - 1980 MHz, downlink: 2110 2170 MHz). 9.1.1 RAN3308 Benefits Operator benefits The Flexi 3-sector RF Module 2100 (FRGX) can be used as a WCDMA and LTE RF Module. The feature provides the operator with the following benefits: • • • • • • 9.1.2 Full 80 W power over full 60 MHz bandwidth The most cost-efficient andcompact 3-sector BTS Site Industry leading RF integration level 3-sector RF in one outdoor IP65 box Low power consumption and OPEX Wide operating temperature range:-35°C - +55°C (-31°F - +131°F) without solar load RAN3308 Functional description The FRGX module supports WCDMA and LTE in dedicated or concurrent mode. It provides an output of 3x80 W at the antenna connector. TX/RX bandwidth is 60 MHz. The main features of the FRGX are as follows: • • • • • • • • • 3GPP 2100 MHz band supported. 3 U high with Flexi platform mechanics. EAC port. Optical chaining supportedby HW (three optical connectors with 6 Gbit/s interfaces). AISG2.0 antenna tilt support with external connector (RS485). Can be used in feederless BTS sites (optical andDC cable up to 200 m). Weight: 25 kg. Volume: 25 l. TX output power tolerance: – – 9.1.3 ≤ +-0.8dB in normal conditions, +15°C -+30°C (3GPP ≤ +-2.0dB). ≤ +-2.0dB in extreme conditions, -35°C -+55°C (3GPP ≤ +-2.5dB). RAN3308 System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces DN09203161Issue:02 ©2016Nokia 529 BTS solution features WCDMA 16 Feature Descriptions and Instructions There is no impact on interfaces. Impact on network and network element management tools There is no impact on network and network element management tools. Impact on system performance and capacity There is no impact on system performance and capacity. 9.1.4 RAN3308 Reference data Requirements g Note: Feature availability with Maintenance Package. Table 201 RAN3308 hardware and software requirements RAS I PA - R N C mc R N C WCDMA 16 Support not required Support not required OMS NetAct Support not required Support not required Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16 WBTS16 MS C S GSN Support not required Support not required MGW Support not required Not relevant UE Support not required This feature requires a Rel.2 or Rel.3 System Module. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no new or modified parameters related to this feature. Sales information Table 202 B S W /A S W BSW RAN3308 Sales information S W c o mp o n e n t RAN L i c e n s e c o n t r o l i n n e t w o r k e l e me n t - 9.2 RAN3158: Flexi RFM 6T6R 2100 (FRGU) Introduction to the feature 530 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BTS solution features The RAN3158: Flexi RFM 6T6R 2100 (FRGU)feature introduces Flexi Multiradio RF Module (FRGU) for 3GPP 2100 MHz band (uplink: 1920-1980 MHz, downlink: 21102170 MHz). 9.2.1 RAN3158 Benefits Operator benefits The Flexi 3-sector RF Module 2100 (FRGU) can be used as a WCDMA and LTE RF Module. This feature benefits the operator as follows: • • • • • • • • • • • 9.2.2 the most cost-efficient andcompact 3-sector BTS Site industry leading RF integration level 3-sector RF in one outdoor IP65 box low power consumption and OPEX ability to be used as a feederless site withone DC and 1...2 optical cables ability to build a TX div or 2TX/2RX MIMO for three sectors withonly one RF Module one 3-sector module providing a more cost effective solution than twoRF Modules or three RRHs in feederless installations reduced weight reduced wind load wide operating temperature range:-35°C - +55°C (-31°F - +131°F) without solar load 1/3 of DC and 1/3 or 2/3 of optical cabling compared to thesite with an RRH RAN3158 Functional description The FRGU module supports WCDMA and LTE in dedicated or concurrent mode. It provides an output of 6x60 W at the antenna connector. TX/RX bandwidth is 60 MHz. The main features of the FRGU are as follows: • • • • • • • • • 3GPP 2100 MHz band supported 3 U high with Flexi platform mechanics EAC port optical chaining supported byHW, three optical connectors with6 Gbit/s interfaces AISG2.0 antenna tilt support with external connector (RS485) ability to be used in feederless BTS sites (optical andDC cable up to 200 m) weight: 25 kg volume: 25 l TX output power tolerance: – – 9.2.3 ≤ +-0.8dB in normal conditions, +15°C -+30°C (3GPP ≤ +-2.0dB) ≤ +-2.0dB in extreme conditions, -35°C -+55°C (3GPP ≤ +-2.5dB) RAN3158 System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces DN09203161Issue:02 ©2016Nokia 531 BTS solution features WCDMA 16 Feature Descriptions and Instructions There is no impact on interfaces. Impact on network and network element management tools There is no impact on network and network element management tools. Impact on system performance and capacity There is no impact on system performance and capacity. 9.2.4 RAN3158 Reference data Requirements Table 203 RAN3158 hardware and software requirements RAS I PA - R N C mc R N C WCDMA 16 Support not required Support not required OMS NetAct Support not required Support not required Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16 WBTS16 MS C S GSN Support not required Support not required MGW Support not required Not relevant UE Support not required This feature requires System Module of Rel.2 or Rel.3. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no new or modified parameters related to this feature. Sales information Table 204 B S W /A S W BSW RAN3158 Sales information S W c o mp o n e n t RAN L i c e n s e c o n t r o l i n n e t w o r k e l e me n t - 9.3 RAN3246: Flexi RRH 2T2R 850 120W (FRCG) Introduction to the feature The RAN3246: Flexi RRH 2T2R 850 120W (FRCG)feature introduces Flexi Multiradio Remote Radio Head 2TX/2RX (FRCG) for 850 MHz 3GPP band 5 (uplink: 824 - 849 MHz, downlink: 869 - 894 MHz). 532 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 9.3.1 BTS solution features RAN3246 Benefits Operator benefits The RAN3246: Flexi RRH 2T2R 850 120W (FRCG)feature provides the following benefits: • • • • • • • • 9.3.2 Full 3GPP band 5 (850 MHz) supported Up to 2x60 W output power at the antenna connector Optical chaining supportedby HW, two optical connectors with 6Gbit/s interfaces 200 000 hours MTBF The most cost-efficient andcompact 2TX/2RX BTS Site Industry leading RF integration level Low power consumption and OPEX Can be used as a WCDMA and LTE module RAN3246 Functional description The FRCG module is able to support up to two sectors with a maximum 2x60 W output power at the BTS antenna connectors. TX/RX bandwidth is 25 MHz. The main features of the FRCG are as follows: • AISG2.0 antenna tilt support with external connector (RS485) EAC port Wide operating temperature range: -40°C- +55°C (-40°F - +131°F) with convectional • cooling 2TX/2RX RF in one outdoor IP65 box • • • • 30 l volume (without solar shield) 23 kg (50.7 lbs) weight The basic WCDMA configuration is up to 4+4 cells. For more information, seeFlexi Multiradio BTS WCDMA Supported Configurationsand Flexi Multiradio BTS RF Sharing Released Configurations . 9.3.3 RAN3246 System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces There is no impact on interfaces. Impact on network and network element management tools There is no impact on network and network element management tools. Impact on system performance and capacity There is no impact on system performance and capacity. 9.3.4 RAN3246 Reference data Requirements DN09203161Issue:02 ©2016Nokia 533 BTS solution features WCDMA 16 Feature Descriptions and Instructions Table 205 RAN3246 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 Support not required Support not required Not planned WBTS16 Not relevant OMS NetAct MSC SGSN MGW UE Support not required Support not required Support not required Support not required Support not required Support not required This feature requires System Module of Rel.3. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no new or modified parameters related to this feature. Sales information Table 206 RAN3246 Sales information BSW/ASW BSW SW component RAN License control in network element - 9.4 RAN3103: Flexi RRH 4T4R 1900 (FHFB) Introduction to the feature The RAN3103: Flexi RRH 4T4R 1900 (FHFB)feature introduces Flexi Multiradio Remote Radio Head 4TX/4RX (FHFB) for 1900 MHz 3GPP extended band 25 (uplink: 1850 1915 MHz, downlink: 1930 - 1995 MHz). 9.4.1 RAN3103 Benefits Operator benefits The Flexi 4TX/4RX RRH 1900 (FHFB) can be used as a WCDMA and LTE module. 534 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BTS solution features This feature benefits the operator as follows: • • • • • • • • • 9.4.2 the most cost-efficient andcompact 4TX/4RX BTS Site industry leading RF integration level SW configurable radio: thesame RF Module for LTE, HSPA+ and WCDMA 4TX/4RX RF in one outdoor IP65 box wide operating temperature range: -35°C- +55°C (-31°F - +131°F) with convectional cooling low power consumption and OPEX ability to be used as feederless site with oneDC and 1...2 optical cables 30 l volume (without solar shield) 23 kg (50.6 lbs) weight RAN3103 Functional description The FHFB module is able to support up to four sectors with a maximum 4x40 W output power at the BTS antenna connectors. TX/RX bandwidth is 65 MHz. The main features of the FHFB are as follows: • extended 3GPP band 25 (1900 MHz) supported • optimization for single sector deployment with 4TX MIMO 4-way uplink RX maximum ratio combining (MRC) HW support • • optical chaining supported byHW, two optical connectors with6 Gbit/s interfaces EAC port • • AISG2.0 antenna tilt support with external connector (RS485) ability to be used in feederless BTS sites (optical andDC cable up to 200 m) • The following are some basic WCDMA configurations: • • 9.4.3 up to 4+4+4+4 cells 8, 10, 20, 30 or 40 W mode per sector (by SW licenses) RAN3103 System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces There is no impact on interfaces. Impact on network and network element management tools There is no impact on network and network element management tools. Impact on system performance and capacity There is no impact on system performance and capacity. 9.4.4 RAN3103 Reference data Requirements DN09203161Issue:02 ©2016Nokia 535 BTS solution features WCDMA 16 Feature Descriptions and Instructions Table 207 RAN3103 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 Support not required Support not required Not planned WBTS16 Not relevant OMS NetAct MSC SGSN MGW UE Support not required Support not required Support not required Support not required Support not required Support not required This feature requires System Module of Rel.3. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no new or modified parameters related to this feature. Sales information Table 208 RAN3103 Sales information BSW/ASW BSW SW component RAN License control in network element - 9.5 RAN3324: FRIJ AirScale RRH 4T4R B66 160 W Introduction to the feature The RAN3324: FRIJ AirScale RRH 4T4R B66 160 Wfeature introduces the FRIJ AirScale RRH 4T4R B66 160 W (uplink: 1710 - 1780 MHz, downlink: 2110 - 2200 MHz). The FRIJ module can also support 3GPP band 4 and band 10. 9.5.1 RAN3324 Benefits Operator benefits The FRIJ AirScale RRH can be used as a WCDMA and LTE module. 536 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BTS solution features The feature provides the operator with the following benefits: • • • • • • • • • 9.5.2 Four Power Amplifiers that enable supporting onesector with up to 4x40 W 4TX MIMO output power at the BTS antenna connectors. FRIJ RRH supports 1 or 2 sector operation. It supports 4x40 W that allows using the entire spectrum splitover 4-pipes. Smaller size and weight compared to prior generation. New, industrial designed outershell and book mount design. IP65 environmental protection class. Its bandwidth filter supportsthe whole 3GPP band 66 (70/90 MHz). Full band (70 UL/90 DL) instantaneous bandwidthenables carriers to be placed anywhere in the band from a single RRH. Optional fan module for additional mounting schemes are available. RAN3324 Functional description The FRIJ module can support up to four sectors with a maximum 4x40 W output power at the BTS antenna connectors. The main features of the FRIJ are as follows: • • • • • • • • • • • • It supports 3GPP FDD bands 4, 10 and band66, with 10 W, 15 W, 20 W, 30 W, 40 W output power per Tx. Up to 4 carriers per antenna connector with amaximum occupied bandwidth of40 MHz. Multiple carriers withmaximum instantaneous bandwidthof 70MHz in uplink and 90MHz in downlink Optical chaining supportedby HW; three 6 Gbit/s optical interfaces. Up to four external alarms. WCDMA RF Sharing Bandwidths: 3.8MHz, 4.2 MHz, 5 MHz. AISG2.0 antenna tilt support with external connector (RS485). MHA, DC and AISG over RF connection supported. 256 QAM LTE supported. -40°C to +40°C with convection cooling. 28 l volume. 21 kg (46.3 lbs) weight. The FRIJ module can be installed: • on a pole. on a wall. vertically without fans. horizontally with fans. • inside the Radio Antenna System (RAS). • • • 9.5.3 RAN3324 System impact Interdependencies between features There are no interdependencies between features. Impact on interfaces DN09203161Issue:02 ©2016Nokia 537 BTS solution features WCDMA 16 Feature Descriptions and Instructions There is no impact on interfaces. Impact on network and network element management tools There is no impact on network and network element management tools. Impact on system performance and capacity There is no impact on system performance and capacity. 9.5.4 RAN3324 Reference data Requirements Table 209 RAN3324 hardware and software requirements RAS I PA - R N C mc R N C Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 Support not required Support not required Support not required WBTS16 OMS NetAct Support not required Support not required MS C S GSN Support not required Support not required MGW Support not required Not relevant UE Support not required This feature requires new hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no new or modified parameters related to this feature. Sales information Table 210 B S W /A S W BSW RAN3324 Sales information S W c o mp o n e n t RAN L i c e n s e c o n t r o l i n n e t w o r k e l e me n t - 9.6 RAN3237: HSUPA Scheduler Capacity Increase for FSMF Introduction to the feature HSUPA scheduler capacity increase up to 320 HSUPA users. 538 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions 9.6.1 BTS solution features RAN3237 Benefits End-user benefits This feature does not affect end user experience. Operator benefits This feature benefits the operator as follows: • • 9.6.2 Support for more HSUPA users per Local Cell Group. Only SW upgrade to WBTS16 is needed to obtain the benefits, noneed for recommissioning. RAN3237 Functional description HSUPA scheduler capacity is increased from 240 to 320 HSUPA users when Local Cell Group is configured into Normal HSPA mode. If Local Cell Group is configured into Small HSPA mode then HSUPA scheduler capacity is increased from 160 to 240 HSUPA users. When more HSUPA users per Local Cell Group are supported it may enable operator to activate less Local Cell Groups and thus enabling more baseband capacity can be used for user traffic. 9.6.3 RAN3237 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity HSUPA scheduler capacity increase: • • 9.6.4 from 240 to 320 HSUPA users in case of Normal HSPA configuration from 160 to 240 HSUPA users in case of Small HSPA configuration RAN3237 Reference data Requirements Table 211 DN09203161Issue:02 RAN3237 hardware and software requirements RAS I PA - R N C mc R N C WCDMA 16 Support not required Support not required ©2016Nokia Fl exi Multiradio BTS Not planned Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16 Not planned 539 BTS solution features WCDMA 16 Feature Descriptions and Instructions Table 211 RAN3237 hardware and software requirements (Cont.) OMS NetAct Support not required NetAct 16.2 MS C S GSN Support not required Support not required MGW Support not required UE Support not required Flexi Multiradio System Module FSMF or newer is required. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 212 RAN3237 Sales information BSW/ASW BSW 9.6.5 SW component RAN License control in network element BTS LK Testing RAN3237: HSUPA Scheduler capacity increase for FSMF Before you start Test environment: • • Hardware requirement: FSMF. Hardware requirement: WCDMA16. Preconditions: • • • RAN1686: HSPA 72 Users Per Cell or RAN2124: HSPA 128 Users per Cell is enabled. RAN1201: Fractional DPCH is enabled. F222 with 1 Local Cell Group. • 320 WCDMA terminals supporting3GPP Rel7 or onward. • • 540 HSPA is enabled for all cells, and a sufficient amount ofprocessing set licenses are used. PIC and FDE are disabled unless otherwise mentioned. ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BTS solution features Procedure 1 320 HSUPA u sers Normal HSUPA is configured. Required actions: a) Add 320 terminals evenly to six cells. b) Open ping session in every terminal. Expected Results: 320 Ping sessions can archive. 2 240 HSUPA u sers Small HSPA is configured Required actions: a) Add 240 terminals evenly to six cells. b) Open ping session in every terminal. Expected Results: 240 Ping sessions can archive. 9.7 RAN2249: Support for Multi-Antenna RET Device Introduction to the feature RAN2249: Support for Multi-Antenna RET Deviceintroduces support for multi-antenna and AISG2.0 compliant remote electrical tilt (RET) devices to Flexi Multiradio BTS. Multi-antenna RETs are typically installed with multiband antennas, which enables the tilting of each band to be controlled separately. 9.7.1 RAN2249 Benefits End-user benefits This feature does not affect end user experience. Operator benefits Multiband antennas with Multi-RET bring the following benefits: • • • 9.7.2 Installation is easier and takes less time. The amount of antennas and cables on the mast is reduced. Tilting for each band is controlled separately. RAN2249 Functional description RAN2249: Support for Multi-Antenna RET Deviceintroduces support for multi-antenna and AISG2.0 compliant RET devices by Flexi Multiradio BTS. DN09203161Issue:02 ©2016Nokia 541 BTS solution features WCDMA 16 Feature Descriptions and Instructions All Antenna Line Device (ALD) suppliers have available equipment compatible with 3GPP/AISG2.0 standards. An antenna can support transmission/reception on different frequency bands, for example, dual band antenna. With a built-in multi-antenna RET device, the physical downtilt of each antenna beam can be separately configured for each supported frequency band. The tilt configuration can be controlled and independentlyconfigured with network management system (NetAct or 3rd party NMS) or the BTS Site Manager. This feature is licensed with SW license for RAN906: Flexi WCDMA BTS 3GPP Antenna tilt support. Activating the antenna tilt license also activates support for multi-antenna RET devices. 9.7.3 RAN2249 System impact Interdependencies between features Together with this feature, the operator must consider the usage of RAN2172: Multi-Band Load Balancing and other layering features that have blind HO/redirection functionality and assume equal coverage between frequency layers. This feature is related to the following features: • • LTE1657: Support for Multi-antenna RET device RAN906: Flexi WCDMA BTS 3GPP Antenna tilt support Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools NetAct 16.2 is required. Impact on system performance and capacity This feature has no impact on system performance and capacity. 9.7.4 RAN2249 Reference data Requirements Table 213 RAN2249 hardware and software requirements RAS I PA - R N C mc R N C WCDMA 16 Support not required Support not required OMS NetAct Support not required NetAct 16.2 MS C Support not required Flexi Multiradio BTS WBTS16 S GSN Support not required Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16 MGW Support not required Not relevant UE Support not required This feature requires RF Modules of Rel.1 or higher and System Modules of Rel.2 or Rel.3. Alarms There are no alarms related to this feature. 542 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BTS solution features Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 214 New parameters introduced by RAN2249 F u l ln a m e A b b r e v i a t e dn a m e RET antenna unit number M a n a g e d Parent structure object RET retAntUnitNumber RET device type RET retDeviceType - Sales information Table 215 RAN2249 Sales information B SW/AS W ASW g S W c o mp o n e n t RAN L i c e n s e c o n t r o l i n n e t w o r k e l e me n t BTS LK Note: This feature has a common license with the RAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Supportfeature. 9.8 RAN3238: WCDMA BTS Support for Harmonized MHA Family Introduction to the feature RAN3238: WCDMA BTS Support for Harmonized MHA Familyintroduces support for new Masthead Amplifiers (MHAs), which streamlines the MHA family. 9.8.1 RAN3238 Benefits End-user benefits This feature does not affect end user experience. Operator benefits This feature benefits the operator as follows: • • • • DN09203161Issue:02 Provides comprehensive MHAportfolio supporting newMHA requirements from the operators. Dual band MHAs based on dual AISG mode provide full MHA visibility for both bands. Full visibility/recovery of fault situation in both bands is enabled. New MHAs have a gain of 12 dB. There is no need for high gain MHAs anymore. ©2016Nokia 543 BTS solution features 9.8.2 WCDMA 16 Feature Descriptions and Instructions RAN3238 Functional description Harmonized Nokia MHA family consist of a wide range MHAs for single and dual band use, that have the following functionalities: • • • • • • • • AISG 2.0 support 12 dB gain excellent Passive Inter Modulation specification (-116 dBm) dual AISG/RET enabling flexible controlfor dual band MHAs MHA/RET control according to AISG/3GPP standard RF by-pass functionality built-in lightning protection guaranteed compatibility with Nokia Multiradio BTS Configuration management tools can identify new MHAs as part of the harmonized MHA family and recognize them through Nokia product codes in the user interface. g Note: Nokia MHAs are active (AISG2.0) MHAs. However, it is possible for the operator to select passive (CWA) mode. From the harmonized MHA family, only single band MHAs (MDTB, MDGB and MDPB) can support CWA mode. Table 216: MHAs in harmonized MHA familylists new MHAs supported by WCDMA software that can be commissioned as official Nokia MHAs. Table 216 9.8.3 MHAs in harmonized MHA family M H A n ame MDTB 850 B an d Pr od u ct c o de A d d i t i o n al i n f o rmati o n 473060A Replaces old 32 dB MDTA MDGB 900 473058A Replaces old 32 dB MDGA MDPB 1900 473059A Replaces old 33 dB MDPA FLDA EU800/900 CS7299440 2 antenna ports FLDB EU800/900 473050A 4 antenna ports FLGA 1800/2100 472962A 2 antenna ports FLGC 1800/2100 473051A 4 antenna ports FLTA 2100/2600 473056A 2 antenna ports FLTB 2100/2600 473057A 4 antenna ports RAN3238 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools A new MHA type, "Nokia" MHA, is introduced into NetAct and BTS Site Manager. Impact on system performance and capacity 544 ©2016Nokia DN09203161Issue:02 WCDMA 16 Feature Descriptions and Instructions BTS solution features This feature has no impact on system performance or capacity. 9.8.4 RAN3238 Reference data Requirements Table 217 RAN3238 hardware and software requirements RAS I PA - R N C mc R N C WCDMA 16 Support not required Support not required OMS NetAct Support not required Support not required Fl exi Multiradio BTS WBTS16 MS C BTS WBTS16 S GSN Support not required Flexi Flexi Lite Multiradio 10 BTS Not relevant MGW Support not required UE Support not required Support not required This feature requires System Modules of Rel.2 or higher. BTS faults and reported alarms Table 218 New BTS faults introduced by RAN3238: WCDMA BTS Support for Harmonized MHA Family F a u l tI D F a u l tn a me R e p o r t e da l a r m s A l a r mI D 4270 MHA in bypass mode 7652 A l a r mn a m e BASE STATION NOTIFICATION 7654 CELL OPERATION DEGRADED For fault descriptions, see Flexi Multiradio BTS WCDMA Faults. Measurements and counters There are no measurements and counters related to theRAN3238: WCDMA BTS Support for Harmonized MHA Familyfeature. Key performance indicators There are no key performance indicators related to theRAN3238: WCDMA BTS Support for Harmonized MHA Family feature. Parameters Table 219 Modified parameters F ul l n ame MHAtype A b b r e v i a t e d n a me mhaType MHA M an ag e d o bj e c t P are n t s t ru c tu r e - For parameter descriptions, seeFlexi Multiradio BTS WCDMA Parameters. Sales information DN09203161Issue:02 ©2016Nokia 545 BTS solution features WCDMA 16 Feature Descriptions and Instructions Table 220 RAN3238 Sales information BSW/ASW BSW 546 SW component RAN License control in network element - ©2016Nokia DN09203161Issue:02 </div> </div> </div> </div> </div> </div> </div> </div> <div class="modal fade" id="report" tabindex="-1" role="dialog" aria-hidden="true"> <div class="modal-dialog"> <div class="modal-content"> <form role="form" method="post" action="https://idoc.tips/report/wcdma16-feature-descriptions-and-instructions-pdf-free" style="border: none;"> <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button> <h4 class="modal-title">Report "Wcdma16 Feature Descriptions and Instructions"</h4> </div> <div class="modal-body"> <div class="form-group"> <label>Your name</label> <input type="text" name="name" required="required" class="form-control" /> </div> <div class="form-group"> <label>Email</label> <input type="email" name="email" required="required" class="form-control" /> </div> <div class="form-group"> <label>Reason</label> <select name="reason" required="required" class="form-control"> <option value="">-Select Reason-</option> <option value="pornographic" selected="selected">Pornographic</option> <option value="defamatory">Defamatory</option> <option value="illegal">Illegal/Unlawful</option> <option value="spam">Spam</option> <option value="others">Other Terms Of Service Violation</option> <option value="copyright">File a copyright complaint</option> </select> </div> <div class="form-group"> <label>Description</label> <textarea name="description" required="required" rows="3" class="form-control" style="border: 1px solid #cccccc;"></textarea> </div> <div class="form-group"> <div style="display: inline-block;"> <div class="g-recaptcha" data-sitekey="6LcHT8sZAAAAAPKfs_PZGhwvz-OHbUMuekQzz5xK"></div> </div> </div> <script src='https://www.google.com/recaptcha/api.js'></script> </div> <div class="modal-footer"> <button type="button" class="btn btn-default" data-dismiss="modal">Close</button> <button type="submit" class="btn btn-success">Send</button> </div> </form> </div> </div> </div> <script> $(document).ready(function () { var inner_height = $(window).innerHeight() - 250; $('#pdfviewer').css({"height": inner_height + "px"}); }); </script> <footer class="footer" style="margin-top: 60px;"> <div class="container-fluid"> Copyright © 2025 IDOC.TIPS. All rights reserved. <div class="pull-right"> <a href="https://idoc.tips/about">About Us</a> | <a href="https://idoc.tips/privacy">Privacy Policy</a> | <a href="https://idoc.tips/term">Terms of Service</a> | <a href="https://idoc.tips/copyright">Copyright</a> | <a href="https://idoc.tips/contact">Contact Us</a> | <a href="https://idoc.tips/cookie_policy">Cookie Policy</a> </div> </div> </footer>  <div class="modal fade" id="login" tabindex="-1" role="dialog" aria-labelledby="myModalLabel"> <div class="modal-dialog" role="document"> <div class="modal-content"> <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-label="Close" on="tap:login.close">×</button> <h4 class="modal-title" id="add-note-label">Sign In</h4> </div> <div class="modal-body"> <form action="https://idoc.tips/login" method="post"> <div class="form-group"> <label class="sr-only" for="email">Email</label> <input class="form-input form-control" type="text" name="email" id="email" value="" placeholder="Email" /> </div> <div class="form-group"> <label class="sr-only" for="password">Password</label> <input class="form-input form-control" type="password" name="password" id="password" value="" placeholder="Password" /> </div> <div class="form-group"> <div class="checkbox"> <label class="form-checkbox"> <input type="checkbox" name="remember" value="1" /> Remember me </label> <label class="pull-right"><a href="https://idoc.tips/forgot">Forgot password?</a></label> </div> </div> <button class="btn btn-primary btn-block" type="submit">Sign In</button> </form> </div> </div> </div> </div>  <script async src="https://www.googletagmanager.com/gtag/js?id=UA-177830117-1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-177830117-1'); </script> <script src="https://idoc.tips/assets/js/jquery-ui.min.js"></script> <link rel="stylesheet" href="https://idoc.tips/assets/css/jquery-ui.css"> <script> $(function () { $("#document_search").autocomplete({ source: function (request, response) { $.ajax({ url: "https://idoc.tips/suggest", dataType: "json", data: { term: request.term }, success: function (data) { response(data); } }); }, autoFill: true, select: function (event, ui) { $(this).val(ui.item.value); $(this).parents("form").submit(); } }); }); </script>  <div id="IDOCTIPS_cookie_box" style="z-index:99999; background: #97c479; width: 100%; position: fixed; padding: 5px 15px; text-align: center; left:0; bottom: 0;"> Our partners will collect data and use cookies for ad personalization and measurement. <a href="https://idoc.tips/cookie_policy" target="_blank">Learn how we and our ad partner Google, collect and use data</a>. <a href="#" class="btn btn-success" onclick="accept_IDOCTIPS_cookie_box();return false;">Agree & close</a> </div> <script> function accept_IDOCTIPS_cookie_box() { document.cookie = "IDOCTIPS_cookie_box_viewed=1;max-age=15768000;path=/"; hide_IDOCTIPS_cookie_box(); } function hide_IDOCTIPS_cookie_box() { var cb = document.getElementById('IDOCTIPS_cookie_box'); if (cb) { cb.parentElement.removeChild(cb); } } (function () { var IDOCTIPS_cookie_box_viewed = (function (name) { var matches = document.cookie.match(new RegExp("(?:^|; )" + name.replace(/([\.$?*|{}\[\]\\\/\+^])/g, '\\$1') + "=([^;]*)")); return matches ? decodeURIComponent(matches[1]) : undefined; })('IDOCTIPS_cookie_box_viewed'); if (IDOCTIPS_cookie_box_viewed) { hide_IDOCTIPS_cookie_box(); } })(); </script>  </body> </html>

Wcdma16 Feature Descriptions and Instructions

Recommend Documents