Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.
Table of Contents This document has 546 pages Summary of changes................................................................... 25 1
Introduction to WCDMA 16 features............................................ 27
2
WCDMA 16 Basic Support with NetAct 15.5 + INES PP337....... 28
3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5
RAN3045 Benefits........................................................................ 31 RAN3045 Functional description..................................................31 RAN3045 System impact............................................................. 31 RAN3045 Reference data............................................................ 32 Activating RAN3045: Activity Based UL Power Control for Rel99 DCH............................................................................................. 33
3.1.6
Verifying RAN3045: Activity Bas ed UL Power Control for Rel99 DCH............................................................................................. 34
3.1.7
Deactivating RAN3045: Activity Based UL Power Control for Rel99 DCH................................................................................... 35 Testing RAN3045: Activity Based UL Power Control for Rel99 DCH............................................................................................. 36 Phase 1: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature deactivated..................................37 Phase 2: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature activated......................................38 RAN3043: Advanced HSUPA Time Division Scheduling............. 39
Activating RAN3043: Advanced HSUPA Time Division Scheduling. 42 Verifying RAN3043: Advanced HSUPA Time Division Scheduling.. 43 Deactivating RAN3043: Advanced HSUPA Time Division Scheduling................................................................................... 44
3.2.6 3.2.7
DN09203161Issue:02
Radio resource management features.........................................31 RAN3045: Activity Based UL Power Control for Rel99 DCH....... 31
3.3 3.3.1
RAN3218: Enhanced Cell Change from HSPA to 2G..................45 RAN3218 Benefits........................................................................45
3.3.2 3.3.3
RAN3218 Functional description..................................................46 RAN3218 System impact............................................................. 46
3.3.4 3.3.5
RAN3218 Reference data............................................................ 47 Activating RAN3218: Enhanced Cell Change from HSPA to 2G..... 48
3.3.6 3.3.7
Verifying RAN3218: Enhanced Cell Change from HSPA to 2G... 50 Deactivating RAN3218: Enhanced Cell Change from HSPA to 2G. 51
Telecom features........................................................................ RAN3086: CSFB with RIM......................................................... RAN3086 Benefits...................................................................... RAN3086 Functional description................................................ RAN3086 System impact........................................................... RAN3086 Reference data..........................................................
151 151 151 151 154 154
Activating RAN3086: CSFB with RIM ........................................ 156 Verifying RAN3086: CSFB with RIM.......................................... 157 Deactivating RAN3086: CSFB with R IM.................................... 158 RAN3082: Device Detection...................................................... 159 RAN3082 Benefits...................................................................... RAN3082 Functional Description...............................................
160 160
4.2.3 4.2.4
RAN3082 System impact........................................................... 162 RAN3082 Reference data.......................................................... 162
4.2.5 4.2.5.1 4.2.6
Activating RAN3082: Device Detectio n......................................164 Activating generic IMEI query in the R NC..................................166 Verifying RAN3082: Device Detection ........................................167
4.2.6.1 4.2.7 4.2.7.1
Verifying generic IMEI query in the R NC....................................169 Deactivating RAN3082: Device Detec tion..................................170 Deactivating a Whitelist or Blacklist fu nctionality....................... 170
4.2.7.2
Deactivating generic IMEI query in th e RNC..............................171
5
Transmission and transport features..........................................173
RAN3247/LTE2507/RG602496Refe rence data........................ 194 Activating RAN3247: Energy Efficien cy Shut Down Mode with RF Sharing.......................................................................................194
6.4.5.1.1 6.4.5.1.2
Activating RG301936: Intelligent MC PA TRX shutdown in GSM..... 195 Activating RG301936: Intelligent MCPA TRX shutdown............ 195 Verifying RG301936: Intelligent MCP A TRX shutdown.............. 195
6.4.5.1.3 6.4.5.2 6.4.5.2.1 6.4.5.2.2
Deactivating RG301936: Intelligent MCPA TRX shutdown........197 Activating RAN955: Power Saving Mode for BTS in WCDMA...197 Activating RAN955: Power Saving Mode for BTS......................197 Verifying RAN955: Power Saving Mo de for BTS....................... 200
6.4.5.2.3 6.4.5.3
6.5 6.5.1
Deactivating RAN955: Power Saving Mode for BTS................. 201 Activating LTE1103: Load Based Po wer Saving for Multi-layer Networks in LTE......................................................................... 202 Activating LTE1103: Load Based Power Saving for Multi-layer Networks.................................................................................... 202 Deactivating LTE1103: Load Based Power Saving for Multi-layer Networks.................................................................................... 204 RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing........... 205 RAN3060 Benefits......................................................................205
6.5.2 6.5.3
RAN3060 Functional description................................................205 RAN3060 System impact........................................................... 207
RAN2706 System impact........................................................... 188 RAN2706 Reference data.......................................................... 189 RAN2367: DNS Support for Certifica te Examination................. 190 RAN2367 Benefits...................................................................... 190 RAN2367 Functional description................................................190 RAN2367 System impact........................................................... 191 RAN2367 Reference data.......................................................... 192 RAN3247/LTE2507/RG602496: Energy Efficiency Shut Down Mode with RF Sharing................................................................193 RAN3247/LTE2507/RG602496Bene fits....................................193 RAN3247/LTE2507/RG602496 Functional description..............193 RAN3247/LTE2507/RG602496Syst em impact......................... 193
RAN3063 Benefits...................................................................... 238 RAN3063 Functional description................................................238 RAN3063 System impact........................................................... 238
6.7.4 6.7.5 6.7.6
RAN3063 Reference data.......................................................... 238 Activating RAN3063: KPI Reporting Based on Cell Type .......... 239 Verifying RAN3063: KPI Reporting Based on Cell Type............ 240
6.7.7 6.8 6.8.1 6.8.2
Deactivating RAN3063: KPI Reporting Based on Cell Type...... 242 RAN3150: mcRNC Event Based Symptom Data Collection......24 2 RAN3150 Benefits...................................................................... 243 RAN3150 Functional description................................................ 243
6.8.3 6.8.4 6.9 6.9.1
RAN3150 System impact........................................................... 244 RAN3150 Reference data.......................................................... 244 RAN2991: Modification of WCDMA F requency......................... 245 RAN2991 Benefits...................................................................... 245
6.9.2 6.9.3 6.9.4 6.9.5
RAN2991 Functional description................................................ 246 RAN2991 System impact........................................................... 248 RAN2991 Reference data.......................................................... 249 Testing RAN2991: Modification of WCDMA Frequency............. 250
6.5.8
8
RAN3063: KPI Reporting Based on C ell Type........................... 238
Testing RAN2702: Parameter level lo gging of BTS user events...... 259 RAN2571: Support of TLS 1.2................................................... 260 RAN2571 Benefits......................................................................260
Authorizing Pre-Shared Key (PSK)............................................ 276 Configuring MSGMONPSK for data encryption......................... 276 Configuring and verifying additional steps for IPA-RNC.............277 Configuring NPEG(P) towards OMU..........................................277
7.2.5.1.6.2 7.2.5.1.6.3 7.2.5.1.6.4 7.2.5.1.6.5
Configuring static IP route to external monitoring tool............... 279 Configuring site routers.............................................................. 279 Configuring external monitoring tool (alternative to DHCP)....... 280 Verifying IP configuration........................................................... 280
7.2.5.2
Activating RAN2973: Enhanced IMSI-based Monitoring on
7.2.5.2.1 7.2.5.2.2 7.2.5.2.3 7.2.5.2.4 7.2.6
mcRNC.......................................................................................281 Configuring IP connection at mcRNC........................................ 281 Configuring Givaxi/givClient....................................................... 283 Installing licenses for mcRNC.................................................... 283 Installing L3 Data Collector........................................................ 284 Verifying RAN2973: Enhanced IMSI-based Monitoring............. 284
7.2.6.1
DN09203161Issue:02
Verifying RAN2973: Enhanced IMSI-based Monitoring from L3 Data Collector on IPA-RNC........................................................284
Installing L3 Data Collector........................................................ 301 Authorizing Pre-Shared Key (PSK)............................................ 301 Configuring MSGMONPSK for data encryption......................... 302 Configuring and verifying additional s teps for IPA-RNC.............302 Activating RAN2930: IMSI-based Monitoring on mcRNC.......... 306
Configuring IP connection at mcRN C........................................ 306 Configuring Givaxi/givClient....................................................... 308 Installing licenses for mcRNC.................................................... 309 Installing L3 Data Collector........................................................ 309
7.2.10.6 7.2.10.6.1
Verifying RAN2930: IMSI-based Monitoring...............................309 Verifying RAN2930: IMSI-based Monitoring from L3 Data Collector on IPA-RNC................................................................................309
7.2.10.6.2 7.2.10.6.3
Verifying RAN2930: IMSI-based call monitoring on mcRNC......311 Verifying RAN2930: IMSI-based Monitoring from L3 Data Collector on mcRNC..................................................................................313
Deactivating RAN2930: IMSI-based call monitoring in mcRNC.315 Analyzing monitored data and troubleshooting..........................316
7.2.10.8.1 7.2.10.8.1.1 7.2.10.8.1.2
Analyzing monitored data...........................................................316 Analyzing monitored data from IPA-RNC...................................316 Analyzing monitored data from mcRNC.....................................317
RAN2646: External Alarm Input Sup port of mcRNC..................333 RAN2646 Benefits...................................................................... 333
8.1.2 8.1.3 8.1.4 8.1.5 8.1.6 8.1.7
RAN2646 Functional description................................................ RAN2646 System impact........................................................... RAN2646 Reference data..........................................................
333
333 334 334
8.2 8.2.1 8.2.2
Activating RAN2646: External Alarm Input Support of mcRNC. 335 Verifying RAN2646: External Alarm I nput Support of mcRNC... 340 Deactivating RAN2646: External Ala rm Input Support of mcRNC... 341 RAN3057: mcRNC Signaling Capacity License.........................342 RAN3057 Benefits......................................................................342 RAN3057 Functional description................................................342
Planning Iu-BC interface configu ration for mcRNC BkPRNC.... 354 Planning Iub interface configuration ..........................................355 Planning Iu and Iur interfaces.................................................... 355 Planning management plane configur ation................................357
8.3.2.2.7 8.3.2.2.8 8.3.2.3 8.3.2.3.1
Planning transport network configuration ..................................357 Principles for NW operations with net work resiliency.................357 Operating principles................................................................... 358 Auto-adaptation in mcRNC........................................................ 358
Operating and Maintaining overview.......................................... 358 NetAct topology view.................................................................. 359 Backup Physical RNC System management............................. 360 Interpreting of the system logs................................................... 364 Redundancy switch.................................................................... 366 Activity model............................................................................. 366 Use cases.................................................................................. 367 Detecting redundancy switch necessi ty..................................... 372 Comparison of prepared and unprepared redundancy switch... 372 Redundancy conflict................................................................... 373
8.3.2.3.7 8.3.2.4
Network Resiliency operations in OMS Element Manager (OMS EM).............................................................................................374 Network Resiliency related terms............................................... 377
8.3.2.5 8.3.3
Miscellaneous notes...................................................................380 RAN3005 System impact........................................................... 381
Enlarging QNDRBD................................................................... 386 Modifying the VG_System LDAP con figuration..........................386 Re-initialize hard disk to enlarge VG_ System manually............ 387
8.3.5.1.3 8.3.5.1.4
Enlarging QNDRBD logical volume and corresponding DRBD file system........................................................................................393 Troubleshooting..........................................................................395
8.3.5.2 8.3.5.3 8.3.5.4 8.3.5.5
Commission PrPRNC.................................................................398 Commission PRNC to StPRNC (mcRNC)..................................399 Commission PRNC to BkPRNC (mcRNC).................................401 Create BkPRNC object at PrPRNC (mcRNC)............................402
Configuring RNCSRV at BkPRNC (mcRNC)............................. 410 Configure network interfaces......................................................411
8.3.5.12 8.3.5.13
MSC configuration for Core Network (mcRNC)..........................411 Configuring SGSN for Core Network in resilient network with mcRNC.......................................................................................414
8.3.5.14 8.3.5.15
Configuring Iur interface for mcRNC network resiliency............ 416 Committing the IP address pre-configuration.............................419
Mapping IP address................................................................... 420 Verifying RAN3005: Network Resilie ncy for mcRNC................. 422 Deactivating RAN3005: Network Re siliency for mcRNC........... 423 Other instructions....................................................................... 425
8.3.8.1 8.3.8.1.1 8.3.8.1.2 8.3.8.1.3
Operating instructions................................................................ 425 Testing IP connectivity for mcRNC in resilient network.............. 425 Performing controlled redundancy s witch.................................. 426 Performing forced redundancy swit ch (mcRNC)........................428
Performing controlled redunda ncy switchback...........................429 Performing forced redundancy switc hback for mcRNC............. 430 Network Resiliency operations in OMS......................................431 Configuring network resiliency using OMS Element Manager... 431 Performing forced redundancy switc h using OMS EM...............432 Performing redundancy switch using OMS EM..........................433 Performing redundancy switchback using OMS EM.................. 433 Reconfiguring BTS for Network Resi liency................................ 434 Configuring IP addresses in backup build for BkPRNC (mcRNC)... 435
8.3.8.1.9 8.3.8.1.10 8.3.8.1.10.1
Performing IP auto adaptation................................................... 435 mcRNC SW builds upgrade on BkPRNC...................................437 Creating BPS fallback................................................................ 438
8.3.8.1.10.2 8.3.8.1.10.3
Upgrading mcRNC SW builds and B PS on BkPRNC................ 439 Activating new BPS on BkPRNC (mcRNC)............................... 442
8.3.8.1.10.4 8.3.8.1.10.5 8.3.9
Operating BPS on BkPRNC with the Activity Mode: Loaded or Active................................................................................. 444 Deleting BPS fallback.................................................................447 RAN2512: Network Resiliency for RNC2600............................. 449
Activating, operating, and maintainin g RAN2512: Network Resiliency for RNC2600............................................................. 460 RAN2512: Network Resiliency for RNC2600 activation procedure overview..................................................................................... 460
8.3.9.5.1
DN09203161Issue:02
8.3.9.5.2
Activating RAN2512: Network Resiliency for RNC2600............ 460
Synchronizing RNCSRV.............................................................472 Configuring associations to the core network............................ 476
8.3.9.5.2.8 8.3.9.5.2.9 8.3.9.5.2.10
Configuring Iur interface towards neighboring RNCs.................480 Planning Iupc interface configuration......................................... 481 Planning Iu-BC interface configuration for RNC2600 BkPRNC. 482
Committing changes and backup con figuration test.................. 482 Reconfiguring BTS for Network Resili ency................................ 483 Configuring RNCSRV.................................................................483 IP addresses mapping............................................................... 487
8.3.9.5.2.15 8.3.9.5.2.16 8.3.9.5.3
Auto-adaptation in RNC2600..................................................... 488 Testing IP connectivity (optional)................................................489 Operating and Maintaining RAN2512 : Network Resiliency for RNC2600................................................................................... 491
Operating and Maintaining overview.......................................... 491 NetAct topology view..................................................................492 Managing Software.................................................................... 493 Updating SW builds on BkPRNC............................................... 495 Synchronizing.............................................................................497 Maintaining IP connectivity ........................................................498 Interpreting of the system logs................................................... 499 Network Resiliency operations...................................................502 Verifying RAN2512: Network Resilien cy for RNC2600.............. 514 Deactivating RAN2512: Network Res iliency for RNC2600........ 515
8.3.9.8 8.3.9.8.1 8.3.9.8.2
Testing RAN2512: Network Resilienc y for RNC2600.................516 Setup the Network Resiliency for RN C...................................... 517 Normal redundancy switch from PrPR NC to BkPRNC.............. 526
8.3.9.8.3
Redundancy switchback from BkPRN C to PrPRNC.................. 527
Example of values of the M5005C58 counter obtained during Phase 2 of RAN3045 testing............................................................................ 38
Figure 2
Example of values of the M5005C59 cou nter obtained during Phase 2 of RAN3045 testing............................................................................ 39
Figure 3
Example of values of the M5005C60 cou nter obtained during Phase 2 of RAN3045 testing............................................................................ 39
Figure 4 Figure 5
HSUPA settings................................................................................ 100 Overview of the RAN2892: WCDMA-LTE Load Balancing feature in Nokia-based radio network...............................................................143
Figure 6
Signaling of RIM UTRA SI procedure............................................... 152
Figure 7
Signaling of RIM UTRA SI Procedure Err or..................................... 153
Figure 8
The IMEI collection and feature operation concept.......................... 161
RF monitoring in BTSSM.................................................................. 217
Figure 20
RF-scanning measurement result for Raw Composite Rx or Composite Rx................................................................................... 218
Figure 21
RF-scanning measurement result for Car rier Rx..............................219
Figure 22
PIM simulation test result................................................................. 221
Figure 23
PIM desensitization test result..........................................................223
SIEM system GUI.............................................................................258 Overview of RAN2973: IMSI-based Call Monitoring.........................269
Figure 31
User Plane monitored data on Iu-PS interface.................................270
Figure 32
End-to end IPv4 packet TCP/UDP/ICMP......................................... 270
Figure 33
User Plane monitored data on Iu-CS interface.................................270
Figure 34
User Plane monitored data on Iub interface for PS and CS calls.....271
Figure 35
Transport Plane monitored data on Iu-PS interface......................... 271
RAN3043 hardware and software require ments................................ 41 New counters introduced by RAN3043.............................................. 41
Table 8
Existing counters related to RAN3043................................................41
Table 9
New parameters introduced by RAN304 3.......................................... 41
Maximum number of calls that be monitor ed based on RNC and monitoring configuration................................................................... 274
Table 124 Table 125
RAN2973 Sales information............................................................. 274 Licenses for RAN2973: IMSI-based Monitoring............................... 275
Table 126
Licenses for RAN2973: IMSI-based Monitoring............................... 283
Table 127
RAN2973 symptoms and recovery actions...................................... 289
Required number of SCTP associations in Iu and Iu-PC compared to a basic situation without network resiliency .....................................356
Table 160
Required number of SCTP associations in Iur compared to a basic situation without network resiliency.................................................. 356
Table 161
Supported IP mapping relationships.................................................357
Flexi Lite’s features are planned separately. Please contact HetRAN Product Management for further information. Note:
Changes between issues 01H (2016-07-11, WCDMA 16) and 02 (2016-07-15, WCDMA 17)
RAN2991: Modification of WCDMA Frequency • •
RAN2991 Functional description has been updated. Step1 in Testing RAN2991 has been updated.
RAN3005: Network Resiliency for mcRNC • • • • •
Miscellaneous notes has been updated. RAN3005 System impact has been updated. BkPRNC-related alarms in Net Act has been removed. NetAct topology view has been added. Create BkPRNC object at PrPRNC (mcRNC) has been updated.
Changes between issues 01G (2016-06-13, WCDMA 16) and 01H (2016-07-11, WCDMA 16) RAN3046: Interference Cancellation for 4Rxhas been added. Changes between issues 01F (2016-04-12, WCDMA 16) and 01G (2016-06-13, WCDMA 16) RAN2504: Configurable Service Accounts has been added.
RAN3086: CSFB with RIM •
002:2306 CSFB_WITH_RIM PRFILE parameter has been added toRAN3086
Reference data.
RAN2991: Modification of WCDMA Frequency •
RAN2991 Functional description has been updated.
•
Step1 in Testing RAN2991 has been updated.
RAN3057: mcRNC Signaling Capacity License • •
RAN3057 Functional description has been updated. Alarm 3295 licence_capacity_exceeded_ahas been added toRAN3057 Reference data.
1 Introduction to WCDMA 16 features This document provides feature descriptions and instructions for the WCDMA 16 release. Note that the subchapter Interdependencies between features lists only dependencies among Nokia RAN WCDMA features. If the feature has no specific hardware requirements, it means that only WCDMA System Module must be used.
g
DN09203161Issue:02
Note: WCDMA 16 is supported by NetAct 16.2 and NetAct 15.5 + INES PP337. For INES support, seeWCDMA 16 Basic Support with NetAct 15.5 + INES PP337 .
WCDMA 16 Basic Support with NetAct 15.5 + INES PP337
WCDMA 16 Feature Descriptions and Instructions
2 WCDMA 16 Basic Support with NetAct 15.5 + INES PP337 INES (Instant Network Element Support) with NetAct 15.5 + PP337 provides basic NetAct management support and compatibility with WCDMA 16. No NetAct SW upgrade is needed, only OSS metadata and configurations for WCDMA 16 are updated to NetAct. INES support in PP337 includes: •
•
WCDMA 16 level Fault Management (FM) and Configuration Management(CM) metadata to be used by NetAct Monitor and Configurator, and FM and CM Northbound Interfaces. Compatibility for several NetAct applications, forexample, NetAct SW Manager.
INES support in PP337 does NOT include: •
•
WCDMA 16 level Performance Management (PM) metadata (new KPIs, measurements, or counters) to be used by NetAct Performance Manager and PM NBI. The new PM data is visible via OMS applications. Any advanced features like 3G Rehosting or WCDMA Frequency Modification.
Recommendations and workarounds: •
Site Rehosting –
•
Performance Management - counters/KPIs – –
•
Rehosting should be donewith the RU50 or RU50 EP1 level SW if BTS rehosting between RNCs is needed.
New counters introducedin WCDMA 16 are visible in OMS. Reports with the new counters can be created with OMS tools.
Documentation of WCDMA 16 alarms, parameters, and counters –
Complete documentation ofthe new or modified alarms, parameters, and counters can be found in the WCDMA 16 operating documentation.
Features supported by INES PP337: •
Radio resource management and Telecom features –
RAN3045: Activity BasedUL Power Control for Rel99 DCH
–
RAN3043: Advanced HSUPA Time Division Scheduling RAN3218: Enhanced CellChange from HSPA to 2G
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 Basic Support with NetAct 15.5 + INES PP337
RAN2367: DNS Support for Certificate Examination RAN3247: Energy Efficiency ShutDown Mode with RF Sharing RAN2973: Enhanced IMSI Based Call Monitoring RAN3060: Flexi Multiradio BTS Antenna Rx RF-sniffing RAN2872: IPA-RNC Symptom Report RAN3150: mcRNC Event Based Symptom Data Collection RAN2268: Multi-Layer Certificate Authorities RAN3096: OMS HP Gen9 HW RAN2571: Support of TLS 1.2
Performance monitoring features
g
Note: PM counter management via OMS16. NetAct 16.2 required for NetAct management support. – – – – •
RAN2862: Multi-RAB Dedicated Counter Set RAN2304: VSWR Monitoring
RNC solution features – – –
•
RAN2164: Compensated CQI Measurement RAN3104: HSPA User Amount Monitoring
RAN2624: External Alarm Input Support of mcRNC RAN3057: mcRNC Signaling Capacity License RAN3005: Network Resiliency for mcRNC
WCDMA 16 Basic Support with NetAct 15.5 + INES PP337
–
RAN2706: Delta Configuration and Change Notifications forBTS Transport RAN3063: KPI Reporting Based on Cell Type RAN2991: Modification of WCDMA Frequency
–
RAN2702: Parameter Level Logging of BTS User Events
3 Radio resource management features 3.1 RAN3045: Activity Based UL Power Control for Rel99 DCH Introduction to the feature With the RAN3045: Activity Based UL Power Control for Rel99 DCHfeature, when a UE is in CELL_DCH state using R99 DCH in uplink (UL) and no data needs to be sent at the moment, its transmission power is lowered to minimum. Thus, the uplink interference from the R99 DCH UL control channel is reduced.
3.1.1
RAN3045 Benefits End-user benefits In case of HSPA cell with R99 UEs, end user benefits from improved HSPA throughput. In case of a R99 cell, more users can be accepted to the cell. Operator benefits Operator benefits from reduced uplink interference (coming from Rel99 UE L1 control channel when there is no data to be sent) and improved HSPA cell throughput. The feature significantly improves the cell capacity when the dominating traffic is in discontinuous or burst patterns, for example, AMR calls.
3.1.2
RAN3045 Functional description In the current implementation, when a UE is in a CELL_DCH state using R99 DCH, it does not have control channel gating, that means, signaling over uplink control channel DPCCH continues even if there is no UL data to be sent. With the RAN3045: Activity Based UL Power Control for Rel99 DCHfeature, BTS detects the uplink data channel inactivity and commands a UE to reduce transmitting power of the UL DPCCH control channel, when UL data channel is inactive. Thus, the UL interference from R99 DCH UEs is reduced, and cell HSPA data capacity increases.
g
Note: The activity based power control is not used when UL TFCI number is greater than 16 or when a UE is in a compressed mode. This feature can work together withRAN3040: IRC Receiver and RAN1308: HSUPA Interference Cancellation Receiverfeatures, which also reduce UL interference.
3.1.3
RAN3045 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity With this feature, uplink interference from R99 DCH UE uplink control channel is reduced. It also provides higher HSPA data cell throughput. With this feature, the cell capacity gain for PA3 channel is up to 5% for voice and PS64 services (assuming 50% activity).
3.1.4
RAN3045 Reference data Requirements Table 1
RAN3045 hardware and software requirements
RAS
I PA - R N C
mc R N C
WCDMA 16
Support not required
Support not required
OMS
NetAct
Support not required
NetAct 16.2
MS C
Support not required
Flexi Multiradio BTS
WBTS16
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
WBTS16
MGW
Support not required
Under planning UE
Support not required
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms There are no alarms related to this feature. Measurements and counters Table 2
New counters introduced by RAN3045
C o u n t e rI D
C o u n t e rn a me
M eas u re me n t
M5005C58
SUM OF R99 USERS
HSPA in WBTS Extension
M5005C59
SUM OF ABPC USERS
HSPA in WBTS Extension
M5005C60
R99 AND ABPC USERS DENOMINATOR
Table 3
HSPA in WBTS Extension
Existing counters related to RAN3045
C o u n t e rI D
C o u n t e rn a me
M1000C320÷M 1000C341
RECEIVED TOTAL WIDEBAND POWER CLASS 0÷RECEIVED TOTAL WIDEBAND POWER CLASS 21
Cell Resource
M eas u re me n t
M5000C151
HSUPA MINIMUM MAC-D THROUGHPUT
HSPA in WBTS
M5000C152
HSUPA MAXIMUM MAC-D THROUGHPUT HSPA in WBTS
M5000C153
HSUPA AVERAGE MAC-D THROUGHPUT HSPA in WBTS
Key performance indicators There are no key performance indicators related to this feature. Parameters
New parameters introduced by RAN3045 F u l ln a m e
A b b r e v i at e dn a m e
Activity based UL power control for Rel99 DCH enabled
activityBasedULPowCtr lEnabled
M a n a g e do b j e c t
BTSSCW
Commands There are no commands related to this feature. Sales information Table 5
RAN3045 Sales information
B SW/AS W
ASW
3.1.5
S W c o mp o n e n t
RAN
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
BTS LK
Activating RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to activate this feature. Before you start Restart of the RNC or the BTS is not required after the activation of this feature. This procedure does not cause downtime and it can be activated at any time of the day. Make sure you have access to the following applications: •
BTS Site Manager
The RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is controlled by a license and requires a valid license file. The feature code for this feature is 5578. Make sure you have the license file installed and the license state is 'Valid'.
Open BTS Site Manager and establish a connection to the BTS.
2
From the menu on the left-hand side, select Commissioning.
3
In Commissioning type, select Reconfiguration, then deselect TRS.
4
Proceed to the BTS Settings page by clicking Next.
5
Select the 'Activity based UL power control for Rel99 DCH' checkbox.
6
Proceed to the Send Parameters page by clicking Next.
7
Click Send parameters.
8
Proceed to the Commissioning Report page by clicking Next, and then click Finish.
Expected outcome The RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is activated.
3.1.6
Verifying RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to verify if the RAN3045: Activity Based UL Power Control for Rel99 DCH feature works properly in the network. Before you start Make sure you have access to the following applications:
Open the RNW Measurement Management application in the Application Launcher.
2
Start the measurement for the M5005C59 SUM OF ABPC USERS counter. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
Set up one R99 call that meets the following conditions: •
• •
•
Transport format combination indicator (TFCI) number in uplink is less than or equal to 16. This can be checked from the TFCS IE in RADIO LINK SETUP message. There are less than or equal to 16 TFCS instances in the TFCS (UL) IE. TFCI 0 is decoded with good quality. No compressed mode is activated in the UE. This can be checked from the Radio Link Reconfiguration Procedure - no compressed mode configuration and activation in the procedure. The UE is not set up for test purpose (test mode, loop test, and so on).
Note that even if the above conditions are fulfilled, the RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is not used on the R99 UE in case when TFCI = 0 does not correspond to UL data discontinuous transmission (DTX) in UL transport format combination set (TFCS) configuration (although such case is very rare).
4
g
Open the RNW Me asurement Presentation application and check the value of the counter M5005C59. Note: Measurement results are available in the application at the next full hour plus 10 minutes. For example, if you start the measurement at 11:22, the collected data is available in OMS at 12:10.
Expected outcome The value of the M5005C59 counter is a non-zero value between 0 and 36000.
3.1.7
Deactivating RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose Follow this procedure to deactivate this feature. Before you start Make sure you have an access to the following applications:
Open BTS Site Manager and establish a connection to the BTS.
2
From the menu on the left-hand side, select Commissioning.
3
In Commissioning type, select Reconfiguration, then deselect TRS.
4
Proceed to the BTS Settings page by clicking Next.
5
Deselect the 'Activity based UL power control for Rel99 DCH' checkbox.
6
Proceed to the Send Parameters page by clicking Next.
7
Click Send parameters.
8
Proceed to the Commissioning Report page by clicking Next, and then click Finish.
Expected outcome The RAN3045: Activity Based UL Power Control for Rel99 DCHfeature is deactivated.
3.1.8
Testing RAN3045: Activity Based UL Power Control for Rel99 DCH Purpose
g
Note: This is an example of verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks. The purpose of this test case is to verify that the RAN3045: Activity Based UL Power Control for Rel99 DCH feature is working on BTS. The following counters are to be checked: • • •
HW configuration: FSME+FSME+2FRGP/2FRGT 20W (F222-x-146-1TX-4RX E Type), FSMF+FRGT (F111)
Before you start Preconditions: • •
• •
3.1.8.1
WBTS has an 'On Air' status Valid license for the RAN3045: Activity Based UL Power Control for Rel99 DCH feature (feature code: 5578) is installed on the BTS. 2-10 cell phones are available for testing. The RAN3045: Activity Based UL Power Control for Rel99 DCHmust be deactivated before you startphase 1 of testing.
Phase 1: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature deactivated Procedure
1
Check values of the co unters M5005C58, M5005C59, and M5005C60 and record them.
2
Set up 2-10 AMR calls, and then mute the UEs to trigger DTX.
3
Release the calls.
4
Check values of the counters M5005C58, M5005C59, and M5005C60, and compare them with the values recorded in step 1.
Expected outcome Values of the counters M5005C58 and M5005C59 are not updated. Value of the M5005C60 counter is updated and different from 0.
Phase 2: Testing with the RAN3045: Activity Based UL Power Control for Rel99 DCH feature activated Procedure
1
Check values of the co unters M5005C58, M5005C59, and M5005C60 and record them.
2
Activate t he RAN3045: Activity Based UL Power Control for Rel99 DCHfeature. For more information, seeActivating RAN3045: Activity Based UL Power Control for Rel99 DCH.
3
Set up 2-10 AMR calls, and then mute the UEs to trigger DTX.
4
Release the calls.
5
Check values of the counters M5005C58, M5005C59, and M5005C60, and compare them with the values recorded in step 1.
Expected outcome Only with the RAN3045: Activity Based UL Power Control for Rel99 DCH(ABPC) feature activated, values of the counters M5005C58, M5005C59, and M5005C60 are updated and different from 0. Figure 1
38
Example of values of the M5005C58 counter obtained during Phase 2 of RAN3045 testing
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.2 RAN3043: Advanced HSUPA Time Division Scheduling Introduction to the feature The RAN3043: Advanced HSUPA Time Division Schedulingfeature introduces extension of 2 ms TTI one HARQ scheduling to higher bitrates (one HARQ peak bitrate of 320kbit/s - 1 Mbit/s, or average bitrate of 40-120 kbit/s) to improve HSUPA throughput when there is a medium number of 2 ms TTI UEs in a cell.
3.2.1
RAN3043 Benefits End-user benefits End users benefit from:
Improved HSUPA throughput for 2 msTTI UEs when there is 8-16 of such UEs in a cell (assuming continuous UL traffic). The number of UEs may be bigger if the UEs generate bursty traffic. Better average RTT timings of the UEs.
Operator benefits This feature provides gain in a cell capacity as a result of reduced UL intra-cell interference thanks to time division scheduling of the users.
3.2.2
RAN3043 Functional description The RAN3043: Advanced HSUPA Time Division Schedulingfeature introduces support for higher average bitrates (between 40 kbit/s and 120 kbit/s) for 2 ms TTI one HARQ scheduling. In current implementation all available HARQ processes are allocated for those bitrates. The 2 ms TTI one HARQ scheduling was introduced in RU20 SW release with the RAN1470: HSUPA 2ms TTIfeature. With RAN3043: Advanced HSUPA Time Division Scheduling feature, this scheduling mechanism is extended to higher bitrates. Thanks to this, the intra-cell interference and E-DPCCH signaling are reduced when there is a medium number of 2 ms UEs in a cell (about 8-16 assuming continuous UL traffic users; this number may be slightly bigger when there are users with UL bursty traffic in a cell).
g
Note: This feature does not affect the scheduling done for the 10 ms UEs (that is, UEs with 10 ms TTI), since 10 ms UEs do not support HARQ-specific scheduling. For 10 ms UEs, always all available HARQ processes are activated. The 2 ms UEs are scheduled with higher bitrates based on various factors, for example, number of UEs in a cell, radio conditions, cell load, QoS parameters, and so on. This means that the cell can have mixed set of UEs (with 2 ms TTI one HARQ with higher bitrate UEs, 2 ms one HARQ with lower bitrate UEs, 2 ms all HARQ UEs, and 10 ms all HARQ UEs) at any point in time. One HARQ allocation with higher throughput is applied only for the scheduled MAC-d flows.
3.2.3
RAN3043 System impact Interdependencies between features The RAN1470: HSUPA 2ms TTI feature is a prerequisite for using this feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity With this feature, the cell capacity gain is expected to be up to 30% (assuming 16 UEs generating continuous UL traffic in PA3 channel conditions). Also, the cell throughput is improved when there is about 8-16 users in a cell. Gain is also possible with slightly higher number of users, when the users have bursty UL traffic.
This feature has no impact on baseband dimensioning.
3.2.4
RAN3043 Reference data Requirements Table 6
RAN3043 hardware and software requirements
RAS
I PA - R N C
mc R N C
WCDMA 16
Support not required
Support not required
OMS
NetAct
Support not required
NetAct 16.2
Fl exi Multiradio BTS WBTS16
MS C
Support not required
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS WBTS16
Under planning
MGW
UE
Support not required
Support not required
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms There are no alarms related to this feature. Measurements and counters Table 7
New counters introduced by RAN3043
C o u n t e rI D M5000C477
C o u n t e rn a me HSUPA USERS WITH 2MS TTI DENOMINATOR
M e as u r e m e n t HSPA in WBTS
M5000C478
HSUPA USERS WITH 10MS TTI DENOMINATOR
HSPA in WBTS
M5000C479
SUM OF HSUPA USERS USING HSPA in WBTS ADVANCED SCHEDULING FOR EACH TTI
M5000C480
HSUPA USER USING ADVANCED SCHEDULING DENOMINATOR
Table 8
HSPA in WBTS
Existing counters related to RAN3043
C o u n t e rI D
C o u n t e rn a me
M e as u r e m e n t
M5000C324
SUM OF HSUPA USERS WITH 2MS TTI
HSPA in WBTS
M5000C325
SUM OF HSUPA USERS WITH 10MS TTI
HSPA in WBTS
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 9
New parameters introduced by RAN3043 F u l ln a m e
A b b r e v i at e dn a m e
M a n a g e do b j e c t
Advanced HSUPA Time Division advHSUPATimeDivSchedE BTSSCW Scheduling enabled nabled
Commands There are no commands related to this feature. Sales information Table 10
RAN3043 Sales information
BSW/ASW
ASW
3.2.5
S W comp on en t
RAN
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
BTS LK
Activating RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to activate this feature. Before you start Restart of the RNC or the BTS is not required after the activation of this feature. This procedure does not cause downtime and it can be activated at any time of the day. Make sure you have access to the following applications: •
BTS Site Manager
The RAN3043: Advanced HSUPA Time Division Schedulingfeature is controlled by a license and requires a valid license file. The feature code for this feature is 5498. Make sure you have the license file installed. The license state must be set to ON.
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 HSUPA Settings page by clicking Next.
5
Select the 'Advanced HSUPA Time Division Scheduling' 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 RAN3043: Advanced HSUPA Time Division Schedulingfeature is activated.
3.2.6
Verifying RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to verify if the RAN3043: Advanced HSUPA Time Division Scheduling feature works properly in the network. Before you start Make sure you have access to the following applications:
Open the RNW Measurement Management application in the Application Launcher.
2
Start the measurement for the M5000C479 SUM OF HSUPA USERS USING ADVANCED SCHEDULING FOR EACH TTI and M5000C480 HSUPA USER USING ADVANCED SCHEDULING DENOMINATOR counters. For details on starting the measurements in the RNW Measurement Management application, seeStarting radio network measurementsin Managing and viewing RNC measurements.
g
Note: Advanced HSUPA Time Division Scheduling may be applied immediately or even after a few hours, depending on the number of UEs with 2ms TTI, cell load, traffic profile, and so on. As soon as the RAN3043 scheduling is applied, the counters' values are increased.
3
Open the RNW Me asurement Presentation application and check the value of the M5000C479 and M5000C480 counters. For details on checking the counter values in the RNW Measurement Presentation application, seeViewing and modifying radio network measurement parametersin Managing and viewing RNC measurements.
Expected outcome The M5000C479 and M5000C480 counters' values are increased.
3.2.7
Deactivating RAN3043: Advanced HSUPA Time Division Scheduling Purpose Follow this procedure to deactivate this feature. Before you start Restart of the RNC or the BTS is not required after the deactivation of this feature. Make sure you have an access to the following applications: •
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 HSUPA Settings page by clicking Next.
5
Clear the 'Advanced HSUPA Time Division Scheduling' 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 RAN3043: Advanced HSUPA Time Division Schedulingfeature is deactivated. Further information After deactivating the feature set the feature license state to OFF.
3.3 RAN3218: Enhanced Cell Change from HSPA to 2G Introduction to the feature The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH before the GSM measurements.
g 3.3.1
Note: The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature supports MultiRAB (AMR + HSPA) CM.
RAN3218 Benefits End-user benefits This feature provides higher end-user data capacity since there are more HSPA/HSDPA configurations operated within the network when comparing to R99 DCH.
Operator benefits This feature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH. This means decreased signaling and optimized resource consumption at the moment of measurements. The DCH resource allocations are not needed before the measurements.
3.3.2
RAN3218 Functional description The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature provides improved inter-system handover and cell change procedures performed from the WCDMA network to the GSM network. The procedures can be performed from the HSPA/HSDPA without changing the configuration to the DCH before the GSM measurements. This means that the GSM is measured with or without the compressed mode when the UE has HSPA/HSDPA configuration. When the feature is not activated, then the users are reconfigured to the DCH configuration before the GSM measurements. This feature does not change the triggers and conditions for the inter-system handover and cell change procedures meaning for example handling of different RAB combinations. The use of the feature can be allowed or denied for certain UEs with the Device Detection mechanism. For more information on Device Detection mechanism, see RAN3082: Device Detection.
3.3.3
RAN3218 System impact Interdependencies between features The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature requires the following features: •
RAN1.5009: WCDMA - GSM Inter-System Handover If RAN1.5009 is not enabled, ISHO from WCDMA to GSM cannot be triggered.
•
RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Features RAN3218 and RAN1668 work under the same feature license.
g
Note: The features work under the same feature license. Impact on interfaces This feature impacts interfaces in the following way: •
The CM measurement parameters for GSMare adapted to the HSPA/HSDPA configurations.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature impacts system performance and capacity in the following way:
The procedure of the inter-system handover isperformed from the HSPA/HSDPA without changing the configuration to the DCH which provides better performance at the moment of the GSM measurements.
RAN3218 Reference data Requirements Table 11 RAS
WCDMA 16
RAN3218 hardware and software requirements I PA - R N C
RNC16
mc R N C
mcRNC16
OMS
NetAct
WCDMA OMS16
NetAct 16.2
Fl exi Multiradio BTS
Support not required
MS C
Support not required
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required MGW
Support not required
Support not required UE
Support not required
This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters Table 12 C o u n t e rI D
C o u n t e rn a m e
Me as u re me n t
M1002C695
ALLOCATION FOR HSPA 2G ISHO COMPRESSED MODE
Traffic
M1002C696
ALLOCATION DURATION FOR HSPA 2G ISHO COMPRESSED MODE
Traffic
M1010C274
ISHO ATTEMPTS TO 2G WITH HSPA COMPRESSED MODE
Inter System Hard Handover
M1010C275
SUCCESSFUL ISHO TO 2G WITH COMPRESSED MODE
Inter System Hard Handover
Table 13 C o u n t e rI D
DN09203161Issue:02
New counters introduced by RAN3218
Existing counters related to RAN3218 C o u n t e rn a m e
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 14
New parameters introduced by RAN3218 F u l ln am e
A b b r e v i a t e dn a me
Transmission Gap Pattern Length for GSM measurements with HSPA/HSDPA
Table 15
M an a g e do b j e c t
RNHSPA
TGPLForHSGSMMeas
Parameters modified by RAN3218 F u l ln am e
A b b r e v i a t e dn a me
BTS support for HSPA CM
M an a g e do b j e c t
WBTS
BTSSupportForHSPACM
Max number of UEs in HSDPA CM due to critical HO
MaxNumberUEHSPACmHO
WCEL
Max number of UEs in HSDPA CM due to NCHO
MaxNumberUEHSPACmNCHO
WCEL
Whitelist features
Whitelist
WDEV
Blacklist features
Blacklist
WDEV
Commands There are no commands related to this feature. Sales information Table 16
RAN3218 sales information
B S W /A S W
ASW
3.3.5
S W c o mp o n e n t
RAN
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
RNC LK
Activating RAN3218: Enhanced Cell Change from HSPA to 2G Purpose Follow this procedure to activate the RAN3218: Enhanced Cell Change from HSPA to 2G feature. Before you start After activating this feature, there is no need to restart RNC or BTS. Activation procedure does not require cell-locking and does not cause a down-time in the network.
Activate the licence key and set feature state to ON for the following features: •
RAN1.5009: WCDMA - GSM Inter-System Handover
g
Note: Ensure that in the corresponding FIFILE this feature is enabled. To set the feature state to ON, use the following command: for IPA-RNC: ZWOA:2,747,A;
–
Check feature status: ZWOS:2,747; for mcRNC
–
g •
g
Note: For mcRNC, all FIFLE controlled ASW features are enabled by default. Consequently, for mcRNC those features do not need to be set separately. RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Note: The RAN3218: Enhanced Cell Change from HSPA to 2Gfeature uses the same license as the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handoverfeature. To set the feature state to ON, use the following command: –
for IPA-RNC:
–
for mcRNC:
ZW7M:FEA=4783:ON; set license feature-mgmt code 0000004783 feature-adminstate on
a) Go to the WBTS object using the following path: RNC object ► WBTSs folder ► WBTS object
b) Right-click on the WBTS object and select Edit parameters.
c) On the Packet Scheduler tab, set the value of the BTSSupportForHSPACM parameter to HSDPA CM for IFHO, LTE and GSMor HSPA CM for IFHO, LTE and GSM.
g
Note: Activation of HSPA/HSDPA CM for GSM also activates HSPA/HSDPA CM for IFHO and LTE.
Further information To set the transmission gap pattern length, use theTGPLForHSGSMMeas RNHSPA parameter. To set the maximum number of UEs that are simultaneously in a HSDPA compressed mode in the cell due to a non-critical handover measurement, use the MaxNumberUEHSPACmNCHO WCEL parameter. To blacklist or whitelist UEs for this feature, use the parameters of WDEV object (provided by theRAN3082: Device detection feature).
3.3.6
Verifying RAN3218: Enhanced Cell Change from HSPA to 2G Purpose Follow this procedure to verify if the RAN3218: Enhanced Cell Change from HSPA to 2G feature works properly in the network. Before you start Make sure you have access to the following applications:
Start the M1002 Traffic and M1010 Inter System Hard Handover measurements. Wait for the measurement interval to begin.
g
Note: In case of 15-minute interval, data collection starts every quarter. For example 11:00, 11:15, 11:30, 11:45. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
In an area with GSM coverage, make a PS call mapped to HSPA or HSDPA services. Keep the service active for 15 minutes. The purpose of this step is to trigger compressed mode measurements of the GSM layer and subsequent handover from WCDMA to GSM.
4
Open the RNW Measurement Presentation application.
5
Check if the values of the following counters have been collected: • • •
M1002C695: ALLOCATION FOR HSPA 2G ISHO COMPRESSED MODE M1010C274: ISHO ATTEMPTS TO 2G WITH HSPA COMPRESSED MODE M1010C275: SUCCESSFUL ISHOTO 2G WITH COMPRESSED MODE
Expected outcome The values of counters M1002C695, M1010C274, and M1010C275 increased.
3.3.7
Deactivating RAN3218: Enhanced Cell Change from HSPA to 2G Purpose Follow this procedure to deactivate theRAN3218: Enhanced Cell Change from HSPA to 2G feature.
a) Go to the WBTS object using the following path: RNC object ► WBTSs folder ► WBTS object
b) Right-click on the WBTS object and select Edit parameters.
c) On the Packet Scheduler tab, set the BTSSupportForHSPACM parameter to a value other than HSDPA CM for IFHO, LTE and GSMand HSPA CM for IFHO, LTE and GSM.
3.4 RAN3093: Enhanced MBLB Introduction to the feature The RAN3093: Enhanced MBLB feature enhances load balancing, layering during voice call setup, inactivity-triggered layering and mobility-triggered layering functionalities of the RAN2172: Multi-Band Load Balancingfeature. It introduces new counters for monitoring SLHO Load State and HSPA Load State in correlation with MBLB decisions. The enhancements are based on live-network experience.
3.4.1
RAN3093 Benefits End-user benefits The user is directed to the optimal frequency layer, which improves the overall end-user experience. Operator benefits Multi-Band Load Balancing enables the optimal usage of frequencies within a network according to and operator preferences, UE capabilities, network capabilities, loadbalancing balancing possibilities, services. With the RAN3093: Enhanced MBLB feature, load is made more sensitive, radio resource utilization is more efficient, and radio network performance is higher. In general, operator strategies on how to use the frequency layers can be better supported. Operator has greater control over utilization of the frequency layers.
Enhanced load balancing enables to use theRAN2172: Multi-Band Load Balancing feature just for balancing HSPA load between the layers (without any preferred layer definitions). It is also possible to prevent useless load balancing actions when the HSPA load level is low. When Enhanced load balancing is enabled, Multi-band load balancing can be done just because of the load balancing reasons if both ot the following conditions are met: • •
HSPA load level of the source cell/layer hasreached a specified threshold. HSPA load difference betweenthe source and target cells/layers exceeds a specified threshold.
Enhanced load balancing and the related load thresholds are controlled by radio network parameters. Enhanced layering during voice call setup - Blind IFHO for the standalone SRB Currently, it is possible to perform Multi-Band Load Balancing (MBLB) layer change for voice calls in RAB setup phase. The RAN3093: Enhanced MBLB feature enables changing preferred layer for CS voice call already in the RRC connection setup phase or when starting CS voice call from CCH state. Less signaling is needed for layering as the correct layer is already known before the RAB setup. Enhanced layering during voice call setup - HSPA load state bypass Currently, MBLB sets theHSPA load state for a cell based on the following indications:
•
downlink power and provided average bit rate (HSDPA) uplink noise rise and provided average bit rate (HSUPA)
• •
maximum number of HSDPA users HSUPA resource status in the BTS
•
If the HSPA load state of cell is set by any of these indications, the MBLB does not consider such a cell as possible target cell for the layer change. This is valid for both CS and PS services. However, as theHSPA load state can only be caused by the HSPA load, it does not necessarily indicate congestion for CS AMR speech RAB. The RAN3093: Enhanced MBLB feature provides an option to bypass theHSPA load state. This is possible for CS AMR speech RAB. Voice calls can be moved by MBLB to a target cell even if the target cell is in HSPA load state. This bypass can be set to ON or OFF. This feature is applicable to any MBLB function, which utilizes the HSPA load state for decision making for the CS AMR speech RAB layering. Such MBLB functions are the MBLB Blind IFHO and the MBLB Mobility HO. Enhanced inactivity-triggered layering without compressed mode measurements Inactivity-triggered layer by change is handover. currently being done by using compressed mode measurements followed a hard When enhanced inactivity-triggered layering is enabled and the radio conditions in the source cell are good enough, the decision on the inactivity-triggered layer change is done without compressed mode measurements. Inactivity-triggered layer change can be prevented completely if the radio conditions in the source cell are bad. and the Enhanced inactivity-triggered layering without compressed mode measurements related thresholds for radio conditions are controlled by radio network parameters.
Enhanced mobility-triggered layering Mobility-triggered layer change is currently being done when the preferred layer definitions change during the active set update (ASU) or serving HS-DSCH cell change (SCC) procedures, or when the UE is detected to moving fast. When Enhanced mobility-triggered layering is enabled, the need for mobility triggered layering is additionally checked after the first RAB setup is completed, and in case of multi-RABs, after the AMR RAB setup is completed. Enhanced mobility triggered layeringis enabled with an radio network parameter. Enhanced inactivity-triggered layering in state transition to CCH state Inactivity-triggered layer change is currently being done by using compressed mode measurements followed by a hard handover. When enhanced inactivity-triggered layering is enabled in the state transition to CCH state, inactivity-triggered layer change is done by state transition instead of hard handover when UE is moving from Cell_DCH to Cell_FACH/PCH or URA_PCH state. Enhanced inactivity-triggered layering in state transition to CCH state is enabled by an radio network parameter. Load counters The new counters bring more visibility to a cell load state. Both Load State and HSPA Load State can be monitored in correlation with MBLB decisions.
3.4.3
RAN3093 System impact Interdependencies between features This feature requires theRAN2172: Multi-Band Load Balancingfeature.
g
Note: The features work under the same license. Impact on interfaces Enhanced layering during voice call setupand Enhanced-inactivity triggered layering reduce NBAP and RRC signaling during layering procedures. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
3.4.4
RAN3093 Reference data Requirements Table 17 RAS
WCDMA 16
54
RAN3093 hardware and software requirements I PA - R N C
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
RNC LK
Activating RAN3093: Enhanced MBLB Purpose Follow these procedures to activate the functionalities of RAN3093: Enhanced MBLB feature: • • •
• •
• •
Activating Enhanced load balancing Activating Enhanced layering during voicecall setup - Blind IFHO in RRC setup Activating Enhanced layering during voicecall setup - Blind IFHO for CS voice call from CCH state Activating the MBLB HSPA load state bypass Activating Enhanced inactivity triggered layering without compressed mode measurements Activating Enhanced mobility triggered layering Activating Enhanced inactivity triggered layering i n state transition to CCH state
Before you start
g
Note: After activating this feature, there is no need to restart RNC or BTS. Activating procedure does not require cell-locking. The RAN3093: Enhanced MBLB feature uses the same license as theRAN2172: MultiBand Load Balancing feature. Install the license key for the RAN2172: Multi-Band Load Balancingfeature in the RNC and set the feature state to ON. For more information, see Activating RAN2172: MultiBand Load Balancing. To set the feature state to ON, use the following command: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=1938:ON; set license feature-mgmt code 0000001938 feature-adminstate on
The RAN2172: Multi-Band Load Balancingfeature is enabled in the cell when it's state is set to ON and one or more of the following WCEL parameters is set to value Enabled:
Activating Enhanced load balancing Purpose Follow this procedure to activate the Enhanced load balancingfunctionality of the RAN3093: Enhanced MBLB feature. Before you start Activate the appropriate phases of the RAN2172: Multi-Band Load Balancingfeature in the cells by setting the parameter value toEnabled in one or more of the following WCEL parameters: •
MBLBRABSetupEnabled defining if Multi-Band Load Balancing is enabled in the
RAB setup phase •
•
•
MBLBStateTransEnabled defining if Multi-Band Load Balancing is enabled in the
state transition to Cell_DCH state. MBLBInactivityEnabled defining if Multi-Band Load Balancing is enabled when inactivity is detected in Cell_DCH state MBLBMobilityEnabled defining if Multi-Band Load Balancing is enabled due to mobility in Cell_DCH state
For more information, seeActivating RAN2172: Multi-Band Load Balancing .
g
Note: The LaySelWeightLoad PFL parameter value must be greater than zero in the PFL objects attached to the appropriate cells before HSPA load is used in the layer selection. Verify that the activation of Multi-Band Load Balancing has been successful for the selected phases. For more information, seeVerifying RAN2172: Multi-Band Load Balancing.
a) Right-click on the PFL object and select Edit parameters.
b) For each cell where the enhanced load balancing is activated, configure the following PFL paramaters in the PFL object attached to the cell in question: •
HSPALoadThreshold
•
HSPALoadMargin
Leave the default value or change it according to needs.
5
Expand the RNC object then expand the WCEL object.
6
Configure the WCEL object: Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.
c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced load balancing parameter to True.
7
3.4.5.2
Select Apply to save the changes.
Activating Enhanced layering during voice call setup - Blind IFHO in RRC setup Purpose Follow this procedure to activateEnhanced layering during voice call setup - Blind IFHO in RRC setup functionality of the RAN3093: Enhanced MBLB feature.
Before you start Set the value of the MBLBRABSetupEnabled parameter to Enabled for Blind IFHO in RAB setup phase according to theRAN2172: Multi-Band Load Balancingfeature activation instructions. Procedure
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.
c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO in RRC setup parameter to True.
5
Select Apply to save the changes.
Further information The following PFL parameters are used by this functionality:
3.4.5.3
•
PrefLayerDCHSDAMR
•
PrefLayerHSPAAMR
•
PrefLayerHSDPAAMR
•
PrefLayerR99AMR
Activating Enhanced layering CS voice call from CCH state during voice call setup - Blind IFHO for Purpose Follow this procedure to activate the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality of the RAN3093: Enhanced MBLB feature.
Before you start In the cells, activate the Blind IFHO in RAB setupand MBLB in RAB Setup for Multi RAB functionalities by configuring the following WCEL parameters: •
•
Set the value of the MBLBRABSetupEnabled parameter to Enabled for Blind IFHO in RAB setup. Set the value of the MBLBRABSetupMultiRAB parameter to eitherEnabled when UE is in Cell_FACH/Cell_PCH stateor Enabled when UE is in Cell_DCH/Cell_FACH/Cell_PCH.
For more information, seeActivating RAN2172: Multi-Band Load Balancing . Verify if the activation of Multi-Band Load BalancingBlind IFHO in RAB setupand MBLB in RAB Setup for Multi RAB has been successful. For more information, seeVerifying RAN2172: Multi-Band Load Balancing. Procedure
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.
c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO for CS voice call from CCH states parameter to True.
5
3.4.5.4
Select Apply to save the changes.
Activating MBLB HSPA load state bypass Purpose Follow this procedure to activate the MBLBHSPA load state bypass function of the RAN3093: Enhanced MBLBfeature. This function is possible for AMR CS speech call.
Before you start Enable and configure at least one of theRAN2172: Multi- Band Load Balancingfeature's functions that utilize HSPA load state for decision making, using the following WCEL parameters: •
MBLBRABSetupEnabled
•
MBLBRABSetupMultiRAB
•
–
value: enabled when UE is in Cell_FACH/Cell_PCH state
– –
value: enabled when UE is in Cell_DCH state value: enabled when UE is in Cell_DCH/Cell_FACH/Cell_PCH
MBLBMobilityEnabled
For more information, seeActivating RAN2172: Multi-Band Load Balancing . Procedure
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.
c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Bypass of HSPA load state in case of CS voice call parameter to True.
5
3.4.5.5
Select Apply to save the changes.
Activating Enhanced inactivity-triggered layering without compressed mode measurements Purpose Follow this procedure to activate the Enhanced inactivity-triggered layering without compressed mode measurementsfunctionality of the RAN3093: Enhanced MBLB feature.
Before you start Activate the RAN2172: Multi-Band Load Balancingfeature due to inactivity by setting the MBLBInactivityEnabled WCEL parameter value toEnabled. Verify that the activation of Multi-Band Load Balancing due to inactivity has been successful. For more information, seeActivating RAN2172: Multi-Band Load Balancing .
Procedure 1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object then expand the FMCI object.
4
Configure the FMCI object. Sub-steps
a) Right-click on the FMCI object and select Edit pa rameters.
b) For each cell where the enhanced inactivity triggered layering without compressed mode measurements is activated, configure the MBLBInactivityRSCPThr parameter. Leave the default value or change it according to needs. • •
5
When the DL channel type is DCH, the FMCI parameter set is defined by the NrtFmciIdentifier WCEL parameter. When the DL channel type is HS-DSCH, the FMCIparameter set is defined by the HSDPAFmciIdentifierWCEL parameter.
Define neighbor cells. For each cell where the enhanced inactivity-triggered layering without compressed mode measurements is activated, define the Intra-RNC inter-frequency neighbor cells that can be target cells for blind inactivity-triggered layering by configuring the BlindHOTargetCell ADJI parameter.
a) In Topology Tree view, click the WCEL object and go to Adjacencies tab.
b) Select ADJIs tab and click Create.
c) Under Handover Control tab, set the value of the BlindHOTargetCell ADJI parameter to Enabled.
d) Apply the changes.
g
64
Note: Under one WCEL object it is possible to configure only one ADJI-neighbor per frequency. Define the ADJI-neighbor by setting the value of the BlindHOTargetCell ADJI parameter to Enabled.
a) Right-click on the HOPI object and select Edit pa rameters.
b) For the Intra-RNC inter-frequency neighbor cells configured in the previous step, configure the BlindHORSCPThr HOPI parameter. Leave the default value or change it according to needs.
7
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.
c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering without CM parameter to True.
8
3.4.5.6
Select Apply to save the changes.
Activating Enhanced mobility triggered layering Purpose Follow this procedure to activate the Enhanced mobility triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature. Before you start Activate the RAN2172: Multi-Band Load Balancingfeature due to mobility by setting the value of the MBLBMobilityEnabled WCEL parameter toEnabled. For more information, seeActivating RAN2172: Multi-Band Load Balancing . Verify that the activation of theRAN2172: Multi-Band Load Balancingfeature due to mobility has been successful. For more information, seeVerifying RAN2172: Multi-Band Load Balancing.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.
c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced mobility-triggered layering parameter to True.
5
3.4.5.7
Select Apply to save the changes.
Activating Enhanced inactivity triggered layering in state transition to CCH state Purpose Follow this procedure is to activate the Enhanced inactivity triggered layering in state transition to CCH state functionality of the RAN3093: Enhanced MBLB feature. Before you start Activate the RAN2172: Multi-Band Load Balancingfeature due to inactivity by setting the value of the MBLBInactivityEnabled WCEL parameter toEnabled. For more information, seeActivating RAN2172: Multi-Band Load Balancing . Verify that the activation ofMulti-Band Load Balancingdue to inactivity has been successful. For more information, seeVerifying RAN2172: Multi-Band Load Balancing .
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Assign the PFL identifier in WCEL from the PFLidentifier parameter.
c) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering to CCH states parameter to True.
5
3.4.6 3.4.6.1
Select Apply to save the changes.
Verifying RAN3093: Enhanced MBLB Verifying Enhanced load balancing Purpose Follow this procedure to verify if the Enhanced load balancingfunctionality of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Activate MBLB in the RAB setup phaseby setting the value of the MBLBRABSetupEnabledWCEL parameter toEnabled in the source cell. For more information, seeActivating RAN2172: Multi-Band Load Balancing .
g
Note: Enhanced load balancing functionality can be used in all MBLB phases but it is easier to verify it in RAB setup phase. In the PFL objects attached to the source cell, set the values of the following weighting factors to 0:
Note: There is no restriction to use HSPA load, band capability, RSCP and preferred layer definitions together in the layer selection but it is easier to verify the Enhanced load balancingfunctionality when band capability, RSCP and preferred layer definitions are not used in the layer selection. Make sure you have access to the following applications: • •
Start the M1000 CELL RESOURCE and M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15-minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
Wait until th e measurement int erval sta rts.
4
In the cell where the enhanced load balancing functionality is ac tivated (source cell), make several PS NRT data calls with 5-second intervals .
5
Keep making PS NRT data calls until HSPA load level in the source cell exceeds the threshold determined by theHSPALoadThreshold parameter in the PFL object attached to the source cell. : The HSPA load level can be verified from the counters: • • •
g
68
M1000C409: SUM OF HSPA LOAD LEVEL SAMPLES M1000C410: HSPA LOAD LEVEL DENOMINATOR M1000C411: MAX HSPA LOAD LEVEL Note: Load balancing does not start until the HSPA load level in the source cell exceeds the threshold determined by the HSPALoadThreshold PFL parameter. When the threshold is exceeded, the UE is handed over to a less-loaded cell in the RAB setup phase
Open the RNW Measurement Presentation application.
7
Check the values of the following counters after the measurement data has been collected: •
M1008C311 MBLB BLIND HO ATTEMPTS WITH LOAD
•
M1008C318: SUCCESSFUL MBLB BLIND HO
For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome Values of the counters M1008C311 and M1008C318 have been incremented.
g
Note: Counters M1008C311 and M1008C318 are not updated until the HSPA load level in the source cell exceeds the threshold determined by theHSPALoadThreshold PFL parameter. Unexpected outcome Blind handover in RAB setup phase has failed, which is indicated by the value increase of counter M1008C311: MBLB BLIND HO ATTEMPTS WITH LOAD.
3.4.6.2
Verifying Enhanced layering during voice call setup - Blind IFHO in RRC setup Purpose Follow this procedure to verify if the Enhanced layering during voice call setup Blind IFHO in RRC setup function of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Make sure you have access to the following applications: • •
Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
Wait until th e measurement int erval sta rts.
4
Configure the RAN2172: Multi-Band Load Balancingfeature so that the source cell is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE. For more information, seeActivating RAN2172: Multi-Band Load Balancing .
5
Make an AMR CS s peech RAB call in the source cell.
6
Open the RNW Measurement Presentation application.
7
Monitor if MBLB moves UE to the target cell by Blind IFHO in RRC setup phase. The M1008C309: MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA counter indicates the Blind IFHO in RRC setup. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome The AMR CS speech RAB was moved to the target cell by the Blind IFHO in RRC setup phase and value of the counter M1008C309 has been incremented. Unexpected outcome The AMR CS speech RAB was not moved to the target cell by the Blind IFHO in RRC setup phase but the establishment was done in the source cell. Further information This functionality uses the following PFL parameters:
Verifying Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state Purpose Follow this procedure to verify if the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state function of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Ensure the Blind IFHO for CS voice call from CCH state function of the RAN3093: Enhanced MBLB feature is activated and theBlind IFHO in RRC setup function is deactivated. Make sure you have access to the following applications: • •
Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
Wait until th e measurement int erval s tarts.
4
Configure the Blind IFHO in RAB setup and MBLB in RAB Setup for Multi RAB functionalities of theRAN2172: Multi-Band Load Balancingfeature so that the source cell is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE. For more information, seeActivating RAN2172: Multi-Band Load Balancing
Make the PS NRT RAB to s top all data transfer and wait until the inactivity is detected for the UE and the UE is transferred to Cell_FACH/Cell_PCH.
7
Make an AMR CS speech call.
g
Note: To verify the Enhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality, the RSCP value reported by a UE is needed. However, reporting the RSCP value is optional for the UE and it is possbile that UE does not report it.
8
Open the RNW Measurement Presentation application.
9
Monitor if when the UE is transferred to Cell_DCH state, the UE is a lso moved to the correct layer based on its capabilities (service is always AMR in this case). The M1008C309: MBLB BLIND HO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA counter indicates the Blind IFHO for CS voice call from CCH state. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome The AMR CS speech RAB was moved to the target cell by the Blind IFHO for CS voice call from CCH state and value of the M1008C309 counter has been incremented. Unexpected outcome The AMR CS speech RAB was not moved to the target cell by the Blind IFHO for CS voice call from CCH state but the establishment was done in the source cell.
3.4.6.4
Verifying the MBLB HSPA load state bypass Purpose Follow this procedure to verify if the MBLB HSPA load state bypassfunction of the RAN3093: Enhanced MBLB feature works properly in the network. This function is possible for AMR CS speech call. Before you start Ensure the MBLB HSPA load state bypassfunctionality of the RAN3093: Enhanced MBLB feature is activated and the Blind IFHO functionality of the RAN2172: Multi-Band Load Balancing feature is activated and configured. Alternatively,Mobility IFHO functionality of the RAN2172: Multi-Band Load Balancingfeature can be used. For more information, see theActivating RAN2172: Multi-Band Load Balancing feature activation.
W ith th e RAN2172: Multi-Band Load Balancing feature, configure layer definitions (PFL-Preferred Frequency Layer parameters) sothe thatpreferred the target cell has higher preference score than the source cell. For more information about the MBLB preference score and preferred layer definitions, see the Handover Control Functional Area Description.
2
Arrange HSPA load state in the MBLB target cell. This can be achieved by loading the target cell so that any of the four triggers turns the HSPA load state on in the target cell: • • • •
downlink power and provided average bit rate (HSDPA) uplink noise rise and provided average bit rate (HSUPA) maximum number of HSDPA users HSUPA resource status in the BTS
For example, set the maximum number of HSDPA users to a desired value in the target cell using the MaxNumberHSDPAUsers WCEL parameter. Then, allocate PS NRT HSDPA calls so that the maximum level is reached. For more information aboutHSPA load state, see the Handover Control Functional Area Description.
3
Open the RNW Measurement Management application.
4
Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
Make an AMR CS speech call in the source cell. Use MBLB Blind IFHO for triggering the layer change.
7
Open the RNW Measurement Presentation application.
8
Monitor if MBLB moves UE to the target cell irrespective of the HSPA load state. The M1008C312: MBLB BLIND HO ATTEMPTS USING HSPA LOAD BYPASS counter indicates theHSPA load state bypass. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome The AMR CS speech call is moved to the target cell by the MBLB and the value counters M1008C312 increased. Unexpected outcome The AMR CS speech call is not moved to the target cell by the MBLB but the establishment is done in the srcinal source cell. Further information: The following counters indicate the blocking due to the MBLBHSPA load state. The new feature decreases the blocking of AMR speech call due to MBLB HSPA load state: • •
M1008C316: BLOCKED MBLB IFHO DUE HSPA LOAD M1008C317: BLOCKED MBLB BLHO DUE HSPA LOAD
The following counters indicate the MBLB layer change attempts using the new HSPA load state bypass feature: •
M1008C312: MBLB BLINDHO ATTEMPTS USING HSPA LOAD BYPASS
•
M1008C313: MBLB IFHOATTEMPTS USING HSPA LOAD BYPASS
MBLB layer change attempts using theHSPA load state bypass are visible also in the following MBLB counters: • • • • • •
74
M1008C296: MBLB IFHO ATTEMPTS WITH UE BAND CAPA M1008C297: MBLB IFHOATTEMPTS WITH SERVICE AND UE FEATURE CAPA M1008C298: M1008C299: M1008C308: M1008C309: CAPA
MBLB IFHO ATTEMPTS WITH RSCP MBLB IFHO ATTEMPTS WITH LOAD MBLB BLIND HO ATTEMPTS WITH UE BAND CAPA MBLB BLINDHO ATTEMPTS WITH SERVICE ANDUE FEATURE
M1008C310: MBLB BLIND HO ATTEMPTS WITH RSCP M1008C311: MBLB BLIND HO ATTEMPTS WITH LOAD
Also increase in the legacy AMR speech call and signaling link HHO DCH request counters can be seen because theHSPA load state bypass allows AMR speech call setup attempt even if the cell is in HSPA load state: • •
M1002C339 Network elementname: DCH HHO REQ FOR SIG LINK IN SRNC M1002C341 Network element name:RT DCH HHO REQ FOR CS VOICE CALL IN SRNC
If the AMR setup fails in the MBLB target cell due to blocking, the re-attempt in the srcinal source cell is made. In this kind of failure scenario, the attempt is seen both in the target cell and the source cell: • •
3.4.6.5
M1002C0 Network elementname: DCH REQ FOR SIG LINK IN SRNC M1002C12 Network element name:RT DCH REQ FOR CS VOICE CALL IN SRNC
Verifying Enhanced inactivity-triggered layering without compressed mode measurements Purpose Follow this procedure to verify if the Enhanced inactivity-triggered layering without compressed mode measurementsfunctionality of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Make sure you have access to the following applications: • •
Start the M1006 RRC SIGNALLING and M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15-minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
Make a PS NRT data call in the cell where the Enhanced inactivity triggered layering without compressed mode measurementsfunctionality is activated. The call should be made in the cell which is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE.
5
Make the PS NRT RAB to s top all data transfer and wait until the inactivity is detected for the UE.
6
When the PS NRT RAB becomes inactive and if the call is made in the cell where the activation parameters are enabled, the UE is transferred to the correct layer based on its capabilities and allocated RAB combination.
7
Check the value of Enhanced inactivity-triggered layering to CCH states parameter in the MBLBEnhancementsEnabled parameter parent structure.
8
Open the RNW Measurement Presentation application.
9
Check the values of the following counters after the measurement data has been collected: • • • • • • • • • • • •
M1008C296: MBLB IFHO ATTEMPTS WITH UE BAND CAPA M1008C297: MBLB IFHO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA M1008C298: MBLB IFHO ATTEMPTS WITH RSCP M1008C299: MBLB IFHO ATTEMPTS WITH LOAD M1008C300: SUCCESSFUL MBLB IFHO M1008C308: MBLB BLIND HO ATTEMPTS WITH UE BAND CAPA M1008C309: MBLB BLINDHO ATTEMPTS WITH SERVICE ANDUE FEATURE CAPA M1008C310: MBLB BLIND HO ATTEMPTS WITH RSCP M1008C311: MBLB BLIND HO ATTEMPTS WITH LOAD M1008C318: SUCCESSFUL MBLB BLIND HO M1006C323: SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITH CM M1006C325: SUCCESSFUL LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM
The proper working of theEnhanced inactivity-triggered layering without compressed mode measurementsfunctionality of the RAN3093 Enhanced MBLB feature is indicated by one of the following outcomes: •
•
The RRC connection is transferredto Cell_FACH/PCH orURA_PCH state in the current layer if the CPICH RSCP measurement result of the source cell is below the threshold defined with theMBLBInactivityRSCPThr FMCI parameter. The values of the above listed counters have not been incremented. The RRC connection is transferredfrom the current layer to the frequency layer which is defined as the for the the UE threshold if the CPICH RSCP measurement result of the source cell preferred is equal toone or above defined with the MBLBInactivityRSCPThr FMCI parameter and below the threshold defined with the BlindHORSCPThr HOPI parameter. –
If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states
–
parameter is set toFalse, one of the counter values: M1008C296, M1008C297, M1008C298, M1008C299 increases in a source WCEL and thus the value of M1008C300 also increases in a handover target WCEL (target cell depends on PFL settings). If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states
parameter is set toTrue, the M1006C323 counter value increases. •
The RRC connection is transferredfrom the current layer to the frequency layer which is defined as the preferred for the UE if the CPICH RSCP measurement result of the source cell is equal to or above the thresholds defined with MBLBInactivityRSCPThr FMCI parameter and BlindHORSCPThr HOPI parameter. –
If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states
–
parameter is set toFalse, one of the counter values: M1008C308, M1008C309, M1008C310, M1008C311 increases in a source WCEL and thus the value of M1008C318 also increases in a handover target WCEL (target cell depends on PFL settings). If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering to CCH states
parameter is set toTrue, the M1006C325 counter value increases. Unexpected outcome The inter-frequency handover attempt or state transition to the preferred layer has failed. In this case, one of the following counter values are incremented: • • • • •
FAILED MBLB IFHO DUE TO UTRAN FAILED MBLB IFHO DUE TO UE NACK FAILED MBLB IFHO DUE TO UE LOST FAILED LAYER CHANGES IN DCH TO PCH/FACH WITH CM FAILED LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM
Note: MBLB blind handover has attempt and success counters but no failure counters.
Verifying Enhanced mobility-triggered layering Purpose Follow this procedure to verify if the Enhanced mobility-triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature works properly in the network. Before you start Set the value of the MBLBRABSetupEnabled WCEL parameter toDisabled.
g
Note: The Enhanced mobility-triggered layeringis not done if Blind IFHO (layering) has been already done in RAB Setup Phase. Make sure you have access to the following applications: • •
Start the M1008 INTRA-SYSTEM HARD HANDOVER measurements with 15minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
Wait until th e measurement int erval sta rts.
4
Make an AMR call in the cell where the enhanced mobility-triggered layering functionality is activated. The call should be made in the cell which is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE.
5
The UE is handed over to the correct layer immediately after the AMR RAB setup.
6
Open the RNW Measurement Presentation application.
7
Check if the val ues of the following counters after the measurement data have been collected: •
M1008C297: MBLB IFHO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA M1008C298: MBLB IFHO ATTEMPTS WITH RSCP M1008C299: MBLB IFHO ATTEMPTS WITH LOAD M1008C300: SUCCESSFUL MBLB IFHO
For details on using the RNW Measurement see Using. RNW Measurement Presentation in ManagingPresentation and viewing application, RNC measurements
Expected outcome One of the counter values: M1008C296, M1008C297, M1008C298, M1008C299 increases in a source WCEL and thus the value of M1008C300 also increases in a handover target WCEL (target cell depends on PFL settings). The Enhanced mobility-triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature has been activated successfully. Unexpected outcome The inter-frequency handover attempt has failed. The values of the following counters are incremented:
3.4.6.7
•
M1008C301: FAILED MBLB IFHO DUE TO UTRAN
• •
M1008C302: FAILED MBLB IFHO DUE TO UE NACK M1008C303: FAILED MBLB IFHO DUE TO UE LOST
Verifying Enhanced inactivity-triggered layering in state transition to CCH state Purpose Follow this procedure to verify if the Enhanced inactivity-triggered layering in state transition to CCH state functionality of the RAN3093: Enhanced MBLB feature has been successful. Before you start Make sure you have access to the following applications: • •
Start the M1006 RRC SIGNALLING measurement with 15-minute interval. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
Wait until th e measurement int erval sta rts.
4
Make a PS NRT da ta call in the cell where the enhanced inactivity triggered layering in state transition to CCH state functionality is activated. The call should be made in the cell which is not defined as the preferred layer for the UE (based on its capability and service) and there exists a frequency layer which is defined as the preferred one for the UE.
5
Make the PS NRT RAB to s top all data transfer and wait until the inactivity is detected for the UE. When the PS NRT RAB becomes inactive and the call is made in the cell where the activation parameters are enabled, the UE is transferred to the CCH state in the correct layer based on its capabilities and allocated RAB combination.
6
Check the value of Enhanced inactivity-triggered layering without CM parameter in the MBLBEnhancementsEnabled parameter parent structure.
7
Open the RNW Measurement Presentation application.
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, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome The RRC connection is transferred from the current layer to CCH state in the frequency layer defined as the preferred one for the UE, which is indicated by one of the following outcomes:
If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to False, the value of counter M1006C323 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by theMBLBInactivityRSCPThr FCMI parameter and below the threshold defined by theBlindHORSCPThr HOPI parameter, the value of counter M1006C323 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by theMBLBInactivityRSCPThr FCMI parameterand the threshold defined by theBlindHORSCPThr HOPI parameter, the value of counter M1006C325 increases.
Unexpected outcome The state transition to preferred layer has failed. In this case, one of the following counters values are incremented: • •
M1006C324: FAILED LAYER CHANGES IN DCH TO PCH/FACH WITH CM M1006C326: FAILED LAYER CHANGES IN DCH TO PCH/FACH WITHOUT CM
If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to False, the value of counter M1006C324 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by the MBLBInactivityRSCPThr FCMI parameter and below the threshold defined by the BlindHORSCPThr HOPI parameter, the value of counter M1006C324 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is equal to or above the threshold defined by the MBLBInactivityRSCPThr FCMI parameter and the threshold defined by the BlindHORSCPThr HOPI parameter, the value of counter M1006C326 increases. If in the MBLBEnhancementsEnabled parameter parent structure the value of Enhanced inactivity-triggered layering without CM parameter is set to True and the CPICH RSCP of the source cell is below the threshold defined by the MBLBInactivityRSCPThr FCMI parameter, the RRC connection is transferred to Cell_FACH/PCH or URA_PCH state in the current layer and no MBLB counters have been incremented.
3.4.7 3.4.7.1
Deactivating RAN3093: Enhanced MBLB Deactivating Enhanced load balancing Purpose Follow this procedure to deactivate theEnhanced load balancingfunctionality of the RAN3093 Enhanced MBLB feature.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced load balancing parameter to False.
5
3.4.7.2
Select Apply to save the changes.
Deactivating in RRC setupEnhanced layering during voice call setup - Blind IFHO Purpose Follow this procedure to deactivate theEnhanced layering during voice call setup - Blind IFHO in RRC setup functionality of the RAN3093 Enhanced MBLB feature.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO in RRC setup parameter to False.
5
3.4.7.3
Select Apply to save the changes.
Deactivating Enhanced layering for CS voice call from CCH state during voice call setup - Blind IFHO Purpose Follow this procedure to deactivate theEnhanced layering during voice call setup - Blind IFHO for CS voice call from CCH state functionality of the RAN3093: Enhanced MBLB feature.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Blind IFHO for CS voice call from CCH states parameter to False.
5
3.4.7.4
Select Apply to save the changes.
Deactivating the MBLB HSPA load state bypass Purpose Follow this procedure to deactivate the MBLBHSPA load state bypass functionality of the RAN3093: Enhanced MBLB feature.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) Under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Bypass of HSPA load state in case of CS voice call parameter to False.
5
3.4.7.5
Select Apply to save the changes.
Deactivating Enhanced inactivity triggered layering without compressed mode measurements Purpose Follow this procedure to deactivate theEnhanced inactivity triggered layering without compressed mode measurementsfunctionality of the RAN3093: Enhanced MBLB feature.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) For each cell where the Enhanced inactivity triggered layering without compressed mode measurementsis deactivated, under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering without CM parameter to False.
5
3.4.7.6
Select Apply to save the changes.
Deactivating Enhanced mobility triggered layering Purpose Follow this procedure to deactivate theEnhanced mobility triggered layeringfunctionality of the RAN3093: Enhanced MBLB feature.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) For each cell where the Enhanced mobility triggered layeringis deactivated, under theMBLBEnhancementsEnabled parameter parent structure, set the value of theEnhanced mobility triggered layering parameter to False.
5
3.4.7.7
Select Apply to save the changes.
Deactivating Enhanced inactivity triggered layering in state transition to CCH state Purpose Follow this procedure to deactivate theEnhanced inactivity triggered layering in state transition to CCH state functionality of the RAN3093 Enhanced MBLB feature.
Expand the RNC object then expand the WCEL object.
4
Configure the WCEL object. Sub-steps
a) Right-click on the WCEL object and select Edit para meters.
b) For each cell where the Enhanced inactivity triggered layering in state transition to CCH stateis deactivated, under the MBLBEnhancementsEnabled parameter parent structure, set the value of the Enhanced inactivity triggered layering to CCH states parameter to False.
5
Select Apply to save the changes.
3.5 RAN2518: High Speed Cell_FACH Enhanced Introduction to the feature The RAN2518: High Speed Cell_FACH Enhancedfeature increases the share of air interface capacity for the RAN1913: High Speed Cell_FACHfeature, which means that the maximum number of common enhanced dedicated transport channel (E-DCH) resources per cell is increased from 10 to 32 users.
3.5.1
RAN2518 Benefits End-user benefits More users can transfer small and medium-sized packets in a more efficient manner. Operator benefits With this feature, cell capacity and throughput is increased by transferring a bigger share of small and medium-sized data bursts using theRAN1913: High Speed Cell_FACH feature, where High Speed Cell_FACH is the most efficient.
RAN2518 Functional description The RAN2518: High Speed Cell_FACH Enhancedfeature increases the number of uplink common channel resources for smartphone UEs for enhanced dedicated transport channel (E-DCH) transmission in Cell_FACH state. Rel8+ UEs in the uplink use the common E-DCH to transfer the application packets to the network. For transferring small packet data, the common E-DCH is privileged, whereas large application data bursts and uploads need to be transferred through the dedicated E-DCH (HSUPA). Currently, the RAN1913: High Speed Cell_FACHfeature allows to configure the maximum number of simultaneous common E-DCH users up to 10 per cell. With the RAN2518: High Speed Cell_FACH Enhancedfeature this limit is increased from 10 to 32 common E-DCH resources allowing up to 32 active HS-RACH users per cell, however in an inactive state there can be more than 32 HS-RACH users in the cell. The RAN2518: High Speed Cell_FACH Enhancedfeature extends the range of BTS baseband resource allocation per Local Cell Group (LCG), for HS Cell FACH uplink usage. Without the RAN2518: High Speed Cell_FACH Enhancedfeature up to four HSUPA resource steps could be statically allocated for HS Cell FACH. With the RAN2518: High Speed Cell_FACH Enhancedfeature the maximum is increased from four to eight HSUPA Resource Steps. For more information, see High Speed Cell_FACH feature dimensioningin the Dimensioning WCDMA RAN: Flexi BTS Baseband document.
3.5.3
RAN2518 System impact Interdependencies between features The following features must be enabled before activating theRAN2518: High Speed Cell_FACH Enhanced feature: •
RAN1913: High Speed Cell_FACH
•
RAN1686: HSPA 72 Users Per Cell
The RAN2902: RACH Capacity Increasefeature is recommended whenRAN2518: High Speed Cell_FACH Enhancedfeature is configured with increased number of common EDCH resources to fully use the system capacity. Impact on interfaces •
Iub –
•
message NBAP: CAPABILITY INDICATION. NWI3 –
•
DN09203161Issue:02
In the NBAP: PHYSICAL SHAREDCHANNEL RECONFIGURATIONmessage, the Common E-DCH System Information IE carries the configuration for up to 32 instances of the Common E-DCH Resource Combination Information IE. BTS level capability reporting to RNC is indicated by extending the private Iub
The value of the commissioning parameterto configure the number of HSUPA Resource Steps allocated for HS-RACH already exists but its range is increased.
SIB5 and SIB5bis indicate the numberof common E-DCH resources. In SIB5 and SIB5bis, the IE Common E-DCH system info carries the configuration of the common E-DCH resources (the maximum number of signaled resources is 32) which is a multiple instance of IE Common E-DCH Resource Configuration information list.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity There is an improvement in latency for HS-RACH users in the cell because of the increased number of resources. With one UE in the cell the performance is not impacted. Packet loss and latency in both low and high load cells is comparable to the RAN1913: High Speed Cell_FACH feature performance. The RAN2518: High Speed Cell_FACH Enhancedfeature allows for an increase in the overall HS-RACH throughput in a cell. Because of that a greater number of users requiring short data transfers is allocated to HS-RACH. The increase in HS-RACH capacity reduces the number of state transitions of users to CELL DCH leading to a reduction in the number of dedicated resource requests in a cell. The uplink capacity is better utilized by common E-DCH users since the interference created by common E-DCH transmission is quite small in comparison to dedicated EDCH transmission for the same size of data. As a result, the dedicated E-DCH users have better average throughput.
3.5.4
RAN2518 Reference data Requirements Table 24 RAS
WCDMA16
RAN2518 hardware and software requirements I PA - R N C
mc R N C
RNC16
mcRNC16
OMS
NetAct
WCDMA OMS16
NetAct 16.2
MS C
Support not required
Flexi Multiradio BTS
WBTS16
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
WBTS16
Under planning
MGW
Support not required
UE
3GPP Rel-8
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms Table 25
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
RNC LK
Activating RAN2518: High Speed Cell_FACH Enhanced Instructions to activate and configure RAN2518: High Speed Cell_FACH Enhanced using the OMS Element Manager. Purpose Follow this procedure to activate the RAN2518: High Speed Cell_FACH Enhanced feature. Before you start Restart of RNC not required after the activation of this feature. Ensure that RNC SW release is the same as (or newer than) BTS SW release. Ensure BTS has the WBTS16 software release installed. This procedure requires cell locking and causes downtime. Make sure you have access to the following applications: • •
OMS Element Manager Application Launcher
Ensure that RAN2518: High Speed Cell_FACH Enhancedlicense exists. The feature code for this feature is 5577. This feature is controlled by the long-term ON/OFF license key. For more information on licensing, see Licensing.
g
Note: Ensure an appropriate amount of BTS baseband resources has been commissioned for HS Cell FACH uplink. This can be done by changing the commissioning of the numOfHsRachResourceStepsRes parameter, which defines the number of HSUPA resource steps per LCG, allocated for HS RACH users. Each resource step supports up to maximum 10 HS RACH users. For more information, see High Speed Cell_FACH feature dimensioningin the Dimensioning WCDMA RAN: Flexi BTS Basebanddocument. The following features must be enabled before activating of theRAN2518: High Speed Cell_FACH Enhanced feature: • •
DN09203161Issue:02
RAN1913: High Speed Cell FACH RAN1686: HSPA 72 users per cell
Set the RAN2518: High Speed Cell_FACH Enhancedfeature state to ON: •
For IPA-RNC, use the following MML command:
•
For mcRNC, use the following SCLI command:
ZW7M:FEA=5577:ON; set license feature-mgmt code 0000005577 feature-adminstate on
2
Open OMS Element Manager.
3
Go to Topology and expand the ROOT directory.
4
Expand the RNC object and t hen the WCEL object.
5
Lock the cell Sub-steps
a) Select the WCEL object.
b) Right click on the cell and select Administrative State Change ► Lock Cell.
6
Configure the WCEL object. Sub-steps
a) From the drop-down menu select Edit Parameters.
b) Set the the HSRACHCommonEDCHRes parameter to value greater than 10 (up to 32). The HSRACHCommonEDCHRes parameter defines the amount of configured common E-DCH resources of the HS-RACH configuration in the cell.
a) Select the WCEL object b) Right click on the cell and select Administrative State Change ► Unlock Cell.
Result Expected outcome The BTS indicates support of theRAN2518: High Speed Cell_FACH Enhancedfeature by using Private NBAP message: Capability Indication with the IE, BTS Capability Container. The BTS indicates support of theRAN2518: High Speed Cell_FACH Enhancedfeature by using Private NBAP message: Capability Indication with the IE, BTS Capability Container. If the BTS is compatible, then PSCR Req sent by RNC to setup HS-RACH is acked with PSCR complete message by the BTS. Cell is unlocked. Unexpected outcome If BTS is not capable of the RAN2518: High Speed Cell_FACH Enhancedfeature, and RNC configuration of common E-DCH resources is greater than 10, RNC raises alarm 7796. RNC does not initiate HS-RACH setup and waits for an operator to fix the problem.
3.5.6
Verifying RAN2518: High Speed Cell_FACH Enhanced Purpose Follow this procedure to verify that the RAN2518: High Speed Cell_FACH Enhanced feature has been activated successfully. Procedure
1
Open the RNW Measurement Management application. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.
Use the RNW Measurement Management application to start the M1006 measurement. Alternatively the measurement can be started using NetAct Administration of Measurements Application.
3
Wait for the next 60-minute interval to begin. The me asurement interval then starts.
4
Make at least 32 simultaneous connections with Rel-8 UE that supports HSRACH. Use Internet radio application, which utilizes TCP/IP as transport and connect each UE to a low bit rate radio station.
5
Wait until the current 60-minute interval ends and then another 10 minutes. After the measurement collection, it takes additional up to 10 minutes for the measurement data to be transferred to the OMS.
6
Open the RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
7
Check if the following counters have been updated: • • • • • • •
M1006C319 MAX NUMBER OF HS-FACH/HS-RACH USERS PERCELL M5000C460 CONFIGURED HS-RACH SIGNATURES M5000C461 NUMBER OF SUCCESSFULLY ACKNOWLEDGED HS-RACH PREAMBLES M5000C489 AVERAGE COMMON EDCH RESOURCE USAGE M5000C490 MAXIMUM COMMON EDCH RESOURCE USAGE M5000C491 AVAILABLE COMMON E-DCH RESOURCES M5006C72 MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH
Expected outcome As many UEs as defined by the HSRACHCommonEDCHRes WCEL parameter can transmit simultaneously over HS-RACH channel. The following counters are updated successfully: • • •
96
M1006C319 MAX NUMBER OF HS-FACH/HS-RACH USERS PER CELL M5000C460 CONFIGURED HS-RACH SIGNATURES M5000C461 NUMBER OF SUCCESSFULLY ACKNOWLEDGED HS-RACH PREAMBLES
M5000C489 AVERAGE COMMON EDCH RESOURCE USAGE M5000C490 MAXIMUM COMMON EDCH RESOURCE USAGE M5000C491 AVAILABLE COMMON E-DCH RESOURCES M5006C72 MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH
Note: With the RAN2518: High Speed Cell_FACH Enhancedfeature (HS RACH Enhanced) up to 32 simultaneously active HS RACH users per cell is supported, as RNC can send maximum 32 common E-DCH resources configurations per cell.
Deactivating RAN2518: High Speed Cell_FACH Enhanced Purpose Follow this procedure to deactivate theRAN2518: High Speed Cell_FACH Enhanced feature.
set license feature-mgmt code 0000005577 feature-adminstate off
Expected outcome Cell is up and running. Number of common E-DCH resources is reduced to the value defined by the RAN1913: High Speed Cell_FACH feature. Unexpected outcome The 7796 alarm is raised.
3.5.8
Testing RAN2518: High Speed Cell_FACH Enhanced Purpose
g 3.5.8.1
Note: This is an example of the verification. Do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples, and they can vary in different networks.
Testing the RAN2518: High Speed Cell_FACH Enhanced related counters Purpose The purpose of this test case is to verify that the RAN2518: High Speed Cell_FACH Enhanced feature works on BTS and counters related to this feature are correctly collected by BTS Site Manager. This test is performed in the Verifying RAN2518: High Speed Cell_FACH Enhanced chapter of feature activation instruction.
3.5.8.2
Testing the subunits consumption of reserved HSUPA resource steps for HS-RACH users Purpose The purpose of this test case is to verify the subunits consumption of reserved HSUPA resource steps for HS-RACH users. In comparison to theRAN1913: High Speed Cell_FACHfeature 8 instead of 4 HSUPA resource steps can be statically reserved for HS-RACH users. This means that one subunit consumption is visible in the case of Flexi System Module release 3, and two subunits are visible for Flexi System Module release 2. The following counter is checked via BTS Site Manager and RNW Measurement Presentation: •
DN09203161Issue:02
M5008C50 CONFIGURED HS-FACH SUBUNITS IN BTS (The amount of subunits configured for EFACH in uplink in BTS.
PC connected to BTS via LMP port or remotely. BTS Site Manager compatible with BTS SW version. Operational Radio Access Network and Core Network. Both FSMr2 and FSMr3 System Module platform can be used in this testing. Access to RNW Measurement Management.
Preconditions •
•
•
The M5012 FSM Level Monitoring measurement isstarted with RNW Measurement Management application. License for the RAN2518: High Speed Cell_FACH Enhancedfeature is installed on RNC. Maximum number of HSUPA Resource steps for HS-RACH users is commissioned as stated below: –
From HSUPA Settings page in HSUPA resource allocation set Number of HSUP A resource steps reserved for HS-RACH users to8.
Procedure
1
Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.
2
Ensure that BTS i s commissioned according to Preconditions.
3
Perform recommissioning procedure with the below HSUPA resource allocation settings. Figure 4
After a full clock hour wait, an additional 15 minutes and open BTS PM Tab in BTS Site Manager.
5
Open Counters Tab.
6
Select BTS from Objects.
7
Expand WBTS BB su bunits usage from Counters.
8
Select the M5008C50 CONF_HSFACH_SU_WBTS counter.
9
Check the same counter via Application Launcher.
10 Use the RNW Measurement Management application to start the M5008 measurement.
11 Wait for the next 60-minute interval to begin. The measurement interval then starts.
12 Wait until the current 60-minute interval ends and then another 10 minutes.
13 Check if the M5008C50 CONF_HSFACH_SU_WBTS counter has been updated.
Expected outcome For Flexi System Module Rel3: •
1 subunit consumption is visible incomparison to 0.5 for the RAN1913: High Speed Cell_FACH feature (4 resource steps).
For Flexi System Module Rel2: •
2 subunits consumption is visible incomparison to 1 for the RAN1913: High Speed Cell_FACH feature (4 resource steps).
3.6 RAN2869: HSPA Subscriber Increase Introduction to the feature The RAN2869: HSPA Subscriber Increasefeature provides a new set of HSPA subscriber capacity steps which operators can choose based on their own traffic profiles. The current limit introduced by theRAN2124: HSPA 128 Users per Cellfeature is 128 HSPA users per cell. TheRAN2869: HSPA Subscriber Increasefeature adds additional
capacity steps which allow to increase the maximum number of HSPA users per cell up to 208. The operator can purchase a pool size of subscriber capacity licenses for the RNC. The pool of additional 16 HSPA users can be allocated between cells (steps from 1 to 5) based on the subscriber amount that needs to be supported for each cell.
3.6.1
RAN2869 Benefits End-user benefits The RAN2869: HSPA Subscriber Increasefeature increases the maximum number of HSPA users per cell over the 128 in high-speed common channels so that more subscribers can be served at the same time. Operator benefits The feature benefits the operator as follows: •
•
3.6.2
It allows the operatorto define/purchase the neededamount of HSPA user capacity per cell. It introduces a flexible capacity step upgrade capability based on traffic increase, resulting in savings due to smaller and more flexible capacity steps.
RAN2869 Functional description The RAN2869: HSPA Subscriber Increasefeature increases the maximum number of HSPA users per cell over the current limit of 128 by adding additional capacity steps. The size of one step is 16 HSPA users and the number of selected steps can vary from 1 to 5, resulting in increasing the maximum number of HSPA users per cell up to 208, depending on HSPATotIncreaseStep parameter HSPATotIncreaseStep defines the capacity stepssettings. used inThe each cell. When the operator allocates one pool of additional 16 HSPA users to some cell, the system reduces the pool size of subscriber capacity licenses.
g
Note: Note that when the operator changes the 16 HSPA users amount (steps) between the cells, the system reduces the pool size of subscriber capacity licenses. The amount of HSPA users per cell is calculated with the following formula: HSPAtot = HSPA + HSDPA/DCH + HS-FACH/RACH + HS-FACH/HS-RACH The limitation for the number of subscribers per cell is set by the, for example, system performance, supported traffic profile, RL interference evolution. If the operator does not enable the RAN2869: HSPA Subscriber Increasefeature, RNC restricts the HSPA user amount to the number indicated by the existing HSPA (HSDPA) license.
3.6.3
RAN2869 System impact Interdependencies between features The following features need to be activated before activation of the RAN2869: HSPA Subscriber Increase feature: • • •
102
RAN1637: HS Cell_FACH DL RAN1913: HS Cell_FACH UL RAN2124: HSPA 128 Users per Cell
RAN2518: High Speed Cell_FACH Enhanced RAN3104: HSPA User Amount Monitoring
• • • • •
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity when the number of users does not exceed the licensed maximum.
3.6.4
RAN2869 Reference data Requirements Table 32
RAN2869 hardware and software requirements
RAS
I PA - R N C
WCDMA 16
RNC16
mc R N C
mcRNC16
OMS
NetAct
WCDMA OMS16
NetAct 16.2
Fl exi Multiradio BTS
WBTS16
MS C
Flexi Flexi Lite Multiradio 10 BTS BTS
WBTS16
S GSN
Support not required
Support not required
Not planned
MGW
UE
Support not required
Support not required
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF. Alarms There are no alarms related to this feature. Measurements and counters Table 33
New counters introduced by RAN2869 C o u n t e rI D
Before you start After the activation of this feature, there is no need to restart RNC or BTS. Activating procedure does not require cell-locking and does not cause downtime in the network. The RAN2869: HSPA Subscriber Increasefeature is enabled by selecting the appropriate amount of HSPA users by theHSPATotIncreaseStep parameter. The parameter introduces 5 capacity steps, where one step introduces 16 additional HSPA users per cell. When operator pool of additional HSPA users to some cell, the systemthe reduces theallocatesone poolsize of subscriber capacity16 licenses.
g
Note: Note that even when the operator changes the 16 HSPA users amount (steps) between the cells, the system reduces the pool size of subscriber capacity licenses. Before activating the RAN2869: HSPA Subscriber Increasefeature, activate the following features: • • •
RAN1637: HS Cell_FACH DL RAN1913: HS Cell_FACH UL RAN2124: HSPA 128 Users per Cell
The monitoring of HSPAtot is enabled by theRAN3104 HSPA User Amount Monitoring feature. The following features are recommended to be activated/configured before activation of the RAN2869: HSPA Subscriber Increasefeature: • • • • • • • •
The RAN2518: High Speed Cell_FACH Enhancedfeature increases common E-DCH resources from 10 to 32. The RAN2902: RACH capacity increase feature increases the number of RACH signatures from 4 to 16. Activate the license for the RAN2869: HSPA Subscriber Increasefeature. To set the feature state to ON, use the following command: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=5465:ON; set license feature-mgmt code 0000005465 feature-adminstate on
For information on managing licenses, seeLicensing.
Note: The HSPATotIncreaseStep parameter cannot be enabled if the HSPA128UsersPerCell parameter is set toDisabled.
Further information The minimum capacity can be defined for HSPA Cell_DCH state users with the PRFILE parameter 007:0521 HSPA_DCH_MIN_RES with the configuration of the first four bits, counted from right, within 0000 0000 x000 1011. When this minimum reservation is determined, HS-FACH users are not permitted to use this capacity. By default, the minimum reservation, determined with this PRFILE parameter, is not active. There is an additional functionality to activate the pre-emption for HS Cell_FACH users with the PRFILE parameter 007:0521 HSPA_DCH_MIN_RES. The pre-emption is determined with the eighth bit within 0000 0000 1000 xxxx. When the pre-emption is activated and the maximum number of HSPA and HS-FACH users per cell is obtained/surpassed, the HS-FACH users are transferred to Cell_PCH state until the number of users is below the maximum licensed number of users. Target UEs for preemption are chosen on their time of HS-FACH allocation.
3.6.6
Verifying RAN2869: HSPA Subscriber Increase Purpose Follow this procedure to verify if the RAN2869: HSPA Subscriber Increasefeature works properly in the network. Before you start Verify the amount of HSPA users selected by theHSPATotIncreaseStep parameter.
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 SIG NALLING measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
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 Presentationin Managing and viewing RNC measurements.
Unexpected outcome The M1006C317 counter, counting the number of users which are not allocated at the HSPA, HSDPA/DCH, HS-FACH/RACH, and HS-FACH/HS-RACH because of the HSPA maximum licensed user amount restriction, is increased.
g 3.6.7
Note: When the M1006C317 counter is increased, the operator needs to allocate more HSPAtot increase steps with theHSPATotIncreaseStep parameter.
Deactivating RAN2869: HSPA Subscriber Increase Purpose Follow this procedure to deactivate theRAN2869: HSPA Subscriber Increasefeature.
Go to WCEL object by the path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object
4
Determine the value of the HSPATotIncreaseStep parameter to Disabled.
g
Note: After deactivation of the RAN2869: HSPA Subscriber Increasefeature, the amount of HSPA users in the cell is based on the owned license and parameter settings.
3.7 RAN3046: Interference Cancellation for 4Rx Benefits, functionality, system impact, reference data, instructions of the feature The RAN3046: Interference Cancellation for 4Rxfeature enhances theRAN1308: HSUPA Interference Cancellation Receiverand RAN2250: Enhanced HSUPA IC features, which interwork with RAN1269: 4-Way RX Diversity, through extending the parallel interference cancelation (PIC) support up to 4-way radio receiver (Rx) diversity cells. Flexi Multiradio 10 Base Station and above versions support the RAN3046: Interference Cancellation for 4Rxfeature, and up to 12 cells per BTS are supported.
3.7.1
RAN3046 benefits The RAN3046: Interference Cancellation for 4Rxfeature provides the following benefits: • • •
3.7.2
Higher uplink cell throughput Higher uplink user throughput Lower interference from 2-ms TTI UEs
RAN3046 functional description The RAN3046: Interference Cancellation for 4Rxfeature enables interference cancelation (IC) at the base transceiver station (BTS) of up to a maximum of 12 4Rx cells per BTS (for example, 4+4+4 or 2+2+2+2+2+2 site configuration). IC at the BTS reduces the interference caused by a high-speed uplink packet access (HSUPA) 2-ms transmission timing interval (TTI) user. In the earlier implementation, IC is supported for 2Rx only. With theRAN3046: Interference Cancellation for 4Rxfeature, IC is now supported also for 4Rx. IC and 4Rx can be activated together in the same cell for
Flexi System Module Rel3 (FSMr3) (that is, FSMr3, FSMr3+FSMr3) or above releases. For Flexi System Module Rel2 (FSMr2), simultaneous activation of 4Rx and IC remains unsupported. For FSMr3 (master) + FSMr2 (slave) configuration, theRAN3046: Interference Cancellation for 4Rx feature is disabled on both FSMr3 master and FSMr2 slave. If FSMr2 is hot inserted as an extension of FSMr3 that has activated the feature, the cells on that FSMr3 will have the feature disabled. The BTSSM performs the restriction. On the other hand, if FSMr2 is hot removed during runtime, the cells on FSMr3 (which has deactivated the feature) will have the feature enabled if either of the following conditions is met (BTSSM removes the restriction): •
•
RAN1308: HSUPA Interference CancellationReceiver , RAN2250: Enhanced HSUPA IC, and RAN1269: 4-Way RX Diversityare activated for the cell. RAN1308: HSUPA Interference CancellationReceiver and RAN1269: 4-Way RX Diversity are activated for the cell.
With the RAN3046: Interference Cancellation for 4Rxfeature, a mixed configuration is supported in PIC pools, so the cells with 2Rx or 4Rx can be located in same PIC pool. The maximum number of cells supported in one PIC pool is calculated based on the PIC pool capacity and the Rx configuration of the cell. •
•
•
•
Maximum of three cells in a single PIC pool having three cells with4Rx and no cell with 2Rx Maximum of four cells ina single PIC pool having two cells with 4Rx andup to two cells with 2Rx Maximum of five cells in asingle PIC pool having onecell with 4Rx and upto four cells with 2Rx Maximum of six cells in asingle PIC pool having nocell with 4Rx and upto six cells with 2Rx
The RAN3046: Interference Cancellation for 4Rxfeature is supported in Flexi Multiradio 10 Base Station and above versions, and up to 12 cells per BTS are supported. Effect of RAN3046 on cell capacity with HSUPA The RAN3046: Interference Cancellation for 4Rxfeature provides higher cell throughput gain as compared to ePIC+2Rx diversity and 4Rx diversity. The cell throughput is decreased with more users in the cell. However, the cell throughput is expected to be higher than that in the same test environment with ePIC+2Rx or with 4Rx and with the same number of users.
3.7.3
RAN3046 system impact RAN3046: Interference Cancellation for 4Rx impact on features, network management tools, and system performance and capacity Interdependencies between features Any of the following feature combinations must be activated to automatically activate the RAN3046: Interference Cancellation for 4Rxfeature: •
RAN1308: HSUPA Interference CancellationReceiver and RAN1269: 4-Way RX Diversity
Impact on interfaces The RAN3046: Interference Cancellation for 4Rxfeature has no impact on interfaces. Impact on network management tools The RAN3046: Interference Cancellation for 4Rxfeature impacts network management tools as follows: • BTS Site Manager (BTSSM) –
–
–
g
Restriction of PIC+4Rx or ePIC+4Rx onpure FSMr3 or above releases is removed during commissioning or recommissioning. Restriction of PIC+4Rx or ePIC+4Rx onFSMr3 + FSMr2 or pure FSMr2 is performed during commissioning or recommissioning. Cells in one PIC pool can be configured with different Rx streams (thatis, 2Rx or 4Rx).
Note: No separate license is required for this feature. Impact on system performance and capacity The RAN3046: Interference Cancellation for 4Rxfeature impacts system performance and capacity as follows: • •
3.7.4
Better signal quality and higher throughput are achieved. Higher cell throughputcan be obtained in the uplink (UL) direction.
RAN3046 reference data RAN3046: Interference Cancellation for 4Rx requirements, measurements and counters, KPIs, and sales information Requirements Table 39
RAN3046 hardware and software requirements
RAS
I PA - R N C
mc R N C
Flexi Multiradio BTS
Flexi Flexi Lite Multiradio 10 BTS BTS
WCDMA 16
Support not required
Support not required
Not planned
WBTS16 3.0
Support not required
OMS Support not required
NetAct Support not required
MS C Support not required
S GSN Support not required
MGW Support not required
UE Support not required
Alarms There are no alarms related to theRAN3046: Interference Cancellation for 4Rxfeature. Commands
There are no commands related to theRAN3046: Interference Cancellation for 4Rx feature. Measurements and counters Table 40
Existing counters related to RAN3046
C o u n t e rI D
C o u n t e rn a me
M5000C151
HSUPA MINIMUM MAC-D THROUGHPUT
5000 - HSPA in WBTS (WBTS)
M eas u re me n t
M5000C152
HSUPA MAXIMUM MAC-D THROUGHPUT
5000 - HSPA in WBTS (WBTS)
M5000C153
HSUPA AVERAGE MAC-D THROUGHPUT
5000 - HSPA in WBTS (WBTS)
M5000C322
HSUPA MACE PDU DATA WITH 2MS TTI
5000 - HSPA in WBTS (WBTS)
M5000C323
HSUPA MACE PDU DATA WITH 10ms TTI
5000 - HSPA in WBTS (WBTS)
M5000C324
SUM OF HSUPA USERS WITH 2MS TTI
5000 - HSPA in WBTS (WBTS)
M5000C325
SUM OF HSUPA USERS WITH 10MS TTI
5000 - HSPA in WBTS (WBTS)
M5008C49
CONFIGURED PIC SUBUNITS IN BTS
5008 - WBTS level monitoring (WBTS)
M5005C40
PIC INDICATION FOR ACTIVE STATE
5005 - HSPA in WBTS Extension (WBTS)
M5005C41
PIC INDICATION FOR INACTIVE STATE
5005 - HSPA in WBTS Extension (WBTS)
For counter descriptions, seeWBTS and Flexi Performance Measurements. Key performance indicators Table 41
Existing key performance indicators related to RAN3046
KIP DI
KnPaIme
RNC_2050b
Active HSUPA 2ms TTI throughput
RNC_2051b
Active HSUPA 10ms TTI throughput
RNC_1883c
Active HSUPA Cell throughput
RNC_5460a
Average HSUPA user throughput
RNC_5118a
Peak number of HSUPA users in WBTS
RNC_1036b
Average number of simultaneous HSUPA users
For KPI descriptions, see WCDMA RAN Key Performance Indicators. Parameters There are no parameters related to theRAN3046: Interference Cancellation for 4Rx feature. Sales information
Activating RAN3046 Instructions to activate the RAN3046: Interference Cancellation for 4Rx feature Purpose Follow this procedure to activate the RAN3046: Interference Cancellation for 4Rx feature. Before you start •
Licensing No separate license is required for this feature. Hardware requirement FSMr3, FSMr3+FSMr3, and above versions are supported. Software requirement WBTS16 3.0 or WBTS17 is required.
•
To activate the RAN3046: Interference Cancellation for 4Rxfeature, activate any of the following feature combinations: – –
RAN1308: HSUPA Interference CancellationReceiver , RAN2250: Enhanced HSUPA IC, and RAN1269: 4-Way RX Diversityare activated for the cell.
•
FSMr3 or FSMr3+FSMr3 version is used.
Procedure
1
Run a test with each of the following: • •
2
4 HSUPA UEs (4*2 ms TTI or 2*2 ms TTI + 2*10ms TTI), each doing FTP uplink in AWGN/VA30/VA120/PA3 channel model 19 HSUPA 2 ms TTI UEs, each doingFTP uplink in AWGN channel model
Compare the throughput and performance of each test run with ePIC+4Rx (RAN3046: Interference Cancellation for 4Rx -activated) against ePIC+2Rx (RAN2250: Enhanced HSUPA IC-activated) in the same configuration.
Result Expected outcome The uplink throughput of the UE and the cell with ePIC+4RxRAN3046: ( Interference Cancellation for 4Rx-activated) is higher than ePIC+2Rx R ( AN2250: Enhanced HSUPA IC-activated). The KPIs and counters related toRAN3046: Interference Cancellation for 4Rxare improved.
3.7.7
Deactivating RAN3046 Instructions to deactivate the RAN3046: Interference Cancellation for 4Rx feature Purpose Follow this procedure to deactivate theRAN3046: Interference Cancellation for 4Rx feature. Before you start •
The RAN3046: Interference Cancellation for 4Rxfeature is activated.
•
To deactivate the RAN3046: Interference Cancellation for 4Rxfeature, deactivate any of the following features: – –
Note: See the feature activation instructions of each of the listed features for deactivation procedures. Result Expected outcome The RAN3046: Interference Cancellation for 4Rxfeature is automatically deactivated.
3.8 RAN3040: IRC Receiver Introduction to the feature This feature introduces the Interference Rejection Combining (IRC) mechanism which provides protection for the R99 UL and HSUPA end users against the interference. The IRC mechanism at base station removes dominant interference from an uplink signal before demodulation and before probable further reduction of interference.
3.8.1
RAN3040 Benefits End-user benefits This feature provides higher end-user throughput within the uplink. Operator benefits This feature provides the IRC mechanism which makes the interference within the uplink decreased to offer improved signal quality, higher end-user and cell throughput and consequently provides more capacity within the uplink. Moreover, the IRC mechanism permits to maintain the cell coverage at the moment of interference.
3.8.2
RAN3040 Functional description The RAN3040: IRC Receiver feature introduces the Interference Rejection Combining (IRC) mechanism which provides protection for the R99 UL and HSUPA end users against the interference. The IRC mechanism at base station removes dominant interference from an uplink signal before demodulation and before probable further reduction of interference. The interference within the uplink is decreased then to offer improved signal quality, higher UE throughput and consequently more capacity within the uplink. Moreover, the IRC mechanism also permits to maintain the cell coverage at the moment of interference. The IRC mechanism protects against intra-cell, inter-cell, and external interference notably when there are not many dominant interferers. The IRC mechanism can remove approximately N-1 dominant interferers where N is the number of antennas per one cell. Note that the IRC mechanism can remove a certain part of dominant interference even when the number of dominant interferers is greater than N-1. The IRC mechanism is based on combining the antenna signals from more than one antenna and estimating the covariance of interference between the antennas, aiming to whitening the interference. Note the difference with the Interference Cancellation (IC) mechanism. The IC mechanism, contrary to IRC mechanism, is based on removing demodulated signals of interferers from the other signals. When compared to Maximum Ratio Combining (MRC) mechanism which maximizes the SNR for white noise, the IRC mechanism provides greater SINR than MRC mechanism after combining. The IRC
mechanism removes dominant interference with proper phasing and weighting of the antenna signals to be combined. The IRC mechanism is an alternative to the MRC mechanism at the receiver chain when summarizing the comparison with the MRC mechanism. This feature can operate with and without the features which provide the IC mechanism. When the feature works without the IC mechanism, the IRC mechanism decreases dominant interference independent on whether the interference srcinates from the enduser at the same cell, surrounding cells and external sources. When the feature is activated together with the IC mechanism, the IC mechanism provides the most efficient protection against own cell interference, whereas the IRC mechanism protects against dominant interference from the sources which are not managed with the IC mechanism.
3.8.3
RAN3040 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •
•
3.8.4
The IRC mechanism provides morecombining gain than the MRC mechanism which means improved signal quality, higher end-user and cell throughput and consequently more capacity within the uplink. Moreover, the IRC mechanism also permits to maintain the cell coverage at the moment of interference. The IRC mechanism alternates theMRC mechanism at the receiver chain and protects against the type of interference which is not managed with the IC mechanism.
RAN3040 Reference data Requirements Table 43
RAN3040 hardware and software requirements
RAS
I PA - R N C
mc R N C
WCDMA 16
Support not required
Support not required
OMS
NetAct
Support not required
NetAct 16.2
MSC
Support not required
Fl exi Multiradio BTS
WBTS16
SGSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
WBTS16
MGW
Support not required
Under planning
UE
Support not required
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 44
New faults introduced by RAN3040
F au l tI D
F a u l tn a m e
4248
R e p o r t e da l ar m s
IRC Receiver not available for pure single RX BTS configuration
7652 BASE STATION NOTIFICATION
Measurements and counters Table 45
New counters introduced by RAN3040
C o u n t e rI D
C o u n t e rn a m e
Me as u re me n t
M5005C55
SUM OF IRC PROCESSED USERS
M5005C56
SUM OF ALL USERS
M5005C57
ALL AND IRC USERS DENOMINATOR
HSPA in WBTS Extension HSPA in WBTS Extension HSPA in WBTS Extension
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 46
New parameters introduced by RAN3040 F u l ln am e
A b b r e v i a t e dn a me
IRC receiver enabled
ircReceiverEnabled
M an a g e do b j e c t
BTSSCW
Commands There are no commands related to this feature. Sales information Table 47
RAN3040 Sales information
B S W /A S W
ASW
3.8.5
S W c o mp o n e n t
RAN
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
BTS LK
Activating 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: •
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.
3.8.6
Verifying RAN3040: IRC Receiver Purpose Follow this procedure to verify if the RAN3040: IRC Receiver feature works properly in the network. Before you start Make sure you have access to the following applications: • •
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, seeStarting radio network measurementsin Managing and viewing RNC measurements.
3
Set up one AMR, R99, or HSUPA call.
4
Run the measurement for one full hour.
5
Open the RNW Me asurement Presentation application and check values of the M5005C55 and M5005C56 counters. For details on checking the counter values in the RNW Measurement Presentation application, seeViewing and modifying radio network measurement parametersin Managing and viewing RNC measurements.
Expected outcome The M5005C55 and M5005C56 counter values are changed from0 to approximately 36000.
3.8.7
Deactivating RAN3040: IRC Receiver Purpose Follow this procedure to deactivate this feature. Before you start Make sure you have access to the following applications: •
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.8.8
Testing RAN3040: IRC Receiver Purpose
g
Note: This is an example of the verification; do not use it for the feature as such in live network. The configuration and parameter settings described are only examples and they can vary in different networks. The purpose of this test case is to verify that the RAN3040: IRC Receiver feature is working on BTS and that the counters related to this feature are correctly collected and fetched by the BTS Site Manager. The following counters are to be checked: • M5005C55 SUM OF IRC PROCESSED USERS Sum of IRC processed users in a cell, obtained by sampling with predefined sampling period the current number of IRC processed users in a cell, and summing all the samples together. •
Sum of all users in a cell, obtained by sampling with predefined sampling period the current number HSUPA and R99 users in a cell, and summing all the samples together. M5005C57 ALL AND IRC USERS DENOMINATOR Number of samples taken to calculate M5005C55 and M5005C56
Test environment: •
PC connected to BTS via LMP port or remotely
• •
BTS Site Manager compatible with BTS SW version Operational Radio Access Network and Core Network FSMr2 or FSMr3 System Module platform Access to RNW Measure Management
• •
Before you start Preconditions: • • •
•
M5005 HSPA in WBTS Extension measurement is started. BTS is working and has been 'On Air' for more than one full clock hour. Valid license for the RAN3040: IRC Receiver feature (feature code: 5428) is installed on the BTS. The RAN3040: IRC Receiver feature is enabled on the BTS (seeActivating RAN3040: IRC Receiver).
Procedure 1
Within one full clock hour make several AMR and HSUPA calls via tested BTS.
2
After furher 15 minutes (after the full clock hour finishes), in the BTS Site Manager, go to BTS PM tab on the left-hand side.
3
In the BTS PM tab, open 'Counters' tab.
4
From ‘Objects’ select Local cell which has been used in test.
5
From ‘Counters’ expand ‘HSPA in WBTS E xtension’ and go to ‘Cell IRC users amount’ tab.
6
Check the values of the three IRC-related counters: M5005C55, M5005C56, M5005C57.
Result Three IRC-related counters are visible: M5005C55, M5005C56, M5005C57.
The value of the counter M5005C55 is greater than 0 and the CPU load on BTS equals M5005C56. The value of the counter M5005C57 should be around 36000.
g
Note: Samples of counters M5005C55, M5005C56, M5005C57 are collected every 100 ms.
3.9 RAN3235: Optimized Packet Handling at RNC Introduction to the feature
The RAN3235: Optimized Packet Handling at RNCfeature introduces the Active Queue Management (AQM) mechanism to improve packet handling at RNC for DL data transmission from CN. The feature pertains to the HSPA data transmission. The mechanism provides that even with the most demanding TCP configurations, packet drops are controlled while ensuring fairness among the traffic flows. The optional mechanism of the HTTP incubation is introduced to ensure that, in specific cases, the performance of the HTTP data transmission is not compromised at the congestion moment.
3.9.1
RAN3235 Benefits End-user benefits The RAN3235: Optimized Packet Handling at RNCfeature provides that even with the most demanding TCP configurations, packet drops are controlled while ensuring fairness among the traffic flows. It also provides decreased amount of dropped DL HSPA packets within RNC PDCP, improved faireness of traffic among competing TCP flows, and, optionally, in specific cases, incubation of HTTP traffic during congestion. Operator benefits This feature optimizes the operator network to manage the TCP and UDP configuration demands within modern portable communication units and consequently, the TCP and UDP end-to-end performance is improved with stable throughput, fairness among the traffic flows, and decreased amount of dropped DL HSPA packets within the RNC PDCP. In specific cases, the performance of the HTTP data transmission is not compromised at the congestion moment within the RNC PDCP.
3.9.2
RAN3235 Functional description The modern communication units have demanding TCP and UDP configurations where greater amount of data is transmitted from CN to RNC and consequently, increased buffer at RNC or advanced queue management are needed to prevent degradation of TCP/UDP performance. The RAN3235: Optimized Packet Handling at RNCfeature introduces the Active Queue Management mechanism to improve TCP and UDP packet managing at RNC for DL data transmission from CN. The feature pertains to the HSPA data transmission. The mechanism optimizes the operator network to manage the TCP and UDP configuration demands within modern portable communication units and consequently the TCP and UDP end-to-end performance is improved with stable throughput, improved faireness of traffic among competing TCP flows, and decreased amount of dropped DL HSPA packets within the RNC PDCP. The Active Que Management mechanism at PDCP
provides high link utilization without introducing undue delays within the end-to-end path through the active monitoring of buffer fill state and performing preventive actions before the queue fills up and incoming HSPA packets are dropped. The mechanism appends a timestamp to each of the incoming HSPA packets and then performs a comparison between the age of the oldest packet and the threshold determined through the percentage of tunable time. Once the oldest packet is older than determined threshold, a probability is computed for each of the incoming HSPA packets. Once the sum of probability computed for incoming HSPA packets is greater than determined threshold, the latest packet is dropped and the computation is started again. This feature optionally introduces the HTTP incubation mechanism ensuring that the HTTP performance is not compromised at the congestion moment during the Active Queue Management mechanism activity within the RNC PDCP. When the Active Queue Management mechanism is enabled without the HTTP incubation mechanism, the HTTP data is not incubated at the congestion moment during the Active Queue Management mechanism activity and the TCP/UDP and HTTP data is dropped. When the Active Queue Management mechanism is enabled with the HTTP incubation mechanism, the HTTP data is incubated at the congestion moment during the Active Queue Management mechanism activity and the HTTP data is not dropped when HTTP is not the dominant traffic. Note that the recommended option is to activate the feature with the mechanisms for AQM only. The dimension of PDCP buffer is retained at optimum value of 1MB size and aligned with the Active Que Management(AQM) algorithm .
g 3.9.3
Note: Single stream FTP download might occasionally face deviations in Download time observations towards the negative side, because of the lower stabilized throughput achieved due to AQM packet drops.
RAN3235 System impact Interdependencies between features This feature has a functional dependency with theRAN2510: In-Bearer Application Optimization feature. When the Active Queue Management mechanism works with the In-Bearer Application Optimization mechanism, the Active Queue Management mechanism performs actions preventing the queue fills up starting with the packet of low priority. When the low priority data is not present, the high priority data is dropped based on the Active Queue Management mechanism through the probability computation. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: •
122
The operator network performance isoptimized to managethe TCP configuration demands within modern portable communication units making the TCP end-to-end performance improved with stable throughput, fairness among the traffic flows, and decreased amount of dropped DL HSPA packets within the RNC PDCP.
The goodput performance is muchmore stable and fairness is improved among different traffic flows for the UE. In specific cases, theperformance of the HTTP data transmission is not compromised at the congestion moment within the RNC PDPC.
RAN3235 Reference data Requirements Table 48
RAN3235 hardware and software requirements
RAS
I PA - R N C
WCDMA 16
RNC16
mc R N C
Fl exi Multiradio BTS
mcRNC16
OMS
NetAct
WCDMA OMS16
NetAct 16.2
Support not required
MS C
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required
S GSN
Support not required
Support not required
MGW
Support not required
UE
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 Table 49
Existing counters related to RAN3235
C o u n t e rI D
C o u n t e rn a m e
M1022C241
RLC DL SDU BYTES DROPPED
Me as u re me n t
Packet Call
Key performance indicators There are no key performance indicators related to this feature. Parameters Table 50
New parameters introduced by RAN3235 F u l ln a me
A b b r e v i a t e dn a me
M a n a g e do b j e c t
Optimized TCP Packet Handling at RNC Enabled
TCPOptimizeEnabled
RNFC
AQM Delay Threshold Time
AQMDelayThresholdTime
RNHSPA
Table 51
Parameters modified by RAN3235 F u l ln a me
RNC Options
A b b r e v i a t e dn a me RncOptions
M a n a g e do b j e c t
RNC
Commands There are no commands related to this feature. Sales information
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
RNC LK
Activating RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to activate the RAN3235: Optimized Packet Handling at RNC feature in RNC. Before you start This activating procedure does not require cell locking. After the activation of this feature, there is no need to restart RNC or BTS. Install the license for the RAN3235: Optimized Packet Handling at RNCfeature and set the feature state to ON using the following command: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=5598:ON; set license feature-mgmt code 0000005598 feature-adminstate on
Procedure
1
Open OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Configure the RNFC object: Sub-steps
a) Go to the RNFC object using the following path: RNC object ► RNFCs folder ► RNFC object.
b) Right-click the RNFC object and select Edit parameters.
c) On the Packet Scheduler tab, set the value of the TCPOptimizeEnabled parameter to: •
124
AQM RED Enabled , for activating the AQM RED mechanism at RNC PDCP. When only the Active Queue Management Random Early Detection (AQM RED) mechanism is activated, both the TCP/UDP and the HTTP packets are dropped during congestion or overflow scenarios.
Note: AQM RED Enabled is the recommended value of the TCPOptimizeEnabled parameter. •
AQM RED Enabled + HTTP Incubation Enabled, for activating both the AQM RED and the HTTP incubation mechanisms at RNC PDCP. When both the AQM RED and the HTTP incubation mechanisms are active, during congestion or overflow scenarios the TCP/UDP packets are dropped and the HTTP packets are incubated (not dropped) in specific scenarios.
d) Click Apply to save the changes.
g 3.9.6
Note: After activating, the RAN3235: Optimized Packet Handling at RNCfeature is applied only to new RRC Connections. Ongoing connections are not affected.
Verifying RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to verify if the RAN3235: Optimized Packet Handling at RNC feature works properly in the network. Before you start Make sure that theRAN3235: Optimized Packet Handling at RNCfeature is activated with the RNFC- TCPOptimizeEnabled parameter valueAQM RED Enabled . Make sure you have access to the following applications: • • •
OMS Element Manager RNW Measurement Management RNW Measurement Presentation
Procedure
1
Set the value of the RNHSPA - AQMDelayThresholdTime parameter to 20 ms.
2
Open the RNW Measurement Management application.
3
Start the M1022 Packet Call measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and Viewing RNC Measurements.
Initiate data transfers with 2 applications (for example HTTP and FTP) in a single UE for producing high traffic load to have congestion.
5
Open the RNW Measurement Presentation application.
6
Check the value of the counter M1022C241: RLC DL SDU BYTES DROPPED. Under congestion conditions, the value of counter M1022C241 is expected to be lower when the RAN3235: Optimized Packet Handling at RNCfeature is activated than when the feature is not activated. Before comparing the measurement results, ensure that the similar load conditions and measurement period were applied to both cases. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome Packets drop is expected to be reduced at RNC PDCP. The drop reduction can be verified with the counter M1022C241. Troubleshooting actions If the packet drop is not reduced, increase the RNHSPAAQMDelayThresholdTime parameter value by 10 ms and repeat the verifying procedure.
g 3.9.7
Note: Optionally, to configure the PDCP buffer size to 2MB, contact your local customer support.
Deactivating RAN3235: Optimized Packet Handling at RNC Purpose Follow this procedure to deactivate theRAN3235: Optimized Packet Handling at RNC feature in RNC.
a) Go to the RNFC object using the following path: RNC object ► RNFCs folder ► RNFC object.
b) Right-click the RNFC object and select Edit parameters.
c) On the Packet Scheduler tab, set the value of the TCPOptimizeEnabled parameter to Disabled.
d) Click Apply to save the changes.
g
Note: After deactivating, the RAN3235: Optimized Packet Handling at RNCfeature is still applied to ongoing connections. Only the new RRC connections are not affected by this feature.
3.10 RAN2902: RACH Capacity Increase Introduction to the feature With the RAN2902: RACH Capacity Increase feature, the maximum number of RACH preamble signatures per cell is increased from 4 to 16.
3.10.1
RAN2902 Benefits End-user benefits This feature provides the end user with faster network access, especially in the highloaded cells. Operator benefits This feature decreases uplink interference thanks to fewer signature collisions and fewer RACH cycles needed. Having more RACH preamble signatures available also improves the performance of theRAN1913: High Speed Cell_FACHand the RAN2518: High Speed Cell_FACH Enhancedfeatures.
RAN2902 Functional description The RAN2902: RACH Capacity Increasefeature increases the number of RACH preamble signatures available in a cell from 4 to 16. Increased number of signatures decreases the probability of collision during the physical RACH procedure. In consequence, RACH procedure needs fewer repetitions and the network access is faster. Additionally, the interference in the uplink is decreased. Increasing the number of RACH preamble signatures is especially beneficial when the RAN1913: High Speed Cell_FACHfeature is in use, and even more beneficial with the RAN2518: High Speed Cell_FACH Enhancedfeature on top of it. The number of subscribers with the HS-Cell_FACH-capable UEs is growing. Using the High Speed Cell_FACH results in significant capacity gain: higher number of users can be served in a cell and/or higher volume of user data can be transferred in a cell (on account of reduced signaling). However, in the current system implementation there is only one preamble signature available for HS RACH. With the RAN2902: RACH Capacity Increase and the RAN1913: High Speed Cell_FACHfeatures activated, the operator can enable up to 12 preamble signatures for HS RACH. The number of RACH preamble signatures can also be increased with the RAN2902: RACH Capacity Increase feature. Operator can allocate up to 8 RACH signatures and up to 12 HS RACH signatures (but no more than 16 signatures in total). Allocating preamble signatures is managed with the RACHPreambleSignatures WCEL parameter. Modification of this parameter requires cell locking and unlocking. Table 53
Available preamble signature combinations RAN1913 deactivated
RAN1913 activated
RACHPreambleSignatures Number of RACH Number of RACH parameter value preamble preamble signatures signatures
RACH 1 signature
1
RACH 2 signatures
2
2
1
RACH 3 signatures
3
3
1
RACH 4 signatures
4
3+3 RACH and HS RACH signatures
1
3 N/A
RACH 8 signatures
g
1
Number of HS RACH preamble signatures
8
1 3
3
7
1
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
Note: To enable HS RACH allocation, theRAN1913: High Speed Cell_FACHfeature has to be activated in the cell. RACH or HS RACH peak throughputs are not increased by this feature, however the average utilization of RACH/HS RACH can improve.
The preamble signatures are signaled to BTS over NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST (HS-RACH) and NBAP: COMMON TRANSPORT CHANNEL SETUP REQUEST (RACH) messages. Total amount of signatures is indicated to BTS by NBAP: CONFIGURATION DATA (Private NBAP message). BTS indicates its capability for using the RAN2902: RACH Capacity Increase feature in the NBAP: CAPABILITY INDICATION (Private NBAP message). The operator can check if BTS is capable of using the RAN2902: RACH Capacity Increase feature by looking up the value of theBTSRACHCapaIncCapability WBTS parameter. The signatures in use are broadcast to UE in SIB5/SIB5bis. For more information, see 3GPP TS 25.433 UTRAN Iub interface Node B Application Part (NBAP) signalling .
g
Note: Certain configurations of: • • • •
Cell range ( cellRange WCEL parameter) Number of cells in Local Cell Group Number of signatures in BTS ( RACHPreambleSignatures WCEL parameter) Rx diversity
impact the Baseband available capacity since more resources for Common Control Channels (CCCH) processing is needed. For more information, see Common Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband .
3.10.3
RAN2902 System impact Interdependencies between features This feature improves performance of the following features: • RAN1913: High Speed Cell_FACH • RAN2518: High Speed Cell_FACH Enhanced Impact on interfaces This feature reduces interference on the Uu interface in the uplink direction. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity Certain configurations of:
•
Cell range ( cellRange WCEL parameter) Number of cells in Local Cell Group Number of signatures in BTS ( RACHPreambleSignatures WCEL parameter)
•
Rx diversity
• •
impact the Baseband available capacity since more resources for Common Control Channels (CCCH) processing is needed. For more information, seeCommon Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband .
Before you start Activating procedure requires cell locking. After the activation of this feature, there is no need to restart RNC or BTS. Activate the license for the RAN2902: RACH Capacity Increasefeature using RACH capacity increase license key. To set the feature state to ON, use the following command: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=5449:ON; set license feature-mgmt code 0000005449 feature-adminstate on
Procedure
1
Open OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
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, set the RACHPreambleSignatures parameter to the desired value.
g
Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing. To enable HS RACH allocation, theRAN1913: High Speed Cell_FACHfeature has to be activated in the cell.
Unexpected outcome The cell cannot be unlocked. Troubleshooting actions If you have assigned HS RACH preamble signatures by setting the RACHPreambleSignatures parameter to one of the following values:
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
• •
Radio resource management features
ensure that theRAN1913: High Speed Cell_FACHfeature is activated in the cell and the RAN2902: RACH Capacity Increase feature state is ON. If you have assigned 8 RACH signatures by setting the value of the RACHPreambleSignatures parameter 8 RACH signatures, ensure that the RAN2902: RACH Capacity Increase featuretostate is ON.
Ensure that the BTS is capable of using the RAN2902: RACH Capacity Increase by checking the value of theBTSRACHCapaIncCapability WBTS parameter. Further information If alarm 3325: INCONSISTENCY IN CONFIGURATION PARAMETERS or 7775: INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS was raised, ensure that the defined number of signatures, cell Rx diversity, and cell range form a compatible configuration. In case of incompatible configuration, system sets the cell up with the default number of signatures (4 signatures) and the default cell range (20 km). For more information, seeCommon Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband.
3.10.6
Verifying RAN2902: RACH Capacity Increase Purpose Follow this procedure to verify if the RAN2902: RACH Capacity Increasefeature works properly in the network. Before you start Make sure you have access to the following applications: • •
Start the M5000 HSPA in WB TS measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome The values of counters M5000C455 and M5000C460 match the number of RACH and HS RACH signatures configured using theRACHPreambleSignatures parameter. Unexpected outcome The values of counters M5000C455 and M5000C460 do not match the number of RACH and HS RACH signatures configured using theRACHPreambleSignatures parameter. Troubleshooting actions Ensure that theRAN1913: High Speed Cell_FACHfeature is activated in the cell if you assigend any HS RACH signatures. Ensure that the BTS is capable of using theRAN2902: RACH Capacity Increase feature by checking the value of theBTSRACHCapaIncCapability WBTS parameter. If alarm 3325: INCONSISTENCY IN CONFIGURATION PARAMETERS or 7775: INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS was raised, ensure that the defined number of signatures, cell Rx diversity, and cell range form a compatible configuration. In case of incompatible configuration, system sets the cell up with the default number of signatures (4 signatures) and the wcdmadefault cell range (20 km). For more information, seeCommon Control Channels dimensioningin Dimensioning WCDMA RAN: Flexi BTS Baseband .
3.10.7
Deactivating RAN2902: RACH Capacity Increase Purpose Follow this procedure to deactivate theRAN2902: RACH Capacity Increasefeature. Before you start Deactivating procedure requires cell locking.
a) Go to the WCEL object using the following path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object
b) Right-click on the WCEL object and select Edit parameters.
c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 1, 2, 3, or 4 RACH signatures.
g
4
Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing.
Set the feature state to OFF. Use the following commands: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=5449:OFF; set license feature-mgmt code 0000005449 feature-adminstate off
Unexpected outcome The cell cannot be unlocked. Troubleshooting actions When the cell cannot be unlocked make sure that you have assigned no more than four RACH signatures and none of the HS RACH signatures.
3.10.8
Testing RAN2902: RACH Capacity Increase Purpose
g
DN09203161Issue:02
Note: It is strongly recommended to test this feature in a live network to observe network performance improvement.
Before you start Testing procedure requires cell locking. There is no need to restart RNC or BTS. Procedure
1
Open OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Deactivate t he RAN1913: High Speed Cell_FACHfeature using the HSRACHEnabled WCEL parameter. For detailed instructions, seeDeactivating RAN1913: High Speed Cell_FACH .
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.
c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 4 RACH signatures.
g
Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing.
5
Open the RNW Measurement Management application.
6
Start the M5000 HSPA in WB TS measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
7
Wait until t he next full hour plus 10 mi nutes. For example, if you start the measurements at 11:22, the collected data is available in OMS at 12:10.
Open the RNW Measurement Presentation application.
9
Check the values of all counters in the range M5000C455–C476 Expected outcome •
The value of the M5000C455 counter is 4.
•
The value of the M5000C460 counter is 0. Values of counters in the range M5000C461–C464are 0. Values of counters in the range M5000C471–C476are 0.
• •
10 In OMS Element Manager, reconfigure the WCEL object: Sub-steps
a) Go to the WCEL object using the following path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object
b) Right-click on the WCEL object and select Edit parameters.
c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 8 RACH signatures.
g
Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing.
11 In the RNW Measurement Management application, start the M5000 HSPA in WBTS measurement. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
12 Wait until the next full hour plus 10 minutes. For example, if you start the measurements at 12:22, the collected data is available in OMS at 13:10.
13 In the the RNW Measurement Presentation application, check the values of all counters in the range M5000C455–C476 Expected outcome
The value of the M5000C455 counter is 8. The value of the M5000C460 counter is 0. Values of counters in the range of M5000C461–C464 are 0. Values of counters in the range of M5000C471–C476 are 0. Values of counters M5000C456and M5000C458 are higher in comparision to results from step 8. Values counters results of from step 8.M5000C457and M5000C459 are lower in comparision to
Further information Counters M5000C465–C470 represent the percentage of R99 RACH signatures utilization. The higher utilization class, the higher load for R99 RACH signatures. Enabling more signatures for use should be reflected by lower R99 RACH signatures utilization and, consequently, a decrease of utilization class.
g
Note: These predictions are based on the assumption that traffic load in the cell is constant.
14 Activate t he RAN1913: High Speed Cell_FACHfeature using the HSRACHEnabled WCEL parameter. For detailed instructions, seeActivating RAN1913: High Speed Cell_FACH .
15 In OMS Element Manager, 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.
c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 4+4 RACH and HS RACH signatures.
g
138
Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing.
16 In the RNW Measurement Management application, start the M5000 HSPA in WBTS measurement.
17 Wait until the next full hour plus 10 minutes. For example, if you start the measurements at 13:22, the collected data is available in OMS at 14:10.
18 In the the RNW Measurement Presentation application, check the values of all counters in the range M5000C455–C476 Expected outcome • • • •
g
The value of the M5000C455 counter is 4. The value of the M5000C460 counter is 4. Values of counters in the range M5000C461–C464 are different than 0. Values of counters in the range M5000C471–C476 are different than 0. Note: These predictions are based on the assumption that UEs with HS RACH support are present in the cell.
19 In OMS Element Manager, 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.
c) On the System Info tab, set the value of the RACHPreambleSignatures parameter to 4+12 RACH and HS RACH signatures.
g
Note: The cell is automatically locked when you edit the RACHPreambleSignatures parameter, and is unlocked when you finish editing.
20 In the RNW Measurement Management application, start the M5000 HSPA in WBTS measurement.
21 Wait until the next full hour plus 10 minutes. For example, if you start the measurements at 14:22, the collected data is available in OMS at 15:10.
22 In the the RNW Measurement Presentation application, check the values of all counters in the range of M5000C455–C476. Expected outcome • • • • • •
The value of the M5000C455 counter is 4. The value of the M5000C460 counter is 12. Values of counters in the range of M5000C456–C459 aresimilar to results from step 16. Values of counters in the range of M5000C465–C470 aresimilar to results from step 16. Values of counters M5000C461and M5000C463 are higher in comparision to results from step 16. Values of counters M5000C462and M5000C464 are lower in comparision to results from step 16.
Further information Counters M5000C465–C470 represent the percentage of R99 RACH signatures utilization. The higher utilization class, the higher load for R99 RACH signatures. Enabling more signatures for use should be reflected by lower R99 RACH signatures utilization and, consequently, a decrease of utilization class.
g
Note: These predictions are based on the assumption that in the cell the traffic load is constant and UEs with HS RACH support are present.
3.11 RAN2892: WCDMA-LTE Load Balancing Introduction to the feature With RAN2892: WCDMA-LTE Load Balancing feature, all traffic steering actions towards high-loaded LTE cells are suspended.
3.11.1
RAN2892 Benefits End-user benefits Blocking of redirections and handovers to high-loaded LTE cells improves the end-user experience. Operator benefits Load balancing between WCDMA and LTE is needed when LTE network starts to get high-loaded. Preventing the redirection and handover attempts to high-loaded LTE cells reduces the need for further redirections and handovers.
Note: This feature is beneficial only in the following cases: •
In the operator's network the LTE1357: LTE-UTRAN load balancingfeature (or other feature supporting the 'Reduce Load in Serving Cell' cause value in RANAP: RELOCATION REQUEST message) and at least one of the following WCDMA RAN features are enabled: – – –
In the operator's network the LTE57: Inter RAT handover from UTRANfeature (or other feature supporting the 'No Radio Resources Available in Target cell' cause value in RANAP: RELOCATION PREPARATION FAILURE message) and the RAN2264: Smart LTE Handoverfeature are enabled.
RAN2892 Functional description The RAN2892: WCDMA-LTE Load Balancingfeature prevents redirections and handovers from WCDMA layer to high-loaded LTE cells. WCDMA to LTE traffic steering is enabled by the following features:
When high load of LTE cell is identified, redirections and handovers from WCDMA to this LTE cell are stopped and a penalty timer for that cell is started. After the penalty timer expires, RNC returns to the normal traffic steering. The penalty timer is operator-tunable and controlled with thePenaltyTimerLTELoadHo RNMOBI parameter. High load in LTE cells is identified when: •
g
Note: Sending the RANAP message with the 'Reduce Load in Serving Cell' cause value in case of LTE to WCDMA handover is provided by the LTE1357: LTE-UTRAN load balancingfeature. •
g
LTE eNodeB initiates handover toWCDMA due to load reasons and the target RNC receives RANAP: RELOCATION REQUEST with the 'Reduce Load in Serving Cell' cause. This is indicated by the non-zero value of theRANAPCause1LTELoadInHo and/or the RANAPCause2LTELoadInHo RNMOBI parameter.
WCDMA initiates handover to LTE cell which experiences high load andeNodeB rejects the handover due to load reasons. Source RNC receives RANAP: RELOCATION PREPARATION FAILURE message with the 'No Radio Resources Available in Target cell' cause. This is indicated by the non-zero value of the RANAPCause1LTELoadOutHo and/or the RANAPCause2LTELoadInHo RNMOBI parameter. Note: Sending the RANAP message with 'No Radio Resources Available in Target cell' cause value in case of WCDMA to LTE handover rejection is provided by the LTE57: Inter RAT handover from UTRANfeature.
If the RNC receives another high-load indication from the LTE cell before the penalty timer has expired, the penalty timer is restarted for that cell.
When redirection from WCDMA to LTE is initiated, the under-penalty LTE cells belonging to the LTE frequency layers selected for redirection are signaled to UE in the RRC CONNECTION RELEASE message asblacklisted cells. While attempting to switch to the suitable LTE cell, UE does not consider any of the under-penalty cells. The source RRM Handover Control entity informs all the other RRM Handover Control entities in the RNC about the under-penalty LTE cells.
Overview of the RAN2892: WCDMA-LTE Load Balancing feature in Nokiabased radio network. RAN2176: LTE PS Handoveractivated + RAN2892: Dynamic WCDMA-LTE Load Balancing activated
LTE57: Inter RAT handover from UTRAN activated + WCDMA to LTE handover failure due to high load of LTE cell
AND/OR
LTE1357: LTEUTRAN load balancing activated + LTE to WCDMA handover request due to high load of LTE cell
Cell ID
Cell ID
LTE cell overload indication
Penalty timer start (or restart if already running) for high-loaded LTE cells
Handover from WCDMA to LTE RAN2264: ( Smart LTE Handover) is not initiated if target LTE cellis under penalty due to high load. Redirection from WCDMA to LTE RAN2717: ( Smart LTE Layering, RAN2980: Measurement BasedLTE Layering) is prevented if all qualified neighboring LTE cells on all target frequencies are under penalty duetotoLTE highsystem load . Otherwise, UEs commanded to redirect receive a list of the neighboring under-penalty LTE cells belonging to the target LTE frequency as a blacklist.
g
DN09203161Issue:02
Note: Some early Rel-8 UEs have problems during e-UTRA Compressed Mode measurements. For more information on this issue, seeTechnical Support Note 149, section 5.20, available inProduct Information Center.
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 balancingfeature (or other feature supporting the 'Reduce Load in Serving Cell' cause value in RANAP: RELOCATION REQUEST message) and at least one of the following WCDMA RAN features are enabled: – – –
In the operator's network the LTE57: Inter RAT handover from UTRANfeature (or other feature supporting the 'No Radio Resources Available in Target cell' cause value in RANAP: RELOCATION PREPARATION FAILURE message) and the RAN2264: Smart LTE Handoverfeature are enabled.
Impact on interfaces This feature impacts Iu interface. Reduced number of redirections and handovers results in reduced signaling load. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature prevents the redirection and handover attempts to high-loaded LTE cells and therefore reduces need for further redirections and handovers.
3.11.4
RAN2892 Reference data Requirements Table 60 RAS
WCDMA 16
RAN2892 hardware and software requirements I PA - R N C
mc R N C
RNC16
mcRNC16
OMS
NetAct
WCDMA OMS 16
NetAct 16.2
MS C
Support not required
Flexi Multiradio BTS
Support not required S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required MGW
Support not required
Support not required UE
3GPP Rel-8
This feature does not require any new or additional hardware. Alarms
There are no alarms related to this feature. Measurements and counters Table 61
New counters introduced by RAN2892
C o u n t e rI D
g
C o u n t e rn a m e
Me as u re me n t
M1010C270
INCOMING HANDOVERS FROM LTE DUE TO LTE Inter System Hard CELL LOAD Handover
M1010C271
LTE ISHO PREPARATION FAIL DUE TO LTE CELL Inter System Hard LOAD Handover
M1010C272
BLOCKED HANDOVERS TO LTE DUE TO LTE CELL LOAD
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, M1006C263, M1006C291, M1006C310. Table 62
Existing counters related to RAN2892
C o u n t e rI D
C o u n t e rn a m e
Me as u re me n t
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. Parameters Table 63
New parameters introduced by RAN2892 F u l ln a me
New parameters introduced by RAN2892 (Cont.) F u l ln a me
A b b r e v i a t e dn a m e
Penalty Timer LTE Load Handover
Table 64
PenaltyTimerLTELoadHo
M an age d object
RNMOBI
Parameters modified by RAN2892 F u l ln a me
A b b r e v i a t e dn a m e
Mobject an ag e d
RNCOptions
RncOptions
RNC
ADJE Identifier
ADJEId
ADJE
Tracking Area Code
AdjeTAC
ADJE
Commands There are no commands related to this feature. Sales information Table 65
RAN2892 sales information
B S W /A S W
ASW
S W c o mp o n e n t
RAN
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
RNC LK
3.11.5 Activating RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to activate the RAN2892: WCDMA-LTE Load Balancingfeature. Before you start After the activation of this feature, there is no need to restart RNC or BTS. Activation procedure does not require cell locking. This feature requires that the following feature is activated in RNC: •
RAN2176: LTE PS Handover
This feature is beneficial only in the following cases: •
In the operator's network the LTE1357: LTE-UTRAN load balancingfeature (or other feature supporting the 'Reduce Load in Serving Cell' cause value in RANAP: RELOCATION REQUEST message) and at least one of the following WCDMA RAN features are enabled: – – –
In the operator's network the LTE57: Inter RAT handover from UTRANfeature (or other feature supporting the 'No Radio Resources Available in Target cell' cause value in RANAP: RELOCATION PREPARATION FAILURE message) and the RAN2264: Smart LTE Handoverfeature are enabled.
Activate the license for the RAN2892: WCDMA-LTE Load Balancingfeature using WCDMA-LTE Load Balancinglicense key. To set the feature state to ON, use the following command: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=5450:ON; set license feature-mgmt code 0000005450 feature-adminstate on
To enable WCDMA to LTE load balancing, WCDMA cells need to have neighboring LTE cells defined with the ADJE object. The ADJE object is required to activate RAN2264: Smart LTE Handover feature. If the RAN2264: Smart LTE Handoverfeature is not active in the cell, then the operator needs to configure ADJE object. Creating ADJE object in the cell does not require license or activation of theRAN2264: Smart LTE Handover feature. Configuring ADJE object requires assigning values to the following parameters: •
AdjLIdentifier
•
AdjeCellId
•
AdjeENodeBId
•
AdjeMCC
•
AdjeMNC
•
AdjeMNCLength
•
AdjePhysicalCellId
•
AdjeTAC
The value of the AdjeTAC parameter is not used by theRAN2892: WCDMA-LTE Load Balancing feature.
g
DN09203161Issue:02
Note: Some early Rel-8 UEs have problems during e-UTRA Compressed Mode measurements. For more information on this issue, seeTechnical Support Note 149, section 5.20, available inProduct Information Center.
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 Handover Control tab, set the value of the WCDMALTELoadBalEnabled parameter to Enabled.
3.11.6 Verifying RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to verify if the RAN2892: WCDMA-LTE Load Balancingfeature works properly in the network. Before you start Activate the following features: •
in WCDMA cell: –
•
RAN2264: Smart LTE Handover
in LTE cell, which is defined in the ADJE object of the WCDMA cell: –
–
LTE57: Inter RAT handover from UTRAN or other feature supporting the 'No Radio Resources Available in Target cell' cause value in RANAP: RELOCATION PREPARATION FAILURE message LTE1357: LTE-UTRAN load balancing or other feature supporting the 'Reduce Load in Serving Cell' cause value in RANAP: RELOCATION REQUEST message
Make sure you have access to the following applications: • •
Start the M1006 RRC signalling and M1010 Inter System Hard Handover measurements. Wait for the measurement interval to begin.
g
Note: In case of 15-minute interval, data collection starts every quarter. For example 11:00, 11:15, 11:30, 11:45. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Applicationin Managing and viewing RNC measurements.
3
Generate a high load in the LTE cell defined in the ADJE object of the WCDMA cell. The purpose of this step is to trigger handovers from LTE to WCDMA due to high load in the LTE cell.
4
During the high load of LTE cell, trigger WCDMA to LTE handover. The purpose of this step is to obtain rejection of WCDMA to LTE handover attempt due to high load in the LTE cell. Triggers for WCDMA to LTE handover of HSDPA users are specified in theRAN2264: Smart LTE Handover feature description.
5
Open the RNW Measurement Presentation application.
6
Check if the values of the following counters have been collected: • • •
M1010C270: INCOMING HANDOVERS FROM L TE DUE TO LTE CELL LOAD M1010C271: LTE ISHO PREPARATION FAIL DUE TO LTE CELL LOAD M1010C272: BLOCKED HANDOVERS TOLTE DUE TO LTE CELL LOAD
For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentationin Managing and viewing RNC measurements.
Expected outcome The values of the following counters have increased: • • •
M1010C270: INCOMING HANDOVERS FROM L TE DUE TO LTE CELL LOAD M1010C271: LTE ISHO PREPARATION FAIL DUE TO LTE CELL LOAD M1010C272: BLOCKED HANDOVERS TOLTE DUE TO LTE CELL LOAD
Verifying the RAN2892: WCDMA-LTE Load Balancingfeature can be also conducted with RAN2717: Smart LTE Layeringor the RAN2980: Measurement based LTE Layering feature instead of the RAN2264: Smart LTE Handoverfeature. Then in step 4, during the high load of LTE cell, trigger WCDMA to LTElayering procedure. Triggers for WCDMA to LTE layering are specified in theRAN2717: Smart LTE Layeringand the RAN2980: Measurement based LTE Layeringfeature descriptions. The purpose of this step is to obtain sending to UE the RRC CONNECTION RELEASE message with EUTRA Target Info IE containig blacklisted LTE cell that is in the high load. If the RAN2717: Smart LTE Layering and/or the RAN2980: Measurement based LTE Layeringfeatures are used for verification, the values of counters M1006C322: RRC CONN REL WITH BLACKLISTED LTE CELLS and M1010C270: INCOMING HANDOVERS FROM LTE DUE TO LTE CELL LOAD are expected to increase.
3.11.7 Deactivating RAN2892: WCDMA-LTE Load Balancing Purpose Follow this procedure to deactivate theRAN2892: WCDMA-LTE Load Balancingfeature. Procedure
1
Open OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
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 Handover Control tab, set the value of the WCDMALTELoadBalEnabled parameter to Disabled.
4 Telecom features 4.1 RAN3086: CSFB with RIM Introduction to the feature The RAN3086: CSFB with RIM feature introduces RAN Information Management (RIM) signaling support for circuit-switched call fallback (CSFB). With the RIM procedure, LTE evolved Node B (eNB) is able to retrieve 3G System Information (SI) from RNC.
4.1.1
RAN3086 Benefits End-user benefits This feature improves the overall end-user experience by accelerating a voice call setup time. Operator benefits This feature enables exchanging information between different Radio Access Technologies via Core Network. With RIM, circuit-switched call fallback is faster.
4.1.2
RAN3086 Functional description The RAN3086: CSFB with RIM feature introduces the RAN Information Management (RIM) procedure to RNC. The RIM procedure is a 3GPP standard. With the RAN3086: CSFB with RIM feature, RNC supports the UTRA System Information (SI) RIM procedure. The RIM procedure enables exchanging information between different Radio Access Technologies via the Core Network. The RIM UTRA procedure signaling happens between LTE (eNB) and RNC. The eNB requests the Single/Multiple Reporting from RNC's reporting cell. The RIM PDUs (RAN INFORMATION REQUEST/RAN INFORMATION/RAN INFORMATION ACK) are sent between the eNB and RNC inside the DIRECT INFORMATION TRANSFER via the CN. For more information, seeSignaling of RIM UTRA SI procedurefigure and Signaling of RIM UTRA SI Procedure Errorfigure.
RNC updates SIB modification of a cell with Multiple Report
RNC terminates the Multiple Reporting (for example reporting cell is deleted in RNC)
DN09203161Issue:02
WCDMA 16 Feature Descriptions and Instructions
Figure 7
Telecom features
Signaling of RIM UTRA SI Procedure Error
RNC
eNB RAN INFORMATION REQUEST/ RAN INFORMATION ACK
RAN INFORMATION ERROR
eNB notices RIM protocol error in incoming message
eNB notices RIM application error in incoming message
RNC notices RIM protocol error in incoming message
RAN INFORMATION
RAN INFORMATION ERROR
RAN INFORMATION RAN INFORMATION APPLICATION ERROR
RAN INFORMATION ACK
RAN INFORMATION REQUEST Single Report/Multiple Report
RAN INFORMATION Single Report/Initial Multiple Report (Application Error Container)
RNC notices RIM application error in incoming message
With the UTRA SI RIM procedure, LTE eNB can inquire cell-specific System Information from RNC. The RNC replies to the request with the relevant System Information Block (SIB) and the Master Information Block (MIB) of a particular cell. RNC includes the MIB, SIB1, SIB3, SIB5, SIB7 in UTRA SI RIM procedure. LTE eNB uses the RNC's System Information for directing the UE to the WCDMA cell with RRC CONNECTION RELEASE (UTRA BCCH container, Rel-9) message, so that the UE reads the SI of the WCDMA cell from the release message. During a circuit-
switched call fallback (CSFB), UE indicates that it establishes the connection towards the RNC based on the SI from UTRA SI RIM procedure. The indication is included in the RRC CONNECTION REQUEST (System Information Stored Indicator, Rel-9). For more information about the RIM procedure, see3GPP TS 48.018 General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP).
4.1.3
RAN3086 System impact Interdependencies between features The Deferred SIB reading functionality of theRAN2746: Fast HSPA Mobilityfeature is recommended to be used with theRAN3086: CSFB with RIM feature. With Deferred SIB reading, the large SIB11 is not needed in RAN INFORMATION report from RNC, as the UE is allowed to send RRC Connection Request without reading SIB11. The following Access Class Restriction features impact working of the RAN3086: CSFB with RIM feature: • • • •
RAN801: Radio Network Access Regulation Function RAN1167: Domain Specific Access Class Restriction RAN2480: Automatic Access Class Restriction RAN3018: BTS Load Based AACR
If any of the Access Class Restriction (ACR) features is active, it updates the SIB3 with cell's access class restriction information. The frequency of updating is 1-6 times/minute. Depending on the ACR feature, the access class restriction procedure is triggered automatically due to the detected overload or manually by the user. This increases the signaling ofRAN3086: CSFB with RIM feature between the RNC and LTE eNB. The increased signaling is seen in a number of INFORMATION DIRECT TRANSFER/RAN INFORMATION (Multiple Report) sending from RNC to LTE and the acknowledge for each message DIRECT INFORMATION TRANSFER/RIM INFORMATION ACK. Impact on interfaces The RAN3086: CSFB with RIM feature impacts interfaces as follows: •
Iu –
A new RANAP:INFORMATIONDIRECT TRANSFER messageis introduced to carry UE – CN signaling messages over the Iu Interface.
Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
RAN3086 hardware and software requirements I PA - R N C
RNC16
mc R N C
Fl exi Multiradio BTS
mcRNC16
OMS
NetAct
WCDMA OMS16
NetAct 16.2
Support not required
MS C
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required
S GSN
Support not required
SG8.0
MGW
Support not required
Support not required UE
3GPP Rel-9
This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 67
New parameters introduced by RAN3086 F u l ln a me
RIM UTRA System Information Application Enabled
Table 68
Deferred Measurement Control Reading
RNFC
RIMUtraSIEnab
A b b r e v i a t e dn a m e DefMeasCtrlReading
Man age d object
WCEL
PRFILE parameters related to RAN3086 P a r a m e t e rI D
002:2306
g
Man age d object
Existing parameters related to RAN3086 F u l ln a me
Table 69
A b b r e v i a t e dn a m e
P a r a m e t e rn a m e CSFB_WITH_RIM
Note: For information on 002:2306 CSFB_WITH_RIM PRFILE parameter settings, see PRFILE Descriptions. Commands There are no commands related to this feature. Sales information
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
RNC LK
Activating RAN3086: CSFB with RIM Purpose Follow this procedure to activate the RAN3086: CSFB with RIM feature. Before you start After activating this feature there is no need to restart RNC or BTS. Activating procedure does not require cell-locking and does not cause downtime in the network. Make sure you have access to the following applications: • •
OMS Element Manager Application Launcher
Install the license key for the RAN3086: CSFB with RIM feature in the RNC and set the feature state to ON. The feature code for this feature is 5418. To set the feature state to ON, use the following command: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=5418:ON; set license feature-mgmt code 0000005418 feature-adminstate on
For information on managing licenses, seeLicensing. Before activating this feature the DefMeasCtrlReading WCEL parameter must be set to Enabled.
g
156
Note: For enabling the DefMeasCtrlReading parameter, license of the RAN2746: Fast HSPA Mobilityfeature is required.
a) Right-click on the RNFC object and select Edit par ameters.
b) Set the RIMUtraSIEnab parameter value to Enabled.
g
5
4.1.6
Note: If all the needed license/feature states are not active (On), the system does not allow to set the RIMUtraSIEnab RNFC parameter to valueEnabled. Otherwise the feature is able to be activated and deactivated without any locking/unlocking of any objects, which means that the new value shall be use after the change.
Select Apply button to save the changes.
Verifying RAN3086: CSFB with RIM Purpose Follow this procedure to verify if the RAN3086: CSFB with RIM works properly in the network. Before you start Message monitoring must be used to verify the message flow between the eNB and the RNC. Procedure
DN09203161Issue:02
1
Generate/expect a RAN INFORMATION REQUEST (Single Report) or RAN INFORMATION REQUEST (Multiple Report) from eNB via Core Network in IU:DIRECT INFORMATION TRANSFER.
2
Check that RNC has answered to the RAN INFORMATION REQUEST with RAN INFORMATION (Single Report) or RAN INFORMATION-REQUEST (Multiple
report) responses inside the IU:DIRECT INFORMATION TRANSFER towards Core Network. 3
Ensure that eNB and UE use the RIM information from RNC in the CSFB of the UE to the RNC, the UE is able to indicate it in the RNC in RRC:RRC CONNECTION REQUEST. The UE indicates it with the System Information Stored Indicator (Rel-9).
Expected outcome RNC replies with RAN INFORMATION to eNB via the Core Network. In CSFB, the UE informs the RNC in RRC CONNECTION REQUEST System Information Stored Indicatorthat it uses the system information from RIM procedure. Unexpected outcome RNC does not respond to the RAN INFORMATION REQUEST or replies with RAN INFORMATION ERROR message.
4.1.7
Deactivating RAN3086: CSFB with RIM Purpose Follow this procedure to deactivate theRAN3086: CSFB with RIM feature.
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 par ameters.
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.
The RAN3082: Device Detection feature introduces Whitelist and Blacklist mechanisms based on the IMEI TAC and SVN information. Whitelisting a feature means that only the listed IMEI (TAC, SVN) codes are allowed to use the feature, like for exampleContinuous Packet Connectivity (CPC). Blacklisting a feature means that defined IMEI codes are not allowed to use the feature.
4.2.1
RAN3082 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature permits to control the feature or functionality usage in the network as per UE model basis. It enables to quickly rule out some misbehaving UEs from the feature usage in case problems are seen in the network. The trialing period can be easily organized for a certain feature with a limited set of UE models, should such a need arise.
4.2.2
RAN3082 Functional Description The RAN3082: Device Detection feature enables device type detection in the RNC based on the International Mobile Equipment Identity (IMEI) Type Allocation Code (TAC) and Software Version Number (SVN) information. A certain feature or functionality usage can be allowed or blocked for a set of UE models based on device detection framework. The IMEI information retrieval for the device detection is performed during the PS RAB setup phase. Alternatively, if the Core Network has the IMEI query enabled, the RNC is able to retrieve the IMEISV information from the related Non-Access Stratum (NAS) signaling. Whitelist and Blacklist functionality The RAN3082: Device Detection feature introduces Whitelist and Blacklist mechanisms based on the IMEI TAC and SVN information. Whitelisting and Blacklisting is done per feature. A specific feature or functionality under the control of Device Detection feature framework can be either Whitelisted or Blacklisted at the time. Whitelisting a feature means that only the listed IMEI (TAC, SVN) codes are allowed to use the feature. However, the listed UE types can use the feature only if they have the capability. By Whitelisting a feature, operator can limit the UE types using it to only a few chosen models. A blacklist functionality contains IMEIs (TAC+SVN) codes that are not allowed to use the feature. Blacklisted UE types are blocked from using the feature even if they have a capability to use it. By Blacklisting a feature operator can rule out misbehaving UEs from using the feature. The feature or functionality allocations can be controlled with the RAN3082: Device Detection framework. The framework always contains a possibility to operate Whitelist or Blacklist based definitions. The feature can be kept available for the UE models that operate properly with the feature. At the same time the feature can be blocked from the UE models that for some reason do not work correctly with the given feature even though claiming to have the capability. Supported RAN features
RAN1644: Continuous Packet Connectivity RAN3218: Enhanced Cell Change from HSPA to 2G
Generic IMEI query Additionally for the UE model information collection, RNC provides a generic IMEI query functionality for operator. It can be used, for example together with Traffica connected to RNC, to collect UE model behavior information from the network. The generic IMEI query is available without a license control. The overallconcept operation environment is presented inThe IMEI collection and operation figure. The left side of the figure presents the means to feature collect the UE behavior information collection from the network. The operator may either directly filter out a specific UE model based on the official IMEI list provided by the corresponding authorities. Further the information can be collected with monitoring the network functionality via the tools like Traffica connected to the RNC. The detailed message monitoring and analysis based on that can be performed with L3 Data Collector (Megamon) system. Figure 8
The IMEI collection and feature operation concept
Manage/RAN3082
Monitor, collect/Generic TÜV TAC
Full TAC list
NetAct L3 Data Collector (Monitoring)
Equipment Identity Register (EIR)
NWI3 CM plan interface
TAC list collection for example with Excel
GUI
CN Traffica (IMEI query enabled at CN)
RNW plan XML
OMS BTS O&M
Traffica reporting with IMEI information (xx% out of calls)
RNC Traffica (IMEI delivery from RNC)
RNC
WDEV object class The RAN3082: Device Detection feature implements a new RNW object class: WCDMA Device Detection (WDEV). The WDEV object class contains the attributes for the UE Type Allocation Code (TAC) and Software Version Number (SVN) based on the feature Blacklist and Whitelist functionality. The WDEV object class is located to the main level of the RNC object hierarchy and is present in the local UI and within the RNW plan interface. Measurement type for device detection
A new measurement type: M1029 Device Detection is introduced where the object id includes the feature information for the Whitelist/Blacklist counter. The target object of the measurement is feature code that refers to the blacklisted or whitelisted feature. A feature code zero is used for counter M1029C0. The measurement is always available regardless of Whitelist/Blacklist features, but no specific statistics data is produced when blacklisting is not activated.
4.2.3
RAN3082 System impact Interdependencies between features The RAN3082: Device Detection feature framework is applied generically to all new applicable features in RRM and Telecom area. The applicable features are specified and implemented to be ready to support the device detection. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
4.2.4
RAN3082 Reference data Requirements Table 71: RAN3082 hardware and software requirementslists the software required for this feature. Table 71 RAS
WCDMA 16
RAN3082 hardware and software requirements I PA - R N C
mc R N C
RNC16
mcRNC16
OMS
NetAct
WCDMA OMS16
NetAct 16.2
Flexi Multiradio BTS
Support not required
MS C
Support not required
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required MGW
Support not required
Support not required UE
Support not required
This feature requires no new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters Table 72: New counters introduced by RAN3082lists counters introduced with this feature.
Note: M1029 Device Detection is a new new measurement type. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 73: New parameters introduced by RAN3082lists parameters introduced with this feature. Table 73
New parameters introduced by RAN3082 F u l ln a m e
M a n a g e do b j e c t
WDEV
WDEVname
WDEVName
WDEV
List of TAC entries
TACList
WDEV
SVN software version number Whitelist features
SVN Whitelist
WDEV WDEV
Blacklist features
Blacklist
WDEV
Change origin
WDEVChangeOrigin
WDEV
WDEV control activation
WDEVControlEnabled
RNFC
IMEIQuery
g
A b b r e v i at e dn a m e WDEVId
WDEV identifier
IMEIQuery
RNC
Note: WCDMA Device Detection (WDEV) is a new object class. Table 74: Parameters modified by RAN3082lists parameters modified by this feature. Table 74
Parameters modified by RAN3082 F u l ln a m e
RNCOptions
A b b r e v i at e dn a m e RNCOptions
M a n a g e do b j e c t
RNC
Commands There are no commands related to this feature. Sales information
L i c e n s e c o n t r o l i n n e t w o r k e l e me n t
RNC LK
Activating RAN3082: Device Detection Purpose Follow this procedure to activate the RAN3082: Device Detection feature. Before you start After activating this feature there is no need to restart RNC. Activating procedure does not require cell-locking. This feature becomes active for the UEs connecting after the feature has been configured. The ongoing connections/calls are not affected. Ensure that the features that are to be controlled with theRAN3082: Device Detection feature are already running in the network. This feature is controlled by a license. For information on managing licenses, see Licensing. The feature code for this feature is 5586. To set the feature state toON, use the following command: •
for IPA-RNC:
•
for mcRNC:
ZW7M:FEA=5586:ON; set license feature-mgmt code 0000005586 feature-adminstate on
The RAN3082: Device Detection feature is a capacity license controlled feature. The number of capacity steps corresponds to the number of simultaneously active Whitelist and Blacklist controlled features. The Blacklist/Whitelist activation consumes one capacity step. It is allowed to activate one Blacklist/Whitelist feature/functionality per one license capacity step. Maximum amount of capacity steps is 16. The upper capacity limit is defined via the Whitelist and Blacklist parameters bitmask length. The feature can be managed via the normal RNW configuration management interfaces: RNW local UI and NetAct. The feature planning related UE model and feature behavior information can be collected from various network and system monitoring tools like Traffica, L3 Data Collector, and the PM measurements providing overall information.
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 value of the WDEVControlEnabled parameter to Enabled. The feature and UE control attributes within the WDEV instances do not have any effect to system behavior unless the feature main control parameter is enabled.
5
Expand the RNC.
6
Create the WDEV object instance(s). Sub-steps
a) Right-click on the RNC object and select Create New Object ► WDEV. Create the needed amount of the WDEV objects with planned TAC, SVN and feature control information. The WDEV object instance contains Whitelist and Blacklist control parameters against which UE models defined within the TAC list are being controlled.
g
Note: The same feature can be controlled via several WDEV instances. The TAC entries defined for a certain feature have to be unique in all WDEV instances containing the same feature control information. The new value is used for the next new calls after the parameter modification. The ongoing calls are not affected. Whitelist: RNC allows to use this feature only for the defined TAC values. Blacklist: RNC blocks the given feature use for the defined TAC values. A particular feature cannot be Blacklisted and Whitelisted simultaneously. The same bit value cannot be set to value 1 in both Whitelist and Blacklist bit masks. This applies to all configured WDEV instances.
a) Right-click on the WDE V object and sele ct Edit par ameters.
b) Set the Whitelist parameter value as needed in relation to defined WDEV objects.
c) Set the Blacklist parameter value as needed in relation to defined WDEV objects.
8
4.2.5.1
Select Apply button to save the changes.
Activating generic IMEI query in the RNC Purpose The RNC provides the option to collect the IMEI information along with the detailed network behavior monitoring via RNC Traffica. This can be used to collect additional UE behavior detailed monitoring data in the network. The generic IMEI information inquiry performed by the RNC can be activated via the RNC level parameter. RNC performs the IMEI query for the defined percentage of the RAB establishments. The RNC query is performed in addition to the CN-initiated IMEI queries. The RNC level IMEI query can be activated for example in case the query is not activated at the core network elements. RNC is able to retrieve the IMEI from the CNperformed queries providing the similar result with the RNC level query.
g
166
Note: The generic IMEI query functionality is available without any license.
a) Right-click on the RNC obje ct and select Edit parameters.
b) Set the value of the IMEIQuery parameter within range 1-100. The IMEIQuery parameter provides the control over generic IMEI query performed by the RNC after RAB establishment.
4
4.2.6
Select Apply button to save the changes.
Verifying RAN3082: Device Detection Purpose Follow this procedure to verify that the activation of the RAN3082: Device Detection feature has been successful. Before you start Define the set of UEs and features to be controlled with the RAN3082: Device Detection feature functionality. Plan both Whitelisted and Blacklisted features in order to validate the overall feature behavior. The features that are controlled with the device detection, have to be properly configured in the network.
Select the features to be controlled with the device detection. Sub-steps
a) Ensure that the features are configured and running in the network.
b) Check if the UEs are in the network where, for example, Blacklisted TAC codes correspond with to UE IMEI information.
2
Open the RNW Measurement Management application. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.
3
Use the RNW Measurement Management application to start the M1029 measurement. Alternatively the measurement can be started using NetAct Administration of Measurements Application.
4
Wait for the next 15-minutes interval to begin. The measurement interval then starts.
5
Make a PS call with the UE that is whitelisted or blacklisted. CPC black/whitelisting is only checked when making a PS call. Without a PS call there are no counter updates.
6
Wait until the current 15-minute interval ends and then another 10 minutes. After the measurement collection, it takes additional up to 10 minutes for the measurement data to be transferred to the OMS.
7
Open the RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
8
Check if any of the following counters have value greater than 0: • •
For the Blacklist configuration the related counter should be updated according to the feature blocking operations the network system performs based on the device detection configuration.
Expected outcome The values of counters M1029C1 and M1029C2 are updated according to the Whitelist and Blacklist operations performed according to theRAN3082: Device Detection feature configuration.
4.2.6.1
Verifying generic IMEI query in the RNC Purpose Follow this procedure to verify that the activation of the IMEI query functionality has been successful. Procedure
1
Open the RNW Measurement Management application. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.
2
Use the RNW Measurement Management application to start the M1029 measurement. Alternatively the measurement can be started using NetAct Administration of Measurements Application.
3
Wait for the next 15-minutes interval to begin. The measurement interval then starts.
4
Make a PS call.
5
Wait until the current 15-minute interval ends and then another 10 minutes. After the measurement collection, it takes additional up to 10 minutes for the measurement data to be transferred to the OMS.
6
Open the RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
Check if the following counter has value greater than 0: •
M1029C0 IMEI QUERY SENT BY RNC
Expected outcome The counter M1029C0 IMEI QUERY SENT BY RNC is updated by the system.
4.2.7
Deactivating RAN3082: Device Detection Purpose Follow this procedure to fully deactivate the RAN3082: Device Detection feature. Procedure
1
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 value of the WDEVControlEnabled parameter value to Disabled.
5
4.2.7.1
Select Apply button to save the changes.
Deactivating a Whitelist or Blacklist functionality Purpose Follow this procedure to deactivate a specific feature Whitelist or Blacklist functionality.
Expand the RNC object then expand the WDEV object.
4
Configure the WDEV object: Sub-steps
a) Right-click on the WDEV object and select Edit Parameters.
b) Set the feature-specific bit value of the Whitelist or Blacklist parameter to 0 to deactivate a specific feature control. The control has to be disabled in all related WDEV instances. The feature control does not affect already ongoing connections/calls.
5
Select Apply button to save the changes.
Expected outcome The RAN3082: Device Detection feature does not control the feature use anymore.
4.2.7.2
Deactivating generic IMEI query in the RNC Purpose Follow this procedure to deactivate generic IMEI query functionality.
5 Transmission and transport features 5.1 RAN3112: mcRNC Integrated Ethernet Switching Introduction to the feature The Multicontroller RNC (mcRNC) has an option to aggregate Ethernet traffic from different external interface processing units (EIPU) within different box controller node (BCN) modules to a single 10 GE interface using the integrated Ethernet Switching. This feature provides new counters that measure both the backplane and the external interfaces Ethernet performance characteristics. These counters allow identifying possible bottlenecks for traffic switched among different BCN modules and assist in the proper connectivity dimensioning and design.
5.1.1
RAN3112 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows the operator to dimension the number of physical 10 GE interfaces to the required capacity of the mcRNC independently of the number of BCN modules and EIPU units conforming to the mcRNC setup. The traffic at the mcRNC external physical interfaces and backplane interfaces can be monitored via the generic PM framework. This provides a possibility to follow the interface utilization and react timely to the traffic increase by planning for the mcRNC connectivity. The backplane link load can be monitored via Ethernet Traffic counters, which allow the system/the operator to verify if the configuration works as intended also from the backplane link load point of view.
5.1.2
RAN3112 Functional description The mcRNC has an option to aggregate Ethernet traffic from different EIPU within different BCN modules to a single 10 GE interface using the integrated Ethernet Switching. This feature provides new counters that measure both the backplane and external interfaces Ethernet performance characteristics. These counters allow identifying possible bottlenecks for traffic switched among different BCN modules and assist in the proper dimensioning and design of the number of 10 GE interface to be used for the connection of the mcRNC to the site router. It provides the benefit to dimension the number of physical 10 GE interfaces to the required capacity of the mcRNC independently of the number of BCN modules and EIPU units conforming the mcRNC setup. The mcRNC provides solution to optimize the external connectivity based on the actual traffic data volume in the network while fully utilizing the processing capacity for the signaling-dominated traffic profile. Within the 10 GE connectivity optimized solution traffic from several EIPU units, that can be located to different BCN modules, can be aggregated to the shared 10GE port located in any BCN module. The physical interface Ethernet measurement supports 1 GE and 10 GE ports including the ports shared by several computing nodes. The RAN3112: mcRNC Integrated Ethernet Switchingfeature introduces new measurement type M805 to measure mcRNC Ethernet interface traffic.
Using the 10 GE interfaces for external connectivity requires a capacity license, which is based on the number of 10 GE interfaces applied for the external connectivity. The mcRNC can support the BCN module front panel 1 GE and 10 GE physical port M805 measurement for the BCN-B HW module variant. TheM805 measurements are supported for all mcRNC capacity steps for all configured and active physical ports that are used for BCN external transport (SFP ports) and for the backplane connectivity. The M805 measurement type can be used even ifRAN3112: mcRNC Integrated Ethernet Switching feature is deactivated . Switch ports used for BCN internal traffic cannot be measured. The external interface SFP ports covered by this feature are the backplane ports from SFP+0 to SFP+6, and external connectivity port from SFP+11 to SFP+12 and SFP13 to SFP22, see Figure 9: mcRNC SFP ports. Figure 9
mcRNC SFP ports
The mcRNC provides new measurementM805 BCN Ethernet Statistics. The M805 BCN Ethernet Statistics measurement provides Ethernet layer statistics of mcRNC interfaces whose operational state is enabled. The object of the measurement is BCN/ETHPORT where BCN refers to the BCN module number and ETHPORT is the port identifier like SFP11.
5.1.3
RAN3112 System impact Interdependencies between features This feature implements the licenses forRAN2696: mcRNC 10 Gigabit Ethernet Based Network Connectivity feature. The 10 GE interfaces licenses are now under a capacitybased license referring to the number of 10 GE physical interfaces applied for the external connectivity (SFP+11 and SFP+12). Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools
This feature has no impact on network and network element management tools. Impact on system performance and capacity This feature improves the current mcRNC solution to optimize the external connectivity based on the actual traffic data volume in the network.
5.1.4
RAN3112 Reference data Requirements Table 76
RAN3112 hardware and software requirements
RAS
I PA - R N C
mc R N C
WCDMA 16
Support not required
mcRNC16
OMS
NetAct
WOMS16
NetAct 16.2
MS C
Support not required
Fl exi Multiradio BTS
Support not required S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required MGW
Support not required
Support not required UE
Support not required
This feature is implemented for the BCN-B hardware. Alarms There are no alarms related to this feature. BTS faults and reported alarms There are no BTS faults and reported alarms related to this feature. Commands There are no commands related to this feature. Measurements and counters Table 77
Key performance indicators There are no KPIs related to this feature. Parameters There are no parameters related to this feature. Sales information Table 78
RAN3112 Sales information BSW /ASW
BSW
S W c o mp o n e n t
RAN
L i cen secon tro l in n etwo rk 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.
RAN3193 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows the operator to secure the OSPF routing messages to prevent accidental OSPFv2 misconfigurations.
5.2.2
RAN3193 Functional description OSPFv2 authentication is supported in RNC2600, mcRNC, and mcBSC according to RFC2328 appendix D.3. The authentication prevents malicious or accidental changes of the controller site routing configuration by discarding received OSPFv2 packets that do not carry a configured key. When using the cryptographic message digest algorithm version 5 (MD5) option, the security is improved as keys will not be transmitted in clear text and thus cannot be gathered by simple packet sniffing. The OSPF site setup is represented in Figure 10: OSPF site solution. The following authentication options are supported in mcRNC: • • •
null key (clear text) MD5 (cryptographic key)
Figure 10
OSPF site solution
The RAN3193: OSPF Authentication for Controllerfeature requires OSPFv2 authentication support in the site routers. The listed authentication methods are supported through all controller products except the MD5 option that is not supported for RNC2600. The RNC2600 supports only the clear text simple password.
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 79 RAS
WCDMA 16
RAN3193 hardware and software requirements I PA - R N C
mc R N C
RNC16
mcRNC16
OMS
NetAct
Support not required
Support not required
Flexi Multiradio BTS
Support not required
MS C
Support not required
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required MGW
Support not required
Support not required UE
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.
The related SCLI command for this feature isset routing ospf interface authtype. This is to set the OSFP routing interfaceauthentication type. Measurements and counters There are no new measurements or counters related to this feature. Key performance indicators There are no KPIs related to this feature. Parameters Table 80
Existing parameters related to RAN3193 F u l l n am e
A b b re v i ate dn ame
Key ID
M an age dob j e ct
keyId
MD5 Secret
secret
Authtype
authType
BFD detect multiplier
bfdDetectMult
BFD monitoring
bfdMonitoring
BFD RX interval
bfdRxInterval
BFD TX interval
bfdTxInterval
Dead interval
deadInterval
Election priority
electionPriority
O2IFC Fast hello interval for interface Hello interval
6 Operability features 6.1 RAN3242: Category for Obsolete Parameters Introduction to the feature The RAN3242: Category for Obsolete Parametersfeature enhances the current parameter categorization in the NetAct application. The feature introduces a new parameter categoryObsolete, and improves theAdvanced category by displaying both the basic and advanced parameters.
6.1.1
RAN3242 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature benefits the operator as follows: •
•
•
Operating expenses (OPEX)is reduced because of the simplified plan file, and limitation of the number of parameters to be displayed in NetAct configuration management (CM) tools. The categorization of the parameters prevents the occurrence of mistake, which leads to a faster search of the needed parameter. The operators are allowed to modify the categorized obsoleteparameters if the parameters are still in use and to give feedback before the parameters are completely removed.
6.1.2
RAN3242 Functional description The RAN3242: Category for Obsolete Parametersfeature improves the parameter categorization in NetAct CM Editor and NetAct CM Plan Editor. The feature introduces a new parameter categoryObsolete. This feature makes the NetAct parameter categorization to have four category views: •
All
•
Basic Advanced Obsolete
• •
The child parameters are also supported to be categorized as Basic, Advanced, or Obsolete. The child parameters can be categorized differently from the parent parameter. And if the child parameter is uncategorized, it is displayed in the view corresponding to the category of the parent parameter. Parameter category views The following are the definition of each category view: •
180
The All view displays all the parameters.This view displays the Basic, Advanced, Obsolete, and the uncategorized parameters.
Note: Uncategorized parameters may be found in network elements that can no longer be modified. This feature targets only the operator configurable RNW and IP parameters. The RNC ATM configuration parameters are not categorized. There might be some cases where a parameter has been categorized differently than the category expected by the operator. In such cases,All view provides an efficient way for the operator to find such parameters. •
•
•
The Basic view displays the parameters that are essential for RNC or BTS integration and deployment and parameters that are used regularly to manage the network. As a default view, the NetAct Configurator displays the parameters under Basic view. The Advanced view displays both the basic and advanced parameters. Advanced parameters are used in network optimization or for fine-tuning functionalities that are related to complex features. Operators often depend on basic parameters, the reason why basic and advanced parameters are combined. The Obsolete view displays only the obsolete parameters that are intended to be removed in the future release.
Nokia Networks' engineering team derives obsolete parameters by gathering the usage of each configuration management parameters at operators' live networks. When the parameter utilization factor is below or equal to the defined target value of 90%-100%, the parameters are categorized as obsolete. These obsolete parameters are the: • •
parameters that are always used as default parameters that are not used by operators
These obsolete parameters are still modifiable and visible in the NetAct Configurator display but will soon be removed. The operators can modify the parameters categorized asObsolete. If they assessed that a certain parameter in theObsolete category is still used in their networks, then they can modify the category and justify the reason why they need to keep the parameter to Nokia Networks customer support. Operators can also create their own user-defined view if they are not satisfied with the pre-defined categorization. This leads to an efficient means for parameter configuration administration and ease the possibility of error or mistake by removing parameters that are not frequently used in the NetAct Configurator display. When the obsolete parameter is in the user-defined view, then it is displayed differently than other parameters to alert the operator that the parameter is a candidate for removal.
6.1.3
RAN3242 System impact Interdependencies between features There are no features interdependent with this feature. This feature is related to LTE2506: Category for Obsolete Parametersfeature. Impact on interfaces There are no impacts on interfaces for this feature.
Impact on network and network element management tools The impact for NetAct are as follows: • • •
•
A new parameter category view Obsolete is introduced. The default view is changed from All to Basic. NetAct displays differentparameter category values for different parameters in the same structure. NetAct displays the obsoleteparameters that arein the user-defined view ina visually different way that alerts the operator that the parameter is intended to be removed.
Impact on system performance and capacity There are no impacts on system performance or system capacity for this feature.
6.1.4
RAN3242 Reference data Requirements Table 82
RAN3242 hardware and software requirements
RAS
I PA - R N C
mc R N C
WCDMA 16
Support not required
Support not required
OMS
NetAct
Support not required
NetAct 16.2
Flexi Multiradio BTS
Support not required
MS C
Support not required
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
Support not required
Support not required
MGW
Support not required
UE
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 asObsolete, see: •
RNC –
Multicontroller RNC IP Parameters
–
Multicontroller RNC RNW Parameters IPA-RNC IP Parameters IPA-RNC RNW Parameters
Flexi Multiradio BTS WCDMA Parameters Flexi Transport Module Parameters
Commands There are no commands related to this feature. Sales information Table 83
RAN3242 Sales information BS W/ASW
S W c o mp o n e n t
BSWNetAct
RAN
L i c e n s e c on t ro l i n n et w o rk element
NetActRadioWCDMA Standard SW
6.2 RAN2706: Delta Configuration and Change Notification for BTS Transport Introduction to the feature The RAN2706: Delta Configuration and Change Notification for BTS Transport feature supports the creation, pre-validation, download, and activation of a delta configuration plan for the base transceiver station's (BTS) transport subsystem (TRS) parameters. A delta configuration plan may consist of updates for both BTS and TRS parameters that are sent to a target set of BTSs. NetAct is able to send a single delta configuration plan to each target BTS. The feature also supports the sending of a configuration change notification (CCN) that is used to synchronize the current configuration of the BTS maintained in NetAct. The BTS sends a CCN to NetAct for every transport configuration managed object (MO) that is modified.
6.2.1
RAN2706 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature benefits the operator as follows: • • •
DN09203161Issue:02
The unnecessary restartof the BTS (and co-located BTS transport)initiated during the complete transport configuration plan activation is prevented. Less service interruptions because theunnecessary BTS transport module reset is avoided. The unnecessary upload of BTS transport configuration isprevented.
RAN2706 Functional description The RAN2706: Delta Configuration and Change Notification for BTS Transport feature supports the on-line configuration plan activation of transport configuration modifications. The following transport provisioning operations are also used in any planned configuration change: • • • • •
creation of a delta configuration planof on-line modifications pre-validation of the delta configuration plan download of the delta configuration plan activation of the configuration plan viewing of the updated transport configuration inNetAct
Creation of a delta configuration plan of on-line modifications The creation of a delta configuration plan containing transport configuration modifications is initiated at NetAct. In using the NetAct Configuration Management (CM) applications, the operator specifies the needed modifications for MOs to:
•
add delete
•
update
•
NetAct provides notification if the specified modification requests are possible and whether the changes to all transport managed objects (MO) may be updated on line.
g
Note: Only the managed objects and parameters that are specified as on-line modifiable do not require a BTS restart. Otherwise, NetAct provides notification that the specified modifications include a change that require a BTS restart. Pre-validation of a delta configuration plan containing transport configuration The delta configuration plan containing transport configuration needs to be pre-validated prior to download. NetAct creates a partial site configuration file (SCF) containing each modification specified in the delta configuration plan for each target BTS. This results in a decrease in download time compared to a complete configuration plan. The Validation operation in NetAct invokes the pre-validation of the delta configuration plan. For more information, seeNetAct documentation CM Operations Manager Help► Provisioning plans. NetAct pre-validates the delta configuration plan for each target BTS, and reports any validation errors.
g
Note: NetAct invokes a BTS site manager (BTSSM) provided plug-in for pre-validation. Download of the delta configuration plan containing transport configuration In this phase, the operator selects a configuration plan containing transport configuration modifications to download to a set of target BTSs. NetAct requests the download of the partial SCF to the set of target BTSs, and tracks the progress of the configuration plan download. During the download operation, the configuration plan is also validated by thePre-activate operation in NetAct.
For more information, seeNetAct documentation CM Operations Manager Help► Provisioning plans.
g
Note: NetAct invokes a BTSSM provided plug-in for pre-validation. Activation of configuration plan containing transport configuration The operator now selects a configuration plan, which has been downloaded to the target set of BTSs, and requests the activation of the parameter modifications by invoking the Activate pre-activated operation addition/deletion/update of the transport parameters values do not require in theNetAct. BTS toThe restart if all the transport managed objects are marked as on-line.
g
Note: NetAct provides a notification if the specified modifications include a change that requires a BTS restart. Activate is another provisioning operation in NetAct, which includes download, validation, and activation in a single operation. For more information, seeNetAct documentation CM Operations Manager Help► Provisioning plans. NetAct tracks the progress of the configuration plan activation of each target BTS and reports the success or failure of the operation. Viewing of the updated transport configuration in NetAct The BTS activates the downloaded configuration plan and includes each MO that is modified during the activation in a configuration change notification (CCN) that is sent to NetAct. CCNs are also sent to NetAct by the BTS in case transport configuration is modified using BTSSM. NetAct updates the data of the BTS configuration to match the changed data indicated in the CCN. Thus, this prevents the need to upload the full transport configuration file from the BTS. NetAct can then display the current data of the BTS configuration. Exceptions in using the delta configuration plan There are exceptions in using the delta configuration plan with regards to MOs that are asynchronous transfer mode (ATM) and non-ATM. Different configuration scenarios and special handling are needed for the ATM and non-ATM MOs that involve the delta configuration plan. Configuration scenarios for ATM MOs The configuration of ATM MOs with the delta configuration plan must be done in a certain order because of the parent-child relationship and interconnection of the MOs. Thus, the use of multiple delta on-line configuration updates in NetAct is needed. If the parameter of any, MO notCreate on-linethe modifiable, only way tooperation modify the parameter is byDelete and is then MO. Thethe configuration order of the MOs in Add/Delete configurator model must be followed:
A special handling is needed for TRDE MO and M-plane connections. The TRDE MO is interrelated to both VPCT and VCCT MOs. Therefore, VPCT and VCCT MOs must be deleted or updated first prior to the delete operation of TRDE MO. All the parameters of the TRDE are on-line configurable if the TRDE is not used in any ATM connection yet. For VCCT that is used for M-plane, the delete operation of the VCCT and the reconfiguration of the new VCCT for M-plane must be done in a single delta configuration plan. Otherwise, the M-plane connection is lost, and site visit is needed if the BTS does not supportRAN2554: Transport configuration fallback for M-plane recovery feature. Configuration scenarios for Non-ATM MOs The online modification of the transport mode and BTS ID parameters are not allowed with the delta configuration plan. A full on-line configuration plan is forced by NetAct or BTSSM in re-commissioning the BTS to modify the parameters. The LinkOAM (LOAM) must be disabled E ( THLK.linkOAMEnabled) using BTSSM for an Ethernet link before LOAM profile can be edited. Otherwise, the modification of the Ethernet LOAM profile is rejected by the BTS. For more information, see BTSSM Online Help>TRS Hardware- Ethernet LinkOAM.
The BTS rejects the swapping of VLAN IDs or IP addresses of two existing IP interfaces (VLAN or plain Ethernet) using a single delta configuration plan. When the BTS tries to apply the new ID on the 1st VLAN, the BTS finds that there is another VLAN already existing with the same ID. The same problem happens when the existing IP addresses are swapped between IP interfaces (VLAN or plain Ethernet). The operator needs multiple delta configuration plans to do VLAN IDs or IP addresses swapping. The following are examples of delta configuration plans on how to swap a VLAN ID of the IP interfaces: 1. Temporary assign an unused VLAN ID to one of the VLAN IP interfaces. 2. Modify the other VLAN IP interface to the previous VLAN ID. 3. Modify the second VLAN IP interface to the first VLAN ID.
g
Note: Same procedures are used to swap IP addresses. Plesiochronous digital hierarchy (PDH) interface type is not allowed to modify using delta configuration plan if there are inverse multiplexing for ATM (IMA) or any ATM configuration objects in the PDH interface. A full configuration plan is forced by NetAct to update the PDH parameter. Manual commissioning or re-commissioning During manual commissioning or re-commissioning using BTSSM, the operator can select, as shown in Figure 12: Send parameters options in BTSSM , either of the following options to send the parameters to the BTS: • •
Only changes- to send only the delta configuration All parameters- to send the full SCF
Figure 12
Send parameters options in BTSSM
Special handling is needed in terms of Bidirectional Forwarding Detection (BFD) in executing manual commissioning or re-commissioning of the BTS. To disable OSPF withdelta BFD configuration that is pre-configured as enabled and BFD option. MO exists, the operator can use the by selecting theOnly changes To enable OSPF with BFD that is pre-configured as disabled and BFD MO does not exist, the operator needs to split the operation using multiple delta configurations in the following order:
The OSPF with BFD can be enabled and disabled in the IP view as shown in Figure 13: OSPF with BFD in BTSSM. Figure 13
OSPF with BFD in BTSSM
To modify Ethernet-based IP interface (IEIF) or VLAN interface (IVIF) local IP address (localIpAddr), and there is an existing BFD MO that is bounded to this address, the operator needs to send full SCF by selecting theAll parameters option. Figure 14
6.2.3
Local IP address
RAN2706 System impact Interdependencies between features This feature is related to the following:
RAN885: Remote BTS SCF Management feature supports configuration updates using delta configuration files and synchronization between NetAct and BTS using configuration change notifications (CCN) for non-transport configuration in WCDMA networks. RAN2554: Transport Configuration Fallback feature supports the creation of a full transport configuration fallback file when activating a full transport subsystem (TRS) configuration file.
Other related features: •
LTE552: Delta Configuration for Transport
Impact on interfaces There are no impacts on interfaces for this feature. Impact on network and network element management tools There are no impacts on network and network element management tools for this feature. Impact on system performance and capacity This feature has an impact on O&M system performance. The time to download a configuration plan and the time to synchronize the configuration changes between the NetAct and target set of BTSs are reduced. There is no impact on system capacity for this fearure.
6.2.4
RAN2706 Reference data Requirements Table 84
RAN2706 hardware and software requirements
RAS
I PA - R N C
mc R N C
WCDMA 16
Support not required
Support not required
OMS
NetAct
Support not required
NetAct 16.2
MS C
Support not required
Fl exi Multiradio BTS
WBTS16
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
WBTS16
MGW
Support not required
Not planned
UE
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 new measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters
There are no parameters related to this feature. Commands There are no commands related to this feature. Sales information Table 85
RAN2706 Sales information BSW /ASW
BSW
S W c o mp o n e n t
RAN
L i cen secon tro l in n etwo rk element
-
6.3 RAN2367: DNS Support for Certificate Examination Introduction to the feature The RAN2367: DNS Support for Certificate Examinationfeature supports the replacement of the fixed IP address of a certificate revocation repository server with the fully qualified domain name (FQDN) indicated within the certificate or in manually configured certificate revocation list (CRL). The feature enables the BTS to query the domain name server (DNS) to acquire the IP address of the repository server by using the FQDN.
6.3.1
RAN2367 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature leads to OPEX savings by eliminating the need to renew all the certificates with fixed IP address that is used in revocation repository in the network. With the introduction of FQDN, only the DNS server needs to be updated when the revocation server is changed.
6.3.2
RAN2367 Functional description It is required to check if the certificates of the remote peers and configured trust anchors are valid and are not revoked. To make this checking possible, each certificate can contain the uniform resource locator (URL) of the corresponding revocation repository server or the URL can be preconfigured manually. It is a drawback for the operators when the address of the repository server is changed. All the certificates integrated to the link of the modified repository server address become invalid and the renewal of certificates is needed. RAN2367: DNS Support for Certificate Examinationfeature supports the DNS resolution in retrieving the addresses of the revocation distribution points. The fully qualified domain name (FQDN) is integrated within the certificates or to the manually configured CRL distribution points (CDP) that direct the certificate examination query to the DNS and retrieve the URL or the IP address of the revocation repository servers.
The DNS client, which is the BTS, sends the FQDN to the DNS and in return, provides the corresponding IP address of the repository server. In this case, only the DNS server needs to be updated when the revocation server address is changed. Domain name server (DNS) DNS is a generic solution that is utilized by several applications and for this feature, it is the certificate examination of network elements (NEs). The DNS IP address must be configured in the NE. The configuration is available in the BTS configuration or in element (EM). A secondary DNS IP address can be configured plan as well, it the is used whenmanager the primary DNS is unreachable. If the DNS query has failed for both primary and secondary DNS, the DNS client indicates the failure and aborts the query. The BTS raises the 61074: CRL Update failurealarm if the CRL update fails. This alarm is raised for one of the following reasons: • • • •
LDAP binding failure LDAP search is empty (no CRL found) LDAP search containing multiple entry CRL signature validation failure
•
CRL file exceeding BTS storage limit BTS certificate being part of the CRL
•
DNS resolution failure
•
The feature supports the following functions: • •
g
6.3.3
DNS Protocol according to RFC1034 and RFC1035 Name lookup to resolve FQDN allocation of the IP address Note: The network elements support both User Datagram Protocol (UDP) and Transmission Control Protocol (TCP) for the DNS queries. If the DNS response is exceeded to 512 bytes, the server replaces it by an explicitly truncated packet and the client retries using TCP.
RAN2367 System impact Interdependencies between features The RAN2084: Support for certificate revocation (BTS)feature is needed to be activated and running. This feature introduces certificate revocation support in BTS. Other related feature isRAN2268: Multi-Layer Certificate Authorities . Impact on interfaces There are no impacts on interfaces for this feature. Impact on network and network element management tools There are no impacts on network and network element management tools for this feature. Impact on system performance and capacity There are no impacts on system capacity for this fearure.
This feature requires no new or additional hardware. Alarms Table 87
Alarms A l arm ID
A l ar m n ame
61074
CRLupdatefailure
Measurements and counters There are no new measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 88
Parameters F u l ln a me
A b b r e v i a t e dn a m e
M a n a g e do b j e c t
Primary DNS Server IPv4 address
IDNS.serverIpAddress
WBTS
Secondary DNS Server IPv4 address
IDNS.serverIpAddress2
WBTS
Commands There are no commands related to this feature. Sales information Table 89
6.4 RAN3247/LTE2507/RG602496: Energy Efficiency Shut Down Mode with RF Sharing Introduction to the feature The RAN3247: Energy Efficiency Shut Down Mode with RF Sharingfeature introduces a power saving mode for RF sharing configurations.
6.4.1
RAN3247/LTE2507/RG602496 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature helps to reduce OPEX due to energy savings provided by a power saving mode for RF sharing configurations.
6.4.2
RAN3247/LTE2507/RG602496 Functional description The RAN3247: Energy Efficiency Shut Down Mode with RF Sharingfeature releases RAT resources from the RF module during low traffic conditions or when required by the operator-defined profile. The Power Amplifier automatically goes into stand-by mode when both conditions are met: •
Depending on RF sharing configuration, at least twoRAT specific features are activated: – RG301936: Intelligent MCPA TRX Shutdown – RAN955: Power Saving Mode for BTS – LTE1103: Load based Power Saving for multi-layer networks
•
6.4.3
There are no radio resources reserved.
RAN3247/LTE2507/RG602496 System impact Interdependencies between features Depending on RF sharing configuration, at least two of the following features must be activated before starting up theRAN3247: Energy Efficiency Shut Down Mode with RF Sharing feature: • • •
g
RG301936: Intelligent MCPA TRX Shutdown RAN955: Power Saving Mode for BTS LTE1103: Load based Power Saving for multi-layer networks Note: NOTE: RAN3247 works under the terms of RG301936, RAN955, and LTE1103 licenses.
Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools
This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
6.4.4
RAN3247/LTE2507/RG602496 Reference data Requirements Table 90
RAN3247 hardware and software requirements
RAS
I PA - R N C
mc R N C
WCDMA 16
Support not required
Support not required
OMS
NetAct
Support not required
Support not required
MS C
Support not required
Flexi Multiradio BTS
WBTS16
S GSN
Support not required
Flexi Flexi Lite Multiradio 10 BTS BTS
WBTS16
MGW
Support not required
Not relevant
UE
Support not required
This feature does not require any new or additional hardware. Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 91
6.4.5
RAN3247 Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
Activating RAN3247: Energy Efficiency Shut Down Mode with RF Sharing Depending on RF sharing configuration, at least two of the following features must be activated before starting up theRAN3247: Energy Efficiency Shut Down Mode with RF Sharing feature: •
RAN955: Power Saving Mode for BTS LTE1103: Load based Power Saving for multi-layer networks
Follow activation procedures in order to activate features in respective technologies.
6.4.5.1 6.4.5.1.1
Activating RG301936: Intelligent MCPA TRX shutdown in GSM Activating RG301936: Intelligent MCPA TRX shutdown Before you start • The license for the RG301936: Intelligent MCPA TRX shutdownfeature has to be installed. • The BSS20984: 2G TRX Automatic Power Downfeature has to be activated. • The Flexi Multiradio licencehas to be installed and enabled. • The BSC release S16.1 or greater. • The Flexi Multiradio 10with BTS GF1 1.0.0 release or greater. Procedure
1
Change value of the 2G TRX Automatic Power Down feature state to ON using the W7M command. ZW7M:FEA=1236:ON;
2
Change value of the Intelligent MCPA TRX shutdownfeature state to ON using the W7M command. ZW7M:FEA=4438:ON;
3
Ensure that the feature state was changed successfully using the W7I command. ZW7I:FEA,FULL:FEA=4438;
6.4.5.1.2
Verifying RG301936: Intelligent MCPA TRX shutdown Purpose Activation of the feature RG301936: Intelligent MCPA TRX shutdowncan be verified by checking the value of the2G TRX Power Down Threshold parameter. This feature is activated when both conditions are met: •
•
The value of the 2G TRX Power Down Threshold parameter is different from zero. Licenses of the RG301936: Intelligent MCPA TRX shutdownand BSS20984: 2G TRX Automatic Power Downfeatures are enabled.
Follow this procedure to verify that RG301936: Intelligent MCPA TRX shutdownfeature has been activated successfully.