You are on page 1of 433

Nokia Networks

WCDMA RAN, Rel. WCDMA
16, Operating Documentation,
Issue 03, Documentation
Change Delivery 1
WCDMA 16 Feature
Descriptions and Instructions
DN09203161
Issue 01E
Approval Date 2016-02-18
 
 

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

f
 

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

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

2

DN09203161

Issue: 01E

WCDMA 16 Feature Descriptions and Instructions

Table of Contents
This document has 433 pages
 

 

Summary of changes................................................................... 21
 

 

1

Introduction to WCDMA 16 features............................................ 24

 

 

2

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

 

 

3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5

Radio resource management features.........................................28
RAN3045: Activity Based UL Power Control for Rel99 DCH....... 28
RAN3045 Benefits........................................................................28
RAN3045 Functional description..................................................28
RAN3045 System impact............................................................. 28
RAN3045 Reference data............................................................ 29
Activating RAN3045: Activity Based UL Power Control for Rel99
DCH............................................................................................. 30
Verifying RAN3045: Activity Based UL Power Control for Rel99
DCH............................................................................................. 31
Deactivating RAN3045: Activity Based UL Power Control for
Rel99 DCH................................................................................... 32
Testing RAN3045: Activity Based UL Power Control for Rel99
DCH............................................................................................. 33
Phase 1: Testing with the RAN3045: Activity Based UL Power
Control for Rel99 DCH feature deactivated..................................34
Phase 2: Testing with the RAN3045: Activity Based UL Power
Control for Rel99 DCH feature activated......................................35
RAN3043: Advanced HSUPA Time Division Scheduling............. 36
RAN3043 Benefits........................................................................36
RAN3043 Functional description..................................................37
RAN3043 System impact............................................................. 37
RAN3043 Reference data............................................................ 38
Activating RAN3043: Advanced HSUPA Time Division Scheduling.
39
Verifying RAN3043: Advanced HSUPA Time Division Scheduling..
40
Deactivating RAN3043: Advanced HSUPA Time Division
Scheduling................................................................................... 41
RAN3218: Enhanced Cell Change from HSPA to 2G.................. 42
RAN3218 Benefits........................................................................42
RAN3218 Functional description..................................................43
RAN3218 System impact............................................................. 43
RAN3218 Reference data............................................................ 44
Activating RAN3218: Enhanced Cell Change from HSPA to 2G.....
45
Verifying RAN3218: Enhanced Cell Change from HSPA to 2G... 47
Deactivating RAN3218: Enhanced Cell Change from HSPA to 2G.
48

3.1.6
3.1.7
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
3.2.5
3.2.6
3.2.7
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7

Issue: 01E

DN09203161

3

WCDMA 16 Feature Descriptions and Instructions

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
3.4.7.6
3.4.7.7
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6

4

RAN3093: Enhanced MBLB.........................................................49
RAN3093 Benefits........................................................................49
RAN3093 Functional description..................................................49
RAN3093 System impact............................................................. 51
RAN3093 Reference data............................................................ 51
Activating RAN3093: Enhanced MBLB........................................ 54
Activating Enhanced load balancing............................................ 55
Activating Enhanced layering during voice call setup - Blind IFHO
in RRC setup................................................................................56
Activating Enhanced layering during voice call setup - Blind IFHO
for CS voice call from CCH state................................................. 57
Activating MBLB HSPA load state bypass................................... 58
Activating Enhanced inactivity-triggered layering without
compressed mode measurements...............................................59
Activating Enhanced mobility triggered layering.......................... 62
Activating Enhanced inactivity triggered layering in state transition
to CCH state.................................................................................63
Verifying RAN3093: Enhanced MBLB..........................................64
Verifying Enhanced load balancing.............................................. 64
Verifying Enhanced layering during voice call setup - Blind IFHO
in RRC setup................................................................................66
Verifying Enhanced layering during voice call setup - Blind IFHO
for CS voice call from CCH state................................................. 68
Verifying the MBLB HSPA load state bypass............................... 69
Verifying Enhanced inactivity-triggered layering without
compressed mode measurements...............................................72
Verifying Enhanced mobility-triggered layering............................ 75
Verifying Enhanced inactivity-triggered layering in state transition
to CCH state.................................................................................76
Deactivating RAN3093: Enhanced MBLB....................................78
Deactivating Enhanced load balancing........................................ 78
Deactivating Enhanced layering during voice call setup - Blind
IFHO in RRC setup...................................................................... 79
Deactivating Enhanced layering during voice call setup - Blind
IFHO for CS voice call from CCH state........................................ 80
Deactivating the MBLB HSPA load state bypass......................... 81
Deactivating Enhanced inactivity triggered layering without
compressed mode measurements...............................................82
Deactivating Enhanced mobility triggered layering...................... 83
Deactivating Enhanced inactivity triggered layering in state
transition to CCH state................................................................. 84
RAN2518: High Speed Cell_FACH Enhanced.............................85
RAN2518 Benefits........................................................................85
RAN2518 Functional description..................................................86
RAN2518 System impact............................................................. 86
RAN2518 Reference data............................................................ 87
Activating RAN2518: High Speed Cell_FACH Enhanced............ 90
Verifying RAN2518: High Speed Cell_FACH Enhanced.............. 92

DN09203161

Issue: 01E

WCDMA 16 Feature Descriptions and Instructions

3.5.7
3.5.8
3.5.8.1
3.5.8.2
3.6
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
3.7
3.7.1
3.7.2
3.7.3
3.7.4
3.7.5
3.7.6
3.7.7
3.7.8
3.8
3.8.1
3.8.2
3.8.3
3.8.4
3.8.5
3.8.6
3.8.7
3.9
3.9.1
3.9.2
3.9.3
3.9.4
3.9.5
3.9.6
3.9.7
3.9.8
3.10
3.10.1
3.10.2
3.10.3
3.10.4
3.10.5

Issue: 01E

Deactivating RAN2518: High Speed Cell_FACH Enhanced........ 94
Testing RAN2518: High Speed Cell_FACH Enhanced................ 96
Testing the RAN2518: High Speed Cell_FACH Enhanced related
counters....................................................................................... 96
Testing the subunits consumption of reserved HSUPA resource
steps for HS-RACH users............................................................ 96
RAN2869: HSPA Subscriber Increase......................................... 98
RAN2869 Benefits........................................................................99
RAN2869 Functional description..................................................99
RAN2869 System impact............................................................. 99
RAN2869 Reference data.......................................................... 100
Activating RAN2869: HSPA Subscriber Increase.......................101
Verifying RAN2869: HSPA Subscriber Increase........................ 103
Deactivating RAN2869: HSPA Subscriber Increase.................. 104
RAN3040: IRC Receiver............................................................ 105
RAN3040 Benefits......................................................................105
RAN3040 Functional description................................................105
RAN3040 System impact........................................................... 106
RAN3040 Reference data.......................................................... 106
Activating RAN3040: IRC Receiver............................................108
Verifying RAN3040: IRC Receiver............................................. 109
Deactivating RAN3040: IRC Receiver....................................... 109
Testing RAN3040: IRC Receiver................................................ 110
RAN3235: Optimized Packet Handling at RNC .........................112
RAN3235 Benefits...................................................................... 112
RAN3235 Functional description................................................ 112
RAN3235 System impact........................................................... 113
RAN3235 Reference data.......................................................... 114
Activating RAN3235: Optimized Packet Handling at RNC......... 115
Verifying RAN3235: Optimized Packet Handling at RNC........... 116
Deactivating RAN3235: Optimized Packet Handling at RNC..... 117
RAN2902: RACH Capacity Increase.......................................... 118
RAN2902 Benefits...................................................................... 118
RAN2902 Functional description................................................ 119
RAN2902 System impact........................................................... 120
RAN2902 Reference data.......................................................... 120
Activating RAN2902: RACH Capacity Increase......................... 122
Verifying RAN2902: RACH Capacity Increase...........................124
Deactivating RAN2902: RACH Capacity Increase.....................125
Testing RAN2902: RACH Capacity Increase............................. 126
RAN2892: WCDMA-LTE Load Balancing.................................. 131
RAN2892 Benefits......................................................................131
RAN2892 Functional description................................................132
RAN2892 System impact........................................................... 135
RAN2892 Reference data.......................................................... 135
Activating RAN2892: WCDMA-LTE Load Balancing..................137

DN09203161

5

WCDMA 16 Feature Descriptions and Instructions

3.10.6
3.10.7

Verifying RAN2892: WCDMA-LTE Load Balancing....................139
Deactivating RAN2892: WCDMA-LTE Load Balancing..............141

 

 

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
4.2.3
4.2.4
4.2.5
4.2.5.1
4.2.6
4.2.6.1
4.2.7
4.2.7.1
4.2.7.2

Telecom features........................................................................142
RAN3086: CSFB with RIM......................................................... 142
RAN3086 Benefits......................................................................142
RAN3086 Functional description................................................142
RAN3086 System impact........................................................... 145
RAN3086 Reference data.......................................................... 145
Activating RAN3086: CSFB with RIM........................................ 146
Verifying RAN3086: CSFB with RIM.......................................... 148
Deactivating RAN3086: CSFB with RIM.................................... 149
RAN3082: Device Detection...................................................... 150
RAN3082 Benefits......................................................................151
RAN3082 Functional Description............................................... 151
RAN3082 System impact........................................................... 153
RAN3082 Reference data.......................................................... 153
Activating RAN3082: Device Detection......................................154
Activating generic IMEI query in the RNC..................................157
Verifying RAN3082: Device Detection........................................158
Verifying generic IMEI query in the RNC....................................160
Deactivating RAN3082: Device Detection..................................161
Deactivating a Whitelist or Blacklist functionality....................... 161
Deactivating generic IMEI query in the RNC..............................162

 

 

5
5.1
5.1.1
5.1.2
5.1.3
5.1.4
5.2
5.2.1
5.2.2
5.2.3
5.2.4

Transmission and transport features..........................................164
RAN3112: mcRNC Integrated Ethernet Switching..................... 164
RAN3112 Benefits...................................................................... 164
RAN3112 Functional description................................................ 164
RAN3112 System impact........................................................... 165
RAN3112 Reference data.......................................................... 166
RAN3193: OSPF Authentication for Controller.......................... 167
RAN3193 Benefits......................................................................168
RAN3193 Functional description................................................168
RAN3193 System impact........................................................... 169
RAN3193 Reference data.......................................................... 169

 

 

6
6.1
6.1.1
6.1.2
6.1.3
6.1.4
6.2

Operability features.................................................................... 171
RAN3242: Category for Obsolete Parameters...........................171
RAN3242 Benefits......................................................................171
RAN3242 Functional description................................................171
RAN3242 System impact........................................................... 172
RAN3242 Reference data.......................................................... 173
RAN2706: Delta Configuration and Change Notification for BTS
Transport.................................................................................... 174
RAN2706 Benefits......................................................................174
RAN2706 Functional description................................................175

6.2.1
6.2.2

6

DN09203161

Issue: 01E

WCDMA 16 Feature Descriptions and Instructions

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
6.4.5.1.1
6.4.5.1.2
6.4.5.1.3
6.4.5.2
6.4.5.2.1
6.4.5.2.2
6.4.5.2.3
6.4.5.3
6.4.5.3.1
6.4.5.3.2
6.5
6.5.1
6.5.2
6.5.3
6.5.4
6.5.5
6.5.6
6.5.7
6.5.8
6.5.8.1
6.5.8.2
6.5.8.3
6.6
6.6.1

Issue: 01E

RAN2706 System impact........................................................... 179
RAN2706 Reference data.......................................................... 180
RAN2367: DNS Support for Certificate Examination................. 181
RAN2367 Benefits......................................................................181
RAN2367 Functional description................................................181
RAN2367 System impact........................................................... 182
RAN2367 Reference data.......................................................... 183
RAN3247/LTE2507/RG602496: Energy Efficiency Shut Down
Mode with RF Sharing................................................................184
RAN3247/LTE2507/RG602496 Benefits.................................... 184
RAN3247/LTE2507/RG602496 Functional description.............. 184
RAN3247/LTE2507/RG602496 System impact......................... 184
RAN3247/LTE2507/RG602496 Reference data........................ 185
Activating RAN3247: Energy Efficiency Shut Down Mode with RF
Sharing.......................................................................................185
Activating RG301936: Intelligent MCPA TRX shutdown in GSM.....
186
Activating RG301936: Intelligent MCPA TRX shutdown............ 186
Verifying RG301936: Intelligent MCPA TRX shutdown.............. 186
Deactivating RG301936: Intelligent MCPA TRX shutdown........ 188
Activating RAN955: Power Saving Mode for BTS in WCDMA...188
Activating RAN955: Power Saving Mode for BTS......................188
Verifying RAN955: Power Saving Mode for BTS....................... 191
Deactivating RAN955: Power Saving Mode for BTS................. 192
Activating LTE1103: Load Based Power Saving for Multi-layer
Networks in LTE......................................................................... 193
Activating LTE1103: Load Based Power Saving for Multi-layer
Networks.................................................................................... 193
Deactivating LTE1103: Load Based Power Saving for Multi-layer
Networks.................................................................................... 195
RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing........... 196
RAN3060 Benefits......................................................................196
RAN3060 Functional description................................................196
RAN3060 System impact........................................................... 198
RAN3060 Reference data.......................................................... 199
Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing.
201
Verifying RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing...
203
Deactivating RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing........................................................................................ 206
Testing RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing.....
207
Test case 1: RF-scanning...........................................................207
Test case 2: PIM simulation........................................................211
Test case 3: PIM desensitization................................................212
RAN2872: IPA-RNC Symptom Report....................................... 214
RAN2872 Benefits......................................................................215

DN09203161

7

WCDMA 16 Feature Descriptions and Instructions

6.6.2
6.6.3
6.6.4
6.6.5
6.6.6
6.6.6.1
6.6.6.2
6.7
6.7.1
6.7.2
6.7.3
6.7.4
6.7.5
6.7.6
6.7.7
6.8
6.8.1
6.8.2
6.8.3
6.8.4
6.9
6.9.1
6.9.2
6.9.3
6.9.4
6.9.5
6.10
6.10.1
6.10.2
6.10.3
6.10.4
6.11
6.11.1
6.11.2
6.11.3
6.11.4
6.12
6.12.1
6.12.2
6.12.3
6.12.4
6.12.5
6.13
6.13.1
6.13.2

8

RAN2872 Functional description................................................215
RAN2872 System impact........................................................... 216
RAN2872 Reference data.......................................................... 216
Configuring RAN2872: IPA-RNC Symptom Report....................217
Testing RAN2872: IPA-RNC Symptom Report...........................224
Symptom report collection using OMS CLI................................ 225
Symptom report collection using RNC MML commands............226
RAN3063: KPI Reporting Based on Cell Type........................... 229
RAN3063 Benefits......................................................................229
RAN3063 Functional description................................................229
RAN3063 System impact........................................................... 229
RAN3063 Reference data.......................................................... 229
Activating RAN3063: KPI Reporting Based on Cell Type.......... 230
Verifying RAN3063: KPI Reporting Based on Cell Type............ 231
Deactivating RAN3063: KPI Reporting Based on Cell Type...... 233
RAN3150: mcRNC Event Based Symptom Data Collection...... 233
RAN3150 Benefits......................................................................234
RAN3150 Functional description................................................234
RAN3150 System impact........................................................... 235
RAN3150 Reference data.......................................................... 235
RAN2991: Modification of WCDMA Frequency......................... 236
RAN2991 Benefits......................................................................236
RAN2991 Functional description................................................237
RAN2991 System impact........................................................... 239
RAN2991 Reference data.......................................................... 240
Testing RAN2991: Modification of WCDMA Frequency............. 241
RAN2268: Multi-Layer Certificate Authorities.............................242
RAN2268 Benefits......................................................................242
RAN2268 Functional description................................................242
RAN2268 System impact........................................................... 244
RAN2268 Reference data.......................................................... 244
RAN3096: OMS HP Gen9 HW...................................................245
RAN3096 Benefits......................................................................245
RAN3096 Functional description................................................246
RAN3096 System impact........................................................... 246
RAN3096 Reference data.......................................................... 246
RAN2702: Parameter Level Logging of BTS User Events.........247
RAN2702 Benefits......................................................................247
RAN2702 Functional description................................................247
RAN2702 System impact........................................................... 249
RAN2702 Reference data.......................................................... 249
Testing RAN2702: Parameter level logging of BTS user events......
250
RAN2571: Support of TLS 1.2................................................... 251
RAN2571 Benefits......................................................................251
RAN2571 Functional description................................................251

DN09203161

Issue: 01E

...................................5.............2.....13.....................1 7...........1............254 RAN2164 Benefits..........2................2 7.5..........2 7...............2................3 7..........6..................4 7..................................1.6....2...............2 7............4 7....................................2...................1......7 7.........................13................... 270 Verifying IP configuration............. 274 Verifying RAN2973: Enhanced IMSI-based call monitoring on mcRNC.2 7.2...... 276 Deactivating RAN2973: Enhanced IMSI-based call monitoring in IPA-RNC...5 Performance monitoring features.......2...............254 RAN2164 System impact.................257 RAN2973 Benefits..... 270 Activating RAN2973: Enhanced IMSI-based Monitoring on mcRNC.........................1 7...........................................1......2 7......... 264 Installing licenses for IPA-RNC......5 7.......................... 262 RAN2973 Reference data........2... 278 7..3 7........2..................1 7..... 274 Verifying RAN2973: Enhanced IMSI-based Monitoring.......4 7..5...........2................2 7.....5................6..258 RAN2973 Functional description.....2............. 271 Configuring Givaxi/givClient..1 7...2......... 269 Configuring site routers....................5....................... 252 RAN2571 Reference data..........3 6...................3 7.....258 RAN2973 System impact.............................2 7........................... 264 Configuring GIVAXI/givClient....254 RAN2164 Functional description......................................................267 Configuring NPEG(P) towards OMU.......5 7...................... 253     7 7................. 267 Configuring and verifying additional steps for IPA-RNC......8 Issue: 01E DN09203161 9 .....................278 Analyzing monitored data and troubleshooting.............276 Deactivating RAN2973: Enhanced IMSI-based Monitoring.........1...4 7.............................5.275 Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on mcRNC.....................2..........6..5............3 7....2..2.5...........2.6....2...........6....... 266 Authorizing Pre-Shared Key (PSK)...........4 7...........2......................................6 7.......1.1..................... 254 RAN2973: Enhanced IMSI Based Call Monitoring................................2..........................2.........................................271 Configuring IP connection at mcRNC......1...........3 7......254 RAN2164: Compensated CQI Measurement............7..................1........2..........5...................6.................................. 269 Configuring external monitoring tool (alternative to DHCP)........................5..2.......1 7..........................2...................................WCDMA 16 Feature Descriptions and Instructions 6.... 274 Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on IPA-RNC............... 273 Installing licenses for mcRNC...................2...............276 Deactivating RAN2973: Enhanced IMSI-based call monitoring in mcRNC....267 Configuring static IP route to external monitoring tool................... 265 Installing L3 Data Collector......2.....2..1.2............5.................6........ 264 Activating RAN2973: Enhanced IMSI-based Monitoring on IPARNC.............. 266 Configuring MSGMONPSK for data encryption........1 7.............2..................2.......1.....................5..2 7...7....................................1 7..............2.........6 7.............. 254 RAN2164 Reference data.2..........1..........................................2 7.........................................................5..........4 RAN2571 System impact...........2.....1 7......3 7..5....1................................2.......1..............1 7.........................5....5..........5..............1....................... 274 Installing L3 Data Collector............. 262 Activating and configuring RAN2973: Enhanced IMSI-based Monitoring..........2..............................

.........3......... 299 Activating RAN2646: External Alarm Input Support of mcRNC..................4. 312 RAN3057 Reference data.2.......2 8...........1 8..........278 Troubleshooting RAN2973: Enhanced IMSI-based Call Monitoring ...2 7....1 7....3.1 8..........................307 RAN3057 Benefits........294 RAN2304 System impact...............4 7.....................................................................316 RAN3005 Functional description...................................1............307 RAN3057 System impact.......................................... 314 RAN3005: Network Resiliency for mcRNC..........................4 7..WCDMA 16 Feature Descriptions and Instructions 7.................... 295 RAN2304 Reference data.....4......2 7.........1................8.......................... 286 RAN2862: Multi-RAB Dedicated Counter Set.................................... 306 RAN3057: mcRNC Signaling Capacity License.............................5 8.... 313 Testing RAN3057: mcRNC Signaling Capacity License..............5 7....................1 10 DN09203161 Issue: 01E ...............5.......................1 7.. 290 Verifying RAN2862: Multi-RAB Dedicated Counter Set.... 289 Activating RAN2862: Multi-RAB Dedicated Counter Set...5.........................................................4.284 RAN3104 System impact....4..........3............................................... 305 Deactivating RAN2646: External Alarm Input Support of mcRNC......1.........................3 7........7 7......298 RAN2646 System impact.......8....4.............2................2......2..........3...............3 7.....................................................................1 7...... 299 RAN2646 Reference data... 291 Deactivating RAN2862: Multi-RAB Dedicated Counter Set.................5 8...............3 8.... 284 RAN3104 Benefits......1 7.............6 7..5...................288 RAN2862 Functional description....................3 7........3.....3..................5...............1......................... 279 Configuring mcRNC to support Layer 3 routing towards Megamon......2. 285 Testing RAN3104: User Amount Monitoring..............................2 8........3 7..............................2......4 8...... 292 RAN2304: VSWR Monitoring........................................ 285 RAN3104 Reference data.9 8.. 288 RAN2862 Benefits.....6 8...................................................293 RAN2304 Functional description....................................298 RAN2646 Benefits..................................... 293 RAN2304 Benefits...................2 7..............284 RAN3104 Functional description..2 7......... 316 RAN3005 Benefits..2..................307 RAN3057 Functional description....................4 8. 298 RAN2646: External Alarm Input Support of mcRNC..............1 8....3 8..........................4.........3 8.298 RAN2646 Functional description..3...... 281 RAN3104: HSPA User Amount Monitoring.......2 8.............316 Differences between RAN3005: Network Resiliency for mcRNC and RAN2512: Network Resiliency for RNC2600 features..........4...................................4 7..................................................................5 Analyzing monitored data..289 RAN2862 System impact.............................4 7............. 318 7.2..............................5 7.......................................5 7........296     8 8....... 300 Verifying RAN2646: External Alarm Input Support of mcRNC...2..........................1........... 289 RAN2862 Reference data....................2 8..... 295 Testing RAN2304: VSWR Monitoring...................................5......3.....................................................1........1...........................1 8........................7 RNC solution features....

.....366 Commission PRNC to BkPRNC (mcRNC).2................3.. 360 Troubleshooting........... 347 RAN3005 Reference data.......WCDMA 16 Feature Descriptions and Instructions 8.......................3.3............................. 321 Planning management plane configuration....3......3............3.........................3.......2.....................3... 338 Comparison of prepared and unprepared redundancy switch.3................1 8.2..3.....10 8.... 319 Planning IP addressing solutions on RNC-cl................................2 8......2...3............6....3..2......3.......................3. 338 Redundancy conflict......................... 370 Configuring secure RNC-cl O&M interface.3.......................3....5......5 8..................................................................2...............................................................1 8...3 8....... 370 Configuring dedicated cluster interface.....................2...3.........................2................................2.....4 8..........3..3.............2...5.4 8....5 8...1 8..2.........353 Re-initialize hard disk to enlarge VG_System manually......................3...5.......2.............................2 8.............324 BkPRNC-related alarms in NetAct.............2 8.... 325 Backup Physical RNC System management...........374 Configuring RNCSRV at BkPRNC (mcRNC)...................323 Operating principles.........12 Issue: 01E Planning for Network Resiliency...... 367 Create BkPRNC object at PrPRNC (mcRNC)....3....7 8............................................3......2..2...........4 8.........9 8.............6.3...........3...............3................ 378 DN09203161 11 ...........369 Create RNCSRV at BkPRNC (mcRNC)...........365 Commission PRNC to StPRNC (mcRNC)....3.340 Network Resiliency related terms...1......... 320 Planning Iu-BC interface configuration for mcRNC BkPRNC...3.................................................3......................3............ 330 Redundancy switch..............1 8..........................373 Synchronization (mcRNC)......................2 8.3.................2...........................2......................6 8............ 348 Activating RAN3005: Network Resiliency for mcRNC.5 8...............................3.........3......3........................1 8...........5 8.............352 Enlarging QNDRBD....... 324 Auto-adaptation in mcRNC.........................2.........3..3 8... 354 Enlarging QNDRBD logical volume and corresponding DRBD file system....2..3....2........3. 333 Detecting redundancy switch necessity.............................. 333 Activity model...2.............323 Principles for NW operations with network resiliency..321 Planning Iu and Iur interfaces......3 8..........6...................8 8. 353 Modifying the VG_System LDAP configuration........1.3 8. 326 Interpreting of the system logs.2. 376 Configure network interfaces..................2..323 Planning transport network configuration ..3.3....5................4 8.............3..3.2........2.......2......6 8........3.5......5.......3............1.........6..................7 8...........3....3.2.5 8....3...............5..................3....3............7 8..................6...................................5.......362 Commission PrPRNC......346 RAN3005 System impact......2......11 8....3..5...................5..............4 8..3....2...................2 8................2 8. 319 Planning Iupc interface configuration...1.........3...........339 Network Resiliency operations in OMS Element Manager (OMS EM).. 324 Operating and Maintaining overview.......... 320 Planning Iub interface configuration ...........5......5............6 8............................................3.................343 Miscellaneous notes...5.......8 8.......3...2.5.........3...........2.................3 8.....4 8......................5.....................3 8....... 333 Use cases.............................2.....3 8..5...3..4 8.............. 378 MSC configuration for Core Network (mcRNC)..........5 8..3.............2..............

.............................386 Mapping IP address.............1......4 12 DN09203161 Issue: 01E ..1.........10............................ 393 Performing forced redundancy switch (mcRNC)............3...........................1................3...3..10....... 416 RAN3308 Reference data. 401 Performing IP auto adaptation.... 392 Performing controlled redundancy switch.......420 RAN3246 System impact..........................3.....416 RAN3308 System impact............. 408 Operating BPS on BkPRNC with the Activity Mode: Loaded or Active...416 RAN3308: Flexi RFM 3T6R 2100 (FRGX)......4 8.8......396 Performing forced redundancy switchback for mcRNC....1.7 8.........8.......3 9...1.................. 397 Network Resiliency operations in OMS.....3..............................4 9.........10.... 400 Configuring IP addresses in backup build for BkPRNC (mcRNC)..........2 9.............5 Configuring SGSN for Core Network in resilient network with mcRNC...6....1...3 8......... 404 Upgrading mcRNC SW builds and BPS on BkPRNC.6 8....8............1..........399 Performing redundancy switch using OMS EM..3 8......................2..398 Configuring OMS for network resiliency using Element Manager..... 389 Other instructions...8.........................4 9..... 391 Operating instructions....10........3........1........................ 383 Committing the IP address pre-configuration.....8..3.3 8......6.................................6 8.....404 Creating BPS fallback............1.....2...1 8................3............3.............................2.......9 8.......3.....3......3...1 8........1 8....14 8...... 400 Reconfiguring BTS for Network Resiliency...1.................1 9...7 8.............................3....1.........................3...414     9 9...........1 9..........................6.......................... 419 RAN3246: Flexi RRH 2T2R 850 120W (FRCG)..............8..........................................416 RAN3308 Functional description...3 9.1.......8.......3....................2 8.................399 Performing redundancy switchback using OMS EM.........................2 9.395 Performing controlled redundancy switchback.............. 418 RAN3158 Reference data...............8....418 RAN3158 Functional description...........8..3......1....3 BTS solution features................... 387 Verifying RAN3005: Network Resiliency for mcRNC. 391 Testing IP connectivity for mcRNC in resilient network...3...............3... 406 Activating new BPS on BkPRNC (mcRNC).1......3....2.......8..... 420 8...........3.............1.......3...1.........1...........................1 9............3....3.............1 8........ 417 RAN3158: Flexi RFM 6T6R 2100 (FRGU) .............2 9.....5 8..........1................3 9..16 8............WCDMA 16 Feature Descriptions and Instructions 8............3...........1.................10 8......................................................8....................380 Configuring Iur interface for mcRNC network resiliency........8..8..............8....................3...........1..8.......................10.....1............8.........................................................................................2 8.2 9............1....418 RAN3158 System impact...............................................4 8.8 8..............5.................. 419 RAN3246 Benefits................................ 416 RAN3308 Benefits.............3.............. 389 Deactivating RAN3005: Network Resiliency for mcRNC.........8 8...................2 8.. 398 Performing forced redundancy switch using OMS EM..417 RAN3158 Benefits... 401 mcRNC SW builds upgrade on BkPRNC........5........ 410 Deleting BPS fallback.........................1 9.............420 RAN3246 Functional description.....8...15 8...8.............5............13 8.....8....1..........5.3..8.............6...3......3..................3..

.........5......430 RAN3238 Functional description........................2 9...8......................425 RAN3237 Benefits. 429 RAN3238: WCDMA BTS Support for Harmonized MHA Family........6 9.................. 429 RAN2249 Reference data.............4 9..428 RAN2249 System impact........... 422 RAN3103 Reference data......... 425 RAN3237: HSUPA Scheduler Capacity Increase for FSMF..............................7..5.............. 428 RAN2249 Benefits.........................8..............423 RAN3324 Benefits. 426 Testing RAN3237: HSUPA Scheduler capacity increase for FSMF...........................................4 9.6...........424 RAN3324 System impact..........................4..................................................................6............................4 Issue: 01E RAN3246 Reference data....................7....1 9.............2 9...........5 9....................................................................2 9....................4.............................7.8....................................................................................2 9......................................................4 9.......................................2 9.............................................428 RAN2249 Functional description.........3 9........................................................... 430 RAN3238 Benefits................... 427 RAN2249: Support for Multi-Antenna RET Device.......................8............................3 9......................................... 424 RAN3324 Reference data.........................................426 RAN3237 Functional description.....................................1 9......4........4 9............................7.............8 9......................7 9............6.....................426 RAN3237 System impact...6........ 420 RAN3103: Flexi RRH 4T4R 1900 (FHFB).... 432 DN09203161 13 .4 9.....3 9......422 RAN3103 System impact................. 431 RAN3238 Reference data....... 426 RAN3237 Reference data...................1 9.........1 9...................... 422 RAN3324: Flexi RRH 4-pipe 1700/2100 160W.........421 RAN3103 Benefits.1 9....5.3.............................................4 9.........4...............431 RAN3238 System impact.5 9...421 RAN3103 Functional description..6........3 9.....5...........3 9..424 RAN3324 Functional description...........WCDMA 16 Feature Descriptions and Instructions 9.......

......... 36 Figure 4 HSUPA settings.................................... 261 DN09203161 Issue: 01E ............................... 248 Figure 29 Overview of RAN2973: IMSI-based Call Monitoring......................................................................................... 260 Figure 32 User Plane monitored data on Iu-CS interface..............................................214 Figure 24 Configuration management selection window...................................................................................... 97 Figure 5 Overview of the RAN2892: WCDMA-LTE Load Balancing feature in Nokia-based radio network............................................................................................................................................. 165 Figure 10 OSPF site solution...179 Figure 15 RFI and PIM testing in commissioning BTS settings................... 152 Figure 9 mcRNC SFP ports.................................................................................................. 234 Figure 26 Frequency modification workflow.............................................260 Figure 33 User Plane monitored data on Iub interface for PS and CS calls...................................................................................................261 Figure 34 Transport Plane monitored data on Iu-PS interface........... 261 Figure 35 Transport Plane monitored data on Iu-CS interface (RTP) (1 of 2) .......................................... 144 Figure 8 The IMEI collection and feature operation concept..................168 Figure 11 Add/Delete configurator model......134 Figure 6 Signaling of RIM UTRA SI procedure..........................................206 Figure 19 RF monitoring in BTSSM.................................................................. 209 Figure 21 RF-scanning measurement result for Carrier Rx...... 205 Figure 18 PIM desensitization visualization.210 Figure 22 PIM simulation test result..................................................................... 238 Figure 27 RUEM Log File Format......................................................................................... 35 Figure 2 Example of values of the M5005C59 counter obtained during Phase 2 of RAN3045 testing....................................................................................... 232 Figure 25 High level overview of the HIT base Fishing macro in mcRNC16................................................................................................................ 36 Figure 3 Example of values of the M5005C60 counter obtained during Phase 2 of RAN3045 testing..259 Figure 30 User Plane monitored data on Iu-PS interface....WCDMA 16 Feature Descriptions and Instructions List of Figures 14 Figure 1 Example of values of the M5005C58 counter obtained during Phase 2 of RAN3045 testing..........................................................208 Figure 20 RF-scanning measurement result for Raw Composite Rx or Composite Rx... 203 Figure 17 RF-scan visualization..................143 Figure 7 Signaling of RIM UTRA SI Procedure Error............................................... 179 Figure 14 Local IP address...................................................................................................................................................... 177 Figure 12 Send parameters options in BTSSM.......................................... 178 Figure 13 OSPF with BFD in BTSSM..............................................................................................202 Figure 16 RF Monitoring................ 260 Figure 31 End-to end IPv4 packet TCP/UDP/ICMP............................... 212 Figure 23 PIM desensitization test result..............................................................248 Figure 28 SIEM system GUI.......................................

......................................... 333 Figure 49 Normal redundancy switch....... 334 Figure 50 Forced redundancy switch................................ 341 Figure 56 Settings panel........................................... 261 Figure 38 Site solution deployment for IPA-RNC........................... 347 Figure 61 BkPRNC icon.............. 348 Figure 63 BkPRNC icon...........................................................................348 Figure 64 Network transport plan..............................................................................................338 Figure 54 RNC Resiliency menu for BkPRNC.............................................................................................316 Figure 47 Network resiliency transport network concept.... 337 Figure 53 System recovery from redundancy conflict........................................... 302 Figure 46 RNW Measurement report for RNC Capacity usage........336 Figure 52 Redundancy Switchback.................................... 343 Figure 58 PrPRNC icon.............. 398 DN09203161 15 .................................................................................................................. 318 Figure 48 Activity model................................................................................................................................................................................................................ 352 Figure 65 Example view of BkPRNC managed object visible in OMS GUI.......................................................................................................WCDMA 16 Feature Descriptions and Instructions Issue: 01E Figure 36 Transport Plane monitored data on Iu-CS interface (RTP) (2 of 2) ....335 Figure 51 Changing any RNCSRV to RNCSRV-Z at BkPRNC.......................................267 Figure 39 IP interfaces between units in the IPA-RNC......................................................................................................342 Figure 57 Show RNW Topology context menu.............................................................................................................................................................................................................................................. 294 Figure 42 Antenna line supervision in use parameter set........301 Figure 44 Connecting external alarm inputs.................272 Figure 41 Monitor VSWR dialog box................................................................................................................... 301 Figure 45 Connecting external alarm inputs............297 Figure 43 External alarm interface..................... 347 Figure 59 BkPRNC icon...........347 Figure 62 PrPRNC icon............................341 Figure 55 RNC Resiliency menu for PrPRNC.....................347 Figure 60 PrPRNC icon............................................................. 268 Figure 40 Site solution deployment for mcRNC........ 261 Figure 37 Transport Plane monitored data on Iub interface.

.......................................... 52 Table 19 Existing counters related to RAN3093............... 89 Table 30 Existing parameters related to RAN2518...... 101 Table 37 New PRFILE parameters introduced by RAN2869......101 Table 35 New parameters introduced by RAN2869.............................................. 38 Table 8 Existing counters related to RAN3043.......................................................................................................................................................................................................................... 44 Table 12 New counters introduced by RAN3218............................................................................. 90 Table 32 RAN2869 hardware and software requirements.. 45 Table 15 Parameters modified by RAN3218............................................ 38 Table 7 New counters introduced by RAN3043............... 53 Table 22 Existing parameters related to RAN3093...................................... 29 Table 3 Existing counters related to RAN3045................................................ 30 Table 5 RAN3045 Sales information................ 29 Table 2 New counters introduced by RAN3045......................................................................29 Table 4 New parameters introduced by RAN3045.... 87 Table 25 Alarms modified by RAN2518...... 101 Table 36 Existing parameters related to RAN2869....................................................................... 39 Table 11 RAN3218 hardware and software requirements..... 45 Table 16 RAN3218 sales information.............................................................................................................38 Table 9 New parameters introduced by RAN3043........ 89 Table 31 RAN2518 Sales information.......................... 30 Table 6 RAN3043 hardware and software requirements............................................................... 51 Table 18 New counters introduced by RAN3093........ 100 Table 34 Existing counters related to RAN2869...................................53 Table 20 New parameters introduced by RAN3093........................................... 100 Table 33 New counters introduced by RAN2869............................WCDMA 16 Feature Descriptions and Instructions List of Tables 16 Table 1 RAN3045 hardware and software requirements.......................................................................................................... 88 Table 27 Existing counters related to RAN2518.............................................. 89 Table 29 Parameters modified by RAN2518............................................................................45 Table 17 RAN3093 hardware and software requirements............................................................................................................ 101 Table 38 RAN2869 Sales information................................................................................. 53 Table 23 RAN3093 Sales information....................................44 Table 14 New parameters introduced by RAN3218................................................................................................................................ 87 Table 26 New counters introduced by RAN2518........ 101 DN09203161 Issue: 01E ........ 54 Table 24 RAN2518 hardware and software requirements............. 44 Table 13 Existing counters related to RAN3218........... 38 Table 10 RAN3043 Sales information.......................................88 Table 28 New parameters introduced by RAN2518....................................... 53 Table 21 Parameters modified by RAN3093..

.......114 Table 45 Existing counters related to RAN3235.............. 136 Table 58 Existing counters related to RAN2892....................................................................................136 Table 59 New parameters introduced by RAN2892................................ 119 Table 50 RAN2902 hardware and software requirements................................................ 114 Table 48 RAN3235 Sales information....... 115 Table 49 Available preamble signature combinations.... 170 Table 76 RAN3193 Sales information.......... 135 Table 57 New counters introduced by RAN2892... 107 Table 43 RAN3040 Sales information........ 174 DN09203161 17 .................................................................. 154 Table 70 RAN3082 Sales information..................WCDMA 16 Feature Descriptions and Instructions Issue: 01E Table 39 RAN3040 hardware and software requirements.............................................................................................. 107 Table 44 RAN3235 hardware and software requirements......... 114 Table 46 New parameters introduced by RAN3235....................... 146 Table 66 RAN3082 hardware and software requirements....................................................107 Table 41 New counters introduced by RAN3040...........122 Table 56 RAN2892 hardware and software requirements...................................... 107 Table 42 New parameters introduced by RAN3040............................................................................................................................................................................. 121 Table 53 New parameters introduced by RAN2902.................... 137 Table 61 RAN2892 sales information... 154 Table 71 RAN3112 hardware and software requirements.............................................................137 Table 62 RAN3086 hardware and software requirements............................ 154 Table 69 Parameters modified by RAN3082...............................166 Table 73 RAN3112 Sales information.................................................................................................... 122 Table 54 Parameters modified by RAN2902....................................... 146 Table 65 RAN3086 Sales information........................ 167 Table 74 RAN3193 hardware and software requirements..................... 136 Table 60 Parameters modified by RAN2892.... 121 Table 51 Existing alarms related to RAN2902............................................... 170 Table 77 RAN3242 hardware and software requirements.........................................................166 Table 72 New counters introduced by RAN3112.................................................................................... 146 Table 64 Existing parameters related to RAN3086...................................... 146 Table 63 New parameters introduced by RAN3086........... 107 Table 40 New faults introduced by RAN3040................................................................................................................................. 153 Table 67 New counters introduced by RAN3082................................................................................................... 122 Table 55 RAN2902 sales information........... 173 Table 78 RAN3242 Sales information........ 153 Table 68 New parameters introduced by RAN3082.... 114 Table 47 Parameters modified by RAN3235............................................................................................................... 169 Table 75 Existing parameters related to RAN3193.............................................121 Table 52 New counters introduced by RAN2902...........................................................................................................................

.... 255 Table 114 New counters introduced by RAN2164.................................... 199 Table 89 New parameters introduced by RAN3060..........................................................................252 Table 111 RAN2571 hardware and software requirements.................. 255 Table 115 RAN2164 Sales information..... 183 Table 84 RAN2367 Sales information.......................... 193 Table 88 RAN3060 hardware and software requirements........................................................................... 185 Table 86 RAN3247 Sales information......................................................................................................................................................................... 257 Table 116 RAN2973 Software requirements......................................WCDMA 16 Feature Descriptions and Instructions 18 Table 79 RAN2706 hardware and software requirements................................................................................................................................................................................................................................217 Table 94 RAN2872 Sales information................................................................................................................ 253 Table 113 RAN2164 hardware and software requirements..................................... 185 Table 87 Parameters used for activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networks feature.........................263 DN09203161 Issue: 01E ..................... 183 Table 82 Alarms................................................... 250 Table 110 Ciphers in priority.................................... 216 Table 92 Existing alarms related to RAN2872............................................. 241 Table 103 RAN2268 hardware and software requirements........................................ 245 Table 106 RAN3096 hardware and software requirements......................... 201 Table 91 RAN2872 hardware and software requirements....................................... 200 Table 90 RAN3060 Sales information...262 Table 117 External monitoring tool requirements................................................ 245 Table 105 RAN2268 Sales information......................................................................................................... 240 Table 101 Existing parameters related to RAN2991................................. 253 Table 112 RAN2571 Sales information....................... 247 Table 108 RAN2702 hardware and software requirements......................... 236 Table 100 RAN2991 hardware and software requirements.. 236 Table 99 RAN3150 Sales information......................................................................... 249 Table 109 RAN2702 Sales information.....................................217 Table 93 Existing OMS LDAP parameters related to RAN2872........... 230 Table 97 RAN3063 Sales information............................................................................................ 180 Table 80 RAN2706 Sales information............................................................... 246 Table 107 RAN3096 Sales information................... 183 Table 83 Parameters.......................................................... 240 Table 102 RAN2991 Sales information.. 230 Table 96 New parameters introduced by RAN3063...... 244 Table 104 New alarms introduced by RAN2268.......... 181 Table 81 RAN2367 hardware and software requirements................... 217 Table 95 RAN3063 hardware and software requirements. 183 Table 85 RAN3247 hardware and software requirements............................................................................................................ 230 Table 98 RAN3150 hardware and software requirements...................

................................................ 290 Table 130 RAN2304 hardware and software requirements............................................................................ 266 Table 121 Licenses for RAN2973: IMSI-based Monitoring........................................323 Table 151 Resilient operation exclusion principle ........ 322 Table 150 Supported IP mapping relationships.................................... 296 Table 132 RAN2304 Sales information........................ 285 Table 124 New counters introduced by RAN3104.................................................322 Table 149 Required number of SCTP associations in Iur compared to a basic situation without network resiliency........... 286 Table 127 RAN2862 hardware and software requirements...................................... 308 Table 139 Signaling capacity license. 313 Table 141 New alarms introduced by RAN3057...............................286 Table 126 RAN3104 Sales information.........................................................................................................330 Table 155 Use cases........................................................................................ 298 Table 134 RAN2646 hardware and software requirements................................... 329 Table 154 RNC Resiliency Logs.........................................................................................................................................................................317 Table 148 Required number of SCTP associations in Iu and Iu-PC compared to a basic situation without network resiliency ............................................................................................. 289 Table 128 New counters introduced by RAN2862................................................................................................................................................................302 Table 137 External Input .............. 286 Table 125 Existing counters related to RAN3104.............................................. 326 Table 152 Resiliency operations impact on BPS operations.................................... 314 Table 145 New parameters introduced by RAN3057........... 264 Table 119 RAN2973 Sales information................... 274 Table 122 RAN2973 symptoms and recovery actions..........................................................................................................................................................327 Table 153 Forbidden switch cases......................................................... 313 Table 143 New counters introduced by RAN3057............ 264 Table 120 Licenses for RAN2973: IMSI-based Monitoring.................................................. 314 Table 146 RAN3057 Sales information.....................WCDMA 16 Feature Descriptions and Instructions Issue: 01E Table 118 Maximum number of calls that be monitored based on RNC and monitoring configuration............................ 290 Table 129 RAN2862 Sales information................................................................................ 280 Table 123 RAN3104 hardware and software requirements.......... 295 Table 131 New counters introduced by RAN2304..................... 314 Table 147 Backup capacity step matrix.......................... 296 Table 133 External Input ................................................ 300 Table 136 External alarm pin mapping...................................................................................... 313 Table 144 New key performance indicators introduced by RAN3057..................... 310 Table 140 RAN3057 hardware and software requirements........................... 304 Table 138 SBHCA counters............333 DN09203161 19 .......... 299 Table 135 RAN2646 Sales information........................................................................ 313 Table 142 Existing alarms modified by RAN3057...............................................

..............................................................................................................................................362 Table 168 Error prompts ............................................................. 419 Table 175 RAN3158 Sales information..........................................431 Table 188 RAN3238 hardware and software requirements........................................................................................................................................................................................................ 348 Table 160 New alarms......................................................................401 Table 172 RAN3308 hardware and software requirements......................... 423 Table 179 RAN3103 Sales information... 430 Table 186 RAN2249 Sales information........................................................................................................ 362 Table 167 Error prompts .................................................................. 352 Table 166 Warning prompts ............. 378 Table 170 SGSN configuration ................................................................... 351 Table 165 RAN3005 Sales information................. 433 DN09203161 Issue: 01E ......................................................... 417 Table 173 RAN3308 Sales information...........WCDMA 16 Feature Descriptions and Instructions 20 Table 156 RNC Resiliency operations menu......................................................................... 427 Table 184 RAN2249 hardware and software requirements... 346 Table 159 RAN3005 hardware and software requirements...................................................... 429 Table 185 New parameters introduced by RAN2249...........................................................381 Table 171 BTS configuration values.................................... 351 Table 164 BTS Parameters.......................................................................................................................................................................... 417 Table 174 RAN3158 hardware and software requirements...................................................................... 423 Table 180 RAN3324 hardware and software requirements............ 426 Table 183 RAN3237 Sales information..................................................................................................................432 Table 190 Modified parameters...................................................................................................................................... 425 Table 182 RAN3237 hardware and software requirements.............. 425 Table 181 RAN3324 Sales information....................................................... 349 Table 163 Parameters modified by RAN3005. 349 Table 162 New parameters introduced by RAN3005.......432 Table 191 RAN3238 Sales information.............................................................................................................................. 421 Table 177 RAN3246 Sales information....................364 Table 169 MSC configuration .............................. 432 Table 189 New BTS faults introduced by RAN3238: WCDMA BTS Support for Harmonized MHA Family................................................ 430 Table 187 MHAs in harmonized MHA family................................................... 343 Table 158 Limitations.341 Table 157 Descriptions of feature-related terms ...................349 Table 161 Related existing alarms............................ 419 Table 176 RAN3246 hardware and software requirements................ 421 Table 178 RAN3103 hardware and software requirements..

RAN3005: Network Resiliency for mcRNC • • • Backup Physical RNC System management has been updated. Changes between issues 01B (2015-09-04. RAN3005: Network Resiliency for mcRNC • RAN3005 Functional description has been updated. WCDMA 16) New feature decsriptions: • Issue: 01E RNC solution features DN09203161 21 . WCDMA 16) RAN2706: Delta Configuration and Change Notification for BTS Transport • RAN2706 Functional description has been updated. Operating BPS on BkPRNC with the Activity Mode: Loaded or Active has been added. WCDMA 16) and 01E (2016-02-18. Changes between issues 01C (2015-10-30. RAN2973: Enhanced IMSI Based Call Monitoring • Verification intructions has been updated.    WCDMA 16 Feature Descriptions and Instructions Summary of changes Summary of changes Changes between issues 01D (2015-11-19. mcRNC SW builds upgrade on BkPRNC has been moved to Other instructions and updated. WCDMA 16) and 01C (2015-10-30.5 + INES PP337 has been added. WCDMA 16) NetAct release has been changed from NetAct 16 to NetAct 16.2 throughout the document. Other changes: RAN2892: WCDMA-LTE Load Balancing • A note has been added to RAN2892 Functional description and to Before you start in activation intructions. RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing • Requirements has been updated. Section WCDMA 16 Basic Support with NetAct 15. WCDMA 16) and 01D (2015-11-19.

RAN3218: Enhanced Cell Change from HSPA to 2G DN09203161 Issue: 01E . Verification instructions have been updated.    Summary of changes WCDMA 16 Feature Descriptions and Instructions – • RAN2646: External Alarm Input Support of mcRNC BTS solution features – RAN3246: Flexi RRH 2T2R 850 120W (FRCG) New feature activation instructions: • Radio resource management features – • RAN3235: Optimized Packet Handling at RNC RNC solution features – RAN2646: External Alarm Input Support of mcRNC New test cases: • Radio resource management features – – – – • Operability features – – – – • – RAN3104: HSPA User Amount Monitoring RAN2304: VSWR Monitoring RNC solution features – • RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing RAN2872: IPA-RNC Symptom Report RAN2991: Modification of WCDMA Frequency RAN2702: Parameter Level Logging of BTS User Events Performance monitoring features – • RAN3045: Activity Based UL Power Control for Rel99 DCH RAN2518: High Speed Cell_FACH Enhanced RAN3040: IRC Receiver RAN2902: RACH Capacity Increase RAN3057: mcRNC Signaling Capacity License BTS solution features – RAN3237: HSUPA Scheduler Capacity Increase for FSMF Removed features: • RAN3180: SW-support for WCDMA/LTE RF-sharing on C-RAN Other updates: • RAN3045: Activity Based UL Power Control for Rel99 DCH – – • 22 RAN3045 Functional description has been updated.

RAN3096: OMS HP Gen9 HW – • RAN3150 Functional description has been updated. Verification intructions have been updated. Transport requirements has been updated. RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing – • Introduction to the feature has been updated. RAN2991: Modification of WCDMA Frequency – • Verification intructions have been updated. RAN2991 Reference data has been updated. Activation intructions have been updated. Backup Physical RNC System management operations has been updated. RAN2706: Delta Configuration and Change Notification for BTS Transport – • RAN2518 Functional description has been updated. RAN2518: High Speed Cell_FACH Enhanced – • Summary of changes RAN3005 Functional description has been updated. RAN3005: Network Resiliency for mcRNC – – Issue: 01E Introduction to the feature has been updated. RAN3057: mcRNC Signaling Capacity License – • RAN3096 Functional description has been updated. RAN3235 Benefits has been updated. Interdependencies between features has been updated. Impact on system performance and capacity has been updated.    WCDMA 16 Feature Descriptions and Instructions – • – – – – – – – – – RAN3057 Functional description has been updated. RAN3235 Functional description has been updated. RAN2973: Enhanced IMSI Based Call Monitoring – • RAN2991 Benefits has been updated. DN09203161 23 . RAN2991 Functional description has been updated. RAN3235: Optimized Packet Handling at RNC – • Activation instructions have been updated. RAN3063: KPI Reporting based on Cell Type – • RAN2706 Functional description has been updated. RAN3150: mcRNC Event Based Symptom Data Collection – • RAN3060 Functional description has been updated.

Note that the subchapter Interdependencies between features lists only dependencies among Nokia RAN WCDMA features.5 + INES PP337. g 24 Note: WCDMA 16 is supported by NetAct 16. For INES support.2 and NetAct 15. see WCDMA 16 Basic Support with NetAct 15. DN09203161 Issue: 01E .5 + INES PP337.    Introduction to WCDMA 16 features WCDMA 16 Feature Descriptions and Instructions 1 Introduction to WCDMA 16 features This document provides feature descriptions and instructions for the WCDMA 16 release. If the feature has no specific hardware requirements. it means that only WCDMA System Module must be used.

INES support in PP337 does NOT include: • • WCDMA 16 level Performance Management (PM) metadata (new KPIs. Features supported by INES PP337: • Radio resource management and Telecom features – – – – – – – – – – Issue: 01E RAN3045: Activity Based UL Power Control for Rel99 DCH RAN3043: Advanced HSUPA Time Division Scheduling RAN3218: Enhanced Cell Change from HSPA to 2G 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 DN09203161 25 . and counters can be found in the WCDMA 16 operating documentation. measurements. Recommendations and workarounds: • Site Rehosting – • Performance Management - counters/KPIs – – • Rehosting should be done with the RU50 or RU50 EP1 level SW if BTS rehosting between RNCs is needed. No NetAct SW upgrade is needed. only OSS metadata and configurations for WCDMA 16 are updated to NetAct. and FM and CM Northbound Interfaces. or counters) to be used by NetAct Performance Manager and PM NBI. and counters – Complete documentation of the new or modified alarms. Compatibility for several NetAct applications. Reports with the new counters can be created with OMS tools. New counters introduced in WCDMA 16 are visible in OMS. parameters.5 + INES PP337 INES (Instant Network Element Support) with NetAct 15.    WCDMA 16 Feature Descriptions and Instructions WCDMA 16 Basic Support with NetAct 15. INES support in PP337 includes: • • WCDMA 16 level Fault Management (FM) and Configuration Management (CM) metadata to be used by NetAct Monitor and Configurator. The new PM data is visible via OMS applications. NetAct SW Manager.5 + INES PP337 2 WCDMA 16 Basic Support with NetAct 15. Documentation of WCDMA 16 alarms. Any advanced features like 3G Rehosting or WCDMA Frequency Modification. parameters.5 + PP337 provides basic NetAct management support and compatibility with WCDMA 16. for example.

2 required for NetAct management support. NetAct 16. – – – – • RNC solution features – – – • RAN2164: Compensated CQI Measurement RAN3104: HSPA User Amount Monitoring RAN2862: Multi-RAB Dedicated Counter Set RAN2304: VSWR 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: Flexi RRH 2T2R 850 120W (FRCG) RAN3103: Flexi RRH 4T4R 1900 (FHFB) RAN3324: Flexi RRH 4-pipe 1700/2100 160W RAN3237: HSUPA Scheduler Capacity Increase for FSMF RAN2249: Support for Multi-Antenna RET Device RAN3238: WCDMA BTS Support for Harmonized MHA Family Features not supported by INES PP337: • Operability features (NetAct 16.5 + INES PP337 – – • – RAN3112: mcRNC Integrated Ethernet Switching RAN3193: OSPF Authentication for Controller Operability features – – – – – – – – – • RAN3086: CSFB with RIM RAN3082: Device Detection Transmission and transport features – • WCDMA 16 Feature Descriptions and Instructions RAN2367: DNS Support for Certificate Examination RAN3247: Energy Efficiency Shut Down 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.    WCDMA 16 Basic Support with NetAct 15.2 required) – 26 RAN3242: Category for Obsolete Parameters DN09203161 Issue: 01E .2 Performance monitoring features g Note: PM counter management via OMS16.

    WCDMA 16 Feature Descriptions and Instructions – – – – Issue: 01E WCDMA 16 Basic Support with NetAct 15.5 + INES PP337 RAN2706: Delta Configuration and Change Notifications for BTS Transport RAN3063: KPI Reporting Based on Cell Type RAN2991: Modification of WCDMA Frequency RAN2702: Parameter Level Logging of BTS User Events DN09203161 27 .

1 RAN3045: Activity Based UL Power Control for Rel99 DCH Introduction to the feature With the RAN3045: Activity Based UL Power Control for Rel99 DCH feature. Thus. Impact on network and network element management tools This feature has no impact on network management or network element management tools.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 3 Radio resource management features 3.1.1 RAN3045 Benefits End-user benefits In case of HSPA cell with R99 UEs. end user benefits from improved HSPA throughput. its transmission power is lowered to minimum.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. 3. 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. for example.1. that means. more users can be accepted to the cell. BTS detects the uplink data channel inactivity and commands a UE to reduce transmitting power of the UL DPCCH control channel. signaling over uplink control channel DPCCH continues even if there is no UL data to be sent. when a UE is in a CELL_DCH state using R99 DCH. Thus. when UL data channel is inactive. 3. when a UE is in CELL_DCH state using R99 DCH in uplink (UL) and no data needs to be sent at the moment. 3. and cell HSPA data capacity increases. 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. This feature can work together with RAN3040: IRC Receiver and RAN1308: HSUPA Interference Cancellation Receiver features.2 RAN3045 Functional description In the current implementation. AMR calls. 28 DN09203161 Issue: 01E . the uplink interference from the R99 DCH UL control channel is reduced. With the RAN3045: Activity Based UL Power Control for Rel99 DCH feature. which also reduce UL interference. it does not have control channel gating. the UL interference from R99 DCH UEs is reduced.1. In case of a R99 cell. The feature significantly improves the cell capacity when the dominating traffic is in discontinuous or burst patterns.

 It also provides higher HSPA data cell throughput. Alarms There are no alarms related to this feature. Parameters Issue: 01E DN09203161 29 . 3.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Impact on system performance and capacity With this feature.2 Support not required Support not required Support not required Support not required This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. the cell capacity gain for PA3 channel is up to 5% for voice and PS64 services (assuming 50% activity). uplink interference from R99 DCH UE uplink control channel is reduced.1.4 RAN3045 Reference data Requirements Table 1 RAN3045 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 WBTS16 WBTS16 Under planning OMS NetAct MSC SGSN MGW UE Support not required NetAct 16. Measurements and counters Table 2 New counters introduced by RAN3045 Counter ID Counter name Measurement M5005C58 SUM OF R99 USERS HSPA in WBTS Extension M5005C59 SUM OF ABPC USERS HSPA in WBTS Extension M5005C60 R99 AND ABPC USERS DENOMINATOR HSPA in WBTS Extension Table 3 Existing counters related to RAN3045 Counter ID Counter name Measurement M1000C320÷M 1000C341 RECEIVED TOTAL WIDEBAND POWER CLASS 0÷RECEIVED TOTAL WIDEBAND POWER CLASS 21 Cell Resource 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. With this feature.

5 Activating RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to activate this feature. 30 DN09203161 Issue: 01E . The feature code for this feature is 5578.    Radio resource management features Table 4 WCDMA 16 Feature Descriptions and Instructions New parameters introduced by RAN3045 Full name Abbreviated name Activity based UL power control for Rel99 DCH enabled activityBasedULPowCtr lEnabled Managed object BTSSCW Commands There are no commands related to this feature. Before you start Restart of the RNC or the BTS is not required after the activation of this feature. Make sure you have the license file installed and the license state is 'Valid'. Sales information Table 5 RAN3045 Sales information BSW/ASW ASW SW component RAN License control in network element BTS LK 3. This procedure does not cause downtime and it can be activated at any time of the day.1. Make sure you have access to the following applications: • BTS Site Manager The RAN3045: Activity Based UL Power Control for Rel99 DCH feature is controlled by a license and requires a valid license file.

6 Proceed to the Send Parameters page by clicking Next. 5 Select the 'Activity based UL power control for Rel99 DCH' checkbox. then deselect TRS. select Commissioning. 3 In Commissioning type. 2 From the menu on the left-hand side.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. 8 Proceed to the Commissioning Report page by clicking Next. 7 Click Send parameters. select Reconfiguration.1. Before you start Make sure you have access to the following applications: • • Issue: 01E RNW Measurement Management RNW Measurement Presentation DN09203161 31 .    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open BTS Site Manager and establish a connection to the BTS. 3. 4 Proceed to the BTS Settings page by clicking Next. and then click Finish. Expected outcome The RAN3045: Activity Based UL Power Control for Rel99 DCH feature is activated.

 see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. Before you start Make sure you have an access to the following applications: 32 DN09203161 Issue: 01E . Expected outcome The value of the M5005C59 counter is a non-zero value between 0 and 36000. 3. 4 g Open the RNW Measurement Presentation application and check the value of the counter M5005C59. This can be checked from the TFCS IE in RADIO LINK SETUP message. This can be checked from the Radio Link Reconfiguration Procedure - no compressed mode configuration and activation in the procedure.1.7 Deactivating RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to deactivate this feature. There are less than or equal to 16 TFCS instances in the TFCS (UL) IE. 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. Note that even if the above conditions are fulfilled. No compressed mode is activated in the UE. For details on using the RNW Measurement Management application. 2 Start the measurement for the M5005C59 SUM OF ABPC USERS counter. if you start the measurement at 11:22.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the RNW Measurement Management application in the Application Launcher. the collected data is available in OMS at 12:10. the RAN3045: Activity Based UL Power Control for Rel99 DCH feature 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). and so on). Note: Measurement results are available in the application at the next full hour plus 10 minutes. For example. TFCI 0 is decoded with good quality. loop test. The UE is not set up for test purpose (test mode.

select Reconfiguration. and then click Finish. 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: • • Issue: 01E Operational Radio Access Network and Core Network. 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. select Commissioning. 4 Proceed to the BTS Settings page by clicking Next. do not use it for the feature as such in a live network.8 Testing RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose g Note: This is an example of verification. 3 In Commissioning type. 6 Proceed to the Send Parameters page by clicking Next. 5 Deselect the 'Activity based UL power control for Rel99 DCH' checkbox.1.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features BTS Site Manager • Procedure 1 Open BTS Site Manager and establish a connection to the BTS. Expected outcome The RAN3045: Activity Based UL Power Control for Rel99 DCH feature is deactivated. 8 Proceed to the Commissioning Report page by clicking Next. FSMr2 or FSMr3 platform DN09203161 33 . 2 From the menu on the left-hand side. 3. then deselect TRS. The configuration and parameter settings described are only examples and they can vary in different networks. 7 Click Send parameters.

8.    Radio resource management features • WCDMA 16 Feature Descriptions and Instructions HW configuration: FSME+FSME+2FRGP/2FRGT 20W (F222-x-146-1TX-4RX E Type). 2-10 cell phones are available for testing. Phase 1: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature deactivated Procedure 1 Check values of the counters M5005C58. and compare them with the values recorded in step 1. 3 Release the calls. and then mute the UEs to trigger DTX.1. Value of the M5005C60 counter is updated and different from 0. and M5005C60. and M5005C60 and record them.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. 34 DN09203161 Issue: 01E . The RAN3045: Activity Based UL Power Control for Rel99 DCH must be deactivated before you start phase 1 of testing. Expected outcome Values of the counters M5005C58 and M5005C59 are not updated. M5005C59. 4 Check values of the counters M5005C58. M5005C59. FSMF+FRGT (F111) Before you start Preconditions: • • • • 3. 2 Set up 2-10 AMR calls.

M5005C59.2 Radio resource management features Phase 2: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature activated Procedure 1 Check values of the counters M5005C58. and M5005C60 and record them.    WCDMA 16 Feature Descriptions and Instructions 3.8. 5 Check values of the counters M5005C58. and then mute the UEs to trigger DTX. Expected outcome Only with the RAN3045: Activity Based UL Power Control for Rel99 DCH (ABPC) feature activated. and compare them with the values recorded in step 1.1. M5005C59. 3 Set up 2-10 AMR calls. M5005C59. and M5005C60 are updated and different from 0. 4 Release the calls. For more information. Figure 1 Issue: 01E Example of values of the M5005C58 counter obtained during Phase 2 of RAN3045 testing DN09203161 35 . values of the counters M5005C58. and M5005C60. 2 Activate the RAN3045: Activity Based UL Power Control for Rel99 DCH feature. see Activating RAN3045: Activity Based UL Power Control for Rel99 DCH.

2 RAN3043: Advanced HSUPA Time Division Scheduling Introduction to the feature The RAN3043: Advanced HSUPA Time Division Scheduling feature introduces extension of 2 ms TTI one HARQ scheduling to higher bitrates (one HARQ peak bitrate of 320kbit/s - 1 Mbit/s.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Figure 2 Example of values of the M5005C59 counter obtained during Phase 2 of RAN3045 testing Figure 3 Example of values of the M5005C60 counter obtained during Phase 2 of RAN3045 testing 3.1 RAN3043 Benefits End-user benefits End users benefit from: 36 DN09203161 Issue: 01E . 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.

 when the users have bursty UL traffic. Impact on system performance and capacity With this feature. This means that the cell can have mixed set of UEs (with 2 ms TTI one HARQ with higher bitrate UEs. always all available HARQ processes are activated. Issue: 01E DN09203161 37 . g Note: This feature does not affect the scheduling done for the 10 ms UEs (that is.    WCDMA 16 Feature Descriptions and Instructions • • Radio resource management features Improved HSUPA throughput for 2 ms TTI UEs when there is 8-16 of such UEs in a cell (assuming continuous UL traffic). QoS parameters. for example. Gain is also possible with slightly higher number of users.2. 2 ms all HARQ UEs. One HARQ allocation with higher throughput is applied only for the scheduled MAC-d flows.2. The number of UEs may be bigger if the UEs generate bursty traffic. Better average RTT timings of the UEs. UEs with 10 ms TTI). Impact on network and network element management tools This feature has no impact on network management or network element management tools. 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. For 10 ms UEs. cell load. 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. this number may be slightly bigger when there are users with UL bursty traffic in a cell). and 10 ms all HARQ UEs) at any point in time. 2 ms one HARQ with lower bitrate UEs. this scheduling mechanism is extended to higher bitrates.3 RAN3043 System impact Interdependencies between features The RAN1470: HSUPA 2ms TTI feature is a prerequisite for using this feature. The 2 ms UEs are scheduled with higher bitrates based on various factors. In current implementation all available HARQ processes are allocated for those bitrates. 3. since 10 ms UEs do not support HARQ-specific scheduling. Thanks to this. Impact on interfaces This feature has no impact on interfaces. and so on. the cell capacity gain is expected to be up to 30% (assuming 16 UEs generating continuous UL traffic in PA3 channel conditions). With RAN3043: Advanced HSUPA Time Division Scheduling feature. the cell throughput is improved when there is about 8-16 users in a cell. 3.2 RAN3043 Functional description The RAN3043: Advanced HSUPA Time Division Scheduling feature introduces support for higher average bitrates (between 40 kbit/s and 120 kbit/s) for 2 ms TTI one HARQ scheduling. Also. radio conditions. number of UEs in a cell. The 2 ms TTI one HARQ scheduling was introduced in RU20 SW release with the RAN1470: HSUPA 2ms TTI feature.

Measurements and counters Table 7 New counters introduced by RAN3043 Counter ID Counter name Measurement M5000C477 HSUPA USERS WITH 2MS TTI DENOMINATOR 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 Existing counters related to RAN3043 Counter ID Counter name Measurement M5000C324 SUM OF HSUPA USERS WITH 2MS TTI HSPA in WBTS M5000C325 SUM OF HSUPA USERS WITH 10MS TTI HSPA in WBTS Key performance indicators There are no key performance indicators related to this feature. 3.2.2 Support not required Support not required Support not required Support not required This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Parameters Table 9 38 New parameters introduced by RAN3043 Full name Abbreviated name Advanced HSUPA Time Division Scheduling enabled advHSUPATimeDivSchedE nabled DN09203161 Managed object BTSSCW Issue: 01E .    Radio resource management features WCDMA 16 Feature Descriptions and Instructions This feature has no impact on baseband dimensioning.4 RAN3043 Reference data Requirements Table 6 RAN3043 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 WBTS16 WBTS16 Under planning OMS NetAct MSC SGSN MGW UE Support not required NetAct 16. Alarms There are no alarms related to this feature.

Issue: 01E DN09203161 39 . Sales information Table 10 RAN3043 Sales information BSW/ASW ASW SW component RAN License control in network element BTS LK 3. The license state must be set to ON. Make sure you have access to the following applications: • BTS Site Manager The RAN3043: Advanced HSUPA Time Division Scheduling feature is controlled by a license and requires a valid license file. Make sure you have the license file installed. The feature code for this feature is 5498.2. Before you start Restart of the RNC or the BTS is not required after the activation of this feature.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Commands There are no commands related to this feature.5 Activating RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to activate this feature. This procedure does not cause downtime and it can be activated at any time of the day.

2. 2 From the menu on the left-hand side. Expected outcome The RAN3043: Advanced HSUPA Time Division Scheduling feature is activated. 6 Proceed to the Send Parameters page by clicking Next. select Reconfiguration. and then click Next. Before you start Make sure you have access to the following applications: • • 40 RNW Measurement Management RNW Measurement Presentation DN09203161 Issue: 01E . 7 Click Send parameters. and then click Finish.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. 8 Proceed to the Commissioning Report page by clicking Next. select Commissioning.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the BTS Site Manager and establish a connection to the BTS. 3 In Commissioning type. 4 Proceed to the HSUPA Settings page by clicking Next. 3. 5 Select the 'Advanced HSUPA Time Division Scheduling' checkbox.

 traffic profile.2. 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.7 Deactivating RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to deactivate this feature. Make sure you have an access to the following applications: • Issue: 01E BTS Site Manager DN09203161 41 . 3 Open the RNW Measurement Presentation application and check the value of the M5000C479 and M5000C480 counters. Expected outcome The M5000C479 and M5000C480 counters' values are increased. cell load. see Viewing and modifying radio network measurement parameters in Managing and viewing RNC measurements. depending on the number of UEs with 2ms TTI. and so on. For details on checking the counter values in the RNW Measurement Presentation application. the counters' values are increased. For details on starting the measurements in the RNW Measurement Management application. Before you start Restart of the RNC or the BTS is not required after the deactivation of this feature.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the RNW Measurement Management application in the Application Launcher. As soon as the RAN3043 scheduling is applied. see Starting radio network measurements in Managing and viewing RNC measurements. 3. g Note: Advanced HSUPA Time Division Scheduling may be applied immediately or even after a few hours.

3. select Commissioning.3. 4 Proceed to the HSUPA Settings page by clicking Next. 3. 3 In Commissioning type. and then click Finish. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH before the GSM measurements. 5 Clear the 'Advanced HSUPA Time Division Scheduling' checkbox. 8 Proceed to the Commissioning Report page by clicking Next. and then click Next. select Reconfiguration.3 RAN3218: Enhanced Cell Change from HSPA to 2G Introduction to the feature The RAN3218: Enhanced Cell Change from HSPA to 2G feature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. Expected outcome The RAN3043: Advanced HSUPA Time Division Scheduling feature is deactivated. g Note: The RAN3218: Enhanced Cell Change from HSPA to 2G feature supports MultiRAB (AMR + HSPA) CM.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the BTS Site Manager and establish a connection to the BTS. 2 From the menu on the left-hand side. 6 Proceed to the Send Parameters page by clicking Next. 42 DN09203161 Issue: 01E . 7 Click Send parameters. Further information After deactivating the feature set the feature license state to OFF.1 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.

 This means that the GSM is measured with or without the compressed mode when the UE has HSPA/HSDPA configuration.5009 is not enabled. 3. RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Features RAN3218 and RAN1668 work under the same feature license. see RAN3082: Device Detection. The use of the feature can be allowed or denied for certain UEs with the Device Detection mechanism. This means decreased signaling and optimized resource consumption at the moment of measurements.3. When the feature is not activated. then the users are reconfigured to the DCH configuration before the GSM measurements. For more information on Device Detection mechanism.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 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.3 RAN3218 System impact Interdependencies between features The RAN3218: Enhanced Cell Change from HSPA to 2G feature requires the following features: • • g RAN1. 3. Impact on interfaces This feature impacts interfaces in the following way: • The CM measurement parameters for GSM are adapted to the HSPA/HSDPA configurations. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH before the GSM measurements.5009: WCDMA - GSM Inter-System Handover If RAN1. The DCH resource allocations are not needed before the measurements. Impact on system performance and capacity This feature impacts system performance and capacity in the following way: Issue: 01E DN09203161 43 . Impact on network and network element management tools This feature has no impact on network management or network element management tools.2 RAN3218 Functional description The RAN3218: Enhanced Cell Change from HSPA to 2G feature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. 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. Note: The features work under the same feature license.3. ISHO from WCDMA to GSM cannot be triggered.

2 Support not required Support not required Support not required Support not required This feature requires no new or additional hardware.4 RAN3218 Reference data Requirements Table 11 RAN3218 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 RNC16 mcRNC16 Support not required Support not required Support not required OMS NetAct MSC SGSN MGW UE WCDMA OMS16 NetAct 16.    Radio resource management features • WCDMA 16 Feature Descriptions and Instructions The procedure of the inter-system handover is performed from the HSPA/HSDPA without changing the configuration to the DCH which provides better performance at the moment of the GSM measurements. Alarms There are no alarms related to this feature.3. Measurements and counters Table 12 Counter ID Counter name Measurement 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 Inter System Hard Handover Table 13 Counter ID 44 New counters introduced by RAN3218 Existing counters related to RAN3218 Counter name Measurement 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 DN09203161 Issue: 01E . 3.

Issue: 01E DN09203161 45 .) Counter ID M1002C370 Counter name Measurement ALLO DURA FOR COM MODE DL TO INT SYS HHO IN SRNC Traffic Key performance indicators There are no key performance indicators related to this feature. Before you start After activating this feature.    WCDMA 16 Feature Descriptions and Instructions Table 13 Radio resource management features Existing counters related to RAN3218 (Cont. Sales information Table 16 RAN3218 sales information BSW/ASW SW component License control in network element ASW RAN RNC LK 3.5 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. Parameters Table 14 New parameters introduced by RAN3218 Full name Abbreviated name Transmission Gap Pattern Length for GSM measurements with HSPA/HSDPA Table 15 TGPLForHSGSMMeas Managed object RNHSPA Parameters modified by RAN3218 Full name Abbreviated name Managed object BTS support for HSPA CM BTSSupportForHSPACM WBTS 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 Commands There are no commands related to this feature. there is no need to restart RNC or BTS.3. Activation procedure does not require cell-locking and does not cause a down-time in the network.

for mcRNC: set license feature-mgmt code 0000004783 feature-adminstate on Ensure the GSM configuration exist in 3G. 46 DN09203161 Issue: 01E . To set the feature state to ON.747.5009: WCDMA - GSM Inter-System Handover g Note: Ensure that in the corresponding FIFILE this feature is enabled. for mcRNC those features do not need to be set separately. use the following command: for IPA-RNC: ZWOA:2. To set the feature state to ON. all FIFLE controlled ASW features are enabled by default. Consequently.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Activate the licence key and set feature state to ON for the following features: • RAN1. for mcRNC – – g • g Note: For mcRNC. Check feature status: ZWOS:2.A. RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Note: The RAN3218: Enhanced Cell Change from HSPA to 2G feature uses the same license as the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. use the following command: – – for IPA-RNC: ZW7M:FEA=4783:ON.747.

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. set the value of the BTSSupportForHSPACM parameter to HSDPA CM for IFHO. use the parameters of WDEV object (provided by the RAN3082: Device detection feature).3. use the TGPLForHSGSMMeas RNHSPA parameter.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. Further information To set the transmission gap pattern length. Before you start Make sure you have access to the following applications: • • Issue: 01E RNW Measurement Management RNW Measurement Presentation DN09203161 47 .    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open OMS Element Manager. To blacklist or whitelist UEs for this feature. use the MaxNumberUEHSPACmNCHO WCEL parameter. LTE and GSM or HSPA CM for IFHO. g Note: Activation of HSPA/HSDPA CM for GSM also activates HSPA/HSDPA CM for IFHO and LTE. LTE and GSM. 2 Go to Topology and expand the ROOT directory. c) On the Packet Scheduler tab. 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. 3.

2 Start the M1002 Traffic and M1010 Inter System Hard Handover measurements.3. Keep the service active for 15 minutes. 11:30.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the RNW Measurement Management application. and M1010C275 increased. 3 In an area with GSM coverage. M1010C274. data collection starts every quarter. For details on using the RNW Measurement Management 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 ISHO TO 2G WITH COMPRESSED MODE Expected outcome The values of counters M1002C695. g Note: In case of 15-minute interval. 4 Open the RNW Measurement Presentation application. Wait for the measurement interval to begin. 11:15. make a PS call mapped to HSPA or HSDPA services. For example 11:00. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.7 Deactivating RAN3218: Enhanced Cell Change from HSPA to 2G Purpose Follow this procedure to deactivate the RAN3218: Enhanced Cell Change from HSPA to 2G feature. 48 DN09203161 Issue: 01E . The purpose of this step is to trigger compressed mode measurements of the GSM layer and subsequent handover from WCDMA to GSM. 11:45. 3.

The enhancements are based on live-network experience. LTE and GSM and HSPA CM for IFHO. 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. radio resource utilization is more efficient. 3. Operator benefits Multi-Band Load Balancing enables the optimal usage of frequencies within a network according to operator preferences. layering during voice call setup. load balancing is made more sensitive. load balancing possibilities.1 RAN3093 Benefits End-user benefits The user is directed to the optimal frequency layer. and radio network performance is higher.4 RAN3093: Enhanced MBLB Introduction to the feature The RAN3093: Enhanced MBLB feature enhances load balancing. 3. Operator has greater control over utilization of the frequency layers.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open OMS Element Manager. 2 Go to Topology and expand the ROOT directory. set the BTSSupportForHSPACM parameter to a value other than HSDPA CM for IFHO. which improves the overall end-user experience. inactivity-triggered layering and mobility-triggered layering functionalities of the RAN2172: Multi-Band Load Balancing feature.4. It introduces new counters for monitoring SLHO Load State and HSPA Load State in correlation with MBLB decisions. 3. LTE and GSM. and services.4. In general.2 RAN3093 Functional description Enhanced load balancing Issue: 01E DN09203161 49 . UE capabilities. c) On the Packet Scheduler tab. network capabilities. With the RAN3093: Enhanced MBLB feature. operator strategies on how to use the frequency layers can be better supported.

 it is possible to perform Multi-Band Load Balancing (MBLB) layer change for voice calls in RAB setup phase. It is also possible to prevent useless load balancing actions when the HSPA load level is low.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Enhanced load balancing enables to use the RAN2172: Multi-Band Load Balancing feature just for balancing HSPA load between the layers (without any preferred layer definitions). it does not necessarily indicate congestion for CS AMR speech RAB. When enhanced inactivity-triggered layering is enabled and the radio conditions in the source cell are good enough. This is valid for both CS and PS services. the MBLB does not consider such a cell as possible target cell for the layer change. Enhanced inactivity-triggered layering without compressed mode measurements and the related thresholds for radio conditions are controlled by radio network parameters. 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 has reached a specified threshold. 50 DN09203161 Issue: 01E . the decision on the inactivity-triggered layer change is done without compressed mode measurements. 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. Enhanced inactivity-triggered layering without compressed mode measurements Inactivity-triggered layer change is currently being done by using compressed mode measurements followed by a hard handover. Enhanced layering during voice call setup . When Enhanced load balancing is enabled.Blind IFHO for the standalone SRB Currently. However. HSPA load difference between the source and target cells/layers exceeds a specified threshold. This feature is applicable to any MBLB function. The RAN3093: Enhanced MBLB feature provides an option to bypass the HSPA load state. Enhanced layering during voice call setup . Enhanced load balancing and the related load thresholds are controlled by radio network parameters.HSPA load state bypass Currently. Such MBLB functions are the MBLB Blind IFHO and the MBLB Mobility HO. as the HSPA load state can only be caused by the HSPA load. which utilizes the HSPA load state for decision making for the CS AMR speech RAB layering. This is possible for CS AMR speech RAB. MBLB sets the HSPA 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. Less signaling is needed for layering as the correct layer is already known before the RAB setup. Inactivity-triggered layer change can be prevented completely if the radio conditions in the source cell are bad. 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.

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. g Note: The features work under the same license. 3. or when the UE is detected to moving fast. and in case of multi-RABs. the need for mobility triggered layering is additionally checked after the first RAB setup is completed. 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. Impact on system performance and capacity This feature has no impact on system performance or capacity. Impact on interfaces Enhanced layering during voice call setup and Enhanced-inactivity triggered layering reduce NBAP and RRC signaling during layering procedures.4.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 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. after the AMR RAB setup is completed. 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. When enhanced inactivity-triggered layering is enabled in the state transition to CCH state.4 RAN3093 Reference data Requirements Table 17 Issue: 01E RAN3093 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 RNC16 mcRNC16 DN09203161 Flexi Multiradio BTS Support not required Flexi Multiradio 10 BTS Flexi Lite BTS Support not required Support not required 51 . 3. Impact on network and network element management tools This feature has no impact on network management or network element management tools. When Enhanced mobility-triggered layering is enabled.3 RAN3093 System impact Interdependencies between features This feature requires the RAN2172: Multi-Band Load Balancing feature.4. Enhanced inactivity-triggered layering in state transition to CCH state is enabled by an radio network parameter. Enhanced mobility triggered layering is enabled with an radio network parameter.

2 Support not required Support not required Support not required Support not required This feature requires no new or additional hardware. Alarms There are no alarms related to this feature.) OMS NetAct MSC SGSN MGW UE WCDMA OMS16 NetAct 16. Measurements and counters Table 18 Counter ID 52 New counters introduced by RAN3093 Counter name Measurement M1000C409 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 Cell Resource 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 Intra System Hard Handover M1008C310 MBLB BLIND HO ATTEMPTS WITH RSCP Intra System Hard Handover M1008C311 MBLB BLIND HO ATTEMPTS WITH LOAD Intra System Hard Handover M1008C312 MBLB BLIND HO ATTEMPTS USING HSPA LOAD BYPASS Intra System Hard Handover M1008C313 MBLB IFHO ATTEMPTS USING HSPA LOAD BYPASS Intra System Hard Handover M1008C314 BLOCKED MBLB IFHO DUE SLHO LOAD Intra System Hard Handover M1008C315 BLOCKED MBLB BLHO DUE SLHO LOAD Intra System Hard Handover M1008C316 BLOCKED MBLB IFHO DUE HSPA LOAD Intra System Hard Handover M1008C317 BLOCKED MBLB BLHO DUE HSPA LOAD Intra System Hard Handover M1008C318 SUCCESSFUL MBLB BLIND HO Intra System Hard Handover DN09203161 Issue: 01E .    Radio resource management features Table 17 WCDMA 16 Feature Descriptions and Instructions RAN3093 hardware and software requirements (Cont.

    WCDMA 16 Feature Descriptions and Instructions Table 19 Radio resource management features Existing counters related to RAN3093 Counter ID Counter name Measurement M1001C259 RRC CONN SETUP COMPLETED AFTER DIRECTED Service Level M1001C260 RRC CONN SETUP COMPLETED AND DIRECTED Service Level Key performance indicators There are no key performance indicators related to this feature. Sales information Issue: 01E DN09203161 53 . Parameters Table 20 New parameters introduced by RAN3093 Full name Abbreviated name Managed object MBLB Enhancements Enabled MBLBEnhancementsEnabl ed WCEL HSPA Load Threshold HSPALoadThreshold PFL HSPA Load Margin HSPALoadMargin PFL MBLB due to Inactivity RSCP Threshold MBLBInactivityRSCPThr FMCI Table 21 Parameters modified by RAN3093 Full name Abbreviated name Layer Selection Weight of Preferred Layer Table 22 LaySelWeightPrefLayer Managed object PFL Existing parameters related to RAN3093 Full name Abbreviated name Managed object Blind HO RSCP threshold BlindHORSCPThr HOPI MBLB in RAB Setup Enabled MBLBRABSetupEnabled WCEL MBLB in State Transition Enabled 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 RAB MBLBRABSetupMultiRAB WCEL Commands There are no commands related to this feature.

 there is no need to restart RNC or BTS. For more information. To set the feature state to ON. see Activating RAN2172: MultiBand Load Balancing.5 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 voice call setup - Blind IFHO in RRC setup Activating Enhanced layering during voice call 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 in state transition to CCH state Before you start g Note: After activating this feature.    Radio resource management features Table 23 WCDMA 16 Feature Descriptions and Instructions RAN3093 Sales information BSW/ASW ASW SW component RAN License control in network element RNC LK 3. Install the license key for the RAN2172: Multi-Band Load Balancing feature in the RNC and set the feature state to ON.4. The RAN3093: Enhanced MBLB feature uses the same license as the RAN2172: MultiBand Load Balancing feature. for mcRNC: set license feature-mgmt code 0000001938 feature-adminstate on The RAN2172: Multi-Band Load Balancing feature 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: • • • • 54 MBLBRABSetupEnabled MBLBStateTransEnabled MBLBInactivityEnabled MBLBMobilityEnabled DN09203161 Issue: 01E . use the following command: • • for IPA-RNC: ZW7M:FEA=1938:ON. Activating procedure does not require cell-locking.

 For more information. see Activating RAN2172: Multi-Band Load Balancing.1 Radio resource management features Activating Enhanced load balancing Purpose Follow this procedure to activate the Enhanced load balancing functionality of the RAN3093: Enhanced MBLB feature. Verify that the activation of Multi-Band Load Balancing has been successful for the selected phases.5. Before you start Activate the appropriate phases of the RAN2172: Multi-Band Load Balancing feature in the cells by setting the parameter value to Enabled 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.4. see Verifying RAN2172: Multi-Band Load Balancing.    WCDMA 16 Feature Descriptions and Instructions 3. Issue: 01E DN09203161 55 . 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. 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.

5. 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.4. 7 3. b) For each cell where the enhanced load balancing is activated. 4 Configure the PFL object: Sub-steps a) Right-click on the PFL object and select Edit parameters. set the value of the Enhanced load balancing parameter to True. 5 Expand the RNC object then expand the WCEL object. 3 Expand the RNC.Blind IFHO in RRC setup Purpose Follow this procedure to activate Enhanced layering during voice call setup - Blind IFHO in RRC setup functionality of the RAN3093: Enhanced MBLB feature. b) Assign the PFL identifier in WCEL from the PFLidentifier parameter. 56 DN09203161 Issue: 01E .    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the OMS Element Manager. Activating Enhanced layering during voice call setup . 6 Configure the WCEL object: Sub-steps a) Right-click on the WCEL object and select Edit parameters.2 Select Apply to save the changes. c) Under the MBLBEnhancementsEnabled parameter parent structure. 2 Go to Topology and expand the ROOT directory.

set the value of the Blind IFHO in RRC setup parameter to True. 2 Go to Topology and expand the ROOT directory. Issue: 01E DN09203161 57 . c) Under the MBLBEnhancementsEnabled parameter parent structure. b) Assign the PFL identifier in WCEL from the PFLidentifier parameter. Procedure 1 Open the OMS Element Manager.5.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Before you start Set the value of the MBLBRABSetupEnabled parameter to Enabled for Blind IFHO in RAB setup phase according to the RAN2172: Multi-Band Load Balancing feature activation instructions. Sub-steps a) Right-click on the WCEL object and select Edit parameters. 5 Select Apply to save the changes.3 PrefLayerDCHSDAMR PrefLayerHSPAAMR PrefLayerHSDPAAMR PrefLayerR99AMR Activating Enhanced layering during voice call setup . 4 Configure the WCEL object. Further information The following PFL parameters are used by this functionality: • • • • 3.Blind IFHO for CS voice call from CCH state 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. 3 Expand the RNC object then expand the WCEL object.4.

Sub-steps a) Right-click on the WCEL object and select Edit parameters. Activating MBLB HSPA load state bypass Purpose Follow this procedure to activate the MBLB HSPA load state bypass function of the RAN3093: Enhanced MBLB feature. 2 Go to Topology and expand the ROOT directory. Set the value of the MBLBRABSetupMultiRAB parameter to either Enabled when UE is in Cell_FACH/Cell_PCH state or Enabled when UE is in Cell_DCH/Cell_FACH/Cell_PCH. see Activating RAN2172: Multi-Band Load Balancing. b) Assign the PFL identifier in WCEL from the PFLidentifier parameter. 5 3.5. For more information.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Before you start In the cells. activate the Blind IFHO in RAB setup and 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. see Verifying RAN2172: Multi-Band Load Balancing. Verify if the activation of Multi-Band Load Balancing Blind IFHO in RAB setup and MBLB in RAB Setup for Multi RAB has been successful. c) Under the MBLBEnhancementsEnabled parameter parent structure. For more information. This function is possible for AMR CS speech call. 3 Expand the RNC object then expand the WCEL object. set the value of the Blind IFHO for CS voice call from CCH states parameter to True. 4 Configure the WCEL object. Procedure 1 Open the OMS Element Manager. 58 DN09203161 Issue: 01E .4.4 Select Apply to save the changes.

Issue: 01E DN09203161 59 . Sub-steps a) Right-click on the WCEL object and select Edit parameters. Procedure 1 Open the OMS Element Manager.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Before you start Enable and configure at least one of the RAN2172: Multi- Band Load Balancing feature's functions that utilize HSPA load state for decision making. 3 Expand the RNC object then expand the WCEL object. 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. 2 Go to Topology and expand the ROOT directory.5. b) Assign the PFL identifier in WCEL from the PFLidentifier parameter. Activating Enhanced inactivity-triggered layering without compressed mode measurements Purpose Follow this procedure to activate the Enhanced inactivity-triggered layering without compressed mode measurements functionality of the RAN3093: Enhanced MBLB feature. 5 3. set the value of the Bypass of HSPA load state in case of CS voice call parameter to True.5 Select Apply to save the changes. c) Under the MBLBEnhancementsEnabled parameter parent structure.4. 4 Configure the WCEL object. see Activating RAN2172: Multi-Band Load Balancing.

 see Activating RAN2172: Multi-Band Load Balancing. For each cell where the enhanced inactivity-triggered layering without compressed mode measurements is activated. Leave the default value or change it according to needs. Procedure 1 Open the OMS Element Manager. define the Intra-RNC inter-frequency neighbor cells that can be target cells for blind inactivity-triggered layering by configuring the BlindHOTargetCell ADJI parameter. the FMCI parameter set is defined by the NrtFmciIdentifier WCEL parameter. 4 Configure the FMCI object. Sub-steps a) Right-click on the FMCI object and select Edit parameters. 60 DN09203161 Issue: 01E . b) For each cell where the enhanced inactivity triggered layering without compressed mode measurements is activated. When the DL channel type is HS-DSCH. configure the MBLBInactivityRSCPThr parameter.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Before you start Activate the RAN2172: Multi-Band Load Balancing feature due to inactivity by setting the MBLBInactivityEnabled WCEL parameter value to Enabled. 3 Expand the RNC object then expand the FMCI object. 2 Go to Topology and expand the ROOT directory. For more information. Verify that the activation of Multi-Band Load Balancing due to inactivity has been successful. Define neighbor cells. the FMCI parameter set is defined by the HSDPAFmciIdentifierWCEL parameter. • • 5 When the DL channel type is DCH.

set the value of the BlindHOTargetCell ADJI parameter to Enabled. g Issue: 01E Note: Under one WCEL object it is possible to configure only one ADJI-neighbor per frequency. DN09203161 61 . b) Select ADJIs tab and click Create. Define the ADJI-neighbor by setting the value of the BlindHOTargetCell ADJI parameter to Enabled. d) Apply the changes.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Sub-steps a) In Topology Tree view. c) Under Handover Control tab. click the WCEL object and go to Adjacencies tab.

Leave the default value or change it according to needs. b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.6 Select Apply to save the changes. 8 3. see Verifying RAN2172: Multi-Band Load Balancing. Sub-steps a) Right-click on the WCEL object and select Edit parameters. b) For the Intra-RNC inter-frequency neighbor cells configured in the previous step. For more information.5.4. see Activating RAN2172: Multi-Band Load Balancing. Activating Enhanced mobility triggered layering Purpose Follow this procedure to activate the Enhanced mobility triggered layering functionality of the RAN3093: Enhanced MBLB feature. Before you start Activate the RAN2172: Multi-Band Load Balancing feature due to mobility by setting the value of the MBLBMobilityEnabled WCEL parameter to Enabled. 62 DN09203161 Issue: 01E . Verify that the activation of the RAN2172: Multi-Band Load Balancing feature due to mobility has been successful. For more information. 7 Configure the WCEL object. configure the BlindHORSCPThr HOPI parameter.    Radio resource management features 6 WCDMA 16 Feature Descriptions and Instructions Configure the HOPI object. set the value of the Enhanced inactivity triggered layering without CM parameter to True. Sub-steps a) Right-click on the HOPI object and select Edit parameters. c) Under the MBLBEnhancementsEnabled parameter parent structure.

 see Verifying RAN2172: Multi-Band Load Balancing. Verify that the activation of Multi-Band Load Balancing due to inactivity has been successful. 5 3. Before you start Activate the RAN2172: Multi-Band Load Balancing feature due to inactivity by setting the value of the MBLBInactivityEnabled WCEL parameter to Enabled.5. c) Under the MBLBEnhancementsEnabled parameter parent structure. b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the OMS Element Manager. For more information. set the value of the Enhanced mobility-triggered layering parameter to True. see Activating RAN2172: Multi-Band Load Balancing. 2 Go to Topology and expand the ROOT directory. 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. 4 Configure the WCEL object.7 Select Apply to save the changes.4. 3 Expand the RNC object then expand the WCEL object. Issue: 01E DN09203161 63 . For more information. Sub-steps a) Right-click on the WCEL object and select Edit parameters.

c) Under the MBLBEnhancementsEnabled parameter parent structure. set the value of the Enhanced inactivity triggered layering to CCH states parameter to True. see Activating RAN2172: Multi-Band Load Balancing. For more information.1 Verifying Enhanced load balancing Purpose Follow this procedure to verify if the Enhanced load balancing functionality of the RAN3093: Enhanced MBLB feature works properly in the network. 3 Expand the RNC object then expand the WCEL object. b) Assign the PFL identifier in WCEL from the PFLidentifier parameter. 2 Go to Topology and expand the ROOT directory. In the PFL objects attached to the source cell. 5 Select Apply to save the changes. 3. g Note: Enhanced load balancing functionality can be used in all MBLB phases but it is easier to verify it in RAB setup phase.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the OMS Element Manager.4. Sub-steps a) Right-click on the WCEL object and select Edit parameters. 4 Configure the WCEL object. set the values of the following weighting factors to 0: • • • 64 LaySelWeightBand LaySelWeightPrefLayer LaySelWeightRSCP DN09203161 Issue: 01E .6.4.6 Verifying RAN3093: Enhanced MBLB 3. Before you start Activate MBLB in the RAB setup phase by setting the value of the MBLBRABSetupEnabledWCEL parameter to Enabled in the source cell.

For details on using the RNW Measurement Management application. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. the UE is handed over to a less-loaded cell in the RAB setup phase DN09203161 65 . RSCP and preferred layer definitions together in the layer selection but it is easier to verify the Enhanced load balancing functionality when band capability. make several PS NRT data calls with 5-second intervals . band capability. 3 Wait until the measurement interval starts.    WCDMA 16 Feature Descriptions and Instructions g Radio resource management features Note: There is no restriction to use HSPA load. When the threshold is exceeded. RSCP and preferred layer definitions are not used in the layer selection. 5 Keep making PS NRT data calls until HSPA load level in the source cell exceeds the threshold determined by the HSPALoadThreshold parameter in the PFL object attached to the source cell. Make sure you have access to the following applications: • • RNW Measurement Management RNW Measurement Presentation Procedure 1 Open the RNW Measurement Management application. 4 In the cell where the enhanced load balancing functionality is activated (source cell). 2 Start the M1000 CELL RESOURCE and M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15-minute interval. : The HSPA load level can be verified from the counters: • • • g Issue: 01E 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.

Before you start Make sure you have access to the following applications: • • 66 RNW Measurement Management RNW Measurement Presentation DN09203161 Issue: 01E . 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.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.6. g Note: Counters M1008C311 and M1008C318 are not updated until the HSPA load level in the source cell exceeds the threshold determined by the HSPALoadThreshold PFL parameter.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 6 Open the RNW Measurement Presentation application. 3. 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.2 Verifying Enhanced layering during voice call setup .4. Expected outcome Values of the counters M1008C311 and M1008C318 have been incremented. see Using RNW Measurement Presentation in Managing and viewing RNC measurements.

7 Monitor if MBLB moves UE to the target cell by Blind IFHO in RRC setup phase. 4 Configure the RAN2172: Multi-Band Load Balancing feature 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.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the RNW Measurement Management application. 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. The M1008C309: MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA counter indicates the Blind IFHO in RRC setup. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 2 Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. For details on using the RNW Measurement Presentation application. For details on using the RNW Measurement Management application. For more information. 6 Open the RNW Measurement Presentation application. see Activating RAN2172: Multi-Band Load Balancing. 5 Make an AMR CS speech RAB call in the source cell. 3 Wait until the measurement interval starts. 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. Further information This functionality uses the following PFL parameters: • • • Issue: 01E PrefLayerDCHSDAMR PrefLayerHSPAAMR PrefLayerHSDPAAMR DN09203161 67 . see Using RNW Measurement Presentation in Managing and viewing RNC measurements.

2 Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval.4.6. 3 Wait until the measurement interval starts. Make sure you have access to the following applications: • • RNW Measurement Management RNW Measurement Presentation Procedure 1 Open the RNW Measurement Management application.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. For details on using the RNW Measurement Management application. For more information. Before you start Ensure the Blind IFHO for CS voice call from CCH state function of the RAN3093: Enhanced MBLB feature is activated and the Blind IFHO in RRC setup function is deactivated.    Radio resource management features • 3.3 WCDMA 16 Feature Descriptions and Instructions PrefLayerR99AMR Verifying Enhanced layering during voice call setup . 4 Configure the Blind IFHO in RAB setup and MBLB in RAB Setup for Multi RAB functionalities of the RAN2172: Multi-Band Load Balancing feature 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. see Activating RAN2172: Multi-Band Load Balancing 68 DN09203161 Issue: 01E . see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.

4 Verifying the MBLB HSPA load state bypass Purpose Follow this procedure to verify if the MBLB HSPA load state bypass function of the RAN3093: Enhanced MBLB feature works properly in the network. 9 Monitor if when the UE is transferred to Cell_DCH state.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 5 Make a PS NRT data call. The M1008C309: MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA counter indicates the Blind IFHO for CS voice call from CCH state.6. 3. However. Mobility IFHO functionality of the RAN2172: Multi-Band Load Balancing feature can be used. 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. the UE is also moved to the correct layer based on its capabilities (service is always AMR in this case). 6 Make the PS NRT RAB to stop all data transfer and wait until the inactivity is detected for the UE and the UE is transferred to Cell_FACH/Cell_PCH. reporting the RSCP value is optional for the UE and it is possbile that UE does not report it. see the Activating RAN2172: Multi-Band Load Balancing feature activation.4. This function is possible for AMR CS speech call. Issue: 01E DN09203161 69 . 7 Make an AMR CS speech call. Alternatively. see Using RNW Measurement Presentation in Managing and viewing RNC measurements. the RSCP value reported by a UE is needed. g Note: To verify the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality. Before you start Ensure the MBLB HSPA load state bypass functionality 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. 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. For details on using the RNW Measurement Presentation application. 8 Open the RNW Measurement Presentation application. For more information.

3 Open the RNW Measurement Management application. configure the preferred layer definitions (PFL-Preferred Frequency Layer parameters) so that the target cell has higher preference score than the source cell. For details on using the RNW Measurement Management application. set the maximum number of HSDPA users to a desired value in the target cell using the MaxNumberHSDPAUsers WCEL parameter. see the Handover Control Functional Area Description. Then. 2 Arrange HSPA load state in the MBLB target cell. allocate PS NRT HSDPA calls so that the maximum level is reached. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. For more information about the MBLB preference score and preferred layer definitions. 4 Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. For more information about HSPA load state.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Make sure you have access to the following applications: • • RNW Measurement Management RNW Measurement Presentation Procedure 1 With the RAN2172: Multi-Band Load Balancing feature. 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. see the Handover Control Functional Area Description. 70 DN09203161 Issue: 01E .

 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 BLIND HO ATTEMPTS USING HSPA LOAD BYPASS M1008C313: MBLB IFHO ATTEMPTS USING HSPA LOAD BYPASS MBLB layer change attempts using the HSPA load state bypass are visible also in the following MBLB counters: • • • • • • Issue: 01E 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 M1008C308: MBLB BLIND HO ATTEMPTS WITH UE BAND CAPA M1008C309: MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA DN09203161 71 . The M1008C312: MBLB BLIND HO ATTEMPTS USING HSPA LOAD BYPASS counter indicates the HSPA load state bypass. 7 Open the RNW Measurement Presentation application. Unexpected outcome The AMR CS speech call is not moved to the target cell by the MBLB but the establishment is done in the original source cell. Use MBLB Blind IFHO for triggering the layer change. Expected outcome The AMR CS speech call is moved to the target cell by the MBLB and the value counters M1008C312 increased. 8 Monitor if MBLB moves UE to the target cell irrespective of the HSPA load state. 6 Make an AMR CS speech call in the source cell. For details on using the RNW Measurement Presentation application. Further information: The following counters indicate the blocking due to the MBLB HSPA load state. see Using RNW Measurement Presentation in Managing and viewing RNC measurements.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 5 Wait until the measurement interval starts.

For details on using the RNW Measurement Management application. In this kind of failure scenario.5 M1002C0 Network element name: 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 measurements functionality of the RAN3093: Enhanced MBLB feature works properly in the network.    Radio resource management features • • WCDMA 16 Feature Descriptions and Instructions 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 the HSPA load state bypass allows AMR speech call setup attempt even if the cell is in HSPA load state: • • M1002C339 Network element name: 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.4. 2 Start the M1006 RRC SIGNALLING and M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15-minute interval. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.6. Before you start Make sure you have access to the following applications: • • RNW Measurement Management RNW Measurement Presentation Procedure 1 Open the RNW Measurement Management application. 72 DN09203161 Issue: 01E . the attempt is seen both in the target cell and the source cell: • • 3. the re-attempt in the original source cell is made.

    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 3 Wait until the measurement interval starts. 4 Make a PS NRT data call in the cell where the Enhanced inactivity triggered layering without compressed mode measurements functionality is activated. 8 Open the RNW Measurement Presentation application. 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. 7 Check the value of Enhanced inactivity-triggered layering to CCH states parameter in the MBLBEnhancementsEnabled parameter parent structure. 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 BLIND HO ATTEMPTS WITH SERVICE AND UE 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 Issue: 01E DN09203161 73 . 6 When the PS NRT RAB becomes inactive and if the call is made in the cell where the activation parameters are enabled. 5 Make the PS NRT RAB to stop all data transfer and wait until the inactivity is detected for the UE. the UE is transferred to the correct layer based on its capabilities and allocated RAB combination.

 the M1006C323 counter value increases. the M1006C325 counter value increases. M1008C309.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions The proper working of the Enhanced inactivity-triggered layering without compressed mode measurements functionality of the RAN3093 Enhanced MBLB feature is indicated by one of the following outcomes: • • The RRC connection is transferred to Cell_FACH/PCH or URA_PCH state in the current layer if the CPICH RSCP measurement result of the source cell is below the threshold defined with the MBLBInactivityRSCPThr FMCI parameter. M1008C297. – – If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states parameter is set to False. – – • If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states parameter is set to False. The values of the above listed counters have not been incremented. M1008C310. one of the counter values: M1008C308. one of the counter values: M1008C296. 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 RRC connection is transferred from the current layer to the frequency layer which is defined as the preferred one for the UE if the CPICH RSCP measurement result of the source cell is equal to or above the threshold 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 to True. M1008C298. The RRC connection is transferred from 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. one of the following counter values are incremented: • • • • • g 74 M1008C301: FAILED MBLB IFHO DUE TO UTRAN M1008C302: FAILED MBLB IFHO DUE TO UE NACK M1008C303: FAILED MBLB IFHO DUE TO UE LOST M1006C324: FAILED LAYER CHANGES IN DCH TO PCH/FACH WITH CM M1006C326: FAILED LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM Note: MBLB blind handover has attempt and success counters but no failure counters. DN09203161 Issue: 01E . If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states parameter is set to True. In this case. 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). Unexpected outcome The inter-frequency handover attempt or state transition to the preferred layer has failed.

4.    WCDMA 16 Feature Descriptions and Instructions 3. 7 Check if the values of the following counters after the measurement data have been collected: • Issue: 01E M1008C296: MBLB IFHO ATTEMPTS WITH UE BAND CAPA DN09203161 75 . 2 Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. 5 The UE is handed over to the correct layer immediately after the AMR RAB setup. 3 Wait until the measurement interval starts. 6 Open the RNW Measurement Presentation application. 4 Make an AMR call in the cell where the enhanced mobility-triggered layering functionality is activated. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. Make sure you have access to the following applications: • • RNW Measurement Management RNW Measurement Presentation Procedure 1 Open the RNW Measurement Management application. g Note: The Enhanced mobility-triggered layering is not done if Blind IFHO (layering) has been already done in RAB Setup Phase.6 Radio resource management features Verifying Enhanced mobility-triggered layering Purpose Follow this procedure to verify if the Enhanced mobility-triggered layering functionality of the RAN3093: Enhanced MBLB feature works properly in the network. 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. Before you start Set the value of the MBLBRABSetupEnabled WCEL parameter to Disabled. For details on using the RNW Measurement Management application.6.

The Enhanced mobility-triggered layering functionality of the RAN3093: Enhanced MBLB feature has been activated successfully. Unexpected outcome The inter-frequency handover attempt has failed. see Using RNW Measurement Presentation in Managing and viewing RNC measurements. Before you start Make sure you have access to the following applications: • • 76 RNW Measurement Management RNW Measurement Presentation DN09203161 Issue: 01E .6.4.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. Expected outcome One of the counter values: M1008C296. 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 values of the following counters are incremented: • • • 3. M1008C297.    Radio resource management features • • • • WCDMA 16 Feature Descriptions and Instructions 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 Presentation application. M1008C298.

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. For details on using the RNW Measurement Management application. 4 Make a PS NRT data call in the cell where the enhanced inactivity triggered layering in state transition to CCH state functionality is activated. the UE is transferred to the CCH state in the correct layer based on its capabilities and allocated RAB combination. see Using RNW Measurement Presentation in Managing and viewing RNC measurements. 6 Check the value of Enhanced inactivity-triggered layering without CM parameter in the MBLBEnhancementsEnabled parameter parent structure. 7 Open the RNW Measurement Presentation application. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 5 Make the PS NRT RAB to stop all data transfer and wait until the inactivity is detected for the UE. 3 Wait until the measurement interval starts. When the PS NRT RAB becomes inactive and the call is made in the cell where the activation parameters are enabled. 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. 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 For details on using the RNW Measurement Presentation application. 2 Start the M1006 RRC SIGNALLING measurement with 15-minute interval.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the RNW Measurement Management application. which is indicated by one of the following outcomes: Issue: 01E DN09203161 77 .

 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 equal to or above the threshold defined by the MBLBInactivityRSCPThr FCMI parameter and below the threshold defined by the BlindHORSCPThr HOPI parameter. 3. the RRC connection is transferred to Cell_FACH/PCH or URA_PCH state in the current layer and no MBLB counters have been incremented.7. In this case. 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.    Radio resource management features • • • WCDMA 16 Feature Descriptions and Instructions If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to False. 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 M1006C324 increases.4.7 Deactivating RAN3093: Enhanced MBLB 3. the value of counter M1006C325 increases. 78 DN09203161 Issue: 01E . the value of counter M1006C323 increases. 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. 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.4. the value of counter M1006C324 increases.1 Deactivating Enhanced load balancing Purpose Follow this procedure to deactivate the Enhanced load balancing functionality of the RAN3093 Enhanced MBLB feature. the value of counter M1006C323 increases. Unexpected outcome The state transition to preferred layer has failed. 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.

    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the OMS Element Manager. Deactivating Enhanced layering during voice call setup . Sub-steps a) Right-click on the WCEL object and select Edit parameters. 5 3. 2 Go to Topology and expand the ROOT directory.Blind IFHO in RRC setup Purpose Follow this procedure to deactivate the Enhanced layering during voice call setup - Blind IFHO in RRC setup functionality of the RAN3093 Enhanced MBLB feature.4. set the value of the Enhanced load balancing parameter to False.2 Select Apply to save the changes. Issue: 01E DN09203161 79 . b) Under the MBLBEnhancementsEnabled parameter parent structure.7. 3 Expand the RNC object then expand the WCEL object. 4 Configure the WCEL object.

    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the OMS Element Manager. 3 Expand the RNC object then expand the WCEL object. b) Under the MBLBEnhancementsEnabled parameter parent structure. Deactivating Enhanced layering during voice call setup .3 Select Apply to save the changes. Sub-steps a) Right-click on the WCEL object and select Edit parameters. 5 3.Blind IFHO for CS voice call from CCH state Purpose Follow this procedure to deactivate the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality of the RAN3093: Enhanced MBLB feature. 4 Configure the WCEL object. 80 DN09203161 Issue: 01E .4. set the value of the Blind IFHO in RRC setup parameter to False.7. 2 Go to Topology and expand the ROOT directory.

b) Under the MBLBEnhancementsEnabled parameter parent structure. set the value of the Blind IFHO for CS voice call from CCH states parameter to False.4. 3 Expand the RNC object then expand the WCEL object. Sub-steps a) Right-click on the WCEL object and select Edit parameters.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the OMS Element Manager.4 Select Apply to save the changes.7. Issue: 01E DN09203161 81 . 4 Configure the WCEL object. 2 Go to Topology and expand the ROOT directory. Deactivating the MBLB HSPA load state bypass Purpose Follow this procedure to deactivate the MBLB HSPA load state bypass functionality of the RAN3093: Enhanced MBLB feature. 5 3.

Deactivating Enhanced inactivity triggered layering without compressed mode measurements Purpose Follow this procedure to deactivate the Enhanced inactivity triggered layering without compressed mode measurements functionality of the RAN3093: Enhanced MBLB feature. 2 Go to Topology and expand the ROOT directory.4. 5 3. Sub-steps a) Right-click on the WCEL object and select Edit parameters.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the OMS Element Manager.7.5 Select Apply to save the changes. 3 Expand the RNC object then expand the WCEL object. set the value of the Bypass of HSPA load state in case of CS voice call parameter to False. 4 Configure the WCEL object. b) Under the MBLBEnhancementsEnabled parameter parent structure. 82 DN09203161 Issue: 01E .

2 Go to Topology and expand the ROOT directory. under the MBLBEnhancementsEnabled parameter parent structure. Issue: 01E DN09203161 83 .4. 3 Expand the RNC object then expand the WCEL object.6 Select Apply to save the changes. Sub-steps a) Right-click on the WCEL object and select Edit parameters. 4 Configure the WCEL object. Deactivating Enhanced mobility triggered layering Purpose Follow this procedure to deactivate the Enhanced mobility triggered layering functionality of the RAN3093: Enhanced MBLB feature.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the OMS Element Manager. b) For each cell where the Enhanced inactivity triggered layering without compressed mode measurements is deactivated.7. 5 3. set the value of the Enhanced inactivity triggered layering without CM parameter to False.

7. under the MBLBEnhancementsEnabled parameter parent structure. 5 3.4. Deactivating Enhanced inactivity triggered layering in state transition to CCH state Purpose Follow this procedure to deactivate the Enhanced inactivity triggered layering in state transition to CCH state functionality of the RAN3093 Enhanced MBLB feature. set the value of the Enhanced mobility triggered layering parameter to False. 3 Expand the RNC object then expand the WCEL object.7 Select Apply to save the changes. 2 Go to Topology and expand the ROOT directory. 4 Configure the WCEL object. Sub-steps a) Right-click on the WCEL object and select Edit parameters.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the OMS Element Manager. 84 DN09203161 Issue: 01E . b) For each cell where the Enhanced mobility triggered layering is deactivated.

3. b) For each cell where the Enhanced inactivity triggered layering in state transition to CCH state is deactivated. under the MBLBEnhancementsEnabled parameter parent structure. Operator benefits With this feature.5. Sub-steps a) Right-click on the WCEL object and select Edit parameters.1 RAN2518 Benefits End-user benefits More users can transfer small and medium-sized packets in a more efficient manner. 5 Select Apply to save the changes. Issue: 01E DN09203161 85 . cell capacity and throughput is increased by transferring a bigger share of small and medium-sized data bursts using the RAN1913: High Speed Cell_FACH feature. set the value of the Enhanced inactivity triggered layering to CCH states parameter to False. 4 Configure the WCEL object. 3 Expand the RNC object then expand the WCEL object. 3. which means that the maximum number of common enhanced dedicated transport channel (E-DCH) resources per cell is increased from 10 to 32 users.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open the OMS Element Manager.5 RAN2518: High Speed Cell_FACH Enhanced Introduction to the feature The RAN2518: High Speed Cell_FACH Enhanced feature increases the share of air interface capacity for the RAN1913: High Speed Cell_FACH feature. where High Speed Cell_FACH is the most efficient. 2 Go to Topology and expand the ROOT directory.

 the RAN1913: High Speed Cell_FACH feature allows to configure the maximum number of simultaneous common E-DCH users up to 10 per cell. the common E-DCH is privileged. Rel8+ UEs in the uplink use the common E-DCH to transfer the application packets to the network. for HS Cell FACH uplink usage. however in an inactive state there can be more than 32 HS-RACH users in the cell. whereas large application data bursts and uploads need to be transferred through the dedicated E-DCH (HSUPA). With the RAN2518: High Speed Cell_FACH Enhanced feature the maximum is increased from four to eight HSUPA Resource Steps. the Common E-DCH System Information IE carries the configuration for up to 32 instances of the Common E-DCH Resource Combination Information IE.2 RAN2518 Functional description The RAN2518: High Speed Cell_FACH Enhanced feature increases the number of uplink common channel resources for smartphone UEs for enhanced dedicated transport channel (E-DCH) transmission in Cell_FACH state. For more information.5. The value of the commissioning parameter to configure the number of HSUPA Resource Steps allocated for HS-RACH already exists but its range is increased.3 RAN2518 System impact Interdependencies between features The following features must be enabled before activating the RAN2518: High Speed Cell_FACH Enhanced feature: • • RAN1913: High Speed Cell_FACH RAN1686: HSPA 72 Users Per Cell The RAN2902: RACH Capacity Increase feature is recommended when RAN2518: High Speed Cell_FACH Enhanced feature is configured with increased number of common EDCH resources to fully use the system capacity. For transferring small packet data. 3. BTS level capability reporting to RNC is indicated by extending the private Iub message NBAP: CAPABILITY INDICATION. Without the RAN2518: High Speed Cell_FACH Enhanced feature up to four HSUPA resource steps could be statically allocated for HS Cell FACH. Currently.5. RNC - UE interface DN09203161 Issue: 01E . With the RAN2518: High Speed Cell_FACH Enhanced feature this limit is increased from 10 to 32 common E-DCH resources allowing up to 32 active HS-RACH users per cell. see High Speed Cell_FACH feature dimensioning in the Dimensioning WCDMA RAN: Flexi BTS Baseband document.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 3. Impact on interfaces • Iub – • NWI3 – • 86 In the NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION message. The RAN2518: High Speed Cell_FACH Enhanced feature extends the range of BTS baseband resource allocation per Local Cell Group (LCG).

    WCDMA 16 Feature Descriptions and Instructions – Radio resource management features SIB5 and SIB5bis indicate the number of common E-DCH resources. Impact on network and network element management tools This feature has no impact on network management or network element management tools. 3. 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.5. With one UE in the cell the performance is not impacted. 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.4 RAN2518 Reference data Requirements Table 24 RAN2518 hardware and software requirements RAS IPA-RNC mcRNC WCDMA16 RNC16 mcRNC16 OMS NetAct WCDMA OMS16 NetAct 16. Packet loss and latency in both low and high load cells is comparable to the RAN1913: High Speed Cell_FACH feature performance. In SIB5 and SIB5bis.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS WBTS16 WBTS16 Under planning MSC SGSN MGW UE Support not required Support not required Support not required 3GPP Rel-8 This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. 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. Because of that a greater number of users requiring short data transfers is allocated to HS-RACH. The RAN2518: High Speed Cell_FACH Enhanced feature allows for an increase in the overall HS-RACH throughput in a cell. the dedicated E-DCH users have better average throughput. As a result. Alarms Table 25 Alarms modified by RAN2518 Alarm ID Alarm name 7796 HIGH SPEED COMMON CHANNEL PROBLEM Measurements and counters Issue: 01E DN09203161 87 . 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.

    Radio resource management features Table 26 Counter ID New counters introduced by RAN2518 Counter name Measurement M1006C327 HS-FACH ABNORMAL RELEASE RRC signalling 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 HSPA in WBTS (WBTS) 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 WBTS R99 HW Resource (WBTS) M5006C73 AVERAGE NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WBTS R99 HW Resource (WBTS) M5006C74 MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WBTS R99 HW Resource (WBTS) M5006C75 AVAILABLE NUMBER OF HIGH SPEED CELL_FACH USERS WITH HS RACH WBTS R99 HW Resource (WBTS) Table 27 Counter ID 88 WCDMA 16 Feature Descriptions and Instructions Existing counters related to RAN2518 Counter name Measurement 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 DN09203161 Issue: 01E .

    WCDMA 16 Feature Descriptions and Instructions Table 27 Radio resource management features Existing counters related to RAN2518 (Cont. Parameters Table 28 New parameters introduced by RAN2518 Full name Abbreviated name Minimum Reduced E-DPDCH gain factor Table 29 MinRedEDPDCH Managed object RNC Parameters modified by RAN2518 Full name Abbreviated name Managed object Number of Common E-DCH Resources for HS-RACH HSRACHCommonEDCHRes WCEL High Speed RACH Enabled HSRACHEnabled WCEL HSPA 72 Users per Cell HSPA72UsersPerCell WCEL RNC Options RncOptions RNC Table 30 Existing parameters related to RAN2518 Full name Abbreviated name Managed object HSUPA enabled HSUPAEnabled WCEL High Speed Cell_FACH DL Enabled HSFACHEnabled WCEL HSDPA enabled HSDPAenabled WCEL Flexible UL RLC Enabled FlexULRLCEnabled RNFC HSDPA Dynamic Resource Allocation HSDPADynamicResourceA llocation RNFC Commands There are no commands related to this feature. Sales information Issue: 01E DN09203161 89 .) Counter ID Counter name Measurement 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 PREAMBLES HSPA in WBTS (WBTS) Key performance indicators There are no key performance indicators related to this feature.

g Note: Ensure an appropriate amount of BTS baseband resources has been commissioned for HS Cell FACH uplink. The feature code for this feature is 5577. Ensure BTS has the WBTS16 software release installed. Before you start Restart of RNC not required after the activation of this feature. see Licensing. see High Speed Cell_FACH feature dimensioning in the Dimensioning WCDMA RAN: Flexi BTS Baseband document.5 Activating RAN2518: High Speed Cell_FACH Enhanced Instructions to activate and configure RAN2518: High Speed Cell_FACH Enhanced using the OMS Element Manager.5. The following features must be enabled before activating of the RAN2518: High Speed Cell_FACH Enhanced feature: • • 90 RAN1913: High Speed Cell FACH RAN1686: HSPA 72 users per cell DN09203161 Issue: 01E . which defines the number of HSUPA resource steps per LCG. Make sure you have access to the following applications: • • OMS Element Manager Application Launcher Ensure that RAN2518: High Speed Cell_FACH Enhanced license exists. This can be done by changing the commissioning of the numOfHsRachResourceStepsRes parameter. Purpose Follow this procedure to activate the RAN2518: High Speed Cell_FACH Enhanced feature.    Radio resource management features Table 31 WCDMA 16 Feature Descriptions and Instructions RAN2518 Sales information BSW/ASW ASW SW component RAN License control in network element RNC LK 3. g Note: License status cannot be changed in the runtime without BTS reset. For more information. For more information on licensing. allocated for HS RACH users. Each resource step supports up to maximum 10 HS RACH users. This procedure requires cell locking and causes downtime. This feature is controlled by the long-term ON/OFF license key. Ensure that RNC SW release is the same as (or newer than) BTS SW release.

4 Expand the RNC object and then 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 Configure the WCEL object. For mcRNC. 3 Go to Topology and expand the ROOT directory. use the following MML command: ZW7M:FEA=5577:ON. use the following SCLI command: set license feature-mgmt code 0000005577 feature-adminstate on 2 Open OMS Element Manager. Sub-steps a) From the drop-down menu select Edit Parameters.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Set the RAN2518: High Speed Cell_FACH Enhanced feature state to ON: • • For IPA-RNC. 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. Issue: 01E DN09203161 91 .

92 DN09203161 Issue: 01E . and RNC configuration of common E-DCH resources is greater than 10. The BTS indicates support of the RAN2518: High Speed Cell_FACH Enhanced feature by using Private NBAP message: Capability Indication with the IE. BTS Capability Container. Procedure 1 Open the RNW Measurement Management application. Cell is unlocked. 8 Unlock the cell. If the BTS is compatible.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 7 Select Apply button to save the changes.5. BTS Capability Container.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. Unexpected outcome If BTS is not capable of the RAN2518: High Speed Cell_FACH Enhanced feature. 3. then PSCR Req sent by RNC to setup HS-RACH is acked with PSCR complete message by the BTS. RNC raises alarm 7796. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. Sub-steps a) Select the WCEL object b) Right click on the cell and select Administrative State Change ► Unlock Cell. RNC does not initiate HS-RACH setup and waits for an operator to fix the problem. For details on using the RNW Measurement Management application. Result Expected outcome The BTS indicates support of the RAN2518: High Speed Cell_FACH Enhanced feature by using Private NBAP message: Capability Indication with the IE.

Alternatively the measurement can be started using NetAct Administration of Measurements Application. see Using RNW Measurement Presentation in Managing and viewing RNC measurements. Use Internet radio application.    WCDMA 16 Feature Descriptions and Instructions 2 Radio resource management features Use the RNW Measurement Management application to start the M1006 measurement. The measurement interval then starts. The following counters are updated successfully: • • • Issue: 01E M1006C319 MAX NUMBER OF HS-FACH/HS-RACH USERS PER CELL M5000C460 CONFIGURED HS-RACH SIGNATURES M5000C461 NUMBER OF SUCCESSFULLY ACKNOWLEDGED HS-RACH PREAMBLES DN09203161 93 . 6 Open the RNW Measurement Presentation application. 5 Wait until the current 60-minute interval ends and then another 10 minutes. 3 Wait for the next 60-minute interval to begin. which utilizes TCP/IP as transport and connect each UE to a low bit rate radio station. After the measurement collection. it takes additional up to 10 minutes for the measurement data to be transferred to the OMS. For details on using the RNW Measurement Presentation application. 4 Make at least 32 simultaneous connections with Rel-8 UE that supports HSRACH. 7 Check if the following counters have been updated: • • • • • • • M1006C319 MAX NUMBER OF HS-FACH/HS-RACH USERS PER CELL 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.

7 Deactivating RAN2518: High Speed Cell_FACH Enhanced Purpose Follow this procedure to deactivate the RAN2518: High Speed Cell_FACH Enhanced feature. as RNC can send maximum 32 common E-DCH resources configurations per cell. 3.5. 94 DN09203161 Issue: 01E .    Radio resource management features • • • • g WCDMA 16 Feature Descriptions and Instructions 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 Enhanced feature (HS RACH Enhanced) up to 32 simultaneously active HS RACH users per cell is supported.

 use the following SCLI command: DN09203161 95 . 6 Select Apply button to save the changes. 7 Unlock the cell. 8 Issue: 01E Set the RAN2518: High Speed Cell_FACH Enhanced feature state to OFF: • For IPA-RNC. 2 Go to Topology and expand the ROOT directory. 5 Expand the RNC object and configure the WCEL object. 4 Lock the cell Sub-steps a) Select the WCEL object. b) Set the HSRACHCommonEDCHRes parameter to the value from 1 to 10. For mcRNC. 3 Expand the RNC object and then the WCEL object. Sub-steps a) From the drop-down menu select Edit Parameters. b) Right click on the cell and select Administrative State Change ► Lock Cell. Sub-steps a) Select the WCEL object b) Right click on the cell and select Administrative State Change ► Unlock Cell. use the following MML command: • ZW7M:FEA=5577:OFF.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open OMS Element Manager.

 This means that one subunit consumption is visible in the case of Flexi System Module release 3.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. 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.5.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions set license feature-mgmt code 0000005577 feature-adminstate off Expected outcome Cell is up and running. The configuration and parameter settings described are only examples. 3. DN09203161 Issue: 01E . This test is performed in the Verifying RAN2518: High Speed Cell_FACH Enhanced chapter of feature activation instruction. and they can vary in different networks. Do not use it for the feature as such in a live network.5. 3.5.8. Unexpected outcome The 7796 alarm is raised.8 Testing RAN2518: High Speed Cell_FACH Enhanced Purpose g 3. The following counter is checked via BTS Site Manager and RNW Measurement Presentation: • 96 M5008C50 CONFIGURED HS-FACH SUBUNITS IN BTS (The amount of subunits configured for EFACH in uplink in BTS.8.1 Note: This is an example of the verification. Number of common E-DCH resources is reduced to the value defined by the RAN1913: High Speed Cell_FACH feature. and two subunits are visible for Flexi System Module release 2. In comparison to the RAN1913: High Speed Cell_FACH feature 8 instead of 4 HSUPA resource steps can be statically reserved for HS-RACH users.

2 Ensure that BTS is commissioned according to Preconditions. Access to RNW Measurement Management. Operational Radio Access Network and Core Network. Preconditions • • • The M5012 FSM Level Monitoring measurement is started with RNW Measurement Management application. Figure 4 Issue: 01E HSUPA settings DN09203161 97 . The NetAct Configuration Management software can be used alternatively. 3 Perform recommissioning procedure with the below HSUPA resource allocation settings. Both FSMr2 and FSMr3 System Module platform can be used in this testing. BTS Site Manager compatible with BTS SW version.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Test environment • • • • • PC connected to BTS via LMP port or remotely. License for the RAN2518: High Speed Cell_FACH Enhanced feature is installed on RNC. Procedure 1 Open the BTS Site Manager. 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 HSUPA resource steps reserved for HS-RACH users to 8.

7 Expand WBTS BB subunits usage from Counters.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 4 After a full clock hour wait. The RAN2869: HSPA Subscriber Increase feature adds additional 98 DN09203161 Issue: 01E . The measurement interval then starts. For Flexi System Module Rel2: • 2 subunits consumption is visible in comparison to 1 for the RAN1913: High Speed Cell_FACH feature (4 resource steps). 9 Check the same counter via Application Launcher. 13 Check if the M5008C50 CONF_HSFACH_SU_WBTS counter has been updated.6 RAN2869: HSPA Subscriber Increase Introduction to the feature The RAN2869: HSPA Subscriber Increase feature provides a new set of HSPA subscriber capacity steps which operators can choose based on their own traffic profiles. 11 Wait for the next 60-minute interval to begin.5 for the RAN1913: High Speed Cell_FACH feature (4 resource steps). The current limit introduced by the RAN2124: HSPA 128 Users per Cell feature is 128 HSPA users per cell. 3. 6 Select BTS from Objects. Expected outcome For Flexi System Module Rel3: • 1 subunit consumption is visible in comparison to 0. 8 Select the M5008C50 CONF_HSFACH_SU_WBTS counter. 10 Use the RNW Measurement Management application to start the M5008 measurement. 5 Open Counters Tab. an additional 15 minutes and open BTS PM Tab in BTS Site Manager. 12 Wait until the current 60-minute interval ends and then another 10 minutes.

3. 3.1 RAN2869 Benefits End-user benefits The RAN2869: HSPA Subscriber Increase feature 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. It introduces a flexible capacity step upgrade capability based on traffic increase. The operator can purchase a pool size of subscriber capacity licenses for the RNC. depending on HSPATotIncreaseStep parameter settings. 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. When the operator allocates one pool of additional 16 HSPA users to some cell.6. Operator benefits The feature benefits the operator as follows: • • It allows the operator to define/purchase the needed amount of HSPA user capacity per cell. 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. 3. resulting in savings due to smaller and more flexible capacity steps. system performance. for example. resulting in increasing the maximum number of HSPA users per cell up to 208. If the operator does not enable the RAN2869: HSPA Subscriber Increase feature.2 RAN2869 Functional description The RAN2869: HSPA Subscriber Increase feature increases the maximum number of HSPA users per cell over the current limit of 128 by adding additional capacity steps.6. the system reduces the pool size of subscriber capacity licenses.6. g Note: Note that when the operator changes the 16 HSPA users amount (steps) between the cells. RL interference evolution.3 RAN2869 System impact Interdependencies between features The following features need to be activated before activation of the RAN2869: HSPA Subscriber Increase feature: • • • Issue: 01E RAN1637: HS Cell_FACH DL RAN1913: HS Cell_FACH UL RAN2124: HSPA 128 Users per Cell DN09203161 99 . RNC restricts the HSPA user amount to the number indicated by the existing HSPA (HSDPA) license. The size of one step is 16 HSPA users and the number of selected steps can vary from 1 to 5.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features capacity steps which allow to increase the maximum number of HSPA users per cell up to 208. The HSPATotIncreaseStep defines the capacity steps used in each cell. supported traffic profile.

    Radio resource management features WCDMA 16 Feature Descriptions and Instructions The following features are related to the RAN2869: HSPA Subscriber Increase feature: • • • • • • • • RAN1644: Continuous Packet Connectivity RAN1308: HSUPA Interference Cancellation Receiver 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. Alarms There are no alarms related to this feature. 3.6. 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. Measurements and counters Table 33 New counters introduced by RAN2869 Counter ID M1006C317 100 Counter name Measurement HSFACH_REJECT_MAX_USE RRC signalling RS DN09203161 Issue: 01E .4 RAN2869 Reference data Requirements Table 32 RAN2869 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS WCDMA 16 RNC16 mcRNC16 WBTS16 WBTS16 Not planned OMS NetAct MSC SGSN MGW UE WCDMA OMS16 NetAct 16.2 Support not required Support not required Support not required Support not required This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.

    WCDMA 16 Feature Descriptions and Instructions Table 34 Radio resource management features Existing counters related to RAN2869 Counter ID Counter name Measurement M1000C282 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 Key performance indicators There are no key performance indicators related to this feature. Sales information Table 38 RAN2869 Sales information BSW/ASW BSW+Long-term capacity license SW component RAN License control in network element RNC LK 3. Parameters Table 35 New parameters introduced by RAN2869 Full name HSPA total increase step Table 36 Abbreviated name Managed object HSPATotIncreaseStep WCEL Existing parameters related to RAN2869 Full name HSPA 128 Users per Cell Table 37 Abbreviated name Managed object HSPA128UsersPerCell WCEL New PRFILE parameters introduced by RAN2869 Parameter ID Parameter name 007:0521 HSPA_DCH_MIN_RES Commands There are no commands related to this feature. Issue: 01E DN09203161 101 .6.5 Activating RAN2869: HSPA Subscriber Increase Purpose Follow this procedure to activate the RAN2869: HSPA Subscriber Increase feature.

 the system reduces the pool size of subscriber capacity licenses. use the following command: • • for IPA-RNC: ZW7M:FEA=5465:ON. 102 DN09203161 Issue: 01E . Activate the license for the RAN2869: HSPA Subscriber Increase feature. where one step introduces 16 additional HSPA users per cell. Activating procedure does not require cell-locking and does not cause downtime in the network. the system reduces the pool size of subscriber capacity licenses. To set the feature state to ON. When the operator allocates one pool of additional 16 HSPA users to some cell. The RAN2869: HSPA Subscriber Increase feature is enabled by selecting the appropriate amount of HSPA users by the HSPATotIncreaseStep parameter. see Licensing. there is no need to restart RNC or BTS. The RAN2902: RACH capacity increase  feature increases the number of RACH signatures from 4 to 16. for mcRNC: set license feature-mgmt code 0000005465 feature-adminstate on For information on managing licenses. 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 the RAN3104 HSPA User Amount Monitoring feature. The following features are recommended to be activated/configured before activation of the RAN2869: HSPA Subscriber Increase feature: • • • • • • • • RAN1644: Continuous Packet Connectivity RAN1308: HSUPA Interference Cancellation Receiver 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 Enhanced  feature increases common E-DCH resources from 10 to 32.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Before you start After the activation of this feature. The parameter introduces 5 capacity steps. Before activating the RAN2869: HSPA Subscriber Increase feature. g Note: Note that even when the operator changes the 16 HSPA users amount (steps) between the cells.

 When the pre-emption is activated and the maximum number of HSPA and HS-FACH users per cell is obtained/surpassed.6. Issue: 01E DN09203161 103 . is not active. counted from right. 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 (144 HSPA users on cell) 2 (160 HSPA users on cell) 3 (176 HSPA users on cell) 4 (192 HSPA users on cell) 5 (208 HSPA users on cell) Note: The HSPATotIncreaseStep parameter cannot be enabled if the HSPA128UsersPerCell parameter is set to Disabled. within 0000 0000 x000 1011. The pre-emption is determined with the eighth bit within 0000 0000 1000 xxxx.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open OMS Element Manager. By default. the minimum reservation.6 Verifying RAN2869: HSPA Subscriber Increase Purpose Follow this procedure to verify if the RAN2869: HSPA Subscriber Increase feature works properly in the network. HS-FACH users are not permitted to use this capacity. 2 Go to Topology and expand the ROOT directory. 3. 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. Before you start Verify the amount of HSPA users selected by the HSPATotIncreaseStep parameter. When this minimum reservation is determined. determined with this PRFILE parameter. 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. 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.

 

 

Radio resource management features

WCDMA 16 Feature Descriptions and Instructions

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


Procedure
1

Open the RNW Measurement Management application.

2

Start the M1006 RRC SIGNALLING measurement.
For details on using the RNW Measurement Management application, see Using the
RNW Measurement Management Application in Managing and viewing RNC
measurements.

3

Open the RNW Measurement Presentation application.

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 Presentation in 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

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

3.6.7 Deactivating RAN2869: HSPA Subscriber Increase
Purpose
Follow this procedure to deactivate the RAN2869: HSPA Subscriber Increase feature.

104

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Radio resource management features

Procedure
1

Open OMS Element Manager.

2

Go to Topology and expand the ROOT directory.

3

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

4

g

Determine the value of the HSPATotIncreaseStep parameter to Disabled.
Note: After deactivation of the RAN2869: HSPA Subscriber Increase feature, the
amount of HSPA users in the cell is based on the owned license and parameter
settings.

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

Issue: 01E

DN09203161

105

 

 

Radio resource management features

WCDMA 16 Feature Descriptions and Instructions

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
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 originates 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.7.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:

The IRC mechanism provides more combining 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 the MRC mechanism at the receiver chain and
protects against the type of interference which is not managed with the IC
mechanism.

3.7.4 RAN3040 Reference data
Requirements

106

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Table 39

Radio resource management features

RAN3040 hardware and software requirements

RAS

IPA-RNC

mcRNC

Flexi
Multiradio
BTS

WCDMA 16

Support not
required

Support not
required

OMS

NetAct

MSC

SGSN

MGW

UE

Support not
required

NetAct 16.2

Support not
required

Support not
required

Support not
required

Support not
required

WBTS16

Flexi
Flexi Lite
Multiradio 10 BTS
BTS
WBTS16

Under
planning

This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio
System Module FSMF.
This feature requires more than one antenna per one cell. With one antenna N-1=0.
Faults
Table 40

New faults introduced by RAN3040

Fault ID

Fault name

4248

Reported alarms

IRC Receiver not
available for pure single
RX BTS configuration

7652 BASE STATION NOTIFICATION

Measurements and counters
Table 41

New counters introduced by RAN3040

Counter ID

Counter name

Measurement

M5005C55

SUM OF IRC PROCESSED USERS

HSPA in WBTS Extension

M5005C56

SUM OF ALL USERS

HSPA in WBTS Extension

M5005C57

ALL AND IRC USERS DENOMINATOR

HSPA in WBTS Extension

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

New parameters introduced by RAN3040
Full name

Abbreviated name

IRC receiver enabled

ircReceiverEnabled

Managed object
BTSSCW

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

Issue: 01E

RAN3040 Sales information

BSW/ASW

SW component

License control in network element

ASW

RAN

BTS LK

DN09203161

107

 

 

Radio resource management features

WCDMA 16 Feature Descriptions and Instructions

3.7.5 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:
BTS Site Manager

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

Open the 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, and then click Next.

4

Proceed to the BTS Settings page by clicking Next.

5

On the BTS Settings page, select the 'Activate IRC Receiver' 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 RAN3040: IRC Receiver feature is activated.

108

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Radio resource management features

3.7.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:

RNW Measurement Management
RNW Measurement Presentation

Procedure
1

Open the RNW Measurement Management application in the Application
Launcher.

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, see Starting radio network measurements in 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 Measurement Presentation application and check values of the
M5005C55 and M5005C56 counters.
For details on checking the counter values in the RNW Measurement Presentation
application, see Viewing and modifying radio network measurement parameters in
Managing and viewing RNC measurements.

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

3.7.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:

Issue: 01E

DN09203161

109

 

 

Radio resource management features

WCDMA 16 Feature Descriptions and Instructions

BTS Site Manager

Procedure
1

Open the 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, and then click Next.

4

Proceed to the BTS Settings page by clicking Next.

5

On the BTS Settings page, clear the 'Activate IRC Receiver' 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 RAN3040: IRC Receiver feature is deactivated.
Further information
After deactivating the feature set the feature license state to OFF.

3.7.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:

110

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.
M5005C56 SUM OF ALL USERS

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Radio resource management features

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 (see Activating
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 Extension’ 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.

Issue: 01E

DN09203161

111

 optionally.8 RAN3235: Optimized Packet Handling at RNC Introduction to the feature The RAN3235: Optimized Packet Handling at RNC feature introduces the Active Queue Management (AQM) mechanism to improve packet handling at RNC for DL data transmission from CN. in specific cases. increased buffer at RNC or advanced queue management are needed to prevent degradation of TCP/UDP performance. Operator benefits This feature optimizes the operator network to manage the TCP and UDP configuration demands within modern portable communication units and consequently. M5005C57 are collected every 100 ms. in specific cases. improved faireness of traffic among competing TCP flows.8.8. g Note: Samples of counters M5005C55. and. The value of the counter M5005C57 should be around 36000. the performance of the HTTP data transmission is not compromised at the congestion moment. The Active Que Management mechanism at PDCP 112 DN09203161 Issue: 01E . 3. The feature pertains to the HSPA data transmission. The RAN3235: Optimized Packet Handling at RNC feature introduces the Active Queue Management mechanism to improve TCP and UDP packet managing at RNC for DL data transmission from CN. incubation of HTTP traffic during congestion. The feature pertains to the HSPA data transmission. The optional mechanism of the HTTP incubation is introduced to ensure that. In specific cases. and decreased amount of dropped DL HSPA packets within the RNC PDCP.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions The value of the counter M5005C55 is greater than 0 and the CPU load on BTS equals M5005C56. M5005C56. It also provides decreased amount of dropped DL HSPA packets within RNC PDCP. fairness among the traffic flows. packet drops are controlled while ensuring fairness among the traffic flows. the TCP and UDP end-to-end performance is improved with stable throughput. packet drops are controlled while ensuring fairness among the traffic flows.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. improved faireness of traffic among competing TCP flows.1 RAN3235 Benefits End-user benefits The RAN3235: Optimized Packet Handling at RNC feature provides that even with the most demanding TCP configurations. 3. 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. 3. The mechanism provides that even with the most demanding TCP configurations. the performance of the HTTP data transmission is not compromised at the congestion moment within the RNC PDCP. and decreased amount of dropped DL HSPA packets within the RNC PDCP.

g Note: Single stream FTP download might occasionally face deviations in Download time observations towards the negative side. a probability is computed for each of the incoming HSPA packets. 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. The dimension of PDCP buffer is retained at optimum value of 1MB size and aligned with the Active Que Management(AQM) algorithm . fairness among the traffic flows. When the low priority data is not present. the latest packet is dropped and the computation is started again. 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. 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. 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. because of the lower stabilized throughput achieved due to AQM packet drops. and decreased amount of dropped DL HSPA packets within the RNC PDCP. Impact on interfaces This feature has no impact on interfaces.8. the Active Queue Management mechanism performs actions preventing the queue fills up starting with the packet of low priority. Once the oldest packet is older than determined threshold. When the Active Queue Management mechanism works with the In-Bearer Application Optimization mechanism. 3. the high priority data is dropped based on the Active Queue Management mechanism through the probability computation. DN09203161 113 . Impact on network and network element management tools This feature has no impact on network management or network element management tools. Note that the recommended option is to activate the feature with the mechanisms for AQM only.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 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. When the Active Queue Management mechanism is enabled without the HTTP incubation mechanism. When the Active Queue Management mechanism is enabled with the HTTP incubation mechanism.3 RAN3235 System impact Interdependencies between features This feature has a functional dependency with the RAN2510: In-Bearer Application Optimization feature. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: • Issue: 01E The operator network performance is optimized to manage the TCP configuration demands within modern portable communication units making the TCP end-to-end performance improved with stable throughput. Once the sum of probability computed for incoming HSPA packets is greater than determined threshold.

3.4 RAN3235 Reference data Requirements Table 44 RAN3235 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 RNC16 mcRNC16 Support not required Support not required Support not required OMS NetAct MSC SGSN MGW UE WCDMA OMS16 NetAct 16. Parameters Table 46 New parameters introduced by RAN3235 Full name Abbreviated name Managed object Optimized TCP Packet Handling at RNC Enabled TCPOptimizeEnabled RNFC AQM Delay Threshold Time AQMDelayThresholdTime RNHSPA Table 47 Parameters modified by RAN3235 Full name RNC Options Abbreviated name RncOptions Managed object RNC Commands There are no commands related to this feature. Measurements and counters Table 45 Existing counters related to RAN3235 Counter ID Counter name M1022C241 RLC DL SDU BYTES DROPPED Measurement Packet Call Key performance indicators There are no key performance indicators related to this feature.8.    Radio resource management features • • WCDMA 16 Feature Descriptions and Instructions The goodput performance is much more stable and fairness is improved among different traffic flows for the UE. the performance of the HTTP data transmission is not compromised at the congestion moment within the RNC PDPC. Alarms There are no alarms related to this feature. In specific cases.2 Support not required Support not required Support not required Support not required This feature requires no new or additional hardware. Sales information 114 DN09203161 Issue: 01E .

5 Activating RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to activate the RAN3235: Optimized Packet Handling at RNC feature in RNC. set the value of the TCPOptimizeEnabled parameter to: • Issue: 01E AQM RED Enabled. both the TCP/UDP and the HTTP packets are dropped during congestion or overflow scenarios. Before you start This activating procedure does not require cell locking.    WCDMA 16 Feature Descriptions and Instructions Table 48 Radio resource management features RAN3235 Sales information BSW/ASW SW component License control in network element ASW RAN RNC LK 3. there is no need to restart RNC or BTS. Install the license for the RAN3235: Optimized Packet Handling at RNC feature and set the feature state to ON using the following command: • • for IPA-RNC: ZW7M:FEA=5598:ON. After the activation of this feature. 3 Configure the RNFC object: Sub-steps a) Go to the RNFC object using the following path: RNC object ► RNFCs folder ► RNFC object. 2 Go to Topology and expand the ROOT directory. DN09203161 115 . b) Right-click the RNFC object and select Edit parameters. When only the Active Queue Management Random Early Detection (AQM RED) mechanism is activated. for mcRNC: set license feature-mgmt code 0000005598 feature-adminstate on Procedure 1 Open OMS Element Manager. for activating the AQM RED mechanism at RNC PDCP.8. c) On the Packet Scheduler tab.

• AQM RED Enabled + HTTP Incubation Enabled. during congestion or overflow scenarios the TCP/UDP packets are dropped and the HTTP packets are incubated (not dropped) in specific scenarios. Before you start Make sure that the RAN3235: Optimized Packet Handling at RNC feature is activated with the RNFC- TCPOptimizeEnabled parameter value AQM RED Enabled. see Using the RNW Measurement Management Application in Managing and Viewing RNC Measurements. g Note: After activating.8. 3 Start the M1022 Packet Call measurement.6 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. Ongoing connections are not affected. For details on using the RNW Measurement Management application. When both the AQM RED and the HTTP incubation mechanisms are active. 3. d) Click Apply to save the changes. 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 . the RAN3235: Optimized Packet Handling at RNC feature is applied only to new RRC Connections.AQMDelayThresholdTime parameter to 20 ms. for activating both the AQM RED and the HTTP incubation mechanisms at RNC PDCP. 2 Open the RNW Measurement Management application.    Radio resource management features g WCDMA 16 Feature Descriptions and Instructions Note: AQM RED Enabled is the recommended value of the TCPOptimizeEnabled parameter. 116 DN09203161 Issue: 01E .

8. Before comparing the measurement results.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 4 Initiate data transfers with 2 applications (for example HTTP and FTP) in a single UE for producing high traffic load to have congestion. the value of counter M1022C241 is expected to be lower when the RAN3235: Optimized Packet Handling at RNC feature is activated than when the feature is not activated. Expected outcome Packets drop is expected to be reduced at RNC PDCP. g Note: Optionally. 3. 5 Open the RNW Measurement Presentation application. ensure that the similar load conditions and measurement period were applied to both cases. Issue: 01E DN09203161 117 . Troubleshooting actions If the packet drop is not reduced. For details on using the RNW Measurement Presentation application. see Using RNW Measurement Presentation in Managing and viewing RNC measurements. 6 Check the value of the counter M1022C241: RLC DL SDU BYTES DROPPED. to configure the PDCP buffer size to 2MB. contact your local customer support. Under congestion conditions. The drop reduction can be verified with the counter M1022C241.7 Deactivating RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to deactivate the RAN3235: Optimized Packet Handling at RNC feature in RNC. increase the RNHSPA-AQMDelayThresholdTime parameter value by 10 ms and repeat the verifying procedure.

c) On the Packet Scheduler tab. 3 Configure the RNFC object: Sub-steps a) Go to the RNFC object using the following path: RNC object ► RNFCs folder ► RNFC object. g Note: After deactivating. the maximum number of RACH preamble signatures per cell is increased from 4 to 16. d) Click Apply to save the changes. Only the new RRC connections are not affected by this feature. Having more RACH preamble signatures available also improves the performance of the RAN1913: High Speed Cell_FACH and the RAN2518: High Speed Cell_FACH Enhanced features. especially in the highloaded cells. Operator benefits This feature decreases uplink interference thanks to fewer signature collisions and fewer RACH cycles needed. the RAN3235: Optimized Packet Handling at RNC feature is still applied to ongoing connections.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open OMS Element Manager. set the value of the TCPOptimizeEnabled parameter to Disabled.9.9 RAN2902: RACH Capacity Increase Introduction to the feature With the RAN2902: RACH Capacity Increase feature.1 RAN2902 Benefits End-user benefits This feature provides the end user with faster network access. 2 Go to Topology and expand the ROOT directory. 3. b) Right-click the RNFC object and select Edit parameters. 3. 118 DN09203161 Issue: 01E .

Increasing the number of RACH preamble signatures is especially beneficial when the RAN1913: High Speed Cell_FACH feature is in use.2 RAN2902 Functional description The RAN2902: RACH Capacity Increase feature increases the number of RACH preamble signatures available in a cell from 4 to 16.9. With the RAN2902: RACH Capacity Increase and the RAN1913: High Speed Cell_FACH features 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. the RAN1913: High Speed Cell_FACH feature has to be activated in the cell. however the average utilization of RACH/HS RACH can improve. Increased number of signatures decreases the probability of collision during the physical RACH procedure. Table 49 Available preamble signature combinations RAN1913 deactivated RACHPreambleSignatures parameter value Number of RACH preamble signatures Number of RACH preamble signatures Number of HS RACH preamble signatures 1 RACH signature 1 1 1 2 RACH signatures 2 2 1 3 RACH signatures 3 3 1 4 RACH signatures 4 3 1 N/A 3 3 8 7 1 4+4 RACH and HS RACH signatures N/A 4 4 4+8 RACH and HS RACH signatures N/A 4 8 4+12 RACH and HS RACH signatures N/A 4 12 3+3 RACH and HS RACH signatures 8 RACH signatures g RAN1913 activated Note: To enable HS RACH allocation. Operator can allocate up to 8 RACH signatures and up to 12 HS RACH signatures (but no more than 16 signatures in total). In consequence. the interference in the uplink is decreased. in the current system implementation there is only one preamble signature available for HS RACH. The number of subscribers with the HS-Cell_FACH-capable UEs is growing. Allocating preamble signatures is managed with the RACHPreambleSignatures WCEL parameter. Issue: 01E DN09203161 119 . Modification of this parameter requires cell locking and unlocking. 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). Additionally.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 3. RACH or HS RACH peak throughputs are not increased by this feature. However. and even more beneficial with the RAN2518: High Speed Cell_FACH Enhanced feature on top of it. RACH procedure needs fewer repetitions and the network access is faster.

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. 3.9. 3. BTS indicates its capability for using the RAN2902: RACH Capacity Increase feature in the NBAP: CAPABILITY INDICATION (Private NBAP message). For more information.433 UTRAN Iub interface Node B Application Part (NBAP) signalling. see Common Control Channels dimensioning in Dimensioning WCDMA RAN: Flexi BTS Baseband. For more information. The signatures in use are broadcast to UE in SIB5/SIB5bis. For more information.9. see Common Control Channels dimensioning in Dimensioning WCDMA RAN: Flexi BTS Baseband. 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. see 3GPP TS 25.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 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. The operator can check if BTS is capable of using the RAN2902: RACH Capacity Increase feature by looking up the value of the BTSRACHCapaIncCapability WBTS parameter. 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. Total amount of signatures is indicated to BTS by NBAP: CONFIGURATION DATA (Private NBAP message). Impact on network and network element management tools This feature has no impact on network management or network element management tools.4 RAN2902 Reference data Requirements 120 DN09203161 Issue: 01E .

2 Support not required Support not required Support not required Support not required This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms Table 51 Existing alarms related to RAN2902 Alarm ID Alarm name 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS 3325 INCONSISTENCY IN CONFIGURATION PARAMETERS Measurements and counters Table 52 Counter ID Issue: 01E New counters introduced by RAN2902 Counter name Measurement M5000C455 CONFIGURED R99 RACH SIGNATURES 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 HSPA in WBTS RACH MESSAGES 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 HS.HSPA in WBTS RACH MESSAGES M5000C465 R99 RACH SIGNATURES UTILIZATION - CLASS 1 HSPA in WBTS M5000C466 R99 RACH SIGNATURES UTILIZATION - CLASS 2 HSPA in WBTS DN09203161 HSPA in WBTS HSPA in WBTS 121 .    WCDMA 16 Feature Descriptions and Instructions Table 50 Radio resource management features RAN2902 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 RNC16 mcRNC16 WBTS16 WBTS16 Under planning OMS NetAct MSC SGSN MGW UE WCDMA OMS16 NetAct 16.

122 DN09203161 Issue: 01E .5 Activating RAN2902: RACH Capacity Increase Purpose Follow this procedure to activate the RAN2902: RACH Capacity Increase feature.) Counter ID Counter name Measurement M5000C467 R99 RACH SIGNATURES UTILIZATION - CLASS 3 HSPA in WBTS M5000C468 R99 RACH SIGNATURES UTILIZATION - CLASS 4 HSPA in WBTS M5000C469 R99 RACH SIGNATURES UTILIZATION - CLASS 5 HSPA in WBTS M5000C470 R99 RACH SIGNATURES UTILIZATION - CLASS 6 HSPA in WBTS M5000C471 HS RACH SIGNATURES UTILIZATION - CLASS 1 HSPA in WBTS M5000C472 HS RACH SIGNATURES UTILIZATION - CLASS 2 HSPA in WBTS M5000C473 HS RACH SIGNATURES UTILIZATION - CLASS 3 HSPA in WBTS M5000C474 HS RACH SIGNATURES UTILIZATION - CLASS 4 HSPA in WBTS M5000C475 HS RACH SIGNATURES UTILIZATION - CLASS 5 HSPA in WBTS M5000C476 HS RACH SIGNATURES UTILIZATION - CLASS 6 HSPA in WBTS Key performance indicators There are no key performance indicators related to this feature. Sales information Table 55 RAN2902 sales information BSW/ASW SW component License control in network element ASW RAN RNC LK 3. Parameters Table 53 New parameters introduced by RAN2902 Full name Abbreviated name Managed object RACH and HS-RACH Preamble Signatures RACHPreambleSignatures WCEL BTS RACH capacity increase capability BTSRACHCapaIncCapability WBTS Table 54 Parameters modified by RAN2902 Full name Abbreviated name High Speed RACH Enabled HSRACHEnabled Managed object WCEL Commands There are no commands related to this feature.9.    Radio resource management features Table 52 WCDMA 16 Feature Descriptions and Instructions New counters introduced by RAN2902 (Cont.

    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Before you start Activating procedure requires cell locking. After the activation of this feature. Unexpected outcome The cell cannot be unlocked. c) On the System Info tab. Troubleshooting actions If you have assigned HS RACH preamble signatures by setting the RACHPreambleSignatures parameter to one of the following values: Issue: 01E DN09203161 123 . To set the feature state to ON. use the following command: • • for IPA-RNC: ZW7M:FEA=5449:ON. and is unlocked when you finish editing. set the RACHPreambleSignatures parameter to the desired value. the RAN1913: High Speed Cell_FACH feature has to be activated in the cell. Activate the license for the RAN2902: RACH Capacity Increase feature using RACH capacity increase license key. To enable HS RACH allocation. for mcRNC: set license feature-mgmt code 0000005449 feature-adminstate on Procedure 1 Open OMS Element Manager. 2 Go to Topology and expand the ROOT directory. there is no need to restart RNC or BTS. 3 Configure the WCEL object: Sub-steps 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. g Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter.

For details on using the RNW Measurement Management application. cell Rx diversity. system sets the cell up with the default number of signatures (4 signatures) and the default cell range (20 km). 3.    Radio resource management features • • • • WCDMA 16 Feature Descriptions and Instructions 3+3 RACH and HS RACH signatures 4+4 RACH and HS RACH signatures 4+8 RACH and HS RACH signatures 4+12 RACH and HS RACH signatures ensure that the RAN1913: High Speed Cell_FACH feature is activated in the cell and the RAN2902: RACH Capacity Increase feature state is ON. Further information If alarm 3325: INCONSISTENCY IN CONFIGURATION PARAMETERS or 7775: INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS was raised. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.6 Verifying RAN2902: RACH Capacity Increase Purpose Follow this procedure to verify if the RAN2902: RACH Capacity Increase feature works properly in the network. 2 Start the M5000 HSPA in WBTS measurement. Before you start Make sure you have access to the following applications: • • RNW Measurement Management RNW Measurement Presentation Procedure 1 Open the RNW Measurement Management application. For more information. 124 DN09203161 Issue: 01E . ensure that the defined number of signatures.9. In case of incompatible configuration. see Common Control Channels dimensioning in Dimensioning WCDMA RAN: Flexi BTS Baseband. ensure that the RAN2902: RACH Capacity Increase feature state is ON. If you have assigned 8 RACH signatures by setting the value of the RACHPreambleSignatures parameter to 8 RACH signatures. and cell range form a compatible configuration. Ensure that the BTS is capable of using the RAN2902: RACH Capacity Increase by checking the value of the BTSRACHCapaIncCapability WBTS parameter.

Before you start Deactivating procedure requires cell locking. Issue: 01E DN09203161 125 . see Using RNW Measurement Presentation in Managing and viewing RNC measurements.7 Deactivating RAN2902: RACH Capacity Increase Purpose Follow this procedure to deactivate the RAN2902: RACH Capacity Increase feature. Expected outcome The values of counters M5000C455 and M5000C460 match the number of RACH and HS RACH signatures configured using the RACHPreambleSignatures parameter. For example. see Common Control Channels dimensioning in Dimensioning WCDMA RAN: Flexi BTS Baseband. system sets the cell up with the default number of signatures (4 signatures) and the wcdmadefault cell range (20 km). For more information. 4 Open the RNW Measurement Presentation application. If alarm 3325: INCONSISTENCY IN CONFIGURATION PARAMETERS or 7775: INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS was raised.9. if you start the measurements at 11:22. cell Rx diversity. In case of incompatible configuration. Ensure that the BTS is capable of using the RAN2902: RACH Capacity Increase feature by checking the value of the BTSRACHCapaIncCapability WBTS parameter. 3.    WCDMA 16 Feature Descriptions and Instructions 3 Radio resource management features Wait until the next full hour plus 10 minutes. the collected data is available in OMS at 12:10. ensure that the defined number of signatures. Troubleshooting actions Ensure that the RAN1913: High Speed Cell_FACH feature is activated in the cell if you assigend any HS RACH signatures. 5 Check if the values of the following counters have been collected: • • M5000C455: CONFIGURED R99 RACH SIGNATURES M5000C460: CONFIGURED HS-RACH SIGNATURES For details on using the RNW Measurement Presentation application. and cell range form a compatible configuration. Unexpected outcome The values of counters M5000C455 and M5000C460 do not match the number of RACH and HS RACH signatures configured using the RACHPreambleSignatures parameter.

Use the following commands: • • for IPA-RNC: ZW7M:FEA=5449:OFF.8 Testing RAN2902: RACH Capacity Increase Purpose g 126 Note: It is strongly recommended to test this feature in a live network to observe network performance improvement. 2 Go to Topology and expand the ROOT directory. DN09203161 Issue: 01E .9. set the value of the RACHPreambleSignatures parameter to 1. 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. Set the feature state to OFF. or 4 RACH signatures. 3 Configure the WCEL object: Sub-steps 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. 3. g 4 Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open OMS Element Manager. 3. for mcRNC: set license feature-mgmt code 0000005449 feature-adminstate off Unexpected outcome The cell cannot be unlocked. 2. and is unlocked when you finish editing.

g Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. and is unlocked when you finish editing. Procedure 1 Open OMS Element Manager. c) On the System Info tab. There is no need to restart RNC or BTS. set the value of the RACHPreambleSignatures parameter to 4 RACH signatures. For details on using the RNW Measurement Management application. For detailed instructions. 2 Go to Topology and expand the ROOT directory. Issue: 01E DN09203161 127 . 4 Configure the WCEL object: Sub-steps 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. 7 Wait until the next full hour plus 10 minutes. the collected data is available in OMS at 12:10. 5 Open the RNW Measurement Management application. 6 Start the M5000 HSPA in WBTS measurement. if you start the measurements at 11:22. 3 Deactivate the RAN1913: High Speed Cell_FACH feature using the HSRACHEnabled WCEL parameter. see Deactivating RAN1913: High Speed Cell_FACH. For example.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Before you start Testing procedure requires cell locking.

10 In OMS Element Manager. Values of counters in the range M5000C471–C476 are 0. c) On the System Info tab. if you start the measurements at 12:22. The value of the M5000C460 counter is 0. the collected data is available in OMS at 13:10. g Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter. check the values of all counters in the range M5000C455–C476 Expected outcome 128 DN09203161 Issue: 01E . set the value of the RACHPreambleSignatures parameter to 8 RACH signatures. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. Values of counters in the range M5000C461–C464 are 0. 11 In the RNW Measurement Management application. 12 Wait until the next full hour plus 10 minutes. For details on using the RNW Measurement Management application.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 8 Open the RNW Measurement Presentation application. reconfigure the WCEL object: Sub-steps 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. 9 Check the values of all counters in the range M5000C455–C476 Expected outcome • • • • The value of the M5000C455 counter is 4. start the M5000 HSPA in WBTS measurement. 13 In the the RNW Measurement Presentation application. and is unlocked when you finish editing. For example.

14 Activate the RAN1913: High Speed Cell_FACH feature using the HSRACHEnabled WCEL parameter. and is unlocked when you finish editing. Values of counters M5000C457 and M5000C459 are lower in comparision to results from step 8. the higher load for R99 RACH signatures. reconfigure the WCEL object: Sub-steps 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. Further information Counters M5000C465–C470 represent the percentage of R99 RACH signatures utilization. consequently. see Activating RAN1913: High Speed Cell_FACH. Values of counters M5000C456 and M5000C458 are higher in comparision to results from step 8. Enabling more signatures for use should be reflected by lower R99 RACH signatures utilization and. g Note: These predictions are based on the assumption that traffic load in the cell is constant. The higher utilization class. 15 In OMS Element Manager. a decrease of utilization class. c) On the System Info tab. The value of the M5000C460 counter is 0. DN09203161 129 . Values of counters in the range of M5000C461–C464 are 0. set the value of the RACHPreambleSignatures parameter to 4+4 RACH and HS RACH signatures.    WCDMA 16 Feature Descriptions and Instructions • • • • • • Radio resource management features The value of the M5000C455 counter is 8. For detailed instructions. Values of counters in the range of M5000C471–C476 are 0. g Issue: 01E Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter.

 if you start the measurements at 14:22. and is unlocked when you finish editing. Note: These predictions are based on the assumption that UEs with HS RACH support are present in the cell. 21 Wait until the next full hour plus 10 minutes. 20 In the RNW Measurement Management application. start the M5000 HSPA in WBTS measurement. 19 In OMS Element Manager.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions 16 In the RNW Measurement Management application. For example. 17 Wait until the next full hour plus 10 minutes. check the values of all counters in the range M5000C455–C476 Expected outcome • • • • g The value of the M5000C455 counter is 4. set the value of the RACHPreambleSignatures parameter to 4+12 RACH and HS RACH signatures. Values of counters in the range M5000C461–C464 are different than 0. start the M5000 HSPA in WBTS measurement. 130 DN09203161 Issue: 01E . c) On the System Info tab. For example. 18 In the the RNW Measurement Presentation application. The value of the M5000C460 counter is 4. g Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter. reconfigure the WCEL object: Sub-steps 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. the collected data is available in OMS at 15:10. if you start the measurements at 13:22. the collected data is available in OMS at 14:10. Values of counters in the range M5000C471–C476 are different than 0.

Enabling more signatures for use should be reflected by lower R99 RACH signatures utilization and. the higher load for R99 RACH signatures. Values of counters in the range of M5000C465–C470 are similar to results from step 16. 3. Operator benefits Load balancing between WCDMA and LTE is needed when LTE network starts to get high-loaded.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 22 In the the RNW Measurement Presentation application.10 RAN2892: WCDMA-LTE Load Balancing Introduction to the feature With RAN2892: WCDMA-LTE Load Balancing  feature.10. Preventing the redirection and handover attempts to high-loaded LTE cells reduces the need for further redirections and handovers. all traffic steering actions towards high-loaded LTE cells are suspended. 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. Issue: 01E DN09203161 131 . Expected outcome • • • • • • The value of the M5000C455 counter is 4.1 RAN2892 Benefits End-user benefits Blocking of redirections and handovers to high-loaded LTE cells improves the end-user experience. consequently. Further information Counters M5000C465–C470 represent the percentage of R99 RACH signatures utilization. Values of counters in the range of M5000C456–C459 are similar to results from step 16. Values of counters M5000C461 and M5000C463 are higher in comparision to results from step 16. a decrease of utilization class. Values of counters M5000C462 and M5000C464 are lower in comparision to results from step 16. The higher utilization class. The value of the M5000C460 counter is 12. 3. check the values of all counters in the range of M5000C455–C476.

2 RAN2892 Functional description The RAN2892: WCDMA-LTE Load Balancing feature prevents redirections and handovers from WCDMA layer to high-loaded LTE cells.10. The penalty timer is operator-tunable and controlled with the PenaltyTimerLTELoadHo RNMOBI parameter. • g LTE eNodeB initiates handover to WCDMA 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 the RANAPCause1LTELoadOutHo and/or the RANAPCause2LTELoadInHo RNMOBI parameter. This is indicated by the non-zero value of the RANAPCause1LTELoadInHo and/or the RANAPCause2LTELoadInHo RNMOBI parameter. If the RNC receives another high-load indication from the LTE cell before the penalty timer has expired. After the penalty timer expires. redirections and handovers from WCDMA to this LTE cell are stopped and a penalty timer for that cell is started. 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 UTRAN feature. WCDMA initiates handover to LTE cell which experiences high load and eNodeB rejects the handover due to load reasons. the penalty timer is restarted for that cell. RNC returns to the normal traffic steering. 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 balancing feature. 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. 3. 132 DN09203161 Issue: 01E .    Radio resource management features g WCDMA 16 Feature Descriptions and Instructions Note: This feature is beneficial only in the following cases: • In the operator's network the LTE1357: LTE-UTRAN load balancing feature (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: – – – • RAN2264: Smart LTE Handover RAN2717: Smart LTE Layering RAN2980: Measurement based LTE Layering In the operator's network the LTE57: Inter RAT handover from UTRAN feature (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 Handover feature are enabled. Source RNC receives RANAP: RELOCATION PREPARATION FAILURE message with the 'No Radio Resources Available in Target cell' cause.

 The source RRM Handover Control entity informs all the other RRM Handover Control entities in the RNC about the under-penalty LTE cells. UE does not consider any of the under-penalty cells.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features When redirection from WCDMA to LTE is initiated. While attempting to switch to the suitable LTE cell. the under-penalty LTE cells belonging to the LTE frequency layers selected for redirection are signaled to UE in the RRC CONNECTION RELEASE message as blacklisted cells. Issue: 01E DN09203161 133 .

RAN2176:LTEPSHandover activated + RAN2892:DynamicWCDMA-LTE LoadBalancing activated LTE57:InterRAT handoverfrom UTRAN activated + WCDMA toLTE handover failure duetohighloadof LTEcell AND/OR LTE1357:LTEUTRANload balancing activated + LTEtoWCDMA handover request duetohighloadof LTEcell CellID CellID LTEcelloverloadindication Penaltytimerstart (or restart ifalreadyrunning) forhigh-loadedLTEcells HandoverfromWCDMA toLTE(RAN2264:SmartLTE Handover)isnotinitiatediftargetLTEcell isunderpenalty duetohighload. g 134 Note: Some early Rel-8 UEs have problems during e-UTRA Compressed Mode measurements. Otherwise.20. available in Product Information Center. DN09203161 Issue: 01E . For more information on this issue. see Technical Support Note 149. section 5.UEscommandedtoredirecttoLTEsystem receivealistoftheneighboringunder-penaltyLTEcells belongingtothetargetLTEfrequencyas a blacklist. ) isprevented ifallqualifiedneighboringLTEcellsonall targetfrequenciesareunderpenaltyduetohighload. RedirectionfromWCDMA toLTE(RAN2717:SmartLTE LayeringRAN2980:MeasurementBasedLTELayering .    Radio resource management features Figure 5 WCDMA 16 Feature Descriptions and Instructions Overview of the RAN2892: WCDMA-LTE Load Balancing feature in Nokiabased radio network.

Alarms Issue: 01E DN09203161 135 . 3.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: • In the operator's network the LTE1357: LTE-UTRAN load balancing feature (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: – – – • RAN2264: Smart LTE Handover RAN2717: Smart LTE Layering RAN2980: Measurement based LTE Layering In the operator's network the LTE57: Inter RAT handover from UTRAN feature (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 Handover feature are enabled. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Reduced number of redirections and handovers results in reduced signaling load.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features 3. Impact on interfaces This feature impacts Iu interface.2 Support not required Support not required Support not required 3GPP Rel-8 This feature does not require any new or additional hardware.10. 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.10.4 RAN2892 Reference data Requirements Table 56 RAN2892 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 RNC16 mcRNC16 Support not required Support not required Support not required OMS NetAct MSC SGSN MGW UE WCDMA OMS 16 NetAct 16.

Parameters Table 59 New parameters introduced by RAN2892 Full name 136 Abbreviated name Managed 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 DN09203161 Issue: 01E . Table 58 Existing counters related to RAN2892 Counter ID Counter name Measurement 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 Key performance indicators There are no key performance indicators related to this feature.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions There are no alarms related to this feature. M1006C310. Measurements and counters Table 57 New counters introduced by RAN2892 Counter ID g Counter name Measurement 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 Inter System Hard Handover M1010C273 BLOCKED REDIRECTIONS TO LTE DUE TO LTE CELL LOAD Inter System Hard Handover 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. M1006C291. M1006C263.

10. This feature requires that the following feature is activated in RNC: • RAN2176: LTE PS Handover This feature is beneficial only in the following cases: • In the operator's network the LTE1357: LTE-UTRAN load balancing feature (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: – – – • Issue: 01E RAN2264: Smart LTE Handover RAN2717: Smart LTE Layering RAN2980: Measurement based LTE Layering In the operator's network the LTE57: Inter RAT handover from UTRAN feature (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 Handover feature are enabled. Activation procedure does not require cell locking. there is no need to restart RNC or BTS.5 Activating RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to activate the RAN2892: WCDMA-LTE Load Balancing feature.) Full name Abbreviated name Penalty Timer LTE Load Handover Table 60 PenaltyTimerLTELoadHo Managed object RNMOBI Parameters modified by RAN2892 Full name Abbreviated name Managed object RNC Options RncOptions RNC ADJE Identifier ADJEId ADJE Tracking Area Code AdjeTAC ADJE Commands There are no commands related to this feature.    WCDMA 16 Feature Descriptions and Instructions Table 59 Radio resource management features New parameters introduced by RAN2892 (Cont. Sales information Table 61 RAN2892 sales information BSW/ASW SW component License control in network element ASW RAN RNC LK 3. DN09203161 137 . Before you start After the activation of this feature.

for mcRNC: set license feature-mgmt code 0000005450 feature-adminstate on To enable WCDMA to LTE load balancing. available in Product Information Center. DN09203161 Issue: 01E . If the RAN2264: Smart LTE Handover feature is not active in the cell. section 5. The ADJE object is required to activate RAN2264: Smart LTE Handover feature.20. For more information on this issue. see Technical Support Note 149. To set the feature state to ON. g 138 Note: Some early Rel-8 UEs have problems during e-UTRA Compressed Mode measurements. then the operator needs to configure ADJE object. Creating ADJE object in the cell does not require license or activation of the RAN2264: Smart LTE Handover feature. WCDMA cells need to have neighboring LTE cells defined with the ADJE object. use the following command: • • for IPA-RNC: ZW7M:FEA=5450:ON. 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 the RAN2892: WCDMA-LTE Load Balancing feature.    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Activate the license for the RAN2892: WCDMA-LTE Load Balancing feature using WCDMA-LTE Load Balancing license key.

 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: • • Issue: 01E RNW Measurement Management RNW Measurement Presentation DN09203161 139 . 3 Configure the WCEL object: Sub-steps 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.6 Verifying RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to verify if the RAN2892: WCDMA-LTE Load Balancing feature works properly in the network. Before you start Activate the following features: • in WCDMA cell: – • RAN2264: Smart LTE Handover in LTE cell.10. c) On the Handover Control tab. 3.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Procedure 1 Open OMS Element Manager. 2 Go to Topology and expand the ROOT directory. set the value of the WCDMALTELoadBalEnabled parameter to Enabled.

    Radio resource management features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the RNW Measurement Management application. data collection starts every quarter. Wait for the measurement interval to begin. 2 Start the M1006 RRC signalling and M1010 Inter System Hard Handover measurements. Triggers for WCDMA to LTE handover of HSDPA users are specified in the RAN2264: Smart LTE Handover feature description. 11:30. 4 During the high load of LTE cell. g Note: In case of 15-minute interval. 3 Generate a high load in the LTE cell defined in the ADJE object of the WCDMA cell. For details on using the RNW Measurement Management application. The purpose of this step is to obtain rejection of WCDMA to LTE handover attempt due to high load in the LTE cell. see Using RNW Measurement Presentation in Managing and viewing RNC measurements. Expected outcome The values of the following counters have increased: • • • M1010C270: INCOMING HANDOVERS FROM LTE DUE TO LTE CELL LOAD M1010C271: LTE ISHO PREPARATION FAIL DUE TO LTE CELL LOAD M1010C272: BLOCKED HANDOVERS TO LTE DUE TO LTE CELL LOAD Further information 140 DN09203161 Issue: 01E . 6 Check if the values of the following counters have been collected: • • • M1010C270: INCOMING HANDOVERS FROM LTE DUE TO LTE CELL LOAD M1010C271: LTE ISHO PREPARATION FAIL DUE TO LTE CELL LOAD M1010C272: BLOCKED HANDOVERS TO LTE DUE TO LTE CELL LOAD For details on using the RNW Measurement Presentation application. The purpose of this step is to trigger handovers from LTE to WCDMA due to high load in the LTE cell. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 11:15. For example 11:00. 5 Open the RNW Measurement Presentation application. 11:45. trigger WCDMA to LTE handover.

c) On the Handover Control tab. 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. 3. set the value of the WCDMALTELoadBalEnabled parameter to Disabled. Issue: 01E DN09203161 141 . Then in step 4. Procedure 1 Open OMS Element Manager. Triggers for WCDMA to LTE layering are specified in the RAN2717: Smart LTE Layering and the RAN2980: Measurement based LTE Layering feature descriptions. 2 Go to Topology and expand the ROOT directory.7 Deactivating RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to deactivate the RAN2892: WCDMA-LTE Load Balancing feature. trigger WCDMA to LTE layering procedure. 3 Configure the WCEL object: Sub-steps 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. If the RAN2717: Smart LTE Layering and/or the RAN2980: Measurement based LTE Layering features are used for verification.    WCDMA 16 Feature Descriptions and Instructions Radio resource management features Verifying the RAN2892: WCDMA-LTE Load Balancing feature can be also conducted with RAN2717: Smart LTE Layering or the RAN2980: Measurement based LTE Layering feature instead of the RAN2264: Smart LTE Handover feature.10. during the high load of LTE cell. 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.

 With RIM. With the RAN3086: CSFB with RIM feature. The eNB requests the Single/Multiple Reporting from RNC's reporting cell. The RIM procedure is a 3GPP standard. LTE evolved Node B (eNB) is able to retrieve 3G System Information (SI) from RNC.1 RAN3086 Benefits End-user benefits This feature improves the overall end-user experience by accelerating a voice call setup time. circuit-switched call fallback is faster. The RIM procedure enables exchanging information between different Radio Access Technologies via the Core Network. 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.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). Operator benefits This feature enables exchanging information between different Radio Access Technologies via Core Network. 4.    Telecom features WCDMA 16 Feature Descriptions and Instructions 4 Telecom features 4. With the RIM procedure.1. RNC supports the UTRA System Information (SI) RIM procedure. 142 DN09203161 Issue: 01E .2 RAN3086 Functional description The RAN3086: CSFB with RIM feature introduces the RAN Information Management (RIM) procedure to RNC. For more information. The RIM UTRA procedure signaling happens between LTE (eNB) and RNC.1. see Signaling of RIM UTRA SI procedure figure and Signaling of RIM UTRA SI Procedure Error figure. 4.

    WCDMA 16 Feature Descriptions and Instructions Figure 6 Telecom features 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 Issue: 01E DN09203161 RNC!updates SIB modification of!a!cell!with Multiple Report RNC terminates the!Multiple Reporting (for!example reporting cell!is!deleted in!RNC) 143 .

 so that the UE reads the SI of the WCDMA cell from the release message.    Telecom features WCDMA 16 Feature Descriptions and Instructions Figure 7 Signaling of RIM UTRA SI Procedure Error RNC eNB RANINFORMATIONREQUEST/ RANINFORMATION ACK RANINFORMATIONERROR eNBnotices RIMprotocol errorin incoming message eNBnotices RIMapplication errorin incoming message RNCnotices RIMprotocol errorin incoming message RANINFORMATION RANINFORMATIONERROR RANINFORMATION RANINFORMATION APPLICATIONERROR RANINFORMATION ACK RANINFORMATIONREQUEST SingleReport/MultipleReport RANINFORMATION SingleReport/InitialMultipleReport (ApplicationErrorContainer) RNCnotices RIMapplication errorin incoming message With the UTRA SI RIM procedure. During a circuit- 144 DN09203161 Issue: 01E . LTE eNB uses the RNC's System Information for directing the UE to the WCDMA cell with RRC CONNECTION RELEASE (UTRA BCCH container. SIB1. Rel-9) message. SIB3. RNC includes the MIB. SIB5. SIB7 in UTRA SI RIM procedure. The RNC replies to the request with the relevant System Information Block (SIB) and the Master Information Block (MIB) of a particular cell. LTE eNB can inquire cell-specific System Information from RNC.

 

 

WCDMA 16 Feature Descriptions and Instructions

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, see 3GPP 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 the RAN2746: Fast HSPA Mobility feature is
recommended to be used with the RAN3086: 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 of RAN3086: 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:INFORMATION DIRECT TRANSFER message is 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 RAN3086 Reference data
Requirements

Issue: 01E

DN09203161

145

 

 

Telecom features

WCDMA 16 Feature Descriptions and Instructions

Table 62

RAN3086 hardware and software requirements

RAS

IPA-RNC

mcRNC

Flexi
Multiradio
BTS

Flexi
Multiradio 10
BTS

Flexi Lite
BTS

WCDMA 16

RNC16

mcRNC16

Support not
required

Support not
required

Support not
required

OMS

NetAct

MSC

SGSN

MGW

UE

WCDMA
OMS16

NetAct 16.2

Support not
required

SG8.0

Support not
required

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 63

New parameters introduced by RAN3086
Full name

Abbreviated name

RIM UTRA System Information
Application Enabled

Table 64

RIMUtraSIEnab

Managed
object
RNFC

Existing parameters related to RAN3086
Full name

Abbreviated name

Deferred Measurement Control
Reading

DefMeasCtrlReading

Managed
object
WCEL

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

RAN3086 Sales information

BSW/ASW
ASW

SW component
RAN

License control in network element
RNC LK

4.1.5 Activating RAN3086: CSFB with RIM
Purpose
Follow this procedure to activate the RAN3086: CSFB with RIM feature.

146

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Telecom features

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:

ZW7M:FEA=5418:ON;
for mcRNC:
set license feature-mgmt code 0000005418 feature-adminstate on

For information on managing licenses, see Licensing.
Before activating this feature the DefMeasCtrlReading WCEL parameter must be
set to Enabled.

g

Issue: 01E

Note: For enabling the DefMeasCtrlReading parameter, license of the
RAN2746: Fast HSPA Mobility feature is required.

DN09203161

147

 

 

Telecom features

WCDMA 16 Feature Descriptions and Instructions

Procedure
1

Open the OMS Element Manager.

2

Go to Topology and expand the ROOT directory.

3

Expand the RNC and expand the RNFC object.

4

Configure the RNFC object:
Sub-steps
a) Right-click on the RNFC object and select Edit parameters.
b) Set the RIMUtraSIEnab parameter value to Enabled.

g

5

Note: If all the needed license/feature states are not active (On), the system
does not allow to set the RIMUtraSIEnab RNFC parameter to value Enabled.
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.

Select Apply button to save the changes.

4.1.6 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

148

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

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

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 Indicator that 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 the RAN3086: CSFB with RIM feature.

Issue: 01E

DN09203161

149

 

 

Telecom features

WCDMA 16 Feature Descriptions and Instructions

Procedure
1

Open the OMS Element Manager.

2

Go to Topology and expand the ROOT directory.

3

Expand the RNC object then expand the RNFC object.

4

Configure the RNFC object:
Sub-steps
a) Right-click on the RNFC object and select Edit parameters.
b) Set the RIMUtraSIEnab parameter value to Disabled.

5

Select Apply button to save the changes.

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.

150

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

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 example Continuous 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.
Generic IMEI query

Issue: 01E

DN09203161

151

 

 

Telecom features

WCDMA 16 Feature Descriptions and Instructions

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 overall operation environment is presented in The IMEI collection and feature
operation concept figure. The left side of the figure presents the means to 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 TAClist

NetAct
L3DataCollector
(Monitoring)

Equipment
Identity
Register(EIR)

NWI3CMplan
interface

TAClist
collectionfor
example
withExcel

GUI

CN Traffica
(IMEIquery
enabledatCN)

RNC Traffica
(IMEIdelivery
fromRNC)

RNW
plan
XML

OMS
BTSO&M

Trafficareportingwith
IMEIinformation
(xx%outofcalls)

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

152

DN09203161

Issue: 01E

Table 67 Counter ID Issue: 01E New counters introduced by RAN3082 Counter name Measurement M1029C0 IMEI QUERY SENT BY RNC Device Detection M1029C1 FEATURE WHITELIST OPERATIONS Device Detection M1029C2 FEATURE BLACKLIST OPERATIONS Device Detection DN09203161 153 .2. Impact on interfaces This feature has no impact on interfaces.    WCDMA 16 Feature Descriptions and Instructions Telecom features 4. Measurements and counters Table 67: New counters introduced by RAN3082 lists counters introduced with this feature.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.2. Impact on network and network element management tools This feature has no impact on network management or network element management tools.4 RAN3082 Reference data Requirements Table 66: RAN3082 hardware and software requirements lists the software required for this feature. The applicable features are specified and implemented to be ready to support the device detection. 4. Table 66 RAN3082 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 RNC16 mcRNC16 OMS NetAct WCDMA OMS16 NetAct 16. Alarms There are no alarms related to this feature.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS Support not required Support not required Support not required MSC SGSN MGW UE Support not required Support not required Support not required Support not required This feature requires no new or additional hardware. Impact on system performance and capacity This feature has no impact on system performance or capacity.

Table 68 New parameters introduced by RAN3082 Full name g Abbreviated name Managed object WDEV identifier WDEVId WDEV WDEV name WDEVName WDEV List of TAC entries TACList WDEV SVN software version number SVN WDEV Whitelist features Whitelist WDEV Blacklist features Blacklist WDEV Change origin WDEVChangeOrigin WDEV WDEV control activation WDEVControlEnabled RNFC IMEI Query IMEIQuery RNC Note: WCDMA Device Detection (WDEV) is a new object class. 154 DN09203161 Issue: 01E . Key performance indicators There are no key performance indicators related to this feature. Table 69: Parameters modified by RAN3082 lists parameters modified by this feature. Sales information Table 70 RAN3082 Sales information BSW/ASW ASW SW component RAN License control in network element RNC LK 4.    Telecom features g WCDMA 16 Feature Descriptions and Instructions Note:  M1029 Device Detection is a new new measurement type.5 Activating RAN3082: Device Detection Purpose Follow this procedure to activate the RAN3082: Device Detection feature.2. Parameters Table 68: New parameters introduced by RAN3082 lists parameters introduced with this feature. Table 69 Parameters modified by RAN3082 Full name Abbreviated name RNC Options RNCOptions Managed object RNC Commands There are no commands related to this feature.

Issue: 01E DN09203161 155 . To set the feature state to ON. Maximum amount of capacity steps is 16. use the following command: • • for IPA-RNC: ZW7M:FEA=5586:ON. The number of capacity steps corresponds to the number of simultaneously active Whitelist and Blacklist controlled features.    WCDMA 16 Feature Descriptions and Instructions Telecom features Before you start After activating this feature there is no need to restart RNC. The upper capacity limit is defined via the Whitelist and Blacklist parameters bitmask length. The feature code for this feature is 5586. 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. The feature can be managed via the normal RNW configuration management interfaces: RNW local UI and NetAct. The Blacklist/Whitelist activation consumes one capacity step. and the PM measurements providing overall information. see Licensing. This feature is controlled by a license. It is allowed to activate one Blacklist/Whitelist feature/functionality per one license capacity step. Activating procedure does not require cell-locking. The ongoing connections/calls are not affected. Ensure that the features that are to be controlled with the RAN3082: Device Detection feature are already running in the network. For information on managing licenses. This feature becomes active for the UEs connecting after the feature has been configured. for mcRNC: set license feature-mgmt code 0000005586 feature-adminstate on The RAN3082: Device Detection feature is a capacity license controlled feature.

Create the needed amount of the WDEV objects with planned TAC. 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. The TAC entries defined for a certain feature have to be unique in all WDEV instances containing the same feature control information. 6 Create the WDEV object instance(s). g Note: The same feature can be controlled via several WDEV instances. The new value is used for the next new calls after the parameter modification. The same bit value cannot be set to value 1 in both Whitelist and Blacklist bit masks. SVN and feature control information. b) Set the value of the WDEVControlEnabled parameter to Enabled. 2 Go to Topology and expand the ROOT directory. A particular feature cannot be Blacklisted and Whitelisted simultaneously. This applies to all configured WDEV instances. The ongoing calls are not affected. The WDEV object instance contains Whitelist and Blacklist control parameters against which UE models defined within the TAC list are being controlled. Sub-steps a) Right-click on the RNC object and select Create New Object ► WDEV. Whitelist: RNC allows to use this feature only for the defined TAC values.    Telecom features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the OMS Element Manager. Sub-steps a) Right-click on the RNFC object and select Edit parameters. 4 Configure the RNFC object. Blacklist: RNC blocks the given feature use for the defined TAC values. 3 Expand the RNC object then expand the RNFC object. 156 DN09203161 Issue: 01E .

    WCDMA 16 Feature Descriptions and Instructions 7 Telecom features Configure the WDEV object. g Issue: 01E Note: The generic IMEI query functionality is available without any license.2. The generic IMEI information inquiry performed by the RNC can be activated via the RNC level parameter. The RNC level IMEI query can be activated for example in case the query is not activated at the core network elements. 8 4. DN09203161 157 . RNC performs the IMEI query for the defined percentage of the RAB establishments. c) Set the Blacklist parameter value as needed in relation to defined WDEV objects. Sub-steps a) Right-click on the WDEV object and select Edit parameters. 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.5.1 Select Apply button to save the changes. b) Set the Whitelist parameter value as needed in relation to defined WDEV objects. RNC is able to retrieve the IMEI from the CNperformed queries providing the similar result with the RNC level query. This can be used to collect additional UE behavior detailed monitoring data in the network. The RNC query is performed in addition to the CN-initiated IMEI queries.

2 Go to Topology and expand the ROOT directory. Sub-steps a) Right-click on the RNC object and select Edit parameters. 158 DN09203161 Issue: 01E .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.2. The features that are controlled with the device detection. 4 Select Apply button to save the changes. b) Set the value of the IMEIQuery parameter within range 1-100. 4.    Telecom features WCDMA 16 Feature Descriptions and Instructions Before you start Procedure 1 Open the OMS Element Manager. The IMEIQuery parameter provides the control over generic IMEI query performed by the RNC after RAB establishment. 3 Configure the RNC object. have to be properly configured in the network.

6 Wait until the current 15-minute interval ends and then another 10 minutes. 4 Wait for the next 15-minutes interval to begin. 8 Check if any of the following counters have value greater than 0: • • Issue: 01E M1029C1 FEATURE WHITELIST OPERATIONS M1029C2 FEATURE BLACKLIST OPERATIONS DN09203161 159 . it takes additional up to 10 minutes for the measurement data to be transferred to the OMS. 2 Open the RNW Measurement Management application. Without a PS call there are no counter updates. The measurement interval then starts. Blacklisted TAC codes correspond with to UE IMEI information. For details on using the RNW Measurement Management application.    WCDMA 16 Feature Descriptions and Instructions 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. for example. Alternatively the measurement can be started using NetAct Administration of Measurements Application. 5 Make a PS call with the UE that is whitelisted or blacklisted. After the measurement collection. CPC black/whitelisting is only checked when making a PS call. 3 Use the RNW Measurement Management application to start the M1029 measurement. see Using RNW Measurement Presentation in Managing and viewing RNC measurements. For details on using the RNW Measurement Presentation application. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. b) Check if the UEs are in the network where. 7 Open the RNW Measurement Presentation application.

    Telecom features WCDMA 16 Feature Descriptions and Instructions 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. Procedure 1 Open the RNW Measurement Management application. 5 Wait until the current 15-minute interval ends and then another 10 minutes. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. For details on using the RNW Measurement Management application. After the measurement collection.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. it takes additional up to 10 minutes for the measurement data to be transferred to the OMS. 6 Open the RNW Measurement Presentation application. Expected outcome The values of counters M1029C1 and M1029C2 are updated according to the Whitelist and Blacklist operations performed according to the RAN3082: Device Detection feature configuration. see Using RNW Measurement Presentation in Managing and viewing RNC measurements.2. 4. The measurement interval then starts. 2 Use the RNW Measurement Management application to start the M1029 measurement.6. For details on using the RNW Measurement Presentation application. 160 DN09203161 Issue: 01E . 4 Make a PS call. 3 Wait for the next 15-minutes interval to begin. Alternatively the measurement can be started using NetAct Administration of Measurements Application.

1 Select Apply button to save the changes. b) Set the value of the WDEVControlEnabled parameter value to Disabled. 3 Expand the RNC object then expand the RNFC object.    WCDMA 16 Feature Descriptions and Instructions 7 Telecom features 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. 2 Go to Topology and expand the ROOT directory. 5 4.2. Issue: 01E DN09203161 161 . Deactivating a Whitelist or Blacklist functionality Purpose Follow this procedure to deactivate a specific feature Whitelist or Blacklist functionality. Procedure 1 Open the OMS Element Manager. 4 Configure the RNFC object: Sub-steps a) Right-click on the RNFC object and select Edit Parameters.7 Deactivating RAN3082: Device Detection Purpose Follow this procedure to fully deactivate the RAN3082: Device Detection feature.

    Telecom features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the OMS Element Manager.2 Deactivating generic IMEI query in the RNC Purpose Follow this procedure to deactivate generic IMEI query functionality. 2 Go to Topology and expand the ROOT directory. The feature control does not affect already ongoing connections/calls. 5 Select Apply button to save the changes.7. 3 Expand the RNC object then expand the WDEV object. Expected outcome The RAN3082: Device Detection feature does not control the feature use anymore. 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. 4 Configure the WDEV object: Sub-steps a) Right-click on the WDEV object and select Edit Parameters.2. 4. 162 DN09203161 Issue: 01E .

2 Go to Topology and expand the ROOT directory. 4 Issue: 01E Select Apply button to save the changes. 3 Configure the RNC object. b) Set the value of the IMEIQuery parameter to 0.    WCDMA 16 Feature Descriptions and Instructions Telecom features Procedure 1 Open the OMS Element Manager. Sub-steps a) Right-click on the RNC object and select Edit parameters. DN09203161 163 .

1 RAN3112 Benefits End-user benefits This feature does not affect the end-user experience. can be aggregated to the shared 10GE port located in any BCN module. This feature provides new counters that measure both the backplane and the external interfaces Ethernet performance characteristics.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. The RAN3112: mcRNC Integrated Ethernet Switching feature introduces new measurement type M805 to measure mcRNC Ethernet interface traffic. 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. The physical interface Ethernet measurement supports 1 GE and 10 GE ports including the ports shared by several computing nodes. 164 DN09203161 Issue: 01E .    Transmission and transport features WCDMA 16 Feature Descriptions and Instructions 5 Transmission and transport features 5.1. Within the 10 GE connectivity optimized solution traffic from several EIPU units. which allow the system/the operator to verify if the configuration works as intended also from the backplane link load point of view. These counters allow identifying possible bottlenecks for traffic switched among different BCN modules and assist in the proper connectivity dimensioning and design. The backplane link load can be monitored via Ethernet Traffic counters. This feature provides new counters that measure both the backplane and external interfaces Ethernet performance characteristics. 5. 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. 5. This provides a possibility to follow the interface utilization and react timely to the traffic increase by planning for the mcRNC connectivity. The traffic at the mcRNC external physical interfaces and backplane interfaces can be monitored via the generic PM framework. 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.1.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. 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. that can be located to different BCN modules.

 The M805 measurement type can be used even if RAN3112: mcRNC Integrated Ethernet Switching feature is deactivated . Impact on network and network element management tools Issue: 01E DN09203161 165 .1. see Figure 9: mcRNC SFP ports.    WCDMA 16 Feature Descriptions and Instructions Transmission and transport features Using the 10 GE interfaces for external connectivity requires a capacity license. Switch ports used for BCN internal traffic cannot be measured. and external connectivity port from SFP+11 to SFP+12 and SFP13 to SFP22. The M805 BCN Ethernet Statistics measurement provides Ethernet layer statistics of mcRNC interfaces whose operational state is enabled. 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). which is based on the number of 10 GE interfaces applied for the external connectivity. The M805 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 mcRNC can support the BCN module front panel 1 GE and 10 GE physical port M805 measurement for the BCN-B HW module variant. Impact on interfaces This feature has no impact on interfaces.3 RAN3112 System impact Interdependencies between features This feature implements the licenses for RAN2696: mcRNC 10 Gigabit Ethernet Based Network Connectivity feature. 5. The object of the measurement is BCN/ETHPORT where BCN refers to the BCN module number and ETHPORT is the port identifier like SFP11. The external interface SFP ports covered by this feature are the backplane ports from SFP+0 to SFP+6. Figure 9 mcRNC SFP ports The mcRNC provides new measurement M805 BCN Ethernet Statistics.

    Transmission and transport features WCDMA 16 Feature Descriptions and Instructions This feature has no impact on network and network element management tools.4 RAN3112 Reference data Requirements Table 71 RAN3112 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 Support not required mcRNC16 Support not required Support not required Support not required OMS NetAct MSC SGSN MGW UE WOMS16 NetAct 16. Measurements and counters Table 72 New counters introduced by RAN3112 Counter ID Counter name M805C0 etherStatsDropEvents M805C1 etherStatsDropEvents M805C2 etherStatsUndersizePkts M805C3 etherStatsOversizePkts M805C4 etherStatsFragments M805C5 etherStatsJabbers M805C6 etherStatsCollisions M805C7 etherStatsPkts64Octets M805C8 etherStatsPkts65to127Octets M805C9 etherStatsPkts128to255Octets M805C10 etherStatsPkts256to511Octets 166 Measurement BCN Ethernet Statistics DN09203161 Issue: 01E .1.2 Support not required Support not required Support not required Support not required This feature is implemented for the BCN-B hardware. 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. 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. Alarms There are no alarms related to this feature.

 

 

WCDMA 16 Feature Descriptions and Instructions

Table 72

Transmission and transport features

New counters introduced by RAN3112 (Cont.)

Counter ID

Counter name

M805C11

etherStatsPkts512to1023Octets

M805C12

etherStatsPkts1024to1518Octets

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

Measurement

Key performance indicators
There are no KPIs related to this feature.
Parameters
There are no parameters related to this feature.
Sales information
Table 73

RAN3112 Sales information
BSW/ASW

SW component

BSW

RAN

License control in network
element
-

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.

Issue: 01E

DN09203161

167

 

 

Transmission and transport features

WCDMA 16 Feature Descriptions and Instructions

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 Controller feature 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.

168

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Transmission and transport features

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 RAN3193 Reference data
Requirements
Table 74

RAN3193 hardware and software requirements

RAS

IPA-RNC

mcRNC

Flexi
Multiradio
BTS

Flexi
Flexi Lite
Multiradio 10 BTS
BTS

WCDMA 16

RNC16

mcRNC16

Support not
required

Support not
required

Support not
required

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

Issue: 01E

DN09203161

169

 

 

Transmission and transport features

WCDMA 16 Feature Descriptions and Instructions

The related SCLI command for this feature is set 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 75

Existing parameters related to RAN3193
Full name

Abbreviated name

Key ID

keyId

Secret

secret

Auth type

authType

BFD detect multiplier

bfdDetectMult

BFD monitoring

bfdMonitoring

BFD RX interval

bfdRxInterval

BFD TX interval

bfdTxInterval

Dead interval

deadInterval

Election priority

electionPriority

Fast hello interval for
interface

fastHelloInterval

Hello interval

helloInterval

Interface

interface

OSPF cost

ospfCost

Passive

passive

Password

password

Retransmit interval

retransmitInterval

Managed object
MD5

O2IFC

Sales information
Table 76

RAN3193 Sales information
BSW/ASW

ASW

170

SW component
RAN

DN09203161

License control in network
element
RNC license key

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Operability features

6 Operability features
6.1 RAN3242: Category for Obsolete Parameters
Introduction to the feature
The RAN3242: Category for Obsolete Parameters feature enhances the current
parameter categorization in the NetAct application. The feature introduces a new
parameter category Obsolete, and improves the Advanced 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 obsolete parameters 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 Parameters feature improves the parameter
categorization in NetAct CM Editor and NetAct CM Plan Editor. The feature introduces a
new parameter category Obsolete.
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:

Issue: 01E

The All view displays all the parameters.This view displays the Basic, Advanced,
Obsolete, and the uncategorized parameters.

DN09203161

171

 

 

Operability features

WCDMA 16 Feature Descriptions and Instructions

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 as Obsolete. If they assessed
that a certain parameter in the Obsolete 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 Parameters feature.
Impact on interfaces
There are no impacts on interfaces for this feature.

172

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Operability features

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 different parameter category values for different parameters in the
same structure.
NetAct displays the obsolete parameters that are in the user-defined view in a
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 RAN3242 Reference data
Requirements
Table 77

RAN3242 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

Support not
required

Support not
required

Support not
required

OMS

NetAct

MSC

SGSN

MGW

UE

Support not
required

NetAct 16.2

Support not
required

Support not
required

Support not
required

Support not
required

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 as Obsolete, see:

RNC



Issue: 01E

Multicontroller RNC IP Parameters
Multicontroller RNC RNW Parameters
IPA-RNC IP Parameters
IPA-RNC RNW Parameters

BTS

DN09203161

173

 

 

Operability features

WCDMA 16 Feature Descriptions and Instructions


Flexi Multiradio BTS WCDMA Parameters
Flexi Transport Module Parameters

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

RAN3242 Sales information
BSW/ASW

SW component

BSW NetAct

RAN

License control in network
element
NetAct Radio WCDMA
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:


174

The unnecessary restart of the BTS (and co-located BTS transport) initiated during
the complete transport configuration plan activation is prevented.
Less service interruptions because the unnecessary BTS transport module reset is
avoided.
The unnecessary upload of BTS transport configuration is prevented.

DN09203161

Issue: 01E

 Otherwise.2. The following transport provisioning operations are also used in any planned configuration change: • • • • • creation of a delta configuration plan of 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 in NetAct 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. NetAct requests the download of the partial SCF to the set of target BTSs. For more information. 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. During the download operation. NetAct pre-validates the delta configuration plan for each target BTS. In using the NetAct Configuration Management (CM) applications. the operator selects a configuration plan containing transport configuration modifications to download to a set of target BTSs. the configuration plan is also validated by the Pre-activate operation in NetAct. Issue: 01E DN09203161 175 . This results in a decrease in download time compared to a complete configuration plan. NetAct creates a partial site configuration file (SCF) containing each modification specified in the delta configuration plan for each target BTS. and tracks the progress of the configuration plan download.    WCDMA 16 Feature Descriptions and Instructions Operability features 6. NetAct provides notification that the specified modifications include a change that require a BTS restart. Download of the delta configuration plan containing transport configuration In this phase. 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. see NetAct documentation CM Operations Manager Help ► Provisioning plans. The Validation operation in NetAct invokes the pre-validation of the delta configuration plan.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. g Note: NetAct invokes a BTS site manager (BTSSM) provided plug-in for pre-validation. and reports any validation errors.

 Different configuration scenarios and special handling are needed for the ATM and non-ATM MOs that involve the delta configuration plan. NetAct updates the data of the BTS configuration to match the changed data indicated in the CCN. 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. and then Create the MO. g Note: NetAct provides a notification if the specified modifications include a change that requires a BTS restart. For more information. the only way to modify the parameter is by Delete. which has been downloaded to the target set of BTSs. The addition/deletion/update of the transport parameters values do not require the BTS to restart if all the transport managed objects are marked as on-line. the use of multiple delta on-line configuration updates in NetAct is needed. validation. g Note: NetAct invokes a BTSSM provided plug-in for pre-validation. The configuration operation order of the MOs in Add/Delete configurator model must be followed: 176 DN09203161 Issue: 01E . If the parameter of any MO is not on-line modifiable. and activation in a single operation. 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. this prevents the need to upload the full transport configuration file from the BTS. Thus. NetAct tracks the progress of the configuration plan activation of each target BTS and reports the success or failure of the operation. see NetAct documentation CM Operations Manager Help ► Provisioning plans. Activate is another provisioning operation in NetAct. which includes download.    Operability features WCDMA 16 Feature Descriptions and Instructions For more information. see NetAct documentation CM Operations Manager Help ► Provisioning plans. and requests the activation of the parameter modifications by invoking the Activate pre-activated operation in NetAct. CCNs are also sent to NetAct by the BTS in case transport configuration is modified using BTSSM. 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. NetAct can then display the current data of the BTS configuration. Thus. Activation of configuration plan containing transport configuration The operator now selects a configuration plan.

The LinkOAM (LOAM) must be disabled (ETHLK. Issue: 01E DN09203161 177 . the modification of the Ethernet LOAM profile is rejected by the BTS. All the parameters of the TRDE are on-line configurable if the TRDE is not used in any ATM connection yet. the M-plane connection is lost. see BTSSM Online Help>TRS Hardware- Ethernet LinkOAM. VPCT and VCCT MOs must be deleted or updated first prior to the delete operation of TRDE MO. Otherwise.    WCDMA 16 Feature Descriptions and Instructions Add/Delete configurator model PPTTor SDHIFor IMAG Physicallayerinterface Addconfiguration Figure 11 Operability features ACCP TCCT TRDE TRDE VPCT TRDE VCCT ATMadaptationlayer(AAL) profilepointer VCTT AAL2 ANBA } A2UT } IAIF } A2ST AAL5-for IPoverATM (IPoA) AAL5 Deleteconfiguration VPTT A special handling is needed for TRDE MO and M-plane connections. 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. 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.linkOAMEnabled) using BTSSM for an Ethernet link before LOAM profile can be edited. For more information. Therefore. The TRDE MO is interrelated to both VPCT and VCCT MOs. and site visit is needed if the BTS does not support RAN2554: Transport configuration fallback for M-plane recovery feature. A full on-line configuration plan is forced by NetAct or BTSSM in re-commissioning the BTS to modify the parameters. Otherwise.

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. The following are examples of delta configuration plans on how to swap a VLAN ID of the IP interfaces: 1. the operator can select. Temporary assign an unused VLAN ID to one of the VLAN IP interfaces. The same problem happens when the existing IP addresses are swapped between IP interfaces (VLAN or plain Ethernet). To disable OSPF with BFD that is pre-configured as enabled and BFD MO exists. Modify the second VLAN IP interface to the first VLAN ID. 3. Modify the other VLAN IP interface to the previous VLAN ID. 2. 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. A full configuration plan is forced by NetAct to update the PDH parameter. To enable OSPF with BFD that is pre-configured as disabled and BFD MO does not exist. g Note: Same procedures are used to swap IP addresses. The operator needs multiple delta configuration plans to do VLAN IDs or IP addresses swapping. Manual commissioning or re-commissioning During manual commissioning or re-commissioning using BTSSM. When the BTS tries to apply the new ID on the 1st VLAN.    Operability features WCDMA 16 Feature Descriptions and Instructions 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. the BTS finds that there is another VLAN already existing with the same ID. as shown in Figure 12: Send parameters options in BTSSM. the operator needs to split the operation using multiple delta configurations in the following order: • • 178 Create BFD MO Enable OSPF with BFD DN09203161 Issue: 01E . the operator can use the delta configuration by selecting the Only changes option.

Figure 13 OSPF with BFD in BTSSM To modify Ethernet-based IP interface (IEIF) or VLAN interface (IVIF) local IP address (localIpAddr). the operator needs to send full SCF by selecting the All parameters option.2.    WCDMA 16 Feature Descriptions and Instructions Operability features The OSPF with BFD can be enabled and disabled in the IP view as shown in Figure 13: OSPF with BFD in BTSSM. and there is an existing BFD MO that is bounded to this address. Figure 14 Local IP address 6.3 RAN2706 System impact Interdependencies between features This feature is related to the following: Issue: 01E DN09203161 179 .

2. Impact on network and network element management tools There are no impacts on network and network element management tools for this feature. Alarms There are no alarms related to this feature. There is no impact on system capacity for this fearure. RAN2554: Transport Configuration Fallback feature supports the creation of a full transport configuration fallback file when activating a full transport subsystem (TRS) configuration file. Impact on system performance and capacity This feature has an impact on O&M system performance.2 Support not required Support not required Support not required Support not required This feature requires no new or additional hardware. Parameters 180 DN09203161 Issue: 01E . Other related features: • LTE552: Delta Configuration for Transport Impact on interfaces There are no impacts on interfaces for this feature. 6. 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.    Operability features WCDMA 16 Feature Descriptions and Instructions • • 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. Key performance indicators There are no key performance indicators related to this feature.4 RAN2706 Reference data Requirements Table 79 RAN2706 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 WBTS16 WBTS16 Not planned OMS NetAct MSC SGSN MGW UE Support not required NetAct 16. Measurements and counters There are no new measurements or counters related to this feature.

Sales information Table 80 RAN2706 Sales information BSW/ASW SW component BSW RAN License control in network element - 6.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. only the DNS server needs to be updated when the revocation server is changed.1 RAN2367 Benefits End-user benefits This feature does not affect the end-user experience. It is a drawback for the operators when the address of the repository server is changed.    WCDMA 16 Feature Descriptions and Instructions Operability features There are no parameters related to this feature. Commands There are no commands related to this feature. Issue: 01E DN09203161 181 .3. 6. RAN2367: DNS Support for Certificate Examination feature supports the DNS resolution in retrieving the addresses of the revocation distribution points. each certificate can contain the uniform resource locator (URL) of the corresponding revocation repository server or the URL can be preconfigured manually. With the introduction of FQDN. To make this checking possible.3. 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. All the certificates integrated to the link of the modified repository server address become invalid and the renewal of certificates is needed.3 RAN2367: DNS Support for Certificate Examination Introduction to the feature The RAN2367: DNS Support for Certificate Examination feature 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). 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. 6. 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.

 only the DNS server needs to be updated when the revocation server address is changed. The DNS IP address must be configured in the NE. Other related feature is RAN2268: Multi-Layer Certificate Authorities. This feature introduces certificate revocation support in BTS. 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 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. it is used when the primary DNS is unreachable. The BTS raises the 61074: CRL Update failure alarm if the CRL update fails. it is the certificate examination of network elements (NEs).    Operability features WCDMA 16 Feature Descriptions and Instructions The DNS client. In this case. which is the BTS. Impact on system performance and capacity There are no impacts on system capacity for this fearure.3 RAN2367 System impact Interdependencies between features The RAN2084: Support for certificate revocation (BTS) feature is needed to be activated and running. A secondary DNS IP address can be configured as well. the server replaces it by an explicitly truncated packet and the client retries using TCP. Domain name server (DNS) DNS is a generic solution that is utilized by several applications and for this feature. If the DNS response is exceeded to 512 bytes. provides the corresponding IP address of the repository server. Impact on network and network element management tools There are no impacts on network and network element management tools for this feature. Impact on interfaces There are no impacts on interfaces for this feature. If the DNS query has failed for both primary and secondary DNS. 182 DN09203161 Issue: 01E . sends the FQDN to the DNS and in return. the DNS client indicates the failure and aborts the query. The configuration is available in the BTS configuration plan or in the element manager (EM). 6.3.

Sales information Table 84 RAN2367 Sales information BSW/ASW BSW Issue: 01E SW component NetAct Radio WCDMA Standard SW DN09203161 License control in network element - 183 . Key performance indicators There are no key performance indicators related to this feature. Alarms Table 82 Alarms Alarm ID Alarm name 61074 CRL update failure Measurements and counters There are no new measurements or counters related to this feature.3. Parameters Table 83 Parameters Full name Abbreviated name Managed object Primary DNS Server IPv4 address IDNS.serverIpAddress2 WBTS Commands There are no commands related to this feature.    WCDMA 16 Feature Descriptions and Instructions Operability features 6.serverIpAddress WBTS Secondary DNS Server IPv4 address IDNS.4 RAN2367 Reference data Requirements Table 81 RAN2367 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 WBTS16 WBTS16 Not planned 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 no new or additional hardware.

Impact on network and network element management tools 184 DN09203161 Issue: 01E . at least two of the following features must be activated before starting up the RAN3247: 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.2 RAN3247/LTE2507/RG602496 Functional description The RAN3247: Energy Efficiency Shut Down Mode with RF Sharing feature releases RAT resources from the RF module during low traffic conditions or when required by the operator-defined profile. and LTE1103 licenses. 6. Operator benefits This feature helps to reduce OPEX due to energy savings provided by a power saving mode for RF sharing configurations.1 RAN3247/LTE2507/RG602496 Benefits End-user benefits This feature does not affect the end-user experience.4.    Operability features WCDMA 16 Feature Descriptions and Instructions 6.4. Impact on interfaces This feature has no impact on interfaces. 6. The Power Amplifier automatically goes into stand-by mode when both conditions are met: • Depending on RF sharing configuration.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 Sharing  feature introduces a power saving mode for RF sharing configurations.4. at least two RAT specific features are activated: – – – • RG301936: Intelligent MCPA TRX Shutdown RAN955: Power Saving Mode for BTS LTE1103: Load based Power Saving for multi-layer networks There are no radio resources reserved.3 RAN3247/LTE2507/RG602496 System impact Interdependencies between features Depending on RF sharing configuration. 6.

Alarms There are no alarms related to this feature.4 RAN3247/LTE2507/RG602496 Reference data Requirements Table 85 RAN3247 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 Support not required Support not required OMS NetAct Support not required Support not required Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS WBTS16 WBTS16 Not relevant MSC SGSN MGW UE Support not required Support not required Support not required Support not required This feature does not require any new or additional hardware. Impact on system performance and capacity This feature has no impact on system performance or capacity. Measurements and counters There are no measurements or counters related to this feature. Sales information Table 86 RAN3247 Sales information BSW/ASW SW component License control in network element ASW RAN RNC LK 6. Key performance indicators There are no key performance indicators related to this feature.4.4. Parameters There are no parameters related to this feature.5 Activating RAN3247: Energy Efficiency Shut Down Mode with RF Sharing Depending on RF sharing configuration. 6.    WCDMA 16 Feature Descriptions and Instructions Operability features This feature has no impact on network management or network element management tools. at least two of the following features must be activated before starting up the RAN3247: Energy Efficiency Shut Down Mode with RF Sharing feature: • Issue: 01E RG301936: Intelligent MCPA TRX Shutdown DN09203161 185 .

Licenses of the RG301936: Intelligent MCPA TRX shutdown and BSS20984: 2G TRX Automatic Power Down features are enabled.4. The BSC release S16. This feature is activated when both conditions are met: • • The value of the 2G TRX Power Down Threshold parameter is different from zero. 186 DN09203161 Issue: 01E . The BSS20984: 2G TRX Automatic Power Down feature has to be activated. ZW7M:FEA=4438:ON.1 or greater. The Flexi Multiradio licence has to be installed and enabled.0 release or greater.1. Follow this procedure to verify that RG301936: Intelligent MCPA TRX shutdown feature has been activated successfully.2 Verifying RG301936: Intelligent MCPA TRX shutdown Purpose Activation of the feature RG301936: Intelligent MCPA TRX shutdown can be verified by checking the value of the 2G TRX Power Down Threshold parameter.5.0.1. ZW7M:FEA=1236:ON.5.4.    Operability features WCDMA 16 Feature Descriptions and Instructions • • 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.1 6. 6.5.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 shutdown feature has to be installed. The Flexi Multiradio 10 with BTS GF1 1. 2 Change value of the Intelligent MCPA TRX shutdown feature state to ON using the W7M command.FULL:FEA=4438. ZW7I:FEA. 6. 3 Ensure that the feature state was changed successfully using the W7I command. Procedure 1 Change value of the 2G TRX Automatic Power Down feature state to ON using the W7M command.4.

<measurementinterval >. see: • • Reporter and Performance Management Principles in NetAct Product Documentation Converting BSC Measurement and Observation Result Files with MEFICO Step result 113009 MCPA POWER DOWNTIME DUE TRAFFIC counter of the Power Saving Measurement has been updated. The operational state of the measurement changes to Enabled within 15 minutes. 4 Start the measurement (TPS). the TRX(s) has been powered down. Issue: 01E DN09203161 187 . 3 Modify the Power Saving measurement (TPM). 2 Ensure that the licence for the Intelligent MCPA TRX shutdown feature has been installed (W7I).AUTOMATIC POWER DOWN (BL-PWS).    WCDMA 16 Feature Descriptions and Instructions Operability features Before you start At least two MCPAs configured in a segment. ZTPS:MEASUR. At the end of the measurement period. For more information.POWER_SAV. 7 Check the measurement data.FULL:FEA=4438. check the 113009 counter of the Power Saving Measurement in NetAct or in the BSC using the MEFICO tool. If the operational state of the TRX(s) is BLOCKED . ZTPI:MEASUR. Procedure 1 Ensure that the licence for the 2G TRX Automatic Power Down feature has been installed (W7I)..<output interval>. ZTPM:MEASUR.POWER_SAV:<measurementday>. The counter is updated when all TRX(s) in the MCPA have been shut down and their operational state is BL-PWS. ZW7I:FEA.FULL:FEA=1236. 5 Wait until the measurement is enabled and interrogate it (TPI). 6 Check the operational state of the TRX(s) (EEI). ZW7I:FEA.POWER_SAV.

Procedure 1 Change value of the Intelligent MCPA TRX shutdown feature state to OFF/CONF using the W7M command. The Power Saving Mode feature can be activated only on the Flexi BTS with software release WBTS6. If the installation is done using an MML interface. the feature covered by the license is automatically set to the ON state. The parameters for this feature can be configured with the RNC RNW Object Browser GUI.4. Feature Descriptions. the license has to be transferred to and installed in the RNC. (Check it in the RNC RNW Object Browser in WCDMA BTS object.3 Deactivating RG301936: Intelligent MCPA TRX shutdown Purpose Follow this procedure to deactivate the RAN955: Power Saving Mode for BTS feature.2 6.POWER_SAV. 6.5.1.4.1 Activating RAN955: Power Saving Mode for BTS in WCDMA Activating RAN955: Power Saving Mode for BTS Purpose The following procedures activate the RAN955: Power Saving Mode for BTS feature. Ensure that the O&M DCN link status is set to Enabled. ZTPE:MEASUR.) Preconditions: The following criteria have to be fulfilled to activate HSPA05 reconfiguration : • 188 The BTS has cells on two frequencies.2. In new installations. For information on managing licenses. 6. DN09203161 Issue: 01E . see the RAN955: Power Saving Mode Feature Description in WCDMA RAN. The feature code for this feature is 1459.5.0 onwards. If the installation is done using NetAct. the feature state (ON/CONFIG/OFF) has to be set by the user. the default state is set to OFF. ZW7M:FEA=4438:OFF.    Operability features WCDMA 16 Feature Descriptions and Instructions 8 Stop the Power Saving measurement (TPE). For more information on the feature. RU20.4. Ensure that you have a valid license.5. see . Rel. Before a license feature can be activated. Before you start This feature belongs to the application software and is under license key management. The license can be installed by using NetAct or a local MML interface.

The multi-operator RAN (MORAN) has to be taken into consideration according to the definitions of the feature management parameters. The cell shutdown decision is based on the other cell shutdown criteria. All cells of the BTS belong to the same Local Cell Group.) The number of remaining UEs in a cell is lower. the network can turn off the Power Saving Mode feature in the BTS by the PWSMInUse parameter.    WCDMA 16 Feature Descriptions and Instructions • • • • • • • • • Operability features All cells in the BTS belong to the same Power Saving Mode cell group. The HSDPA is enabled in all cells in the BTS. HSPA0 cells are reconfigured to HSPA5 cells. During gradual common pilot channel (CPICH) power ramp-down. Every non-remaining cell in a given frequency has PWSMShutdownOrder parameter value set to 1 and the PowerSaveHSPAType parameter in all these cells is set to HSPA5. the UE initiates a soft handover branch removal. The value of the PWSMCellGroup parameter is not zero. 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 number of lost calls during cell shutdown is smaller because of the RNC capability to handle simultaneous inter-frequency/inter-system handovers. the HSPA05 reconfiguration is not required. If HSPA05 reconfiguration is required. the success rate of branch removals and inter-frequency/inter-system handovers is increased.) The remaining cells are not allowed to be shut down. the non-remaining cell cannot be activated for traffic by means of the Power Saving Mode. Licence is installed in the RNC. (HSDPAenabled parameter has value set to Enabled in all cells in the BTS. 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. After CPICH power decrease. Power Saving Mode instructions: • • • The usage of gradual power ramp-down in the Cell Deletion procedure is recommended. DN09203161 189 . the RNC performs a forced inter-frequency handover for the remaining UEs. (PWSMShutdownRemCell parameter value in all remaining cells is set to No. If one or more criteria are not fulfilled. and are recommended for use in the RNC: – – – • • Issue: 01E Service and Load Based Handover Direct RRC Connection Setup HSPA Capability Based Handover. If the operator's actions lead to the situation when the Power Saving Mode environment is not consistent with the Power Saving Mode concept. When the gradual CPICH power ramp-down is used. The following features support traffic balancing between cells after shutdown or activation. For example. and HSPA5 cells are reconfigured to HSPA0 cells before shutdown. The MORAN network operators have to define the PWSMCellGroup and PWSMShutdownOrder parameters correctly. The RNC does not verify the MORAN definitions in the Power Saving Mode. During or after gradual CPICH power ramp-down the RNC detects a need for handover (inter-frequency or intersystem handover) and starts the procedure.) The DCN is working and WBTS is the FlexiBTS type.

    Operability features WCDMA 16 Feature Descriptions and Instructions HSPA05 reconfiguration instructions: • • • • • • • • The HSPA05 reconfiguration (resource swapping in the BTS) can be made only between cells belonging to the same Local Cell Group (LCG). The BTS maps cells from the one Tcell group to the same MAC high speed entity. Set the remaining cell shutdown end time by configuring the PWSMRemCellSDEndHour and the PWSMRemCellSDEndMin parameters. if the HSPA05 reconfiguration is made between different system module releases. the HSDPA is not configured to a cell with PowerSaveHSPAType parameter value set to HSPA0. For the RNC use the MML command: ZDCD. 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. The activation status of the Power Saving Mode for the BTS feature is not relevant. the parameter HSDPAenabled has to be set to value Enabled in both HSPA5 and HSPA0 cells. the HSUPAenabled parameter has to be set to value Enabled in both HSPA5 and HSPA0 cells. even if the HSDPAenabled parameter is set to value Enabled. For the mcRNC/ADA use the sCLI command: show networking-service ntp. so that 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). In cell setup. If the HSPA05 reconfiguration is used. The network operator has to take the LCG cell mapping into consideration when setting the PWSMCellGroup and PowerSaveHSPAType parameters. For working HSPA0 and HSPA5 configuration and reconfiguration. Set the remaining cell shutdown day by configuring the PWSMWeekday parameter. all cells have to be assigned to the same Power Saving Mode cell group. When HSUPA services and HSPA05 reconfiguration are used. Set the non-remaining cell shutdown start time by configuring the PWSMShutdownBeginHour and the PWSMShutdownBeginMin parameters. but the Rel1 system module does not. The cell and Tcell mapping have to be defined correctly by network operator. 3 Configure the WBTS object. 2 Open the RNC RNW Object Browser GUI. The RNC Tcell parameter (Frame timing offset of a cell) selects cells controlled by the shared MAC high speed entity. Some of HSPA functionalities might not be available. 190 DN09203161 Issue: 01E . the Rel2 system module supports HSPA+ functionalities. Set the remaining cell shutdown start time by configuring the PWSMRemCellSDBeginHour and the PWSMRemCellSDBeginMin parameters. This rule applies only for shared schedulers. In the Flexi BTS. Procedure 1 Check the RNC time setting.

Set the PWSMinUse parameter to value ON. Set two cells with the same frequency as remaining cells. Issue: 01E DN09203161 191 .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.4. the related WCEL object has to be locked. When HSPA05 reconfiguration is triggered. Further information After activating the feature. by configuring the PWSMShutdownOrder parameter to value 1. and set the PowerSaveHSPAType parameter to value HSPA0. Note: NOTE: Before configuring the PowerSaveHSPAType parameter. Two different cells with different frequencies are not assigned to the same shutdown order. and set the PowerSaveHSPAType parameter to value HSPA5. Set the third cell as a non-remaining cell. g Note: NOTE: The HSPA5 and shutdown criteria have to be fulfilled: • • g The BTS has cells on two frequencies. Traffic in the cell is low. 6 Cell shutdown 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.5. Expected outcome RAN955: Power Saving Mode for BTS feature is activated in the RNC. 5 Configure the BTS object. 6.2.    WCDMA 16 Feature Descriptions and Instructions 4 Operability features Configure the WCEL object. Configure the PWSMShutdownReCell parameter to value No to avoid shutdown of the remaining cell. The shutdown criteria are met. the RNC or the BTS restart is not required. cell 3 reconfiguration to HSPA0 and cells 1 and 2 reconfiguration to HSPA5 is performed. by configuring the PWSMShutdownOrder parameter to value 0.

 are to be activated.    Operability features WCDMA 16 Feature Descriptions and Instructions Procedure 1 In the RNC object. g Note: When deactivating Power Saving Mode. 2 In the WCEL-1 object.4. DN09203161 Issue: 01E . Set the PWSMinUse parameter value to OFF. set timer to trigger PWSM faster. Result The RAN955: Power Saving Mode for BTS feature has been deactivated. The cells that were shutdown. Procedure 1 Open the RNC RNW Object Browser GUI in the RNC Element Manager. set the PWSM cell group of a cell as 1. 2 Configure the BTS object. otherwise HSPA operational state cannot be enabled. enable PWSM by setting the PWSM usage in BTS as ON. the shutdown order of cells in one PWSM cell group as 1. PowerSaveHSPAType parameter has to be changed to No HSPA05_Reconfig value. Restart of the RNC or the BTS is not required. under the general tab. and HSPA Type of Cell in Power Saving Mode as HSPA5. the cell state changes to BL(P) and shutdown is performed. under the general tab. and modify the shutdown time period. the shutdown order of cells in one PWSM cell group as 0.3 Deactivating RAN955: Power Saving Mode for BTS Purpose Follow this procedure to deactivate the RAN955: Power Saving Mode for BTS feature. 6. under the general tab. Result If no call exists in WCEL-2. 3 In the WCEL-2 object. 4 In the WBTS object.5. set the PWSM cell group of a cell as 1.2. Post requisites • • 192 Set the feature license state to OFF. and HSPA Type of Cell in Power Saving Mode as HSPA0.

3 6.4.5.5. Modification of this parameter does not require eNB restart or object locking.3.1 Operability features 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. Table 87 Parameters used for activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networks feature Parameter Issue: 01E Purpose Requires eNB restart or 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 DN09203161 193 .    WCDMA 16 Feature Descriptions and Instructions 6.4.

 perform the steps described in this procedure. DN09203161 Issue: 01E . Note: A cell must have a unique value for lnCelId parameter and should be only in one power saving group. Expand the MRBTS object. b) Select the Load-based power saving cell list (lbpsCellList) parameter. b) Create new PSGRP object. a) Right click the selected LNBTS object. c) Perform the following configurations: • g 194 Create an entry in the LTE cell configuration identifier (lnCelId) parameter for each cells in the power saving group. Set the Activate load-based power saving (actLBPowerSaving) parameter value to True. 2 Set the activation flag. c) Define the value for the following parameters: • • • • • • 4 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) Define the serving cells and switch-off order in the power saving group.    Operability features WCDMA 16 Feature Descriptions and Instructions 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. Create new PSGRP object. a) b) c) d) 3 Go to the Radio Network Configuration page. Select the LNBTS object. a) Expand the selected PSGRP object.

 perform the steps described in this procedure. Expected outcome The LTE1103: Load Based Power Saving for Multi-layer Networks feature is activated in the eNB. Issue: 01E DN09203161 195 . Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. The control parameters and power saving groups are downloaded and activated in the eNB. b) Define the value for the following parameters: • • • • • 6 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) Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.    WCDMA 16 Feature Descriptions and Instructions • g 5 Operability features Set the Load-based power saving cell switch off order (lbpsCellSOOrder) parameter with a unique value for each cells ranging from 1 to 100.3.5.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. Define the time periods for energy saving. Note: The cell assigned with a value of 100 will not be switched off if the lbpsLastCellSOEnable parameter is set to false. 6. Modification of this parameter does not require eNB restart or object locking.4. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. Multiple cells can also be assigned with a value of 100. a) Select the Load-based power saving period list (lbpsPeriodList) parameter.

6. 196 DN09203161 Issue: 01E .1 RAN3060 Benefits End-user benefits This feature does not affect the end-user experience. Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. The feature provides the automatic detection and evaluation of RFI and PIM. 6. Expand the MRBTS object.    Operability features WCDMA 16 Feature Descriptions and Instructions 2 Configure the Activate load-based power saving (actLBPowerSaving) parameter a) b) c) d) 3 Go to the Radio Network Configuration page. Select the LNBTS object. locating.5. detection. The feature provides a faster and easier approach to monitor radio frequency performance that can be used to optimize and alleviate disturbances. and evaluation of radio frequency interference (RFI) and passive intermodulation (PIM) remotely by means of the BTS site manager (BTSSM). 6.5. 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.2 RAN3060 Functional description The RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature supports the monitoring.5 RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Introduction to the feature RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature supports the monitoring. Operator benefits This feature benefits the operator as follows: • • • The feature introduces OPEX savings by eliminating the need of expensive and labor extensive site portable PIM analyzer to detect degraded uplink performance caused by poor site infrastructure or cabling. and analyzing external disturbances such as RFI and PIM by means of the BTS site manager (BTSSM). Expected outcome The LTE1103: Load Based Power Saving for Multi-layer Networks feature is deactivated in the eNB. Set the Activate load-based power saving (actLBPowerSaving) parameter value to false.

 they are only hazardous to the network when they appear in the receiver (Rx) frequency band that causes interference with the radio reception. Passive inter-modulation (PIM) PIM occurs when two or more signals are present in a passive element such as coaxial cable. 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. connecting bolts. Issue: 01E DN09203161 197 . However. The introduction of this feature provides an automated tool set for RF-sniffing or scanning and PIM test. • PIM simulation mode The test involves the capturing of potential interference based on the BTS actual configuration. which allow operators to retrieve RF performance data that can identify the occurrence of RFI and PIM. duplexer. 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. Multi-carrier configuration refers to BTSs with two or more signal carriers shared in a single antenna. and so on. PIM distortion indicates spurious signals commonly occurs in the BTSs with multi-carrier configuration.    WCDMA 16 Feature Descriptions and Instructions Operability features Radio-frequency interference (RFI) RFIs are external disturbances caused by adjacent sites. harmonics. These disturbances must be detected and resolved as early as possible during the BTS installation or commissioning phase. 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. RF-sniffing/scanning has the following options: – – – g Raw composite Rx Composite Rx Carrier Rx Note: Not all radio modules support Composite Rx and Carrier Rx. The continuous monitoring of RFI determines if the BTS is degraded or is degrading slowly over a period of time. illegal emitter. Off-line test refers to the retrieval of RF measurement that sets the BTS to test dedicated mode. and faulty equipment that are common problems for operators. These spurious signals are inevitable in multi-carrier BTS.

smdf= special extension dedicated to the suite of tests g Note: PIM simulation test does not require a file transfer and therefore. minimum.5. It shows the maximum. 6. Only the visualization of the post-processed or captured data is provided. operators are allowed to view and monitor the RF performance and PIM simulation test. max. which is essential in RF performance management. In the BTSSM.3 RAN3060 System impact Interdependencies between features This feature is related to LTE1434: Flexi Multiradio BTS antenna Rx RF-sniffing 198 DN09203161 Issue: 01E .smdf where: test_name=scan_test for RF-sniffing/scanning or pim_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 . min. that is changing over time. 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#]. For more information on activating the parameters. 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. 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.    Operability features WCDMA 16 Feature Descriptions and Instructions The actRfiTesting and actPimTesting parameters must be set to true to enable RF-sniffing/scanning and PIM channel desensitization test respectively. see Activation of RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing. BTSSM supports the following reports: • • • mean square spectrum This is a two-dimensional plot that shows power density versus frequency. which shows the distribution of the received power over frequency. g Note: The real-time visualization of the streaming data is not supported. It describes the power distribution of the intermediate frequency (IF) signal with respect to the frequency spectrogram This is a three-dimensional plot. respectively. and average power depending on the frequency. not defined in the naming convention. 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).

BTS The BTSSM sends a new request message to the BTS for the on-line.    WCDMA 16 Feature Descriptions and Instructions Operability features Impact on interfaces BTSSM . 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.5.4 RAN3060 Reference data Requirements Table 88 RAN3060 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 WBTS16 WBTS16 Not planned 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 supports the following hardware: • RF module for RFI – – – – – Issue: 01E FXEB FXCB FXDB FHDB FHFB* DN09203161 199 . off-line. 6.

    Operability features WCDMA 16 Feature Descriptions and Instructions FRCG* FRGS FRGT FRGU* FRGY* FXFC FRGP-B FXFA FXFB FXEA FXCA FXDA FXDJ FHDA – – – – – – – – – – – – – – g Note: The RFI support for FHFB. Parameters Table 89 New parameters introduced by RAN3060 Full name 200 Abbreviated name Managed object Activate RFI testing actRfiTesting BTS Activate PIM testing actPimTesting BTS DN09203161 Issue: 01E . and FRCG will be available in future maintenance releases. Alarms There are no new alarms related to this feature. Key performance indicators There are no key performance indicators related to this feature. • RF module for PIM: FXEB FXCB FXDB FHDB FHFB* FRCG* FRGS FRGT FXFC – – – – – – – – – g Note: The PIM support for FHFB. FRCG. Measurements and counters There are no new measurements or counters related to this feature. FRGU. and FRGY RF modules will be available in future maintenance releases.

Before you start BTS restart is not required after the activation of this feature.5.5 Activating RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Purpose Follow the procedure to activate the feature. Issue: 01E DN09203161 201 . For more information on the feature. The RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature 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. see Licensing. For more information on licensing. The procedure is a non-service-affecting activity and does not cause downtime. Make sure you have access to BTS site manager (BTSSM). see RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature description. BTS is up and running. Sales information Table 90 RAN3060 Sales information BSW/ASW ASW SW component RAN License control in network element BTS licence key (LK) 6.    WCDMA 16 Feature Descriptions and Instructions Operability features Commands There are no commands related to this feature. 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.

Select Download to BTS button. 3 Download the licenses to the BTS. 5 Set actPimTesting and actRfiTesting parameters to TRUE. b) Select Activate RFI testing and Activate PIM testing. b) Go to Download License to Site ► Browse c) Select RF scanning/PIM channel desensitization license file. Figure 15 202 RFI and PIM testing in commissioning BTS settings DN09203161 Issue: 01E . Note: NetAct application can alternatively be used. 4 Select Close to close the dialog box.    Operability features WCDMA 16 Feature Descriptions and Instructions 2 Select the required license file. g g Note: The feature has two separate license codes. therefore perform step 2 and 3 for each license. Sub-steps a) Select Commissioning ► BTS Settings. Sub-steps a) Select the RF scanning/PIM channel desensitization license file.

2 onwards.    WCDMA 16 Feature Descriptions and Instructions 6 Operability features Finish the BTS commissioning. Make sure you have access to BTS site manager (BTSSM). Result Expected outcome: The RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature has been activated. 6.mathworks. The BTS is configured with multiple carriers. 2 Select RF Monitoring Figure 16 Issue: 01E RF Monitoring DN09203161 203 . The installation package can be downloaded in  http://www. The BTS is configured with RF HW 2.se/products/compiler/mcr. Procedure 1 Open BTS site manager.5. MATLAB Compiler Runtime (MCR) is installed. RFI and PIM testing are now supported in the BTS.6 Verifying RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Before you start The BTS is commissioned.

    Operability features WCDMA 16 Feature Descriptions and Instructions 3 Verify the RF-scanning test. the BTS is required to set in Test dedicated state and needed BTS restart. c) Select an antenna to be scanned. 204 DN09203161 Issue: 01E . b) Choose a folder where RF scan result will be saved. Sub-steps a) Select PIM desensitization in the Test tab. g Note: PIM desensitization works with RF HW 2. Start with the lowest possible TX power.3 onwards. Sub-steps a) Select RF scan in the Test tab. You will be transferred to File tab where the measurement is visible. A message box will appear notifying that download is completed. c) Select an antenna to be scanned. f) Click Visualize. e) Click Start. d) Select power (in dBm) of the cells to be tested. d) Select Capture type. 4 Verify the PIM desensitization test. g Note: In PIM channel desensitization test. b) Choose a folder where RF scan result will be saved.

PIM desensitization is retrieved and visualized in BTSSM. You will be transferred to File tab where the measurement is visible. A message box will appear notifying that download is completed. Result Expected outcome: RF scan data is retrieved and visualized in BTSSM. then increase the TX power value gradually in Step 4. Figure 17 Issue: 01E RF-scan visualization DN09203161 205 . g Note: If the result does not show too high desensitization value. f) Click Visualize.    WCDMA 16 Feature Descriptions and Instructions Operability features e) Click Start.

7 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).    Operability features WCDMA 16 Feature Descriptions and Instructions Figure 18 PIM desensitization visualization 6. 206 DN09203161 Issue: 01E . Go to Configuration ► License Management Step result Listed are the BTS features and licenses. Procedure 1 Open the License Management dialog box in the BTS site manager.5.

RFI scanning and PIM desensitization testing are now disabled in the BTSSM. b) Deselect Activate RFI testing and Activate PIM testing. 5 Finish the BTS commissioning. therefore perform step 2 for each license. 4 Set actPimTesting and actRfiTesting parameters to FALSE.5. Sub-steps a) Select Commissioning ► BTS Settings. 6. 3 Select Close to close the dialog box. 6. Result Expected outcome: RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature has been deactivated. g Note: NetAct application can alternatively be used. g Note: The feature has two separate license codes. Sub-steps a) Select the RF scanning/PIM channel desensitization license file.8.    WCDMA 16 Feature Descriptions and Instructions 2 Operability features Select the required license file. b) Select Delete button.8 Testing RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing Purpose This is an example of the verification.5. The configuration and parameter settings described are only examples and they can vary in different networks. do not use it for the feature as such in live network.1 Test case 1: RF-scanning Purpose Issue: 01E DN09203161 207 .

DN09203161 Issue: 01E . Operational radio access network (RAN) and core network (CN). Before you start The license for RF-scannning (license key: 5445) is installed in BTS. For license activation. Procedure 1 Select RF Monitoring in BTSSM sidebar. For enabling ‘Activate RFI testing’. see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing.    Operability features WCDMA 16 Feature Descriptions and Instructions This test verifies RF-scanning function introduced in RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing feature. Required test environment: • • • • • • One computer is connected to BTS via LMP port or remotely.2 or beyond. The MATLAB Compiler Runtime (MCR) is installed. The BTS site manager (BTSSM) is compatible with the BTS SW version. FSMr2 or FSMr3 System Module (SM) The BTS is configured with RF HW 2. The ‘Activate RFI testing’ checkbox is enabled in Commissioning BTS settings. Figure 19 2 208 RF monitoring in BTSSM Select RF scan in the Test tab. see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing.

5 Select Capture type ► Raw Composite Rx (RxADC) or Composite Rx (HBF0). 4 Select an antenna to be scanned. Figure 20 Issue: 01E RF-scanning measurement result for Raw Composite Rx or Composite Rx DN09203161 209 . 6 Click Start. 7 Click Visualize. You will be transferred to File tab where the measurement is visible. A message box will appear notifying that download is completed.    WCDMA 16 Feature Descriptions and Instructions Operability features 3 Choose a folder where RF scan results will be saved.

c) Select the cell on which this antenna type is available. 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: • • 210 Filename– name of the test file testType– type of test data that the file contains DN09203161 Issue: 01E . 9 Click Start.    Operability features WCDMA 16 Feature Descriptions and Instructions 8 Repeat Step 4 to Step 8 using different antenna. b) Select Carrier Rx (FIR9). You will be transferred to File tab where the measurement is visible. Sub-steps a) Repeat Step 4 to choose another antenna.

2 or beyond. Specify the following parameters for the cell ID Sim 1. 3 Choose Simulated antenna ► New antenna.2 Test case 2: PIM simulation Purpose This test case is used to validate the BTS configuration by using PIM simulation mode.5. Sim 3. Before you start Required test environment: • • • • • • One computer is connected to BTS via LMP port or remotely. IM9) DN09203161 211 .    WCDMA 16 Feature Descriptions and Instructions • Operability features 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 file available 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. The BTS site manager (BTSSM) is compatible with the BTS SW version. Operational radio access network (RAN) and core network (CN). 2 Select Simulation tab. FSMr2 or FSMr3 System Module (SM) The BTS is configured with RF HW 2. The MATLAB Compiler Runtime (MCR) is installed. Procedure 1 Select RF Monitoring in BTSSM sidebar. IM5. and frequency band: • • • • • • • Issue: 01E 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. IM7. Sim 2.8. 6. 4 Specify the needed parameters.

 add Sim 2 & Sim 3 Cell IDs as in previous steps. then the operator is notified of the error via an error message. All the required parameters must meet the criteria. If there is only one cell on antenna. 6. 212 DN09203161 Issue: 01E . and perform simulation. Figure 22 6 PIM simulation test result Repeat Step 3 to Step 5 for a different WCDMA bands.8. 7 Check result plots. BTSSM displays PIM Simulation results as plot.5.    Operability features WCDMA 16 Feature Descriptions and Instructions 5 Click Simulate. Result Expected outcome: PIM simulation test is executed in BTSSM.3 Test case 3: PIM desensitization Purpose This test case verifies the cell configuration is causing UL Channel interference using the PIM desensitization function. Unexpected outcome: If not all of the required parameters are specified or values are out of range. From the options in Simulated antenna ► Existing antenna.

The MATLAB Compiler Runtime (MCR) is installed. The BTS is in Test Dedicated state. 4 Select an antenna to be tested.2 or beyond. For enabling ‘Activate PIM testing’.    WCDMA 16 Feature Descriptions and Instructions Operability features Before you start The license for PIM channel desensitization (license key: 5446) is installed in BTS. 2 or 3 carriers per antenna are configured. 5 Click Start. Required test environment: • • • • • • • One computer is connected to BTS via LMP port or remotely. 6 Click Visualize. 3 Choose a folder where PIM desensitization results will be saved. see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing. Procedure 1 Select RF Monitoring in BTSSM sidebar. The ‘Activate PIM testing’ checkbox is enabled in Commissioning BTS settings. FSMr2 or FSMr3 System Module (SM) The BTS is configured with RF HW 2. The BTS site manager (BTSSM) is compatible with the BTS SW version. You will be transferred to File tab where the measurement is visible. 2 Select PIM desensitization in the Test tab. Issue: 01E DN09203161 213 . see Activating RAN3060: Flexi Multiradio BTS Antenna Rx RFsniffing. Operational radio access network (RAN) and core network (CN). A message box will appear notifying that download is completed. For license activation.

    Operability features WCDMA 16 Feature Descriptions and Instructions Figure 23 7 PIM desensitization test result Repeat Step 4 to Step 8 for the rest of the antenna and different cell powers. Test results are possible to save in the OS managed file system and as well as to save as picture to the desired folder. Symptom data can be collected with either Basic or Standard profiles. This feature improves and extends the RAN2446: Emergency Symptom Data Collection for IPA-RNC feature. then PIM Desensitization test is started. Result Expected outcome: The PIM Desensitization test is executed in BTSSM. and the storage requirements and load placed on the RNC to collect the data. The BTSSM displays PIM Desensitization Test results as plot. Data 214 DN09203161 Issue: 01E . This influences the type of data collected. 6. If all the required parameters meet the criteria. In certain troubleshooting cases the collection of traffic data is unnecessary in order to resolve the issue.6 RAN2872: IPA-RNC Symptom Report Introduction to the feature RAN2872: IPA-RNC Symptom Report feature provides extended functionality and new data collection profiles for the operator to use when collecting IPA-RNC symptom data (troubleshooting logs). and does not need to be performed.

 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. For more information.    WCDMA 16 Feature Descriptions and Instructions Operability features collection can be triggered either from an OMS or through new MMI commands on the RNC.1 RAN2872 Benefits End-user benefits This feature has no direct impact on the end-user experience. and is a mandatory part of every problem report submitted by the operator to Nokia Networks. The profiles are based on the log collection options from Technical Note TS-RNC-SW-038 RNC PROBLEM REPORT INSTRUCTIONS (TN38).2 RAN2872 Functional description The RAN2872: IPA-RNC Symptom Report feature enables the operator to collect symptom report data from the RNC using multiple profiles. It extends RAN2446: Emergency Symptom Data Collection for IPA-RNC by adding configurable Standard and Basic profiles for the symptom report. Editing the report profiles The symptom report profiles are stored as simple XML files which can be tailored to specific operator situations as required. This event-triggered data collection procedure is aborted if a new user-triggered collection is requested. This reduces the time taken to identify and resolve potential network problems. For more information. Triggering symptom report collection To start the report collection process. refer to Testing RAN2872: IPARNC Symptom Report g Note: When the RAN1805: RNC Event Triggered Symptom Data Collection feature is used. or from OMS CLI. refer to Configuring RAN2872: IPA-RNC Symptom Report Issue: 01E DN09203161 215 . The data collection for each profile can be initiated with a single command from RNC MML. The new profiles give the operator finer control over what data collection is performed on the RNC. 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 collection process in the IPA-RNC can be triggered by certain pre-defined alarms. The symptom report archive file is stored on the RNC hard disk and is automatically uploaded to OMS once it is created. without requiring them to log in remotely and use the CLI. The symptom report is compressed into a single archive file as soon as the data collection is completed. the user must be logged in to the IPA-RNC command shell or the OMS CLI. Operator benefits This feature benefits the operator by providing a quicker and simpler means to collect relevant troubleshooting data required by Nokia Networks. 6.6.6. 6. The symptom report is a collection of configuration data and logs that are essential for problem investigation. but may reduce the length of network outages if they occur.

6.4 RAN2872 Reference data Requirements Table 91 RAN2872 hardware and software requirements RAS IPA-RNC mcRNC WCDMA16 RNC16 Support not required OMS NetAct WCDMA OMS16 NetAct 16. Alarms 216 DN09203161 Issue: 01E . Impact on network and network element management tools This feature has no impact on network management or network element management tools.2 Flexi Multiradio BTS Flexi Lite BTS Flexi Multiradio 10 BTS Support not required Support not required Support not required MSC SGSN MGW UE Support not required Support not required Support not required Support not required This feature requires no new or additional hardware. RAN2229: Troubleshooting Data Management by NetAct - Troubleshooting data is automatically collected by NetAct. It is not recommended to collect data: • • during system start-up and trial as it might increase the start-up time during SW fallback package creation because the limitation of the ZWQB MML command might lead to fallback operation failure.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-RNC and provides two new collection profiles.6. Impact on interfaces This feature has no impact on interfaces.6. Impact on system performance and capacity Symptom data collection consumes system processing resources. 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.    Operability features WCDMA 16 Feature Descriptions and Instructions 6.

This section defines the file format and describes the procedure to update the profiles. the symptom report remains on OMS after collection. The profile XMLs are located under the path /RUNNING/LFILES/and are named RNCSTAND. Sales information Table 94 RAN2872 Sales information BSW/ASW SW component License control in network element BSW RAN - 6.    WCDMA 16 Feature Descriptions and Instructions Table 92 Operability features Existing alarms related to RAN2872 Alarm ID Alarm name 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.6. the symptom report is uploaded to NetAct and removed from OMS after collection. ClusterRoot/OMS/OMSPlatform/ SS_NELogManager/NELogManager/ dwNetActNotifyEnabled If set to 1.XML Issue: 01E DN09203161 217 . The profiles are configured by means of an XML definition file on the RNC hard disk. The XML must be downloaded.5 Configuring RAN2872: IPA-RNC Symptom Report Purpose The Standard and Basic profiles for RAN2872: IPA-RNC Symptom Report can be customized by the operator to add or remove certain types of data from the final report. OMS triggers the alarm 71106 TROUBLESHOOTING DATA RECEIVED once the symptom report is uploaded to OMS. the alarm is not triggered. If set to 0. If set to 0. Parameters Table 93 Existing OMS LDAP parameters related to RAN2872 Attribute Meaning ClusterRoot/OMS/OMSPlatform/ SS_NELogManager/NELogManager/ dwAlarmForUploadCompleted If set to 1.XML and RNCBASIC. Key performance indicators There are no key performance indicators related to this feature. edited externally and uploaded again to the RNC. Procedure 1 Download the XML file for the required profile from the RNC.

 "F" disables collection. there are three possible sub-elements: 1. please consult Symptom report profile XML structure. round may have the value 1. The <msg_mon> element has five attributes: • • 218 unit_type This is a mandatory attribute. All monitoring elements with the same value of round are collected simultaneously. Ensure that the edited file is valid XML. enabled "T" means this symptom log will be collected. similar to the 'run' option in TN38 default_config. the entry is ignored. If the name is not recognized by RAN2872. round This determines in which round to start msgmon collections with configuration of this element. It defines one type or source of data to be collected. If none of the <log_conf> elements can be parsed succesfully. Result The symptom report profile is updated and collects the data that was configured by the operator. and then 2. or 3. 3. etc. Only integers are allowed. DN09203161 Issue: 01E . Symptom report profile XML structure The XML has a root element that depends on the profile type: • • <standard_log_collection> <basic_log_collection> Within the root element. priority The logs with priority 1 are collected first. <msg_mon> The <msg_mon> element can appear multiple times in the root. It defines parameters for collecting message monitoring data. The value range is from 1 to 255. 2. 3 Upload the edited XML file to the original location in the RNC. The new profile can be tested by following the procedures outlined in Testing RAN2872: IPA-RNC Symptom Report. It can be used to toggle off certain types temporarily without deleting the whole element.    Operability features WCDMA 16 Feature Descriptions and Instructions 2 Edit the XML file in an XML editor For information on the XML structure and available options. 2. RAN2872 will use the default log type configuration to collect data for the symptom report. The unit type should be valid for RNC.ini. The <log_conf> element has exactly three attributes: • • • log_type This is a pre-defined name of a log type. otherwise the corresponding element configuration is skipped. <log_conf> The <log_conf> element can appear multiple times in the root.

<def_option> The <def_option> element appears once in the root. This value is in minutes. It should be less than half of the unit's free memory size. round="3" will be started. OR. The value is in bytes. A = Arrive R = Receive Compare operators: <. 3. 0C000) Examples: ZOEC::SA:FAM=0CO. all monitoring is stopped. olc_enabled DN09203161 219 .5. All monitoring elements that are configured with round="1" are started in the first round. ZOECN:OMU:S:(OFAM=0D0)AND(NOT(ATT=1.0BF. ZOEC::SA:(FAM=0FC)AND(PRO=1. the default configuration is used for msgmon collection. The meaning is the same as the instructions of the ZOEC command in RNC shell: EC(N):COMP*16/FUNIT:<S/A/R/SA/SR/AR/SAR>:monitoring_conditions ! WORD ! Give functional unit name (max 6 characters) Monitoring points: S = Send.    WCDMA 16 Feature Descriptions and Instructions • • • Operability features duration This determines how long msgmon will collect messages for the specified unit type. family PRO = process_id (in msg) CPRO = Co-process OPRO = Obj. ZOEC:4:S:DATB4=2. bufsize This determines how much buffer space is reserved for msgmon. <=. <type>: B / W / D <index>: msg offset (hex. It defines default and generic collections options. The <def_option> element can have up to eight attributes: • • Issue: 01E col_timeout This defines the collection timeout. <> Logical operations: AND. ZOEC::SAR:(FAM=0A0)AND(NUM=1. When that timer expires.6:S:(OFAM=0D0)AND(NOT(ATT=1.0C1. process FOC = focus (in msg) CFOC = Co-focus OFOC = Obj.2).2)). and keep the collecting for a period which is specified by the attribute duration. NOT Data field access: ABS<type><index> or DAT<type><index> ABS from msg start. >=. DAT from data start. 1234. conditions This attribute specifies the messages that will be collected. 0A. After the second round is over. >.3. and the elements that are configured with round="2" will be started. 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. The value is in seconds. It should be less than the value of col_timeout in the def_option element. focus ATT = attributes GRO = group NUM = number PHY = physical address Numeric values must start with a number (eg. ZOEC:4.4).2. =. It has the format <S/A/R/SA/SR/AR/SAR>:monitoring conditions. If all the <msg_mon> conditions are invalid. 1.0BE. and collecting is stopped if it has not finished when the time is up.2))AND(GRO>=1).4.

 This primarily affects long outputs from Chorus (bblog.0" encoding="UTF-8"?> <!DOCTYPE standard_log_collection SYSTEM "RNCSTAND. if disk_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%.DTD"> <standard_log_collection> <log_conf log_type="get_alarms" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_wbts_info" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_hpl_data" 220 DN09203161 Issue: 01E . It is specified in minutes and must be greater than the value of col_timeout. If any of the <def_option> attributes are missing or invalid. Because collection will take a longer time in an overloaded system. "T" means overload control is enabled during symptom report collecting. • • • • • • olc_timeout This defines the overload control timeout. "F" means disabled. "F" means disabled. "T" means compression is enabled.    Operability features WCDMA 16 Feature Descriptions and Instructions This defines whether overload control is enabled or disabled. "T" means health check is enabled . which removes some internal delays from the Chorus service terminal actor so that Chorus unit service terminal output becomes faster. "F" means disabled. disk_space_limit This defines the minimum percentage of free space required to perform msgmon and HPL data collection. RAN2872 will use the default values. This value takes effect only if olc_enabled="T". "F" means overload control is disabled. zip_rnw This option compresses the files when collecting the RNW database. perhaps some longer NIU counter outputs). "T" means enabled. The value is given in seconds. Otherwise (if CPU overload continues) the MML/STE command will ABORT and the data will not be collected. 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. If CPU overload occurs during symptom report collecting. a timer is started before MML/STE command execution. rmd logs. the value of olc_timeout will be used for collecting timeout rather than col_timeout. olc_cmd_wait This defines the overload control command waiting time. Example Symptom report profile XML file: RNCSTAND. health_check This option is for performing a health check when collecting the RNW database.XML <?xml version="1. For example. turbo_mode This enables or disables turbo mode.

8038.4B7.0D7A8.0A0F.07B8.0D5B8.7817.8037.0E2F.523)AND(NOT(NUM=1.508.952A . The value is in seconds.4EF.4EE.0D7A6.997)AND(NOT(NUM=14C.0D9DA.    WCDMA 16 Feature Descriptions and Instructions Operability features enabled="T" priority="7"> </log_conf> <log_conf log_type="get_computer_logs" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_spr_data" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_monitorings" enabled="T" priority="6"> <!-.0A340.2))" > </msg_mon> </log_conf> <log_conf log_type="get_sw_data" Issue: 01E DN09203161 221 .0E47B.0C466.8038.0D7A6.9836.0C465.0DD6E)))OR(NUM=0C5DF.997))AND(NOT(NUM=1.2.0C5DF.0B5D1.507.0A33 9.9F6.0A9A6.4FA. --> <msg_mon duration="30" bufsize="0x8FFFFF" unit="ICSU" round="1" conditions="SR:((OFAM=4FD.509.1 4B. conditions: <S/A/R/SA/SR/AR/SAR>:monitoring conditions. bufsize: it indicates how much buffer space is reserved for msg monitoring.0AB2E.0D331.0A49.952B))"> </msg_mon> <msg_mon duration="30" bufsize="0x6E38E" unit="OMU" round="2" conditions="SR:(OFAM=50B.03E 5.0D5BA.4B4. The value is in bytes.9B6)AND(NOT(CFAM=4FD.0CDA9)"> </msg_mon> <msg_mon duration="30" bufsize="0x8FFFFF" unit="RSMU" round="1" conditions="SR:(OFAM=592)"> </msg_mon> <msg_mon duration="30" bufsize="0x8FFFFF" unit="ICSU" round="2" conditions="SR:(OFAM=4FE.07D8.0A9B8. round : it indicates msg monitoring of this group will be done in which run sequence(be similar with run in TN38).8037.9835.duration: it indicates how long msg monitoring will last for specific unit type.0A49.9904.

    Operability features WCDMA 16 Feature Descriptions and Instructions enabled="T" priority="1"> </log_conf> <log_conf log_type="get_sw_data_1" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_sw_data_2" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_niu_counters" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_unit_loads" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_unit_memory" enabled="T" priority="1"> </log_conf> <log_conf log_type="get_startup_data" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_statistics_data" enabled="T" priority="4"> </log_conf> <log_conf log_type="get_atm_configuration_1" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_atm_configuration_2" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_atm_configuration_3" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_atm_configuration_4" enabled="T" priority="3"> 222 DN09203161 Issue: 01E .

    WCDMA 16 Feature Descriptions and Instructions Operability features </log_conf> <log_conf log_type="get_blackbox" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_epu_data" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_ip_configuration" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_ip_configuration_2" enabled="T" priority="2"> </log_conf> <log_conf log_type="get_ss7_configuration" enabled="T" priority="4"> </log_conf> <log_conf log_type="get_mml_data" enabled="T" priority="10"> </log_conf> <log_conf log_type="get_rnw_databases" enabled="T" priority="20"> <rnw_db health_check="F" zip_rnw="F"> </rnw_db> </log_conf> <log_conf log_type="get_hw_data_1" enabled="T" priority="10"> </log_conf> <log_conf log_type="get_hw_data_2" enabled="T" priority="10"> </log_conf> <log_conf log_type="get_hw_data_3" enabled="T" priority="11"> </log_conf> <log_conf log_type="get_control_files" enabled="T" priority="40"> Issue: 01E DN09203161 223 .

 and is a mandatory part of every problem report submitted by the operator to Nokia Networks.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.    Operability features WCDMA 16 Feature Descriptions and Instructions </log_conf> <log_conf log_type="get_synchronization_data" enabled="T" priority="40"> </log_conf> <log_conf log_type="get_application_files" enabled="T" priority="40"> </log_conf> <log_conf log_type="get_vidast" enabled="F" priority="40"> </log_conf> <log_conf log_type="ping_ips" enabled="F" priority="30"> </log_conf> <log_conf log_type="get_disk_logs" enabled="T" priority="20"> </log_conf> <log_conf log_type="execute_own_cmd" enabled="F" priority="40"> </log_conf> <log_conf log_type="get_zwdi_data" enabled="F" priority="50"> </log_conf> <log_conf col_timeout="30"> </log_conf> <log_conf olc_enabled="T" olc_timeout="60" olc_cmd_wait="90"> </log_conf> </standard_log_collection> 6.6. The symptom report can be triggered manually either through the IPA-RNC command shell or via OMS CLI. 224 DN09203161 Issue: 01E .

 use the ZIAI:USERID=SOKERI. The default value of 1 will cause the collected logs to be uploaded to NetAct and removed from the OMS. The SOKERI account remains in the system through NE restarts. The typical error message will be that both sessions are already in use by the SOKERI account and the CBYPRB process. MML command. use the ZIAH:SOKERI:PROFILE:.6. Note: If the RAN2872 log collection is performed under high CPU load. These processes may take several minutes to finish due to the load. The user can be added to the _nokNELogManage group by an administrator with the command fsgpasswd -a <username> _nokNELogmanage. This is due to the number of concurrent login sessions made during collection exceeding the defined limit in the parameter (9. both OMU login sessions can become occupied by running collection processes. To create a SOKERI account. In this case. The password is arbitrary and does not need to be retained. To check the existence of the SOKERI account.6. 137) SEC_EVENT_LOAD_LIMIT.    WCDMA 16 Feature Descriptions and Instructions 6.1 Operability features 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. g g Note: The alarm 3319 NORMAL LOAD OF SECURITY EVENTS EXCEEDED may be raised during the collection of symptom report data. To keep the logs stored on OMS and prevent them from being uploaded to NetAct. 2 Trigger the data collection on the NE with the zcollectNElogs command: Select from available options Issue: 01E DN09203161 225 . the OMS configuration parameter • • ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dw NetActNotifyEnabled must be set to 0. 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. Multiple concurrent logins are made for efficiency reasons. the user must wait until the RAN2872 process is completed before logging in. Procedure 1 Log in to OMS CLI. during which time it will not be possible for the user to log in to OMU. MML command.

 use the ZIAH:SOKERI:PROFILE:. but may need to be recreated after software fallback or upgrades are applied. To check the existence of the SOKERI account. The SOKERI account remains in the system through NE restarts.<date-time>. 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_<NE>_<RNC-ID>.6. The date-time format is YYYYMMDDhhmmss. Error messages There are no error messages in OMS CLI during data collection. The alarm is raised when the collection process has finished and the symptom report is already uploaded to OMS.2 Symptom report collection using RNC MML commands Before you start • NetAct: – – • g 226 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. MML command. Wait for the alarm 71106 TROUBLESHOOTING DATA RECEIVED to be raised. Multiple concurrent logins are made for efficiency reasons.zip. DN09203161 Issue: 01E . The password is arbitrary and does not need to be retained. 6. Note: The alarm 3319 NORMAL LOAD OF SECURITY EVENTS EXCEEDED may be raised during the collection of symptom report data. use the ZIAI:USERID=SOKERI.6.    Operability features WCDMA 16 Feature Descriptions and Instructions • • 3 zcollectNElogs -n <RNC-ID> -p RNCSTAND collects data according to the standard profile. instead the network element will raise the alarm 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED if an error occurs during collection or upload of the symptom report. To create a SOKERI account. MML command. This is due to the number of concurrent login sessions made during collection exceeding the defined limit in the parameter (9. zcollectNElogs –n <RNC-ID> –p RNCBASIC collects data according to the basic profile. 137) SEC_EVENT_LOAD_LIMIT.

 the account login will be blocked for an extended time period for security reasons (multiple failed logins). The report collection will fail and in addition. during which time it will not be possible for the user to log in to OMU. The alarm can be checked with the command ZAHP::NR=0199.. COMMAND EXECUTED 3 Check the progress of the collection on the RNC from the notification alarm 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION. D5C:B. There should be three alarm events during collection: Issue: 01E DN09203161 227 . Note: Do NOT delete the SOKERI account while RAN2872 report collection is ongoing. Procedure 1 Log in to the RNC MML console. In this case. or wait for the alarm 71106 TROUBLESHOOTING DATA RECEIVED to be raised on OMS. USE 'E' COMMAND TO CHECK THE STATUS. after recreating the SOKERI account. collects data according to the basic profile. both OMU login sessions can become occupied by running collection processes. Step result The execution printout should resemble the following: RNC IPA2800 2015-03-04 16:25:40 COLLECTING SYMPTOM DATA. the login delay must be reset by using the command ZIAQ:TYPE=MML. In the event that the SOKERI account is accidentally deleted during report collection. Select from available options • • D5C:S. These processes may take several minutes to finish due to the load. The typical error message will be that both sessions are already in use by the SOKERI account and the CBYPRB process. leading to long delays or even failure the next time symptom report data is collected. the user must wait until the RAN2872 process is completed before logging in. The notification alarm 0199 is raised to indicate the progression of the symptom report collection. This will reset the internal security mechanism for protecting against login attacks.    WCDMA 16 Feature Descriptions and Instructions g g Operability features Note: If the RAN2872 log collection is performed under high CPU load. collects data according to the standard profile. 2 Trigger the data collection using the D5C command.

 and try the command again. the network element will raise the alarm 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED if an error occurs during collection or upload of the symptom report. /*** SOKERI ACCOUNT DOES NOT EXIST ***/ The SOKERI account should be created before the symptom report can be collected. TRY AGAIN LATER ***/ A second symptom data collection was attempted while the first is ongoing.zip.XML NULL NULL • Collection finished and stored to disk HST (07636) IPA2800 EQUIPM 04 09:33:27. /*** COLLECTION REQUEST REJECTED DUE TO SYSTEM OVERLOAD.54 NOTICE NONE 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION LCHPRO OMU-0 NMS RNCBASIC. Result The Symptom report is stored on the RNC hard disk in the location /eclipse/var/symptom/ with a name in the format SYMPxxxx. Wait until the load drops below this level to start the command. ***/ Symptom data collection does not start when the CPU load is over 80%.    Operability features WCDMA 16 Feature Descriptions and Instructions • Collection started HST (07633) IPA2800 EQUIPM 04 09:29:42.ZIP 2015-06- The OMS alarm is raised when the collection process has finished and the symptom report is uploaded successfully.02 NOTICE NONE 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION LCHPRO OMU-0 NMS RNCBASIC.XML NULL SYMP0468.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_<NE>_<RNC-ID>.<date-time>. Error messages • • • /*** COLLECTION IS ONGOING.40 NOTICE NONE 0199 SYMPTOM DATA COLLECTION STATUS NOTIFICATION LCHPRO OMU-0 NMS RNCBASIC. Wait until the current collection finishes. 228 DN09203161 Issue: 01E .XML SYMP0468 NULL • 2015-06- 2015-06- Symptom report uploaded to OMS HST (07637) IPA2800 EQUIPM 04 09:33:57. In addition to the error message.

 allowing operators to filter the existing KPIs based on cell type.3 RAN3063 System impact Interdependencies between features There are no interdependencies between features. and optimize network performance based on the cell type through prime KPI values. 6. 6.    WCDMA 16 Feature Descriptions and Instructions Operability features 6.7.7. This introduces OPEX saving. Additionally. as an alternative.1 RAN3063 Benefits End-user benefits This feature does not affect the end-user experience. Impact on interfaces This feature has no impact on interfaces. or any other type of low power level node (LPN) from the current macro cells.7 RAN3063: KPI Reporting Based on Cell Type Introduction to the feature The RAN3063: KPI Reporting Based on Cell Type feature provides a new cell classification type identification to the RNC. 6. 6. This classification can be used later to identify those cells that need special actions from either system or operability point of view. Operator benefits With the RAN3063: KPI Reporting Based on Cell Type feature.4 RAN3063 Reference data Requirements Issue: 01E DN09203161 229 . Impact on system performance and capacity This feature has no impact on system performance or capacity. manage. pico.2 RAN3063 Functional description The RAN3063: KPI Reporting Based on Cell Type feature introduces a new BTS cell classification identification type to the RNC to identify the micro. 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.7.7. Impact on network and network element management tools This feature has no impact on network and network element management tools. customers are now able to define their own criteria for cell type classification. Customers can analyze. when the cell type can be identified unambiguously.

Key performance indicator There are no key performance indicators related to this feature. Counters There are no counters related to this feature. Alarms There are no alarms related to this feature. Sales information Table 97 RAN3063 Sales information BSW/ASW ASW SW component RAN License control in network element RNC LK 6. Parameter Table 96 New parameters introduced by RAN3063 Full name Cell Type Abbreviated name CellType Managed object WCEL Commands There are no commands related to this feature.    Operability features WCDMA 16 Feature Descriptions and Instructions Table 95 RAN3063 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 RNC16 mcRNC16 OMS NetAct WCDMA OMS16 NetAct 16. 230 DN09203161 Issue: 01E .5 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.7.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS Support not required Support not required Support not required MSC SGSN MGW UE Support not required Support not required Support not required Support not required There are no hardware requirements for this feature.

7. The feature code for this feature is 5574. Use the following commands: • • 2 for IPA-RNC : ZW7M:FEA=5574:ON. for mcRNC: set license feature-mgmt code 0000005574 feature-adminstate on Modify CellType parameter to a predefined value or user defined value. Before you start The RAN3063: KPI Reporting Based on Cell Type feature is activated. Issue: 01E DN09203161 231 .    WCDMA 16 Feature Descriptions and Instructions Operability features Procedure 1 Set the feature state to ON.6 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. 6. Make sure that you have access to NetAct Performance Manager.

DN09203161 Issue: 01E .    Operability features WCDMA 16 Feature Descriptions and Instructions 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. and filter the output by cell type. click Cell Type and then click > to transfer on the Aggregation pane. Figure 24 g 232 Configuration management selection window Note: You can select Filtering to see available values.

Use the following commands: • • for IPA-RNC: ZW7M:FEA=5574:OFF. the information available on the problem ticket is inadequate and delays the solution. Procedure 1 Modify CellType parameter to "Not_defined". The feature code for this feature is 5574. for mcRNC: set license feature-mgmt code 0000005574 feature-adminstate off 6.    WCDMA 16 Feature Descriptions and Instructions 3 Edit time selection 4 Edit KPI/counter selection 5 Select KPI > Preview Report 6 Generate Report g Operability features Note: In order to have the cell type available in reporter. Given that the RNC software is large and complex. 6. 2 Set the feature state to OFF.7. Before you start The RAN3063: KPI Reporting Based on Cell Type feature is activated.8 RAN3150: mcRNC Event Based Symptom Data Collection The RAN3150: mcRNC Event Based Symptom Data Collection feature introduces event based symptom data collection in the mcRNC. Issue: 01E DN09203161 233 . fault tracking and troubleshooting take considerable time. Reporting Suites WCDMA 16 package should be installed. Most often.7 Deactivating RAN3063: KPI Reporting Based on Cell Type Purpose Follow this procedure to deactivate the 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: RNW counters. Operator benefits Operators benefit from faster troubleshooting. master syslog writing or DMX message. DN09203161 Issue: 01E . The feature also provides an easier and faster means for symptom-data collection from customer sites. Figure 25: High level overview of the HIT base Fishing macro in mcRNC16 is the overview of this feature. With this feature.    Operability features WCDMA 16 Feature Descriptions and Instructions 6.1 RAN3150 Benefits End-user benefits This feature does not affect the end-user experience. the mcRNC automatically collects the symptom data related to a failure event based on the user's selected or predefined filter conditions. 6.8.2 RAN3150 Functional description The RAN3150: mcRNC Event Based Symptom Data Collection feature helps overcome the hurdles of the large RNC software and its complexity. mcRNC (RNW and platform) alarms.8. select the required symptom data among: – – – – g 234 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.

 There would not be any impacts to WBTS connectivity from the mcRNC. the latter request is rejected as a multi session for the user plane message monitoring. Impact on commands There are no commands related to this feature. The mcRNC must be reserved before running this feature or another SCLI monitoring session. Impact on network and network element management tools There are no impact on network and network element management tools. monitoring is be paused in the impacted unit. 6. but there would be an increase in rejection of new RRC connection requests. meaning that there would not be any unit or system restarts. If there is a user plane resource unit common between RAN3150 and RAN973. As a result. Impact on system performance and capacity Relative increase in USPU/CSPU Linux CPU load at base load of around 68% is at around 10. User Plane Monitoring is resumed when the overload situation has been rectified. Control Plane message monitoring shall continue. see TN38 available in Product Information Center.8. g Note: For User Plane monitoring initiated by this feature. This feature does be not impact the stability of the system. Impact on interfaces This feature has no impact on interfaces.14%.8.    WCDMA 16 Feature Descriptions and Instructions Operability features For more information on using the HIT based fishing macro. 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. 6.3 RAN3150 System impact Interdependencies between features This feature is interdependent with RAN2973: Enhanced IMSI based call monitoring. an impact is seen on related KPIs from the overloaded Control Plane units. upon detection of overload is detected. when this feature is active on an overloaded unit. Instead. 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.4 RAN3150 Reference data Reference Issue: 01E DN09203161 235 .

Alarms There are no alarms related to this feature. Sales information Table 99 RAN3150 Sales information BSW/ASW SW component BSW RAN License control in network element - 6. Parameters Call acceptability related KPIs are impacted if Control Plane units being monitored are overloaded.    Operability features WCDMA 16 Feature Descriptions and Instructions Table 98 RAN3150 hardware and software requirements RAS IPA-RNC WCDMA 16 OMS mcRNC Planned for later releases NetAct Support not required mcRNC16 Flexi Multiradio BTS Support not required MSC Support not required Support not required Flexi Multiradio 10 BTS Support not required SGSN Support not required Flexi Lite BTS Support not required MGW Support not required UE Support not required There are no hardware requirements for this feature. Operator benefits This feature benefits the operator as follows: 236 DN09203161 Issue: 01E .9 RAN2991: Modification of WCDMA Frequency The RAN2991: Modification of WCDMA Frequency feature 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.9. Counters There are no counters related to this feature. 6.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. Key performance indicator There are no key performance indicators related to this feature.

2 CM Editor Help in Send to network chapter. and delete managed objects without the need to create an RNW plan in the CM editor. 6. The BTS is capable of changing the cell frequency without a BTS reset. see NetAct 16. All the cells within the BTS from the frequency layer have been modified. Frequency refarming requires the modification of the cell frequency. or if a failure occurs during the activation of the frequency changing plan. modify. Issue: 01E DN09203161 237 . g Note: The modification of frequency by Send to Network option is not supported in NetAct. For more information. This feature introduces a faster implementation of cell frequency modification. This feature enables the cell frequency as a modifiable parameter in the RNC. For instance. The modification of cell frequency in RAN2991: Modification of WCDMA Frequency feature is possible only in the following conditions: • • • • g Cell frequency changes are within the same frequency band. The RAN2991: Modification of WCDMA Frequency feature supports the change of cell frequency without the need of BTS reset that leads to lesser BTS outages and disturbances to the traffic. This means that the Direct Activation (DA) operation cannot be used in modifying the cell frequency. The Send to Network feature enables operator to create.2 RAN2991 Functional description Operators perform frequency refarming yearly for more efficient use of the existing frequency spectrum. Operators are able to modify the cell frequency using the NetAct Configurator. Cell frequency changes are within the radio hardware frequency capability. NetAct also provides the notification if the requested task has been successful.9. 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.    WCDMA 16 Feature Descriptions and Instructions • • • Operability features This feature does not require BTS reset and therefore. Note: Other technology RF sharing cells (other than RF sharing WBTSs) experience temporary disturbances during the implementation of cell frequency changes. reduces the number of BTS outages when operators are performing frequency modification activity. Frequency refarming is the reallocation of regulated radio frequency spectrum to another use. 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. describes how RAN2991: Modification of WCDMA Frequency feature works. the existing 2G frequency bands are to be used in 3G or LTE.

 All the consistency checks must be satisfied and if the validations fail. During the RNW configuration plan download. The BTSs using older than WN8. 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 RNC reports the errors to NetAct and aborts the operation. For those BTSs. 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 a BTS reset? The BTS indicates the feature support by setting the Cell Frequency Change Without Reset capability in NBAP: CAPABILITY INDICATION message and sends this message to the RNC.0 SW build are capable to support the frequency change but are incapable to report Cell Frequency Change Without Reset capability.    Operability features WCDMA 16 Feature Descriptions and Instructions Figure 26 Frequency modification workflow NetActConfigurator CMEditor Operatorcreatesthe RNWplan RNC CMOperation Management Operatorinitiatesthe downloadofRNWplan Notifyoperator operationabort BTS DownloadRNWplan Downloadfails:errorreport Consistencycheck:OK Notifyoperator operationabort Validationfails:errorreport RNWplandownloaded Operatorselectsthe RNWplancommands Activationrequest Activation Notifyoperator operationabort RNWconfiguration modification BTSdoesnot incurreset Activationfails:errorreport Operationsuccessful Report The operator creates the radio network (RNW) configuration plan for changing the cell frequency using the NetAct planning tool CM Editor. the RNC reports the error to NetAct and the operation is aborted. But if the download fails. Consistency Check Rule Mask parameter with BTS Frequency 238 DN09203161 Issue: 01E . the operator initiates the RNW configuration plan download to the network elements using NetAct CM Operations Manager.

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 operator can select the activation mode of RNC RNW plan by means of optional features such as Object by Object (Slow). In case of a misconfiguration. Check the configuration of the local cells on the BTS side before trying to merge the frequency layer of the existing cells. Send CM events to NetAct for each change that has been made. Note: If the activation fails. The Consistency Check Rule Mask parameter defines the functionalities that are allowed to be used bypassing the corresponding consistency check rule for the function. g Note:  The BTSs using equal or newer than WN8. the RNC reports the errors to NetAct and the operation is aborted. 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.    WCDMA 16 Feature Descriptions and Instructions Operability features Change Allowed capability is introduced. Service impact level for RNC plan activation and RAN212: Selectable RNW Plan Activation Mechanism feature.2 CM Operations Manager Help in Provisioning plans. Setting BTS Frequency Change Allowed capability in Consistency Check Rule Mask parameter for those BTSs might cause unnecessary disturbances to the end user traffic. the misconfigured cell must be deleted and then recreated with the correct UARFCN. For more information. BTS Frequency Change Allowed capability allows the frequency change. Thus. 6. the RNC performs the following tasks: • • • g Lock and unlock each cell while performing the RNW configuration changes. even though the BTS does not report the Cell Frequency Change Without Reset capability to the RNC. The BTS performs the RNW configuration modifications and changes the value of the defaultCarrier parameter based on the UARFCN. see NetAct 16. The RNC receives the activation command and activates the RNW configuration plan. Use Activation Groups (Moderate). 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 Reset bit in NBAP: Capability Indication message. All Objects Parallel(Fast). During the activation. Distribute the RNW configuration changes to the BTSs.9. However. the merging of frequency layers is not recommended.0 SW build but older than WBTS16 SW build are incapable to support the frequency change without reset. Impact on network and network element management tools Issue: 01E DN09203161 239 . Ensure the cells that share the same antennas are configured with a different frequency layer.3 RAN2991 System impact Interdependencies between features There are no interdependencies between any other features.

Parameters Table 101 Existing parameters related to RAN2991 Full name Abbreviated name Network element Managed object UTRA Absolute Radio Frequency Channel Number UARFCN RNC WCEL Default carrier defaultCarrier BTS LCELW Consistency check rule mask ConsCheckRuleMas RNC k WBTS Commands There are no commands related to this feature.9. Sales information 240 DN09203161 Issue: 01E . Measurements and counters There are no new measurements or counters related to this feature.4 RAN2991 Reference data Requirements Table 100 RAN2991 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS WCDMA 16 RNC16 mcRNC16 WBTS16 WBTS16 OMS NetAct MSC SGSN MGW UE Support not required NetAct 16.2 Support not required Support not required Support not required Support not required Not planned This feature does not require additional hardware. Key performance indicators There are no key performance indicators related to this feature. 6. Impact on system performance and capacity There are no impacts on system capacity for this feature. Alarms There are no alarms related to this feature.    Operability features WCDMA 16 Feature Descriptions and Instructions There are no impacts on the network and network element management tools for this feature.

2 Download the RNW plan to the network elements with CM Operations Manager. The BTS is connected to OMS and NetAct. The plan should fulfill the feature limitations. Issue: 01E DN09203161 241 . The frequency and cell adjacency is modified consistently. The configuration and parameter settings described are only examples and they can vary in different networks.    WCDMA 16 Feature Descriptions and Instructions Table 102 Operability features RAN2991 Sales information BSW/ASW ASW NetAct SW component RAN License control in network element NetAct 6. Before you start The following are the equired test environment and settings: • • • • • The Radio Access Network (RAN) and Operational Core network (CN) are operational.5 Testing RAN2991: Modification of WCDMA Frequency Purpose This test case verifies that BTS restart. 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 shall be within the same frequency band. • • • • • g Note: Other technology RF sharing cells will experience an outage when performing cell frequency changes for RF sharing WBTSs. The BTS configuration is F222 or F333. The RF module is FXDA for 900MHz or FRGT/FRGP for 2100MHz. g Note: This is an example of the verification. The cell frequency changes are within the radio hardware frequency capability. do not use it for the feature as such in a live network. or import the RNW plan with CM Operations Manager from an external source. The RNC validates the downloaded RNW plan. deletion. Procedure 1 Create the RNW plan for changing the cell frequency (UARFCN) with CM Editor. The system module is rel2 or rel3. All the cells within the BTS from the frequency layer are modified. The BTS is capable of changing the cell frequency without a BTS reset.9.

Result Expected result: The cell frequency is modified without the need of BTS restart. Operator benefits 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. 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).1 RAN2268 Benefits End-user benefits This feature does not affect the end-user experience. and the deletion/creation of cells. DN09203161 Issue: 01E . If no Vendor certificate available. 6. 6. The common rules for certificates and the enrolment of operator BTS certificates follow 3GPP Release i11 "TS 33. the CMP messages are signed by an RA acting as gatekeeper in front of the signing CA. 3GPP compliant life cycle management allows a harmonized networkwide and inter-RAT handling. although the certificate is issued and signed by a CA. which leads to considerable OPEX reductions.310 Network Domain Security - Authentication Framework": • • 242 The BTS uses the vendor certificate for initial authentication to CA.10 RAN2268: Multi-Layer Certificate Authorities Introduction to feature The RAN2268: Multi-Layer Certificate Authorities feature brings WCDMA BTS to parity with LTE eNB in terms of certificate management.10. The BTS supports CMP message signing by an RA. This feature applies to WBTS Flexi. 6.2 RAN2268 Functional description The RAN2268: Multi-Layer Certificate Authorities feature 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.10. then the NB is able to use PSK/Refnum if it was pre-configured by the operator. in case the certificate lifetime is close to expire.    Operability features WCDMA 16 Feature Descriptions and Instructions 3 Select and activate the RNW plan in CM Operations Manager. that is. NetAct notifies that the operation is successful.

 the BTS sends an alarm to NetAct whena trust anchor a cross-certificate is close to expire. Thus. With the NetAct CERMA tool. for a certain time. The signing CA key length can be 2048. 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. If the trust relation is established either by a second trust anchor or a cross-certification. 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. Nevertheless. Issue: 01E DN09203161 243 . Trust Anchor and Cross-signed certificate enrolment for BTS The BTS supports the integration of a second operator PKI. the operator is able to trigger for all or a list of BTS the certificate initialization and key update and trust anchor removal. the operator can now add a trust anchor or cross-signed CA certificate manually via the BTSSM. If notified. either individual per BTS or with NetAct scripting for a list of BTS. 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. 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. The BTS applies the same pre-warning time value as used for the own CA signing certificate expiry supervision. 4096. or 8192 bit. The BTS does not remove trust anchors or expired cross-signed certificates autonomously. 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. The available trust anchor or cross-signed certificate is not automatically removed to allow a smooth migration to a new trust relation. 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. 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.    WCDMA 16 Feature Descriptions and Instructions • • Operability features SHA-1 and SHA-256 are supported as hash algorithms for certificate signs. 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.

10.3 RAN2268 System impact Interdependencies between features The RAN2268: Multi-Layer Certificate Authorities feature enhances the network element certificate management feature family. the BTS supports configurable CRL sources. 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.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS WBTS16 WBTS16 Not planned MSC SGSN MGW UE Support not required Support not required Support not required Support not required There are no hardware requirements for this feature. The parameters can be set with the element mangers and NetAct Configurator. Alarms 244 DN09203161 Issue: 01E . Impact on network and network element management tools There is no impact on network and network element management tools.    Operability features WCDMA 16 Feature Descriptions and Instructions To extend the revocation checks in addition to the existing CRL handling of the own certification path. Impact on system performance and capacity There is no impacts on system performance and capacity.4 RAN2268 Reference data Requirements Table 103 RAN2268 hardware and software requirements RAS IPA-RNC mcRNC WCDMA16 Planned for later releases Planned for later releases OMS NetAct WCDMA OMS16 NetAct 16. The BTS offers up to 10 primary and 10 secondary CRLDP entries. 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.10. 6. which can be configured for LDAP download individually as static IP address with path to directory or FQDN with path to directory. 6.

Sales information Table 105 RAN2268 Sales information BSW/ASW SW component BSW RAN License control in network element - 6. to replace the HP Proliant Gen8 server. Operator benefits This feature provides better performance as compared to Gen8.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.11.    WCDMA 16 Feature Descriptions and Instructions Table 104 Operability features New alarms introduced by RAN2268 Alarm ID Alarm name Description 61618 BTS Trust Anchor expired or due to expire This alarm is set when all trust anchor certificate lifetime below a configurable time or its own trust anchor is expired 61074 CRL Update Failure This alarm is raised if the BTS cannot update any of the certificate revocation list. 6. Gen9 uses less time for event handling and task processing commanded by NetAct. Commands There are no commands related to this feature. It also makes OMS less sensitive to unexpected and extremely high overload situations. Key performance indicators There are no KPIs related to this feature. For more details.1 RAN3096 Benefits End-user benefits This feature does not affect the end-user experience. An update of the CRL is attempted on request of the operator. Thus. Issue: 01E DN09203161 245 . Network management works faster end to end. see HP Proliant DL360 Gen9 and HP Proliant BL460c Gen9 in OMS Product Description. Parameters There are no parameters related to this feature. Counters There are no counters related to this feature. particularly the HP Proliant Gen9 blade and rack servers.

3 RAN3096 System impact Interdependencies between features There are no interdependencies between this and any other feature.11. Impact on system performance and capacity This feature has no impact on system performance or capacity. standalone OMS HW can be replaced with the new HP ProLiant DL360 Gen9 and HP ProLiant BL460c Gen9. as in Gen8 and G6) – – – – • Server model: BL460c (blade) 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) – – – – 6.2 RAN3096 Functional description With the RAN3096: OMS HP Gen9 HW feature. 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 are used.4 RAN3096 Reference data Requirements Table 106 RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Multiradio 10 Flexi Lite BTS WCDMA 16 Support not required Support not required Support not required Support not required Support not required NetAct MSC SGSN MGW UE Support not required Support not required Support not required Support not required Support not required OMS WCDMA OMS16 246 RAN3096 hardware and software requirements DN09203161 Issue: 01E .    Operability features WCDMA 16 Feature Descriptions and Instructions The OMS connectivity remains the same as with Gen8 HW. Impact on interfaces This feature has no impact on interfaces.11. 6. 6.11. Impact on network and network element management tools This feature has no impact on network management tools.

 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. Done and missed configurations can be identified much faster thus.1 RAN2702 Benefits End-user benefits This feature does not affect the end-user experience. With the SIEM system. 6.    WCDMA 16 Feature Descriptions and Instructions Operability features This feature requires the HP Proliant DL360 Gen9 and HP Proliant BL460c Gen9. Sales information Table 107 RAN3096 Sales information BSW/ASW SW component BSW RAN License control in network element - 6. 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. Parameters There are no parameters related to this feature.2 RAN2702 Functional description The RAN2702: Parameter Level Logging of BTS User Events feature adds parameter level details to the RUEM log for user requests initiated from the BTS Site Manager.12. the user can then view the details on the Security Information and Event Management (SIEM) system. Alarms There are no alarms related to this feature. and execution status. limiting network problems or even network outages. and parameter value to be. Key performance indicators There are no key performance indicators related to this feature. User requests initiated from the BTS Site Manager Issue: 01E DN09203161 247 . 6. Measurements and counters There are no measurements or counters related to this feature. parameter value.12 RAN2702: Parameter Level Logging of BTS User Events Introduction to the feature The RAN2702: Parameter Level Logging of BTS User Events feature is an enhancement to remote user event log management (RUEM) for the BTS.12. an operator can audit configuration changes done by the BTSSM with enhanced details of parameter name.

    Operability features WCDMA 16 Feature Descriptions and Instructions Parameter level details of this type of request and the corresponding response are added to the RUEM log. 248 Figure 27 RUEM Log File Format Figure 28 SIEM system GUI DN09203161 Issue: 01E . such as SiteConf files. those changes are not recorded in RUEM log. can be downloaded from BTS Site Manager. Requests and corresponding responses are correlated. parameter's level details are added to RUEM log. for example. For the user requests and responses that are currently logged. Configuration files. When activated. they introduce many configuration changes to the BTS. A RAML Request contains multiple operations on multiple objects and parameters. Parameter details typically include parameter name and parameter value it would be changed into. Execution failures related to the configuration files are logged in other type of logs. However. RAML Request. A single RUEM log entry generated for each operation and targeting object pair. thus excluded from this feature. Some requests also include object name. The user can retrieve the configuration files from the BTS Site Manager to get details. The operations impacting BTS configuration or service are logged along with the targeting objects and parameters.

Impact on interfaces This feature has no impact on interfaces.12. the amount of logs to be uploaded from the BTS to NetAct are expected to increase. There are no performance degradation in NetAct. Measurements and counters There are no measurments and counters related to this feature.    WCDMA 16 Feature Descriptions and Instructions Operability features 6. Parameters There are no parameters related to this feature. or the communication between the two. But BTS and NetAct must have enough capacity to support the additional memory space. Additional memory space and processing time on the BTS and NetAct needs to be allocated to handle the extra parameter level logging. 6. Alarms There are no alarms related to this feature.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS WBTS16 WBTS16 Not planned MSC SGSN MGW UE Support not required Support not required Support not required Support not required There are no hardware requirements for this feature.12.4 RAN2702 Reference data Requirements Table 108 RAN2702 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 Support not required Support not required OMS NetAct Support not required NetAct 16.3 RAN2702 System impact Interdependencies between features This feature is an enhancement to RU10 RAN616: Centralised User Event Log Management for BTS feature. Commands Issue: 01E DN09203161 249 . the BTS. Impact on system performance and capacity With the additional parameter level details. Key performance indicators There are no KPIs related to this feature. This would result in more frequent upload of logfiles and the average logfile size also increases. Impact on network and network element management tools This feature has no impact on network and network element management tools.

Sales information Table 109 RAN2702 Sales information BSW/ASW SW component License control in network element ASW NetAct RAN - 6. The following are the required software: • • • • • RNC16 NetAct 16. Before you start The following are the required test environment: • • Operational Radio Access Network and Core Network FSMr2 or FSMr3 platform. 2 In BTS Site Manager perform basic actions.12.2 OMS16 WBTS16 Audit Trail16 Procedure 1 Enable Automatic RUEM files uploading to Audit Trail. Result Every action perfomed in BTS Site Manager should be visible in Audit Trail. 5 Disable Automatic RUEM DB files uploading to Audit Trail. 4 Open NetAct Audit Trial and confirm if perfomed actions were logged. for example enable/disable SSH.5 Testing RAN2702: Parameter level logging of BTS user events Purpose The purpose of this test is to verify if the RAN2702: Parameter level logging of BTS user events feature is activated and working correctly.    Operability features WCDMA 16 Feature Descriptions and Instructions There are no commands related to this feature. 250 DN09203161 Issue: 01E . 3 Wait for about two to three hours.

The purpose is to mitigate security vulnerabilities identified in TLS 1. This feature does not change the cipher suites on the RNC.    WCDMA 16 Feature Descriptions and Instructions g Operability features Note: Reboot BTS and Recover BTS are not logged in RUEM logs when BTS resets happens quickly before the log can be written. OMS. Additionally.2.2 RAN2571 Functional description The RAN2571: Support of TLS 1.2. Issue: 01E DN09203161 251 . 6.310. To support backward compatibility.13. OMS Element Manager.2.2 feature enhances the Transport Layer Security Protocol (TLS) support on the network elements in WCDMA RAN and other related tools.13. so that they are compliant with the regulations specified in 3GPP Release 12 TS 33. Prior to this feature. BTS. and BTSSM. and BTSSM are installed with a list of stronger cipher suites. OMS Element Manager. OMS. OMS Element Manager.13 RAN2571: Support of TLS 1. this feature keeps the cipher supported on OMS. Some of the ciphers in the list of stronger ciphers proposed by this feature are already supported on the RNC prior to this feature.1 and TLS 1. The 3GPP Release 12 requires the TLS end points to support TLS 1. watchdog reset.2. Prior to this feature. Some of those ciphers support Forward Secrecy. instead. the mandatory cipher for TLS 1. and the stop of use of cipher suites with RC4. system crash.2 Introduction to the feature As the support of TLS 1.1 and TLS 1.2 is now used as the default protocol together with the cipher suites specified for TLS 1.2. 6. TLS 1. the network elements in RAN support only TLS 1. Linux reboot. TLS_RSA_WITH_RC4_128_SHA cipher is used for file transfer on some interfaces. 3GPP Release 12 requires TLS end points to support TLS 1.310. This also happens if the BTS is in a state that prevents writing of RUEM log. Operator benefits The Flexi Multiradio BTS is compliant with 3GPP security recommendation. With the changes on OMS and BTS. 6.1 RAN2571 Benefits End-user benefits This feature does not affect the end-user experience.0 when needed to be compliant with release backward compatibility.2 support. The new version fixes well known TLS/SSL MAC security flaw vulnerabilities. but with lowest priority. This feature also improves the security of RAN system by using stronger ciphers for TLS connections. The RNC remains unchanged in this feature.0. In this feature. their interfaces to the RNC no longer use RC4 cipher. for example. and the mandatory cipher specified in 3GPP Release 12 TS 33. so the RNC only supports TLS 1. of one of the stronger ciphers is used. BTS. that is.1 and TLS 1. They continue to support TLS 1. requiring TSL 1.2 without compression. BTS.0.2 in RFC5246. In this feature. The 3GPP Release 12 also requires the TLS end points to support the cipher suites mandatory to TLS 1.1 in RFC4346. including the mandatory cipher for TLS 1.0 and remedied in TLS 1. and BTS Site Manager (BTSSM) are upgraded to support TLS 1.0 is discontinued by 3GPP Rel 9. and so on.

 and SIMO BTS are out of scope.3 RAN2571 System impact Interdependencies between features There are no interdependencies between features.2 feature covers Flexi BTS on FSMr3 platform.    Operability features WCDMA 16 Feature Descriptions and Instructions CompressionMethod. BTS on FSMr1 or FSMr2.13.null. 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. 6. Flexi Lite BTS. and Flexi Zone Pico BTS. Table 110: Ciphers in priority is 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. UltaSite BTS. This feature is also supported for the following interfaces for the OMS: 252 DN09203161 Issue: 01E . Table 110 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 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.

Alarms There are no alarms related to this feature. Key performance indicators There are no KPIs related to this feature. Impact on system performance and capacity This feature has no impact on system performance or capacity. Commands There are no commands related to this feature. Measurements and counters There are no measurements and counters related to this feature.4 RAN2571 Reference data Requirements Table 111 RAN2571 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 Planned for later releases Planned for later releases OMS NetAct WCDMA OMS16 NetAct 16. 6. Parameters There are no parameters related to this feature. Sales information Table 112 RAN2571 Sales information BSW/ASW BSW Issue: 01E SW component RAN DN09203161 License control in network element - 253 .13.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS Not planned WBTS16 Not planned MSC SGSN MGW UE Support not required Support not required Support not required Support not required There are no hardware requirements for this feature.    WCDMA 16 Feature Descriptions and Instructions • • • • • • Operability features HTTPS interface between NetAct and OMS HTTPS interface between NE and OMS BTSOM interface between NE and OMS HTTPS interface between OMS AL based element manager and OMS COBRA interface between OMS 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 interfaces This feature has no impact on interfaces. .1. 7.3 RAN2164 System impact Interdependencies between features There are no features interdependent with RAN2164: Compensated CQI Measurement. see Measurements and counters.1.. For the detailed counter list. 7.1. 7. The BTS gives a maximum throughput for sophisticated UEs when compensated CQI values 31. Impact on system performance and capacity This feature has no impact on system performance and capacity.2 RAN2164 Functional description RAN2164: Compensated CQI Measurement feature introduces the HSPA in WBTS extension counter group.. The retrieved measurement reports are used to optimize the HSDPA scheduler algorithm in the BTS. CLASS 35).1. 7. This feature compensates the reported CQI for the distortion caused by the RAN1224: HSDPA Dynamic Power Allocation feature. Operator benefits This feature brings OPEX savings via reduced manual activity in investigating radio performance because of dedicated counters for compensated CQIs.4 RAN2164 Reference data Requirements 254 DN09203161 Issue: 01E .1 RAN2164 Benefits End-user benefits This feature does not affect the end-user experience.35 are used (raw values are only from 0…30). CLASS 1. Impact on network and network element management tools This feature has no impact on network and network element management tools.. This counter group consists of 36 Compensated CQI distribution class counters (COMPENSATED CQI DISTRIBUTION-CLASS 0.1 RAN2164: Compensated CQI Measurement Introduction to the feature RAN2164: Compensated CQI Measurement feature 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.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions 7 Performance monitoring features 7.

2 Support not required Support not required Support not required Support not required This feature requires no new or additional hardware. Alarms There are no alarms related to this feature.    WCDMA 16 Feature Descriptions and Instructions Table 113 Performance monitoring features RAN2164 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 RNC16 mcRNC16 WBTS16 WBTS16 Not planned OMS NetAct MSC SGSN MGW UE Support not required NetAct 16. Measurement and counters Table 114 Issue: 01E New counters introduced by RAN2164 Counter ID Counter name Measurement M5005C0 COMPENSATED CQI DISTRIBUTION - CLASS 0 HSPA in WBTS Extension M5005C1 COMPENSATED CQI DISTRIBUTION - CLASS 1 HSPA in WBTS Extension M5005C2 COMPENSATED CQI DISTRIBUTION - CLASS 2 HSPA in WBTS Extension M5005C3 COMPENSATED CQI DISTRIBUTION - CLASS 3 HSPA in WBTS Extension M5005C4 COMPENSATED CQI DISTRIBUTION - CLASS 4 HSPA in WBTS Extension M5005C5 COMPENSATED CQI DISTRIBUTION - CLASS 5 HSPA in WBTS Extension M5005C6 COMPENSATED CQI DISTRIBUTION - CLASS 6 HSPA in WBTS Extension M5005C7 COMPENSATED CQI DISTRIBUTION - CLASS 7 HSPA in WBTS Extension M5005C8 COMPENSATED CQI DISTRIBUTION - CLASS 8 HSPA in WBTS Extension M5005C9 COMPENSATED CQI DISTRIBUTION - CLASS 9 HSPA in WBTS Extension M5005C10 COMPENSATED CQI DISTRIBUTION - CLASS 10 HSPA in WBTS Extension M5005C11 COMPENSATED CQI DISTRIBUTION - CLASS 11 HSPA in WBTS Extension M5005C12 COMPENSATED CQI DISTRIBUTION - CLASS 12 HSPA in WBTS Extension M5005C13 COMPENSATED CQI DISTRIBUTION - CLASS 13 HSPA in WBTS Extension DN09203161 255 .

    Performance monitoring features Table 114 WCDMA 16 Feature Descriptions and Instructions New counters introduced by RAN2164 (Cont.) Counter ID Counter name Measurement M5005C14 COMPENSATED CQI DISTRIBUTION - CLASS 14 HSPA in WBTS Extension M5005C15 COMPENSATED CQI DISTRIBUTION - CLASS 15 HSPA in WBTS Extension M5005C16 COMPENSATED CQI DISTRIBUTION - CLASS 16 HSPA in WBTS Extension M5005C17 COMPENSATED CQI DISTRIBUTION - CLASS 17 HSPA in WBTS Extension M5005C18 COMPENSATED CQI DISTRIBUTION - CLASS 18 HSPA in WBTS Extension M5005C19 COMPENSATED CQI DISTRIBUTION - CLASS 19 HSPA in WBTS Extension M5005C20 COMPENSATED CQI DISTRIBUTION - CLASS 20 HSPA in WBTS Extension M5005C21 COMPENSATED CQI DISTRIBUTION - CLASS 21 HSPA in WBTS Extension M5005C22 COMPENSATED CQI DISTRIBUTION - CLASS 22 HSPA in WBTS Extension M5005C23 COMPENSATED CQI DISTRIBUTION - CLASS 23 HSPA in WBTS Extension M5005C24 COMPENSATED CQI DISTRIBUTION - CLASS 24 HSPA in WBTS Extension M5005C25 COMPENSATED CQI DISTRIBUTION - CLASS 25 HSPA in WBTS Extension M5005C26 COMPENSATED CQI DISTRIBUTION - CLASS 26 HSPA in WBTS Extension M5005C27 COMPENSATED CQI DISTRIBUTION - CLASS 27 HSPA in WBTS Extension M5005C28 COMPENSATED CQI DISTRIBUTION - CLASS 28 HSPA in WBTS Extension M5005C29 COMPENSATED CQI DISTRIBUTION - CLASS 29 HSPA in WBTS Extension M5005C30 COMPENSATED CQI DISTRIBUTION - CLASS 30 HSPA in WBTS Extension M5005C31 COMPENSATED CQI DISTRIBUTION - CLASS 31 HSPA in WBTS Extension M5005C32 COMPENSATED CQI DISTRIBUTION - CLASS 32 HSPA in WBTS Extension M5005C33 COMPENSATED CQI DISTRIBUTION - CLASS 33 HSPA in WBTS Extension M5005C34 COMPENSATED CQI DISTRIBUTION - CLASS 34 HSPA in WBTS Extension M5005C35 COMPENSATED CQI DISTRIBUTION - CLASS 35 HSPA in WBTS Extension Key performance indicators 256 DN09203161 Issue: 01E .

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 for Cell_FACH state for mcRNC and IPA-RNC. end-user speech and data. is collected due to legal requirements. meaning that no end-user communication content. User and Transport planes for individual calls based on the specified IMSI numbers in IPARNC and mcRNC. Commands There are no commands related to this feature. the monitored data has very small size comparing to traditional methods of monitoring all calls in RNC.e. Typical use cases for troubleshooting individual calls include (based on 3GPP TS 32. Note that the monitored data content is limited to protocol headers and signaling messages. Trace concepts and requirements): • • • • • • Multivendor UE validation: check how different vendor's UEs are working Subscriber complaint: check how the subscriber's services are working in order to find out the reason for the complaint Malfunctioning UE: when the operator suspects that a UE is not working according to the specifications Checking radio coverage on a particular geographical area Testing a new feature Fine-tuning and optimization of algorithms/procedures As the data is collected for monitored IMSI numbers only. RLC and MAC-d protocol headers are monitored in FACH. Parameters There are no parameters related to this feature. 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. where PDCP. Issue: 01E DN09203161 257 .    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features There are no key performance indicators related to this feature. i.421 Subscriber and equipment trace. This also allows much more extensive data content including data from User and Transport Planes. Sales information Table 115 RAN2164 Sales information BSW/ASW SW component BSW HSPA License control in network element - 7. This functionality allows operator to collect and analyze data from Control.

2.1 RAN2973 Benefits End-user benefits Faster resolution of subscribers' complaints. such as Wireshark and NetHawk. verification and optimization of call related issues in Control. 7.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions 7.2.2 RAN2973 Functional description Functional overview 258 DN09203161 Issue: 01E . Reduced need for external tracing equipment. Standard Windows PC hardware can support simultaneous monitoring in multiple RNCs. Operator benefits Remote and fast network troubleshooting. Transport and User Planes in mcRNC and IPA-RNC.

 nor messages related to any other call(s) (uninterested calls) is collected by this feature. User and Transport Plane monitored data. The data capturing is done with the help of the L3 Data Collector running on a standard Windows PC. 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 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.packetheaders RNC In IPA-RNC and mcRNC. and Transport planes monitoring data for individual calls based on given IMSI numbers. logs. and connected remotely to the monitored RNC. User. Issue: 01E DN09203161 259 . that is end-user speech and data. Note that neither end-user communication content. The L3 Data Analyzer has the capability of analyzing Control. this feature introduces collection of Control.    WCDMA 16 Feature Descriptions and Instructions Figure 29 Performance monitoring features Overview of RAN2973: IMSI-based Call Monitoring GEOinterface Extension option L3DC PS/CS Core IPA RNC/ mcRNC ControlPlane+User Plane+ Transport Plane:messages.

 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. only the last octet of the four is captured. The whole end-to-end TCP/UDP/ICMP header is monitored. User Plane in user plane processing units (DMPG/DSP in RNC2600. RTCP (not in RNC2600) and Iu-CS UP Figure 32 260 User Plane monitored data on Iu-CS interface DN09203161 Issue: 01E . Figure 30 User Plane monitored data on Iu-PS interface Figure 31 End-to end IPv4 packet TCP/UDP/ICMP Protocol headers on Iu-CS: RTP. Nothing is captured from the IPv4 packet payload. The same key is required for analyzing the monitored data at the L3 Data Analyzer tool. The other bits of the IP addresses are marked as zeroes in the monitoring data.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions 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. 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. From the source and destination IP addresses.

 minor and severe errors. RLC and PDCP Figure 33 • • 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). inner TCP/ICMP/UDP Figure 34 • • Iu-CS: IP/UDP/RTP/IuUP headers. exceptions 3. Note: RTCP monitored only in mcRNC. • Protocol headers on Iub: FP. IP/UDP/RTCP full packet Figure 35 Transport Plane monitored data on Iu-CS interface (RTP) (1 of 2) Figure 36 Transport Plane monitored data on Iu-CS interface (RTP) (2 of 2) Iub: IP/UDP/FP headers and MAC/RLC headers of the first PDU Figure 37 g Issue: 01E Transport Plane monitored data on Iu-PS interface Transport Plane monitored data on Iub interface Note: Tail only for DCH transport DN09203161 261 . MAC. UDP.    WCDMA 16 Feature Descriptions and Instructions g g Performance monitoring features Note: Only with CS Voice over HSPA. internal data (such as scheduling info). GTP-U. Transport Plane in transport plane processing units (NPGE in RNC2600. EITP in mcRNC): • Protocol headers on Iu-PS: outer IP. inner IP.

Operations causing high OMU load. 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.4 RAN2973 Reference data Requirements Software requirements Table 116 RAN2973 Software requirements RAS IPA-RNC mcRNC Flexi Multiradi o BTS Flexi Multiradio 10 BTS Flexi Lite BTS WCDMA 16 RNC16 mcRNC16 Support not required Support not required Support not required OMS NetAct MSC SGSN MGW Support not Support not Support not Support not Support not required required required required required 262 DN09203161 UE Support not required Issue: 01E .2.2. General Control Plane/User Plane monitoring using MML/SCLI can be performed in parallel with this feature 4. Impact on network and network element management tools No impact. 7. CPU loads on monitored units will increase to maximum 10%. can cause pausing of RAN2973 monitorings 2.3 RAN2973 System impact Interdependencies between features 1. Existing Megamon/L3Analyzer installed solution can be re-used. General Control Plane monitoring using L3 Data collector can be used in parallel with this feature in a different L3 Data collector session 3.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions Site configuration • • In RNC2600. In mcRNC. CPU loads of the monitored units can increase up to 10% (relative). General/ Event triggered Symptom report collection in mcRNC can be performed in parallel with this feature. it is required to install Ethernet switch onsite as the monitored data collection is done via one SFP port in each BCN box. 7. Impact on system performance and capacity No impacts to KPIs. the monitored data collection is performed via O&M connection to RNC. for example IPA-RNC symptom report collection or file compress/uncompress operations.

 No high performance server HW is required to support simultaneous motoring in multiple RNCs. The monitoring network is the same as used in general L3 Data Collector (Megamon) solution. a private monitoring network needs to be created. In mcRNC. allowing simultaneous usage of RAN2930/RAN2973 and general L3 Data Collector (Megamon) message monitoring.    WCDMA 16 Feature Descriptions and Instructions Table 117 Performance monitoring features External monitoring tool requirements Tool name Purpose Release Location 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 <ID>. Hardware requirements This feature requires external monitoring machine with standard Windows PC HW to run L3 Data Collector (Megamon) SW. Only calls created after monitoring is started can be monitored. General The number of IMSIs that can be monitored per RNC simultaneously is limited. User Plane monitoring cannot be started for branches of ongoing calls. This feature requires TCP/UDP ports 8020 and 8021 be enabled in the transport network. 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. For example. Issue: 01E DN09203161 263 . Transport requirements In IPA-RNC. 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. O&M interface is utilized to control and stream monitored data to remote L3 Data Collector (Megamon). 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 <ID>. where SFP21 or SFP22 ports (or both ports) of each mcRNC module and L3 Data Collector (Megamon) are interconnected via 1G Ethernet Switch. This feature requires at minimum 5 Mbps bandwidth to support the maximum amount of monitored calls.

 16: mcRNC Control Plane and Transport Plane 4: IPA-RNC (RNC2600). Transport Plane. 16: mcRNC Control Plane.1 7.5. see the appropriate Technical Support Solutions (TSS) in NOLS.2.5 Activating and configuring RAN2973: Enhanced IMSIbased Monitoring 7. Sales information Table 119 RAN2973 Sales information BSW/ASW SW component License control in network element ASW RAN RNC LK For external monitoring tool sales information (that is.2. mcRNC Control Plane and User Plane 4: IPA-RNC (RNC2600).5.1.1 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 264 DN09203161 Issue: 01E . and User Plane 4: IPA-RNC (RNC2600). Megamon and IMSIMon3G). 16: mcRNC Alarms There are no alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Parameters There are no parameters related to this feature.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions Table 118 Maximum number of calls that be monitored based on RNC and monitoring configuration Filter Maximum number of calls that can be monitored Control Plane only 16: IPA-RNC (RNC2600). 7. Key performance indicators There are no key performance indicators related to this feature.2.

Wait until port 8021 status shows LISTEN.0. ZQRS:OMU.002. use the following command: ZW7M:FEA=<feature code>:ON. 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 *.* If not displayed correctly.2 Installing licenses for IPA-RNC Procedure 1 To set the feature state to ON. Related descriptions Configuring GIVAXI/givClient on page 264 Backup Physical RNC System management on page 326 Related procedures Configuring GIVAXI/givClient on page 264 Deleting BPS fallback on page 414 Activating new BPS on BkPRNC (mcRNC) on page 408 Upgrading mcRNC SW builds and BPS on BkPRNC on page 406 Creating BPS fallback on page 404 7.5.1. It takes approximately 20 seconds.2.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features Procedure 1 Check Givaxi port status.8021 LISTEN Foreign Address *.2093. The following features need to be turned on: Issue: 01E DN09203161 265 . execute the following command: ZWOC:2.

1. This requires that the same PSK is administered in both the external monitoring tool and IPA-RNC. ENTER KEY(MAX 64 HEXADECIMAL DIGITS): 1234567890ABCDEFFEDCBA09876543211234567890ABCDEFFEDCBA0987654321 266 DN09203161 Issue: 01E .S:K:H:.5. 256bits/8=32 bytes so the key must be 32 bytes long. Step example >ZQ4A:GIVAXIPSK.2.3 Code Object Name Feature 0000005261 IMSI-based Call Monitoring SW Licence Key SI RU00552 IMSI-based Call Monitoring Test LK Software SI RU00551.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.    Performance monitoring features Table 120 WCDMA 16 Feature Descriptions and Instructions Licenses for RAN2973: IMSI-based Monitoring Type g 7.1.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.2.5. The (AES256 crypted) shared key (256bit) must be set by Q4-mml.S:K:H:. Installing L3 Data Collector Procedure 1 7. ZQ4A:GIVAXIPSK. Procedure 1 Set message monitoring encryption preshared key for L3 Data Collector (Megamon) interface.

2. In L3 Data collector.5. use the following command: ZQ4A:MSGMONPSK.1 Note: This key must always be 64 ASCII characters in size. then an IPoA must be created between each of these NPGE/NPGEPs with unique IP on each NPGEP/NPGEP. only the interface that has been configured for IPoA between NPGEs/NPGEPs and OMU must be added to the external interfaces dialog. use the physical IP address. use PHY or P instead of LOG or L. This is unrelated to the GIVAXIPSK that was set in the previous step.1.    WCDMA 16 Feature Descriptions and Instructions 7. The interface must be the same Eg: IFAI10 for all.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. In case each interface (IuPS.2.S:K:H. g 7.5 Performance monitoring features Configuring MSGMONPSK for data encryption Procedure 1 For data encryption key authentication. In the commands.IuCS. 2.5. 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.6.1. Before you start Figure 38 Site solution deployment for IPA-RNC Emil/MegamonPC RNCsite O&Mdata OMS RNC DMCU0-n Site Router OMU(WO) ESA Monitored control/data ICSU0-n NPGE(WO) Usertraffic DCN L3 (aggregation) DCN RSMU Issue: 01E DN09203161 267 .Iub/Iur) has its own NPGE/NPGEP.6 7.2. Purpose 1. If NPGE is used instead of NPGE(P).5.

 However.:10.0:IFAI4.239.10.0.L:AA0:. 268 DN09203161 Issue: 01E .10.6 LAN WritetoUP.10.CP monitoreddataoverIP TP monitoringdata TP monitoreddatausing IPoA 10.P:24:10.239.58. Figure 39 IP interfaces between units in the IPA-RNC External monitoring tool IPA RNC UP monitoreddatausing DMX OMU DMPG CentralizedMonitoringEntityGIVAXI Userinputs UserPlane monitoring agent ELO:10. ZQRS:OMU.10.5(IFAI4).10. 4 Interrogate network status to check whether there is already an IP configured from OMU to O&M.142 NPGE Encrypt+write to TP monitored datafile CP Monitored datausingDMX ICSU TransportPlane monitoringagent ControlPlane monitoringagent IFAI4:10. one ethernet cable is sufficient to connect to the DCN.L:IFAI4:OMU. CP monitored datafile ESA switch CP.0:AA0.N:10. ZQRN:OMU.114 TP Monitoring AAO:10.10.10.10.10.10.6:. use: ZQRN:NPGE. ZQMC:NPGEP. from external monitoring tool machine.L:24:10.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions This does not require any additional cables to the NPGEs. It is sufficient to have one interface card on the monitoring machine In this case.0.10. If a second interface card is available at the external monitoring tool machine.10.Upmonitoringdata UP. 2 Configure IFAI interface at NPGE(P) with destination IP as that of the OMU.58.10.0. ZQRN:NPGEP.:10.10.10. the user needs to login/directly use the external monitoring tool machine to monitor the IPA-RNC.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.0:IFAI4. For NPGE. 3 Configure AA0 (ATM) network interface at OMU with destination IP as that of NPGE(P).6.5(IFAI4):.6:.L:24:10.5(IFAI4).10. then that could be used for using the external monitoring tool remotely.

2.2.2.OMU EL 2.3. 7.1.0:IPF=YES.1.1. 2 Enable IP forwarding for both OMUs towards the external monitoring tool.2. ZQRT:OMU. static routes to both NPGE and External Monitoring Tool side need to be configured on site routers.10.2.255.1.0 255.5.1/24 ----2. or Juniper.24:10.3. The destination IP address with netmask depends on the external monitoring tool machine’s IP address.2. Also. ZQKC:NPGEP. The Local address is the OMU’s IP address in the output.1 but no static route is needed with destination Emil 3.6.1/24 ---.0 2.6:LOG:. 7.1/24 Emil Packets with destination NPGE to be sent to 2. Without the static route configurations.6.0.3 Configuring site routers If there are site routers between RNC and external monitoring tool. 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 Create a static route from NPGE(P) via gateway AA0 interface to external monitoring tool.2/24 cisco 3.2.239.5.10.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.3.3. Huawei. Procedure 1 Cisco3750G(config)#ip route 1.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features Check the output whether the foreign address is that of the O&M (indicated as BSO&M) with state as ESTABLISHED.58.1 Step example NPGE IFAI 1. Commands to configure the site routers depend on the type of router: Cisco.2/24 -----.1:IPF=YES. ZQRT:OMU. Issue: 01E DN09203161 269 .2.0/24 because they are in same subnet.0: 10.1.2.3.255. site router will drop the packets with destination to NPGEP.1.2.3.3. No configuration needed for transfer of UP and CP monitoring data as those involve DMX message based communication.

0 2.2.255.2.255.2.3. assign an IP address to the external monitoring tool workstation.255.0 255.2. 2 For the external monitoring tool.114 7.1.1.4.1 Cisco1(config) towards NPGE #ip route 1.1 Step example NPGE IFAI 1.2 Emil Packets with destination as 1.2/24 cisco1 3.4.255.3.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions Cisco3750G(config)#ip route 1.6.3. Ping 10. configure the routing table so that all packets sent to NPGE(P) (IFAIx) are sent via gateway EL0/EL1 interface on OMU or via site router.6.1.3.1/24 cisco2 4.5 270 DN09203161 Issue: 01E .0/24 to be sent to 2.0 10.0/24 to be sent to 3.10.0 MASK 255.10.255.4.142:PING.239.0:IP=10.3.1/24 ----2.1 --.2.4.2.2.0 3.255.0 3.239.1 Packets towards 1.2.3.1.2.4.0 255.255.3.1/24 ---.1.58.2.255.4.3.1.5.1 Packets towards 4.0 255.3.1.2.3.58. Step example route -p ADD 10.4. ZQRX:NPGE.5 Verifying IP configuration Procedure 1 Ping from NPGE(P) to external monitoring tool.255.1.1.4.0 2.1 Cisco1(config) towards Emil: #ip route 4.2 Cisco2 towards NPGE ip route 1.255.3.2/24 -----.10.4.5.0 255.1. 2 Ping to NPGE(P) from external monitoring tool.1.10.4 Configuring external monitoring tool (alternative to DHCP) Procedure 1 As an alternative to DHCP. 7.0/24 to be sent to 3.1.3.1.2.OMU EL 2.3.2 Cisco2 towards Emil is not needed as they are in same subnet.1.

 It is sufficient to have one interface card on the L3 Data Collector machine. 24*1Gbit/s + 2*10Gbit/s.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features Result Ping is successfully received from either NPGE(P) or external monitoring tool. IP switch is needed (at least 8 port on mcRNC side and one on the L3 Data Collector side). From L3 Data Collector machine. As an example. then refer to section Configuring mcRNC to support Layer 3 routing towards Megamon. route configuration is not needed. one Ethernet cable is sufficient to connect to the switch. Otherwise. the user needs to login/directly use the L3 Data Collector machine to monitor the RNC. Issue: 01E DN09203161 271 .2. 7.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. execute tracert from either side to check where the packets are getting lost or are looping. In this case. If there are no site routers between external monitoring tool and OMU. Pinging between NPGE and OMU must also work fine.5. This needs a 1GE cable from the SFP port (eg. pinging between them can be checked as well.2.5. then that could be used for using the L3 Data Collector remotely. If a second interface card is available at the L3 Data Collector machine.2.2 7. SFP22) of each BCN to the switch. Possibilities are that the site routers might not have been configured properly or static routes are not present. If not.

XX. two 1GigE ports SFP21 and SFP22 per mcRNC module need to be setup to avoid message monitoring drops.0/24 port sfp21/22 Verify that the L3 Data Collector port configuration was successful.10. see Megamon documentation. add troubleshooting megamon network 192. For further details. set troubleshooting centralized-monitoring administrate ifport ENABLE 272 DN09203161 Issue: 01E . Procedure 1 Configure the port for the L3 Data Collector in every module. 2 Enable the L3 Data collector port.    Performance monitoring features Figure 40 WCDMA 16 Feature Descriptions and Instructions Site solution deployment for mcRNC McRNCBCN#1 MonitoringConditions EITP-0 Monitoreddata USPU-n Controlunit USPU-0 Monitoredunit USUP-y USUP-0 SFP21/22 oftwoBCNs andEmilPCShould beinthesameVlan USCP-x USCP-0 CFPU-0 Monitoring SFP port (SFP21/22) Switch McRNCBCN#2 EmilPC EITP-2 USPU-n USPU-1 USUP-z USUP-x USCP-y USCP-x CFPU-1 g Monitoring SFP port (SFP21/22) Note: When this feature must be used alongside general monitoring.

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 Remote IP2 Remote IP3 7.    WCDMA 16 Feature Descriptions and Instructions 3 Performance monitoring features 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).2 : : : : : : : : 393128 SET SET NOT SET ENABLED 192. This key must always be 64 ASCII characters in size.5.2 - modified 14/12/16 modified 14/12/05 modified 14/12/17 Configuring Givaxi/givClient Procedure 1 Check that Givaxi is running correctly and is waiting for external tool to connect.2. set troubleshooting centralized-monitoring administrate msg-mon-psk abcdef1234567890abcdef1234567890abcdef1234567890abcdef12345 67890 g Note: Note that these two keys can have different values.10. netstat -taunp | grep giv Issue: 01E DN09203161 273 . 5 Verify status.2.10.

0:* Installing licenses for mcRNC Procedure 1 To set the feature state to ON.6 Verifying RAN2973: Enhanced IMSI-based Monitoring 7.10.4:8021 LISTEN 7229/givclient 7.5.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.5.6.11.2.1 Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on IPA-RNC Purpose 274 DN09203161 Issue: 01E .2.0. so it should be preceded with zeros.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions Step example # netstat -taunp | grep giv tcp 0 0 192. use the following command: set license feature-mgmt id <feature code> feature-adminstate on The following features need to be turned on: Table 121 Licenses for RAN2973: IMSI-based Monitoring Type g 7.2. Installing L3 Data Collector Procedure 1 From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Data Collector (Megamon) 7.2.4 Code Object Name Feature 0000005261 IMSI-based Call Monitoring SW Licence Key SI RU00552 IMSI-based Call Monitoring Test LK Software SI RU00551.3 0.2. the code should form a 10-digit number.0. In mcRNC.2.

    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features Refer to the Nokia IMSIMon3G IMSI Trace User Manual for instructions.10. Procedure 1 Connect to CFPU-0 through O&M network. 3 Verify troubleshooting configuration for external monitoring tool connectivity from all nodes of the mcRNC to see if they are available.10.2 Verifying RAN2973: Enhanced IMSI-based call monitoring on mcRNC Follow this procedure to verify that this feature has been activated successfully.6. 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: Owner ---------- Issue: 01E Port group --------------- Interface ------------- DN09203161 Address ------------------ 275 . 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. 7.2.2 - modified 14/12/16 modified 14/12/05 modified 14/12/17 COMMAND OK. 2 Show centralized-monitoring in troubleshooting.

10.10.10.12/24 192.10.10.10.10.10.10.37/24 192.22/24 192. 7.10.10.10.10.20/24 192.2.32/24 192.19/24 192.10.10.25/24 192.10.16/24 192.40/24 192.10.10.38/24 192.26/24 192.10.10.33/24 192.10.10.10.14/24 192.10.10.10.10.10.23/24 192.10.10.10.10.30/24 192.10.10.10.7.6.10/24 192.10.10.31/24 192.10.10.10.21/24 192.3 Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on mcRNC Purpose Refer to the Nokia IMSIMon3G IMSI Trace User Manual for instructions.18/24 192.10.10.10. 7.2.11/24 192.7 Deactivating RAN2973: Enhanced IMSI-based Monitoring 7.10.17/24 192.10.10.10.10.13/24 192.10.35/24 Total count: 32 Ping each of those IP addresses above from the L3 Data collector machine and verify that they are responding.10.10.10.1 Deactivating RAN2973: Enhanced IMSI-based call monitoring in IPARNC Follow this procedure to deactivate this feature.10.10.34/24 192.36/24 192.10. 276 DN09203161 Issue: 01E .39/24 192.10.10.10.24/24 192.10.10.10.    Performance monitoring features /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 /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 WCDMA 16 Feature Descriptions and Instructions 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 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 mmonext mmonext mmonext mmonext mmonext mmonext mmonext mmonext 192.10.29/24 192.15/24 192.10.27/24 192.2.28/24 192.9/24 192.10.

:10.---.-----------------------OMU-0 DEFAULT ROUTE NPGE-0 DEFAULT ROUTE NPGE-0 10.0:IFAI4::OMU.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features Procedure 1 Remove the RAN2973 configured network interface from the OMU towards the external monitoring tool.8. ZQRG:OMU. 3 Remove IFAI interface at NPGE(P).:10. 4 Remove the static route from NPGE(P) to the external monitoring tool.0.10.AA0.17.1 10.0:IFAI4.5.97 10.10.10. For static route from NPGE(P) via AA0 to Emil use the following command: ZQKA:<NBR for static route from NPGE(P) via AA0 to Emil>. 2 Remove the configured TCP/IP ATM internal interface of NPGE(P) towards OMU.0:EL0:<IP address designated for RAN2930>.10.72-0 RNC IPA2800 2014-07-25 17:18:22 INTERROGATED STATIC ROUTES UNIT DESTINATION SESSION ID -------. Step example ZQRG:NPGEP.10.-----.17.0:IFAI4.6 DN09203161 LOG PHY PHY 0 0 0 1 2 6 - 277 .0/24 Issue: 01E GATEWAY ADDRESS ROUTE TYPE PREF NBR BFD -----------------.----.56.10. (OPTIONAL) Step example ZQMD:INT:NPGE.56.56. Or ZQRG:NPGE.5. Step example < ZQKB. LOADING PROGRAM VERSION 2. g Note: This step is necessary only if TP monitoring has been configured and activated.---10.

set license feature-mgmt id <feature code> feature-adminstate off 7.7. Procedure 1 Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Data Collector (Megamon) or L3 Analyzer/Viewer (Emil) → Release: LDC TSS16 SW → Standard Update → Maintenance Packet <ID>. This must be ordered from NOLS. g Note: Deleting the PSK impacts also general monitoring. ZW7M:FEA=<feature code>:OFF.8. 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. ZQ4D:MSGMONPSK.8 Analyzing monitored data and troubleshooting 7.2.    Performance monitoring features 5 WCDMA 16 Feature Descriptions and Instructions Delete the pre-shared key using this command: ZQ4D:GIVAXIPSK. Procedure 1 Delete configured ports. 7.2 Deactivating RAN2973: Enhanced IMSI-based call monitoring in mcRNC Follow this procedure to deactivate this feature. 6 Set the feature state to OFF. 278 DN09203161 Issue: 01E . 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.1 Analyzing monitored data Checking the contents of the messages monitored using this feature requires the use of the IMSIMon3G which supports the RAN2973 feature. see release LDC TSS16 SW for Megamon and release LA TSS16 SW for Emil).2.2.

 monitor CFPU unit with filter “SR:OFAM=728. Before and after monitoring: jane kuostat.    WCDMA 16 Feature Descriptions and Instructions g 7. A valid license needs to be requested from Contact Point. Select “action -> if logging -> set logging” in L3 Data Collector.2 Performance monitoring features Note: The type of license key is an on/off license. 5 Collect RNC symptom report. execute the following SCLI command: save symptom-report name <report_name> include group-RNC 6 In cases where IPA-RNC Transport Plane monitoring does not collect any data. 2 Start DMX message monitoring of SW processes responsible for monitoring. Message Analyser (NSN - FI). loadext dmxmon <=Loads dmxmon service terminal extension dmxmon –f a83 <=Starts DMX monitoring for family a83 (XAGENT) Monitoring can be stopped by pressing <ctrl-C>. 4 Collect Megamon interface logging file and DMX message monitoring. monitor OMU and ICSU units with filter “SR:OFAM=728” For mcRNC.8. • • For IPA-RNC. the following logs should be additionally collected from NPGE(P) units.0B12” and USCP unit with filter “SR:OFAM=0A56” 3 Reproduce the problem. Procedure 1 Enable Megamon interface logging.2. use TN38 Rnclogcol. Troubleshooting RAN2973: Enhanced IMSI-based Call Monitoring Purpose Follow these steps to collect necessary logs for Nokia to investigate monitoring data collection problems. For mcRNC. DMX message monitoring for Transport Plane monitoring agent from the NPGE(P). When IMSI-based call monitoring is ongoing and monitored call(s) are active: Issue: 01E DN09203161 279 .exe to collect symptom report with Basic profile. This can be done by using conventional L3 Data Collector or MML/SCLI commands. • • For IPA-RNC.

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). In mcRNC: a) Check the port configuration for the L3 Data Collector in every module. checking if cable has been connected to every module of the mcRNC. DN09203161 between NPGE/NPGE(P) and the External machine 2. Error: illegal_value_of_param_ec (0x00003829) Check whether the IPoA connections are setup between the Transport Plane units.    Performance monitoring features jane jane jane jane jane jane jane jane jane clog Table 122 WCDMA 16 Feature Descriptions and Instructions prtree prtree prtree prtree prtree prtree prtree prtree prtree –sa mon_dst_addr mon_src_addr ipv4_fwd load_sharing ls_path l3l2 gtp_trace udp_trace_ing udp_trace_egr RAN2973 symptoms and recovery actions Problem (observed in L3 Data Collector) After “Get Units” is done. 3. No units are visible in Megamon or only some units are visible Troubleshooting step 1. Verify reply is available for all. c) If not. Check IPoA configuration and ping After “Set Filter”. 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. In L3 Data collector event window. 2. b) Ping from the L3 Data collector machine to IP address of each port configured for the L3 Data Collector in every module. Check site router configuration Issue: 01E . Check that Givaxi is running correctly and is waiting for external tool to connect. “Start” button does not get enabled which means that Set the monitoring conditions correctly. the OMU and the Emil/Megamon. Verify that the Pre-shared key is administered correctly. 280 No Transport Plane monitoring data available (IPA-RNC) 1.

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. O&M connectivity -> OMS -> NetAct 2.    WCDMA 16 Feature Descriptions and Instructions Table 122 Performance monitoring features RAN2973 symptoms and recovery actions (Cont. 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” Check Givaxi port status. Megamon interface must have been configured for both active and standby CFPUs using the add networking ether /CFPU-0 port mmon-<x> iface mmonext SCLI.159. It takes approximately 20 seconds 7.10. Separate mcRNC Subnets can be configured this way as well: 1.2093. the mcRNC units are on the 10. 2. If Port 8021 is not in LISTEN status. Previously working Megamon license for the PC cannot be used for RAN2973 operations. Before you start 1. Monitoring subnet -> Megamon For the sample scenario in figure.1.2.13. in L3 Data collector. And wait until port 8021 status shows LISTEN. the “Operating mode -> IMSI monitoring” option does not appear It means that the RAN2973 specific license is not available.0/24 subnet. then execute ZWOC:2.9 Configuring mcRNC to support Layer 3 routing towards Megamon Follow this procedure to configure mcRNC to support L3 routing towards Megamon. Traffic subnet 3. Issue: 01E DN09203161 281 .0/24 subnet while the megamon server and the NetAct GW are on a separate 10. 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. the following steps are to be executed to setup a path from the monitored mcRNC units to the Megamon server machine.) Problem (observed in L3 Data Collector) Troubleshooting step 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. Purpose In this case.002. in the “setup -> Output files”. The NetAct GW in the figure is a sample configuration only.

IuPs.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Configure the physical interface at each USPU in the mcRNC modules for Megamon. the SCLI command offers either mmon-1 or mmon-2 depending on which of those were configured for the mcRNC module in which the unit resides. 5 Verfiy the procedure.159.13. or IuCS interfaces.10. Step example set routing node USPU-1 static-route 10. show routing node USPU-1 static-route config all Instance: default Static route: 10.13.159.19 g Note: This will not impact the user traffic meant for Iub.213/32 Next hop type: normal Rank: not defined MTU: not defined Source: 10.213/32 nexthop gateway address 10.13.19 Gateway: 10.159.13.10. Step example set routing node USPU-1 static-route 10. Step example add networking address dedicated /USPU-1 iface mmonext ip-address 10.1 Preference: 1 282 DN09203161 Issue: 01E .159.19/24 role megamon 3 Create a static route from the unit to the Megamon server via the Layer 3 switch.1.10.213/32 source 10.1 on 4 Set the route such that packets from <10.1.13.159.13.159. 2 Assign an IP address to the unit.1.19> are forwarded to the gateway without checking the subnet. add networking ether /USPU-1 port mmon-2 iface mmonext g Note: For <port>.

1. 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 ---------.------------.0 0 0 U 283 .13. /USPU-1 mmon-2 mmonext 10.19/24 ….159.0 0. 7 If super user rights are available.13. connect to the USPU-1 via ssh.13.213/32 Next hop type: normal Rank: not defined MTU: not defined Source: 10.13.19 Gateway: 10. check the routing table and verify that the USPU-1 is able to ping the Megamon IP address successfully.10.1.255.159.159.0.159.255.159.    WCDMA 16 Feature Descriptions and Instructions 6 Performance monitoring features Show troubleshooting megamon.255.255.0.1 Preference: 1 Issue: 01E DN09203161 Genmask Flags Metric Ref 255.10.213 10.213 Static route: 10. # ssh USPU-1 # route -n Kernel IP routing table Destination Gateway Use Iface 10.--------------.1 0 mmonext … 10.0 0 mmonext … # ping 10.13.10.-----------------….1.255 UGH 0 0 255.

 the following counters are introduced: 284 DN09203161 Issue: 01E . 7. For monitoring HSPA subscriber amount 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. Operator benefits This feature enables to follow HSPA subscriber evolution in the network. For counting the maximum number of HS-FACH/HS-RACH users per cell.3. 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. 10 Repeat the above steps for all USPUs to be monitored. 9 Megamon shall now be able to set the monitoring filters on the USPU-1 and start monitoring it. the following counters are introduced: • • M1006C318: MAX NUMBER OF HS-FACH/R99-RACH USERS PER CELL The peak number of users in CELL-FACH state on DL/UL HS- FACH/DCH channels per cell during the measurement period.1 RAN3104 Benefits End-user benefits This feature does not affect the end-user experience.3.2 RAN3104 Functional description The RAN3104: HSPA User Amount Monitoring feature introduces new counters to 1006 RRC signalling measurement. which allow the HSPA subscriber amount monitoring per cell including HS-FACH. 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.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions 8 Verify also from the megamon side that it is able to ping the USPU-1. These counters enable to monitor the amount of HSPA subscribers per cell. 7. M1006C319: MAX NUMBER OF HS-FACH/HS-RACH USERS PER 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 RAN3104: HSPA User Amount Monitoring feature introduces new cell level counters. To calculate HSPAtot.

Measurements and counters Issue: 01E DN09203161 285 .    WCDMA 16 Feature Descriptions and Instructions • • Performance monitoring features M1006C321: MAX NUMBER OF HSPA AND HS-FACH USERS PER CELL The actual maximum amount of HS users in CELL_FACH state and CELL_DCH state per cell.3 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 Monitoring feature do not show valid values.3. Impact on network and network element management tools This feature has no impact on network management or network element management tools. 7. Alarms There are no alarms related to this feature. Impact on system performance and capacity This feature has no impact on system performance or capacity. Impact on interfaces This feature has no impact on interfaces.3.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS Support not required Support not required Support not required MSC SGSN MGW UE Support not required Support not required Support not required 3GPP Rel-8 This feature requires no new or additional hardware. 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. 7.4 RAN3104 Reference data Requirements Table 123 RAN3104 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 RNC16 mcRNC16 OMS NetAct WCDMA OMS16 NetAct 16.

3. Parameters There are no parameters related to this feature. Sales information Table 126 RAN3104 Sales information BSW/ASW BSW SW component RAN License control in network element Not defined 7. and they can vary in different networks.    Performance monitoring features Table 124 WCDMA 16 Feature Descriptions and Instructions New counters introduced by RAN3104 Counter ID Counter name 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 M1006C321 MAX NUMBER OF HSPA AND HS-FACH USERS PER CELL RRC Signalling Table 125 Existing counters related to RAN3104 Counter ID g Measurement Counter name Measurement 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 with primary carrier HSDSCH downlink in the cell. The configuration and parameter settings described are only examples. The M1000C283 counter means Cell_DCH state users with primary E-DCH carrier uplink in the cell. DN09203161 Issue: 01E . Commands There are no commands related to this feature. Key performance indicators There are no key performance indicators related to this feature. Do not use it for the feature as such in a live network.5 Testing RAN3104: User Amount Monitoring Purpose g 286 Note: This is an example of the verification.

 the following network elements and equipment are used: • • • • • • • RNC IU-CS IU-PS WRAB one WBTS one IPNB some WCELs to be created Procedure g Issue: 01E 1 Open the RNW Measurement Management application.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features The purpose of this test case is to verify if the counters introduced by the RAN3104 HSPA User Amount Monitoring feature 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 number of 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. 11:30. 2 Start the M1006 measurement. For example 11:00. data collection starts every quarter. Wait for the measurement interval to begin. 11:15. 11:45. DN09203161 287 . the following network elements must be at least on the following software level: • • • RNC: RNC16/mcRNC16 OMS: WOMS16 WBTS: WBTS16 For the test case. Note: In case of a 15-minute interval.

 if you start the measurement at 11:22. Result Expected outcome The value of counters M1006C318.1 RAN2862 Benefits End-user benefits This feature does not affect the end-user experience. the collected data is available in OMS at 11:55. 7. M1006C319. a HS-FACH/HS-RACH user. M1006C320 and M1006C321. For example. 4 Stop all calls before 15 min time interval has passed. Unexpected outcome The value of counters M1006C318. 288 DN09203161 Issue: 01E .4.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions 3 Run a HS-FACH/RACH user. M1006C319. 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 RAN2862: Multi-RAB Dedicated Counter Set Introduction to the feature The RAN2862: Multi-RAB Dedicated Counter Set feature 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 7. M1006C320 and M1006C321 in a selected 15 min time interval is zero and have not incremented. g Note: Measurement results are available in the application after the measurement interval ends plus 10 minutes. M1006C319. Operator benefits This feature improves monitoring capabilities by adapting measurements to the operator’s needs. M1006C320 and M1006C321 have incremented in a selected 15 min time interval. 5 Open the RNW Measurement Presentation application and check the values of counters M1006C318.

Impact on interfaces This feature has no impact on interfaces.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features 7. This optional feature adds new counters for: • • • CS Voice setup attempts. Alarms There are no new alarms related to this feature. Impact on network and network element management tools This feature has no impact on network and network element management tools.4. Impact on system performance and capacity This feature has no impact on system performance and capacity.4 RAN2862 Reference data Requirements Table 127 RAN2862 hardware and software requirements RAS IPA-RNC mcRNC Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS WCDMA 16 RNC16 mcRNC16 Support not required Support not required Support not required OMS NetAct MSC SGSN MGW UE WCDMA OMS16 NetAct 16. 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. and ISHO success rate for CS Voice + PS Multi-RAB 7. access completions. 7.4. and active failures while at least one PS RAB has REL99 DCH.3 RAN2862 System impact Interdependencies between features This feature has no impact on other features. HS-DSCH/DCH. Commands Issue: 01E DN09203161 289 . BTS faults and reported alarms There are no BTS faults and reported alarms related to this feature.2 RAN2862 Functional description The RAN2862: Multi-RAB Dedicated Counter Set feature introduces additional counters for monitoring CS + PS multi-RAB performance. setup failures.4. access failures.2 Support not required Support not required Support not required Support not required This feature requires no new or additional hardware. IFHO.

5 Activating RAN2862: Multi-RAB Dedicated Counter Set Purpose Follow this procedure to activate the feature. Sales information Table 129 RAN2862 Sales information BSW/ASW ASW SW component RAN License control in network element RNC ON/OFF License key 7. Measurements and counters Table 128 New counters introduced by RAN2862 Counter ID Counter name Measurement 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.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions There are no new commands related to this feature. Parameters There are no new parameters related to this feature. 290 DN09203161 Issue: 01E .4. 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 OMS shows the counter values in RNW measurement presentation GUI and forwards data to NetAct if related measurements M1001. see Licensing. 7. M1007.6 Verifying RAN2862: Multi-RAB Dedicated Counter Set Purpose Follow this procedure to verify the feature. For mcRNC: set license feature-mgmt code 0000005571 feature-adminstate on Result Expected outcome: The RAN2862: Multi-RAB Dedicated Counter Set feature has been activated. For more information on licensing. Make sure you have an access to the following applications: • • Issue: 01E RNW Measurement Management RNW Measurement Presentation DN09203161 291 . g Note: The feature code for this feature is 5571. M1008 and M1010 are active. counters have zero value in RNW Measurement Presentation GUI and are not sent to NetAct. Procedure 1 Set the feature state to ON Use this commands to activate the feature: • • For IPA-RNC: ZW7M:FEA=5571:ON.4. Further information: If the RNC does not have the license installed and feature activated.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features The RAN2862: Multi-RAB Dedicated Counter Set feature is controlled by the long-term ON/OFF license key. Before you start The RAN2862: Multi-RAB Dedicated Counter Set feature is activated.

 the feature is not activated. 6 Download a file using PS connection. The measurement interval then starts. if you press the Start button at 11:22. For example. Result Expected outcome: Counter M1001C758 RAB HOLDING TIME CS AMR WITH ACTIVE PS shows higher than zero value. If the counter value is zero. 4 Make a CS Voice call.7 Deactivating RAN2862: Multi-RAB Dedicated Counter Set Purpose Follow this procedure to deactivate the feature. 8 Check with RNW Measurement Presentation GUI that counter M1001C758 has greater than zero value. 7. For details on using the RNW Measurement Management application. 2 Start the M1001 measurements. the data collection starts at 12:00. 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. see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 3 Wait for the next 60-minute interval to begin.4. 292 DN09203161 Issue: 01E .    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions Procedure 1 Open the RNW Measurement Management application. 7 Release both calls. 5 Make a PS call on top of the CS Voice RAB with the same UE. Before you start The RAN2862: Multi-RAB Dedicated Counter Set feature is activated.

Operator benefits RAN2304: VSWR Monitoring feature enables the operator to monitor VSWR (Voltage Standing Wave Ratio) information via BTS Site Manager from all active transmitter antenna lines. Monitoring is possible for 3TX and 6TX RFMs.1 RAN2304 Benefits End-user benefits This feature does not affect end user experience. Performance monitoring counters are provided to enable whole network monitoring for current VSWR values. as well as during troubleshooting cases and as an aid when tuning VSWR alarm thresholds. Use this commands to deactivate the feature: • • For IPA-RNC: ZW7M:FEA=5571:OFF. creating CAPEX saving to network maintenance. For mcRNC: set license feature-mgmt code 0000005571 feature-adminstate off Result Expected outcome: The RAN2862: Multi-RAB Dedicated Counter Set feature has been deactivated. Issue: 01E DN09203161 293 . Purpose of RAN2304: VSWR Monitoring feature is to deliver quasi real time VSWR samples from selected radios antenna lines to BTS Site Manager. VSWR monitoring leads to better remote monitoring capability and faster problem solving. Information is updated with 10 seconds intervals. 7. the better.5. 2TX and 4TX RRHs.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. In addition VSWR is used during installation and tuning transmitting antennas.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features Procedure 1 Set the feature state to OFF g Note: The feature code for this feature is 5571. The smaller the VSWR value. 7. The OMS shows the counters have zero value in RNW Measurement Presentation GUI and are not sent to NetAct.

 Only applicable radio modules are listed. Figure 41 Monitor VSWR dialog box The radio module table enables the user to select and activate VSWR monitoring for specified modules. default value is 60 seconds. 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: • • 294 Stopping the monitoring and choosing the Save As.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions 7.2 RAN2304 Functional description RAN2304: VSWR Monitoring feature is enabled via license.. On pressing start. Starting the VSWR monitoring when temporary file already exists. The user sets a monitoring interval between 10 and 3600 seconds. option. DN09203161 Issue: 01E . Performance Monitoring counters RAN2304: VSWR Monitoring feature introduces a new PM counter for each antenna line. Live VSWR monitoring RAN2304: VSWR Monitoring feature enables VSWR live monitoring via the BTS Site Manager.. The counter shows the average value of VSWR during the measurement period (1h by default).5. The corresponding dialog box is opened by navigating through the menu:Antenna ► Tune and Monitor VSWR ► Monitor VSWR.

.4 RAN2304 Reference data Requirements Table 130 Issue: 01E RAN2304 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 Support not required Support not required WBTS16 WBTS16 Not planned OMS NetAct MSC SGSN MGW UE WCDMA OMS16 NetAct 16. 7. • Saving the data to a user defined file. temporary file is deleted. • • • • • Values are displayed in the Monitored values table for each antenna.2 Support not required Support not required Support not required Support not required DN09203161 Flexi Multiradio BTS Flexi Flexi Lite Multiradio 10 BTS BTS 295 . but is yet to start. Starting monitoring failed - Monitoring cannot be started or license is missing. If not saved.. elapsed time and values are displayed. - monitoring is ongoing and values are displayed and stored to the temporary file. even if the measured VSWR value is lower than 1. Monitoring completed - monitoring is stopped and data can be saved to a user defined file.5... Monitoring.5. g Note:  For following FRM/RHH.. Possible statuses are: Starting monitoring. Impact on interfaces This feature has no impact on interfaces.3 RAN2304 System impact Interdependencies between features This feature shares the same license with RAN907: Antenna Line Supervision. clears the temporary file. but has not yet stopped. Impact on network and network element management tools This feature has no impact on network management or network element management tools. the fixed value of 1. Stopping monitoring . - stopping monitoring is requested. Impact on system performance and capacity This feature has no impact on system performance or capacity.5 is reported: • • FHxA RRH modules FRGF FRM modules with FFGFs manufactured by PW (SW version N_00V010507) 7. - monitoring is requested..5. When monitoring begins.    WCDMA 16 Feature Descriptions and Instructions Performance monitoring features Exiting the BTS Site Manager or disconnecting the BTS while temporary file closes.

. Alarms There are no alarms related to this feature.5 Testing RAN2304: VSWR Monitoring Before you start Test environment: • • • Operational Radio Access Network and Core Network.5.    Performance monitoring features WCDMA 16 Feature Descriptions and Instructions Monitoring is possible for FRGF and all Rel. License key Antenna Line Supervision (key:309) is available.1 and onwards RFM and RRH modules.1 and onwards RFM and RRH modules. Measurements and counters Table 131 New counters introduced by RAN2304 Counter ID Counter name M5010C0 Measurement AVERAGE VALUE OF VSWR 5010 - WBTS Antenna Line (WBTS) Key performance indicators There are no key performance indicators related to this feature. DN09203161 Issue: 01E . Preconditions: • • • 296 WBTS is required to be in On Air status Commissioning parameter Antenna line supervision in use must be enabled. see Figure 42: Antenna line supervision in use parameter set. Parameters There are no parameters related to this feature. HW configuration: Radio modules FRGF and all Rel.2.2. Sales information Table 132 RAN2304 Sales information BSW/ASW ASW SW component RAN License control in network element BTS LK 7. Both FSMr2 and FSMr3 platform can be used for these tests.

 Ant X VSWR. Procedure 1 Open the BTS Site Manager and go to: Antenna -> Tune and Monitor VSWR… 2 Open Monitoring and go to Monitor VSWR.. 7 Verify if the file is saved in desired location. 6 Save the results.. using the "Save As. Issue: 01E DN09203161 297 ." button. current VSWR values should be visible and a saved data file should contain all the measured parameter values: PC time. Result If the antenna is properly set up. 4 VSWR measurements are collected during the defined interval (default interval is 60s). 5 Press the "Stop" button. Ant X+1 VSWR.    WCDMA 16 Feature Descriptions and Instructions Figure 42 Performance monitoring features Antenna line supervision in use parameter set. 3 Press the "Start" button.

mcRNC reacts to the state changes of the alarm inputs. Cost reduction due to changes in the condition of supervised external entities. via SCLI.1 RAN2646: External Alarm Input Support of mcRNC Introduction to the feature This feature enables the utilization of mcRNC-integrated external alarm inputs.1 RAN2646 Benefits End-user benefits This feature does not affect the end-user experience. These can be converted to normal alarm events and reported to operating personnel via the same user interfaces as the internal alarms of mcRNC. if a door is opened or if the temperature of the equipment premises exceeds a certain threshold.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 8 RNC solution features 8. 8.1.2 RAN2646 Functional description The RAN2646: External Alarm Input Support of mcRNC feature enables mcRNC to collect triggering signals and use them to raise or clear a series of user-defined external alarms accordingly. The external alarm input can be assigned to an external alarm input-id ID.1. and NetAct Monitor. The maximum supported input amount in the mcRNC step 7 configuration is 64. They can be monitored like regular mcRNC alarms. These alarms can be managed by regular alarm operations. External Input shows input-id ranges per module number. OMS EM Fault Management GUI. for example door alarms or fire alarms. Table 133 External Input module number input-id 298 1 0 - 7 2 8 - 15 DN09203161 Issue: 01E . External alarm inputs need to be configured into the system before these inputs and their related external alarms can be put into use. which indicates changes in the condition of supervised entities: for example. depending on the number of mcRNC modules in the deployment. which run in increments of 8. External alarms are triggered by other external equipment at the RNC site. and raises or clears the related user-defined external alarms accordingly. Operator benefits Easier alarms management solution for external device. which can be used for indicating changes in the condition of supervised external entities. External alarms. are managed by normal alarm operations. There are eight alarm inputs per BCN module. 8. External alarms are not triggered by the mcRNC itself.

8. There are two RJ45 connectors per module for external alarm input connections. Impact on network and network element management tools This feature has no impact on network management or network element management tools. 8. input polarity.    WCDMA 16 Feature Descriptions and Instructions Table 133 RNC solution features External Input  (Cont.1. Impact on system performance and capacity This feature has no impact on system performance or capacity.) 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 severity and input admin state for certain external alarm inputs.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. Inputs are voltage sensitive. It is also possible to assign a predefined alarm number to the external alarm input.4 RAN2646 Reference data Requirements Table 134 Issue: 01E RAN2646 hardware and software requirements RAS IPA-RNC mcRNC WCDMA16 Support not required mcRNC16 DN09203161 Flexi Multiradio BTS Support not required Flexi Multiradio 10 BTS Flexi Lite BTS Support not required Support not required 299 . This configuration is performed via the Structured Command Line Interface (SCLI). with a pull-up resistor which allows the connection of direct contacts or optical couplers as alarm sources to these alarm inputs. and the definition or definition update take effect at the mcRNC running time.1.

 Both closing and opening the loop will generate an IPMI event to the hardware management system. Key performance indicators There are no key performance indicators related to this feature. Purpose Enabling external alarm inputs in mcRNC. alarm numbers of which are in the range 70400-70431.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 134 RAN2646 hardware and software requirements (Cont. Alarms are activated by closing the alarm circuit with an external switch. As shown in Figure 43: External alarm interface. Measurements and counters There are no measurements or counters related to this feature. which would indicate incorrect functionality of the feature. each BCN module provides eight external alarm interfaces on two RJ45 connectors in the front panel. 300 DN09203161 Issue: 01E .1. the feature raises and clears predefined external alarms.) 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 does not require any new or additional hardware.5 Activating RAN2646: External Alarm Input Support of mcRNC This feature does not require activation. Parameters There are no parameters related to this feature. Alarms There are no such alarms related to this feature. Before you start Functionality of the external alarm inputs needs to be verified before connecting them to the controller. The inputs are voltage sensitive. However. These instructions only illustrate how to enable its functionality. Sales information Table 135 RAN2646 Sales information BSW/ASW BSW License control in network element RAN Activated by default - 8.

 The operation of the external alarm input ports need to be verified before connecting equipment in to the ports. optical isolators) should be used. for example manually triggering an input polarity change and checking that the alarm equipment reacts accordingly. galvanical isolation (relays. such as an optical isolator. Glitches shorter than 10 ms are filtered out by hardware.filtering Levelshifting.filtering Levelshifting. DN09203161 301 . The alarm inputs are not galvanically isolated in the BCN.filtering CH1 CH2 CH3 LMP CH4 CH5-8 Galvanicisolationbetween customerequipmentandBCN Procedure 1 g Issue: 01E Prepare and validate functionality of external alarm equipment. Note: External hardware and external alarm inputs should be tested. to close the circuit. 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. When remote external equipment is used to drive the inputs. Figure 44 Connecting external alarm inputs 2 Shieldedtwistedpaircable RJ-45 2 2 2 Levelshifting.filtering Levelshifting. Port working status can be found out by manually testing each input with working external equipment.    WCDMA 16 Feature Descriptions and Instructions Figure 43 RNC solution features External alarm interface + + Alarm input interface 8 x voltage input (RJ45) The closed loop current of the alarm circuit is 1 mA.

Table 136 External alarm pin mapping Alarm interface 1 302 Alarm interface 2 Pin Pin name number Description Pin name Description 1 EXT_ALARM_P_3 Alarm 3 positive input EXT_ALARM_P_7 Alarm 7 positive input 2 EXT_ALARM_N_3 Alarm 3 negative input EXT_ALARM_N_7 Alarm 7 negative input 3 EXT_ALARM_P_2 Alarm 2 positive input EXT_ALARM_P_6 Alarm 6 positive input 4 EXT_ALARM_P_1 Alarm 1 positive input EXT_ALARM_P_5 Alarm 5 positive input 5 EXT_ALARM_N_1 Alarm 1 negative input EXT_ALARM_N_5 Alarm 5 negative input 6 EXT_ALARM_N_2 Alarm 2 negative input EXT_ALARM_N_6 Alarm 6 negative input 7 EXT_ALARM_P_4 Alarm 4 positive input EXT_ALARM_P_8 Alarm 8 positive input 8 EXT_ALARM_N_4 Alarm 4 negative input EXT_ALARM_N_8 Alarm 8 negative input DN09203161 Issue: 01E . Figure 45 Connecting external alarm inputs + + Table 136: External alarm pin mapping provides a map of the RJ-45 pins for each of the external alarm interfaces.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 2 Connect the external alarm equipment to the mcRNC. Figure 45: Connecting external alarm inputs shows how to connect external equipment to the mcRNC.

 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. To check what are the currently available external alarm inputs that can be used for the new device. The alarm text is modified with the following command: Issue: 01E DN09203161 303 .    WCDMA 16 Feature Descriptions and Instructions 3 RNC solution features Check available external alarm inputs. 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 Default severity Mapping status : : : : 70401 CHANGE THE TITLLE NUMBER_2 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.

 major or critical severity should be set with SCLI for external alarm input. OMS Fault Management will clear warning severity alarms automatically and NetAct will not display warning severity alarms. 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. add hardware config ext-alarm-input input-id <input-id> specific-problem <specific-problem> description <description> polarity <polarity> severity <severity> admin-state <admin-state> t Tip: Table 137: External Input shows input-id ranges per module number.    RNC solution features WCDMA 16 Feature Descriptions and Instructions set hardware config ext-alarm-type specific-problem <specificproblem> title <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. Table 137 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 304 DN09203161 Issue: 01E .

8. 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. Enter the following command: show alarm active filter-by specific-problem <ext-alarmnumber> Step example Issue: 01E DN09203161 305 . open said door.1. Procedure 1 Check if any alarm exists.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Result The operator has successfully configured an external alarm. These instructions only illustrate how to verify its functionality.6 Verifying RAN2646: External Alarm Input Support of mcRNC This feature does not require verification. 3 Verify if the predefined external alarm was raised in mcRNC. Step example Assuming alarm DOOR_SWITCH_1 is mapped to a door sensor. Purpose Verify that external alarms are properly configured.

time Alarm time Event type Application : : : : : : : : : : : : 115661 70400 .fsFrag mentID=RecoveryGroups. addl. These instructions only illustrate how to disable its functionality.7 Deactivating RAN2646: External Alarm Input Support of mcRNC This feature does not require deactivation. info : Description={efg} Unit={BCNMB-B} Positi on=/chassis-1/motherboard-1 Sensor={num ber=254. user ID Ack.1. addl.fsFragmentId=HA. 8.    RNC solution features WCDMA 16 Feature Descriptions and Instructions show alarm active filter-by specific-problem 70400 Step result Alarm ID Specific problem Managed object Severity Cleared Clearing Acknowledged Ack.Name=External alarm} Result The operator has successfully verified external alarm. 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 306 DN09203161 Issue: 01E . Procedure 1 Set the alarm admin state to disabled. fsCluster=ClusterRoot Identif appl. info : input-id=0 Appl.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. Purpose Disabling external alarm inputs in mcRNC.

 connection establishment.2 RAN3057: mcRNC Signaling Capacity License Introduction to the feature The RAN3057: mcRNC Signaling Capacity License feature introduces a new license to control signaling capacity. 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.2. If more signaling capacity is necessary. Signaling capacity usage is monitored by CS+PS session Successful Busy Hour Call Attempt (SBHCA) counters. to approximately 100Mbps in total.2. and connection control. In practice this is equivalent to no PS data throughput. 8. w This feature is a mandatory prerequisite for the usage of WCDMA 16 software and must not be removed from the system.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Result The operator has successfully disabled the external alarm input. The constant growth of smartphone usage demands higher signaling capacity. It is mandatory to activate the feature. 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.2 RAN3057 Functional description Overview A new signaling capacity license is introduced in mcRNC16 to control the usage of signaling capacity on mcRNC HW Rel. the users receive a relevant notification through an alarm. Signalingrelated tasks comprise management. 8. which means to install the license on the controller before the system runs for the first time with the new WCDMA16 software in the live network. More signaling capacity requires the installation of signaling capacity license.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: • With "Buy as You Grow" sales approach the customer saves CAPEX when the signaling load in his network is low and can later buy more signaling capacity licenses when the signaling load grows. After activation the user is obliged to monitor the signaling capacity. delivered as signaling capacity license files.2 controller. 8. Signaling capacity is defined by the total number of the following procedures taking place simultaneously within the system: Issue: 01E DN09203161 307 .

 the feature provides an alarm notification. In case the operator is able to obtain data from the network. Before the feature activation the user estimates the signaling capacity license size on the basis of Successful Busy Hour Call Attempts (SBHCA).    RNC solution features WCDMA 16 Feature Descriptions and Instructions • • • CS voice RAB setup PS user plane allocation in radio network Cell_PCH to Enhanced Cell_FACH transition The RAN3057: mcRNC Signaling Capacity License feature 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. taking into account the following counters: Table 138 SBHCA counters Number 308 Name M1022C21 HS-DSCH/E-DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR INTERACTIVE M1022C22 HS-DSCH/E-DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR BACKGROUND M1022C23 HS-DSCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR INTERACTIVE M1022C24 HS-DSCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR BACKGROUND M1022C25 HS-DSCH/DCH ALLO AFTER HS-DSCH/DCH REQ FOR INTERACTIVE M1022C26 HS-DSCH/DCH ALLO AFTER HS-DSCH/DCH REQ FOR BACKGROUND M1022C27 DCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR INTERACTIVE M1022C28 DCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR BACKGROUND M1022C29 DCH/DCH ALLO AFTER HS-DSCH/DCH REQ FOR INTERACTIVE M1022C30 DCH/DCH ALLO AFTER HS-DSCH/DCH REQ FOR BACKGROUND M1022C31 DCH/DCH ALLO AFTER DCH/DCH REQ FOR INTERACTIVE M1022C32 DCH/DCH ALLO AFTER DCH/DCH REQ FOR BACKGROUND M1022C190 HS-DSCH/E-DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR STREAMING DN09203161 Issue: 01E . he collects measurement from the counters listed in Measurements and counter and use measured values in the relevant Signaling capacity license size formula. License preparations The user is responsible for calculating the required license. The operator purchases new controller and must estimate what the license size is basing on the relevant traffic profile. As a result the customer gets information about the necessity to buy more capacity with the license file. Data for the calculations may be obtained through these possible scenarios: • • The operator has the controller installed in the live network and is able to run specified measurements. When the signaling load approaches the licensed capacity limitation. Calculation of the required capacity license size using data obtained from the live network.

 If the counters for the KPI are not available. using the following formula: Where the signaling capacity reporting period corresponds to the sampling period of the SBHCA counters. Control Plane dimensioning Signaling capacity license for mcRNC chapter • • After the feature activation the user measures required license size using Measurements and counter and Key performance indicators Estimating the license size on the basis of the user's traffic profile. 1. The signaling capacity reporting period is 30 seconds. see Dimensioning WCDMA RAN: RNC (IPA-RNC and mcRNC). Basing on Smartphone traffic profile reference determine the following values: • • Issue: 01E CS BHCA per subscriber PS session BHCA for human per subscriber DN09203161 309 .) Number Name M1022C191 HS-DSCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR STREAMING M1022C192 HS-DSCH/DCH ALLO AFTER HS-DSCH/DCH REQ FOR STREAMING M1022C193 DCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FOR STREAMING M1022C194 DCH/DCH ALLO AFTER HS-DSCH/DCH REQ FOR STREAMING M1022C195 DCH/DCH ALLO AFTER DCH/DCH REQ FOR STREAMING M1001C115 RAB ACCESS COMPLETIONS FOR CS VOICE M1006C220 CELL_PCH TO ENHANCED CELL_FACH SUCCESSFUL Signaling capacity is measured in kilo BHCA (kBCHA). t Tip: For more information. Primary method for calculating the license size is RNC_5537a Average Signaling Capacity Usage KPI.    WCDMA 16 Feature Descriptions and Instructions Table 138 RNC solution features SBHCA counters (Cont. Data for the calculation is taken from the user-specific traffic profile or from default smartphone traffic profile. 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. The divisor 1000 means that signaling capacity is measured in kBHCA units. The RNC Control Plane load strongly depends on the number of subscribers and the related traffic profile.

310 DN09203161 Issue: 01E . 3. Ordering license relevant to predicted signaling capacity. Checking license readiness for system release upgrade. Read out required signaling capacity license size using Signaling capacity license Table 139 Signaling capacity license Capacity license Basic capacity S1-B2 S3-B2 S7-B2 2 927 7 317 16 586 Separately licensed capacity 642 1 605 3 638 Extended capacity 8 922 20 224 3 569 Example of calculations CS BHCA per subscriber = 1 PS session BHCA for human per subscriber = 3. 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. The user checks whether the feature is prepared correctly for this procedure with the command: show license feature-mgmt code 0000005385. If: • • Signaling load > Basic capacity the user must extended the signaling capacity. Calculate the signaling load with the formula: Signaling load=(CS BHCA per subscriber + PS session BHCA per subscriber) * number of subscribers 4.2 PS session BHCA for pollings per subscriber = 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.8 Predicted number of subscribers = 50 000.    RNC solution features WCDMA 16 Feature Descriptions and Instructions • PS session BHCA for pollings per subscriber 2.2 + 12. When the license is available the user instals it according to Installing licenses in the network element. The user is able to check whether the controller is now prepared for software release upgrade procedure. The user orders required signaling capacity license on the basis of the signaling capacity calculations. Predict the number of subscribers. Signaling load < Basic capacity the user does not need to extend the signaling capacity because basic capacity license is enough.

The operator calculates. the controller measures average signaling capacity usage. and reports the average signaling capacity usage to the operator within a defined statistics reporting period. orders. Because of this control. Used Capacity indicates the currently used signaling capacity. 2. measured in kBHCA. Issue: 01E DN09203161 311 . After the license file installation. 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 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. In reply the controller displays the current average signaling capacity usage. 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.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Feature is prepared correctly when the command's printout is: _nokadmin@CFPU-0 [RNC-38] > show license feature-mgmt code 0000005385 CFPU-0@RNC-38 [2015-02-23 13:08:56 +0100] Feature Name Feature Code Type Admin State + License State = Combined Operational State Feature Description : mcRNCSignalingCapacity : 0000005385 : capacity : on + on = on : RAN3057 mcRNC signaling capacity When the proper license has been installed correctly. There are two options as a result of the initial signaling capacity control: • • The controller begins operating with the new software environment with traffic unblocked if Allowed Capacity is greater than Used Capacity. compares it with the actual licensed signaling capacity. the existing licensed signaling capacity are accumulated. In the result Allowed Capacity increases. Based on these calculations. Monitoring the signaling capacity license usage The controller performs signaling capacity license control by collecting CS+PS session SBHCA counters value every 30 seconds. signaling capacity license file to mcRNC. without blocking the AMR voice service if Used Capacity is greater than Allowed Capacity. The licensed signaling capacity limitation defines the maximum CS+PS SBHCA value. and installs required. The user can interrogate the controller for the used signaling capacity with the show license feature-mgmt usage code 0000005385 SCLI command. the user upgrades the software. The controller's application limits the PS data service. If Used Capacity is greater than Allowed Capacity then: 1.

 In practice this is equivalent to no PS data throughput. he can still perform the operation afterward. Activating the feature for the factory pre-commissioned controller License must be installed by the operator right after the commissioning of the controller. This checking helps to remind the operator that more signaling capacity is necessary and he must buy signaling capacity to avoid throughput penalty on PS interfaces. O&M software raises alarm 3360 LICENSE NOT READY to inform the user about failure. Troubleshooting When the user does not activate the feature correctly before system upgrade. 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. The license has been removed. The license has expired. The user must not cancel this alarm manually. 8. This action does not require system restart.3 RAN3057 System impact Interdependencies between features There are no interdependencies between this and any other feature. The operator is responsible to continuously monitor the used signaling capacity by collecting data from the M802 measurement counters listed in Measurements and counter. In this case the operator is responsible for license installation or license renewal. Impact on interfaces This feature impacts interfaces as follows: 312 DN09203161 Issue: 01E . The controller immediately cancels the warning alarm and terminates PS throughput limiting if Allowed Capacity is greater than Used Capacity. After successful feature activation the controller cancels the related alarm and PS traffic is not limited. to approximately 100Mbps in total.2. Operating algorithm details The feature algorithm details are available in SW License Key Controlled IPA-RNC and mcRNC.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 3. The controller checks the signaling capacity usage and warns the operator by alarm 3294 LICENCE CAPACITY WARNING alarm if the signaling capacity usage is close to licensed limitation. This alarm is also raised when: • • • The feature has been disabled. Activating the feature after software clean installation License must be installed a by the operator right after the clean installation procedure was performed. RNC PS throughput capacity will be severely limited. For more information see Alerting signaling capacity license.

    WCDMA 16 Feature Descriptions and Instructions • RNC solution features Iu-PS interface traffic is limited in case the feature is inactive. Alarms Table 141 New alarms introduced by RAN3057 Alarm ID Alarm name 3360 LICENSE NOT READY Table 142 Existing alarms modified by RAN3057 Alarm ID Alarm name 3294 LICENCE CAPACITY WARNING Measurements and counter Table 143 New counters introduced by RAN3057 Counter ID Issue: 01E Counter name M802C26 SIGNALING_CAPA_USE_AVE M802C27 SIGNALING_CAPA_USE_MAX M802C28 SIGNALING_CAPA_LICENSED M802C29 PS_THR_LIMIT_DUR_SIGN DN09203161 Measurement RNC capacity usage measurement 313 .2. In practice this is equivalent to no PS data throughput.2.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS Support not required Support not required Support not required MSC SGSN MGW UE Support not required Support not required Support not required Support not required This feature is mandatory from WCDMA16 release and the license is relevant only to mcRNC HW Rel.4 RAN3057 Reference data Requirements Table 140 RAN3057 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 Support not required mcRNC16 OMS NetAct WCDMA OMS16 NetAct 16. 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: • signaling capacity is controlled by the license 8. The PS limit is approximately 100Mbps in total.

2 (license is relevant only for this HW) SW: • • • • • NetAct 16.5 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. to approximately 100Mbps in total.2. In case the license has not been installed because the feature is disabled or license has expired. RNC PS throughput capacity will be severely limited. O&M software raises alarm 3360 LICENSE NOT READY to inform the user about failure. In practice this is equivalent to no PS data throughput.2 OMS16 mcRNC16 WBTS16/Flexi16 PET tester is needed to generate traffic. Procedure 1 Test the traffic after the license has been installed with zero capacity.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Key performance indicators Table 144 New key performance indicators introduced by RAN3057 KPI ID KPI name Average Signaling Capacity Usage RNC_5537a Parameters Table 145 New parameters introduced by RAN3057 Full name Abbreviated name Managed object Maximum Signaling Capacity MaxSignalingCapacity RNC Signaling Capacity License Warning Threshold SigCapLicWarnThreshold RNC Sales information Table 146 RAN3057 Sales information BSW/ASW License control in network element BSW RNC LK Activated by default No 8. Run the traffic described with the following parameters: 314 DN09203161 Issue: 01E .

b) Run the traffic Run the traffic described with the following parameters: • • 100 HSDPA 14.    WCDMA 16 Feature Descriptions and Instructions • • RNC solution features 100 HSDPA 14. Test the traffic when the license has been installed with a particular capacity. Alarm 3360LICENSE NOT READY is raised.4M call 1000 AMR 12.4M call 1000 AMR 12. Issue: 01E DN09203161 315 . Tip: This example assumes that signaling license capacity is 100 KBHCA Sub-steps a) Install the license and enable feature with 100 KBHCA capacity.2K with call duration 20s Step result • • 2 t RNC PS throughput capacity is limited to 100Mbps in total.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.

 lasting many hours or days. This feature allows RAN recovery from fatal HW failure of a single controller or the controller's site. This feature helps to avoid long outages. When one physical controller has failed.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 3 Check measurement and counter registered values. DN09203161 Issue: 01E .3. 8. the operator is able to command the earlier-configured and synchronized backup physical controller to take over the responsibility of the failed physical controller. Operator benefits This feature shortens the controller's outage time in the radio network.1 new counters added for this feature hold zero value. 8. This feature allows RAN recovery from fatal HW failure of a single controller or the controller's site. Check Measurements and counter values in OMS Application Launcher.2 RAN3005 Functional description The feature improves network availability during single outages and the controllers site outages. the operator is able to command the earlier-configured and synchronized backup physical controller to take over the responsibility of the failed physical controller.1 RAN3005 Benefits End-user benefits This feature improves network services availability in case of catastrophes. This feature introduces the following definitions: • 316 Physical RNC (PRNC) which is a RNC HW with SW installed. These values are updated according to the real signaling capacity value Figure 46 g RNW Measurement report for RNC Capacity usage Note: For mcRNC HW Rel. lasting many hours or days. When one physical controller has failed.3 RAN3005: Network Resiliency for mcRNC Introduction to the feature The feature improves network availability. This feature helps to avoid long outages.3. 8. The feature improves network availability.

One mcRNC configured as BkPRNC is able to protect up to 16 mcRNCs. In case a PrPRNC fails. so that the redundancy mode is N+1. The PrPRNC and the BkPRNC can be in the same physical site or in different sites. With this feature. Table 147 Backup capacity step matrix BkPRNC capacity step Supported PrPRNC capacity steps in the resilient network S1-B2 (Step 1) • S1-B2 (Step 1) S3-B2 (Step 3) • S3-B2 (Step 3) • S1-B2 (Step 1) • S7-B2 (Step 7) • S3-B2 (Step 3) • S1-B2 (Step 1) S7-B2 (Step 7) Figure 47: Network resiliency transport network concept shows in general the resiliency idea and introduces an example network concept. the operator can introduce BkPRNC to protect a PRNC in the network. One PrPRNC has one BkPRNC configured. it does not have its own radio access network under control. 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. the BkPRNC is commanded by the operator to take over the RAN and interfaces. and to run the PrPRNC's services. Protected PRNC (PrPRNC) which is a PRNC with running network services protected by BkPRNC. Issue: 01E DN09203161 317 .    WCDMA 16 Feature Descriptions and Instructions • • RNC solution features Backup PRNC (BkPRNC) which is a PRNC configured only for redundancy purposes.

 Planning and operating principles are the same in both features.1 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. Also there are no differences from other network elemements point ov view. some difference occurs in RAN3005: Network Resiliency for mcRNC: • 318 Smaller number of system resets is needed since the IP Auto Adaptation (IPAA) can be done in both: base build and backup build.2.3. DN09203161 Issue: 01E . However. because of dissimilarities between SW and HW platforms composing two available RNCs.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 47 NetAct Network resiliency transport network concept OMS RNC SGSN SGSN O&M CBC server Core Site A PrPRNC SAS server MSS/MGW SiteB PrPRNC BkPRNC PrPRNC PrPRNC BkPRNC Backhaul Active Standby RNC-clO&M OMS NetAct 8.

2 RNC solution features Iub control plane is included in IPAA which is managed with IP subnet mapping between PrPRNC and BkPRNC.2. thus the user must plan: • • • • • • • 8. RNC-cl interface configuration RNC-cl is a new. 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: • Issue: 01E After the RNCSRV has been created. This interface does not have strict capacity requirements.2.3. thus special verification of configuration is not needed. RNC-cl interface is verified implicitly at every synchronization.2.3. g Note: Typical configuration package size is 1 MB.    WCDMA 16 Feature Descriptions and Instructions • • • • • • 8. Iubc source address setting follows generic mcRNC principle instead of having a dedicated command. Support for M:N mapping for both IP addresses and IP subnets. DN09203161 319 . any O&M IP addressing change introduced to the base configuration will not be automatically populated to the RNCSRV. Length of PrPRNC’s maintenance window is four hours. The addressing change must be done manually for each of the RNCSRVs. Planning for Network Resiliency The feature requires changes in several configuration. Longer resiliency-related operations Task queue in base build identifying ongoing resiliency operation as well as the pending resiliency-related tasks of all RNCSRVs. 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.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. proprietary interface between PrPRNC and BkPRNC. Differences in alarms.

 The activated feature automatically assigns existing O&M IP address. 8. In case SAS validates the RNC’s source IP address. If this interface is not enabled in the system the Iu-BC role is not defined in any IP address in CFPU unit.3. like BTSOM traffic and RNC-OMS traffic.2. the Iu-BC source address is not valid in BkPRNC anymore and must be changed by the user. Examples in this Activation Instruction assume that the user uses shared IP address solution.2 Planning Iupc interface configuration The Iu-PC configurations enhancement is required to ensure this interface is working after the redundancy switch. It means that in addition to RNC-cl traffic all the other O&M traffic. The SAS does not need to support the two simultaneous SCTP connections because the PrPRNC and BkPRNC are not online at the same time.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. Dedicated IP addresses solution This solution requires an additional IP address for RNC-cl to the OMU’s CFPU interface.2.2. In RNC.2. This solution does not require additional IP layer configuration in the RNC. the validation rule is that the SCTP connection establishment is allowed from the PrPRNC and the BkPRNC. The client has to know the server's destination IP address whilst the server validates the address. The procedure is described in Configuring dedicated cluster interface.    RNC solution features WCDMA 16 Feature Descriptions and Instructions • All PrPRNCs must be configured with the selected solution. The Iu-BC configuration follows the existing mcRNC principle. This has an impact on the BkPRNC’s CP configuration as well as to the CP configuration of the cell broadcast centre (CBC). which the system uses for the separate RNC-cl and O&M traffic.even though CBC takes mainly the client's role. 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. 8. When RNW DB is copied from PrPRNC to BkPRNC. 320 DN09203161 Issue: 01E . the Iu-BC source and destination IP addresses are defined in RNW DB. is terminated to the same IP address. This solution requires an additional IP address for RNC-cl for rnccl role in QNOMU. CBC and RNC are able to have both the client and the server roles on Iu-BC . To change the source address give the iubc to a new IP address in CFPU unit and restart the system. This requirement impacts on the BkPRNC’s configuration and the CP configuration of each connected NE. RNC is a client on the Iupc interface.3.

 The CBC must establish a connection to the BkPRNC and restart the broadcast.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. which refers to BkPRNC. the compatibility of the security solution has to be verified together with the feature. The secondary address is used when connection establishment to the primary address does not work.3.2. the secondary RNC (in this case BkPRNC) starts operating and sends a reset request to the CBC.4 Planning Iub interface configuration Iub interface configuration In BTS. which corresponds to the PrPRNC. which is the case after a redundancy switch. If the access is disturbed and insecure connections cannot be established to peers. In this case it is also necessary to manually verify if the broadcasts are ongoing or whether they should be restarted. It is possible that CBC validates the secondary IP addresses meaning that the same secondary IP address must not be used for multiple RNCs. the actual CBC behavior is vendor specific and may vary from the described example. 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.2. which refers to PrPRNC and the secondary IP address.2. When the primary RNC (in this case any of PrPRNC) is disabled.    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. if the operator wants to have an IPSEC at Iub.3. Total required capacity for Iu and Iur interfaces remains the same as without network resiliency. If CBC does not support the secondary IP address. so CBC has to support the primary IP address. the primary IP address has to be changed manually after the redundancy switch. This requirement impacts upon the BkPRNC’s configuration and the CP configuration of each connected NE. the O&M and NBAP configuration must guarantee the connection establishment between BTS and BkPRNC. Issue: 01E DN09203161 321 . 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. 8. by adding additional BkPRNCconfiguration. 8. 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. However. If IPSEC is enabled in the network. 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. In that case. meaning that the solution works also after the redundancy switch and redundancy switchback. Total required capacity remains the same as without network resiliency. in BkPRNC each RNCSRV has to have a unique source IP address.2.

    RNC solution features WCDMA 16 Feature Descriptions and Instructions Each PRNC requires its own SCTP associations. All source UP IP addresses used on the PrPRNC must be mapped with at least one valid IP address on the BkPRNC. 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. The number of required SCTP associations in Iu is doubled to 2N. N in BkPRNC 2N Table 149 Required number of SCTP associations in Iur compared to a basic situation without network resiliency Case Required number of SCTP associations in RNC1 Required number of SCTP associations in RNC2 RNC1 without network resiliency. Table 148: Required number of SCTP associations in Iu and Iu-PC compared to a basic situation without network resiliency and Table 149: Required number of SCTP associations in Iur compared to a basic situation without network resiliency summarize the SCTP associations in the Iu. N in BkPRNC RNC1 with network resiliency. The feature does not have an impact on the user plane (UP) configuration in CN or in neighboring logical RNCs. RNC2 without network resiliency 2N: N in PrPRNC. as shown in Table 150: Supported IP mapping relationships. N in BkPRNC 2N RNC1 without network resiliency. Table 148 Required number of SCTP associations in Iu and Iu-PC compared to a basic situation without network resiliency Case Required number of SCTP 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. when network resiliency is introduced for the controller. that N SCTP associations are needed in a situation where network resiliency is not applied. RNC2 with network resiliency 4N: 2N in PrPRNC. It is assumed. The IP mapping tables in the BkPRNC must be configured manually. RNC2 with network resiliency 2N 2N: N in PrPRNC. 2N in BkPRNC 4N: 2N in PrPRNC. RNC2 without network resiliency N N RNC1 with network resiliency. The BkPRNC can adapt the RNC’s source UP IP addresses from the PrRNC’s physical environment to its own physical environment. 322 DN09203161 Issue: 01E . 2N in BkPRNC Iu and Iur interface user plane (UP) configuration Proper routing between CN and BkPRNC must exist. Iu-PC and Iur interfaces.

2. It is recommended to move the BkPRNC into LOADED Activity mode and run IP connectivity test regularly to ensure that the transport network is working properly. IP connectivity can be verified by doing IP connectivity test in the BkPRNC.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. Since there is no backwards synchronization.2. Iur and Iub interfaces. It is recommended to perform redundancy switch and run each RNCSRV in BkPRNC regularly (for example. The BkPRNC must be connected to a particular OMS. the operator must reconfigure PrPRNC after redundancy switchback to obtain the required configuration.3. This requires care. The BkPRNC uses its own OMS when there is no active RNCSRV in it. Checking the correctness of CP configuration Issue: 01E DN09203161 323 . It allows to easier manage the logical RNC (RNC object) in Net Act.    WCDMA 16 Feature Descriptions and Instructions Table 150 RNC solution features Supported IP mapping relationships IP mapping relationship 8. which may be different to the OMSs of the PrPRNCs.2. particularly if BkPRNC is on a different site to the PrPRNC. when the related RNCSRV is active in the BkPRNC. Iu-PC. With this solution the same NetAct holds alarm and PM data of both physical RNCs.6 Source UP IP selection 1:1 The source IP of PrPRNC is replaced with the source IP of BkPRNC n:1 The source IP of PrPRNC is replaced with the 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 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. during night every now and then) to ensure that signaling connectivity and the BkPRNC’s SW image works properly.2.8 Principles for NW operations with network resiliency Daily operation and maintenance • • • It is not recommended to change the RNW configuration. 8.2.3. 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.3. when the RNCSRV is active in BkPRNC.2. 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. 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. Iu-BC. The BkPRNC uses the OMS of the logical RNC. 8.

2. 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. PRNCs collect the found User Plane IP addresses and Iub Control Plane subnets to the mapping files which are managed with SCLI commands. IP Auto-adaptation in backup build The user is able to perform the operation also in backup build. Iu-PC.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.3. After completed synchronization of the concerned RNCSRV and during other resiliency-related operations are ongoing. Some configuration require manual work and must be done at LOADED mode: • • • • • • 8. and Iur the user must perform a redundancy switch to BkPRNC and keep the RNCSRV active there for a while. The main user interface utilized to manage the feature are text commands. The operation is considerably faster than made in backup build.    RNC solution features WCDMA 16 Feature Descriptions and Instructions To check the CP configuration at Iu.3. The mappings are managed per RNCSRV in BACKUP or LOADED mode.3. the OMS Element Manager (OMS EM) supports most of functionalities related to the feature.2. 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.2. With them you are able to fully manage the feature. 324 DN09203161 Issue: 01E . 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. verifies transport connectivity without checking the higher layers.1 Operating principles Auto-adaptation in mcRNC Overview This feature allows to perform the auto-adaptation operation in both: base and backup build. Iub. without disturbing the network.3 8.3. the RNCSRV operation is added in task queue to wait for the IP Auto-adaptation. It is essential to ensure that SW builds and configurations of PRNCs up-to-date. The queue can be interrogated to see the all the pending operations. Currently there is no existing solution to verify the signaling configuration in the background. Besides of text commands. In both cases the IP address and IP subnet mapping is required between PrPRNC and BkPRNC. and necessary IP connectivity exists. The available IP connectivity test in the BkPRNC. If the IP Auto-adaptation is disabled. the user must switch the RNCSRV to LOADED state and trigger the operation manually. 8.

 With this solution. a major fault occurs in BkPRNC. for example. manual data synchronization. by setting 3436 alarm. Issue: 01E DN09203161 325 .    WCDMA 16 Feature Descriptions and Instructions RNC solution features In addition to legacy functions. OMS EM allows to upload and download corresponding RNCSRV's IP plan when BkPRNC is in LOADED mode. These alarms do not detail what the actual problem in the BkPRNC is. are nevertheless reported to all the PrPRNCs. The BkPRNC is able to filter the alarms. which are sent by the logical RNC to NetAct: • • • 3429 CRITICAL FAULT IN BkPRNC 3436 MAJOR FAULT IN BkPRNC 3437 MINOR FAULT IN BkPRNC NetAct's northbound interface exports the alarms under the logical RNC. which are able to send a fault occurrence report directly to NetAct. and IP connectivity test. When the operator receives an alarm he must check the OMS to see what the actual specific in the BkPRNC is. 8. There are alarms for indicating problems in the Backup PRNC.3. Problems impacting all the RNCSRVs.2.3 BkPRNC-related alarms in NetAct Alarm notification mechanism for the BkPRNC-related alarms in NetAct. The main tool for managing the BkPRNC-related alarms is the OMS EM. Because NetAct does not recognize a physical RNC (PRNC). which you can see in NetAct.3. like alarm management and the RNW DB parameter management. When using OMS EM you cannot perform operations like: commissioning and preconfiguration. In practice this means that feature-related objects like BKPRNC. Related PrPRNC inform NetAct about it. 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 to LOADED Mode in BkPRNC deleting RNC Service configuration Data synchronization schedule configuration Moreover. The alarm is set once even if several major and minor faults occur in BkPRNC at the same time. the user receives NetAct alarm notification in case of fault in BkPRNC. but indicate fault occurrences. RNCSRV and DATSYN can be managed in OMS EM. For more information see OMS documentation. Alarms related to RNCSRV-X are reported only to the PrPRNC-X instead of being reported to all the PrPRNCs. no alarm raised in the controller can be reported to it directly. then the controller reports this situation to the PrPRNCs. HW alarms. NetAct raises the most critical alarm depending on the severity of the faulty occurrence in BkPRNC. For example. If any alarm occurs in the BkPRNC. you can use OMS EM to monitor the BkPRNC and the feature in general. Alarm notification rules The alarm notification mechanism reports alarms according to rules based on fault severity.

Upgrade the BPS. Alarm 3436 MAJOR FAULT IN BkPRNC is canceled. and inquire the BPS fallback progress. 1. A BPS which contains a running SW build is called a running BPS. 3. NetAct reports the most critical problem.3. Alarm 3436 MAJOR FAULT IN BkPRNC is set. 4. BPS deletion. BPS concept overview The feature introduces a Backup Physical RNC System (BPS) containing one base build and up to 16 backup builds. Alarm 3436 MAJOR FAULT IN BkPRNC is set. the system accepts or rejects the requested operation execution according to the exclusion rule. 8.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Another example illustrates how the rule works when different severity faults occur in BkPRNC at the same time. 7. The problem which triggered 3436 MAJOR FAULT IN BkPRNC still exists. At one time. Mutual impacts and exclusion for simultaneous BPS.4 Backup Physical RNC System management Backup Physical RNC System (BPS) management information. User's operations supported on BPS: • • • • • Show particular or all BPS information existing in the system. 2. Alarm 3429 CRITICAL FAULT IN BkPRNC is set. The purpose of BPS fallback is similar to a single-build fallback. New critical fault appears in BkPRNC at the same time. All of the builds are in the same SW version (release and CD version) The BkPRNC is able to hold more than one BPS.2. 6. The user resolved only the problem which triggered Alarm 3429 CRITICAL FAULT IN BkPRNC. and a BPS operation is ongoing. which the operator utilizes to create BPS backup for a recovery purpose. the user is allowed to execute only one of the following operations: BPS fallback creation. Table 151 Resilient operation exclusion principle Requested operation 326 Ongoing BPS operation BPS Fallback BPS deletion (delete nondefault BPS) BPS Upgrade Service Creation x x x Service Deletion x x x DN09203161 Issue: 01E . Activate the BPS. 5. impacts and safety limitations. Delete the BPS. and BPS upgrade. and resilient operations If the user requests to start an operation.3. Create a particular BPS fallback.

- Not applicable Resilient specific operation might be impacted by running BPS operation.) Requested operation Ongoing BPS operation BPS Fallback BPS deletion (delete nondefault BPS) BPS Upgrade Downloading Y Y x Basic adaptation x x x IP auto-adaptation x x x Pre-configuration x x x Configuration deletion x x x Service Activation Y Y x Service deactivation - x - IP connectivity test - Y - BPS Fallback x x x BPS deletion(delete non-default x BPS) x x BPS Upgrade x x x Y The requested resiliency operation execution is allowed. thus the system needs to follow the exclusive rule to allow or deny BPS operation when resilient operation is ongoing: Table 152 Resiliency operations impact on BPS operations. x The requested resiliency operation execution is rejected. Current RNCSRV status Idle Creating Service Downloading Issue: 01E Activity Mode BPS fallback creation request BPS deletion request BPS upgrade request Wait for Synchronization Y Y Y Backup Y Y Y Active x Y x Loaded x Y x Wait for Synchronization x x x Backup - Active - Loaded - Wait for Synchronization x x x Backup x x x DN09203161 327 .    WCDMA 16 Feature Descriptions and Instructions Table 151 RNC solution features Resilient operation exclusion principle  (Cont.

) Current RNCSRV status Loading RNC Service Deleting service configuration Build failure Activating RNC service Testing IP connectivity IP auto adapting Waiting 328 Activity Mode BPS fallback creation request Active - Loaded - Wait for Synchronization - Backup x Active - Loaded - Wait for Synchronization - Backup x Active - Loaded - Wait for Synchronization Y Backup - Active - Loaded - Wait for Synchronization - Backup - Active - Loaded x Wait for Synchronization - Backup - Active BPS deletion request BPS upgrade request x x x x Y Y x x x Y x Loaded x Y x Wait for Synchronization - Backup x x x Active - Loaded x x x Wait for Synchronization x x x Backup x x x Active - DN09203161 Issue: 01E .    RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 152 Resiliency operations impact on BPS operations. (Cont.

 it is possible for the operator to execute a command for a single-build operation. or must be confirmed if the running build or a new build is a backup build.    WCDMA 16 Feature Descriptions and Instructions Table 152 RNC solution features Resiliency operations impact on BPS operations. BPS safety limitations Even though builds belong to one BPS. For a list of exact rules see Table 153: Forbidden switch cases Legacy single-build deletion request is rejected if 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. - Not applicable. It means that BPS can be impacted by a singlebuild operation as below: • • Single-build switch (for example during redundancy switch/switch back and load/unload) might cause an alarm 3361 NE CONFIGURATION IS WRONG if a running build or a new. Safety limitation to prevent the listed problems: • • Single-build switch is forbidden. A Single-build deletion request might cause a deletion of a build belonging to a BPS without any warning.) Current RNCSRV status Doing basic adaptation Deleting Service Activity Mode BPS fallback creation request BPS deletion request BPS upgrade request Loaded - Wait for Synchronization x x x Backup x x x Active - Loaded - Wait for Synchronization x x x Backup x x x Active - Loaded - Y The requested BPS operation execution is allowed. Table 153 Forbidden switch cases Current running build Issue: 01E New build Rule Normal build (neither base nor backup) Backup build Ask for confirmation Base build Backup Reject DN09203161 329 . x The requested BPS operation execution is rejected. activated build is a backup build. (Cont.

2. UNNECESSAR Y and COMPLETE. Logs configtest_rnc srv<RNCSRVID>. EXPECTED means that PrPRNC IPBR/IPRO configurations adapt to BkPRNC according to IP mapping table.but parameters do not match.log Auto-adaption requires complete IP mapping configuration. – – – – MISSING means that records exist in PrPRNC but do not exist in BkPRNC. commit phase. The test results fall into three classes: INCOMPLETE.3. CURRENT means that IPBR/IPRO configurations exist on BkPRNC.) Current running build New build Rule Backup build Normal build Ask for confirmation Backup build Base build Reject Backup build Backup build Reject Related procedures Configuring GIVAXI/givClient on page 264 Deleting BPS fallback on page 414 Activating new BPS on BkPRNC (mcRNC) on page 408 Upgrading mcRNC SW builds and BPS on BkPRNC on page 406 Creating BPS fallback on page 404 8.3. MISMATCH means that records exist both in PrPRNC and BkPRNC.5 Interpreting of the system logs Table 154: RNC Resiliency Logs contains 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 154 Test RNC Resiliency Logs Description 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.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 153 Forbidden switch cases (Cont. g Results • INCOMPLETE: means MISSING or MISMATCH. If there is log indicating 'NO IP-MAPPING' 330 DN09203161 Issue: 01E .

• RNC Resiliency Sync log Sync records RNC service adaptation and configuration test result in synchronization phase. UNNECESSARY IPBR/IPRO means that there is extra IPRO configuration in BkPRNC side comparing with PrPRNC.log 331 . UNNECESSARY: records which exist in BkPRNC are not found in PrPRNC or records which is unused in BkPRNC. Auto-adaption is calculated bases on IPBR. Test • g Issue: 01E • • • • Logs 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. be SUCCESS and triggered NOT TEST. CURRENT and EXPECTED are same as previous explanations. It may result in an inconsistent state in BkPRNC after synchronization. COMPLETE: configuration items in BkPRNC are correct. all packets lost.log UNSUCCESS: pinging from source to destination fails. operator needs to check IP mapping configuration. There is risk that later when a different IPRO is configured in PrPRNC. IP Test PART cannot SUCCESS.) Description Results • • or 'INVALID IP-MAPPING'. 20 percent lost rate means 1 packet dropped(5 packets sent during ip test). INCOMPLETE: means MISSING or MISMATCH. SUCCESS: pinging from source to destination succeeds. Test Loaded results are and classified as Active WARNING. all the IPROs binding to same IPBR are only counted as 1. modes.    WCDMA 16 Feature Descriptions and Instructions Table 154 Test RNC solution features RNC Resiliency Logs (Cont. NOT TEST: pinging has not been executed. – DN09203161 MISSING means that records exist in PrPRNC but do not exist in BkPRNC. no packet lost. RNCSRV-ID>. but connectivity is ok. Packet lost rate provided. in Backup mode. 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. PART SUCCESS:some packets lost. configtest_rnc srv<RNCSRVID>. UNSUCCESS. WARNING: configuration error iptest_rncsrv< found.

 If there is log indicating 'NO IP-MAPPING' or 'INVALID IP-MAPPING'. all the IPROs binding to same IPBR are only counted as 1. There is risk that later when a different IPRO is configured in PrPRNC. UNNECESSARY IPBR/IPRO means that there is extra IPRO configuration in BkPRNC side comparing with PrPRNC. refer to SCLI Commands. UNNECESSARY: records which exist in BkPRNC are not found in PrPRNC or records which is unused in BkPRNC. 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. Auto-adaption is calculated bases on IPBR.log For more information.but parameters do not match. EXPECTED means that PrPRNC IPBR/IPRO configurations adapt to BkPRNC according to IP mapping table. UNNECESSAR Y and COMPLETE.log and show file content local /log/iptest_rncsrv223.) Test g Note: This test is done in BkPRNC in Backup mode only. COMPLETE: configuration items in BkPRNC are okay. – – – • • Logs Auto-adaption requires complete IP mapping configuration. The directories which store the logs are available with the following commands: show file content local /log/configtest_rncsrv223. MISMATCH means that records exist both in PrPRNC and BkPRNC. It may result in an inconsistent state in BkPRNC after synchronization. 332 DN09203161 Issue: 01E . Description Results results are classified as INCOMPLETE. operator needs to check IP mapping configuration.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 154 RNC Resiliency Logs (Cont. CURRENT and EXPECTED are same as previous explanations. CURRENT means that IPBR/IPRO configurations exist on BkPRNC.

6. RNCSRV Activation.3.3.2. 3. In BkPRNC. configuration is done at LOADED mode Use cases Overview of possible use cases Table 155 Use cases Use case w Issue: 01E Description Instruction Normal redundancy switch 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 Changing any RNCSRV to RNCSRV-Z at BkPRNC - Redundancy Switchback Redundancy Switchback Redundancy switchback System recovery from redundancy conflict System recovery from redundancy conflict Redundancy conflict NOTICE: In the following simplified examples RNCSRV.2. 2. 7. RNCSRV Inactivation. g 8. or the conversion in SW upgrade has failed.    WCDMA 16 Feature Descriptions and Instructions 8.6. PrPRNC and BkPRNC with fixed ID numbers show the NE behavior in different use cases.3. 6. RNCSRV configuration has been deleted.6 8. Figure 48 Activity model TransitionsinBackupPRNC Waitingfor synchronization System restart 5 6 1 TransitionsinprotectedPRNC Active Active 1 1 2 2 7 Backup 3 Loaded 4 Loaded 1.2. 5.3.1 RNC solution features Redundancy switch Activity model Figure 48: Activity model shows available Activity Modes of BkPRNC and PrPRNC and transitions between them. DN09203161 333 .2 Note: Synchronization is done at Backup mode. RNCSRV is set from BACKUP mode to LOADED mode.3. 3GPP interfaces are blocked. 4. Another RNCSRV is loaded to memory.3. a backup build is loaded to memory for configuration and testing. Initial synchronization has been completed. the base configuration package is loaded to memory.

• • • 1. 4. 5. RNC-cl interface is established. After self-validation BkPRNC restarts. PrPRNC wants to establish a connection and BkPRNC acknowledges it. Figure 49 Normal redundancy switch PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X Redundancyswitch RNCSRV-X 1 Validation 2 RESET 3 RNCSRV-XtoLOADEDmode RNC-cl establishment/ acknowledgement 4 Deactivate 5 Deactivating RNCSRV-Xto LOADEDmode OK 6 RNCSRV-Xto ACTIVEmode ALARM. Once BkPRNC started and RNC-cl is up. g Note: Redundancy switch might be executed also if BkPRNC-Y has RNCSRV-X already in LOADED mode. BkPRNC activates the RNCSRV-X.RNCSRV ACTIVATION 334 DN09203161 Issue: 01E . Redundancy switch is executed at BkPRNC (using text commands when directly connected to RNC or with OMS GUI). 3.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Normal redundancy switch Preconditions Resiliency association between PrPRNC and BkPRNC was created. BkPRNC orders PrPRNC to deactivate its RNCSRV. 6. After getting acknowledgment from PrPRNC. BkPRNC is in BACKUP mode. 2. RNCSRV-X switches to LOADED mode.

whilst RNCSRV-Xisdisabled orenabled. Usermust verifythe statusand isolate PrPRNC. whilst RNCSRV-X is disabled or enabled. 2. Forced redundancy switch is executed. Figure 50 Forced redundancy switch PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X Redundancyswitch RNCSRV-X Validation RESET 1 RNCSRV-XtoLOADEDmode Deactivate No-replytimer expires 2b 2a BkPRNCdoes not recongnise thestatus ofPrPRNC. Preconditions RNC-cl interface is established or not working. ALARM:Deactivationfailed 3 Forcedredundancy switch RNCSRV-X Validation RNCSRV-X to ACTIVEmode ALARM. Normal redundancy switch fails. Resiliency association between PrPRNC and BkPRNC was created. 3. BkPRNC is in BACKUP mode. • • • 1. User must verify the status and isolate PrPRNC. a) BkPRNC does not recognize the status of PrPRNC. b) Timer expires and alarm is raised.    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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. which is indicated by no reply from PrPRNC or PrPRNC replies with error.RNCSRV ACTIVATION Issue: 01E DN09203161 335 .

2.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Changing any RNCSRV to RNCSRV-Z at BkPRNC Preconditions • RNC-cl interface is established. 4. 5. Redundancy switch was executed some time ago. • • Figure 51 Changing any RNCSRV to RNCSRV-Z at BkPRNC BkPRNC-Y RNCSRV-X RNCSRV-Z PrPRNC-X RNCSRV-X BkPRNC-Z RNCSRV-Z RNCSRV-Xin Activemode 1 Deactivate RNCSRV RNCSRV-XinLOADEDmode Load RNCSRV-Z 2 RESET RNCSRV-ZinLOADEDmode 3 Redundancyswitch RNCSRV-Z Deactivate 4 Deactivating RNCSRV-Zto LOADEDmode OK 5 RNCSRV-Z to ACTIVEmode ALARM. After validation. 3. After getting acknowledgment. Request reported for BkPRNC-Y running RNCSRV-Z instead of RNCSRV-X. Command BkPRNC-Y from the ACTIVE to the LOADED mode. BkPRNC-Y activates the RNCSRV-Z. BkPRNC-Y orders PrPRNC-Z to deactivate its service. Load RNCSRV-Z. PrPRNC-X has no active RNCSRV. BkPRNC-Y is running RNCSRVX.RNCSRV ACTIVATION Redundancy Switchback 336 DN09203161 Issue: 01E . 1. Execute redundancy switch.

Verification of PrPRNC proper behavior after switchback. BkPRNC-Y is running RNCSRV-X. PrPRNC-X has been just powered off. SW and configuration). BkPRNC stays in LOADED mode. 3. After command validation. After getting acknowledgment PrPRNC activates RNCSRV-X and sets an alarm. 4. PrPRNC establishes the RNC-cl and performs ”activity mode query”. PrPRNC orders BkPRNC to deactivate RNCSRV-X. PrPRNC-X has not been isolated. 3. 2. PrPRNC is started and it runs RNCSRV-X. When replied. PrPRNC was restored (HW. 1.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Preconditions Redundancy switch was executed. • • • 1.RNCSRV ACTIVATION System recovery from redundancy conflict Preconditions • • • Forced redundancy switch has been executed. Redundancy switchback is triggered at PrPRNC. 2. RNC-cl is established. Figure 52 Redundancy Switchback PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X RNCSRV-XinLOADEDmode 1 Redundancy switchback Validation 2 Deactivate Deactivating RNCSRV-Xto LOADEDmode 3 OK RNCSRV-Xto ACTIVEmode 4a ALARM. PrPRNC is in LOADED mode RNC-cl interface is established. PrPRNC detects the redundancy conflict Issue: 01E DN09203161 337 .

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).3. 338 DN09203161 Issue: 01E . some existing symptoms like alarms in peer NEs.3. drop of KPIs or even loss of O&M connection inform the user about the necessity of the redundancy switch execution. After redundancy switch command. The difference between these two lies in the activity mode the BkPRNC is in when redundancy switch is being executed.2. Figure 53 1 System recovery from redundancy conflict PrPRNC-X RNCSRV-X BkPRNC-Y RNCSRV-X RNCSRV-Xto ACTIVEmode RNCSRV-Xin ACTIVEmode RNC-clestablishment 2 Activitymodequery 3 4 Redundancyconflictdetected Deactivating RNCSRV-X toLOADEDmode 8. The redundancy conflict is cleared.2. g 8.3 Detecting redundancy switch necessity The user considers redundancy switch in the case of: • • • planning and performing any maintenance actions which may cause a break in delivering controller's services catastrophe in the area where the controller's site is placed occurrence of a breakdown precluding an immediate restoration of the controller Although there is no automatic detection or triggering mechanism for redundancy switch.6.6. PrPRNC shuts down the interfaces and remains in the LOADED mode.3.4 Note: Note that if the O&M connection to PrPRNC is interrupted and forced redundancy switch was performed.3. 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. a system reset takes place and the wanted RNCSRV is activated. there is a danger of redundancy conflict unless PrPRNC had been isolated physically.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 4.

 The reason is that the PrPRNC which becomes active after restart and has not been isolated properly. all RNC management operations and events in NetAct are related to the connected RNC. Another redundancy conflict situation is when both PRNCs try to establish the Iub control plane (CP) connections to BTS. If there is RNC-cl O&M interface. as well as KPIs which measure Core Network decrease. 8. If BTS has working control plane connection. In the result.3. If redundancy conflict takes place there will be two PRNCs online with same RNC ID. In case the latter RNC is activated accidentally. it rejects the CP establishment attempt from colliding PRNC. This means. because NetAct cannot determine which of the connected RNCs is the correct one. 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.3. the PRNC which does not control the BTSs will fail with the call setup attempts received from CN. which means it shuts down the interfaces and goes offline. the latter RNC will replace the original RNC in NetAct topology. Thus it is crucial to solve the redundancy conflict quickly.5 Redundancy conflict Origin of redundancy conflict Redundancy conflict is an undesired situation where both PrPRNC and BkPRNC are online and both of them have the same RNCId. is not aware of the previous redundancy switch and goes online in the network. Both the prepared and unprepared redundancy switch can be done in normal or forced mode. In redundancy conflict situation. Avoiding and solving redundancy conflict When PrPRNC restarts and becomes active. Without the interface BkPRNC does not reply to the activity mode query and it is impossible to resolve the redundancy conflict automatically. the system is able to recover the redundancy conflict in few minutes after the RNC-cl O&M interface establishment. that roughly half of the connection setup attempts originated in CN will fail. If BkPRNC is active. only this one will be visible in the NetAct but not the RNC which has the control of the related WBTSs. The benefit of prepared redundancy switch is that no system reset. The ActivePRNC parameter of the RNC object in NetAct can be used to identify which PRNC is actually connected to NetAct.    WCDMA 16 Feature Descriptions and Instructions RNC solution features In prepared redundancy switch. As NetAct topology has only one instance of the RNC. Redundancy conflict in NetAct Redundancy conflict is problematic for NetAct. Thus the best way to prevent a redundancy conflict is to isolate the PrPRNC after redundancy switch.6. In redundancy conflict the second PRNC reports the RNC to the NetAct topology without knowing the same RNCSRV is already active in another PRNC. the PrPRNC switches to LOADED mode. bad end user experience arise. Issue: 01E DN09203161 339 .2. it establishes the RNC-cl O&M interface and performs activity mode query towards BkPRNC. is needed when command is being executed because the correct sW is already in RNC’s memory and the RNCSRV is faster back online. which takes several minutes. Because only one PRNC has BTSs under control. and not necessarily to the RNC to which the WBTSs are connected to. This leads to a situation where both the PrPRNC and BkPRNC attempt to establish an Iub control plane connection with BTS. Redundancy conflict emerges if PrPRNC is restarted accidentally after forced redundancy switch operation.

• RNC Resiliency ►   (The following options are dependent on the PRNC activity mode. the BTS rejects the control plane connection establishment from the BkPRNC. the BTS has neither an O&M nor a CP connection.3. it is crucial to isolate the PrPRNC after the redundancy switch. Therefore. 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.    RNC solution features WCDMA 16 Feature Descriptions and Instructions BTS behavior in a redundancy conflict A BTS is able to tolerate a redundancy conflict.) – – – – – – Activate (available for both Protected PRNC and Backup PRNC) Force Activation (available for both Protected PRNC and Backup PRNC) Deactivate (available for both Protected PRNC and Backup PRNC) Load for Configuration (available only for Backup PRNC with activity mode "Backup") Unload (available only for Backup PRNC) Delete Backup Configuration (available only for Backup PRNC with activity mode "Backup") RNC Resiliency menu Figure 54: RNC Resiliency menu for BkPRNC and Figure 55: RNC Resiliency menu for PrPRNC presents RNC resiliency menus according to RNW object in OMS EM 340 DN09203161 Issue: 01E . If no PRNC is online. As soon as the PRNC establishes the CP connection. 8.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. It operates in a way that both the Iub control plane and O&M connections are towards the same PRNC. The O&M connection follows the control plane connection in order to have them terminated in the same PRNC.3. the BTS establishes the O&M connection to the same PRNC.2. 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. those BTSs are beyond the BkPRNC’s control.

    WCDMA 16 Feature Descriptions and Instructions RNC solution features Figure 54 RNC Resiliency menu for BkPRNC Figure 55 RNC Resiliency menu for PrPRNC Table 156 RNC Resiliency operations menu Operation Description 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 configuration Representing icon 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 list in OMS EM Settings Panel as shown in the Figure 56: Settings panel. Issue: 01E DN09203161 341 .

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. It resembles ordinary Topology Browser. 342 DN09203161 Issue: 01E . This view is designed for the convenience of user who wants to check and/or modify RNW topology which is stored at Backup PRNC.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 56 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. The Figure 57: Show RNW Topology context menu shows action available for RNCSRV object with ActivityMode parameter set to Loaded (which is indicated using L character at RNCSRV object’s icon). but can be displayed only for RNC Services with ActivityMode parameter set to Loaded. awaiting activation in case of emergency problems or maintenance activities.

8. Auto-adaptation Adaptation done automatically according to mapping tables configured by the user. Using Element Manager in OMS shows impacts from the feature on OMS Element Manager. the OMS displays RNW topology structure of certain RNC Service in a separate tab. t Issue: 01E Tip: See also: Base build. Backup build A build that BkPRNC runs when certain RNC service was selected for operation.3.4 Table 157 Network Resiliency related terms Descriptions of feature-related terms Term Descriptions Adaptation Replacing the local information of PrPRNC by local information of BkPRNC.    WCDMA 16 Feature Descriptions and Instructions Figure 57 RNC solution features Show RNW Topology context menu After the user chooses Show RNW Topology option.2. DN09203161 343 . Automatic procedure of autoadaptation The sequence of auto-adaptations of all BkPRNC RNCSRVs one after the other.

 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. In RAN3005. g Note: Conversion is not particularly related to RNC resiliency. BPS Backup Physical RNC System. Conversion Converting a configuration package from old SW build to new SW build. RNC. Conversion is done at any SW upgrade. LRNC is 1-1 with RNC and PRNC. LRNC is 1-1 with RNC but 1-2 with PRNC. All of the builds are in the same SW version (release and CD version) BTS (WBTS) WCDMA BTS BTSOM BTS O&M application protocol - the protocol used in RNC O&M I/F. with or without resiliency. In mcRNC build consists of configuration data and SW image. BkPRNC has a base build for the PRNC and a backup build per each related PrPRNC. In standard system. using BTSOM as the protocol. Configuration package of the base build. Preconfiguring Tip: See also: Backup build.) Term Backup configuration Descriptions Configuration package of a backup build. Configuration (package) The whole configuration of a build. BTS O&M I/F BTS O&M interface - O&M interface between RNC and BTS. BTSSM BTS site manager Build Collection of programs and files performing required functions of a system. t Tip: See also: Build. One BPS contains one base build and up to 16 backup builds. See also PRNC. t Tip: See also: Backup configuration. LRNC Logical RNC - RNC as defined by 3GPP. t Base build A build that BkPRNC runs when no RNC service has been selected for operation.    RNC solution features Table 157 WCDMA 16 Feature Descriptions and Instructions Descriptions of feature-related terms  (Cont. t Base configuration Tip: See also: Base configuration. t Tip: See also RNC O&M I/F and RNC-cl O&M I/F. BTS O&M I/F and RNC-cl O&M I/F. RNC service. mcRNC Multicontroller RNC - RNC with BCN HW 344 DN09203161 Issue: 01E . which does not contain the SW image. BkPRNC Backup PRNC - PRNC that can back up the RNC services of up to 16 PrPRNCs. Configuration committing A command which tells to the system that the user configuration is done and is ready for configuration adaptation and integrity check.

PRNC Physical RNC - RNC HW and SW. t RNC resiliency group Issue: 01E Tip: See also BTS O&M I/F and RNC O&M I/F.) Term Descriptions • HW: 2-8 BCN modules that have Octeon processors. In RNC pool context also: Logical functionality that can run simultaneously as an RNC service in a PRNC. RNC Common meaning: Radio network controller. loaded and active. Redundancy switchback Switch of (activity of) certain RNC from BkPRNC to PrPRNC. A manual configuration step must be done when RNCSRV is created in BkPRNC. 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. RNC activity mode Defines the state in which the RNCSRV is. RNC. which includes the adaptation rules. Object configuration Configuration of the local part of a backup configuration.    WCDMA 16 Feature Descriptions and Instructions Table 157 RNC solution features Descriptions of feature-related terms  (Cont. backup. Unprepared redundancy switch: redundancy switch where the activating RNCSRV not been raised LOADED mode before commanding the switch. Tip: See also BTS O&M I/F and RNC-cl O&M I/F. This term is introduced because BkPRNC cannot be called as a RNC. RNC area Geographical area covered by the BTSs and cells that the RNC controls. Redundancy switch Switch of (activity of) certain RNC from PrPRNC to BkPRNC. using BTSOM as the protocol. • OS: Linux or Simple executive • Platform: FlexiPlatform + IL (IPA Light) NetAct Nokia product for network management OMS O&M server for RNC. t Tip: See also LRNC. 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. A BkPRNC and all the PrPRNCs protected by it. using BTSOM as the protocol. Values are: waiting for synchronization. t RNC O&M I/F RNC O&M interface - O&M interface between OMS and RNC. It does not run RNC service but waits to be switched on in case of PrPRNC outage. and at certain modifications. Operator configure required objects any time after first synchronization but before activating the RNC service. DN09203161 345 . RNC-cl O&M I/F RNC cluster O&M interface (Informally Cluster O&M interface) - O&M interface between two RNCs.

 When RNCSRV is active. When RNCSRV is in LOADED mode. This is useful with long lasting operations. BkPRNC takes the role of PrPRNC in NetAct. PRNC.    RNC solution features Table 157 WCDMA 16 Feature Descriptions and Instructions Descriptions of feature-related terms  (Cont. any TRIAL relevant operation is rejected. In this case. Synchronization Automatic fetching of configuration package of certain RNC service from corresponding PrPRNC and adaptation to BkPRNC according to adaptation rules. RNC. 8. During TRIAL configuration resiliency relevant operation are rejected. Do not execute synchronization when planned operation is ongoing because of risk of synchronization failure. there are some restrictions related to this method: 1. DN09203161 Issue: 01E . Nevertheless. synchronizing data. The failure or success of the operation depends on the phase of other ongoing operation. the status of BkPRNC is visible in NetAct through parameters of RNC object of PrPRNC.5 Table 158 Miscellaneous notes Limitations Limited area Network and network element management tools Description of the limitation • • • Software management • BkPRNC is not visible in NetAct as individual RNC object if RNCSRV is not active in BkPRNC. Some values are: Idle. TRIAL configuration TRIAL configuration is a standard upgrade method applicable only when updated PrPRNC's RNCSRV is in ACTIVE mode. StPRNC Standard PRNC - PRNC that does not participate in RNC resiliency.2. Transition between different RNC modes which can be a separate operation or a phase of redundancy switch or switchback. Do not to execute RNW or IP plan uploads or downloads at PrPRNC during synchronization because of high risk of plan operation failure. • • 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. 2. there is usually no active RNCSRV.) Term Descriptions RNC service (RNCSRV) The instance of an RNC in certain PRNC. g 346 Note: TRIAL is strongly forbidden in BkPRNC. creating RNC service.3. Because BkPRNC operates after the user performed redundancy switch. t RNCSRV activation / deactivation Tip: See also LRNC.

Figure 60 PrPRNC icon Figure 61 BkPRNC icon This feature impacts network management or network element management tools as described in Miscellaneous notes This feature introduces a new RNW object called PRNC. Figure 58 PrPRNC icon Figure 59 BkPRNC icon This feature impacts network management or network element management tools as described in Miscellaneous notes This feature introduces a new RNW object called PRNC.) Limited area NetAct limitations Description of the limitation • • • The BkPRNC object is removed from topology when BkPRNC is in loaded mode. Issue: 01E DN09203161 347 . 8. Impact on interfaces This feature introduces a new RNC-cl O&M interface. This feature introduces a new RNW object called PRNC. The object can be seen in OMS EM regardless of whether the feature is activated or not.3 RAN3005 System impact Interdependencies between features There are no interdependencies between this and any other feature.    WCDMA 16 Feature Descriptions and Instructions Table 158 RNC solution features Limitations (Cont. which represents either PrPRNC or BkPRNC. The object can be seen in OMS EM regardless of whether the feature is activated or not. which represents either PrPRNC or BkPRNC. The object can be seen in OMS EM regardless of whether the feature is activated or not.3. The BkPRNC object disappears from NetAct after the resiliency switchover. which represents either PrPRNC or BkPRNC. Impact on network and network element management tools This feature is not managed using NetAct. The BkPRNC object is added automatically under RNC object in NetAct after resiliency switchback.

 at least one backup BkPRNC is required.2 Flexi Multiradio BTS Flexi Multiradio 10 BTS Flexi Lite BTS WN9. Carrier connectivity license capacity that defines the maximum number of cells that can be unlocked in the RNC. Signaling capacity license capacity that defines 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. Transport links between BTSs under PrRNCs and BkRNC and between BkRNC and core or other controllers must be sufficient to carry whole traffic The user must install the following capacity licenses in BkPRNC: • • • • Iub throughput 1 Mbit/s license capacity that defines the maximum PS downlink Iub throughput.3.1 WL9. AMR capacity 1 Erl license capacity that defines the maximum number of simultaneous AMR radio access bearers.1 WN9. The unit used is Mbit/s.1 MSC SGSN MGW UE Support not required Support not required Support not required Support not required This feature requires Multicontroller RNC HW Rel.4 RAN3005 Reference data Requirements Table 159 RAN3005 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 Available in mcRNC16 earlier release OMS NetAct WCDMA OMS16 NetAct 16.2 Alarms 348 DN09203161 Issue: 01E .    RNC solution features WCDMA 16 Feature Descriptions and Instructions Figure 62 PrPRNC icon Figure 63 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: • • For every 1-16 protected controllers. with the highest configuration (the amount of BkPRNCs depends on the required redundancy level).

    WCDMA 16 Feature Descriptions and Instructions Table 160 RNC solution features New alarms Alarm ID Alarm name 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 161 Related existing alarms Alarm ID Alarm name 821 OMS SWITCHOVER HAS BEEN PERFORMED 3295 LICENCE CAPACITY EXCEEDED 3360 LICENSE NOT READY 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 162 New parameters introduced by RAN3005 Full Name Issue: 01E Abbreviated name Managed object OAM Connection Establishment Retry Counter ConnectionRetryCounter PRNC OMS backup IP Address OMSBackupIpAddress PRNC OMS IP Address OMSIpAddress 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 Reason RestartReason PRNC Secondary OMS IP address SecOMSIpAddress PRNC DN09203161 349 .

    RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 162 New parameters introduced by RAN3005 (Cont.) Full Name 350 Abbreviated name Managed object PRNC Serving OMS ServingOMS Serving OMS Admin setting ServingOMSAdminSetting PRNC Serving OMS Switchover Request ServingOMSSwoRequest PRNC Activity Mode ActivityMode PRNC/RNCSRV RNC service Change Origin RNCSRVChangeOrigin PRNC/RNCSRV RNC SERVICE Identifier RNCSRVId PRNC/RNCSRV RNC service status 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 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 DN09203161 Issue: 01E .

) Full Name Abbreviated name Managed object 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 backup PRNC BackupUpdateTime RNC/BKPRNC 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 ActivePRNC RNC OMS IP Address OMSIpAddress RNC Secondary OMS IP address SecOMSIpAddress RNC Serving OMS Admin setting ServingOMSAdminSetting RNC Serving OMS Switchover Request ServingOMSSwoRequest OAM Connection Establishment Retry Counter ConnectionRetryCounter RNC RNC Client TLS Mode RncClientTLSMode Table 163 RNC RNC Parameters modified by RAN3005 Full Name Abbreviated name Managed object RNC Identifier RNCId RNC RNC Options RNCOptions RNC Table 164 BTS Parameters Full name Abbreviated name Additional RNC configuration structure Issue: 01E RNC solution features addRncConfig DN09203161 Managed object TMPAR 351 .    WCDMA 16 Feature Descriptions and Instructions Table 162 New parameters introduced by RAN3005 (Cont.

44.43.51.69.52.52.) Full name g Abbreviated name Managed object Currently used far end SCTP tunnel IP address currentSctpIpAddress TMPAR Far End SCTP Subnet IP Address farEndSctpSubnetIpAddress TMPAR Far End SCTP Subnet Mask 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.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 164 BTS Parameters (Cont.43.234/32 rolebtsom: 10.43.5 Activating RAN3005: Network Resiliency for mcRNC Purpose This chapter provides procedures on how to activate RAN3005: Network Resiliency for mcRNC feature.43.254 OMSO&M interfaceconnection PrPRNC-223 BkPRNC-200 O&M RNCId-223 RNCId-200 RNCClusterO&Minterface SSHIP: 10. Assumed and expected network plan is shown in the Figure 64: Network transport plan.3.226/32 roleoms: 10.43. Sales information Table 165 RAN3005 Sales information BSW/ASW ASW License control in network element RNC LK Activated by default No 8.234/32 rolebtsom: 10.235/32 SSHIP: 10.52. Figure 64 Network transport plan OMS 10.51.226/32 roleoms: 10.235/32 instandbyforbackup serviceactivation 352 DN09203161 Issue: 01E .51.43.

3.1 RNC solution features Enlarging QNDRBD Modifying the VG_System LDAP configuration.01.5. Before you start Ensure you have root login credentials. 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 - 2 Confirm that the LDAP servers are running correctly. Refer to SCLI 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. Log in as a root.5.1.3.1 8.    WCDMA 16 Feature Descriptions and Instructions 8.sh Step result This command will prompt the following printout: ********************* WARNING ******************** This script will modify LDAP partition 3 configurable size to 50494 MB Issue: 01E DN09203161 353 . Procedure 1 Confirm that both CFPUs are running correctly. Step example #/opt/nsn/SS_ILCommon/bin/enlargeQNDRBD.modify_LDAP.

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 354 DN09203161 Issue: 01E . wait for the card to come up. Modify VG_System LDAP configuration successfully Please refer to QNDRBD enlarge guide to synchronize hard disk 8. g Note: The <node_name> indicates the node which is the peer to the one the user is currently logged into.3. During the lock and unlock procedure. When you log into CFPU-0. Before you start Ensure logging in as root authority.    RNC solution features WCDMA 16 Feature Descriptions and Instructions ********************* WARNING ******************** Are you sure you want to proceed? [Y/n]: y<ENTER> The operation is successful if this printout occurred.5. the <node_name> is CFPU-1 respectively.1. and vice verse.2 Re-initialize hard disk to enlarge VG_System manually Procedure for initializing the disk in both controller modules to enlarge VG_System manually. The RNC with a larger configuration is more time-consuming.

Wait a few seconds before proceeding to the next step.    WCDMA 16 Feature Descriptions and Instructions 3 RNC solution features Enable network boot for the node. 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> 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 Issue: 01E DN09203161 355 . Sub-steps a) Log in as root: Step example > set user username root b) Power-up the node.

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. because previous step may take some time to reboot the system. Step example > initialise hw Wait for about 15 minutes. enter the following command. After this time the following output is displayed: Hardware successfully initialized 6 Reboot the node from local disk: > set user username root # hwcli -nr -B 2 <node_name> # exit 356 DN09203161 Issue: 01E . you should wait for about three minutes and then try again. S7-B2 capacity step setup might take more than three minutes. If connecting to the node by SSH failed. Don't proceed to next step until watchdog is disabled. 5 Initialize hard disk for node.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Step example ssh CFPU-1 \ wdctl -d exit g Note: To disable the watchdog on the node through SSH. 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 initialization.

. 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..] sync'ed: 18. The initialization process of the new disk is not ready until the synchronization is successfully completed..872 (30. 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 Issue: 01E DN09203161 357 ... 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 [==>. The node will restart and synchronize the Distributed Replicated Block Devices (DRBD). Actual time depends on the size of DRBD.744) K/sec The synchronization is finished if the oos value for all blocks is 0.. g Note: Do not restart the node during the DRBD synchronization..    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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.....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..9% (12176/14996)M finish: 0:05:37 speed: 36. 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-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) 358 DN09203161 Issue: 01E . They should be identical for both managed objects.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Compare the blocks. 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.

 and the SSH session must be started again.    WCDMA 16 Feature Descriptions and Instructions RNC solution features /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. Issue: 01E DN09203161 359 . 10 Repeat the procedure for the second CFPU. Perform steps Lock CFPU: to Switchover SSH to another CFPU:. 9 Switchover SSH to another CFPU: 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. If you have synchronized CFPU-1 as above. and vice verse. then replace <node_name> to CFPU-0.

360 DN09203161 Issue: 01E ...    RNC solution features 8..sh Step result Checking SSH connection.resize_DRBD... Current QNDRBD volume size in node CFPU-1: 2900 MB Checking QNDRBD size in node CFPU-0. 2 Confirm that both CFPUs are running correctly. SSH connection for nodes CFPU-1 CFPU-0: OK Checking QNDRBD size in node CFPU-1.3..1.3 WCDMA 16 Feature Descriptions and Instructions Enlarging QNDRBD logical volume and corresponding DRBD file system Procedure 1 Log in as a root.5.. Current QNDRBD volume size in node CFPU-0: 2900 MB QNDRBD device name: /dev/drbd2 Checking VG_System VFree size in node CFPU-1.02.. 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 - 3 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.

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..r.1...    WCDMA 16 Feature Descriptions and Instructions RNC solution features Checking VG_System VFree size in node CFPU-0.88 GiB Extending logical volume QNDRBD to 2.1...88 GiB Logical volume QNDRBD successfully resized QNDRBD logical volume is resized successfully Scanning volume groups in node CFPU-0...1.r..bcn.bcn.5...12. This may take a while..88 GiB Extending logical volume QNDRBD to 2.20141223. Rounding up size to full physical extent 2.6/FB20141224112056/kernelmap for node CFPU-0 Running mkboot -n CFPU-1 /mnt/config/R_IL_14. Note: This command might take a long time before showing any results.12.5.88 GiB Logical volume QNDRBD successfully resized QNDRBD logical volume is resized successfully Scanning volume groups in node CFPU-1..20141223.. Rounding up size to full physical extent 2. Found volume group "VG_CFPU-0" using metadata type lvm2 Found volume group "VG_System" using metadata type lvm2 Volume groups are scanned Issue: 01E DN09203161 361 .bcn.1. Reading all physical volumes.12. DO NOT operate the cluster! QNDRBD logical volume size in LDAP: 2900 Modifying QNDRBD LDAP configuration.6FB20141224112056 Running mkboot /mnt/config/R_IL_14.12. Overwriting configuration config-R_IL_14.5....6-FB20141224112056 completed successfully Running startup actions for the configuration config-R_IL_14.6/FB20141224112056/kernelmap --nodist for node CFPU-1 Resizing QNDRBD logical volume in node CFPU-1...r. This may take a while.bcn.r. 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. Reading all physical volumes.20141223. Please be patient.20141223.5. ldap_initialize( ldap://directory:389 ) Saving snapshot.

The filesystem on /dev/drbd2 is now 755679 blocks long.8G 2% /mnt/QNOMU /dev/drbd1 20G 75M 19G 1% /var/opt/nsn/SS_ILOMU 8. No need to perform any step. on-line resizing required old desc_blocks = 1.0G 35M 1. # vgs VG #PV #LV #SN Attr VSize VFree VG_CFPU-0 1 9 0 wz--n. <disc>: “disc0” or “disc1”.31g 9.3. Table 167 Error prompts Error <Error> Connecting to <CFPU> by SSH failed.. The prompt indicates that you have enlarged QNDRBD volume to expected size in the system.49.4 g Troubleshooting Note: <CFPU>: “CFPU-0” or “CFPU-1”.08g 179.. run below commands to verify the DRBD size: 1. # df -kh |grep -i omu /dev/mapper/VG_CFPU--0-QNOMU 2. please find the solution proper to the following corresponding prompts: Table 166 Warning prompts Warning Analysis Solution <Warning> This script has been executed. The prompt indicates that you have performed this operation.9 (22-Aug-2009) Filesystem at /dev/drbd2 is mounted on /var/opt/nsn/SS_ILOMU.41. DRBD filesystem is resized successfully Waiting DRBD synchronization to complete after resizing Synchronization completed QNDRBD logical volume is resized successfully! After this procedure. DRBD device is resized successfully Resizing DRBD filesystem. for target node. <Warning> All QNDRBD volumes have been enlarged.89g 2. There is no need to execute it again.53g VG_System 1 11 0 wz--n. resize2fs 1..1. You can continue to perform stepRe-initialize hard disk to enlarge VG_System manually.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Resizing DRBD device.229. new_desc_blocks = 1 Performing an on-line resize of /dev/drbd2 to 755679 (4k) blocks.. Troubleshooting for modifying VG_System LDAP If after modifying VG_System LDAP configuration any unsuccessful prompts occur.. DN09203161 Issue: 01E . VG_System configuration has been modified in LDAP. There is no need to re-size again. 362 Analysis Solution Cannot connect to <CFPU> by Check the network connection SSH.5.

- See <Error> Getting disc partition information from LDAP failed. please check LDAP dn: <Error> Adding new fshwPartitionId:Partition3 in LDAP FP2CLADefaultSysVG failed. You can check fsconfigure log (/var/log/fsconfigure. - If any error prompt occurs. please check LDAP dn: The modification of LDAP configuration has failed. Please check the LDAP server state by using the proper command. please collect syslog and screen output. and contact NOKIA TS and R&D team for investigation. current LDAP modification will be lost after system restart. collect syslog and screen output. - See <Error> Getting disc partition information from LDAP failed. You can remove useless deliveries or snapshots. you can save a snapshot by the SCLI save snapshot command.) Error Analysis Solution <Error> VG_CFPU free space is not enough. - See <Error> Getting disc partition information from LDAP failed. Troubleshooting for enlarging VG_System LDAP configuration If after enlarging VG_System LDAP configuration any unsuccessful prompts occur. <Error> Getting disc partition information from LDAP failed.31g 9. please check LDAP dn: Any other error prompt. After the issue is solved.89g <Error> Saving snapshot failed.68g 37. please check LDAP dn: <Error> Modifying LDAP <disc> Partition3 instance failed. but saving snapshot failed. There is not enough free space on the disc partition to enlarge VG_System volume.39g VG_System 1 11 0 wz--n49. <Error> Searching LDAP DN:FP2CLADefaultSysVG failed. and check free space by using the vgs command: VG #PV #LV #SN Attr VSize VFree VG_CFPU-0 1 11 0 wz--n86. The modification will be lost after system restart. - See <Error> Getting disc partition information from LDAP failed. please find the solution proper to the following corresponding prompts: Issue: 01E DN09203161 363 . or you can run this script again. please check LDAP dn: <Error> Removing fshwPartitionId:Partition3 from LDAP DN:FP2CLADefaultSysVG failed. If it is active. VG_System configuration in LDAP has been modified. log).    WCDMA 16 Feature Descriptions and Instructions Table 167 RNC solution features Error prompts  (Cont. You need at least 28G free space in VG_CPFU. it will attempt to save the snapshot for you.

<Error> DRBD device (<DRBD_device>) role abnormal:<abnormal status> Enlarge QNDRBD requires DRBD disk role to be “Primary/Secondary” or “Secondary/Primary”. Qndrbd_resize. After the issue is solved. this error will be raised. Check the device name with this command and after solving the problem. <Error> Cannot get QNDRBD device name by command fscmfcli -su /<hostname>. Qndrbd_resize. this error will occur. or you can run this script again. The modification will be lost after system restart. if the disk state is not “UpToDate”. The most likely reason is that you have not enlarged the VG_System in both CFPU nodes. If one of OMU RU or OMU RG is locked. Run the lvs command and check what error is reported. Qndrbd_resize. please check this command result.sh needs to get a QNDRBD device name (for example drbd2) by using the command fscmfcli –su /<hostname>.sh will Enlarge the VG_System in report this error if there is not both CFPU nodes before enough free space for running this script. rerun qndrbd_resize.sh will indicate this error. but saving snapshot failed. <Error> Cannot get QNDRBD logical volume size in node <node>. for target node. “UpToDate/UpToDate”. You can check fsconfigure log (/var/log/fsconfigure. qndrbd_resize. If the fscmfcli report fails. please enlarge VG_System logical group first. current LDAP modification will be lost after system restart. you can save a snapshot by the SCLI save snapshot command. Cannot connect to <CFPU> by Check the network connection SSH. Please check QNOMU RU and confirm it is active. Ensure both OMUs are unlocked. this error will be indicated.sh <Error> VFree size is not enough for QNDRBD re-size.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Table 168 Error prompts Error 364 Analysis Solution <Error> Connecting to <CFPU> by SSH failed.sh needs to check the QNDRBD logical volume size by using the lvs command. If the QNDRBD logical volume size cannot be obtained by using the lvs command. please run lvs and check the output. log). it will attempt to save the snapshot for you. VG_System configuration in LDAP has been modified. <Error> Extending logical volume failed! - Please contact NOKIA TS team and R&D team for investigation. <Error> DRBD device Enlarging QNDRBD requires (<DRBD_device>) disk state is DRBD disk state is not “UpToDate/UpToDate”. DN09203161 Issue: 01E . QNDRBD resizing (VFree should at least 18G). <Error> Saving snapshot failed.

43.) Error 8.3. Step example add networking address /QNOMU iface eth0 ip-address 10.51. btsom and rnccl role IP address on PrPRNC and BkPRNC.43.234/32 user /QNHTTPD role oms role rnccl add networking address /QNOMU iface eth0 ip-address 10.234/32 user /QNHTTPD role oms role rnccl add networking address /QNOMU iface eth0 ip-address 10.5. which are used for OMS O&M interface and RNC cluster O&M interface. Procedure 1 Add OMS and BTSOM IP addresses on PrPRNC.43.43. <Error> Resizing DRBD file system failed! Please contact NOKIA TS team and R&D team for investigation.    WCDMA 16 Feature Descriptions and Instructions Table 168 RNC solution features Error prompts  (Cont.235/32 role btsom Issue: 01E DN09203161 365 .235/32 role btsom 2 Add OMS and BTSOM IP addresses on BkPRNC. - Commission PrPRNC Before you start Add oms.51. Step example add networking address /QNOMU iface eth0 ip-address 10. Configure addresses used for OMS O&M interface and RNC cluster O&M interface.52.52. Configure addresses used for OMS O&M interface and RNC cluster O&M interface.2 Analysis Solution <Error> Resizing DRBD device failed! Please contact NOKIA TS team and R&D team for investigation.

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 ---------------------------------------------------------------------PRNC information: ----------------------------------------------------PRNC ID: 223 PRNC name: RNC-223 PRNC mode: 1 (Primary) PRNC IP address: 10.43.43.18 Backup OMS IP address: 0.0.43.7.12.63 2 Interrogate PRNC information 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.226 Restart reason: 0 (Normal restart) Primary OMS IP address: 10.3 WCDMA 16 Feature Descriptions and Instructions 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.5.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.    RNC solution features 8.98 prncname RNC-223 sec-oms-ip 10.43.98 Secondary OMS IP address: 10.0.51.98 Secondary OMS IP address: 10.12.0.43.43.7.0.43.0 366 DN09203161 Issue: 01E .7.18 Backup OMS IP address: 0.3.12.

5 8.5.3.    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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.7.98 prncid 200 prncname RNC-200 sec-oms-ip 10. RNPS.43.12. RNRLC. RNFC.43.18 Issue: 01E DN09203161 367 . RNAC. RNTRM. RNMOBI. 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.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.51.4 Install all the required licenses in the PrPRNC. Copy the file with RNW PLAN (for example RNWPLAND.XML) to /mnt/QNOMU/plan and execute it. RNHSPA.

43.98 Current serving OMS: 1 (primary OMS) Serving OMS selection: 0 (automatic) Connection retry count: 15 RNC Client TLS mode: 2 (Probing) ----------------------------------------------------RNC-OMS O&M connection status: ACTIVE 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.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 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.12.43.226 Restart reason: 0 (Normal restart) Primary OMS IP address: 10. 368 DN09203161 Issue: 01E .43.18 Backup OMS IP address: 10.52.52.12.98 Secondary OMS IP address: 10.20 2 Interrogate PRNC information 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.7.226 - Number of RNCSRV displayed = 0.43.

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 : : : : : : : : : : Issue: 01E 200 not updated 10.5 RNC solution features Create BkPRNC object at PrPRNC (mcRNC) Procedure 1 Create BkPRNC object Step example >add network-resiliency association backup-prnc id 200 ip 10.3.234 not updated off not updated not updated not updated true disabled DN09203161 369 .51.43.43.234 Step result CFPU-0@RNC-223 [2014-11-19 16:08:47 +0800] BkPRNC-200 is added successfully.    WCDMA 16 Feature Descriptions and Instructions 8.5. 2 Interrogate BkPRNC object on PrPRNC Step example >show network-resiliency association Step result CFPU-0@RNC-223 [2014-11-19 16:08:55 +0800] RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10.52.52.43.

Service status 8.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. When Service status changed from creating service to idle the service has been created successfully.52.3. ipaa Data synchronization state : unblocked Data synchronization schedule : -. Creating service takes approximately one and a half minutes. 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 [2014-12-12 16:38:45 +0800] : BkPRNC : 200 : 10.226 RNC service ID : 223 Activity mode : waiting for synchronization Service status : creating service Auto trigger operation : datasync.6 WCDMA 16 Feature Descriptions and Instructions 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. 370 DN09203161 Issue: 01E .    RNC solution features 8.7 : idle Configuring secure RNC-cl O&M interface This chapter describes how to enable security for RNC-cl interface.5.5.3.43.

pem key-file /home/OMU_private. Install the previously copied certificates with the following commands: In BkPRNC: 1. e) Change the Client TLS mode to FORCED in PrPRNC.pem ca-id rootca 2.pem ca-id rootca 2. set security cert BTSOMClient ee-cert cert-file /home/OMU_cert. Perform these steps in both PrPRNC and BkPRNC.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Procedure 1 Configure cluster O&M interface. set security cert BTSOMClient ca-cert cert-file /home/ca-certificate.pem d) Create SSL/TLS layer definition. >set network-resiliency association backup-prnc tls-mode forced Step result CFPU-0@RNC-223 Parameter of BkPRNC-200 is modified.pem OMU_private.pem key-file /home/OMU_private. set security cert BTSOMServer ca-cert cert-file /home/ca-certificate.pem b) Check the files presence.pem ca-certificate. set security cert BTSOMServer ee-cert cert-file /home/OMU_cert. ls -a /home c) Install the certificates. Issue: 01E DN09203161 [2015-07-25 14:25:14 +0530] 371 . • • • OMU_cert.pem In PrPRNC: 1. Sub-steps a) Copy the certificate files into both the PrPRNC and BkPRNC under /home folder.

51.234:8023 Check the configuration correctness.52. Step result 2 Configure RNC-OMS interface.51.43. Copy the certificate files to /tmp folder with the following commands: Step example • • 372 cp /home/Nemuadmin/ca-certificate. >show network-resiliency association CFPU-0@RNC-223 RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10. Sub-steps a) Copy the certificate files to OMS.pem /tmp DN09203161 Issue: 01E .234 backup forced critical less than 100% 24-07-2015.43.43.234:62254 ESTABLISHED 8525/boimed f) 10.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Previous TLS client mode Current TLS client mode : off : forced Check that the cluster link is enabled.pem /tmp cp /home/Nemuadmin/cert.18:14 false enabled Check the 8023 port is opened.226 [2015-07-25 14:25:23 +0530] 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. # netstat -taunp | grep 8023 tcp 0 0 10.52.

pem -key-file /tmp/private. enter the following commands: 1. 8.5.pem c) Activate the RAN1102: Secure Management Interface feature: set license feature-mgmt code 0000001244 feature-adminstate on Step result Feature Name : SecureMngtInterface Feature Code : 0000001244 Type : on/off Admin State + License State = Combined Operational State : on + on = on Feature Description : RAN1102 RAN1206 Secure Mngt Interface d) Change the Client TLS mode to PROBING (in OMS).pem /tmp b) Install the certificates.    WCDMA 16 Feature Descriptions and Instructions • RNC solution features cp /home/Nemuadmin/private.pem 2.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. In OMS. omscertificate install-ee-cert -cert-file /tmp/cert. omscertificate install-ca-cert -cert-file /tmp/ca- certificate.3. Issue: 01E DN09203161 373 . set radio-network omsconn-config client-tls-mode probing f) Check the configuration correctness: Step result Port 8003 is used. 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).

51. The new IP must be added at both the PrPRNC and BkPRNC with the rnccl assigned role.52.51. The rnccl role must not be assigned to multiple IPs in either BkPRNC or PrPRNC. There must be only one IP configured with role rnccl.42/32 backuprnc-vrf iub1 backup-rnc-subnet 10. Step example add networking address dedicated /QNOMU iface eth0 ipaddress 10.43.42/32 Type the following SCLI: start network-resiliency synchronize rnc- service-id 223 ipaa off The result is indicated by the following command: CFPU-0@RNC-200 +0800] [2015-01-08 09:11:37 This command is executed successful.3.43. Procedure 1 Create dedicated interface for BkPRNC's OMU.236/32 /QNOMU /QNHTTPD rnccl Synchronization (mcRNC) Before you start Subnet mapping should be configured on base build of BkPRNC. 374 DN09203161 Issue: 01E .236/32 user /QNHTTPD role rnccl 2 Check the address assigned to rnccl Step example show networking address role rnccl Step result CFPU-0@RNC-223 IP addresses in eth0 address owner user role 8.51.9 [2015-07-13 16:14:55 +0530] default instance: : : : : 10.43.43.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Purpose The operator must add new IP address at both PrPRNC and BkPRNC. The same IP is given as input for creating BKPRNC object in PrPRNC. add network-resiliency subnet-mapping rnc-service-id 223 protect-rnc-vrf iub1 protect-rnc-subnet 10.5.

00:00 no backup data for rnc service 0% enabled Before starting periodic synchronization. g Note: during synchronization. 2 Interrogate Synchronization status Step example >show network-resiliency association rnc-service-id 223 Step result CFPU-0@RNC-200 [2015-01-08 09:11:45 +0800] RNC type PRNC ID PRNC IP : BkPRNC : 200 : 10. the “Activity mode” should be “backup”. the “Backup update time” will be updated. /srv/Log/log/configtest_rncsrv223.log will be generated.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. DN09203161 375 . after synchronization succeeds. the “Service status” will change on different phases: downloading doing basic adaptionidle.43.52.    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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. the synchronization starts automatically. set the schedule time firstly. 3 g Issue: 01E 223 waiting for synchronization downloading datasync. Note: When the time is expired. ipaa unblocked -.

Previous data synchronization schedule : -.3.00:00 Current data synchronization schedule : MON.FRI.FRI. ipaa Current auto trigger operation : datasync Display the result with show network-resiliency association CFPU-0@RNC-200 : BkPRNC PRNC ID PRNC IP Loaded RNC service : 200 : 10.5.TUE. when the time is expired.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 4 Start Periodic Synchronization with ipaa (IP auto adaption) off Before starting periodic synchronization.WED.SAT.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.SUN.THU.52.43.10 [2015-07-24 16:09:47 +0530]RNC type 223 waiting for synchronization idle datasync unblocked MON. the synchronization starts automatically.SUN.10:40 no backup data for rnc service 0% enabled Configuring RNCSRV at BkPRNC (mcRNC) Procedure 1 Load RNC service Type the following SCLI: Step example >start network-resiliency load rnc-service-id 223 376 DN09203161 Issue: 01E . 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.THU.TUE.WED. set the schedule time firstly.10:40 Previous auto trigger operation : datasync.SAT.

Please be patient. ipaa unblocked -.52. ipro is unnecessary. On backup build.00:00 08-01-2015. If ipaa is on when do data synchronization.    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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. ipro. Issue: 01E DN09203161 377 .43. configure the resources such as: CBC ip address. QNUP&QNIUB ip address. 2 Interrogate using SCLI command: Step example >show network-resiliency association rnc-service-id 223 Step result CFPU-0@RNC-200 [2015-01-08 16:10:51 +0800] RNC type PRNC ID PRNC IP : BkPRNC : 200 : 10.09:17 0% enabled Do configuration on backup build.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 backup loading rnc service datasync.

2. 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 378 DN09203161 Issue: 01E .    RNC solution features WCDMA 16 Feature Descriptions and Instructions Result 8. Step example add networking address /QNCFCP iface eth0 ip-address 2.43.66 10.5.12 Configure VRRP loadsharing.11 Configure network interfaces Procedure 1 Add CBC IP address.52.36 Association2 IP 10.24.63.52.2/32 role cbc 2 8.63.2.24. MSC configuration for Core Network (mcRNC) Purpose Table 169 MSC configuration BkPRNC MSC Association1 IP 10.5.43.3.3.36 Point code 8364 8526 Configure alternate IP address of BkPRNC acting as PrPRNC-1 towards MSC Procedure 1 Add a new signaling service access point.162 10.

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.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. 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.24.52.66 local-client-port 2906 primary-remote-ip-addr 10.43.24. 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 Add a new subsystem (for RANAP).    WCDMA 16 Feature Descriptions and Instructions 3 RNC solution features Add two M3UA associations. 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.43.63.52.162 local-client-port 2906 primary-remote-ip-addr 10. 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] Issue: 01E DN09203161 379 .63.

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.43.52.63.43.36 remote-port : 2905 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : client priority : 1 status : connection_down ------------------------------------------------------------------------------ 8.52.3.24.66 local-client-port : 2906 vrf-name : iuiurcp node : /EIPU-0 remote-as-name : MSC primary-remote-ip-addr : 10.5. 380 DN09203161 Issue: 01E .    RNC solution features WCDMA 16 Feature Descriptions and Instructions M3UA Association -----------------------------------------------------------------------------association id : 1 local-as-name : LASMSC primary-local-ip-addr : 10.162 local-client-port : 2906 vrf-name : iuiurcp node : /EIPU-1 remote-as-name : MSC primary-remote-ip-addr : 10.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 : 2 local-as-name : LASMSC primary-local-ip-addr : 10.24.63.

43. 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 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.176 Association2 IP 10.71.52.71.52.4.4.52.43.52.178 local-client-port 2906 primary-remote-ip-addr 10.98 local-client-port 2906 primary-remote-ip-addr 10.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Purpose Table 170 SGSN configuration BkPRNC Association1 IP 10.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.178 10.43.98 SGSN 10.71.179 remote-port 2906 node /EIPU-1 role client exchange-mode double sctp-profile SS7 Issue: 01E DN09203161 381 .4.71.179 Point code 8364 8412 Procedure 1 Add a new signaling service access point.43.4.

52.176 remote-port : 2906 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : client priority : 1 382 DN09203161 Issue: 01E .    RNC solution features WCDMA 16 Feature Descriptions and Instructions 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 Step result M3UA Association -----------------------------------------------------------------------------association id : 3 local-as-name : LASSGSN primary-local-ip-addr : 10.43.71.98 local-client-port : 2906 vrf-name : iuiurcp node : /EIPU-0 remote-as-name : SGSN primary-remote-ip-addr : 10.4.

52.178 local-client-port : 2906 vrf-name : iuiurcp node : /EIPU-1 remote-as-name : SGSN primary-remote-ip-addr : 10.43.146 10.5.3.43.179 remote-port : 2906 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : client priority : 1 status : connection_down ------------------------------------------------------------------------------ 8.52.43.14 Configuring Iur interface for mcRNC network resiliency Procedure for Iur interface configuration. Purpose BkPRNC Peer PRNC Association1 IP 10.46.71.130 10. Step example add signaling service-access-point id 3 name SAP3 network-appearance 3 network-indicator NA0 network-type itu Issue: 01E DN09203161 383 .    WCDMA 16 Feature Descriptions and Instructions RNC solution features status : connection_down -----------------------------------------------------------------------------M3UA Association -----------------------------------------------------------------------------association id : 4 local-as-name : LASSGSN primary-local-ip-addr : 10.202 Point code 8364 8370 Procedure 1 Add a new signaling service access point (AP).4.46.43.193 Association2 IP 10.52.43.

52.43.146 local-server-port 2906 primary-remote-ip-addr 10. 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 384 DN09203161 Issue: 01E .46. Step example add signaling sccp own-point-code id 3 local-as-name LASIUR name LASIUR add signaling sccp destination-point-code id 6 remote-as-name IUR name IUR 5 Add a new subsystem.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.43.130 local-server-port 2906 primary-remote-ip-addr 10.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 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.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 2 Add a new local AS and remote AS.46.43.

43.193 remote-port : 2906 exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : server priority : 1 status : connection_down ----------------------------------------------------------------------------M3UA Association ----------------------------------------------------------------------------association id : 6 local-as-name : LASIUR primary-local-ip-addr : 10.43.43.202 remote-port : 2906 Issue: 01E DN09203161 385 .46.46.52.43.    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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.146 local-server-port : 2906 vrf-name : iuiurcp node : /EIPU-1 remote-as-name : IUR primary-remote-ip-addr : 10.130 local-server-port : 2906 vrf-name : iuiurcp node : /EIPU-0 remote-as-name : IUR primary-remote-ip-addr : 10.52.

00:00 14-01-2015.52.3.    RNC solution features WCDMA 16 Feature Descriptions and Instructions exchange-mode : double sctp-profile : SS7 communication-type : ipsp admin-state : enabled role : server priority : 1 status : connection_down ----------------------------------------------------------------------------- 8.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 386 : : : : : : : : : 223 loaded doing basic adaptation datasync.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 Step result CFPU-0@RNC-223 RNC type PRNC ID PRNC IP [2015-01-14 16:39:53 +0800] : BkPRNC : 200 : 10. ipaa unblocked -.09:17 less than 100% enabled DN09203161 Issue: 01E .43.5.

    WCDMA 16 Feature Descriptions and Instructions 3 RNC solution features 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 mapping is specific for RNCSRV. 8.log. 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.52 iuiurup1 10.16 Mapping IP address Purpose This procedure is necessary to perform auto-adaptation successfully.36 iub2 10.43. thus it must be done at BkPRNC.51. the Backup completeness factor is 100%. 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.51.5.----------------.3.----------------.43.4 iuiurup1 10.5 Issue: 01E DN09203161 387 .51.43.43.51.

22 PrPRNC total unmapped IP count: 8.    RNC solution features WCDMA 16 Feature Descriptions and Instructions iuiurup1 iuiurup2 iuiurup2 iuiurup2 10. BkPRNC total unmapped IP count: 6.52.51.52.43.43.20 10.43.43.43.51.43.43.22 STATUS ------VALID VALID VALID VALID VALID VALID INFO ----IUIURUP1 IUIURUP1 IUIURUP1 IUIURUP2 IUIURUP2 IUIURUP2 Total matched IP mapping count: 6 388 DN09203161 Issue: 01E .4 protect-rnc-vrf iuiurup1 backup-rnc-ip 10.5 10.43.43.43.----------------iuiurup1 10.43.21 10.43.52.22 iuiurup1 iuiurup1 iuiurup1 iuiurup2 iuiurup2 iuiurup2 10.43.5 10.5 iuiurup1 10. There should not be any unmapped IPs under the PrPRNCIP section. g Note: All the unmapped IPs of the PrPRNC should be mapped with proper BkPRNC IP.51.51.51.52.52.6 10.43.52.52.52.51.43.52.20 iuiurup2 10.51. 3 Interrogate mapped IP addressing data from RNCSRV of PrPRNC Step example show network-resiliency ip-mapping rnc-service-id 223 Step result CFPU-0@RNC-223 RNC service [223] IP mapping: PrPRNCvrf PrPRNCIP ----------------. 2 Map PrPRNC IP address to BkPRNC IP address Step example add network-resiliency ip-mapping protect-rnc-ip 10.43.21 10.20 10.43.6 10.21 iuiurup2 10.52.51.43.52.22 [2015-07-09 14:45:13 +0530] BkPRNCvrf ----------------iuiurup1 iuiurup1 iuiurup1 iuiurup2 iuiurup2 iuiurup2 BkPRNCIP ----------------10.43.4 iuiurup1 10.43.20 10.52.21 10.4 10.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.51.6 10.43.43.4 10.43.51.51.52.6 iuiurup2 10.43.

 the PrPRNC cannot be shut down from BkPRNC but it has to be shutdown manually.3. Result When configuration is done properly. Procedure 1 Trigger the switchover with SCLI or via OMS. An alarm indicates the loss of RNC-cl O&M interface.7 Deactivating RAN3005: Network Resiliency for mcRNC Procedure 1 Remove RNC association at PrPRNC. which is verified by performing redundancy switch. 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. IP connectivity test helps to find any problems in IP layer. Troubleshooting in case of redundancy switch failure If the RNC-cl O&M interface is down.    WCDMA 16 Feature Descriptions and Instructions RNC solution features 8. Follow the instructions described in Performing normal redundancy switch from PrPRNC to BkPRNC.6 Verifying RAN3005: Network Resiliency for mcRNC Before you start Correct configuration of PrPRNC and BkPRNC provides synchronization possibility between PrPRNC and BkPRNC. 8. 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 Issue: 01E DN09203161 389 . the PrPRNC automatically shuts down 3GPP services and BkPRNC starts the services.3. the BkPRNC starts and the 3GPP services are back online. what might be a reason of verification failure. After restart.

The O&M application SW sends BTS O&M interface ConfigurationChangeNotification message to OMS when BkPRNC object is deleted successfully.43. ipaa unblocked DN09203161 Issue: 01E .51.226 223 active idle Verify that the successful deletion information has been sent.226 223 backup deleting service datasync. 6 Delete RNCSRV object in BkRNC.52.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 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. 5 Verify that the BKPRNC object in OMS has been successfully deleted. 4 Delete the BKPRNC object at the PrPRNC object using OMS GUI.43. Step result Verify the deletion of RNCSRV using below command: > show network-resiliency association rnc-service-id 223 CFPU-0@RNC-200 RNC type PRNC ID PRNC IP Loaded RNC service RNC service ID Activity mode Service status Auto trigger operation Data synchronization state 390 [2015-07-24 16:00:01 +0530] : : : : : : : : : BkPRNC 200 10. Delete the RNCSRV in BkPRNC using SCLI command: > delete network-resiliency association rnc-service id 223 CFPU-0@RNC-200 Are you sure you want to proceed? [Y/n]: y CFPU-0@RNC-200 [2015-07-24 15:59:51 +0530] [2015-07-24 15:59:53 +0530] The deletion of RNC service 223 is executed.

226 - Number of RNC service displayed = 0.dmp-INITIAL 8.26.43.dmp LDAP Configuration: config-R_QNCB.26.0_4.mips.15:13 less than 100% disabled Verify that the RNCSRV object has been successfully deleted.3.8 Other instructions 8. 8 Verify that the corresponding backup build presence has been deleted.52.mips.3.WR.0_4.8.15.00:00 09-07-2015. 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.15.1 Issue: 01E Operating instructions DN09203161 391 .WR.    WCDMA 16 Feature Descriptions and Instructions Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state 7 : : : : RNC solution features -. Execute the below command to check if the backup build is deleted:> show sw- manage app-sw-mgmt builds all 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.

1 WCDMA 16 Feature Descriptions and Instructions Testing IP connectivity for mcRNC in resilient network Purpose Procedure 1 Configure IP connectivity test mode 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. 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 I/F Plane Total --.1.3.21 : 2015-01-08 17:27:39.48 Note: Refer to /srv/Log/log/iptest_rncsrv223.log file for the IP connectivity test results. 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.8. DN09203161 Issue: 01E .----.----IUB O&M 00080 IUB CP 00080 IUB UP 00080 IU CP 00064 IU UP 00008 SUM 00312 RNC service ID Test start time Test end time g 392 Unsuccess --------00000 00000 00000 00000 00000 00000 Part Success -----------00000 00000 00000 00000 00000 00000 [2015-01-08 17:22:34 +0800] Success Warning Not Test ------.------.    RNC solution features 8.-------00000 00000 00080 00000 00000 00080 00000 00000 00080 00003 00000 00061 00000 00000 00008 00003 00000 00309 : 223 : 2015-01-08 17:22:16.

Step example show network-resiliency association rnc-service-id 223 Step result After controlled redundancy switch succeed: Issue: 01E DN09203161 393 . make sure the RNC service in peer RNC has been deactivated or isolated. Procedure 1 Activate RNCSRV-223 on BkPRNC. t Tip: Redundancy switch over can be triggered from Backup and Loaded modes in BkPRNC. backup PRNC may not perform the full functionality of protected PRNC. 2 Perform controlled redundancy switch. If the completeness of the RNC service to be activated is less than 100.1.3. ********************************WARNING********************************** Are you sure you want to proceed? [Y/n]: y CFPU-0@RNC-223 [2015-01-08 17:28:59 +0800] RNC service 223 is activated.    WCDMA 16 Feature Descriptions and Instructions 8. otherwise backup PRNC and protected PRNC will be alive at the same time. 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.2 RNC solution features Performing controlled redundancy switch Purpose After the redundancy switch. If forced way is used. the BKPRNC object (under RNC object) will be removed from topology of BkPRNC implicitly.8.

51.43.226 RNC service ID Activity mode Service status : 223 : loaded : idle BkPRNC ID : 200 DN09203161 Issue: 01E .52. Activity mode is changed to Loaded on PrPRNC and the PrPRNC stops serving RNC service.00:00 07-07-2015.    RNC solution features WCDMA 16 Feature Descriptions and Instructions • Activity mode is changed to Active • on BkPRNC and the BkPRNC starts serving RNC service.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 : : : : : : : : : 4 223 active idle datasync. 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. ipaa unblocked -.13:28 100% enabled Interrogate Activity Mode on PrPRNC Step example show network-resiliency association Step result CFPU-0@RNC-223 394 [2015-07-09 10:54:47 +0530] RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10.43.

3 Performing forced redundancy switch (mcRNC) Forced redundancy switch command for and procedure prerequisites. Issue: 01E DN09203161 395 . the BkPRNC starts serving RNC service. Prevent it by isolating manually the PrPRNC.3. Before you start w Redundancy conflict.8. BkPRNC starts serving RNC service.13:28 false enabled Note: If during resiliency switch the system restarts spontaneously or on operator's demand. It means NE file restoration has been interrupted and NE configuration is mismatched with running SW build.1. the alarm 3361 MISMATCH BETWEEN SW BUILD CONFIGURATION AND CONFIGURATION NE may occur. where both PrPRNC and BkPRNC are online at the same time.    WCDMA 16 Feature Descriptions and Instructions 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 : : : : : : : : : RNC solution features RNC-200 10. 8. Procedure 1 Perform forced redundancy switch on BkPRNC: Step example start network-resiliency activate rnc-service-id 223 mode forced Step result • Activity mode changes to Active • on BkPRNC. the Activity mode is changed to Active on BkPRNC. Result After forced redundancy switch succeed.234 active off critical 100% 07-07-2015.43.52. may occur when forced redundancy switchback is executed.

18:14 false enabled Result • The Activity mode is ACTIVE • on PrPRNC and the PrPRNC starts serving RNCSRV.51.52.    RNC solution features 8.8. 396 DN09203161 Issue: 01E . Step example start network-resiliency activate rnc-service-id 223 mode controlled 2 Interrogate the activity mode of the PrPRNC Step example show network-resiliency association Step result CFPU-0@RNC-223 [2015-07-25 10:52:21 +0530] RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10.3.234 loaded off critical less than 100% 24-07-2015. The Activity mode is LOADED on BkPRNC and the BkPRNC stops serving RNCSRV.1.4 WCDMA 16 Feature Descriptions and Instructions Performing controlled redundancy switchback Purpose After the redundancy switchback. Procedure 1 Perform controlled redundancy switchback on PrPRNC.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. the BKPRNC object will be created (under RNC object) into topology of PrPRNC implicitly.43.

 where both PrPRNC and BkPRNC are online at the same time. may occur when forced redundancy switchback is executed.1. Step example start network-resiliency activate rnc-service-id 223 mode forced 2 Interrogate the Activity mode in PrPRNC show network-resiliency association Step result CFPU-0@RNC-223 [2015-07-25 11:08:23 +0530] RNC type PRNC ID PRNC IP : PrPRNC : 223 : 10.234 loaded off critical less than 100% 24-07-2015.    WCDMA 16 Feature Descriptions and Instructions 8.18:14 false enabled Result • Activity mode changes to Active on PrPRNC.43. Before you start w Redundancy conflict. Procedure 1 Perform forced redundancy switchback on PrPRNC.3.5 RNC solution features Performing forced redundancy switchback for mcRNC Forced redundancy switchback command for and procedure prerequisites.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.51.52.8. Prevent it by isolating manually the BkPRNC. Issue: 01E DN09203161 397 .43.

 This object needs to point out to the PRNC object that is already in the topology. BkPRNC object must occur under the following path ROOT ► RNC-<ID> ► BkPRNCs. ensure BkPRNC managed object presence in GUI and proceed with step Create RNCSRV in BkPRNC. 3 Create BkPRNC object for PrPRNC. The operator is able to connect 20 PRNC/RNC pairs to one OMS and additionally 10 PRNCs (without RNC service).6 8.1 PrPRNC starts serving RNC service. Go to the specific BkPRNC ID.3.3. Tip: Commission BkPRNC only if this procedure has not been done yet. Procedure 1 t Commission BkPRNC.6.    RNC solution features WCDMA 16 Feature Descriptions and Instructions • 8.8. Step result BkPRNC is present on OMS as shown in the Figure 65: Example view of BkPRNC managed object visible in OMS GUI Figure 65 2 Example view of BkPRNC managed object visible in OMS GUI Create RNCSRV in BkPRNC.1. Right-click on it and create RNCSRV using Create new object option. If it has been done. Network Resiliency operations in OMS Configuring OMS for network resiliency using Element Manager Purpose This chapter instructs how to configure OMS in order to act in the resilient network. BKPRNC object is on the feature license and there is no restriction for creating it. 398 DN09203161 Issue: 01E .1. Open OMS Element Manager.8.

Type in RNCSRV-221 in the search line under the Topology tab. Perform Search for respective RNCSRVby DN in the Navigation bar.8.    WCDMA 16 Feature Descriptions and Instructions RNC solution features BkPRNC IP address is visible under Backup RNC IPv4 Address used for establishing RNC cluster O&M interface. Procedure 1 Search for respective RNCSRVby DN in the Navigation bar.3. 8.8.1.6.6.. PRNC-301/RNCSRV-221 - directs to BkPRNC which contain RNCSRV representing PrPRNC-221. 2 Activate RNCSRV-221 in BkPRNC In BkPRNC.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. right-click on the RNCSRV-221 and select  Resiliency menu. Procedure 1 Search for respective RNCSRVby DN in the Navigation bar. 8. Step result The list of NEs containing searched content is displayed: • • Issue: 01E PRNC-221/RNCSRV-221 - directs to PrPRNC which contain representing RNCSRV.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. DN09203161 399 . if you want to add another PrPRNC. and Create BkPRNC object for PrPRNC. Repeat steps Create RNCSRV in BkPRNC.3. 4 Add another PrPRNC.1.

8. or by right-click on the RNCSRV-221 and checking which RNC Resiliency menu appears according to RNC Resiliency menu.3. while the Parameter Editor/Viewer applications display data directly from the related NE (in this case PRNC). You can recognize where have you been brought either by checking which PRNC is indicated by respective icon. Performing redundancy switchback using OMS EM Purpose This chapter introduces example procedure of redundancy switchback from BkPRNC301 to PrPRNC-221. right-click on the RNCSRV-221 and select  Resiliency menu. 8.4  from RNC Note: The values of the ActivityMode parameter may differ between the Main Parameters application and the Parameter Viewer/Editor applications.3.. 400 DN09203161 Issue: 01E .1. In PrPRNC.6.    RNC solution features WCDMA 16 Feature Descriptions and Instructions t Tip: Click on either first or second result. g 8. Perform Search for respective RNCSRVby DN in the Navigation bar.7  from RNC Reconfiguring BTS for Network Resiliency Purpose The user reconfigures BTS in order to add a BkPRNC configuration. 2 Activate RNCSRV-221 in BkPRNC In BkPRNC.1. right-click on the RNCSRV-221 and select  Resiliency menu. 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. according to Impact on network and network element management tools. which is an additional RNC configuration. 2 Activate RNCSRV-221 in PrPRNC.8. Procedure 1 Search for respective RNCSRVby DN in the Navigation bar. Before you start Primary BTS configuration has been already done.

8.43. on the Iub interface configuration page within the Backup RNC configuration: Table 171 BTS configuration values Parameter Far end SCTP subnet address Value BkPRNC IP address for example: 10.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Procedure 1 Commission BTS using additional PrPRNC and BkPRNC IP addresses.42 Far end SCTP subnet address mask BkPRNC FAREND SCTP for example: 255.8. Configuring IP addresses in backup build for BkPRNC (mcRNC) Procedure 1 Configure IP address resources Configure: • • • • g 8. IPRO configuration is not needed. Performing IP auto adaptation Purpose Purpose The user can perform the IP auto adaptation • • • Issue: 01E to trigger automatically during scheduled synchronization to trigger automatically during manual synchronization to trigger manually on demand DN09203161 401 .8 Note: Re-homing BTS may require changing of BkPRNC information to values related to the new controller.235 g 8.52.255 (/32) OAM address BkPRNC IP address for example: 10.43.3.255.3.1.9 CBC IP address QNUP and QNIUB IP addresses IPRO BFD Note: If IP Auto-adaptation is set to ON when data synchronization is processing.1.52.255. Provide the following information in BTS SM.

Previous auto trigger operation : datasync Current auto trigger operation : datasync. ipaa – When the schedule synchronization starts.52. the user has to perform manual IP auto adaptation for RNCSRV set to LOADED mode. Change the Current auto trigger operation to datasync. Otherwise. 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. check Service Status to monitor which operation is currently ongoing. Check it with the command:show network-resiliency association – Service status rnc-service-id 223 IP auto adaptation is indicated by : doing IP auto adaptation Service Status changes in the following way CFPU-0@RNC-200 (...226 RNC service ID Activity mode : 223 : backup DN09203161 Issue: 01E .) Service Status (.43.) Service Status (.. • Configure IP auto adaptation to trigger automatically during scheduled synchronization.    RNC solution features WCDMA 16 Feature Descriptions and Instructions g Note: If IP auto adaptation is set to trigger automatically then it begins after data synchronization.) [2015-07-09 15:16:11 +0530 :downloading :doing basic adaptation CFPU-0@RNC-200 402 [2015-07-09 15:16:11 +0530] RNC type PRNC ID PRNC IP : BkPRNC : 200 : 10....

• Configure IP auto adaptation to trigger automatically during manual synchronization. Sub-steps 1 Switch RNCSRV to LOADED mode. Sub-steps 1 Trigger manual synchronization. ipaa unblocked -.11:25 less than 100% enabled Note: Refer to /srv/Log/log/configtest_rncsrv223. 2 Trigger commit with IPAA.log file for the IP auto adaptation results. Step example start network-resiliency synchronize rnc-service-id 223 ipaa on Step result CFPU-0@RNC-223 This command is executed successfully.    WCDMA 16 Feature Descriptions and Instructions Service status Auto trigger operation Data synchronization state Data synchronization schedule Backup update time Backup completeness RNC cluster O&M link state g : : : : : : : RNC solution features doing IP auto adaptation datasync.00:00 08-07-2015. Issue: 01E DN09203161 [2015-07-09 16:21:19 +0530] 403 . • [2015-07-09 15:12:58 +0530] Manual IP auto adaptation on demand. Step example start network-resiliency commit ipaa on Step result CFPU-0@RNC-223 This command is executed successfully.

3. For detailed instructions refer to Release upgrade instructions attached to particular SW build.1.    RNC solution features 8. see Upgrading mcRNC SW builds and BPS on BkPRNC. 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. 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). For the operating instruction. No new BPS is created as part of this upgrade and newly created build is not part of any BPS. see Operating BPS on BkPRNC with the Activity Mode: Loaded or Active.1. 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.10.8. BkPRNC upgrade covers only running backup build. Performs resiliency switch back command to switch back to old base build. 8. 2. The upgrade instructions are the same as a regular SW update/upgrade at normal controller.8. 404 DN09203161 Issue: 01E . In Active/Loaded mode. BkPRNC's SW upgrade Upgrade of BkPRNC is to upgrade an active BPS to a new specified BPS (base build and all backup builds).3. The new SW build does not belong to any BPS. 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.10 WCDMA 16 Feature Descriptions and Instructions mcRNC SW builds upgrade on BkPRNC Recommendations for particular types of SW upgrades on PRNCs in the resilient network.1 Creating BPS fallback Instructions for obtaining BPS fallback. BPS upgrade procedure on BkPRNC (Activity mode : Backup) This procedure contains the following steps: • BPS upgrade – – • Base build upgrade Backup builds upgrade BPS activation For the operating instruction. In this time SW upgrade/update might be necessary for the backup build in Active mode. Full release / Change Delivery (CD) update / OnTop installation on the Activity mode: Active or Loaded.

but the task was completed and executed successfully When BPS fallback creation was aborted while base build was being copied to the BPS.. Copying is successful Backup build for RNC service 00001: Build on copying . please be patient!! Base build: Build on copying . 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 RNC service : 222 Start fallback copying! Each build fallback copying need several minutes. please be patient!! Issue: 01E DN09203161 405 .. When BPS fallback creation was aborted while last build was being copied to the BPS... please be patient!! Base build: Build on copying . the following message occurs: root@CFPU-0 [BCN_211] > save sw-manage bps name BPSFB2 BPS name is already used by other BPS.    WCDMA 16 Feature Descriptions and Instructions RNC solution features Procedure 1 Create BPS fallback. The last build copying is ongoing and cannot be aborted. Copying is successful Backup build for RNC service 222: Build on copying .. 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 wait until it finishes Copying is successful Interruption attempted by user . 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... Copying is successful BPS fallback messages for creation abort..

10.iso Step result BPS installation request is sent successfully.. • Upgrade all builds (base build backup builds) simultaneously.8.0_3..WR.dmp.26.. Sub-steps 1 Upgrade both base build and all backup builds belonging to the current.mips.3. Try to abort build copying . Step example set sw-manage bps install all new-bps-name 152603_bps delivery /mnt/backup/backup/R_QNCB. Please check installation task by SCLI "show sw-manage bps upgrade-task".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.1. Build copying is aborted [warning] The left BPS is incomplete! BPS copying is aborted Related descriptions Configuring GIVAXI/givClient on page 264 Backup Physical RNC System management on page 326 8.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Base build: Build on copying . running BPS.15. 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 RNC service: 223 --> RNC service: 224 --> 406 --> Ongoing Queuing Queuing DN09203161 Issue: 01E . There are several optional ways to perform the upgrade..

iso Step result Result: CFPU-0@RNC-200 [2015-07-03 12:06:08 +0530] BPS installation request is sent successfully.    WCDMA 16 Feature Descriptions and Instructions t RNC solution features Tip: Detailed installation log is placed in srv/Log/log/bps_upgrade.WR.dmp.15.mips.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.26. Issue: 01E DN09203161 407 . Step example set sw-manage bps install base-build new-bps-name 152603_bps delivery /mnt/backup/backup/R_QNCB.0_3. 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 . Please check installation task by SCLI "show sw-manage bps upgrade-task".

Step example set sw-manage bps install backup-build bps-name 152603_bps specified-service-id id 223 id 224 Step result CFPU-0@RNC-200 [2015-07-06 10:29:04 +0530] BPS installation request is sent successfully.3.10.3 Activating new BPS on BkPRNC (mcRNC) Purpose 408 DN09203161 Issue: 01E .8.1. Please check installation task by SCLI "show sw-manage bps upgrade-task".log 5 Check new BPS Step example show sw-manage bps all Related descriptions Configuring GIVAXI/givClient on page 264 Backup Physical RNC System management on page 326 8.    RNC solution features WCDMA 16 Feature Descriptions and Instructions 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. 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 --> RNC service: 224 --> t [2015-07-06 10:29:14 +0530] Ongoing Queuing Tip: Detailed installation log is placed in srv/Log/log/bps_upgrade.

WR.mips.15.15.WR.WR. for example do not press buttons Ctrl and C at the same time.0_3. 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 : SW build status : SW delivery : LDAP configuration: ILMFS files : RNW database : NE files : RNC service ID : 223 SW build name : SW build status : SW delivery : LDAP configuration: ILMFS files : Issue: 01E 152603_bps NW R_QNCB.0_3.WR.dmp-INITIAL SS_ILMFS/R_QNCB.15.dmp-BK20150701155422 DN09203161 409 .mips.dmp-BK20150701155422 SS_ILMFS/R_QNCB.26.26.26.dmp config-R_QNCB.mips.dmp DB/R_QNCB.WR.26.15.0_3.0_3. 2 Check the new BPS information.WR.mips.26.26.15. System restart is triggered by this operation.26. And do not terminate the command execution.mips.0_3.15.0_3.WR.15.0_3.    WCDMA 16 Feature Descriptions and Instructions RNC solution features This procedure contains steps to activate new BPS after update or upgrade of SW builds on BkPRNC Procedure 1 w Activate new BPS. 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.mips.dmp SWBuilds/ID_20150629181954640523_UNDEF/NEFiles BK_223_90 UD R_QNCB. Please be patient.mips.dmp config-R_QNCB.

2_10.2_11.WR.mips.WR.mips.26.26. • Upgrading the BPS on the BkPRNC with the Activity Mode: Loaded or Active.    RNC solution features WCDMA 16 Feature Descriptions and Instructions RNW database NE files : DB/R_QNCB.15. > set sw-manage install delivery /mnt/backup/R_QNCB.26.dmp-BK20150701155422 : SWBuilds/ID_20150701155422762718_BACKUP/NEFiles RNC service ID : 224 SW build name : SW build status : SW delivery : LDAP configuration: ILMFS files : RNW database : NE files : BK_224_72 UD R_QNCB.dmp-BK20150701152306 SWBuilds/ID_20150701152306517419_BACKUP/NEFiles Related descriptions Configuring GIVAXI/givClient on page 264 Backup Physical RNC System management on page 326 8.dmp-BK20150701152306 SS_ILMFS/R_QNCB.26.15.dmp-BK20150701152306 DB/R_QNCB.26.0_3.15.0_3.26..26. Sub-steps 1 Install the new delivery.rmp to R_QNCB.mips.15.3.0_3.10.2_11. 2 Check if the new build is created.1.WR.26.WR.2_11.4 Operating BPS on BkPRNC with the Activity Mode: Loaded or Active Procedure for the BPS upgrade on the BkPRNC with the Activity Mode: Loaded or Active..mips.iso Step result CFPU-0@RNC-223 [2016-02-05 12:26:01 +0530] WARNING: Forcing upgrade path from R_QNCB.mips.26.mips.WR. > show sw-manage app-sw-mgmt builds all 410 DN09203161 Issue: 01E .0_3.rmp INFO: installing /mnt/backup/R_QNCB.15.WR.15.iso INFO: This might take several minutes.15.dmp config-R_QNCB.mips.rmp.mips.8.mips.15.WR.15.WR.rmp.WR.0_3.

26.WR.15.rmp-Rakesh Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.15.rmp LDAP Configuration: config-R_QNCB.15.mips.26.WR.15.2_10. Step example > set sw-manage activate delivery-label R_QNCB.2_11.mips.26.mips.26.mips.15.15.mips.2_10.rmpBK20160205092927/ SW Build name: 20160205_A SW Build status: NW SW Delivery: R_QNCB.26.2_10.mips.rmp/ SW Build name: BK_223_15 SW Build status: BU (Active) SW Delivery: R_QNCB.WR.rmp LDAP Configuration: config-R_QNCB. CFPU-0@RNC-223 13:38:09 +0530] Are you sure you want to proceed? [y/N]: y CFPU-0@RNC-223 Issue: 01E DN09203161 [2016-02-05 411 .15.26.rmpBK20160205092927/ Path to RNW database dump: /var/opt/nsn/SS_ILOMU/DB/R_QNCB.WR. Activate the upgraded build with status SW Build status: NW.mips.mips.2_11.WR.WR.26.WR.2_10.26.mips.2_11.15.WR.26.mips.15.15.15.26.mips.2_10.26.2_10.WR.26.rmp/ Path to RNW database dump: N/A (No dump created for this build) 3 Activate the upgraded build.rmpBK20160205092927 Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.rmp-INITIAL Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.mips.2_10.WR.15.WR.rmp Confirm to proceed.rmp/ Path to RNW database dump: /var/opt/nsn/SS_ILOMU/DB/R_QNCB.2_11.WR.2_10.rmp LDAP Configuration: config-R_QNCB.    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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.

26.26.rmp/ Path to RNW database dump: N/A (No dump created for this build) The upgraded build is not a part of the BPS.rmp RNW database : DB/R_QNCB.rmp-Rakesh ILMFS files : SS_ILMFS/R_QNCB.rmp-INITIAL Path to ILMFS files: /var/opt/nsn/SS_ILOMU/SS_ILMFS/R_QNCB.2_10. SW Delivery: R_QNCB.WR.WR.26.rmp LDAP Configuration: config-R_QNCB.To check the result enter:> show swmanage bps all.15.15.15.2_10.15.rmp LDAP configuration: config-R_QNCB.WR.2_11.15.2_10.15.mips.15.26.mips.mips.26.    RNC solution features WCDMA 16 Feature Descriptions and Instructions Step result The upgraded build is activated.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.mips.WR.15.2_10.26.2_11.WR.15.rmpBK20160205092927 RNW database : DB/R_QNCB.26.WR.26.26. SW Delivery: R_QNCB.WR.mips.mips.26.2_11.mips.26.rmp is in SW Build status: NW (Active).15.mips.mips.15.WR.mips.26.mips.2_10.WR.rmp LDAP configuration: config-R_QNCB.2_10.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.2_10. To check the result enter: > show sw-manage app-sw-mgmt builds active.rmpBK20160205092927 NE files : SWBuilds/ID_20160205092927985228_BACKUP/NEFiles 412 DN09203161 Issue: 01E .15.mips.WR.26.WR.2_11.WR.2_10.WR.2_11.mips.15.rmpBK20160205092927 ILMFS files : SS_ILMFS/R_QNCB. 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.

> 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. 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.    WCDMA 16 Feature Descriptions and Instructions • RNC solution features Returning to the base build of an old BPS after a new SW build has been activated. Issue: 01E DN09203161 413 . 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 ****************** 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. The unloading of RNC service 223 is executed. > 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. Post requisites Deactivation and activation of RNCSRV can be done with the resiliency commands when the upgraded build is active. Do you want to continue? [y/n]:y 2 Perform resiliency switch back and unload RNCSRV. Please be patient. The target build is the backup build belongs to BPS 20160204_A. The unload is not possible as the upgraded build is not a part of the BPS.

Procedure 1 Delete BPS fallback.3. Deletion is successful Base build: Build on deleting ..10.1.8. Before you start The user cannot delete BPS which is currently operating. please be patient!! Backup build for RNC service 00001: Build on deleting . Step example > 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.. When BPS fallback deletion was aborted while backup build was deleted.5 WCDMA 16 Feature Descriptions and Instructions Deleting BPS fallback Instructions for deleting BPS fallback. Deletion is successful BPS fallback messages for deletion abort.    RNC solution features 8.. the following message occurs: root@CFPU-0 [BCN_211] > delete sw-manage bps name BPSFB1 ************** WARNING *************** The BPS deletion is requested! ************** WARNING *************** 414 DN09203161 Issue: 01E ..

please be patient!! Backup build for RNC service 222: Build on deleting ...but the task was completed and executed successfully Related descriptions Configuring GIVAXI/givClient on page 264 Backup Physical RNC System management on page 326 Issue: 01E DN09203161 415 . Build deleting is aborted [warning] The left BPS is incomplete! When BPS fallback deletion was aborted while the base build deletion is ongoing. Deletion is successful Base build: Build on deleting .. Try to abort build deleting .. Please wait until it finishes Deletion is successful Interruption attempted by user . The last build deletion is ongoing and cannot be aborted...    WCDMA 16 Feature Descriptions and Instructions RNC solution features 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... 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 00001: Build on deleting .

Optical chaining supported by HW (three optical connectors with 6 Gbit/s interfaces). 9. The feature provides the operator with the following benefits: • • • • • • Full 80 W power over full 60 MHz bandwidth The most cost-efficient and compact 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 9.1. -35°C - +55°C (3GPP ≤ +-2.5dB). +15°C - +30°C (3GPP ≤ +-2.3 RAN3308 System impact Interdependencies between features 416 DN09203161 Issue: 01E .0dB in extreme conditions. It provides an output of 3x80 W at the antenna connector. TX output power tolerance: – – ≤ +-0. ≤ +-2. 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.1. TX/RX bandwidth is 60 MHz. downlink: 21102170 MHz).2 RAN3308 Functional description The FRGX module supports WCDMA and LTE in dedicated or concurrent mode. AISG2. 9. Volume: 25 l. The main features of the FRGX are as follows: • • • • • • • • • 3GPP 2100 MHz band supported.0 antenna tilt support with external connector (RS485).0dB). Weight: 25 kg.1 RAN3308 Benefits Operator benefits The Flexi 3-sector RF Module 2100 (FRGX) can be used as a WCDMA and LTE RF Module.1 RAN3308: Flexi RFM 3T6R 2100 (FRGX) g Note: Feature availability with Maintenance Package. EAC port.8dB in normal conditions. Can be used in feederless BTS sites (optical and DC cable up to 200 m).    BTS solution features WCDMA 16 Feature Descriptions and Instructions 9 BTS solution features 9. 3 U high with Flexi platform mechanics.1.

3 System Module.    WCDMA 16 Feature Descriptions and Instructions BTS solution features There are no interdependencies between features. Impact on interfaces There is no impact on interfaces. Key performance indicators There are no key performance indicators related to this feature. 9.4 RAN3308 Reference data Requirements g Note: Feature availability with Maintenance Package. Impact on network and network element management tools There is no impact on network and network element management tools.2 RAN3158: Flexi RFM 6T6R 2100 (FRGU) Introduction to the feature Issue: 01E DN09203161 417 . Alarms There are no alarms related to this feature. Parameters There are no new or modified parameters related to this feature.2 or Rel. Table 172 RAN3308 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 WBTS16 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 a Rel. Impact on system performance and capacity There is no impact on system performance and capacity. Measurements and counters There are no measurements or counters related to this feature.1. Sales information Table 173 RAN3308 Sales information BSW/ASW SW component License control in network element BSW RAN - 9.

 

 

BTS solution features

WCDMA 16 Feature Descriptions and Instructions

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:










the most cost-efficient and compact 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 with one DC and 1...2 optical cables
ability to build a TX div or 2TX/2RX MIMO for three sectors with only one RF Module
one 3-sector module providing a more cost effective solution than two RF 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 the site with an RRH

9.2.2 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 by HW, three optical connectors with 6 Gbit/s interfaces
AISG2.0 antenna tilt support with external connector (RS485)
ability to be used in feederless BTS sites (optical and DC cable up to 200 m)
weight: 25 kg
volume: 25 l
TX output power tolerance:

≤ +-0.8dB in normal conditions, +15°C - +30°C (3GPP ≤ +-2.0dB)
≤ +-2.0dB in extreme conditions, -35°C - +55°C (3GPP ≤ +-2.5dB)

9.2.3 RAN3158 System impact
Interdependencies between features
There are no interdependencies between features.
Impact on interfaces

418

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

BTS solution features

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 174

RAN3158 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

WBTS16

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

RAN3158 Sales information

BSW/ASW

SW component

License control in network element

BSW

RAN

-

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

Issue: 01E

DN09203161

419

 

 

BTS solution features

WCDMA 16 Feature Descriptions and Instructions

9.3.1 RAN3246 Benefits
Operator benefits
The RAN3246: Flexi RRH 2T2R 850 120W (FRCG) feature provides the following
benefits:







Full 3GPP band 5 (850 MHz) supported
Up to 2x60 W output power at the antenna connector
Optical chaining supported by HW, two optical connectors with 6 Gbit/s interfaces
200 000 hours MTBF
The most cost-efficient and compact 2TX/2RX BTS Site
Industry leading RF integration level
Low power consumption and OPEX
Can be used as a WCDMA and LTE module

9.3.2 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, see Flexi Multiradio BTS WCDMA Supported Configurations and
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

420

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Table 176

BTS solution features

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 177

RAN3246 Sales information

BSW/ASW

SW component

License control in network element

BSW

RAN

-

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.

Issue: 01E

DN09203161

421

 

 

BTS solution features

WCDMA 16 Feature Descriptions and Instructions

This feature benefits the operator as follows:








the most cost-efficient and compact 4TX/4RX BTS Site
industry leading RF integration level
SW configurable radio: the same 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 one DC and 1...2 optical cables
30 l volume (without solar shield)
23 kg (50.6 lbs) weight

9.4.2 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 by HW, two optical connectors with 6 Gbit/s interfaces
EAC port
AISG2.0 antenna tilt support with external connector (RS485)
ability to be used in feederless BTS sites (optical and DC cable up to 200 m)

The following are some basic WCDMA configurations:

up to 4+4+4+4 cells
8, 10, 20, 30 or 40 W mode per sector (by SW licenses)

9.4.3 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

422

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

Table 178

BTS solution features

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 179

RAN3103 Sales information

BSW/ASW

SW component

License control in network element

BSW

RAN

-

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

g

Note: Feature availability with Maintenance Package.
Introduction to the feature
The RAN3324: Flexi RRH 4-pipe 1700/2100 160W  feature introduces Flexi Multiradio
Remote Radio Head 4TX/4RX (FRIJ) for 3GPP band 66 (uplink: 1710 - 1780 MHz,
downlink: 2110 - 2200 MHz). The FRIJ module can also support 3GPP band 4 and band
10.

Issue: 01E

DN09203161

423

 

 

BTS solution features

WCDMA 16 Feature Descriptions and Instructions

9.5.1 RAN3324 Benefits
Operator benefits
The Flexi 4TX/4RX RRH (FRIJ) can be used as a WCDMA and LTE module.
The feature provides the operator with the following benefits:




Compact and energy efficient RRH lowering total cost of ownership.
Network performance improvement with 4RX diversity schemes.
Multi-standard software-configurable RRH supporting HSPA+, LTE and LTE-A air
interfaces.
Full band (70 UL/90 DL) instantaneous bandwidth enables carriers to be placed
anywhere in the band from a single RRH.
Flexible installation options. FRIJ is designed to be mounted on a wall, pole, stacked
vertically or horizontally (with additional fan kit) and can be integrated into the Radio
Antenna System.

9.5.2 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:









3GPP FDD bands 4, 10 and 66
Up to 4 carriers per antenna connector with a maximum occupied bandwidth of 40
MHz
multiple carriers with maximum instantaneous bandwidth of 70MHz in uplink and
90MHz in downlink
optical chaining supported by HW; three 6 Gbit/s optical interfaces
up to four external alarms
AISG2.0 antenna tilt support with external connector (RS485)
MHA, DC and AISG over RF connection supported
256 QAM LTE supported
19.4 l volume
21 kg (46.3 lbs) weight

The FRIJ module can be installed:




on a pole
on a wall
stacked vertically (book mounting)
horizontally with optional fan module
inside the Radio Antenna System (RAS)

9.5.3 RAN3324 System impact
Interdependencies between features
There are no interdependencies between features.
Impact on interfaces
There is no impact on interfaces.

424

DN09203161

Issue: 01E

 

 

WCDMA 16 Feature Descriptions and Instructions

BTS solution features

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

g

Note: Feature availability with Maintenance Package.
Table 180

RAN3324 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

Support not
required

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 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 181

RAN3324 Sales information

BSW/ASW

SW component

License control in network element

BSW

RAN

-

9.6 RAN3237: HSUPA Scheduler Capacity Increase for
FSMF
Introduction to the feature
HSUPA scheduler capacity increase up to 320 HSUPA users.

Issue: 01E

DN09203161

425

6. Impact on system performance and capacity HSUPA scheduler capacity increase: • • from 240 to 320 HSUPA users in case of Normal HSPA configuration from 160 to 240 HSUPA users in case of Small HSPA configuration 9. Operator benefits This feature benefits the operator as follows: • • Support for more HSUPA users per Local Cell Group.6. Impact on network and network element management tools This feature has no impact on network management or network element management tools.4 RAN3237 Reference data Requirements Table 182 426 RAN3237 hardware and software requirements RAS IPA-RNC mcRNC WCDMA 16 Support not required Support not required DN09203161 Flexi Multiradio BTS Not planned Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16 Not planned Issue: 01E . Impact on interfaces This feature has no impact on interfaces. 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.6. 9.3 RAN3237 System impact Interdependencies between features There are no interdependencies between this and any other feature.6. Only SW upgrade to WBTS16 is needed to obtain the benefits. If Local Cell Group is configured into Small HSPA mode then HSUPA scheduler capacity is increased from 160 to 240 HSUPA users. 9.    BTS solution features WCDMA 16 Feature Descriptions and Instructions 9. no need for recommissioning.1 RAN3237 Benefits End-user benefits This feature does not affect end user experience.2 RAN3237 Functional description HSUPA scheduler capacity is increased from 240 to 320 HSUPA users when Local Cell Group is configured into Normal HSPA mode.

RAN1686: HSPA 72 Users Per Cell or RAN2124: HSPA 128 Users per Cell is enabled. RAN1201: Fractional DPCH is enabled. Alarms There are no alarms related to this feature. Sales information Table 183 RAN3237 Sales information BSW/ASW BSW SW component RAN License control in network element BTS LK 9. Hardware requirement: WCDMA16.6.5 Testing RAN3237: HSUPA Scheduler capacity increase for FSMF Before you start Test environment: • • Hardware requirement: FSMF.    WCDMA 16 Feature Descriptions and Instructions Table 182 BTS solution features RAN3237 hardware and software requirements (Cont. DN09203161 427 .) OMS NetAct MSC SGSN MGW UE Support not required NetAct 16. Measurements and counters There are no measurements and counters related to this feature. and a sufficient amount of processing set licenses are used. 320 WCDMA terminals supporting 3GPP Rel7 or onward. Parameters There are no parameters related to this feature. F222 with 1 Local Cell Group.2 Support not required Support not required Support not required Support not required Flexi Multiradio System Module FSMF or newer is required. Preconditions: • • • • • • Issue: 01E HSPA is enabled for all cells. PIC and FDE are disabled unless otherwise mentioned. Key performance indicators There are no key performance indicators related to this feature.

1 RAN2249 Benefits End-user benefits This feature does not affect end user experience. Tilting for each band is controlled separately. b) Open ping session in every terminal. 2 240 HSUPA users Small HSPA is configured Required actions: a) Add 240 terminals evenly to six cells. Expected Results: 240 Ping sessions can archive. b) Open ping session in every terminal.0 compliant remote electrical tilt (RET) devices to Flexi Multiradio BTS.0 compliant RET devices by Flexi Multiradio BTS. 428 DN09203161 Issue: 01E .7. Multi-antenna RETs are typically installed with multiband antennas.7.7 RAN2249: Support for Multi-Antenna RET Device Introduction to the feature RAN2249: Support for Multi-Antenna RET Device introduces support for multi-antenna and AISG2. Operator benefits Multiband antennas with Multi-RET bring the following benefits: • • • Installation is easier and takes less time. which enables the tilting of each band to be controlled separately. Required actions: a) Add 320 terminals evenly to six cells.2 RAN2249 Functional description RAN2249: Support for Multi-Antenna RET Device introduces support for multi-antenna and AISG2. 9. The amount of antennas and cables on the mast is reduced. Expected Results: 320 Ping sessions can archive. 9. 9.    BTS solution features WCDMA 16 Feature Descriptions and Instructions Procedure 1 320 HSUPA users Normal HSUPA is configured.

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. An antenna can support transmission/reception on different frequency bands. With a built-in multi-antenna RET device. The tilt configuration can be controlled and independently configured with  network management system (NetAct or 3rd party NMS) or the BTS Site Manager. 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.7.    WCDMA 16 Feature Descriptions and Instructions BTS solution features All Antenna Line Device (ALD) suppliers have available equipment compatible with 3GPP/AISG2.1 or higher and System Modules of Rel.2 or Rel. the physical downtilt of each antenna beam can be separately configured for each supported frequency band. This feature is licensed with SW license for RAN906: Flexi WCDMA BTS 3GPP Antenna tilt support. for example. dual band antenna. Impact on network and network element management tools NetAct 16. Impact on system performance and capacity This feature has no impact on system performance and capacity.7.3.2 is required.4 RAN2249 Reference data Requirements Table 184 RAN2249 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 WBTS16 WBTS16 Not relevant OMS NetAct MSC SGSN MGW UE Support not required NetAct 16.0 standards. 9.2 Support not required Support not required Support not required Support not required This feature requires RF Modules of Rel. Issue: 01E DN09203161 429 . 9. Activating the antenna tilt license also activates support for multi-antenna RET devices. Alarms There are no alarms related to this feature.

 which streamlines the MHA family.1 RAN3238 Benefits End-user benefits This feature does not affect end user experience.    BTS solution features WCDMA 16 Feature Descriptions and Instructions Measurements and counters There are no measurements and counters related to this feature.8. There is no need for high gain MHAs anymore. Parameters Table 185 New parameters introduced by RAN2249 Full name Abbreviated name Managed object Parent structure RET antenna unit number retAntUnitNumber RET - RET device type retDeviceType RET - Sales information Table 186 RAN2249 Sales information BSW/ASW ASW g SW component RAN License control in network element BTS LK Note: This feature has a common license with the RAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Support feature. Operator benefits This feature benefits the operator as follows: • • • • 430 Provides comprehensive MHA portfolio supporting new MHA requirements from the operators. Full visibility/recovery of fault situation in both bands is enabled. Dual band MHAs based on dual AISG mode provide full MHA visibility for both bands. 9. New MHAs have a gain of 12 dB.8 RAN3238: WCDMA BTS Support for Harmonized MHA Family Introduction to the feature RAN3238: WCDMA BTS Support for Harmonized MHA Family introduces support for new Masthead Amplifiers (MHAs). Key performance indicators There are no key performance indicators related to this feature. DN09203161 Issue: 01E . 9.

 MDGB and MDPB) can support CWA mode. From the harmonized MHA family.8.    WCDMA 16 Feature Descriptions and Instructions BTS solution features 9. Table 187: MHAs in harmonized MHA family lists new MHAs supported by WCDMA software that can be commissioned as official Nokia MHAs. However.0 support 12 dB gain excellent Passive Inter Modulation specification (-116 dBm) dual AISG/RET enabling flexible control for 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.3 RAN3238 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on network and network element management tools A new MHA type. that have the following functionalities: • • • • • • • • AISG 2. is introduced into NetAct and BTS Site Manager.8. g Note: Nokia MHAs are active (AISG2. Impact on system performance and capacity Issue: 01E DN09203161 431 . it is possible for the operator to select passive (CWA) mode. Table 187 MHAs in harmonized MHA family MHA name Band Product code Additional information MDTB 850 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 9. only single band MHAs (MDTB.0) MHAs. Impact on interfaces This feature has no impact on interfaces.2 RAN3238 Functional description Harmonized Nokia MHA family consist of a wide range MHAs for single and dual band use. "Nokia" MHA.

    BTS solution features WCDMA 16 Feature Descriptions and Instructions This feature has no impact on system performance or capacity.2 or higher. see Flexi Multiradio BTS WCDMA Parameters. BTS faults and reported alarms Table 189 New BTS faults introduced by RAN3238: WCDMA BTS Support for Harmonized MHA Family Fault ID Fault name Reported alarms Alarm ID 4270 MHA in bypass mode Alarm name 7652 BASE STATION NOTIFICATION 7654 CELL OPERATION DEGRADED For fault descriptions. Parameters Table 190 Modified parameters Full name MHA type Abbreviated name mhaType Managed object MHA Parent structure - For parameter descriptions.8. Measurements and counters There are no measurements and counters related to the RAN3238: WCDMA BTS Support for Harmonized MHA Family feature. see Flexi Multiradio BTS WCDMA Faults. 9. Key performance indicators There are no key performance indicators related to the RAN3238: WCDMA BTS Support for Harmonized MHA Family feature. Sales information 432 DN09203161 Issue: 01E .4 RAN3238 Reference data Requirements Table 188 RAN3238 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 WBTS16 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 Modules of Rel.

    WCDMA 16 Feature Descriptions and Instructions Table 191 RAN3238 Sales information BSW/ASW BSW Issue: 01E BTS solution features SW component RAN DN09203161 License control in network element - 433 .